07-18-2011 10:14 AM
Hello Everyone,
When a trasport request is created for any BI analysis authorization ( including the Z*), the type of trasport request created
is workbench request. What is the reason behind this because when any Customised Role / Profile is included in transport request this will be customised request unlike analysis authorization.
Thanks in advance.....
07-18-2011 2:05 PM
Hi Rashmi,
The difference is In BI, the AA authorizations are independent. Any objects that are independent of the client will be captured in the workbench type of transport request, when they are required in the other client. Hence you can see the Workbech type request for transporting changed Repository objects and changed system settings from cross-client tables. However, customizing requests involve changes recorded to client-specific Customizing objects .
The Analysis authorizations are always captured in a Workbench type of transport request by default due to the above design.
You can still transport both the PFCG role, and AA in a single transport request, you can do the same by following the steps mentioned in the below Wiki:
https://wiki.sdn.sap.com/wiki/display/BI/HowtotranportroleandAAtogetherinBI
Regards,
Raghu
08-04-2011 5:55 AM
Hi Raghu,
thanks for the wiki link and your reply..
I totally agree with the design of workbench request and customizing request. But correct me if my understanding is wrong. Even the Analysis Authorization also hold the client specific information like the authorization-relevant info-objects details.So how can this be treated as independent.
Regards,
Rashmi
08-04-2011 7:15 AM
Hi,
Analysis Authorization also hold the client specific information like the authorization-relevant info-objects details
No.. AA will not hold the authorization relevant info objects.. The logic will only check if they are authorization relevant or not. The request holds the data from the below analysis authorization tables:
RSECHIE
RSECTXT
RSECVAL
Hope this answers your question.
Regards,
Raghu
08-04-2011 12:52 PM
AA is a different entity/object from Auth. releveant objects . It only contains the Meta-data(description) of the auth. objects and not the Auth. objects.