Short Dump DYNPRO_MSG_IN_HELP in Conversion Exit
Hi Gurus,
I've written the following conversion exit:
FUNCTION CONVERSION_EXIT_ZBZEI_INPUT.
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(INPUT)
*" EXPORTING
*" VALUE(OUTPUT)
*" EXCEPTIONS
*" INPUT_NOT_VALID
DATA : CPI_OUT(4) type n, CPI_IN(5), cpi_in2(5), cpi_in3(5).
DATA : CPI_YEAR(4), CPI_PERIOD(3).
DATA : CPI_NUM2(2) TYPE N.
DATA : CPI_NUM3(2) TYPE N,
index(2) type n,
index2(2) type n,
merker(1).
DATA : CPI_C8, CPI_C7, CPI_C6, CPI_C5.
DATA: SONDERZ. "nimmt das Trennungszeichen auf
*-initializations-----------------------------------------------------*
check not input is initial.
CPI_IN2 = INPUT.
CLEAR : cpi_in, cpi_in3, cpi_out, OUTPUT, index, index2, merker,
cpi_num2, cpi_num3.
do.
if cpi_in2+index(1) co '0123456789' and merker ne 'X'.
cpi_in+index2(1) = cpi_in2+index(1).
add 1 to index2.
endif.
if cpi_in2+index(1) = ':'.
merker = 'X'.
clear index2.
endif.
if cpi_in2+index(1) co '0123456789' and merker = 'X'.
cpi_in3+index2(1) = cpi_in2+index(1).
add 1 to index2.
endif.
add 1 to index.
if index = 5.
exit.
endif.
enddo.
if cpi_in3 is initial.
cpi_out = cpi_in.
else.
cpi_num2 = cpi_in.
cpi_num3 = cpi_in3.
cpi_out(2) = cpi_num2.
cpi_out+2(2) = cpi_num3.
endif.
if cpi_out(2) > 23.
message e000 raising input_not_valid.
endif.
if cpi_out+2(2) > 59.
message e001 raising input_not_valid.
endif.
output = cpi_out.
* output+2(2) = cpi_in+3(2).
endfunction.
The problem is when the user inputs an invalid value and presses directly after this F4 the conversion exit will call and I get the short dump DYNPRO_MSG_IN_HELP when I trigger the error message.
Is there any way to know that the program is in value-request? Maybe a system field? Can I catch this error?
Thanks for help.
Lars
Hello Lars,
refering to OSS 84510 SAP does not allow error messages in this environment. However, to find out if you are in a F4- context you can use the kernel function 'DY_GET_DYNPRO_EVENT'
data: event(3).
"check if we are in F4 environment
call 'DY_GET_DYNPRO_EVENT' id 'EVENT' field event.
if sy-subrc <> 0 or ( event <> 'PAI'
and event <> 'INP' )."PAI also POV
" not F4 help
message e000 raising input_not_valid.
else.
"F4 help -> only S message
message s000 display like 'E' raising input_not_valid.
endif.
Kind regards, miro
Similar Messages
-
Short dump due to conversion error on screen
Hello all,
I have designed one screen, and throwing error message if perticular filed is blank as (message e002(z2)). If i keep the filed blank system is throwing error message but giving short dump because of 'Conversion error' .
Error analysis : 'The program has been interrupted and cannot resume. |
Program "SAPMZTIMECOLLECT_NEW" attempted to display fields on screen 0101.
| An error occurred during the conversion of this data. '
Please, could you help to understand why system is giving short dump.
Thanks in advance..!!Solved for me.
If we don't have value for the field which we are passing it to tablecontrol, then declare the variable with the same type and assigned space for the same and submit it to table control output. then the error is not coming.
Ex: If we dont have the value for the table control field (KOSTL), then declare one constant K_KOSTL LIK below,
DATA:K_KOSTL TYPE KOSTL.
K_KOSTL = ' '.
IF the value of table control field is initial, then pass K_KOSTL to it.
This what I have done.
Regards
Ramesh. -
KNA1 short dump with Unicode conversion
Hello,
We did Unicode conversion in our dev box. every thing looks okay except one issue.
when we are trying to create customer using XD01. it gives a short dump DBIF_RSQL_INVALID_REQUEST in the update program at command INSERT KNA1.
we looked at data, structure of KNA1 with non unoicode system and not found any differnece. if i execute the same data in non-unicode system it works.
any idea what must be the issue?
regards
ShammiHi Shammi,
Have you checked in OSS if you find any note.
Regards,
Atish -
Short dump on using screen exit via screen exit - MEREQ001
Hi Experts,
Short text
Incorrect screen type: Screen is incorrectly defined or used.
What Happened
The attribute screen type with the values 'Normal Screen' and
'Subscreen' determines the use of the screen. If a normal screen is used
as subscreen or vice versa, an error occurs.
The screen "SAPLXM02" 0111 has, in this respect, an inappropriate screen type.
Error analysis
This is a programming error in the application.
Trigger Location of Runtime Error
Program SAPLXM02
Include LMEVIEWSF01
Row 209
Regards,
Moderator message: not a proper question, please do more research before asking, study the entire dump text for hints, search for SAP notes.
Edited by: Thomas Zloch on May 13, 2011 1:32 PMHi Experts,
Short text
Incorrect screen type: Screen is incorrectly defined or used.
What Happened
The attribute screen type with the values 'Normal Screen' and
'Subscreen' determines the use of the screen. If a normal screen is used
as subscreen or vice versa, an error occurs.
The screen "SAPLXM02" 0111 has, in this respect, an inappropriate screen type.
Error analysis
This is a programming error in the application.
Trigger Location of Runtime Error
Program SAPLXM02
Include LMEVIEWSF01
Row 209
Regards,
Moderator message: not a proper question, please do more research before asking, study the entire dump text for hints, search for SAP notes.
Edited by: Thomas Zloch on May 13, 2011 1:32 PM -
Short dump after AC_FLUSH_CALL
Hi all,
I'm using Netweaver 04 and I've developed a report that displays a dynpro containing a dynamic document and it auto-refreshes itself through the CL_GUI_TIMER class.
After a period of correct working the report crashes with a short dump about the wrong exit of AC_FLUSH_CALL function module (CL_GUI_CFW->FLUSH method). sy-subrc = 2.
Can you help me? Thanks in advance.
AngeloMy monitoring application accesses each second a DB table to check if its contents are changed and dispay a particular record on the dynpro.
FILL_HEADER is fixed and FILL_VALUES can change.
This is most of PBO code:
SET PF-STATUS 'STATUS1100'.
SET TITLEBAR 'TITLE1100'.
CLEAR flag.
IF first = 'X'. " prima display
CLEAR: i_text, is_ma_data.
REFRESH: i_text, is_ma_data.
CREATE OBJECT head_cont
EXPORTING container_name = top_screen.
CREATE OBJECT values_cont
EXPORTING container_name = values.
CREATE OBJECT fill_header
EXPORTING no_margins = 'X'.
CREATE OBJECT fill_values
EXPORTING no_margins = 'X'.
CALL METHOD fill_header->initialize_document.
PERFORM fill_field_names.
CALL METHOD fill_header->merge_document.
CALL METHOD fill_header->display_document
EXPORTING
parent = head_cont
container = 'FILL_HEADER'
reuse_control = 'X'
reuse_registration = 'X'.
first = ' '.
ENDIF.
CALL METHOD fill_values->initialize_document
EXPORTING
background_color = bg_color.
PERFORM fill_field_values.
merge document
CALL METHOD fill_values->merge_document.
CALL METHOD fill_values->display_document
EXPORTING
parent = values_cont
container = 'FILL_VALUES'
reuse_control = 'X'
reuse_registration = 'X'.
ENDIF.
refresh
CREATE OBJECT gui_timer.
SET HANDLER event_handler->on_finished FOR gui_timer.
gui_timer->interval = timeout.
CALL METHOD gui_timer->run.
CALL METHOD cl_gui_cfw=>update_view.
Thanks.
Angelo -
Hi
I am getting a short dump "'DYNPRO_MSG_IN_HELP' "when i click '1 box pack' button in VL02N transaction during our upgrade system from 4.6C to ECC 6.0. When i go through the old SAP note - 401823, it says to add entries in VFBS transaction for all T185 entries for this kind of dumps. But i am missing entries for SAPMV50A, I0 and ZVPK combination at support pack level '14'(SAP_APPL) in our system.
Could anyone let me know the entries to be maintained for all the T185* tables mentioned in VFBS transaction.
(or) is there any OSS note already created for this issue? please let me know all the details.
Thank you,
AnilHi Laxmi,
We are already in Support pack. (SAPKH60014), and note which you given was SP - SAPKH60007, so this correction was already implemented in our system.
Is there a note/solution specific to '1 BOX PACK' dump and T185* table entry missing?
Let me know,
thank you,
Anil -
Short dump when '1 BOX PACK' clicked on VL02N, in ECC 6 system
Hi
I am getting a short dump "'DYNPRO_MSG_IN_HELP' "when i click '1 box pack' button in VL02N transaction during our upgrade system from 4.6C to ECC 6.0. When i go through the old SAP note - 401823, it says to add entries in VFBS transaction for all T185 entries for this kind of dumps. But i am missing entries for SAPMV50A, I0 and ZVPK combination at support pack level '14'(SAP_APPL) in our system.
Could anyone let me know the entries to be maintained for all the T185* tables mentioned in VFBS transaction.
(or) is there any OSS note already created for this issue? please let me know all the details.
Thank you,
AnilHi Laxmi,
We are already in Support pack. (SAPKH60014), and note which you given was SP - SAPKH60007, so this correction was already implemented in our system.
Is there a note/solution specific to '1 BOX PACK' dump and T185* table entry missing?
Let me know,
thank you,
Anil -
Custom error message in user exit is giving Short dump
Hi All,
We have a scenario where in if any user try to create/Change/Delete particular types of contract in SAP system we have to issue error message
saying ZIN/ZIR contract creation/Change/Deletion is blocked in SAP. This has to be done from the web application. So we are putting below code
in user exit MV45AFZZ in the form USEREXIT_SAVE_DOCUMENT_PREPARE.
CONSTANTS: lc_vbcpic01 TYPE sy-uname VALUE u2018VBCPIC01u2019, u201CWeb application user ID
lc_zin TYPE vbak-auart VALUE u2018ZINu2019,
lc_zir TYPE vbak-auart VALUE u2018ZIRu2019,
lc_text(32) TYPE c VALUE u2018Check long text for more detailsu2019.
DATA: l_uname TYPE sy-uname.
CLEAR: l_uname.
MOVE sy-uname TO l_uname.
*If user ID is not the Web application ID then block the creation/Change/Deletion
IF l_uname NE lc_vbcpic01
AND ( vbak-auart EQ lc_zin
OR vbak-auart EQ lc_zir ).
MESSAGE e830(zv) WITH lc_text.
ENDIF.
This code is working fine while creating/Changing the contract i.e. Giving us error message so that user wonu2019t be able to create/change the contract.
But when we delete the contract from VA42, Control is coming to this message statement and is giving Short dump. Below is the error analysis of the dump.
Error Analysis:
During "Exit Command" processing, the program tried to send a " " message.
This is not allowed at this point in processing.
The program had to be terminated.
Screen name.............. "SAPMV45A"
Screen number............ 4001
If any one has come across such scenario/any work around for this problem please let me know your inputs. Your inputs are highly appreciated.
I am working on 4.6C version of SAP.
Note: When i issue information/Warning message contract is getting deleted after displaying the message.
Thanks,
Vinod.I exactly replicated the same in DELETE_DOCUMENT also
I am getting the Dump. I tried with exit also , but it continued and deleted. To avoid deletion we have to use Leave program or LEAVE TO CURRENT TRANSACTION.
Delete Function is Defined as EXIT command. so it is not possible to give error message. To convice you i just copied demo program and raised the error message.
it is also giving the dump.
copy the demo program DEMO_DYNPRO_AT_EXIT_COMMAND and make this change , information to error .
MODULE cancel INPUT.
MESSAGE e888(sabapdocu) WITH text-001 ok_code input1 input2.
IF ok_code = 'CANCEL'.
CLEAR ok_code.
LEAVE PROGRAM.
ENDIF.
ENDMODULE.
and see... -
WBS Conversion FM using RFC Causing Short Dumps
Hello,
I have been trying to validate WBS element entries by using an RFC call to a FM on the back-end. However, I keep getting short dumps on the back-end system with 'Statement "MESSAGE E" is not allowed in this form.' message. The custom back-end FM calls one of the CPJN FMs like CONVERSION_EXIT* that deal with WBS elements.
So, I tried changing the custom FM to use the data element that does a the conversion instead of the FM. Now, I get a short dumps on the front-end with CALL_FUNCTION_REMOTE_ERROR with 'Key does not correspond to mask: B/0000-XXXXXXX.0.0.0' message.
Has anyone been successful without duplicating the CONVERSION_EXIT* FMs in order to validate a WBS element entry remotely?
Thank you in advance for any assistance.
Regards, Dean.Hello Dean
On ERP 6.0 (IDES) there is the RFC-enabled fm /SPE/WBS_ELEM_CONV_INT_EXT available.
If you feed the fm with an external ID it tries to convert it into the corresponding internal ID and vice versa. Perhaps this fm might be useful for you.
Probably the BAPI BAPI_PROJECT_EXISTENCECHECK is more useful (can be feed either with internal or external ID).
Regards
Uwe -
Hi,
In PO creation (ME21N/ME22N), i wanted to call custom report, mean while I have implemented one exit
"MM06E005 ->EXIT_SAPMM06E_006", in that, I called Z-program, in which a statement
call screen 100.
is there, which is causing the short dump.
Short dump Details:
The system attempted to use dynpro 0100 in program "SAPLXM06".
This dynpro does not exist.
In the same manner, if I call another function module it is not happening.
Please suggest me.My actual Intension is to popup a screen with a report in ME21N(PO creation), for that I have generated one normal report and called that report from the Exit I have told previously, In that report I have created 100 screen and called it.
When I am creating a PO, the screen calling statement there, is throwing a short dump.
Hope now you understood Everything.
Thank you for responding. -
GETWA_NOT_ASSIGNED_RANGE Short Dump in BW
Hi,
Recently, we have upgraded our BW system from SP10 to SP12 and done with Unicode Conversion on existing BW3.5
After this, while executing FI GL queries, they are displaying message: "Field Symbol has not been assigned" with short dump "GETWA_NOT_ASSIGNED_RANGE". I
I am attaching the few lines of short dump for yours reference.
Runtime Errors GETWA_NOT_ASSIGNED_RANGE
ShrtText
Field symbol has not been assigned.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLRRI4" had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program.
Error analysis
The system tried to access an anasigned field symbol (data segment number 32771).
The field symbol is no longer assigned, because a Unicode program previously tried to set the field symbol using an ASSIGN statement with an offset/length declaration. The memory addressed in this offset/length declaration, however, no longer lay within the valid range.
Information on where terminated
The termination occurred in the ABAP program "SAPLRRI4" in "CODE_TAB_SPLIT". The main program was "SAPMSSY1 ". The termination occurred in line 71 of the source code of the (Include) program "LRRI4U01" of the source code of program "LRRI4U01" (when calling the editor 710).
Source Code Extract
Line
SourceCde
41
42
DATA: L_S_CODEL TYPE RRI4_S_CODEL,
43
L_CODE TYPE RSSG_S_CODELINE,
44
L_I TYPE I.
45
FIELD-SYMBOLS: <L_SP>, <L_CODE>.
46
47
L_I = STRLEN( C_S_CODEL-LINE ).
48
IF L_I LE 72.
49
*................................... Zeile kurz also ok
50
L_CODE = C_S_CODEL-LINE.
51
APPEND L_CODE TO C_T_CODE.
52
53
ELSEIF C_S_CODEL-LINE CP '''''*' AND C_S_CODEL-LINE(1) NE ''''.
54
*................................... Zeile enthält '....', aber nicht
55
ganz vorne => ersten Teil abschneid
56
ASSIGN C_S_CODEL-LINE(SY-FDPOS) TO <L_CODE>.
57
L_CODE = <L_CODE>.
58
APPEND L_CODE TO C_T_CODE.
59
SHIFT C_S_CODEL-LINE BY SY-FDPOS PLACES.
60
if C_S_CODEL-LINE(1) eq '*'.
61
SHIFT C_S_CODEL-LINE right.
62
endif.
63
PERFORM CODE_TAB_SPLIT CHANGING C_S_CODEL
64
C_T_CODE.
65
ELSE.
66
*.................................... ab der Stelle 72 rückwärts ein
67
Space suchen und dort teilen
68
DO.
69
L_I = 72 - SY-INDEX.
70
ASSIGN C_S_CODEL-LINE+L_I(1) TO <L_SP>.
>>>>>
IF <L_SP> EQ SPACE.
72
ASSIGN C_S_CODEL-LINE(L_I) TO <L_CODE>.
73
L_CODE = <L_CODE>.
74
APPEND L_CODE TO C_T_CODE.
75
SHIFT C_S_CODEL-LINE BY L_I PLACES.
76
if C_S_CODEL-LINE(1) eq '*'.
77
SHIFT C_S_CODEL-LINE right.
78
endif.
79
PERFORM CODE_TAB_SPLIT CHANGING C_S_CODEL
80
C_T_CODE.
81
EXIT.
82
ENDIF.
83
ENDDO.
84
ENDIF.
85
ENDFORM.
Please help me to resolve this issue at earliest as its impacting the Business.
Best Regards,
Venkata Challapalli.Check OSS notes:
555143
838560 -
Short dump CONVT_CODEPAGE in transaction I18N
Hi,
I'm trying to install the french language into a Solution Manage 4.0 system.
SQL Server 2005 database + Windows 2003 X64
When I run I18N > I18N Menu > I18N Customizing > I18N System Configuration in order to activate french I have a dump (more details bellow).
Same error when I try to run report RSCPINST.
I'm running out of idea, I'm unable to find a way to solve this issue, anybody can help me ?
Thanks in advance,
V.Ch.
Short dump long text :
Runtime Errors CONVT_CODEPAGE
Except. CX_SY_CONVERSION_CODEPAGE
Date and Time 21.01.2008 22:02:16
Short text
A character set conversion is not possible.
What happened?
At the conversion of a text from codepage '4110' to codepage '4103':
- a character was found that cannot be displayed in one of the two
codepages;
- or it was detected that this conversion is not supported
The running ABAP program 'SAPLSCP2' had to be terminated as the conversion
would have produced incorrect data.
The number of characters that could not be displayed (and therefore not
be converted), is 1. If this number is 0, the second error case, as
mentioned above, has occurred.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_CODEPAGE', was not
caught in
procedure "CHECK_PROFILE" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Characters are always displayed in only a certain codepage. Many
codepages only define a limited set of characters. If a text from a
codepage should be converted into another codepage, and if this text
contains characters that are not defined in one of the two codepages, a
conversion error occurs.
Moreover, a conversion error can occur if one of the needed codepages
'4110' or '4103' is not known to the system.
If the conversion error occurred at read or write of screen, the file
name was 'G:\usr\sap\L1D\SYS\profile\DEFAULT.PFL'. (further information about
the file: "X 2673")
Missing RAISING Clause in Interface
Program SAPLSCP2
Include LSCP2U23
Row 103
Module type (FORM)
Module Name CHECK_PROFILE
Trigger Location of Exception
Program SAPLSCP2
Include LSCP2U23
Row 142
Module type (FORM)
Module Name CHECK_PROFILE
Source Code Extract
Line
SourceCde
112
fname = a_profilefilename.
113
parname = a_parname.
114
115
open dataset fname for input in text mode encoding default.
116
do.
117
read dataset fname into rec1.
118
if sy-subrc <> 0.
119
if sy-subrc = 8.
120
rec3 = 'OpenErr'.
121
exit.
122
elseif sy-subrc = 4.
123
rec3 = 'NotIn'.
124
exit.
125
else.
126
rec3 = 'rcNot0.'.
127
exit.
128
endif.
129
else.
130
if rec1 np '##*' and
131
rec1 cs parname.
132
rec3 = rec1.
133
exit.
134
endif.
135
endif.
136
enddo.
137
close dataset fname.
138
139
fname = a_defaultfilename.
140
open dataset fname for input in text mode encoding default.
141
do.
>>>>>
read dataset fname into rec1.
143
if sy-subrc <> 0.
144
if sy-subrc = 8.
145
rec2 = 'OpenErr'.
146
exit.
147
elseif sy-subrc = 4.
148
rec2 = 'NotIn'.
149
exit.
150
else.
151
rec2 = 'rcNot0.'.
152
exit.
153
endif.
154
else.
155
if rec1 np '##*' and
156
rec1 cs parname.
157
rec2 = rec1.
158
exit.
159
endif.
160
endif.
161
enddo.Hi,
Check [this note.|Note 990971 - Error in character conversion:CX_SY_CONVERSION_CODEPAGE dump] This will solve your problem.
Feel free to revert back.
--Ragu -
RE: Short dump after activation of BADI
Hi all,
We are getting short dumps in all the transactions after activating the BADI 'BADI_LAYER'
We are not able to execute any of the transactions.
The details of runtimeerror
Runtime Errors RAISE_EXCEPTION
Date and Time 30.07.2007 09:58:06
Short text
Exception condition "SINGLE_EXIT_MULTIPLY_ACTIVE" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
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
A RAISE statement in the program "CL_EXITHANDLER================CP" raised the
exception
condition "SINGLE_EXIT_MULTIPLY_ACTIVE".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct the error
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:
"RAISE_EXCEPTION" " "
"CL_EXITHANDLER================CP" or "CL_EXITHANDLER================CM001"
"GET_INSTANCE"
or
"CL_EXITHANDLER================CP" "SINGLE_EXIT_MULTIPLY_ACTIVE"
or
"SAPMF05A " "SINGLE_EXIT_MULTIPLY_ACTIVE"
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.
System environment
SAP-Release 700
Application server... "sapdevp"
Network address...... "192.168.0.205"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 80686"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "SAPDEVP"
Database type..... "ORACLE"
Database name..... "TDV"
Database user ID.. "SAPSR4"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 23:08:16"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10103_SHARE "
Patch level. 52
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 6271344
Heap.... 0
Page.... 57344
MM Used. 1728072
MM Free. 360856
User and Transaction
Client.............. 400
User................ "FIUSER01"
Language key........ "E"
Transaction......... "FB50 "
Program............. "CL_EXITHANDLER================CP"
Screen.............. "SAPMF05A 1010"
Screen line......... 7
Information on where terminated
Termination occurred in the ABAP program "CL_EXITHANDLER================CP" -
in "GET_INSTANCE".
The main program was "SAPMF05A ".
In the source code you have the termination point in line 145
of the (Include) program "CL_EXITHANDLER================CM001".
Source Code Extract
Line
SourceCde
115
SELECT SINGLE is_impl FROM badiisimpled INTO is_impl
116
WHERE badi_name = mig_badi_name.
117
IF sy-subrc NE 0.
118
not yet filled
119
is_impl = cl_enh_badi_tool_utilities=>update_badiisimpled( mig_badi_name ).
120
ENDIF.
121
122
IF is_impl = 'X'.
123
ok at least one implementation found
124
act_imp_existing = 'X'.
125
ENDIF.
126
127
ENDIF.
128
ENDIF.
129
ELSE.
130
131
check how many implementations exist for an exit
132
CALL METHOD cl_badi_flt_data_trans_and_db=>act_imps_per_flt_val
133
EXPORTING
134
runtime_call = seex_true
135
exit_name = exit_name
136
EXCEPTIONS
137
singular_exit_multiply_active = 1
138
no_active_implementation = 2
139
only_default_implementation = 3
140
OTHERS = 4.
141
CASE sy-subrc.
142
WHEN 0.
143
act_imp_existing = seex_true.
144
WHEN 1.
>>>>>
RAISE single_exit_multiply_active.
146
WHEN 2.
147
act_imp_existing = seex_false.
148
WHEN 3.
149
act_imp_existing = seex_false.
150
def_impl = seex_true.
151
WHEN 4.
152
RAISE data_incons_in_exit_managem.
153
ENDCASE.
154
155
new parameter considered for performance purposes
156
IF act_imp_existing = seex_true OR
157
def_impl = seex_true OR
158
null_instance_accepted = seex_false.
159
160
ok, then do your job
161
CREATE OBJECT exit TYPE (abs_type_classname).
162
CATCH SYSTEM-EXCEPTIONS move_cast_error = 1.
163
instance ?= exit.
164
ENDCATCH.
Contents of system fields
Name
Val.
SY-SUBRC
1
SY-INDEX
0
SY-TABIX
0
SY-DBCNT
2
SY-FDPOS
1
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
FSKB
SY-UCOMM
SY-TITLE
Enter G/L Account Document: Company Code TJ01
SY-MSGTY
S
SY-MSGID
B!
SY-MSGNO
015
SY-MSGV1
00001140
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20070730
SY-UZEIT
095806
SY-XPROG
SY-XFORM
Active Calls/Events
No. Ty. Program Include Line
Name
5 METHOD CL_EXITHANDLER================CP CL_EXITHANDLER================CM001 145
CL_EXITHANDLER=>GET_INSTANCE
4 METHOD CL_EXIT_MASTER================CP CL_EXIT_MASTER================CM004 2
CL_EXIT_MASTER=>CLASS_CONSTRUCTOR
3 METHOD CL_EX_FI_HEADER_SUB_1300======CP CL_EX_FI_HEADER_SUB_1300======CM003 53
CL_EX_FI_HEADER_SUB_1300=>IF_EX_FI_HEADER_SUB_1300~PUT_DATA_TO_SCREEN_PBO
2 FORM SAPMF05A MF05AF00_D0100_PRE_APPL_SUB_2 50
D0100_PRE_APPL_SUB_PBO
1 MODULE (PBO) SAPMF05A MF05AO00_D0100_PRE_APPL_SUB 10
D0100_PRE_APPL_SUB
Chosen variables
Name
Val.
No. 5 Ty. METHOD
Name CL_EXITHANDLER=>GET_INSTANCE
EXIT_NAME
BADI_LAYER
44445445452222222222
2149FC19520000000000
00000000000000000000
00000000000000000000
NULL_INSTANCE_ACCEPTED
2
0
0
0
ACT_IMP_EXISTING
2
0
0
0
INSTANCE
F0000000
F0000000
%_SPACE
2
0
0
0
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
SEEX_TRUE
X
5
8
0
0
SYST-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
<%_TABLE_BADIISIMPLED>
SY-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-SUBRC
1
0000
1000
SY-XPROG
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No. 4 Ty. METHOD
Name CL_EXIT_MASTER=>CLASS_CONSTRUCTOR
%_SPACE
2
0
0
0
SYST-REPID
CL_EXIT_MASTER================CP
4454545544554533333333333333334522222222
3CF5894FD13452DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-REPID
CL_EXIT_MASTER================CP
4454545544554533333333333333334522222222
3CF5894FD13452DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CL_EXIT_MASTER=>LAYER_EXIT
F0000000
F0000000
%_DUMMY$$
2222
0000
0000
0000
No. 3 Ty. METHOD
Name CL_EX_FI_HEADER_SUB_1300=>IF_EX_FI_HEADER_SUB_1300~PUT_DATA_TO_SCREEN_PBO
IM_BKPF
TJ01 2007SA00000000200707300400000000000000000000000000000000000000
2225433222222222233335433333333333333333333333333333333333333333333333333333333222222222222222
0004A01000000000020073100000000200707300400000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IM_X_NO_INPUT
2
0
0
0
FLT_VAL
IN
44
9E
00
00
<EXIT_OBJ>-IMP_CLASS
<FLT_CACHE_LINE>-OBJ
|
| F0000000 |
| F0000000 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| ME->INSTANCE_BADI_TABLE |
| Table[initial] |
| <EXIT_OBJ> |
| ??? |
| ?????? |
| ?????? |
| <%_L001> |
| ??? |
| ?????? |
| ?????? |
| RSJOBINFO |
| 00000000000000 ## |
| 2222222222222222222222222222222233333333333333222222222222222222222222222222222200 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| SY-REPID |
| CL_EX_FI_HEADER_SUB_1300======CP |
| 4454554454444455554533333333334522222222 |
| 3CF58F69F851452F352F1300DDDDDD3000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| <%_L001>-METHOD_NAME |
| ??? |
| ?????? |
| ?????? |
| EXIT_OBJ_TAB |
| Table[initial] |
| SY-SUBRC |
| 1 |
| 0000 |
| 1000 |
| ME |
|
F0000000
C0003000
SXRT_TRUE
X
5
8
0
0
No. 2 Ty. FORM
Name D0100_PRE_APPL_SUB_PBO
*BSEG-STBUK
2222
0000
0000
0000
%_DUMMY$$
2222
0000
0000
0000
SY-REPID
SAPMF05A
5454433422222222222222222222222222222222
310D605100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SYST-REPID
SAPMF05A
5454433422222222222222222222222222222222
310D605100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
KDBTAB-DMBTR
0.0.0.0.0.0.1.
0000000
000000C
%_SPACE
2
0
0
0
KDPTAB-BELNR
2222222222
0000000000
0000000000
0000000000
KDPTAB-GJAHR
0000
3333
0000
0000
0000
KDPTAB-BUZEI
000
333
000
000
000
KDBTAB-XRUND
2
0
0
0
SPACE
2
0
0
0
F05ACTRL
2
0
0
0
SYST
######################################ð#######################################~######### C####
00000000000000000000000000000000000000F0000000000000000000000000000000000000107000000050240000
000000200000000000002010100010000000000000000010400000000000000000000000000080E000200080030100
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000D000000C
BSED
0000000# ############## 0000000000000000
2222222222222222233333330200000000000000223333333333333333222222222222222222222222222222222222
00000000000000000000000000000C000000C000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000C0000000C000000C000000000000000000000000000000000000000000000000000000
SY-SUBRC
1
0000
1000
G_APPL_SUB_ACTIVE
X
5
8
0
0
CHAR_X
X
5
8
0
0
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
BKPF-BUKRS
TJ01
5433
4A01
0000
0000
BKPF
TJ01 2007SA00000000200707300400000000000000000000000000000000000000
2225433222222222233335433333333333333333333333333333333333333333333333333333333222222222222222
0004A01000000000020073100000000200707300400000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_APPL_SUB_DISABLE
2
0
0
0
T005-INTCA
IN
44
9E
00
00
No. 1 Ty. MODULE (PBO)
Name D0100_PRE_APPL_SUB
C_FIELD_DIALOG_ALL
BUTTON_DIALOG_ALL
4555445444444544422222222222222222222222222222222222222222222222222222222222222222222222222222
2544FEF491CF7F1CC00000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ab_jfune"
of the SAP kernel, in line 2561 of the module
"//bas/700_REL/src/krn/runt/abfunc.c#10".
The internal operation just processed is "FUNE".
Internal mode was started at 20070730095806.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=4436)
When : 7/30/2007 9:58:6.359
Threads : 2
Computer Name : SAPDEVP
User Name : SAPServiceTDV
Number of Processors: 4
Processor Type: x86 Family 6 Model 15 Stepping 6
Windows Version : 5.2 Current Build: 3790
State Dump for Thread Id 250c
eax=34d52300 ebx=000003f8 ecx=0001ccc0 edx=34d039e0 esi=000003f8 edi=00000000
eip=7c82ed54 esp=053fceb4 ebp=053fcf24 iopl=0 nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200297
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:053fceb4=7c822124
7c82ed5c 8d642400 lea esp,[esp] ss:6627b4c7=00002100
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
053fcf24 77e6ba42 000003f8 0001d4c0 00000000 053fcf5c ntdll!KiFastSystemCallRet
053fcf38 0100b3aa 000003f8 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
053fcf5c 0055b4ac 0055b4e5 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess
053fcf60 0055b4e5 7c38b5c8 7c38b5c8 7c38b5c8 01d35ab0 disp+work!NTStack
053fcf7c 0055b519 7c38b5c8 00000000 008536a8 7c38b5c8 disp+work!CTrcStack2
053fcf88 008536a8 7c38b5c8 00000000 005f0059 00300030 disp+work!CTrcStack
053fcfac 008569fa 6d1d037c 0000001b 00000000 01cfc168 disp+work!rabax_CStackSave [abrabax.c (6871)
053fd084 006aaaf4 0134837c 0134835c 00000a01 235f1640 disp+work!ab_rabax
053fd0c0 0067bb56 00000003 34cf5708 00000000 053fd128 disp+work!ab_jfune
053fd128 007af183 00000000 34cf5708 053fd274 34cf8c26 disp+work!ab_extri
053fd13c 00837a37 00000000 34cf7dd6 00596fa0 34cf68b4 disp+work!ab_xevent
053fd148 00596fa0 34cf68b4 000003db 34cf7dd6 00000000 disp+work!ab_dstep
053fd274 00597fa1 34cf5708 34cf5708 053ffd04 00597b13 disp+work!dynpmcal
053fd284 00597b13 34cf5708 34cf5708 00000003 053ffd04 disp+work!dynppbo0
053fd2a0 0056dcf1 34cf5708 0006e768 00000000 0000000c disp+work!dynprctl
053ffd04 00471848 00000013 07de0048 00000001 00494960 disp+work!dynpen00
053ffd14 00494960 0000000c 00000000 00000003 00000002 disp+work!Thdynpen00
053ffee0 00494ee2 00000001 00000000 00000000 00430000 disp+work!TskhLoop
053fff00 00421150 00000000 00000000 7ffd8000 053fff60 disp+work!ThStart
053fff14 00401080 00000003 003f6850 00000001 00000000 disp+work!DpMain
053fff60 011a94a0 00000003 003f6850 003f78f8 01bd5000 disp+work!nlsui_main
053fffc0 77e523e5 00000000 00000000 7ffd8000 88602680 disp+work!wmainCRTStartup
053ffff0 00000000 011a935d 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
State Dump for Thread Id 27bc
eax=00000001 ebx=00000103 ecx=fffffffe edx=003f01f8 esi=00000000 edi=00000000
eip=7c82ed54 esp=075dfec0 ebp=075dff04 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:075dfec0=7c821514
7c82ed5c 8d642400 lea esp,[esp] ss:6845e4d3=50004500
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
075dff04 010f7ffc 000006c0 00000000 00000000 003f77d0 ntdll!KiFastSystemCallRet
075dff84 7c349565 00000000 00000000 00000000 0587ff08 disp+work!SigIMsgFunc
075dffb8 77e6608b 0587ff08 00000000 00000000 0587ff08 MSVCR71!endthreadex
075dffec 00000000 7c3494f6 0587ff08 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
SAPMF05A
0
22.05.2007
11:37:49
1563648
E
1
Prg
SAPMSSYD
0
10.01.2007
12:33:28
21504
E
2
Prg
SAPFSYSCALLS
0
09.09.2004
14:18:32
8192
E
3
Typ
TFDIR
0
13.02.2005
17:31:57
3072
4
Prg
SAPLAPAR_EBPP_SERVICES
4
03.01.2007
11:23:55
114688
E
5
Typ
T042ZEBPP
0
08.01.2002
14:42:24
2048
6
Typ
T020
0
24.02.1999
03:17:19
3072
7
Typ
RFOPT2
0
11.12.2003
15:00:17
5120
8
Prg
SAPFF001
0
22.05.2007
11:37:49
195584
E
9
Typ
SWOTOBJID
0
04.05.1995
15:20:52
2048
10
Prg
SAPLSWOR
10
10.01.2007
12:33:34
292864
E
11
Typ
TFBUF
0
30.11.1998
22:08:34
3072
12
Typ
ACC_KONTEXT
0
08.01.2003
17:30:26
3072
13
Typ
BKPF
0
13.03.2006
11:01:29
18432
14
Prg
SAPLFACSCORE
14
01.12.2006
22:00:12
13312
E
15
Typ
T001
0
25.08.2005
22:03:13
13312
16
Prg
SAPLACHD
16
03.01.2007
11:23:55
51200
E
17
Prg
SAPFSPOR
0
09.09.2004
14:18:32
15360
E
18
Prg
SAPLSCNT
18
18.02.2005
14:16:06
30720
E
19
Typ
DYCBOX
0
20.08.1998
11:16:53
3072
20
Prg
SAPLSVSM
20
18.02.2005
14:16:06
27648
E
21
Prg
SAPLSGUI
21
10.01.2007
12:33:33
82944
E
22
Prg
SAPLSTTM
22
05.07.2005
13:10:18
69632
E
23
Prg
SAPLSBDC
23
05.07.2005
13:10:18
44032
E
24
Prg
CL_DATAPROVIDER===============CP
24
28.02.2005
21:00:46
49152
E
25
Prg
%_CCNTL
24
18.02.2005
14:15:08
15360
E
26
Typ
OBJ_RECORD
0
14.02.1998
08:30:43
2048
27
Prg
SAPLSTUP
27
08.03.2005
19:04:31
73728
E
28
Prg
SAPLCNDP
28
01.12.2006
22:04:33
193536
E
29
Prg
SAPSHDTV
18
05.01.2005
16:26:16
33792
E
30
Typ
SHDSTU
0
14.12.1998
23:15:34
2048
31
Typ
SHDSTCIU
0
14.12.1998
23:15:34
2048
32
Prg
SAPFGUICNTL
0
18.02.2005
14:15:08
24576
E
33
Prg
SAPLOLEA
33
05.07.2005
13:10:18
96256
E
34
Prg
SAPLSFES
34
10.01.2007
13:26:20
256000
E
35
Prg
SAPLSPLUGIN
35
09.09.2004
14:18:36
8192
E
36
Typ
ARFCRDATA
0
13.02.2005
18:20:24
7168
37
Prg
SAPLGRFC
37
13.02.2005
18:20:25
16384
E
38
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
39
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
40
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
41
Typ
ACGL_HEAD
0
11.12.2003
14:59:21
8192
42
Typ
RF05A
0
11.04.2005
11:50:21
38912
43
Typ
TCURC
0
01.12.1999
12:14:40
2048
44
Prg
SAPLFAGL_ACTIVATION_SERVICES
44
30.04.2007
17:00:55
45056
E
45
Prg
SAPLSTR9
45
09.05.2006
10:39:47
39936
E
46
Prg
CONTEXT_X_TR_SYS_PARAMS
45
09.05.2006
10:39:47
40960
E
47
Typ
TCONT
0
09.09.2004
14:18:43
2048
48
Typ
CONTEXTB
0
09.09.2004
14:15:52
6144
49
Typ
FAGL_ACTIVEC
0
19.08.2004
16:55:10
5120
50
Typ
FAGL_CHECK_SETUP
0
11.12.2003
15:01:05
2048
51
Prg
SAPLSHD0
51
03.01.2007
06:52:22
232448
E
52
Prg
SAPLBFFM3
52
10.01.2007
13:15:21
169984
E
53
Typ
OFIWA
0
15.04.1998
00:11:05
2048
54
Typ
FTEXTS
0
20.08.2001
12:13:26
3072
55
Prg
SAPLITSR
55
10.01.2007
14:23:52
107520
E
56
Typ
FMRFC
0
13.08.1997
12:32:59
2048
57
Typ
TBE01
0
20.01.2003
16:41:38
2048
58
Typ
TBE31
0
03.09.1997
03:01:11
2048
59
Typ
TBE31
0
03.09.1997
03:01:11
2048
60
Typ
TBE11
0
03.09.1997
03:01:06
2048
61
Prg
CONTEXT_X_SP_INFO
55Hello Sowmya
The BAdI BADI_LAYER is not defined for <b>Multiple-Use</b> (see checkbox on tabstrip <i>Attributes</i>).
Apparently you have created <i>several </i>implementation of this BAdI and activated <i>several </i>(at least 2) of these implementations.
If you inactivate all except a single implementation the BAdI (and all transactions using this BAdI) should work again.
Regards
Uwe -
How to avoid short dump in ECC 5.0
Hi
Can anyone tell me how to avoid short dump in ECC 5.0
I'm told we can avoid program going to short dump, instead IT WILL GRACEFULLY EXIT..Hi
By implementing the code as for every unsuccess/failure conditions control has come out of the program. then only u can avoid dumps even though u code the not perfect functionality.
Regards,
kumar -
Short dump while reconstructing request in ODS
Hi
I had loaded a request into a few ODS, but later found i had to do some changes to the PSA manually, so i deleted the request from all the ODS and modified the records in the PSA.
Now when i try reconstruction it gives a short dump in one of the ODS with message "Exception condition "NOT_EXIST" raised. ".
Data from this ODS was further loaded to a few other targets as delta and while deleting the request it gave a message saying the delta will be deactivated, I said Ok and the request was deleted.
I was able to reconstruct the request in all the other ODS and cubes without any issues.
what could be the problem???
Regards
SujaiHi
I am doing PSA to ODS. The data is available in PSA. the reconstruction went thru fine in the other targets. but when i try it in the ODS that i want it goes for a dump. This is where the error occurs.. shown in the dump..
select * from rsreqicods into table l_t_rsreqicods where
tabname = i_dta and
typ = 'I' and
odssid = i_odssid.
if sy-subrc <> 0.
raise not_exist. -----> Error in this line
exit.
endif.
Regards
Sujai
Maybe you are looking for
-
Since the upgrade to 3.6.9 was released today, we are now getting the following error on one of our secure websites. Our SSL certificate has been in place since March and is generated by Thawte. This site works fine in Internet Explorer and worked fi
-
Please check the below Cursor Procedure and correct that code Please
Hai Every One. Please check the below code I have two issues in that code 1. Invalid cursor 2. Record must be enter Please correct this code and send me pls its urgent.I cont understand where i done mistake PROCEDURE fetch_detail_PROC IS cursor c1 is
-
General problem : how to get start "grid computing"?
hi all, please read this and giud me kindly. i m university student and my final year project title is "new middleware models such as "grid services on p2p". this tittle was proposed by our acadamic staff and then i must go through this. now i have t
-
Does Endeca Server(Mdex) in latitude support East Asian languages?
Hi, we're on latitude 2.2.2 the Mdex engine in Latitude is different from the one in Infront, without Basic RLP to do the indexing and word segmentation for East Asian Language. In this way latitude cannot support Chinese or Japanese keyword search.
-
TS3274 Screen still won't rotate on iPad
Screen won't rotate. The settings show it is unlocked & it's not set to the mute button. Tried resetting iPad based on other threads & it still won't rotate. Any ideas? Thank you.