How To Fix SZDM_CC_CHKS_TITLES125 - An After Import Method accessed a table with Native-SQL


SZDM_CC_CHKS_TITLES125 - Overview

  • 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

  • Show details Hide details
  • 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.


SZDM_CC_CHKS_TITLES125 - Details

  • 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

    Already have an account? Login here!




Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


SZDM_CC_CHKS_TITLES125 - Related SAP Errors

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author