3 weeks ago - last edited 3 weeks ago
Dear all
there is a system set up problem with SAP user and "office key" as assigned to the SAP user. And because of this the user can not find his/her "OfficeKey" number in transaction CG54.
There seems to exist several "correction" reports as delivered by SAP (i have found i believe three different variants). But we do not know: which of the several ABAP Routines will help.
E.g. problem is like: by using the "Name" you can not find the corresponding "SO key (in CG54) But by using SE16 you find the data (and chekcing the relevant SAP tables) and if you use the SO key as identified: You can use this to dispatch the SDS
We would like to ge rid of this problem. Seems to be a "system set up" problem. Any idea?
C.B.
Request clarification before answering.
Hi C.B.
Just a hunch: did you perhaps run an auth trace? Not sure what changed and when, but it seems that C_SHER_TD2 with ACTVT = 03 is required.
Jan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello i will check this; but i would not assume an authorization problem
in relation to: https://dev-workbench.com/en/sap-dictionary/authorization-object/c_sher_td2
I can not see any dependency to the "Office User". And as mentioned: if we identify the key on data base level and the user enters the key a "dispatch" of SDS is possible.
I need to look for my notes to list here the ABAP routines we have identified so far which may help to get rid of the probelm
C.B.
PS: these two ABAP report we have found (i believe there is more like this). these reports eems to be good options for getting a solution.. but may be you have more insight?
But what is the correct approach? There as as well this transaction which i have found:
DEAR ALL PROBLEM WAS SOLVED BY USING ABAP Reports like the above ones. Inconsistency in database could be removed.
User | Count |
---|---|
87 | |
10 | |
9 | |
9 | |
7 | |
6 | |
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.