Update Pricing Procedure in PO (Replication from SRM to ECC)

[Former Member]

Hi All,

We have an extended classic scenario where the PO is replicated from SRM to ECC. Our requirement is that the pricing procedure needs to be picked up from ECC and updated in the PO before the PO is posted in backend.

We tried to use the BADI-  BBP_ECS_PO_OUT_BADI  in SRM and BBP_PO_INBOUND_BADI  in ECC, but could not find the relevant fields to update the pricing procedure data.

Please advise if you have encountered this issue before/ if there is any other suitable BADI for this.

Thanks! MS

[vinita_kasliwal · Accepted solution]

Hi MS

In  BADI BBP_ECS_PO_OUT_BADI  in Extended classic scenario .what fields are you trying to add

the custom field is added on to the below structure ?

INCL_EEW_PD_ITEM_CSF_SC

INCL_EEW_PD_ITEM_CSF_PO

INCL_EEW_PD_ITEM_CSF_CONF

INCL_EEW_PD_ITEM_CSF

In this method : BBP_B46B_PO_OUTBOUND  you can map your custom fields

Put a breakpoint there and you will be able to see .

For picking up the pricing procedure from Ecc do you have the logic in place try to have a RFC call in SRM and create the logic here and then align it to pass to the backend and see if it works

Sample code:

        Customer fields

  MOVE 'POHEADER'               TO w_customer_fields-refobject.

*PO approver

  MOVE 'ZZAPPROVER'             TO w_customer_fields-fieldname.

  MOVE is_header-zzlastapprover TO w_customer_fields-container.

  APPEND w_customer_fields      TO ct_bapi_customer_fields.

*SC Date

  MOVE 'ZZSCDATE'               TO w_customer_fields-fieldname.

  MOVE lv_scheader-created_at   TO w_customer_fields-container(15).

  APPEND w_customer_fields      TO ct_bapi_customer_fields.

Regards

Vinita

[Former Member · Accepted solution]

Hi Vinita,

Thanks for your reply. We are working on this and will provide with an update.

Cheers, MS

[Former Member · Accepted solution]

Hello,

The structure for the pricing procedure is already present in the badi - BBP_ECS_PO_OUT_BADI  in SRM. We need to add the pricing conditions in that structure- CT_BAPI_POCOND and CT_BAPI_POCONDHEADER from the PO item/ header details.

No developments were required on the ERP side.

Thank you for helping us resolve this issue.

Cheers, MS