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

BEx Transportation question

Hi, in our project we have frontend BEx developers. They need to transport existing queries as well as new queries. they are not authorized to do anything else with the adm-workbench except display only. how is the best way to handle this beside an organizational approach which would look i.e like that:

1. existing queries:

create transport, assign transport to be bex transport with adm (this is down by backend developers)

2. new queries: (this is done also from backend developers)

adm transport connector, collect new query elements, assign development class and than proceed like 1.

What we would like to achive is an approach where we minimize the overhead for the backend developers without allowing the frontend developers to change anything in the adm.

Thx for any hints from Michael Soine

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jun 08, 2004 at 05:52 PM

    Hi Michael,

    the easiest approach could be to grant partial allowance for some awb and transport management functions, which could require a very narrow authorization profile in your case.

    To achieve a profile with the necessary authorizations only, one approach could be to do an authorization trace (ST01) for all steps which a frontend developer needs to perform in the awb.

    Best regards, Steen

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      The way we handle it is this:

      Query developers have the ability to create only ZQRY* and YQRY* names queries in DEV. Existing queries which have been transported already are automatically collected in a standard common BEx transport (<i>RSA1 -> Transport Connection -> BEx</i>) which is transported by our BW Admin (me) periodically as requested by Query Developers.

      For new Queries, we have a very simple transport request form which they fill out and the Query and associated needed objects are collected and transported by our BW Admin.

      They query developers only have the ability to create sub-tasks in transports, and they cannot release any transports. They only have read only access to RSA1 functions to allow them to better view modeling and data flow.

      Query developers don't have access to much else (well the can create web templates and workbooks as well). There is currently no overlap with front-end developement (queries and reports) and backend development and modeling users.

      - Stephen

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.