How To Fix SZDM_CC_CHKS_TITLES125 - An After Import Method 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: 125

• Message text: An After Import Method accessed a table with Native-SQL

What causes this issue?

A trace in one of the SAP internal test systems has found that your
after-import-method (AIM) accessed a database table by native SQL
(either EXEC-SQL or ADBC).
The name of the AIM 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 AIM 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 AIM accesses via native
SQL, then apply for an exemption for this ATC-message.
If you have not yet declared the table, then make the necessary
declaration in your development or maintenance system:
Call transaction SOBJ_EXT.
Enter the name of the transport object type that triggers the AIM.
Select "Used database tables" in the navigation area.
Enter the name of the table accessed via native SQL with an appropriate
value for "Access type" and "Lock mode".
If your AIM calls an API that is listed in transaction SLAPI and if this
API accesses the table via native SQL, then enter the name of this API
in "Used APIs". If the table is not yet declared in the SLAPI entry,
then ask the owner of the API to declare the table there.
If the RFC module calls an API that is not listed in transaction SLAPI
and if this API accesses the table via native SQL, then ask the owner of
the API to create an SLAPI entry for this API and to declare all
accessed tables there.

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_TITLES125 - An After Import Method accessed a table with Native-SQL ?

  The SAP error message SZDM_CC_CHKS_TITLES125 indicates that an After Import Method has accessed a table using Native SQL, which is not allowed in certain contexts, particularly during the import of transport requests. This restriction is in place to ensure data integrity and consistency during the transport process.
  Cause:
  The error typically arises when:
  
  An After Import Method (a piece of custom code that runs after a transport import) attempts to execute Native SQL statements to access database tables.
  The use of Native SQL can lead to inconsistencies or unexpected behavior, especially if the database structure has changed or if the transport is being applied in a different environment.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review the After Import Method: 
  
  Check the code in the After Import Method that is causing the error. Look for any Native SQL statements (e.g., OPEN SQL statements that are not using the standard ABAP SQL syntax).
  
  
  
  Refactor the Code:
  
  If Native SQL is being used, consider refactoring the code to use Open SQL instead. Open SQL is the recommended way to access database tables in SAP as it is database-independent and ensures better compatibility and stability.
  
  
  
  Testing:
  
  After making changes, test the After Import Method in a development or quality assurance environment to ensure that it works correctly without causing the error.
  
  
  
  Documentation:
  
  Document the changes made to the After Import Method for future reference and to inform other developers or team members.
  
  
  
  Transport Request:
  
  If the After Import Method is part of a transport request, ensure that the transport request is correctly configured and that all dependencies are included.
  
  
  
  Related Information:
  
  Native SQL vs. Open SQL: Native SQL allows direct access to the database using SQL syntax specific to the database system, while Open SQL is a SAP-specific abstraction that provides a consistent interface across different database systems.
  Transport Management System (TMS): Understanding how the TMS works can help in managing transport requests and their associated methods.
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or updates related to this error message.
  
  If the issue persists after following these steps, consider reaching out to SAP support or consulting with an experienced SAP ABAP developer for further assistance.