4RD S4HANA2021 Set-Up EN XX

Set-Up Instructions | PUBLIC
SAP S/4HANA
2022-01-24
Setting Up Direct Material Sourcing (4RD)

© 2021 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Version Note - On Premise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4 Introduction to Direct Material Sourcing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.1 Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2 Target Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.3 Use of this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.4 Terminology Used in this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.5 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
5 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1 Business Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6 Configure the S/4HANA Hub System on On-Premise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6.1 Configure Best Practices Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Bidder Role Definition(5RY). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Direct Material Sourcing Basic Settings (5OO). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.2 Configure Communication from Hub system to Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Create RFC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Create Logical System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Assign RFC Destinations for Synchronous Method Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Activate AIF Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Integration Options and SOA Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.3 Maintain Switch Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
6.4 S/4HANA Hub System Configuration Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Activate SAP S/4HANA Procurement Hub and Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Define Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Assign Connected Systems to RFC Destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configure Control Plane for the APIs of Central Procurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Define Company Code, Plant, Purchasing Organization for Connected System. . . . . . . . . . . . . . . . . .74
Define Local Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Define Material Groups from Respective Connected System into the Hub system. . . . . . . . . . . . . . . 76
Define Grouping of Company Codes of Connected Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Configure Version Management in Central Purchase Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Commodity Pricing Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

2 PUBLIC Content
Configure Header Condition for Central Purchase Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Maintain Condition Type Mapping for Purchasing Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
6.5 UI Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Configure Destination for Connected System on Frontend System. . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.6 Unified Key Mapping Service for Central Procurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Manage Key Mapping for Supplier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
6.7 Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Other Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
6.8 Extend Central Purchase Contract using BADIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.9 Central Procurement Operations Monitor – Central Contract Management Scenario. . . . . . . . . . . . . . .100
Monitor Connected System Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Monitor Central Contract Management Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
7 Configure the Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

7.1 ERP or S/4HANA On-premise as Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Create Trusted Connection from Connected System to SAP S/4HANA Fiori Frontend System. . . . . . 102
Configure OData Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Clean up Gateway Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Configure User-Defined Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Define Purchase Contract Document Type for Subordinate Central Contracts. . . . . . . . . . . . . . . . . 107
7.2 S/4HANA Cloud as Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Configure Communication Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Maintain Clickjacking Protection Whitelist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
8 Setup Integration with SAP S/4HANA for Supplier Quotation Management. . . . . . . . . . . . . . . . . 114
8.1 Prerequisites in BTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
8.2 Configuration in S/4HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Configure OData Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Manage Channel and Parameters for SAP Event Mesh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
8.3 Additional Service in BTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
9 Integration with SAP S/4HANA for Enterprise Contract Management(Optional). . . . . . . . . . . . . .116

9.1 Switch on Legal Transaction Facete in Sourcing Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
9.2 Switch on Integration with Enterprise Contract Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
9.3 Assign Linked Object Type to Default Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
9.4 Define Integration Variant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Assign Profile to Integration Variant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Assign Value of Set Type to Integration Mapping Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Set Active Indicator for Integration Variant Enablement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
10 Integration with SAP Enterprise Contract Assembly(Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . 121

10.1 Manage Document Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
11 Monitoring and Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Content PUBLIC 3
12 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
12.1 Authorization Objects & Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Authorization Objects & Roles for Preferred Supplier List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Authorization Objects & Roles for Sourcing Supplier List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
12.2 Known Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
12.3 Support & Ticket Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

4 PUBLIC Content
1 Version Note - On Premise
 Note
The following content is for the On Premise version.

Version Note - On Premise PUBLIC 5
2 Purpose
This document describes additional configuration steps that have to be carried out by customers in order to
activate Activate Direct material soucring process. As these configuration steps are customer-specific, they cannot
be delivered by SAP, and must be carried out by the customer.

6 PUBLIC Purpose
3 Document History
Version Date Change
1.0 First Version Document of SAP Direct

Material Sourcing for Release version
2021 OP

Document History PUBLIC 7
4 Introduction to Direct Material Sourcing
Direct material sourcing process allows central purchaser to have an overview of all the direct material
requirements across various plants and carry out the sourcing of the requirements appropriately.
In this process sourcing manager can create sourcing event (Sourcing project) to conduct sourcing with the
competitive suppliers and evaluate them to finally award the business to one or multiple capable suppliers and
create relevant documents like Purchase order or central contract to enable operational procurement of direct
materials.
4.1 Scope
Direct material sourcing process supports two major process
1. Strategic Sourcing
Key Process
1. Create ‘Sourcing project’ by adding ‘Materials’ from connected backend systems or by adding the ‘Free
text’ for the material which do not yet have the material number
2. Suppliers to be invited for sourcing is determined by preferred supplier list which is already maintained
based on ‘Material group’ and ‘Company code’ in the central hub system. Central purchaser can modify
the supplier list and the same can be approved as per the configured approval flow to eventually consider
the finalized set of suppliers for sourcing process
3. Central purchaser can optionally ‘Create’ or ‘Add’ legal transaction which adds associated legal and other
co-applicable documents to the sourcing project. These documents can be reviewed by participating
suppliers

8 PUBLIC Introduction to Direct Material Sourcing
4. Sourcing project is published after maintaining all relevant information for every material
5. Sourcing project publish can be optionally be put into approval workflow for better control of the process
6. Published ‘Sourcing project’ is viewable by participating suppliers. Suppliers have right to ‘Decline’ to
participate in the sourcing process
7. Participating suppliers can create ‘Supplier quotation’ and can revise multiple times until the end of the
submission time line
8. Central purchaser can compare, negotiate and finalize awarding scenario to award business to competitive
suppliers
9. Central purchaser can create legal transaction in ‘Supplier quotation’ which can be further reviewed by
suppliers
10. Supplier, central purchaser and other related stakeholders review all the legal and related documents and
sign off those documents offline. Legal transaction status reflects the readiness of the document related
process.
11. Finalised awarding scenario would go through ‘Approval process’ to finally create relevant ‘follow-on-
documents’
12. Purchase orders are created in the respective connected backend systems
13. Created central contract can be further enriched to distribute them as operational contracts in the
respective connected back-end systems
2. Demand driven sourcing
1. Create ‘Sourcing project’ by adding relevant purchase requisition items using ‘Process purchase
requisition centrally’ application
2. Suppliers to be invited for sourcing is determined by preferred supplier list which is already maintained
based on ‘Material group’ and ‘Company code’ in the central hub system. Central purchaser can modify
the supplier list and the same can be approved as per the configured approval flow to eventually consider
the finalized set of suppliers for sourcing process
3. Central purchaser can optionally ‘Create’ or ‘Add’ legal transaction which adds associated legal and other
co-applicable documents to the sourcing project. These documents can be reviewed by participating
suppliers
4. Sourcing project is published after maintaining all relevant information for every material
5. Sourcing project publish can be optionally be put into approval workflow for better control of the process

Introduction to Direct Material Sourcing PUBLIC 9
6. Published ‘Sourcing project’ is viewable by participating suppliers. Suppliers have right to ‘Decline’ to
participate in the sourcing process
7. Participating suppliers can create ‘Supplier quotation’ and can revise multiple times until the end of the
submission time line
8. Central purchaser can compare, negotiate and finalize awarding scenario to award business to competitive
suppliers
9. Central purchaser can create legal transaction in ‘Supplier quotation’ which can be further reviewed by
suppliers
10. Supplier, central purchaser and other related stakeholders review all the legal and related documents and
sign off those documents offline. Legal transaction status reflects the readiness of the document related
process.
11. Finalised awarding scenario would go through ‘Approval process’ to finally create relevant ‘follow-on-
documents’
12. Purchase orders are created in the respective connected backend systems
13. Created central contract can be further enriched to distribute them as operational contracts in the
respective connected back-end systems
4.2 Target Audience
This setup guide is intended for technical consultants/Administrators who want to set up or perform any
configuration activity to get Direct Material Sourcing for On-Premise edition working.
4.3 Use of this Document
This setup guide contains information about Direct Material Sourcing process and set-up related configuration to
help you get started in On-Premise environment.
It describes very basic steps for an easy introduction and working example.
4.4 Terminology Used in this Document
Table 1:
Terms Meaning
PO Purchase Order

Terms Meaning
RFC Remote Function Call
DMS Direct Material Sourcing
Table 2:
Terms Meaning
SAP S/4HANA HUB System Identifies the SAP S/4HANA system from releases 2021 OP.
The SAP S/4HANA system acts as a hub system when it is
connected to multiple connected systems.
 Note
You can find detail information in the following SAP Note:
3090957 - SAP S/4HANA for central procurement
2021: Release Information Note
Connected System Any ERP system from release ERP6.06 releases and above,
with add-on HUBERPI is considered as the connected system.
Any S/4HANA On-Premise 1709 and higher, with add-on

HUBS4IC is considered as connected system.
Any S/4HANA Cloud 1905 is considered as connected system.
You can find detail information for Integration Component HU

BERPI and HUBS4IC in the following SAP Notes:
2491065 - Release Information Note for HUBERPI Integra

tion Component in SAP S/4HANA for Central Procurement
2573672 - Release Information Note to Enable SAP S/

4HANA as a Back-End for Central Procurement
Logical System Identifies a unique combination of system ID and client of a

connected system. This unique combination enables data ex
change between the connected system and the SAP S/4HANA
Hub system.
4.5 Prerequisites
It is mandatory that scope item 4RD - Direct Material Sourcing is active. Scope item 4RI - Preferred Supplier List,
1RO - Master Data Integration and 1NN - Business Event Handling should also be active as prerequisites.

Introduction to Direct Material Sourcing PUBLIC 11
1XV - SAP S/4HANA for Enterprise Contract Management and 2OQ - Integration to SAP Enterprise Contract
Assembly are optional for the imeplementaion and you can choose to enable them when you need Enterprise
Contract integration.
If the scope item is not active, please request the activation via BCP – Ticket Component : XX-S4C-OPR-SRV.

5 Preparation
5.1 Business Roles
The following roles are provided as example roles from SAP. You can use these as templates to create your own
roles.
Table 1: Business Roles
Name (Role) ID (Role)
Configuration Expert - Business Process Configuration SAP_BR_BPC_EXPERT
Administrator SAP_BR_ADMINISTRATOR
Administrator - Data Replication SAP_BR_ADMINISTRATOR_DATA_REPL

Preparation PUBLIC 13
6 Configure the S/4HANA Hub System on
On-Premise
6.1 Configure Best Practices Content
In this chapter, you can get the configuration details that included in best practices content for this scope item.
If your system is set up by activation the best practices content, you can skip this chapter.
If your system is not set up by activation the best practices content or your system is an upgraded On Premise
system, you can refer the configuration details in this chapter to configure the required customizing manually.
 Note
For more details about Implementation of SAP S/4HANA with SAP Best Practices, you can refer to
Administration Guide to Implementation of SAP S/4HANA with SAP Best Practices.
6.1.1 Bidder Role Definition(5RY)
6.1.1.1 Define BP Roles
Use
In this activity, you can define new business role for bidder to for extend master data usage in process.

14 PUBLIC Configure the S/4HANA Hub System on On-Premise
Procedure
1. Access the transaction using one of the following navigation options:
SAP IMG Menu SAP Portfolio and Project Management Portfolio
Management Base System Interfaces SAP Human
Capital Management Integration SAP Porfolio and Project
Management System Customizing for SAP HCM SAP
Business Partner Business Partner Basic Settings
Business Partner Roles Define BP Roles
Transaction Code SPRO
2. On the Change View “Define BP Roles”: Overview screen, choose New Entries and make the following entries:
Std Assignment BP
BP Role Title Description BP Role Cat. Role ->BP Role Cat.
BBP001 Bidder Bidder BBP001 Checked
3. Save your entries.
6.1.2 Direct Material Sourcing Basic Settings (5OO)
6.1.2.1 Number Range Settings for Sourcing Project Process
6.1.2.1.1 Define Number Range for Sourcing Projects
Use
In this activity, you can define number range for sourcing project so that the creation can happen.

Configure the S/4HANA Hub System on On-Premise PUBLIC 15
Procedure
SAP IMG Menu Materials Management > Purchasing> Sourcing > Product
Sourcing > Sourcing Project and Supplier Quotation > Define
Number Range for Sourcing Projects
2. Choose Change Intervals.

3. On the Edit Intervals: Sourcing Project ID, Object SRCGPROJID screen, create the following entry:
Number Range Number Range

No. From Number To Number Status External
01 1000000000 1999999999 0 Unchecked
6.1.2.1.2 Define Number Range for Supplier Quotations for

Sourcing Projects
Use
In this activity, you can define number range for supplier quotations so that the creation can happen.
Procedure
SAP IMG Menu Materials Management Purchasing Sourcing
Product Sourcing Sourcing Project and Supplier Quotation
Define Number Range for Supplier Quotations for Sourcing
Projects

3. On the Edit Intervals: Srcg Proj Qtn ID, Object SPQTNID screen, create the following entry:

01 2000000000 2999999999 0 Unchecked
6.1.2.1.3 Define Number Range for Procurement Projects
Use
In this activity, you can define number range for procurement project so that the creation can happen.
Procedure
Define Number Range for Procurement Projects

3. On the Edit Intervals: Procmt Procjet ID, Object PROCMTPROJ screen, create the following entry:

01 3000000000 3999999999 0 Unchecked

6.1.2.1.4 Define Number Range for Negotiations
Use
In this activity, you can define number range for negotiations so that the creation can happen.
Procedure
Product Sourcing Negotiations Define Number Range for
Negotiations

3. On the Edit Intervals: : SorcProj.Negptiation, Object SRCGPRONGN screen, create the following entry:

01 4000000000 4999999999 0 Unchecked
6.1.2.1.5 Define Number Range for Awarding Scenarios
Use
In this activity, you can define number range for awarding scenario so that the creation can happen.

Procedure
Product Sourcing Awarding Scenario Define Number
Range for Awarding Scenarios

3. On the Edit Intervals: Awarding Scenario ID, Object SPAWDID screen, create the following entry:

01 5000000000 5999999999 0 Unchecked
6.1.2.1.6 Define Number Range for Temporary Condition

Amounts in Supplier Quotation
Use
In this activity, you can define number range for sourcing project quotation condition record so that the creation
can happen.
Procedure
Define Number Range for Temporary Condition Amounts in
Supplier Quotations


3. On the Edit Intervals: SPQTN Cond Record ID, Object SPQTNCRID screen, create the following entry:

01 00000001 99999999 0 Unchecked
6.1.2.2 Workflow for Sourcing Project Process
6.1.2.2.1 Sourcing Project WF Scenario Activation
Use
In this activity, you can activate the scenario of sourcing project workflow.
Procedure
SAP IMG Menu ABAP Platform Application Server Business
Management SAP Business Workflow Flexible Workflow
Scenario Activation
2. On the Change View “Activating a scenario” screen, choose New Entries and create the following settings:
Scenario Active
WS01800160 select
3. Save your settings.

6.1.2.2.2 Supplier List WF Scenario Activation
Use
In this activity, you can activate the scenario of supplier list workflow.
Procedure
Scenario Activation
Scenario Active
WS02000090 select
6.1.2.2.3 Awarding WF Scenario Activation
Use
In this activity, you can activate the scenario of awarding workflow.

Procedure
Scenario Activation
Scenario Active
WS01800213 select
6.1.2.2.4 Supplier List WF Task & Decision Key
Use
In this activity, you can maintain the workflow tasks and decision keys for supplier list workflow.
Procedure
1. Access the transaction using the following navigation path:
SAP IMG Menu ABAP Platform SAP Gateway Service Enablement
Content Workflow Settings Maintain Task Names and
Decision Options
2. On the Change View “Step Name”: Overview screen, choose New Entries and create following settings:
Workflow ID Step ID Step Description
WS02000090 0000000010 Approve Sourcing Supplier List

3. On the Change View “Step Name”: Overview screen, select the entry with Workflow ID WS02000090 Step ID
0000000010, choose Decision Keys in the Dialog Structure and create the following settings:
Key Decision Text Comment On Nature
1 Approve Unchecked POSITIVE
2 Reject Checked NEGATIVE
4. Save your settings and back to the Change View “Step Name”: Overview screen.
WS02000090 0000000052 Release of Sourcing Supplier List with

adaptations
6.1.2.2.5 SP&AW Workflow Task & Decision Keys
Use
In this activity, you can maintain the workflow tasks and decision keys for sourcing project and awarding workflow.
Procedure
1. Access the transaction using the following navigation path:
SAP IMG Menu ABAP Platform SAP Gateway Service Enablement
Content Workflow Settings Maintain Task Names and
Decision Options

WS01800160 0000000020 Release Sourcing Project
4. Save your settings and back to the Change View “Step Name”: Overview screen.
WS01800213 0000000020 Manual Release of Awarding Scenario
6.1.2.3 General Settings for Sourcing Project
6.1.2.3.1 Define Item Types for Sourcing Projects
Use
In this activity, you can define item types for sourcing project.

Procedure
Define Item Types for Sourcing Projects
2. On the Change View “Define Item Types for Sourcing Projects”: Overview screen, choose New Entries and create
following settings:
Item Type Item Type Item Classification Name
N Item C Complex Project Item
N Item G General Standard Item
S Item Set S Set Item Set
6.1.2.3.2 Define Group and Text for Follow-On Documents for

Supplier Quotations
Use
In this activity, you can define group and text for follow-on documents for supplier quotations.
Procedure
Follow-On Documents Define Group and Text for Follow-
On Documents for Supplier Quotations

2. On the Change View “Group and Text for Follow-On Documen..”: Overview screen, choose New Entries and
create following settings:
Follow-on Document Group Group Description
STD Standard
6.1.2.3.3 Define Follow-On Documents for Supplier

Quotations (Sourcing Projects)
Use
In this activity, you can define follow-on documents for supplier quotations(Sourcing Projects).
Procedure
Follow-On Documents Define Follow-On Documents for
Supplier Quotations (Sourcing Projects)
2. On the Change View “Define Follow-On Documents for Supplier Quo..”: Overview screen, choose New Entries
and create following settings:
Follow-On Document Group Group Description Cat
STD Standard C Central Contract
STD Standard F Purchase order

3. Save your settings and select the entry with Follow-On Document Group STD Cat C Central Contract, choose
Follow On Document Type in the Dialog Structure and create the following settings:
OTyp Doc. Type Descript.
HRMK Quantiy Contract
HRWK Standard
MK Quantity Contract
WK Value Contract
6.1.2.3.4 Define Sourcing Project Types
Use
In this activity, you can define sourcing project type.
Procedure
Define Sourcing Project Types
2. On the Change View “Define Sourcing Project Types”: Overview screen, choose New Entries and create following
settings:
Sourcing Project Type Follow-On Document Group Sourcing Project Type Description
ST STD Standard Sourcing

6.1.2.3.5 Define Document Types
Use
In this activity, you can assign internal note and external note as attachment type for sourcing project and supplier
quotations.
Procedure
SAP IMG Menu Logistics - General Product Lifecycle
Management(PLM) Document Management Control
Data Define DMS Document Types
2. On the Change View “ Define DMS Document Types”: Overview screen, choose entry with Ty. SL1 For External
Use , choose Define object links from Dialogue Strcutureand create following settings:
Type(DocumentType) Object Object Desc. Scr. No.
SL1 SPQTN Splr. Quotation (SP) 100
SL1 SRCGPROJ Sourcing Project 100
3. Save your settings, and go back to Define document types level, choose entry with Ty. SL9 For Internal Use,
choose Define object links from Dialogue Strcutureand create following settings:
Type(DocumentType) Object Object Desc. Scr. No.
SL9 SRCGPROJ Sourcing Project 100

6.1.2.4 ECM Integration Settings
6.1.2.4.1 Enable Enterprise Contract Management

Integration
Use
In this activity, you create the entry for business function that switch on/off the legal transaction facette in sourcing
project interface.
Procedure
Enable Enterprise Contract Management Integration
2. On the Change View “ Enable Enterprise Contract Management Integ.. ”: Overview screen, choose New Entries
Business Feature ID Feature State
SOURCINGPROJECTECMINTEGRATION 1 Inactive
6.1.2.4.2 Define Technical Types for Linked Object Types
Use
In this activity, you define technical types for linked object types.

Procedure
SAP IMG Menu Enterprise Contract Management General Settings
Define Technical Types for Linked Object Types
2. On the Change View “ Enable Enterprise Contract Management Integ.. ”: Overview screen, choose New Entries
Business En Semantic Ob Semantic Ob

LnkObj.TTP LnkObj.TeC tity ject ject Attribute Variable Name Text Field
SRPR Internal SAP I_SrcgProjNa SourcingProject SourcingPro SourcingProject SOURCING

meBySeman ject/Sourcing PROJECTNAME
ticKey ProjectVersion
SPQN Internal SAP I_SrcgProjQtn SourcingPro SourcingPro SupplierQuota SourcingPro

NameBySe jectQuotation jectQuotation/ tion jectQuotation
manticKey SrcgProjQuota Name
tionVersion
6.1.2.4.3 Define Linked Object Types
Use
In this activity, you define linked object types for sourcing project and supplier quotation.
Procedure
SAP IMG Menu Enterprise Contract Management General Settings
Define Linked Object Types

2. On the Change View “ Define Linked Object Types”: Overview screen, choose New Entries and create following
settings:
LnkObj. Ty Long Text LnkObj.TTp Integr.Lnk Default
0008 Sourcing Project SRPR Sourcing Project(SP) Checked
0009 Supplier Quotation SPQN Supplier Quota Checked

tion(SQN)
6.1.2.4.4 Define Integration Variants
Use
In this activity, you define identifying attributes and integration variants for sourcing project and supplier
quotations.
Procedure
SAP IMG Menu Enterprise Contract Management Integration
Integration with Business Objects Define Integration
Variants
2. On the Change View “ Define Integration Variants”: Overview screen, choose Define Identifying Attributes from
Dialogue Structure, choose New Entries and create following settings:
Text of Technical Field

Identifying Attributes Description CDS View Source Technical Field Name Name
SAP_SRCGPROJ_TYP Sourcing Project Type I_SOURCINGPRO SOURCINGPROJECT SOURCINGPROJECT

E JECTTYPETEXT TYPE TYPETEXT

Text of Technical Field
Identifying Attributes Description CDS View Source Technical Field Name Name
SAP_SPQTN_TYPE Supplier Quotation I_SOURCINGPRO SOURCINGPROJECT SOURCINGPROJECT

Type JECTTYPETEXT TYPE TYPETEXT
3. Save your settings, choose Define Integration Variant from Dialogue Structure, choose New Entries and create
following settings:
Int. Var. Description Integration Link Main Org
SRPR Sourcing Project Sourcing Project(SP) Company Code
SPQN Supplier Quotation Supplier Quotation(SQN) Company Code
6.1.2.4.5 Define Integration Variants
Use
In this activity, you maintain the integration variant mapping to identifying attributes, and variables mapping to
integration variant.
Procedure
Integration with Business Objects Define Integration
Variants

2. On the Change View “ Define Integration Variants”: Overview screen, select Int.Var. SPQN on Define Integration
Variant level, choose Map Integration Variant to Identifying Attributes from Dialogue Structure, choose New
Entries and create following settings:
Identifying Attributes Description
SAP_CM_COMPANY_CODE Company Code
SAP_CM_PURCH_ORG Purchasing Organization
SAP_SPQTN_TYPE Supplier Quotation Type
3. Save your settings, and go back to select Int.Var. SRPR on Define Integration Variant level, choose Map
Integration Variant to Identifying Attributes from Dialogue Structure, choose New Entries and create following
settings:
Identifying Attributes Description
SAP_CM_COMPANY_CODE Company Code
SAP_CM_PURCH_ORG Purchasing Organization
SAP_SRCGPROJ_TYPE Sourcing Project Type
4. Save your settings, and go back to select Int.Var. SPQN on Define Integration Variant level, choose Map
Variables to Integration Variant from Dialogue Structure, choose New Entries and create following settings:
Integration Mapping
Variable Description Set Type Technical Type of Set Technical Type Text
S_MAIN_ENTITY Main Entity (Supplier/ Entity 06 Business Partner

Bidder)
S_SOURCE_LINKED_O Linked Object Linked Object SQN Supplier Quotation

BJECT
SAP_SPQTN_PUR Purchase Organization Entity 05 Purchase Organization

CHASE_ORG
5. Save your settings, and go back to select Int.Var. SRPR on Define Integration Variant level, choose Map Variables
to Integration Variant from Dialogue Structure, choose New Entries and create following settings:
Integration Mapping
S_MAIN_ENTITY Main Entity (Purchase Entity 05 Purchase Organization

Organization)
S_SOURCE_LINKED_O Linked Object Linked Object SP Sourcing Project

BJECT

Integration Mapping
SAP_SRCGPROJ_BUSI Business Partner Entity 06 Business Partner

_PARTNER (Supplier/Bidder)
SAP_SRCGPROJ_PUR Purchaser Responsible Internal Contact

CHASE_RESP
6.1.2.4.6 Define Category Qualifier and Property
Use
In this activity, you maintain the category qualifiers for supplier quotations.
Procedure
SAP IMG Menu Enterprise Contract Management Categories Define
Category Qualifier and Property
2. On the Change View “ Define Category Qualifier and Property”: Overview screen, choose Define Category
Qualifiers from Dialogue Structure, choose New Entries and create following settings:
Category
Qualifier Category Qualifier Name
SAP_SPQT Visible in Supplier Quotation Management

NM_TAGS
SAP_SPQT Acceptance / Rejection Required

NM_TAGS_
ACCP_REQ
D

Category
Qualifier Category Qualifier Name
SAP_SPQT Confirmation Required

NM_TAGS_
CONF_REQ
D
SAP_SPQT Display
NM_TAGS_
DISPLAY
6.1.2.4.7 Define Category Qualifier and Property
Use
In this activity, you maintain the qualifier hierarchies for supplier quotations.
Procedure
SAP IMG Menu Enterprise Contract Management Categories Define
Category Qualifier and Property
2. On the Change View “ Define Category Qualifier and Property”: Overview screen, choose Define Qualifier
Hierarchies from Dialogue Structure, choose New Entries and create following settings:
Catgory Parent Category

Qualifier Catgory Qualifier Name Qualifier Description Is Select
SAP_SPQT Visible in Supplier Quotation Man Visible in Supplier Quotation Man

NM_TAGS agement agement

Catgory Parent Category
Qualifier Catgory Qualifier Name Qualifier Description Is Select
SAP_SPQT Acceptance / Rejection Required SAP_SPQTNM_TAGS Acceptance / rejection required X

NM_TAGS_
ACCP_REQ
D
SAP_SPQT Confirmation Required SAP_SPQTNM_TAGS Confirmation required X

NM_TAGS_
CONF_REQ
D
SAP_SPQT Display SAP_SPQTNM_TAGS Document for display only X

NM_TAGS_
DISPLAY
6.1.2.4.8 Define Document Stamps
Use
In this activity, you maintain the document stamps for supplier quotations.
Procedure
SAP IMG Menu Enterprise Contract Management Documents Define
Document Stamps

2. On the Change View “ Define Document Stamps”: Overview screen, choose New Entries and create following
settings:
Stamp
Name Long Text MultStamps
RQTN Rejected by supplier Unchecked
AQTN Accepted by supplier Unchecked
CQTN Confirmed by supplier Unchecked
6.1.2.5 ECA Integration Settings
6.1.2.5.1 SP- Document Variables
Use
In this activity, you create the document variables and for sourcing project.
Procedure
Integration with Enterprise Contract Assembly Variables
Define Document Variables
2. On the Change View “ Define Document Variables ”: Overview screen, choose Maintain Variable/Association
Source from Dialogue Structure, choose New Entries and create following settings:
Variable CDS View Name Variable Description
SourcingProjectAllowedCurrencies C_SRCGPROJALLWDCRCYDOCVARBL Allowed Currencies for Sourcing Project
SourcingProjectContacts C_SRCGPROJCONTACTDOCVARBL Contacts in Sourcing Project

SourcingProjectDeliveryAddress C_SRCGPROJDELIVERYADDRDOC Delivery Address in Sourcing Project

VARBL
SourcingProjectDemandManagement C_SRCGPROJDMNDDISTRDOCVARBL Demand Management in Sourcing

Project
SourcingProject C_SOURCINGPROJECTDOCVARBL Sourcing Project
SourcingProjectItem C_SOURCINGPROJECTITEMDOC Sourcing Project Item

VARBL
SourcingProjectItemIncoterms C_SRCGPROJITMINCOTERMSDOC Incoterms for Sourcing Project Item

VARBL
SourcingProjectItemLinking C_SRCGPROJITEMLINKAGEDOC Item Linking in Sourcing Project

VARBL
SourcingProjectItemPaymentTerms C_SRCGPROJITEMPAYTTRMSDOC Payment Terms for Sourcing Project

VARBL Item
SourcingProjectProcurementProject C_SRCGPROJPROCMTPROJDOC Procurement Project in Sourcing

VARBL Project
SourcingProjectItemShippingInstruc C_SRCGPROJSHIPGINSTRNDOC Shipping Instructions for SP Item

tions VARBL
3. Save your settings, and select the corresponding variables, choose Maintain Variable Source Field Alias from
Ref.
Field/ Curr/
Alias/Assoc. Associ Quan Data Leng Dec.Pla
Variable Technical Field Name ation Field Type th ces Long Text
SourcingPro SRCGPROJALLO SrcgProjAllo Field CUKY 5 Allowed Currencies

jectAllowed WEDCURRENCY wedCurrency
Currencies
SourcingPro CURRENCYNAME CurrencyName Field CHAR 40 Name of Currency

jectAllowed
Currencies
SourcingPro CURRENCY CurrencyShort Field CHAR 15 Short Name of Cur

jectAllowed SHORTNAME Name rency
Currencies
SourcingPro BUSINESSPART BusinessPart Field CHAR 10 Business Partner

jectContacts NER ner

Ref.
Field/ Curr/
SourcingPro SourcingProject SourcingPro Field CHAR 4 Contact Category

jectContacts ContactsCATE jectContacts
GORY Category
SourcingPro SOURCINGPRO SourcingPro Field RAW 16 Sourcing Project

jectContacts JECTUUID jectUUID UUID
SourcingPro SRCGPROJCNTC SrcgProjCntc Field CHAR 1 Visible to Supplier

jectContacts TISVISIBLETO tIsVisibleTo
SUPLR Suplr
SourcingPro SourcingProject SourcingPro Field CHAR 40 Name of Contact Cat

jectContacts ContactsCAT jectContacts egory
NAME CatName
SourcingPro SRCGPROJAD SrcgProjAd Field CHAR 10 Address Number

jectDeliver DRESSID dressID
yAddress
SourcingPro COMPANYCODE CompanyCode Field CHAR 4 Company Code

jectDemand
Management
SourcingPro PLANT Plant Field CHAR 4 Plant

jectDemand
Management
SourcingPro PROCUREMENT Procurement Field CHAR 10 Procurement Project

jectDemand PROJECT Project
Management
SourcingPro PURCHA Purcha Field CHAR 3 Purchasing Group

jectDemand SINGGROUP singGroup
Management
SourcingPro SOURCINGPRO SourcingPro Field RAW 16 Item UUID

jectDemand JECTITEMUUID jectItemUUID
Management
SourcingPro SRCGPRO SrcgPro Field CHAR 9 Unconfirmed De

jectDemand JITMDMNDOP jItmDmndOp mand
Management TIONALITY tionality
SourcingPro PROCUREMENT Procurement Field CHAR 60 Name of Procure

jectDemand PROJECTNAME ProjectName ment Project
Management

Ref.
Field/ Curr/
SourcingPro PLANTNAME PlantName Field CHAR 30 Plant Name

jectDemand
Management
SourcingPro COMPANYCODE CompanyCode Field CHAR 25 Company Name

jectDemand NAME Name
Management
SourcingPro PURCHASINGOR PurchasingOr Field CHAR 4 Purchasing Organiza

jectDemand GANIZATION ganization tion
Management
SourcingPro PROCMTHUB ProcmtHubPur Field CHAR 20 Name of Purchasing

jectDemand PURGORGNAME gOrgName Organisation
Management
SourcingPro SRCGPROJFOL SrcgProjFollo Field CHAR 1 Category of Follow-

jectDemand LOWONDOCU wOnDocument On Document
Management MENTCAT Cat
SourcingPro PURCHASINGDO PurchasingDo Field CHAR 60 Name fo Category of

jectDemand CUMENTCATE cumentCate Document
Management GORYNAME goryName
SourcingPro SRCGPROJFOL SrcgProjFollo Field CHAR 4 Type of Follow-On

jectDemand LOWONDOCU wOnDocument Document
Management MENTTYPE Type
SourcingPro PURCHASINGDO PurchasingDo Field CHAR 20 Name of Type of

jectDemand CUMENTTYPE cumentType Document
Management NAME Name
SourcingPro SourcingPro Multiple Allowed Currency

ject jectAllowed Associa
Currencies cion
SourcingPro SourcingPro Multiple Contacts

ject jectContacts Associa
cion
SourcingPro SourcingPro Multiple Demand Manage

jectItem jectDemand Associa ment
Management cion

Ref.
Field/ Curr/
SourcingPro SourcingPro Multiple Item

ject jectItem Associa
cion
SourcingPro SourcingPro Multiple Item Incoterms

jectItem jectItemInco Associa
terms cion
SourcingPro SourcingPro Multiple Item Linking

jectItem jectItemLinking Associa
cion
SourcingPro SourcingPro Multiple Item Payment Terms

jectItem jectItemPay Associa
mentTerms cion
SourcingPro SourcingPro Multiple Procurement Project

ject jectProcure Associa
mentProject cion
SourcingPro SourcingPro Multiple Item Shipping In

jectItem jectItemShip Associa structions
pingInstruc cion
tions
SourcingPro CASHDIS CashDis Field DEC 3 Days 1

ject COUNT1DAYS count1Days
SourcingPro CASHDIS CashDis Field DEC 5 3 Discount Percent 1

ject COUNT1PERCENT count1Percent

ject COUNT2DAYS count2Days

ject COUNT2PER count2Percent
CENT

ject
SourcingPro CREATIONDATE CreationDate Field DEC 21 7 Created On

ject TIME Time
SourcingPro DOCUMENTCUR DocumentCur Field CUKY 5 Document Currency

ject RENCY rency

Ref.
Field/ Curr/
SourcingPro EXTERNALSOUR ExternalSour Field CHAR 70 External Reference

ject CINGPROJEC cingProjectRef
TREF
SourcingPro INCOTERM IncotermsClas Field CHAR 3 Incoterms

ject SCLASSIFICATION sification
SourcingPro INCOTERMSLO IncotermsLoca Field CHAR 70 Incoterms Location 2

ject CATION2 tion2
SourcingPro INCOTERM Incoterm Field CHAR 28 Incoterms (Part 2)

ject STRANSFERLO sTransferLoca
CATION tion
SourcingPro INCOTERMSVER IncotermsVer Field CHAR 4 Incoterms Version

ject SION sion
SourcingPro MATERIALGROUP MaterialGroup Field CHAR 9 Material Group

ject
SourcingPro NETPAYMENT NetPayment Field DEC 3 Days Net

ject DAYS Days
SourcingPro PAYMENTTERMS PaymentTerms Field CHAR 4 Payment Terms

ject
SourcingPro PURCHASER Purchaser Field NUMC 8 Purchaser Responsi

ject RESPWORKA RespWorkA ble
GREEMENT greement

ject SINGGROUP singGroup

ject GANIZATION ganization tion
SourcingPro PURCONTRVALI PurContrValidi Field DATS 8 End of Validity Period

ject DITYENDDATE tyEndDate
SourcingPro PURCONTRVALI PurContrValidi Field DATS 8 Start of Validity Pe

ject DITYSTARTDATE tyStartDate riod
SourcingPro QTNLATESTSUB QtnLatestSub Field DEC 21 7 Submission Deadline

ject MISSIONDATE missionDate
TIME Time

Ref.
Field/ Curr/
SourcingPro SOURCINGPRO SourcingPro Field CHAR 10 Sourcing Project

ject JECT ject
SourcingPro SOURCINGPRO SourcingPro Field CHAR 60 Name of Sourcing

ject JECTNAME jectName Project
SourcingPro SOURCINGPRO SourcingPro Field NUMC 5 Version of Sourcing

ject JECTVERSION jectVersion Project
SourcingPro SRCGPROJ SrcgProj Field DEC 21 7 Published On

ject PUBGDTETME PubgDteTme
SourcingPro SRCGPROJTOTAL SrcgProjTotal Field Docu CURR 15 2 Total Target Amount

ject TARGETAMOUNT TargetAmount ment
Cur
rency
SourcingPro SOURCINGPRO SourcingPro Field CHAR 2 Sourcing Project Type

ject JECTTYPE jectType
SourcingPro SOURCINGPRO SourcingPro Field CHAR 40 Description of Sourc

ject JECTTYPETEXT jectTypeText ing Project Type

ject NAME Name
SourcingPro PURCHASING Purchasing Field CHAR 18 Name of Purchasing

ject GROUPNAME GroupName Group
SourcingPro PURCHASINGOR PurchasingOr Field CHAR 20 Name of Purchasing

ject GANIZATION ganization Organization
NAME Name
SourcingPro MATERIAL MaterialGroup Field CHAR 20 Name of Material

ject GROUPTEXT Text Group
SourcingPro MATERIAL MaterialGroup Field CHAR 20 Name of Purchasing

ject GROUPNAME Name Organization

ject

ject SHORTNAME Name rency

Ref.
Field/ Curr/
SourcingPro PURCHASER Purchaser Field CHAR 80 Full Name of Pur

ject RESPFULLNAME RespFullName chaser Responsible
SourcingPro INCOTERM IncotermsClas Field CHAR 30 Incoterms Classifica-

ject SCLASSIFICA sificationName tion Name
TIONNAME
SourcingPro INCOTERMSVER IncotermsVer Field CHAR 30 Name of Incoterms

ject SIONNAME sionName Version
SourcingPro SRCGPROJFOL SrcgProjFollo Field CHAR 1 Category of Follow-

ject LOWONDOCU wOnDocument On Document
MENTCAT Cat
SourcingPro SRCGPROJFOL SrcgProjFollo Field CHAR 4 Type of Follow-On

ject LOWONDOCU wOnDocument Document
MENTTYPE Type
SourcingPro PURCHASINGDO PurchasingDo Field CHAR 20 Name for Type of Fol

ject CUMENTTYPE cumentType low-On Document
NAME Name

jectItem
SourcingPro DOCUMENTCUR DocumentCur Field CUKY 5 Document Currency

jectItem RENCY rency
SourcingPro FORMATTEDITE FormattedIte Field CHAR 60 Item Number

jectItem MID mID
SourcingPro MANUALDELI ManualDeliver Field CHAR 10 Delivery Address

jectItem VERYADDRESSID yAddressID
SourcingPro MATERIAL Material Field CHAR 40 Material

jectItem
SourcingPro MATERIALGROUP MaterialGroup Field CHAR 9 Material Group

jectItem
SourcingPro MAXIMUMRE MaximumRe Field Re QUAN 13 3 Maximum Requested

jectItem QUESTEDQUAN questedQuan ques Quantity
TITY tity ted
Quan
tityU
nit

Ref.
Field/ Curr/
SourcingPro PERFORMANCE Performance Field DATS 8 End of Performance

jectItem PERIODENDDATE PeriodEndDate Period
SourcingPro PERFORMANCE Performance Field DATS 8 Start of Performance

jectItem PERIODSTART PeriodStart Period
DATE Date

jectItem
SourcingPro PRODUCTTYPE ProductType Field CHAR 4 Product Type

jectItem
SourcingPro PURCHASERE PurchaseRe Field CHAR 10 Purchase Requisition

jectItem QUISITION quisition
SourcingPro PURCHASERE PurchaseRe Field NUMC 5 Item in Purchase

jectItem QUISITIONITEM quisitionItem Requisition

jectItem SINGGROUP singGroup

jectItem GANIZATION ganization tion
SourcingPro REFERENCEDELI ReferenceDeli Field CHAR 10 Delivery Address

jectItem VERYADDRESSID veryAddressID
SourcingPro REQUESTEDDELI RequestedDeli Field DATS 8 Requested Delivery

jectItem VERYDATE veryDate Date
SourcingPro REQUESTED Requested Field Re QUAN 13 3 Requested Quantity

jectItem QUANTITY Quantity ques
ted
Quan
tityU
nit
SourcingPro REQUESTED Requested Field UNIT 3 Requested Quantity

jectItem QUANTITYUNIT QuantityUnit Unit
SourcingPro SOURCINGPRO SourcingPro Field NUMC 5 Sourcing Project Item

jectItem JECTITEM jectItem
SourcingPro SOURCINGPRO SourcingPro Field CHAR 1 Item Type

jectItem JECTITEMTYPE jectItemType

Ref.
Field/ Curr/
SourcingPro SRCGPROJITEM SrcgProjItem Field CHAR 1 Item Classification

jectItem CLASSIFICATION Classification
SourcingPro SRCGPROJITEM SrcgProjItem Field CHAR 40 Item Description

jectItem DESCRIPTION Description
SourcingPro SRCGPROJITE SrcgProjIte Field CHAR 10 Unconfirmed De

jectItem MUNCONFDDE mUnconfdDe mand
MANDRSN mandRsn
SourcingPro SRCGPROJITEM SrcgProjItem Field Docu CURR 15 2 Target Amount

jectItem TARGETAMOUNT TargetAmount ment
Cur
rency
SourcingPro SRCGPROJITEM SrcgProjItem Field Docu CURR 15 2 Total Target Amount

jectItem TOTALTARGETA TotalTargetA ment
MOUNT mount Cur
rency
SourcingPro STORAGELOCA StorageLoca Field CHAR 4 Storage Location

jectItem TION tion
SourcingPro SOURCINGPRO SourcingPro Field CHAR 60 Name of Item Tye

jectItem JECTITEMTYPE jectItemType
NAME Name
SourcingPro SRCGPROJITEM SrcgProjItem Field CHAR 60 Name of Item Classi

jectItem CLASSIFICATION Classification fication
NAME Name
SourcingPro PRODUCTTYPE ProductType Field CHAR 40 Name of Product

jectItem NAME Name Type
SourcingPro MATERIAL MaterialGroup Field CHAR 20 Name of Material

jectItem GROUPNAME Name Group
SourcingPro MATERIAL MaterialGroup Field CHAR 60 Description of Mate

jectItem GROUPTEXT Text rial Group
SourcingPro UNITOFMEASUR UnitOfMeasur Field CHAR 30 Long Name of Unit of

jectItem ELONGNAME eLongName Measure
SourcingPro UNITOFMEASUR UnitOfMeasur Field CHAR 10 Name of Unit of

jectItem ENAME eName Measure

Ref.
Field/ Curr/

jectItem

jectItem NAME Name
SourcingPro PROCMTHUB ProcmtHubPur Field CHAR 20 Name of Purchasing

jectItem PURGORGNAME gOrgName Organization
SourcingPro PURCHASINGDO PurchasingDo Field CHAR 60 Name fo Category of

jectItem CUMENTCATE cumentCate Document
GORYNAME goryName
SourcingPro PURCHASINGDO PurchasingDo Field CHAR 20 Name of Type of

jectItem CUMENTTYPE cumentType Document
NAME Name

jectItem

jectItem SHORTNAME Name rency

jectItemInco
terms
SourcingPro INCOTERM IncotermsClas Field CHAR 3 Incoterms

jectItemInco SCLASSIFICATION sification
terms

jectItemInco CATION1 tion1
terms

jectItemInco CATION2 tion2
terms
SourcingPro INCOTERM Incoterm Field CHAR 28 Incoterms (Part 2)

jectItemInco STRANSFERLO sTransferLoca
terms CATION tion
SourcingPro INCOTERMSVER IncotermsVer Field CHAR 4 Incoterms Version

jectItemInco SION sion
terms

Ref.
Field/ Curr/

jectItemInco
terms
SourcingPro SOURCINGPRO SourcingPro Field RAW 16 Item UUID

jectItemLink JECTITEMUUID jectItemUUID
ing
SourcingPro SOURCINGPRO SourcingPro Field RAW 16 Sourcing Project

jectItemLink JECTUUID jectUUID UUID
ing
SourcingPro SRCGPROJECTI SrcgProjectI Field RAW 16 Item Linking UUID

jectItemLink TEMLINKA temLinka
ing GEUUID geUUID
SourcingPro SRCGPROJITEM SrcgProjItem Field RAW 16 Item UUID

jectItemLink LINKEDSTA LinkedSta
ing BLEUUID bleUUID

jectItemPay COUNT1DAYS count1Days
mentTerms

jectItemPay COUNT1PERCENT count1Percent
mentTerms

jectItemPay COUNT2DAYS count2Days
mentTerms

jectItemPay COUNT2PER count2Percent
mentTerms CENT

jectItemPay
mentTerms
SourcingPro NETPAYMENT NetPayment Field DEC 3 Days Net

jectItemPay DAYS Days
mentTerms

Ref.
Field/ Curr/
SourcingPro PAYMENTTERMS PaymentTerms Field CHAR 4 Payment Terms

jectItemPay
mentTerms

jectItemPay
mentTerms

jectItemPay
mentTerms
SourcingPro PAYMENTTERMS Payment Field CHAR 30 Name of Payment

jectItemPay NAME TermsName Terms
mentTerms
SourcingPro SRCGPROJPRO SrcgProjPro Field CHAR 10 Procurement Project

jectProcure CUREMENTPRO curementPro
mentProject JECT ject

jectItemShip
pingInstruc
tions

jectItemShip
pingInstruc
tions
SourcingPro SHIPPINGIN ShippingIn Field CHAR 2 Shipping Instructions

jectItemShip STRUCTION struction
pingInstruc
tions

jectItemInco NAME Name
terms
SourcingPro INCOTERM IncotermsClas Field CHAR 30 Incoterms Classifica-

jectItemInco SCLASSIFICA sificationName tion Name
terms TIONNAME

Ref.
Field/ Curr/
SourcingPro INCOTERMSVER IncotermsVer Field CHAR 30 Name of Incoterms

jectItemInco SIONNAME sionName Version
terms
4. Save your Settings
6.1.2.5.2 SQTN - Document Variables
Use
In this activity, you create the document variables and for supplier quotation.
Procedure
Integration with Enterprise Contract Assembly Variables
Define Document Variables
2. On the Change View “ Define Document Variables ”: Overview screen, choose Maintain Variable/Association
Source from Dialogue Structure, choose New Entries and create following settings:
SupplierQuotationDemandManage C_SPQTNITEMDEMANDDISTRDOC Demand Management in Supplier Quo

ment VAR tation
SupplierQuotation C_SOURCINGPROJQTNDOCVARBL Supplier Quotation
SupplierQuotationItem C_SRCGPROJQTNITEMDOCVARBL Supplier Quotation Item
SupplierQuotationIncoterms C_SPQTNITEMINCOTERMSDOCVAR Incoterms for Supplier Quotation Item

SupplierQuotationItemLinking C_SRCGPROJQTNITEMLINKDOCVAR Item Linking in Supplier Quotation
SupplierQuotationItemPaymentTerms C_SRCGPROJQTNITMPAYTTERMDOC Payment Terms for SQ Item

VAR
SupplierQuotationItemConditionA C_SRCGPROJQTNITMCNDNAMTDOC Condition Amount in SQ Item

mount VAR
SupplierQuotationItemConditionValid R_SRCGPROJQTNITMCNDNVALIDITY Condition Validity in SQ Item

ity
SupplierQuotationItemShippingInstruc C_SRCGPROJQTNITMSHIPINSTDOC Shipping Instructions for SQ Item

tions VAR
SupplierQuotationSupplierContacts C_SRCGPROJQTNSUPLRCNTCTDOC Supplier Contacts in Supplier Quotation

VAR
3. Save your settings, and select the corresponding variables, choose Maintain Variable Source Field Alias from
Field/ Ref.
Asso Curr/
Alias/Assoc. Association cia Quan Data Len Dec.Pl
Variable Technical Field Name Path tion Field Type gth aces Long Text
SupplierQuota COMPANYCODE CompanyCode Field CHAR 4 Company

tionDemand Code
Management
SupplierQuota MAXANNUALRE MaxAnnualRe Field Re QUAN 13 3 Maximum

tionDemand QUESTEDQUAN questedQuan ques Requested
Management TITY tity ted Quantity
Quan
tityU
nit
SupplierQuota PLANT Plant Field CHAR 4 Plant

tionDemand
Management
SupplierQuota PROCUREMENT Procurement Field CHAR 10 Procure

tionDemand PROJECT Project ment
Management Project
SupplierQuota PURCHA Purcha Field CHAR 3 Purchasing

tionDemand SINGGROUP singGroup Group
Management

Field/ Ref.
Asso Curr/
SupplierQuota PURCHASINGOR PurchasingOr Field CHAR 4 Purchasing

tionDemand GANIZATION ganization Organiza
Management tion
SupplierQuota REQUESTED Requested Field UNIT 3 Unit of Re

tionDemand QUANTITYUNIT QuantityUnit quested
Management Quantity
SupplierQuota SRCGPROJQTN SrcgProjQtnTo Field Re QUAN 13 3 Total Of

tionDemand TOTOFFERED tOfferedQuan ques fered Quan
Management QUANTITY tity ted tity
Quan
tityU
nit
SupplierQuota STORAGELOCA StorageLoca Field CHAR 4 Storage Lo

tionDemand TION tion cation
Management
SupplierQuota PLANTNAME PlantName Field CHAR 30 Plant Name

tionDemand
Management

tionDemand NAME Name Name
Management
SupplierQuota PURCHASING Purchasing Field CHAR 18 Name of

tionDemand GROUPNAME GroupName Purchasing
Management Group
SupplierQuota PURCHASINGOR PurchasingOr Field CHAR 20 Name of

tionDemand GANIZATION ganization Purchasing
Management NAME Name Organiza
tion
SupplierQuota SupplierQuota Multi Demand

tionItem tionDemand ple Manage
Management Asso ment
cia
cion

Field/ Ref.
Asso Curr/
SupplierQuota SupplierQuota Multi Item

tion tionItem ple
Asso
cia
cion
SupplierQuota SupplierQuota Multi Incoterms

tionItem tionIncoterms ple for Item
Asso
cia
cion
SupplierQuota SupplierQuota Multi Payment

tionItem tionItemPay ple Terms for
mentTerms Asso Item
cia
cion
SupplierQuota SupplierQuota Multi Condition

tionItem tionItemCondi ple Amount in
tionAmount Asso Item
cia
cion
SupplierQuota SupplierQuota Multi Condition

tionItem tionItemCondi ple Valdty in
tionValidity Asso Item
cia
cion
SupplierQuota SupplierQuota Multi Shipping

tionItem tionItemShip ple Instruc
pingInstruc Asso tions for
tions cia Item
cion
SupplierQuota SupplierQuota Multi Supplier

tion tionSupplier ple Contacts
Contacts Asso
cia
cion
SupplierQuota BIDDER Bidder Field CHAR 10 Business

tion Partner

Field/ Ref.
Asso Curr/
SupplierQuota BUSINESSPART BusinessPart \_BUSINESS Field CHAR 80 Name of

tion NERNAME nerName PARTNER Business
Partner
SupplierQuota CASHDIS CashDis Field DEC 3 Days 1

tion COUNT1DAYS count1Days
SupplierQuota CASHDIS CashDis Field DEC 5 3 Discount

tion COUNT1PER count1Percent Percent 1
CENT

tion COUNT2DAYS count2Days

tion COUNT2PER count2Percent Percent 2
CENT

tion Code
SupplierQuota COMPANYCODE CompanyCode \_COMPANY Field CHAR 40 Company

tion NAME Name CODE Name
SupplierQuota CURRENCYNAME CurrencyName \_DOCU Field CHAR 20 Name of

tion MENTCUR Document
RENCY Currency
SupplierQuota CURRENCY CurrencyShort \_DOCU Field CHAR 3 Short

tion SHORTNAME Name MENTCUR Name of
RENCY Document
Currency
SupplierQuota DOCUMENTCUR DocumentCur Field CUKY 5 Document

tion RENCY rency Currency
SupplierQuota EXTERNALSOUR ExternalSour Field CHAR 70 External

tion CINGPRO cingProjectQtn Reference
JECTQTNREF Ref
SupplierQuota LOGICALSYSTEM LogicalSystem Field CHAR 10 Logical

tion System
SupplierQuota MATERI MaterialGroup Field CHAR 9 Material

tion ALGROUP Group

Field/ Ref.
Asso Curr/
SupplierQuota MATERIAL MaterialGroup \_MATERI Field CHAR 60 Name of

tion GROUPNAME Name ALGROUP Material
\_TEXT Group
SupplierQuota MATERIAL MaterialGroup \_MATERI Field CHAR 60 Description

tion GROUPTEXT Text ALGROUP of Material
\_TEXT Group
SupplierQuota NETPAYMENT NetPayment Field DEC 3 Days Net

tion DAYS Days

tion SINGGROUP singGroup Group
SupplierQuota PURCHASING Purchasing \_PURCHA Field CHAR 18 Name of

tion GROUPNAME GroupName SINGGROUP Purchasing
Group

tion GANIZATION ganization Organiza
tion
SupplierQuota PURCHASINGOR PurchasingOr \_PURCHA Field CHAR 20 Name of

tion GANIZATION ganization SINGORGA Purchasing
NAME Name NIZATION Organiza
tion
SupplierQuota QTNLATESTSUB QtnLatestSub Field TMST Submission

tion MISSIONDATE missionDate Deadline
TIME Time
SupplierQuota SOURCINGPRO SourcingPro \_SOUR Field CHAR 60 Name of

tion JECTNAME jectName CINGPRO Sourcing
JECT Project
SupplierQuota SOURCINGPRO SourcingPro Field CHAR 10 Supplier

tion JECTQUOTATION jectQuotation Quotation
SupplierQuota SOURCINGPRO SourcingPro Field RAW 16 Supplier

tion JECTQUOTATIO jectQuotatio Quotation
NUUID nUUID UUID
SupplierQuota SOURCINGPRO SourcingProjec Field RAW 16 Sourcing

tion JECTUUID tUUID Project
UUID

Field/ Ref.
Asso Curr/
SupplierQuota SRCGPROJQT SrcgProjQtnOf Field CUKY 5 Quotation

tion NOFFERCUR ferCurrency Currency
RENCY
SupplierQuota SRCGPROJQTN SrcgProjQtn Field SrcgP CURR 15 2 Total

tion TOTNETAMT TotNetAmt rojQt Amount
nOf
fer
Cur
rency
SupplierQuota SRCGPROJQUO SrcgProjQuota Field NUMC 5 Version

tion TATIONVERSION tionVersion
SupplierQuota SOURCINGPRO SourcingPro Field CHAR 60 Name

tion JECTQUOTATION jectQuotation
NAME Name
SupplierQuota ALTERNATIVEI AlternativeIte Field INT4 10 Alternative

tionItem TEMID mID Item ID

tionItem Code
SupplierQuota FORMATTEDITE FormattedIte Field CHAR 60 Item Num

tionItem MID mID ber
SupplierQuota HIERARCHYNO HierarchyNode Field INT4 10 Descend

tionItem DESUBTREESIZE SubTreeSize ant Count
SupplierQuota MANUALDELI ManualDeliver Field CHAR 10 Address

tionItem VERYADDRESSID yAddressID
SupplierQuota MATERIAL Material Field CHAR 40 Material

tionItem
SupplierQuota MATERI MaterialGroup Field CHAR 9 Material

tionItem ALGROUP Group
SupplierQuota NETAMOUNT NetAmount Field SrcgP CURR 13 2 Net Order

tionItem rojQt Value
nOf
fer
Cur
rency

Field/ Ref.
Asso Curr/
SupplierQuota NETPRICEA NetPriceA Field SrcgP CURR 11 2 Net Order

tionItem MOUNT mount rojQt Price
nOf
fer
Cur
rency
SupplierQuota NETPRICEQUAN NetPriceQuan Field DEC 5 Price Unit

tionItem TITY tity
SupplierQuota ORDERPRICEU OrderPriceUnit Field UNIT 3 Order Price

tionItem NIT Unit
SupplierQuota ORDERPRICEU OrderPriceUnit Field DEC 5 Quantity

tionItem NITTOORDERU ToOrderU Conversion
NITNMRTR nitNmrtr
SupplierQuota ORDPRICEUNIT OrdPriceUnit Field DEC 5 Quantity

tionItem TOORDERU ToOrderU Conversion
NITDNMNTR nitDnmntr
SupplierQuota PERFORMANCE Performance Field DATS 8 End of Per

tionItem PERIODENDDATE PeriodEndDate formance
Period
SupplierQuota PERFORMANCE Performance Field DATS 8 Start of

tionItem PERIODSTART PeriodStart Perform
DATE Date ance Period

tionItem
SupplierQuota PRODUCTTYPE ProductType Field CHAR 4 Product

tionItem Type
SupplierQuota PROPOSEDDELI ProposedDeli Field DATS 8 Proposed

tionItem VERYDATE veryDate Delivery
Date

tionItem SINGGROUP singGroup Group

tionItem GANIZATION ganization Organiza
tion

Field/ Ref.
Asso Curr/
SupplierQuota REFERENCEDELI ReferenceDeli Field CHAR 10 Address

tionItem VERYADDRESSID veryAddressID
SupplierQuota REQUESTEDDE RequestedDeli Field DATS 8 Requested

tionItem LIVERYDATE veryDate Delivery
Date
SupplierQuota REQUESTED Requested Field Re QUAN 13 3 Requested

tionItem QUANTITY Quantity ques Quantity
ted
Quan
tityU
nit
SupplierQuota REQUESTED Requested Field UNIT 3 Unit of Re

tionItem QUANTITYUNIT QuantityUnit quested
Quantity
SupplierQuota SOURCINGPRO SourcingPro Field NUMC 5 Item

tionItem JECTQUOTATIO jectQuotationI
NITEM tem
SupplierQuota SRCGPROJQTNI SrcgProjQtnI Field CHAR 1 Item Type

tionItem TEMCLASSIFICA temClassifica
TION tion
SupplierQuota SRCGPROJQTNI SrcgProjQtnI Field CHAR 40 Item De

tionItem TEMDESCRIP temDescription scription
TION
SupplierQuota SRCGPROJQTNI SrcgProjQtnIte Field CHAR 2 Item Offer-

tionItem TEMOFFERING mOfferingCode ing Code
CODE
SupplierQuota SRCGPROJQTNI SrcgProjQtnI Field SrcgP CURR 15 2 Total

tionItem TEMTOTNETAMT temTotNetAmt rojQt Amount
nOf
fer
Cur
rency

Field/ Ref.
Asso Curr/
SupplierQuota SRCGPROJQT SrcgProjQtnOf Field Re QUAN 13 3 Offered

tionItem NOFFERED feredQuantity ques Quantity
QUANTITY ted
Quan
tityU
nit
SupplierQuota SRCGPROJQUO SrcgProjQuota Field CHAR 1 Item Type

tionItem TATIONITEM tionItemType
TYPE
SupplierQuota SRCGPROJITEM SrcgProjItem Field CHAR 60 Name of

tionItem CLASSIFICA Classification Item Classi
TIONNAME Name fication

tionItem
SupplierQuota PRODUCTTYPE ProductType Field CHAR 40 Name of

tionItem NAME Name Product
Type
SupplierQuota MATERIAL MaterialGroup Field CHAR 20 Name of

tionItem GROUPNAME Name Material
Group
SupplierQuota MATERIAL MaterialGroup Field CHAR 60 Description

tionItem GROUPTEXT Text of Material
Group
SupplierQuota SRCGPROJQT SrcgProjQtnOf Field CUKY 5 Quotation

tionItem NOFFERCUR ferCurrency Currency
RENCY
SupplierQuota CURRENCYNAME CurrencyName Field CHAR 40 Description

tionItem
SupplierQuota CURRENCY CurrencyShort Field CHAR 15 Short Text

tionItem SHORTNAME Name

tionItem NAME Name Name

tionIncoterms Code

Field/ Ref.
Asso Curr/
SupplierQuota INCOTERM IncotermsClas Field CHAR 3 Incoterms

tionIncoterms SCLASSIFICA sification
TION
SupplierQuota INCOTERMSLO IncotermsLoca Field CHAR 70 Incoterms

tionIncoterms CATION1 tion1 Location 1
SupplierQuota INCOTERMSLO IncotermsLoca Field CHAR 70 Incoterms

tionIncoterms CATION2 tion2 Location 2
SupplierQuota INCOTERM Incoterm Field CHAR 28 Incoterms

tionIncoterms STRANSFERLO sTransferLoca (Part 2)
CATION tion
SupplierQuota INCOTERMSVER IncotermsVer Field CHAR 4 Incoterms

tionIncoterms SION sion Version

tionIncoterms

tionIncoterms

tionItemPay COUNT1DAYS count1Days
mentTerms

tionItemPay COUNT1PER count1Percent Percent 1
mentTerms CENT

tionItemPay COUNT2DAYS count2Days
mentTerms

tionItemPay COUNT2PER count2Percent Percent 2
mentTerms CENT

tionItemPay Code
mentTerms
SupplierQuota NETPAYMENT NetPayment Field DEC 3 Days Net

tionItemPay DAYS Days
mentTerms

Field/ Ref.
Asso Curr/
SupplierQuota PAYMENTTERMS PaymentTerms Field CHAR 4 Terms of

tionItemPay Payment
mentTerms

tionItemPay
mentTerms
SupplierQuota ADDITIONALVA AdditionalVa Field NUMC 2 Days

tionItemCondi LUEDAYS lueDays
tionAmount
SupplierQuota BASEUNIT BaseUnit Field UNIT 3 Base Unit

tionItemCondi of Measure
tionAmount
SupplierQuota CNDNMAXNUM CndnMaxNum Field NUMC 2 Max. Num

tionItemCondi BEROFSALESOR berOfSalesOr ber of Or
tionAmount DERS ders ders
SupplierQuota CONDITIONAL ConditionAlter Field CUKY 5 Condition

tionItemCondi TERNATIVECUR nativeCurrency Currency
tionAmount RENCY
SupplierQuota CONDITIONCAL ConditionCal Field CHAR 1 Calculation

tionItemCondi CULATIONTYPE culationType Type
tionAmount SHORT Short
SupplierQuota CONDITION ConditionChan Field CHAR 3 Reason for

tionItemCondi CHANGEREASON geReason Condition
tionAmount Change
SupplierQuota CONDITIONEX ConditionExclu Field CHAR 1 Exclusion

tionItemCondi CLUSION sion
tionAmount
SupplierQuota CONDITIONISDE ConditionIsDe Field CHAR 1 Deletion In

tionItemCondi LETED leted dicator
tionAmount

Field/ Ref.
Asso Curr/
SupplierQuota CONDITIONLO ConditionLo Field Condi CURR 11 2 Lower limit

tionItemCondi WERLIMIT werLimit tionAl
tionAmount terna
tive
Cur
rency
SupplierQuota CONDITION ConditionQuan Field Condi DEC 5 Pricing Unit

tionItemCondi QUANTITY tity tion
tionAmount Quan
tityU
nit
SupplierQuota CONDITION ConditionQuan Field UNIT 3 Unit of

tionItemCondi QUANTITYUNIT tityUnit Measure
tionAmount
SupplierQuota CONDITIONRA ConditionRate Field Condi CURR 11 2 Condition

tionItemCondi TEVALUE Value tion Amount
tionAmount Rate
Val
ueUnit
SupplierQuota CONDITIONRA ConditionRate Field CUKY 5 Condition

tionItemCondi TEVALUEUNIT ValueUnit Currency
tionAmount
SupplierQuota CONDITIONRE ConditionRe Field CHAR 10 Number of

tionItemCondi CORD cord Condition
tionAmount Record
SupplierQuota CONDITIONRE ConditionRelea Field CHAR 1 Release

tionItemCondi LEASESTATUS seStatus Status
tionAmount
SupplierQuota CONDITIONSCA ConditionSca Field Condi CURR 15 2 Scale Value

tionItemCondi LEAMOUNT leAmount tion
tionAmount Sca
leA
mount
Cur
rency

Field/ Ref.
Asso Curr/
SupplierQuota CONDITIONSCA ConditionSca Field CUKY 5 Scale Cur

tionItemCondi LEAMOUNTCUR leAmountCur rency
tionAmount RENCY rency
SupplierQuota CONDITIONSCA ConditionScale Field Condi QUAN 15 3 Scale

tionItemCondi LEQUANTITY Quantity tion Quantity
tionAmount Scale
Quan
tityU
nit
SupplierQuota CONDITIONSCA ConditionScale Field UNIT 3 Scale Unit

tionItemCondi LEQUANTITYU QuantityUnit
tionAmount NIT
SupplierQuota CONDITIONSE ConditionSe Field NUMC 2 Sequential

tionItemCondi QUENTIALNUM quentialNum Number of
tionAmount BERSHORT berShort Condition
SupplierQuota CONDITIONTEX ConditionTextID Field CHAR 10 Text num

tionItemCondi TID ber
tionAmount
SupplierQuota CONDITIONTO ConditionToBa Field DEC 5 Denomina

tionItemCondi BASE seQtyDnmntr tor for Con
tionAmount QTYDNMNTR version
SupplierQuota CONDITIONTO ConditionToBa Field DEC 5 Numerator

tionItemCondi BASEQTYNMRTR seQtyNmrtr for Conver
tionAmount sion
SupplierQuota CONDITIONTYPE ConditionType Field CHAR 4 Condition

tionItemCondi Type
tionAmount
SupplierQuota CONDITIONUP ConditionUp Field Condi CURR 11 2 Upper limit

tionItemCondi PERLIMIT perLimit tionAl
tionAmount terna
tive
Cur
rency
SupplierQuota CONDITIONVALI ConditionValidi Field DATS 8 Valid To

tionItemCondi DITYENDDATE tyEndDate
tionAmount

Field/ Ref.
Asso Curr/
SupplierQuota CONDITIONVALI ConditionValidi Field DATS 8 Valid From

tionItemCondi DITYSTARTDATE tyStartDate
tionAmount
SupplierQuota FIXEDVALUE FixedValueDate Field DATS 8 Fixed Value

tionItemCondi DATE Date
tionAmount
SupplierQuota MAXIMUMCON MaximumCon Field Condi CURR 13 2 Max. Con

tionItemCondi DITIONAMOUNT ditionAmount tionAl dition Value
tionAmount terna
tive
Cur
rency
SupplierQuota MAXIMUMCON MaximumCon Field Condi QUAN 15 3 Max. Con

tionItemCondi DITIONBASIS ditionBasis tion dition Base
tionAmount VALUE Value Quan Value
tityU
nit
SupplierQuota MINIMUMCONDI MinimumCon Field Condi QUAN 15 3 Min. Condi

tionItemCondi TIONBASIS ditionBasis tion tion Value
tionAmount VALUE Value Quan
tityU
nit
SupplierQuota PAYMENTTERMS PaymentTerms Field CHAR 4 Payment

tionItemCondi Terms
tionAmount
SupplierQuota PRICINGSCALE PricingScaleBa Field CHAR 1 Scale Base

tionItemCondi BASISSHORT sisShort Type
tionAmount
SupplierQuota PRICINGSCALE PricingScale Field NUMC 4 Pricing

tionItemCondi LINE Line scale
tionAmount
SupplierQuota PRICINGSCALE PricingScale Field CHAR 1 Scale Type

tionItemCondi TYPE Type
tionAmount

Field/ Ref.
Asso Curr/
SupplierQuota CONDITIONRE ConditionRe Field CHAR 10 Number of

tionItemCondi CORD cord Condition
tionValidity Record
SupplierQuota CONDITIONVALI ConditionValidi Field DATS 8 Valid To

tionItemCondi DITYENDDATE tyEndDate
tionValidity
SupplierQuota CONDITIONVALI ConditionValidi Field DATS 8 Valid From

tionItemCondi DITYSTARTDATE tyStartDate
tionValidity

tionItemShip Code
pingInstruc
tions

tionItemShip
pingInstruc
tions
SupplierQuota SHIPPINGIN ShippingIn Field CHAR 2 Shipping

tionItemShip STRUCTION struction Instruction
pingInstruc
tions

tionItemShip
pingInstruc
tions
SupplierQuota SHIPPINGIN ShippingIn Field CHAR 30 Name of

tionItemShip STRUCTION structionName Shipping
pingInstruc NAME Instruction
tions

tionItemShip NAME Name Name
pingInstruc
tions
SupplierQuota BIDDER Bidder Field CHAR 10 Business

tionSupplier Partner
Contacts

Field/ Ref.
Asso Curr/
SupplierQuota BUSINESSPART BusinessPart Field CHAR 10 Business

tionSupplier NER ner Partner
Contacts
SupplierQuota SRCGPROJQTN SrcgProjQtn Field CHAR 4 Contact

tionSupplier SUPPLIERCON SupplierCon Category
Contacts TACTCAT tactCat
6.2 Configure Communication from Hub system to Connected

System
6.2.1 Create RFC
Use
In this activity, you create the RFC for the Connected System.
Procedure
1. Log on to the S/4HANA Hub system and execute transaction SM59.

2. Choose Create.
3. On the RFC Destination screen, enter the following entries
○ RFC Destination: <Enter the RFC Destination name for Connected System, for example,
XXXCLNTYYY (XXX: System ID, YYY: Client)>
○ Connection Type:H
○ Description 1: <Enter the RFC Description>
On the Technical Settings tab, enter the following entries:
○ Host: <Host of the Connected System>
○ Port: <Port>
○ Path Prefix: /sap/opu/odata/sap/?sap-client=<client of connected system>

On the Logon & Security tab, enter the following entries:
○ Basic authentication: X
○ Language: <Your Language>
○ Client: <Client of Connected System>
○ User: <User>
○ Password: <Password>
In the Security Options area, enter the following entries:
○ SSL: Active
○ SSL Certificate: <Select the SSL Certificate>
4. Choose Save.
6.2.2 Create Logical System
Use
In this activity, you create the logical system for the Connected System.
Procedure
1. Log on to the S/4HANA Hub system and execute transaction BD54.

2. Confirm the Information dialog box, and then choose New Entries.
3. On the New Entries: Overview of Added Entries screen, enter the following entries:
○ Log.System: <Enter the Logical System name for Connected System, for example,
XXXCLNTYYY (XXX: System ID, YYY: Client)>
○ Name: <Enter the Logical System Name>
4. Choose Save.
6.2.3 Assign RFC Destinations for Synchronous Method Calls
Use
In this activity, you assign the RFC destination for BAPI calls.

Procedure
1. Log on to the S/4HANA Hub system and execute transaction BD97.

2. Select the Logical System you created in the previous step, and then choose Standard BAPI destination.
3. In the Assign RFC Destinations for Synchronous Method Call dialog box, enter the following entries:
○ RFC destination for BAPI calls: <Enter the RFC you created in the previous step>
4. Choose Continue and Save.
6.2.4 Activate AIF Content
Use
In this activity, you activate the AIF content which is required for central purchase contracts in the hub systems.
Procedure
1. Log on to the S/4HANA Hub system and execute transaction /AIF/SETUP without Test Mode enabled. You can
now use the AIF content in your SAP S/4HANA system.
2. Execute transaction /AIF/CONTENT_EXTRACT and enter SAP_COM_0243 as the deployment scenario. The AIF
content for the inbound and outbound messages is extracted.
6.2.5 Integration Options and SOA Services
In On-Premise, the communication from the S/4HANA Hub system to the connected system can be P2P or via PI
and vice versa.
In both cases, the following services/namespaces needs to be configured:
● Namespace in S/4HANA On-Premise HUB system: http://sap.com/xi/APPL/sProc

● Namespace in Connected System: http://sap.com/xi/HubERPI
SAP S/4HANA Hub System:
● PurchaseContractDistributionReplicationRequest_Out
● PurchaseContractDistributionConfirmationRequest_In
● SourceListChangeRequest_Out
● SourceListChangeRequestConfirmation_In

Connected System:
● PurchaseContractDistributionReplicationRequest_In
● PurchaseContractDistributionConfirmationRequest_Out
● SourceListChangeRequest_In
● SourceListChangeRequestConfirmation_Out
For detail web service configuration steps, please refer to Configuring Web Services in SOA Manager.
6.3 Maintain Switch Framework
Use
You need to turn on necessary switch and business function to take advantage of full usage of sourcing project,
supplier list funcationalities.
Procedure
1. Login into the S/4HANA Hub system and execute transaction SFW5.
2. Turn on the switch: MM_PUR_EXT_PR_CL_ONP_SWITCH
3. Turn on the business function: MM_PUR_EXT_PR_CL_ONP_SWTCH_FUN
For more details, please refer to the introduction and steps in Switch Framework
6.4 S/4HANA Hub System Configuration Steps
6.4.1 Activate SAP S/4HANA Procurement Hub and Scenarios
Use
In this activity, you enable SAP S/4HANA as a procurement hub system and activate hub scenarios.

Procedure
1. Login into the S/4HANA Hub system and execute transaction SPRO.
2. Navigate to configuration activity: SAP Reference IMG > Materials Management > Purchasing > Central
Procurement > Settings in Hub System > Active SAP S/4HANA Procurement Hub and Scenarios
3. On the Change View “Hub Activation”: Overview screen, choose New Entries and then enter the following
entries:
○ Activate HUB: Selected
4. Choose Save.
5. In the dialog box which shows Setting once saved cannot be changed, Do you want to
continue?, choose Save if you need to active SAP S/4HANA Procurement Hub in the system.
6. In Dialog structure area, choose Scenario Activation.
7. In the Change View “Scenario Activation”: Overview screen, choose New Entries and then enter the following
entries:
○ Activate Scenarios for Procurement Hub: Central Contract Management
○ Activation status: Selected
8. Choose Save.
9. In the Change View “Scenario Activation”: Overview screen, choose New Entries and then enter the following
entries:
○ Activate Scenarios for Procurement Hub: Direct Material Sourcing
○ Activation status: Selected
10. Choose Save.
6.4.2 Define Connected System
Use
In this activity, you configure the connected system in S/4HANA Hub system.
Procedure
Procurement > Settings in Hub System > Define Company Code, Plant, Purchasing Organization for Connected
System
3. On the Change View “Connected Systems”: Overview screen, choose New Entries and then enter the following
entries:
○ Connected System ID: <Your Connected System ID>

○ Connected Sys Name: <Your Connected System Name>
○ Logical System: The Logical system defined in the step Create Logical System [page 67].
4. Choose Save.
6.4.3 Assign Connected Systems to RFC Destinations
Use
In this activity, you can assign connected systems to RFC destinations.
Procedure
1. Log on to the S/4HANA Hub system and execute transaction SPRO.

2. Navigate to configuration activity: SAP Reference IMG Materials Management Purchasing Central
Procurement - Settings in Hub System Assign Connected Systems to RFC Destinations .
3. On the Change View “Hub System Connection for OP”: Overview screen, choose New Entries and then make the
following entries:
○ ConnSysID: The connected system ID defined in the step Define Connected System [page 70].
○ RFC Destination: The RFC destination defined in the step Create RFC [page 66]
4. Choose Save.
6.4.4 Configure Control Plane for the APIs of Central

Procurement
Use
In this activity, you can configure the control plane for the APIs of direct material sourcing to perform several
business operations.

Procedure

Procurement Settings in Hub System Configure Control Plane for the APIs of Central Procurement
3. On the Change View Change View “API Control Plane for Bounded Context”: Overview screen, choose New
Entries and then make the following entries:
The connected system ID is defined in the step .
Connected Bounded Message Activate

System ID Context Operation Protocol API Name API Version API Driver Driver
connected DMS 6CP Direct ODATA MMPUR_PO_ 1 CL_MMPUR_ check

system ID Materials CREATE_SRV DI
Sourcing Cre RECT_MAT_S
ate PO RC_DRIVER
connected DMS 6RA Direct ODATA MMPUR_CCT 1 CL_MMPUR_ check

system ID Materials R_BE_SRV DI
Sourcing RECT_MAT_S
Read Delivery RC_DRIVER
Address
connected DMS 6RD Direct ODATA MMPUR_BE_ 1 CL_MMPUR_ check

system ID Materials VALUE_HELP DI
Sourcing _SRV RECT_MAT_S
Read Docu RC_DRIVER
ment Type
connected DMS 6RM Direct ODATA MMPUR_BE_ 1 CL_MMPUR_ check

Read Material RC_DRIVER
connected DMS 6RS Direct ODATA MMPUR_CCT 1 CL_MMPUR_ check

system ID Materials R_BE_SRV DI
Sourcing RECT_MAT_S
Read Storage RC_DRIVER
Location Data
connected DMS 6RP Direct ODATA MMPUR_BE_ 1 CL_MMPUR_ check

Read Pur RC_DRIVER
chasing
Group

Connected Bounded Message Activate
System ID Context Operation Protocol API Name API Version API Driver Driver
connected CCM 2AH Archive ODATA MM_PUR_CC 1 CL_MMPUR_ check

system ID Local Con TR_AR CENTRL_CT
tracts CHIVE_SRV R_DRIVER
connected CCM 2CD Central ODATA MM_PUR_CC 1 CL_MMPUR_ check

system ID Contract TR_CHECK_S CENTRL_CT
Check Distri RV R_DRIVER
bution
connected CCM 2DI Central SOAP PURCHASE 1 CL_MMPUR_ check

system ID Contract Dis CONTRAC CENTRL_CT
tribute TDISTRIBU R_DRIVER
TIONREPL
ICA-TIONRE
QUEST_IN
connected CCM 2OM Central ODATA MM_PUR_CP 1 CL_MMPUR_ check

system ID Procurement ROC_OPS_M CENTRL_CT
Operations NTR_CCTR_ R_DRIVER
Monitor for BE_SRV
CCM
connected CCM 2RD Central ODATA MM_PUR_CC 1 CL_MMPUR_ check

system ID Contract TR_CAL CENTRL_CT
Read Release LOFF_SRV R_DRIVER
Info
connected CCM 2RM Central ODATA MMPUR_BE_ 1 CL_MMPUR_ check

system ID Contract VALUE_HELP CENTRL_CT
Read Material _SRV R_DRIVER
connected CCM 2RR Central ODATA MMPUR_CCT 1 CL_MMPUR_ check

system ID Contract R_BE_SRV CENTRL_CT
Read Related R_DRIVER
Information
connected CCM 2SL Source SOAP SOURCE 1 CL_MMPUR_ check

system ID List Update LISTCHAN CENTRL_CT
GERE R_DRIVER
QUEST_IN
4. Choose Save.

6.4.5 Define Company Code, Plant, Purchasing Organization for
Connected System
Use
In this activity, you specify a unique combination of the Connected Company Code, Connected Plant, Connected
Purchasing Organization and Logical System.
Procedure

System
3. On the change view "Connected Company Codes": Overview screen, choose New Entries and then make the
following entries:
○ Conn. Company Code: Your Company Code in connected system
○ Company Code ID: Your Company Code Unique ID
○ Company Name: Your Company Name
○ Register: Selected
The Company Code ID is a unique ID that represents the combination of Connected Company Code and
Connected System.
4. Choose Save.
5. Choose the Connected Company Code you created and double click Connected Plants in Dialog Structure.
6. On the change view "Connected Plants": Overview screen, choose New Entries and then make the following
entries:
○ Connected Plant: Your Plant in connected system
○ Plant Name: Your Plant Name
○ Plant Unique ID: Your Plant Unique ID
The Plant Unique ID is a unique ID that represents the combination of Connected Plant and Connected
System.
7. Choose Save.
8. Choose the Connected System you created and double click Connected Purchasing Organization in Dialog
Structure.
9. On the change view "Connected Purchasing Organization": Overview screen, choose New Entries and then make
the following entries:
○ Connected Purch Org: Your Purchasing Organization in connected system
○ Conn. Purch Org ID: Your Purchasing Organization Unique ID
○ Conn. Purch Org Name: Your Purchasing Organization Name

The Purch Org ID is a unique ID that represents the combination of Connected Purchasing Organization
and Connected System.
10. Choose Save.
6.4.6 Define Local Connected System
Use
In this activity, you define the same S/4HANA Hub system as connected system for local scenario.
Procedure

System
3. On the Change View “Connected Systems”: Overview screen, choose New Entries and then make the following
entries:
○ Connected System ID: <S/4HANA Hub System ID> for example: LOCAL
○ Connected Sys Name: <S/4HANA Hub System Name>
○ Logical System: Logical System for S/4HANA Hub system
4. Choose Save.
5. On the change view "Connected Company Codes": Overview screen, choose New Entries and then make the
following entries:
○ Conn. Company Code: Your Local Company Code
○ Company Code ID: Your Company Code Unique ID
○ Company Name: Your Local Company Name
The Company Code ID is a unique ID that represents the combination of Connected Company Code and
Connected System.
○ Choose the Connected Company Code you created and double click Connected Plants in Dialog Structure.
6. Choose Save.
7. Choose the Connected Company Code you created and double click Connected Plants in Dialog Structure.
8. On the change view "Connected Plants": Overview screen, choose New Entries and then make the following
entries:
○ Connected Plant: Your Local Plant
○ Plant Name: Your Local Plant Name
○ Plant Unique ID: Your Plant Unique ID

The Plant Unique ID is a unique ID that represents the combination of Connected Plant and Connected
System.
9. Choose Save.
10. Choose the Connected System you created and double click Connected Purchasing Organization in Dialog
Structure.
11. On the change view "Connected Purchasing Organization": Overview screen, choose New Entries and then make
○ Connected Purch Org: Your Local Purchasing Organization
○ Conn. Purch Org ID: Your Purchasing Organization Unique ID
○ Conn. Purch Org Name: Your Local Purchasing Organization Name
The Purch Org ID is a unique ID that represents the combination of Connected Purchasing Organization
and Connected System.
12. Choose Save.
6.4.7 Define Material Groups from Respective Connected

System into the Hub system
Use
In this activity, you harmonize the Material Group which exists in the Connected System to the Hub system.
Procedure
2. Navigate to configuration activity: SAP Reference IMG >Logistics-General Material Master >Settings for Key
Fields > Define Material Groups
3. On the Change View “Material Groups”: Overview screen, choose New Entries and then enter the following
entries:
Material Group: Your material group in the connected system
Material Group Description: Your Material Group Description
4. Choose Save.

6.4.8 Define Grouping of Company Codes of Connected
Systems
Use
In this activity, you define grouping of the company codes of different connected systems. In a central purchase
contract hierarchy, this grouping is used to determine the central purchase contacts that should be created for the
maintained distributions.
Procedure

Procurement- Settings in Hub System Define Grouping of Company Codes of Connected Systems
3. On the change view "Define group name": Overview screen, choose New Entries and then make the following
entries:
○ Group ID: Your Group ID, for example: DG
○ Group ID Name: Your Group Name, for example: Demo Group
4. Choose Save.
5. Choose the Group ID you created and double click Assign company code to group in Dialog Structure.
6. On the change view "Assign company code to group": Overview screen, choose New Entries and then make the
following entries:
○ ConnCoCode: Your Company Code in connected system
○ ConnSysID: Your Connected System ID
○ Activate: check
7. You can add required connected company codes to the group.
8. Choose Save.
6.4.9 Configure Version Management in Central Purchase

Contracts
When you configure version management, you can define the settings to generate and manage versions of a
purchasing document, such as central purchase contracts. You can also define reasons for changes that result in
the creation of newer versions of the purchasing document.
Please note that the settings you make for these configuration steps work only for FIORI app.

6.4.9.1 Define Reasons for Version-Relevant Changes for
Purchasing Documents
Use
In this activity, you define reasons for changes that result in the creation of versions of a purchasing document (for
example, legal changes or documentation issues).
Procedure
1. 1. Login into the S/4HANA Hub system and execute transaction SPRO.
2. Navigate to configuration activity: SAP Reference IMG Materials Management Purchasing Version
Management Configure Versioning and Reason for Change for Fiori Applications Define Reasons for Version-
Relevant Changes for Purchasing Documents application.
3. On the Change View “Versioning Maintenance View for Reason Codes” Overview screen, choose New Entries
and then make the following entries:
○ Reason: Your Reason, for example: 01
○ Reason Description: Your Reason Description, for example: documentation issues
4. Choose Save.
6.4.9.2 Set Up Version Management for Purchasing

Documents
Use
In this activity, you configure the settings to manage the versioning of a purchasing document.
For a combination of purchasing document category, purchasing document type and purchasing organization, you
can:
1. Activate version management

If version management is active, changes to a purchasing document are managed in versions.
2. Set up field selection for versions
You can specify the fields, which when changed, result in the creation of newer versions.

Procedure
2. Navigate to configuration activity: SAP Reference IMG Materials Management Purchasing Version
Management Configure Versioning and Reason for Change for Fiori Applications Set Up Version-Relevant
Changes for Purchasing Documents
3. On the Change View "Purchasing Documents Details" Overview screen, choose New Entries and then make the
following entries:
○ Category: Central Contract
○ Doc Type: Central Contract Document Type, for example: WK
○ Purc. Org.: Your Purchasing Organization in Central Procuremnt Hub sysrtem
○ Activate: check
○ Reason: You can set Optional or Required
○ Pur. Note: You can set Optional or Required
4. Choose Save.
5. Choose the Purchasing Documents Details you created and double click Purchasing Document Field Details in
Dialog Structure.
6. On the change view "Purchasing Document Field Details": Overview screen, choose New Entries and then make
○ Version-Relevant Facet: You can choose Header, Item , Distribution, Condition Header
or Condition Item. For example: Header
○ Version-Relevant Field: Field for Header, Item , Distribution, Condition Header or
Condition Item. For example: KTWRT (Target Value)
7. Choose Save.
6.4.10 Commodity Pricing Configuration
With Commodity Pricing you can apply complex pricing formulas, rules and conditions in an easy way. Direct
material sourcing On-Premise support this function.
For using Commodity Procurement, you must have activated the following business function:
● LOG_CPE_SD_MM
● LOG_CMM_PRC_SFWS_SRCG_CPE
● LOG_CMM_PRC_BF_CCTR_EXT
● LOG_CMM_PRC_BF_MIGRATION
For more information, please refer the document: Product Assistance Enterprise Business Applications
Cross-Line-of-Business Commodity Management Commodity Procurement at the SAP Help Portal.

Prerequisites
Please use follow and finish all steps in Setting Up Central Purchase Contracts (2ME)- Configure Commodity
Pricing for Central Purchase Contracts before you execute the commodity pricing configuration steps specifically in
4RD.
6.4.10.1 Pricing Configuration
6.4.10.1.1 Define Condition Type for Commodity Price
Use
In this activity, you define condition type for commodity pricing.
Procedure

2. Navigate to configuration activity: SAP Reference IMG Materials Management Purchasing Conditions
Define Price Determination Processes Define Condition Types Set Pricing Condition Types - Purchasing
3. On the Change View “Conditions: Condition Types” Overview screen, choose New Entries and then make the
following entries:
○ Condition Type: ZCMM Commodity Price
○ Access Sequence: 0001 Metal Prices
○ Control. Data 1
○ Condition Class: A Discount or surcharge
○ Calculation Type: Q Commodity Price
4. Choose Save.
6.4.10.1.2 Define Base Condition Type
Use
In this activity, you define base condition type for central purchase contract.

Procedure
3. On the Change View “Conditions: Condition Types” Overview screen, select condition type PPR0 and choose
Copy As…
4. On the Change View “Conditions: Condition Types” Details of Selected Set screen, choose New Entries and then
make the following entries:
○ Condition Type: ZPR0 Default Gross Price
5. Choose Copy.
6. Choose Save.
6.4.10.1.3 Define Pricing Procedure for Commodity Pricing
Use
In this activity, you define pricing procedure for commodity pricing.
Procedure

Define Price Determination Processes Set Calculation Schema - Purchasing
3. On the Change View "Schemas" Overview screen, select condition type A10001 and choose Copy As…
4. On the Change View "Schemas": Details of Selected Set screen, and make the following entries:
○ Procedure: Z10001
5. Choose Copy.
6. On the Specify object to be copied popup screen, choose copy all.
7. Choose Continue.
8. On the Change View "Schemas": Overview screen, select procedure Z10001 and double click Control data in
Dialog Structure.
9. On the Change View "Control data": Overview screen, change first line condition type from PPR0 to ZPR0.
10. Choose New Entries and make the following entries:
○ Step: 30
○ Condition Type: ZCMM
○ Print Type: a

○ Subtotal: 9
11. Choose Save.
12. Choose Back.
13. On the Change View “Schemas” Overview screen, select condition type AXX001 and choose Copy As…
14. On the Change View “Schemas": Details of Selected Set screen, and make the following entries:
○ Procedure: ZXX001
15. Choose Copy.
16. On the Specify object to be copied popup screen, choose copy all.
17. Choose Continue.
18. On the Change View "Schemas": Overview screen, select procedure ZXX001 and double click Control data in
Dialog Structure.
19. On the Change View "Control data": Overview screen, change first line condition type from PPR0 to ZPR0.
20.Choose New Entries and make the following entries:
○ Step: 30
○ Print Type: a
○ Subtotal: 9
21. Choose Save.
6.4.10.1.4 Assign Pricing Procedure for Condition Supplements
Use
In this activity, you assign pricing procedure to base condition type for condition supplements.
Procedure

3. On the Change View “Conditions: Condition Types” Overview screen, select condition type ZPR0 and choose
Details.
4. On the Change View “Conditions: Condition Types” Details of Selected Set screen, go to Master Data section
○ Pricing Procedure: ZXX001
5. Choose Save.

6.4.10.1.5 Define Schema Group for Suppliers
Use
In this activity, you define schema group for suppler.
Procedure

Define Price Determination Processes Define Schema Group Define Schema Group for Suppliers
3. On the Change View “Schema Group for Suppliers” Overview screen, choose New Entries and make the
following entries:
○ Sch.Grp Supp: ZC
○ Description: Schema Group for Commodity
4. Choose Save.
6.4.10.1.6 Determine Calculation Schema for Commodity

Pricing in Purchasing
Use
In this activity, you define determination of calculation schema for commodity pricing in purchasing.
Procedure

Define Price Determination Processes Define Schema Determination Determine Calculation Schema for
Standard Purchase Orders

3. On the Change View “Determination of Calculation Schema in Purchasing” Overview screen, choose New Entries
○ Schema GrpPOrg: 1010
○ Sch.Grp Supp: ZC
○ Proc.: Z10001
4. Choose Save.
6.4.10.2 Maintain Field Catalog
Use
In this activity, you maintain condition tables for the application M (Purchasing) and usage FA (Formula Assembly).
In these tables, you define master data to determine commodity pricing formulas or its parts in purchasing
documents.
Procedure

2. Navigate to configuration activity: SAP Reference IMG Materials Management Purchasing Commodity
Pricing Settings for Formula Assembly Maintain Field Catalog
3. On the Change View "CPE FA Fieldattributes": Overview screen, choose New Entries and make the following
entries:
Formula Assembly Fieldname Data element
COMPANY_CODE EKORG
EXTERNAL_MATERIAL MM_PUR_HUB_MATNR
MAT_GROUP MATKL
PLANT WERKS_D
PURCH_ORG EKORG
VENDOR ELIFN
VENDOR_GROUP KALSK
4. Choose Save.

6.4.10.3 Maintain Field Mapping
Use
In this activity, you can make fields from e.g. the structures KOMK and KOMP available in the Formula Assembly.
Procedure

Pricing Settings for Formula Assembly Maintain Field Mapping
3. On the Determine Work Area: Entry popup screen, input M (Purchasing) and choose Continue.
4. On the Change View "CPE FA Fieldmapping": Overview screen, choose New Entries and make the following
entries:
Structure Name Component Name Formula Assembly Fieldname
KOMK BUKRS COMPANY_CODE
KOMK EKORG PURCH_ORG
KOMK LIFNR VENDOR
KOMP MATKL MAT_GROUP
KOMP PMATN EXTERNAL_MATERIAL
KOMP WERKS PLANT
LFM1 KALSK VENDOR_GROUP
5. Choose Save.

6.4.10.4 Assign BRFplus Application to Pricing Procedure
Use
In this activity, you configure a selected application for using the Formula Assembly within the Commodity Pricing
Engine.
Procedure

Pricing Settings for Formula Assembly Assign BRFplus Application to Pricing Procudure
3. On the Determine Work Area: Entry popup screen, input M (Purchasing) and choose Continue.
4. On the Change View "Assign BRF+ Application to Pricing Procedure": Overview screen, choose New Entries and
make the following entries:
○ Proc.: Z10001
○ BRFplus Application Name: CPE_MD_FORMULA_ASSEMBLY
 Note
If you cannot find BRFplus application CPE_MD_FORMULA_ASSEMBLY in the system, please follow the
manual instruction mentioned in 2937677 - BRF Application CPE_MD_FORMULA_ASSEMBLY for Time
Dependent Conditions to import the required BRFplus application into your system.
5. Choose the entry you created and double click Assign BRF + Functions in Dialog Structure.
6. On the Change View "Assign BRF+ Functions": Overview screen, choose New Entries and then make the
following entries:
○ BRFplus Function：
APPL_M_FORM_CCTR_MD_FUNCTION
APPL_M_TERM_CCTR_MD_FUNCTION
7. Choose Save.

6.4.10.5 Define CPE Term
Use
In this activity, you define terms for the commodity pricing engine (CPE). A commodity pricing formula has to
include at least one term. The value of all terms included in a formula is combined to give the formula value.
Procedure
Pricing MM-Specific CPE Objects Define CPE Term
3. On the Change View "CPE Term": Overview screen, choose New Entries and then make the following entries:
○ Term Key: your term key, for example: ZTERM_AG
○ Valid From: today
○ Description: your term description, for example: Term for Silver
○ Calculation Type: 20 Fixed Term Rate
4. Click Enter.
5. Make the following entries:
○ Fixed Rate: your fixed rate, for example: 1
○ Currency Fixed Rate: your formula currency, for example: EUR
○ PrcUnit Fixed Value: your price unit fixed value, for example: 1
○ UoM for Fixed Value: your commodity UoM, for example: KG
6. Choose Save.
6.4.10.6 Define CPE Formula
Use
In this activity, you define CPE formula for central purchase contract. A commodity pricing formula is used to price
commodities that are contained in a product and that can be linked to condition types used in documents for the
pricing of this product.

Procedure
Pricing MM-Specific CPE Objects Define CPE Formula .
3. On the Change View "CPE Formula": Overview screen, choose New Entries and then make the following entries:
Formula Key: your formula key, for example: ZFORM_AG
Condition Type: ZCMM
Valid From: today
Description: your formula description, for example: Formula for Silver
Commodity UoM: your commodity UoM, for example: KG
Formula Currency: your formula currency, for example: EUR
Form.Eval.Rtine: 1 SAP CPE Formula Evaluation
Combination Routine: 3 Average of Terms
Qty Conversion Rule: 80 Sourcing Project commodity Quantity
4. Choose Save.
5. Choose the CPE formula you created and double click Terms of Formula in Dialog Structure.
6. On the Change View "Terms of Formula": Overview screen, choose New Entries and make the following entries:
TermNo. In Formula: 1
Term Key: ZTERM_AG
7. Choose Save.
6.4.10.7 Specify Commodities
Use
In this activity , you specify commodities. Commodities represent traded goods with a specific quality.
Procedure
Procurement Settings in Hub System Specify Commodities
3. On the Change View "Commodities": Overview screen, choose New Entries and make the following entries:
Commodity: your commodity, for example: AG
Commodity Name: your commodity name, for example: Silver
UoM: your unit of measure, for example: KG
4. Choose Save.

6.4.10.8 Map Condition Types to Commodities
Use
In this activity , you map a CPE condition type to exactly one commodity (1:1 relationship).
Procedure
Procurement - Settings in Hub System Map Condition Types to Commodities .
3. On the Change View "Map Condition Types to Commodities": Overview screen, choose New Entries and make
Condition Type (CTyp): ZCMM
Commodity: AG
4. Choose Save.
6.4.10.9 Specify Quantity Conversion Source for Document

Category
Use
In this activity , you would specify quantity conversion source for document category.
Procedure
Pricing Engine Application-Specific CPE Settings Choose Quantity Conversion Sources .
3. On the Change View "CPE: Quantity Conversion Sources Used per Document Categ": Overview screen, choose
New Entries and make the following entries:
Application: ERP Material Management
Document Category: Sourcing Project Quotation

Src: 08
Description : Integration into Sourcing Project
4. Choose Save.
6.4.11 Configure Header Condition for Central Purchase

Contracts
6.4.11.1 Define Condition Type for Header Condition
Use
In this activity, you define condition type for header condition.
Procedure
3. On the Change View “Conditions: Condition Types” Overview screen, choose New Entries and then make the
following entries:
○ Condition Type: ZRA1 Discount % on Gross
○ Access Sequence: KB01 Header discounts
○ Condition Class: A Discount or surcharge
○ Calculation Type: A Percentage
○ Scale Base Type: C Quantity scale
○ Scale Type: A Base scale
4. Choose Save.
6.4.11.2 Define Pricing Procedure for Header Condition
Use
In this activity, you define pricing procedure for header condition.

Procedure
Define Price Determination Processes Set Calculation Schema - Purchasing
3. On the Change View "Schemas": Overview screen, select procedure Z10001 and double click Control data in
Dialog Structure.
4. On the Change View "Control data": Overview screen, choose New Entries and then make the following entries:
○ Step: 990
○ Condition Type: ZRA1
5. Choose Save.
6.4.12 Maintain Condition Type Mapping for Purchasing

Documents
Use
In this activity, you enable the mapping of conditions for central purchase contracts in the SAP S/4HANA hub
system with the conditions for central purchase contracts in the connected systems.
Procedure
Procurement- Settings in Hub System Maintain Condition Type Mapping for Purchasing Documents
3. On the Change View "Maintain Condition Type Mapping for Purchasing Documents": Overview screen, choose
New Entries and then enter the following entries:
○ Sys ID: <Your Connected System ID defined in the previous step>
○ Con. Typ. in HUB Sys.: <Your Condition Type in S/4HANA Hub System>
○ Con. Type in Backend: <Your Condition Type in Connected System>
4. Choose Save.

6.5 UI Integration
UI integration enables the central purchaser to navigate from S/4HANA Hub system to connected system and
perform actions like editing purchase requisition and purchase order and so on.
To enable UI Integration, user in connected system should have enough authorization for transaction
MMPURPAMEREQ and MMPURPAMEPO.
To enable Single Sign-On Between S/4HANA Hub system and connected system for UI navigation, you can refer to
User Authentication and Single Sign-On -> Integration in Single Sign-On (SSO) Environments -> Single Sign-On for
Interaction Between Systems.
The steps in this chapter can be done by executing task list SAP_GATEWAY_ADD_SYSTEM in the S/4HANA Fiori
frontend system.
For more details, please refer to Configuration Using Task Lists
6.5.1 Configure Destination for Connected System on Frontend

System
To connect an SAP System (Connected System) to an SAP Gateway System (Frontend), you need to carry out the
following steps in this chapter:
● Create ABAP / HTTP(S) Connections for SAP System (SM59)

● Create Aliases for SAP System
HTTP Connection and HTTPS Connection can be configured based on your security policy.
6.5.1.1 Create RFC Destination of Type ABAP Connection
Use
In this activity, you create the RFC destination of type ABAP connection for the Connected System.
Procedure
1. Log on to the S/4HANA Fiori frontend system and execute transaction SM59.
2. Choose Create.

3. On the RFC Destination screen, make the following entries:
○ RFC Destination: <Connected System>_RFC, for example, XXXCLNTYYY_RFC (XXX: System ID,
YYY: Client)
○ Connection Type: 3
On the Technical Settings tab, make the following entries:
○ Target Host: <Host of the Connected System>
○ Instance No.: <Instance number of Connected System>
On the Logon & Security tab, make the following entries:
○ Current User: checked
4. Choose Save.
6.5.1.2 Create RFC Destination of Type HTTP Connection to

ABAP System for HTTPS Connection
Use
In this activity, you create the RFC destination of type HTTP connection to ABAP system for HTTPS connection for
the Connected System based on your security policy. If HTTP connection is used, you can skip this step.
Procedure
2. Choose Create.
○ RFC Destination: <Connected System>_HTTPS, for example, XXXCLNTYYY_HTTPS (XXX: System ID,
YYY: Client)
○ Connection Type: H
○ Host: <HTTPS Host of Connected System>
○ Port: <HTTPS Port of Connected System>
○ Trust Relationship: X

On the Security Options tab, make the following entries:
○ SSL: Active
○ SSL Certificate: DEFAULT SSL Client (Standard)
4. Choose Save.
6.5.1.3 Create RFC Destination of Type HTTP Connection to

ABAP System for HTTP Connection
Use
In this activity, you create the RFC destination of type HTTP connection to ABAP system for HTTP connection for
the Connected System based on your security policy. If HTTP connection is used, you can skip this step.
Procedure
2. Choose Create.
○ RFC Destination: <Connected System>_HTTP, for example, XXXCLNTYYY_HTTP (XXX: System ID,
YYY: Client)
○ Connection Type: H
○ Host: <HTTP Host of Connected System>
○ Port: <HTTP Port of Connected System>
○ Trust Relationship: X
On the Security Options tab, make the following entries:
○ SSL: Active
4. Choose Save.

6.5.1.4 Create SAP Gateway System Alias
Use
In this activity, you create the system alias mapping UI navigation.
Procedure
2. In the Table/View field, enter the view /IWFND/V_DFSYAL and choose Maintain.
3. On the Change View “Manage SAP System Aliases”: Overview screen, choose New Entries and make the
following entries.
○ SAP System Alias: <Connected System Alias>, for example, XXXCLNTYYY (XXX: System ID, YYY:
Client)
○ Description: <Description for Connected System Alias>
○ RFC Destination: <Connected System>_RFC, the RFC Destination with connection type 3 created in the
step Create RFC Destination of Type ABAP Connection [page 92].
○ Software Version: DEFAULT
○ System ID: <Your Connected System ID>
○ Client: <Your Connected System Client>
4. Choose Save.
6.5.1.5 Create System Alias for Connected System
Use
In this activity, you create the customer system alias for the connected system for UI navigation.
Procedure
2. In the Table/View field, enter the view /UI2/VC_SYSALIAS and choose Maintain.
3. On the Change View “UI2: Maintenance of Customer System Aliases” screen, choose New Entries and make the
following entries.

○ Alias: Connected System ID defined in the step Define Company Code, Plant, Purchasing Organization for
Connected System [page 74].
4. Choose Save.
6.5.1.6 Configure System Alias Mapping
Use
In this activity, you create the system alias mapping UI navigation.
Procedure
2. In the Table/View field, enter the view /UI2/V_ALIASMAP and choose Maintain.
3. On the Change View “UI2: Maintenance of System Alias Mapping” screen, choose New Entries and make the
following entries.
○ Source: Alias defined in the step Create System Alias for Connected System [page 95].
○ Target System Alias: of the RFC Destination with connection type H created in the step <Connected
System>Create RFC Destination of Type HTTP Connection to ABAP System for HTTPS Connection [page
93], for example, <XXXCLNTYYY (XXX: System ID, YYY: Client)
4. Choose Save.
6.5.1.7 Register Connected System as Safe Host (Optional)
Use
In this activity, you register connected system as safe host in HTTP_WHITELIST table.
Procedure
1. Log on to the S/4HANA Fiori frontend system and execute transaction SE16.
2. In the Table Name field, enter the table HTTP_WHITELIST and choose Create Entries.

3. On the Table HTTP_WHITELIST Insert screen, make the following entries.
○ ENTRY_TYPE: 30 ClickJacking Framing Protection
○ SORT_KEY: next to existing ones (for example, 0002)
○ PROTOCOL: *
○ HOST: Host of Connected System
○ PORT: leave field empty
○ URL: *
4. Choose Save.
6.6 Unified Key Mapping Service for Central Procurement
In the complex landscape of central procurement, each connected system in the landscape have its own data
management and governance. In the absence of such data management, there is no way for central purchaser to
work with centralized master data. It gets more difficult with multiple business scenario and verity of master data
objects.
With Unified Key Mapping Service for Central Procurement, Central Purchaser can process following Direct
Material Sourcing scenarios.
● Ability to process Central Purchase Contract for PO creation with various suppliers across the connected
systems
6.6.1 Manage Key Mapping for Supplier
Use
In this activity, you can create, edit, or delete key mapping information for Supplier, by creating, editing, or deleting
records in mapping groups.
A mapping group specifies the key mapping data for object IDs that are mapped to each other. Each mapping
group includes an object type, a business system, an object ID type, and an object ID. Each object instance can
have one or more object IDs.
Procedure
1. Login into the S/4HANA Hub system and execute transaction MDG_KM_MAINTAIN.
2. In the Data Replication section, navigate to the Manage Key Mapping application.
3. On the Manage Key Mapping screen, make the following entries and choose Add Row.

○ Business Object Type: Supplier
○ Business System: Logical System for S/4HANA Hub system
○ Object ID Type: ERP Vendor Number
○ Object ID: your supplier ID in S/4HANA Hub system
4. On the Mapped Objects screen, make the following entries in line No. 2 and choose Save.
○ System ID: your connected system ID
○ Object ID Type: ERP Vendor Number
○ Object ID: your supplier ID in connected system
6.7 Master Data
To create a central purchase contract in SAP S/4HANA Cloud HUB system and distributed to multi connected
systems, you need to make the following data for creating central purchase contract also exist in connected
system.
● Supplier
● Pricing Schema
● Inco-terms
● Payment Terms
● Shipping Instructions
● Document Types
● Unit of Measures
● Currency
● Tax code
The Purchase Organization data in the hub and the connected systems are not harmonized. Purchase Organization
view data is not required to supplier in Hub system.
6.7.1 Other Data
Make the following data in S/4HANA Cloud Hub system used for creating central contract also valid in connected
system.
● Pricing Schema
● Inco-terms
● Payment Terms
● Shipping Instructions
● Document Types
● Unit of Measures
● Currency
● Tax code

6.8 Extend Central Purchase Contract using BADIs
The following BADIs are implemented for Central Purchase Contract extensions:
● MM_PUR_S4_CCTR_FLDCTRL_SIMPLE: Change of Field Controls for Central Purchase Contracts

This Business Add-In (BAdI) is used in the Fiori UI for Manage Purchase Contracts (MM-FIO-PUR-SQ-CON)
component. You can use this BAdI to change the field control properties of specific fields in the FIORI user
interface at header, item, and distribution facets.
● MM_PUR_S4_CCTR_CHECK: Check of Central Purchase Contract Before Saving
This BAdI is used in the Fiori UI for Manage Purchase Contracts (MM-FIO-PUR-SQ-CON) component. You can
use this BAdI raise to messages when processing central purchase contracts. This may be necessary, for
example, if a new error message needs to be raised based on your own validations.
● MM_PUR_S4_CCTR_MODIFY_HEADER: Change of Central Purchase Contract Before Saving
use this BAdI to modify header data in central purchase contracts. This may be necessary, for example, if new
customs fields are introduced in central purchase contracts at header level.
● MM_PUR_S4_CCTR_MODIFY_ITEM: Change of Central Purchase Contract Item Before Saving
This BAdI is used in the Fiori UI for Manage Central Purchasing Contracts (MM-FIO-PUR-SQ-CON) component.
You can use this BAdI to modify item data in central purchase contracts. This may be necessary, for example, if
new custom fields are introduced at item level in central purchase contracts.
● MM_PUR_S4_CCTR_MOD_DISTR_CTR: Change of Outline Agreements Created from Central PC Before
Distribution
This Business Add-In (BAdI) is used to modify information, such as header, item, and item condition data in
outline agreements to be distributed to a particular connected system after the central contract has been
approved. This enables you to create distributed outline agreements in the connected system with different
data in comparison to the approved central contract. This may be necessary, for example, if suppliers are
represented differently in the connected systems.
● MM_PUR_S4_CCTR_MAP_TO_OA: Formation of Outline Agreements from the Central Contract
use this BAdI to modify the data, such as header data, item data, or item conditions, in the contracts to be
distributed to a particular connected system after the central contract has been approved. This enables you to
create distributed contracts in the connected system with the different data than the one available in the
approved central contract. This may be necessary, for example, if suppliers are represented differently in the
connected systems.
● MM_PUR_S4_CCTR_MAP_TO_OA: Formation of Outline Agreements from Central Purchase Contracts
This Business Add-In (BAdI) is used in the Fiori UI for Manage Purchase Contracts (MM-FIO-PUR-OA)
component. You can use this BAdI to influence the formation of outline agreements based on the central
contact data, during the split of the central contact.
● MM_PUR_S4_CCTR_PRINT_PREVIEW : Retrieval of Output Form Details for Print Preview in Central Contracts
This Business Add-In (BAdI) is used to retrieve template details for the output form of the Print Preview feature
in central purchase contracts.

6.9 Central Procurement Operations Monitor – Central
Contract Management Scenario
6.9.1 Monitor Connected System Status
6.9.1.1 Schedule Status Check of Connected Systems
Use
In this activity, you schedule job to check connection status of all connected systems that configured in the chapter
Define Connected System [page 70].
Procedure
1. Log on to the SAP S/4HANA Fiori UI launchpad with the user that has the role template SAP_BR_BPC_EXPERT.
2. In the Job Scheduling for Purchasing section, navigate to the Schedule Status Check of Connected Systems
application.
3. On the Application Jobs screen, choose Create.
4. On the Template Selection screen, make the following entries and choose Step 2.
○ Job Template: Check Status of Connected Systems
○ Job Name: <Your Job Name>, for example, Check Status of Connected Systems
5. Scheduling Options is by default set to Start immediately.
6. To change the Scheduling Options, choose Define Recurrence Pattern.
7. On the Scheduling Information screen, choose the required option and maintain the fields accordingly and
confirm with OK.
8. Choose Step 3 and choose Schedule.
9. Check the Application Jobs screen for the scheduled job and once the status is displayed as finished, then the
job is complete.
6.9.1.2 Monitor Connected System Status
Purpose
You can use the Central Procurement Operations Monitor application to monitor connected system status.

Procedure
2. In the Operations Monitoring for Central Procurement section, navigate to the Central Procurement Operations
Monitor application.
3. In the Connected Systems section, you can check the conneted system status (Online/Offline).
4. Choose section title or the chart to go to the detail screen for Monitor Connected Systems.
5. On the Monitor Connected Systems screen, check detail Connected System and System Status.
6.9.2 Monitor Central Contract Management Scenario
You can use the Central Procurement Operations Monitor application to monitor messages and perform related
troubleshooting activities.
You can monitor following information:
● Central Purchase Contracts XML messages in the hub system

● Central Purchase Contracts XML messages in the connected system
● Release Order Update jobs in the hub system
Procedure
2. In the Operations Monitoring for Central Procurement section, navigate to the Central Procurement Operations
Monitor application.
3. In the Central Contract Management section, you can choose following monitor options:
○ Need Attention in Hub System
This function monitors failed outbound/inbound messages for Central Purchase Contracts in the hub
system. You can select the error purchase requisition and choose Investigate to open the Message
Dashboard application for detail information.
○ Need Attention in Connected System
This function monitors failed outbound/inbound messages for Central Purchase Contracts in the
connected system. You can select the error purchase requisition and choose Investigate to navigate to
connected system for detail information.
○ Failed Release Order Update Jobs
This function monitors failed Release Order Update jobs in the hub system. You can select the failed job
and choose View Job Details to open the Schedule Import of Release Orders application for detail
information. And you can also have the option to Restart or Dismiss the job.

7 Configure the Connected System
The necessary steps which are needed in the Connected System.
7.1 ERP or S/4HANA On-premise as Connected System
7.1.1 Create Trusted Connection from Connected System to

SAP S/4HANA Fiori Frontend System
In this chapter, you establish the trusted connection from connected system to S/4HANA Fiori frontend system.
To enable Single Sign-On Between S/4HANA Hub system and connected system for UI navigation, you can refer to
User Authentication and Single Sign-On -> Integration in Single Sign-On (SSO) Environments -> Single Sign-On for
Interaction Between Systems.
The trusted connection from connected system to S/4HANA Fiori frontend system can be done by executing task
list SAP_SAP2GATEWAY_TRUSTED_CONFIG in the connected system.
For more details, please refer to Configuration Using Task Lists and SAP Note 2510134 .
7.1.2 Configure OData Services
Use
In this activity, the following OData Service needs to be registered in the connected system.
● Creation of PO with data: MMPUR_PO_CREATE_SRV

This OData service is used to create Purchase Orders in the respective systems from which the Purchase
Requisitions were created.
● Back-end Data for Central Contracts: MMPUR_CCTR_BE_SRV
This OData service is used to fetch the data for Partners, Scheduling Agreement type, etc from connected
system which are used in the central contracts application.
● Calloff against Central contracts: MM_PUR_CCTR_CALLOFF_SRV
This OData service is used to extract the release orders which are created for the replicated contracts.

102 PUBLIC Configure the Connected System
● Central Contract Archive: MM_PUR_CCTR_ARCHIVE_SRV
This OData service is used to perform archiving actions on the replicated contracts when the Central
Contract(s) are archived.
● Material Value Help Service: MMPUR_BE_VALUE_HELP_SRV
This OData service is used to fetch the Material from connected system.
● Check backend contract creation/update from Cntrl Contract: MM_PUR_CCTR_CHECK_SRV
This OData service is used to check the Outline Agreement if it still has errors in the connected system.
● Central Procurement Admin Monitor Backend Status for CCTR:
MM_PUR_CPROC_OPS_MNTR_CCTR_BE_SRV
This OData service is the Connected System service which is used to determine whether the connected system
is S/4HANA or ERP and is required to navigate to connected system by clicking Investigate in Central
Procurement Interface Monitor application.
Procedure
For information of how to activate and maintain the OData services, please refer to SAP Gateway Foundation
(SAP_GWFND)
Search for the chapter Activate and Maintain Services : SAP Gateway Foundation (SAP_GWFND) > SAP Gateway
Foundation Developer Guide > OData Channel > Basic Features > Service Life-Cycle > Activate and Maintain
Services .
 Note
For SAP Gateway Configuration, please refer to SAP Gateway Foundation Configuration Guide in SAP Gateway
Foundation (SAP_GWFND) .
7.1.3 Clean up Gateway Cache
Use
This activity allows you to clear the cache for SAP gateway.
Cleaning up the cache is an operational activity that you can perform on a regular basis to ensure that irrelevant
files are removed from your system.
Procedure
1. Log onto the connected system (ERP) and enter transaction /N/IWFND/CACHE_CLEANUP.

Configure the Connected System PUBLIC 103
2. Check Cleanup Cache for all Models and choose Execute.
3. Enter transaction /N/IWBEP/CACHE_CLEANUP.
4. Check Cleanup Cache for all Models and choose Execute.
7.1.4 Configure User-Defined Search
7.1.4.1 Configure User-Defined Search for SOA Services
Purpose
In the activity, you configure user-defined search to enable search for asynchronous Web service operations using
attributes from the XML payload. The user-defined search is required for Central Purchase Contracts Scenario of
Central Procurement Operations Monitor.
This step is required if you setup the communication from the S/4HANA HUB system to the connected system via
P2P.
Procedure
1. Log on to the connected system and enter transaction SOAMANAGER.

2. On the newly opened SOA Management page, go to Monitoring tab and choose User-Defined Search.
3. On the User Defined Search: Configuration screen, choose Create.
4. On the Create Configuration screen, search for
PurchaseContractDistributionReplicationRequest_In by entering the Interface. Select the Interface
and choose Create.
5. On the Field section, search String PurchaseContract. Right click field PurchaseContract under
PurchaseContract and choose Add from the context menu.
6. On the Details of Configuration – Attribute section, enter following entries:
○ Status: Active
○ Extraction Type: Direct: extract search results at message runtime
7. On the Details of Configuration – Search Parameters section, change Search Name and check XML Path with
following values:
○ Search Name: ProcmtHubCentralContract
○ XML Path: /{http://sap.com/xi/APPL/
sProc}PurchaseContractDistributionReplicationRequest/PurchaseContract/
PurchaseContract

8. Choose Save to save the user-defined search.
9. Choose Back.
10. On the User Defined Search: Configuration screen, choose Create.
11. On the Create Configuration screen, search for
PurchaseContractDistributionConfirmationRequest_Out by entering the Interface. Select the
Interface and choose Create.
12. On the Field section, search String PurchaseContract. Right click field PurchaseContract under
PurchaseContractConfirmation and choose Add from the context menu.
13. On the Details of Configuration – Attribute section, enter following entries:
○ Status: Active
○ Extraction Type: Direct: extract search results at message runtime
14. On the Details of Configuration – Search Parameters section, change Search Name and check XML Path with
following values:
○ Search Name: ProcmtHubCentralContract
○ XML Path: /{http://sap.com/xi/APPL/
sProc}PurchaseContractDistributionConfirmationRequest/
PurchaseContractConfirmation/PurchaseContract
15. Choose Save to save the user-defined search.
To make created user-default search help take effect for historical messages, please execute report
SRT_UDS_INDEX for receiver interface PurchaseContractDistributionReplicationRequest_In, sender interface
PurchaseContractDistributionConfirmationRequest_Out.
7.1.4.2 Configure User-Defined Search for Integration Engine
Purpose
In the activity, you configure user-defined search to enable search for asynchronous Web service operations using
attributes from the XML payload. The user-defined search is required for Central Requisitioning Scenario of Central
Procurement Operations Monitor.
 Note
Note This step is required if you setup the communication from the S/4HANA HUB system to the connected
system via PI.
Procedure
1. Log on to the connected system and enter transaction SXMS_LMS_CONF.

2. On the Manage Filters and Search Criteria screen, choose Add.
3. On the Entry Filter screen, enter following entries and choose Continue.

○ Name: PurchaseContractDistributionReplicationRequest_In
○ Namespace: http://sap.com/xi/HubERPI
○ Description: Central Contract
4. Double click the filter you created, on the Search Criteria for Selected Filter section, choose Add.
5. On the Extractor Data screen, enter following entries and choose Continue:
○ Name: PROCMTHUBCENTRALCONTRACT
○ Description: Central Contract ID
○ XPath: /n0:PurchaseContractDistributionReplicationRequest/PurchaseContract/
PurchaseContract
○ Extract During Message Processing: check
○ Extract Using External Job: check
6. On the Namespace Prefixes for Selected Filter section, choose Add.
7. On the Entry Namespace Prefix screen, enter following entries and choose Continue:
○ Prefix: n0
○ Namespace: http://sap.com/xi/APPL/sProc
8. Choose Active to activate the user-defined search.
9. On the Manage Filters and Search Criteria screen, choose Add.
10. On the Entry Filter section, enter following entries and choose Continue.
○ Name: PurchaseContractDistributionConfirmationRequest_Out
○ Namespace: http://sap.com/xi/HubERPI
○ Description: Central Contract
11. Double click the filter you created, on the Search Criteria for Selected Filter section, choose Add.
12. On the Extractor Data screen, enter following entries and choose Continue:
○ Name: PROCMTHUBCENTRALCONTRACT
○ Description: Central Contract ID
○ XPath: /n0:PurchaseContractDistributionConfirmationRequest/
PurchaseContractConfirmation/PurchaseContract
○ Extract During Message Processing: check
○ Extract Using External Job: check
13. On the Namespace Prefixes for Selected Filter section, choose Add.
14. On the Entry Namespace Prefix screen, enter following entries and choose Continue:
○ Prefix: n0
○ Namespace: http://sap.com/xi/APPL/sProc
15. Choose Active to activate the user-defined search.
To make created user-default search help take effect for historical messages, please execute report
SXMS_EXTRACT_MESSAGES for receiver interface PurchaseContractDistributionReplicationRequest_In,
sender interface PurchaseContractDistributionConfirmationRequest_Out.

7.1.5 Define Purchase Contract Document Type for Subordinate
Central Contracts
Use
In this activity, you define purchase contact document type for local contract that distributed from Subordinate
Central Contracts.
Procedure
To configure Purchase Contract Document Type for Subordinate Central Contracts in the connected system,
perform the following steps:
1. Log on to the connected system and enter transaction SPRO.

2. Navigate to the configuration activity: Materials Management Purchasing Contract Define Document
Types .
3. On the Change View "View to maintain restart conditions": Overview screen, you can copy your existing quantity
and value contract document types to create following contract document types which is used for Subordinate
Central Contracts distribution.
Purchasing Doc. Type Doc. Type Description
HSMK Quantity Contract
HSWK Value Contract
4. Choose Save.
7.2 S/4HANA Cloud as Connected System
SAP Cloud Connector for Integration with On-Premise Systems
For all scenarios integrating SAP S/4HANA Cloud with SAP On-Premise scenarios, the SAP_COM_0200 – Cloud
Connector communication arrangement must be activated. This is a prerequisite for all other communication
arrangements.

To check if the SAP_COM_0200 – Cloud Connector communication arrangement is active in your system, go to the
Maintain Communication Arrangements app. If it is not active, you must set it up.
To set up the communication scenario, follow the procedure under Integrating On-Premise Systems.
When configuring the access control list for the cloud to on-premise scenario, you need to specify URL paths
(resources) which can be invoked on the on-premise host. The SAP Cloud Platform Cloud Connector uses very
strict allow lists for its access control.
Add following permitted URL paths (Resources) in accessible resource.
SAP ERP as connected system:
● /sap/opu/odata/sap/MMPUR_PO_CREATE_SRV
● /sap/opu/odata/sap/MMPUR_CCTR_BE_SRV
● /sap/opu/odata/sap/MMPUR_BE_VALUE_HELP_SRV
● /sap/bc/srt/scs_ext/sap/purchasecontractconfirmationin
● /sap/bc/srt/scs_ext/sap/purchasecontractdistributionr2
● /sap/opu/odata/sap/API_CENTRAL_PURCHASECONTRACT_SRV
● /sap/bc/srt/scs_ext/sap/srcelistchangereqconfin
● /sap/bc/srt/scs_ext/sap/srcelistchangereqin
● /sap/opu/odata/sap/MM_PUR_CPROC_OPS_MNTR_CCTR_BE_SRV
7.2.1 Configure Communication Management
A communication arrangement describes a communication scenario with a remote system during configuration
time. It provides the required metadata for the service configuration, such as credentials, outbound ports,
destinations, URLs, and other service specifications which contain technical data to enable inbound and outbound
communications. The activation of a Communication Arrangement will populate the required configuration tables
of the Web Service such as logical ports and RFC destinations, as well as the authorization settings for the
communication users.
7.2.1.1 Create Communication User
Use
In this activity, you create the communication user for the outbound communication scenarios.

Procedure
1. Log on to the SAP S/4HANA Fiori UI launchpad with the user that has the role template
SAP_BR_ADMINISTRATOR.
2. Under the Communication Management section, navigate to the Maintain Communication Users application
3. On the Maintain Communication Users screen, choose New.
4. Under User Data, make the following entries:
○ User Name
○ Description
○ Password
5. Choose Create.
6. Make a note of user data. This is required when you create the communication arrangement.
7.2.1.2 Create Communication Systems
Use
In this activity, you create the communication system for the connected system. This enables data exchange
between the connected system and the SAP S/4HANA Cloud Hub system by using remote function calls.
Procedure
2. In the Communication Management section, navigate to the Communication Systems application.
3. On the Communication System screen, choose New.
4. On the New Communication System screen, enter the following entries and choose Create.
○ System ID: Your Communication System ID
○ System Name: Your Communication System Name
5. In the General Data area, retain the default system name.
6. In the Technical Data area, maintain the values for following fields:
Fields Values
Host Name The virtual host name for the S/4HANA On-premise hub sys
tem maintained in cloud connector.

Fields Values
HTTPS Port The https port for the S/4HANA On-premise hub system
maintained in cloud connector
User Cloud Connector X
Instance Number For example: 00
Client For example: 100
7. In the Contact Information area, maintain the values for the following fields:
Fields Values
Contact Person Name For example: John Smith
Phone Number For example: +918888333322
E-Mail For example: abc@xyz.com
8. To add the User for Inbound Communication area, choose Add.

9. In the New Inbound Communication User dialog box, choose the Authentication Method with User Name and
Password and enter the user name that you created in step Create Communication User [page 108]. Confirm
with OK.
10. To add the User for the Outbound Communication area, choose Add.
11. In the New Outbound User dialog box, choose the Authentication Method with User Name and Password and
enter the user name, password of the SAP S/4HANA Cloud Hub system created in step Create Communication
User [page 108]. Confirm with Create.
12. Choose Save.
7.2.1.3 Create Communication Arrangements for Direct

Material Sourcing
Use
In this activity, you create a communication arrangement that describes a communication scenario with a remote
system during configuration. It provides the required metadata for the service configuration, such as credentials,
outbound ports, destinations, URLs and other service specifications. This contains technical data to enable
inbound and outbound communications.

Procedure
1. Log on to the Fiori launchpad with user that has the role template SAP_BR_ADMINISTRATOR.
2. In the Communication Management section, navigate to the Communication Arrangements application.
3. On the Maintain Communication Arrangements screen, choose New.
4. On the New Communication Arrangement screen, make the following entries and then choose Create:
○ Scenario: SAP_COM_0513(SAP S/4HANA Procurement Hub - Central Sourcing Satellite Integration)
○ Arrangement Name: Your Communication Arrangement Name
5. On the Communication Arrangement screen, make the following entries:
In the Common Data section:
Communication System: Maintain the communication system ID defined in step Create Communication
Systems [page 109].
In the Outbound Services section:
Outbound HTTP Connections: Maintain Path /sap/opu/odata/sap/?sap-client=<S/4HANA hub system
client number>
6. Choose Save.
7.2.1.4 Create Communication Arrangements for Central

Procurement Foundation Layer
Use
Procedure
○ Scenario: SAP_COM_0587 (SAP S/4HANA Procurement Hub - Foundation Layer Hub Integration)
○ Arrangement Name: <Your Communication Arrangement Name>
5. On the Communication Arrangement screen, make the following entries and then choose Save:
Communication System: Maintain the communication system ID defined under step Create Communication
Systems [page 109].

6. Choose Save.
7.2.1.5 Create Communication Arrangements for Central

Purchase Contract
Use
Procedure
○ Scenario: SAP_COM_0243 (SAP S/4HANA Procurement Hub – Central Contract Management Integration)
○ Arrangement Name: Your Communication Arrangement Name
5. On the Communication Arrangement screen, make the following entries:
○ Communication System: Maintain the communication system ID defined in step
6. On the Outbound Services screen, make the following entries:
○ Outbound HTTP Connections: Maintain Path /sap/opu/odata/sap/?sap-client=<S/4HANA hub
system client number>
○ Central Contract Replication Confirmation: Maintain Path /sap/bc/srt/scs_ext/sap/
purchasecontractconfirmationin/?sap-client=<S/4HANA hub system client number>
○ Source List Confirmation: Maintain Path /sap/bc/srt/scs_ext/sap/srcelistchangereqconfin?
sap-client=<S/4HANA hub system client number>
7. Choose Save.

7.2.2 Maintain Clickjacking Protection Whitelist
User
In this activity, you maintain S/4HANA Hub system as trusted host in S/4HANA Cloud as connected system.
Procedure
2. In the Security section, navigate to the Maintain Clickjacking Protection Whitelist application.
3. On the Maintain Clickjacking Protection Whitelist screen, choose Create.
4. Under Add Trusted Host, make the following entries:
○ Trusted Host Name: host name of S/4HANA Fiori frontend system
○ Schema: HTTPS
○ Port: https port of S/4HANA Fiori frontend system
5. Choose Add.

8 Setup Integration with SAP S/4HANA for
Supplier Quotation Management
To use SAP S/4HANA for supplier quotation management, It is mandatory that SAP S/4HANA for supplier
quotation management in SAP BTP is active.
If the solution is not active, please request the activation via BCP – Ticket Component : XX-S4C-OPR-SRV.
8.1 Prerequisites in BTP
You should check and finish all steps in Technical Prerequisites, Onboarding and Connectivity in Admin Guide for
SAP S/4HANA for supplier quotation management.
8.2 Configuration in S/4HANA System
8.2.1 Configure OData Services
Use
In this activity, the OData Services in chapter Connectivity of Admin Guide for SAP S/4HANA for supplier quotation
management need to be configured in the SAP S/4HANA system.
Procedure
For information of how to activate and maintain the OData services, please refer to SAP Gateway Foundation
(SAP_GWFND)
Search for the chapter Activate and Maintain Services: SAP Gateway Foundation (SAP_GWFND) SAP Gateway
Foundation Developer Guide OData Channel Basic Features Service Life-Cycle Activate and Maintain
Services .

114 PUBLIC Setup Integration with SAP S/4HANA for Supplier Quotation Management
 Note
For SAP Gateway Configuration, please refer to SAP Gateway Foundation Configuration Guide in SAP Gateway
Foundation (SAP_GWFND) .
8.2.2 Manage Channel and Parameters for SAP Event Mesh
Use
In this activity, the channel connections in Step 5a of Additional Services in Admin Guide for SAP S/4HANA for
supplier quotation management need to be configured in SAP S/4HANA system.
Procedure
This step should start after the front steps finished in BTP, so please directly follow complete steps in chapter
Additional Service in BTP [page 115] for all the procedures.
8.3 Additional Service in BTP
SAP S/4HANA for supplier quotation management needs additional cloud services to cover its functionality. You
should check and finish all steps in Supplier Quotation Management Admin Guide-Additional Service.

Setup Integration with SAP S/4HANA for Supplier Quotation Management PUBLIC 115
9 Integration with SAP S/4HANA for
Enterprise Contract
Management(Optional)
To use SAP S/4HANA for Enterprise Contract Management in Central Purchase Contracts, It is mandatory that
scope item 1XV - SAP S/4HANA for Enterprise Contract Management is active. You can check this in the App
Manage Your Solution.
If the scope item is not active, please request the activation via BCP – Ticket Component : XX-S4C-OPR-SRV. This
is a price-relvenent scope item.
9.1 Switch on Legal Transaction Facete in Sourcing Project
Use
In this activity, you choose to switch on legal transaction facete to make it present in sourcing project application.
Procedure

2. Navigate to configuration activity: SAP Reference IMG > Enterprise Contract Management > Integration >
Integration with Business Objects > Enable Switch for Business Object Integration Enable.
3. On the change view "Enable Enterprise Contract Management Integration": Overview screen, choose the entry
Business Feature ID:SOURCINGPROJECTECMINTEGRATION and make the following entries.
Ftr State:Active
4. Choose Save.

116 PUBLIC Integration with SAP S/4HANA for Enterprise Contract Management(Optional)
9.2 Switch on Integration with Enterprise Contract
Management
Use
In this activity, you add an entry for switch on integration with enterprise contract management or switch it off with
selection.
SAP Central Business Configuration
1. Choose Save.
2. On the change view "Business Object Integration Switch": Overview screen, choose New Entries and make the
following entries.
Business Feature ID : LCM_BOINTEGRATION
Ftr State: Active
3. In the Realize phase, navigate to the Configuration Activities tab. Search for Enable Switch for Business Object
Integration and choose Go to Activity button to navigate directly to the SAP S/4HANA Cloud system. Log on to
the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration (SAP_BR_BPC_EXPERT).
4. Log on to the project experience in SAP Central Business Configuration.
Procedure

Integration with Business Objects > Enable Switch for Business Object Integration Enable.
3. On the change view "Business Object Integration Switch": Overview screen, choose New Entries and make the
following entries.
Business Feature ID: LCM_BOINTEGRATION
Ftr State: Active
4. Choose Save.

Integration with SAP S/4HANA for Enterprise Contract Management(Optional) PUBLIC 117
9.3 Assign Linked Object Type to Default Profile
Use
In this activity, you assign sourcing project and supplier quotation object to default profile that can be assigned to
contexts and legal transactions.
SAP Central Business Configuration
1. Log on to the project experience in SAP Central Business Configuration.

2. In the Realize phase, navigate to the Configuration Activities tab. Search for Define Profiles and choose Go to
Activity button to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a
Configuration Expert - Business Process Configuration (SAP_BR_BPC_EXPERT).
3. On the change view "Define Sets": Overview screen, choose the Profile Set G5 and double click Linked Objects in
Dialog Structure.
4. On the change view "Linked Objects": Overview screen, choose New Entries and make the following entries.
LObj. Set: G5 (Generic Linked Objects)
LnkObj. Ty: 0008 (Sourcing Project)
LObj. Set: G5 (Generic Linked Objects)
LnkObj. Ty: 0009 (Supplier Quotation)
Procedure

2. Navigate to configuration activity: SAP Reference IMG > Enterprise Contract Management > Profiles > Define
Profiles.
3. On the change view "Define Sets": Overview screen, choose the Profile Set G5 and double click Linked Objects in
Dialog Structure.
4. On the change view "Linked Objects": Overview screen, choose New Entries and make the following entries.
○ LObj. Set: G5 (Generic Linked Objects)
LnkObj. Ty: 0008 (Sourcing Project)
○ LObj. Set: G5 (Generic Linked Objects)
LnkObj. Ty: 0009 (Supplier Quotation)
5. Choose Save.

9.4 Define Integration Variant
9.4.1 Assign Profile to Integration Variant
Use
In this activity, you assign profile to your integration variant of sourcing project and supplier quotation.
Procedure

Integration with Business Objects > Define Integration Variants
3. On the Change view "Define Integration Variant": Overview screen, choose the Integration Variant SRPR and
SPQN, make the following entries:
Profile: GENERIC
4. Choose Save.
9.4.2 Assign Value of Set Type to Integration Mapping Variable
Use
In this activity, you assign set type to integration mapping variable for integration variants sourcing project and
supplier quotation.
Procedure

3. On the change view "Define Integration Variant": Overview screen, choose the Integration Variant SPQN, and
double click Map Variables to Integration Variant in Dialog Structure.

Integration with SAP S/4HANA for Enterprise Contract Management(Optional) PUBLIC 119
On the change view " Map Variables to Integration Variant": Overview screen,
choose Integration Mapping Variable S_MAIN_ENTITYand make the following entries:
Value of Set Type: 0006
Choose Integration Mapping Variable S_SOURCE_LINKED_OBJECT and make the following entries:
Choose Integration Mapping Variable SAP_SPQTN_PURCHASE_ORG and make the following entries:
4. On the change view "Define Integration Variant": Overview screen, choose the Integration Variant SRPR, and
double click Map Variables to Integration Variant in Dialog Structure.
On the change view " Map Variables to Integration Variant": Overview screen,
choose Integration Mapping Variable S_MAIN_ENTITY and make the following entries:
Choose Integration Mapping Variable S_SOURCE_LINKED_OBJECT and make the following entries:
Choose Integration Mapping Variable SAP_SRCGPROJ_BUSI_PARTNER and make the following entries:
Choose Integration Mapping Variable SAP_SRCGPROJ_PURCHASE_RESP and make the following entries:
5. Choose Save.
9.4.3 Set Active Indicator for Integration Variant Enablement
Use
In this activity, you need set active indicator for enable relevant integration variants.
Procedure

3. On the change view "Define Integration Variant": Overview screen, choose the Integration Variant SRPR and
SPQN, make the following entries:
Active: Checked
4. Choose Save.

10 Integration with SAP Enterprise Contract
Assembly(Optional)
To use SAP S/4HANA for Enterprise Contract Assembly, It is mandatory that scope item Integration to SAP
Enterprise Contract Assemblyagement (2OQ) is active. You can check this in the App Manage Your Solution.
If the scope item is not active, please request the activation via BCP – Ticket Component : XX-S4C-OPR-SRV. This
is a price-relvenent scope item.
To do the set-up process, please refer to the document of Setting Up Integration to SAP S/4HANA Cloud for
Enterprise Contract Assembly (2OQ).
10.1 Manage Document Variables
Use
In this activity, you maintain source filed alias of sourcing project and supplier quotation object to pre-delivered
variables.
Procedure

2. Navigate to configuration activity: SAP Reference IMG Enterprise Contract Management Integration
Integration with Enterprise Contract Assembly Variables Define Document Variables .
3. On the change view "Maintain Variable/Association Source": Overview screen, choose the Variable
LinkedObjects and double click Maintain Variable Source Field Alias in Dialog Structure.
4. On the Change View "Maintain Variable Source Field Alias": Overview screen, choose New Entries and make the
following entries.
○ Alias/Assoc. Name: SupplierQuotation
○ Field/Association: 1 Single Association
○ Long Text: Supplier Quotation
○ Alias/Assoc. Name: SourcingProject
○ Field/Association: 1 Single Association
○ Long Text: Sourcing Project
5. Choose Save.

Integration with SAP Enterprise Contract Assembly(Optional) PUBLIC 121
11 Monitoring and Error Handling
For monitoring the integration of the SAP S/4HANA system (hub system) with the connected systems, you can use
the Application Interface Framework (AIF) in the SAP S/4HANA system (hub system).
For more information, please refer the document Operations Guide at the SAP Help Portal under https://
help.sap.com/viewer/p/SAP_S4HANA_ON-PREMISE
Navigate to following section in chapter Central Procurement.
● Monitoring and Error Handling in the SAP S/4HANA System (Hub System)
● Monitoring and Error Handling in the SAP ERP Back-End System
● Monitoring and Error Handling in the SAP S/4HANA Back-End System

122 PUBLIC Monitoring and Error Handling
12 Appendix
12.1 Authorization Objects & Roles
You can change the authorization and role assignment for different business process like sourcing supplier list
proposal, preferred supplier list proposal or restrict the sup-plier list creation into any single type.
12.1.1 Authorization Objects & Roles for Preferred Supplier List
Authorization
Fields Value Description
SUPLRLTYPE 01 Standard Supplier List
02 User Specified Supplier List
ACTVT Value Description
01 Create
02 Change
03 Display
06 Delete
PQ Propose
F4 Value Help
The following authorization objects are for basic operations of preferred supplier list:
Authorization Object ACTVT SUPLRLTYPE Role in Fiori Launchpad
M_SUPL_TYP 01 01 or 02 Purchaser
Supplier List Type
02 01 or 02 Purchaser

Appendix PUBLIC 123
F4 01 or 02 Purchaser
Authorization Object ACTVT BUKRS Role in Fiori Launchpad
M_SUPL_BUK 01 $BUKRS Purchaser
Company Code
02 $BUKRS Purchaser
03 $BUKRS Purchaser
06 $BUKRS Purchaser
F4 $BUKRS Purchaser
Authorization Object ACTVT MATKL Role in Fiori Launchpad
M_SUPL_MAT 01 Purchaser
Material Group
02 Purchaser
03 Purchaser
06 Purchaser
F4 Purchaser
The following authorization objects are used to propose preferred supplier list:
M_SUPLPTYP 03 01 or 02 Purchaser
Supplier List Type
PQ 01 or 02 Purchaser
F4 01 or 02 Purchaser

124 PUBLIC Appendix
M_SUPLPBUK 03 $BUKRS Purchaser
Company Code
PQ $BUKRS Purchaser
F4 $BUKRS Purchaser
M_SUPLPMAT 03 Purchaser
Material Group
06 Purchaser
F4 Purchaser
12.1.2 Authorization Objects & Roles for Sourcing Supplier List
Authorization
Fields Value Description
SRSLREFTYP SP Sourcing Project
ACTVT Value Description
01 Create
02 Change
03 Display
06 Delete
F4 Value Help
22 Enter, Include, Assign

Appendix PUBLIC 125
The following authorization objects are for basic operations of sourcing supplier list:
M_SRSL_RTP 01 SP Sourcing Manager
Supplier List Reference

Object Type
02 SP Sourcing Manager
F4 SP Sourcing Manager
Authorization Object ACTVT BUKRS Role in Fiori Launchpad
M_SRSL_BUK 01 $BUKRS Sourcing Manager
Company Code
02 $BUKRS Sourcing Manager
F4 $BUKRS Sourcing Manager
Authorization Object ACTVT MATKL Role in Fiori Launchpad
M_SRSL_MTK 01 Sourcing Manager
Material Group
02 Sourcing Manager
03 Sourcing Manager
06 Sourcing Manager
F4 Sourcing Manager
The following authorization objects are used to propose preferred supplier list:
M_SRSLARTP 03 SP Sourcing Manager
Reference Object Type

126 PUBLIC Appendix
F4 SP Sourcing Manager
M_SRSLABUK 03 $BUKRS Sourcing Manager
Company Code
F4 $BUKRS Sourcing Manager
M_SRSLAMTK 03 Sourcing Manager
Material Group
22 Sourcing Manager
F4 Sourcing Manager
12.2 Known Restrictions
For restrictions related with central purchase contracts, please refer to Setting Up Central Purchase Contracts
(2ME) .
12.3 Support & Ticket Component
If you encounter errors with central contract relevant steps, please open a customer ticket to component MM-PUR-
HUB-CTR.
If you encounter errors with PO creation APIs or relevant steps, please open a customer ticket to component MM-
PUR-HUB-RFQ.
If you encounter errors for integration with SAP S/4HANA for supplier quotation management, please refer to
chapter Monitoring and Troubleshooting of Admin Guide for SAP S/4HANA for supplier quotation management.

Appendix PUBLIC 127
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you
agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at
any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.

128 PUBLIC Important Disclaimers and Legal Information
Important Disclaimers and Legal Information PUBLIC 129
www.sap.com/contactsap
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

4RD S4HANA2021 Set-Up EN XX

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

4RD S4HANA2021 Set-Up EN XX

Uploaded by

Copyright:

Available Formats

Set-Up Instructions | PUBLIC

Setting Up Direct Material Sourcing (4RD)

THE BEST RUN

1 Version Note - On Premise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4 Introduction to Direct Material Sourcing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

6 Configure the S/4HANA Hub System on On-Premise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Setting Up Direct Material Sourcing (4RD)

7 Configure the Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

9 Integration with SAP S/4HANA for Enterprise Contract Management(Optional). . . . . . . . . . . . . .116

10 Integration with SAP Enterprise Contract Assembly(Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . 121

11 Monitoring and Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Setting Up Direct Material Sourcing (4RD)

Setting Up Direct Material Sourcing (4RD)

The following content is for the On Premise version.

Setting Up Direct Material Sourcing (4RD)

Setting Up Direct Material Sourcing (4RD)

Version Date Change

1.0 First Version Document of SAP Direct

Setting Up Direct Material Sourcing (4RD)

Direct material sourcing process supports two major process

Setting Up Direct Material Sourcing (4RD)

Setting Up Direct Material Sourcing (4RD)

4.2 Target Audience

4.3 Use of this Document

4.4 Terminology Used in this Document

Setting Up Direct Material Sourcing (4RD)

RFC Remote Function Call

DMS Direct Material Sourcing

Any S/4HANA On-Premise 1709 and higher, with add-on

Any S/4HANA Cloud 1905 is considered as connected system.

You can find detail information for Integration Component HU­

2491065 - Release Information Note for HUBERPI Integra­

2573672 - Release Information Note to Enable SAP S/

Logical System Identifies a unique combination of system ID and client of a

Setting Up Direct Material Sourcing (4RD)

Setting Up Direct Material Sourcing (4RD)

5.1 Business Roles

Table 1: Business Roles

Name (Role) ID (Role)

Configuration Expert - Business Process Configuration SAP_BR_BPC_EXPERT

Administrator - Data Replication SAP_BR_ADMINISTRATOR_DATA_REPL

Setting Up Direct Material Sourcing (4RD)

6.1 Configure Best Practices Content

6.1.1 Bidder Role Definition(5RY)

6.1.1.1 Define BP Roles

Setting Up Direct Material Sourcing (4RD)

1. Access the transaction using one of the following navigation options:

SAP IMG Menu SAP Portfolio and Project Management Portfolio

Management Base System Interfaces SAP Human

Capital Management Integration SAP Porfolio and Project

Management System Customizing for SAP HCM SAP

Business Partner Business Partner Basic Settings

Business Partner Roles Define BP Roles

Transaction Code SPRO

BBP001 Bidder Bidder BBP001 Checked

3. Save your entries.

6.1.2 Direct Material Sourcing Basic Settings (5OO)

6.1.2.1 Number Range Settings for Sourcing Project Process

6.1.2.1.1 Define Number Range for Sourcing Projects

Setting Up Direct Material Sourcing (4RD)

1. Access the transaction using one of the following navigation options:

Transaction Code SPRO

2. Choose Change Intervals.

You can find detail information for Integration Component HU

2491065 - Release Information Note for HUBERPI Integra