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
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