List of application role + menu role and explanation if we have several applications role with specials rules.
|
List of authorization objects mandatory for the application.
|
DSOs / aDSO
Cubes
WP1:
Multi Providers / Composites Providers
WP1:
PF1:
Main Master Data
Main Extractors


Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
Template Application name DataFlow
Transformation: 0FI_AA_11 -> DSO_FAA1
Start routine: extraction from master data C_ASSET in internal table itb_asset in function of fields from package (c_compcde, c_at_main, c_asset, dato).
Field routine: 0PLANT is determined with a look up in itb_asset with source field fields BURKS (company code), ANLN1 (C_AT_MAIN) and ANLN2 (C_ASSET). If correspondance found in intenal table, take the plant if not, plant is empty.
Transformation: DSO_FAA1 -> DSO_FAA2
Start routine: Is ource fields, we have two type of key figures '("TR" and "YR"). In function of the Asset Transaction Type (transtype) we assigned the differents key figures in one target to have in result fields only "TR" key figures.
If transtype = 'CUM' we assigned the "YR" key figures in "TR" key figures, example: <source_fields>-acq_val_tr TO wa_trans-cacq_vl_yr.
If transtype = 'PNL' we keep the assignation "TR" → "TR", example: <source_fields>-acq_val_tr TO wa_trans-acq_val_tr.
Transformation: DSO_FAA1 -> DSO_FAA3
Start routine: take only source data where transtype <> 'PLN'.
Check if for each record a period exists, if not calculate the period.
Same principle as Transformation: DSO_FAA1 -> DSO_FAA2, we regroup different key figures in same key figures "TR" but here not in function of TRANSTYPE but FISCPER.

Transformation: 0FI_AA_12 -> DSO_FAA3
Start routine; Check if for each record a period exists, if not calculate the period.
extraction from master data C_ASSET in internal table itb_asset in function of fields from package (c_compcde, c_at_main, c_asset, dato).
Field routine: 0PLANT is determined with a look up in itb_asset with source field fields BURKS (company code), ANLN1 (C_AT_MAIN) and ANLN2 (C_ASSET). If correspondance found in intenal table, take the plant if not, plant is empty.
Transformation: DSO_FAA1 -> CUB_FAA1
Start routine; extraction from master data C_ASSET & C_AT_AFAB in internal table itb_asset & itb_afab in function of fields from package (c_compcde, c_at_main, c_asset, (dato & datefrom for C_ASSET)).
Field routines:
0ASSET_CLAS: field "asset_clas" determined with a look up in itb_asset with source field fields COMP_CODE, C_AT_MAIN and C_ASSET.
0CHRT_ACCTS: field " chrt_accts" determined with a look up in itb_afab with source field fields COMP_CODE, C_AT_MAIN, C_ASSET and C_AT_AFAB.
0BALSHA_APC: field " balsha_apc" determined with a look up in itb_afab with source field fields COMP_CODE, C_AT_MAIN, C_ASSET and C_AT_AFAB.
0CO_AREA: field "co_area" determined with a look up in itb_asset with source field fields COMP_CODE, C_AT_MAIN and C_ASSET.
C_COSTCTR: field "c_costctr" determined with a look up in itb_asset with source field fields COMP_CODE, C_AT_MAIN and C_ASSET.
Key figures:
0INV_SUP_TR = INV_SUP_TR + VA_INVS_TR
0ORD_DEP_TR = ORD_DEP_TR + VAW_ODP_TR
0RES_TRF_TR = RES_TRF_TR + VAW_AVR_TR
REVAL_TR + VA_RAPC_TR = REVAL_TR + VA_RAPC_TR
0REV_ODP_TR = REV_ODP_TR + VA_RODP_TR
0SPC_DEP_TR = SPC_DEP_TR + VAW_SDP_TR
0UPL_DEP_TR = UPL_DEP_TR + VAW_UDP_TR
Transformation: DSO_FAA2 -> CUB_FAA2
Start routine; extraction from master data C_ASSET & C_AT_AFAB in internal table itb_asset & itb_afab in function of fields from package (c_compcde, c_at_main, c_asset, (dato & datefrom for C_ASSET)).
Field routines:
0CHRT_ACCTS: field " chrt_accts" determined with a look up in itb_afab with source field fields COMP_CODE, C_AT_MAIN, C_ASSET and C_AT_AFAB.
0BALSHA_APC: field " balsha_apc" determined with a look up in itb_afab with source field fields COMP_CODE, C_AT_MAIN, C_ASSET and C_AT_AFAB.
0CO_AREA: field "co_area" determined with a look up in itb_asset with source field fields COMP_CODE, C_AT_MAIN and C_ASSET.
C_COSTCTR: field "c_costctr" determined with a look up in itb_asset with source field fields COMP_CODE, C_AT_MAIN and C_ASSET.
RSDS 0FI_AA_12 PF1_020 -> ADSO APFIAA04
Start routine: extraction from master data C_ASSET2 in internal table LT_C_ASSET2 in function of fields from package (c_compcde, c_at_man2, c_asset2, dato = 99991231).
Field routine: C_MGN_ACC is determined with a look up in LT_C_ASSET2 with source field fields BURKS (company code), ANLN1 (C_AT_MAN2) and ANLN2 (C_ASSET2). If correspondance found in intenal table, take the C_MGN_ACC.
0FIAA_SIM : equal source field SIM only if he is not equal to 'N'.
ADSO APFIAA04 -> ADSO ABFIAA05
Field routine: C_RECONTR = C_RECONTR from master data C_ASSET2 in function of company code, c_at_man2 and c_asset2.
Calmonth, calquarter... determined in function of fiscal period.
RSDS 0FI_AA_11 PF1_020 -> ADSO APFIAA02
Start routine: extraction from master data C_ASSET2 in internal table LT_C_ASSET2 in function of fields from package (c_compcde, c_at_man2, c_asset2, dato = 99991231).
Field routine: C_MGN_ACC is determined with a look up in LT_C_ASSET2 with source field fields BURKS (company code), ANLN1 (C_AT_MAN2) and ANLN2 (C_ASSET2). If correspondance found in intenal table, take the C_MGN_ACC.
EVALGROUP5 is determined with a look up in LT_C_ASSET2 with source field fields BURKS (company code), ANLN1 (C_AT_MAN2) and ANLN2 (C_ASSET2) and dateto = 99991231 If correspondance found in intenal table, take the evalgroup5.
ADSO APFIAA02 -> ADSO ABFIAA06
Field routine: C_RECONTR = C_RECONTR from master data C_ASSET2 in function of company code, c_at_man2 and c_asset2.
Calmonth, calquarter... determined in function of fiscal period.
In calculation view CV_FIAA_CPFIAA04 (used in CPFIAA04) an union is done with DSO_FAA3 & DSO_FAA1, another union is done between ABFIAA05 & ABFIAA06. Then another union is done with the two previous unions.
| Multi Provider / composite | Query name | Description |
|---|---|---|
| CPFIAA04 | BW_QRY_CPFIAA04_0001 | FIAA - WP1/PF1 Detailed Eval. Accounting Grid - Posted dep. |
| MPR_FAA2 | BW_QRY_MPR_FAA2_0001 BW_QRY_MPR_FAA2_0003 BW_QRY_MPR_FAA2_0004 BW_QRY_MPR_FAA2_1001 BW_QRY_MPR_FAA2_1002 BW_QRY_MPR_FAA2_1003 BW_QRY_MPR_FAA2_1004 | FIAA Asset History Sheet (for Dep) FIAA Asset Balance (S_ALR_87011963) (Core) FIAA AuC not yet brought into service (Core) FIAA Balance Sheet by Flow (WB & BD) FIAA Acquisition by CGU and Sites (WorkB) FIAA Fixed Assets Closing Bal. by CGU (BroadC) FIAA Detailed Evaluation Accounting Grid (Core) |
| MPR_FAA4 | BW_QRY_MPR_FAA4_1002 BW_QRY_MPR_FAA4_1004 BW_QRY_MPR_FAA4_1005 BW_QRY_MPR_FAA4_1007 BW_QRY_MPR_FAA4_1011 BW_QRY_MPR_FAA4_1013_WBK_RSA BW_QRY_MPR_FAA4_1014 BW_QRY_MPR_FAA4_1015 BW_QRY_MPR_FAA4_1016 BW_QRY_MPR_FAA4_1018 BW_QRY_MPR_FAA4_1019 | FIAA FC L6710 Acqui. by CGU and Sites (Core) FIAA Detailed Eval. Accounting Grid - Posted dep. (WorkB) FIAA AuC not yet brought into service (Core) FIAA Five-yearly Inventory Report (Core) FIAA FC L3005 Bal. Sheet by Flow (WorkB) FIAA FC L6720 Fixed Assets Closing Bal. CGU RSA (WorkB) FIAA Report Insurance Values (Core) FIAA FC L3005 Bal. Sheet by Flow - Posted dep. (Core) FIAA FC L3005 Bal. Sheet by Flow - Planned dep. (Core) FIAA FC L6720 Fixed Assets Closing Bal. by CGU - Planned dep FIAA Detailed Evaluation Accounting Grid - Planned (Core) |
Queries role menu

Workbooks role menu

There is a process chain BD_AAC - Asset Accounting Broadcast that is responsible to to run the list of broadcasts below → process chain not scheduled since 2013 (at 09/25/2023)
For instance, variant L3005_J3_ZFR3
Schedule
There is no schedule for FIAA workbooks.
The setting below is empty.
Data Loading
Detail of process chain, list + link between or special event done for the loading
| Main Process Chain | Final Provider Loading | Frequency | Time start | Duration |
|---|---|---|---|---|
| PC_FIAA |
| Daily (not the week-end) | arround 1:15 am | 10 mins |
Data come from SAP system. To compare data between BW and sources systems, check propagation layers.
<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)>
<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>
<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)>
<Describe how to handle errors (eg. error codes, description and respective resolution, alert users)>
<List the existing bugs, its criticity, workarounds and resolution plan.>
<List past & future evolutions for the application (including links to MED/FSD/TSD)>