Hello Faraz,
maybe you still need the information: in the SAP note 1816989 you will find them.
Wilhelm
Hello Faraz,
maybe you still need the information: in the SAP note 1816989 you will find them.
Wilhelm
hello experts,
I have a workflow that sends notifications to the user's SAP inbox. I need to send the notifications received in the inbox of each user of SAP for their e-mail externally. I've checked that it is possible to configure the automatic transmission for a single user, being already in the user inbox, go in menu SETTINGS then USER OFFICE SETTINGS screen will open that tab AUTOMATIC TRANSMISSION and insert the address of external mail user. I know that to enter the e-mail address is necessary to register EXTERNAL COMPANIES plus CONTACT PERSONS EXTERNAL. This does not solve my problem because I need to configure the automatic sending of more than a thousand users and doing this manually is not feasible. I tried to upload from the list of e-mail through a LSMW tab AUTOMATIC TRANSMISSION, just not working but I believe that because I have not registered external companies or the PEOPLE CONTACT EXTERNAL, and found out that this tab only is allowed to configure a single e-mail outside (is that right?). I found some stuff talking about the Transaction SO16 to do this, but have not seen how to use this transaction to do what I need. I wonder if anyone has done this configuration or have material on this subject that can help me accomplish this task.
Thanks and Regards,
Carlos Drehmer
ABAP Developer.
RSECADMIN can be used for taking trace in BI. Please put check in the checkbox near the user id field.then only log can be tracked.
Nitin,
Run RSECADMIN and click on the ANALYSIS tab. Under that tab click on error logs. Once in that screen click on on configure log recording and enter the user you want to trace-make sure you save. In the previous screen you should then be able to capture information as to what is failing for the user. You'll have to run the report first under the user and then click display. After you're done make sure you remove the ID from recording. This is what i've done in the past when troubleshooting auth issues when users are running queries in the BEX analyzer and portal.
-Wes
Sorry Nitin, Dinesh is correct!
Be it Key figures or Characteristics, when you are executing BI queries, authorization concept works based on what an user is requesting in the query output and what authorization it has.
Output is only displayed when both exactly matches, else it says...."better luck next time!" :-)
Thank you for your advice, Julius,
These tables will be generated in production, so we aren't sure what the table names will be. We do know that the tables will be prefixed by /BIC/A (DSO Active Table) or /BIO/B (DSO Change Log) however. I don't see how we can restrict SE16 developer's access to these tables with S_TABU_NAM. I'm sure it is my ignorance, so please advise.
Thank you,
Dale
Hi Praveen
Have you verified if the person assigned to the user moved positions? Alternatively, a change to their 0105 mapping Have a look at their PA20 record for organisational assignments to see if they are in a different position.You should see a history of the user's org assignments with date delimits
If the user is still in the same position and access was deleted from the position, you might see who last made a change in PP01 or you might need to run a report to see who has the PLOG access for Infotype 1001 with AG (Role). If you HRP1001 table logged you can run report RHCDOC_DISPLAY
Dear All,
Here again same issue, scenario is, BAPI/program executed the 24 batches and suddenly does not execute the next batch mean batch number 25, ABAPER is demanding debug access on Production system while we already granted more then 4 time access of debug for same scenario. when I said to ABAPER that why you people does not rectify the program error then they are saying me that there is no solution of this error. We need debug access to find out the program error for same scenario whenever we face this issue.
what do you say about ABAPER mean why they are demanding the debug access instead rectify the program?
due to some reason, I can't use firefighter.
Regards,
The table does not have to exist (yet) to maintain s_tabu_nam.
So you can work out the name (spaces) from the DSOs and enter them. The authorization will not be destroyed together with the table...
Cheers,
Julius
Thank Debmalya..:)
Hi Jamil,
If you are using ID based FF id access, suggest you create a FF Id for Debug access and give it to the abaper or just maintain debug access to one FF id (time limieted ?), this way he should get Debug access via FF Id.
Do have in Mind FF id with Debug generate a lot of logs.
Rgds
Ganesh.S
Hi Julius,
I am also getting same issue.
User is locked in Solman due to in correct login. System is connected through CUA.
When i am trying to unlocking it locally, getting bellow message.
User XXXXXX is still locked
Message no. 01333
SAP_BASIS support pack is SAPKB70210
Seeking for your comment.
Thanks-
Guru Prasad Dwivedi
A possible explnation is the SOLMAN is the CUA master. This means that the RFC user in it's own logical system is the "call back" user but you are expecting it also to perform the CUA client tasks (for itself).
CUA "hogs" the logical system names with the same name as the technical connections, but the master is a child of itself.
--> Check the auths of the user in the logical system of SOLMAN and your SCUM settings.
--> Check for programs doing DB updates on USR02...
--> Check for locks on the user in Sm12 (this is also a common cause of confusion, as you are locally in change mode (lock) and the RFC user in logsys wants to change it as well...)
ps: There is a setting in table USR_CUST via which you can relax the locks, but you should actually fix the problem....
A good solution is an IDM and only maintain identities from there.
Cheers,
Julius
HI,
the passwords are not imported into central system when you add a new child system. So John will have to use his old password to log on to corresponding child system. You will be to reset password from central system in any child system.
Cheers
Hi Security 13 Team
You can obtain some of the transaction to S_TABU_DIS mapping where the transaction code is an SM30/31/34 call
To do this, you can go to table TSTCP in ALV mode and filter for PARAM contains '/*SM3*'. Within the PARAM results you can locate the tables/views/etc and then go to table TDDAT to look up the table to auth group mapping.
This will not give you transactions where the program contains a call for S_TABU_DIS. You might be able to look at SU24 data (USOBT_C and USOBX_C) to see if there are any proposals.
After that you may need to look at testing each transaction in the roles and mapping them out - back to your comment about testing/tracing each transaction.
As another consideration, if you are being asked to lock down S_TABU_DIS you should also consider removing it as much as possibly and granting S_TABU_NAM to the specific table instead.
Mess in a system is always time consuming to clean up.
Hi SAP Experts,
Can anyone please explain about Audit logs and what for SM19 T Code is used in SAP MM.
Thanks
Routhu
Hello Routhu, there are no special rules in SM19 for the module MM. What things you want to log or check in MM. Maybe you can use other logs. For more information about SM19 or the security audit log use the search function in this forum or the SAP Help. kind regards Bernhard
Thanks Bernhard for your reply
Could you please explain me Actuall what is Audit Log and its function in SAP MM. Can you give any Link to find any Document related to Audit Log.
Thanks
Routhu
Hi,
Search before putting a question on SCN, then you will obviously get the documents/Links.
http://help.sap.com/saphelp_nw70ehp3/helpdata/en/4D/41BEC4AA601C86E10000000A42189B/frameset.htm
Regards,
Rama
Thank you All