| Status | Approved |
|---|---|
| Owner | BECHTER-ext, Alex |
| Stakeholders | ANGGREANI-ext, Lisa Dirk van Mierlo |
| Jira Request ID | ERP-114 - Getting issue details... STATUS |
| Jira Development ID | ERP-558 - Getting issue details... STATUS |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | S/4 HANA (All instances) |
| Business Process Reference | 09.05.04.01. Process General Journal Entries |
Functional Overview
In the new S/4 HANA system, a standard SAP Fiori application will be deployed which allows for upload of manual journal entries in batches via Excel upload functionalities.
The standard Fiori applications does not provide a functionality to automatically attach the Excel template as supporting document to the journals created as part of the upload batch. At Syensqo, internal controls exist around existence of supporting documents for manual journal entries to be able to retrospectively explain the purpose of journal entries during internal or external audits. This is in line with industry practice and also recommended with view to the heightened focus on internal controls with regards to SOX compliance in the future.
The purpose of this enhancement is to equip the standard Fiori application for mass journal uploads via Excel functionality (going by its current Fiori app ID of F2547A) with a built-in functionality to automatically attach the Excel file to all journal entries created via a batch upload.
Scope and Objectives
The scope of the enhancement shall be limited to the prevailing version of the Excel upload functionality for manual journals in the latest S/4 HANA version deployed at Syensqo. At the time of writing, the enhancement shall therefore just apply to Fiori application F2547A.
The enhancement addresses the gap of the SAP standard delivery of the Fiori application to attach supporting documents automatically as part of the upload process. Some code analysis of the existing programs revealed that SAP seemed to work on such a feature in the past but decided not to implement it for unknown reasons (code snippet has been commented out). Further clarifications were sought from SAP on whether it is intended to add the functionality as a standard feature in the foreseeable future but no roadmap items or feedback from SAP was obtained that point into this direction.
With this enhancement compliance with internal controls regarding supporting documents for manual journals posted in the system will be system-assured.
Step | Description | Comment |
|---|---|---|
Assumptions
Dependencies
No dependencies other than
- Fiori apps need to be deployed with all required Odata services actively running.
- Master data readiness for posting journal entries in S/4 HANA systems.
- Base configuration for posting journal entries needs to be in place to commence testing.
Security, Integrity and Controls
No specific security or export control requirements applicable to this enhancement. The standard authorization checks of the calling program shall be followed and accesses as well as authorizations to the underlying Fiori application shall be granted according to the swim lane assignments in Signavio.
Configuration Requirements
Not applicable. Call-up point of enhancement is not dependent on system configurations.
Language Requirements
Not applicable as the enhancement is only executed in background processing without user intervention.
Special Requirements
Not applicable. No special requirements identified for this custom development.
Design Rationale
Functional Requirements
Proposed Technology to Use
For this custom development it is likely that an implicit enhancements in the app's OData services are needed to capture the uploaded batch file in order to link it to the journals created.
Data Source Considerations
This section is not applicable to this custom development.
Data Validation Considerations
This section is not applicable to this custom development.
Custom Tables
This section is not applicable to this custom development.
Selection Screen Enhancement
This section is not applicable to this custom development.
Processing Logic
Volumetrics
Performance Considerations
During peak days for manual journal entries, typically towards the end of an accounting period especially during quarterly or yearly closes, the volume of manual journal can spike up. The enhancement should be able to handle such sudden spikes of concurrently processed journals in an efficient manner.
Error Handling
Special error handling is not required. IT support tickets must be raised should the user detect any journal entries that bypassed the validation implemented via this enhancement. This would need to be investigated further by the technical team to identify glitches in the coding that allow users to bypass the implemented checks of this custom development.
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Enhancement Implementation
| Enhancement Type | Standard Definition Name | Custom Implementation Name | Design Rationale Reference |
|---|---|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
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.
ABAP | ZFI | ZMM | ZPS | ZCO | ZSD | ZBC | ZFI | ZCA |
|---|---|---|---|---|---|---|---|---|
| TABLES | ZFIT | ZMMT | ZPST | ZCOT | ZSDT | ZBCT | ZFIT | ZCAT |