How To Fix SZDM_CC_CHKS_TITLES127 - A Configuration-Task accessed a table with Native-SQL

SAP Error Message - Details

• Message type: E = Error

• Message class: SZDM_CC_CHKS_TITLES - Title messages related to check classes

• Message number: 127

• Message text: A Configuration-Task accessed a table with Native-SQL

What causes this issue?

A trace in one of the SAP internal test systems has found that your
configuration-task accessed a database table by native SQL (either
EXEC-SQL or ADBC).
The name of the configuration-task and the name of the system where the
trace was executed and where you can find the call stack leading to the
native SQL command can be found in the detailed messages. Inspect the
call stack in order to find out the name of the accessed database table.

System Response

If the configuration-task runs as part of a zero-downtime-upgrade in a
customer system, then the upgrade procedure aborts with an error
message. Solving this kind of errors requires help from the SAP
development support.

How to fix this error?

If you have already declared the table that your configuration-task
accesses via native SQL, then apply for an exemption for this
ATC-message.
If you have not yet declared the tables, then make the necessary
declarations in your development or maintenance system:
The class implementing your configuration task must implement interface
IF_TR_CTS_CFG_TASK.
In method GET_TASK_META_DATA, declare the tables the RFC-module accesses
by implementing a call of method IR_META_DATA->ADD_TABLE(...). For each
table, provide an appropriate value for ACCESS_TYPE and LOCK_MODE.
If the RFC module calls an API that is listed in transaction SLAPI, then
declare this API by implementing a call of IR_META_DATA->ADD_SLAPI(...).
If the RFC module calls an API that is not listed in transaction SLAPI,
then ask the owner of the API to create an SLAPI entry for this API and
declare all accessed tables there. Declare this new SLAPI entry in your
implementation of GET_TASK_META_DATA by implementing a call of
IR_META_DATA->ADD_SLAPI(...).

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

<DS:TX.SZDM_CC_GENERAL_ZDO>Further information ...</>

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SZDM_CC_CHKS_TITLES127 - A Configuration-Task accessed a table with Native-SQL ?

  The SAP error message SZDM_CC_CHKS_TITLES127 indicates that a configuration task has accessed a table using Native SQL, which is generally not recommended in certain contexts within SAP. This error typically arises in the context of SAP's Data Management or Configuration Management processes, where the system expects to use standard ABAP methods for data access rather than direct SQL queries.
  Cause:
  
  Native SQL Usage: The error is triggered when a configuration task attempts to access database tables directly using Native SQL instead of using the appropriate ABAP data access methods (like Open SQL).
  Best Practices Violation: Using Native SQL can lead to issues with database independence, security, and maintainability. SAP encourages the use of Open SQL for these reasons.
  Configuration Task Design: The design of the configuration task may not adhere to SAP's guidelines, leading to this error.
  
  Solution:
  
  Review the Code: Check the configuration task code to identify where Native SQL is being used. Look for any EXEC SQL statements or similar constructs.
  Refactor to Open SQL: Replace Native SQL statements with Open SQL statements. Open SQL is designed to be database-independent and is the preferred method for accessing database tables in SAP.
  Testing: After making changes, thoroughly test the configuration task to ensure that it functions correctly without the Native SQL calls.
  Consult Documentation: Refer to SAP documentation or guidelines regarding best practices for data access in configuration tasks to ensure compliance.
  
  Related Information:
  
  Open SQL vs. Native SQL: Open SQL is a subset of SQL that is designed to work with SAP's database abstraction layer, allowing for better portability and security. Native SQL, on the other hand, is specific to the underlying database and can lead to issues if the database changes.
  SAP Notes: Check for any relevant SAP Notes that may provide additional context or solutions for this error message.
  SAP Community: Engage with the SAP Community forums or support channels for insights from other users who may have encountered similar issues.
  
  By addressing the use of Native SQL in your configuration tasks and adhering to SAP's best practices, you should be able to resolve the error and improve the maintainability of your code.