add config material srm 70

7/14/2019 Add Config Material SRM 70

http://slidepdf.com/reader/full/add-config-material-srm-70 1/33

A d d i t i o nal Co n f i g ur at i onMat er i al f or SAP SRM 7.0

Re lease 2008



SRM 7.0 17.02.2009

2



SRM 7.0 17.02.2009

3

Copyright

©Copyright 2007 SAP AG. All rights reserved.

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

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

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

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registeredtrademarks 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 aretrademarks or registered trademarks of Citrix Systems, Inc.

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

J ava is a registered trademark of Sun Microsystems, Inc.

J avaScript is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, BACK-END, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAPproducts and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of SAP AG in Germany and in several other countries all over theworld. All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.

These materials are subject to change without notice. These materials are provided by SAPAG and its affiliated companies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting anadditional warranty.



SRM 7.0 17.02.2009

4

SAP - Important Disclaimers

SAP Library document classification: PUBLIC

This document is for informational purposes only. Its content is subject to change withoutnotice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES,EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULARPURPOSE.



SRM 7.0 17.02.2009

5

Table of Contents:1 Service Procurement Scenario.......................................................................................6

1.1 Overview..............................................................................................................6

1.1.1 New Features:..................................................................................................7

1.1.2 Advantages of SAP SRM 7.0 with SAP ERP6.0 SAP Enhancement Package 4.0over previous releases of SAP SRM:..............................................................................7

1.2 Configuration:.......................................................................................................7

1.2.1 Configurations in SAP ERPsystem (Release SAP ERP 6.0 SAP EnhancementPackage 4.0)..................................................................................................................7

1.2.2 Configurations in SAP PI system......................................................................9

1.2.3 Configurations in SAP SRM system................................................................10

1.2.4 Configurations in SAP SRM-MDM..................................................................13

1.2.5 Configurations in SAP Enterprise Portal for harmonized user role:..................13

1.3 Testing...............................................................................................................14

2 Sourcing Scenario........................................................................................................15

2.1 Overview............................................................................................................15

2.1.1 Automatic demand transfer from SAP ERPto SAP SRM .................................15

2.1.2 Manual demand transfer through user interaction...........................................16

2.1.3 Direct RFx creation from SAP ERPsystems into SAP SRM for centralizedsourcing 16

2.2 Configuration:.....................................................................................................17

2.2.1 Configuration in SAP ERPsystem:..................................................................17

2.2.2 Configurations in SAP PI system:...................................................................17

2.2.3 Configurations in SAP SRM system:...............................................................18


2.2.5 Testing...........................................................................................................18

3 Central Contract Management Scenario.......................................................................19

3.1 Overview............................................................................................................19

3.1.1 Benefits and Features:....................................................................................20

3.1.2 Advantages of SAP SRM 7.0 over previous release of SAP SRM:..................20

3.2 Configuration:.....................................................................................................21

3.2.1 Configurations in SAP ERPsystem (Release ERP 6.0 SAP EnhancementPackage 4.0)................................................................................................................21

3.2.2 Configurations in SAP PI system:...................................................................22

3.2.3 Configurations in SAP SRM system:...............................................................22


3.2.5 Testing...........................................................................................................23

4 Appendix......................................................................................................................24

4.1 BAdi Implementations:........................................................................................24

4.1.1 Implementation of BAdi ME_REQ_SOURCING_CUST...................................24



SRM 7.0 17.02.2009

6

4.1.2 Implementation of BAdi BBP_EBPXML_OUT_BADI .......................................29

4.2 Frequently Asked Questions...............................................................................31

5 References:..................................................................................................................33

This document contains additional information for the configuration of SAP SupplierRelationship Management 7.0 (SAP SRM 7.0) and should only be used in conjunction withthe Solution Manager Content for SAP SRM 7.0 (for more information, see the SAP SRM 7.0Master Guide at http://service.sap.com/instguides ->Installation & Upgrade Guides ->SAPBusiness Suite Applications ->SAP SRM ->SAP SRM Server 7.0).

SAP SRM 7.0 delivers new features in following integration scenarios with SAP EnterpriseResource Planning (SAP ERP) 6.0 SAP Enhancement Package 4.0:

1. Service Procurement

2. Sourcing

3. Central Contract Management

This document describes different configurations required for new features developed in eachof the above scenarios. Implementation of BAdi’s and frequently asked questions arecovered in the Appendix.

1 Service Procurement Scenario

1.1 Overview

Service Procurement Scenario supports procurement of various service types commonlyused in major industries, such as time-based and deliverable-based services, externalstaffing.

SAP SRM 7.0 can be integrated with different releases of SAP ERP systems. SAP ERP 6.0SAP Enhancement Package 4.0 is the recommended SAP ERP version to access new andenhanced Service Procurement (MM-SRV) features in SAP SRM 7.0.

SAP SRM 7.0 works with older versions of SAP ERP and BACK-END, but ServiceProcurement (MM-SRV) is not supported in the standard release.

The required settings for integration of SAP SRM 7.0 with SAP ERP versions (up to SAP ERP6.0 SAP Enhancement Package 3.0) remain the same as in older SAP SRM versions.

This document explains the settings required to integrate SAP SRM 7.0 with SAP ERP 6.0SAP Enhancement Package 4.0.

Figure: Overview of Service Procurement



SRM 7.0 17.02.2009

7

1.1.1 New Features:

Sourcing Enablement for Purchase Requisitions for External Service Procurement in SAPSRM.

Purchase Order and Contract Creation in SAP ERPbased on SAP SRM RFx includingResponse Modification.

Enable Supplier Collaboration for External Service Procurement by integration betweenMM-SRV and Supplier Self-Service.

Enhance SUS to allow supplier to submit Service Entry Sheet and Invoice for servicesperformed.

1.1.2 Advantages of SAP SRM 7.0 with SAP ERP 6.0 SAPEnhancement Package 4.0 over previous releases of SAP SRM:

Features

SAP SRM 7.0with SAPERP6.0 SAPEnhancementPackage 4.0

( SAP SRM 7.0 & SAPERP2005 SAP EnhancementPackage 3.0 or less ) andSAP SRM 6.0 or less

PR with Hierarchical structure transferredto SAP SRM

Supported Not Supported

Response Modification for RFx based onpreceding MMSRV document


Purchaser defined line types in RFxevents


Catalog with hierarchical servicestructures


Follow on document in SAP ERPincludingResponse Modification items


1.2 Configuration:

For SAP SRM 7.0 with SAP ERP6.0 SAP Enhancement Package 4.0, the following solutionsare mandatory: SAP ERP, SAP SRM, SAP PI, SAP Enterprise Portal. Configurations requiredin these solutions are detailed below:

1.2.1 Configurations in SAP ERP (Release SAP ERP 6.0 SAPEnhancement Package 4.0)

Step 1: Ensure that SAP Enhancement Package 4.0 business function LOG_MM_P2PSE_1is ON.

Goto transaction SFW5 and expand node ‘Enterprise Business Functions’:



SRM 7.0 17.02.2009

8

Activate the switch LOG_MM_P2PSE_1

Note

You can get the complete documentation on business function _ LOG_MM_P2PSE_1 byclicking on the information icon under Documentation highlighted in the abovescreenshot.

Step 2: Create Implementation of BAdi ME_REQ_SOURCING_CUST. Refer to Appendixsection 5.1.1 for complete details.

Step 3: Activate event type linkages for external sourcing

Go to transaction SWETYPV in SAP ERPsystem. Check that the following entries are present:

If it is not present then copy the entry for event ‘Created’ for object type ‘BUS2105’and Receiver Type ‘WS53800009’ and change the event name.

Note

Workflow event RFXREQUESTED is used to trigger XML message while creating SAPSRM RFx from Collective Processing of Purchase Requirements (CPPR).Workflow event SOURCINGREQUESTED is used to trigger an XML message whiletransferring the Purchase Request (PR) as an external requirement to SAP SRMSourcing.If you do not see XML messages getting created, verify that steps 3-5 are properlyconfigured.

Step 4: Activate outbound messages through qRFC

(ERP) Transaction SPRO ->Other mySAP.com components

Supplier RelationshipManagementMessage Control Activate outbound messages through qRFC



SRM 7.0 17.02.2009

9

Check that following entries are present:

Step 5: Configure RFC destination for the Workflow system.

Go to Transaction SM59 Select Logical Connections Create a new connection for the desired client in the Workflow system

Step 6: Configure RFC destination for SAP Information Exchange (SAP XI).

Go to Transaction SM59 Select HTTP Connections to ABAP System Create a new connection for the SAP XI

Step 7: Create SU01 XI user:

Go to Transaction SU01. Create an SAP XI user that is used in transferring and receiving the XMLs between

the two systems.

Note

To ensure that normal PR creation in SAP ERP is not affected, maintain customizing

for System Messages. Transaction SPROMaterials Management External Services ManagementDefine Attributes of System Messages.

Maintain category as ‘W’ (Warning) in Message 35.

EPRTRANS table is not used.

Background report BBP_EXTREQ_TRANSFER should not be scheduled orexecuted.

BAdi BBP_BADI_EXTREQ_OUT or user exit BBPK001 is no longer used in this case.

1.2.2 Configurations in SAP Process Integration (SAP PI)For more details see Solution Manager under Configuration SAP SRM 7.0 BasicSettings for Service Procurment Classic System Connections SAP Netweaver ProcessIntegration



SRM 7.0 17.02.2009

10

Figure: ESOA Services for service procurement

For more details, refer to http://help.sap.com and http://service.sap.com/instguides.

Note

Integration Scenario, SE_Services_Procurement, contains the necessary processmappings. These need to be configured in the Integration Directory.

Consulting SAP Note 1270081 contains troubleshooting tips forESOA services inSAP SRM.

1.2.3 Configurations i n SAP SRM

Step 1: Configure RFC destination for SAP XI system.

Go to Transaction SM59 Select HTTP Connections to ABAP System Create a new connection for the SAP XI system

Note

Here, assume that the RFC destination to SAP ERP is configured as in previous releases.

http://help.sap.com/

http://service.sap.com/instguides



http://help.sap.com/



SRM 7.0 17.02.2009

11

Step 2: Create SU01 XI user:

Go to Transaction SU01. Create an SAP XI user that is used in transferring and receiving the XMLs between

the two systems.

Step 3: Purchasing organization assignment to RFC user

Go to transaction PPOSA_BBP in SAP SRM system. Search for RFC user used in SAP XI system for defining RFC destination to SAP

SRM system. Check that this user is assigned to purchasing organization.

Note

This step remains the same as in earlier releases of SAP SRM. Maintain user andorganizational data for RFC channel users.

Step 4: Hierarchy Configurations:

Refer to SAP Note 1269445. This note has manual corrections. Please carry outthese corrections in SAP SRM.

Go to transaction SPRO, and check the customizing found in this path:

a. SAP Implementation Guide SAP Supplier Relationship ManagementSRM Server Cross-Application Basic Settings Configurable ItemNumbering Define Configurable Item Numbering Scheme

b. Read documentation provided here. Important steps to complete:i. Configure rule components for each rule.

ii. Configure rule assignment for item level.[Please note: Do not configure anything else at this time unless you haveextensive experience with line item numbering configurations.]

c. Rules are assigned various rule components. Check that only one rule withcheckbox ‘Call-Offs Numbered Internally’ is set, as below:



SRM 7.0 17.02.2009

12

Note

Without this, item numbering of the line items in application will be blank.

Hierarchy customization for RFx and Quote

a) From SAP SRM 7.0, it is necessary to assign hierarchy templates to transactiontypes of business objects RFx and Quote.

b) A hierarchy template is a customizable hierarchical pattern which determines howa hierarchy is structured. It is possible to customize which item types (outlines,services, materials) appear in the procurement document, as well as on which

levels they appear in each of your hierarchy templates.After customizing a hierarchy template, assign the template to a documenttransaction type. Depending on the assigned template, the system determineswhich item types can be used in the hierarchy in the corresponding document.

c) In SAP SRM 7.0, there are standard hierarchy templates delivered: HIER_SRM,HIER_SE. It is not recommended to create new templates.

d) Hierarchy template HIER_SE can be assigned to RFxtransaction types of whichare intended for MM-SRV scenario.For other scenarios, we can assign hierarchy template HIER_SRM to transactiontypes of RFx.

e) For creation of new RFx transaction type, refer to SAP Note 1267549.

1. Refresh metadata entries (refer to SAP Note 1270412).

2. Corrections mentioned in these Notes are delivered as standard in SP02 and futurereleases.

Step 5: Number Range and Sourcing customizing

Number Range customizing and Sourcing customizing remain the same as in previousreleases. Ensure that Sourcing customizing for Product Categories in ServiceProcurement scenario is maintained as ‘Sourcing Always carried out’.

Step 6: Define Back-End Systems

Go to transaction SPRO -> SAP Implementation Guide SAP Supplier Relationship

Management

SRM Server

Technical Basic Settings

Define SystemLandscape



SRM 7.0 17.02.2009

13

Enter all required information about the SAP SRM and SAP ERP systems you wish toconnect to. The field "System Alias for POWL Navigaton" must be filled with thecorresponding system alias. This is maintained in the SAP Enterprise Portal's systemlandscape. The entry in this field is case sensitive.

The field "Integrated UI" must also be flagged, to indicate that this system is a part of Procure-to-Pay scenario.

1.2.4 Configurations in SRM-MDM

SRM-MDM is not mandatory solution for Business Suite 7. But to maintain masterdata for service hierarchies in SAP SRM, SRM-MDM 3.0 can be used.

SAP Note 1177780 is available for configuration of SRM-MDM 3.0.

SAP Note 1171711 provides details on SRM-MDM 3.0 repository information.

Use SAP Note 1224654 if repository is being upgraded from SRM-MDM 2.0 to SRM-MDM 3.0

1.2.5 Configurations in SAP Enterprise Portal for harmonizeduser role:

Check that all required Business Packages as mentioned in the SAP Note 1232945 areinstalled.

Note

If the data source in portal is maintained in LDAP & users are copied from SAP SRM

backend, then this step can be skipped. If the data source in portal is ABAP, thenproceed with the following steps:

Step 1: Assign Harmonized Roles to Users

After the installation of Business Package for SAP SRM 7.0, a set of new portalroles is created. These roles can be found in the folder structure:

Portal Content Content Provided by SAP specialist SRM 70 SuiteRoles

The Business Package for SAP SRM 7.0 offers four harmonized roles:

Operational Purchaser (SAP ERP)

Strategic Purchaser (SAP ERP)

Operational Purchaser (SAP ERP/SAP SRM)

Strategic Purchaser (SAP ERP/SAP SRM)

Roles Operational Purchaser (SAP ERP/SAP SRM) & Strategic Purchaser (SAPERP/SAP SRM) will show up applications from both SAP ERP & SAP SRMsystems and are considered as harmonized roles.

Step 3: Assign these harmonized roles to portal users as required.



SRM 7.0 17.02.2009

14

For more information on harmonized roles for SAP ERP and SAP SRM, see SAPSolution Manager under SAP SRM 7.0 Basic Settings for SAP SRMBusiness Package for SAP SRM 7.0 Configuration of Procure-to-Pay Scenario User Configuration Assigning Business Package roles to Users

Please refer to SAP Note 1263876 for additional information.

Note

SAP Supplier Self-Services (SAP SUS) configurations remain the same as inprevious releases.

1.3 Testing

The following configurations for Service Procurement in SAP SRM 7.0 with SAP ERP 6.0SAP Enhancement Package 4.0 must be implemented.

1Log on to SAP Enterprise Portal with user assigned with harmonized Purchasing role.

2Create PR with Service item and services under this item. Confirm that data providedhere matches with conditions mentioned in implementation of BAdiME_REQ_CUST_SOURCING so that PR can be transferred to external sourcing withoutmanual intervention.

3. Save the PR.

4. Go to Sourcing and check the PR (external requirement in SAP SRM) has beentransferred with all the services with hierarchy.

5. Create follow-on-document draft RFx in Sourcing.

6. Goto RFx and publish it by providing minimum required details.

7. Log on to user as Bidder and create response with RFx modification and submit theresponse by providing minimum required details.

8. Log on to SAP Enterprise Portal with user assigned with harmonized Purchasing roleand award the response.

9. Open the awarded response and create follow-on-document Purchase Order (PO).

10. Log on to SUS Portal with user having Order processor role.

11. Search for PO created from RFx Response.

12. Open the order and Create order response.

13. Log on to SUS portal with user having Service Agent role.

14. Create Service Entry Sheet for the Purchase order which is confirmed.

15. Log on to SAP Enterprise Portal with user assigned with harmonized Purchasing role.

16. Accept the service entry sheet from supplier.

17. Log on to SUS Portal with user assigned with Invoicing role.

18. Create Invoice and send the Invoice.

19. Log on to SAP Enterprise Portal with user assigned with harmonized Purchasing role.

20. Accept the invoice from Supplier.



SRM 7.0 17.02.2009

15

2 Sourcing Scenario

2.1 Overview

In Business Suite 7, Sourcing is enhanced through the increased integration of SAP SRM

7.0 and SAP ERP6.0 SAP Enhancement Package 4.0. This tightly integrated centralizedsourcing process in BS 7 provides:

the ability to simplify centralized sourcing by aggregating demands from multipleback-end SAP ERP systems into central SAP SRM system

online collaboration with suppliers reduced supply cycle time and communication errors easy identification of new suppliers reduced processing costs savings on time and sharper focus on strategic activities

Centralized sourcing in SAP SRM takes place in following ways:

2.1.1 Automatic demand transfer f rom SAP ERP to SAP SRM



SRM 7.0 17.02.2009

16

2.1.2 Manual demand transfer through user interaction

2.1.3 Direct RFx creation from SAP ERP into SAP SRM for



SRM 7.0 17.02.2009

17

Centralized Sourcing

2.2 Configuration:

Configuration for Processes 3.1.1 and 3.1.2 remains the same as the process described inConfiguration of Service Procurement Scenario in Section 2.2

Configuration for Process 3.1.3 Direct RFx creation from SAP ERP system to SAP SRMsystem for centralized sourcing is described below:

2.2.1 Configuration in SAP ERP:

This remains the same as the process described inSection 2.2.1

2.2.2 Configurations i n SAP PI:

For more details, see Solution Manager under Configuration SAP SRM 7.0 BasicSettings for Service Procurment Classic System Connections SAP Netweaver Process

Integration



SRM 7.0 17.02.2009

18

Figure: ESOA services for sourcing

Note

The Integration scenario SE_Sourcing_Enhancements contains the necessaryprocess mappings, which needs to be configured in the Integration Directory.

Here, services QueryCodeListProvider andRFQRequestSUITEAllowedBiddersByIndentifyingElementsQuery_In are synchronousservices.

SAP Note 1268336 provides detailed information on configuration of synchronousservices.

SAP Note 1270081 has troubleshooting tips for ESOA services in SAP SRM.

2.2.3 Configurations i n SAP SRM system:

Follow Step 1 to Step 7 as described in Section 2.2.3.

Step 8: BAdi Implementation

Implement method IF_EX_BBP_EBPXML_OUT_BADI~REQUESTFORQUOTE of BAdiBBP_EBPXML_OUT_BADI as described in Appendix Section 5.1.2


This process remains the same as that described inSection 2.2.4

Note

There are additional roles to be assigned for execution of synchronous services. SAP Note1268336 contain details of these roles.

2.2.5 Testing

Below are the minimum steps required to ensure that configurations for Sourcing in SAP SRM7.0 with SAP ERP6.0 SAP Enhancement Package 4.0 works as desired:



SRM 7.0 17.02.2009

19

1. Log on to SAP Enterprise Portal with a user that has the roleSAP_SRM_ERP_OP_HARMassigned and navigate to the work center, Purchasing (Harmonized).

2. Create Purchase Requisitions that contain Service and Standarditems (the item category is ‘D’ for service items, and blank for other items).

3. Navigation path to reach Enterprise Portal CPPR: Purchasing PurchasingDocuments Purchase Requitions

4. Search and Select the Purchase Requisitions created in Step 1 and select ‘StartCollective Processing’.

5. Select the PR and Create RFx.

6. Publish the RFx after entering all the mandatory fields.

7. Log on to SAP SRM portal as a Bidder and submit the new RFx bid.

8. Log on to SAP SRM portal as Purchaser with harmonized role and accept theRFxResponse.

9. Once the Rfx Response is accepted, create Follow-on Document Purchase Order orContract as per the requirement.

3 Central Contract Management Scenario

3.1 Overview

The Central Contract Management scenario deals with the creation and maintenance of

Contracts which are long term agreements between Strategic Purchasers and Suppliers. Thisacts as a template for applying discounts/price based conditions when Purchase Orders orany other purchasing documents are used for procurement.

Contracts can also be distributed from SAP SRM to any SAP ERP backend systems so thatcondition and pricing benefits are also available in procurement in the backend. Here, theSAP SRM contract acts as a central contract document and the distributed one in SAP ERP is

just a technical document for reference purposes.



SRM 7.0 17.02.2009

20

1. SAP SRM sends contract data to SAP ERP.

2. Contract data is stored in a specific object in SAP ERP.

3. Search for source of supply in SAP ERP yields specific object and assigns it to the sourcelist/purchase requisition.

4. When the PO is created out of the purchase requisition, contract completion data requestis sent to SAP SRM.

5. SAP SRM calls the Internet pricing and configurator (IPC) tool for the latest pricinginformation.

6. Price calculation and evaluation of background information are performed and contractrelease information data is sent to SAP ERP.

7. After the PO has been released, release information is sent to SAP SRM in order toupdate the contract.

8. Purchaser requisition document history is updated with contract and PO data.

Settings required for integration of SAP SRM 7.0 with SAP ERP versions until SAP ERP 6.0SAP Enhancement Package 3.0 remains the same as in older SAP SRM versions. Thisdocument explains the settings required to integrate SAP SRM 7.0 with SAP ERP 6.0 SAPEnhancement Package 4.0.

3.1.1 Benefits and Features:

Purchase Contracts and GOA’s are merged to form a single Central Contract which isavailable for sourcing locally in SAP SRM and can also be distributed to different SAPERP systems

Release information in SAP ERP is updated back to SAP SRM. This helps in gettingmore discounts if the contract is part of a hierarchy.

Currency at distribution level enables better integration with SAP ERP systems as the

same item can be distributed to SAP ERP systems with different currencies.

3.1.2 Advantages of SAP SRM 7.0 over previous release of SAP SRM:

Feature SAP SRM 7.0 SAP SRM 6.0 / 5.0

Aggregate based discounts Applicable for release fromboth SAP SRM and SAP ERP

Applicable only for localpurchase contracts in SAPSRM

Block Local Sourcing New column at item to block itlocal sourcing

Not applicable as GOA’s arenot available for sourcing

Currency At distribution level, whichhelps in maintaining differentcurrency for each distributionentry based on SAP ERPpurchase organization

At item level, for which itemhad to be duplicated for newdistribution entry with eachdifferent currency

Maintaining Distribution entries Now features ‘AssignDistribution’ button onitemlevel, through whichdistribution entries can be

maintained for multiple items atthe same time

User has to go to each item tomaintain distribution entries forthat item.(It was header leveldistribution in 5.0)



SRM 7.0 17.02.2009

21

Contract Hierarchy Central contracts havehierarchies and benefits fromSAP ERP call-off also.

Only Purchase contractssupported contract hierarchiesand not GOA’s

Backend transfer mode Uses SAP XI based services totransfer to SAP ERP backends

which are SAP EnhancementPackage 4.0 and above

Uses IDOCs for SAP ERPtransfer

Releases Handled centrally in thedocument

Separate for purchasecontracts and GOA’s

Contract Mass Update Mass update of contracts fromaward winning Bid

Feature not available

3.2 Configuration:

For Business Suite 7, SAP ERP, SAP SRM, SAP PI, SAP Enterprise Portal are mandatorysolutions.

3.2.1 Configurations in SAP ERP system (Release SAPERP6.0 SAP Enhancement Package 4.0)

Step 1: Ensure that SAP Enhancement Package 4.0 business function LOG_MM_P2PSE_1is ON.

This step is same as Step 1 of Section 2.2.1

Step 2: Configure RFC destination for the Workflow system.

Go to Transaction SM59 Select Logical Connections Create a new connection for the desired client in the Workflow system

Step 3: Configure RFC destination for SAP XI system.

Go to Transaction SM59 Select HTTP Connections to ABAP System Create a new connection for the SAP XI system

Step 4: Price and Condition setting.

The condition types mapping between SAP SRM and SAP ERP have to be done aspart of a IMG activity:

Integration with Other mySAP.com Components Supplier RelationshipManagement Central Contract Assignment of Conditions

The point in time when the current prices from SAP SRM arequeried can be defined. This is relevant to purchase order items with reference to acentral contract (call-off).



SRM 7.0 17.02.2009

22

Integration with Other mySAP.com Components Supplier RelationshipManagement Central Contract Price Calculation

3.2.2 Configurations in SAP PI system:

For more information, see Solution Manager under Configuration SAP SRM 7.0 BasicSettings for Service Procurment Classic System Connections SAP Netweaver ProcessIntegration

Figure: ESOA services for Central Contract Management

Note

The Integration scenario contains the necessary process mappings, which need to beconfigured in the Integration Directory.

Here, services PurchaseOrderSRMPricingSimulateQueryResponse_Out andPurchasingContractSRMArchivingCheckQueryResponse_Out are synchronousservices. SAP Note 1268336 provides detailed information on configuration of synchronous services.

Consulting SAP Note 1270081 is created for troubleshooting if anything goes wrongin ESOA services in SAP SRM.

3.2.3 Configurations i n SAP SRM system:

Step 1: Configure RFC destination for SAP XI.

Go to Transaction SM59 Select HTTP Connections to ABAP System Create a new connection for the SAP XI

Step 2: Number Range

Number Range customizing remains the same as in previous releases.

Step 3: Define Back-End Systems

The customizing remains the same as in previous releases. It has to be noted that thebackend system defined is SAP Enhancement Package 4.0 in SPRO ->SupplierRelationship Management ->SRM Server Technical Basic Settings DefineSystem Landscape.

Step 4: New Transaction type

The ‘Characteristic Value’ which was present till 6.0 to choose between PurchaseContract and GOA, has been removed. Now the type is always Central Contract.



SRM 7.0 17.02.2009

23

Define new transaction types in SPRO ->Supplier Relationship Management ->SRMServer Cross-Application Basic Settings Define Transaction Types.

Step 5: PPOMA_BBP entry

New transaction type defined has to be assigned the CT_PROC_TY attribute in the

Organization Plan (PPOMA_BBP) transaction.

Step 6: WF-Batch user in Organization Plan

WF-BATCH user should be added to SAP SRM organization plan and this usershould have following roles: /SAPSRM/ST_PURCHASER and/SAPSRM/EMPLOYEE.

Step 7: Configure Alert parameter

Alert parameters can be configured in the customizing function with default values in

SPRO ->Supplier Relationship Management ->SRM Server Cross-ApplicationBasic Settings Enter Alert Threshold Data for Contracts.

Note

Please refer to SAP Note 1268821 for more details on Central Contract Managementconfigurations in SAP SRM and SAP ERP.


This remains same as described inSection 2.2.4

Note

There are additional roles to be assigned for execution of synchronous services. See SAPNote 1268336 for details of these roles.

3.2.5 Testing

Below are the minimum steps required to ensure that configurations for Central ContractManagement in SAP SRM 7.0 with SAP ERP6.0 SAP Enhancement Package 4.0 works asdesired:

21. Log on to SAP Enterprise Portal with user assigned with harmonized StrategicPurchasing role.

22. Create a central contract with basic header details like supplier and target value.

23. Add an item with a backend product category and enter a purchase organization of the same backend in the item distribution screen.

24. Also maintain price and conditions in the item.

25. Save and Release the Contract.

26. Login to the corresponding SAP ERP system and check for the central contract intransaction ME33K.

27. The contract will be replicated in the SAP ERP system with all the details, such asbasic header data, item price and conditions.



SRM 7.0 17.02.2009

24

28. Refer to this contract in SAP ERP PO and confirm that the latest pricing andconditions are applied to PO net price.

29. Save the PO and check the SAP SRM contract item releases for call-off values fromthe SAP ERP PO.

4 Appendix

4.1 BAdi Implementations:

4.1.1 Implementation of BAdi ME_REQ_SOURCING_CUSTa) Go to transaction SE18 and enter BAdi Name as ME_REQ_SOURCING_CUST.

b) Click on action ‘Display’.

c) Click on action ‘BAdi Implementation’ as highlighted:



SRM 7.0 17.02.2009

25

d) Create enhancement implementation as shown below:

e) Then you will be prompted to create BAdi implementation as follows:



SRM 7.0 17.02.2009

26

f) Copy sample class implementation CL_EXM_ME_REQ_SOURCE_CUST.

g) You will get 2 methods:



SRM 7.0 17.02.2009

27

h) Method:a. IF_EX_ME_REQ_SOURCE_CUST~ACTIVE: Here, 3 output parameters

need to be set to true. By default, coding from sample class will be copied. There is no need to modify anything here. when parameter CV_AUT_SOURCING is set to true, external sourcing

(e.g. SAP SRM system) is active in SAP ERP system when parameter CV_EXT_RFX_IND is set to true, RFx can be created

out of PR directly from SAP ERP system using application CPPR when parameter CV_EXT_SC_IND is set to true, PR in SAP ERP system

will be transferred to SAP SRM using application CPPR

b. IF_EX_ME_REQ_SOURCE_CUST~CHECK_EXTERNAL_SOURCE: Thismethod has output parameter CV_EXT_SOURCING. When this is set, PRwill be transferred to SAP SRM without any manual interaction in CPPR.Hence the code logic here needs to be adopted based on material group andpurchasing group, as in table V_T160EX.

i. For example: If V_T160EX has following entries corresponding toprofile 84 meant for SAP SRM 7.0 system then:



SRM 7.0 17.02.2009

28

Following code logic can be written in this method:

I F ( i s_r eq_i t em- ekgr p = ' E7U' AND i s_r eq_i t em- mat kl = ' QZA04' ) OR( i s_r eq_i t em- ekgr p = ' E7U' AND i s_r eq_i t em- mat kl = ' QZA05' ) OR( i s_r eq_i t em- ekgr p = ' E7U' AND i s_r eq_i t em- mat kl = ' QZA06' ) OR( i s_r eq_i t em- ekgr p = ' E7U' AND i s_r eq_i t em- mat kl = ' QZA07' ) OR( i s_r eq_i t em- ekgr p = ' E7U' AND i s_r eq_i t em- mat kl = ' QZA08' ) OR( i s_r eq_i t em- ekgr p = ' E7U' AND i s_r eq_i t em- mat kl = ' QZA09' ) OR( i s_r eq_i t em- ekgr p = ' E7U' AND i s_r eq_i t em- mat kl = ' QZA10' ) OR( i s_r eq_i t em- ekgr p = ' E7U' AND i s_r eq_i t em- mat kl = ' QZA11' ) OR( i s_r eq_i t em- ekgr p = ' E7U' AND i s_r eq_i t em- mat kl = ' QZA12' ) .

cv_ext_sourci ng = cl _mmpur _const ant s=>yes.

ENDI F.

Note

After activating code logic in the BAdi, delete corresponding entries from tableV_T160EX. Any condition can be mentioned here based on fields in the item structure.

If you wish to directly copy entries from table V_T160EX into your BAdi code then copyreport program ZSY_160EX from attached text file into your SAP ERP system.

T160EX Program.txt



SRM 7.0 17.02.2009

29

This report copies data from table T160EX and provides sample code as output. Itcontains text file T160EX.txt in the location provided by user as input parameter. If thisprogram is not run in test run mode then entries from table T160EX is deleted. It isrecommended to run this program in test run mode an verify the result sample code.

There are 3 input parameters in this report program:

o Parameter 1: RFC destination of SAP SRM system. This is mandatory input. Userhas option of using F4 help here.

o Parameter 2: Path name where the text file containing the sample code needs tobe stored. This is not mandatory. If this is left blank, then the file will be stored inSAP work directory of system.

o Parameter 3: Test run. Run this report in the productive environment with Testrun unchecked. By default, test run is active.

4.1.2 Implementation of BAdi BBP_EBPXML_OUT_BADI

1. Go to transaction SE19 and enter BADI Name BBP_EBPXML_OUT_BADI.

2. Provide implementation name:



SRM 7.0 17.02.2009

30

3. Give Filter Value as RFQ:



SRM 7.0 17.02.2009

31

4. Implement method REQUESTFORQUOTE:

5. Below code should be added here:

cv_syst em_t ype = ' ESASAPXML1' .

Note

This value is picked from table BBP_FUNCTION_MAP for ESOA system type.

4.2 Frequently Asked Questions

Can we connect 2 SAP SRM systems to one SAP ERP system using SAP XI?

Yes. This is possible by defining appropriate Technical and Business Systems in SAPXI.

Do we require SAP PI for synchronous services?

When using single SAP SRM system to one SAP ERP system, Servicecommunication with SAP PI is not needed.

When using multiple SAP SRM systems for one SAP ERP system, even thesynchronous services have to be configured with SAP PI.

How to handle synchronous services when there are 2 SAP SRM systems?

When using 2 SAP SRM systems, synchronous services have to be configured viaSAP PI.

Is there a possibility for failure in synchronous service call? If so, how can we cross-check?

Yes, there is a possibility for the failure of the synchronous service call, for examplewhen there is a communication failure between SAP SRM and SAP XI or betweenSAP ERP and SAP XI..

If a communication failure occurs, an error message will appear on the front-end UI.



SRM 7.0 17.02.2009

32

As this is a synchronous call in the same Logical Unit Work, the response wis sentimmediately.

If we have defined synchronous services via SAP XI, will they be traced in queue?

No, but any error message will be displayed on UI as this is synchronous call in samelogical unit of work.

If SAP XI queue is blocked with multiple asynchronous calls, will synchronous services behelp up in queue?

No, response is immediate for synchronous services.

While creating a Purchase Order in SAP ERP and referencing a Central Contract fromSAP SRM as source of supply, there is a synchronous call to SAP SRM for the latestpricing data.

If there are large numbers of Purchase Orders being accessed or created simultaneously,will this affect performance of system?

Yes, there might be a negative effect on performance whilst the Internet PricingConfigurator is being accessed.

If the purchaser has granted the right for the bidder to "Add Items" to a Bid, will the bidderbe able to add service hierarchy items from a Service Catalog?

Yes, this is possible. From SAP SRM 7.0, it is possible to integrate SAP SRM withSRM-MDM 3.0. SRM-MDM 3.0 provides Service hierarchies which can be used bybidder to add service hierarchies as new items in RFx Response. For this, we need toprovide catalog ID in attribute CAT in supplier organization (transactionPPOMV_BBP) structure as shown below:

Within the development specification, it was stated that it should be possible to specify

with in SAP ERP, whether the value of the limit will be displayed in SUS Order. Is thispossible, if so where is this setting made.

Value of limit is always displayed. There is no setting to control, limits not beingdisplayed.

Service Catalog integration with SUS. Is this possible?

No, this is not possible.

In order to enable MM-SRV hierarchical structure within SUS business objects, do thefollowing configuration setting needs to be set in SAP SRM IMG >SAP SupplierRelationship Management >SRM Server >Cross-Application Basic Settings >ServiceProcurement >Activate Service Procurement for Transaction Types SUCF (SUSConfirmation), SUIV (SUS Invoice), SUPO (SUS PO), PCOS (SUS PO Confirmation)

No. These are meant only for RFx transaction types.



SRM 7.0 17.02.2009

Are material and services w/o hierarchy still supported in SAP Enhancement Package 4.0in Central Contracts? Can we use the direct ECC creation of contracts for materialcontracts?

Yes. You can create contracts in ECC but they won’t be called central contracts. Thiswill be specific to particular SAP ERP system.

Is it possible to maintain master data for services (hierarchies) in SAP SRM like MSS inSAP ERP?

Yes, you can upload data from MSS to MDM catalog using transaction MECCM. Forthis SRM-MDM 3.0 is mandatory. After this, we can access SRM-MDM from SAPSRM business documents and retrieve service records from SRM-MDM.

SRM-MDM 3.0 is mandatory for Business Suite 7 or SAP SRM 7.0?

SRM-MDM 3.0 is not mandatory. But if there is need to maintain master data forservice hierarchies like MSS in SAP ERP then SRM-MDM 3.0 is mandatory.

In our SAP ERP system, we have large number of entries in table T160EX. When Iupgrade to Business Suite 7, do I have to write logic manually in BAdiME_REQ_SOURCING_CUST, or can it be atomated?

Yes it can. If you wish to directly copy entries from table T160EX into your BAdi codethen copy report program ZSY_160EX from attached text file into your SAP ERPsystem.

T160EX Program.txt

This report copies data from table T160EX and provides sample code as output.Same code is stored as text file T160EX.txt in the location provided by user as inputparameter. If this program is not run in test run mode then, entries from table

T160EX are deleted

There are 3 input parameters in this report program:

o Parameter 1: RFC destination of SAP SRM system. This is mandatory input. Userhas the option of using F4 help here.

o Parameter 2: Path name where the text file containing sample code needs to bestored. This is not mandatory.

If this is left blank, the file will be stored in SAP work directory system (forexample, in folder path C:). Remember that you should have written authorizationfor the folder mentioned here.

o Parameter 3: Test run, in productive environment run this report using Test run asunchecked. By default, test run is active.

5 References: Release Information SAP Note 1223493 contains latest support packages for SAP

SRM, SAP Netweaver, SAP PI, and SAP Enterprise Portal and associatedcomponents.

Master guide, upgrade guides and installation guides fromservice.sap.com/instguides SAP Business Suite Applications SAP SRM SAPSRM 7.0

Live Expert sessions fromSAP SRM 7.0 Learning Maps

http://service.sap.com/~sapidb/011000358700000429402008E

http://service.sap.com/~sapidb/011000358700000429402008E