Payment terms chagnes in EBP are not replicated to R/3

[Former Member]

Hi SRM Experts,

Changes to Purchase order in EBP are not replicated in R/3 system.

We have created purchase order in EBP extended classic scenario & changed payments terms these chagnes are not replicated in R/3 system.

What could be the problem.

Regards

Ravi Shankar.

Edited by: RAVI SHANKAR H.N on Oct 14, 2009 1:22 PM

[Former Member]

BADI implemented.

[Former Member]

This kind of updation mismatches are found common in EC scenario. Try to run the cleaning jobs once again, as a workaround pls do some dummy change in PO in SRM and then re trigger the PO change again to R/3 then it must update. Root cause is not known..but assume some performance issue with the component.

Thanks

Kiran

[Former Member]

Hi Kiran,

I tried all the possiblities but still it is not working.

Regards

Ravi Shankar

[Former Member]

Hi

we do had similar problem. Implemented the BADI BBP_PO_INBOUND_BADI, after we raised message with SAP.

Proposed solution was:

Noticed that the problem is at POHEADERX, here the `X` is missing

in the following fields:

DSCNT1_TO X

DSCNT2_TO X

DSCNT3_TO X

DSCT_PCT1 X

DSCT_PCT2 X

I have inserted X in the test data, and checked the PO at ME23N. The newpayment term PT09 is successfully updated to backend PO.

So, please implement the badi BBP_PO_INBOUND_BADI at your backend

system ABCCLNT100, and fill the `X` in the above mentioned fields

at structure POHEADERX and pass it to BAPI_PO_CHANGE. It should solve

the problem.

R/Reddy.

[former_member183819]

Thanks reddy . Many customers had the same issue.

It definetly helps community

BR

Muthu