High- Level Specification

Functional Overview

This enhancement is to ensure that manual journals posted in the system have adequate supporting documents attached before they get routed for review and approval.

The primary purpose is to increase the degree of SOX compliance and to further tighten internal controls around manual journal entries and to drive up efficiency in the journal review process in the new S/4 HANA systems.

Internal controls exist at Syensqo around the existence of supporting documents for manually posted journals in the system. This is currently monitored via detective mechanisms at period-end that requires manual With the proposed enhancement it is safeguarded that

1.) the internal control is adhered to in all cases in a preventive manner rather than via detective monitoring activities at period-end

2.) Approvers/Reviewers don’t need to spend time rejecting journals that lack supporting documents which should lead to efficiency gains compared to the current state.

Scope and Objectives

This enhancement shall be applicable to manual journals posted via the below two Fiori applications and its respective successor apps in future S/4 HANA releases:

• F4670A - Verify Currency Adjustment- New Version
• F2457A - Verify General Journal Entries - New Version

Please note that Fiori app 'F4670A - Verify Currency Adjustment-New Version' also allows for bulk upload processing via Excel upload functionality. As part of this process, another enhancement (ERP-558) automatically attaches the Excel upload template as supporting document to all journals submitted for review in the respective upload batch. As such, the existence of a supporting document is system-assured if journal entries are entered via this mode of entry and therefore doesn't require further validation via this enhancement. Journals uploaded via Excel upload functionality shall be exempted from the validations proposed in this enhancement.

SAP standard does not provide similar validation features in its current S/4 HANA releases and also doesn't intend to implement any in the foreseeable future. An incident with SAP was logged to query about possible inclusions in the future roadmap designs for journal entries. While the request was acknowledged and generally understood as a legit requirement, SAP also pointed out that there is no roadmap item planned out currently to embed this feature into the standard product offerings in the foreseeable future. Please refer to OSS incident 858195/2025 for further reference.

Assumptions

The following assumptions are taken for this custom development:

• Fiori applications evolve over time as SAP is constantly improving its current product offerings. At the time of writing, the enhancement is applicable to journal entries posted via Fiori apps F4670A and F2457A which are the latest journal entry apps available in S/4 private cloud environments. If new apps are released by SAP in future releases that offer significantly better useability for journal entry processing, Syensqo may adopt these applications as new default entry methods for journal entries. The enhancement may need to be extended to those successor applications as well in future releases.
• The enhancement shall be withdrawn once SAP adds the built feature into its scope of standard functionalities for journal entry processing.
• The enhancement shall remain in place even if Syensqo decides to move away from a mandatory review process for high-value G/L journals to ensure compliance with internal controls and best practices for journal entry processing. Journals posted without adequate levels of support invite audit queries that may be difficult to resolve without proper justifications.

Dependencies

Security, Integrity and Controls

Configuration Requirements

Language Requirements

Special Requirements

Design Rationale

Functional Requirements

Proposed Technology to Use

Data Source Considerations

Data Validation Considerations

Custom Tables

Master Data

Configuration Table

Selection Screen Enhancement

Processing Logic

Volumetrics

Performance Considerations

Error Handling

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Enhancement Implementation

Other Development Objects

Appendix

Custom Authorization Group Naming Convention

This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.

See also

Change log