Short Dump when loading data (Runtime Error ITAB_DUPLICATE_KEY) Urgent Pls

Dear Guru
We are loading data into (2 ODS and ! Cube) from one Infopkg.
When i do delta update it throws following error
(for one ODS it is green) and for another ODS and CUBE it is red.
Runtime Error          ITAB_DUPLICATE_KEY
What happened?
Error in ABAP application program.
The current ABAP program "GP229LMXTFYDS5X6UC3ND03NIV2" had to be terminated
because one of the
statements could not be executed.
Please suggest me some solution, i am with client..its a serious issue now.
Hope you understand
Thanks in Adv
Dev

hi,
hope if you retrigger the load it would be successful.
force the request status to red and delete from the all target and retrigger the load.
else chk if in the detail tab u could find the data upto PSa. if so delete the red request alone and pull the records to tohose records from PSA.
Ramesh

Similar Messages

ABAP short dump when loading data into Infocube

Hello All,
I am getting an ABAP short dump error when loading data into Infocube. I tried to load data from PSA and ODS.
I ran the code to compress the Infocube, no improvement still getting the same error.
Error Analysis:
A raise statement in the program "SAPLRSDU_PART" raised in the exception.
Internal Notes:
The termination occured in the function "ab_i fune" of the SAP Basis system. Specifically in the line 2316 of the module "//bas/620/src/krn/runt/abfunc. C#18".
The internal operation just processed is "FUNE"
Advance thanks !!!
Siv

Hello Siv,
try to run program SAP_DROP_EMPTY_FPARTITIONS to display existing partitions. Then compare it to the number of uncompressed requests. Maybe there's a mismatch.
SAP notes that might help: 385163, 590370
Regards,
Marc
SAP NetWeaver RIG, US BI

Short Dump when loading Data into Cube UNCAUGHT_EXCEPTION(Pls Help)

Dear Guru's
i am trying to load data into a Cube from a ODS and the load gets dump...
In Dump Analysis.....
The exception 'ZCX_EDW_MAP_ROOT' was raised, but it was not caught anywhere
along
"UNCAUGHT_EXCEPTION" "ZCX_EDW_MAP_ROOT"
"ZCL_EDW_MAP_ROOT==============CP" or "ZCL_EDW_MAP_ROOT==============CM002"
"LOAD_MAPPING_INFOPROV"
So it would be great if some one can give me some suggestion to handle this issue
Thanks in Adv
Dev

Dear Arun,
i have checked the routine there exists some code
Eg: data: vref_monitor type ref to zcl_edw_monitor,
But to say fact i ddnot i understood it....
Any suggestions dude...pls
thanks in adv
Dev

GETWA_NOT_ASSIGNED short dump when load business partner master data

Hi
I've this error GETWA_NOT_ASSIGNED short dump when load business partner master data, it's running in BI 7.0 with support package 12.
The error is because the field symbol is that pointed to the line of an internal table that was deleted.
I think that it's an incompatibility between subroutine and unicode.
Do you have idea about correct this error?
Regards
Jose.

Hi Ravi
Yes, it's a dump
It's when running a process chain to load Business partner master data
The error say:
-.You address a field symbol that pointed to the line of an internal table that was deleted.
-.You address a field symbol that was previously reset using UNASSIGN or that pointed to a local field that no longer exist.
-. You address a global function interface, although the respective function module is not active - that is, is not in the list of active calls. the list of active calls can be taken from this short dump.
I think that it's for the unicode corversion because I've the last support package 12 installed and the rest of the process chain are running perfect.
My hotmail mail is [email protected] if you need the screen shot.
Regards and thanks a lot
Jose

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 loading data in ODS

Hi,
When i scheduled data load for ODS, a short dump was generated with following error:
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"RULE_BASED_MODIFY_RSMONMESS" "(FORM)"
How to correct the error
The exception must either be prevented, caught within the procedure
"RULE_BASED_MODIFY_RSMONMESS"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-01654: unable to extend index
SAPBD2.RSMONMESS~AXY by 128 in tablespace PSAPBD2"
Internal call code.........: "[RSQL/INSR/RSMONMESS ]"
Please check the entries in the system log (Transaction SM21).
Please suggest what needs to be done.

Hi Sneh,
This is table space issue.
You need to contact basis guys to get it resolved.
Take a screen shot of this error and send the information to basis guys.
Once they clear the problem. repeat the step.
Hope this helps,
Sri.....

Regarding short dump while loading data

Hi All,
I am loading data using 0FI_GL_4. This is a periodic load which was working fine till March. There are lot of postings that happened in April and period was open till 20th. Now when I am trying to load that for 12th period April. I am getting the following error "ABAP/4 processor: DBIF_RSQL_SQL_ERROR" in short dump.
This is the error analysis:
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"BWFIR_READ_BSEG_CPUDT_DATA" "(FUNCTION)"
I am tried to load data 5 times till now and every time I am getting the same error. I checked with Basis people for the DB space and it is fine.
Why I am suddenly getting this error???

Hi,
it looks like an internal table overflow in your source system.
Try reducing the data_package size of your load or ask your basis guys to have a look on short dump and perhaps increase this memory.
Try RSA3 in the source system and see if it works with your data_package size values from BW and see if it works. If not reduce the number of records...
On which plugin release is your system running?
hope this helps,
Oliviier.

Short dump while loading data

Hi All,
I am getting this error message while loading data in BW. The eeror message is below:
Data not received in PSA Table.
Diagnosis
Data has not been updated in PSA Table . The request is probably still running or there was a short dump.
Procedure
In the short dump overview in BW, look for the short dump that belongs to your data request. Make sure the correct date and time are specified in the selection screen.
You can use the wizard to get to the short dump list, or follow the menu path "Environment -> Short dump -> In Data Warehouse".
Removing errors
Follow the instructions in the short dump.
When I checked the short dump it is as below.
ShrtText
An SQL error occurred when accessing a table.
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer termination messages, especially those beyond their normal deletion date.
How to correct the error
    Database error text........: "ORA-14400: inserted partition key does not map to any partition"
    Internal call code.........: "[RSQL/INSR//BIC/B0000541000 ]"
    Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem in the SAP note system. If you have access to the note system yourself, use the following search criteria:
How to correct the error
    Database error text........: "ORA-14400: inserted partition key does not map to any partition"
    Internal call code.........: "[RSQL/INSR//BIC/B0000541000 ]"
    Please check the entries in the system log (Transaction SM21).
    You may able to find an interim solution to the problem in the SAP note system. If you have access to the note system yourself, use the following search
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
    "GP12DW003276UZE34XM7O2QXLER" or "GP12DW003276UZE34XM7O2QXLER"
    "INSERT_ODS"
Can someone suggest me what should I check?
Thanks in advance.

Thanks a lot Manga. I did what you told and it gave me this error message.
Inconsistency: High value for table /BIC/B0000541000: 0002 ; PARTNO value in RSTSODS: 0022
So you mean to say once I click on correct error button, it should be good. So after that if do the loading, it should not give me this problem if I am right.
But can you tell me what exactly does that error message mean? Also is this not an table space issue. I have to wait to correct that error as DBA is currently looking into it.
Assigned points. Will assign more points if the issue resolves.

Business Graphic working but short dumping when 'No Data' is available

Dear Experts,
I am trying to plot a graph (Bar chart) and it is working very well except when these is no data. In that instance instead of not displaying a data, it is giving short dump.
I am trying to plot a graph for a project from a list of the projects. In the Context, List of projects is a parent node while the cost data (used for drawing graph) is on child node. Both are with the cardinality of 0..n
When the project has cost data, graph is working beautifully but when the project does not have a cost data i get short dump.
Here is the what I get in Internet explorer.
The following error text was processed in the system UPG : Access via 'NULL' object reference not possible.
The error occurred on the application server SAPSANDPIT_UPG_00 and in the work process 2 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/CBUSINESS_GRAPHICS======CP
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C7STANDARD==============CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program CL_WDR_VIEW_ADAPTER===========CP
Method: IF_WDR_NW7_DELTA_RENDERER~CALCULATE_DELTA_BLOCKS of program CL_WDR_VIEW_ADAPTER===========CP
Method: IF_WDR_NW7_DELTA_RENDERER~CALCULATE_DELTA_BLOCKS of program CL_WDR_WINDOW_CONTENT_ADAPTER=CP
Method: SET_CONTENT of program CL_WDR_NW7_INT_WIN_ADAPTER====CP
Method: SET_CONTENT of program CL_WDR_NW7_MAIN_WIN_ADAPTER===CP
Method: IF_WDR_CLIENT~SEND_RESPONSE of program CL_WDR_CLIENT_SSR_LS==========CP
And here is what is in ST22
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
Exception              CX_SY_REF_IS_INITIAL
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
     caught in
    procedure "IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT" "(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:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component.
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
Problem is at following point
                                                                                mv_CHARTDATA = mv_DATA->create_simple_element( name = 'ChartData' parent = mv_DATA ). "#
*   >> END_UCA BUSINESS_GRAPHICS|BUSINESS_GRAPHICS|CHARTDATA
*   >> Property: Get BUSINESS_GRAPHICS-SERIES_SOURCE
    mv_SERIES_SOURCE = get_bound_node( i_binding = wd_BUSINESS_GRAPHICS->bp_SERIES_SOURCE )
                                                                                *   >> Property: UCA BUSINESS_GRAPHICS-SERIES_ELEMENTS
*   >> UCA BUSINESS_GRAPHICS|BUSINESS_GRAPHICS|SERIES_ELEMENTS
mv_SERIES_ELEMENTS = mv_SERIES_SOURCE->get_elements( ).
*   >> END_UCA BUSINESS_GRAPHICS|BUSINESS_GRAPHICS|SERIES_ELEMENTS
*   >> Property: UCA BUSINESS_GRAPHICS-SERIES_SOURCE_PATH
*   >> UCA BUSINESS_GRAPHICS|BUSINESS_GRAPHICS|SERIES_SOURCE_PATH
mv_SERIES_SOURCE IN in above code is initial when data does not exists for a project.
Thanks in advance for your help.
ABAPer

Forgot to add following info from ST22
Information on where terminated
    Termination occurred in the ABAP program "/1WDA/CBUSINESS_GRAPHICS======CP" -
     in "IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT".
    The main program was "SAPMHTTP ".
In the source code you have the termination point in line 753
    of the (Include) program "/1WDA/CBUSINESS_GRAPHICS======CCIMP".
    The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
    procedure "IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT" "(METHOD)", but it was
     neither handled locally nor declared
    in the RAISING clause of its signature.
The procedure is in program "/1WDA/CBUSINESS_GRAPHICS======CP "; its source
     code begins in line
    390 of the (Include program "/1WDA/CBUSINESS_GRAPHICS======CCIMP ".
Thanks
ABAPer

While loading data Runtime error MOVE_TO_LIT_NOTALLOWED_NODATA

Dear Masters
While loading data from r/3 to PSA only, I am getting below error
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
There is no long text, when I clicked Error message, I got below message only
 Job terminated in source system > Request set to red
In r/3 side in st22, I got below runtime errors
Runtime Errors MOVE_TO_LIT_NOTALLOWED_NODATA
Short text
 Error at assignment: Overwritten protected field.
any other sap notes to fix this issue
Please help me to resolve below issue
Thanks in advance
Raja S

Hi Raja,
Your error message suggests that there is some overlapping of the filed while you have done the mapping and at the time of extraction this particular field is being tried to be overwritten by some other mapping which is not possible.
Check in your mappings again and load it.
Cheers!
Amit

2LIS_06_INV - Dump when loading data

Hi all!
I'm having a problem when I try to load data with IS 2LIS_06_INV. The infopackage starts in background but it seems to be very slow. Suddently the error appears:
Short dump in the Warehouse
Diagnosis
The data update was not finished. A short dump has probably been logged in BI. This provides information about the error.
System Response
"Caller 70" is missing.
Is there any error with SAP standard extrator?
Does anyone face with this problem yet?
Regards,
Thiago

This error is thrown when the processing time for extraction is too long. In this case, it most likely was caused because of large data volumes. This can also occur if there are multiple, concurrent background jobs running on the source system.
The two most common resolutions are:
1) Wait for more background processes to free up on the source system and re-start the InfoPackage.
2) Reduce the package sizes for the extraction.

Dump when loading Data from DSO to Cube

Hi,
i get a short dump DBIF_REPO_PART_NOT_FOUND when trying to load data from a dso to a cube. From DSO to DSO it works fine.
any idea`s?
thx!
Dominik

the Dump occurs in the last step of the last data pakage in the DTP Monitor.
I checked the OSS note, but i don´t know how to check the kernel version.
Now i used another DSO for testing and i got another Dump with a different name.
After that i logged in again and it works with my test DSO data...
But still not working with the original one...
@Kazmi: What detaisl u mean exactly?

Short dump while loading data in to Bw using Process Chain.

got the problem in the Production System.......... I won't get any confirmation from my customer to debug the program in the Poduction.
In BW I have to load the data every day using the process chain. in the monitor I can't find any problem every thing is working fine. status is green.. and loads the data into ODS successfully. But the job runs more than 6 Hrs and automatically an E-mail is sent to us that the processing takes long time.But it loads the data successfully into ODS.
Since 10 days everyday we got a mail with the same problem. My customer asked me tTo analyse the problem.
I check the short dump there I found that due to some problem the program get intrupted.
the short dump
""Lokale Schnittstelle:
*" IMPORTING
*" VALUE(I_INFOCUBE) TYPE RSINFOCUBE
*" EXCEPTIONS
*" ILLEGAL_INPUT
*" REQUEST_NOT_CLOSED
*" INHERITED_ERROR
DATA: l_s_cube TYPE rsd_s_cube,
l_t_dummy TYPE rsdri_t_rfcdata,
l_s_rsapoadm TYPE rsapoadm,
l_nothing_found TYPE rs_bool.
get type of cube
CALL FUNCTION 'RSD_CUBE_GET_ONLY_DB'
EXPORTING
i_infocube = i_infocube
i_objvers = rs_c_objvers-active
i_with_atr_nav = rs_c_false
i_with_message = rs_c_false
IMPORTING
e_s_cube = l_s_cube
EXCEPTIONS
infocube_not_found = 1
illegal_input = 2
OTHERS = 3.
CASE sy-subrc.
WHEN 0.
WHEN 1.
RAISE illegal_input
WHEN OTHERS.
RAISE inherited_error.
ENDCASE.
In the short dump I observed that the porgram get intrupted at RAISE illegal_input when sy-subrc = 1.
I have to analyse this. problem........ whay is so happened...............
Any one of you face the same problem............... if so please let me give your valuble suggestions regarding this.
Cheers
sailekha

Looks like it reaches the water mark level thats why you are getting message.

Short Dump while loading data into the GL ODS

Hello Guyz
I am getting a database error while loading the GL ODS in BW. I am performing an INIT load, and the error occurs during the activation stage:
Database Error

Hello Atul,
PSAPTEMP has nothing to do with PSA. It is a temporary storage space and is present in all systems.
You can check this in transaction DB02 if you are using Bw 3.x and DB02OLD if you are using BI 7.0. Once in DB02/DB02OLD, you will see a block which says tablespaces. In this block, there is a push button for freespace statistics, click on it and it will take you to a screen which shows the free space for all tablespaces.
Hope this helps,
Regards.

Errors when loading data to ODS

Hi,
I am getting the following dump when loading data to ODS
whta might be the problem
Runtime Error MESSAGE_TYPE_X
Date and Time 29.09.2006 14:26:52
ShrtText
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.
is especially useful if you want to keep a particular message.
Error analysis
Short text of error message:
Test message: SDOK_GET_PHIO_ACCESS 001
Technical information about the message:
Message classe...... "1R"
Number.............. 000
Variable 1.......... "SDOK_GET_PHIO_ACCESS"
Variable 2.......... 001
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
"SAPLSDCL" or "LSDCLF00"
"INTERNAL_ERROR"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "bomw093a"
Network address.......... "132.186.125.66"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 16
Short dump setting....... "full"
Database server.......... "BOMW093A"
Database type............ "ORACLE"
Database name............ "BIW"
Database owner........... "SAPDAT"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Nov 4 2004 23:26:03"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "43"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory usage.............
Roll..................... 8112
EM....................... 6271776
Heap..................... 0
Page..................... 24576
MM Used.................. 3921120
MM Free.................. 258392
SAP Release.............. "640"
User and Transaction
Client.............. 800
User................ "IC881147"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSDCL"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLSDCL" in "INTERNAL_ERROR".
The main program was "RSRD_BROADCAST_PROCESSOR ".
The termination occurred in line 25 of the source code of the (Include)
program "LSDCLF00"
of the source code of program "LSDCLF00" (when calling the editor 250).
The program "SAPLSDCL" was started as a background job.
Job name........ "SECOQUERY"
Job initiator... "IC881147"
Job number...... 14265102
Source Code Extract
Line
SourceCde
1
2
INCLUDE LSDCLF00 *
3
4
5
6
 FORM INTERNAL_ERROR *
7
8
 Handles unexpected error conditions (internal errors)
9
10
--> VALUE(U_ROUTINE) Routine/function module where error occured
11
--> VALUE(U_ERROR_CODE) Identifier in routine (e.g. number)
12
--> VALUE(U_VAR1) Variable containing further information
13
--> VALUE(U_VAR2) Variable containing further information
14
--> VALUE(U_VAR3) Variable containing further information
15
--> VALUE(U_VAR4) Variable containing further information
16
17
form internal_error
18
using value(u_routine)
19
value(u_error_code)
20
value(u_var1)
21
value(u_var2)
22
value(u_var3)
23
value(u_var4).
24
>>>>>
message x000 with u_routine u_error_code u_var1 u_var2.
26
27
endform.
28
29
30
*& Form BAD_OBJECT_TO_SYMSG
31
32
 maps error information in u_bad_object into system message
33
 variables
34
35
--> VALUE(U_BAD_OBJECT) structure containing error information
36
37
form bad_object_to_symsg
38
using value(u_bad_object) type sdokerrmsg.
39
40
sy-msgid = u_bad_object-id.
41
sy-msgty = u_bad_object-type.
42
sy-msgno = u_bad_object-no.
43
sy-msgv1 = u_bad_object-v1.
44
sy-msgv2 = u_bad_object-v2.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
4
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Report Dissemaintion Framework: Executing the Transferred Settings
SY-MSGTY
X
SY-MSGID
1R
SY-MSGNO
000
SY-MSGV1
SDOK_GET_PHIO_ACCESS
SY-MSGV2
001
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
15 FORM SAPLSDCL LSDCLF00 25
INTERNAL_ERROR
14 FORM SAPLSDCI LSDCIU13 303
PHIO_GET_CONTENT_ACCESS
13 FUNCTION SAPLSDCI LSDCIU13 113
SDOK_PHIO_GET_CONTENT_ACCESS
12 FUNCTION SAPLSKWF_CONTENT LSKWF_CONTENTU02 63
SKWF_PHIO_CONTENT_ACCESS_GET
11 METHOD CL_RSRA_KWF_UTILITIES=========CP CL_RSRA_KWF_UTILITIES=========CM00B 50
CL_RSRA_KWF_UTILITIES=>COPY_MIME_TO_FOLDER
10 METHOD CL_RSRA_KWF_TMPL==============CP CL_RSRA_KWF_TMPL==============CM002 28
CL_RSRA_KWF_TMPL=>GET_STYLESHEET
9 METHOD CL_RSRA_KWF_TMPL==============CP CL_RSRA_KWF_TMPL==============CM001 227
CL_RSRA_KWF_TMPL=>CONSTRUCTOR
8 METHOD CL_RSRA_ENGINE_BC=============CP CL_RSRA_ENGINE_BC=============CM010 9
CL_RSRA_ENGINE_BC=>SET_TEMPLATE_FOLDER
7 METHOD CL_RSRA_ENGINE_BC=============CP CL_RSRA_ENGINE_BC=============CM001 75
CL_RSRA_ENGINE_BC=>CONSTRUCTOR
6 METHOD CL_RSRA_JOB===================CP CL_RSRA_JOB===================CM003 47
CL_RSRA_JOB=>EXECUTE_SINGLE
5 METHOD CL_RSRA_JOB===================CP CL_RSRA_JOB===================CM00E 14
CL_RSRA_JOB=>EXECUTE_SINGLE_RC
4 METHOD CL_RSRD_PRODUCER_RA===========CP CL_RSRD_PRODUCER_RA===========CM001 147
CL_RSRD_PRODUCER_RA=>IF_RSRD_F_PRODUCER_RT~PRODUCE
3 METHOD CL_RSRD_SETTING===============CP CL_RSRD_SETTING===============CM005 28
CL_RSRD_SETTING=>EXECUTE_NODES
2 METHOD CL_RSRD_SETTING===============CP CL_RSRD_SETTING===============CM002 73
CL_RSRD_SETTING=>EXECUTE
1 EVENT RSRD_BROADCAST_PROCESSOR RSRD_BROADCAST_PROCESSOR 197
START-OF-SELECTION
Chosen variables
Name
Val.
No. 15 Ty. FORM
Name INTERNAL_ERROR
U_ROUTINE
SDOK_GET_PHIO_ACCESS
54445445554445444455
34FBF754F089FF133533
SY-MSGV1
SDOK_GET_PHIO_ACCESS
54445445554445444455222222222222222222222222222222
34FBF754F089FF133533000000000000000000000000000000
U_ERROR_CODE
001
333
001
SY-MSGV2
001
33322222222222222222222222222222222222222222222222
00100000000000000000000000000000000000000000000000
U_VAR1
2
0
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SDOKI_MODE_DELETE
5
0000
5000
U_VAR2
2
0
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
No. 14 Ty. FORM
Name PHIO_GET_CONTENT_ACCESS
SYST
####################################################A#######P###############è#################
0000000000000000000000000000000000000000000000000000400000005000000000000000E00000000000000000
0000000010002000000000000000000000000000400000001000100010000000000000000000840000000000000000
PHIO_OBJECT_ID-CLASS
2222222222
0000000000
DUMMY_VERSTYPE
0
3
0
DUMMY_FCT_EXPORT
222222222222222222222222222222
000000000000000000000000000000
DUMMY_FCT_IMPORT
222222222222222222222222222222
000000000000000000000000000000
DUMMY_FCT_DELETE
222222222222222222222222222222
000000000000000000000000000000
FCT_VIEW
222222222222222222222222222222
000000000000000000000000000000
BUFF_XPIRE
000000000000
333333333333
000000000000
NO_BUFFER
2
0
SUBRC_AUX
3
0000
3000
SDOKA_EVENT_PH_FROM_REL_PRE
0022
3333
0022
SCREEN
%_17SNS0001592815_%_%_%_%_%_%_
2533545333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
5F173E30001592815F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
<%_TABLE_SDOKSTRE>
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
CONTEXT[]
Table IT_5544[0x89]
FUNCTION=SKWF_PHIO_CONTENT_ACCESS_GETDATA=CONTEXT[]
Table reference: 324
TABH+ 0(20) = 00000000801CE03C0000000044010000A8150000
TABH+ 20(20) = 0000000059000000FFFFFFFF047B0200D00E0000
TABH+ 40( 8) = 10000000C1248000
store = 0x00000000
ext1 = 0x801CE03C
shmId = 0 (0x00000000)
id = 324 (0x44010000)
label = 5544 (0xA8150000)
fill = 0 (0x00000000)
leng = 89 (0x59000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000058
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
hsdir = 0x00000000
ext2 = 0x381CE03C
>>>>> 2nd level extension part <<<<<
tabhBack = 0x98DC033D
delta_head = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
CONTEXT
22222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PROPERTIES[]
Table[initial]
PROPERTIES
22222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 13 Ty. FUNCTION
Name SDOK_PHIO_GET_CONTENT_ACCESS
ALLOW_MODEL
2
0
CACHE_SERVER
0000000000
2222222222222222222222222222222222222222222222222222222222222222333333333322222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
CLIENT
800
333
800
CONTENT_ONLY
X
5
8
CONTENT_OR_URL_ONLY
2
0
OBJECT_ID
222222222222222222222222222222222222222222
000000000000000000000000000000000000000000
RAW_MODE
2
0
TEXT_AS_STREAM
X
5
8
USE_URL_AT
2
0
ACCESS_MODE
00
33
00
DOCUMENT_HTTPS_URL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
DOCUMENT_URL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
MODEL_RETURNED
2
0
COMPONENTS[]
Table[initial]
COMPONENT_ACCESS[]
Table IT_5533[0x8616]
CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_COMPONENT_ACCESS
Table reference: 337
TABH+ 0(20) = 00000000481BE03C00000000510100009D150000
TABH+ 20(20) = 00000000A8210000FFFFFFFF04C5010088190000
TABH+ 40( 8) = 01000000C1248000
store = 0x00000000
ext1 = 0x481BE03C
shmId = 0 (0x00000000)
id = 337 (0x51010000)
label = 5533 (0x9D150000)
fill = 0 (0x00000000)
leng = 8616 (0xA8210000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000107
occu = 1 (0x01000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
hsdir = 0x00000000
ext2 = 0x001BE03C
>>>>> 2nd level extension part <<<<<
tabhBack = 0x985D043D
delta_head = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
CONTEXT[]
Table IT_5544[0x89]
FILE_CONTENT_ASCII[]
Table IT_5534[0x1022]
CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_FILE_CONTENT_ASCII
Table reference: 312
TABH+ 0(20) = 00000000B01BE03C00000000380100009E150000
TABH+ 20(20) = 00000000FE030000FFFFFFFF04C50100D81A0000
TABH+ 40( 8) = 10000000C1248000
store = 0x00000000
ext1 = 0xB01BE03C
shmId = 0 (0x00000000)
id = 312 (0x38010000)
label = 5534 (0x9E150000)
fill = 0 (0x00000000)
leng = 1022 (0xFE030000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000113
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
hsdir = 0x00000000
ext2 = 0x681BE03C
>>>>> 2nd level extension part <<<<<
tabhBack = 0xB813043D
delta_head = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
FILE_CONTENT_BINARY[]
Table IT_5535[0x1022]
CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_FILE_CONTENT_BINARY
Table reference: 325
TABH+ 0(20) = 00000000181CE03C00000000450100009F150000
TABH+ 20(20) = 00000000FE030000FFFFFFFF04C50100101B0000
TABH+ 40( 8) = 10000000C1248000
store = 0x00000000
ext1 = 0x181CE03C
shmId = 0 (0x00000000)
id = 325 (0x45010000)
label = 5535 (0x9F150000)
fill = 0 (0x00000000)
leng = 1022 (0xFE030000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000114
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
hsdir = 0x00000000
ext2 = 0xD01BE03C
>>>>> 2nd level extension part <<<<<
tabhBack = 0xC08FD33C
delta_head = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
PROPERTIES[]
Table[initial]
COMPONENT_ACCESS
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
FILE_CONTENT_ASCII
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
FILE_CONTENT_BINARY
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OBJECT_ID_AUX
222222222222222222222222222222222222222222
000000000000000000000000000000000000000000
X_DOCUMENT_URL
X
5
8
X_DOCUMENT_HTTPS_URL
X
5
8
X_COMPONENT_ACCESS
X
5
8
SUBRC_AUX
0
0000
0000
%_DUMMY$$
2222
0000
%_SPACE
2
0
SY-REPID
SAPLSDCI
5454544422222222222222222222222222222222
310C343900000000000000000000000000000000
No. 12 Ty. FUNCTION
Name SKWF_PHIO_CONTENT_ACCESS_GET
CACHE_SERVER
0000000000
2222222222222222222222222222222222222222222222222222222222222222333333333322222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PHIO
2222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000
USE_URL_AT
2
0
X_ALLOW_MODEL
2
0
X_CONTENT_ONLY
X
5
8
X_CONTENT_OR_URL_ONLY
2
0
X_RAW_MODE
2
0
X_TEXT_AS_STREAM
X
5
8
ACCESS_MODE
00
33
00
DOCUMENT_HTTPS_URL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
DOCUMENT_URL
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ERROR
000
2222222222222222222223332222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
X_MODEL_RETURNED
2
0
COMPONENT_ACCESS[]
Table IT_5533[0x8616]
CONTEXT[]
Table IT_5544[0x89]
FILE_CONTENT_ASCII[]
Table IT_5534[0x1022]
FILE_CONTENT_BINARY[]
Table IT_5535[0x1022]
PROPERTIES[]
Table[initial]
SKWFA_C_ACT_READ
03
33
03
SYST-REPID
SAPLSKWF_CONTENT
5454545454445445222222222222222222222222
310C3B76F3FE45E4000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PHIO+1(42)
222222222222222222222222222222222222222222
000000000000000000000000000000000000000000
CL_ABAP_TABLEDESCR=>TABLEKIND_STD
S
5
3
SKWFC_YES
X
5
8
No. 11 Ty. METHOD
Name CL_RSRA_KWF_UTILITIES=>COPY_MIME_TO_FOLDER
I_S_MIME_IO
FM_FOLDER 3AA00E1E0D0E3DCBE10000000A1144B5
4454444452234433434343434444333333334333343
6DF6FC4520031100515040534325100000001114425
I_S_FOLDER_IO
FBW_FLD 08BSWBLVV6N1IJCIG3VHEX2H8
4455444222233455445534344444354453432222222
627F6C40000082372C666E19A397368582880000000
L_T_PROPERTY_REQUEST
Table IT_5512[1x25]
CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_PROPERTY_REQUEST
Table reference: 316
TABH+ 0(20) = 28D5D23C68D5D23C000000003C01000088150000
TABH+ 20(20) = 0100000019000000FFFFFFFF04C5010038110000
TABH+ 40( 8) = 10000000C1248400
store = 0x28D5D23C
ext1 = 0x68D5D23C
shmId = 0 (0x00000000)
id = 316 (0x3C010000)
label = 5512 (0x88150000)
fill = 1 (0x01000000)
leng = 25 (0x19000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000069
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xC00BE03C
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 3644 (0x3C0E0000)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
hsdir = 0x00000000
ext2 = 0x600DE03C
>>>>> 2nd level extension part <<<<<
tabhBack = 0x98D5033D
delta_head = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
L_S_PROPERTY_REQUEST
KW_RELATIVE_URL
4555444545455542222222222
B7F25C14965F52C0000000000
L_T_PHIO
Table IT_5494[1x43]
CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_PHIO
Table reference: 309
TABH+ 0(20) = E8D4D23CE0D3D23C000000003501000076150000
TABH+ 20(20) = 010000002B000000FFFFFFFF04C5010018120000
TABH+ 40( 8) = 10000000C1248000
store = 0xE8D4D23C
ext1 = 0xE0D3D23C
shmId = 0 (0x00000000)
id = 309 (0x35010000)
label = 5494 (0x76150000)
fill = 1 (0x01000000)
leng = 43 (0x2B000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000073
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x2010E03C
pghook = 0x00000000
idxPtr = 0x00000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
store_id = 3643 (0x3B0E0000)
shmIsReadOnly = 0 (0x00000000)

Hi priya,
Not sure: check syntax in your Update Roules, also at level of start routine.
Ciao.
Riccardo.

Short Dump when loading data (Runtime Error ITAB_DUPLICATE_KEY) Urgent Pls

Similar Messages

Maybe you are looking for