Enterprise Resource Planning Blog Posts by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Troubleshooting to identify modifications during a process

henrietta_helena_erdei
Product and Topic Expert
Product and Topic Expert
‎2024 Jun 14 2:03 PM
539

In this post blog, I will guide you how to identify Z programs/ enhancements 

 

Introduction

 

Purpose and target

Many times the root cause of an issue is an incorrect coding in a custom program. For this reason, I created this blog to help you to exclude, if the root cause of the issue is an incorrect coding in your custom program. ( SAP does not support modification) 

Target audience: Functional, technical expert, Consultant

Version: SAP S/4HANA, ERP

 

How to identify Z programs/enhancements

There are 2 options to identify, if the root cause of the issue is a modification. 

 

1. Set a trace via ST12

  1. Go to Tcode ST12

henrietta_helena_erdei_0-1718283011119.png

 

  1. Once the trace is started open a new screen and execute the steps to recreate the process
  2. Once it is finished go back to Tcode ST12 and click button End traces & collect
  3. Select all of them and press enter
  4. Click on full screen button on the Collected trace analysis section
  5. Once the status is green the system finished with collecting the called programs

henrietta_helena_erdei_1-1718283011125.png

  1. The first line is the summary, so select the second one and click on the ABAP Trace
  2. Click on the program column (name)  to select it,  right click on the mouse and select sort in descending order

henrietta_helena_erdei_2-1718283011127.png

 

The Z programs will be listed. You can set breakpoint in every Z programs and test them one by one, if the incorrect coding in a Z program is causing the issue.

 

2. Via debugger by using the button Configure Debugger Layer

 

henrietta_helena_erdei_3-1718283137684.png

 

henrietta_helena_erdei_4-1718283137686.png

To jump between the Z programs use F5 button

Always ensure that it is still active

henrietta_helena_erdei_5-1718283137689.png

To skip the Z program you can use the Goto Statement

Menu >> Debugger >> Goto Statement

If you have any questions, feel free to ask on our SAP Community which is the official channel for consulting inquiries. ( modification) 


I hope this blog post was helpful for you. If so, click on "like" or "share". I'm looking forward to your feedback and thoughts or clarification questions you may have in the comment section below. 



Helpful links: 

 

Popular Blog Posts