Hi ,
Dump in Runtime error is : DSTEP_WRONG_PROGRAM
Program : SAPMSSYD..
Error shows in 58 line) below>>>> CALL FUNCTION 'SPC_REMOVE_DOCUMENT' DESTINATION gv_vmc
How to solve this error... What is the exact proposed solution solve this error.
Category Internal Kernel Error
Runtime Errors DSTEP_WRONG_PROGRAM
Application Component BC-ABA-LA
Date and Time
Short text
Program "SAPLPRC_INT" cannot resume
What happened?
Error in the SAP kernel.
The current ABAP "SAPMSSYD" program had to be terminated because the
ABAP processor detected an internal system error.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
Program "SAPLPRC_INT" was interrupted and is now supposed to resume. However,
program "SAPMSSYD" was loaded instead and the original program could not resume
.
There is an internal system error.
eliminated with ABAP/4.
How to correct the error
Try to eliminate the error by regenerating the program "SAPMSSYD". To
do this, proceed as follows:
Call Transaction SE38 in the R/3 System, enter the program
name "SAPMSSYD" and then choose "Generate".
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:
"DSTEP_WRONG_PROGRAM" " "
"SAPMSSYD" or "LPRC_INTF13"
" "
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
nformation on where terminated
Termination occurred in the ABAP program "SAPMSSYD" - in " ".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 58
of the (Include) program "LPRC_INTF13".
ource Code Extract
ine SourceCde
28 DELETE TABLE gt_head WITH TABLE KEY pd_handle = us_head-pd_handle.
29
30 * ext. data source new kernal BADI impl. obj. can be used by other transaction;
31 * clean them up in programm PRC_INT_INIT instead of here
32 * REFRESH gt_datasource_badi.
33
34 * delete lines for item data
35 DELETE gt_item WHERE pd_handle = us_head-pd_handle.
36
37 * delete the additional information for delay item load mode
38 DELETE gt_delay_item_load WHERE pd_handle = us_head-pd_handle.
39
40 * delete buffered information from object buffer
41 CALL FUNCTION 'PRC_PRIDOC_INIT_OB'
42 EXPORTING
43 iv_pd_handle = us_head-pd_handle
44 iv_group_processing = us_head-group_processing.
45
46 * delete buffered information from database buffer
47 CALL FUNCTION 'PRC_PRIDOC_INIT_DB'
48 EXPORTING
49 iv_pd_guid = us_head-wrk_data-knumv.
50
51 * dequeue entry for pricing document
52 PERFORM dequeue_pridoc USING us_head-enqueue_mode
53 us_head-wrk_data-knumv
54 us_head-pd_handle
55 uv_bal_log.
56
57 break_rfc.
>>>> CALL FUNCTION 'SPC_REMOVE_DOCUMENT' DESTINATION gv_vmc
59 EXPORTING
60 iv_document_id = us_head-wrk_data-knumv
61 IMPORTING
62 es_profile = gs_profile_add
63 EXCEPTIONS
64 communication_failure = 1 MESSAGE lv_message
66 OTHERS = 3.
67 add_profile 'SPC_REMOVE_DOCUMENT'.
68
69 IF sy-subrc NE 0.
70 * log errors in application log for header
71 PERFORM check_error USING us_head
72 space "header level
73 uv_bal_log
74 CHANGING lv_message.
75 MESSAGE e600 WITH us_head-ipc_dest RAISING ipc_error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.