SAP-SRM7.0 EHP2 -Operational Contract Management

SAP Enhancement Package 2 for SAP Supplier Relationship Management (SAP SRM) 7.0: Operational Contract ManagementBased on SAP Solution Manager Content

Target Audience ■ System Administrators ■ Consultants

PUBLICDocument version: 1.0 – 2011-11-08

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of SAP Solution

Manager. For more information on the SAP Solution Manager content, see SAP Note 1461039.

Version Date Description

1.0 2011-11-08 Initial version

2/66 PUBLIC 2011-11-08

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1461039&_NLANG=en&_NVERS=0

Table of Contents

Chapter 1 Important Information About This Document . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Basic Settings for Contract Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.2 SAP NetWeaver Process Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.2.1 Configuration of PI-Independent Enterprise Services . . . . . . . . . . . . . . . . . . . . 9

2.2.2 SRM, PI-Independent Enterprise Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2.3 Importing Business Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.2.4 Checking Integration Scenarios and Related Interfaces . . . . . . . . . . . . . . . . . . 14

2.2.5 More Information About SAP NetWeaver Process Integration . . . . . . . . . . . . . 14

2.3 Configuring Synchronous Services for Operational Contract

Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.4 Scheduling Reports to Archive or Delete Transactional Data . . . . . . . . . . . . . 15

2.5 Pricing Settings for Purchasing Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.6 Alert Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.6.1 Alert Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.6.2 Making Settings for Contract Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.6.3 Triggering Events for Central Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.7 Setting Up TREX Server and TREX Search . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.8 Workflow Settings for Business Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.8.1 Set Up Workflow for Business Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.8.2 Setting Up Application-Controlled Workflow for Operational Contract

Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.9 Contract Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.9.1 Configuration Options for Operational Contract Management . . . . . . . . . . . . 26

2.9.2 More Information About SRM Integration with ERP . . . . . . . . . . . . . . . . . . . . 27

2.9.3 Making Settings for Central Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.9.4 Making Settings for Back-End Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.9.5 More Information About Contract Configuration . . . . . . . . . . . . . . . . . . . . . . 32

2.10 Settings for Analytics in Contract Management . . . . . . . . . . . . . . . . . . . . . . . 33

2.10.1 Contract Management: Available Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2011-11-08 PUBLIC 3/66

Chapter 3 Operational Contract Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.1 Define Usage of Central Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.1.1 Configuration Content for Defining Usage of Central Contracts . . . . . . . . . . . 35

3.2 Developing Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.2.1 Configuration Content for Developing Contracts . . . . . . . . . . . . . . . . . . . . . . 36

3.2.1.1 Assign General Contract Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.2.1.1.1 Assign General Contract Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.2.1.1.2 Assigning Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.2.1.2 Upload Contract from Another System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.2.1.2.1 Upload Contract from Another System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.2.1.2.2 Define a Condition Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.2.1.2.3 Define an External Number Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.2.1.2.4 Define a Transaction Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.2.1.3 Create Contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.2.1.4 Define Discounts Based on Hierarchical Contract Release Values . . . . . . . . . . 41

3.2.1.5 Activate Contract Upload to Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.2.1.5.1 Setting Up Contract Replication to Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.2.1.5.2 More Information About Activating Contract Upload to Catalog . . . . . . . . . . 42

3.2.1.6 Complete Contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.2.1.7 Approve Contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.2.1.7.1 Smart Form: Form for Offline Approval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.2.1.7.2 Smart Form: Output Form for Contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.2.1.7.3 Smart Form: Form for Output E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.2.1.7.4 More Information About Approving Contracts . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2.1.8 Output Contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2.1.8.1 Enter Contract-Specific Attributes for Output . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2.1.8.2 User Attributes in SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2.1.8.3 Smart Form: Background Processing of Contracts . . . . . . . . . . . . . . . . . . . . . . 52

3.2.1.8.4 Smart Form: Form for Output E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.2.1.8.5 Smart Form: Output Form for Contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.2.1.8.6 More Information About Outputting Contracts . . . . . . . . . . . . . . . . . . . . . . . 54

3.2.1.9 Change Contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.2.1.9.1 Configuring Mass Change Parameters in Contract Management . . . . . . . . . . 54

3.2.1.9.2 Smart Form: Mass Change to Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.2.1.9.3 More Information About Changing Contracts . . . . . . . . . . . . . . . . . . . . . . . . 57

3.3 Processing Contracts and Sourcing Rules in ERP . . . . . . . . . . . . . . . . . . . . . . . 57

3.4 Negotiating Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4/66 PUBLIC 2011-11-08

3.4.1 Configuration Content for Negotiating Contracts . . . . . . . . . . . . . . . . . . . . . . 58

3.4.1.1 Basic Settings for Negotiating Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3.4.1.2 Making Settings for Contract Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3.5 Processing Delivery Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

3.6 Searching for Sources of Supply Centrally . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

3.6.1 Configuration Content for Searching for Sources of Supply

Centrally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

3.7 Monitoring Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

3.7.1 Configuration Content for Monitoring Contracts . . . . . . . . . . . . . . . . . . . . . . 61

3.7.1.1 Smart Form: Event Framework Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

3.7.1.2 More Information About Monitoring Contracts . . . . . . . . . . . . . . . . . . . . . . . 61

2011-11-08 PUBLIC 5/66

This page is left blank for documents that are printed on both sides.

1 Important Information About This Document

The configuration documentation for SAP Supplier Relationship Management (SAP SRM) is delivered

with the SAP Solution Manager content. To implement and configure SAP SRM, you must use SAP

Solution Manager, which contains the complete configuration documentation including links to

Customizing, SAP Notes, and SAP ERP documentation.

This guide contains only the SAP SRM configuration documentation and references to other

documentation. It provides you with a quick overview of the required SAP SRM configuration settings.

CAUTION

This guide is a supplement to the SAP Solution Manager content and does not replace it. The

complete configuration content and tool support is only available in SAP Solution Manager.

For more information on the SAP Solution Manager content, see SAP Note 1461039 and the SAP SRM

master guide at http://service.sap.com/instguides under Installation & Upgrade Guides SAP Business

Suite Applications SAP SRM SAP SRM Server 7.01 .

Business Functions

SAP enhancement package 1 for SAP Supplier Relationship Management 7.0 (SAP SRM 7.0) includes

the following business functions:

■ SRM, Strategic Sourcing Innovations

■ SRM, Catalog Innovations

■ SRM, Approval Process

■ SRM, Continuous Innovations

■ SRM, Implementation Simplification

■ SRM, Service Procurement Innovations

■ SRM, PI-Independent Enterprise Services

■ SRM, Supplier Collaboration

■ SRM, Self-Service Procurement

■ SRM, Analytics

For more information about these business functions, see SAP Help Portal at http://help.sap.com

SAP Supplier Relationship Management Business Functions and Customizing Switches .

1 Important Information About This Document

2011-11-08 PUBLIC 7/66


http://service.sap.com/instguides

http://help.sap.com

2 Basic Settings for Contract Management

2.1 SAP Notes

The following SAP Notes apply:

■ 734060 SRM: Upload and download of documents using MS Excel

■ 609222 Sourcing: Create R/3 contracts, tricks and hints

■ 646903 Global outline agreement: Tips and tricks

■ 859049 SRM 5.0: Restrictions for uploading and downloading

■ 812884 How to change the fields used for Excel upload and download

■ 673479 Excel download: Quantities not displayed correctly

■ 790860 Frequently asked questions for Excel upload and download

■ 1268821 SRM 7.0 / ERP 6.04: Config. of Central Contract Management

■ 1268336 Business Suite 2008: Synchronous peer-to peer Services

■ 1252865 Central Contracts: Search help for Central Contract dumps

■ 1271697 Wrong information in contracts tracking for calloffs

■ 1269289 Portal error appears at CPPR in central contract link

■ 1263470 CCM:Replication of Central Contracts with more than 10 items

■ 1269803 Enter Net Price error for Central Contract

■ 1314597 SRM central contract: Error in price determination Customizing

■ 1270081 Trouble shooting SOA Services

2.2 SAP NetWeaver Process Integration

2.2.1 Configuration of PI-Independent Enterprise Services

PI-independent services use the Web Services Reliable Messaging (WSRM) protocol. For asynchronous

enterprise services with compatible signatures, WSRM enables point-to-point communication between

SAP Business Suite applications.

To use this process, you must have activated the business function Improvements for SOA Reuse Functions

(FND_SOA_REUSE_1) and you must have defined settings in Customizing under Cross-Application

Components Processes and Tools for Enterprise Applications Enterprise Services Point-to-Point Enablement for

Asynchronous Enterprise Services . The business function SRM, PI-Independent Enterprise Services (SRM_WSRM_1)

is then automatically activated.


2.1 SAP Notes

2011-11-08 PUBLIC 9/66

















Process

To configure WSRM, proceed as follows:

Configuring bgRFC (Background Remote Function Call)

Configure bgRFC as described on SAP Help Portal at http://help.sap.com under SAP NetWeaver

Library SAP NetWeaver by Key Capability Application Platform by Key Capabilities Platform-Wide Services

Connectivity Components of SAP Communication Technology Classical SAP Technologies (ABAP) RFC

Background Communication bgRFC (Background Remote Function Call) bgRFC Configuration .

Configuring the Web Service Runtime

Configure the Web service runtime in client 000 as well as in the production client using report

SRT_ADMIN. For more information, see SAP Help Portal at http://help.sap.com under SAP NetWeaver

Library SAP NetWeaver by Key Capability Application Platform by Key Capabilities ABAP Technology ABAP

Workbench ABAP Workbench Tools Web Services Creating Consumers/Providers for the Enterprise Services Repository

7.1 Managing the Web Service Runtime Configuring the Web Service Runtime .

SOA Manager

Use the SOA Manager (transaction code SOAMANAGER) to administer and configure service providers

and consumer proxies in both the SAP Supplier Relationship Management (SAP SRM) system and the

SAP ERP system. For more information about how to use the SOA Manager, see SAP Help Portal at

http://help.sap.com under SAP NetWeaver Library SAP NetWeaver by Key Capability Application

Platform by Key Capabilities ABAP Technology ABAP Workbench ABAP Workbench Tools Web Services

Working with the SOA Manager .

Proceed as follows:

1. Under Technical Administration Profile Management , you create a profile.

NOTE

Ensure that the names of the profiles and the versions are the same for provider and consumer.

2. Under Technical Administration System Connections , you create a provider system and assign a profile

to it.

NOTE

To be able to use the input help, you must have configured the Services Registry correctly.

If this is not the case, you can enter the SLD identifier manually. The SLD identifier is made

up as follows:

<Client>.SystemName.<SID>.SystemNumber.<Installation

Number>.SystemHome.<database host name>

Example: 340.SystemName.QV5.SystemNumber.0020270862.SystemHome.uxdbqv5

The WSIL URL is made up as follows:

http://<host name>:<http port>/sap/bc/srt/wsil?sap-client=<client>

Example: http://uxciqv5.wdf.sap.corp:50050/sap/bc/srt/wsil?sap-client=340



10/66 PUBLIC 2011-11-08

http://help.sap.com

http://help.sap.com

http://help.sap.com

3. Under Service Administration User Account Management , you enter a service user. Ensure that this

service user has sufficient bgRFC authorization in the SAP SRM system.

4. Under Service Administration User Account Management Account Assignment , you assign a user

account to the system connection. You do so for all service interfaces and for all service groups.

5. Choose Service Administration Business Scenario Configuration and proceed as follows:

1. Choose New.

2. In step 1 (General), enter the business scenario name and description.

3. Choose Next.

4. In step 2 (Provider Side), choose Add to enter all relevant inbound services, for example:

■ PurchaseOrderERPConfirmation_In

■ PurchaseOrderERPContractReleaseNotification_In

■ PurchaseRequestERPSourcingRequest_In

■ PurchasingContractERPConfirmation_In

■ PurchasingContractSRMReplicationConfirmation_In

■ RFQRequestSUITERequest_In

■ SupplierInvoiceSUITEContractReleaseNotification_In

■ PurchaseOrderERPRequest_In_V1

5. For each of the services, choose Assign Profile to assign the profile created in step 1.

6. Choose Next.

7. In step 3 (Consumer Side), choose Add to enter the service group /SAPSRM/

SERVICEPROC_CLASSIC.

8. Choose Assign Business Application to assign the provider system created in step 2 to the service

group.

6. You activate the business function Improvements for SOA Reuse Functions (FND_SOA_REUSE_1).

7. You activate the support for point-to point communication. You do so in Customizing for Cross-

Application Components under Processes and Tools for Enterprise Applications Enterprise Services Point-to-Point

Enablement for Asynchronous Enterprise Services Activate Support for Point2Point Communication .

2.2.2 SRM, PI-Independent Enterprise Services

Technical Data

Technical Name of Business Function SRM_WSRM_1

Type of Business Function Enterprise Business Function

Available As Of SAP enhancement package 1 for SAP SRM 7.0

Technical Usage SRM

Application Component SRM Enterprise Services (SRM-EBP-ESA)

Directly Dependent Business Function Requiring Activation in Addition

Improvements for SOA reuse functions (FND_SOA_REUSE_1)



2011-11-08 PUBLIC 11/66

You can use this business function to exchange asynchronous enterprise services between SAP SRM

and SAP ERP by means of the Web Service Reliable Messaging (WSRM) protocol. In this case, an

integration server, for example, SAP NetWeaver Process Integration (SAP NetWeaver PI) is no longer

required and you reduce installation costs.

Prerequisites

You have installed the following components as of the version mentioned:

Type of Component Component Is Needed Only for the Following Features

Software Component SRM_SERVER 701

You have activated the business function Improvements for SOA reuse functions (FND_SOA_REUSE_1) in the SAP

Business Suite Foundation system and defined settings in Customizing under Cross Application

Components Processes and Tools for Enterprise Applications Enterprise Services Point-to-Point Enablement for

Asynchronous Enterprise Services .

Features

For more information, see:

■ Enterprise Services for Cross-System Data Exchange [external document]

■ PI-Independent Enterprise Services [external document]

2.2.3 Importing Business Scenarios

In this section, you transfer the business scenario Operational Contract Management from the SAP Integration

Repository, generate it, and activate it.

Prerequisites

You must have:

■ Defined the business systems for SAP Supplier Relationship Management (SAP SRM) and Materials

Management (MM) in the SAP System Landscape Directory. For more information about SAP

NetWeaver Process Integration (SAP NetWeaver PI), see the SAP Marketplace at service.sap.com/

instguidesNW70.

■ Imported the SAP NetWeaver PI content for SAP SRM into the SAP Integration Repository. See

SAP Note 836200.

Procedure

1. Log on to the SAP Netweaver PI system.

2. Choose Integration Builder: Configuration.

3. In the left pane, select the Objects tab.

4. Choose Service Without Party Business System .



12/66 PUBLIC 2011-11-08


5. Right-click to display the context menu and choose Business Systems Assign Business System . This

opens the wizard.

6. Choose Continue. The wizard guides you through the required steps.

7. Select a business system.

8. You can create communication channels either manually or automatically. You can create them

automatically here. In this case, the systems are applied from the SAP System Landscape Directory

(SLD). Channels must be complete in terms of URLs and authentication information.

9. Choose Finish, and then choose Close.

10. On the main screen, choose Tools Transfer Integration Scenario from Integration Repository . This opens

a wizard.

11. Choose Name using input help Central_Contract_Management (with namespace http://sap.com/xi/

SRM/Basis/Global\IC and component SAP SRM SERVER IC 7.01).

12. Select Continue. The scenario name is Central_Contract_Management.

13. Choose Finish and then choose Close. The Business Scenario Configurator opens automatically.

14. Select Component View.

15. The Select Component View window opens.

16. Choose Apply.

17. Choose Assign Services. The Assign Services to Application Component window opens.

18. Press F4 to retrieve the available services.

19. Choose Assign.

20. Select the related service and choose OK.

21. Assign a business service to all roles.

22. Choose Configure Connections.

23. Select the connections from the Service Assignment tab.

24. Press F4 in the Communication Channel field.

25. Select a communication channel. This channel must be of type XI.

NOTE

■ If the systems are applied from the SAP Landscape Directory, the Integration Builder

automatically creates the communication channels.

■ If the systems are not applied from the SAP Landscape Directory, you create

communication channels manually. To do this, choose an existing service and then

Communication Channel using context menu New. You must assign a communication channel

for each connection.

26. Choose OK and then choose Apply.

27. Choose Generate to open the Create Configuration Objects window.

28. Select Simulation, then Generate, then mark all in the list Scope of Generation.

29. Choose Start to generate a log. Check the log for errors and save it if required.

30. In the Close Integration Scenario screen, choose Apply.



2011-11-08 PUBLIC 13/66

31. In the left pane, select the Scenarios tab; your scenario has been added.

2.2.4 Checking Integration Scenarios and Related Interfaces

In this section, you check the integration scenario to which the Contract Management business scenario is

assigned and the interfaces that are used for communication between SAP Supplier Relationship

Management and Materials Management. For the Contract Management business scenario, the

Central_Contract_Management integration scenario provides the following interfaces, which you

can check in the Integration Builder:

Supplier Relationship Management Direction Materials Management

PurchasingContractSRMReplicationRequest_Out Asynchronous call (consumer)

PurchasingContractSRMReplicationRequest_In

PurchasingContractSRMReplicationConfirmation_In Asynchronous call (provider)

PurchasingContractSRMReplicationConfirmation_Out

PurchaseOrderSRMPricingSimulateQueryResponse_In Synchronous call (provider)

PurchaseOrderSRMPricingSimulateQueryResponse_Out

PurchaseOrderERPContractReleaseNotification_In Asynchronous call (provider)

PurchaseOrderERPContractReleaseNotification_Out

PurchasingContractSRMArchivingCheckQueryResponse_Out Synchronous call (consumer)

PurchasingContractSRMArchivingCheckQueryResponse_In

SupplierInvoiceSUITEContractReleaseNotification_In Asynchronous call (provider)

SupplierInvoiceSUITEContractReleaseNotification_Out

Procedure

1. Start the SAP Integration Builder.

2. Choose Integration Builder: Configuration.

3. Under the Scenario tab, expand the scenario to display detailed information.

2.2.5 More Information About SAP NetWeaver Process Integration

The following SAP notes apply:

■ 1286936

■ 884695

Perform the following activity in Customizing for SAP Supplier Relationship Management under:

SRM Server Activate Business Functions .

Run the following transactions in the SAP SRM system:

■ User Maintenance (SU01)



14/66 PUBLIC 2011-11-08



■ Role Maintenance (PFCG)

■ Start Integration Builder (SXMB_IFR)

■ HTTP Service Hierarchy Maintenance (SICF)

2.3 Configuring Synchronous Services for Operational Contract Management

You can configure the following synchronous services to exchange contract information between SAP

Supplier Relationship Management (SAP SRM) and SAP Enterprise Resources Planning (ERP):

■ PurchaseOrderSRMPricingSimulateQueryResponse_In

Using this service, the SAP SRM system receives a request from the SAP ERP system or another

back-end system to calculate a price. After calculating the price, the SAP SRM system returns the

conditions and any error information.

■ PurchasingContractSRMArchivingCheckQueryResponse_Out

Using this service, the SAP SRM system requests from the SAP ERP system or another back-end

system the archiving status of the purchasing contract created from an SAP SRM contract.

For more information about the above-mentioned enterprise services, see SOA SAP SRM on SAP

Help Portal at http://help.sap.com.

From a more practical point of view, SAP Note 1268336 provides detailed information on how to

configure synchronous services, whereas SAP Note 1270081 lists possible configuration issues and

describes how they can be solved.

Procedure

Run transaction SOA Manager (SOAMANAGER) to configure the services.

2.4 Scheduling Reports to Archive or Delete Transactional Data

You can schedule report BBP_CONTRACT_MASS_UPDATE to archive and delete mass change work

packages.

NOTE

Each time a user makes a change in the Perform Mass Changes function, a work package is created in

the system. This work package contains the following data:

■ Selected contract(s)

■ Mass change methods and filters

■ Messages that occurred during the simulation step (if carried out)


2.3 Configuring Synchronous Services for Operational Contract Management

2011-11-08 PUBLIC 15/66

http://help.sap.com



Use the transactions SM36 (Scheduling Background Jobs) or SM36WIZ (Job Definition Wizard) to schedule

the report.

EXAMPLE

For example, you want to run a weekly report to archive and delete work packages that are

more than 7 days old.

To do this, create and save a report variant WEEKLY with the action type Archive WP(s)

deactivated. Set the parameter WP Older Than to 7 to keep work packages created during the

previous week. Similarly, you can set WP Older Than to 14 if you want to keep work packages

created in the previous two weeks.

2.5 Pricing Settings for Purchasing Contracts

Perform the following activities in Customizing for SAP Supplier Relationship Management (SAP SRM)

under SRM Server Cross-Application Basic Settings Pricing :

■ Process Condition Types

■ Process Calculation Schema

■ Process Condition Groups

■ Check Technical and Customizing Settings for Conditions

Prerequisites

You have worked out a blueprint for the pricing structure you want to use in your purchasing contracts,

for example, how your gross prices and your rebates are to be calculated.

For more information, see SAP Help Portal at http://help.sap.com under SAP Supplier Relationship

Management Functions Global Functions Pricing .

2.6 Alert Settings

2.6.1 Alert Management

In SAP Supplier Relationship Management (SAP SRM), the Alert Management function allows you to

monitor business processes in your SAP SRM system. If events cause changes, the system evaluates

them and triggers alerts, messages, or tasks to inform the responsible employees, who can then react

quickly and directly.

Prerequisites

You have completed the configuration steps described in SAP Solution Manager under <project name>

Configuration Structures SAP SRM <release> Basic Settings for SAP SRM Cross-Application Settings Alert

Framework .

In particular, you have performed the following Customizing activities:


2.5 Pricing Settings for Purchasing Contracts

16/66 PUBLIC 2011-11-08

http://help.sap.com

■ Define Events

■ Define Event Schema

Integration

Alert Management is composed of functions from the SAP standard component Alert Management

but offers extended functionality. Alerts are processed and distributed using the Alert Framework. By

default, notifications and alerts are transmitted by e-mail, but it is also possible to view alerts in the

universal worklist (UWL) under the Alerts tab.

More Information

For more information, see the SAP Help Portal under http://help.sap.com SAP NetWeaver <release>

Library SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability

Business Services Business Communication Services Alert Management (BC-SRV-GBT-ALM) .

2.6.2 Making Settings for Contract Alerts

You can specify default alert thresholds for contract expiry dates, release quantities, and release values

in Customizing for SAP Supplier Relationship Management (SAP SRM). When a contract is created,

the default thresholds are then copied to the contract. However, users can define specific alerts for a

specific contract by overwriting the default values in that contract.

Prerequisites

You have defined transaction types in Customizing for SAP SRM under SRM Server Cross-Application

Basic Settings Define Transaction Types .

Procedure

To create default alert threshold values for a contract, in the Customizing activity Enter Threshold Data

for Contracts, proceed as follows:

1. Choose New Entries.

2. Select a transaction type from the dropdown list, for example, CCTR for a central contract.

3. Enter the alert thresholds (as a percentage) for the release value of a contract for both header and

item level. For example, if you want the system to alert the user when the release value of a contract

at header level has reached 95% of the target value, enter 95 in the Header Val. column.

4. Enter the number of days before which a contract will expire. For example, if you want the system

to alert the user that the contract is due to expire in 100 days, enter 100 in the Exp. Days column.

5. Enter the alert threshold (as a percentage) for the release quantity of a contract. For example, if

you want the system to alert the user when the release quantity of a contract has reached 95% of

the target quantity, enter 95 in the Item Qty column.


2.6 Alert Settings

2011-11-08 PUBLIC 17/66

http://help.sap.com

Result

Once the contract has been created, the report BBP_CONTRACT_CHECK checks the values taken

from the contract (or, if the values are not found in the contract, from this Customizing table) against

the current status of the contract. When a threshold is exceeded, an alert is triggered and the purchaser

is informed via e-mail if, for example:

■ The validity of the contract has almost expired.

■ The release quantity is approaching the target quantity.

■ The release value is approaching the target value (at both header and item level).

2.6.3 Triggering Events for Central Contracts

To use events with central contracts, you need to define the events that trigger actions and bundle

events used for an object type in event schemas. You also define here whether the events are used later

to trigger alerts or messages in SRM Alert Management (Event Category). You assign alert categories

to the alert events (Subcategory of the Events) and you define the event deadline after or before which

an alert or message is sent.

Prerequisites

You have defined transaction types in Customizing for SAP Supplier Relationship Management (SAP

SRM) under SRM Server Cross-Application Basic Settings Define Transaction Types .

You have processed event schemas, chosen event categories, assigned subcategories of events, and

defined event deadlines in Customizing for SAP SRM under SRM Server Cross-Application Basic Settings

Event and Event Schema for Alert Management .

You have defined the recipient of notifications in Customizing for SAP SRM under SRM Server Cross-

Application Basic Settings Event and Event Schema for Alert Management Define Recipient of Notifications .

NOTE

You can define your own events and overwrite existing (delivered) events using the Business Add-

In (BAdI) Alerts/Messages and Events in SRM Alert Management (BBP_ALERTING). You can implement

this BAdI in Customizing for SAP SRM under SRM Server Business Add-Ins Alerts/Messages and

Events in SRM Alert Management .

Procedure

Changing the event texts for central contracts

You can change the event texts for central contracts in Customizing for SAP SRM under SRM Server

Cross-Application Basic Settings Event and Event Schema for Alert Management Define Events . Proceed as

follows:

1. In the dialog structure, choose Event Objects.

2. Select the object type BUS2000113.


2.6 Alert Settings

18/66 PUBLIC 2011-11-08

3. In the dialog structure, choose Event Definition.

4. The system displays all events delivered by SAP SRM for the contract, together with their texts.

By default, the text A contract is approaching the value limit is assigned to the event

GOING_TO_EXPIRE. You can change this text to suit your requirements.

Establishing events for central contracts

You can establish events for central contracts in Customizing for SAP SRM under SRM Server Cross-

Application Basic Settings Event and Event Schema for Alert Management Define Event Schema . Proceed as follows:

1. In the dialog structure, choose Event Objects.

2. Select the object type BUS2000113.

3. In the dialog structure, choose Event Schema.

4. The system displays all events delivered by SAP SRM for the contract, together with their texts.

5. Define an event schema that bundles the events used for the contract.

6. Determine whether the events should subsequently trigger alerts or messages in SRM Alert

Management (Event Category).

7. Assign alert categories to the alert events (Subcategory of the Events) and define the event deadline

after or before which an alert or message is sent.

8. Define who is to receive inbox notifications when an alert is triggered for a contract that is about

to expire. For example, the creator of the contract could receive information on the contract, and

the action required, in his or her inbox.

2.7 Setting Up TREX Server and TREX Search

The settings described below enable the full text search for documents (supplier texts, internal notes,

or attachments) in the Contract Management application of SAP SRM.

Documents indexing is done initially with report BBP_TREX_INDEX_ADMIN. Once full-text search

is enabled, documents are automatically indexed by the SAP SRM application when saving new or

updated documents.

Prerequisites

■ You have installed the TREX Server. For more information, as well as the necessary configuration

activities, see SAP Solution Manager under Basic Configuration Configuration Structures SAP

NetWeaver 7.0 (2004s) Standalone Engines Search and Classification (TREX) .

■ After installing the TREX Server you have completed the following:

● You have set up the TREXPreprocessor.ini file and protected the file against unauthorized

access (since it contains user and password data) by adding the following information after

the [httpclient] section:

#basic authent

user=<user for SRM Server>


2.7 Setting Up TREX Server and TREX Search

2011-11-08 PUBLIC 19/66

password=<password for SRM Server user>

● After manually adding entries to the TREXPreprocessor.ini file you have restarted the TREX

preprocessor.

Procedure

Creating RFC Destination and Defining Back-End

1. Using transaction SM59, create an RFC destination with TCP/IP connection for the TREX server.

NOTE

Only use one RFC destination for TREX. SAP SRM supports only one TREX Server, although

it is technically possible to specify several RFC destinations for TREX.

2. In Customizing for SAP Supplier Relationship Management, define a back-end system for the

TREX server by choosing SRM Server Technical Basic Settings Define System Landscape .

Specify a logical system (you can enter any key, such as TREX), an RFC destination (the one you

created in step 1), and assign system type TREX search tool.

For more information, see Defining RFC Destination and Back-End System [external document].

Activating Full Text Search in SAP SRM Application

Run report BBP_TREX_INDEX_ADMIN using the action parameter A .

To enable the display of the corresponding field for TREX text searches in documents of SAP SRM

purchase contracts, you must run the report using parameter A at least once.

For more information, see the documentation of report BBP_TREX_INDEX_ADMIN in your SAP

SRM system.

NOTE

If you are using the Invoice Management System (IMS), you have to run the report

BBP_TREX_INDEX_ADMIN for the business object Invoice.

2.8 Workflow Settings for Business Scenarios

2.8.1 Set Up Workflow for Business Scenarios

You use this process to set up the workflow for your business scenario. The configuration steps depend

on the workflow framework you use. SAP Supplier Relationship Management (SAP SRM) supports

the following workflow frameworks:

■ Process-controlled workflow framework

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 (BRF) can be applied to control further the process flow.



20/66 PUBLIC 2011-11-08

The process-controlled workflow framework is the default framework in the SAP SRM system.

■ Application-controlled workflow framework

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.

The application-controlled workflow framework is the framework that was available in SAP SRM

5.0 and lower. It is only intended to be used if you are upgrading from SAP SRM 5.0 or lower and

you need to continue using your existing workflows.

For more information about the workflow frameworks, see SAP Help Portal at http://

help.sap.com under SAP Supplier Relationship Management Functions Business Workflow .

Prerequisites

You have performed the basic workflow Customizing as described in SAP Solution Manager under

<project name> Configuration SAP SRM <release> Basic Settings for SAP SRM Cross-Application Settings

Business Workflow .

Process

Perform the following steps:

■ Check which workflow framework is active in your system. To do so, go to Customizing for SAP

SRM under SRM Server Cross-Application Basic Settings Business Workflow Select Workflow

Framework . Select Show Current Settings and choose Execute.

■ If your workflow framework is the process-controlled workflow framework, you do not have

to perform any scenario-specific Customizing steps. All Customizing steps necessary for this

workflow framework are described in SAP Solution Manager under <project name> Configuration

SAP SRM <release> Basic Settings for SAP SRM Cross-Application Settings Business Workflow Process-

Controlled Workflow .

■ If your workflow framework is the application-controlled workflow framework, check

whether there is any workflow documentation specific to your scenario in addition to this

document in SAP Solution Manager. For example, you might have to activate certain workflow

templates, adjust the start conditions for the relevant workflows, or implement a Business Add-

In (BAdI). For general configuration information, see SAP Solution Manager under <project name>

Configuration SAP SRM <release> Basic Settings for SAP SRM Cross-Application Settings Business

Workflow Application-Controlled Workflow .

More Information

The following scenario-specific workflow documentation is available in SAP Solution Manager under

<project name> Configuration SAP SRM <release> :

■ Basic Settings for Service Procurement External Staffing Other Settings Workflow Settings for Business

Scenarios



2011-11-08 PUBLIC 21/66

http://help.sap.com

http://help.sap.com

■ Basic Settings for Strategic Sourcing General Settings Workflow Settings for Business Scenarios

■ Basic Settings for Contract Management General Settings Workflow Settings for Business Scenarios

2.8.2 Setting Up Application-Controlled Workflow for Operational Contract Management

If you use application-controlled workflows, you have to perform some standard Customizing for SAP

Business Workflow. For more information, see Customizing for SAP Supplier Relationship

Management (SAP SRM) under SRM Server Cross-Application Basic Settings Business Workflow

Application-Controlled Workflow Technical Configuration . Then choose

■ Customize SAP Business Workflow Automatically

■ Activate Standard Tasks

NOTE

If the workflow does not work as expected, see SAP Note 322526 (Analysis for Workflow

Problems).

Prerequisites

You have created your organizational structure. We recommend that you map your enterprise

structure at least at departmental level. See Creating the Organizational Plan [external document].

Before you can assign processors to standard tasks, you must have created the relevant users or

regenerated the roles, as appropriate. See Regenerating Role Profiles [external document].

You have performed the basic Customizing for application-controlled workflow described in Setting Up

Business Workflow for Application-Controlled Workflow [external document].

Procedure

1. In Customizing for SAP SRM, choose SRM Server Cross-Application Basic Settings Business Workflow

Application-Controlled Workflow Technical Configuration Perform Task-Specific Customizing .

2. Expand the SRM and the SRM-EBP folders. Find folder SRM-EBP-WFL and click Activate Event

Linking for this folder.

3. Activate the event linkage for the following workflows:

Business Object

Triggering Events Workflows Belonging to Business Object

Event Linkage (by Default) Activated

Start Conditions (by Default) Activated 1) 2)

BUS2000113 (Contract)

SAVED/ CHANGEVERSIONSAVED

WS14000086 (auto approval) WS14000088 (one-step approval)

YesNo

NoNo

BUS2200 (RFx) SAVED/ CHANGEVERSIONSAVED

WS14500026 (auto approval)

Yes No



22/66 PUBLIC 2011-11-08

WS14500027 (one-step approval)

No No

BUS2202 (Supplier Quote)

TOBEACCEPTED WS79000010 (auto approval)WS79000002 (one-step approval)

YesNo

NoNo

1) Start condition activation is required if several workflows are assigned to the same business object and triggering event.

2) If you activate a start condition, the event linkage of the related workflow is activated automatically.

Workflow WS14500051 (generic workflow for SAP SRM alerts) is triggered by the event

APPROVAL_NOT_PROCESSED, providing that a deadline has been specified in Customizing for

Alert Management (Define Event Schema). (This workflow monitors approval workflows, and triggers

an alert/message if no approval has been granted when the deadline passes.) Activate this workflow

if you want to use SAP SRM Alert Management.

CAUTION

If an event linkage is activated and the corresponding start condition is not activated, the

workflow is started every time the event occurs (and the start condition rules are not

followed).

The following workflows are optional:

Business Object (BO)

Triggering Events Workflow Template

Event Linkages (by Default) Activated?

Start Conditions Required? 3)

BUS2000113 (Contract)

ALERTBUSINESSWAREHOUSESAVED/ CHANGEVERSIONSAVED

WS10400022 (contract alert)WS14000148 (n-step approval)

NoNo

NoYes 3)

BUS2202 (Supplier Quote)

TOBEACCEPTED WS14500044 (n-step approval)

No Yes 3)

BUS2200 (RFx) EXTERNALAUCTIONSTARTEDSAVED/ CHANGEVERSIONSAVED

WS14000091 (alert workflow)WS14500028 (n-step approval)

NoNo

NoYes 3)

3) Create and activate start conditions if several workflows are assigned to the same business object and triggering event.

4. If you use the standard approval workflows, define the conditions under which the workflows are

started.

NOTE

The start conditions are shipped by SAP by default in such a way that the workflows are

executable. However, you can change the start conditions to fit your requirements. For more

information, see Customizing for SAP SRM under SRM Server Cross-Application Basic Settings



2011-11-08 PUBLIC 23/66

Business Workflow Application-Controlled Workflow Business Process Configuration Define Conditions

for Starting Workflows .

CAUTION

The delivered or changed start conditions must be activated before the workflow runs.

NOTE

If multiple approval workflow types are activated for a specific procurement scenario (using

event linkage), you must prevent these workflows from starting simultaneously. You do this

by activating the delivered start conditions or by defining your own start conditions. We

recommend that you modify the delivered start conditions to suit your requirements. If you

define new start conditions, bear in mind that the start condition editors use Boolean logic

rules. This means that a status that is defined in a start condition will appear in its inverse

form in the other start conditions. This ensures that the other condition always shows False

when the first one shows True.

5. Assign processors to some standard tasks.

If you want a certain group of persons to be able to approve your work items, you must specify all

possible processors for the task in question. For example, tasks TS10008069 and TS10008127 for

standard two-level approval and task TS10008126 for single-level approval. These tasks are assigned

to the manager role. If required you can, however, specify these processors differently.

Assign a processor to the tasks in the table in Customizing for SAP SRM, under SRM Server

Cross-Application Basic Settings Business Workflow Application-Controlled Workflow Technical

Configuration Perform Task-Specific Customizing .

Expand the SRM and the SRM-EBP folders. Find folder SRM-EBP-WFL and click the Assign Agents

hyperlink for this folder.

The following tasks are required for Contract Management:

Task (Description) Used/Usable in Workflow Processor (Type of Task Agent Assignment)

TS10407926 (CTR Check in alert workflow)

WS10400022 General task

TS14007969 (Approval task in one-step approval of CTR)

WS14000088 Manager role or general task

TS14507918 (Send contract back to creator)


TS14507919 (Check contract by reviewer)


TS14507920 (Approval task to add to approval of CTR)


TS14507922 (Approval task for one-step approval of RFx)


TS14507924 (Approval task to add to approval of RFx)




24/66 PUBLIC 2011-11-08

TS14507925 (Check RFx response by reviewer)


TS14507928 (Return RFx to creator) WS14500028 General task

TS14507930 (Approval task to add to approval of RFx response)


TS14507931 (Check RFx response by reviewer)


TS14507935 (Approval task in n-step approval of RFx response)


TS14507937 (Return RFx response to creator)


TS79007914 (Approval task in one-step approval of RFx response)

WS79000002 Manager role

For more information, see Technical Information on Standard Workflows [external document].

6. You need to specify who is to be authorized to change or insert the approver or reviewer. You do

this by specifying the possible processors in the workflow template (transaction PFTC_CHG:

Additional Data Agent Assignment Maintain ). This affects the following workflows in SAP SRM

that are relevant to Contract Management:

■ WS14000086 – Auto approval of contract

■ WS14000088 – One-step approval of contract

■ WS14000145 – N-step approval of contract

■ WS14500026 – Auto approval of RFx

■ WS14500027 – One-step approval of RFx

■ WS14500028 – N-step approval of RFx

■ WS14500044 – N-step approval of bid

■ WS79000002 – One-step approval of bid

■ WS79000010 – Auto approval of bid

Approvers or reviewers who can be inserted

Here, you specify who may be inserted as an approver/reviewer in the above workflows:

■ WS14500010 – Approval fragment to insert in approval of contract

■ WS14500022 – Approval fragment to insert in approval of RFx

■ WS14500040 – Approval fragment to insert in approval of bid

RECOMMENDATION

We recommend that you restrict the processors (that is, the approvers or reviewers that

can be inserted) at this point, and specify the relevant workflow tasks and general tasks

instead (see table above).

For more information, see Customizing for SAP SRM under SRM Server Cross-

Application Basic Settings Business Workflow Application-Controlled Workflow Technical

Configuration Perform Task-Specific Customizing .



2011-11-08 PUBLIC 25/66

2.9 Contract Configuration

2.9.1 Configuration Options for Operational Contract Management

The following provides a short overview regarding the standard and alternative configurations for

central contracts. It outlines the use of Business Add-Ins (BAdIs) available for Operational Contract

Management in SAP Supplier Relationship Management (SAP SRM) and in the back-end systems.

NOTE

When creating a central contract from the sourcing application of SAP SRM or from SAP Bidding

Engine, the system uses the following logic:

■ It first checks whether the CT_PROC_TY attribute is maintained in the organizational plan.

If so, the attribute determines the transaction type CCTR or the customer-defined transaction

type for central contracts.

■ If no attribute exists, the system checks the transaction type settings for follow-on documents.

For more information, see Customizing for SAP SRM under SRM Server Cross-Application

Basic Settings Define Transaction Types .

■ If the transaction type settings are not available, the system uses the first transaction type for

contracts that exists in the BBPC_PROC_TYPE table.

Process Alternatives

Alternative 1

If a contract is to be created directly in the back-end system (with no copy in SAP SRM), you need to

implement and activate the BAdI BBP_DETERMINE_LOGSYS. This allows you to determine, for

example, whether contracts of certain purchasing organizations are to be created directly in a back-

end system or in SAP SRM.

You have two optional BAdIs at your disposal to change the data before actually creating a contract in

the back-end system:

■ BBP_CTR_BE_CREATE in the SAP SRM system

■ BBP_CTR in the SAP ERP back-end system

Alternative 2

By default, the system creates a central contract from the sourcing application in SAP SRM or from

SAP Bidding Engine, depending on Customizing. You can distribute the central contract to one or

more back-end systems. For more information, see Making Settings for Back-End Contracts [page 27].

More Information

For more information, see Making Settings for Central Contracts [page 27].



26/66 PUBLIC 2011-11-08

2.9.2 More Information About SRM Integration with ERP

For more information about SRM integration with ERP, see SAP Help Portal at http://

help.sap.com SAP ERP SAP ERP Enhancement Packages ERP Central Component Enhancement Package 5

(Release: SAP enhancement package 5, SP04, for SAP ERP 6.0, incl. SPS 19) English Business Functions (SAP

Enhancement Package 5 for SAP ERP 6.0) Business Functions in SAP ERP Enterprise Business Functions Logistics

Materials Management Procurement - SRM Integration 2 .

2.9.3 Making Settings for Central Contracts

SAP Supplier Relationship Management (SAP SRM) provides all relevant settings for central contracts.

If you want to use your own contract types and these are different from the default (CCTR) ones

included in the standard shipment, you need to create corresponding transaction types and provide

the number ranges.

If you want to transfer local contract data to an SAP catalog, you must specify a back-end system for

the catalog in the back-end destination table.

Procedure

Activity Description Path in Customizing for SAP SRM

Maintaining transaction types

This setting controls the processing of a specific business transaction.We recommend that you use the standard transaction type as shipped.

SRM Server Cross-Application Basic Settings Define Transaction Types

Maintaining number ranges for central contracts

This setting is mandatory. SRM Server Cross-Application Basic Settings Number Ranges SRM Server Number Ranges Define Number Ranges for Purchase Contracts

Configuring the transfer of contract data to the SAP catalog

To enable the transfer of contract data to the SAP catalog, define a table entry in table BBP_BACKEND_DEST that uses system type catalog.This setting is mandatory if you want to transfer local contracts to the SAP catalog.Only if you specify a catalog system in this activity will the contract management application in SAP SRM enable the function Distribute Contract to catalog on the user interface.

SRM Server Technical Basic Settings Define System Landscape

Defining the catalog

To be able to use the catalog, you must first define it in Customizing.

SRM Server Master DataContent Management Define

External Web Services

2.9.4 Making Settings for Back-End Contracts

This section describes the steps for configuring how back-end contracts are created when you are

working in SAP Bidding Engine or in Sourcing. The Business Add-In (BAdI)



2011-11-08 PUBLIC 27/66

http://help.sap.com

http://help.sap.com

BBP_DETERMINE_LOGSYS controls back-end system determination. The contracts are transferred

to the back-end system by RFC. From a technical point of view, IDocs are processed in the back-end

system. From SAP enhancement package 4 for SAP ERP 6.0, the system distributes the contracts using

enterprise services.

The back-end process results in one contract, which is available for price and source determination.

For more information about the creation of back-end contracts, see SAP Note 609222. For an overview

on how you can configure contract management across the SAP SRM and back-end systems, see

Configuration Options for Operational Contract Management [page 26].

Prerequisites

SAP SRM

■ You have defined an RFC destination for the back-end system and you have defined the back-end

system in which you want to create contracts. For more information, see Defining RFC Destination

and Back-End System [external document]. If you have already defined a back-end system (FI) as a

destination in another business scenario, you can use this destination for back-end contracts also.

■ You have defined the transaction type for purchasing contracts. This must exist in SAP SRM, and

the internal number range for this must be identical to the external number range in the back-

end system.

For more information, see Customizing for SAP SRM under SRM Server Cross-Application Basic

Settings Define Transaction Types

If you do not use the same transaction type in SAP SRM and the back-end systems, you must map

this data manually using BAdIs (see Configuration Options for Operational Contract Management [page 26]).

For further details refer to step 4 of the Setting Up Organizational Data and Mapping (Master) Data procedure

(see below).

■ You have set up the condition types for pricing conditions. These can be the same as in the back-

end system. If you have used a different technical name in SAP SRM, you have made sure that all

other settings are identical to those in the back-end system.

● You have to ensure that the conditions specified in Customizing in SAP SRM and each of the

corresponding back-end systems are consistent. This means that a condition type in SAP SRM

has the same technical attributes as the corresponding condition type in the back end. If you

do not use the same name, your SAP SRM condition types need to be mapped to your back-

end condition types. You can map the condition types in Customizing for SAP ERP under

Integration with Other mySAP.com Components Supplier Relationship Management Central Contract

Assignment of Conditions .

● You have defined the point in time when current prices in SAP SRM are decided in Customizing

for SAP ERP under Integration with Other mySAP.com Components Supplier Relationship Management

Central Contract Price Calculation .



28/66 PUBLIC 2011-11-08

● You have two possibilities to achieve the required consistency. You can create your own

condition types in SAP SRM and customize them in the same way as the original back-end

condition types. However, this may become difficult if you use more than one back-end system,

since their Customizing can differ. Alternatively, you can create new condition types in the

back-end system and customize them in the same way as the SAP SRM condition types. In

Customizing for SAP SRM, choose SRM Server Cross-Application Basic Settings Pricing .

● Finally, you have to ensure that the back-end condition Customizing, including calculation

schema and calculation schema determination, is consistent and working properly. You can

test the back-end condition Customizing by manually creating a contract in the back-end

system (which uses the same condition types that you receive via Central Contract from SAP

SRM), and creating a purchase order with relation to this contract.

Back-End System

■ Release 4.6B or higher with Plug-In 2004.1

■ Number range object BBP_SRV and internal number assignment for service items

■ External number range for purchasing contracts

■ You have worked through IDoc Customizing.

NOTE

You are using synchronous IDs and settings in SAP SRM and back-end systems for:

■ Master data, such as products, product categories, and suppliers

■ Other data, such as currencies, payment terms, text IDs, transaction types, and condition types

RECOMMENDATION

We recommend that you replicate master data, such as products, product categories and

suppliers from the back-end system. See Downloading Business Objects [external document].

Constraints

For external requirements, the scenario does not support the following:

■ Contract limits

■ The assignment of back-end sources of supply (contract, purchasing info record)

Procedure

Procedure in SAP SRM

Determining Contracts to Be Created in the Back-End System

Transaction Code SPRO

Customizing Path SRM Server Business Add-Ins Shopping Carts and Requirement ItemsDetermine Backend System / Company Code

Set up Business Add-In BBP_DETERMINE_LOGSYS and implement the method

CONTRACT_LOGSYS_DETERMINE so that contracts are created in the back-end system.



2011-11-08 PUBLIC 29/66

■ If you want to create back-end contracts only, all you need to do in the BAdI method is to specify

the parameter for the logical system.

■ If you want to create back-end and local contracts, you must define an algorithm that decides

when to create a local and when to create a back-end contract, as you can only create either a local

or a back-end contract from the sourcing application in SAP SRM or from a winning bid in SAP

Bidding Engine.

EXAMPLE

You can implement the method, for example, so that only back-end contracts of specific

purchasing organizations are created. For assistance, refer to the sample program code in

transaction SE18.

Determining the Transaction Type for Back-End Contracts

Do one of the following:

■ In the organizational plan, assign the CT_PROC_TY attribute (for example, CCTR) to the

responsible purchasing group. See Creating the Organizational Plan [external document].

■ In the Business Add-In Create Contract in back-end System (BBP_CTR_BE_CREATE), implement

method CONTRACT_PROCESS_TYPE_FILL, enter a value in field EV_PROCESS_TYPE.

In Customizing for SAP SRM, choose SRM Server Business Add-Ins Follow-On Document Generation

in the Back-End System Create Contract in Back-End System .

Setting Up Organizational Data and Mapping (Master) Data

1. Using transaction PPOMA_BBP, make sure the purchasing organization and purchasing group of

the back-end system exist in the organizational plan.

1. Make sure that you link the SAP SRM purchasing organization to the purchasing organization

you use for contracts in the back-end system: On the Function tab under section Local, proceed

as follows:

■ Select the Purchasing Organization checkbox.

■ Enter the key of the back-end purchasing organization.

■ Enter the key of the logical system (back end).

2. Make sure that you link the SAP SRM purchasing organization to the purchasing group you

use for contracts in the back-end system. To do so, on the Function tab under section Local,

proceed as follows:

■ Select the Purchasing Group checkbox.

■ Enter the key of the back-end purchasing group.

2. Make sure table VENMAP contains supplier data with identical GUID, back-end supplier number,

and logical system.

3. Make sure table BBP_LOCMAP contains location data with mapping for business partner and

logical system.



30/66 PUBLIC 2011-11-08

4. You must use a BAdI to map this data, if you do not use identical data in SAP SRM and the back-

end systems for the following:

■ Product categories

■ Products

■ Condition types for normal positions

■ Condition types for service positions

■ Text IDs

■ Transaction types

Use BAdI BBP_CTR_BE_CREATE in SAP SRM.

RECOMMENDATION

We recommend that you map the data there. For more information, see Customizing

for SAP SRM under SRM Server Cross-Application Basic Settings Business Add-Ins Follow-

On Document Generation in the Back-End System Create Contract in Back-End System

Alternatively, you can use a BAdI in the back-end system: BBP_CTR_BADI. For more

information, see Customizing for SAP ERP under Integration with other mySAP.com Components

Supplier Relationship Management Business Add-Ins for SRM (BAdIs) Contracts and Conditions

Change Contracts and Conditions .

Procedure in the Back-End System

Setting Up IDoc Inbound Processing

NOTE

Back-end inbound processing uses different IDocs for creating contracts and conditions.

Transaction Code WE42

Menu Path Tools ALE ALE Development IDoc Inbound Processing Define Process Code

1. Assign the inbound processing code BLAO for purchasing contracts to message type BLAORD.

2. Assign the inbound processing code COND for conditions to message type COND_A.

Creating ALE Partner Settings

Transaction Code WE20

Menu Path Tools ALE ALE Administration Runtime Settings Partner Profiles

Create a partner profile for partner type LS (logical system of sending SAP SRM) with the following

entries and settings in the Inbound parameters section:

■ Message type BLAORD (for purchasing contracts), Process Code BLAO and Transfer IDoc

immediately activated.



2011-11-08 PUBLIC 31/66

■ Message type COND_A (master conditions, for price determination), Process Code COND and

Transfer IDoc immediately activated.

For more information, see Defining RFC Destination and Back-end System [external document].

Specifying Document Types for Back-End Contracts

Transaction Code OMEF

Customizing Path Materials Management Purchasing Contract Define Document Types

1. Choose the transaction type for back-end contracts.

2. Enter a number range for external number assignment that is identical to the internal number

range you specified in SAP SRM for back-end contracts.

NOTE

If you do not want to use a transaction type already defined in the back-end system, you can

create a new one for back-end contracts. See Determining the Transaction Type for Back-end

Contracts above.

NOTE

If the back-end system is SAP enhancement package 4 for SAP ERP 6.0 or higher, you must define

settings for enterprise services. For more information, see Configuring Synchronous Services for Operational

Contract Management [page 15].

2.9.5 More Information About Contract Configuration

Perform the following activities in Customizing for SAP SRM under SRM Server Cross-Application Basic

Settings :

■ Switch On Version Control for Purchasing Documents

■ Activate Enhanced Authorizations for Contracts

The following Business Add-Ins are available in Customizing for SAP SRM under SRM Server Business

Add-Ins Contract Management :

■ Initial Upload

■ Change Contract Status

■ Implementation of Methods for Making Mass Changes

Run the following system transactions in SAP SRM:

■ WE20

■ WE21



32/66 PUBLIC 2011-11-08

2.10 Settings for Analytics in Contract Management

2.10.1 Contract Management: Available Queries

This document lists the predefined queries for Contract Management, delivered by SAP.

Prerequisites

■ You have performed all the steps necessary for general SAP NetWeaver BI configuration. See SAP

Solution Manager under <project name> Configuration SAP SRM <release> Basic Settings for SAP

SRM Basic Settings for Analytics .

■ All the business content for this scenario is installed and activated. For more information, see SAP

Solution Manager under <project name> Configuration SAP SRM <release> Basic Settings for SAP

SRM Basic Settings for Analytics Lists of Content Objects and Transactions .

Features

Query List

Description Technical Name

Contract Alerts 0SRCT_DS1_Q007

Contract Details 0SRCT_DS1_Q003

Contract Utilization 0BBP_MP03_Q0001

Contract Utilization Detail 0SRCT_DS1_Q901

Contract alerts 0BBP_MP03_Q0704

Contract expiration 0SRCT_DS1_Q903

Contract releases (Hierarchy) 0SRCT_DS1_Q012

Contract utilization overview 0SRCT_DS1_Q902

Contracts per Product Category (current) 0SRCT_DS1_Q005

Contracts per Product and Vendor 0SRCT_DS1_Q008

Contracts per Purchasing Organization / Purchasing Group 0SRCT_DS1_Q006

Expiring Contracts 0SRCT_DS1_Q004

Global Outline Agreements - Target Values 0SRCT_DS1_Q002

Local Contract Releases of Global Outline Agreements 0SRCT_DS1_Q001

Releases Scheduling Agreements of Global Outline Agreements 0SRCT_DS1_Q010

SUS: Contract Overview 0SRCT_DS1_SP_Q001

SUS: Expiring Contracts 0SRCT_DS1_SP_Q002

Scheduling Agreement Details 0SRCT_DS1_Q009

Scheduling Agreements About to Expire 0SRCT_DS1_Q011

Contract utilizations by categories 0BBP_MP03_Q0702

Contract utilizations by suppliers 0BBP_MP03_Q0703

Contract utilizations details 0BBP_MP03_Q0701

Contract alerts 0BBP_MP03_Q0704


2.10 Settings for Analytics in Contract Management

2011-11-08 PUBLIC 33/66

3 Operational Contract Management

You can find a scenario description in SAP Solution Manager under <project name> Scenarios

Operational Contract Management . Select the Documentation tab.

SAP Supplier Relationship Management scenario and process descriptions are also available on SAP

Help Portal at http://help.sap.com under SAP Supplier Relationship Management Business Scenarios .

3.1 Define Usage of Central Contracts

The process Define Usage of Central Contracts consists of the following process steps:

1. Define contract hierarchies

2. Define quota arrangements

You can find a process description in SAP Solution Manager under <project name> Scenarios

Operational Contract Management Business Processes Define Usage of Central Contracts . Select the

Documentation tab.

3.1.1 Configuration Content for Defining Usage of Central Contracts

The following Business Add-In is available in Customizing for SAP Supplier Relationship Management

(SAP SRM):

SRM Server Business Add-Ins Sourcing Redetermination of the Contract To Be Used (Quota Arrangement) .

3.2 Developing Contracts

The process Developing Contracts consists of the following process steps:

1. Assign general contract authorizations

2. Upload contracts from another system

3. Create contract

4. Use complex service hierarchies in contracts

You can only use this step if you have activated the SRM, Service Procurement Innovations

(SRM_SERVICE_PROC_1) business function and the Central Contract Management

(SRM_701_Serv_Proc_CCM) Customizing switch.

5. Define discounts based on released values


3.1 Define Usage of Central Contracts

2011-11-08 PUBLIC 35/66

http://help.sap.com

6. Activate contract upload to catalog

7. Complete contract

8. Release contract

9. Approve contract

10. Distribute contract to SAP ERP

11. Distribute scheduling agreement to SAP ERP

12. Group back-end contract

13. Output contract

14. Process workload reassignment

15. Mass change for contract


Operational Contract Management Business Processes Developing Contracts . Select the Documentation tab.

3.2.1 Configuration Content for Developing Contracts

3.2.1.1 Assign General Contract Authorizations

3.2.1.1.1 Assign General Contract Authorization

You can use this process step to activate the authorization feature and authorize users to create, change,

display, print, or delete various sections of a central contract.

You can assign authorization at the following levels:

■ Authorization object: If you assign authorization to the authorization object, then all the roles

using this authorization object and the users assigned to these roles will have the assigned

authorization.

■ Role: If you assign authorization to a role, then only the users assigned to this role will have the

assigned authorization.

An authorized user can grant authorization to other users who generally do not have authorization

for a central contract in the Contract Management application. There are two authorization objects

used by the Contract Management application.

Procedure

1. You activate the new authorization object BBP_CTR_2 in the customizing activity Activate Extended

Authorizations for Contracts (BBP_CTR_EXT_AUTH).

For more information, see the customizing activity documentation.

2. If you want to authorize all the roles that use the new authorization object, then assign

authorization in the authorization object BBP_CTR_2.

For more information, see the document Assigning Authorizations.



36/66 PUBLIC 2011-11-08

NOTE

You can only assign authorization to the activity field in the old authorization object

BBP_PD_CTR. Authorization for the other fields, for example the sections field, should be

maintained in the authorization object BBP_CTR_2.

3. If you want to authorize a selected role, then assign authorization to the role.

For more information, see the document Assigning Authorization.

Result

All the users assigned to this role will have the same authorization for central contracts.

Example

You have authorized the operational purchaser role to create, display, and change the following sections

of a central contract:

■ Main Information

■ Documents

■ Conditions

All the users assigned to the role operational purchaser can create, display, and change a central contract

but they cannot do the following:

■ Delete a central contract

■ Grant authorization to other users for a central contract

■ View or create a confidential contract/central contract

3.2.1.1.2 Assigning Authorizations

Procedure

Assigning Authorizations to an Authorization Object

1. On the SAP Easy Access screen, choose Tools ABAP Workbench Development Other Tools

Authorization Objects Objects . Note that, alternatively, you can run the following system

transaction in SAP SRM: Maintain Authorization Objects (SU21).

2. Expand BBP.

3. Select the node you would like to change.

4. Click Change.

5. Choose Permitted Activities.

6. Select the authorizations as required and save.

Assigning Authorizations to a Role

1. On the SAP Easy Access screen, choose Tools User and Role Maintenance Role Maintenance . Note

that, alternatively, you can run the following system transaction in SAP SRM: Role Maintenance

(PFCG).



2011-11-08 PUBLIC 37/66

2. Enter the role.

3. Choose Change.

4. On the Authorizations tab page, choose Change Authorization Data.

5. Expand BBP Component Authorization object for contracts in SRM5 BBP_CTR_2 .

6. For each of the fields, select the authorizations as required and save.

7. Save the role.

3.2.1.2 Upload Contract from Another System

3.2.1.2.1 Upload Contract from Another System

You use this process step to configure all the activities required to upload SAP ERP contracts and

scheduling agreements to an SAP Supplier Relationship Management (SAP SRM) system.

Process

1. If you want to change the contract data that is transferred from the SAP back-end system to the

SAP SRM system, implement one of the following Business Add-Ins (BAdIs):

■ BBP_CTR_INIT_UP in the SAP SRM system

■ BBP_CTR_INIT_UP_PI in the back-end system

For more information, see the BAdI documentation.

NOTE

By default, the text IDs in the back-end system are not mapped to the text IDs in the SAP

SRM system. The mapping is required to upload the long texts from the back-end system to

the SAP SRM system.

You can map the text IDs in one of the following ways:

■ Map the text IDs in the BAdI BBP_CTR_INIT_UP.

■ In the SAP SRM system, do the following:

1. In Customizing for SAP SRM under SRM Server Cross-Application Basic Settings Text

Schema Define Text Types , assign the text type K01 for the text object BBP_PD.


Schema Define Text Schema , assign the text type K01 for text schema CTR for Header and

Item.


Mapping Text Mapping for Inbound and Outbound Texts , map the text IDs.

2. To upload the contracts and scheduling agreements from the SAP back-end system to the SAP

SRM system, run the report BBP_CONTRACT_INITIAL_UPLOAD.



38/66 PUBLIC 2011-11-08

RECOMMENDATION

We recommend that a system administrator uploads all the contracts and scheduling

agreements to the SAP SRM system as a one-time task and then closes the contracts in the

SAP back-end system. This ensures that SAP SRM is the lead contract management system.

For more information, see the documentation for report

BBP_CONTRACT_INITIAL_UPLOAD.

3. If you want to be able to create contracts in Contract Management, create the condition types.

For more information, see the document Define a Condition Type.

NOTE

If you have not specified an external number range, the internal number range defined for

the contract transaction type will be used instead.

4. Define the external number range in the SAP SRM system. The contract IDs will be created within

the defined number range.

For more information, see the document Define an External Number Range.

5. Define the transaction type for a contract in the SAP SRM system

For more information, see the document Define a Transaction Type.

3.2.1.2.2 Define a Condition Type

You can use this process step to create the condition types required to create a central contract in the

Contract Management application.

Process

You can do it in one of the following ways:

■ If you want to reuse the condition types (defined in the back-end system) within the SAP SRM

system, do the following:

1. See Customizing for the back-end system: Materials Management Purchasing Conditions

Define Price Determining Process Define Condition Types .

2. Find out the details of all the condition types used for a central contract in the back-end system.

3. Create the identified condition types with the same technical settings within the SAP SRM

system, in the Customizing activity Process Condition Types (BBP_PRCCONDTYPE).

■ Implement one of the following BAdIs:

● BBP_CTR_INIT_UP in the SAP SRM system

● BBP_CTR_INIT_UP_PI in the back-end system



2011-11-08 PUBLIC 39/66

3.2.1.2.3 Define an External Number Range

You use this process step to define the external number ranges for central contracts. The external

number range has to begin with the object ID of the central contract that you want to create in the

SAP SRM system.

For more information, see Customizing for SAP Supplier Relationship Management (SAP SRM) under

SRM Server Cross-Application Basic Settings Number Ranges SRM Server Number Ranges Define Number

Ranges for Purchase Contracts .

3.2.1.2.4 Define a Transaction Type

You use this process step to define transaction types for central contracts to allow these types of

documents to be created in the SAP Supplier Relationship Management (SAP SRM) system.

Process

You can do this in one of the following ways:

■ If you want to reuse document types created in the back-end system as transaction types in the

SAP SRM system, do the following:

1. Perform the following activity in Customizing for the back-end system under SAP Customizing

Implementation Guide Materials Management Purchasing Contract Define Document Types .

2. Identify the document types that can be uploaded to the SAP SRM system.

3. Define the external number ranges in Customizing for SAP SRM under SRM Server Cross-

Application Basic Settings Number Ranges SRM Server Number Ranges Define Number Ranges for

Purchase Contracts ..

4. Create the identified document types as transaction types in the SAP SRM system in the

Customizing activity Define Transaction Types (SIMG_B2B_EVENT_TYPE).

5. Assign the external number ranges you created to the transaction types.

NOTE

If you do not specify an external number range, the internal number range will be used

instead.

■ Implement one of the following BAdIs:

● BBP_CTR_INIT_UP in the SAP SRM system

● BBP_CTR_INIT_UP_PI in the back-end system

3.2.1.3 Create Contract

To be able to create and edit contract documents in the SAP Supplier Relationship Management (SAP

SRM) system, you first need to define the number ranges and transactions types that you want to use.



40/66 PUBLIC 2011-11-08

Prerequisites

You have set up the organizational structure, and decided who in the organizational plan is authorized

to create, edit, or display contracts by assigning the relevant authorization roles

For more information, see SAP Solution Manager under SAP SRM 7.0 EHP1 Basic Settings for SAP SRM

Organizational Management .

3.2.1.4 Define Discounts Based on Hierarchical Contract Release Values

In the standard SAP Supplier Relationship Management (SRM) system, hierarchies for contracts are

inactive.

You can define condition types for discounts, where the scale base is the aggregated release value of all

previous contract release values. Hence you can use contract hierarchies to support and improve your

purchasing operations.

The following features are available:

■ The discount automatically takes effect with the next purchase order if the previous purchase

order raised the release value of the contract above the specified limit.

■ If you use contract hierarchies, the system automatically determines the release value for each

hierarchy level, and updates the aggregated release value for that particular contract hierarchy.

■ Each release value added at the header level of a subordinate contract is added to the superordinate

contract. The system determines the discounts according to the aggregated release value within

the contract hierarchy up to seven hierarchy levels.

To allow purchasers to use discounts based on release values within a contract hierarchy, make the

required settings in Customizing for SAP SRM under SRM Server Cross-Application Basic Settings

Activate Hierarchies for Product Categories, Suppliers, and Contracts . A default condition type ‘01AG’ has

already been pre-delivered in the standard system for release-value based discounting. If you wish to

define your own condition type, you must make all the necessary settings in Customizing for SAP SRM

under SRM Server Cross-Application Basic Settings Pricing .

3.2.1.5 Activate Contract Upload to Catalog

3.2.1.5.1 Setting Up Contract Replication to Catalog

In this section, you make the following settings that are required for the export of SAP SRM central

contracts to SRM-MDM Catalog:

■ Setting Up Key Mapping for Contract Item Categories [external document]

■ Implementing BAdI to Enrich Contract Data [external document]

■ Configuring the External Integration Role [external document]



2011-11-08 PUBLIC 41/66

3.2.1.5.2 More Information About Activating Contract Upload to Catalog

The following Business Add-In is available in Customizing for SAP SRM: SRM Server Business Add-Ins

SAP XML Interfaces Change SAP XML Outbound Mapping .

The following SAP Note applies: 1268821

3.2.1.6 Complete Contract

Perform the following activities in Customizing for SAP Supplier Relationship Management under:

■ SRM Server Cross-Application Basic Settings Enter Alert Threshold Data for Contracts

■ SRM Server Cross-Application Basic Settings Background Processing Define Threshold Value for Background

Processing

■ SRM Server Cross-Application Basic Settings Digital Signature Activate Digital Signature

3.2.1.7 Approve Contract

3.2.1.7.1 Smart Form: Form for Offline Approval

The Form for Offline Approval (BPP_OUT_OFFAPP) Smart Form is used to send an automatic e-mail via

the SAP Supplier Relationship Management (SAP SRM) system to approvers. In this e-mail, they can,

for example, click a link to accept or reject a request. This approval status is then sent back to the SAP

SRM system automatically.

NOTE

For more information about Customizing options for offline approval, see the Business Add-In

(BAdI) BBP_OFFLINE_APP_BADI in Customizing for SAP SRM under SRM Server Business Add-

Ins (BAdIs) Business Workflow Process/Application-Controlled Workflow Customer Enhancement of Offline

Approval , submethod DETERMINE_FORM_AND_PARAMS.

You use this procedure to make changes to the standard e-mail text and layout that is delivered with

the SAP SRM software in this Smart Form. You may need to do this, for example, to adapt the text to

the specific needs of your company or your corporate design.

Procedure1. Go to the Smart Forms initial screen (transaction SMARTFORMS).

2. Enter BPP_OUT_OFFAPP.

3. Make your changes and save.

ResultYou have now customized the text of the Smart Form. This is the text that appears in the automatically-

generated e-mail that is sent to users within your company on the basis of this Smart Form.



42/66 PUBLIC 2011-11-08

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=%201268821&_NLANG=en&_NVERS=0

3.2.1.7.2 Smart Form: Output Form for Contract

The Output Form for Contract (BBP_CONTRACT) Smart Form provides the layout and text for the output

of purchasing contracts to the supplier.

You use this procedure to make changes to the standard texts delivered with the SAP Supplier

Relationship Management (SAP SRM) software in this Smart Form. You may need to do this, for

example, to adapt the text to the specific needs of your company or your corporate design.

Procedure

1. Go to the Smart Forms initial screen (transaction SMARTFORMS).

2. Enter BBP_CONTRACT.


Result

You have now customized the purchasing contract form in the Smart Form.

3.2.1.7.3 Smart Form: Form for Output E-Mail

The Form for Output E-Mail (BBP_OUTPUT_COVER) Smart Form provides the text and layout of the

automatic e-mails sent by the SAP Supplier Relationship Management (SAP SRM) system to external

business partners to inform them about events concerning the following business objects:

■ RFx

■ RFx response

■ Auction

■ Purchase order

■ Purchasing contract

For example, when a new purchasing contract is issued, the business partner involved receives

notification about this from the SAP SRM system via e-mail.

You use this procedure to make changes to the standard e-mail texts that are delivered with the SAP

SRM software in this Smart Form. You may need to do this, for example, to adapt the text to the specific

needs of your company or your corporate design.

Procedure


2. Enter BBP_OUTPUT_COVER.


Result

You have now customized the text of the Smart Form. This is the text that appears in the automatically-

generated e-mail that is sent to business partners.



2011-11-08 PUBLIC 43/66

3.2.1.7.4 More Information About Approving Contracts

The following Business Add-Ins are available in Customizing for SAP SRM under SRM Server Business

Add-Ins :

■ Business Workflow Application-Controlled Workflow Customer Enhancement of Offline Approval

■ Document Output Change Forms for Document Output

For more information, see SAP Help Portal at http://help.sap.com Supplier Relationship Management

Functions Business Workflow Application-Controlled Workflows Approval Workflows for Documents and Objects

Workflow for Contracts .

For information about Smart Forms, see SAP Help Portal at http://help.sap.com SAP NetWeaver

<release> Library SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key

Capability Business Services Smart Forms Using SAP Smart Forms .

3.2.1.8 Output Contract

3.2.1.8.1 Enter Contract-Specific Attributes for Output

To ensure correct output, make entries for the following attributes in Customizing for SAP SRM under

SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan :

■ PRI

■ SF_HEADER

■ SF_FOOTER

■ SF_GRAPHIC

For more information about making entries for attributes, see User Attributes in SAP SRM [page 44].

3.2.1.8.2 User Attributes in SAP SRM

The following table lists the attributes available in SAP Supplier Relationship Management (SAP SRM).

NOTE

Some of the attributes are only simulated. The attributes are marked accordingly in the table

T77OMATTR. Tables that are not attribute tables form the basis of user attribute simulation.

Attributes indicated as system-dependent can have different values in different systems.

Attribute Description and Example Value

Definition System-Dependent

ACS System alias for accounting systemsExample value: ABCCLNT123

Specifies the back-end system where the account assignment is checked. This attribute is required for: ■ Invoices without purchase order reference ■ Local invoices



44/66 PUBLIC 2011-11-08

http://help.sap.com

http://help.sap.com

(In the case of a supplier, the back-end system is determined using the attribute VENDOR_ACS)

We recommend that you define this attribute at a high level in your organizational plan.Prerequisite: You must have defined the back-end system in Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings Define Basic Settings. .

ADDR_BILLT Invoice recipient address

Default invoice recipient address in purchase order.

ADDR_SHIPT Ship-to addressExample value: 12345

Default ship-to party address in purchase order.Enter at least one ship-to address and set it as the default address.

AN1 AssetExample value: ABCCLNT123\000000001111

Specifies the asset in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.

AN2 Asset subnumberExample value: Q4CCLNT300\1234

Defines the asset sub-number in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.

ANK Asset classExample value: QW4CLNT100\00001000

Defines the asset class in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.

ANR OrderExample value: ABCCLNT123\000000000040

Defines the order in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.

APO Sales order itemExample value: Q4CCLNT300\123456

Defines the sales order item in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.

APPRV_LIM Approval limit The value up to which a user is allowed to approve.You define this attribute using tab card Extended attributes.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan.

AUN Sales orderExample value: ABCCLNT123\000000000333

Specifies the sales order in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.

BSA Transaction type: Shopping cart follow-on documentExample value: ABCCLNT123\ECA3

Defines the transaction type in the respective system for follow-on documents from shopping carts.The attribute needs to be defined once per system, for the local SAP SRM system and for all connected back-end systems.



2011-11-08 PUBLIC 45/66

BUDGET User budget Amount available to an employee for purchases. Required for the Purchasing Budget Workflow [external document].

BUK Company codeExample value: QW4CLNT100\1000

Company code in the back-end system.Generally, the user inherits the company code from his/her company. If you want to overwrite the value inherited from the company you should define the company code via this attribute only.You define the company code of the company for the organizational unit assigned to the company on the Function tab.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan.

BWA Movement typeExample value: ABCCLNT123\123

Defines the type of goods movement in the back-end system. This value is required if reservations are to be created in the back-end system.

CAT Catalog IDExample value: MDMCA30

Defines the catalogs to which a user has access. You must define this attribute in Customizing for SAP Supplier Relationship Management under SRM Server Master Data

Content Management Define External Web Services.

CNT Cost centerExample value: ABCCLNT123\0000001000

Defines the cost center in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.

COCODE Company Code Company Code

COMPANY Company Identifies a legally independent section of the company.This attribute is simulated. The simulated value contains the number of an organizational unit that is indicated as company in the organizational plan.It identifies an organizational unit as company on the Function tab.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan.

CT_PROC_TY Transaction Type: Contract

Transaction Type for Contract

CUR Local currencyExample value: EUR

Default currency of the user

DP_PROC_TY Transaction type: Direct materialExample value: ECDP

Specifies the transaction type that is used when purchase orders for direct materials are created via BAPI, shopping cart, or bid invitation/bid. You have to maintain this attribute for the responsible purchasing group (see also the attribute TEND_TYPE). The specified transaction type has to correspond to the document type used in the back-end system for direct material purchase orders with external number assignment. The value for this attribute can be



46/66 PUBLIC 2011-11-08

inherited. For example, purchasing groups can inherit it from their purchasing organization.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Define Transaction Types.

EXT_ITS Current ITS of an external partnerExample value: http://abc.firma.com/wgate/

Obsolete from SRM 7.0

FORWARD_WI Flag: Forward work itemExample value: X

Indicator: Specifies whether work items are to be forwarded as e-mails.

IS_COMPANY Indicator: Company

Indicator: Identifies an organizational unit as independent legal entity.This attribute is simulated. You set this indicator for an organizational unit on the Function tab by selecting Company.You should define an organizational unit high up in the organizational plan as company by setting this indicator. If you have further organizational units in a lower level of your plan that represent subsidiaries, you also need to set this indicator.See Customizing for SAP Supplier Relationship Management under: SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan.

IS_PGR Indicator: Purchasing group

This indicator specifies that an organizational unit is identified as purchasing group.This attribute is simulated. You set this indicator on the Function tab.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan.

IS_POR Indicator: Purchasing organization

This indicator specifies that an organizational unit is identified as purchasing organization.This attribute is simulated. You set this indicator on the Function tab.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan.

ITS_DEST Current ITS of a userExample value: http://abc.firma.com/wgate/

Obsolete from SRM 7.0

KNT Account assignment categoryExample value: CC

Default value for account assignment when creating shopping cart or lean purchase order.The default value for the account assignment is determined on the basis of the value for this attribute (for



2011-11-08 PUBLIC 47/66

example CC - cost center) in connection with the relevant account assignment object (in this example CNT cost center).Note: In Customizing, no check occurs to establish whether the value for the relevant account assignment object is maintained.

LAG Storage location An organizational unit that allows you to differentiate between different material stocks within a plant.You define this attribute on the Extended Attributes tab.

NET NetworkExample value: ABCCLNT123\000000600003

Specifies the network in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.

PM_ARWRK Plant for work centerExample value: ABCCLNT123\1234

Plant in which the executing work center is located.This attribute is used as a selection criterion when searching for orders in the back-end system.

PM_AUART Order typeExample value: ABCCLNT123\PM01

Order types distinguish orders according to their use, for example, maintenance and service orders.This attribute is used as a selection criterion when searching for orders in the back-end system.

PM_GL_ACCT PM: Default G/L accountExample value: ABCCLNT123\417000

Default value for the G/L account in the component detail data.

PM_IPHAS PhaseExample value: ABCCLNT123\0

Phases subdivide the life cycle of an order into several subsections (for example, created and released) and determine which activities are allowed for the order in each section.This attribute is used as a selection criterion when searching for orders in the back-end system.This is a mandatory attribute.

PM_IWERK Planning plantExample value: ABCCLNT123\1234

Plant at which maintenance tasks are planned and prepared.This attribute is used as a selection criterion when searching for orders in the back-end system.

PM_PUR_GRP PM purchasing groupExample value: ABCCLNT123\001

Number of the organizational unit that is indicated as the purchasing group in the organizational plan. Default value in the component detail data.

PM_PUR_ORG PM purchasing organizationExample value: ABCCLNT123\1000

Number of an organizational unit that is indicated as the purchasing organization in the organizational plan. Default value in the component detail data.

PM_SWERK Maintenance plantExample value: ABCCLNT123\1234

Plant at which the technical objects of a company are installed.



48/66 PUBLIC 2011-11-08

This attribute is used as a selection criterion when searching for orders in the back-end system.

PM_VAWRK Plant for main work centerExample value: ABCCLNT123\1234

Plant at which the main work center entered is located.This attribute is used as a selection criterion when searching for orders in the back-end system.

PM_WGR PM material groupExample value: ABCCLNT123\000000001

Indicates the key of the material group that unites materials and services with the same properties. Default value in the component detail data.

PM_WRK Plant of the componentExample value: ABCCLNT123\1000

Plant at which the component required to execute the order (reservation or requirement request) is planned. Default value in the component detail data.This is a mandatory attribute.

PRCAT Material group Defines the product categories for which the user has authorization. We recommend that you define a default value. For example, if a user mainly purchases office materials, it would make sense to specify office materials as the default value.To improve performance, we recommend that you use wildcards and ranges to restrict the product categories defined as much as possible.You define this attribute using tab card Extended attributes.

PRI Default printerExample value: PRINTER

Printer name

PRO WBS element Defines the WBS element The work breakdown structure (WBS) represents the hierarchical organization of a project. WBS elements are the individual structural elements in a work breakdown structure Default value for account assignment when creating shopping cart or lean purchase order.

PURCH_GRP Purchasing group Number of an organizational unit that is indicated as local purchasing group in the organizational plan.This attribute is simulated. You define an organizational unit as purchasing group on the Function tab.

PURCH_GRPX ERP purchasing group

Number of the organizational unit that is indicated as the purchasing group in the organizational plan. The value contains the ID and the associated back-end system of a back-end purchasing group.This attribute is simulated. You define the ID and the associated system on the Function tab.

PURCH_ORG Purchasing organization

Number of an organizational unit that is indicated as local purchasing organization in the organizational plan.This attribute is simulated. You define an organizational unit as purchasing organization on the Function tab.

PURCH_ORGX R/3 purchasing organization

Number of an organizational unit that is indicated as the purchasing organization in the organizational plan.



2011-11-08 PUBLIC 49/66

This attribute is simulated. You define the ID and the associated system on the Function tab.

REQUESTER Goods recipientExample value: See definition

Indicates the organizational units or users for which this employee can create shopping carts, and so on.A user can select all users in an organizational unit as alternative goods recipients if the attribute is maintained with the following entry, for example: O 50000019.If a specific user is to be selected as alternative goods recipient, the attribute needs to be maintained as follows: <US><User ID of alternative goods recipient>, for example USMANAGER22.Before you can order direct materials, you must have defined the necessary plants. You use this attribute to define these plants in the organizational plan. You enter plants as follows: <type_BP><partner_number_for_plant>, for example, BP1195.For the purposes of the direct materials scenario the business partner number (it can have a maximum of ten positions) defined in this attribute must be linked to a plant in table CRMM_LOCMAP.Buy on behalf of: To enable substitute shopping you enter all users for whom a purchasing assistant can buy on behalf of.The values defined for the attribute form the basis for the F4 help for the Goods Recipient field available to the purchasing assistant or other employee creating shopping carts for other users in the Shop scenario.

RESP_PRGRP Purchasing group responsible

Number of the organizational unit for which the purchasing group is responsible.This attribute is simulated. You define the organizational responsibility of a purchasing group on the Responsibility tab.

RESP_PRCAT Product category responsible

Number of the product category for which the purchasing group is responsible.This attribute is simulated. You define the product responsibility of a purchasing group on the Responsibility tab.

ROLE User roleExample value: /SAPSRM/EMPLOYEE

Indicates the role of the user, for example manager, employee, or purchasing assistant.If no approval workflow for new users is in force, a default value must be set for the attribute ROLE, for example /SAPSRM/EMPLOYEE. (If no default value is found, the approval workflow is activated automatically.)

SF_FOOTER SAP Smart Forms: Footer

Defines the footer to be used when purchase orders or contracts are output. The values are determined using Smart Forms on the basis of the purchasing group. You define the footer using the transaction SE78.



50/66 PUBLIC 2011-11-08

SF_GRAPHIC SAP Smart Forms: Company logo

Defines the company logo to be used when purchase orders or contracts are output. The values are determined using Smart Forms on the basis of the purchasing group. You define the company logo using transaction SO10.

SF_HEADER SAP Smart Forms: HeaderExample value: BBP_COMPANY

Defines the header to be used when purchase orders or contracts are output. The values are determined using Smart Forms on the basis of the purchasing group. You define the header using the transaction SE78.

SLAPPROVER Spending limit approverExample value: USMANAGER1

Specifies the approver used in workflows based on a spending limit.

SPEND_LIM Spending limit The value up to which a user is allowed to spend before the spending limit approval workflow is triggered.You define this attribute using tab card Extended attributes.

SYS System aliasExample value: ABCCLNT123

Defines the systems to be searched to find purchase orders. This attribute is used to generate worklists for employees that create confirmations or invoices centrally. The attribute can refer both to the local system and back-end systems. Generally, several values are defined: The local systems and various back-end systems.You must define the systems in Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings Define Basic Settings.

TEND_TYPE Transaction type: Bid invitationExample value: BID

Specifies the transaction type for bid invitations created automatically, for example in the PLM (collaborative engineering). You define this attribute for the purchasing group that is responsible for the organizational unit of the entry channel. The value for this attribute can be inherited. For example, purchasing groups can inherit it from their purchasing organization. You define the transaction type in Customizing.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Define Transaction Types.

TOG Tolerance groupExample value: CONF

Defines the tolerance group. Using this attribute, you define for a user group which tolerance checks are used when quantity or value tolerances for deliveries or invoices are exceeded.

VENDOR_ACS Accounting system for the vendorExample value: ABCCLNT123

Specifies the back-end system where the account assignment is checked. This attribute is required for: ■ Invoices without purchase order reference ■ Local invoices.We recommend that you define this attribute at a high level in your organizational plan.Prerequisite: You must have defined the back-end system in Customizing for SAP Supplier Relationship Management



2011-11-08 PUBLIC 51/66

under SRM Server Technical Basic Settings Define Basic Settings.

VENDOR_SYS System alias for vendorExample value: ABCCLNT123

Defines the systems to be searched to find purchase orders to create a worklist for a vendor creating confirmations or invoices centrally. Can refer both to the local system and to the back-end system. Generally, multiple values are entered: The local systems and various back-end systems.You must define the systems in Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings Define Basic Settings.

WGR Product category See attribute PRCAT.This attribute is simulated. The values of the attribute PRCAT serve as the basis for the simulation.Whilst you can define single values, masks, and areas for PRCAT, you can only use single values for WGR.

WRK Plant Specifies the plant in the ERP back-end system. This attribute is only required if the back-end system is an SAP System.You define this attribute using tab card Extended attributes.

3.2.1.8.3 Smart Form: Background Processing of Contracts

You use this Smart Form Background Processing Contract (BBP_CTR_BGR_PROCESSING) to send e-mails

about your purchasing contracts to purchasing organizations. These e-mails contain standard text and

a link to the contract.

You use this procedure to make changes to the standard e-mail text that is delivered with the SAP

Supplier Relationship Management (SAP SRM) software.

Procedure1. On the SAP Easy Access screen, choose Tools Form Printout SMARTFORMS - Smart Forms .

2. Enter the name of the form as BBP_CTR_BGR_PROCESSING and choose Change. The SAP Smart

Form Builder screen appears.

3. Choose PA_MAINPAGE MAIN

4. To change the standard e-mail text of a contract, double-click the text element TE_CTR_MAIL

New PC Created.

5. Make the required changes and click Save.

3.2.1.8.4 Smart Form: Form for Output E-Mail

The Form for Output E-Mail (BBP_OUTPUT_COVER) Smart Form provides the text and layout of the

automatic e-mails sent by the SAP Supplier Relationship Management (SAP SRM) system to external

business partners to inform them about events concerning the following business objects:



52/66 PUBLIC 2011-11-08

■ RFx

■ RFx response

■ Auction

■ Purchase order

■ Purchasing contract

For example, when a new purchasing contract is issued, the business partner involved receives

notification about this from the SAP SRM system via e-mail.

You use this procedure to make changes to the standard e-mail texts that are delivered with the SAP

SRM software in this Smart Form. You may need to do this, for example, to adapt the text to the specific


Procedure


2. Enter BBP_OUTPUT_COVER.


Result


generated e-mail that is sent to business partners.

3.2.1.8.5 Smart Form: Output Form for Contract

The Output Form for Contract (BBP_CONTRACT) Smart Form provides the layout and text for the output

of purchasing contracts to the supplier.

You use this procedure to make changes to the standard texts delivered with the SAP Supplier

Relationship Management (SAP SRM) software in this Smart Form. You may need to do this, for

example, to adapt the text to the specific needs of your company or your corporate design.

Procedure


2. Enter BBP_CONTRACT.


Result

You have now customized the purchasing contract form in the Smart Form.



2011-11-08 PUBLIC 53/66

3.2.1.8.6 More Information About Outputting Contracts




3.2.1.9 Change Contract

3.2.1.9.1 Configuring Mass Change Parameters in Contract Management

You can define your own mass change parameters for the Mass Changes function in Contract

Management. As an example for creating new mass change parameters, you can use any of the mass

change parameters in the standard SAP Supplier Relationship Management (SAP SRM) system (listed

in view BBPV_CTR_MASSOP, language table BBPC_CTR_MASSOPT).

For contract mass changes, the following packages are provided:

■ /SAPSRM/PDO_AO_CTR_MASS for business logic

■ /SAPSRM/CH_WD_UI_AO_CTR_MASS for UI

Procedure

In Maintain Table Views (transaction SM30), enter view BBPV_CTR_MASSOP and choose Maintain.

Choose New Entries and make the following entries:

Field Value

Mass Change Method Enter a name starting with “Z_” for your new mass change method.

+ If you want item data to be filtered, select this indicator (available for location, product category, product, supplier/partner, product number).

Sort Order Choose the order in which the contracts are to be processed by the system.If the order is not important, you can choose Space. If the mass change is not to be combined with another mass change method, choose Isolated Execution.

Group of Mass Change

Choose whether the mass changes apply to header data or item data, or choose Miscellaneous (No Display).

Sections Choose the type of section where you want to make changes. This affects whether the system makes authorization checks for this section or not.

Mass Change Enter a text to describe your mass change. This text appears on the UI. Make sure that it is translated into all languages that are used in your system.

Create a structure and table type in the ABAP Dictionary

In the ABAP Dictionary (transaction SE11), create a new structure in the customer namespace. Include

the components to store the old value and new value of the field, and any other parameters that are

required to control the business logic. You use this structure in the Web Dynpro component.

In structure /SAPSRM/S_PDO_CTR_MC_PMNT_TRMS for the mass update of payment terms:

■ Component PMNT_TRMS_OLD is used to store the old payment term value



54/66 PUBLIC 2011-11-08

http://help.sap.com

■ Component PMNT_TRMS_NEW is used to store the new payment term value

■ Component SELECT_FIELD_FROM is used to determine whether to update a specific payment

term or all payment terms

In the ABAP Dictionary (transaction SE11), create a new table type in the customer namespace. As the

line type, enter the structure that you created above. You use this table type as parameters in the

Business Add-In (BAdI) implementation.

See table type /SAPSRM/T_PDO_CTR_MC_PMNT_TRMS for the mass update of payment terms.

Create a Web Dynpro component

■ Create a new Web Dynpro component in the Z or Y namespace and implement the interface /

SAPSRM/WDI_CTR_MC

■ In method GET_VIEW_CONTEXT of the component controller, implement the following code,

where <node name> is the name of the context node:

ron_context = wd_context->get_child_node (name =

IF_COMPONENTCONTROLLER=>wdctx_<node name>)

■ Create a view and an inbound plug in the view. Embed the view to the window.

■ Create a context node in the component controller with the required attributes from the structure

that you created above, and link the node to the view controller context node.

■ Create an action ACTIONREJ_CHNG in the view

Method ONACTIONACTIONREJ_CHNG is created automatically.

■ Implement the following code in the method:

wd_comp_controller->fire_reject_changes_evt ( )

■ To create the view layout, see payment term component /SAPSRM/WDC_UI_AO_CT_MC_D

and view V_AO_CTRM_INCO_HEAD.

Create an implementation for the BAdI

In the BAdI Builder (transaction SE18), enter enhancement spot /SAPSRM/CTR_MASS_CHANGE.

The BAdI /SAPSRM/CTR_MC_BADI and interface /SAPSRM/IF_EX_CTR_MASS_BADI have been

defined with the following methods:

Method Description

CTR_DEFINE_UI Provides the screen information of the parameters or mass change method for the UI. The current implementation is valid only for ABAP Web Dynpro.

CTR_GET_READ_FLAGS Distinguishes between header and item parameters.

CTR_CHANGE Maps the new values with the old, and also validates them.

CTR_GET_STATUS_MESSAGE Provides the status of the mass change process.

CTR_VALIDATE Validates the screen input values.

To create a Z implementation, go to transaction SE19.



2011-11-08 PUBLIC 55/66

In the Create Implementation area, enter enhancement spot /SAPSRM/CTR_MASS_CHANGE and

create an implementation for the BAdI /SAPSRM/CTR_MC_BADI. The desired implementation name

is Z<mass change parameter name>.

Implement the interface methods above as per the desired logic and activate the methods and BAdI.

NOTE

See the Incoterm implementation class /SAPSRM/CL_CTR_MC_HI_INCOTERM.

Add a filter value to the enhancement implementation with filter /SAPSRM/PDO_CTR_MC_OPKEY

and comparator =, for the new mass change parameter. In this case, the filter value is the name of the

field specified in the Customizing table, for example, HDR_INCOTERM.

For more information, see Customizing for SAP SRM under SRM Server Business Add-Ins Contract

Management Implementation of Methods for Making Mass Changes .

NOTE

Check that:

■ Your change method is listed in the change methods table that is displayed in step 2 of the

contract mass update transaction

■ The view relevant to the parameter is displayed in Step 2 of the contract mass update

transaction when you click your newly created change method

■ The contracts are updated successfully when you choose Start Mass Changes for the newly

created change method

3.2.1.9.2 Smart Form: Mass Change to Contracts

You use the Smart Form Mass Change to Contracts (BBP_CTR_MASS_END) to notify users about the

status of their mass changes to purchasing contracts.

When a user makes mass changes, the system automatically generates an e-mail to notify the user about

which mass changes were performed and whether they were successful or not.

You use this procedure to make changes to the standard e-mail text that is delivered with the SAP

Supplier Relationship Management (SAP SRM) software. You may need to do this, for example, to

adapt the text to the specific needs of your company or your corporate design.

Procedure


2. Enter BBP_CTR_MASS_END.




56/66 PUBLIC 2011-11-08

Result


generated e-mail that is sent to users within your company after they have performed or attempted to

perform mass changes within the SAP SRM system.

3.2.1.9.3 More Information About Changing Contracts


Library SAP NetWeaver by Key Capability Application Platform by Key Capability Business Services Smart Forms

Using SAP Smart Forms .

3.3 Processing Contracts and Sourcing Rules in ERP

The process Processing Contracts and Sourcing Rules in ERP consists of the following process steps:

1. Process vendor master data

2. Process message conditions

3. Process contracts in ERP

4. Process purchasing info records

5. Process source list

6. Process quota arrangement

7. Process conditions for procurement


Operational Contract Management Business Processes Processing Contracts and Sourcing Rules in ERP . Select the

Documentation tab.

To find the process-related configuration content, select the Configuration tab.

3.4 Negotiating Contracts

The process Negotiating Contracts consists of the following process steps:

1. Search for contracts

2. Negotiate contract

3. Renew contract

4. Update contracts via mass-update


Operational Contract Management Business Processes Negotiating Contracts . Select the Documentation tab.


3.3 Processing Contracts and Sourcing Rules in ERP

2011-11-08 PUBLIC 57/66

http://help.sap.com

3.4.1 Configuration Content for Negotiating Contracts

3.4.1.1 Basic Settings for Negotiating Contracts

Before you configure this process, be sure to complete the basic settings for Strategic Sourcing, which you

can find in SAP Solution Manager under <project name> Configuration SAP SRM <release> Basic

Settings for Strategic Sourcing .

3.4.1.2 Making Settings for Contract Negotiation

These settings have an effect when negotiating a contract from the contract management application

in SAP Supplier Relationship Management (SAP SRM) or from SAP Bidding Engine.

You can set up contract negotiation in SAP SRM in one of the following ways:

■ Using the transaction type Customizing. We strongly recommend this user-independent

alternative. See Customizing for SAP SRM under SRM Server Cross-Application Basic Settings Define

Transaction Types .

■ Using transaction PPOMA_BBP and defining the following user attributes in the organizational

plan:

● TEND_TYPE

Determines the transaction type for RFxs

● CT_PROC_TYPE

Determines the transaction type for purchase contracts

When using the negotiate function the system always creates an RFx. Within the related RFx response,

submitted by the bidder, the system offers the following options to conclude the process:

■ Update the contract that is currently used

■ Create a new contract

Prerequisites

For the RFx-related transaction type (for example, RFCR) that you are using for contract negotiation,

you have selected the Contract indicator in the customizing activity Define Transaction Types, under the

Process Control section of the view Transaction Types.

Procedure

Setting Up the Transaction Type for the Update Process

1. Using transaction SPRO and the Customizing activity Defining Transaction Types, in the view Transaction

Object Types select the table entry with business transaction category BUS2000113

2. In the navigation tree, select Transaction Types.

3. Select a contract-specific transaction type, for example, CCTR.

4. In the navigation tree, select Transaction Types of Follow-on Documents. Make sure the table contains an

entry with the following data:


3.4 Negotiating Contracts

58/66 PUBLIC 2011-11-08

■ Business transaction category: BUS2000113

■ Transaction type (as selected above): CCTR

■ Subsequent object type: BUS2200

■ Follow-up transaction type: (for example) RFCR or another RFx-specific transaction type that

you use for contract negotiation.

Setting Up the Transaction Type for the Create Process

1. Using transaction SPRO and the Customizing activity Define Transaction Types, in the transaction

object type view select the entry with business object type BUS2200.

2. In the navigation tree, select Transaction Types.

3. Select a contract-specific transaction type, for example, RFCR.

4. In the navigation tree, select Transaction Types of Follow-on Documents. Make sure the table contains an

entry with the following data:

■ Business transaction category: BUS2200

■ Transaction type (as selected above): RFCR

■ Subsequent object type: BUS2000113

■ Follow-up transaction type: (for example) CCTR, or another RFx-specific transaction type

that you use for purchase contracts.

3.5 Processing Delivery Schedules

The process Processing Delivery Schedules consists of the following process steps:

1. Create or process scheduling agreements

2. Release scheduling agreements

3. Transmit and monitor scheduling agreements

4. Process delivery schedules and releases

5. Transmit and monitor delivery schedules

6. Administer scheduling agreements

7. Monitor or view list display of scheduling agreements


Operational Contract Management Business Processes Processing Delivery Schedules . Select the Documentation

tab.

To find the process-related configuration content, select the Configuration tab.

3.6 Searching for Sources of Supply Centrally

The process Searching for Sources of Supply Centrally consists of the following process steps:

1. Start sourcing application


3.5 Processing Delivery Schedules

2011-11-08 PUBLIC 59/66

2. Search for appropriate source of supply

3. Assign contract

4. Assign supplier

5. Create RFx from sourcing application

6. Create auction from sourcing application

7. Process workload distribution

8. Create purchase order from sourcing application

9. Create contract from sourcing application

You can find a process description in SAP Solution Manager under <project name> Scenarios Self-

Service Procurement Extended Classic Business Processes Searching for Sources of Supply Centrally .

3.6.1 Configuration Content for Searching for Sources of Supply Centrally

Perform the following activities in Customizing for SAP SRM:

■ SRM Server Business Add-Ins Changes to Purchasing Document Data

■ SRM Server Business Add-Ins RFx Control of RFx Publication

■ SRM Server Business Add-Ins RFx Subsequent Split of Grouping

■ SRM Server Cross-Application Basic Settings Configure Priorities

■ SRM Server Business Add-Ins Interface Configuration Appearance of Priorities

■ SRM Server Business Add-Ins Sourcing Redetermination of the Contract To Be Used (Quota

Arrangement)

■ SRM Server Activate Business Functions

■ SRM Server Cross-Application Basic Settings Service Procurement Activate Service Procurement

Innovations

■ SRM Server Cross-Application Basic Settings Service Procurement Activate Central Contract Management

Innovations

Run the following system transaction in SAP SRM: ABAP Editor (se38)

3.7 Monitoring Contracts

The process Monitoring Contracts consists of the following process steps:

1. Send and receive alerts

2. Process reports in SAP NetWeaver BI

3. Run context-sensitive graphical reports

You can only use this step if you have activated the SRM, Analytics (SRM_ANALYTICS_1) business function

and the Embedded Analytics for Purchasers (SRM_701_EMB_ANALYTICS) Customizing switch.


Operational Contract Management Business Processes Monitoring Contracts . Select the Documentation tab.



60/66 PUBLIC 2011-11-08

3.7.1 Configuration Content for Monitoring Contracts

3.7.1.1 Smart Form: Event Framework Messages

The Smart Form Event Framework Messages (BBP_OUT_EXCEPTION) is the form that is used to send an

e-mail to users to inform them that a particular event has happened. For example, it is used to remind

a user that a purchasing contract is about to expire, or to inform the user when a new purchase order

has been created.

You use this procedure to make changes to the standard e-mail text that is delivered with the SRM

software in this Smart Form. You may need to do this, for example, to adapt the text to the specific


Procedure


2. Enter BBP_OUT_EXCEPTION.


Result


generated e-mail that is sent to users within your company on the basis of this Smart Form.

3.7.1.2 More Information About Monitoring Contracts

Perform the following activities in Customizing for SAP SRM:

■ SRM Server Cross-Application Basic Settings Define Transaction Types

■ SRM Server Cross-Application Basic Settings Organizational Management Event Control for Organizational

Management

Perform the following activities in Customizing for SAP NetWeaver under Business Intelligence Settings

for BI Content Supplier Relationship Management :

■ Carry out SRM Product Category Matching

■ Carry out SRM Business Partner Matching






2011-11-08 PUBLIC 61/66

http://help.sap.com

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

62/66 PUBLIC 2011-11-08

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2011 SAP AG. 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 AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle and Java are registered trademarks of Oracle.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP companySybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG 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.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

2011-11-08 PUBLIC 63/66

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.comhttp://service.sap.com/srm-instinstguides

64/66 PUBLIC 2011-11-08

http://service.sap.comhttp://service.sap.com/srm-instinstguides

http://service.sap.comhttp://service.sap.com/srm-instinstguides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2011 SAP AG. 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 AG. The information contained herein may be changed without prior notice.

SAP-SRM7.0 EHP2 -Operational Contract Management

Documents

Transcript of SAP-SRM7.0 EHP2 -Operational Contract Management