on 2023 Jun 07 6:28 AM
Dear All,
Need support on below query.
We have a custom program which runs in background every day to create/ change requirements. This program uses FM BAPI_REQUIREMENTS_CREATE / BAPI_REQUIREMENTS_CHANGE. Since we have millions of records and database commits, it takes huge time to finish the job. To improve the performance we implemented parallel processing ( ref. Implementing Parallel Processing (sap.com) ). It has improved performance more than 40-50%.
We don not see any issues if run 3-4 parallel jobs. But if we increase the job numbers like 5, 6 etc., it causes issues like update processes are full, overloading system update queue, CPU bottleneck .
How this can be resolved from ABAP side and BASIS side to get maximum improved performance without causing system issues
Thank you.
Regards,
Manoj
Request clarification before answering.
Hello manoj_yadav
BAPI_REQUIREMENTS_CREATE / BAPI_REQUIREMENTS_CHANGE mange planned independent requirements, that is the demand plan.
I just cannot believe that your demand plan is so unstable that you need to change millions of planned independent requirements every day. If it were really so unstable, it would have huge impact on MRP planning and thus on the entire supply chain, you would have much bigger problems than long running jobs.
So it is either:
Best regards
Dominik Tylczynski
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Dominik,
Thank you so much for quick response.
Yes, you are right, we are creating planned independent requirements. There might be some reasons during initial development/design of this report. We are also not sure why they delete the requirements and create again everyday.
But as suggested, I will check if only changed records can be considered instead of all.
Best regards,
Manoj
You could make use of server group. You can set several limits in a server group. Like the maximum number of work processes being used.
jack.graus2 Of course server groups is also an option. Still I think the root cause is an incorrect design of demand update report that is deleting and recreating millions of records daily. That should not be the case - demand plans are not that unstable.
User | Count |
---|---|
78 | |
12 | |
9 | |
8 | |
7 | |
5 | |
4 | |
4 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.