SAP Enhancement Package 2 for SAP Supplier Relationship

SAP Enhancement Package 2 for SAP Supplier Relationship Management 7.0: Strategic SourcingSAP Enhancement Package 2 for SAP Supplier Relationship Management 7.0: Strategic Sourcing Based on SAP Solution Manager Content
Target Audience System Administrators Consultants
PUBLIC Document version: 1.0 – 2011-11-08
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
2.1 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.1 Sourcing Scenario with SAP Business Suite 7 . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.2 Define Technical Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.2.1 Defining Technical Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.3 Define Communication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.4 Import Business Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.4.1 Importing Business Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.4.2 More Information About Importing Business Scenarios . . . . . . . . . . . . . . . . . 14
2.2.5 Check Integration Scenario and Related Interfaces . . . . . . . . . . . . . . . . . . . . . 14
2.2.5.1 Checking Integration Scenario and Related Interfaces . . . . . . . . . . . . . . . . . . . 14
2.2.5.2 More Information About Checking Integration Scenario and Related
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3.1.2 More Information About System Connections . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.2 Define Number Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.2.1 Defining Number Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.2.2 More Information About Defining Number Ranges . . . . . . . . . . . . . . . . . . . . 18
2.3.3 Define Transaction Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.3.1 More Information About Defining Transaction Types . . . . . . . . . . . . . . . . . . . 18
2.3.3.2 Making Settings for RFxs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.4 Influence Message Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3.5 Create Payment Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3.5.1 Creating Payment Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3.5.2 More Information About Creating Payment Conditions . . . . . . . . . . . . . . . . . 20
2.3.6 Define Output Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2011-11-08 PUBLIC 3/130
2.3.6.2 Setting Up Bidder Notification Using Smart Forms . . . . . . . . . . . . . . . . . . . . . 21
2.3.6.3 More Information About Defining Output Settings . . . . . . . . . . . . . . . . . . . . . 21
2.3.7 Set Up File Upload/Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3.7.1 Setting Up File Upload/Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3.7.2 Making Settings for Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3.7.3 Uploading and Downloading Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3.7.4 More Information About Setting Up File Upload/Download . . . . . . . . . . . . . . 24
2.3.8 Define Customer Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3.9 Organizational Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.9.1.1 Configuration of the Organizational Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.9.2 Adjust Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3.9.2.2 Adjusting Roles for External Business Partners and Contacts . . . . . . . . . . . . . 26
2.3.9.3 Process User Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.3.9.3.1 Maintaining the User Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.3.9.3.2 More Information About Processing User Attributes . . . . . . . . . . . . . . . . . . . . 28
2.3.10 Open Partner Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.3.10.1 Making Settings for OPI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.3.10.2 More Information About Making Settings for OPI Configuration . . . . . . . . . . 29
2.3.11 Workflow Settings for Business Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.3.11.1 Set Up Workflow for Business Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.3.11.2 Setting Up Application-Controlled Workflow for Strategic
Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4 Settings for the Sourcing Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.4.1 Overview of Settings for the Sourcing Application . . . . . . . . . . . . . . . . . . . . . . 33
2.4.2 Define Sourcing for Product Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.4.2.1 Overview About Defining Sourcing for Product Categories . . . . . . . . . . . . . . . 34
2.4.2.2 More Information About Defining Sourcing for Product
Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.4.4 Integration with SAP ERP 6.0 EHP 4 Onwards . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.4.4.1 Configuration in SAP ERP 6.0 SAP Enhancement Package 4 . . . . . . . . . . . . . . . 35
2.4.4.2 Direct RFx Creation from ERP Using CPPR . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.4.4.2.1 Direct RFx Creation from SAP ERP into SAP SRM for Centralized
Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.4.4.2.3 More Information About Direct RFx Creation from ERP Using
CPPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.5.1 Overview of Sourcing with Auction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.5.2 More Information About Installing Live Auction Cockpit . . . . . . . . . . . . . . . . 38
2.5.3 Settings for Auctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.5.3.1 Activating ICF Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.5.3.2 Defining a Web Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.5.3.3 Live Auction Properties: Overview and Modifications . . . . . . . . . . . . . . . . . . . 41
2.5.3.3.1 JCo Property Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.5.3.3.2 JCo Client Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.5.3.3.3 JCo Message Server Client Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.5.3.3.4 JCo Pool Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.5.3.3.5 More Information about Configuring SAP User Management Engine for SAP
Internet Transaction Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.5.3.3.7 Modifying Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.5.3.5.1 Creating HTTP Connections to an External Server Behind the
Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.5.3.5.3 Server Name and IP Address Behind the Firewall . . . . . . . . . . . . . . . . . . . . . . . 51
2.5.3.6 Enabling Auctions in Java Outside the Firewall . . . . . . . . . . . . . . . . . . . . . . . . 52
2.5.3.6.1 Creating HTTP Connections to an External Server Outside the
Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.5.3.6.3 Server Name and IP Address Outside the Firewall . . . . . . . . . . . . . . . . . . . . . . 54
2.5.3.7 Enabling Auctions in ABAP Outside the Firewall . . . . . . . . . . . . . . . . . . . . . . . 54
2.5.3.7.1 Creating HTTP Connections to an External Server Outside the
Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.5.3.7.3 Server Name and IP Address Outside the Firewall . . . . . . . . . . . . . . . . . . . . . . 54
2.5.3.7.4 Defining Settings to Allow Access to Live Auction using the SAP NetWeaver
or NetWeaver Business Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.5.3.8 Defining Number Ranges for Auctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.5.3.9 Copying Customizing Settings from the Default Client . . . . . . . . . . . . . . . . . . 57
2011-11-08 PUBLIC 5/130
2.5.3.10 Server Name and IP Address Outside the Firewall . . . . . . . . . . . . . . . . . . . . . . 54
2.5.3.11 LAC Smoke Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.5.3.11.1 Smoke Testing User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.5.3.11.2 Smoke Testing the LAC Applet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.5.3.11.3 More Information about Live Auction Cockpit Smoke Tests . . . . . . . . . . . . . . 61
2.5.3.12 Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.5.3.13.2 Configuring the Applet for Double-Byte Languages for Windows . . . . . . . . . . 63
2.5.3.13.3 Configuring the Applet for Double-Byte Languages for UNIX . . . . . . . . . . . . . 64
2.5.3.14 More Information about Creating a New Archive File with Images . . . . . . . . . 64
2.5.3.15 Managing Live Auction Cockpit Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.5.3.16 Configuring the Applet to Run with Reverse Proxy . . . . . . . . . . . . . . . . . . . . . 72
2.5.3.17 Monitoring Live Auction Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
2.5.3.18 Activating GRMG Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.5.3.19 Verifying the GRMG Availability Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . 75
2.5.3.20 More Information about Configuring SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . 79
2.5.3.21 Making Settings for Live Auctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
2.5.3.22 Configuring Live Auction Cockpit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
2.5.3.23 More Information About Settings for Auctions . . . . . . . . . . . . . . . . . . . . . . . . 80
2.5.3.24 More Information about Uninstalling Live Auction Cockpit . . . . . . . . . . . . . . 80
2.5.3.25 Configuring Live Auctions Using RFx Responses Created Behind the
Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
2.6 Creation of Follow-On Documents for Strategic Sourcing . . . . . . . . . . . . . . . 82
2.7 Processing Collaborative Bidding Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
2.8 Integration with Other Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
2.8.1 Make Settings for SAP PLM cFolders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
2.8.1.1 cFolder Settings for SAP SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
2.8.1.2 Creating a Requirement from an Existing cFolders Collaboration . . . . . . . . . . 86
2.8.1.3 Integration with SAP PLM cFolders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
2.8.1.4 More Information About Settings for SAP PLM cFolders . . . . . . . . . . . . . . . . . 88
2.8.2 Make Settings for Supplier Self-Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
2.8.2.1 Integrating Supplier Self-Services with SAP Bidding Engine . . . . . . . . . . . . . . . 89
2.9 Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
2.9.1.1 Strategic Sourcing: Available Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
6/130 PUBLIC 2011-11-08
2.9.2 Settings for Strategic Sourcing with RFx and Auction . . . . . . . . . . . . . . . . . . . 91
2.9.2.1 Installing DataSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
2.9.2.2 More Information About Settings for Strategic Sourcing for RFx and
Auction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
2.9.3.1 Integrating SAP NetWeaver BI with SAP Bidding Engine . . . . . . . . . . . . . . . . . 93
2.9.3.2 Installing Business Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
2.9.3.3 Maintaining System IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
2.9.3.4 More Information About Settings for BI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Chapter 3 Strategic Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3.1 Strategic Sourcing with RFx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3.1.1 Processing Shopping Carts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3.1.1.1 Configuration Content for Processing Shopping Carts . . . . . . . . . . . . . . . . . . 99
3.1.2 Processing Purchase Requisitions in SAP ERP . . . . . . . . . . . . . . . . . . . . . . . . . 100
3.1.3 Searching for Sources of Supply Centrally . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
3.1.3.1 Configuration Content for Searching for Sources of Supply
Centrally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
3.1.5 Processing Bidding Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
3.1.5.1 Configuration Content for Processing Bidding Events . . . . . . . . . . . . . . . . . . 103
3.1.5.2 Defining Dynamic Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
3.1.5.3 Activating Adaptable RFx Response Handling . . . . . . . . . . . . . . . . . . . . . . . . 104
3.1.5.4 Configuring Tender Fee . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
3.1.5.5 Configuring Two-Envelope RFx Response . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.1.5.6 Configuring Multiparty Verification Process . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.1.5.7 Configuring Earnest Money Deposit (EMD) . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.1.5.8 Configuring Offline Bidding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.1.5.8.1 Defining Encryption and Digital Signature Settings . . . . . . . . . . . . . . . . . . . . 108
3.1.5.8.2 Defining Proxy Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
3.1.5.8.3 Defining User and User E-Mail ID Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
3.1.5.8.4 Configuring Adobe Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
3.1.5.8.5 Permitting Offline Bidding Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
3.1.5.8.6 Defining Condition-Dependent Document Output . . . . . . . . . . . . . . . . . . . . 110
2011-11-08 PUBLIC 7/130
3.1.5.8.8 Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
3.1.6.1 Processing Collaborative Bidding Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
3.1.7 Evaluating Bids/RFx Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
3.1.8 Processing RFx Responses in Supplier Self-Services . . . . . . . . . . . . . . . . . . . . 112
3.1.8.1 User Management for RFx Response Submission Outside Firewall . . . . . . . . 112
3.1.8.2 Transaction Data for RFx Response Submission Outside Firewall . . . . . . . . . 113
3.1.8.3 Technical Settings for RFx Response Submission Outside Firewall . . . . . . . . . 114
3.1.8.4 Replicating Master Data for RFx Response Submission Outside
Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
3.1.8.5 Configuring Live Auction for Submitting Bids Outside Firewall . . . . . . . . . . . 115
3.1.8.6 Starting Application Monitors for RFx Response Submission Outside
Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3.1.8.7 Setting Up Role for Using SAP NetWeaver Business Client (NWBC) in Supplier
Self-Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3.1.8.8 Configuring RFx Responses Outside the Firewall in the Purchaser
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
3.1.8.8.2 Replicating Master Data to the Supplier Self-Services (SUS)
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
3.1.8.9 Configuring RFx Responses Outside the Firewall in the Purchaser
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
3.1.8.9.2 Replicating Master Data to the Supplier Self-Services (SUS)
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
3.1.8.10.1 Configuring SOA Messages in Purchaser and Supplier Systems . . . . . . . . . . . 127
8/130 PUBLIC 2011-11-08
The configuration documentation for SAP Supplier Relationship Management (SAP SRM) is delivered
with the SAP Solution Manager content. To implement and configure SAP SRM, you must use SAP
Solution Manager, which contains the complete configuration documentation including links to
Customizing, SAP Notes, and SAP ERP documentation.
This guide contains only the SAP SRM configuration documentation and references to other
documentation. It provides you with a quick overview of the required SAP SRM configuration settings.
CAUTION
This guide is a supplement to the SAP Solution Manager content and does not replace it. The
complete configuration content and tool support is only available in SAP Solution Manager.
For more information on the SAP Solution Manager content, see SAP Note 1461039 and the SAP SRM
master guide at http://service.sap.com/instguides under Installation & Upgrade Guides SAP Business
Suite Applications SAP SRM SAP SRM Server 7.01 .
Business Functions
SAP enhancement package 1 for SAP Supplier Relationship Management 7.0 (SAP SRM 7.0) includes
the following business functions:
SRM, Strategic Sourcing Innovations
SRM, Analytics
For more information about these business functions, see SAP Help Portal at http://help.sap.com
SAP Supplier Relationship Management Business Functions and Customizing Switches .
1 Important Information About This Document
2011-11-08 PUBLIC 9/130
2 Basic Settings for Strategic Sourcing
2.1 SAP Notes
1268336 Business Suite 2008: Synchronous peer-to peer Services
1263876 SAP SRM: Configuration of Procure-to-Pay Scenario
2.2 SAP NetWeaver Process Integration
2.2.1 Sourcing Scenario with SAP Business Suite 7
In Business Suite 7, Sourcing is enhanced through the increased integration of SAP SRM 7.0 and SAP
ERP 6.0 SAP Enhancement Package 4.0. This tightly-integrated centralized sourcing process in Business
Suite 7 provides the following:
The ability to simplify centralized sourcing by aggregating demands from multiple back-end SAP
ERP systems into the central SAP SRM system
Online collaboration with suppliers
Easy identification of new suppliers
Reduced processing costs
Savings on time and sharper focus on strategic activities
Further information on the new features in Sourcing in SAP SRM 7.0 can be found in the release notes:
http://service.sap.com/releasenotes SAP Solutions SAP SRM .
For more information, see the SAP Service Marketplace at http://service.sap.com/srm-inst/
SAP SRM Server 7.0 Additional Configuration Material for SAP SRM 7.0 .
Section 2 of the document describes the Sourcing processes and configuration requirements in detail.
2.2.2 Define Technical Users
2.2.2.1 Defining Technical Users
In order for the Enterprise Services to communicate with the SAP NetWeaver Process Integration (SAP
NetWeaver PI), it is necessary to assign a technical user to the communication channel. We recommend
that you create this technical user as a service user and not as a dialog user. In addition to the Process
Integration (PI) role, this user should be assigned with the following additional SAP SRM roles :
2.1 SAP Notes
2011-11-08 PUBLIC 11/130
Remember to activate the role using the role maintenance transaction (PFCG).
Procedure
Create the service user using the user maintenance transaction (SU01) and assign the required roles.
2.2.3 Define Communication Settings
RFC Destinations (Display/Maintain) (SM59)
SLD API Customizing (SLDAPICUST)
Integration Engine - Administration (SXMB_ADM)
Test SLD Connection (SLDCHECK)
2.2.4 Import Business Scenarios
2.2.4.1 Importing Business Scenarios
In this section, you transfer the business scenario Strategic Sourcing from the SAP Integration
Repository, generate it, and activate it.
Prerequisites
You have done the following:
Defined the business systems for SAP Supplier Relationship Management (SAP SRM) and SAP ERP
in the SAP System Landscape Directory. For more information about SAP NetWeaver Process
Integration (SAP NetWeaver PI), see the SAP Service Marketplace at http://service.sap.com/
instguidesNW70
Imported the SAP NetWeaver PI content for SAP SRM into the SAP Integration Repository. See
SAP Note 836200
2. Choose Integration Builder: Configuration.
3. In the left pane, select the Objects tab.
4. Choose Service Without Partner Business System .
12/130 PUBLIC 2011-11-08
opens the wizard.
6. Choose Continue. The wizard guides you through the required steps.
7. Create the business system for both SAP SRM and ERP (you can bypass this step if the business
system is already set up).
8. Select a business system.
9. Create communication channels either manually or automatically. You can create them
automatically here. In this case, the systems are applied from the SAP System Landscape Directory
(SLD). Channels must be complete in terms of URLs and authentication information.
10. Choose Finish and then choose Close.
11. On the main screen, choose Tools Transfer Integration Scenario from Integration Repository . This opens
a wizard.
Basis/Global/IC and component SRM SERVER IC 7.01).
13. Choose Continue. The scenario name is SE_Sourcing_Enhancements.
14. Choose Finish and then choose Close. The Business Scenario Configurator opens automatically.
15. Select Component View. The Select Component View window opens.
16. Choose Apply.
17. Choose Assign Services. The Assign Services to Application Component window opens.
18. Press F4 to retrieve the available services.
19. Choose Assign.
22. Choose Configure Connections.
24. Press F4 in the Communication Channel field.
25. Select a communication channel. This channel must be of type XI.
NOTE
If the systems are applied from the SAP Landscape Directory, the Integration Builder
automatically creates the communication channels.
If the systems are not applied from the SAP Landscape Directory, you must create
communication channels manually. To do this, choose an existing service and then
choose Communication Channel using New context menu. You must assign a communication
channel for each connection.
27. Choose Generate to open the Create Configuration Objects window.
28. Choose Simulation, then choose Generate. In the list, Scope of Generation, select all items.
29. To generate a log, choose Start. Check the log for errors and save it if required.
2011-11-08 PUBLIC 13/130
30. In the Close Integration Scenario screen, choose Apply.
31. In the left pane, select the Scenarios tab; your scenario has been added.
32. In the left pane, select the Change List tab.
33. Expand the Standard Change List.
34. Right-click the scenario name SE_Sourcing_Enhancements and select Activate.
2.2.4.2 More Information About Importing Business Scenarios
The following SAP Note applies:
SAP Note 884695 Configuration of several integration scenarios
Run the following system transactions in SAP NetWeaver:
Start Integration Builder (SXMB_IFR)
HTTP Service Hierarchy Maintenance (SICF)
2.2.5 Check Integration Scenario and Related Interfaces
2.2.5.1 Checking Integration Scenario and Related Interfaces
In this section, you check the integration scenario to which the Strategic Sourcing business scenario is
assigned and the interfaces that are used for communication between SAP Supplier Relationship
Management and Materials Management. For the Strategic Sourcing business scenario, the
SE_Sourcing_Enhancements integration scenario provides the following interfaces, which you can
check in the Integration Builder:
SAP Supplier Relationship Management Direction Materials Management
PurchaseRequestERPSourcingRequest_In Asynchronous call (provider)
14/130 PUBLIC 2011-11-08
2. Choose Integration Builder: Configuration.
3. Under the Scenario tab, expand the scenario to display detailed information.
2.2.5.2 More Information About Checking Integration Scenario and Related Interfaces
Run the following system transaction in SAP NetWeaver:
Start Integration Builder (SXMB_IFR)
2.3.1.1 Defining RFC Destination and Back-End System
You must define RFC and back-end system settings to connect a back-end system to the SAP Supplier
Relationship Management (SAP SRM) system.
Prerequisites
Using the transaction SALE, you have defined a logical system for the back-end system.
For more information, see Customizing for SAP Supplier Relationship Management (SAP SRM)
under: SRM Server Technical Basic Settings ALE Settings Distribution (ALE) Basic Settings
Logical Systems Define Logical System .
To enable search help, you have created a second RFC connection for the same back-end system,
and you have made sure that the user is a system or dialog user.
Procedure
Activity Description For more information, see:
Defining the RFC destination SAP SRM communicates with the back-end system by means of RFC calls. Define the RFC destination for
your back-end system and an RFC user with sufficient authorization. As the user’s logon language from SAP SRM is used, you do not have to enter a logon language for the back-end system.
Define a second RFC connection for search help in the back-end system (for example, for account assignment).
Customizing for SAP SRM: SRM Server Technical Basic Settings Define RFC
Destinations For more information regarding authorization for the search help RFC connection, see SAP Note 656633 Search help requires dialog users.
2.3 General Settings
2011-11-08 PUBLIC 15/130
Customizing for SAP SRM: SRM Server Technical Basic Settings Define System
Landscape
Defining Back-End System
In the SAP SRM system, define the local and the back-end systems as follows:
1. Enter the logical system, destination and system type of the SAP SRM System. Define your SAP
SRM system as local if the logical system is your local SAP SRM system and if purchase orders,
confirmations, and invoices are to be created there.
2. Enter the logical system, destination, and system type of the back-end system and select the RFC
indicator if the logical system is RFC-compatible.
Defining RFC Destinations
1. Log on to SAP SRM.
2. Using transaction SM59, define an RFC destination for the back-end system.
3. Log on to your back-end system.
4. Using transaction SM59, define an RFC destination for SAP SRM.
Testing RFC Connection
2. Go to transaction SM59.
3. Under RFC destinations ABAP Connections , double-click the entry for your back-end system.
4. Choose Connection Test.
5. If the test was not successful, start by checking the entries under Technical Settings.
6. Choose Remote logon. This should cause a window to be opened in the back-end system. If this does
not happen, check the logon data to make sure that the correct user and password were entered.
In addition, check the authorization level of the user in the back-end system. You can also do this
by choosing menu path Utilities Test Authorization Test .
7. If remote logon was successful, you are now logged on to the back-end system. In this system, go
to transaction SM59 and, under RFC Destinations ABAP connections , double-click the entry for
the SAP SRM system. Test the connection and attempt remote logon.
Result
If a window is opened in SAP SRM, the connection is correct. If you are unable to establish a connection,
there are a number of possible causes for the error:
The entry for the system under Technical Settings (transaction SM59) is incorrect
The user or password was entered incorrectly
The specified user does not have the required level of authorization
16/130 PUBLIC 2011-11-08
The following SAP Note applies:
SAP Note 989263 Setting up connection between SSO and LAC
Perform the following activities in Customizing for SAP SRM:
SRM Server Technical Basic Settings Define RFC Destinations
SRM Server Technical Basic Settings ALE Settings Distribution (ALE) Basic Settings Logical Systems
Define Logical System
2.3.2 Define Number Ranges
2.3.2.1 Defining Number Ranges
You specify the number ranges for the following Strategic Sourcing documents in SAP Supplier
Relationship Management (SAP SRM):
RFxs
Auctions
Bids
Prerequisites
You have specified the number ranges for the following Materials Management documents in SAP
SRM:
Follow-on documents for each back-end system
You have also defined the number ranges for business partners in SAP SRM.
Procedure
Customizing Number Ranges in SAP SRM
1. In Customizing for SAP SRM, define number ranges by choosing SRM Server Cross-Application
Basic Settings Number Ranges SRM Server Number Ranges .
2. Choose every Material Management document mentioned above, for example:
Define Number Range for Local RFxs
Define Number Range for Local RFx Responses
Define Number Range for Auctions
2011-11-08 PUBLIC 17/130
SRM Server Cross-Application Basic Settings Number Ranges SRM Server Number Ranges Define Number
Ranges for Local RFxs
Ranges for Auctions
Ranges for Local RFx Responses
2.3.3 Define Transaction Types
Perform the following activity in Customizing for SAP SRM:
SRM Server Cross-Application Basic Settings Define Transaction Types
Run the following system transaction in SAP SRM:
Change Attributes (PPOMA_BBP)
1267549
1270412
2.3.3.2 Making Settings for RFxs
This section describes the settings you need to make in order to create an RFx in SAP Bidding Engine.
Procedure
1. Define the transaction type for RFxs by completing one of the following:
1. Make the settings you require in Customizing for Supplier Relationship Management, by choosing
SRM Server Cross-Application Basic Settings Define Transaction Types .
2. Using transaction PPOMA_BBP, define the transaction type for RFxs in the organizational
plan, and assign the attribute TEND_TYPE to the responsible user.
Optional
If you want to control the visibility and the ready-for-input field properties of the business object
document in screen, you can perform it using the customizing activities:
In Customizing, choose SRM Server Cross-Application Basic Settings Extensions and Field Control
(Personalization) Configure Field Control .
18/130 PUBLIC 2011-11-08
2.3.5 Create Payment Conditions
2.3.5.1 Creating Payment Conditions
Creating payment conditions
You can use this setting to define rules used by SAP SRM to determine payment conditions. When processing business documents, you want to select payment conditions via an input help, this step is mandatory. The input help comes from view BBPV_PTERM_LOCAL for local terms of payment and tables BBP_PAYTERM and BBP_PAYTERM_TEXT for back-end payment terms. The input help will display only those terms of payment that have a description in table BBP_PAYTERM_TEXT (back-end table T052U).
Customizing for SAP Supplier Relationship Management under SRM Server Cross-Application Basic Settings Create Payment Conditions
You can create payment conditions in one of the following ways:
Create local terms of payment manually in SAP SRM. Refer to the above-mentioned path in
Customizing. Alternatively, you can initially load the local terms of payment from one of your
back-end systems using report BBP_UPLOAD_PAYMENT_TERMS. Since the local terms use the
days/percentage values only, the result will be just a subset of all back-end terms.
Load terms of payment from all your back-end systems.
NOTE
Do not use report BBPGETVC. Run report BBP_UPLOAD_PAYMENT_TERMS instead.
When you use this report, not only the day/percentage values but the complete range (as
in tables T052/T052U) is uploaded from your back-end systems, and is stored in tables
BBP_PAYTERM and BBP_PAYTERM_TEXT, respectively.
2011-11-08 PUBLIC 19/130
SAP recommends that you change descriptions in the back-end system. There is no update
mechanism. Subsequent calls of the report will reload everything and overwrite any texts
manually entered in BBP_PAYTERM_TEXT.
SRM Server Cross-Application Basic Settings Create Payment Conditions
Run the following program in SAP SRM:
Transfer Payment Terms from Selected Back-end Systems (BBP_UPLOAD_PAYMENT_TERMS)
2.3.6 Define Output Settings
2.3.6.1 Defining Output Settings
To ensure that you can print RFxs, send them by e-mail, and fax them to bidders (as well as ensure that
bidders can receive RFxs), you must do the following:
Make printer settings for the users in your system
Maintain the e-mail address and fax number of your bidders in the Web interface of SAP Supplier
Relationship Management (SAP SRM)
Define the processing types and forms that are used to output documents
NOTE
see Customizing for SAP Supplier Relationship Management under SRM Server Business Add-Ins Document
Output Change Forms for Document Output .
Procedure
1. Make printer settings for the users in your system as follows:
1. Call transaction ppoma_bbp.
2. Select the users you require.
3. On the Attributes tab page, enter the value PRI for the attribute Default Printer.
2. Maintain the e-mail addresses and fax numbers of your bidders as follows:
1. On the Web interface of SAP SRM, choose Manage Business Partners.
2. Search for the bidders you require and enter their fax numbers and e-mail addresses.
3. Define the processing types and forms that are used to output documents:
1. In Customizing for SAP Supplier Relationship Management, choose SRM Server Cross-Application Basic
Settings Set Output Actions and Output Format Define Actions for Document Ouput .
20/130 PUBLIC 2011-11-08
2. Make settings as required for the following business objects:
BBP_PD_BID
BBP_PD_QUOT
BBP_PD_AUC
2.3.6.2 Setting Up Bidder Notification Using Smart Forms
SAP Bidding Engine provides bidders with information relating to RFxs, auctions, and bids in the form
of an e-mail. Using smart forms, you can design the information in your notification exactly the way
you want, without having to modify code.
NOTE
Smart forms can be used with printers, the Internet (using generated HTML output), faxes, or e-
mail.
For more information about smart forms, see SAP Solution Manager under <project name>
Configuration SAP SRM <release> Basic Settings for Strategic Sourcing General Settings Define Output
Settings or SAP Help Portal under SAP ERP <release> ERP Central Component SAP Library SAP
ERP Central Component Financials Incentive and Commission Management Administration Information
System Administration Correspondance in ICM Smart Forms
Prerequisites
You have made the basic technical settings for e-mails. For more information, see SAP Solution
Manager under <project name> Configuration SAP SRM <release> Basic Settings for SAP SRM
System Connections Technical Settings for E-Mail.
You have used the Business Add-In Change Smart Form for E-Mails Relating to Bids to design the smart
forms in accordance with your requirements (see below).
You have made printer, fax, and e-mail settings (as described in the document Defining Output
Settings [page 20]).
Procedure
Design your smart forms using the transaction SMARTFORMS. The default form is BBP_BIDINV_BID.
We recommend that you first copy this form as described in Customizing for SAP Supplier Relationship
Management under
SRM Server Business Add-Ins Document Output Change Forms for Document Output
2.3.6.3 More Information About Defining Output Settings
2011-11-08 PUBLIC 21/130
SRM Server Cross-Application Basic Settings Set Output Actions and Output Format Define Actions for
Document Output
CAUTION
This Customizing Activity has been updated for SRM 7.0 Enhancement Package 1. If you have
activated the Business Function SRM_SOURCING_1, double-check the Customizing of your
SAP SRM system.
SRM Server Business Add-Ins Document Output Change Forms for Document Output
Run the following system transactions in SAP SRM:
SAP Smart Forms (smartforms)
2.3.7 Set Up File Upload/Download
2.3.7.1 Setting Up File Upload/Download
When you are uploading and downloading files between systems, you must ensure that the decimal
notation settings in both systems are the same. In other words, you must have the same decimal notation
settings in your SAP Supplier Relationship Management (SAP SRM) Server and in the system where
you access the file offline.
You can also change the default value above which the system switches to background processing. In
the standard system, this value is 1000 and currently applies to download, upload and other
performance-critical processes within the following business objects:
BUS2000113 (Contract)
BUS2200 (RFx)
SOCO (Sourcing Cockpit)
Depending on whether you are downloading or uploading data, the system interprets the threshold
value differently:
When downloading a document, the system checks the number of items and switches to
background processing if the number of items has reached the threshold.
When uploading a document, the threshold refers to the number of items to be modified using
the upload file. These are the items where you have set the change indicator in the upload file.
When using Microsoft Excel to download and upload data, see SAP Note 734060 SRM: Up- and Download
of Documents using MS Excel.
22/130 PUBLIC 2011-11-08
1. Log on to your SRM Server system.
2. Choose Personalization User Account .
Make sure that field Decimal notation has the same value as the decimal notation setting of the system
(for example, your local PC) you are using for editing downloaded data.
NOTE
If the settings in both systems are not the same, the numbers in the downloaded or uploaded
file will display incorrectly.
(Optional)
1. Go to Customizing for SAP Supplier Relationship Management (SAP SRM) SRM Server Cross-Application
Basic Settings Define Threshold Value for Background Processing .
2. Change the threshold value for the relevant business object and save your entries.
2.3.7.2 Making Settings for Performance
You can make settings to improve performance when processing larger documents, for example,
documents with more than 500 line items.
You can set threshold values above which certain processes for contracts, RFxs, and bids are moved to
the background. These processes are as follows:
Contracts: Copy, Negotiate, Preview, Download, Upload, Change Currency
RFx: Copy, Create from Template, Create Purchase Order from Bid, Create/Update Contract from
Bid, Upload, Download
Auction: Upload, Download
Sourcing Cockpit: Create follow-on documents such as SRM contract, RFx, and Auction
Procedure
1. Go to Customizing for SAP Supplier Relationship Management (SAP SRM) SRM Server Cross-Application
Basic Settings Background Processing Define Threshold Value for Background Processing .
2. Choose New Entries.
3. Use the Object Type input help to choose the business transaction category you need.
4. Enter the number of items above which you want to have the processes run in the background.
For example, you can stipulate that the above processes for RFxs are to run in the background if
the RFx has more than 500 items.
5. Save your entry.
2011-11-08 PUBLIC 23/130
BUS2000113 (contract)
BUS2200 (RFx)
2.3.7.3 Uploading and Downloading Documents
You can transfer purchasing documents such as RFxs or contracts in a tabular file structure from your
SRM system to a local PC and back again. Using the Business Add-In (BAdI) Upload/Download SRM
Documents, you can change the selection and order of document data in the file to be up- or downloaded.
Procedure
To use the BAdI Download SRM Documents, go to Customizing for Supplier Relationship Management (SAP SRM)
and choose SRM Server Business Add-Ins Upload/Download SRM Documents.
More Information
SAP Note 734060 – SRM: Upload and Download of Documents Using MS Excel
SAP Note 734946 – SRM: Restrictions on Upload and Download
SAP Note 859049 – SRM 5.0: Restrictions for uploading and downloading
2.3.7.4 More Information About Setting Up File Upload/ Download
SRM Server Cross-Application Basic Settings Define Threshold Value for Background Processing
SRM Server Business Add-Ins Upload/Download SRM Documents
The following SAP Notes apply:
SAP Note 734060SRM: Upload and download of documents using MS Excel
SAP Note 812884How to change the fields used for Excel Up- and Download
SAP Note 673479Excel download: Quantities not displayed correctly
SAP Note 790860Frequently asked questions for Excel upload and download
2.3.8 Define Customer Fields
The following SAP Notes apply:
SAP Note 822424 CUF Customer fields cannot be changed in the bid
24/130 PUBLIC 2011-11-08
SAP Note 672960 User–defined fields 2
Run the following system transaction in SAP SRM:
ABAP Dictionary Maintenance (se11)
Customer Fields Define Customer Fields on Header Level
SRM Server Cross-Application Basic Settings Extensions and Field Control (Personalization) Configure
Customer Fields Define Customer Fields on Item Level
SRM Server Cross-Application Basic Settings Extensions and Field Control (Personalization) Create Table
Extensions and Supply with Data Define Customer Table Extensions on Header Level
SRM Server Cross-Application Basic Settings Extensions and Field Control (Personalization) Create Table
Extensions and Supply with Data Define Customer Table Extensions on Item Level
2.3.9 Organizational Configuration
You find the relevant configuration steps for configuring the organizational plan in SAP Solution
Manager under <project name> Configuration SAP SRM <release> Basic Settings for SAP SRM
Organizational Management .
Documentation
HR: Set Up Central Person (OO_CENTRAL_PERSON)
Integration Business Partner and Organizational Management (BBP_BP_OM_INTEGRATE)
Programs
Customizing Objects
2011-11-08 PUBLIC 25/130
2.3.9.2.1 Adjusting Roles for Internal Employees
To enable you to use the bidding functions of SAP Bidding Engine, you must maintain the roles
responsible for RFxs and RFx responses.
CAUTION
If you copy one of the roles delivered by SAP, you need to maintain attribute access rights by role.
In Customizing for SAP Supplier Relationship Management (SAP SRM), choose SRM Server Cross-
Application Basic Settings Roles Maintain Attribute Access Rights by Role .
The following roles are relevant:
/SAPSRM/OP_PURCHASER Operational Purchaser
/SAPSRM/ST_PURCHASER Strategic Purchaser
1. Go to transaction PFCG.
2. Enter the name of the required role (for example, /SAPSRM/OP_PURCHASER) or choose Views
and select a role from the list.
3. Choose Change role.
CAUTION
You can only maintain the role when you are logged on in the original language for the role.
4. On the Authorizations tab page, choose Change Authorization Data.
5. Correct the authorization objects have the status Incomplete (or are displayed in yellow).
6. Select Generate ( Shift+F5 ).
7. Save your changes.
8. Use transaction SU01 in the SRM server to assign the role to SRM user.
2.3.9.2.2 Adjusting Roles for External Business Partners and Contacts
Procedure
You create supplier companies or bidder contacts and assign them the role /SAPSRM/SUPPLIER. If you
want to allow those external users to participate in Strategic Sourcing events such as RFx or auctions,
you must also assign the role /SAPSRM/BIDDER to these users.
1. Go to transaction PFCG.
2. Enter the name of the required role (for example, /SAPSRM/SUPPLIER) or choose Views and select
a role from the list.
3. Choose Change role.
26/130 PUBLIC 2011-11-08
CAUTION
You can only maintain the role when you are logged on in the original language for the role.
4. On the Authorizations tab page, choose Change Authorization Data.
5. Correct the authorization objects have the status Incomplete (or are displayed in yellow).
6. Select Generate ( Shift+F5 ).
8. Use transaction SU01 in the SRM server to assign the role to an external user.
2.3.9.3 Process User Attributes
Prerequisites
You have created the root node of the organizational plan.
Before managers can approve the creation of new user master records, they have been assigned
the manager role /SAPSRM/MANAGER.
To enable the Web application Change Attributes, you have assigned a change authorization to the
role responsible for changing the user attributes. See Customizing for SAP Supplier Relationship
Management under SRM Server Cross-Application Basic Settings Roles Maintain Attribute Access Rights
by Role .
Procedure
1. Specify values for the main user attributes using the transaction PPOMA_BBP, tab card Attributes.
For most attributes, you can do this using the Web application Change Attributes. Important attributes
include the following:
Product categories: The product responsibilities have to be set on the tab card Extended
Attributes (attribute PRCAT)
Systems: ACS, SYS
Document types: BSA
Contract transaction type: CT_PROC_TY
purchasing organization, or purchasing group) and the responsibilities of an organizational
unit (attributes PURCH_GRP, PURCH_GRPX, PURCH_ORG, PURCH_ORGX, RESP_PGRP,
RESP_PRCAT in the earlier SAP SRM releases)
Procurement attributes have to be set on the tab cards Function and Responsibility
Currency: CUR
2011-11-08 PUBLIC 27/130
Current ITS for an external partner and current ITS of user: In transaction PPOMA_BBP,
provide for all internal RFx / Auction users the link to the SRM server for the attribute EXT_ITS
and ITS_DEST. In addition, provide these attributes as well for the external Business Partners
(suppliers/bidders) in transaction PPOMV_BBP. These attribute settings are necessary in order
to provide the URL log-on link in the e-mail to the bidder.
Transaction type for RFxs created from Sourcing: TEND_TYPE
Default printer: This attribute is also used when adding bidders to an RFx or Auction. The
user can select an Output Medium. If Printer is selected, the system reads the default printer settings
from the user attributes: PRI
2. To make sure all attributes that are necessary for your business scenario have been specified, start
transaction BBP_ATTR_CHECK.
2. Execute the report for the relevant applications.
2.3.9.3.2 More Information About Processing User Attributes
SRM Server Cross-Application Basic Settings Organizational Management Change Organizational Plan
Perform the following transaction in SAP SRM:
EPP Organizational Model: Checks (BBP_ATTR_CHECK)
2.3.10 Open Partner Interface Configuration
2.3.10.1 Making Settings for OPI Configuration
The Open Partner Interface (OPI) allows you to integrate web-based lists of suppliers (supplier
directories) into SAP Supplier Relationship Management (SAP SRM) applications using intranet or
Internet connections. If a supplier directory supports the OPI, business partner data can be transferred
directly from the supplier list into the respective SAP SRM application. The communication between
the supplier list and the SAP SRM server is handled completely in the user’s Web browser and is entirely
HTTP-based.
Procedure
To link supplier directories from commercial providers with SAP SRM using the OPI, and to transfer
partner data as sources of supply into your SAP SRM system, perform the activities in Customizing for
SAP Supplier Relationship Management by choosing SRM Server Master Data Content Management Define
External Web Services .
28/130 PUBLIC 2011-11-08
CAUTION
To make a Web service accessible for individual users or for user groups, you must assign the Web
service as the value for the attribute CAT.
You do this in attribute maintenance (transaction PPOMA_BBP). The input help for this attribute
lists all the available Web services.
2.3.10.2 More Information About Making Settings for OPI Configuration
SRM Server Master Data Content Management Define External Web Services
SRM Server RFx Activate Temporary Contact Person Creation
2.3.11 Workflow Settings for Business Scenarios
2.3.11.1 Set Up Workflow for Business Scenarios
You use this process to set up the workflow for your business scenario. The configuration steps depend
on the workflow framework you use. SAP Supplier Relationship Management (SAP SRM) supports
the following workflow frameworks:
Process-controlled workflow framework
These are approval workflows based on SAP Business Workflow in which the modeled or configured
process, and not the application itself, controls the process flow. A unified workflow template is
used and a process is evaluated by way of a process schema containing a set of distinct process levels.
The Business Rule Framework (BRF) can be applied to control further the process flow.
The process-controlled workflow framework is the default framework in the SAP SRM system.
Application-controlled workflow framework
These are approval workflows based on SAP Business Workflow in which the application is in
control over the SAP Business Workflow templates. Multiple workflow templates can be used,
using defined start conditions.
The application-controlled workflow framework is the framework that was available in SAP SRM
5.0 and lower. It is only intended to be used if you are upgrading from SAP SRM 5.0 or lower and
you need to continue using your existing workflows.
For more information about the workflow frameworks, see SAP Help Portal at http://
help.sap.com under SAP Supplier Relationship Management Functions Business Workflow .
Prerequisites You have performed the basic workflow Customizing as described in SAP Solution Manager under
<project name> Configuration SAP SRM <release> Basic Settings for SAP SRM Cross-Application Settings
Business Workflow .
2011-11-08 PUBLIC 29/130
Perform the following steps:
Check which workflow framework is active in your system. To do so, go to Customizing for SAP
SRM under SRM Server Cross-Application Basic Settings Business Workflow Select Workflow
Framework . Select Show Current Settings and choose Execute.
If your workflow framework is the process-controlled workflow framework, you do not have
to perform any scenario-specific Customizing steps. All Customizing steps necessary for this
workflow framework are described in SAP Solution Manager under <project name> Configuration
SAP SRM <release> Basic Settings for SAP SRM Cross-Application Settings Business Workflow Process-
Controlled Workflow .
If your workflow framework is the application-controlled workflow framework, check
whether there is any workflow documentation specific to your scenario in addition to this
document in SAP Solution Manager. For example, you might have to activate certain workflow
templates, adjust the start conditions for the relevant workflows, or implement a Business Add-
In (BAdI). For general configuration information, see SAP Solution Manager under <project name>
Configuration SAP SRM <release> Basic Settings for SAP SRM Cross-Application Settings Business
Workflow Application-Controlled Workflow .
<project name> Configuration SAP SRM <release> :
Basic Settings for Service Procurement External Staffing Other Settings Workflow Settings for Business
Scenarios
Basic Settings for Strategic Sourcing General Settings Workflow Settings for Business Scenarios
Basic Settings for Contract Management General Settings Workflow Settings for Business Scenarios
2.3.11.2 Setting Up Application-Controlled Workflow for Strategic Sourcing
You have to perform some standard Customizing for application-controlled workflow. Workflows
WS79000010 and WS79000002 are especially relevant for accepting a bid.
Prerequisites
You have created your organizational structure. We recommend that you map your enterprise
structure at least at departmental level. See Creating the Organizational Plan [external document].
Before you can assign processors to standard tasks, you must have created the relevant users or
regenerated the roles, as appropriate. For more information, see Regenerating Role Profiles [external
document].
30/130 PUBLIC 2011-11-08
Procedure
1. In Customizing for SAP SRM, choose SRM Server Cross-Application Basic Settings Business Workflow
Application-Controlled Workflow Technical Configuration Perform Task-Specific Customizing .
2. Expand the SRM and the SRM-EBP folders.
3. Find folder SRM-EBP-WFL and choose Activate Event Linking for this folder. Activate the event linkage
for the following workflows:
WS10000223 (Approve new password)
WS10000192 (Approve new user)
WS10000209 (Bidder or supplier registration)
WS79000010 (Without approval for bid)
WS79000002 (One-step approval for bid)
WS14500026 (Without approval for publication of RFx and its change versions)
WS14500027 (One-step approval for publication of RFx and its change versions)
WS14500028) (n-Step approval for publication of RFx and its change versions)
WS14500044 (n-Step approval for supplier bid)
NOTE
To use workflow WS14500028, you must implement a Business Add-in (BAdI). For more
information, see Customizing for SAP SRM under SRM Server Business Add-Ins Business
Workflow Application-Controlled Workflow Determination of Approver for n-Step Dynamic Approval
Workflow .
CAUTION
You must set up the workflows WS79000010 and WS79000002 in any case, even if you do not
intend to use approval steps in your process. These workflows control the system behavior
after accepting a bid.
4. If you use the standard approval workflows, define the conditions under which the workflows are
started.
NOTE
The start conditions are shipped by SAP by default in such a way that the workflows are
executable. However, you can change the start conditions to fit your requirements. For more
information, see Customizing for SAP SRM under SRM Server Cross-Application Basic Setting
Business Workflow Application-Controlled Workflow Business Process Configuration Define Conditions
for Starting Workflows .
5. Assign processors to some standard tasks, as listed in the table below.
If you want a certain group of persons to be able to approve your work items, you must specify all
the possible processors for the task in question. For example, tasks TS10008069 and TS10008127 for
standard two-level approval and task TS10008126 for single-level approval. These tasks are normally
assigned to the manager role. If required, you can, however, specify these processors differently.
2011-11-08 PUBLIC 31/130
1. In Customizing for SAP SRM, choose SRM Server Cross-Application Basic Setting Business
Workflow Application-Controlled Workflow Technical Configuration Perform Task-Specific
Customizing .
2. Expand the SRM and the SRM-EBP folders.
3. Find folder SRM-EBP-WFL and choose Assign Agents for this folder.
Task/Description Used in Workflows Processor
TS10008054 Approve new password WS10000223 Manager role or general task
TS10008125 Approve new user WS10000192 Manager role or general task
TS10008109 Approve supplier or bidder WS10000209 Administrator or purchaser
TS14507922 Approval tasks in one-step approval of RFx
WS14500027 Manager role or general task
TS14507924 Approval task to insert in approval of RFx
TS41507925 Check RFx by reviewer WS14500023 Manager role or general task
TS14507928 Send RFx back to creator WS14500028 General task
TS14507930 Approval task to insert in approval of bid
TS148507935 Approval task in n-level approval of bid
TS14507937 Send bid back to creator WS14500044 General task
TS79007914 Approval task in one-step approval of bid
WS79000002 Manager role
For more information, see Technical Information on Standard Workflows [external document].
6. Specify who is to be authorized to change or insert the approver or reviewer.
You do this by specifying the possible processors in the workflow template, by accessing transaction
PFTC_CHG and then choosing Additional data Agent assignment Maintain .
This affects the following workflows in the SAP SRM system that are relevant to Strategic Sourcing:
WS14500026 Without approval for publication of RFx and its change versions
WS14500027 One-step approval of RFx
WS14500028 N-step approval of RFx
WS14500044 N-step approval of bid
WS79000002 One-step approval of bid
WS79000010 Auto approval of bid
Approvers or reviewers who can be inserted
Here, you specify who may be inserted as an approver or reviewer in the above workflows:
WS14500022 - Approval fragment to insert in approval of RFx
WS14500040 - Approval fragment to insert in approval of bid
32/130 PUBLIC 2011-11-08
RECOMMENDATION
We recommend that you restrict the processors (that is, the approvers/reviewers that can be
inserted) at this point, and specify the relevant workflow tasks and general tasks described in
the above table instead.
More Information
To troubleshoot when a workflow is not working as expected, see SAP Note 322526 Analysis for workflow
problems.
2.3.11.3 Making Settings for Workflow Starting Conditions
When you define conditions for starting workflows, you must make specific settings for the strategic
sourcing business scenario.
Procedure
Follow the instructions described in Customizing for SAP SRM under SRM Server Cross-Application
Basic Settings Business Workflow Application-Controlled Workflow Business Process Configuration Define
Conditions for Starting Workflows . Make sure that you define the workflows you require for business objects
BUS2200 (RFx) and BUS2202 (RFx Response).
2.4 Settings for the Sourcing Application
2.4.1 Overview of Settings for the Sourcing Application
If you want to activate sourcing for the shopping cart and external requirements from SAP ERP or
external systems, you can define the following for each product category:
Whether requirements will be processed in the sourcing application
Whether the system should transfer approved requirement items to the purchaser's sourcing
application and, if so, which items
Whether, if a source of supply is missing, the system should automatically create an RFx
Whether requirements for items without a source of supply are grouped together in a purchase
order
Whether requirements are grouped together, but not sent to the sourcing application
Whether requirements for items without a source of supply are grouped together in an RFx
Prerequisites
You have set up the product category master data in the SAP SRM system.
You have defined the back-end systems for product categories. You do this using the following
Customizing activities:
2011-11-08 PUBLIC 33/130
for Product Category
in Backend System (Purch. Reqs, Reservations, Purch. Orders)
If you have activated Service Procurement, you have defined the service hierarchy templates for
the transaction types, as described in SAP Solution Manager under <project name> Configuration
SAP SRM <release> Basic Settings for Service Procurement Classic Activate Service Procurement Classic .
2.4.2 Define Sourcing for Product Categories
2.4.2.1 Overview About Defining Sourcing for Product Categories
You must specify either that the product category of the requirement is transferred to the sourcing
application or that the system always creates a RFx. In the standard, no requirements are transferred.
Procedure
Transaction Code SPRO
Customizing Path SAP Supplier Relationship Management SRM Server Sourcing Define Sourcing for Product Categories
Specify that requirements with the appropriate product categories are transferred to the sourcing
application:
Always
Only when a source of supply has not yet been assigned
Never
Configuring Sourcing to Always Create RFxs
Choose Automatic creation of RFx for items without source of supply in the Sourcing column.
Configuring Automatic Grouping for Sourcing
Choose Automatic grouping; sourcing for items without assigned source of supply in the Sourcing column.
If a source of supply is assigned to a requirement, the report BBP_SC_TRANSFER_GROUPED
automatically groups requirements together for the creation of a PO. If the requirement does not
have a source of supply, it appears in the worklist of the sourcing application for manual
assignment. Once you have assigned a source of supply, you can submit the requirement to the
report.
Choose Automatic grouping; sourcing is never carried out in the Sourcing column.
34/130 PUBLIC 2011-11-08
If a source of supply is assigned to a requirement, the report BBP_SC_TRANSFER_GROUPED
automatically groups requirements together for the creation of a PO. If the requirement does not
have a source of supply, an incomplete PO is created.
Choose Automatic grouping and creation of RFx item without source of supply in the Sourcing column.
If a source of supply is not assigned to a requirement, the report BBP_SC_TRANSFER_GROUPED
automatically groups requirements together for the creation of an RFx from several requirement
items.
SRM Server Sourcing Define Sourcing for Product Categories
SRM Server Business Add-Ins Sourcing Define Execution of Sourcing
SRM Server Business Add-Ins Sourcing Find and Check Sources of Supply
2.4.3 Start Automatic Grouping of Requirements
To start automatic grouping of requirements, run the following program in SAP SRM:
BBP_SC_TRANSFER_GROUPED
2.4.4.1 Configuration in SAP ERP 6.0 SAP Enhancement Package 4
Prerequisites
SAP enhancement package 4.0 for SAP ERP 6.0 business function LOG_MM_P2PSE_1 is ON.
Procedure
1. Access transaction SFW5 and expand node Enterprise Business Functions.
NOTE
You can access documentation about business function LOG_MM_P2PSE_1 in this transaction by
choosing the information icon under Documentation.
2011-11-08 PUBLIC 35/130
2.4.4.2 Direct RFx Creation from ERP Using CPPR
2.4.4.2.1 Direct RFx Creation from SAP ERP into SAP SRM for Centralized Sourcing
Using the Collective Processing of Purchase Requisitions (CPPR), you can create an RFx document
directly into the SAP SRM server, bypassing SAP SRM Sourcing.
NOTE
Prerequisites
You have completed the configuration steps in SAP Solution Manager for SAP SRM 7.0 under Basic
Settings for Plan-Driven Procurement Basic Settings for Plan-Driven Procurement with Plant Maintenance External
Requirement Integration Settings for External Requirements From ERP 6.0 EHP 4 Onwards .
Procedure
1. Access transaction SE19 and enter BADI Name BBP_EBPXML_OUT_BADI.
2. Choose Create Impl.
4. Under Defined filters, enter RFQ as a filter value.
5. Implement method REQUESTFORQUOTE.
6. Enter following code:
cv_system_type = 'ESASAPXML1'
This value is taken from table BBP_FUNCTION_MAP for ESOA system type.
2.4.4.2.2 Synchronous Services Configuration for Sourcing
You need to configure the synchronous Enterprise Services for bidder search help (RFx creation). In
Collective Processing of Purchase Requisitions (CPPR), the user can select bidders that will be assigned
to the RFx in SAP SRM. These bidders need to be queried from the SAP SRM system. Therefore, the
synchronous service operation
Prerequisites
You have completed the configuration steps in SAP Solution Manager for SAP SRM 7.0 under Basic
Settings for Plan-Driven Procurement Basic Settings for Plan-Driven Procurement with Plant Maintenance External
Requirement Integration Settings for External Requirements From ERP 6.0 EHP 4 Onwards .
36/130 PUBLIC 2011-11-08
RFQRequestSUITEAllowedBiddersByIdentifyingElementsQueryResponse service and of
1. Access transaction SOAMANAGER.
2. On the Application and Scenario Communication tab, choose Single Service Administration.
3. Search for the provider service in the Search tab, for example Bidders for
RFQRequestSUITEAllowedBiddersByIdentifyingElementsQueryResponse_In in SAP SRM.
4. Select the service from search results and choose Apply Selection.
5. In the Configurations tab, use the CREATE SERVICE action to create a Web service for this enterprise
service proxy.
6. Enter the name for service, description, and binding name.
For example, you could enter SRM_Bidders as the new service name, Bidders from SRM as the
description and SRM_Bidders as the new binding name.
7. Choose Apply Settings.
8. Under Transport Channel Authentication, choose the UserID/Password checkbox.
Authorization at Web service level is imposed. Only users who have access to the provider system
are able to access this Web service.
9. Save your entries.
10. On the Overview tab, choose Display Selected Binding's WSDL url and copy the wsdl address displayed in a
text area.
1. Access transaction SOAMANAGER.
2. On the Application and Scenario Communication tab, choose Single Service Administration.
3. Search for the consumer proxy, for example Bidders for
RFQRequestSUITEAllowedBiddersByIdentifyingElementsQueryResponse_Out in SAP ERP.
4. Select the consumer proxy from search results and choose Apply Selection.
5. In the Configurations tab, choose Create logical port.
6. Enter a logical port name description, such as LP_SRM_ERP_Bidders.
7. Select the check box Logical Port is Default.
8. Select configuration type WSDL Based Configuration.
9. Select Via HTTP access as the WSDL access settings.
10. Enter the WSDL address you copied during configuration of the provider system, and then enter
the WSDL access user and password that is used in the provider (SAP SRM) system to execute the
service.
2011-11-08 PUBLIC 37/130
11. Choose the Apply Settings pushbutton. The user should be a dialog or service user in the provider
system and should exist in the SAP SRM organizational plan. The user should have roles
SAP_BC_WEBSERVICE_CONSUMER assigned. To execute the underlying purchasing processes in SAP
SRM, the user should also have application roles (/SAPSRM/EMPLOYEE) assigned.
For more information, see SAP Note 1268336.
12. Save your entries.
2.4.4.2.3 More Information About Direct RFx Creation from ERP Using CPPR
Refer to SAP Note 1268336
Run the following transactions in SAP SRM:
SE19
SOAMANAGER
SOAMANAGER
For more information, see the documentation aboutSOA Manager in SAP Help Portal at http://
help.sap.com/saphelp_nw70/helpdata/EN/b0/787748cf3a4200bb1ba32a62aa8519/frameset.htm.
2.5.1 Overview of Sourcing with Auction
Beside using RFx for sourcing, you can also use auctions to determine the source of supply (that is,
supplier) for your requirement generated from your shopping cart and ERP purchasing requisition.
2.5.2 More Information About Installing Live Auction Cockpit
For more information about installing Live Auction Cockpit, see SAP Service Marketplace at http://
service.sap.com/instguides under SAP Business Suite Applications SAP SRM SAP SRM Server 5.0
Installation Guide: Live Auction Cockpit 2.0 . The following sections are particularly relevant:
Installation Step by Step
2.5 Sourcing with Auction
Activate the internet communication framework (ICF) services to enable external clients to
communicate with the ABAP server.
Prerequisites You have activated the Customizing switch Activate/Deactivate Live Auction on ABAP Server on the ABAP
server and you are configuring the Live Auction client.
Procedure 1. Start transaction SICF in the SAP Supplier Relationship Management (SAP SRM) system.
2. Enter SERVICE in the Hierarchy Type field.
3. Enter DEFAULT_HOST in the Virtual Host field.
4. Enter /sap/ in the Service Path field.
5. Enter LACMESSAGING in the Service Name field.
6. Choose execute (F8).
7. In the resulting screen, right click the node lacmessaging under hierarchy /default_host/sap/ and select
Activate Service from the context menu.
8. Repeat the steps above for the following services:
/default_host/sap/bc/bsp/sapsrm/bsp_dhtml_apple
/default_host/sap/bc/bsp/sapsrm/bsp_java_applet
2.5.3.2 Defining a Web Alias
To enable easy customization of the Live Auction Cockpit applet, the resource files are packaged
separately from the Web application itself. In order for the applet to retrieve its resources, the Web
server must make the resource files accessible through HTTP. You can enable this by creating a Web
alias for the directory that contains the resources. Without this alias, the applet cannot load properly.
Prerequisites The J2EE Engine is running.
Procedure
SAP NetWeaver Application Server Java 7.02 and 7.03
Use the following procedure for SAP NetWeaver releases up to (but excluding) SAP NetWeaver 7.3. The
procedure for SAP NetWeaver 7.30 is described below.
1. Open the J2EE Engine Administration tool.
EXAMPLE
On UNIX, browse to:
<INSTDIR>\usr\sap\<sapsid>\<instancenumber>\j2ee\admin\go.sh Port: 5<instance
number>04
2. Enter the J2EE Engine administrator password and choose Connect.
3. In the navigation pane, choose Server Services HTTP Provider .
4. Select the Runtime tab.
5. Select the Aliases tab.
6. Enter Alias: srm/lib/resources.
8. Choose Add.
NOTE
If you are using load balancing (that is, running Live Auction Cockpit on more than one Java
server) you must carry out the following steps:
1. On the central instance, share the srmla folder (<INSTDIR>:\usr\sap\<SAPSID>>\SYS
\global\srmla) for the dialog server user.
2. Maintain the alias for the dialog instance so that the path points to the shared folder on the
central instance.
Use the following procedure for SAP NetWeaver 7.30:
1. Go to the SAP NetWeaver Administrator using the following URL: http://<host>:<port>/nwa.
<host> is the host on which the SAP NetWeaver Application Server Java 7.30 is installed.
<port> is the HTTP port of the Internet Communication Manager (ICM). It has the following
format: 5<Java instance number>00.
2. Choose Configuration Infrastructure Java HTTP Provider Configuration Aliases .
3. Choose Add Alias.
5. Enter the path.
<INSTDIR>:\usr\sap\<SAP system ID>\SYS\global\srmla\resources
2.5.3.3 Live Auction Properties: Overview and Modifications
This section gives you an overview of the adaptable properties of the Live Auction Cockpit. It also
explains how to configure the properties.
JCo Property Settings [page 41]
JCo Client Settings [page 42]
JCo Message Server Cient Settings [page 43]
JCo Pool Settings [page 44]
More Information about Configuring SAP User Management Engine (UME) for ITS [page 45]
Other Property Settings for LAC [page 45]
Modifying Properties [page 45]
2.5.3.3.1 JCo Property Settings
SAP Java Connector (JCo) properties are listed in the following table, with default values provided
where required. You must optimize default values marked with an asterisk (*) to suit your system
requirements.
Property Name Description Default Value
jco.client.lang Creates a JCo pool with the specified value for the SAP logon language.
* English, EN German, DE Japanese, JA
jco.client.client SAP client -
jco.client.user Logon user
NOTE
You have to define this user in the SAP system as follows: User type: communication or system user
Roles assigned: Purchaser and Bidder
-
jco.client.r3name SAP ERP name -
jco.client.ashost SAP application server -
jco.client.sysnr SAP system number -
600,000 ms (10 minutes)
jco.poolmgr.maxwaittime The maximum length of time, in milliseconds, for the system to wait for a connection request when the pool is exhausted.
30,000 ms (30 seconds)
jco.poolmgr.timeoutcheckinterval The length of time, in milliseconds, after which all connections are periodically checked for time- outs.
60,000 ms (1 minute)
jco.pool.maxconn The absolute maximum number of connections that can be simultaneously opened for a given pool.
15*
jco.pool.maxpoolsize The maximum number of connections that can be kept open and managed in the pool.
10*
jco.performance.monitor Monitors the time it takes to run ABAP function modules and writes the statistics to the monitor log file. 0 = disabled 1 = enabled Log file: <INSTDIR>\usr\sap\<sapsid>\ <instanceNumber>\j2ee\cluster\server0\ log
\applications\sap.com\com. sap.srm.la
0*
jco.performance.monitor.interval The intervals, in milliseconds, at which the statistics for the execution times of ABAP function modules are written to the log file.
300,000 ms (5 minutes)
jco.pool.monitor Monitors the JCo pool and writes the statistics to the monitor log file. 0 = disabled 1 = enabled Log file: <INSTDIR>\usr\sap\<sapsid>\ <instanceNumber>\j2ee\cluster\server0\ log
\applications\sap.com\com.sap.srm.la
\srmlaLog-[n].log
300,000 ms (5 minutes)
2.5.3.3.2 JCo Client Settings
SAP Java Connector (JCo) properties that control the communication between the Live Auction applet
and the back-end SAP system are listed in the following table.
Property Name Description
Jco.client.client The number of the client on which the SAP Supplier Relationship Management (SAP SRM) application is running.
Jco.client.passwd NOTE
The password is not displayed. Instead, each character in the password is represented by an asterisk (*).
Jco.client.user JCo users must be assigned standard authorization objects, such as S_RFC, contained as part of the standard RFC user’s profile, and must have authorization to access the following function groups: BACV
NOTE
For connectivity between the UI and back-end system, the generic back-end user must be assigned the following roles: Purchaser Roles
EXAMPLE
A bidder role
SAP_BBP_STAL_BIDDER (which should include the profile containing the authorization object BBP_VEND)
In addition to these two types of roles, assign the additional authorization object, S_BTCH_ADMIN, to the RFC user profile to fully control the auction process.
2.5.3.3.3 JCo Message Server Client Settings
SAP Java Connector (JCo) properties that control group load balancing are listed in the following table.
NOTE
You need to provide either the application server settings or the group load balancing settings,
not both. However, if both settings are available, Live Auction Cockpit uses the application server
settings without load balancing as default.
Property Names Description
jco.client.ashost
jco.client.sysnr
SAP Java Connector (JCo) properties for creating pooled connections are listed in the following table.
RECOMMENDATION
We strongly recommend that you test your environment to determine the optimal values for
the three properties listed in the table below. To assist you in this task, you can also enable the
performance monitors, jco.performance.monitor and jco.pool.monitor, which write the
performance data to the log file for analysis.
Property Name Descriptions Recommended Settings
jco.pool.maxconn This value refers to the absolute maximum number of connections that Live Auction Cockpit can simultaneously open for each pool.
CAUTION
Live Auction Cockpit creates a pool for each supported SAP client. Therefore, in a multiple SAP client scenario, it is possible to have more than one pool.
This value has to be equal to or greater than the value for jco.pool.maxpoolsize. You have to set this value high enough to handle peak activity loads.
RECOMMENDATION
For 25 concurrent bidders, we recommend setting the value to 15.
jco.pool.maxpoolsize This value refers to the maximum number of pooled connections kept for reuse.
CAUTION
The difference between the value of jco.pool.maxconn and jco.pool.maxpoolsize is the number of connections that can be opened on the SAP system to perform a task and then disconnect. These connections are not reused and are therefore seen as expensive regarding system load.
You have to set this value high enough so that, under a typical system load, no additional connections are required.
RECOMMENDATION
For 25 concurrent bidders, we recommend setting the value to 10.
jco.client.lang This is an optional setting. When this value is set, a JCo pool is created with its value used as the SAP logon language. The value for this property must be a comma separated list of valid 2-letter SAP external language codes.
CAUTION
Ensure that the SAP Supplier Relationship Management system has a language installed for each of the corresponding language codes. On-the-fly connections, which are more resource-consuming than pooled connections, are created for
If you expect a large group of users to log on in different languages, we strongly recommend that you specify each of those languages in the property file. This enables the use of pooled connections and avoids the unnecessary use of multiple one-time connections. As a result of defining language values in the property file, a JCo pool is created to maintain connections for each language and client number combination. Therefore, we recommend that you also adjust the value for jco.pool.maxpoolsize accordingly.
44/130 PUBLIC 2011-11-08
Property Name Descriptions Recommended Settings users who log on with a language that is not listed in the property file.
2.5.3.3.5 More Information about Configuring SAP User Management Engine for SAP Internet Transaction Server
For more information about configuring SAP User Management Engine (SAP UME) for SAP Internet
Transaction Server (ITS), see SAP Service Marketplace at http://service.sap.com/instguides under
SAP Business Suite Applications SAP SRM SAP SRM Server 5.0 Installation Guide: Live Auction Cockpit 2.0
Configuring UME for ITS .
The following table lists some additional important configuration properties for the Live Auction
Cockpit (LAC) based on Java.
CAUTION
Do not configure the following properties when using Live Auction based on ABAP. These
properties are only relevant for Live Auction based on the Java.
Property Name Description Default Value
msg.client.protocol Overrides the default messaging protocol used by the Live Auction applet. This is useful when reverse proxies are used in the system landscape. If no value is specified, the default protocol is used.
Empty (no override)
msg.client.serverHost Overrides the default host name of the messaging server used by the Live Auction applet. This is useful when reverse proxies are used in the system landscape. If no value is specified, the default server host name is used.
Empty (no override)
msg.client.serverPort Overrides the default port number of the messaging server used by the Live Auction applet. This is useful when reverse proxies are used in the system landscape. If no value is specified, the default server port is used.
Empty (no override)
srmla.um Authentication of the User Management Engine (UME). 0 = disabled.
Empty (enabled)
Procedure
You can adapt Live Auction Cockpit properties as described in the following linked sections:
JCo Message Server Client Settings [page 43]
JCo Pool Settings [page 44]
Other Property Settings for LAC [page 45]
The SAP NetWeaver tools you can use to modify properties are described in the next sections. Use the
tool that fits your requirements.
Modifying Properties with the Configuration Adapter Service (SAP NetWeaver Application Server Java 7.02 and 7.03)
1. Stop the J2EE server.
2. Launch the J2EE engine Configuration Adapter Service.
On Windows: Go to usr\sa