on 06-08-2017 2:46 PM
Hello Experts,
Would like to seek your suggestions for below issue post Oracle upgrade,
We have a custom table for which edit access is required in Production.
In Development and Quality systems, the Edit button is available in Data browser of SE11/SE16 but the same is not available in Production.
We have option to edit via SM30 or in debug mode, but the requirement is to have edit access in SE11/SE16 itself directly.
Below are few checks done,
Questions:
1) Is TMG requires to be generated in order to have edit access in Production?
2) Who can help in enabling "Maintain entries" of SE16N?
3) Is any settings to be done from ABAP perspective?
4) Could this be an authorization issue? If so please suggest the steps to verify.
5) Is this anything to be done with setting specific to table or to be done globally?
Many Thanks for your suggestions and help!!
'the requirement is to have edit access in SE11/SE16 itself directly.' -> Fire the requester...
(SU53, S_TABU_DIS, S_TABU_NAM, S_TABU_CLI, SM30/SE54, SCC4, TRESC, delivery class, SOBJ...)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raymond,
Thank you for the clues.
1) Below is the result of authorization check in SU53 after displaying table entries,
2) As mentioned, Table maintenance dialog is not created and hence edit via SM30 is not available which is still an option.
3) With the help of SCC4, we could only have temporary edit access for limited time.
Could you please suggest for other necessary checks to have permanent edit access.
Sorry if am missing something.
Thanks for your support!
Giving SE16[n] to users is not a good idea, if you do so, you will have to insure that no "cautious" table will be allowed so manage every S_TABU* for every table/group with a generated dialog or the editable flag...
Your screenshot seems related to PFCG transaction, so better try to start a trace (with ST01) on authorization-check, execute SE16, exit, stop trace and display/analyze it it. You will get list of failed (and successful if required at ST01) authorization checks.
Did you check SU53 for an authorization objects hit in your production system?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
See Raymonds answer to the question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
9 | |
9 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.