Direct Material requisition from ECC to SRM Sourcing Cockpit ( Badi/ User exit for this requirement)

[Former Member]

Hi All  ,

The requirement is  1. send PR’s with Item category (blank, L, K) and without acct. assigned (direct PR’s) from CPPR to SRM RFX .

                                 2. Remove Direct Procurement (DP) flag for MRP generated PR’s.

                                            3.Flag these PR items with Z-field for easy identification

                                            4. In SRM fill the account assignment information with valid commitment item

We can use BAdi ' ME_REQ_SOURCE_CUST' to transfer PR ( whose item category is blanl ,L ,K ) from CPPR to SRM  .So the first requirement can be done .

But for 2, 3 and 4 th requirement , the badi ME_REQ_SOURCE_CUST' cannot be used becoz there is no changing parameter contains Direct procurement flag .

For the 3 rd requirement how can we create Z-field and while moving to SRM

Is there any BADI / User exit available to meet requirement 2 , 3 and 4 .

Thanks and Regards

sijin KP

[channu_s]

Hello Sijin,

Did you got the solution for this?

Thanks

CB

[vinita_kasliwal]

You havent mentioned all the details to be able to help you . However please answer below queries

Classic / Ext Classic ?

PI or SOA or RFC ?

BAdIs which may affect the transfer process of the PO:

Extended classic:PO transfer    BBP_ECS_PO_OUT_BADI

Other FM

BBP_PD_PO_TRANSFER_EXEC

B46B_DPO_TRANSFER

BBP_PO_INBOUND (ECC)

BAPI_PO_CREATE1 (ECC)

You can map the custom fields in parameter bapi_extensionin of badi BBP_PO_INBOUND_BADi...

Classic : Implement the BADI, BBP_CREATE_BE_PO_NEW, creating the new implementation of interface IF_EX_BBP_CREATE_BE_PO_NEW, method FILL_PO_INTERFACE1. This BAdI will only be called in classic scenario when RFC is used to create documents in ECC.

In classic scenario, if ESOA is used, then BAdI /SAPSRM/BD_SOA_MAPPING should be used.

Refer link :

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=340264144