Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: SZDM_CC_CHKS_TITLES - Title messages related to check classes
Message number: 126
Message text: An XPRA report accessed a table with Native-SQL
A trace in one of the SAP internal test systems has found that your XPRA
accessed a database table by native SQL (either EXEC-SQL or ADBC).
The name of the XPRA 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.
If the XPRA 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.
If you have already declared the table that your XPRA 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:
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Call transaction SLAPIError message extract from SAP system. Copyright SAP SE.
SZDM_CC_CHKS_TITLES126
- An XPRA report accessed a table with Native-SQL ?The SAP error message SZDM_CC_CHKS_TITLES126 indicates that an XPRA (a type of report used in SAP for data migration or adjustments during upgrades) has accessed a table using Native SQL, which is not allowed in certain contexts. This error typically arises during system upgrades or when executing specific reports that are not compliant with the current system's data access rules.
Cause:
- Native SQL Usage: The XPRA report is trying to access database tables directly using Native SQL, which can lead to inconsistencies and is generally discouraged in favor of Open SQL.
- Upgrade Issues: This error often occurs during system upgrades when certain reports or programs are not updated to comply with the new standards or restrictions.
- Custom Code: If there are custom developments or modifications that utilize Native SQL inappropriately, this can trigger the error.
Solution:
- Review the XPRA Report: Check the specific XPRA report that is causing the error. If it is a standard SAP report, ensure that you are on the latest version of the software, as SAP may have released a fix.
- Modify Custom Code: If the error is due to custom code, refactor the code to use Open SQL instead of Native SQL. This will ensure better compatibility with SAP's data access rules.
- Check for Notes: Look for SAP Notes related to the specific XPRA report or the error message. SAP often provides patches or workarounds for known issues.
- Consult Documentation: Review the documentation for the XPRA report to understand its requirements and limitations.
- Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance.
Related Information:
By addressing the underlying cause of the error and ensuring compliance with SAP's data access standards, you can resolve the issue effectively.
Get instant SAP help. Sign up for our Free Essentials Plan.
SZDM_CC_CHKS_TITLES125
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 na...
SZDM_CC_CHKS_TITLES122
A Configuration-Task uses RFC-calls
What causes this issue? A trace in one of the SAP internal test systems has found that your configuration task calls a function module via RFC. The n...
SZDM_CC_CHKS_TITLES127
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 SQ...
SZDM_CC_CHKS_TITLES130
An After Import Method performed a non-declared read-access to a table
What causes this issue? A trace in one of the SAP internal test systems has found that your after-import-method (AIM) read from a database table that...
Click on this link to search all SAP messages.