SRM local PO CHANGE generates backend errors? But then dissappear?

[Former Member]

Hi there,

I have a strange situation where if I go CHANGE an SRM local PO that has already been ordered, let's say I increase the quantity or price and click the "CHECK" button I sometimes get errors like the following:

This purchase order has back-end errors
No instance of object type PurchaseOrder has been reated. External reference:
PO header data still faulty
External document number 3200000240 already assign d

But the really weird thing is if I click on check again a couple of time the errors eventually dissappear and I can order the PO.

And this error seems to only happen sometimes...very ad hoc.....

I do have the BBP_DOC_CHECK_BADI active but the code inside the custom development has NOTHING to do with these errors above.

Why on earth would it be trying to assign that PO number in the backened anyway if it is already created in the backend?

And ideas on this strange problem?

NOTE: We are on SRM 5.0

Any help would be greatly appreciated

Thanks

Lynton

[lisa_sheil]

Hi Lynton,

Have you also taken a look at note 1154122: BBP_POC : Backend Data validation from SRM, this note guides you through how to choose if you wish to have a backend check during a PO modification.

I understand this issue is random but if you wish you could have it that on PO modification no backend errors will appear.

Also the following notes 1091707 might be of interest for this issue.

1091707: BBP_POC:While Check a PO wrong error messages are displayed

1089752: Follow on note for 1044898: Issues with Local PO

I hope this helps,

Kind Regards,

Lisa

[Former Member]

hi,

Please check in RZ20 -CCMS monitoring in SAP B2B procurement under purchase order

to find out what is the reasons for the error

Regards

G.Ganesh Kumar

[Former Member]

Hi there,

The RZ20 monitor is active BUT these errors do not appear in there at all.

As I said I can literally click the button "ORDER" a couple times and the errors just "dissappear", very weird.

I think it is a LOCKING issue, I have seen this thread but am still trying to work out if it is a workflow lock in table or SM12 type lock.

Thanks anyway

Lynton

[Former Member]

Hi there,

I have just appiled Note 1025486 - Wrong error message ME218 when PO is locked at backend.

It seems to be pretty relevant, so going to wait and see if the error comes back now....

Lynton