- SAP Managed Tags:
Se você gostaria de ler esse blog post em português, veja (link).
Hello, everybody,
This is the first post of a two-post series about the Messaging Framework Flow Execution (/TMF/MF_FLOW_EXEC) solution and its updates provided in SAP Note 3430381.
The Flow Execution (/TMF/MF_FLOW_EXEC) solution is part of the Messaging Framework in the SAP Tax Declaration Framework (SAP TDF) and now enables the parallel execution of event flows in two complementary ways:
1. Parallelization of the processing sequence, covered in this post.
2. Parallelization of the step processing, covered in the second post of the series.
The main goals of these are optimizing event processing and improving performance in high-volume scenarios.
What is a processing sequence?
To better understand this, we need an example, so imagine a scenario where:
- 1000 events are to be processed
- /TMF/MF_FLOW_EXEC has been scheduled to run a single job
- On the selection screen, only the Flow parameter equals EVENTR and BATCHR.
This scenario is more suitable for low-volume event scenarios, and the process runs sequentially from start to finish. For example, using the scenario created above, the Release step will only be initialized after all 1000 events have finalized the Validation step.
The image above illustrates the processing sequence.
Optimization in the Processing Sequence
The Flow Execution (/TMF/MF_FLOW_EXEC) solution is suitable for a high volume of events since it can manage the competition between the processing steps, enabling parallel execution.
For this to be possible, you must create multiple jobs informing only the steps where you want parallelism or leave them blank. If you leave them blank, the program manages the processing steps and it’s important to use the Endless Execution option.
To use the Endless Execution option, follow the steps described in Setting up Endless Execution | SAP Help Portal
To better understand how this optimization works, let's look at an example:
Assuming there are 10000 events to be processed and 5 jobs have been initialized. When the first job initializes it will reserve the Validation step; the second job will reserve the next step, in this case, the Release step, and so on.
Therefore, at each step that the event finalizes, this event is immediately available to be processed by the following steps. Because of this, the system does not need to wait for all 10000 events to process to start the next step.
For more product documentation related to the Messaging Framework - Flow Execution solution access the Help Portal.
We'd love to hear from you. Leave your comment below if you have any questions or suggestions for an upcoming post. And don't forget to follow the tag SAP Tax Declaration Framework for Brazil here in SAP Community to stay connected with the latest news about the Tax Declaration Framework (TDF).
See you next time!
Bruno Maciel
SAP TDF Development Team
| User | Count |
|---|---|
| 7 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
