SRM PO error-Account assignment cannot be changed after goods/invoice receipt

[Former Member]

Hi,

The SRM PO throws account assignment error in system (SRM7.2).

Scenario: Shopping cart is created and SRM PO is sent to backend system and GR is also posted.The purchaser is now trying to change any data like,value,currency etc and the system throws account assignment error.

The issue is system throws account assignment error for any change in other parameters but actually nothing is changed in account assignement part.This error is the backend error but not sure what can be done to stop this error.

Need guidance from experts whomever came across this type of issue.

Thank you

swathi

[Former Member]

We had the same issue and we implemented the notes mentioned 1869472 and it resolved the issue

Suresh

[Former Member]

Hi Swathi

Please refer the below note.

1869472 - Error ME458 - Account assignment cannot be change after GR / IR (in SRM or ECC side)

The resolution is provided in the above mentioned note.

Thanks

Abhishekh Narsingpuria

Message was edited by: Zoltan Keller please do not ask for points

[wendy_xu]

Hi Swathi,

Indeed many notes were introduced w.r.t. this issue.
So please tell me the Version and SP of your SRM and ECC.
Maybe I could provide some related ones for you.

Best regards,
Wendy

[Former Member]

Hi Wendy,

This is the system version we are using.

[wendy_xu]

Hi Swathi,

Please firstly follow the KAB 1869472 Abhishekh mentioned below, and implement all the notes in that KBA, and then test with a new PO created from the very beginning.

If you have old POs already affected in production and you don't want to change the customizing in OME9 in production, you could implement note 1915208, then delete the change version of the PO, and do the required changes again.

Regards,
Wendy

[Former Member]

Thanks a lot for all your responses.

I will update further after trying these notes.

Thank you

Swathi

[laurent_burtaire]

Hello Swathi,

ECC message is ME, number 458.

Make a where-used to check where it is called.

This is linked to existing customizing maintained in OME9 transaction.

Regards.

Laurent.

[jerry_martinek2]

Hi,

We started experiencing the ME 458 error last year when SAP introduced some new edits in BAPI_PO_CHANGE.

It's triggered when the SRM account assignment (CO and FM) fields do not match the ERP PO account fields.

SRM function B470_ACCSERV_CHECKACCASSIGNMT calls ERP function BBP4X_CODINGBLOCK_CHECK_47A. 

In our case this only happened for material POs, services do not have this problem.

There are numerous OSS notes out there for this problem, some are for MM and others for SRM.

Hope this helps.

Jerry

[Former Member]

Can you share a screenshot? What is the message number?

[Former Member]

Hi Manosij,

Please find the error detail.