on 09-24-2013 9:08 PM
hello people,
I need your help.
i have a next error:
The URL call http://cry-svr-bw70.crysol.local:8000/sap/bc/webdynpro/SAP/GRRM_WD_RNP was terminated because of an error.
Note
Environment
GRC Risk Management 10.0
Reproducing the Issue
I try with note:
1804950 - GRC RM 10.0- From Rsk & Opportunity OIF submission of Issue resulted in dump
but it didn't work
This note describes exactly what happens in my case.
please ask for some tips.
Hello Calderon,
have you checked case management customizing (Process Control->Cases->Check customizing for Case Management)?
All items should be green.
You can adjust it following instructions from OSS note 1570080.
Best regards
André Yuji
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the same problem, Did you find a solution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Calderon,
Could you please provide us the ST22 short dump? Usually this is an error in the master data. Please, provide us the dump and I will be able to analyze it.
Thank you,
Fernando
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Fernando,
this shows the transaction ST22.
Category ABAP Programming Error
Runtime Errors ASSERTION_FAILED
ABAP Program CL_GRFN_API_IDENT=============CP
Application Component GRC
Date and Time 25.09.2013 10:29:53
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) "
How 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_API_IDENT=============CP" or "CL_GRFN_API_IDENT=============CM001"
"GET_ENTITY_ID"
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
fter the short dump. Then choose "System->List->Save->Local File
Unconverted)".
. If the problem occurs in a problem of your own or a modified SAP
rogram: The source code of the program
In the editor, choose "Utilities->More
tilities->Upload/Download->Download".
. Details about the conditions under which the error occurred or which
ctions and input led to the error.
Source Code Extract
Line SourceCde
1 method get_entity_id.
2
3 data: lv_rest type string,
4 lv_entity type grfn_api_entity_id.
5
>>>>> assert iv_object_id is not initial.
7 split iv_object_id at c_separator_entity into lv_entity lv_rest.
8
9 * --- special cases to adopt legacy situations
10 if lv_entity = grpc0_c_entity-control.
11 " check for XCONTROL
12 data: lv_infix type string.
13 split lv_rest at c_separator_entity into lv_infix lv_rest.
14 assert lv_rest is not initial. " control ID must contain 2 slashes!
15
16 if lv_infix eq grfnh_central_type.
17 lv_entity = grpc0_c_entity-xcontrol.
18 endif.
19 endif.
rv_entity = lv_entity.
assert rv_entity is not initial.
Dear Calderon,
When there is an assert condition violated, usually this is some inconsistency in your system master data. According to the reprodution steps you provided, I suggest you to check the relationship and validity between the objects you want to assign.
This situation needs further debugging in order to know exactly the corrupted object.
Thank you,
Fernando
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.