Access Management
This Colmar application will use composite roles, which contain many roles inside below
Composite Role | Role Name | M44 | M441 | A10 | A11 | A12 | A13 | A14 | A15 | A16 | A17 | A18 | A19 | A20 | M09 | ZBI_RCS_CO_A21 | ZBI_RCS_PS_A02 | ZR_TOUT_CA_P01 | ZR_TOUT_CA_P04 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ZC_RCS_COL_C01 | COLMAR - Administrator | X | X | X | X | X | X | X | X | ||||||||||
ZC_RCS_COL_C02 | COLMAR - IT Admin | X | X | X | X | X | X | X | X | X | |||||||||
ZC_RCS_COL_C03 | COLMAR - GBU Coordinator | X | X | X | X | X | X | X | X | X | X | ||||||||
ZC_RCS_COL_C04 | COLMAR - Reporting Plant | X | X | X | X | X | X | X | X | X | |||||||||
ZC_RCS_COL_C06 | COLMAR - Forecaster | X | X | X | X | X | X | X | X | X | X | X | X | ||||||
ZC_RCS_COL_C06_PAX | COLMAR - Forecaster - For PAX | X | X | X | X | X | X | X | X | X | X | X |
Auhtorization variables on queries are based on info objects: C_BFCA_4, C_MA_PR__C_BFCA_4, C_PLANT, C_COMPCDE and C_FAMINPR.
C_AUTHMA variables are customer exit variables.
For Colmar application, authorization objects will be in application roles.
History: 2023: To segregate data of Po2, authorization scope (C_AUTHMA) has to be added into project bundle (C_MA_PR). It is required to modify web portal, authorization application role, C_MA_PR object and BW querie
| Role | Role Name | Auth Obj | Family (C_MA_PR__C_FAMINPR) | GBU (C_BFCA_2__C_BFCA_4) | C_COMPCDE | Plant | Provider | C_AUTHMA (For Po2) |
| ZR_RCS_PS_A10 | RPSA10 - COLMAR - Forecast - Technical role | |||||||
| ZR_RCS_PS_A11 | RPSA11 - COLMAR - Reporting - Technical role | |||||||
| ZR_RCS_PS_A12 | RPSA12 - COLMAR - Data entry - Data scope | Z_IP_002 | $V_C_FAMINPR_32 | $V_C_BFCA_4_32 | All | $V_C_PLANT_32 | See provider sheet | $V_C_AUTHMA_32 |
| ZR_RCS_PS_A13 | RPSA13 – COLMAR - Data entry - Data scope - All | Z_IP_004 | All | All | All | All | See provider sheet | All |
| ZR_RCS_PS_A14 | RPSA14 – COLMAR - Reporting - Data scope | Z_IP_003 | $V_C_FAMINPR_33 | $V_C_BFCA_4_33 | All | $V_C_PLANT_33 | See provider sheet | $V_C_AUTHMA_33 |
| ZR_RCS_PS_A15 | RPSA15 – COLMAR - Reporting - Data scope - All | Z_IP_005 | All | All | All | All | See provider sheet | All |
| ZR_RCS_PS_A16 | RPSA16 – COLMAR - Display Master Data | Z_IP_006 | $V_C_FAMINPR_33 | $V_C_BFCA_4_33 | All | $V_C_PLANT_33 | See provider sheet | $V_C_AUTHMA_33 |
| ZR_RCS_PS_A17 | RPSA17 – COLMAR - Administrator master data maintenance | Z_IP_007 | $V_C_FAMINPR_32 | $V_C_BFCA_4_32 | All | $V_C_PLANT_32 | See provider sheet | $V_C_AUTHMA_32 |
| ZR_RCS_PS_A18 | RPSA18 – COLMAR - GBU dedicated master data maintenance | Z_IP_007 | $V_C_FAMINPR_32 | $V_C_BFCA_4_32 | All | $V_C_PLANT_32 | See provider sheet | $V_C_AUTHMA_32 |
| ZR_RCS_PS_A19 | RPSA19 – COLMAR - Trans GBU master data maintenance | Z_IP_007 | $V_C_FAMINPR_32 | $V_C_BFCA_4_32 | All | $V_C_PLANT_32 | See provider sheet | $V_C_AUTHMA_32 |
| ZR_RCS_PS_A20 | RPSA20 - COLMAR - Data online entry - Data scope | Z_IP_001 | All | All | All | All | All | |
| ZBI_RCS_CO_A21 | CBS Project costs Reporting Analysis - End User role | ZBI_CBS_PC | All | All | All | All | AREA_F_CO_CBS_PS | |
| ZBI_RCS_PS_A02 | Project Costs and Structures Analysis - End User role | ZBI_PS | N/A | N/A | All | All | CUB_WBS6 AREA_PSCO |
The application role will use class (user exit) to get the perimeter value of authorization objects, which get value from DSO DPIPCO15. This DSO is updated in Colmar Portal by Francois.
The application role will use class (user exit) to get the perimeter value of authorization objects, which get value from DSO DPIPCO15. This DSO is updated in Colmar Portal by Francois.
Variable detail gets from SM30 - ZBIU001_V_VAR
Display class = SE24 - ZCL_BIU001_COLMAR_AUTH.
A New Variable V_C_AUTHMA_39 to extract the User specific authorisations ECO/SCO from the DSO DPIPCO15. This varaible is visible for User to modify and input values on authorisation
scope (ECO/SCO). This will help users to restrict the data in queries BW_QRY_MVIPCO02_0001 and BW_COLMAR_MVIPCO17_0001.
However, the normal perimeter roles such as Plant if it is assigned to a Colmar user as well, it will combine the access with the DSO DPIPCO15
For example, user KLMLUNG has authorization only for Novecare GBU and 2 plants 0263 and 0269 in the DPIPCO15 but he also have role ZR_RCS_CA_P02 to access all plants
As a result of this, he can access all plants with in Novecare GBU (CS) for BW query but this user can see the project only 2 plants in the Colmar portal
DataFlow
Overview
The differents providers are loaded with webdynpros:
Objective of the application
COLMAR = C apex O verall L ifecycle M anagement A pprovals and R eporting
COLMAR is a tool to follow and forecast industrial projects for all GBU.
Tool Leader + IT leader of the application: francois.carette@solvay.com
Main functionalities
Documentation here
https://drive.google.com/drive/folders/1SvrJBD9ZKyKZm9rKjmiNM0Q_4ld44f6G
https://sites.google.com/a/solvay.com/colmar/home
Technical Rules on Workbench
Explanation for the process on the technical side. Can be specific cases or general rules depending on the scope.
Reporting
Main queries
| Query | Description |
|---|---|
| BW_QRY_MVIPCO02_0001 | Mass Upload - Transactional data |
| BW_QRY_MVIPCO02_0003 | COLMAR - Family of Inv Proj. - List - Mass upload |
| BW_QRY_MVIPCO03_0004 | Forecasts - Summary data |
| BW_QRY_MVIPCO03_0001 | Forecasts follow up |
| BW_QRY_MVIPCO03_0002 | Project exeeding auth. Amount |
| BW_QRY_MVIPCO03_0003 | Actual CAPSPEND - CAPEX detail |
| BW_QRY_MVIPCO03_0005 | Quarterly switch control |
| BW_QRY_MVIPCO03_0007 | Reporting - Company Currency |
| BW_QRY_MVIPCO03_0008 | Forecast version comparison VS active |
| BW_QRY_MVIPCO03_0009 | Reporting - Euro |
| BW_QRY_MVIPCO03_0010 | Reporting - Company Code JV |
| BW_QRY_MVIPCO03_0011 | Reporting - Euro JV |
| BW_QRY_MVIPCO03_0013 | COLMAR - CAPSPEND Follow Up |
| BW_QRY_MVIPCO03_0014 | COLMAR - CAPEX Follow Up |
| BW_QRY_MVIPCO03_0012 | COLMAR - Auth. Amount Follow Up |
| BW_QRY_MVIPCO03_0015 | Check Actual for Non PS project |
| BW_QRY_MVIPCO10_0001 | COLMAR Plant List |
| BW_QRY_MVIPCO04_0001 | BFC Activity 1 - list - mass upload |
| BW_QRY_MVIPCO04_0002 | BFC Activity 2 - list - mass upload |
| BW_QRY_MVIPCO04_0003 | Sub Axis 1 - list - mass upload |
| BW_QRY_MVIPCO04_0004 | Sub Axis 2 - list - mass upload |
| BW_QRY_MVIPCO04_005 | COLMAR - Plant/BFC/Valstream/logsys - list |
| BW_QRY_MVIPCO04_006 | COLMAR - Plant/BFC/Valstream/logsys - list2 |
| BW_QRY_MVIPCO04_007 | COLMAR - Value Stream - list |
| BW_QRY_MVIPCO08_0001 | COLMAR : Projects not saved nor validated on active version |
| BW_QRY_MVIPCO08_0002 | COLMAR : Projects not saved nor validated on active version |
| BW_QRY_MVIPCO12_0001 | Plant Enveloppe definition |
| BW_QRY_MVIPCO11_0002 | GBU Enveloppe follow up |
| BW_QRY_MVIPCO11_0001 | Plant Enveloppe follow up - Company Curr - Not JV |
| BW_QRY_MVIPCO11_0004 | Plant Enveloppe follow up -EUR - not JV |
| BW_QRY_MVIPCO11_0005 | Plant Enveloppe follow up -EUR - JV |
| BW_QRY_MVIPCO11_0003 | Plant Enveloppe follow up - Company Curr - JV |
| BW_QRY_MVIPCO13_0001 | COLMAR - Family Of Inv. Project |
| BW_QRY_MVIPCO14_0001 | COLMAR - Budget version creation control |
| BW_QRY_MVIPCO04_0011 | BW - COLMAR - Plant/BFC/Valstream/logsys - list (Core Query) |
| BW_QRY_MVIPCO04_0012 | BW - COLMAR - Plant/BFC/Valstream/logsys - list2 (Core Query |
| BW_QRY_MVIPCO04_0013 | BW - COLMAR - Value Stream - list (Core Query) |
| BW_COLMAR_MVIPCO17_0001 | BW COLMAR - Forecast Data (Core Query) |
| BW_COLMAR_MVIPCO17_0006 | BW - COMAR - PS Project Creation (Core Query) |
| BW_COLMAR_MVIPCO17_0007 | BW COLMAR - CarryOver (Core Query) |
| BW_QRY_MVIPCO04_0015 | BW - COLMAR - Plant/BFC/Valstream/logsys - list4 (Core Query |
| BW_QRY_MVIPCO04_0014 | BW - COLMAR - Plant/BFC/Valstream/logsys - list3 (Core Query |
| BW_COLMAR_MVIPCO17_0008 | BW - COLMAR - PS Project Status Update (Core Query) |
| BW_COLMAR_MVIPCO17_0009 | BW - COLMAR - PS Project Budget Update (Core Query) |
| BW_COLMAR_MVIPCO17_0005 | BW COLMAR - Forecast Data (Core Query) with validation filte |
| F_MVIPCO19_001 | COLMAR Forecast Data Entry |
| BW_QRY_MVIPCO19_0001 | Forecasts - Summary data |
It is in menu role ZR_RCS_CA_M44:
Broadcast
There are some broadcasting as well but it is out of scope of BW support. The broadcasting is manage directly by Francois.
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
Detail of process chain, list + link between or special event done for the loading
| Main Process Chain | Final Provider Loading | Frequency | Time start | Duration |
|---|---|---|---|---|
META - D - COLMAR Daily loads PC_COLMAR_05 | Meta chain for PC_COLMAR_01 PC_COLMAR_04 PC_COLMAR_09 PC_COLMAR_02 | Daily | Arround 3 am | 2 hours |
TD - D - Daily backup of IP cubes PC_COLMAR_02 | DPIPCO24 DPIPCO23 DPIPCO27 DPIPCO22 DPIPCO21 CRIPCO05 CRIPCO04 | Daily | Arround 4:40 am | 10 mins |
TD - D - Actual loading PC_COLMAR_01 | C_INV_PR DPIPCO16 DPIPCO20 APIPCO34 DPIPCO06 ABIPCO01 CRIPCO03 | Daily | Arround 3:10 am | 30 mins |
TD - D - COLMAR Mass realignment PC_COLMAR_04 | CRIPCO11 | Daily | Arround 4:50 am | 25 mins |
TD - D - CRIPCO10 loading PC_COLMAR_09 | CRIPCO10 | Daily | Arround 4:40 am | 3 mins |
Data Quality Control
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
- Colmar Folder missing in Portal WBP (BPJ)
the errors we found on BPJ portal server , were indicating problem in the backend system (WBP).
Sometimes when there are temporary bottlenecks/freezes on the backend, the connection from the portal gets lost, and it's necessary to restart the portal.
==> contact : Benelux MIM Support <bmimsupp@in.ibm.com> , CSC Belgium <CSCBE@be.ibm.com> ,
==> solution : restart BPJ
Roadmap
<List past & future evolutions for the application (including links to MED/FSD/TSD)>