Overview 

In order to manage authorization of BW data, we start to use C_AUTHMA (Scope) attribute of master data to manage the authorization of Carve out in BW from PAX project. 

As we have following authorization objects (this document managed by authorization team) to control all applications, therefore, we need to add C_AUTHMA into the following master data as attributes:

In all BW sensible applications, the GBU + company code or/and plant or minimum GBU as added as authorization objects to split the data to follow the authorization rules.

GBU

See the wiki page about it.

GBU Master data

How to update authorization scope (Version 2)

1. At the moment, we need to update the authorization scope to 3 companies objects (C_COMPCDE, 0COMP_CODE, and C_COMPPRS) by flat file 

            1.1 Modify scope in flat file. The format of the file is here  (can change only impacted companies)

            1.2 We have to  upload these files by program SE38 : ZBW_FILE_TRANSFERT to

Logical path = Z_C_AUTHMA = /exploit/BW/authorization_scope/

C_COMPCDE    <- DTS_AUTH_C_COMPCDE    (file Z_C_COMPCDE_C_AUTHMA = C_COMPCDE_Auth_MA.csv)

0COMP_CDOE <- DTS_AUTH_0COMP_CODE (file Z_0COMP_C0DE_C_AUTHMA = 0COMPCDE_Auth_MA.csv)

C_COMPPRS    <- DTS_AUTH_C_COMPPRS     (file Z_C_COMPPRS_C_AUTHMA = C_COMPPRS_Auth_MA.csv)

           1.3 Update global filter

                1.3.1  Excepted plant,  in case we Solvay sold a company but some plant still belong to Solvay, we need to add this exception in global filter

Note: C_PLANT, we need to have first 3 characters of source system as well while 0PLANT does not need

               1.3.2 Impacted company, we can specific company to reload in order to speed up the reload all master data.

               1.3.3 Impacted plant, we can specific plant to reload in order to speed up 

Note: point 1.3.2 and 1.3.3 are required to set flag "Global Filter Active" as "N" or delete it after reload completed

              1.3.4 Check with authorization team that the new roles are assigned to the impacted users already

              1.3.5 Run process chain PC_C_AUTHMA it will update all master data attributes 

How to update authorization scope (Version 3)

This will be automatic by getting new field from PF1_050.  This is plan.  Will review the plan again after M2C project in Oct 2021 

Important document

Main control carve out files starting from 2021

And google doc for all new Merge, Acquisition and divestment :

Important document about PAX project :

https://docs.google.com/presentation/d/1_beONorj0VAheuAB51zvyqGXgINvQuQVa29XbLYINsU/edit#slide=id.g5c4c209cf1_0_7

8095 PAX, EIRENE & JV - Structures (official)

Work done on the data for PAX

https://drive.google.com/file/d/1-rsOfQeTinaGLwPtk50x14QoaCZ4vb33/view?ts=5c0532ff

Documentation shared to BASF, Alsachimie and Domo

https://sites.google.com/a/solvay.com/pax-program/tsa

Values about scope of PAX

The scope is linked to plant and company code, for any new dev it should be integrated

Rules about the company code :

Contacts :

The main contact for SBS is caroline.mathieu-stoissich@solvay.com  about all divestiment or merge 

The main contact for SBS about PAX is maria.pasquale@solvay.com