Dump While Displaying PO
Hi All,
I have service PO containing 3000 records. But now when i try to display in me23n it is giving dump, the dump is below;
How this problem can be solved. Current Version is 4.7 (SAPKH47029). I also tried to search for SAP note but unable to get.
Appreciate your answers & points will be rewarded.
Runtime errors COMPUTE_BCD_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
Occurred on 17.06.2008 at 09:38:25
>> Short dump has not been completely stored. It is too big.
Overflow for arithmetical operation (type P) in program "SAPLEINR"
What happened?
Error in ABAP application program.
The current ABAP program "SAPLEINR" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
A value does not fit in a calculation field.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that 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_ARITHMETIC_OVERFLOW',
was neither
caught nor passed along using a RAISING clause, in the procedure "BET_ANALYSE"
"(FORM)"
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:
An overflow has been determined in the current arithmetical operation
containing operands of type P. Possible causes include:
1. The results field of type P is to small and the result does not fit
into it.
places.
2. The result or partial result has more than 31 decimal places.
How to correct the error
The exception must either be prevented, caught within the procedure
"BET_ANALYSE"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
You may need to define the result field to be larger, if it is still
possible to do so.
It may be possible to split the current process so that only smaller
values occur.
Eine Vorablösung zu dem aufgetretenen Fehler findet sich vielleicht
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
If you require an interim solution to this error, you can look in the
SAP note system. If you have access to
the SAP notes system yourself, enter the following search strings:
"COMPUTE_BCD_OVERFLOW"
"BCD_FIELD_OVERFLOW" (By release 4.0a, this error has been remedied at this
point)
"SAPLEINR" or "LEINRF0P"
"BET_ANALYSE"
Regards
Irfan
Hi
Please logonto
https://websmp206.sap-ag.de/support,
Give the Customer S- User ID & password for logging
Log the message in the Customer meesages tab page.
Thanks & Regards
Kishore
Similar Messages
-
Short dump while displaying cube data in production
Hi Folks,
I'm getting a short dump while displaying cube data in production, please suggest
Thanks and Regards
SanthoshHi Santosh,
I'd suggest to follow as per SAP Note: 568768 - Analysis of SQL Errors causing Shortdumps or Error messages. The Note contains precise steps to analyze such an ABAP dump.
cheers
m./ -
Short dump while displaying a particular tab
hi all,
In a user exit, in IW32 transaction i am displaying a particular tab after a popup warning box. I am able to display the tab i wanted to using field-symbols and changing the T185 at runtime (i changed the build group and panel fields at runtime). but after displaying the screen, if i click on header tab it is giving me a short dump. the error is raised relative to CAUFVD_UPD-INDBT and the error is "ERROR WHEN READING ORDER HEADER WITH INDEX". can anyone explain me what could be the problem? and a possible solution to avoid it.
thanks in advance,
Anil.Hi Santosh,
I'd suggest to follow as per SAP Note: 568768 - Analysis of SQL Errors causing Shortdumps or Error messages. The Note contains precise steps to analyze such an ABAP dump.
cheers
m./ -
Dump while displaying shopping cart in portal ?
Hi,
We are in SRM 7.0 and we are using portal.
We are in intial upgrade stage from SRM 5 to SRm 7.0.
When we select the shopping cart and click on DISPLAY or EDITin portal nothing is happened.
From HTTP watch , we found that ..it is going to the URL and it is stucked.
When we try to access the URL directly , we are getting below error.
Error when processing your request
What has happened?
The URL http:// ........./sap/bc/webdynpro/sap/powl was not called due to an error.
Note
The following error text was processed in the system RST : An exception occurred that was not caught.
The error occurred on the application server fsp55a02_RST_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: INITIALIZE of program CL_POWL_MODEL=================CP
Method: HANDLEDEFAULT of program /1BCWDY/J9ZTOJ20D6QLEKKWJHSF==CP
Method: HANDLEDEFAULT of program /1BCWDY/J9ZTOJ20D6QLEKKWJHSF==CP
Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/J9ZTOJ20D6QLEKKWJHSF==CP
Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_IF_VIEW=====CP
Method: DISPLAY_TOPLEVEL_COMPONENT 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
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
Could any one please let me know the issue.
Regards
Venkatesh PHi ,
Below is the dump.
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_POWL_FATAL_EXCEPTION
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_POWL_FATAL_EXCEPTION' 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
'CL_POWL_MODEL=================CP' has to be
terminated.
Line SourceCde
61 result = cl_powl_util=>ms_display_alvdialog_as_popup
62 .
63
64 * read configuration setting for POWL FOCUS
65 CALL METHOD me->read_config_property
66 EXPORTING
67 i_property = 'POWL_DEFAULT_FOCUS'
68 * i_type =
69 IMPORTING
70 result = mv_powl_focus.
71
72 * switch POWL delta rendering on (if requested in corresponding URL parameter)
73 mr_table_helper->set_powl_delta_rend_state( i_powl_delta_rend ).
74
75 m_refresh_srv_group = i_srv_group.
76
77 l_applid = i_applid.
78
79 IF m_applid IS INITIAL AND
80 l_applid IS INITIAL.
81
82 * try to get application ID from configuration
83 me->read_config_property(
84 EXPORTING i_property = 'POWL_APPLICATION_ID'
85 IMPORTING result = l_applid
86 ).
87
88 IF l_applid IS INITIAL.
89
90 * we expect a valid application ID!
>>>> RAISE EXCEPTION TYPE cx_powl_fatal_exception
92 EXPORTING
93 textid = 'APPLID_ILLEGAL'.
94 ENDIF.
95
96 ENDIF.
97 " clear latest switched query
98 CLEAR ms_new_query.
99
100 * check if we have to do a full (re-)initialization
101 IF l_applid IS NOT INITIAL AND
102 m_applid <> l_applid.
103
104 m_applid = l_applid.
105 l_do_full_init = 'X'.
106 ELSE.
107 l_do_full_init = space.
108 ENDIF.
109
110 * check if we can exit here since the WD session data is still valid
Regards
Venkatesh P -
Short dump while displaying infocube data
Hi Folks,
I have created one infocube in BW 7.3 with 2 characteristics and one keyfigure for uploading flat file data.
I have successfully uploaded the data into infocube.When i go for displaying data by right click on the infocube it is throwing some short dump.
Pls find the short dump below.
Category ABAP Programming Error
Runtime Errors RAISE_EXCEPTION
ABAP Program SAPLRRSI
Application Component BW-BEX-OT
Error analysis |
A RAISE statement in the program "SAPLRRSI" raised the exception
condition "X_MESSAGE".
Since the exception was not intercepted by a superior
program, processing was terminated.
|
We are using BW 7.3. Pls help me ..Thanks in advance.
Regards
sriHi,
check following threads as well
1. ST03N Raise Exception Shortdump when Access BI Workload
2 See if you can activate the Infocube RSDG_CUBE_ACTIVATE
3. CHECK if you have sufficient memory to work in case this is dev or test system
4. check in RSRV in case there is any issue with design
5. InfoCube Data not Visible in BI
Go to Manage>Infocube content>Execute(you may not be able to see anything here)>in the menu (where DETAILS, SORTING)etc are available click on the 10th option> CHANGE LAYOUT--> You may not have anything selected at the left pane in this pop up window.
Select all or your desired objects from COLUMN SET to DISPLAYED COLUMNS. Click on the tick mark & ow see.I think it'll help u...
As suggested you may have some authorization issue.
Thanks and regards
Kiran -
To handle dump while displaying the data
hi,
I have a requirement in which i have created a assignment block which fetches some data after confirming an account. But sometimes if the number of rows of data fetched are more than 1000 then it gives dump.
Can anyone suggest how to handle this dump as we can not restrict the data for 1000 records due to our requirement.
Or if it can be done by using Try and Catch than How ?
Cheers,
SharadHi,
Are you sure that the exception comes just because the result is more than 1000? Any way, you can put your code within a try..catch block.
try.
<your code>...
catch cx_root.
<handle exception if you want>
endtry.
{code{
note that cx_root will catch all exceptions, but you will lose the advantage of exception specific handling. Also, the exception must be "catcheable".
Regards,
Arun Prakash -
Short dump in J1iex while display
Hi
I have come across a short dump while displaying an invoice number (Using tcode J1iex) which was already posted. Dump says there is a conversion error .
Screen name.............. "SAPLJ1IEX"
Screen number............ 0200
Screen field............. "J_1IEXITEM-AVAILABLE_AT1"
Error text............... "FX015: Sign lost."
Can anyone please clarify what can be done in this case.
Regards
Prabhakar.Hi
Thanks for the reply.
J_1IEXITEM-AVAILABLE_AT1 ( Available CENVAT credit field) is getting a value 0.01- . There is a field conversion problem from ABAP program to Screen display (Dump message) .
This variable has
Technical type description : P(7) DECIMALS 2
Absolute type description: J_1IEXAVLAT1
As such we have applied some notes which is not related to this application.
Please clarify.
Regards
Prabhakar. -
Getting short dumps while reading bulky data from excel sheet
Hi all,
We have converted our non-unicode based sap system (R/3 4.7, Windows 2003,
SQL 2000) into a unicode based system recently. We are facing two peculiar
problems for last few days.
*Problem 1 - *Whenever we want to upload the data from excel sheet, the
system throws a dump after reading about 400 entries, while last week the
same system used to read about 8000 entries in a single go.
*Problem 2 - *Also, whenever we realease a transport requst from development
containing a lot of changes, the request will reach the quality system but
without the changes. but if i ll try to import the changes into quality
system after generating more than one request containing small small
changes, they get reflected in QAS immediately. Is there any size
constraint in transporting a request fro DEV->QAS->PRD.
Please suggest some ways.
I am pasting the dump (that I am getting while data uploading from Excel).
~~~~~~~~~~~~~~~~~~
Runtime errors
MESSAGE_TYPE_X*
Occurred on
22.02.2008 at
13:21:02*
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that 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
Short text of error message:
Control Framework : Error processing control
Technical information about the message:
Diagnosis
An error occurred when the system tried to process the commands
from the Automation Queue on the presentation server.
There are several possible reasons for this:
- The installation of the SAP GUI on the presentation server is
faulty or obsolete.
- There is an error in the application program
- There is an error in the SAPGUI or an integrated control
Procedure
1. Make sure that you have imported the appropriate Support
Package, the current kernel, and GUI patch for the release of your
System
2. Check whether the error occurs locally on one or a few PCs, or
generally on all PCs. Note whether the error only occurs for some
users, for example because of a specific Customizing setting.
If it only occurs locally, this suggests an installation problem
with the PC. Check the installation; if necessary, reinstall the
software. In the dump, search for the SY-MSGLI field, since it may
point to the cause of the error.
3. Activate the Automation Trace (in accordance with SAP Note
158985).
4.Start the transaction and continue until the screen immediately
before the dump.
5. From the System -> Utilities menu, choose Autom. Queue,
Synchronous Processing.
The status bar of the GUI displays the text:
"Automation synchron flush mode on"
6. If you now proceed with the application, the short dump will
display the ABAP call that caused the error; the Automation Trace
will contain the error on the presentation server.
7. If necessary, load the short dump and trace files on to
sapservX, so that SAP can analyze them.
Message classe...... "CNDP"
Number.............. 006
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"MESSAGE_TYPE_X" C
"SAPLOLEA" or "LOLEAU02"
"AC_SYSTEM_FLUSH"
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....... "nhbho930"
Network address.......... "192.168.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
Short dump setting....... "full"
Database server.......... "NHBHO930"
Database type............ "MSSQL"
Database name............ "DEV"
Database owner........... "dev"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 17 2007 00:18:58"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "196"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 300
User................ "NHBABAP"
Language key........ "E"
Transaction......... "SE38 "
Program............. "SAPLOLEA"
Screen.............. "SAPMSDYP 0010"
Screen line......... 0
Information on where terminated
The termination occurred in the ABAP program "SAPLOLEA" in
"AC_SYSTEM_FLUSH".
The main program was "ZBDC_CONTRACT ".
The termination occurred in line 29 of the source code of the (Include)
program "LOLEAU02"
of the source code of program "LOLEAU02" (when calling the editor 290).
~~~~~~~~~~~~~~~~~~~~~
Thank you all.
Cheers.
Mitra __.____._for the 50 millionth time: Excel spreadsheets are NOT databases, you should NOT try to use them as such and NEVER access them using JDBC.
You should also under NO condition use the JDBC-ODBC bridge driver (that was actually the 78 millionth time that was told someone). -
Short Dump while executing ALV Grid.
Hi All,
I m getting a short dump while trying to execute an ALV.
The dump exception is of type
CX_SY_DYN_CALL_ILLEGAL_TYPE class.
The message displayed is : " Call to form 'GI_FIELDCAT' is incorrect .The actual parameter in PERFORM is different data type than requested for form GI_FIELDCAT " .
The part of programe included is as follows:
FORM build_fieldcat .
PERFORM gi_fieldcat USING 'MBLNR' text-014 '1' '20'.
PERFORM gi_fieldcat USING 'ZEILE' text-005 '2' '4'.
PERFORM gi_fieldcat USING 'MATNR' text-006 '3' '18'.
PERFORM gi_fieldcat USING 'MAKTX' text-028 '4' '40'.
PERFORM gi_fieldcat USING 'MATKL' text-029 '5' '40'.
PERFORM gi_fieldcat USING 'BUDAT' text-027 '6' '10'.
PERFORM gi_fieldcat USING 'MENGE' text-026 '7' '9'.
PERFORM gi_fieldcat USING 'DMBTR' text-025 '8' '13'.
PERFORM gi_fieldcat USING 'WAERS' text-011 '9' '5'.
PERFORM gi_fieldcat USING 'RSNUM' text-012 '10' '10'.
PERFORM gi_fieldcat USING 'PSPHI' text-013 '11' '10'.
ENDFORM. " build_fieldcat
FORM gi_fieldcat USING fieldname TYPE slis_fieldcat_alv-fieldname
colmname TYPE slis_fieldcat_alv-seltext_m
colmpos TYPE slis_fieldcat_alv-col_pos
outputlen TYPE slis_fieldcat_alv-outputlen.
wa_fieldcat-fieldname = fieldname.
wa_fieldcat-seltext_m = colmname.
wa_fieldcat-col_pos = colmpos.
wa_fieldcat-outputlen = outputlen.
wa_fieldcat-
APPEND wa_fieldcat TO it_fieldcat.
CLEAR wa_fieldcat.
ENDFORM. " gi_fieldcat
Can ayone gimmi a solution for the same.Hi,
Try to change ur code like the below.
Attached: sample code
Building field catalog
PERFORM modify_catlog USING:
'GT_OUTPUT' 'AUART' text-t02 '1',
'GT_OUTPUT' 'KUNNR' text-t03 '2',
'GT_OUTPUT' 'NAME' text-t04 '3',
'GT_OUTPUT' 'KWMENG' text-t05 '4',
'GT_OUTPUT' 'VRKME' text-t06 '5',
'GT_OUTPUT' 'LFIMG' text-t07 '6',
'GT_OUTPUT' 'GEWEI' text-t08 '7',
'GT_OUTPUT' 'VOLUM' text-t09 '8',
'GT_OUTPUT' 'VOLEH' text-t10 '9',
'GT_OUTPUT' 'BRGEW' text-t11 '10',
'GT_OUTPUT' 'UOMGW' text-t12 '11',
'GT_OUTPUT' 'VARCE' text-t13 '12',
'GT_OUTPUT' 'UOMVR' text-t14 '13'.
FORM modify_catlog USING pa_tabname TYPE string
pa_field TYPE string
pa_text TYPE string
pa_pos TYPE string.
CLEAR gs_fieldcatalog.
*Modifying field catalog
gs_fieldcatalog-col_pos = pa_pos.
gs_fieldcatalog-fieldname = pa_field.
gs_fieldcatalog-tabname = pa_tabname.
gs_fieldcatalog-seltext_m = pa_text.
APPEND gs_fieldcatalog TO gt_fieldcatalog.
CLEAR gs_fieldcatalog.
l_repid = sy-repid.
To call function to display ALV output
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = l_repid
it_fieldcat = gt_fieldcatalog
TABLES
t_outtab = gt_output
EXCEPTIONS
program_error = 1
OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE e000 WITH text-t16.
ENDIF.
Reward if helpful.
Regards,
Ramya -
Short Dump while executing New Hire (action type) in PA40
Hi All,
i am getting short dump while executing PA40 for new hire action type can anyone look into this and guide as i am new to HCM.
Category ABAP Programming Error
Runtime Errors SYNTAX_ERROR
ABAP Program /1PAPAXX/HDR_21000A
Application Component Not Assigned
Date and Time 21.08.2014 14:07:03
Short text
Syntax error in program "/1PAPAXX/HDR_21000A ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPFP50M" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in
include "/1PAPAXX/HDR_21000AO01 " in
line 52:
""LV_LENGTH" has already been declared"
The include has been created and last changed by:
Created by: "HCM04 "
Last changed by: "HCM03 "
Error in the ABAP Application Program
The current ABAP program "SAPFP50M" 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 "/1PAPAXX/HDR_21000A ".
You can also perform the syntax check from the ABAP Editor.
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 look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following syntax error was found in the program /1PAPAXX/HDR_21000A :
""LV_LENGTH" has already been declared"
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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..... 731
SAP Basis Level. 0007
Application server... "dc-ds-erp"
Network address...... "172.16.23.111"
Operating system..... "Linux"
Release.............. "3.0.13-0.27-default"
Hardware type........ "x86_64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "dc-ds-erp"
Database type..... "ORACLE"
Database name..... "ECD"
Database user ID.. "SAPSR3"
Terminal.......... "NLC-HP"
Char.set.... "C"
SAP kernel....... 720
created (date)... "Sep 14 2013 06:16:24"
create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"
Database version. "OCI_112, 11.2.0.3.0, V1, default"
Patch level. 500
Patch text.. " "
Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
SAP database version. 720
Operating system..... "Linux 2.6, Linux 3"
Memory consumption
Roll.... 0
EM...... 37708200
Heap.... 0
Page.... 106496
MM Used. 4666776
MM Free. 3709976
User and Transaction
Client.............. 210
User................ "HCM03"
Language key........ "E"
Transaction......... "PA40 "
Transaction ID...... "53EF470299AB5D67E1000000AC10176F"
EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"
EPP Connection ID....... 00000000000000000000000000000000
EPP Caller Counter...... 0
Program............. "SAPFP50M"
Screen.............. "MP000000 1000"
Screen Line......... 3
Debugger Active..... "none"
Information on where terminated
Termination occurred in the ABAP program "SAPFP50M" - in
"GET_HEADER_WITH_TCLAS".
The main program was "MP000000 ".
In the source code you have the termination point in line 146
of the (Include) program "FP50MDHD".
Source Code Extract
Line
SourceCde
116
CALL FUNCTION 'HR_HEADER_GET'
117
EXPORTING
118
DHDID = FHD_HID
119
BEGDA = BEGDA
120
TCLAS = TCLAS
121
* Es wird nur einer der folgenden 3 Parameter benutzt.
122
* Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.
123
* Der erste der nicht initial ist wird ausgewertet.
124
* MOLGA =
125
P0001 = P0001
126
PERNR = PSPAR-PERNR
127
IMPORTING
128
PROG = HEADER_PROG
129
DNUM = HEADER_DYNNR
130
EXCEPTIONS
131
HEADER_DEACTIVATED = 1
132
HEADER_UNKNOWN = 2
133
HEADER_GENERATE_DEACTIVATED = 3
134
HEADER_GENERATE_FAILED = 4
135
INTERNAL_ERROR = 5
136
OTHERS = 6.
137
138
IF NOT SY-SUBRC IS INITIAL.
139
* Bei Problemen gibt's eben ein leeres Dynpro.
140
HEADER_PROG = 'SAPMP50A'.
141
HEADER_DYNNR = '0090'.
142
ELSE. " NOT sy-subrc IS INITIAL. "
143
* Dann setzen wir jetzt auch noch das Datum fest.
144
PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.
145
* Und schalten auf Uebergabe der PERNR mit globalen Variablen.
>>>>>
PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).
147
ENDIF. " (ELSE) NOT sy-subrc IS INITIAL. "
148
* Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.Hi,
Error Log: Syntax error
""LV_LENGTH" has already been declared"
please check LV_LENGTH variable declaration.
It may be declared more once! -
ABAP Dumps while loading data form one DSO to another DSO
Hi All,
We are getting following ABAP dump while loading data from one DSO to another DSO.
Please find below ABAP Dump we are getting.
Please let us know how we can resolve this issue.
Category ABAP Programming Error
Runtime Errors MESSAGE_TYPE_X
ABAP Program CL_RSBK_CMD_DP_LOOP===========CP
Application Component BW-WHM-DST
Date and Time 30.05.2014 07:10:03
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
Invalid program status
Long text of error message:
Technical information about the message:
Message class....... "RSBK"
Number.............. 299
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"CL_RSBK_CMD_DP_LOOP===========CP" or "CL_RSBK_CMD_DP_LOOP===========CM00Q"
"GET_LOG"
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..... 731
SAP Basis Level. 0004
Application server... "cab-bi-prod1"
Network address...... "10.10.72.43"
Operating system..... "Windows NT"
Release.............. "6.1"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 12
Shortdump setting.... "full"
Database server... "nguksvamds039"
Database type..... "ORACLE"
Database name..... "PWB"
Database user ID.. "SAPSR3"
Terminal.......... " "
Char.set.... "C"
SAP kernel....... 720
created (date)... "Dec 20 2011 02:14:54"
create on........ "NT 6.0 6002 S x86 MS VC++ 16.00"
Database version. "OCI_11201_SHARE, 11.2.0.3.0 "
Patch level. 117
Patch text.. " "
Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
SAP database version. 720
Operating system..... "Windows NT 5.1, Windows NT 5.2, Windows NT 6.0, Windows
NT 6.1"
Memory consumption
Roll.... 0
EM...... 12569376
Heap.... 0
Page.... 24576
MM Used. 3422928
MM Free. 764192
User and Transaction
Client.............. 100
User................ "THARDEEP"
Language key........ "E"
Transaction......... " "
Transaction ID...... "03C1E7E3F560F14CA2AD00505698028E"
EPP Whole Context ID.... "53873353A7E31150E10080000A0A2142"
EPP Connection ID....... 00000000000000000000000000000000
EPP Caller Counter...... 0
Program............. "CL_RSBK_CMD_DP_LOOP===========CP"
Screen.............. "SAPMSSY0 1000"
Screen Line......... 6
Debugger Active..... "none"
Information on where terminated
Termination occurred in the ABAP program "CL_RSBK_CMD_DP_LOOP===========CP" -
in "GET_LOG".
The main program was "RSBATCH_EXECUTE_PROZESS ".
In the source code you have the termination point in line 7
of the (Include) program "CL_RSBK_CMD_DP_LOOP===========CM00Q".
The program "CL_RSBK_CMD_DP_LOOP===========CP" was started as a background job.
Job Name....... "BIDTPR_10616_1"
Job Initiator.. "THARDEEP"
Job Number..... 07100200
Source Code Extract
Line SourceCde
1 METHOD get_log.
2 DATA: l_r_request TYPE REF TO cl_rsbk_request.
3 IF p_r_log IS INITIAL.
4 TRY.
5 l_r_request = cl_rsbk_request=>create_from_db( if_rsbk_cmd~n_requid ).
6 CATCH cx_rs_not_found.
>>>>> MESSAGE x299(rsbk).
8 ENDTRY.
9 IF l_r_request->get_uses_new_log( ) = rs_c_false.
10 p_r_log = cl_rsbm_log_cursor_process=>create_for_process( i_r_process ).
11 ELSE.
12
13 TRY.
14 DATA l_runid TYPE rsbrun.
15 l_runid = l_r_request->get_runid( ).
16 IF l_runid = 0.
17 l_runid = 1.
18 ENDIF.
19 p_r_log = cl_rsbm_log_cursor_process_dtp=>create_new(
20 i_requid = if_rsbk_cmd~n_requid
21 i_runid = l_runid ).
22 IF n_datapakid IS NOT INITIAL.
23 p_r_log->goto_datapackage( n_datapakid ).
24 ENDIF.
25 CATCH cx_rs_not_found .
26 MESSAGE x299.
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 1
SY-TABIX 0
SY-DBCNT 1
SY-FDPOS 25
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Execute Batch Process
SY-MSGTY X
SY-MSGID RSBK
SY-MSGNO 299
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20140530
SY-UZEIT 071002
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
7 METHOD CL_RSBK_CMD_DP_LOOP===========CP CL_RSBK_CMD_DP_LOOP===========CM00Q 7
CL_RSBK_CMD_DP_LOOP=>GET_LOG
6 METHOD CL_RSBK_CMD_DP_LOOP===========CP CL_RSBK_CMD_DP_LOOP===========CM00J 38
CL_RSBK_CMD_DP_LOOP=>SET_DP_IN_PROCESS
5 METHOD CL_RSBK_CMD_DP_LOOP===========CP CL_RSBK_CMD_DP_LOOP===========CM00B 9
CL_RSBK_CMD_DP_LOOP=>IF_RSBK_CMD~SET_PROCESS_PARAMETERS
4 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM00E 15
CL_RSBK_PROCESS=>SET_MEMENTO
3 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM003 30
CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~GET_OBJECT_REF
2 FUNCTION SAPLRSBATCH LRSBATCHU13 428
RSBATCH_EXECUTE_PROCESS
1 EVENT RSBATCH_EXECUTE_PROZESS RSBATCH_EXECUTE_PROZESS 374
START-OF-SELECTION
Chosen variables
Name
Val.
No. 7 Ty. METHOD
Name CL_RSBK_CMD_DP_LOOP=>GET_LOG
I_R_PROCESS
{O:1*\CLASS=CL_RSBK_PROCESS}
F0000000
E0001000
FE00000001000000
SCREEN
%_17NNS0005639652_%_%_%_%_%_%_
2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
5F17EE30005639652F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
25005F00310037004E004E00530030003000300035003600330039003600350032005F0025005F0025005F0025005F
SPACE
2
0
0
0
2000
SY-REPID
CL_RSBK_CMD_DP_LOOP===========CP
4455544544454554445333333333334522222222
3CF232BF3D4F40FCFF0DDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
43004C005F005200530042004B005F0043004D0044005F00440050005F004C004F004F0050003D003D003D003D003D
ME->IF_RSBK_CMD~N_REQUID
0
0000
0000
00000000
L_R_REQUEST
{O:initial}
F0000000
F0000000
FF00000000000000
%_DUMMY$$
2222
0000
0000
0000
2000200020002000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
53004100500043004E0056004500200020002000200020002000200020002000200020002000200020002000200020
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SY-MSGID
RSBK
55442222222222222222
232B0000000000000000
00000000000000000000
00000000000000000000
5200530042004B002000200020002000200020002000200020002000200020002000200020002000
SY-MSGNO
299
333
299
000
000
320039003900
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
%_##TVREG_001
2
0
0
0
2000
RS_C_FALSE
2
0
0
0
2000
No. 6 Ty. METHOD
Name CL_RSBK_CMD_DP_LOOP=>SET_DP_IN_PROCESS
I_R_PROCESS
{O:1*\CLASS=CL_RSBK_PROCESS}
F0000000
E0001000
FE00000001000000
I_DATAPAKID
000236
333333
000236
000000
000000
300030003000320033003600
L_TH_RANGE_X
Table[initial]
L_S_RANGE_X
2222222222222222222222222222220022222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
L_TH_RANGE
Table[initial]
L_S_RANGE
2222222222222222222222222222220022222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
RSBC_C_DPSTATE-ACTIVE
5
3
5
0
0
3500
L_R_ROOT
{O:1091*\CLASS=CX_RS_FAILED}
B0004000
C0003400
BC00000043040000
ME
{O:72*\CLASS=CL_RSBK_CMD_DP_LOOP}
B0004000
70008000
B700000048000000
ME->P_R_LOG
{O:initial}
F0000000
F0000000
FF00000000000000
No. 5 Ty. METHOD
Name CL_RSBK_CMD_DP_LOOP=>IF_RSBK_CMD~SET_PROCESS_PARAMETERS
I_MEMENTO
ÿ#######4103##############D#####################D#A#T#A#P#A#K#I#D#¼####0#0#0#2#3#6#½#
F00000803333000000000000004000000000000000000000404050405040404040B0000303030303030B0
F621120041030000160000C0004900000000000000000000401040100010B09040C000C000000203060D4
FF0602010102800034313033000000000106000000000C000000440900000000000000000000000000000000000000
I_R_PROCESS
{O:1*\CLASS=CL_RSBK_PROCESS}
F0000000
E0001000
FE00000001000000
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
43004F004E00560045005200530049004F004E005F0045005800490054002000200020002000200020002000200020
SY-SUBRC
0
0000
0000
00000000
ME->N_DATAPAKID
000236
333333
000236
000000
000000
300030003000320033003600
ME
{O:72*\CLASS=CL_RSBK_CMD_DP_LOOP}
B0004000
70008000
B700000048000000
No. 4 Ty. METHOD
Name CL_RSBK_PROCESS=>SET_MEMENTO
I_TH_CMD_MEMENTO
Table IT_42[5x52]
\CLASS=CL_RSBK_PROCESS\METHOD=IF_RSBATCH_EXECUTE~GET_OBJECT_REF\DATA=L_S_PROCESS-TH_CMD_MEMENT
Table reference: 21
TABH+ 0(20) = 10C64700DF070000000000000000000000000000
TABH+ 20(20) = 150000002A000000050000003400000020000000
TABH+ 40(16) = 045A0000A006000005000000A425C000
store = 0x10C64700DF070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 21 (0x15000000)
label = 42 (0x2A000000)
fill = 5 (0x05000000)
leng = 52 (0x34000000)
loop = 32 (0x20000000)
xtyp = TYPE#000010
occu = 5 (0x05000000)
accKind = 4 (ItAccessHashed)
idxKind = 0 (ItIndexNone)
uniKind = 1 (ItUniYes)
keyKind = 3 (user defined)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
stMode = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
isUsed = 1
isCtfyAble = 1
hasScndKeys = 0
hasRowId = 0
scndKeysOutdated = 0
scndUniKeysOutdated = 0
----- Shareable Table Header Data -----
tabi = 0x607B4100DF070000
pgHook = 0x0000000000000000
idxPtr = 0xC08D5000DF070000
id = 36 (0x24000000)
shmTabhSet = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 5 (0x05000000)
lineAlloc = 5 (0x05000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
rowId = 18446744073709551615
scndKeyAdmin = 0x0000000000000000
##LOOP_DP ###쀀
00444554522222222222221000
30CFF0F4000000000000004020
0000000000000000000000000C
00000000000000000000000000
030000004C004F004F0050005F00440050002000200020002000200020002000200020002000200020002000140000
##X_DATASTORE ###쀀
00554454554542222222221000
408F414134F250000000004030
0000000000000000000000000C
00000000000000000000000000
0400000058005F004400410054004100530054004F0052004500200020002000200020002000200020002000140000
##ERROR_FILTER ###쀀
FF455455444545222222221000
FF522F2F69C452000000004040
FF00000000000000000000000C
FF000000000000000000000000
FFFFFFFF4500520052004F0052005F00460049004C0054004500520020002000200020002000200020002000140000
##TRFN ###쀀
FF554422222222222222221000
EF426E00000000000000004040
FF00000000000000000000000C
FF000000000000000000000000
FEFFFFFF5400520046004E002000200020002000200020002000200020002000200020002000200020002000140000
##U_ODSO ###쀀
00554454222222222222221000
605FF43F000000000000004040
0000000000000000000000000C
00000000000000000000000000
0600000055005F004F00440053004F0020002000200020002000200020002000200020002000200020002000140000
%_DUMMY$$
2222
0000
0000
0000
2000200020002000
SYST
##########################A###P#######|#########<#############################T#########XC####
0000000000000000000000100040005000000070000000003000000000000000000000000000105000100000540000
10000010000010000000109010101000000000C000000000C000000000000000000000000000604000E00000830500
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
0100000000000000000000000100000000000000000000000100000000000000000000000000000001000000190000
SYST-REPID
CL_RSBK_PROCESS===============CP
4455544555444553333333333333334522222222
3CF232BF02F3533DDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
43004C005F005200530042004B005F00500052004F0043004500530053003D003D003D003D003D003D003D003D003D
L_R_ERROR
{O:initial}
F0000000
F0000000
FF00000000000000
L_S_CMD_MEMENTO
##LOOP_DP ###쀀
00444554522222222222221000
30CFF0F4000000000000004020
0000000000000000000000000C
00000000000000000000000000
030000004C004F004F0050005F00440050002000200020002000200020002000200020002000200020002000140000
ME->P_TH_CMD_R
Table IT_724[8x48]
{O:1*\CLASS=CL_RSBK_PROCESS}\DATA=P_TH_CMD_R
Table reference: 353
TABH+ 0(20) = 00306E00DF070000000000000000000000000000
TABH+ 20(20) = 61010000D40200000800000030000000FFFFFFFF
TABH+ 40(16) = 04E100005042030009000000BC25C800
store = 0x00306E00DF070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 353 (0x61010000)
label = 724 (0xD4020000)
fill = 8 (0x08000000)
leng = 48 (0x30000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000037
occu = 9 (0x09000000)
accKind = 4 (ItAccessHashed)
idxKind = 3 (ItIndexList)
uniKind = 1 (ItUniYes)
keyKind = 3 (user defined)
cmpMode = 2 (cmpSingleMcmpR)
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 = 0x302E6E00DF070000
pgHook = 0x0000000000000000
idxPtr = 0x80306E00DF070000
id = 647 (0x87020000)
shmTabhSet = 0x0000000000000000
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 9 (0x09000000)
lineAlloc = 9 (0x09000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
rowId = 18446744073709551615
scndKeyAdmin = 0x0000000000000000
########P Í#2# #
000000005222222222C03020
103000000000000000D02000
000000000000000000000000
000000000000000000000000
010000000300000000000000000000005000200020002000200020002000200020002000CD00000032000000200000
########P ·#H# #
000000005222222222B04020
300040100000000000708000
000000000000000000000000
000000000000000000000000
030000000000000004000000010000005000200020002000200020002000200020002000B700000048000000200000
########X ¶#I# #
00FF00005222222222B04020
40FF70108000000000609000
00FF00000000000000000000
00FF00000000000000000000
04000000FFFFFFFF07000000010000005800200020002000200020002000200020002000B600000049000000200000
########T °#O# #
FF00FF005222222222B04020
FF00EF40400000000000F000
FF00FF000000000000000000
FF00FF000000000000000000
FFFFFFFF00000000FEFFFFFF040000005400200020002000200020002000200020002000B00000004F000000200000
########T ®#Q# #
FF0000005222222222A05020
EF0060404000000000E01000
FF0000000000000000000000
FF0000000000000000000000
FEFFFFFF0000000006000000040000005400200020002000200020002000200020002000AE00000051000000200000
L_S_CMD_R
########P ·#H# #
000000005222222222B04020
300040100000000000708000
000000000000000000000000
000000000000000000000000
030000000000000004000000010000005000200020002000200020002000200020002000B700000048000000200000
SY-REPID
CL_RSBK_PROCESS===============CP
4455544555444553333333333333334522222222
3CF232BF02F3533DDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
43004C005F005200530042004B005F00500052004F0043004500530053003D003D003D003D003D003D003D003D003D
CX_RS_STEP_FAILED=>FAILED_IN_PARALLEL_MODE
L_S_CMD_MEMENTO-NODE
3
0000
3000
03000000
SY-SUBRC
0
0000
0000
00000000
L_S_CMD_MEMENTO-MEMENTO
ÿ#######4103##############D#####################D#A#T#A#P#A#K#I#D#¼####0#0#0#2#3#6#½#
F00000803333000000000000004000000000000000000000404050405040404040B0000303030303030B0
F621120041030000160000C0004900000000000000000000401040100010B09040C000C000000203060D4
FF0602010102800034313033000000000106000000000C000000440900000000000000000000000000000000000000
ME
{O:1*\CLASS=CL_RSBK_PROCESS}
F0000000
E0001000
FE00000001000000
No. 3 Ty. METHOD
Name CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~GET_OBJECT_REF
I_PROCESS_TYPE
DTP_LOAD
4555444422
440FCF1400
0000000000
0000000000
4400540050005F004C004F004100440020002000
I_BATCH_ID
DTPR_10616_1
455553333353222222222222222222
4402F10616F1000000000000000000
000000000000000000000000000000
000000000000000000000000000000
44005400500052005F00310030003600310036005F0031002000200020002000200020002000200020002000200020
I_BATCH_PROCESS
238
2222223332
0000002380
0000000000
0000000000
2000200020002000200020003200330038002000
I_PARAMETER
ۿĂȁ#ㄴ㌰##༅##(Ѐޱ##########PROCESSྫ##ꨨ##Ѐڪ##ꨌ##Ѐ###ꨄ##Ѐª##ꨂ##Ȁྭ##ꨴ##Ѐª##ꨨ###ྮ##갴##⠀¼#砠) ㈀㌀㘀##ÿ#
F008330000020B00000000005544455A002000A000000A000000A000000A003000A002100A003000B0220000000FF0
F2104000500801000000000002F3533B008800A00C800A004800A002000D004800A008400E004F00C0090000000FF0
0000330000000000000000000000000000A000000A000000A000000A000000A000000A000000A0020070333333FF00
61201300F0004700000000000000000F00A004600A004800A004000A002F00A004000A008F00C0080080000236FF00
FF060201010280003431303300000000050F0000000028000004B10700000000000000000000000000000000000000
R_R_RSBATCH_EXECUTE
{O:initial}
F0000000
F0000000
FF00000000000000
L_S_PROCESS-PROCESSTYPE
2
0
0
0
2000
L_S_PROCESS-NO_COMMIT
2
0
0
0
2000
L_R_PROCESS
{O:1*\CLASS=CL_RSBK_PROCESS}
F0000000
E0001000
FE00000001000000
L_S_PROCESS-DATAPAKID
000236
333333
000236
000000
000000
300030003000320033003600
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
L_S_PROCESS-NODE
-1
FFFF
FFFF
FFFFFFFF
L_S_PROCESS-TH_CMD_MEMENTO
Table IT_42[5x52]
No. 2 Ty. FUNCTION
Name RSBATCH_EXECUTE_PROCESS
ID
DTPR_10616_1
455553333353222222222222222222
4402F10616F1000000000000000000
000000000000000000000000000000
000000000000000000000000000000
44005400500052005F00310030003600310036005F0031002000200020002000200020002000200020002000200020
I_DIALOG_DEBUG_MODE
2
0
0
0
2000
PROCESS
238
E000
E000
EE000000
G_T_COLS[]
Table[initial]
SY-REPID
SAPLRSBATCH
5454554454422222222222222222222222222222
310C232143800000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5300410050004C00520053004200410054004300480020002000200020002000200020002000200020002000200020
L_MODULE_TYPE
M
4
D
0
0
4D00
G_PROCESS_TYPE
2222222222
0000000000
0000000000
0000000000
2000200020002000200020002000200020002000
%_FL2*CTRL_200_WAIT
<initial>
<initial>
<initial>
<<iinniittiiaall>>
ICON_SELECT_DETAIL
@16@
4334
0160
0000
0000
4000310036004000
L_S_CTRL-LANGU
E
4
5
0
0
4500
SY-LANGU
E
4
5
0
0
4500
SYST-REPID
SAPLRSBATCH
5454554454422222222222222222222222222222
310C232143800000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5300410050004C00520053004200410054004300480020002000200020002000200020002000200020002000200020
SYST
##########################A###P#######|#########<#############################T#########XC####
0000000000000000000000100040005000000070000000003000000000000000000000000000105000100000540000
10000010000010000000109010101000000000C000000000C000000000000000000000000000604000E00000830500
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
0100000000000000000000000100000000000000000000000100000000000000000000000000000001000000190000
%_FL2*CTRL_1100
<initial>
<initial>
<initial>
<<iinniittiiaall>>
%_DUMMY$$
2222
0000
0000
0000
2000200020002000
L_MODULE_NAME
CL_RSBK_PROCESS
4455544555444552222222222222222222222222
3CF232BF02F35330000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
43004C005F005200530042004B005F00500052004F0043004500530053002000200020002000200020002000200020
%_SPACE
2
0
0
0
2000
G_T_BATCH_SERV
00
22222222222222222222222222222222222222222222222222222222222222222222222222222222233
00000000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
L_S_CTRL-PROCESS_TYPE
DTP_LOAD
4555444422
440FCF1400
0000000000
0000000000
4400540050005F004C004F004100440020002000
G_SUBRC
0
0000
0000
00000000
L_S_CTRL-BATCH_ID
DTPR_10616_1
455553333353222222222222222222
4402F10616F1000000000000000000
000000000000000000000000000000
000000000000000000000000000000
44005400500052005F00310030003600310036005F0031002000200020002000200020002000200020002000200020
OKCODE
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
L_S_CTRL-BATCH_PROCESS
238
2222223332
0000002380
0000000000
0000000000
2000200020002000200020003200330038002000
SAVEOK
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
L_PARAMETER
ۿĂȁ#ㄴ㌰##༅##(Ѐޱ##########PROCESSྫ##ꨨ##Ѐڪ##ꨌ##Ѐ###ꨄ##Ѐª##ꨂ##Ȁྭ##ꨴ##Ѐª##ꨨ###ྮ##갴##⠀¼#砠) ㈀㌀㘀##ÿ#
F008330000020B00000000005544455A002000A000000A000000A000000A003000A002100A003000B0220000000FF0
F2104000500801000000000002F3533B008800A00C800A004800A002000D004800A008400E004F00C0090000000FF0
0000330000000000000000000000000000A000000A000000A000000A000000A000000A000000A0020070333333FF00
61201300F0004700000000000000000F00A004600A004800A004000A002F00A004000A008F00C0080080000236FF00
FF060201010280003431303300000000050F0000000028000004B10700000000000000000000000000000000000000
L_R_BATCH_EXECUTE
{O:initial}
F0000000
F0000000
FF00000000000000
L_RETURN
<empty string>
10000000
40001000
1400000001000000
L_T_MSG
Table[initial]
%_TAG*CTRL_200_VAL
<initial>
<initial>
<initial>
<<iinniittiiaall>>
G_CURSOR_LINE
0
0000
0000
00000000
SY-SUBRC
0
0000
0000
00000000
No. 1 Ty. EVENT
Name START-OF-SELECTION
L_T_CTRL
Table IT_26[1x424]
\PROGRAM=RSBATCH_EXECUTE_PROZESS\DATA=L_T_CTRL
Table reference: 15
TABH+ 0(20) = D08B4C00DF070000000000000000000000000000
TABH+ 20(20) = 0F0000001A00000001000000A8010000FFFFFFFF
TABH+ 40(16) = 040000005090000004000000C130C000
store = 0xD08B4C00DF070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 15 (0x0F000000)
label = 26 (0x1A000000)
fill = 1 (0x01000000)
leng = 424 (0xA8010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000013
occu = 4 (0x04000000)
accKind = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniNo)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
stMode = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
isUsed = 1
isCtfyAble = 1
hasScndKeys = 0
hasRowId = 0
scndKeysOutdated = 0
scndUniKeysOutdated = 0
----- Shareable Table Header Data -----
tabi = 0x10854C00DF070000
pgHook = 0x508C4C00DF070000
idxPtr = 0x0000000000000000
id = 21 (0x15000000)
shmTabhSet = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 508 (0xFC010000)
lineAlloc = 12 (0x0C000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
rowId = 18446744073709551615
scndKeyAdmin = 0x0000000000000000
DTPR_10616_1 238
4555533333532222222222222222222222223332222222222222222222222222222222222222222222222222222222
4402F10616F10000000000000000000000002380000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
44005400500052005F00310030003600310036005F0031002000200020002000200020002000200020002000200020
SYST
##########################A###P#######|#########<#############################T#########XC####
0000000000000000000000100040005000000070000000003000000000000000000000000000105000100000540000
10000010000010000000109010101000000000C000000000C000000000000000000000000000604000E00000830500
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
0100000000000000000000000100000000000000000000000100000000000000000000000000000001000000190000
L_S_CTRL
DTPR_10616_1 238 BIDTPR_10616_1 07100200cab-bi-prod1_
4555533333532222222222222222222222223332244455553333353222222222222222222333333336662662776635
4402F10616F100000000000000000000000023800294402F10616F100000000000000000007100200312D29D02F41F
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
44005400500052005F00310030003600310036005F0031002000200020002000200020002000200020002000200020
SCREEN
%_17NNS0005639652_%_%_%_%_%_%_
2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
5F17EE30005639652F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
25005F00310037004E004E00530030003000300035003600330039003600350032005F0025005F0025005F0025005F
L_S_CTRL-BATCH_PROCESS
238
2222223332
0000002380
0000000000
0000000000
2000200020002000200020003200330038002000
%_SPACE
2
0
0
0
2000
L_S_PAR-WP_NO
12
332
120
000
000
310032002000
ID
DTPR_10616_1
455553333353222222222222222222
4402F10616F1000000000000000000
000000000000000000000000000000
000000000000000000000000000000
44005400500052005F00310030003600310036005F0031002000200020002000200020002000200020002000200020
L_PROCESS
238
E000
E000
EE000000
L_S_HEADER-HOLD_PAR_PROCS
X
5
8
0
0
5800
SY
##########################A###P#######|#########<#############################T#########XC####
0000000000000000000000100040005000000070000000003000000000000000000000000000105000100000540000
10000010000010000000109010101000000000C000000000C000000000000000000000000000604000E00000830500
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
0100000000000000000000000100000000000000000000000100000000000000000000000000000001000000190000
PROCESS
999999999
FC93
F9AB
FFC99A3B
Internal notes
The termination was triggered in function "ab_jmess"
of the SAP kernel, in line 1411 of the module
"//bas/720_REL/src/krn/runt/abdynpro.c#7".
The internal operation just processed is "MESS".
Internal mode was started at 20140530071002.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=1724)
When : 5/30/2014 7:9:54.12
Threads : 2
Computer Name : NGUKSVRMDS040
User Name : pwbadm
Number of Processors: 4
Processor Type: Intel64 Family 6 Model 37 Stepping 1
Windows Version : 6.1 Current Build: 7601
State Dump for Thread Id 1374
0000000002178EF0 0000000140F6F2A1 0020002000200020 disp+work!DumpStacks [ntstcdbg.c (548)]
0000000002178FF0 000000013FB0E304 0000000074D126B0 disp+work!NTDebugProcess [ntstcdbg.c (383)]
0000000002179020 000000013FD1C439 0000000074D126B0 disp+work!CTrcStack2 [dptstack.c (354)]
0000000002179070 000000013FD21A7F 0000000002179AD0 disp+work!rabax_CStackSave [abrabax.c (8649)]
0000000002179980 000000013FCD37FC 000000000000005C disp+work!ab_rabax [abrabax.c (1419)]
00000000021799C0 000000013FD0BBE1 0000000000000000 disp+work!ab_jmess [abdynpro.c (1418)]
0000000002179B50 000000013FD7E5D8 0000000000000001 disp+work!ab_extri [abextri.c (721)]
0000000002179BA0 000000013FD7EEC5 0000000000000001 disp+work!ab_xevent [abrunt1.c (278)]
0000000002179C30 000000013FD5C589 000007DF000002A0 disp+work!ab_trigg [abrunt1.c (57)]
0000000002179CC0 000000013FB77126 0000000000000016 disp+work!ab_run [absubmit.c (511)]
0000000002179E70 000000013FB7BA2D 0000000000000000 disp+work!dynpmcal [dymainstp.c (2732)]
0000000002179F00 000000013FB7ACDC 000000000217A0E0 disp+work!dynppai0 [dymainstp.c (1355)]
0000000002179FD0 000000013FB34EEF 0000000000000020 disp+work!dynprctl [dymainstp.c (470)]
000000000217F3C0 000000013F9C3CC0 0000000000000000 disp+work!dynpen00 [dymain.c (2026)]
000000000217F690 000000013F9C44BC FFFFFFFFFFFFFF00 disp+work!TskhLoop [thxxhead.c (4871)]
000000000217F6F0 000000013F8EC603 00000000000D9E9C disp+work!ThStart [thxxhead.c (1195)]
000000000217F790 000000013F8C10A1 FFFFFFFF00000001 disp+work!DpMain [dpxxdisp.c (1174)]
000000000217F7C0 0000000141246B8E 0000000000000001 disp+work!nlsui_main [thxxanf.c (80)]
000000000217F7F0 000000007799652D 0000000000000000 disp+work!__tmainCRTStartup [crtexe.c (552)]
000000000217F820 0000000077ACC541 0000000000000000 kernel32!BaseThreadInitThunk
000000000217F870 0000000000000000 0000000000000000 ntdll!RtlUserThreadStart
State Dump for Thread Id 290
000000000E0BF880 000007FEFDAB3C2F 00000000DBAAC265 ntdll!NtFsControlFile
000000000E0BF8F0 0000000141139FAF FFFFFFFFFFFFFFFE KERNELBASE!ConnectNamedPipe
000000000E0BF990 0000000074C81D9F 00000000024BC0D0 disp+work!SigIMsgFunc [signt.c (717)]
000000000E0BF9C0 0000000074C81E3B 0000000074D12AC0 MSVCR100!endthreadex
000000000E0BF9F0 000000007799652D 0000000000000000 MSVCR100!endthreadex
000000000E0BFA20 0000000077ACC541 0000000000000000 kernel32!BaseThreadInitThunk
000000000E0BFA70 0000000000000000 0000000000000000 ntdll!RtlUserThreadStart
List of ABAP programs affected
Index Typ Program Group Date Time Size Lang.
0 Prg RSBATCH_EXECUTE_PROZESS 0 13.08.2013 12:28:38 45056 E
1 Prg SAPMSSY0 1 13.08.2013 09:12:51 111616 E
2 Prg SAPMSSYD 1 13.08.2013 10:17:05 23552 E
3 Prg SAPFSYSCALLS 1 07.03.2005 18:01:13 8192 E
4 Prg RSDBRUNT 0 13.08.2013 10:51:31 306176 E
5 Prg SAPLSPRI 5 13.08.2013 10:49:40 407552 E
6 Typ PRI_PARAMS 0 27.10.1998 15:01:35 5120
7 Typ ARC_PARAMS 0 08.08.1997 14:45:20 5120
8 Typ PRI_LAYOUT 0 04.09.2002 14:38:36 3072
9 Typ PRIPAR_EXT 0 09.09.2011 20:56:18 3072
10 Typ PRIPAR_EX2 0 09.09.2011 20:54:51 2048
11 Typ PRIPAR_EX3 0 09.09.2011 20:54:52 3072
12 Typ TPRI_DEF 0 01.02.2001 17:50:49 5120
13 Prg SAPLSPOO 13 13.08.2013 10:14:36 181248 E
14 Typ TSP03 0 13.08.1998 16:56:08 5120
15 Typ USR01 0 09.09.2011 20:55:50 4096
16 Typ TSP1D 0 09.09.2011 20:57:01 5120
17 Prg SAPLRSPOLSTDRV 17 28.05.2009 08:18:25 64512 E
18 Typ TSPOPTIONS 0 06.12.1996 16:09:18 2048
19 Prg SAPCNVE 19 07.03.2005 18:01:13 9216 E
20 Prg SAPLSPOC 20 09.09.2011 21:19:41 177152 E
21 Typ RSPOCHECK 0 14.07.1997 13:01:20 4096
22 Typ DEVPAR 0 09.09.2011 20:54:15 3072
23 Typ RSPOATTR 0 19.01.2000 18:34:33 2048
24 Typ RSSCR 0 23.11.1999 09:24:41 5120
25 Prg RSDBSPBL 0 07.03.2005 18:01:13 84992 E
26 Prg SAPDB__S 0 07.03.2005 18:01:13 21504 E
27 Typ VARID 0 28.05.2009 08:12:55 5120
28 Typ SSCRFIELDS 0 02.05.1997 13:16:39 5120
29 Prg RSDBSPVA 0 13.08.2013 10:51:31 160768 E
30 Prg %_CSYDB0 0 07.03.2005 18:01:13 40960 E
31 Typ RSVAMEMKEY 0 16.12.1996 19:31:50 2048
32 Prg RSDBSPMC 0 05.09.2006 14:14:08 92160 E
33 Typ DDSHDESCR 0 28.11.1997 16:26:30 4096
34 Typ SPPARAMS 0 07.03.1997 14:48:48 2048
35 Prg SAPLICON 35 13.12.2007 11:37:48 31744 E
36 Prg %_CICON 35 13.12.2007 11:37:48 126976 E
37 Typ ICONT 0 05.09.2006 14:14:08 2048
38 Prg SAPLSABE 38 09.09.2011 21:09:40 14336 E
39 Prg SAPLSECU 39 13.08.2013 10:16:43 110592 E
40 Typ RSSUBINFO 0 22.11.1999 21:15:17 3072
41 Prg RSDBSPVD 0 09.09.2011 21:33:31 102400 E
42 Typ DFIES 0 09.09.2011 20:54:19 10240
43 Typ VARI 0 16.12.1996 19:38:11 6144
44 Typ RSDSFIELDS 0 28.05.2009 08:12:29 3072
45 Prg %_CRSDS 0 07.03.2005 18:01:13 11264 E
46 Typ RSDSEXPR 0 16.12.1996 19:31:30 3072
47 Typ RVARI 0 18.06.1999 11:23:08 4096
48 Prg SAPLSVAR 48 13.08.2013 10:49:34 936960 E
49 Typ RSVARKEY 0 16.12.1996 19:31:51 2048
50 Prg SAPLSSEL 50 13.08.2013 10:42:32 1699840 E
51 Prg RSDBSPDS 0 13.12.2007 11:37:48 66560 E
52 Typ RSEXFCODE 0 18.07.1997 17:04:17 2048
53 Prg SAPLDSYA 53 13.08.2013 10:45:29 52224 E
54 Prg SAPFSDS1 53 07.03.2005 18:01:13 61440 E
55 Typ TDCLD 0 14.07.1998 14:53:43 5120
56 Prg SAPLSDOD 56 13.08.2013 10:42:31 50176 E
57 Typ DOKIL 0 07.04.1997 18:29:04 3072
58 Prg SAPLLANG 58 09.09.2011 21:12:32 11264 E
59 Typ T002 0 25.09.2007 11:09:36 2048
60 Prg SAPFSPOR 0 24.06.2008 18:36:49 16384 E
61 Typ RSPARINT 0 10.03.1995 17:53:00 2048
62 Prg SAPLSCNT 62 07.03.2005 18:01:13 34816 E
63 Prg SAPSHDTV 62 13.08.2013 08:38:56 38912 E
64 Prg SAPFGUICNTL 1 07.03.2005 18:01:13 27648 E
65 Prg SAPLOLEA 65 13.08.2013 08:38:34 110592 E
66 Prg SAPLSGUI 66 04.12.2009 20:43:32 105472 E
67 Prg SAPLSTTM 67 09.09.2011 21:26:18 79872 E
68 Prg SAPLSBDC 68 13.12.2007 10:50:07 49152 E
69 Prg SAPLSFES 69 13.08.2013 10:47:09 316416 E
70 Prg SAPLTHFB 70 13.08.2013 10:21:30 472064 E
71 Typ WPINFO 0 28.05.2009 08:12:57 6144
72 Prg SAPLURFC 72 13.08.2013 10:49:32 29696 E
73 Prg SAPLSPLUGIN 73 09.09.2011 21:19:29 9216 E
74 Typ SWCBCONT 0 09.09.2011 20:56:57 3072
75 Typ OLE_VERBS 0 09.02.1995 13:23:37 2048
76 Typ OLE_PA 0 13.01.1995 11:06:59 2048
77 Typ SSCRTEXTS 0 15.08.1997 14:15:15 3072
78 Prg SAPLRSBATCH 78 13.08.2013 12:29:38 689152 E
79 Prg /1BCDWBEN/SAPLREN0002 79 23.11.2005 13:29:42 294912 E
80 Prg SAPLSENA 80 28.05.2009 08:20:47 39936 E
81 Prg SAPLBTCH 81 13.08.2013 10:51:12 2248704 E
82 Prg SAPLRS_GENERAL 82 13.08.2013 12:20:02 120832 E
83 Prg /1BCDWBEN/SAPLREN0003 83 23.11.2005 13:29:44 282624 E
84 Prg SAPLSYDB 84 09.09.2011 21:28:17 65536 E
85 Typ MSXXLIST_V6 0 28.05.2009 08:12:22 4096
86 Typ BAL_S_MSG 0 09.09.2011 20:53:51 7168
87 Prg CL_RSBK_PROCESS===============CP 87 10.09.2011 08:11:36 103424 E
88 Prg IF_RSBATCH_CALLBACK===========IP 78 09.09.2011 22:39:45 9216 E
89 Prg IF_RSBATCH_EXECUTE============IP 78 09.09.2011 22:39:45 8192 E
90 Typ RSBK_S_PROCESS 0 09.09.2011 20:56:47 4096
91 Typ RSBK_S_CMD_MEMENTO 0 09.09.2011 20:54:56 2048
92 Prg CL_RSBK_REQUEST===============CP 92 13.08.2013 11:53:19 222208 E
93 Prg CL_RSBK_REQUEST_GENERAL=======CP 93 10.09.2011 08:12:31 38912 E
94 Prg SAPLRRSI 94 13.08.2013 12:29:38 393216 E
95 Typ RSD_S_COB_PRO 0 09.09.2011 20:56:49 26624
96 Prg CL_RSR========================CP 96 13.08.2013 12:06:59 180224 E
97 Prg CL_RS_BASE====================CP 97 13.08.2013 12:27:37 15360 E
98 Prg CL_RSD_CHA====================CP 98 13.08.2013 11:55:18 563200 E
99 Prg CL_RSD_IOBJ_VERS==============CP 99 13.08.2013 12:03:26 301056 E
100 Prg SAPLRRMS 100 13.08.2013 12:29:38 49152 E
101 Prg SAPLRRI1 101 13.08.2013 12:29:38 496640 E
102 Typ RSR_S_DEBUGFLAGS 0 13.08.2013 12:01:28 14336
103 Prg CL_RSDDTREX_CORE==============CP 103 13.08.2013 12:29:38 49152 E
104 Prg SAPLRSDI 104 09.09.2011 22:19:14 43008 E
105 Prg SAPLRSDG_IOBJ_DB_READ 105 13.08.2013 12:29:38 355328 E
106 Typ RSD_S_AGGRINFO 0 09.09.2011 20:55:04 2048
107 Typ RSD_S_VIOBJ 0 09.09.2011 20:55:07 30720
108 Prg SAPLRSDN_IOBJ 108 13.08.2013 12:29:38 163840 E
109 Prg CL_RSROA_VQ_SERVICES==========CP 109 13.08.2013 12:29:37 86016 E
110 Prg CL_ABAP_ELEMDESCR=============CP 110 28.05.2009 08:29:24 41984 E
111 Prg CL_ABAP_DATADESCR=============CP 111 28.05.2009 08:29:18 21504 E
112 Prg CL_ABAP_TYPEDESCR=============CP 112 13.08.2013 10:48:27 33792 E
113 Prg CL_ABAP_REFDESCR==============CP 113 13.08.2013 10:48:27 34816 E
114 Prg CL_ABAP_STRUCTDESCR===========CP 114 13.08.2013 10:48:27 49152 E
115 Prg CL_ABAP_COMPLEXDESCR==========CP 115 28.05.2009 08:29:17 19456 E
116 Prg CL_ABAP_TABLEDESCR============CP 116 09.09.2011 21:11:02 37888 E
117 Prg CL_ABAP_CLASSDESCR============CP 117 28.05.2009 08:29:15 34816 E
118 Prg CL_ABAP_OBJECTDESCR===========CP 118 28.05.2009 08:29:28 37888 E
119 Prg CL_ABAP_INTFDESCR=============CP 119 28.05.2009 08:29:25 27648 E
120 Prg CL_ABAP_SOFT_REFERENCE========CP 120 18.11.2005 14:35:28 10240 E
121 Prg CL_ABAP_REFERENCE=============CP 121 07.03.2005 18:01:13 8192 E
122 Prg CL_RSRTS_METADATA=============CP 122 13.08.2013 12:28:25 106496 E
123 Prg CL_RSRTS_METADATA_R3IS========CP 123 13.08.2013 11:55:22 157696 E
124 Prg IF_RSRTS_METADATA=============IP 117 13.08.2013 11:55:54 26624 E
125 Prg %_CABAP 117 28.05.2009 08:14:56 36864 E
126 Prg IF_SERIALIZABLE_OBJECT========IP 117 07.03.2005 18:01:13 5120 E
127 Prg CL_RSROA_VQ_METADATA==========CP 127 13.08.2013 11:55:22 252928 E
128 Prg CL_RSL_ME_METADATA============CP 128 13.08.2013 12:28:21 233472 E
129 Prg IF_RSDRV_TREX_NAME_MAPPER=====IP 117 13.08.2013 12:29:31 8192 E
130 Prg CL_RSDDLTIP_IPROV_TABLE=======CP 130 13.08.2013 11:55:15 147456 E
131 Prg CL_RSAN_PR_ANPR_PROV_TRANSIENTCP 131 13.08.2013 11:55:06 117760 E
132 Prg CL_RSD_DTA====================CP 132 13.08.2013 12:03:25 320512 E
133 Typ LVC_S_ROID 0 19.01.2000 18:31:34 2048
134 Typ RSZCOMPKEY 0 09.09.2011 20:55:16 3072
135 Prg IF_RSO_TLOGO_MAINTAIN=========IP 117 09.09.2011 22:36:34 13312 E
136 Prg IF_RSD_DTA====================IP 117 09.09.2011 22:35:40 30720 E
137 Prg CL_RSRTS_METADATA_ODP=========CP 137 13.08.2013 12:03:31 396288 E
138 Prg IF_RSRTS_TRPR=================IP 117 13.08.2013 12:10:34 10240 E
139 Prg CL_RSR_QPROV_METADATA=========CP 139 13.08.2013 11:55:23 248832 E
140 Typ RSD_S_DTA_PRO 0 09.09.2011 20:55:08 26624
141 Typ RSD_S_IOBJ_OBN 0 09.09.2011 20:56:49 2048
142 Prg CX_RSD_IOBJ_NOT_FOUND=========CP 142 09.09.2011 22:36:07 16384 E
143 Prg CX_RSD_IOBJ_EXCEPTION=========CP 143 09.09.2011 22:36:07 14336 E
144 Prg CX_RS_STATIC_CHECK============CP 144 09.09.2011 22:37:44 19456 E
145 Prg CX_RS_ERROR===================CP 145 09.09.2011 22:37:36 13312 E
146 Prg CX_STATIC_CHECK===============CP 146 18.11.2005 14:35:29 11264 E
147 Prg CX_ROOT=======================CP 147 09.09.2011 21:51:41 13312 E
148 Prg CX_NO_CHECK===================CP 148 18.11.2005 14:35:29 11264 E
149 Typ RSAROUT 0 09.09.2011 20:49:50 4096
150 Typ RSAROUTT 0 09.09.2011 20:50:52 2048
151 Typ RSDVDPA 0 09.09.2011 20:56:49 9216
152 Typ RSDIOBJV 0 09.09.2011 20:54:57 5120
153 Typ RSDKYF 0 09.09.2011 20:46:44 5120
154 Typ RSDVTIM 0 09.09.2011 20:56:49 12288
155 Typ RSDVUNI 0 09.09.2011 20:56:49 9216
156 Typ RSDVCHA 0 09.09.2011 20:55:09 14336
157 Prg CL_RSDRC_NCUM_GEN_TYPES=======CP 157 13.08.2013 12:28:48 9216 E
158 Prg CL_RSD_IOBJ_UTILITIES=========CP 158 09.09.2011 22:25:11 57344 E
159 Prg SAPLRSDN 159 13.08.2013 12:29:38 86016 E
160 Prg SAPLRSVERS 160 13.08.2013 12:29:38 371712 E
161 Typ RSNPAR 0 09.09.2011 20:55:07 3072
162 Prg SAPLSTR4 162 13.08.2013 10:42:32 74752 E
163 Prg %_CTRNSP 162 07.03.2005 18:01:13 10240 E
164Hi Hardeep,
Looks like the transformation and DTP need to be activated again.
The error is RSBK (299) - 'Invalid program status'. So please activate the transformation and DTP possibly activate the DSO's too.
It should then work.
Thanks
Amit -
Dump while copying the entries in view cluster
Hi Experts,
I am having a scenario where i am getting the dump while copying the entries through the vies cluster.
I have 2 tables CU00 and CU01. CU01 is depended on CU00.
CU00- it is having schema which are defined by the user.(SCHEMA-P,DESC)
CU01- this table is having the different tabs in a tab strip for a each of the user defined schema.(SCHEMA-P,SEQNO-P,TABID)
the data will be as follows
In CU00
SCHEMA1 first schema
SCHEMA2 second schema
In CU01
SCHEMA1 01 TAB1
SCHEMA1 02 TAB2
SCHEMA2 01 TAB2
SCHEMA2 02 TAB3
I maintained above 2 tables in a view cluster by making CU00 is the start point and defined the field dependencies as well.
in the T-code SE54 i tried to copy the existing schema and all its dependencies(means all the dependent entries in the CU01 table also).
when i pressed the SAVE button it is going for the dump by saying due to duplicate entries in the table CU01.
but it should check the consistency and display the error message when i pressed the COPY key.
I am badly struck up here. Please help me on this issue.
thanks in advance.Hi Gouri,
CU01 and CU00 both are dictionary tables.
What I think is, while copying all the dependencies for a particular schema the system ha to check whether the data can be inserted into the child tables or not. I too dont know whether this can be done or not.
If not, it should display an error message stating that " primary key violation occurs please use different key values..."
thanks for the reply. -
ENT-06954: Error while Displaying BIBean for Cube/Dimension Dataviewer.
Hi all,
I have defined a cube with three dimensions. All elements are deployed and the mappings is executed successfully. If I try to open the dataviewer either for the cube or for the dimensions I receive the following errors:
ENT-06954: Error while Displaying BIBean for Cube Dataviewer.
at oracle.wh.ui.owbcommon.dataviewer.dimensional.CubeDataViewerMain.getDataviewObject(CubeDataViewerMain.java:391)
at oracle.wh.ui.owbcommon.dataviewer.dimensional.CubeDataViewerEditor._init(CubeDataViewerEditor.java:66)
at oracle.wh.ui.editor.Editor.init(Editor.java:1115)
at oracle.wh.ui.editor.Editor.showEditor(Editor.java:1431)
at oracle.wh.ui.owbcommon.IdeUtils._tryLaunchEditorByClass(IdeUtils.java:1431)
at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1344)
at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1362)
at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:864)
at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:851)
at oracle.wh.ui.console.commands.DataViewerCmd.performAction(DataViewerCmd.java:19)
at oracle.wh.ui.console.commands.TreeMenuHandler$1.run(TreeMenuHandler.java:188)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
ENT-06972: Error while Displaying BIBean for Dimension Dataviewer.
at oracle.wh.ui.owbcommon.dataviewer.dimensional.DimDataViewerMain.getDimensionListObject(DimDataViewerMain.java:479)
at oracle.wh.ui.owbcommon.dataviewer.dimensional.DimDataViewerEditor._init(DimDataViewerEditor.java:89)
at oracle.wh.ui.editor.Editor.init(Editor.java:1115)
at oracle.wh.ui.editor.Editor.showEditor(Editor.java:1431)
at oracle.wh.ui.owbcommon.IdeUtils._tryLaunchEditorByClass(IdeUtils.java:1431)
at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1344)
at oracle.wh.ui.owbcommon.IdeUtils._doLaunchEditor(IdeUtils.java:1362)
at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:864)
at oracle.wh.ui.owbcommon.IdeUtils.showDataViewer(IdeUtils.java:851)
at oracle.wh.ui.console.commands.DataViewerCmd.performAction(DataViewerCmd.java:19)
at oracle.wh.ui.console.commands.TreeMenuHandler$1.run(TreeMenuHandler.java:188)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
In another warehouse this function works properly. I am using OWB 10gR2 (10.2.0.1.31).
Any hints to fix this issue would be appreciated.
Thanks in Advance, C.If you run OWB using the supplied shell script or batch file are there other errors on the console before the exception. OWB uses a component (OLAPI does some validation over and above any other) which dumps the errors on the the standard output which often illustrates some invalid metadata in the OLAP catalog.
-
Dump while downloading to excel file!!
Hi,
I'm getting a dump while downloading the ALV (Grid) report into an excel file.
When i inspected, the dump was - " Only character-type data objects are supported at the argument position "obj". In this particular case, the operand "obj" has the non-charcter-type type "P". "-
i'm having few currency values to be displayed.
Thought of an alternative my moving the values into char type field and to display it, but the values are getting rounded of.
Thanks in advance..
Any help would be suitably rewarded.
Kumar R.All the internal fields to be char type..if download functionality to be given..
if there is any issue in doing this...
create any another field in ur table(internal ) of type c length same like ur coressponding currency or quatity field....
move these fields into ur new char field and then prepare fieldcatlog on this..
hope this helps...
i handled like this only..
Praveen . -
Dump while Select files - Confirm Target step in MOPZ
Hi All,
I'm getting dump while trying to confirm files in mopz. This is in the step confirm target.
Please see this link, issue exactly what we have but the notes cannot be implemented which is in this link Maintenance Optimizer: "Value loss during allocation"
Kindly have a look on below dump
Category ABAP Programming Error
Runtime Errors CONVT_DATA_LOSS
Except. CX_SY_CONVERSION_DATA_LOSS
ABAP Program CL_MO_SMP_ADAPTER=============CP
Application Component SV-SMG-MAI
Date and Time 16.12.2011 00:32:20
Short text
Value loss during allocation.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_MO_SMP_ADAPTER=============CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
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 that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_DATA_LOSS', was not
caught in
procedure "GET_2ND_CHECK_RESULT" "(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:
Value "01200314695000002461|01200314694900013074:01200314694900009502|" was
allocated in a field which is not long enough.
Therefore the target field could not store all information of
"01200314695000002461 01200314694900013074:01200314694900009502 ".
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"CONVT_DATA_LOSS" "CX_SY_CONVERSION_DATA_LOSS"
"CL_MO_SMP_ADAPTER=============CP" or "CL_MO_SMP_ADAPTER=============CM00A"
"GET_2ND_CHECK_RESULT"
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.
The exception must either be prevented, caught within proedure
"GET_2ND_CHECK_RESULT" "(METHOD)", or its possible occurrence must be declared
in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP Release..... 702
SAP Basis Level. 0004
Application server... "OMEGASOL"
Network address...... "172.16.1.13"
Operating system..... "Windows NT"
Release.............. "6.0"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 5
Shortdump setting.... "full"
Database server... "OMEGASOL"
Database type..... "DB6"
Database name..... "OS1"
Database user ID.. "SAPOS1"
Terminal.......... "124.123.157.231"
Char.set.... "C"
SAP kernel....... 720
created (date)... "Aug 5 2010 02:21:12"
create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
Database version. "DB6_81 "
Patch level. 59
Patch text.. " "
Database............. "DB6 08.02., DB6 09."
SAP database version. 720
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0, Windows NT 6.1"
Memory consumption
Roll.... 0
EM...... 33518336
Heap.... 0
Page.... 81920
MM Used. 32855760
MM Free. 658336
User and Transaction
Client.............. 100
User................ "OS1_USER"
Language key........ "E"
Transaction......... " "
Transaction ID...... "344F27E12581F11B97DA920465FA5E5A"
EPP Whole Context ID.... "920465FA5E5A1ED189E9DA9C282A77DA"
EPP Connection ID....... "920465FA5E5A1ED189E9DAF1CA0A37DA"
EPP Caller Counter...... 1
Program............. "CL_MO_SMP_ADAPTER=============CP"
Screen.............. "SAPMHTTP 0010"
Screen Line......... 2
Debugger Active..... "none"
Server-Side Connection Information
Information on Caller of "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. "124.123.157.231"
Caller Port........... 8000
Universal Resource ID. "/sap/bc/webdynpro/sap/wda_mopz_plan"
Program............. "CL_MO_SMP_ADAPTER=============CP"
Screen.............. "SAPMHTTP 0010"
Screen Line......... 2
Information on Caller ofr "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. "124.123.157.231"
Caller Port........... 8000
Universal Resource Id. "/sap/bc/webdynpro/sap/wda_mopz_plan"
Information on where terminated
Termination occurred in the ABAP program "CL_MO_SMP_ADAPTER=============CP" -
in "GET_2ND_CHECK_RESULT".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 19
of the (Include) program "CL_MO_SMP_ADAPTER=============CM00A".
The termination is caused because exception "CX_SY_CONVERSION_DATA_LOSS"
occurred in
procedure "GET_2ND_CHECK_RESULT" "(METHOD)", but it was neither handled locally
nor declared
in the RAISING clause of its signature.
The procedure is in program "CL_MO_SMP_ADAPTER=============CP "; its source
code begins in line
1 of the (Include program "CL_MO_SMP_ADAPTER=============CM00A ".
Source Code Extract
Line SourceCde
1 method GET_2ND_CHECK_RESULT.
2 DATA ls_buffer TYPE smp_buffer.
3 CLEAR ev_status.
4 DATA lv_crm_id TYPE crmt_object_guid.
5 mo_controller->crm_adapter->get_crm_id(
6 IMPORTING ev_crm_id = lv_crm_id
7 ).
8 SELECT * FROM smp_buffer INTO ls_buffer WHERE crm_id EQ lv_crm_id AND action EQ mopzp_c_ac
9 ev_status = ls_buffer-action_lock.
10 ENDSELECT.
11
12 IF ev_status EQ 2.
13 DATA lt_errors TYPE mopzp_t_errors.
14
15
16 IF ls_buffer-data IS NOT INITIAL.
17 DATA lt_start TYPE mopzp_tt_system_constellation.
18 DATA lt_target TYPE mopzp_tt_system_constellation.
>>>>> call TRANSFORMATION id SOURCE XML ls_buffer-data RESULT system_base = lt_start
20 system_goal = lt_target
21 stacklist = et_targets
22 errors = lt_errors.
23 et_target_constellation = lt_target.
24 et_start_constellation = lt_start.
25 on_errors( lt_errors ).
26 ENDIF.
27
28 IF ls_buffer-error IS NOT INITIAL.
29 CLEAR lt_errors.
30 CALL TRANSFORMATION id SOURCE XML ls_buffer-error
31 RESULT errors = lt_errors.
32 on_errors( lt_errors ).
33 ENDIF.
34 ELSEIF ev_status EQ 0.
35 check_target_constellation_asc( ).
36 ENDIF.
37 endmethod.
Thanks in advance
UdayHi,
yes, upgrade to latest level is a good move to eliminate all possible bugs. Also, you can read my blog on assigning to correct product system in solman 7.1
#sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification work in SOLMAN7.1
hope it helps,
Cheers,
Nicholas Chang
Maybe you are looking for
-
Help needed in seeing the material master.
Hi all, How can i see the sales area info in a system. i.e. what material is assigned to what sales area, the mapping between the sales org., distr. channel, division and plants? I ask this because when I see some tabs/views in mm03, it asks me the s
-
Graphics problem in OS X Mavericks
Hello, Sorry for my english in advance. I have Macbook Air 13" (mid 2012) [CPU: Core i5 with GPU: HD 4000]. I faced problem with the GPU. First after update to OS X Mavericks (10.9.1) I could not boot it. It's hangs on Gray screen with Apple's logo a
-
Zen Vision:M Warranty questi
I got a ZVM (30 GB) and the extended one year 2 years of coverage. If my HDD fails in a year and a half, what will happen? I'm assuming there will be some costs like shipping, but will I get a new ZVM? Or will they just fix it's What if a newer playe
-
I posted a question this morning. Now my Inbox is full of mail from Apple Discussions Descriptions. But I have never subscribed to any. The instructions for unsubsribing are: 1) Visit <http://discussions.apple.com> 2) Login, if you have not already.
-
Dealing with functions not in class Object
Hi, while i was working on GJ i faced the following problem, when i write a generic class i have to take into my consideration those functions that i want to define for the row type class and not included in class Object (toSting() is in class Object