Improve the Debugging Process for Dynamic Actions

  • by Deepankar Maitra, Senior Manager, Accenture
  • April 8, 2011
Learn how to write dynamic actions to automatically create records and quickly identify and resolve HR infotype debugging issues that can sometimes occur.
Key Concept
Dynamic actions are an effective way of adding or updating HR infotypes. During a standard HR business process such as hiring, promoting, or terminating, there is always a need to automatically create a record to reduce the effort for the user as well as to enforce the standard used in the organization so that the data is accurate. For example, every salaried staff needs to have a 5X8 weekly work schedule, which is essential for other SAP processes such as time capture. The hiring administrator can be asked to create this every time a new salaried employee is hired. However, an easier way is to create this record automatically for salaried employees through dynamic actions every time a hire action is performed in the system.

Although dynamic actions are very effective, they can be a challenge to debug. Only one table — T588Z — has all the dynamic action statements. It is not possible to split the logic into multiple tables so that it is easily readable. If complex scenarios are implemented using this SAP mechanism and they are not working well, it becomes very difficult to figure out where the problem lies. This is particularly true if the dynamic actions are a part of a global implementation that incorporates logic for different countries for the same infotype in the same table.

I am going to explain how the debugging process can be made simple, so that the problem can be diagnosed and resolved quickly. For example, salaried staff are supposed to be assigned a 5X8 work schedule, but they have been assigned a 4X10 instead by the dynamic action routine. It is 1,000 lines long, has evolved over the last 10 years, and has very little documentation. Several lines seem to assign the 5X8 schedule, but you really don’t know which line is being executed in this specific instance. If you knew you would find out what is causing this issue. I am going to discuss how you can get to the bottom of this issue by:

  • Structuring the code
  • Using debugging techniques to identify the code that is not working correctly
Note
This article does not cover basic concepts of how to write dynamic actions. For more information about how to write dynamic actions, refer to standard SAP documentation or reference previous articles about dynamic actions in the knowledgebase.

Deepankar Maitra

Deepankar Maitra has more than 25 years of consulting experience specializing in SAP-based solutions for human resources, supply chain, and reporting in multi-national companies around the world. He has successfully directed large implementation projects as solution architect, delivery manager, global lead, and country lead. His expertise lies in pragmatic harmonization of data and synthesis of processes using tools that improve process execution through quantum leaps in productivity.

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.