Set-Up Instructions | PUBLIC

SAP S/4HANA Cloud

2023-07-03

Setting Up Accounts Payable (J60)

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

THE BEST RUN

Content

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

2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Required Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
SAP Cloud Connector for Integration with On-Premise Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

3 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1 Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Create Technical Communication User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Create Communication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Create Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 Configuration Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1 Ticket Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Setting Up Accounts Payable (J60)

2 PUBLIC Content
1 Purpose

This document describes additional configuration steps that you must perform in the productive system at the
customer's site. As these configuration steps are company-specific, they cannot be delivered by SAP, and must be
carried out by the company setting up the SAP solution.

 Caution

This setup instructions guide is only relevant for China (CN) and South Korea (KR). If you are not
implementing the solution for either country, do not process the instructions in this guide.

For China, this guide covers the following:

• Activation of the outbound services for China-specific third-party payment integration functions
• Workflow API integration functions described in the Accounts Payable (J60) test script

For South Korea, this guide covers the following:

• Registration with SmartBill to use their APIs to communicate with the National Tax Service
• Workflow API integration functions described in the Accounts Payable (J60) test script

Setting Up Accounts Payable (J60)

Purpose PUBLIC 3
2 Preparation

2.1 Required Information

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

Type of Information Required Your Data

SAML local identity provider certificate of Jam instance

 Tip
Create a ZIP file.

SAML local identity provider issuer of certificate of Jam in­

stance

Communication user ID starting with CC

SAP S/4HANA Cloud System

2.2 Prerequisites

2.2.1 SAP Cloud Connector for Integration with On-Premise

Systems

Setting Up Integration with On-Premise Systems (including SAP S/4HANA

Cloud, private edition)

For all scenarios integrating SAP S/4HANA Cloud with SAP On-Premise scenarios, the SAP_COM_0574 - SAP BTP
Connectivity Service - On Premise Integration communication arrangement must be activated. This is a prerequisite
for all other communication arrangements.

To check if the SAP_COM_0574 - SAP BTP Connectivity Service - On Premise Integration communication
arrangement is active in your system, go to the Communication Arrangements app. If it is not active, you must
set it up.

To set up the communication scenario, follow the procedure under Integrating On-Premise Systems.

Setting Up Accounts Payable (J60)

4 PUBLIC Preparation
3 Configuration

The following sections describe all settings required for this scope item. These can be divided into the following
main groups:

• Communication arrangement set-up

• Configuration using the self-service configuration user interface via the Manage Your Solution app or the
project experience in SAP Central Business Configuration

3.1 Communication Arrangement

The following communication arrangements must be activated in SAP S/4HANA for communication with web
services, depending on the integration functionalities you want to use.

 Caution

Communication arrangements SAP_COM_0554 and SAP_COM_0711 are only relevant for China.
Communication arrangement SAP_COM_0468 is only relevant for South Korea.

Table 1: Communication Arrangements for China

Communication Arrangement ID Communication Arrangement Name

SAP_COM_0554 Finance - Third-party Communication Client Integration

SAP_COM_0711 Finance - China Payment Approval Integration

Table 2: Communication Arrangements for South Korea

Communication Arrangement ID Communication Arrangement Name

SAP_COM_0468 Finance - South Korea Electronic Invoicing

3.1.1 Create Technical Communication User

Prerequisite

To carry out the following activity, a business user with a business role must exist. The business role must
contain the business catalog SAP_CORE_BC_COM (Communication Management), for example, the business role
SAP_BR_ADMINISTRATOR (Administrator).

Setting Up Accounts Payable (J60)

Configuration PUBLIC 5
Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Maintain Communication Users.
3. To create a new user, choose New. You can also use an existing user.
4. Enter a description and assign a password for the user. Choose Create.
5. Make a note of the user data for later use.

3.1.2 Create Communication System

Purpose

In this section, you create the communication systems.

 Caution

Communication arrangements SAP_COM_0554 and SAP_COM_0711 are only relevant for China.
Communication arrangement SAP_COM_0468 is only relevant for South Korea.

Procedure for SAP_COM_0554 - Only Relevant for China

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Systems.
3. Choose New.
4. Enter a system ID and system name. Choose Create.
5. In the Technical Data section, enter the Host Name and Port for the system that you wish to integrate.
6. Open Cloud Connector if required.
7. In the Users for Outbound Communication section, add an outbound user by selecting Authentication Method:
User Name and Password (for a user with access to the system maintained in Technical Data section).
8. Choose Save.

Procedure for SAP_COM_0711 - Only Relevant for China

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Systems.
3. Choose New.

Setting Up Accounts Payable (J60)

6 PUBLIC Configuration
 4. Enter a system ID and system name. Choose Create.
5. In the Technical Data section, enter the Host Name and Port for the system that you wish to integrate.
6. Open Cloud Connector if required.
7. In the Users for Inbound Communication section, add an inbound user by selecting or creating a user name and
authentication method.
8. Choose Save.

Procedure for SAP_COM_0468 - Only Relevant for South Korea

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Systems.
3. Choose New.
4. Enter a system ID and system name. Choose Create.
5. In the Technical Data section, enter the Host Name and Port for the system that you wish to integrate.
6. Open Cloud Connector if required.
7. In the Users for Inbound Communication section, add an inbound user by selecting or creating a user name and
authentication method.
8. Choose Save.

3.1.3 Create Communication Arrangement

Purpose

In this section, you create the communication arrangements.

 Caution

Communication arrangements SAP_COM_0554 and SAP_COM_0711 are only relevant for China.
Communication arrangement SAP_COM_0468 is only relevant for South Korea.

Procedure for SAP_COM_0554 - Only Relevant for China

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Arrangements.
3. Choose New to create a new communication arrangement.
4. Select SAP_COM_0554 (Finance - Third-party's Communication Client Integration).
5. Adapt the Arrangement Name if required.

Setting Up Accounts Payable (J60)

Configuration PUBLIC 7
6. Choose Create.
7. In the Common Data section, select the Communication System from the input help that was created in the
Create Communication System [page 6] section. The outbound communication user that was maintained in
the communication system is automatically added to the Outbound Communication section.
8. Activate services to be used in Outbound Services section, and enter the path and port accordingly.
9. Choose Save. The communication arrangement is activated.

Procedure for SAP_COM_0711 - Only Relevant for China

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Arrangements.
3. Choose New to create a new communication arrangement.
4. Select SAP_COM_0711 (Finance - China Payment Approval Integration).
5. Adapt the Arrangement Name if required.
6. Choose Create.
7. In the Common Data section, select the Communication System from the input help that was created in the
Create Communication System [page 6] section. The technical user that was created in the Create Technical
Communication User [page 5] section is added to the Inbound Communication section.
8. Choose Save. The communication arrangement is activated.

Procedure for SAP_COM_468 - Only Relevant for South Korea

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Arrangements.
3. Choose New to create a new communication arrangement.
4. Select SAP_COM_0468 (Finance - South Korea Electronic Invoicing).
5. Adapt the Arrangement Name if required.
6. Choose Create.
7. In the Common Data section, select the Communication System from the input help that was created in the
Create Communication System [page 6] section. The technical user that was created in the Create Technical
Communication User [page 5] section is added to the Inbound Communication section.
8. Choose Save. The communication arrangement is activated.

Setting Up Accounts Payable (J60)

8 PUBLIC Configuration
3.2 Configuration Items

Purpose

In this section, you handle additional configuration items for China.

 Caution

This section only applies to China. If you are working with the South Korea solution, do not implement
activities in this section.

Prerequisites

To carry out the following activity, a business user with a business role must exist. The business role must
contain the business catalog SAP_CORE_BC_COM (Communication Management), for example, the business role
SAP_BR_ADMINISTRATOR (Administrator) is required.

Additionally, the business role SAP_BR_BPC_EXPERT (Configuration Expert - Business Process Configuration)
must be assigned to the user.

Procedure for SAP_COM_0554

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 as a BPC_EXPERT.

2. Open Manage Your Solution.
3. If necessary, change the country or region by choosing Set Local Version.
4. Choose Configure Your Solution.
5. Search for Activate Services for Data Exchange.
6. For the Activate Services for Data Exchange row, choose Configure.
7. Continue with the procedure in the following procedure.

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. To locate the activity in
the tree view, search for the following activity: Activate Services for Data Exchange.
3. Choose Open Documentation for the found line item to see more details about this configuration activity.
4. 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.

Setting Up Accounts Payable (J60)

Configuration PUBLIC 9
5. Continue with the procedure in the following table.

Procedure

1. Make the following entries and choose Save:

Query Pay­
Send Payment ment Item Sta­ Query Bank Query Bank
Files (Out­ tus (Out­ Statement Balance (Out­
Company Code House Bank Acct ID bound) bound) (Outbound) bound)

1310 CNBK1 CNAC1 Selected Selected Deselected Selected

1310 CNBK2 CNAC9 Selected Selected Deselected Selected

1311 CNBK1 CNAC1 Deselected Deselected Deselected Deselected

 Note

For more information about the outbound services of this integration scenario, see SAP Note 2937538 .

Procedure for SAP_COM_0711

No SSCUI configuration is required for SAP_COM_0711. However, you must deactivate the predelivered payment
workflow to avoid data inconsistency.

Setting Up Accounts Payable (J60)

10 PUBLIC Configuration
4 Appendix

4.1 Ticket Component

If you encounter issues during configuration, open an SAP support ticket for the following component:

Implementation Step Component Comment

All steps for China FI-LOC-EPI-CN

All steps for South Korea XX-CSC-KR-FI

Setting Up Accounts Payable (J60)

Appendix PUBLIC 11
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 Accounts Payable (J60)

12 PUBLIC Important Disclaimers and Legal Information
Setting Up Accounts Payable (J60)
Important Disclaimers and Legal Information PUBLIC 13
www.sap.com/contactsap

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