How can I transfer PR in ECC to SRM?

[Former Member]

Hi Experts,

How can I transfer PR in ECC to SRM, no matter the PR were created manually or generated automatically by MRP??

Thanks a lot!!!!!!

[Former Member · Accepted solution]

Hi,

You can use BAPI'S to create a shopping carts in SRM for the PR's.

BBP_PD_SC_CREATE

BBP_PD_SC_CREATE_EXTERNAL

Thanks

prasad.s

[Former Member · Accepted solution]

Hi,

I do not need Shopping Cart for PRs.

I need sourcing for requirements from ECC PR. Bid for this reuqirements, then create contract.

Thanks very much!!!!!!

[Former Member · Accepted solution]

Hi,

I do not need Shopping Cart for PRs.

I need sourcing for requirements from ECC PR. Bid for this reuqirements, then create contract.

From the PR data shopping cart will be created, in SRM there is no PR document Creation.

Using the BAPI's Shopping cart's will be created based onthe backend PR's.

there SC's placed in Sourcing if the sourcing custamization done..

SPRO> SRM> SRM server--> Sourcing --> define souring for product categories

Thanks

prasad.s

[Former Member · Accepted solution]

Hi prasad.s,

I understand, there is no PR creation in SRM. And BAPI can create Shopping cart. But using BAPI need additional coding.

As I know for Plan Driven Procurement we can transfer PR in ECC to SRM sourcing cockpit, and assign sourcing for this requirements.

So How can I make the PR requirements in ECC appear in sourcing cockpit.

Thanks very much!!!!!!

[Former Member · Accepted solution]

Hi,

I understand, there is no PR creation in SRM. And BAPI can create Shopping cart. But using BAPI need additional coding.

As I know for Plan Driven Procurement we can transfer PR in ECC to SRM sourcing cockpit, and assign sourcing for this requirements.

So How can I make the PR requirements in ECC appear in sourcing cockpit.

One way to transfer PR's Is Using Plan driven procurement.. Hope this process you know already.

Another way was using BAPI's create shopping carts for PR's and assign sourcing.. as you said additionla coding required , need to technical guy help to implement bapi.

I think there is no other way...

Thanks

prasad.s

[former_member183819 · Accepted solution]

Hi Jock,

http://help.sap.com/saphelp_srm40/helpdata/EN/38/39d03bcf36d137e10000000a114084/frameset.htm

 Identify the product category which is going to use in Sourcing Cockpit.

 REQREQ Transfer jobs needs to be scheduled to transfer Purchase request to Sourcing cockpit.

 The Purchase request needs to setup profile in the EBAN table.

 You can use table EPRTRANS to check requirements, that are transferred to the purchase order work list or to the sourcing application.

 u2022 You have periodically scheduled job BBP_EXTREQ_TRANSFER to transfer

 requirements from the backend system to Enterprise Buyer.

 RFC communication needs to be set up for communicating between r/3 and EBP and this RFC user must be assigned to your entry channel in EBP.

 Define profile V_T160PR .this specifies the target system as EBP and where External Procurement coverage request is needs to be transferred.

 You have specified combinations of product category and purchasing group to identify which purchase requisition will belong to which profile.

 Requirements that are to be procured externally (that is, not by the execution system) are identified using two attributes: Purchasing group and material group .

 You have defined the combinations of purchasing group and material group that are to be procured via Enterprise Buyer in the maintenance view V_T160EX. Furthermore,

 you have entered the profile name (specified in the previous step ) which defines the target system for each combination.

 See path in the Plug-In IMG: Integration with other mySAP.com Components u2192 Supplier Relationship Management u2192 Plan-driven Procurement u2192 Control External Procurement.

 (Optional setting) If you need more flexible criteria to determine which profile the system is to use for which purchase requisition, you have set up the customer exit BBPK0001.

EBP Settings

 Replicated material groups, material types as product categories, materials as products, and vendors to the Enterprise Buyer system.

Defined the execution (external) system as a backend system. IMG path: Supplier

Relationship Management u2192 SRM Server 􀃆 Technical Basic Settings 􀃆 Define Backend Systems.

 Defined that the product categories of external requirements are transferred to the application Sourcing. (You can specify whether requirements with these product categories are always transferred to the Sourcing application, are only transferred when a source of supply has not yet been assigned, or are never transferred to the Sourcing application). IMG path: Supplier Relationship Management u2192 SRM Server 􀃆 Sourcing 􀃆 Define Sourcing for Product Categories.

We need to pull the plant from r/3 system and mapped in extended attributes.

Settings for the Organizational Structure in the Enterprise Buyer System

You have defined an entry channel for the execution (external) system in the organizational plan. Via the entry channel the Enterprise Buyer system receives the external requirements. This entry channel must have at least one remote user. The entry channel must be maintained below the company level.

You have created an SAP Enterprise Buyer remote user that is linked to the organizational unit for the entry channel.

The user must be an Enterprise Buyer (BBP) user, that is, a user with business partner and central person. A standard R/3 user is not sufficient. You should not assign a particular role to the user but should assign a profile, in the transaction PFCG, that allows the user to log on to the system via RFC.

You must have defined a local purchasing group as responsible for this entry channel. You do this by entering the organizational unit of the entry channel (purchasing group responsible) on the tab card Function of the purchasing group.

You have defined the attribute DP_PROC_TY for this purchasing group.

You have defined the following attributes for the purchasing organization of the responsible purchasing group:

BUK (company code in the execution (external) system). The value should be defined as <logical system of the execution system>/<company code>, for example, QW8CLNT250/1000.

BSA (document type in the execution (external) system). The value should be defined as <logical system of the execution system>/<document type>, for example, A3CCLNT300/ECQ3.

You have defined the attribute CUR (local currency) at the entry channel.

[former_member196437 · Accepted solution]

Hey,

You need to follow the Direct Procurement configurations and Plant driven procurement configuration.

As Muthu said,

check Sourcing for product categories,

RFC Entry channel,

Responsible purchasing group,

V_T160EX and V_T160PR Table entries,

Std Report in R/3, BBP_EXT_REQ_TRANSFER,

finally maintain attributes of Org structure.

Thanks

Sai