Access Management
See Technical Documentation - CAPEX Analysis report
DataFlow
Overview
Use the google presentation below as a template. This google presentation must be saved in the Reporting GDrive folder under the corresponding application. Then post the link to the document here.
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
Template Application name DataFlow
Objective of the application
The Asset Accounting (FI-AA) component is used for managing and supervising fixed assets with the SAP System. In Financial Accounting, it serves as a subsidiary ledger to the General Ledger, providing detailed information on transactions involving fixed assets. FI-AA was developed exclusively to meet IFRS16 requirements; however, it is being or will be used across Solvay for other requirements. As of 01.01.2019, the new IFRS 16 leases standard is mandatory for European IFRS balance sheet accountants in Europe. With IFRS 16, it is no longer required to treat financial and operational leases differently from an accounting perspective and therefore this new leasing standard eliminates nearly all "off-balance" sheet accounting for leases.
Technical Rules on Workbench
ECC Changes
Activated data sources 0FI_A_11 and 0FI_AA_12 from SAP standard business content in PF1 and WP1 source systems.
Data Source – Transaction Data
0FI_AA_12 contains asset period values (data comes from ANLP table)
0FI_AA_11 contains asset line items information (data comes from ANLC, ANEP, ANEA tables).
BW Changes
Info Area in BW
Creation of new info area for Propagation, BTL and Reporting objects.
ODP Source System
Not applicable as establishing ODP connection is out of scope for WP1 and PF1 is not eligible as it is not on EHP8.
Info Objects
Info object:
New info objects Calendar Year/Month (C_CALMNTH), Calendar Year/Quarter (C_CALQTR) are created.
Propagation Layer
There are two new ADSOs created in propagation layer (IA_FIAA_PROPAGATION_LAYER) from PF1 only. Propagation layer for WP1 was already developed as part of previous requirements.
FIAA: Transactions - Solvay (APFIAA02) based on 0FI_AA_11 from PF1
FIAA: Period Values - Solvay (APFIAA04) based on 0FI_AA_12 from PF1
Business Transformation Layer
There are four new ADSOs created in business transformation layer (IA_FIAA_BUSINESS_TRANS_LAYER) for both PF1 and WP1.
WP1 - FIAA: Transactions - Rhodia Level 2 (ABFIAA01)
WP1 - FIAA: Period Values - Rhodia Level 2 (ABFIAA03)
PF1 - FIAA: Transactions - Solvay Level 2 (ABFIAA02)
PF1 - FIAA: Period Values - Solvay Level 2 (ABFIAA04)
Reporting Layer
There are four new cubes created in reporting layer (IA_FIAA_REPORTING_LAYER)
WP1 - FIAA Transactions Data - Rhodia (CRFIAA01)
WP1 - FIAA Period Values Data - Rhodia (CRFIAA03)
PF1 - FIAA Transactions Data - Rhodia (CRFIAA02)
PF1 - FIAA Period Values Data - Rhodia (CRFIAA04)
Multi provider
Cubes CRFIAA01/02/03/04 are included in Multi provider (MVFICX01) and required fields are mapped as per business requirement. Please fine the below link for MP mappings.
Please find the MP mappings
Reporting
Dependencies with other applications
We should have the information where the application is sending or receiving information (e.g. APD open hub)
Data Loading
Info Providers and objects loaded
Process Chain | Code | Type | Frequency | Time start | Duration | Comments |
|---|---|---|---|---|---|---|
FI - Asset Accounting | PC_FIAA | SLAVE |
| arround 1:15 am | 10 mins |
|
Data Quality Control
Data come from SAP system. To compare data between BW and sources systems, check propagation layers.
Operational Documentation
Procedures
<Describe the recurring procedures needed to operate the application (eg. start/pause/terminate/restart the app processes, data preparation, data ingestion, ETL, data visualization, data export, other manual activities)>
Scheduling
<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>
Monitoring
<Describe the monitoring checks to confirm the application is performing well (eg. check the overall status, check performance metrics like runtime/data volume/memory/disk/CPU, maintain and react to alerts/notifications)>
Error Handling
<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>
Known Bugs
<List the existing bugs, its criticity, workarounds and resolution plan.>