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

RoleRole NameAuth ObjFamily (C_MA_PR__C_FAMINPR)GBU (C_BFCA_2__C_BFCA_4)C_COMPCDEPlantProviderC_AUTHMA (For Po2)
ZR_RCS_PS_A10RPSA10 - COLMAR - Forecast - Technical role






ZR_RCS_PS_A11RPSA11 - COLMAR - Reporting - Technical role






ZR_RCS_PS_A12RPSA12 - COLMAR - Data entry - Data scopeZ_IP_002$V_C_FAMINPR_32$V_C_BFCA_4_32All$V_C_PLANT_32See provider sheet$V_C_AUTHMA_32
ZR_RCS_PS_A13RPSA13 – COLMAR - Data entry - Data scope - AllZ_IP_004AllAllAllAllSee provider sheetAll
ZR_RCS_PS_A14RPSA14 – COLMAR - Reporting - Data scopeZ_IP_003$V_C_FAMINPR_33$V_C_BFCA_4_33All$V_C_PLANT_33See provider sheet$V_C_AUTHMA_33
ZR_RCS_PS_A15RPSA15 – COLMAR - Reporting - Data scope - AllZ_IP_005AllAllAllAllSee provider sheetAll
ZR_RCS_PS_A16RPSA16 – COLMAR - Display Master DataZ_IP_006$V_C_FAMINPR_33$V_C_BFCA_4_33All$V_C_PLANT_33See provider sheet$V_C_AUTHMA_33
ZR_RCS_PS_A17RPSA17 – COLMAR - Administrator master data maintenanceZ_IP_007$V_C_FAMINPR_32$V_C_BFCA_4_32All$V_C_PLANT_32See provider sheet$V_C_AUTHMA_32
ZR_RCS_PS_A18RPSA18 – COLMAR - GBU dedicated master data maintenanceZ_IP_007$V_C_FAMINPR_32$V_C_BFCA_4_32All$V_C_PLANT_32See provider sheet$V_C_AUTHMA_32
ZR_RCS_PS_A19RPSA19 – COLMAR - Trans GBU master data maintenanceZ_IP_007$V_C_FAMINPR_32$V_C_BFCA_4_32All$V_C_PLANT_32See provider sheet$V_C_AUTHMA_32
ZR_RCS_PS_A20RPSA20 - COLMAR - Data online entry - Data scopeZ_IP_001AllAllAllAll
All
ZBI_RCS_CO_A21CBS Project costs Reporting Analysis - End User roleZBI_CBS_PCAllAllAllAllAREA_F_CO_CBS_PS
ZBI_RCS_PS_A02Project Costs and Structures Analysis - End User roleZBI_PSN/AN/AAllAllCUB_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

QueryDescription
BW_QRY_MVIPCO02_0001Mass Upload - Transactional data
BW_QRY_MVIPCO02_0003COLMAR - Family of Inv Proj. - List - Mass upload
BW_QRY_MVIPCO03_0004Forecasts - Summary data
BW_QRY_MVIPCO03_0001Forecasts follow up
BW_QRY_MVIPCO03_0002Project exeeding auth. Amount
BW_QRY_MVIPCO03_0003Actual CAPSPEND - CAPEX detail
BW_QRY_MVIPCO03_0005Quarterly switch control
BW_QRY_MVIPCO03_0007Reporting - Company Currency
BW_QRY_MVIPCO03_0008Forecast version comparison VS active
BW_QRY_MVIPCO03_0009Reporting - Euro
BW_QRY_MVIPCO03_0010Reporting - Company Code JV
BW_QRY_MVIPCO03_0011Reporting - Euro JV
BW_QRY_MVIPCO03_0013COLMAR - CAPSPEND Follow Up
BW_QRY_MVIPCO03_0014COLMAR - CAPEX Follow Up
BW_QRY_MVIPCO03_0012COLMAR - Auth. Amount Follow Up
BW_QRY_MVIPCO03_0015Check Actual for Non PS project
BW_QRY_MVIPCO10_0001COLMAR Plant List
BW_QRY_MVIPCO04_0001BFC Activity 1  - list - mass upload
BW_QRY_MVIPCO04_0002BFC Activity 2  - list - mass upload
BW_QRY_MVIPCO04_0003Sub Axis 1 - list - mass upload
BW_QRY_MVIPCO04_0004Sub Axis 2 - list - mass upload
BW_QRY_MVIPCO04_005COLMAR - Plant/BFC/Valstream/logsys - list
BW_QRY_MVIPCO04_006COLMAR - Plant/BFC/Valstream/logsys - list2
BW_QRY_MVIPCO04_007COLMAR - Value Stream - list
BW_QRY_MVIPCO08_0001COLMAR : Projects not saved nor validated on active version
BW_QRY_MVIPCO08_0002COLMAR : Projects not saved nor validated on active version
BW_QRY_MVIPCO12_0001Plant Enveloppe definition
BW_QRY_MVIPCO11_0002GBU Enveloppe follow up
BW_QRY_MVIPCO11_0001Plant Enveloppe follow up - Company Curr - Not JV
BW_QRY_MVIPCO11_0004Plant Enveloppe follow up -EUR - not JV
BW_QRY_MVIPCO11_0005Plant Enveloppe follow up -EUR - JV
BW_QRY_MVIPCO11_0003Plant Enveloppe follow up - Company Curr - JV
BW_QRY_MVIPCO13_0001COLMAR - Family Of Inv. Project
BW_QRY_MVIPCO14_0001COLMAR - Budget version creation control
BW_QRY_MVIPCO04_0011BW - COLMAR - Plant/BFC/Valstream/logsys - list (Core Query)
BW_QRY_MVIPCO04_0012BW - COLMAR - Plant/BFC/Valstream/logsys - list2 (Core Query
BW_QRY_MVIPCO04_0013BW - COLMAR - Value Stream - list (Core Query)
BW_COLMAR_MVIPCO17_0001BW COLMAR - Forecast Data (Core Query)
BW_COLMAR_MVIPCO17_0006BW - COMAR - PS Project Creation (Core Query)
BW_COLMAR_MVIPCO17_0007BW COLMAR - CarryOver (Core Query)
BW_QRY_MVIPCO04_0015BW - COLMAR - Plant/BFC/Valstream/logsys - list4 (Core Query
BW_QRY_MVIPCO04_0014BW - COLMAR - Plant/BFC/Valstream/logsys - list3 (Core Query
BW_COLMAR_MVIPCO17_0008BW - COLMAR - PS Project Status Update (Core Query)
BW_COLMAR_MVIPCO17_0009BW - COLMAR - PS Project Budget Update (Core Query)
BW_COLMAR_MVIPCO17_0005BW COLMAR - Forecast Data (Core Query) with validation filte
F_MVIPCO19_001COLMAR Forecast Data Entry
BW_QRY_MVIPCO19_0001Forecasts - 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 ChainFinal Provider LoadingFrequencyTime startDuration

META - D - COLMAR Daily loads


PC_COLMAR_05

Meta chain for

PC_COLMAR_01

PC_COLMAR_04

PC_COLMAR_09

PC_COLMAR_02

DailyArround 3 am2 hours

TD - D - Daily backup of IP cubes


PC_COLMAR_02

DPIPCO24

DPIPCO23

DPIPCO27

DPIPCO22

DPIPCO21

CRIPCO05

CRIPCO04

DailyArround 4:40 am10 mins

TD - D - Actual loading


PC_COLMAR_01

C_INV_PR

DPIPCO16

DPIPCO20

APIPCO34

DPIPCO06

ABIPCO01

CRIPCO03

DailyArround 3:10 am30 mins

TD - D - COLMAR Mass realignment


PC_COLMAR_04

CRIPCO11DailyArround 4:50 am25 mins

TD - D - CRIPCO10 loading


PC_COLMAR_09

CRIPCO10DailyArround 4:40 am3 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)>