on 10-19-2015 9:04 AM
Hi,
Has anyone tried to optimize this program when running your IP10 or IP30?
Currently, we have a slow performance issue when running the background job from IP30 transaction.
We have applied and followed the SAP notes about slow running and dump-occurring issues, but still did not work.
NOTES Applied and followed:
2167820
2140915
Hope someone can shed some light on this.
Regards,
Nazarene
Hi All,
thanks for all your replies.
we've discovered that the standard program was going into a loop where it will end up to the date 31.12.9999 after searching for the Maintenance package that was supposed to be assigned detected earlier.
we just changed the configuration message control to E for maintenance package so that no one will leave the field blank.
Regards,
Nahz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nazarene,
Are you using any developments in the maintenance plan calling or order creation process?
If so, they can dramatically slow the IP30 process down.
Try deactivating these developments and re-test.
Also get your ABAP Team to put a trace on IP30 to see where the performance issues arise.
PeteA
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nazarene,
Here i dont think you will get a solution.
Please contact SAP again, they should provide a solution or a work around for performance issue.
Are you able to identify whether this is due to data issue or standard program issue ?
Regards
Terence
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
7 | |
6 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.