Making Settings for the Procurement of External Requirements 

You have to ensure the following prerequisites or perform the following activities:

System Requirements

You use R/3 Release 3.1I or higher with BBP Plug-In 2004.1 and SAP Note 505030 (Restrictions when integrating external requirements). Furthermore, the plan-driven procurement scenario requires SAP Note 441892 (Integration External Requirements) and all related notes.

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.

For further information, see the Implementation Guide (IMG):

Supplier Relationship Management   ®  SRM Server   ®  Cross-Application Basic Settings  ®  Organizational Management

Remote Connections and ALE Settings

You have defined the following remote connections and ALE settings for the logical system:

·        From Enterprise Buyer to the execution (external) system

·        From the execution (external) system to Enterprise Buyer

Make sure the logon user is the same as the RFC user of the entry channel in Enterprise Buyer.

For further information, see SAP Implementation Guide (IMG):

Supplier Relationship Management  ® SRM Server  à Technical Basic Settings à ALE Settings

Location/Plant

·        You have replicated plants from the execution system. See Making Settings for External Locations and Business Partners.

Further Settings in the Enterprise Buyer System

You have made the following settings in the Enterprise Buyer system:

·        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  ® SRM Server  à Technical Basic Settings à Define Backend Systems.

·        Performed all the Customizing necessary for contracts. See Making Settings for Purchase Contracts.

·        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  ® SRM Server  à Sourcing à Define Sourcing for Product Categories.

·        Defined that the Extended Classic Scenario is active. IMG path: Supplier Relationship Management  ® SRM Server  à Cross-Application Basic Settings  ® Activate Extended Classic Scenario

For further definition of exactly when, under which circumstances the Extended Classic Scenario is active, you can implement the Business Add-In Control Extended Classic Scenario

·        Defined tolerance groups in Customizing: Supplier Relationship Management  ® SRM Server à Cross-Application Basic Settings à Set Tolerance Checks. The tolerance keys PM, PR and PZ are significant for the Order Response.

You have assigned the tolerance group to one or more user groups by defining the attribute TOG for the relevant organizational node.

Further Settings in the R/3 Execution System

You have made the following settings in the R/3 execution system:

·        To set up the RFC communication between R/3 and Enterprise Buyer you have created an RFC destination in R/3 that corresponds to the RFC user of the entry channel in Enterprise Buyer.

·        You have created a user with which you can log on remotely using transaction <SU01>.
The user type should be defined as a “background user” (or “system” user from release 4.6x) and authorizations SAP_ALL and SAP_NEW should be allocated.
To test these users, create them as dialog users initially. Log on to the backend system with the user ID, then if successful, change to background (or system) user. If you have several backend systems, you have to define this user (the same as the RFC user of the entry channel in Enterprise Buyer) in each of these systems.

·        Defined the profiles (in the IMG or view maintenance V-T160PR) that specify the Enterprise Buyer system as the target system to which the external-procurement requirement coverage requests are transferred. You have named the profile and have defined the RFC destination of the Enterprise Buyer target system, transaction SM59. The RFC destination corresponds to the RFC user of the entry channel.
For example, you have set up a profile tk which references to the logical system q4c/client 300.

See path in the Plug-In IMG: Integration with other mySAP.com Components  ®  Supplier Relationship Management  ®  Plan-driven Procurement  ®  Maintain Profiles for External Procurement.

·        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.
For example, you have set up a combination 001/EXT which references to the tk profile.

See path in the Plug-In IMG: Integration with other mySAP.com Components  ®  Supplier Relationship Management  ®  Plan-driven Procurement  ®  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.

See path in the Plug-In IMG: Integration with other mySAP.com Components  ®  Supplier Relationship Management  ®  Business Add-Ins (BAdIs)  ®  Plan-driven Procurement  ®  Define Profiles.

·        You can use table EPRTRANS to check requirements, that are transferred to the purchase order worklist or to the sourcing application.

·        You have periodically scheduled job BBP_EXTREQ_TRANSFER to transfer requirements from the backend system to Enterprise Buyer.

·        You can use transaction SMQ1 to check objects in the transfer queue.

See also:

Making Settings for Purchase Contracts