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
sri

Hi,
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

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
Santhosh

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./

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 loading master data (0material_attr).

Hi,
I am experiencing a short dump while loading 0matrial_attr from R/3.
Name of the runtime error :
DBIF_RSQL_SQL_ERROR
program is generating exception at this point.
***Try to insert the records into the ODS table
INSERT /BIC/B0002905000 FROM TABLE L_T_DATA.
pls help me.

Hi,
I am sure I am looking at the proper dump.
the code I have pasted is the standard code.. which I get to see in the dump analysis.
******************************dump 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 "INSERT_ODS"
"(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:
The exception must either be prevented, caught within the procedure
"INSERT_ODS"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-14400: inserted partition key does not map to
any partition"
Internal call code.........: "[RSQL/INSR//BIC/B0002905000 ]"
Please check the entries in the system log (Transaction SM21).
system log in SM 21 is below**************
After the attempt to access a database table the database system has
returned an error code which indicates that the operation concerned
could not be performed successfully.

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./

Short dump while loading statistics data - 'CX_RSR_X_MESSAGE'

Hi all,
When I am loading statistics data with Init selection, system gives short dump error. Below is the message-
The exception 'CX_RSR_X_MESSAGE' 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 'SAPLRRMS' has to be
terminated.
If anyone know the answer please share with me.
Regards,

Hi Preet,
Please find the details of short dump from ST22-
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
     and therefore caused a runtime error.
The reason for the exception is:
No text available for this exception
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_RSR_X_MESSAGE"
"SAPLRRMS" or "LRRMSU13"
"RRMS_X_MESSAGE"
Regards,

Short dump while importing Infocube

Hi,
I am trying to copy and InfoCube from one system to another. I already created the XML file from system 1. When I try to upload the XML file into system 2 I get the following run time error:
TSV_TNEW_OCCURS_NO_ROLL_MEMORY. (Short Text: No Roll Storage space of length 8896 available for OCCURS area).
Any suggestions on how to correct this issue?

Its an Memory issue ;send the short dump snapshot to BASIS for investigation and asking to increase the memory in to your system.
Hope it Helps
Chetan
@CP..

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,
Sharad

Hi,
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

Regarding Short Dump While loading data from DB Connect

Dear All,
We are having an issue of getting short dump while loading data from DB Connect to BW. We were able to load the data into BW Dev using the same data source without any problem. Whereas in Production, I am getting the following error:
Runtime Error PERFORM_CONFLICT_TAB_TYPE
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
What could be the reason for the error that I am getting

hi,
Refer Note 707986 - Writing in trans. InfoCubes: PERFORM_CONFLICT_TAB_TYPE
Summary
Symptom
When data is written to a transactional InfoCube, the termination PERFORM_CONFLICT_TAB_TYPE occurs. The short dump lists the following reasons for the termination:
("X") The row types of the two tables are incompatible.
("X") The table keys of the two tables do not correspond.
Other terms
transactional InfoCube, SEM, BPS, BPS0, APO
Reason and Prerequisites
The error is caused by an intensified type check in the ABAP runtime environment.
Solution
Workaround for BW 3.0B (SP16-19), BW 3.1 (SP10-13)
Apply the attached correction instructions.
BW 3.0B
Import Support Package 20 for 3.0B (BW3.0B Patch20 or SAPKW30B20) into your BW system. The Support Package is available oncenote 0647752 with the short text "SAPBWNews BW3.0B Support Package 20", which describes this Support Package in more detail, has been released for customers.
BW 3.10 Content
Import Support Package 14 for 3.10 (BW3. 10 Patch14 or SAPKW31014) into your BW system. The Support Package is available once note 0601051 with the short text "SAPBWNews BW 3.1 Content Support Package 14" has been released for customers.
BW3.50
Import Support Package 03 for 3.5 (BW3.50 Patch03 or SAPKW35003) into your BW system. The Support Package is available once note 0693363 with the short text "SAPBWNews BW 3.5 Support Package 03", which describes this Support Package in more detail, has been released for customers.
The notes specified may already be available to provide advance information before the Support Package is released. However, in this case, the short text still contains the term "Preliminary version" in this case.
Header Data
Release Status: Released for Customer
Released on: 18.02.2004 08:11:39
Priority: Correction with medium priority
Category: Program error
Primary Component: BW-BEX-OT-DBIF Interface to Database
Secondary Components: FIN-SEM-BPS Business Planning and Simulation
Releases
Software
Component Release From
Release To
Release And
subsequent
SAP_BW 30 30B 30B
SAP_BW 310 310 310
SAP_BW 35 350 350
Support Packages
Support
Packages Release Package
Name
SAP_BW_VIRTUAL_COMP 30B SAPK-30B20INVCBWTECH
Related Notes
693363 - SAPBWNews BW SP03 NW'04 Stack 03 RIN
647752 - SAPBWNews BW 3.0B Support Package 20
601051 - SAPBWNews BW 3.1 Content Support Package 14
Corrections Instructions
Correction
Instruction Valid
from Valid
to Software
Component Ref.
Correction Last
Modifcation
301776 30B 350 SAP_BW J19K013852 18.02.2004 08:03:33
Attributes
Attribute Value
weitere Komponenten 0000031199
Thanks
(Activate ODS/Cube and Transfer rules again..)

Short dump while executing info package in 3.5 data flow?

Hi,
i am getting short dump while executing info package while executing info package. it was working perfectly 2 days back suddenly it is giving this problem. it is a full load for info object text data and i have only 600 records. when i tried with " only info package" it is working perfectly n bringing the data into PSA. But when i use "PSA and the into data target" it is giving short dump.
i replicated Data source and also i activated transfer rules, update rules still it is not working. When i check with another info objects it is working perfectly fine. i dont know what is wrong with only particular info object.
Please find attached short dump.
Thanks

Hi,
When you load transaction data I think there is a deadlock.
Check in the process overview (transaction SM50) the waiting processes are in program SAPLSENA .
The program SAPLSENA is the lock handler tool.
Also check if ACR is running on this target while your load is happening.
Check in SM12 if there are any lock entries for the Infoobject to which you are loading data and on RSICCONT table .
Try reloading after deleting the locks manually.
Regards.

System Throws short dump while executing data source 2LIS_11_VASCL in RSA3.

Hello Experts,
I got short dump while executing data source 2LIS_11_VASCL in RSA3.
The details are as follow.
When importing object "MC11VA0SCL_TAB", the structure did not match the
structure of the target object. The error occurred in component
no. 567.
This may be due to one of the following reasons:
- the structure is actually different (the next field has, for
example, a different data type) or
- the same sequence of components were exported and imported,
but the fields were from other include units.
I have checked source and target fields and those are of same length and data type.
Could you please give some points why this short dump occurs.
Thanks
Konda Reddy

Hi,
This error is not between BI and R/3. It is within R/3. You may have setup data and then modified the datasource.
Delete setup data, generate your datasource again. Setup data and try again.
If you are on a live system with data setup after a downtime and you do not want to delete it, then bring your datasource to the original state when you setup data and pull data.
Cheers....

Short dump while changing the end date of infotype 0167 through PA30

Hi all,
I am getting short dump while changing the end date of infotype 0167(Health Plans) through Tcode PA30.
dump descript is as below
An exception occurred that was not caught.
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_HRPA_VIOLATED_POSTCOND
Date and Time          11.03.2010 07:06:26
What happened?
    The exception 'CX_HRPA_VIOLATED_POSTCONDITION' 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_HRPA_SAPUP50R_ADAPTER======CP' has to be
    terminated.
thanks
shahid

Search OSS Notes for that.

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!

Short dump while client export

Hi,
I am trying to export a client from BI test system, I am getting the below message:
InfoProvider ZSEBCST02 has been changed in the meantime
Message no. UCM0142
Diagnosis
InfoProvider ZSEBCST02 is used in data basis QinetiQ Data Basis Management as the data target of data stream Totals Records. The InfoProvider has been changed since you last saved the data basis. Therefore, the definition of the data model of data basis QinetiQ Data Basis Management is now based on the state of the InfoProvider before it was last changed and may be obsolete.
System Response
The saved version of data basis QinetiQ Data Basis Management will remain active for now.
Procedure
Check the data model of data basis QinetiQ Data Basis Management as to whether adjustments need to be made to the changed definition of InfoProvider ZSEBCST02.
Save data basis QinetiQ Data Basis Management.
The client export process does not start and it throws a short dump:
Runtime Errors         MESSAGE_TYPE_X
Date and Time          01.08.2008 11:05:02
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:
Program error(s)
Long text of error message:
Diagnosis
A program error occurred.
System Response
Processing terminated
Procedure
Please notify SAP.
Procedure for System Administration
Technical information about the message:
Message class....... "UGMD"
Number.............. 000
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_UG_MD_STORAGE_CHAR_LOCAL===CP" or "CL_UG_MD_STORAGE_CHAR_LOCAL===CM00N"
"IF_UG_MD_STORAGE_CHAR~TRANSPORT_BY_SEL"
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... "SFRNDEVSAP09"
Network address...... "10.0.32.38"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "8x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "SFRNDEVSAP09"
Database type..... "ORACLE"
Database name..... "BI1"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Feb 4 2008 00:38:16"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 67037440
Heap.... 0
Page.... 24576
MM Used. 58875536
MM Free. 3966304
User and Transaction
Client.............. 100
User................ "SUPERUSER"
Language key........ "E"
Transaction......... "SCC8 "
Transactions ID..... "44B15FDD2C31F115B69C00151736FC1B"
Program............. "CL_UG_MD_STORAGE_CHAR_LOCAL===CP"
Screen.............. "SAPMSCC1 0121"
Screen line......... 15
Information on where terminated
Termination occurred in the ABAP program "CL_UG_MD_STORAGE_CHAR_LOCAL===CP" -
in "IF_UG_MD_STORAGE_CHAR~TRANSPORT_BY_SEL".
The main program was "SAPMSCC1 ".
In the source code you have the termination point in line 491
of the (Include) program "CL_UG_MD_STORAGE_CHAR_LOCAL===CM00N".
Source Code Extract
Line
SourceCde
461
APPEND ls_idx_sel TO lt_idx_sel.
462
ENDIF.
463
464
ENDLOOP.
465
466
    set initial combination
467
LOOP AT lt_idx_sel ASSIGNING <ls_idx_sel>.
468
READ TABLE <ls_idx_sel>-t_idx INTO ld_idx_sel INDEX 1.
469
READ TABLE lt_sel ASSIGNING <ls_sel> INDEX ld_idx_sel.
470
READ TABLE lt_key INTO ls_key
471
WITH TABLE KEY fieldname = <ls_sel>-fieldname.
472
ASSIGN COMPONENT <ls_sel>-fieldname
473
OF STRUCTURE <ls_data>
474
TO <data>.
475
<data> = <ls_sel>-low.
476
ENDLOOP.
477
478
lf_found = abap_true.
479
WHILE lf_found = abap_true.
480
481
      create entry for current key selection combination
482
TRY.
483
cl_finb_tr_tabu_tabkey=>create_c(
484
EXPORTING i_tabname          = ld_tabname
485
i_key              = <ls_data>
486
i_keyfields_filled = ld_keyfields_filled
487
i_keymode          = ld_keymode
488
IMPORTING e_tabkey           = ls_transport-tabkey ).
489
         CATCH cx_root .
490
CATCH cx_finb_tr.              "N875173
>>>>>
MESSAGE x000(ugmd). ">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
492
CATCH cx_sy_dyn_call_error.    "N875173
493
MESSAGE x000(ugmd). ">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
494
ENDTRY.
495
496
INSERT ls_transport INTO TABLE et_transport.
497
498
      proceed to next combination
499
CLEAR: lf_found,
500
ld_count.
501
502
WHILE lf_found IS INITIAL.
503
504
ADD 1 TO ld_count.
505
READ TABLE lt_idx_sel ASSIGNING <ls_idx_sel> INDEX ld_count.
506
IF sy-subrc IS NOT INITIAL.
507
EXIT.
508
ENDIF.
509
510
READ TABLE lt_key INTO ls_key
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
2
SY-DBCNT
2
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
1
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
121_C
SY-UCOMM
DBAC
SY-TITLE
Client Export
SY-MSGTY
X
SY-MSGID
UGMD
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
1
SY-DATUM
20080801
SY-UZEIT
110457
SY-XPROG
SAPLSYST
SY-XFORM
SYSTEM_HOOK_OPEN_DATASET
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
14 METHOD       CL_UG_MD_STORAGE_CHAR_LOCAL===CP    CL_UG_MD_STORAGE_CHAR_LOCAL===CM00N   491
CL_UG_MD_STORAGE_CHAR_LOCAL=>IF_UG_MD_STORAGE_CHAR~TRANSPORT_BY_SEL
13 METHOD       CL_UG_MD_DISPATCHER_CHAR======CP    CL_UG_MD_DISPATCHER_CHAR======CM00J     6
CL_UG_MD_DISPATCHER_CHAR=>IF_UG_MD_CHAR_INTERNAL~TRANSPORT_BY_SEL
12 METHOD       CL_UG_MD_BUFFER_CHAR==========CP    CL_UG_MD_BUFFER_CHAR==========CM00F     3
CL_UG_MD_BUFFER_CHAR=>IF_UG_MD_CHAR_INTERNAL~TRANSPORT_BY_SEL
11 METHOD       CL_UG_MD_CHAR=================CP    CL_UG_MD_CHAR=================CM01M    59
CL_UG_MD_CHAR=>IF_UG_MD_MANUAL_TRANSPORT~TRANSPORT_BY_SEL
10 METHOD       CL_UC_MD_CHAR=================CP    CL_UC_MD_CHAR=================CM00J    53
CL_UC_MD_CHAR=>IF_UG_MD_MANUAL_TRANSPORT~TRANSPORT_BY_SEL
9 METHOD       CL_UG_MD_TR_CLIENTCOPY========CP    CL_UG_MD_TR_CLIENTCOPY========CM006    84
CL_UG_MD_TR_CLIENTCOPY=>COLLECT_FIELDNAME_CONTENT
8 METHOD       CL_UG_MD_TR_CLIENTCOPY========CP    CL_UG_MD_TR_CLIENTCOPY========CM001    41
CL_UG_MD_TR_CLIENTCOPY=>IF_FINB_TR_METHOD_CLIENTCOPY~CC_COLLECT_OBJECTS
7 METHOD       CL_FINB_TR_OBJECT_BASE========CP    CL_FINB_TR_OBJECT_BASE========CM00M    17
CL_FINB_TR_OBJECT_BASE=>IF_FINB_TR_OBJECT_CC~CC_COLLECT_OBJECTS
6 FUNCTION     SAPLFINB_TR_CC                      LFINB_TR_CCU02                         83
FINB_TR_CC_EXIT_ANALYZE
5 FORM         SAPLFINB_TR_CC                      LFINB_TR_CCF01                        688
CC_ANALYZE_CLIENT_LOCAL
4 FUNCTION     SAPLFINB_TR_CC                      LFINB_TR_CCU01                        196
FINB_TR_CC_EXIT
3 FORM         SAPLSCCR                            LSCCRF2K                              293
RUN_EXITS
2 FUNCTION     SAPLSCCR                            LSCCRU06                             1087
SCCR_PERFORM_CLIENT_COPY
1 MODULE (PAI) SAPMSCC1                            MSCC1I03                              482
CHECK_MODE
Chosen variables
Name
Val.
No.      14 Ty.          METHOD
Name CL_UG_MD_STORAGE_CHAR_LOCAL=>IF_UG_MD_STORAGE_CHAR~TRANSPORT_BY_SEL
IT_SEL
Table[initial]
IF_COMPLETE
2
0
0
0
IF_USE_MASK
X
5
8
0
0
IF_TEXT_ONLY
2
0
0
0
ET_TRANSPORT
Table[initial]
ET_TRANSPORT_SEL
Table[initial]
LD_TABNAME
T100A
533342222222222222222222222222
410010000000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
<LS_DATA>
00000000000000
2222222222222222222222222222222222222222222222222333333333333332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LD_KEYFIELDS_FILLED
01
33
01
00
00
LD_KEYMODE
G
4
7
0
0
LS_TRANSPORT-TABKEY
00000000000000
2222222222222222222222222222222222222222222222222333333333333332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
CL_ABAP_TABLEDESCR=>TABLEKIND_STD
S
5
3
0
0
%_PRINT
000                                                                                0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-REPID
CL_UG_MD_STORAGE_CHAR_LOCAL===CP
4455454455545444544455444443334522222222
3CF57FD4F34F2175F3812FCF31CDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-MSGID
UGMD
54442222222222222222
57D40000000000000000
00000000000000000000
00000000000000000000
SPACE
2
0
0
0
SY-MSGNO
000
333
000
000
000
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-XPROG
SAPLSYST
5454555522222222222222222222222222222222
310C393400000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No.      13 Ty.          METHOD
Name CL_UG_MD_DISPATCHER_CHAR=>IF_UG_MD_CHAR_INTERNAL~TRANSPORT_BY_SEL
IT_SEL
Table[initial]
IF_COMPLETE
2
0
0
0
IF_USE_MASK
X
5
8
0
0
IF_TEXT_ONLY
2
0
0
0
ET_TRANSPORT
Table[initial]
ET_TRANSPORT_SEL
Table[initial]
%_SPACE
2
0
0
0
SY-REPID
CL_UG_MD_DISPATCHER_CHAR======CP
4455454454455454445544453333334522222222
3CF57FD4F4930143852F3812DDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME
|
| 3000C000 |
| E0001C00 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| ME->DO_LOCAL |
|
3000C000
F0000C00
%_PRINT
000                                                                                0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.      12 Ty.          METHOD
Name CL_UG_MD_BUFFER_CHAR=>IF_UG_MD_CHAR_INTERNAL~TRANSPORT_BY_SEL
IT_SEL
Table[initial]
IF_COMPLETE
2
0
0
0
IF_USE_MASK
X
5
8
0
0
IF_TEXT_ONLY
2
0
0
0
ET_TRANSPORT
Table[initial]
ET_TRANSPORT_SEL
Table[initial]
%_SPACE
2
0
0
0
SY-REPID
CL_UG_MD_BUFFER_CHAR==========CP
4455454454544455444533333333334522222222
3CF57FD4F256652F3812DDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SCREEN
%_AUTOTEXT003
2545545455333222222222222222222222222222222222222222222222222222222222222222222222222222222222
5F154F4584003000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
No.      11 Ty.          METHOD
Name CL_UG_MD_CHAR=>IF_UG_MD_MANUAL_TRANSPORT~TRANSPORT_BY_SEL
IT_SEL
Table[initial]
IF_COMPLETE
2
0
0
0
IF_USE_MASK
X
5
8
0
0
IF_TEXT_ONLY
2
0
0
0
ET_TRANSPORT
Table IT_111628[0x404]
CLASS=CL_UG_MD_TR_CLIENTCOPYMETHOD=COLLECT_FIELDNAME_CONTENTDATA=LT_TRANSPORT
Table reference: 13198
TABH+ 0(20) = 007B9174FE07000000E9F174FE07000000000000
TABH+ 20(20) = 8E3300000CB401000000000094010000FFFFFFFF
TABH+ 40(16) = 04E801000017000010000000A2278001
store        = 0x007B9174FE070000
ext1         = 0x00E9F174FE070000
shmId        = 0     (0x00000000)
id           = 13198 (0x8E330000)
label        = 111628 (0x0CB40100)
fill         = 0     (0x00000000)
leng         = 404   (0x94010000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000108
occu         = 16    (0x10000000)
access       = 2     (ItAccessSorted)
idxKind      = 0     (ItIndexNone)
uniKind      = 1     (ItUnique)
keyKind      = 3     (user defined)
cmpMode      = 3     (cmpSingleMcmpU)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xA0FBAD74FE070000
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 48249 (0x79BC0000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
collHook     = 0x0000000000000000
ext2         = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
ET_TRANSPORT_SEL
Table IT_126753[0x176]
CLASS=CL_UG_MD_TR_CLIENTCOPYMETHOD=COLLECT_FIELDNAME_CONTENTDATA=LT_TRANSPORT_SEL
Table reference: 118
TABH+ 0(20) = B0315375FE070000C0294E75FE07000000000000
TABH+ 20(20) = 7600000021EF010000000000B0000000FFFFFFFF
TABH+ 40(16) = 04800400801B000010000000C1248001
store        = 0xB0315375FE070000
ext1         = 0xC0294E75FE070000
shmId        = 0     (0x00000000)
id           = 118   (0x76000000)
label        = 126753 (0x21EF0100)
fill         = 0     (0x00000000)
leng         = 176   (0xB0000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000132
occu         = 16    (0x10000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x60320F75FE070000
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 53553 (0x31D10000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x10000000)
lineAlloc    = 16    (0x10000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
collHook     = 0x0000000000000000
ext2         = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
%_DUMMY$$
2222
0000
0000
0000
<LS_SEL>
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME->DT_RFIELDNAME
Table IT_126975[2x60]
DATA=DT_RFIELDNAME |
| Table reference: 5220 |
| TABH+ 0(20) = 309A0C75FE070000000000000000000000000000 |
| TABH+ 20(20) = 64140000FFEF0100020000003C000000FFFFFFFF |
| TABH+ 40(16) = 04E80100300B0000100000002A278001 |
| store        = 0x309A0C75FE070000 |
| ext1         = 0x0000000000000000 |
| shmId        = 0     (0x00000000) |
| id           = 5220 (0x64140000) |
| label        = 126975 (0xFFEF0100) |
| fill         = 2     (0x02000000) |
| leng         = 60    (0x3C000000) |
| loop         = -1    (0xFFFFFFFF) |
| xtyp         = TYPE#000045 |
| occu         = 16    (0x10000000) |
| access       = 2     (ItAccessSorted) |
| idxKind      = 1     (ItIndexLinear) |
| uniKind      = 1     (ItUnique) |
| keyKind      = 2     (table_line) |
| cmpMode      = 3     (cmpSingleMcmpU) |
| occu0        = 1 |
| groupCntl    = 0 |
| rfc          = 0 |
| unShareable = 0 |
| mightBeShared = 0 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind       = 0 |
| isUsed       = 1 |
| isCtfyAble   = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi         = 0x6015FD74FE070000 |
| pgHook       = 0x0000000000000000 |
| idxPtr       = 0xA01BFD74FE070000 |
| shmTabhSet   = 0x0000000000000000 |
| id           = 53632 (0x80D10000) |
| refCount     = 0     (0x00000000) |
| tstRefCount = 0     (0x00000000) |
| lineAdmin    = 16    (0x10000000) |
| lineAlloc    = 16    (0x10000000) |
| shmVersId    = 0     (0x00000000) |
| shmRefCount = 1     (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook      = Not allocated |
| collHook     = Not allocated |
| ext2         = Not allocated |
| >>>>> 2nd level extension part <<<<< |
| tabhBack     = Not allocated |
| delta_head   = Not allocated |
| pb_func      = Not allocated |
| pb_handle    = Not allocated |
| <LS_SEL>-FIELDNAME |
| ??? |
| ?????? |
| ?????? |
| SY-SUBRC |
| 0 |
| 0000 |
| 0000 |
| LT_SEL |
| Table[initial] |
| LT_TRANSPORT |
| Table[initial] |
| LT_TRANSPORT_SEL |
| Table[initial] |
| %_SPACE |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| ME |
|
3000C000
70008C00
ME->DO_GUID_FIELD
|
| F0000000 |
| F0000000 |
| ME->DT_FDEP_INT |
| Table IT_126944[1x124] |
| DATA=DT_FDEP_INT
Table reference: 215
TABH+ 0(20) = B0753A2EFF07000090203775FE07000000000000
TABH+ 20(20) = D7000000E0EF0100010000007C000000FFFFFFFF
TABH+ 40(16) = 04B701005009000001000000A2078C01
store        = 0xB0753A2EFF070000
ext1         = 0x90203775FE070000
shmId        = 0     (0x00000000)
id           = 215   (0xD7000000)
label        = 126944 (0xE0EF0100)
fill         = 1     (0x01000000)
leng         = 124   (0x7C000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000035
occu         = 1     (0x01000000)
access       = 2     (ItAccessSorted)
idxKind      = 0     (ItIndexNone)
uniKind      = 1     (ItUnique)
keyKind      = 3     (user defined)
cmpMode      = 3     (cmpSingleMcmpU)
occu0        = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 1
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x10753A2EFF070000
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 27288 (0x986A0000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 1     (0x01000000)
lineAlloc    = 1     (0x01000000)
shmVersId    = 1380 (0x64050000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x0043E873FE070000
collHook     = 0x0000000000000000
ext2         = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
<LS_FDEP>
No.      10 Ty.          METHOD
Name CL_UC_MD_CHAR=>IF_UG_MD_MANUAL_TRANSPORT~TRANSPORT_BY_SEL
IT_SEL
Table[initial]
IF_COMPLETE
2
0
0
0
IF_USE_MASK
X
5
8
0
0
IF_TEXT_ONLY
2
0
0
0
ET_TRANSPORT
Table IT_111628[0x404]
ET_TRANSPORT_SEL
Table IT_126753[0x176]
%_SPACE
2
0
0
0
SY-REPID
CL_UC_MD_CHAR=================CP
4455454454445333333333333333334522222222
3CF53FD4F3812DDDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME
|
| 3000C000 |
| 70008C00 |
| SYST |
| ################################################ð#################################x#####XC#### |
| 000000000000000000000000000000000000002000000000F000000000000000000000000000109000700000540000 |
| 1010202000000000000020001000100000000080000000000000000000000000000000000000B00000800000830500 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000C |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| No.       9 Ty.          METHOD |
| Name CL_UG_MD_TR_CLIENTCOPY=>COLLECT_FIELDNAME_CONTENT |
| IO_MSG |
|
A0005000
F0000B00
CT_OBJECT
Table IT_43581[133x8]
FUNCTION=FINB_TR_CC_EXIT_ANALYZEDATA=LT_TMP_OBJECTS
Table reference: 3715
TABH+ 0(20) = 70438B74FE070000000000000000000000000000
TABH+ 20(20) = 830E00003DAA00008500000008000000FFFFFFFF
TABH+ 40(16) = 04720100D00400001B000000C1288001
store        = 0x70438B74FE070000
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 3715 (0x830E0000)
label        = 43581 (0x3DAA0000)
fill         = 133   (0x85000000)
leng         = 8     (0x08000000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000011
occu         = 27    (0x1B000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 4     (cmpSingleEq)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xA0548C74FE070000
pgHook       = 0x3066DB74FE070000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 24950 (0x76610000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 1105 (0x51040000)
lineAlloc    = 1105 (0x51040000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
SYST-REPID
CL_UG_MD_TR_CLIENTCOPY========CP
4455454455554444454455333333334522222222
3CF57FD4F42F3C95E43F09DDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LT_FATTR
Table IT_122877[1x294]
CLASS=CL_UG_MD_TR_CLIENTCOPYMETHOD=COLLECT_FIELDNAME_CONTENTDATA=LT_FATTR
Table reference: 4265
TABH+ 0(20) = F0151175FE070000000000000000000000000000
TABH+ 20(20) = A9100000FDDF01000100000026010000FFFFFFFF
TABH+ 40(16) = 04E80100200C00000A000000A4058401
store        = 0xF0151175FE070000
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id

"InfoProvider ZSEBCST02 has been changed in the meantime"
1. Lock all users.
2. Put all jobs on hold.
3. Make sure that your upstream system (R/3, etc.) are not pushing data into BI.
4. Cycle the BI system.
5. Retry.

Short dump while displaying infocube data

Similar Messages

Maybe you are looking for