config clm1.pdf

Configuration GuideIntegration of SAP ERP and SAP Sourcing OnDemand Wave 8

Target Audience ■ SAP ERP Experts, Consultants, and Key Users ■ SAP NetWeaver Process Integration (SAP NetWeaver PI) Experts and Consultants ■ SAP Sourcing Experts and Consultants ■ SAP Service Delivery Consultants ■ SAP Hosting ■ IT Network Experts

PUBLICDocument version: 1.1 – 2011-08-18

Document History

CAUTION

Before you start the implementation, make sure that you have the most recent version of this

documentation. You can find the most recent version on SAP Service Marketplace at http://

service.sap.com/eso.

The following table provides an overview of the most important document changes.

Version Date Description

1.0 2011-03-31 Initial version

1.1 2011-08-18 Corrected the PI path in the topic, “Import Process Integration Content to Integration Repository”

2/134 PUBLIC 2011-08-18

http://service.sap.com/eso


Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 General SAP Sourcing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.1 Create System Property is_sapint_installed . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.2 Check Integrated Document Types for RFx and Contract . . . . . . . . . . . . . . . . 15

2.3 Create RFx Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.4 Edit Integrated System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.5 Define Default Language Preferences for Localized Resource

Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.6 Edit Integrated Document Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.7 Create Scheduled Tasks to Import XML Messages for Materials, Vendors, and

RFx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 3 SAP NetWeaver Process Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.1 Set Up System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.2 Define RFC Destination and Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.3 Import Process Integration Content to Integration Repository . . . . . . . . . . . . 25

3.4 Configure Integration Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.5 Configure Communication Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 4 Master Data Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.1 Integration Architecture for Master Data Integration . . . . . . . . . . . . . . . . . . . 37

4.2 Create Cross-System Company Codes and Business Areas . . . . . . . . . . . . . . . . 39

4.3 Extract Customizing Data from SAP ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4.4 Carry Out Initial Load of Customizing Data to SAP Sourcing . . . . . . . . . . . . . 43

4.5 Define Logical System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.6 Maintain RFC Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.7 Maintain Port Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.8 Maintain Partner Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.9 Maintain Distribution Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4.10 Verify Transaction Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.11 Verify Value List Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

2011-08-18 PUBLIC 3/134

4.12 Verify Pricing Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4.13 Verify ISO Codes of Currencies, Units of Measure, and Countries . . . . . . . . . . 52

4.14 Verify Incoterms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4.15 Define External System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4.16 Define Vendor Account Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

4.17 Carry Out Initial Load of Materials and Vendors from SAP ERP to SAP

Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4.18 Transfer Changes to Materials or Vendors from SAP ERP to SAP

Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4.19 Publish Suppliers from SAP Sourcing to SAP ERP . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 5 Integration of Suppliers with Multiple SAP ERP Systems . . . . . . . . . . . . . 63

5.1 Enable Integration of Suppliers with Multiple SAP ERP Systems . . . . . . . . . . . 63

5.2 Define External System for Each SAP ERP System . . . . . . . . . . . . . . . . . . . . . . 63

5.3 Define Vendor Account Groups for Each SAP ERP System . . . . . . . . . . . . . . . 64

5.4 Configure Each SAP ERP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.5 SAP NetWeaver Process Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.5.1 Register Each SAP ERP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.5.2 Define RFC Destination and Port for Each SAP ERP System . . . . . . . . . . . . . . . 65

5.5.3 Import Each SAP ERP System from System Landscape Directory to

Integration Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.5.4 Send Supplier Master from SAP Sourcing to Multiple SAP ERP

Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.5.5 Send Vendor Master from Multiple SAP ERP Systems to SAP

Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Chapter 6 Business Process Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

6.1 SAP ERP RFQ to SAP Sourcing RFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

6.1.1 Integration Architecture for SAP ERP RFQ to SAP Sourcing RFP . . . . . . . . . . 71

6.1.2 Configure IDoc for RFQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

6.1.3 Configure RFQ Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

6.2 SAP Sourcing RFP Award to SAP ERP Purchase Order . . . . . . . . . . . . . . . . . . . 74

6.2.1 Integration Architecture for SAP Sourcing RFP Award to SAP ERP Purchase

Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

6.2.2 Define Item Text for Purchase Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

6.3 SAP Sourcing RFP Award or Master Agreement to SAP ERP Outline

Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

6.3.1 Create Pricing Conditions in SAP Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4/134 PUBLIC 2011-08-18

6.3.2 Assign Pricing Conditions in SAP Sourcing to Pricing Condition Types in SAP

ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

6.3.3 SAP Sourcing RFP Award to SAP ERP Outline Agreement . . . . . . . . . . . . . . . . 77

6.3.3.1 Integration Architecture for SAP Sourcing RFP Award to SAP ERP Outline

Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

6.3.3.2 Configure RFP Award to Transfer Pricing Conditions . . . . . . . . . . . . . . . . . . . 78

6.3.4 SAP Sourcing Master Agreement to SAP ERP Outline Agreement . . . . . . . . . . 79

6.3.4.1 Configure Master Agreement Type to Transfer Pricing

Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

6.3.4.2 Set Up Item Text IDs for Contract and Scheduling Agreement . . . . . . . . . . . . 80

6.3.4.3 Block Integrated Fields from User Changes in SAP ERP . . . . . . . . . . . . . . . . . . 81

Chapter 7 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.1 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.2 Mapping of Fields Between SAP ERP and SAP Sourcing . . . . . . . . . . . . . . . . . . 86

7.2.1 Mapping of Customizing Data from SAP ERP to SAP Sourcing . . . . . . . . . . . . 86

7.2.2 Mapping of Material Master Data from SAP ERP to SAP Sourcing . . . . . . . . . . 90

7.2.3 Mapping of Vendor Master Data from SAP ERP to SAP Sourcing . . . . . . . . . . 91

7.2.4 Mapping of Supplier Master Data from SAP Sourcing to SAP ERP . . . . . . . . . . 93

7.2.5 Mapping of SAP ERP RFQ to SAP Sourcing RFP . . . . . . . . . . . . . . . . . . . . . . . . 95

7.2.6 Mapping of SAP Sourcing RFP Award to SAP ERP Purchase Order . . . . . . . . . 103

7.2.7 Mapping of SAP Sourcing RFP Award to SAP ERP Outline

Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

7.2.8 Mapping of SAP Sourcing Master Agreement to SAP ERP Outline

Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

7.3 Sending Files and Customizing Data via FTPS Protocol . . . . . . . . . . . . . . . . . 125

7.4 Configuring SSL/HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

7.5 Publishing RFx to Different Subcontexts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

7.6 Extensions to Integration of SAP ERP and SAP Sourcing . . . . . . . . . . . . . . . . 130

2011-08-18 PUBLIC 5/134

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

1 Introduction

To deliver a closed-process loop and provide additional value on top of the value derived by core SAP

Sourcing functionality, you can integrate SAP Sourcing OnDemand wave 8 with the overall operational

sourcing and source-to-contract scenarios in the back-end SAP ERP system.

This guide assumes that you are integrating SAP Sourcing with SAP ERP before transactional data exists

in SAP Sourcing. After transactional data exists in SAP Sourcing, additional effort is required to integrate

SAP Sourcing with SAP ERP because of the need for subsequent analysis of transactional documents,

possible subsequent adjustments of the master data that is used in those documents, and subsequent

mass replication to SAP ERP.

If you have already integrated SAP E-Sourcing on-demand wave 6 or SAP Sourcing OnDemand wave

7 with SAP ERP, and want to upgrade to wave 8, follow the component upgrade guide for SAP Sourcing

OnDemand wave 8, and not this guide.

Prerequisites

Mandatory Components

The following table shows the mandatory components for the standard integration scenarios.

Mandatory Components for Standard Integration Scenarios

System Release

SAP ERP 6.0*

SAP Sourcing OnDemand Wave 8

SAP NetWeaver Process Integration (SAP NetWeaver PI) 7.0 or 7.1

* The standard integration components are delivered with support packages, as specified in the

following table.

SAP ERP Release and Support Package

SAP ERP Release Support Package

SAP ERP 6.0 18 or higher

SAP ERP 6.0 enhancement package 2 8 or higher




SAP ERP 6.0, SAP ERP 6.0 Enhancement Package 2, SAP ERP 6.0 Enhancement Package 3

If you do not want to upgrade to the specified support package, you can implement the standard

integration components via SAP Notes 1364669 and 1458469.

1 Introduction

2011-08-18 PUBLIC 7/134

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1364669&_NLANG=en&_NVERS=0


SAP ERP 6.0 Enhancement Package 4, SAP ERP 6.0 Enhancement Package 5

Integration of service line items requires SAP ERP 6.0 enhancement package 4 or higher. For other

constraints, see SAP Note 1527171.

If you do not want to upgrade to the specified support package, you can implement the standard

integration components via SAP Notes 1516322, 1509572, 1521005, and 1364357. For additional

corrections, see SAP Notes 1537841, 1528894, 1526807, and 1548521.

RECOMMENDATION

We recommend upgrading to the specified support package for SAP ERP 6.0 enhancement package

4 or higher because many manual steps are required to implement the standard integration

components via SAP Notes.

Required Experts

You must provide the following experts:

■ SAP NetWeaver PI expert or consultant to carry out the required changes in SAP NetWeaver PI

■ SAP ERP expert or consultant to carry out the required changes in SAP ERP

■ IT network expert to establish and test network connectivity

Integration

The following tables provide a list of all the tasks that are necessary to complete the integration, and

indicate who carries out each task. They also indicate the solutions for which a task is relevant; for

example, if you are integrating SAP ERP only with Supplier Management, you need to carry out only

the tasks that are listed as necessary for Supplier Management. You can also use the tables as checklists

to track tasks.

FTP Details

Task Carried Out By Necessary For Done

Provide FTP server details: ■ Host ■ IP ■ Account ■ Password ■ Directory structure

SAP Hosting Strategic SourcingContract Lifecycle Management (CLM)Supplier Management

Provide external IP of sending server [page 125]

Your IT network expert Strategic SourcingCLMSupplier Management

Open TCP ports 30000–40000 outbound [page 125]


Allow FTP access outbound from sending server to hosted FTP [page 125]


1 Introduction

8/134 PUBLIC 2011-08-18










General SAP Sourcing Configuration


Create system property is_sapint_installed [page 15]

SAP Service Delivery consultant

Strategic SourcingContract Lifecycle Management (CLM)Supplier Management

Check integrated document types for RFx and contract [page 15]


Strategic SourcingCLM

Create RFx template [page 17]

SAP Service Delivery consultantYour ERP expert or consultant

Strategic Sourcing

Edit integrated system configuration [page 17]


Strategic SourcingCLMSupplier Management

Define default language preferences for localized resource strings [page 18]



Edit integrated document configuration [page 19]



Create scheduled tasks to import XML messages for materials, vendors, and RFx [page 20]



SAP NetWeaver Process Integration (SAP NetWeaver PI)


Set up system landscape directory [page 23]

Your NetWeaver PI expert or consultant


Define RFC destination and port [page 24]



Import process integration content to Integration Repository [page 25]



Configure integration scenarios [page 25]



Configure SAP ERP communication channels [page 33]



Configure SAP Sourcing communication channels [page 33]



1 Introduction

2011-08-18 PUBLIC 9/134


Activate configuration scenario [page 33]



Provide SAP Certification Authority (SAP CA) trusted certificate(On SAP Service Marketplace at http://service.sap.com /tcs, choose SSL Server Certificates.)



Enter PI host in external DNS



Construct SAP NetWeaver PI URL



Configure SSL/HTTPS [page 126]



Master Data Integration


Create cross-system company codes and business areas [page 39]

Your ERP expert or consultant


Extract Customizing data from SAP ERP [page 41]

Your ERP expert or consultant / Your key user


Carry out initial load of Customizing data to SAP Sourcing [page 43]



Define logical system [page 44]



Maintain RFC destination [page 45]



Maintain port definition [page 46]



Maintain partner profile [page 47]



1 Introduction

10/134 PUBLIC 2011-08-18

http://service.sap.com/tcs



Maintain distribution model [page 48]



Verify transaction types [page 49]: ■ Purchase order ■ Contract ■ Scheduling

agreement

Your ERP expert or consultant / Your key userSAP Service Delivery consultant


Verify value list values [page 50]: ■ Vendor account

groups (only necessary for Supplier Management)

■ Header text IDs (only necessary for Strategic Sourcing and CLM): ● RFQs ● Purchase orders ● Contracts ● Scheduling

agreements ■ Item text IDs (only

necessary for Strategic Sourcing and CLM): ● RFQs ● Purchase orders ● Contracts ● Scheduling

agreements



Verify pricing conditions [page 51]



Verify ISO codes [page 52]: ■ Currencies ■ Units of measure ■ Countries



Verify Incoterms [page 54] Your ERP expert or consultantSAP Service Delivery consultant


Define external system [page 54]



1 Introduction

2011-08-18 PUBLIC 11/134

Task Carried Out By Necessary For DoneSAP Service Delivery consultant

Supplier Management

Define vendor account groups [page 55]

Your ERP expert or consultantSAP Service Delivery consultant

Supplier Management

Carry Out Initial Load of Materials and Vendors from SAP ERP to SAP Sourcing [page 57]



Transfer changes to materials or vendors from SAP ERP to SAP Sourcing [page 59]



Publish suppliers from SAP Sourcing to SAP ERP [page 61]


Supplier Management

The tasks in the following Integration of Suppliers with Multiple SAP ERP Systems table are necessary only if

you want to publish suppliers from SAP Sourcing to multiple SAP ERP systems, and vice versa. If you

are integrating SAP Sourcing with a single SAP ERP system, you can skip the Integration of Suppliers with

Multiple SAP ERP Systems table and proceed to the Business Process Integration table.

Integration of Suppliers with Multiple SAP ERP Systems


Enable integration of suppliers with multiple SAP ERP systems [page 63]


Supplier Management

Define external system for each SAP ERP system [page 63]


Supplier Management

Define vendor account groups for each SAP ERP system [page 64]


Supplier Management

Configure each SAP ERP system [page 64]


Supplier Management

Register each SAP ERP system [page 65]


Supplier Management

Define RFC destination and port for each SAP ERP system [page 65]


Supplier Management

Import each SAP ERP system from System Landscape Directory


Supplier Management

1 Introduction

12/134 PUBLIC 2011-08-18

Task Carried Out By Necessary For Doneto Integration Builder [page 65]

Send supplier master from SAP Sourcing to multiple SAP ERP systems [page 66]


Supplier Management

Send vendor master from multiple SAP ERP systems to SAP Sourcing [page 68]


Supplier Management

Business Process Integration


Configure IDoc for RFQ [page 72]


Strategic Sourcing

Configure RFQ output [page 72]


Strategic Sourcing

Define item text for purchase order [page 75]


Strategic Sourcing

Configure RFP award to transfer pricing conditions [page 78]


Contract Lifecycle Management (CLM)

Create pricing conditions in SAP Sourcing [page 76]


CLM

Assign pricing conditions in SAP Sourcing to pricing condition types in SAP ERP [page 77]



Configure master agreement type to transfer pricing conditions [page 79]


CLM

Set up item text IDs for contract and scheduling agreement [page 80]



Block integrated fields from user changes in SAP ERP [page 81]



Constraints

For special points to consider when integrating SAP ERP and SAP Sourcing, see SAP Note 1527171.

More Information

Troubleshooting [page 83]

Mapping of Fields Between SAP ERP and SAP Sourcing [page 86]

Extensions to Integration of SAP ERP and SAP Sourcing [page 130]

1 Introduction

2011-08-18 PUBLIC 13/134


2 General SAP Sourcing Configuration

Prerequisites

You have configured SAP Sourcing as described in the configuration guide on SAP Service Marketplace

at http://service.sap.com/eso.

2.1 Create System Property is_sapint_installed

The system property is_sapint_installed indicates whether integration with SAP ERP is enabled for

this SAP Sourcing system.

Procedure

NOTE

This is carried out by the SAP Service Delivery consultant.

1. Log on to SAP Sourcing with any user that has access to enterprise-level system properties.

2. Choose Setup.

3. On the System Setup tab, find the Configuration section and click System Properties.

4. Create the property is_sapint_installed with the value TRUE. If the property already exists, but

has the value FALSE, change the value to TRUE and restart the application.

2.2 Check Integrated Document Types for RFx and Contract

NOTE


The following integrated document types are provided in the workbook:

■ Integrated document type for RFx

■ Integrated document type for contracts

You need them to create integrated RFx and contracts.

Procedure

Check Integrated Document Type for RFx

1. Log on to SAP Sourcing with any user that has access to this object.

2. Choose Setup.


2.1 Create System Property is_sapint_installed

2011-08-18 PUBLIC 15/134


3. On the Document Setup tab, find the RFx section and click RFx Types.

4. Click the integrated document type.

5. On the Integration tab, verify that values are entered for the attributes in the following table. The

value list type must exist in SAP Sourcing and in SAP ERP; for more information, see Verify Value

List Values [page 50].

Integrated Document Type Attributes and Value List Types for RFx

Attribute Value List Type

Default Header Text Header Text ID

Default Line Item Text Item Text ID

Verify that pricing conditions are assigned to the integrated document type; for more information,

see Verify Pricing Conditions [page 51].

RECOMMENDATION

We recommend leaving the Use ERP Validation checkbox selected. If this checkbox is selected,

several validations are carried out when the user changes the phase to Open for Response and

when the user publishes the RFP award to SAP ERP. This enables the user to correct any errors

that might otherwise prevent the purchase order or outline agreement from being created

in SAP ERP.

Check Integrated Document Type for Contract


2. Choose Setup.

3. On the Document Setup tab, find the Agreements section and click Master Agreement Types.

4. Click the integrated document type.

5. On the Integration Details tab, verify that values are entered for the attributes in the following table.

The value list type must exist in SAP Sourcing and in SAP ERP; for more information, see Verify

Value List Values [page 50].

Integrated Document Type Attributes and Value List Types for Contract

Attribute Value List Type

Default Header Text Header Text ID

Default Line Item Text Item Text ID

Verify that pricing conditions are assigned to the integrated document type; for more information,

see Verify Pricing Conditions [page 51].

RECOMMENDATION

We recommend leaving the Use ERP Validation checkbox selected. If this checkbox is selected,

several validations are carried out when the user publishes the master agreement or

subagreement to SAP ERP. This enables the user to correct any errors that might otherwise

prevent the contract from being created in SAP ERP.


2.2 Check Integrated Document Types for RFx and Contract

16/134 PUBLIC 2011-08-18

More Information

For information about workbooks, see the Reference Guide. (On the SAP Sourcing UI, choose Reference

Guide.)

2.3 Create RFx Template

NOTE

This is carried out by the SAP Service Delivery consultant in collaboration with your ERP expert

or consultant.

This template is used to create RFx that are to be imported from SAP ERP to SAP Sourcing. The

minimum requirement is that the template is of an integrated document type, has at least one line

item group, at least one Incoterm, and at least one pricing condition. All other features are optional.

Procedure

1. Log on to SAP Sourcing as a user with enough authority to create RFx templates.

2. Choose Enterprise Sourcing RFx Create RFx Template .

3. Select your integrated document type for RFx (see Check Integrated Document Types for RFx and

Contract [page 15]) and choose Continue.

4. Enter a display name, for example, RFx Template for Integration.

5. Add users as collaborators who need to access the template.

6. On the Line Items tab, check that the template has at least one line item group.

Normally, the RFx type is set up so that an RFx template created from this RFx type always has a

default line item group. You can edit the default line item group in the template, replace it, or add

more, but be sure to leave at least one line item group in the template.

7. Choose Document Setup .

8. On the Delivery Info tab, add at least one Incoterm, and choose Save.

9. On the Pricing Model tab, choose Add Pricing Condition to add at least one pricing condition, and choose

Save.

10. Save the RFx template.

2.4 Edit Integrated System Configuration

NOTE


This object contains customer-specific settings for the integration of SAP ERP and SAP Sourcing. (The

object is the same irrespective of whether SAP Sourcing is on-premise or hosted.)


2.3 Create RFx Template

2011-08-18 PUBLIC 17/134

Procedure


2. Choose Setup.

3. On the System Setup tab, find the Integration section and click Integrated System Configuration.

4. Click the integrated system configuration object.

5. Choose Edit.

6. Maintain the integrated system configuration as required. Information is provided for certain fields

in the following table. The values for the other fields depend on your integration scenario.

NOTE

The service name and namespace in the SAP Sourcing integration configuration object are

case-sensitive. Make sure that the same case is used in both SAP NetWeaver Process Integration

(SAP NetWeaver PI) and SAP Sourcing.

Fields and Values for Integrated System Configuration

Field Value

Use FTP Select(The values for the FTP fields will be provided by SAP Hosting.)

PI URL https://<PI host>:443/sap/xi/adapter_plain?namespace=http://sap.com/xi/ESourcing/SRMJS&service=<name of Sourcing business system configured in PI>&scheme=&QOS=BE&sap-user=<user ID to connect to PI server>&sap-client=<client number of PI system>&sap-language=<your language>

NOTE

443 is the HTTPS port and must not be changed.

EXAMPLE

https://host.customerdomain.com/sap/xi/adapter_plain?namespace=http://sap.com/xi/ESourcing/SRMJS&service=sourcing5&scheme=&QOS=BE&sap-user=i821067&sap-client=001&sap-language=EN

PI Password

Enter the password that is used to connect to the SAP NetWeaver PI system.

SAP ERP Release

Specify the SAP ERP release and enhancement package that you want to integrate with SAP Sourcing. The default value is SAP ERP 6.0. It is particularly important to change this to your release and enhancement package if you want to integrate service line items in SAP Sourcing with SAP ERP.

2.5 Define Default Language Preferences for Localized Resource Strings

NOTE


Each localized resource string has a default language value that is displayed if no specific language value

is provided. Because SAP Sourcing is delivered in English, the default language in the standard system

is English. If you want to use other languages, you can install language packs for those languages. If


2.5 Define Default Language Preferences for Localized Resource Strings

18/134 PUBLIC 2011-08-18

you install a language pack for another language, your custom localized resource strings may have

default values in that language, rather than in English.

When integrating SAP Sourcing with SAP ERP, you can export certain localized fields from SAP ERP

to SAP Sourcing. If one of these fields has localized resource strings for multiple languages, all of the

localized resource strings are added to the object that is imported to SAP Sourcing, provided that the

language packs for those languages have been installed. (SAP Sourcing accepts only localized resource

strings for languages whose language packs have been installed.) In the standard system, SAP Sourcing

requires each inbound localized resource string to have a value in the default language English. Because

it is not always possible to guarantee that SAP ERP will provide a value in English for each localized

resource string, you can use the integrated system configuration object in SAP Sourcing to define a

ranking of default languages, and thus determine the default language. The integrated system

configuration object is an enterprise-level configuration object with a series of settings for integration.

This functionality is available only for master data that is imported from SAP ERP; it is not available for

standard CSV imports.

EXAMPLE

In the integrated system configuration object, you define a ranking of French, Spanish, English.

The import file from SAP ERP contains values in Spanish and English. The value in Spanish is

therefore the default language value because a value in French was not provided.

If language values are provided for language packs that are installed in SAP Sourcing, but the languages

are not included in the ranking in the integrated system configuration object, the import will fail with

an error indicating that a default language value was not provided.

Procedure

1. Log on to SAP Sourcing with any user that has access to the integrated system configuration object.

2. Choose Setup.

3. On the System Setup tab, find the Integration section and click Integrated System Configuration.

4. Click the integrated system configuration object and choose Edit.

5. Add references to one or more language packs that are installed in your system. You do this by

choosing Add Language Pack.

6. Rank the languages as required. You do this by choosing Reorder List and then dragging and dropping

the languages to the required order of preference. If the list is empty, SAP Sourcing defaults to

English.

2.6 Edit Integrated Document Configuration

NOTE



2.6 Edit Integrated Document Configuration

2011-08-18 PUBLIC 19/134

The integrated document configuration (IDC) contains company-scoped settings for the integration

of SAP ERP and SAP Sourcing.

If you have imported the company quickstart workbook, you simply need to edit the IDC object as

described below. If you have not imported this workbook, you must create the IDC object and maintain

it as described below.

Procedure

1. Log on to SAP Sourcing as a user in the company context with system administration rights.

2. Choose Setup.

3. On the System Setup tab, find the Integration section and click Integrated Document Configuration.

4. Click the IDC object.

5. Choose Edit.

6. Maintain the IDC object as shown in the following table:

Fields and Values for Integrated Document Configuration

Field Value

External ID idc

Display Name Integrated Document Configuration

RFx Template Select the RFx template that you created in Create RFx Template [page 17].

Integrated System Configuration

Select the integrated system configuration object that you edited in Edit Integrated System Configuration [page 17].

Excluded/Included Attribute List

This is a list of zero or more exportable business objects and an excluded/included attribute list for each. You use it to control which fields are rendered in an export.

Field Length Validation List This allows configuration of additional field length validation. For example, if a field is 10 characters in SAP Sourcing, but only 5 characters in SAP ERP, you can configure a validation for that here.

More Information

For information about including additional fields as integrated fields, or excluding fields, see SAP Library

for SAP Sourcing on SAP Help Portal at http://help.sap.com SAP Business Suite SAP Sourcing

Integration of SAP Sourcing and SAP ERP Master Data Managing Integrated Fields in SAP Sourcing .

2.7 Create Scheduled Tasks to Import XML Messages for Materials, Vendors, and RFx

NOTE


You must create the following scheduled tasks in SAP Sourcing to import the XML messages that are

generated by SAP NetWeaver Process Integration:

■ Scheduled task for materials



20/134 PUBLIC 2011-08-18

http://help.sap.com

■ Scheduled task for vendors

■ Scheduled task for RFx

Procedure

1. Log on to SAP Sourcing as a user with system administration rights.

2. Choose Setup.

3. On the System Setup tab, find the Scheduled Tasks section and click Scheduled Tasks.

4. Choose Create.

5. Select Data Import Monitor and choose Create.

6. Create the scheduled task for materials as shown in the following table.

Field Value

Inactive (Status) Select this checkbox until you are ready to run the task.

Display Name Master Data Import

Description For materials, enter Import of Materials.For vendors, enter Import of Vendors.For RFx, enter Import of RFx.

Run As User Choose a key user.

Frequency Set the frequency according to your business requirements. However, be aware that running these tasks too frequently will cause performance issues.

RECOMMENDATION

The tasks run off the same daemon so we recommend the following frequencies: ■ For materials, once daily in the middle of the night ■ For vendors, three times daily ■ For RFx, every 10 minutes

Start Date As required.

Expiration Date As required.

On These Days As required.

7. Click Data Import Task Configuration.

8. Maintain the data import task configuration as shown in the following table.

Field Value

Data Location FTP

Requires Authentication Select

FTP Information Provided by SAP Hosting.

Delete Data from FTP Server After Downloading Select

Upload Directory Provided by SAP Hosting.

Queue Directory Provided by SAP Hosting.

Archive Directory Provided by SAP Hosting.

Receipt Notice TypeCompletion Notice Type

Be aware that a setting other than None could cause many e-mails or alerts because an e-mail or alert is sent for each import file.

9. Save your entries.



2011-08-18 PUBLIC 21/134

10. Create the scheduled task for vendors and the scheduled task for RFx.

More Information

Integration Architecture for Master Data Integration [page 37]

Publishing RFx to Different Subcontexts [page 130]



22/134 PUBLIC 2011-08-18

3 SAP NetWeaver Process Integration

3.1 Set Up System Landscape Directory

Procedure

NOTE

This is carried out by your NetWeaver Process Integration (PI) expert or consultant.

1. In the process integration tools (transaction SXMB_IFR), log on to the System Landscape Directory

(SLD).

2. Import the Component Repository (CR) content into the SLD. For instructions, see SAP Note

669669.

3. Create a new Web Application Server (Web AS) ABAP technical system to register the SAP ERP

system in the SLD. For instructions, see SAP Note 584654.

4. Create a new standalone technical system to register the SAP Sourcing system in the SLD. For more

information, click Help and navigate to Working with SLD Technical Systems Creating New Standalone

Technical Systems .

5. Create a business system for the SAP ERP system as shown in the following table:

Field Value Example

Business System Enter the business system for the SAP ERP system

QV5_340

Role Application System

Related Integration Server

SAP NetWeaver Process Integration (SAP NetWeaver PI) system that is defined in the SLD

INTEGRATION_SERVER_X7X

Technical System Technical system that you defined in step 3

Client Client of the SAP ERP system

Logical System Name Logical system of the SAP ERP system<SID>CLNT<Client Number>

QV5CLNT340

6. Create a business system for the SAP Sourcing system as shown in the following table:

Field Value Example

Business System Enter the business system for the SAP Sourcing system

FRU_pwdf6788

Role Application System

Related Integration Server

SAP NetWeaver PI system that is defined in the SLD

INTEGRATION_SERVER_X7X

Technical System Technical system that you defined in step 4


3.1 Set Up System Landscape Directory

2011-08-18 PUBLIC 23/134



Field Value Example

Logical System Name Logical system of the SAP Sourcing system as defined in Define Logical System [page 44]

FRUESO

7. Choose the technical system that you created in steps 3 and 4, and add the respective business

system.

8. To retrieve the newly created business system, clear the SLD data cache by logging on to the

Integration Directory (SAP NetWeaver PI 7.0) or Integration Builder (SAP NetWeaver PI 7.1) and

choosing Environment Clear SLD Data Cache .

3.2 Define RFC Destination and Port

Procedure

NOTE


1. In the SAP NetWeaver Process Integration (SAP NetWeaver PI) system, define the RFC destination

using transaction SM59, as shown in the following table:

Parameters and Values for RFC Destination

Field Value Example

RFC Destination <SID of SAP ERP system>CLNT<client number of SAP ERP system> QV5CLNT340

Connection Type 3(For connection to ABAP systems)

Target Host Host name of SAP ERP system

System Number System number of SAP ERP system

Language Details to connect to SAP ERP system

Client Details to connect to SAP ERP system

User Details to connect to SAP ERP system

Password Details to connect to SAP ERP system

2. In the SAP NetWeaver PI system, define the port for SAP NetWeaver PI to receive the SAP ERP RFQ

IDocs. You do this using transaction IDX1, as shown in the following table:

Parameters and Values for Port

Field Value Example

Port SAP<SID of SAP ERP system> SAPQV5

Client Client of SAP ERP system 340

Description RFC Destination Pointing to SAP ERP System

RFC Destination RFC destination that you created in step 1 QV5CLNT340


3.2 Define RFC Destination and Port

24/134 PUBLIC 2011-08-18

3.3 Import Process Integration Content to Integration Repository

Procedure

NOTE


1. In the process integration tools (transaction SXMB_IFR), log on to the Integration Repository (SAP

NetWeaver PI 7.0) or Enterprise Services Builder (SAP NetWeaver PI 7.1).

2. Download the SAP ERP interface definitions from SAP Service Marketplace at http://

service.sap.com/swdc Support Packages and Patches Browse Our Download Catalog SAP Content ESR

Content (XI Content) XI CONTENT SAP_APPL XI CONTENT SAP_APPL 604 .

3. Download the SAP Sourcing interface definitions and mappings from SAP Service Marketplace at

http://service.sap.com/swdc Support Packages and Patches Browse our download catalog SAP Content

ESR Content (XI Content) XI CONTENT ESC SRM JAVA SERVER XI CONTENT ESC

SRMJSERVER 8.0 .

4. If you are using SAP NetWeaver PI 7.1 or higher, download the latest support package of XI

CONTENT SAP_BASIS 7.00 from SAP Service Marketplace at http://service.sap.com/swdc

Support Packages and Patches Browse Our Download Catalog SAP Content ESR Content (XI Content) XI

CONTENT SAP_BASIS XI CONTENT SAP_BASIS 7.00 .

5. Import the downloaded content by choosing Tools Import Design Objects .

3.4 Configure Integration Scenarios

Procedure

NOTE


In the following procedure, there are some differences between SAP NetWeaver PI 7.0 and 7.1. These

differences are indicated by SAP NetWeaver PI 7.0 or SAP NetWeaver PI 7.1.

1. In the process integration tools (transaction SXMB_IFR), log on to the Integration Directory (SAP

NetWeaver PI 7.0) or Integration Builder (SAP NetWeaver PI 7.1).

2. SAP NetWeaver PI 7.0: Choose Tools Transfer Integration Scenario from Integration Repository .

SAP NetWeaver PI 7.1: Choose Tools Apply Model from ES Repository .

3. SAP NetWeaver PI 7.0: In the dialog box that appears, click the input help for the Name field, choose

the integration scenario for this software component (see note below), and choose Continue.

SAP NetWeaver PI 7.1: In the dialog box that appears, select Process Integration Scenario, click the input

help for the Name field, choose the integration scenario for this software component (see note

below), and choose Continue.


3.3 Import Process Integration Content to Integration Repository

2011-08-18 PUBLIC 25/134

http://service.sap.com/swdc




NOTE

The software component is E-SOURCING SRM JAVA SERVER <Release>.

4. If required, change the configuration scenario name and choose Finish, and then choose Close.

The configurator screen appears.

5. SAP NetWeaver PI 7.0: In the component view, right-click SAP ERP ENHANCE PACKAGE – 6.0

and choose Assign Service.

SAP NetWeaver PI 7.1: In the component view, click SAP ERP ENHANCE PACKAGE – 6.0.

6. SAP NetWeaver PI 7.0: Click the create icon with the tooltip Create Services for Business Systems.

SAP NetWeaver PI 7.1: Click the create icon with the tooltip Create Business System Components for Business

Systems.

7. In the wizard that appears, proceed as follows:

1. In step 1 of the wizard, choose Continue.

2. In step 2 of the wizard, choose Continue.

3. In step 3 of the wizard, select the respective business system for ERP 6.0 that is previously

defined in the system landscape directory.

NOTE

If the business system for ERP 6.0 is not available in the list of business systems, the business

system already exists as a business component. In this case, do the following.

1. Exit the wizard by clicking Cancel.

2. In the model configurator, click the input help for the Communication Component field.

3. Under Search Criteria, ensure that the Communication Component Selection attribute has the

value All Business System Components.

4. Select the communication component for the business system for ERP 6.0 and choose

Apply.

5. Skip steps d) and e) below.

4. Deselect the Create Communication Channels Automatically checkbox.

5. Choose Finish and then choose Close.

8. SAP NetWeaver PI 7.0 only: In the Assign Services to Application Components dialog box, choose Assign.

9. Repeat steps 5 to 8 for E-SOURCING ON DEMAND – 8.0.

Check RFC Connection Between SAP NetWeaver Process Integration and SAP ERP

RECOMMENDATION

Print out Check RFC Connection Between SAP Net Weaver Process Integration and SAP ERP because you will

need to refer to it frequently in this topic.

1. SAP NetWeaver PI 7.0: In the component view, double-click the connector (<->) between Receive

RFC Call of RFC_PING and Send Configuration Test Request to ERP.

SAP NetWeaver PI 7.1: In the component view, click the connector (<->) between Receive RFC Call

of RFC_PING and Send Configuration Test Request to ERP.



26/134 PUBLIC 2011-08-18

2. SAP NetWeaver PI 7.0: On the Connections from the Service Assignment tab, position the cursor in the

Communication Channel field for Sender Business System Services and, in the dropdown for the create icon,

choose Create Communication Channel with Template.

SAP NetWeaver PI 7.1: On the Connections from Component Assignment tab, position the cursor in the

Communication Channel field for Sender Business System Components and, in the dropdown for the create

icon, choose Create Communication Channel with Template.

3. In the dialog box that appears, proceed as follows:

1. In step 1 of the dialog box, choose Continue.


3. In step 3 of the dialog box, note down the name of the communication channel. You can

rename the communication channel if you wish.

NOTE

If you rename the communication channel, be sure to note down the original name and

the new name, and keep this information safe. This will help you later on in this guide.



Communication Channel field for Receiver Business System Services and, in the dropdown for the create icon,

choose Create Communication Channel with Template.


Communication Channel field for Receiver Business System Components and, in the dropdown for the create

icon, choose Create Communication Channel with Template.

5. In the dialog box that appears, proceed as follows:



3. In step 3 of the dialog box, note down the name of the communication channel. You can

rename the communication channel if you wish.

NOTE

If you rename the communication channel, be sure to note down the original name and

the new name, and keep this information safe. This will help you later on in this guide.


6. Choose Apply.

Send Supplier Master from SAP Sourcing to SAP ERP

1. SAP NetWeaver PI 7.0: In the component view, double-click the connector (<-) between Send Supplier

Master to ERP and Receive Vendor Master from Partner Component.

SAP NetWeaver PI 7.1: In the component view, click the connector (<-) between Send Supplier Master

to ERP and Receive Vendor Master from Partner Component.

2. Repeat steps 2 to 6 of Check RFC Connection Between SAP NetWeaver Process Integration and SAP ERP.



2011-08-18 PUBLIC 27/134

Send Vendor Master from SAP ERP to SAP Sourcing

1. SAP NetWeaver PI 7.0: In the component view, double-click the connector (->) between Send Vendor

Master to Partner Component and Receive Supplier Master from ERP.

SAP NetWeaver PI 7.1: In the component view, click the connector (->) between Send Vendor Master

to Partner Component and Receive Supplier Master from ERP.


Send Material Master from SAP ERP to SAP Sourcing

1. SAP NetWeaver PI 7.0: In the component view, double-click the connector (->) between Send

Material Master to Partner Component and Receive Material from ERP.

SAP NetWeaver PI 7.1: In the component view, click the connector (->) between Send Material Master

to Partner Component and Receive Material from ERP.


Communication Channel field for Sender Business System Services and, in the dropdown for the Communication

Channel field, select the communication channel that you created for sender business system services

in Check RFC Connection Between SAP NetWeaver Process Integration and SAP ERP, and choose OK.


Communication Channel field for Sender Business System Components and, in the dropdown for the

Communication Channel field, select the communication channel that you created for sender business

system components in Check RFC Connection Between SAP NetWeaver Process Integration and SAP ERP, and

choose OK.


Send RFQ from SAP ERP to SAP Sourcing

1. SAP NetWeaver PI 7.0: In the component view, double-click the connector (->) between Send

Quotation to Partner Component and Receive RFx from ERP.

SAP NetWeaver PI 7.1: In the component view, click the connector (->) between Send Quotation to

Partner Component and Receive RFx from ERP.


Send RFP Response from SAP Sourcing to SAP ERP

1. SAP NetWeaver PI 7.0: In the component view, double-click the connector (<-) between Send

Response of RFx Update to ERP and Receive RFC Call of BBP_ES_PR_RFQ_UPDATE.

SAP NetWeaver PI 7.1: In the component view, click the connector (<-) between Send Response of

RFx Update to ERP and Receive RFC Call of BBP_ES_PR_RFQ_UPDATE.

2. Repeat steps 2 and 3 of Check RFC Connection Between SAP NetWeaver Process Integration and SAP ERP.


Communication Channel field for Receiver Business System Services and, in the dropdown for the Communication



28/134 PUBLIC 2011-08-18

Channel field, select the communication channel that you created for receiver business system

services in Check RFC Connection Between SAP NetWeaver Process Integration and SAP ERP, and choose OK.


Communication Channel field for Receiver Business System Components and, in the dropdown for the

Communication Channel field, select the communication channel that you created for receiver business


choose OK.

4. Choose Apply.

Publish SAP Sourcing RFx Award to SAP ERP Outline Agreement


RFC Call of BBP_ES_OA_UPDATE and Send Award to ERP for Outline Agreement Update.


of BBP_ES_OA_UPDATE and Send Award to ERP for Outline Agreement Update.









choose OK.









choose OK.

4. Choose Apply.

Publish SAP Sourcing RFx Award to SAP ERP Purchase Order


RFC Call of BBP_ES_PO_CREATE and Send Award to ERP for Purchase Order Creation.


of BBP_ES_PO_CREATE and Send Award to ERP for Purchase Order Creation.



2011-08-18 PUBLIC 29/134









choose OK.









choose OK.

4. Choose Apply.

Publish SAP Sourcing Master Agreement to SAP ERP Outline Agreement


RFC Call of BBP_ES_OA_UPDATE and Send Agreement to ERP.


of BBP_ES_OA_UPDATE and Send Agreement to ERP.









choose OK.







30/134 PUBLIC 2011-08-18





choose OK.

4. Choose Apply.

Generate Configuration Objects

1. SAP NetWeaver PI 7.0: Under Configuration Steps, click Generate.

SAP NetWeaver PI 7.1: Click the icon with the tooltip Create Configuration Objects.

2. In the dialog box that appears, select Generation, ensure that all three checkboxes under Scope of

Generation are selected, select Create New, and then choose Start.

The following table shows the configuration objects that are generated for Check RFC Connection Between

SAP NetWeaver Process Integration and SAP ERP. The sender business system is SAP Sourcing, the receiver

business system is SAP ERP.

Configuration Objects Generated for Check RFC Connection Between SAP NetWeaver Process Integration and SAP ERP

Sender Interface Sender Communication Channel TemplateReceiver Interface Receiver Communication Channel Template Interface Mapping

MI_OB_Configuration_Test CT_Generic_Sending_HTTP_Channel_For_ES_Documents RFC_PING CT_Generic_Receiving_RFC_Channel_For_ERP_Functions IM_Configuration_Test_To_RFC_ PING

The following table shows the configuration objects that are generated for Send Supplier Master from SAP

Sourcing to SAP ERP. The sender business system is SAP Sourcing, the receiver business system is SAP ERP.

Configuration Objects Generated for Send Supplier Master from SAP Sourcing to SAP ERP

Sender Interface Sender Communication Channel Receiver Interface Receiver Communication Channel Interface Mapping

MI_OB_Supplier CT_Supplier_Sending_File_Channel_For_ES CREMAS.CREMAS05 CT_Generic_Receiving_IDOC_Channel_For_ERP_Inbound_IDOCs IM_Supplier_To_Vendor

The following table shows the configuration objects that are generated for Send Vendor Master from SAP

ERP to SAP Sourcing. The sender business system is SAP ERP, the receiver business system is SAP Sourcing.

Configuration Objects Generated for Send Vendor Master from SAP ERP to SAP Sourcing

Sender Interface Sender Communication ChannelReceiver Interface Receiver Communication Channel Interface Mapping

CREMAS.CREMAS05 CT_Generic_Sending_HTTP_Channel_For_ERP_Outbound_IDOCs MI_IB_Supplier CT_Supplier_Receiving_File_Channel_For_ES IM_ERP_Vendor_To_ES_Supplier

The following table shows the configuration objects that are generated for Send Material Master from SAP

ERP to SAP Sourcing. The sender business system is SAP ERP, the receiver business system is SAP Sourcing.

Configuration Objects Generated for Send Material Master from SAP ERP to SAP Sourcing


MATMAS.MATMAS05 CT_Generic_Sending_HTTP_Channel_For_ERP_Outbound_IDOCs MI_IB_Material CT_Material_Receiving_File_Channel_For_ES IM_ERP_Material_To_ES_Material



2011-08-18 PUBLIC 31/134

The following table shows the configuration objects that are generated for Send RFQ from SAP ERP to SAP

Sourcing. The sender business system is SAP ERP, the receiver business system is SAP Sourcing.

Configuration Objects Generated for Send RFQ from SAP ERP to SAP Sourcing


REQOTE.ORDERS05 CT_Generic_Sending_IDOC_Channel_For_ERP_Outbound_IDOCs MI_IB_RFx CT_RFx_Receiving_File_Channel_For_ES IM_ORDERS05_To_RFx

The following table shows the configuration objects that are generated for Send RFP Response from SAP

Sourcing to SAP ERP. The sender business system is SAP Sourcing, the receiver business system is SAP ERP.

Configuration Objects Generated for Send RFP Response from SAP Sourcing to SAP ERP


MI_OB_RFx_Response CT_RFx_Response_Sending_File_Channel_For_ES BBP_ES_PR_RFQ_ UPDATE

CT_Generic_Receiving_RFC_Channel_For_ERP_Functions IM_RFx_To_PurchaseRequisition

The following table shows the configuration objects that are generated for Publish SAP Sourcing RFx Award

to SAP ERP Outline Agreement. The sender business system is SAP Sourcing, the receiver business system

is SAP ERP.

Configuration Objects Generated for Publish SAP Sourcing RFx Award to SAP ERP Outline Agreement


MI_OB_Award_To_ OA

CT_Generic_Sending_HTTP_Channel_For_ES_Documents BBP_ES_OA_UPDATE CT_Generic_Receiving_RFC_Channel_For_ERP_Functions IM_Award_To_OA

The following table shows the configuration objects that are generated for Publish SAP Sourcing RFx Award

to SAP ERP Purchase Order. The sender business system is SAP Sourcing, the receiver business system is

SAP ERP.

Configuration Objects Generated for Publish SAP Sourcing RFx Award to SAP ERP Purchase Order


MI_OB_Award_To_ Purchase_Order

CT_Generic_Sending_HTTP_Channel_For_ES_Documents BBP_ES_PO_CREATE CT_Generic_Receiving_RFC_Channel_For_ERP_Functions IM_Award_To_Purchase_Order

The following table shows the configuration objects that are generated for Publish SAP Sourcing Master

Agreement to SAP ERP Outline Agreement. The sender business system is SAP Sourcing, the receiver business

system is SAP ERP.

Configuration Objects Generated for Publish SAP Sourcing Master Agreement to SAP ERP Outline Agreement


MI_OB_Agreement CT_Generic_Sending_HTTP_Channel_For_ES_Documents BBP_ES_OA_UPDATE CT_Generic_Receiving_RFC_Channel_For_ERP_Functions IM_Agreement_To_OA



32/134 PUBLIC 2011-08-18

3.5 Configure Communication Channels

Procedure

NOTE


1. In the process integration tools (transaction SXMB_IFR), log on to the Integration Directory (SAP

NetWeaver PI 7.0) or Integration Builder (SAP NetWeaver PI 7.1).

2. Under Configuration Scenario, open the configuration scenario that you created in Configure Integration

Scenarios [page 25].

3. Configure the communication channels that are associated with the SAP ERP business system.

Double-click a communication channel and enter the data shown in the following table for that

communication channel. In the following tables, the names of the communication channels are

the names in the standard system. You may have renamed the communication channels when

you created them in Configure Integration Scenarios [page 25].

Parameters and Values for Communication Channel CT_Generic_Receiving_IDOC_Channel_For_ERP_Inbound_IDOCs

Parameter Value Example

RFC Destination <RFC destination of SAP ERP system> QV5CLNT340

Interface Version SAP Release 4.0 or Higher

Port SAP<ERP system ID> SAPQV5

SAP Release Enter the current release of your SAP ERP system. You can get the release by checking the system status.

Parameters and Values for Communication Channel CT_Generic_Receiving_RFC_Channel_For_ERP_Functions

Parameter Value

Application Server Enter the host name of the SAP system.

System Number Enter the system number of the SAP system.

Logon User Enter the logon user for logging on to the SAP system.

Logon Password Enter the logon password for logging on to the SAP system.

Logon Language Enter the logon language of the SAP system.

Logon Client Enter the logon client of the SAP system.

All data has already been copied from the template for the following communication channels:

■ CT_Generic_Sending_HTTP_Channel_For_ERP_Outbound_IDOCs

■ CT_Generic_Sending_IDOC_Channel_For_ERP_Outbound_IDOCs

4. Configure the communication channels that are associated with the SAP Sourcing business system.

Double-click a communication channel and enter the data shown in the following table for that

communication channel. In the following tables, the names of the communication channels are

the names in the standard system. You may have renamed the communication channels when

you created them in Configure Integration Scenarios [page 25].



2011-08-18 PUBLIC 33/134

NOTE

The default transport protocol of the file communication channel templates is FTP.

Request the FTP details in the following tables (for example, path of FTP directory, IP address

of FTP server) from your hosting team.

Parameters and Values for Communication Channel CT_Supplier_Receiving_File_Channel_For_ES

Parameter Value

Target Directory Enter the path of the FTP directory.(This information will be provided by SAP Hosting.)

Server Enter the fully qualified domain name (FQDN) of the FTP server.

Connection Security Choose FTPS (FTP Using SSL/TLS) for Control and Data Connection.

Command Order Choose AUTH TLS, USER, PASS, PBSZ, PROT.

Anonymous Login Deselect.

User Name Enter the user name of the FTP account.

Password Enter the password of the FTP account.

Parameters and Values for Communication Channel CT_Supplier_Sending_File_Channel_For_ES

Parameter Value

Source Directory Enter the path of the FTP directory.

File Name *Vendor*.xml

Server Enter the FTP server.






Quality of Service(This field is on the Processing tab.)

Exactly Once

Poll Interval (Secs)(This field is on the Processing tab.)

Set the poll interval according to your business requirements. However, be aware that a very short poll interval will reduce performance.

RECOMMENDATION

We recommend a poll interval of 300 seconds (5 minutes).

Processing Mode(This field is on the Processing tab.)

Choose Delete.

Parameters and Values for Communication Channel CT_RFx_Response_Sending_File_Channel_For_ES

Parameter Value

Source Directory Enter the path of the FTP directory.

File Name *rfx*.xml

Server Enter the FTP server.







34/134 PUBLIC 2011-08-18

Parameter Value


Quality of Service(This field is on the Processing tab.)

Exactly Once

Poll Interval (Secs)(This field is on the Processing tab.)

Set the poll interval according to your business requirements. However, be aware that a very short poll interval will reduce performance.

RECOMMENDATION

We recommend a poll interval of 300 seconds (5 minutes).

Processing Mode(This field is on the Processing tab.)

Choose Delete.

Parameters and Values for Communication Channel CT_Material_Receiving_File_Channel_For_ES

Parameter Value

Target Directory Enter the path of the FTP directory.

Server Enter the FQDN of the FTP server.






Parameters and Values for Communication Channel CT_RFx_Receiving_File_Channel_For_ES

Parameter Value

Target Directory Enter the path of the FTP directory.

Server Enter the FQDN of the FTP server.






All data has already been copied from the template for the following communication channel:

CT_Generic_Sending_HTTP_Channel_For_ES_Documents

5. Activate all configuration objects and the configuration scenario as follows:

1. Expand the change lists on the Change Lists tab.

2. Right-click your change list and choose Activate.

3. In the dialog box that appears, choose Activate.

4. Most objects are in your change list, but some are in the standard change list. Activate these

objects too.

This activates the SAP ERP business system and SAP Sourcing business system, communication

channels, receiver determinations, interface determinations, receiver agreements, sender

agreements, and configuration scenario.

See also Sending Files and Customizing Data via FTPS Protocol [page 125].



2011-08-18 PUBLIC 35/134

4 Master Data Integration

4.1 Integration Architecture for Master Data Integration

You must replicate Customizing data and then material and vendor master data from SAP ERP to SAP

Sourcing.

You replicate the Customizing data using program BBP_ES_CUSTOMIZINGDATA_EXTRACT. This

program generates XML files that you import to SAP Sourcing manually. This is described in detail

later in this chapter.

You replicate material and vendor master data using Application Link Enabling (ALE) distribution and

SAP NetWeaver Process Integration (SAP NetWeaver PI) configuration. This is described in detail later

in this chapter. For an overview of the process, see below.

Material Master Data from SAP ERP to SAP Sourcing

In the following figure, a material is sent from SAP ERP, triggering the creation of a material in SAP

Sourcing.

Figure 1: Integration Architecture for Material Master Data

See also Mapping of Material Master Data from SAP ERP to SAP Sourcing [page 90].



2011-08-18 PUBLIC 37/134

Vendor Master Data from SAP ERP to SAP Sourcing

In the following figure, a vendor is sent from SAP ERP, triggering the creation of a supplier in SAP

Sourcing.

Figure 2: Integration Architecture for Vendor Master Data

See also Mapping of Vendor Master Data from SAP ERP to SAP Sourcing [page 91].

Supplier Publishing from SAP Sourcing to SAP ERP

In the following figure, a supplier is published from SAP Sourcing, triggering the creation of a vendor

in SAP ERP.



38/134 PUBLIC 2011-08-18

Figure 3: Integration Architecture for Supplier Publishing

See also Mapping of Supplier Master Data from SAP Sourcing to SAP ERP [page 93].

More InformationTroubleshooting [page 83]

4.2 Create Cross-System Company Codes and Business Areas

NOTE

This is carried out by your ERP expert or consultant.

To avoid errors in the distributed environment, you must name specific global organizational units

the same in all systems involved in distribution. To use Application Link Enabling (ALE), you must

assign local organizational units to the following global organizational units in each of these systems

to ensure that they are used consistently in the distributed environment.

■ Cross-system company codes

■ Cross-system business areas

Cross-system company codes are used in distribution in financial accounting. There is one central

system for each cross-system company code in the distributed environment. You must assign the local

company codes to the cross-system company codes in each system involved in distribution.

When an IDoc with company code dependent data is sent, the company code is replaced with the cross-

system company code in all company code fields. When the IDoc is received, the reverse conversion

takes place in the target system.



2011-08-18 PUBLIC 39/134

Cross-system business areas are used in distribution in financial accounting. You must assign the local

business areas to the cross-system business areas in each system involved in distribution.

When an IDoc with business area data is sent, the business area is replaced with the cross-system business

area in all business area fields. When the IDoc is received, the reverse conversion takes place in the target

system.

Procedure

Create Cross-System Company Codes

1. In transaction SALE, choose:

■ (SAP R/3 4.6C) Modelling and Implementing Business Processes Cross Application Settings Global

Organizational Units Cross-System Company Codes

■ (SAP Enterprise 4.70 and above): Modelling and Implementing Business Processes Global Organizational

Units Cross-System Company Codes

2. In the dialog box, select Cross-System Company Codes and click Choose.

3. Choose New Entries.

4. Enter the relevant global company codes and choose Save.

5. Choose Back.

6. Select Assign Cross-System Company Code to Chart of Accounts and click Choose.

7. Enter a chart of accounts for each global company code and choose Save.

8. Choose Back.

9. Select Assign Company Code to Cross-System Company Code and click Choose.

10. Enter a global company code for each organizational company code and choose Save.

NOTE

You can assign only one company code to each global company code.

Create Cross-System Business Areas

1. In transaction SALE, choose:

■ (SAP R/3 4.6C) Modelling and Implementing Business Processes Cross Application Settings Global

Organizational Units Cross-System Business Areas

■ (SAP Enterprise 4.70 and above): Modelling and Implementing Business Processes Global Organizational

Units Cross-System Business Areas

2. In the dialog box, select Cross-System Business Areas and click Choose.

3. Choose New Entries.

4. Enter the relevant cross-system business areas and choose Save.

5. Choose Back.

6. Select Assign Business Area to Cross-System Business Area and click Choose.

7. Enter a cross-system business area for each organizational business area and choose Save.



40/134 PUBLIC 2011-08-18

NOTE

You can assign only one business area to each cross-system business area.

4.3 Extract Customizing Data from SAP ERP

NOTE

This is carried out by your ERP expert, consultant, or key user.

You must extract the following Customizing data from SAP ERP:

■ Company codes

■ Purchasing organizations

■ Purchasing groups

■ Payment terms

■ Material groups

■ Plants

■ Condition types (pricing conditions), specifically all condition types of condition classes A

(discount or surcharge) and B (prices)

RECOMMENDATION

We recommend extracting the condition types from SAP ERP as described below. However,

instead of extracting the condition types from SAP ERP, you can create the pricing conditions

manually in SAP Sourcing, and map them to the pricing condition types in SAP ERP. For

more information, see the following:

● Create Pricing Conditions in SAP Sourcing [page 76]

● Assign Pricing Conditions in SAP Sourcing to Pricing Condition Types in SAP ERP [page 77]

You extract the Customizing data from SAP ERP using program BBP_ES_CUSTOMIZINGDATA_EXTRACT.

The extracted data is rendered as an XML document. The format of the XML data is specific to the

needs of the SAP Sourcing application. You can store the XML files on an application server or locally.

For more information about this program, see the program documentation in SAP ERP.

Various Business Add-In (BAdI) exits are provided to enhance the standard functionality.

You can use BAdI BADI_BBP_ES_ADDITIONAL_DATA to enhance or extend the Customizing data during

the extraction process.

You can use BAdI BADI_BBP_ES_DOWNLOAD_XML to define other locations for saving the XML files.

You can use BAdI BADI_BBP_ES_REMOVE_DATA to exclude fields from the XML document that are

relevant only for integration with earlier releases of SAP Sourcing. These fields may otherwise cause

warnings when you extract Customizing objects from SAP ERP to SAP Sourcing. These fields are as

follows:

■ DISPLAY_NAME_ID

■ DOCUMENT_DESCRIPTION_ID

BAdI BADI_BBP_ES_REMOVE_DATA has an example class BBP_ES_CL_REMOVE_DATA.



2011-08-18 PUBLIC 41/134

NOTE

If BAdI BADI_BBP_ES_REMOVE_DATA is not visible in Customizing for Integration with Other mySAP.com

Components E-Sourcing Business Add-Ins (BAdIs) , see SAP Note 1458469.

If you are integrating suppliers from multiple SAP ERP systems with SAP Sourcing, you can use the

XML files to identify company codes and purchasing organizations with the same identification number

in different SAP ERP systems. If you do not want a company code or purchasing organization to be

overwritten in SAP Sourcing when an object with the same identification number is extracted from a

different SAP ERP system to SAP Sourcing, you must implement BAdI BADI_BBP_ES_CHANGE_DATA to

render the identification number of the company code or purchasing organization unique for

integration with SAP Sourcing, for example, by appending the number of the logical system to the

number of the object. (This is not needed for other Customizing objects because only company codes

and purchasing organizations are supported when integrating suppliers from multiple SAP ERP

systems.)

EXAMPLE

Purchasing organizations 0001 and 0002 exist in SAP ERP systems ERP001 and ERP002. You

implement BAdI BADI_BBP_ES_CHANGE_DATA to change the identification number of each

purchasing organization to 0001_ERP001, 0001_ERP002, 0002_ERP001, 0002_ERP002 for

integration with SAP Sourcing.

BAdI BADI_BBP_ES_CHANGE_DATA has an example implementation

CL_EXM_IM_BADI_BBP_ES_CHG_DATA.

NOTE

If BAdI BADI_BBP_ES_CHANGE_DATA is not visible in Customizing for Integration with Other mySAP.com

Components E-Sourcing Business Add-Ins (BAdIs) , see SAP Note 1458469.

Procedure

1. In transaction BBP_ES_CUST_DOWNLOAD, enter the languages in which you want to extract the data

(for Customizing objects that support multiple languages).

2. Specify whether you want the generated XML files to be saved on the application server or locally.

The objective is to get the files to a location where the importer from the SAP Sourcing application

can access them.

As a guideline:

■ If you want to schedule the program as a background job, always save the generated XML files

on the application server. (You can implement a BAdI if you want to store the files in a different

location that is accessible to the application server.)

■ If you want to execute the program online, you can save the files on the application server or

locally.



42/134 PUBLIC 2011-08-18



3. Select the Customizing objects that you want to extract, and check the file names.

4. Choose Execute or schedule the program for execution periodically as needed.

5. Verify that the files are saved in the location that you specified. If you selected Save on Application

Server in step 2, you can use transaction AL11 to check the application server directory.

More Information


Mapping of Customizing Data from SAP ERP to SAP Sourcing [page 86]

Sending Files and Customizing Data via FTPS Protocol [page 125]

SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com SAP ERP Central Component

Logistics Materials Management (MM) Purchasing (MM-PUR) Conditions and Price Determination (MM-

PUR-VM)

4.4 Carry Out Initial Load of Customizing Data to SAP Sourcing

NOTE


You must import the following Customizing data to SAP Sourcing in the order given below:

■ Company codes

■ Purchasing organizations

■ Plants

■ Purchasing groups

■ Material groups

■ Payment terms

■ Condition types (pricing conditions)

RECOMMENDATION

We recommend importing the condition types from SAP ERP as described below. However,

instead of importing the condition types from SAP ERP, you can create the pricing conditions

manually in SAP Sourcing, and map them to the pricing condition types in SAP ERP. For

more information, see the following:

● Create Pricing Conditions in SAP Sourcing [page 76]

● Assign Pricing Conditions in SAP Sourcing to Pricing Condition Types in SAP ERP [page 77]

The initial load of Customizing data to SAP Sourcing is a manual process in which you upload the XML

files that you generated in Extract Customizing Data from SAP ERP [page 41].

If a field is optional in SAP Sourcing, and if an invalid value is exported from SAP ERP, the field will be

left blank in SAP Sourcing, and a warning message will be issued. The import will otherwise continue

successfully. For example, if the value of the company code to which a plant is assigned is invalid in

SAP Sourcing, you must export the correct company code and reexport the plant.


4.4 Carry Out Initial Load of Customizing Data to SAP Sourcing

2011-08-18 PUBLIC 43/134

http://help.sap.com

If you export, for example, a plant before the company code to which the plant is assigned, the plant

will be created in SAP Sourcing, but a warning message will be issued that the company code was not

found. The import will otherwise continue successfully. You must then export the company code and

reexport the plant.

Procedure

1. Log on to SAP Sourcing as the enterprise user or as a user that is scoped to the enterprise company.

NOTE

Most often, the Customizing data is wanted at enterprise level. This requires you to log on

to SAP Sourcing as the enterprise user or as a user that is scoped to the enterprise company.

If any of the objects are company-scoped, and you import them as a company-level user, only

that company will see the Customizing data. Whether this is desired depends on how you

segregate your data.

2. Choose Setup.

3. On the System Administration tab, find the Import and Export Tools section and click Import Data.

4. Choose Create and follow the wizard.

RECOMMENDATION

For each pricing condition, we recommend entering a description in SAP Sourcing. This

description can be longer than the name that is extracted from SAP ERP. For example, you can

use the description to explain to your suppliers how the pricing condition is used in the RFx

process. For more information, see Create Pricing Conditions in SAP Sourcing [page 76]. (There is no

equivalent description field in SAP ERP, so a description cannot be extracted from SAP ERP.)

More Information

SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com SAP ERP Central Component

Logistics Materials Management (MM) Purchasing (MM-PUR) Conditions and Price Determination (MM-

PUR-VM)

4.5 Define Logical System

NOTE


This step creates a logical system of SAP Sourcing, as maintained in the SAP NetWeaver Process

Integration (SAP NetWeaver PI) system.

NOTE

Logical systems are defined cross-client.


4.5 Define Logical System

44/134 PUBLIC 2011-08-18

http://help.sap.com

Procedure

1. In transaction BD54, choose New Entries.

2. Create a logical system that identifies the SAP Sourcing system, as shown in the following table:

Fields and Values for Logical System

Field Value Example

Logical System <Logical System Name> FRUESO

Name Sourcing Logical System

4.6 Maintain RFC Destination

NOTE


You need to maintain the RFC destination in order to define the target system of the master data IDocs.

RECOMMENDATION

To improve throughput of master data IDocs, we recommend bundling single IDocs for SAP

NetWeaver Process Integration (SAP NetWeaver PI) using the XML HTTP port type on the

outbound side and the plain HTTP adapter on the inbound side. By choosing the XML HTTP port

type, IDocs are sent using HTTP in one XML message containing multiple IDocs. With the XML

file port type, the ALE layer creates the IDocs directly in one single file in their XML representation.

Procedure

1. In transaction SM59, select HTTP Connections to ABAP System and choose Create.

2. Create an entry for material, as shown in the following table:

Fields and Values for Material

Field Value Example

RFC Destination

<SID of SAP NetWeaver PI><Client Number of SAP NetWeaver PI>_HTTPPLAIN_<Message Type>

X7X001_HTTPPLAIN_MATMAS

Connection Type

H

Description HTTP Connection to SAP NetWeaver PI System for Material Load

Target Host <SAP NetWeaver PI Server> uscix7x.sap.com

Service No. HTTP Service Port of SAP NetWeaver PI Server 50050

Path Prefix /sap/xi/adapter_plain/?namespace=urn:sap-com:document:sap:idoc:messages&interface=MATMAS.MATMAS05&service=<Sender System>&qos=EO (or EOIO)

/sap/xi/adapter_plain/?namespace=urn:sap-com:document:sap:idoc:messages&interface=MATMAS.MATMAS05&service=QV5_340&qos=EO

Language Details to connect to SAP NetWeaver PI system

Client Details to connect to SAP NetWeaver PI system

User Details to connect to SAP NetWeaver PI system

Password Details to connect to SAP NetWeaver PI system


4.6 Maintain RFC Destination

2011-08-18 PUBLIC 45/134

3. Create an entry for vendor, as shown in the following table:

Fields and Values for Vendor

Field Value Example

RFC Destination

<SID of SAP NetWeaver PI><Client Number of SAP NetWeaver PI>_HTTPPLAIN_<Message Type>

X7X001_HTTPPLAIN_CREMAS

Connection Type

H

Description HTTP Connection to SAP NetWeaver PI System for Vendor Load

Target Host <SAP NetWeaver PI Server> uscix7x.sap.com

Service No. HTTP Service Port of SAP NetWeaver PI Server 50050

Path Prefix /sap/xi/adapter_plain/?namespace=urn:sap-com:document:sap:idoc:messages&interface=CREMAS.CREMAS05&service=<Sender System>&qos=EO (or EOIO)

/sap/xi/adapter_plain/?namespace=urn:sap-com:document:sap:idoc:messages&interface=CREMAS.CREMAS05&service=QV5_340&qos=EO

Language Details to connect to SAP NetWeaver PI system

Client Details to connect to SAP NetWeaver PI system

User Details to connect to SAP NetWeaver PI system

Password Details to connect to SAP NetWeaver PI system

4. Ensure the status of the connection by choosing Connection Test.

If the connection is successful, the RFC connection test screen appears, indicating the connection

type and other connection data.

The RFC destinations are used in the next step Maintain Port Definition [page 46].

4.7 Maintain Port Definition

NOTE


Prerequisites

You have carried out the step Maintain RFC Destination [page 45].

Procedure

1. In transaction WE21, select XML HTTP and choose Create.

2. Create an entry for material, as shown in the following table:

Fields and Values for Material

Field Value Example

Port <SID of SAP NetWeaver PI System>_<Message Type>

X7X_MATMAS

Description XML HTTP Port to <SID of SAP NetWeaver PI System> Client <SAP NetWeaver PI Client> for <Message Type>

XML HTTP Port to X7X Client 001 for MATMAS

RFC Destination RFC destination that you created in Maintain RFC Destination [page 45]

X7X001_HTTPPLAIN_MATMAS


4.7 Maintain Port Definition

46/134 PUBLIC 2011-08-18

Field Value Example

Content Type Text/XML

3. Create an entry for vendor, as shown in the following table:

Fields and Values for Vendor

Field Value Example

Port <SID of SAP NetWeaver PI System>_<Message Type>

X7X_CREMAS

Description XML HTTP Port to <SID of SAP NetWeaver PI System> Client <SAP NetWeaver PI Client> for <Message Type>

XML HTTP Port to X7X Client 001 for CREMAS

RFC Destination RFC destination that you created in Maintain RFC Destination [page 45]

X7X001_HTTPPLAIN_CREMAS

Content Type Text/XML

4.8 Maintain Partner Profile

Procedure

NOTE


1. In transaction WE20, select Partner Type LS and choose Create.

2. Create a partner profile, as shown in the following table:

Fields and Values for Partner Profile

Field Value Example

Partner Number <Partner Number of SAP Sourcing Logical System> FRUESO

Partner Type LS

Type O or US

Agent Enter the job (person or group of persons) to be notified in case of error 50010120

Language EN

3. Maintain outbound parameters, as shown in the following tables:

Outbound Parameters for Message Type MATMAS

Field Value Example

Message Type MATMAS

Receiver Port Choose the XML HTTP port that you created in Maintain Port Definition [page 46]

X7X_MATMAS

Output Mode For better performance throughput in the initial upload of materials, select Collect IDocs

Basic Type MATMAS05

Outbound Parameters for Message Type CREMAS

Field Value Example

Message Type CREMAS


4.8 Maintain Partner Profile

2011-08-18 PUBLIC 47/134

Field Value Example

Receiver Port Choose the XML HTTP port that you created in Maintain Port Definition [page 46]

X7X_CREMAS

Output Mode For better performance throughput in the initial upload of vendors, select Collect IDocs

Basic Type CREMAS05

4. This step is necessary only if you want to publish suppliers from SAP Sourcing to SAP ERP.

Maintain inbound parameters, as shown in the following table.

Inbound Parameters for Message Type CREMAS

Field Value

Message Type CREMAS

Process Code CRE1

Processing by Function Module Trigger Immediately

4.9 Maintain Distribution Model

Procedure

NOTE


1. In transaction BD64, switch to edit mode.

2. Choose Create Model View.

3. Create a model view, as shown in the following table:

Field Value

Short Text ERP – Sourcing Integration

Technical Name ERP_ES_INT

4. In the Distribution Model list, select ERP – E-Sourcing Integration and choose Add Message Type.

5. Add the message types MATMAS and CREMAS, as shown in the following tables:

Fields and Values for Message Type MATMAS

Field Value Example

Sender Logical System of SAP ERP<SID>CLNT<Client Number>

QV5CLNT340

Receiver Logical System of SAP Sourcing FRUESO

Message Type MATMAS

Fields and Values for Message Type CREMAS

Field Value Example

Sender Logical System of SAP ERP<SID>CLNT<Client Number>

QV5CLNT340

Receiver Logical System of SAP Sourcing FRUESO

Message Type CREMAS


4.9 Maintain Distribution Model

48/134 PUBLIC 2011-08-18

6. If you want to distribute all materials or vendors, you can skip this step. If you do not want to

distribute all materials or vendors, you must apply filters as follows.

1. In transaction BD64, select your distribution model and switch to change mode.

2. Expand your distribution model and double-click No Filter Set for the message type MATMAS

(material master) or CREMAS (vendor master).

3. In the dialog box that appears, choose Create Filter Group.

4. Enter values for the possible filter groups.

4.10 Verify Transaction Types

NOTE

This is carried out by your ERP expert, consultant, or key user in collaboration with the SAP

Service Delivery consultant.

For purchase orders, contracts, and scheduling agreements to be created correctly, the transaction

types must be maintained identically in SAP ERP and SAP Sourcing.

Procedure

Purchase Order

1. In Customizing for Materials Management (transaction SPRO), choose Purchasing Purchase Order

Define Document Types . Note the entry for purchase order in the Type column.

2. Log on to SAP Sourcing as the enterprise user or as a user with system administration rights. Choose

Setup. On the System Setup tab, find the Integration section and click Transaction Type. Note the entry for

purchase order in the External ID column.

3. Verify that the entry in SAP Sourcing matches the entry in SAP ERP.

Contract

1. In Customizing for Materials Management (transaction SPRO), choose Purchasing Contract Define

Document Types . Note the entry for contract in the Type column.



contract in the External ID column.


Scheduling Agreement

1. In Customizing for Materials Management (transaction SPRO), choose Purchasing Scheduling Agreement

Define Document Types . Note the entry for scheduling agreement in the Type column.


4.10 Verify Transaction Types

2011-08-18 PUBLIC 49/134



scheduling agreement in the External ID column.


4.11 Verify Value List Values

NOTE



The value list values for vendor account group and text ID in SAP Sourcing must match the values in

SAP ERP. A set of values is delivered with SAP Sourcing, but you may have to update them or add new

values to match the values in SAP ERP.

Procedure

NOTE

When editing the CSV files for value list values, be sure to enclose any values starting with leading

zeros within double quotation marks; otherwise, the leading zeros will be lost.

Text ID: Header Texts

1. In Customizing for Materials Management (transaction SPRO) in SAP ERP, choose Purchasing RFQ/

Quotation Texts for RFQs/Quotations Define Text Types for Header Texts .


Setup. On the Master Data tab, find the Master Data section and click Value List Types and Values. In the

list of value list types, click Header Text ID.

3. Verify that the text IDs that are used in RFQs are available in SAP Sourcing.

4. Carry out steps 1 to 3 for the following documents:

■ Purchase order

■ Contract

■ Scheduling agreement

Text ID: Item Texts

1. In Customizing for Materials Management (transaction SPRO) in SAP ERP, choose Purchasing RFQ/

Quotation Texts for RFQs/Quotations Define Text Types for Item Texts .



list of value list types, click Item Text ID.

3. Verify that the text IDs that are used in RFQs are available in SAP Sourcing.


4.11 Verify Value List Values

50/134 PUBLIC 2011-08-18

4. Carry out steps 1 to 3 for the following documents:

■ Purchase order

■ Contract


NOTE

For the following documents, the item text IDs in Customizing for Integration with Other mySAP.com

Components (transaction SPRO) under E-Sourcing Settings for E-Sourcing Integration must not be used

in SAP Sourcing. Otherwise, the document header/item text or document number from SAP

Sourcing will be missing in the document texts in SAP ERP.

■ RFQ

■ Purchase order

■ Contract


4.12 Verify Pricing Conditions

NOTE



The pricing conditions that are used in business documents in SAP Sourcing must match those in SAP

ERP (for example, FR00 in SAP Sourcing and FR00 in SAP ERP), or must be assigned to those in SAP

ERP (for example, ABCD in SAP Sourcing is assigned to FR00 in SAP ERP).

Procedure

1. In Customizing for Materials Management (transaction SPRO) in SAP ERP, choose Purchasing

Conditions Define Price Determination Process Define Condition Types Define Condition Type .

2. In Customizing for Materials Management (transaction SPRO) in SAP ERP, choose Integration with Other

mySAP.com Components E-Sourcing Assign Condition Types .


Setup. On the Master Data tab, find the Master Data section and click Pricing Conditions.

4. Verify that all pricing conditions that are used in business documents in SAP Sourcing are available

in SAP ERP or are assigned to pricing condition types in SAP ERP.

More Information

Create Pricing Conditions in SAP Sourcing [page 76]

Assign Pricing Conditions in SAP Sourcing to Pricing Condition Types in SAP ERP [page 77]


4.12 Verify Pricing Conditions

2011-08-18 PUBLIC 51/134

4.13 Verify ISO Codes of Currencies, Units of Measure, and Countries

NOTE



For all sent messages to be understood correctly in both SAP ERP and SAP Sourcing, the ISO codes of

currencies and units of measure in SAP Sourcing must match the ISO codes of currencies and units of

measure in SAP ERP, and the display name IDs of countries in SAP Sourcing must match the ISO codes

of countries in SAP ERP.

Currencies

When currencies are sent from SAP ERP to SAP Sourcing or vice versa, the currency is always

communicated via its ISO code. Therefore, if a currency is used in an integrated document, the currency

must have the same ISO code in both SAP ERP and SAP Sourcing. A unique ISO code is already assigned

to each currency that is delivered with SAP Sourcing. However, if you add currencies, be sure to assign

the same ISO code to the currency in both SAP Sourcing and SAP ERP.

You can assign an ISO code to multiple currencies in SAP ERP. By identifying one of the currencies as

the primary currency in SAP ERP, you can define which currency is used by SAP ERP for this ISO code.

In SAP Sourcing, you must assign the ISO code to the same currency that is identified as the primary

currency in SAP ERP. Otherwise, SAP Sourcing may not be able to find the appropriate currency.

Units of Measure

When purchasing document line items that contain units of measure are sent from SAP ERP to SAP

Sourcing or vice versa, the unit of measure is always communicated via its ISO code. Therefore, if a

unit of measure is used in an integrated document, the unit of measure must have the same ISO code

in both SAP ERP and SAP Sourcing. A unique ISO code is already assigned to each unit of measure that

is delivered with SAP Sourcing. However, if you add units of measure, be sure to assign the same ISO

code to the unit of measure in both SAP Sourcing and SAP ERP.

You can assign an ISO code to multiple units of measure in both SAP Sourcing and SAP ERP. By

identifying one of the units of measure as the primary unit of measure, you can define which unit of

measure is used by the system for this ISO code. Be sure to identify the same primary unit of measure

for the ISO code in both SAP Sourcing and SAP ERP. Otherwise, a line item could be processed using

the incorrect unit of measure in one of the systems.

EXAMPLE

For the ISO code GRM, you have identified the primary unit of measure as G (gram) in SAP ERP,

but as GC (Celsius) in SAP Sourcing. When a line item with the unit of measure G (gram) in SAP

ERP is sent to SAP Sourcing, its ISO code GRM is sent to SAP Sourcing. Based on your setting in

SAP Sourcing, the ISO code GRM is interpreted as the unit of measure GC (Celsius). When the



52/134 PUBLIC 2011-08-18

line item is returned to SAP ERP, its ISO code GRM is sent to SAP ERP, where it is interpreted as

G (gram). Though the unit of measure has not changed in SAP ERP, the line item has been

processed with the incorrect unit of measure in SAP Sourcing.

Within the limits of the SAP Sourcing business rules, you can change the unit of measure in a line item.

However, if you choose another unit of measure with the same ISO code as the original, the change

will be lost when the line item is returned to SAP ERP.

Countries

When countries are sent from SAP ERP to SAP Sourcing, the country is always communicated via its

ISO code. Therefore, if a country is used in an integrated document, the ISO code of the country in

SAP ERP must match the display name ID of the country in SAP Sourcing. In the standard system, all

countries are set up correctly. However, if you add countries, be sure that the ISO code for the country

in SAP ERP matches the display name ID of the country in SAP Sourcing.

Procedure

1. In Customizing for SAP NetWeaver (transaction SPRO) General Settings Currencies Check Currency

Codes , verify the ISO codes for the relevant currencies.


Setup. On the Master Data tab, find the Master Data section and click Currencies. For each relevant

currency, verify that the ISO code is the same as in SAP ERP. If an ISO code is assigned to multiple

currencies in SAP ERP, verify in SAP Sourcing that the ISO code is assigned to the same currency

that is identified as the primary currency in SAP ERP.

3. In Customizing for SAP NetWeaver General Settings Check Units of Measurement , verify the ISO codes

for the relevant units of measure. If an ISO code is assigned to multiple units of measure, identify

one of the units of measure as the primary unit of measure.


Setup. On the Master Data tab, find the Master Data section and click Unit of Measure. For each relevant

unit of measure, verify that the ISO code is the same as in SAP ERP. If an ISO code is assigned to

multiple units of measure, verify that the default unit of measure for the ISO code is the same as

the primary unit of measure in SAP ERP.

5. In Customizing for SAP NetWeaver General Settings Set Countries Define Countries in mySAP

Systems , go to the details screen for each country involved in ALE distribution and verify the ISO

code.



value list type list, choose Country. For each relevant country, verify that the display name ID in

SAP Sourcing matches the ISO code in SAP ERP.



2011-08-18 PUBLIC 53/134

4.14 Verify Incoterms

NOTE

This is carried out by your ERP expert or consultant in collaboration with the SAP Service Delivery

consultant.

For business documents (for example, purchase orders) to be created correctly, the Incoterms must be

maintained identically in SAP ERP and SAP Sourcing. If you add Incoterms or change the Incoterms

locations in SAP ERP or SAP Sourcing, be sure to add the Incoterms or update the Incoterms locations

identically in SAP Sourcing or SAP ERP.

Procedure

1. In Customizing for Materials Management (transaction SPRO), choose Purchasing Vendor Master

Check Incoterms .


Setup. On the Master Data tab, find the Master Data section and click Incoterms.

3. Verify that each Incoterm exists in SAP ERP and in SAP Sourcing. For each Incoterm, if the Location

Mandatory checkbox is selected in SAP ERP, verify that the Location field in SAP Sourcing is set to

Yes. If the Location Mandatory checkbox is not selected in SAP ERP, verify that the Location field in SAP

Sourcing is set to No.

4.15 Define External System

NOTE


consultant.

An external system represents an SAP ERP system that is integrated with SAP Sourcing.

Prerequisites

The SAP ERP system must exist before you create it as an external system in SAP Sourcing.

Procedure

1. Find the logical system name of the SAP ERP system that you want to integrate with SAP Sourcing.

You do this as follows:

1. Log on to the SAP ERP system that you are integrating with SAP Sourcing.

2. In Customizing for IDoc Interface / Application Link Enabling (ALE) (transaction SALE), choose

Basic Settings Logical Systems Assign Logical System to Client .

3. Select the client representing the integrated SAP ERP system and choose Details.

4. Note down the value of the Logical System field. Generally, it is in the format <System

ID>CLNT<Client Number>.


4.14 Verify Incoterms

54/134 PUBLIC 2011-08-18

NOTE

Keep this value safe because you will need it in steps 2 and 3 below, and also in Define Vendor

Account Groups [page 55].

2. Define the external system in SAP Sourcing. You do this as follows:


2. Choose Setup.

3. On the System Setup tab, find the Integration section and click External Systems.

4. Choose New.

5. Enter the required information as shown in the following table.

Field Value

External ID Enter the logical system name of the SAP ERP system. This is the value that you noted down in step 1.

NameDescription

Choose the desired language from the dropdown and enter a name and description in that language.


3. Define a system property for the external system. This represents the SAP ERP system that is

integrated with SAP Sourcing for business documents. You do this as follows:


2. Choose Setup.


4. Choose New.

5. Create the system property as shown in the following table.

Field Value

Set odp.doc

Name odp.doc.integration.external_system

Value Enter the logical system name of the SAP ERP system. This is the value that you noted down in step 1.


4.16 Define Vendor Account Groups

NOTE


consultant.

A vendor account group is a classifying feature of vendor master records in SAP ERP. You need to define

vendor account groups in SAP Sourcing to ensure that vendors can be published from SAP Sourcing

to SAP ERP successfully, and vice versa. The vendor account group determines the following:

■ Interval from which a unique number is assigned to a vendor



2011-08-18 PUBLIC 55/134

■ Whether the number is assigned by the user (external number assignment) or by the system

(internal number assignment)

Prerequisites

The vendor account groups must exist in SAP ERP before you create them in SAP Sourcing.

Procedure

1. Find the relevant vendor account group values in SAP ERP. You do this as follows:

1. Log on to the SAP ERP system that you are integrating with SAP Sourcing.

2. In Customizing for Financial Accounting (New) (transaction SPRO), choose Accounts Receivable and

Accounts Payable Vendor Accounts Master Data Preparations for Creating Vendor Master Data Assign

Number Ranges to Vendor Account Groups .

3. For each vendor account group that you want to define in SAP Sourcing, note down the value

in the Group field.

4. For the same vendor account groups, click the value help for the Number Range field and note

down whether the number range interval is internal or external.

2. Define the vendor account groups in SAP Sourcing. You do this as follows:


2. Choose Setup.

3. On the Master Data tab, find the Organization and Accounting Information section and click Vendor

Account Group.

4. Choose New.

5. Create the vendor account group as shown in the following table.

Field Value

External ID Enter any unique value.

RECOMMENDATION

If you are integrating suppliers in multiple SAP ERP systems, we recommend using a naming convention for the external ID that identifies the vendor account group and the SAP ERP system of the vendor account group, for example, <Vendor Account Group><System ID>CLNT<Client Number>.

NameDescription

Choose the desired language from the dropdown and enter a name and description in that language.

External System

Enter the logical system name of the SAP ERP system. This is the value that you noted down in step 1 of Define External System [page 54].

External Vendor Account Group

Enter the value from the Group field in SAP ERP. This is the value that you noted down in step 1 above.

Number Range Select Internal or External to match the number range in SAP ERP. This is the setting that you noted down in step 1 above.




56/134 PUBLIC 2011-08-18

4.17 Carry Out Initial Load of Materials and Vendors from SAP ERP to SAP Sourcing

Procedure

NOTE


Carry Out Initial Load of Materials

NOTE

You can prevent the sending of materials without purchasing data to SAP Sourcing by

implementing the Business Add-In (BAdI) IDOC_CREATION_CHECK in SAP ERP. Sample code is

provided below.

METHOD if_ex_idoc_creation_check~idoc_data_check.

DATA: ls_idoc_data TYPE edidd.

IF idoc_control-rcvprn = 'FRWESO' "System name defined in BD64

AND idoc_control-mestyp = 'MATMAS' "Defined in WE20

AND idoc_control-idoctp = 'MATMAS05'. "Defined in WE20

IF cl_bbp_es_settings=>es_erp_active( ) = 'X'.

READ TABLE idoc_data WITH KEY segnam = 'E1MARCM'

TRANSPORTING NO FIELDS.

IF sy-subrc <> 0.

CLEAR create_idoc.

ENDIF.

ENDIF.

ENDIF.

ENDMETHOD.

NOTE

The following procedure describes how to carry out the initial load manually. You can also carry

out the initial load in the background. You do this in transaction SM36 by scheduling a background

job for program RBDSEMAT. You can monitor the background job in transaction SM37.

1. In transaction BD10, enter your data as shown in the following table:

Parameters and Values for Sending Materials

Field Value Example

Material Enter the materials that you want to send.

Message Type MATMAS

Logical System Logical system of SAP Sourcing FRUESO

Number of Materials per Process Remove any value in this field and leave it blank.

2. Choose Execute.



2011-08-18 PUBLIC 57/134

3. This step is necessary only if you selected the output mode Collect IDocs when maintaining the

partner profile. For more information, see Maintain Partner Profile [page 47].

In transaction SE38, execute program RSEOUT00 to process the IDocs. Enter the parameters as shown

in the following table. You can also schedule this program as a background job.

Parameters and Values for Program RSEOUT00

Parameter Value

Basic Type MATMAS05

Port of Receiver Enter the port that you created in Maintain Port Definition [page 46].

Logical Message MATMAS

Maximum Number of IDocs Enter the number of IDocs to be exported in a single message. The number depends greatly on the message size of the single IDoc. The number can be higher for small objects, but should be lower for large objects such as materials. If the message becomes too large, more memory and time is required for extraction in SAP ERP and for mapping in SAP NetWeaver Process Integration. For materials, we have found that bundling approximately 100 IDocs leads to optimum throughput when sending only client-level data.

Carry Out Initial Load of Vendors

NOTE

The following procedure describes how to carry out the initial load manually. You can also carry

out the initial load in the background. You do this in transaction SM36 by scheduling a background

job for program RBDSECRE. You can monitor the background job in transaction SM37.

1. In transaction BD14, enter your data as shown in the following table:

Parameters and Values for Sending Vendors

Field Value Example

Account Number of Vendor Enter the vendors that you want to send.

Message Type CREMAS

Target System Logical system of SAP Sourcing FRUESO

Number of Vendors per Process Remove any value in this field and leave it blank.

2. Choose Execute.






Parameter Value

Basic Type CREMAS05


Logical Message CREMAS



58/134 PUBLIC 2011-08-18

Parameter Value

Maximum Number of IDocs Enter the number of IDocs to be exported in a single message. The number depends greatly on the message size of the single IDoc. The number can be higher for small objects, but should be lower for large objects. If the message becomes too large, more memory and time is required for extraction in SAP ERP and for mapping in SAP NetWeaver Process Integration.

Follow-Up Activities

1. In transaction WE02, check the IDocs by entering criteria such as the date and time created, direction,

and basic type.

2. After a full batch of files is imported, verify the success of the import in SAP Sourcing as follows:

1. Log on to SAP Sourcing as the enterprise user or as a user with system administration rights.

2. Choose Setup.

3. On the System Administration tab, find the Import and Export Tools section and click Import Data.

4. In the Data Import List dropdown, choose All Data Imports (if not already selected).

5. Correct any file errors and subsequent errors due to missing dependencies. Be sure to correct

all errors before importing the next batch of files.

More Information


Mapping of Material Master Data from SAP ERP to SAP Sourcing [page 90]

Mapping of Vendor Master Data from SAP ERP to SAP Sourcing [page 91]

4.18 Transfer Changes to Materials or Vendors from SAP ERP to SAP Sourcing

NOTE


Whenever there is any change in the material master data or vendor master data, change pointers are

needed to generate IDocs from the application documents.

Procedure

Maintain Number Range for Change Pointers

Internal numbers are assigned to change pointers for unique identification. The system can only

generate the numbers if a number range is maintained for number range interval 01.

1. In transaction BDCP, choose Display Intervals to determine whether a number range is already

maintained for interval 01.

2. If no number range is maintained for interval 01, choose Interval Maintain .

3. On the Maintain Number Range Intervals screen, choose Insert Interval.

4. Enter interval 01 and a number range, and choose Insert.



2011-08-18 PUBLIC 59/134

5. To verify that the entry is error-free, choose Interval Check .


Activate Change Pointers – Generally

1. In Customizing for IDoc Interface / Application Link Enabling (ALE) (transaction SALE), choose Modelling

and Implementing Business Processes Master Data Distribution Replication of Modified Data Activate Change

Pointers - Generally .

2. Select the Change Pointers Activated – Generally checkbox.


Activate Change Pointers for Message Types

1. In Customizing for IDoc Interface / Application Link Enabling (ALE) (transaction SALE), choose Modelling

and Implementing Business Processes Master Data Distribution Replication of Modified Data Activate Change

Pointers for Message Types .

2. For each relevant message type, select the Active checkbox.


Create IDocs from Change Pointers

NOTE

The following procedure describes how to create IDocs from change pointers manually. You can

also create IDocs from change pointers in the background. You do this in transaction SM36 by

defining a variant and then scheduling a background job for program RBDMIDOC. This program

reads the change pointers and generates IDocs from them.

1. In transaction BD21, enter message type MATMAS to send IDocs for changes to materials, or

CREMAS to send IDocs for changes to vendors.

2. Choose Execute.






Parameter Value

Basic Type MATMAS05 for materials or CREMAS05 for vendors


Logical Message MATMAS for materials or CREMAS for vendors

Maximum Number of IDocs Enter the number of IDocs to be exported in a single message. The number depends greatly on the message size of the single IDoc. The number can be higher for small objects, but should be lower for large objects such as materials. If the message becomes too large, more memory and time is required for extraction in SAP ERP and for mapping in SAP NetWeaver



60/134 PUBLIC 2011-08-18

Parameter ValueProcess Integration. For materials, we have found that bundling approximately 2500 IDocs leads to optimum throughput when sending only client-level data.

More Information


4.19 Publish Suppliers from SAP Sourcing to SAP ERP

NOTE


This step is necessary only if you want to publish suppliers from SAP Sourcing to SAP ERP.

Prerequisites

To publish suppliers from SAP Sourcing to SAP ERP, all non-integrated fields for vendor master data

must be optional in SAP ERP (that is, they must not require a value). If they are mandatory, the vendor

will not be created in SAP ERP because SAP Sourcing provides values only for integrated fields. You

can use transaction WE02 in SAP ERP to view the corresponding IDoc CREMAS05 and its log.

Procedure

Maintain Account Group

1. In Customizing for Integration with Other mySAP.com Components (transaction SPRO), choose E-Sourcing

Settings for E-Sourcing Integration .

2. Under Vendor Publishing, enter the account group that is used to identify suppliers published from

SAP Sourcing to SAP ERP.


4. Choose Setup.

5. On the Master Data tab, find the Master Data section and click Value List Types and Values.

6. Choose Vendor Account Group.

7. Choose Edit.

8. Choose Add and enter the same account group that you entered in step 2.

9. In the SAP ERP Customizing client, activate business configuration set BBP_ES_VENDOR_MASTER in

transaction SCPR20.

NOTE

When a supplier is published from SAP Sourcing to SAP ERP, the number range that is entered

in the External ID field in SAP Sourcing is not validated against the account group number range

that is configured in SAP ERP. If you want to validate the number range in SAP Sourcing, you

must use custom scripting in SAP Sourcing for your own specific validation.



2011-08-18 PUBLIC 61/134

Assign Supplier Administrator Profile to Users Designated to Publish Suppliers

1. In SAP Sourcing, choose Setup.

2. On the System Administration tab, find the Accounts and Security section and click Internal User Accounts.

3. On the Security tab, select the Supplier Administrator profile and save your entries.

Allow Republishing of Suppliers

If a supplier was published unsuccessfully from SAP Sourcing to SAP ERP, a user who is assigned the

Tenant Administrator profile can allow it to be republished after correcting the errors that caused the

supplier to be published unsuccessfully. In this profile, make sure that the Manage Integration of Suppliers

with External Systems permission is set to Allow, as described below.

1. In SAP Sourcing, choose Setup.

2. On the System Administration tab, find the Accounts and Security section and click Security Profiles.

3. Open the Tenant Administrator profile.

4. On the Access Rights tab, find the Show Only field and choose Supplier Management from the dropdown.

5. Check that the Manage Integration of Suppliers with External Systems permission is set to Allow.

For more information about republishing suppliers, see SAP Library for SAP Sourcing on SAP Help

Portal at http://help.sap.com SAP Business Suite SAP Sourcing Integration of SAP Sourcing and SAP ERP

Master Data Publishing Suppliers from SAP Sourcing to SAP ERP .

More Information


Mapping of Supplier Master Data from SAP Sourcing to SAP ERP [page 93]



62/134 PUBLIC 2011-08-18

http://help.sap.com

5 Integration of Suppliers with Multiple SAP ERP Systems

The steps in this chapter are necessary only if you want to publish suppliers from SAP Sourcing to

multiple SAP ERP systems, and vice versa. If you are integrating SAP Sourcing with a single SAP ERP

system, you can skip this chapter and proceed to the Business Process Integration [page 71] chapter.

5.1 Enable Integration of Suppliers with Multiple SAP ERP Systems

NOTE


In this step, you define a system property to enable the integration of suppliers with multiple SAP ERP

systems.

Procedure


2. Choose Setup.


4. Choose New.

5. Create the system property as shown in the following table.

Field Value

Set odp.doc

Name odp.doc.integration.enable.suppliers_to_from_multi_external_systems

Value TRUE


5.2 Define External System for Each SAP ERP System

Procedure

NOTE


consultant.


5.1 Enable Integration of Suppliers with Multiple SAP ERP Systems

2011-08-18 PUBLIC 63/134

Define an external system in SAP Sourcing for each SAP ERP system that you want to integrate with

SAP Sourcing. To do this, follow the steps in Define External System [page 54].

5.3 Define Vendor Account Groups for Each SAP ERP System

Procedure

NOTE


consultant.

Define the vendor account groups in SAP Sourcing for each SAP ERP system that you want to integrate

with SAP Sourcing. To do this, follow the steps in Define Vendor Account Groups [page 55].

5.4 Configure Each SAP ERP System

Procedure

NOTE



Carry out the following steps for each SAP ERP system that you want to integrate with SAP Sourcing.

1. Apply SAP Note 1458469.

2. Implement Business Add-In (BAdI) BADI_BBP_ES_CHANGE_DATA. This is required to transfer

Customizing data and master data from each SAP ERP system to SAP Sourcing. The enhancement

spot is BBP_ES_EXT_EXTRACTION.

Manipulate the external ID of the company codes and purchasing organizations in the BAdI before

replicating the company codes and purchasing organizations from SAP ERP to SAP Sourcing.

3. Extract the company codes and purchasing organizations, and import them from SAP ERP to SAP

Sourcing. For more information, see the following:

■ Extract Customizing Data from SAP ERP [page 41]

■ Carry Out Initial Load of Customizing Data to SAP Sourcing [page 43]

4. Configure the replication of vendors (suppliers) to/from SAP-Sourcing.

NOTE

You need to make only the settings for vendors (message type CREMAS), not materials

(message type MATMAS).

For more information, see the following:

■ Define Logical System [page 44]

■ Maintain RFC Destination [page 45]


5.3 Define Vendor Account Groups for Each SAP ERP System

64/134 PUBLIC 2011-08-18


■ Maintain Port Definition [page 46]

■ Maintain Partner Profile [page 47]

■ Maintain Distribution Model [page 48]

5.5 SAP NetWeaver Process Integration

5.5.1 Register Each SAP ERP System

Procedure

NOTE


In the System Landscape Directory (SLD), register each SAP ERP system that you want to integrate

with SAP Sourcing. To do this, carry out steps 3 and 5 in Set Up System Landscape Directory [page 23].

5.5.2 Define RFC Destination and Port for Each SAP ERP System

Procedure

NOTE


Follow the steps in Define RFC Destination and Port [page 24] for each SAP ERP system that you want to

integrate with SAP Sourcing.

5.5.3 Import Each SAP ERP System from System Landscape Directory to Integration Builder

Procedure

NOTE


1. In the process integration tools (transaction SXMB_IFR), log on to the Integration Builder.

2. Under Communication Component, right-click Business System and choose Assign Business System...

3. In the dialog box that appears, choose Continue Continue , and select the business system that

represents the SAP ERP system that you want to integrate with SAP Sourcing.

4. Deselect Create Communication Channels Automatically.

5. Click the value help for the Add to Scenario field, select the configuration scenario, and choose

Apply.



2011-08-18 PUBLIC 65/134

6. Choose Finish.

7. Repeat for each SAP ERP system that you want to integrate with SAP Sourcing.

5.5.4 Send Supplier Master from SAP Sourcing to Multiple SAP ERP Systems

Procedure

NOTE


In the process integration tools (transaction SXMB_IFR), log on to the Integration Builder and then

open the configuration scenario that you configured for a single SAP ERP system. This is the

configuration scenario that you created in Configure Integration Scenarios [page 25].

Modify Receiver Determination

1. In the configuration scenario, search for the receiver determination shown in the following table.

Field Value

Communication Component (Sender) SAP Sourcing system

Interface MI_OB_Supplier

Namespace http://sap.com/xi/Esourcing/SRMJS

2. In the Configured Receivers section, click the dropdown and choose Insert Receiver to add an SAP ERP

business system.

3. In the Communication Component field, choose the SAP ERP business system from the value help.

4. Open the value help for the Condition field.

5. In the dialog box that appears, open the value help for the Left Operand field.

6. Select XPath and make the following entry:

/p1:MT_Supplier_Export/fcidataexport/objects/object/fields/LOG_SYS

7. In the Right Operand field, enter the logical system of the SAP ERP system, as specified in the SLD.


9. Repeat steps 2 to 8 for each SAP ERP system that you want to integrate with SAP Sourcing.

Copy Interface Determination

1. In the configuration scenario, search for the interface determination shown in the following table.

Field Value

Communication Component (Sender) SAP Sourcing system

Interface MI_OB_Supplier


Communication Component (Receiver) SAP ERP system

2. Choose Copy Object.



66/134 PUBLIC 2011-08-18

3. In the Communication Component field for the receiver, choose the SAP ERP business system from the

value help. This is the SAP ERP system to which you want to connect.

4. In the Add to Scenario field, choose the configuration scenario from the value help.

5. Choose Copy.


Copy Communication Channel

1. In the configuration scenario, search for the receiver communication channel

CT_Generic_Receiving_IDOC_Channel_For_ERP_Inbound_IDOCs.

NOTE

You may have renamed this communication channel.


3. In the Communication Component field, choose the SAP ERP business system from the value help. This

is the SAP ERP system that you imported from the SLD to the Integration Builder.

4. Rename the communication channel.

5. Choose Copy.

6. Switch to edit mode.

7. Maintain the RFC destination and port as shown in the following table.

Field Value

RFC Destination Enter the SAP ERP logical system.

Port SAP<system ID of SAP ERP system>



Copy Receiver Agreement

1. In the configuration scenario, search for the receiver agreement shown in the following table.

Field Value

Communication Component (Sender)

SAP Sourcing system

Communication Component (Receiver)

SAP ERP system

Interface CREMAS.CREMAS05

Namespace urn:sap-com:document:sap:idoc:messages

Receiver Communication Channel

CT_Generic_Receiving_IDOC_Channel_For_ERP_Inbound_IDOCs


3. In the Communication Component field for the receiver, choose the SAP ERP business system from the

value help. This is the SAP ERP system to which you want to connect.


5. Choose Copy.



2011-08-18 PUBLIC 67/134

Ignore any error that the communication channel does not match the receiver.


7. Choose the receiver communication channel that you created in Copy Communication Channel above.



5.5.5 Send Vendor Master from Multiple SAP ERP Systems to SAP Sourcing

Procedure

NOTE


In the process integration tools (transaction SXMB_IFR), log on to the Integration Builder and then

open the configuration scenario that you configured for a single SAP ERP system. This is the

configuration scenario that you created in Configure Integration Scenarios [page 25].

Copy Receiver Determination

1. In the configuration scenario, search for the receiver determination shown in the following table.

Field Value

Communication Component (Sender) SAP ERP system




3. In the Communication Component field for the sender, choose the SAP ERP system from the value help.

This is the SAP ERP system to which you want to connect.

4. Choose Copy.


Copy Interface Determination

1. In the configuration scenario, search for the interface determination shown in the following table.

Field Value




Communication Component (Receiver) SAP Sourcing system






68/134 PUBLIC 2011-08-18


5. Choose Copy.


Copy Communication Channel

1. In the configuration scenario, search for the sender communication channel

CT_Generic_Sending_HTTP_Channel_For_ERP_Outbound_IDOCs.

NOTE

You may have renamed this communication channel.


3. In the Communication Component field, choose the SAP ERP business system from the value help. This

is the SAP ERP system that you imported from the SLD to the Integration Builder.

4. If you wish, rename the communication channel.


6. Choose Copy.


Copy Sender Agreement

1. In the configuration scenario, search for the sender agreement shown in the following table.

Field Value

Communication Component (Sender)

SAP ERP system



Sender Communication Channel CT_Generic_Sending_HTTP_Channel_For_ERP_Outbound_IDOCs





5. Choose Copy.

Ignore any message to specify a communication channel, or any message that the communication

channel does not match the sender.


7. Choose the sender communication channel that you created in Copy Communication Channel above.



Copy Receiver Agreement

1. In the configuration scenario, search for the receiver agreement shown in the following table.



2011-08-18 PUBLIC 69/134

Field Value


Communication Component (Receiver) SAP Sourcing system

Interface MI_IB_Supplier


Receiver Communication Channel CT_Supplier_Receiving_File_Channel_For_ES





5. Choose Copy.




70/134 PUBLIC 2011-08-18

6 Business Process Integration

6.1 SAP ERP RFQ to SAP Sourcing RFP


6.1.1 Integration Architecture for SAP ERP RFQ to SAP Sourcing RFP

In the following figure, an RFQ is sent from SAP ERP, triggering the creation of an RFP in SAP Sourcing.

A receipt containing the RFP ID is sent back from SAP Sourcing.

Figure 4: Integration Architecture for SAP ERP RFQ to SAP Sourcing RFP

More Information

Configuring SSL/HTTPS [page 126]

Mapping of SAP ERP RFQ to SAP Sourcing RFP [page 95]




2011-08-18 PUBLIC 71/134


6.1.2 Configure IDoc for RFQ

Procedure

NOTE


Carry out the following steps in SAP ERP.

1. In transaction SM59, set up the SAP NetWeaver Process Integration (SAP NetWeaver PI) hub as the

ABAP RFC destination.

2. In transaction BD54, maintain a logical system, using exactly the same name as the RFC that you

created in step 1.

3. In transaction WE21, define a transactional RFC port for the RFC, using exactly the same name as

the RFC that you created in step 1.

4. In transaction WE20, maintain a partner profile, using exactly the same name as the RFC that you

created in step 1.

1. Add outbound parameters as shown in the following table:

Fields and Values for Outbound Parameters

Field Value

Partner Role LS

Partner Type LS

Message Type REQOTE

2. On the Outbound Options tab, maintain your data as shown in the following table:

Fields and Values for Outbound Options

Field Value

Receiver Port Enter the port that you created in step 3

Packet Size 1

Transfer IDoc Immediately Select this checkbox

Basic Type ORDERS05

3. On the Message Control tab, maintain your data as shown in the following table:

Fields and Values for Message Control

Field Value

Application EA

Message Type NEU

Process Code ME12

6.1.3 Configure RFQ Output

Procedure

NOTE




72/134 PUBLIC 2011-08-18


1. In transaction MK01, create a pseudo vendor. This vendor is used to transfer RFQ data to SAP

Sourcing. When creating this vendor, you must pick an account group that allows an external

number range (which can be alphanumeric). In Customizing for Financial Accounting (transaction

SPRO) Accounts Receivable and Accounts Payable Vendor Accounts Master Data Preparations for Creating

Vendor Master Data Assign Number Ranges to Vendor Account Groups , you can check whether the account

group allows an external number range.

2. In Customizing for Integration with Other mySAP.com Components E-Sourcing Settings for E-Sourcing

Integration , enter the vendor from step 1 in the Vendor Ext. System field.

This entry indicates which vendor is to be taken as placeholder for SAP Sourcing. If an RFQ is

created with this vendor, the system realizes that the request has to be sent to SAP Sourcing. You

can use any existing vendor in the system; however, we recommend creating a new vendor exactly

for this purpose.

3. Define the partner role LS (logical system) for RFQ as shown in the following table. You do this in

Customizing for Materials Management Purchasing Messages Output Control Partner Roles per Message

Type Define Partner Roles for Request for Quotation .

Fields and Values for Partner Role

Field Value

Output Type NEU

Message Transmission Medium 6

Partner Function LS

4. In transaction MN01, configure the output control for the RFQ. Use output type NEU and key

combination Purch. Org./Vendor for EDI. This enables RFQs created with the supplier that you

maintained in step 2 to generate IDocs and transfer them to the SAP NetWeaver Process Integration

(SAP NetWeaver PI) hub. Maintain your data as shown in the following table.

Fields and Values for Output Control

Field Value

Vendor Enter the vendor that you maintained in step 2

Partner Function LS

Partner Enter the name of the SAP NetWeaver PI hub

Medium 6 (EDI)

Dispatch Time 4

Language Default

You may need to set this up for each purchasing organization to be integrated with SAP Sourcing.

5. Maintain an item text type for RFQs with the description SOURCING REF RFQ. You do this in

Customizing for Materials Management Purchasing RFQ/Quotation Texts for RFQs/Quotations Define

Text Types for Item Texts . This is used to populate SAP ERP RFQ and SAP Sourcing RFP cross-

reference information in the RFQ item text.



2011-08-18 PUBLIC 73/134


Integration , enter the ID of the item text type for RFQs from step 5.

NOTE

The field with this ID must not be used for any other purpose in SAP ERP. Otherwise, the

document header/item text or the document number from SAP Sourcing will be missing in

the document text in SAP ERP.

7. Maintain a text type for purchase requisitions with the description SOURCING REF RFP. You do

this in Customizing for Materials Management Purchasing Purchase Requisition Texts for Purchase

Requisitions Define Text Types . This is used to populate SAP ERP RFQ and SAP Sourcing RFP cross-

reference information in the purchase requisition item text.


Integration , enter the ID of the text type for purchase requisitions from step 7.

NOTE

The field with this ID must not be used for any other purpose in SAP ERP. Otherwise, the

document header/item text or the document number from SAP Sourcing will be missing in

the document text in SAP ERP.

6.2 SAP Sourcing RFP Award to SAP ERP Purchase Order


6.2.1 Integration Architecture for SAP Sourcing RFP Award to SAP ERP Purchase Order

In the following figure, business is awarded in SAP Sourcing, and a synchronous call is sent to the back

end to create a purchase order. The receipt back contains the purchase order number. It is assumed

that the SAP NetWeaver Process Integration (SAP NetWeaver PI) server or Web service on the back end

is listening on HTTPS.



74/134 PUBLIC 2011-08-18


Figure 5: Integration Architecture

More Information

Configuring SSL/HTTPS [page 126]

Mapping of SAP Sourcing RFP Award to SAP ERP Purchase Order [page 103]


6.2.2 Define Item Text for Purchase Order

Procedure

NOTE


Create a new purchase order item text to store the SAP Sourcing specific cross-reference information

as follows:

1. In Customizing for Materials Management (transaction SPRO), choose Purchasing Purchase Order

Texts for Purchase Orders Define Text Types for Item Texts .

2. Create a new record as shown in the following table:

Fields and Values for Item Text for Purchase Order

Field Value

Seq. No. Enter any two-digit unique numeric value.

Meaning Enter a description.



2011-08-18 PUBLIC 75/134

3. In Customizing for Integration with Other mySAP.com Components, choose E-Sourcing Settings for E-Sourcing

Integration .

4. Under Reference to ES Request for Proposal, enter the item text ID from step 2 in the Seq. No. Purch. Ord.

field.

NOTE

The item text ID for purchase order in Customizing for Integration with Other mySAP.com

Components under E-Sourcing Settings for E-Sourcing Integration must not be used in SAP

Sourcing. Otherwise, the document header/item text or the document number from SAP

Sourcing will be missing in the document text in SAP ERP.

6.3 SAP Sourcing RFP Award or Master Agreement to SAP ERP Outline Agreement

See also:

■ SAP Sourcing RFP Award to SAP ERP Outline Agreement [page 77]

■ SAP Sourcing Master Agreement to SAP ERP Outline Agreement [page 79]


6.3.1 Create Pricing Conditions in SAP Sourcing

NOTE


This step is necessary only if you do not extract the pricing condition types from SAP ERP as described

in Extract Customizing Data from SAP ERP [page 41].

Prerequisites

The corresponding pricing condition types exist in SAP ERP.

Procedure


2. Choose Setup.

3. On the Master Data tab, find the Master Data section and click Pricing Conditions.

4. Choose New.

5. Create the new pricing condition. Information is provided for certain fields in the following table.

The values for the other fields depend on your requirements.



76/134 PUBLIC 2011-08-18


Fields and Values for Pricing Condition

Field Value

Condition Type ID

Enter an ID, for example, FROO. It must be unique in SAP Sourcing, but can be the same as the corresponding pricing condition type ID in SAP ERP.

Name Choose the desired language from the dropdown and enter a name and description in that language.

EXAMPLE

You can use the description to explain to your suppliers how the pricing condition is used in the RFx process.

Description

Logical System If you imported the pricing conditions by uploading an XML file, the logical system is the SAP ERP system from which you imported the pricing conditions. If you create the pricing condition manually, choose the logical system from the value help.

6. Save your entries and create the next pricing condition.

7. Assign the pricing conditions to the integrated document type. For more information, see Check

Integrated Document Types for RFx and Contract [page 15].

ResultYou have completed the necessary master data configuration for integrating the pricing conditions.

The next step is to add the new pricing conditions to the integrated master agreement type. For more

information, see Configure Master Agreement Type to Transfer Pricing Conditions [page 79].

6.3.2 Assign Pricing Conditions in SAP Sourcing to Pricing Condition Types in SAP ERP

NOTE


This step is necessary only if you do not extract the pricing condition types from SAP ERP as described

in Extract Customizing Data from SAP ERP [page 41]. In addition, it is necessary only if the names of your

pricing condition types are different in SAP ERP and SAP Sourcing; for example, if the name of the

pricing condition in SAP Sourcing is RB00, but the name of the pricing condition type in your calculation

schema in SAP ERP is ZB00.

ProcedureAssign the pricing condition in SAP Sourcing to the corresponding pricing condition type in the

calculation schema in SAP ERP. You do this in Customizing for Integration with Other mySAP.com

Components (transaction SPRO) under E-Sourcing Assign Condition Types .

6.3.3 SAP Sourcing RFP Award to SAP ERP Outline Agreement

See also SAP Sourcing RFP Award or Master Agreement to SAP ERP Outline Agreement [page 76].




2011-08-18 PUBLIC 77/134


6.3.3.1 Integration Architecture for SAP Sourcing RFP Award to SAP ERP Outline Agreement

In the following figure, business is awarded in SAP Sourcing, and a synchronous call is sent to the back

end to create an outline agreement. The receipt back contains the outline agreement ID. It is assumed

that the SAP NetWeaver Process Integration (SAP NetWeaver PI) server or Web service on the back end

is listening on HTTPS.

Figure 6: Integration Architecture

More InformationConfiguring SSL/HTTPS [page 126]

Mapping of SAP Sourcing RFP Award to SAP ERP Outline Agreement [page 107]


6.3.3.2 Configure RFP Award to Transfer Pricing Conditions

NOTE


This step is necessary only if you want to transfer pricing conditions from an RFP award in SAP Sourcing

directly to an outline agreement or purchase order in SAP ERP.

PrerequisitesThe pricing conditions exist in SAP Sourcing. For more information, see Create Pricing Conditions in SAP

Sourcing [page 76].



78/134 PUBLIC 2011-08-18

Procedure


2. Choose Setup.

3. On the Document Setup tab, find the RFx section and click RFx Types.

4. In the list of RFx types, click the integrated type that you want to use to create integrated RFxs.

5. Choose Edit.

6. On the Integration tab, choose Add Pricing Condition in the pricing conditions table, select the pricing

conditions that you created in Create Pricing Conditions in SAP Sourcing [page 76], and choose OK.


NOTE

You can filter the available pricing conditions by the document type.

For pricing conditions to be copied from one document to the other, the pricing conditions must

exist in both document types. For example, if you want to create a master agreement from an RFP

award, the pricing conditions must exist in both the RFx and master agreement. If the RFx has

pricing conditions PCON1 and PCON2, and the master agreement has pricing conditions PCON1

and PCON3 (but not PCON2), only the data from PCON1 is copied from the RFP award to the

master agreement.

6.3.4 SAP Sourcing Master Agreement to SAP ERP Outline Agreement

See also SAP Sourcing RFP Award or Master Agreement to SAP ERP Outline Agreement [page 76].


6.3.4.1 Configure Master Agreement Type to Transfer Pricing Conditions

NOTE


This step is necessary only if you want to transfer an agreement with pricing conditions from SAP

Sourcing to a contract or scheduling agreement in SAP ERP.

Prerequisites

The pricing conditions exist in SAP Sourcing. For more information, see Create Pricing Conditions in SAP

Sourcing [page 76].

Procedure




2011-08-18 PUBLIC 79/134


2. Choose Setup.

3. On the Document Setup tab, find the Agreements section and click Master Agreement Types.

4. In the list of master agreement document types, click the integrated type that you want to use to

create integrated master agreements.

5. Choose Edit.

6. On the Integration Details tab, choose Add Pricing Condition in the pricing conditions table, select the

pricing conditions that you created in Create Pricing Conditions in SAP Sourcing [page 76], and choose

OK.


6.3.4.2 Set Up Item Text IDs for Contract and Scheduling Agreement

Procedure

NOTE



1. In Customizing for Integration with Other mySAP.com Components (transaction SPRO), choose E-Sourcing

Settings for E-Sourcing Integration .

2. Under Reference to ES Master Agreement, enter an item text ID for contract and scheduling agreement.

In the contract or scheduling agreement in SAP ERP, this text ID contains the document number

and document description of the master agreement or subagreement in SAP Sourcing.

RECOMMENDATION

We recommend defining a new text ID for this purpose. For contracts, you do this in

Customizing for Materials Management Purchasing Contract Texts for Contracts Define Text Types

for Item Texts . For scheduling agreements, you do this in Customizing for Materials

Management Purchasing Scheduling Agreement Texts for Scheduling Agreements Define Text Types for

Item Texts .

NOTE

The fields with the item text IDs for contract and scheduling agreement in Customizing for

Integration with Other mySAP.com Components E-Sourcing Settings for E-Sourcing Integration must not

be used for any other purpose in SAP ERP. Otherwise, the document header/item text or the

document number from SAP Sourcing will be missing in the document text in SAP ERP.

3. Under Reference to ES Request for Proposal, enter an item text ID for contract and scheduling agreement.

In the contract or scheduling agreement in SAP ERP, this text ID contains the document number

and document description of the request for proposal (RFP) in SAP Sourcing.



80/134 PUBLIC 2011-08-18

RECOMMENDATION

We recommend defining a new text ID for this purpose; see above.

NOTE

The fields with the item text IDs for contract and scheduling agreement in Customizing for

Integration with Other mySAP.com Components E-Sourcing Settings for E-Sourcing Integration must not

be used for any other purpose in SAP ERP; see above.

6.3.4.3 Block Integrated Fields from User Changes in SAP ERP

Procedure

NOTE


You can block integrated fields from user changes in SAP ERP in one of the following ways:

■ Importing the field selection keys ESSA and ESCO with their related settings to your system using

a Business Configuration (BC) Set. You do this in transaction SCPR20 by entering BC Set

BBP_ES_CONTRACT_FIELD_CONTROL and activating it.

■ Creating the field selection keys ESSA and ESCO manually by carrying out the following steps:

1. In Customizing for Materials Management (transaction SPRO), choose Purchasing Scheduling

Agreement Define Screen Layout at Document Level .

2. Select the field selection key ESSA and choose Details.

3. Set the fields in the following table to Display.

Field Selection Groups and Fields

Field Selection Group Fields

Basic Data, Item Plant, Short Text, Material Group, Material Description, Manufacturer Part Number

Terms of Delivery and Payment Terms of Payment (Days, Percent), Terms of Payment, Incoterms Part 1, Currency, Incoterms Part 2, Incoterms Item, Incoterms Part 2 Item

Administrative Data, Header Target Value, Purchasing Group, Start of Validity Period, Validity Period End

Quantity And Price Target Quantity, Unit of Measure, Price And Price Unit, Price Date, Order Price Unit (Purchasing), Condition Group

Reference Data, Item Purchase Requisition, Info Record, Request for Quotation, Vendor Material, Vendor Number

Administrative Data, Item Deletion Indicator

Delivery Monitoring Planned Delivery Time

Enjoy Fields Vendor, Supplying Plant



2011-08-18 PUBLIC 81/134

4. In Customizing for Materials Management, choose Purchasing Contract Define Screen Layout at

Document Level .

5. Select the field selection key ESCO and choose Details.

6. Repeat step 3 above.



82/134 PUBLIC 2011-08-18

7 Appendix

7.1 Troubleshooting

Procedure

The following table contains tips for troubleshooting the integration of SAP ERP and SAP Sourcing:

Troubleshooting Integration of SAP ERP and SAP Sourcing

Issue Solution

In data import, files are successfully created by SAP ERP and/or SAP NetWeaver Process Integration (SAP NetWeaver PI) and sent to SAP Sourcing, but they are not picked up by SAP Sourcing.

This implies an issue with the data import monitor process. Check that the scheduled task is configured correctly, including the Run As user, schedule settings, file system or FTP settings, and so on. For more information, see: ■ Extract Customizing Data from SAP ERP [page 41] ■ Carry Out Initial Load of Materials and Vendors from SAP

ERP to SAP Sourcing [page 57] ■ Transfer Changes to Materials or Vendors from SAP ERP to

SAP Sourcing [page 59]Also check the SAP Sourcing application server logs.

In data import, the files are successfully picked up by SAP Sourcing, but the import fails due to: ■ Empty file (also known as zero-byte file)

Empty files are identified by the importer, moved out of the queue, and notification is sent.

■ Corrupt fileCorrupt files are usually due to malformed XML inside the file. This is not generally expected because the files are machine-made.

■ Data validation failureData validation failures are anticipated conditions, and messages are provided.

Check the data import record for the file imported. You do this as follows:1. Log on to SAP Sourcing.2. Choose Setup.3. On the System Administration tab, find the Import and

Export Tools section and click Import Data.All data imports are displayed with basic information such as the result of the import, number of records imported successfully, and number of failed records. You can also filter the data imports by date.For detailed information about the import session, click the data import name to access the trace.txt file. Any pertinent errors and/or warnings are logged here. This trace file and the SAP Sourcing application server logs provide most data for troubleshooting import problems. You will need the trace file and SAP Sourcing application server logs if you contact SAP Sourcing support.

In data import, you get an error message that a default language value was not provided.

See Define Default Language Preferences for Localized Resource Strings [page 18].

In data import, you get a warning message about invalid or missing values in SAP Sourcing, but the data import continues successfully.

See Extract Customizing Data from SAP ERP [page 41].

7 Appendix

7.1 Troubleshooting

2011-08-18 PUBLIC 83/134

Issue Solution

You want to add table-based questions to an RFx, but you get an error message that the unit category No Dimension contains no units of measure.


2. Choose Setup.3. On the Master Data tab, find the Master Data section

and click Unit of Measure.4. Check that the unit category No Dimension exists,

and that one of the units of measure in this unit category is designated as the primary unit. This unit category usually contains units of measure such as EA and BOX.

HTTP requests are not fully read after timeout. See SAP Note 807000.

You want to publish suppliers from SAP Sourcing to SAP ERP, but the file export fails.

Check the SAP Sourcing application server logs because the error message that is displayed on the SAP Sourcing UI is also written to the application server logs, where more diagnostic information can generally be found.Also check the integrated system configuration object, which contains the settings used by the export process, including where to send the file. You can access the integrated system configuration object in SAP Sourcing as follows:1. Choose Setup.2. On the System Setup tab, find the Integration section

and click Integrated System Configuration.

An RFx is created in SAP Sourcing via import, but the file export fails when the receipt is sent to SAP ERP.

Check the trace.txt file and/or SAP Sourcing application server logs. For information about how to access the trace.txt file, see above.Also check the integrated system configuration object, which contains the settings used by the export process, including where to send the file. For information about how to access the integrated system configuration object, see above.

You want to enable the logging of synchronous messages in SAP NetWeaver PI from synchronous calls between SAP Sourcing and SAP ERP via SAP NetWeaver PI.

1. In the Integration Engine in SAP NetWeaver PI (transaction sxmb_adm), choose Integration Engine Configuration.

2. Choose Change Configuration.3. Add the parameter LOGGING_SYNC with the

category RUNTIME and the current value 1.

You want to publish master agreements or awards from SAP Sourcing to SAP ERP, but the HTTP publish process fails.

Enable the logging of synchronous messages in SAP NetWeaver PI. (For performance reasons, synchronous messages are not logged by default in SAP NetWeaver PI.)Check the monitoring tools in SAP NetWeaver PI and/or SAP ERP, and/or the application server logs in SAP Sourcing. This is because master agreements and awards are published from SAP Sourcing to SAP ERP via synchronous HTTP requests through SAP NetWeaver PI. When the publish process fails, the errors that are displayed on the SAP Sourcing UI can come from SAP

7 Appendix

7.1 Troubleshooting

84/134 PUBLIC 2011-08-18


Issue SolutionERP, SAP NetWeaver PI, or SAP Sourcing, depending on where the failure originated. Where possible, the source of the problem is clearly identified, but such context is not always readily available. SAP Sourcing writes whatever context it has to the application server logs.Also check the integrated system configuration object, which contains the settings used by the export process, including the SAP NetWeaver PI URL. For information about how to access the integrated system configuration object, see above.Analyze the payload XML that SAP Sourcing writes to the application server file system. The error message specifies the location and name of this file.Check that the HTTP J2EE ports to connect from the hosting SAP NetWeaver PI system are open.

You want to publish master agreements or awards from SAP Sourcing to SAP ERP, but get the following errors: ■ Error in ESO : class java.io.IOException Server

returned HTTP response code: 500 for URL http://host:port/sap/xi/adapter_plain?namespace=http://frictionless.esource.com/v2.0&interface=MI_ESI_OA&service=BS_FCI_TEST&QOS=BE&sap-user=&sap-password=&sap-client=xxx&sap-language=EN. Please contact your system administrator.

■ Error in PI: No receiver could be determined.

Make sure that the business service name, interface name, and namespace text are entered in SAP Sourcing in the same case as configured in SAP NetWeaver PI. For more information, see Edit Integrated System Configuration [page 17].

Outline agreements (OA) or purchase orders (PO) are not created correctly in SAP ERP. You want to log the RFC calls and debug.

1. Store the incoming data in global memory. You do this in Customizing for Integration with Other mySAP.com Components (transaction SPRO) E-Sourcing

Settings for E-Sourcing Integration by selecting the Activate Log checkbox. As a result, all data from SAP Sourcing (RFP award to PO, RFP award to OA, master agreement to OA) is stored in memory area es of database table INDX.

2. Using transaction BBP_ES_ANALYZE, analyze and reprocess the stored data. You do this by entering OA* for documents that have been created as outline agreements, or PO* for all incoming purchase orders. Then click the input help. For each OA or PO, the system displays the date and time of creation, and the RFX document number or master agreement/subagreement number. To display the data structure of any given OA or PO, and how it was processed by the corresponding RFC function module in SAP ERP, select the corresponding ID and choose Execute. You can then reprocess the OA or PO, or start debugging.

7 Appendix

7.1 Troubleshooting

2011-08-18 PUBLIC 85/134

Issue Solution

You get an error message that the purchase order (PO) contains faulty items.

Check that the Incoterms locations are maintained identically in SAP ERP and SAP Sourcing. For more information, see Verify Incoterms Locations [page 54].

7.2 Mapping of Fields Between SAP ERP and SAP Sourcing

7.2.1 Mapping of Customizing Data from SAP ERP to SAP Sourcing

The following table shows how the company code is mapped from SAP ERP to SAP Sourcing.

Mapping of Company Code from SAP ERP to SAP Sourcing

SAP ERP Field Label

SAP ERP Field Name

SAP Sourcing Field Label

SAP Sourcing Interface Object

SAP Sourcing Interface Object Field

Extra Mapping Logic

Company Code T001- BUKRS External ID masterdata.CompanyCode

EXTERNAL_ID

City T001- ORT01 City masterdata.CompanyCode

CITY

Country Key T001- LAND1 Country masterdata.CompanyCode

COUNTRY

Currency Key T001- WAERS Currency masterdata.CompanyCode

CURRENCY

Name of Company Code or Company

T001- BUTXT Display Name masterdata.CompanyCode

NAME

Replicated masterdata.CompanyCode

IS_REPLICATED

Constant value TRUE

The following table shows how the purchasing organization is mapped from SAP ERP to SAP Sourcing.

Mapping of Purchasing Organization from SAP ERP to SAP Sourcing

SAP ERP Field Label

SAP ERP Field Name




Extra Mapping Logic

Purchasing Organization

T024E- EKORG External ID masterdata.POrg EXTERNAL_ID

Company Code T024E- BUKRS Company Code masterdata.POrg COMPANY_CODE

Purchasing Organization Description

T024E- EKOTX Display Name masterdata.POrg NAME

Replicated masterdata.POrg IS_REPLICATED

Constant value TRUE

The following table shows how the purchasing group is mapped from SAP ERP to SAP Sourcing.

7 Appendix


86/134 PUBLIC 2011-08-18

Mapping of Purchasing Group from SAP ERP to SAP Sourcing

SAP ERP Field Label

SAP ERP Field Name




Extra Mapping Logic

Purchasing Group

T024- EKGRP External ID masterdata.POrg EXTERNAL_ID

Tel.No.Pur.Grp T024- EKTEL Telephone masterdata.POrg TELEPHONE

Fax Number T024- TELFX Fax masterdata.POrg FAX

E-Mail Address T024- SMTP_ADDR

E-Mail Address masterdata.POrg EMAIL_ADDRESS

Desc.Pur.Grp T024- EKOTX Display Name masterdata.POrg NAME


Constant value TRUE

The following table shows how the payment term is mapped from SAP ERP to SAP Sourcing.

Mapping of Payment Term from SAP ERP to SAP Sourcing

SAP ERP Field Label

SAP ERP Field Name




Extra Mapping Logic

Terms of Payment Key

T052- ZTERM External ID masterdata.PaymentTerm

EXTERNAL_ID

Language Key T052U- SPRAS (This field is not displayed on the user interface.)

masterdata.PaymentTerm

NAME – language

Own Explanation of Term of Payment

T052U- TEXT1 Display Name masterdata.PaymentTerm

NAME

Own Explanation of Term of Payment

T052U- TEXT1 Description masterdata.PaymentTerm

DESCRIPTION

Replicated masterdata.PaymentTerm

IS_REPLICATED

Constant value TRUE

Cash Discount Percentage Rate

T052-ZPRZ1 % Discount masterdata.PaymentTermSub

DISCOUNT

Days from Baseline Date for Payment

T052-ZTAG1 Days masterdata.PaymentTermSub

PAY_DAY

Cash Discount Percentage Rate

T052-ZPRZ2 % Discount masterdata.PaymentTerm

DISCOUNT


T052-ZTAG2 Days masterdata.PaymentTerm

PAY_DAY

7 Appendix


2011-08-18 PUBLIC 87/134

SAP ERP Field Label

SAP ERP Field Name




Extra Mapping Logic


T052-ZTAG3 Days masterdata.PaymentTerm

PAY_DAY

The following table shows how the material group is mapped from SAP ERP to SAP Sourcing.

Mapping of Material Group from SAP ERP to SAP Sourcing

SAP ERP Field Label

SAP ERP Field Name




Extra Mapping Logic

Material Group T023- MATKL Category ID masterdata.InternalCat

CATEGORY_ID

Language Key T023-SPRAS (This field is not displayed on the user interface.)

masterdata.InternalCat

NAME – language

Material Group Description

T023T- WGBEZ Display Name masterdata.InternalCat

NAME

Long Text Describing the Material Group

T023T- WGBEZ60

Display Name masterdata.InternalCat

NAME

Replicated masterdata.InternalCat

IS_REPLICATED

Constant value TRUE

The following table shows how the plant is mapped from SAP ERP to SAP Sourcing.

Mapping of Plant from SAP ERP to SAP Sourcing

SAP ERP Field Label

SAP ERP Field Name




Extra Mapping Logic

Plant T001W- WERKS External ID masterdata.Plant EXTERNAL_ID

House Number and Street

T001W- STRAS Street masterdata.Plant STREET

City T001W- ORT01 City masterdata.Plant CITY

Postal Code T001W- PSTLZ Postal Code masterdata.Plant POSTAL_CODE

Region (State, Province, County)

T001W- REGIO ERP Region masterdata.Plant ERP_REGION

Country Key T001W- LAND1 Country masterdata.Plant COUNTRY

Name T001W-NAME1 Display Name masterdata.Plant NAME

Name 2 T001W-NAME2 Description masterdata.Plant DESCRIPTION


T024W-EKORG Purchasing Organizations

masterdata.PlantPOrg

PORG

Company Code T001K-BUKRS Company Code masterdata.Plant EXTERNAL_COMPANY

7 Appendix


88/134 PUBLIC 2011-08-18

SAP ERP Field Label

SAP ERP Field Name




Extra Mapping Logic


Constant value TRUE

The following table shows how the condition type (pricing condition) is mapped from SAP ERP to SAP

Sourcing.

Mapping of Condition Type (Pricing Condition) from SAP ERP to SAP Sourcing

SAP ERP Field Label

SAP ERP Field Name




Extra Mapping Logic

(This field is not displayed on the user interface.)

eso.masterdata.pricingcondition

EXTERNAL_ID T685A-KSCHL and T000-LOGSYS

Replicated eso.masterdata.pricingcondition

IS_REPLICATED

Always TRUE

Name T685T-VTEXT Name eso.masterdata.pricingcondition

NAME – language

Logical System T000-LOGSYS Logical System eso.masterdata.pricingcondition

LOGICAL_SYSTEM

Condition Type T685A-KSCHL Condition ID eso.masterdata.pricingcondition

EXTERNAL_PC_ID

Application T685A-KAPPL Item Type eso.masterdata.pricingcondition

MATERIAL_SERVICE

MATERIAL or SERVICE

T685A-KKOPF and T685A-KPOSI

Condition Applies To


TYPE HEADER or ITEM or BOTH

Plus/Minus Sign of Condition Amount

T685A-KNEGA Impact on Price eso.masterdata.pricingcondition

SIGN POSITIVE or NEGATIVE or BOTH

Calculation Type for Condition

T685A-KRECH Calculation Type


UNIT A PercentageB Fixed Amount

Condition Class T685A-KOAID Condition Class eso.masterdata.pricingcondition

COND_CLASS A Discount or SurchargeB Prices

Scale Basis Indicator

T685A-KZBZG Scale Base eso.masterdata.pricingcondition

SCALE_BASE B Value ScaleC Quantity Scale

Scale Type T685A-STFKZ Scale Type eso.masterdata.pricingcondition

SCALE_TYPE <Blank> Can Be Maintained in Condition RecordA Base ScaleB To Scale

Checking Rule for Scale Rates

T685A-KSTPR Scale Check eso.masterdata.pricingcondition

SCALE_CHECK <Blank> NoneA Descending

7 Appendix


2011-08-18 PUBLIC 89/134

SAP ERP Field Label

SAP ERP Field Name




Extra Mapping LogicB Ascending

7.2.2 Mapping of Material Master Data from SAP ERP to SAP Sourcing

The following table shows how material master data is mapped from SAP ERP to SAP Sourcing.

SAP ERP interface: IDoc MATMAS05

SAP Sourcing interface: MI_IB_Material

Mapping of Material Master Data from SAP ERP to SAP Sourcing

SAP ERP Field Label

IDoc Segment

IDoc Segment Field


SAP Sourcing Interface Object Class Name


Material Type E1MARAM MTART Product Type

masterdata.Material PRODUCT_TYPE

Material E1MARAM MATNR External ID masterdata.Material EXTERNAL_ID

Material E1MARAM MATNR External Name

masterdata.Material EXTERNAL_NAME

Material Description (Short Text)

E1MAKTM MAKTX Display Name

masterdata.Material Value field below NAME node

Material Description Language

E1MAKTM SPRAS_ISO Language masterdata.Material Language attribute below NAME node

Material Description (Short Text)

E1MAKTM MAKTX Description masterdata.Material Value field below DESCRIPTION node

Material Description Language

E1MAKTM SPRAS_ISO Language masterdata.Material Language attribute below DESCRIPTION node

Base Unit of Measure

E1MARAM MEINS Base Unit masterdata.Material BASE_UNIT

Order Unit E1MARAM BSTME Order Unit masterdata.Material ORDER_UNIT

Material Group

E1MARAM MATKL Product Category

masterdata.Material INTERNAL_CAT

Material Type E1MARAM MTART Product Type

masterdata.Material PRODUCT_TYPE

Mark Material for Deletion(See Extra Mapping Logic below.)

E1MARAM LVORM Inactive masterdata.Material INACTIVE

Plant E1MARCM WERKS Plant Masterdata.ProductPlant PLANT

7 Appendix


90/134 PUBLIC 2011-08-18

SAP ERP Field Label

IDoc Segment

IDoc Segment Field




Mark for Deletion at Plant Level(See Extra Mapping Logic below.)

E1MARCM LVORM Delete Masterdata.ProductPlant Delete attribute

Extra Mapping Logic

The following table contains extra mapping logic for certain fields.

Extra Mapping Logic

SAP ERP Field Label Extra Mapping Logic

Mark Material for Deletion If the material is flagged for deletion in SAP ERP, the product will be inactivated in SAP Sourcing.

Mark for Deletion at Plant Level If the material/plant relation is flagged for deletion in SAP ERP, the product/plant relation will be deleted in SAP Sourcing.

7.2.3 Mapping of Vendor Master Data from SAP ERP to SAP Sourcing

The following table shows how vendor master data is mapped from SAP ERP to SAP Sourcing.

SAP ERP interface: IDoc CREMAS05

SAP Sourcing interface: MI_IB_Supplier

Mapping of Vendor Master Data from SAP ERP to SAP Sourcing

SAP ERP Field Label

IDoc Segment

IDoc Segment Field




Vendor(See Extra Mapping Logic below.)

E1LFA1M LIFNR or Header Text

External ID Masterdata.vendor EXTERNAL_ID

Name E1LFA1M NAME1 Display Name

Masterdata.vendor DISPLAY_NAME

Name 2 E1LFA1M NAME2 Abbreviated Name

Masterdata.vendor NAME_2

Name 3 E1LFA1M NAME3 Alternative Name

Masterdata.vendor NAME_3

Search Term 1/2

E1LFA1M SORTL Keywords Masterdata.vendor KEYWORDS

Street/House Number, Supplement

E1LFA1M STRAS Address 1 Masterdata.vendor ORDER_ADDRESS_1

District E1LFA1M ORT02 District Masterdata.vendor DISTRICT

7 Appendix


2011-08-18 PUBLIC 91/134

SAP ERP Field Label

IDoc Segment

IDoc Segment Field




Postal Code E1LFA1M PSTLZ Postal/ZIP Code

Masterdata.vendor ORDER_POSTAL_ CODE

City E1LFA1M ORT01 City Masterdata.vendor ORDER_CITY

Country(See Extra Mapping Logic below.)

E1LFA1M LAND1 Country Masterdata.vendor ORDER_COUNTRY

Region(See Extra Mapping Logic below.)

E1LFA1M REGIO ERP Region Masterdata.vendor ORDER_ERP_REGION

PO Box E1LFA1M PFACH PO Box Masterdata.vendor ORDER_PO_BOX

Postal Code E1LFA1M PSTL2 PO Box Postal Code

Masterdata.vendor ORDER_PBOX_ POSTAL_CODE

Telephone(See Extra Mapping Logic below.)

E1LFA1M TELF1 Main Phone Masterdata.vendor ORDER_TELEPHONE_1

Fax(See Extra Mapping Logic below.)

E1LFA1M TELFX Main Fax Masterdata.vendor ORDER_FAX_1

Sender Partner

EDI_DC40 SNDPRN External System

Masterdata.vendor LOG_SYS

Block for All Purchasing Organizations

E1LFA1M SPERM Inactive odp.masterdata.VendorLogSys INACTIVE

Mark for Deletion for All Areas

E1LFA1M LOEVM Inactive odp.masterdata.VendorLogSys INACTIVE

Sender Partner

EDI_DC40 SNDPRN External System

odp.masterdata.VendorLogSys LOG_SYS

Account Group

E1LFA1M KTOKK Vendor Account Group

odp.masterdata.VendorLogSys EXT_VEN_ ACCT_GROUP_ ID

Vendor E1LFA1M LIFNR External Supplier ID

odp.masterdata.VendorLogSys EXTERNAL_SUPPLIER_ID


E1LFM1M EKORG Purchasing Organization

odp.masterdata.VendorLogSysPOrg PORG

Block for Selected Purchasing Organization

E1LFM1M SPERM Delete odp.masterdata.VendorLogSysPOrg Delete attribute

7 Appendix


92/134 PUBLIC 2011-08-18

SAP ERP Field Label

IDoc Segment

IDoc Segment Field




(See Extra Mapping Logic below.)

Mark for Deletion for Selected Purchasing Organization(See Extra Mapping Logic below.)

E1LFM1M LOEVM Delete odp.masterdata.VendorLogSysPOrg Delete attribute

Extra Mapping Logic


Extra Mapping Logic


Vendor If the vendor header text Reference Number Sourcing is filled in SAP ERP, the same value will be copied to EXTERNAL_ID. Otherwise, the SAP ERP vendor ID will be copied to EXTERNAL_ID.

Country The ISO country code is transferred.

Region In SAP Sourcing, the key is the country code and region. Therefore, in SAP NetWeaver Process Integration (SAP NetWeaver PI), the country and region are concatenated with an underscore before mapping (for example, US_CA ).

Telephone The SAP ERP fields Telephone and Extension are concatenated to a single IDoc field and mapped to Main Phone of SAP Sourcing supplier.

Fax The SAP ERP fields Fax and Extension are concatenated to a single IDoc field and mapped to Main Fax of SAP Sourcing supplier.

Block for Selected Purchasing Organization

If the vendor/purchasing organization relation is blocked in SAP ERP, the supplier/purchasing organization relation will be deleted in SAP Sourcing.

Mark for Deletion for Selected Purchasing Organization

If the vendor/purchasing organization relation is marked for deletion in SAP ERP, the supplier/purchasing organization relation will be deleted in SAP Sourcing.

7.2.4 Mapping of Supplier Master Data from SAP Sourcing to SAP ERP

The following table shows how supplier master data is mapped from SAP Sourcing to SAP ERP.

SAP Sourcing interface: MI_OB_Supplier

SAP ERP interface: IDoc CREMAS05

7 Appendix


2011-08-18 PUBLIC 93/134

Mapping of Supplier Master Data from SAP Sourcing to SAP ERP




SAP ERP Field Label

IDoc Segment

IDoc Segment Field

External ID Masterdata.vendor EXTERNAL_ID Vendor E1LFA1M LIFNR

Display Name

Masterdata.vendor DISPLAY_NAME Name E1LFA1M NAME1

Abbreviated Name

Masterdata.vendor NAME_2 Name 2 E1LFA1M NAME2

Alternative Name

Masterdata.vendor NAME_3 Name 3 E1LFA1M NAME3

Keywords Masterdata.vendor KEYWORDS Search Term 1/2

E1LFA1M SORTL

Address 1 Masterdata.vendor ORDER_ADDRESS_1 Street E1LFA1M STRAS

District Masterdata.vendor DISTRICT District E1LFA1M ORT02

Postal/ZIP Code

Masterdata.vendor ORDER_POSTAL_ CODE Postal Code E1LFA1M PSTLZ

City Masterdata.vendor ORDER_CITY City E1LFA1M ORT01

CountrySee Extra Mapping Logic below.

Masterdata.vendor ORDER_COUNTRY Country E1LFA1M LAND1

ERP Region Masterdata.vendor ORDER_ERP_REGION Region E1LFA1M REGIO

PO Box Masterdata.vendor ORDER_PO_BOX PO Box E1LFA1M PFACH

PO Box Postal Code

Masterdata.vendor ORDER_PBOX_ POSTAL_CODE

Postal Code E1LFA1M PSTL2

Main Phone Masterdata.vendor ORDER_TELEPHONE_1 Telephone E1LFA1M TELF1

Main Fax Masterdata.vendor ORDER_FAX_1 Fax E1LFA1M TELFX

External IDSee Extra Mapping Logic below.

Masterdata.vendor EXTERNAL_ID Vendor Text(SAP Sourcing reference number maintained in text ID ESIN)

E1LFA1L TDLINE

Vendor Account Group

Masterdata.vendor EXT_VEND_ ACCT_GROUP_ ID

Vendor Account Group

E1LFA1M KTOKK

Supplier External ID

odp.masterdata.VendorLogSys EXTERNAL_SUPPLIER_ID Vendor ID E1LFA1M LIFNR

InactiveSee Extra Mapping Logic below.

odp.masterdata.VendorLogSys INACTIVE Centrally Imposed Purchasing Block

E1LFA1M SPERM

7 Appendix


94/134 PUBLIC 2011-08-18




SAP ERP Field Label

IDoc Segment

IDoc Segment Field

InactiveSee Extra Mapping Logic below.

odp.masterdata.VendorLogSys INACTIVE Central Deletion Flag

E1LFA1M LOEVM

Extra Mapping Logic


Extra Mapping Logic

SAP Sourcing Field Label Extra Mapping Logic

Country The ISO country code is transferred.

External ID The SAP Sourcing reference supplier number is stored in the SAP ERP text field when the supplier is published from SAP Sourcing to SAP ERP.

Inactive When an SAP Sourcing supplier record is inactivated either at header level or for a particular SAP ERP system, the central purchasing block and also central deletion flag are set in SAP ERP.

7.2.5 Mapping of SAP ERP RFQ to SAP Sourcing RFP

The following table shows how an SAP ERP RFQ is mapped to an SAP Sourcing RFP. For extra mapping

logic, see Extra Mapping Logic below.

SAP ERP interface: REQOTE:ORDERS05

SAP Sourcing interface: MI_IB_RFx

Mapping of SAP ERP RFQ to SAP Sourcing RFP

SAP ERP Field Label

IDoc Segment

IDoc Segment Field SAP Sourcing Field Label



RFQ E1EDK01 BELNR Title on Header tab rfx.RFXDoc DISPLAY_NAME


E1EDK14 ORGID Purchasing Organization rfx.RFXDoc EXTERNAL_PORG_ID

Purchasing Group

E1EDK14 ORGID Purchasing Group rfx.RFXDoc PURCHASING_GRP

Company Code

E1EDK14 ORGID Company Code rfx.RFXDoc EXTERNAL_COMPANY_CODE

Currency E1EDK01 HWAER Currency rfx.RFXDoc CURRENCY

Target Value E1EDS01 SUMME Outline Agreement Value Limit

rfx.RFXDoc OA_VALUE_ LIMIT

Validity Start Date

E1EDK03 DATUMUZEIT

Planned Open Date rfx.RFXDoc PLANNED_ OPEN_DATE

Quotation Deadline Date

E1EDK03 DATUMUZEIT

RFx Response Due Date rfx.RFXDoc DUE_DATE

7 Appendix


2011-08-18 PUBLIC 95/134

SAP ERP Field Label

IDoc Segment




Validity End Date

E1EDK03 DATUMUZEIT

RFx Response Due Date rfx.RFXDoc DUE_DATE

Title E1EDP19 IDTNR Title ontology.LineItemDoc DISPLAY_NAME

Material E1EDP19 IDTNR Material ontology.LineItemDoc MATERIAL

Item Category

E1EDP01 PSTYP Item Type ontology.LineItemDoc LINE_ITEM_ TYPE_ENUM

Short Text E1EDP19E1EDC01

KTEXTKTXT1

Description on Line Item ontology.LineItemDoc DOCUMENT_DESCRIPTION

Material Group

E1EDP01E1EDC01

MATKL Product Category ontology.LineItemDoc INTERNAL_CAT

RFQ Quantity

E1EDP01E1EDC01

MENGE Quantity ontology.LineItemDoc QUANTITY

Order Unit E1EDP01E1EDC01

MENEE Quantity ontology.LineItemDoc QUANTITY

Plant E1EDP01 WERKS Plant ontology.LineItemDoc PLANT

Item Category

E1EDP01 PSTYP Item Category ontology.LineItemDoc ITEM_CAT

Delivery Date

E1EDP20 EDATU Delivery Date ontology.LineItemDoc DELIV_DATE

Item Text ID E1EDPT1 TDID Default Line Item Text(Note: This label is found for filter setting on AbsIntegratedDocTypeBo.)

erp.Text(Line item)

TEXT_ID

Item Text E1EDPT2 TDLINE Long Description(Note: This label is found on LineItemDoc.)

erp.Text(Line item)

TEXT

Name E1EDPA1 NAME1 Name ontology.LineItemDoc DLVRY_ADDR_ NAME

Street/House Number

E1EDPA1 STRAS Street ontology.LineItemDoc DLVRY_ADDR_ ADDR1

District E1EDPA1 ORT02 District ontology.LineItemDoc DLVRY_ADDR_ DISTRICT

Postal Code E1EDPA1 PSTLZ Postal Code ontology.LineItemDoc DLVRY_ADDR_ ZIP_CODE

City E1EDPA1 ORT01 City ontology.LineItemDoc DLVRY_ADDR_ CITY

Region E1EDPA1 REGIO State ontology.LineItemDoc DLVY_ADDR_ REGION

Country E1EDPA1 LAND1 Country ontology.LineItemDoc DLVY_ADDR_ COUNTRY

Identifier for RFQ Document

Relationship(Note: This is the column header in the collection of document links in the RFx document.)

doc.link(Header)

LINK_DEFINITION

RFQ Document

E1EDK01 BELNR Title(Note: This is the column header in the collection of

doc.link(Header)

EXT_REF_DOC

7 Appendix


96/134 PUBLIC 2011-08-18

SAP ERP Field Label

IDoc Segment




document links in the RFx document.)

Identifier for RFQ Document


doc.link(Line item)

LINK_DEFINITION

RFQ Document

E1EDK01 BELNR Title – when in a collection of document links on the line item detail page.RFQ# / Line# – as the column header in the line item collection.Note: The document ID and the line number are displayed in the same column of the collection, for example:6000000514 : 00010

doc.link(Line item)

EXT_REF_DOC

RFQ Line Item

E1EDP01 POSEX Title – when in a collection of document links on the line item detail page.RFQ# / Line# – as the column header in the line item collection.Note: The document ID and the line number are displayed in the same column of the collection, for example:6000000514 : 00010

doc.link(Line item)

EXT_REF_LINE

Identifier for PR Document


doc.link(Line item)

LINK_DEFINITION

PR Document

E1EDP02 BELNR Title – when in a collection of document links on the line item detail page.PR# / Line# – as the column header in the line item collection.Note: The document ID and the line number are displayed in the same column of the collection, for example:

doc.link(Line item)

EXT_REF_DOC

7 Appendix


2011-08-18 PUBLIC 97/134

SAP ERP Field Label

IDoc Segment




0010034040 : 00010

PR Line Item E1EDP02 ZEILE Title – when in a collection of document links on the line item detail page.PR# / Line# – as the column header in the line item collection.Note: The document ID and the line number are displayed in the same column of the collection, for example:0010034040 : 00010

doc.link(Line item)

EXT_REF_LINE

Header Text ID

E1EDKT1 TDID Default Header Item Text(Note: This label is found for filter setting on AbsIntegratedDocTypeBo.)

erp.Text(Header)

TEXT_ID

Header Text E1EDKT1 TDLINE Description(Note: This label is found on rfx.RFXDoc.)

erp.Text(Header)

TEXT

Extra Mapping Logic


Extra Mapping Logic



Map on condition E1EDK14-QUALF = '014'

Purchasing Group Map on condition E1EDK14-QUALF = '009'

Company Code Map on condition E1EDK14-QUALF = '011'

Target Value Map E1EDS01-SUMME on condition E1EDS01-SUMID = ‘009’

Validity Start Date Map E1EDK03-DATUM on condition E1EDK03-IDDAT = '019'If E1EDK03-UZEIT is blank, concatenate E1EDK03-UZEIT with ’12:00’; otherwise, concatenate E1EDK03-DATUM with E1EDK03-UZEIT

Quotation Deadline Date

If quotation deadline date is not initial, map quotation deadline date into DUE_DATE (map E1EDK03- DATUM on condition E1EDK03-IDDAT = '004')If validity end date is not initial, map validity end date into DUE_DATE (map E1EDK03- DATUM on condition E1EDK03-IDDAT = '020')If E1EDK03-UZEIT is blank, concatenate E1EDK03-DATUM with ’23:59’ (time); otherwise, concatenate E1EDK03-DATUM with E1EDK03-UZEIT

Validity End Date If quotation deadline date is not initial, map quotation deadline date into DUE_DATE (map E1EDK03- DATUM on condition E1EDK03-IDDAT = '004')If validity end date is not initial, map validity end date into DUE_DATE (map E1EDK03- DATUM on condition E1EDK03-IDDAT = '020')

7 Appendix


98/134 PUBLIC 2011-08-18

SAP ERP Field Label Extra Mapping LogicIf E1EDK03-UZEIT is blank, concatenate E1EDK03-DATUM with ’23:59’ (time); otherwise, concatenate E1EDK03-DATUM with E1EDK03-UZEIT

Title Map on conditionE1EDP01- PSTYP = 0 (material item) &E1EDP19-QUALF = ‘001’ &E1EDP19-IDTNR exists (that is, material exists)

Material Map on conditionE1EDP01- PSTYP = 0 (material item) &E1EDP19-QUALF = ‘001’ &E1EDP19-IDTNR exists (that is, material exists)

Item Category If E1EDP01-PSTYP = 0 (material item)Map constant “1”If E1EDP01-PSTYP = 9 (service item)Map constant “2”

Short Text If E1EDP01-PSTYP = 0 (material item) &E1EDP19-QUALF = ‘001’Map E1EDP19-KTEXTIf E1EDP01-PSTYP = 9 (service item)Map E1EDC01-KTXT1

Material Group If E1EDP01-PSTYP = 0 (material item)Map E1EDP01-MATKLIf E1EDP01-PSTYP = 9 (service item)Map E1EDC01-MATKL

RFQ Quantity Quantity in SAP Sourcing is represented by concatenation of quantity and unit separated by spaceIf E1EDP01-PSTYP = 0 (material item)Map concatenation of E1EDP01-MENGE and E1EDP01-MENEEIf E1EDP01-PSTYP = 9 (service item)Map concatenation of E1EDC01-MENGE and E1EDC01-MENEE

Order Unit

Delivery Date If E1EDP20-EZEIT is blank, concatenate E1EDP20-EDATU with ’23:59’; otherwise, concatenate E1EDP20-EDATU with E1EDP20-EZEIT

Item Text ID Retrieve the text ID starting from position 2(Note: This value is compared with the value in the document type object to determine which text to retain.)

Item Text Concatenate all texts corresponding to each text ID(Note: Of the concatenated sets of item texts, only one is retained.)

Name If E1EDKA1 with PARVW = 'WE' is filled, take these data as delivery address for all items; otherwise, on item level, take E1EDPA1 if provided

Street/House Number

If E1EDKA1 with PARVW = 'WE' is filled, take these data as delivery address for all items; otherwise, on item level, take E1EDPA1 if provided

District If E1EDKA1 with PARVW = 'WE' is filled, take these data as delivery address for all items; otherwise, on item level, take E1EDPA1 if provided

Postal Code If E1EDKA1 with PARVW = 'WE' is filled, take these data as delivery address for all items; otherwise, on item level, take E1EDPA1 if provided

City If E1EDKA1 with PARVW = 'WE' is filled, take these data as delivery address for all items; otherwise, on item level, take E1EDPA1 if provided

7 Appendix


2011-08-18 PUBLIC 99/134


Region If E1EDKA1 with PARVW = 'WE' is filled, take these data as delivery address for all items; otherwise, on item level, take E1EDPA1 if provided

Country If E1EDKA1 with PARVW = 'WE' is filled, take these data as delivery address for all items; otherwise, on item level, take E1EDPA1 if provided

Identifier for RFQ Document(Header)

Default to ‘SAPINT-ERP_RFQ_Document’

Identifier for RFQ Document(Line item)

Default to ‘SAPINT-ERP_RFQ_Document’

Identifier for PR Document

Default to ‘SAPINT-ERP_PR_Document’

PR Document If E1EDP02-QUALF = 016, map E1EDP02-BELNR

PR Line Item If E1EDP02-QUALF = 016, map E1EDP02-ZEILE

Header Text ID Retrieve the text ID starting from position 2(Note: This value is compared with the value in the document type object to determine which text to retain.)

Header Text Concatenate all texts corresponding to each text ID(Note: Of the concatenated sets of item texts, only one is retained.)

Response Mapping of SAP Sourcing RFP to SAP ERP PR/RFQ

The following table shows the response mapping of an SAP Sourcing RFP to an SAP ERP PR/RFQ. For

extra mapping logic, see Extra Mapping Logic for Response Mapping of SAP Sourcing RFP to SAP ERP PR/RFQ

below.

SAP Sourcing interface: MI_OB_RFx_Response

SAP ERP interface: BBP_ES_PR_RFQ_UPDATE

Response Mapping of SAP Sourcing RFP to SAP ERP PR/RFQ




SAP ERP Field Label RFC Parameter

RFC Parameter Field/Table Name

Document ID(Note: Not usually displayed)

rfx.RFXDoc UNIQUE_DOC_ NAME

ES_DOC_NAME, ES_DOC_LINE, ES_DOC_TYPE, and ES_DOC_ID are concatenated and saved as text in customized text ID in corresponding PR item and RFQ item

ES_DOC_NAME

ET_CROSSREF-ES_DOC_NAME

Line Item Number

ontology.LineItemDoc

LINE_ITEM_ NUMBER

ES_DOC_NAME, ES_DOC_LINE,

ES_DOC_LINE ET_CROSSREF-ES_DOC_LINE

7 Appendix


100/134 PUBLIC 2011-08-18






(Note: This is labeled only as a column header in the collection. It is unlabeled on the details page.)

ES_DOC_TYPE, and ES_DOC_ID are concatenated and saved as text in customized text ID in corresponding PR item and RFQ item

Document Type(Note: DOC_TYPE of RFx – not displayed)


ES_DOC_TYPE ET_CROSSREF-ES_DOC_TYPE



UNIQUE_DOC_ NAME


ES_ID ET_CROSSREF-ES_ID

Title – when in a collection of document links on the line item detail page.PR# / Line# – as the column header in the line item collection.Note: The document ID and the line number are displayed in the

doc.link(Line item)

EXT_REF_DOC To identify which PR document to update

ERP_PR_ID ET_CROSSREF-ERP_PR_ID

7 Appendix


2011-08-18 PUBLIC 101/134






same column of the collection, for example:0010034040 : 00010

Title – when in a collection of document links on the line item detail page.PR# / Line# – as the column header in the line item collection.Note: The document ID and the line number are displayed in the same column of the collection, for example:0010034040 : 00010

doc.link(Line item)

EXT_REF_LINE To identify which PR item to update

ERP_PR_ITEM_ ID

ET_CROSSREF-ERP_PR_ITEM_ ID

Title – when in a collection of document links on the line item detail page.RFQ# / Line# – as the column header in the line item collection.Note: The document ID and the line number are displayed in the same column of the collection, for example:6000000514 : 00010

doc.link(Line item)

EXT_REF_DOC To identify which RFQ document to update

ERP_RFQ_ID ET_CROSSREF-ERP_RFQ_ID

Title – when in a collection of document links

doc.link(Line item)

EXT_REF_LINE To identify which RFQ item to update

ERP_RFQ_ITEM _ID

ET_CROSSREF-ERP_RFQ_ITEM _ID

7 Appendix


102/134 PUBLIC 2011-08-18






on the line item detail page.RFQ# / Line# – as the column header in the line item collection.Note: The document ID and the line number are displayed in the same column of the collection, for example:6000000514 : 00010

Extra Mapping Logic for Response Mapping of SAP Sourcing RFP to SAP ERP PR/RFQ


Extra Mapping Logic for Response Mapping of SAP Sourcing RFP to SAP ERP PR/RFQ



Map to constant RFQ

Title – when in a collection of document links on the line item detail page.PR# / Line# – as the column header in the line item collection.Note: The document ID and the line number are displayed in the same column of the collection, for example:0010034040 : 00010

If LINK_DEFINITION = SAPINT-ERP_PR_Document

Title – when in a collection of document links on the line item detail page.RFQ# / Line# – as the column header in the line item collection.Note: The document ID and the line number are displayed in the same column of the collection, for example:6000000514 : 00010

If LINK_DEFINITION = SAPINT-ERP_RFQ_Document

7.2.6 Mapping of SAP Sourcing RFP Award to SAP ERP Purchase Order

The following table shows how an SAP Sourcing RFP award is mapped to an SAP ERP purchase order.

SAP Sourcing interface: MI_OB_AWARD_TO_PURCHASE_ORDER

SAP ERP interface: BBP_ES_PO_CREATE

7 Appendix


2011-08-18 PUBLIC 103/134

Mapping of SAP Sourcing RFP Award to SAP ERP Purchase Order






Company Code rfx.RFXDoc EXTERNAL_COMPANY_CODE

Company Code PO_HEADER COMP_CODE

Transaction Type

rfx.RFXDoc TRANSACTION_TYPE

Purchasing Document Type

PO_HEADER DOC_TYPE

Created By rfx.RFXDoc CREATED_BY_USER

Name of Person Who Created Object

PO_HEADER CREATED_BY

Supplier ID rfx.RFXDoc EXTERNAL_SUPPLIER_ID

Vendor Account Number

PO_HEADER VENDOR

Payment Terms rfx.RFXDoc VEN_PAY_ TERM


PO_HEADER PMNTTRMS


rfx.RFXDoc EXTERNAL_PORG_ID


PO_HEADER PURCH_ORG

Purchasing Group

rfx.RFXDoc PURCHASING_GRP

Purchasing Group

PO_HEADER PUR_GROUP

Currency rfx.RFXDoc CURRENCY Currency Key PO_HEADER CURRENCY

ERP Start Date rfx.RFXDoc ERP_START_ DATE

Start of Validity Period

PO_HEADER VPER_START

ERP End Date rfx.RFXDoc ERP_END_ DATE

End of Validity Period

PO_HEADER VPER_END

Line Item Number


LINE_ITEM_ NUMBER

Item Number of Purchasing Document

POITEM PO_ITEM

Description ontology.LineItemDoc

DOCUMENT_DESCRIPTION

Short Text POITEM SHORT_TEXT

Product ID ontology.LineItemDoc

MATERIAL Material Number

POITEM MATERIAL

Plant ontology.LineItemDoc

BLI_PLANT Plant POITEM PLANT

Product Category


CATEGORY Material Group POITEM MATL_GROUP

QuantityItem Type


QUANTITYLINE_ITEM_ TYPE_ENUM

Purchase Order Quantity

POITEM QUANTITY

QuantityItem Type



Order Unit in ISO Code

POITEM PO_UNIT_ISO

Currency ontology.LineItemDoc

UNIT_PRICE Currency Amount

POITEM NET_PRICE

Price Unit ontology.LineItemDoc

PRICE_UNIT Price Unit POITEM PRICE_UNIT

7 Appendix


104/134 PUBLIC 2011-08-18






Item Type ontology.LineItemDoc

LINE_ITEM_ TYPE_ENUM

Item Cat. POITEM ITEM_CAT

Incoterms ontology.LineItemDoc

DELIVERY_TERM

Incoterms (Part 1)

POITEM INCOTERMS1

Incoterms Location


DELIVERY_TERM_LOCATION

Incoterms (Part 2)

POITEM INCOTERMS2

ERP Document and External Reference

doc.link LINK_DEFINITION and EXT_REF_DOC

RFQ Number POITEM RFQ_NO

External Reference

doc.link LINK_DEFINITION and EXT_REF_LINE

Item Number of RFQ

POITEM RFQ_ITEM

External Reference

rfx.RFXDoc RFX_UNIQUE_ DOC_NAME

Document Number of External Document

POITEM EXT_RFX_ NUMBER

External Reference


LINE_ITEM_ NUMBER

Item Number of External Document

POITEM EXT_RFX_ITEM

NA NA PI System Parameter

Logical System POITEM EXT_RFX_SYSTEM

Line Item Number


LINE_ITEM_ NUMBER


POSCHEDULE PO_ITEM

Line Item Number


LINE_ITEM_ NUMBER

Delivery Schedule Line Number

POSCHEDULE SCHED_LINE

Delivery Date ontology.LineItemDoc

SLI_DELIV_DATE

Delivery Date POSCHEDULE DELIVERY_DATE

Quantity ontology.LineItemDoc

QUANTITY Scheduled Quantity

POSCHEDULE QUANTITY

External Reference


LINK_DEFINITION and EXT_REF_DOC

Purchase Requisition Number

POSCHEDULE PREQ_NO

External Reference


LINK_DEFINITION and EXT_REF_LINE

Item Number of Purchase Requisition

POSCHEDULE PREQ_ITEM

Default Header Text

rfx.RFXDoc RFX_DESCRIPTION and RFX_HDR_ TEXT_ID

Text ID POTEXTHEADER

TEXT_ID

Description rfx.RFXDoc RFX_DESCRIPTION and

Text Line POTEXTHEADER

TEXT_LINE

7 Appendix


2011-08-18 PUBLIC 105/134






RFX_HDR_ TEXT_ID

Line Item Number

ontology.LineItemDoc and rfx.RFXDoc

LINE_ITEM_ NUMBER and BLI_LONG_ DESC and RFX_ITEM_ TEXT_ID


POTEXTITEM PO_ITEM

Default Line Item Text


BLI_LONG_ DESC and RFX_ITEM_ TEXT_ID

Text ID POTEXTITEM TEXT_ID

Long Description


BLI_LONG_ DESC and RFX_ITEM_ TEXT_ID and UNIQUE_DOC_ NAME and RFX_UNIQUE_ DOC_NAME

Text Line POTEXTITEM TEXT_LINE


QUANTITY Quantity PO_SRV_LINE MENGE


QUANTITY Un (Unit of Measure)

PO_SRV_LINE MEINS_ISO

Price Unit ontology.LineItemDoc

PRICE_UNIT Gross Price PO_SRV_LINE PEINH

Description ontology.LineItemDoc


Short Text PO_SRV_LINE KTEXT1

Incoterm Description – Extended Price


TOTAL_COST NET_PRICE PO_SRV_LINE TBTWR

Line Item Number


LINE_ITEM_ NUMBER

Service No. PO_SRV_TEXT ITEM_NO

Line Item Number


LINE_ITEM_ NUMBER

NA PO_SRV_TEXT EXTROW


ontology.LineItemDocrfx.RFXDoc

BLI_LONG_ DESCRFX_ITEM_ TEXT_IDFOLLOWON_DOCTYPE

TEXT_ID PO_SRV_TEXT TEXT_ID

Long Description

ontology.LineItemDocrfx.RFXDoc

RFX_UNIQUE_ DOC_NAMEPROPOSAL

Text Line PO_SRV_TEXT TEXT_LINE

7 Appendix


106/134 PUBLIC 2011-08-18






LINE_ITEM_ NUMBERBLI_LONG_ DESCRFX_ITEM_ TEXT_ID

7.2.7 Mapping of SAP Sourcing RFP Award to SAP ERP Outline Agreement

The following table shows how an SAP Sourcing RFP award is mapped to an SAP ERP outline agreement.

SAP Sourcing interface: MI_OB_AWARD_TO_OA

SAP ERP interface: BBP_ES_OA_UPDATE

Mapping of SAP Sourcing RFP Award to SAP ERP Outline Agreement






NA scenario.accepted_proposal

FOLLOWON_DOCTYPE

ES Document Number (Master Agreement)

CROSSREF ES_DOC_TYPE

RFx scenario.accepted_proposal

RFX_UNIQUE_ DOC_NAME

ES RFx Number CROSSREF ES_RFX_NUMBER


UNIQUE_DOC_ NAME

ES Master Agreement Name

CROSSREF ES_MA_NAME

Default Header Text

scenario.accepted_proposal

FOLLOWON_DOCTYPERFX_HDR_ TEXT_ID

Text ID CROSSREF HEAD_TEXT_ ID



FOLLOWON_DOCTYPERFX_ITEM_ TEXT_ID

Text ID CROSSREF ITEM_TEXT_ID

Company Code scenario.accepted_proposal

EXTERNAL_COMPANY_CODE

Company Code HEADER COMP_CODE

Transaction Type


TRANSACTION_TYPE


HEADER DOC_TYPE

Created By scenario.accepted_proposal

CREATED_BY_USER

Name of Person Who Created Object

HEADER CREATED_BY

Supplier ID scenario.accepted_proposal

EXTERNAL_SUPPLIER_ID


HEADER VENDOR

7 Appendix


2011-08-18 PUBLIC 107/134






Default Language in Supplier Master


USER_LANGUAGE

ISO Code for Language Key

HEADER LANGU_ISO

Default Payment Term in Supplier Master


VEN_PAY_ TERMS


HEADER PMNTTRMS



EXTERNAL_PORG_ID


HEADER PURCH_ORG

Purchasing Group


PURCHASING_GRP

Purchasing Group

HEADER PUR_GROUP

Currency scenario.accepted_proposal

CURRENCY ISO Code Currency

HEADER CURRENCY_ISO

Base Date scenario.accepted_proposal

BASE_DATE Purchasing Document Date

HEADER DOC_DATE

ERP Start Date scenario.accepted_proposal

ERP_START_ DATE

Validity Start HEADER VPER_START

ERP End Date scenario.accepted_proposal

ERP_END_ DATE

Validity End HEADER VPER_END

Outline Agreement Value Limit


OA_VALUE_ LIMIT

Target Value for Header Area per Distribution

HEADER ACUM_VALUE

Default Header Text


RFX_DESCRIPTIONRFX_HDR_ TEXT_IDFOLLOWON_DOCTYPE

Text ID HEADER_TEXT TEXT_ID


RFX_DESCRIPTIONRFX_HDR_ TEXT_ID

Tag Column HEADER_TEXT TEXT_FORM

Description scenario.accepted_proposal

RFX_DESCRIPTIONRFX_HDR_ TEXT_ID

Text Line HEADER_TEXT TEXT_LINE

NA NA Constant=1 Number of a Condition Record

HEAD_CONDITION

SERIAL_ID

NA NA Counter starts from 1

Sequential Number of the Condition

HEAD_CONDITION

COND_COUNT

Condition Type ID

eso.doccommon.pricingcondition.supplement

PC_ID Condition Type HEAD_CONDITION

COND_TYPE

7 Appendix


108/134 PUBLIC 2011-08-18






Currency scenario.accepted_ proposal

CURRENCY ISO Code Currency for Scales

HEAD_CONDITION

SCALE_CURR_ ISO

Amount/Percent(See Extra Mapping Logic below.)


UNIT, AMOUNT, PERCENT

Condition Amount

HEAD_CONDITION

COND_VALUE

Currency(See Extra Mapping Logic below.)

scenario.accepted_ proposaleso.doccommon.pricingcondition.supplement

CURRENCY, UNIT

ISO Code Currency

HEAD_CONDITION

CURRENCY_ISO


HEAD_COND_ SCALE_VAL

SERIAL_NO




COND_COUNT

From/To(See Extra Mapping Logic below.)

eso.doccommon.pricingcondition.scale

VOLUME_THRESHOLD

Currency Amount


SCALE_BASE_ VALUE


eso.doccommon.pricingcondition.supplementeso.doccommon.pricingcondition.scale


Currency Amount


COND_VALUE


HEAD_COND_ VALIDITY

SERIAL_ID

ERP Start Date scenario.accepted_ proposal

ERP_START_ DATE

Validity Start Date of Condition Record

HEAD_COND_ VALIDITY

VALID_FROM

ERP End Date scenario.accepted_ proposal

ERP_END_ DATE

Validity End Date of Condition Record

HEAD_COND_ VALIDITY

VALID_TO

Line Item Number

scenario.accepted_line_item

LINE_ITEM_ NUMBER


ITEM ITEM_NO

Description scenario.accepted_line_item


Short Text ITEM SHORT_TEXT

Product ID scenario.accepted_line_item

MATERIALLINE_ITEM_ TYPE_ENUM

Material Number

ITEM MATERIAL

7 Appendix


2011-08-18 PUBLIC 109/134






Plant scenario.accepted_line_item

BLI_PLANT Plant ITEM PLANT

Product Category


CATEGORY Material Group ITEM MATL_GROUP

Quantity scenario.accepted_line_item


Target Quantity ITEM TARGET_QTY




ITEM PO_UNIT_ISO

ISO Code in System Administration



ISO Code for Purchase Order Price Unit

ITEM ORDERPR_UN_ ISO

NA scenario.accepted_line_item

Constant = 1 Numerator for Conversion of Order Price Unit into Order Unit

ITEM CONV_NUM1

NA scenario.accepted_line_item

Constant = 1 Denominator for Conversion of Order Price Unit into Order Unit

ITEM CONV_DEN1

Total Price scenario.accepted_line_item

UNIT_PRICELINE_ITEM_ TYPE_ENUM

Currency Amount

ITEM NET_PRICE

Item Type scenario.accepted_line_item


Item Category ITEM ITEM_CAT

Incoterms scenario.accepted_line_item

DELIVERY_TERM

Incoterms (Part 1)

ITEM INCOTERMS1

Incoterms Location


DELIVERY_TERM_LOCATION

Incoterms (Part 2)

ITEM INCOTERMS2

External Reference

doc.link LINK_DEFINITION and Constant = SAPINT-ERP_RFQ_Document and EXT_REF_DOC

RFQ Number ITEM RFQ_NO

External Reference

doc.link LINK_DEFINITION and Constant = SAPINT-ERP_RFQ_Document and EXT_REF_LINE

Item Number of RFQ

ITEM RFQ_ITEM

7 Appendix


110/134 PUBLIC 2011-08-18






External Reference

doc.link LINK_DEFINITION and Constant = SAPINT-ERP_PR_Document and EXT_REF_DOC

Purchase Requisition Number

ITEM PREQ_NO

External Reference

doc.link LINK_DEFINITION and Constant = SAPINT-ERP_PR_Document and EXT_REF_LINE

Item Number of Purchase Requisition

ITEM PREQ_ITEM

Line Item Number


LINE_ITEM_ NUMBER


ITEM_CONDITION

ITEM_NO

Line Item Number


LINE_ITEM_ NUMBER

Number of a Condition Record

ITEM_CONDITION

SERIAL_ID

NA NA Counter starts from 1 for each material


ITEM_CONDITION

COND_COUNT

Condition Type ID


PC_ID Condition Type ITEM_CONDITION

COND_TYPE



QUANTITY Condition Unit of Measure in ISO

ITEM_CONDITION

SCALE_UNIT_ ISO




Condition Amount

ITEM_CONDITION

COND_VALUE



CURRENCY, UNIT

ISO Code Currency

ITEM_CONDITION

CURRENCY_ISO

Price Unit scenario.accepted_line_item

PRICE_UNIT Condition Pricing Unit

ITEM_CONDITION

COND_P_UNT




ITEM_CONDITION

COND_UNIT_ ISO

7 Appendix


2011-08-18 PUBLIC 111/134






Line Item Number


LINE_ITEM_ NUMBER


ITEM_COND_ SCALE_QUAN

ITEM_NO

Line Item Number


LINE_ITEM_ NUMBER



SERIAL_NO

NA NA COND_COUNT of the ITEM_CONDITION this item belongs to



COND_COUNT



UNIT_THRESHOLD

Condition Scale Quantity


SCALE_BASE_ QTY




Currency Amount


COND_VALUE

Line Item Number


LINE_ITEM_ NUMBER


ITEM_COND_ VALIDITY

ITEM_NO

Line Item Number


LINE_ITEM_ NUMBER


ITEM_COND_ VALIDITY

SERIAL_ID


VALID_FROM Validity Start Date of Condition Record

ITEM_COND_ VALIDITY

VALID_FROM


VALID_TO Validity End Date of Condition Record

ITEM_COND_ VALIDITY

VALID_TO

Line Item Number

scenario.accepted_line_itemscenario.accepted_proposal

LINE_ITEM_ NUMBERBLI_LONG_ DESCRFX_ITEM_ TEXT_ID


ITEM_TEXT ITEM_NO




Text ID ITEM_TEXT TEXT_ID

7 Appendix


112/134 PUBLIC 2011-08-18






NA scenario.accepted_line_itemscenario.accepted_proposal

BLI_LONG_ DESCRFX_ITEM_ TEXT_ID

Tag Column ITEM_TEXT TEXT_FORM

Long Description



Text Line ITEM_TEXT TEXT_LINE

Line Item Number

scenario.accepted_ line_item

LINE_ITEM_ NUMBER


SRV_COND ITEM_NO

Line Item Number


LINE_ITEM_ NUMBER


SRV_COND EXTROW

Line Item Number


LINE_ITEM_ NUMBER


SRV_COND SERIAL_ID

NA NA Counter starts from 1 for each service


SRV_COND COND_COUNT

Condition Type ID


PC_ID Condition Type SRV_COND COND_TYPE




SRV_COND SCALE_UNIT_ ISO




Condition Amount

SRV_COND COND_VALUE



CURRENCY, UNIT

ISO Code Currency

SRV_COND CURRENCY_ISO

Price Unit scenario.accepted_ line_item


SRV_COND COND_P_UNT




SRV_COND COND_UNIT_ ISO

Line Item Number


LINE_ITEM_ NUMBER


SRV_COND_ SCALE_QUAN

ITEM_NO

7 Appendix


2011-08-18 PUBLIC 113/134






Line Item Number


LINE_ITEM_ NUMBER



EXTROW

Line Item Number


LINE_ITEM_ NUMBER



SERIAL_NO

NA NA COND_COUNT of the SRV_COND this item belongs to



COND_COUNT



UNIT_THRESHOLD



SCALE_BASE_ QTY




Currency Amount


COND_VALUE

Line Item Number


LINE_ITEM_ NUMBER


SRV_COND_ VALIDITY

ITEM_NO

Line Item Number


LINE_ITEM_ NUMBER


SRV_COND_ VALIDITY

EXTROW

Line Item Number


LINE_ITEM_ NUMBER


SRV_COND_ VALIDITY

SERIAL_ID


VALID_FROM Validity Start Date of Condition Record

SRV_COND_ VALIDITY

VALID_FROM


VALID_TO Validity End Date of Condition Record

SRV_COND_ VALIDITY

VALID_TO

Line Item Number


LINE_ITEM_ NUMBER

Service No. SRV_LINE ITEM_NO

Line Item Number


LINE_ITEM_ NUMBER

NA SRV_LINE EXTROW


QUANTITY Quantity SRV_LINE MENGE


QUANTITY Un (Unit of Measure)

SRV_LINE MEINS_ISO

7 Appendix


114/134 PUBLIC 2011-08-18






Price Unit scenario.accepted_line_item

PRICE_UNIT Gross Price SRV_LINE PEINH

Description scenario.accepted_line_item


Short Text SRV_LINE KTEXT1

Incoterm Description – Extended Price


TOTAL_COST NET_PRICE SRV_LINE TBTWR

Line Item Number


LINE_ITEM_ NUMBER

Service No. SRV_TEXT ITEM_NO

Line Item Number


LINE_ITEM_ NUMBER

NA SRV_TEXT EXTROW




TEXT_ID SRV_TEXT TEXT_ID

Long Description



NA SRV_TEXT TEXT_FORM

Long Description

scenario.accepted_proposalscenario.accepted_line_item

RFX_UNIQUE_ DOC_NAMEPROPOSALLINE_ITEM_ NUMBERBLI_LONG_ DESCRFX_ITEM_ TEXT_ID

Text Line SRV_TEXT TEXT_LINE

Extra Mapping Logic


Extra Mapping Logic


Amount/Percent COND_VALUE is set to AMOUNT or PERCENT based on the value of UNIT.

Currency Either CURRENCY or "P1" is mapped to CURRENCY_ISO based on the value of UNIT.("P1" identifies that percent value is used.)

From/To VOLUME_THRESHOLD is mapped to SCALE_BASE_VALUE; UNIT_THRESHOLD is mapped to SCALE_BASE_QTY.

7 Appendix


2011-08-18 PUBLIC 115/134

7.2.8 Mapping of SAP Sourcing Master Agreement to SAP ERP Outline Agreement

The following table shows how an SAP Sourcing master agreement is mapped to an SAP ERP outline

agreement.

SAP Sourcing interface: MT_AGREEMENT


Mapping of SAP Sourcing Master Agreement to SAP ERP Outline Agreement






Title in Document Links collection table(See Extra Mapping Logic below.)

contracts.Contract

EXT_REF_DOC(Based on LINK_DEF)

Purchasing Document Number

HEADER NUMBER

Currency contracts.Contract

CURRENCY ISO Code Currency

HEADER CURRENCY_ISO

Payment Terms contracts.Contract

PAYTERMS Terms of Payment Key

HEADER PMNTTRMS

Company code contracts.Contract

EXTERNAL_COMPANY_CODE

Company Code HEADER COMP_CODE

Transaction Type(See Extra Mapping Logic below.)

contracts.Contract

FOLLOWON_DOCTYPE

ES Document Type


Transaction Type

contracts.Contract

TRANSACTION_TYPE


HEADER DOC_TYPE

Supplier contracts.Contract

EXTERNAL_SUPPLIER_ID


HEADER VENDOR


contracts.Contract

EXTERNAL_PORG_ID


HEADER PURCH_ORG

Purchasing Group

contracts.Contract

PURCHASING_GRP

Purchasing Group

HEADER PUR_GROUP

Created By: (Timestamp)

contracts.Contract

BASE_DATE Purchasing Document Date

HEADER DOC_DATE

Effective Date contracts.Contract

EFFECTIVE_DATE

Start of Validity Period

HEADER VPER_START

Expiration Date contracts.Contract

EXPIRATION_DATE

End of Validity Period

HEADER VPER_END

Agreement Maximum

contracts.Contract

LIMIT_VALUE Target Value for Header Area per Distribution

HEADER ACUM_VALUE

Not visible on user interface

contracts.Contract

USER_LANGUAGE

ISO Code for Language Key

HEADER LANGU_ISO

7 Appendix


116/134 PUBLIC 2011-08-18






Default Header Text in corresponding document type

contracts.Contract

HDR_TEXT_ID Text ID HEADER_TEXT TEXT_ID

NA(See Extra Mapping Logic below.)

NA HDR_TEXT_ID Tag Column HEADER_TEXT TEXT_FORM

Description(See Extra Mapping Logic below.)

contracts.Contract


Text Line HEADER_TEXT TEXT_LINE

Incoterms contracts.Contract

DELIVERY_TERM

Incoterms (Part 1)

HEADER INCOTERMS1

Incoterm Location

contracts.Contract

DEL_TERM_ LOC

Incoterms (Part 2)

HEADER INCOTERMS2


HEAD_CONDITION

SERIAL_ID



HEAD_CONDITION

COND_COUNT

Condition Type ID


PC_ID Condition Type HEAD_CONDITION

COND_TYPE

Currency contracts.Contract

CURRENCY ISO Code Currency for Scales

HEAD_CONDITION

SCALE_CURR_ ISO




Condition Amount

HEAD_CONDITION

COND_VALUE


contracts.Contracteso.doccommon.pricingcondition.supplement

CURRENCY, UNIT

ISO Code Currency

HEAD_CONDITION

CURRENCY_ISO


HEAD_COND_ VALIDITY

SERIAL_ID

Effective Date contracts.Contract

EFFECTIVE_DATE

Validity Start Date of Condition Record

HEAD_COND_ VALIDITY

VALID_FROM

Expiration Date contracts.Contract

EXPIRATION_DATE

Validity End Date of Condition Record

HEAD_COND_ VALIDITY

VALID_TO

7 Appendix


2011-08-18 PUBLIC 117/134






Line Item Number

contracts.LineItem

LINE_ITEM_ NUMBER


ITEM ITEM_NO

Description contracts.LineItem


Material Short Text

ITEM SHORT_TEXT

Material(See Extra Mapping Logic below.)

contracts.LineItem

MATERIAL Material Number

ITEM MATERIAL

Supplier Part Number

contracts.LineItem

VENDOR_PART_ NUM

Material Number Used by Vendor

ITEM VEND_MAT

Plant contracts.LineItem

PLANT Plant ITEM PLANT

Product Category

contracts.LineItem

INTERNAL_CAT

Material Group ITEM MATL_GROUP

Contracted Quantity(See Extra Mapping Logic below.)

contracts.LineItem

QUANTITYISO Unit of Measure is to be used

Target Quantity ITEM TARGET_QTY

Contract Quantity

contracts.LineItem

QUANTITYField contains unit of measure


ITEM PO_UNIT_ISO

NA contracts.LineItem

QUANTITY ISO Code for Purchase Order Price Unit

ITEM ORDERPR_UN_ ISO

Unit Price contracts.LineItem

UNIT_PRICE Currency Amount

ITEM NET_PRICE

Price Unit contracts.LineItem

PRICE_UNIT Price Unit ITEM PRICE_UNIT

Delivery Lead Time (Days)

contracts.LineItem

DELIVERY_LEAD

Planned Delivery Time

ITEM PLAN_DEL

No label contracts.LineItem

DELIVERY_TERMS

Incoterms (Part 1)

ITEM INCOTERMS1

No label(See Extra Mapping Logic below.)

contracts.LineItem

AWARDED_INCOTERM_LOCATION

Incoterms (Part 2)

ITEM INCOTERMS2

Item Type(See Extra Mapping Logic below.)

contracts.LineItem


Item Category ITEM ITEM_CAT

NA contracts.LineItem

ITEM_CAT Item Category in Purchasing Document

OA_ITEMS ITEM_CAT

7 Appendix


118/134 PUBLIC 2011-08-18






Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER


ITEM_COND_ VALIDITY

ITEM_NO

Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER


ITEM_COND_ VALIDITY

SERIAL_ID

Unit Price Date Begin

contracts.LineItem

UP_BEGIN Validity Start Date of Condition Record

ITEM_COND_ VALIDITY

VALID_FROM

Unit Price Date End

contracts.LineItem

UP_END Validity End Date of Condition Record

ITEM_COND_ VALIDITY

VALID_TO

Title in Document Links table of header(See Extra Mapping Logic below.)

doc.link EXT_REF_DOC RFQ Number ITEM RFQ_NO


doc.link EXT_REF_LINE Item Number of RFQ

ITEM RFQ_ITEM


doc.link EXT_REF_DOC Purchase Requisition Number

ITEM PREQ_NO


doc.link EXT_REF_LINE Item Number of Purchase Requisition

ITEM PREQ_ITEM

Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER


ITEM_CONDITION

ITEM_NO

Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER


ITEM_CONDITION

SERIAL_ID

NA NA Counter starts from 1 for each material


ITEM_CONDITION

COND_COUNT

Condition Type ID


PC_ID Condition Type ITEM_CONDITION

COND_TYPE

7 Appendix


2011-08-18 PUBLIC 119/134









Condition Amount

ITEM_CONDITION

COND_VALUE

Quantity contracts. LineItem


ITEM_CONDITION

SCALE_UNIT_ ISO



CURRENCY, UNIT

ISO Code Currency

ITEM_CONDITION

CURRENCY_ISO



ITEM_CONDITION

COND_P_UNT


contracts. LineItem


ITEM_CONDITION

COND_UNIT_ ISO

Line Item Number

contracts.LineItem

LINE_ITEM_ NUMBER



ITEM_NO

Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER



SERIAL_NO

NA NA COND_COUNT of the ITEM_CONDITION this item belongs to



COND_COUNT



UNIT_THRESHOLD



SCALE_BASE_ QTY




Currency Amount


COND_VALUE



SERIAL_NO




COND_COUNT



VOLUME_THRESHOLD

Currency Amount


SCALE_BASE_ VALUE

7 Appendix


120/134 PUBLIC 2011-08-18









Currency Amount


COND_VALUE

Line Item Number

Contracts.LineItem

LINE_ITEM_ NUMBER


ITEM_TEXT ITEM_NO

Default Line Item Text from corresponding integrated document type

Contracts.LineItem

ITEM_TEXT_ID Text ID ITEM_TEXT TEXT_ID

NA(See Extra Mapping Logic below.)

contracts.Lineitem

LONG_DESC Tag Column ITEM_TEXT TEXT_FORM

Description(See Extra Mapping Logic below.)

contracts.Lineitem

LONG_DESC Text Line ITEM_TEXT TEXT_LINE

Unique Document Name(See Extra Mapping Logic below.)

doc.link UNIQUE_DOC_ NAME


CROSSREF ES_MA_NUMBER

Follow-On Document Type(See Extra Mapping Logic below.)

doc.link FOLLOWON_DOCTYPE

ES Document Type


Document Reference(See Extra Mapping Logic below.)

doc.link EXT_REF_DOC ES RFx Number CROSSREF ES_RFX_NUMBER

Display Name contracts.contract

DISPLAY_NAME

ES Master Agreement Name

CROSSREF ES_MA_NAME

Line Item Number

contracts.LineItem

LINE_ITEM_ NUMBER


SRV_LINE ITEM_NO

Line Item Number

contracts.LineItem

LINE_ITEM_ NUMBER

Line Number SRV_LINE EXTROW

Quantity contracts.LineItem

QUANTITY Quantity with Sign

SRV_LINE MENGE

Unit of Measure contracts.LineItem

QUANTITY Base Unit of Measure

SRV_LINE MEINS_ISO

7 Appendix


2011-08-18 PUBLIC 121/134






Field contains unit of measure


PRICE UNIT Price Unit SRV_LINE PEINH

Document Description

contracts.LineItem

DOCUMENT DESCRIPTION

Short Text SRV_LINE KTEXT1

Unit Price contracts.LineItem

UNIT_PRICE Gross Price SRV_LINE TBTWR

Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER


SRV_COND ITEM_NO

Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER


SRV_COND EXTROW

Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER


SRV_COND SERIAL_ID

NA NA Counter starts from 1 for each service


SRV_COND COND_COUNT

Condition Type ID


PC_ID Condition Type SRV_COND COND_TYPE


contracts. LineItem


SRV_COND SCALE_UNIT_ ISO




Condition Amount

SRV_COND COND_VALUE



CURRENCY, UNIT

ISO Code Currency

SRV_COND CURRENCY_ISO

Price Unit contracts. LineItem


SRV_COND COND_P_UNT


contracts. LineItem


SRV_COND COND_UNIT_ ISO

Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER



ITEM_NO

7 Appendix


122/134 PUBLIC 2011-08-18






Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER



EXTROW

Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER



SERIAL_NO

NA NA COND_COUNT of the SRV_COND this item belongs to



COND_COUNT



UNIT_THRESHOLD



SCALE_BASE_ QTY




Currency Amount


COND_VALUE

Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER


SRV_COND_ VALIDITY

ITEM_NO

Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER


SRV_COND_ VALIDITY

EXTROW

Line Item Number

contracts. LineItem

LINE_ITEM_ NUMBER


SRV_COND_ VALIDITY

SERIAL_ID

Unit Price Date Begin

contracts. LineItem

UP_BEGIN Validity Start Date of Condition Record

SRV_COND_ VALIDITY

VALID_FROM

Unit Price Date End

contracts. LineItem

UP_END Validity End Date of Condition Record

SRV_COND_ VALIDITY

VALID_TO

Extra Mapping Logic


Extra Mapping Logic


Title in Document Links collection table

This field is used when changing a contract.

7 Appendix


2011-08-18 PUBLIC 123/134


Transaction Type The ES Document Type field is used to differentiate between contract and scheduling agreement. Map to the specific value in SAP ERP.

NA SAP NetWeaver Process Integration (SAP NetWeaver PI) mapping breaks this into 132-character lines.

Description SAP NetWeaver PI mapping breaks this into 132-character lines.

Amount/Percent COND_VALUE is set to AMOUNT or PERCENT based on the value of UNIT.

Currency Either CURRENCY or "P1" is mapped to CURRENCY_ISO based on the value of UNIT.("P1" identifies that percent value is used.)

Material Check the value of the INCLUDE_PART_NUMBER field to identify if it is a regular material or a free-text item. If a free-text item, the field will be set to blank (that is, it will have no value).

Contracted Quantity This will be a combination of quantity and unit of measure. SAP NetWeaver PI needs to extract and separate the quantity and unit of measure from the string containing the quantity and unit of measure.

No label This is the Incoterm location of the awarded Incoterm.

Item Type For material line items, the value of the SAP Sourcing Item Type field is LINE_ITEM_TYPE_ENUM = 1, and the value of the SAP ERP Item Category field is ITEM_CAT = 0.For service line items, the value of the SAP Sourcing Item Type field is LINE_ITEM_TYPE_ENUM = 2, and the value of the SAP ERP Item Category field is ITEM_CAT = 9.

Title in Document Links table of header

Document number is taken from item document links based on LINK_DEFINITION type = RFQ.


Item number is taken from item document links based on LINK_DEFINITION type = RFQ.


Document number is taken from item document links based on LINK_DEFINITION type = PR.


Item number is taken from item document links based on LINK_DEFINITION type = PR.

From/To VOLUME_THRESHOLD is mapped to SCALE_BASE_VALUE; UNIT_THRESHOLD is mapped to SCALE_BASE_QTY.

NA SAP NetWeaver PI mapping breaks this into 132-character lines.

Description SAP NetWeaver PI mapping breaks this into 132-character lines.

Unique Document Name

Concatenate the class name to distinguish master agreement and subagreement.

Follow-On Document Type

The ES Document Type field is used to differentiate between contract and scheduling agreement. Map to the specific value in SAP ERP.

Document Reference If the LINK_DEFINITION is RFx, ES_RFX_NUMBER will be filled.

Response Mapping of SAP ERP Outline Agreement to SAP Sourcing Master Agreement

The following table shows the response mapping of an SAP ERP outline agreement to an SAP Sourcing

master agreement.


7 Appendix


124/134 PUBLIC 2011-08-18

SAP Sourcing Interface: MT_AGREEMENT_RESPONSE

Response Mapping of SAP ERP Outline Agreement to SAP Sourcing Master Agreement

SAP ERP Field Label

RFC Parameter






CROSSREF ES_MA_NUMBER Master Agreement ID in master agreement table

contracts.Contract UNIQUE_DOC_ NAME


ITEM ITEM_NO Line Item Number

contracts.LineItem LINE_ITEM_ NUMBER

Purchasing Document Number

NA PURCHASINGDOCUMENT Title in Document Links collection table

doc.link EXT_DOC_REF


ITEM ITEM_NO Title in Document Links collection table

doc.link EXT_REF_LINE

Message Type: S Success, E Error, W Warning, I Info, A Abort

RETURN TYPE NA NA TYPE

Message Text

RETURN MESSAGE NA NA TEXT

7.3 Sending Files and Customizing Data via FTPS Protocol

Procedure

NOTE

This is carried out by your IT network expert.

Sending Files via FTPS Protocol

If you want to send files via FTPS protocol, you need to:

7 Appendix

7.3 Sending Files and Customizing Data via FTPS Protocol

2011-08-18 PUBLIC 125/134

■ Ensure that port 21 (for control connection) and TCP ports 30000-40000 (for passive data

connection) are open outbound from your network to the external IP address of the hosted FTP

server.

■ Ensure that FTP access outbound is allowed from your network.

■ Edit the host file on the SAP NetWeaver Process Integration (SAP NetWeaver PI) server to add the

fully qualified domain name (FQDN) and external IP of the hosted FTP server.

NOTE

This is necessary only if you are unable to resolve the external IP to FQDN.

■ Provide the hosting team with the external IP of the server sending the files. The hosting team will

add the IP to the access control list (ACL) of the hosting firewall to allow access.

NOTE

A thawte signed SSL certificate is installed on the hosted FTP servers. Since a thawte intermediate

certificate is installed in the Visual Administrator on your SAP NetWeaver PI server, no additional

certificate is needed.

Sending Customizing Data via FTPS Protocol

If you want to send Customizing data from SAP ERP to SAP Sourcing via FTPS protocol instead of

importing it manually, the generated XML files from SAP ERP can be placed in a directory on the SAP

NetWeaver PI server or on a local FTP server. Customizing data placed on the SAP NetWeaver PI server

or on a local FTP server can be moved to the SAP Hosting FTP server by configuring the file

communication channel using FTPS protocol.

To do this, you must carry out the above steps for Sending Files via FTPS Protocol, and also carry out the

following steps:

■ Create the communication channels to send files via FTPS protocol to the FTPS host.

■ Follow the standard SAP NetWeaver PI configuration steps for creating a sender agreement, receiver

agreement, interface determination, and receiver determination. You can use dummy names for

message interfaces because only the communication channels are important.

7.4 Configuring SSL/HTTPS

NOTE


Configure Secure Sockets Layer (SSL)/HTTPS according to whichever of the following scenarios is in

use at your company.

■ Using Proxy in DMZ (HTTPS from Internet and HTTP to SAP NetWeaver PI)

■ Using SAP Web Dispatcher in DMZ (HTTPS from Internet and HTTP to SAP NetWeaver PI)

■ Using Proxy in DMZ (HTTPS from Internet and HTTPS to SAP NetWeaver PI)

7 Appendix


126/134 PUBLIC 2011-08-18

■ Using SAP Web Dispatcher in DMZ (HTTPS from Internet and HTTPS to SAP NetWeaver PI)

For information about each of these scenarios, see below.

Procedure

Using Proxy in DMZ (HTTPS from Internet and HTTP to SAP NetWeaver PI)

In this scenario, the proxy redirects the traffic to HTTP to SAP NetWeaver Process Integration (SAP

NetWeaver PI) via SOAP adapter.

This requires you and SAP Hosting to open port 443 for HTTPS traffic in the demilitarized zone (DMZ).

You do not need to configure SAP NetWeaver PI for SSL on ABAP or Java because the proxy redirects

the traffic from HTTPS to HTTP.

Using SAP Web Dispatcher in DMZ (HTTPS from Internet and HTTP to SAP NetWeaver PI)

SAP Web Dispatcher is a software load balancer that is installed outside the SAP NetWeaver Process


1. Open port 443 for HTTPS traffic in the demilitarized zone (DMZ). Request SAP Hosting to do the

same.

2. Configure HTTPS on SAP Web Dispatcher.

1. Install SAP Cryptographic Library on SAP Web Dispatcher.

1. Download SAP Cryptographic Library from SAP Service Marketplace at http://

service.sap.com/swdc.

2. Extract the package containing the library (sapcrypto.dll for Windows NT or

libsapcrypto.<ext> for UNIX), a license ticket (ticket), and the configuration tool

(sapgenpse).

3. On SAP Web Dispatcher, create the subdirectory sec for the PSE files. In the following, this

directory is referred to as the SECUDIR directory.

4. Copy the library, ticket, and sapgenpse to the SECUDIR directory.

2. Set the profile parameters for SAP Web Dispatcher as shown in the following table.

Parameter Value

rdisp/mshost <Host name of SAP NetWeaver PI system>

ms/http_port <Message server_HTTP_port of SAP NetWeaver PI system>

icm/server_port_1 PROT=HTTPS, PORT=443, TIMEOUT=300

SECUDIR <Path to sec folder>

ssl/ssl_lib <Path to sec folder>\sapcrypto.dll

ssl/server_pse <Path to sec folder>\SAPSSLS.pse

icm/HTTPS/verify_client 0

3. Create PSE and SSL certificate requests for SAP Web Dispatcher.

1. Switch to the SECUDIR directory.

2. In the command prompt, use the configuration tool’s get_pse command to create an

SSL server PSE as follows.

7 Appendix


2011-08-18 PUBLIC 127/134



NOTE

To avoid copying special characters, do not copy and paste the following command

text to the command prompt. Instead, enter it manually.

sapgenpse get_pse –p SAPSSLS.pse –r certreq.txt –x <password> “CN=<public internet

address>,OU=SAP-AG,O=SAP-AG,C=DE”

3. Check if SAPSSLS.pse is created along with a certreq.txt file.

4. Send the request to SAP Certification Authority (SAP CA) to be signed.

1. Request the SSL server certificate on SAP Service Marketplace at http://

service.sap.com/tcs.

The type of server for which the certificate will be used is SAP Web Application Server 6.20 and

Newer.

NOTE

You can request an SSL test server certificate on SAP Service Marketplace at http://

service.sap.com/ssltest.

2. Copy the content of the certreq.txt file and paste it in the certificate request.

SAP CA will return a certificate request response for each request that you send.

3. Copy the result to the certreq_answer.txt file.

5. Download SAP root certificate from SAP Service Marketplace at https://tcs.mysap.com/

invoke/tc/getCert?SAPServerCA.der and save it as SAPROOTCA.cert in the SECUDIR

directory.

6. Import certificate response.


2. In the command prompt, use the configuration tool’s import_own_cert command to

import the SSL server certificate response as follows:

sapgenpse import_own_cert –p SAPSSLS.pse –c certreq_answer.txt –x password> -r

SAPROOTCA.cert

7. Create credentials for the user running SAP Web Dispatcher.


2. In the command prompt, use the configuration tool’s seclogin command to create

credentials for a specific user as follows:

sapgenpse seclogin –p SAPSSLS.pse –x <password> -O [Windows_domain>\] <sid>adm

8. Restart SAP Web Dispatcher.

3. Configure HTTP on SAP NetWeaver PI server by setting the profile parameters for SAP Web

Dispatcher as shown in the following table.

Parameter Value

icm/server_port_<xx> PROT=HTTP.....

icm/HTTPS/verify_client 0

7 Appendix


128/134 PUBLIC 2011-08-18



http://service.sap.com/ssltest

http://service.sap.com/ssltest

https://tcs.mysap.com/invoke/tc/getCert?SAPServerCA.der

https://tcs.mysap.com/invoke/tc/getCert?SAPServerCA.der

For more information, see SAP Web Dispatcher and SSL on SAP Help Portal at http://help.sap.com/

saphelp_nw04/helpdata/en/d8/a922d7f45f11d5996e00508b5d5211/frameset.htm.

NOTE

In case the above URL does not work, you can find SAP Web Dispatcher and SSL on SAP Help Portal

at http://help.sap.com as follows:

1. Choose SAP NetWeaver SAP NetWeaver 2004 .

2. In the SAP NetWeaver 2004 library, choose SAP NetWeaver Solution Life Cycle Management

System Management SAP Web Dispatcher Architecture and Functions of the SAP Web Dispatcher SAP

Web Dispatcher and SSL .

Using Proxy in DMZ (HTTPS from Internet and HTTPS to SAP NetWeaver PI)

In this scenario, the proxy redirects the traffic from HTTPS 443 to the PI ABAP ICM HTTPS port. SAP

Sourcing sends the relevant business data, for example, master data or business process data, via SAP

NetWeaver Process Integration (SAP NetWeaver PI) SOAP adapter.


same.

2. Configure SSL/HTTPS for SAP NetWeaver PI.

3. Configure SAP NetWeaver PI for SSL for ABAP and Java.

Using SAP Web Dispatcher in DMZ (HTTPS from Internet and HTTPS to SAP NetWeaver PI)

SAP Web Dispatcher is a software load balancer that is installed outside the SAP NetWeaver Process



same.

2. Configure SSL/HTTPS for SAP NetWeaver PI.

3. Enable SAP Web Dispatcher for port 443 for HTTPS SSL.

4. Configure SAP Web Dispatcher for HTTPS 443 to HTTPS to PI ABAP ICM HTTPS. For more

information, see step 2 Configure HTTPS on SAP Web Dispatcher in the above scenario Using SAP Web

Dispatcher in DMZ (HTTPS from Internet and HTTP to SAP NetWeaver PI).

SAP Sourcing sends the relevant business data, for example, master data or business process data,

via SAP NetWeaver PI.

5. Configure SAP NetWeaver PI for SSL for ABAP and Java.

For more information, see SAP Web Dispatcher and SSL on SAP Help Portal at http://help.sap.com/

saphelp_nw04/helpdata/en/d8/a922d7f45f11d5996e00508b5d5211/frameset.htm. See also Note

above.

More Information

Integration Architecture for SAP ERP RFQ to SAP Sourcing RFP [page 71]

Integration Architecture for SAP Sourcing RFP Award to SAP ERP Purchase Order [page 74]

7 Appendix


2011-08-18 PUBLIC 129/134

http://help.sap.com/saphelp_nw04/helpdata/en/d8/a922d7f45f11d5996e00508b5d5211/frameset.htm


http://help.sap.com



Integration Architecture for SAP Sourcing RFP Award to SAP ERP Outline Agreement [page 78]

7.5 Publishing RFx to Different Subcontexts

Procedure

The standard integration works with a single subcontext. However, you can publish RFx to different

subcontexts within an enterprise as follows:

1. Create a new FTP/file import directory for each subcontext.

2. In SAP NetWeaver Process Integration (SAP NetWeaver PI), apply conditional logic to route the

request from SAP ERP (for example, to create an RFx in SAP Sourcing) to the respective file folder.

3. Configure the data import monitor (one for each subcontext). As user, specify the user with which

the objects are to be imported in the subcontext.

NOTE

The integrated document configuration (IDC) is used to determine which attributes are relevant

for integration. As the IDC is scoped at enterprise level, the IDC is common to all subcontexts.

More Information

Create Scheduled Tasks to Import XML Messages for Materials, Vendors, and RFx [page 20]

7.6 Extensions to Integration of SAP ERP and SAP Sourcing

You can extend the integration of SAP ERP and SAP Sourcing by enhancing or modifying the following

components:

■ SAP ERP

For material, vendor, and RFQ scenarios, you need to enhance IDocs if the existing IDoc interfaces

do not meet your requirements. For more information, see SAP Library for SAP NetWeaver on

SAP Help Portal at http://help.sap.com SAP NetWeaver Functional View SAP NetWeaver by Key

Capability Application Platform by Key Capability Platform-Wide Services Connectivity Components of SAP

Communication Technology Classical SAP Technologies (ABAP) IDoc Interface/ALE Development

Structure, Documentation, and Definition of IDoc Types Defining New IDoc Types Extending an IDoc

Type .

For purchase order and outline agreement scenarios, the RFC interfaces BBP_ES_PO_CREATE and

BBP_ES_OA_UPDATE have additional parameters such as EXTENSION_IN and EXTENSION_OUT to

support enhancements. For information about the parameter EXTENSION_IN, see the function

module documentation, for example, BAPI_CONTRACT_CREATE in the Function Builder (transaction

SE37).

■ SAP Sourcing

You can use the SAP Sourcing extension framework to enhance objects in SAP Sourcing.

7 Appendix

7.5 Publishing RFx to Different Subcontexts

130/134 PUBLIC 2011-08-18

http://help.sap.com

If you want to make a field mandatory in SAP Sourcing because the corresponding field has been

made mandatory in SAP ERP, you can use SAP Sourcing page customization.

If you want to carry out additional validations in SAP Sourcing, you can use custom scripting.

For more information, see SAP Library for SAP Sourcing on SAP Help Portal at http://

help.sap.com.

■ SAP NetWeaver Process Integration (SAP NetWeaver PI)

You can use the Integration Repository to enhance SAP Sourcing interface definitions, SAP ERP

interfaces, and their related mapping in your software component version. When creating your

software component version, you can build a dependency to the SAP software component version.

For more information, see SAP Library for SAP NetWeaver on SAP Help Portal at http://

help.sap.com SAP NetWeaver SAP NetWeaver PI SAP NetWeaver Process Integration Library

Developer's Guide Providing, Discovering, and Consuming Services Managing Services in the Enterprise Services

Repository Organizing and Managing Content in ESR Software Component Versions Underlying Software

Component Versions .

7 Appendix

7.6 Extensions to Integration of SAP ERP and SAP Sourcing

2011-08-18 PUBLIC 131/134

http://help.sap.com

http://help.sap.com

http://help.sap.com

http://help.sap.com

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

132/134 PUBLIC 2011-08-18

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™. 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.

2011-08-18 PUBLIC 133/134

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2011 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.