Status
Owner	Lisa Anggreani
Stakeholders	MADJARIAN, Gilles
Jira Request ID
Jira Development ID

High- Level Specification

Parameter	Value
Application System	S/4 HANA RoW, S/4 HANA CUI, S/4 HANA CHINA
Business Process Reference	09.07.01.05. Manage General Ledger Period Close

Functional Overview

The functional design describes the scenario(s) where this user interface will be invoked and describes some estimates, requirements, and initial designs for how the user interface will work.

This apps will be called from Advance Financial Closing (AFC) task list and also can be executed from S4 HANA directly if required. This app is required in all three S/4 HANA Production systems.  

Scope and Objectives

Detail the functional scope and objectives of the User Interface. Please also describe the gap that will be addressed by this User interface (Compared to SAP Standard

Please refer to ERP-199

Process Flow Diagram

Insert the flowchart and fill in the steps

Please refer to ERP-199

Assumptions

Describe any assumptions that have been made in the process of completing this design. What functionality is expected of configuration or other developments that pass information to this development and/ or retrieve the information processed by it (performance, triggers, exceptions, etc.)> 

Please refer to ERP-199

Dependencies

Indicate any dependencies or constraints that may impact development, in terms of requirements from internal or external applications or teams, limited access to legacy system, time constraints or data restrictions. Also, please specify schedule dependencies e.g. interface or batch jobs that must run prior to execution.

Please refer to ERP-199

Security, Integrity and Controls

To detail the security requirements for processing this object, any data integrity issues associated with the object and the teams that will be responsible for processing the object, i.e. authorization/roles required to who can execute the interface, encryption requirement, etc.

This transaction will be assigned to role as per swimlane described in L4 09.07.01.05. Manage General Ledger Period Close

Configuration Requirements

Specify the configuration requirements for this object. Like in case of substitution/ routine specify the configuration needed

Not Applicable

Language Requirements

Specify the language requirements for this object. Specify the required language and type of translation, like labels, data. For non 4S languages the column Regulatory is mandatory to be filled in and details need to be provided.

Language for any error messages will need to be translated as per KDD055 - Multi-Language Support.

Special Requirements

Specify any special requirements or considerations that may impact the enhancement based on specific locations, regulatory compliance or system limitations. Clearly outline requirements e.g. localization rules for countries like China

This program needs to be accessible via Fiori Apps in each of production client. Also be able to be called from Advance Financial Closing (AFC). Please refer to OSS Note: 2879220 - AFC Integration of customer-specific reports for coding requirements

Design Rationale

This template may be used to specify User Interfaces to SAP applications

Recommended UI Technology

Consider which technology will be most appropriate – the use of Fiori framework as User Interfaces, other than this, justification is required.

Use of Fiori framework as User Interface 

Application Screen

Wireframe or Mock-Up

Please provide a Hi fidelity mock-up of the new application’s screens. Ensure Orica Brand’s standards are adhered to. (i.e. logo, font, colors, etc.) 

The developers should follow UI best practice to keep the screens user-friendly and consistent

Apps Name: Reclass Capex Supplier and Finance (Lease) Debt

Screen Behavior

Is any dynamic screen behaviour required? This typically sets the visibility, read-only or mandatory properties of the UI elements. E.g. if field ‘a’ has a value ‘x’, then make fields ‘b’, ‘c’ and ‘d’ read-only, and make field ‘e’ mandatory. For simple input fields, does the value need to be validated? Can a value-help be assigned?

Screen Validation: 

• When "Posting Period" and "Fiscal Year" specified on selection screen are greater than current date issue warning  (should only be run at month-end)
• When parameter for Ledger Group populated not equal to (<>) '0L' issue error message "Only ledger '0L' is allowed'
• Issue error when mandatory fields on selection parameters are not populated

Dynamic screen is required for "Reclass Tasks". When user select "Reclassification to Capex Supplier" it expands the screen to show these four parameters, and hidden the parameters for Finance Lease Debt. The same when a radio button "Reclassification to Finance Lease Debt" is selected, four parameters are shown. And parameters related to Capex supplier are now hidden. 

Dynamic screen is also required for "Production Run". When user select "Production Run" it expands the screen to show "Background Processing" option. When user select Radio button for "Test Run", the "Background Processing" option is hidden . 

Additionally, please refer to section "Selection Screen Enhancement" on ERP-199

Screen Navigation

How will the user navigate between screens? Are any buttons required that trigger actions?

Screen Default Layout on "Test Run" for Capex Supplier. For Finance Lease Debt default layout has "Contract Number" instead of "WBS" or "Project"

 

Screen Default Layout on "Production Run" for Capex Supplier. For Finance Lease Debt default layout has "Contract Number" instead of "WBS" or "Project"

Data Integration

Provide the details about the information will be displayed in the interface and where /how the information will be read/stored from. This must match to the screen mock-up

Selection screen 

Field	Table-Field Name	Input / Value help	Source Table
RLDNR	Ledger Group	Value Help	FAGL_TLDGRP
RBUKRS	Company Code	Value Help	T001
GJAHR	Fiscal Year	Input
POPER	Posting Period	Input
RACCT	GL Account	Value Help	SKA1, where Posting Block (XSPEB ) <>"X", Balance Sheet account (XBILK) = X", Account Group (KTOKS) = "ABST"
BLART	Document Type	Value Help	T003 (include BLART, and LTEXT)
BUDAT	Reversal Posting Date	Input
RACCT	Target Account:	Value Help	SKA1, where Posting Block (XSPEB ) <>"X", Balance Sheet account (XBILK) = X", Account Group (KTOKS) = "SAKO"
RACCT	Offset Account:	Value Help	SKA1, where Posting Block (XSPEB ) <>"X", Balance Sheet account (XBILK) = X", Account Group (KTOKS) = "SAKO"
RMVCT	Transaction Type:	Value Help	T856

Report Layout

Field	Table-Field Name	Display Field Name	Value	Source
		Status	"OK to post" or "ERR" (on test run)  "Posted" or "ERR" (on production run)	Spool result  BAPI_ACC_DOCUMENT_CHECK (test run) API_ACC_DOCUMENT_SRV or BAPI_ACC_DOCUMENT_POST (production run)
BELNR	Document Number	R_DocNum	(as per spool result on production run)
GJAHR	Fiscal Year	R_FY	(as per spool result on production run)
RBUKRS	Company Code	R_CoCd	(as per spool result on production run)
BUDAT	Posting Date	R_PostDt	(as per spool result on production run)
RACCT	G/L Account	R_Acc	(as per spool result on production run) = target G/L Account
RMVCT	Transaction Type	R_TType	(as per spool result on production run)
PRCTR	Profit Centre	R_Pctr	(as per spool result on production run)
RWCUR	Transaction Curr	R_TC	(as per spool result on production run)
WSL	Amount in TC	R_TC Amt	(as per spool result on production run)
RHCUR	Company Code Curr	R_LC	(as per spool result on production run)
HSL	Amount in LC	R_LC Amt	(as per spool result on production run)
RKCUR	Global Curr	R_GC	(as per spool result on production run)
KSL	Amount in GC	R_GC Amt	(as per spool result on production run)
...	...	(as per data retrieved from step 1-3 for Capex Reclass or step 1-2 for Finance Lease Debt Reclass)	(as per original value retrieved from step 1-3 for Capex Reclass  or step 1-2 for Finance Lease Debt Reclass)	Please refer to ERP-199 (Section: Processing Logic)

Custom Tables

If any custom configuration tables are required, which will be read by the enhancement logic, then specify them here.

Master data - N/A

Table Name (add more sections for different tables) 

Include an overview of the table and what it’s used for 

Field	Description	Data Type/Length	Validation rule / Value help

 Configuration table - N/A

Table Name (add more sections for different tables) 

Include an overview of the table and what it’s used for 

Field	Description	Data Type/Length	Validation rule / Value help

Tooltips

Not applicable

Front-End

This program/Fiori Apps will be run from desktop/laptop. This is not meant to be run from mobile phone / tablet

Mobile Services

Not applicable

Authentication & Authorization

Accessing the Fiori Apps should be done out of portal using SSO. Or triggering the apps from Advance Financial Close (AFC) by logging to AFC portal via SSO

Accessibility

Not applicable

Volumetrics

Please refer to ERP-199

Performance Consideration

Please refer to ERP-199

Error Handling

Please refer to ERP-199

Testing

How to Test

Please provide some guidance and/or test data to help the developer unit test the user interface. This can be included here or in a separate document. If possible, testing is to be done prior by Functional team, for those transactions or business processes to be automated. Please include both positive and negative testing (to validate error situations handling)

Please refer to ERP-199

Test Conditions and Expected Results

List all test conditions – this will then be used as a basis to execute both the technical and functional unit tests

Please refer to ERP-199

Test Considerations/Dependencies

List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.

Please refer to ERP-199

Other Information

Development Details

Package

Package Name	Parent Package

UI Implementation

UI Type	UI Name	Fiori Catalogue	Design Rationale Reference

API Implementation

API Type	API Name	Purpose / High Level Logic	API Product	Design Rationale Reference

Other Development Objects

Object Type	Object Name	Purpose/High Level Logic	Design Rationale Reference

Appendix

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log