on 2016 Feb 09 10:26 AM
Hi Experts
We have a problem whereby some packages which have failed in the BW backend (and are not longer running as a job in SM37 or SM50) are still showing as "Running" in the Package Status within EPM.
I checked the process chain (in this case /CPMB/COPY) and could see that it had failed as a 'red'.
What had actually happened was that the user attempted to 'Abort' the run of this package. This appears to have worked but the status does not reflect the outcome.
Is there anything we can do to update these statuses ?
Thanks
Ian
Request clarification before answering.
Hi Ian,
Can you please check what is the status of the job in SM37?
Also, please let us know what BPC SP you are using.
Regards,
Gersh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
May be after some time it will become failed after timeout
I remember the behavior like this in the past...
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ian,
Please check if UJD_STATUS table information is inline with the process chain execution status for the package you have executed. If not then update the table entry, I think that should align frontend status with back end status.
Thanks
Prashant
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 7 | |
| 7 | |
| 6 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.