EHP3 for SAP SRM 7.0
EHP7 for SAP ERP
6.0
October 2014
English
Technical Basis Settings
(SRM@ERP) (S00)
Building Block Configuration Guide
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): 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 2 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): 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 3 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
Content
1
Purpose .............................................................................................................................. 6
2
Preparation ......................................................................................................................... 6
3
4
5
6
2.1
Check Personalization ............................................................................................. 6
2.2
Check Add-on and ERP Integration Steps ............................................................... 6
2.3
SRM Integration Steps ............................................................................................. 7
2.4
Check SAP Virtual Machine Container (VMC) ......................................................... 7
Activation User Settings ..................................................................................................... 7
3.1
Maintain ERP Roles ................................................................................................. 7
3.2
Enable SAP Scripting ............................................................................................... 8
3.3
Set Decimal Notation and Date Format ................................................................... 9
3.4
Check User Authorization ...................................................................................... 10
3.5
Check User Access Key......................................................................................... 11
Prerequisites..................................................................................................................... 12
4.1
Update BC Set Definition ....................................................................................... 12
4.2
Language Check .................................................................................................... 12
Logical Systems and Client Maintenance ........................................................................ 12
5.1
Define Logical System for SRM ............................................................................. 12
5.2
Maintaining Client Settings..................................................................................... 13
Customizing Switches ...................................................................................................... 14
6.1
7
6.1.1
Deactivate BW-Based Analytics ........................................................................ 15
6.1.2
Activate BW-Independent Analytics ................................................................... 15
6.1.3
Activate Portal-Independent Navigation Frame ................................................. 15
6.1.4
Activate Embedded Analytics for Purchaser ..................................................... 16
Internet Pricing Component Configuration ....................................................................... 16
7.1
8
Activate/Deactivate Business Functions ................................................................ 15
Check IPC Configuration........................................................................................ 16
Technical Basic Settings .................................................................................................. 17
8.1
Evaluation Path for Purchaser Assignment ........................................................... 17
8.2
Activation of Services ............................................................................................. 17
8.2.1
Activation of Services for SAP NWBC ............................................................... 17
8.2.2
Activation of Services for SAP SRM .................................................................. 19
8.2.3
Activation of Special Services for SAP SRM ..................................................... 19
8.3
Start Application Monitors ...................................................................................... 20
8.4
SLD Cache Entry ................................................................................................... 20
8.5
Maintain Transaction COMC_TEXT ...................................................................... 21
8.6
Deactivate Geocoding for BP Addresses ............................................................... 22
8.7
Integration between Business Partner and HCM Employees ................................ 23
© SAP SE
Page 4 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
8.8
Maintain Role of Business System ........................................................................ 23
8.9
Business Partner Settings ...................................................................................... 23
9
8.9.1
Define Number Ranges for Business Partners .................................................. 23
8.9.2
Define Groupings for Business Partner and Assign Number Ranges ............... 24
8.9.3
Check Assignment of Vendor Number Range to Vendor Account Group ......... 25
8.9.4
Define Number Assignment for Direction Vendor to BP .................................... 26
8.9.5
Set BP Role Category for Direction BP to Vendor ............................................. 27
8.9.6
Define BP Role for Direction Vendor to BP ....................................................... 27
User Management and Roles........................................................................................... 29
9.1
Mass Generation of Profiles for SRM PFCG Roles ............................................... 29
9.2
Maintain Authorization Profiles .............................................................................. 29
9.3
Mass Synchronization of Roles .............................................................................. 30
9.4
Define User Groups ............................................................................................... 30
9.5
Define Generic Business Users ............................................................................. 31
9.6
Create Technical System Users............................................................................. 32
9.7
Update the User Login Time (ltime) ....................................................................... 33
10
RFC Destinations .......................................................................................................... 33
10.1
11
Define RFC Destinations ........................................................................................ 33
Queues ......................................................................................................................... 34
11.1
Register Inbound Queues ...................................................................................... 34
11.2
Register Outbound Queue ..................................................................................... 35
© SAP SE
Page 5 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
Technical Basis 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 Quick Guide for Activation
Consultant.
Before starting the implementation, complete the following activities:

Read the Quick Guide for Activation Consultant delivered with the specific SAP RDS
SRM (Service Marketplace at http://service.sap.com/solutionpackages (Quicklink
/rds-srm).

Ensure that you meet the recommended prerequisites.
2 Preparation
Before the installation, preparatory activities must be performed. Some of these activities can
only be performed manually, while others are automated. All of these activities are described
in this document.
2.1 Check Personalization
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.2 Check Add-on and ERP Integration Steps
Ensure that, in addition to the necessary SAP ERP, SRM and NetWeaver components, the
following system components are installed and deployed correctly (for information on the
required releases and support package levels see the RDS SRM Software Requirement
Document, available on Service Marketplace and RDS SRM V2.703 Step-by-Step Guide for
SRM@ERP).
Ensure that the following prerequisites are fulfilled:

The system landscape directory (SLD) is up and running.

The installation client is maintained correctly as the business system in the
connected SLD.

The entry in the SLD cache table has to be updated by running the SLDCHECK
transaction.
© SAP SE
Page 6 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
2.3 SRM Integration Steps
2.4 Check SAP Virtual Machine Container (VMC)
The SAP Virtual Machine Container (VMC) which is part of SAP NetWeaver 7.01 has to
be activated (see Note 854170).
The IPC (Internet Pricing and Configurator) is based on the VMC (VMC is used
exclusively as a runtime environment for selected SAP Java components like Internet
Pricing Configurator). It is used to enable consistent pricing and configuration through all
sales channels, and it does not need an online SAP system while still maintaining pricing
and configuration data in one place.
The Lean Navigation Frame does not carry a JAVA stack and therefore simplified pricing
is used instead. The IPC settings are optional.
Procedure
1. Access the activity using the following navigation option:
SM52
Transaction Code
2. Use the transaction to determine whether the virtual machine is activated. Check if VMC
is active is displayed on the screen.
If the virtual machine is not activated, you have to turn it on since it is required by the
Internet Pricing and Configurator (IPC). For more information, see SAP Note854170.
No customizing steps are necessary. Your system administrator has to set profile
parameters and restart the system.
3 Activation User Settings
3.1 Maintain ERP Roles
Use
The following procedure describes how to maintain the role for the activation - and an
RFC user, wh ich is necessary to activate the SAP SRM rapid-deployment solutionspecific content.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
PFCG
2. On the Role Maintenance Screen enter role Z_SAP_NBPR_A_RDS_SRM_1C and
choose Change. If the role does not exist in the ERP system, the Add-on BP-ERP was
not imported into the ERP system. In this case, please perform the following steps.
3. Select the Authorizations tab.
4.
Choose Change Authorization Data.
© SAP SE
Page 7 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
5. Open the Cross-application Authorization Objects node.
6. Choose Activate for every inactive line.
7. Repeat step 5 and 6 for all other nodes.
8. Choose Generate.
9.
Choose Execute.
10. Choose Back twice.
11. Save your entries.
12. Repeat steps 2 - 10 for role Z_SAP_NBPR_RFC_RDS_SRM_1C.
3.2 Enable SAP Scripting
Use
eCATTs are used to automate the activation of SAP Best Practices configuration settings.
Prior to the activation, you must allow eCATT processing in the system by setting the profile
parameter sapgui/user_scripting. The value for Enable or disable user scripting on the frontend must be set to true.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
RZ11
2. On the Maintain Profile Parameters screen, make the following entries:
Field Name
Description
User Action and
Values
Note
Param. Name
Profile parameter name
sapgui/user_scripting
3. Choose Display.
4. On the Display Profile Parameters Attributes screen, select Change values.
5. On the Change Parameter Value screen, make the following entries.
Field Name
Description
User Action and
Values
Note
New Value
New Value for user
scripting
TRUE
Enable SAP Scripting
6. Choose Save.
When you save the change, the window closes and the current value of the
parameter changes to TRUE. This change only becomes effective when you log
on to the system again.
If the parameter is set in RZ11, you lose the change when you restart the server.
© SAP SE
Page 8 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
3.3 Set Decimal Notation and Date Format
Use
Perform this activity to set up the activation user ID.
Procedure
1. Access the activity using the following navigation options:
SAP Menu
System  User Profile  Own Data
Transaction Code
SU3
2. Choose the Defaults tab page.
3. Make sure you set Decimal Notation according to your country’s default, like
1.234.567,89.
4. Make sure that you set Date Format according to your country’s default, like
DD/MM/YYYY.
5. Make sure that you assign your printer in the field output device (see also the Printer
Environment section above).
6. Save your settings.
7. Log off from the system.
8. Log on to the system.
Logging off and on is necessary since the change in the user settings only
becomes effective when you log on to the system again.
9. When the complete activation procedure is finished, you may change these values as
desired.
© SAP SE
Page 9 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
3.4 Check User Authorization
Use
In this activity, you check if a user is created.
You can skip this chapter if you are not using Solution Builder for activation of the RDS
SRM solution.
The authorization role SAP_NBPR_A_RDS_SRM_1C exist by copying the role into Z*
namespace, which includes all authorization the activation user needs, to activate the
RDS SRM solution. This role needs to be assigned to the activation user.
In the Activation Content you require the following roles to be assigned:
Z_SAP_NBPR_A_RDS_SRM_1C
Z_SAP_NBPR_RFC_RDS_SRM_1C
Roles to be assigned.
.
Directly after activation of the SAP Best Practices content, remove the authorizations
you have given to the system user who has performed the activation steps. This is for
security reasons to prevent the system user from misusing the authorizations granted
before.
Procedure
1. To carry out the activity, choose one of the following navigation options:
SAP Menu
Tools  Administration  User Maintenance  Users
Transaction Code
SU01
2. On the User Maintenance: Initial Screen, in the User field, enter <User-ID> and choose
Create.
3. Choose the Address tab.
4. Make the following entries:
Field Name
User Action and Values
Last name
<Last name of the user>
First name
<First name of the user>
Note
5. Choose the Logon Data tab.
6. Make the following entries:
Field Name
User Action and Values
Password
<initial password>
User type
Dialog
© SAP SE
Note
Page 10 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
7. Choose the Defaults tab.
8. Make the following entries:
Field Name
User Action and Values
Note
Logon language
EN
Make sure that the
logon language of
the activation user
is always English
(and NOT the local
language of the
activation user) for
all activation
activities.
Decimal notation
1.234.567,89
Date format
DD.MM.YYYY
9. Choose the Roles tab and assign role Z_SAP_NBPR_A_RDS_SRM_1C.
10. Save your entries.
Result
A user to activate SAP Best Practices content has been created.
3.5 Check User Access Key
Use
The activation user needs to be registered as a developer.
Procedure
1. Access the activity using the following navigation options:
Transaction Code
SE38
2. Maintain Z_RDS_TEST as the program.
3. Choose Create.
4.
Maintain the access key for your user, if you get a pop-up to confirm the access key.
Your system administrator can provide the Access key for you.
© SAP SE
Page 11 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
4 Prerequisites
4.1 Update BC Set Definition
You can skip this step if you do not use SAP Best Practices Solution for
implementation.
We recommend that you turn off the creation of activation links. By doing this, you can
significantly increase activation speed and avoid errors.
Procedure
1. Run the following activity:
SAP Menu
Tools  Customizing  Business Configuration Sets 
Activation of BC Sets
Transaction Code
SCPR20
2. On the Business Configuration Sets: Activation screen, choose Utilities → System
Settings.
3. Choose Change (Shift + F1).
4. In the Activation section, select the radio button for Do Not Create parameter.
5. Choose Enter on the information message.
6. Save your settings.
4.2 Language Check
Make sure that your logon language is always English (and not your local language) for all
activation activities.
5 Logical Systems and Client Maintenance
Use
You need to make certain client settings to ensure that the environment for the
implementation has been set up correctly.
5.1 Define Logical System for SRM
Use
The purpose of this activity is to define the logical systems required.
© SAP SE
Page 12 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management  SRM Server 
Technical Basic Settings  ALE Settings  Distribution (ALE)
 Basic Settings  Logical Systems  Define Logical System
Transaction Code
SPRO
2. Choose New Entries.
3. Enter the following logical systems:
Logical System
Name
<system ID>CLNT<client number>
<own description>
ONECLNTERP
One Client ERP System
ONECLNTEBP
One Client EBP System

The system ID is a three-letter word.

The client number is the 3-digit system client number.

Example: BSXCLNT100:
System ID: BSX
Client: 100
Using the Solution Builder for the automated activation, one of the logical
systems will be created with the name NONE.
4. Choose Save (Ctrl+S).
5. Choose Back (F3).
5.2 Maintaining Client Settings
Use
You need to maintain the client settings to ensure that the implementation activities for
implementation of your solution are supported.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu
Tools (Administration (Administration
(Client Maintenance
Transaction Code
SCC4
(Client Administration
2. On the Display View: “Clients”: Overview screen, switch to change mode.
3. Select your current client, and choose Details.
4. Maintain the following settings:
Field Name
© SAP SE
Description
User action and
Values
Comment
Page 13 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
Field Name
Description
User action and
Values
Comment
ORT01
City
<Your Location>
LOGSYS
Logical System
Select the logical
system of the current
client <system
ID>CLNT<client
number>
As defined before
MWAER
Standard
Currency
Select the currency of
your country
Like EUR, USD, GBP, and
so on
CCCATEGORY
Client Role
Customizing
CCCOR_ACTV
Automatic
Recording of
Changes
Select
Required to record
customizing changes
CCNOCLIIND
Cross-Client
Object Changes
Changes to repository
and cross-client
customizing allowed
Required to create or
change cross-client
customizing settings
5. Save your settings.
6 Customizing Switches
Use
You need to check the status of the customizing switches for SRM.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management  SRM Server (Display
Status of Customizing Switches
Transaction Code
SPRO
2. On the Display View: “Clients”: Overview screen, check the status of the following
customizing switches:
Customizing Switch ID
Planned Status
SRM_700_ANALYTICS_BW
Inactive
SRM_700_ANALYTICS_LOCAL
Active
SRM_700_LOCAL_MENU
Active
© SAP SE
Page 14 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
6.1 Activate/Deactivate Business Functions
6.1.1
Deactivate BW-Based Analytics
Use
The purpose of this activity is to deactivate BW based Analytics.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management  SRM Server  Analytics
 Activate/Deactivate BW-Based Analytics
Transaction Code
SPRO
2. Choose Planned Status of Customizing Switch and set the status to Inactive.
6.1.2
Activate BW-Independent Analytics
Use
The purpose of this activity is to activate BW independent Analytics.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management  SRM Server  Analytics
 Activate/Deactivate BW-Independent Analytics
Transaction Code
SPRO
2. Choose Planned Status of Customizing Switch and set the status to Active.
6.1.3
Activate Portal-Independent Navigation Frame
Use
If you want to use the SAP NetWeaver Business Client you have to activate the PortalIndependent Navigation Frame. If you want to use the SAP NetWeaver Portal the PortalIndependent Navigation Frame has to be deactivated. Refer to the S06 configuration guide UI
Integration for more detailed information.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management  SRM Server 
Technical Basic Settings  Portal-Independent Navigation
Frame Activate/Deactivate Portal-Independent Navigation
Frame
Transaction Code
SPRO
© SAP SE
Page 15 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
2. Choose Planned Status of Customizing Switch and set the status to Active.
6.1.4
Activate Embedded Analytics for Purchaser
Use
In this customizing activity, you can deactivate or activate the embedded analytics functions
for the Contract Management and Business Partner work centers. You do this by deactivating
or activating the customizing switch Embedded Analytics for Purchasers
(SRM_701_EMB_ANALYTICS).
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management  SRM Server  Analytics
 Deactivate/Activate Embedded Analytics for Purchasers
Transaction Code
SPRO
2. Choose Planned Status of Customizing Switch and set the status to Active.
7 Internet Pricing Component Configuration
7.1 Check IPC Configuration
The IPC (Internet Pricing and Configurator) is based on the VMC (VMC is used exclusively as
a runtime environment for selected SAP Java components like Internet Pricing Configurator).
It is used to enable consistent pricing and configuration through all sales channels, and it
does not need an online SAP system while still maintaining pricing and configuration data in
one place.
The Lean Navigation Frame does not carry a JAVA stack and therefore simplified pricing is
used instead. The IPC settings are optional.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Supplier Relationship Management (SRM Server (CrossApplication Basic Settings (Pricing (Check Technical and
Customizing Settings for Conditions
Transaction Code
SPRO
2. Execute the IMG activity. You will get a list of details.
If the IPC is not running, contact your system administrator for further assistance.
The result will be a list giving an overview of all relevant customizing settings and its links
to the customizing maintenance. At the end of the list, further checks are displayed for
simulating different scenarios with regard to pricing. If the IPC is not configured, a dump
occurs when you execute the function Simulation of Pricing with Manual Price.
© SAP SE
Page 16 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
If the BAdI BBP_PRICEDATA_READ with the implementation
BBP_PRODUCT_PRICE is activated the implementation prevents the IPC call.
8 Technical Basic Settings
8.1 Evaluation Path for Purchaser Assignment
Use
An evaluation path is an instruction to the system, which determines which object types and
relationships are to be included in an evaluation of your organizational plan.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
OOAW
2. Execute transaction OOAW and check if the following table entries are available
(otherwise the evaluation path for the purchaser assignment will not work.):
EvalPath
Evaluation path text
A490
Purchases for
A491
Is a Purchaser of
A492
Is a Purchaser of
B490
Is Supervised By
B491
Has Purchaser
B492
Has Purchaser
3. Enter the missing entries.
4. Save your settings.
8.2 Activation of Services
8.2.1
Activation of Services for SAP NWBC
Activate the services needed for SAP NWBC using the transaction SICF.
1. Access the activity using the following navigation options:
Transaction Code
SICF
2. On the Maintain Services screen, choose Execute (F8).
3. On the Maintain Services screen, expand the Virtual Hosts / Services node as follows and
activate all the services listed below:
© SAP SE
Page 17 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
default_host
sap
public
bc
icons
default_host
sap
public
bc
icons_rtl
default_host
sap
public
bc
pictograms
default_host
sap
public
bc
ur
default_host
sap
public
bc
webdynpro*
default_host
sap
public
bc
webicons
default_host
sap
public
bsp
sap
htmlb
default_host
sap
public
icf_info*
default_host
sap
public
icman
default_host
sap
bc
bsp
sap
public
default_host
sap
bc
bsp
sap
rsr_bex_launch/
default_host
sap
bc
bsp
sap
system
default_host
sap
bc
igs_data
default_host
sap
bc
NWBC*
default_host
sap
bc
print*
default_host
sap
bc
smart_forms
default_host
sap
bc
wd_trace_tool
default_host
sap
bc
wdvd
default_host
sap
bc
webdynpro
kyk*
default_host
sap
bc
webdynpro
sap
cfs_application
default_host
sap
bc
webdynpro
sap
configure_*
default_host
sap
bc
webdynpro
sap
create_complaints_comp
default_host
sap
bc
webdynpro
sap
cust_cockpit_comp
default_host
sap
bc
webdynpro
sap
FITE_EXPENSES
default_host
sap
bc
webdynpro
sap
FITV_POWL_TRIPS
default_host
sap
bc
webdynpro
sap
FITV_TRIP_FORM
default_host
sap
bc
webdynpro
sap
hress_a_cats/
default_host
sap
bc
webdynpro
sap
lcm_application
default_host
sap
bc
webdynpro
sap
lo_oif_cdocs_appl
default_host
sap
bc
webdynpro
sap
lo_oif_main_app
default_host
sap
bc
webdynpro
sap
LO_OIF_OC
default_host
sap
bc
webdynpro
sap
lo_oif_reuse_cond_appl
default_host
sap
bc
webdynpro
sap
lo_oif_vcfg_appl
default_host
sap
bc
webdynpro
sap
lord*
default_host
sap
bc
webdynpro
sap
mmpur_ui_pr_app
default_host
sap
bc
webdynpro
sap
mmpur_vndctcdta_app
default_host
sap
bc
webdynpro
sap
mmsrv_sp_details_app
default_host
sap
bc
webdynpro
sap
mt_order_app
default_host
sap
bc
webdynpro
sap
o2c_*
default_host
sap
bc
webdynpro
sap
POWL*
default_host
sap
bc
webdynpro
sap
psu_md_wui_wda_pss_oif_cfg
default_host
sap
bc
webdynpro
sap
qimt_notification_app
© SAP SE
bc
Page 18 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
default_host
sap
bc
webdynpro
sap
sawe_sa
default_host
sap
bc
webdynpro
sap
sawe_time_ps call
default_host
sap
bc
webdynpro
sap
wd_*
default_host
sap
bc
webdynpro
sap
wdhc_application
default_host
sap
bc
webdynpro
sap
WDK*
*activate all services.
4. Choose Back.
8.2.2
Activation of Services for SAP SRM
Activate the services needed for the SAP SRM using transaction SICF.
1. Access the activity using the following navigation options:
SICF
Transaction Code
2. On the Maintain Services screen choose Execute (F8).
3. On the Maintain Services screen, expand the Virtual Hosts / Services node as follows and
activate all the services listed below:
default_host
sap
bc
webdynpro
sappssrm*
sap
bc
webdynpro
sapsrm*
sap
bc
webdynpro
sap
ibo_wda_inbox
sap
bc
webdynpro
sap
ibo_wda_wfl_substit
sap
bc
webdynpro
sap
ibo_wdc_wfl_substit
sap
bc
bsp
sap
bbp_ve_service
sap
bc
bsp
sap
smart_forms
sap
bc
bsp
sap
ros_prescreen
sap
bc
bsp
sapsrm*
sap
sapsrm*
sap
bw
Bex
*activate all services.
4. Choose Back.
8.2.3
Activation of Special Services for SAP SRM
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SICF_INST
2. On the ICF: Report for Activating Special Service During Installation screen, enter the
Technical Name '*' and choose Execute to activate all services.
© SAP SE
Page 19 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
8.3 Start Application Monitors
Use
The purpose of this activity is to start the application monitor.
Procedure
1. Access the activity using the following navigation options:
IMG Path
Supplier Relationship Management SRM Server  CrossApplication Basic Settings  Start Application Monitors
Transaction Code
SPRO
or
Transaction Code
BBPMONSTART
2. Execute the activity. TA BBPMONSTART starts the Application Monitor on CCMS-Server
for SRM by running the report BBP_STARTUP_TOOL_FOR_CCMS
Note: In case if you are unable to start the Application Monitors check with your BASIS
team.
8.4 SLD Cache Entry
Use
The purpose of this activity is to enter the SLD Cache. If you have an Exchange Infrastructure
System Landscape Directory, you just need to add a business system (example BS_RS5201)
and it should automatically update this entry in the SLD Cache table when you run the
SLDCHECK transaction.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu
Tools  ABAP Workbench  Overview  Data Browser
Transaction Code
SE16
2. Enter the following table name: LCRT_CLNTCACHE.
3. Choose Table Contents. If the table is empty, please proceed as described below.
4. Choose Create Entries (F5) and create an entry as below:
Field
Value
SRTFD
<system ID>CLNT<client number>
AEDAT
<current date>
BS_KEY_NAME
<system ID>_<client number>
BS_ROLE
LOC
BS_CAPTION
<system ID>_<client number>

© SAP SE
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.
Page 20 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide

The client number is the 3-digit SAP client number.

Example: BSXCLNT100.
5. Choose Save (Ctrl+S).
Example: Table LCRT_CLNTCACHE Display
Field
Value
SRTFD
Q5K300
AEDAT
15.07.2009
BS_KEY_NAME
Q5K_300
BS_ROLE
LOC
BS_CAPTION
Q5K_300
8.5 Maintain Transaction COMC_TEXT
Use
Proceed according to consulting note no. 879990:
To avoid the program termination in transaction MDS_LOAD_COCKPIT (Master Data
Synchronization), dummy entries in customizing tables have to be created using transaction
COMC_TEXT.
Procedure
Procedure using SAP GUI:
1. Access the activity using the following navigation option:
Define Text Schema
Transaction Code
COMC_TEXT
2. Make a dummy entry for text object Product as shown in the following example:
Text Objects Details
Field
Value
Text Object
PRODUCT
Meaning
Basic Texts
Text Objects
Key Structure
COMT_PRLGTEXT_PRODUCT
Comm. Structure
COMT_PRLGTEXT_PRODUCT_COM
Procedure Details
Field
Value
Text Object
PRODUCT
Meaning
Basic Texts
© SAP SE
Page 21 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
PR_0001
Text Schema
Procedure
Basic Text
Dscrptn Proc.
Definition of Procedure: Overview
Field
Value
Text Object
PRODUCT
Meaning
Basic Texts
Text Schema
PR_0001
Dscrptn Proc.
Basic Text
Definition of Procedure
BASE (Description: Basic text)
INSP (Description: Inspection text)
INTC (Description: Internal note)
Text
8.6 Deactivate Geocoding for BP Addresses
To de-activate the geocoding of business partner addresses, the report
GEOCODING_SET_GEOFLAG has to be carried out and the corresponding flag Deactivate
Geocoding / Geolocation has to be set (see SAP Note 613647).
Procedure
1. Using SAP GUI
Access the activity using the following navigation option:
Transaction Code
SE38
Run report GEOCODING_SET_GEOFLAG and select Disable Geoservices.
2. Using Solution Builder (eCATT)
To avoid SAP GUI recording of report GEOCODING_SET_GEOFLAG, the entry in the
corresponding customizing table GEOCUST is created directly using INLINE-ABAP:
Table GEOCUST Display
Field Name
Value
MANDT
200
GEOFLAG
X
© SAP SE
Page 22 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
8.7 Integration between Business Partner and HCM
Employees
Procedure
1. Access the activity using the following navigation option:
Transaction Code
OO_CENTRAL_PERSON
2. Check the following entries in table T77S0 and update if required:
Group Name
Semantic Abbreviation
Value of Semantic Abbreviation
(GRPID)
(SEMID)
(GSVAL)
HRALX
HRAC
X
HRALX
OADBP
(empty)
HRALX
OADRE
(empty)
HRALX
OBPON
ON
HRALX
ONUMB
1
HRALX
PBPHR
ON
HRALX
PNUMB
1
8.8 Maintain Role of Business System
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SXMB_ADM
2. Choose Integration Engine Configuration
3. Choose Menu-> Edit --> Change Selected Configuration Data
4. Select in field Role of Business System: LOC Application System
5. Choose Save.
8.9 Business Partner Settings
8.9.1 Define Number Ranges for Business Partners
The purpose of this activity is to maintain number ranges for Business Partner. BP created
from vendor synchronization should have the same numbering as the vendors. For that, the
number ranges for BP have to be identical to the number range for the vendors. Furthermore,
they have to be set to external (the External NR flag is set).
Create external number ranges for BP in the customizing with a numbering similar to the
number ranges of the vendors to be synchronized:
© SAP SE
Page 23 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
Procedure
1. Access the activity using the following navigation options:
IMG Path
Cross-Application Components → SAP Business Partner →
Business Partner → Basic Settings → Number Ranges and
Groupings → Define Number Ranges
Transaction Code
SPRO
2. Choose Change Intervals.
3. Choose Insert Interval (Shift + F1) and maintain the following entries:
NO
From Number
To Number
Current
Number
Ext
Description
(not in the table)
01
0000000001
0000299999
Standard customizing, which
has to be adopted accordingly
in order to sync the number
ranges with Y3
Y3
0000300000
0000399999
X
This entry has to be created if
you use a baseline package.
This entry might differ in your
system landscape if you have
not installed a BAIO package
AB
A
Z
X
Standard customizing which is
already there
The settings mentioned in this document are examples in case you are activating
the SRM package on top of an SAP Best Practices Baseline package (only in that
case you can take over the settings as described in this document).
If you are not using the setting provided in this document, you have to use your
own number range settings to map the vendor and business partner number
ranges.
4. Choose Enter.
5. Choose Save (Ctrl+S).
8.9.2 Define Groupings for Business Partner and Assign
Number Ranges
Use
The number ranges defined for the Business Partner (BP) have to be assigned to the BP
Grouping.
Define BP Groupings for vendor to BP synchronization. Afterwards assign the external
number ranges for the corresponding BP to them. Choose one of the external BP Groupings
for standard grouping by selecting Ext.Std Grping.
© SAP SE
Page 24 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
Procedure
1. Access the activity using the following navigation options:
IMG Path
Cross-Application Components →SAP Business Partner →
Business Partner → Basic Settings → Number Ranges and
Groupings → Define Groupings and Assign Number Ranges
Transaction Code
SPRO
2. Choose New Entries.
3. Choose Insert Interval (Shift + F1) and maintain the following entries:
Grouping
Short Name
Description
Number
Range
Ext
0002
Vendor to BP
Vendor to BP
synchronization
Y3
X
GPEX
Vendor to BP
Vendor to BP
synchronization
AB
X
Ext.Standard
Grouping
X
The settings mentioned in this document are examples in case you are activating
the SRM package on top of an SAP Best Practices Baseline package (only in that
case you can take over the settings as described in this document).
If you are not using the settings provided in this document, you have to use your
own number range settings in order to map the vendor and business partner
number ranges.
4. Choose Enter.
5. Choose Save (Ctrl+S).
8.9.3 Check Assignment of Vendor Number Range to Vendor
Account Group
Use
The purpose of this activity is to check and maintain the assignment of the vendor account
groups to the appropriate number range for the vendors.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Financial Accounting (New) → Accounts Receivable and
Accounts Payable → Vendor Accounts → Master Data →
Preparations for Creating Vendor Master Data → Assign Number
Ranges to Vendor Account Groups
Transaction Code
SPRO
2. Assign the relevant Vendor Account Groups for vendor to BP synchronization. For
example, assign Vendor Account Groups as shown in the following examples.
© SAP SE
Page 25 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
Vendor
Account
Group
Name
Number range
LIEF
Vendors
XX
YB01
Vendors
Y3
YBIV
Vendors
Y3
If you are not using the setting provided in this document, you need to use your
own account groups instead.
8.9.4 Define Number Assignment for Direction Vendor to BP
Use
The purpose of this activity is to assign the business partner groupings to the account groups
for the vendor master records. This is to ensure that when you process vendors as part of
vendor integration, the system also updates the business partner at the same time. With this
assignment you can choose whether the vendor master record is to be created with an
account group, either with internal or external number assignment.
To allow the same numbering for vendor to BP synchronization, the corresponding BP
Groupings are to be assigned to the appropriate Vendor Account Groups with the flag set for
same numbering.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Cross-Application Components → Master Data Synchronization
→ Customer/Vendor Integration → Business Partner Settings
→Settings for Vendor Integration → Field Assignment for
Vendor Integration → Assign Keys → Define Number
Assignment for Direction Vendor to BP
Transaction Code
SPRO
2. Make sure that the following entry exists in the table. If not, choose New Entries (F5) to
create it:
Group
Grp.
Same No
YBIV
0002
X
YB01
0002
X
LIEF
GPEX
X
If you are not using the setting provided in this document, you need to make your
own assignment for the Business Partner Grouping and Vendor Account Group.

BP Grouping 0002 is assigned to Accounting Group YBIV, YB01 (Vendors with NR AB):
Accounting Group YB01, YBIV → NR AB: A – ZZZZZZZZZZ
© SAP SE
External
Page 26 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
BP Grouping GPEX is assigned to Accounting Group LIEF.
Accounting Group LIEF → NR AB: A – ZZZZZZZZZZ
External
The number is similar so the Same Number indicator can be set.
3. Choose Save (Ctrl+S).
8.9.5 Set BP Role Category for Direction BP to Vendor
Use
The purpose of this activity is to define which BP role categories enable vendor integration in
the direction from the business partner to the vendor. You can determine how the system
creates a corresponding vendor in Financial Accounting when you process a business
partner.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Cross-Application Components → Master Data Synchronization
→ Customer/Vendor Integration → Business Partner Settings →
Settings for Vendor Integration → Set BP Role Category for
Direction BP to Vendor
Transaction Code
SPRO
2. Check if the following entries exist in the table. If not, choose New Entries (F5) to create
them:
Role Cat.
Description
BBP000
Vendor
BBP001
Bidder
BBP002
Portal Provider
BBP003
Plant
BBP004
Purchasing Firm
BBP005
Service Provider
BBP006
Invoicing Party
3. Choose Save (Ctrl+S).
8.9.6 Define BP Role for Direction Vendor to BP
Use
The purpose of this activity is to assign BP roles to the account group for the vendor master
record in which the business partner is to be created when processing the vendor.
Procedure
© SAP SE
Page 27 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
1. Access the activity using the following navigation options:
IMG Path
Cross-Application Components → Master Data Synchronization
→ Customer/Vendor Integration → Business Partner Settings →
Settings for Vendor Integration → Define BP Role for Direction
Vendor to BP
Transaction Code
SPRO
2. Check if the following entries exist in the table. If not, choose New Entries (F5) to create
them:
Group
BP Role
0001
BBP000
0001
BBP001
0001
BBP006
0001
FLVN00
0001
FLVN01
KRED
BBP000
KRED
BBP001
KRED
BBP006
KRED
FLVN00
KRED
FLVN01
LIEF
BBP000
LIEF
BBP001
LIEF
BBP006
LIEF
FLVN00
LIEF
FLVN01
YB01
BBP000
YB01
BBP001
YB01
BBP006
YB01
FLVN00
YB01
FLVN01
YBIV
BBP000
YBIV
BBP001
YBIV
BBP006
YBIV
FLVN00
YBIV
FLVN01
© SAP SE
Page 28 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
If you are not using the standard setting, you need to make your own assignment
for the Vendor Account Group and BP Role.
Make the entries for the additional account groups you are using (instead the
account groups YB91, YBIV) and replace it with your own account groups.
3. Choose Save (Ctrl+S).
9 User Management and Roles
9.1 Mass Generation of Profiles for SRM PFCG Roles
Use
Roles are delivered without authorization profiles. The creation of these profiles can be done
automatically.
Procedure
1. Access the activity using the following navigation option:
SAP Menu
Tools  Administration  User Maintenance  Role
Administration  Generate Profiles for Roles
Transaction Code
SUPC
2. In the section, Which roles do you want to output?, select the option Roles with noncurrent profiles.
3. In the section Additional restrictions, enter the role Z_SAPSRM_*.
4. Choose the Execute (F8) button to start the selection.
5. On the screen Roles: Mass generation of profiles, the list of roles with missing or
incomplete authorizations will be displayed.
6. Select all entries and choose the Maintain Authorization Data (F7) button.
9.2 Maintain Authorization Profiles
Procedure
1. Access the activity using the following navigation option:
SAP Menu
Tools  Administration  User Maintenance  Role
Administration  Generate Profiles for Roles
Transaction Code
SUPC
2. In the section "Which roles do you want to output?" select the option "Roles with no
authorization data".
3. In the section Additional restrictions, enter the role Z_SAPSRM*.
© SAP SE
Page 29 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
4. Choose the Execute (F8) button to start the selection.
5. On the screen Roles: Mass generation of profiles the list of roles with missing or
incomplete authorizations will be displayed.
6. Select a role and choose the Maintain Authorization Data (F7) button or if you are asked
for the maintenance type option. Confirm the dialog with Enter.
7. On the Change role: Authorizations screen, the authorizations assigned to the role are
displayed. Select the incomplete (yellow marked) or missing (red marked) authorizations
and maintain the incomplete/missing information.
8. Complete the authorization maintenance by choosing the Generate button (from the
menu, choose Authorizations  Generate).
9. Go back to the list of roles and repeat it for every role.
Typical reasons for incomplete authorizations are organizational levels. You can
restrict the authorization to specific organizational units, or allow it for all (*).
10. Cross check for selecting "All Roles" in section "Which Roles do you want to output?"
and Execute (F8) for the role Z_SAPSRM*. The Output List should be in Green display.
9.3 Mass Synchronization of Roles
Procedure
1. Access the activity using the following navigation option:
Transaction Code
PFCG
2. Choose menu Utilities (Mass comparison
3. Enter Z_SAPSRM* in field Role
4. In Section of action choose Schedule or check job for full reconciliation
5. Choose Execute (F8) twice.
9.4 Define User Groups
Use
The purpose of this activity is to create user groups, which are later assigned to the different
user.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu
Tools (Administration (User maintenance (User Groups
Transaction Code
SUGR
2. Enter the user groups as listed below
3. Choose Create and create the following user groups:
© SAP SE
Page 30 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
User Group
Text
Comment
DEMO
Demo
User group for (demo) business
user
INTEGRATION
Integration
User group for technical user
4. Maintain the first name and the last name of this user.
9.5 Define Generic Business Users
Use
The purpose of this activity is to create an RFC user ID that is needed for the SM59
connection and a system user to execute spooling jobs.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu
Tools (Administration (User maintenance (Users
Transaction Code
SU01
2. Enter a user name as listed below.
3. Choose Create and create the following users:
User ID
Description
SRM Standard Roles
ADMIN1
Administrator
Z_SAPSRM_EMPLOYEE,
Z_SAPSRM_ADMINISTRATOR
EMPLOYEE1
Employee
Z_SAPSRM_EMPLOYEE
INVOICER1
Invoicer
Z_SAPSRM_1C_INVOICER
MANAGER1
Manager 1
Z_SAPSRM_EMPLOYEE,
Z_SAPSRM_MANAGER
MANAGER2
Manger 2
Z_SAPSRM_EMPLOYEE,
Z_SAPSRM_MANAGER
PURCHASER1
Purchaser 2
Z_SAPSRM_EMPLOYEE,
Z_SAPSRM_OP_PURCHASER,
Z_SAPSRM_ST_PURCHASER
PURCHASER2
Purchaser 2
Z_SAPSRM_EMPLOYEE,
Z_SAPSRM_OP_PURCHASER,
Z_SAPSRM_ST_PURCHASER,
SECRETARY1
Secretary
Z_SAPSRM_EMPLOYEE,
Z_SAPSRM_SECRETARY
You can select either the standard SRM roles or the SAP Best Practices roles.
SAP Best Practices roles do not contain authorization objects and are optimized
for navigation purposes.
4. Maintain the first name and the last name of this user.
5. Choose the Logon data tab page, set the Dialog indicator in the User Type screen area
and enter a password of this user.
6. Set the Password initial twice.
© SAP SE
Page 31 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
7. Maintain the user group DEMO
8. Choose the Role tab and assign the user roles listed above.
9. Choose Save (Ctrl+S).
9.6 Create Technical System Users
Use
The purpose of this activity is to create an RFC user ID that is needed for the SM59
connection and a system user to execute spooling jobs.
Procedure
1. Access the activity using one of the following navigation options:
SAP Menu
Tools (Administration (User maintenance (Users
Transaction Code
SU01
2. Enter a user name as listed below, for example EXTBBP.
3. Choose Create and create the following users:
User ID
Description
EXTBBP
User for organizational model
WF-BATCH
Batch user for workflows
RFCUSER
SRM RFC user
RFCUSER_DIA
RFC Dialog User
4. Maintain the first name and the last name of this user.
5. Choose the Logon data tab page, set the System indicator in the User Type screen area
and enter a password ’welcome’ for this user.
6. Maintain the user group INTEGRATION.
7. Choose Save (Ctrl+S).
.
© SAP SE
Page 32 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
9.7 Update the User Login Time (ltime)
Use
With the automated implementation, an eCATT changes the ltime field, which simplifies the
first log on for the demo user. In a successful run, the demo users do not need to change the
password at the first logon.
Procedure

If the solution builder automatic activation is used, you can log on with the demo user
without changing the default password,

If the solution builder automated activation is not used, you have to change the
password when you log on with the demo user the first time.
10 RFC Destinations
10.1 Define RFC Destinations
Use
The purpose of this activity is to define an RFC destination.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Supplier Relationship Management SRM Server 
Technical Basic Settings  Define RFC Destinations
Transaction Code
SM59
2. Choose Create.
3. Enter the RFC Destinations and the Connection Type.
RFC Destination
Description
Connection Type
<system ID>CLNT<client number>
e.g. BSXCLNT100
3
ONECLIENTERP
ONEClientERP
3
ONECLIENTEBP
ONEClientEBP
3

The system ID is a three-letter word.

The client number is the 3-digit SAP client number.
4. Choose the Technical Settings tab page and enter the following values:

Target Server: physical server name

System Number: system number of the system
© SAP SE
Page 33 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
5. Choose Save (Ctrl+S).
6. Choose Connection Test (Ctrl+F3) to test the connection.
7. Go to Utilities → Test → Authorization Test (Ctrl+F4) to test the authorization (logon of the
user will be simulated).
8. Choose Back (F3).
11 Queues
11.1 Register Inbound Queues
Use
The purpose of this activity is the registration of queues for background processing.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SMQR
2. Choose Registration.
3. On the Queue Registration sub screen, make the following entries:
Field Name
Value
Queue name
MDS_BUPA_CUST
Mode
D
Max. Runtime
60
Destination
Attempts
30
Pause
300
Scheduler Monitoring
0
3. Choose Continue (Enter).
MONITORTIME
PAUSE
DESTINATION
MAXRUNTIME
MODE
Queue Name
ATTEMPTS
4. Repeat the Registration for the following queues:
MDS_BUPA_CUST
D
60
30
300
0
MDS_BUPA_VEND
D
60
30
300
0
MDS_CUST_BUPA
D
60
30
300
0
MDS_ECCMAT_PRODM
AT
D
60
30
300
0
MDS_ECCMATGRP_PR
ODCA
D
60
30
300
0
© SAP SE
Page 34 of 35
SAP Best Practices
Technical Basis Settings (SRM@ERP) (S00): Configuration Guide
MDS_ECCMATTYP_PRO
DCAT
D
60
30
300
0
MDS_ECCPINFREC_PR
ODMAT
D
60
30
300
0
MDS_ECCSERV_PROD
SERV
D
60
30
300
0
MDS_ECCSERVTYP_PR
ODCAT
D
60
30
300
0
MDS_PRODMAT_ECCM
AT
D
60
30
300
0
MDS_PRODMAT_ECCPI
NFREC
D
60
30
300
0
MDS_PRODSERV_ECC
SERV
D
60
30
300
0
MDS_VEND_BUPA
D
60
30
300
0
11.2 Register Outbound Queue
Use
The purpose of this activity is to specify the logical destination of the ERP client for the
outbound queue.
Procedure
1. Access the activity using the following navigation option:
Transaction Code
SMQS
2. Choose Registration button.
3. On the Queue Registration sub screen, make the following entries:
Field Name
Value
Destination
RFC connection to your back-end system
Max. Conn.
1
Max. Runtime
60
W/o RFC
Scheduler Monitor
0
4. Choose Continue (Enter).
© SAP SE
Page 35 of 35