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
How many users? Which user category ? Is there critical period ? Which geographical perimeter? Describe in one sentence: around 50 users, worldwide or 200 users / European Site
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 queries
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 |
For Colmar application, authorization objects will be in application roles
| 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.
Variable detail gets from SM30 - ZBIU001_V_VAR
Display class = SE24 - ZCL_BIU001_COLMAR_AUTH

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

Detail of Colmar authorization
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Exemple of dataflow overview :
Template Application name DataFlow
Detail of main topics with explanations of the rules and only the main + special rules about queries to run and use in the correct way
Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...
Detail of process chain, list + link between or special event done for the loading
Detail of frequency : monthly; weekly or else
if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.
It is in menu role ZR_RCS_CA_M44
Documentation here
https://drive.google.com/drive/folders/1TibbQ_Tl69xv9m3S4syLYa-uQQ4j7je7
https://sites.google.com/a/solvay.com/colmar/home
There are some broadcasting as well but it is out of scope of BW support. The broadcasting is manage directly by Francois.

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
List recurring procedures
Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016