Skip to Content
author's profile photo Former Member
Former Member

In BW 3.5 - Making an Customer Auth Obj and Organizational Item


We are running a very old BW 3.5 system. We have need to take a Customer Created Authorization Object and raise it to an Organizational Level so it can be used in roles that follow a Template-Derived role pattern. I know how this is done on the ECC side, but I am having issues replicating the process on the BW side.

Does someone have experience with this? If so, can you tell me the difference between ECC and BW? I am sure I am missing something on the BW side.

Thank you.


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 11, 2013 at 08:33 PM

    You cannot promote Auth Objects to org. levels. You can only promote fields. That then applies to all objects which use the field.

    If you also have a custom field and the org.field create program is not available to adjust SU24 and roles, then you can maintain the USORG table with the field as it does not affect anything (except perhaps test roles).

    But using derived roles has more disadvantages than just this. I have always regretted it when I became tempted to use them.

    Perhaps you can explain where you are using your custom object and what it is controlling access to which does not have a standard object for it and "old concept" reporting field for?

    Also: is a release upgrade planned? With the new BW reporting concept you have much more flexibility.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Rich,

      Based on your latest reply, Please try to create a new customized authorization object by using t code RSSM instead of using SU21.

      Here Salesorg field is by default Organizational field.

      Steps to create BW Auth objects.

      1. Please make sure characteristic value (0salesorg) is authorization relevant or if not make that one as "Authorization Relevant" under Business Explorer tab of RSD1 t code.

      Note: if you are using customized sales org by copying standard characteristic value of Salesorg then make sure to maintain that value as Auth Relevant.

      2. Go to RSSM and Specify the name of Customized auth object and click on create.

      3. Select the sales org char value from right hand side pane and move it to left hand side.then save the Object.

      4. Add the newly created auth object in to required roles then Sales org field by default will be appeared as organizational field from there you can derive the as per your requirement.

      I hope this will helps to your requirement.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.