Main issues with GRC object in SE75 transaction
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.”
The GRC object in SE75
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