3699966 - Unexpected custom field automatically populated in group reporting upload template in application "Import Group Journal Entries".

Symptom

Unexpected custom field automatically populated in Group Reporting Upload template in application “Import Group Journal Entries” (Fiori ID: F3073).

The field:

Is included in all Group Reporting upload templates when downloading the template from the app
Appears even though it is not intended to be manually populated for Group Reporting
May have been originally created for other processes (for example, Billing or Financial Accounting)
Causes confusion for users, who expect the field not to be required for Group Reporting uploads

The behavior occurs without any error message, and data upload remains technically possible.

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

Navigate to the "Import Group Journal Entries" application.
Click on the "Download Template" button.
Select any template and click "Download".
Open the downloaded Excel upload template and observe the custom field automatically populated.

Cause

In SAP S/4HANA Cloud Public Edition, the appearance of a custom field in Group Reporting upload templates is the result of standard business context inheritance and template generation logic.

When a custom field is enabled for "Accounting: Coding Block to Consolidation Journal Entry", the system automatically makes the field available for consolidation and Group Reporting–related processing, as consolidation journal entries and Group Reporting are treated as interconnected business functions.

Additionally, if the same custom field is created or released for the business context "Group Reporting: Journal Entry Item", the system interprets this as the field being relevant for Group Reporting journal entries.

The Import Group Journal Entries app generates upload templates dynamically and automatically includes all active custom fields that are associated with Group Reporting business contexts. Once a custom field is enabled for Group Reporting journal entries, the system assumes it may be relevant for manual uploads and therefore includes it in all Group Reporting templates.

The system does not distinguish between:

Custom fields intended for automatic derivation (for example, from Billing or Financial Accounting), and
Custom fields intended for manual input during Group Reporting uploads.

There is also no selective field inclusion mechanism in standard template generation in SAP S/4HANA Cloud Public Edition. As a result, all active custom fields marked for Group Reporting business contexts are included in the upload template.

Resolution

This is the expected system behavior.

The presence of a custom field in the Group Reporting upload template:

Does not prevent data upload,
Does not require the field to be populated,
Does not affect validation, posting logic, or consolidation results,
As long as the field is not defined as mandatory and no validation logic depends on it.

Empty or unused Custom Fields included in the template are ignored by the system during upload, and the remaining Group Reporting data is processed normally.

No system correction or configuration change is required.

If the custom field should not appear in the Group Reporting upload template, the only supported option is to remove the “Group Reporting: Journal Entry Item” business context from the custom field. Otherwise, the field can safely remain in the template without functional impact.

Keywords

group reporting, custom field, upload template, import group journal entries, Fiori ID F3073, accounting coding block, consolidation journal entry, group reporting journal entry item, template generation logic, unexpected field, S/4HANA Cloud. , KBA , FIN-CS-COR-2CL , S/4HANA Financial Consolidation, Core Processing (Publ Cld) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions