on 2021 Jul 07 2:58 AM
Hi.
I would like to understand the behaviour of the BPC package status.
We are in the midst of upgrading our BPC from 10.0 to 10.1.
In 10.0 (Production), we managed to run package with status Succeeded although the custom BAdI generated message with status E & I. In the log, I can see there is a few rejected line coming from the BAdI with status E.
But in 10.1 (Development), it does not work like that. We have copied same set of data like Production and the output log is similar for both systems after we ran the package. The only different is the package status returned Failed status.
Production (10.0): BAdI status = I & E, script logic status = ? I assume S, final status = Succeeded
Development (10.1): BAdI status = I & E, script logic status = ? I assume S, final status = Failed
So, I'm wondering is there any SPRO setting that we need to activate for the package status?
I understand if you will question me why I still need the final status as Succeeded although there are rejected lines from BAdI. This is their practise. They will download the log to see the status for each record and for them, all packages should return Success status.
Thanks for reply. I just got the answer after checking with OSS.
The logic to populate the package status is different between 10.0 and 10.1. You may refer to class CL_UJK_RUN_LOGIC (method EXECUTE_LGX) via Tcode SE24. Try find 'warning' word in the coding.
In 10.1, there are more validation and logic to update the warning status.
Example: If the BAdI returns message type I or W, the class will update the package status as Warning.
This answered my question on why in PRD (10.1), all packages have Success status although there is rejected record returned by BAdI. Compared to DEV (10.0), the status is Warning. It is because of 10.1 new logic.
Since my users want to have same status as PRD, then I have to change the message status in BAdI from I / E to S. Then class CL_UJK_RUN_LOGIC will update the pacakage status as Succeeded.
Thanks anyway.. have a nice day!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please read the following notes:
https://launchpad.support.sap.com/#/notes/0002771555
https://launchpad.support.sap.com/#/notes/0002663218
https://launchpad.support.sap.com/#/notes/0002391076
P.S.
The most relevant:
https://launchpad.support.sap.com/#/notes/2487016
https://answers.sap.com/questions/113793/how-to-stop-the-script-execution-in-case-of-error.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi sumaiya.zaidj,
Logic for decide package status should be connsistent between 10.0 and 10.1 if there is no other reason caused difference, I would recommend you to raise a ticket to SAP.
Best regards, William
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.