Set-Up Instructions | PUBLIC

SAP S/4HANA Cloud

2024-06-26

Setting Up Scheduling Agreements in Procurement

(BMR)
© 2024 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Cloud-to-Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Required Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
2.2 Configuration in the SAP S/4HANA Cloud Edition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Communication User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Communication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Assign Tax Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Assign Company Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Configure Program Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Assign Program Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Output Parameter Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Assign Recipients to Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Maintain Supplier Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1 Ticket Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Setting Up Scheduling Agreements in Procurement (BMR)

2 PUBLIC Content
1 Purpose

This document describes additional configuration steps that have to be carried out by customers in order to
activate the Scheduling Agreements in Procurement. As 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 supplier system. If the supplier system is an SAP S/4HANA
cloud system, please follow the instruction in section Cloud-to-Cloud Integration:

Setting Up Scheduling Agreements in Procurement (BMR)

Purpose PUBLIC 3
2 Cloud-to-Cloud Integration

Follow the instructions in this chapter only if the supplier’s system is an SAP S/4HANA cloud system.

2.1 Preparation

2.1.1 Required Information

During the activities described in this guide, you will be required to enter or provide system-specific information. To
ensure a smooth and efficient integration with SAP S/4HANA, we recommend that you have the information listed
in the table below at hand prior to starting the integration process.

Information Required:

SAP S/4HANA Cloud system System details: URL, Username, Password

Supplier system System details like host name, URLs, URIs, User and Password.
These are just examples as details will depend on the actual
supplier system. Liaise with your supplier to get the required
system information.

2.1.2 Prerequisites

1. External system is already set up.

In order to configure the integration, users require the following catalog roles in S/4HANA CLOUD:
SAP_BR_CONF_EXPERT_BUS_NET_INT
2. It is also mandatory that scope item BMR- Scheduling Agreements in Procurement is active.
• 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, please request the activation via BCP – Ticket Component: XX-S4C-OPR-SRV.

Setting Up Scheduling Agreements in Procurement (BMR)

4 PUBLIC Cloud-to-Cloud Integration
2.2 Configuration in the SAP S/4HANA Cloud Edition

Prerequisite

To configure the EDI integration, users require the following catalog roles in S/4HANA 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)

2.2.1 Communication User

Procedure

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

2.2.2 Communication System

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Systems.
3. Choose New.
4. In the dialog box, maintain System ID and System Name. For example, ID: <EDI_Integration_Buyer>,
, System Name: < EDI_Integration_Buyer>.
5. Choose Create.
6. Maintain Host Name. <Supplier system>.
7. Add a User for Inbound Communication. In the dialog box, choose User Name and Password as Authentication
Method. The User Name is the user you created in the previous chapter. Choose OK.

Setting Up Scheduling Agreements in Procurement (BMR)

Cloud-to-Cloud Integration PUBLIC 5
8. Add a User for Outbound Communication. In the dialog box, choose User Name and Password as Authentication
Method. User Name and Password are provided by the supplier. Choose Create.
9. Add a Business Partner, then choose the supplier from the list that corresponds with the communication
system you are currently creating. For example, 10300001.
10. Choose Save.

2.2.3 Communication Arrangement

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Arrangements.
3. Choose New.
4. In the dialog box, maintain Scenario SAP_COM_0445 Sourcing and Procurement Scheduling Agreements With
Suppliers Integration and enter an Arrangement Name.
5. Choose Create.
6. Maintain Communication System as defined in Communication System [page 5] section. For example,
<EDI_Integration_Buyer>.
7. 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.
8. Under Outbound Services, maintain the Path for Request to create/change/delete Scheduling Agreement
release service.
The path to be used is specific to the target system and can be provided by the supplier only.
For example,

Outbound Services Path

Request to create/change/delete scheduling agreement re- /sap/bc/srt/scs_ext/sap/

lease schedgagrmtdlivschedule_in

9. Choose Save.

2.2.4 Assign Tax Codes

Use

In this activity you map tax rates and tax types, as sent by your supplier’s system, to tax codes used by your SAP
S/4HANA Cloud system.

Setting Up Scheduling Agreements in Procurement (BMR)

6 PUBLIC Cloud-to-Cloud Integration
For example, in an incoming invoice the supplier sends a tax rate of "19.000000 %" and tax type "VAT". In your
SAP S/4HANA Cloud system, this would fall under tax code "V1". Thus, the corresponding mapping needs to be
maintained in this activity.

Procedure

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

Configure Your Solution:

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Navigate to Implementation Cockpit Manage Your Solution Configure Your Solution .
3. On the Configure Your Solution: Realize Phase screen, select the values as shown below:
• Application Area: Sourcing and Procurement
• Sub-application area: Integration
4. In the Configure Item area, choose the entry with above values and Name: Integration with Suppliers.
5. On the Configure Your Solution: Integration with Suppliers screen, choose the Configuration Steps tab.
6. Search for Assign Tax Codes for the Transfer of Supplier Invoices and select Configure.
7. Choose New Entries.
8. Enter the supplier’s ID as Invoicing Party.
9. Enter the type of tax (for example VAT) under Tax Type.
10. Enter the country where the transaction originates from under Country/Region Key.
11. Under Tax Code enter the respective tax code of your SAP S/4HANA Cloud system.
For example,

Field Name and their corresponding User Action and Values

Invoicing Party Tax Type Tax Rate Country/Region Key Tax Code

____(blank) VAT 0,000000 DE V0

____(blank) VAT 7,000000 DE V2

____(blank) VAT 19,000000 DE V1

12. Choose Save.

13. One line item has to be created for each tax code mapping.

SAP Central Business Configuration:

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

2. Go to the Business Processes Configuration app. To locate the activity in the tree view, search for the following
activity: Assign Tax Codes for the Transfer of Supplier Invoices.
Choose Open Documentation for the found line item to see more details about this configuration activity.
Choose the link 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.
4. Enter the supplier’s ID as Invoicing Party.

Setting Up Scheduling Agreements in Procurement (BMR)

Cloud-to-Cloud Integration PUBLIC 7
5. Enter the type of tax (for example VAT) under Tax Type.
6. Enter the country where the transaction originates from under Country/Region Key.
7. Under Tax Code enter the respective tax code of your SAP S/4HANA Cloud system.
For example,

Field Name and their corresponding User Action and Values

Invoicing Party Tax Type Tax Rate Country/Region Key Tax Code

____(blank) VAT 0,000000 DE V0

____(blank) VAT 7,000000 DE V2

____(blank) VAT 19,000000 DE V1

8. Choose Save.
9. One line item has to be created for each tax code mapping.

2.2.5 Assign Company Code

Use

In this activity, you map the name or the account number, which your supplier (invoicing party) uses in invoices for
your company, to the company code ID as used by your SAP system.

Procedure

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

Configure Your Solution:

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Navigate to Implementation Cockpit Manage Your Solution Configure Your Solution .
3. On the Configure Your Solution: Realize Phase screen, select the values as shown below:
• Application Area: Sourcing and Procurement
• Sub-application area: Integration
4. In the Configure Item area, choose the entry with above values and Name: Integration with Supplier.
5. On the Configure Your Solution: Integration with Suppliers screen, choose the Configuration Steps tab.
6. Search for Assign Company Code and select Configure.
7. Choose New Entries.
8. As Invoicing Party, enter the supplier's ID. For example, 10300001.

Setting Up Scheduling Agreements in Procurement (BMR)

8 PUBLIC Cloud-to-Cloud Integration
9. Enter the name or the account number, which your supplier uses in invoices for your company, as
Company Code Name. For example: 10100003, which is Bill-To Party ID for business partner 10100003 in
communication system
10. Enter the Company Code, for example 1010, used in your SAP S/4HANA Cloud system.
11. Choose Save.
12. One line item should be created for each company code mapping.

SAP Central Business Configuration:

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

2. Go to the Business Processes Configuration app. To locate the activity in the tree view, search for the following
activity: Assign Company Code.
Choose Open Documentation for the found line item to see more details about this configuration activity.
Choose the link 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.
4. As Invoicing Party, enter the supplier's ID. For example, 10300001.
5. Enter the name or the account number, which your supplier uses in invoices for your company, as
Company Code Name. For example: 10100003, which is Bill-To Party ID for business partner 10100003 in
communication system
6. Enter the Company Code, for example 1010, used in your SAP S/4HANA Cloud system.
7. Choose Save.
8. One line item should be created for each company code mapping.

2.2.6 Configure Program Parameters

Use

In this activity, you define document types and other control parameters for incoming invoices.

Procedure

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

Configure Your Solution:

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

2. Go to the Business Processes Configuration app. Search for Assign Tax Codes and choose Go to Activity 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. On the Configure Your Solution: Realize Phase screen, select the values as shown below:
• Application Area: Sourcing and Procurement

Setting Up Scheduling Agreements in Procurement (BMR)

Cloud-to-Cloud Integration PUBLIC 9
 • Sub-application area: Integration
4. In the Configure Item area, choose the entry with above values and Name: Integration with Supplier.
5. On the Configure Your Solution: Integration with Suppliers screen, choose the Configuration Steps tab.
6. Search for Configure Program Parameters and select Configure.
7. Choose New Entries.
8. Enter the program parameters configuration ID, for example: Default.
9. Enter RE as Invoice Doc. Type.
10. Enter RE as Cred.Memo Doc. Type.
11. In the Processing field, choose Unclarified error: park invoice.
12. Don't tick any of the check boxes: Check matl no, Check UoM, Check.
13. Choose Save.

SAP Central Business Configuration:

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

2. Go to the Business Processes Configuration app. To locate the activity in the tree view, search for the following
activity: Configure Program Parameters.
Choose Open Documentation for the found line item to see more details about this configuration activity.
Choose the link 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.
4. Enter the program parameters configuration ID, for example: Default.
5. Enter RE as Invoice Doc. Type.
6. Enter RE as Cred.Memo Doc. Type.
7. In the Processing field, choose Unclarified error: park invoice.
8. Don't tick any of the check boxes: Check matl no, Check UoM, Check.
9. Choose Save.

2.2.7 Assign Program Parameters

Use

In this activity, you define document types and other control parameters for incoming invoices.

Procedure

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

Configure Your Solution:

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a
Configuration Expert - Business Process Configuration.

Setting Up Scheduling Agreements in Procurement (BMR)

10 PUBLIC Cloud-to-Cloud Integration
2. Navigate to Implementation Cockpit Manage Your Solution Configure Your Solution .
3. On the Configure Your Solution: Realize Phase screen, select the values as shown below:
• Application Area: Sourcing and Procurement
• Sub-application area: Integration
4. In the Configure Item area, choose the entry with above values and Name: Integration with Supplier.
5. On the Configure Your Solution: Integration with Suppliers screen, choose the Configuration Steps tab.
6. Search for Assign Program Parameters and select Configure.
7. Choose New Entries.
8. Enter the previously created program parameters configuration ID.
9. Choose Save.

SAP Central Business Configuration:

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

2. Go to the Business Processes Configuration app. To locate the activity in the tree view, search for the following
activity: Assign Program Parameters.
Choose Open Documentation for the found line item to see more details about this configuration activity.
Choose the link 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.
4. Enter the previously created program parameters configuration ID.
5. Choose Save.

2.2.8 Output Parameter Determination

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Navigate to Output Control Output Parameter Determination .
3. Enter Show rules for: Scheduling Agreement Releases and Determination Step: Channel.
4. For each supplier to whom you would like to send Scheduling Agreement Releases via EDI, create an entry such
as the one below:

Output Type Role Recipient Channel

SCHEDULING_AGREE- LF Supplier ID that shall receive EDI

MENT_REL Scheduling Agreement Re-
leases via EDI

5. Activate the new entries (you’ll have to confirm the activation in a dialog box).
6. Navigate to Output Control Output Parameter Determination .
7. Enter Show rules for: Scheduling Agreement Releases and Determination Step: Output Type.
8. Maintain the following entries:
• Document Type: Empty
• Output Type: SCHEDULING_AGREEMENT_REL
• Dispatch time: 1 (immediately)
9. Activate the new entries (you’ll have to confirm the activation in a dialog box).

Setting Up Scheduling Agreements in Procurement (BMR)

Cloud-to-Cloud Integration PUBLIC 11
2.2.9 Assign Recipients to Users

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Navigate to Message Monitoring Assign Recipients to Users
3. In the left Users assigned to recipients area, choose Add User, enter the user, e.g. Configuration Expert –
Business Network Integration, choose Add.
4. 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.
5. In the Assign Recipients dialog box, enter the following settings:

Name- Recipient
space Name Message Type Overview Technical User

/MMSAR EDI_MM_ Application Error or Technical Error Set flag Set flag
SCHED-
GAGRMT_
RECIPI-
ENT

6. Choose Assign.
7. Repeat the steps from 4 to 6 for following Namespace and Recipient Name:

Name-
space Recipient Name

/MMEDI EDI_MM_INVC_RECIPIENT

/LEEDI EDI_DELIN_RECIPIENT

The sequence of activities for the communication arrangement, interaction with Cloud Service Center, and the
self-service configuration user interface can vary and need to be adapted by authors accordingly.

2.2.10 Maintain Supplier Master Data

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Manage Supplier Master Data.
3. On the Supplier Master screen, enter your business partner in the business partner field, for example:
10300001.
4. Choose Go and select the supplier entry.
5. On the Supplier screen, choose Edit.
6. On the Company Codes tab, choose the entry with the company code value, for example: Company Code:
1010.
7. On the Company Code screen, select the Correspondance tab.
8. Enter your supplier as Account at Supplier. For example: 10100003, which is Bill-To Party ID for business
partner 10100003 in communication system

Setting Up Scheduling Agreements in Procurement (BMR)

12 PUBLIC Cloud-to-Cloud Integration
9. Choose Save.

Setting Up Scheduling Agreements in Procurement (BMR)

Cloud-to-Cloud Integration PUBLIC 13
3 Appendix

3.1 Ticket Component

Purpose Component Comment

For issues about the overall integration CA-GTF-INT-EDI

process as well as the SAP Cloud Integra-
tion

For all issues related to the procurement MM-PUR-GF-EDI

system

For all issues related to the sales system SD-SLS-OA-EDI or SD-BIL-EDI

Setting Up Scheduling Agreements in Procurement (BMR)

14 PUBLIC Appendix
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

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 Scheduling Agreements in Procurement (BMR)

Important Disclaimers and Legal Information PUBLIC 15
www.sap.com/contactsap

© 2024 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