SAP SRM Training material

My SAP SRM is a purchasing platform that delivers sustainable savings and value generated for world-class supply management. SRM covers the full supply cycle, from strategic sourcing to operational procurement and supplier enablement, leveraging consolidated content and master data. With mySAP SRM, you can collaborate with all suppliers for all purchased goods and services. This means you constantly optimize supplier selection, compress cycle times, and device focused sourcing and procurement strategies.

Step by Step instructions below on how to configure SRM.

1. Introduction

This document contains the set-up / configuration of mySAP SRM  , classic deployment, self-service procurement scenario as used for procurement of indirect material in the EADS TRIO project. The document is intended for process owners and system administrators involved.

1. Technical Basic Settings

2.1.   Create RFC Connection

As the EBP is a separate SAP system beside the SAP R/3 backend system, the EBP has to be connected to the SAP R/3 backend.

2.1.1. Step 1: Create RFC User for connection in EBP

2.1.2. Step 2: Create RFC User for connection in R/3

2.1.3. Step 3: Create RFC connection in EBP

Note: Logon language for connection was intentionally left blank. By doing so, the system takes the logon language of the EBP user for the connection. This is important for displaying system messages from the backend system in the user logon language.

2.1.4. Step 4: Create RFC connection in R/3

2.2.   Create ALE Connection

Some communication between EBP and SAP R/3 is done by ALE. Therefore the ALE connection has to be configured as well.

2.2.1. Step 1: Define logical system in EBP

2.2.2. Step 2: Define logical system in R/3

2.2.3. Step 3: Assign logical system to client in EBP

2.2.4. Step 4 : Create distribution model

2.2.5. Step 5: Generate partner profiles

2.2.6. Step 6: Distribute distribution model

2.2.7. Step 7: Generate partner profiles in R/3

2.3.   Define Backend System

2.3.1. Step 1: Define backend system

Relevant backend systems have to be defined in EBP.

2.3.2. Step 2: Define backend system for product category

Backend system that the documents are posted in, depending on the product category have to be specified.

2.4.   Jobs

As material management documents (purchase orders, goods receipts) are to be created in the backend system, relevant information about the spooler and the update frequency has to be defined.

2.4.1. Step 1: Set parameters for controlling the required jobs

2.4.2. Step 2: Create Job User in EBP

2.4.3. Step 3: Define Jobs in EBP

2.5.   Publish HTML

The EBP is accessed by the web browser using HTML pages. These HTML files have first to be published to the ITS (for this system the internal ITS of the WebAS is used).

2.5.1. Step 1: Maintain required data for publishing

2.5.2. Step 2: Select target for publishing

2.5.3. Step 3: Publish

Modifications on HTML Templates

To cover the requirements of EADS DS several modifications were made to the HTML Templates. Please refer to document TrIO_TDD_EBP 2006-01-23 HTML Spec v1-6.doc for further details.

1. Master Data

3.1.   Catalogs

In the implemented scenarios demands are covered from catalogs. In order to use catalogs, they have to be defined in EBP.

3.1.1. Step 1 : Define Web Service

3.1.2. Step 2: Define call structure for Web Service

1. Cross-Application Basic Settings

4.1.   Roles

Following Roles have been created:

Note:

• The role YTF_EBP_EMPLOYEE is designed for requestor users, who are supposed to create shopping carts.
• The role YTF_EBP_MANAGER is designed for approver users, who are supposed to approve shopping carts.
• In order to enable changes to the shopping cart during approval and to have the workflow react properly, the workflow security settings have to be set to “Medium”
  (Transaction PFCG -> choose role -> maintain -> personalization -> personalization key object = BBP_WFL_SECURITY set to “medium”).

4.2.   Organizational Management

For details on the specification please refer to the attached PowerPoint file:

For details on the realization please refer to the attached Excel sheet:

Notes:

• The responsible purchasing group is determined by the commodity group
• As the attributes “CAT” and “CNT” are maintained on user level, they must be maintained manually after creating new users
• The delivery address is defined on county division level (DS FR) and inherited to business units → users, default address must be flagged for user
• Based on current requirements the only currency set up in the system is Euro. By adding additional currencies to the respective level (country node) in the organizational model, every currency can be handled by the EBP system.

4.3.   Number Ranges

Number ranges have to defined for the documents created by EBP (shopping cart, purchase order). The po number range is assigned to a transaction type (= document type in backend).

4.3.1. Step 1: Set the number range

4.3.2. Step 2: Use the number range

4.3.3. Step 3: Define transaction types

4.4.   Workflow

For workflow related customizing and development please refer to TrIO_TDD_EBP Workflow – Technical & Customizing_v3.doc

4.5.   Tax

The tax calculation like all financial processes will take place in the backend.

4.6.   Account Assignment

Accounting data is suggested by EBP. Therefore several settings have to be made.

4.6.1. Step 1: Define account assignment category

Based on requirements the only account assignment type set up in the system is cost center. Every SAP account assignment category (i.e. assets, wbs elements, …) can be added later on if required.

4.6.2. Step 2: Define automatic g/l account determination according to product category and account assignment category

For details regarding the g/l account determination please refer to the attached Excel sheet.

4.7.   Objects in Backend System

The creation of follow on documents is defined per purchasing group

4.8.   Application Monitors

In order to have application monitors available for administration usage, the monitors have to be activated.

4.9.   Business Partner Number Range

Vendors are uploaded from the backend system. In order to enable the same vendor id like in the backend system, the number ranges have to be aligned.

4.9.1. Step 1: Define number range

Set number range F1 to comprise backend number ranges F1 and F2

4.9.2. Step 2: Define grouping

1. Middleware Settings

Certain master data is uploaded from the backend system using the CRM middleware solution. Therefore the middleware has to be configured to enable the upload.

5.1.   R/3 Backend

Check SAP note 720819

Check the following tables / entries

5.2.   SRM

5.2.1. Maintain Middleware Settings

Check SAP note 720819

Check the following tables / entries

5.2.2. Maintain Industry Settings

5.2.3. Maintain Middleware Site

5.2.4. Set Middleware Settings

5.2.5. Upload Data From Backend

1. Appendix I: Multi Backend Capabilities of EBP

The mySAP SRM EBP solution is basically multi backend capable according to SAP. Nevertheless there are some limiting factors in the standard solution, which can easily overcome by standard enhancements using BADIs.

Based on the requirements for the EBP implementation at EADS DCS France the current EBP implementation is designed for France but can be easily enhanced for further countries.

• Additional organizations can be easily added to the organizational model as it is already designed to encapsulate organization / country specific settings.
• Additional languages will require additional maintenance of customer specific system messages in the respective language
• Additional currencies can easily added in the organizational model
• Additional backend systems can easily be connected to the EBP system on the standard way

However enhancements have to be checked before enhancing the EBP and eventually will have to be adapted. Known limitations from enhancements are:

• Approver determination in approval workflow

1. Appendix II: Remarks On system copy

7.1.   Copy of EBP

Some special factors have to be taken into account when copying EBP. Therefore the copy of an EBP system should be carefully considered.

Please refer to the Excel task list attached. In addition please refer to the official SAP guide how to copy and transport EBP systems.

7.2.   Copy of R/3

Connection between R/3 and EBP has to be checked and eventually corrected

• RFC-connection (see above chapter 2.1)
• ALE-connection (see above chapter 2.2)

Special attentions has to be given to the number range. When copying the backend on a periodic basis without the EBP, the number range for purchase documents will deviate between the two systems and will have to be remaintained according to chapter 4.3.