Account Assignment is going wrong to backend when SC's are copied

[Former Member]

Dear SRM Gurus,

We are using SRM 5.5 Extended classic scenario. In this we have created a new SC by copying the old one and just changing the asset number in the cost assignment. SC is created correctly and a PO is created correctly with reference to that SC. The account assignment of that PO is also the same as SC, but when the PO is approved and posted in backend the R/3 PO IO number in the account assignment is different from PO of SRM. Asset number in backend(SAP R/3) PO is coming same as SRM PO but the IO number is different, it is picking the IO number of the Asset from which the SC is copied.

Can anybody tell the reason why it is happening only when we are copying a old SC having Asset as cost assignment to a New SC and changing the asset.

Can anybody tell the funcional module or BAPI which is used to transfer the PO data from SRM and creates a PO in R/3(backend system).

Thanks in Advance,

Chandra Sekhar.

[Former Member]

Hi

<u>This definitely seems to be a bug in the SRM system.Seems like it's side-effect of previous SAP Note or some SAP OSS Note is missing..</u>

The function module or BAPI which is used to transfer the PO data from SRM and creates a PO in R/3(backend system) is

<b>Function module - BAPI_PO_CREATE1 function module in R/3 is called as RFC call from SRM system..</b>

<u>Any of the Business Add-Ins can be used (since each of them gets called)</u>

BADI - BBP_CREATE_PO_BACK

BBP_ECS_PO_OUT_BADI

BBP_CREATE_PO_BE_NEW

<u><b>P.S. Please Read the relevant SAP documenatation of these BADIs before implementing the same.</b></u>

<u>Hope this will help. Do let me know.</u>

Regards

- Atul