How to understand how SAP workflow triggers
Today, I will talk to you about how to understand SAP workflow triggering. Many people may not know much about it. In order to make you understand better, the editor has summarized the following for you. I hope you can get something according to this article.
In general, SAP workflows can be triggered in many ways. For example, we can trigger events by calling standard business objects, either based on status, at the user exit, or in BADI, and so on. However, sometimes you will find that an event can be triggered in a standard business object type, but not in a business object type that inherits it. This is because the trigger object in the standard code is the standard object of the call, so the inherited object cannot trigger the standard event. If there is no user exit or BADI available at this time, it can be painful to trigger the process. But you don't have to be in pain. Xiaosheng offers you a trick to "have a good waist, good shoulders, good legs and feet."
Establish a trigger process, trigger the process through standard things, and then establish a trigger event in which the trigger agent joins its own object, and pay attention to passing the standard trigger object into its own object at this time. Let us create another process, and the trigger event is the trigger event of your own object. At this time, the last object that triggered the process has been passed in and successfully imported into your object instance.
Workflow in SAP is really chicken, inflexible, and complex to develop.
After reading the above, do you have any further understanding of how to understand SAP workflow triggering? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.
