1VP Set-Up EN XX
1VP Set-Up EN XX
1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 Required Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1 Configuration in SAP Cloud for Customer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Log On and User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Project Scoping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Define Business Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Master Data Preparation Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Set Up Communication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Adjust Mashup URL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
ID Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configure Communication Arrangements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configure Opportunity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configure Organizational Work Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Code List Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
End of Purpose - Blocking of Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Configure Customer Insights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.2 Configuration in SAP S/4HANA Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
How to Get the SAP S/4HANA Cloud Public Edition System URL. . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Configuration of Channel Binding for Enterprise Event Enablement. . . . . . . . . . . . . . . . . . . . . . . . . 54
Authorizations for INTERNAL_SALES_REP in SAP S/4HANA Cloud Public Edition. . . . . . . . . . . . . . . 55
Configuration for Filter Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Configuration for Business Partner End of Purpose - ILM Settings for Data Protection. . . . . . . . . . . . 58
Self-Service Configuration UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.3 Configuration in SAP Event Mesh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.4 Configuration in SAP Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
How to Get the SAP Cloud Integration runtime URL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
How to Get the SAP Cloud Integration (SCI) Client Certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Upload Client Certificates for Authentication in SAP Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . 63
Copy Integration Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Configure and Deploy the iFlows Using Web UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.1 Message Monitoring in SAP S/4HANA Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Assign the Message Monitoring Authorizations to INTERNAL_SALES_REP. . . . . . . . . . . . . . . . . . . . 87
Monitor Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.2 Ticket Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
6.3 System ID for SAP S/4HANA Cloud Public Edition System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
6.4 Restricting Tax Number in Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
6.5 Material Master Initial Load Using IDoc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
6.6 Configure Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Tip
We recommend setting up this integration scenario using the Cloud Integration Automation Service (CIAS).
CIAS provides a guided workflow that features:
With the included project management tool and complementary support information, CIAS helps reduce the
time you need for manual tasks. For more information, see the product page on the SAP Help Portal.
Navigate directly to the Maintenance Planner to start the guided CIAS workflow.
This document describes the procedure to configure the integration using certificate-based authentication
between SAP S/4HANA Cloud Public Edition and SAP Cloud for Customer system using SAP Cloud Integration
(SCI). Although it’s possible to configure the integration using basic authentication (user and password), this isn’t
explained in this document.
As these configuration steps are customer-specific, they can’t be delivered by SAP, and must be completed by the
customer. This document describes the general configuration steps to manually set up the configuration within the
existing system landscape.
1. If you have any queries or feedback about this document, please create a ticket using the CSN component
CA-GTF-INT-CFC.
2. For known limitations and corresponding workarounds in this integration scenario, you can refer to this SAP
Note . This note also provides a spreadsheet with the known code list mappings that need to be imported
into the SAP Cloud for Customer tenant during the configuration. See section Perform Code List Mapping for
more details.
You’re required to enter or provide system-specific information. To ensure a smooth and efficient integration of
SAP S/4HANA Cloud Public Edition and SAP Cloud for Customer systems, we recommend that you have the
information listed in the following table before starting the integration process.
Information required:
SAP Business Technology Platform (SAP BTP) with Event Mesh Service Subscription
Note
If you want to include event-based Equipment and Functional location replication in your scope, then you would
also require a subaccount on SAP Business Technology Platform (SAP BTP) with the Event Mesh Service
subscribed.
2.2 Prerequisites
It’s mandatory that scope item Opportunity-to-Order with SAP Cloud for Customer (1VP) is active in your SAP
S/4HANA Cloud Public Edition system. Depending on your configuration environment for SAP S/4HANA Cloud
Public Edition, choose one of the following options:
If the scope item isn’t active, request the activation via BCP – Ticket Component: XX-S4C-OPR-SRV.
• Initial user and access information for your SAP S/4HANA Cloud Public Edition tenant.
• Initial user and access information for your SAP Cloud for Customer tenant provided via email by Cloud
Management Service.
• Initial user and access information for your SAP Cloud Integration tenant.
• SAP Cloud Integration Client Certificate
If you would like to include Registered Products and Installation Points integration in your scope, then there are
special prerequisites for this scenario:
1. Scope item Business Event Handling (1NN ) is a prerequisite and needs to be activated in your SAP S/
4HANA Cloud Public Edition system.
2. You have a subaccount on SAP Business Technology Platform (SAP BTP) with Subscription to SAP Event Mesh
service. This includes:
• Configuration of entitlements and adding a Service Plan (plan type: Default) for SAP Event Mesh service.
• Creation of an instance of SAP Event Mesh service
• Subscription to SAP Event Mesh service by administrator of the global account.
• User access to the SAP Event Mesh UI by assignment of role collection in the subaccount.
Note
For details on setting up SAP Event Mesh Service, visit the SAP help document for What Is SAP Event Mesh.
While creating an instance for SAP Event Mesh service, ensure that you use the JSON scope that includes
topic rules for publish and subscribe. By registering your SAP S/4HANA Cloud Public Edition System in SAP
Business Technology Platform (SAP BTP), maintaining SAP BTP Extensions in SAP S/4HANA Cloud Public
Edition and adding service plans for SAP S/4HANA Cloud Public Edition Extensibility and SAP Event Mesh,
you can skip the manual creation of Communication Arrangement in SAP S/4HANA Cloud Public Edition (the
manual creation of communication arrangement for SAP Event Mesh Service is explained in this guide). For
more details, visit Create an SAP S/4HANA Cloud Private Edition Extensibility Service Instance in the Cloud
Foundry Environment.
Before you perform the initial data load, you need to ensure that the steps described in scope item Sell from Stock
(BD9) have been executed. With this scope item, business partners and material data become available in the SAP
S/4HANA Cloud Public Edition system.
Ensure that the SSL trust is established between all the applications. Contact system administrator for further
details.
The following sections describe all settings required for this scope item. This can be divided into the following main
groups:
The SAP Cloud for Customer tenant is available with initial user and password.
When a new tenant is available, the tenant owner gets an email from Cloud Management Service. The email
contains tenant - access and support information. The initial user with password can be found in the access
information. To make certain configuration, the first step is to do scoping with the initial user.
In case you have a preconfigured system, you can directly perform Master Data preparation step after scoping.
1. Open the Frontend Access tenant URL in the web browser of your SAP Cloud for Customer system.
Note
Administrator
Business Configuration
Business Partners
Procedure
Sales Product and Service Portfolio for Sales Sell Standard Products
Communication and Information Ex- Integration with External Applications Integration with SAP ERP
change and Solutions
Communication and Information Ex- Integration with External Applications Integration of Master Data
change and Solutions
Communication and Information Ex- Integration with External Applications Integration into Sales, Service, and
change and Solutions Marketing Process
Scoping depends on the business needs. Some of the elements are selected automatically due to business
logic. This is needed for Communication and Information Exchange.
9. Choose Next.
10. In the Questions step, drill down to the scoping elements:
• Choose General Business Data Business Partners Handling of Business Partners .
Note
Customer Insights is part of the SAP Sales Cloud, Intelligent Sales Add-On, and is only available with a
license.
• Choose Communication and Information Exchange Integration with External Applications and
Solutions .
Select the Scoping element in the hierarchy and create the following values in the right pane. Mark In Scope
for the following elements listed in the table:
Exchanges Rates
Products
Organizational Structures
Opportunities:
Sales Quotes:
Field Value
COD_QUOTE_WCVIEW
Sales Sales Quotes
Field Value
Job ID SALESREP
Division Sales
Code List Mapping for integration with External Applications Communication and Information Exchange
and Solutions
Opportunities Sales
6. Choose Close.
Note
The following values or information depends on the customer’s real business, and therefore should be adapted
accordingly. Organizational structure is replicated from SAP S/4HANA Cloud Public Edition. Only Company
needs to be created as per the SAP S/4HANA Cloud Public Edition system, remaining entities are replicated
from SAP S/4HANA Cloud Public Edition.
Field Value
Valid To <Unlimited>
Country/Region <Country/Region>
4. Choose Save.
Note
The replication of organizational structure from SAP S/4HANA Cloud Private Edition is described as a
part of this guide. If you want to replicate the organizational structure from SAP S/4HANA Cloud Private
Edition, then skip the creation of SubOrg Units as the following procedure describes. The replication of
Organizational structure from SAP S/4HANA Cloud Private Edition is described as a part of this guide.
5. Choose New to create a new SubOrg Unit. In the dialog box, enter the following values:
Field Value
Valid To <Unlimited>
Sales Checked
6. Choose Save
7. Repeat the same for below Sub-Org Unit.
Field Value
Field Value
Language English
Valid to <Unlimited>
Field Value
User ID FIELD_SALES_REP
SALES_REP_ROLE Checked
01 Direct Sales
02 Indirect Sales
Z1 Direct sale Z1
Z2 Wholesale Z2
Z3 Other sales Z3
Division Description
00 Product Division 00
01 Product Division 01
10 Product Division 10
20 Product Division 20
Note
If root hierarchy exists, then you don’t need to create a new hierarchy.
Product Category ID can be maintained on the left, the Product Category and Product Assignment Allowed
can be maintained on the right. Product Category ID is the Material group available in the SAP S/4HANA
Cloud Public Edition system.
ROOT ROOT
2 Material group 1
3 Material group 2
Note
In case you are implementing the Intelligent Enterprise Suite (IES) Lead-to-Cash solution, skip this task.
Procedure
Procedure
Host Name Enter SCI system URL Host Name is the value of SCI system
worker node without prefix https://. re-
fer to How to Get the SAP Cloud Inte-
gration runtime URL [page 62]
System Instance ID Enter System ID of S4 Cloud system Refer to System ID for SAP S/4HANA
Cloud Public Edition System [page 89]
Business System ID Enter System ID of S4 Cloud system To get the business system ID of your
SAP S/4HANA Cloud Public Edition,
navigate to the Communication Sys-
tems app in the SAP S/4HANA Cloud
Public Edition system, choose Adapt
Filters, select Own SAP Cloud System,
choose OK.
6. Choose Close.
Note
Once the mashup is configured in SAP Cloud for Customer, the link on the SAP S/4HANA Cloud Public
Edition Sales Order will be enabled in the SAP Cloud for Customer document flow. Once the user selects
the link, the SAP S/4HANA Cloud Public Edition Sales Order display UI will be opened. It is a UI integration
with a named user. Hence, either SSO has to be set up or a logon is required on the SAP S/4HANA Cloud
Public Edition side.
In case you have SSO configured for your Cloud for Customer and SAP S/4HANA Cloud Public Edition systems as
per section, Configure Single Sign-On [page 90]: Use SSO URL in mashup.
3.1.7 ID Mapping
Procedure
ID External ID
1 L001
2 L002
ROOT
Note
External ID values are available in the SAP S/4HANA Cloud Public Edition system. Refer to the Code List
Mapping [page 29] section for details.
6. Choose Save.
Use
The communication scenarios mentioned in the following table are relevant for your project scope. Create them
one after the other. Communication scenarios that are not mentioned in the table can be disabled.
Material Replication from SAP Business Replicate Material from SAP Business Confirm Material Replication to SAP
Suite Suite - Select Business Suite - Select
Business Partner Replication from SAP Replicate Business Partner Attachment Confirm Business Partner Replication to
Business Suite from SAP Business Suite -Deselect SAP Business Suite - Select
Business Partner Replication to SAP Confirm Business Partner Replication Replicate Business Partner to SAP Busi-
Business Suite from SAP Business Suite - Select ness Suite - Select
Pricing in Sales Quote Follow Up Scenario Request Sales Document Data from SAP
in SAP Business Suite Business Suite -Select
Note
In case you are implementing the In-
telligent Enterprise Suite (IES) Lead-
to-Cash solution, skip this communi-
cation scenario.
Creation of Sales Quote Follow Up Docu- Notify Sales Quote of Sales Order Re- Create Sales Quote Follow Up Document
ment in SAP Business Suite quest Creation in SAP Business Suite - in SAP Business Suite -Select
Select
Replicate Sales Quote Attachment to
Note
Notify Sales Quote of Sales Order Crea- SAP Business Suite- Deselect
In case you are implementing the In- tion in SAP Business Suite - Select
telligent Enterprise Suite (IES) Lead-
to-Cash solution, skip this communi-
cation scenario.
Creation of Opportunity Follow Up Docu- Notify Opportunity of Follow Up Docu- Create Opportunity Follow Up Document
ment in SAP Business Suite ment from SAP Business Suite - Select in SAP Business Suite -Select
Registered Product and Installation Point Replicate Registered Products from SAP
Replication from SAP Business Suite Business Suite - Select
Registered Product and Installation Point Confirm Installation Point Replication Replicate Install Point to External System
Replication to External System from SAP Busi-ness Suite - Select - Select
Product Stock Request from SAP Busi- Request Stock from SAP Business Suite
ness Suite - Select
Business Partner End of Purpose Check Check Business Partner End of Purpose
from SAP ERP
from SAP ERP - Select
Business Partner End of Purpose Check Check End of Purpose of Business Part-
from SAP Business Suite
ners from SAP Business Suite – Select
Business Document Flow Query from Request Document Flow from SAP Busi-
SAP Business Suite
ness Suite - Select
Note
In case you do not see any of the configuration scenarios, recheck the project scoping and add the necessary
scoping elements.
If you plan to replicate business partners via Master Data Integration then additionally select the question
under ID Mapping: Do you want to replicate ID mapping from an external application to your Cloud solution?
Procedure
Field Value
Field Value
25. Under Outbound Communication Credentials, choose Download. The client certificate you have downloaded
has to be installed in the SCI system.
26. Enter a name for Cloud for Customer Client Certificate X.509 (for example, C4CSSLClient.cer) and choose
Save.
You have to upload this certificate when you configure the C4C-to-SCI inbound iFlow.
Procedure
1. Choose the work center view: Business Configuration Implementation Projects Select the current project
and choose Open Activity List .
2. Choose the Fine-Tune tab.
3. Choose Opportunity from the table, then navigate to Maintain Custom Status from the next page.
4. Under available Document Types, select OPPT and custom Status 2, then check the checkbox for status Create
ERP Sales Order.
Procedure
Purpose
The codes used in the SAP S/4HANA Cloud Public Edition and SAP Cloud for Customer systems aren’t always the
same. Therefore, they must be mapped in SAP Cloud for Customer using the Code List Mapping Tool.
Procedure
1. Open this SAP Note and download the attached zip file S4_C4C_Merge_20171214.zip. Save it locally.
This file will be uploaded to SAP Cloud for Customer in the next steps.
2. Choose the work center view: Business Configuration Upload Code List .
3. For the Code List Mapping, choose SAP On-Premise Integration.
4. Choose Upload. Select the file that you’ve downloaded in step 1.
5. Check the status of the Code List Mapping upload in the Application Log:
1. Go to Business Configuration Upload Code List Application Log .
2. Click the required Application Log ID.
The log displays information in the following tabs:
• General: Displays a high-level summary and administrative data for the job
• Settings: Displays settings selected during an upload
• Results: Displays the detailed results of the job including a list of detailed message descriptions, and
the nature of the message.
3. You can also export the information on the tabs to a spreadsheet. To do this, choose Export to Microsoft
Excel, and select the tab from which you want to export the data.
You may get error for the below external code values. Maintain the code list mapping for external code
to the local code using Manual Code List mapping.
• CashDiscountTermsCode (Material)
• Base Quantity Type (Material)
• PriorityCode (Price call in Sales Quote)
• PartyRoleCode (Price call in Sales Quote)
• ExternalSalesPricingProcedureCode (Price call in Sales Quote)
• MeasureUnitCode (Material)
• ExternalSalesPriceSpecificationElementTypeCode (Sales Quote Follow up)
• BusinessPartnerRoleCode (Business Partner)
• FormOfAddressCode (Business Partner)
• BusinessTransactionDocumentProcessingTypeCode (Pricing in Sales quote)
Purpose
If code list error is observed in message monitoring during the replication of initial load of master data from SAP
S/4HANA Cloud Public Edition to SAP Cloud for Customer system, then perform the following steps:
Procedure
The code list mapping UI contains the following tables, which are hierarchical:
A. Local data type: Displays the data types available in the SAP Cloud for Customer system. Select the
data type for which the code list needs to be mapped.
B. Code list mapping rule: Set the code list mapping rules for the data type selected in the above table.
There are two possible rules:
• Local and remote codes are equal: This rule can be used when the values in both the SAP Cloud
for Customer system and the SAP S/4HANA Cloud Public Edition system are the same. If this rule is
selected, there’s no need to do any mapping for the code values.
• Map Individual values: This rule can be used when the values in the SAP Cloud for Customer system
and the SAP S/4HANA Cloud Public Edition system are different. If this rule is selected, the individual
code values for the data type need to be mapped to values in the SAP S/4HANA Cloud Public Edition
system. An example and the list of SAP S/4HANA Cloud Private Edition tables corresponding to the
local data types are mentioned in the next steps.
C. Code List mapping: Map each code value (only the required ones) for the local data type from SAP
Cloud for Customer system to the corresponding values in the SAP S/4HANA Cloud Public Edition system.
6. In the Code List Mapping Definition section, select the row with Local Data Type Name to configure the code list
values.
7. In the Code List Mapping Rule section, edit the mapping rule.
Note
If you can’t change existing values, you may delete the entries and create new ones.
Note
For the mappings, you need to create the following settings, see the example below.
Local Code Code represented by the SAP Cloud for For the local code type
Customer system BusinessTransactionDocumentPro
cessingTypeCode with value ZA
Description Description of what the code repre- Local code value ZA has a descrip-
sents tion Sales Quote with External
Pricing in the SAP Cloud for Cus-
tomer system.
External Code Code as maintained in the SAP S/ Refer the SAP S/4HANA Cloud Private
4HANA Cloud Public Edition backend Edition table for the external code for
system sales order
Value: TA
Inbound Default If this is checked, the inbound value is In case each external code is mapped
considered as default to multiple internal codes
Outbound Default If this is checked, the outbound value is In case each internal code is mapped to
considered as default multiple external codes
M Machine
S Customer Equipment
X Equipment Services
Note
Maintain Code List Mapping for TextCollectionTextTypeCode by adding a row under Code List Mapping
where Local Code 10011 (Internal Comment) is mapped to 0001.
Purpose
You can block Business Partner in SAP Cloud for customer system and SAP Cloud for Customer after End of
Purpose of the Business Partners.
To set up End of Purpose – Blocking of Business Partner in SAP Cloud for Customer system, a BAdI needs to be
implemented using the SAP Cloud Applications Studio. For detailed information, refer to section Prerequisites for
SAP Cloud for Customer system from https://help.sap.com/viewer/5d3ae4aa1f174b2cb6ec625c93ef8884/DEV/
en-US/c2e2464b9e1441e1b2adf3bbfc6a975a.html.
Purpose
Customer Insights helps you, as a sales representative, to thrive in the digital-sales era by surfacing relevant
insights and recommending actions to fully leverage growth opportunities and provide an enhanced customer
experience.
Note: Customer Insights is part of the SAP Sales Cloud, Intelligent Sales Add-On and is only available with a license.
Procedure
To use Customer Insights, administrators must add Customer Insights to the scope of the project and user must be
assigned to the Customer Insights work center, this is included in section 3.1.2 and 3.1.3.
The SAP S/4HANA Cloud Public Edition System URL is included in the SAP S/4HANA Cloud Public Edition
provisioning email (email sender: SAP s4scc) and includes system access and administrative information.
The communication arrangement needs to be activated in the SAP S/4HANA Cloud Public Edition system for the
communication with Web Services.
Prerequisite
Administrator has the catalog role ID SAP_CORE_BC_COM assigned in the SAP S/4HANA Cloud Public Edition
system.
Use
The communication user defined in the SAP S/4HANA Cloud Public Edition system is used for inbound
communication, and for processing messages in the system. Technically, the user is used to call OData Services in
SAP S/4HANA Cloud Public Edition from SAP Cloud Integration.
Procedure
1. Access the SAP S/4HANA Cloud Public Edition system and log in as an Administrator.
2. Open the Maintain Communication Users(F1338) app.
3. Choose New.
Note
Make a note of the technical User ID of this user. For example: C0000007668
Procedure
1. Access the SAP S/4HANA Cloud Public Edition system and log on as an administrator.
Follow this link to automatically configure the communication system and skip the steps 2-10.
2. Open the Maintain Communication Systems app.
3. Choose New.
4. To get the system ID, see chapter Configure Communication Arrangements [page 24]. Copy this system ID and
enter the same in ID. In the System Name, enter any descriptive name.
5. Choose Create.
6. In the Host Name field, enter the SAP Cloud Integration Runtime URL without "https://". For more information,
refer to chapter How to Get the SAP Cloud Integration runtime URL [page 62].
7. Enter the SAP Cloud for Customer's Business System in the Logical System ID and Business System fields. See
chapter Configure Communication Arrangements [page 24] for getting the system ID and enter it here.
Note
Unless there is an IDOC-based integration, the Logical System field is not useful. Although this field is not
mandatory during the communication system creation, the Logical System field is manadtory when you
create a communication arrangement, therefore, you may enter any dummy value for the Logical System
field in this step.
An outbound communication user is required to connect SAP S/4HANA Cloud Public Edition to the SAP Business
Technology Platform (SAP BTP), Event Mesh on Cloud Foundry. Skip this section if you’ve registered your SAP
S/4HANA Cloud Public Edition System in BTP global account, maintained SAP BTP Extensions in SAP S/4HANA
Cloud Public Edition and added service plans for SAP S/4HANA Cloud Public Edition Extensibility and Event Mesh,
in which case the communication System and arrangement (SAP_COM_0092) would be automatically created.
Note
You can retrieve the required values from the Service Key of the EMS Service Instance in the SAP BTP cockpit.
Here are the steps to navigate: SAP BTP cockpit global account that contains the Event Mesh service
subaccount that contains the Event Mesh service space of your EMS Service Instances select your EMS
service instance Service Keys .
Procedure
Use
The communication arrangement in the SAP S/4HANA Cloud Public Edition system defines all relevant information
for the communication with SAP Business Technology Platform (SAP BTP). For example, it contains the
communication system, inbound and outbound authentication.
Note
Some of the Communication Scenarios are handled by the Data Replication Framework (DRF). Although the
creation of the replication model is handled automatically by SAP S/4HANA Cloud Public Edition, you must
specify a name for the replication model.
The replication model name can be used to view and analyze messages in the data replication log, available
in the Monitor Replication app. For more information, see https://help.sap.com/viewer/product/
SAP_S4HANA_CLOUD/ . Then, go to Product Assistance English Generic Information Data Replication
Framework .
Field Values
Host Name See chapter How to Get the SAP Cloud Integration runtime
URL [page 62].
Path You can get it once the iFlow Replicate Business Partner from
SAP Business Suite has been deployed. See chapter Configure
and Deploy the iFlows Using Web UI [page 64].
Outbound Authentication (Basic Authentication): Username Typically, p-user (SCN user) or s-user (support portal user).
and password
User requires role ESBMessaging.send.
Purpose
This communication arrangement in the SAP S/4HANA Cloud Public Edition system consists of inbound and
outbound services Sales Order.
Procedure
Tip
You can use the Value Help ( ) to search for a specific sce-
nario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the that you created in the Create
Communication System for Integration [page 36] section, the Inbound and Outbound Communication users
are entered automatically.
7. Note down the SAP S/4HANA Cloud Public Edition tenant ID, which is displayed in the My System field. It's
used in SAP Cloud for Customer system. For more information, see chapter Set Up Communication System
[page 21]. You use this in the fields such as System Instance ID, Business System ID, IDOC Logical System ID
when defining the communication system in SAP Cloud for Customer.
8. Verify the following Inbound Services and Maintain Outbound Services.
Create Sales Quote or Opportunity Follow Up Document Replicate Material to SAP Cloud for Customer - Deselect
from SAP Cloud for Customer
Replicate Business Partner from Client to SAP S/4HANA Notify Sales Quote or Opportunity of Follow Up Document to
Cloud Public Edition system SAP Coud for Customer - Select
Replicate Business Partner Relationship from Client to SAP Replicate Business Partners from SAP S/4HANA Cloud
S/4HANA Cloud Private Edition system Public Edition System to Client - Deselect
Request Pricing for Sales Document or Opportunity from Replicate Business Partner Relationship from SAP S/4HANA
SAP S/4HANA Cloud Private Edition Cloud Public Edition System to Client - Deselect
Receive confirmation for Business Partner from Client Send Confirmation of Business Partner to Client - Deselect
Receive confirmation for Business Partner Relationship from Send Confirmation of Business Partner Relationship to Cli-
Client ent - Deselect
9. Choose Save.
10. The communication arrangement is now active.
Purpose
This communication scenario SAP_COM_0008 provides end-points (inbound and outbound) for the replication of
Business Partner, Customer, and Supplier master through ALE IDOCs or SOAP services.
If you want to replicate Business Partners via Master Data Integration, please skip this chapter and refer to the
Configuration in SAP S/4HANA Cloud Public Edition in the section Replication of Master Data via SAP Master
Data Integration Service [page 75].
Procedure
Tip
You can use the Value Help ( ) to search for a specific sce-
nario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the that you created in the Create
Communication System section, the Inbound and Outbound Communication users are entered automatically.
Verify the below Inbound Services, and Maintain Outbound Services.
Business Partner - Replicate from Client to SAP S/ Business Partner - Replicate from SAP S/4HANA Cloud Public
4HANA Cloud Public Edition Edition to Client- Select
Business Partner Relationship - Replicate from Client to Business Partner Relationship - Replicate from SAP S/4HANA
SAP S/4HANA Cloud Public Edition Cloud Public Edition to Client- Select
Business Partner - Receive Confirmation from Client to Business Partner - Send Confirmation from SAP S/4HANA Cloud
SAP S/4HANA Cloud Public Edition. Public Edition to Client- Select
BP Relationship - Receive Confirmation from Client to BP Relationship - Send Confirmation from SAP S/4HANA Cloud
SAP S/4HANA Cloud Public Edition Public Edition to Client- Select
7. Under Additional Properties, choose X (Yes) for property Integration with C4C enabled. In the outbound service
Business Partner - Replicate from SAP S/4HANA Cloud Public Edition to Client go to Additional Properties and
maintain the below values:
System Filters Leave this field empty till Initial Data Load from SAP S/4HANA Cloud
Public Edition is replicated.
Select X after the Initial master data is replicated, this ensures contin-
uous replication of data.
This Replication Model will be used in the later in Define Filter Criteria.
Note
In case you want to set filters for your Product Replication, Select System Filters as X else, Select System
Filter as Empty.
8. Choose Save.
9. The communication arrangement is now active.
Purpose
This communication scenario SAP_COM_0009 provides end-points (inbound and outbound) for the replication of
material masters through ALE IDOCs or SOAP services.
Procedure
Tip
You can use the Value Help ( ) to search for a specific sce-
nario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the that you created in the Create
Communication System section, the Inbound and Outbound Communication users are entered automatically.
Verify the below Inbound Services and maintain Outbound Services.
Replicate Product from Client to SAP S/4HANA Cloud Public Replicate Product from SAP S/4HANA Cloud Public Edition
Edition system system to Client - Deselect
Product Master - Create, Read, Update, Delete Product Master - Replicate from SAP S/4HANA Cloud Public
Edition to Client - Select
Product Master - Replicate from Client to SAP S/4HANA Product Master - Confirmation from SAP S/4HANA Cloud
Cloud Public Edition Public Edition to Client - Deselect
7. In the outbound service Product Master - Replicate from SAP S/4HANA Cloud Private Edition to Client go to
Additional Properties and maintain the below values:
System Filters Leave this field empty till Initial Data Load from SAP S/
4HANA Cloud Public Edition is replicated.
In case you want to set filters for your Product Replication, select System Filters as X otherwise, select
System Filter as Empty.
8. Choose Save.
9. The communication arrangement is now active.
Purpose
This communication scenario SAP_COM_0114 provides endpoints (outbound) for the replication of currency
exchange rate through SOAP services.
Procedure
Tip
You can use the Value Help ( ) to search for a specific sce-
nario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the that you created in the Create
Communication System section, the Inbound and Outbound Communication users are entered automatically.
7. Maintain the below Outbound Services
Replicate Currencies from SAP S/4HANA Cloud Public Edition system to target system - Deselect
Replicate Exchange Rates from SAP S/4HANA Cloud Public Edition to target system - Select
Replicate Incoterms from SAP S/4HANA Cloud Public Edition to target system - Deselect
Replicate Material Groups from SAP S/4HANA Cloud Public Edition to target system - Deselect
Replicate Item Category from SAP S/4HANA Cloud Public Edition to target system - Deselect
Replicate Region Codes from SAP S/4HANA Cloud Public Edition to target system - Deselect
Replicate Unit of Measure from SAP S/4HANA Cloud Public Edition to target system - Deselect
8. In the outbound service Replicate Exchange Rates from SAP S/4HANA to Target system go to Additional
Properties and maintain the below values:
9. Choose Save.
10. The communication arrangement is now active.
Purpose
This communication scenario provides endpoints (inbound and outbound) for the replication of Sales Office, Sales
Group, and Sales Organization data through SOAP services.
Procedure
Tip
You can use the Value Help ( ) to search for a specific sce-
nario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the that you created in the Create
Communication System for Integration [page 36] section, the Inbound and Outbound Communication users
are entered automatically.
Enter a replication model name in Additional Properties section, for example: <SALES_ORG>.
Note
Outbound Services
8. Choose Save.
9. The communication arrangement is now active.
Purpose
This communication arrangement in the SAP S/4HANA Cloud Public Edition system consists of outbound services
for Procurement Master Data Integration. The communication scenario SAP_COM_0116 provides endpoints for the
replication of Plants and Purchasing Organization through SOAP services.
Procedure
Tip
You can use the Value Help ( ) to search for a specific sce-
nario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the that you created in the Create
Communication System section, the Inbound and Outbound Communication users are entered automatically.
7. Maintain the following Outbound Services.
Outbound Services
8. In the outbound service Replicate Exchange Rates from SAP S/4HANA to Target system go to Additional
Properties and maintain the following values:
9. Choose Save.
10. The communication arrangement is now active.
Purpose
This communication arrangement in the SAP S/4HANA Cloud Public Edition system consists of inbound services
for Asset Management Master Data Integration. The communication scenario SAP_COM_0395 provides endpoints
for the replication of Equipment and Functional Location through OData services.
Procedure
Tip
You can use the Value Help ( ) to search for a specific sce-
nario.
5. Choose Create.
Inbound Services
Functional Location
Equipment
Note
This communication is OData based, therefore, client certificate authentication is not supported. Please
use basic user authentication for the outbound communication.
7. Choose Save.
8. The communication arrangement is now active.
This communication arrangement in the SAP S/4HANA Cloud Public Edition system consists of outbound services
for SAP Event Mesh Service on SAP Business Technology Platform (SAP BTP). The communication scenario
SAP_COM_0092 provides end-points for the SAP Event Mesh service, which is used in the equipment and functional
location replication in this setup.
Note
Skip this section if you've registered your SAP S/4HANA Cloud Public Edition System in SAP Global account,
maintained SAP BTP Extensions in SAP S/4HANA Cloud Public Edition and added service plans for SAP S/
4HANA Cloud Public Edition Extensibility and SAP Event Mesh, in which case this Communication Arrangement
would be automatically created.
Procedure
Tip
You can use the Value Help ( ) to search for a specific sce-
nario.
5. Choose Create.
6. In the screen area Common Data, field Communication System, select the communication system you created
previously in Create Communication System and Technical Users for SAP Event Mesh [page 37] section for
SAP Event Mesh from the value help.
7. Specify the following fields in the Additional Properties section.
1. Channel: channel name
2. Description: channel description
3. Topic Space: topic space name. The Topic Space needs to match the namespace that will be defined in the
SAP Event Mesh service instance.
Reconnect Attempts: number of reconnect attempts allowed if there are connection failures. It's
recommended to enter 0 for an infinite number of reconnect at-tempts
4. QoS: quality of service, defaulting to value 1
5. Reconnect Attempts: number of reconnect attempts allowed if there are connection failures. It's
recommended to enter 0 for an infinite number of reconnect attempts
6. Reconnect Wait Time(sec): idle time between 2 reconnect attempts 7. In the section Outbound Services,
specify Path (for example: /protocols/mqtt311ws) and choose Save.
8. In the section Outbound Services, specify Path (for example: /protocols/mqtt311ws).
Note
The Service path can be obtained from the Service Key of the SAP Event Mesh Service Instance, from the
field URI listed under messaging.
9. Choose Check Connection to check whether a connection can be established between SAP S/4HANA Cloud
Public Edition and SAP BTP.
Note
Skip this section if you've registered your SAP S/4HANA Cloud Public Edition System in SCP Global
account, maintained SAP BTP Extensions in SAP S/4HANA Cloud Public Edition, and added service
plans for SAP S/4HANA Cloud Public Edition Extensibility and SAP Event Mesh, in which case this
Communication Arrangement would be automatically created.
Purpose
This communication scenario provides endpoint for the replication of material stock through OData service.
Procedure
Tip
You can use the Value Help ( ) to search for a specific sce-
nario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the communication system that you
created in the Create Communication System for Integration [page 36] section, the Inbound Communication
user is entered automatically.
Verify the below Inbound Services:
Inbound Service
7. Choose Save.
8. The communication arrangement is now active.
Purpose
This communication scenario SAP_COM_0091 in the SAP S/4HANA Cloud Public Edition system consists of
services for blocking of Business Partner, Customer, and Supplier data.
Procedure
Tip
You can use the Value Help ( ) to search for a specific sce-
nario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the that you created in the Create
Communication System section, the Inbound and Outbound Communication users are entered automatically.
Verify and Maintain Outbound Services.
Outbound Services
ABABusinessPartnerEOPRemoteOut - Select
ABABusinessPartnerEOPComplout - Select
This communication scenario SAP_COM_0173 in the SAP S/4HANA Cloud Public Edition system consists of service
for requesting credit-relevant data, such as the credit limit or the credit exposure of a business partner.
Tip
You can use the Value Help ( ) to search for a specific
scenario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the communication system that you
created in the Create Communication System section, the Inbound and Outbound Communication users are
entered automatically.
Verify the below Inbound Service:
Inbound Service
7. Choose Save.
8. The communication arrangement is now active.
This communication scenario SAP_COM_0303 in the SAP S/4HANA Cloud Public Edition system consists of
services for extracting operational journal entry items to an external system using this inbound service
Tip
You can use the Value Help ( ) to search for a specific
scenario.
5. Choose Create.
6. Maintain Common Data. In the Communication System field, select the communication system that you
created in the Create Communication System section, the Inbound and Outbound Communication users are
entered automatically.
Inbound Service
1. Choose Save.
Prerequisite
Scope item Business Event Handling (1NN ) is activated in your SAP S/4HANA Cloud Public Edition system.
Procedure
Procedure
Purpose
Filter objects are used to remove the SAP S/4HANA Cloud Public Edition outbound processing code values that
aren’t supported by the receiver system. During SAP S/4HANA Cloud Public Edition inbound processing, these
code values are added again.
Note
The below steps are optional and should be performed based on your requirement.
Procedure
1. Log in to SAP S/4HANA Cloud Public Edition system as Administrator - Data Replication.
2. From Data Replication navigate to Define Filter Criteria
3. Select the relevant Replication Model (for example, <BPS4TOC4C> for Business Partner Replication and choose
Display. A new window opens to Display Filter Criteria.
4. The Replication Models are maintained during communication arrangement configuration, for example, see
chapter Create Communication Arrangement SAP_COM_0025 [page 39] for Business Partner Replication
Model.
5. Select Edit and choose the Filter Criteria to Include Business Objects.
6. Select the BP role to be Include in your Business Partner replication to SAP Cloud for Customer.
7. Choose the Show Segment filter and choose the filter object Business Partner Role-98601.
8. Select Edit and choose the filter criteria to include Business Objects.
9. Select the BP Role to be included in your Business Partner replication to SAP Cloud for Customer.
Maintain the code list mapping for above values in SAP Cloud for Customer system.
Prerequisite
To carry out the following activity, a business user with a business role template
SAP_BR_DATA_PRIVACY_SPECIALIST (Configuration Expert - Business Process Configuration) containing the
business catalog for Information Lifecycle Management (SAP_CORE_BC_ILM) is required.
Note
For detailed information on this topic, refer to ILM Settings for Data Protection.
Choose New to create the audit area BUPA_DP if it does not already exist.
Enter the following information and check the ILM objects as mentioned below:
Choose Save.
After you've assigned the relevant ILM objects to audit areas, you can use the ILM Policies app to set policies that
include residence and retention rules that you maintain to satisfy your business needs. For more information, see
ILM Policies.
Procedure
4. If an ILM Policy already exists, then choose Continue, otherwise choose New.
5. To create a new policy, choose New.
6. Enter a value for Policy Name, choose APPL_NAME from the Available Condition Fields and add the item to the
Selected Condition Fields.
7. Choose Save, then Edit Rules.
8. Under Rules for policy choose Add, choose BUP (Business Partners).
9. Enter values for Residence Period, Residence Prd Unit, and Time Ref as per your business requirement:
Prerequisite
To carry out the following activity, a business user (Administrator) with a business role SAP_BR_BPC_EXPERT
(Configuration Expert - Business Process Configuration) is required.
Use
This section describes how to check the sales organization and sales order type values maintained in the SAP
S/4HANA Cloud Public Edition system. These values should be mapped with the values in the SAP Cloud for
Customer for the messages to flow correctly.
Procedure
1. Depending on your configuration environment for SAP S/4HANA Cloud Public Edition, choose one of the
following options:
• Configure Your Solution:
Log on to the SAP Fiori Launchpad in the SAP S/4HANA Cloud Public Edition system as a Configuration
Expert - Business Process Configuration (SAP_BR_BPC_EXPERT).
Navigate to Manage Your Solution Configure Your Solution
On the Configure Your Solution: Realize Phase screen, search for Define Common Distribution Channel and
choose Configure.
• SAP Central Business Configuration:
Log on to the project experience in SAP Central Business Configuration.
Go to the Business Processes Configuration app. To locate the activity in the tree view, search for the
following activity: Define Common Distribution Channel.
• Choose Open Documentation for the found line item to see more details about this configuration activity.
• Choose the line item to navigate directly to SAP S/4HANA Cloud Public Edition system.
• Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration
(SAP_BR_BPC_EXPERT).
2. Check the value maintained for the distribution channel and ensure that the same value is mapped with the
sales organization data in SAP Cloud for Customer and select Save
3. Choose Set Status to Confirm and choose Save.
In order to replicate Registered Product (Equipment) and Installation points (Functional Location), you need to
create four queues.
1. Equipment queue
2. Functional location queue
3. Equipment error queue
4. Functional locational error queue
Prerequisites
Ensure the prerequisites listed in the Preparation section that are relevant to SAP Event Mesh Service initial setup
are met.
Procedure
Note
SAP provides prepackaged, generic integration content called integration flows (iFlows) for the integration of
SAP Cloud for Customer with SAP S/4HANA Cloud Public Edition systems using SAP Cloud Integration (SCI).
Prerequisites
In order to import and deploy iFlows, you need the AuthGroup.IntegrationDeveloper role assigned to your
user in your SCI tenant.
The SAP Cloud Integration (SCI) runtime URL is included in the SCI provisioning email.
Alternatively, you can get it once the iFlow Replicate Business Partner from SAP Business Suite has been deployed.
See chapter Configure and Deploy the iFlows Using Web UI [page 64].
In the SCI Web UI, navigate to Operations View. Choose the Started tile. Search for the iFlow Replicate Business
Partner from SAP Business Suite. Choose the status Started. The first part of the listed endpoint is the required SCI
tenant runtime URL. Example: https://<tenant>-iflmap.hana.ondemand.com
In the SAP Cloud Integration (SCI) provisioning email, follow the link under Certificate Information. On the next
screen, choose X509 Certificate with option Binary CER. Download it to your local machine.
Procedure
Note
In case you are using basic authentication, upload the Inbound Communication Users of the target systems
(for example, SAP S/4HANA Cloud Public Edition, SAP Cloud for Customer, SAP EMS).
Enter the communication authentication type you are choosing for SAP S/4HANA Cloud Public Edition and SAP
Cloud for Customer systems.
In case you are using Basic authentication, maintain the User Credential of the target System.
In case you are using Client Certificate authentication, maintain the PV key alias for the target System.
Procedure
1. Connect to the tenant management node of the SAP CPI system with the URL http://<tenant management
node URL>/itspaces.
2. On the Discover tab, select All and search for the following packages:
• SAP Cloud for Customer Integration with SAP S/4HANA Cloud Public Edition
• SAP Cloud for Customer - Customer Insights Integration with SAP S/4HANA Cloud Private Edition
3. Choose Copy on the top-right corner of the package overview page.
4. If the integration package is being created for the first time, then you would see the message Integration
Package Created. Otherwise, you can decide to either create a new copy of the package or overwrite the
existing integration package content. Choose Overwrite.
5. On the Discover tab, select All and search for package SAP Cloud for Customer – Customer Insights
Integration with SAP S/4HANA Cloud Public Edition.
Purpose
In the subsequent sections, you will find more details on the configuration of iFlows. These sections, contain the
information on the communication scenario and outbound service from the sender and inbound service from the
receiver for each iFlow. With this information, the sender and receiver addresses and authentication details can be
easily retrieved for iFlow configuration.
Procedure
Note
If you've redeployed key store (system.jks) in your SAP Cloud Integration (SCI) tenant, you need to redeploy all
the iFlows or restart them to avoid any caching related issues.
1. Log on to the tenant management node of the SCI system with the URL:
User Action or
Field Values
URL https://
<tenant
management
node>/
itspaces
2. To configure the iFlows, choose the Design mode from the navigation on the left.
3. Select the integration package copied.
4. All iFlows are displayed on the Artifacts tab of the package.
5. Choose the iFlows mentioned in the subsequent sections (one after the other) by choosing Actions
Configure .
Note
You can either configure a single iFlow or do a mass configuration by selecting all iFlows in one direction.
However, the mass configuration of iFlows isn’t explained in this document.
Note
Do not deploy the iFlows Replicate Installation Point from SAP Business Suite - Initial Load and Replicate
Registered Products from SAP Business Suite – Initial Load unless you are replicating equipment and
functional location master data. To deploy them, you need to run them once if you want to replicate the
master data from SAP S/4HANA Cloud Public Edition to SAP Cloud for Customer. In this case, both
SAP Cloud for Customer and SAP S/4HANA Cloud Public Edition systems are configured as receivers.
7. Choose iFlow to configure the sender system (in this example C4C) and receiver system (in this example
S4HANA) details.
1. Choose the Sender tab and then choose Authorization as Client Certificate
2. Browse for the certificate. Import the SAP Cloud for Customer communication arrangement X.509
certificate.
3. Choose Receiver tab: Enter the Protocol-Host-Port name of the SAP S/4HANA Cloud Public Edition system.
Contact your system administrator for these details.
4. Choose Proxy type as Internet
5. Choose the Authentication as Client Certificate
6. Choose the Private Key alias as maintained in your CPI Keystore
7. Choose Save and choose Deploy.
8. Repeat the same procedure for all the iFlows that have the same sender (C4C) and receiver (S4) systems.
• For the SAP S/4HANA Cloud Public Edition system URL, refer to chapter How to Get the SAP S/4HANA
Cloud Public Edition System URL [page 34].
• For the iFlows, which have receiver as C4C, the host of C4C is the URL of the SAP Cloud for Customer
system without HTTPS prefix, that is, myXXXXX.XXXX.XXXXXXX.com.
• For Private Key alias, specify an alias for the private key that is to be used to sign the response message.
The tenant private key has to be part of the tenant keystore.
8. The integration flows are deployed in the SCI tenant.
9. To see status of the deployed artifacts, check Monitor Integration Content Monitor.
10. The status of the iFlow should be green for successful deployment.
Procedure
Note
In case you are implementing the Intelligent Ente5.1rprise Suite (IES) Lead-to-Cash solution, skip this task. The
IES Lead-to-Cash integration scenario uses SAP Master Data Integration service to replicate business partner
master data, which is described in the section Replication of Master Data via SAP Master Data Integration
Service [page 75].
If you prefer direct integration, then include the following iFlows in the configuration:
Sender Communication
Direction of the Message Scenario : Outbound Serv- Receiver Communication
Name of the iFlow (Description) flow ice Scenario : Inbound Service
Replicate Business Partner from S4 (Sender) to C4C (Re- SAP_COM_0008 : Business Business Partner Replication
SAP Business Suite (Business Part- ceiver) Partner - Replicate from from SAP Business Suite :
ner Replication from SAP Business SAP S/4HANA Cloud Public Replicate Business Partner
Suite) Edition to Client from SAP Business Suite
Replicate Business Partner Rela- S4 (Sender) to C4C (Re- SAP_COM_0008 : Business Business Partner Replication
tionship from SAP Business Suite ceiver) Partner Relationship - Rep- from SAP Business Suite :
(Business Partner Replication from licate from SAP S/4HANA Replicate Business Partner
SAP Business Suite) Cloud Public Edition to Cli- Relationship from SAP Busi-
ent ness Suite
Confirm Business Partner Repli- S4 (Sender) to C4C (Re- SAP_COM_0008 : Business Business Partner Replication
cation from SAP Business Suite ceiver) Partner - Send Confirmation to SAP Business Suite : Con-
(Business Partner Replication to SAP from SAP S/4HANA Cloud firm Business Partner Replica-
Business Suite) Public Edition to Client tion from SAP Business Suite
Confirm Business Partner Relation- S4 (Sender) to C4C (Re- SAP_COM_0008 : BP Rela- Business Partner Replication
ship Replication from SAP Busi- ceiver) tionship - Send Confirma- to SAP Business Suite : Con-
ness Suite (Business Partner Repli- tion from SAP S/4HANA firm Business Partner Rela-
cation to SAP Business Suite) Cloud Public Edition to Cli- tionship Replication from SAP
ent Business Suite
Replicate Business Partner to SAP C4C (Sender) to S4 (Re- Business Partner Replica- SAP_COM_0008 : Business
Business Suite (Business Partner ceiver) tion to SAP Business Partner - Replicate from Client
Replication to SAP Business Suite) Suite : Replicate Business to SAP S/4HANA Cloud Public
Partner to SAP Business Edition
Suite
Replicate Business Partner Rela- C4C (Sender) to S4 (Re- Business Partner Replica- SAP_COM_0008 : Business
tionship to SAP Business Suite ceiver) tion to SAP Business Partner Relationship - Repli-
(Business Partner Replication to SAP Suite : Replicate Business cate from Client to SAP S/
Business Suite) Partner Relationship to SAP 4HANA Cloud Public Edition
Business Suite
Confirm Business Partner Replica- C4C (Sender) to S4 (Re- Business Partner Replica- SAP_COM_0008 : Business
tion to SAP Business Suite (Busi- ceiver) tion to SAP Business Suite Partner - Receive Confirma-
ness Partner Replication from SAP tion from Client to SAP S/
Business Suite) 4HANA Cloud Public Edition
Table 1:
Name of the iFlow (Descrip- Direction of the Message Direction of the Message Receiver Communication
tion) Flow Flow Scenario : Service
Confirm Material Replication C4C (Sender) to S4 (Receiver) Material Replication from SAP_COM_0009 : Product
to SAP Business Suite (Mate- SAP Business Suite : Confirm Master - Confirmation from
rial Replication from SAP Busi- Material Replication to SAP Client to SAP S/4HANA Cloud
ness Suite) Business Suite Public Edition
Replicate Material from SAP S4 (Sender) to C4C (Receiver) SAP_COM_0009 : Product Material Replication from
Business Suite (Material Rep- Master - Replicate from SAP Business Suite : Repli-
lication from SAP Business SAP S/4HANA Cloud Public cate Material from SAP Busi-
Suite) Edition to Client ness Suite
Note
In case you are implementing the Intelligent Enterprise Suite (IES) Lead-to-Cash solution, skip this task. The
IES Lead-to-Cash integration uses SAP CPQ for creation of Sales Quotes.
Create Sales Quote Follow Up C4C (Sender) to S4 (Re- Creation of Sales Quote SAP_COM_0025: Create Sales
Document in SAP Business Suite ceiver) Follow Up Document in Quote or Opportunity Follow
(Creation of Sales Quote Follow Up SAP Business Suite: Cre- Up Document from C4C
Document in SAP Business Suite) ate Sales Quote Follow Up
Document in SAP Business
Suite
Create Opportunity Follow Up C4C (Sender) to S4 (Re- Creation of Opportunity SAP_COM_0025: Create Sales
Follow Up Document in
Document in SAP Business Suite ceiver) Quote or Opportunity Follow
SAP Business Suite: Cre-
(Creation of Opportunity Follow Up Up Document from C4C
ate Opportunity Follow Up
Document in SAP Business Suite) Document in SAP Business
Suite
Notify Opportunity or Sales Quote S4 (Sender) to C4C (Re- SAP_COM_0025: Notify Creation of Sales Quote Fol-
of Follow Up Document from SAP ceiver) Sales Quote or Opportunity low Up Document in SAP
Business Suite (Creation of Sales of Follow Up Document to Business Suite: Notify Sales
Quote Follow Up Document in SAP C4C Quote of Sales Order Request
Business Suite) Creation in SAP Business
Suite
Request Sales Document Data C4C (Sender) to S4 (Re- Pricing in Sales Quote Fol- SAP_COM_0025: Request
from SAP Business Suite (Pricing ceiver) low Up Scenario in SAP Pricing for Sales Document or
in Sales Quote Follow Up Scenario in Business Suite: Request Opportunity from S/4
SAP Business Suite) Sales Document Data from
SAP Business Suite
Request Sales Order Pricing from C4C (Sender) to S4 (Re- Pricing in Opportunity Fol- SAP_COM_0025: Request
SAP Business Suite (Pricing in Op- ceiver) low Up Scenario in SAP Pricing for Sales Document or
portunity Follow Up Scenario in SAP Business Suite: Request Opportunity from S/4
Business Suite) Opportunity Data from SAP
Business Suite
Request Document Flow from SAP C4C (Sender) to S4 (Re- Business Document Flow SAP_COM_0025: Request
Business Suite(Business Document ceiver) Query from SAP Business Document Flow from S/4
Flow Query from SAP Business Suite: Request Document
Suite) Flow from SAP Business
Suite
Replicate Currency Exchange Rate S4 (Sender) to C4C (Re- SAP_COM_0114: Exchange Currency Exchange Rate
from SAP Business Suite (Currency ceiver) Rates – Replicate (A2X) Replication from SAP Busi-
Exchange Rate Replication from SAP ness Suite: Replicate Cur-
Business Suite) rency Exchange Rate from
SAP Business Suite
Replicate Sales Area from SAP S4 (Sender) to C4C (Re- SAP_COM_0427: Sales Area Organization Hierarchy Rep-
Business Suite (Organization Hier- ceiver) - Replicate lication from SAP Business
archy Replication from SAP Business Suite: Replicate Organization
Suite) Hierarchy from SAP Business
Suite
Replicate Sales Group from SAP S4 (Sender) to C4C (Re- SAP_COM_0427: Sales Organization Hierarchy Rep-
Business Suite (Organization Hier- ceiver) Group - Replicate lication from SAP Business
archy Replication from SAP Business Suite: Replicate Organization
Suite) Hierarchy from SAP Business
Suite
Replicate Sales Office from SAP S4 (Sender) to C4C (Re- SAP_COM_0427: Sales Of- Organization Hierarchy Rep-
Business Suite (Organization Hier- ceiver) fice - Replicate lication from SAP Business
archy Replication from SAP Business Suite: Replicate Organization
Suite) Hierarchy from SAP Business
Suite
Replicate Sales Organization from S4 (Sender) to C4C (Re- SAP_COM_0427: Sales Or- Organization Hierarchy Rep-
SAP Business Suite (Organization ceiver) ganization - Replicate lication from SAP Business
Hierarchy Replication from SAP Suite: Replicate Organization
Business Suite) Hierarchy from SAP Business
Suite
Replicate Plant from SAP Business S4 (Sender) to C4C (Re- SAP_COM_0116: Plants - Organization Hierarchy Rep-
Suite (Organization Hierarchy Repli- ceiver) Replicate lication from SAP Business
cation from SAP Business Suite) Suite : Replicate Organization
Hierarchy from SAP Business
Suite
Request Stock from SAP Business C4C (Sender) to S4 (Re- Product Stock Request SAP_COM_0164: Material
Suite (Product Stock Request from ceiver) from SAP Business Suite: Stock - Read
SAP Business Suite) Request Stock from SAP
Note It’s a synchronous
Business Suite
replication.
Check End of Purpose of Business S4 (Sender) to C4C (Re- SAP_COM_0091: ABABusi- Business Partner End of Pur-
Partners from SAP Business Suite ceiver) nessPartnerEOPRemoteOut pose Check from SAP Busi-
(Business Partner End of Purpose ness Suite: Check End of
Check from SAP Business Suite) Purpose of Business Partners
from SAP Business Suite
Check End of Purpose of Custom- S4 (Sender) to C4C (Re- SAP_COM_0091: Custom- Business Partner End of Pur-
ers from SAP Business Suite (Busi- ceiver) erERPEndOfPurposeCheck- pose Check from SAP ERP:
ness Partner End of Purpose Check QueryResponse_Out Check Business Partner End
from SAP ERP) of Purpose from SAP ERP
Maintain End of Purpose of Busi- S4 (Sender) to C4C (Re- SAP_COM_0091: ABABusi- Business Partner End of Pur-
ness Partners from SAP Business ceiver) nessPartnerEOPComplout pose Check from SAP Busi-
Suite (Business Partner End of Pur- ness Suite: Maintain End of
pose Check from SAP Business Purpose of Business Partners
Suite) from SAP Business Suite
Maintain End of Purpose of Cus- S4 (Sender) to C4C (Re- SAP_COM_0091: Customer- Business Partner End of Pur-
tomers from SAP Business Suite ceiver) ERPEndOfPurposeBlockNo- pose Check from SAP ERP:
(Business Partner End of Purpose tification_Out Maintain Business Partner
Check from SAP ERP) End of Purpose from SAP ERP
Procedure
Configuration of iFlows for replication of Equipment and Functional Location from SAP S/
4HANA Cloud Public Edition to SAP Cloud for Customer
• Replicate Registered Products from SAP Business Suite (Registered Product and Installation Point Replication
from SAP Business Suite)
• Replicate Installation Point from SAP Business Suite (Registered Product and Installation Point Replication
from SAP Business Suite)
These iFlows replicate created and changed equipment and installation points in SAP S/4HANA Cloud Public
Edition. In this iFlow configuration sender system is EMS service and receiver systems are SAP S/4HANA Cloud
Public Edition and SAP Cloud for Customer systems.
Communication User (More Tab) This is the technical User ID of the inbound communica-
tion user used in the Create Communication Arrangement
SAP_COM_0395 [page 48]. To retrieve the technical User ID
please search the inbound communication user in the app
Maintain Communication Users in your SAP S/4HANA Cloud
Public Edition system.
Receiver Business System (More Tab) Enter your SAP C4C Business system ID
Sender Business System (More Tab) Enter your SAP S/4HANA Cloud Public Edition Business sys-
tem ID
Host <xxxxx.cfapps.sap.hana.ondemand.com>
Path
/protocols/amqp10ws
Credential Name <EMS_Credential> (same credential that was used in the sender
tab)
Destination Type
Topic
Configuration of iFlows for replication of Equipment and Functional Location from SAP S/4HANA Cloud
Public Edition to SAP Cloud for Customer
Configuration of iFlows for replication of Equipment and Functional Location from SAP S/4HANA Cloud Public
Edition to SAP Cloud for Customer involves SAP Event Mesh service. Therefore, in the configuration EMS is the
sender. SAP S/4HANA Cloud Public Edition and SAP Cloud for Customer are both receivers:
• Replicate Registered Products from SAP Business Suite (Registered Product and Installation Point Replication
from SAP Business Suite)
• Replicate Installation Point from SAP Business Suite (Registered Product and Installation Point Replication
from SAP Business Suite)
These iFlows replicate created and changed equipments and installation points in SAP S/4HANA Cloud Public
Edition. In this iFlow configuration sender system is EMS service and receiver systems are SAP S/4HANA Cloud
Public Edition and SAP Cloud for Customer systems.
Communication User (More Tab) This is the technical User ID of the inbound communica-
tion user used in the Create Communication Arrangement
SAP_COM_0395 [page ] . To retrieve the technical User ID
please search the inbound communication user in the app
Maintain Communication Users in your SAP S/4HANA Cloud
Public Edition system.
Receiver Business System (More Tab) Enter your SAP C4C Business system ID
Sender Business System (More Tab) Enter your SAP S/4HANA Cloud Public Edition Business sys-
tem ID
Configuration of iFlows for replication of Equipment and Functional Location from SAP Cloud for Customer to
SAP S/4HANA Cloud Public Edition
Equipment_DataStore (More Tab) Give a unique name for the data store
FunctionalLocation_DataStore (More Tab) Give a unique name for the data store
In the Receiver tab, there are two receivers. Select the dropdown option for viewing the other receiver. Ensure to
configure SAP Cloud for Customer as receiver for replication confirmation messages.
Name of the iFlow (Descrip- Direction of the Message Sender Communication Sce- Receiver Communication
tion) Flow nario: Service Scenario: Service
Request Credit Account Data C4C (Sender) to S4 (Receiver) Retrieve Credit Account from SAP_COM_0173: Finance -
from SAP Business Suite SAP S/4HANA Cloud Private Credit Management Integra-
( Retrieve Credit Account from Edition and SAP S/4HANA tion
SAP S/4HANA Cloud Private Cloud Public Edition to show
Edition and SAP S/4HANA credit limits and usage for
Cloud Public Edition to show customers (Request Credit
credit limits and usage for Account Data from SAP Busi-
customers) ness Suite)
Request Invoice Accounting C4C (Sender) to S4 (Receiver) Retrieve Invoices from SAP SAP_COM_0303: Finance -
Documents from SAP Busi- S/4HANA Cloud Private Accounting Analytics Integra-
ness Suite ( Retrieve invoices Note Edition and SAP S/4HANA tion
from SAP S/4HANA Cloud Cloud Public Edition (Re-
It’s a synchronous replica-
Private Edition and SAP S/ quest Invoice Accounting
tion.
4HANA Cloud Public Edition) Documents from SAP Busi-
ness Suite)
Purpose
Note
Skip this section if you are implementing SAP Best Practices scope solution.
In case you are implementing the Intelligent Enterprise Suite (IES) Lead-to-Cash solution, refer to this section to
perform master data replication (for example: Business Partners). The IES Lead-to-Cash integration scenario uses
SAP Master Data Integration service to replicate business partner master data, which is described in the section.
SAP Master Data Integration serves as a central entry point for master data integration within the Intelligent Suite.
The subsequent chapters describe the integration of SAP Master Data Integration with SAP Cloud for Customer
for replication of business partner. Carry out the following configuration only if you choose to integrate business
partner via the SAP Master Data Integration service.
For information on the administration of SAP Master Data Integration, refer to the Administration guide.
You need to have administrator authorization on your account in order to set up Master Data Integration in your
subaccount.
Set Up Communication between SAP S/4HANA Cloud Public Edition and SAP
Master Data Integration
Prerequisite to create a service instance is to be included as a member of the space. Navigate to your
Subaccount select your space Members Add .
Follow the Administration Guide for SAP Master Data Integration for the configuration in SAP Master Data
Integration. This guide describes the steps you need to perform as an administrator to set up and run the SAP
Master Data Integration for business partners. It covers only application-specific information.
1. To create and set up the SAP Master Data Integration business system, refer to Prerequisites - Business System
Configuration.
Follow the steps required for the subscription process for SAP Master Data Integration Orchestration, and to
set up distribution models for the Business Partner SOAP APIs of the receiver system, refer to Creating MDO
Distribution Model for Business Partner Replication.
Set Up Communication between SAP Cloud for Customer and SAP Master Data
Integration
To perform settings in Master Data Integration tenant, you need to set up communication with SAP Cloud for
Customer, follow the Technical Setup in SAP Master Data Integration.
• Communication User
• Communication System
• Communication Arrangements
The following communication arrangements must be activated in SAP S/4HANA Cloud Public Edition for
communication with web services.
To find more information on communication management settings on your SAP S/4HANA Cloud Public Edition,
follow the link to Communication Management .
Prerequisite
To carry out the following activity, a business user with a business role needs to exist. The business role needs to
contain the business catalog SAP_CORE_BC_COM (Communication Management), for example, the business role
SAP_BR_ADMINISTRATOR (Administrator).
The communication user defined in the SAP S/4HANA Cloud Public Edition system is used for inbound
communication and processing messages in the system. Technically, the user is needed to call services in SAP
S/4HANA Cloud Public Edition.
Procedure
1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud Public Edition system.
2. Open Communication Systems.
3. Choose New to create a new system.
4. Enter the system ID and a system name of the SAP MDI client system.
Note
It is recommended that you set this value as the subdomain name of your SAP Business Technology
Platform subaccount in which you have created an MDI business partner service instance.
5. Choose Create.
6. In the Technical Data section, enter hostname of the SAP MDI system that you wish to integrate.
7. On your subaccount navigate to Instances and Subscriptions, choose any instance with service key and open
its service key, the host name is populated under the field “uri.”
8. Paste the hostname value in the Host Name field and provide value for the Logical System field. Additionally,
ensure that the value for Business System and System ID are the same.
9. To add inbound user to the business system, navigate to Users for Inbound Communication section and select
the Add button. Select the communication user that was created earlier and select OK.
10. The outbound user will be used to communicate with the MDI BuPa service. We are using basic authentication
for this setup. Refer to the the service keys of SCP Master Data for business partners instance created for
Note
Procedure
Tip
You can use the Value Help ( ) to search for a specific sce-
nario.
5. Choose Create.
Output
Service Path Replication Model Mode
Replication of product via Master Data Integration used the MDI Client Adapter on SAP S/4 HANA Cloud. You need
to create the following communication arrangements:
For configuration settings in SAP Cloud for Customer, refer to Prepackaged Integration with SAP Master Data
Integration on SAP Help Portal.
For configuration settings in SAP Cloud Integration for data services, refer to Prepackaged Integration with SAP
Master Data Integration on SAP Help Portal.
5.1 Initial Data Load from SAP S/4HANA Cloud Public Edition
Purpose
This section describes how to execute the initial data load of material and customer master data from your SAP
S/4HANA Cloud Public Edition system to the SAP Cloud for Customer system.
Note
The prerequisite is that the Organizational structure is already maintained in the SAP S/4HANA Cloud Private
Edition system.
1. Log on to your SAP S/4HANA Cloud Public Edition system as Administrator – Data Replication.
2. Under Data Replication, choose the app Replicate by Replication Model.
3. In the Replication Model field, select the organizational structure replication model (for example,
<SALES_ORG>).
4. In the Replication Mode section, select the Initialization radio button.
5. Click on the checkbox of Business Object to deselect all the business objects.
6. Select Sales Function Unit Business Object.
7. Choose Display Filter Criteria.
8. Choose Edit to adapt the filter criteria.
9. Under Main Filters section, choose SD MD Sales Organization (8SDMD_980). Under Filter Criteria section to
include Business Object.
10. Close the browser window and return to the Replicate by Replication Model screen.
11. Choose Replicate.
This replication can be checked in real time in the C4C system (Navigate: Administrator General
Settings , verify Org Structures under Company).
12. Repeat the steps 6–11 for the following business objects.
5.1.2 Plant
Prerequisite
The Plant master date is already maintained in the SAP S/4HANA Cloud Private Edition system.
Procedure
1. Log on to your SAP S/4HANA Cloud Public Edition system as Administrator – Data Replication.
2. Under Data Replication, choose the app Replicate by Replication Model.
3. In the Replication Model field, select the plant replication model (for example, <PLANT>).
4. In the Replication Mode section, choose the radio button Initialization.
5. Select Plant Business Object.
6. Choose Display Filter Criteria.
7. Choose Edit to adapt the filter criteria.
8. Under Main Filters section, choose Logistics MDR: Relevant plants (LMDR_PLANT).
9. Under Filter Criteria section for Business Object, add the Plant for the replication in the SAP Cloud for
Customer system.
Prerequisites
Ensure that credit segment data is maintained for the business partner in the SAP S/4HANA Cloud Public Edition
system. For example, use business partner 17100005. If this data isn’t maintained, you run into errors related to
credit check.
Note
You can restrict Customers sensitive tax numbers from replication between SAP Cloud for Customer and SAP
S/4HANA Cloud Public Edition by following the steps mentioned in chapter Restricting Tax Number in Business
Partner [page 89].
Procedure
1. Log on to your SAP S/4HANA Cloud Public Edition system as Administrator - Data Replication.
2. Under Data Replication, choose the app Replicate by Replication Model.
3. In the Replication Model field, select Business Partner Replication Model, for example <BPS4TOC4C>.
4. In the Replication Mode section, select the Initialization radio button.
5. Choose Display Filter Criteria.
6. Choose Edit to adapt the filter criteria.
7. Under the Main Filters section, choose the filter object BP Service Filter (OTC 986).
8. Under Filter Criteria for Business Objects section, choose Create.
9. If you want to replicate specific business partner, then enter the filter criteria as follows:
Note
ExternalID for Customer in SAP Cloud for Customer can be based on your settings of Default
Configurations in ID Mapping for Integration. By default, CustomerID is set as ExternalID.
Procedure
1. Log on to your SAP S/4HANA Cloud Public Edition system as Administrator - Data Replication.
2. Under Data Replication, choose the app Replicate by Replication Model.
3. In the Replication Model field, select Product Replication Model,
Example
<PROD_REP>.
8. Choose Save.
9. Close the browser window and return to Replicate by Replication by Model screen.
10. Choose Replicate.
Procedure
1. Log on to your SAP S/4HANA Cloud Public Edition system as Administrator - Data Replication.
2. Under Data Replication app, choose Replicate by Replication Model.
3. In the Replication Model field, select the exchange rate replication model
Example
<EXCH_RATE>.
8. Choose Save.
9. Close the browser window and return to Replicate by Replication Model screen.
10. Choose Replicate.
Note
You can also update the existing currency exchange rate manually by using the app Maintain Exchange Rate.
1. Log on to your SAP S/4HANA Cloud Public Edition system as Maintenance Planner.
2. Go to app Create Technical Object.
3. Choose Technical Object Type as Equipment from the dropdown.
4. Enter Technical Object Category. For example, S (Customer Equipment) and choose Continue.
5. Enter equipment data. The Mandatory data is as follows:
• General Data: Description
• Organizational Data: Partner Function (for example: <17100003>)
• Sales and Distribution: Sales Organization (for example: <1710 or 1010>), Distribution Channel, Division
• Additional Functions Show Serial Number Data: Material , for example, <TG11>, Serial Number.
6. Choose Save and note the Technical Object number which is the equipment number.
To initiate master data replication, log on to your SAP Cloud Integration tenant and deploy the iFlow Replicate
Registered Products from SAP Business Suite - Initial Load.
Note
To apply replication filter for this equipment configure the iFlow on the More tab, give Filter Condition as:
<Equipment eq 'Technical Object Number’> and deploy the iFlow to run it once.
Note
It is mandatory that the material and business partner master data that is used in the creation of the technical
objects (equipment and functional location) are already repli-cated to the C4C system before the technical
objects are replicated.
1. Log on to your SAP S/4HANA Cloud Public Edition system as Maintenance Planner.
2. Go to app Create Technical Object.
3. Choose Technical Object Type as Functional Location from the dropdown.
4. Enter Technical Object ID details in the same format as Edit Mask.
5. Select a Technical Object Category, for example: S.
6. Enter Functional Location data. The Mandatory data is as follows:
• General Data: Description
• Organizational Data: Partner Function (for example: <17100003>)
• Sales and Distribution: Sales Organization (for example: <1710 or 1010>), Distribution Channel, Division.
7. Choose Save and note the Technical Object data, which is the Functional Location ID.
8. To initiate master data replication, log on to your SAP Cloud Integration tenant and deploy the iFlow Replicate
Installation Point from SAP Business Suite - Initial Load.
Note
To apply replication filter for this functional location configure the iFlow on the More tab, give Filter
Condition as: <FunctionalLocation eq ‘Technical Object ID'> and deploy the iFlow to run it
once.
Use
This authorization is required to enable the business user <INTERNAL_SALES_REP> to monitor messages in the
SAP S/4HANA Cloud Public Edition system.
Prerequisite
To carry out the following activity, a business user (Administrator) with a business catalog role
SAP_CA_BC_COM_CONF_PC (Communication Management - Message Monitoring Configuration) is required.
Procedure
1. Log on to SAP Fiori launchpad in the SAP S/4HANA Cloud Public Edition system as an Administrator.
2. Under Message Monitoring, choose Assign Recipients to Users.
3. On the Assign Recipient screen, add your business user <INTERNAL_SALES_REP> using the + sign. Make the
following entries for Communication Arrangement SAP_COM_0025 and choose Assign:
• Namespace: /SDCFC
• Recipient for Alert: SDCFC_ALL
• Message Type: Application Error or Technical Error
• Include on Overview: Checked
Note
You can also assign this message monitoring authorization to multiple business users based on your
requirement.
4. • Choose Assign
5. Repeat the above steps for Communication ArrangementSAP_COM_0009
Use
The procedure describes how to monitor messages in the SAP S/4HANA Cloud Public Edition system.
Procedure
1. Log on to your SAP S/4HANA Cloud Public Edition system as a Business User <Internal Sales
Representative>, which you assigned as recipient.
2. Under Message Monitoring, choose Message Dashboard.
The Interface Monitor screen is displayed.
3. Use the Calendar Monitor to select the date range to view the triggered messages and choose Search.
4. In the Result List, select an interface and choose All Messages to display all messages for that interface,
5. To check the log, select the message entry. The log is displayed on the right-side of the screen.
6. Note
The error messages are automatically reprocessed by a background job. The frequency of the job run is set
to 5 minutes.
Additionally, you can manually reprocess the error message by choosing Reprocess.
You can also change the trace level of the interface to get a detailed log of the failed messages.
Component
CA-GTF-INT-CFC
1. Access the SAP S/4HANA Cloud Public Edition system and log on as an Administrator.
2. Choose Communication Systems from the ID Communication Management app.
3. Search for the System ID with system name Own System.
4. The System ID that appears in the search result is the SAP S/4HANA Cloud Public Edition system ID that is to
be used in SAP Cloud for Customer.
You can restrict sensitive customer data, for example tax data, from replicating between SAP Cloud for Customer
and SAP S/4HANA Cloud Public Edition.
Procedure
1. Connect to the tenant management node of the SAP Cloud Integration (SCI) system with the URL http://
<tenant management node URL>/itspaces.
2. Go to the Design tab, Choose the integration package you created for SAP Cloud for Customer Integration with
SAP S/4HANA Cloud Public Edition.
3. Choose the Artifacts tab of the package and choose the Artifact Value Mapping for SAP Cloud for Customer
Integration with SAP S/4HANA Cloud Public Edition by choosing Actions Configure .
4. Maintain the value mapping for the schema or agency: S4, Identifier:TaxCode to agency: S4, Identifier:
IgnoreTaxCode evaluating from a tax code type to true under Value Mappings for S4,
IgnoreTaxCode.
5. Maintain the sensitive tax code to be filtered, for example: DE1 under Value Mappings for S4, TaxCode.
6. Choose Save and deploy the Value Mapping.
Repeat these steps for all tax codes that you want to prevent from replicating between SAP S/4HANA Cloud Public
Edition and SAP Cloud for Customer.
Prerequisite
1. Deploy the iFlow: Replicate Material from SAP Business Suite (Valid for SAP S/4HANA Cloud Public Edition
Release 1511 – 1709).
2. Configure the Outbound Service for IDoc: Replicate Product from S/4 System to Client in Create
Communication Arrangement SAP_COM_0009 [page 42].
Procedure
1. Log on to your SAP S/4HANA Cloud Public Edition system as Administrator - Data Replication.
2. Under Data Replication, choose the app Replicate by Replication Model.
3. In the Replicate by Replication Model, select Prod Rep.
4. Create the following entries and choose Execute:
• Message Type: MATMAS_CFS
• Logical System: Enter the SAP Cloud for Customer tenant ID
• Material: Specify the material that is to be sent
• Send Material in Full: Select checkbox
Note
Currently, Create Communication Arrangement SAP_COM_0025 [page 39] does not support third-party
item category group for product replication. Please use product with standard item category for product
replication.
Purpose
For Single Sign-On, SAP Identity Authentication Services (IAS) should be part of your SAP S/4HANA Cloud Public
Edition License. You should raise a request to bundle the IAS with SAP Cloud for Customer, which is provisioned
with your SAP S/4HANA Cloud Public Edition instance.
For Single Sign-on, SAP Identity Authentication Services (IAS) should be part of your SAP S/4HANA Cloud Public
Edition License.
You should raise a request to bundle the same IAS with SAP Cloud for Customer, which is provisioned with your
SAP S/4HANA Cloud Public Edition instance.
Procedure
Example
https://myxxxxxxx-sso.vlab.sapbydesign.com/
.
18. Choose Save.
19. In Trust, Choose SAML 2.0 Configuration and Import the C4C metadata file you’ve downloaded earlier.
20.Choose Save.
21. Configure Name ID attribute as Login Name.
22. Choose Save.
23. Configure Default Name ID Format as Unspecified.
24. Choose Save.
25. Go Back to the home page and navigate to Users & Authorizations Import User .
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 an 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.
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.
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.