RAR5.3 Rule Upload - ORA-00001: unique constraint violated

[Former Member]

Hello,

I'm trying to upload rule text files (specifically function action and function permission files via Configuration>Rule Upload>Function Authorization) and I get the error:

-Function Actions are successfully created

-ORA-00001: unique constraint (SAPSR3DB.SYS_C005587) violated

I have verified that I have correctly uploaded Static Text (via /VIRSA/ZCC_DOWNLOAD_DESC) and Auth Objects (via /VIRSA/ZCC_DOWNLOAD_SAPOBJ) for all connected systems.

I am unsure why I am receiving the above error. My permission function data refuses to upload.

1) Can anyone provide an insight or guidance on my issue?

2) Is there anywhere I can go to find out what exactly "ORA-00001: unique constraint (SAPSR3DB.SYS_C005587) violated" means? The log doesn't provide any more detail than this error message.

Much appreciated!!

[Former Member · Accepted solution]

Hi Jes

Are you trying to upload the static text and auth objects via Configuration>Rule Upload>Function Authorization ? If so please do not do that .

You have to upload the sap delivered functions here which you get with the support packages ( usually comes in a zip file for AC 5.3 as 5.3_download_files ) like R3_function_action.txt , R3_function_permission.txt and other module functions

[Former Member · Accepted solution]

Hi Sahad,

>

> Hi Jes
> 
> Are you trying to upload the static text and auth objects via  Configuration>Rule Upload>Function Authorization ?

No. I have uploaded static text files correctly through Configuration>Upload Objects>Text Objects and I have uploaded auth object files correctly through Configuration>Upload Objects>Permissions.

>

> You have to upload the sap delivered functions here which you get with the support packages ( usually comes in a zip file for AC 5.3 as 5.3_download_files ) like R3_function_action.txt , R3_function_permission.txt  and other module functions

As stated in my original post, I am already doing this.

I am loading function files correctly and I am loading static text/auth object files correctly. But I am still seeing the error, unfortunately.

[Former Member]

Hello Jes,

You are getting this error as the files will contain a space or some other error.

Open these files in Word and check TABs and ENTERs are correct.

Basically your file is NOT EXACTLY TAB DELIMITED FILE.

There some TAB here or there in your file.

Regards,

Surpreet

[Former Member]

Hi ,

We were also getting the same error ..........as told to you earlier by others It seems that in the table one of the field has not null constraint.Means that the file which you are trying to upload has field empty so when trying to upload oracle will not understand as the file which you are trying to upload has empty filed there .And one more thing is that when you have downloaded the authorisation object data and static text data please save the text file in unicode format.Even if you upload you might get this error.PLease correct me if i am wrong ...

[Former Member]

As Surpreet mentioned, and after looking into it more, I think my function upload files have a slight formatting error somewhere within the text file/s. I'm working throw the files slowly to find the formatting issue/s.

This is the path I'm currently going down. I will reply with my results when finished. Thanks to all for your insight - I really appreciate it!

--

Jes Behrens

[Former Member]

After thoroughly examining our function authorization files, I was able to correct the mistakes and get the files uploaded successfully in RAR5.3.

Our issue was duplicate rows. I had been manually manipulating/editing the function upload files to upload and test in our Sandbox environment. I found several cases where I had 2 rows that were identical or were identical except one was Enabled and one was Disabled. In either case, I removed the duplicate row. I also ensured I didn't have any extra tabs, spaces, or other formatting errors.

My issue was not related to static text or auth object uploads. The issue was strickly with my Function Permission upload text files. I'm happy to say I have made the necessary fixes.

Thanks again to all for your replies - I really appreciate it!

--

Jes Behrens

[Former Member]

Dear Jes,

Please follow the steps as mentioned at bellow, for uploading Authorization Object and Authorization Text what you have downloaded from backend system using report /VIRSA/ZCC_DOWNLOAD_DESC & /VIRSA/ZCC_DOWNLOAD_SAPOBJ from SE38

A) Bellow Mention Process For Authorization Text Upload (Received through /VIRSA/ZCC_DOWNLOAD_DESC )

1. From your SAP server (backend system), enter transaction code SE38. The ABAP Editor: Initial screen appears.

2. In the Program field, enter /VIRSA/ZCC_DOWNLOAD_DESC, and click Execute.

3. In the Local File field, enter a path and the name for the static text file. The suggested name for this file is SAPtext.txt. Use the Search button located to the right of the Local File field to navigate to the desired directory, and name the file. For easy access, store the file on your desktop and name it SAPText.txt.

4. Click Execute.

5. Return to Risk Analysis and Remediation(RAR), select the Configuration tab, and navigate to Upload Objects > Text Objects.

6. Complete the following fields: System ID If you have connected to multiple SAP systems, enter a single system ID, and repeat the steps above for each SAP system.  Local File u2013 Enter the path to (or browse to) SAPText.txt.

7. Click the appropriate button to execute this process in the background or foreground. To execute this job in the background, the SAPText.txt file must be stored on an application server. If the text must be in multiple languages, the user must log on to the back-end ABAP system using the language under which the file should be exported. Run the program as described above for each language that you want to load into Risk Analysis and Remediation, and upload each file as described above.

============

B) Beloow Mention Steps For Upload Authorization Object (Received from /VIRSA/ZCC_DOWNLOAD_SAPOBJ )

To upload authorization objects:

1. From your SAP server (backend system), enter transaction code SE38. The ABAP Editor: Initial screen appears.

2. In the Program field, enter /VIRSA/ZCC_DOWNLOAD_SAPOBJ, and click Execute.

3. In the Local File field, enter the path to and the name of the authorization object file. The suggested name for this file is SAPAuthObj.txt. Use the Search button located to the right of the Local File field to navigate to the desired directory, and then name the file. For easy access, store the file on your desktop, and name it SAPAuthObj.txt.

4. Click Execute.

5. Return to Risk Analysis and Remediation, and navigate to Configuration > Upload Objects > Authorization Objects.

6. In the Local File field, enter the specified path (or browse to the location), and specify SAPAuthObj.txt

7. Click the button to execute this process in the background or foreground. To execute this job in the background, the text file must be stored on an application

Hope it will be helpfull for you

Regards

Pavel

PwC - India

[Former Member]

>

> Dear Jes,
> 
> Please follow the steps as mentioned at bellow, for uploading Authorization Object and Authorization Text what you have downloaded from backend system using report /VIRSA/ZCC_DOWNLOAD_DESC & /VIRSA/ZCC_DOWNLOAD_SAPOBJ from SE38
> 
> 
> A) Bellow Mention Process For  Authorization Text  Upload (Received through /VIRSA/ZCC_DOWNLOAD_DESC )
> 
> 1. From your SAP server (backend system), enter transaction code SE38. The ABAP Editor: Initial screen appears.
> 
>  2. In the Program field, enter /VIRSA/ZCC_DOWNLOAD_DESC, and click Execute.
> 
>  3. In the Local File field, enter a path and the name for the static text file. The suggested name for this file is SAPtext.txt. Use the Search button located to the right of the Local File field to navigate to the desired directory, and name the file. For easy access, store the file on your desktop and name it SAPText.txt.
> 
>  4. Click Execute.
> 
> 
>  5. Return to Risk Analysis and Remediation(RAR), select the Configuration tab, and navigate to Upload Objects > Text Objects.
> 
>  6. Complete the following fields: System ID If you have connected to multiple SAP systems, enter a single system ID, and repeat the steps above for each SAP system.  Local File u2013 Enter the path to (or browse to) SAPText.txt.
> 
> 
>  7. Click the appropriate button to execute this process in the background or foreground. To execute this job in the background, the SAPText.txt file must be stored on an application server. If the text must be in multiple languages, the user must log on to the back-end ABAP system using the language under which the file should be exported. Run the program as described above for each language that you want to load into Risk Analysis and Remediation, and upload each file as described above.
> ============
> B) Beloow Mention Steps For Upload  Authorization Object (Received from /VIRSA/ZCC_DOWNLOAD_SAPOBJ )
> 
> To upload authorization objects:
> 
> 1. From your SAP server (backend system), enter transaction code SE38. The ABAP Editor: Initial screen appears.
> 
> 2. In the Program field, enter /VIRSA/ZCC_DOWNLOAD_SAPOBJ, and click Execute.
> 
> 3. In the Local File field, enter the path to and the name of the authorization object file. The suggested name for this file is SAPAuthObj.txt. Use the Search button located to the right of the Local File field to navigate to the desired directory, and then name the file. For easy access, store the file on your desktop, and name it SAPAuthObj.txt.
> 
> 4. Click Execute.
> 
> 5. Return to Risk Analysis and Remediation, and navigate to Configuration > Upload Objects > Authorization Objects. 
> 
> 6. In the Local File field, enter the specified path (or browse to the location), and specify SAPAuthObj.txt
> 
> 
> 7. Click the button to execute this process in the background or foreground. To execute this job in the background, the text file must be stored on an application
> 
> Hope it will be helpfull for you
> 
> 
> Regards
> Pavel
> PwC - India

Hi Pavel,

I am well aware of these steps and have already followed them correctly. I have uploaded static text files correctly through Configuration>Upload Objects>Text Objects and I have uploaded auth object files correctly through Configuration>Upload Objects>Permissions.

Loading the files correctly is not my issue

I need to know what "unique constraint" I violated. Is there anywhere I can go to find out what exactly "ORA-00001: unique constraint (SAPSR3DB.SYS_C005587) violated" means? The log doesn't provide any more detail than this error message.

Any thoughts?

Thanks!!

--

Jes Behrens

[Former Member]

Hi Jes,

It seems like the Functions file you are trying to upload is corrupted. Please ask basis team to download it again service market place and upload it again.

Also ask them to check what information they find in alert log of oracle.

[Former Member]

Dear Jes,

The Meaning of "ORA-00001: unique constraint violated"

This error is issued if a user tries to insert an already existing value into a column defined unique.

Unique Key

The unique constraint doesn't allow duplicate values in a column. If the unique constraint encompasses two or more columns, no two equal combinations are allowed.

You do one thing ask your BASIS Admin to delete Authorization Object (table name is virsa_cc_sapobj) data from GRC RAR then again try to upload Authorization files which you got from Backend system.

Note: Must take a backup of this table before deleting it.

Regards

Pavel

PwC - India