CONFIDENTIAL

2024-10-18

Administration Guide for SAP Group Reporting

Data Collection - Integration with SAP S/4HANA
Cloud, public edition
© 2024 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Technical Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 Supported Data Centers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Onboarding for SAP Group Reporting Data Collection Applications on SAP S/4HANA
Cloud - Main Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4 Subscribe to SAP Group Reporting Data Collection Applications. . . . . . . . . . . . . . . . . . . . . . . 10

5 Create a Service Instance of SAP Group Reporting Data Collection for the Datamapping
Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

6 Create a Service Instance of SAP Group Reporting Data Collection for SAP Cloud
Transport Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

7 Configuration and Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

7.1 Identity Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.2 Establish Your Communication Arrangement in SAP S/4HANA Cloud. . . . . . . . . . . . . . . . . . . . . . . .19
Create a Technical Communication User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Create a Communication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Create a Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.3 Create HTTP Destinations on SAP Business Technology Platform. . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.4 Automatically Update the Import Status from your SAP S/4HANA Cloud System. . . . . . . . . . . . . . . 25
7.5 Display a Link to the Task Log App in the Data Mapping Job List or Runs. . . . . . . . . . . . . . . . . . . . . 28

8 Optional Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

8.1 Enable Custom Fields for Manual Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
8.2 Enable Custom Fields for Data Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
8.3 Update Custom Fields for Data Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
8.4 Enable SAP Controlling - Profitability Analysis (CO-PA) Fields for Data Mapping. . . . . . . . . . . . . . . . 34
8.5 Configure Destinations for Scheduled Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.6 Configure Destinations for Remotely Stored Folders or CSV Files. . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.7 Add Cache Duration Parameter for Enter Package Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
8.8 Configure Destinations for ACDOCA or ACDOCU as Source Instances. . . . . . . . . . . . . . . . . . . . . . . 41
8.9 Configure Destinations for SAP ECC as Source Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configure the Cloud Connector for SAP ECC as Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Create Destinations for SAP ECC as Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
2 CONFIDENTIAL Content
8.10 Configure Destinations for OData Custom Connections as Source Instances for Data Mapping
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

8.11 Enable Custom Themes Using UI Theme Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

8.12 Configure Destinations for Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

9 User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

9.1 Define and Bundle Roles on SAP Business Technology Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . 52

9.2 Add Business Catalogs to Business Users in SAP S/4HANA Cloud. . . . . . . . . . . . . . . . . . . . . . . . . .55

10 SAP Cloud Transport Management Service Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . 57

11 Group Journal Entries - Import API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

11.1 List Mapping Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

11.2 List Mapping Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

11.3 Start Running a Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

11.4 Start Running a Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

11.5 Process Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

11.6 Close Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

11.7 Retrieve Mapped Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

11.8 Send Mapped Data to Backend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

11.9 Delete Mapped Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

11.10 Cancel a Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

11.11 Retrieve the Run Result. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

11.12 Retrieve the Mapping Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

11.13 Retrieve the Import Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

11.14 Create a Batch Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

12 Security and Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

12.1 Security Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

12.2 Additional Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

12.3 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Information Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Deletion of Personal Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

12.4 Export Comments, Questions, and Answers Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

13 Get Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

13.1 Cloud System Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Content CONFIDENTIAL 3
1 Overview

About This Guide

This administration guide describes the steps you need to perform as an administrator to set up and run SAP
Group Reporting Data Collection. It covers application-specific information only. For general information about
SAP Business Technology Platform, see the documentation on SAP Help Portal at https://help.sap.com/CP.

This guide addresses the following target audience:

• System administrators
• Key users

About SAP Group Reporting Data Collection

SAP Group Reporting Data Collection is hosted on the SAP Business Technology Platform and relies on data
such as master data and allowed breakdowns from SAP S/4HANA Cloud. For more information about using
the functions and features provided by SAP Group Reporting Data Collection, see the user guide on SAP Help
Portal at SAP Group Reporting Data Collection.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
4 CONFIDENTIAL Overview
1.1 System Landscape

The figure below provides an overview of the system landscape for SAP Group Reporting Data Collection and is
followed by an explanation:

The system landscape consists of the following main areas:

• SAP Business Technology Platform

SAP Group Reporting Data Collection is provided by SAP using an SAP Business Technology Platform (SAP
BTP) provider account which you subscribe to using your SAP BTP customer account.
On SAP BTP, your customer account establishes the connection to the SAP Fiori launchpad for SAP Group
Reporting Data Collection using SAP S/4HANA Cloud SDK and OData services.
• SAP S/4HANA Cloud
The SAP BTP app writes consolidation data back to SAP S/4HANA Cloud, application component FIN-CS,
using SAP S/4HANA Cloud SDK and OData services.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Overview CONFIDENTIAL 5
2 Technical Prerequisites

Before you start to use SAP Group Reporting Data Collection, check the requirements and recommendations in
this section.

Browser and Browser Settings

You need an installed browser to run SAP Group Reporting Data Collection. SAP recommends that you use
Google Chrome, Mozilla Firefox, or Microsoft Edge based on Chromium.

Integration Procedure

To access the integration procedure between finDncLDl group reporting in SAP S/4HANA and SAP Group
Reporting Data Collection (deployed on the SAP BTP), you need to activate the Group Reporting - Data from
SAP Group Reporting Data Collection (287) scope item.

 Note

For more information, see https://me.sap.com/processnavigator/globalSearch/287 .

Pre-Defined Content for Forms

If you want to use pre-defined forms in the Manage Forms app, you must activate the following scope items:

Pre-Defined Form Scope Item

Actual Reported Data Group Reporting - Financial Consolidation (1SG)

 Note
For more information, see https://me.sap.com/process-
navigator/globalSearch/1SG .

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
6 CONFIDENTIAL Technical Prerequisites
 Pre-Defined Form Scope Item

Consolidation of Investments Group Reporting - Financial Consolidation (1SG), only for

SAP S/4 HANA 2020 and higher

 Note
For more information, see https://me.sap.com/process-
navigator/globalSearch/1SG .

ESG (Environmental, Social, and Governance) Data Group Reporting - Environmental, Social, and Governance
Data (4R7)

 Note
For more information, see https://me.sap.com/process-
navigator/globalSearch/4R7 .

Reported Financial Data Integration (SAP_COM_0248)

You must apply the Reported Financial Data Integration (SAP_COM_0248) scenario. This communication
scenario provides the following SOAP-based APIs for submitting reported financial data from an external
system to SAP S/4HANA or SAP S/4HANA Cloud for group reporting and receiving confirmations:

• FinancialConsolidationReportedFinancialDataBulkIn: Reported Financial Data for Group Reporting - Bulk

Import and Update
• FinancialConsolidationReportedFinancialDataBulkOut: Reported Financial Data for Group Reporting -
Receive Confirmation

For more information about both API services, see the SAP API Business Hub .

2.1 Supported Data Centers

SAP Group Reporting Data Collection supports the following data centers:

Region Infrastructure Provider Region Host

Europe (Frankfurt) Amazon Web Services (AWS) eu10.hana.ondemand.com

Europe (Frankfurt) EU access only Amazon Web Services (AWS) eu11.hana.ondemand.com

Canada (Montreal) Amazon Web Services (AWS) ca10.hana.ondemand.com

 Note

SAP Personal Data Manager is not available for the Canada (Montreal) cf-ca10 region.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Technical Prerequisites CONFIDENTIAL 7
3 Onboarding for SAP Group Reporting
Data Collection Applications on SAP S/
4HANA Cloud - Main Steps

This section gives you an overview of each step to perform when onboarding the SAP Group Reporting Data
Collection apps on SAP S/4HANA Cloud.

Hover over each step and click it to get detailed information on the tasks to perform.

• #unique_5/unique_5_Connect_42_subsection-im1 [page 9]
• #unique_5/unique_5_Connect_42_subsection-im2 [page 9]
• #unique_5/unique_5_Connect_42_subsection-im3 [page 9]
• #unique_5/unique_5_Connect_42_subsection-im4 [page 9]
• #unique_5/unique_5_Connect_42_subsection-im5 [page 9]

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Onboarding for SAP Group Reporting Data Collection Applications on SAP S/4HANA
8 CONFIDENTIAL Cloud - Main Steps
Get your subaccount for Cloud Foundry (Step 1)

 Note

SAP Group Reporting Data Collection is available for the following regions:

• Europe (Frankfurt) cf-eu10

• Europe (Frankfurt) cf-eu11
• Canada (Montreal) cf-ca10

For more information, see the SAP Business Technology Platform Basic Platform Concepts Regions
documentation: Regions.

Subscribe to SAP Group Reporting Data Collection with the correct entitlement (Step 2)
For more information, see Subscribe to SAP Group Reporting Data Collection Applications [page 10].

Configure your Identity Provider - IdP (Step 3)

For more information, see Identity Provider [page 19].

Establish Your Communication Arrangement in SAP S/4HANA Cloud (Step 4)

For more information, see Establish Your Communication Arrangement in SAP S/4HANA Cloud [page 19].

Create HTTP Destinations (Step 5)

For more information, see Create HTTP Destinations on SAP Business Technology Platform [page 23] and
Managing Destinations.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Onboarding for SAP Group Reporting Data Collection Applications on SAP S/4HANA
Cloud - Main Steps CONFIDENTIAL 9
4 Subscribe to SAP Group Reporting Data
Collection Applications

The following section explains how to subscribe to SAP Group Reporting Data Collection applications.

Prerequisites

1. An SAP identity provider or any other identity provider that supports SAML2.0.
2. A global account for SAP Business Technology Platform. To onboard to SAP Business Technology Platform,
follow the SAP BTP documentation under: Subscribe to Multitenant Applications Using the Cockpit.
3. A subaccount for the Cloud Foundry environment.

 Note

SAP Group Reporting Data Collection is available for the following regions:
• Europe (Frankfurt) cf-eu10
• Europe (Frankfurt) cf-eu11
• Canada (Montreal) cf-ca10
For more information, see the SAP Business Technology Platform Basic Platform Concepts
Regions documentation: Regions.

4. Then you must ensure that the SAP Group Reporting Data Collection entitlement is assigned to your
subaccount. For more information, see Configure Entitlements and Quotas for Subaccounts.

Context

Once you have performed the prerequisites above, you can subscribe to SAP Group Reporting Data Collection
applications using the following steps:

Procedure

1. Open the SAP BTP Cockpit and navigate to your subaccount under the global account.
2. Choose Instances and Subscriptions to display a list of the applications to which you have subscribed.
3. Choose Create.

The New Instance or Subscription dialog box opens.

4. From the Service list, select the SAP Group Reporting Data Collection application.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
10 CONFIDENTIAL Subscribe to SAP Group Reporting Data Collection Applications
  Note

The Service list allows you to create service instances to consume services or environments, and
subscriptions to consume applications.

5. Select the standard plan.

6. Choose Create.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Subscribe to SAP Group Reporting Data Collection Applications CONFIDENTIAL 11
5 Create a Service Instance of SAP
Group Reporting Data Collection for the
Datamapping Plan

If you want to use the Group Journal Entries - Import API or automatically update the import status from
your SAP S/4HANA Cloud or SAP S/4HANA system, you need to enable the SAP Group Reporting Data
Collection Service. You first create an instance of the SAP Group Reporting Data Collection Service and then
create service keys for accessing it. These tasks are performed in the SAP BTP cockpit.

Prerequisites

 Note

The procedure described in this chapter is intended only for Group Journal Entries - Import API users or
for configuring the display of the import status in real time, it is not required if you want to use SAP Group
Reporting Data Collection applications.

You have subscribed to SAP Group Reporting Data Collection in your subaccount, as described in the previous
chapter: Subscribe to SAP Group Reporting Data Collection Applications [page 10].

Context

To enable the Group Journal Entries - Import API or to enable the display of the import status in real time, you
perform the following steps:

1. Create a service.
2. If necessary, enable Cloud Foundry.
3. Create a space.
4. Create a service instance.
5. Create service keys.
6. Create a JSON web token.

Procedure

1. To create a service:
a. Ensure that you have entitled the Group Reporting Data Collection service with the Datamapping
plan to your global account. This service plan is required to push data to ACDOCU through the Data
Mapping application.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Create a Service Instance of SAP Group Reporting Data Collection for the
12 CONFIDENTIAL Datamapping Plan
 b. In the SAP BTP Cockpit, navigate to Entitlements Subaccount Assignments and select your
subaccount from the drop-down list.
c. Select Go.
d. If there are no entries maintained for Service Group Reporting Data Collection, choose Configure
Entitlements Add Service Plans .
e. From the pop-up choose SAP Group Reporting Data Collection Service.
f. Select the service plan datamapping and choose the Add 1 Service Plans button.
g. Save your changes.

Following is a screenshot of the entitlement screen on SAP BTP Cockpit.

 Note

For more information, see the "Configure Entitlements and Quotas for Subaccounts" chapter of the
SAP Business Technology Platform documentation.

2. To enable Cloud Foundry if it hasn't already been done:

a. Navigate within the SAP BTP Cockpit to the overview section of your subaccount.
b. Choose the Enable Cloud Foundry button.
c. Enter a name and choose Create.
3. To create a service instance:

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Create a Service Instance of SAP Group Reporting Data Collection for the
Datamapping Plan CONFIDENTIAL 13
 a. In the subaccount in which you are entitled to use the SAP Group Reporting Data Collection Service,
choose Cloud Foundry Spaces in the navigation area.
b. If you do not have a space yet, create one as described in the "Create Spaces" chapter of the SAP
Business Technology Platform documentation. Open the newly created space in which you want to
create a service instance.
c. Choose Services Service Marketplace for your space in the SAP BTP Cockpit. All available
services are displayed here.
d. Choose the SAP Group Reporting Data Collection tile.
e. Choose Create.
f. Select the SAP Group Reporting Data Collection service, the datamapping plan and choose Create.

4. Create a service key to generate the credentials needed to communicate directly with the service instance:
a. Choose the service instance which has been created in the previous step.
b. Create a service key from the right-hand navigation pane.
c. On the pop-up, enter a name for the service key and choose Save.

 Note

Detailed instructions to create the service keys are described in the "Create Service Keys Using the
Cockpit" chapter of the SAP Business Technology Platform documentation.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Create a Service Instance of SAP Group Reporting Data Collection for the
14 CONFIDENTIAL Datamapping Plan
6 Create a Service Instance of SAP Group
Reporting Data Collection for SAP Cloud
Transport Management

If you want to transport objects between different subaccounts of SAP Group Reporting Data Collection
using SAP Cloud Transport Management, you need to enable the corresponding SAP Group Reporting Data
Collection service.

Prerequisites

 Note

The procedure described in this chapter is intended only if you want to use SAP Cloud Transport
Management, it is not required if you want to use SAP Group Reporting Data Collection applications only.

 Note

A dedicated license is required to use SAP Cloud Transport Management with SAP Group Reporting Data
Collection.

You have subscribed to SAP Group Reporting Data Collection in your subaccount, as described in the previous
chapter: Subscribe to SAP Group Reporting Data Collection Applications [page 10].

Context

To enable the transport using SAP Cloud Transport Management, you first create an instance of the SAP Group
Reporting Data Collection service and then create a service key for accessing it. These tasks are performed in
the SAP BTP cockpit:

1. Create a service.
2. If necessary, enable Cloud Foundry.
3. Create a space.
4. Create a service instance.
5. Create a service key.

Procedure

1. To create a service:

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Create a Service Instance of SAP Group Reporting Data Collection for SAP Cloud
Transport Management CONFIDENTIAL 15
 a. Ensure that you have entitled the Group Reporting Data Collection service with the transportdata plan
to your global account. This service plan is required to use SAP Cloud Transport Management.

b. In the SAP BTP Cockpit, navigate to Entitlements Subaccount Assignments and select your
subaccount from the drop-down list.
c. Select Go.
d. If there are no entries maintained for Service Group Reporting Data Collection, choose Configure
Entitlements Add Service Plans .
e. From the pop-up choose SAP Group Reporting Data Collection Service.
f. Select the service plan transportdata and click the Add 1 Service Plans button.
g. Save your changes.

Following is a screenshot of the entitlement screen on SAP BTP Cockpit:

 Note

For more information, see the "Configure Entitlements and Quotas for Subaccounts" chapter of the
SAP Business Technology Platform documentation.

2. To enable Cloud Foundry if it hasn't already been done:

a. Navigate within the SAP BTP Cockpit to the overview section of your subaccount.
b. Choose the Enable Cloud Foundry button.
c. Enter a name and click Create.
3. To create a service instance:
a. In the subaccount in which you are entitled to use the SAP Group Reporting Data Collection Service,
choose Cloud Foundry Spaces in the navigation area.
b. If you do not have a space yet, create one as described in the "Create Spaces" chapter of the SAP
Business Technology Platform documentation. Open the newly created space in which you want to
create a service instance.
c. Choose Services Service Marketplace for your space in the SAP BTP Cockpit. All available
services are displayed here.
d. Click on the SAP Group Reporting Data Collection tile.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Create a Service Instance of SAP Group Reporting Data Collection for SAP Cloud
16 CONFIDENTIAL Transport Management
 e. Choose Create.
f. Select the SAP Group Reporting Data Collection service, the transportdata plan and choose Create.

4. To create a service key to generate the credentials needed to communicate directly with the service
instance:
a. Navigate to Instances and Subscriptions, and select the service instance which has been created in the
previous step.
b. Create a Service Key from the right-hand navigation pane.
c. On the pop-up, enter a name for the service key and choose Save.

 Note

Detailed instructions to create the service keys are described in the "Create Service Keys Using the
Cockpit" chapter of the SAP Business Technology Platform documentation.

d. Once the key is created, download it to use it later.

• The uaa section contains the URL, the clientid, and the clientsecret needed to create the import
destination.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Create a Service Instance of SAP Group Reporting Data Collection for SAP Cloud
Transport Management CONFIDENTIAL 17
 • The field transport-service-v1 of the endpoints section contains the URL of the SAP Group
Reporting Data Collection import service.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Create a Service Instance of SAP Group Reporting Data Collection for SAP Cloud
18 CONFIDENTIAL Transport Management
7 Configuration and Integration

This section describes the configuration and integration required for your app.

7.1 Identity Provider

You must configure your identity provider (IdP).

SAP Cloud Identity Services is configured as the default IdP, but you can also add your instance of Identity
Authentication Service or a different IdP.

As a prerequisite, you have created business users and user groups in your IdP. You must also provide the user
groups in the assertion attribute Groups. This assertion attribute is required for the assignment of roles in the
User Account and Authentication (UAA) service. For more information, see Federation Attribute Settings of any
Identity Provider.

You must also verify that the assertion attributes email, family_name and given_name are provided.

If you use the Identity Authentication Service, you can find more information in the SAP Business
Technology Platform documentation under Manually Establish Trust and Federation Between UAA and Identity
Authentication.

You can also use your own identity provider. For more information, see Corporate Identity Providers.

7.2 Establish Your Communication Arrangement in SAP S/

4HANA Cloud

A communication arrangement needs to be activated in SAP S/4HANA Cloud for communication with web
services.

Before doing the configuration in SAP S/4HANA Cloud, you need to have the administrator business user that
contains the business catalog SAP_CORE_BC_COM (Communication Management). For example, the business
role SAP_BR_ADMINISTRATOR (Administrator).

 Note

The communication scenario used is SAP_COM_0241 (Finance - Cloud Consolidation Data Collection
Integration).

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Configuration and Integration CONFIDENTIAL 19
Related Information

Create a Technical Communication User [page 20]

Create a Communication System [page 20]
Create a Communication Arrangement [page 22]

7.2.1 Create a Technical Communication User

To create a technical communication user on your SAP S/4HANA Cloud system, you perform the following
steps:

Context

Procedure

1. Under Communication Management, choose Maintain Communication Users (F1338).

2. Choose New to create a new user (for example, GRDC_0241_COM_USER).
3. Enter a description and password for the user and choose Create.
4. Make note of the user data. You need the user data to create the communication arrangement.

Related Information

Create a Communication System [page 20]

Create a Communication Arrangement [page 22]

7.2.2 Create a Communication System

To create a communication system on your SAP S/4HANA Cloud system, you perform the following steps:

Procedure

1. Under Communication Management, choose Communication Systems (F1762).

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
20 CONFIDENTIAL Configuration and Integration
 2. Choose New to create a system.
3. Enter a system ID and a system name, and choose Create.
4. Under the Technical Data section, enter information regarding the system you wish to integrate.
5. Enter the host name.

You can determine the host name as follows:

• Open the SAP BTP Cockpit.
• Go to the subscriber/consumer account.
• Open your subaccount.
• From the General tab, select the Subdomain name and add it to this FQDN (fully qualified domain
name): [subdomain_name].grdc-sap.cfapps.[region_name].hana.ondemand.com

 Note

This fully qualified domain name equals your host name.

6. Under OAuth 2.0 Identity Provider, select the Enabled checkbox.

7. Upload the certificate file retrieved from the SAP Business Technology Platform account.
• Open the SAP BTP Cockpit.
• Go to the subscriber/consumer account.
• From the left column, choose Destination.
• Choose Download Trust.
• Upload the downloaded file in the OAuth 2.0 Identity Provider section.
• The OAuth 2.0 SAML Issuer must match the Common Name (CN) of the Signing Certificate Subject.

8. In the User for Inbound Communication section, choose the + button, enter the technical communication
user you created previously, and save.
9. In the User for Outbound Communication section, choose the + button, enter the technical communication
user you created previously, and save.

Related Information

Create a Technical Communication User [page 20]

Create a Communication Arrangement [page 22]

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Configuration and Integration CONFIDENTIAL 21
7.2.3 Create a Communication Arrangement

To create a communication arrangement on your SAP S/4HANA Cloud system, you perform the following
steps:

Procedure

1. Under Communication Management, choose Communication Arrangements (F1763).

2. Choose New, select the scenario for SAP Group Reporting Data Collection, SAP_COM_0241 Finance - Cloud
Consolidation Data Collection Integration, and choose Create.
You can adapt the arrangement name if necessary.
3. Under Common Data, select the Communications System from the input help you created previously and
verify that the technical user is entered for Inbound Communication.
4. Verify that the Authentication Method associated to this user is OAuth 2.0.
5. For Outbound Communcation, verify that the User Name corresponds to the User for Outbound
Communication you created previously at step 9 of Create a Communication System [page 20].
6. Under Outbound Services, verify that the syntax of the paths corresponds to the following:

 Tip

Don't forget to add a slash at the end of the path.

 Caution

Only the outbound services provided below require a UI link, the others can be left empty.

Description Path

UI link to the Manage Packages app /ui-scenario-manager/

UI link to the Define Ad Hoc Items app /ui-define-adhocitems/

UI link to the Manage Forms app /ui-designer/

UI link to the Enter Package Data app /ui-enter-data/

UI link to the Define Data Mapping app /ui-data-mapping/

UI link to the Run Data Mapping app /ui-run-mapping/

7. Save your changes.

Related Information

Create a Technical Communication User [page 20]

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
22 CONFIDENTIAL Configuration and Integration
Create a Communication System [page 20]

7.3 Create HTTP Destinations on SAP Business Technology

Platform

Configure destinations to allow communication between SAP S/4HANA Cloud and SAP Business Technology
Platform.

Prerequisites

Retrieve the OAuth 2.0 Details from the communication arrangement you created in the previous Create
Communication Arrangement procedure:

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Choose Communication Arrangements (F1763).
3. Open the previously created communication arrangement.
4. Under the Inbound Communication section, click on the link OAuth 2.0 Details.

 Tip

You need the displayed information to create the destination.

Procedure

1. Open the SAP BTP Cockpit.

2. Go to the subscriber/consumer account.

3. From the left column, choose Connectivity Destinations .

4. Choose Create Destination.
5. Enter S4HanaCConsoEndpoint as the name.
6. Enter the destination configuration details by providing the information in the following table and save your
changes.

 Note

Ensure the correct capitalization of the destination name S4HanaCConsoEndpoint. If the destination
S4HanaCConsoEndpoint already exists, change it to the settings given in the following table.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Configuration and Integration CONFIDENTIAL 23
 Parameter Value

Type HTTP

URL The value of SAML2 Audience as it appears in OAuth 2.0

Details

Proxy-Type Internet

Authentication OAuth2SAMLBearerAssertion

Audience The value of SAML2 Audience as it appears in OAuth 2.0

Details

AuthnContextClassRef urn:oasis:names:tc:SAML:2.0:ac:classes:X509

Client Key The value of Client ID as it appears in OAuth 2.0 Details

Token Service URL The value of Token Service URL as it appears in OAuth 2.0
Details

Token Service User Login name of communication user

Token Service Password Password of communication user

Additional Properties Choose New Property and enter the following key into the
first field (do not choose from the drop-down menu):

• sap-client
Change the value of the second field to enter the
client number of the system.

 Caution
If scope is defined as an additional property, remove
this property from the destination.

 Note

All other fields, mandatory or not, can be left empty.

 Note

When choosing Check Connection, if you receive the message "Connection to S4HanaCConsoEndpoint
established", it only indicates that the SAP S/4HANA system can be reached, not that the
configuration is correct.

 Caution

There is a cache configured on this destination service, so when you do changes, you will have to wait
for them to apply. The cache is five minutes and there is no way to clear this cache manually.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
24 CONFIDENTIAL Configuration and Integration
7.4 Automatically Update the Import Status from your SAP
S/4HANA Cloud System

When running a job, the Import Status column indicates the status reported by the SAP S/4HANA Cloud
system regarding the import (and displays errors if rows have been rejected).

Prerequisites

• You have created and configured your SAP S/4HANA Cloud destinations as described in Configure
Destinations for Scheduled Jobs [page 35].
• You have created a service instance of SAP Group Reporting Data Collection for the datamapping plan, and
a service key, as indicated in Create a Service Instance of SAP Group Reporting Data Collection for the
Datamapping Plan [page 12].

Context

To display this import status in real time, you must follow the procedure below.

 Note

If you don't follow this procedure, the import status isn't instantly updated. You must open the run and go
back to the list to see it updated.

Procedure

1. Open the SAP BTP Cockpit and navigate to your subaccount under the global account.
2. Choose Instances and Subscriptions to display the list of applications to which you have subscribed.
3. Once the service key has been created as indicated in Create a Service Instance of SAP Group Reporting
Data Collection for the Datamapping Plan [page 12], choose View to see the parameters of the keys.
From this file, you need the following parameters:
• clientid
• clientsecret
• identityzone
4. Copy the JSON code.
5. From the SAP Fiori launchpad in your SAP S/4HANA system, choose the Communication Systems tile.
6. Choose New to create a new communication system with the following properties:

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Configuration and Integration CONFIDENTIAL 25
 Parameter Value

System ID Import_Status (you can enter any value)

System Name Import_Status (you can enter any value)

Host Name Enter the following

value: grdc-api.grdc-sap.cfapps.
[region_name].hana.ondemand.com

UI Host Name Blank

Logical System Blank

Port Default

Business System Business_System_Import_Status (you can enter

any value)

7. In the Users for Inbound Communication tab, create a new user with any value.
8. In the Users for Outbound Communication tab, create a new user with the following properties:

Parameter Value

Authentication Method User Name and Password

User Name clientid value from the JSON code

Password clientsecret value from the JSON code

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
26 CONFIDENTIAL Configuration and Integration
 9. Choose Save and open the Communication Arrangements tile.
10. Choose New and create a new communication arrangement with the following properties:

Parameter Value

Scenario SAP_COM_0248 (Finance - Group Reporting Reported Fi-

nancial Data Integration)

Arrangement Name Import_Status_Comm_Arr

11. Choose Create.

12. In the Common Data section, enter the Communication System name you created at step 6.
13. Go to the Outbound Services section.
14. In the Path field, enter the following syntax: /dam/soap/v0/fincs_rptdfindatabulkin?
tenantId=<Identityzone>, where identityzone corresponds to the value indicated in the JSON
code.
For example:

/dam/soap/v0/fincs_rptdfindatabulkin?tenantId=your_customer_subaccount

 Caution

This parameter is case-sensitive.

15. Choose Save.

16. Open the SAP BTP Cockpit and navigate to your subaccount.

17. Under Connectivity Destinations , open the S4HanaCConsoEndpoint destination and choose Edit.
18. Choose New Property and enter the following values:

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Configuration and Integration CONFIDENTIAL 27
 Parameter Value

Property Name ComSysFincsCallBack

Value Same value as for the Business System you entered at

step 6 when creating a new communication system.

In our example:
Business_System_Import_Status

19. Repeat this operation for all destinations S4HanaCConsoEndpoint_XX defined for your subaccount.

7.5 Display a Link to the Task Log App in the Data Mapping
Job List or Runs

When running a job, you can display a link to the Task Log app in the job list page or in the header of the Run
page.

Context

Depending on the type of job run (manual, scheduled, or run through the Group Journal Entries -
Import API), you must add an additional property to the following destinations:

Destination Name Type of Job Run Add LaunchPadUrl Property?

S4HanaCConsoEndpoint Manual Yes

S4HanaCConsoEndpoint_API Scheduled run through the Group Yes

Journal Entries - Import API

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
28 CONFIDENTIAL Configuration and Integration
Procedure

1. From the SAP BTP Cockpit, under Connectivity Destinations , open the destination you want to
modify.
2. Choose New Property to add the LaunchPadUrl property to display a link to the Task Log app:

Additional Properties LaunchPadUrl https://

<Fiori_Launch_Pad_Address
>

 Caution

All these changes do not impact runs from the past. The link to the Task Log app will not be displayed in
past runs. You would have to run the job again.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Configuration and Integration CONFIDENTIAL 29
8 Optional Configuration

The sections linked below describe the configuration you need to perform if you want to enable specific
features.

Related Information

Enable Custom Fields for Manual Data Collection [page 30]

Enable Custom Fields for Manual Data Collection for SAP S/4HANA 2020
Enable Custom Fields for Data Mapping [page 31]
Enable Custom Fields for Data Mapping for SAP S/4HANA 2020 and higher
Configure Destinations for Remotely Stored Folders or CSV Files [page 36]
Configure Destinations for Scheduled Jobs
Display a Link to the Task Log App in the Data Mapping Job List or Runs [page 28]

8.1 Enable Custom Fields for Manual Data Collection

This topic explains how you can enable your own custom fields for the Data Collection app, in addition to the
standard fields that are provided in the ACDOCU table.

Prerequisites

You have created custom fields at the Group Reporting level, as documented in the following section: Custom
Field Extensibility.

In order for the custom fields to be available in the Data Collection app, the Business Context must be Group
Reporting Journal Entry Item. For more information, see Extensibility.

Context

For the Data Collection app, we support custom fields of data type Code List (custom field with master data)
and Association to Business Object (custom field with master data and attributes). All other data types like
Text, Date, Checkbox (custom fields with no master data) are not supported.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
30 CONFIDENTIAL Optional Configuration
  Note

If you want to add more than five attributes in a Custom Business Object, you can follow this procedure:
Adding a Value Help with the Custom CDS Views App.

Procedure

1. To enable custom fields for Manual Data Collection, you must activate the following from the Custom Fields
and Logic app:
2. From the SOAP APIs tab, select the FinancialConsolidationReportedFinancialDataBulkIn data source and
click Enable Usage.
3. From the oData APIs tab, select the API_GRTRANSACTIONDATA_SRV data source and click Enable Usage.

The custom fields are then visible in three APIs:

• API_GRTRANSACTIONDATA_SRV
• API_GRMASTERDATA_SRV
• FINCS_ALL_CHARACTERISTICS_PROP_SRV

8.2 Enable Custom Fields for Data Mapping

This topic explains how you can enable your own custom fields for Data Mapping apps, in addition to the
standard fields that are provided in the ACDOCU table.

Prerequisites

You have created custom fields at the Group Reporting level, as documented in the following section: Custom
Field Extensibility.

In order for the custom fields to be available in the Data Mapping app, the Business Context must be Group
Reporting Journal Entry Item. For more information, see Extensibility.

Context

For the Data Mapping app, we support custom fields of all data types. Code List (custom field with master
data), Association to Business Object (custom field with master data and attributes) and all other data types
like Text, Date, Checkbox (custom fields with no master data). If you want to add more than five attributes in a
Custom Business Object, you can follow this procedure: Adding a Value Help with the Custom CDS Views App.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Optional Configuration CONFIDENTIAL 31
Procedure

1. From the SAP Fiori launchpad:

a. Log on to the SAP Fiori launchpad in your SAP S/4HANA system.
b. Choose the Communication Arrangements tile.
c. Activate the communication scenario SAP_COM_0248.
2. From the SAP BTP cockpit:

a. Under Connectivity Destinations , create a new destination with the following properties:

Parameter Value

Name S4HanaCConsoEndpoint_API

Type HTTP

URL Depending on your system, endpoint

url followed by -api (same as
the token service api hostname for
S4HanaCConsoEndpoint).

Example: https://myserver-
api.s4hana.ondemand.com

Authentication BasicAuthentication

User/Password Same as the token service user for

S4HanaCConsoEndpoint.

Additional Properties sap-client Client number of your system

3. From the Custom Fields and Logic app:

 Note

When you create a custom field, the XML Namespace field is automatically populated and you
must not modify it. For example, if your namespace is YY1, the XML Namespace field is: http://
SAPCustomFields.com/YY1_.

a. Open each custom field you want to enable.

b. From the SOAP APIs tab, select the FinancialConsolidationReportedFinancialDataBulkIn data source
and click Enable Usage.
c. From the oData APIs tab, select the API_GRTRANSACTIONDATA_SRV data source and click Enable
Usage.
d. From the User Interfaces tab, select the C_CNSLDTNDATACOLLTSKLG, the
FIN_CONS_GENERICLOG_SRV and the A_CNSLDTNGRPJRNLITEM data sources and click Enable
Usage.

 Note

Enabling these UIs and reports allows you to see the custom fields in the Task Log app and in the
import logs. To see the custom fields in import logs, you must follow the procedure described in
Update Custom Fields for Data Mapping [page 33].

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
32 CONFIDENTIAL Optional Configuration
8.3 Update Custom Fields for Data Mapping

This topic explains how you can update custom fields for Data Mapping.

Context

When you add or modify custom fields in your SAP S/4HANA source system, you can use the Update Custom
Fields button in the Run Data Mapping app to update the SAP Group Reporting Data Collection metadata
accordingly, and display updated import and traceability logs after running a job.

 Restriction

This feature is available for all versions of SAP S/4HANA Cloud and for SAP S/4HANA 2021 and higher
versions.

To display the Update Custom Fields button:

Procedure

1. From the SAP BTP Cockpit, grant your user the GRDC_EXTENSIBILITY role.

Once this role added, you can see the Update Custom Fields button displayed from the Run Data Mapping
app.
2. Choose the Update Custom Fields button to display any new or modified custom fields in the import and
traceability logs.

 Note

It might take several minutes for the new custom fields to be available.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Optional Configuration CONFIDENTIAL 33
8.4 Enable SAP Controlling - Profitability Analysis (CO-PA)
Fields for Data Mapping

This topic explains how you can enable custom fields retrieved from SAP Controlling - Profitability Analysis
(CO-PA) in a data mapping definition with the ACDOCA table as source, in addition to the standard and custom
fields that are provided in the ACDOCA table.

Context

The underlying views can be identified by looking at the consumption view in ABAP Development Tools for
Eclipse.

Procedure

1. Create a package in transaction SE21.

2. Open ABAP Development Tools for Eclipse and add the package to your favorites.

 Tip

You can download the ABAP Development Tools for Eclipse from the following link: https://
www.eclipse.org/downloads/packages/release/2022-06/r .

In the following example, names that you can freely define are marked in green, and views/fields that need
to be assigned are marked in red.
3. Create an extension for E_JournalEntryItem (the extension view of the virtual data model):

a. Choose File Create ABAP Repository Object Core Data Services Data Definition and create
an extension for E_JournalEntryItem.
b. Use the Extend View template.
c. Insert the WW fields (WW fields are the CO-PA fields) you want to add to the report (in this example,
the WW field WWSBU).

 Note

Use the persistence alias as in E_JournalEntryItem to address the field of the underlying table
ACDOCA.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
34 CONFIDENTIAL Optional Configuration
 4. Create an extension for A_GLAccountLineItem (the CDS view for the API_GLACCOUNTLINEITEM API):
a. Use the Extend View template.
b. Add the name of the append view and the view to be extended.
c. Insert the WW fields that you want to add to the cube.

 Note

Use the _Extension alias that is used for E_JournalEntryItem in A_GLAccountLineItem to address
these fields.

 Note

Once this procedure performed, you can verify that the CO-PA fields are correctly retrieved in the
Define Data Mapping app by opening a template file that includes the custom fields source or by
selecting the corresponding filters in the data mapping definition.

8.5 Configure Destinations for Scheduled Jobs

When scheduling data mapping jobs, you must ensure that the corresponding SAP S/4HANA Cloud
destination is created and configured as described in this section.

Procedure

From the SAP BTP cockpit, Under Connectivity Destinations , check that the
S4HanaCConsoEndpoint_API destination is configured as follows:

Parameter Value

Name S4HanaCConsoEndpoint_API

Type HTTP

URL Depending on your system, URL fol-

lowed by -api, as displayed in the
corresponding communication arrange-
ment.

Authentication BasicAuthentication

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Optional Configuration CONFIDENTIAL 35
Parameter Value

Additional Properties sap-client Client number of your system

8.6 Configure Destinations for Remotely Stored Folders or

CSV Files

When running a data mapping job with a CSV file as source, you can now use a remote folder location to store
and read your CSV source files from. When running a data mapping job of any source type with a CSV file as
target, you can also use a remote folder location to store the CSV output files generated. And when running a
job with the traceability log activated, you can define a remote folder location to store and read your traceability
log file from.

Prerequisites

Your folder or CSV file containing the data to import must be accessible through HTTP(s) using a single URL
call.

If required, you also need to get the appropriate credentials to access this URL (basic authentication or user
token).

If you need to use a storage location that requires generated authentication token (like OneDrive or Google
Drive), you must use SAP Open Connectors to get a direct access URL with the appropriate credentials.

 Note

A dedicated license is required to use SAP Open Connectors with SAP Group Reporting Data Collection.

 Caution

Only the following connectors are supported with SAP Group Reporting Data Collection:

• Google Drive
• Microsoft OneDrive
• SharePoint

For more information on how to configure these connectors, see https://

help.openconnectors.ext.hana.ondemand.com/home/catalog.

If you want to use another connector than the ones listed above, you can create an enhancement request
following the SAP Note: 3009217 .

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
36 CONFIDENTIAL Optional Configuration
Context

To use a folder or a file stored in a remote web location, you must create a dedicated destination in the SAP
BTP Cockpit which will let the application know the remote location.

To do so, you will need to perform the following configuration:

Procedure

1. Open the SAP BTP Cockpit and go to your subaccount.

2. From the left panel, choose Connectivity Destinations .

3. Choose Create Destination.
4. Enter the name and configuration details as follows:
a. For a file as source:

Parameter Value

Type HTTP

URL CSV file URL

Proxy Type Internet

Authentication • NoAuthentication if the URL can be accessed without credentials.

• BasicAuthentication if you want to provide user and password infor-
mation, or an access token as password.

User • Username for Basic Authentication

• Not used if you want to provide an access token (you can put any
value)

Password • Enter the password for Basic Authentication

• Or the access token

Additional Properties GRDCExtRes file

TokenAsPassword • Set to true if the password

contains an access token.
• Otherwise you must remove
this property.

b. For a folder as source:

Parameter Value

Type HTTP

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Optional Configuration CONFIDENTIAL 37
 Parameter Value

URL CSV folder URL

 Note
The approved syntax is the Open Connectors one.

• The default URL for a folder is: <URL>/folders/contents?

path=%2F<FOLDER_NAME>
• The default URL for a file contained in this folder is: <URL>/files?
path=%2F<FILE_NAME>

 Caution
You can only navigate to the root of the folder specified in this URL.
If you want to create sub-folders, you need to create as many destina-
tions as there are sub-folders.

Proxy Type Internet

Authentication • NoAuthentication if the URL can be accessed without credentials.

• BasicAuthentication if you want to provide user and password infor-
mation, or an access token as password.

User • Username for Basic Authentication

• Not used if you want to provide an access token (you can put any
value)

Password • Enter the password for Basic Authentication

• Or the access token

Additional Properties GRDCExtRes folder

TokenAsPassword • Set to true if the password

contains an access token.
• Otherwise you must remove
this property.

c. For a folder as target:

Parameter Value

Type HTTP

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
38 CONFIDENTIAL Optional Configuration
 Parameter Value

URL CSV folder URL

 Note
The approved syntax is the Open Connectors one.

• The default URL for a folder is: <URL>/folders/contents?

path=%2F<FOLDER_NAME>
• The default URL for a file contained in this folder is: <URL>/files?
path=%2F<FILE_NAME>

 Caution
You can only navigate to the root of the folder specified in this URL.
If you want to create sub-folders, you need to create as many destina-
tions as there are sub-folders.

Proxy Type Internet

Authentication • NoAuthentication if the URL can be accessed without credentials.

• BasicAuthentication if you want to provide user and password infor-
mation, or an access token as password.

User • Username for Basic Authentication

• Not used if you want to provide an access token (you can put any
value)

 Note
The user must have write access to the corresponding folder.

Password • Enter the password for Basic Authentication

• Or the access token

Additional Properties GRDCExtRes folder

TokenAsPassword • Set to true if the password

contains an access token.
• Otherwise you must remove
this property.

5. Once the destination is successfully configured, you can access the Source Instance for CSV and File Name
fields from the Run Data Mapping app.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Optional Configuration CONFIDENTIAL 39
  Note

With SAP Open Connectors, the URL and the authentication token can be retrieved directly:

8.7 Add Cache Duration Parameter for Enter Package Data

The grdc-cache-duration property of the S4HanaCConsoEndpoint destination manages cache duration for the
master data of the Enter Package Data app. Its default value is set to 60 minutes.

Context

If you need to modify the master data in SAP S/4HANA and want to see the modifications reflected in the Enter
Package Data app rapidly, you can change this value to 0 minutes. However, it is recommended to keep a 60

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
40 CONFIDENTIAL Optional Configuration
minutes value if you are working in a production environment, to have better performances when using this
app.

Procedure

1. From the SAP BTP Cockpit, under Connectivity Destinations , open the S4HanaCConsoEndpoint
destination.
2. Choose New Property to add the grdc-cache-duration property to your destination.
3. Set the value in minutes.

Additional Properties grdc-cache-duration 60

8.8 Configure Destinations for ACDOCA or ACDOCU as

Source Instances
To use an SAP S/4HANA Accounting table (ACDOCA) or SAP S/4HANA Group Reporting table (ACDOCU) as
source instance for Data Mapping, you perform the following configuration.

Prerequisites

First you must activate the following specific services in your source SAP S/4HANA system:

• For ACDOCA as source instance:

SAP S/4HANA Version Web Service to be Activated

SAP S/4HANA 1809 or 1909 API_JOURNALENTRYITEMBASIC_SRV

SAP S/4HANA 2020 and higher API_GLACCOUNTLINEITEM

For any SAP S/4HANA version, if you want to activate • API_BUSINESSAREA_SRV

value help for the following fields, you must activate the
• API_CHARTOFACCOUNTS_SRV
corresponding services:
• API_PARTNERCOMPANY_SRV
• API_SEGMENT_SRV
• API_LEDGER_SRV
• API_GLACCOUNTINCHARTOFACCOUNTS_SRV
• API_COMPANYCODE_SRV

 Note

If you use an SAP S/4HANA 1809 or 1909 system with the API_JOURNALENTRYITEMBASIC_SRV API,
you may find that some fields are missing, as they are not exposed by the API. If you need them,

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Optional Configuration CONFIDENTIAL 41
 as this API supports extensibility (https://api.sap.com/api/API_JOURNALENTRYITEMBASIC_SRV/
overview ), you can add your own custom fields. For more information on creating custom fields,
see Custom Fields and Logic.

• For ACDOCU as source instance:

SAP S/4HANA Version Web Service to be Activated

SAP S/4HANA 1909 / 2020 and higher API_GRMASTERDATA_SRV

API_GRTRANSACTIONDATA_SRV

SAP S/4HANA 2022 and higher API_GRMASTERDATA_SRV

API_CNSLDTNGRPJRNLITEM

For more information, see SAP Note 3423097 .

 Note

For more information on how to activate these services, see Activate OData Services V2.

Context

To use the ACDOCA or ACDOCU table as a source instance, you must then create a dedicated destination in the
SAP BTP Cockpit which will let the application know the location of the SAP S/4HANA system of the ACDOCA
or ACDOCU table you want to use.

To do so, you will need to perform the following configuration:

Procedure

1. Open the SAP BTP Cockpit and go to your subaccount.

2. Under Connectivity Destinations , choose Destinations.

3. Open the existing standard destination S4HanaCConsoEndpoint or choose Create Destination if you want
to retrieve data from another external system.
4. Add the name and configuration details, depending on your SAP S/4HANA system.

Parameter Value

Type HTTP

URL URL of your SAP S/4HANA system

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
42 CONFIDENTIAL Optional Configuration
 Parameter Value

Authentication Depending on the following:

• If you want to schedule jobs, you must set this parameter to
BasicAuthentication.
• Otherwise choose the appropriate authentication type, depending on the
SAP S/4HANA system you use.

Additional Properties sap-client Client number of your

system

GRDCExtRes ACDOCA ACDOCU

For SAP S/4HANA

2022 and higher only:
API_CNSLDTNGRPJRNLITEM. For
more information, see SAP Note
3423097

 Note

You can use the same destination for both ACDOCA or ACDOCU tables by adding the value ACDOCA
ACDOCU to the GRDCExtRes Additional Property.

 Note

The other parameters of the destination must be configured according to the SAP S/4HANA system
you use.

8.9 Configure Destinations for SAP ECC as Source Instance

To use an SAP ECC system as a source instance, you must create dedicated destinations in the SAP BTP
Cockpit, which will let the application know the location of the SAP ECC system you want to use.

 Note

You must implement the SAP note 3144499 before you start using an SAP ECC system as source
instance.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Optional Configuration CONFIDENTIAL 43
8.9.1 Configure the Cloud Connector for SAP ECC as Source

Use the cloud connector to establish a secure connection between the SAP Business Technology Platform,
SAP Group Reporting Data Collection, and your on-premise landscape.

Prerequisites

You must complete the following steps:

• Configure principal propagation to an ABAP system for RFC using an SNC (Secure Network
Communications) connection. For more information, see Configure Principal Propagation to an ABAP
System for RFC.
For more information about activities required to authenticate users against on-premise systems, see
Authenticating Users against On-Premise Systems.
• Link the cloud connector with your SAP BTP subaccount. To do so, you must log on to the Cloud Connector
and add a subaccount with the information for your subaccount.

Context

The SAP Connectivity service includes a cloud connector that is a content-agnostic technology to connect
on-premise systems to cloud systems and takes the place of a reverse proxy in an architecture.

Procedure

1. Log on to the Cloud Connector.

2. Go to the Cloud To On-Premise tab for your subaccount.
3. Go to the Access Control tab.
4. Map the RFC in the SAP ECC backend.
a. Add Mapping Virtual To Internal System and enter the following:

Parameter Value

Backend-type ABAP System

Protocol RFC

Application Server Host for the SAP ECC backend services

Instance Number Instance number of the SAP ECC backend

Virtual Application Server Enter any value.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
44 CONFIDENTIAL Optional Configuration
 Parameter Value

 Note
Remember your entry as you need it to configure
the destination in your SAP BTP subaccount.

Virtual Instance Number Enter any numerical value.

 Note
Remember your entry as you need it to configure
the destination in your SAP BTP subaccount.

Principal Type X.509 Certificate (General Usage)

b. Select the mapping you just created and add Resources.

Parameter Value

Function Name FC

Naming Policy Prefix

c. Add Resources.

Parameter Value

Function Name FIN

Naming Policy Prefix

d. Add Resources.

Parameter Value

Function Name BAPI

Naming Policy Prefix

8.9.2 Create Destinations for SAP ECC as Source

Create destinations to allow communication between SAP ECC and SAP Business Technology Platform.

Context

You must create and configure a destination in order to communicate with the SAP ECC system through RFC.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Optional Configuration CONFIDENTIAL 45
Procedure

1. Log on and open the SAP BTP Cockpit.

2. Go to the subscriber/consumer account.

3. Under Connectivity Destinations , choose Create Destination.

4. Enter the name and configuration details for the RFC destination as follows:

Parameter Value

Name Same name as the Virtual Host name you created at step 4 of the previous
step, "Map the RFC in the SAP ECC backend": Configure the Cloud Connector
for SAP ECC as Source [page 44] with _RFC added at the end. For example:
YourECCDestinationName_RFC

Type RFC

Repository User Technical user with required access

Additional Properties jco.client.ashost <host as defined in Cloud Connector>

jco.client.client Client number in SAP ECC

jco.client.sysnr <instance number as defined in Cloud

Connector>

jco.client.trace 1

jco.destination.grdcextres ECC

jco.destination.auth_type PrincipalPropagation

 Caution

If you have chosen to create a technical user and set its authentication to BasicAuthentication, then
this user must be granted the appropriate global parameters.

5. If you want to use your own BAPI that allows you to select multiple company codes, you must add the
RE_T_BUKRS associated type to the COMPANYCODE parameter.

 Caution

The Import/Export parameters in your BAPI must comply with the ones defined in the standard BAPI
"BAPI_SL_GETTOTALRECORDS".

6. Then add the BAPI name [BAPI_NAME] to the jco.destination.multi-company-code-bapi additional

property of your destination:

Parameter Value

Additional Properties jco.destination.multi-company-code- [BAPI_NAME]

bapi

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
46 CONFIDENTIAL Optional Configuration
8.10 Configure Destinations for OData Custom Connections
as Source Instances for Data Mapping

Configure a dedicated destination to use an OData service as source instance for Data Mapping.

Prerequisites

To use an OData Custom Connection as your source instance, the service must be active and accessible. The
authentication between the service and the SAP Business Technology Platform must be configured with the
appropriate authorizations.

SAP Group Reporting Data Collection supports the OData V2 and V4.

The OData service you are using may contain multiple entity sets. However, the data is retrieved exclusively
through the single entity set configured in your destination.

For OData V2, the main OData query options used are the following:

• $top
• $skip
• $select
• $filter
• $metadata

 Note

For OData V2, it is recommended that you use the sap:aggregation-role attribute to distinguish
between dimensions, measures and technical properties.

Example:

<Property Name="CostCenter" Type="Edm.String" MaxLength="10" sap:aggregation-

role="dimension" sap:display-format="UpperCase" sap:text="CostCenter_Text"
sap:label="Cost Center"/>

For OData V4, the main OData query options used are the following:

• $top
• $skip
• $metadata
• $apply

For ODATA V4, the following annotations are supported:

• Common.Label: free text containing the description of the entity set property. This annotation is optional.
• Analytics.AnalyticalContextType
Two types supported:
• Dimension
• Measure

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Optional Configuration CONFIDENTIAL 47
  Note

This annotation is mandatory, only properties with this annotation and these two types
Dimension or Measure are displayed in data mapping apps.

 Note

For performance reasons, the OData service you are using must implement an aggregation mechanism for
the relevant fields in order to optimize the payload size (volume of the data generated for upload) and the
import process.

Procedure

1. Open the SAP BTP Cockpit and go to your subaccount.

2. Under Connectivity Destinations , choose Create Destination.

3. Enter the name and configuration details as follows:

 Note

Below is an example with the ACDOCP OData V2 service as source.

Parameter Value

Type HTTP

URL URL of your system

Proxy Type Internet

Authentication Depending on your system

User User name of the communication user

Password Password of the communication user

Additional Properties oDataEntitySet A_FinPlanningEntryItem

oDataServiceName sap/opu/odata/sap/
API_FINPLANNINGENTRYITEM_
SRV

SAP-client Client number of the

system

 Note

Below is an example with the GHG OData V4 service as source.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
48 CONFIDENTIAL Optional Configuration
 Parameter Value

Type HTTP

URL URL of your system

Proxy Type Internet

Authentication OAuth2ClientCredentials

Client ID

Client Secret

Additional Properties oDataEntitySet JournalEntryEmissions

oDataServiceName api/grl-postings-
srv/v1/api/
JournalEntryExtractionSer
vice

8.11 Enable Custom Themes Using UI Theme Designer

You can create your own custom themes by modifying SAP standard themes, and use them to adapt the visual
appearance of your SAPUI5 applications to match your company's brand.

Themes are created in a browser-based tool called the UI theme designer. It has a WYSIWYG designer to make
it easy to create and maintain custom themes. By simply changing theme parameter values, images, and other
resources, you can create your own themes with your corporate brand, corporate colors, and company logo.

For more information, see the documentation for UI Theme Designer on the SAP Help Portal, in the following
section: Launching UI Theme Designer from SAP Fiori Launchpad Configuration Cockpit on Cloud Foundry.

 Note

Custom themes available in SAP BTP are not the same as the ones available in SAP S/4HANA (or any other
application).

Prerequisites

To enable users to work with the UI theme designer, you must assign the Theme_Admin role to the user's role.

Ensure that the required role collections have been configured and assigned to the users as indicated in the
UI Theme Designer documentation under What is UI Theme Designer Initial Setup of UI Theme Designer
Developer PaaS Scenario Setting up Permissions for the UI Theme Designer .

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Optional Configuration CONFIDENTIAL 49
Procedure

To learn how to design themes with the UI Theme Designer, see the documentation for UI Theme Designer
under UI Theme Designer for the Cloud Foundry Environment Create Themes — End to End Flow .

 Caution

A set of default themes is provided for SAP Group Reporting Data Collection. To avoid display issues, we
recommend that you don't enable other SAP standard themes.

8.12 Configure Destinations for Notifications

This section explains how to configure your destination in the SAP BTP Cockpit to allow users to receive
notifications in the SAP Fiori Launchpad or by email, about data mapping job runs.

Prerequisites

You must first configure the ComSysFincsCallBack property so that the import status from your SAP S/
4HANA system is instantly updated. For more information, see Automatically Update the Import Status from
your SAP S/4HANA Cloud System [page 25] and Automatically Update the Import Status from your SAP
S/4HANA System.

You must also verify that the assertion attributes email, family_name and given_name are correctly configured
in your identity provider (IdP).

Procedure

1. Assign the SAP_GRDC_RDM_SET_NOTIFY_USERS role to the Data Mapping user who will configure
notifications from within the Run Data Mapping app.
2. Open the SAP BTP Cockpit.
3. Go to the subscriber/consumer account.

4. From the left column, choose Connectivity Destinations .

5. Choose Create Destination.
6. Enter SAP_Business_Notifications_Mail as the name.

 Note

Ensure the correct capitalization of the destination name SAP_Business_Notifications_Mail.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
50 CONFIDENTIAL Optional Configuration
  Caution

You can't choose any other destination name.

7. Enter the destination configuration details by providing the information in the following table and save your
changes.

Parameter Value

Type MAIL

Proxy-Type Internet

Authentication BasicAuthentication

User User account's email address used to connect to the SMTP server for sending
email notifications

Password Password of user account's email address used to connect to the SMTP server
for sending email notifications

Additional Properties mail.smtp.from Email of sender

mail.smtp.host Smtp server adress (example: smtp-

mail.outlook.com)

mail.smtp.port Port number of your stmp server

 Caution

There is a cache configured on this destination service, so when you do changes, you will have to wait
for them to take effect. The cache is configured for five minutes and there is no way to clear this cache
manually.

 Note

Notifications can't be sent to distribution lists.

Results

Open the Run Data Mapping app to further configure email notifications.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Optional Configuration CONFIDENTIAL 51
9 User Management

This section describes how to configure user management for your application. As a prerequisite, you have
created business users and user groups in your identity provider (IdP). SAP ID service is configured as the
default IdP, but you can also add your instance of SAP Cloud Identity Services - Identity Authentication or a
different IdP.

For more information, see Identity Provider [page 19].

 Tip

If you use principal propagation, you must inform your users that they must set their global parameters
before connecting to SAP Group Reporting Data Collection.

If you use the Identity Authentication service, you can find more information in the SAP BTP documentation
under Manually Establish Trust and Federation Between UAA and Identity Authentication.

9.1 Define and Bundle Roles on SAP Business Technology

Platform

SAP Group Reporting Data Collection provides the following roles that you must assign to users or groups.

 Note

As a prerequisite for assigning roles to IdP users or user groups, you also need to configure role collections.
A role collection consists of one or more roles from one or more applications and can be used to bundle
authorizations within and across applications.

For more information on how to assign a role collection to a user group, see Map Role Collections to User
Groups.

For more information about how to create roles and how to bundle them in role collections using the SAP
BTP cockpit, see Building Roles and Role Collections for Applications.

 Note

Any role not listed below has no impact on user rights and can be ignored.

App Role Description

Manage Packages SAP_BCR_FIN_CCON_GRDC_SCM_P Access Manage Packages

C

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
52 CONFIDENTIAL User Management
 App Role Description

Define Ad Hoc Items SAP_BCR_FIN_CCON_GRDC_MAHI_ Access Manage Ad Hoc Items

PC

Manage Forms SAP_BCR_FIN_CCON_GRDC_DFR_P Access Manage Forms

C
Access the comments, questions and an-
SAP_BCR_FIN_CCON_CQA_PC swers functionality from the Manage Forms
app.

Enter Package Data SAP_BCR_FIN_CCON_GRDC_ERD_P Access Enter Package Data

C
Access the comments, questions and an-
SAP_BCR_FIN_CCON_CQA_PC swers functionality from the Enter Package
Data app.

Define Data Mapping

SAP_GRDC_DDM_READ Access mapping definitions in read-only

mode, with no rights to download the map-
ping file.

SAP_GRDC_DDM_WRITE Create, delete and edit mapping definitions,

with no rights to overwrite a mapping file.

When creating a mapping definition, the

user is allowed to upload a mapping file.

For existing mapping definitions, the user

isn't allowed to upload a new mapping file.

SAP_GRDC_DDM_EDIT_RESTRIC- Access in read-only mode the complete list

TIONS of mapping definitions and edit the defini-
tion access restrictions.

This role allows a user to see and modify

the access restrictions of all definitions,
independently of any access restrictions
changes.

For more information on access restric-

tions, see Define Access Restrictions.

SAP_GRDC_DDM_DOWNLOAD_MAP- Access mapping definitions in read-only

mode,with the right to download the map-
PING _FILE
ping file.

SAP_GRDC_DDM_UPLOAD_MAP- Edit a mapping definition with the right to

upload a mapping file but with no rights to
PING _FILE
modify or delete the definition.

Run Data Mapping

SAP_GRDC_RDM_READ Access jobs in read-only mode.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
User Management CONFIDENTIAL 53
App Role Description

SAP_GRDC_RDM_WRITE Create, delete and edit jobs with no rights

to run them.

SAP_GRDC_RDM_RUN Run a job in test mode without importing

data (test mode or import into a CSV file).

SAP_GRDC_RDM_RUN_IMPORT Run a job and import data only.

SAP_GRDC_RDM_ENABLE_TL Generate a traceability log.

 Note
This right can't be assigned
alone, you must also add
the SAP_GRDC_RDM_RUN_TEST
right and / or SAP_GRDC_RDM_ENA-
BLE_TL right.

SAP_GRDC_RDM_DOWNLOAD_TL Download a traceability log.

SAP_GRDC_RDM_RUN_DWNLD_CSV Download the CSV file when running a job

with CSV file as target.

SAP_GRDC_RDM_SET_NO- Activate email notifications.

TIFY_USERS

GRDC_EXTENSIBILITY Access the Update Custom Fields button.

SAP Cloud Transport Management GRDC_TMS_EXPORT Access the SAP Cloud Transport Manage-
Service ment service.

For more information, see SAP Cloud Trans-

port Management Service Implementation
[page 57].

Export Comments, Questions and An- GRDC_CQA_EXPORT Access the Export Comments, Questions
swers Data API and Answers Data API.

For more information, see Export Com-

ments, Questions, and Answers Data [page
82].

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
54 CONFIDENTIAL User Management
9.2 Add Business Catalogs to Business Users in SAP S/
4HANA Cloud

Business users in the SAP S/4HANA Cloud system, who need access to the respective SaaS application, must
have the relevant business catalogs assigned to them using the corresponding business role.

Context

 Note

Ensure that the value of the User Name field for all business users you want to use for a scenario in SAP
S/4HANA Cloud is the same as the Login Name field of the corresponding user master data in your SAP
Cloud identity tenant.

The user name of a business user is independent from the user name of a communication user.

Procedure

1. Log on to the SAP Fiori launchpad.

2. Choose the Maintain Business Users tile (F1303).
3. Select the business user you want to assign to the business role.

4. Choose Edit Add Business Roles , and select the corresponding business role. If necessary, you can
use the Search field in the upper right of the view. Ensure that this business role contains the correct
business catalog for your needs.

The table below outlines the business catalogs required according to the SAP Group Reporting Data
Collection module that your user will use:

SAP Group Reporting Data Collection

module Required Business Catalog Embedded SAP Business Role (*)

Manage Packages Group Reporting Data Collection – Administrator – Group Reporting

Manage Packages
SAP_BR_ADMINISTRATOR_GRP
SAP_FIN_BC_CCON_GRDC_SCM_PC

Manage Forms Group Reporting Data Collection – Administrator – Group Reporting

Define Forms
SAP_BR_ADMINISTRATOR_GRP
SAP_FIN_BC_CCON_GRDC_DFR_PC

Enter Package Data Group Reporting Data Collection – General Ledger Accountant – Group
Enter Data Reporting

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
User Management CONFIDENTIAL 55
 SAP Group Reporting Data Collection
module Required Business Catalog Embedded SAP Business Role (*)

SAP_FIN_BC_CCON_GRDC_ERD_PC SAP_BR_GL_ACCOUNTANT_GRP

Consolidation – Read only Apps

SAP_FIN_BC_CCON_READ_PC

Define Data Mapping Group Reporting Data Collection – Administrator – Group Reporting
Define Data Mapping
SAP_BR_ADMINISTRATOR_GRP
SAP_FIN_BC_CCON_GRDC_DDM_PC
Cost Accountant - Overhead
Overhead Cost Accounting - Cost
SAP_BR_OVERHEAD_ACCOUNTANT
Center Master Data

SAP_FIN_BC_OH_MD_CCA_PC

 Note
This business catalog is only
required if you want to add Profit
Center as a source filter in an
ACDOCA mapping definition.

Run Data Mapping Group Reporting Data Collection - General Ledger Accountant - Group
Run Data Mapping Reporting

SAP_FIN_BC_CCON_GRDC_RDM_PC SAP_BR_GL_ACCOUNTANT_GRP

Define Ad Hoc Items Group Reporting Data Collection - Administrator - Group Reporting
Define Ad Hoc Items
SAP_BR_ADMINISTRATOR_GRP
SAP_FIN_BC_CCON_GRDC_MAHI_P
C

(*) These business roles are provided by SAP. Their usage is not mandatory, you can create your own role
with the business catalogs outlined in the table above.

5. Choose OK.

The business role is displayed in the table under Assigned Business Roles.
6. Save your changes.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
56 CONFIDENTIAL User Management
10 SAP Cloud Transport Management
Service Implementation

The SAP Cloud Transport Management service lets you transport objects between different subaccounts of
SAP Group Reporting Data Collection.

The SAP Cloud Transport Management Service allows you to transport forms and folders (not predefined
content), as well as data mapping definitions and jobs, from within SAP Group Reporting Data Collections apps
located in different subaccounts, for example from a TEST to a PROD system.

 Note

A dedicated license is required to use SAP Cloud Transport Management with SAP Group Reporting Data
Collection.

 Note

The configuration steps given below are valid for an environment where you have a common global account
for both SAP Group Reporting Data Collection and the SAP Cloud Transport Management Service. If your
SAP Cloud Transport Management Service entitlement is managed in a different subaccount, steps 1 to 4
and 8 are done in this subaccount. The remaining steps must be configured as described in the source and
target subaccounts. For more information, see the SAP Cloud Transport Management documentation.

The following graphic outlines the steps required to implement the SAP Cloud Transport Management Service:

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
SAP Cloud Transport Management Service Implementation CONFIDENTIAL 57
• #unique_42/unique_42_Connect_42_subsection-im1 [page 58]
• #unique_42/unique_42_Connect_42_subsection-im2 [page 58]
• #unique_42/unique_42_Connect_42_subsection-im3 [page 58]
• #unique_42/unique_42_Connect_42_subsection-im4 [page 58]
• #unique_42/unique_42_Connect_42_subsection-im5 [page 58]
• #unique_42/unique_42_Connect_42_subsection-im6 [page 59]
• #unique_42/unique_42_Connect_42_subsection-im7 [page 59]
• #unique_42/unique_42_Connect_42_subsection-im8 [page 59]
• #unique_42/unique_42_Connect_42_subsection-im9 [page 60]

Hover over each step for a description. Click the step for more information.

Step 1: Add the Cloud Transport Management entitlement and plans to your source subaccount.

1. Select your source subaccount and choose Entitlements Configure Entitlements Add Service
Plans .
2. In the list of entitlements, search for Cloud Transport Management, select both the available standard plans
and click Add Service Plan.
3. Once back on the Entitlements page, choose Save.

Step 2: Subscribe to the Cloud Transport Management application.

Subscribe to the Cloud Transport Management application as described in the following chapter of the
SAP Cloud Transport Management documentation: Steps to Use the User Interface of Cloud Transport
Management.

Step 3: Assign user roles and permissions in Cloud Transport Management.

This procedure is described in the following chapter of the SAP Cloud Transport Management documentation:
Steps to Assign User Roles and Permissions in Cloud Transport Management.

Step 4: Create a service instance of Cloud Transport Management and the corresponding service key.
Download the service key for later use.

Create a service instance of Cloud Transport Management and the corresponding service key, that you must
download for later use. This procedure is described in the following chapter of the SAP Cloud Transport
Management documentation: Creating a Service Instance and a Service Key.

Step 5: Assign the GRDC_TMS_EXPORT role to the user who will run the export.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
58 CONFIDENTIAL SAP Cloud Transport Management Service Implementation
For more information, see Map Role Collections to User Groups.

Step 6: Create a service instance of SAP Group Reporting Data Collection (transportdata plan) and a
service key for accessing it. Download the service key for later use.

Open the target subaccount and follow the procedure described here: Create a Service Instance of SAP Group
Reporting Data Collection for SAP Cloud Transport Management [page 15].

 Note

You can use the same space for both transportdata and datamapping service plans.

Step 7: Create the target destination to specify where to transport content to.

Open your source subaccount and create a destination to specify where to transport content to.

 Note

The parameters to enter in the URL, Client ID, Client Secret and Token Service URL fields are the ones that
have been generated at step 6.

Name CTMS_TARGET_SYSTEM

Type HTTP

URL Endpoint from service key generated at step 6

https://grdc-transport.../.com/
rest/v1/tms

Proxy Type Internet

Authentification OAuth2ClientCredentials

Client ID Client ID from service key generated at step 6

sb-xxx|grdc-broker-xxx

Client Secret Secret ID from service key generated at step 6

Token Service URL Type Dedicated

Token Service URL URL from service key generated at step 6

https://
your_target_subaccount.authentication...

Step 8: Create a source transport node and a target transport node, then create the transport route
between these two transport nodes

From the source subaccount, open the SAP Cloud Transport Management application and do the following:

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
SAP Cloud Transport Management Service Implementation CONFIDENTIAL 59
1. Open the Transport Nodes, and create a new source transport node with the following properties:
• Name: enter a name of your choice
• Allow Upload to Node: checked
2. Create the target transport node, with the following properties:
• Name: enter a name of your choice
• Allow Upload to Node: not checked
• Forward Mode: Auto
• Content Type: Application Content
• Destination: select the destination you created at step 7: CTMS_TARGET_SYTEM.
3. Create the transport route between the two transport nodes, as described in Create Transport Routes.

Step 9: Create the Cloud Transport Management destination to specify where to transport content to.

Open your source subaccount and create a destination named GRDC_TMS_EXPORT_BACKEND to specify
where to transport content to. This destination contains the following properties, which can be found in the
service key generated at step 4:

Name GRDC_TMS_EXPORT_BACKEND

Type HTTP

URL URI from service key generated at step

4

https://transport-service-
app-backend...

Proxy Type Internet

Authentification OAuth2ClientCredentials

Client ID Client ID from service key generated at

step 4

sb-xxx|alm-ts-backend-xxx

Client Secret Client Secret from service key gener-

ated at step 4

Token Service URL Type Dedicated

Token Service URL <URL from service key generated at

step 4>/oauth/token

https://
your_source_subaccount.aut
hentication…/oauth/token

Additional Properties source-node-name Transport node created at step 8.1

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
60 CONFIDENTIAL SAP Cloud Transport Management Service Implementation
11 Group Journal Entries - Import API

The Group Journal Entries – Import API (Technical name: API_CnsldtnGrpJrnlEntr_Imprt) allows you to
import data from any external system to the ACDOCU table of SAP S/4HANA Finance for Group Reporting,
through the Data Mapping service.

Prerequisites

You have created a service instance of SAP Group Reporting Data Collection for the datamapping plan, and
a service key, as indicated in Create a Service Instance of SAP Group Reporting Data Collection for the
Datamapping Plan [page 12].

Procedure

1. Open the SAP BTP Cockpit and navigate to your subaccount under the global account.
2. Choose Instances and Subscriptions to display the list of applications to which you have subscribed.
3. Once the service key has been created as indicated in Create a Service Instance of SAP Group Reporting
Data Collection for the Datamapping Plan [page 12], choose View to see the parameters of the keys.

• The uaa section contains the URL, the clientid, and the clientsecret needed to create an access token
for calling APIs.
• The field datamapping-service-v1 of the endpoints section contains the URL of the SAP Group
Reporting Data Collection service API.
4. Create a JSON Web Token (JWT) that allows you to call the API, using the oauth client credentials flow:
a. You must adapt the URL to match the following pattern: <url_returned_from_service_keys>/
oauth/token.
b. You need to define the following message body in the POST call:

Key Value

client_id <clientid_returned_from_service_keys>

client_secret <clientsecret_returned_from_service_keys>

grant_type client_credentials

The JSON Web token for API access is included in the response body.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Group Journal Entries - Import API CONFIDENTIAL 61
  Note

The information contained in the "access_token" value is the one that you must use in
the Authorization header of all subsequent requests with the following format: Bearer
[value_of_access_token].

In the context of the creation of the oauth client credentials flow as indicated in Create a Service
Instance of SAP Group Reporting Data Collection for the Datamapping Plan [page 12], you must create
a new destination from the SAP BTP Cockpit with the following properties:

5. In the context of the creation of the oauth client credentials flow as indicated in Create a Service Instance
of SAP Group Reporting Data Collection for the Datamapping Plan [page 12], you must create a new
destination from the SAP BTP Cockpit with the following properties:

Parameter Value

Name S4HanaCConsoEndpoint_API

Type HTTPS

URL Depending on your system, URL followed by -api, as displayed in the corre-
sponding communication arrangement.

Authentication BasicAuthentication

Additional Properties sap-client Client number of your system

Results

You can now create a mapping definition and, if necessary, a job, from within the Define Data Mapping or Run
Data Mapping apps. The API lets you specify the definition or job to use and pushes the data to be mapped and
sent to the backend.

You have two options:

• First, you can select a mapping definition from existing CSV-based mapping definitions, which then creates
and runs the corresponding job.
• Alternatively, you can select a job from existing CSV-based jobs and run it.

11.1 List Mapping Definitions

API_CnsldtnGrpJrnlEntr_Imprt/CnsldtnGrpJrnlEntrMapping (read)

This API retrieves the list of valid mapping definitions based on CSV files, in read-only mode.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
62 CONFIDENTIAL Group Journal Entries - Import API
 Request Parameters Required Data Type Description

name yes string Name of the definition.

description yes string Provides more details about a mapping definition.

Name of the CSV file on which the mapping defini-

mappingFileName yes string
tion is based.

 Sample Code

GET
{
"results": [
{
"ID": "4c5c0952-518c-452b-a293-e2508614deb7",
"name": "BasicMapping",
"description": "Description of Mapping_basic.xlsx",
"mappingFileName": "Mapping_basic.xlsx",
"status": true,
"sourceType": "CSV",
}
]
}

11.2 List Mapping Jobs

API_CnsldtnGrpJrnlEntr_Imprt/CnsldtnGrpJrnlEntrJob (read)

This API retrieves the list of mapping jobs based on valid CSV mapping definition files, in read-only mode.

Parameter Required Data Type Description

name yes string Name of the job.

description yes string Provides more details about a mapping job.

Name of the mapping definition on which the job is

mappingFileName yes string
based.

 Sample Code

GET
{
"results": [
{
"ID": "0d5b538a-b2da-45f1-a700-e260672acfef",
"name": "BasicJob",
"description": "Mapping job created for API",
"destination": "S4HanaCConsoEndpoint",
"mappingDefinition_name": "BasicMapping",
"mappingDefinition_type": "CSV",
}
]

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Group Journal Entries - Import API CONFIDENTIAL 63
 }

11.3 Start Running a Definition

API_CnsldtnGrpJrnlEntr_Imprt/StartCnsldtnGrpJrnlEntrMappg (action)

This API:

1. Creates a job based on the definition. Starts a new empty run for the created job and returns its identifier.
2. Checks that the mapping definition exist and is valid, and check that the provided input columns
correspond to the data mapping definition input columns.
3. Creates a job based on the provided Mapping Definition with the input parameters below.
4. Creates a new run and makes it wait for the data (provide a timeout to cancel waiting if no data is coming).
5. Returns the new created run identifier.

Request Parameter Required Data Type Description

mappingDefiniti yes string Name of the mapping definition

onName

yes string Headers of input columns

dataHeader
'colName1,colName2,colName3'

actionAfterMapp yes integer Either the result is automatically sent to the back-
ing end or staged on SCP (in the SAP HANA Database
table)

The values are: send=0, stage=1, both=2

optional integer Period in days during which the mapped data will
dataRetentionPe
be staged, after this period data will be deleted.
riod
The default value is one week, the maximun is 30
days.

optional string Options to choose when uploading data. The val-

updateMode
ues are:

• delete-all
• overwrite

The defaut value is delete-all.

For more information, see Import Options.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
64 CONFIDENTIAL Group Journal Entries - Import API
 Request Parameter Required Data Type Description

optional string Options to choose when uploading data. The val-

periodicMode
ues are:

• periodic
• Year-to-date

The defaut value is periodic.

For more information, see Import Options.

sourceDocType optional string Provides the list of document types with a comma
as separator. This parameter allows you to select
the different document types that you want to con-
sider for calculating the delta between the value
provided in the source data and the data which
already exist in the system. For more information,
see Import Options.

destinationDocT optional string This parameter allows you to select the document
ype type on which you want to import data. By default,
if the parameter is left empty, then it's the docu-
ment type associated to the destination that is
used. For more information, see Import Options.

Global parameters of your environment

consolidationLe Only for SAP S/ string
dger 4HANA 1909

Global parameters of your environment

consolidationVe yes string
rsion

Global parameters of your environment

consolidationCh yes string
artOfAccounts

yes string Global parameters of your environment

fiscalYear

yes string Global parameters of your environment

fiscalPeriod

optional boolean This parameter allows you to perform a test run,

isTestMode
and ckeck for errors in the import and traceability
logs, without sending any data to the ACDOCU ta-
ble.

This parameter allows you to specify the name of

traceabilityLog optional string
the destination when generating a traceability log
Destination when a job is run.

 Note

You must add the parameter values to a query string. If the resulting URL is too large, you must use a batch
request. For more information, see Create a Batch Request [page 75].

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Group Journal Entries - Import API CONFIDENTIAL 65
Response Parame-
ters Required Data Type Description

runId yes string Returns the new created run identifier.

 Sample Code

POST
https://grdc-api.grdc-sap.cfapps.[region_name].hana.ondemand.com/odata/v2/
API_CnsldtnGrpJrnlEntr_Imprt/StartCnsldtnGrpJrnlEntrMappg?
mappingDefinitionName='{{definitionName}}'&dataHeader='I_FSItem,I_SubItem,I_Am
ount'&actionAfterMapping=1&dataRetentionPeriod=1&consolidationLedger='Y1'&cons
olidationVersion='Y10'&consolidationChartOfAccounts='Y1'&fiscalYear='2011'&fis
calPeriod='013'&traceabilityLogDestination='mydestinationname'

response
{
"runId" : "fd617deb-075a-41e0-a4d4-ba67d50b2426"
}

11.4 Start Running a Job

API_CnsldtnGrpJrnlEntr_Imprt/StartCnsldtnGrpJrnlEntrJob (action)

This API:

1. Starts a new empty run for the selected jobs with the request parameters below, and sets a validity period
for the run.

 Note

This value is set to 10 minutes. After 10 minutes of inactivity, the run status is "Expired".

2. Returns the new created run identifier.

Request Parameters Required Data Type Description

mappingJobName yes string Name of the job

yes string Headers of input columns

dataHeader
'colName1,colName2,colName3'

actionAfterMapp yes integer Either the result is automatically sent to the back-
ing end or staged on SAP BTP (in the SAP HANA Data-
base table)

The values are: send=0, stage=1, both=2

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
66 CONFIDENTIAL Group Journal Entries - Import API
 Request Parameters Required Data Type Description

optional integer Period in days during which the mapped data will
dataRetentionPe
be staged. After this period, data will be deleted.
riod
The default value is one week, the maximun is 30
days.

Global parameters of your environment

consolidationLe Only for SAP S/ string
dger 4HANA 1909

Global parameters of your environment

consolidationVe yes string
rsion

Global parameters of your environment

consolidationCh yes string
artOfAccounts

yes string Global parameters of your environment

fiscalYear

yes string Global parameters of your environment

fiscalPeriod

optional boolean This parameter allows you to perform a test run,

isTestMode
and ckeck for errors in the import and traceability
logs, without sending any data to the ACDOCU ta-
ble.

This parameter allows you to generate a traceabil-

generateTraceab optional boolean
ity log when a job is run.
ilityLog

 Note

You must add the parameter values to a query string. If the resulting URL is too large, you must use a batch
request. For more information, see Create a Batch Request [page 75].

Response Parame-
ters Required Data Type Description

runId yes string Returns the new run identifier.

 Sample Code

POST
https://grdc-api.grdc-sap.cfapps.[region_name].hana.ondemand.com/odata/v2/
API_CnsldtnGrpJrnlEntr_Imprt/StartCnsldtnGrpJrnlEntrJob?
mappingJobName='{{jobName}}'&dataHeader='I_FSItem,I_SubItem,I_Amount'&actionAf
terMapping=1&dataRetentionPeriod=1&consolidationLedger='Y1'&consolidationVersi
on='Y10'&consolidationChartOfAccounts='Y1'&fiscalYear='2011'&fiscalPeriod='013
'&generateTraceabilityLog='true'

response
{
"runId" : "fd617deb-075a-41e0-a4d4-ba67d50b2426"
}

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Group Journal Entries - Import API CONFIDENTIAL 67
11.5 Process Data
API_CnsldtnGrpJrnlEntr_Imprt/ProcessCnsldtnGrpJrnlEntrJob (action)

This API:

1. Processes input date for the selected run using the parameters below.
2. Then it saves the logs, and also renews the validity period for the run.
3. The received data will be processed in the run.

 Note

The call is asynchronous and the data is processed like a regular run.

Request Parameters Required Data Type Description

runId yes string

yes string Headers of input columns: must use the same sep-
dataHeader
arator as the one used in the mapping definition.

yes string CSV file content: must use the same separator as
data
the one used in the mapping definition. To upload
multiple lines with a single request, you must sepa-
rate them with the characters “%0A” (correspond-
ing to the line feed character).

 Note

You must add the parameter values to a query string. If the resulting URL is too large, you must use a batch
request. For more information, see Create a Batch Request [page 75].

 Sample Code

POST
https://grdc-api.grdc-sap.cfapps.[region_name].hana.ondemand.com/odata/v2/
API_CnsldtnGrpJrnlEntr_Imprt/ProcessCnsldtnGrpJrnlEntrJob?
runId='fd617deb-075a-41e0-a4d4-
ba67d50b2426'&dataHeader='I_FSItem,I_SubItem,I_Amount'&data='172100,915,132%0A
172999,915,456'

11.6 Close Job

API_CnsldtnGrpJrnlEntr_Imprt/CloseCnsldtnGrpJrnlEntrJob (action)

This API:

1. Closes the run.

2. Computes the final status and logs, and then triggers the post processing actions (set in the
actionAfterMapping parameter):

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
68 CONFIDENTIAL Group Journal Entries - Import API
 1. If data is staged, it triggers a validity period from the dataRetentionPeriod parameter. Data is
deleted after this period.
2. If data is not staged, it's directly sent to the S/4HANA backend.

Request Parameters Required Data Type Description

runId yes string Identifier of the run

 Note

You must add the parameter values to a query string.

 Sample Code

POST
https://grdc-api.grdc-sap.cfapps.[region_name].hana.ondemand.com/
odata/v2/API_CnsldtnGrpJrnlEntr_Imprt/CloseCnsldtnGrpJrnlEntrJob?
runId='fd617deb-075a-41e0-a4d4-ba67d50b2426'

11.7 Retrieve Mapped Data

API_CnsldtnGrpJrnlEntr_Imprt/GetCnsldtnGrpJrnlEntr (read)

This API returns the staged data generated by the selected run, if the run is configured to stage the data
(otherwise it returns an error).

 Note

This function supports paging.

Request Parameters Required Data Type Description

runId yes string Identifier of the run

optional integer Number of rows to retrieve

top

optional integer Row from which you to start retrieving data

skip

 Note

You must add the parameter values to a query string.

Response Parame-
ters Required Data Type Description

numberOfRows yes integer Total number of mapped rows

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Group Journal Entries - Import API CONFIDENTIAL 69
Response Parame-
ters Required Data Type Description

yes string JSON string such as "["col1","col2",..."coln"]"

columns

rows yes largestring JSON string such

as "[["valC1R1","valC2R1",...,"valCnR1"],
["valC1R2","valC2R2",...,"valCnR2"],...,
["valC1Rm","valC2Rm",...,"valCnRm"]]"

 Sample Code

GET
https://grdc-api.grdc-sap.cfapps.[region_name].hana.ondemand.com/odata/v2/
API_CnsldtnGrpJrnlEntr_Imprt/GetCnsldtnGrpJrnlEntr?runId='fd617deb-075a-41e0-
a4d4-ba67d50b2426'&top=100&skip=2
response:
{
"numberOfRows": 2,
"columns":
"[\"SUBITEMCATEGORY\",\"PROFITCENTER\",\"FINANCIALSTATEMENTITEM\",\"SUBITEM\",
\"CONSOLIDATIONUNIT\",\"CHARTOFACCOUNTS\",\"AMOUNTINLOCALCURRENCYCURRENCY\",\"
COSTCENTER\",\"AMOUNTINLOCALCURRENCY\"]",
"rows":
"[[\"1\",\"17\",\"141200\",\"955\",\"CUDC18\",\"a\",\"EUR\",\"17\",\"807.00000
0\"],

[\"1\",\"17\",\"141200\",\"955\",\"CUDC18\",\"a\",\"EUR\",\"17\",\"807.000000\
"]]"
}

11.8 Send Mapped Data to Backend

API_CnsldtnGrpJrnlEntr_Imprt/SendCnsldtnGrpJrnlEntr (action)

This API sends the staged data generated by a run to the ACDOCU table and removes it.

If the data is no longer available, it returns an error.

Request Parameters Required Data Type Description

runId yes string Identifier of the run

 Note

You must add the parameter values to a query string.

 Sample Code

POST

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
70 CONFIDENTIAL Group Journal Entries - Import API
 https://grdc-api.grdc-sap.cfapps.[region_name].hana.ondemand.com/odata/v2/
API_CnsldtnGrpJrnlEntr_Imprt/SendCnsldtnGrpJrnlEntr?runId='fd617deb-075a-41e0-
a4d4-ba67d50b2426'

11.9 Delete Mapped Data

API_CnsldtnGrpJrnlEntr_Imprt/DeleteCnsldtnGrpJrnlEntr (action)

This API deletes the staged data generated by the selected run, if the run is configured to stage the data
(otherwise it returns an error).

Request Parameters Required Data Type Description

runId yes string Identifier of the run

 Note

You must add the parameter values to a query string, at the end of the base URL.

 Sample Code

POST
https://grdc-api.grdc-sap.cfapps.[region_name].hana.ondemand.com/
odata/v2/API_CnsldtnGrpJrnlEntr_Imprt/DeleteCnsldtnGrpJrnlEntr?
runId='fd617deb-075a-41e0-a4d4-ba67d50b2426'

11.10 Cancel a Run

API_CnsldtnGrpJrnlEntr_Imprt/CancelCnsldtnGrpJrnlEntrJob(action)

This API removes all the staged data, closes the run and updates the logs.

Request Parameters Required Data Type Description

runId yes string Identifier of the run

 Note

You must add the parameter values to a query string, at the end of the base URL.

 Sample Code

POST

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Group Journal Entries - Import API CONFIDENTIAL 71
 https://grdc-api.grdc-sap.cfapps.[region_name].hana.ondemand.com/
odata/v2/API_CnsldtnGrpJrnlEntr_Imprt/CancelCnsldtnGrpJrnlEntrJob?
runId='fd617deb-075a-41e0-a4d4-ba67d50b2426'

11.11 Retrieve the Run Result

API_CnsldtnGrpJrnlEntr_Imprt/CnsldtnGrpJrnlEntrRun (read)

This API returns statistics of the selected run: status, link to the task log, statistics, and logs.

Request Parameters Required Data Type Description

runId yes string Identifier of the run

 Note

You must add the parameter values as GUID to identify the oData entity.

 Sample Code

GET
https://grdc-api.grdc-sap.cfapps.[region_name].hana.ondemand.com/odata/v2/
API_CnsldtnGrpJrnlEntr_Imprt/ CnsldtnGrpJrnlEntrRun(guid'fd617deb-075a-41e0-
a4d4-ba67d50b2426')
response:
{
"executionStatus": "Success",
"executionStatusLabel": null,
"executionStatusListLabel": null,
"totalProcessTime": 723,
"duration": null,
"totalItemsProcessed": 8,
"rejectedItems": 0,
"mappingErrors": null,
"noMappingErrors": null,
"generatedItemsAfterAggregation": null,
"generatedItems": 8,
"linkToTaskLog": null,
"actionAfterMapping": 2,
"parentExecutionId": null,
"last_push_data_timestamp": "1636721371457",
"importLogStatus": "Success",
"importStatusLabel": null,
"importStatusCriticality": null,
"consolidationLedger": null,
"noConsolidationLedger": null,
"consolidationVersion": "Y10",
"consolidationChartOfAccounts": "Y1",
"fiscalYear": "2010",
"fiscalPeriod": "013",
"dataRetentionPeriod": "3600000",
"updateMode": 1,
"isPeriodicMode": true,
"updateModeLabel": null,
"isPeriodicLabel": null,
"erLogs": 0,
"erLogsVersion": 0,

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
72 CONFIDENTIAL Group Journal Entries - Import API
 "erLogsAvailable": null,
"erLogTypeUsed": null,
}

11.12 Retrieve the Mapping Logs

API_CnsldtnGrpJrnlEntr_Imprt/CnsldtnGrpJrnlEntrRun/MappingLog (read)

This API returns mapping logs.

Request Parameters Required Data Type Description

runId yes string Identifier of the run

 Note

You must add the parameter values as GUID to identify the oData entity.

 Sample Code

GET
https://grdc-api.grdc-sap.cfapps.[region_name].hana.ondemand.com/odata/v2/
API_CnsldtnGrpJrnlEntr_Imprt/ CnsldtnGrpJrnlEntrRun(guid'fd617deb-075a-41e0-
a4d4-ba67d50b2426')/MappingLog
response:
{
"results": [
{

"OrdinalID": "147740923107183",
"content": null,
"message": "Global Parameters - Chart of Accounts: Y1",
"level": "INFO",
"datasourceContentRowNumber": null,
"type": "MappingLogs",
"execution_ID": "f62ca2b8-89a3-4333-82b0-6883bfb4ddd5",

},

{
"OrdinalID": "147561866801460",
"content": null,
"message": "The mapping definition to be run is
BasicMappingDemo.",
"level": "INFO",
"datasourceContentRowNumber": null,
"type": "MappingLogs",
"execution_ID": "f62ca2b8-89a3-4333-82b0-6883bfb4ddd5",

},
{
"OrdinalID": "147651501011109",
"content": "A1610,F15,482\r\n",
"message": "Row 2 does not match any rules.",
"level": "INFO",
"datasourceContentRowNumber": 2,
"type": "MappingLogs",

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Group Journal Entries - Import API CONFIDENTIAL 73
 "execution_ID": "f62ca2b8-89a3-4333-82b0-6883bfb4ddd5",

}
]
}

11.13 Retrieve the Import Logs

API_CnsldtnGrpJrnlEntr_Imprt/CnsldtnGrpJrnlEntrRun/ImportLog (read)

This API returns the import logs from the Task Log application.

Request Parameters Required Data Type Description

runId yes string Identifier of the run

 Note

You must add the parameter values as GUID to identify the oData entity.

 Sample Code

GET
https://grdc-api.grdc-sap.cfapps.[region_name].hana.ondemand.com/odata/v2/
API_CnsldtnGrpJrnlEntr_Imprt/ CnsldtnGrpJrnlEntrRun(guid'fd617deb-075a-41e0-
a4d4-ba67d50b2426')/ImportLog
response:
{
"results": [
{

"CnsldtnlogItemnumber": "eb949cdd-f54e-4d2b-919f-595d8bd9ce02",
"CnsldtnLogNumber": null,
"SystemMessageTypeSortOrder": "1.0",
"SortField": "1.0",
"CnsldtnJrnlEntryAmtInGrpCrcy": "0.00",
"CnsldtnTriggeringAmtInGrpCrcy": "1614.00",
"CnsldtnJrnlEntryAmtInLoclCrcy": "0.00",
"CnsldtnTriggeringAmtInLoclCrcy": "1614.00",
"CnsldtnJrnlEntryAmtInTransCrcy": "0.00",
"CnsldtnTriggeringAmtInTC": "0.00",
"CnsldtnJrnlEntryQtyInBsUnt": "0.00000000",
"CnsldtnTriggeringQtyInBsUnt": "0.00000000",
"AssignmentReference": "",
"BillingDocumentTypeText": "",
"ChartOfAccountsText": "a",
"ConsolidationAcquisitionPeriod": "000",
"ConsolidationAcquisitionYear": "0000",
"ConsolidationVersion": "YB2",
"ConsolidationApportionment": "0",
"ConsolidationChartOfAccounts": "Y1",
"CurrencyConversionsDiffType": "0",
"CnsldtnReferenceJrnlEntry": "",
"ConsolidationDocumentType": "",
"FinancialStatementItem": "141200 (Derivatives, Current)",
"SubItem": "955 (Fair value)",
"SubItemCategory": "1 (Transaction Types)",

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
74 CONFIDENTIAL Group Journal Entries - Import API
 "ConsolidationGroup": "",
"InvesteeConsolidationUnit": "",
"ConsolidationLedger": "Y1",
"PartnerConsolidationUnit": "",
"PostingLevel": "",
"ConsolidationUnit": "CUDC18 (CUDC18)",
"CompanyCode": "",
"ControllingAreaText": "",
"CostCenterText": "17",
"CnsldtnTaskLogItemType": "Uploaded Data",
"FinancialTransactionType": "",
"PostingFiscalPeriod": "005",
"PostingFiscalYear": "2019",
"FunctionalAreaText": "",
"CnsldtnTaskLogItemTypeTxt": "",
"CnsldtnMsgTypeTxt": "Error",
"MessageCriticality": 1,
"PartnerProfitCenterText": "",
"PartnerSegmentText": "",
"ProfitCenterText": "17",
"CnsldtnTskLgItmRowNmbr": "000001",
"CnsldtnSegmentText": "",
"CnsldtnJrnlEntryAmtGrpCrcy": "EUR",
"CnsldtnTriggeringAmtGrpCrcy": "EUR",
"CnsldtnJrnlEntryAmtLoclCrcy": "EUR",
"CnsldtnTriggeringAmtLoclCrcy": "EUR",
"CnsldtnJrnlEntryAmtTransCrcy": "",
"CnsldtnTriggeringAmtTransCrcy": "",
"CnsldtnJrnlEntryQtyBaseUnit": "",
"CnsldtnTriggeringQtyBaseUnit": "",
"SystemMessageIdentification": "",
"SystemMessageNumber": ""
}
]
}

11.14 Create a Batch Request

The endpoint to send a batch request is API_CnsldtnGrpJrnlEntr_Imprt/$batch.

For more information, see the official oData documentation at: https://www.odata.org/documentation/odata-
version-2-0/batch-processing/

 Sample Code

POST
body
{
--batch_d86a-5aa9-49b7
Content-Type: multipart/mixed; boundary=changeset_9ab1-ec21-1095
--changeset_9ab1-ec21-1095
Content-Type: application/http
Content-Transfer-Encoding: binary
POST ProcessCnsldtnGrpJrnlEntrJob?
runId='{{current_run_id}}'&dataHeader='I_FSItem,I_SubItem,I_Amount'&data='1721
00,SUBI01,132%0A172999,SUBI01,456' HTTP/1.1
Accept: application/json
Content-Type: application/json
--changeset_9ab1-ec21-1095--

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Group Journal Entries - Import API CONFIDENTIAL 75
 --batch_d86a-5aa9-49b7--
}
response
{
--batch_abe912a1-dd34-4dd2-9bf9-e470a9e903b9
Content-Type: multipart/mixed; boundary=changeset_b25cb74a-b1b4-4013-
aab2-88d2248e6dd9
--changeset_b25cb74a-b1b4-4013-aab2-88d2248e6dd9
Content-Type: application/http
Content-Transfer-Encoding: binary
HTTP/1.1 200 OK
DataServiceVersion: 1.0
Content-Type: application/json
Content-Length: 43
{"d":{"ProcessCnsldtnGrpJrnlEntrJob":true}}
--changeset_b25cb74a-b1b4-4013-aab2-88d2248e6dd9--
--batch_abe912a1-dd34-4dd2-9bf9-e470a9e903b9--
}

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
76 CONFIDENTIAL Group Journal Entries - Import API
12 Security and Data Protection and Privacy

This document describes the security and data protection and privacy configurations and how SAP Group
Reporting Data Collection complies with them.

The following sections cover the main security measures that are in place and the security-relevant settings
that you need to make.

12.1 Security Recommendations

These recommendations help you evaluate the security of the configuration of SAP Group Reporting Data
Collection in your landscape.

 Remember

As part of the cloud shared responsibility model (restricted access), you're responsible for determining if
any of these recommendations are relevant to your environment and to what extent.

The security recommendations are provided as a courtesy, without a warranty, and may be subject to
change. For more information, see the disclaimer.

SAP Group Reporting Data Collection is delivered with secure default configurations wherever this is possible.
However, you might want to review some settings and adjust them to your particular use case and corporate
policies. For more information on these recommendations, see the recommended settings for the SAP
Business Technology Platform: SAP BTP Security Recommendations.

Related Information

Additional Services [page 77]

Data Protection and Privacy [page 78]

12.2 Additional Services

To comply with security and data protection and privacy, you need to subscribe to the following services, from
your global account on the SAP Business Technology Platform.

• SAP Data Privacy Integration

SAP Data Privacy Integration is an information framework that allows you to identify data subjects and
inform them about which of their personal data is stored and used by an application and process requests

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Security and Data Protection and Privacy CONFIDENTIAL 77
 from the data subject regarding their personal data. Depending on your country and the laws that apply
there regarding data protection, you may need to subscribe to the SAP Data Privacy Integration Next
Generation service (application plan name ngdpi) to manage personal data.
For more information, see Data Privacy Integration and Manage Personal Data - Data Privacy Integration
NextGen.
• SAP Audit Log Viewer
The SAP Audit Log Viewer service allows you to display the audit logs for any events related to security or
data modification within SAP Group Reporting Data Collection apps.
For more information, see Audit Log Viewer for Cloud Foundry Environment.

12.3 Data Protection and Privacy

Data protection is associated with numerous legal requirements and privacy concerns. In addition to
compliance with general data protection and privacy acts, it is necessary to consider compliance with industry-
specific legislation in different countries. SAP provides specific features and functions to support compliance
with regard to relevant legal requirements, including data protection, which are documented in these templates
along with the assumptions that have been guiding the implementation in the software. By nature of legal
requirements the conclusion whether these features are covering customer specific demands as well as the
conclusion whether additional measures have to be taken is solely with the customer.

 Note

SAP does not provide legal advice in any form. SAP software supports data protection compliance by
providing security features and specific data protection-relevant functions, such as simplified blocking and
deletion of personal data. In many cases, compliance with applicable data protection and privacy laws will
not be covered by a product feature. Definitions and other terms used in this document are not taken from
a particular legal source.

 Caution

The extent to which data protection is supported by technical means depends on secure system operation.
Network security, security note implementation, adequate logging of system changes, and appropriate
usage of the system are the basic technical requirements for compliance with data privacy legislation and
other legislation.

Which personal data is processed by SAP Group Reporting Data Collection?

• User ID
• Email address
• Last Name
• First Name

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
78 CONFIDENTIAL Security and Data Protection and Privacy
12.3.1 Glossary

The following terms are general to SAP products. Not all terms may be relevant for this SAP product.

Term Definition

Artificial Intelligence (AI) The simulation of human intelligence processes by machines

and computer systems – typically by learning, coming to its
own conclusions, appearing to understand complex content,
engaging in natural dialogs with people, enhancing human
cognitive performance (also known as cognitive computing)
or replacing people on execution of nonroutine tasks. Appli-
cations include autonomous vehicles, automatic speech rec-
ognition and generation and detecting novel concepts and
abstractions (useful for detecting potential new risks and
aiding humans to quickly understand very large bodies of
ever-changing information)

Automated Decision Making The ability to make decisions by technological means with-
out human involvement.

Blocking A method of restricting access to data for which the primary

business purpose has ended.

Business Purpose The legal, contractual, or in other form justified reason for
the processing of personal data to complete an end-to-end
business process. The personal data used to complete the
process is predefined in a purpose, which is defined by the
data controller. The process must be defined before the per-
sonal data required to fulfill the purpose can be determined.

Consent The action of the data subject confirming that the usage
of his or her personal data shall be allowed for a given pur-
pose. A consent functionality allows the storage of a consent
record in relation to a specific purpose and shows if a data
subject has granted, withdrawn, or denied consent.

Data Subject Any information relating to an identified or identifiable natu-

ral person ("data subject"). An identifiable natural person is
one who can be identified, directly or indirectly, in particular
by reference to an identifier such as a name, an identifica-
tion number, location data, an online identifier, or to one or
more factors specific to the physical, physiological, genetic,
mental, economic, cultural, or social identity of that natural
person.

Deletion Deletion of personal data so that the data is no longer avail-

able.

End of Business Defines the end of active business and the start of residence
time and retention period.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Security and Data Protection and Privacy CONFIDENTIAL 79
Term Definition

End of Purpose (EoP) The point in time when the processing of a set of personal
data is no longer required for the primary business purpose,
for example, when a contract is fulfilled. After the EoP has
been reached, the data is blocked and can only be accessed
by users with special authorizations (for example, tax audi-
tors).

End of Purpose (EoP) check A method of identifying the point in time for a data set when
the processing of personal data is no longer required for the
primary business purpose. After the EoP has been reached,
the data is blocked and can only be accessed by users with
special authorization, for example, tax auditors.

Personal data Any information relating to an identified or identifiable natu-

ral person ("data subject"). An identifiable natural person is
one who can be identified, directly or indirectly, in particular
by reference to an identifier such as a name, an identifica-
tion number, location data, an online identifier, or to one or
more factors specific to the physical, physiological, genetic,
mental, economic, cultural, or social identity of that natural
person.

Processing of Personal Data Processing means any operation or set of operations which
is performed on personal data or on sets of personal data,
whether or not by automated means, such as collection, re-
cording, organisation, structuring, storage, adaptation or al-
teration, retrieval, consultation, use, disclosure by transmis-
sion, dissemination or otherwise making available, alignment
or combination, restriction, erasure or destruction.

Purpose The information that specifies the reason and the goal for
the processing of a specific set of personal data. As a rule,
the purpose references the relevant legal basis for the proc-
essing of personal data.

Residence period The period of time between the end of business and the
end of purpose (EoP) for a data set during which the data
remains in the database and can be used in case of sub-
sequent processes related to the original purpose. At the
end of the longest configured residence period, the data is
blocked or deleted. The residence period is part of the over-
all retention period.

Retention period The period of time between the end of the last business
activity involving a specific object (for example, a business
partner) and the deletion of the corresponding data, subject
to applicable laws. The retention period is a combination of
the residence period and the blocking period.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
80 CONFIDENTIAL Security and Data Protection and Privacy
 Term Definition

Sensitive personal data A category of personal data that usually includes the follow-
ing type of information:

• Special categories of personal data, such as data reveal-

ing racial or ethnic origin, political opinions, religious or
philosophical beliefs, trade union membership, genetic
data, biometric data, data concerning health or sex life
or sexual orientation.
• Personal data subject to professional secrecy
• Personal data relating to criminal or administrative of-
fenses
• Personal data concerning insurances and bank or credit
card accounts

Technical and organizational measures (TOM) Some basic requirements that support data protection and
privacy are often referred to as technical and organizational
measures (TOM). The following topics are related to data
protection and privacy and require appropriate TOMs, for
example:

• Access control: Authentication features

• Authorizations: Authorization concept
• Read access logging
• Transmission control / Communication security
• Input control / Change logging
• Availability control
• Separation by purpose: Is subject to the organizational
model implemented and must be applied as part of the
authorization concept.

12.3.2 Information Report

The feature provides data associated to the Data Subject. It is in the duty of the customer to check, whether
all the data reported shall get handed over to the data subject, because the report might contain internal
customer information or information on other third parties. Data subjects have the right to receive information
regarding their personal data undergoing processing. The personal data record feature helps you to comply
with the relevant legal requirements for data protection by allowing you to search for and retrieve personal
data for a specified data subject. The search results are displayed in a comprehensive and structured list
containing all personal data of the data subject specified, organized according to the purpose for which the
data was collected and processed. The extracted data can be downloaded in form of a report, that provides
configuration and extensibility functionality. The access to the personal data record is only allowed with
authorization.

For more information on how to manage personal data, see the Data Privacy Integration NextGen
documentation, Manage Personal Data - Data Privacy Integration NextGen section.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Security and Data Protection and Privacy CONFIDENTIAL 81
12.3.3 Deletion of Personal Data

Simplified Blocking and Deletion

The processing of personal data is subject to applicable laws related to the deletion of this data when the
specified, explicit, and legitimate purpose for processing this personal data has expired. If there is no longer
a legitimate purpose, that requires the retention and use of personal data, it must be deleted irrecoverably.
Blocking is necessary when the original retention period has expired but additional applicable extended and
overruling (mandated by law) retention periods are still in place. After the expiration of the longest retention
period, the data must be deleted.

Deletion of Personal Data

When considering compliance with data protection regulations, it is also necessary to consider compliance
with industry-specific legislation in different countries. A typical potential scenario in certain countries is
that personal data shall be deleted after the specified, explicit, and legitimate purpose for the processing
of personal data has ended, but only if no other retention periods are defined in legislation, for example,
retention periods for financial documents. Legal requirements in certain scenarios or countries also often
require blocking of data in cases where the specified, explicit, and legitimate purposes for the processing of
this data have ended, however, the data still has to be retained in the database due to other legally mandated
retention periods. Sometimes, transactional data are personal data with relation to a master data object, e.g.
a sales order with reference to a business partner. Therefore, the challenge for deletion and blocking is first to
handle transactional data and finally other data, such as business partner data.

SAP Group Reporting Data Collection recommends that you delete your personal data.

For more information on deleting personal data, see the Data Privacy Integration NextGen documentation,
Deleting Personal Data - Data Privacy Integration NextGen section.

12.4 Export Comments, Questions, and Answers Data

With this app, you can export business data for comments, questions, and answers into CSV files from the
Enter Package Data app.

App ID:F7182

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
82 CONFIDENTIAL Security and Data Protection and Privacy
Prerequisites

To display the Export Comments, Questions, and Answers Data app under Home Administration , you
must have the GRDC_CQA_EXPORT role assigned to your user. For more information on roles, see Define and
Bundle Roles on SAP Business Technology Platform [page 52].

Key Features

You can use this app to do the following:

• Export business data for comments, questions, and answers.

• Download exported data as CSV files.
The CSV file contains the following:
• All versions of all comments, questions, and answers of the whole tenant.
• Only texts, the file doesn't include amounts or quantities.
• Everything is exported, including comments, questions, and answers. You can't choose between them.
• Cancel exports while they are running.
• Delete exported data.
• See a history of exports, with information such as when the export was run and by whom.

 Note

Generated CSV files expire after 14 days. You can run a new export only if you have deleted the existing
export or wait until it has expired.

Example: Questions

The following diagram shows an example of a generated CSV file containing all the questions, unless they are
deleted or expired:

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Security and Data Protection and Privacy CONFIDENTIAL 83
Example: Comments

The following diagram shows an example of a generated CSV file containing all the comments, unless they are
deleted or expired:

Example: Answers

The following diagram shows an example of a generated CSV file containing all the answers, unless they are
deleted or expired:

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
84 CONFIDENTIAL Security and Data Protection and Privacy
13 Get Support

This section gives you support information for SAP Group Reporting Data Collection apps and their
environment.

Troubleshooting

For configuration issues, please review the Administration Guide to ensure that trust has been properly
established between all components (SAP Business Techology Platform, SAP S/4HANA and SAP S/4HANA
Cloud, the Cloud Connector and Web Dispatcher for OnPremise).

For connectivity issues, see SAP BTP Connectivity Support.

SAP Support Information

If you can't find a solution to your issue, collect and provide the following specific, issue-relevant information to
SAP Support:

• URLs of SAP Group Reporting Data Collection apps.

• A screenshot of the error message for the failed operation or the error message from the HttpResponse
body.
• For Enter Package Data: screenshots of the form design and the form once it's been run.
• For Data Mapping: the source file if a CSV file is used, the mapping definition and the traceability logs.
• Access credentials for your S/4HANA or SAP S/4HANA Cloud system defined in the incident. Even if SAP
Group Reporting Data Collection is hosted on SAP BTP, we recommend entering your system ID, it would
allow SAP Product Support to get remote access to your system if it's required to resolve your issue.

You can submit this information by creating a customer ticket in the SAP CSS system using the following
components:

• FIN-CS-CDC for SAP Group Reporting Data Collection apps

• FIN-CS-CDC-CQA for Comments and Define Ad Hoc Items app
• FIN-CS-CDC-DAM for Define Data Mapping and Run Data Mapping apps
• FIN-CS-CDC-DC for Enter Package Data app
• FIN-CS-CDC-RPD for Manage Forms and Manage Packages apps
• BC-MID-SCC for the Cloud Connector app
• BC-CP-LCM-TMS for the SAP Cloud Transport Management app

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Get Support CONFIDENTIAL 85
Configuration issue

If you experience a serious issue that can't be resolved using only traces and logs, SAP Support may request
access to the following components:

• SAP BTP subaccount

• For the Cloud Foundry environment, provide the region and global account name. In the cockpit, open
the affected subaccount, and copy the URL.
• Add the cloudconsohcp@sap.com user as a member of the subaccount.
• Cloud Connector
Follow the instructions in these SAP notes:
• To provide access to the Administration UI via a browser, see 592085 SAP note.
• To provide SSH access to the operating system of the Linux machine on which the connector is
installed, see 1275351 SAP note.
• SAP S/4HANA system

Issue when using SAP Group Reporting Data Collection apps

In most cases, SAP will try to reproduce your issue in-house and will rely on traces and logs to find the root
cause.

However, if SAP can't find root cause based on the information provided, we may request access to SAP Group
Reporting Data Collection apps.

To allow this access:

• Assign the relevant role collection to the SAP user cloudconsohcp@sap.com, so this user can login to
your SAP Group Reporting Data Collection apps.
• If required, create a pending user in your SAP S/4HANA system with the same email or with p1942507962
as login name.

13.1 Cloud System Notifications

SAP Cloud customers can subscribe to various SAP Cloud Service notifications.

Cloud System Notification Subscriptions (CSNS) is an application that allows SAP Cloud customers to
configure, customize, and subscribe to various SAP Cloud Service notifications.

• Within CSNS, you can set your preferences for which types of notifications you would like to receive in
cases of both planned and unplanned downtimes, as well as customer communication notifications. You
can manage the existing subscriptions, add new ones, and set notification recipients.
• You can access the CSNS application via the Cloud System Notification Subscriptions . You can access
the User Guide and watch videos via the Support Page .

Cloud Availability Center (CAC) offers you a personalized dashboard with focus on relevant information about
your Cloud product availability and maintenance.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
86 CONFIDENTIAL Get Support
 • In CAC, you can view your SAP Cloud products with status and availability, an events calendar, notifications
history, and the latest news.
• You can access the CAC via the Cloud Availability Center . You can access the User Guide and watch
videos via the Support Page .

 Note

To sign up for notifications, an S-User is required.

If you have any issues with your S-User, create an incident under the XX-SER-SAPSMP-SUP component in
the SAP for Me .

You can use the following SAP Knowledge Base Articles to assist you in this task:

• 1271482 - How does an administrator create or delete S-user IDs

• 1511008 - How to add or change authorizations for a S-User ID
• 1282854 - Information on adding/editing/deleting authorizations for an S-user ID

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Get Support CONFIDENTIAL 87
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.

Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
88 CONFIDENTIAL Important Disclaimers and Legal Information
Administration Guide for SAP Group Reporting Data Collection - Integration with SAP S/
4HANA Cloud, public edition
Important Disclaimers and Legal Information CONFIDENTIAL 89
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