You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »




PO2 - BW - Authorization scope



Definition


The Authorization scope (technical name = C_AUTHMA) is a field that is used in BW to segregate authorization depending on the user profile. 

Until D1, all Solvay users have by default access to all company codes SOLVAY 

From D1, ECO users will only have access to the data of the legal entities ECO and SCO users to the legal entities SCO

Only users working for the TSA will have access to the data of the legal entities ECO and SCO.


Overview of changes 


  • Before D1, all companies are assigned to the scope SOLVAY and all BW users in SOLVAY can access the data of a company in the scope SOLVAY
  • After D1, each company is assigned to the scope ECO or to the scope SCO
  • A user working for ECO can only access the data of the scope ECO and a user working for SCo can only access the data of the scope SCO. 


Illustration 



Company 1, 2 & 4 are in the scope ECO after D1

Company 3 is in the scope SCO after D1


User E is working for a GBU ECO (ex: Soda Ash), after D1, he will only have access to the scope ECO. He can not see anymore the data of the company 3. 

User S is working for a GBU SCO (ex: Novecare), after D1, he will only have access to the scope SCO. He can not see anymore the data of the company 1,2 & 4. 

User G is working for the Global Business Services. As part of the TSA, he will have access to the scope ECO and SCO


BW - How to fill the prompt with the new scopes ?


When you open a BW report, you need to fill the prompt

It is mandatory to enter a scope in the field "Auth Scope" otherwise you get the message "No applicable data found" when you run your report. 

Normally the field is updated by default with your authorization profile. 


Before D1

The authorization scope = SOLVAY for all users in Solvay


After D1

The authorization scope SOLVAY doesn't exist anymore and must be replaced by the new authorization scope ECO, SCO or ECO & SCO depending on the user. 



BW - No data applicable


You run the report and you have the message "No applicable data found"

=> You probably run the report with an inconsistent perimeter

Illustration 



User E is working for a GBU ECO and enters SCO in the prompt

=> There will be an error message "No applicable data found"

=> He must replace the authorization scope SCO by ECO





User S is working for a GBU SCO and enters ECO in the prompt

=> There will be an error message "No applicable data found"

=> He must replace the authorization scope ECO by SCO





User G is working for the Global Business Services. He enters ECO in the prompt + a GBU SCO (ex: CS Novecare)

=> Even if he has access to both scopes ECO and SCO, there will be an error message "No applicable data found"

=> He must replace the authorization scope ECO by the scope of the GBU = SCO



BW - Historical data


Some companies are splitted in 2, in order to separate businesses when they are related to 2 different scopes in a single company (carve out process)

Illustration : ZFR3 - Rhodia Operation


  • Before D1, there are ECO & SCO businesses in the company Rhodia Operation (ex: Silica (ECO) & Novecare (SCO)) 
  • On D1, SCO businesses are carved out in a new company 6422

The user E who is working for a GBU ECO will keep the access to Rhodia Operation including historical data. 

The user S who is working for a GBU SCO will have access to the new company code 6422 & the historical data of Rhodia Operation for his GBU only. 

The user G who is working for the Global Business Services will keep the access to all GBUs in Rhodia Operation and will have access to the new company 6422. 



Related contents



  • No labels