Dump in st22
Name of runtime error : CONNE_IMPORT_WRONG_COMP_TYPE
this error comes everyday, as basis user. It is related to database MONI,
can anybody help
Thanks in advance
B
A quick search for oss notes shows that there are several causes for this error. If your system was recently updated (or support packages where applied), oss note 997535 might be worth a try.
If this does not match your problem, post more information here (most of this information is written in the short dump):
- name of the ABAP causing this error
- name of the table affected
- history of you system (recent upgrades, recently applied basis support packages, ...)
Best regards,
Elmar.
Similar Messages
-
Hi , Is there any Function Module or a way to read the Short Dump generated in ST22 for a particular program.?
I have a Z program running in Background on daily basis.For error Handling , when the program generates a short dump , i want to read the short dump. I tried the FM /SDF/GET_DUMP_LOG .with this i am able to read the runtime error , exception , error short text but i am unable to read the entire log description.
like what happened , what can u do etc which can be viewed in st22.Any Inputs Appreciated.
Thanks & Regards,
John.Hi,
Try FM
"STRUCTURE_DUMP" -- Current contents of internal tables will be printed
RS_SNAP_DUMP_DISPLAY
Best regards,
Prashant -
Can't open layout getting Dump in ST22
Hi All,
I am getting an layout no display and dump ST22 with the following details for few users, It seems the data set they try to open via the layout is locked but ususally when the layout is open and they select that version then they get a message ' this is locked or somthing', but I have never seen they can't even open the layout. Specially, with only one layout. Is there a table or somthing I can release that locked for this user? OR how can I resolve this issue!!! I am in SEM 4.0 Add-on into BW3.0B
The termination occurred in the ABAP program "SAPLUPC_DATASLICE" in
"UPC_DATASLICE_CHASEL_CHECK".
The main program was "SAPMHTTP ".
The termination occurred in line 162 of the source code of the (Include)
program "LUPC_DATASLICEU10"
of the source code of program "LUPC_DATASLICEU10" (when calling the editor
1620).Hi,
I think the problem is related to Active/Deactive Dataslices.
In your case Dataslices is ACTIVE ??
Please put a break point in FM UPC_DATASLICE_CHASEL_CHECK and check exactly where are you getting the dump.
Just to analyse the problem , deactivate it and check whether you are getting the dump or not ?
Thanks
pratyush -
My application is running correctly and we never getting any dump in browser but in ST22 there are thousands of dumps recorded for application.
The details are as below. My all services are activated. Kindly suggest what could be the cause
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_WD_GENERAL
Date and Time 07/07/2011 10:39:42
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_WD_GENERAL' was raised, but it was not caught anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CX_WD_GENERAL=================CP' has to be
terminated.
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
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_WD_GENERAL', was not caught and
therefore caused a runtime error.
The reason for the exception is:
WebDynpro Exception: ICF service node
"/sap/bc/webdynpro/sap/App/undefined" does not exist (see SAP Note
1109215).
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:
"UNCAUGHT_EXCEPTION" "CX_WD_GENERAL"
"CX_WD_GENERAL=================CP" or "CX_WD_GENERAL=================CM003"
"RAISE"Hi Shefali,
In ST22 what does in show in the "Source Code Extract" session. Usually it points to code which raosed the exception.
You can try putting a breakpoint there and see what happens at runtime.
Please revert back in case of doubts.
Regards,
Sumit -
Unable to create Material CR , cannot display the page , dump in ST22
Hi Experts,
We are implementing MDG with EHP6 with following components installed with
But I am unable to create Material CR . I am getting the initial page for Create Material but after I hit continue, the next page cannot be displayed .
It is creating an ST22 dump that the config id 'MDG_BS_MAT_PLANT_LIST_ATS' is having an invalid column 'DISPO_TXT' . But I am unable to find the relevant UIBB for this config id . Any thoughts on this issue and how to resolve it. How can I edit the configuration , I don't see that UIBB .
I am unable to find the UIBB for config id 'MDG_BS_MAT_PLANT_LIST_ATS'
I am unable to see the UIBB for MDG_BS_MAT_PLANT_LIST_ATS
I could see the component configuration for MDG_BS_MAT_PLANT_LIST_ATSI found a note 1830324 from SAP regarding this issue , but it is related to SP08 and we are already in SP09.
This note is about the List Component (WD ABAP component FPM_LIST_UIBB_ATS). When the List Component is started it reads the columns from the configuration. All columns in the configuration should be part of the field catalog that is defined by the feeder class (feeder class method get_definition, parameter io_field_catalog). Otherwise the column is invalid (this could happen e. g. when a column that has already been configured is later removed from the field catalog). When such a invalid column is detected the List Component should raise an X-message and in the short text the name of the configuration and the name of the invalid column should be mentioned. The solution then would be to remove that invalid column from the configuration.
Not sure why we are still getting the invalid column issue. -
hi all ,
i am analysisng the dump for some program ,
for analyzing that dump i went to ST22 ,
in that i have seen ,the first line is the given below.
SQL error 60 occurred when accessing table "VBFA ".
i have unserstood the problem is while accesing the table VBFA.
can please suggest what is the SQL error 60.
and how to see that SQL error 60.
please kindly give me the suggestions on it.
thanks in afdvancveHi
The error is DBIF_RSQL_SQL_ERROR, this is because of sequence of the fields in select of the ttable VBFA into itab
the itab sequence should match with select from
check the same and re arragange the same according to the table occurance
Regards
Shiva -
DYNPRO_NOT_FOUND in abap program dumps in st22
Hi All,
We are facing an issue in Abap dumps
Run Time error DYNPRO_NOT_FOUND
Termination occurred in the ABAP program "MP058400" - in "SET_INIT_TAB".
The main program was "MP058400 ".
In the source code you have the termination point in line 49
of the (Include) program "MP058420".
I have an idea that it is releated to Screens but its a standard Tcode PA40 and info type 584.
Please suggest the how can i solve the dump.
Regards
Harsha TejaHi Deepak,
We had installed ECC 6.0 Ehp5 recently and released to HCM consultant they are testing PA30 infotype 584.
Regrads
Harsha Teja -
Hi,
I get a set of 30 dumps daily on my Solman system.
The user is SMD_RFC & the dump is as follows:
Runtime Errors CREATE_DATA_UNKNOWN_TYPE
Exception CX_SY_CREATE_DATA_ERROR
Date and Time 28.01.2011 00:30:52
Short text
CREATE DATA: The specified type "/BI0/V0MSS_C04D2" is no valid data ty
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_SMD_AGGREGATE_MDX==========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CREATE_DATA_ERROR', was not
caught in
procedure "INITIALIZE" "(METHOD)", 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:
The dynamically specified type "/BI0/V0MSS_C04D2" at CREATE DATA is no valid
data type.
The type is either unknown or an object type.
I found Note 1492999..however this is for DB6, whereas I'm on SQL.
Some of the dumps have the specified type with MSS in the short text..while some dumps have the specified type as DB6.
I couldn't find a note for MSS:(
We're on SP25.
pls. help.
Thanks,
Saba.> oh..i coudldn't find it in the script section of DBACOCKPIT...how do i run this?
in the script section? That is a transaction called by SOLMAN_SETUP to set up the BI content/connection
> I know these dumps are basically harmless..but still, cing 30 of them daily sure doen'st bring a smile to your face every morning:(
Harmless in the sense that the data can't be put into those cubes, they are mainly used by SolMan diagnostics.
Markus -
SAP ST22 dump SAPSQL_ARRAY_INSERT_DUPREC
Hi All,
We are getting dump SAPSQL_ARRAY_INSERT_DUPREC in testing system. SAP basis: 701 and Oracle 10.2.0.2
We are getting this dump from yesterday only and the details of the dump are as mentioned below:
============================================================================================
Short text
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSBAL_DB_INTERNAL" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(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:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
Information on where terminated
Termination occurred in the ABAP program "SAPLSBAL_DB_INTERNAL" - in
"BAL_DB_INTERNAL_NO_UPDATE_TASK".
The main program was "SWNCCOLL ".
In the source code you have the termination point in line 64
of the (Include) program "LSBAL_DB_INTERNALU02".
The program "SAPLSBAL_DB_INTERNAL" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BASIS"
Job Number..... 08893100
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", but it was neither
handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "SAPLSBAL_DB_INTERNAL "; its source code begins
line
1 of the (Include program "LSBAL_DB_INTERNALU02 ".
System environment
SAP-Release 701
Application server... "appl543"
Network address...... "122.99.01.88"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "099DER88BN90000"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 27
Shortdump setting.... "full"
Database server... "appl543"
Database type..... "ORACLE"
Database name..... "Q22"
Database user ID.. "SAPSR3"
=====================================================================================================
Also some jobs are cancelled and they are forming the above dump. the detials are:
SAP_COLLECTOR_FOR_NONE_R3_STAT BASIS Canceled 17.12.2010 00:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT BASIS Canceled 17.12.2010 02:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT BASIS Canceled 17.12.2010 03:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT BASIS Canceled 17.12.2010 04:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT BASIS Canceled 17.12.2010 05:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT BASIS Canceled 17.12.2010 06:43:31
**The cancelled job SAP_COLLECTOR_FOR_NONE_R3_STAT generating the above dump at ST22.**
Please suggest us a solution. Thanks in advance!!!
Regards
Veera
Edited by: Veerab on Dec 17, 2010 11:33 AM> 1 of the (Include program "LSBAL_DB_INTERNALU02 ".
Try the following:
open http://service.sap.com/notes
Search for "LSBAL_DB_INTERNALU02"
Markus -
How to delete the short dump list in st22
Hi all,
i want to clear the runtime error list in ST22.
How to clear the list of short dump in ST22.
is there any T.code kindly suggest
thanks in advance
Sundar.cDear Sundar,
By default, short dumps are stored in the system for 14 days. The transaction for managing short dumps is ST22. You can delete short dumps in accordance with a time specification using the Reorganize function, which you can call by choosing
Goto u2192 Reorganize in ST22. You can save a short dump without a time limit using the Keep function, which you can choose under Short Dump u2192 Keep/Release in ST22.
The short dumps are stored in table SNAP. If there are too many entries in table SNAP, problems can occur during the reorganization (see SAP Note 11838). There are different options for deleting short dumps from table SNAP:
1. Call transaction ST22. Choose Goto u2192 Reorganize. You can now specify that all short dumps older than n days old (default 7) are to be deleted. If a very large number of records are deleted at once during the reorganization,
ORACLE error ora1562, failed to extend rollback segment ..., can occur. In this case, see SAP Note 6328.
2. Dropping and recreating table SNAP with the database utility (transaction SE14): you can use this transaction to drop and recreate the table SNAP. This means that all short dumps are deleted.
3. The reorganization program RSSNAPDL deletes old short dumps in pieces (to avoid database problems) from table SNAP. It deletes short dumps that are not flagged for retention and are older than seven days old. Schedule this program at a time of low workload, as large changes in the database are to be expected. The program RSNAPJOB performs a standard scheduling: it starts the program RSSNAPDL every day at 1:00 a.m.
4. TableSNAP is also automatically reorganized. At every short dump that occurs in dialog (the dump is displayed immediately after it is created), a maximum of 20 short dumps that are older than 7 days old are deleted from SNAP. This reorganization should be sufficient in normal production operation.
Hope this information resolves your error and also more useful in the feature.
Thanks
Kishore -
Dear All,
I want to configure the St22 dump in mail , With criteria if Mail is more than 150 in a day it should send a mail.Please Let me know the steps need to be done.
RKHello Rableen,
in RZ20 there are several MTEs, where dumps are catched, for example, ABAP dumps are displayed under:
RZ20 --> SAP CCMS Monitor Templates
--> Entire System
--> <SID> --> Application Server
--> <instance> --> R3Abap
and here you have these MTEs
You can configure threshold values in the properties of MTE "Shortdumps Frequency" and assign an autoreaction method.
But this MTE is only for ABAP dumps. Other type of dumps you can find as described in KBA:
1942651 - RZ20 does not display shortdumps
but there is no such monitor in RZ20, which cathes all dumps from ST22 in one MTE.
Regards,
Alwina -
SAP GRC PC 3.0 - Report Center (Webdynpro) dump
Hi Experts,
We are facing some problems regarding Report Center. We recently changed to Webdynpro reports according to sapnote 1384133 since we don't have BOE, and when clicking any report, the system shows the following error:
Error when processing your request
What has happened?
The URL http://clsaperm.atrame.deloitte.com:8000/sap/bc/webdynpro/sap/GRPC_REPORT/ was not called due to an error.
Note
The following error text was processed in the system PCD : The ASSERT condition was violated.
The error occurred on the application server CLSAPERM_PCD_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: WDDOINIT of program /1BCWDY/BG5C59ETETZCTQICUKMQ==CP
Method: IF_WDR_COMPONENT_DELEGATE~WD_DO_INIT of program /1BCWDY/BG5C59ETETZCTQICUKMQ==CP
Method: DO_INIT of program CL_WDR_DELEGATING_COMPONENT===CP
Method: INIT_CONTROLLER of program CL_WDR_CONTROLLER=============CP
Method: INIT_CONTROLLER of program CL_WDR_COMPONENT==============CP
Method: INIT of program CL_WDR_CONTROLLER=============CP
Method: INIT of program CL_WDR_CLIENT_COMPONENT=======CP
Method: INIT of program CL_WDR_CLIENT_APPLICATION=====CP
Method: IF_WDR_RUNTIME~CREATE of program CL_WDR_MAIN_TASK==============CP
Method: HANDLE_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
The dump from ST22 is the following:
Errores tiempo ejec. ASSERTION_FAILED
Fecha y hora 13.10.2011 15:49:20
|Texto breve |
| The ASSERT condition was violated. |
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"ASSERTION_FAILED" " "
"/1BCWDY/BG5C59ETETZCTQICUKMQ==CP" or "/1BCWDY/B_BG5C59ETFKLOL21YX00Z"
"WDDOINIT"
Usuario y transacción
Client.............. 100
User................ "SAPGRCPC"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "0ECCF5E07EACF196AD48E61F13572E0F"
Program............. "/1BCWDY/BG5C59ETETZCTQICUKMQ==CP"
Screen.............. "SAPMHTTP 0010"
Screen Line......... 2
Information on Caller ofr "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. "10.139.19.110"
Caller Port........... 8000
Universal Resource Id. "/sap/bc/webdynpro/sap/grpc_report"
Info posición de cancelación
Termination occurred in the ABAP program "/1BCWDY/BG5C59
in "WDDOINIT".
The main program was "SAPMHTTP ".
In the source code you have the termination point in lin
of the (Include) program "/1BCWDY/B_BG5C59ETFKLOL21YX00Z
La cancelación ocurrió en una aplicación Web Dynpro
Componente Web Dynpro GRPC_REPORT
Controlad.Web Dynpro COMPONENTCONTROLLER
Detalle código fuente
Lín. Txt.fte.
1018 * <COMPONENTCONTROLLER> (COMPONENT)
1019 * Notes: NOT intended for use outside of framework dr
1020 * UDate: 20111012 172704
1021 *====================================================
1022 class CL_COMPONENTCONTROLLER_Ctr implementation.
1023
1024 *==================
1025 method Constructor.
1026 *==================
1027 " Do NOT modify the Constructor, any changes will not
1028
1029 Me->Wd_This = Wd_This.
1030 Me->Wd_Context = Wd_Context.
1031 endmethod.
1032
1033 * +--------------------------------------------------
1034 * | general methods
1035 * +--------------------------------------------------
1036
1037 method WDDOAPPLICATIONSTATECHANGE . "#EC NEEDED
1038 endmethod.
1039
1040 method WDDOBEFORENAVIGATION . "#EC NEEDED
1041 endmethod.
1042
1043 method WDDOEXIT . "#EC NEEDED
1044 endmethod.
1045
1046 METHOD wddoinit.
1047
>>>>> assert 1 = 2.
1049 * Old reporting infrastructure replaced by new one in GRFN namespace.
1050
1051 CALL FUNCTION 'GRPC_API_SESSION_OPEN'
1052 * EXPORTING
1053 * I_LANGUAGE = SY-LANGU
1054 * I_TIMEFRAME = I_TIMEFRAME
1055 * I_TF_YEAR = I_TF_YEAR
1056 IMPORTING
1057 e_session_id = wd_this->m_session_id
1058 * E_RETURN_CODE = e_return_code
1059 * TABLES
1060 * ET_MESSAGE = ET_MESSAGE
1061 .
1062
1063 CREATE OBJECT wd_this->mr_timeframe
1064 EXPORTING
1065 i_context = wd_context.
1066 wd_this->mr_timeframe->set_session( wd_this->m_session_id ).
1067
We are on SP7 for GRCFND_A and other components in ABAP side, and SP7 for all software components in Java side.
Regards,
Edited by: Pedro Zuñiga on Oct 13, 2011 9:31 PMHi Pedro,
Were you able to resolve this issue? We are experiencing the same problem.
Thanks,
Mahwish -
Dump run time error "dbif_rsql_sql_error"
Hi guru's,
I have a genric data source with function module which feeds data to a genric ods in bw.
But at time of data upload i see quality status in manage of ods green saying (0 of 0 records extracted) but it asks me to check dump in st22 which is as follows
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Occurred on 21.11.2006 at 23:57:48
An SQL error occurred when accessing a table.
What happened?
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. 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
"ZL3_BW_SALES_ORDER_ITEM" "(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:
How to correct the error
The exception must either be prevented, caught within the procedure
"ZL3_BW_SALES_ORDER_ITEM"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-01555: snapshot too old: rollback segment
number 222 with name "_SYSSMU222$" too small"
Internal call code.........: "[RSQL/FTCH/VBAP ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"SAPLZL3_BW_VARIANT" or "LZL3_BW_VARIANTU03"
"ZL3_BW_SALES_ORDER_ITEM"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "wieap053"
Network address.......... "10.50.197.53"
Operating system......... "HP-UX"
Release.................. "B.11.23"
Hardware type............ "ia64"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "wieap007"
Database type............ "ORACLE"
Database name............ "P00"
Database owner........... "SAPR3"
Character set............ "en_US.iso88591"
SAP kernel............... "640"
Created on............... "May 21 2006 20:37:10"
Created in............... "HP-UX B.11.23 U ia64"
Database version......... "OCI_920 "
Patch level.............. "129"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "HP-UX B.11"
User, transaction...
Client.............. 001
User................ "RFC_P92"
Language key........ "E"
Transaction......... " "
Program............. "SAPLZL3_BW_VARIANT"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where termination occurred
The termination occurred in the ABAP program "SAPLZL3_BW_VARIANT" in
"ZL3_BW_SALES_ORDER_ITEM".
The main program was "SBIE0001 ".
The termination occurred in line 240 of the source code of the (Include)
program "LZL3_BW_VARIANTU03"
of the source code of program "LZL3_BW_VARIANTU03" (when calling the editor
2400).
The program "SAPLZL3_BW_VARIANT" was started as a background job.
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "ZL3_BW_SALES_ORDER_ITEM" "(FUNCTION)" but was not handled locally,
not declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLZL3_BW_VARIANT ". Its source code starts
in line 5
of the (Include) program "LZL3_BW_VARIANT$03 ".
Source code extract
002100 a~werks
002110 c~edatu
002120 a~aedat
002130 a~erdat
002140 FROM ( vbap AS a
002150 INNER JOIN vbak AS b
002160 ON a~vbeln = b~vbeln
002170 AND b~vbtyp = 'W' "C0006-R2
002180 INNER JOIN vbep AS c
002190 ON a~vbeln = c~vbeln
002200 AND a~posnr = c~posnr
002210 AND c~etenr = '1' )
002220 WHERE a~vbeln IN
002230 ( SELECT objectid
002240 FROM cdhdr
002250 WHERE objectclas = 'VERKBELEG'
002260 * AND tcode = 'VA02'
002270 AND udate IN l_r_aedat )
002280 OR a~erdat IN l_r_aedat.
002290
002300 ENDIF. "Full or Delta ?
002310 ENDIF. "First data package ?
002320
002330 * Fetch records into e_t_data
002340
002350 FETCH NEXT CURSOR s_cursor
002360 INTO CORRESPONDING FIELDS
002370 OF TABLE l_t_data
002380 PACKAGE SIZE s_s_if-maxsize.
002390
> IF sy-subrc <> 0.
00241 0
002420 CLOSE CURSOR s_cursor.
002430
002440 ** Do not insert the upload date in the timestamp table when testing on
002450 ** the R/3 system
002460 * IF SY-TCODE <> 'RSA3'
002470 * AND SY-TCODE <> 'RSO2'
002480 * AND SY-TCODE <> 'SE37'
002490 * AND I_READ_ONLY IS INITIAL.
002500 *
002510 * ls_zl3_bw_timest-upload_date = sy-datum.
002520 * ls_zl3_bw_timest-oltpsource = s_s_if-dsource.
002530 *
002540 * INSERT INTO zl3_bw_timest VALUES ls_zl3_bw_timest.
002550 *
002560 * ENDIF.
002570
002580 RAISE no_more_data.
002590 ENDIF.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 1
SY-TABIX 1 SY-DBCNT 1
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM
SY-TITLE Data extraction using SUBMIT_JOB as batch process
SY-MSGTY E SY-MSGID BM
SY-MSGNO 026 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
9 FUNCTION ZL3_BW_SALES_ORDER_ITEM
SAPLZL3_BW_VARIANT
LZL3_BW_VARIANTU03 240
8 FUNCTION RSA3_GET_DATA_SIMPLE
SAPLRSA3
LRSA3U06 74
7 FORM EXTRACTOR_FETCH
%_T002T1
??? 0
6 FORM EXTRACT_EAPI_INTO_QUEUE
%_T002T1
??? 0
5 FUNCTION RSC1_DELTA_BIW_GET
SAPLRSC1
LRSC1U03 390
4 FORM DATA_TRANSFER
GP3Z7WZZ1QZLIWHNBB8PBL5TTS7
GP3Z7WZZ1QZLIWHNBB8PBL5TTS7 128
3 FUNCTION RSAP_DATA_TRANSFER
SAPLRSAP
LRSAPU06 137
2 FUNCTION RSAP_PERFORM_EXTRACTION
SAPLRSAP
LRSAPU19 135
1 EVENT START-OF-SELECTION
SBIE0001
SBIE0001 60
Chosen variables
9 FUNCTION ZL3_BW_SALES_ORDER_ITEM
SAPLZL3_BW_VARIANT
LZL3_BW_VARIANTU03 240
I_DSOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
I_INITFLAG
2
0
I_MAXSIZE 050000
333333
050000
I_READ_ONLY
2
0
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
E_T_DATA[] Table IT_1937[0x103]
I_T_FIELDS[] Table IT_1917[13x30]
I_T_SELECT[] Table IT_1916[1x123]
<%_TABLE_CDHDR> ???
%_DUMMY$$
2222
0000
SY-REPID SAPLZL3_BW_VARIANT
5454543545554544452222222222222222222222
310CAC3F27F61291E40000000000000000000000
SYST-REPID SAPLZL3_BW_VARIANT
5454543545554544452222222222222222222222
310CAC3F27F61291E40000000000000000000000
<%_TABLE_ZL3_VARIANT_CONF> ???
L_R_AEDAT[] Table IT_1938[1x19]
%_SPACE
2
0
S_S_IF-MAXSIZE 050000
333333
050000
S_CURSOR 20
0001
0004
L_T_DATA[] Table IT_1939[0x111]
SY-SUBRC 0
0000
0000
SY-UZEIT 220930
333333
220930
L_T_DATA 00000000000000 ##
2222222222333333333333332222222222222200
0000000000000000000000000000000000000000
... + 40 ######
0000002222222222222222222222222222222222
00000C0000000000000000000000000000000000
... + 80 000000000000000000000000
2222222333333333333333333333333
0000000000000000000000000000000
%_PRINT 001SBIE0001_RFC
2222333544433335544222222222222222222222
000000132950001F263000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 X8 ###A###PX_PAPER DRF
2222222225320004000555545452222222222454
000000000880000100008F010520000000000426
... + 120 C_P92 LIST1S
4553322222222222222222222222222222445535
3F09200000000000000000000000000000C93413
... + 160 TEXT 1 5D 2 ###Y
545522222222323422222222222222320015
4584000000001054000000000000002000E9
L_T_DATA-AEDAT 00000000
33333333
00000000
8 FUNCTION RSA3_GET_DATA_SIMPLE
SAPLRSA3
LRSA3U06 74
I_CHABASNM
222222222222222222222222222222
000000000000000000000000000000
I_DATAPAKID 000000
333333
000000
I_INITFLAG
2
0
I_ISOURCE
222222222222222222222222222222
000000000000000000000000000000
I_MAXSIZE 000000
333333
000000
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
I_RLOGSYS
2222222222
0000000000
I_UPDMODE
22
00
E_T_DATA[] Table IT_1937[0x103]
I_T_FIELDS[] Table[initial]
I_T_SELECT[] Table[initial]
SY ########################################
0000000000000000000000000000000000000000
000100000001000100000000000A000000000000
... + 40 ###############A#######P################
0000000000000004000000050000000000000001
0001000000010001000100000000000000000003
... + 80 ###################g####################
0000000000000000000600000000000000000000
0000000000000000000700000000000000000000
... + 120 #######################################T
0000000000000000000000000000000000010005
0000000000000000000000000000000000060004
... + 160 ################ u############# E0X X1
0000000000000001270000000000000222435253
00000000000000E0050020000C0000C000508081
... + 200 000 ####__S 001
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000010
... + 240 80
222223322222222
000008000000000
S_S_IF_SIMPLE-T_FIELDS Table IT_1917[13x30]
S_S_IF_SIMPLE-T_SELECT Table IT_1916[1x123]
G_T_FIELDS Table[initial]
%_DUMMY$$
2222
0000
G_S_RODCHABAS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
22222222222222
00000000000000
SY-REPID SAPLRSA3
5454554322222222222222222222222222222222
310C231300000000000000000000000000000000
RSAL_S_LOGPARMS-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
G_T_LANGU Table[initial]
E_T_DATA 00000000000000 ##
2222222222333333333333332222222222222200
0000000000000000000000000000000000000000
... + 40 ######
0000002222222222222222222222222222222222
00000C0000000000000000000000000000000000
... + 80 0000000000000000
22222223333333333333333
00000000000000000000000
S_S_IF_SIMPLE-INITFLAG
2
0
S_FNAME ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
S_S_IF_SIMPLE-DSOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
SY-XFORM CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
SY-XPROG SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
S_S_IF_SIMPLE-MAXSIZE 050000
333333
050000
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
S_S_IF_SIMPLE-REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
%_PRINT 001SBIE0001_RFC
2222333544433335544222222222222222222222
000000132950001F263000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 X8 ###A###PX_PAPER DRF
2222222225320004000555545452222222222454
000000000880000100008F010520000000000426
... + 120 C_P92 LIST1S
4553322222222222222222222222222222445535
3F09200000000000000000000000000000C93413
... + 160 TEXT 1 5D 2 ###Y
545522222222323422222222222222320015
4584000000001054000000000000002000E9
G_S_INTERFACE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 000000 000000
2222222222333333222333333
0000000000000000000000000
SYST-REPID SAPLRSA3
5454554322222222222222222222222222222222
310C231300000000000000000000000000000000
7 FORM EXTRACTOR_FETCH
%_T002T1
??? 0
SYST-REPID %_T002T1
2553335322222222222222222222222222222222
5F40024100000000000000000000000000000000
E_T_DATA Table IT_1937[0x103]
SY-SUBRC 0
0000
0000
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
SY-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGNO 026
333
026
%_DUMMY$$
2222
0000
SY-REPID %_T002T1
2553335322222222222222222222222222222222
5F40024100000000000000000000000000000000
6 FORM EXTRACT_EAPI_INTO_QUEUE
%_T002T1
??? 0
G_TABIX 1
0000
0001
SY ########################################
0000000000000000000000000000000000000000
000100000001000100000000000A000000000000
... + 40 ###############A#######P################
0000000000000004000000050000000000000001
0001000000010001000100000000000000000003
... + 80 ###################g####################
0000000000000000000600000000000000000000
0000000000000000000700000000000000000000
... + 120 #######################################T
0000000000000000000000000000000000010005
0000000000000000000000000000000000060004
... + 160 ################ u############# E0X X1
0000000000000001270000000000000222435253
00000000000000E0050020000C0000C000508081
... + 200 000 ####__S 001
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000010
... + 240 80
222223322222222
000008000000000
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
L_T_DATA Table IT_1937[0x103]
C_SUBRC 0
0000
0000
I_OSOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
5 FUNCTION RSC1_DELTA_BIW_GET
SAPLRSC1
LRSC1U03 390
I_CHABASNM
222222222222222222222222222222
000000000000000000000000000000
I_DATAPAKID 000000
333333
000000
I_INITFLAG
2
0
I_ISOURCE
222222222222222222222222222222
000000000000000000000000000000
I_MAXSIZE 000000
333333
000000
I_PRIVATE_MODE
2222
0000
I_READ_ONLY
2
0
I_REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
I_RLOGSYS
2222222222
0000000000
I_UPDMODE
22
00
E_T_DATA[] Table IT_1926[0x103]
I_T_FIELDS[] Table[initial]
I_T_SELECT[] Table[initial]
SBIWA_C_FLAG_OFF
2
0
L_PROGNAME
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
L_FUNCTION /BIC/QIZL3_BW_SALES_ORD__10001
244425454354555444554545533333
F293F19AC3F27F31C53FF24FF10001
L_T_QRFCRCV Table IT_1936[1x56]
L_SUBRC 0
0000
0000
S_READ_ONLY
2
0
L_DELTA_TYPE E
4222
5000
RSAOT_C_DELTA-OWN E
4222
5000
SYST-REPID SAPLRSC1
5454554322222222222222222222222222222222
310C233100000000000000000000000000000000
RSAOT_C_DELTA-ALE A
4222
1000
L_NO_MORE_DATA
2
0
L_UPDMODE D
42
40
SBIWA_C_UPDMODE_DELTA D
42
40
RSAL_SAVE_SUBRC 0
0000
0000
L_POOLNAME %_T002T1
2553335322222222222222222222222222222222
5F40024100000000000000000000000000000000
S_S_ROIS-ISOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
G_FLAG_INTERFACE_INITIALIZED X
5
8
<%_TABLE_ROOSPRMSC> ???
%_SPACE
2
0
SYST ########################################
0000000000000000000000000000000000000000
000100000001000100000000000A000000000000
... + 40 ###############A#######P################
0000000000000004000000050000000000000001
0001000000010001000100000000000000000003
... + 80 ###################g####################
0000000000000000000600000000000000000000
0000000000000000000700000000000000000000
... + 120 #######################################T
0000000000000000000000000000000000010005
0000000000000000000000000000000000060004
... + 160 ################ u############# E0X X1
0000000000000001270000000000000222435253
00000000000000E0050020000C0000C000508081
... + 200 000 ####__S 001
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000010
... + 240 80
222223322222222
000008000000000
SBIW_C_TRUE X
5
8
SY-REPID SAPLRSC1
5454554322222222222222222222222222222222
310C233100000000000000000000000000000000
QS_NOSENDS NOSENDS
44544452
EF35E430
4 FORM DATA_TRANSFER
GP3Z7WZZ1QZLIWHNBB8PBL5TTS7
GP3Z7WZZ1QZLIWHNBB8PBL5TTS7 128
SY-SUBRC 0
0000
0000
SY-REPID GP3Z7WZZ1QZLIWHNBB8PBL5TTS7
4535355535544544443544355532222222222222
703A77AA11AC978E22802C544370000000000000
SPACE
2
0
SYST-REPID GP3Z7WZZ1QZLIWHNBB8PBL5TTS7
4535355535544544443544355532222222222222
703A77AA11AC978E22802C544370000000000000
%_DUMMY$$
2222
0000
P_S_REQUEST-UPDMODE D
42
40
SBIWA_C_UPDMODE_DELTA D
42
40
SBIWA_C_UPDMODE_REPEAT R
52
20
SRSC_C_UPDMODE_INITSIMU S
52
30
SBIWA_C_UPDMODE_DELTAINIT C
42
30
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
L_FNAME RSC1_DELTA_BIW_GET
554354445454455445222222222222
2331F45C41F297F754000000000000
P_S_REQUEST-REQUNR REQU_43VWUSBH207E5H8W64KGNKSPN
545553355554433343435334444554
2515F436753282075588764B7EB30E
RODKYF
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
22222222
00000000
L_T_ZL3_SALES Table IT_1926[0x103]
ROISGEN ZL3_BW_SALES_ORDER_ITEM PHD00
5435455544455454455454422222225443322222
AC3F27F31C53FF2452F945D00000000840000000
... + 40 PBW82 T /B
5453322222522222222222222222222222222224
02782000004000000000000000000000000000F2
... + 80 IC/CCPB0000000766 3Z7WZZ1QZLIW
4424454333333333322222222222353555355445
93F33020000000766000000000003A77AA11AC97
... + 120 HNBB8PBL5TTS7
4444354435553222222222222222222222222222
8E22802C54437000000000000000000000000000
... + 160 RFC_P92
2222222222222222222222222222222225445533
000000000000000000000000000000000263F092
... + 200 20060322161543 000000000
2222233333333333333222222222222333333333
0000020060322161543000000000000000000000
... + 240 00000
33333
00000
ROIST
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222
0000000000000000000000000000000
%_PRINT 001SBIE0001_RFC
2222333544433335544222222222222222222222
000000132950001F263000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 X8 ###A###PX_PAPER DRF
2222222225320004000555545452222222222454
000000000880000100008F010520000000000426
... + 120 C_P92 LIST1S
4553322222222222222222222222222222445535
3F09200000000000000000000000000000C93413
... + 160 TEXT 1 5D 2 ###Y
545522222222323422222222222222320015
4584000000001054000000000000002000E9
3 FUNCTION RSAP_DATA_TRANSFER
SAPLRSAP
LRSAPU06 137
I_ISOURCE ZL3_BW_SALES_ORDER_ITEM
543545554445545445545442222222
AC3F27F31C53FF2452F945D0000000
I_S_REQUEST REQU_43VWUSBH207E5H8W64KGNKSPNDZL3_BW_SA
5455533555544333434353344445544543545554
2515F436753282075588764B7EB30E4AC3F27F31
... + 40 LES_ORDER_ITEM 20061121210928RFC_B
4455454455454422222223333333333333354454
C53FF2452F945D000000020061121210928263F2
... + 80 W PHD00 PBW82 000000D T X
5222222544332222254533222223333334252252
7000000084000000002782000000000004040080
... + 120 X
5
8
I_T_SELECT Table IT_57[0x123]
RODIOBJCMP 0000
2222222222222222222222222222223333222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
22222222222222
00000000000000
L_S_LOGPARMS-MSGV3
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
RODCHA
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222Tell your basis guys
"ORA-01555: snapshot too old: rollback segment"
ie the job took too long for the current settings you have for rollbacks
They will adjust the settings -
Memory Dump :FBL5N No roll storage space of length 1753104 available for internal storage.
Dear Friends,
I am getting below error during T-Code FBL3N Report. No roll storage space of length 1753104 available for internal storage.
Our Server' RAM size is 24 GB,and existing parameters are as below
ztta/roll_area: 6500000
ztta/roll_extension:2000683008
abap/heap_area_total:2000683008
abap/heap_area_dia: 5000000000
abap/heap_area_nondia: 2000683008
em/initial_size_MB: 4092
Please suggest Parameter to be change.
Details Dump log ST22
Runtime Errors TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Date and Time 04.03.2014 10:18:48
|Short Text |
| No roll storage space of length 1753104 available for internal storage. |
|What happened? |
| Each transaction requires some main memory space to process |
| application data. If the operating system cannot provide any more |
| space, the transaction is terminated. |
|What can you do? |
| |
| Try to find out (e.g. by targetted data selection) whether the |
| transaction will run with less main memory. |
| |
| If there is a temporary bottleneck, execute the transaction again. |
| - |
| |
| If the error persists, ask your system administrator to check the |
| following profile parameters: |
| |
| o ztta/roll_area (1.000.000 - 15.000.000) |
| Classic roll area per user and internal mode |
| usual amount of roll area per user and internal mode |
| o ztta/roll_extension (10.000.000 - 500.000.000) |
| Amount of memory per user in extended memory (EM) |
| o abap/heap_area_total (100.000.000 - 1.500.000.000) |
| Amount of memory (malloc) for all users of an application |
| server. If several background processes are running on |
| one server, temporary bottlenecks may occur. |
| Of course, the amount of memory (in bytes) must also be |
| available on the machine (main memory or file system swap). |
| Caution: |
| The operating system must be set up so that there is also |
| enough memory for each process. Usually, the maximum address |
| space is too small. |
| Ask your hardware manufacturer or your competence center |
| about this. |
| In this case, consult your hardware vendor |
| abap/heap_area_dia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each dialog process. |
| Parameters for background processes: |
| abap/heap_area_nondia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each background process. |
| Other memory-relevant parameters are: |
| em/initial_size_MB: (35-1200) |
| Extended memory area from which all users of an |
| application server can satisfy their memory requirement. |
| Note which actions and input led to the error. |
| |
| For further help in handling the problem, contact your SAP administrator |
| . |
| |
| You can use the ABAP dump analysis transaction ST22 to view and manage |
| termination messages, in particular for long term reference. |
| |
|Error analysis |
| The internal table "\CLASS=ZCL_IM__GTA_TAX_CODE\METHOD=IF_EX_FI_ITEMS_CH_DATA~C |
| HANGE_ITEMS\DATA=GT_BSIK" could not be enlarged further. |
| |
| Memory location: "Session memory" |
| |
| You attempted to extend the data structure for the management of the |
| memory blocks for table "\CLASS=ZCL_IM__GTA_TAX_CODE\METHOD=IF_EX_FI_ITEMS_CH_D |
| ATA~CHANGE_ITEMS\DATA=GT_BSIK". However, the 1753104 bytes required for |
| this were no longer available in the specified memory area. |
| |
| The amount of memory requested is no longer available. |
|How to correct the error |
| |
| Try to decide by analysis whether this request is |
| reasonable or whether there is a program error. You should pay |
| particular attention to the internal table entries listed below. |
| |
| |
| |
| |
| |
| |
| 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: |
| |
| "TSV_TNEW_BLOCKS_NO_ROLL_MEMORY" " " |
| "ZCL_IM__GTA_TAX_CODE==========CP" or "ZCL_IM__GTA_TAX_CODE==========CM001" |
| "IF_EX_FI_ITEMS_CH_DATA~CHANGE_ITEMS" |
| |
| 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... "NEWPRD1" |
| Network address...... "10.0.0.1" |
| Operating system..... "Windows NT" |
| Release.............. "6.0" |
| Hardware type........ "16x AMD64 Level" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 19 |
| Shortdump setting.... "full" |
| |
| Database server... "NEWPRD1" |
| Database type..... "ORACLE" |
| Database name..... "PRD" |
| Database user ID.. "SAPSR3" |
| |
| Terminal................. " " |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 700 |
| created (date)... "Sep 17 2012 22:56:00" |
| create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00" |
| Database version. "OCI_10201_SHARE (10.2.0.4.0) " |
| |
| Patch level. 353 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 700 |
| Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows |
| NT 6.0, Windows NT 6.1, Windows NT 6.2" |
| |
| Memory consumption |
| Roll.... 16192 |
| EM...... 1826770240 |
| Heap.... 0 |
| Page.... 40960 |
| MM Used. 1815573536 |
| MM Free. 2717408 |
|User and Transaction |
| |
| Client.............. 500 |
| User................ 1651 |
| Language key........ "E" |
| Transaction......... " " |
| Transactions ID..... "ED4EA3E3AB0AF11DA318E61F131BC713" |
| |
| Program............. "ZCL_IM__GTA_TAX_CODE==========CP" |
| Screen.............. "SAPMSSY0 1000" |
| Screen line......... 6 |
|Information on where terminated |
| Termination occurred in the ABAP program "ZCL_IM__GTA_TAX_CODE==========CP" - |
| in "IF_EX_FI_ITEMS_CH_DATA~CHANGE_ITEMS". |
| The main program was "RFITEMGL ". |
| |
| In the source code you have the termination point in line 64 |
| of the (Include) program "ZCL_IM__GTA_TAX_CODE==========CM001". |
| The program "ZCL_IM__GTA_TAX_CODE==========CP" was started as a background job. |
| Job Name....... "RFITEMGL" |
| Job Initiator.. "BASIS" |
| Job Number..... 09115400 |
|Source Code Extract |
|Line |SourceCde |
| 34| MANDT TYPE BSEG-MANDT, |
| 35| BUKRS TYPE BSEG-BUKRS, |
| 36| BELNR TYPE BSEG-BELNR, |
| 37| GJAHR TYPE BSEG-GJAHR, |
| 38| BUZEI TYPE BSEG-BUZEI, |
| 39| QSSKZ TYPE BSEG-QSSKZ, |
| 40| KTOSL TYPE BSEG-KTOSL, |
| 41| HKONT TYPE BSEG-HKONT, |
| 42| END OF TY_BSEG, |
| 43| |
| 44| BEGIN OF TY_FINAL, |
| 45| BUKRS TYPE BSEG-BUKRS, |
| 46| BELNR TYPE BSEG-BELNR, |
| 47| GJAHR TYPE BSEG-GJAHR, |
| 48| END OF TY_FINAL. |
| 49| |
| 50| DATA: CW_ITEMS TYPE RFPOSXEXT, |
| 51| GT_BSIK TYPE STANDARD TABLE OF TY_BSIK, |
| 52| GW_BSIK TYPE TY_BSIK, |
| 53| GT_BSAK TYPE STANDARD TABLE OF TY_BSAK, |
| 54| GW_BSAK TYPE TY_BSAK, |
| 55| GT_BSEG TYPE STANDARD TABLE OF TY_BSEG, |
| 56| GW_BSEG TYPE TY_BSEG, &nbsap basis wrote:
|Information on where terminated |
| Termination occurred in the ABAP program "ZCL_IM__GTA_TAX_CODE==========CP" - |
| in "IF_EX_FI_ITEMS_CH_DATA~CHANGE_ITEMS". |
| The main program was "RFITEMGL ". |
| |
| In the source code you have the termination point in line 64 |
| of the (Include) program "ZCL_IM__GTA_TAX_CODE==========CM001". |
| The program "ZCL_IM__GTA_TAX_CODE==========CP" was started as a background job. |
| Job Name....... "RFITEMGL" |
| Job Initiator.. "BASIS" |
| Job Number..... 09115400 |
First of all try to optimize code. -
Short dump in reading selection values in Report
Hi all,
I have created a Navegational Attributte and added this Info Object in the existing Query and for this object we have created Charactistics Value Variable with Uesr Entry.
But, When we use input selection option to select a vlaue for this Variable in the Variable Selection Screen it is trying to read the values and going into short Dump but for other variables Selection option is working fine.
Please anyone help me if you have the solution.
Regards,
Ali.Hi,
Try deleting the master data and reload the master data again and check for the selection variables. Check the short dump in ST22 it will say which master table ie SID table or master table where the join fails.
Thanks,
Arun
Maybe you are looking for
-
Page-break in alv background job for alv output variant not coming correctl
Hi, I have created an ALV grid report. When i run the report in background i get the output with correct page-break on FIELD1. Now when i run the report in background with an "ALV output variant" (its the ALV variant that controls the fields display
-
There have been many reports that UK users of Ebay cannot see certain pages on Ebay after recent Updates by Ebay. I have a problem. When I open 'My Ebay' on my iMac (Snow Leopard with Safari V 5.1.10) the Summery Page will just not load properly, i
-
Iphoto book - problem with deleting extra pages
I am finishing up a book with iphoto of 85 pages of photos. I want to delete 6 empty pages, but when I go to All Pages View, hold control key and click, the only option is to add pages. I don't want to purchase book and assume apple won't charge/pr
-
How do you replicate KSB1 drilldown functionality in BW?
We would our finance infocubes to allow users to drill down to partner object (usually a PM work order) & description, Purchase Order & Description, Material Number & description as they can do in KSB1. Our developers are saying that: <i>* KSB1 is a
-
How Can I make the following query faster
Hi Guru I want your valuable suggestion to make the following query faster.I did not write all required columns list. I gave here all those columns where I have conditon like decode,case when,or subquery (SELECT CASE WHEN REPORTED_BY IS NULL THEN