3785789 - Version specific FS item mapping not applied during data release/realignment to group reporting

Requirement to maintain separate FS item mappings for different standard versions in Group Reporting.

During data release/realignment (RUJ) to Group Reporting, the system applies only one FS item mapping and ignores the version-specific mapping.

No error message is shown; results do not match expected FS item assignment.

SAP S/4HANA Cloud Public Edition

1. Assign FS item mappings per standard version (for example, Version A -> Mapping 1; Version B -> Mapping 2), including different revisions if required.
2. Run the Release Universal Journal in Data Monitor for version A and B.
3. Observe that postings use only the mapping version 1 defined in Version A, rather than the version-specific mapping. FS Mapping version 2 is ignored in version B
4. Run realignment job for version B but don't work neither. 

The Group Reporting Preparation Ledger configuration is set to a fixed FS item mapping; the realignment job considers only that mapping, so version-specific mappings are not applied.

1. Open the configuration activity “Define Group Reporting Preparation Ledgers.”
2. Change the FS item mapping in the preparation ledger to the mapping required for the version you intend to release/realign.
3. Run the realignment/Release Universal Journal job again.
4. When working with another version that uses a different FS item mapping, update the preparation ledger’s FS item mapping accordingly before running realignment.
5. Verify that the FS items are transferred according to the intended version-specific mapping.

refer to: Define Group Reporting Preparation Ledgers

group reporting, preparation ledger, fs item mapping, version, version-specific, realignment, ruj, release universal journal, data release, acdoca, fincs_fsimapitm, mapping revision, consolidation, s/4hana cloud public edition, finance , KBA , FIN-CS-COR-DT-2CL , Data Transfer (Public Cloud) , Problem