srm quick guide v1701

SAP SRM 7.01 / EHP5 for SAP ERP 6.0

September 2011

English

Quick Guide to Implementing the SAP Best Practices for SRM Package V1.701

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

SAP Best Practices Quick Guide to Implementing the SAP Best Practices for SRM Package V1.701

Copyright

© 2011 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

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.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

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.

© SAP AG of 71


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 AG of 71


Contents

1 Purpose................................................................................................................. 7

2 Solution Overview.................................................................................................8

3 System Setup & Preparation – System Administrator...........................................9

3.1 Install SAP ERP....................................................................................................9

3.1.1 Release and Support Package Level.....................................................................9

3.1.2 Required SAP Components.................................................................................10

3.1.2.1 SAP ERP Core Components 6.0 (SAP ECC 6.0)................................................10

3.1.2.2 SAP ERP 6.0 Application Server ABAP with Component SRM Server of Enhancement Package 5 Support Package Stack 5 for SAP ERP 6.0 - "SRM Server of “SAP ERP 6.05” SPS06 AS ABAP"......................................................10

3.1.2.3 SAP ERP Lean Catalog.......................................................................................13

3.1.2.4 SAP Frontend Components, for Example SAP GUI for Windows and SAP NetWeaver Business Client.................................................................................13

3.1.2.5 SAP Best Practices All-in-One Add-on and SAP Best Practices Solution Builder Add-on................................................................................................................. 14

3.2 General Client Settings.......................................................................................15

3.3 Cross Client Settings...........................................................................................15

3.4 NetWeaver Business Client – Activate Context Menu Additional Details............16

3.5 SAP Enterprise Extensions Sets and Enterprise Business Functions.................17

3.6 SAP Notes and Messages..................................................................................17

3.7 SRM-specific Pre-Activation Activities.................................................................21

3.7.1 Maintain Integration Engine.................................................................................21

3.7.2 Fix Possible Inconsistency in BBP_BAPI_PO.....................................................21

3.7.3 Deactivate BBP-BAdI Implementations of BAdI HRALX_HRALXSYNC_BADI....22

3.7.4 SLD Connection..................................................................................................23

3.7.5 VMC and IPC.......................................................................................................24

3.7.6 Execute Report RHSOBJCH...............................................................................25

3.8 Generic Pre-Activation Activities.........................................................................25

3.8.1 Set Up of http and https Services........................................................................25

3.8.2 Activation of Services for SAP Best Practices Solution Builder...........................26

3.8.3 Deselecting Activation Links in BC Sets..............................................................26

3.9 Maintain Profile Parameters................................................................................27

3.9.1 SAP Scripting......................................................................................................27

3.9.2 Authentication Using SAP Logon Tickets............................................................27

3.9.3 Set Default Timeout for http and https Services..................................................29

3.10 Creating User for Activation of SAP Best Practices Content...............................29

4 Activation of Business Content / Scenarios – Activation Consultant...................32

© SAP AG of 71


4.1 Initial Check of System Readiness......................................................................32

4.2 Check Content Prerequisite in the Client............................................................32

4.3 Scenarios to be Activated...................................................................................33

4.4 Activation Language............................................................................................33

4.5 User Settings for Activation.................................................................................33

4.5.1 Deactivate Info Dialog Box on Dynpro Size Check..............................................33

4.5.2 SAP Software Change Registration (SSCR): Developer Key..............................34

4.5.3 Unicode Settings.................................................................................................34

4.5.4 Allow GUI Scripting..............................................................................................35

4.5.5 Set Decimal Notation and Date Format...............................................................35

4.6 Getting the Business Content for Activation........................................................36

4.6.1 Getting the Solution Scope File...........................................................................36

4.6.2 Getting the Installation Data Files........................................................................37

4.6.3 Creating a Folder for the SAP Best Practices Activation.....................................37

4.7 Activation of Scenarios........................................................................................38

5 Error Handling: Installation Errors during Activation – Activation Consultant......43

5.1 Error Occurs During Activation of Automated Task.............................................43

5.1.1 General Issue- Inconsistencies in SOBJ..............................................................44

5.1.2 General Issue- Runtime Error PXA_NO_FREE_SPACE.....................................45

5.1.3 S00- Check IPC Configuration.............................................................................45

5.1.4 S03 – WE31: Creation of IDoc Z1P550* Transfer Structures..............................45

5.1.5 S03 - Organizational Model: Manual Upload of ORG Model Template................46

5.1.6 S03 - Organizational Model: Manual Upload of ORG Model Template................47

5.1.7 S03- Organizational Model: Set Attribute for Delivery Address...........................48

5.1.8 S03 - Activate Synchronization Options...............................................................49

5.1.9 S03 -Initial Replication of Material Data...............................................................51

5.1.10 S03 -Initial Replication of Material Type / Material Group / Material Data............51

5.1.11 S03 -Initial Replication of Vendor Data................................................................52

5.1.12 S03 - Change Client-specific Configuration Parameters......................................53

5.1.13 S03 - Contact Person / Service Agent.................................................................53

5.1.14 S03 –Maintain the Vendor Business Partner.......................................................54

6 Evaluate Business Content / Scenarios – Business Consultant..........................55

6.1 Review of Business Scenarios............................................................................55

6.2 List of Default Values and Personalized Values..................................................56

7 Issues during Usage of Activated Package – Business Consultant....................57

7.1 FI Integration for Invoicing...................................................................................57

7.1.1 Check Tax Type for GL Account..........................................................................57

7.1.2 Invoicing Error Tax code XX does not exist, check entries..................................57

7.2 External Catalog Integration................................................................................58

© SAP AG of 71


7.3 Lean Catalog Integration NWBC Usage – white Page after Item Transfer..........58

7.4 Performance Issues for Scheduled Jobs.............................................................59

7.5 Customizing for Team Purchasing is Missing.....................................................59

8 Frequently Asked Questions (FAQ) – Business Consultant................................60

8.1 HR/HCM Integration............................................................................................60

8.2 NWBC Personalization........................................................................................60

8.3 NWBC / Portal Integration...................................................................................60

9 Further Information – Business Consultant.........................................................62

9.1 Use of SAP Portal...............................................................................................62

9.2 Use of SAP Best Practices Roles for Demo and Evaluation...............................62

9.3 Reporting............................................................................................................62

9.4 Lean Inbox..........................................................................................................64

9.5 Workflow Adjustments.........................................................................................65

9.6 Simplified Pricing.................................................................................................66

9.7 BAdI for Transfer of Shopping Cart Number to Purchase Documents................66

10 Security Aspects - System Administrators..........................................................69

10.1 User Administration and Authentication..............................................................69

10.2 RFC Destinations................................................................................................69

10.3 Roles Management.............................................................................................69

© SAP AG of 71


Quick Guide to Implementing the SAP Best Practices for SRM V1.701

1PurposeThis quick guide provides step by step information you need to implement the complete SAP Best Practices SRM package using the SAP Best Practices solution builder.

Before proceeding with this document you must have,

The scope relevant defined for you

Finalized technical prerequisites

Required resources available (see involved roles)

This document does not provide a general overview and explanations of SAP Best Practices. For more information about content and positioning, see the SAP Best Practice documentation CD/DVD.

This document is intended for

System administrators and basis consultants

o System Set up & Preparation incl. troubleshooting.

Activation consultants (can be also basis consultants)

o Activation of Business Content / Scenarios

Business consultants

o Evaluate Business Content / Scenarios incl. troubleshooting

o FAQ and further information for extended usage the package

who already have a sound knowledge of SAP Best Practices, including the tools and documentation.

The following sections are assigned to the roles required for the successful installation of the SAP Best Practices package for SRM.

© SAP AG of 71


2 Solution Overview

SAP Best Practices for Supplier Relationship Management (SRM) V1.701

Is based on SAP SRM 7.01 on top of SAP ERP (One client installation, which is based on an add-on installation on ECC)

Provides an accelerated deployment (compared to SRM) of the required configuration settings.

Provides procurement features of ECC 6.0 – Ehp5 bundled with SRM 7.01 in an concise package and contains two predefined business scenarios (supported for one client installation):

Self Service Procurement (Procure-to-Pay)

Strategic Sourcing with Request for Quotation (RFQ)

Is targeting on customer that:

are aiming on simple procurement scenarios

do not yet use SAP SRM

are using only one Backend (ECC) system

Requires a client in the backend (ECC) system:

which was set up based on SAP Best Practices content (e.g. SAP Best Practices for Baseline Package V1.605) or which contains the basic configuration settings (see also chapter “Check Content Prerequisite in the client”) in the area of Logistics, Materials Management, Financial Accounting and Controlling

The SAP Best Practices for SRM package only contains the SRM specific configuration settings!

© SAP AG of 71


3 System Setup & Preparation – System Administrator

3.1 Install SAP ERP Prior to installing and activating a SAP Best Practices package (SAP BP package), the target SAP Application Server (AS) must be installed with the Support Package Stack (SPS), specified in this section and the SAP Notes as specified in detail in section SAP Notes and Messages in this guide.

For SAP Best Practices for SRM this is also SAP ERP AS ABAP, because the SRM functionality used in the SAP BP for SRM package (one client installation) is based on SAP ERP.

3.1.1 Release and Support Package Level The deliverables of SAP Best Practices (BP) packages were developed and tested in a system landscape with specific SPS levels. If the SPS level in your system is different, there may be errors during the activation. You may be able to perform the activation activities manually using the configuration guides, but errors may still occur.

Make sure that your system meets the minimum SPS level requirements. In case your system has an exceptional SPS level compared to the SAP Best Practices requirements, only LIMITED SUPPORT can be provided.

If you need a higher SPS level in your system, for example because of additional functionality, FIRST import and activate SAP Best Practices on the SPS levels as mentioned below, THEN upgrade your system to the current SPS level.

The support package levels relevant for SAP Best Practices for SRM V1.70 are listed together with the required components in the next section.

Receiving the Software at the Correct SP Level

For delivery of the software, an installation number and a corresponding license agreement are required. An S-USER is required to order software in the Software Catalog or download from SAP's Software Distribution Center within SAP's Service Marketplace (SAP's SWDC in SMP). You can only order unrestricted SAP software. Contact the SAP contract department to ask for a physical shipment or create a customer message on component XX-SER-GEN-CONTR.

For downloading SPSs, use the Maintenance Optimizer within your SAP Solution Manager. You can also select relevant SPs manually one-by-one via SAP's SWDC in the SMP:

https://service.sap.com/swdc Download Support Packages and Patches Support Packages and Patches - Entry by Application Group SAP Application Components SAP ERP SAP ERP ENHANCE PACKAGE EHP4 FOR SAP ERP 6.0

© SAP AG of 71

https://service.sap.com/swdc


Only the current Service Release (SR) is delivered to SAP customers / partners via SAP's SWDC in SMP and standard delivery (for example, Software Catalogue). If you encounter the situation that the required SPS for correct SAP BP packages activation is based on SPS level LOWER than the current SR, the request for the necessary SPS is handled via a customer message. For details, see the SAP Note 925690 - Standard Ordering Procedures for SAP Software (https://service.sap.com/sap/support/notes/925690).

3.1.2 Required SAP Components

3.1.2.1 SAP ERP Core Components 6.0 (SAP ECC 6.0)You can find detailed information for SPS definition for the SRs of SAP ERP, in SAP Note 774615 – Support Package levels of ERP/ECC installations/upgrades.

3.1.2.2 SAP ERP 6.0 Application Server ABAP with Component SRM Server of Enhancement Package 5 Support Package Stack 5 for SAP ERP 6.0 - "SRM Server of “SAP ERP 6.05” SPS06 AS ABAP"

SAP ERP 6.0 based SAP BP packages focus mainly on the set of software components bundled in SAP ECC 6.0. However a complete update of all ABAP software components of enhancement package 4 for SAP ERP 6.0 is technically not required for the use of SAP Best Practices for SRM V1.70.

In the following list you see the software components bundled within the SRM Server of SAP ERP 6.05 SPS05 AS ABAP:

Software Component

Release SP Level Description

SAP Basis 7.02

(SAP_BASIS)

702 0008 SAP Basis Component

SAP ABA 7.02

(SAP_ABA)

702 0008 Cross-Application Component

PI Basis 7.01

(PI_BASIS)

702 0008 Basis Plug-In

SAP Web UIF 7.01

(WEBCUIF)

701 0005 SAP WEBCUIF 700

SAP BS Foundation 7.02

(SAP_BS_FND)

702 0006 SAP Business Suite Foundation

SAP BW 7.02

(SAP BW)

702 0008 SAP Business Warehouse

SAP APPL 6.05 605 0005 Logistics and Accounting

© SAP AG of 71

https://service.sap.com/sap/support/notes/774615



(SAP_APPL)

SRM SERVER 7.0*

(SRM_SERVER)

701 0005 SAP enhancement package 4 SPS06 for SAP ECC 6.0 (ABAP) is in sync with Support package level SP07 of SRM_SERVER 700 and SRM_EXT_FUNC 700

SRM SERVER

SRM_EXT_FUNC 7.0*

(SRM_EXT)

701 0005 SRM Extended Functionality for SRM_SERVER including PPS

* The SRM add-on 7.01 consists of two ABAP software components: SRM_SERVER 701 and SRM_EXT 701.

Usually required software components and SP levels are downloaded using the Maintenance Optimizer of SAP Solution Manager. If you need to download manually from SAP's Software Distribution Center in Service Marketplace please follow below given path:

Installation:

https://service.sap.com/swdc SAP Software Distribution Center Download Installations and Upgrades Entry by Application Group SAP Application Components SAP SRM SAP SRM 7.0 / NW7.01 Installation and Upgrade <Select your target DB> 51036866, "DVD SAP SRM 7.0 SR1/NW7.01 SR1 Installation Export "

Support Packages:

https://service.sap.com/swdc SAP Software Distribution Center Download Support Packages and Patches Entry by Application Group SAP Application Components SAP ERP SAP ERP Enhancement Package EhP4 for SAP ERP 6.0 / NW7.01 Entry by Component SRM Server SRM Server 7.0

The combination of the SAP best Practices for SRM package with other SAP Best Practices packages (e.g. SAP Best Practices for Baseline package) a complete update of all ABAP software components of enhancement package 4 for SAP ERP 6.0 might be required.

Detailed information regarding the installation of enhancement package 4 for SAP ERP 6.0 can be found in SAP Note 1143022 - Installation of Enhancement Package 4 on SAP ERP 6.0.

As outlined in SAP Note 1064635, SPS levels for SAP ERP are synchronized throughout all enhancement package versions. Software components and add-ons not used within an enhancement pack should have the SP level assigned to the concurrent SPS of SAP ECC 6.00.

Attached to note 1386389 is SAP BAiO/BP: Stack Information/Explanation for Used Products, an overview of all software components and their support package levels combined in the various support package stacks is given.

SRM specific Customizing

The SRM software components (Add-ons) contain client dependent customizing which is only imported into client 000. These standard customizing entries have to be transported (for example, by using transaction SCC1) after the installation of the SRM software components from client 000 to already existing target clients. Target

© SAP AG of 71






clients are those for which you would like to use the SRM functionality and in which you are going to activate the SAP Best Practices for SRM package.

The transport of these customizing entries from client 000 to the desired client has to be done before activating the SAP Best Practices for SRM package. To transport the missing customizing to the target client, perform the following steps:

1. Run transaction SAINT and choose menu entry Goto Support Packages in the system.

In case an error message appears when entering transaction SAINT “No valid maintenance certificate found for system xxx” please request the required maintenance certificates.

As of 2009, maintenance certificates are required to be able to install and maintain SAP Software using the tools Add-On Installation Tool and Support Package Manager. These maintenance certificates can be requested using SAP Solution Manager and distributed automatically to the systems to be maintained.

For more information, see the SAP Support Portal under:

http://service.sap.com/maintenancecertificate and SAP Note 1240265

2. Look for the packages

- SRM_SERVER and- SRM_EXT

The list of imported support packages is displayed with date and time of the import.

3. Choose the support packages which have been imported after the creation of your development client. The transports of these support packages need to be copied to the target client to get the client dependent settings.

4. Create a new mode and run Transaction SCC1

5. Enter the transport of the related support package, like SAPK-70004INSRMEXT (support package 04 of SRM_EXT).

6. Enter the source client (normally client 000) and import client.

7. Select the Including Request Subtask option

8. Start the copy with Start immediately (Copy in Foreground (F5))

9. Repeat it with every required support package transport.

Only client dependent settings are copied during the transport copy. Client independent settings and workbench objects are not taken into account.

There might be customizing conflicts and that existing customizing settings might be overwritten in the target client. For more information, see SAP Note 337623.

© SAP AG of 71

http://service.sap.com/maintenancecertificate%20and%20SAP%20Note%201240265


3.1.2.3 SAP ERP Lean Catalog

The following SAP Add-ons must be imported into the system:

SAPCCMAN 311 000

For more information, see note 755052

This Add-on contains the central catalog tool "Catman". This tool controls the manual data entry and Quality control.

SAPCCLCT 102 000

For more information, see note 1509352

This Add-on contains the SAP ERP Lean catalog based on ABAP WebDynpro.

If you want to activate this scenario, additional payable Add-on components are needed. See also note 1509352 for details. Contact: Peter Reske ([email protected])

3.1.2.4 SAP Frontend Components, for Example SAP GUI for Windows and SAP NetWeaver Business Client

Ensure that you have installed the latest and appropriate SAP frontend components.

The following download path below leads you to an overview on how to install SAP frontend components and how to apply patches. On the navigation level SAP Frontend Components, you can select the SAP frontend components depending on your requirements.

To download the SAP frontend components, go to the Software Distribution Center (SWDC) on the SAP Service Marketplace:

https://service.sap.com/swdc, then choose Download Support Packages and Patches Support Packages and Patches - Entry by Application Group SAP Frontend Components

Download the version SAP NetWeaver Business Client 3.0.

NWBC v3.0 is specifically released for all SAP Business All-in-One customers with SAP NetWeaver 7.01 SP06 against a single ABAP stack.

SAP NetWeaver Business Client 3.0: SAP NWBC 3.0 is the mandatory user interface connected to SAP BP for SRM. The minimum technical prerequisite is enhancement package 1 Support Package Stack 6 for SAP NetWeaver 7.0 application server ABAP ("SAP NW 7.01 SPS06 AS ABAP"). We strongly recommend useinthe related application support package stack – enhancement package 4 Support Package Stack 6 for SAP ERP 6.0 application server ABAP ("SAP ERP 6.04 SPS06 AS ABAP") as a minimum, which is available as of April 12, 2010.

© SAP AG of 71



In addition, you need to import the corrections referred to in SAP Note 1353538 - "SAP NetWeaver Business Client 3.0 - Patch Collection". This note is also listed in the section SAP Notes and Messages of this document.

3.1.2.5 SAP Best Practices All-in-One Add-on and SAP Best Practices Solution Builder Add-on

The following SAP Best Practices Add-ons must be imported into the system:

Software Component

Release Version Description

BP-ERP (1) 605 V[xy]

Use the latest version as outlined in SAP Note 1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons

For more information, see the document Importing SAP Best Practices Add-Ons (ADDONINS.PDF) on the configuration DVD.

SAP Best Practices All-in-One based on ERP 6.0 (ECC 600, EhP4)

This Add-on contains the SAP Best Practices technical framework (for example, BC-Sets, eCATTS, print programs)

BP-SOLBLD (1) 70 V[yz] Best Practices Solution Builder on EHP5

This Add-on contains the SAP Best Practices solution builder program

(1) Additional and detailed information is listed in the document Importing SAP Best Practices Add-Ons (ADDONINS.PDF) on the configuration CD.

To download the SAP Best Practices Add-ons, go to the Software Distribution Center (SWDC) on the SAP Service Marketplace:

https://service.sap.com/swdc, then choose Download Installations and Upgrades Installations and Upgrades - Entry by Application Group SAP Best Practices SAP BP FOR SRM SRM - V1.701.

Regular Updates Technical Environment

The technical add-ons provided by SAP Best Practices form the technical environment required for the automated implementation of your SAP Best Practices version with the SAP Solution Builder. This technical framework is continuously updated providing enhanced, fixed, or additional technical objects required for the technical implementation process.

SAP Best Practices therefore offers updated versions of the add-ons on a regular basis. Each updated add-on replaces the previous version in your system. For more information about the currently available versions of the add-on BP-ERP and the add-on BP-SOLBLD, see SAP Note 1301301 (The relevant content and execution of SAP Note 1301301 is included in the section SAP Notes and Messages of this document.)

Since the solution scope file and the most current installation data files always correspond to the current technical add-ons, you always need to make sure the most current versions are in your system before the technical implementation of your SAP Best Practices version starts.

© SAP AG of 71



The update of the technical framework has no impact on scope or business content of your SAP Best Practices version as it is described in the respective documentation.

3.2 General Client SettingsTo check and maintain the settings of clients in your system, use transaction code SCC4.

Client Role: The system cannot have any clients with a role of productive client. If the system contains a productive client, extension sets cannot be activated as required. Additionally, the automatic activation of SAP Best Practices content using the SAP Best Practices solution builder is not allowed in a productive client, because BC sets cannot be activated in the productive system.

Changes and Transport for Client Specific Objects - Automatic recording of changes required: In order to activate a SAP Best Practices packages automatic recording of changes is required. This flag means that all the changes are automatically recorded in a change request.

Cross Client Object changes - Changes to Repository and cross-client Customizing allowed required: During the activation of a SAP Best Practices package cross-client objects are created. Cross-client functions include all cross-client customizing objects (e.g. factory calendar, definition of price list conditions, printer controls). But in particular they also include all objects of the SAP Repository (e.g. Reports, module pools, screens, Dictionary etc.). In the following chapter you can find a list of cross client customizing settings created during the activation of the SAP Best Practices for SRM Package.

In case you have not maintained the setting as described (Changes to Repository and cross-client Customizing allowed) you will be asked during the activation of the package if these settings have to be done automatically by the solution builder. In case your reject the required changes the activation cannot be executed automatically.

3.3 Cross Client Settings The following cross client customizing settings and repository objects are created during the activation of the SAP Best Practices for SRM package. Refer to the section in the configuration guide to analyze possible conflicts in your system landscape.

Configuration Step and Chapter in Configuration Guide

Building Block

Type Comment

Define logical system for SRM

S00 Cross client customizing

If the logical system is already maintained and assigned no changes will be done during activation.

Maintaining Client Settings


Customizing Switches S00 Cross client customizing

Activate Services S00 Services Maintenance of

© SAP AG of 71


Configuration Step and Chapter in Configuration Guide

Building Block

Type Comment

Services affects all clients. No transport request is created.

Define RFC Destinations

S00 RFC Destination No transport request is created.

Creation of IDoc Z1P550* Transfer Structures

S03 Repository objects IDOC transfer structures have to be created in customer namespace which are used for the upload of the ORG Model Template.

Creation of HR Users:

Create Transaction Z_PASRM

S03 Repository objects This transaction is created in the customer namespace in order to simplify the manual creation of HR- users

Delete Logical Systems for Postprocessing Office


Maintain Standard Setting for SAP Business Workflow

S03 RFC Destination

Cross client customizing

This activity is a manual step during the activation and can be therefore checked during the activation process.

3.4 NetWeaver Business Client – Activate Context Menu Additional Details

To use the specific functions in SAP NetWeaver Business Client, you must activate the context menu Additional details in the transaction PFCG. In order to use the context menu you have to maintain the client-independent table SSM_CUST:

1. Access transaction SM30:

2. Choose the table/view: ssm_cust.

3. Choose the Maintain.

4. Choose New Entries.

5. Choose ADD_MENU_DETAILS.

6. Set value to YES.

© SAP AG of 71


7. Save your settings.

3.5 SAP Enterprise Extensions Sets and Enterprise Business Functions

Use

After installing SAP ERP, the following SAP ECC extension sets need to be activated before you start activation of SAP Best Practices for SRM.

Activating enterprise extensions, business functions, and business function sets makes permanent changes to your system and cannot be undone. For more information about the impact, see the documentation of the related extension or business function.

Procedure

1. Run the following activity:

IMG Menu Activate SAP ECC Extensions

Transaction Code SFW5

2. On the Switch Framework: change Business Function Status screen, select each of the following entries (by marking the column Planned Status) and then choose the Activate Changes button:

Enterprise Extensions

Planned Status

Remarks

No specific enterprise extensions need to be activated Inherited from SAP ERP backend system

Depends on your backend ERP settings

Enterprise Business Functions

Planned Status

Remarks

/KYK/GEN_AIO_SIMPLIFICATION

ON SAP All-In-One Roles

3. The system displays an informational dialog box. Choose Continue.

4. Choose Back.

3.6 SAP Notes and MessagesIf issues become apparent after shipment of this SAP Best Practices Package (and hence of this document), an SAP Note exists to document how to solve the issues.

© SAP AG of 71


Before you start the activation of the related SAP Best Practices scope, check the latest version of the SAP Note for BP SRM below to obtain updates and corrections for problems that have not become apparent until after shipment.

All SAP Notes have to be applied to the system via the SAP Note Assistant. All SAP Notes mentioned below need to have the implementation status Completely implemented. Some SAP Notes require manual action before you set the status to completely implemented.

To avoid activation errors as a result of generating loads, you have to perform a mass generation using transaction SGEN as described in the SAP Note 481548.

SAP Note # Description Component Area Remark

1606895 SAP Best Practices for SRM V1.701

SV-SMB-AIO-BP-SRM

General Info

Always check the SAP Note for Best Practices for SRM Package DE V1.701 for updates on the implementation of SAP Best Practices for SRM

The following SAP Notes must be implemented (if not stated otherwise in the SAP Note mentioned above):


1301301 Release Strategy for SAP Best Practices Package ABAP Add-ons

SV-SMB-AIO-BP

Acti-vation

Note 1301301 refers to other notes. In summary:

The SRM package is based on enhancement package 4 for SAP ERP 6.0. Therefore, you need the following Add-ons:

- BP-ERP 605V1 or higher

The relevant note for the Best Practices Add-On BP-ERP 604Vx is referenced in SAP Note 1301301. Always check this referenced note and follow the instructions.

Attached to this add-on specific note you can find the corrections for the add-on. Always apply the correction transport for the corresponding add-on

- BP-SOLBLD 70V5 or higher

The relevant solution builder overview note for your solution builder version is referenced in note 1301301. Always check this referenced note, follow the instructions and apply the

© SAP AG of 71



mentioned notes.

1368177 NWBC v3.0 for BAiO BC-WD-CLT-BUS

Usage Not required – this note contains only text and is the starting point for the installation of the NWBC 3.0 for BAIO. Please skip the steps mentioned in this note and refer to the referenced and important notes which have to be executed:

- 1353538 (see below)

- 1400383 (see below)

1353538 SAP NetWeaver Business Client 3.0 - Patch Collection

BC-WD-CLT-BUS

Usage Note 1353538 refers to other notes. Check which notes are required for your system landscape or NWBC.

1400383 SAP BAiO: SAP NWBC 3.0 & EhP4 for SAP ERP 6.0 (ABAP), Config

BC-WD-CLT-BUS

Usage This note describes in detail how to set up the NWBC. Check with your system administrator in case of questions. This note requires deep basis knowledge.

1239471 BP DX:Changes to BP address data not replicated

AP-MD-BP-DX Acti-vation

Needs to be implemented to avoid problems during creation of the PD Org structure

570861 Checking the size between subscreens and elements

BC-FES-GUI Usage Only refer to the section for end users: and deactivate the dialog box for screen size check manually.

1433603 NWBC causes locks in Web Dynpro applications

BC-WD-CLT-BUS

Usage

517484 Inactive services in the Internet Communication Framework

BC-MID-ICF Usage Activate the virtual host and services using the transaction SICF.

Do not refer to the referenced note: 1131945 - Active services for SRM 6.0 in transaction SICF Skip this section.

1456162 Navigation to catalog is cancelled in IE8

SRM-EBP-CAT Usage

1436150 SRM70: BP inbound processing: Role and bidder indicator

SRM-EBP-ADM-XBP

Activation

Solves Issue during Replication

1605994 AS ABAP 7.02.08: eCATT / Error in parser of ABAP statement

BC-TWB-TST-CAT CATT

Activation

This note fixes an issue which caused trouble in Ecatts containing Inline ABAP.

If you are going to enhance the scope of the SAP Best Practices for SRM package, the following notes might be important. They provide additional data for productive use of the scenarios.

© SAP AG of 71


You do not have to apply these notes in the system. They are not relevant for the activation and usage of the SAP Best Practices for SRM package. They simply provide additional information.


1398626 SRM@ERP: Mass generation of employees from users

PA-PA-XX Info SRM@ERP: Mass generation of employees from users

33582 Transport dialog box when saving personnel planning data

BC-BMT-OM Info In the SRM One client scenario the following entry should exist in table T77S0:

TRSP CORR X Transport Switch (X = No Transport).

Otherwise issue may occur on creation of a contact person for a supplier/bidder with user or when changing personal user settings

Note: During activation of SAP Best Practices for SRM we switch off transport request.

1437987 Release of Portal-Independent Navigation Frame for SRM 7.0

SRM-EBP-CA-UI

Info This note provides an overview what to do to use NWBC 3.0 in SRM 7.0

However: The required steps for NetWeaver described in the mentioned note 1437317 are already described in note 1353538 (see section above) no action required at this point.

The SRM note 1435692 is already mentioned in the section above and mandatory to apply.

The SRM Note 1430999 contains a list of notes that are not directly relevant for the BAIO package only apply these notes in case of issues during usage. no action required at this point.

© SAP AG of 71



1172901 SAP SRM add-on 7.0 for ERP 6.0 EHP4

BC-UPG-ADDON

Info Note provides upgrade Info for SRM 7.0

337623 Customizing after installation or upgrade

BC-UPG-ADDON

Info Required customizing entries which are part of SRM add-on have to be brought from SAP sample client 000 to a desired target client

3.7 SRM-specific Pre-Activation Activities

Use

After installing SAP ERP and the other needed SAP components, applying the required SAP SP and SAP Notes, and importing the SAP Best Practices add-on, you can prepare your system for activation.

3.7.1 Maintain Integration Engine

Use

The purpose of this activity is to configure the integration engine.

Procedure

1. Access the activity using the following navigation options:

Transaction Code sxmb_adm

2. Choose Integration Engine Configuration

3. Choose menu Edit Change Global Configuration Data

4. Make the following entries

Field Name Description User Action and Values

Note

Role of Business System

Role of Business System LOC Application System

5. Choose Save

3.7.2 Fix Possible Inconsistency in BBP_BAPI_PO

During upgrade to ERP6.0 EhP4/5 inconsistency can occur preventing correct re-read of backend document from SRM in ERP. If this inconsistency exists in your system dumps occur occasionally. This is mostly the case when PO is being retrieved from ERP via RFC from SRM.

© SAP AG of 71


To fix the inconsistency proceed as follow:


Transaction Code SE37

2. Enter function module "BBP_GET_SWITCH_STATE_RFC"

3. Click Utilities Repair Function Group

4. Choose BBP_BAPI_PO as the function group and confirm

5. The following message is displayed:

The following objects can be repaired automatically

The following modules contain an include and an entry in the function library

no entry in TFDIR.

This is generated during repair

6. Choose button Repair, assign a new workbench task and confirm the changes.

3.7.3 Deactivate BBP-BAdI Implementations of BAdI HRALX_HRALXSYNC_BADI

Use

The synchronization of HR-data BP using report HRALXSYNC is not working for this package due to incorrect BBP-implementations of BAdI HRALX_HRALXSYNC_BADI. Deactivate the implementations.

Procedure



2. Enter BAdI Name HRALX_HRALXSYNC_BADI and choose Display

3. On the Business Add-Ins: Display Definition HRALX_HRALXSYNC_BADI screen choose Implementation Overview to see the available implementations.

Yellow highlighted implementations are active and need to be deactivated.

4. Select an active implementation and choose Change.

5. Confirm the pop-up by choosing Maint. in orig. lang.

6. Choose Deactivate (Ctrl+F4) to deactivate the active implementation.

7. Choose Back.

8. Proceed with the next active implementation as described in steps 3-6.

© SAP AG of 71


3.7.4 SLD Connection

Check the correct SLD entry using transaction SLDCHECK. The output of the transaction should look as follows:

If the check receives errors similar to the below mentioned ones, contact your system administrator to set up SLD correctly.

To run the SRM scenario without setting up a complete SLD connection at least an entry in table LCRT_CLNTCACHE is required.



Table name LCRT_CLNTCACHE

2. Create a new entry as follows:

Parameter Name Value Note

SRTFD <System-ID><client> For example,

© SAP AG of 71


Parameter Name Value Note

RQE102

AEDAT Date Actual date

BS KEY NAME <Key Name of Business System>

For example, RQECLNT102

BS ROLE LOC Role of Business System

BS CAPTION <Business System Name> For example, RQECLNT102

3. Save your entries.

4. If an issue occurs in transaction MDS_LOAD_COCKPIT see SAP Note 997389.

In this case, contact your system administrator to create a complete SLD entry.

Set up SLD connection, maintaining

o Transaction RZ70, transferring technical data to SLD

o Transaction SM59 TCP/IP connectionsLCRSAPRFCSAPSLDAPISLD_UC

o Transaction SAPSLDAPICUST

Create business system for the SRM client in SLD

Run transaction SLDCHECK in the SRM client to verify the correct set-up

3.7.5 VMC and IPC

The VMC (Virtual Machine Container) is available in the basis software delivery (part of SAP NetWeaver 7.0) has to be activated.

The IPC (Internet Pricing and Configurator) is based on the VMC. It is used to enable consistent pricing and configuration through all sales channels and 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 being used instead. The IPC settings are optional.


Transaction Code SM52

Use the transaction to determine whether the virtual machine is activated.

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 Note 854170.

No customizing steps are necessary. Your system administrator has to set profile parameters and restart the system.

© SAP AG of 71


3.7.6 Execute Report RHSOBJCH

Use

The purpose of this activity is to run report if SOBJ is inconsistent. This step is necessary if Activate standard tasks displays error messages.

Procedure

1. Access the activity using one of the following navigation options:

SAP Menu Tools ABAP Workbench Development ABAP Editor


2. Enter the following data at program: RHSOBJCH and Execute.

3. Select all of the objects.

4. Perform a reconciliation by choosing List Update selection

5. After the object list has been reconciled, table OBJS is consistent.

3.8 Generic Pre-Activation Activities

3.8.1 Set Up of http and https Services

Use

http and https services have to be set up in order to use the SAP NWBC.

© SAP AG of 71


Procedure


Transaction Code SMICM

2. On the ICM Monitor screen, choose the menu path Goto Services (shift+F1)).

3. Activate http and https services.

3.8.2 Activation of Services for SAP Best Practices Solution Builder

Activate the services needed for the SAP Best Practices solution builder and SAP NWBC using the transaction SICF.


Transaction Code SICF

2. On the Maintain Services screen choose Execute (F8).

3. On the Maintain service screen expand the Virtual Hosts / Services node as follows and activate all the services listed below:

default_host sap public myssocntl

default_host sap bc bsp smb sc_scoping_tool

These services are needed for the SAP Best Practices solution builder

3.8.3 Deselecting Activation Links in BC SetsWe recommend that you turn off the creation of activation links. By doing this, you can significantly increase activation speed and avoid errors.

Procedure


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.


© SAP AG of 71


3.9 Maintain Profile Parameters

3.9.1 SAP Scripting

Use

eCATTs are used to automate the activation of SAP Best Practices configuration settings. Prior to 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 front-end must be set true.

Procedure


Transaction Code RZ11

2. On the Maintain Profile Parameters screen, make the following entries


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.


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.

3.9.2 Authentication Using SAP Logon Tickets

Use

To fulfill the requirement of the SAP Best Practices solution builder use, the following profile parameters have to be set as listed below. The set of these profile parameters is also necessary for the communication between SAP NetWeaver Business Client and SAP EEC system to work correctly. Execute the following steps.

© SAP AG of 71


Procedure





Note

Param. Name Profile parameter name login/accept_sso2_ticket

3. Choose Display.



Parameter Name Description New value

Note

login/accept_sso2_ticket Accept SSO ticket logon for this (component) system

1 Check and adapt value if necessary

6. Choose Save.

7. Choose Back (F3).



Note

Param. Name Profile parameter name login/create_sso2_ticket

9. Choose Display.




Note

login/create_sso2_ticket Create SSO tickets on this system

2 Check and adapt value if necessary

12. Choose Save.

This adaptation of the profile parameters login/accept_sso2_ticket and login/create_sso2_ticket is necessary to you use the SAP Best Practices solution builder as well as the SAP NetWeaver Business Client.

© SAP AG of 71


3.9.3 Set Default Timeout for http and https Services

Use

We recommended that you set the following for both services TIMEOUT and PROCTIMEOUT to 300 or 600 (seconds). The default is 60.

The values are also set using system parameters (see below section Procedure):

icm/server_port_<*> - Standard value for *: 0: http, 1 or 2: https

For example:

icm/server_port_0 = PROT=HTTP, PORT=8000, PROCTIMEOUT=300,

TIMEOUT=600

icm/server_port_2 = PROT=HTTPS, PORT=44300, PROCTIMEOUT=300,

TIMEOUT=600

Procedure



2. On the Edit Profiles screen, enter your instance profile.

3. In the Edit Profile box, select the radio button for Extended maintenance and choose Change.

4. On the Maintain Profile screen, make the following entries


Note

icm/server_port_<*> Standard value for *:

0: http, 1 or 2: https

300or600

Set to 300 or 600 (seconds) for TIMEOUT and PROCTIMEOUT, the default is 60

5. Choose Back

6. Choose Save.

This adaptation of these profile parameters is only necessary if you are using SAP NetWeaver Business Client.

3.10 Creating User for Activation of SAP Best Practices Content

Use

In this activity, you create a user to run the activation of the related SAP Best Practices scope. However SRM does not supply separate customizing or setup roles (according to the SRM security guideline). Instead, you should use the functions provided in Role Maintenance (transaction PFCG). Here you can define a role corresponding to your individual IMG project with all the authorizations you need to access the corresponding IMG activities required for the SAP

© SAP AG of 71


Best Practices scope. For more information about building a role for a Customizing project, see the documentation for the transaction PFCG.

Alternatively you can use the authorization profile SAP_ALL. If this authorization does not apply to your authorization concept, you should restrict the rights of the user according to your internal authorization guidelines. Without the profile SAP_ALL, issues during the activation may occur and need to be solved. You can use the transaction SU53 to get information on the missing authorizations and extend the authorization data as necessary.

Directly after activation of the SAP Best Practices content, remove the authorizations you have given to the system user that has performed the activation steps. This is for security reasons to avoid that the system user misuses 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 page.

4. Make the following entries:

Field Name User Action and Values Note

Last name <Last name of the user>

First name <First name of the user>

5. Choose the Logon Data tab page.



Password <initial password>

User type Dialog

7. Choose the Defaults tab page.



Logon language EN

Decimal notation 1.234.567,89

Date format DD.MM.YYYY

© SAP AG of 71


9. Choose the Roles tab page.

10. Enter the user role you created that contains the necessary authorization profile

Alternatively you can assign the profile SAP_ALL on the Profiles tab page. Make sure that this corresponds to your internal security guidelines.


Result

A user to activate SAP Best Practices content has been created.

© SAP AG of 71


4 Activation of Business Content / Scenarios – Activation Consultant

The following section describes the activities that have to be done by the consultant activating SAP Best Practices in the system.

4.1 Initial Check of System ReadinessIt is necessary that you check if your system administrator has applied the correct SPS level as outlined above in the section Release and Support Package Level.

In addition, ensure that the system administrator has also finished all activities as described in the section System Setup & Preparation – System Administrator.

Continue with the following steps only if these prerequisites are met.

4.2 Check Content Prerequisite in the Client

The activation of the SAP Best Practices for SRM package in an “empty client” is not supported!

In order to configure a one client system using the package, existing application configuration settings have to exist in your client. The following list provides you with an overview of the most required settings.

- Enterprise Structure / Assignments

o Company

o Credit Control Area

o Company Code

o Controlling Area

o Valuation Level (Standard)

o Plant

o Storage Location

o Purchasing Organization

o Purchasing Group

- Financial Accounting / Controlling Settings

o Company Code Settings

o Activity-Based Costing in Controlling Area

o Activate components/control indicators

o Primary and Secondary Cost Elements

o Cost Centers and Cost Elements

- Material Management and Logistics Settings

o Vendor account groups and field selection

© SAP AG of 71


o Vendor number ranges and grouping

o Material types, attributes of material types, number ranges for material types

o Material groups

o Procurement settings.

If you have no client available containing any application configuration settings you can create a copy of client 000 and activate for example the SAP Best Practices for Baseline package V1.604 for Germany (or at least the basic Purchasing scenario Procurement without Quality Management which contains all relevant basic settings) in this client.

You can find more information about this package on:

http://help.sap.com/ SAP Best Practices Baseline packages Based on SAP ECC 6.00 V1.604

4.3 Scenarios to be ActivatedWhen you activate the SAP Best Practices for SRM package, you get both predefined scenarios up and running in your system. Details for these scenarios are available on the documentation DVD in the area Business Information Preconfigured Scenarios. Select the scenarios map for overviews, process flows, and details of the scenarios.

4.4 Activation LanguageMake sure that your logon language is always English (and NOT your local language) for all activation activities.

4.5 User Settings for Activation

For activation, we recommend that only one User ID be used to activate the SAP Best Practices. It can be a tedious procedure to change ownership of the activation of the solution.

Make sure that you only have one single SAP GUI session running when you activate SAP Best Practices. If you run several SAP GUI sessions, some automated installation activities might run into errors.

4.5.1 Deactivate Info Dialog Box on Dynpro Size Check

Use

The dialog box sizing conflicts may appear which may pop up during activation has to be deactivated.

© SAP AG of 71

http://help.sap.com/


Procedure

1. Log on with the user in the system.

2. Choose the first button from the right side of the Standard Tool Bar Customizing of Local Layout or type ALT + F12.

3. Select the menu item Options.

4. Choose the Options tab page.

5. De-select the Enable dialog box for dynpro size check checkbox.

6. Choose the OK button at the bottom.

4.5.2 SAP Software Change Registration (SSCR): Developer Key

Use

The user ID used for activation has to be registered as developer on SAP Service Marketplace (SAP Software Change Registration (SSCR)). For more information, see SAP Note 86161. The SSCR developer key is needed, because the user ID used for SAP Best Practices activation creates and changes objects from the customer name range during the SAP Best Practices activation process. If the SAP Best Practices activation user is not registered as a developer, the automated SAP Best Practices activation incurs errors.

Procedure

1. Access the SAP Service Marketplace at http://service.sap.com/sscr.

2. On the SAP Software Change Registration (SSCR) start page, you get the detailed user documentation on how to proceed to get the SSCR developer key.

An SSCR developer key is a 20 character combination of digits that is queried when an SAP ERP user tries to create or change an object from the customer name range FOR THE FIRST TIME. The prompting message for the developer key appears once for each SAP ERP user; if registration is successful, this SAP ERP user is no longer prompted to enter a developer key. The SSCR developer key is generated from the installation number of the affected installation and the SAP ERP user name.

4.5.3 Unicode Settings

Use

Before each user logs on to the system for the first time, the user’s local GUI must be set to use the Unicode code page.

Procedure

1. From the SAP Logon pad, select your system ID.

2. Choose the Change Item button.

3. On the System Entry Properties dialog box, choose the Code Page tab page.

4. On the Encoding dropdown, select Unicode (UTF-8).

© SAP AG of 71

http://service.sap.com/sscr


5. Choose OK.

4.5.4 Allow GUI Scripting

Use

Perform this activity so that eCATTs GUI scripts can by executed with your GUI.

Procedure



10. Choose the Scripting tab page.

11. Select the Enable scripting checkbox.

12. Deselect the checkboxes Notify When a Script Attaches to a Running GUI and Notify When a Script opens a Connection.


4.5.5 Set Decimal Notation and Date Format

Use

Perform this activity to set up the activation user ID.

Procedure


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 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 section Printer Environment above).


7. Log off from the system.

8. Log on to the system.

Log off and log 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 AG of 71


Result

The decimal notation and date format have been set up according to your country format. The standard printer has been defined.

4.6 Getting the Business Content for Activation

Perform the steps Getting the Solution Scope File and Getting the Installation Data Files on the same day. If you download them at different times, you may encounter errors due to mismatching.

4.6.1 Getting the Solution Scope File

Use

The technical structure for each solution (scenarios, building blocks, and technical objects) of the SAP Best Practices is managed by a solution scope file.

Procedure

1. The solution scope file can be found as attachment to the SAP Best Practices for SRM support note (for details on the SAP Note number see above section SAP Notes and Messages).

2. Download the solution scope ZIP-file that corresponds to:

<Mat-Nr Config DVD>_Scope_<Solution_ID><Add-On Version>.ZIP

The naming convention corresponds to:

the material number of the configuration DVD 5XXXXXXX

or the number of the download object / file in the software distribution center (same number as material number of configuration DVD)

5XXXXXXX.ZIP

The number of the download object can be found on the SAP Software Distribution Center in the download area for the download object Config: Best Practices All-in-One.

or the SAP Best Practices Add-On Version for example BP-ERP 604V4

You can determine the Add-On Version as follows:SAP Easy Access menu: System Status Component information (Prerequisite: The Add-On version/release has been installed in the system).

Example: 5XXXXXXX_SCOPE_BP_SRM_V1700_604V#.zip

© SAP AG of 71


4.6.2 Getting the Installation Data Files

Use

The installation settings (configuration settings and master data) of the SAP Best Practices are managed by the installation data files.

Procedure

1. The installation data files can be found as attachment to the SAP Best Practices for SRM support note (for details on the SAP Note number see above section SAP Notes and Messages).

2. Download installation data ZIP-file package from the solution note:

<Mat-Nr Config DVD>_BP_FILES_<IND>_<Add-On Version><Languages>.ZIP

The naming convention corresponds to:

the material number of the configuration DVD 5XXXXXXX

or the number of the download object / file in the software distribution center (same number as material number of configuration DVD)

5XXXXXXX.ZIP

The number of the download object can be found on the SAP Software Distribution Center in the download area for the download object Config: Best Practices All-in-One.

or the SAP Best Practices Add-On Version e.g. BP-ERP 605V2

You can determine the Add-On Version as follows:SAP Easy Access menu: System Status Component information (Prerequisite: The Add-On version/release has been installed in the system).

Select the zip file for which languages you would like to activate the package

e.g. EN_DE for language English and German

Example: 5XXXXXXX_BP_FILES_SRM_605V#_EN_DE.zip

4.6.3 Creating a Folder for the SAP Best Practices Activation1. Create a folder on a hard drive (for example, on your local hard drive) that can be

accessed from within the SAP system where you want to activate SAP Best Practices for SRM. Ensure that the persons who will activate SAP Best Practices have the necessary user rights to access this folder.

2. Extract the files from the ZIP files you downloaded in the previous task into the folder you created in step 1. You should have one solution scope file (*.xml), many variant files (*.TXT).

© SAP AG of 71


4.7 Activation of ScenariosFor an instruction on how to get information on all scenarios included in the SAP Best Practices for SRM package, see section Scenarios to be Activated above.

Step 1: Import the Solution File

1. To run the SAP Best Practices solution builder, from the Command field, enter /n/smb/bbi and press Enter.

2. On the Solution builder – solution editor screen, from the menu, choose Solution Import.

3. On the Select one format to import dialog box, choose the Import XML file button.

4. On the Select the XML file dialog box, browse to the location of your XML file (in the folder you created during step Creating a Folder for the SAP Best Practices Activation, see above), select it, and choose Open.

5. Set the uploaded solution as the favorite solution: choose Solution Set Favorite.

Step 2: Set Document Path for Solution Builder

Use

This activity sets the document path for information that may be useful during activation so that users can find details from the SAP Help Portal about the scenario being activated.

Procedure

1. From the SAP Best Practices solution builder menu, choose Goto User Settings.

2. Choose the External Documents tab page.

3. Choose the Display <> Change button.

4. Choose the Insert Row button.


Parameter Value

DOCUMENTATION http://help.sap.com/

6. Choose Save.

7. Choose Back.

Step 3: Upload the Installation Data

Use

The purpose of this step is to upload the installation data to the solution builder. This step is mandatory even if you do not want to personalize your solution.

© SAP AG of 71


To assure the installation data upload is working correctly, make sure before installation data upload the following user settings are set as described (access via Solution Builder Solution Editor Goto User Settings, tabstrip General):

o Deselect the setting Check consistency with eCATT definitions during Installation data upload

o Select the setting Maintain references in eCATT Definitions during Installation Data upload

Procedure

1. From the SAP Best Practices solution builder main menu, choose Upload Installation Data (Ctrl + F5).

On the Upload and Download external file data dialog box, browse to the location of your installation data files (in the folder you created during step Creating a Folder for the SAP Best Practices Activation, see above), select it, and choose Continue (Enter).

Step 4: Personalize the Solution

This step is mandatory to check the interfaces and integration points in the back end client. It is essential for the activation of the package that all personalization steps have to be executed accurately.

Wrong maintenance of the personalization and integration data may lead to issues during the activation and the usage of the package.

1. Choose Personalization (Ctrl+F8) On the Generic Personalization Composer screen, you can see all activities that are can be personalized. These personalization steps are mandatory to handle the back end client integration.

The personalization of the required information for the SRM configuration about the enterprise structure in the back end client is also done in the Generic Personalization and not in the function Enterprise Structure Personalization.

2. Navigate to all activities and double-click the activity to maintain the required data. A document is attached for each step. These documents describe which data has to be maintained and how to determine the required values in the back end client. To open the document, choose Display documentation.

3. Make any personalized entries and set the status to document the progress of your personalization activities.


Step 5: Starting Activation

1. Ensure that your solution is set as a favorite solution.

2. From the menu, choose Goto Implementation (Ctrl + F6).

3. Select the top node of the solution, and choose the Activate button.

© SAP AG of 71


4. On the Activate solution dialog box, make the following entries:

Field Name User Action and Values

Comments

Target Language

EN You can also use target language DE. As a result, selected language independent fields are filled with German description texts instead of English texts.

Installation Data <location of folder with installation data>

for example, Z:\sme\files

This folder was created in step Creating a Folder for the SAP Best Practices Activation

You cannot use UNC paths (for example, \\dwdf030\SME\...).

Always use a mapped network drive (for example, Z:\SME )

Also it is not possible to use any root directory of your local drive (for example, C:\)

Workbench <workbench request number>

Enter an existing workbench request number, or choose the Workbench Request button to create one.

Customizing <customizing request number>

Enter an existing customizing request number, or choose the Customizing Request button to create one.

New activation flag for transport requests

Deselect or Select

New activation flag has been inserted to the solution builder. I you want to create Customizing and Workbench request automatically then select this checkbox. Otherwise deselect it and create them manually.

Skip this screen Deselect If selected, the system does not display the Activate solution dialog box upon resumption of activation following an error or manual activity. If deselected, the Activate solution dialog box will display every time after resumption of activation.

With demo data Select If selected, system executes activation steps that create demo data. If deselected, these steps are not executed.

Activation w/o demo data – What does this mean?

If you want to activate the SAP Best Practices package without demo data, you can deselect the checkbox to turn off activation of demo data.

After activation is completed, you will not be able to test the business scenarios. The scenario testing requires the presence of the demo data and related configuration settings.

To test the business processes with customer demo data, you can create your own demo data. Proceed as follows:

Select the business scenario you want to test

© SAP AG of 71


Check the row in the Prerequisites Matrix file for this scenario to determine the required prerequisite building blocks.

Go to the Solution Builder Building Block Builder – Scenario Edit View.

Look at the steps that have the check box activated in column De (Demo) for all building blocks that belong to the scenario..

Refer to the corresponding Configuration Guide and create the required configuration and master data activities manually.

Errors occur during activation – Where can I find more information to solve the issue?

In case of any issues during activation always check section: Error Handling: Installation Errors during activation

5. Choose Continue.

Manual Step Handling

There are some manual steps that you will need to handle during activation. The solution builder displays a procedure dialog box with instructions for you to follow to process the step.

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 use the DEFAULT values in the manual step configuration descriptions and configuration guides, respectively, but use your personalized values wherever applicable.

Running an eCATT in Foreground Mode

Some activation activities require to run an eCATT in foreground mode. The following description provides an instruction on how to run the eCATT in the foreground mode.

Procedure

1. On the Start eCATT Testconfiguration screen, select Display Start Options.

2. Choose the Execute button.

3. On the following screen, choose the UI Control tab page.

4. In the TCD box, in Start Mode for Command TCD, use the dropdown to select A Process in Foreground, Synchronous Local.

Step 7: Personalization

You can get the list of default values and their personalized values. To generate a list containing default and personalized values refer to SAP Note 1421667.This is an optional step and is only possible if you have personalized the solution (see step 5).

© SAP AG of 71


This task is usually carried out together with the business consultant who will take over the steps as described in section Evaluate Business Content / Scenarios – Business Consultant below.

Step 8: Post-Activation Activities

Deactivate Info Dialog Box on Dynpro Size Check

Use

For all system users created during the activation the dialog box sizing conflicts may appear has to be deactivated. For more information, see the configuration guide for S00 – section: Define Business User.

Procedure

1. Log on with the user in the system.



4. Choose the Options tab page.

5. De-select the Enable dialog box for dynpro size check checkbox.


© SAP AG of 71


5 Error Handling: Installation Errors during Activation – Activation Consultant

The following information helps you to solve problems that might occur during the installation process.

Before you start with detailed error analyzing and working through the error processing as described below, proceed as follows:

Activate your solution or the respective scenario in the solution builder implementation assistant again. It might be the case that error does not reappear. In this case, no correctional activities are needed and the installation is proceeding.

5.1 Error Occurs During Activation of Automated Task

Use

When an activation of an automated task runs into errors, the activation stops at the point of the error. No further implementation can be done until the error is resolved.

Procedure

1. On the Implementation Assistant – Solution View screen, select a task that has a red light in the Current status column.

2. Expand the task and choose the log that is assigned to this task. Detailed information about the error is displayed in the Error List pane.

3. In the Error List pane choose Display Detailed Log. The detailed log information about an eCATT or BC set activation is displayed.

4. In this log information check entries with a red light to identify the reason for the error.

a. In case the error can be solved based on the log information, you can run the eCATT or BC set again.

In case the activation fails because of locked objects, make sure that no objects are locked by any users. Then try to activate the activity again.

See the document SAP Best Practices Tools for details about the manual activation of eCATTs and BC sets. The document can be found on the documentation DVD in the area Technical Information -> Tools and Concepts.

5. In case the log information is not sufficient to solve the problem you can proceed as follows:

a. Execute the task manually: use the description of the related section in the configuration guide for executing the task,

or

© SAP AG of 71


b. Open a customer message for this problem specifying the component SV-SMB-AIO-BP-SRM.

Do NOT delete solution builder scenarios after they have been activated. If you delete scenarios, the activation history and the respective logs are lost and it is not possible to find possible error reasons with tenable efforts.

In such cases NO SAP SUPPORT CAN BE PROVIDED.

6. When you have solved the problem (either executed the task manually or a solution has been provided via customer message), choose the Change button that is displayed in the Old Status column to the right of the task.

Do NOT proceed with installation if the problem has not been solved. If you continue without solving the problem, severe errors might result in the subsequent installation steps that cause incalculable efforts to fix.

In such cases NO SAP SUPPORT CAN BE PROVIDED.

7. Choose the Change button that is displayed in the Old Status column to the right of the task.

8. On the Confirmation dialog box, choose OK to manually change the status to successful.

9. On the Information dialog box, enter a reason for changing the status.

10. Choose Continue.

The information is saved in a log. To view details for a changed task, choose the red light in the Original Status column for that task. A dialog box displays the user who performed the change, the date of the change, and the reason for the change. Choose Continue to close the dialog box.

11. Choose Activate to continue with the installation.

5.1.1 General Issue- Inconsistencies in SOBJ

Use

In case of error messages regarding inconsistencies of SOBJ, run the following procedure. For more information, see the section 3.7.6 Execute Report RHSOBJCH.

Procedure


SAP Menu Tools ABAP Workbench Development ABAP Editor


2. Enter the following data at program: RHSOBJCH and Execute.

3. Select all of the objects.

4. Perform a reconciliation by choosing List Update selection

© SAP AG of 71


5. After the object list has been reconciled, table OBJS is consistent.

5.1.2 General Issue- Runtime Error PXA_NO_FREE_SPACE

Use

The runtime error PXA_NO_FREE_SPACE occurs (displayed, for example, in transaction ST22)

Procedure

Analyze the dump using transaction ST22 and refer to note 147568.

Check whether the value of the profile parameter abap/buffersize is appropriate.Check the procedure and size with your system-administrator.

Result

The dump no longer occurs.

5.1.3 S00- Check IPC Configuration

Dump During IPC Check

Use

If you encounter a short dump during the check of the IPC (issue in program: BBP_CND_CUSTOMIZING_CHECK; message “Incorrect status in pricing”) please refer to note 1357489. The issue is based on an incorrect set up of the Virtual Machine Container (VMC)

Procedure

Re deploy Java Applikation of VMC according to note 1357489 and reset VMC

Result


5.1.4 S03 – WE31: Creation of IDoc Z1P550* Transfer Structures

Use

The Ecatt stops with an error “S00344 No batch input data for screen SAPLSTRD 0300”. The reason is that the pop up for the transport request is not working properly. This Ecatt has to run in foreground mode !

However in case the issue occurs in the backround the header of the transfer structure was created in some database tables. Before proceeding these entries have to be deleted in order to avoid inconsistencies. Proceed with checking the issue, then removing the inconsistent entries and create the correct entries.

Procedure - Checking

You can check this as follows:

1. Start transaction WE31.

2. Enter segment type Z1P550x and choose Change. If the message appears Segment Z1P550x does not exist yet, choose Back.

© SAP AG of 71


3. Start again transaction WE31 and choose Create. If the message appears Structure Z1P550x already exists, the folllowing steps have to be conducted for the following segments: Z1P5500, Z1P5501, Z1P5502, Z1P5503.

Procedure – Table Maintenance

Make sure you have the appropriate authorization for ABAP dictionary and the table maintenance.

4. Start transaction SE16N.

5. Enter table name EDISEGMENT and selection criteria: Segm.type - Z1P550x

6. Remove the entries Z1P550x (Z1P5500, Z1P5501, Z1P5502, Z1P5503)

7. Repeat this step for the following tables: EDISDEF; EDSAPPL, DD02L.

In case you cannot delete the entries you have to switch temporality the table maintenance options for these tables using transaction SE11 (tab page Delivery and Maintenance).

Procedure – Run eCATT in foreground mode.

8. After deletion of the entries you can proceed with the activation in the solution builder.

9. On the screen Implementation Assistant – Solution View flag activity /SMBSRM/WE31_O001_S03 - Creation of IDoc Z1P550* transfer structures and select check box FG (Foreground activation mode).

10. Save your entries

11. Choose Activate in order to restart the activation.

12. On the Start eCATT Testconfiguration screen, select Display Start Options.

13. Choose the Execute button.

14. On the following screen, choose the UI Control tab page.

15. In the TCD box, in Start Mode for Command TCD, use the dropdown to select A Process in Foreground, Synchronous Local.

16. Confirm all Pop-Ups with Enter. Check the entries for the transport request.

Result

You have created the required transfer structures.

5.1.5 S03 - Organizational Model: Manual Upload of ORG Model Template

Use

When uploading the external txt-file the following error occurs: „…program RHALTD00 of type BINP has not been registered for object PDOTYPES”

© SAP AG of 71


Procedure

The issue occurs when the IDoc Z1P550* transfer structures are not created correctly. For checking the structures and fixing any issues proceed as described in the previous section: S03 – WE31: Creation of IDoc Z1P550* transfer structures.

Make sure that the structures are created correctly. To do so you can check Configuration Guide S03 – section: Creation of IDoc Z1P550* Transfer Structures.

Repeat all steps following the Creation of IDoc Z1P550* Transfer Structures activity:

Structure Info for Data Transfer Object - see S03 Config Guide (Chapter 3.6.3)

- T777D registration of Z1P550* transfer structures - see S03 Config Guide (chapter 3.6.2.1)

- Switch of Transport Requests for HR Customizing – see S03 Config Guide (chapter 2.2)

Result

The upload of the txt files should work – In case the upload does not work - also check the next chapter.

5.1.6 S03 - Organizational Model: Manual Upload of ORG Model Template

Use

When uploading the external txt-file the following error occurs: „…Conversion has failed in field xx of line xx”

Procedure

1. Start transaction SM30

2. Enter Table SXDA3

3. Select the following entries in table SXDA3 and maintain the data as follows (especially fields: Value and Identifier):

DX object

DX sub cat

Item Tab Name

Field Name

Req. Field

Value Active Ident.

777 0 <Sequence number> used for step SXDA2

Z1P5500 INFTY X 5500 X X





777 0 <Sequence Z1P5503 INFTY X 5503 X X

© SAP AG of 71


number> used for step SXDA2

Result

The upload of the txt files should work

5.1.7 S03- Organizational Model: Set Attribute for Delivery Address

Use

The Ecatt stops with an error: “Error in eCATT command FUN BBP_GET_SHIPTO_ADDR; EXCEPTION TYPES_NOT_MAINTAINED; ERROR MESSAGE No Address Type is Assigned to Transaction for Address Determination BBP003”.

Standard Customizing is missing which has to be maintained manually.

Procedure

1. Access the activity using the following navigation option:

IMG Path Supplier Relationship Management SRM Server Master Data Business Partner Manage Address Types

2. On the Change view: “BP Adress types”: Overview screen, check if the following entries exist. In case they are missing make the following entries.

Address Type Name Several Uses

BILL_FROM Invoicing Party Address X

BILL_TO Invoice Recipient Address X

GOODS_REC Ship-to Party Address X

POST_TO Ordering Address of Vendor X

SHIP_FROM Shipping Address of Vendor X

SHIP_TO Ship-To Address X

3. Save your entries and go back to the IMG menu.


IMG Path Supplier Relationship Management SRM Server Master Data Business Partner Assign Transaction to Address Type

5. On the Change view: “Transn for BP Adress Determin: BP Adress Type Assignm screen, check if the following entries exist. In case they are missing make the following entries.

Transaction Description Address Type

BBP000 Send order POST_TO

BBP001 Receive goods SHIP_FROM

© SAP AG of 71


BBP002 Receive bill BILL_FROM

BBP003 Send goods SHIP_TO

BBP004 Send bill BILL_TO

BBP005 Distribute goods (inhouse) GOODS_REC

6. Save your entries and go back to the solution builder.

7. Restart the activation.

8. If the activation still gets back with an error proceed you can maintain the adress data of the organization model manually. Proceed as follows (only in case if the error still occurs):


Transaction PP02

10. On the initial screen, enter the import parameters for Object ID, Infotype, Subtype, and validity and choose Change.

Field Value

Object ID 30000001 EBP Company

Infotype Selection

Infotype 1222 General Attribute Maint.

Subtype 0020 EBP: B2B Procurement

Validity <validity period>

11. On the next screen, choose Edit New Entries.

12. Enter the import parameters for the specific attribute (together with the flags for the fields Default and Excluded) and choose Save.

Attribute Value Low Value High Default

ADDR_SHIPT <select for the address number in table ADRC>

Search for EBP_COMP and select Address number

Result

You have created the required data manually and can proceed with the activation. You can check the result in the organization model using transaction PPOMA_BBP.

5.1.8 S03 - Activate Synchronization Options

Unable to Activate Synchronization between <> and <> ECCMAT and PRODMAT

Use

The activation stops stops with an error, e.g.: “Unable to activate synchronization ECCMAT and PRODMAT “during activation of task Activate Synchronization Options - /SMBA0/MDSV_CTRL_OPT__B04C_J01.

© SAP AG of 71


If you enter the table in via Cross-Application Components Master Data Synchronization Synchronization Control Synchronization Control Activate Synchronization Options you get the same issue when changing the parameters manually.

Procedure


IMG Menu Cross-Application Components Master Data Synchronization Material/Service Integration Activate/De-activate Synchronization (Material to Product and vice versa).

Transaction Code SPRO

2. Check if the following entries exist:

Source Object Target Object Act. Ind.

ECCMAT PRODMAT X

ECCMATGRP PRODCAT X

ECCMATTYP PRODCAT X

ECCPINFREC PRODMAT X

ECCSERV PRODSERV X

ECCSERVTYP PRODCAT X

PRODCAT ECCMATGRP X

PRODCAT ECCMATTYP X

PRODCAT ECCSERVTYP X

PRODMAT ECCMAT X

PRODMAT ECCPINFREC X

PRODSERV ECCSERV X


IMG Menu Cross-Application Components Master Data Synchronization Synchronization Control Synchronization Control Activate Synchronization Options


4. Check if the following entries exist:


BP CUSTOMER X

BP VENDOR X

CUSTOMER BP X

VENDOR BP X

ECCMAT PRODMAT X

ECCMATGRP PRODCAT X

ECCMATTYP PRODCAT X

ECCPINFREC PRODMAT X

ECCSERV PRODSERV X

© SAP AG of 71



ECCSERVTYP PRODCAT X

PRODMAT ECCMAT X

PRODMAT ECCPINFREC X

PRODSERV ECCSERV X

5. In case all entries are there you can ignore the issue and proceed with the activation.

Result

The issue can be ignored.

5.1.9 S03 -Initial Replication of Material Data

Dump during Replication of Materials

Use

If you encounter a short dump during the replication of materials Category ABAP Programming Error, Runtime Error COMMIT_IN_PERFORM_ON_COMMIT, ABAP Program SAPLSDMP, proceed as follows to solve this error.

Procedure

17. Start transaction SE37.

18. In the Function Module field, enter the value BBP_PROD_PRCAT_COND_GET_HANDLE.

19. Choose Test/Execute (F8).

20. In the IV_MAINT_CONTEXT field, enter the value PRODUCT.

21. Choose Execute (F8).

Result


5.1.10 S03 -Initial Replication of Material Type / Material Group / Material Data

Dump during Replication of Material Type, Material Groups or Materials

Use

You are in transaction MDS_LOAD_COCKPIT and start an initial download of material master, material type, or group. The system terminates with MESSAGE_TYPE_X and short text "No connection to the System Landscape Directory".

Procedure

Refer to SAP Note 997389 and set up an entry in the table for the System Landscape Directory.

© SAP AG of 71


Result


5.1.11 S03 -Initial Replication of Vendor Data

Issue: R11 335: Errors Occurred during Call of Function Module BUPA_ROLE_ADD_2.

Use

You are in transaction MDS_LOAD_COCKPIT and start an initial download of vendor data. You get an error message: R11 335: Errors occurred during call of function module BUPA_ROLE_ADD_2.

Procedure

Apply SAP Note 1436150.

Result

The error no longer occurs and the replication is working.

Issue: INTERNAL.SYSTEM_NOTCONFIGURED_AS_XMB System not Configured as XI Integration Engine

Use

You are in transaction MDS_LOAD_COCKPIT and start an initial download of vendor data. You get an error message: INTERNAL.SYSTEM_NOTCONFIGURED_AS_XMB System not configured as XI Integration Engine. In transaction ST22 you get a dump in program SAPLBUPA_MDM_PROXY with Error SYSTEM_ONCOMMIT_INTERRUPTED.

Procedure

Check the following:

Run transaction SXMB_ADM

Select Integration Engine Configuration

Menu: EDIT / Change Global Configuration Data

Set Role of Business System to "Application System".

Result

The error no longer occurs and the replication is working.

© SAP AG of 71


5.1.12 S03 - Change Client-specific Configuration Parameters

Use

The eCATT /SMBSRM/SAPCND_V_CFGC_O001_S03 stops with an error ‘Objects for config. file could not be created without errors - Message no. /SAPCND/CUSTOMIZING025‘

Procedure

Ignore the message and proceed with the activation. For further details refer to note 1231346.

Result

The activation can proceed.

5.1.13 S03 - Contact Person / Service Agent

Use

The eCATT /SMBSRM/DATA_SUPCONT_O001_S04 - Contact Person / Service Agent stops with an error. This task creates the service agents for existing Business partner. In case the business partners are missing an error occurs.

Procedure

1) Make sure that the required buiness partners (300000 / 300002 / 300003) are synced correctly. You can use transaction SE16 to check if these business partners exist in table BUT000.

If no there were issues during the replication of vendors.Check the log files of the vendor replication. Make sure note 1436150 was applied. This solves issues during the replication of vendor master data.

Note: Contact person / service agent are master data objects and can be also created later in the SRM application itself.

2) Use transaction SM30 to check that table T77S0 contains the folllowing entry:

GRPID (Group): TRSP

SEMID (Semantic Abbr,): CORR

GSVAL (Value Abbr.): X

TEXT (Description): Transport Switch (X = No Transport)

In case GSVAL (Value Abbr.) is blank there might be a dump when creating the service agents.For the creation of SRM master data this flag is mandatory.

Result

In case these prerequisite conditions are fulfilled you can proceed with the activation.

© SAP AG of 71


5.1.14 S03 –Maintain the Vendor Business Partner

Use

When maintaining the business partner the following message appears:Organizational unit does not exist, check entries.

As a result the business partner cannot be saved.

Procedure

Check if the supplier is assigned to the Vendor Group.

1. Start transaction PPOMV_BBP and check if the vendor is assigned to the vendor group.

2. You can search for vendors using the vendor search on the left hand side.

3. Select the missing vendor code in the hit list, select the vendor group root node and choose Assign.

4. Save your entries

Result

After the assignment of the vendor, maintain and save the vendor business partner.

© SAP AG of 71


6 Evaluate Business Content / Scenarios – Business Consultant

The following sections describe the activities that have to be done by the business consultant who is taking care that the business processes work as desired.

The section Review of Business Scenarios provides an overview where the business consultant can get information on the SAP Best Practices scenarios activated in the system.

The section on Usage of Personalized Values explains how to proceed if the SAP Best Practices activation was done using personalized data files, and you want to use the process documentation reflecting the personalized values. This section can be ignored if the SAP Best Practices activation was performed using default values.

The section User Maintenance and Settings outlines the activities that the business consultant has to perform to enable system users to exploit the business process documentation. The necessary user settings are described.

The section Creation of Queries in Personal Object Worklists (POWLs) refers to information that is needed when you work with the SAP NWBC. In several business process documents, it is necessary that you create queries. In such cases, refer to the description as outlined below.

The section Errors during Usage of Activated Package lists errors that users might face in the system when applying the business process documentation. The information provided helps to solve such errors.

The section Errors with SAP NetWeaver Business Client (SAP NWBC) describes possible errors that only occur when using SAP NWBC.

6.1 Review of Business Scenarios

Details for individual scenarios are available on the documentation DVD in the area Business Information Preconfigured Scenarios. Select the scenarios map for an overview of all scenarios. Depending on the scenarios you are interested in, choose the corresponding scenario box on the map. When you select the box, an information window opens. When you then select the information icon, you directly get to the scenario overview HTML page. On that page, you can access the business process documentation, process overview document, and the configuration guide of the respective scenario.

The business process documentation (BPD) provides a detailed process step description of the business scenario.

The scenario overview document contains a graphical overview of the scenario process flow.

The configuration guide describes crucial parts of the system configuration of the respective scenario. Together with the configuration guides of the underlying building blocks, you can track which system settings have been configured. For more information about the building block concept, see the section Technical Information Tools and Concept Building Block Concept on the documentation DVD.

You can use the documents as described above to review the business scenarios you are interested in. Use the business process documentation (BPD) to evaluate the scenario in the system.

© SAP AG of 71


6.2 List of Default Values and Personalized Values

This section can be ignored if the SAP Best Practices activation was performed using default values.

To generate a list containing default and personalized values refer to SAP Note 1421667

On details how to proceed, see the instruction above in the section Scoping and Activation of Scenarios, Step 7: Personalization. This is a task that the business consultant usually performs together with the consultant who carries out the SAP Best Practices activation.

© SAP AG of 71


7 Issues during Usage of Activated Package – Business Consultant

The following information helps you to solve problems that might occur after the installation of the package when evaluating the business processes.

7.1 FI Integration for Invoicing

7.1.1 Check Tax Type for GL Account It is recommended to set the tax type to ‘*’ for the gl accounts defaulted for product categories.


SAP Menu Accounting Financial Accounting General Ledger Master Records G/L accounts Individual Processing Centrally

Transaction Code FS00

2. Enter the GL account defaulted in SRM, e.g. 521000, and company code, e.g. 1000.

Access the activity using the following navigation options in order to check the assigend accounts in SRM for the specific product catergories.

IMG Menu Supplier Relationship Management SRM Server Cross-Application Basic Settings Account Assignment Define G/L account for Product Category and Account Assignment Category


3. In Edit mode branch to tab page Control Data

4. Enter ‘*”All tax types allowed into the field Tax category

5. Save the new entry

6. Repeat for all defaultet GL accounts to avoid error message in SRM

7.1.2 Invoicing Error Tax code XX does not exist, check entries.

Error “Tax code XX does not exist, check entries” might appear when approving an invoice document with manager position.

This step depends on your Tax customizing in the system.

1. Go to table sm30 and maintain table BBP_TAX.

2. Enter the missing entry XX and description No Tax.

© SAP AG of 71


3. Check the “No tax” checkbox and “Default” radio button.

4. Save.

Check also the following:

IMG Menu Supplier Relationship Management Cross Application Basic Settings Tax Calculation Determine System for Tax Calculation


1. Choose “No Tax Calculation” (If No Tax is enabled for your process) or set it to your configured value.

2. Save.

7.2 External Catalog IntegrationFor some Microsoft Windows Internet Explorer versions (e.g. MS Windows IE 7) the catalog integration is not working properly due to restrictive cookie handling. In order to solve this issue you have to adopt the browser settings as follows (description MS Windows IE 7)

1. Open your Browser

2. Go to Tools -> Internet Options

3. Go to Privacy Tab

4. Make the settings to "Accept All Cookies" instead of Medium.

5. Apply and Ok

6. Restart your browser.

7.3 Lean Catalog Integration NWBC Usage – white Page after Item Transfer

For some Microsoft Windows Internet Explorer versions (e.g. MS Windows IE 8) there might be problems transferring selected items back to the application. You will see a white page after you select “Transfer Items”. In this case set up the following:

IMG Menu Supplier Relationship Management SRM Server Master Data Content Management Define External Web Services


1. Select the ID of your defined Lean Catalog e.g.” LEAN_CAT” and choose “Standard Call Structure”.

2. Search for the parameter BYPASS_INB_HANDLER.

3. Set the Parameter Value to X.

© SAP AG of 71


7.4 Performance Issues for Scheduled Jobs

Use

Report BBP_GET_STATUS_2

Report may lead to performance problems with increasing number of SRM documents. Per default the job is running every 15 min for all documents.

Recommendation:

Define a job variant comprising all documents: schedule only once a day

Define a job variant comprising documents created in the last 7 days: schedule for every 15 min.

Procedure

2. To adjust the jobs run may use the following transactions:

Transaction Code

SM36 - Job Definition

Transaction Code

SM37 - Job Overview

7.5 Customizing for Team Purchasing is Missing

Use

The standard customizing settings for the team customizing for the shopping cart is missing

Procedure


SAP Reference IMG Menu

Supplier Relationship Management SRM Server Cross-Application Basic Settings Define Transaction Types


2. Select the following transaction object types BUS2121 - Shopping Cart and choose Transaction types.

3. Select and double-click Transaction Type SHC - Shopping Cart.

4. Make the following entry:

© SAP AG of 71


Parameter Name Value Comment

Team Purchasing 1 – No team purchasing

2 – Admin only

3- admin and All Users

Choose the appropriate value depending on your requirements


© SAP AG of 71


8 Frequently Asked Questions (FAQ) – Business Consultant

In this section, you can find information about questions that were raised by external tester and consultants during testing cycles.

8.1 HR/HCM IntegrationQ. What is the reason that the HR/HCM Integration is activated (HRALX/HRAC = X) and is it

possible to run SRM@ERP one client without HR/HCM Integration?

A. There are two reasons why HR integration for SRM@ERP is mandatory:

User accounts that want to use “Self-Service Procurement” of SRM must be assigned to business partners of type “Person” and role “Employee”, otherwise they cannot be referenced in SRM documents (by the so-called “Partner Set”)

In ERP, business partners of type “Person” and role “Employee” must be created in the HCM employee data model (and hence through HR components), otherwise you create clashes with ERP components that use the “HR Mini Master” (e.g. Sales, …)

The requirement is hence not only due to SRM but to ensure the overall ERP Business Suite consistency. The data model decision is aligned with ERP colleagues and could not make by SRM individually.

There are two notes to facilitate employee creation in ERP:

797875: Describes how one can configure a screen sequence for PA40 that combines all mandatory details required to create personnel records in SRM ("mini master")

1398626: Provides a mass enabled API and a report to create personnel records on the basis of SU01 user records; the API and the report are shipped via EA_HR

The report solution provided by note 1398626 minimizes the manual steps as far as possible. Prerequisites are SU01 user accounts, which are used as templates for the HR personnel records.

8.2 NWBC Personalization

Q. Is it possible to change the web UI and how can this be done? In every project the customer wants that the SRM web UI reflects the corporate identity of the company. Is it possible to insert the company logo and change the colors?

A. It is planned to support customer logo branding, but no branding related to colors in the first version. We know that this is an important requirement and we will consider it for the next release of NWBC. not in scope in this package

8.3 NWBC / Portal IntegrationQ. Is SAP NetWeaver Business Client (NWBC) required to deploy SRM functionality in SAP

Business All-in-One?

A. No, a customer can use either NBWC version 3.0 or the SAP NetWeaver Portal. Note that SRM functionality is preconfigured to use NWBC version 3.0. Prior versions of NWBC will not work. Using the SAP NetWeaver Portal would require some configuration. All functionality

© SAP AG of 71


was tested and validated in the NetWeaver Business Client for HTML (and additionally on the SAP Portal)

Q. What are the benefits that the SAP NetWeaver Business Client provides?

A. SAP NetWeaver Business Client is a rich user interface client that offers a unified environment for and a single point of entry to SAP business applications and technologies. NWBC greatly simplifies the user experience and is also available as a zero footprint browser client (NetWeaver Business Client for HTML).

Q. Is there any loss in functionality when using SRM functionality in SAP Business All-in-One in the zero footprint NetWeaver Business Client for HTML?

A. No. All functionality was tested and validated in the NetWeaver Business Client for HTML.

© SAP AG of 71


9 Further Information – Business ConsultantIn this section, you can find additional configuration activities that are not preconfigured in the SAP Best Practices for SRM package.

9.1 Use of SAP Portal If you want to use the SAP Portal as UI for SRM then refer to the additional S06 Portal Configuration Guide attached to solution note 1606895.

9.2 Use of SAP Best Practices Roles for Demo and Evaluation

New harmonized roles for Demo are shipped with SRM V1.701. These roles are in the SAP Best Practices Namespace and are seperated by user position.

Role Description Comment

SAP_NBPR_SRM_EMPLOYEE_S

New harmonized scen. demo role for Employee

SAP_NBPR_SRM_MANAGER_M

New harmonized scen. demo role for manager

SAP_NBPR_SRM_PURCHASER_S

New harmonized scen. demo role for Purchaser

SAP_NBPR_SRM_BIDDER_S

New harmonized scen. demo role for Bidder

9.3 Reporting

Use

Reporting can be done either using OLTP Reporting or BI Reporting. The activation of the customizing switches enables the display of reports on the NWBC UI for both areas (SRM OLTP Reporting / BI Reporting). During activation of the SAP Best Practices for SRM package the preconfiguration is done for OLTP Reporting:

That means the status for the switches is changed as follows:

SRM_700_ANALYTICS_LOCAL OLTP Reporting ‚ON‘

SRM_700_ANALYTICS_BW BI reporting default ‘OFF’

Procedure

1. You can activate the BW-Based Analytics using the following navigation option:


Supplier Relationship Management SRM Server Analytics Activate/Deactivate BW-Based Analytics

Supplier Relationship Management SRM Server

© SAP AG of 71


Analytics Activate/Deactivate BW-Independent Analytics


This triggers the activation of the following customizing switches.

2. You can change the delivered customizing using the following navigation option:

Transaction Code LPD_CUST

OLTP reporting is based on infoset queries (POWL outside, inside infosets). The reports are being called using launchpads (transaction LPD_CUST). The following customizing is preconfigured (out-of- the box reporting):

The delivered standard customizing covers reporting without BI (OLTP Reporting) for the following roles: Operational Purchaser; Strategic Purchaser

Role Instance Description

OP_PUR OLTP_REPORTS OLTP Reports of Operational Purchaser

ST_PUR OLTP_REPORTS OLTP Reports of Strategic Purchaser

Optionally standard customizing covers reporting with BI for the following roles: Operational Purchaser; Strategic Purchaser

Role Instance Description

OP_PUR BI_REPORTS BI Reports of Operational Purchaser Role

ST_PUR BI_REPORTS BI Reports of Strategic Purchaser Role

3. Choose New Launchpad to define new launchpads for specific roles (such as Manager) for OLTP or BI reporting.

4. To use the reporting within the delivered SRM roles you have to enhance the roles accordingly. You can change the delivered SRM roles using the following navigation option:

Transaction Code PFCG

5. Enter the role name and choose Change.

SRM roles are delivered in the following namespace: /SAPSRM/* for example, /SAPSRM/MANAGER

© SAP AG of 71


6. On the tab page page Menu search for the corresponding reporting node and enter the following data

Parameter Value Example for the Use of OLTP

Web Dynpro Applicat. < enter WEB Dynpro Applicat>

/SAPSRM/WDA_L_REP_LPD

For using the customizing launchpad

Description <Description> For example, Reports

Parameter

for example, ROLE_OLTP

<Role defined in customizing launchpad>

For example, MANAGER

for example, INSTANCE_OLTP

<Instance defined in customizing launchpad>

For example, OLTP_REPORTS


9.4 Lean Inbox

Use

In order to see only the relevant items in your work queue you can personalize the lean inbox.

Prerequisite

The customizing-switch SRM_700_LOCAL_MENU (SPRO SAP Customizing Implementation Guide Supplier Relationship Management SRM Serve Technical Basic Settings Portal-Independent Navigation Frame Activate/Deactivate Portal-Independent Navigation Frame) for usage of portal-independent navigation frame was activated. This is done during activation of SAP Best Practices for SRM package.

Procedure

1. You can personalize your inbox using the following navigation option:


Cross-Application Components Processes and Tools for Enterprise Applications Inbox


Define Tasks and Actions

You can define actions and their properties, define default actions for specific tasks, and assign custom attributes and actions to tasks. You can change existing tasks and actions or define new ones. For more information, see the documentation for the Customizing activity.

Set Refresh Interval

The inbox uses the personal object worklist (POWL) to assemble the list of work items, alerts, and notifications. You can set an interval for automatic refresh of the POWL.

© SAP AG of 71


If the IMG activity is not available in your IMG menu you can access the customizing tables directly using transaction SM30:

IBO_C_WF_ACC for actions IBO_C_WF_APC for action properties IBO_C_WF_TAC for tasks and their default actions IBO_C_WF_CAC for assignment of custom attributes to tasks IBO_C_WF_TTAC for assignment of actions to tasks

These customizing tables override the entries in the following system tables:

IBO_C_WF_ACS for actions IBO_C_WF_APS for action properties IBO_C_WF_TAS for tasks and their default actions IBO_C_WF_CAS for assignment of custom attributes to tasks IBO_C_WF_TTAS for assignment of actions to tasks

9.5 Workflow Adjustments

Use

In order to adjust the workflow settings you can use the following activity to model your completion and approval processes for SAP Supplier Relationship Management business objects, for example, shopping cart. In this example we show you how to change the preconfigured shopping cart approval process.

Example: Change Shopping Cart Approval – Procedure

This is only an example for the workflow adjustments. Further adjustments might be required in case you are going to meet specific requirements.

1. You can adjust the workflow settings using the following navigation option:


Supplier Relationship Management SRM Server Cross-Application Basic Settings Business Workflow Process-Controlled Workflow Business Process Configuration Define Process Levels


2. In the Dialog Structure, choose Business Objects and select BUS2121 - SRM Shopping Cart

3. Select Process Schema Evaluation and select the event that you require, in this case 3C_SC_600_001

4. Choose Process Level Configuration.

5. On the screen Change View “ Process level configuration”: Overview enter the following data

Resp. Resolver Name Resp. Resolver Parameter Impact

Old value: Old value: The workflow has changed in that way that all shopping

© SAP AG of 71


Resp. Resolver Name Resp. Resolver Parameter Impact

RR_MANAGER

New value:

RR_ROLE

<blank>

New value:

/SAPSRM/MANAGER

carts (created by any users) will be forwarded for approval to managers which are assigned to the role /SAPSRM/MANAGER.


9.6 Simplified Pricing

Use

The SAP Best Practices for SRM package is preconfigured using the IPC (Internet Pricing and Configurator) based on the VMC (Virtual Machine Configuration) which is available in the basis software delivery (JAVA stack is not required). This activity is optional, since not all purchasing documents can be created using simplified pricing, e.g. for the strategic sourcing scenario with RFQ simplified pricing cannot be used. However simplified pricing can be used optionally for the Self Service Procurement Scenario.

Procedure

To allow the simplified pricing, the default implementation BBP_PRODUCT_PRICE of BAdI BBP_PRICEDATA_READ has to be activated.



2. Under Edit Implementation enter Implementation for Classic BAdI:

BBP_PRODUCT_PRICE- Read Price from Product Master

3. Choose Change and activate the implementation.

9.7 BAdI for Transfer of Shopping Cart Number to Purchase Documents

Use

I order to track the shopping cart number in the purchase order you can use BADIs to transfer the shopping cart number into the purchase requisition / purchase order (field in PR/PO: Requirement Type). If this field is already in use for other purposes do not execute the following steps.

Procedure for Purchase Requisition



2. Create a new implementation for the classical BAdI:

BBP_CREATE_BE_RQ_NEW – Purchase Requisition

3. Paste the following Coding in method FILL_RQ_INTERFACE

© SAP AG of 71


method IF_EX_BBP_CREATE_BE_RQ_NEW~FILL_RQ_INTERFACE.

* Die Bedarfsnummer mit der Shoppingcard Nummer füllen

data : wa_items type bbps_badi_rq_item,

wa_header type bbps_bs_transfer_header_ext.

loop at cs_rq_document-it_requisition_items into wa_items.

* Suche nach der richtigen Bedarsnummer

loop at is_sc_document-header into wa_header.

wa_items-trackingno = wa_header-object_id.

endloop.

modify cs_rq_document-it_requisition_items from wa_items.

endloop.

endmethod.

4. Activate the method and the BAdI Implementation

Procedure for Purchase Order



2. Create a new implementation for the classical BAdI

BBP_CREATE_BE_PO_NEW – Purchase Order

3. Paste the following Coding in method FILL_PO_INTERFACE1

method IF_EX_BBP_CREATE_BE_PO_NEW~FILL_PO_INTERFACE1.

>>>>>>>

* Die Bedarfsnummer mit der Shoppingcard Nummer füllen

data : wa_items type BBPS_BADI_PO_ITEM_1,

wa_itemsx type BBPS_BADI_PO_ITEMX_1,

wa_header type BBPS_BS_TRANSFER_HEADER_EXT.

* Übertragung der Shopping Card

loop at cs_po1_document-it_poitem into wa_items.

* Suche nach der richtigen Bedarsnummer

loop at is_sc_document-header into wa_header.

wa_items-trackingno = wa_header-object_id.

endloop. modify cs_po1_document-it_poitem from wa_items.

endloop.

© SAP AG of 71


loop at cs_po1_document-it_poitemx into wa_itemsx.

wa_itemsx-trackingno = 'X'.

modify cs_po1_document-it_poitemx from wa_itemsx.

endloop.

<<<<<<

endmethod.

4. Activate the method and the BAdI Implementation

© SAP AG of 71


10 Security Aspects - System AdministratorsThis section provides an overview of the security-relevant information that applies to the deliverables of this SAP Best Practices package.

10.1 User Administration and Authentication In this chapter you will find an overview of the required users for this package

Purpose User-ID User Type

Created in Initial Password

Authorization Profile

Comment

Activation User

User ID is defined by your System-Admin.

Dialog (Type A)

Creation described in Quick Guide

Password is defined by your System Admin.

Authorization is defined by your System Admin.

Evaluation User

User ID is defined by your System-Admin.

Dialog (Type A)

Creation described in Quick Guide

Password is defined by your System Admin.

Authorization is defined by your System Admin.

You can check the user using transaction SU01.

10.2 RFC DestinationsIn this chapter you will find an overview of the required RFC destinations created and used for this package.

RFC Destination

Description Connection Type

Created in

Logon Data Comment

ONEClientERP OneClient ERP

3 S00 RFCUSERBBP/remote

ONEClientEBP OneClient EBP

3 S00 RFCUSERBBP/remote

ERP_LOCAL ERP local 3 S00 RFCUSERBBP/remote

You can check the roles using transaction SM59.

10.3 Roles ManagementIn this chapter you will find an overview of the template roles used for this package.


/SAPSRM/EMPLOYEE Employee user scen. demo role

SAP_NBPR_SRM_EMPLOYEE_S

New harmonized scen. demo role for Employee

© SAP AG of 71

http://help.sap.com/saphelp_nw04s/helpdata/en/99/acdc3ed98f7650e10000000a114084/content.htm



/SAPSRM/MANAGER Manager user demo role

SAP_NBPR_SRM_MANAGER_M

New harmonized scen. demo role for manager

/SAPSRM/OP_PURCHASER Purchaser user scen. demo role

SAP_NBPR_SRM_PURCHASER_S

New harmonized scen. demo role for Purchaser

SAP_AIO_PURCHASER-S Purchaser user scen. demo role

/SAPSRM/BIDDER Bidder user scen. demo role

SAP_NBPR_SRM_BIDDER_S

New harmonized scen. demo role for Bidder

You can check the roles using transaction PFCG.

© SAP AG of 71