Short Dump in extractor
Hello Friends,
I am trying to create an extractor in R/3 for BW. This extractor would be based on a function module. The function module is ready and I have seperately tested the function module(FM). It is working fine and fetching the data.
However, since this FM is for an extractor, it requires a table 'E_T_DATA' as a parameter. I have defined the table E_T_DATA as a parameter in the FM.
Now when I go to transaction RSA3 and try to test the extractor it gives me a short dump. It says the following:
When calling the function module "ZTEST_FM_CONTRACTOR", one of the parameters needed according to the interface description was not specified.
This parameter was "E_T_DATA".
Now if I test the extractor in RSA3 in the debuging mode, I find that following:
<i>CALL FUNCTION S_FNAME
EXPORTING
I_REQUNR = S_S_IF_SIMPLE-REQUNR
I_DSOURCE = S_S_IF_SIMPLE-DSOURCE
I_MAXSIZE = S_S_IF_SIMPLE-MAXSIZE
I_INITFLAG = S_S_IF_SIMPLE-INITFLAG
TABLES
I_T_SELECT = S_S_IF_SIMPLE-T_SELECT
I_T_FIELDS = S_S_IF_SIMPLE-T_FIELDS
EXCEPTIONS
NO_MORE_DATA = 1
ERROR_PASSED_TO_MESS_HANDLER = 2
OTHERS.</i>
In the above code <i>S_FNAME</i> holds the name of the FM ZTEST_FM_CONTRACTOR, which I have created. But if we see here the call to my FM is not exporting "E_T_DATA". But still it is giving a short dump saying "E_T_DATA" was not exported. Also since it is the SAP code I cannot even change it.
I hope friends, you are understanding what I am trying to communicate. Please assist me in this. Thanks!
Regards,
Prem.
Hi Premanand,
PLease refer the below lilnk to get a better understanding of the FM Extrcator.
FM Extraction -->
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
Hope this helps.
Thanks & Regards,
Sh
Similar Messages
-
Short Dump, Exception condition "NOT_EXIST" raised
Dear Colleagues!
I am having a problem with short dump, I am getting the message Exception condition "NOT_EXIST" raised.
I am trying to load data to ODS with full load and filtering via a DTP.
In the monitoring the load doesn't even get started.
I have already loaded data succesfully in this ODS... But now it doesn't work anymore..
I also tried to replicate and active all the rules and objects again.
And in the source system if I test the extractor it works fine.
I saw an earlier thread on this issue, and it recommended programs ZDMDELTAREPAIR or RSBDELTAREPAIR, but this thread was especially for BW 3.5. We are using 7.0 and have SP10. Are these programs still valid or is there another note for 7.0?
Hope you can help!
Regards Silje
Does anyone have any ideas?
regards, UrosHi again,
I tried RSBDELTAREPAIR and it worked!
Thanks to the forum again!
Silje -
Short dump error when extracting delta records from R/3
I am working on BW 3.5 and I am facing some short dump error when extracting delta records from the r/3 to BW.
Below is the error message
Kindly do the needful ASAP.
Job started
Step 001 started (program SBIE0001, variant &0000000024277, user ID BWREMOTE)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0ISCM_PAYMENT_01
Current Values for Selected Profile Parameters *
abap/heap_area_nondia......... 2000000000 *
abap/heap_area_total.......... 2000000000 *
abap/heaplimit................ 40000000 *
zcsa/installed_languages...... DE *
zcsa/system_language.......... E *
ztta/max_memreq_MB............ 2047 *
ztta/roll_area................ 6500000 *
ztta/roll_extension........... 2000000000 *
2,454 LUWs confirmed and 2,454 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DAT
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelledHi,
I look at the transaction ST22 to see which type of error has given you. Take a look at the notes to correct the error.
Another option is to look at OSS notes, because the error is giving you a standard extractor.
Greetings, -
Short dump while extracting data
Hi,
When i extract the data from the datasource 2lis_05_item in rsa3 i m getting the following short dump. Can anyone tell what to do in this case?
Runtime Errors CONNE_IMPORT_WRONG_STRUCTURE
Exceptn CX_SY_IMPORT_MISMATCH_ERROR
Date and Time 06.12.2006 09:42:15
ShrtText
Error when importing object "MC05Q00ITM_TAB".
What happened?
Error in ABAP application program.
The current ABAP program "SAPLMCEX" had to be terminated because one of t
statements could not be executed.
This is probably due to an error in the ABAP program.
When attempting to import data, the
structure of the complex object "MC05Q00ITM_TAB" was not compatible with
target object.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ER
was neither
caught nor passed along using a RAISING clause, in the procedure
"MCEX_BW_LO_API" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
When attempting to import data, the structure of the complex object
"MC05Q00ITM_TAB"
was not compatible with the target object. The error occurred with
component no. 32.
sing RAISING Clause in Interface
Program SAP
Include LMC
Row 5
Module type (FU
Module Name MCE
gger Location of Exception
Program SAP
Include LMC
Row 241
Module type (FU
Module Name MCE
rce Code Extract
e SourceCde
11 endif.
12 enddo.
13 END-OF-DEFINITION.
14 ***** end macro *****I suppose that you are doing enhancement to your datasource 2LIS_02_ITM
Have you done the following steps in the extractor:
1. Append the new field in MC02M_0ITM structure
2. Append the new field in MCEKPO structure
3. Use Tcode LBWE and expand the Purchsing to get 2LIS_02_ITM and click on the Datasource to uncheck the 'hide' and 'fields only'
4. Activate the data source, by using Tcode RSA5
3. After that I have make changes to the user-exit to add logic for the new field
Do remember to carry out the following steps before you modify the Extraction structure:
1. Make sure that the following steps are carried out at a time when no updates are performed so that no data is lost.
2. Start the update collective run directly from within the Customizing Cockpit. Up to PI(-A) 2001.2 , this collective run exclusively concerns the V3 update. As of PI(-A) 2002.1, depending on the update mode setting of the application, the collective run concerns either the V3 update or the update from the extraction queue ("Delta Queued", see Note 505700).
3. Load all data of the respective DataSource into the BW System.
Hope it helps.
regards
Vinod -
Short dump in RSA3 --Z Data Source
Hi,
I created a Z data source based on view and i appended extract structure to insert ZZ fields.
When i execute the data source it is showing me short dump how shall i proceed
I checked the view conditions and it is extracting data and showing now error and i checked the enhancements i have written in CMOD and checked the program it is displaying No syntax errors
Please advise me on how to correct the errors....
If need further info of short dump please ask
Runtime Error DBIF_RSQL_INVALID_RSQL
Exception CX_SY_OPEN_SQL_DB
What happened?
Error in ABAP application program.
The current ABAP program "SAPLRSA3" had to be terminated because one of the
Statements could not be executed.
Error analysis
An exception occurred. This exception is dealt with in more detail belo.The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', waS neither caught nor passed along using a RAISING clause, in the procedure "RSA3_GEN_GET_DATA" "(FUNCTION)"
Since the caller of the procedure could not have expected this exceptio to occur, the running program was terminated.
The reason for the exception is:
The data read during a SELECT access could not be inserted into the target field.
Either conversion is not supported for the target field's type or the target field is too short to accept the value or the data are not in a form that the target field can accept.
Information on where terminated
The termination occurred in the ABAP program "SAPLRSA3" in "RSA3_GEN_GET_DATA".
The main program was "RSFHGEN2 ".
The termination occurred in line 226 of the source code of the (Include)
program "LRSA3U03"
of the source code of program "LRSA3U03" (when calling the editor 2260).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "RSA3_GEN_GET_DATA" "(FUNCTION)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLRSA3 ". Its source code starts in line 5
of the (Include) program "LRSA3$03 ".
Program
002150
002160 CASE G_S_INTERFACE-UPDMODE.
002170 WHEN 'F' OR 'C' OR 'I'.
002180 * First data package -> OPEN CURSOR
002190 IF G_COUNTER_DATAPAKID = 0.
002200 * Open Cursor for dynamical SELECT
002210 OPEN CURSOR WITH HOLD G_CURSOR FOR
002220 SELECT * FROM (G_S_OLTPSOURCE-EXTRACTOR)
002230 WHERE (L_T_DYNAMIC_SELECT).
002240 ENDIF.
002250 * Fetch first data package
> FETCH NEXT CURSOR G_CURSOR
002270 APPENDING CORRESPONDING FIELDS OF TABLE E_T_DATA
002280 PACKAGE SIZE G_S_INTERFACE-MAXSIZE.
002290 IF SY-SUBRC <> 0.
002300 RAISE NO_MORE_DATA.
002310 ENDIF.
002320 G_COUNTER_DATAPAKID = G_COUNTER_DATAPAKID + 1.
002330 WHEN 'D'.
002340 PERFORM FETCH_GEN_DELTA IN PROGRAM (L_GEN_PROGID)
002350 TABLES E_T_DATA
002360 L_T_DYNAMIC_SELECT
002370 G_T_FIELDS
002380 USING G_S_INTERFACE-MAXSIZE
002390 CHANGING L_FLG_NO_MORE_DATA.
002400 IF L_FLG_NO_MORE_DATA = 'X'.
002410 IF NOT L_T_BDCPS[] IS INITIAL.
002420 L_T_BDCPS-PROCESS = SBIWA_C_FLAG_ON.
002430 MODIFY L_T_BDCPS
002440 TRANSPORTING PROCESS WHERE PROCESS = SBIWA_C_FLAG_OFF.Hello,
This thread is answered. Was it the table space or something else?
We may have a similar issue as recently posted in thread:
"Short dump in SAP R/3: SQL statement buffer overflow?"
Best regards
Thomas -
Short Dump Error when we check the Data Source in RSA3
Hi. Experts.
We are using Data Source 2Lis_13_VDITM and when we try to check in RSA3
for recorts it is going short dump. I am just providing the error information.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in procedure "MCEX_BW_LO_API" "(FUNCTION)", 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:
When importing the object "MC13VD0ITM_TAB", the component no. 96 in the dataset has a different type from the corresponding component of the target object in the program "SAPLMCEX".
The data type is "N" in the dataset, but "X" in the program.
Since I don't have much knowledge in ABAP, Please help me out regarding this issue. Suggest me possible solution and let me know if you need any further information.Hi,
Try adding a TRY CATCH block in the extractor function module to catch the exception.
For the type mismatch you will have to make sure the variables are of same type or they can be type converted.
Use the debug mode of RSA3 to find what data is being exchanged.
You will need to change your extractor to avoid the dump.. or ensure that the value being passed to that object is correctly being passed(correct format)
Cheers
Kiran -
LOAD_PROGRAM_NOT_FOUND Short dump in R/3
Hi frnds,
I am facing some short dump problem while loading the data from R/3 BW, its a master data.
The short dumps are LOAD_PROGRAM_NOT_FOUND and RAISE_EXCEPTION in R/3.
Not able to find the exact problem and please suggest some OSS Notes.
Thanks
Harihi Hari,
check if helps oss note 899405-Master data extrctn: LOAD_PROGRAM_NOT_FOUND in source system
Symptom
You are loading master data in delta mode from an SAP source system. The DataSource uses generic extraction in the process.
The request is displayed in the monitor as being incorrect. The status indicates that the extraction process has probably terminated with a runtime error.
In the source system, you find the runtime error LOAD_PROGRAM_NOT_FOUND with the exception CX_SY_PROGRAM_NOT_FOUND. The point of termination is in the function module RSA3_GEN_GET_DATA.
The short dump occurs only if there is no data available for the delta.
Other terms
OLTP, extractor, data extraction, DataSource, service API, SAPI, dump, SAPLRSA3, LRSA3U03, RSAPTM2, EXTRACTOR_FETCH, EXTRACTOR_INIT, NO_MORE_DATA
Reason and Prerequisites
This is caused by a program error.
When you implemented Note 853001, calls for function modules were relocated to subroutines. This changed the query for the exception NO_MORE_DATA in such a way that it is not caught when the extractor is initialized. The extraction process then tries to start the program, but the program has not been generated because data is missing. The system issues the short dump.
Solution
After you have implemented the correction specified below, you must reactivate the transfer rules for the affected DataSource. It is only by doing this that the correction is also implemented in the generated program for the extraction process.
To correct the problem, you need to have Support Package 07 in the relevant source system Service API 7.00. The attached composite note informs you of the software components that contain Service API 7.0 and specifies the corresponding Support Packages for these components.
As an alternative, you can also implement the advance correction from the attachment.
You must implement the correction in the BW system only if it is affected in its role as a source system for itself (myself connection) or for another BW system.
Note: Service API is an internal component. It is not delivered separately, but as part of other software components: PI, CRM, PI_BASIS and a number of others. For this reason, a composite note has been created which tells you in which Support Packages of the above-mentioned software components the SAP correction note is contained. However, the composite note is not released until the release date of the corresponding SAPI Support Package. Different SAPI versions are delivered for Basis Releases 3.1I, 4.0B, 4.6D, 6.20 and 6.40. The version for 4.0B is also valid for R/3 Releases 4.6B and 4.6C. -
Short dump in delta extract using bgRFC in NW 2004s
Short dump in delta extract after Support Pack install, using bgRFC.
InfoSet Query extractor from Z-table residing on BW system into ODS.
Init and Full loads load successfully, delta loads short dump.
"MESSAGE_TYPE_X"
"SAPLARFC" or "LARFCU25"
"TRFC_SET_QUEUE_RECEIVER_LIST"
Problem began after support pack install, from SP 9 to SP 12. Switched to Classic RFC in SM59, seemed to correct this extractor but caused problems in other extractors.Hi Kevin,
check out this note: https://websmp205.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1054970&_NLANG=EN
it might help.
regards
Siggi -
Short Dump testing 0CRM_SALES_ACT_1 Datasource Extraction
Hi
Please can someone assist with the following problem in CRM 4.0. Using transaction RSA6-Extractor Checker S-API for 0CRM_SALES_ACT_1, we get a short dump when clicking on 'Extraction'. The following error message is displayed.
'An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE',
was neither
caught nor passed along using a RAISING clause, in the procedure "INSTANTIATE"
"(FORM)"
Any assistance is much appreciated.
Thanks
NeilResolved.
-
Load getting failed due to short dump
Hi All,
Process Chain is getting failed due to following short dump Include Report LFZI_CA_PCA_DERIVATIONSU37 not found. Please suggest on rectifying this dump. Its a delta load.
Regards,
AsimHi All
As requested please find details short dump below. And datasource name is this GECPC_GLPCP and its extractor is ZPCC_V_GLPCP.
Short text
Syntax error in program "SAPLZFI_CA_PCA_DERIVATIONS ".
hat happened?
Error in the ABAP Application Program
The current ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLZFI_CA_PCA_DERIVATIONS " in
include "LZFI_CA_PCA_DERIVATIONSUXX " in
line 77:
"INCLUDE report "LZFI_CA_PCA_DERIVATIONSU37" not found"
The include has been created and last changed by:
Created by: "SAP* "
Last changed by: "SAP* "
Error in the ABAP Application Program
The current ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "SAPLZFI_CA
You can also perform the syntax check from the ABAP Edito
If the problem persists, proceed as follows:
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 lo
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following syntax error was
"INCLUDE report "LZFI_CA_PCA_DE
How to correct the error
Probably the only way to elimin
If you cannot solve the problem
notification to SAP, include th
1. The description of the curre
To save the description, cho
(Unconverted)".
2. Corresponding system log
Display the system log by callin
Restrict the time interval to 10
ter the short dump. Then choose "
nconverted)".
If the problem occurs in a probl
ogram: The source code of the pro
In the editor, choose "Utilities
ilities->Upload/Download->Downloa
Details about the conditions und
tions and input led to the error.
Information on where terminated
Termination occurred in the ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" - in
"START_ROUTINE".
The main program was "RSBATCH_EXECUTE_PROZESS ".
In the source code you have the termination point in line 102
of the (Include) program "ZFICA_DERIVE_PCA_OBJECTS_S".
The program "GP9IQHCDEPFH201E24O25IAYXXW" was started as a background job.
Job Name....... "BIDTPR_6726959_1"
Job Initiator.. "ALEREMOTE"
Job Number..... 17271800
Line SourceCde
72 ASSIGN 'L_DERIVE_CHRT_ACCTS-UPD_CHRT_AC
73 assign (<derive_chrt_accts_field>) to
74 IF <derive_chrt_accts> IS ASSIGNED.
75 zzi_attributes_upd-chrt_accts_upd = '
76 ENDIF.
77 zzi_attributes_upd-/bic/gactivity_upd
78 zzi_attributes_upd-/bic/gfactv_upd
79 zzi_attributes_upd-/bic/gglobacct_upd
80 zzi_attributes_upd-/bic/ggforacc_upd
81 zzi_attributes_upd-/bic/ggrracc_upd
82 zzi_attributes_upd-/bic/ggra_code_upd
83 zzi_attributes_upd-/bic/gsegmtion_upd
84 zzi_attributes_upd-/bic/ggaapflg_upd
85 zzi_attributes_upd-/bic/gsub_item_upd
86 zzi_attributes_upd-/bic/gsegmnt_upd
87 zzi_attributes_upd-/bic/gacctgrp_upd
88 zzi_attributes_upd-comp_code_details_up
89 zzi_attributes_upd-gbfi0600_upd
90 zzi_attributes_upd-/bic/zaccsuf_upd
91 zzi_attributes_upd-/bic/gconunit_upd
92 zzi_attributes_upd-/bic/gtpunit_upd
93 *--------------------------------------
94 * Store a copy of the source fields if
95 *--------------------------------------
96 MOVE-CORRESPONDING <source_fields> TO z
97 CLEAR zze_attributes.
Runtime Errors SYNTAX_ERROR
Date and Time 04.08.2014 17:27:39
98 *----------------------------------------------------------------------*
99 * Derive all PCA fields for reporting
100 *----------------------------------------------------------------------*
101
>>>>> CALL FUNCTION 'ZFI_CA_DERIVE_PCA_ATTRIBUTESII'
103 EXPORTING
104 i_zfi_ca_pca_attributes = zzi_attributes
105 i_zfi_ca_pca_attributes_upd = zzi_attributes_upd
106 msgty = 'I'
107 recno = <source_fields>-record
108 IMPORTING
109 e_zfi_ca_pca_attributes = zze_attributes
110 TABLES
111 monitor_recno = lt_monitor_recno.
112
113 *----------------------------------------------------------------------*
114 * On the recurrsive load delete entries where the data is the same
115 *----------------------------------------------------------------------*
116 IF zzg_realignment_run = 'X'.
117 IF zzi_attributes = zze_attributes.
118 DELETE source_package INDEX la_tabix.
119 ELSE.
120 MOVE-CORRESPONDING zze_attributes TO <source_fields>.
121 ENDIF.
SY-SUBRC 0
SY-INDEX 3
SY-TABIX 1
SY-DBCNT 10
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Execute Batch Proces
SY-MSGTY E
SY-MSGID R7
SY-MSGNO 057
SY-MSGV1 ZBAL_LC
SY-MSGV2 A
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20140804
SY-UZEIT 172720
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXIT
No. Ty. Program Include Line
Name
8 FUNCTION GP9IQHCDEPFH201E24O25IAYXXW ZFICA_DERIVE_PCA_OBJECTS_S 102
START_ROUTINE
7 METHOD GP9IQHCDEPFH201E24O25IAYXXW ZFICA_DERIVE_PCA_OBJECTS_S 102
LCL_TRANSFORM=>START_ROUTINE
6 METHOD GP9IQHCDEPFH201E24O25IAYXXW GP9IQHCDEPFH201E24O25IAYXXW 1299
LCL_TRANSFORM=>EXECUTE
5 METHOD CL_RSTRAN_TRFN_CMD============CP CL_RSTRAN_TRFN_CMD============CM005 70
CL_RSTRAN_TRFN_CMD=>IF_RSBK_CMD_T~TRANSFORM
4 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM00Q 93
CL_RSBK_PROCESS=>PROCESS_REQUEST
3 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM002 13
CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~EXECUTE
2 FUNCTION SAPLRSBATCH LRSBATCHU13 437
RSBATCH_EXECUTE_PROCESS
1 EVENT RSBATCH_EXECUTE_PROZESS RSBATCH_EXECUTE_PROZESS 374
START-OF-SELECTION
REQUEST
DTPR_1FR9TKO2U6M616ATG9C2EYKRH
455553453544353433345434345454
4402F16294BF256D61614793259B28
000000000000000000000000000000
000000000000000000000000000000
DATAPACKID
000001
333333
000001
000000
000000
MONITOR
Table[initial]
SOURCE_PACKAGE
3000000001012P2013K4AU0ACD 2013005 00 0
3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
300000000101202013B415013402013001000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
300000000101202013B415013402013002000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
300000000101202013B415013402013003000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
300000000101202013B415013402013004000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000
00000000000000000000000000000000000
33333333333335333343453444233333332
300000000101202013B4150134020130050
00000000000000000000000000000000000
00000000000000000000000000000000000
Table IT_110723[600000x1144]
{A:114*\TYPE=%_T00003S00000115O0000
Table reference: 3570
TABH+ 0(20) = 90A161080000000060C1
TABH+ 20(20) = F20D000083B00100C027
TABH+ 40(16) = 03730000242D00000400
store = 0x90A1610800000000
ext1 = 0x60C1190C00000000
shmId = 0 (0x00000000)
id = 3570 (0xF20D0000)
label = 110723 (0x83B00100)
fill = 600000 (0xC0270900)
leng = 1144 (0x78040000)
loop = 128 (0x80000000)
xtyp = ROL.115.11556
occu = 4 (0x04000000)
accKind = 1 (ItAccessStand
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniNo)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
stMode = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
isUsed = 1
isCtfyAble = 1
hasScndKeys = 0
hasRowId = 0
scndKeysOutdated = 0
scndUniKeysOutdated = 0
----- Shareable Table Header Data -----
tabi = 0xB008190C00000000
pgHook = 0x404CE73B00000000
idxPtr = 0x0000000000000000
id = 61767 (0x47F10000)
shmTabhSet = 0x0000000000000000
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 606204 (0xFC3F0900)
lineAlloc = 600004 (0xC4270900)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
rowId = 18446744073709551615
scndKeyAdmin = 0x0000000000000000
----- 1st level extension part --------
regHook = 0xC8C0190C00000000
collHook = 0x0000000000000000
ext2 = 0x0000000000000000
RI-CLUSTR
0
00
00
ZE_ATTRIBUTES
00000
22222222222222222233333
00000000000000000000000
00000000000000000000000
00000000000000000000000
ZI_ATTRIBUTES
AU0A 070221000020130
45342222333333333333333
15010000070221000020130
00000000000000000000000
00000000000000000000000
ZI_ATTRIBUTES_UPD
XXXXX XXXXXX XX XXXX
55555255555522552555522
88888088888800880888800
00000000000000000000000
00000000000000000000000
SOURCE_FIELDS>-RECORD
1
0000
1000
T_MONITOR_RECNO
Table[initial]
ZG_REALIGNMENT_RUN
2
Regards,
Asim
GECPC_GLPCP -
Short dump 'Table does not exist in database'
Hello All,
When a report is executing it is going to short dump by saying 'Table does not exist in database'. As per the short dump analysis this issue is happening because of the following Native SQL statement statement :
Program : %_T050N0 (This is a dynamic program generating by SAP )
Form Name : DYN_LIC_SEL_TOT
exec sql performing LOOP_MOVE_WRITE_ISAP.
select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty into :dcat-lplate, :dcat-matnr,
:dcat-werks, :dcat-charg, :dcat-holdflag,
:dcat-qty from ZLICENSE_R2 where itm_num = :p_matnr and
model_lot = :p_charg
endexec.
As per the customer this issue occurring since they migrated the SAP back-end data base from Oralce to DB6. Here I felt that ZLICENSE_R2 is not migrated from the Oracle to DB6. But as per the BASIS Team, even this table was not maintained in Oracle also. If the table was not maintained in the Oracle, this issue should have been there even before migration also.
Following is the short dump details:
Short text
Table does not exist in database.
What happened?
The table or view name used does not
exist in the database.
The error occurred in the current database connection "DEFAULT".
What can you do?
Check the spelling of the table names in your report.
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
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_NATIVE_SQL_ERROR', was not
caught in
procedure "DYN_LIC_SEL_TOT" "(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:
Triggering SQL statement: "select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty from ZLICENSE_R2 where itm_num = ? and model_lot = ? "
Database error code: "-204"
Could you please let me know what might be the reason for this issue.
Many Thanks in Advance.Transaction SE11, input ZLICENSE_R2 for table name, and display the table. Did the table display? If not, that is the main problem.
If the table displays, go to menu item Utilities -> Database Object -> Database Utility
In the resulting screen, under the "Status" fields, you should see text "Exists in the database." If you don't, then the table exists in the dictionary, but doesn't exist in the database system. Click the "Create database table" button and then you should be able to run the program.
You may need basis team's help to carryout some of these actions. -
Short Dump while scrolling in a maintenance view
A maintenance view has one field, defined as "Radiobutton".
1) Select the radiobutton for one entry.
2) Scroll down so that in the new page (i.e. the entries displayed in the new page) the entry selected in the first step is not visible.
3) Select any radiobutton again corresponding to any of the entries displayed in the new page.
4) On scrolling up again the short dump occurs.
The short dump text says "More than one radio button is active".
Any inputs in this regards are appreciated.
Thanks.
Gajendra.Hi,
that means you are trying to make two radio buttons active.
parameters: ra radiobutton group g1 default = 'X',
rb radiobutton group g1.
ra = 'X'.
and rb = 'X'.
in your case so obviously it will dump.
check your coding..
and show your code...
Regards
vijay -
SHORT DUMP WHILE EXECUTING DTP.
Hi Gurus,
I have got a short dump while executing DTP the Error is as Follows.
Runtime Error: MESSAGE_TYPE_X.
Reasons for Error: 1.The installation of the SAP GUI on the present server is faulty or obselete
2.There is a error in the application program
And i have sent the sreen shot of the Short Dump to BASIS TEAM and they have replied me that they have to install some patches and it will take some time.
But i have no much time and i have to someway or the other execute the DTP and load the data.
Is there any shortcuts for this i mean to say without the involvement of Basis team that i can do in th BI System
Regards
Amar.Hi Amar,
If the problem is with with System itself, how can we all have a short cut in that case. You may give it another trial, but you have to wait for the patches to be applied. Ask your basis team to get it done ASAP.
Thanks..
Shambhu -
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... -
Short dump while creating a plant.
Dear experts,
Iam getting a short dump whenever I try to create a plant and save it. Iam posting the contents of the dump ... Iam using Ecc 6.0 with Oracle as database. Kindly help me to resolve this ...
Runtime Errors RAISE_EXCEPTION
Date and Time 27.10.2007 17:10:59
Short text
Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" 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 "DATA_INCONS_IN_EXIT_MANAGEM".
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" "DATA_INCONS_IN_EXIT_MANAGEM"
or
"SAPLS_IMG_TOOL_5 " "DATA_INCONS_IN_EXIT_MANAGEM"
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... "BSLERP"
Network address...... "10.60.0.30"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "BSLERP"
Database type..... "ORACLE"
Database name..... "BTS"
Database user ID.. "SAPSR3"
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...... 17768808
Heap.... 0
Page.... 65536
MM Used. 12293456
MM Free. 1291704
User and Transaction
Client.............. 800
User................ "MURTHYTSN"
Language key........ "E"
Transaction......... "SPRO "
Program............. "CL_EXITHANDLER================CP"
Screen.............. "SAPLSZA1 0201"
Screen line......... 70
Information on where terminated
Termination occurred in the ABAP program "CL_EXITHANDLER================CP" -
in "GET_INSTANCE".
The main program was "SAPLS_IMG_TOOL_5 ".
In the source code you have the termination point in line 36
of the (Include) program "CL_EXITHANDLER================CM001".
Source Code Extract
Line
SourceCde
6
type_ref TYPE REF TO cl_abap_typedescr,
7
class_name TYPE seoclsname,
8
abs_type_classname TYPE string,
9
def_impl TYPE seex_boolean VALUE seex_false,
10
mig_enhspotname TYPE enhspotname,
11
is_impl TYPE enhboolean,
12
mig_badi_name TYPE enhbadiid.
13
14
CALL METHOD cl_exithandler=>get_class_name_by_interface
15
EXPORTING
16
instance = instance
17
IMPORTING
18
class_name = class_name
19
CHANGING
20
exit_name = exit_name
21
EXCEPTIONS
22
no_reference = 1
23
no_interface_reference = 2
24
no_exit_interface = 3
25
data_incons_in_exit_managem = 4
26
class_not_implement_interface = 5
27
OTHERS = 6.
28
CASE sy-subrc.
29
WHEN 1.
30
RAISE no_reference.
31
WHEN 2.
32
RAISE no_interface_reference.
33
WHEN 3.
34
RAISE no_exit_interface.
35
WHEN 4.
>>>>>
RAISE data_incons_in_exit_managem.
37
WHEN 5.
38
RAISE class_not_implement_interface.
39
ENDCASE.
40
41
CONCATENATE '\CLASS=' class_name INTO abs_type_classname.
42
43
Is the given instance initial?
44
IF NOT instance IS INITIAL.
45
CALL METHOD cl_abap_typedescr=>describe_by_object_ref
46
EXPORTING
47
p_object_ref = instance
48
RECEIVING
49
p_descr_ref = type_ref.
50
CHECK type_ref->absolute_name NE abs_type_classname.
51
ENDIF.
52
53
SELECT SINGLE mig_enhspotname mig_badi_name FROM sxs_attr INTO (mig_enhspotname,mig_badi_n
54
WHERE exit_name = exit_name.
55
Contents of system fields
Name
Val.
SY-SUBRC
4
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
ADDR0200
SY-UCOMM
CHCK
SY-TITLE
Edit address: 5002
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20071024
SY-UZEIT
171059
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
43 METHOD CL_EXITHANDLER================CP CL_EXITHANDLER================CM001 36
CL_EXITHANDLER=>GET_INSTANCE
42 FUNCTION SAPLXSZAR ZXSZARU01 25
EXIT_SAPLSZAR_001
41 FUNCTION SAPLSZAR LSZARU01 108
ADDR_REGIONAL_DATA_CHECK
40 FORM SAPLSZA2 LSZA2F20 382
CHECK_ADDR1_DATA
39 FUNCTION SAPLSZA2 LSZA2U02 42
ADDR_CHECK
38 FUNCTION SAPLSZA0 LSZA0U01 79
ADDR_INSERT
37 FORM SAPLSZA1 LSZA1F22 1886
INSERT_ADDRESS_INTO_MEMORY
36 FORM SAPLSZA1 LSZA1F22 2234
PUT_ADDRESS_TO_MEMORY
35 FORM SAPLSZA1 LSZA1I02 409
D0100_OK_CODE
34 FORM SAPLSZA1 LSZA1F03 17
D0100_OK_CODE_WRAPPER
33 MODULE (PAI) SAPLSZA1 LSZA1I02 13
D0100_OK_CODE
32 FUNCTION SAPLSZA1 LSZA1U01 200
ADDR_DIALOG_INTERN
31 FUNCTION SAPLSZA1 LSZA1U05 177
ADDR_DIALOG
30 FORM SAPL0ORG LSVIMF24 292
ADDRESS_MAINTAIN
29 FORM SAPL0ORG LSVIMFX2 577
DETAIL_PAI
28 MODULE (PAI) SAPL0ORG LSVIMIXX 354
DETAIL_PAI
27 FORM SAPL0ORG LSVIMF2L 337
CALL_DYNPRO
26 FUNCTION SAPL0ORG L0ORGU34 35
VIEWPROC_V_T001W
25 FUNCTION SAPL0ORG L0ORGU33 49
VIEWFRAME_V_T001W
24 FUNCTION SAPLSVIM LSVIMU01 138
VIEW_MAINTENANCE
23 FUNCTION SAPLSVIM LSVIMU03 427
VIEW_MAINTENANCE_CALL
22 FORM SAPLS_CUS_ACTIVITY LS_CUS_ACTIVITYF01 358
START_SELECTED_TRANSACTION
21 MODULE (PAI) SAPLDSYH LDSYHI12 56
D1200_PAI_MODULE
20 FUNCTION SAPLDSYH LDSYHU11 70
OUTLINE_LIST_TCODES
19 FUNCTION SAPLS_CUS_ACTIVITY LS_CUS_ACTIVITYU07 103
S_CUS_ACTIVITY_EXECUTE
18 FUNCTION SAPLS_CUS_IMG_ACTIVITY LS_CUS_IMG_ACTIVITYU04 35
S_CUS_IMG_ACTIVITY_EXECUTE
17 FUNCTION SAPLS_IMG_TOOL_1 LS_IMG_TOOL_1U02 63
STREE_EXIT_TO_OBJECT_COBJ
16 FUNCTION SAPLSHI1 LSHI1U16 120
STREE_EXIT_TO_OBJECT
15 FORM SAPLSHI01 LSHI01F0Y 185
EXIT_TO_OBJECT_HC
14 FORM SAPLSHI01 LSHI01F05 70
HANDLE_LINK_CLICK
13 METHOD SAPLSHI01 LSHI01CI1 25
LCL_APPLICATION=>HANDLE_LINK_CLICK
12 METHOD CL_ITEM_TREE_CONTROL==========CP CL_ITEM_TREE_CONTROL==========CM013 53
CL_ITEM_TREE_CONTROL=>HANDLE_NODE_KEY_ITEM_NAME_EVT
11 METHOD CL_ITEM_TREE_CONTROL==========CP CL_ITEM_TREE_CONTROL==========CM00S 60
CL_ITEM_TREE_CONTROL=>HANDLE_EVENT
10 METHOD CL_GUI_COLUMN_TREE============CP CL_GUI_COLUMN_TREE============CM01O 15
CL_GUI_COLUMN_TREE=>HANDLE_EVENT
9 METHOD CL_TREE_CONTROL_BASE==========CP CL_TREE_CONTROL_BASE==========CM017 32
CL_TREE_CONTROL_BASE=>DISPATCH
8 METHOD CL_GUI_CFW====================CP CL_GUI_CFW====================CM001 138
CL_GUI_CFW=>DISPATCH
7 FORM SAPLSHI01 LSHI01F1M 17
EXECUTE_USER_COMMAND_W_EXITS
6 FUNCTION SAPLSHI01 LSHI01U12 30
STREE_BROWSER_PAI
5 MODULE (PAI) SAPLSHI01 LSHI01I01 55
PAI_200
4 FUNCTION SAPLSHI01 LSHI01U07 165
STREE_BROWSER_DYNP_HC
3 FUNCTION SAPLSHI21 LSHI21U03 144
STREE_EXTERNAL_DISPLAY
2 FORM SAPLS_IMG_TOOL_5 LS_IMG_TOOL_5F01 20
DISPLAY_REFERENCE_IMG
1 MODULE (PAI) SAPLS_IMG_TOOL_5 LS_IMG_TOOL_5I01 39
USER_COMMAND_0100
Chosen variables
Name
Val.
No. 43 Ty. METHOD
Name CL_EXITHANDLER=>GET_INSTANCE
EXIT_NAME
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
NULL_INSTANCE_ACCEPTED
2
0
0
0
ACT_IMP_EXISTING
2
0
0
0
INSTANCE
F0000000
F0000000
SY-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_SPACE
2
0
0
0
CL_DRAGDROP=>COPY
1
0000
1000
CL_WB_REQUEST=>TO_IMMEDIATE_START
SY-SUBRC
4
0000
4000
CL_DRAGDROP=>USEDEFAULTEFFECT
4
0000
4000
SYST-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CL_GUI_CONTROL=>LIFETIME_DEFAULT
0
0000
0000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ABS_TYPE_CLASSNAME
No. 42 Ty. FUNCTION
Name EXIT_SAPLSZAR_001
IV_NATION
2
0
0
0
X_ACCEPT_ERROR
2
0
0
0
X_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
X_DIALOG_ALLOWED
X
5
8
0
0
Y_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Y_RETCODE
2
0
0
0
ERROR_TABLE[]
Table IT_2299[0x572]
\FUNCTION-POOL=SZA1\FORM=INSERT_ADDRESS_INTO_MEMORY\DATA=ERROR_TABLE[]
Table reference: 208
TABH+ 0(20) = 00000000F8EB2E3D00000000D0000000FB080000
TABH+ 20(20) = 000000003C020000FFFFFFFF04A90100303E0000
TABH+ 40( 8) = 10000000C1248001
store = 0x00000000
ext1 = 0xF8EB2E3D
shmId = 0 (0x00000000)
id = 208 (0xD0000000)
label = 2299 (0xFB080000)
fill = 0 (0x00000000)
leng = 572 (0x3C020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000317
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0xD09AD03C
>>>>> 2nd level extension part <<<<<
tabhBack = 0x30F18E3D
delta_head = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
%_VIASELSCR
0
4
%_SPACE
2
0
0
0
SY-REPID
SAPLXSZAR
5454555452222222222222222222222222222222
310C83A120000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LR_EXIT
F0000000
F0000000
%_DUMMY$$
2222
0000
0000
0000
Y_ERROR_TABLE
Table[initial]
No. 41 Ty. FUNCTION
Name ADDR_REGIONAL_DATA_CHECK
IV_NATION
2
0
0
0
X_ACCEPT_ERROR
2
0
0
0
X_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
X_DIALOG_ALLOWED
X
5
8
0
0
X_T005
800IN IND064 ININD000 00 15500 4111 0000 00 436 664000INDIEN 000 1
3334424443332222222222224444433322233233333223333223333233233322222233333344444423332322222222
8009E09E40640000000000009E9E40000000001550000411100000000004360000006640009E495E00000100000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Y_ADRC_REGIO
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Y_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Y_RETCODE
2
0
0
0
ERROR_TABLE[]
Table IT_2299[0x572]
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LV_MAND
C
422
300
000
000
SY-REPID
SAPLSZAR
5454554522222222222222222222222222222222
310C3A1200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_SPACE
2
0
0
0
%_CX_GRID_ID
1
0000
1000
SYST-REPID
SAPLSZAR
5454554522222222222222222222222222222222
310C3A1200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SV_THERE_IS_CUST_EXIT
X
5
8
0
0
T005S
22222222222222
00000000000000
00000000000000
00000000000000
T005
00 000 00 00 00 00 0000 00 000 000
2222222223322222222222222222233322233233233222332223333233222222222222233322222223332222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
CO_ERROR
E
4
5
0
0
No. 40 Ty. FORM
Name CHECK_ADDR1_DATA
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
FIELDNAME
222222222222222222222222222222
000000000000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
C_NULL
0
0000
0000
RETURNCODE_ERRORS
2
0
0
0
C_ERROR_OCCURRED
E
4
5
0
0
H_ADRC_STRUC+0(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDR1_DATA+460(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
H_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_COMM_TTX
TTX
555
448
000
000
NATION
2
0
0
0
G_ACCEPT_ERROR
2
0
0
0
G_DIALOG_ALLOWED
X
5
8
0
0
T005
800IN IND064 ININD000 00 15500 4111 0000 00 436 664000INDIEN 000 1
3334424443332222222222224444433322233233333223333223333233233322222233333344444423332322222222
8009E09E40640000000000009E9E40000000001550000411100000000004360000006640009E495E00000100000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
TSAD6T
222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
ERROR_TABLE[]
Table IT_2299[0x572]
%_SPACE
2
0
0
0
No. 39 Ty. FUNCTION
Name ADDR_CHECK
ADDRESS_HANDLE
8005002
3333333222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
8005002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDRESS_NUMBER
2222222222
0000000000
0000000000
0000000000
ADDRESS_OBJECT_TYPE
1
3
1
0
0
NATION
2
0
0
0
RETURNCODE
2
0
0
0
ERROR_TABLE[]
Table IT_2299[0x572]
ADDRESS_DATA_1
00000000000000000003XYZ SOLUTIONS LIMITED
3333333333333333333355525445544452444454422222222222222222222222222222222222222222222222222222
0000000000000000000389A03FC549FE30C9D945400000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDRESS_DATA_2
0000000000000000
3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDRESS_DATA_3
0000000000000000
3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LV_ADRC_STRUC+0(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDRESS_DATA_1+460(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_DEFAULT_HANDLE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
SAPLSZA2
5454554322222222222222222222222222222222
310C3A1200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ERROR_TABLE
000
2222222222222222222223332222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LV_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_DEFAULT_NATION
2
0
0
0
C_SHOW_ALL
2
0
0
0
C_PERSONAL_ADDRESS
2
3
2
0
0
SY-REPID
SAPLSZA2
5454554322222222222222222222222222222222
310C3A1200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ADDRESS_DATA_2+32(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 38 Ty. FUNCTION
Name ADDR_INSERTDear Sunil,
Thanks a lot for your reply. I did search in service market place for notes regarding this problem. However, i could not find possible solutions to resolve this. I will once again search the notes in case if i have missed something. in case, if you come across any solutions to resolve this problem, Kindly post that here and that would be a great help for me.
Regards,
Chaitanya
Maybe you are looking for
-
AssertionError while trying to deploy a CMP Entity bean
Following are my deployment-descriptors - =========================================================================== ejb-jar.xml :- =========== <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.c
-
Informix 7.3 - Oracle 8i migration: Generate Exception Blocks not offered
I have installed OMWB 2.0.2 and plugin for Infromix Dynamic Server 7.3. There is no offered checkbox "Generate Exception Blocks" in "Parse Options" panel for customization of parsing stored procedures in Source Model. (But it was normally offered and
-
hi, in alv's using fuction modules how to add pushbuttons in application tool bar?
-
System restore w/o the vault
is there a way to do a system restore to earlier date (like a couple of hours go) to recover my deleted 'trash' in the mail client. and sadly i have not been using the vault.. thank you in advance
-
OpenSSH 4.3p1 Compile Issues (Bad OpenSSL Headers)
I was upgrading the version of OpenSSH on my other systems and thought I would also upgrade it on my Mac. The distributed version was OpenSSH 3.8p1 IIRC. First I find that the version of Zlib is out of date. Not surprising and very excusable. So I fi