cancel
Showing results for 
Search instead for 
Did you mean: 

ME22N: change of PO details in backend not getting replicated with SRM 7.0

Former Member
0 Kudos

Hi All,

We have created Purchase order using shopping cart in SRM 7.0 extended classic scenario. The PO created in SRM 7.0 is replicated into backend in ME21N using a Custom BDC program.

But when the Purchase order is changed in SRM 7.0 the data is not getting replicated. We are not allowed to change the PO details in backend using ME22N (No change in SRM Backend is allowed ), So we are not able to write a Custom BDC program for that. Hence the PO is not getting closed and throwing error.

Please suggest me an alternative.

Regards,

Lakshmi Narayana

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Laurent,

we had other cusumizations so not using SAP SRM standard functionality.

Regards.

Lakshmi.

laurent_burtaire
Active Contributor
0 Kudos

Hi,

Being in Extended Classic Scenario, PO cannot be in change mode in R/3.

This is due to check done on PO status (fied STATUS from EKKO table).

When PO is created by SRM replication, its status is 'K' (Purchase Order from BBP). What you could do is to substitute this status with value 'I' (Purchase Order from BAPI) using BAdI BBP_ECS_PO_OUT_BADI.

In this way, R/3 PO can be modified in R/3.

Nevertheless, by doing this, you won't have your SRM PO output after modification(s) (as it is done in standard) because changes are in R/3.

To be able to get an R/3 PO output with ECS, see following note:

883693 - ECS: PO output determination in R/3.

Regards.

Laurent.

laurent_burtaire
Active Contributor
0 Kudos

Hello Lakshmi,

Why did you create a customer program to replicate PO from SRM to R/3 ????

This is SAP SRM standard functionality.

Regards.

Laurent.