| Status | Approved |
|---|---|
| Owner | Lisa Anggreani |
| Stakeholders | MADJARIAN, Gilles |
| Jira Request ID | ERP-96 - Getting issue details... STATUS |
| Jira Development ID | ERP-198 - Getting issue details... STATUS |
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
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
Process Flow Diagram
Assumptions
Dependencies
Security, Integrity and Controls
This transaction will be assigned to role as per swimlane described in L4 09.07.01.05. Manage General Ledger Period Close
Configuration Requirements
Not Applicable
Language Requirements
Language for any error messages will need to be translated as per KDD055 - Multi-Language Support.
Special Requirements
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
Recommended UI Technology
Use of Fiori framework as User Interface
Application Screen
Wireframe or Mock-Up
Apps Name: Reclass Capex Supplier and Finance (Lease) Debt
Screen Behavior
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.
Additionally, please refer to section "Selection Screen Enhancement" on ERP-199
Screen Navigation
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
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
Master data - N/A
| Field | Description | Data Type/Length | Validation rule / Value help |
|---|---|---|---|
Configuration table - N/A
| 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
Performance Consideration
Error Handling
Testing
How to Test
Test Conditions and Expected Results
Test Considerations/Dependencies
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 |
|---|---|---|---|