SAP Community - SAP HANA

Clean Core Alternative for Function Module(TERM_CONTROL_EDIT)

2026-04-03T14:39:24.006000+02:00

Dear Experts,

We are working on Clean Core compliance for our SAP S/4HANA 2023 On-Premise system. During ATC (ABAP Test Cockpit) checks, the function module [TERM_CONTROL_EDIT] was flagged as internal/unreleased.

Current Usage: This function module is currently being used in our custom code,

Request: We would like to understand:

Whether there are any released APIs or function modules available as alternatives to [TERM_CONTROL_EDIT]
If there is a recommended Clean Core-compliant approach to achieve the same functionality
Whether there are plans to release this function module or provide an alternative in future releases

System Details:

Product: SAP S/4HANA 2023 On-Premise
Purpose: Clean Core transformation and ATC compliance

We appreciate your assistance in this matter.

Clean Core – Need Released API Alternatives for Standard Tables and Classes in S/4HANA 2023 (On-Prem

2026-04-03T14:49:13.580000+02:00

Dear Experts,

We are currently working on Clean Core / ABAP Cloud compliance for our custom ABAP developments in S/4HANA 2023 (On-Premise).

As part of this effort, we are replacing direct usage of non-released objects (standard tables/classes) with released APIs (CDS views / RAP / whitelisted objects) in line with SAP’s Clean Core principles.

Objects Identified in Our Custom Code

We need guidance in identifying released alternatives (APIs / CDS Views / RAP BOs) for the following objects:

Classes

CL_EAML_AUSP_LFE_DATA_HANDLER

Standard Tables

ILOA
ADRC
ADRV

CDS Views (Need confirmation on release status or Alternative)

I_EQUIPMENTDATA
I_LINEARASSETMANAGEMENTDATA

Our Questions

Released API Availability
Are there any released CDS views / RAP BOs / APIs available as alternatives for:
- Functional Location / Equipment-related data (ILOA)
- Address data (ADRC, ADRV)
- Class CL_EAML_AUSP_LFE_DATA_HANDLER
CDS View Release Status
Are the following CDS views officially released for ABAP Cloud / Clean Core usage?
- I_EQUIPMENTDATA
- I_LINEARASSETMANAGEMENTDATA
Best Practice in Absence of APIs
In scenarios where no released API is available in S/4HANA 2023 On-Premise, what is the recommended approach:
- Create a wrapper class and expose as released API?
- Build custom CDS views on top of tables?
- Use key-user extensibility or side-by-side extensions?

What We Have Done So Far

Executed ATC checks (ABAP_CLOUD_READINESS / Clean Core checks)
Identified usage of non-released objects
Started replacing with released CDS views where available, but facing gaps for the above objects

Objective

Our goal is to:

Ensure compliance with Clean Core principles
Use only released and upgrade-safe artifacts
Avoid direct dependency on standard tables and unreleased classes

Request

If anyone has:

Mapping references (Standard Table → Released CDS/API)
SAP Notes or documentation links
Practical experience handling these objects in S/4HANA 2023 On-Prem

your guidance would be highly appreciated.

Clean Core – Alternative to Implicit Enhancement in Program SAPFC68A for Work Center Save Event

2026-04-03T15:00:53.171000+02:00

Dear Experts,

We are currently working on Clean Core compliance for our custom developments in S/4HANA 2023 (On-Premise) and have encountered a challenge regarding enhancements.

Current Scenario

We have implemented an implicit enhancement in standard SAP program SAPFC68A to capture data when Work Center master data is saved.

This enhancement is currently used to trigger custom logic during the save operation.

Clean Core Concern

As per Clean Core guidelines, implicit enhancements are not recommended, since they:

Modify SAP standard behavior
Are not upgrade-safe
Violate extensibility principles

What We Have Checked

We explored standard extensibility options but could not find a suitable alternative:

BAdIs (Business Add-Ins)
BTEs (Business Transaction Events)
User Exits

Unfortunately, none of the available options seem to support triggering logic specifically during Work Center save.

Our Questions

Recommended Approach
What is the SAP-recommended approach in Clean Core for handling such scenarios where:
- We need to trigger custom logic during Work Center save
- No suitable BAdI/User Exit is available
Alternative Extensibility Options
Are there any:
- Released BAdIs (even indirect ones)
- RAP-based or event-based mechanisms
- Business Object events or Enterprise Event Enablement options
that can be used for Work Center updates?
Fallback Strategy
In absence of any released enhancement option:
- Is implicit enhancement acceptable as a temporary workaround?

Objective

Our goal is to:

Remove implicit enhancements
Follow upgrade-safe and compliant extensibility patterns
Align fully with Clean Core principles

Request

If anyone has:

Experience handling similar Work Center enhancement scenarios
Knowledge of hidden/released BAdIs or events
SAP Notes or recommended architecture

your guidance would be highly appreciated.

Clean Core – Released API Alternative for Function Module CRAP_WORKCENTER_CREATE in S/4HANA 2023

2026-04-03T15:05:30.470000+02:00

Dear Experts,

We are currently working on Clean Core / ABAP Cloud compliance in S/4HANA 2023 (On-Premise) and are reviewing our custom developments to replace usage of non-released function modules.

Current Scenario

In our custom implementation, we are using the function module CRAP_WORKCENTER_CREATE to create Work Center master data programmatically.

However, this function module is not released for use under Clean Core / ABAP Cloud guidelines and is flagged during ATC checks.

Our Challenge

We need to identify a released and upgrade-safe alternative to achieve the same functionality (i.e., Work Center creation).

What We Have Checked

Searched for released BAPIs for Work Center creation

Our Questions

Released API Availability
Is there any released BAPI / RAP BO available for:
- Creating Work Center master data
- Updating Work Center data
Recommended Approach
What is the SAP-recommended approach in Clean Core when:
- A required standard function module is not released
- No direct API is available

Objective

Our goal is to:

Replace usage of non-released function modules
Ensure upgrade-safe and compliant development
Align fully with Clean Core principles

Request

If anyone has:

Knowledge of released APIs for Work Center create/update
SAP Notes or official documentation references
Experience handling similar scenarios

your guidance would be highly appreciated.

Practice System is full right now, but no worries... spots will open soon. Keep trying!

2026-04-04T07:49:56.015000+02:00

While trying to access Hands-on Practice for Intermediate ABAP Programming(S4D401) and Hands-on Practice for Data Modelling in ABAP Dictionary and ABAP Core Data Services(S4D430), I am getting the below error message

Temporarily unavailable

The Practice System is full right now, but no worries... spots will open soon. Keep trying!

Kindly let me know how long it will take for sap to provide access systems as I have to finish the modules for certification purpose.

Enable ssl in Hana replication for DR

2026-04-05T10:01:00.231000+02:00

Hello ,

Could you please help me in implementing the best practice of SSL activation for HANA DB replication with DR site?

Regards;

Clean Core – Released API Alternative for Table TMP_SPEC

2026-04-06T14:58:13.383000+02:00

Dear Experts,

We are currently working on Clean Core / ABAP Cloud compliance in our S/4HANA 2023 On-Premise system and are addressing findings from ATC (ABAP Test Cockpit) checks.

Background

During our analysis, we identified usage of the following standard table:

Table: TMP_SPEC
Application Component: MM-SRV (External Services Management)

This table is currently accessed directly in our custom code.

Business Requirement

We use table TMP_SPEC to:

Read model (template) service specifications
Retrieve service specification data required for maintenance planning and service processing

Current Challenge

Direct table access is flagged as non-compliant under Clean Core guidelines
We were unable to find:
- Any released CDS View
- Any released API / function module

that provides equivalent functionality for accessing template service specifications

Request

We would like to request clarification on the following:

Released API Availability
Is there any released API / CDS View / RAP BO available as an alternative to:
- Read model/template service specifications
- Access service specification data in a Clean Core-compliant way
Recommended Approach
What is the SAP-recommended Clean Core compliant approach to:
- Work with service specification templates
- Avoid direct access to table TMP_SPEC
Future Roadmap
Are there any plans to:
- Release an API or CDS view for this functionality
- Provide a successor object for TMP_SPEC

System Details

Product: S/4HANA 2023 On-Premise
Context: Clean Core transformation and ATC compliance

Objective

Our goal is to:

Eliminate direct table access (TMP_SPEC)
Use only released and upgrade-safe APIs
Ensure compliance with Clean Core principles

We appreciate your support in confirming whether a compliant alternative exists or if an Influence Request should be raised.

Career with SAP S4/Hana- I have 7 years of experience in SAP ARIBA as Front end.

2026-04-06T23:18:12.129000+02:00

Career with SAP S4/Hana- I have 7 years of experience in SAP ARIBA as Front end. I need proper guidance as to how to advance in a proper manner course difficulty wise. Need to grow myself here. Doubts I have like, should I go for S4 Hana and SAP Ariba, or S4 Hana or S4 Hana and Ariba and procurement and Sourcing. Please guide and help.

Deployment Issue HANA HDI: schemaParameterChangeNotSupported

2026-04-07T12:58:00.579000+02:00

Hi All,
We have recently performed Node upgrade from 18 to 20 for few services in our landscape.

After deployment of service, below error is encountered:
"{"error":"schemaParameterChangeNotSupported","description":"Changing the 'schema' parameter for instance '' is not supported (is '<Subaccountname-spacename-servicename>', was '<some guid>')"}"

I have observed that initially for few services the mta.yaml did not have config schema name as follows and these services are having above mentioned error:

config:

schema: ${default-container-name}

These 2 lines were added sometime later after intial deployment of these services.

We have had many deployments of these services after this addition but only now, our deployment is resulting into the specified error.

For these services, we have HANA HDI schema name as some guid and for rest others we have name of HANA HDI schema as <SubaccountName-SpaceName-ServiceName>.

Please suggest how to fix/proceed.

@anshuman_s22

Thanks.

Integrate Genesys with SAP S4 HANA by Softphone Connector

2026-04-08T15:22:36.413000+02:00

I need some information on integrating genesys with SAP S4 HANA by Softphone connector. Please help me on these if anyone knows about it.

Business Area (GSBER) not updated after Asset change in Purchase Requisition

2026-04-08T16:12:59.645000+02:00

We are facing an issue in Purchase Requisition (ME51N / ME52N) related to Account Assignment (Category A – Asset).

When a PR is created:

The Business Area (GSBER) is derived based on the initially entered Asset.
However, if the Asset (ANLN1) is changed afterwards, the Business Area is not updated accordingly.

Questions

Is this standard SAP behavior that GSBER is not re-derived after Asset change in PR?
Is there any standard configuration or setting to enable re-derivation of Business Area?
Does SAP recommend implementing a BAdI (e.g. ME_PROCESS_REQ_CUST) to handle this?
Is there any SAP Note addressing this behavior?

Best regards,

How is table ORDR field ImportEnt used?

2026-04-09T17:47:53.865000+02:00

https://help.sap.com/doc/089315d8d0f8475a9fc84fb919b501a3/10.0/en-US/SDKHelp/Marketing_Documents/ORDR.htm

There is no further explanation how this field is used. I currently work in a setup where this field in B1 has been somehow renamed (how can one do this?) and I need to know what its original purpose is and how it gets used in B1.

How to check the memory usage of a specific table in SAP HANA

2026-04-13T08:22:06.643000+02:00

How to check the memory usage of a specific table in SAP HANA

HANA DB User for Calculation View

2026-04-13T09:24:05.922000+02:00

The BW Team has requested HANA DB User for Calculation View.
In our landscape we have, BW on HANA version NW 7.5, HANA DB version 2.00.089.00 and HANA Cockpit version 2.18.5 in use. The BW team is using Eclipse version: 2023-06 (4.28.0)
To be able to provide the HANA DB user, what steps are required, which privileges to assign to this HANA DB user, which eclipse version should be installed. User to be created in System DB or Tenant DB, kindly suggest.

only active database instances are loaded into system memory

2026-04-14T07:57:25.686000+02:00

Dear Team,

Please ensure only active database instances are loaded into system memory,with a view to optimising RAM utilisation and reducing infrastructure cost .

Regards,

Amit

S4 HANA 2020 Upgrade On Premise - S4 HANA 2023 or S4 HANA 2025

2026-04-14T10:44:13.702000+02:00

Dear Experts,

Kindly suggest which is best and lesser time consuming.

S4 HANA 2020 to S4 HANA 2023 or

S4 HANA 2020 to S4 HANA 2025

How can I set up fields for TmSp_GetDefaultElementsforCR automated?

2026-04-15T14:50:57.973000+02:00

My company has a Database with 6 schemata (what Business One calls Companies).

a) How can I set up the fields of TmSp_GetDefaultElementsforCR (In Business One "Default Elements for Crystal Report") automated? For example, I'd need the field "foo" in all schemata with a given translation in English/Spanish/German/French.

b) How can I copy the whole bunch of a custom field (foo with all its translations, might be more than the four listed in a) into another schema?

Memory_Size of Expensive Statements in DB monitor

2026-04-16T13:26:37.545000+02:00

A huge value shows under column Memory_Size of Expensive Statements in DB monitor(DB02, DBACOCKPIT, etc.)

Is this OSS Note 3239915 applicable to only SCALE OUT or to SCALE IN as well

please confirm

partitioning recommendation for the acctcr table

2026-04-16T14:12:26.967000+02:00

Hello

We are analyzing how to proceed with the partitioning of the ACCTCR table, and the recommendation for partitioning the ACCTCR table, as per note 2044468 - topic 27 - indicates that we should perform partitioning by HASH using the AWREF column.

If our strategy is to apply NSE, we need to perform partitioning by RANGE. Which column should we use to perform the RANGE partitioning?

HANA does not retain table partitioning when a column is added to the table

2026-04-17T17:17:19.440000+02:00

When adding a column through a SAP(DDIC) transport the table partitions are merged. The table was partitioned because the row count was nearing the 2 billion limit and the column addition undid the partitions. Is this normal operations for HANA when a column is added to a partitioned table? If so, how do we avoid this?