The document provides steps to troubleshoot and resolve common authorization and spool issues in SAP. It describes using transaction codes like SU56, S_BCE_68001425, /nPFCG, SE91, SM37, SP01 and SAP tables to check authorization objects, roles, and transactions a user has access to. It also provides instructions on resolving a spool error by defining the job spooler and output device for the user via transaction code SU3.

1. 1. When user receive an authorization error such as the below dialog box, request the user to enter /nSU56
or /nSU53 to display more details on the authrization issue.
2. In Su56, expend the menu and you will see the object value and transaction type. In this scenario we know
user do not have authorization on object value “0111” and transaction “V”
3. We now know that user is not authorized for object “C_PROJ_TCD”, value “0111” and type “V”.
4. Use T-Code S_BCE_68001425 to search for the authorization object. In this scenario we enter the username
and authorization object and it will display the role.

2. 5. Below is the results. Now we have to find the correct role which we need to give authorization too. If you are
not sure, consult with your consultant.
6. Open /nPFCG to edit the role.
7. Enter the role name.
8. Click on Authorization tab and click “display authorization data”
9. Expend the menu and locate the object or use the “FIND” button to search for object “C_PROJ_TCD”
10. Below are the authorization you need to provide accordingly.
11. In this case, we select “0111 which is Basic WBS dates”

3. 12. Save
13. Click on generate profile button
14. Now do user comparison
15. Ask user to re-login and try the transaction again.
Addtional Info
If you know the Authorization object and would like to search which transaction is using it, you can open this
transaction from SAP menu.

4. ow to Check ABAP Dumps Message Type X
Steps:
1. Execute ST22 > Double click on any entries
2. Go to Source Code Extract

5. 3. Locate “>>>>” and you will see Message X041 in this example. Take note of the Message class and
number.
4. Now open SE91. Enter the details we found from Source Code Extract in ST22:
-Message Class: RD
-Message Number: 041
Click Display

6. 5. Here, we determine what the message indicates
6. Now we know that the ABAP Dump message type X is due Extract Structure does not exist at the time
of transport. Informed the ABAP consultant or Function consultant about this issue.
Most common SPOOL error encountered by BASIS. How do we resolve this issue?
Steps
1. Execute SM37. You found an error Job. When you double click you found
2. You saw the below error
3. This error is caused by job spooler is not defined when job creation hence it picks up the job owner’s
default output device.
4. Since the default output device is no populated on master user record, the job log can’t find the print
parameter.
5. To resolve the issue, please populate the output device and select your preference for your SAP spool
request via transaction code SU3.
6. For Output device, you can choose one of SAP printer which has been defined in SAP (you can look at
via transaction code SPAD)

7. 7. Recommendation: please do not select LOCL if you want to opt ‘Output immediately’. Moreover, this
output device is not good for network performance
8. Select ‘Output immediately’ if you want to immediate print for every spool request that you create in
SAP. Recommendation: do not select this.
9. Select ‘Delete After Output’ if you want SAP to delete every spool that you create. Recommendation:
do not select this. You can manage your spools e.g. printing, reprinting, deletion, etc via transaction code
SP01 as below: