PO changes not replicated fully in backend

[Former Member]

Hi,

We are running SRM 5.5 ECS linked to ECC6.0 running in ECS mode. PO's are raised in SRM and then replicated in the backend okay. When viewing the PO in R/3 - all appears ok including the GL account field. However, if the account assignment in the PO on SRM is changed say to a WBS element, then the original value for the GL account in the backend is removed and left blank.

BADI BBP_DOC_CHANGE_BADI (method BBP_SC_CHANGE) is used to pass back any changes to R/3, including the GL account which has been determined via BADI BBP_DETERMINE_ACCT. Debugging the BADI's has shown GL Account is populated, but I can't explain why the value is removed in R/3.

We not sure if this is SAP standard behavior, or whether it can be fixed by config changes or BADI's.

Any help would be much appreciated.

Thanks and regards

Marc

[Former Member]

Hi Marc,

If the data is being passed to the backend then you should report the problem to OSS as this is not normal behavoir.

We have the same system setup as you and we're experience MUCH pain in the area of service po replication, especially account assignment.

What level are your systems at.

If you get an OSS note, please post in the thread.

Thanks,

Jerry

[Former Member]

Hi Marc,

If the data is being passed to the backend then you should report the problem to OSS as this is not normal behavoir.

We have the same system setup as you and we're experience MUCH pain in the area of service po replication, especially account assignment.

What level are your systems at.

If you get an OSS note, please post in the thread.

Thanks,

Jerry

[ricardo_cavedini]

Hello,

You can check if changes applied to PO in question are reaching the BBP_PO_INBOUND. This FM is called from SRM to ECC in case of Extended Classic Scenario.

- Breakpoint at FM B46B_DPO_TRANSFER;

- SE37 BBP_PD_PO_TRANSFER_EXEC, enter PO header GUID and execute;

- Program will stop at FM where the BP was set.

- Look for statement CALL FUNCTION 'BBP_PO_INBOUND' DESTINATION lv_destination;

- F6 or F5 to debug into ERP (2nd session will start). Here you can check the table lt_bapi_return in order to check if the PO has been updated or not in backend.

- Otherwise, check if account tables have the values defined in your badi.

Regards,

Ricardo