2ME S4HANA2022 Set-Up EN XX

Set-Up Instructions | PUBLIC
SAP S/4HANA
2022-09-17
Setting Up Central Purchase Contracts (2ME)

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

Content
1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Important Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Business Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 Configure the S/4HANA Hub System on On-Premise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1 Configure Best Practices Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Central Procurement -General Configuration (2C8). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Situation Handling for Procurement (2R0). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Central Purchase Contracts (2RS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2 Configure Communication from Hub system to Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Create RFC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Create Logical System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Activate AIF Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Integration Options and SOA Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.3 S/4HANA Hub System Configuration Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Active SAP S/4HANA Procurement Hub and Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Define Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Assign Connected Systems to RFC Destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Configure Control Plane for the APIs of Central Procurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Define Company Code, Plant, Purchasing Organization for Connected System. . . . . . . . . . . . . . . . . .77
Define Local Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Define Grouping of Company Codes of Connected Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Maintain Reasons for Blocking Central Purchase Contract Items. . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Define Conditions to Restart Central Purchase Contract Processes. . . . . . . . . . . . . . . . . . . . . . . . . .81
Configure Fields for Editability of Purchase Outline Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Activate Item Hierarchies in Central Procurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Define Material Groups from Respective Connected System into the Hub system. . . . . . . . . . . . . . . 84
Deactivate Batch Parallelization for Mass Changes to Central Purchase Contracts. . . . . . . . . . . . . . . 85
Configure Version Management in Central Purchase Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Configure Commodity Pricing for Central Purchase Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Configure Header Condition for Central Purchase Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Maintain Condition Type Mapping for Purchasing Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Maintain Change Reasions for Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
3.4 UI Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Configure destination for connected system on Frontend System. . . . . . . . . . . . . . . . . . . . . . . . . . 101

2 PUBLIC Content
Configure Destination for Own System on Embeded System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.5 Unified Key Mapping Service for Central Procurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Manage Key Mapping for Supplier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Manage Key Mapping for Material. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
3.6 Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
3.7 Extend Central Purchase Contract using BADIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
3.8 Central Procurement Operations Monitor – Central Contract Management Scenario. . . . . . . . . . . . . . . 113
Monitor Connected System Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Monitor Central Contract Management Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
4 Configure the Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

4.1 ERP or S/4HANA On-premise as Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Create Trusted Connection from Connected System to SAP S/4HANA Fiori Frontend System. . . . . . 115
Configure OData Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Cleaning up Gateway Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Configure Batch Parallelization for Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Configure User-Defined Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Define Purchase Contract Document Type for Subordinate Central Contracts. . . . . . . . . . . . . . . . . 121
4.2 S/4HANA Cloud as Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
SAP Cloud Connector Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Configure Communication Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Maintain Clickjacking Protection Whitelist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5 Monitoring and Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
6 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
6.1 Known Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
6.2 Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Content PUBLIC 3
1 Purpose
The purpose of this document is to describe the general configuration steps required to manually set up the
configuration within the system landscape that has already been installed using the corresponding installation or
configuration guides for installation.
This document describes additional configuration steps that have to be carried out by customers in order to
activate the Central Purchase Contracts. As these configuration steps are customer-specific, they cannot be
delivered by SAP, and must be carried out by the customer.
The following figure provides you with an overview of the systems and their connection within Central Purchase
Contracts.
If you want to install SAP S/4HANA locally (on-premise) and if you do not want to configure manually and prefer an
automated installation process using BC Sets and other tools, you can set up a best-practice client and activate the
implementation content. For more information, see the Administration Guide for the Implementation of SAP S/
4HANA, on premise edition which is linked in the content library (included in the documentation package).

4 PUBLIC Purpose
2 Preparation
2.1 Important Definitions
Table 1:
Terms Meaning
SAP S/4HANA Hub system Identifies the SAP S/4HANA system from releases 2022 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:
3247542 - SAP S/4HANA for central procurement
2022: 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 SAP S/4HANA Cloud 2208 and higher release is consid

ered as connected system.
 Note
You can find detail information for Integration Component
HUBERPI and HUBS4IC in the following SAP Notes:
2491065 - Release Information Note for HUBERPI Inte

gration Component in SAP S/4HANA for Central Procure
ment
2573672 - Release Information Note to Enable SAP S/

4HANA as a Back-End for Central Procurement

Preparation PUBLIC 5
Terms Meaning
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.
2.1.1 Business Roles
• SAP_BR_BPC_EXPERT
• SAP_BR_ADMINISTRATOR

6 PUBLIC Preparation
3 Configure the S/4HANA Hub System on
On-Premise
3.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 setting up by activation the Best Practices Content, you can skip this chapter.
If your system is not setting up by activation the Best Practices Content or your system is an upgraded On Premise
system, you can refer the configuration details in the 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.
3.1.1 Central Procurement -General Configuration (2C8)
3.1.1.1 Manage Notification Providers
Use
In this activity, you can manage Notification Providers via activating/deactivating registered Notification Providers
in Hub system.
Procedure
1. Access the transaction using one of the following navigation options:

Configure the S/4HANA Hub System on On-Premise PUBLIC 7
SAP IMG Menu ABAP Platform Notification Channel Notification
Channel Provider Enablement Administration
Notification Provider Settings Manage Notification
Providers
Transaction Code SPRO
2. On the Change View “View for maintenance of activated notification providers” screen make the following
entries:
Notification Provider ID Is Active?
PROC_HUB_NOTIF_PROVIDER X
3. Save your entries.
3.1.1.2 Activation of Scope-Dependent Application Job

Catalog Entries
Use
In this activity, you activate Job Catalog to check Connected System status for central procurement.
Procedure
SAP IMG Menu ABAP Platform Application Server System

Administration System Administration Activation of
Scope-Dependent Application Job Catalog Entries
2. On the Change View “Application job scope”: Overview screen, create the following entry:
Application job scope
SAP_MMHUB_CONSYS_STS_J

8 PUBLIC Configure the S/4HANA Hub System on On-Premise
3.1.1.3 Responsibility Management for Central Procurement
3.1.1.3.1 Define Functions
Use
In this activity, you can create functions that are assigned to team members so that they can perform various
tasks.
Procedure
SAP IMG Menu Cross-Application Components General Application

Functions Responsibility Management Functions
Define Functions
2. On the Change View “Function Maintenance View” screen, choose New Entries and create the following entry:
Function
Descrip
Function tion
SCTPUR Central
Purchasing
WF_ADMIN Workflow
Adminis
tration
3.1.1.3.2 Define Function Profiles
Use
In this activity, you can create function profiles and assign functions to a function profile. You can group similar
functions for a business process in a function profile.

Procedure

Functions Responsibility Management Functions
Define Function Profiles
2. On the Change View “Function Profile” screen, choose New Entries and create the following entry:
Function
Profile De
Profile scription
SCPRC Central
Procure
ment Func
tions

4. On the View “Function Profile”: Overview screen, select the entry you just created, choose Function Profile to
Function Mapping in the Dialog Structure and create following settings:
Function
Descrip
Function tion
SCTPUR Central
Purchasing
WF_ADMIN Workflow
Adminis
tration
3.1.1.3.3 Assign Function Profiles to Standard Team Category
Use
In this activity, you can assign a function profile to a team category.

Procedure

Functions Responsibility Management Teams and
Responsibilities Team Categories Assign Function
Profiles to Team Category
2. On the View “Map Function Profiles to Standard Team Category”: Overview screen, choose New Entries and
create the following entry:
Function
Profile
Descrip
Category Profile tion
CPROC SCPRC Central

Procure
ment
Functions
3.1.1.3.4 Define Team Types
Use
In this activity, you can create and maintain team types for a standard team category.
Procedure

Functions Responsibility Management Teams and
Responsibilities Team Categories Define Team Types
2. On the Change View ”Team Type”: Overview screen, choose New Entries and create the following entry:

Team
Type De
Team Type Category scription
SCPRC CPROC Central

Procure
ment
3.1.1.4 Define DMS Document Type for Document

Management
Use
In this activity, you define the settings for the document type.
Procedure
1. Access the transaction using the following transaction:
SAP IMG Menu Cross-Application Components Document

Management Control Data Define DMS Document
Type
2. On the Change View “Define document types”: Overview screen, double-click the Define document status
descriptions folder.
3. On the Change View “ Define document status descriptions ”: Overview screen, choose New Entries and make
following entries:
Status
Lang. Document Status Abbrev. Texgt
EN AA WR Work Re
quest
EN AR AR Archived
EN FR H3 Released

Status
Lang. Document Status Abbrev. Texgt
EN IA IW In Work
4. Save your settings and return to the “ Define document types ”: Overview screen (you may need to choose the
Back (F3) icon twice).
5. On the Change View “Define document types”: Overview screen, choose New Entries.
6. On the New Entries: Details of Added Entries screen, enter the following values:
Field Name Description User Action and Values Comment
Document Type SL1
Doc. Type Desc. For External Use
Use KPro x
Version Assgmt x
Change Docs x
Use DS Package x
Number Assgmt 1
Internal Number Range 02 Choose Number Ranges to

define your own number
ranges.
Number Exit MCDOKZNR Choose Default to generate

this entry.
Vers. No. Incr. 1 Enter 1 if you want versions

to start with "00" instead of
"01"
User ‘*’
Authorization Group -
Lab/Office -
7. Save your settings and choose the Back (F3) icon to return to the Change View “Define document types”:
Overview screen.
8. On the Change View “Define document types”: Overview screen, select the document type SL1 and double-click
the Define document status folder.
9. On the Change View "Define document status": Overview screen, choose New Entries.

Field Name Description User Action and Values
Document Status AA
Status type P
10. Choose the Next Entry (F8) icon and add the new entries as follows:
Document Status IA
Prev. 1 Previous document status 1 AA
Document Status FR
Status type S
Prev. 1 Previous document status 1 IA
Document Status AR
Status type A
Prev. 1 Previous document status 1 FR
13. Save your settings and return to the Change View "Define document status": Overview screen (you may need to
choose the Back (F3) icon twice).
14. Select document type SL1, choose Edit in the menu bar and then choose the Copy As… (F6) icon and add the
new entries as follows:
Field Name Description User Action and Values Comment
Document Type SL9 Overwrite existing value
Doc. Type Desc. For Internal Use Overwrite existing value
15. Press Enter. Confirm the dialog box, which states: dependent entries copied.
16. Save your settings and return to the Change View “Define document types”: Overview screen (you may need to
choose the Back (F3) icon twice). The document type SL9 and the status network for the document type SL9
as copied from document type SL1 is created.

3.1.2 Situation Handling for Procurement (2R0)
3.1.2.1 Manage Notification Providers
Use
In this activity, you can manage Notification Providers via activating/deactivating registered Notification Providers.
Procedure
1. Access the transaction using the following navigation path:
IMG Path ABAP Platform Notification Channel Notification Channel Provider Enablement
Administration Notification Provider Settings Manage Notification Providers
2. On the Change View “View for maintenance of activated notification providers” screen choose New Entries and
create the following settings:
Notification Provider ID Is Active?
SIT_NOTIF_PROV check
SIT_NOTIF_PROV_EXT check
3. Save your settings.
3.1.2.2 Activation of Scope-Dependent Background Job

Definitions
Use
In this activity, you can insert the name of the job definition into table STJR_JOBD_SCOPE using the maintenance
view, if the assigned job definition is to be active (in other words, in scope) in the current client. In addition, you set
the status to “On”. If you do not want the job definition in the current client to be active, you set the scope status to
“Off”.

Procedure
IMG Path ABAP Platform Application Server System Administration Activation of
Scope-Dependent Background Job Definitions
2. On the Change View “Scope switch of technical jobs”: Overview screen choose New Entries and create the
following settings:
Scope
Job Definition Name State
SIT_TECH_JOB_BATCH_DAILY On
SIT_TECH_JOB_CLEAN_SIT_DATA On
SIT2_RT_CLEANUP On
3.1.3 Central Purchase Contracts (2RS)
3.1.3.1 Basic Setting
3.1.3.1.1 Define Number Ranges for Central Purchase

Contract
Use
In this activity, you define the number ranges for central purchase contract.
Procedure

SAP IMG Menu Materials Management Purchasing Central
Procurement – Setting in Hub System Central Purchase
Contract Define Number Ranges
Transaction Code OMH6
2. Choose Change Intervals.

3. On the Maintain Intervals: Purchasing document screen, create the following entry:
Field Name Entry
No 47
From No. 4700000000
To Number 4799999999
Nr Status 0
Ext Leave empty
3.1.3.1.2 Define Screen Layout at Document Level for Central

Purchase Contract
Use
In this activity, you define the number ranges for central purchase contract.
Procedure
Procurement Central Purchase Contract Define Screen
Layout at Document Level

2. On the Change View " View for Screen Layout in Central Purchase Contract": Overview screen, create the
following entries:
Field Name Values
Field Sel. Key ME31C
Field selection ............+.......................++...........+...+................
Field selection ......-..............................................................C
Field selection .........................------+..-.-.+-------........................
Field selection . ..
Field selection ..+......… -------
Field selection
Field selection
Description Create Central Contract
Field Name Values
Field selection ............*......*................*+...........+...+................
Field selection ......-..............................................................C
Field selection .........................------+..-.-.+-------........................
Field selection *.***....... -------
Field selection
Field selection
Description Change Central Contract
Field Name Values
Field selection ........*.*****..***......*.........**...........+**.+..*...*..*.*.**.
Field selection .***..-...*.**....***.....**...........*..........*........*.........C
Field selection .........................------+..-.-.+-------........................

Field Name Values
Field selection * **
Field selection ************ -------
Field selection
Field selection
Description Display Central Contract
Field Name Values
Field Sel. Key MKC
Field selection .................................................+++.+......+.........
Field selection ......-.............+................................................C
Field selection .........................------+..-.-.+-------........................
Field selection .......+.... -------
Field selection
Field selection
Description Central Quantity Contract
Field Name Values
Field Sel. Key PT0C
Field selection .................................................+.+.+..............+.
Field selection .........................------+..-.-.+-------........................
Field selection .........… ----------
Field selection
Field selection
Description Standard item central contract

Field Name Values
Field Sel. Key PT2C
Field selection .................................................+.+.+..............+.
Field selection .........................------+..-.-.+-------........................
Field selection .........… ----------
Field selection
Field selection
Description Consignment item Central Contr
Field Name Values
Field Sel. Key PT3C
Field selection ........-.-----..---......-.........--...........+.+.+..............+.
Field selection ........-----------------...................--........................
Field selection - -
Field selection -----....... ---.......
Field selection
Field selection
Description Subcontrg item, Central Contr
Field Name Values
Field Sel. Key PT4C
Field selection ...-..............................................++-....-........-.+.
Field selection ......-.-...........+..--............................................C
Field selection ........-----------------...................--........................
Field selection - .---

Field Name Values
Field selection ----------.. ----------
Field selection
Field selection
Description Material unknown Central Contr
Field Name Values
Field Sel. Key PT8C
Field selection ..............+--....---.-. .-..----...----.--..+-----.-.----..-.-.-+-
Field selection -.-..--..-----..-.--+..-..--.--.----.---.--.....-.-..---.....--...--.C
Field selection -----.-- --.- ---------.- - - -
Field selection . -- -.----------------------- -.. -- -
Field selection .....................----......
Field selection
Field selection
Description Material Grp Central Contract
Field Name Values
Field Sel. Key WKC
Field selection ..............+..................................+.+.+......+.........
Field selection .........................------+..-.-.+-------........................
Field selection .......+.… -------
Field selection
Field selection
Description Central Value Contract
3. Save your entry.

3.1.3.1.3 Define Document Type for Central Purchase
Contract
3.1.3.1.3.1 Define Document Type MK
Use
The purpose of this activity is to define document type MK for central purchase contract.
Procedure
1. Access the activity using the following navigation options:
IMG Menu Materials Management Purchasing Central

Procurement Central Purchase Contract Define
Document Types
2. On the Document Central Contract Change screen, select New Entries and make the following data:
Field Name User Action and Values
Type MK
Doc. type description Quantity Contract
Item number interval 10
Number range in the case of internal number assignment 47
FieldSel. MKC
3. Press Enter.
4. Select the line for the newly created Type MK and double-click Allowed item categories.
5. On the Admissible Item Categories for Document Type MK Quantity Contract screen, choose New Entries.
6. On the Admissible Item Categories for Document Type MK screen, enter the following data:
ItCat. Text for Item Cat.
Standard

K Consignment
L Subcontracting
M Material unknown
7. Press Enter.
Result
The order type MK Quantity Contract is defined.
3.1.3.1.3.2 Define Document Type WK
Use
The purpose of this activity is to define document type WK for central purchase contract.
Procedure

Document Types
Type WK
Doc. type description Value Contract

FieldSel. MKC
3. Press Enter.
4. Select the line for the newly created Type WK and double-click Allowed item categories.
5. On the Admissible Item Categories for Document Type WK Value Contract screen, choose New Entries.
6. On the Admissible Item Categories for Document Type WK screen, enter the following data:
Standard
K Consignment
L Subcontracting
M Material unknown
W Material group
7. Press Enter.
Result
The order type WK Value Contract is defined.
3.1.3.1.3.3 Define Document Type HRMK
Use
The purpose of this activity is to define document type HRMK for hierarchy central purchase contract.

Procedure

Document Types
Type HRMK
Doc. type description Quantity Contract
FieldSel. MKC
Control Indicator H
3. Press Enter.
4. Select the line for the newly created Type HRMK and double-click Allowed item categories.
5. On the Admissible Item Categories for Document Type HRMK Value Contract screen, choose New Entries.
6. On the Admissible Item Categories for Document Type HRMK screen, enter the following data:
Standard
L Subcontracting
M Material unknown
7. Press Enter.
Result
The order type HRMK Value Contract is defined.

3.1.3.1.3.4 Define Document Type HSMK
Use
The purpose of this activity is to define document type HSMK for subordinate central purchase contract.
Procedure

Document Types
Type HSMK
FieldSel. MKC
Control Indicator C
3. Press Enter.
4. Select the line for the newly created Type HSMK and double-click Allowed item categories.
5. On the Admissible Item Categories for Document Type HSMK Value Contract screen, choose New Entries.
6. On the Admissible Item Categories for Document Type HSMK screen, enter the following data:
Standard
L Subcontracting

M Material unknown
7. Press Enter.
Result
The order type HSMK Value Contract is defined.
3.1.3.1.3.5 Define Document Type HRWK
Use
The purpose of this activity is to define document type HRWK for hierarchy central purchase contract.
Procedure

Document Types
Type HRWK

FieldSel. WKC
Control Indicator H
3. Press Enter.
4. Select the line for the newly created Type HRWK and double-click Allowed item categories.
5. On the Admissible Item Categories for Document Type HRWK Value Contract screen, choose New Entries.
6. On the Admissible Item Categories for Document Type HRWK screen, enter the following data:
Standard
L Subcontracting
M Material unknown
W Material group
7. Press Enter.
Result
The order type HRWK Value Contract is defined.
3.1.3.1.3.6 Define Document Type HSWK
Use
The purpose of this activity is to define document type HSWK for subordinate central purchase contract.
Procedure

Document Types
Type HSWK
FieldSel. WKC
Control Indicator C
3. Press Enter.
4. Select the line for the newly created Type HSWK and double-click Allowed item categories.
5. On the Admissible Item Categories for Document Type HSWK Value Contract screen, choose New Entries.
6. On the Admissible Item Categories for Document Type HSWK screen, enter the following data:
Standard
L Subcontracting
M Material unknown
W Material group
7. Press Enter.
Result
The order type HSWK Value Contract is defined.

3.1.3.1.4 Define Tolerance Limit for Central Purchase
Contract Archiving
Use
In this activity, you define the tolerance limit for central purchase contract archiving.
Procedure

Procurement Central Purchase Contract Central
Purchase Contract Criteria for Archiving Define
Tolerance Limit for Archiving
2. On the Change View " Document Archiving": Overview screen, select New Entries and make the following data:
Field Name Entry
Document Type MK
Item Category 0
Resid. time 1 30
Resid. time 2 30

4. On the Change View " Document Archiving": Overview screen, select New Entries and make the following data:
Field Name Entry
Document Type WK
Item Category 0
Resid. time 1 30
Resid. time 2 30

3.1.3.1.5 Activation of Scope-Dependent Application Job
Catalog Entries
Use
In this activity, you activate the scope-dependent application job catalog entries for mass change of central
purchase contract.
Procedure
IMG Path ABAP Platform Application Server System Administration Activation of Scope-
Dependent Application Job Catalog Entries
2. On the Change View “Application job scope”: Overview screen, choose New Entries and create the following
settings:
Job Definition Name
SAP_MM_PUR_MASSCCTRBG_J
SAP_MM_CCTR_PRICE_UPDATE_DETAILS
3. Save your settings
3.1.3.2 Assign Central Purchase Contract Object Link to DMS

Document Type
Use
In this activity, you define the settings for the document type.

Procedure
IMG Path Cross-Application Components Document Management Control Data Define
DMS Document Type
2. On the Change View “Define document types”: Overview screen, double-click the Maintain object link
descriptions folder.
3. On the Change View “Maintain object link descriptions”: Overview screen, choose New Entries and add the new
entries as follows:
Object De
Lang. Object scription
EN EKKO_CCTR Central Pur

Contract
5. On the Change View “Define document types”: Overview screen, select the document type SL1, and double-
click the Define object links folder.
6. Choose New Entries and add the new entries as follows:
Document Type SL1
Object EKKO_CCTR
Screen no. 218
8. On the Change View “Define document types”: Overview screen, select the document type SL9, and double-
click the Define object links folder.
9. Choose New Entries and add the new entries as follows:
Document Type SL9
Object EKKO_CCTR
Screen no. 218

3.1.3.3 Output Management for Central Purchase Contracts
3.1.3.3.1 Assign Form Templates
Use
The purpose of this activity is to assign form templates for central purchase contract.
Procedure
1. Access the activity using the following navigation option:
SAP ECC Menu Cross-Application Component Output Control Assign

Form templatesAssign Form templates
2. On the Change view “Form Template”: Overview screen, click new entries and enter the following values and
choose Enter:
Application Object Type Output Type Form Type Form Template ID
CENTRAL_PURCHASE_CONTRACT CENTRAL_CONTRACT Output Forms (Gateway Inter EV_CENTRAL_CON

face) TRACT
Result
The Form templates are assigned to central purchase contract.

3.1.3.3.2 Assign Email Templates
Use
Procedure

Email templates
2. On the Change view “Email Template”: Overview screen, click new entries and enter the following values and
choose Enter:
Application Object Type Output Type Form Template ID
CENTRAL_PURCHASE_CONTRACT CENTRAL_CONTRACT MM_PUR_CCTR_DE

FAULT_TEMPLATE
Result
The Email templates are assigned to central purchase contract.
3.1.3.3.3 Assign Doc Types for Output
Use
The purpose of this activity is to assign document types to central purchase contract application objects and
output types, relevant during output item creation via output parameter determination.

Procedure

Doc Types for Output
2. On the Change view “Assign Doc Types”: Overview screen, click new entries and enter the following values and
choose Enter:
Application Object Type Output Type Doc Type
CENTRAL_PURCHASE_CONTRACT CENTRAL_CONTRACT SL1
Result
The doc types are assigned to central purchase contract.
3.1.3.3.4 Define Output Settings for Document Types
Use
The purpose of this activity is to define rules that determine one or more document types for the output..
Procedure
SAP ECC Menu Cross-Application Component Output Control Define

Output Settings for Document Types

2. On the Change view "Define Output Settings for Document Types"screen, click new entries and enter the
following values and choose Enter:
Application Object Type Output Type Doc Type Channel Relvant Merge
CENTRAL_PURCHASE_CON CENTRAL_CONTRACT SL1 EMAIL check check

TRACT
CENTRAL_PURCHASE_CON CENTRAL_CONTRACT SL1 PRINT check check

TRACT
Result
The doc types are assigned to central purchase contract.
3.1.3.4 Workflow for Central Purchase Contracts
3.1.3.4.1 Scenario Activation
Use
In this activity, you can activate or deactivate flexible workflow scenarios. Scenarios are not visible in the Fiori
Workflow Editor app until they have been activated in the back-end system.
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
WS00800346 select
3.1.3.4.2 Maintain Task Names and Decision Options
Use
In this activity, you can maintain workflow tasks that need to be included in the task filter together with their names
and decision keys.
Procedure
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
WS00800346 0000000009 Release of Central Purchase Contract
3. On the Change View “Step Name”: Overview screen, select the entry with Workflow ID WS00800346 Step ID
0000000009, choose Decision Keys in the Dialog Structure and create the following settings:
Key Decision Text Nature
1 Release POSITIVE
2 Reject NEGATIVE
4. Save your settings and back to the Change View “Step Name”: Overview screen.
5. On the Change View “Step Name”: Overview screen, choose New Entries and create following settings:

Workflow ID Step ID Step Description
WS00800346 0000000032 Release of Hierarchical Central Contracts
6. On the Change View “Step Name”: Overview screen, select the entry with Workflow ID WS00800346 Step ID
0000000032, choose Decision Keys in the Dialog Structure and create the following settings:
Key Decision Text Nature
1 Release POSITIVE
2 Reject NEGATIVE
3.1.3.4.3 Define Conditions to Restart Central Purchase

Contract Processes
Use
With this activity, you can define conditions based on the purchasing document types to restart processes, such as
the flexible workflow, for central purchase contracts and central purchase contract hierarchies.
Procedure
Materials Management > Purchasing > Central Procurement

> Central Purchase Contract > Define Conditions to Restart
IMG Menu Central Purchase Contract Processes
2. On the Define Conditions to Restart Central Purchase Contract Processes screen, select New Entries and make
the following data:
Catagory Doc. Type Activate
Central Purhase Contract ALL X

Catagory Doc. Type Activate
Central Purchase Contract Hierarchy ALL X
3. Press Enter.
4. Select the line for the newly created Catagory Central Purchase Contract and double-click Purchasing Doc.
Workflow Relevant Field Details.
5. On the Purchasing Doc. Workflow Relevant Field Details screen, choose New Entries and entry the following
entries:
Facet for Customizing Central Contracts Fields for Customizing Central Contracts Eable
EKKO Header BEDAT X
EKKO Header BSAKZ X
EKKO Header BSART X
EKKO Header BSTYP X
EKKO Header BUKRS X
EKKO Header EKGRP X
EKKO Header EKORG X
EKKO Header INCO1 X
EKKO Header KDATB X
EKKO Header KDATE X
EKKO Header KTWRT X
EKKO Header LIFNR X
EKKO Header SPRAS X
EKKO Header WAERS X
EKPO Item LOEKZ X
EKPO Item MATKL X
EKPO_DISTR Distribution ISDELETED X
EKPO_DISTR Distribution PURCHASINGDOCUMENTDISTRPCT X
EKPO_DISTR Distribution TARGETQUANTITY X
6. Press Enter.
7. Save your settings and return to Define Conditions to Restart Central Purchase Contract Processes screen.

8. Select the line for the newly created Catagory Central Purchase Contract Hierarchy and double-click Purchasing
Doc. Workflow Relevant Field Details.
9. On the Purchasing Doc. Workflow Relevant Field Details screen, choose New Entries and entry the following
entries:
Facet for Customizing Central Contracts Fields for Customizing Central Contracts Eable
EKKO Header BEDAT X
EKKO Header BSAKZ X
EKKO Header BSART X
EKKO Header BSTYP X
EKKO Header BUKRS X
EKKO Header EKGRP X
EKKO Header EKORG X
EKKO Header INCO1 X
EKKO Header KDATB X
EKKO Header KDATE X
EKKO Header KTWRT X
EKKO Header LIFNR X
EKKO Header SPRAS X
EKKO Header WAERS X
EKPO Item LOEKZ X
EKPO Item MATKL X
EKPO_DISTR Distribution ISDELETED X
EKPO_DISTR Distribution PURCHASINGDOCUMENTDISTRPCT X
EKPO_DISTR Distribution TARGETQUANTITY X
10. Press Enter.


3.1.3.5 Version Management for Central Purchase Contracts
3.1.3.5.1 Define Number Ranges
Use
In this activity, you define the number ranges for central purchase contract versioning.
Procedure

Procurement Setting in Hub System Central Purchase
Contract Define Number Ranges
2. Choose Change Intervals.

3. On the Maintain Intervals: Purchasing document screen, create the following entry:
Field Name Entry
No 48
From No. 4800000000
Nr Status 0
Ext Leave empty
Field Name Entry
No 49
From No. 4900000000
Nr Status 0

Field Name Entry
Ext Leave empty
3.1.3.5.2 Define Number Ranges for Version Management
Use
Procedure
SAP IMG Menu Materials Management Purchasing Version

Management Configure Versioning and Reason for Version
Management Define Number Ranges for Version
Management
2. Choose Change View “Purchasing Document Type for Version-Relevant Changes” screen, create the following
entry:
Category Doc. Type Vers. Doc. Item Int. Num. Rang.
Central Contract HRMK Change Request Document 10 48
Central Contract HRMK Version History Document 10 49
Central Contract HRWK Change Request Document 10 48
Central Contract HRWK Version History Document 10 49
Central Contract HSMK Change Request Document 10 48
Central Contract HSMK Version History Document 10 49

Category Doc. Type Vers. Doc. Item Int. Num. Rang.
Central Contract HSWK Change Request Document 10 48
Central Contract HSWK Version History Document 10 49
Central Contract MK Change Request Document 10 48
Central Contract MK Version History Document 10 49
Central Contract WK Change Request Document 10 48
Central Contract WK Version History Document 10 49
3.1.3.6 Excel-Based Data Exchange
3.1.3.6.1 Define Settings for Excel-Based Data Exchange for

Central Purchase Contracts
Use
In this activity, you define the configuration settings to upload or download purchasing document information using
a Microsoft Excel file.
Procedure
SAP IMG Menu Materials Management Purchasing Excel-Based Data

Define Settings for Excel-Based Data Exchange
2. On the Change View “Business Object”: Overview screen, choose New Entries and create following settings:
Document ID Document Description
EXL_OPS_CCTR Central Purchase Contract

3. On the Change View “Business Object”: Overview screen, select the entry with Document ID EXL_OPS_CCTR,
double click Worksheet in the Dialog Structure.
4. On the Change View “Worksheet”: Overview screen, create the following entries:
Worksheet ID
WS_1
WS_2
WS_3
WS_4
WS_5
WS_6
WS_7
WS_8
5. On the Change View “Worksheet”: Overview screen, select the entry with Worksheet ID WS_1, double click
Worksheet Description in the Dialog Structure.
6. On the Change View “Worksheet Description”: Overview screen, create the following entries:
Language Worksheet ID
EN Central Contract Header
7. Double click Columns in the Dialog Structure.

8. Choose Change View “Columns” screen, create the following entry:
Seq. Key Read

Field Name Global Field Name No. Download Field Only Mandatory
AEDAT CREATIONDATE 28 X X
ANGNR SUPPLIERQUOTATION 21 X
BSART PURCHASECONTRACTTYPE 27 X X X
BUKRS COMPANYCODE 7 X X
CONTENT PURGDOCNOTETEXT 31 X
CONTRHDRISCREATED CONTRHDRISCREATED 32 X
DISTRIBUTIONTYPE CNTRLPURCONTRFLXBLDISTRISALLWD 33 X
EBELN CENTRALPURCHASECONTRACT 1 X X X
EKGRP PURCHASINGGROUP 8 X X

Seq. Key Read
EKORG PURCHASINGORGANIZATION 9 X X X
ERNAM CREATEDBYUSER 11 X X
IHRAN QUOTATIONSUBMISSIONDATE 25 X
IHREZ CORRESPNCEXTERNALREFERENCE 26 X
INCO1 INCOTERMSCLASSIFICATION 12 X
INCO2_L INCOTERMSLOCATION1 22 X
INCOV INCOTERMSVERSION 24 X
KDATB VALIDITYSTARTDATE 3 X X X
KDATE VALIDITYENDDATE 4 X X
KTWRT PURCHASECONTRACTTARGETAMOUNT 5 X
LIFNR SUPPLIER 2 X X X
PROCSTAT PURCHASINGPROCESSINGSTATUS 6 X X
RSCOD PURCHASINGDOCVERSIONREASONCODE 30 X
TELF1 SUPPLIERPHONENUMBER 29 X
UNSEZ CORRESPNCINTERNALREFERENCE 19 X
VERKF SUPPLIERRESPSALESPERSONNAME 20 X
WAERS CURRENCY 10 X X X
ZBD1P CASHDISCOUNT1PERCENT 13 X
ZBD1T CASHDISCOUNT1DAYS 14 X
ZBD3T NETPAYMENTDAYS 17 X
ZTERM PAYMENTTERMS 18 X
9. Save your entries and back to Change View “Worksheet”: Overview screen.

EN Central Contract Item

Seq. Key Read

ABMNG PURGDOCRELEASEORDERQUANTITY 6 X
BEDNR REQUIREMENTTRACKING 18 X
BORGR_MISS ISINFOATREGISTRATION 19 X
BPRME ORDERPRICEUNIT 30 X X
BSTAE SUPPLIERCONFIRMATIONCONTROLKEY 20 X
CONTRITEMISCREATED CONTRITEMISCREATED 36 X
EBELP CENTRALPURCHASECONTRACTITEM 2 X X X
EVERS SHIPPINGINSTRUCTION 21 X
IDNLF SUPPLIERMATERIALNUMBER 7 X
INSMK STOCKTYPE 35 X
KTMNG TARGETQUANTITY 5 X
KZABS ISORDERACKNRQD 22 X
LABNR PURGDOCORDERACKNNUMBER 23 X
LOEKZ PURCHASINGCONTRACTDELETIONCODE 37 X
MAHN1 NODAYSREMINDER1 24 X
MATKL MATERIALGROUP 4 X X X
MATNR MATERIAL 3 X X
MEINS ORDERQUANTITYUNIT 33 X X

Seq. Key Read
MWSKZ TAXCODE 34 X
NETPR CONTRACTNETPRICEAMOUNT 29 X X
PRODUCTTYPE PRODUCTTYPE 28 X X
PRSDR PRICEISTOBEPRINTED 27 X
REPOS INVOICEISEXPECTED 8 X
SCHPR PURGDOCESTIMATEDPRICE 9 X
TARGET_VALUE CNTRLPURCONTRITMTARGETAMOUNT 31 X
TXZ01 MATERIALDESCRIPTION 10 X
UEBTK UNLIMITEDOVERDELIVERYISALLOWED 11 X
UEBTO OVERDELIVTOLRTDLMTRATIOINPCT 12 X
UNTTO UNDERDELIVTOLRTDLMTRATIOINPCT 13 X
WAERS DOCUMENTCURRENCY 32 X X
WEBRE INVOICEISGOODSRECEIPTBASED 14 X
WEPOS GOODSRECEIPTISEXPECTED 15 X
WEUNB GOODSRECEIPTISNONVALUATED 16 X
XERSY EVALDRCPTSETTLMTISALLOWED 17 X
EN Contract Header Distribution


Seq Key
. Down Fiel Read Manda
Field Name Global Field Name No. load d Only tory
COMPANYCODE PROCMTHUBCOMPANYCODE 7 X X X
CONTRHDRDISTRISCREATED CONTRHDRDISTRISCREATED 16 X
DISTRIBUTIONNUMBER DISTRIBUTIONKEY 3 X X X
DISTRIBUTIONTYPE PURGDOCUMENTDISTRIBUTION 12
TYPE
DOCUMENTCURRENCY CURRENCY 14 X X X
ISDELETED TEXTISDELETED 17 X
PAYMENTTERMS PAYMENTTERMS 11 X X
PLANT PLANT 9 X X
PROCUREMENTHUBSOURCESYSTEM PROCUREMENTHUBSOURCESYSTEM 2 X X
PURCHASINGDOCUMENT CENTRALPURCHASECONTRACT 1 X X X
PURCHASINGDOCUMENTCATEGORY PROCMTHUBPURGDOCITMCATE 6 X X X
GORY
PURCHASINGDOCUMENTDISTRPCT CNTRLPURCONTRDISTRIBUTIONPCT 4 X X
PURCHASINGDOCUMENTTYPE PURGDOCUMENTDISTRIBUTION 12 X
TYPE
PURCHASINGGROUP PROCMTHUBPURCHASINGGROUP 5 X X X
PURCHASINGINFORECORDUPDATE PURCHASINGINFORECORDUPDATE 13 X
CODE CODE
PURCHASINGORGANIZATION PROCMTHUBPURCHASINGORG 8 X X X
SOURCELISTISUPDATED SOURCELISTISUPDATED 15 X
STORAGELOCATION STORAGELOCATION 10 X
20.On the Change View “Worksheet”: Overview screen, select the entry with Worksheet ID WS_4, double click
EN Contract Item Distribution

Seq Key
CONTRITMDISTRISCREATED CONTRITMDISTRISCREATED 19 X
DISTRIBUTIONNUMBER DISTRIBUTIONKEY 3 X X X
DISTRIBUTIONTYPE PURGDOCUMENTDISTRIBUTION 12
TYPE
PLANT PLANT 9 X X
GORY
PURCHASINGDOCUMENTITEM CENTRALPURCHASECONTRACTITEM 2 X X X
PURCHASINGDOCUMENTTYPE PURGDOCUMENTDISTRIBUTION 12 X
TYPE
CODE CODE
TARGETQUANTITY TARGETQUANTITY 11 X X
TARGETVALUE TARGETAMOUNT 18 X X

EN Central Cont. Item Pricing

Global Field
Field Name Name Seq. No. Download Key Field Read Only Mandatory
CENTRAL CENTRAL 1 X X X X
PURCHASE PURCHASE
CONTRACT CONTRACT
PURCHASE PURCHASE
CONTRACTI CONTRACTI
TEM TEM
CNDN_CHGRE CONDITION 18 X
ASON CHANGEREA
SON
CONDITION CONDITION 19 X X
CALCULATION CALCULATION
TYPENAME TYPENAME
CLASSIFICA CLASSIFICA
TIONDESC TIONDESC
CONDITIONIS CONDITIONIS 20 X
DELETED DELETED
CONDITION CONDITION 11 X X X
QUANTITY QUANTITY
QUANTITYUNIT QUANTITYUNIT
CONDITIONRA CONDITIONRA 13 X X
TEVALUE TEVALUE
CONDITIONRA CONDITIONRA 14 X X X
TEVALUEUNIT TEVALUEUNIT

Global Field
CONDITIONRE CONDITIONRE 15 X X
CORD CORD
SCALEEXISTS SCALEEXISTS
TEXT TEXT
CONDITION CONDITION 9 X X X X
TYPE TYPE
CONDITIONVA CONDITIONVA 8 X X
LIDITYEND LIDITYEND
DATE DATE
LIDITYSTART LIDITYSTART
DATE DATE
CON CON 21 X
TRITMCNDNIS TRITMCNDNIS
CREATED CREATED
PLANT PROCMTHUB 6 X X
PLANT
PROCUREMEN PROCUREMEN 5 X X
THUBSOURCE THUBSOURCE
SYSTEM SYSTEM
TXZ01 MATERIALDE 4 X X
SCRIPTION
EN Central Cont. Item Commodity

Global Field
PURCHASE PURCHASE
CONTRACT CONTRACT
PURCHASE PURCHASE
CONTRACTI CONTRACTI
TEM TEM
COMMODITY COMMODITY 12 X X X
COMMODITY COMMODITY 13 X X
NAME NAME
QUANTITY QUANTITY
COMMODITY PURG 3 X X X X
QUANTITYSEQ DOCCMMD
NUMBER TYQTYSQNTL
NUMBER
COMMODITY COMMODITYU 7 X X
QUANTITYUNIT NIT
CON CON 14 X
TRITMCMMD TRITMCMMD
TYISCREATED TYISCREATED
ISDELETED ISDELETED 15 X
PERITEM PURG 10 X X
QUANTITY DOCCMMD
TYREFDO
CITMQTY
PERITEMUNIT ITEMQUANTI 11 X X
TYUNIT
PURG PURG 16 X
DOCCMMD DOCCMMD
TYUPDATECY TYUPDATECY
CLE CLE

Global Field
PURG PURG 17 X X
DOCCMMD DOCCMMD
CLETEXT CLETEXT
SCRIPTION
VALIDITYEND PURG 9 X X
DATE DOCCMMD
TYQTYVALID
TODATE
VALIDITY PURG 8 X X
FROMDATE DOCCMMD
TYQTYVALID
FROMDATE
EN Central Contract Header Notes

Global Field
PURCHASE PURCHASE
CONTRACT CONTRACT
CONTENT PURGDOCNO 7 X
TETEXT
ISCREATED ISCREATED 8 X

Global Field
LANGUAGE PURCHASING 5 X X
DOCUMENT
NOTELAN
GUAGE
LANGUAGE LANGUAGE 6 X X
NAME NAME
NOTETYPE PURCHASING 3 X X
DOCUMENT
NOTETYPE
PURCHASING PURCHASING 4 X X
DOCUMENT DOCUMENT
NOTETITLE NOTETITLE
PURCHASING PURCHASING 2
DOCUMENT DOCUMENT
NOTEUUID NOTEUUID
EN Central Contract Item Notes
42.Double click Columns in the Dialog Structure.

Global Field
PURCHASE PURCHASE
CONTRACT CONTRACT
PURCHASE PURCHASE
CONTRACTI CONTRACTI
TEM TEM
TETEXT

Global Field
DOCUMENT
NOTELAN
GUAGE
NAME NAME
DOCUMENT
NOTETYPE
DOCUMENT DOCUMENT
NOTETITLE NOTETITLE
DOCUMENT DOCUMENT
NOTEUUID NOTEUUID
44.Save your entries.
3.1.3.6.2 Define Settings for Excel-Based Data Exchange for

Hierarchy Central Purchase Contracts
Use
In this activity, you define the configuration settings to upload or download purchasing document information using
a Microsoft Excel file.
Procedure

Define Settings for Excel-Based Data Exchange
2. On the Change View “Business Object”: Overview screen, choose New Entries and create following settings:
Document ID Document Description
EXL_OPS_HCTR Hierarchy Central Purchase Contract
3. On the Change View “Business Object”: Overview screen, select the entry with Document ID EXL_OPS_HCTR,
Worksheet ID
WS_1
WS_2
WS_3
WS_4
WS_5
WS_6
WS_7
WS_8
EN Hierarchy Central Cont. Header

Seq. Key Read

AEDAT CREATIONDATE 28 X X
ANGNR SUPPLIERQUOTATION 21 X

Seq. Key Read
BSART PURCHASECONTRACTTYPE 27 X X X
BUKRS COMPANYCODE 7 X X
CONTENT PURGDOCNOTETEXT 31 X
CONTRHDRISCREATED CONTRHDRISCREATED 32 X
DISTRIBUTIONTYPE CNTRLPURCONTRFLXBLDISTRISALLWD 33 X
EKGRP PURCHASINGGROUP 8 X X
EKORG PURCHASINGORGANIZATION 9 X X X
ERNAM CREATEDBYUSER 11 X X
IHRAN QUOTATIONSUBMISSIONDATE 25 X
IHREZ CORRESPNCEXTERNALREFERENCE 26 X
INCO1 INCOTERMSCLASSIFICATION 12 X
INCOV INCOTERMSVERSION 24 X
KDATB VALIDITYSTARTDATE 3 X X X
KDATE VALIDITYENDDATE 4 X X
KTWRT PURCHASECONTRACTTARGETAMOUNT 5 X
LIFNR SUPPLIER 2 X X X
PROCSTAT PURCHASINGPROCESSINGSTATUS 6 X X
RSCOD PURCHASINGDOCVERSIONREASONCODE 30 X
TELF1 SUPPLIERPHONENUMBER 29 X
UNSEZ CORRESPNCINTERNALREFERENCE 19 X
VERKF SUPPLIERRESPSALESPERSONNAME 20 X
WAERS CURRENCY 10 X X X

Seq. Key Read
ZBD3T NETPAYMENTDAYS 17 X
ZTERM PAYMENTTERMS 18 X
EN Hierarchy Central Cont. Item

Seq. Key Read

ABMNG PURGDOCRELEASEORDERQUANTITY 6 X
BEDNR REQUIREMENTTRACKING 18 X
BORGR_MISS ISINFOATREGISTRATION 19 X
BPRME ORDERPRICEUNIT 30 X X
BSTAE SUPPLIERCONFIRMATIONCONTROLKEY 20 X
CONTRITEMISCREATED CONTRITEMISCREATED 36 X
EBELP CENTRALPURCHASECONTRACTITEM 2 X X X
EVERS SHIPPINGINSTRUCTION 21 X
IDNLF SUPPLIERMATERIALNUMBER 7 X
INSMK STOCKTYPE 35 X

Seq. Key Read
KTMNG TARGETQUANTITY 5 X
KZABS ISORDERACKNRQD 22 X
LABNR PURGDOCORDERACKNNUMBER 23 X
LOEKZ PURCHASINGCONTRACTDELETIONCODE 37 X
MATKL MATERIALGROUP 4 X X X
MEINS ORDERQUANTITYUNIT 33 X X
MWSKZ TAXCODE 34 X
NETPR CONTRACTNETPRICEAMOUNT 29 X X
PRODUCTTYPE PRODUCTTYPECODE 28 X X
PRSDR PRICEISTOBEPRINTED 27 X
REPOS INVOICEISEXPECTED 8 X
SCHPR PURCHASINGPRICEISESTIMATED 9 X
TARGET_VALUE CNTRLPURCONTRITMTARGETAMOUNT 31 X
TXZ01 MATERIALDESCRIPTION 10 X
UEBTK UNLIMITEDOVERDELIVERYISALLOWED 11 X
UEBTO OVERDELIVTOLRTDLMTRATIOINPCT 12 X
UNTTO UNDERDELIVTOLRTDLMTRATIOINPCT 13 X
WAERS DOCUMENTCURRENCY 32 X X
WEBRE INVOICEISGOODSRECEIPTBASED 14 X
WEPOS GOODSRECEIPTISEXPECTED 15 X
WEUNB GOODSRECEIPTISNONVALUATED 16 X

Seq. Key Read
XERSY EVALDRCPTSETTLMTISALLOWED 17 X
EN Hierarchy Cont. Header Dist.

Seq Key
CONTRHDRDISTRISCREATED CONTRHDRDISTRISCREATED 17 X
DISTRIBUTIONNUMBER PURGDOCITEMDISTRIBUTIONKEY 3 X X X
GROUPINGID PROCMTHUBCOMPANYCODEGROU 8 X X X
PINGID
PLANT PLANT 10 X X
GORY
PURCHASINGDOCUMENTTYPE PURCHASINGDOCUMENTTYPE 13 X

Seq Key
CODE CODE
EN Hierarchy Cont. Item Dist.

Seq Key
CONTRITMDISTRISCREATED CONTRITMDISTRISCREATED 20 X
DISTRIBUTIONNUMBER PURGDOCITEMDISTRIBUTIONKEY 3 X X X
GROUPINGID PROCMTHUBCOMPANYCODEGROU 8 X X X
PINGID
PLANT PLANT 10 X X

Seq Key
GORY
PURCHASINGDOCUMENTITEM CENTRALPURCHASECONTRACTITEM 2 X X X
PURCHASINGDOCUMENTTYPE PURCHASINGDOCUMENTTYPE 13 X
CODE CODE
TARGETQUANTITY TARGETQUANTITY 12 X X
TARGETVALUE TARGETAMOUNT 19 X X
EN Hierarchy Cont. Item Pricing

Global Field
PURCHASE PURCHASE
CONTRACT CONTRACT

Global Field
PURCHASE PURCHASE
CONTRACTI CONTRACTI
TEM TEM
CNDN_CHGRE CONDITION 18 X
ASON CHANGEREA
SON
CALCULATION CALCULATION
TYPENAME TYPENAME
CLASSIFICA CLASSIFICA
TIONDESC TIONDESC
CONDITIONIS CONDITIONIS 20 X
DELETED DELETED
QUANTITY QUANTITY
QUANTITYUNIT QUANTITYUNIT
CONDITIONRA CONDITIONRA 13 X X
TEVALUE TEVALUE
CONDITIONRA CONDITIONRA 14 X X X
TEVALUEUNIT TEVALUEUNIT
CONDITIONRE CONDITIONRE 15 X X
CORD CORD
SCALEEXISTS SCALEEXISTS
TEXT TEXT
CONDITION CONDITION 9 X X X X
TYPE TYPE
LIDITYEND LIDITYEND
DATE DATE

Global Field
LIDITYSTART LIDITYSTART
DATE DATE
CON CON 21 X
TRITMCNDNIS TRITMCNDNIS
CREATED CREATED
PLANT PROCMTHUB 6 X X
PLANT
PROCUREMEN PROCUREMEN 5 X X
THUBSOURCE THUBSOURCE
SYSTEM SYSTEM
SCRIPTION
EN Hierarchy Cont. Item Commodity

Global Field
PURCHASE PURCHASE
CONTRACT CONTRACT
PURCHASE PURCHASE
CONTRACTI CONTRACTI
TEM TEM
COMMODITY COMMODITY 12 X X X

Global Field
NAME NAME
QUANTITY QUANTITY
COMMODITY PURG 3 X X X X
QUANTITYSEQ DOCCMMD
NUMBER TYQTYSQNTL
NUMBER
COMMODITY COMMODITYU 7 X X
QUANTITYUNIT NIT
CON CON 14 X
TRITMCMMD TRITMCMMD
TYISCREATED TYISCREATED
PERITEM PURG 10 X X
QUANTITY DOCCMMD
TYREFDO
CITMQTY
PERITEMUNIT ITEMQUANTI 11 X X
TYUNIT
PURG PURG 16 X
DOCCMMD DOCCMMD
CLE CLE
PURG PURG 17 X X
DOCCMMD DOCCMMD
CLETEXT CLETEXT
SCRIPTION
VALIDITYEND PURG 9 X X
DATE DOCCMMD
TYQTYVALID
TODATE

Global Field
VALIDITY PURG 8 X X
FROMDATE DOCCMMD
TYQTYVALID
FROMDATE
EN Hierarchy Cont. Header Notes

Global Field
PURCHASE PURCHASE
CONTRACT CONTRACT
TETEXT
DOCUMENT
NOTELAN
GUAGE
NAME NAME
DOCUMENT
NOTETYPE
DOCUMENT DOCUMENT
NOTETITLE NOTETITLE

Global Field
DOCUMENT DOCUMENT
NOTEUUID NOTEUUID
EN Hierarchy Cont. Item Notes
42.Double click Columns in the Dialog Structure.

Global Field
PURCHASE PURCHASE
CONTRACT CONTRACT
PURCHASE PURCHASE
CONTRACTI CONTRACTI
TEM TEM
TETEXT
DOCUMENT
NOTELAN
GUAGE
NAME NAME
DOCUMENT
NOTETYPE

Global Field
DOCUMENT DOCUMENT
NOTETITLE NOTETITLE
DOCUMENT DOCUMENT
NOTEUUID NOTEUUID
44.Save your entries.
3.1.3.6.3 Define Technical Settings for Excel-Based Data

Exchange for Central Purchase Contracts
Use
In this activity, you define the technical settings required to download procurement information using an Excel file.
Procedure

Define Technical Settings for Excel-Based Data
2. On the Change View “Business Object”: Overview screen, select the entry with Document ID EXL_OPS_CCTR,
Worksheet ID CDS Name Method Name Class Name Hierarchy Notation
WS_1 C_PURCNTRLCONTR CCTR_HEADER_GET CL_MM_MASS_OPS_C 1.0

MASSUPDT DATA CTR
WS_2 C_PURCNTRLCON CCTR_ITEM_GETDATA CL_MM_MASS_OPS_C 1.1

TRITMMASSUPDT CTR

WS_3 C_CNTRLPUR CCTR_HDRDISTRIBU CL_MM_MASS_OPS_C 1.2

CONTRHDRDISTR TION_GETDATA CTR
WS_4 C_CNTRLPURCON CCTR_ITEMDISTRIBU CL_MM_MASS_OPS_C 1.1.1

TRITMDISTR TION_GETDATA CTR
WS_5 C_CEPUCOITMCNDN CCTR_ITEMCONDI CL_MM_MASS_OPS_C 1.1.2

MASSUPDT TION_GETDATA CTR
WS_6 C_CEPUCOITMCMMD CCTR_ITEM CL_MM_MASS_OPS_C 1.1.3

TYMASSUPDT CMMDTY_GETDATA CTR
WS_7 C_CEPUCOHDRNO CCTR_HEADER CL_MM_MASS_OPS_C 1.3

TESFORMASSUPDT NOTES_GETDATA CTR
WS_8 C_CEPUCOITMNO CCTR_ITEM CL_MM_MASS_OPS_C 1.1.4

TESFORMASSUPDT NOTES_GETDATA CTR
4. Save your entries and back to Change View “ Business Object ”: Overview screen.
5. On the Change View “Business Object”: Overview screen, select the entry with Document ID EXL_OPS_HCTR,
WS_1 C_CNTRLPURCONTR HCTR_HEADER_GET CL_MM_MASS_OPS_H 1.0

HIERMASSUPDT DATA CTR
WS_2 C_CNTRLPURCONTR HCTR_ITEM_GETDATA CL_MM_MASS_OPS_H 1.1

HIERITMMASSUPDT CTR
WS_3 C_CPURCON HCTR_HDRDISTRIBU CL_MM_MASS_OPS_H 1.2

HIERHDRDISTRMAS TION_GETDATA CTR
SUPDT
WS_4 C_CPURCONHIERITM HCTR_ITEMDISTRIBU CL_MM_MASS_OPS_H 1.1.1

DISTRMASSUPDT TION_GETDATA CTR
WS_5 C_CPURCONHIER HCTR_ITEMCONDI CL_MM_MASS_OPS_H 1.1.2

ITMCNDNMASSUPDT TION_GETDATA CTR
WS_6 C_CPURCONHIER HCTR_ITEM CL_MM_MASS_OPS_H 1.1.3

ITMCMMDTYMAS CMMDTY_GETDATA CTR
SUPDT
WS_7 C_CEPUCOHIERHDR HCTR_HEADER CL_MM_MASS_OPS_H 1.3

NOTESMASSUPDT NOTES_GETDATA CTR

WS_8 C_CEPUCOHIERITM HCTR_ITEM CL_MM_MASS_OPS_H 1.1.4

NOTESMASSUPDT NOTES_GETDATA CTR
3.2 Configure Communication from Hub system to Connected

System
3.2.1 Create RFC
Use
In this activity, you create the RFC for the Connected System.
Procedure
1. Login into the S/4HANA Hub system and execute transaction SM59.
2. Choose Create.
3. In 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>
Under Technical Settings Tab, enter the following entries:
• Host: <Host of the Connected System>
• Port: <HTTPS Port>
• Path Prefix: /sap/opu/odata/sap/?sap-client=<Client of Connected System>
Under Logon & Security Tab, enter the following entries:
• Basic authentication: X
• Language: <Your Language>
• Client: <Client of Connected System>

• User: <User>
• Password: <Password>
In Security Options area, enter the following entries:
• SSL: Active
• SSL Certificate: <Select the SSL Certificate>
4. Choose Save.
3.2.2 Create Logical System
Use
In this activity, you create the logical system for the Connected System.
Procedure
1. Login into the S/4HANA Hub system and execute transaction BD54.
2. Confirm the Information dialog box, and then choose New Entries.
3. In 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.
3.2.3 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. Login into 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.
3.2.4 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.
3.3 S/4HANA Hub System Configuration Steps

3.3.1 Active 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: check
4. Choose Save.
5. In dialog box which show 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: check
8. Choose Save.
3.3.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 step Create Logical System [page 71]
4. Choose Save.
3.3.3 Assign Connected Systems to RFC Destinations
Use
In this activity, you can assign connected systems to RFC destinations.
Procecure
1. Log on to the S/4HANA Hub system and execute transaction SPRO.

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 73]
• RFC Destination: The RFC destination defined in the step Create RFC [page 70]
4. Choose Save.

3.3.4 Configure Control Plane for the APIs of Central
Procurement
Use
In this activity, you can configure the control plane for the APIs of central procurement 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:
 Note
The connected system ID is defined in the step Define Connected System [page 73].
Connect Bound Operati Messag API Name API API Driver Activa
ed ed on e Versio te
System Contex Protoc n Driver
ID t ol
con CCM 2AH ODATA MM_PUR_CCTR_ARCHIVE_SRV 1 CL_MMPUR_CENTRL_CTR_D check

nected Archive RIVER
system Local
ID Con
tracts
con CCM 2CD ODATA MM_PUR_CCTR_CHECK_SRV 1 CL_MMPUR_CENTRL_CTR_D check

nected Central RIVER
system Con
ID tract
Check
Distri
bution

con CCM 2DI SOAP PURCHASECONTRACTDISTRIBU 1 CL_MMPUR_CENTRL_CTR_D check
nected Central TIONREPLICATIONREQUEST_IN RIVER
system Con
ID tract
Distrib
ute
con CCM 2ED ODATA MM_PUR_OA_EDITABILITY_SRV 1 CL_MMPUR_CENTRL_CTR_D check

nected Outline RIVER
system Agree
ID ment
Edita
bility
con CCM 2OM ODATA MM_PUR_CPROC_OPS_MNTR_CC 1 CL_MMPUR_CENTRL_CTR_D check

nected Central TR_BE_SRV RIVER
system Pro
ID cure
ment
Opera
tions
Moni
tor for
CCM
con CCM 2RD ODATA MM_PUR_CCTR_CALLOFF_SRV 1 CL_MMPUR_CENTRL_CTR_D check

system Con
ID tract
Read
Re
lease
Info
con CCM 2RM ODATA MMPUR_BE_VALUE_HELP_SRV 1 CL_MMPUR_CENTRL_CTR_D check

system Con
ID tract
Read
Mate
rial

con CCM 2RR ODATA MMPUR_CCTR_BE_SRV 1 CL_MMPUR_CENTRL_CTR_D check
system Con
ID tract
Read
Re
lated
Infor
mation
con CCM 2SL SOAP SOURCELISTCHANGEREQUEST_IN 1 CL_MMPUR_CENTRL_CTR_D check

nected Source RIVER
system List
ID Update
4. Choose Save.
3.3.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
• Active: check

 Note
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
• Active: check
 Note
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
• Active: check
 Note
The Purch Org ID is a unique ID that represents the combination of Connected Purchasing Organization
and Connected System.
10. Choose Save.
3.3.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
• Register: check
 Note
The Company Code ID is a unique ID that represents the combination of Connected Company Code and
Connected System.
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
• Register: check
 Note
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

• Register: check
 Note
The Purch Org ID is a unique ID that represents the combination of Connected Purchasing Organization
and Connected System.
12. Choose Save.
3.3.7 Define Grouping of Company Codes of Connected

Systems
Use
In this activity, you define group 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
You can add required connected company codes to the group.
7. Choose Save.

3.3.8 Maintain Reasons for Blocking Central Purchase Contract
Items
Use
In this activity, you can maintain reasons for blocking a central purchase contract item at the item and item
distribution levels.
Procedure
1. Log 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 > Central Purchase Contract > Maintain Reasons for Blocking Central
Purchase Contract Items
3. On the change view "Block reason codes": Overview screen, choose New Entries and then make the following
entries:
• Block Reason Code: Your block reason code
• Block Reason Description: Your block reason description
4. Choose Save.
3.3.9 Define Conditions to Restart Central Purchase Contract

Processes
Use
In this activity, you can define conditions based on the purchasing document types to restart processes, such as
the flexible workflow, for central purchase contracts and central purchase contract hierarchies.
In this configuration step, you can select various attributes for central purchase contracts or central purchase
contract hierarchies that are relevant for the restart of the flexible workflow. Whenever you update the values of
these attributes in an approved document, the system triggers a restart of the approval process.

Procedure
Procurement- Settings in Hub System > Central Purchase Contract > Define Conditions to Restart Central
Purchase Contract Processes
3. On the change view "Define Conditions to Restart Central Purchase Contract Processes": Overview screen,
choose New Entries and then make the following entries:
• Category: Your Central Purchase Contract Doc Category
• Doc. Type: Your Doc Type for Central Purchase Contract
• Activate: check
4. On the change view "Define Conditions to Restart Central Purch": Overview screen, choose the Purchasing
Document Details you created and double click Purchasing Doc. Workflow Relevant Field Details in Dialog
Structure.
5. On the change view "Purchasing Doc. Workflow Relevant Field Details ": Overview screen, choose New Entries
and then make the following entries:
• Facet for Customizing Central Contract: Your Facet for Customizing Central Contract
• Fields for Customizing Central Contract: Your Fields for Customizing Central Contract
• Enable: check
6. Choose Save.
3.3.10 Configure Fields for Editability of Purchase Outline

Agreements
3.3.10.1 Maintain Fields for Editability of Purchase Outline

Agreements
Use
In this activity, you can make specific fields editable at the header and item levels of purchase outline agreements
created locally from the connected system.

Procedure
Procurement- Settings in Hub System > Central Purchase Contract > Maintain Fields for Editability of Purchase
Outline Agreements
3. On the change view "Maintainace View for Field Editablility": Overview screen, choose New Entries and then
make the following entries:
• Connected System: Your Connected System ID
• Table: Header or Item for Outline Agreements
• Field: field in Header or Item table
• Editable for Contract: check
• Editable for Scheduling Agreement: check
4. Choose Save.
3.3.10.2 Schedule Replication Config Data to Connected

System
Use
In this activity, you schedule job to replicate config data from S/4HANA Central Procurement hub system to
connected system.
Procedure
1. Log onto 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 Replication Config Data to Connected
System 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: Application job template for outline agreement field editability
• Job Name: <Your Job Name>, for example, Application job for outline agreement field
editability
5. Scheduling Options is by default set to Start immediately. To change the Scheduling Options, choose
Define Recurrence Pattern.
6. On the Scheduling Information screen, choose the required option and maintain the fields accordingly and
confirm with OK.

7. Choose Step 3 , make the following entries:
Connected System ID: <Your Connected System ID> or ALL for all connected systems
8. Choose Schedule and check the Application Jobs screen for the scheduled job and once the status is displayed
as finished, then the job is complete.
3.3.11 Activate Item Hierarchies in Central Procurement
Use
You can use item hierarchies in central procurement to structure and sort items, such as materials or services, in a
hierarchy。
In this activity, you can activate the item hierarchy function for central purchase contracts.
In a standard system this function is turned off.
Procedure
Procurement- Settings in Hub System > Activate Item Hierarchies in Central Procurement
3. On the Display/Change Switch State of Lightweight Business screen, choose Change Statue.
3.3.12 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.
3.3.13 Deactivate Batch Parallelization for Mass Changes to

Central Purchase Contracts
Use
For exporting Excel from Mass Changes to Central Contracts app, Batch Parallelization needs to be deactivated for
service MM_PUR_CNTRLCTRMASS_UPDT_SRV.
Procedure
1. Log on to the S/4HANA Hub system and execute transaction /n/IWBEP/CONF_SERVICE.

2. In the Service field, enter the service MM_PUR_CNTRLCTRMASS_UPDT_SRV and choose Execute.
3. On the Change Configuration screen, check Deactivate Parallelization of Batch Request.
4. Choose Save.
3.3.14 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.

3.3.14.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
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
3. On the Change View “Versioning Maintenance View for Reason Codes” Overview screen, choose New Entries
• Reason: Your Reason, for example: 01
• Reason Description: Your Reason Description, for example: documentation issues
4. Choose Save.
3.3.14.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:
• Activate version management
If version management is active, changes to a purchasing document are managed in versions.
• 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 Purcahsing Docurement Field Details
in Dialog Structure.
6. On the change view " Purcahsing Docurement Field Details ": Overview screen, choose New Entries and then
• 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.
3.3.15 Configure Commodity Pricing for Central Purchase

Contracts
With Commodity Pricing you can apply complex pricing formulas, rules and conditions in an easy way.
 Note
For using Commodity Procurement, you must have activated the following business functions.
• LOG_CPE_SD_MM
• LOG_CMM_PRC_BF_CCTR_CPE_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.

3.3.15.1 Pricing Configuration
3.3.15.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.
3.3.15.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
• Condition Type: ZPR0 Default Gross Price
5. Choose Copy.
6. Choose Save.
3.3.15.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 Contral data in
Dialog Structure.
9. On the Change View "Contral 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 Contral data in
Dialog Structure.
19. On the Change View "Contral 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.
3.3.15.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.

3.3.15.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.
3.3.15.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.
3.3.15.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

3.3.15.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 C omponent 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
3.3.15.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
• 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.
3.3.15.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
2. Navigate to configuration activity: SAP Reference IMG Materials Management Purchasing Commodity
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.
3.3.15.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
• 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: 70 Cmdty Quantities in Centr. Purch. Contr.

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.
3.3.15.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 (Text): your commodity name, for example: Silver
• UoM: your unit of measure, for example: KG
4. Choose Save.
3.3.15.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): your condition type, for example: ZCMM
• Commodity: your commodity code , for example: AG
4. Choose Save.
3.3.15.9 Define Additional Commodity Settings
Use
In this activity, you can specify the update cycle that defines the frequency of the creation of new condition records
for the central contract.
Procedure
Procurement- Settings in Hub System > Central Purchase Contract> Define Additional Commodity Settings .
3. On the Change View "Additional Commodity Settings for Central Procurement": Overview screen, choose New
Entries and make the following entries:
• Commodity: your commodity code, for example: AG
• Cycle Ind.: your cycle indicator for commodity update, for example: 1 Monthly
4. Choose Save.

3.3.16 Configure Header Condition for Central Purchase
Contracts
3.3.16.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 enter 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.
3.3.16.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 Contral data in
Dialog Structure.
4. On the Change View “Contral data”: Overview screen, choose New Entries and then enter the following entries:
• Step: 990
• Condition Type: ZRA1
5. Choose Save.
3.3.17 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.

3.3.18 Maintain Change Reasions for Conditions
Use
In this activity, you configure the reasons from the search help when a new condition is added, changed, or deleted
for the document.
Procedure
Define Price Determination Processes Define Change Reasons for Conditions
3. On the Change View “Change Reason Code”: Overview screen, choose New Entries and then enter the following
entries:
• Reason: <Your reason code>
• Description: <Your reason description>
4. Choose Save.
3.4 UI Integration
UI integration enables the central purchaser to navigate from S/4HANA Hub system to connectedsystem and
perform actions like editing purchase requisition and purchase order and so on.
 Note
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

3.4.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.
3.4.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.

3.4.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)
• 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.

3.4.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 HTTPS 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)
• Host: <HTTP Host of Connected System>
• Port: <HTTP Port of Connected System>
On the Security Options tab, make the following entries:
• SSL: Inactive
4. Choose Save.
3.4.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 101].
• Software Version: DEFAULT
• System ID: <Your Connected System ID>
• Client: <Your Connected System Client>
4. Choose Save.
3.4.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 77].
4. Choose Save.

3.4.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 104].
• Target System Alias: <Connected System> of the RFC Destination with connection type H created in the
step Create RFC destination of type HTTP Connection to ABAP system for HTTPS connection [page 102],
for example, XXXCLNTYYY (XXX: System ID, YYY: Client)
4. Choose Save.
3.4.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.
3.4.2 Configure Destination for Own System on Embeded

System
 Note
The configuration steps in this chapter is only required if embedded Fiori deployment is used on your SAP S/
4HANA system.
You need to carry out the following steps in this chapter:
• Create ABAP/HTTP(S) connections for own system (SM59)

• Create system alias mapping for S4PRC
HTTP connection and HTTPS connection can be configured based on your security policy.
3.4.2.1 Create RFC Destination of Type ABAP Connection
Use
In this activity, you create RFC destination of type ABAP connection for the connected system.
Procedure
2. Choose Create.
3. Under RFC Destination screen, make the following entries:
• RFC Destination: <Connected System>_RFC, for example, XXXCLNTYYY_RFC (XXX: System ID,
YYY: Client)
• Connection Type: 3
Under Technical Settings tab, make the following entries:
• Target Host: <Host of the Connected System>

• Instance No.: <Instance number of Connected System>
Under Logon & Security tab, make the following entries:
4. Choose Save.
3.4.2.2 Create RFC Destination of Type HTTP Connection for

HTTPS Connection
Use
In this activity, you create the RFC destination of type HTTP connection to ABAP system for HTTPS connection for
Own System. Based on your security policy. If HTTP connection is used, you can skip this step.
Procedure
1. Log on to the SAP S/4HANA Fiori frontend system and execute transaction SM59.
2. Choose Create.
3. Under RFC Destination screen, make the following entries:
• RFC Destination: <Own System>_HTTPS, for example, XXXCLNTYYY_HTTPS (XXX: System ID, YYY:
Client)
Under Technical Settings tab, make the following entries:
• Host: <HTTPS Host of Own System>
• Port: <HTTPS Port of Own System>
Under Logon & Security tab, make the following entries:
• Client: <Client of Own System>
Under Security Options tab, make the following entries:
• SSL: Active
• SSL Certificate: DEFAULT SSL Client (Standard)
4. Choose Save.

3.4.2.3 Create RFC Destination of Type HTTP Connection for
HTTP Connection
Use
In this activity, you create the RFC destination of type HTTP connection to ABAP system for HTTP connection for
Own System. Based on your security policy. If HTTPS connection is used, you can skip this step.
Procedure
1. Log on to the SAP S/4HANA Fiori frontend system and execute transaction SM59.
2. Choose Create.
3. Under the RFC Destination screen, make the following entries:
• RFC Destination: <Own System>_HTTP, for example, XXXCLNTYYY_HTTP (XXX: System ID, YYY:
Client)
Under the Technical Settings tab, make the following entries:
• Host: <HTTP Host of Own System>
• Port: <HTTP Port of Own System>
Under the Logon & Security tab, make the following entries:
Under the Security Options tab, make the following entry:
• SSL: Inactive
4. Choose Save.
3.4.2.4 Configure System Alias Mapping
Use
In this activity, you create the system alias mapping for S4PRC.

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 System Alias: S4PRC
• Target System Alias: <Own System> of the RFC Destination with connection type H created in the step
Create RFC Destination of Type HTTP Connection for HTTPS Connection [page 107], for example,
XXXCLNTYYY (XXX: System ID, YYY: Client)
4. Choose Save.
3.5 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 central
purchase contract scenarios.
• Ability to process Central Purchase Contract with various suppliers across the connected systems
3.5.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
3.5.2 Manage Key Mapping for Material
Use
In this activity, you can create, edit, or delete key mapping information for Material, 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. Log onto the Fiori launchpad with user that has the role template ADMINISTRATOR_DATA_REPL.
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: Product
• Business System: Logical System for S/4HANA Hub System
• Object ID Type: your material ID type
• Object ID: your material 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: your material ID type in connected system

• Object ID: your material ID in connected system
3.6 Master Data
To create a central purchase contract in SAP S/4HANA 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.
• Pricing Schema
• Inco-terms
• Payment Terms
• Unit of Measures
• Currency
• Tax code
3.7 Extend Central Purchase Contract using BADIs
The following BADI's 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
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
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 distrib-
uted 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 out-line 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.
● MM_PUR_S4_CCTR_WF_TRGGR : Restart of Flexible Workflow for 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 restart the flexible workflow for the application Manage Central Purchase Contracts when
central purchase contracts are modified. This BADI provides the capability to overrule the configuration to restart
the flexible workflow for central purchase contracts.
● MM_PUR_S4_CCTR_PRINT_PREVIEW : Define Criteria for Editability of Central Contracts in SAP S/4HANA

System
This Business Add-In (BAdI) is used to define criteria for the editability of central purchase contracts created from
external systems (such as SAP Ariba) in the SAP S/4HANA system. By default, you cannot edit a central purchase
contract in the SAP S/4HANA landscape that is created from an external system. However, with the
implementation of this BAdI, you can edit central purchase contracts in the SAP S/4HANA landscape.

3.8 Central Procurement Operations Monitor – Central
Contract Management Scenario
3.8.1 Monitor Connected System Status
3.8.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 .
Procedure
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.
3.8.1.2 Monitor Connected System Status
Purpose
You can use the Central Procurement Operations Monitor application to monitor connected system status.

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 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 detal Connected System and System Status.
3.8.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.

4 Configure the Connected System
The necessary steps which is needed in the Connected System.
4.1 ERP or S/4HANA On-premise as Connected System
4.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.
 Note
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 .
4.1.2 Configure OData Services
Use
In this activity, the following OData Services need to be registered in the connected system.
• 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.

Configure the Connected System PUBLIC 115
• 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.
• Outline agreement editibilty: MM_PUR_OA_EDITABILITY_SRV
This OData service enables you to configure the connected systems for the editability of the distributed outline
agreements.
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) .
4.1.3 Cleaning 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.

116 PUBLIC Configure the Connected System
Procedure
To clear the cache for gateway in the connected system, perform the following steps:
1. Log onto the connected system and enter transaction /N/IWFND/CACHE_CLEANUP.

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.
4.1.4 Configure Batch Parallelization for Gateway
Use
A parallelization of consecutive queries in a batch request is used to optimize the performance of the batch request
processing.
When a user requests for Catalog extraction, multiple batch requests are sent to the connected system. For
performance optimization, we recommend the user to activate batch parallelization for Gateway in the connected
system.
Configuration Parameters
The following parameters are valid for the current SAP client:
• "Activate Parallelization for Batch Queries": Mark or unmark this option to enable or disable the parallelization.
• "Maximum Number of Parallel Queries": Specify the maximum number to limit the amount of parallel
processing queries to save system resources.
Procedure
To configure the batch parallelization for gateway in the connected system, perform the following steps:
1. Log onto the connected system and enter transaction SPRO.

2. Navigate to the configuration activity: SAP NetWeaver Gateway Service Enablement Back-end OData
Channel Configuration Settings Define Parallelization of Batch Queries .
3. Check the Activate Parallelization for Batch Queries checkbox.
4. Choose Save.
Result
Performance Optimization

In case of serialization, the duration of the consecutive queries is the sum of all query processing times. Contrary to
this, the total duration in the parallel mode is just the maximum duration of these query processing times and a
minimal overhead for parallelization.
4.1.5 Configure User-Defined Search
4.1.5.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.
 Note
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
PurchaseContractConfirmationand 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.
 Note
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 .
4.1.5.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
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.

 Note
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.
4.1.6 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.
4.2 S/4HANA Cloud as Connected System

4.2.1 SAP Cloud Connector Installation and Configuration
Setting Up Integration with On-Premise Systems (including SAP S/4HANA

Cloud, private edition)
For all scenarios integrating SAP S/4HANA Cloud with SAP On-Premise scenarios, the SAP_COM_0574 – SAP BTP
Connectivity Service - On Premise Integration communication arrangement must be activated. This is a prerequisite
for all other communication arrangements.
To check if the SAP_COM_0574 – SAP BTP Connectivity Service - On Premise Integration communication
arrangement is active in your system, go to the 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.
 Note
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 whitelists for its access control.
Add following permitted URL paths (Resources) in accessible resource.
• /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
4.2.2 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 user.

4.2.2.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.
4.2.2.2 Create Communication Systems
Use
In this activity, you create the communication system for the S/4HANA On-premise hub system. This enables data
exchange between the connected S/4HANA Cloud system and the S/4HANA On-premise Hub system.
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
 Note
Make a note of this name as it is required in later steps
5. In the General Data area, retain the default system name.

6. In the Technical Data area, maintain the values for following fields:
Table 2:
Fields Values
Host Name The virtual host name for the S/4HANA On-premise hub sys
tem maintained in cloud connector
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:
Table 3:
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 123]. 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 On-premise Hub system. Confirm with Create.
12. Choose Save.

4.2.2.3 Create Communication Arrangements for Central
Procurement Foundation Layer
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_0587 (SAP S/4HANA Procurement Hub - Foundation Layer Hub Integration)
• Arrangement Name: Your Communication Arrangement Name
5. On the Communication Arrangements screen, make the following entries and then choose Save:
Communication System: Maintain the communication system ID defined under
6. Choose Save.
4.2.2.4 Create Communication Arrangements for Central

Purchase Contract
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_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 Create Communication
Systems [page 123]
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.
4.2.3 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.

5 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 Operation 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

Monitoring and Error Handling PUBLIC 127
6 Appendix
6.1 Known Restrictions
The following are the known restrictions of the Central Purchase Contracts scenario:
• Central Contract item with Account Assignment Category – Unknow (U) is only supported.
• Contract item with item category ‘Standard’ is only supported
• Purchasing document types MK, WK are only supported (Quantity Contract, Value Contract)
Manage Central Contract application supports Contract Types “Quantity Contract” and “Value Contract” only.
During distribution, if Contract is selected as Outline Agreement category, the contract type entered at the
header information of the central contract is copied to Outline Agreement type. If Scheduling agreement is
selected as Outline Agreement category, user can select Outline agreement type based on connected system
using search help.
• Creation of Attachments, Partners is not supported
6.2 Support
If you encounter errors with the integration content, please open a customer ticket on the component MM-PUR-
HUB-CTR.

128 PUBLIC Appendix
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.

Important Disclaimers and Legal Information PUBLIC 129
www.sap.com/contactsap
© 2022 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

2ME S4HANA2022 Set-Up EN XX

Uploaded by

Copyright:

Available Formats

2ME S4HANA2022 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

2ME S4HANA2022 Set-Up EN XX

Uploaded by

Copyright:

Available Formats

Set-Up Instructions | PUBLIC

Setting Up Central Purchase Contracts (2ME)

THE BEST RUN

3 Configure the S/4HANA Hub System on On-Premise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Setting Up Central Purchase Contracts (2ME)

4 Configure the Connected System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

5 Monitoring and Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Setting Up Central Purchase Contracts (2ME)

Setting Up Central Purchase Contracts (2ME)

2.1 Important Definitions

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

Any SAP S/4HANA Cloud 2208 and higher release is consid­

2491065 - Release Information Note for HUBERPI Inte­

2573672 - Release Information Note to Enable SAP S/

Setting Up Central Purchase Contracts (2ME)

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

2.1.1 Business Roles

Setting Up Central Purchase Contracts (2ME)

3.1 Configure Best Practices Content

3.1.1 Central Procurement -General Configuration (2C8)

3.1.1.1 Manage Notification Providers

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

Setting Up Central Purchase Contracts (2ME)

Transaction Code SPRO

Notification Provider ID Is Active?

3. Save your entries.

3.1.1.2 Activation of Scope-Dependent Application Job

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

SAP IMG Menu ABAP Platform Application Server System

Transaction Code SPRO

Application job scope

3. Save your entries.

Setting Up Central Purchase Contracts (2ME)

3.1.1.3.1 Define Functions

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

SAP IMG Menu Cross-Application Components General Application

Transaction Code SPRO

3. Save your entries.

3.1.1.3.2 Define Function Profiles

Setting Up Central Purchase Contracts (2ME)

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

SAP IMG Menu Cross-Application Components General Application

3. Save your entries.

5. Save your entries.

3.1.1.3.3 Assign Function Profiles to Standard Team Category

In this activity, you can assign a function profile to a team category.

Setting Up Central Purchase Contracts (2ME)

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

SAP IMG Menu Cross-Application Components General Application

CPROC SCPRC Central

3. Save your entries.

3.1.1.3.4 Define Team Types

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

SAP IMG Menu Cross-Application Components General Application

Setting Up Central Purchase Contracts (2ME)

SCPRC CPROC Central

3. Save your entries.

3.1.1.4 Define DMS Document Type for Document

1. Access the transaction using the following transaction:

Any SAP S/4HANA Cloud 2208 and higher release is consid

2491065 - Release Information Note for HUBERPI Inte

Field selection ..................................*+...........+...+................

Field selection ........*.***............................+.+.........**.

Field selection .***..-.............**.............................*.........C