SAP Supplier Relationship Management 7.

0: Operational Contract
Management
Based on SAP Solution Manager Content

Target Audience
n System Administrators
n Consultants

PUBLIC
Document version: 1.0 ‒ 10/26/2009
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 1230438.

Version Date Description

1.0 10/26/2009 Initial version

2/72 PUBLIC 10/26/2009

Table of Contents

Chapter 1 Important Information About this Document . . . . . . . . . . 5

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

2.1 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 SAP NetWeaver Process Integration . . . . . . . . . . . . . . . . 7
2.2.1 Importing Business Scenarios . . . . . . . . . . . . . . . . . . 7
2.2.2 Checking Integration Scenarios and Related Interfaces . . . . . . . . . 9
2.2.3 More Information About SAP NetWeaver Process Integration . . . . . . 10
2.3 Configuring Synchronous Services for Operational Contract Management . 10
2.4 Scheduling Reports to Archive or Delete Transactional Data . . . . . . 11
2.5 Pricing Settings for Purchasing Contracts . . . . . . . . . . . . . . 11
2.6 Alert Settings . . . . . . . . . . . . . . . . . . . . . . . . 12
2.6.1 Alert Management . . . . . . . . . . . . . . . . . . . . . . 12
2.6.2 Making Settings for Contract Alerts . . . . . . . . . . . . . . . 12
2.6.3 Triggering Events for Central Contracts . . . . . . . . . . . . . . 13
2.7 Setting Up TREX Server and TREX Search . . . . . . . . . . . . . 14
2.8 Workflow Settings for Business Scenarios . . . . . . . . . . . . . . 16
2.8.1 Set Up Workflow for Business Scenarios . . . . . . . . . . . . . . 16
2.8.2 Setting Up Application-Controlled Workflow for Operational Contract
Management . . . . . . . . . . . . . . . . . . . . . . . . 17
2.9 Contract Configuration . . . . . . . . . . . . . . . . . . . . 21
2.9.1 Configuration Options for Operational Contract Management . . . . . . 21
2.9.2 Making Settings for Central Contracts . . . . . . . . . . . . . . . 22
2.9.3 Making Settings for Back-End Contracts . . . . . . . . . . . . . . 23
2.9.4 More Information About Contract Configuration . . . . . . . . . . 28
2.10 Settings for Analytics in Contract Management . . . . . . . . . . . 29
2.10.1 Contract Management: Available Queries . . . . . . . . . . . . . 29

Chapter 3 Operational Contract Management . . . . . . . . . . . . . . 31

3.1 Define Usage of Central Contracts . . . . . . . . . . . . . . . . 31
3.1.1 Configuration Content for Defining Usage of Central Contracts . . . . . 31
3.2 Developing Contracts . . . . . . . . . . . . . . . . . . . . . 31
3.2.1 Configuration Content for Developing Contracts . . . . . . . . . . 32
3.2.1.1 Assign General Contract Authorizations . . . . . . . . . . . . . . 32
3.2.1.1.1 Assign General Contract Authorization . . . . . . . . . . . . . . 32

10/26/2009 PUBLIC 3/72

3.2.1.1.2 Assigning Authorizations . . . . . . . . . . . . . . . . . . . 33
3.2.1.2 Upload Contract from Another System . . . . . . . . . . . . . . 34
3.2.1.2.1 Upload Contract from Another System . . . . . . . . . . . . . . 34
3.2.1.2.2 Define a Condition Type . . . . . . . . . . . . . . . . . . . . 35
3.2.1.2.3 Define an External Number Range . . . . . . . . . . . . . . . . 36
3.2.1.2.4 Define a Transaction Type . . . . . . . . . . . . . . . . . . . 36
3.2.1.3 Create Contract . . . . . . . . . . . . . . . . . . . . . . . 36
3.2.1.4 Define Discounts Based on Release Values . . . . . . . . . . . . . 37
3.2.1.5 Activate Contract Upload to Catalog . . . . . . . . . . . . . . . 37
3.2.1.5.1 Setting Up Contract Replication . . . . . . . . . . . . . . . . . 37
3.2.1.5.2 More Information About Activating Contract Upload to Catalog . . . . . 37
3.2.1.6 Complete Contract . . . . . . . . . . . . . . . . . . . . . 38
3.2.1.7 Approve Contract . . . . . . . . . . . . . . . . . . . . . . 38
3.2.1.7.1 Smart Form: Form for Offline Approval . . . . . . . . . . . . . . 38
3.2.1.7.2 Smart Form: Output Form for Contract . . . . . . . . . . . . . . 58
3.2.1.7.3 Smart Form: Form for Output E-Mail . . . . . . . . . . . . . . . 57
3.2.1.7.4 More Information About Approving Contracts . . . . . . . . . . . 40
3.2.1.8 Output Contract . . . . . . . . . . . . . . . . . . . . . . 40
3.2.1.8.1 Enter Contract-Specific Attributes for Output . . . . . . . . . . . . 40
3.2.1.8.2 User Attributes in SAP SRM . . . . . . . . . . . . . . . . . . 40
3.2.1.8.3 Smart Form: Background Processing of Contracts . . . . . . . . . . 57
3.2.1.8.4 Smart Form: Form for Output E-Mail . . . . . . . . . . . . . . . 57
3.2.1.8.5 Smart Form: Output Form for Contract . . . . . . . . . . . . . . 58
3.2.1.8.6 More Information About Outputting Contracts . . . . . . . . . . . 58
3.2.1.9 Change Contract . . . . . . . . . . . . . . . . . . . . . . 58
3.2.1.9.1 Configuring Mass Change Parameters in Contract Management . . . . . 58
3.2.1.9.2 Smart Form: Mass Change to Contracts . . . . . . . . . . . . . . 61
3.2.1.9.3 More Information About Changing Contracts . . . . . . . . . . . . 62
3.3 Processing Contracts and Sourcing Rules in ERP . . . . . . . . . . . 62
3.4 Negotiating Contracts . . . . . . . . . . . . . . . . . . . . 62
3.4.1 Configuration Content for Negotiating Contracts . . . . . . . . . . 63
3.4.1.1 Basic Settings for Negotiating Contracts . . . . . . . . . . . . . . 63
3.4.1.2 Making Settings for Contract Negotiation . . . . . . . . . . . . . 63
3.5 Processing Delivery Schedules . . . . . . . . . . . . . . . . . . 64
3.6 Searching for Sources of Supply Centrally . . . . . . . . . . . . . 65
3.6.1 Configuration Content for Searching for Sources of Supply Centrally . . . 65
3.7 Monitoring Contracts . . . . . . . . . . . . . . . . . . . . . 65
3.7.1 Configuration Content for Monitoring Contracts . . . . . . . . . . 66
3.7.1.1 Smart Form: Event Framework Messages . . . . . . . . . . . . . . 66
3.7.1.2 More Information About Monitoring Contracts . . . . . . . . . . . 66

4/72 PUBLIC 10/26/2009

1 Important Information About this Document

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 1230438 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.0 .

10/26/2009 PUBLIC 5/72

This page is left blank for documents
that are printed on both sides.
2 Basic Settings for Contract Management

2 Basic Settings for Contract

Management

2.1 SAP Notes

The following SAP Notes apply:

n 734060 SRM: Upload and download of documents using MS Excel
n 609222 Sourcing: Create R/3 contracts, tricks and hints
n 646903 Global outline agreement: Tips and tricks
n 859049 SRM 5.0: Restrictions for uploading and downloading
n 812884 How to change the fields used for Excel upload and download
n 673479 Excel download: Quantities not displayed correctly
n 790860 Frequently asked questions for Excel upload and download
n 1268821 SRM 7.0 / ERP 6.04: Config. of Central Contract Management
n 1268336 Business Suite 2008: Synchronous peer-to peer Services
n 1252865 Central Contracts: Search help for Central Contract dumps
n 1271697 Wrong information in contracts tracking for calloffs
n 1269289 Portal error appears at CPPR in central contract link
n 1263470 CCM:Replication of Central Contracts with more than 10 items
n 1269803 Enter Net Price error for Central Contract
n 1314597 SRM central contract: Error in price determination Customizing
n 1270081 Trouble shooting SOA Services

2.2 SAP NetWeaver Process Integration

2.2.1 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:

10/26/2009 PUBLIC 7/72

2 Basic Settings for Contract Management
2.2 SAP NetWeaver Process Integration

n 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.
n 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 Partner Business System .
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.0).
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.

8/72 PUBLIC 10/26/2009

2 Basic Settings for Contract Management
2.2 SAP NetWeaver Process Integration

Note
n If the systems are applied from the SAP Landscape Directory, the Integration Builder
automatically creates the communication channels.
n 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.
31. In the left pane, select the Scenarios tab; your scenario has been added.

2.2.2 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 Direction Materials Management
Management
PurchasingContractSRMReplica- Asynchronous call (consumer) PurchasingContractSRMReplica-
tionRequest_Out tionRequest_In
PurchasingContractSRMReplica- Asynchronous call (provider) PurchasingContractSRMReplica-
tionConrmation_In tionConrmation_Out
PurchaseOrderSRMPricingSimu- Synchronous call (provider) PurchaseOrderSRMPricingSimu-
lateQueryResponse_In lateQueryResponse_Out
PurchaseOrderERPContractRe- Asynchronous call (provider) PurchaseOrderERPContractRe-
leaseNotication_In leaseNotication_Out
PurchasingContractSRMArchiv- Synchronous call (consumer) PurchasingContractSRMArchiv-
ingCheckQueryResponse_Out ingCheckQueryResponse_In

Procedure
1. Start the SAP Integration Builder.
2. Choose Integration Builder: Configuration.
3. Under the Scenario tab, expand the scenario to display detailed information.

10/26/2009 PUBLIC 9/72

2 Basic Settings for Contract Management
2.3 Configuring Synchronous Services for Operational Contract Management

2.2.3 More Information About SAP NetWeaver Process

Integration

The following SAP notes apply:

n 1286936
n 884695
Run the following transactions in the SAP SRM system:
n User Maintenance (SU01)
n Role Maintenance (PFCG)
n Start Integration Builder (SXMB_IFR)
n 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):
n 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.
n 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.

10/72 PUBLIC 10/26/2009

2 Basic Settings for Contract Management
2.4 Scheduling Reports to Archive or Delete Transactional Data

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:

n Selected contract(s)
n Mass change methods and filters
n Messages that occurred during the simulation step (if carried out)
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 :
n Process Condition Types
n Process Calculation Schema
n Process Condition Groups
n 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 .

10/26/2009 PUBLIC 11/72

2 Basic Settings for Contract Management
2.6 Alert Settings

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:
n Define Events
n 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 .

12/72 PUBLIC 10/26/2009

2 Basic Settings for Contract Management
2.6 Alert Settings

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.

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:
n The validity of the contract has almost expired.
n The release quantity is approaching the target quantity.
n 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 .

10/26/2009 PUBLIC 13/72

2 Basic Settings for Contract Management
2.7 Setting Up TREX Server and TREX Search

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.
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.

14/72 PUBLIC 10/26/2009

2 Basic Settings for Contract Management
2.7 Setting Up TREX Server and TREX Search

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
n 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) .
n After installing the TREX Server you have completed the following:
l 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>
password=<password for SRM Server user>
l After manually adding entries to the TREXPreprocessor.ini file you have restarted the
TREX preprocessor.

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.

10/26/2009 PUBLIC 15/72

2 Basic Settings for Contract Management
2.8 Workflow Settings for Business Scenarios

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:
n 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.
The process-controlled workflow framework is the default framework in the SAP SRM system.
n 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:
n 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.

16/72 PUBLIC 10/26/2009

2 Basic Settings for Contract Management
2.8 Workflow Settings for Business Scenarios

n 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 .
n 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:
Setting Up Application-Controlled Workflow for Confirmations and Invoices [external document]
Setting Up Application-Controlled Workflow for Strategic Sourcing [external document]
Setting Up Application-Controlled Workflow for Operational Contract Management [page 17]

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
n Customize SAP Business Workflow Automatically
n 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].

10/26/2009 PUBLIC 17/72

2 Basic Settings for Contract Management
2.8 Workflow Settings for Business Scenarios

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 Event Linkage Start Conditions
Belonging to (by Default) (by Default)
Business Object Activated Activated 1) 2)
BUS2000113 SAVED/ WS14000086 Yes No
(Contract) CHANGEVER- (auto approval) No No
SIONSAVED WS14000088
(one-step approval)
BUS2200 (RFx) SAVED/ WS14500026 (auto Yes No
CHANGEVER- approval) No No
SIONSAVED WS14500027
(one-step approval)
BUS2202 (Supplier TOBEACCEPTED WS79000010 (auto Yes No
Quote) approval) No No
WS79000002
(one-step approval)

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:

18/72 PUBLIC 10/26/2009

2 Basic Settings for Contract Management
2.8 Workflow Settings for Business Scenarios

Business Object Triggering Events Workflow Event Linkages Start Conditions

(BO) Template (by Default) Required? 3)
Activated?
BUS2000113 ALERTBUSINESS- WS10400022 No No
(Contract) WAREHOUSE (contract alert) No Yes 3)
SAVED/ WS14000148 (n-step
CHANGEVER- approval)
SIONSAVED
BUS2202 (Supplier TOBEACCEPTED WS14500044 (n-step No Yes 3)
Quote) approval)
BUS2200 (RFx) EXTERNALAUC- WS14000091 (alert No No
TIONSTARTED workflow) No Yes 3)
SAVED/ WS14500028 (n-step
CHANGEVER- approval)
SIONSAVED

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 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 (via 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

10/26/2009 PUBLIC 19/72

2 Basic Settings for Contract Management
2.8 Workflow Settings for Business Scenarios

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 WS10400022 General task
workflow)
TS14007969 (Approval task in WS14000088 Manager role or general task
one-step approval of CTR)
TS14507918 (Send contract back to WS14000148 General task
creator)
TS14507919 (Check contract by WS14500008 Manager role or general task
reviewer)
TS14507920 (Approval task to add WS14500010 Manager role or general task
to approval of CTR)
TS14507922 (Approval task for WS14500027 Manager role or general task
one-step approval of RFx)
TS14507924 (Approval task to add WS14500022 Manager role or general task
to approval of RFx)
TS14507925 (Check RFx response WS14500023 Manager role or general task
by reviewer)
TS14507928 (Return RFx to WS14500028 General task
creator)
TS14507930 (Approval task to add WS14500040 Manager role or general task
to approval of RFx response)
TS14507931 (Check RFx response WS14500041 Manager role or general task
by reviewer)
TS14507935 (Approval task in WS14500044 Manager role or general task
n-step approval of RFx response)
TS14507937 (Return RFx response WS14500044 General task
to creator)
TS79007914 (Approval task WS79000002 Manager role
in one-step approval of RFx
response)

20/72 PUBLIC 10/26/2009

2 Basic Settings for Contract Management
2.9 Contract Configuration

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:
n WS14000086 ‒ Auto approval of contract
n WS14000088 ‒ One-step approval of contract
n WS14000145 ‒ N-step approval of contract
n WS14500026 ‒ Auto approval of RFx
n WS14500027 ‒ One-step approval of RFx
n WS14500028 ‒ N-step approval of RFx
n WS14500044 ‒ N-step approval of bid
n WS79000002 ‒ One-step approval of bid
n 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:
n WS14500010 ‒ Approval fragment to insert in approval of contract
n WS14500022 ‒ Approval fragment to insert in approval of RFx
n 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 .

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.

10/26/2009 PUBLIC 21/72

2 Basic Settings for Contract Management
2.9 Contract Configuration

Note
When creating a central contract from the sourcing application of SAP SRM or from SAP Bidding
Engine, the system uses the following logic:
n 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.
n 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 .
n 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:
n BBP_CTR_BE_CREATE in the SAP SRM system
n 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 23].

More Information
For more information, see Making Settings for Central Contracts [page 22].

2.9.2 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.

22/72 PUBLIC 10/26/2009

2 Basic Settings for Contract Management
2.9 Contract Configuration

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 SRM Server Cross-Application
of a specific business transaction. Basic Settings Define Transaction
We recommend that you use Types
the standard transaction type as
shipped.
Maintaining number ranges for This setting is mandatory. SRM Server Cross-Application
central contracts Basic Settings Number Ranges
SRM Server Number Ranges Define
Number Ranges for Purchase Contracts
Configuring the transfer of To enable the transfer of contract SRM Server Technical Basic Settings
contract data to the SAP catalog data to the SAP catalog, Define System Landscape
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.
Defining the catalog To be able to use the catalog, you SRM Server Master Data
must first define it in Customizing. Content Management Define External
Web Services

2.9.3 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)
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

10/26/2009 PUBLIC 23/72

2 Basic Settings for Contract Management
2.9 Contract Configuration

on how you can configure contract management across the SAP SRM and back-end systems, see
Configuration Options for Operational Contract Management [page 21].

Prerequisites

SAP SRM

n 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.
n 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
21]). For further details refer to step 4 of the Setting Up Organizational Data and Mapping (Master) Data
procedure (see below).
n 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.
l 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 .
l 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 .
l 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.

24/72 PUBLIC 10/26/2009

2 Basic Settings for Contract Management
2.9 Contract Configuration

Back-End System

n Release 4.6B or higher with Plug-In 2004.1

n Number range object BBP_SRV and internal number assignment for service items
n External number range for purchasing contracts
n You have worked through IDoc Customizing.

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

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

n 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:
n Contract limits
n The assignment of back-end sources of supply (contract, purchasing info record)

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
Items Determine 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.
n 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.
n 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.

10/26/2009 PUBLIC 25/72

2 Basic Settings for Contract Management
2.9 Contract Configuration

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:
n 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].
n 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.
a) 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:
n Select the Purchasing Organization checkbox.
n Enter the key of the back-end purchasing organization.
n Enter the key of the logical system (back end).
b) 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:
n Select the Purchasing Group checkbox.
n 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.
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:
n Product categories
n Products
n Condition types for normal positions
n Condition types for service positions
n Text IDs
n Transaction types

26/72 PUBLIC 10/26/2009

2 Basic Settings for Contract Management
2.9 Contract Configuration

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:
n Message type BLAORD (for purchasing contracts), Process Code BLAO and Transfer IDoc immediately
activated.
n 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].

10/26/2009 PUBLIC 27/72

2 Basic Settings for Contract Management
2.9 Contract Configuration

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 10].

2.9.4 More Information About Contract Configuration

Perform the following activities in Customizing for SAP SRM under SRM Server Cross-Application
Basic Settings :
n Switch On Version Control for Purchasing Documents
n 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 :
n Initial Upload
n Change Contract Status
n Implementation of Methods for Making Mass Changes
Run the following system transactions in SAP SRM:

28/72 PUBLIC 10/26/2009

2 Basic Settings for Contract Management
2.10 Settings for Analytics in Contract Management

n WE20
n WE21

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
n 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 .
n 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

10/26/2009 PUBLIC 29/72

2 Basic Settings for Contract Management
2.10 Settings for Analytics in Contract Management

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

30/72 PUBLIC 10/26/2009

3 Operational Contract Management

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.
The SAP SRM 7.0 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. Define discounts based on released values
5. Activate contract upload to catalog
6. Complete contract
7. Release contract

10/26/2009 PUBLIC 31/72

3 Operational Contract Management
3.2 Developing Contracts

8. Approve contract
9. Distribute contract to SAP ERP
10. Distribute contract to SAP SRM
11. Distribute scheduling agreement to SAP ERP
12. Group back-end contract
13. Output contract
14. Process workload reassignment
15. Change contract
You can find a process description in SAP Solution Manager under <project name> Scenarios
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:
n Authorization object BBP_CTR_2: 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.
n 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.

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.

32/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

Note
You can only assign authorization to the activity field in the authorization object BBP_CTR_2.
Authorization for the other fields, for example the sections field, should be maintained either in
the authorization object BBP_PD_CTR or in the required roles.

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:
n Main Information
n Documents
n Conditions
All the users assigned to the role operational purchaser can create, display, and change a central
contract but they cannot do the following:
n Delete a central contract
n Grant authorization to other users for a central contract
n View or create a confidential contract/central contract

3.2.1.1.2 Assigning Authorizations

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.

10/26/2009 PUBLIC 33/72

3 Operational Contract Management
3.2 Developing Contracts

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).
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 can use this process step to configure all the activities required to upload the 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):
n BBP_CTR_INIT_UP in the SAP SRM system
n 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:

n Map the text IDs in the BAdI BBP_CTR_INIT_UP. For more information, see the sample code
provided in the BAdI Implementation.
n In the SAP SRM system, do the following:
a) For the text object BBP_PD, assign the text type K01 in the Customizing activity Define
Text Types.
b) For the text schema CTR, assign the text type K01 in the Customizing activity Define Text
Schema.

34/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

n If you want 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.

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_UP-
LOAD.
2. 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.
3. 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.
4. Define the transaction type for a contract in the customizing activity Define Transaction Types 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:
n 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).
n Implement one of the following BAdIs:
l BBP_CTR_INIT_UP in the SAP SRM system
l BBP_CTR_INIT_UP_PI in the back-end system

10/26/2009 PUBLIC 35/72

3 Operational Contract Management
3.2 Developing Contracts

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 back-end 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:
n 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 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 number ranges you created to the transaction types.
n Implement one of the following BAdIs:
l BBP_CTR_INIT_UP in the SAP SRM system
l BBP_CTR_INIT_UP_PI in the back-end system

3.2.1.3 Create Contract

To be able to create and edit contracts in the SAP Supplier Relationship Management (SRM) system,
you first need to define the number ranges that you want to use.

36/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

Prerequisites
You need to have decided which number ranges you want to use (internal or external number
ranges). You also need to have decided who, in the organizational plan, should be authorized
to create, edit, or display contracts.

3.2.1.4 Define Discounts Based on Release Values

In the standard SAP Supplier Relationship Management (SRM) system, hierarchies for contracts are
inactive. To allow purchasers to use discounts based on release values, make the required settings in
Customizing for SAP SRM under SRM Server Cross-Application Basic Settings Activate Hierarchies for
Product Categories, Suppliers, and Contracts . In addition, make all the necessary settings in Customizing for
SAP SRM under SRM Server Cross-Application Basic Settings Pricing .
If you do not define the discounts, contract releases will not lead to better conditions, the main
benefit of central contract management.

3.2.1.5 Activate Contract Upload to Catalog

3.2.1.5.1 Setting Up Contract Replication

In this section, you make the following settings that are required for the import of contracts from
client systems:
n Setting Up Key Mapping for Contract Item Categories [external document]
n Implementing BAdI to Enrich Contract Data [external document]
n Configuring the External Integration Role [external document]

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

10/26/2009 PUBLIC 37/72

3 Operational Contract Management
3.2 Developing Contracts

3.2.1.6 Complete Contract

Perform the following activities in Customizing for SAP SRM under SRM Server Cross-Application
Basic Settings :
n Enter Alert Threshold Data for Contracts
n Define Threshold Value for Background Processing
n 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.

Procedure
1. Go to the Smart Forms initial screen (transaction SMARTFORMS).
2. Enter BPP_OUT_OFFAPP.
3. Make your changes and save.

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 users within your company on the basis of this Smart
Form.

38/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

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.
3. Make your changes and save.

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:
n RFx
n RFx response
n Auction
n Purchase order
n 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
1. Go to the Smart Forms initial screen (transaction SMARTFORMS).
2. Enter BBP_OUTPUT_COVER.
3. Make your changes and save.

10/26/2009 PUBLIC 39/72

3 Operational Contract Management
3.2 Developing Contracts

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.

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 :
n Business Workflow Application-Controlled Workflow Customer Enhancement of Offline Approval
n 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 :
n PRI
n SF_HEADER
n SF_FOOTER
n SF_GRAPHIC
For more information about making entries for attributes, see User Attributes in SAP SRM [page 40].

3.2.1.8.2 User Attributes in SAP SRM

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

40/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

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 Definition System-Dependent
Example Value
ACS System alias for Specifies the back-end
accounting systems system where the account
Example value: assignment is checked.
ABCCLNT123 This attribute is required
for:
n Invoices without
purchase order
reference
n Local invoices
(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 address Default ship-to party
Example value: 12345 address in purchase order.
Enter at least one ship-to
address and set it as the
default address.
AN1 Asset Specifies the asset in
Example value: ABC- the back-end system.
CLNT123\000000001111 Default value for account
assignment when
creating shopping cart or
lean purchase order.

10/26/2009 PUBLIC 41/72

3 Operational Contract Management
3.2 Developing Contracts

AN2 Asset subnumber Defines the asset

Example value: sub-number in the
Q4CCLNT300\1234 back-end system. Default
value for account
assignment when
creating shopping cart or
lean purchase order.
ANK Asset class Defines the asset class
Example value: in the back-end system.
QW4CLNT100\00001000 Default value for account
assignment when
creating shopping cart or
lean purchase order.
ANR Order Defines the order in
Example value: ABC- the back-end system.
CLNT123\000000000040 Default value for account
assignment when
creating shopping cart or
lean purchase order.
APO Sales order item Defines the sales order
Example value: item in the back-end
Q4CCLNT300\123456 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 order Specifies the sales
Example value: ABC- order in the back-end
CLNT123\000000000333 system. Default value
for account assignment
when creating shopping
cart or lean purchase
order.

42/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

BSA Transaction type: Defines the transaction

Shopping cart follow-on type in the respective
document system for follow-on
Example value: documents from
ABCCLNT123\ECA3 shopping carts.
The attribute needs to
be defined once per
system, for the local SAP
SRM system and for
all connected back-end
systems.
BUDGET User budget Amount available to an
employee for purchases.
Required for the Purchasing
Budget Workflow [external
document].
BUK Company code Company code in the
Example value: back-end system.
QW4CLNT100\1000 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 type Defines the type of
Example value: goods movement in
ABCCLNT123\123 the back-end system.
This value is required
if reservations are to be
created in the back-end
system.

10/26/2009 PUBLIC 43/72

3 Operational Contract Management
3.2 Developing Contracts

CAT Catalog ID Defines the catalogs to

Example value: which a user has access.
MDMCA30 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 center Defines the cost center
Example value: in the back-end system.
ABCCLNT123\0000001000 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: Transaction Type for
Contract Contract
CUR Local currency Default currency of the
Example value: EUR user

44/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

DP_PROC_TY Transaction type: Direct Specifies the transaction

material type that is used when
Example value: ECDP 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 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 Obsolete from SRM 7.0
partner
Example value:
http://abc.firma.com/wgate/
FORWARD_WI Flag: Forward work item Indicator: Specifies
Example value: X whether work items
are to be forwarded as
e-mails.

10/26/2009 PUBLIC 45/72

3 Operational Contract Management
3.2 Developing Contracts

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 This indicator specifies
group 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.

46/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

IS_POR Indicator: Purchasing This indicator specifies

organization 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 user Obsolete from SRM 7.0
Example value:
http://abc.firma.com/wgate/
KNT Account assignment Default value for account
category assignment when
Example value: CC 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 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.

10/26/2009 PUBLIC 47/72

3 Operational Contract Management
3.2 Developing Contracts

NET Network Specifies the network

Example value: ABC- in the back-end system.
CLNT123\000000600003 Default value for account
assignment when
creating shopping cart or
lean purchase order.
PM_ARWRK Plant for work center Plant in which the
Example value: executing work center is
ABCCLNT123\1234 located.
This attribute is used as a
selection criterion when
searching for orders in the
back-end system.
PM_AUART Order type Order types distinguish
Example value: orders according to
ABCCLNT123\PM01 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 account Default value for the
Example value: G/L account in the
ABCCLNT123\417000 component detail data.
PM_IPHAS Phase Phases subdivide the life
Example value: cycle of an order into
ABCCLNT123\0 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 plant Plant at which
Example value: maintenance tasks are
ABCCLNT123\1234 planned and prepared.
This attribute is used as a
selection criterion when
searching for orders in the
back-end system.

48/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

PM_PUR_GRP PM purchasing group Number of the

Example value: organizational unit
ABCCLNT123\001 that is indicated as the
purchasing group in
the organizational plan.
Default value in the
component detail data.
PM_PUR_ORG PM purchasing Number of an
organization organizational unit
Example value: that is indicated as the
ABCCLNT123\1000 purchasing organization
in the organizational
plan. Default value in the
component detail data.
PM_SWERK Maintenance plant Plant at which the
Example value: technical objects of a
ABCCLNT123\1234 company are installed.
This attribute is used as a
selection criterion when
searching for orders in the
back-end system.
PM_VAWRK Plant for main work Plant at which the main
center work center entered is
Example value: located.
ABCCLNT123\1234 This attribute is used as a
selection criterion when
searching for orders in the
back-end system.
PM_WGR PM material group Indicates the key of the
Example value: material group that
ABCCLNT123\000000001 unites materials and
services with the same
properties. Default value
in the component detail
data.
PM_WRK Plant of the component Plant at which the
Example value: component required
ABCCLNT123\1000 to execute the order
(reservation or
requirement request)
is planned. Default value
in the component detail
data.
This is a mandatory
attribute.

10/26/2009 PUBLIC 49/72

3 Operational Contract Management
3.2 Developing Contracts

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 printer Printer name
Example value: PRINTER
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.

50/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

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 Number of an
organization organizational unit
that is indicated as the
purchasing organization
in the organizational
plan.
This attribute is
simulated. You define
the ID and the associated
system on the Function tab.
REQUESTER Goods recipient Indicates the
Example value: See organizational units
definition 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

10/26/2009 PUBLIC 51/72

3 Operational Contract Management
3.2 Developing Contracts

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 dened the
necessary plants. You
use this attribute to
dene these plants in
the organizational plan.
You enter plants as fol-
lows: <type_BP><part-
ner_num-
ber_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.

52/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

RESP_PRGRP Purchasing group Number of the

responsible 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 Number of the product
responsible 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 role Indicates the role of
Example value: the user, for example
/SAPSRM/EMPLOYEE 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.

10/26/2009 PUBLIC 53/72

3 Operational Contract Management
3.2 Developing Contracts

SF_GRAPHIC SAP Smart Forms: Defines the company logo

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: Header Defines the header to
Example value: be used when purchase
BBP_COMPANY 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 approver Specifies the approver
Example value: used in workflows based
USMANAGER1 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 alias Defines the systems to be
Example value: searched to find purchase
ABCCLNT123 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

54/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

Settings Define Basic

Settings.
TEND_TYPE Transaction type: Bid Specifies the transaction
invitation type for bid invitations
Example value: BID 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 group Defines the tolerance
Example value: CONF 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 Specifies the back-end
the vendor system where the account
Example value: assignment is checked.
ABCCLNT123 This attribute is required
for:
n Invoices without
purchase order
reference
n Local invoices.
We recommend that
you define this attribute
at a high level in your
organizational plan.

10/26/2009 PUBLIC 55/72

3 Operational Contract Management
3.2 Developing Contracts

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.
VENDOR_SYS System alias for vendor Defines the systems to be
Example value: searched to find purchase
ABCCLNT123 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.

56/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

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.

Procedure
1. 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:
n RFx
n RFx response
n Auction
n Purchase order
n 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
1. Go to the Smart Forms initial screen (transaction SMARTFORMS).
2. Enter BBP_OUTPUT_COVER.
3. Make your changes and save.

10/26/2009 PUBLIC 57/72

3 Operational Contract Management
3.2 Developing Contracts

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.

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
1. Go to the Smart Forms initial screen (transaction SMARTFORMS).
2. Enter BBP_CONTRACT.
3. Make your changes and save.

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

3.2.1.8.6 More Information About Outputting 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.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:

58/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

n /SAPSRM/PDO_AO_CTR_MASS for business logic

n /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:
n Component PMNT_TRMS_OLD is used to store the old payment term value
n Component PMNT_TRMS_NEW is used to store the new payment term value
n 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.

10/26/2009 PUBLIC 59/72

3 Operational Contract Management
3.2 Developing Contracts

Create a Web Dynpro component

n Create a new Web Dynpro component in the Z or Y namespace and implement the interface
/SAPSRM/WDI_CTR_MC
n 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=>wd-
ctx_<node name>)
n Create a view and an inbound plug in the view. Embed the view to the window.
n 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.
n Create an action ACTIONREJ_CHNG in the view
Method ONACTIONACTIONREJ_CHNG is created automatically.
n Implement the following code in the method:
wd_comp_controller->fire_reject_changes_evt ( )
n 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.

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.

60/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.2 Developing Contracts

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:
n Your change method is listed in the change methods table that is displayed in step 2 of the
contract mass update transaction
n 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
n 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
1. Go to the Smart Forms initial screen (transaction SMARTFORMS).
2. Enter BBP_CTR_MASS_END.
3. Make your changes and save.

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 users within your company after they have performed
or attempted to perform mass changes within the SAP SRM system.

10/26/2009 PUBLIC 61/72

3 Operational Contract Management
3.3 Processing Contracts and Sourcing Rules in ERP

3.2.1.9.3 More Information About Changing Contracts

For information about Smart Forms, see SAP Help Portal at http://help.sap.com SAP NetWeaver
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
You can find a process description in SAP Solution Manager under <project name> Scenarios
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
You can find a process description in SAP Solution Manager under <project name> Scenarios
Operational Contract Management Business Processes Negotiating Contracts . Select the Documentation tab.

62/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.4 Negotiating Contracts

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.

Note
These settings apply identically to the negotiation of global outline agreements.

You can set up contract negotiation in SAP SRM in one of the following ways:
n 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 .
n Using transaction PPOMA_BBP and defining the following user attributes in the organizational
plan:
l TEND_TYPE
Determines the transaction type for RFxs
l CT_PROC_TYPE
Determines the transaction type for purchase contracts
When using the negotiate function the system always creates an RFx. Within the related bid,
submitted by the bidder, the system offers the following options to conclude the process:
n Update the contract that is currently used
n 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 Becomes a Contract indicator in the customizing activity Define Transaction Types,
under the Process Control section of the view Transaction Type Details.

10/26/2009 PUBLIC 63/72

3 Operational Contract Management
3.5 Processing Delivery Schedules

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:
n Business transaction category: BUS2000113
n Transaction type (as selected above): CCTR
n Subsequent object type: BUS2200
n 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:
n Business transaction category: BUS2200
n Transaction type (as selected above): RFCR
n Subsequent object type: BUS2000113
n 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

64/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.6 Searching for Sources of Supply Centrally

You can find a process description in SAP Solution Manager under <project name> Scenarios
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
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:

n SRM Server Business Add-Ins Changes to Purchasing Document Data
n SRM Server Business Add-Ins RFx Control of RFx Publication
n SRM Server Business Add-Ins RFx Subsequent Split of Grouping
n SRM Server Cross-Application Basic Settings Configure Priorities
n SRM Server Business Add-Ins Interface Configuration Appearance of Priorities
n SRM Server Business Add-Ins Sourcing Redetermination of the Contract To Be Used (Quota Arrangement)
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

10/26/2009 PUBLIC 65/72

3 Operational Contract Management
3.7 Monitoring Contracts

2. Process reports in SAP NetWeaver BW

You can find a process description in SAP Solution Manager under <project name> Scenarios
Operational Contract Management Business Processes Monitoring Contracts . Select the Documentation tab.

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
needs of your company or your corporate design.

Procedure
1. Go to the Smart Forms initial screen (transaction SMARTFORMS).
2. Enter BBP_OUT_EXCEPTION.
3. Make your changes and save.

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 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:

n SRM Server Cross-Application Basic Settings Define Transaction Types
n 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 :
n Carry out SRM Product Category Matching
n Carry out SRM Business Partner Matching

66/72 PUBLIC 10/26/2009

3 Operational Contract Management
3.7 Monitoring 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 .

10/26/2009 PUBLIC 67/72

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>”.
Example Arrows separating the parts of a navigation path, for example, menu options
Example
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 n Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
n Cross-references to other documentation or published works
Example n Output on the screen following a user action, for example, messages
n Source code or syntax quoted directly from a program
n 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

68/72 PUBLIC 10/26/2009

 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

© Copyright 2009 SAP AG. All rights reserved.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
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 is a registered trademark of Oracle Corporation.
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.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented
by Netscape.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 in several other countries all over the world. 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.
This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2
from Michael Kay (http://saxon.sf.net/), XSLT version 1.

10/26/2009 PUBLIC 69/72

Disclaimer
Some 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.

Documentation in the SAP Service Marketplace

You can find this document at the following address:
http://service.sap.comhttps://service.sap.com/srm-instinstguides

70/72 PUBLIC 10/26/2009

This page is left blank for documents
that are printed on both sides.
 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

© Copyright 2009 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.