Skip to Content

Code Debugging

Hi,

Is there a way to find this kind of name in my solution? I assume this is a business object? Y5Y6****_CL_IC8************** because I need to check the code inside this object and change the necessary adjustments. But I can't trace this object because of the name SAP support gave me when I wrote an incident.

Regards,

JM

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jan 10 at 04:04 AM

    Dear JM,

    This is the backend Class information from ABAP you cannot find it via SDK.

    You have to recheck your absl file and you custom implementation by using debug SDK functionality.

    Regards
    Anant

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Anant,

      Can I trace it by doing the debug of sdk? I've been trying to debug it but the information I need does not pop-up.

      Regards,

      JM

  • Jan 11 at 02:16 PM

    Dear JM,

    Without logging into the backend of your tenant, it would be very difficult to answer this query from here.

    However maybe these details may help you to solve this:

    - Solution ID: Y5Y6****

    - Script file: the IC represents relationship to the file name.

    I would recommend reproducing the scenario again in your tenant (if possible) with debugging switched on in the SDK. Check the scripts that execute with the information the SAP Engineer provided and correlate the scripts.

    Alternatively, re-open the incident and ask for the correct name for your testing.

    Thank you JM. Have a good weekend! :)

    Regards

    Andy Blankley

    Add comment
    10|10000 characters needed characters exceeded

    • Hi JM,

      Unfortunately, I cannot connect to your tenant without an incident opened to our Support System.

      If you are still unsure of the root cause of an issue or the details, please re-open the incident that you mentioned and ask the support colleague to provide more information. They should be in a position to provide you the file path / line number of the affected ABSL script file.

      Regards,

      Andy Blankley