ERP PO doc type created from SRM is not taking correct docum

[former_member203412]

Hi,

We are using SRM for Sourcing Process with PI integration..

Following is the Process:-

1, Pr created in ERP

2, This PR will be moved to SRM for Sourcing throug CPPR

3, Bidding process done in srm,

4, Bid will be awarded as PO in ERP

We are able to run end to end successfully, Only problem we are facing

is the Doc type restriction

in ERP we have NB pr linked only to NB PO,

FO pr linked only to FO PO,

ZM pr linked only to ZM PO,

for NB Pr after sourcing in SRM its creating NB PO in ERP,

but for FO pr after sourcing it is trying to create with NB PO type.

we have implemented the SAP Note 1709468 - CPPR: PO generation only

with document type NB possible, but still we are facing the issue

Please find the error message.

" Doc. type/item cat. FO/D (requisition) <-> NB/D (purch. order)"
" Purchase order item 00001 still contains faulty schedule lines "

Thanks & Regards,

Venkatesh M.

[former_member203412 · Accepted solution]

Thanks for you are Help.

I had Solved the Issue by Implement the BADI : PUR_SPOT_SE_PURCHASE_ORDER

Method INBOUND_PROCESSING.

This Badi will triggers before creation of PO in R3.

Regards,

Venkatesh M.

[former_member203412 · Accepted solution]

BADI Name : PUR_SE_POERPREQUEST_V1_ASYN

Method : INBOUND_PROCESSING

[aromalr · Accepted solution]

Hi, Venkatesh,  I have a similar problem. We are on classic scenario and PO is getting created in backend.When user clicks create puchase order button all document type for PO will be shown in the popup. But the issue is system always takes a default document type even if we chooses any one in the popup for creation of Purchase Order. can we solve this issue with the badi PUR_SE_POERPREQUEST_V1_ASYN  Regards Aromal R

[former_member203412 · Accepted solution]

HI Aromal,

we solved the issue by Implemented the BADI. Please try to implement below and let me if required any further information

Enhancement spot : PUR_SPOT_SE_PURCHASE_ORDER

BADI: PUR_SE_POERPREQUEST_V1_ASYN

Method : INBOUND_PROCESSING

This Badi will triggers before creation of PO in R3.

Regards,

Venkatesh M.

[aromalr · Accepted solution]

thanks for your reply. How to get the document type we have selected at popup(Creation of PO) in this badi.  Aromal R

[former_member203412 · Accepted solution]

In that BADI you will get the Purchase Requisition Number as a input parameter.

Query the table EBAN to get the PR order type by passing Purchase Requisition Number as a input parameter.

Regards,

Venkatesh M.

[aromalr · Accepted solution]

Thank you.but it did not work for us.We completed it with an implicit enhancement spot

Aromal

[Former Member]

Hi experts!!

I new in these foros and I need some help . I have a similar problem to the one proposed

We are using too SRM for Sourcing Process with PI integration..

We need to reach the Following Process:-

1, SC created in SRM  and transfer to ERP as PR

2. Pr created in ERP

2, This PR will be moved to SRM for Sourcing through CPPR

3, Bidding process done  and published in SRM,

4. Bids created in SUS system and sent to SRM using XI

4, Bid  awarded in SRM and transfer as PO or Contract in ERP

To get the first step (transfer PR from ERP to SRM using CPPR) will use the badi ME_REQ_SOURCING-CUST. The process following with bidding process done in SRM and then we will submit  bids in SUS system and we will award the bid winner in SRM. But I haven't any idea how I can transfer

this bid winner to ERP again as a PO or even as a Contract.  ¿the same badi ME_REQ_SOURCING-CUST lets us to do this or we need other thing?, ¿we need configured some special WF as automatic approval to approve the bid winner who release a new event to create PO or Contract in ERP ? and this case which WF we need.

At least you  are able to run end to end this part successfully, so I wonder how can I do the same.

Can anyone help me please?  thanks

Regards,

Mar

[Former Member]

Hi Venkatesh,

You will not be able to create a FO type document unless you make an enhancement in the BADI for the document type.

Sourcing doest understand limit type. let me give you an example.

You have a limit type of Shopping Cart- Move to SOurcing- Rfx(material type) - Response (material type) - If you create a PO from response the type will be Material or NB. In order to make to type B( limit) you will have to write an enhancement in the BADI.

There is this setting in spro Activate/Deactivate Limit Items in Bidding Documents. Activate this and see if it works.

Regards,

Naveen

[Former Member]

Hello,

My suggestion is instead of implementing any BADI, you should debug why this happens?

Double check your config. If config is alright. Debug the ECC PO creation process from RFX.

Thanks,

Sushil.

[laurent_burtaire]

Hello,

what is value populated for DP_PROC_TY attribute in your organizational structure ?

Did you check lowwing OSS notes:

1323983 - Show PO process types if Preceeding doc. is SC for RFx

1640101 - Wrong process type in PO from RFx with Shp as preceeding doc

1669044 - PO process type is incorrect when created from RFX

Regards.

Laurent.

[former_member203412]

Hi Laurent ,

Thanks for the response.

We implemented the 2nd OSS Note, but still the issue was not solved. The other 2 OSS notes is applicable in our scenario.

The PO is created in R/3 System, not in the SRM System . We are using XI for this.

Please let me know if you have any ideas.

Regards,

Venkatesh M

[former_member208675]

Hi,

If you are using XI to transfer PO from SRM to ECC BAdi BBP_CREATE_BE_PO_NEW is not used.

Instead BAdi /SAPSRM/BD_SOA_MAPPING, method MAP_BACKEND_TO_SOA is called.

I hope it helps.

Regards,

[former_member203412]

Hi Vinay,

We implemented the BADI "/SAPSRM/BD_SOA_MAPPING" . This BADI is getting triggered. But we didn't find the method "MAP_BACKEND_TO_SOA" in this BADI. This method is present in the BADI "/SAPSRM/BD_BID_DECOUP_MAP_SOA" .

In our scenario the PO is created in R/3 System, not in the SRM System . We are using XI for this. And while creating the PO in the R3 system, we need to change the PO order type.

Please let us know which is the correct BADI and the correct method and how to use ?

BADI : /SAPSRM/BD_BID_DECOUP_MAP_SOA

Methods :MAP_SOA_TO_BACKEND

MAP_BACKEND_TO_SOA

BADI: /SAPSRM/BD_SOA_MAPPING

Methods :MAP_XI_TO_BACKEND

MAP_BACKEND_TO_XI

Regards,

Venkatesh

[Former Member]

You have to implement the BADI BBP_CREATE_BE_PO_NEW to change the PO document type before PO is sent to ERP system.

You can also refer the below link.

http://wiki.sdn.sap.com/wiki/display/SRM/BBP_CREATE_BE_PO_NEW+-+Create+PO+in+backend

With Regards,

Malay

[former_member203412]

Hi Malay,

Thanks for quick response,

I implemented the BADI BBP_CREATE_BE_PO_NEW , but the BADI was not triggered while creating the purchase order.

The PO is created in R/3 System, not in the SRM System . We are using XI for this.

Please let me know if you have any ideas.

Regards,

Venkatesh M

[Former Member]

Please try in "BBP_SRC_DETERMINE" BADI.

It will work.

With Regards,

Malay