catalogid field not going in R3 backend

[Former Member]

hi all,

Catalog id field is there in SRM PO but this field is not there in R3 PO.

How can i get this field in R3 PO.

I am working in SRM 4.0 extended classic scenario.

Thanks,

Smita

[yann_bouillut]

Hi Smita,

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 catalofue id value.

Kind regards,

Yann

[Former Member]

Thanks Yann!

I am going to implement BBP_ECS_PO_OUT_BADI and inside this i am going to assign BBPS_IF_BAPIMEPOITEM_PI-TRACKINGNO = BBP_PDS_PO_ITEM_D-CATALOGID

for all the items.

Is there anything else i need to do in the R3 side?

Warm Regards,

Smita

[yann_bouillut]

Hi Smita,

No as tracking number is standard.

Kind regards,

Yann

[Former Member]

hi Yann,

I explored EKPO table and Tracking no field has been used. There is other field we can use as we have explored all options.

We will have to go for a custom defined field at R3 side and then pass the catalogid there.

Can you help me out how to achieve it.

Thanks & Regards,

Smita

[yann_bouillut]

Hi SMita,

Maybe you can find another R/3 PO standard field to store your catalog id.

If not :

You will have to use R/3 PO badi to transfer the tracking field value to your custom PO field.

Kind regards,

Yann

[Former Member]

Thanks Yann !

Can you give me some more idea about the R/3 PO Badi.

What will be approach for this? Where all i need to do coding to achieve this.

Warm Regards,

Smita

[yann_bouillut]

Hi Smita,

Not sure, but check R/3 extension SAPL2012 in transaction SMOD.

There is the option of populating customer-specific fields for header, item, or account assignment data via the parameter EXTENSIONIN.

Kind regards,

Yann