Dump SAPSQL_ARRAY_INSERT_DUPREC when loading a hierarchy

Hi Guru's,
I have an error when i try to load a hiearchy on my BI system. I want to load the Cust_sales hierarchy but i ahev a short dump : SAPSQL_ARRAY_INSERT_DUPREC
Any idea ?
Cyril

hi...
it seems you have tried to insert data fro an internal table to database and in the mean it tried to insert duplicate entry ie records with same key fields.
way to solve it:::
way1.
*sort the internal table in use.
sort t_table.
Delete adjecent duplicates.
DELETE ADJACENT DUPLICATE ENTRIES FROM t_table
now proceed.
way2.
loop at the internal table and now go for insert....
if duplicte exist in that case it will set sy-subrc but will not give dump....
regards

Similar Messages

Dump ASSIGN_TYPE_CONFLICT when loading into Cube

Hi,
since an few weeks we have sometimes a problem when loading data from DSO to cube.
After transport a changed cube the first dataload into the cube dumps with ASSIGN_TYPE_CONFLICT.
We always activate all transformations and all DTPs which belong to the changed cube and also transport them.
When we repeat the dataload after the dump there is no problem and the data will be loaded successfully.
The dump appears on a very strange coding-place:
* FORM WRITE_DATA_CHAVL                                              *
* Kommentar: incoming data is based in characteritic values!        *
*              Transformation to Dimension Id's needs first to        *
*              translate the charateristic values into SID's          *
FORM write_data_chavl
USING
    i_r_data       TYPE REF TO data
    i_simulation   TYPE rs_bool
    i_trexaggr     TYPE rs_bool
    i_req_sid      TYPE rssid
    i_t_tabix      TYPE gt_t_tabix
    i_ncum_loadtp TYPE ncum_loadtype
    i_pkg_id       TYPE rssid
CHANGING
    c_subrc        TYPE i.
DATA:
    l_recno       LIKE sy-tabix,
    l_erridx      LIKE sy-tabix,
    l_nexterr     LIKE sy-tabix,
    l_errnumbers TYPE i,
    l_subrc1      LIKE sy-subrc,
    l_pdimid      TYPE rssid.
FIELD-SYMBOLS:
    <l_t_cubeval> TYPE g_t_cubecha,
    <l_s_cubecha> TYPE g_s_cubecha.
IF i_pkg_id <> 0.
*   bug, cube is not delta write enabled...
    cl_rsdd_cube_writer=>monitor_log(
      i_recno    = 0
      i_msgid    = 'DBMAN'
>>>      i_msgno    = '971'
      i_errtp    = ''
      i_errnm    = ''
      i_fieldnm = '' ).
    c_subrc = cl_rsdd_cube_writer=>nc_error-no_continue.
    RETURN.
ENDIF.
Does anyone else have this problem?
Or does anyone even have the solution?
I haven't found anything useful in SDN and SAP-Notes....
Christian

Hi Christian,
In that case check if this helps.....
1905680 - SP32: 'ASSIGN_TYPE_CONFLICT' in transformation during loading data using DTP
It says
SAP NetWeaver BW 7.31 (SAP NW BW 7.3 EnhP 1)
Import Support Package 10 for SAP NetWeaver BW 7.31 (SAPKW73110) into your BW system.
Regards

Mobile Application Crashes when loading Sales Hierarchy

Hi guys,
When I am trying to load the sales Hierarchy tile set in the Product component the system hangs out.
I checked for notes and founf out the note 630848.
But this note is valid for 3.0 SP17 .
We are using 4.0 sp07.
Any one has some clue for my issue

Fredrick,
I waited for the projects to get published.
I did ot make any chnages in the UI
This is the line which gives the error.
Private CMSAInbox As CMSAInbox
This is what I found after the trace observation
During the trace, after the following SQL command is run:
-- CATG_QRY
SELECT [SMOCATG].[MANDT] [MANDT], [SMOCATG].[SFACATG] [SFACATG], [SMOCATG].[CATGID] [CATGID], [SMOCATG].[SFAHIER] [SFAHIER], [SMOCATG].[SFAPARCATG] [SFAPARCATG], [SMOCATG].[NONASSIGN] [NONASSIGN], [SMOCATG].[LOGSYS]
[LOGSYS] FROM [SMOCATG] [SMOCATG] WHERE [SMOCATG].[DELETED] = '0'
AND SMOCATG.CATGID = 'HWANMPROBEFILMZZZZ'
OPTION (FAST 100)
The same SQL query keeps getting executed over and over again in an infinite loop until we kill the trace. The looping SQL query is:
-- CATGT
SELECT [CATGT].[SFACATGT] [SFACATGT], [CATGT].[SFACATG] [SFACATG], [CATGT].[CATTEXT] [CATTEXT], [CATG].[CATGID] [CATGID], [CATG].[SFAHIER] [SFAHIER], [CATG].[SFAPARCATG] [SFAPARCATG] FROM [SMOCATG] [CATG],[SMOCATGT]
[CATGT] WHERE [CATG].[DELETED] = '0' AND [CATGT].[DELETED] = '0' AND CATG.SFACATG*=CATGT.SFACATG
AND CATG.SFACATG = '2277A14AEF1EA64B89FD30E37FA2D8ED' AND CATG.SFAHIER = '' AND CATGT.MANDT = '000' AND CATGT.LANGU = 'EN'
Thanks for the patience

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

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?

Numbering nodes when loading hierarchy from a flat file.

Hi All,
I want to load a hierarchy from a flat file. When we number the nodes, do they have to be in a sequence or can I give them any number I want? I want to make the GL account number as the node number since it makes it easy to generate the node number that way. The way I see it, the important thing is the parent node number; so this approach should be fine. Please correct me if I am wrong.
Thanks,
Uday

Hi Uday,
   You need to have a running sequence numbers for Node Id field in the flat file. The file structure is as
NODEID IOBJNM      NODENAME TLEVEL LINK PARENTID
00000001 0GLACC     GL233344             00000001
00000002 0GLACC     GL435556             00000001
00000003 0GLACC     GL545666             00000001
00000004 0costcenter cc433232            00000002
00000005 0costcenter cc433233            00000002
00000006 0costcenter CC555551            00000003
The Parentid will calculated by the system automatically.
when you prepare you file csv please ensure that you have 8 characters for the Node ID " 00000003" other wise you will get error.
And if you want to add GL Account number to your hierarchy then you need to add GL A/c Number as external characteristics in hierarchy and add it to your flat file .
Hope it helps.
Cheers,
Balaji

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

Error when loading hierarchy through flat file

Dear All,
We are facing an issue during hierarchy upload through flat file.
Below is the message :-
Error 8 when compiling the upload program: row 658, message: A newer version of data type /BIC/B0000559000 was.
Message no. RSAR233.
Nothing else is being displayed.
Request you to guide on this.
Thanks & Regards,
Anup

Hi,
I faced the same issue earlier.
This is what i did. SE38-RS_TRANSTRU_ACTIVATE_ALL run the program and give your sourcesystem name this activates all the structure including new version /BIC structure what you have stated.
After which you need to refresh the RSA1 Tcode and do the same process again to load the hierarchy.
It should work fine now.
Hope this helps.
Regards,
Harish
Edited by: Harish3152 on May 18, 2010 2:23 PM
Edited by: Harish3152 on May 18, 2010 2:32 PM

Data Load Error: When loading Hierarchy through a flat file

Hi Bw experts,
I am getting the error message: Info object is not available: Message RSAR210, when trying to load the Hierarchy through flat file upload with IDOC processing.The info object is active. I am getting this error message only for one hierarchy, other hierarchies for the same inof object are loaded successfully.Can some one help me in this?
Thanks in Advance.
Regards,
Bala

Hi Bala,
Can you please share the solution asap..
As we are also facing the same issue.
Your quick response will be appreciated a lot
Regards,
Sai

Error "ERROR_PERIOD_VERSION" when loading DTP - Abap short dump

Hi,
I got this Error when loading with DTP. it occured in the transformation end routine.
I have this function module in my End routine. * REBW_FIRST_DAY_OF_PERIOD_GET*
Information on where terminated
    Termination occurred in the ABAP program "SAPLREBW_UTIL" - in
     "REBW_FIRST_DAY_OF_PERIOD_GET".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 41
    of the (Include) program "LREBW_UTILU03".
Source Code Extract
Line SourceCde
   11 *"     REFERENCE(E_SPERIOD) TYPE XFELD
   12 *" EXCEPTIONS
   13 *"      ERROR_PERIOD
   14 *"      ERROR_PERIOD_VERSION
   15 *"      FIRSTDAY_NOT_DEFINED
   16 *"      PERIOD_NOT_DEFINED
   17 *"----
   18 DATA:
   19     DATUM(8),
   20     TAG(2),
   21     IMONAT     TYPE I,
   22     JAHR       type rsfiscyear,
   23     DATE       type rscalday,
   24     PERZAHL(4) TYPE N,
   25     IRC(1)     TYPE N,
   26     ls_t009    like t009,
   27     ls_t009y   like t009y,
   28     ls_t009b   like t009b.
   29
   30 *
   31 * Version der Periodenermittlung nachlesen
   32 *
   33   IF I_FISCVAR NE ls_T009-PERIV.
   34     SELECT SINGLE * FROM T009
   35                     into ls_t009
   36                     WHERE PERIV = I_fiscvar.
   37     IF SY-SUBRC NE 0.
   38 *
   39 *     In Tabelle $ fehlt der Eintrag $
   40 *
>>>>>       RAISE ERROR_PERIOD_VERSION.
   42     ENDIF.
   43   ENDIF.
   44 *
   45 * Periode überprüfen
   46 *
   47   PERZAHL = ls_T009-ANZBP + ls_T009-ANZSP.
   48   IF I_FISCPER < 1 OR I_FISCPER > PERZAHL.
   49 *
does any knows how I can resolve it.
thanks

check table t009, it seems you have some entries missing (based on fiscal variant)
you can solve this, by going to the source system tree, right-click on your source system and choose transfer global settings.
you can transfer all settings now...
M.

Error in loading a Hierarchy

When we are loading a hierarchy in the BW system, we get the following error :
Error in the hierarchy structure: see error log.
We tried activation of the hierarchy data source then rerun the load. Still it fails with the same error.
Please let us knwo if any one has inputs regarding the same.

Please go through the following SAP Notes.
[Note 1266877 - BW hierarchy error when loading|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1266877]
[Note 384945 - BW: Incorrect hierarchy extraction for 0REOBJ|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=384945]
You will also find plent of threads with the same issue. Just search with the key words from the Error Log.
Regards,
Gaurav

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 SAPSQL_ARRAY_INSERT_DUPREC

Hi Experts,
I am getting a the short dump SAPSQL_ARRAY_INSERT_DUPREC after executing report SDRQCR21 at line 1258
INSERT VBBE FROM TABLE DA_XVBBE.
Please help.

Did you look for OSS notes for your version ?
33267
SDRQCR21 cancels with duplicate record
25444
SDRQCR21: Recovery of sales and delivery requirements
1023578
SDRQCR21 not fixing when wrong plant or material in VBBE
1562605
CALL_FUNCTION_REMOTE_ERROR SAPSQL_ARRAY_INSERT_DUPREC
Regards,
Raymond

Error while loading the Hierarchy from R/3 to BI.

Dear all ,
I am trying to load a hierarchy FROM R/3 to BI . When I am executing the Info package its showing an below Error.
Hierarchy object is u201CWBS elementu201D
The level of the node ID 01494179 does not suit the lev. of the higher lev. node
The level of the node ID 01494178 does not suit the lev. of the higher lev. node
The level of the node ID 01493822 does not suit the lev. of the higher lev. node
Could you please let me know what would be the reasonu2026u2026?
Regards,
Raghu

Hi
looks like there is some inconsistency in hierchy data you are tring to laod.
Check hierarchy in r3 if its ok, if yes try deleting complete hierarchy and reloading it.
You may also chose to adjust it manually
Regards
Sudeep

Error while loading the Hierarchy to 0GLACCEXT

Dear all ,
I am trying to load a hierarchy ZEM 1 that is manually created in R/3. when I am executing the Infopackage its showing an Error that
1.Record 8 :Node characteristic 0GL_ACCOUNT is not entered as hierarchy characteristic for 0GLACCEXT
2.Too many error records - update terminated
and what is the the concept of 0BAL_DPEND to be added as attribute to OGLACCEXT.
Thanks

Hi Dash ,
I am providing the long test for the error ...Also can you tell me how I should use 0BAL_DPEND field as an attribute of Hieararchy of 0GLACCEXT. Coz i am supposed to do this
<u>Hierarchy for Characteristic 0GLACCEXT with Attribute 0BAL_DEPEND
The hierarchy for characteristic 0GLACCEXT is used as the financial statement version in BW queries. To technically enable the particular exception aggregation for contra items, the hierarchy table of characteristic 0GLACCEXT contains the attribute Balance-Dependency of a Hierarchy Node (technical name 0BAL_DEPEND).</u>
The Long Error Message
Diagnosis
    The nodes NODEID = [00000194, 00001627 ] have the same node names
    NODENAME = '10000000950090 '. This is not allowed because neither node
    is a leaf and both nodes are assigned to the same characteristic
    0GL_ACCOUNT .
    Note that a maximum of 50 characters is available for message variables.
    The node name NODENAME = '10000000950090 ' might not be displayed in its
    full length.
System Response
Procedure
    Try to localize the problem. If the hierarchy is loaded from an SAP
    source system, you can check whether the extracted data is correct by
executing transaction RSA3 in the source system. If necessary, check if
the data is modified with a user exit. If the hierarchy is loaded from a
file, check the contents of this file. The problem might also be due to
an error in the transfer rules or in the transformation.
You can identify the two duplicate nodes from the values for the node ID
NODEID = [00000194, 00001627 ].
The problem can be caused by identical nodes delivered more than once
from the source. It is also possible that incorrect values for
parameters such as the node name NODENAME or validity period [DATEFROM,
DATETO] are the cause of the problem.
First check if the value for node name NODENAME = '10000000950090 ' is
correct. The node name consists of the characteristic value for the
hierarchy basic characteristic and the characteristic values of all the
characteristics compounded to this characteristic. Errors creating the
node name often result in duplicate nodes. This problem also occurs if
the node names of all nodes are initial.
If the structure of the hierarchy is defined as time-dependent, the time
validity of a node can be restricted with the fields DATEFROM and
DATETO. Duplicate nodes generally do not occur if the validity intervals
of two nodes do not overlap in time. In this case check if the fields
DATEFROM and DATETO are correctly filled.
In this case the duplicate nodes are not leaves. If you want to reuse an
existing subtree at another location in the hierarchy, you can refer to
this subtree with a link node. Possibly one of the two duplicate nodes
were incorrectly not marked as link nodes.
please Suggest What to do

Dump SAPSQL_ARRAY_INSERT_DUPREC when loading a hierarchy

Similar Messages

Maybe you are looking for