EHP3 for SAP SRM
7.0
EHP7 for SAP ERP
6.0
October 2014
English
Generic Configuration
Settings (SRM@ERP)
(S03)
Building Block Configuration Guide
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
© SAP SE
Page 2 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Copyright
© 2014 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. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting
an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated
companies’ strategy and possible future developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any
time for any reason without notice. The information in this document is not a commitment, promise, or
legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject
to various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.
© SAP SE
Page 3 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths, and
options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade, and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
© SAP SE
Page 4 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Content
1
Purpose ................................................................................................................. 8
2
Preparation ............................................................................................................ 8
2.1
3
Prerequisites ......................................................................................................... 8
Back-end integration ............................................................................................. 8
3.1
Define System Landscape .................................................................................... 8
3.2
Define Number Ranges......................................................................................... 9
3.2.1
3.3
Define Number Ranges for Supplier List
9
ALE Settings ....................................................................................................... 10
3.3.1
Activate Change Pointers Generally
10
3.3.2
Create ALE Distribution Model
10
3.3.3
Define Partner Profile – Outbound
12
3.3.4
Define Partner Profile - Inbound
13
3.3.5
Maintain Port
14
3.4
Configuration of Product Data ............................................................................. 15
3.4.1
Set Material Number Display
15
3.4.2
Define Output Format and Storage Format of Product IDs
15
3.4.3
Specify Number Assignment Settings for Product Type
16
3.4.4
Maintain Table TBLSYSDEST
16
3.5
Purchasing Document Settings ........................................................................... 16
3.5.1
Determine System for Tax Calculation
16
3.5.2
Enter Tax Code
17
3.5.3
Version Control for Purchasing Documents
18
3.6
Configuration of Organizational Model ................................................................ 18
3.6.1
CREATE BP for Root Organization
18
3.6.2
Create Package Z001
19
3.6.3
Assign and Activate User Exit for ORG Number Range
19
3.6.4
Create Include ZXHIVU01
20
3.6.5
T77S0 SWITCH OFF
20
3.6.6
CREATE REPORT Z_SMBSRM_CREATE_ORG
21
3.6.7
Manual Upload of ORG Model Template
22
3.6.8
Execute Report RHSOBJCH
22
3.6.9
Maintain Company, Purchasing Organization, and Purchasing Group
23
3.6.10 Maintain the Responsibilities for Purchasing Group
24
3.6.11 Replicate Locations from ERP Backends
24
3.6.12 Creation of Positions in Organizational Structure
25
3.6.13 Maintenance of ORG Attributes
26
© SAP SE
Page 5 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.6.14 Organizational Model: Set Attributes for Delivery Address
28
3.6.15 T77S0 SWITCH OFF
28
3.6.16 Creation of HR Users
29
3.6.16.1 Creation of Transaction Z_PASRM ............................................................... 29
3.6.16.2 Create Transaction Z_PASRM ...................................................................... 30
3.6.16.3 Creating HR Users (Using Transaction Z_PASRM) ...................................... 31
3.6.17 Set Up Integration with Organizational Management
33
3.6.18 Maintain Purchaser User
33
3.7
Configuration of Supplier Data ............................................................................ 34
3.7.1
Create Supplier Groups (Supplier Root)
34
3.7.2
Maintain Table BBP_MARKETP_INFO
34
3.7.3
Upload Payment Terms
35
3.7.4
Upload QM Systems
35
3.8
Define External Web Services ............................................................................ 35
3.8.1
Define External Catalog and Call Structure for Catalog Integration
35
3.8.2
Maintain Description of Web Service
37
3.9
Configuration of Middleware Data ....................................................................... 37
3.9.1
Set Control Parameters
37
3.9.2
Job Processing
38
3.9.2.1
Create Variant for Report BBP_GET_STATUS_2 ......................................... 38
3.9.2.2
Create Variant for Report CLEAN_REQREQ_UP ......................................... 38
3.9.2.3
Create Variant for Report HRALXSYNC ........................................................ 38
3.9.2.4
Schedule Report BBP_GET_STATUS_2 ...................................................... 40
3.9.2.5
Schedule Report CLEAN_REQREQ_UP ...................................................... 40
3.9.2.6
Schedule Report RSPPFPROCESS ............................................................ 41
3.9.2.7
Match up Organizational Units and Persons with Business Partners ........... 41
3.9.2.8
Schedule Periodic Comparison (HRALXSYNC) ............................................ 42
3.9.3
Determining FMs for Data Exchange: BP
42
3.9.4
Activate Synchronization Options
43
3.9.5
Activate/De-activate Synchronization (Material to Product)
44
3.9.6
Maintain Post Processing Orders (PPO) Settings
45
3.9.6.1
Activation of the Forward Error Handling (FEH) ............................................ 45
3.9.6.2
Delete Logical Systems for Post Processing Office ...................................... 45
3.9.6.3
Activate Creation of Post Processing Orders ................................................ 46
3.9.6.4
Activation of PPO Requests for Platform Objects ......................................... 47
3.9.6.5
Reactivate Post Processing Orders (PPO) .................................................... 47
3.10
Basic Workflow Settings...................................................................................... 47
3.10.1 Maintain Standard Setting for SAP Business Workflow
47
3.10.2 Generalize Dependant Tasks
48
© SAP SE
Page 6 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.10.3 Event Type Linkages for Workflow
48
3.10.4 Copy BRF Objects
49
3.11
Master Data Synchronization .............................................................................. 50
3.11.1 Execution of Essential SRM Reports
50
3.11.1.1 Reports Registration ...................................................................................... 50
3.11.1.2 Report Run – COM_HIERARCHY_DELETE_ALL ........................................ 51
3.11.1.3 Report Run – COM_PRODUCT_DELETE_ALL ............................................ 51
3.11.1.4 Report Run – COM_PRODUCT_UPGRADE ................................................ 52
3.11.2 Initial Replication
52
3.11.2.1 Initial Replication of Customizing Comparison: Product ................................ 52
3.11.2.2 Initial Replication of Material Type ................................................................. 52
3.11.2.3 Initial Replication of Material Group ............................................................... 53
3.11.3 Write Description ‘Product’ into the Product Numbering Scheme
54
3.11.3.1 Initial Replication of Material Data ................................................................. 54
3.11.3.2 T77S0 SWITCH OFF ..................................................................................... 55
3.11.3.3 Initial Replication of Vendor Data .................................................................. 55
3.12
Maintain Attributes for EBP Company ................................................................ 56
3.12.1 T77S0 SWITCH OFF
56
3.12.2 Maintain Extended Attributes for EBP Company
57
3.12.3 Maintain Details for Positions
58
3.13
Back-end system for Product Category / Accounting Data ................................. 59
3.13.1 Define Back-end System for Product Categories
59
3.13.2 Define G/L Account and Account Assignment for Product Categories
60
3.14
Maintain the Vendor Business Partner ............................................................... 61
3.15
Client-Specific Configuration Parameters ........................................................... 62
3.16
Initial Run of Report HRALXSYNC ..................................................................... 63
© SAP SE
Page 7 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Generic Configuration Settings (SRM@ERP)
1 Purpose
This configuration guide provides the information that you need to set up the configuration of
this building block manually.
If you do not want to configure the building block manually and prefer to use an automated
installation process using BC Sets and other tools, refer to the SAP Best Practices Quick
Guide.
If you use PERSONALIZED values (for example, company code 9999 instead of the
default value company code 1000, or shipping point 8888 instead of default value
shipping point 1000, and so on), replace the DEFAULT values in the descriptions below
with your personalized values.
2 Preparation
2.1 Prerequisites
Before you start implementing the customizing steps described in this configuration guide
check if Building Block S00 is implemented.
3 Back-end integration
3.1 Define System Landscape
Use
The purpose of this activity is to define the system landscape (Table BBP_BACKEND_DEST
and BBP_BACKEND_TEXT).
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → Technical
Basic Settings → Define System Landscape
Transaction Code
SPRO
2. Choose New Entries.
3. Enter the following data:
Logical system
Description
RFC Destination
Sys. Type
<system-name>CLNT
<client-number>
<systemname>CLNT <clientnumber>
<system-name>CLNT
<client-number>
LOCAL
ONECLNTEBP
One Client EBP
<system-name>CLNT
<client-number>
EBP_ONE
© SAP SE
Page 8 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
ONECLNTERP
One Client ERP
<system-name>CLNT
<client-number>
ERP_3.0
Continuation of table:
RFC
Local
X
X
FI valid
System Landscape
Directory Name
RFC (Dialog)
Real time …
SRM_SERVER_<systemname>_<client-number>
<systemname>CLNT <clientnumber>
Real time …
SRM_SERVER_<systemname>_<client-number>
<systemname>CLNT <clientnumber>
Real time …
SRM_SERVER_<systemname>_<client-number>
<systemname>CLNT <clientnumber>
4. Choose Save (Ctrl+S).
5. Choose Back (F3).
3.2 Define Number Ranges
3.2.1 Define Number Ranges for Supplier List
Use
The purpose of this activity is to maintain number ranges for the supplier list.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → CrossApplication Basic Settings → Number Ranges → SRM Server
Number Ranges → Define Number Ranges for Supplier List
Transaction Code
SPRO
2. Choose Change Intervals.
3. Choose Insert Interval (Shift + F1) and maintain the following entries:
NO
From Number
To Number
01
1000000000
1999999999
02
2000000000
2999999999
© SAP SE
Current
Number
Ext
Description
(not in the table)
X
Page 9 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
4. Choose Enter.
5. Choose Save (Ctrl+S).
3.3 ALE Settings
3.3.1 Activate Change Pointers Generally
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
BD61
or
IMG Path
Supplier Relationship Management → SRM Server → Technical
Basic Settings → ALE Settings (Logical System) → Distribution
(ALE) → Modeling and Implementing Business Processes →
Master Data Distribution → Replication of Modified Data →
Activate Change Pointers – Generally
Transaction Code
SPRO
2. Select theChange Pointers Activated – Generally checkbox.
3. Choose Save.
3.3.2 Create ALE Distribution Model
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
BD64
2. Switch to edit mode (F9).
3. Choose the Create model view button. A dialog box appears.
4. Enter a short text related to the local SRM client (for example, EBP_RDECLNT002).
5. Enter a technical name (for example, EBP_RDE002).
6. Choose Continue (Enter).
7. Choose the newly created entry on the screen.
In case of non-BAPI based message types (e.g. ACLPAY), carry out the following steps for
message type:
8. Choose the Add message type button and make the following entries in the dialog box:
Field Name
User Action and Values
Sender
Enter the logical destination of the SRM client, which is
<system-name>CLNT <client-number>, for example: RDECLNT002
Receiver
© SAP SE
Enter the logical destination of the back end client, for example:
ONECLNTERP
Page 10 of 63
SAP Best Practices
Message Type
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
ACLPAY
9. Choose Continue (Enter).
10. Repeat steps 8 to 9 to add message types BBPCO and BBPIV.
In case of BAPI-based message types (e.g. MBGMCR) the following steps are performed:
11. Select the distribution model and choose the Add BAPI button and make the following
entries in the dialog box:
Field Name
User Action and Values
Sender/client
Enter the logical destination of the SRM
client,
<system-name>CLNT <client-number>,
for example: RDECLNT002
Receiver/server
Enter the logical destination of the back
end client,
for example: ONECLNTERP
Obj. name/interface
Enter BAPI name GoodsMovement
Method
Enter BAPI method CreateFromData
Message-Type MBGMCR
is used
12. Choose Continue (Enter).
13. Repeat steps 11 to 12 for the following data:
Field Name
User Action and Values
Sender/client
Enter the logical destination of the
SRM client,
<system-name>CLNT <clientnumber>,
for example: RDECLNT002
Receiver/server
Enter the logical destination of the
back end client,
for example, ONECLNTERP
Obj. name/interface
Enter BAPI name
AcctngGoodsMovement
Method
Enter BAPI method Post
Message-Type
ACC_GOODS_MOVEMENT
is used
For BAPI- and non-BAPI based message types, the changes finally have to be saved:
14. Choose Save (CTRL+S).
© SAP SE
Page 11 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.3.3 Define Partner Profile – Outbound
Use
Generate the partner profiles with the transaction BD64 and create the missing outbound
parameters for partner type logical system ONECLNTERP and message type MBGMCR with the
transaction WE20
Procedure
1. Access the activity using the following navigation option:
Transaction code
BD64
2. Select distribution model EBP_<system ID><client number> (for example, BP_RDE002).
3. Access the activity using the following navigation:
Environment → Generate Partner Profiles
SAP menu
4. Select <Sys-ID>CLNT<Client> (SRM System) as the Model View.
5. Select ONECLNTERP (ERP Backend) as the Partner System.
6. Verify 3 as the Version.
7. Verify Transfer IDoc immediately as the Output Mode.
8. Choose Execute.
9. Select Back twice.
10. Access the following transaction choosing one of the following navigation options:
SAP ECC Menu
Tools → ALE → Runtime Settings → ALE Administration →
Runtime Settings → Partner Profiles
Transaction Code
WE20
11. In the left frame, select the line Partner Type LS and choose Create. This will open empty
fields on the right frame. Enter the following data:
Field Name
Description
User Action and Values
Comment
Partner No.
ONECLNTERP
Partn.Type
LS
Logical system
Ty.
US
User
Agent
<your user account>
Lang.
EN
English
12. Choose Create Outbound Parameter and enter the following data:
Field Name
Message Type
Description
User Action and Values
Comment
MBGMCR
Outbound options
Receiver port
<A00000000x>
Pack. Size
1
© SAP SE
Transactional RFC port
for OneClient
Page 12 of 63
SAP Best Practices
Field Name
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Description
User Action and Values
Transfer IDoc
immediately
Switch on
Basic type
MBGMCR01
Cancel
Processing after
Syntax error
Comment
SwithchOFF
Post Processing: Permitted Agent
Type
US
Agent
<your user account>
Language
EN
13. Save your entries.
3.3.4 Define Partner Profile - Inbound
Use
Create the missing inbound parameters for the partner type logical system <name of logical
system> and message type MBGMCR and BBPIV.
Procedure
1. Access the transaction choosing one of the following navigation options:
SAP ECC Menu
Tools → ALE → Runtime Settings → ALE Administration →
Runtime Settings → Partner Profiles
Transaction Code
WE20
2. In the left frame, mark the line Partner Type LS and choose Create. This will open empty
fields on the right frame. Enter the following data:
Field Name
Description
Partner No.
User Action and Values
Comment
<name of logical system>
Value from table T000
for the client
<system-name>CLNT <clientnumber>
Partn.Type
LS
Logical system
Ty.
US
User
Agent
<your user account>
Lang.
EN
English
3. Choose Create Inbound Parameter and enter the following data (repeat this for both
message types):
Field Name
Message Type
Description
User Action and Values
User Action and Values
MBGMCR
BBPIV
BAPI
IV01
Inbound options
Process Code
© SAP SE
Page 13 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Trigger
immediately
X
X
SwitchOFF
SwitchOFF
Type
US
US
Agent
<your user account>
<your user account>
Language
EN
EN
Cancel
Processing after
Syntax error
Post Processing: Permitted Agent
4. Save your entries
3.3.5 Maintain Port
Use
In this step you create a new port. In case you are would like to use an existing port as well as
setup the SRM scenarios in several clients (parallelly in one system), you have to change an
existing RFC destination for the Transactional RFC Port.
Procedure
1. Access the activity using one of the following navigation options:
SAP ECC Menu
Tools → ALE → Runtime Settings → ALE Administration →
Runtime Settings → Port Maintenance
Transaction Code
WE21
2. In case you are going to reuse an existing port, search for the Transactional RFC Port
with description.
3. Select the port and check and maintain the RFC destination:
Old value
New value
Comment
for example:
ONECLNTERP, or
your own RFC data.
<system-name>CLNT <client-number>,
Check if the RFC can be
reused.
for example: RDECLNT002
4. Choose Save (CTRL+S). Confirm any dialog boxes by choosing Yes.
5. If you create a new port, select the Transactional RFC node and choose Create. Let the
system generate a port name or define your own port name.
6. Maintain the Port Description and enter the RFC destination for your client <systemname>CLNT <client-number>, for example: RDECLNT002.
7. Choose Save (CTRL+S). Confirm any dialog boxes by choosing Yes.
© SAP SE
Page 14 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.4 Configuration of Product Data
3.4.1 Set Material Number Display
Use
Conversion settings on Material Number (ERP) are transferred to Product ID (SRM). Both
settings have to be in sync.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
OMSL
or
IMG Path
Logistics – General → Material Master → Basic Settings →
Define Output Format of Material Numbers
Transaction Code
SPRO
2. Check the data on Material Numbers Conversion.
3.4.2 Define Output Format and Storage Format of Product
IDs
Use
The data for converting the Product ID is transferred from Material Numbers Conversion.
Specify the Product ID length.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
COMCPRFORMAT
or
IMG Path
Cross-Application Components → SAP Product → Basic
Settings → Define Output Format and Storage Format of
Product IDs
Transaction Code
SPRO
2. On the Change View “Data for Converting the Product ID”: Details screen, make the
following entry:
Field Name
User Action and Values
Prod. ID Length
18
3. Choose Save.
© SAP SE
Page 15 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.4.3 Specify Number Assignment Settings for Product Type
Procedure
1. Access the activity using the following navigation options:
IMG Path
Cross-application components → SAP Product → Settings for
Product Type → Number Assignment → Specify Number
Assignment Settings
Transaction Code
SPRO
2. Select the entry Material on the left-hand side.
3. Choose Details (CTRL+SHFT+F2).
4. Choose the entry Alphanumeric IDs Are Not Checked Against Number Ranges from the
dropdown list of the ExternalNumberAssgmt field.
5. Carry out the same steps for the Service object.
3.4.4 Maintain Table TBLSYSDEST
Procedure
1. Access the activity using the following navigation option:
SAP menu
Tools → ABAP Workbench → Overview → Data Browser
Transaction Code
SE16
2. Maintain the logical system data of the related ERP client as follows:
Field
Value
MANDT
<client-number>
LOGSYS
<system-name>CLNT <client-number>
RFCDEST
<system-name>CLNT <client-number>
DIALOGDEST
3.5 Purchasing Document Settings
3.5.1 Determine System for Tax Calculation
Use
The purpose of this activity is to define the system for tax calculation.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → CrossApplication Basic Settings → Tax Calculation → Determine
system for Tax calculation
Transaction Code
SPRO
© SAP SE
Page 16 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
2. Choose the required option.
3. Choose Save (Ctrl+S).
4. Choose Back (F3).
The default configuration is No Tax Calculation. To change it, replace it manually.
Transaction Code
SM30
In the table BBP_TAX_DEST, select the tax calculation system Tax Calculation
Occurs in Backend via radio button and save the change.
3.5.2 Enter Tax Code
Use
The purpose of this activity is to define the tax codes.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → CrossApplication Basic Settings → Tax Calculation → Enter Tax code
Transaction Code
SPRO
2. Enter the necessary tax codes, which you have used for procurement.
3. Choose Save (Ctrl+S).
4. Choose Back (F3).
The default configuration is the tax code P0 (No Tax). Depending on your system
setup, you must include the other tax codes manually or even replace the default
one.
Transaction Code
SM30
Maintain table BBP_TAX as shown here:
© SAP SE
Tax ind.
Tax descript.
No tax
I0
I0 without tax
selected
I1
I1 with tax
V0
V0 without tax
V1
V1 with tax
V2
V2 with tax
VN
VN without tax
Default
Tax category
Sales Tax
selected
Selected
selected
Page 17 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.5.3 Version Control for Purchasing Documents
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → CrossApplication Basic Settings → Switch On Version Control for
Purchasing Documents
Transaction Code
SPRO
2. On the Change View Version Control for Documents: Overview screen, choose New
Entries.
3. Add active entries for contract, bid invitation, bid, purchase order, quotation, invoice, and
auction by choosing the following business transaction categories from the dropdown box
and selecting the activation checkbox for each entry:
Table: BBP_CT_VERSION
Business Transaction Category
Comment: Business Transaction Cat. - Table:
BBP_CT_VERSION
Contract
BUS2000113 Contract
RFx
BUS2200 RFx
Purchase Order
BUS2201 Purchase Order
RFx Response
BUS2202 RFx Response
Invoice
BUS2205 Invoice
Auction
BUS2208 Auction
4. Choose Save.
3.6 Configuration of Organizational Model
3.6.1 CREATE BP for Root Organization
Procedure
1. Access the activity using the following navigation option in the SAP SRM system:
Transaction Code
BP
2. Choose Organization
3. On the Basic Data tab page, enter EBP Root both in Organizational Unit fields.
4. Select the Address tab page and maintain the fields as in the following table:
Field
Entry Value
Title
Company
Name
<Company>
House no/street
<Street>
© SAP SE
Page 18 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
City
<City>
Country
<Country>
Language
<Language>
Postal Code
<Postal Code>
Telephone no.
<Telephone no.>
Fax number
<Fax. number>
E-Mail Address
<E-Mail Address>
5. Choose Save.
6. Remember the created BP number.
7. Access the activity using the following navigation option in the SAP SRM system:
Transaction Code
SM30
8. Enter Table/View T77S0
9. Choose Maintain.
10. Maintain the created BP number in VALUE field; abbreviation for group = HRALX and
Sem. abbr. = OADBP
11. Choose Save.
3.6.2 Create Package Z001
Procedure
1. Access the activity using the following navigation option in the SAP SRM system:
Transaction Code
SE80
2. Select Package and enter Z001.
3. Choose Enter.
4. In the dialog box choose Yes.
5. Maintain a short description.
6. Choose Enter.
3.6.3 Assign and Activate User Exit for ORG Number Range
Procedure
User exits are deployed in two steps. Step1 is to assign an exit to a project and Step 2 is to
activate the project.
© SAP SE
Page 19 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Phase 1:
1. Access the activity using the following navigation option:
Transaction Code
CMOD
2. Enter YSMBSRM as project name on the Initial Screen, check the Attributes radio-button,
and choose the Create button.
3. Enter any description in the Short text field of the Attributes of Enhancement Project
screen and choose Save.
4. Choose the Enhancement Assignments button.
5. In the Enhancement column, enter RHIV0001 and choose Enter.
6. Save your entries.
Phase 2:
1. On the Initial screen, choose the Activate Project button.
3.6.4 Create Include ZXHIVU01
Prerequisites
Download the SMBSRMH_INCLUDE_ZXHIVU01.txt file into your local folder.
Procedure
1. Access the activity using the following navigation option in the SAP SRM system:
Transaction Code
SE38
2. Enter ZXHIVU01 in the Program field and choose the Create button.
3. In the Program Attributes dialog box, enter any description in Title field and then select
TYPE Include program from the dropdown list in the Type field.
4. Choose the Save button.
5. In the Create Object Directory Entry dialog box, enter your package and choose Save.
6. In the editor, copy the source code from the SMBSRMH_INCLUDE_ZXHIVU01.txt file into
the report program.
7. Choose the Activate button.
3.6.5 T77S0 SWITCH OFF
Use
This activity switches off the transport connection for HR-specific customizing. This is
recommended for setting up the organizational data model.
© SAP SE
Page 20 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Normally, this task is performed automatically. Should it be necessary to perform
it manually, follow the procedure outlined below.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SM30
2. Enter table/view T77S0 and choose Maintain.
3. Choose Position and enter the following data:
Field
Value
Group Name
TRSP
Semantic Abbrev.
CORR
4. Change the value for this entry from <blank> to X.
3.6.6
CREATE REPORT Z_SMBSRM_CREATE_ORG
To create the organizational model in the system, first download the file
SMBSRMH_REPORT_UPLOAD_ORG.TXT to your local folder ("c:tmp").
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SE38
Program
Z_SMBSRM_CREATE_ORG
2. Enter the above report name in the Program field, choose Create (F5).
Ensure that you create the report with the above name space without any other
changes or it would lead to incomplete ORG set up with errors in further steps.
3. In the dialog box screen of Attributes enter any title and select Executable Program Type
in the Attributes box and click the Save button.
4. If Create Object Directory Entry dialog box appears, enter Z001 in the package field and
click the Save button.
5. If Workbench Request dialog box prompts appears, enter the Request number from
dropdown(F4) help or click Create for New Requests (F7).
6. In the Report screen, delete any default lines and copy the program from file
SMBSRMH_REPORT_UPLOAD_ORG.TXT
7. Click Activate (Cltrl+F3) button.
© SAP SE
Page 21 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.6.7 Manual Upload of ORG Model Template
In order to create an organizational model in the system, first download the
SMBSRM_RDS_ORG_UPLOAD_SAMPLE_A2O_SRMATERP.TXT file into your local folder.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SE38
Program
Z_SMBSRM_CREATE_ORG
2. Execute the report Z_SMBSRM_CREATE_ORG (F8 button).
3. In organization structure, select the purchasing node created with F4 Help.
4. On the Creation of Org Structure via Spread Sheet Upload selection screen, maintain the
following fields:
Field
Entry Value
Organizational Root
10001011 (Example)
This should be ORG ID of PURCHASING Node.
TXT File with Org
SMBSRM_RDS_ORG_UPLOAD_SAMPLE_A2O_SRMATERP.TXT
Test Mode
Blank
5. Choose F8.
6. Ensure that the list program doesnt contain any error messages.
First run the report in the test mode by checking the Test Mode field.
3.6.8 Execute Report RHSOBJCH
Use
If the SOBJ is inconsistent the purpose of this activity is to run a report This step is necessary
if Activate standard tasks displays error messages.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu
Tools → ABAP Workbench → Development → ABAP Editor
Transaction Code
SE38
2. Execute the program: RHSOBJCH.
3. Select all of the objects.
If no objects are found, ignore this step.
4. Perform a reconciliation by choosing List → Update selection.
© SAP SE
Page 22 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
5. After the object list has been reconciled, the table OBJS is consistent.
3.6.9 Maintain Company, Purchasing Organization, and
Purchasing Group
Use
This step can be skiped, if the organization structure was uploaded with report
Z_SMBSRM_CREATE_ORG
If you have personalized your enterprise structure, you must check whether the entries have
been assigned correctly.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
PPOMA_BBP
2. Search for the organizational unit EBP Company.
3. Choose the Function tab page, select the Company checkbox, and enter the following
Company Code assignment after having selected the corresponding logical back-end
system:
Flag
Company Code
System
Company Code
1000
ONECLNTERP
4. Search for the organizational unit Purchasing Organization ERP and double-click the
entity.
5. Choose the Function tab page, select the Purchasing Organization checkbox, and enter
the following assignment after having selected the corresponding logical back-end
system:
Flag
Purch. Organization
System
Correspond to
Purch. Organization
1000
ONECLNTERP1000
6. Search for the organizational unit Purchasing Group ERP and double-click the entity.
7. Choose the Function tab page, select the Purchasing Group checkbox and enter the
purchasing group:
Flag
Purchasing Group
Correspond to
Purchasing Group
100
8. Choose Save (Ctrl+S).
© SAP SE
Page 23 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.6.10 Maintain the Responsibilities for Purchasing Group
This step can be skiped, if the organization structure was uploaded with report
Z_SMBSRM_CREATE_ORG
Procedure
1. Access the activity using the following navigation option in the SAP SRM system:
Transaction Code
PPOMA_BBP
2. Double-click the organizational unit Purchasing Group ERP.
3. Choose the Responsibility tab page.
4. In the section Organizational Responsibility, choose the Object ID field.
5. Use the F4 help to search for the EBP Company organizational unit.
6. Select the EBP Company Organizational unit and choose Continue.
7. Choose Save.
3.6.11 Replicate Locations from ERP Backends
To replicate specific locations and plants from the back end to SAP SRM, use
Viewing Account Assignment Categories Used in SAP SRM. If you wish to
replicate all of the locations and plants from the back end to SAP SRM, follow the
steps in Tax Settings in SAP SRM.
Use
The purpose of this activity is to replicate all locations from the backend to SAP SRM.
Procedure
1. Access the activity using the following navigation option in the SAP system:
Transaction Code
SE38
2. Enter BBP_LOCATIONS_GET_ALL as the Program Name.
3. Choose the Execute button to update the report with all the location data in SAP SRM
from all connected back end systems.
4. Check the final results for any errors by accessing them in SRM:
Transaction Code
SLG1
5. Analyze the application log object BBP_LOCATIONS_GET_ALL.
© SAP SE
Page 24 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.6.12 Creation of Positions in Organizational Structure
Use
In the SRM@ERP deployment, each position related to a user, bears a person instead of a
central person, In case of the SRM@ERP scenario, the creation of users in the ORG is not
possible with the transaction code USERS_GEN, as it is deactivated when the SAP_HR
component is installed (see SAP Note no. 797875).
Instead, the positions are created with the following transaction:
Procedure
1. Access the activity using the following navigation option:
Transaction Code
PP01
2. On the initial screen, enter the following data:
Field
Value
Plan Version
Current plan
Object Type
Position
Active tab page
Infotype Name
Select Object
3. Choose the icon Create infotype (F5).
4. On the Create Object screen, make the following entries:
Field
Value
Validity
Enter a validity period
Object
Object abbr.
Enter the position abbreviation, for example: EMPLOYEE1
Object name
Enter the position name, for example: Eric Employee
5. Choose Save (Ctrl+S).
6. On the Essential Relationships screen, make the following entries
(note that the Relationship Specification field already has the value A 003: Belongs to.):
Field
Value
Relationships
Related Object
Type of related object
Organizational unit
ID of related object
Enter the desired organizational unit ID
7. Choose Save (Ctrl+S).
Result
The system displays the success message Record created (Message no. 5A022) after
successful creation of the position.
© SAP SE
Page 25 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.6.13 Maintenance of ORG Attributes
Use
The purpose of this activity is to create the SRM ORG Attributes.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
PP02
2. On the initial screen, enter the import parameters for Object ID, Infotype, Subtype, and
Validity and choose Change.
Field
Value
Object ID
30000001 EBP Company
Infotype Selection
Infotype
1222 General Attribute Maint.
Subtype
0020 EBP: B2B Procurement
Validity
<validity period>
3. On the next screen, choose Edit → New Entries.
4. Enter the import parameters for the specific attribute (together with the flags for the fields
Default and Excluded) and choose Save.
Attribute
Value Low
KNT
AS
KNT
CC
KNT
NET
KNT
OR
KNT
SO
BUK
ONECLNTERP\<company code>
for example: 1000
CNT
ONECLNTERP\<cost center>
for example: 1201
CUR
EUR/USD
PM_SWERK
ONECLNTERP\<plant>
for example: 1000
ROLE
/SAPSRM/BIDDER
ROLE
/SAPSRM/EMPLOYEE
ROLE
/SAPSRM/PURCHASER
PM_PUR_ORG
<Purchasing Org>
for example: 1000
BSA
for example: ONECLNTERP\NB
© SAP SE
Value High
Default
X
X
ONECLNTERP
Page 26 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Attribute
Value Low
VENDOR_ACS
ONECLNTERP
VENDOR_ACS
<system name>CLNT<client number>
SYS
ONECLNTERP
SYS
ONECLNTEBP
SYS
<system name>CLNT<client number>
ACS
ONECLNTERP
BWA
201
CAT
CORPEXPRESS
DP_PROC_TY
ECDP
DP_PROC_TY
ECPO
DP_PROC_TY
ECPP
CT_PROC_TY
PCTR
TEND_TYPE
BID
TEND_TYPE
BIDX
TEND_TYPE
RFCR
TEND_TYPE
RFPM
TEND_TYPE
RFPP
TEND_TYPE
RFPS
TEND_TYPE
RFQU
ADDR_SHIPT
<select for the address number in table
ADRC>
Value High
Default
Search for EBP_COMP and select
Address number
PRI
LOC01
PRCAT
for example:
for example:
PRCAT
<system name>CLNT<client
number>\<Product cat>
for example: YBF01
<system
name>CLNT<client
number>\<Product
cat>
for example: YBF02
PRCAT
<system name>CLNT<client
number>\<Product cat>
for example: YBR01
<system
name>CLNT<client
number>\<Product
cat>, for example:
YBR05
<system name>CLNT<client
number>\<Product cat>
for example: YBS01
<system
name>CLNT<client
number>\<Product
cat>, for example:
YBS02
<system name>CLNT<client
number>\<Product cat>
for example: YBZ01
<system
name>CLNT<client
number>\<Product
PRCAT
PRCAT
© SAP SE
Page 27 of 63
SAP Best Practices
Attribute
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Value Low
Value High
Default
cat>
for example: YBZ03
<system name>CLNT<client
number>\<Product cat>
for example: YBT01
<system name>CLNT<client
number>\<Product cat>
for example: YBD01
PRCAT
PRCAT
IST_DEST
X
Example:
https://uxcirde.wdf.sap.corp:44320/nwbc/
3.6.14 Organizational Model: Set Attributes for Delivery
Address
Use
In the ORG model we need to maintain the delivery address values for EBP Company.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
PPOMA_BBP
2. Select EBP Company(EBP_COMP) from the model.
3. Click Address Tab
4. Maintain Adress values.
5. Choose Save.
3.6.15 T77S0 SWITCH OFF
Use
This activity switches off the transport connection for HR-specific customizing. This is
recommended at least for setting up the organizational data model.
Normally, this task is performed automatically. Should it be necessary to perform
it manually, follow the procedure outlined below.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SM30
2. Enter the table/view T77S0 and choose Maintain.
3. Choose Position and enter the following data:
Field
© SAP SE
Value
Page 28 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Group Name
TRSP
Semantic Abbrev.
CORR
4. Change the value for this entry in table T77S0 from <blank> to X.
3.6.16 Creation of HR Users
3.6.16.1
Creation of Transaction Z_PASRM
Download BC Set
Download the BC Set Z_SRM_HR_ACTION.bcs (included in the file SRM_HR_ACTION.rar),
which is attached to SAP Note no. 797875, and extract the file.
Upload BC Set
Upload the BC Set Z_SRM_HR_ACTION using the transaction SCPR3.
© SAP SE
Page 29 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
BC Sets are cross client objects. If you have already created the BC Set in another
client, you can skip this step.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SCPR3
2. From the menu, choose BC SET → Upload.
3. Select the file for the BC Set upload.
4. Choose Save and select a package, for example, Z001.
Activate BC Set
Activate BC Set Z_SRM_HR_ACTION using the transaction SCPR20.
1. Access the activity using the following navigation option:
Transaction Code
SCPR20
2. Enter BC Set Z_SRM_HR_ACTION and choose Activate BC Set (F7)
3. Choose an appropriate customizing and workbench request.
4. Confirm the activation options with Enter (Continue Activation).
3.6.16.2
Create Transaction Z_PASRM
Transactions are cross client objects. If you have created the transaction already
in another client, you can skip this step.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SE93
2. Create transaction Z_PASRM by copying transaction PAL1.
3. Choose Save and select a package, for example, Z001.
4. Then change the transaction text of transaction Z_PASRM to Employees (SRM).
5. Access the activity using the following navigation option:
Transaction Code
SM30
6. Enter the table number T588A.
7. Choose Maintain.
8. Select PAL1 and choose Copy as.
9. Change the PAL1 to Z_PASRM transaction value for Menu (from L1) to ES.
10. Choose Save.
© SAP SE
Page 30 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.6.16.3 Creating HR Users (Using Transaction Z_PASRM)
Use
The purpose of this activity is to create several HR Users with action type Employee (SRM)
using the transaction Z_PASRM.
Procedure
1. Access the activity using the following user-defined transaction (see SAP Note 797875).
Transaction Code
Z_PASRM
2. On the initial screen, enter the new personnel number in the Personnel no. field, select
the action type Employee (SRM) and choose Execute (F8). Make the following entries:
Depending on the number range settings (internal or external number
assignment), you have to enter a personnel number. If not, the personnel number
is determined by the system.
Field
User Action and Values
Comment
Create Actions screen
Start
Enter the start date
Position
Enter the position ID,
for example: 500000xx
Personnel area
Enter the desired value,
Choose the
corresponding value
from input help,
for example: ADMIN1
for example:1000
Employee group
Enter the desired value,
for example: 1
Employee subgroup
Enter the desired value.
Choose the
corresponding value
from input help.
Choose Save.
Organizational assignment screen
Subarea
Enter the desired value,
for example: 1010
Choose from input
help.
Choose Save.
Create Personal Data screen
Title
For example: Mr
Last name
For example: Admin
First name
For example: Max
Birthdate
Enter birthdate
Nationality
Enter nationality
Choose Save.
© SAP SE
Page 31 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3. In the Subtypes for Info type Addresses dialog box, choose 1 – Permanent Residence.
Create Addresses screen
Postal Code/City
Enter the desired values
Choose Save.
Create Communication screen
ID/number
(Type 0001 System user name)
For example: ‘ADMIN1’
(is equal to the
corresponding SU01
User)
Choose Save.
Create Communication screen
ID/number
(Type 0010 e-mail)
For example:
admin1@aol.com
Choose Save.
The system displays the message Record created (Message no. PG102) after the
successful creation of the HR User.
4. Choose Back.
5. Create the following employees as described in previous steps, using the following data:
Personnel no.
Position
Name
ID/number (system user)
<personal
number>,
for example, 2
500000xx
Hans Manager1
MANAGER1
<personal
number>,
for example, 3
500000xx
Gerda Manager2
MANAGER2
<personal
number>,
for example, 4
500000xx
Claudia Purchaser1
PURCHASER1
<personal
number>,
for example, 5
500000xx
Peter Purchaser2
PURCHASER2
<personal
number>,
for example, 6
500000xx
Eric Employee1
EMPLOYEE1
<personal
number>,
for example, 7
500000xx
Janet Secretary1
SECRETARY1
<personal
number>,
for example, 8
500000xx
Leo Invoicer1
INVOICER1
© SAP SE
Page 32 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.6.17 Set Up Integration with Organizational Management
Use
The purpose of this activity is to set up integration between HR and SRM organizational
structure objects.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → Crossapplication Basic Settings → Organizational Management →
Integration Business Partner → Set Up Integration with
Organizational Management
Transaction Code
SPRO
2. Ensure that the following entries have been made:
Group
Sem. Abbr.
Value Abbr.
HRALX
HRAC
X
HRALX
OADRE
X
HRALX
OBPON
ON
PLOGI
PLOGI
01
3. If you have made any changes, Choose Save (Ctrl-S).
3.6.18 Maintain Purchaser User
Procedure
1. Access the activity using the following navigation option in the system:
Transaction Code
PPOMA_BBP
2. Double-click user Purchaser1 in the organizational structure.
3. Choose the icon with the quick infor text Go to on top in the extreme left corner.
4. Choose the Purchaser Assignment menu option from the drop-down list.
5. Select the PURCHASER1 (example) user.
6. Choose the Assign icon on top (with quick info text Assign).
7. In the dialog box displayed, select the corresponding purchasing group (local example).
8. Choose Continue.
9. Choose Save.
10. Choose the Back arrow.
If you are working with the Portal, a Portal user must be created for every SAP
SRM user. Refer to the S06 building block configuration guide for more
information.
© SAP SE
Page 33 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.7 Configuration of Supplier Data
3.7.1 Create Supplier Groups (Supplier Root)
Procedure
1. Access the activity using the following navigation option:
Transaction Code
PPOCV_BBP
2. In the initial dialog box, choose Continue (Enter) to confirm the suggested validity range.
3. On the Vendor Groups (BBP) Create screen, in the Details for Vendor Group New:
Vendor Group screen area, make the following entries on the Name tab page:
Field
Value
Object abbr.
SupplierRoot
Name
Supplier Root
4. Choose Save.
5. Change the Language to add a second language.
6. Choose Save and confirm the Transport dialog box.
3.7.2 Maintain Table BBP_MARKETP_INFO
Use
This step enables the customer to automatically download supplier information from the SAP
Marketplace. The fields, Supplier Root and Currency are supplied.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → Technical
Basic Settings → Settings for Supplier Synchronization →
Information on Automatic Download from Marketplace
Transaction Code
SPRO
2. Make the following entries in the BBP_MARKETP_INFO table to maintain the
combination of VG and the supplier root ID (see previous section):
Field
Value
Vendor Root
VG<supplier root object ID>
Currency
EUR
You can check the created supplier root object ID in table HRP1000 with Object type VG.
3. Choose Save.
© SAP SE
Page 34 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.7.3 Upload Payment Terms
Use
The purpose of this activity is the initial replication of payment terms.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Cross-Application Components → Master Data Synchronization
→ Synchronization of Mass Data → Execute Synchronization
Cockpit
Transaction Code
SPRO
2. In the Customizing Synchronization, choose the program
BBP_UPLOAD_PAYMENT_TERMS and execute
3. On the next screen, enter data transfer system as ONECLNTERP.
4. Execute the program by choosing (F8).
Run transaction SLG1 to check for any application error during the replication.
3.7.4 Upload QM Systems
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SE38
The ERP backend is taken from the BBP_BACKEND_DEST table.
2. Enter the report name BBP_UPLOAD_QM_SYSTEMS.
3. Choose Execute (F8).
4. Enter the logical system for ERP backend in the Data Procurement from System field.
5. Choose Execute (F8).
3.8 Define External Web Services
3.8.1 Define External Catalog and Call Structure for Catalog
Integration
Use
The purpose of this activity is to define an external web catalog (for example, Corporate
Express) to allow purchasing of descriptive items directly from an external service provider
catalog.
Procedure
© SAP SE
Page 35 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
1. Access the activity using one of the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → Master Data →
Content Management → Define External Web Services (Catalogs,
Vendor Lists, and so on.)
Transaction Code
SPRO
2. Choose New Entries.
Field
Value
Web Service ID
CORPEXPRESS
Description
CORPORATE EXPRESS Catalog
Bus.Type of a WebService
Choose Product Catalog from input help
3. Choose Enter.
4. Enter the <vendor for P2P scenario> e.g. Corporate Express 300012 for Germany
baseline, BLACKWOODS for Australia Baseline,and so on, in the Business Partner field.
If you have personalized the vendor number, replace it with the personalized
value.
5. Flag the Use Error Log checkbox.
6. Enter the Codepage of Service for your external catalog, for example, iso-8859-1 (for
CORPORATE EXPRESS Catalog).
7. Choose Goto → Translation.
8. Select your target language (for example, DE) and maintain the texts in your target
language.
For the code page, use the same value (do not translate – just copy the value).
9. Choose Enter.
10. Double-click the Standard Call Structure node.
11. Choose New Entries.
12. Make the following entries:
Seq.
Parameter Name
Parameter Value
Type
10
https://order.staplesadvantage.at/
URL
20
/easyorder.oci/isapv1?OCI_VERSION=2.0
URL
30
Username
SAPOCIDEMO
Fixed Value
40
Password
DEMO777OCI
Fixed Value
50
HOOK_URL
60
~OkCode
ADDI
Fixed Value
70
~target
_parent
Fixed Value
80
~caller
CTLG
Fixed Value
Return URL
13. Choose Save (Ctrl+S).
© SAP SE
Page 36 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.8.2 Maintain Description of Web Service
Use
In this activity you maintain the description of the defined web service in the target language.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → Master Data →
Content Management → Define External Web Services
Transaction Code
SPRO
2. Select the entry CORPEXPRESS and choose Goto → Translation. Select the target
language (for example, DE).
3. Maintain the description for the CORPEXPRESS Web Service ID in target language.
4. Choose Save (Ctrl+S).
3.9 Configuration of Middleware Data
3.9.1 Set Control Parameters
Use
The purpose of this activity is to set control parameters.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → Technical
Basic Settings → Set Control Parameters
Transaction Code
SPRO
2. Choose New Entries.
3. Enter the following data:
Key Control Record
Configuration Key Description
Value Control
Record
SPOOL_JOB_USER
User that executes spool job.
EBP_JOB
SPOOL_LEAD_INTERVALL
Interval by which the retry time incr.
60
SPOOL_MAX_RETRY
Max. number of retries for writing
BAPIS
5
4. Choose Save (Ctrl+S).
5. Choose Back (F3).
© SAP SE
Page 37 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.9.2 Job Processing
3.9.2.1
Create Variant for Report BBP_GET_STATUS_2
Use
The purpose of this activity is to create a variant for the report BBP_GET_STATUS_2.
Procedure
1. Access the activity using the following options:
Transaction Code
SA38
2. Enter program name, for example BBP_GET_STATUS_2, then choose Execute (F8).
3. Enter the logical system ONECLNTERP.
4. In the menu, choose Goto → Variants → Save As Variant.
5. Enter the variant name and meaning, and save your entries.
3.9.2.2
Create Variant for Report CLEAN_REQREQ_UP
Use
The purpose of this activity is to create a variant for report CLEAN_REQREQ_UP.
Procedure
1. Access the activity using the following options:
Transaction Code
SA38
2. Enter the program name, for example CLEAN_REQREQ_UP, then choose Execute (F8).
3. Enter the logical system ONECLNTERP.
4. In the menu, choose Go to → Variants → Save As Variant.
5. Choose Save.
6. Enter the variant name, for example <VAR02>, a variant meaning and save your entries.
3.9.2.3
Create Variant for Report HRALXSYNC
Use
The purpose of this activity is to create a variant for the report HRALXSYNC.
Procedure
1. Access the activity using the following options:
Transaction Code
SA38
2. Enter the program name, for example HRALXSYNC, then choose Execute (F8).
3. Make the following entries:
Flag
© SAP SE
Act. Ind.
Page 38 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Branch from organizational unit
X
Include all object types
X
Run attribute check
X
4. In the menu, choose Go to → Variants → Save As Variant.
5. Enter the variant name, for example <VAR02>, a variant meaning and save your entries
and choose Back.
© SAP SE
Page 39 of 63
SAP Best Practices
3.9.2.4
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Schedule Report BBP_GET_STATUS_2
Use
The purpose of this activity is to schedule report BBP_GET_STATUS_2 periodically to update
the status of the document created. First we create a variant before scheduling the reports
periodically.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu
Tools → CCMS → Background Processing → Define Job
Transaction Code
SM36
2. Type in the Job name BBP_GET_STATUS_2, and Job class C (low priority).
3. Choose Start condition.
4. Choose Immediate.
5. Select the Periodic job checkbox and choose Period values (F5).
6. Choose Other period. Type in 2 min (default 15 min) and save three times.
7. Choose Define steps (F6) and ABAP program. Enter the Name: BBP_GET_STATUS_2.
8. Select Choose the Variants and then Save (Ctrl+S).
9. Choose Back (F3) and then Save (Ctrl+S).
3.9.2.5
Schedule Report CLEAN_REQREQ_UP
Use
The purpose of this activity is to schedule the report CLEAN_REQREQ_UP periodically to
check whether the documents have been created in the backend. It is recommended to
create a variant before you schedule the reports periodically.
Procedure
1. Access the activity using the following navigation options:
SAP Menu
Tools → CCMS → Background Processing → Define Job
Transaction Code
SM36
© SAP SE
Page 40 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
2. Type in the Job name and choose Start condition.
3. Choose Immediate.
4. Choose Periodic Job and Period values (F5).
5. Choose Other period. Enter the value 2 min and save three times.
6. Choose Define Steps (F6) and ABAP program. Enter the Name: CLEAN_REQREQ_UP.
7. Select Choose the Variants and then Save (Ctrl+S).
8. Choose Back (F3) and then Save (Ctrl+S).
Schedule the background Job CLEAN_REQREQ_UP (status update of
documents and first follow-on documents posted in SRM) to be run with the
frequency of every 5 min and with the ABAP program CLEAN_REQREQ_UP.
Follow the steps described for the first job.
3.9.2.6
Schedule Report RSPPFPROCESS
Schedule the background Job RSPPFPROCESS (Selection and Processing of Outputs) to be
run with the frequency of every 2 min and with the ABAP program RSPPFPROCESS. Follow
the steps described for the first job.
3.9.2.7
Match up Organizational Units and Persons with
Business Partners
Use
The purpose of this activity is to repair any inconsistency between the Organizational Units
and persons with the business partner data.
Procedure
1. Access the activity using the following transaction:
Transaction Code
SE38
Program
HRALXSYNC
2. Choose the Branch from Organizational Unit checkbox.
3. Search for all the organizational units that you need to perform the matching.
4. Select Include all Object Types.
5. Choose Save as Variant (Ctrl+S) to save the setting in a variant (for example, ORGMATCH) first.
6. Choose Save.
7. Choose Execute (F8) to run the report now.
8. Select all entries and choose Start Repair.
© SAP SE
Page 41 of 63
SAP Best Practices
3.9.2.8
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Schedule Periodic Comparison (HRALXSYNC)
Use
The purpose of this activity is to plan a periodic check and update for business partner
addresses from organizational units.
Procedure
1. Access the activity using the following transaction code:
Transaction Code
SM36
2. Enter a job name (for example, OM-BP Comparison).
3. Choose Enter.
4. Enter the ABAB program name HRALXSYNC with the variant (for example, ORGMATCH) that you created in the step Match up Organizational Units and Persons with
Business Partners.
5. Choose Save (Ctrl+S).
6. Choose Back (F3).
7. Choose the Start condition (F5) button to define the start time and date.
8. Choose Period Values to ensure that it is scheduled as a periodic daily job.
9. Save (Ctrl+S) the period values in the dialog box.
10. Choose Save (Ctrl+S) on the Start Time screen.
11. Choose Save on the Define Background Job screen to save the scheduled job.
12. A message states that your job is saved with the status Released.
3.9.3 Determining FMs for Data Exchange: BP
Use
In this activity, entries are created and updated in the CRMC_BUT_CALL_FU table that
determines the event at which FM is executed in order to allow data exchange between
vendor and supplier.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Cross-Application Components → SAP Business Partner →
Data Distribution → Activate FM
Transaction Code
SPRO
2. Ensure that the following entries are included in table CRMC_BUT_CALL_FU
(transaction: SM30):

CRM Inbound → ABA_FSBP_INBOUND_MAIN

CRM Outbound → BBP_IFC_OUTBOUND

CRM Inbound → BBP_IFC_INBOUND
© SAP SE
Page 42 of 63
SAP Best Practices

Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Business Partner Outbound → MDS_BUPA_OUTBOUND
3. Check and, if required, maintain the following entries:
CRMC_BUT_CALL_FU
Determining Function Modules for Data Exchange: BP
Event
(ZTPKT)
Application
Object
(OBJAP)
Item
FM
(POSNR)
Call
CRMIN
BUPA
(BP)
…
BBP_IFC_INBOUND
X
CRMIN
BUPA
ABA_FSBP_INBOUND_MAIN
X
CRMIN
BUPA
BUPA_INBOUND_MAIN_CENTRAL
X
CRMIN
BUPR
BUPA_INBOUND_REL_CENTRAL
X
CRMOU
BUPA
BUPA_OUTBOUND_BPS_FILL_CENTRAL
X
CRMOU
BUPA
ABA_FSBP_OUTBOUND_BPS_FILL
X
CRMOU
BUPA
BBP_IFC_OUTBOUND
X
CRMOU
BUPA
ABA_FSBP_OUTBOUND_BPS_FILL
X
CRMOU
BUPR
(BP Rel.ship)
BUPA_OUTBOUND_BPR_FILL_CENTRAL
X
BPOUT
BUPA
BUPA_OUTBOUND_MAIN
BPOUT
BUPA
BUPA_OUTBOUND_ALE_MAIN
Blank
BPOUT
BUPR
BUPA_OUTBOUND_ALE_REL
blank
BPOUT
BUPX
(BP and BP
Rel.ship)
MDS_BUPA_OUTBOUND
X
MERGE
BUPA
MERGE_BUPA_CENTRAL
X
MERGE
BUPA
BBP_IFC_MERGE
X
MERGE
BUPA
MERGE_BUPA_FINSERV
X
MERGE
BUPR
MERGE_BUPR_CENTRAL
X
CRMIN:
CRMOU:
BPOUT:
MERGE:
CRM Inbound
CRM Outbound
Business Partner Outbound
Merging of Current Data
3.9.4 Activate Synchronization Options
Use
The purpose of this activity is to activate objects for master data synchronization.
© SAP SE
Page 43 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Procedure
Before implementing this step, check Source and Target Objects in SPRO under
Cross-Application Components → Master Data Synchronization →
Material/Service Integration → Activate/De-activate Synchronization (Material to
Product and vice versa).
The following entries have to exist:
Source Object
Target Object
Act. Ind.
ECCMAT
PRODMAT
X
ECCMATGRP
PRODCAT
X
ECCMATTYP
PRODCAT
X
ECCPINFREC
PRODMAT
X
ECCSERV
PRODSERV
X
ECCSERVTYP
PRODCAT
X
PRODMAT
ECCMAT
X
PRODMAT
ECCPINFREC
X
PRODSERV
ECCSERV
X
3.9.5 Activate/De-activate Synchronization (Material to
Product)
Use
The purpose of this activity is to activate objects for master data synchronization.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Cross-Application Components → Master Data Synchronization
→ Synchronization Control → Synchronization Control →
Activate Synchronization Options
Transaction Code
SPRO
2. Choose New Entries.
3. Enter the following data if the following entries are not in the table:
Source Object
Target Object
Act. Ind.
BP
CUSTOMER
X
BP
VENDOR
X
CUSTOMER
BP
X
VENDOR
BP
X
ECCMAT
PRODMAT
X
© SAP SE
Page 44 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
ECCMATGRP
PRODCAT
X
ECCMATTYP
PRODCAT
X
ECCPINFREC
PRODMAT
X
ECCSERV
PRODSERV
X
ECCSERVTYP
PRODCAT
X
PRODMAT
ECCMAT
X
PRODMAT
ECCPINFREC
X
PRODSERV
ECCSERV
X
4. Choose Save (Ctrl+S).
If you do not want to synchronize certain objects, deactivate them.
For example, if you do not want to synchronize changes to business partners in SRM
with vendors in ECC, deactivate the entry Source Object BP - Target Object
VENDOR.
3.9.6 Maintain Post Processing Orders (PPO) Settings
Use
An order, which is generated automatically in the post processing office for checking and
processing errors that occur, for example, during mass runs.
The data required for creating a post processing order is transferred to the post processing
office via an interface by the business process to which the event belongs.
Post processing orders can be processed and completed manually in the post processing
sesktop, or can also be completed and deleted by way of reports.
The eCATT is performing 4 steps for setting up the PPO:
3.9.6.1
Activation of the Forward Error Handling (FEH)
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Cross-Application Components → Processes and Tools for
Enterprise Applications → Enterprise Services → Error and
Conflict Handler → Activate Error and Conflict Handler
Transaction Code
SPRO
2. On the Change View Activate FEH for Client: Details screen, select the Activated
checkbox.
3.9.6.2
Delete Logical Systems for Post Processing Office
1. Access the activity using one of the following navigation options:
Transaction Code
© SAP SE
SM30
Page 45 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Table
/SAPPO/VLGSYS
The Logical Systems for Postprocessing Orders are only needed if the post
processing office across all clients or systems is used. For SRM@ERP, no
entries are needed, otherwise a dump occurs during master data synchronization.
2. In case you are using SM30 for table maintenance, enter the table name
/SAPPO/VLGSYS and choose Maintain.
3. Delete all entries with the fields COMPONENT and OBJLOGSYS (F8).
4. Choose Save (Ctrl+S).
3.9.6.3
Activate Creation of Post Processing Orders
Use
The purpose of this activity is to activate the creation of post processing orders.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Cross-Application Components → General Application
Functions → Postprocessing Office → Business Processes →
Activate Creation of Postprocessing Orders
Transaction Code
SPRO
2. Choose New Entries.
3. Enter the following data:
Component
Business Process
Act.
AP-MD
CVI_01
X
AP-MD
CVI_02
X
AP-MD
CVI_03
X
AP-MD
CVI_04
X
AP-MD
PROD_01
X
AP-MD
PROD_02
X
AP-MD
PROD_03
X
AP-MD
PROD_04
X
AP-MD
PROD_05
X
AP-MD
PROD_06
X
AP-MD
PROD_07
X
AP-MD
PROD_11
X
AP-MD
PROD_12
X
4. Choose Save (Ctrl+S).
© SAP SE
Page 46 of 63
SAP Best Practices
3.9.6.4
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Activation of PPO Requests for Platform Objects
Use
The purpose of this activity is to activate objects for master data synchronization.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Cross-Application Components → Master Data Synchronization
→ Synchronization Control → Synchronization Control →
Activate PPO Requests for Platform Objects in the Dialog
Transaction Code
SPRO
2. Choose New Entries.
3. Enter the following data:
Syn. Object
PPO Active
PRODMAT
X
BP
X
PRODCAT
X
PRODSERV
X
4. Choose Save (Ctrl+S).
3.9.6.5
Reactivate Post Processing Orders (PPO)
Use
This eCATT checks if the post processing office setting is maintained correctly.
Note: This activity is not required during Manual Setup.
3.10 Basic Workflow Settings
3.10.1 Maintain Standard Setting for SAP Business Workflow
Use
The purpose of this activity is to set all standard settings that are necessary for the workflow
management.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → CrossApplication Basic Settings → Business Workflow→ ProcessControlled Workflow → Technical Configuration → Customize
SAP Business Workflow Automatically
Transaction Code
SWU3
2. Execute by choosing the Perform Automatic Workflow Customizing (F9) icon on each of
the nodes, except the following (which are optional but not required):
© SAP SE
Page 47 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide

Optional: Maintain Prefix Numbers

Optional: Check if workflow customizing Maintain Additional Settings and Services →
Maintain Web Server is correctly maintained; otherwise, maintain the web server
setting.
Maintain the web server address as follows: http://<host>:<port>/

Optional: Maintain Standard Domain for Internet Mail: A standard domain for the
current system is required for this function. Automatic customizing is not possible for
the standard domain.
For more information, refer to the SAP Library: Choose mySAP Technology
Components → SAP Web Application Server → Basis S ervices/Communication
Interfaces (BC-SRV) → Communication Interfaces (BC-SRV-COM) → SAPconnect
(BC-SRV-COM) → SAPconnect: Administration → Default Domain.

Optional: Maintain Guided Procedures Gateway: Check if workflow customizing
Guided Procedures → Maintain Guided Procedures Gateway is maintained correctly;
otherwise, maintain the Gateway setting.
The system user WF-BATCH is used. All automatically created users have the
profiles SAP_ALL / SAP_NEW assigned to them, which gives them full
authorization rights. If this authorization is not applicable to your project, you have
to restrict the rights of these users according to your company’s security policy.
3.10.2 Generalize Dependant Tasks
Procedure
1. Access the activity using the following navigation options:
IMG Path
SAP Supplier Relationship Management → SRM Server →
Cross-Application Basic Settings → Business Workflow →
Process-Controlled Workflow → Technical Configuration →
Generalize Tasks
Transaction Code
/SAPSRM/WF_GEN
2. On the initial screen, make the following entries:
Field
Value
Task Type
Task group
Task
SRM Approval Process Decision Tasks (40000003)
3. Choose Execute.
4. Select all tasks and choose Generalize.
5. Repeat these steps for Task SRM Approval Process User Tasks (40000005 and
40000007).
3.10.3 Event Type Linkages for Workflow
Procedure
1. Access the activity using the following navigation option:
© SAP SE
Page 48 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
IMG Path
Supplier Relationship Management → SRM Server → CrossApplication Basic Settings → Business Workflow → ProcessControlled Workflow → Technical Configuration → CheckEvent
Type Linkage
Transaction Code
SPRO
2. Check if the following two entries are available, and if the Linkage Activated flag has been
set:
Field
Value
Object Category
CL ABAP CLASS
Object Type
/SAPSRM/CL_WF_PDO
Event
READY_FOR_RELEASE
Receiver Type
SRM_PROCESS_START
Linkage Setting (Event Receiver)
Receiver Call
M Method
Class Name
/SAPSRM/CL_WF_PROCESSS_EXEC
Interface Name
BI_EVENT_HANDLER_STATIC
Method Name
ON_EVENT
Event delivery
Using tRFC (Default)
Linkage Activated
Selected
Behavior Upon Error Feedback
Do not change linkage
Field
Value
Object Category
CL ABAP CLASS
Object Type
/SAPSRM/CL_WF_PDO
Event
READY_FOR_WORKFLOW
Receiver Type
WS_400000_14
Linkage Setting (Event Receiver)
Receiver Call
Function Module
Receiver Function Module
/SWW_WI_CREATE_VIA_EVENT_IBF
Event delivery
Using tRFC (Default)
Linkage Activated
selected
Behavior Upon Error Feedback
System defaults
The Event Type Linkages Overview shows these event type linkages with the status No
errors.
3.10.4 Copy BRF Objects
Use
This activity executes a report to transport Business Rule Framework (BRF) objects specific
to SAP Supplier Relationship Management (SAP SRM) to a sandbox system.
© SAP SE
Page 49 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Procedure
1. Access the activity using the following navigation option:
Transaction Code
/SAPSRM/BRFTRANSPORT
or:IMG Path
SAP Supplier Relationship Management → SRM Server →
Cross-Application Basic Settings → Business Workflow →
Process-Controlled Workflow → Technical Configuration →
Copy BRF Objects
Transaction Code
SPRO
2. On the Program BRF_TRANSPORT_SIMPLE screen, enter SRM_WF in the Application
Class field.
3. Select Copy
4. Choose Execute (F8).
3.11 Master Data Synchronization
3.11.1 Execution of Essential SRM Reports
3.11.1.1
Reports Registration
Use
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SE16
2. Enter the Table Name COMC_PR_TOOL_REG.
3. Choose New Entries.

PROGRAM_NAME - Name of the program/report you want to run as below:
o
COM_HIERARCHY_DELETE_ALL

USER_NAME - User with which you are logged on

EXEC_DATE - Date on which you would like to run this report
4. Choose Save (Ctrl+S) for each program entry made.
5. Repeat steps 3 to 4 for the reports below as well:
 COM_PRODUCT_DELETE_ALL
 COM_PRODUCT_UPGRADE
It is recommended to run these reports before the initial data replication in order
to avoid any inconsistencies.
© SAP SE
Page 50 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
The execution of these reports does not have any impact on your ERP backend
data.
It is not recommended to run these reports in a productive system.
3.11.1.2
Report Run – COM_HIERARCHY_DELETE_ALL
Use
The purpose of this activity is to run the COM_HIERARCHY_DELETE_ALL report. This report
deletes all hierarchy and category data in table COMM_HIERARCHY before the initial
replication.
You can later use transaction COMM_HIERARCHY to see what kind of categories are
replicated from back-end system after replication.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu
Tools → ABAP Workbench → Development → ABAP Editor
Transaction Code
SE38
2. Enter the following data for the following program: COM_HIERARCHY_DELETE_ALL.
3. Choose Execute (F8).
4. Answer the question to delete all hierarchies with YES and Execute.
3.11.1.3
Report Run – COM_PRODUCT_DELETE_ALL
In case there are already existing products in the system, perform the same step using
program COM_PRODUCT_DELETE_ALL,. This report deletes all product master data in the
COMM_PRODUCT table.
You can later use the transaction COMMPR01 to see what kind of products are replicated
from the back-end system.
Use
The purpose of this activity is to run the report COM_PRODUCT_DELETE_ALL.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu
Tools → ABAP Workbench → Development → ABAP Editor
Transaction Code
SE38
2. Enter the following data at program: COM_PRODUCT_DELETE_ALL.
3. Choose Execute (F8).
4. Answer the question to delete all products with YES, unchecked Simulation – No deletion
and Execute.
© SAP SE
Page 51 of 63
SAP Best Practices
3.11.1.4
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Report Run – COM_PRODUCT_UPGRADE
Use
The purpose of this activity is to run report COM_PRODUCT_UPGRADE.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu
Tools → ABAP Workbench → Development → ABAP Editor
Transaction Code
SE38
2. Enter the following for the program: COM_PRODUCT_UPGRADE
3. Choose Execute (F8).
3.11.2 Initial Replication
Execute the synchronization of master data.
Use the synchronization cockpit (transaction: MDS_LOAD_COCKPIT) and perform the
following steps:
3.11.2.1 Initial Replication of Customizing Comparison:
Product
Use
The purpose of this activity is the initial replication of customizing for product replication.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
SPRO
IMG Path
Cross-Application Components → Master Data Synchronization
→ Synchronization of Mass Data → Execute Synchronization
Cockpit
Alternative option:
Transaction Code
MDS_LOAD_COCKPIT
2. In the Customizing Synchronization window, choose the report titled: Customizing
Comparison: Product with the program name: MSI_MAPPING_PRODUCT_CUST and
double-click it.
3. Select both Number-ID Conversion & Message Control checkboxes.
4. Choose Execute (F8).
3.11.2.2 Initial Replication of Material Type
Use
The purpose of this activity is the initial replication of material type.
© SAP SE
Page 52 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
SPRO
IMG Path
Cross-Application Components → Master Data Synchronization
→ Synchronization of Mass Data → Execute Synchronization
Cockpit
Alternative option:
Transaction Code
MDS_LOAD_COCKPIT
2. In the Synchronization Process window, choose Material Type as the source object and
Product Category as the target object and double-click the entry.
3. Remove the flag Background Processing.
4. Choose Start Synchronization (F8).
You can check the replication status by choosing on the Monitor tab page. The
progress status should be green. If this is not the case, however, execute the
transaction SMQ2 (qRFC Monitor - Inbound queue) to check if the queues are
indeed held in the status Ready. To release the queue, double-click the queue
name and choose the Activate Queue (F6) to release it.
If you cannot activate the entire solution in one day an error can occur in the
MDS_LOAD_COCKPIT as the Business System cannot be selected correctly.
In this case, change the AEDAT field of lcrt_clntcache table for the ERP business
system to the actual date (use transaction SE16).
3.11.2.3 Initial Replication of Material Group
Use
The purpose of this activity is the initial replication of master group.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
SPRO
IMG Path
Cross-Application Components → Master Data Synchronization
→ Synchronization of Mass Data → Execute Synchronization
Cockpit
Alternative option:
Transaction Code
MDS_LOAD_COCKPIT
2. In the Synchronization Process window, choose Material Group as the source object and
Product Category as the target object and double-click the entry.
3. Remove the Background Processing flag.
4. Choose Start Synchronization (F8).
© SAP SE
Page 53 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
You can check the replication status by choosing the Monitor tab page. The progress
status should be green. If not, however, execute the transaction SMQ2 (qRFC
Monitor - Inbound queue) to check if the queues are indeed held in the status Ready.
To release the queue, double-click the queue name and choose the Activate Queue
(F6) icon to release it.
3.11.3 Write Description ‘Product’ into the Product Numbering
Scheme
After the synchronization of material type and group, the numbering scheme R3PRODSTYP
has been created in the view cluster COMVC_SCHEME entry. Now the description for the
numbering scheme has to be entered (Maintenance View COMV_SCHEME).
Procedure
1. Access the activity using the following navigation options:
IMG Path
Cross-Application Components → SAP Product → Product
Category → Define Category Numbering Schemes
Transaction Code
SPRO
2. In the Change “Define Numbering Scheme”: Overview screen, make the following entry:
Numbering schema
Scheme Description
Levels
R3PRODSTYP
Product
2
3. Select the entry R3PRODSTYP, choose Define Numbering Scheme Levels and make the
following entries:
Level
Scheme Description
1
4
2
4
4. Save your entries.
3.11.3.1 Initial Replication of Material Data
Use
The purpose of this activity is the initial replication of master data.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
SPRO
IMG Path
Cross-Application Components → Master Data Synchronization
→ Synchronization of Mass Data → Execute Synchronization
Cockpit
Alternative option:
Transaction Code
© SAP SE
MDS_LOAD_COCKPIT
Page 54 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
2. In the Synchronization Process window, choose Material as the source object and
Product: Material as the target object and double-click the entry.
3. Remove the Background Processing flag.
4. In the selection criteria, select the material, which you would like to replicate:
Field Name
Incl/Excl
Option
Lower Limit
Upper Limit
Material
I Select specified
values
EQ: Equal Single
Values
*
*
5. Choose Start Synchronization (F8).
You can check the replication status by choosing on the Monitor tab page. The
progress status should be green. If not, however, execute the transaction SMQ2
(qRFC Monitor - Inbound queue) to check if the queues are indeed held in the
status Ready. To release the queue, double-click on the queue name and choose
the Activate Queue (F6) icon to release it.
3.11.3.2
T77S0 SWITCH OFF
Use
This activity switches off the transport connection for HR-specific customizing. This is
recommended for setting up the organizational data model.
Normally, this task is performed automatically. Should it be necessary to perform
it manually, follow the procedure outlined below.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SM30
2. Enter the table/view T77S0 and choose Maintain.
3. Choose Position and enter the following data:
Field
Value
Group Name
TRSP
Semantic Abbrev.
CORR
4. Change the value for this entry from <blank> to X.
3.11.3.3 Initial Replication of Vendor Data
Use
The purpose of this activity is the initial replication of vendor data.
Procedure
© SAP SE
Page 55 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
1. Access the activity using one of the following navigation options:
Transaction Code
SPRO
IMG Path
Cross-Application Components → Master Data Synchronization
→ Synchronization of Mass Data → Execute Synchronization
Cockpit
Alternative option:
Transaction Code
MDS_LOAD_COCKPIT
2. On the Synchronization Process screen, choose Vendor as the source object and
Business Partner as the target object and double-click the entry.
3. Remove the flag Background Processing.
4. In the selection criteria, select the vendor, which you would like to replicate (for example,
300012):
Field Name
Incl/Excl
Option
Lower Limit
Upper Limit
Vendor
I Select specified
values
EQ: Equal Single
Values
*
*
5. Choose Start Synchronization (F8).
3.12 Maintain Attributes for EBP Company
3.12.1 T77S0 SWITCH OFF
Use
This activity switches off the transport connection for HR-specific customizing. This is
recommended for setting up the organizational data model.
Normally, this task is performed automatically. Should it be necessary to perform
it manually, follow the procedure outlined below.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SM30
2. Enter table/view T77S0 and choose Maintain.
3. Choose Position and enter the following data:
Field
Value
Group Name
TRSP
Semantic Abbrev.
CORR
4. Change the value for this entry from <blank> to X.
© SAP SE
Page 56 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.12.2 Maintain Extended Attributes for EBP Company
Use
The maintenance of the SRM Extended Attributes has to be carried out manually.
The product categories, the locations, and the storage locations have to be maintained.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
PPOMA_BBP
2. Search for the relevant ORG unit EBP Company.
3. Double-click the search result in the Hit list to display the details.
4. On the Extended Attributes tab page in the Details for Organizational unit EBP Company
area, choose Product Categories and check the following entries:
Product Cat
To Product Cat
Src. System
Default
<Product Cat>,
<Product Cat>,
for example, YBF01
for example, YBF02
<system
name>CLNT<client
number>
<Product Cat>,
<Product Cat>,
for example, YBR01
for example, YBR05
<Product Cat>,
<Product Cat>,
for example, YBS01
for example, YBS02
<system
name>CLNT<client
number>
<system
name>CLNT<client
number>
<system
name>CLNT<client
number>
<Product Cat>,
for example, YBT01
<Product Cat>,
<Product Cat>,
for example, YBZ01
for example, YBZ03
<system
name>CLNT<client
number>
<system
name>CLNT<client
number>
<Product Cat>,
for example, YBD01
X
5. Choose Locations and make entries for the locations (that is, the plant) as in the example
list below. You should select the plant under the company code that you defined.
Partner ID
Plant
Company Code
Description
Src. System
Use F4
help to
select the
partner ID
1000
1000
Plant 1000
ONECLNTERP
Use F4
help to
select the
partner ID
<plant>,
<company
code>,
Plant 1
ONECLNTERP
© SAP SE
for example:
1000
Default
X
for example,
1000
Page 57 of 63
SAP Best Practices
Use F4
help to
select the
partner ID
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
<plant>,
for example:
1100
<company
code>,
Plant 2
ONECLNTERP
for example,
1000
6. Choose Storage Locations, and make entries for the storage locations as in the example
list below. You should select the Storage Location under your defined Plant.
Plant
Storage Location
Description
Src. System
1000
1020
Shop floor
ONECLNTERP
1000
1030
Shipping (L WM)
ONECLNTERP
1000
1040
Shipping w/o LWM
ONECLNTERP
1000
1050
Stores - (Lean WM)
ONECLNTERP
1000
1060
Returns
ONECLNTERP
1100
1130
Shipping (L WM)
ONECLNTERP
1100
1140
Shipping w/o LWM
ONECLNTERP
1100
1160
Returns
ONECLNTERP
7. Choose Save (Ctrl+S).
3.12.3 Maintain Details for Positions
Procedure
1. Access the activity using the following navigation option:
Transaction Code
PPOMA_BBP
2. Search for the relevant ORG unit EBP Company.
3. Maintain the following data:
a. Double-click MANAGER2. In Details for Position Manager1, choose the:
Basic data tab page. Set the Head of own org. unit flag.
b. Double-click MANAGER1. In Details for Position Manager1, choose the Basic
data tab page. Set the Head of own org. unit flag.
4. Maintain the following data:
c.
Double-click MANAGER2. Choose Goto → Managerial Assignment
d. Move the Purchasing Group 1CLNTERP to Manager2
Use the search term in case the organizational unit does not exist in the results
list on the left-hand side.
© SAP SE
Page 58 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.13 Back-end system for Product Category /
Accounting Data
3.13.1 Define Back-end System for Product Categories
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → Technical
Basic Settings → Define Backend System for Product Category
Transaction Code
SPRO
2. Choose New Entries.
3. On the Change View “Determination of Target System using Product Categories” screen,
make the following entries:
Category ID
Source System Name
Target System
<Product Cat>, for
example, YBD01
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBF01
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBF02
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBR01
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBR02
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBR03
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBR04
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBR05
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBS01
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBS02
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBT01
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBZ01
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBZ02
<system name>CLNT<client
number>
ONECLNTERP
<Product Cat>, for
example, YBZ03
<system name>CLNT<client
number>
ONECLNTERP
© SAP SE
Page 59 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
*
4.
<system name>CLNT<client
number>
ONECLNTERP
The name of the system is a three-letter word. This is the second part of the server
name. It is separated by an underscore.

The client number is the 3-digit SAP client number.

Example: BSXCLNT100.
5. Choose Save (Ctrl+S).
6. Choose Back (F3).
3.13.2 Define G/L Account and Account Assignment for
Product Categories
Use
The purpose of this activity is to define accounting assignment.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management → SRM Server → CrossApplication Basic Settings → Account Assignment → Define G/L
account for Product Category and Account Assignment Category
Transaction Code
SPRO
2. Access the activity using the following navigation options:
3. Choose New Entries.
4. Maintain the following entries:
Category
ID
Source System
Account
Assignment
Category
G/L account
Default
*
<system
name>CLNT<client
number>
AS
<G/L account>,
for example, 608000 (for
material type HAWA or
521000 (for material type
FHMI).
X
This entry depends on
your ERP settings.
*
<system
name>CLNT<client
number>
CC
<G/L account>,
for example, 608000 (for
material type HAWA or
521000 (for material type
FHMI).
X
*
<system
name>CLNT<client
number>
NET
This entry depends on
your ERP settings.
X
*
<system
name>CLNT<client
OR
<G/L account>,
for example, 608000 (for
X
© SAP SE
Page 60 of 63
SAP Best Practices
Category
ID
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
Source System
Account
Assignment
Category
number>
G/L account
Default
material type HAWA or
521000 (for material type
FHMI).
*
<system
name>CLNT<client
number>
SO
This entry depends on
your ERP settings.
X
*
<system
name>CLNT<client
number>
STR
<G/L account>,
for example, 608000 (for
material type HAWA or
521000 (for material type
FHMI).
X
*
<system
name>CLNT<client
number>
WBS
<G/L account>,
for example, 608000 (for
material type HAWA or
521000 (for material type
FHMI).
X
This entry depends on
your ERP settings.
<Product
Cat.>, for
example,
YBD01
<system
name>CLNT<client
number>
CC
<G/L account>,
for example, 608000 (for
material type HAWA or
521000 (for material type
FHMI).
X
This entry depends on
your ERP settings.
<Product
Cat.>, for
example,
YBT01
<system
name>CLNT<client
number>
CC
<G/L account>,
for example, 608000 (for
material type HAWA or
521000 (for material type
FHMI).
X
This entry depends on
your ERP settings.
 The system-name is a three-letter word. This is the second part of the underscoreseparated server name.

The client-number is the 3-digit SAP client number.
5. Choose Save (Ctrl+S).
3.14 Maintain the Vendor Business Partner
(OPTIONAL)
Use
The purpose of this activity is to maintain the vendor business partners.
Procedure
© SAP SE
Page 61 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
1. In the SRM system use transaction ‘bbp_update_mapping’.
2. On the Vendor Mapping – Adjust Backend screen, in the Add/Change/Delete section,
maintain the following fields:

Backends field New Backend Entry: ONECLNTERP

Add to Backend: <systemId>CLNT<clientnumber>
If you have personalized the vendor number, replace it with the personalized
value.
3. In case one of the following messages appears:
- Specify an e-mail address for the company
- Incoterterm not maintained in system,
maintain the e-mail address on the Company Data – Contact Data tab page and check
again the incoterms on the Supplier Data Change tab page.
Repeat step 2 for all required vendors used in the scenarios (for example, 300000,
300002 and 300003).
4. Choose Save.
3.15 Client-Specific Configuration Parameters
Use
The purpose of this activity is to trigger the regeneration of condition tables.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SM30
2. Enter the /SAPCND/V_CFGCC table and choose Maintain.
3. On the Change View “Client-Specific Configuration Parameters for Customers” screen,
change the value for parameter REGEN_GROUP_WS from 1 to 2.
4. Choose Save (Ctrl+S).
Note: Sometimes the execution of this activity takes a while.
© SAP SE
Page 62 of 63
SAP Best Practices
Generic Configuration Settings (SRM@ERP) (S03): Configuration Guide
3.16 Initial Run of Report HRALXSYNC
It is recommended to run the report initially after setting up the org data model.
1. Access the activity using one of the following navigation options:
SAP Menu
Tools → ABAP Workbench → Development → ABAP Editor
Transaction Code
SE38
2. Enter the following data for the following program: HRALXSYNC
3. Choose Execute (F8).
4. Enter the following entries:
Flag
Act. Ind.
Branch from Organizational unit
X
Include all object types
X
Run attribute check
X
5. Choose Execute (F8).
6. Select all entries and choose Start Repair.
7. Check the result. Issues for object type S and number 500000xx can be ignored.
8. Choose Back (F3).
© SAP SE
Page 63 of 63