n

n



















































































































































n

n

n

n

n

n

n

n

n

n











n

n

n

n

n







‘ ’












¸ ¸









n



l


l


l


n







‘ ’




’ ’ ’ ’
’ ’ ’ ’


















‘ ’ ‘ ’
‘ ’

n


n


n





















n




¸ ¸
‘ ’
n

n

n














n



n




¸












¸ ¸














¸







n


n




¸
¸


































¸








n

n










¸
¸ ¸
¸















n



n

l

l

l

l

n




¸ ¸
¸









¸
¸ ’ ’
’ ’











¸ ¸ ¸

‘ ’
¸



¸ ¸


¸ ¸












n

n








¸ ¸


n

n

n

n

n

n

n










’ ’


¸ ¸















n

n








¸


¸






n

n


¸ ¸





n

n

n

n

n

n

n

n

n




n

n


n
























¸
¸


























n

n
¸
n





























¸


¸ ¸















































¸

¸ ¸
¸




¸
















‘ ’


n




n


n



¸








¸ ¸






¸










¸










¸
¸






¸




¸


¸


¸







¸


¸

¸



¸





















































¸




n

n


n

n

n

n

n

n

n

n










n

n
¸






¸

¸ ¸




















































¸




¸


¸




¸


¸





¸




¸












¸


¸




















¸ ¸











































¸ ¸
¸




¸









¸



¸ ¸
¸
¸



























’ ’
’ ’







’ ’





























¸ ¸
¸




















¸ ¸























¸ ¸

¸















¸

¸
¸

















¸




¸






























¸
































































¸










n

n














¸





































































n
¸
n










¸












¸






¸











n

n












¸



















¸














¸






n




n
¸









¸










¸





¸






















¸













n


n










¸ ¸ ¸
¸
n

n


















¸
¸



¸



¸




¸
¸ ¸
¸

n

n




















n


n

n


n
























¸
¸

¸














¸

































¸ ¸







¸






















¸ ¸


















¸







n



¸


n


¸


¸ ¸ ¸


























¸ ¸
¸ ¸ ¸

n






¸ ¸ ¸
¸ ¸ ¸







n

n










n

n

n

n

n

n
¸
n

n

n

n

n





















¸



¸

¸
¸
¸










n
¸ ¸

n
¸
¸



¸
¸









n


n

n

n

n

n


n





¸
¸ ¸










n



n













n

n

n

n

n



¸ ¸


¸ ¸ ¸






n
¸
¸ ¸
n
¸
¸ ¸
n
¸
¸ ¸ ¸
n
¸
¸ ¸ ¸
n
¸
¸ ¸
n
¸

¸
¸









n

n

n













¸
¸ ¸ ¸




















¸

n

¸ ¸
¸
n

¸ ¸
¸ ¸































¸

¸ ¸










¸ ¸ ¸






n

n
¸
n
¸
n
¸
n
¸ ¸ ¸
n
¸
n


n


















¸





n
¸ ¸
n
¸
n

n

n







¸



















n

n

¸






¸ ¸


¸










n

n

¸











¸ ¸

¸ ¸














n

n


¸






¸ ¸



















¸ ¸


¸









¸





¸
¸







¸


¸ ¸










¸
¸










¸






¸ ¸









¸
¸

¸ ¸






n
¸
¸
n
¸
¸ ¸ ¸ ¸
n
¸
¸
n
¸
¸
n
¸
¸
n
¸
¸
n
¸
¸
n
¸
¸ ¸
n
¸
¸
n
¸
¸






¸











¸




































¸














¸















n

n

n











n

n

n


¸ ¸



n
¸ ¸
¸ ¸
n
¸
¸
n
¸
¸
n

¸ ¸
n
¸
¸




¸ ¸ ¸






























































“ ”










n


n

n

n

n













































“ ”









™ ’















Document History

Caution

Before you start the implementation, make sure you have the latest version of SAP Solution Manager Content. For more information on the SAP Solution Manager content, see SAP Note 1461039. The following table provides an overview of the most important document changes.
Version Date Description

1.0

7/12/2010

Initial Version

2/84

PUBLIC

07/12/2010

Table of Contents

Chapter 1 Chapter 2 2.1 2.2 2.2.1 2.2.2 2.2.2.1 2.2.2.2 2.2.3 2.2.3.1 2.2.3.2 2.2.4 2.2.4.1 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.3.6 2.3.7 2.4 2.4.1 2.4.2 2.4.2.1 2.4.2.2 2.4.2.2.1 2.4.2.2.2 2.4.3 2.4.3.1 2.4.3.2 2.4.3.3

Important Information About This Document . . . . . . . . . . Basic Settings for Service Procurement Classic . . . . . . . . . SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . Settings for External Requirements From ERP 6.0 EHP 4 Onwards . . . . Configuring SAP ERP (Release SAP ERP 6.0 SAP Enhancement Package 4) . Making Settings for External Requirements (From ERP 6.0 EHP 4 Onwards) Making Settings for the Procurement of External Requirements with SOA (From ERP 6.0 EHP 4 Onwards) . . . . . . . . . . . . . . . . More Information About Making Settings for External Requirements . . SAP NetWeaver Process Integration . . . . . . . . . . . . . . . Importing Business Scenarios for Sourcing . . . . . . . . . . . . Checking Integration Scenario and Related Interfaces . . . . . . . . Collaborative Processing of Purchase Requisition (CPPR) . . . . . . . Harmonizing Roles . . . . . . . . . . . . . . . . . . . . . Activate Service Procurement Classic . . . . . . . . . . . . . . Activating Service Procurement . . . . . . . . . . . . . . . . More Information About Activating Service Procurement Classic . . . . Defining Sourcing for Product Categories . . . . . . . . . . . . Configuring Park and Hold . . . . . . . . . . . . . . . . . . More Information About Configuring Park and Hold . . . . . . . . Configuring Contract Handling for Invoices . . . . . . . . . . . More Information About Contract Handling for Invoices . . . . . . . Settings for Supplier Collaboration . . . . . . . . . . . . . . . SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . System Connections . . . . . . . . . . . . . . . . . . . . Testing the Connection to the System Landscape Directory . . . . . . Checking the Connection Between MM and SAP NetWeaver PI . . . . Setting Up Connectivity . . . . . . . . . . . . . . . . . . . More Information About Checking the Connection Between MM and SAP NetWeaver PI . . . . . . . . . . . . . . . . . . . . . . . SAP NetWeaver Process Integration . . . . . . . . . . . . . . . Configuring Integration Scenarios . . . . . . . . . . . . . . . Importing Business Scenarios for Service Procurement Classic . . . . . Checking Integration Scenarios and Related Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 9 9 9 9 10 10 12 12 12 14 15 16 16 16 17 18 18 19 19 20 20 20 20 21 21 21 22 22 22 24 27

07/12/2010

PUBLIC

3/84

2.4.3.4 2.4.4 2.4.4.1 2.4.4.2 2.4.4.3 2.4.4.3.1 2.4.4.4 2.4.4.5 2.4.4.5.1 2.4.4.5.2 2.4.4.5.2.1 2.4.4.5.3 2.4.4.5.3.1 2.4.4.5.4 2.4.4.5.5 2.4.4.5.6 2.4.4.6 2.4.4.6.1 2.4.4.6.2 2.4.4.7 2.4.4.7.1 2.4.4.8 2.4.4.8.1 2.4.4.9 2.4.4.9.1 2.4.4.9.2 2.4.4.9.3 2.4.5 2.4.5.1 2.4.5.2 2.4.5.2.1 2.4.5.3 2.4.5.3.1 2.4.5.3.2 2.4.5.3.2.1 2.4.5.3.2.2 2.4.5.3.3 2.4.5.4 2.4.5.5 2.4.5.6 2.4.5.7 2.4.5.7.1

More Information About SAP NetWeaver Process Integration . . . . . . Settings for Materials Management . . . . . . . . . . . . . . . . Maintaining Data in the Materials Management System . . . . . . . . Setting Up IDocs . . . . . . . . . . . . . . . . . . . . . . . Create Distribution Model . . . . . . . . . . . . . . . . . . . Creating a Distribution Model . . . . . . . . . . . . . . . . . . Configuring User Exit VSV00001 . . . . . . . . . . . . . . . . . Purchase Order Output Settings for SAP ERP 6.0 EHP3 and Earlier . . . . . Outputting Purchase Order Documents in IDOC Format . . . . . . . . Purchase Order Output . . . . . . . . . . . . . . . . . . . . Setting Up Purchase Order Output . . . . . . . . . . . . . . . . Scheduling Agreement Releases Output . . . . . . . . . . . . . . Setting Up Scheduling Agreement Release Outputs . . . . . . . . . . Setting Up Partner Profile for Connectivity . . . . . . . . . . . . . Setting Up Supplier for Purchase Order Output . . . . . . . . . . . Setting up Supplier for Outputting Scheduling Agreement Releases . . . . Purchase Order Output Settings for SAP ERP 6.0 EHP4 Onwards . . . . . Outputting Purchase Order Documents in Services . . . . . . . . . . More Information About PO Output Settings for SAP ERP 6.0 EHP4 Onwards Invoice Verification . . . . . . . . . . . . . . . . . . . . . . Setting Up Invoice Verification . . . . . . . . . . . . . . . . . Evaluated Receipt Settlement (ERS) . . . . . . . . . . . . . . . Setting up Evaluated Receipt Settlement (ERS) . . . . . . . . . . . Data Processing in Materials Management . . . . . . . . . . . . . Maintaining Data in the Materials Management System . . . . . . . . Setting up Vendor Master Data . . . . . . . . . . . . . . . . . Setting Up Purchasing Information Records . . . . . . . . . . . . Settings for Supplier Self-Services . . . . . . . . . . . . . . . . Where to Find the Documentation for Supplier Replication and Transfer . . Defining Organizational Plan for Suppliers . . . . . . . . . . . . . Creating the Organizational Plan . . . . . . . . . . . . . . . . . Supplier Self-Services User Management . . . . . . . . . . . . . . Configuring Supplier Self-Services User Management . . . . . . . . . Defining RFC Destinations for User Data Synchronization . . . . . . . Creating an RFC User . . . . . . . . . . . . . . . . . . . . . Synchronizing User Data . . . . . . . . . . . . . . . . . . . More Information About Supplier Self-Services User Management . . . . Setting Up Services for Supplier Self-Services . . . . . . . . . . . . Making Settings for Business Partners . . . . . . . . . . . . . . . Defining Customer Settings . . . . . . . . . . . . . . . . . . Number Ranges for Documents . . . . . . . . . . . . . . . . . Defining Number Ranges . . . . . . . . . . . . . . . . . . .

28 29 47 29 32 32 34 36 36 36 36 37 37 39 41 42 44 44 44 45 45 46 46 47 47 48 49 50 50 50 51 52 52 55 55 56 57 57 59 60 61 61

4/84

PUBLIC

07/12/2010

4. . Processing Invoices by Supplier . . . . . . .16 More Information About Defining Number Ranges . . .5. . Processing Evaluated Receipt Settlements (ERS) in ERP .4 3. . . . . Processing Follow-On Documents . . . . . . . . .3 3.3. . . . . . . . . . . . . . . .1 3. .7. . . Defining Filters for Scheduling Agreement Releases . . .7. . . . . . . . . . .8 3. Extending Tax Number Mapping . . . . Creating Buyer Data for Plant Maintenance Integration Creating Buyer Data . . .3. . . . . .1 3. . . . . .7 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 07/12/2010 PUBLIC 5/84 .5. . . . Purchase Requisition with Service Directories . . . . . . . .13 3. . . .14 3. . . . Settings for Supplier Self-Services . . . . . . .3 3. . . . . . . .3. . . . . . . . . . . . . Defining Dynamic Attributes . . . .10 2. . . . . . . . Supplier Self-Services: Available Queries . . .4 3. Searching for Sources of Supply Centrally . . .5. .10 3. . . . . . Configuration Content for Processing Sales Orders in SAP SUS . . . . . .5. . . . . . . 62 62 62 62 63 63 64 65 65 65 66 66 66 67 67 67 68 69 70 70 71 71 72 72 72 73 73 73 74 74 75 76 76 76 77 77 77 Service Procurement Classic . . . . . . . . . .5. . . . . . . . . . . . . .6 Chapter 3 3. . . . . . . . . .9 2. . . . . .3. . . . . . . .4. . . . . . .12 3. . . . .9. . . . . . . . . . . . . . . .2. . . . . . . . . . . . . Basic Settings for Processing Sales Orders . . .10. . . . Processing Purchase Orders in SAP ERP .1 3.1 3. . .11 2. . . . .7 3.3 3. . . . . .3. . . . Configuring Tender Fee . . . . . . . Configuring Earnest Money Deposit (EMD) . . . . . . . . . . . .4. . Processing Evaluated Receipt Settlements (ERS) in ERP . . . . . .2 3. . .7. .1 3.6 3. . . Defining Means of Transport . . . . .15 3. . Configuring Two-Envelope RFx Response . . . . . . . . . .3. . . . . . .5. . Activating Adaptable RFx Response Handling . . . . . . . . . . . . . . . . . . . Evaluating Bids . . Entering Services in SAP ERP . . Processing Invoices by Supplier . . .11 3. . . . . . . . .4. . . . . . . Configuration Content for Searching for Sources of Supply Centrally Processing Bidding Events . . . . . . . . . . . . . . .3. . . . . . Configuring Multiparty Verification Process . . . . . . . . . . . . . . . . . . . . Analyzing Service Procurement . . . . . . . . . . .5 3. . .1 2. . . . . Processing Sales Orders in Supplier Self-Services . . .6 3. .8 2. . . . . . .4. . Configuration Content for Processing Bidding Events . . . Reports in Service Procurement . . . . . .4.7. . . . . .2 3. . . .4. . .2. Verifying Logistics Invoices Online . . . . .9 3. . .2 3.13. . . . . . . . .5 3. . . . . . . . . . .1 3. Where to Find the Relevant Configuration Documentation . .1. . . . . . . . . . . . . . . . . . .1 2. . . Verifying Logistics Invoices in Background . . . . Entering Services by Supplier .

6/84 PUBLIC 07/12/2010 .

It provides you with a quick overview of the required SAP SRM configuration settings. To implement and configure SAP SRM. Strategic Sourcing Innovations SRM. Approval Process SRM. Continuous Innovations SRM. Caution This guide is a supplement to the SAP Solution Manager content and does not replace it. SAP Notes.1 Important Information About This Document 1 Important Information About This Document The configuration documentation for SAP Supplier Relationship Management (SAP SRM) is delivered with the SAP Solution Manager content.sap. Supplier Collaboration SRM. Service Procurement Innovations SRM. Analytics For more information about these business functions. which contains the complete configuration documentation including links to Customizing. see SAP Help Portal at help.01 . Self-Service Procurement SRM.sap. Business Functions SAP enhancement package 1 for SAP Supplier Relationship Management 7. you must use SAP Solution Manager.0) includes the following business functions: n n n n n n n n n n SRM. 07/12/2010 PUBLIC 7/84 . The complete configuration content and tool support is only available in SAP Solution Manager. For more information on the SAP Solution Manager content.com SAP Supplier Relationship Management Business Functions and Customizing Switches .com/instguides under Installation & Upgrade Guides SAP Business Suite Applications SAP SRM SAP SRM Server 7. see SAP Note 1461039 and the SAP SRM master guide at http://service.0 (SAP SRM 7. Catalog Innovations SRM. PI-Independent Enterprise Services SRM. This guide contains only the SAP SRM configuration documentation and references to other documentation. and SAP ERP documentation. Implementation Simplification SRM.

.This page is left blank for documents that are printed on both sides.

Activate the switch LOG_MM_P2PSE_1 07/12/2010 PUBLIC 9/84 .2 Settings for External Requirements From ERP 6.0: Synchronous peer-to peer services 1287412 Prerequisites for OCI integration in SRM 7. paging/SMS via SMTP 1268336 Business Suite 7.0 EHP 4 Onwards 2. fax.2 Basic Settings for Service Procurement Classic 2 Basic Settings for Service Procurement Classic 2. Run transaction SFW5 and expand node ‘Enterprise Business Functions’ 2.2. Procedure 1.additional information 2.0 1286936 PI configuration for SRM .1 SAP Notes The following SAP Notes apply: n n n n n 836200 Import of Process Integration Content 455140 Configuration E-mail.0 business function LOG_MM_P2PSE_1 is ON.1 Configuring SAP ERP (Release SAP ERP 6.0 SAP Enhancement Package 4) This ensures that SAP Enhancement Package 4.

There is no need to modify anything here. 4. external sourcing (e.0 EHP 4 Onwards 2. 7. You will get two methods: n Method 1: IF_EX_ME_REQ_SOURCE_CUST~ACTIVE: Here. By default. Create enhancement implementation When prompted.0 EHP 4 Onwards) 2.2 Basic Settings for Service Procurement Classic Settings for External Requirements From ERP 6. Select CL_EXM_ME_REQ_SOURCE_CUST and choose Copy the Sample Class.1 Making Settings for the Procurement of External Requirements with SOA (From ERP 6. three output parameters need to be set to true.2. coding from the sample class will be copied. Run transaction SE18 and enter BAdI Name ME_REQ_SOURCING_CUST. PR in SAP ERP system will be transferred to SAP SRM using application CPPR n Method 2: IF_EX_ME_REQ_SOURCE_CUST~CHECK_EXTERNAL_SOURCE: This method has output parameter CV_EXT_SOURCING. Choose Display. RFx can be created out of PR directly from SAP ERP system using application CPPR l When the parameter CV_EXT_SC_IND is set to true. A sample code logic for purchasing group ‘E7U’ and material groups QZA04 and QZA05 is given below: 10/84 PUBLIC 07/12/2010 .2 2. material group and purchasing group can be used as parameters to determine the Purchase Request to be transferred to SAP SRM). l When the parameter CV_AUT_SOURCING is set to true. the Purchase Request will be transferred to SAP SRM without any manual interaction in Collaborative Processing of Purchase Requisition (CPPR). 3.2.g. SAP SRM system) is active in SAP ERP system l When the parameter CV_EXT_RFX_IND is set to true.0 with enhancement package 4 or higher and the business function LOG_MM_P2PSE_1 is ON. you create a BAdi implementation. When the output parameter variables are set.0 EHP 4 Onwards) Prerequisites You use SAP ERP 6. You have setup the system connections as described in the SAP Solution Manager: Solution Manager <Project Name> Configuration SAP SRM <release> Basic Settings for SAP SRM System Connections Implementation of ME_REQ_SOURCING_CUST BADI 1. 5.g.2. 2. 6. Choose BAdI Implementation.2 Making Settings for External Requirements (From ERP 6. Hence the code logic here needs to be adopted based on parameters in the Purchase Request (e.

If you are upgrading from earlier versions of ERP. Note In order to ensure correct XML transfer between SAP ERP and SAP SRM. you must register queue MMPURS_BUS2105_* using transaction SMQR.com Components Supplier Relationship Management Message Control Activate outbound messages through qRFC Ensure that following entries are present: 07/12/2010 PUBLIC 11/84 . n Workflow event SOURCINGREQUESTED is used to trigger an XML message while transferring the Purchase Request (PR) as an external requirement to SAP SRM Sourcing. Activate event type linkages for external sourcing 1. Run transaction SWETYPV in SAP ERP system. Ensure that the following entries are present: BOR Object Type BOR Object Type BUS2105 BUS2105 RFXREQUESTED SOURCINGREQUESTED WS53800009 WS53800009 No errors No errors 3. delete corresponding material group & purchasing group entries from the table V_T160EX after activating the code logic in the BAdI.2 Basic Settings for Service Procurement Classic Settings for External Requirements From ERP 6. Note You can also use any condition based on fields in the item structure. cv_ext_sourcing = cl_mmpur_constants=>yes.0 EHP 4 Onwards IF ( is_req_item-ekgrp = ’E7U’ AND is_req_item-matkl = ’QZA04’ ) OR ( is_req_item-ekgrp = ’E7U’ AND is_req_item-matkl = ’QZA05’ ). n If you do not see XML messages getting created.2 2. verify that steps 2 ‒ 4 are properly configured. If they are not present then copy the entry for event ‘Created’ for object type ‘BUS2105’ and Receiver Type ‘WS53800009’ and change the event name. Activate outbound messages through qRFC in SAP ERP Transaction Menu Path SPRO Integration with Other mySAP. Note n Workflow event RFXREQUESTED is used to trigger XML message while creating SAP SRM RFx from Collective Processing of Purchase Requirements (CPPR). 2.

12/84 PUBLIC 07/12/2010 .1 Importing Business Scenarios for Sourcing In this section.3. Create a new connection for the desired client in the Workflow system Note n To ensure that normal PR creation in SAP ERP is not affected.2. Run transaction SM59 2. n BAdI BBP_BADI_EXTREQ_OUT or user exit BBPK001 is no longer used in this case.2 2.3 SAP NetWeaver Process Integration 2. n Background report BBP_EXTREQ_TRANSFER should not be scheduled or executed.2.2. n EPRTRANS table is not used. maintain customizing for System Messages: Transaction Menu Path SPRO Materials Management External Services Management Define Attributes of System Messages.2 More Information About Making Settings for External Requirements The following SAP Notes applies: 1270081 Run the following system transaction in SAP SRM: Switch Framework Customizing [SFW5] 2. 2.0 EHP 4 Onwards Object Type BUS2105 BUS2105 Event RFXREQUESTED SOURCINGREQUESTED Tech queued Remote Function Call queued Remote Function Call Configure RFC destination for the Workflow system 1. you transfer the business scenario Strategic Sourcing from the SAP Integration Repository. Maintain category as ‘W’ (Warning) in Message 35.2. generate it.2 Basic Settings for Service Procurement Classic Settings for External Requirements From ERP 6. Choose Logical Connections 3. and activate it.

Choose Assign. You can create them automatically here. Select a business system. 15.sap. On the main screen. Choose Finish and then choose Close. 11. Create the business system for both SAP SRM and ERP (you can bypass this step if the business system is already setup). Assign a business service to all roles. Choose Configure Connections. 8. 3. In the left pane. 13. Choose Apply. select the Objects tab. 9. Choose Integration Builder: Configuration. You can create communication channels either manually or automatically. 16. 11. 19. 17. Choose Finish. Choose Assign Services. Choose Component View. The scenario name is SE_Sourcing_Enhancements. 23. The Business Scenario Configurator opens automatically. The wizard guides you through the required steps. Choose Continue. 10. Channels must be complete in terms of URLs and authentication information. 21. Right-click to display the context menu and choose Business Systems Assign Business System . 6. Log on to the SAP Netweaver PI system. This opens the wizard. 22. In this case. Choose Name using input help SE_Sourcing_Enhancements (with namespace http://sap. 20. and then choose Close. 7. 4. see the SAP Marketplace at service.2 2. Choose Continue.com/xi/SRM/Basis/Global/IC and component SRM SERVER IC 7. The Select Component View window opens. 07/12/2010 PUBLIC 13/84 .com/instguidesNW70. n Imported the SAP NetWeaver PI content for SAP SRM into the SAP Integration Repository. choose Tools Transfer Integration Scenario from Integration Repository . 12. Procedure 1. The Assign Services to Application Component window opens. Select the related service and choose OK. See SAP Note 836200. 5. 18. 2.0 EHP 4 Onwards Prerequisites You have: n Defined the business systems for SAP Supplier Relationship Management (SAP SRM) and SAP ERP in the SAP System Landscape Directory. 14. For more information about SAP NetWeaver Process Integration (SAP NetWeaver PI). the systems are applied from the SAP System Landscape Directory (SLD). Choose Service Without Partner Business System .01). Press F4 to retrieve the available services. This opens a wizard.2 Basic Settings for Service Procurement Classic Settings for External Requirements From ERP 6.

select the Scenarios tab. 2. Expand the Standard Change List. To do this choose an existing service and then Communication Channel using context menu New. choose Apply.2 2.INVOIC01 14/84 PUBLIC 07/12/2010 . then mark all in the list Scope of Generation. 29. the Integration Builder automatically creates the communication channels. Supplier Self-Services SupplierPortalTradingPartner_CreateOrChange_In PurchaseOrderRequest_In PurchaseOrderChangeRequest_In PurchaseOrderConfirmation_Out DespatchedDeliveryNotication_Out InvoiceRequest_Out Direction Asynchronous call (provider) Asynchronous call (provider) Asynchronous call (provider) Asynchronous call (consumer) Asynchronous call (consumer) Asynchronous call (consumer) Materials Management Z_CREMAS_SUSMM. select the Change List tab. Choose Start to generate a log. For the Plan-Driven Procurement business scenario. 26. Select the connections from the Service Assignment tab. Choose OK and then choose Apply. You must assign a communication channel for each connection. 28. In the left pane. your scenario has been added. In the Close Integration Scenario screen. Choose Simulation.2 Checking Integration Scenario and Related Interfaces In this section. 34. 27. 33. Select a communication channel. In the left pane. This channel must be of type XI.CREMAS03 ORDERS. Press F4 in the Communication Channel field. Right click on the scenario name SE_Sourcing_Enhancements and choose Activate. Check the log for errors and save it if required. 35. Note n If the systems are applied from the SAP Landscape Directory. then Generate. see SAP Note 1268336.2. which you can check in the Integration Builder: For more information. 30.DELVRY01 INVOIC. n If the systems are not applied from the SAP Landscape Directory.ORDERS02 ORDRSP. 32.0 EHP 4 Onwards 24. 31.ORDERS02 ORDCHG. the Plan_Driven_Procurement_SupplierEnablement integration scenario provides the following interfaces. you create communication channels manually. Choose Generate to open the Create Configuration Objects window.2 Basic Settings for Service Procurement Classic Settings for External Requirements From ERP 6. you check the integration scenario to which the Plan‒Driven Procurement business scenario is assigned and the interfaces that are used for communication between Supplier Self-Services and Materials Management. 25.3.ORDERS02 DESADV.

2 2.0 EHP3 release notes. see SAP ERP 6. 2.4 Collaborative Processing of Purchase Requisition (CPPR) In SAP Business Suite 7.0 and SAP ERP 6. Collective Processing of Purchase Requisitions (CPPR) is a WebDynpro-based application that covers the functions of the SAP ERP transaction "Assign and Process Purchase Requisitions" (ME57).DELVRY03 GSVERF. 3. For more information. Start the SAP Integration Builder.2.0 EHP3 Business Function "Material Management Purchasing" (LOG_MM_CI_2). Under the Scenario tab. CPPR was introduced in SAP ERP 6. You must set up harmonized roles between SAP ERP and SAP SRM to use CPPR functionality.GSVERF01 DELINS. see SAP Solution Manager under <project name> Configuration SAP SRM <release>.DELFOR02 1.Asynchronous call (provider) tion_In InvoiceRequest_In PurchaseOrderRequest_In Procedure Asynchronous call (provider) Asynchronous call (provider) STPPOD.0. the CPPR function is extended to create RFxs in SAP SRM 7.0.0 with reference to purchase requisitions and for manual demand transfer through user interaction.0 with enhancement package 4. expand the scenario to display detailed information.0 EHP 4 and Onwards Direct RFx Creation from SAP ERP Using CPPR 07/12/2010 PUBLIC 15/84 . Choose Integration Builder: Configuration. 2. EHP1 Basic Settings for Strategic Sourcing Settings for the Sourcing Application Integration with ERP 6.0 EHP 4 Onwards ServiceAcknowledgementInforma. Sourcing is enhanced through the increased integration of SAP SRM 7. In SAP Business Suite 7. See SAP Note 1263876 for more details. This tightly integrated centralized sourcing process in SAP BS 7 provides the ability to simplify centralized sourcing by aggregating demands from multiple back-end SAP ERP systems into the central SAP SRM system Centralized sourcing in SAP SRM takes place in following ways: n Automatic demand transfer from SAP ERP to SAP SRM n Manual demand transfer through user interaction using CPPR.2 Basic Settings for Service Procurement Classic Settings for External Requirements From ERP 6. For more information on CPPR and using CPPR without SAP SRM 7.

More particularly. For more information on harmonized roles for SAP ERP and SAP SRM.3 Basic Settings for Service Procurement Classic Activate Service Procurement Classic 2.2 2. you define the settings pertaining to the use of service hierarchies. 2.0. Prerequisites You have ensured that all required Business Packages as mentioned in the SAP Note 1232945 are installed. These roles can be found in the folder structure: Portal Content Content Provided by SAP specialist SRM 70 Suite Roles n The Business Package for SAP SRM 7.1 Harmonizing Roles In this section you can assign SAP ERP and SAP Supplier Relationship Management (SAP SRM) harmonized roles to the SAP NetWeaver Portal user to allow the portal user to execute Collaborative Processing of Purchase Requisition (CPPR) tasks.0 User Configuration Assigning Business Package Roles to Portal Users 2.2. a set of new SAP NetWeaver Portal roles is created. Procedure If the data source in the SAP NetWeaver Portal is maintained in LDAP and users are copied from SAP SRM backend. Assign these harmonized roles to SAP NetWeaver Portal users as required.0 offers four harmonized roles: l Operational Purchaser (SAP ERP) l Strategic Purchaser (SAP ERP) l Operational Purchaser (SAP ERP/SAP SRM) l Strategic Purchaser (SAP ERP/SAP SRM) Roles Operational Purchaser (SAP ERP/SAP SRM) & Strategic Purchaser (SAP ERP/SAP SRM) n will have data from both SAP ERP & SAP SRM system applications.4.3.0 Basic Settings for SAP SRM Business Package for SAP SRM 7. see SAP Solution Manager under SAP SRM 7. 16/84 PUBLIC 07/12/2010 . then proceed with the following steps: 1. Assign Harmonized Roles to Users n After the installation of Business Package for SAP SRM 7. If the data source in the SAP NetWeaver Portal is ABAP.1 Activating Service Procurement You use this procedure to define the settings for SAP Supplier Relationship Management (SAP SRM) and Materials Management (MM) in SAP ERP that are required to run the Service Procurement Classic scenario.3 Activate Service Procurement Classic 2. then this step can be skipped.

The system performs a check on open quantities and informatory lines.2 2. that is. Settings in SAP SRM 1. The template HIER_SE should be assigned to RFx transaction types used to process external service requests transferred from Materials Management in SAP ERP. The template HIER_SRM is used in RFx transaction types to process local RFxs. Go to Customizing for SAP Supplier Relationship Management under SRM Server Sourcing Define Sourcing for Product Categories to ensure that the sourcing strategy for product categories used in service procurement is maintained as Sourcing always carried out. you can save purchase requisitions (SAP ERP). If you create new RFx transaction types. and that you select Integrated UI for the SAP SRM and SAP ERP systems. Go to Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Service Procurement Activate Service Procurement to assign a hierarchy template to the RFx transaction type. Select the Show Indent checkbox to show indentation in hierarchies in the SAP SRM system. 6. You assign the relevant Rule ID to an RFx transaction type in section Rule Assignment for Item Levels.2 More Information About Activating Service Procurement Classic Perform the following activities in Customizing for SAP Supplier Relationship Management under: 07/12/2010 PUBLIC 17/84 . 2. Go to Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Configurable Item Numbering Define Configurable Item Numbering Scheme to assign a configurable item number to the relevant RFx transaction types. If you leave the attribute unchanged. POWL Navigation is filled with the corresponding system aliases for the SAP ERP and SAP SRM systems in the SAP NetWeaver Portal landscape. RFxs created without reference to SAP ERP requests.3 Basic Settings for Service Procurement Classic Activate Service Procurement Classic Settings in SAP ERP Go to Customizing for SAP ERP under Materials Management External Services Management Define Attributes of System Messages and change the attribute of the messages SE035 and SE36 from ’Warning’ to ’Error’. Go to Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings Define System Landscape to ensure that the field System Alias f. Implement Business Add-In BBP_DETERMINE_LOGSYS if you plan to connect multiple back-end systems to SAP SRM and if you want to create back-end contracts as follow-on documents from sourcing. You do this to restrict outgoing purchase requisitions. 4. 2. By default. SAP delivers two hierarchy templates. You must implement this Business Add-In to determine the back-end system in which contracts must be created. 3. number ranges for six levels (D1 to D6) are given as ‘Rule ID’ in section Rules of the dialog structure.3. 5. follow the instructions in SAP Note 1267549 to enable hierarchies and refer to SAP Note 1270412 to update metadata entries.

4 Configuring Park and Hold You use this procedure to configure the park and hold function for the Service Procurement Classic scenario in the SAP ERP and SAP Supplier Relationship Management (SAP SRM) systems. Specify that requirements with the appropriate product categories are transferred to the Sourcing application: n Always n Only when a source of supply has not yet been assigned n Never n Auto RFx creation with no source of supply assigned n Auto grouping and sourcing with no source of supply assigned n Auto grouping but no sourcing for item with no source of supply assigned n Auto grouping and creation of RFx with no source of supply assigned 2. 2.3. In Customizing for SAP ERP. Procedure 1. 2. perform the activity under SRM Server Cross-Application Basic Settings Service Procurement Define Status for Purchase Orders in Back-End 18/84 PUBLIC 07/12/2010 .3 Defining Sourcing for Product Categories You use this procedure to specify either that the product category of the requirement is transferred to the Sourcing application or that the system always creates an RFx. Procedure 1.2 2. In the standard. To use this procedure.3 Basic Settings for Service Procurement Classic Activate Service Procurement Classic n n SRM Server SRM Server Innovations Activate Business Functions Cross-Application Basic Settings Service Procurement Activate Service Procurement 2. no requirements are transferred. In Customizing for SAP Supplier Relationship Management. go to SRM Server Sourcing Define Sourcing for Product Categories . You have activated the Materials Management — Enhancements in Procurement (LOG_MM_CI_3) business function in the SAP ERP system. you must activate the business function SRM. In Customizing for SAP Supplier Relationship Management. perform the activity under Materials Management Purchasing Environment Data Activate ’Park and Hold’ in Purchasing Documents to activate the park and hold function. Service Procurement Innovations (SRM_SERVICE_PROC_1).3.

Run transaction Display Attributes (PPOSA_BBP) to map SAP ERP product groups to SAP SRM purchasing groups. You have activated the Procurement .3. Note You do not have to change harmonized roles. or Save based on the purchasing group.5 More Information About Configuring Park and Hold Perform the following activities in Customizing for SAP Supplier Relationship Management under: n n SRM Server SRM Server Innovations Activate Business Functions Cross-Application Basic Settings Service Procurement Activate Service Procurement 2. In Customizing for SAP ERP. unless you use the SAP ERP buyer for listing purchase orders and purchase requisitions using POWL. In Customizing for SAP ERP.3 Basic Settings for Service Procurement Classic Activate Service Procurement Classic System to specify whether purchasing documents must be created with the status Park.3.6 Configuring Contract Handling for Invoices You use this procedure to configure contract handling for invoices in the SAP ERP system. Hold. 3. Procedure 1.SRM Integration 2 (LOG_MM_P2PSE_2) business function in the SAP ERP system. 2. perform the activity under Materials Management Logistics Invoice Verification Incoming Invoice Activate Direct Posting to Contracts to allow direct references to contracts when creating invoices and parking documents. hold. perform the activity under Materials Management Logistics Invoice Verification Invoice Block Set Tolerance Limits to set the tolerance key for contracts (PC: Price variance for contract). 2. Note that you must have activated the related business function. Result Purchasing documents are created with the park. 07/12/2010 PUBLIC 19/84 .2 2. or save status in the back-end system based on the above Customizing in SAP SRM.

distribution models and so on. in the system in which the SAP application component is installed n Completing the configuration settings and performing other activities required for the interactions in a SAP system landscape. servers. 4. 2.0.0.4 Settings for Supplier Collaboration 2. Procedure Perform the steps in these guidelines in the sequence in which they appear. This involves. and 5 Note 656633: Search help requires dialog users Note 614940: DataSources for the Enterprise Buyer Note 150315: BW-Authorizations for Remote-User in BW and OLTP Note 751772: New roles for purchase analysis as of BI Cont 3. Problems with Back-end tax indicator and jurisdiction code Note 673372: Short dumps UNCAUGHT_EXCEPTION in SRM 3.2 2.2 System Connections This section contains information about connecting the systems in a SAP system landscape.4.2 Note 119092: EDI: Delivery costs during invoice receipt MM Note 890812: Inbound EDI message ORDRSP: Cancelling a purchase order Note 995388: MM-SUS: Sending Texts from SUS (ORDRSP) to MM 2. for example: n Defining logical systems and assigning clients in the Online Transaction Processing System (OLTP) n Determining the systems.4. 20/84 PUBLIC 07/12/2010 .3. Run the following transaction in the SAP SRM system: Display Attributes (PPOSA_BBP).4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 2.5. clients.1 SAP Notes The following SAP Notes are relevant: n n n n n n n n n Note 741822: TAX.7 More Information About Contract Handling for Invoices The following SAP Notes are relevant: n Note 1267549: Creation of new transaction types for RFx and Quote n Note 1270412: Item Level fields become invisible Perform the following activity in Customzing for SAP Supplier Relationship Management: SRM Server Cross-Application Basic Settings Service Procurement Define Status for Purchase Orders in Back-End System .

create an RFC destination to connect the SAP ERP Materials Management (MM) system to the integration server. 2. perform the following steps for each of the MM systems.1 Testing the Connection to the System Landscape Directory To test the connection to the System Landscape Directory run transaction SLDCHECK.4.4.2.4. The system displays a log that lists the current configuration data.2 2.1 Setting Up Connectivity In this section you define the logical systems for the scenario. enter the following data: Log. Defining the Logical Systems Transaction Code Customizing SPRO SAP Implementation Guide SAP Web Application Server Application Server IDoc Interface / Application Link Enabling (ALE) Basic Settings Logical System Define Logical System For the MM and the SAP SUS systems. errors. System <MM_BS>CLNT<client> For example.2 Checking the Connection Between MM and SAP NetWeaver PI 2.2.2. and notes for checking. JSNCLNT003 Name (examples) QX8 client 100 JSN client 003 07/12/2010 PUBLIC 21/84 . QX8CLNT100 <SUS_BS>CLNT<client> For example. Caution If you are using the Plan-Driven Procurement with Supplier Integration business scenario with more than one MM system. and you create a transactional port for the RFC destination. the function test results.2.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 2.

3 SAP NetWeaver Process Integration 2.2 More Information About Checking the Connection Between MM and SAP NetWeaver PI Run the following system transactions in SAP SRM: n RFC Destinations (Display/Maintain) [SM59] n Port Definition [WE21] n Maintaining Logical Systems [BD54] 2. Creating the Transactional Port Transaction Code Menu Path WE21 Tools ALE ALE Administration Port Maintenance Runtime Settings In system <MM_BS> create a Transactional Port for RFC destination <INTEGRATION-SERVER_BS>CLNT<client>. The determined objects are created or existing configuration objects are checked to ensure that they can be used before including them in a configuration scenario. Together with additional assignments. 2. the information saved in the integration scenario is used to calculate the relevant logical routing objects and the collaboration agreement. 22/84 PUBLIC 07/12/2010 .2 2.1 Configuring Integration Scenarios You can use an integration scenario from the Integration Repository as a template for configuration.2. create <INTEGRATION-SERVER_BS>CLNT<client> RFC destination with 3Connection type (SAP ERP connection).2. Thus.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration Defining the RFC Destination Transaction Code Menu Path SM59 Tools ALE ALE Administration Maintain RFC Destination Runtime Settings In system <MM_BS>.4. the configuration of more extensive and more collaborative processes is made as automated as possible. The whole process is logged so that you have a good overview and can analyze and understand the configuration.4.4.3.

Each time that you call the integration scenario configurator. choose the menu option Tools Transfer Integration Scenario from Integration Repository Note Use this option when you have not yet created a configuration scenario for your configuration data. In this case.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration Prerequisites You must create a configuration scenario in the Integration Directory by grouping together all configuration objects that result from the configuration or that are reused. When you configure an integration scenario you perform the following activities. Select the Integration Scenario and the Component View In this step you select the integration scenario and the component view (if multiple component views are defined for the integration scenario). Only once you have done so can you continue with further activities. Activity Run the integration scenario configurator Description You can call the integration scenario configurator as follows: In the object editor for the configuration scenario. This enables you to divide up configuration work into multiple steps and means that the configuration is not affected by any changes to the integration scenario in the Integration Repository.2 2. the component view is displayed in an interactive graphic. the integration scenario is also loaded from the Integration Repository. However. Once you have executed this activity. In this step you assign services to the application components of integration scenario. you map the participants in an integration scenario displayed in the component view to actual senders and receivers of messages in your system landscape. choose the menu option Scenario Integration Scenario Configurator In the main menu bar of the Integration Builder (Integration Directory). In this way. This means that the relevant data is always available when you reload the configuration scenario. Integration All the configuration settings that you make with the integration scenario configurator are saved in the Integration Directory together with the configuration scenario. you must first select an integration scenario from the Integration Repository and create the configuration scenario in the Integration Directory. Assign the Services 07/12/2010 PUBLIC 23/84 . this is always the version in which the object was originally included and configured.

2 2. In this step. The generation log enables you to recognize which configuration objects require manual work.3. A generation log provides you with an overview of all changes made in the Integration Directory as a result of the configuration of the integration scenario. they will be reused and enhanced. Shows or hides the configuration steps in a bar next to the graphical editor. It informs you which configuration objects have been created or reused. and configure communication. You can start the dialogs belonging to the individual configuration steps from this bar. you specify communication channels that are relevant for the sender/receiver relations. These are then used to calculate the relevant collaboration agreements. You can simulate generation for test purposes. you transfer the Service Procurement Classic business scenario from the SAP Integration Repository. Use Generation Check Configurability Display Configuration Description Checks whether you have made all the assignments required to generate the configuration objects.2 Importing Business Scenarios for Service Procurement Classic In this section.4. Configuration Scenario Objects Scenario Objects for Connection View Display Configuration Steps View Zoom 2. Displays all objects that were generated or created manually for a connection of the component view and which match the current configuration of the connection. 24/84 PUBLIC 07/12/2010 . If they do already exist. Furthermore. You call them from the menu bar in the integration scenario configurator. you activate sender/receiver relations for the individual connections in the integration scenario.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration Configure the Connections In this step. the calculated configuration objects will be created (if they do not yet exist). generate it. Increases or decreases the size of the graphical display of the component view. if required. Generate the Configuration Objects Use the generation log and perform manual post processing Additional functions When you configure an integration scenario you can use the following additional functions.

Choose Business Systems Assign Business System .com/instguidesNW70. Choose Apply. 9. See SAP Note 836200. 12. Select a business system. For more information about SAP NetWeaver Process Integration (SAP NetWeaver PI).4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration This business scenario is also applicable to Plan-Driven Procurement with Supplier Integration using ECC 6. the systems are applied from the SAP System Landscape Directory (SLD). 8. You can create communication channels either manually or automatically.2 2. 14. 11. The Integration Scenario Configurator opens automatically.0 with enhancement package 4 since the purchase order document is transferred between the SAP ERP and SUS systems. Press F4 to retrieve the available services. In the left pane. Choose Integration Builder: Configuration. On the main screen. 2. Choose Continue. In this case. 07/12/2010 PUBLIC 25/84 . Choose Finish. This opens a wizard. Choose Finish and then choose Close. 1. The wizard guides you through the required steps. Channels must be complete in terms of URLs and authentication information. You can create them automatically here. Select Component View. 10.com/xi/SRM/Basis/Global/IC and component SRM SERVER IC 7. 5. Log on to the SAP NetWeaver PI system. The Select Component View window opens.01). Choose Assign Services. choose Tools Transfer Integration Scenario from Integration Repository . 15. 13. 4. The Assign Services to Application Component window opens. 3. This opens the wizard. and then choose Close. 16. Choose Assign. The scenario name is SE_Services_Procurement. select the Objects tab. 7. n The SAP NetWeaver PI content for SAP SRM is imported into the SAP Integration Repository. You can only performed the steps below if you have activated the SAP ERP business function ‘LOG_MM_P2PSE_1’. see the SAP Marketplace at service. 6. n See SAP note 1269540 to get more information about the Business scenarios in SAP SRM which can be used with various versions of SAP SRM and in combination with various versions of SAP ERP. Choose Name using input help SE_Services_Procurement (with namespace http://sap.sap. Prerequisites You must have: n The business system for Materials Management (MM) and the business system for Supplier Self-Services (SUS) is defined in the SAP System Landscape Directory. Select Continue.

2 2. Press F4 in the Communication Channel field. 6. Choose OK and then choose Apply. Business System Business System for SAP 26/84 PUBLIC 07/12/2010 . Choose Generate to open the Create Configuration Objects window. 23. Double-click on GeneratedReceiverChannel_XI. Select a communication channel. then mark all in the list Scope of Generation.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 17. Select Activate. Select Change. Authentication data Authentication type Select Use Logon Data for SAP System. In the Close Integration Scenario screen. Choose the Objects tab and go to Service Without Party SUS Communication Channel 2. 18. Choose Start to generate a log. 27. Configuring Communication Channels for MM 1. Check the log for errors and save it if required. 2. 3. 19. Double-click on GeneratedReceiverChannel_XI. In the left pane. Note a) If the systems are applied from the SAP Landscape Directory. Assign a business service to all roles. 20. Select the related service and choose OK. 3. 21. In the left pane. b) If the systems are not applied from the SAP Landscape Directory. Select Generation. 25. you create communication channels manually. This channel must be of type XI. choose Apply. 28. To do so. To do this choose an existing service and then Communication Channel using context menu New. 4. 22. Choose the Objects tab and go to Service Without Party Business System <Business System for SAP SUS> Communication Channel . the default path reads as follows: /sap/xi/engine/?type=receiver 5. then select Simulation. start transaction SICF in the SUS system and go to Goto Port Information . select the Change Lists tab. 26. You must assign a communication channel for each connection. your scenario has been added. Select Change. 24. 29. Configuring Communication Channels for SUS 1. right-click on the newly added scenario name and select Activate. the Integration Builder automatically creates the communication channels. Choose Configure Connections. Check all settings and enter data for Target Host and Service Number. Select the connections from the Service Assignment tab. select the Scenarios tab.

11. and Receiver Agreements) and Additional Configuration Objects. 6.2 2. Choose the Objects tab and go to Service Without Party Business System Business System for SAP SUS Communication Channel 8.4. senders. Enter the RFC destination and port that you defined in section Configuring the IDoc Adapter [external document] in this guide. You have generated a log for Generation of Business Scenario Configuration with the Integration Scenario Configurator.3 Checking Integration Scenarios and Related Interfaces You use this procedure to check the integration scenario to which the Service Procurement Classic business scenario is assigned and the interfaces that are used for communication between Supplier Self-Services and Materials Management. Check all settings.CREMAS03 07/12/2010 PUBLIC 27/84 . Authentication data Authentication type Select Use Logon Data for SAP System. Interface Determinations. the default path reads as follows: /sap/xi/engine/?type=receiver 5.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 4. the SE_Services_Procurement integration scenario provides the following interfaces. 10. 9. Select Activate. Sender Agreements. This includes information about Generation Settings. To do so. and communication channels. Check all settings and enter data for Target Host and Service Number. Double-click on GeneratedReceiverChannel_XI.01 for some messages types. which you can check in the Integration Builder: Supplier Self-Services SupplierPortalTradingPartner_CreateOrChange_In Direction Asynchronous call (provider) Materials Management Z_CREMAS_SUSMM. Generation Statistic.3. start transaction SICF in the SAP SUS system and go to Goto Port Information . Select Change. 7. Note You need to define two communication channels for the MM system because the traditional IDOC data posting is still valid in SAP SRM 7. Result The business scenario Service Procurement Classic has been configured for receivers. Connection from the Business Scenario for each interface (with Receiver Determinations. Selected Component View. 2. Select Activate. For the Service Procurement Classic business scenario.

2 2.INVOIC01 ORDRSP. expand the scenario to display detailed information.DELVRY01 ServiceAcknowledgementERPCreateRequest_In INVOIC. 2.ORDERS02 DESADV. 2.DELFOR02 INVOIC. 3.INVOIC01 ServiceAcknowledgementERPCre.3.4. Choose Integration Builder: Configuration.Asynchronous call (consumer) ateRequest_Out InvoiceRequest_Out Procedure Asynchronous call (consumer) 1.Administration (SXMB_ADM) Start Integration Builder (SXMB_IFR) 28/84 PUBLIC 07/12/2010 . Under the Scenario tab.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration ServiceAcknowledgementInforma.DELVRY03 PurchaseOrderERPRequest_Out_V1 ServiceAcknowledgementERPConrmation_Out ServiceAcknowledgementERPNotication_Out DELINS.4 More Information About SAP NetWeaver Process Integration The following SAP Notes apply: n 1286936 n 884695 Run the following system transactions: n n n n n n n n User Maintenance (SU01) Role Maintenance (PFCG) RFC Destinations (Display/Maintain) (SM59) HTTP Service Hierarchy Maintenance (SICF) SLD Administration (RZ70) SLD API Customizing (SLDAPICUST) Integration Engine . Start the SAP Integration Builder.Asynchronous call (provider) tion_In PurchaseOrderERPRequest_In_V1 Asynchronous call (provider) ServiceAcknowledgementERPConrmation_In ServiceAcknowledgementERPNotication_In PurchaseOrderRequest_In InvoiceRequest_In PurchaseOrderConfirmation_Out DespatchedDeliveryNotication_Out Asynchronous call (provider) Asynchronous call (provider) Asynchronous call (provider) Asynchronous call (provider) Asynchronous call (consumer) Asynchronous call (consumer) STPPOD.

define change-relevant fields.2 2. and define an object class before assigning the message type to this class. Creating a Reduced Message Type Transaction Code Menu Path BD53 SAP Customizing Implementation Guide SAP NetWeaver Application Server IDoc Interface /Application Link Enabling (ALE) Modeling and Implementing Business Processes Master Data Distribution Scope of Data for Distribution Message Reduction Create Reduced Message Type 1.4 Settings for Materials Management 2.4.4.1 Maintaining Data in the Materials Management System In this section you perform the necessary steps to configure supplier master data and set up purchasing info records.4. See n Setting up Supplier Master Data [external document] n Setting up Purchasing Info Records [external document] 2. create the reduced message type Z_CREMAS_SUSMM with the following segments: E1LFA1M (*) Segment for general vendor data | |__ E1LFA1A (+) Segment for standard vendor data . Based on reference message type CREMAS.4.2 Setting Up IDocs In this section you create a reduced message type within the customer namespace. Ensure segment E1LFA1M contains the following fields: Field MSGFN LIFNR KTOKK LAND1 NAME1 Text (*) Function (*) Account number of vendor or creditor (*) Vendor account group (*) Country of company (*) Employee’s last name 07/12/2010 PUBLIC 29/84 .4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 2.enhancement |__ E1LFM1M (+) Segment for purchasing organization data vendor SMD 2.4.

30/84 PUBLIC 07/12/2010 . County) (*) Character field length = 10 (*) Language key (+) Tax number 1 (+) Tax number 2 (+) House number and street (+) First telephone number (+) Fax number (+) Address (+) Jurisdiction for tax calculation . Choose Activate change pointers to enable subsequent synchronization of the supplier data. Box (*) Postal Code (*) Postal Code (+) Region (State. Province.O.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration NAME2 ORT01 ORT02 PFACH PSTL2 PSTLZ REGIO SORTL SPRAS STCD1 STCD2 STRAS TELF1 TELFX ADRNR TXJCD (+) Employee’s last name (*) City (+) District (+) P. Ensure segment E1LFA1A contains the following fields: Field LFURL Text (+) Uniform resource locator 4. Ensure segment E1LFM1M contains the following fields: Field MSGFN LIFNR EKORG WAERS Text (*) Function (*) Vendor’s account number (*) Purchasing organization (*) Purchase order currency 5.tax jurisdiction code 3. Caution After creating the reduced message type. ensure the segments E1LFA1M and E1LFA1A contain the fields marked with (+).2 2.

go to Cross-Application Components Classification System Maintain Object Types and Class Types 2. Choose vendor LFA1. go to Cross-Application Components Maintain Object Types and Class Types . In the Implementation Guide. 2. 5. Save your entries. Enter the Class Type description Lists for vendor distribution. Double-click Class Types. 2. 4. 7. class type under the Functions section. In the Implementation Guide. Delete the following entry: Object KRED Table LFA1 Field ADRNR Defining an Object Class for Master Data Distribution Prerequisites If the class type ALV is available. Select Multiple classification and Distr. Double-click Class Types. Choose vendor LFA1. Choose work area (message type) Z_CREMAS_SUSMM.2 2. you have assigned the supplier LFA1 to class type ALV as follows: 1. 3. 6. 6.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration Defining Change-Relevant Fields Transaction Code Menu Path BD52 Tools ALE ALE Development IDocs Engineering Change Management Define Change-Relevant Fields 1. 3. Select Multiple classification and Distr. you have done the following assignment: 1. Double-click on the ALV class type 5. Classification System Classes If the class type ALV is not available. Copy Class Type 010 with a new name (ALV). 4.class type. Save your entries Procedure Classes Transaction Code Menu Path CL01 SAP Customizing Implementation Guide SAP NetWeaver Application Server IDOC Interface / Application Link Enabling (ALE) Modeling and Implementing Business Processes Master Data Distribution Distribution Using Object Classes Maintain Classes 07/12/2010 PUBLIC 31/84 .

Choose Save. for example. Enter a record with the following data: Message Type Z_CREMAS_SUSMM Class Z_CRED_SUSMM_<SUS_BS> PoP 2 (Push) 2.3 Create Distribution Model 2. 5. You can define the partner profiles for all outbound and inbound messages based on the information in the distribution model.1 Creating a Distribution Model The applications that communicate with each other in your distributed systems are specified in the distribution model.4. 32/84 PUBLIC 07/12/2010 . see Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings ALE Settings Distribution (ALE) Modeling and Implementing Business Processes Maintain Distribution Model and Distribute Views .4.3. see Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings ALE Settings Distribution (ALE) Modeling and Implementing Business Processes Partner Profiles Generate Partner Profiles . Create Class. Choose Logical system <SUS_BS>CLNT<client> 2. for example. 3.2 2.4. On the Basic Data tab page enter a description. 4. 2. Supplier Replication. Z_CRED_SUSMM_<SUS_BS> 3. For more information. The distribution model consists of separate model views where you can define system-wide message flows.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 1. For more information. Choose New Entries. Assigning Message Type to Distribution Object Class Transaction Code Menu Path BD68 Self-Services Supplier SAP Customizing Implementation Guide SAP NetWeaver Application Server IDOC Interface / Application Link Enabling (ALE) Modeling and Implementing Business Processes Master Data Distribution Distribution Using Object Classes Assign Classes to Receiving Logical System 1. Choose Class type ALV.4. Ensure that the Status is set to Released.

doc. select which message types to add to your model view. 07/12/2010 PUBLIC 33/84 . and to add message types and BAPIs to your model views.0 WMMBXY ACC_GOODS_MOVEMENT ACLPAY BBPCO BBPIV Back-End System 4. Select your SAP SRM system as the Sender and the name of the connected back-end system as the Receiver.doc. Select your SAP Supplier Relationship Management (SAP SRM) system as the Sender and the name of the connected back-end system as the Receiver.5 and Higher MBGMCR ACC_GOODS_MOVEMENT ACLPAY BBPCO BBPIV Goods receipt (mat. Choose Add message type and select the model view for which you wish to define message flow between SRM Server and the back-end system. To create model views. Generating Partner Profiles After you have created and distributed the model views. The following table shows which message types to select depending on which back-end system is connected to your SAP SRM system: Message Type Back-End System 3. 5. 3. Save your entries.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration Creating Model Views You must specify the cross-system message flow between SRM Server and all the connected back-end systems.) WMMBXY Goods receipt (acc. In the Message Type field.1 Back-End System 4. Choose Add BAPI to add Business Application Programming Interfaces (BAPIs) to your model view. you must generate partner profiles for outbound and inbound messages in SRM Server. Click once on the model view you created. The following table shows which BAPIs to add: Object Name/Interface IncomingInvoiceEC (EC Incoming Invoice) BBP_PCSTAT (Procurement Card Statement) Method Create Create 6. 2. Enter change mode and create a model view in Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings ALE Settings Distribution (ALE) Modeling and Implementing Business Processes Maintain Distribution Model and Distribute Views . proceed as follows: 1.) Procurement Card Invoice (CO) Invoice ACPJMM ACLPAY BBPCO BBPIV 4.2 2.

Enter the name of the model view you created in the SAP SRM system in the Model View field. 4.2 2. Select the inbound parameter Trigger by background program. 2. Choose Execute (or F8). 6. At Outbound Parameters.4. Ensure that the partner profile was generated in the back-end system in Customizing for SAP NetWeaver under Application Server IDoc Interface/Application Link Enabling (ALE) Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views . Choose Edit Model View Distribute . Select the output mode Collect IDocs and transfer. Generate a partner profile in Customizing for SAP NetWeaver under Application Server IDoc Interface/Application Link Enabling (ALE) Modelling and Implementing Business Processes Partner Profiles Generate Partner Profiles . enter 3 in the Version field. Select the relevant back-end system and choose Continue. Select the model view for which you want to generate partner profiles. Alternately. Enter the name of the back-end system in the Partner System field. 2. Enter the name of the SAP SRM system in the Partner System field. 2. Enter the name of your model view in the Model View field.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 1. proceed as follows: 1. you add coding to a user exit in the supplier master data and you assign the user exit to a project. you can use transaction BD64. Generate partner profiles in Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings ALE Settings Distribution (ALE) Modeling and Implementing Business Processes Partner Profiles Generate Partner Profiles or see SAP Solution Manager for SAP SRM under Basic Settings for SAP SRM System Connections Logical Systems and RFC Connections in the SRM Landscape Create Distribution Model . 3. If no partner profile was generated in the back-end system.4. 5. 3. Choose Execute (or F8). Note You can also generate partner profiles in the back-end system in Customizing for SAP Supplier Relationship Management under SRM Server Technical Basic Settings ALE Settings Distribution (ALE) Modeling and Implementing Business Processes Maintain Distribution Model and Distribute Views . Alternately. 7.4 Configuring User Exit VSV00001 To enable the IDoc transfer of supplier e-mail addresses to the supplier self-services system. or you can use transaction BD64. you can use the link in SAP Solution Manager for SAP SRM under Basic Settings for SAP SRM System Connections Logical Systems and RFC Connections in the SRM Landscape Create Distribution Model . 4. 34/84 PUBLIC 07/12/2010 . or use transaction BD82.

2 2. read table idoc_data into ls_idoc_data with key segnam = ’E1LFA1M’. clear ls_idoc_data. read table idoc_data into ls_idoc_data with key segnam = segment_name. if segment_name = ’E1LFA1A’. ls_idoc_data type edidd. Defining the Identification Type Transaction code Menu Path CMOD Tools ABAP Workbench Project Management Utilities Enhancements 1. see SAP Note 756472. 4. Add the following coding to user exit Customer and Vendor Distribution Receipt/Issue: data: ls_data_a type E1LFA1A. Activate the enhancement assignment. ZPSMM. modify idoc_data from ls_idoc_data index lv_index. for example. ls_data_a = ls_idoc_data-sdata. lv_index type sy-tabix. Choose Enhancement Assignments and assign enhancement VSV00001 and component EXIT_SAPLKD01_001 to the project.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration Caution You must also program the user exits EXIT_SAPLEINM_001 and EXIT_SAPLEINM_005 to enable purchase order response. For more information. Prerequisites You have created a customer project. Choose Project ZPSMM. endif. ls_data_m type E1LFA1M. 2. Note Ensure that the display of your project shows a green light for user exit EXIT_SAPLKD01_001 07/12/2010 PUBLIC 35/84 . lv_index = sy-tabix. ls_idoc_data-sdata = ls_data_a. select single smtp_addr from adr6 into ls_data_a-lfurl where addrnumber = ls_data_m-ADRNR and flgdefault = ’X’. ls_data_m = ls_idoc_data-sdata. 3.

2.4.4.5.2 2.4. Add new Processing Routine for EDI with Processing Program RSNASTED and Form Routine EDI_PROCESSING in the message type NEU. see SAP Note 793229. the purchase order output is in IDOC format. 36/84 PUBLIC 07/12/2010 . Choose Maintain Message types for PO.5.4.0 with enhancement package 3 or earlier.4. Setting Up Purchase Order Output Transaction Code IMG Path SPRO SAP Customizing Implementation Guide Materials Management Purchasing Messages Output control Message types Define message types for Purchase Order 1. because in Materials Management (MM) free text items are not supported in the order response and ASN. Prerequisites You have created Output type NEU for purchase order printout.2 Purchase Order Output 2.5 Purchase Order Output Settings for SAP ERP 6. Caution For the correct control of follow-on documents in Supplier Self-Services. Define Partner Roles for the message type as EDI and Function LS (Logical System). 2.0 EHP3 and Earlier 2.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 2. 4. Save your entries and choose Exit. Caution Free text items cannot be used in the Plan-Driven Procurement with Supplier Integration scenario.4.4.4.5.1 Outputting Purchase Order Documents in IDOC Format If you are using a SAP ERP system with release ECC 6. 2. 3.1 Setting Up Purchase Order Output In this section you set up two printing operations for the message type for purchase order output.

Caution Free text items cannot be used in the Plan-Driven Procurement with Supplier Integration scenario.4. Defining Message Schema for Purchase Order Transaction Code IMG Path SPRO SAP Customizing Implementation Guide Materials Management Purchasing Messages Output Control Message Determination Schemas Define Message Schema for Purchase Order 1. Choose New Entries. 07/12/2010 PUBLIC 37/84 . because in Materials Management (MM) free text items are not supported in the order response and ASN. 8.3 Scheduling Agreement Releases Output 2.4.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 5. 3. Enter the following records: Activity/operation 1 2 Note CTyp NEU NEU Name (Example) New PO printout New PO printout Short Text New Change The output operation will be used for IDoc transfer. Select procedure RMBEF1 and double click on Control Data. 7. Choose Maintain Message Determination Schema: Purchase Order. 2. Choose Fine-Tuned Control: Purchase Order.1 Setting Up Scheduling Agreement Release Outputs In this section you set up two printing operations for the message type for scheduling agreement release output.2 2. 2.4.4. Specify the control data for the Message type NEU with the requirement 101. Prerequisites You have created Output type NEU for scheduling agreement release. Save your input. 4.5. Choose Save.5. 6.3.

Add new Processing Routine for EDI with Processing Program RSNASTED and Form Routine EDI_PROCESSING in the message type NEU. 3. 5. 2. Specify the control data for the Message type NEU with the requirement 101. Save your input. 8. see SAP Note 793229. 3. 38/84 PUBLIC 07/12/2010 . Choose New Entries. 4. Choose Maintain Message Determination Schema: Outline Agreement. 7.2 2. Save your entries and choose Exit. Choose Maintain Message Types for Forecast Delivery Schedule/Expediter. Select procedure RMBEV1 and double click on Control Data. Defining Message Schema for Outline Agreement Transaction Code IMG Path SPRO Implementation Guide for R/3 Customizing (IMG) Materials Management Purchasing Messages Output Control Message Determination Schemas Define Message Schema for Outline Agreement 1. 6. Save your input. Setting Up Scheduling Agreement Release Output Transaction Code IMG Path SPRO SAP Customizing Implementation Guide Materials Management Purchasing Messages Output control Message types Define Message Types for Scheduling Agreement Release/Expediter 1. 4. Enter the following records: Activity/operation 1 2 Note CTyp NEU NEU Name (Example) Outline agreement Outline agreement Short Text New Change The output operation will be used for IDoc transfer. Choose Fine-Tuned Control: Forecast Delivery Schedule/Expediter. 2. Define Partner Roles for the message type as EDI and Function LS (Logical System).4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration Caution For the correct control of follow-on documents in SUS.

Choose LS Partner Type (logical system).4. perform the following steps for each of the MM systems. 3. Recommendation For each message type. on the Output Options tab. 2. a) Message type Z_CREMAS_SUSMM Partner Function Basic Type CREMAS03 Receiver Port Port in <MM_BS> for destination <INTEGRATION-SERVER_BS> b) Message type ORDERS in Detail Partner Function LS Basic Type ORDERS02 Receiver Port Port in <MM_BS> for destination Application EF Message Type NEU Process Code ME10 <INTEGRATION-SERVER_BS> Caution On the Message Control tab.4 Setting Up Partner Profile for Connectivity You have to create a new partner type for the <SUS_BS>CLNT<client> logical system to determine the documents to be exchanged by the Materials Management (MM) system and the SAP Supplier Self-Services (SAP SUS) suppliers. Creating the Partner Type for Document Exchange Transaction Code Menu Path WE20 Tools ALE Partner Profile ALE Administration Runtime Settings 1. do not select the Change indicator.4.5.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 2. Enter the Partner Number for the <SUS_BS>CLNT<client> system.2 2. Caution If you are using the Plan-Driven Procurement with Supplier Integration business scenario with more than one MM system. 07/12/2010 PUBLIC 39/84 . select the Transfer IDoc immed. In the Outbound Parmtrs section. create outbound messages with the data listed below.

select the Change indicator. In the IDoc Type box. select Queue Processing. create inbound messages with the following data: a) Message type ORDRSP in Detail (Receipt of a purchase order confirmation) 40/84 PUBLIC 07/12/2010 . cancellation of goods receipt notifications. d) Message type DELINS in detail (for scheduling agreement releases) Partner Function LS Basic Type DELFOR02 Receiver Port Port in <MM_BS> for destination Application EL Message Type LPH1 Process Code ME14 <INTEGRATION-SERVER_BS> Caution On the Message Control tab. enter DELVRY03 in the Basic Type field. e) Message type STPPOD (for notification of goods receipt. and return deliveries. 4. In the Inbound parmtrs section.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration c) Message type ORDCHG in Detail Partner Function LS Basic Type ORDERS02 Receiver Port Port in <MM_BS> for destination Application EF Message Type NEU Process Code ME11 <INTEGRATION-SERVER_BS> Caution On the Message Control tab. since a purchase order is changed. and return deliveries) Partner Function LS Basic Type DELVRY03 Receiver Port Port in <MM_BS> for destination Application Message Type GRN Process Code <INTEGRATION-SERVER_BS> Note Use report RPODDELVRY for sending notifications of goods receipts.2 2. do not set the Change indicator. Note On the Output Options tab page. and enter IDOC_QUEUE_SUS_MM in the Rule Name field. cancellations of goods receipt notifications.

70 SR SAP Library SAP R/3 Enterprise Application Components Logistics Materials Management Purchasing Entering Text.4. Prerequisites You have defined the message type NEU for purchase order output.0 the purchase orders are sent out using the new enterprise services if the business function (LOG_MM_P2PSE_1) is activated. See SAP Note 1075345 for the follow-on document control in the Purchase Order and apply the instructions specified in that note into the SAP ERP system correctly.ASN) Partner Function Process Code DELS c) Message type INVOIC (Receipt of a Logistics Invoice Verification) Partner Function Process Code INVL 2. This does not require any additional configuration in the SAP ERP system.2 2. b) Message type DESADV (Receipt of an advanced shipping notification . the configurations mentioned below need to performed. As of SAP SRM 7. use ORDR instead of ORDR_SUS.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration Partner Function Process Code ORDR SUS Caution If you make configurations for SAP SRM.5. For more information.com SAP R/3 and R/3 Enterprise SAP R/3 and R/3 Enterprise 4.4. see SAP Help Portal at help. however confirmations of the XI need to be implemented.sap. you configure supplier master data to allow a supplier to send out orders to the Supplier Self-Services (SUS) component.5 Setting Up Supplier for Purchase Order Output In this section. Defining Purchasing Output Transaction Code Menu Path MN04 Logistics Materials Management Data Messages Purchase Order Purchasing Create Master 07/12/2010 PUBLIC 41/84 . If you do not activate the business function (LOG_MM_P2PSE_1). Printing and Transmitting Documents .

if the purchase order is newly created.4./Vendor for EDI and choose Enter. partner. n ORDCHG.2 2. if it is not necessary to send every document immediately. enter LPH1 and choose Enter. when saving the application). Select Key combination: Purchasing Output Determination: Purch. In the Output Type field. Org. Defining Purchasing Output Transaction Code Menu Path MN10 Logistics Materials Management Purchasing Master Data Messages Scheduling Agreement Delivery Schedule Create 1. 2. Org. 2. set time to 4 (send immediately. and medium must be exactly as given.5.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 1. 3.4. Prerequisites You have defined the message type LPH1 for scheduling agreement releases.6 Setting up Supplier for Outputting Scheduling Agreement Releases In this section you configure supplier master data to enable a supplier to send out scheduling agreement releases to the Supplier Self-Services (SUS) component. 3 (send when calling transaction in the application) is sufficient. Enter a record with the following data: 42/84 PUBLIC 07/12/2010 . Result This output creates the following IDoc: n ORDERS. Enter a record with the following data: Vendor <Vendorr> Partner Function Partner LS Medium Time 3 (Logical system) <SUS_BS>CLNT<client> 6(EDI) Note Values for partner function. 3. Time setting is up to customer needs./Vendorr for EDI and choose Enter. If so. 2. For each supplier existing in the SUS system you create an output condition record. In the Output type field enter NEU and choose Enter. if a purchase order is changed. Select Key combination: Purchasing Output Determination: Purch.

4. and medium must be exactly as given. endif. Configuring User Exit MEETA001 For calculating open quantities in scheduling agreement releases. if not every document has to be sent immediately.. modify i_ekeh from ls_ekeh. 3 (send upon calling transaction in the application) is sufficient.2 2. Choose for example project ZMMLPA. when saving the application). immed.ls_ekeh-dabmg. Add the following coding to user exit Define schedule line type (backlog. Ensure the display of your project shows a green light for user exit EXIT_SAPLEINL_001. endloop. If so. if lv_menge eq 0. you configure the user exit MEETA001: Transaction Code Menu Path CMOD Tools ABAP Workbench Project Management Utilities Enhancements 1. ls_ekeh-menge = lv_menge. Time setting is up to customer needs. Choose Enhancement assignments and assign enhancement MEETA001 and component EXIT_SAPLEINL_001. 07/12/2010 PUBLIC 43/84 . set time to 4 (send immediately. preview): .. 3.req. data: ls_ekeh like i_ekeh lv_menge like i_ekeh-menge loop at i_ekeh into ls_ekeh check not ls_ekeh-updkz is initial lv_menge = ls_ekeh-menge . Result This output creates the IDoc DELINS.. 2. partner. Activate the enhancement assignment. .4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration Vendor <Vendor> Partner Function Partner Medium Time 3 LS (Logical System) <SUS_BS>CLNT<client> 6(EDI) Values for partner function... clear ls_ekeh-updkz else.

0 with enhancement package 4. enter OPS_SE_PUR_CHANGED_EVENT CHECK. 14.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 2.4. 4. enter WS53800008. In the Receiver Type field.4.2 More Information About PO Output Settings for SAP ERP 6. 2. 10. 13. In the Receiver Type field. 9. In the Receiver Function Module field. Select the Linkage Activated checkbox. enter CHANGED. enter SWW_W1_CREATE_VIA_EVENT_IBF. 16.4.1 Outputting Purchase Order Documents in Services If you are using an SAP ERP system with a release of ECC 6. enter CL_SE_PUR_WF_OUT.4. 6. enter CREATED. Event Type Linkages [SWETYPV] 44/84 PUBLIC 07/12/2010 . and the business function LOG_MM_P2PSE_1 is activated.6 Purchase Order Output Settings for SAP ERP 6. 7. 5. 3.2 2. Choose New Entries. For more information on BADI documentation see. Choose New Entries. In the Receiver Function Module field. In the Object Types field. In the Check Function Module Field. In the Event field. the purchase order output uses Enterprise Services method execution. SAP Note 1317798. Maintain Event Type Linkages for Purchase Order Output in PurchaseOrderERPRequest_Out_V1 SOA Service (Supplier Self-Services Scenario) 1.0 EHP4 Onwards 2.6. Select the Linkage Activated checkbox. 11. Save your entries. 15. enter WS53800008. 2. enter SWW_W1_CREATE_VIA_EVENT_IBF. In the Object Types field. Run transaction Display/Maint. 12.4.4. In the Event field. 8. Save your entries. enter CL_SE_PUR_WF_OUT.6. Event Type Linkages (SWETYPV).0 EHP4 Onwards Run the following system transactions in SAP SRM: n Business Add-Ins: Definitions [SE18] n Display/Maint.

you perform the customizing activities required for the invoice verification.7 Invoice Verification 2.7. Assigning Tax Codes Transaction Code IMG Path OBCD SAP Customizing Implementation Guide Materials Management Logistics Invoice Verification EDI Assign Tax Codes Assign to all tax codes of the SRM system (Partn.1 Setting Up Invoice Verification In this section. Defining Program Parameters Transaction Code IMG Path OMRY SAP Customizing Implementation Guide Materials Management Logistics Invoice Verification EDI Enter Program Parameters 07/12/2010 PUBLIC 45/84 .type (partner type) LS.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 2. 2. PartnerNo (partner number) <SUS_BS>CLNT<client>) the according tax code of the MM system. Assigning Partner Data to Company Code Transaction Code IMG Path OBCA SAP Customizing Implementation Guide Materials Management Logistics Invoice Verification EDI Assign Company Code 1.4. Choose New Entries.4. the logical system defined for the SUS system will have a name such as <SUS_SID>CLNT<client>. Enter a record with the following data: Partner Type LS Partner Number <SUS_BS>CLNT<client> Company Code <CoCode of the connected MM_BS> Note Typically.4.4.2 2.

Enter the Partner number for the vendor .8.4.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 1. Enter a record with the following data: Partner Type LS Partner Number <SUS_BS>CLNT<client> Company Code <CoCode of the connected MM_BS> Note Enter the following in the details view: n Document type for invoice: RE n Document type for credit memo: RE Note For invoices with delivery costs.8 Evaluated Receipt Settlement (ERS) 2. Prerequisites You must define ERS output types. 2. 1. Choose New Entries. If you do not plan to use ERS you can skip this section. create outbound messages with the following data: Message type GSVERF in detail (credit advice message within ERS processing) 46/84 PUBLIC 07/12/2010 .4.1 Setting up Evaluated Receipt Settlement (ERS) This section describes the settings required for using ERS processing. 2.2 2. 2. Creating the Partner Type for ERS Document Exchange Transaction Code Menu Path WE20 Tools ALE Partner Profiles ALE Administration Runtime Settings Maintain the following settings for each vendor with which you want to use ERS processing.4. Choose Partner type LI(vendor) 3. In the Outbound parmtrs section. see SAP Note 800866.4.

2 2.4

Basic Settings for Service Procurement Classic Settings for Supplier Collaboration

Partner Function
VN

Basic Type
GSVERF01

Receiver Port
port in <MM_BS> for destination

Application
MR

Message Type
ERS6

Process Code
MRRL

<INTEGRATION_SERVER_BS>

Creating Condition Records Transaction Code Menu Path
MRM1

SAP Customizing Implementation Guide Materials Management Logistics Invoice Verification Message Determination Maintain Conditions

1. Enter Output type ERS6. 2. Select and choose Enter Key combination CoCode, Vendor and choose Enter. 3. Create for every supplier a record with the following data:
Vendor
<supplier>

Partner function
LS (Logical System)

Partner

Medium

Time
3

<SUS_BS>CLNT<client> (EDI) 6

Values for partner function, partner and medium must be exactly as given. Time setting is up to customer needs; 3 (send upon calling transaction in the application) is sufficient, if not every document has to be sent immediately. If so, set time to 4 (send immediately, when saving the application). For more information about creating condition records, see the documentation of the Customizing for SAP ERP in SAP Customizing Implementation Guide Materials Management Logistics Invoice Verification Message Determination Maintain Conditions .

2.4.4.9 Data Processing in Materials Management

2.4.4.9.1 Maintaining Data in the Materials Management System
In this section you perform the necessary steps to configure supplier master data and set up purchasing info records. See n Setting up Supplier Master Data [external document]

07/12/2010

PUBLIC

47/84

2 2.4

Basic Settings for Service Procurement Classic Settings for Supplier Collaboration

n Setting up Purchasing Info Records [external document]

2.4.4.9.2 Setting up Vendor Master Data
In this section, you create, replicate, and synchronize supplier master data. To enable the Evaluated Receipt Settlement (ERS) process for a vendor, you specify the account number together with the company code.
Setting up Vendor Account Numbers Transaction Code Menu Path XK01 Logistics Materials Management Purchasing Data Vendor Central Create Master

1. On the Correspondence Accounting screen, enter the company code in the Acc w/ Vendorfield. 2. Select Environment Classification and select the class type ALV, when required. Assign the class Z_CRED_SUSMM_<SUS_BS> to the supplier. 3. In the supplier address data, under Street Address, enter a city and a country.
Note

Only vendors for whom you have entered address data are replicated in SUS. 4. Choose Communication and enter an e-mail address.
Note

Make sure that you use an Account Group with an e-mail address. As a prerequisite, you have determined for this account group that the internet mail address is required. You do this in transaction OMSG under Field Status General Data Communication . See Customizing for SAP ERP under Logistics - General Business Partner Vendors Control Define Account Groups and Field Selection (Vendor)
Initially Replicating Vendor Data Transaction Code Menu Path BD14 Tools ALE Cross-Application Master Data Distribution Vendor Send

1. In the Send Vendor screen, enter the reduced message type, for example, Z_CREMAS_SUSMM. 2. For parallel processing, enter a value in the Number of Vendors per Process field. 3. Choose Execute.

48/84

PUBLIC

07/12/2010

2 2.4

Basic Settings for Service Procurement Classic Settings for Supplier Collaboration

Synchronizing Vendor Data Transaction Code Menu Path SE38 Tools Editor ABAP Workbench Development ABAP

1. Choose report RBDMIDOC. 2. Create variant MM-SUS. 3. Maintain variant MM-SUS with message type Z_CREMAS_SUSMM.
Note

Using transaction SM36, define a job with report RBDMIDOC and variant MM-SUS.

2.4.4.9.3 Setting Up Purchasing Information Records
This is an optional setting. Purchasing information records allow you to enter information necessary for Evaluated Receipt Settlement (ERS) and to maintain proposal data for the document flow. For example, whether or not you can receive an order acknowledgement or an advanced shipment notification (ASN) for a Purchase Order item depends on the purchasing data settings in the information record.
Enabling Order Acknowledgement, ASN Receipt and ERS Transaction Code Menu Path ME12 Logistics Materials Management Data Info record Change Purchasing Master

1. Select an information record. 2. Choose Purch. Org. data 1. 3. Set the indicator Ackn.Reqd (Order Acknowledgement Required) on the Control tab page.
Caution

By doing this you set the indicator Ackn.reqd for each position item with the relevant material. 4. To be able to receive order acknowledgement and ASN information, select in the ConfContrK (Confirmation Control Key) field control key 0001.
Note

Entering this control key in the info record saves data input when you create purchase orders.

07/12/2010

PUBLIC

49/84

2 2.4

Basic Settings for Service Procurement Classic Settings for Supplier Collaboration

5. To enable ERS processing, n Select the GR-Based IV indicator (goods receipt-based invoice verification for purchase order items) n Select the Tax code.

2.4.5 Settings for Supplier Self-Services
Note

Note that you must make the settings for supplier self-services in the supplier self-services client. If you are running supplier self-services on a different client than SAP SRM, remember to switch to the supplier self-services client before you make the supplier self-services settings (see transaction SOLAR_PROJECT_ADMIN for changing the client in your logical system).

2.4.5.1 Where to Find the Documentation for Supplier Replication and Transfer
You find the documentation for supplier replication and transfer in SAP Solution Manager under <project name> Configuration Structures SAP SRM 7.0 EHP1 Basic Settings for Supplier Qualification With Customizing Switch Supplier Self-Registration : n Supplier Replication from SAP ERP to Supplier Self-Services (MM-SUS) n Supplier Transfer from Supplier Self-Services to SAP ERP

2.4.5.2 Defining Organizational Plan for Suppliers
In this procedure, you define the organizational data in the supplier self-services system. You define only the root node (Central Supplier Group) and then you assign the supplier organizational plan to this root node. You define the central supplier group so that you can assign the respective currency to the corresponding supplier.
Procedure

Perform the following steps in the supplier self-services system:
Creating an Organizational Plan

Go to Customizing for SAP SRM under SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Organizational Management Create Organizational Plan or use transaction PPOCA_BBP.

50/84

PUBLIC

07/12/2010

Org.2 2. This is the default value for the central organizational unit for suppliers (Central Supplier Group) in the customizing activity Making Settings for Business Partners.4. 2. Note You can ignore the message about size problems that is issued. Enter a technical name and description for the organizational plan (for example. 3. Creating an Organizational Plan for Suppliers Go to Customizing for SAP SRM under SAP Supplier Relationship Management SRM Server Technical Basic Settings Settings for Supplier Synchronization Create Supplier Groups or use transaction PPOCV_BBP.2. Making Settings for Business Partners Go to Customizing for SAP SRM under Customizing for SAP SRM SAP Supplier Relationship Management Supplier Self-Services Master Data Make Settings for Business Partners . 2. 2. Save your input. Organization. Choose the Function tab and set the indicator Purch. 1. Enter a technical name and description for the organizational plan (for example. Maintain the following fields in the Customizing activity Make Settings for Business Partnersas described in the customizing under: n Central Supplier Group n Purchasing Organization Result You have defined a purchasing organization for all suppliers. SUS_PURORGS).4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 1. This is the default value for the purchasing organization (Default Pur.1 Creating the Organizational Plan Perform the following activity in Customizing for SAP SRM: SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan Run the following system transaction in SAP SRM: Change Supplier Groups [PPOMV_BBP] 07/12/2010 PUBLIC 51/84 . Save your input. and a central organizational unit for suppliers in the supplier self-services system. SUS_SUPPLIER) without setting the indicator Purch. Organization.) in the customizing activity Making Settings for Business Partners.5.

for example. SAP NetWeaver Business Intelligence (SAP NetWeaver BI) and SAP Bidding Engine.3 Supplier Self-Services User Management 2.2 2.4. which you access via http://<hostname>:<port>/sap/bc/bsp/sap/srmsus.5. first name. you can replicate the supplier user data to other components.3. if required Perform the following steps in the supplier self-services system: Performing SAP SRM Administrator Setup Run transaction SU01. you do the following: n Define the settings for business partners to replicate the business partners and to create users through user management n Make the relevant settings for the https protocol.1 Configuring Supplier Self-Services User Management When administrating user data of suppliers in addition to the administration in supplier self-services. Additionally. In this procedure. if required n Adjust the roles for supplier self-services user management in the supplier self-services back end. Note Make sure that a valid e-mail address. if required.5. and assign the role SAP SRM SUS: Administrator Purchaser (/SAPSRM/SUS_ADMIN_PURCH_EHP1) to it. and should only be assigned after careful consideration. Defining Settings for the Secure Sockets Layer Protocol For encrypting data from browser to system. Caution The role /SAPSRM/SUS_ADMIN_PURCH_EHP1 gives the user a wide range of authorizations.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 2. and last name are assigned to this user. this user can act as an SAP SRM administrator. you can make settings for the HTTPS protocol. srm_admin). create a dialog user (for example. You replicate the user data of suppliers in SAP Supplier Relationship Management (SAP SRM) for bidding or in SAP NetWeaver BI for reporting (analytics). 52/84 PUBLIC 07/12/2010 .4. if required n Run a supplier self-services (SUS) upgrade. The user name allows you to log in to supplier self-services.

Perform the following steps if necessary: Selecting Display role in SUS User Management (UM) Means that Only these roles are displayed in the supplier self-services user management. 2. 4. Using input help. For maintaining this set. Choose the Personalization tab.sap. an attribute set for supplier self-services specific settings exist. Note The personalization is valid for all roles.com SAP NetWeaver SAP NetWeaver Library SAP NetWeaver by Key Capability Security Network and Transport Layer Security Using the Secure Sockets Layer Protocol with the AS ABAP .4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration You can find more information on SAP Help Portal at http://help. Examples for changing attributes: Authorizations or menu entries Note For all roles maintained in transaction PFCG. Users can adjust created roles by changing the role attributes specific to supplier self-services. for example as copy of the delivered SAP roles. Defining Roles Customizing Path SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Master Data Define Roles 1. Select the entry BBP_SUS_ROLES_ATTRIBUTES (supplier self-services specific role attributes) and choose Change values. Users can create their own roles.2 2. select the corresponding role in transaction PFCG. By this the supplier administrator can assign these roles to the respective user. The system displays the Maintaining SUS specific roles dialog box. Service agent 07/12/2010 PUBLIC 53/84 . The user can be displayed as service agent by the buyer. 3. Choose Change Role. 5. choose one of the roles listed in the documentation of Customizing activity Define roles: If you want to change attributes of a role. copy the corresponding role in transaction PFCG to a new role in the customer name space and correct this one.

In this role the user is authorized to maintain any supplier user data. the previous data is no longer available. a maximum number of send attempts. For more information. The user is informed if a purchase order response has not been created for a purchase order within a specific period of time. The user is informed if a confirmation has not been created for a confirmed purchase order for a service within a specific period of time. The user is informed if a shipping notification (ASN) has not been created for a confirmed purchase order within a specific period of time. it takes the form of an e-mail with a standard text and a URL that links directly to the necessary follow-on activity. . start the mass generation of profiles. This role is automatically assigned to the user while the SUS Administrator is registering himself or herself.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration SAP SRM Administrator The user is defined as SAP SRM Administrator. Choose Save. or a fixed recipient) in the above Customizing activity. The user is informed if an invoice has not been created for a confirmed purchase order within a specific period of time. the priority.2 2. 6. see Regenerating Role Profiles [external document]. If it is a message. SUS Administrator Notification if purchase order not opened Notification if purchase order response is missing Notification if ASN is missing Notification if confirmation is missing Notification if invoice is missing Note You specify the type of notification in SAP SRM Customizing under SRM Server Cross-Application Basic Setting Event and Event Schema for Alert Management Define Event Schema. Performing a Mass Generation of Profiles If you have changed roles. 54/84 PUBLIC 07/12/2010 . The user is informed if a purchase order is not opened within a specific period of time. The notification can be a message or an alert. the alert category. You have to make additional settings for alerts (for example. Upgrading User Data Caution You must perform the following steps before you run the user data upgrade. After the upgrade.

07/12/2010 PUBLIC 55/84 . The RFC user is an SAP user of the type Service. Run the report BBP_SUS_BP_UM_SUS20_TO_SUS3OT.1 Creating an RFC User To receive messages (including status messages). 2.3. Enter a name. SUS UM in SUS 2.0 to SUS UM in SUS in SRM 4.0 UME 3. Procedure 1. Therefore. 5.0 UME 3. for example MAIL_ADMIN. an RFC user is required.2. Choose New. you can enter the systems to which the user data that was entered in supplier self-services should be replicated. 3.0 Do the following: No steps are necessary Run the migration report BBP_SUS_BP_UM_JUM2SUM Run the migration reports BBP_SUS_BP_UM_JUM2SUM and BBP_SUS_BP_UM_SUS20_TO_SUS3OT. 4.0 SUS in SRM 4.0 to SUS UM in SUS 2.5. An RFC user is also required in order to receive messages using the SMTP plug-in.2 Defining RFC Destinations for User Data Synchronization 2. select the user type Service.3. On the tab page Logon data. see SAP Note 729355. 2.0 to SUS UM in SUS in SRM 4.0 to UME 4.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration Note For more information about upgrading the data in SUS User Management.4. An RFC user has to be created in every client in which messages are to be received.0 Note In the Customizing activity Maintain Systems for Synchronization of User Data. it is not possible for a person to logon with this user name in dialog mode. If you want to change from User Management Engine (UME) 3. Enter a password.5.0 to SUS in SAP SRM 5. Choose Tools Administration User Maintenance Users . No steps necessary if report BBP_COPY_FI_INFO_TO_ITEM has already been run.2 2.4.

2. Save your entries. 7. Under Logical System. Choose Save. and FctMod Delete User fields. In the Roles in External Systems view.2 Synchronizing User Data You define the logical systems that you use to synchronize user data from Supplier Self-Services (SUS) User Management. for example /SAPSRM/BIDDER. If you want to use the business partner ID from the procurement system instead of the one from SUS. FctMod. you can set the indicator Use Purchasing BP ID. see SAP Help Portal (link above this document in SAP Solution Manager) n You have made the settings in Customizing for SAP Supplier Relationship Management under SAP Implementation Guide SAP Supplier Relationship Management SRM Server Technical Basic Settings Define System Landscape Procedure 1. that can be assigned to the user in this system. 9. BP ID field. Create User. In the External Systems view.4. 7. change.3. In Customizing for SAP Supplier Relationship Management under SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Master Data Maintain Systems for Synchronization of User Data 2. On the Profiles tab page. enter the name of a function module in the FctMod. select the system to which you want to connect the SUS User Management. This function module is called in the external system to assign the user to the relevant supplier company. enter the authorization profile S_A. select New Entries. 3. Prerequisites n You know which systems the suppliers should access from SUS. In the FctMod.2 2. and delete users in the external system. 56/84 PUBLIC 07/12/2010 . 6. For information about creating an RFC user. In the System Name field. Set the Activated indicator to activate the synchronization of user data with this system. 10.SCON. Enter a role. enter the function modules that are called to create. 8. select New Entries. These systems are relevant for the synchronization of user data.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 6.5. 5. enter the reference name of your choice. Change User. This profile minimizes the risk of misuse. 11.2. If necessary. This is relevant if your suppliers access reporting functions in SAP NetWeaver Business Intelligence (SAP Netweaver BI) or want to participate in RFxs via the SAP Bidding Engine. 4. You have maintained the relevant RFC destinations in Customizing for SAP Supplier Relationship Management under SAP Implementation Guide SAP Supplier Relationship Management SRM Server Technical Basic Settings Define RFC Destinations . even if the communication system does not store the password is encoded form.

13.2 2.4 Setting Up Services for Supplier Self-Services You need to make the following settings to use Business Server Pages (BSP) as a user interface and start the self-registration directly. Only these roles.3.5. 2. specify the roles in the external system to which these roles are to be assigned. and the standard role defined in step 7. In the SUS Roles column.5.4. for example sus_service.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 12. see SAP Solution Manager under SAP SRM Configuration SAP SRM 7. Choose the Roles tab page and assign the following roles: n SAP_BC_BASIS_MONITORING n /SAPSRM/SUS_ADMIN_SUPPL_EHP1 07/12/2010 PUBLIC 57/84 . Enter a user name.4. Choose the Logon data tab page and set the Service indicator in the User Type screen area. Result The user data synchronization is activated between SUS User Management and the relevant external systems. Save your entries. are replicated to the external system. You define a user called sus_service. In the Roles column. For more information about activating SICF Services. 2. Choose Create. which is to be used for anonymous login for the self-registration. enter the roles that you want to replicate from the SUS system.0 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration Settings for Supplier Self-Services Setting Up Services for SUS Activate SICF Services Perform the following steps in the Supplier Self-Services (SUS) system: Creating and Assigning Users Transaction Code SU01 1. 3. 4.3 More Information About Supplier Self-Services User Management Perform the following activity in Customizing for SAP SRM: Supplier Self-Services Interface Specify Data Privacy Settings for Suppliers Run the following system transaction in SAP SRM: n User Maintenance [SU01] Settings for User 2.

2. for example sus_service. for example /sus_selfreg. 6. Note We recommend that you use HTTPS. choose Create External Aliases. Choose External Aliases.2 2. Choose Save. If you use HTTPS. 4. Activating SICF Services Transaction Code Note SICF For more information about inactive services in the Internet Communication. see SAP Note 517484. enter the name of the user you created before (see “Creating and Assigning User”). Enter a password. select the radio button SSL in the Security Requirements area. The Maintain external aliases dialog box appears. On the Logon data tab page. Enter an appropriate name in the External Alias field. Activate the following SICF services for SUS by choosing Activate Service in the context menu: n n n n n n n n n n n sap sap sap sap sap sap sap sap sap sap sap bc bsp sap system : System Services Business Server Pages bc bsp sap public bc : Basis Mime Objects public bsp sap htmlb : HTMLB Public Handler public bc bc bsp sap srmsus : SUS Supplier Self-Services bc bsp sap srmsus_selfreg bc bsp sap bbp_sus_sagent (only relevant for Service Procurement) public bsp sap public bc public bsp sap system public bc ur xi Creating Aliases Transaction Code Creating an alias for supplier self-registration SICF 1.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 5. 3. 5. 58/84 PUBLIC 07/12/2010 . You can create and activate the service in transaction SMICM. Choose Execute. In the context menu (secondary mouse button) for the virtual host.

Test the SICF service. see Defining Organizational Plans for Suppliers [page 50].4.2 2. The URL for suppliers is maintained so that the self-registration can be started directly. change the URL in the URL for UM field. 2. Adjusting URLs Transaction Code Customizing Path SICF Supplier Relationship Management Supplier Self-Services Master Data Make Settings for Business Partners To adjust the URL for self-registration. Save your entries. use transaction Vendor Groups (BBP) Change (PPOMV_BBP) Procedure Customizing Path Supplier Relationship Management Supplier Self-Services Master Data Make Settings for Business Partners 07/12/2010 PUBLIC 59/84 . 9.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 7. in this case: https://<hostname. for example by calling https://<hostname>:<port>/sap/bc/bsp/sap/ srmsus_selfreg. see Setting up Services for Supplier Self-Services [page 57]. Result The SICF services for SUS are activated. This URL is sent by e-mail to the corresponding user and enables the user to start the self-registration process. Note Enter the same path that you used as the external alias in “Creating an alias for supplier self-registration”. To check whether the organizational plan for suppliers has been correctly defined.domain><port>/sus_selfreg.5.5 Making Settings for Business Partners Prerequisites n You have defined organizational plans for suppliers. n You have defined a URL for User Management Registration. Choose the Trg Element tab page and enter the service target by choosing a node in the Virtual Hosts / Services selection tree as follows: <name of virtual host> sap bc bsp sap srmsus_selfreg 8.

enter the URL destination for your SAP Bidding Engine system under Parameter value. Choose Save.5. 2. and information area n To force users to change the password on initial login Prerequisites For the location of your SAP Bidding Engine and SAP NetWeaver BI. 2.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 1. you have connected SAP Bidding Engine and SAP NetWeaver BI to your Supplier Self-Services (SUS) system. if you want to link directly to them from your application. Enter data as described in the Customizing activity. 3.2 2. For the key BW_SERVER. Procedure IMG Path Supplier Relationship Management Supplier Self-Services Settings for User Interface Customer Settings 1. header line. 60/84 PUBLIC 07/12/2010 . menu width.com) with the following: http://<UM>:<port>/sus_selfreg. enter the URL destination for your SAP NetWeaver BI system under Parameter value.6 Defining Customer Settings In this section you can define n The location of your SAP Bidding Engine and SAP NetWeaver Business Intelligence (SAP NetWeaver BI) systems. For the key BIDDING_SERVICE.4. breadcrumb. Replace the specified URL (www. n List entries per page n Item list entries per page n The menu folder status n To show the payment status of invoices n To show and hide elements of the user interface: Scenario. 2.xyz-supplier-portal.

5. If you have entered the key FORCE_INITITIAL_PASSWORD_CHANGE with value TRUE. SHOW_ELEMENT_BREADCRUMB. n URL before changing: http:://<hostname. NO_TOP_LOGO. extend the URL to &SAP-CLIENT=<client number> with no space.4.domain:port>/SAP/BW/BEX?CMD=LDOC&TEMPLATE_ID=0TPL_BBP_C01_SUS_00 n URL after changing: http:://<hostname. new SUS users have to change the password with the first login.5. ITEM_LIST_ENTRIES_PER_PAGE.4. that you have defined for the transaction type. MENU_FOLDER_STATUS.7. 4. You must specify number ranges for the following local documents: n n n n n Purchase orders Purchase order responses Shipping notifications Confirmations Invoices Procedure See Customizing for SAP SRM under SAP Implementation Guide SAP Supplier Relationship Management SRM Supplier Self-Services Cross-Application Basic Settings Settings for Documents Number Ranges For the interval number.domain:port>/SAP/BW/BEX?CMD=LDOC&TEMPLATE_ID=0TPL_BBP_C01_SUS_00&SAP-CLIENT=300 3. See Customizing for SAP SRM under SAP Implementation Guide SAP Supplier Relationship Management SRM Supplier Self-Services Cross-Application Basic Settings Settings for Documents Define Transaction Types 07/12/2010 PUBLIC 61/84 . you must enter the value of Int. but on different clients. MENU_WIDTH and SHOW_ELEMENT_INFO.7 Number Ranges for Documents 2. For the keys LIST_ENTRIES_PER_PAGE. SHOW_ELEMENT_MENU.1 Defining Number Ranges You specify the number ranges for the documents in the Supplier Self-Services system. SHOW_INVOICE_PAY_STATUS.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration Note If SAP NetWeaver BI and SUS run in the same system.2 2. 2.No. see the documentation of the Customizing activity Customer Settings.

9 Creating Buyer Data for Plant Maintenance Integration 2. Procedure Transaction Code BBP_SUS_BP_ADM 1.9. Choose Business partner as company code.4.5.1.4.5.2 2. 2. 3.8 Extending Tax Number Mapping Perform the following activity in Customizing for SAP SRM: Supplier Self-Services (BAdIs) Master Data Extension for Tax Number Mapping Business Add-Ins 2.4.7.5.5. For ERS processing. Expand the Business partner folder. In the selection screen.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 2.1 Creating Buyer Data In this section you define the SRM master data for the buyer within business partner administration. enter the following data: n The company code (corresponding company code in MM system) n Address and tax information n Other information if required 62/84 PUBLIC 07/12/2010 .4. this includes entering the company code within the account data.1 More Information About Defining Number Ranges Perform the following activities in Customizing for SAP SRM: n n n n n n SRM Server Cross-Application Basic Settings Number Ranges Define Number Ranges for Purchase Orders SRM Server Cross-Application Basic Settings Number Ranges Define Number Ranges for Purchase Order Responses SRM Server Cross-Application Basic Settings Number Ranges Define Number Ranges for Shipping Notifications SRM Server Cross-Application Basic Settings Number Ranges Define Number Ranges for Confirmations SRM Server Cross-Application Basic Settings Number Ranges Define Number Ranges for Invoices SRM ServerCross-Application Basic SettingsDefine Transaction Types Supplier Self-Services Number Ranges Supplier Self-Services Number Ranges Supplier Self-Services Number Ranges Supplier Self-Services Number Ranges Supplier Self-Services Number Ranges 2.

Note This configuration step is optional. The system then excludes these items when it creates shipping notifications based on scheduling agreement releases. Choose Execute.4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 4. 07/12/2010 PUBLIC 63/84 . the system includes all items from the scheduling agreement release in the shipping notification by default. 2.4.5. you can then create shipping notifications based on the scheduling agreement releases. 2.2 2. Procedure Transaction code Customizing Path SPRO SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Cross-Application Basic Settings Settings for Documents Specify Means of Transport Caution You must maintain the keys and descriptions manually in accordance with the entries in the SAP Materials Management system. In the Supplier Self-Services (SUS) system. If you do not want the system to include all items in the shipping notification.11 Defining Filters for Scheduling Agreement Releases You can receive scheduling agreement releases from Materials Management (MM).5. When you create a shipping notification based on a scheduling agreement release.10 Defining Means of Transport This section describes the procedure you use to enter keys and descriptions for individual shipping material types that determine how goods are transported. for example). Result The system shows a report result with the <new business partner number>. you can use BAdI BBP_SUS_FILTER_SCHAR (Filters for Scheduling Agreement Releases) to filter out items (by delivery date.4.

delivered by SAP. Features Query List Description Authorization for Suppliers from SUS / Supplier Portal Sales Values (for Vendor) Sales Values per Contract (for Vendor) Sales History (for Vendor) SUS: Contract Overview SUS: Expiring Contracts SUS: Evaluation Data on Document Level Evaluation of Criteria (SUS) Comparison of Overall Scores (SUS) Evaluation of Criteria (with Event / SUS) SUS: Evaluation of Service Provider Sales Values per Service Agent (for Vendor) SUS: Supplier Consignment Stock SUS: Cobweb Diagram for Supplier Scores Technical Name 0SRSA_IS1_Q001 0SR_MC01_SUS_Q0001 0SR_MC01_SUS_Q0002 0SR_MC02_SUS_Q1002 0SRCT_DS1_SP_Q001 0SRCT_DS1_SP_Q002 0SR_VE_SUS_Q001 0SR_VE_C1_SUS_Q001 0SR_VE_C1_SUS_Q002 0SR_VE_C1_SUS_Q009 0SR_VE_C1_SUS_Q005 0SR_MC01_SUS_Q0003 0IC_C03_Q0019 0SR_VE_C1_Q021 64/84 PUBLIC 07/12/2010 . see SAP Solution Manager under <project name> Configuration SAP SRM <release> Basic Settings for SAP SRM Basic Settings for Analytics Lists of Content Objects and Transactions .2 2. Prerequisites n You have performed all the steps necessary for general SAP NetWeaver BI configuration.4.6 Supplier Self-Services: Available Queries This document lists the predefined queries for Supplier Self-Services. See SAP Solution Manager under <project name> Configuration SAP SRM <release> Basic Settings for SAP SRM Basic Settings for Analytics .4 Basic Settings for Service Procurement Classic Settings for Supplier Collaboration 2. For more information. n All the business content for this scenario is installed and activated.

1 Purchase Requisition with Service Directories The process Purchase Requisition with Service Directories consists of the following process steps: 1. select the Configuration tab. Release purchase requisitions 3. Select the Documentation tab. Process purchase requisitions 2. 5. 4. 8. 07/12/2010 PUBLIC 65/84 . Select the Documentation tab. Monitor/view list display of purchase requisitions You can find a process description in SAP Solution Manager under <project name> Scenarios Service Procurement Classic Business Processes Purchase Requisition with Service Directories . You can find a scenario description in SAP Solution Manager under <project name> Scenarios Service Procurement Classic . 7.3 Service Procurement Classic 3 Service Procurement Classic This section describes the settings that are required to run the Service Procurement Classic scenario. 3. 6. 3. To find the process-related configuration content.2 Searching for Sources of Supply Centrally The process Searching for Sources of Supply Centrally consists of the following process steps: 1. 2. 9. 3. Start sourcing application Search for appropriate source of supply Assign contract Assign supplier Create RFx from sourcing application Create auction from sourcing application Process workload distribution Create purchase order from sourcing application Create contract from sourcing application You can find a process description in SAP Solution Manager under <project name> Scenarios Self-Service Procurement Extended Classic Business Processes Searching for Sources of Supply Centrally .

3 Service Procurement Classic Processing Bidding Events 3. Upload RFx from file 3. Complete and save RFx 4.3. Withdraw bid You can find a process description in SAP Solution Manager under <project name> Scenarios Strategic Sourcing with RFx Business Processes Processing Bidding Events . Select the Documentation tab.2. Process workload reassignment 8. Change RFx 7. 3.1 Configuration Content for Searching for Sources of Supply Centrally Perform the following activities in Customizing for SAP SRM: SRM Server SRM Server SRM Server SRM Server SRM Server SRM Server SRM Server Innovations n SRM Server Innovations n n n n n n n Business Add-Ins Changes to Purchasing Document Data Business Add-Ins RFx Control of RFx Publication Business Add-Ins RFx Subsequent Split of Grouping Cross-Application Basic Settings Configure Priorities Business Add-Ins Interface Configuration Appearance of Priorities Business Add-Ins Sourcing Redetermination of the Contract To Be Used (Quota Arrangement) Cross-Application Basic Settings Service Procurement Activate Service Procurement Cross-Application Basic Settings Service Procurement Activate Central Contract Management Run the following system transaction in SAP SRM: ABAP Editor (se38) 3. Confirm participation 9. Create RFx 2.3 3. To find the process-related configuration content. Approve publication of RFx 5. Publish RFx 6.1 Configuration Content for Processing Bidding Events Perform the following activities in Customizing for SAP SRM: 66/84 PUBLIC 07/12/2010 . select the Configuration tab. Change bid 11. Create and submit bid 10.3 Processing Bidding Events The process Processing Bidding Events consists of the following process steps: 1.

Business Add-Ins Changes to Purchasing Group and Purchasing Organization Assignments . Activate the Customizing switch. To the bidder. Procedure 1.3.3 Activating Adaptable RFx Response Handling You use this procedure to activate Adaptable RFx Response Handling. Procedure Complete the activities in Customizing for Supplier Relationship Management by choosing SRM Server RFx Questions Process Dynamic Attributes . 3.2 Defining Dynamic Attributes Dynamic attributes refer to specific characteristics of products and services and can be incorporated into the bidding process in SAP Bidding Engine. RFx Questions Assign Groups to Product Categories .3 Service Procurement Classic Processing Bidding Events n n n n n SRM Server SRM Server SRM Server SRM Server SRM Server RFx Questions Define Data Types for Dynamic Attributes .4 Configuring Tender Fee A purchaser creates an RFx with a tender fee feature. 07/12/2010 PUBLIC 67/84 . 3. the purchasing organization can block access to the RFx by supplier until the tender fee payment has been submitted and processed. RFx Questions Assign Dynamic Attributes to Groups .3. 3. Prerequisites You have activated the business function SRM.3. 2.3 3. and allows the purchaser to simulate the weights used to evaluate RFx Responses in a response comparison. The tender fee is later paid by a supplier that has an interest in creating and submitting a response to the RFx. This allows the supplier to carry out RFx response modification at line item level. RFx Questions Define Groups . They are used to customize RFxs and appear as additional fields requesting specific information. Strategic Sourcing Innovations (SRM_SOURCING_1). Essentially. they appear as input fields for describing in detail the products or services being offered. Go to Customizing for SAP Supplier Relationship Management under SRM Server RFx Extended RFx Process RFx Response Activate/Deactivate Adaptable RFx Response Handling .

which allows suppliers to only access the RFx once they have paid the tender fee. such as online payment. The results of the evaluation of a supplier’s technical response (acceptance or non-acceptance) may determine whether a subsequent price evaluation is conducted.5 Configuring Two-Envelope RFx Response Purchasers create an RFx requiring a two-envelope response when their organization’s procurement process involves receiving and then evaluating separate technical and price responses from suppliers. n You have defined a transaction type for RFxs with a tender fee in Customizing for SAP Supplier Relationship Management SRM Server Cross-Application Basic Settings Define Transaction Types . Define the basic data for the tender fee. and the currency for the tender fee amount. a tender fee amount. Activate tender fees for RFxs in Customizing for SAP SRM under SRM Server RFx Extended RFx Process Tender Fee and Earnest Money Deposit (EMD) Activate/Deactivate Tender Fee . Procedure 1. such as the type of RFx it can appear on (restricted or public). or bank check. bank draft. Prerequisites n You have defined RFx types for the types of procurement your organization conducts. 68/84 PUBLIC 07/12/2010 . Define the payment method.3 3. n You have defined a transaction type for the two envelope RFx process in Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Define Transaction Types . cash. Result You can create an RFx with a tender fee feature.3 Service Procurement Classic Processing Bidding Events Prerequisites n You have defined RFx types for the different types of procurement your organization conducts. Procedure 1. in Customizing for SAP SRM under SRM Server RFx Extended RFx Process Tender Fee and Earnest Money Deposit (EMD) Define Basic Data for Tender Fee Payment . Activate the two-envelope RFx Response function in Customizing for SAP SRM under SRM Server RFx Extended RFx Process RFx Response Two-Envelope RFx Response Activate/Deactivate Two-Envelope RFx Response . This is done in order to determine which supplier offers the best value in terms of technical merit and price. in Customizing for SAP SRM under SRM Server RFx Extended RFx Process Tender Fee and Earnest Money Deposit (EMD) Define Tender Fee and EMD Payment Method .3. 3. 3. 2.

3 3. Define the basic data. 2. and duration time allowed for the simultaneous logon process to occur. such as initiation. success. You do this in Customizing for SAP SRM under SRM Server RFx Extended RFx Process Simultaneous Logon Define Basic Data for Simultaneous Logon . where two or more openers will simultaneously log on to the system to open the response. Result Purchasers can create an RFx with two-envelope features. and can upload documents to cFolders that can be accessed by internal users and suppliers who respond to the RFx. failure of the opening process by openers. 3.3. The procurement process may require that the opening of the supplier’s technical and price responses be conducted using a multiparty verification process.6 Configuring Multiparty Verification Process Purchasers create an RFx requiring a two-envelope RFx response when their organization’s procurement process involves receiving and then evaluating separate technical and price responses from suppliers. n You have defined a transaction type for a two-envelope RFx response process in Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Define Transaction Types . or whether the rejection of a technical response results in the automatic rejection of the price response. This is done in order to determine which supplier offers the best value in terms of technical merit and price. Define the cFolders available for storing RFx responses in Customizing for SAP SRM under SRM Server RFx Extended RFx Process RFx Response Two-Envelope RFx Response Define Basic Data for Technical RFx Response Folders . Activate simultaneous logon in Customizing for SAP SRM under SRM Server RFx Extended RFx Process Simultaneous Logon Activate/Deactivate Simultaneous Logon at RFx Response Opening . 3. 07/12/2010 PUBLIC 69/84 .3 Service Procurement Classic Processing Bidding Events 2. The multiparty verification process is used to preserve the integrity of the unopened responses until an official opening is conducted by pre-designated openers. Prerequisites n You have defined the RFx types for the different types of procurement your organization conducts. in Customizing for SAP SRM under SRM Server RFx Extended RFx Process RFx Response Two-Envelope RFx Response Define Basic Data for Two-Envelope RFx Response . Procedure 1. Define the basic data for multiparty verification. such as whether an e-mail is sent with the result of the technical response evaluation.

Evaluate Bid 2.4 Service Procurement Classic Evaluating Bids Result Purchasers can create an RFx with two-envelope RFx response features. Select the Documentation tab. bank draft. 3. Activate EMD in Customizing for SAP Supplier Relationship Management (SAP SRM) under SRM Server RFx Extended RFx Process Tender Fee and Earnest Money Deposit (EMD) Activate/Deactivate Earnest Money Deposit . and the currency for the EMD amount. Award Bid 3. if awarded the follow-on purchase order or contract. they will perform the work or deliver the materials as specified by the line item structure and any terms and conditions of the procurement document.3. in Customizing for SAP SRM under SRM Server RFx Extended RFx Process Tender Fee and Earnest Money Deposit (EMD) Define Tender Fee and EMD Payment Method . and essentially acts as the supplier’s guarantee that. The EMD is typically submitted as a letter of credit. 3. and then define the openers and evaluators of the technical and pricing responses. Procedure 1. bid guarantee. Define the basic data for EMD. such as online payment. To find the process-related configuration content. cash.4 Evaluating Bids The process Evaluating Bids consists of the following process steps: 1. 3. such as the type of RFx it can be used in. Approve Bid You can find a process description in SAP Solution Manager under <project name> Scenarios Strategic Sourcing with Live Auction Business Processes Evaluating Bids . or bid bond. 2. Define payment methods. an EMD amount. in Customizing for SAP SRM under SRM Server RFx Extended RFx Process Tender Fee and Earnest Money Deposit (EMD) Define Basic Data for Earnest Money Deposit .3 3. The EMD is submitted by a supplier submitting a response to the RFx. 70/84 PUBLIC 07/12/2010 . Result The purchaser can create an RFx with an EMD feature.7 Configuring Earnest Money Deposit (EMD) You use this procedure to allow purchasers to create an RFx with an earnest money deposit (EMD) feature. and bank check. select the Configuration tab.

which you can find in SAP Solution Manager under <project name> Configuration SAP SRM <release> Basic Settings for Strategic Sourcing .5 Service Procurement Classic Processing Follow-On Documents Note Before you configure this process. 5. To find the process-related configuration content. 3. 7. 3. Create or process purchase orders Release purchasing documents Find new source of supply Compare quotations Generate or manage versions of purchase orders Monitor the output of messages Monitor or view list display of purchase orders You can find a process description in SAP Solution Manager under <project name> Scenarios Self-Service Procurement Classic Business Processes Processing Purchase Orders in SAP ERP . 2. 4. Create purchase order in ERP 2. To find the process-related configuration content. select the Configuration tab. Select the Documentation tab. be sure to complete the basic settings for Strategic Sourcing. Note Complete the basic settings for Strategic Sourcing in SAP Solution Manager under <project name> Configuration SAP SRM 7. Create contract in ERP You can find a process description in SAP Solution Manager under <project name> Scenarios Strategic Sourcing with Live Auction Business Processes Processing Follow-on Documents .5 Processing Follow-On Documents The process Processing Follow-on Documents consists of the following process steps: 1. select the Configuration tab. 07/12/2010 PUBLIC 71/84 . 6. Create contract in SRM 3. 3.0 EHP1 Basic Settings for Strategic Sourcing .3 3.6 Processing Purchase Orders in SAP ERP The process Processing Purchase Orders in SAP ERP consists of the following process steps: 1. Select the Documentation tab.

7 Processing Sales Orders in Supplier Self-Services The process Processing Sales Orders in Supplier Self-Services consists of the following process steps: 1. For Service Procurement you can find these steps in SAP Solution Manager. Select the Documentation tab. Create sales order 2. If SUS runs in a different client than SAP Supplier Relationship Management (SAP SRM). web transactions.3 3.7. Configuration SAP SRM 7. 3.0 Basic Settings for Service Procurement For Plan-Driven Procurement you can find these steps in SAP Solution Manager.7.0 Basic Settings for 3. 72/84 PUBLIC 07/12/2010 . More Information In SAP Solution Manager.2 Basic Settings for Processing Sales Orders This section of the SAP Solution Manager structure contains the process documentation. Before you carry out the configuration steps contained in this section.0 Basic Settings for Plan-Driven Procurement . To change the client in your logical system. ensure that you have already completed the basic settings for Service Procurement or Plan-Driven Procurement. by choosing Configuration SAP SRM 7. by choosing Configuration SAP SRM 7. Note If you are configuring the Service Procurement business scenario. and configuration information for the business process Processing Sales Orders. you must switch to the SUS client before you define the SUS settings. They are only relevant for Plan-Driven Procurement. choose <project name> Plan-Driven Procurement . Create and send purchase order response (Supplier Self-Services) You can find a process description in SAP Solution Manager under <project name> Scenarios Plan-Driven Procurement with Supplier Integration Business Processes Processing Sales Orders in Supplier Self-Services .7 Service Procurement Classic Processing Sales Orders in Supplier Self-Services 3.1 Settings for Supplier Self-Services You must define the settings for supplier self-services (SUS) in the SUS client. run transaction SOLAR_PROJECT_ADMIN. you do not need to execute the back-end transactions.

Select the Documentation tab. 3.7. Create confirmation 2.8 Entering Services by Supplier The process Entering Services by Supplier consists of the following process steps: 1. Send confirmation You can find a process description in SAP Solution Manager under <project name> Scenarios Service Procurement Classic Business Processes Entering Services by Supplier .9 Entering Services in SAP ERP The process Entering Services in SAP ERP consists of the following process steps: 07/12/2010 PUBLIC 73/84 .8 Service Procurement Classic Entering Services by Supplier 3. select the Configuration tab.3 Configuration Content for Processing Sales Orders in SAP SUS Perform the following activities in Customizing for SAP SRM: n n n n n n n n n n SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Business Add-Ins (BAdIs) Master Data Extension for Duplication Check SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Cross-Application Basic Settings Settings for Documents Define Settings for Follow-On Documents for Inconsistent POs SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Business Add-Ins (BAdIs) SAP XML Interface Change Inbound SAP XML Mapping SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Business Add-Ins (BAdIs) Settings for Documents Version Control SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Business Add-Ins (BAdIs) Settings for Documents Changes to Purchasing Document Data SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Business Add-Ins (BAdIs) Settings for Documents Check Purchasing Document SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Business Add-Ins (BAdIs) Settings for Documents Download Documents SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Business Add-Ins (BAdIs) Settings for Documents Further Authorization Check for SRM Documents SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Business Add-Ins (BAdIs) Settings for Documents Carry out Activity During Saving SAP Implementation Guide SAP Supplier Relationship Management Supplier Self-Services Business Add-Ins (BAdIs) SAP XML Interface Change SAP XML Outbound Mapping 3.3 3. To find the process-related configuration content.

invoices can be entered with reference to a purchase order. the goods supplied or the service provided turn out to be defective or the price charged is too high. select the Configuration tab. Send invoice 3. can enter and process credit memos or subsequent debits/credits. 4. Select the Documentation tab. Create credit memo You can find a process description in SAP Solution Manager under <project name> Scenarios Plan-Driven Procurement with Supplier Integration Business Processes Processing Invoices by Supplier . As supplier or service provider. confirmation. Process service entry sheets Print and transmit service entry sheets Release collective service entry sheets Import CATS data You can find a process description in SAP Solution Manager under <project name> Scenarios Service Procurement Classic Business Processes Entering Services in SAP ERP . 3. or contact person before they are sent to the customer. following a purchase order. 74/84 PUBLIC 07/12/2010 . 2. Processing Invoices by Supplier Process documentation You can use this business process to display and process invoices in Supplier Self-Services (SUS). If.10 Processing Invoices by Supplier 1. shipping notification. 3. supplier. In SUS. Enter invoice in SUS 2.3 Service Procurement Classic 3. you as an internal employee. or service provider. Select the Documentation tab.10 Processing Invoices by Supplier The process Processing Invoices by Supplier consists of the following process steps: 1. To find the process-related configuration content. all invoices or processes must be approved by an internal employee.

Create credit memo (SUS) 3. Create or process invoices in background Release invoice System triggers prepayment in background Cancel invoice Transmit invoice View list display of invoices Perform revaluation You can find a process description in SAP Solution Manager under <project name> Scenarios Plan-Driven Procurement with Plant Maintenance Business Processes Verifying Logistics Invoices in Background . Enter invoice in SUS 2. 6. 2.11 Verifying Logistics Invoices in Background The process Verifying Logistics Invoices in Background consists of the following process steps: 1. Send Invoice (SUS) 3. Select the Documentation tab. 4. 5.11 Verifying Logistics Invoices in Background Process Figure 1: 1.3 Service Procurement Classic 3. 3. 07/12/2010 PUBLIC 75/84 . 7.

Transmit invoices You can find a process description in SAP Solution Manager under <project name> Scenarios Plan-Driven Procurement with Plant Maintenance Business Processes Processing Evaluated Receipt Settlements (ERS) in ERP . Park invoice Create or process invoices in background Release invoice Cancel invoice Transmit invoice View list display of invoices Perform Revaluation You can find a process description in SAP Solution Manager under <project name> Scenarios Plan-Driven Procurement with Plant Maintenance Business Processes Verifying Logistics Invoices Online . n Communication errors are avoided. ERS has the following advantages: n Purchasing transactions are closed more quickly. the vendor creates no invoice for an ordering transaction. 2. instead you post it on the vendor’s behalf based on information contained in purchase orders and goods receipts.12 Verifying Logistics Invoices Online 3. 4. 3. When you use evaluated receipt settlement (ERS). Select the Documentation tab. Monitor evaluated receipt settlements 3. n There are no price or quantity variances in Invoice Verification.3 Service Procurement Classic 3. 5. Procedure The following business process runs in SAP SRM: 76/84 PUBLIC 07/12/2010 . Perform evaluated receipt settlements 2.1 Processing Evaluated Receipt Settlements (ERS) in ERP You can use this business process to settle goods receipts automatically. Select the Documentation tab. 6. 7. 3. 3.13 Processing Evaluated Receipt Settlements (ERS) in ERP The process Processing Evaluated Receipt Settlements (ERS) in ERP consists of the following process steps: 1.13.12 Verifying Logistics Invoices Online The process Verifying Logistics Invoices Online consists of the following process steps: 1.

Monitor evaluated receipt settlements.0 Basic Settings for Service Procurement Analytics n For Strategic Sourcing (including variants Strategic Sourcing with RFx and Strategic Sourcing with Live Auction): <project name> Configuration Structures SAP SRM 7.0 Basic Settings for Self-Service Procurement Analytics n For Plan Driven Procurement (all scenario variants): <project name> Configuration Structures SAP SRM 7.15 Where to Find the Relevant Configuration Documentation You can find the configuration information for this process in SAP Solution Manager under the following paths: n For Self Service Procurement (all scenario variants): <project name> Configuration Structures SAP SRM 7.0 Basic Settings for Plan Driven Procurement Analytics n For Service Procurement (all scenario variants): <project name> Configuration Structures SAP SRM 7. 3.14 Analyzing Service Procurement 1.0 EHP1 Basic Settings for SAP SRM Basic Settings for Analytics .16 Reports in Service Procurement This section outlines the Service Procurement reports. 07/12/2010 PUBLIC 77/84 .14 Analyzing Service Procurement The process Analyzing Service Procurement consists of the following process steps: n System collects data n View reports n Work with reports You can find a process description in SAP Solution Manager under <project name> Procurement External Staffing Business Processes Analyzing Service Procurement . Prerequisites You have performed all the required configuration steps in SAP Solution Manager under <project name> Configuration SAP SRM 7.0 Basic Settings for Strategic Sourcing n For Contract Management: <project name> Configuration Structures SAP SRM 7. Perform evaluated receipt settlements. Scenarios Service 3.3 Service Procurement Classic 3. Transmit invoices.0 Basic Settings for Contract Management Analytics 3. 3. 2.

Delivery Date Delivery Delays Document count . shopping carts Excessive Invoices Goods and Services Confirmations per Document Number Invoice Document Overview Invoice Status Invoices per Contract Invoices per Invoice Number with Items Invoices per Product / Product Category Invoices per Vendor Key Performance Indicators Maverick Buying Analysis Number of Suppliers per Country Number of categories where PO value w/o contract >X Number of suppliers by category Open Approvals: Confirmations Open Items (Confirmations) Open Items (Invoices) Open Items Confirmations Overview of Purchase Order Value per Requester Overview of Return Deliveries Query Name 0SR_PO_C1_Q0006 0SR_MC02_Q2001 0SR_C02_Q0002 0SR_PO_C1_Q0005 0SR_MC02_Q0006 0SR_MC01_Q0715 0SR_MC02_Q3002 0SRCF_D2_Q0001 0SR_MC02_Q3001 0SRIV_D3_Q0003 0SRIV_D3_Q0005 0SRIV_D3_Q0004 0SRIV_D3_Q0002 0SRIV_D3_Q0001 0SR_MC01_Q0004 0SR_MC02_Q0002 0SR_MC01_Q0006 0SR_MC01_Q0711 0SR_MC01_Q0709 0SRCF_D2_Q0003 0SR_MC02_Q2002 0SR_PO_C1_Q0003 0SR_PO_C1_Q0002 0SR_C02_Q0001 0SRCF_D2_Q0004 Pareto Analysis According to PO Volume per Category 0SR_MC02_Q0005 78/84 PUBLIC 07/12/2010 . Query Description Accepted Purchase Order Quantities per PO and Item Confirmation Document Overview Cost Center Overview Deadline Monitoring .16 Reports in Service Procurement Procedure Ensure that all the correct business content for this scenario is installed and activated.3 Service Procurement Classic 3. The queries for the Service Procurement scenario are listed here.POs.Current Values for Req. See the documentation under the above path to locate the data sources and Operational Data Store (ODS) objects you want to install.

Order Value Workload per Purchasing Group Purchase Order Status 0SR_MC02_Q0001 0SR_C01_Q0001 0SRAC_D4_Q0002 0SRAC_D4_Q0004 0SR_C02_Q0003 0SRCF_D2_Q0002 0SR_PO_C1_Q0004 0SR_MC02_Q0003 0SRAC_D4_Q0001 07/12/2010 PUBLIC 79/84 .3 Service Procurement Classic 3.16 Reports in Service Procurement Pareto Analysis According to Purchase Order Volume 0SR_MC02_Q0004 (Chart) Purchase Order Document Analysis Purchase Order Values per Procurement Card Purchase Orders per Order Number with Items Purchase Orders per Product /Product Category Purchase Values per Order Status of Goods and Services Confirmation Documents Variance Invoice Value .

pushbutton labels.sap. for example. “Enter your <User Name>”. menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note. for example. database table names. and names of installation. for example. screen titles. program names. messages n Source code or syntax quoted directly from a program n File and directory names and their paths.com /example 123456 Example Example EXAMPLE EXAMPLE 80/84 PUBLIC 07/12/2010 . Arrows separating the parts of a navigation path. and database tools Technical names of system objects. These include report names. menu names. and menu options. names of variables and parameters. for example. SELECT and INCLUDE Keys on the keyboard Example Example Example Example http://www. for example. transaction codes. These include field labels. SAP Note 123456 n Words or characters quoted from the screen. n Cross-references to other documentation or published works n Output on the screen following a user action.Typographic Conventions Example <Example> Description Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system. upgrade. and key concepts of a programming language when they are surrounded by body text.

and PowerPoint are registered trademarks of Microsoft Corporation. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. ICA. DB2 Connect. S/390. WinFrame. BladeCenter. XHTML and W3C are trademarks or registered trademarks of W3C®.. POWER6. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Nothing herein should be construed as constituting an additional warranty.sf. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only. IBM.1 Gamma and XSLT processor SAXON 6. XSLT version 1. POWER6+. VideoFrame. System p. X/Open. WebSphere. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. System z10. the Adobe logo. z/OS. i5/OS. Redbooks. All other product and service names mentioned are the trademarks of their respective companies. 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. and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Linux is the registered trademark of Linus Torvalds in the U. OSF/1. World Wide Web Consortium. Program Neighborhood. POWER. AS/400. UNIX. RACF. System z9. Inc. MVS/ESA.sap. All rights reserved. Oracle is a registered trademark of Oracle Corporation. DB2 Universal Database. PowerVM. Intelligent Miner. These materials are subject to change without notice. RETAIN. POWER5.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. Massachusetts Institute of Technology. iSeries. MetaFrame. S/390 Parallel Enterprise Server. Windows. This document was created using stylesheet 2007-12-10 (V7. if any.S. eServer. Parallel Sysplex. POWER5+. xApps. OS/400. OS/2. DB2. and other countries. GPFS. System p5. pSeries. HTML. Adobe. The information contained herein may be changed without prior notice. PartnerEdge. System i5. 07/12/2010 PUBLIC 81/84 .com © Copyright 2010 SAP AG. and MultiWin are trademarks or registered trademarks of Citrix Systems. and SAP Group shall not be liable for errors or omissions with respect to the materials. Java is a registered trademark of Sun Microsystems. PowerPC. PostScript. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Outlook. xApp. Netfinity. Power Architecture. Inc.net/). Citrix. XML. System x. xSeries. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. Acrobat. System z. used under license for technology invented and implemented by Netscape. ByDesign. z9. Inc. AIX. HACMP. Microsoft. System i. z/VM. SAP NetWeaver. SAP Business ByDesign.5.2) / XSL-FO: V5. BatchPipes. SAP. Excel.2 from Michael Kay (http://saxon. National product specifications may vary. System Storage. and Motif are registered trademarks of the Open Group. R/3. Data contained in this document serves informational purposes only. zSeries. z10. OS/390. Duet. without representation or warranty of any kind. JavaScript is a registered trademark of Sun Microsystems. OpenPower.

com/srm-inst 82/84 PUBLIC 07/12/2010 . Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited. as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.sap. Documentation in the SAP Service Marketplace You can find this document at the following address: http://service.Disclaimer Some components of this product are based on Java™.

This page is left blank for documents that are printed on both sides. .

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.com © Copyright 2010 SAP AG. . All rights reserved.sap. 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.