Set-Up Instructions | PUBLIC

SAP S/4HANA Cloud

2022-07-09

Setting Up Sales Scheduling Agreements (3NR)

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

THE BEST RUN

Content

1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Cloud-to-Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
2.2 Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Communication User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Communication Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Maintain Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 Configuration in SAP Integration (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Deploy Technical Communication User Data with Credential Artifact. . . . . . . . . . . . . . . . . . . . . . . . . 8
Deployment and Configuration of Integration Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.4 Configuration in S/4HANA Cloud. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Application Related Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Define Mapping for Inbound Texts for Integration with Buyers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
BRF+Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Assign Recipients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Maintain Customer Material （Optional）. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3 On-Premise-to-Cloud Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

3.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.2 Configuration in SAP S/4HANA Cloud. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Application-Related Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Communication-Related Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.3 Set Up On-Premise to SAP Integration Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configure PSE for Certificate-Based Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Export the SAP On-Premise System Public Certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Cloud Integration User for Basic Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.4 Set Up SAP CIntegration to SAP On-Premise Certificate-Based Authentication. . . . . . . . . . . . . . . . . . . 44
Create SAP On-Premise System User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Configure SSL Client Certificates for On-Premise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.5 Configuration in SAP Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Deploy Technical Communication User Data with Credential Artifact. . . . . . . . . . . . . . . . . . . . . . . . 46
Deployment and Configuration of Integration Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Developing and Deploying Mapping Extensions for Integration Package. . . . . . . . . . . . . . . . . . . . . . 59
3.6 Troubleshooting and Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
SAP Ingergration Message Analyze. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Setting Up Sales Scheduling Agreements (3NR)

2 PUBLIC Content
 AIF Message Dashboard log Analyze. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.7 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Ticket Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Setting Up Sales Scheduling Agreements (3NR)

Content PUBLIC 3
1 Purpose

This document describes additional configuration steps that must be carried out by customers to activate the
Integration of SAP S/4HANA Sales Scheduleing Agreement (3NR) scope item. Since these configuration steps are
customer-specific, they cannot be delivered by SAP and must be carried out by the customer.

Setting up this scenario depends on the type of the buyer system. If the buyer system is an SAP S/4HANA cloud
system, follow the instructions in the Cloud-to-Cloud Integration chapter. The chapter describes how you can
implement the cloud-to-cloud deployment option without the SAP Integration middleware in between, as depicted
in the following figure:

If the buyer
system is an SAP on-premise system, follow the instructions in the Cloud-to-On-Premise Integration chapter. With
this deployment option, you will implement the integration of the SAP S/4HANA Sales system with an SAP S/
4HANA or SAP ERP Buyer on-premise system through SAP Integration as depicted in the following figure:

Setting Up Sales Scheduling Agreements (3NR)

4 PUBLIC Purpose
2 Cloud-to-Cloud Integration

2.1 Preparation

2.1.1 Prerequisites

It is mandatory that Sales Scheduling Agreements(3NR)Scope Item is active.

Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options to
check the status:

● Manage Your Solution:

In the SAP S/4HANA Cloud system, in the SAP Fiori launchpad, open the Manage Your Solution app and go to
View Solution Scope.
● SAP Central Business Configuration:
In the Scope and Organizational Structure phase, navigate to the Activities tab. Search for Define Scope and
choose Open.

If the scope item is not active, request the activation through BCP – Ticket Component: XX-S4C-OPR-SRV.

During the activities described in this guide, you are required to enter or provide system-specific information. To
ensure a smooth and efficient integration to SAP S/4HANA, ensure that you have the information listed in the
following table before starting the integration process.

Required Required Information

SAP S/4HANA Clooud System System details such as URL, Username, and Password

 Note
These are just examples since details depend on the
actual supplier system. Liaise with your supplier to get the
required system information.

Buyer System System details, such as host name, URLs, URIs, Username,
and Password

2.2 Communication Arrangement

You must activate a communication arrangement in SAP S/4HANA for communication with Web services.

Setting Up Sales Scheduling Agreements (3NR)

Cloud-to-Cloud Integration PUBLIC 5
2.2.1 Communication User

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Choose Communication Management Maintain Communication Users .
3. Choose New.
4. Enter User Name, Description, and Password.
5. Choose Create.

2.2.2 Communication Systems

Purpose

In this activity, you can define a communication system.

Procedure

1. Start the Communication Systems by choosing Communication Management Communication Systems .

2. Choose New to create a communication system.
3. On the New Communication System screen, make the following entries:
○ ID: <EDI_Integration_Supplier>
○ System Name: <EDI_Integration_Supplier>
4. Choose Create.
5. On the Communication Systems screen, make the following entries:
○ Host Name: <Buyer System>, for example, sysID-Client-api
○ Logical System: Buyer_Logical System

 Note

If using CPI to set up connection, the logic system will be empty.

6. Under Business Partner, choose Add to add the Supplier Business Partner ID, for example, 10100003.
7. In the Usewr for Inbound Communication area, choose Add.

Setting Up Sales Scheduling Agreements (3NR)

6 PUBLIC Cloud-to-Cloud Integration
  Note

The Inbound Communication User mentioned in the procedure here must be used as an Outbound
Communication User in the buyer system.

8. On the New Inbound Communication User screen, enter the following details:
○ User Name: <User name that you have created eariler>
○ Authentication Method: User Name and Password
9. Choose OK.
10. In the User for Outbound Communication area, choose Add.
11. On the New Outbound Communication User screen, enter the following details:
○ User Name: <Inbound Communication User details provided by the buyer>
○ Password: <Password>
○ Authentication Method: User Name and Password
12. Choose OK and then save.

2.2.3 Maintain Communication Arrangement

Purpose

In this activity, you can maintain communication arrangements.

Procedure

1. Select Communication Management Communication Arrangements .

2. Open Communication Arrangement app.
3. Choose New.
4. On the Coimmunication Arrangement screen, make the following entries:
○ Scenario: SAP_COM_0444 (Sales with Buyers Integration)
5. Choose Create.
6. On the Communication Arrangement screen, make the following entries:
○ Communication System： <Select the communication system you have created earlier, for
example, EDI_Integration_Supplier.
7. Maintain the paths for the following services:
○ Outbound Services:

Setting Up Sales Scheduling Agreements (3NR)

Cloud-to-Cloud Integration PUBLIC 7
 Service Path

Outbound Delivery - Notify (B2B) /sap/bc/srt/scs_ext/sap/deliveryrequest_in

Customer Invoice- Send (B2B) /sap/bc/srt/scs_ext/sap/invoicerequest_in

8. The system now automatically updates default information from the communication system and
communication scenario. For example, user IDs as well as inbound and outbound services.
9. Choose Save.

2.3 Configuration in SAP Integration (Optional)

 Note

This is only Relevant to CPI relevant system set-up.

To work with the integration flows of this package, copy the prepackaged integration flow scenario to your
workspace. Then configure the integration flows. Finally, to activate the integration flows, deploy them.

To carry out configuration in the S/4HANA Cloud Integration, the URL of your Cloud Integration tenant is required.
This URL is provided by the Cloud Integration tenant provisioning mail.

2.3.1 Deploy Technical Communication User Data with

Credential Artifact

Purpose

 Note

Due to security reasons, we do not recommend user-based or password-based authentication. If it is

certificate-based authentication for the SAP S/4HANA Cloud buyer system, you can skip this chapter.

Procedure

1. Open the Cloud Integration tenant Web UI, for example, https://<your Cloud Integration tenant
URL>/itspaces.
2. In the tenant menu, choose Monitor.

Setting Up Sales Scheduling Agreements (3NR)

8 PUBLIC Cloud-to-Cloud Integration
 3. Choose the Security Material in the Manage Security Material section.
4. Choose Add.
5. Select User Credentials.
6. Enter the following values in the Add Users Credential dialog box:
Supplier Cloud System Crtedenials:

Field Name Value

Name <s4cesupplier_credential>

Description <Optional>

User <User Alias Name of your technical user>

Password <Password of your technical user>

Buyer On_Premise System Credentials:

Field Name Value

Name <opbuyer_credential>

Description <Optional>

User <User Alias Name of your technical user>

Password <Password of your technical user>

User Credentials of User Account Used for Mail Notification (Optional):

Field Name Value

Name <MailUserCredential>

Description <Optional>

User <User Alias Name of your mail account>

Password <Password of your user>

7. Choose OK to save the user credentials.

2.3.2 Deployment and Configuration of Integration Package

2.3.2.1 Copying Integration Package from Content Catalog

Procedure

1. Open the Cloud Integration tenant Web UI, for example, https://<your SAP Integration tenant
URL>/itspaces.
2. In the tenant menu, choose Discover.
3. Select All to see all the published integration packages.

Setting Up Sales Scheduling Agreements (3NR)

Cloud-to-Cloud Integration PUBLIC 9
4. Search for the Integration package name Integration of SAP S/4HANA Cloud for Sales Scheduling Agreement
with SAP S/4HANA or SAP ERP.
5. Choose the package to display the package content.
6. To copy the integration package of the catalog to your customer workspace, choose Copy Package in the upper
right corner.
7. In the tenant menu, choose Design.
8. On the Design tab page, select the integration package that you copied.
An overview of the artifacts available in the selected integration package is displayed. The following list is
provided:
○ Receive Customer Invoice: For Invoice processing
○ Advance Shipping Notification: For outbound delivery processing
○ Update Sales Scheduling Agreement: For sales scheduling agreement processing
○ ValueMapping_TextID_SalesSchedulingAgreement: Value mapping for text processing

2.4 Configuration in S/4HANA Cloud

Setting up the connection between buyer and supplier using EDI requires some basic configuration activities as
described in the following chapters.

2.4.1 Application Related Settings

To configure the EDI integration, users require the following catalog roles in S/4HANA Cloud:

● Application Role – Business Network Integration (SAP_BR_CONF_EXPERT_BUS_NET_INT)

● Internal Sales Representative (SAP_BR_INTERNAL_SALES_REP)
● Administrator (SAP_BR_ADMINISTRATOR)
● Master Data Specialist - Business Partner Data (SAP_BR_BUPA_MASTER_SPECIALIST)

2.4.1.1 Convert External to Internal Partner Number

Purpose

In this Customizing activity, you map the External Partner number to Internal Partner number.

Setting Up Sales Scheduling Agreements (3NR)

10 PUBLIC Cloud-to-Cloud Integration
Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Choose Sales Scheduling Agreement Master Data Assign Sold-to Parties .
○ On the list page of the fiori app, you can see all the processing options that are saved in database as well as
the draft processing options.
3. On click of Create (+), you can create a new Sold-to Party assignment with Supplier, Partner Description,
Unloading Point and valid Sold-to Party.
4. Choose +, and enter the following details:

Fields Example Values

Supplier 10300001 (any text up to 17 characters)

Partner Description Enter Buyer Plant: 1010 (any text up to 30 characters)

(Buyer Plant number)

Unloading Point

Sold-to Party 10100003 (invalid Sold-to Party or empty Sold-to Party will
result in error)

5. Choose Save (ensure that the supplier, Partner Description, unloading point combination is unique).

2.4.1.2 Define Delivery Schedule EDI Processing Options

Purpose

In this master data fiori app, you can define Sold-to Party and Unloading Point and also configure the behavior of
Check purchase order number and unloading point.

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Choose Sales Scheduling Agreement Master Data Manage Delivery Schedule Processing .
○ On the list page of the fiori app, you can see all the processing options that are saved in database as well as
the draft processing options.
3. On click of Create (+), you can create a new processing option with valid Sold-to Party and enter an unloading
point. You can also maintain the check for purchase order number and unloading point. Unloading point is
optional.
4. Choose +, and enter the following details:

Setting Up Sales Scheduling Agreements (3NR)

Cloud-to-Cloud Integration PUBLIC 11
 Fields Example Values

Sold-to Party 10100003 (invalid Sold-to Party or empty Sold-to Party will
result in error)

Unloading Point

Check Purchase Order Number PO number check (No Update) (X)

Check Unloading Point No Processing

5. Choose Save (ensure that the supplier, plant, unloading point combination is unique).

2.4.1.3 Maintain Partner Description to Sold-to Parties

Purpose

In this Customizing activity, maintain the Partner Description to Sold-to Partners.

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Choose Customer Master Manage Customer Master Data .
3. On the list page of the fiori app, choose the Business Partner Number, such as 10100003 for DE, 17100003 for
US.
4. Choose Go and select the customer entry.
5. On the screen of Customer, choose Edit, navigate to Sales Areas tab, choose the line of sales organization, for
example, 1010 for DE, 1710 for US.
6. On the Sales Area screen, navigate to Partner Functions tab , make following entries:

Partner Roles Partner Descriptions

SH (Ship-to Party) 1010 (or other buyer plant)

7. Choose Apply and choose Save.

Setting Up Sales Scheduling Agreements (3NR)

12 PUBLIC Cloud-to-Cloud Integration
2.4.1.4 Maintain Account at Customer

Purpose

In this Customizing activity, maintain the Account at Customer to Sold-to Partners.

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Choose Customer Master Manage Customer Master Data .
3. On the list page of the Fiori app, choose the Business Partner Number, such as 10100003 for DE, 17100003 for
US.
4. Choose Go and select the customer entry.
5. On the screen of Customer, choose Edit, navigate to Company Codes tab, choose the line of company code, for
example, 1010 for DE, 1710 for US.
6. On the Company Code screen, navigate to Correspondence tab , make following entries:

Field Field Value

Account at Customer 10300001 (or other Supplier ID from Buyer sys-tem)

7. Choose Apply and choose Save.

2.4.2 Define Mapping for Inbound Texts for Integration with

Buyers

Purpose

An external buyer system might send long texts relevant for the supplier using the SOAP service interface. For
example, a purchase order message sent from the external buyer system can contain texts that need to be stored
with the corresponding sales order in the supplier system.

For integration with the external buyer system, you can define the mapping between the inbound SOAP service text
types and the text IDs in the supplier's SAP S/4HANA Cloud system.

Setting Up Sales Scheduling Agreements (3NR)

Cloud-to-Cloud Integration PUBLIC 13
Procedure

Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:

Configure Your Solution:

Test Pass / Fail / Com­

Step # Test Step Name Instruction Expected Result ment

1 Log On Log on to the SAP Fiori launchpad as a The SAP Fiori launch­
BPC_EXPERT . pad displays.

2 Access the App Open .

3 Open Configure Your Choose Configure Your Solution.

Solution
 Note
To create country-/region-dependent set­
tings for the intended local version, choose
Set Local Version.

5 Go to Configuration Choose Define Mapping for Inbound Texts for

Details Integration with Buyers.

Setting Up Sales Scheduling Agreements (3NR)

14 PUBLIC Cloud-to-Cloud Integration
 Test Pass / Fail / Com­
Step # Test Step Name Instruction Expected Result ment

6 Change item cate­ Choose New Entries. You can create your own
gory assignment entries as shown in the following examples, and
choose Save:

XML XML
Msg. Text
Type Txt.Obj. Type TxSch ID

Schedu­ Header Sales T3 TX11

lingA­ Note
gree­
mentRe­
quest

Schedu­ Header Pick T3 TX07

lingA­ Pack In­
gree­ struc­
mentRe­ tions
quest

Schedu­ Item Pick T3 TX07

lingA­ Pack In­
gree­ struc­
mentRe­ tions
quest

Schedu­ Item Ship­ T3 TX13

lingA­ ping In­
gree­ struc­
mentRe­ tions
quest

Schedu­ Header Ship­ T3 TX13

lingA­ ping In­
gree­ struc­
mentRe­ tions
quest

SAP Central Business Configuration:

Test Step Pass / Fail / Com­

# Test Step Name Instruction Expected Result ment

1 Log on Log on to the project experience in SAP Central The SAP Fiori
Business Configuration. launchpad displays.

Setting Up Sales Scheduling Agreements (3NR)

Cloud-to-Cloud Integration PUBLIC 15
Test Step Pass / Fail / Com­
# Test Step Name Instruction Expected Result ment

2 Open Active Flexi­ In the Realize phase, navigate to the

ble Workflow Configuration Activities tab and search for the
following activity: Define Mapping for Inbound
Texts for Integration with Buyers.

Choose the line item in the search result to see

more details about this configuration activity.

Choose the Go to Activity button to navigate di­

rectly to the SAP S/4HANA Cloud system. Log
on to the SAP Fiori launchpad as a .

3. Check Flexible Choose New Entries. You can create your own
Workflow for PO entries as shown in the following examples, and
Approval choose Save:

XML
Msg. XML Text
Type Txt.Obj. Type TxSch ID

Schedu­ Header Sales T3 TX11

lingA­ Note
gree­
mentRe­
quest

Schedu­ Header Pick T3 TX07

lingA­ Pack In­
gree­ struc­
mentRe­ tions
quest

Schedu­ Item Pick T3 TX07

lingA­ Pack In­
gree­ struc­
mentRe­ tions
quest

Schedu­ Item Shipping T3 TX13

lingA­ Instruc­
gree­ tions
mentRe­
quest

Schedu­ Header Shipping T3 TX13

lingA­ Instruc­
gree­ tions
mentRe­
quest

Setting Up Sales Scheduling Agreements (3NR)

16 PUBLIC Cloud-to-Cloud Integration
2.4.3 BRF+Settings

Purpose

In BRF+, you set parameters that control the output from SAP S/4HANA.

2.4.3.1 BRF+ Settings for Advance Shipping Notice

Purpose

In this Customizing activity, you define how the system determines output parameters for Advance Shipping Notice
(ASN).

Prerequisites

You must have the user and password along with authorization to access the S/4HANA cloud system.

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Access the App Open Output Parameter The Output Parameter

Determination. Determination screen
displays.

Setting Up Sales Scheduling Agreements (3NR)

Cloud-to-Cloud Integration PUBLIC 17
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

2 Output Type In the Select Business Details are displayed in

Rules section, enter the the Maintain Business
required details: Rules section.

Show Rules for:

Outbound
Delivery

Determination Step:
Output Type

3 Add Rules Expand the Maintain

Business Rules section.
Choose Edit. In Table
Contents, choose Insert
New Row and enter the
following:

● #: <next
higher
number>
● Delivery Type:
<blank>
● Output Type:
DELIVERY_NOT
E(Delivery
Note)
● Dispatch Time: 1
(Immediately)

4 Activate Choose Activate( Ctrl Rules are activated.

+ A ).

5 Receiver Determination Step: Details are displayed in

the Maintain Business
Receiver
Rules section.

Setting Up Sales Scheduling Agreements (3NR)

18 PUBLIC Cloud-to-Cloud Integration
 Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

6 Add Rules Expand the Maintain

Business Rules section,
and choose Edit. In
Table Contents, choose
Insert New Row and en­
ter the following:

● #: <next
higher
number>
● Output Type:
blank
● Role: WE
● Exclusive Indicator:
False

7 Activate Choose Activate ( Ctrl Rules are activated.

+ A ).

8 Channel Determination Step: Details are displayed in

Channel the Maintain Business
Rules section.

9 Add Rules Expand the Maintain

Business Rules section.

Choose Edit.

In the Table Contents

section, choose +
(Insert New Row).

Make the following en­

tries:

● #: <next
higher
number>
● Output Type:
DELIVERY_NOT
E(Delivery
Note)
● Role: WE
● Receiver ID:
<blank>
● Channel: EDI

Setting Up Sales Scheduling Agreements (3NR)

Cloud-to-Cloud Integration PUBLIC 19
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

10 Activate Choose Activate ( Ctrl Rules are activated.

+ A ).

11 Output Relevance Determination Step: Details are displayed in

Output Relevance the Maintain Business
Rules section.

12 Add Rules Expand the Maintain

Business Rules section.

Choose Edit.

In the Table Contents

section, choose +
(Insert New Row).

Make the following en­

tries:

● #: <next
higher
number>
● Output Type:
DELIVERY_NOT
E(Delivery
Note)
● Document Cat.:
J(Delivery)
● TotalGdsMvtStat: C
(Completely
processed)
● Relevance
Indicator: X
(True)

2.4.3.2 BRF+ Settings for Billing Document (Supplier Invoice)

Purpose

In this Customizing activity, you define how the system determines output parameters for Supplier invoice.

Setting Up Sales Scheduling Agreements (3NR)

20 PUBLIC Cloud-to-Cloud Integration
Prerequisites

You must have the user and password along with authorization to access the SAP S/4HANA cloud system.

Procedure

Test Step Pass / Fail / Com­

Test Step # Name Instruction Expected Result ment

1 Access the Open Output Parameter Determination. The Output

App Parameter
Determination
screen displays.

2 Output In the Select Business Rules section, enter the re­ Details are displayed
Type quired details: in the Maintain
Business Rules sec­
Show Rules for: Billing Document
tion.
Determination Step: Output Type

3 Add Rules Expand the Maintain Business Rules section.

Choose Edit. In Table Contents, choose Insert New
Row and enter the following:

● #: <next higher number>

● Delivery Type: <blank>
● Output Type:
BILLING_DOCUMENT(Billing
Document)
● Dispatch Time: 1 (Immediately)

4 Activate Choose Activate( Ctrl + A ). Rules are activated.

5 Receiver Determination Step: Receiver Details are displayed

in the Maintain
Business Rules sec­
tion.

Setting Up Sales Scheduling Agreements (3NR)

Cloud-to-Cloud Integration PUBLIC 21
 Test Step Pass / Fail / Com­
Test Step # Name Instruction Expected Result ment

6 Add Rules Expand the Maintain Business Rules section, and

choose Edit. In Table Contents, choose Insert New
Row and enter the following:

● #: <next higher number>

● Output Type:
BILLING_DOCUMENT(Billing
Document)
● Role: RE
● Exclusive Indicator: false

7 Activate Choose Activate ( Ctrl + A ). Rules are activated.

8 Channel Determination Step: Channel Details are displayed

in the Maintain
Business Rules sec­
tion.

9 Add Rules Expand the Maintain Business Rules section.

Choose Edit.

In the Table Contents section, choose + (Insert

New Row).

Make the following entries:

● #: <next higher number>

● Output Type:
BILLING_DOCUMENT(Billing
Document)
● Role: <blank>
● Receiver ID: BILL-TO PARTY (Example for
US is 17100003 and for DE is 10100003)
● Channel: EDI

10 Activate Choose Activate ( Ctrl + A ). Rules are activated.

11 Output Determination Step: Output Relevance Details are displayed

Relevance in the Maintain
Business Rules sec­
tion.

Setting Up Sales Scheduling Agreements (3NR)

22 PUBLIC Cloud-to-Cloud Integration
 Test Step Pass / Fail / Com­
Test Step # Name Instruction Expected Result ment

12 Add Rules Expand the Maintain Business Rules section.

Choose Edit.

In the Table Contents section, choose + (Insert

New Row).

Make the following entries:

● #: <next higher number>

● Output Type:
BILLING_DOCUMENT(Billing
Document)
● Posting Status: C (Posting document
has been created)
● Relevance Indicator: X (True)

13 Activate Choose Activate ( Ctrl + A ). Rules are activated.

2.4.4 Assign Recipients

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Select Message Monitoring Assign Recipients to Users .
3. On the Assign Recipients to User screen, Choose Add User.
4. On the Add User screen, enter your Name or ID, for example, CONF_EXPERT_BUS_NET_INT, then Choose Add.
5. If the user to be assigned to recipients already exists, directly choose the user in the left area, then on the right
Recipients for User screen, choose Assign.
6. In the Assign Receiptents dialog box enter below entries and choose Assign.

Nameapcace Recipient Name Message Type Include on Overview Tech. User

/SDSAR EDI_SD_SCHEDGAGR Application Error or Set flag Set flag

MT_RECIPIENT Technical Error

7. Choose Assign.
8. Repeat the steps from 5 to 7 for both Namespace and Recipient for Alert.

Namespace Recipient for Alert

/SDEDI EDI_SD_INVC_RECIPIENT

Setting Up Sales Scheduling Agreements (3NR)

Cloud-to-Cloud Integration PUBLIC 23
 Namespace Recipient for Alert

/LEEDI EDI_DELOUT_RECIPIENT

2.4.5 Maintain Customer Material （Optional）

Purpose

 Note

If the customer-masterial info record already exists, or if you want to maintain the customer

material manually when creating the scheduling agreement, you may skip the step.

This chapter is about master data maintenance and does not refer to a customizing activity.

In this activity, you maintain unique customer-specific names for your company's products.

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system with role
SAP_BR_INTERNAL_SALES_REP.
2. Choose Manage Customer Materials.
3. Choose Create Object.
4. Enter Customer, Product, Sales Organization, Distribution Channel, and Customer Material.
5. Choose Save.
For each material that customers order through EDI, you maintain a customer material. The customer material
maps the ID, which the customer uses for the material ordered, to a material.

Setting Up Sales Scheduling Agreements (3NR)

24 PUBLIC Cloud-to-Cloud Integration
3 On-Premise-to-Cloud Integration

Follow the instructions in this chapter only if the buyer system is an SAP on-premise system that you connect with
through SAP Cloud Integration.

3.1 Prerequisites

It is mandatory that Sales Scheduling Agreements(3NR)Scope Item is active. You can check this in the Manage Your
Solution App under View Solution Scope.

If the scope item is not active, request the activation through BCP – Ticket Component: XX-S4C-OPR-SRV.

During the activities described in this guide, you are required to enter or provide system-specific information. To
ensure a smooth and efficient integration to SAP S/4HANA, ensure that you have the information listed in the
following table before starting the integration process:

Required Required Information

SAP S/4HANA Cloud Platform Integration System System details such as URL, Username, and Password

 Note
These are just examples since details depend on the
actual supplier system. Liaise with your supplier to get the
required system information.

Buyer System System details, such as host name, URLs, URIs, Username,
and Password

Supplier System System details such as host name, URLs, URIs, User, and
Password

 Note
These are just examples since details depend on the
actual supplier system. Liaise with your supplier to get the
required system information.

To configure the EDI integration, users require the following business roles in S/4HANA Enterprise Cloud:

● Configuration Expert – Business Network Integration (SAP_BR_CONF_EXPERT_BUS_NET_INT)

● Configuration Expert – Business Process Configuration (SAP_BR_BPC_EXPERT)
● Master Data Specialist - Business Partner Data (SAP_BR_BUPA_MASTER_SPECIALIST)
● Internal Sales Representative (SAP_BR_INTERNAL_SALES_REP)

For more information about how to manage business users and business roles, see Identity and Access
Management in the SAP Help Portal.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 25
SAP Cloud Connector for Integration with On-Premise Systems

For all scenarios integrating SAP S/4HANA Cloud with SAP On-Premise scenarios, the SAP_COM_0200 – Cloud
Connector communication arrangement must be activated. This is a prerequisite for all other communication
arrangements.

To check if the SAP_COM_0200 – Cloud Connector communication arrangement is active in your system, go to the
Maintain Communication Arrangements app. If it is not active, you must set it up.

To set up the communication scenario, follow the procedure under Integrating SAP Cloud Connector.

3.2 Configuration in SAP S/4HANA Cloud

3.2.1 Application-Related Settings

3.2.1.1 Assign Sold-to Parties for EDI Processing

Purpose

In this master data fiori app, you can define Supplier, Partner Description, Unloading Point and Sold-to Party.

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Choose Sales Scheduling Agreement Master Data Assign Sold-to Parties .
○ On the list page of the fiori app, you can see all the processing options that are saved in database as well as
the draft processing options.
3. On click of Create (+), you can create a new Sold-to Party assignment with Supplier, Plant, Unloading Point and
valid Sold-to Party.
4. Choose +, and enter the following details:

Fields Example Values

Supplier 10300001 (any text up to 17 characters)

Partner Description Plant in buyer system

Unloading Point 101A (any text up to 25 characters) (Optional Field)

Sold-to Party 10100003 (invalid Sold-to Party or empty Sold-to Party)

Setting Up Sales Scheduling Agreements (3NR)

26 PUBLIC On-Premise-to-Cloud Integration
 5. Choose Save (ensure that the supplier, Partner Description, unloading point combination is unique).

3.2.1.2 Define Delivery Schedule EDI Processing Options

Purpose

In this master data fiori app, you can define Sold-to Party and Unloading Point and also configure the behavior of
Check purchase order number and unloading point.

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Choose Sales Master Data Manage Delivery Schedule Processing .
○ On the list page of the fiori app, you can see all the processing options that are saved in database as well as
the draft processing options.
3. On click of Create (+), you can create a new processing option with valid Sold-to Party and enter an unloading
point. You can also maintain the check for purchase order number and unloading point. Unloading point is
optional.
4. Choose +, and enter the following details:

Fields Example Values

Sold-to Party 10100003 (invalid Sold-to Party or empty Sold-to Party will
result in error)

Unloading Point 101A (any text up to 25 characters)(Optional Field)

Check Purchase Order Number PO number check (No Update) (X)

Check Unloading Point No Processing

5. Choose Save (ensure that the supplier, plant, unloading point combination is unique).

3.2.1.3 Maintain Partner Description to Sold-to Parties

Purpose

In this Customizing activity, maintain the Partner Description to Sold-to Partners.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 27
Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Choose Customer Master Manage Customer Master Data .
3. On the list page of the fiori app, Choose the Business Partner Number, such as 10100003 for DE, 10100007 for
US.
4. On the screen of Customer, Choose Edit, navigate to Sales Areas tab, choose the line of sales organization, for
example, 1010 for DE, 1710 for US.
5. On the Sales Area screen, navigate to Partner Functions tab , make following entries:

Partner Roles Partner Descriptions

SH 1010 (or other buyer plant)

6. Choose Apply and Choose Save.

3.2.1.4 Define Mapping for Inbound Texts for Integration with

Buyers

Purpose

An external buyer system might send long texts relevant for the supplier using the SOAP service interface. For
example, a scheduling agreement message sent from the external buyer system can contain texts that need to be
stored within the corresponding scheduling agreement in the supplier system.

For integration with the external buyer system, you can define the mapping between the inbound SOAP service text
types and the text IDs in the supplier's SAP S/4HANA Cloud system.

Procedure

Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:

Configure Your Solution:

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Choose Implementation Cockpit Manage Your Solution Configure Your Solution .
3. On the Configure Your Solution: Realize Phase screen, make the following entries:
○ Application Area: Sales
○ Sub Application Area: Blank
4. In the Configuration Item area, choose the entry that has these values and also the Name as Integration
with Buyers.

Setting Up Sales Scheduling Agreements (3NR)

28 PUBLIC On-Premise-to-Cloud Integration
 5. On the Configure Your Solution: Integration with Buyers screen area, choose the Configuration Steps tab.
6. Search for Define Mapping for Inbound Texts for Integration with Buyers and choose Configure.
7. Choose New Entries. You can create your own entries as shown in the following examples:

XML Msg. Type Txt.Obj. XML Text Type TxSch ID

SchedulingAgreement Header Sales Note T3 TX11

Request

SchedulingAgreement Item Pick Pack Instructions T3 TX07

Request

SchedulingAgreement Item Pick Pack Instructions T3 TX07

Request

SchedulingAgreement Item Shipping Instructions T3 TX13

Request

SchedulingAgreement Header Shipping Instructions T3 TX13

Request

8. Choose Save.

SAP Central Business Configuration:

1. Log on to the project experience in SAP Central Business Configuration..

2. In the Product-Specific Configuration phase, navigate to the Configuration Activities tab and search for the
following activity: Define Mapping for Inbound Texts for Integration with Buyers.
Choose the line item in the search result to see more details about this configuration activity.
Choose the Go to Activity button to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP
Fiori launchpad as a Configuration Expert - Business Process Configuration.
3. Choose New Entries. You can create your own entries as shown in the following examples:

XML Msg. Type Txt.Obj. XML Text Type TxSch ID

SchedulingAgreement Header Sales Note T3 TX11

Request

SchedulingAgreement Item Pick Pack Instructions T3 TX07

Request

SchedulingAgreement Item Pick Pack Instructions T3 TX07

Request

SchedulingAgreement Item Shipping Instructions T3 TX13

Request

SchedulingAgreement Header Shipping Instructions T3 TX13

Request

4. Choose Save.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 29
3.2.1.5 BRF+Settings

Purpose

In BRF+, you set parameters that control the output from SAP S/4HANA.

3.2.1.5.1 BRF+ Settings for Advance Shipping Notice

Purpose

In this Customizing activity, you define how the system determines output parameters for Advance Shipping Notice
(ASN).

Prerequisites

You must have the user and password along with authorization to access the S/4HANA cloud system.

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Access the App Open Output Parameter The Output Parameter

Determination. Determination screen
displays.

Setting Up Sales Scheduling Agreements (3NR)

30 PUBLIC On-Premise-to-Cloud Integration
 Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

2 Output Type In the Select Business Details are displayed in

Rules section, enter the the Maintain Business
required details: Rules section.

Show Rules for:

Outbound
Delivery

Determination Step:
Output Type

3 Add Rules Expand the Maintain

Business Rules section.
Choose Edit. In Table
Contents, choose Insert
New Row and enter the
following:

● #: <next
higher
number>
● Delivery Type:
<blank>
● Output Type:
DELIVERY_NOT
E(Delivery
Note)
● Dispatch Time: 1
(Immediately)

4 Activate Choose Activate( Ctrl Rules are activated.

+ A ).

5 Receiver Determination Step: Details are displayed in

the Maintain Business
Receiver
Rules section.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 31
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

6 Add Rules Expand the Maintain

Business Rules section,
and choose Edit. In
Table Contents, choose
Insert New Row and en­
ter the following:

● #: <next
higher
number>
● Output Type:
blank
● Role: WE
● Exclusive Indicator:
False

7 Activate Choose Activate ( Ctrl Rules are activated.

+ A ).

8 Channel Determination Step: Details are displayed in

Channel the Maintain Business
Rules section.

9 Add Rules Expand the Maintain

Business Rules section.

Choose Edit.

In the Table Contents

section, choose +
(Insert New Row).

Make the following en­

tries:

● #: <next
higher
number>
● Output Type:
DELIVERY_NOT
E(Delivery
Note)
● Role: WE
● Receiver ID:
<blank>
● Channel: EDI

Setting Up Sales Scheduling Agreements (3NR)

32 PUBLIC On-Premise-to-Cloud Integration
 Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

10 Activate Choose Activate ( Ctrl Rules are activated.

+ A ).

11 Output Relevance Determination Step: Details are displayed in

Output Relevance the Maintain Business
Rules section.

12 Add Rules Expand the Maintain

Business Rules section.

Choose Edit.

In the Table Contents

section, choose +
(Insert New Row).

Make the following en­

tries:

● #: <next
higher
number>
● Output Type:
DELIVERY_NOT
E(Delivery
Note)
● Document Cat.:
J(Delivery)
● Goods Mvmnt Sts:
C (Completely
processed)
● Relevance
Indicator: X
(True)

3.2.1.5.2 BRF+ Settings for Billing Document (Supplier

Invoice)

Purpose

In this Customizing activity, you define how the system determines output parameters for Supplier invoice.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 33
Prerequisites

You must have the user and password along with authorization to access the SAP S/4HANA cloud system.

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

1 Access the App Open Output Parameter The Output Parameter

Determination. Determination screen
displays.

2 Output Type In the Select Business Details are displayed in

Rules section, enter the the Maintain Business
required details: Rules section.

Show Rules for:

Billing Document

Determination Step:
Output Type

3 Add Rules Expand the Maintain

Business Rules section.
Choose Edit. In Table
Contents, choose Insert
New Row and enter the
following:

● #: <next
higher
number>
● Delivery Type:
<blank>
● Output Type:
BILLING_DOCUM
ENT(Billing
Document)
● Dispatch Time: 1
(Immediately)

4 Activate Choose Activate( Ctrl Rules are activated.

+ A ).

5 Receiver Determination Step: Details are displayed in

the Maintain Business
Receiver
Rules section.

Setting Up Sales Scheduling Agreements (3NR)

34 PUBLIC On-Premise-to-Cloud Integration
 Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

6 Add Rules Expand the Maintain

Business Rules section,
and choose Edit. In
Table Contents, choose
Insert New Row and en­
ter the following:

● #: <next
higher
number>
● Output Type:
BILLING_DOCUM
ENT(Billing
Document)
● Role: RE
● Exclusive Indicator:
false

7 Activate Choose Activate ( Ctrl Rules are activated.

+ A ).

8 Channel Determination Step: Details are displayed in

Channel the Maintain Business
Rules section.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 35
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

9 Add Rules Expand the Maintain

Business Rules section.

Choose Edit.

In the Table Contents

section, choose +
(Insert New Row).

Make the following en­

tries:

● #: <next
higher
number>
● Output Type:
BILLING_DOCUM
ENT(Billing
Document)
● Role: <blank>
● Receiver ID:
BILL-TO PARTY
(Example for US is
1710001 and for
DE is 17100001)
● Channel: EDI

10 Activate Choose Activate ( Ctrl Rules are activated.

+ A ).

11 Output Relevance Determination Step: Details are displayed in

Output Relevance the Maintain Business
Rules section.

Setting Up Sales Scheduling Agreements (3NR)

36 PUBLIC On-Premise-to-Cloud Integration
 Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment

12 Add Rules Expand the Maintain

Business Rules section.

Choose Edit.

In the Table Contents

section, choose +
(Insert New Row).

Make the following en­

tries:

● #: <next
higher
number>
● Output Type:
BILLING_DOCUM
ENT(Billing
Document)
● Posting Status: C
(Posting
document has
been created)
● TotalGdsMvtStat: C
(Completely
processed)
● Relevance
Indicator: X
(True)

13 Activate Choose Activate ( Ctrl Rules are activated.

+ A ).

 Note

● You can make table entries with an empty Receiver ID to make it applicable to all receivers (wildcard). If a
more specific entry with a Receiver ID exists, it would overrule the more generic entry without Receiver ID.
● If you are maintaining entries without Receiver ID, make sure that you put them at the end of the list.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 37
3.2.1.6 Assign Recipients

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Select Message Monitoring Assign Recipients to User .
3. On the Assign Recipients to User screen, Choose Add User.
4. On the Add User screen, enter your Name or ID, for example, CONF_EXPERT_BUS_NET_INT, then Choose Add.
5. On the Assign Receipts screen, enter below entries and choose Assign.

Nameapcace Recipient Name Message Type Include on Overview Tech. User

/SDSAR EDI_SD_SCHEDGAGR Application Error or Set flag Set flag

MT_RECIPIENT Technical Erro

6. Choose Assign.
7. On the Recipients (Cloud Edition) screen, choose Append Row.
8. Repeat the steps from 3 to 7 for both Namespace and Recipient for Alert.

Namespace Recipient for Alert

/SDSAR EDI_SD_INVC_RECIPIENT

/LEEDI EDI_DELOUT_RECIPIENT

3.2.1.7 Maintain Customer Material (Optional)

Purpose

This chapter is about master data maintenance and does not refer to a customizing activity.

In this activity, you maintain unique customer-specific names for your company's products. This must be done for
all materials, which customers order through EDI.

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Choose Manage Customer Materials.

Setting Up Sales Scheduling Agreements (3NR)

38 PUBLIC On-Premise-to-Cloud Integration
 3. Choose Create Object.
4. Enter Customer, Material, Sales Organization, Distribution Channel, and Customer Material.
5. Choose Save.
For each material that customers order through EDI, you must maintain a customer material. The customer
material maps the ID, which the customer uses for the material ordered, to a material.

3.2.2 Communication-Related Settings

3.2.2.1 Download Client Certificate in SAP Integration

Purpose

This step is relevant only for certificate-based authentication.

Procedure

1. Log on as SAP Integration Administrator to your Cloud Integration tenant WEB UI, for example, https://
<your SAP BTP tenant URL>/itspaces.
2. In the tenant menu, choose Monitor.
3. Choose the Keystore in the Manage Security section.
4. Search for sap_cloudintegrationcertificate. (Type Key Pair).
5. Choose Download Certificate.
6. Enter or select the file path to store the certificate in your local machine.

3.2.2.2 Create Communication User

Procedure

1. 1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud Supplier system.
2. Choose Communication Management Maintain Communication Users .
3. Choose New.
4. Maintain the Username and Description.
5. Assign a password for the user to use basic authentication. Else, assign the SAP Integration public client
certificate to the user for certificate-based authentication.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 39
 ○ For basic authentication, enter a password in the Password field.
○ For certificate-based authentication, select Upload Certificate (exported from SAP Integration KeyStore).
For more information, see the Download Client Certificate in SAP Integration chapter.
6. Choose Create.
7. Note down the user data for further steps.

 Note

Basic authentication with a username and password is possible, but not recommended in a productive
environment due to security reasons.

3.2.2.3 Create Communication Systems

Procedure

1. Open the Communication Systems app by choosing Communication Management Communication

Systems .
2. Choose New to create a communication system.
3. On the New Communication System screen, make the following entries:
○ ID: <CPI Tenant ID>
○ System Name: <CPI Tenant ID>
4. Choose Create.
5. On the Communication Systems screen, make the following entries:
1. Enter Host Name as <IFLMAP hostname for CPI Tenant>, for example, CPI_app_ID-
iflmap.hcisb.int.sap.hana.ondemand.com.
2. Add abusiness partner.
3. In the User for Inbound Communication area, choose Add.
4. On the New Inbound Communication User screen, enter the following details:

Field Value

User Name <Username created in the previous chapter>

Authentication Method Username and Password or SSL Client certificate

5. Choose OK.
6. In the Uder for Outbound Communication User screen, choose Add.
7. On the New Outbound Communication User screen, enter the following details:
○ User Name: <User details provided by the Buyer>
For username, enter <CPI Tenant UserName>.
○ Authentication Method: Username and Password or SSL Client certificate
○ For Client Certificate, enter Default Client Certificate.

Setting Up Sales Scheduling Agreements (3NR)

40 PUBLIC On-Premise-to-Cloud Integration
 8. Choose OK.

6. Choose Save.

3.2.2.4 Create Communication Arrangement

Procedure

1. Open the Communication Arrangements app by choosing Communication Management Communication

Arrangements .
2. Choose New.
3. On the Coimmunication Arrangement screen, enter the required details:
○ Scenario: SAP_COM_0444 (Sales scheduling Agreement with Buyers Integration)
Then choose Create.
4. On the Communication Arrangement screen, enter the required details:
○ Communication System： <Select the communication system you have created earlier, for
example, CPI Tenant ID.
○ Outbound Services:

Service Field Value

Outbound Delivery - Notify Path /cxf/EDI/DeliveryRequest_In

Customer Invoice- Send Path /cxf/EDI/InvoiceRequest_In

○ Inbound Services:

Service Field Value

Delivery Schedule of Sales Path /sap/bc/srt/scs_ext/sap/

Scheduling Agreement - Create, schedgagrmtdlivschedule_in
Upload

5. Choose Save.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 41
3.2.2.5 Export S/4HANA Cloud Supplier Public Certificate

Procedure

1. Open the Communication Arrangments app by choosing Communication Management Communication

Arrangements .
2. Enter SAP_COM_0444 in the Scenario ID field and choose Go.
3. In the Outbound Communication area, choose Download.
4. Choose Download Authentication Cert. and save the downloaded certificate in a local folder.

3.3 Set Up On-Premise to SAP Integration Connectivity

3.3.1 Configure PSE for Certificate-Based Authentication

For certificate-based authentication, a certificate signed by one of the CAs mentioned in the SAP BTP Integration
Service operations guide is mandatory. For a list of supported CAs, in the SAP Help Portal, proceed as follows:

1. Scroll down to the Operations section on the same page.

2. Choose the Operations guide for SAP BTP (PDF) link.
3. In the document that has opened, use the navigation panel on the right side and go to Concepts of Secure
Communication Basics HTTPS-Based Communication Load Balancer Root Certificates Supported by
SAP .
In this section, you can see a list of supported SAP Certification Authorities (CAs).

Procedure to Upload Certificate in On-Premise System

1. Go to transaction SE16.
2. On the Data Browser: Initial screen, enter Table Name as STRUSTSSL.
3. Choose Table and then Create Entries.
4. Confirm the Information dialog box with Enter.
5. Choose New Entries.
6. On the New Entries: Overview of Added Entries screen, enter a new SSL Client name (with Identity as SAPCPI
and Description as CPI Connection).
7. Choose Save and then select or create a workbench request.
8. Go to transaction STRUST.
9. On the Trust Manager: List screen, a new entry appears with the name SSL Client <Description text in step 6>.

Setting Up Sales Scheduling Agreements (3NR)

42 PUBLIC On-Premise-to-Cloud Integration
 10. Choose Display and then the Change icon.
11. Create a PSE with a certificate signed by a root CA supported by the HCP integration service load balancer in
the SSL Client <Description text in step 6> folder. For more information about how to create a PSE, see
Configuring SAP NetWeaver AS for ABAP to Support SSL.

 Note

It is also possible to use an already-available signed certificate. In that case, import the p12 file into the PSE
mentioned in step 11. For more information about how to import the p12 file into PSE, see Importing a
PKCS#12 File.

12. Double-click the PSE in the SSL Client <Description text in step 6> folder. The details of the PSE are displayed
on the right side.
13. Choose the Import Certificate icon in the Certificate section.
14. Enter or select the File path to one of the public certificates of the SAP HCP integration service load balancer:
○ Baltimore Cybertrust Root
○ GTE CyberTrust Global Root
15. Choose Enter.
16. Choose the Add to Certificate List icon. The certificate appears in Certificate List of Own Certificate.
17. Repeat the steps for the second public certificate of the SAP HCP integration service load balancer.
18. Choose Save.

3.3.2 Export the SAP On-Premise System Public Certificate

Purpose

This public certificate of the on-premise system is required to configuration the Integration Flows.

Procedure

1. Go to transaction STRUST.
2. On the Trust Manager: Display screen, choose the SSL Client (Standard or Anonymous or your own SSL Client
PSE).
3. Double-click Own Certificate on the right side.
4. Verify certificate details in the Certificate section.
5. Choose Display Change (Ctrl+F1) .
6. Choose Export Certificate in the Certificate section to export the public certificate.
7. Accept the default File Format, and in the Export Certificate dislog box, enter or select a File path (with
extension .cer or .crt).
8. Choose Enter to continue and store the certificate.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 43
3.3.3 Cloud Integration User for Basic Authentication

Basic authentication with a user and password is possible. However, it is not recommended in a productive
environment due to security reasons.

To connect the on-premise system to the Cloud Integration service, you require an SAP BTP integration service
user with the appropriate roles assigned. This should be a generic user. Ideally, an explicit SAP SCN user must be
created for this.

Procedure

1. Log on to your SAP S/4 HANA Cockpit.

2. Choose Security Authorizations Groups .
3. Maintain the SCN User.
To use an SNC user for basic authentication, add the SCN user (P-User) to a user group of the SAP S/4HANA
Cockpit Authorization Management with the following roles:
○ AuthGroup.IntegrationDeveloper
○ AuthGroup.BusinessExpert
○ esbmessagestorage.read
○ ESBMessaging.send

3.4 Set Up SAP CIntegration to SAP On-Premise Certificate-

Based Authentication

3.4.1 Create SAP On-Premise System User

Purpose

For setting up certificate-based authentication, a communication user is required to configure the basic
authentication or to be mapped to a client certificate.

Procedure

1. Go to transaction SU01.
2. In the User field, enter the system username.

Setting Up Sales Scheduling Agreements (3NR)

44 PUBLIC On-Premise-to-Cloud Integration
 3. Choose Create.
4. Enter the following data:

Field Name Value

On the Address tab page:

Last Name <Last Name of user>

First Name <First Name of user>

Function Function of user (Optional)

E-mail Address <E-mail Address>(Optional)

On the Logon Data tab page:

New Password <Initial Password>

Repeat Password <Repeat Initial Password>

Uder Type Dialog

On the Roles tab page:

Role <Copy of SAP standard role

SAP_XI_APPL_SERV_USER>

5. Choose Save.

3.4.2 Configure SSL Client Certificates for On-Premise

Purpose

For setting up certificate-based authentication, a client certificate must be mapped to the communication user.

Procedure

1. Go to transaction SM30.
2. Enter the name of the VUSREXTID view in the Table/View field and choose Maintain.
3. In the External ID type field, enter DN and choose Continue.
4. Create a new entry by choosing New Entries.
5. Choose Import to import the public client certificate from the SAP integration system.
6. Select the file that contains the public certificate and choose Open.
7. Enter the sequence, for example 000, the User ID you have created.
8. Select the Activated checkbox.
9. Choose Save.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 45
3.5 Configuration in SAP Integration

To work with the integration flows of this package, copy the prepackaged integration flow scenario to your
workspace. Then configure the integration flows. Finally, to activate the integration flows, deploy them.

To carry out configuration in the HANA Cloud Integration, the URL of your Cloud Integration tenant is required. This
URL is provided by the Cloud Integration tenant provisioning mail.

3.5.1 Deploy Technical Communication User Data with

Credential Artifact

Purpose

 Note

Due to security reasons, we do not recommend user-based or password-based authentication. If it is

certificate-based authentication for the SAP S/4HANA Cloud buyer system, you can skip this chapter.

In the Communication Arrangement chapter, a Communication User in your SAP S/4HANA Cloud (buyer and
supplier) system was created. You must store these credentials in your Cloud Integration tenant as User Credential.

Procedure

1. Open the Cloud Integration tenant Web U, for example, https://<your Cloud Integration tenant
URL>/itspaces.
2. In the tenant menu, choose Monitor.
3. Choose Security Material in the Manage Security Material section.
4. Choose Add.
5. Select User Credentials.
6. Enter the following values in the Add Users Credential dialog box:
Suppplier Cloud System Credentials

Field Name Value

Name <s4cesupplier_credential>

Description <Optional>

User <User Alias Name of your technical user>

Setting Up Sales Scheduling Agreements (3NR)

46 PUBLIC On-Premise-to-Cloud Integration
 Field Name Value

Enter the username created in Communication User.

Password <Password of your technical user>

Buyer On_Premise System Credentials:

Field Name Value

Name <opbuyer_credential>

Description <Optional>

User <User Alias Name of your technical user>

Enter user name of a technical user available in the on-

premise system.

Password <Password of your technical user>

User Credentials of User Account Used for Mail Notification (Optional):

Field Name Value

Name <MailUserCredential>

Description <Optional>

User <User Alias Name of your mail account>

Password <Password of your user>

7. Choose OK to save the user credentials.

3.5.2 Deployment and Configuration of Integration Package

3.5.2.1 Copying Integration Package from Content Catalog

Procedure

1. Open the Cloud Integration tenant Web UI, for example, https://<your Cloud Integration tenant
URL>/itspaces.
2. In the tenant menu, choose Discover.
3. Select All to see all the published integration packages.
4. Search for the Integration package name SAP S/4HANA Cloud for Sales Integration with SAP S/4HANA.
5. Choose the package to display the package content.
6. To copy the integration package of the catalog to your customer workspace, choose Copy Package in the upper
right corner.
7. In the tenant menu, choose Design.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 47
8. On the Design tab page, select the integration package that you copied.
An overview of the artifacts available in the selected integration package is displayed. The following list is
provided:
○ Receive Supplier Invoice: For Invoice processing
○ Receive Advance Shipping Notification: For outbound delivery processing
○ Update Sales Scheduling Agreements: For sales scheduling agreement processing
○

3.5.2.2 Maintain SAP Integration Value Mapping Artifact for

Scheduling Agreement Request iFlow

Purpose

Value mappings are required and are delivered as a template. This template is part of the prepackaged SAP Cloud
Integration content. This value mapping template must be adapted based on the configuration settings in
customer systems (SAP S/4HANA cloud and SAP S/4HANA/ERP on-premise).

Procedure

1. In the Design section, select the package, which contains the integration content.
An overview of the artifacts available in the selected integration package is displayed in the Artifacts tab.
2. Select the value mapping artifact Value Mapping for Supplier in Cloud and Buyer in OnPremise.
3. To configure value mapping, choose Configure in the Actions column for the respective artifact.
4. In the Value Mappings section, depending on your customizing, check and adapt the values of mappings of the
following fields:
○ PartnerNumber
○ TextIDHeader
Maintain corresponding values in the on-premise system for the following Text IDs available in S/4HANA Cloud
system:
○ SalesNote
○ PickPackInstruction
○ ShippingInstructions
For example:

OPBuyer, TextIDHeader S4CESupplier, TextIDHeader

EKKO SalesNote

○ TextIDItem
○ PickPackInstructions

Setting Up Sales Scheduling Agreements (3NR)

48 PUBLIC On-Premise-to-Cloud Integration
 ○ MaterialText
○ ShippingInstructions
For example:

OPBuyer, TextIDItem S4CESupplier, TextIDItem

EKPO SalesNote

 Note

Text node is created and the corresponding text is passed to the receiver system only if the TextID is
maintained in the Value Mapping table.

5. Choose Save.

3.5.2.3 Deploy Value Mapping

Procedure

1. Choose the icon in the top left corner and select the Design section from the dropdown list.
All available integration packages for the tenant are displayed.
2. Search for the package name Integration of SAP S/4HANA Cloud for Sales Integration with SAP S/4HANA.
3. Choose the integration package.
The package content list is displayed.
4. Select Artifacts.
All the artifacts are listed at the bottom of the page.
5. In the Actions menu of the value mapping artifact, choose Deploy.

3.5.2.4 Deployment and Configuration of Sales Scheduling

Agreement Request Integration Flow

Procedure

1. Open the Cloud Integration tenant Web UI, for example, https://<your Cloud Integration tenant
URL>/itspaces.
2. In the tenant menu, choose Design.
3. On the Design tab page, select the package Integration of SAP S/4HANA Cloud for Sales Integration with SAP
S/4HANA, which contains the integration flows objects.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 49
4. To configure the Scheduling Agreement Request, choose Configure in the Actions column of the Update Sales
Scheduling Agreements artifact.
5. Enter the relevant details on the Sender tab page:

Field Value

Sender OPBuyer

Adapter Type IDOC

Address /EDI/DELINS_DELFOR02

This address must be unique on Cloud Integration tenant. If you want to deploy this scenario
twice on the same tenant, change this address.

Authorization Role-based Authentication or Certificate-based Authentication

For Certificate Choose Browse and select the stored certificate (see Export S/4 HANA Cloud Supplier Public
Authentication Certificate).

For User Role ESBMessaging.send

Body Size (in MB) 40 (keep default)

Attachment Size (in MB) 100 (keep default)

6. Enter the relevant details on the Receiver tab page for the receiver, S4CEsupplier:

Field Value

Receiver S4CESupplier

Adapter Type SOAP

Address https:// s4cesupplier_host:port/sap/bc/srt/scs_ext/sap/

schedgagrmtdlivschedule_in

To retrieve the SOAP Service URL, check the Communication Arrangement created in Create

Communication Arrangement, on the UI under Inbound Services Service URL .

Proxy Type On-Premise

Authentication Basic Authentication or Certificate Authentication

Credential Name (only s4cesupplier_credential

for basic authentication)
(Enter the name from the Deploy Technical Communication User Data with Credential Artifact
chapter.)

Private Key Alias (for <private_key_alias>

Certificate-based
Authentication) (Alias for SSL Keypair in Cloud Integration keystore. For example,
sap_cloudintegrationcertificate (provided by SAP). The alias must refer to the SSL Keypair
from which the public certificate was exported for Create Communication User.

Timeout (in ms) 300000

Compress Message <Uncheck>

Allow Chunking <Check>

Setting Up Sales Scheduling Agreements (3NR)

50 PUBLIC On-Premise-to-Cloud Integration
 Field Value

Clean-up Request <Check>

Headers

7. Enter the relevant details on the Receiver tab page for Cloud Integration error mail notification. (Optional - Keep
default values if Mail Notification is not active):

Field Value

Receiver CPI_Error

Adapter Type Mail

Address <smtp.server.com:port>

(Enter SMTP mail server details, for example

smtp.gmail.com:587. By default, the ports 587 (SMTP+
STARTTLS) and 465 (SMTPS) are supported.)

Timeout (in ms) 3000

Protection STARTTLS Mandatory

(Settings depend on the Mail provider.)

Authentication Plain User/Password

(Settings depend on the Mail provider.)

Credential Name <MailUserCredential>

From <mailfrom@mail.com>

To <mailto@mail.com>

CC <cc@mail.com>

BCC <bcc@mail.com>

Subject Error happens when processing message in CPI

Mail Body ${in.body}

If you want to receive the complete error log, keep the mail
body unchanged.

Body Mime-Type Text/Plain

Body Encoding UTF-8

Add Message Attachments <Do not select this option>

8. If you want to implement mapping extension for this iFlow, enter the relevant details on the Receiver tab page
for the receiver, IDOC2SOAP_SalesSchedulingAgreementCustomMapping_iFlow:

Field Value

Adapter Type ProcessDirect

Address /EDI/DELINS_DELFOR02_CustomMap

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 51
 Field Value

This address must be unique on Cloud Integration Tenant. If this scenario has to be deployed twice
on the same tenant, you must change this address. In addition to that, the address maintained here
must be the same as the one defined for the sender ProcessDirect adapter in the corresponding
order confirmation custom integration flow.

For more information about the mapping extension process, refer to the Developing and Deploying Mapping
Extensions for Integration Package chapter.

9. Enter the relevant details on the More tab page:

Field Value

Enable Logging Set to true if payload must be logged as an attachment to Message Processing Log (MPL). The

attachments can be found in the message details under Web UI Operations View

Monitor Message Processing .

Default is false (recommended for better performance).

Extension Required false

Set it to true, if you want to activate the extension process.

Mail Notification For SAP S/4HANA, if you require mail notifica- tions for integration service errors and SAP S/
4HANA Cloud Sales errors, enter true to set it to active.

10. Choose Save.

11. Choose Deploy to directly deploy the iFlow.

3.5.2.5 Deployment and Configuration of Supplier Invoice

Request Integration Flow

Procedure

1. Open the Cloud Integration tenant Web UI, for example, https://<your Cloud Integration tenant
URL>/itspaces.
2. In the tenant menu, choose Design.
3. On the Design tab page, select the required package, which contains the integration scenarios.
An overview of the artifacts available in the selected integration package is displayed.
4. To configure the Invoice Request, choose Configure in the Actions column of the Receive Supplier Invoice
artifact.
5. Enter the relevant details on the Sender tab page:

Setting Up Sales Scheduling Agreements (3NR)

52 PUBLIC On-Premise-to-Cloud Integration
 Field Value

Sender S4CESupplier

Adapter Type SOAP

Address /EDI/InvoiceRequest_in

(This address must be unique on Cloud Integration Tenant. If you want to deploy this scenario
twice on the same tenant, change this address.)

Authorization Role-based Authentication or Certificate-based Authentication

For Certificate Choose Browse and select the stored certificate (see Export S/4 HANA Cloud Supplier Public
Authentication Certificate).

For User Role ESBMessaging.send

Body Size (in MB) 40 (keep default)

Attachment Size (in MB) 100 (keep default)

6. Enter the relevant details on the Receiver tab page for the receiver, OPBuyer:

Field Value

Receiver OPBuyer

Adapter Type IDOC

Address Using Reverse Proxy/Webdispatcher:

https://<ReverseProxy/Webdispatcher host>:<ReverseProxy/
Webdispatcher port>/sap/bc/srt/idoc?sap- client=<OP_Client>

Using Cloud Connector:

http://<opbuyer_host>:<opbuyer_port>/sap/bc/srt/idoc?sap-
client=<op_client>

Ensure that the host and port of the on-premise system are accessible through public
network. Reverse proxy/SAP Webdispatcher or cloud connector, depending on customer
landscape, can be used to expose on-premise system to the public.

The usage of a Cloud connector is recommended. Details for configuring a Cloud connector
are available in the SAP Help Portal.

Proxy Type Internet (Reverse Proxy/SAP Webdispatcher) or On-Premise (Cloud Connector)

Authentication Basic Authentication or Certificate Authentication (for Cloud connector, only Basic or None)

Credential Name (only opbuyer_credential

for basic authentication)
(Enter the name from the Deploy Technical Communication User Data with Credential Artifact
chapter.)

Private Key Alias (for <private_key_alias>

Certificate-based
Authentication) Alias for SSL Keypair in SAP Cloud keystore.

For example, hcicertificate (provided by SAP).

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 53
 Field Value

For more information about certificate to user mapping, see Configure SSL Client certificates
for On-Premise chapter.

Allow Chunking <select this option

Clean-up Request <select this option>

Headers

7. If you want to implement mapping extension for this iFlow, enter the relevant details on the Receiver tab page
for the receiver, SOA2IDoc_InvoiceCustomMapping_iFlow:

Field Value

Adapter Type Process Direct

Address EDI/SupplierInvoiceRequest_CustomMap

This address must be unique on Cloud Integration Tenant. If

this scenario has to be deployed twice on the same tenant,
you must change this address. In addition to that, the
address maintained here must be the same as the one
defined for the sender ProcessDirect adapter in the
corresponding invoice custom integration flow.

For more information about the mapping extension process, refer to the Developing and Deploying Mapping
Extensions for Integration Package chapter.

8. Enter the relevant details on the Receiver tab page for Cloud Integration error mail notification. (Optional - keep
default values if Mail Notification is not active):

Field Value

Receiver CPI_Error

Adapter Type Mail

Address <smtp.server.com:port>

(Enter SMTP mail server details, for example:

smtp.gmail.com:587. By default, the ports 587 (SMTP
+ STARTTLS) and 465 (SMTPS) are supported.)

Timeout (in ms) 3000

Protection STARTTLS Mandatory

(Settings depend on the Mail provider.)

Authentication Plain User/Password

(Settings depend on the Mail provider.)

Credential Name <MailUserCredential>

From <mailfrom@mail.com>

To <mailto@mail.com>

Setting Up Sales Scheduling Agreements (3NR)

54 PUBLIC On-Premise-to-Cloud Integration
 Field Value

Subject CPI Error

Mail Body ${in.body}

If you want to receive the complete error log, keep the mail
body unchanged.

Body Mime-Type Text/Plain

Body Encoding UTF-8

Add Message Attachments <Do not select this option>

9. Enter the relevant details on the More tab page:

Field Value

Enable Logging Set to true if payload must be logged as an attachment to Message Processing Log (MPL). The

attachments can be found in the message details under Web UI Operations View

Monitor Message Processing .

Default is false (recommended for better performance).

Extension Required false

Set it to true, if you want to activate the extension process.

Mail Notification For SAP BTP, if you require mail notifica- tions for integration service errors and SAP S/4HANA
Cloud Sales errors, enter true to set it to active.

Receiver Parnter <Logical system name of SAP on-premise system in the format
SIDCLNTXXX, where SID is the system ID of SAP on-premise system
and XXX denotes Client number (as defined in transaction WE20
under Partner Type LS)>

This is used to populate RCVPRN field in IDoc.

Receiver Port <Logical system name of SAP on-premise system in the for mat
SIDCLNTXXX, where SID is the system ID of SAP on- premise system
and XXX denotes Client number (as defined in transaction WE20
under Partner Type LS)>

This is used to populate RCVPRN field in IDoc.

Sender Partner <Logical system name of SAP S/4HANA as explained in the Define
Logical System chapter> (can be checked using transaction WE20Partner Type LS)

This is used to populate the SNDPRN field in IDoc.

Sender Port <Free text to be mapped to the RCVPOR field in IDoc>. For example, the
Logical System name in Define Logical System.

10. Choose Save.

11. Choose Deploy to directly deploy the iFlow.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 55
3.5.2.6 Deployment and Configuration of Delivery Request
Integration Flow

Procedure

1. Open the Cloud Integration tenant Web UI, for example, https://<your Cloud Integration tenant
URL>/itspaces.
2. In the tenant menu, choose Design.
3. On the Design tab page, select the required package, which contains the integration scenarios.
An overview of the artifacts available in the selected integration package is displayed.
4. To configure the Delivery Request, choose Configure in the Actions column of the Advance Shipping Notification
artifact.
5. Enter the relevant details on the Sender tab page:

Field Value

Sender S4CESupplier

Adapter Type SOAP

Address /EDI/DeliveryRequest_in

(This address must be unique on SAP Cloud BTP Tenant. If you want to deploy this scenario
twice on the same tenant, change this address.)

Authorization Role-based Authentication or Certificate-based Authentication

For Certificate Choose Browse and select the stored certificate (see Export S/4 HANA Cloud Supplier Public
Authentication Certificate).

For User Role ESBMessaging.send

Body Size (in MB) 40 (keep default)

Attachment Size (in MB) 100 (keep default)

6. Enter the relevant details on the Receiver tab page for the receiver, OPBuyer:

Field Value

Receiver OPBuyer

Adapter Type IDOC

Address Using Reverse Proxy/Webdispatcher:

https://<ReverseProxy/Webdispatcher host>:<ReverseProxy/
Webdispatcher port>/sap/bc/srt/idoc?sap- client=<OP_Client>

Using Cloud Connector:

http://<opbuyer_host>:<opbuyer_port>/sap/bc/srt/idoc?sap-
client=<op_client>

Setting Up Sales Scheduling Agreements (3NR)

56 PUBLIC On-Premise-to-Cloud Integration
 Field Value

Ensure that the host and port of the on-premise system are accessible through public
network. Reverse proxy/SAP Webdispatcher or cloud connector, depending on customer
landscape, can be used to expose on-premise system to the public.

The usage of a Cloud connector is recommended. Details for configuring a Cloud connector
are available in the SAP Help Portal.

Proxy Type Internet (Reverse Proxy/SAP Webdispatcher) or On-Premise (Cloud Connector)

Authentication Basic Authentication or Certificate Authentication (for Cloud connector, only Basic or None)

Credential Name (only opbuyer_credential

for basic authentication)
(Enter the name from the Deploy Technical Communication User Data with Credential Artifact
chapter.)

Private Key Alias (for <private_key_alias>

Certificate-based
Authentication) Alias for SSL Keypair in SAP Integration keystore.

For example, hcicertificate (provided by SAP).

For more information about certificate to user mapping, see Configure SSL Client certificates
for On-Premise chapter.

Allow Chunking <select this option

Clean-up Request <select this option>

Headers

7. If you want to implement mapping extension for this iFlow, enter the relevant details on the Receiver tab page
for the receiver, SOA2IDoc_DeliveryCustomMapping_iFlow:

Field Value

Adapter Type Process Direct

Address /EDI/DeliveryRequest_CustomMap

This address must be unique on Cloud Integration Tenant. If

this scenario has to be deployed twice on the same tenant,
change this address. In addition to that, the address
maintained here must be the same as the one defined for
the sender Process Direct adapter in the corresponding
delivery custom integration flow.

For more information about the mapping extension process, refer to the Developing and Deploying Mapping
Extensions for Integration Package chapter.

8. Enter the relevant details on the Receiver tab page for SAP Integration error mail notification. (Optional - keep
default values if Mail Notification is not active):

Field Value

Receiver CPI_Error

Adapter Type Mail

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 57
 Field Value

Address <smtp.server.com:port>

(Enter SMTP mail server details, for example:

smtp.gmail.com:587. By default, the ports 587 (SMTP
+ STARTTLS) and 465 (SMTPS) are supported.)

Protection STARTTLS Mandatory

(Settings depend on the Mail provider.)

Authentication

Credential Name <MailUserCredential>

From <mailfrom@mail.com>

To <mailto@mail.com>

Subject CPI Error

Mail Body ${in.body}

If you want to receive the complete error log, keep the mail
body unchanged.

Body Mime-Type Text/Plain

Body Encoding UTF-8

Add Message Attachments <Do not select this option>

9. Enter the relevant details on the More tab page:

Field Value

Enable Logging Set to true if payload must be logged as an attachment to Message Processing Log (MPL). The

attachments can be found in the message details under Web UI Operations View

Monitor Message Processing .

Default is false (recommended for better performance).

Extension Required false

Set it to true, if you want to activate the extension process.

Mail Notification For SAP S/4HANA , if you require mail notifica- tions for integration service errors and SAP S/
4HANA Cloud Sales errors, enter true to set it to active.

Receiver Parnter <Logical system name of SAP on-premise system in the format
SIDCLNTXXX, where SID is the system ID of SAP on-premise system
and XXX denotes Client number (as defined in transaction WE20
under Partner Type LS)>

This is used to populate RCVPRN field in IDoc.

Setting Up Sales Scheduling Agreements (3NR)

58 PUBLIC On-Premise-to-Cloud Integration
 Field Value

Receiver Port <Free text to be mapped to the RCVPOR field in IDoc in the
format SAPSID, where SID is the system ID of the SAP on- premise
system>

This is used to populate RCVPOR field in IDoc.

Sender Partner <Logical system name of SAP S/4HANA as explained in the Define
Logical System chapter> (can be checked using transaction WE20Partner Type LS)

This is used to populate the SNDPRN field in IDoc.

Sender Port <Free text to be mapped to the RCVPOR field in IDoc>. For example, the
Logical System name in Define Logical System.

10. Choose Save.

11. Choose Deploy to directly deploy the iFlow.

3.5.3 Developing and Deploying Mapping Extensions for

Integration Package

3.5.3.1 Purpose and Benefits

The Integration of SAP S/4HANA Sales Scheduling Agreements enables you to implement the following processes:
scheduling agreement between buyer and supplier, outbound delivery, and customer invoice. For each process, a
standard structure for source and target messages, including messages mappings, is delivered and used in the
corresponding integration flow out of the box.

For some or other reasons, you may want to change the standard process by adding, for example, new fields to the
standard messages structure, or by changing the messages mappings. This section describes how you can add
custom fields to your standard structure for source and target messages and provide a custom message mapping
to reflect the fields enhancement in your Integration Content.

To facilitate the extension process as described above, a dedicated Integration Package named SAP S/4HANA
Cloud for Sales Integration with SAP S/4HANA - Extension Mapping has also been published in the content catalog.
For each integration flow available in the standard integration package, a corresponding custom (or mapping)
integration flow has been delivered within the mapping extension package. This allows you to define or customize
your mapping or field extensions. For example, for the invoice process a corresponding integration flow is available
in the mapping extension package. It can be used to define any mapping deviation from the standard process.

From a technical perspective, SAP Integration provides an adapter called ProcessDirect adapter to connect the
standard iFlow (also known as producer) and custom iFlow (also known as consumer). The ProcessDirect adapter
connects the plug-in touchpoints at a lower network latency in comparison to the SOAP or HTTP adapter.

Providing a dedicated custom integration package combined with the ProcessDirect adapter for extension
purposes has the following advantages:

● Better life-cycle management of your standard integration flows and packages

If you make any changes to the standard integration flow or package provided out of the box by SAP, the life-
cycle management of your artifact object breaks. Then you won’t receive updates related to those objects in

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 59
 your Cloud Integration tenant. Additionally, copying the updated standard package from the content catalog to
the design workspace of your tenant containing the modified packages results in the overwriting of all the
changes made previously to that package. Therefore, defining all required changes in a dedicated Integration
Package helps you to manage the lifecycle of your Integration Packages in a better way.
● Agile and flexible customizing of the standard content
SAP Integration enables integration developers to customize their integration flows without modifying them
entirely. The SAP BTP provides plug-in touchpoints to custom iFlows, where integration developers can add
custom content.
● Reusability of custom iFlows by multiple integration processes spanning multiple integration projects:
It enables the reuse of integration flows for mapping across integration projects and Camel context. Therefore,
integration developers must define repetitive logic flows only once. They can also call them from any
integration flow using the ProcessDirect adapter.

For more information about ProcessDirect adapter, see Configure Communication Channel with ProcessDirect
Adapter in SAP Help Portal.

3.5.3.2 Available Mapping Extension iFlows in Integration

Package

The package SAP S/4HANA Cloud for Sales Integration with SAP S/4HANA - Extension Mapping comes with the
following integration flows out of the box:

● Receive Supplier Invoice Custom Mapping-to define mapping extension for invoice process
● Advance Shipping Notification Custom Mapping-to define mapping extension for the outbound delivery process
● Update Sales Scheduling Agreements Custom Mapping-to define mapping extension for the sales scheduling
agreement delivery schedule process

3.5.3.3 Template Structure of Mapping Extension iFlows

To aid in the implementation of your mapping extensions, templates for custom integration flows, defining some
processing steps are delivered. The delivered templates are generic and provide quite the same steps for all custom
integration flows.

You must understand the structure of the template before you start implementing the extension. The most
important parts of the templates are the following:

● Sender component
It represents the producer or the standard integration flow.
● Sender ProcessDirect adapter
The adapter is used to consume data from the standard integration flow.
Note that the address maintained in the Sender ProcessDirect adapter must be the same as the one defined in
the Receiver ProcessDirect adapter in standard integration flow. Those parameters have been externalized to
allow you to configure them easily during the integration flow configuration.
● Exception subprocess
It is used to handle exceptions directly in custom integration flows.

Setting Up Sales Scheduling Agreements (3NR)

60 PUBLIC On-Premise-to-Cloud Integration
 ● Message mapping
In the message mapping step, you define your custom mapping. To foster your custom mapping
implementation, a standard mapping using the standard WSDL files has been provided.
The mapping template embodies the following structure:
○ Source mapping structure
It consists of two messages types - Message1 and Message2.
Message1 represents the output or the result of the standard mapping generated in standard integration
flow.
Message2 represents your custom message type. In others words, this message type must be superseded
with your custom source message type.
● Target message structure
This message type is a placeholder for your custom target message structure. You can replace it with a custom
message type. If field extension is not required in the target structure, you can use it as provided to you.
● Mapping logic
The delivered mapping logic maps all corresponding fields of the source Message1 type with the target
message type, which are basically the same message types.

3.5.3.4 Implementation Steps for Mapping Extension

The extension procedure is the same for all integration flows. The procedure described here is a general one and
applies to all custom integration flows.

The following figure depicts the extension steps at a glance:

3.5.3.4.1 Extend Structure of Source and Target Message in

Supplier or Buyer System

First, you must extend either your target structure or source structure, or both, directly in the source system or
target system. This can be an IDoc type or a SOAP message, depending on your business requirements. Second,
you must generate a corresponding WSDL file to be imported and used in your custom integration flow in Cloud
Integration Service.

For more information about how to extend an IDoc type in an on-premise system (S/4HANA or SAP ERP), see the
respective chapter on SAP Help Portal.

For information about how to extend a SOAP API in S/4HANA using the Custom Fields and Logic app, see the
respective chapter on SAP Help Portal.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 61
After completing the extension process, generate WSDL files and make them available for the integration flow.

 Note

The custom mapping integration package is released only once, and its lifecycle management is under the
control of the customer. So, you must always make sure that the standard WSDLs files used in the mapping
extension integration flow objects are up-to-date or consistent with the corresponding WSDLs files of the
standard integration flow before extending or using them in the mapping integration flow objects.

3.5.3.4.2 Create WSDLs for Message Processing

To generate and download a WSDL for the IDoc-XML message structure in your Supplier system (SAP S/4HANA or
ERP), do as follows:

1. Open your Supplier system (SAP S/4HANA or ERP).

2. Go to transaction SE38
3. On the ABAP Editor: Initial screen, enter SRT_IDOC_WSDL_NS as program name in the Program field.
4. Keep all other settings and choose Execute.
5. On the Generate portTypes WSDL for IDocTypes screen, enter the basic and message type of your extended
IDoc.
6. Choose Execute.
7. In the opened windows, enter a name for the WSDL file.
8. Save the WSDL file in your local machine.

To download the WSDL of the extended SOAP API in your Buyer system (SAP S/4HANA Cloud), do as follows:

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system
2. Go to Communication Management Communication Arrangements .
3. Search for the communication arrangement object (created in the Create Communication Arrangement
chapter).
This object was created using the SAP_COM_0444 communication scenario.
4. Select the communication arrangement to open it.
5. To download WSDL for the outbound API (in this case, Purchase Order), scroll down to the Outbound Services
section.
6. Choose Download WSDL on the right side of the API name.
7. Save the downloaded file in your local system.
8. To download WSDLs for inbound APIs (in this case, Order Confirmation, Invoice and Delivery), scroll down to
the Inbound Services section.
9. Choose the arrow (WSDL Column) on the right side of the Service URL/Service Interface column.
10. Save the downloaded file in your local system.

Setting Up Sales Scheduling Agreements (3NR)

62 PUBLIC On-Premise-to-Cloud Integration
3.5.3.4.3 Import WSDLs and Implement Custom Mapping in
SCP Integration Service

Procedure

1. Open the SCP Integration tenant Web UI.

For example, https://<Your Cloud Integration tenant URL>/itspaces.
2. In the tenant menu, choose Design.
3. On the Design tab page, select the package SAP S/4HANA Cloud for Sales Integration with SAP S/4HANA -
Extension Mapping, which contains the integration flows objects.
An overview of the artifacts available in the selected integration package is displayed.
4. Choose the integration flow you want to extend, for example, Update Sales Scheduling Agreements Custom
Mapping.
5. Choose Edit.
6. In the Integration Process boundary, choose the Message Mapping processing step.
7. In the Message Mapping property at the bottom of the page, choose the Processing tab.
The name of the Message Mapping resource is displayed.
8. Choose the Message Mapping name.
The Message Mapping editor is displayed. In this editor, a source messages structure and a target structure are
displayed on the left side and right side of the page respectively.
The source message structure consists of two different message types - Message1 and Message2. The target
message structure embodies only one message type.
9. On the left side of the page, where the source message structure is displayed, choose the pencil icon next to
the Source Messages text to edit the message type. (In this case, it is Message2.)
The Source and Target Messages panel opens, and a table containing two rows is displayed for source
messages. The message type to be replaced is displayed in the second row of the table.
10. To replace the message type with a custom message type, go to the Actions table header.
11. Choose the Replace Message icon near the trash icon. The Select Source Message screen displays.
12. Choose Upload from File System to choose a WSDL file from the file system.
Once the import is completed, the Select Source Message screen is closed and the Source and Target Messages
panel displays again.
13. Choose OK to save your changes and go back to the mapping editor.
Now you can implement your mapping logic as per your requirements. For more information about message
mapping definition, see Create Message Mapping Definition Resource in SAP Help Portal.
When you create message mappings, check whether it works as expected. By simulating a mapping, you can
verify the correctness and their functioning. For more information, see in SAP Help Portal.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 63
3.5.3.4.4 Deploy Custom Integration Flow

Purpose

After implementing and testing your custom mapping, configure and deploy the custom integration flow during the
runtime of the SAP BTP integration service.

Procedure

1. Open the SAP Cloud BTP tenant Web UI, for example, https://<your Cloud Integration tenant
URL>/itspaces.
2. In the tenant menu, choose Design.
3. On the Design tab page, select the package Integration of SAP S/4HANA Cloud for Sales Integration with SAP
S/4HANA - Extension Mapping, which contains the integration flows objects.
4. Choose Configure in the Actions column of the custom integration flow that you want to configure. For example,
Update Sales Scheduling Agreements Custom Mapping.
5. Enter the relevant details on the Sender tab page:

Field Value

Sender OPBuyer

Adapter Type ProcessDirect

Address /EDI/ DELINS_DELFOR02_CustomMap

This address must be unique on the Cloud Integration tenant. If you want to deploy this
scenario twice on the same tenant, change this address. Additionally, the address maintained
here must be the same as the one defined for the receiver ProcessDirect adapter in the
standard integration flow.

6. Enter the relevant details on the Receiver tab page for the receiver, Custom_CPI_Error:

Field Value

Receiver Custom_CPI_Error

Adapter Type Mail

Address <smtp.server.com:port>

(Enter SMTP mail server details, for example,

smtp.gmail.com:587. By default, the ports 587 (SMTP
+ STARTTLS) and 465 (SMTPS) are supported.)

Protection STARTTLS Mandatory

Setting Up Sales Scheduling Agreements (3NR)

64 PUBLIC On-Premise-to-Cloud Integration
 Field Value

(Settings depend on the Mail provider.)

Authentication Plain User/Password

(Settings depend on the Mail provider.)

Credential Name <MailUserCredential>

From <mailfrom@mail.com>

To <mailto@mail.com>

Subject SAP CPI process error

Mail Body ${in.body}

If you want to receive the complete error log, keep the mail
body unchanged.

7. Enter the relevant details on the More tab page:

Field Value

Mail Notification For SAP BTP, if you require mail notifications for integration service errors and SAP S/4HANA
Cloud Sales errors, enter true to set it to active.

8. Choose Save.
9. Choose Deploy to directly deploy the iFlow.

3.5.3.4.5 Activate Extension Process

Purpose

By activating the extension process, the custom integration flow where you have implemented your custom
mapping, is called through a touch point defined in the standard integration flow. This touch point or exit point is
defined using an external property, which can be set to true or false by configuring the standard integration flow.

Procedure

1. Open the Cloud Integration tenant Web UI, for example, https://<your Cloud Integration tenant
URL>/itspaces.
2. In the tenant menu, choose Design.
3. On the Design tab page, select the package Integration of SAP S/4HANA Cloud for Sales Integration with SAP
S/4HANA, which contains the integration flows objects.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 65
4. Choose Configure in the Actions column of the custom integration flow that you want to configure.
For example, Create, Change, or Update Sales Scheduling Agreement.
5. On the More tab, enter the following parameter:

Field Value

Extension Required True

6. On the Receiver tab, choose the receiver corresponding to your custom integration flow as defined in the
standard integration flow.
For example, Create, Change, or /EDI/DELINS_DELFOR02_CustomMap.
7. Ensure that the value maintained for the Address parameter is the same as the one maintained in the sender
ProcessDirect adapter of the custom integration flow.
8. Choose Save.
9. Choose Deploy.

3.6 Troubleshooting and Log

Purpose

On the SAP Integration Web UI, you can analyze the deployed integration flows in the Monitoring section.

Procedure

1. Open the SAP Cloud BTP tenant Web UI.

For example, https://<your Cloud Integration tenant URL>/itspaces.
2. Choose Monitor.
3. On the Overview screen, choose the tile with a message status you want to analyze.
4.

3.6.1 SAP Ingergration Message Analyze

Purpose

On the SAP Integration Web UI, you can analyze the deployed integration flows in the Monitoring section.

Setting Up Sales Scheduling Agreements (3NR)

66 PUBLIC On-Premise-to-Cloud Integration
Procedure

1. Open the Cloud Integration tenant Web UI, for example, https://<your Cloud Integration tenant
URL>/itspaces.
2. Choose Monitor.
3. On the Overview screen, choose the tile with a message status you want to analyze.
4. On the left side, select the message you want to analyze. The issues that occurred on the right pane are
displayed.

3.6.2 AIF Message Dashboard log Analyze

Purpose

On the Message Dashboard, you can analyze the deployed log.

Procedure

1. Log on to FLP and navigate to Message Monitoring tab. Open the Message Dashboard.
2. Choose Sales SchedgAgrmt process integration - /SDSAR.
3. Choose All Messages to check all relevant AIF messages.
4. Below error messages are usually displayed in message dashboard.

Field Name Detail

Error Description Delivery schedule type &1 is not supported

Message No. EDI_SD801

Diagnosis The system uses two release type in sales scheduling

agreement:

Forecast Schedule release

JIT Schedule release

System Response The system stops processing the EDI message

Procedure Please provide Delivery Schedule type JIT or FRC in Payload

file or EDI segment fields

Field Name Detail

Error Description Multiple sales scheduling agreements are found for Sold-to
Party &1

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 67
 Field Name Detail

Message No. EDI_SD802

Diagnosis The system uses the following search criteria to search for a
sales scheduling agreement:
○ The Sold-to Party that either comes in with the EDI
message or is determined in the Assign Sold-to Parties
app.
○ Customer material, partner description, and unloading
point (if any) that comes in with the EDI message.

If the system find multiple sales scheduling agreement, it

could be due to the following reasons:

New sales scheduling agreements created for the same

sold-to party but haven't deleted or rejected the old sales
schedule agreement.

System Response The system stops processing the EDI message

Procedure
○ Delete the old sales schedule agreement in Change

Sales Scheduling Agreement app More Sales

Document Delete .
○ Reject both header and item level of sales schedule
agreement in Change Sales Scheduling Agreement
app Reason for Rejection .

Field Name Detail

Error Description No sales scheduling agreement is found for sold-to party

Message No. EDI_SD803

Diagnosis The system uses the following search criteria to search for a
sales scheduling agreement:
○ The sold-to party that either comes in with the EDI
message or is de-termined in the Assign Sold-to
Parties app.
○ Customer material, partner description, and unloading
point (if any) that comes in with the EDI message

If the system cannot find a sales scheduling agreement, it

could be due to the following reasons:
○ None of the existing sales scheduling agreements
match the search criteria.
○ The sales scheduling agreement is rejected.

System Response The system stops processing the EDI message

Procedure ○ Contact the business users and tell them to do the

following:

Setting Up Sales Scheduling Agreements (3NR)

68 PUBLIC On-Premise-to-Cloud Integration
 Field Name Detail

○ Enter search criteria and manually search for the

sales scheduling agreement in the Change
Scheduling Agreements app.
○ If necessary, correct the sales scheduling
agreement or change the master data of the sales
scheduling agreement. Manually search for the
sales scheduling agreement again.
○ Reprocess the EDI message in the Message Dashboard
app.

If the reprocessing fails, contact the business users and ask

them to create a new sales scheduling agreement.

Field Name Detail

Error Description Sales scheduling agreement &2 of customer &1 is currently

being processed

Message No. EDI_SD820

Diagnosis The system locked the sales scheduling agreement right

now

System Response The system stops processing the EDI message

Procedure Unlock the sales scheduling agreement and process again

Field Name Detail

Error Description Sales document &2 is currently being processed by &1

Message No. Message no. V1042

Diagnosis The system locked the sales scheduling agreement right

now

System Response The system stops processing the EDI message

Procedure Unlock the sales scheduling agreement and process again

Field Name Detail

Error Description Sales scheduling agreement processing failed

Message No. EDI_SD824

Diagnosis General system message mentioned that the processing

failed due to some issue occurred

System Response

Procedure Check if detail error message output

Field Name Detail

Error Description &1 must be provided in the source data

Message No. EDI_SD825

Diagnosis Necessary fields have to be provided in pay-load file.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 69
 Field Name Detail

For example, the system uses two release type in sales

scheduling agreement:

Forecast Schedule release

JIT Schedule release

System Response The system stops processing the EDI message

Procedure Provide those mentioned fields in Payload file or EDI

segment fields

Field Name Detail

Error Description Customer reference &2 doesn't match purchase order

number &1

Message No. EDI_SD826

Diagnosis Customer reference in sales scheduling agreement does

not match purchase or-der number.

PO Number Check(No Update)(X) in the Manage Delivery

Schedule Processing app

System Response The system stops processing the EDI message

Procedure ○ Change check options for Purchase Order Number with

sold-to party in the Manage Delivery Schedule
Processing app.
○ Manually change the customer reference filed with the
matched purchase order number in the Change Sales
Scheduling Agreement app

Field Name Detail

Error Description Unloading point &1 does not match in sales scheduling
agreement &2

Message No. EDI_SD835

Diagnosis Unloading point not match in sales scheduling agreement.

Unloading point Check(No Update)(X) in the Manage

Delivery Schedule Pro-cessing app

System Response The system stops processing the EDI message

Procedure ○ Change check options for unloading point with sold-to

party in the Manage Delivery Schedule Processing app.
○ Manually change to matched unloading point filed in
the Change Sales Schedul-ing Agreement app

Field Name Detail

Error Description Delivery schedule processing option not found for sold-to
party &1

Setting Up Sales Scheduling Agreements (3NR)

70 PUBLIC On-Premise-to-Cloud Integration
 Field Name Detail

Message No. EDI_SD834

Diagnosis

System Response The system stops processing the EDI message

Procedure Create a delivery schedule processing option for sold-to

party in the Manage De-livery Schedule Processing app

Field Name Detail

Error Description JIT delivery schedule is not supported in sales scheduling

agreement &1

Message No. EDI_SD837

Diagnosis MRP for DS type setting to E JIT delivery schedules are not
used in sales schedule agreement

System Response If only created JIT delivery schedule release, system stops
processing the EDI message.

If create both FRT and JIT schedule release, system will only
process FRT release, JIT will not process

Procedure Manually change the MRP for DS type setting in Change

Sales Scheduling Agreement app More Goto Header
Sales .

Field Name Detail

Error Description Release no. &1 has already been allowed for in scheduling
agreement &2 (OP)

Message No. V4056

Diagnosis The release number entered has already been allowed for,
that is, it corresponds to the release number for the
preceding release number

System Response If the message is defined as an error in Customizing for

variable messages, the system does not allow any further
processing

Procedure Choose another release number from the number for the
preceding release number, change in Change Sales
Scheduling Agreement app Select Item Fore.DlSch or
JIT DlSch Dlv.schedule filed .

Field Name Detail

Error Description The text ID for the received text type &1 cannot be
determined

Message No. EDI_SD030

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 71
 Field Name Detail

Diagnosis The system could not determine a text type as no record

has been specified in view EDI_V_TXTIN_SUP

System Response The system stops processing the EDI message

Procedure Define mapping for inbound texts type for integration with
buyers.

Define mapping in the SSC UI step Define Mapping for

Inbound Texts for Integration with Buyers under Sales

Integration with Buyers .

Field Name Detail

Error Description Error UNCAUGHT_EXCEPTION

(1F09B73915F6B645E10000000A11447B) when calling
EDI_SD_SCHEDGAGRMT_PROCESSING

Line 1 in CL_GOAL_ACCESS================CM01I
(CL_GOAL_ACCESS================CP)

An exception with the type CX_GOAL_SCHDA_EXC was

raised, but was not handled locally or declared in a RAISING
clause.

Error when calling EDI_SD_SCHEDGAGRMT_PROCESSING

Message No. /AIF/MES078

Diagnosis The error happens when the buyer releases a quantity of

the outlined material for the first time (Initial version).

They may send the following:

○ A forecast delivery schedule and a JIT de-livery

schedule at the same time.
○ A JIT delivery schedules without a fore-cast delivery
schedule.

The system only processes the EDI message if the first

inbound delivery schedules is forecast deliv-ery schedule

System Response The system stops processing and raise exception when JIT
release coming and execute first.

The system stops processing the EDI message

Procedure ○ Contact the buyer to resend the forecast delivery

schedule.

Setting Up Sales Scheduling Agreements (3NR)

72 PUBLIC On-Premise-to-Cloud Integration
 Field Name Detail

After the system processes the forecast delivery schedule,

manually reprocess the JIT delivery schedule

Field Name Detail

Error Description The old delivery schedule &1 is not identical with delivery
schedule &2.

Message No. EDI_SD804

Diagnosis It is possible that a previous delivery schedule number of

the incoming EDI message was not scheduled in Sales
Scheduling Agreement, which means there was a gap in
delivery schedule numbers

System Response The system stops processing the EDI message

Procedure Choose another release number from the number for the
preceding release number, change in Change Sales
Scheduling Agreement app > Select Item > Fore.DlSch or JIT
DlSch > Dlv.schedule filed .

Field Name Detail

Error Description The delivery schedule &1 cannot be processed.

Message No. EDI_SD805

Diagnosis The delivery schedule key is not set to 1, 2, or blank.

The system processes the delivery schedule when the

delivery schedule key is one of the following:

•1 - The delivery schedule is to meet the Odette standard.

Schedule lines in the old delivery schedule that come before
the validity period of the new delivery schedule are copied
to the new delivery schedule.

•2 - The delivery schedule is to meet the German

Automobile Suppliers Association (VDA) standard. No
schedule lines in the old delivery schedule are copied to the
new delivery schedule.

•Blank - No schedule lines in the old delivery schedule are

copied to the new delivery schedule.

System Response The system stops processing the EDI message

Procedure As the message sender, you review the schedule line in the
purchase scheduling agreement. To recreate those old
schedule lines that are not copied, you do it manually.

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 73
 Field Name Detail

Error Description Order quantities in schedule lines have been added.

Message No. EDI_SD807

Diagnosis The system determined that you have delivered materials

behind schedule according to the planned cumulative
quantity that comes in with electronic data interchange
(EDI) message.

System Response The system adds (a) order quantities in the existing
schedule lines or (b) existing schedule lines by the quantity
that has been delivered behind schedule.

Procedure To identify changed schedule lines, compare data in the

delivery schedule with original data in the EDI message.

Field Name Detail

Error Description Order quantities in schedule lines have been deducted.

Message No. EDI_SD808

Diagnosis The system determined that you have delivered materials

ahead of schedule according to the planned cumulative
quantity that comes in with electronic data interchange
(EDI) message.

System Response The system reduces (a) order quantities in the existing
schedule lines or (b) existing schedule lines by the quantity
that has been delivered ahead of schedule.

Procedure To identify changed schedule lines, compare data in the

delivery schedule with original data in the EDI message.

Field Name Detail

Error Description The date type &1 is invalid. It can only be D, W, or M.

Message No. EDI_SD809

Diagnosis In the electronic data interchange (EDI) message, the date

type in the schedule line is invalid.

System Response The system stops processing the EDI message.

Procedure Manually correct the date type to one of the followings and
reprocess the message:

D (Day)

W (Week)

Setting Up Sales Scheduling Agreements (3NR)

74 PUBLIC On-Premise-to-Cloud Integration
 Field Name Detail

M (Month)

3.7 Appendix

3.7.1 Ticket Component

Implementation Step Component Comment

All CA-GTF-INT-EDI

Setting Up Sales Scheduling Agreements (3NR)

On-Premise-to-Cloud Integration PUBLIC 75
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.

Setting Up Sales Scheduling Agreements (3NR)

76 PUBLIC Important Disclaimers and Legal Information
Setting Up Sales Scheduling Agreements (3NR)
Important Disclaimers and Legal Information PUBLIC 77
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