Configuring Plan Driven Procurement between ERP and SRM

Applies to:
SAP SRM 7.0, SRM 5.0, ECC5.0, ECC6.0. For more information, visit the Supplier Relationship Management homepage

Summary
This document details the configurations required to set up Plan Driven Procurement Scenario between SRM and SAP ERP System. Author: Virender Singh, CPIM CSCP

Company: Intelligroup Inc. Created on: 8 November 2010

Author Bio
Virender Singh is a SAP SRM 7.0 Certified Professional consultant with more than 9 years of SAP Consulting Experience working with Leading IT Organization serving global clients. He has extensive experience of a number of implementations, upgrades, rollouts and run/maintain lifecycles of SAP Solutions running on SAP SRM, ECC, SNC, SAP Solution Manager. As a professional member of APICS and APICS Certified CPIM CSCP associate he has adequate knowledge and experience of modern day Supply Chain and Supplier Relationship processes. Currently in Intelligroup Inc., he is involved in providing innovative solutions to Global clients on SAP SRM and SCM.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1

Configuring Plan Driven Procurement between ERP and SRM

Table of Contents
Requirements ..................................................................................................................................................... 3 Plan Driven Procurement Scenario .................................................................................................................... 3 Configurations in SRM System ........................................................................................................................... 3 Create a Transaction Type for Shopping Carts .............................................................................................. 3 Activate Extended Classic Scenario ............................................................................................................... 3 Create an Entry Channel in the Org Structure for Plan Driven Procurement ................................................. 3 Setup the RFC User in the above Channel Organization ............................................................................... 3 Create a Local Purchasing Group in the Org Structure .................................................................................. 4 Complete Sourcing Configuration or BADI for Sourcing, if Required ............................................................. 4 Configurations in ERP System ........................................................................................................................... 4 Create a RFC Connection from ERP to SRM ................................................................................................. 4 Maintain the Configurations in V_T160PR Table ............................................................................................ 4 Maintain the Configurations in V_T160EX Table ............................................................................................ 4 Schedule Report BBP_EXTREQ_TRANSFER ............................................................................................... 5 BBP_BADI_EXTREQ_OUT ............................................................................................................................ 5 Manual Handling of PR Transfer to SRM ........................................................................................................ 5 Related Content .................................................................................................................................................. 6 Disclaimer and Liability Notice ............................................................................................................................ 7

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 2

Configuring Plan Driven Procurement between ERP and SRM

Requirements
An enterprise runs Materials Requirement Planning in ERP System and generates Purchase Requisitions as a part of Planning run, Plant Maintenance and/or Project Systems. The current landscape also has a SRM system which is connected to the ECC System. Client wants the Procurement Platform and Sourcing capabilities of SRM be used for optimizing the plan driven procurement. This document describes the technical configurations of setting up Plan Driven Procurement between ECC and SRM.

Plan Driven Procurement Scenario

Plan Driven Procurement with Plant Maintenance o o This scenario processes requirements that have been generated in systems other than SAP SRM. This works in Extended Classic Scenario.

Plan Driven Procurement with Supplier Integration o This scenario is used to process procurement of Direct Materials from ERP system where Supplier is also collaborating with the company using SUS. In this case ERP(MM) system is integrated with SRM-SUS system for Collaboration functions. Requisitions are not pushed to SRM in this case. Procurement process takes place within ERP (MM) System only.

Configurations in SRM System

Create a Transaction Type for Shopping Carts Create a Shopping cart Transaction Type for SCs created by Plan Driven Procurement. This is required if you want a different transaction type for the Shopping Carts created by Purchase Requisitions from ERP System. This is an optional Step. Activate Extended Classic Scenario Complete the configurations required to activate Extended Classic Scenario in SRM system. You may also use BADI for Handling Extended Classic Scenario for this purpose. Create an Entry Channel in the Org Structure for Plan Driven Procurement Entry channel is required for processing the external requirements in SRM System. This Entry channel is created in the Organization Structure anywhere under the root org unit. This Org unit inherits the attributes from the higher level organizational units. Setup the RFC User in the above Channel Organization When a Requisition is pushed by ERP System into SRM System, RFC User which processes this data in SRM is used as Shopping Cart Creator. SRM User is complete only and only if the user has a SU01 id and is integrated in the organizational structure. Due to this reason this RFC user need to be integrated into the org structure under the Organization for Entry Channel.
Note: This RFC User must have appropriate role to create a Shopping Cart in SRM System.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 3

Configuring Plan Driven Procurement between ERP and SRM

Create a Local Purchasing Group in the Org Structure As Purchasing Group is used to derive the product responsibility and organizational responsibility while application documents are processed in SRM. Create a local purchasing group in the organization structure and assign the above Entry Channel Organizational Unit in the organizational responsibilities and respective product category(Material group in ERP) in the product responsibilities of this purchasing group. Complete Sourcing Configuration or BADI for Sourcing, if Required Complete the necessary configurations required for SRM System to generate an item in Work List.

Configurations in ERP System

Create a RFC Connection from ERP to SRM Create a RFC Connection from ERP to SRM System with a RFC User. This RFC user is the one which is set up in the Entry Channel of the SRM System. Maintain the Configurations in V_T160PR Table Create a profile for the SRM System in table V_T160PR. One profile is created for each SRM System connected to a ERP System.

Maintain the Configurations in V_T160EX Table In order for the Purchase Requisitions to get transferred to SRM System, assign the combination of Material Group and Purchasing Group to this profile in this table. This configuration ensures that whenever a purchase requisition is created with this material group and purchase group, system identifies the purchase requisition as the PR eligible to go to SRM System and creates an entry of this PR in EPRTRANS Table. This profile is updated in the EBAN record of the purchase requisition. Any requisition with profile updated in it can not be modified in ERP System after it is created.

Note: Manual Indicator in this table is used if there is a requirement to process the selective PRs manually in ERP System by the respective teams.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 4

Configuring Plan Driven Procurement between ERP and SRM

Schedule Report BBP_EXTREQ_TRANSFER This report is scheduled in background to pick up requisitions from EPRTRANS table and push it to SRM. Once a Requisition is pushed to SRM , the entry from EPRTRANS will be removed. BBP_BADI_EXTREQ_OUT This BADI in ERP System (R/3 4.6B Onwards), is used to edit the standard transfer before PRs are pushed to SRM. This BAdi is called before the transfer is made to the external system using report BBP_EXTREQ_TRANSFER. Check the documentation of this BADI for more information about the same. Manual Handling of PR Transfer to SRM If for some reasons there is a requirement to send only selective PRs from ERP to SRM System, then it is required to set the Manual Indicator in the V_T160EX Table shown below:

This indicator will ensure that the PR satisfying the criteria in V_T160EX is not updated in EPRTRANS Table immediately on Saving or Approval. Rather than that the report RM06BZ10 need to be used for selecting the respective PRs having Manual Processing indicator. This report will then update these entries in EPRTRANS Table from where BBP_EXTREQ_TRANSFER report will pick the entries and push it to SRM

Please refer to the OSS Note 648074 for more details around this option.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 5

Configuring Plan Driven Procurement between ERP and SRM

Related Content
Extended transfer of purchase requisitions to SRM The Social Network for SAP Professionals For more information, visit the Supplier Relationship Management homepage

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 6

Configuring Plan Driven Procurement between ERP and SRM

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 7