Вы находитесь на странице: 1из 38

SAP Supplier Relationship Management

PDF download from SAP Help Portal:


http://help.sap.com/saphelp_srm703/helpdata/en/74/344c430fab4d0bbc30996d56cc293a/frameset.htm

Created on February 19, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC Page 1 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Table of content
1 SAP Supplier Relationship Management
1.1 What's New in SAP Supplier Relationship Management
1.1.1 What's New in SAP Enhancement Package 3 for SRM 7.0
1.1.1.1 Support Package Stack 05
1.1.1.1.1 SRM, Continuous Innovations 3
1.1.1.1.1.1 Inconsistent Business Partner Handling
1.1.1.1.2 Assign Supplier Button
1.1.1.1.3 Assign Supplier or Currency to selected items in Shopping Cart
1.1.1.1.4 Text Format for Long Text Boxes
1.1.1.1.5 Check for Open Purchase Orders before Contract Completion
1.1.1.1.6 Additional Status for RFx
1.1.1.2 Support Package Stack 07
1.1.1.2.1 SRM, Large Document Handling
1.1.1.2.1.1 Large Document Handling for Contracts
1.1.1.2.1.2 Large Document Handling for RFx
1.1.1.2.2 Mass Changes to Contracts
1.1.1.2.3 Mass Copy of Contracts
1.1.1.2.4 Defer Sourcing
1.1.1.2.5 Rejection Reason in Sourcing Application
1.1.1.2.6 Follow-On Documents in Shopping Cart
1.1.1.2.7 Contract Release Value Update
1.2 Business Functions and Customizing Switches
1.3 Overview
1.4 Master Data
1.4.1 Product Categories
1.4.2 Product Category Hierarchies and Supplier Hierarchies
1.4.3 Business Partners
1.4.3.1 Locking of Business Partners
1.4.3.2 Business Partner Change Monitor
1.4.4 User and Employee Data
1.4.5 Addresses
1.4.6 Revision Level Display
1.5 Functions
1.5.1 Global Functions
1.5.2 Administrative Functions
1.5.3 Central Contract Management
1.5.4 Shopping Cart
1.5.5 Purchase Orders
1.5.6 Sourcing
1.5.7 Invoices and Credit Memos
1.5.8 Confirmations
1.5.9 Business Workflow
1.5.9.1 Process-Controlled Workflows
1.5.9.2 Application-Controlled Workflows
1.5.10 Supplier Qualification
1.5.11 Supplier Self-Services
1.5.12 Analytics
1.5.13 Integration with Collaboration Projects (cProjects)
1.5.14 Procurement Card Payment Process
1.5.15 Archiving
1.5.16 Country-Specific Functions
1.6 SRM-MDM Catalog
1.6.1 Catalog Content Management
1.6.2 SRM-MDM Catalog for Product Procurement
1.6.3 SRM-MDM Catalog: Service Procurement
1.7 Business Packages
1.7.1 Business Package for SAP Supplier Relationship Management
1.7.2 Business Package for Supplier Collaboration 4.0
1.8 Procurement for Public Sector (PPS)

PUBLIC Page 2 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
1 SAP Supplier Relationship Management

Product Information

Product SAP Supplier Relationship Management

Release 7.0

SAP Enhancement Package 3, SP 07 for SAP SRM 7.0

Based On SAP enhancement package 4 for SAP NetWeaver 7.0 Support Package Stack 06

BI Content Release BI Content 7.47

Documentation Published January,2015

Use
SAP Supplier Relationship Management (SAP SRM) provides you with innovative methods to coordinate your business processes with your key suppliers and
make them more effective. SAP SRM enables you to optimize your procurement strategy, to work more effectively with your supplier pool, and thus to gain long-
term benefits from all your supplier relationships.
With SAP SRM you can examine and forecast purchasing behavior, shorten procurement cycles, and work with your partners in real time. This allows you to
develop long-term relationships with all those suppliers that have proven themselves to be reliable partners.
The efficient processes in SAP SRM enable you to cut down your procurement expenses and to work more intensively with more suppliers than ever before.
SAP SRM is part of SAP Business Suite.
The SAP SRM documentation offers a comprehensive description of the functional scope of SAP SRM, and highlights the relationship between the application
and the underlying technologies.

More Information

For more information about SAP NetWeaver, see the SAP NetWeaver Getting Started Guide at http://help.sap.com SAP NetWeaver SAP
NetWeaver Library Getting Started- Using SAP Software
For more information about the implementation of an SAP SRM solution and associated business scenarios, see the SAP SRM Master Guide (

http://service.sap.com/srm-inst SAP SRM Server 7.13 )


For more information about SAP SRM configuration information, see SAP Solution Manager

1.1 What's New in SAP Supplier Relationship Management

1.1.1 What's New in SAP Enhancement Package 3 for SRM 7.0

1.1.1.1 Support Package Stack 05

1.1.1.1.1 SRM, Continuous Innovations 3

With this business function you can enhance certain features of shopping cart in SAP Supplier Relationship Management (SAP SRM) functions, and implement
new functions. Inconsistent Business Partner Handling is the new feature available with this business function.

More Information
For more information about the business function, see SRM, Continuous Innovations 3.

Technical Details

Technical Name of Business Function SRM_CONT_IMPR_3

Available as of SAP Enhancement Package 3 (SP05) for SAP SRM 7.0

For more information about the features provided with this business function, see the following release notes:
Inconsistent Business Partner Handling

Effects on Customizing

PUBLIC Page 3 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
To use SRM, Continuous Innovations 3, you must first activate the business function in Customizing for SAP Supplier Relationship Management under SRM
Server --> Business Function

1.1.1.1.1.1 Inconsistent Business Partner Handling

With this feature you can as an SAP SRM administrator edit or display any document in Supplier Relationship Management (SAP SRM) that is assigned to a
business partner who is terminated or whose role has become inconsistent in the SAP SRM organizational structure. For example, it is possible for you to confirm
the delivery of goods if the shopping cart was ordered by a business partner whose role is now inconsistent in the SAP SRM organizational structure.
You can transfer the ownership of an SRM document from one business partner to another business partner. This is applicable for all the business partner roles
such as requester, goods recipient, invoice recipient, and employee responsible (in case of contracts).
You can also track the changes once the business partner role is transferred from one employee to another employee. The changes that you can track are as
follows:
Changed by
Changed On
Old Business Partner
New Business Partner
Document Updated
Business Object Type
Document Number
Note that if any open workflow item in the document is displayed, you cannot transfer the document ownership until the workflow item is closed.

Technical Details

Technical Name of Product Feature SRM_CONT_IMPR_PF14

Product Feature Is New

Country Dependency Valid for all countries

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-ADM-XBP

Available as of SAP Enhancement Package3 (SP05) for SAP SRM 7.0

Required Business Functions SRM, Continuous Innovations 3

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Serve Continuous
Improvement Activate/Deactivate Inconsistent Business Partner Handling

1.1.1.1.2 Assign Supplier Button

This feature enables a shopping cart user to assign the supplier after entering the value in the Supplier field for any shopping cart item on the Source of
Supply tab page.
Thus, it reduces the additional effort of choosing the Assign Supplier button after entering the value in the Supplier field.
Note that the Assign Supplier button is not displayed once the switch is activated.

Technical Details

Technical Name of Product Feature SRM_CONT_IMPR_PF12

Product Feature Is New

Country Dependency Valid for all country

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-SHP

Available as of SAP Enhancement Package 3 (SP05) for SAP SRM 7.0

Required Business Functions SRM, Continuous Innovations 2

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Continuous
Improvement Activate/Deactivate Assign Supplier Button

1.1.1.1.3 Assign Supplier or Currency to selected items in

PUBLIC Page 4 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
1.1.1.1.3 Assign Supplier or Currency to selected items in
Shopping Cart

This feature enables an operational purchaser to select multiple items in a shopping cart and assign a mutual supplier and currency or both for all the selected
items at once. Thus, it reduces the effort of assigning a supplier or currency for each item individually.
Note that this feature is available for shopping carts with any status in edit mode.

Technical Details

Technical Name of Product Feature SRM_CONT_IMPR_PF13

Product Feature Is New

Country Dependency Valid for all countries

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-SHP

Available as of SAP Enhancement Package 3 (SP05) for SAP SRM 7.0

Required Business Functions SRM, Continuous Innovations 2

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Continuous
Improvement Ass. Supp. or Cur. to Selected items in SC

1.1.1.1.4 Text Format for Long Text Boxes

This feature enables you to format the texts you enter in the long text boxes.
With the formatting options, you can emphasize key points and enhance readability as follows:
Add three types of header style
Use alphabetical and non-alphabetical lists
Indent texts to the right or the left of the page
Bold or italicize the text
The enhanced screens with long text boxes for the business objects are as follows:
Header approval Note under Header, Item , and Approval tab page
All the notes under Notes and Attachment tab page
Internal Note text box in purchase order (PO) and Header Approval Note text box in Shopping Cart (SC) are enhanced. Note to Supplier text box in PO and
SC is also enhanced.

Technical Details

Technical Name of Product Feature SRM_CONT_IMPR_PF10

Product Feature Is New

Country Dependency Valid for all countries

Software Component Version SRM-EBP-FW

Application Component SRM_SERVER 713

Available as of SAP Enhancement Package 3 (SP05) for SAP SRM 7.0

Required Business Functions SRM, Continuous Innovations

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic
Settings Activate/Deactivate Text Format for Long Text Boxes

Note
If you have configured SAP Supplier Self-Services in a separate system, you need to define the customizing settings for this function again in that system.

1.1.1.1.5 Check for Open Purchase Orders before Contract


Completion

PUBLIC Page 5 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
This feature enables you to prevent the completion of a central contract if there is any open purchase order (PO) (both classic and extended classic case) against
the central contract.
Previously, the completion of contracts was possible without checking for open purchase orders that were assigned to the contract.
If a contract is in complete status, it is not possible to close the POs that are associated with it.

Technical Details

Technical Name of Product Feature SRM_CONT_IMPR_PF11

Product Feature Is New

Country Dependency Valid for all countries

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-CON

Available as of SAP Enhancement Package 3 (SP05) for SAP SRM 7.0

Required Business Functions SRM, Continuous Innovations

Additional Details

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic
Settings- Service Procurement Activate/Deactivate Check for Open Purchase Orders before Contract Compl.

1.1.1.1.6 Additional Status for RFx

This feature allows the system to set a new status, Ended, for RFxs. The new status, Ended indicates that the bidding period of an RFx is ended.
Previously, when you published an RFx, it was not possible to know if the bidding period has ended, even if the submission deadline was in the past. In the
purchaser's view, the RFx was in Published status, even after the bidding period ended.
Thus, the new status, Ended improves the transparency in the bidding process.

Technical Details

Technical Name of Product Feature SRM_CONT_IMPR_PF09

Product Feature Is New

Country Dependency Valid for all countries

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-BID

Available as of SAP Enhancement Package 3 (SP05) for SAP SRM 7.0

Required Business Functions SRM, Continuous Innovations 2

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server RFx
Activate/Deactivate Additional Status after Publishing RFx

Note
If you have configured SAP Supplier Self-Services in a separate system, you need to define the customizing settings for this function again in that system.

1.1.1.2 Support Package Stack 07

1.1.1.2.1 SRM, Large Document Handling

With this business function you can use the large document handling framework of SAP Supplier Relationship Management. The new features available with this
business function are as follows:
Large Document Handling for Central Contracts
Large Document Handling for RFx

PUBLIC Page 6 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
More Information
For more information about the business function, see SRM, Large Document Handling.

Technical Details

Technical Name of Business Function SRM_LDH_3

Available as of New
SAP Enhancement Package 3 (SP07) for SAP SRM 7.0

For more information about the features provided with this business function, see Large Document Handling for Contracts and Large Document Handling for RFx.

Effects on Customizing
To use SRM, Large Document Handling, you must first activate the business function in Customizing for SAP Supplier Relationship Management under SRM
Server --> Business Function

1.1.1.2.1.1 Large Document Handling for Contracts

This feature enables a purchaser to work on a definite set of line items of a contract with numerous line items.

Technical Details

Technical Name of Product Feature SRM_LDH_3_PF1

Product Feature Is New

Country Dependency Valid for all country

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-CONT

Available as of SAP Enhancement Package 3 (SP07) for SAP SRM 7.0

Required Business Functions SRM, Large Document Handling

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic
Settings Large Document Handling Activate/Deactivate Large Document Handling for Contracts.

1.1.1.2.1.2 Large Document Handling for RFx

This feature enables a purchaser to work on a definite set of line items of an RFx with numerous line items.

Technical Details

Technical Name of Product Feature SRM_LDH_PF2


SRM_CONT_IMPR_PF

Product Feature Is New


New

Country Dependency Valid for all country

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-BID

Available as of SAP Enhancement Package 3 (SP07) for SAP SRM 7.0

Required Business Functions SRM, Large Document Handling

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic
Settings Large Document Handling Activate/Deactivate Large Document Handling for RFx.

1.1.1.2.2 Mass Changes to Contracts


PUBLIC Page 7 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
1.1.1.2.2 Mass Changes to Contracts

This feature enables the purchaser to select multiple contracts, enter data that is common across the contracts, and set the contracts to Saved status. Later,
depending on the requirement, the purchaser can update the individual contract with specific data before publishing.

Technical Details

Technical Name of Product Feature SRM_CONT_IMPR_3_PF3

Product Feature Is New

Country Dependency Valid for all country

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-CON

Available as of SAP Enhancement Package 3 (SP07) for SAP SRM 7.0

Required Business Functions SRM, Continuous Innovations 3

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Continuous
Improvement Activate/Deactivate Mass Changes to Contracts.

1.1.1.2.3 Mass Copy of Contracts

The purchaser can copy multiple contracts from personal object worklist (POWL) at once. A background job runs for the creation of copied contracts. When the
selected contracts are copied, the purchaser gets an e-mail notification regarding the successful creation of copied contracts
. In the action log, you can find the following information:
Errors encountered while copying contracts
Warning message to maintain e-mail id for the business partner if it is missing
Message for successfully created contracts

Technical Details

Technical Name of Product Feature SRM_CONT_IMPR_3_PF2

Product Feature Is New

Country Dependency Valid for all country

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-CON

Available as of SAP Enhancement Package 3 (SP07) for SAP SRM 7.0

Required Business Functions SRM, Continuous Innovations 3

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Continuous
Improvement Activate/Deactivate Mass Copy of Contracts.

1.1.1.2.4 Defer Sourcing

This feature enables you to hide the requisitions or shopping cart items in the sourcing application for a specified time frame until you intend to carry out a sourcing
process for them. The selected items are available again in the search screen for sourcing after the time interval expires.

Technical Details

Technical Name of Product Feature SRM_CONT_IMPR_3_PF1

Product Feature Is New

Country Dependency Valid for all country

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-SOCO

PUBLIC Page 8 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Available as of SAP Enhancement Package 3 (SP07) for SAP SRM 7.0

Required Business Functions SRM, Continuous Innovations 3

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Sourcing
Activate/Deactivate Defer Sourcing.

1.1.1.2.5 Rejection Reason in Sourcing Application

This feature enables the purchaser to enter the reason for rejecting an item or items of a shopping cart or a purchase requisition in the sourcing cockpit.

Note
The ID and the name of the purchaser, who rejects the item or items, as well as the time when the purchaser rejects the item or items, get captured in the
note for rejection reason by default

Technical Details

Technical Name of Product Feature SRM_CONT_IMPR_2_PF1

Product Feature Is New

Country Dependency Valid for all country

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-SOC

Available as of SAP Enhancement Package 3 (SP07) for SAP SRM 7.0

Required Business Functions SRM, Continuous Innovations 2

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Sourcing
Activate/Deactivate SOCO Rejection Reason..

1.1.1.2.6 Follow-On Documents in Shopping Cart

This feature enables you to activate the function that restricts the follow-on documents applicable for items in a shopping cart that are relevant for sourcing. This
feature allows a purchaser with specific authorization to assign the follow-on documents applicable for items in a shopping cart. These follow-on documents appear
against the items in the Carry Out Sourcing screen as applicable. The operational purchaser can then view, select, and assign only those follow-on documents
as applicable for an item in the shopping cart. This enables faster purchasing of items relevant for sourcing.

Note
This feature is applicable only to purchase order, contract, auction, and RFx follow-on document types. This feature is not applicable for items added from
catalog and for existing shopping cart items.

Technical Details

Technical Name of Product Feature SRM_CONT_IMPR_2_PF2

Product Feature Is New

Country Dependency Valid for all countries

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-SHP

Available as of SAP Enhancement Package 3 (SP07) for SAP SRM 7.0

Required Business Functions SRM, Continuous Innovations 3

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Continuous
Improvement Activate/Deactivate Follow-On Documents in Shopping Cart.
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Cross Application Basic
Settings Define Settings for Creation of Follow-On Documents in Shopping Cart.

PUBLIC Page 9 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
1.1.1.2.7 Contract Release Value Update

This feature enables you to activate the function that updates the release value of a hierarchical service item under a central contract hierarchy.
When you assign a supplier for a hierarchical service item under a contract hierarchy, the system allows you to select a subline item as a reference. The system
also updates the release value for the selected hierarchical service item and updates the aggregated release value for the entire central contract hierarchy.

Technical Details

Technical Name of Product Feature SRM_CONT_IMPR_1_PF1

Product Feature Is New

Country Dependency Valid for all countries

Software Component Version SRM_SERVER 713

Application Component SRM-EBP-CON

Available as of SAP Enhancement Package 3 (SP07) for SAP SRM 7.0

Required Business Functions SRM, Continuous Innovations

Effects on Customizing
You define the Customizing settings for this function in Customizing for SAP Supplier Relationship Management under SRM Server Sourcing
Activate/Deactivate Release Value for a Hierarchical Service Item.

1.2 Business Functions and Customizing Switches

You can selectively implement new functions or enhance existing ones by activating business functions.
SAP Supplier Relationship Management (SAP SRM) favors a two-step activation process and a flexible approach for the implementation of new functions and the
enhancement of existing functions. This approach uses business functions and Customizing switches. You use business functions to display Customizing
activities and Customizing switches. Once the Customizing switches are visible, you use them to activate new fields or execute new code.

Business Functions
For general information about business functions, see Introduction: Enhancement Packages and Business Functions
For information about individual business functions, see the related documentation that is linked from the Switch Framework: Change Business Function Status
screen. The documentation describes the business value, possible limitations, and dependencies.

Activation of Business Functions


When you activate business functions, you activate Switch Framework switches (SFW switches). SFW switches directly control whether new Customizing
activities and Customizing switches are visible.
You can activate SAP SRM business functions in Customizing for SAP Supplier Relationship Management under SRM Server Activate Business
Functions .

Deactivation of Business Functions


In SAP SRM, you can deactivate a business function if the following applies:
The business function only activates Customizing switches and does not directly activate any code or fields.
The Customizing switches corresponding to the business functions can be deactivated.
For more information, see the documentation of the individual business functions.
To deactivate a business function, perform the following steps:
1. Check whether there are limitations at Customizing switch level. You can find this information in the business function description and in the documentation
of the Customizing switch in Customizing for SAP Supplier Relationship Management. If there are no limitations, deactivate the Customizing switch or
switches in Customizing for SAP Supplier Relationship Management.
2. Run transaction Switch Framework Customizing (SFW5), select the business function, and deselect the Revertible checkbox. To do this, you need
special authorizations.
3. Save and activate your changes.

Customizing Switches
Customizing switches are Customizing activities that allow you to execute new code and display the related user interface elements, such as new fields, buttons,
or columns. Customizing switches affect the user interface and the business logic as follows:
They call soft switch methods in the code, so that some sections of the code are only executed if the Customizing switch is active.
The Customizing switch framework provides table columns where Customizing switches can be entered. This has the following effect:
If the Customizing switch is active, the table entries assigned to the Customizing switch are taken into account at runtime.
If the Customizing switch is inactive, the table entries assigned to the Customizing switch are ignored at runtime.

Activation of Customizing Switches

PUBLIC Page 10 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
You can find a list of all Customizing switches in Customizing for SAP Supplier Relationship Management under SRM Server Display Status of Customizing
Switches . From here, you can also navigate to the Customizing activities where you activate or deactivate the Customizing switches. The documentation
available with the Customizing activities provides further information, such as the initial status and the revertibility of the Customizing switch.

Deactivation of Customizing Switches


Most of the Customizing switches are revertible and can be deactivated. A Customizing switch is revertible if the following applies:
The function switched on using the Customizing switch only affects the business process or user interface, but not the data that is written to the database.
The function switched on using the Customizing switch does affect data written to the database, but you have not yet created a document with this function,
so no data has yet been written to the database.
To find out whether a Customizing switch is revertible, see the documentation of the Customizing activity that you use to activate or deactivate the Customizing
switch.

Note
Some Customizing switches are active by default. You only have to deactivate them if you do not want to use the related function. Deactivating a Customizing
switch can be useful, for example, to ensure that unused fields are not displayed unnecessarily. It also ensures that code sections are not executed
unnecessarily, which can have a positive effect on system performance.
In case of a one-to-one relationship of business function and Customizing switch, the Customizing switch is automatically activated when the business function
is activated.

1.3 Overview

SAP Supplier Relationship Management (SAP SRM) is part of the SAP Business Suite. SAP SRM covers the full procurement cycle, from strategic sourcing to
operational procurement and supplier enablement by making use of consolidating core business content and master data.
SAP SRM is a purchasing application that offers sustainable savings and value generation through enterprise-wide supply management. With SAP SRM, you
collaborate with suppliers in the process of purchasing goods and services. This means you can optimize supplier selection and devise focused sourcing and
procurement strategies.
The SAP SRM user interface is based on the SAP NetWeaver Portal and Web Dynpro technologies. It provides a clear and effective means of managing the
divergent information required by the different users within an organization. The SAP NetWeaver Portal design features transparent and seamless integration by
displaying information from many SAP SRM application sources in a single portal browser window. This means that from your SAP SRM Control Center (the
starting point in the application), you have access to all SAP SRM applications that apply to your current work tasks.
You can also use SAP SRM applications without the SAP NetWeaver Portal and its navigation frame (see Portal-Independent Navigation Frame).
This overview provides you with an introduction to SAP SRM, including:
An introduction to the SAP SRM concepts
An overview of the SAP SRM user interface including basic navigation tips
Information on getting started

1.4 Master Data

All master data is available locally in the SAP Supplier Relationship Management (SRM) system. This data includes, for example, product master records,
business partner master records, and product categories. You copy the master data from the back-end system to SAP SRM.

Note
In SAP SRM, both materials and services are stored as products. However, you can distinguish materials from services by the product type.
Product categories correspond to material groups in the SAP back-end system.
Business partner master records correspond to supplier master records in the SAP back-end system.

Prerequisites
If the SAP SRM system communicates with an SAP back-end system, the length of the product ID has been restricted to a maximum of 18 characters.
This should be the case even if the products are created locally, and not replicated from the back-end system. If you assign a product ID with more than 18
characters, a different number (with a maximum of 18 characters) has to be assigned in the back-end system.
You have applied the delivered Business Add-Ins (BAdIs) to make sure that product IDs are unique across all systems. See Customizing: Cross-
Application Components SAP Product Enhancements Influence Internal Number Assignment and Influence External Number Assignment .

Caution
If these recommendations are not observed, you could have mismatched product or material numbers between your back-end, SAP SRM, and other systems.

More Information
For information about the replication of supplier master records, see Manage External Business Partners.
For information about the replication of material and supplier master records in the product master, see SAP Solution Manager under SAP SRM 2007 Basic
Settings for SRM Master Data Replication , choose the Configuration tab and open the document Replication of Materials from SAP Backend Systems.
For information about product categories, see Product Categories

PUBLIC Page 11 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
For more information about SRM-MDM Catalog, see SAP Help Portal at http://help.sap.com SAP Supplier Relationship Management SAP Catalog
Content Management SRM-MDM Catalog 2.0 .

1.4.1 Product Categories

You can create or replicate product categories manually in the back-end system.
When you create product categories, you can either manually configure the source system for the product category or select it using the search help.
In the following Customizing activities, you can access the search help for the source system:
Supplier Relationship Management SRM Server Technical Basic Settings Define Backend System for Product Category
Supplier Relationship Management SRM Server Cross-Application Basic Settings Account Assignment Define G/L Account for Product
Category and Account Assignment Category
Supplier Relationship Management SRM Server Cross-Application Basic Settings Define Objects in the Backend System (Purchase
Requests, Reservations, Purchase Orders)
Supplier Relationship Management SRM Server Sourcing Define Sourcing for Product Categories

Activities
In the back-end system, use the transaction COMM_HIERARCHY to create new product hierarchies and product categories .

1.4.2 Product Category Hierarchies and Supplier Hierarchies

You can use hierarchies to group together related product categories and suppliers, making them easier to find and report on. SAP Supplier Relationship
Management (SAP SRM) has three types of multilevel hierarchy:
Product category hierarchies
Supplier hierarchies
Central contract hierarchies
Central contract hierarchies are specific to central contract management and are described separately under Central Contract Hierarchies.

Prerequisites
You have activated each type of hierarchy in Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic
Settings Activate Hierarchies for Product Categories, Suppliers, and Contracts .
You have made all necessary configuration settings for the relevant hierarchy types in SAP Solution Manager under <project name> Configuration
SAP SRM <release> Basic Settings for SAP SRM Cross-Application Settings Hierarchies .

Features
You can use product category hierarchies and supplier hierarchies for reporting within SAP NetWeaver BI. To access the reports, go to the SAP NetWeaver

documentation in SAP Help Portal at http://help.sap.com SAP NetWeaver SAP NetWeaver <release> Library SAP Library SAP NetWeaver
Library SAP NetWeaver by Key Capability Information Integration: Key Areas BI Content Supplier Relationship Management Contract
Management .
Product Category Hierarchies
Product category hierarchies provide the following:
Extended search of product categories
Import of product category hierarchies into the SAP SRM system, for example:
Back-end material categories from SAP ERP
Standard product category hierarchies (such as UNSPC, eClass)
Customer-defined product categories
For information about importing external product category hierarchies, see SAP Solution Manager under <project name> Configuration SAP SRM
<release> Basic Settings for SAP SRM Cross-Application Settings Hierarchies Define Product Category Hierarchies .
Automatic determination of supply sources
During the sourcing process, the system selects all sources of supply that are assigned to the product category of a contract item or a supplier list entry. If
no source of supply can be selected from the product category, the next superordinate product category level in the product category hierarchy is used.
Supplier Hierarchies
Supplier hierarchies provide the following:
Structure and model of supplier relationships
In the back-end system, use transaction BPH to structure and model supplier relationships (for example, you have a superordinate supplier and want to

assign dependent, local subsidiaries to it). For more information about how to use transaction BPH, see SAP Help Portal at http://help.sap.com SAP
ERP SAP ERP Central Component Cross-Application Components SAP Business Partner (SAP BP) Concepts Business Partner Group
Hierarchy .
Hierarchy upload and download
Import of external supplier hierarchies into the SAP SRM system
You can import external data sources, such as D&B family trees or your own existing supplier categories. This means that you can incorporate the latest
market information into your supplier hierarchies. For example, new mergers and acquisitions in the supply base can immediately be taken into
consideration in reporting. For information about importing external supplier hierarchies, go to SAP Solution Manager under <project name>

PUBLIC Page 12 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Configuration SAP SRM <release> Basic Settings for SAP SRM Cross-Application Settings Hierarchies Define Supplier Hierarchies .

1.4.3 Business Partners

SAP Supplier Relationship Management (SAP SRM) uses the SAP business partner concept. An internal or external business partner is created in SAP SRM
for every person, organization, or group of people that could be involved in a business transaction, such as a bid invitation or a purchase order. Within the context
of business transactions, business partners can adopt various partner functions, as long as they have fulfilled the relevant requirements.
Business partners aggregate the master data of a person, organization, or group of people.

Prerequisites
The organizational structure exists. See SAP Solution Manager <project name> Configuration SAP SRM <release> Basic Settings for SAP
SRM Organizational Management User Management Organizational Structure Define Organizational Structure .
The business partner functions have been created in partner processing. Here you can enter your own description for the partner function, within a partner
function type. These texts are then displayed in the appropriate documents of a business transaction.
For more information, see Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Define
Partner Functions .

Features
A dynamic structure of partner functions is defined for the different business transactions in SAP SRM. For example, an internal employee can adopt the partner
function Requester or Goods Recipient , when creating a shopping cart.
The system automatically performs a semantic and syntactic check of data entered in partner processing. Among other things, the system checks whether the
business partner may adopt the assigned partner function.
Through the partner function, the corresponding business partner is assigned to the relevant documents of the business transaction. See also Addresses.
External Business Partners
The following table lists the partner functions for external business partners:

External Business Partner Functions

External Business Partner Function Description

Bidder Company that can submit bids in response to a bid invitation

Supplier Business partner from whom goods and services can be obtained

Contact person Specific contact person from the bidder or supplier company

Ship-from address Outbound delivery address of the company from where the goods are shipped

Invoicing party Business partner that sends the invoice

Note
During invoice creation, you can enter an invoicing party that differs from the supplier. The invoicing party is a mandatory partner function. If you do not enter
an invoicing party, the system uses the supplier.

When you create a supplier or bidder, you can also define a contact person. A user is then created for the contact person in SAP SRM in the Maintain User
transaction (SU01). The user ID and password are then sent to the contact person via e-mail. For every employee of a supplier or bidder, a contact person can be
created in addition to the business partner for that company.
Internal Business Partners
The following table lists the partner functions for internal business partners:

Internal Business Partner Functions

Internal Business Partner Function Description

Requester Employee in a company that requests a requirement. A requirement coverage request


can also be created on behalf of another employee.

Purchasing company Company that uses SAP SRM for procurement

Goods recipient Employee in a company that confirms goods receipt or performance of service

Ship-to address Address of a company to where the goods are delivered

Invoice recipient Business partner to whom the invoice is sent

Location Business partner that represents a delivery address or a plant in the back-end system

Employee responsible Employee in the company who is responsible for the contract

Internal business partners, with the exception of locations, are created for an organizational unit or an employee in the organizational structure. When a business
partner is created for an employee, this business partner is assigned to the relevant organizational unit within the organizational structure.
A relationship is defined between the employee business partner and the business partner of the associated organizational unit. For example, when you create a
sales employee's business partner, the employee relationship to the business partner of the organizational unit SALES is defined. The employee relationship
includes the employee's business address that is used when goods are delivered, for example.

1.4.3.1 Locking of Business Partners


PUBLIC Page 13 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
1.4.3.1 Locking of Business Partners

You can use this function to lock business partners for whom you want to suspend or terminate your business relationship. Locking a business partner means that
you can no longer create procurement documents (shopping carts, purchase orders, auctions, or RFx, for example) in respect of this business partner. You have
to end all procurement transactions before you can select the lock checkbox.
Before you save the lock checkbox, the system displays a list of all affected procurement documents. You can branch to the detail view of the individual
documents.
You can archive a supplier after you have locked it.

Prerequisites
You have one of the following roles:
SAP SRM: Strategic Purchaser (/SAPSRM/ST_PURCHASER_EHP1)
SAP SRM: Administrator (/SAPSRM/ADMINISTRATOR_EHP1)

Activities
To lock a supplier, select the Central Lock checkbox in business partner maintenance.
To delete the lock, deselect the Central Lock checkbox.
To archive a supplier, select the Archiving checkbox in business partner maintenance.

1.4.3.2 Business Partner Change Monitor

Business Partner Change Monitor in SRM Server


You can use this function as a purchaser to check changes made to supplier master data. Master data changes can reach the SAP Supplier Relationship
Management (SAP SRM) system in two ways:
Suppliers change their own data in supplier self-services.
Purchasers change supplier data in business partner management in SRM Server.
New supplier master data can reach the SAP SRM system in the following ways:
You have created a supplier master record manually in the SRM Server.
You have transferred a supplier from the Supplier Directory to the SRM Server.
You can transfer the changes automatically to the appropriate back-end system, provided that the supplier already exists in the back end.

Busines Partner Change Monitor in Supplier Self-Services


To use this function, you must activate the business function SRM, Supplier Collaboration (SRM_SUCO_1).

The following Customizing activity is relevant: SAP Supplier Relationship Management Supplier Collaboration Supplier Self-Registration
Activate/Deactivate Supplier Self-Registration . If you have activated this Customizing switch, the Business Partner Change Monitor is also available in
supplier self-services. It displays the changes that suppliers have made to their own data.

Restrictions

Caution
Note the following restrictions for both, the Business Partner Change Monitor in the SRM Server and in supplier self-services:
Data specific to SAP SRM, such as the purchasing organization, or data specific to SAP ERP, for example, FI data, are not transferred from the
Business Partner Change Monitor . You can use the transfer function for general master data, for example telephone numbers, or e-mail addresses.
You cannot transfer more than one additional address to the back-end system.

Activities

Activities in SAP SRM


In the SRM Administration work center, workset Application Monitors , select the Business Partner Change Monitor .
To transfer the changes to the back-end system, select a business partner and click Transfer Changes to Backend .

Activities in Supplier Self-Services


The following activities apply if you have activated the business function SRM, Supplier Collaboration (SRM_SUCO_1).

Prerequisites
You have activated the Customizing switch Supplier Self-Registration (SRM_701_SUCO_SUP_REG).

PUBLIC Page 14 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Activities
In the Application Monitors work center in supplier self-services, select the Business Partner Change Monitor .
To transfer the changes to the back-end system, select a business partner and click Transfer Changes to Backend .
If you do not want to transfer the changes to the back end, and you want to delete them in supplier self-services, click Delete .

1.4.4 User and Employee Data

The system administrator can use this function to maintain the personal, position, and user account data of an employee. The system administrator can also use
this function to preconfigure user self-registration as follows:
Create the first users and define them as managers
Manage the user master records of employees working within the company
Internal and external employees can use the self-service application to request users and enter their personal data.

Prerequisites
You have configured the organizational plan in SAP Solution Manager under <project name> Configuration SAP SRM <release> Basic Settings
for SAP SRM Organizational Management User Management Organizational Structure Create Organizational Plan .
You have maintained the business partner number ranges in Customizing for SAP Supplier Relationship Management under Cross-Application
Components SAP Business Partner Business Partner Basic Settings Number Ranges and Groupings Define Number Ranges .
You have defined the business partner groupings in Customizing for SAP Supplier Relationship Management under Cross-Application Components
SAP Business Partner Business Partner Basic Settings Number Ranges and Groupings Define Groupings and Assign Number Ranges .
Check whether group 0001 exists and create it, if necessary. This group must use an internal number assignment (that is, a number range must be
assigned). Make sure that at least one standard group is defined.
Number ranges for address management have been set up in Customizing: SAP Web Application Server Application Server Basis Services
Address Management Maintain Address and Person Number Range.
SAP Business Partner integration with Organizational Management has been set up in Customizing for SAP Supplier Relationship Management under
SRM Server Cross-Application Basic Settings Organizational Management Integration Business Partner-Organizational Management Set Up
Integration with Organizational Management .
A corresponding business partner has been created for each node in the organizational plan in Customizing for SAP Supplier Relationship Management
under SRM Server Cross-Application Basic Settings Organizational Management Integration Business Partner-Organizational Management
Match Up Organizational Units and Persons with Business Partners .

Features
Create, copy, or change employee data
Delete employee data and corresponding user account
Assign or unassign an employee or user account

Note
You cannot delete employees and their user accounts if they are involved in open transactions. When you delete an employee, the system also deletes the
user account. If HR integration is not active and the option Delete employee with positions is selected, the positions are deleted as well.

Activities
Personal
Personal data is a combination of name and title of an employee. These details are required when you create a new employee master record. You maintain them
on the application header.
Position
Position data comprises basic and address data. In Basic Data , you assign an organizational unit when you create an employee. If you have already maintained
this organizational unit in the organizational plan, the system automatically adopts the appropriate parameter setting for the user. If the employee is a department
head, select the department(s) under Department Head of . If the employee is a purchaser in a purchasing group that is not in his own department, you can
specify the purchasing group in the field.
User Account
User account data contains standard settings, extended settings, and role assignment information. Enter the User ID and E-Mail address for the employee in the
standard settings. You can enter a password for the user, if required. The password is deactivated by default and logon is only possible through the portal. You
can make additional settings as required.

More Information
For information about user attributes, seeUser Attributes.

1.4.5 Addresses

You can create and manage addresses for a business partner.

PUBLIC Page 15 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Purchasers can edit addresses for suppliers (external addresses). The system administrator can edit addresses for your own company (internal addresses) and
for external business partners (external addresses). Suppliers can edit their own addresses.

Prerequisites
You have created address types and partner functions in the SAP Supplier Relationship Management (SRM) system and you have assigned business
transactions to the address types.
You can only set the ship-to address or invoice recipient address for companies, that is, business partners for whom the attribute IS_COMPANY is set in the
master data. This applies to independent legal entities. For example, subsidiary companies.

Features
All addresses and address types are saved with the business partner. You can only add standard addresses to the system using master data maintenance. For
more information, see Manage External Business Partners. If no additional address is available for a business partner, the system uses the standard address.
You can define an ordering address, a ship-from address, or an invoicing party address as default. These do not replace the standard address. The standard
address should not be changed.
You can enter an address in the business document that differs from that in business partner master data and use the c/o field for the alternative name of the
business partner. This address is only used once for the current transaction and is not saved in the master data.
If you want to use an address for a business partner on a long term basis that does not exist in the master data, you should enter the address in business partner
maintenance. You should enter the alternative name in the c/o field and enter further data in the other address fields. Later, you can assign this address to a
business document using the search help.

Activities
Purchasers can set the following addresses and defaults for suppliers or for themselves:
Ordering address
Ship-from address
Invoicing party address
System administrators can set the following addresses and defaults for their own company (purchasing side):
Ship-to address
Invoice recipient address

1.4.6 Revision Level Display

The revision level to which materials have been assigned in SAP ERP can also be displayed in the SAP SRM system. If different revision levels are available for
a material replicated from SAP ERP, you can choose between them in the SAP SRM business objects.

Integration
This function is mainly used in the business scenario Plan-Driven Procurement with Plant Maintenance .

Prerequisites
You are using SAP ERP 2005 Support Pack 9 or higher
The product type of the product for which you want to display the revision level is Material
The product ID has been replicated from SAP ERP
You are using a homogenous system landscape, that is, the revision level for the product is the same in all connected backend systems

Activities
You activate the Revision Level field from SAP ERP in Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application
Basic Settings - Extensions and Field Control (Personalization) Configure Field Control Configure Control for Fields on Item Level . Revision level
activation is available for the following business objects:
Shopping cart
Purchase order
Purchase order response
Confirmation
Invoice
Central contract
RFx
RFx response
Auction

Example

PUBLIC Page 16 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
To activate the Revision Level field for the shopping cart, insert structure field name REV_LEV and Bus Obj Typ BUS 2121 in the view
/SAPSRM/V_MDF_IC and set the Visible and Enabled indicators.

1.5 Functions

This section contains functional descriptions for each area within SAP Supplier Relationship Management (SAP SRM).
For specific configuration information for these areas, see the SAP Solution Manager.

1.5.1 Global Functions

This section explains functions that occur throughout SAP Supplier Relationship Management (SAP SRM). Even though the functions are normally used in similar
fashion throughout the different SAP SRM areas, there are exceptions. The explanations in this section are provided as a general overview of the different
functions. Transaction-specific details are described in the relevant documentation.

1.5.2 Administrative Functions

The functions listed in this section are those carried out by the user with the role SRM Administrator or the system administrator.

1.5.3 Central Contract Management

You can use this function to manage central contracts in SAP Supplier Relationship Management (SAP SRM) and connected SAP ERP systems. The features of
contract management allow you to negotiate new contracts with new and existing suppliers, as well as renegotiate expiring contracts with existing suppliers.

Integration

Initial Upload from SAP ERP to SAP SRM


You can use program BBP_CONTRACT_INITIAL_UPLOAD to upload purchasing contracts and scheduling agreements from an SAP ERP system to an SAP
SRM system to use as the basis for a central contract. This upload is a one-time activity performed at the time of installation in the SAP SRM back-end system.
For more information, see the program documentation using transaction SE38.

Search and Classification (TREX)


In central contracts, you can use the TREX Search Engine to carry out full-text searches in attachments, supplier texts, and notes. The TREX Search Engine is
delivered with SAP SRM, but you must first install it and run program BBP_TREX_INDEX_ADMIN. This program creates a new index for existing documents and
enables all new or changed documents to be indexed automatically when you save the central contract. The documents must be indexed for the full-text search to
work.

SAP NetWeaver Business Warehouse


You can integrate SAP NetWeaver Business Warehouse, to use reports to evaluate and analyze your central contracts. For more information, see the SAP Help

Portal at http://help.sap.com SAP NetWeaver BI Content Supplier Relationship Management Contract Management .

Archiving
You can archive complete hierarchies by running a report in the system. To do this, the contracts within the hierarchy must all have the status of Can be
Archived . For more information, see Archiving Central Contracts (SRM-EBP-CON).

Features
In the Central Contract Management application, you can use the following features:
Create and change a central contract and renegotiate an existing central contract directly with suppliers by creating an RFx (see Central Contracts and
Creating Central Contracts).
Use a central contract as source of supply across all connected systems, accumulating buying power into a superordinate contract using contract
hierarchies (see Central Contract Hierarchies).
Update data in purchasing info records and source list records automatically when you create or change a central contract then distribute it from SAP SRM
to SAP ERP (see Central Contract Distribution).
Control access to a central contract through the assignment of authorizations (see Authorizations in a Central Contract).
Configure the system to generate alerts for release quantity or expiring contracts, for example. This helps you to tailor your central contract and define its
conditions as you develop it. For more information, see Alert Management.
Check the status of a central contract throughout its lifecycle (see, Status Management)
Export and import data from central contracts. This allows you to create or edit data offline and then update it in the system (see Upload and Download of
Purchasing Documents).
Check the change history for all fields on the user interface in central contract management and select versions of a central contract and compare changes
at header and item level (see Central Contracts).

PUBLIC Page 17 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
More Information
Hierarchies

1.5.4 Shopping Cart

Using the shopping cart, company employees can procure the goods and services that they need for their work area. This takes the pressure off the purchasing
department, who in turn can concentrate on strategic tasks, such as contractual negotiation.

Integration
This function is used in the business scenario Self-Service Procurement .
If shopping carts contain incomplete items (for example the supplier is not entered), purchasers receive a work item in their Universal Worklist (UWL) for
completion.

Prerequisites
To use shopping carts, you must have made the following settings in Customizing for SAP Supplier Relationship Management :
You have defined the organizational structure and the attributes of the organizational units in Customizing for SAP Supplier Relationship Management under
SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan .
You have defined the back-end system where you create purchase orders, purchase requisitions, and reservations. You do this in Customizing of SAP
Supplier Relationship Management under SRM Server Technical Basic Settings Define System Landscape and Define Back-End System
for Product Category .
You have set up the catalogs in Customizing for SAP Supplier Relationship Management under SRM Server Master Data Content
Management Define External Web Services .
You have specified which follow-on documents the back-end system or SAP SRM creates from the shopping cart in Customizing for SAP Supplier
Relationship Management under SRM Server Cross-Application Basic Settings Define Objects in Back-End System (Purch. Reqs,
Reservations, Purch. Orders) .

Note
To create service purchase orders in the back-end system, you use a back-end system with release SAP R/3 4.0B or higher.

To order using procurement cards, ensure the following:


The procurement cards have been configured in Customizing for SAP Supplier Relationship Management under SRM Server Procurement Card
Purchase orders are created locally in the SAP SRM system
The supplier accepts the procurement card.
When creating the shopping cart, the purchaser selects the product category that has been defined for the procurement card in Customizing.

Features

User Interface Variants


In the Shop application, there are three user interface variants:
Shopping Cart (Professional)
Purchasers or purchasing assistants can use the Professional user interface to fill shopping carts with products quickly and easily.
Shopping Cart (Wizard)
Employees can order products simply by using the Wizard user interface.
Simplified Shopping Cart
Employees who occasionally request products or free-text items can use the simplified shopping cart to order products in a fast and self-explaining way.
You can use the Business Add-In (BAdI) Change Display in Shopping Cart to override the standard settings of the interface and tailor the interface to fit the
requirements of your enterprise. You can access this BAdI in Customizing for SAP Supplier Relationship Management under SRM Server Business
Add-Ins (BAdIs) Shopping Cart and Requirement Items Change Display in Shopping Cart .

Workflow
A workflow starts once the shopping cart is ordered. This workflow checks whether approval is required.
If an approval is required, a work item is sent to the universal worklist (UWL) of the relevant approver.
If no approval is required, the system creates the necessary follow-on documents, such as purchase requisitions, purchase orders, or reservations, for the
shopping cart. The shopping cart information and the Customizing settings in your SRM system determine what types of documents are created and what
system they are created in.
For more information about approval workflows, see Process-Controlled Workflows.

Caution
You cannot delete items that have been approved and for which follow-on documents exist in the back-end system. This applies under the following
circumstances:
A purchase requisition has been created and the Completed indicator has been set for it, or the quantity received for the purchase order is equal to or

PUBLIC Page 18 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
greater than the quantity requested.
A reservation has been created and the Final Issue indicator has been set for it, or the quantity withdrawn is equal to the quantity requested.
A purchase order has been created and the Delivery Completed indicator has been set for it, or a goods receipt has been entered.

More Information
Procurement Card Payment Process
Process-Controlled Workflows

1.5.5 Purchase Orders

In SAP Supplier Relationship Management (SAP SRM), you process purchase orders selecting the Purchasing tab and choosing Purchasing in the Detailed
Navigation area. You can also create purchase orders from scratch, using the service Create Documents Purchase Order . In this case, the details such
as the purchaser’s organizational data are transferred from the user attributes to the purchase order.
You use the purchase order either for local procurement (standalone scenario) or in the extended classic scenario. For more information, see Technical Scenarios.

Integration
This function is used in the following business scenarios:
Self-Service Procurement
Service Procurement
Plan-Driven Procurement

Sourcing
By default, SAP SRM does not transfer requirement items to the purchaser's Sourcing application. If you activate Sourcing for product categories, SAP SRM
does not immediately create local purchase orders from shopping cart items. Using the functions of the purchaser's Sourcing application, you can process items
from different shopping carts and combine these into purchasing contracts, purchase orders, live auctions, or RFx.
For more information, see Customizing for SAP SRM under SRM Server Sourcing Define Sourcing for Product Categories .

Prerequisites
If you want to generate back-end purchase orders from all local purchase orders, you must have activated the extended classic scenario.
For more information, see Customizing for SAP SRM under SRM Server Business Add-Ins Control Extended Classic Scenario Activate Extended
Classic Scenario .

Features
You can create purchase orders in the following ways:
From shopping cart items
If the shopping cart is complete and approved, a purchase order is generated automatically and is transferred directly to the approval workflow before it is
sent to the supplier.
If the shopping cart items are incomplete, the system creates separate purchase orders. Using a Business Add-In, you can combine incomplete items into
one purchase order.
For more information, see Customizing for SAP SRM under SRM Server Business Add-Ins (BAdIs) Define Grouping Criteria for Local Purchase
Orders .
From RFx responses
For more information, see SAP Bidding Engine.
From live auctions
For more information, see Live Auction Cockpit.
From requirements from external systems, for example, planning systems.
For more information, see Procurement of External Requirements.
Manually
Depending on whether the purchase order is complete or incomplete, it is sent into the approval workflow or it appears in your POWL.

Overview
The purchase order Overview displays all the required header and item data of the purchase order.
Note the following functions:
Add/Remove Condition
You can add or remove prices and conditions (percentage discounts and absolute discounts) per item and on header level. See Price Data Processing in
the Purchase Order.
Propose Sources of Supply
You can have the system determine and assign sources of supply, for example, contracts, and supplier-specific prices. For more information, see
Assigning Existing Sources of Supply and Central Contracts.
Default Settings
You can enter default values for the delivery address and account assignment values of purchase order items. If you enter values here, these values are
defaulted to any new item you add afterwards. The values are retained for subsequent items unless you change the settings again.

PUBLIC Page 19 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
As the delivery address or company address, you can use a master data address. To display master data addresses, choose the search help for the
Name field. In the popup, select Find Ship-To Adresses of Employees or Find Ship-To Addresses of Companies from the More Search Helps drop-
down box and choose Start Search . Your personal master data addresses are displayed then.
If you want to reset the values to the settings defined in organizational management, you can run report /SAPSRM/CUSTMZ_SW_PO_DEFAULT. For more
information, see the report documentation.
The following Customizing activity is relevant: SAP Supplier Relationship Management SRM Server Purchase Order Activate/Deactivate Default
Values for Purchase Order Items .
To enter default values for the delivery address and account assignment values of purchase order items, you must activate the business function SRM,
Continuous Innovations (SRM_CONT_IMPR_1).

Header
Note the following functions:
General Data
Partner
You can accept a preferred supplier if it has been suggested by the requester of a shopping cart: In the partner table, select the line Preferred
Supplier and then click on Select as Supplier.
Procurement Card
If you want to pay by procurement card, enter your card information here.
Output
You can choose a medium other than the supplier’s default output medium if you need to, provided the relevant fax, e-mail and XML data exists in the
supplier master record. You can change the data for fax and e-mail and, if necessary, can set a different printer. If you choose Order and Send
immediately , the purchase order output starts immediately (according to the current Customizing settings).
To create an output for a completed purchase orders, use the query Document Output in your POWL.
For more information, see Output of Purchasing Documents and Customizing under SRM Server Cross-Application Basic Settings Set Output
Actions and Output Format Define Actions for Document Output .

Note
If you have defined and activated your own form for the selected output medium, SAP SRM uses this in place of the standard form.

Budget
If you are authorized to view the budget, a table shows, for each selected account assignment object, the budget and the credit limit used.

Items
Note the following functions:
Add items
You can add items to your purchase order from catalog, shopping cart, product master, or as free description.

Note
You cannot transfer ordered items to a purchase order.

When you have added an item, you can change the delivery date and the price in the item overview.
The description and unit of measure can, however, only be changed if the item does not contain a product master record. You can only change the quantity
unit for existing items to a unit of the same dimension, for example, from a kilogram to a gram.
Limit items
You can process the value limit (maximum purchase order value that goods or services must not exceed) and the expected value (estimated
value of the purchaser, either under or the same as the value limit). The expected value serves to update the commitment in Controlling and the
budget is reduced by this amount.
You can spread the value limit over partial limits (contract limits and remaining limits) or establish an undefined value limit. The sum of the
contract limits created may be greater than the value limit. The system checks and ensures that the value of the ordered items is not greater
than the value limit.
You can assign the relevant product category and define the period in which the goods should be delivered or the service performed.

Note
If you do not specify a value limit or a remaining limit, the system designates the remaining limit by default as unlimited .

Order as Direct Material


If you click on this button, the selected item is ordered as stock item and you do not need to assign an account.

Item Details
Note the following functions:
General Data
Material items that have been replicated from the ERP system can have their revision level displayed in the General Data of the item.
Basic
You can define tolerances for over- and underdelivery and the system uses these to check the confirmation.
Partner
The system takes into account both, sources of supply (for example, contracts) with a location that you assign here, and sources of supply without
location. In the extended classic scenario case, the system derives the plant in the back-end system from the location.

Note
You can combine requirements that contain different partners in one purchase order. At header level, you can enter partners that are valid for all
items.

PUBLIC Page 20 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Prices and Conditions
You can add or remove prices and conditions (percentage discounts and absolute discounts). See Price Data Processing in the Purchase Order.
Account Assignment
The account assignment is transferred from the preceding document, if existing. You can assign the following types of accounts (also multiple account
assignment):
Asset
Cost center
Network
Order
Sales order
WBS element
You can copy the account assignment data to a clipboard and use it for further items in the purchase order.
Related Documents
Document Control
You can define the follow-on documents that the system expects for this item. This definition overrules the settings made in the supplier master data.
Statistics
You can display the value of the goods received and services rendered to date, as well as the value of the invoices received to date.
History
The purchase order and its related documents are displayed. The history is item-specific.
Delivery
Delivery Schedule
You can specify delivery dates for each individual item in a purchase order.

Example
If you order three trucks, you can specify that one truck is delivered per month.

Purchase Order Response Delivery Schedule


You can accept or reject changes the supplier made in the purchase order response.
Shipping Notification
You can display the following data (further details are available from the carrier's system via the URL):
Delivered quantity with unit of measure and delivery date
Shipping notification number, item number, and tracking number
Sales document number and item number (of the supplier)
Call URL of the carrier
You can use the BAdI Calculate Schedule Lines for Deliveries to set up the system in such a way that it automatically suggests distributed
scheduling agreements when you enter shopping cart items in a purchase order.
For more information, see Customizing for SAP SRM under SRM Server Business Add-Ins (BAdIs) Calculation of Phased Deliveries.

Notes and Attachments


You can attach files of any document type. You can also specify text notes at header and item level.

Approval
You can see the current state in the approval workflow that the purchase order is in. In the item details under Approval Preview , you can see the approval status
per item.

Tracking
History
The purchase order and its preceding and follow-on documents (for example, shopping cart and confirmation) are displayed.
Version Overview
You can access the different versions of the purchase order.
Change Documents
All changes are tracked, whether initiated by the system or by a user.

More Information
Settings for the Purchase Order in the Extended Classic Scenario

1.5.6 Sourcing

You can source goods using auctions or RFxs (requests for information, requests for proposal, and/or requests for quotation). You can source goods with or without
the integration of the sourcing application. As a professional purchaser you can use the sourcing application to process requirements and to determine the best
source of supply.

1.5.7 Invoices and Credit Memos

The following section describes the functionality within SAP Supplier Relationship Management (SAP SRM) that enables you to process invoices and credit
memos.
An invoice is a document that states the invoice recipient’s obligations to the supplier or service provider, and is created after the goods receipt or service
performance has been confirmed. A credit memo, by contrast, reduces the invoice recipient’s obligations to the supplier or service provider. It is created if the

PUBLIC Page 21 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
goods supplied or the service provided turns out to be defective or if the price charged is too high.

1.5.8 Confirmations

You can use this function in SAP Supplier Relationship Management (SAP SRM) to confirm the delivery of goods, and enter services rendered and hours worked.

Integration
This function is used in the following business scenarios:
Self Service Procurement
Service Procurement
Plan-Driven Procurement
In SAP SRM, the goods receipt and the service entry sheet are represented by a single confirmation document. Confirmations can refer either to purchase orders
created in SAP SRM, or to purchase orders created outside SAP SRM in the back-end system.

Prerequisites

Roles
You must have one of the following roles assigned to you before you can perform any of the confirmation procedures:

Role Name Portal Role SAP SRM Server Role

Employee com.sap.pct.srm.ro_employeeselfservice /SAPSRM/EMPLOYEE

Operational Purchaser com.sap.pct.srm.ro_operationalpurchaser /SAPSRM/OP_PURCHASER

Supplier com.sap.pct.srm.ro_supplier /SAPSRM/SUPPLIER

Goods Recipient com.sap.pct.srm.ro_goodsrecipient /SAPSRM/RECIPIENT

Depending on the roles assigned to you in SAP SRM, different options are available for confirming goods and services, as well as for entering time data for
services rendered.
If you have been assigned the Employee or Operational Purchaser role, you can enter confirmations for goods receipts and services performed. You can do so
for items in your own shopping cart, or for which you are the requester or the goods recipient.
If you have been assigned the Supplier role, you can do the following:
Confirm that goods have been delivered or services have been rendered
Enter times for services rendered
For more information, see Confirmation Processing.

System Requirements
To create a confirmation from a back-end service purchase order item, you must have installed SAP R/3 4.0 or a later release.

Confirmations Relating to Purchase Orders for Materials Created in a Back-End System


To transfer confirmation documents to the back-end system using the ALE interface, you must have made the ALE settings in Customizing for SAP Supplier
Relationship Management under SRM Server Technical Basic Settings ALE Settings (Logical System) .

Confirmations Relating to Purchase Orders for Services Created in a Back-End System


SAP SRM assigns the confirmation a number from the number range set in Customizing for SAP Supplier Relationship Management under SRM Server
Cross Application Basic Settings Number Ranges SRM Server Number Ranges . When you transfer the confirmation to the back-end system and
create it there, the system copies the number from SAP SRM to the communication number field on the service entry sheet.
The number range in SAP SRM for the confirmation must not overlap with the number in the communication number field of the service entry sheet that was
transferred to the back-end system by data exchange. If the number ranges do overlap, the service entry sheet will not be created.

Features
The functions available for confirmations include the following:

Function Description

Revert Restores items that have been deleted from the purchase order.

Details Opens the Item Details Basic Data


Item Data
Account Assignment
You can see who bears the costs and, if necessary, you can distribute the cost
among several cost centers. In the case of confirmations referring to back-end
purchase orders, you cannot change the account assignment unless you are
creating an unplanned item for the limit item of a service purchase order.

PUBLIC Page 22 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Notes and Attachments
You can attach documents providing additional information for the approver. You
can also enter a text that is sent to the supplier, or an internal note to send the
approver or purchaser a message.

Final Delivery Indicates whether the confirmation represents the final delivery of the item. SAP SRM
transfers this information to the purchase order item and, in the case of unplanned
items, to the total limit for the purchase order.

Save Temporarily saves an incomplete confirmation. It can be reprocessed at any point.

Confirm Posts the confirmation after you have entered all confirmation information. The approval
workflow starts in the background.

Activities
You use the goods, services, and time confirmation to confirm, for example, the receipt of goods or services. The outcome of the workflow depends on your
technical scenario. A local purchase order is saved in SAP SRM as a confirmation. A purchase order entered outside SAP SRM is copied to the back-end
system as either a goods receipt or a service entry sheet.

More Information
Service Time Entry
Approval Workflow
Return Deliveries

1.5.9 Business Workflow

SAP Supplier Relationship Management (SAP SRM) provides two frameworks for approval workflows, application-controlled and process-controlled. The
application-controlled workflow framework was used in SAP SRM 5.0 and earlier, and the process-controlled workflow framework was introduced in SAP SRM
2007 (SAP SRM 6.0).

Note
The application-controlled workflow framework is supported for customers of SAP SRM 5.0 or earlier to maintain their older workflows. New SAP SRM
customers must use the process-controlled workflow framework. It is not supported that new customers use application-controlled workflows!

Prerequisites
Process-controlled workflows are used by default in new SAP SRM systems. You can switch the workflow framework setting to application-controlled workflows in
Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Business Workflow Select Workflow
Framework .

Features

Application-Controlled Workflows
These are approval workflows based on SAP Business Workflow, in which the application is in control over the SAP Business Workflow templates. Multiple
workflow templates can be used, using defined start conditions.

Process-Controlled Workflows
These are approval workflows based on SAP Business Workflow, in which the modeled or configured process, and not the application itself, controls the process
flow. A unified workflow template is used, and a process is evaluated by way of a process schema containing a set of distinct process levels. The Business Rule
Framework can be applied to control further the process flow.

1.5.9.1 Process-Controlled Workflows

In SAP Supplier Relationship Management (SAP SRM), you use process-controlled workflows to model and carry out approval processes for purchasing
documents, such as shopping carts. Workflows provide easy and flexible implementation of approval processes. Approval processes typically run on several
process levels. Throughout these process levels, a document can require different kinds of checks and can involve agents with different roles, for example:
A purchaser must complete a document lacking important information.
A specialist must check and approve technical or other product-related information in the document.
A manager must give financial approval, for example, if a shopping cart exceeds an employee's individual spending limit.
Responsibility for approving the items of a document can be distributed among several agents. However, at each process level, all items of the document must
be decided upon. Therefore, the next process level cannot start until all agents have processed their respective items.
Users can only make decisions in an approval process if they have received a workflow work item in their Universal Worklist (UWL). If there is more than one
responsible agent for the items of a document on one process level, each agent receives a workflow work item. As soon as one of them accesses his or her work
item, the document is locked for other users.

PUBLIC Page 23 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Process-controlled workflows are available for the following business objects:
Shopping cart
Purchase order
Contract
RFx
Quote
Invoice
Confirmation

Note
Purchase order responses do not use the process-controlled workflow framework. Instead, the process logic is hard-coded. For more information, see Approval
Workflow for Purchase Order Responses.

Integration
This function is used in the following business scenarios:
Self-Service Procurement
Plan-Driven Procurement
Service Procurement
Sourcing
Contract Management
The process-controlled workflow uses the following SAP NetWeaver technologies:
SAP Business Workflow
The SAP Business Workflow provides workflow templates that drive and control the approval process. The SAP Business Workflow also creates the work
items that are displayed in the responsible agent's UWL.
For more information about SAP Business Workflow, see the related documentation for SAP NetWeaver 7.0 on SAP Help Portal at http://help.sap.com

SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Business Services SAP Business
Workflow .
SAP Business Rule Framework (BRF)
You use the BRF to define triggering events and expressions that serve as start conditions for the different process levels.
You define expressions in the BRF at design time. Expressions return a result; for example, the shopping cart limit or the total shopping cart amount. At
runtime, by using these expressions, the system checks whether or not a predefined process level must be activated. For example, the system checks
whether a shopping cart limit has been exceeded.

For more information about the BRF, see SAP Help Portal at http://help.sap.com SAP ERP Central Component Cross-Application Services
Business Rule Framework (BRF) .

Note
You define settings for the SAP Business Workflow, BRF, and process-controlled workflows in SAP Solution Manager under <project name>
Configuration SAP SRM <release> Basic Settings for SAP SRM Cross-Application Settings Business Workflow Process-Controlled
Workflow .

Universal Worklist (UWL)


The UWL in the SAP NetWeaver Portal is used for delivering workflow work items to the responsible agents. From the UWL, the responsible agent can
navigate directly to the application in which the task can be completed. In addition, you can use the Approve or Reject pushbuttons provided by the UWL
to approve or reject a document immediately.
Alternatively, users can access their work items directly from the document. When they open a document using the personal object worklist (POWL), the
Show My Tasks button is available. Choosing the button opens a popup that displays the user’s current work items for this document.

Features

Simple Configuration at Design Time


Simple options for implementing complex business processes, for example, with the help of the BRF.
Predefined standard process level types:
Approval with completion
Approval
Automatic
Generic set of SAP Business Workflow templates, on which all processes are based:
Main SRM Approval Process Template (WS40000014)
Process Level Control (WS40000015)
Completion Subworkflow (WS40000017)
Approval Subworkflow (WS40000016)

Flexible Adaptation at Runtime


Adding ad hoc agents
Adding ad hoc reviewers
Forwarding work items
Assigning substitutes
Using the back-and-forth function

PUBLIC Page 24 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
For more information, see Approval Workflow Features.

Approval Process Overview


An approval process overview is available for all users involved in the approval process. The process overview gives the following information:
History of the document: all completed process levels and any restart of the process
Current status of the document: all work items at the current process level
Forecast of further required decision steps
The approval process overview shows all work items that have been created for a process level.

Decision Sets
Responsibility for the items of a document can be distributed among several agents. The items are grouped according to the area of responsibility to which they
are assigned. Each group of items represents one decision set. A work item is created for each decision set so that the responsible agents can approve or reject
their respective items. For more information, see Decision Sets.

1.5.9.2 Application-Controlled Workflows

In SAP Supplier Relationship Management (SAP SRM), a range of business transactions are based on application-controlled workflow processes. Some
workflows are essential while others can be used on an optional basis. Some are also provided as alternatives to others.
The documentation for application-controlled workflows uses older SAP SRM terminology so that it corresponds to the SAP SRM user interface. The affected terms
include the following:
Bid invitation (now referred to as RFx )
Bid (now referred to as RFx response )
Vendor (now referred to as supplier )
The universal worklist (UWL) in the SAP NetWeaver Portal is used for delivering workflow work items to the responsible agents. From the UWL, the responsible
agent can navigate directly to the application in which the task can be completed. In addition, you can use the Approve or Reject pushbuttons provided by the
UWL to approve or reject a document immediately.

Features
The following (standard) application-controlled workflows support SAP SRM basic processes:

Workflow for: Scenario

Shopping cart (SC) Approval workflows for shopping carts


WS10000060 – Without approval The relevant approval workflow is started, depending on the total value of the shopping
WS10000129 – One-step approval cart and the role of the requester.
WS10000031 – Two-step approval

Confirmation (CF) Approval workflows for confirmations


WS10400010 – Without approval The relevant approval workflow is started, depending on completion status, creator role,
WS10400002 – One-step approval and total value of the confirmation.
WS10400009 – Two-step approval
WS10400020 – Administrator approval

Invoice (IV) Approval workflows for invoices


WS10400016 – Without approval The relevant approval workflow is started, depending on completion status, invoice
WS10400017 – One-step approval category (credit memo or invoice), creator role, and total value of the invoice.
WS10400018 – Two-step approval
WS10400021 – Administrator approval

Purchase order (PO) Approval workflows for purchase orders and change versions of purchase orders
WS14000075 – Without approval The relevant approval workflow is started, depending on various attributes of the object
WS14000089 – One-step approval type Purchase Order EC (BUS2201), for example, change of account assignment
WS14000145 – n-step approval data , and total amount difference .

Purchase order response (POR) Workflows for transfer of data of purchase order response to purchase order
WS14500001 – Automatic data transfer Depending on the various criteria, the POR data is either transferred to the purchase
WS14500019 – Manual data transfer order automatically or manually by the purchaser.

Contract (CTR) Approval workflows for contracts and change versions of contracts
WS14000086 – Without approval The relevant approval workflow is started, depending on various attributes of the object
WS14000088 – One-step approval type Purchasing Contract (BUS2000113), for example, change of conditions . The alert
WS14000148 – n-step approval workflow reacts to certain events that are evaluated by SRM Alert Management.
WS10400022 – Alert workflow

Bid Approval workflows for bids


WS79000010 – Without approval The relevant approval workflow is started, depending on whether a manager or an
WS79000002 – One-step approval employee of the purchasing group accepts a bid for a bid invitation.
WS14500044 – n-step approval

Bid invitation Approval workflows for bid invitations


WS14500026 – Without approval After bid invitations (and their change versions) are published, one of these three
WS14500027 – One-step approval approval workflows is started, depending on the start conditions. The implementation of
WS14500028 – n-step approval the BAdI BBP_WORKFLOW_APPROV_BADI is a prerequisite for n-step approval (with back
WS14000091 – Alert workflow & forth-processing). (If this is not the case, the manager of the purchasing organization is
WS14500035 – Monitoring workflow determined as approver.) The Alert Workflow waits for a reply from the external auction
tool. The Monitoring Workflow sends a notification when the bid invitation ends.

PUBLIC Page 25 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
tool. The Monitoring Workflow sends a notification when the bid invitation ends.

New password This workflow starts after an SAP SRM user requests a new password.
WS10000223

New bidder/vendor This workflow starts when a bidder or vendor requests a new user for the SAP SRM
WS10000209 system.

Transfer of SC to PM system This workflow causes a SC to be transported as requirement coverage request to the PM
WS10000202 backend (only for classic scenario).

These workflows support further SAP SRM processes or are provided as an alternative to standard workflows:

Workflow for: Scenario

Spending limit for SC (one-step) One-step approval workflow for shopping cart (alternative to SC workflows)
WS10000276 The system uses spending and approval limits to first determine whether approval is
necessary, and then to determine the approver.

Spending limit for SC (n-step (dynamic)) Multistep approval workflow for shopping cart (alternative to one-step spending limit
WS14000109 WFL)
Step by step approval of SC depending on spending and approval limit.

Spending limit for SC with BAdI (n-step (dynamic)) N-step approval workflow for shopping cart (alternative to all SC workflows)
WS14000133 Determination of approver occurs dynamically via a BAdI.

Item-based approval for SC Multistep approval of individual SC items by responsible approver


WS14500015

Complete SC Completion of shopping cart by purchaser


WS14000044 Incomplete shopping cart completed by purchaser before approval.

Purchasing budget workflow (SC) Approval of the SC is not dependent on its value, but rather on the employee's
(Workflow scenario) purchasing budget.

Approval Workflows for Suppliers and Bidders Approval of suppliers


WS14000043 – Without approval Relevant approval workflow is started, depending on processor authorization.
WS14000030 – One-step approval

Lock SUS suppliers Notification workflow after a SUS supplier has been locked
WS145000021 Workflow starts after a SUS supplier has been locked. All purchasers of the purchasing
organization of the locked supplier receive a notification by e-mail.

Procurement card Approval of card charges


WS10000093 – First approval The cardholder is responsible for approval unless the settlement value exceeds the
WS10000100 – Second approval spending limit set in Customizing. If this is the case, the manager is responsible for
approval. (For more information, see Customizing for SAP SRM under SRM Server
Procurement Card Process Procurement Card .

Purchase order response (POR) Notification when a POR is received and monitoring of POR receipt
WS14500007 – Notification As an alternative to the workflow for manual data transfer, ( WS14500019 ) the
WS14500017 – Alert workflow notification workflow just informs the purchaser that the document requires processing.
The alert workflow monitors receipt of a POR for a PO where the Purchase Order
Response Expected indicator is set.

Stochastic document check (IV and CF) Flexible use of approval workflows for stochastic document check of invoices and
confirmations
Depending on the document type, its subtype, and the document value, you can create
your own rules for using certain specific workflows for random checks of IV and CF. For
more information, see release note Changes in SAP Business Workflow (Enterprise
Buyer 4.0) , section Workflow Settings for Stochastic Document Check

Correct XML invoices Correction workflow for erroneous XML invoices


WS14500020 Erroneous XML invoices are no longer automatically sent back. Now, they can be
corrected or processed by the responsible employee before they are posted. The work
item contains a link used to branch to invoice processing.

As well as these additional workflows, there are other workflows designed to make working with the SRM Server easier. Mostly, these are notification workflows that
send a message to the responsible processor when a certain system event occurs. In addition, you can easily change the approval processes of SAP SRM
documents by using or activating predefined default settings. (For more information, see the Changes to SAP Business Workflow release note . )

Activities
You configure application-controlled workflow settings in Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application
Basic Settings Business Workflow Application-Controlled Workflow .

1.5.10 Supplier Qualification

Supplier Qualification with SAP SRM


The business scenario Supplier Qualification comprises the following functions:
Supplier registration
Supplier preselection
Supplier directory

PUBLIC Page 26 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
You can use Supplier Qualification with SAP SRM and SAP ERP as a back-end system, or only using SAP ERP. The following tables show the relationship
between the above functions.
The first table ( Supplier Registration, Supplier Preselection, and Supplier Directory without Separate Registration System ) is valid if you have activated the
business function SRM, Supplier Collaboration (SRM_SUCO_1).

The second table ( Supplier Registration, Supplier Preselection, and Supplier Directory with Separate Registration System ) is valid if you have not activated the
business function SRM, Supplier Collaboration (SRM_SUCO_1).

Supplier Registration, Supplier Preselection, and Supplier Directory without Separate Registration System
The following Customizing activity is relevant: SAP Supplier Relationship Management Supplier Collaboration Supplier Self-Registration
Activate/Deactivate Supplier Self-Registration .

Steps Sub-Steps Results

Supplier registration The purchaser sends an invitation e-mail to a potential -


supplier, or a potential supplier calls up the Web site of the
purchasing company.

- The potential supplier calls up a URL that opens the self- -


registration page in the supplier self-services system.

- The potential supplier enters their master data and assigns The potential supplier is registered in the supplier self-
themselves to one or more product categories. services system as a business partner with the Potential
Supplier role.

- The potential supplier automatically receives a link to one -


or more questionnaires (a general questionnaire and one
questionnaire for each product category). You can define
which questionnaire to use for which product category in
Customizing for SAP Supplier Relationship Management
under Supplier Collaboration Supplier Self-
Registration Questionnaire Settings Assign
Questionnaire and Language to Product Category

- The potential supplier fills out the questionnaires. The questionnaires are stored in the supplier self-services
system.

Supplier preselection The purchaser calls up Supplier Preselection in the SRM -


Server system.

- The purchaser reviews the master data and the Accepted potential suppliers appear in the supplier
questionnaires in the supplier self-services system and directory.
either accepts or rejects the potential supplier.

Supplier transfer The purchaser selects a supplier from the supplier Supplier master records are created in the SRM Server
directory in SAP SRM and transfers this supplier into the system. An XML message is sent to supplier self-services.
SRM Server System using OPI. The supplier data is transferred to the Business Partner
Change Monitor (SAP SRM) and can be transferred from
there to the SAP ERP system.

Supplier enablement The supplier self-services system sends an e-mail with a -


registration number to the supplier.

- The supplier uses the registration number to create a user -


in supplier self-services.

- The supplier can change his or her master data in supplier The changes are transferred to the supplier directory.
self-services.

Data transfer The purchaser sees these changes in the Business -


Partner Change Monitor .

- In the Business Partner Change Monitor , the purchaser The master data is automatically updated in SAP ERP.
triggers the automatic update of master data using the
Transfer Change to Backend button.

Supplier Registration, Supplier Preselection, and Supplier Directory with Separate Registration System

Steps Sub-Steps Results

Supplier registration The purchaser sends an invitation e-mail to a potential -


supplier, or a potential supplier calls up the Web site of the
purchasing company.

- The potential supplier calls up a URL that opens the self- -


registration page in the supplier registration system (ROS
system).

- The potential supplier enters their master data and assigns The potential supplier is registered in the ROS system as
themselves to one or more product categories. a business partner with the Potential Supplier role.

- The potential supplier automatically receives one or more -


questionnaires (a general questionnaire and one
questionnaire for each product category). You can define
which questionnaire to use for which product category in
Customizing for SAP Supplier Relationship Management
under SRM Server Supplier Registration Basic
Settings Assign Questionnaire and Language to
Product Category

PUBLIC Page 27 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
- The potential supplier fills out the questionnaires and The questionnaires are stored in the ROS system.
returns them.

Supplier preselection The purchaser calls up Supplier Preselection in the SRM -


Server system.

- The purchaser reviews the master data and the Accepted potential suppliers appear in the supplier
questionnaires in the ROS system and either accepts or directory.
rejects the potential supplier.

Supplier transfer The purchaser selects a supplier from the supplier Supplier master records are created in the SRM Server
directory in SAP SRM and transfers this supplier into the system. If a supplier in the master data record is flagged as
SRM Server System using OPI. a portal supplier, an XML message is sent to supplier self-
services.
The supplier data is transferred to the Business Partner
Change Monitor (SRM Server) and can be transferred
manually from there to the SAP ERP system.

Supplier enablement The supplier self-services system sends an e-mail with a -


registration number to the supplier.

- The supplier uses the registration number to create a user -


in supplier self-services.

- The supplier can change his or her master data in supplier The changes are transferred to the supplier directory.
self-services.

Data transfer The purchaser sees these changes in the Business -


Partner Change Monitor .

- In the Business Partner Change Monitor , the purchaser The master data is automatically updated in SAP ERP.
triggers the automatic update of master data using the
Transfer Change to Backend button.

Supplier Qualification with SAP ERP


For more information, see Supplier Qualification with SAP ERP.

Prerequisites
You have carried out the necessary configuration steps. See SAP Solution Manager under <project name> Configuration SAP SRM <release> Basic
Settings for Supplier Qualification .

More Information
Business Partner Change Monitor
Supplier Registration
Supplier Directory
Supplier Preselection

1.5.11 Supplier Self-Services

Supplier self-services (SUS) is a solution that reduces the costs of procurement cycles by improving the exchange of business documents and shortening the
time it takes to process the content of these documents. While purchasers use familiar methods to order goods and services, SUS integrates suppliers into the
procurement process to a much larger extent.
Using SUS, suppliers do not need their own systems to supply goods and services, but have direct Internet access to the purchaser's procurement system via a
Web browser. By this means, they are able to rapidly react to order functions received from the host.

Integration
You can use supplier self–services with the following business scenarios:
Service Procurement
SUS is installed separately, and configured to work together with SAP SRM or SAP ERP as procurement system. From a technical aspect, the connection
to SAP SRM represents a standalone scenario with a Financial Accounting (FI) back-end system. Connecting to an SAP ERP system allows the user to
collaborate on purchase orders containing service item hierarchies.
Plan-Driven Procurement with Supplier Integration
SUS is installed separately, and configured to work together with Materials Management (MM) as procurement system. This enables the procurement of
direct materials. From a technical aspect, this represents a classic scenario with one or more MM back-end systems.
In both scenarios, purchasers can enhance their selected procurement system to grant suppliers access to SUS. As of SAP SRM 7.0 and enhancement
package 4 for SAP ERP 6.0, purchase orders, advanced shipping notifications (ASN), invoices, confirmations (service entry sheets), and evaluated receipt
settlement (ERS) invoices (see the following sections) are transferred using the eSOA interface.

More Information
For information on configuration, see SAP Solution Manager under Configuration SAP SRM 2007 Basic Settings for Service Procurement or Basic

PUBLIC Page 28 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Settings for Plan-Driven Procurement

1.5.12 Analytics

You can find information on how to integrate SAP NetWeaver Business Warehouse (SAP NetWeaver BW) reports into SAP NetWeaver Portal in the SAP

NetWeaver documentation on SAP Help Portal at http://help.sap.com SAP NetWeaver SAP NetWeaver <release> Library SAP Library SAP
NetWeaver Library SAP NetWeaver by Key Capability Information Integration by Key Capability Business Intelligence BI Suite: Business Explorer
Integrating Content from BI into the Portal.
You can also use several reports directly in the SAP Supplier Relationship Management (SAP SRM) system without installing an SAP NetWeaver BW system
(see BW-Independent Analytics).

1.5.13 Integration with Collaboration Projects (cProjects)

You can use this process to integrate SAP Supplier Relationship Management (SAP SRM) with cProjects. This enables you to handle your entire purchasing
process for materials and services from sourcing to time and expense recording using cProjects and SAP SRM.
The process is used in the business scenario Service Procurement External Staffing .

Prerequisites
To integrate SAP SRM with cProjects, you have made the necessary configuration settings as described in SAP Solution Manager under Scenarios
Service Procurement External Staffing Business Processes Requesting External Staff .

Process
1. You send an external requirement from cProjects to the SAP SRM sourcing application.
2. The SAP SRM system creates a requirement and sends a confirmation to cProjects.
3. As a purchaser, you process this requirement in the sourcing application and create a purchase order. Alternatively, you create an RFx using SAP Bidding
Engine. The system sends the purchase order number and the item number to cProjects.
4. SAP SRM records the times worked and the expenses incurred and sends them to cProjects. The time recording in SAP SRM is a prerequisite for the
complete mapping of the RFx in cProjects. The time recording in supplier self-services (SUS) cannot be mapped.

More Information

For more information about Collaboration Projects, see SAP Help Portal at http://help.sap.com/ SAP ERP SAP cProject Suite Project and Portfolio
Management Collaboration Projects Integration with Supplier Relationship Management .

1.5.14 Procurement Card Payment Process

In the SAP Supplier Relationship Management (SAP SRM) system, you can specify procurement card as the payment method when purchasing items provided
you are using the Materials Management functions in SAP SRM. In addition, you can manage settlements for purchases made using a procurement card, that is,
you can transfer the settlement file that the bank or card company sends you to the SAP SRM system to check that the contents are correct and specify account
assignments.

Prerequisites
To specify procurement card as payment method:
You must be using the Materials Management functions in the SAP SRM component.
You must have entered your procurement card details using the Create User transaction.
The settlement files are transferred to SAP SRM and invoices and transaction figures are transferred from SAP SRM to the back-end system via the ALE
interface.
You have set up the ALE distribution model in Customizing for SAP SRM and the back-end system.
Menu path in Customizing: Supplier Relationship Management SRM Server Technical Basic Settings ALE Settings (Logical System)
The procurement cards must be set up so that the system can transfer the settlement information from the card company and carry out updates in
Accounting in the back-end system.
You can use the information on the procurement cards to control the postings in Accounting and validate the procurement card numbers on the bank's
settlement file. This information also provides an overview of the cards issued, the assignment of cards to employees and an overview of information such as
the transaction limit or overall limit of a card and the approval workflow.
Menu path in Customizing: Supplier Relationship Management SRM Server Procurement Card
In the back-end system, Accounting should be set up and the card company should be created as a vendor.
If you want to create commitments, you must have specified this in Customizing:
Menu path in Customizing: Supplier Relationship Management SRM Server Procurement Card Manage Commitments

Process

PUBLIC Page 29 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
1. You specify procurement card as payment method when creating a requirement coverage request.
2. The settlement data is transferred to SAP SRM.
3. At the same time, the system generates an invoice for all purchases that were made using a procurement card. The invoice is updated in accounts
payable accounting in the back-end system and blocked for payment. The system can then pay the invoice during the payment run.
4. If the value of purchases made using the procurement card exceeds the value specified in Customizing, the system places a work item in the cardholder's
SAP SRM inbox when updating the invoice. The cardholder checks the purchases made and can change the account assignment if necessary.
5. If you want the manager to monitor expenditure as well, he or she receives a work item in his or her inbox. When the manager has given his or her
approval, the system posts the invoice to a G/L account in Accounting.

Note
The cardholder and the manager cannot reject items. If the settlement data contains errors, you can leave the work item in its current status and take
organizational measures.
The system always generates the invoice.

Result
The transaction figures in Accounting in the back-end system are updated. The system also generates an invoice that it can pay in the payment run.

More Information
See Archiving Procurement Cards for more information.

1.5.15 Archiving

SAP Supplier Relationship Management (SAP SRM) uses the standard SAP Data Archiving component (CA-ARC) for the documents created and managed in
SAP SRM. The process of archiving removes inactive and deleted documents from the database, storing them in compact archive files from which they can be
easily accessed. Archiving allows you to keep your database to a manageable size while observing statutory data retention regulations.
You manage document archiving with the transaction Document Archiving (SARA).

Archiving objects serve as liaisons between the respective document type to be archived and the individual (partial) programs, Customizing settings, database
tables, and so on. You determine what data is to be archived and under what conditions.
You can use the transaction Archiving Objects (AOBJ) to display all archiving objects in SAP SRM and their associated tables. We do not, however,
recommend that you change the predefined settings in the SAP SRM archiving objects, as this can lead to errors in the archiving process.

Note
Archived documents can be displayed but cannot be changed.

You use the SAP SRM document search function to view archived documents, which are displayed in the same way as when they were active in the database.
The following documents, listed with their archiving object codes, can be archived:
Live auctions (BBP_LA)
Approved supplier list (BBP_AVL)
RFx (BBP_BID)
Confirmations (BBP_CF)
Purchasing contracts and global outline agreements (BBP_CTR)
Invoices (BBP_INV)
Mass changes of purchasing contracts and global outline agreements (BBP_MASSOP)
Procurement cards (BBP_PC_ARC)
Purchase order responses (BBP_PCO)
Purchase orders (BBP_PO)
Bids/RFx responses (BBP_QUOT)
Shopping carts (BBP_SC)
SUS advanced shipping notifications (BBP_SUSASN)
SUS confirmations (BBP_SUSCF)
SUS invoices (BBP_SUSINV)
SUS purchase order responses (BBP_SUSPCO)
SUS purchase orders (BBP_SUSPO)
The archiving component can also archive data relevant to workflows, such as process levels and decision sets. Business objects that pass a combined
completion and approval process are related to the history information of that process, and cannot be archived independently. The archive object for each such
business object is extended to cover the tables of the corresponding workflow information.

Constraints
You cannot process or change archived documents. You can only display archived document data and use it in customer programs.
You cannot restore archived data to the database system. Note, however, that as the only documents archived are those of completed business processes,
it is not necessary to restore archived data.
The system searches for archived documents differently to how it searches for active documents. The criteria used to search for archived documents
depend on the selected fields from the document type-specific field catalog.
The document history of an archived document does not display all subsequent documents of the whole document chain, but only the document that directly
follows.

PUBLIC Page 30 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
You cannot call the Live Auction Cockpit from archived auctions. This means that you cannot display historical live auction data for archived auctions (for
example, Chat). We recommend that you set a longer residence time for auctions if it is necessary to keep them active for a longer time.

More Information

For more information about data archiving, see SAP Help Portal at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP
NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Data Archiving (CA-ARC)

1.5.16 Country-Specific Functions

SRM supports the following country-specific functions:


Tax calculation and related nota fiscal functions for Brazil
Tax calculation in the shopping cart for India, based on an extra tax field, jurisdiction code
Entry of payment reference numbers as legally required in Scandinavia and commonly used in Switzerland

Prerequisites
In addition to all standard SRM Customizing settings that your company requires, before you can post any documents in SRM for any of the specifically localized
countries, you need to activate the country-specific business functions. You can can do this in transaction SFW5.
Additional country-specific prerequisites are described in the documentation that follows.

1.6 SRM-MDM Catalog

1.6.1 Catalog Content Management

You can use this business scenario to import and manage product content, make this content available in an MDM data repository, and access it via the Web
browser in your SAP Supplier Relationship Management (SAP SRM) procurement processes.

Prerequisites
You can implement this business scenario with different releases of the relevant application components. However, only certain combinations are valid. For more
information, see:
SAP SRM 7.01 Master Guide on SAP Service Marketplace at http://service.sap.com/instguides
Scenario & Process Component List on SAP Service Marketplace at http://service.sap.com/scl

Process
The business processes run as follows:
1. Managing Content in SRM-MDM Catalog
2. Searching in Catalog Data
3. Managing Service Content in SRM-MDM Catalog
4. Transferring Service Hierarchy from SAP ERP
5. Transferring Service Hierarchy and Non Hierarchical Items from RFx Response in SAP SRM
6. Displaying Flat Services
7. Storing and Displaying Sustainability Information

1.6.2 SRM-MDM Catalog for Product Procurement

You use the SRM-MDM Catalog to search, compare, and procure products from suppliers.
It provides:
Catalog content management functions, such as the import of catalog structures or data, the transfer of catalog items to a procurement application, and
search functions
Procurement catalogs
Supplier catalogs in a Web-based environment
The SRM-MDM Catalog is based on functions provided by SAP NetWeaver Master Data Management (SAP NetWeaver MDM) and bundles together in one
specific application those SAP NetWeaver MDM functions required for catalog content management.
The figure below displays an overview of the SRM-MDM Catalog.

PUBLIC Page 31 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
SRM-MDM Catalog: Overview

Integration
The following table shows the SAP NetWeaver MDM modules included in the SRM-MDM Catalog:

MDM Server MDM Import Manager MDM Business Content

MDM Import Server MDM Workflow MDM Java API

MDM Console MDM Data Manager

Business Scenarios
The search in the catalog repository is integrated with the following SAP SRM and SAP ERP business scenarios:
SAP SRM: Self-Service Procurement
SAP SRM: Service Procurement
SAP SRM: Contract Management
SAP ERP: Purchase Requisition (as of SAP ERP 2005)
SAP ERP: Purchase Order (as of SAP ERP 2005)
SAP ERP: Work Order (SAP Plant Maintenance (SAP PM) / SAP Project System (SAP PS))

Features

Importing and Mapping Catalog Data


Using the MDM Import Manager, you can:
Import data from suppliers such as
Product catalogs
Product hierarchies
The supplier catalogs and product hierarchies can have any format supported by the standard SAP NetWeaver MDM application, such as MS EXCEL,
XML, or content from running database systems such as MS SQL, MS ACCESS, or Oracle. The catalog content is compatible with standard classifications
such as UNSPSC and eClass.
Import product master data, purchasing contracts, and suppliers from SAP SRM
Import purchasing contracts and purchasing info records from SAP ERP
Upload contract data from SAP SRM 2007 and SAP ERP.
For more information, see Import and Mapping of Catalog Data. The system stores contract prices per catalog item together with the contract ID, the amount,
and the contract item category.
Perform a value and key mapping between the supplier's source and the destination structure. Wherever both are in sync, you can auto-map this data. A
matching function ensures that no duplicate data occurs.

Enriching Data from Supplier


Using the MDM Data Manager, you can enrich imported data. For example, you can add images and attachments to records, add new items manually, perform a
mass change, or reassign records to another category.

PUBLIC Page 32 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Approval of Supplier Catalog Data
Using the MDM Workflow Manager, you have a framework for defining workflows. You can create your own workflow rules to establish role-based workflows using
Microsoft Visio 2003 Standard. When designing your workflow, you can use MDM validations and assign the workflow steps to users or roles.

Providing Data for a Web-Enabled Catalog Search


Using the MDM Data Manager, you can determine the necessary parameters for collecting the data for your procurement catalog(s) and making them accessible
on the Web. From the procurement application of the supported business scenarios you can open the SRM-MDM Catalog, select catalog items, and transfer the
data.

Fully Configurable User-Specific Search UI


All aspects of the Search UI are configurable to meet user-specific requirements. See User-Specific Configuration for Product Procurement for more details.

Business Add-In (BAdI) for the Open Catalog Interface (OCI) Outbound Process
SAP Supplier Relationship Management (SAP SRM) provides a BAdI for the OCI outbound process for passing dynamic parameters calculated at runtime. For
example, you can pass a parameter that restricts the set of product items the user is allowed to retrieve in a search.
For more information about transferring additional parameters, see Customizing for Supplier Relationship Management (SAP SRM) under SRM Server
Business Add-Ins (BAdIs) External Web Services (Catalogs, Vendor Lists etc.) Transfer Additional Parameters

Predefined Catalog Repository


The SRM-MDM Catalog includes a predefined data repository for your catalog data. This standard repository comprises the main table Catalog Items and a
number of additional sub-tables, for example, for value lookups or classification.
For more information, see Loading Predefined Repositories for Product Procurement and Extending Predefined Repositories.

Inheritance Levels for Supported Languages


The system enables inheritance levels for the supported languages.

Example
US is to be used as the primary language. FR as the secondary language in case US is unavailable. DE substitutes the secondary language if FR is
unavailable.
On the other hand, the language of your content (the data language in fields and tables, for example) can be in any language supported by SAP NetWeaver
MDM 7.1.

The following table shows the supported languages:

Chinese (ZH) Finnish (FI) Hungarian (HU) Polish (PL) Swedish (SV)

Czech (CS) French (FR) Italian (IT) Portuguese (PT) Thai (TH)

Danish (DA) German (DE) Japanese (JA) Russian (RU) Turkish (TR)

Dutch (NL) Greek (EL) Korean (KO) Slovakian (SK)

English (US) Hebrew (HE) Norwegian (NO) Spanish (ES)

Constraints
The SRM-MDM Catalog component uses SAP NetWeaver MDM technology. However, it does not cover the full scope of functions provided by SAP NetWeaver
MDM.

1.6.3 SRM-MDM Catalog: Service Procurement

You use the SRM-MDM Catalog to search and procure services from suppliers.
It provides:
Uploads of service hierarchies from the SAP Supplier Relationship Management (SAP SRM) RFx
Uploads of service hierarchies from SAP ERP using the transaction MECCM
Upload of service hierarchies and contract details from SAP SRM central contracts
Service procurement catalogs
Web-enabled catalog search
Fully configurable search user interface (UI)
Cart Preview. For more information, see User-Specific Configuration: Shopping Options.
The SRM-MDM Catalog is based on functions provided by SAP NetWeaver Master Data Management (SAP NetWeaver MDM) and bundles together in one
specific application those SAP NetWeaver MDM functions required for the service procurement scenario.
The figure below displays an overview of the upload scenario for service procurement and the service procurement scenario for the SRM-MDM Catalog.

PUBLIC Page 33 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Service Procurement

Legend
XML 1 = Hierarchy structure (headers and outlines)
XML 2 = Service Items (functional location, infolines and free text)
XML 3= Non-hierarchical items (not applicable for service data transferred from SAP ERP)

Integration
The following table shows the SAP NetWeaver MDM components included in the SRM-MDM Catalog for service procurement:

MDM Server MDM Import Manager

MDM Import Server MDM Business Content

MDM Console MDM Java API

MDM Data Manager

Business Scenarios
The search in the catalog repository is integrated with the following SAP SRM and SAP ERP business scenarios:
SAP SRM: Self-Service Procurement
SAP SRM: Service Procurement
SAP SRM: Contract Management

Features
Import of service hierarchies using the MDM Import Manager with SAP Process Integration (SAP PI)
The MDM Import Manager with SAP Process Integration (SAP PI) is used for importing service hierarchies based on the SAP SRM RFx. XML is
supported.
For more information, see Transferring Service Hierarchies from SAP SRM.
Import of service hierarchies from SAP ERP
The transaction MECCM is used for importing service hierarchies from SAP ERP. XML is supported.
Provision of data for a web-enabled catalog search
Using the MDM Data Manager, you can determine the necessary parameters for collecting the data for your procurement catalog and making them
accessible on the Web. From the procurement application of the supported business scenarios you can open the SRM-MDM Catalog, select catalog items,
and transfer the data.
Predefined catalog repository
The SRM-MDM Catalog includes a predefined data repository for your catalog data. This standard repository comprises the main table Catalog Items and a
number of additional sub-tables, for example, for value lookups or classification.
For more information, see Loading Predefined Repositories for Service Procurement.
Fully configurable user-specific search UI
All aspects of the Search UI are configurable to meet user-specific requirements. For more information, see User-Specific Configuration for Service
Procurement.

PUBLIC Page 34 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Inheritance Levels for Supported Languages
The system enables inheritance levels for the supported languages.

Example
US is to be used as the primary language. FR as the secondary language in case US is unavailable. DE substitutes the secondary language if FR is
unavailable.
On the other hand, the language of your content (the data language in fields and tables, for example) can be in any language supported by SAP NetWeaver
MDM 7.1.

The following table shows the supported languages:

Chinese (ZH) Finnish (FI) Hungarian (HU) Polish (PL) Swedish (SV)

Czech (CS) French (FR) Italian (IT) Portuguese (PT) Thai (TH)

Danish (DA) German (DE) Japanese (JA) Russian (RU) Turkish (TR)

Dutch (NL) Greek (EL) Korean (KO) Slovakian (SK)

English (US) Hebrew (HE) Norwegian (NO) Spanish (ES)

Constraints
The SRM-MDM Catalog component for service procurement uses SAP NetWeaver MDM technology. However, it does not cover the full scope of functions
provided by SAP NetWeaver MDM.

Note
Service procurement data can only be uploaded from SAP SRM or SAP ERP.
For more information, see:
Transferring Service Hierarchies from SAP SRM
Transferring Service Hierarchies from SAP ERP

SAP Note 1250442

1.7 Business Packages

This section contains functional information on the following business packages:


Business Package for SAP SRM 7.0 EHP1
You must install and configure this business package to use SAP enhancement package 1 for SAP SRM 7.0. For more information about configuring this
business package, see SAP Solution Manager under <project name> Configuration SAP SRM 7.0 EHP1 Basic Settings for SAP SRM
Business Package for SAP SRM .
Business Package for Supplier Collaboration 4.0
For more information about configuring this business package, see SAP Solution Manager under <project name> Configuration SAP SRM 7.0
EHP1 Basic Settings for SAP SRM Business Package for Supplier Collaboration 4.0 .

1.7.1 Business Package for SAP Supplier Relationship


Management

The Business Package for SAP SRM 7.0 EHP1 is based on the overall solution of SAP enhancement package 1 for SAP Supplier Relationship Management
7.0 (SAP enhancement package 1 for SAP SRM 7.0). Tailored worksets have been defined for all SAP SRM roles based on their specific requirements. These
are made up of iViews of the different SAP SRM components, for example SAP SRM Server and SAP Bidding Engine. In the case of the harmonized roles
belonging to the Procurement Business Package for SAP ERP & SAP SRM, users can also access iViews of SAP ERP components.
Technical Data

Availability SAP NetWeaver 7.0, SP17

Data Source SAP enhancement package 1 for SAP SRM 7.0

Recommended Browser For information about system prerequisites for these components, see SAP Service

Marketplace at http://service.sap.com/pam .

Languages Available DE German


EN English

Support EP-PCT-SRM

Features

PUBLIC Page 35 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
This business package contains content for the following areas:
SAP SRM
Harmonized Procurement for SAP ERP & SAP SRM (Procurement Business Package for SAP ERP & SAP SRM)
SAP SRM on One Client in SAP ERP
SAP SRM, Procurement for Public Sector (PPS)
SAP SRM User Interface Add-On

Note
For documentation relating to the SAP SRM User Interface Add-On, go to help.sap.com under SAP Business Suite SAP Supplier
Relationship Management SAP SRM User Interface Add-On .

Generic Roles
Control Center User (cc_user)
You can use this generic role if you want to give users access to a number of daily tasks under the Home tab of the top-level navigation bar. For more

information about this role, see SAP Help Portal at http://help.sap.com SAP NetWeaver SAP NetWeaver <release> SAP Library SAP
NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability Portal Portal Administration Guide Super
Administration Pre-configured Roles Every User Roles Role: Control Center User (cc_user) .
Roles for Technical Purposes
SRM Portal Toolkit (com.sap.pct.srm.com.ro_srmportaltoolkit)

Recommendation
We recommend that you do not assign two versions of the same role to one user. For example, do not assign Operational Purchaser (which is the role from
SAP SRM 7.0) and Operational Purchaser - EHP1 (which is the role from SAP enhancement package 1 for SAP SRM 7.0) to the same user.

More Information
Portal Concepts

1.7.2 Business Package for Supplier Collaboration 4.0

The Business Package for Supplier Collaboration 4.0 runs on SAP NetWeaver Portal 7.0 to create a self-service, collaborative environment for supplier
companies, hosted by the purchasing organization. Suppliers have access to various supplier-managed transactions, business package content, and processes
related to purchasing through a web-based, interactive gateway. This business package can be connected to SAP ERP back-end systems and other solutions,
such as SAP Supplier Relationship Management (SRM) , SAP Product Lifecycle Management (PLM) , Collaboration Folders (cFolders) , and SAP Supply
Chain Management (SCM) , to provide collaborative planning, sourcing, procurement, content management, and design processes. Information exchange
between a purchasing organization and its supplier companies is quick and effective. Implementation of the Business Package for Supplier Collaboration 4.0
accelerates processes in purchasing by reducing cycle times and improving process efficiency.
For purchasing organizations and suppliers companies, implementing this business package:
Accelerates the procurement process
Reduces errors
Minimizes the risk of supply shortages
Enhances collaboration with suppliers
The specific benefits for supplier companies are:
No investment costs
Shorter sales cycles
Lower warehousing costs
Increased sales transparency
Improved customer relationships

Technical Data

Availability SAP NetWeaver 7.0, SPS15

Data Source SAP Supplier Relationship Management (SRM) 7.0, SP00


SAP Supplier Self-Services (SUS) 4.0
SAP Inventory Collaboration Hub (ICH) 5.0
SAP R/3 ERP 2005 Enhancement Pack 4
SAP NetWeaver 7.0 BI Content Add-On 4
SAP NetWeaver Portal 7.0, SP15
SAP Product Lifecycle Management (PLM)/Collaboration Folders (cFolders)
SAP Supply Chain Management (SCM)

Browser Recommendation For information about system prerequisites for these components, see the Product Availability Matrix on SAP Service

Marketplace at http://service.sap.com/pam .

Languages Available CA Catalan


CS Czech
DA Danish
DE German
EL Greek
EN English
ES Spanish
FI Finnish

PUBLIC Page 36 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
FR French
HE Hebrew
HU Hungarian
IT Italian
JA Japanese
KO Korean
NL Dutch
NO Norwegian
PL Polish
PT Portuguese
RU Russian
SK Slovakian
SV Swedish
TH Thai
TR Turkish
ZF Chinese traditional
ZH Chinese

Support EP-PCT-SRM-SC

1.8 Procurement for Public Sector (PPS)

Procurement for Public Sector (PPS) is tailored to meet the procurement needs of public sector organizations. PPS is based on SAP Supplier Relationship
Management (SAP SRM), in many cases extending and augmenting standard SAP SRM functionality to meet the demands of public sector organizations. PPS
offers cost savings and improved efficiency through seamless integration between the contract management and financial processes, while complying with
international procurement policies and public regulations.

Prerequisites
In SAP ERP, you have activated the Enterprise Extension Public Services (EA-PS) . Depending on the required functions in PPS, you have activated a selection
of the following business functions:

Required Function in PPS Business Function in SAP ERP Available From

Configurable item hierarchies PS_GOVPROC_ITEMTYPES SAP_APPL, SAP ERP 6.0, EHP 3

Shopping cart commitment PS_GOVPROC_SCCMT SAP_APPL, SAP ERP 6.0, EHP 3

Pricing arrangements PSM_GOVPROC_PA EA-PS in SAP ERP 6.0, EHP 3

Period of performance PSM_GOVPROC_JFMIP EA-PS in SAP ERP 6.0, EHP 3

Fast Pay PSM_GOVPROC_JFMIP EA-PS in SAP ERP 6.0, EHP 3

Acceptance period PSM_GOVPROC_JFMIP EA-PS in SAP ERP 6.0, EHP 3

Earmarked funds PSM_PPS_INTEGRATION EA-PS in SAP ERP 6.0, EHP 4

Smart number PSM_PPS_INTEGRATION EA-PS in SAP ERP 6.0, EHP 4

Account assignment distribution PSM_PPS_INTEGRATION EA-PS in SAP ERP 6.0, EHP 4

Incremental funding PSM_PPS_INTEGRATION EA-PS in SAP ERP 6.0, EHP 4

For more information about the individual business functions, see the documentation in the SAP ERP system.
In SAP SRM, you have activated the following business functions:
SRM, Procurement for Public Sector (SRM_PUBLIC_SECTOR_1)
SRM, Cross-Industry Functions (SRM_CROSS_INDUSTRY_1)

Integration

Extended Classic Scenario


PPS procurement documents are created in SAP SRM, and financial processes, such as goods receipt (GR) and invoice receipt (IR), occur in SAP ERP.
Therefore, to be able to take advantage of PPS functionality, you must have SAP ERP installed on your system and activated the extended classic scenario. For
more information about the extended classic scenario, see Technical Scenarios.

Note
The following technical scenarios are not supported for SAP PPS:
Classic scenario (prerequisite for the Service Procurement business scenario)
Standalone scenario
SAP SRM in one client in SAP ERP

SAP Document Builder


You can use SAP Document Builder to create and manage complex procurement documents that are frequently used in public sector organizations to meet legal
requirements. SAP Document Builder is a content-driven, cross-application solution powered by SAP Net Weaver. You can create complex documents, utilizing

PUBLIC Page 37 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
business content from the procurement application, text clauses based on legal regulations, and definable rules. Within PPS, you can create contracts, RFx
documents, and purchase orders with SAP Document Builder.
For more information, see the documentation for SAP Document Builder at SAP xApps SAP Document Builder .

SAP Records Management


SAP Records Management is a document management system that allows you to store electronic records of purchasing documents, follow-on processes, and of
related documentation. It also provides central access to these electronic records at any time. For example, SAP Records Management automatically creates a
record for a purchase order. In the course of the procurement process, data from goods receipts and from invoices is added to the record. Moreover, the record also
contains documentation complementing the procurement data, such as contractual agreements, e-mails, or correspondence with your supplier. Thus, SAP
Records Management supports you in fulfilling your requirements regarding document storage, for example audit requirements.
Within PPS, electronic records can be created automatically for purchase requisitions, RFx documents, purchase orders, and contracts. The system provides
navigation from procurement documents to the related electronic record, as well as from the record in SAP Records Management to the procurement document in
the procurement application.
SAP Records Management is part of SAP NetWeaver. To use SAP Records Management for SAP SRM, you must use an SAP ERP system (minimum SAP
ERP 6.0). SAP does not support that you use the SAP Records Management that is located in the SAP SRM system. For more information, see the Configuration
documentation in SAP Solution Manager under <project name> SAP SRM 7.0 EHP1 Basic Settings for SAP SRM Cross-Application Settings
Integration with other SAP Components Integration with SAP Records Management

Features
For an overview of the functions that are available with Procurement for Public Sector, see the following documents:
Features of SRM, Cross-Industry Functions
Features of SRM, Procurement for Public Sector

More Information
For the technical setup and system landscape information, see the Master Guide for SAP SRM, section on Procurement for Public Sector, at

http://service.sap.com/instguides .

For more information about SAP SRM, see SAP Help Portal at http://help.sap.com SAP Business Suite SAP Supplier Relationship Management .
For more information about SAP SRM and PPS configuration information, see SAP Solution Manager.

PUBLIC Page 38 of 38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.