Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0

Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Document version: 1.0 – 2016-01-20
CUSTOMER
Basic Settings for SAP Enhancement Package 4 for
SAP SRM 7.0
Based on SAP Solution Manager Content
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 2171391
.
Table 1
Version
Date
Description
1.0
2016-01-20
Initial Version
2
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Document History
Content
1
Important Information About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
2
Basic Settings for SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
3
3.1
Flexible Deployment Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Portal-Independent Navigation Frame and Inbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Portal-Independent Navigation Frame Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inbox Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BW-Independent Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring BW-Independent Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PI-Independent Enterprise Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration of PI-Independent Enterprise Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About PI-Independent Enterprise Services . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9
9
10
11
11
12
12
14
4.5
4.6
SAP NetWeaver Process Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configure Business Systems with an Integration Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up Business Systems Landscapes for SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About Business System Configuration with Integration Engine . . . . . . . . . . . . .
Define Business Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Business Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Check Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking SAP NetWeaver PI Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About Checking Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configure IDoc Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the IDoc Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the IDoc Adapter for Supplier Self-Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About Configuring IDoc Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Advanced XML Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About SAP NetWeaver Process Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
15
15
15
16
16
16
16
18
18
18
19
19
19
20
5
5.1
Customizing Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Synchronizing Customizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6
6.1
System Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automated Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automated Configuration of the Portal Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automated Configuration Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Back-End Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Back-End Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical Systems and RFC Connections in the SAP SRM Landscape . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Logical Systems and RFC Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Distribution Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logical Systems and RFC Connections in the SAP ERP Landscape . . . . . . . . . . . . . . . . . . . . . . . . . .
Middleware Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2
3.3
4
4.1
4.2
4.3
4.4
6.2
6.3
6.4
6.5
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Content
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
23
23
23
23
24
24
25
25
27
29
29
3
6.6
6.7
6.8
6.9
6.10
7
7.1
7.2
7.3
7.4
7.5
8
8.1
8.2
8.3
9
9.1
9.2
9.3
9.4
4
Defining Middleware Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specify Back-End System for Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Settings in SAP SRM and in the Back-End System . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define Settings for Standalone Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Aligning Units of Measurement, Currencies, and Exchange Rates . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Engine (CE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up Configuration Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About Configuration Engine (CE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Technical Settings for E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Technical Settings for E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quick Guide to SMTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Control Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Jobs for Scheduling Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduling Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
31
32
37
37
38
38
38
39
39
39
43
44
44
Master Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replication of Materials from ERP Back-End Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customizing Material Replication in SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading Customizing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Materials and Service Master Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading Business Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About Materials and Service Master Download . . . . . . . . . . . . . . . . . . . . . . . .
Checking Downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46
46
46
47
49
49
50
51
Organizational Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Organizational Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Portal Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintain User Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Harmonized Procurement Roles for SAP ERP and SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Regenerating Role Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maintaining the User Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integration of Business Partners into Organizational Management . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up Integration with Organizational Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduling Periodic Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About Integrating Business Partners into Organizational Management . . . . . . .
52
52
52
56
58
75
77
77
77
79
74
81
81
81
82
82
Locations and Business Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Making Settings for Locations and External Business Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Partner Address Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Business Partner Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Number Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Number Ranges for Business Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Locations and Business Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
83
54
84
84
85
85
85
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Content
10
10.1
10.2
10.3
Supplier Master Data Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Settings for Supplier Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Locked Suppliers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating and Registering Root Supplier Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About Settings for Supplier Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . .
Replicating Supplier Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking Downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
11.1
11.2
11.3
11.4
11.5
11.6
11.7
11.8
11.9
11.10
11.11
11.12
11.13
11.14
11.15
11.16
11.17
11.18
Cross-Application Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Defining Configurable Item Numbering Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Activating Revision Level Field for Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Output Actions and Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Defining Actions for Document Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Condition-Dependent Document Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Uploading Product Category Hierarchy Files from External Systems . . . . . . . . . . . . . . . . . . . . . . 91
More Information About Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Number Ranges for Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Defining Number Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
More Information About Number Ranges for Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Text Schema and Text Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Define Transaction Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Activate Extended Classic Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Setting Up Extended Classic Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Business Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Select Workflow Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Process-Controlled Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Application-Controlled Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Universal Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Alert Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Configuring SRM Alert Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Settings for Tax Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Making Settings for Tax Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Tax Calculation in the SAP ERP Financial Accounting System . . . . . . . . . . . . . . . . . . . . . . . . . . 124
More Information About Settings for Tax Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Settings for Account Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Making Settings for Account Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
More Information About Settings for Account Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Payment Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Creating Payment Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Create Incoterms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Pricing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Set Up Simplified Pricing for Classic Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
More Information About Pricing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Define Objects in the Back-End System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Setting Up Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Configuring Attachment Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
More Information About Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Start Application Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Content
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
87
87
87
87
88
88
51
5
11.19
11.20
11.21
11.22
11.23
11.24
11.25
11.26
11.27
11.28
11.29
11.30
11.31
11.32
Message Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Background Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integration with Other SAP Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integration with SAP Records Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integration with SAP ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Catalog Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Digital Signatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Experience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
POWL and Advanced Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optimistic Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switch on Version Control for Purchasing Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About Switching on Version Control for Purchasing Documents . . . . . . . . . . .
Define Status Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information About Defining Status Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activate Direct Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activate/Deactivate Automatic Enlargement of Long Text Boxes . . . . . . . . . . . . . . . . . . . . . . . . . .
Activate/Deactivate Purchase Order Header Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activate/Deactivate Central Substitution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
12.1
12.2
Component Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Select Additional Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Defining User Attributes in the Organizational Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
131
132
132
132
137
138
138
138
139
139
139
139
139
139
140
140
140
140
140
140
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Content
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 2165450
under
master guide at service.sap.com/instguides
Applications SAP SRM SAP SRM Server 7.14
and the SAP SRM
Installation and Upgrade Guides
SAP Business Suite
Business Functions
SAP enhancement package 4 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
For more information about these business functions, see SAP Help Portal at help.sap.com
SAP Supplier
Relationship Management SAP SRM 7.0 EHP4 Application Help SAP Library Business Functions and
Customizing Switches .
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Important Information About This Document
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
7
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.
8
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Basic Settings for SAP SRM
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 Portalindependent 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 help.sap.com
Technology Platform SAP NetWeaver
SAP NetWeaver <release> ABAP Technology UI Technology Web UI Technology Floorplan
Manager for Web Dynpro ABAP Launchpad .
○
3.
In the System Alias for POWL Navigation field, enter SAP_BW.
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
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Flexible Deployment Variants
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
9
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 10].
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 PortalIndependent 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
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.
10
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Flexible Deployment Variants
●
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 9]
●
For more information about the POWL, see SAP Help Portal at help.sap.com
Enterprise Management
SAP ERP SAP ERP 6.0 EHP8 Application Help SAP Library SAP ERP Cross-Application Functions
Cross-Application Components General Application Functions Personal Worklist .
3.2
3.2.1
BW-Independent Analytics
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
Server Analytics Activate/Deactivate BW-Independent Analytics .
SRM
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.
●
You have adapted the layout of Crystal Reports to your requirements under Manage Generic Crystal Reports.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Flexible Deployment Variants
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
11
More Information
For more information about how to configure the Portal-independent navigation frame, see Portal-Independent
Navigation Frame Configuration [page 9].
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 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 help.sap.com
under SAP NetWeaver Library SAP NetWeaver by
Key Capability Application Platform by Key Capabilities ABAP Technology ABAP Workbench ABAP
Workbench Tools Web Services Creating Consumers/Providers for the Enterprise Services Repository 7.1
Managing the Web Service Runtime Configuring the Web Service Runtime .
SOA Manager
Use the SOA Manager (transaction code SOAMANAGER) to administer and configure service providers and
consumer proxies in both the SAP Supplier Relationship Management (SAP SRM) system and the SAP ERP
under
system. For more information about how to use the SOA Manager, see SAP Help Portal at help.sap.com
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 .
12
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Flexible Deployment Variants
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
to it.
Technical Administration
System Connections , you create a provider system and assign a profile
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
6.
Service Administration
Business Scenario Configuration
and proceed as follows:
1.
Choose New.
2.
In step 1 (General), enter the business scenario name and description.
3.
Choose Next.
4.
In step 2 (Provider Side), choose Add to enter all relevant inbound services, for example:
○
PurchaseOrderERPConfirmation_In
○
PurchaseOrderERPContractReleaseNotification_In
○
PurchaseRequestERPSourcingRequest_In
○
PurchasingContractERPConfirmation_In
○
PurchasingContractSRMReplicationConfirmation_In
○
RFQRequestSUITERequest_In
○
SupplierInvoiceSUITEContractReleaseNotification_In
○
PurchaseOrderERPRequest_In_V1
5.
For each of the services, choose Assign Profile to assign the profile created in step 1.
6.
Choose Next.
7.
In step 3 (Consumer Side), choose Add to enter the service group /SAPSRM/SERVICEPROC_CLASSIC.
8.
Choose Assign Business Application to assign the provider system created in step 2 to the service group.
You activate the business function Improvements for SOA Reuse Functions (FND_SOA_REUSE_1).
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Flexible Deployment Variants
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
13
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:
14
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
SRM Server
Activate Business Functions .
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Flexible Deployment Variants
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 selfservices (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>
EHP4 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
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
SAP NetWeaver Process Integration
Configuration
SAP SRM 7.0
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
15
Run the following transactions in SAP SRM, SUS, and SAP ERP:
●
User Maintenance (SU01)
●
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
EHP4 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:
Table 2
Activity
In
You have defined a logical system using transaction SALE, as
described in Customizing for SAP NetWeaver under
Web Application Server
Application Server
Interface / Application Link Enabling (ALE)
Settings
Logical Systems
Procurement scenario
IDoc
Basic
●
Define Logical System .
described in Customizing for SAP NetWeaver under
Application Server
Interface / Application Link Enabling (ALE)
Settings
Logical Systems
SAP Supplier Relationship Management (SAP SRM) and
supplier self-services (SUS) for the Service
SAP
Materials Management in SAP Enterprise Resource
Planning (SAP ERP) and supplier self-services (SUS) for
the Plan—Driven Procurement scenario
You have assigned the client to the logical system, as
Web Application Server
●
SAP
IDoc
Basic
Assign Logical System to
Client
16
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
SAP NetWeaver Process Integration
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/
●
SAP Supplier Relationship Management (SAP SRM) and
SUS_ADMIN_SUPPLIER and
supplier self-services (SUS) for the Service
SAP_EC_SUS_ADMIN_VENDOR to the XIAPPLUSER user.
Procurement scenario
●
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
SAP NetWeaver Process Integration (SAP NetWeaver PI)
LCRSAPRFC.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
SAP NetWeaver Process Integration
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
17
You have defined a technical name, for example, QWA.
System Landscape Directory (SLD)
You have defined a business system name, for example,
System Landscape Directory (SLD)
QWA_100.
You have defined a back-end system, as described in
●
Defining Back-End Systems [page 24].
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:
●
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:
18
○
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.
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
SAP NetWeaver Process Integration
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.4.3
More Information About Configuring IDoc Adapter
For more information, see SAP Solution Manager under <project> Configuration
Settings for SRM SAP NetWeaver Process Integration Configure IDoc Adapter :
●
Integration Using the IDoc Adapter
●
Creating Ports
●
Maintaining the Integration Server
SAP SRM 7.0 EHP4
Basic
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).
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
SAP NetWeaver Process Integration
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
19
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 EHP4
Integration Defining SAP NetWeaver PI Settings
Basic Settings for SRM
SAP NetWeaver Process
●
<project name> Configuration SAP SRM 7.0 EHP4
Integration Error and Conflict Handler
Basic Settings for SRM
SAP NetWeaver Process
20
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
SAP NetWeaver Process Integration
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 help.sap.com
under Technology Platform 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).
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Customizing Synchronization
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
21
Result
The above objects are synchronized in the SAP SRM and SAP ERP systems.
22
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Customizing Synchronization
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
help.sap.com
Technology Platform SAP NetWeaver SAP NetWeaver <release> 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
SAP Business Suite Applications
Service Marketplace at service.sap.com/instguides
SRM Server 7.02 Guide for Automated Configuration: SAP SRM Portal .
6.1.2
SAP SRM
SAP
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
help.sap.com
Technology Platform SAP NetWeaver SAP NetWeaver <release> Technology
Consultant’s Guide Configuration Wizard Business Suite Connectivity Configuration - Overview .
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
23
The following table lists the individual scenarios for which automated configuration is supported and where to find
their corresponding connectivity guides.
Table 3
System Configuration
SAP SRM on One Client in SAP ERP
Path to Documentation on SAP Service Marketplace
service.sap.com/instguides
Applications
SAP SRM
SAP Business Suite
SAP SRM Server 7.13
Connectivity Guide for Automated Configuration: SAP SRM on
One Client in SAP ERP
Connecting SAP SRM to SAP ERP
service.sap.com/instguides
Applications
SAP SRM
SAP Business Suite
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)
service.sap.com/instguides
Applications
SAP SRM
SAP Business Suite
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 29].
24
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
Procedure
Defining Back-End System
Go to Customizing for SAP Supplier Relationship Management under
Define System Landscape .
SRM Server
Technical Basic Settings
●
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.
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
6.3.1
Logical Systems and RFC Connections in the SAP SRM
Landscape
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.
Prerequisites
If 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 .
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
25
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
.
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
Server
Technical Basic Settings Define RFC Destinations .
1.
SRM
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 selfservices 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
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,
26
ABAP connections , and double-click the entry for your supplier self-services
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
check the authorization level of the user in the SAP ERP system. You can also do this by choosing
Authorization .
7.
Test
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.
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
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
27
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:
Table 4
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:
Table 5
6.
Object Name/Interface
Method
IncomingInvoiceEC (EC Incoming Invoice)
Create
BBP_PCSTAT (Procurement Card Statement)
Create
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
28
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
transaction BD64. Select the model view for which you want to generate partner profiles. Choose
Model View
Edit
Distribute . Select the relevant back-end system and choose Continue.
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)
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
29
Prerequisites
You have been assigned to the SAP_CRM_MW_ADMINISTRATOR role. This role allows you to run transaction
Administration Console (SMOEAC).
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:
Console ).
Administration
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.
Administration
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
4.
. See also SAP Note 720819
.
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.
30
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
More Information
SAP Note 519794
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:
Console ).
2.
Select object type Sites.
3.
Choose
4.
Enter the name, description, and type (R/3)
Object
Administration
Administration
Create .
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
.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
31
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).
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
32
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
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.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
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
33
○
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.
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:
○
34
Consumer application: SRM (for example)
○
Object name: *
○
Destination: <SM59 RFC destination of SRM system>
○
Download type: Request (R)
○
Queue name: ' '
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
9.
○
InQueue name: ' '
○
BAPI name: ' '
○
Short description: DEFAULT DESTINATION FOR SRM
○
Data record inactive: ' '
○
Ignore Data: ' '
○
InQueue indicator: X
○
Use XML: X
○
Stop data: ' '
Save your entries.
6.5.3.4
6.5.3.4.1
Checking OLTP Parameters
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.
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: ' '
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
35
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.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:
36
○
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)
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
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:
●
In the SAP SRM system, in Customizing for SAP Web Application Server under
Units of Measurement
●
In the back-end system, in Customizing for SAP NetWeaver under
Measurement
General Settings
General Settings
Check
Check Units of
Adjusting currencies and exchange rates
If an SAP FI back-end system is used, run the following reports:
●
BBP_GET_CURRENCY
●
BBP_GET_EXRATE
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
37
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
Units of Measurement
●
In the back-end system, in Customizing for SAP NetWeaver under
Measurement
General Settings
General Settings
Check
Check Units of
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
4.
Choose Adjust.
6.7
Edit
Select
Select All .
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.7.2
More Information About Configuration Engine (CE)
The following SAP Note applies:
●
38
844817
(Technical information for the VMC-based AP 7.00 engines)
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
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
Table 6
Transaction
SCOT
Menu Path
SAP Menu
Basis Tools
Communication
Business 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
Table 7
Transaction
SCOT
Menu Path
SAP Menu
Basis Tools
Communication
1.
Choose
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
View
Business Communication
SAPconnect
Jobs .
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
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
39
without the need for any additional external components. In the outbound 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, SMS=+491759628717@sms-server.company.com), or to an external provider (for example, FAX=
+16105954900@fax-provider.com). For receiving, the fax/text message server or provider sends e-mails to
addresses with the SAP system's domain (for example, FAX=+496227751624@crm-prod.company.com).
Prerequisites
The 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 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.
40
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
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
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
created or changed.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
Activate
after being
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
41
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:
Table 8
8.
SAPscript/Smart Forms
PDF
ABAP List
HTM
Business Object/Link
HTM
RAW Text
TXT
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:
Table 9
4.
SAPscript/Smart Forms
PDF
ABAP List
PDF
Business Object/Link
TXT
RAW Text
TXT
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.
42
Confirm.
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
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
2.
If there is not already a job scheduled, choose
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.
View
Jobs .
Job
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
Server Technical Basic Settings Set Control Parameters .
SRM
Table 10
Key Control Record
Description
Value Control Record
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
<number>
BAPIs
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
43
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
Table 11
Report Name
Description
Required/ Optional
CLEAN_REQREQ_UP (and
Updating of documents (purchase
Required
START_CLEANER)
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.
BBP_GET_STATUS_2
This report updates shopping carts.
Required
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.
44
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
RSPPFPROCESS
If the purchase orders are to be
Optional
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.
BBPERS
If you use Evaluated Receipt Settlement
Optional
(ERS) for local purchase orders for
which confirmations exist, you must
start BBPERS.
BBP_DELETE_LOCAL_ACCOUNT
Optional
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
System Connections
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
45
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 backend 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 25]
Process
You have to perform the following steps in the order given:
1.
Customizing Material Replication in SAP SRM [page 46]
2.
Defining Middleware Parameters [page 29]
3.
Downloading Customizing Objects [page 47]
4.
Downloading Business Objects [page 49]
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 25].
46
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Master Data Replication
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 measure or countries in
your backend systems, you have to make corresponding entries in the SAP SRM system.
Path in Customizing:
2.
○
Countries: SAP Web Application Server
mySAP Systems (CRM, SRM, SCM,...) .
○
Currencies:
○
Units of Measure:
SAP Web Application Server
General Settings
Set Countries
Specify Countries in
Currencies
Check Currency Codes
General Settings
SAP Web Application Server
General Settings
Check Units of Measurement
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 25]
●
Customizing Material Replication in SAP SRM [page 46]
●
Defining Middleware Parameters [page 29]
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:
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Master Data Replication
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
47
○
DNL_CUST_BASIS3
○
DNL_CUST_PROD0
○
DNL_CUST_PROD1
○
DBL_CUST_SRVMAS
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
48
(Problems with logical system during data exchange)
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Master Data Replication
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 25]
●
Customizing Material Replication in SAP SRM [page 46]
●
Defining Middleware Parameters [page 29]
●
Downloading Customizing Objects [page 47]
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).
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Master Data Replication
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
49
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)
50
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Master Data Replication
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Master Data Replication
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
51
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 54]).
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.
52
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
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
Systems .
7.
SRM Server
Technical Basic Settings
Define Back-end
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.
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
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
53
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
Helps, Search Helps and Favorites
SRM Server
Interface Configuration
Cross-Application Basic Settings
Input Helps and Search Helps
Message Control
Display of Input
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.
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 Basis Services Address Management Maintain Address and Person Number
Range .
●
Partner functions in Customizing for SAP Supplier Relationship Management
Application Basic Settings Define Partner Functions .
SRM Server
Cross-
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.
54
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 .
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
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.
Table 12
To retrieve all the location numbers from each back-end
BBP_LOCATIONS_GET_ALL
system that is connected
To retrieve all the location numbers from one particular back-
BBP_LOCATIONS_GET_FROM_SYSTEM
end system
To retrieve selected locations
BBP_LOCATIONS_GET_SELECTED
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 SAP SRM 7.0
EHP4 Application Help SAP Library 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 .
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
55
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 4 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.
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 EHP4.
56
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
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.
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
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
57
8.1.3
8.1.3.1
Maintain User Attributes
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.
Table 13
Attribute
Description and Example
Definition
System-Dependent
Value
ACS
System alias for accounting
Specifies the back-end
systems
system where the account
Example value: ABCCLNT123
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
Server
SRM
Technical Basic
Settings
Define Basic
Settings. .
ADDR_BILLT
Invoice recipient address
Default invoice recipient
address in purchase order.
ADDR_SHIPT
58
Ship-to address
Default ship-to party address
Example value: 12345
in purchase order.
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
Enter at least one ship-to
address and set it as the
default address.
AN1
Asset
Specifies the asset in the
Example value:
back-end system. Default
ABCCLNT123\000000001111 value for account assignment
when creating shopping cart
or lean purchase order.
AN2
Asset subnumber
Defines the asset sub-
Example value:
number in the back-end
Q4CCLNT300\1234
system. Default value for
account assignment when
creating shopping cart or lean
purchase order.
ANK
Asset class
Defines the asset class in the
Example value:
back-end system. Default
QW4CLNT100\00001000
value for account assignment
when creating shopping cart
or lean purchase order.
ANR
Order
Defines the order in the back-
Example value:
end system. Default value for
ABCCLNT123\0000000000
account assignment when
40
creating shopping cart or lean
purchase order.
APO
Sales order item
Defines the sales order item
Example value:
in the back-end system.
Q4CCLNT300\123456
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
Server
SRM
Cross-Application
Basic Settings
Organizational
Management
Change
Organizational Plan.
AUN
Sales order
Specifies the sales order in
the back-end system. Default
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
59
BSA
Example value:
value for account assignment
ABCCLNT123\0000000003
when creating shopping cart
33
or lean purchase order.
Transaction type: Shopping
Defines the transaction type
cart follow-on document
in the respective system for
Example value:
follow-on documents from
ABCCLNT123\ECA3
shopping carts.
The attribute needs to be
defined once per system, for
the local SAP SRM system
and for all connected backend systems.
BUDGET
User budget
Amount available to an
employee for purchases.
Required for the Purchasing
Budget Workflow [external
document].
BUK
Company code
Company code in the back-
Example value:
end system.
QW4CLNT100\1000
Generally, the user inherits
the company code from
his/her company. If you want
to overwrite the value
inherited from the company
you should define the
company code via this
attribute only.
You define the company code
of the company for the
organizational unit assigned
to the company on the
Function tab.
See Customizing for SAP
Supplier Relationship
Management under
Server
SRM
Cross-Application
Basic Settings
Organizational
Management
Change
Organizational Plan.
BWA
Movement type
Defines the type of goods
Example value:
movement in the back-end
ABCCLNT123\123
system. This value is required
if reservations are to be
created in the back-end
system.
60
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CAT
Catalog ID
Defines the catalogs to which
Example value: MDMCA30
a user has access. You must
define this attribute in
Customizing for SAP Supplier
Relationship Management
under
SRM Server
Master Data
Content
Management
Define
External Web Services.
CNT
Cost center
Defines the cost center in the
Example value:
back-end system. Default
ABCCLNT123\0000001000
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
Server
SRM
Cross-Application
Basic Settings
Organizational
Management
Change
Organizational Plan.
CT_PROC_TY
Transaction Type: Contract
Transaction Type for
Contract
CUR
Local currency
Default currency of the user
Example value: EUR
DP_PROC_TY
Transaction type: Direct
Specifies the transaction type
material
that is used when purchase
Example value: ECDP
orders for direct materials
are created via BAPI,
shopping cart, or bid
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
61
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
Server
SRM
Cross-Application
Basic Settings
Define
Transaction Types.
EXT_ITS
Current ITS of an external
Obsolete from SRM 7.0
partner
Example value: http://
abc.firma.com/wgate/
FORWARD_WI
Flag: Forward work item
Indicator: Specifies whether
Example value: X
work items are to be
forwarded as e-mails.
IS_COMPANY
Indicator: Company
Indicator: Identifies an
organizational unit as
independent legal entity.
This attribute is simulated.
You set this indicator for an
organizational unit on the
Function tab by selecting
Company.
You should define an
organizational unit high up in
the organizational plan as
company by setting this
indicator. If you have further
organizational units in a lower
level of your plan that
represent subsidiaries, you
also need to set this
indicator.
62
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
See Customizing for SAP
Supplier Relationship
Management under:
Server
SRM
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
Server
SRM
Cross-Application
Basic Settings
Organizational
Change
Management
Organizational Plan.
IS_POR
Indicator: Purchasing
This indicator specifies that
organization
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
Server
SRM
Cross-Application
Basic Settings
Organizational
Change
Management
Organizational Plan.
ITS_DEST
Current ITS of a user
Obsolete from SRM 7.0
Example value: http://
abc.firma.com/wgate/
KNT
Account assignment
Default value for account
category
assignment when creating
Example value: CC
shopping cart or lean
purchase order.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
63
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
Network
Specifies the network in the
Example value:
back-end system. Default
ABCCLNT123\0000006000
value for account assignment
03
when creating shopping cart
or lean purchase order.
PM_ARWRK
Plant for work center
Plant in which the executing
Example value:
work center is located.
ABCCLNT123\1234
This attribute is used as a
selection criterion when
searching for orders in the
back-end system.
PM_AUART
Order type
Order types distinguish
Example value:
orders according to their use,
ABCCLNT123\PM01
for example, maintenance
and service orders.
This attribute is used as a
selection criterion when
searching for orders in the
back-end system.
PM_GL_ACCT
PM_IPHAS
64
PM: Default G/L account
Default value for the G/L
Example value:
account in the component
ABCCLNT123\417000
detail data.
Phase
Phases subdivide the life
Example value:
cycle of an order into several
ABCCLNT123\0
subsections (for example,
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
created and released) and
determine which activities
are allowed for the order in
each section.
This attribute is used as a
selection criterion when
searching for orders in the
back-end system.
This is a mandatory attribute.
PM_IWERK
Planning plant
Plant at which maintenance
Example value:
tasks are planned and
ABCCLNT123\1234
prepared.
This attribute is used as a
selection criterion when
searching for orders in the
back-end system.
PM_PUR_GRP
PM purchasing group
Number of the organizational
Example value:
unit that is indicated as the
ABCCLNT123\001
purchasing group in the
organizational plan. Default
value in the component detail
data.
PM_PUR_ORG
PM purchasing organization
Number of an organizational
Example value:
unit that is indicated as the
ABCCLNT123\1000
purchasing organization in
the organizational plan.
Default value in the
component detail data.
PM_SWERK
Maintenance plant
Plant at which the technical
Example value:
objects of a company are
ABCCLNT123\1234
installed.
This attribute is used as a
selection criterion when
searching for orders in the
back-end system.
PM_VAWRK
Plant for main work center
Plant at which the main work
Example value:
center entered is located.
ABCCLNT123\1234
This attribute is used as a
selection criterion when
searching for orders in the
back-end system.
PM_WGR
PM material group
Indicates the key of the
Example value:
material group that unites
ABCCLNT123\000000001
materials and services with
the same properties. Default
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
65
value in the component detail
data.
PM_WRK
Plant of the component
Plant at which the component
Example value:
required to execute the order
ABCCLNT123\1000
(reservation or requirement
request) is planned. Default
value in the component detail
data.
This is a mandatory attribute.
PRCAT
Material group
Defines the product
categories for which the user
has authorization. We
recommend that you define a
default value. For example, if
a user mainly purchases
office materials, it would
make sense to specify office
materials as the default
value.
To improve performance, we
recommend that you use
wildcards and ranges to
restrict the product
categories defined as much
as possible.
You define this attribute
using tab card Extended
attributes.
PRI
Default printer
Printer name
Example value: PRINTER
PRO
WBS element
Defines the WBS element The
work breakdown structure
(WBS) represents the
hierarchical organization of a
project. WBS elements are
the individual structural
elements in a work
breakdown structure Default
value for account assignment
when creating shopping cart
or lean purchase order.
PURCH_GRP
Purchasing group
Number of an organizational
unit that is indicated as local
purchasing group in the
organizational plan.
66
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
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 recipient
Indicates the organizational
Example value: See definition
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
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
67
to be maintained as follows:
<US><User ID of alternative
goods recipient>, for
example USMANAGER22.
Before you can order direct
materials, you must have
defined the necessary plants.
You use this attribute to
define these plants in the
organizational plan. You enter
plants as follows:
<type_BP><partner_number
_for_plant>, for example,
BP1195.
For the purposes of the direct
materials scenario the
business partner number (it
can have a maximum of ten
positions) defined in this
attribute must be linked to a
plant in table
CRMM_LOCMAP.
Buy on behalf of: To enable
substitute shopping you
enter all users for whom a
purchasing assistant can buy
on behalf of.
The values defined for the
attribute form the basis for
the F4 help for the Goods
Recipient field available to the
purchasing assistant or other
employee creating shopping
carts for other users in the
Shop scenario.
RESP_PRGRP
Purchasing group
Number of the organizational
responsible
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.
68
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
This attribute is simulated.
You define the product
responsibility of a purchasing
group on the Responsibility
tab.
ROLE
User role
Indicates the role of the user,
Example value: /SAPSRM/
for example manager,
EMPLOYEE
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
Defines the company logo to
logo
be used when purchase
orders or contracts are
output. The values are
determined using Smart
Forms on the basis of the
purchasing group. You define
the company logo using
transaction SO10.
SF_HEADER
SAP Smart Forms: Header
Defines the header to be used
Example value:
when purchase orders or
BBP_COMPANY
contracts are output. The
values are determined using
Smart Forms on the basis of
the purchasing group. You
define the header using the
transaction SE78.
SLAPPROVER
Spending limit approver
Specifies the approver used
Example value:
in workflows based on a
USMANAGER1
spending limit.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
69
SPEND_LIM
Spending limit
The value up to which a user
is allowed to spend before the
spending limit approval
workflow is triggered.
You define this attribute
using tab card Extended
attributes.
SYS
System alias
Defines the systems to be
Example value: ABCCLNT123
searched to find purchase
orders. This attribute is used
to generate worklists for
employees that create
confirmations or invoices
centrally. The attribute can
refer both to the local system
and back-end systems.
Generally, several values are
defined: The local systems
and various back-end
systems.
You must define the systems
in Customizing for SAP
Supplier Relationship
Management under
Server
Settings
SRM
Technical Basic
Define Basic
Settings.
TEND_TYPE
Transaction type: Bid
Specifies the transaction type
invitation
for bid invitations created
Example value: BID
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
Server
70
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
SRM
Cross-Application
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
Basic Settings
Define
Transaction Types.
TOG
Tolerance group
Defines the tolerance group.
Example value: CONF
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
Specifies the back-end
vendor
system where the account
Example value: ABCCLNT123
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
Server
Settings
SRM
Technical Basic
Define Basic
Settings.
VENDOR_SYS
System alias for vendor
Defines the systems to be
Example value: ABCCLNT123
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
Server
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
SRM
Technical Basic
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
71
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.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:
Table 14
Function
●
Companies
●
Purchasing
organizations
●
Responsibility
Note
For purchasing groups
only.
Purchasing groups
●
Product responsibility
Extended attributes
●
Product categories
●
Plants
●
Storage locations
●
Approval limits
Attributes
All other attributes
(for product groups)
●
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.
72
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
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
Management Create Organizational Plan
SRM Server
Cross-Application Settings
Organizational
Procedure
1.
See Customizing for SAP Supplier Relationship Management under SRM Server
Settings Organizational Management Change Organizational Plan .
Cross-Application
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.
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
73
○
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.
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
Settings Roles Maintain Attribute Access Rights by Role .
Cross-Application Basic
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:
74
○
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
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
○
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)
2.
○
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
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.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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
75
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.
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:
Table 15
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
76
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
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.
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
Data Create Users Import Users from File or from Other System .
8.2
8.2.1
SRM Server
Master
Roles
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:
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
77
●
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.
●
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
78
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
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
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:
Roles Define Roles
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
SRM Server
Cross-Application Basic Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
79
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.
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
Settings Roles Maintain Attribute Access Rights by Role .
Cross-Application Basic
For more information, see SAP Note 644124.
7.
Choose
Utilities
8.
Select All Roles
9.
Enter /SAPSRM/*
Mass generation
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
Settings Roles Maintain Attribute Access Rights by Role .
Cross-Application Basic
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:
80
○
Product categories: The product responsibilities have to be set on the tab card Extended Attributes
(attribute PRCAT).
○
Systems: ACS, SYS
○
Document types: BSA
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
○
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)
2.
○
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
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 help.sap.com
under SAP Supplier Relationship Management
SAP SRM 7.0 EHP4 Application Help SAP Library Business Packages Business Package for SAP Supplier
Relationship Management 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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
81
Procedure
Proceed as described in Customizing for SAP Supplier Relationship Management under SRM Server
Application Settings Organizational Management Integration Business Partner — Organizational
Management Set Up Integration with Organizational Management
8.3.2
Cross-
Scheduling Periodic Comparison
You need to check and update business partner addresses from organizational units at regular intervals to
prevent data inconsistencies.
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 CrossApplication 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
82
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Organizational Management
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 Basis Services Address Management Maintain Address and Person Number
Range .
●
Partner functions in Customizing for SAP Supplier Relationship Management
Application Basic Settings Define Partner Functions .
SRM Server
Cross-
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.
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Locations and Business Partners
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
83
Table 16
To retrieve all the location numbers from each back-end
BBP_LOCATIONS_GET_ALL
system that is connected
To retrieve all the location numbers from one particular back-
BBP_LOCATIONS_GET_FROM_SYSTEM
end system
To retrieve selected locations
BBP_LOCATIONS_GET_SELECTED
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 SAP SRM 7.0
EHP4 Application Help SAP Library 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
Table 17
Activity
84
Description
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
For more information, see:
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Locations and Business Partners
Defining address types
You must have specified the six address
Customizing for SAP SRM under
types shipped with SAP Enterprise
Server
Buyer, for example, goods recipient
Partner
(GOODS_REC).
Define Address Types
Assigning transactions to address types You must have assigned predefined
transactions to the address types you
Master Data
Manage Address Types
Customizing for SAP SRM under
Server
SRM
Business
Master Data
SRM
Business
created. There is a recommended set of
Partner Manage Address Types
assignments, including, for example, the Assign Transaction to Address Type
assignment of transaction Ship Goods
to the Ship-To address.
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
Settings Number Ranges and Groupings Define Number Ranges .
Business Partner
Basic
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
Settings Number Ranges and Groupings Define Groupings and Assign Number Ranges .
9.4
Basic
Locations and Business Partners
Specify Data Privacy Settings for Suppliers
Perform the following activities in Customizing for SAP SRM: SAP Supplier Relationship Management
Server Master Data Business Partner Specify Data Privacy Settings for Suppliers
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Locations and Business Partners
SRM
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
85
Define Partner Schema
Perform the following activities in Customizing for SAP SRM: SAP Supplier Relationship Management
Server Cross-Application Basic Settings Define Partner Schema
SRM
Check Locations
Run the following system transactions in SAP SRM: Application Log: Display Logs (SLG1)
86
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Locations and Business Partners
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Supplier Master Data Replication
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
87
10.1.3 More Information About Settings for Supplier
Synchronization
Make Global Settings
Perform the following Customizing activity in SAP SRM:
Supplier Synchronization Define Global Settings .
SRM Server
Technical Basic Settings
Settings for
Perform the following Customizing activity in SAP SRM: SRM Server Technical Basic Settings
Supplier Synchronization Define Settings for Each Backend System .
Settings for
Define Settings for Each Back-End System
Maintain Supplier Groups
Perform the following Customizing activity in SAP SRM:
●
SRM Server
Replication .
Technical Basic Settings
Settings for Supplier Synchronization
Notes on Supplier
●
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
Download from Marketplace
Settings for Supplier Synchronization
Information on Automatic
●
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:
88
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Supplier Master Data Replication
○
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.
○
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 51].
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Supplier Master Data Replication
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
89
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
Numbering Define Configurable Item Numbering Scheme
11.2
Configurable Item
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:
Table 18
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
‘‘
90
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
11.3
11.3.1
Output Actions and Format
Defining Actions for Document Output
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings
and Output Format Define Actions for Document Output
11.3.2
Set Output Actions
Condition-Dependent Document Output
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings
and Output Format Condition-Dependent Document Output
Set Output Actions
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
11.4.2
Attachments .
More Information About Hierarchies
Define Contract Hierarchies
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server
for Product Categories, Suppliers, and Contracts
Cross-Application Basic Settings
Activate Hierarchies
Define Product Category Hierarchies
Perform the following Customizing activities in SAP SRM:
●
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings
Hierarchies for Product Categories, Suppliers, and Contracts
Activate
●
SAP Supplier Relationship Management
Product Category Hierarchy
Adaptation of
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
SRM Server
Business Add-Ins
Master Data
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
91
Assign category hierarchies to applications in Customizing for Cross-Application Components under
Product Product Category Assign Category Hierarchies to Applications
SAP
Define Supplier Hierarchies
Perform the following Customizing activities in SAP SRM:
●
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings
Hierarchies for Product Categories, Suppliers, and Contracts
Activate
●
SAP Supplier Relationship Management
Hierarchy Types
Change Supplier
11.5
SRM Server
Business Add-Ins
Master Data
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.
92
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
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 CrossApplication 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.
For more information, see Customizing for SAP SRM 7.0 under
Settings Define Transaction Types .
11.5.2
SRM Server
Cross-Application Basic
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
SRM Server Number Ranges Define Number Ranges for Local Purchase Orders
Number Ranges
Assign Purchase Order Responses
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings
SRM Server Number Ranges Define Number Ranges for Purchase Order Response
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
Number Ranges
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
93
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
SRM Server Number Ranges Define Number Ranges for Local Invoices
Number Ranges
Assign Invoice Defaults
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings
SRM Server Number Ranges Define Number Ranges for Invoice Defaults
Number Ranges
Assign Purchasing Contracts
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings
SRM Server Number Ranges Define Number Ranges for Purchase Contracts
Number Ranges
11.6 Text Schema and Text Mapping
Define Text Types
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management
Define Text Types
SRM Server
Cross-Application Basic Settings
Text Schema
Cross-Application Basic Settings
Text Schema
Cross-Application Basic Settings
Text Schema
Define Text Schemas
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management
Define Text Schema
SRM Server
Define Fixed Values for Text Types
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management
Define Fixed Values for Texts
SRM Server
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.
94
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management
Mapping for Internal Texts
SRM Server
Cross-Application Basic Settings
Text Mapping
Text
Cross-Application Basic Settings
Text Mapping
Text
Cross-Application Basic Settings
Define Transaction
Text Mapping for Inbound and Outbound Texts
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management
Mapping for Inbound and Outbound Texts
11.7
SRM Server
Define Transaction Types
Perform the following Customizing activity in SAP SRM:
SAP Supplier Relationship Management
Types
SRM Server
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
95
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
Application Basic Settings Activate Extended Classic Scenario .
SRM Server
Cross-
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
Activate Extended Classic Scenario .
SRM Server
Business Add-Ins
Control Extended Classic Scenario
11.9 Business Workflow
11.9.1
Select Workflow Framework
Perform the following activity in Customizing for SAP SRM:
Business Workflow Select Workflow Framework .
11.9.2
11.9.2.1
SRM Server
Cross-Application Basic Settings
Process-Controlled Workflow
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 97].
Prerequisites
You have created your organizational structure at least down to departmental level. For more information, see
Creating the Organizational Plan [page 52].
96
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
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 79].
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 99] and the related documentation for SAP
NetWeaver 7.0 in SAP Help Portal at help.sap.com
Capability Application Platform by Key Capability
2.
SAP NetWeaver Library SAP NetWeaver by Key
Business Services SAP Business Workflow .
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.
For more information, see Business Rule Framework Settings [page 100] and SAP Library for SAP ERP
Central Component on SAP Help Portal at 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 103].
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
help.sap.com
under Technology Platform
Business Configuration Sets (BC-CUS) .
SAP NetWeaver
SAP NetWeaver <release>
Customizing
Features
BC Sets are available for the following business objects:
●
Shopping cart
●
Purchase order
●
Confirmation
●
Invoice
●
Contract
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
97
●
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.
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:
Table 19
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
/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
/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
/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
/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
Purchase order
Confirmation
Invoice
Contract
98
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
Quote
RFx
11.9.2.3
11.9.2.3.1
/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
/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
Define Technical Configuration
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
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
99
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 100] to define SAP SRM-specific events and expressions.
11.9.2.4
11.9.2.4.1
Define Settings for Business Rule Framework
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
help.sap.com
Enterprise Management SAP ERP SAP ERP 6.0 EHP8 SAP Library SAP ERP CrossApplication 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
Business Workflow Process-Controlled Workflow BRF Configuration .
Cross-Application Basic Settings
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 97].
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.
100
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
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
●
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 help.sap.com
Enterprise Management SAP ERP SAP ERP 6.0
EHP8 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 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 101].
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 103] 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 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-
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
101
Application Settings
Business Workflow
Framework
Define Expressions .
Process-Controlled Workflow
Define Settings for Business Rule
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:
1.
In the BRF Objects field, enter SRM_WF.
2.
Expand
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
Applicatn Class
SRM_WF
All Groups .
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:
○
○
102
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 (prefix 0C_C4_C_). The
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
103
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 service.sap.com/srm-inst
SAP SRM Server 7.0 Workflow Guide — SAP SRM 7.0 .
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 97].
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:
Table 20
104
Business Object
Task ID
Task Name
Contract (BUS2000113)
40007980
SRM Contract Approval
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
Business Object
Shopping cart (BUS 2121)
RFx (BUS2200)
Purchase order (BUS2201)
Supplier Quote (BUS2202)
Confirmation (BUS2203)
Invoice (BUS2205)
Automatic
Task ID
Task Name
40008003
Accept Decision / Adjust Document
40007997
Revise Document
40107926
Review Document
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
40107917
SRM RFx Completion
40007982
SRM RFx Approval
40107922
Accept Decision / Adjust Document
40007998
Revise Document
40107927
Review Document
40007973
SRM Purchase Order Completion
40007974
SRM Purchase Order Approval
40007995
Accept Decision / Adjust Document
40007996
Revise Document
40107924
Review Document
40007981
SRM RFx Response/Bid Approval
40007999
Revise Document
40107928
Review Document
40008000
SRM Bid Approval
40107934
Revise Bid
40107935
Review Bid
40007987
SRM Confirmation Approval
40008004
Revise Document
40107929
Review Document
40008005
SRM Invoice Approval
40008006
Revise Document
40107925
Review Document
40007988
Automatic Approval
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
105
Business Object
●
Task ID
Task Name
40007989
Automatic Rejection
Decision type:
○
Decision type 1: decision for entire document
○
Decision type 2: item-based decision for entire document
○
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 help.sap.com
SAP Supplier Relationship Management
SAP SRM 7.0 EHP4 Application Help SAP Library 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:
Table 21
Business Object
Process Level Type
Decision Types
Contract (BUS2000113)
Approval with Completion
Not applicable
Approval
1, 2
Approval with Completion
1, 2
Approval
1, 2, 3, 4
Approval with Completion
1
Approval
1
Approval with Completion
1, 2
Approval
1, 2
Approval with Completion
Not applicable
Approval
1
Approval with Completion
Not applicable
Approval
1
Approval with Completion
Not applicable
Approval
1
Shopping cart (BUS 2121)
RFx (BUS2200)
Purchase order (BUS2201)
Supplier Quote (BUS2202)
Confirmation (BUS2203)
Invoice (BUS2205)
●
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.
106
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
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
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
SAP Business Suite
implementations are based, see SAP Service Marketplace at service.sap.com/srm-inst
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
SAP Supplier Relationship Management SAP SRM 7.0
responsibility, see SAP Help Portal at help.sap.com
EHP4 Application Help SAP Library 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).
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
107
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:
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
●
SRM Server
Workflow
Cross-Application Basic Settings
Business Workflow
Activate Asynchronous Processing of
●
SRM Server Cross-Application Basic Settings
Overlapping Responsibility
Business Workflow
Activate Parallel Approval with
108
Activate Business Functions
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
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
●
Activate Sample BC Sets for Process Level Definition
The following Business Add-Ins are available in Customizing for SAP SRM under
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
SRM Server
Business Add-
Application-Controlled Workflow
11.9.3.1
Setting Up Business Workflow for ApplicationControlled 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 52].
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 79].
Procedure
Activate the specific workflows by activating the event linkage
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
109
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.
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):
Table 22
Business Object
Triggering Events
Workflows Belonging to Business
Event Linkage
Start
Object
(by Default)
Conditions
Activated
(by Default)
Activated
BUS2121
SAVED
(Shopping Cart)
WS10000060
No
No
No
No
No
No
No
No
No
No
Yes
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
(auto approval)
WS10000129
(one-step approval)
WS10000031
(two-step approval)
WS10000276
(spending limit approval)
WS14000044
(completion by purchaser)
BUS2201
SAVED/
WS14000075
(Purchase Order)
CHANGEVERSIONSAVED
(auto approval)
WS14000089
(one-step approval)
BUS2203
SAVED
(Confirmation)
WS10400002
(one-step approval)
WS10400009
(two-step approval)
WS10400010
(auto approval)
WS10400020
(administrator approval)
BUS2205
110
SAVED
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
WS10400016
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
(Invoice)
(auto approval)
WS10400017
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
Yes
No
No
No
Yes
No
No
No
(one-step approval)
WS10400018
(two-step approval)
WS10400021
(administrator approval)
BUS2000113
SAVED/
WS14000086
(Contract)
CHANGEVERSIONSAVED
(auto approval)
WS14000088
(one-step approval)
BUS2200
SAVED/
WS14500026
(RFx)
CHANGEVERSIONSAVED
(auto approval)
WS14500027
(one-step approval)
BUS2202
TOBEACCEPTED
(Supplier RFx
WS79000010
(auto approval)
Response)
WS79000002
(one-step approval)
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:
Table 23
Business Object
Triggering Events
(BO)
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
Workflow Template
Event Linkages
Start
(by Default)
Conditions
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
111
BUS2121
SAVED
(Shopping Cart)
WS14000109
Activated
Required
No
Yes (see note)
No
Yes (see note)
No
No
No
No
No
No
No
Yes (see note)
Yes
No
No
No
No
Yes (see note)
No
Yes (see note)
No
No
No
Yes (see note)
Yes
No
Yes
No
Yes
No
No
No
No
No
(n-step spending limit approval)
WS14500015
(line-item approval)
WS14000045
(delete SC item after application
error)
WS10000202
(transfer PM requisition)
WS10000215
(resubmit SC item by
administrator)
BUS2201
SAVED/
WS14000145
(Purchase Order)
CHANGEVERSIONSAVED
(n-step approval)
BUS2205
ERRORINVOICETOBEPROCE WS14500020
(Invoice)
SSED
(error correction)
BUS2000113
ALERTBUSINESSWAREHOU
WS10400022
(Contract)
SE
(contract alert)
SAVED/
WS14000148
CHANGEVERSIONSAVED
(n-step approval)
TOBEACCEPTED
WS14500044
BUS2202
(Supplier RFx
(n-step approval)
Response)
BUS2200
EXTERNALAUCTIONSTARTE WS14000091
(RFx)
D
(alert workflow)
SAVED/
WS14500028
CHANGEVERSIONSAVED
(n-step approval)
COMPLETED
WS14000043
BUS1006200
(Business Partner)
(auto approval)
WS14000030
(one-step approval)
WS14500021
(BP locked)
BBP_PCARD
APPROVECHARGES1
(Procurement Card)
(one-step approval)
APPROVECHARGES2
112
WS10000093
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
WS10000100
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
(two-step approval)
BUS2203
RETURN
(Confirmation)
WS10001048
No
No
(notify supplier of goods return)
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 .
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 ApplicationControlled 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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
113
4.
Click the link Assign Agents for this folder.
Note
For a complete list of mandatory workflows, see SAP Help Portal at 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
Table 24
Task
Used/Usable in Workflow
(Description)
TS10007947
Processor
(Type of Task Agent Assignment)
WS10000093
General task
WS10000265
General task
WS10000031
Manager role or general task
TS10008126
WS10000129
Manager role or general task
(approval task in one-step approval of SC)
WS10000276
TS10008127
WS10000031
Manager role or general task
WS10000265
Manager role or general task
WS10000271
Manager role or general task
TS10107914
WS10000031
General task
(present changes in SC to requestor)
WS10000060
TS10407914
WS10400002
Manager role or general task
WS10400009
Manager role or general task
WS10400011
Manager role or general task
WS10400008
Manager role or general task
WS10400014
Manager role or general task
WS10400015
Manager role or general task
(approve charges of P-Card)
TS10008061
(ask whether requester accepts rejection of SC)
TS10008069
(1st approval task in two-step approval of SC)
(2nd approval task in two-step approval of SC)
TS10008212
(check SC by reviewer)
TS10008214
(approval task to insert in approval of SC)
(approval task in one-step approval of GR)
TS10407915
(1st approval task in two-step approval of GR)
TS10407916
(check GR by reviewer)
TS10407917
(approval task to insert in approval of GR)
TS10407918
(approval task to insert in approval of INV)
TS10407919
114
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
(check INV by reviewer)
TS10407920
WS10400017
Manager role or general task
WS10400018
Manager role or general task
WS10400009
Manager role or general task
WS10400018
Manager role or general task
WS10400020
Administrator
WS10400021
Administrator
WS10400022
General task
TS10407972
WS10000031
General task
(change rejected SC)
WS10000060
TS14007938
WS10000060
(present changes to creator of SC)
WS10000129
(approval task in one-step approval of INV)
TS10407921
(1st approval task in two-step approval of INV)
TS10407922
(2nd approval task in two-step approval of GR)
TS10407923
(2nd approval task in two-step approval of INV)
TS10407924
(administrator approval task for GR)
TS10407925
(administrator approval task for INV)
TS10407926
(check CTR in alert workflow)
General task
WS10000031
WS10000276
WS14000044
WS14000109
WS14500015
TS14007947
WS14000044
General task
WS14000088
Manager role or general task
WS14000089
Manager role or general task
WS14000002
Manager role or general task
WS14000154
Manager role or general task
WS14000145
General task
(completion task of SC)
TS14007969
(approval task in one-step approval of CTR)
TS14007970
(approval task in one-step approval of PO)
TS14008026
(approval task to insert in approval of PO)
TS14008027
(check PO by reviewer)
TS14008028
(send PO back to purchaser)
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
115
TS14507918
WS14000148
General task
WS14500008
Manager role or general task
WS14500010
Manager role or general task
WS14500027
Manager role or general task
WS14500022
Manager role or general task
WS14500023
Manager role or general task
WS14500028
General task
WS14500040
Manager role or general task
WS14500041
Manager role or general task
WS14500044
Manager role or general task
WS14500044
General task
WS14500020
Administrator
WS79000002
Manager role
(Send contract back to creator)
TS14507919
(check contract by reviewer)
TS14507920
(approval task to insert in approval of CTR)
TS14507922
(approval task in one-step approval of RFx)
TS14507924
(approval task to insert in approval of RFx)
TS14507925
(check RFx by reviewer)
TS14507928
(Send RFx back to creator)
TS14507930
(approval task to insert in approval of RFx
response)
TS14507931
(check contract by reviewer)
TS14507935
(approval task in n-level approval of RFx
response)
TS14507937
(send RFx response back to creator)
TS14508056
(correct erroneous invoice)
TS79007914
(approval task in one-step approval of RFx
response)
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.
116
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
●
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
●
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).
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
117
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 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 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
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
118
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
SRM Server
Business Add-
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
●
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
Business Workflow Universal Worklist Object Visualization .
Cross-Application Basic Settings
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 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
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
119
(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
Alerts/Messages, and Events in SRM Alert Management .
SRM Server
Business Add-Ins
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:
●
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.
●
120
External tax system (Vertex® or Taxware®)
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
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 .
Prerequisites
Settings for Tax Calculation
Table 25
Setting
Define the system for tax calculation.
Customizing path
SAP Supplier Relationship Management
Cross-Application Basic Settings
SRM Server
Tax Calculation
Determine System for Tax Calculation
Define the allowed invoice verification tolerances for the
variances between calculated tax amounts and tax amounts
SAP Supplier Relationship Management
Cross-Application Basic Settings
SRM Server
Set Tolerance Checks
entered manually (optional).
Define whether taxes for the total freight costs (that is, for
SAP Supplier Relationship Management
all company codes) are to be calculated with a separate tax
Cross-Application Basic Settings
code (optional).
Tax Calculation for Freight Costs
Define whether taxes for freight costs for specific company
Business Add-Ins
(optional).
Freight Costs
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
Tax Calculation
SAP Supplier Relationship Management
codes are to be calculated with a separate tax code
SRM Server
Tax Calculation
Define
SRM Server
Calculate Tax for
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
121
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:
Table 26
Setting
Customizing path
You can maintain tax codes.
SAP Supplier Relationship Management
Cross-Application Basic Settings
SRM Server
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
Cross-Application Basic Settings
SRM Server
Tax Calculation
Assign
Enterprise Buyer Tax Code to FI System
You can use individual tax code determination.
SAP Supplier Relationship Management
Business Add-Ins
You can change or supplement the data used to calculate tax
depending on the system selected for tax calculation.
(optional).
Determine Tax Code
SAP Supplier Relationship Management
Business Add-Ins
You can specify a tax code for country and product category
Tax Calculation
Tax Calculation
SRM Server
Change Tax Data
SAP Supplier Relationship Management
Cross-Application Basic Settings
SRM Server
SRM Server
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
Technical Basic Settings Define Backend Systems .
SRM Server
Required entries:
●
Logical system, for example VERTEX
●
Name, for example VERTEX
●
Destination, for example EXT_DEST
●
System type: Tax external system
122
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
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).
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
3.
SRM Server
Technical Basic Settings
Define RFC Destinations .
Define the back-end system in Customizing for SAP Supplier Relationship Management under
Server Technical Basic Settings Define Backend Systems .
SRM
Required entries:
4.
○
Logical system, for example VERTEX
○
Name, for example VERTEX
○
Destination, for example EXT_DEST
○
System type: Tax external system
Edit the business partners.
1.
In the SAP Easy Access menu, choose
2.
Enter the business partner (BusPartner), for example, the company that the goods are to be delivered to.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
Master Data
Business Partner
Process Business Partner .
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
123
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.
4.
5.
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
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
Edit all products that are to be checked.
1.
In the SAP Easy Access menu choose
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
Master Data
Products
Process Products .
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.
124
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
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
Cross-Application Basic Settings Tax Calculation Activate Withholding Tax .
SRM Server
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:
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
Account
the SAP SRM categories by choosing SRM Server Cross-Application Basic Settings
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
Account Assignment
Supplier Relationship Management under SRM Server Business Add-Ins
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
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
125
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
Account
Customizing for SAP Supplier Relationship Management under SRM Server Business Add-Ins
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.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).
126
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
For more information, see Customizing for SAP Supplier Relationship Management under
Application Basic Settings Create Payment Conditions .
SRM Server
Cross-
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.14 Create Incoterms
Go to Customizing for SAP Supplier Relationship Management under
Settings Create Incoterms .
SRM Server
Cross-Application Basic
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
127
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
●
1540489
— Technical information for the VMC based AP 7.00 engines
— Customized condition type not considered in pricing
Set General Configuration Parameters
Perform the following activity in Customizing for SAP SRM:
Time Zones Maintain System Settings
SAP Web Application Server
General settings
Process Condition Types
Perform the following activity in Customizing for SAP SRM:
Pricing Process Condition Types
SRM Server
Cross-Application Basic Settings
SRM Server
Cross-Application Basic Settings
SRM Server
Cross-Application Basic Settings
Edit Calculation Schema
Perform the following activity in Customizing for SAP SRM:
Pricing Process Calculation Schema
Process Condition Group
Perform the following activity in Customizing for SAP SRM:
Pricing Process Condition Groups
Check Technical and Customizing Settings for Conditions
Perform the following activity in Customizing for SAP SRM: SRM Server
Pricing Check Technical and Customizing Settings for Conditions
Cross-Application Basic Settings
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.
128
Access the activity using the following navigation options:
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
Table 27
Customizing Path
SAP Supplier Relationship Management
Server
Cross-Application Basic Settings
SRM
Define
Objects in Backend System (Purch. Reqs, Reservations,
Purch. Orders)
Transaction Code
SPRO
2.
Choose New Entries.
3.
Make the following entries (Example):
Table 28
Purchasing Grp.
Category ID
Source System
Int. Proc.
External
Procurement
<system
Choose Option
Choose option
you have defined
name>CLNT<client
'Reservn generated if
‘Purchase order if
(Example 50000056)
number>
stock available,
item data complete
otherwise ext. proc.'
else purch. req.’
Purchasing groups
4.
*
○
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.
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.
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
129
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
Settings Define Settings for Attachments .
SRM Server
Cross-Application Basic
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
Order in Backend System .
Follow-On Document Generation in the Backend System
Purchase
●
SRM Server Business Add-Ins
Requisition in Backend System .
Follow-On Document Generation in the Backend System
Purchase
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.
2.
Double-click in the detail view to define the new Doc. type desc. = SRM Documents. Set the Use KPro
indicator.
130
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
○
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.
○
3.
In the screen area Field selection, enter – in the Document Status field.
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
Server Cross-Application Basic Settings Define Settings for Attachments
SRM
11.18 Start Application Monitors
Perform the following activity in Customizing for SAP SRM:
Start Application Monitors .
SRM Server
Cross-Application Basic Settings
11.19 Message Control
Perform the following activities in Customizing for SAP SRM under
Settings Message Control :
●
SRM Server
Cross-Application Basic
Influence Message Control
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
131
●
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
SRM Server
Cross-Application Basic Settings
Background Processing
Activate/Deactivate Advanced
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
●
SAP Supplier Relationship Management
132
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
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
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 (BCSRV-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 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 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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
133
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.
134
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
11.21.1.5 More Information About Settings for SAP Records
Management
Perform the following activity in Customizing for SAP NetWeaver: Application Server
Application Link Enabling (ALE) Communication Create RFC Connections .
IDoc Interface /
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
135
5.
Assign Logical System to Client
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
with SAP Records Management Activate Integration with SAP Records Management
Integration
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
SAP Records Management Define Transfer Conditions for Records Management
Integration with
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
with SAP Records Management Define Integration Scenarios
Integration
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.
Result
You have now connected the SAP SRM system to the SAP RM system and enabled the creation of records for
purchasing documents.
136
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
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
Systems Define Logical Systems
ALE Settings
Distribution (ALE)
Basic Settings
●
SRM Server
Connections
ALE Settings
Distribution (ALE)
Communication
Technical Basic Settings
Logical
Create RFC
Perform the following activity in Customizing for SAP Web Application Server:
●
Application Server
Repositories
Basis Services
Knowledge Provider
Content Management Service
Define Content
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
●
SRM Server
Innovations
Cross-Application Basic Settings
Service Procurement
Activate Service Procurement
●
SRM Server Cross-Application Basic Settings
in Back-End System
Service Procurement
Define Status for Purchase Orders
Activate Business Functions
11.21.2.2 More Information About Contract Limits
Perform the following activities in Customizing for SAP Supplier Relationship Management under:
●
SRM Server
●
SRM Server
Innovations
Activate Business Functions
Cross-Application Basic Settings
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
Service Procurement
Activate Service Procurement
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
137
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
SAP ERP Activate Linking to SAP ERP Documents
Integration with
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
Integration Activate/Deactivate Catalog Integration Using ABAP FTP
Catalog
●
SRM Server Cross-Application Basic Settings
Integration Define FTP Servers
Integration with Other SAP Components
Catalog
●
SRM Server Cross-Application Basic Settings
Integration Define FTP Files
Integration with Other SAP Components
Catalog
11.22 Digital Signatures
Perform the following activity in Customizing for SAP SRM:
Digital Signature Activate Digital Signatures .
SRM Server
The following Business Add-In is available in Customizing for SAP SRM:
Signature Define Customer-Specific Document Preview .
Cross-Application Basic Settings
SRM Server
Business Add-Ins
Digital
11.23 User Experience
Perform the following activities in Customizing for SAP Supplier Relationship Management (SAP SRM):
●
SRM Server
●
SRM Server
Redesign
Cross-Application Basic Settings
User Experience
Activate Keyboard Navigation
●
SRM Server Cross-Application Basic Settings
Transaction Type Selection
User Experience
Activate/Deactivate Dropdown for
Activate Business Functions
●
SRM Server
Cross-Application Basic Settings
User Experience
Activate/Deactivate Progress Bar
●
SRM Server
Cross-Application Basic Settings
User Experience
Activate/Deactivate Browse Mode
138
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
●
SRM Server
Documents
Cross-Application Basic Settings
User Experience
Define Threshold Values for Large
●
SRM Server
Fields
Cross-Application Basic Settings
User Experience
Activate/Deactivate Mandatory
11.24 POWL and Advanced Search
Perform the following activities in Customizing for SAP SRM under
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
SRM Server
Cross-Application Basic
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
Control for Purchasing Documents
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
SRM Server
Cross-Application Basic Settings
Switch on Version
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
139
11.28 Define Status Schema
11.28.1 More Information About Defining Status Schema
Perform the following Customizing activities in SAP SRM:
SAP Supplier Relationship Management
Schema for User Status
SRM Server
Cross-Application Basic Settings
Define 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.30 Activate/Deactivate Automatic Enlargement of Long
Text Boxes
Perform the following activity in Customizing for Supplier Relationship Management (SAP SRM):
SRM Server
boxes
Cross Application Basic Settings
Activate/Deactivate Automatic enlargement of Long Text
11.31 Activate/Deactivate Purchase Order Header Condition
Perform the following activity in Customizing for Supplier Relationship Management (SAP SRM):
SRM Server
Cross Application Basic Settings
Activate/Deactivate Purchase Order Header Condition
11.32 Activate/Deactivate Central Substitution
Perform the following activity in Customizing for Supplier Relationship Management (SAP SRM) under:
Server Cross Application Basic Settings Activate/Central Substitution
140
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
SRM
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Cross-Application Settings
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:
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Component Planning
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
141
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:
142
○
Purchasing group
○
Purchasing organization
○
Material group
○
G/L account
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Component Planning
○
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.
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Component Planning
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
143
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:
Table 29
Function
●
Companies
●
Purchasing
organizations
●
Responsibility
Note
For purchasing groups
only.
Purchasing groups
●
Product responsibility
Extended attributes
●
Product categories
●
Plants
●
Storage locations
●
Approval limits
Attributes
All other attributes
(for product groups)
●
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.
144
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Component Planning
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
Management Create Organizational Plan
SRM Server
Cross-Application Settings
Organizational
Procedure
1.
See Customizing for SAP Supplier Relationship Management under SRM Server
Settings Organizational Management Change Organizational Plan .
Cross-Application
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.
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.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Component Planning
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
145
○
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.
146
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Component Planning
Typographic Conventions
Table 30
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
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
Example
Hyperlink to an SAP Note, for example, SAP Note 123456
●
Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
Example
●
Cross-references to other documentation or published works
●
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
Basic Settings for SAP Enhancement Package 4 for SAP SRM 7.0
Typographic Conventions
CUSTOMER
© Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.
147
www.sap.com
© Copyright 2015 SAP SE or an SAP affiliate company. All rights
reserved.
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies. Please see
www.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising