Purchase Order Modification: External Document Number already assigned

[Former Member]

Hello,

We're running Extended Classic Scenario in a SRM 4.0 implementation.

The problem is the following: When the user modifies a purchase order (this purchase order is already replicated to the backend), sometimes (not always), the next error occurs:

"Purchase Order XXXXXXXXXX: PO header data still faulty "

"Purchase Order XXXXXXXXXX: External document number XXXXXXXXX already assigned"

The system does not provide additional info (RZ20 give us the same message, no ST22 dumps...

We think it could be some kind of error in the standard BAPI BAPI_PO_CHANGE.

We've revised the SAP OSS but didn´t find anything....

Some idea?

Regards and Thanks in advance!!!

[Former Member · Accepted solution]

Hi

<u>Any other rrors / dumps noticved in system using RZ20 and ST22 transactions ?</u>

<b>Have you seen this helpful pointers and link ?</b>

<u>The related SAP OSS notes are as under :</u>

<b></b>

<b>Note 1000184 - Account assignment error when document transfer to back end</b>

Note 966323 - Service Item: Not able to create PO in ERP backend

<b>Do let me know.</b>

Regards

- Atul

[Former Member · Accepted solution]

Hello,

No additional info in RZ20 / ST22.

Thanks for the help but the links you provided me are focused on the first replication / creation of the purchase order.

In my case, the purchase order is already replicated.

Moreover, when the user modifies a purchase order and the error occurs, if we try to post the modification again a bit later, the purchase order is modified correctly.

Strange thing....

[pvanhoove · Accepted solution]

Hello,

The reason could be a locked object (po, budget, contract...). There are many notes around this, check if any can apply in your backend .

rgds,

Pierre

[Former Member · Accepted solution]

Hello,

You were correct Pierre, the purchase order was locked.....

Thanks.

[Former Member · Accepted solution]

I have seen this behaviour too.. what do you mean with "locked", a user is locking the PO?