AP SRM 7 EhP3 or SAP ERP 6 EhP7 - websmp202.sap-ag.desapidp/012002523100002826722015E/RDS_SLC...AP...

AP SRM 7 EhP3 or

SAP ERP 6 EhP7

SAP Supplier Life Cycle Management 2.0 (SAP SLC 2.0 SP01)

April 2015

English

SAP Supplier Lifecycle Management Rapid-Deployment Solution V4: Software and Delivery Requirements

SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany

Document Revisions Date

0 19.01.2015

1 20.03.2015

2

SAP Rapid Deployment Solutions Software and Delivery Requirements

© SAP SE Public of 33

Copyright

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

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

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

National product specifications may vary.

These materials are provided by SAP SE 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 and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

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.



Table of Contents Contents

1 Purpose of the Document .............................................................................................................. 5

2 General Project Prerequisites ....................................................................................................... 5

2.1 General Scoping Options for SLC ....................................................................................... 5

3 Technical Requirements for SLC@SRM ....................................................................................... 6

3.1 Software Product Versions.................................................................................................. 6

3.2 SAP Notes ........................................................................................................................... 9

3.3 SAP Solution Manager and SAP Solution Manager Content Add-On .............................. 12

3.4 SAP Best Practices Solution Builder and Activation Content Add-On .............................. 13

3.5 Other Deployments ........................................................................................................... 14

3.6 Activate Business Functions ............................................................................................. 16

3.7 Software Landscape Diagram ........................................................................................... 17

3.8 Connectivity ....................................................................................................................... 18

3.9 Authorizations ................................................................................................................... 18

4 Technical Requirements for SLC@ERP ..................................................................................... 21

4.1 Software Product Versions................................................................................................ 21

4.2 SAP Notes ......................................................................................................................... 24

4.3 SAP Solution Manager and SAP Solution Manager Content Add-On .............................. 25

4.4 SAP Best Practices Solution Builder and Activation Content Add-On .............................. 26

4.5 Other Deployments ........................................................................................................... 27

4.6 Activate Business Functions ............................................................................................. 28

4.7 Software Landscape Diagram ........................................................................................... 29

4.8 Connectivity ....................................................................................................................... 30

4.9 Authorizations ................................................................................................................... 30



1 Purpose of the Document This document contains all information to:

Validate that key prerequisites such as software products and versions match the customer situation

Check that all prerequisites for a customer implementation are in place

Check that correct content, tools and skills are in place before the project starts

The document lists different kinds of requirements on package level if they are valid for all scope items included in the package. For requirements valid for certain scope items only, these scope items are mentioned.

The document contains pre-requisites only, not the procedures to meet them. For how-to information (e.g. how to find the download area) please refer to the configuration guides.

2 General Project Prerequisites The following prerequisites need to be in place before an implementation project can start.

Prerequisite Responsibility

Kick off and workshop dates, location and attendees agreed Customer

Customer team allocated with correct skills and training in place Customer

Project sponsors and stakeholder identified Customer

Hardware fully commissioned Customer

Software licenses in place Customer

Infrastructure team can respond to requests quickly enough e.g. CSS notes, BW content, patches, user requests, authorization changes and transports

Customer

User interfaces agreed e.g. SAPGUI, Netweaver Business Client or Portal

Customer

Remote access is in place for SAP consultants and SAP Active Global Support

Customer

Decision made whether pre-assembled delivery will be used Customer

Decision made whether SAP Best Practices Solution Builder will be used to activate content.

Customer

Decision made whether Solution Manager will be used. Solution Manager set up with any relevant templates.

Customer

Tool for project repository and collaboration agreed Customer

Test management tool agreed Customer

2.1 General Scoping Options for SLC You may choose from 2 deployment variants with 3 different scoping options:

SLC@SRM with BGRFC communication to Sell-side, offering scope items SL1-SL4 and SLW

SLC@SRM with SOA communication to Sell-side, offering scope items SL5-SL8 and SLX



SLC@ERP with BGRFC communication to Sell-side, offering scope items SLA-SLD and SLT

For more details, see also chapters 3.7 and 4.7.

The technical requirements for the deployment variant SLC@SRM are described in chapter 3. The technical requirements for the deployment variant SLC@ERP are described in chapter 4.

3 Technical Requirements for SLC@SRM This section contains technical requirements in different areas. For each requirement, the relevance for scope items of the package is provided.

3.1 Software Product Versions The following software products and versions are required:

Product

Product Version

Components

SAP Solution Manager Logical Component

Comments

Relevance

SAP SRM

EHP3 for SAP SRM 7.0 (SP07)

SRM_SERVER

SRM70_EHP3_SRM_SERVER_HUB (Buy-Side system), SRM70_EHP3_SLC_SUS (Sell-side system “SUS”)

Based on SAP NetWeaver 7.0 EHP3

All SLC@SRM Scope Items

SAP ERP

EHP7 FOR SAP ERP 6.0 (SP07)

- central applications

SAP_APPL ERP60_EHP7_CENTRAL_APPLICATION

.

Usually, required software components and SP levels are downloaded using the Maintenance Optimizer of the SAP Solution Manager. If you need to download manually from the SAP Software Distribution Center in the Service Marketplace, use the following navigation paths:

For installing software, go to https://service.sap.com/swdc Installations and Upgrades

Entry by Application Group SAP Application Components

For support packages, go to https://service.sap.com/swdc Support Packages and

Patches Entry by Application Group SAP Application Components

3.1.1 SAP SLC@SRM DEPLOYMENT The SAP Supplier LifeCycle Management on SAP Supplier Relationship Management can be integrated to SAP ERP systems. In order to provide a standardized installation process, a complete installation of the ABAP part of Enhancement Package 7 for SAP ERP 6.0 is required.

https://service.sap.com/swdc




3.1.2 SAP ERP Core Components 7.0 (SAP ECC 7.0 Backend) Detailed information regarding the installation of Enhancement Package 7 for SAP ERP 6.0 can be found at service.sap.com/erp-ehp7-inst in the Master Guide for SAP Enhancement Package 7 for ERP 6.0.

To download Enhancement Package 7, go to the Software Download Center (SWDC) on SAP

Service Marketplace https://service.sap.com/swdc Support Packages and Patches A-Z Index

SAP ERP SAP ERP ENHANCE PACKAGE EHP7FOR SAP ERP 6.0.

Product Version Release SP Level Comment

EHP 7 for ERP6.0 617 0007 SAP enhancement package 7 for SAP ERP 6.0

The following software components are required in their respective SPS levels for SAP enhancement package 7 for SAP ERP 6.0:.

.

Software Component Release SP Level Comment Description

SAP Basis

(SAP_BASIS)

740 0009 SAP Basis Component

SAP ABA

(SAP_ABA)

740 0009 Cross-Application Component

PI Basis

(PI_BASIS)

740 0009 Basis Plug-In

SAP Web UI Framework

(WEBCUIF)

747 0007 SAP WEBCUI Framework

SAP BS Foundation

(SAP_BS_FND)

747 0007 SAP Business Suite Foundation

SAP BW

(SAP BW)

740 0009 SAP Business Warehouse

SAP APPL

(SAP_APPL)

617 0007 Logistics and Accounting

SAP AP_700

700 0032 SAP Application Platform

SMCERPIT

100 0009 Integration Comp. for Integration of Supplier Lifecycle Management

SRMSMC 200 0001 SAP Supplier Lifecycle Management 2.0

Usually, required software components and SPS levels are downloaded using the Maintenance Optimizer in SAP Solution Manager. Alternatively, you can download the software manually from the SAP Software Download Center (SWDC) on SAP Service Marketplace:

https://websmp107.sap-ag.de/erp-ehp7-inst





Browse our Download Catalog SAP Application Components


Patches Browse our Download Catalog SAP Application Components SAP ERP

SAP ERP ENHANCE PACKAGE EhP7 for SAP ERP 6.0 Entry by Component

For detailed information on SPS definition for the SRs of SAP ERP, see SAP Note 774615 Support Package levels of ERP/ECC installations/upgrades.

The combination of SAP Best Practices for SAP SRM Self-Service Procurement with other SAP Best Practices packages and/or predefined and rapid-deployment solution packages may require a complete update of all ABAP software components of Enhancement Package 7 for 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 Package should have the SP level assigned to the current SPS of SAP ECC 6.0.

For an overview of all software components and their Support Package levels combined in the various SAP ERP Support Package Stacks, see SAP Note 1386389.

3.1.3 SAP Supplier Relationship Management – Enhancement Package 3 for SRM 7.0 (Sell-Side & Buy-Side)

The following software components are bundled with SAP SRM 7.03:

Software Component Release SP Level Description

SAP Basis 7.4

(SAP_BASIS)


SAP ABA 7.4

(SAP_ABA)


PI Basis 7.4

(PI_BASIS)


SAP Web UI Framework 7.47

(WEBCUIF)


SAP BS Foundation 7.47

(SAP_BS_FND)


SAP BW 7.4

(SAP BW)


SAP AP_700


SRM SERVER 7.03

(SRM_SERVER)

713 0007 SAP Enhancement Package 7 for SAP ECC 6.0 (ABAP) is in sync with SRM_SERVER 703

SRM SERVER

SRM_PLUS 713 0007 SRM_PLUS for mySAPSRM

SMCSRMIT 100 0009 Integration Comp. for Integration of Supplier Lifecycle Management 2.0

Only if SAP Supplier Lifecycle Management is to be deployed on an SAP enhancement package 1



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







or 2 for SAP SRM 7.0 system.


We require two servers or clients with above configuration to set up SAP Supplier Life Cycle Management. One SRM Server for the Buy Side and one for the Sell Side of SAP Supplier Life Cycle.

Required software components and SP levels are usually downloaded using the Maintenance Optimizer of the SAP Solution Manager. If you need to download manually from the SAP Software Distribution Center in the Service Marketplace, use the following navigation paths:

Installation:

https://service.sap.com/swdc Software Downloads Software Download Center

Installations and Upgrades A - Z Index Select S (on the Installations and Upgrades tab

page on the main page) SAP SRM SAP SRM ENHANCE PACKAGE EHP2 FOR

SAP SRM 7.0 Installation <Select your target DB> 51036866, "DVD SAP SRM 7.0 SR1/NW7.01 SR1 Installation Export "

Support Packages:


Support Packages and Patches A - Z Index Select S (on the Support Packages and

Patches tab page on the main page) SAP SRM SAP SRM ENHANCE PACKAGE

EHP3 FOR SAP SRM 7.0 Entry by Component SRM Server SRM Server 7.03

3.2 SAP Notes If issues become apparent after shipment of this SAP Rapid Deployment Solution package (and hence of this document), a SAP Note exists to document how to solve the issues.

Before you start the activation of the related SAP Rapid Deployment Solution scope, check the latest version of the SAP Note for the solution package to obtain updates and corrections for problems that have not become apparent until after shipment.

SAP Note #

Description Component Area Remark

2107080

SAP RDS for Supplier Lifecycle Management V4.703)

SV-RDS-SRM General Info

Always check the SAP Note

SAP RDS for Supplier Lifecycle Management V4.703 for updates on the

implementation of SAP Rapid Deployment Solution for SRM

Apply all SAP Notes to the system via the SAP Note Assistant (transaction SNOTE). All SAP Notes mentioned below must 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, perform a mass generation using transaction SGEN as described in SAP Note 481548.



http://service.sap.com/sap/support/notes/481548



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

Note: For the latest SLC 2.0 release it comes with updated notes and need not be again implemented.

SAP Note # Description Component Area Remark

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 is installed in one client of a SAP ERP system (based on enhancement package 6 for SAP ERP 6.0) Therefore, you need the following Add-ons:

- BP-ERP 607Vx

- BP-SOLBLD 70Vx

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.

1433603 NWBC causes locks in Web Dynpro applications

BC-WD-CLT-BUS

Usage

1456162 Navigation to catalog is cancelled in IE8

SRM-EBP-CAT Usage

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

1836704 User locked when creating vendor contact person

SRM-EBP-ADM-XBP

Usage Implement the attached correction instructions or apply the relevant Support Package.

1993962 Transfer of PRs failing in one client scenario

SRM-EBP-EXR Usage Implement the attached correction instructions or apply the relevant Support Package.

0002140623 Sellside Task Menu corrupted in case of Customer Roles

SLC-ACT

2123491 Supplier are not able to access tasks of activity management

SLC-ACT

2131830 THTMLB Tree tag is returning empty rows

CA-WUI-UI-TAG














1809709 Supplier cannot logon to the qual. request using init. user

SLC-SUP

1809710 Redirection of supplier to the final registration page

SLC-SUP

1574317 The Release Information Note (RIN) contains information about and references to SAP Notes for applying support packages to SAP Supplier Lifecycle Management 1.0.

SLC-SUP

1838973 This Release Information Note (RIN) contains detailed information about and references to SAP Notes required for applying SP04 of SAP Supplier Lifecycle Management 1.0.

SLC-SUP

1598759 The Add-On Installation Note describes what needs to be done to install SAP Supplier Lifecycle Management based on SAP enhancement package 2 for SAP NetWeaver 7.0 technology.

BC-UPG-ADDON

1841471 Release strategy for ABAP add-ons for interface components

BC-UPG-ADDON

1710197 Corrections for unified rendering up to SAP_BASIS

BC-WD-ABA







1891604 Sell side: Qualification request opens as empty

SLC-QUA

If you are going to enhance the scope of the SAP Rapid Deployment Solution for SRM/SLC package, the mentioned notes might be important. They provide additional data for productive use of the scenarios.

You do not have to apply these notes in the system. Moreover for SLC2.0 already these might have been available in the standard delivery . They are not relevant for the activation and usage of the selected Rapid Deployment Solution for SLC. They simply provide additional information.

3.3 SAP Solution Manager and SAP Solution Manager Content Add-On

For the implementation of the solution package, SAP Solution Manager is recommended.

Product Product Version Comments

SAP Solution Manager SAP Solution Manager 7.0 Enhancement Package 1

SP18 or higher

Or

SAP Solution Manager 7.1

SP01 or higher

Or

SAP Solution Manager 7.1 on HANA (ST 712)

SP00 or higher

If using SAP Solution Manager 7.0 with SP below 24, see SAP Note 1579267.

For SAP rapid-deployment solutions, implementation content is available in SAP Solution Manager templates.

The SAP Solution Manager template for this solution package is in the ST-RDS 100 content add-on. You can download the latest available ST-RDS 100 content add-on from SAP Software Download Center on SAP Service Marketplace at service.sap.com/swdc.

For more information about downloading and installing ST-RDS 100 content add-ons, see SAP Note 1726649 and SAP Note 1686668 respectively.

In the ST-RDS 100 content add-on, access the template in the following way:

If you have SAP Solution Manager 7.1 SP04 or lower, select the template ID and template name in the table below.

If you have SAP Solution Manager 7.1 SP05 or higher, select the solution package name(s) in the table below.

Template ID and Template Name

RDS_SLC_SRM703V4 - SAP Supplier Lifecycle Management RDS_V4

Solution SAP Supplier Lifecycle Management RDS SLC@SRM with BGRFC_V4








Package Name(s)

SAP Supplier Lifecycle Management RDS SLC@SRM with SOA_V4

3.4 SAP Best Practices Solution Builder and Activation Content Add-On

For tool-supported, automated activation of the solution package, SAP Best Practices solution builder is recommended.


SAP Best Practices solution builder

BP-SOLBLD 70Vx

Always use the latest available version as outlined in SAP Note 1301301.

Add-on for the implementation tool (only necessary to be implemented in a system where content activation shall be done using the Solution Builder (i.e. Sandbox or Development System).

The following content is required:

(SAP Best Practices Add-On and SAP Best Practices Solution Builder Add-On)

The following SAP Best Practices add-ons must be imported in the system:

Product Product Version

Components as tested

Solution Manager Component

Comments Relevance

SAP Best Practices Configuration Content (for SAP SRM and SAP NetWeaver)

BP-ERP 617 V3

BP-CANW 740V4

Always use the latest available versions as outlined in SAP Note 1301301.

BP-SOLBLD 70 V9

BP-ERP

BP-CANW

BP-SOLBLD

None SAP Best Practices All-in-One based on SAP ERP

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


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

All SLC@SRM Scope Items





Note: The automated implementation content available with SAP Best Practices Solution Builder is developed and tested for SRM 7.03.

You can find additional and detailed information in the document Importing SAP Best Practices Add-Ons (ADDONINS.PDF) on the Configuration DVD (latest available DVD via SAP Note 1240936).

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

https://service.sap.com/swdc Installations and Upgrades Browse our Download

Catalog SAP Best Practices search for BP-SPLBLD and BP-CANW.

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 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 (see also 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 have to ensure the system is at the current versions before you start the technical implementation of the SAP Best Practices version.

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.5 Other Deployments

3.5.1 SAP Frontend Components

3.5.1.1 Enterprise Portal Ensure that you have installed the latest applicable SAP frontend components.

If you want to use the Enterprise Portal, use the following SAP NetWeaver EP version:

SAP Components Release

SAP NetWeaver 7.4 SAP NETWEAVER 7.4 or higher version

BP SLC BP for SLC 100 Portal Content for SAP Supplier Lifecycle

Management 1.0 or higher version

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

https://service.sap.com/swdc Download Support Packages and Patches Support Packages

and Patches - Entry by Application Group SAP Frontend Components







You will find an overview of how to install SAP frontend components and how to apply patches. You can select the SAP frontend components to meet your requirements.

3.5.1.2 SAP NetWeaver Business Client If you want to use the NetWeaver Business Client you have to use following version:

SAP Component Version Comment

SAP NetWeaver Business Client

NWBC NW BUSINESS CLIENT 4.0

BC-WD-CLT-BUS SAP Note 1353538





You can find additional information about the NWBC in SAP Note 900000. Further release restrictions are listed in SAP Note 1029940 and configuration instructions in SAP Note 1368177.

3.5.2 SAP Process Integration (SAP PI)

SAP PI is only necessary if you want to activate scenario SL5, SL6, SL7, SL8 or SLX.

Ensure the following PI components are bundled with SAP PI 7.4:


SAP_ABA 740 0008 Cross-Application Component

SAP_BASIS 740 0008 SAP Basis Component

PI_BASIS 2008_1_710 0008 Basis Plug-In

SAP_BW 740 0008 SAP Business Warehouse

For more details, see https://websmp110.sap-ag.de/instguidesnw70. In case of problems, refer to the PI Troubleshooting Guide, see Sap Note 806546.

Each PI is required for DEVELOPMENT, TEST and PRODUCTIVE clients.

Import the SRM content referring SAP Note 836200 into PI.

For more information on installing the SWCs, refer to the Service Marketplace at https://websmp110.sap-ag.de/instguidesnw70 and search for Installation Guide – SAP Process Integration 7.0.



https://websmp110.sap-ag.de/instguidesnw70

https://websmp110.sap-ag.de/instguidesnw70



3.6 Activate Business Functions Functionality in this solution package requires certain business functions to be active in the SAP landscape. These business functions need to be activated:

Use After installing SAP SLC on SAP SRM USER INTERFACE ADD-ON, you have to activate the following Extension Sets/Business Functions before you start activating the SAP Rapid Deployment Solution package content.

Activating Enterprise Extensions, Business Functions, and Business Function Sets means permanent changes to your system which cannot be undone. For more information about the impacts on your system, see the documentation of the related Extension Set or Business Function.

Procedure 1. Run the following activity:

IMG Menu IMG SAP Supplier Relationship Management

SRM Server Activate Business Functions

Transaction Code SFW5

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

Business Functions Planned Status

Comment

SRM_ANALYTICS_1, SRM_CONT_IMPR, SRM_CONT_IMPR_1

ON SRM, Analytics (Reversible)

SRM, Continuous Improvement CC (Reversible)

SRM relevant Function Switches

SMC_SUPPL_CLASS_1 ON SLC, Supplier Classification (Reversible)

SMC_SUPPL_DATA_MGT_1 ON SLC; Supplier Portfolio Management (Reversible)

SMC_SUPPL_EVAL_1 ON SLC, Supplier Evaluation

SMC_SUPPL_QUA_BFW_1 ON SLC, Supplier Qualification (Buy Side)

SMC_SUPPL_QUA_OFW_1 ON SLC, Supplier Qualification (Sell Side)

SMC_SUPPL_REG_BFW_1 ON SLC, Supplier Registration (Buy Side)

SMC_SUPPL_REG_OFW_1 ON SLC, Supplier Registration (Sell Side)

SMC_SUPPL_SMNT_OFW_1 ON SLC, Supplier Data Maintenance (Sell Side)

SMC_ACTIVITY_MGT_OFW_1 ON SLC, Activity Management(Sell Side)

SMC_ACTIVITY_MGT_1 ON SLC, Activity Management(Buy Side)



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

4. Choose Back.

3.7 Software Landscape Diagram The following graphic illustrates the required software components if SAP Supplier Lifecycle Management 2.0 SP01 is deployed on SAP enhancement package 3 for SAP Supplier Relationship Management 7.0.

Block Diagram:

SLC Buy-side on

SRM Server

Sell-side

BGRFC

or SOA

SAP ERP

Backend



Details

Sell-Side and Buy-Side Deployment: SAP Supplier Lifecycle Management 2.0 SP01 on SAP enhancement package 3 for SAP SRM 7.0

3.8 Connectivity The following connectivity is required: You create connection between SLC@SRM Buy-Side system to SUS Sell-Side System and running Backend ECC system.

Here for Automated content to work we need to create Trusted RFC’s for above system topology by the customer BASIS administrator with the authorizations as per described in below section 3.9.

The trusted RFC’s are used for Remote activation of RDS Content.

3.9 Authorizations

Use



In this activity, you create a user to run the activation of the related SAP Rapid Deployment Solution scope.

Customers need to provide relevant authorization for the Activation or Login User for cross-communication between clients, servers, portals etc and other configurations like Workflow customizing, RFC destinations creation etc which involves critical access. These have to be provided based upon your company security norms.

We recommend using only one User ID to activate the SAP Rapid Deployment Solution content. Thus you avoid changing ownership during the activation of the solution.

SAP does not supply separate Customizing or setup roles (according to the security guideline). Instead, use the functions provided in Role Maintenance (transaction PFCG). In the Role Maintenance, you can define a role corresponding to your individual IMG project with all the authorizations you need to access the IMG activities required for the SAP Rapid Deployment Solution scope. For more information about defining a role for a Customizing project, see the documentation for transaction PFCG.

If authorization issues occur during activation you can use transaction SU53 to get information on the missing authorizations and extend the authorization data as necessary.

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 the User ID and choose Create.

3. Choose the Address tab.

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.



Password <initial password>

User type Dialog

7. Choose the Defaults tab.



Logon language EN

Decimal notation 1.234.567,89

Date format DD.MM.YYYY

Output Device <your printer name>



9. Choose the Roles tab and enter the user role you created that contains the necessary authorization profile.

11. Save your entries.

Result You have created the user to activate SAP Rapid Deployment Solution content.

Repeat the steps above for all systems and clients you use. Make sure that you always create the same user in all systems and clients.

Additional Authorizations for Business/Technical USERs: Provide additional Authorizations for the below Business USERS.

1. User CATMAN (Buy-Side)

Object: CA_POWL

Field Name: POWL_APPID Value : *

Field Name: POWL_CAT Value : *

Field Name: POWL_LSEL Value : *

Field Name: POWL_QUERY Value : *

Field Name: POWL_RA_AL Value : *

Field Name: POWL_TABLE Value : *

Object: /SRMSMC/AC

Field Name: /SRMSMC/AC Value: *

Object: /SRMSMC/BO

Field Name: /BOFU/BO Value: *

Field Name: ACTVT Value:*

Object: /SRMSMC/EX


Object: S_ICF

Field Name: ICF_FIELD Value:*

Filed Name: ICF_VALUE Value:*

2. User RFC_SMNGT (Sell-Side)

Object: S_USER_AGR


Field Name: ACT_GROUP Value:*

Object: S_USER_GRP


Field Name: CLASS Value:*

Object: S_USER_PRO




Filed Name: PROFILE Value:*

3. RFCSYSUSER for SOA settings in SELL-SIDE system requires above RFC_SMNGT additional authorisation.

Directly after activation of the SAP Rapid Deployment Solution content, remove the authorizations you have given to the system user that has performed the activation steps. Thus you avoid that the system user misuses the authorizations granted before.

4 Technical Requirements for SLC@ERP This section contains technical requirements in different areas. For each requirement, the relevance for scope items of the package is provided.

The table lists all software required to implement and run the solution:

Product Product Version Comment

SAP ERP EHP 7 for ERP 6.0 Used as basis for SLC for Buyside

SAP SRM EHP 3 for SRM 7.0 Based on SAP EHP3 FOR SAP NETWEAVER 7.0 needed for Sellside

SAP NETWEAVER

EHP2 for SAP NETWEAVER Or higher

Usually, required software components and SP levels are downloaded using the Maintenance Optimizer of the SAP Solution Manager. If you need to download manually from the SAP Software Distribution Center in the Service Marketplace, use the following navigation paths:


Entry by Application Group SAP Application Components


Patches Entry by Application Group SAP Application Components

4.1 Software Product Versions The following software products and versions are required:

Product Product Version Components SAP Solution Manager Logical Component

Comments

Relevance

SAP SLC Supplier lifecycle management 2.0

SRMSLC ERP60_EHP7_CENTRAL_APPL_SLC

All SLC@ERP Scope Items





EHP 7 for ERP6.0

EHP7 FOR SAP ERP 6.0 (SP03) - central applications

SAP_APPL ERP60_EHP7_CENTRAL_APPLICATION

EHP 3 for SRM 7.0

Based on SAP EHP3 FOR SAP NETWEAVER 7.0

SRM_SERVER

SRM70_EHP3_SLC_SUS

Sell-side system “SUS”)

4.1.1 Software Product Versions

4.1.1.1 SAP Supplier Life Cycle Management on SAP ERP Core Component Server 6.0

Product Version

Release SP Level Comment

EHP 7 for ERP6.0

607 0007 SAP enhancement package 7 for SAP ERP 6.0

You can find detailed information on the SPS definition for the SRs of SAP ERP in the SAP Note 774615 – Support Package levels of ERP/ECC installations/upgrades.

The following software components are bundled with SAP ERP 6.0 EhP 7

Software Component

Release SP Level Description

SAP Basis 7.40

(SAP_BASIS)


SAP ABA 7.40

(SAP_ABA)


PI Basis 7.40

(PI_BASIS)



(WEBCUIF)



(SAP_BS_FND)


SAP BW 7.40

(SAP BW)


SAP APPL 6.17

(SAP_APPL)

617 0007 Logistics and Accounting




SAP AP_700


SMCERPIT

100 0009 Integration Comp. for Integration of Supplier Lifecycle Management 2.0


4.1.1.2 SAP Supplier Relationship Management – Enhancement Package 3 for SRM 7.0 – Sell side SAP SLC on SAP SUS

Product Version Release SP Level Comment

EHP 3 for SRM 7.0 713 0007 Based on SAP EHP3 FOR SAP NETWEAVER 7.0

The following applicable software components are bundled with SAP SRM 7.03:

Software Component

Release SP Level Description

SAP Basis 7.40

(SAP_BASIS)


SAP ABA 7.40

(SAP_ABA)


PI Basis 7.40

(PI_BASIS)



(WEBCUIF)



(SAP_BS_FND)


SAP BW 7.40

(SAP BW)


SAP AP_700


SRM SERVER 7.13

(SRM_SERVER)

713 0007 SAP Enhancement Package 7 for SAP ECC 6.0 (ABAP) is in sync with

SRM SERVER



SRM_SERVER 703

SRM_PLUS 713 0007 SRM_PLUS for mySAPSRM

SMCSRMIT 100 0009 Integration Comp. for Integration of Supplier Lifecycle Management 2


We require two servers or clients with above configuration to set up SAP Supplier Life Cycle Management. One SRM Server for the Buy Side and one for the Sell Side of SAP Supplier Life Cycle.

Required software components and SP levels are usually downloaded using the Maintenance Optimizer of the SAP Solution Manager. If you need to download manually from the SAP Software Distribution Center in the Service Marketplace, use the following navigation paths:

Installation:


Installations and Upgrades A - Z Index Select S (on the Installations and Upgrades tab

page on the main page) SAP SRM SAP SRM ENHANCE PACKAGE EHP2 FOR

SAP SRM 7.0 Installation <Select your target DB> 51036866, "DVD SAP SRM 7.0 SR1/NW7.01 SR1 Installation Export "

Support Packages:


Support Packages and Patches A - Z Index Select S (on the Support Packages and

Patches tab page on the main page) SAP SRM SAP SRM ENHANCE PACKAGE

EHP3 FOR SAP SRM 7.0 Entry by Component SRM Server SRM Server 7.03

4.2 SAP Notes The following SAP Notes need to be considered:

SAP Note No

Content Comments Relevance

1736212 FileUpload: File is not uploaded

1776744 Corrections for unified rendering up to SAP_BASIS










1574317 The Release Information Note (RIN) contains information about and references to SAP Notes for applying support packages to SAP Supplier Lifecycle Management 1.0.

1838973 This Release Information Note (RIN) contains detailed information about and references to SAP Notes required for applying SP04 of SAP Supplier Lifecycle Management 1.0.

1598759 The Add-On Installation Note describes what needs to be done to install SAP Supplier Lifecycle Management based on SAP enhancement package 2 for SAP NetWeaver 7.0 technology.

1612290 The Integration Component Installation Note provides information about the prerequisites and installation of SAP Supplier Lifecycle Management integration components for SAP ERP and SAP SRM.

0002135748 SLC@ERP mising create/change authorization for vendor master

SLC-SUP

0002136177 SLC@ERP mising create/change authorization for vendor master

SLC-SUP

0002140623 Sellside Task Menu corrupted in case of Customer Roles

SLC-ACT

2123491 Supplier are not able to access tasks of activity management

SLC-ACT

2131830 THTMLB Tree tag is returning empty rows

CA-WUI-UI-TAG


SLC-SUP


SLC-SUP

4.3 SAP Solution Manager and SAP Solution Manager Content Add-On

For the implementation of the solution package, SAP Solution Manager is recommended.


SAP Solution Manager SAP Solution Manager 7.0 Enhancement Package 1

If using SAP Solution Manager 7.0 with SP below 24, see SAP Note












SP18 or higher

Or

SAP Solution Manager 7.1

SP01 or higher

Or

SAP Solution Manager 7.1 on HANA (ST 712)

SP00 or higher

1579267.

For SAP rapid-deployment solutions, implementation content is available in SAP Solution Manager templates.

The SAP Solution Manager template for this solution package is in the ST-RDS 100 content add-on. You can download the latest available ST-RDS 100 content add-on from SAP Software Download Center on SAP Service Marketplace at service.sap.com/swdc.

For more information about downloading and installing ST-RDS 100 content add-ons, see SAP Note 1726649 and SAP Note 1686668 respectively.

In the ST-RDS 100 content add-on, access the template in the following way:

If you have SAP Solution Manager 7.1 SP04 or lower, select the template ID and template name in the table below.

If you have SAP Solution Manager 7.1 SP05 or higher, select the solution package name(s) in the table below.

Template ID and Template Name

RDS_SLC_SRM703V4 - SAP Supplier Lifecycle Management RDS_V4

Solution Package Name(s)

SAP Supplier Lifecycle Management RDS SLC@ERP with BGRFC_V4

4.4 SAP Best Practices Solution Builder and Activation Content Add-On

For tool-supported, automated activation of the solution package, SAP Best Practices solution builder is recommended.



BP-SOLBLD 70Vx

Always use the latest available version as outlined in SAP Note 1301301.

Add-on for the implementation tool (only necessary to be implemented in a system where content activation shall be done using the Solution Builder (i.e. Sandbox or Development System).

The following content is required:

Product Product Version Components Comments Relevance








as tested

BP-ERP 617Vx Vx

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

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

SAP Best Practices All-in-One based on SAP ERP.

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

BP-CANW 740Vx Vx SAP Best Practice to be installed on SRM Server (SRM-SUS)

BP-SOLBLD 70Vx Vx SAP Best Practices solution builder

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

4.5 Other Deployments

4.5.1 SAP Frontend Components

4.5.1.1 Enterprise Portal Ensure that you have installed the latest applicable SAP frontend components.

If you want to use the Enterprise Portal, use the following SAP NetWeaver EP version:

SAP Release Components







Components

SAP NetWeaver EP 7.03 EP BC 7.0 SP24 X or higher version

EP Content EP 7.03 BP SLC 100 X Portal Content for SAP Supplier Lifecycle

Management 1.0 or higher version





4.5.1.2 SAP NetWeaver Business Client If you want to use the NetWeaver Business Client you have to use following version:

SAP Components

Release Component Comment

SAP NetWeaver Business Client

NWBC NW BUSINESS CLIENT 4.0

BC-WD-CLT-BUS SAP Note 1353538





You can find additional information about the NWBC in SAP Note 900000. Further release restrictions are listed in SAP Note 1029940 and configuration instructions in SAP Note 1368177.

4.6 Activate Business Functions Functionality in this solution package requires certain business functions to be active in the SAP landscape. These business functions need to be activated:

Product Business Function Configuration or Data required

Relevance

SLC SMC_SUPPL_CLASS_1 SLC, Supplier Classification (Reversible)

SLC SMC_SUPPL_DATA_MGT_1 SLC; Supplier Portfolio Management (Reversible)

SLC SMC_SUPPL_EVAL_1 SLC, Supplier Evaluation








SLC SMC_SUPPL_QUA_BFW_1 SLC, Supplier Qualification (Buy Side)

SLC SMC_SUPPL_QUA_OFW_1 SLC, Supplier Qualification (Sell Side)

SLC SMC_SUPPL_REG_BFW_1 SLC, Supplier Registration (Buy Side)

SLC SMC_SUPPL_REG_OFW_1 SLC, Supplier Registration (Sell Side)

SLC SMC_SUPPL_SMNT_OFW_1 SLC, Supplier Data Maintenance (Sell Side)

SRM SRM_ANALYTICS_1 SRM, Analytics (Reversible)

SRM SRM_CONT_IMPR SRM, Continuous Improvement CC (Reversible)

SLC SMC_ACTIVITY_MGT_1 SLC, Activity Management (Buy Side) (Reversible)

SLC SMC_ACTIVITY_MGT_OFW_1 SLC, Activity Management (Sell Side) (Reversible)

4.7 Software Landscape Diagram The following graphic illustrates the required software components if SAP Supplier Lifecycle Management 2.0 SP01 is deployed on SAP enhancement package 3 for SAP Supplier Relationship Management 7.0.

Block Diagram:

SLC Buy-side on

SAP ERP

Sell-side (SUS)

SRM7.03 BGRFC



4.8 Connectivity You create connection between SLC@SRM Buy-Side system to SUS Sell-Side System and running Backend ECC system.

Here for Automated content to work we need to create Trusted RFC’s for above system topology by the customer BASIS administrator with the authorizations as per described in below section 4.9.

The trusted RFC’s are used for Remote activation of RDS Content.

4.9 Authorizations

Use In this activity, you create a user to run the activation of the related SAP Rapid Deployment Solution scope.

Customers need to provide relevant authorization for the Activation or Login User for cross-communication between clients, servers, portals etc and other configurations like Workflow customizing, RFC destinations creation etc which involves critical access. These have to be provided based upon your company security norms.



We recommend using only one User ID to activate the SAP Rapid Deployment Solution content. Thus you avoid changing ownership during the activation of the solution.

SAP does not supply separate Customizing or setup roles (according to the security guideline). Instead, use the functions provided in Role Maintenance (transaction PFCG). In the Role Maintenance, you can define a role corresponding to your individual IMG project with all the authorizations you need to access the IMG activities required for the SAP Rapid Deployment Solution scope. For more information about defining a role for a Customizing project, see the documentation for transaction PFCG.

If authorization issues occur during activation you can use transaction SU53 to get information on the missing authorizations and extend the authorization data as necessary.

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 the User ID and choose Create.

3. Choose the Address tab.



Last name <Last name of the user>

First name <First name of the user>

5. Choose the Logon Data tab.



Password <initial password>

User type Dialog

7. Choose the Defaults tab.



Logon language EN

Decimal notation 1.234.567,89

Date format DD.MM.YYYY

Output Device <your printer name>

9. Choose the Roles tab and enter the user role you created that contains the necessary authorization profile.

11. Save your entries.

Result



You have created the user to activate SAP Rapid Deployment Solution content.

Repeat the steps above for all systems and clients you use. Make sure that you always create the same user in all systems and clients.

Additional Authorizations for Business/Technical USERs: Provide additional Authorizations for the below Business USERS.

1. User CATMAN (Buy-Side)

Object: CA_POWL

Field Name: POWL_APPID Value : *

Field Name: POWL_CAT Value : *

Field Name: POWL_LSEL Value : *

Field Name: POWL_QUERY Value : *

Field Name: POWL_RA_AL Value : *

Field Name: POWL_TABLE Value : *

Object: /SRMSMC/AC

Field Name: /SRMSMC/AC Value: *

Object: /SRMSMC/BO



Object: /SRMSMC/EX


Object: S_ICF

Field Name: ICF_FIELD Value:*

Filed Name: ICF_VALUE Value:*

2. User RFC_SMNGT (Sell-Side)

Object: S_USER_AGR


Field Name: ACT_GROUP Value:*

Object: S_USER_GRP


Field Name: CLASS Value:*

Object: S_USER_PRO


Filed Name: PROFILE Value:*



Directly after activation of the SAP Rapid Deployment Solution content, remove the authorizations you have given to the system user that has performed the activation steps. Thus you avoid that the system user misuses the authorizations granted before.

AP SRM 7 EhP3 or SAP ERP 6 EhP7 - websmp202.sap-ag.desapidp/012002523100002826722015E/RDS_SLC...AP...

Documents

Transcript of AP SRM 7 EhP3 or SAP ERP 6 EhP7 - websmp202.sap-ag.desapidp/012002523100002826722015E/RDS_SLC...AP...