CUSTOMER

How-To Execute Field Extension of ACDOCU

SAP S/4HANA Finance for group reporting

1 HOW TO EXECUTE FIELD EXTENSION

Applies to:

This guide applies to the following SAP S/4HANA Finance for group reporting versions:

On Premise
S4 1909- FPS01
S4 2020- FPS00 & FPS01& FPS02
S4 2021- FPS00 & FPS01& FPS02

REVISION HISTORY

Date Description Version

23 - Aug-2021 Final Version V1
23-Sep-2021 Updated Version V2
13-Dec-2021 Updated Version V3
09-Sep-2022 Add note in 1.1.10 V4
Add information coding block chapter 1.2.5.1 V5
11-Oct-2022
and 1.2.5.2.
Add information in chaper 1.3.6. so that there V6
21-Oct-2022
is a reference to chapter from scenario 2

Purpose:

This document intends to help customers and partners better understand custom dimension
extension of table ACDOCU for consolidation processing and reporting. When designing the SAP
S/4HANA system and the group reporting area, the focus was placed on the most common
dimensions that are widely used according to experience. However, customers nowadays may have
additional reporting requirements. Hence, there’s now a demand for the extensibility of Universal
Journal Table ACDOCA and Group Reporting Table ACDOCU.

How to execute field extension of ACDOCU 2

TABLE OF CONTENTS
1 BACKGROUND INFORMATION ...................................................................................................... 5
1.1 Scenario 1: Custom Field in ACDOCU and no relation to ACDOCA ......................................... 5
1.1.1 Create new custom field ................................................................................................................. 5
1.1.2 Enable for UIs and reports .............................................................................................................. 6
1.1.3 Enable the OData APIs .................................................................................................................... 7
1.1.4 Enable the SOAP APIs .................................................................................................................... 7
1.1.5 Enable for Business Scenarios ...................................................................................................... 8
1.1.6 Save and publish ............................................................................................................................. 8
1.1.7 Maintain master data for extension fields ..................................................................................... 8
1.1.8 Upload RFD (insert this field in upload file) .................................................................................. 9
1.1.9 Manual posting with usage of the custom field.......................................................................... 10
1.1.10 Check the Group Data Analysis app ............................................................................................ 11
1.1.11 Availability in GRDC ...................................................................................................................... 11
1.1.11.1 Manual Data Entry – forms .......................................................................................................... 11
1.1.11.2 Mapping from external source ..................................................................................................... 11
1.1.11.3 Mapping from ACDOCA .............................................................................................................. 11
1.2 Scenario 2: Custom Field in ACDOCA and ACDOCU ................................................................ 12
1.2.1 Create new custom field ............................................................................................................... 12
1.2.2 Enable for UIs and reports ............................................................................................................ 12
1.2.3 Enable the OData APIs ................................................................................................................. 12
1.2.4 Enable the SOAP APIs .................................................................................................................. 12
1.2.5 Enable for Business Scenarios .................................................................................................... 12
1.2.5.1 Enable UIs and reports for Accounting: Coding Block (until 2021 FPS1) ....................................... 13
1.2.5.2 Enable UIs and reports for Accounting: Coding Block (as of 2021 FPS1) ...................................... 13
1.2.6 Save and publish ........................................................................................................................... 13
1.2.7 Maintain master data for extension fields ................................................................................... 13
1.2.8 Upload RFD (insert this field in upload file) ................................................................................ 13
1.2.9 Manual posting with usage of the custom field.......................................................................... 13
1.2.10 Check the Group Data Analysis app ............................................................................................ 13
1.2.11 Availability in GRDC ...................................................................................................................... 13
1.2.11.1 Manual Data Entry – forms .......................................................................................................... 13
1.2.11.2 Mapping from external source ..................................................................................................... 13
1.2.11.3 Mapping from ACDOCA .............................................................................................................. 13
1.3 Scenario 3: Extend the existing Coding Block from ACDOCA to ACDOCU ............................ 14
1.3.1 Prerequisite .................................................................................................................................... 14
1.3.2 Create the same field with a check table in group reporting .................................................... 15
1.3.3 Enable for UIs and reports ............................................................................................................ 17
1.3.4 Enable the OData APIs ................................................................................................................. 18
1.3.5 Enable the SOAP APIs .................................................................................................................. 18
1.3.6 Enable for business scenarios ..................................................................................................... 18
1.3.7 Save and publish ........................................................................................................................... 19
1.3.8 Maintain master data for extension fields ................................................................................... 19
1.3.9 Upload RFD (insert this field in upload file) ................................................................................ 19
1.3.10 Manual posting with usage of the custom field.......................................................................... 19

2
1.3.11 Check the Group Data Analysis app ............................................................................................ 19
1.3.12 Availability in GRDC ...................................................................................................................... 19
1.3.12.1 Manual Data Entry – forms .......................................................................................................... 19
1.3.12.2 Mapping from external source ..................................................................................................... 19
1.3.12.3 Mapping from ACDOCA .............................................................................................................. 19
2 ADDITIONAL INFORMATION ........................................................................................................ 19
2.1 Limitations ...................................................................................................................................... 19
2.2 Related Information ....................................................................................................................... 19

How to execute field extension of ACDOCU 4

1 BACKGROUND INFORMATION
The following steps serve as a step-by-step guide for custom field extension. The following
different use cases are covered:

▪ Scenario 1: Custom Field in ACDOCU and no relation to ACDOCA

▪ Scenario 2: Custom Field in ACDOCU and in ACDOCA
▪ Scenario 3: Extend the existing Coding Block from ACDOCA to ACDOCU

The SAP S/4HANA for group reporting 1909 FPS1 release and later releases include the following
new and improved key features:

▪ The extensibility framework was introduced, allowing you to define your own custom fields
and use them in the consolidation process. Once the fields are created and activated, they
behave similarly to standard delivered fields. Therefore, upload, process, and report data on
additional extended fields are supported.

Prerequisite:
Log on with user role SAP_BASIS_BCG_EXT, and the business catalog SAP_BASIS_BC_EXT is
assigned.

1.1 Scenario 1: Custom Field in ACDOCU and no relation to ACDOCA

1.1.1 Create new custom field

o Start the Custom Fields app from the Fiori launchpad

o Create
o Insert Field Properties (example below for BRAND dimension)
o Create and Edit

How to execute field extension of ACDOCU 5

1.1.2 Enable for UIs and reports

In the UIs and Reports tab, you define/enable where the new custom field will be available based
on the consolidation processing and reporting.

Consolidation - Released Reported Data Enable Usage

Consolidation - Released Reported Data Enable Usage
Consumption view for crcy translation Enable Usage
Consumption view for data collection Enable Usage
Consumption view for manual journal entry Enable Usage
Consumption view for reclassification Enable Usage

How to execute field extension of ACDOCU 6

Group Data Analysis Enable Usage
Group Data Analysis Cube Enable Usage
Group Data Analysis – With Reporting Rules Enable Usage
Group Journal Entry Item Enable Usage
Group Journal Entry Item Enhanced - S&V Enable Usage
Group Reporting Unified Selection Enable Usage
Group Reporting Validation View Enable Usage
Journal Entry Item Enable Usage
Local/Group Data Analysis Query Enable Usage
Local/Group Data Analysis Query with Reporting Rules Enable Usage
Matrix Consolidation Foundation Cube Enable Usage
Matrix Consolidation Foundation Cube with Reporting Rule Enable Usage
Post Group Journal Entries Enable Usage
Post Group Journal Entries Service Enable Usage
Rule-Based Group Data Analysis Cube Enable Usage
Task log service Enable Usage

1.1.3 Enable the OData APIs

1.1.4 Enable the SOAP APIs

How to execute field extension of ACDOCU 7

1.1.5 Enable for Business Scenarios

The Business Scenarios setting determines in which context the customer field will be used. The
first business case describes the scenario where the custom field is solely used in group reporting
and not in accounting. Hence, the business scenario Coding Block for accounting shall not be
enabled.

1.1.6 Save and publish

Afterwards, save and publish the custom field by selecting Save and then Publish.

1.1.7 Maintain master data for extension fields

Depending on which type of field has been created, master data will have to be maintained.

For example, if “code list” is defined, then only selected values are allowed to be used, as the
following screenshot shows:

For example, if the type “text” is selected, then a “free text” up to the length specified in the
properties of the custom field can be entered. The same logic applies for type date, email, etc.

How to execute field extension of ACDOCU 8

However, it’s recommended to not use these types because they consume quite a significant
share of the allowed space for custom fields.

Additional Note:
There are space limitations for each business context. The limitation depends on the number
of custom fields and the length of the data type that is used. The Business Context Capacity
bar shows the remaining space. The limitation for business context is up to 100 fields and up
to 1000 characters.

It is not 1000 characters per field, but rather you can use a maximum of 1000 characters
within the maximum 100 fields. In other words, if you create 1 field with 1000 characters,
then you won’t be able to create more fields due to exceeded capacity.

However, there is no limitation due to type. In some types, such as “checkbox”, you only
need one character. But for “web address”, you can use 200 characters. Both contribute to
the maximum number of characters per Business Context. In such a case, 1 checkbox field of
1 char + 1 web address field of 200 chars = 2 fields and 201 characters are used. In this
example, you would have 98 fields and 799 characters left.

For the type “Code List”, master data values must be maintained. For large amounts of master
data, you can use the upload function to upload master data from Excel files.

Once master data is maintained, the published field then automatically becomes part of the data
model and is ready to be used during the various consolidation steps.

1.1.8 Upload RFD (insert this field in upload file)

The newly created field can be used in a flexible upload. To do so, you must add the new field to
the column structure. It’s important to use the prefix “ZZ1_” before the field name.

How to execute field extension of ACDOCU 9

1.1.9 Manual posting with usage of the custom field

When posting manual group journal entries, the newly created field must be added to the
template first. In the overview screen, select “Create”. When the detail screen opens, click on the
“Settings” symbol (cog icon).

A pop-up window appears where the list of fields can be seen. Here, the newly created custom
field appears in the list and must be added to the template.

How to execute field extension of ACDOCU 10

 Please note:
You can create a group journal entry by using a new custom field. However, the Display
Group Journal Entries app doesn’t show this content. Instead, you can use the Group Data
Analysis app, which is described in next chapter.

1.1.10 Check the Group Data Analysis app

Click the tile Group Data Analysis.

On the left panel with the ranges of additional dimensions, “BRAND” should appear on the left
panel so that it can be used in reporting. When dragging the field into the column or row
structure, the values appear because the breakdown takes “BRAND” into account.

Note: For custom fields you cannot create a hierarchy for reporting purpose.

1.1.11 Availability in GRDC

1.1.11.1 Manual Data Entry – forms

The custom field is available for manual data entry in the forms. You must copy pre-delivered forms and
adjust.

1.1.11.2 Mapping from external source

The custom field is available in the template file for the output definition at the end of the table
with the identifier.

1.1.11.3 Mapping from ACDOCA

The custom field is available in the template file for the output definition at the end of the table
with the identifier.

How to execute field extension of ACDOCU 11

1.2 Scenario 2: Custom Field in ACDOCA and ACDOCU
In this chapter, you find information on how to create a new field in the universal journal
(ACDOCA) and make this field available for group reporting (ACDOCU).

1.2.1 Create new custom field

Please refer to 1.1.1 Create new custom field

1.2.2 Enable for UIs and reports

Please refer to 1.1.2 Enable for UIs and reports

1.2.3 Enable the OData APIs

Please refer to 1.1.3 Enable the OData APIs

1.2.4 Enable the SOAP APIs

Please refer to 1.1.4 Enable the SOAP APIs

1.2.5 Enable for Business Scenarios

The Business Scenarios setting determines in which context the customer field will be used. This
second business case describes the scenario where the custom field is used in group reporting and
in accounting. Therefore, the business scenario Coding Block for accounting must be enabled.

In this step, the ZZ1_BRAND dimension in the ACDOCA table (Universal Journal) will automatically
be generated. This dimension will be available for financial accounting – general ledger postings.
There is an automatic mapping between the ZZ1_BRAND of ACDOCA and ZZ1_BRAND of ACDOCU.
Business context for Accounting: Coding Block is created and needs to be maintained. This is
described in the subchapters below.

How to execute field extension of ACDOCU 12

1.2.5.1 Enable UIs and reports for Accounting: Coding Block (until 2021 FPS1)

1.2.5.2 Enable UIs and reports for Accounting: Coding Block (as of 2021 FPS1)

1.2.6 Save and publish

Please refer to 1.1.6 Save and publish.

1.2.7 Maintain master data for extension fields

Not applicable, master data already exist.

1.2.8 Upload RFD (insert this field in upload file)

Please refer to 1.1.8 Upload RFD (insert this field in upload file)

1.2.9 Manual posting with usage of the custom field

Please refer to 1.1.9 Manual posting .

1.2.10 Check the Group Data Analysis app

Please refer to 1.1.10 Check the Group Data Analysis app

1.2.11 Availability in GRDC

1.2.11.1 Manual Data Entry – forms

Refer to 1.1.11.1 Manual Data Entry – forms

1.2.11.2 Mapping from external source

Refer to 1.1.11.2 Mapping from external source

1.2.11.3 Mapping from ACDOCA

Refer to 1.1.11.3 Mapping from ACDOCA

How to execute field extension of ACDOCU 13

1.3 Scenario 3: Extend the existing Coding Block from ACDOCA to ACDOCU
There are cases where ACDOCA was already enhanced prior to the existence of the newly
launched extensibility framework. Such cases occur if customers have created ACDOCA
enhancements using traditional Coding Block extensions. The following steps serve as a step-by-
step guide to show you how to link those fields created in ACDOCA with transaction OXK3 to group
Reporting in ACDOCU.

1.3.1 Prerequisite

A custom field in CI_COBL was created in transaction OXK3:

This field in ACDOCA contains a check table:

Subsequently, the field was enabled for “Custom Fields and Logic” with business context “Coding
Block” in transaction SCFD_EUI for database table ACDOCA:

How to execute field extension of ACDOCU 14

1.3.2 Create the same field with a check table in group reporting

The field shall also be used in group reporting. However, if you just enable the business scenario
Accounting: Coding Block to Consolidation Journal Entry, then the field will not have a check table
in the generated append to table ACDOCU. As a result, data validation against the check table
won’t work, such as in flexible upload.
To create the same field with a check table in group reporting, the following approach must be
followed instead:

(1) Create an append structure to CJE_S_INCL_EEW_PS

How to execute field extension of ACDOCU 15

 (2) Add the field with the same data element but with a different name (for example, with a
suffix), and add the same check table to the field:

(3) Now use SCFD_EUI for group reporting, database table ACDOCU:

(4) Choose “Attach Field to Existing Custom Field” and attach it to the Coding Block custom
field:

How to execute field extension of ACDOCU 16

 (5) The field is now available for group reporting, and it has a check table as in Coding Block.

The created field is now connected to Group Reporting with the respective check table.

1.3.3 Enable for UIs and reports

o Start the Custom Fields and Logic app from the Fiori front end

o Select the field and maintain the ACDOCU usage as needed and as described below.

How to execute field extension of ACDOCU 17

1.3.4 Enable the OData APIs
Please refer to 1.1.3 Enable the OData APIs

1.3.5 Enable the SOAP APIs

Please refer to 1.1.4 Enable the SOAP APIs

1.3.6 Enable for business scenarios

The Business Scenarios setting determines in which context the customer field will be used.
Enable business scenario “Accounting: Coding Block to Consolidation Journal Entry” for the field.

With this step, the ZZ1_BRAND dimension in ACDOCA table (Universal Journal) will automatically
be generated. This dimension will be available for financial accounting – general ledger postings.
There’s an automatic mapping between the ZZ1_BRAND of ACDOCA and ZZ1_BRAND of ACDOCU.

How to execute field extension of ACDOCU 18

Pls. refer to 1.2.5 Enable for Business Scenarios
The settings described there must be made.

1.3.7 Save and publish

Please refer to 1.1.6 Save and publish.

1.3.8 Maintain master data for extension fields

Not applicable, master data already exist.

1.3.9 Upload RFD (insert this field in upload file)

Please refer to 1.1.8 Upload RFD (insert this field in upload file)

1.3.10 Manual posting with usage of the custom field

Please refer to 1.1.9 Manual posting with usage of the custom field.

1.3.11 Check the Group Data Analysis app

Please refer to 1.1.10 Check the Group Data Analysis app

1.3.12 Availability in GRDC

1.3.12.1 Manual Data Entry – forms

Refer to 1.1.11.1 Manual Data Entry – forms

1.3.12.2 Mapping from external source

Refer to 1.1.11.2 Mapping from external source

1.3.12.3 Mapping from ACDOCA

Refer to 1.1.11.3 Mapping from ACDOCA

2 ADDITIONAL INFORMATION

2.1 Limitations
Please refer the following note for restrictions: 2849287 - Extensibility in Group Reporting

2.2 Related Information

Please refer the following note for further information: 2453614 - FAQ: Universal Journal
Extensibility

How to execute field extension of ACDOCU 19

How to execute field extension of ACDOCU 20
 www.sap.com/contactsap

© 2021 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

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. See www.sap.com/copyright for additional trademark information and notices.

How to execute field extension of ACDOCU 21