You are on page 1of 5

Hello All,

When an access requested is submitted, the message that we like to read on the monitor
is: Request submitted successfully with the following request number. But, sometimes we get
to see errors when the request is submitted. In this document, Please find some of the common
issues along with solutions here.

Error No: 1
When submitting an Access Request, if you get the following error:

Solution

Go to transaction (t-code) GRFNMW_GEN_VERSION


Enter MSMP Process ID SAP_GRAC_ACCESS_REQUEST
Reactivate the workflow

If still errors appears after reactivating then try deleting the existing BRFPLUS rule and test again.
Error No: 2
When submitting an Access Request, if you get the following error:

Solution

This error occurs due to Failure to complete configuration to set number ranges for
provisioning requests.
Follow path from transaction SPRO > Governance, Risk and Compliance > Access
Control > User Provisioning > Maintain Number Range Intervals for Provisioning
Requests (Click on the clock icon to execute.)
Enter GRACREQNO in the field and click paper icon to create. Click on Number Ranges
and add field to set range. (Be sure to save values before exiting.)
Next, click execute icon before Define Number Range for Provisioning Requests, and
click on New Entries. (It may begin with the number one (1).)
After creating, go back to the previous screen. There should be a screen with the
number range and a field labelled Active. The circle should be empty in this active field
next to the line where the number range is displayed, but it is mandatory to click into
the field to make it active (circle will fill with black dot). Save entries.
After creating workflow in MSMP, requests will now be created starting with the first
number defined in the range.

Error No: 3
When submitting an Access Request, if you get the following error:

Solution

If a request type has ASSIGN OBJECT actions then, Add atleast one role to the
request error message will be shown if no role is added

Error No: 4
When submitting an Access Request, if you get the following error:

Solution
If using mapped default roles, but they have not been set up in NWBC it will error
because it adds an additional line item.
Please run simulation if using a BRF+ rule. Check the decision table for items expected
and it should return a result. If it does not return expected results, please adjust the
rule.
Check If SAP_ALL profile is assigned to the background user WF-BATCH.

Error No: 5

When submitting an Access Request, if you get the following error:

Solution

Check if the valid from and valid to dates are maintained properly or not.
Also check if the valid to date is later than the current date.

Error No: 6

When submitting an Access Request, if you get the following error:

ITEM 0002 resulted to cannot resolve path; check routing mapping


Request submit failed; error in MSMP submit method
Solution
Wrong BRF+ object ID for initiator rule copied to Rule ID under step 2, Maintain Rules.
Check the settings in the decision table.
Check if the Rule Result is maintained properly or not.
Additionally, verify that event linkage is active for starting workflow and access approval
(Transaction SWE2).

Error No: 7

When submitting an Access Request, if you get the following error:

XYZ is not a valid User

Solution

This error could be due to Parameter 2051.

If set to YES, the application validates the UserID exists on the specified source system.
If the user does not exist, the application does not allow the request to continue. The
validation is performed when you choose Submit or press Enter. This has to be set to
NO.
I decided to create this blog to gather the issues of not having the GRC object created in
SE75.
First of all, a brief explanation about the transaction:
SE75 Long text (SAPScript texts)
Long Texts (also referred as SapScript texts or text objects) are the containers for containing
long texts in SAP systems, and they are usually attached to business objects, that users can
enter free comments.
Long Texts were initially created for SapScript tool because old database systems had text
columns limited around 255 characters. The new database systems do not have this restriction
any more, but Long Texts remain.
Source: http://wiki.scn.sap.com/wiki/x/1YRMB
The GRC object in SE75


Main issues:
If GRC text object ID is not in SE75 list, the following issues may occur in the system. The
notes listed below are In chronological order:
1895324 Role Import ends with an error LONG_TEX failed
2156904 Access Request Creation Error
2151993 Description and Control Objectives Blank After Access Risk Save
1983201 Error while saving comment in Notes section of ad hoc issue
1982125 Reason code and Activity description is missing in reports
1801435 Error Inserting Records error on request submission
1847877 Risk ID detail Description not getting saved
1800347 Short Dump on FF Login
1890058 Saving note failed error comes while saving Mitigation Control
1793111 Error Creating TEXT/LONG TEXT failed
1843287 Submitting a request there is an error while inserting request reason
1791799 GRC 10.0 Error while inserting the request reason
All the notes above present the same solution.
Object GRC must be created in SE75.
KBA 2156904 shows the manual steps on how to do it.
You can also use the following SAP note to run a script to update the text tables directly into
the database:
2058516 Creating entries in TTXOB,TTXOT,TTXID and TTXID Table

You might also like