ticm srm basic settings
DESCRIPTION
SRM configTRANSCRIPT
Basic Settings for SAP Enhancement Package 3 for SAP SRM 7.0Based on SAP Solution Manager Content
Target Audience ■ System Administrators ■ Consultants
PUBLICDocument version: 1.0 – 2013-08-13
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 1853038.
Version Date Description
1.0 2013-08-13 Initial Version
2/148 PUBLIC 2013-08-13
Table of Contents
Chapter 1 Important Information About This Document . . . . . . . . . . . . . . . . . . . . . 9
Chapter 2 Basic Settings for SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 3 Flexible Deployment Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1 Portal-Independent Navigation Frame and Inbox . . . . . . . . . . . . . . . . . . . . . . 13
3.1.1 Portal-Independent Navigation Frame Configuration . . . . . . . . . . . . . . . . . . . 13
3.1.2 Inbox Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2 BW-Independent Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2.1 Configuring BW-Independent Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3 PI-Independent Enterprise Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.3.1 Configuration of PI-Independent Enterprise Services . . . . . . . . . . . . . . . . . . . . 16
3.3.2 More Information About PI-Independent Enterprise Services . . . . . . . . . . . . . 18
Chapter 4 SAP NetWeaver Process Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1 Configure Business Systems with an Integration Engine . . . . . . . . . . . . . . . . . 19
4.1.1 Setting Up Business Systems Landscapes for SAP SRM . . . . . . . . . . . . . . . . . . . 19
4.1.2 More Information About Business System Configuration with Integration
Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.2 Define Business Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.2.1 Working with Business Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.3 Check Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.3.1 Checking SAP NetWeaver PI Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.3.2 More Information About Checking Configuration . . . . . . . . . . . . . . . . . . . . . 21
4.4 Configure IDoc Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.4.1 Configuring the IDoc Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.4.2 Configuring the IDoc Adapter for Supplier Self-Services . . . . . . . . . . . . . . . . . 22
4.4.3 More Information About Configuring IDoc Adapter . . . . . . . . . . . . . . . . . . . . 23
4.5 Configuring the Advanced XML Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.6 More Information About SAP NetWeaver Process Integration . . . . . . . . . . . . . 23
2013-08-13 PUBLIC 3/148
Chapter 5 Customizing Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1 Synchronizing Customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 6 System Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1 Automated Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1.1 Automated Configuration of the Portal Systems . . . . . . . . . . . . . . . . . . . . . . . 27
6.1.2 Automated Configuration Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.2 Back-End Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2.1 Defining Back-End Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.3 Logical Systems and RFC Connections in the SAP SRM Landscape . . . . . . . . . 29
6.3.1 Defining Logical Systems and RFC Destinations . . . . . . . . . . . . . . . . . . . . . . . . 29
6.3.2 Create Distribution Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.3.2.1 Creating a Distribution Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.4 Logical Systems and RFC Connections in the SAP ERP Landscape . . . . . . . . . . 33
6.5 Middleware Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.5.1 Defining Middleware Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.5.2 Specify Back-End System for Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.5.2.1 Specifying Back-End Systems for Download . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.5.3 Defining Settings in SAP SRM and in the Back-End System . . . . . . . . . . . . . . . 35
6.5.3.1 Defining Download Settings in the Back-End System . . . . . . . . . . . . . . . . . . . 35
6.5.3.2 Check Users of Adapter Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.5.3.2.1 Checking Users of Adapter Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.5.3.3 Check Definitions of RFC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.5.3.3.1 Checking RFC Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.5.3.4 Checking OLTP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.5.3.4.1 Checking OLTP Parameters for Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.5.3.5 Check Subscription Table for Upload and Download Objects . . . . . . . . . . . . . 39
6.5.3.5.1 Checking Subscription Table for Upload and Download Objects . . . . . . . . . . . 39
6.5.3.6 Check Middleware Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.5.3.6.1 Checking Middleware Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.5.4 Define Settings for Standalone Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.5.4.1 Defining Settings for SAP SRM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.6 Aligning Units of Measurement, Currencies, and Exchange Rates . . . . . . . . . . 40
6.7 Configuration Engine (CE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.7.1 Setting Up Configuration Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.7.2 More Information About Configuration Engine (CE) . . . . . . . . . . . . . . . . . . . 42
6.8 Technical Settings for E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4/148 PUBLIC 2013-08-13
6.8.1 Defining Technical Settings for E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.8.2 Quick Guide to SMTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.9 Setting Control Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.10 Jobs for Scheduling Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.10.1 Scheduling Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 7 Master Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.1 Replication of Materials from ERP Back-End Systems . . . . . . . . . . . . . . . . . . . 49
7.2 Customizing Material Replication in SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . 49
7.3 Downloading Customizing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7.4 Materials and Service Master Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.4.1 Downloading Business Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.4.2 More Information About Materials and Service Master Download . . . . . . . . . 53
7.5 Checking Downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Chapter 8 Organizational Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.1 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.1.1 Organizational Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.1.1.1 Creating the Organizational Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.1.1.2 Making Settings for Locations and External Business Partners . . . . . . . . . . . . . 57
8.1.1.3 Defining the Supplier Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.1.1.4 More Information About Organizational Structure . . . . . . . . . . . . . . . . . . . . . 59
8.1.2 Creating Portal Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.1.3 Maintain User Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
8.1.3.1 User Attributes in SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
8.1.3.2 Defining User Attributes in the Organizational Plan . . . . . . . . . . . . . . . . . . . . 69
8.1.3.3 Maintaining the User Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
8.1.4 User Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
8.1.5 More Information About User Management . . . . . . . . . . . . . . . . . . . . . . . . . . 74
8.2 Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
8.2.1 Harmonized Procurement Roles for SAP ERP and SAP SRM . . . . . . . . . . . . . . 74
8.2.2 Regenerating Role Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
8.2.3 Maintaining the User Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
8.2.4 More Information About Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
8.3 Integration of Business Partners into Organizational Management . . . . . . . . . 78
8.3.1 Setting Up Integration with Organizational Management . . . . . . . . . . . . . . . . 78
8.3.2 Scheduling Periodic Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
2013-08-13 PUBLIC 5/148
8.3.3 More Information About Integrating Business Partners into Organizational
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Chapter 9 Locations and Business Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
9.1 Making Settings for Locations and External Business Partners . . . . . . . . . . . . . 57
9.2 Partner Address Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
9.2.1 Managing Business Partner Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
9.3 Number Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
9.3.1 Defining Number Ranges for Business Partners . . . . . . . . . . . . . . . . . . . . . . . . 83
9.4 Locations and Business Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Chapter 10 Supplier Master Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
10.1 Settings for Supplier Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
10.1.1 Locked Suppliers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
10.1.2 Creating and Registering Root Supplier Groups . . . . . . . . . . . . . . . . . . . . . . . 85
10.1.3 More Information About Settings for Supplier Synchronization . . . . . . . . . . . 86
10.2 Replicating Supplier Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
10.3 Checking Downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Chapter 11 Cross-Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
11.1 Defining Configurable Item Numbering Scheme . . . . . . . . . . . . . . . . . . . . . . . 89
11.2 Activating Revision Level Field for Document . . . . . . . . . . . . . . . . . . . . . . . . . 89
11.3 Output Actions and Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
11.3.1 Defining Actions for Document Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
11.3.2 Condition-Dependent Document Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
11.4 Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
11.4.1 Uploading Product Category Hierarchy Files from External
Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
11.4.2 More Information About Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
11.5 Number Ranges for Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
11.5.1 Defining Number Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
11.5.2 More Information About Number Ranges for Documents . . . . . . . . . . . . . . . 92
11.6 Text Schema and Text Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
11.7 Define Transaction Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
11.8 Activate Extended Classic Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
11.8.1 Setting Up Extended Classic Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
11.9 Business Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
11.9.1 Select Workflow Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6/148 PUBLIC 2013-08-13
11.9.2 Process-Controlled Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
11.9.2.1 Approval Process Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
11.9.2.2 Business Configuration Sets for SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
11.9.2.3 Define Technical Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
11.9.2.3.1 Technical Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
11.9.2.4 Define Settings for Business Rule Framework . . . . . . . . . . . . . . . . . . . . . . . . . 99
11.9.2.4.1 Business Rule Framework Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
11.9.2.4.2 Creating BRF Expressions for SRM Approval Processes . . . . . . . . . . . . . . . . . 100
11.9.2.5 Define Business Process Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
11.9.2.5.1 Process-Controlled Workflow Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
11.9.2.5.2 Configuring Parallel Approval with Overlapping Responsibility . . . . . . . . . . 106
11.9.2.5.3 More Information About Defining Business Process
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
11.9.3 Application-Controlled Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
11.9.3.1 Setting Up Business Workflow for Application-Controlled
Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
11.9.3.2 Additional Information: Maintaining Guided Procedures Gateway . . . . . . . . 116
11.9.3.3 More Information About Application-Controlled Workflows . . . . . . . . . . . . 117
11.9.4 Universal Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
11.10 Alert Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
11.10.1 Configuring SRM Alert Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
11.11 Settings for Tax Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
11.11.1 Making Settings for Tax Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
11.11.2 Tax Calculation in the SAP ERP Financial Accounting System . . . . . . . . . . . 123
11.11.3 More Information About Settings for Tax Calculation . . . . . . . . . . . . . . . . . . 123
11.12 Settings for Account Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
11.12.1 Making Settings for Account Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
11.12.2 More Information About Settings for Account Assignment . . . . . . . . . . . . . . 125
11.13 Payment Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
11.13.1 Creating Payment Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
11.14 Create Incoterms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
11.15 Pricing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
11.15.1 Set Up Simplified Pricing for Classic Scenario . . . . . . . . . . . . . . . . . . . . . . . . . 126
11.15.1.1 Setting Up Configuration Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
11.15.2 More Information About Pricing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
11.16 Define Objects in the Back-End System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
11.17 Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
11.17.1 Setting Up Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
2013-08-13 PUBLIC 7/148
11.17.2 Configuring Attachment Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
11.17.3 More Information About Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
11.18 Start Application Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
11.19 Message Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
11.20 Background Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
11.21 Integration with Other SAP Components . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
11.21.1 Integration with SAP Records Management . . . . . . . . . . . . . . . . . . . . . . . . . . 130
11.21.1.1 Integration with SAP Records Management . . . . . . . . . . . . . . . . . . . . . . . . . . 130
11.21.1.2 Making Settings for ArchiveLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
11.21.1.3 Making Settings for Knowledge Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
11.21.1.4 Making Settings for SAP Records Management . . . . . . . . . . . . . . . . . . . . . . . 131
11.21.1.5 More Information About Settings for SAP Records Management . . . . . . . . . 133
11.21.1.6 Defining Settings for SAP SRM Integration . . . . . . . . . . . . . . . . . . . . . . . . . . 133
11.21.1.7 More Information About Settings for SAP SRM Integration . . . . . . . . . . . . . 135
11.21.2 Integration with SAP ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
11.21.2.1 More Information About Contract Handling for Invoices . . . . . . . . . . . . . . . 135
11.21.2.2 More Information About Contract Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
11.21.2.3 More Information About Links to SAP ERP Documents . . . . . . . . . . . . . . . . 136
11.21.3 Catalog Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
11.21.3.1 More Information About Catalog Integration . . . . . . . . . . . . . . . . . . . . . . . . 136
11.22 Digital Signatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
11.23 User Experience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
11.24 POWL and Advanced Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
11.25 Optimistic Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
11.26 Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
11.26.1 More Information About Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
11.27 Switch on Version Control for Purchasing Documents . . . . . . . . . . . . . . . . . 137
11.27.1 More Information About Switching on Version Control for Purchasing
Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
11.28 Define Status Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
11.28.1 More Information About Defining Status Schema . . . . . . . . . . . . . . . . . . . . . 137
11.29 Activate Direct Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Chapter 12 Component Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
12.1 Select Additional Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
12.2 Defining User Attributes in the Organizational Plan . . . . . . . . . . . . . . . . . . . . 69
8/148 PUBLIC 2013-08-13
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 1853038 and the SAP
SRM master guide at http://service.sap.com/instguides under Installation and Upgrade
Guides SAP Business Suite Applications SAP SRM SAP SRM Server 7.13
Business Functions
SAP enhancement package 3 for SAP Supplier Relationship Management 7.0 (SRM 7.0) includes the
following Business Functions:
■ SRM, Strategic Sourcing Innovations
■ SRM, Catalog Innovations
■ SRM, Approval Process
■ SRM, Continuous Innovations
■ SRM, Implementation Simplification
■ SRM, Service Procurement Innovations
■ SRM, PI-Independent Enterprise Services
■ SRM, Supplier Collaboration
■ SRM, Self-Service Procurement
■ SRM, Analytics
■ SRM, Strategic Sourcing Innovations 2
■ SRM, Analytics 2
■ SRM Continuous Innovations 2
■ SRM Catalog Innovations 2
■ SRM, Supplier Collaboration 2
1 Important Information About This Document
2013-08-13 PUBLIC 9/148
For more information about these business functions, see SAP Help Portal at http://help.sap.com
SAP Supplier Relationship Management Business Functions and Customizing Switches .
1 Important Information About This Document
10/148 PUBLIC 2013-08-13
2 Basic Settings for SAP SRM
This section of the SAP Solution Manager structure contains basic configuration steps that apply to all
SAP SRM scenarios.
NOTE
For each client of each system that is part of your SAP SRM system landscape and is based on SAP
NetWeaver (for example, SAP SRM Server, SAP Business Information Warehouse), ensure that
you have performed all SAP NetWeaver configuration steps (see SAP Solution Manager
Configuration ). For basic configuration steps regarding catalog content management using the
SRM-MDM Catalog, see Basic Settings for SRM-MDM Catalog.
2 Basic Settings for SAP SRM
2013-08-13 PUBLIC 11/148
This page is left blank for documents that are printed on both sides.
3 Flexible Deployment Variants
3.1 Portal-Independent Navigation Frame and Inbox
3.1.1 Portal-Independent Navigation Frame Configuration
Using the Portal-independent navigation frame, you can use SAP Supplier Relationship Management
(SAP SRM) applications without using SAP NetWeaver Portal.
Procedure
To configure the Portal-independent navigation frame, proceed as follows:
1. In Customizing for SAP Supplier Relationship Management, define the following settings:
■ Activate the Portal-independent navigation frame in Customizing for SAP Supplier
Relationship Management under SRM Server Technical Basic Settings Portal-Independent
Navigation Frame Activate/Deactivate Portal-Independent Navigation Frame .
■ Define an RFC connection of type H (HTTP) to the SAP ERP back-end system under SRM
Server Technical Basic Settings Define RFC Destinations , or use transaction SM59. The name of
the connection must end with one of the following character sequences:
● For a non-secure connection, use_HTTP.
Example: SAP_ERP_HTTP.
● For a secure connection, use _HTTPS.
Example: SAP_ERP_HTTPS.
■ Enter the HTTP connection defined above, but without the suffix, in the Customizing activity
Define System Landscape in the System Alias for POWL Navigation field. Enter, for example, SAP_ERP.
■ Activate the Internet Communication Framework (ICF) service /sap/bc/nwbc/srm in
transaction HTTP Service Hierarchy Maintenance (SICF). Use this service to start NetWeaver
Business Client (NWBC) for HTML.
2. If you want to use SAP NetWeaver Business Warehouse (SAP NetWeaver BW) together with the
Portal-independent navigation frame, define your SAP NetWeaver BW system in Customizing for
SAP Supplier Relationship Management under SRM Server Technical Basic Settings Define System
Landscape . Make the following entries:
■ In the Logical System field, enter SAP_BW. This entry must be identical with the system alias that
you defined in Customizing for the launchpad. For more information about the launchpad,
see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com SAP
NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology UI Technology
Web UI Technology Floorplan Manager for Web Dynpro ABAP Launchpad .
3 Flexible Deployment Variants
3.1 Portal-Independent Navigation Frame and Inbox
2013-08-13 PUBLIC 13/148
■ In the System Alias for POWL Navigation field, enter SAP_BW.
3. For SAP NetWeaver BW, as for all systems that you define in the Customizing activity Define System
Landscape, you must configure an RFC connection of type H (HTTP) under SRM Server Technical
Basic Settings Define RFC Destinations , or use transaction SM59. The name of the connection must
end with one of the following character sequences:
■ For a non-secure connection, use _HTTP.
Example: SAP_BW_HTTP.
■ For a secure connection, use _HTTPS.
Example: SAP_BW_HTTPS.
More Information
The Portal-independent navigation frame uses a special inbox. For more information about how to
configure the Portal-independent inbox, see Inbox Configuration [page 14].
3.1.2 Inbox Configuration
You can run your SAP Supplier Relationship (SAP SRM) system using the Portal-independent
navigation frame instead of SAP NetWeaver Portal. If you do so, instead of the universal worklist (UWL),
an inbox is used that is based on the personal object worklist (POWL). For this inbox, you can, for
instance, define your own settings for tasks and actions and you can set the refresh interval for the
POWL. You can also use the generic POWL configuration options.
Prerequisites
■ You have activated the Portal-independent navigation frame in Customizing for SAP SRM under
SRM Server Technical Basic Settings Portal-Independent Navigation Frame Activate/Deactivate Portal-
Independent Navigation Frame . The inbox is then used automatically.
■ If you use SAP NetWeaver Portal, you have adjusted the required Portal roles according to your
needs. The Portal roles contain both the POWL-based inbox and the UWL. If you choose to use the
inbox, you must remove the UWL from the Portal roles. However, you can also continue to use
the UWL in SAP NetWeaver Portal. You must then remove the inbox from the Portal roles.
Process
To configure the inbox, perform the following activities in Customizing for Cross-Application
Components under Processes and Tools for Enterprise Applications Inbox :
■ Define Tasks and Actions
You can define actions and their properties, define default actions for specific tasks, and assign
custom attributes and actions to tasks. You can change existing tasks and actions or define new
ones. For more information, see the documentation for the Customizing activity.
■ Set Refresh Interval
3 Flexible Deployment Variants
3.1 Portal-Independent Navigation Frame and Inbox
14/148 PUBLIC 2013-08-13
The inbox uses the personal object worklist (POWL) to assemble the list of work items, alerts, and
notifications. You can set an interval for automatic refresh of the POWL.
■ Hide Task Details Area
You can hide the task details displayed in the area below the task list in the inbox.
■ Assign Task IDs to POWL Types
When you assign task IDs to POWL types, the assigned task IDs are displayed in a dropdown box
when defining a query in the POWL. This enables the user to create a worklist for work items with
a specific task ID.
More Information
■ Portal-Independent Navigation Frame Configuration [page 13]
■ For more information about the POWL, see SAP Help Portal at http://help.sap.com SAP ERP
SAP ERP Enhancement Packages SAP ERP Cross-Application Functions Cross-Application Components
General Application Functions Personal Worklist .
3.2 BW-Independent Analytics
3.2.1 Configuring BW-Independent Analytics
You can use a select number of reports in the SAP Supplier Relationship Management (SAP SRM)
system without having to install an SAP NetWeaver Business Warehouse (SAP NetWeaver BW) system.
The reports are available in SAP SRM using both the SAP NetWeaver Portal and in the Portal-
independent navigation frame.
Prerequisites
If you want to use BW-independent reports using Crystal Reports, ensure that the following software
components are available:
■ SAP NetWeaver 7.02 or higher
■ SAP GUI 7.10 or higher
■ Microsoft .NET Framework 2.0 or higher
■ Crystal Reports ALV Adapter
■ SAP Active Component Framework
Procedure
Activate BW-independent analytics in Customizing for SAP Supplier Relationship Management under
SRM Server Analytics Activate/Deactivate BW-Independent Analytics .
If you want to use Crystal Reports, perform the following activities in Customizing for SAP NetWeaver
under Application Server SAP List Viewer (ALV) :
■ You have enabled the use of Crystal Reports under Maintain Web Dynpro ABAP-Specific Settings by
selecting the Allow Crystal Reports checkbox.
3 Flexible Deployment Variants
3.2 BW-Independent Analytics
2013-08-13 PUBLIC 15/148
■ You have adapted the layout of Crystal Reports to your requirements under Manage Generic Crystal
Reports.
More Information
For more information about how to configure the Portal-independent navigation frame, see Portal-
Independent Navigation Frame Configuration [page 13].
For information about how to install Crystal Reports ALV Adapter and SAP Active Component
Framework, see SAP Note 1353044.
3.3 PI-Independent Enterprise Services
3.3.1 Configuration of PI-Independent Enterprise Services
PI-independent services use the Web Services Reliable Messaging (WSRM) protocol. For asynchronous
enterprise services with compatible signatures, WSRM enables point-to-point communication between
SAP Business Suite applications.
To use this process, you must have activated the business function Improvements for SOA Reuse Functions
(FND_SOA_REUSE_1) and you must have defined settings in Customizing under Cross-Application
Components Processes and Tools for Enterprise Applications Enterprise Services Point-to-Point Enablement for
Asynchronous Enterprise Services . The business function SRM, PI-Independent Enterprise Services (SRM_WSRM_1)
is then automatically activated.
Process
To configure WSRM, proceed as follows:
Configuring bgRFC (Background Remote Function Call)
Configure bgRFC as described on SAP Help Portal at http://help.sap.com under SAP NetWeaver
Library SAP NetWeaver by Key Capability Application Platform by Key Capabilities Platform-Wide Services
Connectivity Components of SAP Communication Technology Classical SAP Technologies (ABAP) RFC
Background Communication bgRFC (Background Remote Function Call) bgRFC Configuration .
Configuring the Web Service Runtime
Configure the Web service runtime in client 000 as well as in the production client using report
SRT_ADMIN. For more information, see SAP Help Portal at http://help.sap.com under SAP NetWeaver
Library SAP NetWeaver by Key Capability Application Platform by Key Capabilities ABAP Technology ABAP
Workbench ABAP Workbench Tools Web Services Creating Consumers/Providers for the Enterprise Services Repository
7.1 Managing the Web Service Runtime Configuring the Web Service Runtime .
SOA Manager
Use the SOA Manager (transaction code SOAMANAGER) to administer and configure service providers
and consumer proxies in both the SAP Supplier Relationship Management (SAP SRM) system and the
3 Flexible Deployment Variants
3.3 PI-Independent Enterprise Services
16/148 PUBLIC 2013-08-13
SAP ERP system. For more information about how to use the SOA Manager, see SAP Help Portal at
http://help.sap.com under SAP NetWeaver Library SAP NetWeaver by Key Capability Application
Platform by Key Capabilities ABAP Technology ABAP Workbench ABAP Workbench Tools Web Services
Working with the SOA Manager .
Proceed as follows:
1. Under Technical Administration Profile Management , you create a profile.
NOTE
Ensure that the names of the profiles and the versions are the same for provider and consumer.
2. Under Technical Administration System Connections , you create a provider system and assign a profile
to it.
NOTE
To be able to use the input help, you must have configured the Services Registry correctly.
If this is not the case, you can enter the SLD identifier manually. The SLD identifier is made
up as follows:
<Client>.SystemName.<SID>.SystemNumber.<Installation
Number>.SystemHome.<database host name>
Example: 340.SystemName.QV5.SystemNumber.0020270862.SystemHome.uxdbqv5
The WSIL URL is made up as follows:
http://<host name>:<http port>/sap/bc/srt/wsil?sap-client=<client>
Example: http://uxciqv5.wdf.sap.corp:50050/sap/bc/srt/wsil?sap-client=340
3. Under Service Administration User Account Management , you enter a service user. Ensure that this
service user has sufficient bgRFC authorization in the SAP SRM system.
4. Under Service Administration User Account Management Account Assignment , you assign a user
account to the system connection. You do so for all service interfaces and for all service groups.
5. Choose Service Administration Business Scenario Configuration and proceed as follows:
1. Choose New.
2. In step 1 (General), enter the business scenario name and description.
3. Choose Next.
4. In step 2 (Provider Side), choose Add to enter all relevant inbound services, for example:
■ PurchaseOrderERPConfirmation_In
■ PurchaseOrderERPContractReleaseNotification_In
■ PurchaseRequestERPSourcingRequest_In
■ PurchasingContractERPConfirmation_In
■ PurchasingContractSRMReplicationConfirmation_In
■ RFQRequestSUITERequest_In
■ SupplierInvoiceSUITEContractReleaseNotification_In
■ PurchaseOrderERPRequest_In_V1
5. For each of the services, choose Assign Profile to assign the profile created in step 1.
3 Flexible Deployment Variants
3.3 PI-Independent Enterprise Services
2013-08-13 PUBLIC 17/148
6. Choose Next.
7. In step 3 (Consumer Side), choose Add to enter the service group /SAPSRM/
SERVICEPROC_CLASSIC.
8. Choose Assign Business Application to assign the provider system created in step 2 to the service
group.
6. You activate the business function Improvements for SOA Reuse Functions (FND_SOA_REUSE_1).
7. You activate the support for point-to point communication. You do so in Customizing for Cross-
Application Components under Processes and Tools for Enterprise Applications Enterprise Services Point-to-
Point Enablement for Asynchronous Enterprise Services Activate Support for Point2Point Communication .
3.3.2 More Information About PI-Independent Enterprise Services
Perform the following activity in Customizing for SAP SRM: SRM Server Activate Business Functions .
3 Flexible Deployment Variants
3.3 PI-Independent Enterprise Services
18/148 PUBLIC 2013-08-13
4 SAP NetWeaver Process Integration
4.1 Configure Business Systems with an Integration Engine
4.1.1 Setting Up Business Systems Landscapes for SAP SRM
SAP Supplier Relationship Management (SAP SRM) supports various scenarios. Some of these scenarios
require SAP NetWeaver Process Integration (SAP NetWeaver PI) for inter-application communication.
To use SAP NetWeaver PI, you must define the business system landscapes for the different servers and
clients, depending on the deployment setup.
Prerequisites
You have set up the SAP NetWeaver PI system.
Procedure
1. Configure the business systems for SAP Supplier Relationship Management (SAP SRM) and
supplier self-services (SUS) if XML data is sent and received in the application server/client.
2. Configure the business system for SAP ERP 6.0 EHP 4 and higher if you have activated the business
function Procurement - SRM Integration (LOG_MM_P2PSE_1).
4.1.2 More Information About Business System Configuration with Integration Engine
For more information, see SAP Solution Manager under <project name> Configuration SAP SRM 7.0
EHP3 Basic Settings for SRM SAP NetWeaver Process Integration :
■ Configuration of Business Systems with Integration Engine
■ Configuring the Role of the Business System
■ Connecting to the Integration Server
■ Activating an HTTP Service on the Receiver System
■ Registering Queues
■ Connecting to the System Landscape Directory
■ Creating a User for the Runtime Workbench
■ Creating Optional Destinations
■ Configuring Communication and Security
Run the following transactions in SAP SRM, SUS, and SAP ERP:
■ User Maintenance (SU01)
4 SAP NetWeaver Process Integration
4.1 Configure Business Systems with an Integration Engine
2013-08-13 PUBLIC 19/148
■ Role Maintenance (PFCG)
■ RFC Destination (SM59)
■ HTTP Service Hierarchy Maintenance (SICF)
■ SLD Administration (RZ70)
■ SLD API Customizing (SLDAPICUST)
■ Integration Engine - Administration (SXMB_ADM)
4.2 Define Business Systems
4.2.1 Working with Business Systems
For more information, see SAP Solution Manager under <project name> Configuration SAP SRM 7.0
EHP3 Basic Settings for SRM SAP NetWeaver Process Integration Define Business Systems Working with Business
Systems
Run the following transaction in the SAP NetWeaver PI system: Start Integration Builder (SXMB_IFR)
4.3 Check Configuration
4.3.1 Checking SAP NetWeaver PI Settings
Procedure
Check whether you have performed the following steps for all business systems:
Activity In
You have defined a logical system using transaction SALE, as described in Customizing for SAP NetWeaver under SAP Web Application Server Application Server IDoc Interface / Application Link Enabling (ALE) Basic Settings Logical Systems
Define Logical System .You have assigned the client to the logical system, as described in Customizing for SAP NetWeaver under SAP Web Application Server Application Server IDoc Interface / Application Link Enabling (ALE) Basic Settings Logical Systems
Assign Logical System to Client
■ SAP Supplier Relationship Management (SAP SRM) and supplier self-services (SUS) for the Service Procurement scenario
■ Materials Management in SAP Enterprise Resource Planning (SAP ERP) and supplier self-services (SUS) for the Plan—Driven Procurement scenario
You have defined the XIAPPLUSER user. ■ SAP Supplier Relationship Management (SAP SRM) and supplier self-services (SUS) for the Service Procurement scenario
■ Materials Management in SAP Enterprise Resource Planning (SAP ERP) and supplier self-services (SUS) for the Plan—Driven Procurement scenario
You have assigned the roles /SAPSRM/SUS_ADMIN_SUPPLIER and
■ SAP Supplier Relationship Management (SAP SRM) and supplier self-services (SUS) for the Service Procurement scenario
4 SAP NetWeaver Process Integration
4.2 Define Business Systems
20/148 PUBLIC 2013-08-13
SAP_EC_SUS_ADMIN_VENDOR to the XIAPPLUSER user.
■ supplier self-services (SUS) for the Plan—Driven Procurement scenario
You have defined the HTTP destination to the SAP Netweaver PI system in transaction RFC Destinations (SM59).
■ SAP Supplier Relationship Management (SAP SRM) and supplier self-services (SUS) for the Service Procurement scenario
■ supplier self-services (SUS) for the Plan—Driven Procurement scenario
You have activated the PI service in transaction HTTP Service Hierarchy Maintenance (SICF).
■ SAP Supplier Relationship Management (SAP SRM) and supplier self-services (SUS) for the Service Procurement scenario
■ supplier self-services (SUS) for the Plan—Driven Procurement scenario
You have configured the Integration Engine in transaction Integration Engine - Administration (SXMB_ADM).
■ SAP Supplier Relationship Management (SAP SRM) and supplier self-services (SUS) for the Service Procurement scenario
■ supplier self-services (SUS) for the Plan—Driven Procurement scenario
You have registered the queues in transaction Integration Engine - Administration (SXMB_ADM).
■ SAP Supplier Relationship Management (SAP SRM) and supplier self-services (SUS) for the Service Procurement scenario
■ Supplier Self-Services (SUS) for the Plan—Driven Procurement scenario
You have defined the SLD access data in transaction SLD API Customizing (SLDAPICUST).
■ SAP Supplier Relationship Management (SAP SRM) and Supplier Self-Services (SUS) for the Service Procurement scenario
■ Supplier Self-Services (SUS) for the Plan—Driven Procurement scenario
You have defined the RFC destinations LCRSAPRFC and SAPSLDAPI in transaction RFC Destinations (SM59).
■ SAP Supplier Relationship Management (SAP SRM) and Supplier Self-Services (SUS) for the Service Procurement scenario
■ supplier self-services (SUS) for the Plan—Driven Procurement scenario
You have defined the SAP J2EE connection parameters for LCRSAPRFC.
SAP NetWeaver Process Integration (SAP NetWeaver PI)
You have defined a technical name, for example, QWA. System Landscape Directory (SLD)
You have defined a business system name, for example, QWA_100.
System Landscape Directory (SLD)
You have defined a back-end system, as described in Defining Back-End Systems [page 28].
■ SAP Supplier Relationship Management (SAP SRM) and supplier self-services (SUS) for the Service Procurement scenario
■ supplier self-services (SUS) for the Plan—Driven Procurement scenario
4.3.2 More Information About Checking Configuration
Run the following transaction in the SAP Supplier Relationship Management (SAP SRM) and SAP ERP
systems:
4 SAP NetWeaver Process Integration
4.3 Check Configuration
2013-08-13 PUBLIC 21/148
■ Test SLD Connection (SLDCHECK)
4.4 Configure IDoc Adapter
4.4.1 Configuring the IDoc Adapter
In this section, you configure the IDoc adapter for a Materials Management (MM) system. This allows
the Integration Server to communicate with the MM system via IDocs.
RECOMMENDATION
We recommend that you use XIAPPLUSER as the log-on user. Create the user XIAPPLUSER
with the communications user type and all profiles that are necessary to run the applications in
the MM system.
Procedure
1. Run transaction SM59 to create an RFC destination of type R/3 connection to the MM system, for
example, <MM RFC DESTINATION>.
2. Run transaction IDX1 to create a port in the IDoc Adapter corresponding to the receiver port
defined in the MM system:
■ Enter <SAP MM SID> as the port.
■ Enter the client number of the MM system.
■ Provide a short description.
■ Enter <MM RFC destination> as RFC destination.
■ Save your entries.
4.4.2 Configuring the IDoc Adapter for Supplier Self-Services
You must configure the IDoc Adapter only for the Plan-Driven Procurement and Service Procurement
Classic scenarios, as document data in IDoc format is sent to (outbound) and received from (inbound)
the SAP ERP system.
The following IDoc types are used:
■ CREMAS3
■ DELFOR02
■ DELVRY01
■ DELVRY03
■ GSVERF01
■ ORDERS02
4 SAP NetWeaver Process Integration
4.4 Configure IDoc Adapter
22/148 PUBLIC 2013-08-13
4.4.3 More Information About Configuring IDoc Adapter
For more information, see SAP Solution Manager under <project> Configuration SAP SRM 7.0 EHP3
Basic Settings for SRM SAP NetWeaver Process Integration Configure IDoc Adapter :
■ Integration Using the IDoc Adapter
■ Creating Ports
■ Maintaining the Integration Server
Run the following transaction in SAP ERP:
■ User Maintenance (SU01)
Run the following transaction in SAP NetWeaver Process Integration (SAP NetWeaver PI):
■ Meta Data Overview in IDoc Adapter (IDX2)
4.5 Configuring the Advanced XML Monitor
You use this procedure to configure the Advanced XML Monitor (/SAPSRM/ADV_XML_MONITOR), which is
an enhanced and SRM-specific version of the standard SAP NetWeaver monitor Integration Engine:
Monitor (SXMB_MONI).
Based on the SAP NetWeaver user—defined message search function, the Advanced XML Monitor
allows you to retrieve messages and, for example, check whether central contracts are correctly
distributed to SAP ERP systems.
To configure the Advanced XML Monitor, you must first run report LMS Entries Generator (/SAPSRM/
_LMS_ENTRIES_GENERATOR).
Procedure
Run transaction Abap Editor (SE38), then report LMS Entries Generator (/SAPSRM/
_LMS_ENTRIES_GENERATOR). For more information, see the related documentation.
4.6 More Information About SAP NetWeaver Process Integration
The following SAP Note applies: 1270081.
For more information, see SAP Solution Manager under:
■ <project name> Configuration SAP SRM 7.0 EHP3 Basic Settings for SRM SAP NetWeaver Process
Integration Defining SAP NetWeaver PI Settings
■ <project name> Configuration SAP SRM 7.0 EHP3 Basic Settings for SRM SAP NetWeaver Process
Integration Error and Conflict Handler
4 SAP NetWeaver Process Integration
4.5 Configuring the Advanced XML Monitor
2013-08-13 PUBLIC 23/148
This page is left blank for documents that are printed on both sides.
5 Customizing Synchronization
5.1 Synchronizing Customizing
You use this procedure to synchronize Customizing settings between SAP Supplier Relationship
Management (SAP SRM) and SAP ERP.
NOTE
For more information, see the standard documentation for Customizing Synchronization at
http://help.sap.com under SAP Solution Manager Implementing and Upgrading SAP Solutions
Customizing Synchronization .
The following objects are supported:
■ Country codes
■ Currency codes
■ Exchange rate
■ Incoterms
■ Payment terms
■ Quality Management systems (master data setup)
■ Tax codes
■ Unit of measure, dimensions, and ISO codes
Prerequisites
You must have:
■ Set up the SAP Solution Manager system
■ Configured the systems in the system landscape, for example SAP SRM and SAP ERP. You can do
this in Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic
Settings Define System Landscape .
■ Set the correct product version.
Procedure
Run transaction Synchronizing Customizing (SCDT_GROUPS), then transaction Setup Customizing
Distribution (SCDT_SETUP).
Result
The above objects are synchronized in the SAP SRM and SAP ERP systems.
5 Customizing Synchronization
5.1 Synchronizing Customizing
2013-08-13 PUBLIC 25/148
This page is left blank for documents that are printed on both sides.
6 System Connections
6.1 Automated Configuration
6.1.1 Automated Configuration of the Portal Systems
You can automate the configuration of the basic settings of SAP NetWeaver Portal used in SAP Supplier
Relationship Management (SAP SRM). To integrate SAP SRM with SAP NetWeaver Portal, you must
configure both the SAP SRM and SAP NetWeaver Portal systems, and you can use a wizard-based
configuration tool to perform the mandatory configuration necessary in both systems for this
integration.
More Information
For more information about automated configuration, see SAP Library for SAP NetWeaver on SAP Help
Portal at http://help.sap.com Technology Consultant’s Guide Configuration Wizard Business Suite
Connectivity Configuration - Overview .
For more information about the automated configuration of SAP NetWeaver Portal used in SAP SRM,
see SAP Service Marketplace at http://service.sap.com/instguides SAP Business Suite
Applications SAP SRM SAP SRM Server 7.13 Guide for Automated Configuration: SAP SRM Portal .
6.1.2 Automated Configuration Templates
You can run automated configuration templates (ACTs) to automate the mandatory configuration
steps necessary to connect the SAP Supplier Relationship Management (SAP SRM) system with other
SAP systems.
Integration
ACTs run in SAP NetWeaver Application Server (SAP NetWeaver AS) Java. SAP NetWeaver AS Java can
be either a standalone component of an SAP NetWeaver installation or part of the SAP NetWeaver
component of an SAP Solution Manager installation.
More Information
For more information about automated configuration, see SAP Library for SAP NetWeaver on SAP Help
Portal at http://help.sap.com Technology Consultant’s Guide Configuration Wizard Business Suite
Connectivity Configuration - Overview .
The following table lists the individual scenarios for which automated configuration is supported and
where to find their corresponding connectivity guides.
6 System Connections
6.1 Automated Configuration
2013-08-13 PUBLIC 27/148
System Configuration
Path to Documentation on SAP Service Marketplace
SAP SRM on One Client in SAP ERP
http://service.sap.com/instguides SAP Business Suite Applications SAP SRM SAP SRM Server 7.13 Connectivity Guide for Automated Configuration: SAP SRM on One Client in SAP ERP
Connecting SAP SRM to SAP ERP
http://service.sap.com/instguides SAP Business Suite Applications SAP SRM SAP SRM Server 7.13 Connectivity Guide for Automated Configuration: Connectivity Guide for Automated Configuration: SAP ERP to SAP Supplier Relationship Management
Connecting SAP SRM to SAP NetWeaver Business Warehouse (SAP NetWeaver BW)
http://service.sap.com/instguides SAP Business Suite Applications SAP SRM SAP SRM Server 7.13 Connectivity Guide for Automated Configuration: SAP NetWeaver Business Warehouse to SAP Supplier Relationship Management
6.2 Back-End Systems
6.2.1 Defining Back-End Systems
You must make the following settings to connect one or more back-end systems to SAP SRM:
Prerequisites
■ You have defined your back-end systems as unique logical systems. For more information, see
Defining Logical Systems and RFC Destinations [external document].
■ For each back-end system:
● You have specified the logical system.
● You have specified the RFC destination.
● You have created a second RFC connection for the same back-end system (for account
assignment search help in the back-end system, for example).
■ You have defined how FI data is to be validated.
■ Before you can define back-end systems for product categories, you have to define middleware
parameters. For more information, see Defining Middleware Parameters [page 33].
Procedure
Defining Back-End System
Go to Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings
Define System Landscape .
■ Enter the logical system, destination, and system type of the SAP SRM system. Define your SAP
SRM system as local if purchase orders, confirmations, and invoices are to be created there.
■ Enter the logical system, destination, and system type of the back-end system, and select the RFC
indicator if the logical system is RFC-compatible.
6 System Connections
6.2 Back-End Systems
28/148 PUBLIC 2013-08-13
For more information (for example, on authorization), see SAP Note 656633 Search help requires dialog
users.
Defining Back-End System for a Product Category
This step determines, depending on the product category, whether purchase orders and their follow-
on documents (confirmations, goods receipts/service entry sheets, and invoices) are to be created locally
in SAP SRM or in the back-end system.
1. To define the source and target system for each category, go to Customizing for SAP Supplier
Relationship Management under SRM Server Technical Basic Settings Define Back-End System for Product
Category .
2. For specific settings, go to Customizing for SAP Supplier Relationship Management under SRM Server
Cross-Application Basic Settings Define Objects in Back-End System (Purch. Reqs, Reservations, Purch.
Orders) .
6.3 Logical Systems and RFC Connections in the SAP SRM Landscape
6.3.1 Defining Logical Systems and RFC Destinations
This section describes the settings you must make to connect a back-end system to your SAP Supplier
Relationship Management (SAP SRM) system.
PrerequisitesIf you want your SAP SRM system to communicate with your supplier self-services system, you must
have specified your supplier self-services system as a unique logical system.
Procedure
Defining the Logical System
Perform the activity in Customizing for SAP Supplier Relationship Management under SRM Server
Technical Basic Settings ALE Settings Distribution (ALE) Basic Settings Logical Systems Define Logical
System .
Assigning the Logical System to a Client
Perform the activity in Customizing for SAP Supplier Relationship Management under SRM Server
Technical Basic Settings ALE Settings Distribution (ALE) Basic Settings Logical Systems Assign Logical
System to Client .
Defining the RFC Destination
The SAP SRM system communicates with a back-end system using RFC calls. Therefore, you must
define RFC destinations for these systems and an RFC user with appropriate authorizations. For
information about the recommended profile for the RFC user, see SAP Note 642202.
6 System Connections
6.3 Logical Systems and RFC Connections in the SAP SRM Landscape
2013-08-13 PUBLIC 29/148
Since the user's logon language from SAP SRM is used, you do not have to enter a logon language for
supplier self-services.
NOTE
In general, you do not need an RFC destination for this scenario. It is only required for functions
such as user synchronization.
You can define the RFC destination in Customizing for SAP Supplier Relationship Management under
SRM Server Technical Basic Settings Define RFC Destinations .
1. Use transaction SU01 to define RFC users to communicate between the systems. You have to define
a user both in SAP SRM and the supplier self-service component. If you are using several supplier
self-services systems, you must define a user in each of these systems.
NOTE
The user must be a system or dialog user.
2. Log on to the SAP SRM system.
3. Using transaction SM59, define an RFC destination for supplier self-services. If you have more than
one supplier self-services system, define an RFC destination for each of these systems.
4. Log on to your supplier self-services system.
NOTE
If you are using several supplier self-services systems, you must log on to each of them in
turn.
5. Using transaction SM59, define an RFC destination for SAP SRM. If you are using several supplier
self-services systems, we recommend that you give the RFC destination for SAP SRM the same
name in each of your supplier self-services systems.
Testing an RFC Connection
1. Log on to the SAP SRM system.
2. Call transaction SM59.
3. Select RFC destinations ABAP connections , and double-click the entry for your supplier self-
services system.
4. Choose Test connection.
5. If the test was not successful, start by checking the entries under on the Technical Settings tab page.
6. Choose Remote logon. This should cause a window to be opened in the SAP ERP system. If this does
not happen, check the logon data to make sure that the correct user and password were entered.
In addition, check the authorization level of the user in the SAP ERP system. You can also do this
by choosing Test Authorization .
7. If the remote logon was successful, you are now logged on to the SAP ERP system. In this system,
call SM59. Select RFC destinations ABAP connections , and double-click the entry for SAP SRM.
Test the connection and remote logon as described in the previous steps.
6 System Connections
6.3 Logical Systems and RFC Connections in the SAP SRM Landscape
30/148 PUBLIC 2013-08-13
Result
If a window is opened in SAP SRM, the connection is correct for system communication. If you are
unable to establish a connection, there are a number of possible causes, including the following:
■ The entry for the system on the Technical settings tab page (transaction SM59) is incorrect
■ The user or password was not entered correctly
■ The specified user does not have the required level of authorization
6.3.2 Create Distribution Model
6.3.2.1 Creating a Distribution Model
The applications that communicate with each other in your distributed systems are specified in the
distribution model. The distribution model consists of separate model views where you can define
system-wide message flows.
For more information, see Customizing for SAP Supplier Relationship Management under SRM Server
Technical Basic Settings ALE Settings Distribution (ALE) Modeling and Implementing Business Processes
Maintain Distribution Model and Distribute Views .
You can define the partner profiles for all outbound and inbound messages based on the information
in the distribution model.
For more information, see Customizing for SAP Supplier Relationship Management under SRM Server
Technical Basic Settings ALE Settings Distribution (ALE) Modeling and Implementing Business Processes Partner
Profiles Generate Partner Profiles .
Procedure
Creating Model Views
You must specify the cross-system message flow between SRM Server and all the connected back-end
systems. To create model views, and to add message types and BAPIs to your model views, proceed as
follows:
1. Enter change mode and create a model view in Customizing for SAP Supplier Relationship
Management under SRM Server Technical Basic Settings ALE Settings Distribution (ALE) Modeling
and Implementing Business Processes Maintain Distribution Model and Distribute Views .
2. Click once on the model view you created. Choose Add message type and select the model view for
which you wish to define message flow between SRM Server and the back-end system. Select your
SAP Supplier Relationship Management (SAP SRM) system as the Sender and the name of the
connected back-end system as the Receiver.
3. In the Message Type field, select which message types to add to your model view. The following table
shows which message types to select depending on which back-end system is connected to your
SAP SRM system:
6 System Connections
6.3 Logical Systems and RFC Connections in the SAP SRM Landscape
2013-08-13 PUBLIC 31/148
Message Type Back-End System 3.1
Back-End System 4.0 Back-End System 4.5 and Higher
Goods receipt (mat.doc.)
WMMBXY WMMBXY MBGMCR
Goods receipt (acc.doc.)
ACPJMM ACC_GOODS_MOVEMENT ACC_GOODS_MOVEMENT
Procurement Card ACLPAY ACLPAY ACLPAY
Invoice (CO) BBPCO BBPCO BBPCO
Invoice BBPIV BBPIV BBPIV
4. Choose Add BAPI to add Business Application Programming Interfaces (BAPIs) to your model view.
Select your SAP SRM system as the Sender and the name of the connected back-end system as the
Receiver.
5. The following table shows which BAPIs to add:
Object Name/Interface Method
IncomingInvoiceEC (EC Incoming Invoice) Create
BBP_PCSTAT (Procurement Card Statement) Create
6. Save your entries.
Generating Partner Profiles
After you have created and distributed the model views, you must generate partner profiles for
outbound and inbound messages in SRM Server.
1. Generate partner profiles in Customizing for SAP Supplier Relationship Management under SRM Server
Technical Basic Settings ALE Settings Distribution (ALE) Modeling and Implementing Business Processes
Partner Profiles Generate Partner Profiles or see SAP Solution Manager for SAP SRM under Basic
Settings for SAP SRM System Connections Logical Systems and RFC Connections in the SRM Landscape Create
Distribution Model .
2. Enter the name of your model view in the Model View field.
3. Enter the name of the back-end system in the Partner System field.
4. At Outbound Parameters, enter 3 in the Version field.
5. Select the output mode Collect IDocs and transfer.
6. Select the inbound parameter Trigger by background program.
7. Choose Execute (or F8).
NOTE
You can also generate partner profiles in the back-end system in Customizing for SAP Supplier
Relationship Management under SRM Server Technical Basic Settings ALE Settings Distribution (ALE)
Modeling and Implementing Business Processes Maintain Distribution Model and Distribute Views , or you
can use transaction BD64. Select the model view for which you want to generate partner profiles.
Choose Edit Model View Distribute . Select the relevant back-end system and choose
Continue.
6 System Connections
6.3 Logical Systems and RFC Connections in the SAP SRM Landscape
32/148 PUBLIC 2013-08-13
Ensure that the partner profile was generated in the back-end system in Customizing for SAP
NetWeaver under Application Server IDoc Interface/Application Link Enabling (ALE) Modelling and Implementing
Business Processes Maintain Distribution Model and Distribute Views . Alternately, you can use transaction
BD64.
If no partner profile was generated in the back-end system, proceed as follows:
1. Generate a partner profile in Customizing for SAP NetWeaver under Application Server IDoc Interface/
Application Link Enabling (ALE) Modelling and Implementing Business Processes Partner Profiles Generate
Partner Profiles . Alternately, you can use the link in SAP Solution Manager for SAP SRM under
Basic Settings for SAP SRM System Connections Logical Systems and RFC Connections in the SRM Landscape
Create Distribution Model , or use transaction BD82.
2. Enter the name of the model view you created in the SAP SRM system in the Model View field.
3. Enter the name of the SAP SRM system in the Partner System field.
4. Choose Execute (or F8).
6.4 Logical Systems and RFC Connections in the SAP ERP Landscape
Procedure
You must perform the following Customizing activities in the back-end system:
1. Name the logical system.
You can find more information in Customizing for the back-end system under SAP NetWeaver
Application Server IDoc Interface/Application Link Enabling (ALE) Basic Settings Logical Systems Define
Logical System
2. Create the RFC connection.
3. Specify the RFC destinations for method calls.
You can find more information in Customizing for the back-end system under SAP NetWeaver
Application Server IDoc Interface/Application Link Enabling (ALE) Communication
6.5 Middleware Parameters
6.5.1 Defining Middleware Parameters
You specify:
■ The system from which the data is to be replicated
■ The data to be replicated (using filters)
Prerequisites
You have been assigned to the SAP_CRM_MW_ADMINISTRATOR role. This role allows you to run
transaction Administration Console (SMOEAC).
6 System Connections
6.4 Logical Systems and RFC Connections in the SAP ERP Landscape
2013-08-13 PUBLIC 33/148
You have defined RFC destinations and customized master data replication, as described in:
Defining the RFC Destination [external document]
Customizing Material Replication in SAP SRM [external document]
Procedure
To specify the SAP back—end systems in the middleware parameters:
1. Run transaction Administration Console (SMOEAC) (middleware menu: Administration Administration
Console ).
2. Select object type Sites.
3. Choose Create.
4. Enter the name, description, and type (R/3)
5. To enter the RFC destination of the back—end system, choose Site attributes.
6. Repeat steps 2 to 5 for all further back—end systems.
NOTE
See also SAP Note 720819 Middleware consumer entry for SRM in the OLTP system
To specify the SAP SRM system as the consumer of the back—end system for the delta download:
1. Log on to the back—end system.
2. Run transaction SM30.
3. Verify and, if necessary, change or insert entries in tables CRMCONSUM and CRMRFCPAR as
described in SAP Note 430980. See also SAP Note 720819.
4. To ensure correct filtering of the object MATERIAL, you must insert an entry in table
CRMPAROLTP running transaction SM30:
■ Parameter name 1: CRM_FILTERING_ACTIVE
■ Parameter name 2: MATERIAL
■ Parameter name 3: MATERIAL
■ User: CRM
■ Parameter value 1: X
■ Parameter value 2: blank
If, in the previous step, you have defined an additional consumer or a consumer other than CRM, you
must create a corresponding entry per consumer in the table. You enter each separate consumer in
the field USER.
NOTE
Since this table entry cannot be used if there is a connected CRM system, this entry cannot be
shipped as part of the standard system.
More Information
SAP Note 519794.
6 System Connections
6.5 Middleware Parameters
34/148 PUBLIC 2013-08-13
6.5.2 Specify Back-End System for Download
6.5.2.1 Specifying Back-End Systems for Download
You use this procedure to specify the system from which the data is to be replicated using middleware.
Prerequisites
■ You have been assigned to the role SAP_CRM_MW_ADMINISTRATOR. This role is required
to display the Middleware menu.
■ You have defined the RFC destinations and done the related Customizing in SRM Server.
Procedure
To specify the back-end systems for Middleware Download:
1. Run transaction Administration Console (SMOEAC) (middleware menu: Administration Administration
Console ).
2. Select object type Sites.
3. Choose Object Create .
4. Enter the name, description, and type (R/3)
To enter the RFC destination of the SAP back-end system:
1. Choose Site Attributes.
2. Repeat steps 2 to 5 for all further SAP back-end systems.
More Information
See SAP Note 720819.
6.5.3 Defining Settings in SAP SRM and in the Back-End System
6.5.3.1 Defining Download Settings in the Back-End System
You use this procedure to specify the data and filters for the replication via middleware.
Procedure
To specify the SAP SRM system, which is the consumer of the SAP back-end system, for the delta
download, proceed as follows:
1. Log on to the SAP back-end system.
2. Run transaction Call View Maintenance (SM30).
3. Verify and, if necessary, change or insert entries in the CRMCONSUM, CRMRFCPAR, and
CRMSUBTAB tables as described in SAP Note 430980.
4. When you maintain CRMSUBTAB, make three entries for CONSUMER= SRM-system;
Objectname=' '; Download; and OBJCLASS = CUSTOMIZING + MATERIAL+ SERVICE_MASTER
using the relevant function name (for example CRS_MATERIAL_EXTRACT).
6 System Connections
6.5 Middleware Parameters
2013-08-13 PUBLIC 35/148
NOTE
See also SAP Note 720819.
To ensure correct filtering of the object MATERIAL, (using transaction SM30) you need to insert an
entry in the CRMPAROLTP table:
■ Parameter name 1: CRM_FILTERING_ACTIVE
■ Parameter name 2: MATERIAL
■ Parameter name 3: MATERIAL
■ User: CRM
■ ParVal1: X
■ ParVal2:
If (in the previous step) you have defined an additional consumer or a consumer other than CRM, you
need to create a corresponding entry per consumer in the table. You enter each separate consumer in
the User field.
More Information
SAP Note 519794
6.5.3.2 Check Users of Adapter Functions
6.5.3.2.1 Checking Users of Adapter Function
Procedure
1. Run transaction Call View Maintenance (SM30) to edit table Possible Users of R/3 Adapter Functionality
(CRMCONSUM) in the SAP Enterprise Resource Planning (SAP ERP) system. Enter the consumer,
for example, SAP CRM or SAP SRM system, or a logical RFC destination such as E7SCLNT300,
which is linked to SAP ERP.
2. Create the following entries for your new consumer in the table CRMCONSUM of the SAP ERP
system:
■ CONSUMER = SRM (for example)
■ AKTIV = X
■ TEXT = SRM Consumer (for example)
NOTE
You can also choose another consumer name instead of "SRM". You can ignore the warning
message "Choose the key from the allowed namespace" by choosing ENTER.
6 System Connections
6.5 Middleware Parameters
36/148 PUBLIC 2013-08-13
6.5.3.3 Check Definitions of RFC Connections
6.5.3.3.1 Checking RFC Connections
Procedure
1. Run transaction Call View Maintenance (SM30) and edit table Definitions for RFC Connections
(CRMRFCPAR) in the SAP ERP system. Enter a consumer. For more information, see the entries
in table Possible Users of R/3 Adapter Functionality (CRMCONSUM) and the RFC destinations.
2. Create the following entries for initial downloads in table CRMRFCPAR of the SAP ERP system:
■ Consumer application: SRM (for example)
● Object name: *
● Destination: <SM59 RFC destination of SRM system>
● Download type: Initial Download (I)
● Queue name: ' '
● InQueue name: ' '
● BAPI name: ' '
● Short description: DEFAULT DESTINATION FOR SRM
● Data record inactive: ' '
● Ignore Data: ' '
● InQueue indicator: X
● Use XML: X
● Stop data: ' '
3. Save your entries.
4. Create the following entries for the delta download of the material master in table
CRMRFCPAR of the SAP ERP system:
■ Consumer application: SRM (for example)
■ Object name: MATERIAL
■ Destination: <SM59 RFC destination of SRM system>
■ Download type: Delta Download (D)
■ Queue name: ' '
■ InQueue name: ' '
■ BAPI name: ' '
■ Short description: DEFAULT DESTINATION FOR SRM
■ Data record inactive: ' '
■ Ignore Data: ' '
■ InQueue indicator: X
■ Use XML: X
■ Stop data: ' '
5. Save your entries.
6 System Connections
6.5 Middleware Parameters
2013-08-13 PUBLIC 37/148
6. Create the following entries for the delta download of the service master in table CRMRFCPAR
of the OLTP system:
■ Consumer application: SRM (for example)
■ Object name: SERVICE_MASTER
■ Destination: <SM59 RFC destination of SRM system>
■ Download type: Delta Download (D)
■ Queue name: ' '
■ InQueue name: ' '
■ BAPI name: ' '
■ Short description: DEFAULT DESTINATION FOR SRM
■ Data record inactive: ' '
■ Ignore data: ' '
■ InQueue indicator: X
■ Use XML: X
■ Stop data: ' '
7. Save your entries.
8. If you want to perform a request, create the following entries in table CRMRFCPAR of the OLTP
system:
■ Consumer application: SRM (for example)
● Object name: *
● Destination: <SM59 RFC destination of SRM system>
● Download type: Request (R)
● Queue name: ' '
● InQueue name: ' '
● BAPI name: ' '
● Short description: DEFAULT DESTINATION FOR SRM
● Data record inactive: ' '
● Ignore Data: ' '
● InQueue indicator: X
● Use XML: X
● Stop data: ' '
9. Save your entries.
6.5.3.4 Checking OLTP Parameters
6.5.3.4.1 Checking OLTP Parameters for Replication
Run transaction Call View Maintenance (SM30) to edit table CRM OLTP Parameters (CRMPAROLTP) in
the SAP Enterprise Resource Planning (SAP ERP) system.
6 System Connections
6.5 Middleware Parameters
38/148 PUBLIC 2013-08-13
Procedure
If the following entries do not yet exist for your consumer user, for example, SRM, create them for the
delta download object MATERIAL in table CRMPAROLTP of the OLTP system:
■ Parameter name: CRM_FILTERING_ACTIVE
■ Parameter name 2: MATERIAL
■ Parametername 3: ' '
■ User: SRM (for example)
■ Parametervalue: X
■ Parametervalue 2: '
If the following entries do not yet exist for your consumer user, for example, SRM, add them for the
delta download object SERVICE_MASTER in table CRMPAROLTP of the OLTP system:
■ Parameter name: CRM_FILTERING_ACTIVE
■ Parametername 2: SERVICE_MASTER
■ Parametername 3: ' '
■ User: SRM (for example)
■ Parametervalue: X
■ Parametervalue 2: ' '
6.5.3.5 Check Subscription Table for Upload and Download Objects
6.5.3.5.1 Checking Subscription Table for Upload and Download Objects
Run transaction Call View Maintenance (SM30) to edit table Subscription Table for Upload and Download Objects
(CRMSUBTAB) in the SAP Enterprise Resource Planning (SAP ERP) system. You must specify a
consumer. For more information, see the entries in table Possible Users of R/3 Adapter Functionality
(CRMCONSUM) and the objects for downloading.
Procedure
1. Copy the following entries in table CRMSUBTAB in the SAP ERP system:
■ CONSUMER: CRM; OBJCLASS: MATERIAL
■ CONSUMER: CRM; OBJCLASS: CUSTOMIZING
■ CONSUMER: CRM; OBJCLASS: SERVICE_MASTER
NOTE
When you copy an entry, only change the CONSUMER entry that refers to the consumer
name that you created ("SRM", for example).
2. Save your entries.
6 System Connections
6.5 Middleware Parameters
2013-08-13 PUBLIC 39/148
6.5.3.6 Check Middleware Parameters
6.5.3.6.1 Checking Middleware Parameters
Procedure
1. Run transaction Call View Maintenance (SM30) to edit table Middleware Parameter (SMOFPARSFA) in
the SAP Supplier Relationship Management (SAP SRM) system.
2. Create the following entries:
■ Key: MCRM
■ Parameter name 1: MCRM_CONSUMER
■ Parameter name 2: ' '
■ Parameter name 3: ' '
■ User: SRM (for example)
■ Parameter value 1: SRM (for example)
■ Parameter value 2: SRM (for example)
3. Save your entries.
6.5.4 Define Settings for Standalone Systems
6.5.4.1 Defining Settings for SAP SRM System
You can deactivate all the customizing and business objects that are not required for SAP SRM scenarios.
Procedure
1. Run transaction Abap Editor (SE38).
2. Run report Middleware Settings for Product for SRM Systems (BBP_PRODUCT_SETTINGS_MW).
3. Perform a test run and check the log.
4. Deselect the Test Mode checkbox and run the report again.
6.6 Aligning Units of Measurement, Currencies, and Exchange Rates
Prerequisites
The units of measurement (UOMs), currencies, and exchange rates in the SAP Supplier Relationship
Management (SAP SRM) system must be identical with the UOMs, currencies, and exchange rates in
the back-end system.
Procedure
Perform the following steps in the SAP SRM system and in the Supplier Self-Services system:
Checking Units of Measurement
Verify that the contents of the following Customizing activities are identical:
6 System Connections
6.6 Aligning Units of Measurement, Currencies, and Exchange Rates
40/148 PUBLIC 2013-08-13
■ In the SAP SRM system, in Customizing for SAP Web Application Server under General Settings Check
Units of Measurement
■ In the back-end system, in Customizing for SAP NetWeaver under General Settings Check Units of
Measurement
Adjusting currencies and exchange rates
If an SAP FI back-end system is used, run the following reports:
■ BBP_GET_CURRENCY
■ BBP_GET_EXRATE
Whenever currencies and exchange rates are updated in the back-end system, these reports align them
with those in the SAP SRM system.
Assigning ISO Codes
Verify that you have assigned the relevant ISO codes in the following Customizing activities, particularly
if you have connected catalogs:
■ In the SAP SRM system, in Customizing for SAP Web Application Server under General Settings Check
Units of Measurement
■ In the back-end system, in Customizing for SAP NetWeaver under General Settings Check Units of
Measurement
NOTE
To automatically adjust ISO codes in the SAP SRM system to conform to the ISO codes from the
back-end system, proceed as follows:
1. In the Customizing activity Check Units of Measurements in the SAP SRM system, on the initial
screen, choose ISO Codes. On the “ISO Units”: Overview screen, choose Utilities Adjustment .
2. Select your back-end system and choose Execute.
3. Go to Edit Select Select All .
4. Choose Adjust.
6.7 Configuration Engine (CE)
6.7.1 Setting Up Configuration Engine
Procedure
Follow the instructions in SAP Note 854170 to activate the Virtual Machine Container (VMC), then
run transaction Maintain Services (SICF) to activate the related service.
NOTE
In certain cases, you can use the simplified pricing function as an alternative to the Configuration
Engine. For more information, see Customizing for SAP Supplier Relationship Management under
SRM Server Business Add-Ins Pricing Switch On Simplified Pricing (Classic Scenario) .
6 System Connections
6.7 Configuration Engine (CE)
2013-08-13 PUBLIC 41/148
6.7.2 More Information About Configuration Engine (CE)
The following SAP Note applies:
■ 844817 (Technical information for the VMC-based AP 7.00 engines)
6.8 Technical Settings for E-Mail
6.8.1 Defining Technical Settings for E-Mail
This setting enables communication between the buyer and suppliers, for example, sending notification
to the supplier when a new order is created, or an existing order is changed.
Prerequisites
The user SAPconnect must be activated (transaction SICF).
Procedure
Creating the Mail Service in SAPconnect
Transaction SCOT
Menu Path SAP Menu Basis Tools Business Communication Communication SAPconnect
NOTE
An alternative method of setting up mail via SMTP is described in SAP Note 455140.
Creating a Job for the Mail Service in SAPconnect
Transaction SCOT
Menu Path SAP Menu Basis Tools Business Communication Communication SAPconnect
1. Choose View Jobs .
2. Choose Create.
3. Enter a name for the job and choose Enter.
4. Select the variant INT.
5. Choose Schedule.
6. Select Schedule Periodically. You can then enter the duration of time between the jobs.
7. Enter the duration time and choose Create.
6.8.2 Quick Guide to SMTP Configuration
As of SAP Web Application Server 6.10, the SAP system's kernel supports SMTP (Simple Mail Transfer
Protocol) directly, meaning that e-mails can be exchanged between the SAP system and any SMTP-
compliant mail server without the need for any additional external components. In the outbound
6 System Connections
6.8 Technical Settings for E-Mail
42/148 PUBLIC 2013-08-13
direction, the SAP system passes the mails to a single mail server, whereas in the inbound direction
mails can be received from any number of mail servers.
As of SAP Web Application Server 6.20, faxes and text messages (pager/ SMS) can also be exchanged via
SMTP. For this purpose, the faxes and messages are packed into e-mails. For sending, the mail server
refers to the domain of their recipients' addresses and forwards the e-mails either to an internal fax/
text message server (for example, [email protected]), or to an external
provider (for example, [email protected]). For receiving, the fax/text message
server or provider sends e-mails to addresses with the SAP system's domain (for example, FAX=
PrerequisitesThe mail servers involved must be SMTP-compliant.
If you want to use text messaging in the SAP system, then you must define names for the messaging
services to be used, such as SMS, with transaction SA14.
Procedure
Setting the Profile Parameters (Transaction RZ10)
You must adapt the SAP Web Application Server’s profile if the SMTP functionality is to be used. The
SAPconnect send job can only be scheduled for servers on which SMTP is active, so ideally you should
activate SMTP on all of the SAP system’s application servers.
You must set the profile parameters below. The placeholder <*> stands for the sequence number
(starting with zero) of parameters that occur several times.
■ icm/plugin_<*> = PROT=SMTP,PLG=<prog>
This loads the SMTP plug-in. It is a dynamic library that implements the SMTP protocol. <prog>
specifies the file name of the SMTP plug-in. The program is located in the execution directory of
the SAP Web Application Server instance, has the name smtpplugin and the extension typical for
your operating system (.so, .dll, and so on).
■ icm/server_port_<*> = PROT=SMTP,PORT=<port>
This opens a TCP/IP port for the reception of mails by the SMTP plug-in. <port> specifies the
number of the port that is to be used. This port must not be occupied by any other program on
this host. If no mails (including status notifications) are to be received in this SAP system, you can
set <port> to 0.
You can use TIMEOUT to define an optional maximum time (in seconds) that is to be waited for a
response from the mail server.
■ is/SMTP/virt_host_<*> = <host>:<port>,<port>,...
This defines a virtual mail host for the reception of mails. If all inbound mails (including status
notifications) are to be received and processed in a single client of the SAP system, this parameter
is not required and is/SMTP/virt_host_0 = *:*; is taken as the default. If several clients are to
receive, a virtual mail host must be created for every client. <host> specifies the name of the host
6 System Connections
6.8 Technical Settings for E-Mail
2013-08-13 PUBLIC 43/148
to which inbound mails are addressed. You can specify * here if the mails are to be distributed
independently of the host addressed. <port> specifies the number of a port to which inbound mails
are addressed.
EXAMPLE
Under UNIX, the profile parameters could be as follows:
rdisp/start_icman = true
icm/plugin_0 = PROT=HTTP,PLG=./httpplugin.so
icm/plugin_1 = PROT=HTTPS,PLG=./httpplugin.so
icm/plugin_2 = PROT=SMTP,PLG=./smtpplugin.so
icm/server_port_0 = PROT=HTTP,PORT=1080
icm/server_port_1 = PROT=HTTPS,PORT=1443
icm/server_port_2 = PROT=SMTP,PORT=25000,TIMEOUT=180
icm/server_port_3 = PROT=SMTP,PORT=25001,TIMEOUT=180
is/SMTP/virt_host_0 = *:25000;
is/SMTP/virt_host_1 = *:25001;
User Administration (Transaction SU01)
■ Service user
You must create a service user to process the inbound mails in every SAP system client in which
mails (or status notifications) are to be received. You use transaction SU01 to create a user of the
type Service and assign the profile S_A.SCON to it.
■ User addresses
Every single user who is to receive e-mails in an SAP system needs an Internet mail address. This
is also used as the sender address. You enter the Internet mail address of a user in transaction
SU01 on the Address tab page under E-Mail.
Client Assignment (Transaction SICF)
Each SAP system client in which inbound mails (or status notifications) are to be received and processed
must have an SMTP server. In transaction SICF, there should be one SMTP server (called SAPconnect)
supplied in every SAP system. You use this one for the first client then create an additional SMTP server
for each additional client. You make the following settings on the SMTP servers:
■ Host data
You enter the sequence number of a parameter is/SMTP/virt_host_<*> from the profile. If you
only have one client and therefore did not enter a parameter of this kind, you enter 0.
■ Service data
You enter the client to which the mails received via this virtual mail host are to be forwarded, as
well as the logon data of the system user created for inbound mails.
■ Handler list
6 System Connections
6.8 Technical Settings for E-Mail
44/148 PUBLIC 2013-08-13
You enter CL_SMTP_EXT_SAPCONNECT as item 1.
NOTE
As of SAP Web AS 6.20, each SMTP server must be activated ( Service/Host Activate after
being created or changed.
SAPconnect Administration (Transaction SCOT)
You must make the SAPconnect settings in each client that is to be used to send communications.
■ Default domain
Under Settings Default Domain , you define the domain of this SAP system client. This is used for
the following purposes:
● The SMTP plug-in logs on to the mail server using the domain as ID.
● The message ID of outbound e-mails is compiled with this domain.
● If an SAP user who has no Internet mail address maintained sends an e-mail, a sender address
composed of the SAP user name and this domain is generated.
■ Node
There is always one SMTP node in each client. This node is created by the SAP system and cannot
be deleted. To configure the node for sending Internet mail, you:
1. Ensure you are in the Node view.
2. Double-click on the node name.
3. Select Node in use.
4. Specify the mail server to which outbound mails are to be passed in Mail Host and Mail Port.
5. Choose Set adjacent to Internet.
6. Specify the address areas of recipient addresses that are to be reached via this node. This is
usually * if all e-mails are to be sent using SMTP.
7. Enter output formats for SAP documents. The following settings are recommended here:
SAPscript/Smart Forms PDF
ABAP List HTM
Business Object/Link HTM
RAW Text TXT
8. Confirm.
If you want to configure the node for sending faxes as well, you:
1. Choose Set adjacent to Fax.
2. Specify the address areas of recipient addresses that are to be reached via this node. This is
usually * if all faxes are to be sent using SMTP.
3. Enter output formats for SAP documents. The following settings are recommended here:
SAPscript/Smart Forms PDF
ABAP List PDF
Business Object/Link TXT
6 System Connections
6.8 Technical Settings for E-Mail
2013-08-13 PUBLIC 45/148
RAW Text TXT
4. Enter the domain of the fax server or fax provider under Conversion into Internet Address. The system
generates the local part of the Internet address automatically. The address then has the format
FAX=+RecipientNumber@Domain.
5. Confirm.
If you want to configure the node for sending text messages (pager/SMS) as well, you:
1. Choose Set adjacent to Pager (SMS).
2. Specify the address areas of recipient addresses that are to be reached via this node. This is
usually * if all text messages (pager/SMS) are to be sent using SMTP.
3. Enter the domain of the text message (pager/SMS) server or provider under Conversion into Internet
Address. The system generates the local part of the Internet address automatically. The address
then has the format SMS=+RecipientNumber@Domain.
4. Confirm.
■ Send job
E-mails sent from an SAP application are merely put into a queue. A periodic background process,
known as the SAPconnect send job, takes the e-mails from this queue and sends them via the
Internet. To schedule this job from SAPconnect administration, you:
1. Choose View Jobs .
2. If there is not already a job scheduled, choose Job Create .
3. Enter a job name and confirm.
4. Select the variant SAP&CONNECTALL by placing the cursor on it.
5. Choose Schedule Job.
6. Choose Schedule Periodically.
7. Enter an appropriate time period, such as 10 minutes.
8. Choose Create.
■ Inbound
If you want inbound e-mails to a specific address or with a specific content to automatically start
a program that processes these e-mails, you can configure this under Settings Inbound Processing .
If you want inbound e-mails to a specific address or from a specific sender to be automatically
redirected to another recipient or distribution list, you can configure this under Settings Inbound
Distribution .
6.9 Setting Control Parameters
Procedure
Set the following control parameters in Customizing for SAP Supplier Relationship Management under
SRM Server Technical Basic Settings Set Control Parameters .
Key Control Record Description Value Control Record
6 System Connections
6.9 Setting Control Parameters
46/148 PUBLIC 2013-08-13
SPOOL_JOB_USER User that executes spool job <AdminUser>
SPOOL_LEAD_INTERVAL Interval by which the retry time occurs <number of seconds>
SPOOL_MAX_RETRY Maximum number of retries for writing BAPIs <number>
6.10 Jobs for Scheduling Reports
6.10.1 Scheduling Reports
You cannot continue processing a requirement request in SAP SRM until the corresponding
documents have been created in the back-end system.
At intervals defined by you, the system checks whether the documents have been created. After they
have been created, the requirement request is updated and can be processed further. For this reason,
you schedule the report CLEAN_REQREQ_UP to run periodically using transaction SM36.
You should also schedule report BBP_GET_STATUS_2 (updating requirement requests) to run in the
SAP SRM system, so that information on the status of purchase requisitions, purchase orders, and
reservations is up to date.
Scheduling Reports
Report Name Description Required/ Optional
CLEAN_REQREQ_UP (and START_CLEANER)
Updating of documents (purchase requisitions, purchase orders, reservations) is executed asynchronously in the back-end system. You cannot process the shopping cart in the SAP SRM system until the update has been carried out.Use transaction SM36 to schedule report CLEAN_REQREQ_UP to run periodically (for example, every 30 minutes). Create a variant with only a logical system name, and schedule this job with this variant.If you previously used the report START_CLEANER, you can also use transaction SM36 to schedule this report.
Required
BBP_GET_STATUS_2 This report updates shopping carts.To ensure that information on the status of purchase requisitions, purchase orders, and reservations is up to date, use transaction SM36 to schedule this report to run periodically (for example, every 30 minutes) in the SAP SRM system. Create a variant, and schedule this job with the variant.
Required
RSPPFPROCESS If the purchase orders are to be transferred to the suppliers, schedule this report to run at regular intervals.
NOTE
Do not schedule this report if you have selected Processing when saving document for the Action Profile in the Customizing activity Define Actions for Document Output. You make this setting in the Processing Time field on the Action Definition tab.
Optional
BBPERS If you use Evaluated Receipt Settlement (ERS) for local purchase orders for which confirmations exist, you must start BBPERS.
Optional
6 System Connections
6.10 Jobs for Scheduling Reports
2013-08-13 PUBLIC 47/148
BBP_DELETE_LOCAL_ACCOUNT This report updates account assignment tables and deletes those account assignment objects that are no longer valid, that is when the expiration date has passed.
Optional
6 System Connections
6.10 Jobs for Scheduling Reports
48/148 PUBLIC 2013-08-13
7 Master Data Replication
7.1 Replication of Materials from ERP Back-End Systems
You want to replicate materials or service masters from an SAP ERP back-end system or multiple SAP
ERP back-end systems. This documentation describes this process. In addition to describing the various
procedures involved, it provides information about how to proceed if problems arise during the
replication process.
Prerequisites
You have defined the logical system and RFC destinations for the SAP ERP back-end system. For more
information, see Defining Logical Systems and RFC Destinations [page 29]
Process
You have to perform the following steps in the order given:
1. Customizing Material Replication in SAP SRM [page 49]
2. Defining Middleware Parameters [page 33]
3. Downloading Customizing Objects [page 50]
4. Downloading Business Objects [page 52]
Result
The replication of the materials is complete.
For more information, see SAP Note 429423.
7.2 Customizing Material Replication in SAP SRM
Before replicating SAP SRM Customizing data and master data from your back-end systems, you have
to perform some Customizing activities in the SAP SRM system.
Prerequisites
You have read and implemented Defining Logical Systems and RFC Destinations [page 29].
Procedure
1. Perform the Customizing steps for units of measure, currencies, and countries. Make sure that the
associated ISO codes are entered in full and that there are no ambiguities (for example, two units
of measure with the same ISO code). If you have added your own entries for currencies, units of
7 Master Data Replication
7.1 Replication of Materials from ERP Back-End Systems
2013-08-13 PUBLIC 49/148
measure or countries in your backend systems, you have to make corresponding entries in the
SAP SRM system.
Path in Customizing:
■ Countries: SAP Web Application Server General Settings Set Countries Specify Countries in mySAP
Systems (CRM, SRM, SCM,...) .
■ Currencies: SAP Web Application Server General Settings Currencies Check Currency Codes
■ Units of Measure: SAP Web Application Server General Settings Check Units of Measurement
2. Set the output format and storage form for the product IDs. We recommend that you define a
length of 18 characters, in keeping with the length of the back-end material number. See
Customizing for SAP SRM under SRM Server Master Data Products Define Output Format and Storage
Form of Product IDs .
CAUTION
Read the documentation for all the fields of this Customizing activity with great care. In
particular, the decision as to whether you opt for lexicographical or nonlexicographical
storage of product IDs is important.
CAUTION
Enter only templates in the Template ID field. Do not use this field to enter descriptive texts.
7.3 Downloading Customizing Objects
After this procedure has been completed, the Customizing objects for material number conversion,
material types, material groups, and service category are available in the SAP SRM system.
Prerequisites
You have completed the following steps:
■ Defining Logical Systems and RFC Destinations [page 29]
■ Customizing Material Replication in SAP SRM [page 49]
■ Defining Middleware Parameters [page 33]
Procedure
Updating Table Entries in CRMATAB from SAP ERP
1. Assign role MW_ADMIN to the RFC user responsible for master data replication in the SAP ERP system.
2. Run report SMOF_FILL_CRMATAB, and enter the SAP ERP site name as the source site, and the
following Customizing object names:
■ DNL_CUST_BASIS3
■ DNL_CUST_PROD0
■ DNL_CUST_PROD1
■ DBL_CUST_SRVMAS
7 Master Data Replication
7.3 Downloading Customizing Objects
50/148 PUBLIC 2013-08-13
Downloading Customizing Objects
1. Call transaction R3AS.
2. Using the multiple selection dialog box for Load Object, choose the Customizing objects:
■ DNL_CUST_BASIS3 (units of measure, dimensions, and currencies)
■ DNL_CUST_PROD0 (product categories)
■ DNL_CUST_PROD1 (product categories)
■ DNL_CUST_SRVMAS (service categories)
3. Enter the Source Site (that is, the back-end system) and Destination Site (SAP SRM system), which
was defined using the Administrator Console (transaction SMOEAC).
4. To start the download, choose Execute.
Checking the Download is Complete
1. To start the Download Monitor, call transaction R3AM1. If all the traffic lights are green, the
download was successful. If a traffic light is yellow, select Refresh and observe whether the block
number increases. If so, the download is still in progress. If not, continue with the next step.
2. In the back-end system, check the outbound queue in transaction SMQ1. For Queue name, enter the
correct queue name, and choose Execute to display the queue. If the queue is locked, try to release
the lock on it and to activate it. If the queue disappears after you select Refresh, the download process
has proceeded further.
3. Using transaction SMQ2, check the inbound queue in the SAP SRM system and activate it if
necessary.
4. Using the transactions SMWP and SMW01, you can get detailed information about the progress of
the download. You start these transactions in the SAP SRM system. Look out for any error messages
and correct the errors wherever possible. After calling transaction SMW01, proceed as follows to
get information about the download:
1. Choose Execute.
2. Select a line and choose Show BDoc Msg Errors/Receivers.
5. After eliminating any errors, call transaction SMQ2. Choose Execute, and select a Queue Name.
6. Select Display.
7. Double-click on the number in the Entries column.
8. Select an entry and choose Execute to activate the queue.
9. To check whether the material types, material groups, and service categories have arrived in the
SAP SRM system, call transaction COMM_HIERARCHY. You should see all the required data. If
not, check your filter settings again and look at the data in the back-end system. Check whether
the tables assigned to the objects contain the necessary data in the back-end system.
More Information
SAP Note 765018 (Problems with logical system during data exchange)
7 Master Data Replication
7.3 Downloading Customizing Objects
2013-08-13 PUBLIC 51/148
7.4 Materials and Service Master Download
7.4.1 Downloading Business Objects
You use this procedure to perform the initial download of business objects from your SAP back-end
systems. You can also specify filters to restrict the variety of materials to be replicated.
NOTE
Specify the appropriate filter conditions appropriately for the database format of the
corresponding fields in the back-end system. In particular, material or service numbers must have
18 characters and include leading zeros (unless you specified the lexicographical storage format
for material numbers).
After the download, you can check that the business objects have been downloaded correctly. A
frequent cause of error is missing units of measure in the SAP SRM system.
Prerequisites
You have completed the following steps:
■ Defining Logical Systems and RFC Destinations [page 29]
■ Customizing Material Replication in SAP SRM [page 49]
■ Defining Middleware Parameters [page 33]
■ Downloading Customizing Objects [page 50]
Procedure
Procedure
Downloading Business Objects (Initial Download)
Log on to your SAP SRM system.
If you wish to define filters to restrict the selection of materials to be replicated, choose Middleware:
Basis Data Exchange Object Management Business Objects (Choose Transaction Code R3AC1).
In change mode, click (Filter Settings)on the line containing the business object MATERIAL. The Object
Filter Settings screen is displayed.
Enter the values for the tables and fields displayed in the input help. Only those materials matching
the set values are replicated. For Source Site Name, choose the name of the corresponding back-end system
and select the filter option Filter only in source database.
To start the download for materials, and the service master (if required), call transaction R3AS and
specify object MATERIAL, or object SERVICE_MASTER as appropriate and the Source Site (back-end
system) and Destination Site (SAP SRM system).
7 Master Data Replication
7.4 Materials and Service Master Download
52/148 PUBLIC 2013-08-13
Checking the Initial Download
1. To start the Download Monitor, call transaction R3AM1. If all the traffic lights are green, the
download was successful. If a traffic light is yellow, select Refresh and observe whether the block
number increases. If so, the download is still in progress. If not, continue with the next step.
2. In the back-end system, check the outbound queue in transaction SMQ1. For Queue name, enter the
correct queue name, and choose Execute to display the queue. If the queue is locked, try to release
the lock on it and to activate it. If the queue disappears after you select Refresh, the download process
has proceeded further.
3. Using transaction SMQ2, check the inbound queue in the SAP SRM system and activate it if
necessary.
4. Using the transactions SMWP and SMW01, you can obtain detailed information about the progress
of the download. You start these transactions in the SAP SRM system. Look out for any error
messages and correct the errors wherever possible. After calling transaction SMW01, proceed as
follows to obtain information about the download:
1. Choose Execute.
2. Select a line and choose Show BDoc Msg Errors/Receivers.
5. After eliminating any errors, call transaction SMQ2. Choose Executeand select a Queue Name.
6. Select Display.
7. Double-click on the number in the Entries column.
8. Select an entry and choose Execute to activate the queue.
Result
Required materials and service masters are available in the SAP SRM system. To check them, use
transaction COMMPR01 (role SAPCRM_MENUE: Master Data Products Process Products ).
More Information
See SAP Note 765018 (Problems with logical system during data exchange).
7.4.2 More Information About Materials and Service Master Download
Select Business Objects
The following SAP Note applies: SAP Note 519794
Run the following system transaction in SAP SRM: Set Up Business Objects Exchange (R3AC1)
Start Initial Download
The following SAP Note applies: SAP Note 309734
Run the following system transaction in SAP SRM: Start Initial Load (R3AS)
7 Master Data Replication
7.4 Materials and Service Master Download
2013-08-13 PUBLIC 53/148
7.5 Checking Downloads
You can run the following transactions to check whether you have successfully replicated your supplier
master data:
■ Application Log: Display Logs (SLG1)
Displays a detailed log of a specific transaction
■ Shows New Vendor Repl. from Backend (BBP_SNEW_SYNCVD)
Displays newly replicated suppliers as of a specific point in time
■ Display Supplier Groups (PPOSV_BBP)
Displays the available supplier groups and supplier in the SAP SRM system
Prerequisites
You have replicated the supplier master data.
Procedure
Run the above transactions.
7 Master Data Replication
7.5 Checking Downloads
54/148 PUBLIC 2013-08-13
8 Organizational Management
8.1 User Management
8.1.1 Organizational Structure
8.1.1.1 Creating the Organizational Plan
Prerequisites
You must first make settings for external locations (see Making Settings for Locations and External Business
Partners [page 57]).
Procedure
CAUTION
You must only create the first user with transaction SU01. You use the SAP NetWeaver Portal
application to create all subsequent users.
1. Go to transaction SU01 and create an ABAP user.
2. Assign this user the administrator role /SAPSRM/ADMINISTRATOR.
3. As this administrator, create your organizational plan.
At the very least, you must create a root node for the organizational plan. The remaining
organizational units can be created by the employees and managers themselves using the self-
service Web application. We recommend that you define your organizational plan to at least
departmental level, specify which organizational units are purchasing organizations and
purchasing groups, and create the user master records for the managers of the departments using
the Portal application SRM Administration:
1. In Customizing for SAP Supplier Relationship Management, create the root organizational
unit by choosing SRM Server Cross-Application Basic Settings Organizational Management Create
Organizational Plan . Remember to enter an address for the organizational unit.
NOTE
You start to create the organizational plan in the Customizing activity Create Organizational
Plan (transaction PPOCA_BBP). After leaving this activity, you make changes to the
organizational plan in the Customizing activity Change Organizational Plan (transaction
PPOMA_BBP).
2. Create the remaining organizational units.
If you define a company, purchasing organization, or purchasing group you have to select the
corresponding indicator on the Function tab page.
8 Organizational Management
8.1 User Management
2013-08-13 PUBLIC 55/148
CAUTION
You must enter an address for each organizational unit. If you fail to do so, the self-service
Web transaction for creating users will not work.
4. Using the SAP NetWeaver Portal application, Business partner: Employee, create user master
records for the departmental managers (users with the role /SAPSRM/MANAGER) and assign the
managers to the relevant organizational units. Managers have three functions within the
organizational plan:
■ They assign users to organizational units.
■ They either approve new users or specify a default role that renders approval unnecessary. If
a default role is assigned, the approval process can be deactivated.
■ They maintain important user attributes.
After the managers have been created via the Portal application, check PPOMA_BBP to make
sure that all the users have been attached to the appropriate organizational units. Make sure
that the indicator is set for the Head of Own Organizational Unit check box for each manager.
5. Create an organizational root node for your suppliers in transaction PPOCV_BBP.
6. After creating your organizational plan, you can run a report to check that a business partner has
been defined for each node in the organizational structure. In Customizing for SAP Supplier
Relationship Management, choose SRM Server Cross-Application Basic Settings Organizational
Management Integration Business Partner – Organizational Management Match Up Organizational Units and
Persons with Business Partners .
CAUTION
You first have to set up the integration with Organizational Management in Customizing for
SAP Supplier Relationship Management, by choosing SRM Server Cross-Application Basic Settings
Organizational Management Integration Business Partner – Organizational Management Set Up Integration
with Organizational Management . Note that you only have to do this if you use the HR replication
method to set up the organizational structure instead of setting the structure up manually.
NOTE
If errors occur for any of the organizational root nodes, select the node in the Object Overview
screen (on the right side), and choose Start Resynchronization.
You first need to consider the error messages and correct them in PPOMA_BBP, for example,
then you can execute the resynchronization.
We recommend that you define the attributes VENDOR_ACS (accounting system for the
supplier) and VENDOR_SYS (system alias for supplier) at a high level in the organizational plan.
In Customizing for SAP Supplier Relationship Management, choose SRM Server Technical Basic
Settings Define Back-end Systems .
7. After creating your organizational structure, you can run a report to check that the attributes
have been defined correctly for the individual applications allowed for the users: transaction
BBP_ATTR_CHECK or report BBP_CHECK_CONSISTENCY.
8 Organizational Management
8.1 User Management
56/148 PUBLIC 2013-08-13
Enhancing the Organizational Plan
To make the connection between purchasing organizations and purchasing groups more flexible, you
can lessen the hierarchical restrictions of the organizational model by activating the Business Add-In
(BAdI) Display of Input Helps, Search Helps, and Favorites and by performing the Customizing activity Influence
Message Control to deactivate the checks in the method layer. In this case, the hierarchical restrictions
only have default character.
Choose the following in Customizing for SAP Supplier Relationship Management:
■ SRM Server Business-Add-Ins Interface Configuration Input Helps and Search Helps Display of Input
Helps, Search Helps and Favorites
■ SRM Server Cross-Application Basic Settings Message Control Influence Message Control
Employees that are assigned to the line organization of the HR organizational model, and
simultaneously work as purchasers in an SAP SRM purchasing organization, can be assigned to the
new relationship type Is Purchaser of.
In the Purchasing View of transaction PPOMA_BBP you have several possibilities to assign the purchaser to
a purchasing group:
■ Using drag and drop within the hierarchy
■ Using drag and drop from the selection area into the hierarchy
■ Using the Assign button and the search help to find the object to be assigned to the selected unit
in the hierarchy
8.1.1.2 Making Settings for Locations and External Business Partners
This section describes the settings you need to make for locations and external business partners.
PrerequisitesYou have defined the following:
■ Business partner groupings and assigned number ranges in Customizing for Cross-Application
Components SAP Business Partner Business Partner Basic Settings Number Ranges and Groupings Define
Groupings and Assign Number Ranges . You must ensure that at least one standard grouping with
external number assignment has been defined with the ‘External Standard Grouping’ indicator
set for this grouping.
■ Number ranges for address management in Customizing for SAP Web Application Server, by
choosing Application Server Base Basis Services Address Management Maintain Address and Person
Number Range .
■ Partner functions in Customizing for SAP Supplier Relationship Management SRM Server Cross-
Application Basic Settings Define Partner Functions .
You can enter the texts you want to use for the partner function for a partner function type. These
texts are displayed in the relevant documents for a business transaction.
8 Organizational Management
8.1 User Management
2013-08-13 PUBLIC 57/148
Prerequisites for External Business Partners
1. You must first create the organizational plan with at least one organizational unit to which the
external business partners can be assigned (supplier root node). For more information, see SAP
Solution Manager under <project> Configuration SAP SRM <release> Basic Settings for Service
Procurement External Staffing Settings for Supplier Self-Services Defining Organizational Plans for Suppliers .
2. You must first create business number ranges and groupings. For more information, see SAP
Solution Manager under <project> Configuration SAP SRM <release> Basic Settings for Service
Procurement External Staffing Settings for Supplier Self-Services Number Ranges for Documents
NOTE
The internal business number range should not overlap with the external number range for
suppliers.
Procedure
Locations
You can use the following three ABAP reports to download locations from the back-end system and
store them as business partners in SAP SRM.
BBP_LOCATIONS_GET_ALL To retrieve all the location numbers from each back-end system that is connected
BBP_LOCATIONS_GET_FROM_SYSTEM To retrieve all the location numbers from one particular back-end system
BBP_LOCATIONS_GET_SELECTED To retrieve selected locations
Prior to SAP SRM 3.0 (EBP 4.0), locations were not given business partner numbers in SAP SRM system.
If you are configuring an upgrade, you can use ABAP reports BBP_LOCATIONS_GET_FROM_SYSTEM and
BBP_LOCATIONS_GET_SELECTED to check that the following conversions have been made:
■ Conversion of user favorites
■ Conversion of user attributes
■ Conversion of old documents
The ABAP report BBP_LOCATIONS_GET_ALL checks these automatically.
Once you have run these ABAP reports, the location data is available in the SAP SRM system. Table
BBP_LOCMAP contains the mapping information (in other words, which business partner number
corresponds to which location in which back-end system).
For more information, see SAP Note 563180 — Locations for EBP 4.0 – plant replication
External Business Partners
1. Replicating or creating the supplier master records.
The supplier master records must exist in the system. They have to be replicated from the back-
end system and assigned to at least one purchasing organization. Alternatively, they can be created
using the application Managing External Business Partners.
8 Organizational Management
8.1 User Management
58/148 PUBLIC 2013-08-13
For more information, see help.sap.com SAP Supplier Relationship Management Functions Global
Functions External Business Partners Manage External Business Partners .
2. Schedule updating of business partner addresses in Customizing for SAP Supplier Relationship
Management under SRM Server Cross-Application Basic Settings Organizational Management Integration
Business Partner – Organizational Management Schedule Periodic Comparison .
8.1.1.3 Defining the Supplier Structure
Procedure
You can display the supplier group for external supplier organizational units and suppliers in
transaction PPOMV_BBP. The supplier group is represented in this transaction as an organizational object
to which the suppliers are assigned.
You can edit the supplier group attributes in transaction PPOMV_BBP.
NOTE
Suppliers are created and maintained in SAP SRM by users with the Administrator role. You can
maintain business partner Supplier and business partner Bidder in the SAP NetWeaver Portal.
8.1.1.4 More Information About Organizational Structure
Make Settings for Locations and External Business Partners
Perform the following activity in Customizing for SAP SRM: Cross-Application Components SAP Business
Partner Business Partner Basic Settings Number Ranges and Groupings Define Number Ranges
Define Organizational Structure
Run the following system transactions in SAP SRM: HR: Set Up Central Person (OO_CENTRAL_PERSON)
Display Organizational Structure
Perform the following activity in Customizing for SAP SRM: SAP Supplier Relationship Management SRM
Server Cross-Application Basic Settings Organizational Management Display Organizational Plan
8.1.2 Creating Portal Users
When you create a business partner user in SAP Supplier Relationship Management (SAP SRM), for
example, an employee or supplier contact person, you must also create a user in the SAP NetWeaver
Portal. In SAP enhancement package 3 for SAP SRM 7.0, you can create Portal users automatically by
following the configuration steps outlined below:
1. Create an RFC destination for the Portal server in the SAP SRM client.
2. Activate the UME-SPML connection.
8 Organizational Management
8.1 User Management
2013-08-13 PUBLIC 59/148
3. Map the Portal role to the SAP SRM roles.
4. Check the SAPJSF user.
Prerequisites
You must have downloaded Business Package for SAP SRM 7.0 EHP3.
Procedure
Creating an RFC destination for the Portal server in the SAP SRM client
1. Run transaction SM59.
2. Select HTTP connection to External Server and choose Create.
3. In the RFC Destination field, enter SPML.
4. In the Connection Type field, enter G.
5. In the Target Host field, enter the Portal server.
6. In the Service No field, enter the port number of the Portal server.
7. In the Logon & Security tab, choose Basic Authentication.
8. In the Logon & Security tab, enter the SAPJSF user and password.
9. Save your entries.
Activating the UME-SPML connection
In Customizing, go to SRM Server Master Data Create Users Activate UME-SPML Connector .
In the RFC Destination field, select the entry (SPML) that you created in the previous step.
Select Activate SPML and save your changes.
Mapping the portal role to the SAP SRM roles
In this step, you need to find the Portal role unique ID for the SAP SRM roles required and maintain
the personalization settings in the SAP SRM client for each role.
To find the Portal role unique ID, proceed as follows:
1. Log on in the Portal as an Administrator.
2. Go to User Administration.
3. Open existing user.
4. Go to Assigned Roles.
5. Select the required Portal role and choose Show Details.
6. Copy the unique ID.
7. Note the unique IDs of all required roles.
Next, you must maintain the personalization settings as follows:
1. Run transaction PFCG.
2. Open the /SAPSRM/* role in change mode and select Personalization.
3. Double-click Personalizations Object Key for Mapping EP and SRM Roles (/SAPSRM/SRM_ROLES).
4. Add the corresponding Portal roles unique ID.
8 Organizational Management
8.1 User Management
60/148 PUBLIC 2013-08-13
5. Repeat the above steps for the /SAPSRM/BIDDER and /SAPSRM/SUPPLIER roles.
Checking SAPJSF user and Role Assignment
1. Run transaction SU01.
2. Select the SAPJSF user and confirm that it has the following roles assigned:
■ SAP_BC_JSF_COMMUNICATION
■ SAP_BC_JSF_COMMUNICATION_RO
8.1.3 Maintain User Attributes
8.1.3.1 User Attributes in SAP SRM
The following table lists the attributes available in SAP Supplier Relationship Management (SAP SRM).
NOTE
Some of the attributes are only simulated. The attributes are marked accordingly in the table
T77OMATTR. Tables that are not attribute tables form the basis of user attribute simulation.
Attributes indicated as system-dependent can have different values in different systems.
Attribute Description and Example Value
Definition System-Dependent
ACS System alias for accounting systemsExample value: ABCCLNT123
Specifies the back-end system where the account assignment is checked. This attribute is required for: ■ Invoices without purchase order reference ■ Local invoices
(In the case of a supplier, the back-end system is determined using the attribute VENDOR_ACS)
We recommend that you define this attribute at a high level in your organizational plan.Prerequisite: You must have defined the back-end system in Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings Define Basic Settings. .
ADDR_BILLT Invoice recipient address
Default invoice recipient address in purchase order.
ADDR_SHIPT Ship-to addressExample value: 12345
Default ship-to party address in purchase order.Enter at least one ship-to address and set it as the default address.
AN1 AssetExample value: ABCCLNT123\000000001111
Specifies the asset in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.
AN2 Asset subnumberExample value: Q4CCLNT300\1234
Defines the asset sub-number in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.
8 Organizational Management
8.1 User Management
2013-08-13 PUBLIC 61/148
ANK Asset classExample value: QW4CLNT100\00001000
Defines the asset class in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.
ANR OrderExample value: ABCCLNT123\000000000040
Defines the order in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.
APO Sales order itemExample value: Q4CCLNT300\123456
Defines the sales order item in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.
APPRV_LIM Approval limit The value up to which a user is allowed to approve.You define this attribute using tab card Extended attributes.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan.
AUN Sales orderExample value: ABCCLNT123\000000000333
Specifies the sales order in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.
BSA Transaction type: Shopping cart follow-on documentExample value: ABCCLNT123\ECA3
Defines the transaction type in the respective system for follow-on documents from shopping carts.The attribute needs to be defined once per system, for the local SAP SRM system and for all connected back-end systems.
BUDGET User budget Amount available to an employee for purchases. Required for the Purchasing Budget Workflow [external document].
BUK Company codeExample value: QW4CLNT100\1000
Company code in the back-end system.Generally, the user inherits the company code from his/her company. If you want to overwrite the value inherited from the company you should define the company code via this attribute only.You define the company code of the company for the organizational unit assigned to the company on the Function tab.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan.
BWA Movement typeExample value: ABCCLNT123\123
Defines the type of goods movement in the back-end system. This value is required if reservations are to be created in the back-end system.
CAT Catalog IDExample value: MDMCA30
Defines the catalogs to which a user has access. You must define this attribute in Customizing for SAP Supplier Relationship Management under SRM Server Master Data
Content Management Define External Web Services.
8 Organizational Management
8.1 User Management
62/148 PUBLIC 2013-08-13
CNT Cost centerExample value: ABCCLNT123\0000001000
Defines the cost center in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.
COCODE Company Code Company Code
COMPANY Company Identifies a legally independent section of the company.This attribute is simulated. The simulated value contains the number of an organizational unit that is indicated as company in the organizational plan.It identifies an organizational unit as company on the Function tab.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan.
CT_PROC_TY Transaction Type: Contract
Transaction Type for Contract
CUR Local currencyExample value: EUR
Default currency of the user
DP_PROC_TY Transaction type: Direct materialExample value: ECDP
Specifies the transaction type that is used when purchase orders for direct materials are created via BAPI, shopping cart, or bid invitation/bid. You have to maintain this attribute for the responsible purchasing group (see also the attribute TEND_TYPE). The specified transaction type has to correspond to the document type used in the back-end system for direct material purchase orders with external number assignment. The value for this attribute can be inherited. For example, purchasing groups can inherit it from their purchasing organization.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Define Transaction Types.
EXT_ITS Current ITS of an external partnerExample value: http://abc.firma.com/wgate/
Obsolete from SRM 7.0
FORWARD_WI Flag: Forward work itemExample value: X
Indicator: Specifies whether work items are to be forwarded as e-mails.
IS_COMPANY Indicator: Company
Indicator: Identifies an organizational unit as independent legal entity.This attribute is simulated. You set this indicator for an organizational unit on the Function tab by selecting Company.You should define an organizational unit high up in the organizational plan as company by setting this indicator. If you have further organizational units in a lower level of
8 Organizational Management
8.1 User Management
2013-08-13 PUBLIC 63/148
your plan that represent subsidiaries, you also need to set this indicator.See Customizing for SAP Supplier Relationship Management under: SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan.
IS_PGR Indicator: Purchasing group
This indicator specifies that an organizational unit is identified as purchasing group.This attribute is simulated. You set this indicator on the Function tab.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan.
IS_POR Indicator: Purchasing organization
This indicator specifies that an organizational unit is identified as purchasing organization.This attribute is simulated. You set this indicator on the Function tab.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan.
ITS_DEST Current ITS of a userExample value: http://abc.firma.com/wgate/
Obsolete from SRM 7.0
KNT Account assignment categoryExample value: CC
Default value for account assignment when creating shopping cart or lean purchase order.The default value for the account assignment is determined on the basis of the value for this attribute (for example CC - cost center) in connection with the relevant account assignment object (in this example CNT cost center).Note: In Customizing, no check occurs to establish whether the value for the relevant account assignment object is maintained.
LAG Storage location An organizational unit that allows you to differentiate between different material stocks within a plant.You define this attribute on the Extended Attributes tab.
NET NetworkExample value: ABCCLNT123\000000600003
Specifies the network in the back-end system. Default value for account assignment when creating shopping cart or lean purchase order.
PM_ARWRK Plant for work centerExample value: ABCCLNT123\1234
Plant in which the executing work center is located.This attribute is used as a selection criterion when searching for orders in the back-end system.
PM_AUART Order type Order types distinguish orders according to their use, for example, maintenance and service orders.
8 Organizational Management
8.1 User Management
64/148 PUBLIC 2013-08-13
Example value: ABCCLNT123\PM01
This attribute is used as a selection criterion when searching for orders in the back-end system.
PM_GL_ACCT PM: Default G/L accountExample value: ABCCLNT123\417000
Default value for the G/L account in the component detail data.
PM_IPHAS PhaseExample value: ABCCLNT123\0
Phases subdivide the life cycle of an order into several subsections (for example, created and released) and determine which activities are allowed for the order in each section.This attribute is used as a selection criterion when searching for orders in the back-end system.This is a mandatory attribute.
PM_IWERK Planning plantExample value: ABCCLNT123\1234
Plant at which maintenance tasks are planned and prepared.This attribute is used as a selection criterion when searching for orders in the back-end system.
PM_PUR_GRP PM purchasing groupExample value: ABCCLNT123\001
Number of the organizational unit that is indicated as the purchasing group in the organizational plan. Default value in the component detail data.
PM_PUR_ORG PM purchasing organizationExample value: ABCCLNT123\1000
Number of an organizational unit that is indicated as the purchasing organization in the organizational plan. Default value in the component detail data.
PM_SWERK Maintenance plantExample value: ABCCLNT123\1234
Plant at which the technical objects of a company are installed.This attribute is used as a selection criterion when searching for orders in the back-end system.
PM_VAWRK Plant for main work centerExample value: ABCCLNT123\1234
Plant at which the main work center entered is located.This attribute is used as a selection criterion when searching for orders in the back-end system.
PM_WGR PM material groupExample value: ABCCLNT123\000000001
Indicates the key of the material group that unites materials and services with the same properties. Default value in the component detail data.
PM_WRK Plant of the componentExample value: ABCCLNT123\1000
Plant at which the component required to execute the order (reservation or requirement request) is planned. Default value in the component detail data.This is a mandatory attribute.
PRCAT Material group Defines the product categories for which the user has authorization. We recommend that you define a default value. For example, if a user mainly purchases office materials, it would make sense to specify office materials as the default value.
8 Organizational Management
8.1 User Management
2013-08-13 PUBLIC 65/148
To improve performance, we recommend that you use wildcards and ranges to restrict the product categories defined as much as possible.You define this attribute using tab card Extended attributes.
PRI Default printerExample value: PRINTER
Printer name
PRO WBS element Defines the WBS element The work breakdown structure (WBS) represents the hierarchical organization of a project. WBS elements are the individual structural elements in a work breakdown structure Default value for account assignment when creating shopping cart or lean purchase order.
PURCH_GRP Purchasing group Number of an organizational unit that is indicated as local purchasing group in the organizational plan.This attribute is simulated. You define an organizational unit as purchasing group on the Function tab.
PURCH_GRPX ERP purchasing group
Number of the organizational unit that is indicated as the purchasing group in the organizational plan. The value contains the ID and the associated back-end system of a back-end purchasing group.This attribute is simulated. You define the ID and the associated system on the Function tab.
PURCH_ORG Purchasing organization
Number of an organizational unit that is indicated as local purchasing organization in the organizational plan.This attribute is simulated. You define an organizational unit as purchasing organization on the Function tab.
PURCH_ORGX R/3 purchasing organization
Number of an organizational unit that is indicated as the purchasing organization in the organizational plan.This attribute is simulated. You define the ID and the associated system on the Function tab.
REQUESTER Goods recipientExample value: See definition
Indicates the organizational units or users for which this employee can create shopping carts, and so on.A user can select all users in an organizational unit as alternative goods recipients if the attribute is maintained with the following entry, for example: O 50000019.If a specific user is to be selected as alternative goods recipient, the attribute needs to be maintained as follows: <US><User ID of alternative goods recipient>, for example USMANAGER22.Before you can order direct materials, you must have defined the necessary plants. You use this attribute to define these plants in the organizational plan. You enter plants as follows: <type_BP><partner_number_for_plant>, for example, BP1195.For the purposes of the direct materials scenario the business partner number (it can have a maximum of ten
8 Organizational Management
8.1 User Management
66/148 PUBLIC 2013-08-13
positions) defined in this attribute must be linked to a plant in table CRMM_LOCMAP.Buy on behalf of: To enable substitute shopping you enter all users for whom a purchasing assistant can buy on behalf of.The values defined for the attribute form the basis for the F4 help for the Goods Recipient field available to the purchasing assistant or other employee creating shopping carts for other users in the Shop scenario.
RESP_PRGRP Purchasing group responsible
Number of the organizational unit for which the purchasing group is responsible.This attribute is simulated. You define the organizational responsibility of a purchasing group on the Responsibility tab.
RESP_PRCAT Product category responsible
Number of the product category for which the purchasing group is responsible.This attribute is simulated. You define the product responsibility of a purchasing group on the Responsibility tab.
ROLE User roleExample value: /SAPSRM/EMPLOYEE
Indicates the role of the user, for example manager, employee, or purchasing assistant.If no approval workflow for new users is in force, a default value must be set for the attribute ROLE, for example /SAPSRM/EMPLOYEE. (If no default value is found, the approval workflow is activated automatically.)
SF_FOOTER SAP Smart Forms: Footer
Defines the footer to be used when purchase orders or contracts are output. The values are determined using Smart Forms on the basis of the purchasing group. You define the footer using the transaction SE78.
SF_GRAPHIC SAP Smart Forms: Company logo
Defines the company logo to be used when purchase orders or contracts are output. The values are determined using Smart Forms on the basis of the purchasing group. You define the company logo using transaction SO10.
SF_HEADER SAP Smart Forms: HeaderExample value: BBP_COMPANY
Defines the header to be used when purchase orders or contracts are output. The values are determined using Smart Forms on the basis of the purchasing group. You define the header using the transaction SE78.
SLAPPROVER Spending limit approverExample value: USMANAGER1
Specifies the approver used in workflows based on a spending limit.
SPEND_LIM Spending limit The value up to which a user is allowed to spend before the spending limit approval workflow is triggered.You define this attribute using tab card Extended attributes.
SYS System aliasExample value: ABCCLNT123
Defines the systems to be searched to find purchase orders. This attribute is used to generate worklists for employees that create confirmations or invoices centrally. The attribute can refer both to the local system and back-end
8 Organizational Management
8.1 User Management
2013-08-13 PUBLIC 67/148
systems. Generally, several values are defined: The local systems and various back-end systems.You must define the systems in Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings Define Basic Settings.
TEND_TYPE Transaction type: Bid invitationExample value: BID
Specifies the transaction type for bid invitations created automatically, for example in the PLM (collaborative engineering). You define this attribute for the purchasing group that is responsible for the organizational unit of the entry channel. The value for this attribute can be inherited. For example, purchasing groups can inherit it from their purchasing organization. You define the transaction type in Customizing.See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Define Transaction Types.
TOG Tolerance groupExample value: CONF
Defines the tolerance group. Using this attribute, you define for a user group which tolerance checks are used when quantity or value tolerances for deliveries or invoices are exceeded.
VENDOR_ACS Accounting system for the vendorExample value: ABCCLNT123
Specifies the back-end system where the account assignment is checked. This attribute is required for: ■ Invoices without purchase order reference ■ Local invoices.We recommend that you define this attribute at a high level in your organizational plan.Prerequisite: You must have defined the back-end system in Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings Define Basic Settings.
VENDOR_SYS System alias for vendorExample value: ABCCLNT123
Defines the systems to be searched to find purchase orders to create a worklist for a vendor creating confirmations or invoices centrally. Can refer both to the local system and to the back-end system. Generally, multiple values are entered: The local systems and various back-end systems.You must define the systems in Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings Define Basic Settings.
WGR Product category See attribute PRCAT.This attribute is simulated. The values of the attribute PRCAT serve as the basis for the simulation.Whilst you can define single values, masks, and areas for PRCAT, you can only use single values for WGR.
WRK Plant Specifies the plant in the ERP back-end system. This attribute is only required if the back-end system is an SAP System.You define this attribute using tab card Extended attributes.
8 Organizational Management
8.1 User Management
68/148 PUBLIC 2013-08-13
8.1.3.2 Defining User Attributes in the Organizational Plan
System administrators can define the most important user attributes at organizational unit level in the
organizational plan using the Customizing activity Change Organizational Plan (transaction PPOMA_BBP).
You define the attributes using the tab pages Function, Responsibility, Attributes, and Extended Attributes. The
following table provides an overview of the attributes that you define on each tab page:
Function Responsibility Extended attributes Attributes
■ Companies ■ Purchasing
organizations ■ Purchasing groups
NOTE
For purchasing groups only.
■ Product responsibility (for product groups)
■ Organizational responsibility (for departments and groups)
■ Product categories ■ Plants ■ Storage locations ■ Approval limits
All other attributes
If managers want to edit attributes for their organizational units, or users in their organizational units,
they can use the Web application Change Attributes. Employees can use this Web application to change
their own attributes.
Prerequisites
You have defined at least the top node of your organizational plan with transaction PPOCA_BBP. See
Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Settings
Organizational Management Create Organizational Plan
Procedure
1. See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Settings
Organizational Management Change Organizational Plan .
Alternatively, use transaction PPOMA_BBP.
2. Search for the organizational unit for which you want to define user attributes.
Defining attributes using tab card Function
1. On the Details screen, choose tab card Function.
2. Specify whether the organizational unit is a company, a purchasing organization, or a purchasing
group.
Defining attributes using tab card Responsibility
NOTE
The details on this tab page replace the previously used attributes RESP_PGRP, RESP_PRCAT, and
RESP_WGR on the tab pages Attributes and Extended Attributes.
1. On the Details screen, choose tab card Responsibility.
8 Organizational Management
8.1 User Management
2013-08-13 PUBLIC 69/148
2. Specify the product categories and organizational units for which the purchasing group is
responsible. You can use wildcards (*) and ranges to do this.
Defining attributes using tab card Attributes
1. On the Details screen, choose tab card Attributes.
2. Enter a value for each attribute you wish to define.
3. To locally deactivate an attribute value for a certain organizational unit, and to prevent it being
inherited by a subordinate organizational unit, set the Excluded indicator.
4. To define an attribute value as the default value in cases where multiple values exist, check
Default.
5. Save your entries.
Defining attributes using tab card Extended Attributes
NOTE
You define a logical system for the attributes Material Group, Storage Location, and Plant. This logical
system is the source system for the data, not the target system to which the business documents
are later transferred. You can define the target system for a material group in Customizing for
SAP Supplier Relationship Management under SRM Server Technical Basic Settings Define Backend System
for Product Category .
1. On the Details screen, choose tab card Extended Attributes.
2. For Extended Attribute, choose the attribute that you want to define.
■ Product categories
You can define product categories (material groups) (attributes PRCAT and WGR). You can enter
both individual product category IDs, as well as value areas and wildcards (*).
■ Plants
You can define plants (attribute WRK) together with the relevant company code.
■ Storage locations
You can define storage locations (attribute LAG) together with the relevant value and the
logical system.
■ Order value limits
You can define the spending limit (attribute SPEND_LIM) and approval limit (attribute
APPRV_LIM) and the user budget together with the currency
3. To locally deactivate an attribute value for a certain organizational unit, and to prevent it being
inherited by a subordinate organizational unit, set the Deactivate indicator.
4. To define an attribute value as the default value in cases where multiple values exist, check
Default.
5. Save your entries.
8 Organizational Management
8.1 User Management
70/148 PUBLIC 2013-08-13
Result
The attributes you have defined are saved in the organizational plan.
8.1.3.3 Maintaining the User Attributes
Prerequisites
■ You have created the root node of the organizational plan.
■ Before managers can approve the creation of new user master records, they have been assigned
the manager role /SAPSRM/MANAGER.
■ To enable the Web application Edit Attributes, you have assigned a change authorization to the role
responsible for changing the user attributes.
Go to Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic
Settings Roles Maintain Attribute Access Rights by Role .
Procedure
1. Specify values for the main user attributes using the transaction PPOMA_BBP, tab card Attributes. For
most attributes you can do this using the Web application Edit Attributes. Important attributes
include:
■ Product categories: The product responsibilities have to be set on the tab card Extended
Attributes (attribute PRCAT).
■ Systems: ACS, SYS
■ Document types: BSA
■ Role: ROLE
■ Direct material transaction type: DP_PROC_TY
■ Contract transaction type: CT_PROC_TY
■ Procurement attributes: The procurement attributes define the function (company,
purchasing organization, or purchasing group) and the responsibilities of an organizational
unit (attributes PURCH_GRP, PURCH_GRPX, PURCH_ORG, PURCH_ORGX, RESP_PGRP, RESP_PRCAT in
the earlier SAP SRM releases)
■ Procurement attributes have to be set on the tab cards Function and Responsibility.
■ Currency: CUR
■ Ship-to address: ADDR_SHIPT
■ Transaction type for RFx created from Sourcing: TEND_TYPE
■ Default printer: This attribute is as well used when adding bidders to an RFx or Auction. The
user can select an Output Medium. In case of Printer, the system reads the default printer settings
from the user attributes: PRI
2. To make sure all attributes that are necessary for your business scenario have been specified, you
can start transaction BBP_ATTR_CHECK.
1. Mark the User Attributes for Application check type.
8 Organizational Management
8.1 User Management
2013-08-13 PUBLIC 71/148
2. Execute the report for the relevant applications.
8.1.4 User Attributes
A set of user attributes is required for working with SAP Supplier Relationship Management (SAP SRM).
Each user attribute represents a value that is stored under a particular name within the organizational
structure. Depending on a user's role, a different set of attributes is required.
NOTE
Employees must have certain user attributes to allow them to create shopping carts without
having much information about the business background.
A set of attributes is predefined for each of the standard roles supplied with SAP SRM, for example,
company code, catalog ID, and purchasing organization.
You maintain attributes by scenario. The scenario for SAP SRM is called BBP.
You can define attributes either for a particular user (that is, per position) or for an organizational unit.
■ System administrators can define the most important user attributes at organizational unit level.
The purchasing organization and purchasing group are also defined using attributes.
■ Managers can change the attributes defined for their organizational unit(s) or for users in their
organizational unit(s).
■ Users can change their own attributes, provided they are authorized.
Integration
The user attributes are integrated into the organizational plan.
Prerequisites
■ The root node for the organizational plan has been defined in Customizing for SAP SRM: SRM
Server Cross-Application Basic Settings Organizational Management Create Organizational Plan .
■ A first user has been created and assigned to the root node of the organizational plan.
Features
■ Definition of multiple values for attributes
■ Definition of default values for attributes with multiple values
You maintain these default values in the organizational plan.
■ Definition of different values for system-dependent attributes in different systems for
configurations with several back-end systems.
To see which attributes are system-dependent, refer to the table of attributes in SAP Solution
Manager under Attributes for the SRM Scenario.
8 Organizational Management
8.1 User Management
72/148 PUBLIC 2013-08-13
NOTE
If you define system-dependent attributes, you must enter the system name followed by a
backslash in front of the attribute name.
■ Different types of inheritance for attributes:
● Normal or additive inheritance
● Local values overwrite inherited values
● Local values do not overwrite inherited values. In this case, redefinition is not allowed.
● No inheritance
Activities
We recommend that the system administrator specify values for the main user attributes. For more
information, refer to Customizing for SAP SRM under SRM Server Cross-Application Basic Settings
Organizational Management Change Organizational Plan.
Before an employee can create a shopping cart, for example, the following attributes must have values
assigned to them:
Attribute Description
ACS System alias for accounting (system in which account assignment is checked)
BSA Document type in back-end system
BUK Company code
BWA Movement type (if back-end system reservations have been created)
CUR Local currency
KNT Account assignment category
WGR Product category
WRK Plant in back-end system
■ Define the attributes Ship-to address (ADDR_SHIPT) and Company (COMPANY) at least once at a high level
in the organizational plan. The number of the organizational unit is then copied to the COMPANY
attribute. The Ship-to address and Company attributes are then inherited by organizational units at a
lower level in the organizational plan. If you define other organizational units as subsidiaries, you
can identify these as separate legal entities with different addresses using these attributes.
■ Assign attributes to roles and maintain the access rights for attributes by role. A set of roles with
predefined user attributes is supplied. However, it is possible to create company-specific roles in
the customer name range and assign user attributes to them. See Customizing under SRM Server
Cross-Application Basic Settings Roles Maintain Attribute Access Rights per Role .
■ Display the attribute properties, such as attribute text, type of inheritance, priority, and whether
the attribute is visible.
CAUTION
Do not change the properties of supplied user attributes.
8 Organizational Management
8.1 User Management
2013-08-13 PUBLIC 73/148
Procedure
More Information
For more information about the maintenance of user data, see User and Employee Data [external document].
8.1.5 More Information About User Management
Maintain User Attributes
Run the following system transactions in SAP SRM: EBP Organizational Model: Checks (BBP_ATTR_CHECK).
Import Users from File or from Other Systems
Perform the activity in Customizing for SAP Supplier Relationship Management under SRM Server Master
Data Create Users Import Users from File or from Other System .
8.2 Roles
8.2.1 Harmonized Procurement Roles for SAP ERP and SAP SRM
Using the harmonized Operational Purchaser and Strategic Purchaser roles, users have a single point
of access to Personal Object Worklists (POWLs) and to services that allow them to create and process
purchasing documents in either SAP Supplier Relationship Management (SAP SRM) or in SAP ERP.For
each role, SAP offers two variants:
■ SAP ERP and SAP SRM Systems
The purchaser or strategic purchaser is working with procurement documents in one or more
SAP ERP systems and in an SAP SRM system. For this purpose, you use the roles Operational
Purchaser (ERP/SRM) - EHP2 and Strategic Purchaser (ERP/SRM) - EHP2.
■ Several SAP ERP Systems
The purchaser or strategic purchaser is working with procurement documents in several SAP ERP
systems, but not in an SAP SRM system. For this purpose, you use the roles Operational Purchaser
(ERP) - EHP2 and Strategic Purchaser (ERP) - EHP2.
NOTE
While the Buyer role provided in SAP ERP only allows you to search for procurement
documents in a single SAP ERP system, the Operational Purchaser (ERP) - EHP1 and Strategic
Purchaser (ERP) - EHP2 roles allow you to select procurement documents from all SAP ERP
systems that you have connected. Note you must have an SAP SRM system implemented to
use this selection option because the respective dialog box is provided by the SAP SRM system.
The harmonized procurement roles support various organizational structures:
■ Local procurement, whereby the procurement process is carried out decentrally within
individual purchasing departments.
8 Organizational Management
8.2 Roles
74/148 PUBLIC 2013-08-13
■ Central procurement, whereby major parts of the procurement process, for example contract
management, RFx handling, and sourcing are carried out centrally by a central purchasing
department.
Features
The harmonized procurement roles for SAP ERP and SAP SRM have the following features:
Operational Purchaser (ERP/SRM) - EHP2
By default, the Operational Purchaser (ERP/SRM) - EHP2 role contains the following worksets:
■ Work Overview, providing, for example, workflow items, alerts, notifications, and tasks for
operational purchasers.
■ Purchasing Documents, allowing operational purchasers to work with shopping carts in SAP
SRM as well as purchase requisitions in SAP ERP. Purchasers can also access the Sourcing
applications of SAP SRM or SAP ERP to complete incomplete documents and assign sources of
supply. They can work with all purchase orders that are available, either in SAP ERP or SAP SRM,
depending on where the documents were originally created, and they can access purchase order
responses in SAP SRM.
■ Receiving, allowing operational purchasers to specifically access purchase orders waiting for goods
receipt and purchase orders waiting for service entry, as well as service entry sheets in SAP ERP.
Purchasers can also work with purchase orders with pending confirmations in SAP SRM.
■ Invoice Processing, allowing operational purchasers to work with SAP ERP and SAP SRM
purchase orders waiting for invoices, as well as working with invoices in SAP ERP.
■ Supplier Master Data
■ Material Master Data
■ Service Master Data
The three worksets related to master data allow operational purchasers to access the main
procurement-related iViews for master data handling in SAP ERP that are included in the Buyer role
in SAP ERP (delivered as of Business Package for Buyer 1.5). For information about this business package,
see SAP Library for SAP ERP Central Component on SAP Help Portal at http://help.sap.com.
Strategic Purchaser (ERP/SRM) - EHP2
By default, the Strategic Purchaser (ERP/SRM) - EHP2 role contains the following worksets:
■ Work Overview, providing, for example, workflow items, alerts, notifications, and tasks for
strategic purchasers.
■ Strategic Sourcing, allowing strategic purchasers to work with requests for quotation in SAP ERP
as well as RFx documents and auctions in SAP SRM.
■ Contract Management, allowing strategic purchasers to work with contracts and scheduling
agreements in the SAP ERP system as well as central contracts and quota arrangements in the SAP
SRM system.
■ Workload Redistribution
■ Business Partner
8 Organizational Management
8.2 Roles
2013-08-13 PUBLIC 75/148
Operational Purchaser (ERP) - EHP2
By default, the Operational Purchaser (ERP) - EHP2 role contains the following worksets:
■ Work Overview, providing, for example, workflow items, alerts, notifications, and tasks for
operational purchasers.
■ Purchasing Documents, allowing operational purchasers to work with purchase requisitions
and purchase orders in SAP ERP.
■ Receiving, allowing operational purchasers to specifically access purchase orders waiting for goods
receipt and purchase orders waiting for service entry, as well as service entry sheets in SAP ERP.
■ Invoicing, allowing operational purchasers to work with purchase orders waiting for invoices as
well as invoices in SAP ERP.
■ Supplier Master Data
■ Material Master Data
■ Service Master Data
The three worksets related to master data allow operational purchasers to access the main
procurement-related iViews for master data handling in SAP ERP that are included in the Buyer role
in SAP ERP (delivered as of Business Package for Buyer 1.5). For information about this Business Package,
see SAP Library for SAP ERP Central Component on SAP Help Portal at http://help.sap.com.
Strategic Purchaser (ERP) - EHP2
By default, the Strategic Purchaser (ERP) - EHP2 role contains the following worksets:
■ Work Overview, providing, for example, workflow items, alerts, notifications, and tasks for
strategic purchasers.
■ Strategic Sourcing, allowing strategic purchasers to work with requests for quotation and info
records in SAP ERP.
■ Contract Management, allowing strategic purchasers to work with contracts and scheduling
agreements in SAP ERP
8.2.2 Regenerating Role Profiles
You have to regenerate the authorizations for each role that you intend to use. This ensures that the
profiles belonging to these roles are assigned all the required authorizations.
Go to Customizing for Supplier Relationship Management: SRM Server Cross-Application Basic Settings
Roles Define Roles
Procedure
1. Enter the name of the role for which you want to generate the profile.
2. Choose Change.
3. Choose Authorizations.
4. Choose Display Authorization Data.
8 Organizational Management
8.2 Roles
76/148 PUBLIC 2013-08-13
5. Choose Generate.
6. Repeat steps 1 to 5 for each role required.
You can also generate multiple profiles in Role Maintenance, PFCG:
CAUTION
If you copy one of the roles delivered by SAP, you need to maintain attribute access rights by
role.
Go to Customizing for Supplier Relationship Management: SRM Server Cross-Application
Basic Settings Roles Maintain Attribute Access Rights by Role .
For more information, see SAP Note 644124.
7. Choose Utilities Mass generation
8. Select All Roles
9. Enter /SAPSRM/*
10. Choose Execute.
8.2.3 Maintaining the User Attributes
Prerequisites
■ You have created the root node of the organizational plan.
■ Before managers can approve the creation of new user master records, they have been assigned
the manager role /SAPSRM/MANAGER.
■ To enable the Web application Edit Attributes, you have assigned a change authorization to the role
responsible for changing the user attributes.
Go to Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic
Settings Roles Maintain Attribute Access Rights by Role .
Procedure
1. Specify values for the main user attributes using the transaction PPOMA_BBP, tab card Attributes. For
most attributes you can do this using the Web application Edit Attributes. Important attributes
include:
■ Product categories: The product responsibilities have to be set on the tab card Extended
Attributes (attribute PRCAT).
■ Systems: ACS, SYS
■ Document types: BSA
■ Role: ROLE
■ Direct material transaction type: DP_PROC_TY
■ Contract transaction type: CT_PROC_TY
■ Procurement attributes: The procurement attributes define the function (company,
purchasing organization, or purchasing group) and the responsibilities of an organizational
8 Organizational Management
8.2 Roles
2013-08-13 PUBLIC 77/148
unit (attributes PURCH_GRP, PURCH_GRPX, PURCH_ORG, PURCH_ORGX, RESP_PGRP, RESP_PRCAT in
the earlier SAP SRM releases)
■ Procurement attributes have to be set on the tab cards Function and Responsibility.
■ Currency: CUR
■ Ship-to address: ADDR_SHIPT
■ Transaction type for RFx created from Sourcing: TEND_TYPE
■ Default printer: This attribute is as well used when adding bidders to an RFx or Auction. The
user can select an Output Medium. In case of Printer, the system reads the default printer settings
from the user attributes: PRI
2. To make sure all attributes that are necessary for your business scenario have been specified, you
can start transaction BBP_ATTR_CHECK.
1. Mark the User Attributes for Application check type.
2. Execute the report for the relevant applications.
8.2.4 More Information About Roles
For more Information, see SAP Help Portal at http://help.sap.com under SAP Supplier Relationship
Management Business Packages Business Package for SAP SRM 7.13 Harmonized Procurement Roles for SAP ERP
& SAP SRM .
8.3 Integration of Business Partners into Organizational Management
8.3.1 Setting Up Integration with Organizational Management
NOTE
This step only needs to be carried out if you are using the HR replication method to set up the
organizational structure. It is not required if you are setting up the structure manually.
Procedure
Proceed as described in Customizing for SAP Supplier Relationship Management under SRM Server Cross-
Application Settings Organizational Management Integration Business Partner — Organizational Management Set Up
Integration with Organizational Management
8.3.2 Scheduling Periodic Comparison
You need to check and update business partner addresses from organizational units at regular intervals
to prevent data inconsistencies.
8 Organizational Management
8.3 Integration of Business Partners into Organizational Management
78/148 PUBLIC 2013-08-13
When a business partner is created for an organizational unit, the current address of the unit is copied
from the unit to the business partner master record. If the address data of the organizational unit is
changed, the address copied to the business partner master record will be invalid.
Procedure
To compare and synchronize address data, you need to do the following steps:
1. Call transaction SE38.
2. Create a variant of the program HRALXSYNC.
3. Schedule the variant to run periodically in transaction SM36.
For more information, see Customizing for SAP Supplier Relationship Management under SRM Server
Cross-Application Basic Settings Organizational Management Integration Business Partner — Organizational
Management Schedule Periodic Comparison .
8.3.3 More Information About Integrating Business Partners into Organizational Management
Set Up Integration with Organizational Management
The following SAP Notes apply:
■ 550055
■ 1148817
Match Organizational Units and Persons with Business Partners
Perform the following activity in Customizing for SAP SRM: SAP Supplier Relationship Management SRM
Server Cross-Application Basic Settings Organizational Management Integration Business Partner — Organizational
Management Match Up Organizational Units and Persons with Business Partners
8 Organizational Management
8.3 Integration of Business Partners into Organizational Management
2013-08-13 PUBLIC 79/148
This page is left blank for documents that are printed on both sides.
9 Locations and Business Partners
9.1 Making Settings for Locations and External Business Partners
This section describes the settings you need to make for locations and external business partners.
Prerequisites
You have defined the following:
■ Business partner groupings and assigned number ranges in Customizing for Cross-Application
Components SAP Business Partner Business Partner Basic Settings Number Ranges and Groupings Define
Groupings and Assign Number Ranges . You must ensure that at least one standard grouping with
external number assignment has been defined with the ‘External Standard Grouping’ indicator
set for this grouping.
■ Number ranges for address management in Customizing for SAP Web Application Server, by
choosing Application Server Base Basis Services Address Management Maintain Address and Person
Number Range .
■ Partner functions in Customizing for SAP Supplier Relationship Management SRM Server Cross-
Application Basic Settings Define Partner Functions .
You can enter the texts you want to use for the partner function for a partner function type. These
texts are displayed in the relevant documents for a business transaction.
Prerequisites for External Business Partners
1. You must first create the organizational plan with at least one organizational unit to which the
external business partners can be assigned (supplier root node). For more information, see SAP
Solution Manager under <project> Configuration SAP SRM <release> Basic Settings for Service
Procurement External Staffing Settings for Supplier Self-Services Defining Organizational Plans for Suppliers .
2. You must first create business number ranges and groupings. For more information, see SAP
Solution Manager under <project> Configuration SAP SRM <release> Basic Settings for Service
Procurement External Staffing Settings for Supplier Self-Services Number Ranges for Documents
NOTE
The internal business number range should not overlap with the external number range for
suppliers.
9 Locations and Business Partners
9.1 Making Settings for Locations and External Business Partners
2013-08-13 PUBLIC 81/148
Procedure
Locations
You can use the following three ABAP reports to download locations from the back-end system and
store them as business partners in SAP SRM.
BBP_LOCATIONS_GET_ALL To retrieve all the location numbers from each back-end system that is connected
BBP_LOCATIONS_GET_FROM_SYSTEM To retrieve all the location numbers from one particular back-end system
BBP_LOCATIONS_GET_SELECTED To retrieve selected locations
Prior to SAP SRM 3.0 (EBP 4.0), locations were not given business partner numbers in SAP SRM system.
If you are configuring an upgrade, you can use ABAP reports BBP_LOCATIONS_GET_FROM_SYSTEM and
BBP_LOCATIONS_GET_SELECTED to check that the following conversions have been made:
■ Conversion of user favorites
■ Conversion of user attributes
■ Conversion of old documents
The ABAP report BBP_LOCATIONS_GET_ALL checks these automatically.
Once you have run these ABAP reports, the location data is available in the SAP SRM system. Table
BBP_LOCMAP contains the mapping information (in other words, which business partner number
corresponds to which location in which back-end system).
For more information, see SAP Note 563180 — Locations for EBP 4.0 – plant replication
External Business Partners
1. Replicating or creating the supplier master records.
The supplier master records must exist in the system. They have to be replicated from the back-
end system and assigned to at least one purchasing organization. Alternatively, they can be created
using the application Managing External Business Partners.
For more information, see help.sap.com SAP Supplier Relationship Management Functions Global
Functions External Business Partners Manage External Business Partners .
2. Schedule updating of business partner addresses in Customizing for SAP Supplier Relationship
Management under SRM Server Cross-Application Basic Settings Organizational Management Integration
Business Partner – Organizational Management Schedule Periodic Comparison .
9.2 Partner Address Types
9.2.1 Managing Business Partner Addresses
Procedure
Activity Description For more information, see:
9 Locations and Business Partners
9.2 Partner Address Types
82/148 PUBLIC 2013-08-13
Defining address types You must have specified the six address types shipped with SAP Enterprise Buyer, for example, goods recipient (GOODS_REC).
Customizing for SAP SRM under SRM Server Master Data Business
Partner Manage Address TypesDefine Address Types
Assigning transactions to address types
You must have assigned predefined transactions to the address types you created. There is a recommended set of assignments, including, for example, the assignment of transaction Ship Goods to the Ship-To address.
Customizing for SAP SRM underSRM Server Master Data Business
Partner Manage Address TypesAssign Transaction to Address Type
9.3 Number Ranges
9.3.1 Defining Number Ranges for Business Partners
For business partners which are transferred from external systems, you define number ranges with
external number assignment.
Procedure
You define business partner number ranges (for internal and external number assignment) in the
central business partner maintenance.
See Customizing under Cross-Application Components SAP Business Partner Business Partner Basic Settings
Number Ranges and Groupings Define Number Ranges .
NOTE
When replicating suppliers from multiple back-end systems, the number range (for which the
standard indicator has been set) is used for external number assignment.
Therefore, we recommended configuring this number range big enough to cover all number
ranges set in the individual back-end systems.
See Customizing under Cross-Application Components SAP Business Partner Business Partner Basic
Settings Number Ranges and Groupings Define Groupings and Assign Number Ranges .
9.4 Locations and Business Partners
Specify Data Privacy Settings for Suppliers
Perform the following activities in Customizing for SAP SRM: SAP Supplier Relationship Management
SRM Server Master Data Business Partner Specify Data Privacy Settings for Suppliers
Define Partner Schema
Perform the following activities in Customizing for SAP SRM: SAP Supplier Relationship Management
SRM Server Cross-Application Basic Settings Define Partner Schema
9 Locations and Business Partners
9.3 Number Ranges
2013-08-13 PUBLIC 83/148
Check Locations
Run the following system transactions in SAP SRM: Application Log: Display Logs (SLG1)
9 Locations and Business Partners
9.4 Locations and Business Partners
84/148 PUBLIC 2013-08-13
10 Supplier Master Data Replication
10.1 Settings for Supplier Synchronization
10.1.1 Locked Suppliers
Suppliers that have been locked in SAP Enterprise Resource Planning (SAP ERP) are also replicated as
locked suppliers in SAP Supplier Relationship Management (SAP SRM). When a supplier has been
replicated and is subsequently locked, the lock indicator is displayed in the supplier master data as well.
It is not possible to prevent a locked supplier from being replicated, as to do so would create data
inconsistencies between SAP ERP and SAP SRM.
10.1.2 Creating and Registering Root Supplier Groups
In SAP Supplier Relationship Management (SAP SRM), you must create a root supplier group as
suppliers are grouped together in groups at the organizational plan level. You can do this in
Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings
Settings for Supplier Synchronization Create Supplier Groups .
To enable the SAP SRM processes to assign newly created suppliers to the organizational plan, you
must register the root supplier group, as follows:
■ For supplier maintenance and data transfer between SAP SRM and Supplier Self Services or SAP
Registration of Suppliers (ROS) systems, go to Customising for SAP Supplier Relationship
Management under SRM Server Technical Basic Settings Settings for Supplier Synchronization
Information on Automatic Download from Marketplace .
NOTE
The Vendor Root attribute must have the following format: VGxxxxxxxx, the object type
identifier ‘VG’ followed by the 8-digit ID with no spaces.
■ For replication of suppliers from SAP ERP systems, go to Customising for SAP Supplier Relationship
Management under SRM Server Technical Basic Settings Settings for Supplier Synchronization Define
Global Settings .
NOTE
The format is the 8-digit ID without the leading object type identifier ‘VG’
If the root supplier group is not created or not registered, neither supplier data maintenance, nor
supplier replication/distribution is possible.
10 Supplier Master Data Replication
10.1 Settings for Supplier Synchronization
2013-08-13 PUBLIC 85/148
10.1.3 More Information About Settings for Supplier Synchronization
Make Global Settings
Perform the following Customizing activity in SAP SRM: SRM Server Technical Basic Settings Settings
for Supplier Synchronization Define Global Settings .
Define Settings for Each Back-End System
Perform the following Customizing activity in SAP SRM: SRM Server Technical Basic Settings Settings
for Supplier Synchronization Define Settings for Each Backend System .
Maintain Supplier Groups
Perform the following Customizing activity in SAP SRM:
■ SRM Server Technical Basic Settings Settings for Supplier Synchronization Notes on Supplier Replication .
■ SRM Server Technical Basic Settings Settings for Supplier Synchronization Create Supplier Groups .
■ SRM Server Technical Basic Settings Settings for Supplier Synchronization Change Supplier Groups .
■ SRM Server Technical Basic Settings Settings for Supplier Synchronization Display Supplier Groups
■ SRM Server Technical Basic Settings Settings for Supplier Synchronization Information on Automatic Download
from Marketplace
10.2 Replicating Supplier Master Data
You can transfer all supplier master data from the selected back-end system to the SAP SRM system
by means of transaction Transfer Supplier Master (BBPGETVD).
NOTE
For performance reasons, we recommend that you schedule this report as a weekly job. To do so,
go to the SAP menu and choose System Services Jobs Define Job .
Prerequisites
You have made the settings described in the Prerequisites section of Making Settings for Supplier Replication
[external document].
Procedure
1. Run transaction BBPGETVD.
2. On the transaction selection screen, you can do the following:
■ Specify the logical system that corresponds to the back-end system from which you want to
retrieve the supplier master data.
■ Restrict your supplier selection if required.
■ Specify further selections options.
10 Supplier Master Data Replication
10.2 Replicating Supplier Master Data
86/148 PUBLIC 2013-08-13
■ Specify the supplier root. The supplier root contains all the supplier groups you have defined
in the SAP SRM system. The supplier root is created with transaction Create Supplier Groups
(PPOCV_BBP).
■ By default, only SAP ERP numbers (formerly known as R/3 numbers) are transferred. Internal
numbers refer to SAP SRM numbers.
3. Choose Start Transfer.
4. On the second screen, choose Start Transmission.
5. View the application log of the transaction after completion of the transfer, as described in Checking
Downloads [page 54].
Result
Your supplier master data is automatically replicated to the SAP SRM system, and is stored as business
partner data.
10.3 Checking Downloads
You can run the following transactions to check whether you have successfully replicated your supplier
master data:
■ Application Log: Display Logs (SLG1)
Displays a detailed log of a specific transaction
■ Shows New Vendor Repl. from Backend (BBP_SNEW_SYNCVD)
Displays newly replicated suppliers as of a specific point in time
■ Display Supplier Groups (PPOSV_BBP)
Displays the available supplier groups and supplier in the SAP SRM system
Prerequisites
You have replicated the supplier master data.
Procedure
Run the above transactions.
10 Supplier Master Data Replication
10.3 Checking Downloads
2013-08-13 PUBLIC 87/148
This page is left blank for documents that are printed on both sides.
11 Cross-Application Settings
11.1 Defining Configurable Item Numbering Scheme
Perform the following Customizing activities in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Configurable Item
Numbering Define Configurable Item Numbering Scheme
11.2 Activating Revision Level Field for Document
In this Customizing activity, you enable the revision level field (technical field name “REV_LEV”) on
the SAP SRM business documents.
Procedure
Perform the following Customizing activity in SAP SRM: SAP Supplier Relationship Management SRM
Server Cross-Application Basic Settings Extensions and Field Control (Personalization) Configure Field Control
Configure Control for Fields on Item Level
Example
Configure the revision level field in the SAP SRM Contract business object:
Structure Field Name REV_LEV
Bus. Object Type BUS2000113
Bus. Object Subtype ‘ ‘
Transaction Type ‘ ‘
Item Type ‘ ‘
Item Process Type ‘ ‘
Field Visible X
Field Enabled X
Field Required ‘ ‘
11.3 Output Actions and Format
11.3.1 Defining Actions for Document Output
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Set Output Actions and
Output Format Define Actions for Document Output
11 Cross-Application Settings
11.1 Defining Configurable Item Numbering Scheme
2013-08-13 PUBLIC 89/148
11.3.2 Condition-Dependent Document Output
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Set Output Actions and
Output Format Condition-Dependent Document Output
11.4 Hierarchies
11.4.1 Uploading Product Category Hierarchy Files from External Systems
Procedure
To upload product category hierarchy information to SAP Supplier Relationship Management (SAP
SRM 7.0) through a flat file adapter, see the detailed instructions provided in SAP Note 831808
Attachments .
11.4.2 More Information About Hierarchies
Define Contract Hierarchies
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Activate Hierarchies for
Product Categories, Suppliers, and Contracts
Define Product Category Hierarchies
Perform the following Customizing activities in SAP SRM:
■ SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Activate Hierarchies
for Product Categories, Suppliers, and Contracts
■ SAP Supplier Relationship Management SRM Server Business Add-Ins Master Data Adaptation of Product
Category Hierarchy
Assign category hierarchies to applications in Customizing for Cross-Application Components under SAP
Product Product Category Assign Category Hierarchies to Applications
Define Supplier Hierarchies
Perform the following Customizing activities in SAP SRM:
■ SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Activate Hierarchies
for Product Categories, Suppliers, and Contracts
■ SAP Supplier Relationship Management SRM Server Business Add-Ins Master Data Change Supplier
Hierarchy Types
11 Cross-Application Settings
11.4 Hierarchies
90/148 PUBLIC 2013-08-13
11.5 Number Ranges for Documents
11.5.1 Defining Number Ranges
You specify the number ranges for the Materials Management documents in the SAP SRM system.
You must specify number ranges for the following local documents:
■ Shopping carts
■ Purchase orders
■ Purchase contracts
■ Purchase order responses
■ Confirmations for goods and services
■ Invoices
■ RFx
■ RFx Responses
■ Auction
■ Supplier list
■ Survey package
■ Survey
If you create Materials Management documents in the back-end system, you also determine in SAP
SRM the internal number range for:
■ Purchase requisitions
■ Purchase orders
■ Reservations
■ Service Entry Sheet
This is then used in the back-end system as an external number range.
You can define different number ranges for different back-end systems.
NOTE
The number range interval for a back-end document (for example, a back-end purchase order)
must be the same as the internal number range that you use for the local document in SAP SRM
7.0. The number range in the back-end system must use external number assignment.
Procedure
In Customizing for SAP SRM Classic Scenario, define number ranges by choosing SRM Server Cross-
Application Basic Settings Number Ranges SRM Server Number Ranges Define Number Ranges for Shopping Carts
and Follow-On Documents .
CAUTION
The interval number for the shopping cart number range must be the value of Int.No. that you
have defined for the transaction type of the shopping cart.
11 Cross-Application Settings
11.5 Number Ranges for Documents
2013-08-13 PUBLIC 91/148
For more information, see Customizing for SAP SRM 7.0 under SRM Server Cross-Application
Basic Settings Define Transaction Types .
11.5.2 More Information About Number Ranges for Documents
Number Ranges for Documents in Different Back-End Systems
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Number Ranges SRM
Server Number Ranges Define Number Ranges per Backend System for Follow-on Documents
Assign Shopping Carts and Follow-On Documents
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Number Ranges SRM
Server Number Ranges Define Number Ranges for Shopping Carts and Follow-On Documents
Assign Local Purchase Orders
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Number Ranges SRM
Server Number Ranges Define Number Ranges for Local Purchase Orders
Assign Purchase Order Responses
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Number Ranges SRM
Server Number Ranges Define Number Ranges for Purchase Order Response
Assign Local Confirmations of Services and Goods Receipts
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Number Ranges SRM
Server Number Ranges Define Number Ranges for Local Confirmations of Services and Goods Receipts
Assign Local Invoices
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Number Ranges SRM
Server Number Ranges Define Number Ranges for Local Invoices
Assign Invoice Defaults
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Number Ranges SRM
Server Number Ranges Define Number Ranges for Invoice Defaults
11 Cross-Application Settings
11.5 Number Ranges for Documents
92/148 PUBLIC 2013-08-13
Assign Purchasing Contracts
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Number Ranges SRM
Server Number Ranges Define Number Ranges for Purchase Contracts
11.6 Text Schema and Text Mapping
Define Text Types
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Text Schema Define Text
Types
Define Text Schemas
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Text Schema Define Text
Schema
Define Fixed Values for Text Types
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Text Schema Define Fixed
Values for Texts
Text Mapping for Internal Texts
NOTE
Before mapping texts, run report /SAPSRM/GET_TEXT_CUST_ERP in the SAP Supplier Relationship
Management (SAP SRM) system to copy texts from the back-end system to the SAP SRM system.
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Text Mapping Text
Mapping for Internal Texts
Text Mapping for Inbound and Outbound Texts
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Text Mapping Text
Mapping for Inbound and Outbound Texts
11.7 Define Transaction Types
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Define Transaction
Types
11 Cross-Application Settings
11.6 Text Schema and Text Mapping
2013-08-13 PUBLIC 93/148
11.8 Activate Extended Classic Scenario
11.8.1 Setting Up Extended Classic Scenario
NOTE
You cannot run the Service Procurement External Staffing scenario in extended classic mode.
This section describes the settings for connecting a back-end system to SAP SRM and for enabling the
extended classic scenario.
Prerequisites
You have set up the following:
■ The back-end system with its logical system and its RFC destination has been set up.
■ To enable the extended classic scenario for SAP SRM on a back-end system from SAP R/ 3 Release
4.6 B, you have to specify a purchasing group when you create a back-end purchase order. To this
end, you have done one of the following:
● If the local purchasing group has a purchasing organization with no reference to the back-
end system, you must have specified a purchasing group that is valid in the back-end system
for the EKG parameter of the RFC user.
● You have used the customer exits of the BAPIs BAPI_PO_CREATE1 and BAPI_PO_CHANGE
to determine the purchasing group.
● In SAP SRM you use a purchasing group and a purchasing organization with a reference to
the back-end system, in the same way as you do for the SAP SRM classic scenario. In this way,
you transfer organizational data to the back-end system.
Procedure
Activating the Extended Classic Scenario
If you use the extended classic scenario, you must activate it in SAP SRM.
In Customizing for SAP SRM, activate the extended classic scenario by choosing SRM Server Cross-
Application Basic Settings Activate Extended Classic Scenario .
Implementing a BAdI to Control the Extended Classic Scenario
If you want to control the extended classic scenario in a more differentiated way (for example, depending
on product category), you can use an SRM Server Business Add-In (BAdl).
In Customizing for SAP SRM, choose SRM Server Business Add-Ins Control Extended Classic Scenario
Activate Extended Classic Scenario .
11 Cross-Application Settings
11.8 Activate Extended Classic Scenario
94/148 PUBLIC 2013-08-13
11.9 Business Workflow
11.9.1 Select Workflow Framework
Perform the following activity in Customizing for SAP SRM: SRM Server Cross-Application Basic Settings
Business Workflow Select Workflow Framework .
11.9.2 Process-Controlled Workflow
11.9.2.1 Approval Process Settings
You can use this process to configure the settings required to use process-controlled workflows.
NOTE
Note that you can easily set up an automatic (zero-step) approval workflow or a one-step approval
workflow by applying Business Configuration Sets (BC Sets). If you do so, you do not need to
perform the configuration steps described below.
If you want to set up an automatic (zero-step) approval workflow, you can configure an approval
process that does not involve the SAP Business Workflow. Owing to schema naming conventions,
we recommend to use a zero-step BC Set to activate this scenario. If you use this scenario, no work
items are generated.
For more information, see Business Configuration Sets for SAP SRM [page 96].
Prerequisites
You have created your organizational structure at least down to departmental level. For more
information, see Creating the Organizational Plan [page 55].
Before you can assign responsible agents to standard tasks, you must have created the required users
or regenerated the roles, as appropriate. For more information, see Regenerating Role Profiles [page 76].
Procedure
To use process-controlled workflows, you must perform the following configuration steps:
1. Define technical configuration
These standard workflow settings apply to all SAP components. You can, for example, check the
prefix number used for the new workflow template and for the related tasks.
For more information, see Technical Configuration [page 98] and the related documentation for SAP
NetWeaver 7.0 in SAP Help Portal at http://help.sap.com SAP NetWeaver Library SAP NetWeaver
by Key Capability Application Platform by Key Capability Business Services SAP Business Workflow .
2. Define settings for Business Rule Framework (BRF)
The BRF is a flexible tool that allows you to create SRM-specific events and expressions. Events
and expressions are used to evaluate process schemas and process levels.
11 Cross-Application Settings
11.9 Business Workflow
2013-08-13 PUBLIC 95/148
For more information, see Business Rule Framework Settings [page 99] and SAP Library for SAP ERP
Central Component on SAP Help Portal at http://help.sap.com SAP Library SAP ERP Cross-
Application Functions Cross-Application Services Business Rule Framework (BRF) .
3. Define business process configuration for process-controlled workflows
In this step, you set up your approval processes using process schemas and process levels. You also
define how the agents responsible for approving documents are determined.
For more information, see Process-Controlled Workflow Settings [page 102].
11.9.2.2 Business Configuration Sets for SAP SRM
SAP Supplier Relationship Management (SAP SRM) supplies a number of Business Configuration Sets
(BC Sets) which contain the Customizing settings necessary for process-controlled workflows. To use
a BC Set, you must first activate it. If you use a BC Set to configure a workflow, you do not have to
configure the Business Rule Framework (BRF) nor define a process schema for this process.
For more information about BC Sets, see the related documentation for SAP NetWeaver 7.0 in SAP
Help Portal at http://help.sap.com under SAP NetWeaver Library SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability Customizing Business Configuration Sets (BC-CUS) .
Features
BC Sets are available for the following business objects:
■ Shopping cart
■ Purchase order
■ Confirmation
■ Invoice
■ Contract
■ Supplier Quote
■ RFx
For each of these business objects, there is one BC Set to customize a process without approval, and
one to customize a process with one-step manager approval. When you activate a BC Set, the system
automatically creates a process schema and configures all necessary process levels. For each business
object, you can activate one BC Set only.
BC Sets for Processes Without Approval
The process schema configured when you activate a BC Set for processes without approval contains
only one process level, in which the items of the document are approved automatically.
In these processes, there are no reviewers, no defaults for ad hoc approvers, and the contact person
does not receive a work item for acceptance when the approval process is finished.
11 Cross-Application Settings
11.9 Business Workflow
96/148 PUBLIC 2013-08-13
If you use only BC Sets for processes without approval and you have not configured any other process
schemas, SAP Business Workflow is not involved and you do not have to perform any Customizing
activities for SAP Business Workflow.
BC Sets that configure processes without approval use the naming convention /SAPSRM/
C_<BO>_600_000_SP04.
BC Sets for Processes With One-Step Manager Approval
The process schema configured when you activate a BC Set for processes with one-step manager
approval contains one process level for approval by the document creator's manager, and one for
automatic decision. If the system cannot determine a responsible agent, the document is rejected
automatically.
In these processes, there are no reviewers, no defaults for ad hoc approvers, and the contact person
does not receive a work item for acceptance when the approval process is finished.
BC Sets that configure processes with one-step manager approval use the naming convention /SAPSRM/
C_<BO>_600_001_SP04.
Available BC Sets
To activate BC Sets, use transaction SCPR20. The following BC Sets are available:
Business Object BC Set Process Schema Description
Shopping cart /SAPSRM/C_SC_600_000_SP04 9C_SC_600_000_SP04 Without approval
/SAPSRM/C_SC_600_001_SP04 9C_SC_600_001_SP04 One-step manager approval
Purchase order /SAPSRM/C_PO_600_000_SP04 9C_PO_600_000_SP04 Without approval
/SAPSRM/C_PO_600_001_SP04 9C_PO_600_001_SP04 One-step manager approval
Confirmation /SAPSRM/C_CO_600_000_SP04 9C_CO_600_000_SP04 Without approval
/SAPSRM/C_CO_600_001_SP04 9C_CO_600_001_SP04 One-step manager approval
Invoice /SAPSRM/C_IN_600_000_SP04 9C_IN_600_000_SP04 Without approval
/SAPSRM/C_IN_600_001_SP04 9C_IN_600_001_SP04 One-step manager approval
Contract /SAPSRM/C_CT_600_000_SP04 9C_CT_600_000_SP04 Without approval
/SAPSRM/C_CT_600_001_SP04 9C_CT_600_001_SP04 One-step manager approval
Quote /SAPSRM/C_QT_600_000_SP04 9C_QT_600_000_SP04 Without approval
/SAPSRM/C_QT_600_001_SP04 9C_QT_600_001_SP04 One-step manager approval
RFx /SAPSRM/C_RQ_600_000_SP04 9C_RQ_600_000_SP04 Without approval
/SAPSRM/C_RQ_600_001_SP04 9C_RQ_600_001_SP04 One-step manager approval
11 Cross-Application Settings
11.9 Business Workflow
2013-08-13 PUBLIC 97/148
11.9.2.3 Define Technical Configuration
11.9.2.3.1 Technical Configuration
You can use this process to configure the SAP Business Workflow for use with SAP Supplier Relationship
Management (SAP SRM) process-controlled workflows.
Process
To configure the SAP Business Workflow, you must perform the steps described below. You can find
these steps in Customizing for SAP SRM under SRM Server Cross-Application Basic Settings Business
Workflow Process-Controlled Workflow Technical Configuration .
■ Customize SAP Business Workflow Automatically
You can perform extensive checks to ensure that the settings for the standard business workflow
are complete. To do so, run report Perform Automatic Workflow Customizing. You can also process each
step individually.
■ Check Event Trigger Configuration
Ensure that the triggering event READY_FOR_WORKFLOW has been linked to the main workflow
template (WS40000014). A triggering event is required to start the workflow.
■ Check Event Type Linkage
Here, you can also ensure that the triggering event READY_FOR_WORKFLOW has been linked
to the main workflow template (WS40000014). By default, the workflow template is active.
In addition, ensure that the triggering event READY_FOR_RELEASE has been linked to the
receiver type SRM_PROCESS_START. This event is required to trigger the event handler.
■ Generalize Tasks
Set all tasks of task groups TG 40000003 and TG 40000007 as 'general'. General tasks can be processed
by all users.
■ Check Task Generalization
Ensure that the related tasks have been delivered as general tasks and that they are consistent.
General tasks are tasks for which user assignment is unrestricted. The tasks belonging to task groups
TG 40000003 and TG 40000007 must be defined as general tasks.
■ Check Task Consistency
Check whether tasks are consistent or not. This step is optional.
■ Copy BRF Objects
Execute report BRF_TRANSPORT_SIMPLE to copy Business Rule Framework (BRF) objects to your
test system.
Result
You can go to Business Rule Framework Settings [page 99] to define SAP SRM-specific events and expressions.
11 Cross-Application Settings
11.9 Business Workflow
98/148 PUBLIC 2013-08-13
11.9.2.4 Define Settings for Business Rule Framework
11.9.2.4.1 Business Rule Framework Settings
In SAP Supplier Relationship Management (SAP SRM), the Business Rule Framework (BRF), with its
events and expressions, is used for the following:
■ To evaluate process schemas
■ To evaluate process levels
■ To define defaults for ad hoc process levels
■ To determine whether the contact person receives a work item when the approval process is
finished
■ To define rules based on which reviewers are added to the approval process
For more information about the BRF, see SAP Library for SAP ERP Central Component on SAP Help
Portal at http://help.sap.com SAP Library SAP ERP Cross-Application Functions Cross-Application
Services Business Rule Framework (BRF) BRF Objects and BRF for Developers.
Process
To define BRF settings, you must perform the steps described below.
You can find these steps in Customizing for SAP SRM under SRM Server Cross-Application Basic Settings
Business Workflow Process-Controlled Workflow BRF Configuration .
NOTE
If you use Business Configuration Sets (BC Sets) to set up your approval processes, you do not
have to configure the BRF for these processes. For more information, see Business Configuration Sets
for SAP SRM [page 96].
Define Events
To define events, start the Business Rule Framework Workbench (transaction BRF).
BRF events form a connection between the SAP SRM system and the BRF. They are the central entry
point for using the BRF. You must assign an event to each process schema, so that the system can
determine the process schema to be used for a specific approval process. You must also assign an event
to each process level, so that the system can determine for each process level whether or not the process
level needs to be performed. Each event contains a BRF expression.
Define Expressions
To define expressions, start the Business Rule Framework Workbench (transaction BRF).
You can choose from various expression types, for example:
■ 0CN001 - Constant
■ 0CF001 - Call function module/method
■ 0FB001 - SAP formula interpreter
■ 0CE001 - Case expression
11 Cross-Application Settings
11.9 Business Workflow
2013-08-13 PUBLIC 99/148
■ 0RV001 - Random generator
A constant expression, for example, can be used to return the shopping cart limit. You can also use the
SAP Formula Interpreter to build more complex expressions. For more information, see SAP Library
for SAP ERP Central Component on SAP Help Portal at http://help.sap.com SAP Library SAP ERP
Cross-Application Functions Cross-Application Services Business Rule Framework (BRF) BRF Objects Expression
Expression Type .
When an event is triggered, the system reads the expression that is assigned to the event and returns a
result that determines further processing. You can nest expressions; in other words, expressions can
access results of other expressions.
SAP SRM delivers a number of expressions that you can use. These are listed and explained in a document
on SAP Service Marketplace at http://service.sap.com/srm-inst SAP SRM Server 7.0 Workflow
Guide — SAP SRM 7.0 . You can also create your own expressions. For more information, see Creating
BRF Expressions for SRM Approval Processes [page 100].
Define Groups
This optional step allows you to classify BRF objects. For example, you can group all events that are
used to evaluate workflow levels.
Result
You can go to Process-Controlled Workflow Settings [page 102] to set up your approval processes and define
how the agents responsible for approving documents are determined.
11.9.2.4.2 Creating BRF Expressions for SRM Approval Processes
SAP Supplier Relationship Management (SAP SRM) delivers a number of Business Rule Framework
(BRF) expressions that you can use to set up your process-controlled workflows. These expressions are
listed and explained in a document on SAP Service Marketplace at http://service.sap.com/srm-
inst SAP SRM Server 7.0 Workflow Guide — SAP SRM 7.0 . If the delivered expressions do not meet
your requirements, you can also create your own expressions.
Procedure
To create BRF expressions, start the Business Rule Framework Workbench (transaction BRF) or go to
SAP Solution Manager under Configuration Structures SAP SRM 7.0 Basic Settings for SAP SRM Cross-
Application Settings Business Workflow Process-Controlled Workflow Define Settings for Business Rule Framework
Define Expressions .
Most of the expressions used in SAP SRM are nested expressions that use a function module to evaluate
constant expressions.
To create an expression with function module access (type 0CF001), do the following:
11 Cross-Application Settings
11.9 Business Workflow
100/148 PUBLIC 2013-08-13
1. In the BRF Objects field, enter SRM_WF.
2. Expand Applicatn Class SRM_WF All Groups .
3. Select Expressions and choose Create BRF Object. A dialog box appears.
4. In the Expression field, enter a technical name. Select an implementation class, in this case 0CN001.
Choose Continue.
5. Enter a short text.
6. Optionally, you can assign the expression to a group.
7. Select a result type, for example, B (Boolean), C (character), D (date), or F (floating point number).
8. In the Fld/Struct Lngth field and in the Output Length field, enter the required values.
9. In the Access FM field, enter function module /SAPSRM/WF_BRF_0EXP000. This function module
provides access to the business object attributes of the document to be approved.
10. In the Parameter table, enter the constant expressions you need, depending on the data type of the
business object attribute. The parameter patterns described below are defined for the following
data types:
■ Simple data type: The result is stored, for example, in a character field.
■ Table: The result is a table that can have more than one entry.
■ Object: The attribute itself is a business object. The system then checks an attribute of this
business object. This attribute can in turn be a simple data type, a table, or another object.
NOTE
To find out the data type of the business object attribute, go to transaction SWO1 and
choose the required business object and the attribute.
The following parameter patterns apply:
■ For business object attributes with simple data types:
● 1st parameter: name of the business object class; represented by a constant expression
(prefix 0C_C1_C_)
● 2nd parameter: method 0C_C2_C_GET_PROPERTY
● 3rd parameter: name of the business object attribute; represented by a constant expression
(prefix 0C_C3_C_)
■ For business object attributes with tables as data types:
● 1st parameter: name of the business object class; represented by a constant expression
(prefix 0C_C1_C_)
● 2nd parameter: method 0C_C2_C_GET_TABLE_PROPERTY
● 3rd parameter: name of the business object table attribute; represented by a constant
expression (prefix 0C_C3_C_)
● 4th parameter: value for which the system checks if that value is contained in the table;
represented, for example, by a constant expression (prefix 0C_C4_C_)
● 5th parameter and following: optional additional values for which the system checks if
the values are contained in the table; represented, for example, by a constant expression
11 Cross-Application Settings
11.9 Business Workflow
2013-08-13 PUBLIC 101/148
(prefix 0C_C4_C_). The system checks if the table contains at least one of the values
entered as 4th, 5th, or following parameter.
■ For business object attributes with object types:
● 1st parameter: name of the business object class; represented by a constant expression
(prefix 0C_C1_C_)
● 2nd parameter: method 0C_C2_C_GET_PROPERTY
● 3rd parameter: name of the business object attribute; represented by a constant expression
(prefix 0C_C3_C_). In this case, the attribute itself is a business object.
● 4th parameter and following: name of the attribute of the business object returned by the
preceding parameter; represented by a constant expression (prefix 0C_C3_C_)
NOTE
If you use self-defined constant expressions, the parameters can also be in customer
namespace A-Z, for example, using the prefix AC_C2_C_.
■ Save your entries.
Example
Expression 0V_SC_CREATEDBY returns the user name of the shopping cart creator.
The parameters used for function module /SAPSRM/WF_BRF_0EXP000 are as follows:
■ 1st parameter: 0C_C1_C_FWFSCRLCNTNT for the business object Shopping Cart
■ 2nd parameter: 0C_C2_C_GET_PROPERTY for the method to access business object attributes
■ 3rd parameter: 0C_C3_C_CREATEDBY for the attribute that the system is to return
11.9.2.5 Define Business Process Configuration
11.9.2.5.1 Process-Controlled Workflow Settings
In this section, you define the business process configuration for process-controlled workflows. For
example, you model your approval processes and define how the agents responsible for approving
documents are determined.
Prerequisites
You have checked if the Business Rule Framework (BRF) events and BRF expressions needed to evaluate
process schemas and process levels are available in the system, or you have created new events and
expressions as required.
NOTE
For a list of BRF expressions delivered with SAP Supplier Relationship Management (SAP SRM)
and descriptions on how you can use them, see SAP Service Marketplace under http://
service.sap.com/srm-inst SAP SRM Server 7.0 Workflow Guide — SAP SRM 7.0 .
11 Cross-Application Settings
11.9 Business Workflow
102/148 PUBLIC 2013-08-13
Process
To configure process-controlled workflows, you must perform the steps described below. You can find
these steps in Customizing for SAP SRM under SRM Server Cross-Application Basic Settings Business
Workflow Process-Controlled Workflow Business Process Configuration .
Filter Value Definition
Define filter values for the Business Add-Ins (BAdIs) Define Agents (/SAPSRM/BD_WF_AGENTS)
and Define Reviewers (/SAPSRM/BD_WF_REVIEWER_RULE) to determine which user is assigned to a
process level.
Approval Process Definition
In the Customizing activity Define Process Levels, you define process schemas for each business object.
Process schemas contain all possible process levels of an approval process for a specific business object.
You can define more than one process schema per business object. Each business object is assigned a
BRF event. Using the BRF expression assigned to this BRF event, the system determines the correct
process schema.
NOTE
If you use Business Configuration Sets (BC Sets) to set up your approval processes, you do not
have to perform this Customizing activity. For more information, see Business Configuration Sets for
SAP SRM [page 96].
For each process schema, you define the necessary process levels. For each process level, you specify
the following:
■ Level type:
● Approval with completion: Document check by a specialist; document changes allowed.
● Approval: Financial approval; by default, document changes are not allowed.
● Automatic: System decision; automatic approval or automatic rejection, depending on
configuration.
Note that completion levels always run before approval levels.
■ Responsibility resolver name and responsibility parameter that you have defined as filter values
for the BAdI Define Agents. For information on the values you can use, see the BAdI documentation.
■ Evaluation ID: the BRF event to be used to evaluate the process level. Whether or not the process
level is performed depends on the result returned by the BRF expression assigned to this BRF event.
■ Task ID: Assign a workflow dialog task to each process level. Tasks contain the text for the work
item that the responsible agents receive.
The following tasks are available:
Business Object Task ID Task Name
Contract (BUS2000113) 40007980 SRM Contract Approval
11 Cross-Application Settings
11.9 Business Workflow
2013-08-13 PUBLIC 103/148
Business Object Task ID Task Name
40008003 Accept Decision / Adjust Document
40007997 Revise Document
40107926 Review Document
Shopping cart (BUS 2121) 40007952 SRM Shopping Cart Completion
40007953 SRM Shopping Cart Approval (1)
40007954 SRM Shopping Cart Approval (2)
40007994 Accept Decision / Adjust Document
40007936 Revise Document
40007945 Review Document
RFx (BUS2200) 40107917 SRM RFx Completion
40007982 SRM RFx Approval
40107922 Accept Decision / Adjust Document
40007998 Revise Document
40107927 Review Document
Purchase order (BUS2201) 40007973 SRM Purchase Order Completion
40007974 SRM Purchase Order Approval
40007995 Accept Decision / Adjust Document
40007996 Revise Document
40107924 Review Document
Supplier Quote (BUS2202) 40007981 SRM RFx Response/Bid Approval
40007999 Revise Document
40107928 Review Document
40008000 SRM Bid Approval
40107934 Revise Bid
40107935 Review Bid
Confirmation (BUS2203) 40007987 SRM Confirmation Approval
40008004 Revise Document
40107929 Review Document
Invoice (BUS2205) 40008005 SRM Invoice Approval
40008006 Revise Document
40107925 Review Document
Automatic 40007988 Automatic Approval
40007989 Automatic Rejection
■ Decision type:
● Decision type 1: decision for entire document
● Decision type 2: item-based decision for entire document
11 Cross-Application Settings
11.9 Business Workflow
104/148 PUBLIC 2013-08-13
● Decision type 3: overall decision for partial document
● Decision type 4: item-based decision for partial document
For more information, see SAP Help Portal at http://help.sap.com SAP Supplier Relationship
Management Functions Business Workflow Process-Controlled Workflow Decision Types .
The decision types that are available depend on the business object and the process level type. The
following combinations are possible:
Business Object Process Level Type Decision Types
Contract (BUS2000113) Approval with Completion Not applicable
Approval 1, 2
Shopping cart (BUS 2121) Approval with Completion 1, 2
Approval 1, 2, 3, 4
RFx (BUS2200) Approval with Completion 1
Approval 1
Purchase order (BUS2201) Approval with Completion 1, 2
Approval 1, 2
Supplier Quote (BUS2202) Approval with Completion Not applicable
Approval 1
Confirmation (BUS2203) Approval with Completion Not applicable
Approval 1
Invoice (BUS2205) Approval with Completion Not applicable
Approval 1
■ Changeable checkbox: By default, document changes are allowed on completion levels only.
Therefore, this checkbox is selected for completion levels, and deselected for approval levels. You
can, however, override this setting, and define for both completion and approval levels which fields
are changeable and which actions are allowed. You do so in Customizing for Supplier Relationship
Management under SRM Server Cross-Application Basic Settings Extensions and Field Control
(Personalization) . For more information, see SAP Note 1277921.
Note that changing fields during an approval process can result in the process being restarted. You
can use the BAdI Manage Process Restarts (/SAPSRM/BD_WF_PROCESS_RESTART) to override the standard
system behavior for process restarts.
NOTE
The design time version of the process schema serves as a template for the runtime version. At
runtime, additional process levels can be inserted, for example, by using the BAdI Process Level
Configuration (/SAPSRM/BD_WF_PROCESS_CONFIG), or by adding ad hoc agents.
Optionally, you can also define the following settings in this Customizing activity:
■ Defaults for Ad Hoc Process Levels
You can define defaults for ad hoc process levels.
■ Acceptance by Contact Person
11 Cross-Application Settings
11.9 Business Workflow
2013-08-13 PUBLIC 105/148
You can determine whether the contact person receives a work item when the approval process
is finished.
■ Reviewer
You can define rules based on which reviewers are added to the approval process.
Responsibility and Agent Determination
Agent determination is performed using the BAdI Define Agents(/SAPSRM/BD_WF_RESP_RESOLVER). SAP
SRM delivers implementations for typical scenarios. For more information on the strategies on which
these implementations are based, see SAP Service Marketplace at http://service.sap.com/srm-
inst SAP Business Suite Applications SAP SRM SAP SRM 7.0 Workflow in SAP Supplier Relationship
Management 7.0 .
To determine the agents responsible for completing or approving purchasing documents, the BAdI is
called three times and completes the following steps:
■ Each item is assigned an area of responsibility. Areas of responsibility can be, for example,
departments, product categories, or cost centers. All items with the same area of responsibility
form a decision set. For each decision set a new subworkflow is started.
■ The responsible agents are determined for each area of responsibility. For example, if the area of
responsibility is a department, the system assigns all employees belonging to this department as
responsible agents. For a cost center, the cost center manager is the responsible agent. Each
responsible agent receives a work item.
■ If the system cannot determine a responsible agent, a fallback agent is determined.
For more information, see the BAdI documentation.
11.9.2.5.2 Configuring Parallel Approval with Overlapping Responsibility
You can configure the system to allow for parallel approval with overlapping responsibility. If you do
so, several agents responsible for approving one specific shopping cart item can receive their work items
in parallel instead of one after the other in a fixed sequence. For more information about parallel
approval with overlapping responsibility, see SAP Help Portal at http://help.sap.com SAP Supplier
Relationship Management Functions Business Workflow Process-Controlled Workflow Agent Determination .
To use this procedure, you must activate the business function SRM, Approval Process
(SRM_APF_IMPR_1).
Procedure
You configure parallel approval in Customizing for SAP Supplier Relationship Management under
SRM Server Cross-Application Basic Settings Business Workflow Process-Controlled Workflow Business Process
Configuration Define Process Levels . Proceed as follows:
11 Cross-Application Settings
11.9 Business Workflow
106/148 PUBLIC 2013-08-13
1. Create a process schema for determining all agents who are responsible for approving the item.
You must create one process level for each responsible agent or group of responsible agents, as
usual. The sequence in which you include the process levels is irrelevant.
2. Create a process schema for parallel approval. The process level on which you want to implement
parallel approval must contain the following entries:
■ Responsibility Resolver Name: RR_PARALLEL_APPROVAL
■ Parameter: Name of the process schema you have created in step 1
■ Decision Type: 4 — Item-Based Decision for Partial Document
Result
Using the Responsibility Resolver Name (RR_PARALLEL_APPROVAL) and the object type (BUS2121) as
filter values, the Business Add-In (BAdI) Define Agents (/SAPSRM/BD_WF_RESP_RESOLVER) can now
call the BAdI implementation for parallel approval, /SAPSRM/BD_WF_SC_RR_PA. This
implementation enables the parallel creation of work items for all responsible agents that you defined
in the first process schema above. Therefore, by including this process schema into the superordinate
process schema, the work items are sent out in parallel instead of in sequence. Note, however, that the
corresponding document is locked for other users while a work item is being processed.
Example
You create a process schema with three process levels. On the first process level, the system determines
the office assistant as the responsible agent, on the second level the operational purchaser, and on the
third level the line manager of the requester. If you now include this process schema into a superordinate
one with the values listed above under step 2, the system creates the work items for all three responsible
agents in parallel and sends them out at the same time. The agents can now process the work items
independently of one another.
11.9.2.5.3 More Information About Defining Business Process Configuration
Perform the following activities in Customizing for SAP Supplier Relationship Management (SAP SRM):
■ SRM Server Activate Business Functions
■ SRM Server Cross-Application Basic Settings Business Workflow Activate Asynchronous Processing of
Workflow
■ SRM Server Cross-Application Basic Settings Business Workflow Activate Parallel Approval with Overlapping
Responsibility
Perform the following activities in Customizing for SAP SRM under SRM Server Cross-Application Basic
Settings Business Workflow Process-Controlled Workflow Business Process Configuration :
■ Define Recipient of Notifications
■ Define Deadlines for Events
11 Cross-Application Settings
11.9 Business Workflow
2013-08-13 PUBLIC 107/148
■ Activate Sample BC Sets for Process Level Definition
The following Business Add-Ins are available in Customizing for SAP SRM under SRM Server Business
Add-Ins Business Workflow Process-Controlled Workflow :
■ Define Deadlines for Events
■ Determine Shopping Cart Value for Purchasing Budget Workflow
■ Adjust Search Help for Ad Hoc Agent
■ Adjust Search Help for Reviewers
■ Customer Enhancement of Offline Approval
■ POR Start Conditions and Agent Determination
11.9.3 Application-Controlled Workflow
11.9.3.1 Setting Up Business Workflow for Application-Controlled Workflows
In this procedure, you can perform standard Customizing for SAP Business Workflow. For more
information, see the following Customizing activities:
■ SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Business Workflow
Application-Controlled Workflow Technical Configuration Customize SAP Business Workflow
Automatically
■ SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Business Workflow
Application-Controlled Workflow Technical Configuration Activate Standard Tasks
NOTE
If the workflow is not working 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 [page 55].
Before you can assign processors to standard tasks, you must have created the required users or
regenerated the roles, as appropriate. See Regenerating Role Profiles [page 76].
Procedure
Activate the specific workflows by activating the event linkage
Activate the event linkage of those workflows that you want to use in your scenario. Assign a processor
to the tasks in the table below by performing the Customizing activity for SAP Supplier Relationship
Management under SRM Server Cross-Application Basic Settings Business Workflow Application-Controlled
Workflow Technical Configuration Perform Task-Specific Customizing .
1. Expand the SRM folder.
2. Expand the SRM-EBP folder.
11 Cross-Application Settings
11.9 Business Workflow
108/148 PUBLIC 2013-08-13
3. Go to folder SRM-EBP-WFL.
4. Click the link Activate event linking for this folder.
Workflows with delivered start conditions:
Event linkages and delivered start conditions per workflow listed according to business objects (default
settings):
Business Object Triggering Events Workflows Belonging to Business Object
Event Linkage(by Default)Activated
Start Conditions(by Default)Activated
BUS2121(Shopping Cart)
SAVED WS10000060(auto approval)
No No
WS10000129(one-step approval)
No No
WS10000031(two-step approval)
No No
WS10000276(spending limit approval)
No No
WS14000044(completion by purchaser)
No No
BUS2201(Purchase Order)
SAVED/ CHANGEVERSIONSAVED
WS14000075(auto approval)
Yes No
WS14000089(one-step approval)
No No
BUS2203(Confirmation)
SAVED WS10400002(one-step approval)
Yes Yes
WS10400009(two-step approval)
Yes Yes
WS10400010(auto approval)
Yes Yes
WS10400020(administrator approval)
Yes Yes
BUS2205(Invoice)
SAVED WS10400016(auto approval)
Yes Yes
WS10400017(one-step approval)
Yes Yes
WS10400018(two-step approval)
Yes Yes
WS10400021(administrator approval)
Yes Yes
BUS2000113(Contract)
SAVED/ CHANGEVERSIONSAVED
WS14000086(auto approval)
Yes No
WS14000088(one-step approval)
No No
11 Cross-Application Settings
11.9 Business Workflow
2013-08-13 PUBLIC 109/148
BUS2200(RFx)
SAVED/ CHANGEVERSIONSAVED
WS14500026(auto approval)
Yes No
WS14500027(one-step approval)
No No
BUS2202(Supplier RFx Response)
TOBEACCEPTED WS79000010(auto approval)
Yes No
WS79000002(one-step approval)
No No
NOTE
■ Start condition activation is required if several workflows are assigned to the same business
object and triggering event.
■ 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
or message if no approval has been granted when the deadline passes.) Activate this workflow if you
want to use SAP SRM Alert Management.
NOTE
If an event linkage is activated and the corresponding start condition is not activated, the workflow
is started every time the event occurs (the start condition rules are not followed).
Workflows without delivered start conditions:
You can use the following workflows in addition to the ones above:
Business Object (BO)
Triggering Events Workflow Template Event Linkages(by Default)Activated
Start ConditionsRequired
BUS2121(Shopping Cart)
SAVED WS14000109(n-step spending limit approval)
No Yes (see note)
WS14500015(line-item approval)
No Yes (see note)
WS14000045(delete SC item after application error)
No No
WS10000202(transfer PM requisition)
No No
WS10000215 No No
11 Cross-Application Settings
11.9 Business Workflow
110/148 PUBLIC 2013-08-13
(resubmit SC item by administrator)
BUS2201(Purchase Order)
SAVED/ CHANGEVERSIONSAVED
WS14000145(n-step approval)
No Yes (see note)
BUS2205(Invoice)
ERRORINVOICETOBEPROCESSED
WS14500020(error correction)
Yes No
BUS2000113(Contract)
ALERTBUSINESSWAREHOUSE
WS10400022(contract alert)
No No
SAVED/ CHANGEVERSIONSAVED
WS14000148(n-step approval)
No Yes (see note)
BUS2202(Supplier RFx Response)
TOBEACCEPTED WS14500044(n-step approval)
No Yes (see note)
BUS2200(RFx)
EXTERNALAUCTIONSTARTED
WS14000091(alert workflow)
No No
SAVED/ CHANGEVERSIONSAVED
WS14500028(n-step approval)
No Yes (see note)
BUS1006200(Business Partner)
COMPLETED WS14000043(auto approval)
Yes No
WS14000030(one-step approval)
Yes No
WS14500021(BP locked)
Yes No
BBP_PCARD(Procurement Card)
APPROVECHARGES1 WS10000093(one-step approval)
No No
APPROVECHARGES2 WS10000100(two-step approval)
No No
BUS2203(Confirmation)
RETURN WS10001048(notify supplier of goods return)
No No
NOTE
Create and activate start conditions if several workflows are assigned to the same business object
and triggering event.
Define start conditions for some of the workflows before you can execute them
The start conditions are supplied by SAP by default in such a way that the workflows can be started
immediately. However, you can change the start conditions as required. For more information, see
Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic
Settings Business Workflow Application-Controlled Workflow Business Process Configuration Define Conditions
for Starting Workflows .
11 Cross-Application Settings
11.9 Business Workflow
2013-08-13 PUBLIC 111/148
NOTE
The delivered or changed start conditions must be activated before the workflow runs.
NOTE
If multiple approval workflow types are activated for a specific procurement scenario (using event
linkage), you must prevent these workflows from starting together. 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,
note that the start condition editors use Boolean logic rules. This means that a status that is defined
in a start condition appears in its inverse form in the other start conditions. This ensures that the
other condition always shows False when the first one shows True.
Approval workflows for purchase orders and change versions of purchase orders
Workflows WS14000075 (auto approval) and WS14000089 (one-step approval) react to the same
event: Save the change. If the start conditions are not activated, both workflows start together as soon
as the change version is saved.
Therefore, the start condition WorkflowStart WS14000075 defines clearly the prerequisites for starting
Workflow WS14000075, and the start condition WorkflowStart WS14000089 defines exactly the reverse
circumstances under which only Workflow WS14000089 starts.
This ensures that one workflow always starts, but both workflows never start together.
Assign processors to some standard tasks if you want to use the associated workflows
If you want a certain group of persons to be able to approve your work items, you must specify all the
possible processors for the task in question. For example, tasks TS10008069 and TS10008127 refer to
standard two-level approval, and task TS10008126 refers to single-level approval. These tasks are usually
assigned to the manager role. If required, however, you can specify a different processor.
Assign a processor to the tasks in the table below with the Customizing activity for SAP Supplier
Relationship Management under SRM Server Cross-Application Basic Settings Business Workflow
Application-Controlled Workflow Technical Configuration Perform Task-Specific Customizing .
1. Expand the SRM folder.
2. Expand the SRM-EBP folder.
3. Go to folder SRM-EBP-WFL.
4. Click the link Assign Agents for this folder.
NOTE
For a complete list of mandatory workflows, see SAP Help Portal at http://help.sap.com
SAP Supplier Relationship Management Functions Business Workflow Application-Controlled Workflow
Approval Workflows for Documents and Objects Technical Information on Standard Workflows .
Assign a processor to the following tasks if you want to use the associated workflows
Task(Description)
Used/Usable in Workflow Processor
11 Cross-Application Settings
11.9 Business Workflow
112/148 PUBLIC 2013-08-13
(Type of Task Agent Assignment)
TS10007947(approve charges of P-Card)
WS10000093 General task
TS10008061(ask whether requester accepts rejection of SC)
WS10000265 General task
TS10008069(1st approval task in two-step approval of SC)
WS10000031 Manager role or general task
TS10008126(approval task in one-step approval of SC)
WS10000129WS10000276
Manager role or general task
TS10008127(2nd approval task in two-step approval of SC)
WS10000031 Manager role or general task
TS10008212(check SC by reviewer)
WS10000265 Manager role or general task
TS10008214(approval task to insert in approval of SC)
WS10000271 Manager role or general task
TS10107914(present changes in SC to requestor)
WS10000031WS10000060
General task
TS10407914(approval task in one-step approval of GR)
WS10400002 Manager role or general task
TS10407915(1st approval task in two-step approval of GR)
WS10400009 Manager role or general task
TS10407916(check GR by reviewer)
WS10400011 Manager role or general task
TS10407917(approval task to insert in approval of GR)
WS10400008 Manager role or general task
TS10407918(approval task to insert in approval of INV)
WS10400014 Manager role or general task
TS10407919(check INV by reviewer)
WS10400015 Manager role or general task
TS10407920(approval task in one-step approval of INV)
WS10400017 Manager role or general task
TS10407921(1st approval task in two-step approval of INV)
WS10400018 Manager role or general task
TS10407922(2nd approval task in two-step approval of GR)
WS10400009 Manager role or general task
TS10407923(2nd approval task in two-step approval of INV)
WS10400018 Manager role or general task
TS10407924(administrator approval task for GR)
WS10400020 Administrator
11 Cross-Application Settings
11.9 Business Workflow
2013-08-13 PUBLIC 113/148
TS10407925(administrator approval task for INV)
WS10400021 Administrator
TS10407926(check CTR in alert workflow)
WS10400022 General task
TS10407972(change rejected SC)
WS10000031WS10000060
General task
TS14007938(present changes to creator of SC)
WS10000060WS10000129WS10000031WS10000276WS14000044WS14000109WS14500015
General task
TS14007947(completion task of SC)
WS14000044 General task
TS14007969(approval task in one-step approval of CTR)
WS14000088 Manager role or general task
TS14007970(approval task in one-step approval of PO)
WS14000089 Manager role or general task
TS14008026(approval task to insert in approval of PO)
WS14000002 Manager role or general task
TS14008027(check PO by reviewer)
WS14000154 Manager role or general task
TS14008028(send PO back to purchaser)
WS14000145 General task
TS14507918(Send contract back to creator)
WS14000148 General task
TS14507919(check contract by reviewer)
WS14500008 Manager role or general task
TS14507920(approval task to insert in approval of CTR)
WS14500010 Manager role or general task
TS14507922(approval task in one-step approval of RFx)
WS14500027 Manager role or general task
TS14507924(approval task to insert in approval of RFx)
WS14500022 Manager role or general task
TS14507925(check RFx by reviewer)
WS14500023 Manager role or general task
TS14507928(Send RFx back to creator)
WS14500028 General task
TS14507930(approval task to insert in approval of RFx response)
WS14500040 Manager role or general task
TS14507931(check contract by reviewer)
WS14500041 Manager role or general task
TS14507935 WS14500044 Manager role or general task
11 Cross-Application Settings
11.9 Business Workflow
114/148 PUBLIC 2013-08-13
(approval task in n-level approval of RFx response)
TS14507937(send RFx response back to creator)
WS14500044 General task
TS14508056(correct erroneous invoice)
WS14500020 Administrator
TS79007914(approval task in one-step approval of RFx response)
WS79000002 Manager role
NOTE
SC: Shopping Cart, PO: Purchase Order, GR: Goods Receipt (Confirmation), CTR: Contract, INV: Invoice
Authorization for changing or inserting the approver or reviewer
You also 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 workflow templates in the SAP SRM system. Note that you only have to
change the settings for the workflows that you require.
■ WS10000129 - One-step approval of shopping cart
■ WS10000031 - Two-step approval of shopping cart
■ WS10000060 - Workflow auto approval of shopping cart
■ WS10400002 - One-step approval of goods receipt
■ WS10400009 - Two-step approval of goods receipt
■ WS10400010 - Workflow auto approval of goods receipt
■ WS10400016 - Invoice auto approval
■ WS10400017 - One-step approval of invoice
■ WS10400018 - Two-step approval of invoice
■ WS10400020 - Approval of goods receipt by administrator
■ WS10400021 - Approval of invoice by administrator
■ WS14000075 - Auto approval of purchase order
■ WS14000086 - Auto approval of contract
■ WS14000088 - One-step approval of contract
■ WS14000089 - One-step approval of purchase order
■ WS14000109 - N-step approval of shopping cart over value limit
■ WS14000133 - N-step approval of shopping cart
■ WS14000145 - N-step approval of purchase order
■ WS14000145 - N-step approval of contract
■ WS14000154 - Reviewer workflow for purchase order
■ WS14500026 - Auto approval of RFx
11 Cross-Application Settings
11.9 Business Workflow
2013-08-13 PUBLIC 115/148
■ WS14500027 - One-step approval of RFx
■ WS14500028 - N-step approval of RFx
■ WS14500044 - N-step approval of RFx response
■ WS79000002 - One-step approval of RFx response
■ WS79000010 - Auto approval of RFx response
Approvers or reviewers who can be inserted
With these templates, you can specify who may be inserted as an approver or reviewer in the above
workflows:
■ WS10000271 - Approval fragment to insert in approval of shopping cart
■ WS10400008 - Approval fragment to insert in approval of goods receipt
■ WS10400014 - Approval fragment to insert in approval of invoice
■ WS14000002 - Approval fragment to insert in approval of purchase order
■ WS14500010 - Approval fragment to insert in approval of contract
■ WS14500022 - Approval fragment to insert in approval of RFx
■ WS14500040 - Approval fragment to insert in approval of RFx response
RECOMMENDATION
We recommend that you restrict the processors (that is, the approvers or reviewers that can
be inserted), and specify the required workflow tasks as general tasks instead (see table above).
For more information, see the Customizing activities for SAP Supplier Relationship Management under
SRM Server Cross-Application Basic Settings Business Workflow Application-Controlled Workflow Technical
Configuration Perform Task-Specific Customizing .
NOTE
For a complete list of mandatory workflows, see SAP Help Portal at http://help.sap.com SAP
Supplier Relationship Management Functions Business Workflow Application-Controlled Workflow Approval
Workflows for Documents and Objects Technical Information on Standard Workflows .
Assign authorization for changing shopping carts during the approval process
This is controlled by means of a role-based attribute BBP_WFL_SECURITY, and you can set it in the
transaction PFCG on the Personalization tab page. There are four possible levels of authorization:
■ High: The workflow is never restarted.
■ Medium: The workflow is restarted based on start conditions.
■ Low: The workflow is always started.
■ No: No changes to the shopping cart are allowed during approval.
11.9.3.2 Additional Information: Maintaining Guided Procedures Gateway
The Customizing activity SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings
Business Workflow Application-Controlled Workflow Technical Configuration Customize SAP Business Workflow
11 Cross-Application Settings
11.9 Business Workflow
116/148 PUBLIC 2013-08-13
Automatically takes you to the Automatic Workflow Customizing screen. The activity Maintain Guided Procedures
Gateway ( Guided Procedures Maintain Guided Procedures Gateway ) is not required for SAP SRM 7.0. It is
therefore normal if a red 'x' is displayed next to this activity.
11.9.3.3 More Information About Application-Controlled Workflows
Perform the following activities in Customizing for SAP SRM under SRM Server Cross-Application Basic
Settings Business Workflow Application-Controlled Workflow Business Process Configuration :
■ Define Conditions for Starting Workflows
■ Define Stochastic Check of Documents
■ Define Recipient of Notifications
The following Business Add-Ins are available in Customizing for SAP SRM under SRM Server Business
Add-Ins Business Workflow Application-Controlled Workflow :
■ Authorization to Change During Approval
■ Determine Approver (Administrator)
■ Determination of Approver for n-Step Dynamic Approval Workflow
■ Control Workflow for Stochastic Document Check
■ Allow Changes to Approvers
■ Select Users when Creating/Changing Approvers
■ Customer Enhancement of Offline Approval
The following SAP Note applies: SAP Note 322526
11.9.4 Universal Worklist
Perform the following activity in Customizing for SAP SRM: SRM Server Cross-Application Basic Settings
Business Workflow Universal Worklist Object Visualization .
11.10 Alert Framework
11.10.1 Configuring SRM Alert Management
You can use the procedures described below to customize the alerts for SAP Supplier Relationship
Management (SAP SRM) Alert Management and the events that trigger them.
Prerequisites
Before the system can trigger alerts and notifications, the report on deadline monitoring must be
scheduled as a background job. For more information, see Customizing for SAP SRM under SRM
Server Cross-Application Basic Settings Business Workflow Process-Controlled Workflows Technical Configuration
11 Cross-Application Settings
11.10 Alert Framework
2013-08-13 PUBLIC 117/148
Customize SAP Business Workflow Automatically Maintain Runtime Environment Schedule Background Job for Missed
Deadlines .
Procedure
■ Maintaining event texts
To maintain the texts for individual events for an object type, see Customizing for SAP SRM under
SRM Server Cross-Application Basic Settings Event and Event Schema for Alert Management Define
Events .
■ Maintaining event schema texts
To enter deadlines, event categories, and alert categories for the individual events for an event
schema and object type, see Customizing for SAP SRM under SRM Server Cross-Application Basic
Settings Event and Event Schema for Alert Management Define Event Schema .
■ Activating event schemas
To assign an event schema to a transaction type of an object type and to activate this schema (thus
activating all associated events), see Customizing for SAP SRM under SRM Server Cross-Application
Basic Settings Define Transaction Types . When an event schema is assigned to a transaction type, the
alert function for this is also activated. To define the event schema for the object type Employee
(BUS1006003), see Customizing for SAP SRM under SRM Server Cross-Application Basic Settings
Organizational Management Event Control for Organizational Management .
■ Adjusting alert categories
We do not recommend changing the alert categories provided with the SAP SRM system. We
recommend that you first make copies of the alert categories and then modify these. By changing
alert categories, you can add recipient types and define subscription authorizations. You can also
change the title, the short text, and the long text. Note that the short text always matches the
event text. To adjust alert categories, see Customizing for SAP Web Application Server under Base
Basis Services Generic Business Tools Alert Management Define Alert Categories .
■ Defining your own events and overriding predefined alerts
You can use the Business Add-In (BAdI) BBP_ALERTING to configure events, alerts, and messages
to your own requirements. To do this, see Customizing for SAP SRM under SRM Server Business
Add-Ins Alerts/Messages, and Events in SRM Alert Management .
11.11 Settings for Tax Calculation
11.11.1 Making Settings for Tax Calculation
You can calculate sales tax in the SAP Supplier Relationship Management Management (SAP SRM)
and supplier self-services (SUS) systems. The system calculates tax when you create a shopping cart, a
purchase order, or enter an invoice or a credit memo.
You can use the tax calculation functions in the following applications:
11 Cross-Application Settings
11.11 Settings for Tax Calculation
118/148 PUBLIC 2013-08-13
■ Shop
The system determines a tax indicator. You can change the default tax indicator. You can display
the tax amounts for each item individually and as a total amount. You can define whether the
system takes tax amount into account in the approval process.
■ Create Purchase Order
You can change the default tax indicator. The system calculates the tax on the basis of the current
data. You can display the tax amounts for each item individually and as a total amount.
■ Enter Invoice/ Credit Memo
You can change the default tax indicator. Depending on the legal requirements, the system
calculates the taxes either for each item individually or as a total amount. In addition, you can
enter the taxes manually for each tax code or as a total tax amount.
■ Evaluate Receipt Settlement (ERS)
The system recalculates the tax. You define the tax code in the purchase order.
You can use the following systems for tax calculation:
■ SAP back-end system (tax calculation takes place in the financial accounting system)
If you already have an SAP back-end financial accounting system, we recommend that you use the
existing tax calculation provided by the back-end system. You do not need to make any additional
Customizing settings for tax calculation.
■ External tax system (Vertex® or Taxware®)
If you do not have an SAP financial accounting system, you can use an external tax system, such
as Vertex® or Taxware® (suitable for large customers only). This type of tax calculation is only
valid for the USA and Canada.
If an external tax system is connected to the SAP back-end system, it is called up automatically
from the back-end system.
■ Customer-specific implementation (tax calculation in SAP SRM)
If you do not have an SAP back-end financial accounting system, you can use a customer-specific
implementation for simple tax calculation (for example, if you only have two tax codes).
■ SAP Transaction Tax Engine (TTE)
If you use supplier self-services (SUS), or need to calculate taxes for several countries, you must
use SAP Transaction Tax Engine, which is part of Internet Pricing and Configurator (IPC).
NOTE
If more than one country is involved, and each country has its own tax code, it is not possible
to directly connect SAP SRM to an external tax system.
For example, if both US tax and European tax are needed, you must use TTE or the back-end
system for tax calculation.
Specify the systems in Customizing for SAP Supplier Relationship Management under SRM
Server Cross-Application Basic Settings Tax Calculation Determine System for Tax Calculation .
11 Cross-Application Settings
11.11 Settings for Tax Calculation
2013-08-13 PUBLIC 119/148
Prerequisites
Settings for Tax Calculation
Setting Customizing path
Define the system for tax calculation. SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Tax Calculation Determine System for Tax Calculation
Define the allowed invoice verification tolerances for the variances between calculated tax amounts and tax amounts entered manually (optional).
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Set Tolerance Checks
Define whether taxes for the total freight costs (that is, for all company codes) are to be calculated with a separate tax code (optional).
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Tax Calculation Define Tax Calculation for Freight Costs
Define whether taxes for freight costs for specific company codes are to be calculated with a separate tax code (optional).
SAP Supplier Relationship Management SRM Server Business Add-Ins Tax Calculation Calculate Tax for Freight Costs
Procedure
Tax Calculation in the SAP Back-End Financial Accounting System
If you choose to calculate tax in the SAP back-end system, tax calculation takes place in the respective
financial accounting system (depending on the attribute of the user System Alias for Financial
Accounting Systems in the organization model). The SAP back-end system has to be defined as a
financial accounting system.
The system determines the tax code from the entries in the tables and fields: for example, from the
product category, country of goods recipient, or the domestic/international indicator.
If the tax indicators in SAP SRM do not match the tax indicator in the financial accounting system,
you can map them to the tax indicators of the financial accounting system.
The following table gives an overview of all settings you can make:
Setting Customizing path
You can maintain tax codes.
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Tax Calculation Enter Tax Code
You can map tax codes that have different names in the FI system and in SAP SRM to each other.
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Tax Calculation Assign Enterprise Buyer Tax Code to FI System
You can use individual tax code determination.
SAP Supplier Relationship Management SRM Server Business Add-Ins Tax CalculationDetermine Tax Code
You can change or supplement the data used to calculate tax
SAP Supplier Relationship Management SRM Server Business Add-Ins Tax CalculationChange Tax Data
11 Cross-Application Settings
11.11 Settings for Tax Calculation
120/148 PUBLIC 2013-08-13
depending on the system selected for tax calculation.
You can specify a tax code for country and product category (optional).
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Tax Calculation Determine Tax Code for Country/ Product Category
Tax Calculation with Vertex® or Taxware®
NOTE
This type of tax calculation is only valid for the USA and Canada.
Define the destination of the external system, for example EXT_DEST, in Customizing for SAP Supplier
Relationship Management under SRM Server Technical Basic Settings Define RFC Destinations .
Define the back-end system in Customizing for SAP Supplier Relationship Management under SRM
Server Technical Basic Settings Define Backend Systems .
Required entries:
■ Logical system, for example VERTEX
■ Name, for example VERTEX
■ Destination, for example EXT_DEST
■ System type: Tax external system
Tax Jurisdiction Code
NOTE
This type of tax calculation is only valid for the USA and Canada.
The tax jurisdiction code is required for all tax calculation procedures in the USA and Canada. You
enter this code in the delivery address master record in SAP SRM (log on as an administrator and choose
Edit External Addresses).
This information must then be transported to the back-end system for tax calculation (either an
external system or an SAP system). You enable this by implementing the BAdI BBP_TAX_MAP_BADI, see
SAP Note 436760.
Customer-Specific Implementation
You can carry out customer-specific tax calculation by replacing the function module
NOR3_TAX_CALCULATION with your own function module.
Go to table BBP_FUNCTION_MAP, in the Object field enter TAX. Find Method = Calculate_NOR3, Type =
LOCAL, and Function NOR3_TAX_CALCULATION. You can then replace this entry with your own function
module.
NOTE
The interfaces of the new customer function module must be the same as the default function
module (that is, import/export parameters, tables and exceptions, and so on).
11 Cross-Application Settings
11.11 Settings for Tax Calculation
2013-08-13 PUBLIC 121/148
SAP Transaction Tax Engine (TTE)
1. Configure SAP Transaction Tax Engine.
For more information, see the SAP Service Marketplace at service.sap.com/srm SAP SRM in Detail -
Previous Releases SRM 3.0 and 2.0 Scenarios in Detail Supplier Enablement Implementation Information
Config. Guide for TTE . If you have access to SAP Solution Manager, you can also use the
configuration information there.
NOTE
Only continue once you have successfully configured SAP Transaction Tax Engine.
2. Define the destination of the external system, for example EXT_DEST, in Customizing for SAP
Supplier Relationship Management under SRM Server Technical Basic Settings Define RFC
Destinations .
3. Define the back-end system in Customizing for SAP Supplier Relationship Management under
SRM Server Technical Basic Settings Define Backend Systems .
Required entries:
■ Logical system, for example VERTEX
■ Name, for example VERTEX
■ Destination, for example EXT_DEST
■ System type: Tax external system
4. Edit the business partners.
1. In the SAP Easy Access menu, choose Master Data Business Partner Process Business Partner .
2. Enter the business partner (BusPartner), for example, the company that the goods are to be
delivered to.
NOTE
You must specify a business partner because the business partner is used to determine
the location. Verify that the Company attribute for the business partner in the
organizational model has been maintained.
3. On the Number for Tax and Reporting tab page, make the following entries:
■ Tax category, for example DE0 for the VAT registration number in Germany
■ Name
■ Tax number; this is checked on the basis of the tax category selected
4. On the Tax Classifications tab page, maintain the following data for countries that you work
with:
■ Country, for example DE
■ Region
■ Tax type, for example VAT
■ Tax group, for example FULL
5. Edit all products that are to be checked.
1. In the SAP Easy Access menu choose Master Data Products Process Products .
11 Cross-Application Settings
11.11 Settings for Tax Calculation
122/148 PUBLIC 2013-08-13
2. Enter the ID/short text for a product and click Start.
3. Choose the General tab page. Make the following entries:
■ Country, for example DE
■ Tax type, for example VAT
■ Tax group, for example HALF
More Information
SAP Note 741822 (TAX. Problems w/ Backend tax indicator and jurisdiction code)
11.11.2 Tax Calculation in the SAP ERP Financial Accounting System
Tax calculation takes place in the respective SAP ERP financial accounting system, depending on the
posting of the document. As prerequisite, you must specify this logical system in the user attribute ACS
(System Alias for Accounting System) in transaction PPOMA_BBP.
The system determines the tax code from the entries in the tables and fields, for example, from the
product category, country of goods recipient, or the domestic/international indicator.
If the tax indicators in SAP SRM do not match the tax indicator in the financial accounting system,
you can map them to the tax indicators of the financial accounting system.
11.11.3 More Information About Settings for Tax Calculation
Activate Withholding Tax
Perform the following activity in Customizing for SAP Supplier Relationship Management under SRM Server
Cross-Application Basic Settings Tax Calculation Activate Withholding Tax .
11.12 Settings for Account Assignment
11.12.1 Making Settings for Account Assignment
You must make the relevant account assignment settings.
Prerequisites
You have defined the account assignment categories in Customizing for SAP Supplier Relationship
Management under SRM Server Cross-Application Basic Settings Account Assignment Define Account
Assignment Categories. .
Procedure
1. Select account assignment categories:
11 Cross-Application Settings
11.12 Settings for Account Assignment
2013-08-13 PUBLIC 123/148
In Customizing for SAP Supplier Relationship Management, select the required account assignment
categories from a preconfigured list by choosing SRM Server Cross-Application Basic Settings
Account Assignment Define Account Assignment Categories.
2. Map account assignment categories (simple mapping):
In Customizing for SAP Supplier Relationship Management, map back-end account assignment categories
to the SAP SRM categories by choosing SRM Server Cross-Application Basic Settings Account Assignment
Define Account Assignment Categories .
3. Change account assignment categories (complex mapping during creation or import):
You can change account assignment categories using Business Add-Ins. You do this in Customizing
for SAP Supplier Relationship Management under SRM Server Business Add-Ins Account Assignment
Change Account Assignment Category when Creating Backend Documents or Change Account Assignment Category
when Importing Backend Documents.
Use these BAdIs if you need to:
■ Map an SAP SRM account assignment category to multiple back-end account assignment
categories or vice versa
■ Override the simple mapping in special cases, such as third party orders
CAUTION
If you want to process third party orders, you must use the Customizing activity Change
Account Assignment Category when Creating Backend Documents (BAdI BBP_ACCCAT_MAP_EXP)
to change the account assignment category for third party orders to 1.
NOTE
You can recognize third party orders by the subtype ET at item level.
4. Define rules for G/L account determination:
You can specify that the criteria used to determine the G/L account are to be based on the product
category and account assignment category. See Customizing for SAP Supplier Relationship
Management under SRM Server Cross-Application Basic Settings Account Assignment Define G/L
Account for Product Category and Account Assignment Category .
Alternatively, you can use Business Add-Ins to define your own criteria for determining the G/L
account. See Customizing for SAP Supplier Relationship Management under SRM Server Business Add-
Ins Account Assignment Determine G/L Account .
5. Maintain local accounting data:
In Customizing for SAP Supplier Relationship Management, maintain local accounting data, including
entering account assignment information and defining an account assignment object for local
validation, by choosing SRM Server Cross-Application Basic Settings Account Assignment Maintain
Local Accounting Data .
11 Cross-Application Settings
11.12 Settings for Account Assignment
124/148 PUBLIC 2013-08-13
11.12.2 More Information About Settings for Account Assignment
The following SAP Note is relevant: 1040976 — F4 Backend Search Help Does Not Return Results
Process Local Accounting Data
The following SAP Note is relevant: 1232945 — BP for SRM 7.0: Installing the Business Packages
11.13 Payment Conditions
11.13.1 Creating Payment Conditions
In this step, you create the payment conditions for SAP SRM. If you want to select payment conditions
using input help when processing business documents, this step is mandatory. The input help comes
from view BBPV_PTERM_LOCAL for local terms of payment, and tables BBP_PAYTERM and
BBP_PAYTERM_TEXT for back-end payment terms.
The input help will display only those terms of payment that have a description in table
BBP_PAYTERM_TEXT (back-end table T052U).
For more information, see Customizing for SAP Supplier Relationship Management under SRM Server
Cross-Application Basic Settings Create Payment Conditions .
Procedure
You can create payment conditions in one of the following ways:
■ Create local terms of payment manually in SAP SRM.
Refer to the above-mentioned Customizing activity.
Alternatively, you can initially load the local terms of payment from one of your back-end systems
using report BBP_UPLOAD_PAYMENT_TERMS. Since the local terms use the days/percentage values
only, the result will be just a subset of all back-end terms.
■ Load terms of payment from all your back-end systems.
NOTE
● Do not use report BBPGETVC. Instead, run report BBP_UPLOAD_PAYMENT_TERMS. When you
use this report, not only the day/percentage values, but the complete range (as in tables
T052/ T052U) is uploaded from your back-end systems, and is stored in tables
BBP_PAYTERM and BBP_PAYTERM_TEXT respectively.
● We recommend that you change descriptions in the back-end system. There is no update
mechanism. Subsequent calls of the report will reload everything and overwrite any texts
manually entered in BBP_PAYTERM_TEXT.
11 Cross-Application Settings
11.13 Payment Conditions
2013-08-13 PUBLIC 125/148
11.14 Create Incoterms
Go to Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic
Settings Create Incoterms .
11.15 Pricing
11.15.1 Set Up Simplified Pricing for Classic Scenario
11.15.1.1 Setting Up Configuration Engine
Procedure
Follow the instructions in SAP Note 854170 to activate the Virtual Machine Container (VMC), then
run transaction Maintain Services (SICF) to activate the related service.
NOTE
In certain cases, you can use the simplified pricing function as an alternative to the Configuration
Engine. For more information, see Customizing for SAP Supplier Relationship Management under
SRM Server Business Add-Ins Pricing Switch On Simplified Pricing (Classic Scenario) .
11.15.2 More Information About Pricing
The following SAP Notes apply:
■ 844817 — Technical information for the VMC based AP 7.00 engines
■ 1540489 — Customized condition type not considered in pricing
Set General Configuration Parameters
Perform the following activity in Customizing for SAP SRM: SAP Web Application Server General settings
Time Zones Maintain System Settings
Process Condition Types
Perform the following activity in Customizing for SAP SRM: SRM Server Cross-Application Basic Settings
Pricing Process Condition Types
Edit Calculation Schema
Perform the following activity in Customizing for SAP SRM: SRM Server Cross-Application Basic Settings
Pricing Process Calculation Schema
Process Condition Group
Perform the following activity in Customizing for SAP SRM: SRM Server Cross-Application Basic Settings
Pricing Process Condition Groups
11 Cross-Application Settings
11.14 Create Incoterms
126/148 PUBLIC 2013-08-13
Check Technical and Customizing Settings for Conditions
Perform the following activity in Customizing for SAP SRM: SRM Server Cross-Application Basic Settings
Pricing Check Technical and Customizing Settings for Conditions
11.16 Define Objects in the Back-End System
The purpose of this activity is to define objects in the back-end system.
Procedure
1. Access the activity using the following navigation options:
Customizing Path SAP Supplier Relationship Management SRM Server Cross-Application Basic SettingsDefine Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)
Transaction Code SPRO
2. Choose New Entries.
3. Make the following entries (Example):
Purchasing Grp. Category ID Source System Int. Proc. External Procurement
Purchasing groups you have defined (Example 50000056)
* <system name>CLNT<client number>
Choose Option 'Reservn generated if stock available, otherwise ext. proc.'
Choose option ‘Purchase order if item data complete else purch. req.’
■ The system name is a three-letter word. This is the second part of the underscore-separated
server name.
■ The client number is the 3-digit SAP client number.
4. Choose Save (Ctrl+S).
11.17 Attachments
11.17.1 Setting Up Attachments
To use attachments in conjunction with your purchasing documents, you have to define the following
settings described below.
Prerequisites
You have entered and executed the RFC destination NONE in transaction Workplace Single Sign-On
Admin. (SSO2). You have also checked that the profile parameters login/create_sso2_ticket and
login/accept_sso2_ticket of your SAP SRM system are set to value 1 (ticket including certificate). If
this is not the case, run transaction Profile Parameter Maintenance (RZ11) and change the values accordingly.
11 Cross-Application Settings
11.16 Define Objects in the Back-End System
2013-08-13 PUBLIC 127/148
Procedure
1. Create a user in transaction User Maintenance (SU01) for each client that is to use the attachment
service, for example SERVICExxx, where xxx = client number.
2. In the Address area, enter a name in the Last Name field.
3. In the Logon Data area, enter a password in the Initial password and Repeat password fields.
4. As User Type choose communication user.
Save your entries.
To display attachments in the Web browser, you first have to define the following settings in the Internet
communication framework in transaction Maintain Services (SICF):
1. In the Hierarchy Type field, select ALIAS (External Aliases).
2. In the Virtual Host field, choose your virtual host.
3. Enter a name for the external alias, for example /attach_<clientno>.
NOTE
You must activate the http server DOCSERVER.
4. Enter a description, for example, Attachment display.
5. Choose Execute.
6. In the Logon Data area, enter the client number in the corresponding field.
7. Enter user name and password for the respective client, as created in steps 1 to 5.
8. Save your entries.
9. Repeat steps 6 to 13 for each client.
More Information
See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings
Define Settings for Attachments .
11.17.2 Configuring Attachment Transfer
If you wish to store shopping cart attachments in the back-end system, you must first activate the data
transfer by creating an active method in the Business Add-Ins (BAdIs) BBP_CREATE_BE_PO_NEW (for
purchase orders) or BBP_CREATE_BE_RQ_NEW (for purchase requisitions).
For more information, see the following Customizing activites in SAP SRM:
■ SRM Server Business Add-Ins Follow-On Document Generation in the Backend System Purchase Order in
Backend System .
■ SRM Server Business Add-Ins Follow-On Document Generation in the Backend System Purchase Requisition
in Backend System .
Procedure
You have to configure the back-end Document Management System (DMS) in transaction DC10:
1. Create document type SRM. Note that no flag is set in any of the columns.
11 Cross-Application Settings
11.17 Attachments
128/148 PUBLIC 2013-08-13
2. Double-click in the detail view to define the new Doc. type desc. = SRM Documents. Set the Use KPro
indicator.
■ Enter 1 in the Number assignment field.
■ Enter an internal number range interval. You can use an existing interval or create a new one
in transaction CV90. The internal number range must be used, because the GUID of the SAP
SRM attachments has more digits than the number in the back-end system.
■ Maintain the number exit. The number exit is a program exit for document numbers. It
controls number assignment and version numbering for documents. The default setting is
MCDOKZNR. If you want to control the number assignment or the version increment via a
USER_EXIT, then you have to replace the program MCDOKZNR with a company-specific program.
You can find further information in the field help for number exit.
■ In the screen area Field selection, enter – in the Document Status field.
3. Go to the dialog structure and double-click the entry Define object links. Define the new object links
EKPO and EBAN. Maintain object link descriptions for EKPO (Purchase order item; Scr.no. 248) and
EBAN (Purchase req. item; Scr. no. 247)
4. Define the workstation application in transaction DC30.
NOTE
All required file types should be included in this list.
11.17.3 More Information About Attachments
Set Up Attachments
Perform the following Customizing activity in SAP SRM: SAP Supplier Relationship Management SRM
Server Business Add-Ins Follow-On Document Generation in the Backend System Purchase Requisition in Backend
System
Transfer Attachments
Perform the following Customizing activity in SAP SRM: SAP Supplier Relationship Management SRM
Server Cross-Application Basic Settings Define Settings for Attachments
11.18 Start Application Monitors
Perform the following activity in Customizing for SAP SRM: SRM Server Cross-Application Basic Settings
Start Application Monitors .
11.19 Message Control
Perform the following activities in Customizing for SAP SRM under SRM Server Cross-Application Basic
Settings Message Control :
11 Cross-Application Settings
11.18 Start Application Monitors
2013-08-13 PUBLIC 129/148
■ Influence Message Control
■ Influence Incoming Message Control
■ Influence Message Control for Invoice Simulation
11.20 Background Processing
Perform the following activities in Customizing for SAP Supplier Relationship Management:
■ SRM Server Activate Business Functions
■ SRM Server Cross-Application Basic Settings Background Processing Activate/Deactivate Advanced
Background Processing
■ SRM Server Cross-Application Basic Settings Define Threshold Value for Background Processing
11.21 Integration with Other SAP Components
11.21.1 Integration with SAP Records Management
11.21.1.1 Integration with SAP Records Management
This section describes how to integrate SAP Supplier Relationship Management (SAP SRM) with SAP
Records Management. SAP Records Management is document management system that enables you
to store purchasing documents centrally in the form of electronic records, and to access them any
time. SAP Records Management is part of SAP NetWeaver. To use SAP Records Management for SAP
SRM, you must use an SAP ERP system (minimum SAP ERP 6.0). SAP does not support that you use
the SAP Records Management that is located in the SAP SRM system.
RECOMMENDATION
Depending on the number of records you expect, we recommend to use a separate client or system
for SAP Records Management. From there, you can access procurement documents in all SAP
SRM or SAP ERP systems that you have connected.
When you activate the SRM-RM integration, records are automatically created in the Records
Management system for shopping carts, contracts, RFxs, and purchase orders. The record is created
automatically when a defined status (saved, released, approved) of the Business Object document is
reached using the call handler. The business data is known by the SAP SRM application at runtime and
a queue entry is written with the relevant data into the call handler tables. The call handler background
job then processes the queue and creates the record via RFC call.
Customizing is divided into settings that apply to the following components:
■ ArchiveLink
■ Knowledge Provider
■ SAP Records Management
11 Cross-Application Settings
11.20 Background Processing
130/148 PUBLIC 2013-08-13
■ SAP Supplier Relationship Management
11.21.1.2 Making Settings for ArchiveLink
This section describes how to make settings for ArchiveLink.
ArchiveLink is an integral part of SAP Web Application Server and enables you to link archived
documents to purchasing documents created in SAP Supplier Relationship Management (SAP SRM).
To link to archived purchasing documents that you created in the SAP SRM system, you define an
archive Link ID and customize the relevant technical data.
For more information about the required settings in R/3 (Records Management System) or SAP ERP,
see Customizing for SAP NetWeaver under Application Server Basis Services ArchiveLink
More Information
http://help.sap.com SAP NetWeaver SAP NetWeaver Release 7.0 (2004s) SAP NetWeaver Library
SAP NetWeaver by Key Capability Application Platform by Key Capability Business Services ArchiveLink
(BC-SRV-ARL)
11.21.1.3 Making Settings for Knowledge Provider
This section describes how to make settings for Knowledge Provider (KPro). Knowledge Provider (KPro)
is an integral part of SAP Web Application Server and provides cross-application and cross-media
document management technologies.
For more information, see the related documentation on SAP Help Portal at http://help.sap.com
under SAP NetWeaver SAP NetWeaver Release 7.0 (2004s) SAP NetWeaver Library SAP NetWeaver by
Key Capability Application Platform by Key Capability Business Services Knowledge Provider (BC-SRV-KPR) .
11.21.1.4 Making Settings for SAP Records Management
This section describes how to make the preliminary technical settings that are required in the SAP
Records Management (SAP RM) system to communicate with the SAP SRM system.
For more information, see the related documentation on SAP Help Portal at http://help.sap.com
under SAP ERP SAP ERP Cross-Application Functions Cross-Application Components Records and Case
Management .
Procedure
Go through the steps below.
Create SAP RM User
Run transaction User Maintenance (SU01) to create an SAP RM user with extended authorizations.
11 Cross-Application Settings
11.21 Integration with Other SAP Components
2013-08-13 PUBLIC 131/148
Edit Role
Perform this activity to assign role SRMCALLMON to the newly created user and check whether you
have the necessary authorizations for call handler authorization object S_CALLMON.
Edit Registry Objects
Run transaction SRM Registry Maintenance (SRMREGEDIT) to configure SAP RM objects. To do so,
expand the node S_AREA_CMG. This node contains a list of predefined service providers, which
enable record search, and record models for purchasing documents. You can copy them to your own
namespace and change them to meet your specific requirements.
Create Record Models
Perform this activity to create record models for purchasing documents. A record model is a predefined
template that enables you to specify what to attach to a record. You can copy record models to your
own namespace and change them to meet your specific requirements.
Define Logical Systems and RFC Connections
Perform these activities to connect the SAP RM system to the SAP SRM system.
Define Integration Scenarios
Run transaction SM34 and enter view cluster SRMAICONFIG to define the integration scenarios. For more
information, see the Customizing documentation for SAP SRM under SRM Server Cross-Application
Basic Settings Integration with Other SAP Components Integration with SAP Records Management Define Integration
Scenarios
Create Content Models
Run the wizard to create a content model in the SAP RM system. A content model enables you to
technically define documents with a common structure.
Assign Logical System to Client
Perform this activity to assign each logical system to a specific client.
Define RFC Connections for Method Calls
Perform this activity to define RFC connections in all systems for background and method calls. Each
logical system is assigned to an RFC destination for background and method calls.
Define Relationship Between Documents in Case Management and ArchiveLink Content Repositories
Run transaction SM30 to define in view /SAPPSPRO/SEMALD the relationship between the semantic
classification of documents in Case Management and the ArchiveLink content repositories.
11 Cross-Application Settings
11.21 Integration with Other SAP Components
132/148 PUBLIC 2013-08-13
11.21.1.5 More Information About Settings for SAP Records Management
Perform the following activity in Customizing for SAP NetWeaver: Application Server IDoc Interface /
Application Link Enabling (ALE) Communication Create RFC Connections .
Run the following system transactions in the SAP Records Management (SAP RM) system:
■ Role Maintenance (PFCG)
■ Maintain Authorization Objects (SU21)
■ Case Management (SCASE)
■ Create Content Models (SRMCMCREATE)
■ Client Administration (SCC4)
■ Monitor for Call Handler (SRMCALLMON)
Run the report RBDSDEST.
11.21.1.6 Defining Settings for SAP SRM Integration
To integrate the SAP Supplier Relationship Management (SAP SRM) system with the SAP Records
Management (SAP RM) system, you define the settings as described below.
Prerequisites
The preliminary settings in the SAP RM system have been made. For more information, see Customizing
for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings
Integration with Other SAP Components Integration with SAP Records Management Notes on SAP Record
Management .
Procedure
1. Create the SAP RM user
Run transaction User Maintenance (SU01) to create the user with extended authorizations.
2. Edit Role
Assign the role SRMCALLMON to the newly created user and check that you have the necessary
authorizations for the call handler authorization object S_CALLMON.
3. Define Background Job for Call Handler reports SRM_CALL_HANDLER_REPORT and
SRM_CALL_HANDLER_REPOR3.
When you create a purchasing document in the SAP SRM system, the system creates an entry in
a dedicated table. The call handler, a basis replication tool, processes this to create the corresponding
record and to link the purchasing document to the record by means of a predefined service provider.
4. Define Logical Systems and RFC Connections
Connect the SAP RM system to the SAP SRM system.
5. Assign Logical System to Client
11 Cross-Application Settings
11.21 Integration with Other SAP Components
2013-08-13 PUBLIC 133/148
Assign each logical system to a specific client.
6. Specify the data for SAP RM System in your system landscape.
7. Define RFC Connections for Method Calls
Define RFC connections in all systems for background and method calls. Each logical system is
assigned to an RFC destination for background and method calls.
8. Run transaction SM30 to define in view /SAPPSSRM/SEMCLS the relationship between the semantic
classification of documents in Case Management and the ArchiveLink content repositories.
9. Activate SAP RM Integration
Set the relevant indicator to activate the SAP RM integration.
To avoid inconsistencies in the SAP RM system, you can activate and deactivate SAP RM integration
once only. When the call handler reaches a defined status (Saved, Released, Approved, and so on) of
the business object (SC, CTR, PO or RFx), the SAP RM system automatically creates the record.
The SAP SRM application knows the business data at runtime and writes queue entry with the
relevant data into the call handler tables. The call handler background job processes the queue
and an RFC call creates the record.
Configuration Steps
Perform the following activities in Customizing for SAP Supplier Relationship Management:
1. SRM Server Cross-Application Basic Settings Integration with Other SAP Components Integration with SAP
Records Management Activate Integration with SAP Records Management
Perform this activity to link the SAP SRM system to the SAP RM system
2. SRM Server Cross-Application Basic Settings Integration with Other SAP Components Integration with SAP
Records Management Define Transfer Conditions for Records Management
Perform this activity to specify when a record is created for a specific purchasing document. For
example, you can specify that a record for a purchase order must be created when its status is set
to Held
3. SRM Server Technical Basic Settings Define System Landscape
Perform this activity to specify details about your SAP RM system, including the name and
description, in your SAP SRM system.
4. SRM Server Cross-Application Basic Settings Integration with Other SAP Components Integration with SAP
Records Management Define Integration Scenarios
Perform this activity to link the SAP SRM business objects to the corresponding SAP RM element
types.
5. SRM Server Technical Basic Settings Maintain Portal Information
Perform this activity to allow users to access purchasing documents on the SAP NetWeaver Portal
from a record stored in the SAP RM system.
11 Cross-Application Settings
11.21 Integration with Other SAP Components
134/148 PUBLIC 2013-08-13
Result
You have now connected the SAP SRM system to the SAP RM system and enabled the creation of
records for purchasing documents.
11.21.1.7 More Information About Settings for SAP SRM Integration
Perform the following activities in Customizing for SAP Supplier Relationship Management (SAP SRM):
■ SRM Server Technical Basic Settings ALE Settings Distribution (ALE) Basic Settings Logical Systems
Define Logical Systems
■ SRM Server Technical Basic Settings ALE Settings Distribution (ALE) Communication Create RFC
Connections
Perform the following activity in Customizing for SAP Web Application Server:
■ Application Server Basis Services Knowledge Provider Content Management Service Define Content
Repositories
Run the following system transactions in the SAP SRM system:
■ Role Maintenance (PFCG)
■ Maintain Authorization Objects (SU21)
■ Schedule Background Job (SM36)
■ Client Administration (SCC4)
■ Monitor for Call Handler (SRMCALLMON)
Run the report RBDSDEST.
11.21.2 Integration with SAP ERP
11.21.2.1 More Information About Contract Handling for Invoices
Perform the following activities in Customizing for SAP Supplier Relationship Management under:
■ SRM Server Activate Business Functions
■ SRM Server Cross-Application Basic Settings Service Procurement Activate Service Procurement
Innovations
■ SRM Server Cross-Application Basic Settings Service Procurement Define Status for Purchase Orders in Back-
End System
11.21.2.2 More Information About Contract Limits
Perform the following activities in Customizing for SAP Supplier Relationship Management under:
■ SRM Server Activate Business Functions
11 Cross-Application Settings
11.21 Integration with Other SAP Components
2013-08-13 PUBLIC 135/148
■ SRM Server Cross-Application Basic Settings Service Procurement Activate Service Procurement
Innovations
11.21.2.3 More Information About Links to SAP ERP Documents
Perform the following activities in Customizing for SAP Supplier Relationship Management under:
■ SRM Server Activate Business Functions
■ SRM Server Cross-Application Basic Settings Integration with Other SAP Components Integration with SAP
ERP Activate Linking to SAP ERP Documents
11.21.3 Catalog Integration
11.21.3.1 More Information About Catalog Integration
Perform the following activities in Customizing for SAP Supplier Relationship Management under:
■ SRM Server Activate Business Functions
■ SRM Server Cross-Application Basic Settings Integration with Other SAP Components Catalog Integration
Activate/Deactivate Catalog Integration Using ABAP FTP
■ SRM Server Cross-Application Basic Settings Integration with Other SAP Components Catalog Integration
Define FTP Servers
■ SRM Server Cross-Application Basic Settings Integration with Other SAP Components Catalog Integration
Define FTP Files
11.22 Digital Signatures
Perform the following activity in Customizing for SAP SRM: SRM Server Cross-Application Basic Settings
Digital Signature Activate Digital Signatures .
The following Business Add-In is available in Customizing for SAP SRM: SRM Server Business Add-Ins
Digital Signature Define Customer-Specific Document Preview .
11.23 User Experience
Perform the following activities in Customizing for SAP Supplier Relationship Management (SAP SRM):
■ SRM Server Activate Business Functions
■ SRM Server Cross-Application Basic Settings User Experience Activate Keyboard Navigation Redesign
■ SRM Server Cross-Application Basic Settings User Experience Activate/Deactivate Dropdown for Transaction
Type Selection
11 Cross-Application Settings
11.22 Digital Signatures
136/148 PUBLIC 2013-08-13
■ SRM Server Cross-Application Basic Settings User Experience Activate/Deactivate Progress Bar
■ SRM Server Cross-Application Basic Settings User Experience Activate/Deactivate Browse Mode
■ SRM Server Cross-Application Basic Settings User Experience Define Threshold Values for Large
Documents
11.24 POWL and Advanced Search
Perform the following activities in Customizing for SAP SRM under SRM Server Cross-Application Basic
Settings POWL and Advanced Search :
■ Adjust POWL Layout, Search Criteria, and Pushbuttons
■ Define Object Types for Advanced Search
■ Define Default POWL Application for Advanced Search
11.25 Optimistic Lock
Perform the following activities in Customizing for SAP Supplier Relationship Management (SAP SRM):
■ SRM Server Activate Business Functions
■ SRM Server Technical Basic Settings Activate/Deactivate Optimistic Lock
11.26 Version Control
11.26.1 More Information About Version Control
Perform the following Customizing activities in SAP SRM:
SAP Supplier Relationship Management SRM Server Business Add-Ins Version Control
11.27 Switch on Version Control for Purchasing Documents
11.27.1 More Information About Switching on Version Control for Purchasing Documents
Perform the following Customizing activities in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Switch on Version Control
for Purchasing Documents
11.28 Define Status Schema
11.28.1 More Information About Defining Status Schema
Perform the following Customizing activities in SAP SRM:
11 Cross-Application Settings
11.24 POWL and Advanced Search
2013-08-13 PUBLIC 137/148
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Define Status Schema for
User Status
The following SAP Notes apply:
SAP Note 1232945
11.29 Activate Direct Material
Perform the following activity in Customizing for Supplier Relationship Management (SAP SRM):
SRM Server Sourcing Activate/Deactivate Direct Material
11 Cross-Application Settings
11.29 Activate Direct Material
138/148 PUBLIC 2013-08-13
12 Component Planning
12.1 Select Additional Components
Using this process, you can select additional components from Web-based catalogs in SAP Supplier
Relationship Management (SAP SRM). You use the components for the following purposes:
■ Maintenance or service orders
■ Projects
In SAP SRM you assign materials to the orders/projects where they are required. Procurement occurs
in SAP SRM.
NOTE
This process does not currently support processing of services.
Prerequisites
■ You have been assigned to the role Component Planner (/SAPSRM/PLANNER). You process the roles
in Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application
Basic Settings Roles Define Roles .
■ You have assigned certain values to attributes. For more information, see User Attributes for Component
Planning [external document].
Procedure
The following graphic shows the process overview for component planning:
12 Component Planning
12.1 Select Additional Components
2013-08-13 PUBLIC 139/148
Figure 1:
1. Creating orders/projects in the back-end system
Create a maintenance/service order or a project. Add components to the order/project-based
transaction as required.
2. Changing to component planning for the order/project in SAP SRM
Log on to SAP SRM. Choose Component Planning.
3. Searching for orders/select projects in SAP SRM that were created in the back-end system
Enter criteria to search for orders or enter a project definition or a WBS element. Start the search/
selection.
The system uses a function module to search for the orders/project in the back-end system and
displays the result in SAP SRM. By default, the system displays detail data (including transaction
number and tax code) for the first transaction.
If you choose an order/project, the transactions for the order are also displayed in the overview
tree. In addition, header data of the order/network is also displayed for the selected transaction. In
the project scenario, the header data also contains the ID of the WBS element. The individual
order/project components are listed in the component overview.
RECOMMENDATION
You can only change this data in the back-end system.
4. Displaying and changing default values
Choose Display default values to edit the values for the following fields:
■ Purchasing group
12 Component Planning
12.1 Select Additional Components
140/148 PUBLIC 2013-08-13
■ Purchasing organization
■ Material group
■ G/L account
■ Plant
■ Goods recipient
■ Unloading point
■ Requirement date type (only project scenario)
NOTE
● If you enter a manual requirement date, this will always overwrite a different
requirement date type that is defaulted.
● If you want to use default values that cannot be processed using the organization
model, you can use the Business Add-In Set Default Values for Component Planning
(BBP_PM_DEFAULT_VAL) to define input help for selected fields.
The system then transfers these values to the detail data screen for each component
added, where they can also be changed.
Choose Return to Component Overview to display the component overview again.
5. Choosing new components from the catalog
First choose the catalog from which you require components. In the catalog, choose the required
component in appropriate quantity and order the shopping cart.
The system transfers the components contained in the shopping cart to the component overview
and assigns the components transferred from the catalog to the selected transaction.
NOTE
The system also transfers SAP product master data from the catalog, where applicable.
6. Creating new components manually
(As an alternative to 5) Enter a description or a back-end material number for the component and
choose Add component. The system adds the component to the component overview.
7. Displaying detail data for components
You can display detail data for each component. To do this, click on the description of the relevant
component in the component overview.
8. Changing and deleting component data
You can only change and delete components copied from a catalog during an SAP SRM session,
or components that have been manually created.
To delete a component, click on the symbol in the column Action in the component overview.
To change a component, display the detail data. Perform changes to the general data or purchasing
data.
9. Creating and changing long texts for components
You can only add or change long texts for components that were copied from a catalog or entered
manually.
12 Component Planning
12.1 Select Additional Components
2013-08-13 PUBLIC 141/148
To process a long text, display the detail data for the component. Choose Long text. Enter a long
text.
10. Checking components
You can check all the data for components added in SAP SRM.
Defective components are highlighted in red in the component overview. You can read the error
in the detail screen before correcting the data. Carry out the check again in the component
overview.
NOTE
You can use the Business Add-In Check and Complete Component Data (BBP_PM_COMP_CHK)
to supplement or check component data.
11. Transfer component data to the back-end system
Save the order/project. After a check, the components added in the SAP SRM system are transferred
to the back-end system.
NOTE
■ Order scenario
The updated components for orders or order-based transactions are now in the back-
end system. Components already transferred can no longer be changed in SAP SRM.
They do, however, remain in the component overview.
■ Project scenario
The updated components for projects are now in the back-end system. The system
changes to the initial screen where you can enter another project definition or WBS
element.
You can also further process the order/project or transactions here.
If the order/project status allows, reservations are automatically generated for stock component and
purchase requests for non-stock components during transfer to the back-end system.
12.2 Defining User Attributes in the Organizational Plan
System administrators can define the most important user attributes at organizational unit level in the
organizational plan using the Customizing activity Change Organizational Plan (transaction PPOMA_BBP).
You define the attributes using the tab pages Function, Responsibility, Attributes, and Extended Attributes. The
following table provides an overview of the attributes that you define on each tab page:
Function Responsibility Extended attributes Attributes
■ Companies ■ Purchasing
organizations ■ Purchasing groups
NOTE
For purchasing groups only.
■ Product responsibility (for product groups)
■ Product categories ■ Plants ■ Storage locations ■ Approval limits
All other attributes
12 Component Planning
12.2 Defining User Attributes in the Organizational Plan
142/148 PUBLIC 2013-08-13
■ Organizational responsibility (for departments and groups)
If managers want to edit attributes for their organizational units, or users in their organizational units,
they can use the Web application Change Attributes. Employees can use this Web application to change
their own attributes.
Prerequisites
You have defined at least the top node of your organizational plan with transaction PPOCA_BBP. See
Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Settings
Organizational Management Create Organizational Plan
Procedure
1. See Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Settings
Organizational Management Change Organizational Plan .
Alternatively, use transaction PPOMA_BBP.
2. Search for the organizational unit for which you want to define user attributes.
Defining attributes using tab card Function
1. On the Details screen, choose tab card Function.
2. Specify whether the organizational unit is a company, a purchasing organization, or a purchasing
group.
Defining attributes using tab card Responsibility
NOTE
The details on this tab page replace the previously used attributes RESP_PGRP, RESP_PRCAT, and
RESP_WGR on the tab pages Attributes and Extended Attributes.
1. On the Details screen, choose tab card Responsibility.
2. Specify the product categories and organizational units for which the purchasing group is
responsible. You can use wildcards (*) and ranges to do this.
Defining attributes using tab card Attributes
1. On the Details screen, choose tab card Attributes.
2. Enter a value for each attribute you wish to define.
3. To locally deactivate an attribute value for a certain organizational unit, and to prevent it being
inherited by a subordinate organizational unit, set the Excluded indicator.
4. To define an attribute value as the default value in cases where multiple values exist, check
Default.
5. Save your entries.
12 Component Planning
12.2 Defining User Attributes in the Organizational Plan
2013-08-13 PUBLIC 143/148
Defining attributes using tab card Extended Attributes
NOTE
You define a logical system for the attributes Material Group, Storage Location, and Plant. This logical
system is the source system for the data, not the target system to which the business documents
are later transferred. You can define the target system for a material group in Customizing for
SAP Supplier Relationship Management under SRM Server Technical Basic Settings Define Backend System
for Product Category .
1. On the Details screen, choose tab card Extended Attributes.
2. For Extended Attribute, choose the attribute that you want to define.
■ Product categories
You can define product categories (material groups) (attributes PRCAT and WGR). You can enter
both individual product category IDs, as well as value areas and wildcards (*).
■ Plants
You can define plants (attribute WRK) together with the relevant company code.
■ Storage locations
You can define storage locations (attribute LAG) together with the relevant value and the
logical system.
■ Order value limits
You can define the spending limit (attribute SPEND_LIM) and approval limit (attribute
APPRV_LIM) and the user budget together with the currency
3. To locally deactivate an attribute value for a certain organizational unit, and to prevent it being
inherited by a subordinate organizational unit, set the Deactivate indicator.
4. To define an attribute value as the default value in cases where multiple values exist, check
Default.
5. Save your entries.
Result
The attributes you have defined are saved in the organizational plan.
12 Component Planning
12.2 Defining User Attributes in the Organizational Plan
144/148 PUBLIC 2013-08-13
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 Example
Arrows separating the parts of a navigation path, for example, menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
http://www.sap.com Textual cross-references to an internet address
/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.
■ Cross-references to other documentation or published works
Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2013-08-13 PUBLIC 145/148
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +49/18 05/34 34 34F +49/18 05/34 34 20
www.sap.com
© Copyright 2013 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
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. National product specifications may vary.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.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
DisclaimerPlease see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.
Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/srm-instinstguides
146/148 PUBLIC 2013-08-13
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com
© Copyright 2013 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.