Skip to Content
Author's profile photo Neal Zhou

Substitution trouble shooting (debug)

This blog’s purpose is to provide the steps to trouble shooting from the code level by debugging.

1. Execute t-code: “GGB1”, this will show you all the substitution definitions.

     /wp-content/uploads/2016/08/1_1011472.png

2. Find your own substitution definition. (in our example, we use a substitution for FI at line item level). Click on the substitution definition and then in the command field input “=shcb”. This will show the source code of the substitution.

      /wp-content/uploads/2016/08/2_1011477.png

3. In the source code part, please set a breakpoint for the target step (the target step means the steps you defined under the substitution, in our example it’s step “001” then you can set the breakpoint at line “G_STEP = ‘001’”, if you’re using other steps, let’s say it’s step 011, then you can set a breakpoint at line “G_STEP = ‘011’ ”.

      /wp-content/uploads/2016/08/3_1011478.png

4. Reproduce your issue and the system will enter debug mode, then you can trace the substitution debugging value to see where the problem is.

Assigned tags

      4 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Adrian Hudgins
      Adrian Hudgins

      Incredibly helpful, thank you!

      Author's profile photo A. de Smidt
      A. de Smidt

      Thanks very helpful article 🙂

      Author's profile photo Vamshi Mohan Patil
      Vamshi Mohan Patil

      Thanks a lot. Very helpful 🙂

      Author's profile photo Olivier Su
      Olivier Su

      66666666666666666666666666666666666666666666666666