cancel
Showing results for 
Search instead for 
Did you mean: 

SE Sheet updated a different PO

ajitkumar
Active Contributor
0 Kudos
109

While creating a Service entry sheet for PO 10, another service PO, 09, of the same plant got updated in the PO history. In the SE sheet, the referred packages are of PO 10 ( P, I of ESLL data of the SE sheet ).  There are no update errors in SM13

PO 10 was not permitting further SE sheet even after deleting the created SE sheet. This got corrected with report rmbestk3

Though a single instance, any clue how updation of a different PO could happen ?

Thanks
Ajit

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos
ajitkumar
Active Contributor
0 Kudos

Thanks for the response. The note appears to be the solution . But we have got this error only on one instance in over 50000 SE sheets created so far. Subesquent posting, after cancelling the SE sheet also went to the correct PO.

Is it advisable to apply correction in such scenario too?

Former Member
0 Kudos

Notes published by SAP doesn't necessarily have to be resolving an issue which has been occuring very frequently, we have come across Notes which actually Solved only once and also there are Notes which we have applied hoping that the error might not occur in the future, even though the error had never occured before.

So can't really judge whether this is one time or multiple. But one thing is certain, applying the code correction will ensure that the error doesn't occur again. Atleast hypothetically!!!

/Manoj

JL23
Active Contributor
0 Kudos

such notes are automatically included in hotpackages as it  fixes program errors that happened at some SAP customers. when you implement the hotpackages, then you get those fixes automatically.

Of course some fixes cause other problems and need again to be fixed.

But this cannot be avoided, this is the remaining risk.

Answers (0)