Error while processing your query : ASSERTION_FAILED : CL_GRFN_DOCUMENTS_MODEL=======CP

[Former Member]

Hi Experts,

When I try to upload a document from my GRC NWBC i get the following dump. I have checked the note 1952142 and already those settings are maintained in the system.  Please find the below dump details and screenshot.

Please find the below details.

System Details :  SAP GRC EHP 2 NW 7.0

Dump Details:

Category               ABAP Programming Error

Runtime Errors         ASSERTION_FAILED

ABAP Program           CL_GRFN_DOCUMENTS_MODEL=======CP

Application Component  GRC

Date and Time          21.11.2014 13:35:19

Short text

     The ASSERT condition was violated.

What happened?

     In the running application program, the ASSERT statement recognized a

     situation that should not have occurred.

     The runtime error was triggered for one of these reasons:

     - For the checkpoint group specified with the ASSERT statement, the

       activation mode is set to "abort".

     - Via a system variant, the activation mode is globally set to "abort"

       for checkpoint groups in this system.

     - The activation mode is set to "abort" on program level.

     - The ASSERT statement is not assigned to any checkpoint group.

What can you do?

     Note down which actions and inputs caused the error.

     To process the problem further, contact you SAP system

     administrator.

     Using Transaction ST22 for ABAP Dump Analysis, you can look

     at and manage termination messages, and you can also

     keep them for a long time.

Error analysis

     The following checkpoint group was used: "No checkpoint group specified"

     If in the ASSERT statement the addition FIELDS was used, you can find

     the content of the first 8 specified fields in the following overview:

     " (not used) "

     " (not used) "

     " (not used) "

     " (not used) "

     " (not used) "

     " (not used) "

" (not used) "

" (not used) "

to correct the error

Probably the only way to eliminate the error is to correct the program.

-

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"ASSERTION_FAILED" " "

"CL_GRFN_DOCUMENTS_MODEL=======CP" or "CL_GRFN_DOCUMENTS_MODEL=======CM005"

"IF_GRFN_API_MODEL~SAVE"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

   To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

   Display the system log by calling transaction SM21.

   Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

   In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

and goes on.

Kindly help me out for a fix.

Regards,

Prithivi Raj

[Former Member · Accepted solution]

HI Guys,

Thanks for your response.

I found a solution in the Opentext Knowledge base. Please find the below.

1. Go to Include/Program LSDCLF05 and search for FORM 'get_comps_subst_names'.

2. At the end of this form, create an enhancement implementation using something like this.

FIELD-SYMBOLS: <fs_name> TYPE SDOK_FILNM.

LOOP AT t_subst_names ASSIGNING <fs_name>.

REPLACE ALL OCCURRENCES OF '\' IN <fs_name> WITH '|'.

REPLACE ALL OCCURRENCES OF ':' IN <fs_name> WITH '?'.

ENDLOOP.

After having the above code in the program we were able to upload the documents without any dump/issues.

Regards,

Prithivi Raj

[Former Member]

Hi,

Can you also pls provide the source code snapshot of the ST22 dump.

Thanks

KH

[Former Member]

Hello Prithivi Raj,

It seems that you have special characters in the file. I believe system is using full file name to upload the file content.

Please, let me know as we have a note to fix it, however, the note is in pilot release.

Best Regards,

Fernando