cancel
Showing results for 
Search instead for 
Did you mean: 

Extended Classic Scenario, BADI for PO creation in R/3

Former Member
0 Kudos

Hi,

We are using the extended classic scenario. When the PO gets replicated from SRM to R/3, right now the field CATALOGID is not being transmitted to the backend R/3 system.

1) What BADI should I implement (and the method) to transmit the CATALOGID to R/3?

2) After implementing the BADI, do I also have to change the BAPI?

3) Is the BAPI used to transfer data from SRM to R/3, BAPI_PO_CREATE?

Thanks and Regards,

Peter

Accepted Solutions (0)

Answers (1)

Answers (1)

yann_bouillut
Active Contributor
0 Kudos

Hi Peter,

1-You can use BBP_ECS_PO_OUT_BADI for ECS scenario.

Since the R3 PO does not have field for catalog id, the EKKO- BEDNR (Tracking Number) field can been used for example to store this information. In this BADI all the items are identified and their tracking number field is populated with a catalogue id value.

2-If you use the tracking number field, no use of R/3 BADI is required.

3-BAPI_PO_CREATE1

Please check my answers in this post :

Kind regards

Yann

Message was edited by: Yann Bouillut

Message was edited by: Yann Bouillut

Former Member
0 Kudos

Hi Yann,

The answers were very helpful. Want to award points, but do not see any stars on the left hand side of the answer. Let me know how can I award points.

Regards,

Pete

yann_bouillut
Active Contributor
0 Kudos

Hi Peter,

I do see the star....

but you maybe have set the post flag off while creating the post.

You can open a new thread. I will then answer with link to this post

Thanks ! )

Kind regards,

Yann

Message was edited by: Yann Bouillut