...
| Panel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
| Panel | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
Link to the BW Catalog of role https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I
|
...
Solstice Google Drive document
MVCOPA01
P&L
WP1
Updated dataflow after Solstice update (Rules are unchanged except for the Solstice split)
...
Last change : PO2 Project 08/2023
Non ERP
PQ1
PQ1 flows are kept only for historical data, they are replaced by PF1 flows since 01.2018.
PF1:
CPCOPA03
More details here.
...
-c_tecpct2 (reference c_tecpctr) - Technical Profit Center:
This object is used to determine dynamically the organisational structure (activity1, GBU...).
It follows the business rules in COPA, these rules have changed after SPS project and the old model technical MD, c_techba, is now used for historical data only (before 2018).
cf. part "8.7 Organisation structure" of the specification document: https://drive.google.com/open?id=1lBBAR1mIJpdyw-RHrglgSSGm14uY1J1Whx9-j0k5jZ8/file/d/19tbW1LlskpgOQHslJAH1Aby85wZYjmRsKc6BBtE5SVM/view
The entries in this MD are generated only by the SID generation in transactional flows then transformation from the MD to itself determines the attributes.
-c_techpac - Technical Part Activity:
This object is used to determine dynamically the partner organisational structure.
It follows the business rules in COPA, these rules have changed after SPS project and the old model technical MD, c_techpba, is now used for historical data only (before 2018).
cf. part "8.8 Partner Organisation structure" of the specification document: https://drive.google.com/open?id=1lBBAR1mIJpdyw-RHrglgSSGm14uY1J1Whx9-j0k5jZ8/file/d/19tbW1LlskpgOQHslJAH1Aby85wZYjmRsKc6BBtE5SVM/view
The entries in this MD are generated only by the SID generation in transactional flows then transformation from the MD to itself determines the attributes.
...
-c_tgbr5:
This object is used to determine dynamically the GBR axis.
cf. specifications: https://drive.google.com/open?id=18IyjGuveYkJ0hnnCT2YfpjjL3lf0BvpkCxlSL3NLzScfile/d/1AL5UzU3oIFqyzMAwU9Dv6Ko6SNWQcF6Z992nB5WxhAU/view
The entries in this MD are generated only by the SID generation in transactional flows then transformation from the MD to itself determines the attributes.
...
- customer_master_data.csv
- material_master_data.csv
- non-erp_data.csv
Example of user manual to upload non-ERP file
Dataflow :
https://docs.google.com/presentation/d/1fmDajNiJ7SF12m8K_ytJgScvxoaMmcEnUCVP7-S1d8w/edit
...
The file loaded in WBP was stored the following directory: https://drive.google.com/drive/folders/1CxIL3OR68e3DGFi6a3SFxY3eOfGm0nbK1sPk5Jh8nJBNVeYIV2dX2yOB23XDQGjyU
GBU: the GBU in the reporting is the attribute of c_techba. The GBU stored in the DSO from the Business transformation layer is also the attribute of c_techba (replaced between propagation and business layer) and not the GBU from PQ1 which is linked to the business area in ZZCONACT.
...
2: Company is not LER and Plant is Trading Plant
3: Company is not LER
The list of companies is managed in Global filter master data C_GLBFILT manually or by flat file:
...
To have more details about Z_LER_RULES, there is a dedicated document about it:
https://drive.google.com/open?id=1-54NzGz63dagA-UyyIIoNgK8fwmzo-e-YAnASxInwjofile/d/1AXQaMXmP4AdN9FeP8eByaRVQqDgs59BJBPL3NxSAhfc/view
1) determine where the program is sued to be able to select the data from corresponding dso:
...
If c_fieldn = QUANTITY (standard case): we pick data from ODS_PCP4
If necessary, we convert quantitites and amounts with module functions: 'Z_CONVERT_CURRENCY' with type of rate CAR3 + 'Z_MD_CONVERT_MATERIAL_UNIT_F'
And we calculate new value fields:
If no records are found in ODS_PCP4, we determine value fields from source DSO
...
All the reporting is available throught workbooks in the role "PL - P&L Reporting" ZR_RCS_CA_M12
Query documentation:
https://drive.google.com/adrive/solvay.com/folderview?id=0B-qbTutzOfcHNjRBa2p0UjNZZ1E&usp=sharing_eid&ts=57514e3bfolders/1pFQ_tfTUYK1xEz4-cz0JFel7arKyY7Nn?usp=drive_link
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0vENc8kM25OfmJzOTNoeFBpdm1vVGhHLUlaX1E0UElkSEJNaGdsRkVGUy1YUGpUdUdkOUU19pPWUmAkTcW1aYlzlqyHOxvL6JfDdaKe
https://drive.google.com/open?id=0B_p_Afe8sjVlN1J3YzYzdE8taDg/drive/folders/1zF0862L7nRnu39MXdtVORT-HkmHavs-R
https://drive.google.com/open?id=0B_p_Afe8sjVlTEVnc3NjdDV5U0U https://drive.google.com/drive/folders/0B0vENc8kM25OfjZybWxDdnlHQ0VCNnlHTFZYNHVycmpZZU1Ia2dNUlJtWkZHbmx5SG9nRTA1miRFX_LJKQ5YGWq-r3-YETCNkZcRhLvy
https://drive.google.com/drive/folders/1xY6QOu8gmrvmyncdpSu5trUA5SQIliRX
https://drive.google.com/drive/folders/1rzUHdVecCOROXOkZBpp7uhbHNJqIc63Y1fZQwSGmRV3IuB1DlBf92ASEYatiSYNF6
Main queries
There are several queries but the main ones are:
...
All queries use structures for key figures. There are many key figures, using calculated and restricted key figures inside.
Main functionnalities: Jump query available
...
Data come from SAP system. To compare data between BW and sources systems, check propagation layers.
Table KE30 can valid with P&L on non-console view.
Table CE1+ Operating concern in the source should be the same value as Propagation layer of COPA data.
Operational Documentation
...
P&L : Non ERP transaction
https://drive.google.com/open?id=1gF426ok7VvnF1-idij_FCsMt7HMYQuY4LiN34CseSZs/file/d/1Mqb9wnFqnp2tl6j4AFKbWjm6BnDGSxPTQJHyOYvwspQ/view
P&L : Time reference for CICC and GM flat files
https://drive.google.com/open?id=1cqPl_gkWdFubpTRyxbSaJtsa4iv8m4uH-bRT8dGOyoYfile/d/1EoZAjLveLXL2wASs1m-l1D8LO8l28y5A_Jze6sO-bS4/view
IM: Delta + full load of current and previous months.
Program for LER determination
https://drive.google.com/open?id=1pEJTKs37dEloE7HGiY9lVsPf0crLoxxbzVN9oN33cr8/file/d/1VnOB0-jeV85c6kJYram-fuIh70U3gWU7LHiTHtB8e0I/view
https://docsdrive.google.com/spreadsheetsfile/d/1jVkZGYuzpfkIfGY1Ob1AOMNQrhtNnO11xrquBBzAI3w/edit?usp=sharing12hYsIOncEYpMI6aeOtjZtIHS3o2-GCLnnCZiKzJOUiU/view
Program for LER info providers
https://drive.google.com/open?id=1-54NzGz63dagA-UyyIIoNgK8fwmzo-e-YAnASxInwjo/file/d/1AXQaMXmP4AdN9FeP8eByaRVQqDgs59BJBPL3NxSAhfc/view
Scheduling
<Describe the scheduling in place for the application (eg. existing jobs, trigger time/event based, dependencies)>
...
<List the existing bugs, its criticity, workarounds and resolution plan.>
Roadmap
Todo list: https://drive.google.com/open?id=1GVVKIEbmSyeZx2lke4kmLg5MWHhjgsjka_7ewLcNGsY/file/d/1cvHfPpBByAQnYIZUZpvMkwFQmgmGESkSdrQrBhcTz9s/view