Hi Experts
We are trying to set up a test ESS leave workflow using standard template WS12300111. In addition, a leave applicant and approver (chief position of org unit) have been set up in Organization management.
All tasks in the template WS12300111 has been set to General Tasks as indicated in the forum message
Unfortunately I am still encountering the runtime error whenever I use PTARQ transaction to test submitting a leave application in the system. A snapshot of the runtime error is below.
Is there any other necessary set up that I may have missed in the workflow setup that is causing the shortdump ?
Points will be awarded for answers. Thanks.
Runtime Errors MESSAGE_TYPE_X
Date and Time 15.06.2008 17:38:53
Short dump has not been completely stored (too big)
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
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
Short text of error message:
Unable to read RFC destination WORKFLOW_LOCAL_500
Long text of error message:
Technical information about the message:
Message class....... "SWF_RUN"
Number.............. 617
Variable 1.......... "WORKFLOW_LOCAL_500"
Variable 2.......... "RFC_READ_DESTINATION_TYPE"
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
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:
"MESSAGE_TYPE_X" " "
"CL_SWF_RUN_WIM_LOCAL==========CP" or "CL_SWF_RUN_WIM_LOCAL==========CM088"
"IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER"
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.
Information on where terminated
Termination occurred in the ABAP program "CL_SWF_RUN_WIM_LOCAL==========CP" -
in "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER".
The main program was "RPTARQUIATEST ".
In the source code you have the termination point in line 10
of the (Include) program "CL_SWF_RUN_WIM_LOCAL==========CM088".
Source Code Extract
Line SourceCde
1 METHOD if_swf_run_wim_utl_internal~get_system_user .
2 DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4 TRY.
5 IF me->m_int_state-system_user IS INITIAL.
6 me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destinatio
7 ENDIF.
8 re_user = me->m_int_state-system_user.
9 CATCH cx_swf_run_wim INTO l_excp.
>>>>> MESSAGE ID l_excp->t100_msg-msgid
11 TYPE 'X'
12 NUMBER l_excp->t100_msg-msgno
13 WITH l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
14 l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
15 ENDTRY.
16
17 ENDMETHOD. "
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.