Anda di halaman 1dari 46

Rel ease 2008

SRM 7.0 RKT:


SAP SRM One Client in SAP ERP
RKT Collateral 28.01.2009
SAP SRM One Client 2

Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 3
Copyright

Copyright 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400,
OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC
are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World
Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and
services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other
product and service names mentioned are the trademarks of their respective companies.
Data contained in this document serves informational purposes only. National product
specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP
AG and its affiliated companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 4
SAP - Important Disclaimers

SAP Library document classification: PUBLIC
This document is for informational purposes only. Its content is subject to change without
notice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES,
EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR
PURPOSE.
Coding samples
Any software coding and/or code lines / strings ("Code") included in this documentation are
only examples and are not intended to be used in a productive system environment. The
Code is only intended better explain and visualize the syntax and phrasing rules of certain
coding. SAP does not warrant the correctness and completeness of the Code given herein,
and SAP shall not be liable for errors or damages caused by the usage of the Code, except if
such damages were caused by SAP intentionally or grossly negligent.
Internet hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are
intended to serve as a hint where to find supplementary documentation. SAP does not
warrant the availability and correctness of such supplementary documentation or the ability to
serve for a particular purpose. SAP shall not be liable for any damages caused by the use of
such documentation unless such damages have been caused by SAP's gross negligence or
willful misconduct.
Accessibility
The information contained in the SAP Library documentation represents SAP's current view of
accessibility criteria as of the date of publication; it is in no way intended to be a binding
guideline on how to ensure accessibility of software products. SAP specifically disclaims any
liability with respect to this document and no contractual obligations or commitments are
formed either directly or indirectly by this document. This document is for internal use only
and may not be circulated or distributed outside your organization without SAP's prior written
authorization.


Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 5

COPYRIGHT ........................................................................................................................................... 3
SAP - IMPORTANT DISCLAIMERS .......................................................................................................... 4
Coding samples ................................................................................................................................ 4
Internet hyperlinks............................................................................................................................ 4
Accessibility...................................................................................................................................... 4
SAP SRM ON ONE CLIENT IN SAP ERP ................................................................................................ 6
Availibility........................................................................................................................................................ 7
DEPLOYMENT OPTION SAP SRM ON ONE CLIENT IN SAP ERP ......................................................... 8
Structure of the document................................................................................................................. 8
BASIC SETTINGS FOR SAP SRM............................................................................................................ 9
Technical System Settings: System Connections ............................................................................................ 9
Create RFC Destinations.................................................................................................................................. 9
Define Logical System................................................................................................................................... 10
Define Backend Systems................................................................................................................................ 11
Define logical systems for product categories............................................................................................... 11
Maintain ALE settings and Distribution Model ............................................................................................ 12
Definition of ALE Port................................................................................................................................... 12
Create & Generate distribution model ........................................................................................................... 12
Maintain and Generate Partner Profiles......................................................................................................... 13
Register and Activate Queues ........................................................................................................................ 14
Activate of Inbound and Outbound queue............................................. Fehler! Textmarke nicht definiert.
Other System Connection Settings................................................................................................................. 15
ORGANIZATIONAL MANAGEMENT ...................................................................................................... 16
Create Organizational Structure for SRM...................................................................................................... 16
Create vendor root .......................................................................................................................................... 17
BUSINESS PARTNERS........................................................................................................................... 18
Creation of business partners with and without HR integration.................................................................... 19
Define BP number ranges and other settings for business partners .............................................................. 21
Define groupings for BP ................................................................................................................................ 23
Define BP Roles ..................................................................................... Fehler! Textmarke nicht definiert.
Check number ranges for BP relationships.................................................................................................... 25
Vendor number range and grouping .............................................................................................................. 27
MASTER DATA REPLICATION & SYNCHRONIZATION .......................................................................... 28
Preparatory Steps............................................................................................................................................ 28
Activate Vendor Master Data Synchronization............................................................................................. 28
Replication and Synchronization of Vendor Master Data............................................................................. 31
Preparatory Steps............................................................................................................................................ 31
Determining Function Modules for Data Exchange: BP............................................................................... 35
Replication and synchronization of the material master data........................................................................ 37
Preparatory Steps............................................................................................................................................ 37
Activate Material Master Data Synchronization ........................................................................................... 38
Activate Creation of Postprocessing Orders .................................................................................................. 40
Activate PPO Requests for Platform Objects in the Dialog.......................................................................... 42
NON-SRM ONE CLIENT SPECIFIC BASIC SRM AND ERP SETTINGS.................................................... 44
Cross application settings and SRM Business Workflow............................................................................. 44
Business Package for SRM 7.0 ...................................................................................................................... 45
SETTINGS FOR SELF-SERVICE PROCUREMENT..................................................................................... 46
SETTINGS FOR SERVICE PROCUREMENT INCLUDING SUS.................................................................... 46

Gelscht: 08.01.2009
Gelscht: 15
Gelscht: 18
Gelscht: 20
Gelscht: 22
Gelscht: 23
Gelscht: 26
Gelscht: 34
RKT Collateral 28.01.2009
SAP SRM One Client 6
SAP SRM on one client in SAP ERP

Use
The SAP SRM on one client in SAP ERP (abbr. SRM one client) targets customers that like to
utilize simple procurement scenarios with SRM but do not aim to use a separate SRM
installation. This SRM deployment option is focused on low TCO and operates within the
same instance as the Backend (ECC) system.
It is of highest importance to pay attention which scenarios are released officially with this
installation variant.

The following scenarios are released within the SRM one client:
Service Procurement External Staffing in standalone deployment
Self-Service Procurement in classic deployment
SUS in connection with Service Procurement (EBP-SUS) and with Self-Service
Procurement (MM-SUS).

This also includes:
Operational usage of contracts: manual creation of local contracts and their assignment
as sources of supply (no distribution of contracts to ERP)
Request for Proposal (RFP) only in connection with the external staffing scenario for
service procurement in local deployment

See also
Descriptions of the SRM Business Scenarios as well as the Technical Scenarios can be found
in SAP Solution Manager or in the Online Help Portal at http://help.sap.com SAP Solutions
SAP Business Suite SAP Supplier Relationship Mgmt. SAP Supplier Relationship
Mgmt. SAP SRM 7.0

SRM Business Documents in SAP SRM on one client in SAP ERP
shopping cart
purchase order (either standalone deployment with local P.O. in SRM, or classic
deployment with P.O. in ERP no extended classic deployment)
contract (local contract in SRM, available for procurement in SRM no transmission
to ERP)
goods receipt (in SRM routed to ERP)
invoice (in SRM routed to ERP)
bid invitation (RFP - for local scenario external staffing in SRM)
quotation (RFP - for local scenario external staffing in SRM)

Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 7
Availability

The SRM AddOn has been available with ERP 6.0 and SRM 5.0. The newest SRM one client
version is SRM 7.0 with ERP6.0 EhP4. This version uses the same technical platform like
SRM 7.0, e.g. use of SAP Enterprise Portal is mandatory for SRM 7.0 Add-On.

Customers with an existing SRM 5.0 AddOn and ERP 6.0 system can upgrade to SRM 7.0
AddOn after the installation of ERP 6.0 EhP4.

ERP 6.0 with Enhancement Packages
EhP0 EhP1 EhP2 EhP3 EhP4 EhP5
SRM5.0/NW7.00 o.k. o.k. o.k. o.k. - -
SRM5.0/NW7.01 - - - - o.k. -
SRM7.0/NW7.01 - - - - o.k. o.k.


Limitations

Please be aware that the following deployment and migration constraints apply:

ERP 6.0 with SAP SRM in one client in SAP ERP does not support any multiple-
backend functions or hub deployment for procurement
Upgrade or migration from an existing standalone SRM system to ERP 6.0 with SAP
SRM in one client in SAP ERP is not supported via standard SAP upgrade path
SAP does not offer standard migration paths from an SAP SRM in one client in SAP
ERP to a deployment with a standalone SRM system*
The extended classic deployment is not supported

Note

Note 963000 Usage and release of SRM as AddOn to ECC in ERP 6.0 and all related notes
for most recent updates, changes and further details.



Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 8
Deployment option SAP SRM on one client in SAP
ERP
The deployment option SAP SRM on one client in SAP ERP differs significantly regarding a
number of technical and systemic settings of the SRM Server. Master data and business
partner replication is handled differently in SRM one client.
Most of the process settings and configuration is identical to the regular SRM server set up.
Due to this fact, configuration which is not specific for SRM one client, will be referred only via
cross reference.

Structure of the document
The structure of this document refers roughly to the one as pointed out in SAP Solution
Manager for SAP SRM 7.0 (as of September 2008, subject to change). Please read the actual
solution manager content if more detailed information configuration information is needed for
SRM scenarios, e.g. Service Procurement External Staffing, and/or SAP SRM
solutions/applications.







Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 9
Basic Settings for SAP SRM

Basic settings of a SRM Server comprise of a number of technical, communication and other
rather technical settings in diverse customizing views. The SRM one client co-exists in the
ERP system as an additional software package as virtual application resp. system. The
document does not distinguish between SRM and ERP settings explicitly. Any of the technical
settings listed below can concern both systems, either the SRM or the ERP system.
The naming conventions on the screenshots are only proposals. Please feel free to stick to
your own naming conventions.

Technical System Settings: System Connections
Note
The logical system name QV4CLNT301 depicted on several screenshots is the logical system
of the local ERP client.

Create RFC Destinations
Use transaction SM59 and create RFC destination for current client, the SRM client. Maintain
log on data accordingly.
Customizing path to Creation of RFC connections

Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 10

Example for an SM59 entry


Tips & Tricks:
Please check the created RFC destinations and hit button Remote Logon. This is only
successful if the related users had been created previously.

Define Logical System
Customizing path to view V_TBDLS


Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 11


Define Backend Systems
Customizing path to view BBP_BACKEND_DEST


Please maintain entries analogous to 1CLNTEBP, 1CLNTERP, 1CLNTSUS and your local
logical system. Logical system names on the screenshot are examples!

Note
Adhere to the System Landscape Directory settings as shown on the screen shot use your
own SLD names of course.

Define logical systems for product categories
Customizing path to view V_BBP_DET_LOGSYS
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 12


Example for product category target determination


Maintain ALE settings and Distribution Model
Define ALE port. Maintain and distribute message types ACC_GOODS_MOVEMENT,
ACLPAY, BBPCO, BBPIV and MBGMCR.


Definition of ALE Port
Transaction WE21
Alternative customizing path: SPRO SAP Customizing Implementation Guide Logistics
General Product Data Replication ALE Systems in Network Define Port


Create & Generate distribution model
Use transaction BD64 to create a distribution model. Generate partner profiles for the newly
created model view. Distribute model view to the backend system afterwards.
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 13


See also
Please branch to SAP Solution Manager or in the Online Help Portal at http://help.sap.com
SAP Solutions SAP Business Suite SAP Supplier Relationship Mgmt. SAP
Supplier Relationship Mgmt. SAP SRM 7.0 Basic Settings for SAP SRM System
Connections

Maintain and Generate Partner Profiles
Maintain and generate partner profiles for message types ACC_GOODS_MOVEMENT,
ACLPAY, BBPCO, BBPIV, MBGMCR and SYNCH with transaction WE20




See also
Please branch to SAP Solution Manager or in the Online Help Portal at http://help.sap.com
SAP Solutions SAP Business Suite SAP Supplier Relationship Mgmt. SAP
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 14
Supplier Relationship Mgmt. SAP SRM 7.0 Basic Settings for SAP SRM System
Connections

Register and Activate Queues
Registration of Inbound queue
Register inbound queues CSA* and R3A* in transaction SMQR:
1. Press pushbutton Registration
2. Enter CSA* / R3A* in field Queue Name.
3. Press enter.



Registration of Outbound queue

Register outbound queue for the logical destination of ERP client with transaction SMQS:
1. Press pushbutton Registration.
2. Enter logical destination of ERP client in field Destination.
3. Press enter.

Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 15



Other System Connection Settings

Please maintain
Units of Measures, Currencies, Exchange Rates, Locations etc.
Internet Pricing Configurator if relevant
Technical Settings for E-Mail if relevant
Diverse other Control Parameters
SRM Jobs relevant for SRM one client scenarios

Follow the detailed description in SAP Solution Manager SAP Solutions SAP Business
Suite SAP Supplier Relationship Mgmt. SAP Supplier Relationship Mgmt. SAP SRM
7.0 Basic Settings for SAP SRM System Connections

Tips & Tricks:
If you do not intend to use IPC for pricing activate the simplified pricing via BAdI "Pricing" in
transaction SE18 or under SRM Server BAdIs.


Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 16
Organizational Management
SRM organizational structure is used for maintenance of user and organizational entities
attributes as well as for diverse responsibilities determination.

Create Organizational Structure for SRM
Transaction PPOMA_BBP is used for maintenance of the existing organizational model.

Note
Create all SAP Enterprise Core Component (SAP ERP) purchasing organizations to which
suppliers are assigned, from the back-end system. This is necessary to ensure that master data
synchronization works properly.
Set up purchasing groups in SAP Materials Management (SAP ERP) first, and then assign these
to the SAP SRM purchasing groups.


There are three transactions for maintain the SRM organizational model:
PPOCA_BBP Create new Org-Structure
PPOMA_BBP Maintain Org-Structure
PPOSA_BBP Displaying Org-Structure

Tips & Tricks:
Branch to http://help.sap.com Supplier Relationship Management Functions
Administrative Functions User Attributes to find further information relevant for user
attributes in SRM.

Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 17
Create main organizational entities e.g. company, purchasing organization and purchasing
group. Maintain addresses for these entities

See also
Please branch to SAP Solution Manager or in the Online Help Portal at http://help.sap.com
SAP Solutions SAP Business Suite SAP Supplier Relationship Mgmt. SAP SRM
7.0 Basic Settings for SAP SRM Organizational Management User Management
Organizational Structure

Create vendor root
Use transaction PPOCV_BBP for vendor root creation. (PPOMV_BBP for maintenance)


See also
Please branch to SAP Solution Manager or in the Online Help Portal at http://help.sap.com
SAP Solutions SAP Business Suite SAP Supplier Relationship Mgmt. SAP SRM
7.0 Basic Settings for SAP SRM Organizational Management User Management
Define Supplier Structure
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 18

Note
Create a root object before you start with the replication of supplier master data and enter it in the
table BBP_MARKETP_INFO under Vendor Root. The IDs must refer to the values within the
organizational model. Maintenance is possible through Tx SM30.


Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 19
Business Partners
Within SRM the business partner concept is utilized. A business partner record is created for
each user, person, organization or group that can be involved in a SRM business transaction.
Please read the entire chapter and maintain all settings before replication is carried out in the
system!

See also
Please branch to SAP Solution Manager or in the Online Help Portal at http://help.sap.com
SAP Solutions SAP Business Suite SAP Supplier Relationship Mgmt. Master Data
Business Partners

Creation of business partners with and without HR integration
The steps of business partners creation for users depend on the technical scenario used at the
customer. Technical creation of users or technology used, e.g. LDAP, is not discussed here
explicitly.

The following scenarios are the most common:

SAP ERP with SAP ERP HCM system
The SAP SRM system receives the relevant data from the SAP ERP HCM system. The transaction
USERS_GEN is not active in this scenario. The HR users are created via transaction PA40. The
assignment to an organizational unit is carried out here as well. The technical user (i.e. SU01) is
assigned via HR transaction PA30. Select infotype 105 communication and subtype 0001 to
assign the corresponding user ID. Run and schedule job report HRALXSYNC to run
periodically.

Tips & Tricks:
For SAP ERP systems with HCM use transaction BBP_BP_OM_INTEGRATE (report
HRALXSYNC) to replicate the entire organizational plan, i.e. organizational units and
persons. The replicated objects are displayed in transaction BP.

SAP ERP with ALE Connection to an SAP ERP HCM system
Technical users are created.The business partner is created automatically at inbound of ALE
messages. Corresponding HR infotypes are to be created in the target system.

Note
User name must be identical to the SAP ERP HCM system.
Restrictions might apply if e.g. organizational model is used for determination of responsibilities by
other applications than SRM in the ERP system.

SAP ERP without SAP ERP HCM system (standalone)

You include the existing users via transaction USERS_GEN in the SAP SRM system.

In case integration with HR is activated table T77S0 must be maintained
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 20
The table T77S0 is a central control table of the HR integration model. Please use transaction
SM30 for table maintenance. Please set the parameters as described in the table.
Group Sem. abbr. Value
abbr.
Description
HRALX HRAC Activate HR Integration
HRALX MERID X Enter Integration Error in IDOC
HRALX MSGRE 0 Recipient of Error Message When Creating BP
HRALX OADBP 101 Business Partner of Standard Address
HRALX OADRE X Address Necessary for Business Partner?
HRALX OBPON ON Integration O-BP Active
HRALX OBWIG X Ignore Business Partner Warnings
HRALX ONUMB 2 Number Assignment Business Partner (Org. Unit)
HRALX OSUBG 10 Subgroup of Business Partner (Organizational Unit)
HRALX PALEO Log: Organizational Units in ALE
HRALX PALEP Log: Employees in ALE
HRALX PBPHR OFF Employees Are Replicated from HR System
HRALX PCATS Integration P-BP for CATS Active
HRALX PINAC Activate ALE Distribution of Inactive Employees
HRALX PLEVE 3 Log: Detail Level of Error Messages (1 - 5)
HRALX PNUMB 2 Number Assignment Business Partner (Employee)
HRALX PQUAL Import Qualifications
HRALX PRTON Log Active
HRALX PSUBG 10 Business Partner Subgroup (Employees)
HRALX PSYNO Log: Organizational Units in Dialog
HRALX PSYNP Log: Employees in Dialog
HRALX USRAC X Create Relationship to User

Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 21
Screenshot of table T77S0:


See also
Please branch to SAP Solution Manager or in the Online Help Portal at http://help.sap.com
SAP Solutions SAP Business Suite SAP Supplier Relationship Mgmt. SAP SRM
7.0 Basic Settings for SAP SRM Organizational Management User Management

Note
Make the settings for group HRALX as well as for the ALE distribution as described in SAP note
550055 and the here listed related notes.
Schedule job to run report HRALXSYNC periodically (transaction
BBP_BP_OM_INTEGRATE).
Please refer to note 893227 - Replication sequence for vendors and employees for further
information.
Before business partners can be created, replicated and/or generated the corresponding
groupings, number ranges and other technical settings must be maintained in the system.

Define BP number ranges and other settings for business partners
General assumption is that certain basic non-SRM relevant settings, number ranges,
groupings etc. were created at ERP implementation!
Before SRM number ranges are defined the actual Vendor number ranges and the actual
number assigned have to be checked in the ERP system. Assign only available number
ranges to SRM business partners and make sure that there are no overlaps!


Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 22
Customizing path to Number Ranges Definition (transaction BUCF)


The following screen appears:


Please click on Maintain intervals and enter the number range you choose for your SRM
business partners. Example:

Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 23

Note
Two number ranges, one for ERP and one for SRM are required.

Define groupings for BP
Now please navigate to Define Groupings and Assign Number Ranges using the following
navigation path (view V_TB001)


Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 24
Example for BP grouping and its number range assignment.


Define BP Roles
Customizing path is the following: Cross Application Components SAP Business Partner
Business Partner Basic Settings Business Partner Roles Define BP Roles


Please maintain the following business partners roles into the view BUPA_TB003:
BBP000 to BBP006
BUP001 to BUP005

Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 25


Check number ranges for BP relationships


Example of number range for business partner relationships:
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 26


Follow this path to reach the relevant customizing views: Cross Application Components
SAP Business Partner Business Partner Business Partner Relationships Basic
Settings Field Groupings Configure Field Attributes for Each BP Relationship Category


Maintain entry BUR010 Has the Employee here transaction BUBP.

Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 27

Vendor number range and grouping
Follow this path to reach the relevant customizing views:


Example for Vendor master records number range intervals


Tips & Tricks:
In case the business partner generation fails analyze whether some basic technical settings
which are not primarily relevant for SRM one client were not performed in ERP during the
initial implementation.
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 28
Master Data Replication & Synchronization

To enable bidirectional synchronization of master data business partner vendor and
product material/service between SRM one client and ERP following customizing
settings must be maintained.

Preparatory Steps
Read information for master data synchronization.
IMG path Tx. SPRO Cross-Application Components Master Data Synchronization
Preparatory Steps for Master Data Synchronization


Activate Vendor Master Data Synchronization
Follow this customizing path Cross-Application Components Master Data
Synchronization Synchronization Control Synchronization Control Activate
Synchronization Options
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 29


Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 30
Example for active synchronization options.


Note
If you do not want to synchronize certain objects uncheck the Active Indicator, e.g. no
synchronization of SRM business partners with vendors in ECC is required. Deactivate the
entry in column Source Object BP and column Target Object VENDOR.
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 31

Replication and Synchronization of Vendor Master Data
Preparatory Steps
Step 1: Read information for master data synchronization. IMG path SPRO Cross-
Application Components Master Data Synchronization Customer/Vendor integration
Preparatory Steps for Customer-Vendor Integration


Step 2: Assign account groups of the vendor master record to business partner groupings for
the synchronization in direction business partner vendor

Follow the customizing path to view V_TBC001: 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 BP to Vendor
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 32


Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 33
Example:


Step 3: Assign specific BP Role Category for Synchronization in direction BP vendor (for
example, BBP000 - vendor)

Follow the customizing path to view V_TBC002: 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


Step 4: Assign account groups of vendor master record to business partner groupings for
synchronization in direction Vendor Business Partner. This grouping determines the
number range of the Business Partner.

Follow the customizing path to view CVIV_VEND_TO_BP1: 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
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 34



Step 5: Assign account groups of vendor master record to business partner groupings for
synchronization in direction Vendor Business Partner

Follow the customizing path to view CVIV_VEND_TO_BP2: Cross-Application Components
Master Data Synchronization Customer/Vendor Integration Business Partner Settings
Settings for Vendor Integration Field Assignment for Vendor Integration Define BP
Role for Direction Vendor to BP


Maintain Number Assignment for Direction BP to Customer
Follow the customizing path to to view V_TBD001: Cross-Application Components Master
Data Synchronization Customer/Vendor Integration Business Partner Settings
Settings for Customer/Vendor Integration Business Partner Settings Settings for
Customer Integration Field Assignment for customer integration Number Assignment for
Direction BP to Customer

Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 35
Determining Function Modules for Data Exchange: BP
Maintain the following into table CRMC_BUT_CALL_FU using transaction SM30.


Start transaction MDS_LOAD_COCKPIT for replication
Start Synchronisation Process for
Vendor Business Partner
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 36


Tips & Tricks:
Before setting up synchronization of vendors business partners all backend purchasing
organizations to which vendors are assigned must be created in SRM. Use transaction
PPOMA_BBP.
Before replication all product categories, -hierarchies and material- as service master data
have to be deleted with reports COM_HIERARCHY_DELETE_ALL and
COM_PRODUCT_DELETE_ALL.
If the replication progress does not change check the transaction SMQ1 and SMQ2 for the
status of the queue. There it is possible to start the queue directly.

Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 37
Replication and synchronization of the material master data

Note
It is assumed that all material master relevant settings and configurations were carried out
successfully in ERP before the following customizing and the replication will be performed
(product types, product ID length etc.)

Preparatory Steps
Read information for material master data synchronization. IMG path SPRO Cross-
Application Components Master Data Synchronization Material/Service integration
Preparatory Steps for Material-Service Integration

Excerpt from customizing activity documentation:
Customizing of Required Entry Fields in the Material Master Record
The material master record makes it possible to demand that a required entry be made within a view for
fields. In the context of master data synchronization between the product and the material master, there
are two possibilities:
a) You do not define any new fields as required entry fields in the views Basic Data 1 and Basic Data 2
(Processing Status K) or Purchasing (Processing Status E).
b) If you do define new fields as required entry fields in these views, you must implement the Business
Add-In Enhancements for Material Master to Product Mapping and define fixed values for mapping there
for these fields.
The service master record makes it possible to demand that a required entry can be made within a view
for fields. In the context of master data synchronization between the product and the service master,
there are two possibilities:
a) You do not define any new fields as required entry fields in the views of the service master.
b) If you do define new fields as required entry fields in these views, you must implement the Business
Add-In Enhancements for Service Master to Product Mapping and define fixed values for mapping there
for these fields.
Harmonizing Number Ranges for Material Master/Service Master and Product
When a material master or a product (product type material) is created in the context of master data
synchronization, then the system creates the corresponding target object with the identical identifier.
This system behavior has the following effects on number range assignment:
In the case of internal number assignment for the product and the material, the number range
intervals of both objects may not overlap. Both number range intervals are independent of each
other, and could be updated differently.
In the case of external number assignment for the product and the material, the number range
intervals of both objects may not overlap either. If the number ranges do overlap, you must
take organizational steps to ensure that identical identifiers are assigned.
When a service master or a product (product type service) is created in the context of master data
synchronization, then the system creates the corresponding target object with the identical identifier.
This system behavior has the following effects on number range assignment:
In the case of internal number assignment for the product and the service master, the number
range intervals of both objects may not overlap. Both number range intervals are independent
of each other, and could be updated differently.
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 38
In the case of external number assignment for the product and the service master, the number
range intervals of both objects may not overlap either. If the number ranges do overlap, you
must take organizational steps to ensure that identical identifiers are assigned.

Activate Material Master Data Synchronization
Follow this customizing path to view: MDSV_CTRL_OPT_B


Example:
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 39



Start transaction MDS_LOAD_COCKPIT for replication
Start Synchronisation Process for
Material Type Product Category
Material Group Product Category
Service Category Product Category


Tips & Tricks:
If the replication progress does not change check the transaction SMQ1 and SMQ2 for the
status of the queue. It is possible to start the queue directly.
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 40
Activate Creation of Postprocessing Orders
During the synchronization of master data various errors or other problems might occur. The
postprocessing office will collect those problems in postprocessing orders. Those orders can
later be re-processed or deleted. The postprocessing needs to be activated for all processes
that shall be monitored.

Refer to the preparatory steps for synchronization control excerpt:
Activation of the Postprocessing Office for Synchronization Processes
Since the Postprocessing Office is connected for master data synchronization by means of the
Synchronization Cockpit, you must ensure that the creation of postprocessing orders has been
activated for the business processes of the software component AP-MD. If you do not do so,
you will not be able to carry out initial synchronization using the Synchronization Cockpit.
Registration of Queues for Background Processing
You must ensure that the queues for background processing of the synchronization processes have
been registered and activated correspondingly. Since the queues in the background processing of the
individual synchronization processes within a synchronization run are numbered sequentially, the queue
names must be generically registered, by entering a * at the end of the queue name.


Follow the customizing path to view /SAPPO/VA_BPROC
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 41


Maintain the entries within view /SAPPO/VA_BPROC.
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 42


Activate PPO Requests for Platform Objects in the Dialog
Follow this customizing path to view: MDSV_CTRL_OBJPPO.
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 43


Follow the customizing path to view


See also
Go to http://help.sap.com for further information regarding SAP Postprocessing Office.
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 44
Non-SRM One Client specific Basic SRM and ERP
Settings
Further details regarding standard SRM and ERP customizing settings are not discussed in
this document. Generally, the SRM one client system set up does not differ from regular SRM
system.
The most important SRM settings for SRM One Client scenarios are mentioned shortly
including the path SRM 7.0 solution manager content.
Customizing of ERP processes necessary for SRM One Client is not discussed explicitly.

See also
Go to http://help.sap.com SAP Business Suite SAP SRM 7.0 Business Scenarios
(excerpt):
Self-Service Procurement (Classic)
Service Procurement Requesting External Staff
Processing Shopping Carts
Processing Sales Orders in SUS
Entering Services in SRM
Entering Invoices in SRM
Operational Contract Management
etc.

The scenarios released within the SRM one client:
Service Procurement External Staffing in standalone deployment
Self-Service Procurement in classic deployment
SUS in connection with Service Procurement (EBP-SUS) and with Self-Service
Procurement (MM-SUS).
Operational usage of contracts: manual creation of local contracts and their assignment
as sources of supply
Request for Proposal (RFP) only in connection with the external staffing scenario for
service procurement in local deployment

Cross application settings and SRM Business Workflow
Descriptions of the SRM Business Scenarios as well as the Technical Scenarios can be found
in SAP Solution Manager SAP Solutions SAP SRM Configuration Structures SAP
SRM 7.0 Basic Settings for SAP SRM

Cross Application Settings
Hierarchies
Number Ranges for Documents (within SRM)
Define Transaction Types
Switch on Version Control
Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 45
Business Workflow Process-Controlled Workflow
Application-Controlled Workflow
Settings for Tax Calculation
Settings for Account Assignment
etc.

Business Package for SRM 7.0
Descriptions of the SRM Business Scenarios as well as the Technical Scenarios can be found
in SAP Solution Manager SAP Solutions SAP SRM Configuration Structures SAP
SRM 7.0 Basic Settings for SAP SRM Business Package for SAP SRM 7.0
Install and configure the SRM Business Content for Enterprise Portal. The use of Enterprise
Portal for SRM 7.0 is mandatory!

Note
The business content delivered is not SRM One Client specific. Further configuration of
iViews and other portal content might be required within your project!
Refer to chapter Business Partners regarding the portal user management concepts and
user/business partner concepts possible within SRM.

Gelscht: 08.01.2009
RKT Collateral 28.01.2009
SAP SRM One Client 46
Settings for Self-Service Procurement
The central and mostly used scenario is the self-service procurement. Please find further
information for configuration in the SAP Solution Manager SAP Solutions SAP SRM
Configuration Structures SAP SRM 7.0 Basic Settings for Self-Service Procurement.

Note
Self Service Procurement is mostly connected to an external or internal content engine i.e.
Catalog. In case you utilize SRM-MDM catalog please branch to SAP Solution Manager
SAP Solutions SAP SRM Configuration Structures SAP SRM 7.0 Basic Settings
for SRM-MDM Catalog (Catalog Content Management)

Settings for Service Procurement including SUS
Find details and further information for Service Procurement at SAP Solution Manager
SAP Solutions SAP SRM Configuration Structures SAP SRM 7.0 Basic Settings
for Service Procurement

Note
For details regarding SRM-SUS branch to SAP Solution Manager SAP Solutions SAP
SRM Configuration Structures SAP SRM 7.0 Basic Settings for Service Procurement
Settings for SAP SUS

Gelscht: 08.01.2009