Set-Up Instructions | PUBLIC

SAP S/4HANA Cloud

2023-07-03

Setting Up Compliance Formats - Support Preparation

(1J2)
© 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
2.3 SAP Cloud Connector for Integration with On-Premise Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Configuring Communication Management - SAP_COM_0438. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

3.1 Communication User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2 Communication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3 Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4 Configuring Communication Arrangement - SAP_COM_0733 (Only for Brazil). . . . . . . . . . . . . . . . 10

4.1 Technical Communication User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2 Communication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.3 Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

5 Configuring Communication Arrangement - SAP_COM_0775 (Only for Brazil). . . . . . . . . . . . . . . . 12

5.1 Technical Communication User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.2 Communication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.3 Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

6 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.1 Ticket Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Setting Up Compliance Formats - Support Preparation (1J2)

2 PUBLIC Content
1 Purpose

This document describes additional configuration steps that you must carry out in the productive system on
customer site to activate the electronic submission of Compliance Formats - Support Preparation (formerly
Advance Compliance Reporting) standard reports . 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 Brazil (BR), Germany (DE), Singapore (SG), Netherlands
(NL), Great Britain (GB), and New Zealand (NZ). If you are not implementing the solution for one of those
countries, do not process the instructions in this guide. For Brazil (BR), Germany (DE), Singapore (SG),
Netherlands (NL), Great Britain (GB), and New Zealand (NZ), this is relevant for the following reports:

Brazil

• EFD-Reinf Report
• EFD-ICMS-IPI Report
• ECD Report
• ECF Report
• EFD Contribuições Report

Germany:

• Advance VAT Return

• Application for Permanent Extension
• Registration of Special Advance Payment

Singapore:

• GST Return Submission

Netherlands:

• EC Sales List
• VAT Return

Great Britain:

• Great Britain - Northern Ireland EC Sales List

• VAT Return
• Withholding Tax Report

New Zealand:

• Goods and Services Tax (GST) Report

Setting Up Compliance Formats - Support Preparation (1J2)

Purpose PUBLIC 3
2 Preparation

2.1 Required Information

During the course of the activities described in this guide, you will be required to 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 Recommendation: 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

Before you start installing this scenario, check if the following prerequisites are prepared.

• External system SAP Localization Hub Advanced Compliance Reporting (SLHACR) is already configured and
setup.

Setting Up Compliance Formats - Support Preparation (1J2)

4 PUBLIC Preparation
2.3 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 Compliance Formats - Support Preparation (1J2)

Preparation PUBLIC 5
3 Configuring Communication Management -
SAP_COM_0438

3.1 Communication User

Use

In SAP S/4HANA Cloud, the management of data integration is based on communication scenarios. The relevant
communication scenario for SAP S/4HANA Compliance Formats - Support Preparation (formerly Advance
Compliance Reporting) to SAP Localization Hub Advanced Compliance Reporting (SLHACR) Integration is
SAP_COM_0438. For the communication scenario, a communication user is needed.

Procedure

1. Log on to your SAP S/4HANA system as a Configuration Expert - Business Network Integration
(SAP_BR_CONF_EXPERT_BUS_NET_INT).
2. From the SAP Fiori launchpad, open Maintain Communication Users (F1338).
3. Choose New to create a new communication user.
4. On the Create Communication User screen, make the following entries and choose Create:

Field Name User Entry or Actions

User Name For example, DUMMY_USER

Description For example, DUMMY_USER

Password For example, Initial1!

Setting Up Compliance Formats - Support Preparation (1J2)

6 PUBLIC Configuring Communication Management - SAP_COM_0438
3.2 Communication System

Use

A communication system is used to define the host name of the HCI tenant and to assign users for the inbound and
outbound communication.

Additionally, a second communication system with the host name of the external system is needed to enable
the navigation from SAP S/4HANA to external system. A communication user is not needed here to access the
external system.

Procedure

1. Log on to your SAP S/4HANA system as a Configuration Expert - Business Network Integration
(SAP_BR_CONF_EXPERT_BUS_NET_INT).
2. From the SAP Fiori launchpad, open Communication Systems (F1762).
3. Choose New to create a new communication system.
4. On the New Communication System screen, make the following entries and choose Create:

Field Name User Entry or Action

ID For example, External Service

System Name For example, External Service

5. On the Communication System screen, make the following entries:

Field Name User Entry or Action Comments

Host Name <host name from external

system account services or
support representative>

Auth. Endpoint <endpoint from an external If you do not plan to use OAuth authen­
system account services or tication, skip this field.
support representative>

Token Endpoint <endpoint from an external If you do not plan to use OAuth authen­
system account services or tication, skip this field.
support representative>

6. In the Users for Outbound Communication area, choose Add.

Setting Up Compliance Formats - Support Preparation (1J2)

Configuring Communication Management - SAP_COM_0438 PUBLIC 7
7. Make the following entries and choose Create:

Field Name User Entry or Action Comments

Authentication Method User name and password

Or

OAuth 2.0

User Name <user name for external Only enter this value if you selected
system logon> the User name and password authenti­
cation method in the first row

Password <password for external Only enter this value if you selected
system logon> the User name and password authenti­
cation method in the first row

OAuth 2.0 Client ID <client ID of external Only enter this value if you selected the
system> OAuth 2.0 authentication method in the
first row

Client Secret <client secret of external Only enter this value if you selected the
system> OAuth 2.0 authentication method in the
first row

8. Choose Save.

3.3 Communication Arrangement

Use

The Communication arrangement in SAP S/4HANA system defines all relevant information for the communication
with Integration. For example, it contains the communication system, inbound and outbound authentication.

Procedure

1. Log on to your SAP S/4HANA system as a Configuration Expert - Business Network Integration
(SAP_BR_CONF_EXPERT_BUS_NET_INT).
2. From the SAP Fiori launchpad, open Communication Arrangements (F1763).
3. Choose New.

Setting Up Compliance Formats - Support Preparation (1J2)

8 PUBLIC Configuring Communication Management - SAP_COM_0438
4. On the New Communication Arrangement screen, make the following entries and choose Create:

Field Name User Entry or Action

Scenario SAP_COM_0438

Arrangement Name <Arrangement name of this Communication

Arrangement>

5. On the Communication Arrangements screen, make the following entries and choose Create:

Field Name User Entry or Action

Communication System <communication system from prior

section>

User Name/Certificate <username of outbound communication is

automatically assigned after you select
the communication system>

6. Choose Save. The communication arrangement becomes active and all required configurations are generated.

Setting Up Compliance Formats - Support Preparation (1J2)

Configuring Communication Management - SAP_COM_0438 PUBLIC 9
4 Configuring Communication Arrangement -
SAP_COM_0733 (Only for Brazil)

The following communication arrangements must be activated in SAP S/4HANA for communication with web
services.

Communication Arrangement ID Name of Communication Arrangement

SAP_COM_0733 Finance - Complementary Data Transfer for Brazilian ACR Reports Integration

4.1 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).

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Maintain Communication Users (F1338).
3. Choose New to create a new user (for example, USER_NAME) or select an existing user.
4. Enter a description for the user.
5. Assign a password for the user.
6. Choose Create.
7. Make a note of user data. This is required when you create the communication arrangement.

Setting Up Compliance Formats - Support Preparation (1J2)

10 PUBLIC Configuring Communication Arrangement - SAP_COM_0733 (Only for Brazil)
4.2 Communication System

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Systems (F1762).
3. Choose New to create a new system.
4. Enter a system ID and a system name.
5. Choose Create.
6. In the Technical Data section, enter host and port information.
7. Choose Save.

4.3 Communication Arrangement

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Arrangements (F1763).
3. Choose New to create a new communication arrangement.
4. Select SAP_COM_0733 (Communication Arrangement Name).
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
Communication System section.The technical user that was created in the Technical Communication User
section is automatically added to the Inbound Communication section.
8. Choose Save.

The communication arrangement will be activated.

Setting Up Compliance Formats - Support Preparation (1J2)

Configuring Communication Arrangement - SAP_COM_0733 (Only for Brazil) PUBLIC 11
5 Configuring Communication Arrangement -
SAP_COM_0775 (Only for Brazil)

The following communication arrangements must be activated in SAP S/4HANA for communication with web
services.

Communication Arrangement ID Name of Communication Arrangement

SAP_COM_0775 Finance - ACR Services for Partner Enablement Integration

5.1 Technical Communication User

Prerequisite

To perform 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).

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Maintain Communication Users (F1338).
3. Choose New to create a new user (for example, USER_NAME) or select an existing user.
4. Enter a description for the user.
5. Assign a password for the user.
6. Choose Create.
7. Make a note of user data. This is required when you create the communication arrangement.

Setting Up Compliance Formats - Support Preparation (1J2)

12 PUBLIC Configuring Communication Arrangement - SAP_COM_0775 (Only for Brazil)
5.2 Communication System

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Systems (F1762).
3. Choose New to create a new system.
4. Enter a system ID and a system name.
5. Choose Create.
6. In the Technical Data section, enter host and port information.
7. Choose Save.

5.3 Communication Arrangement

Procedure

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Communication Arrangements (F1763).
3. Choose New to create a new communication arrangement.
4. Select SAP_COM_0775 (Communication Arrangement Name).
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
Communication System [page 13] section.The technical user that was created in the Technical Communication
User [page 12] section is automatically added to the Inbound Communication section.
8. Choose Save.

The communication arrangement is activated.

Setting Up Compliance Formats - Support Preparation (1J2)

Configuring Communication Arrangement - SAP_COM_0775 (Only for Brazil) PUBLIC 13
6 Appendix

6.1 Ticket Component

In case of issues during the configuration, open an SAP support ticket for the following component.

Implementation Step Component Comment

Creation of Communication System FI-LOC-SRF-RUN

and Communication Arrangement
FI-LOC-FI-BR-ACR (For
SAP_COM_0733 )

Setting Up Compliance Formats - Support Preparation (1J2)

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 Compliance Formats - Support Preparation (1J2)

Important Disclaimers and Legal Information PUBLIC 15
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