Load error in ODS

Hi all,
We are doing unit testing.For this i am trying to load the data psa then into ODS.There are three info packages we have created for full,init and delata.One week back we have loaded the data using delta and it was successful.
Now to day i am trying to load the data using it is giving 0 records.
When i am trying to load the data using full it is giving the following error
(Full 2.146 has overlapping selections with init. 0000002056 : No updates into ODS ZXXX )
Please help me out to find the solution for this.
Thanks to all

Hi,
You have to amke your FULL infopackage...as.."Repair full request".
Go to that full infopackage-in menu-Schedule-> Repair full request.
Save.
check out this...
ODS Object switch from Delta to Full Upload
Hope i m clear.
Regards,
San!
Message was edited by: San!

Similar Messages

Date load error From ODS to Cube?

Guru's,
Here is a status of data load and suggest me.
Actually we are loading data from ODS to Cube which is full load.This loading is done thorugh process chain and it is loaded for every half an hour.Every time the earlier load will be deleted and next load will be taken to cube.Two days ago the load had gone wrong.When I tried to see cause for the failure in Monitor details I could see Update missing and processing missing.When I see in process chains log view I got info stating some invalid characterstic had appeared.But when I search in PSA the whole of the data packets are green.If there is any invalid characterstics PSA should show a red status.But it is not showing.Please guide me how could I solve this?
point will be definitely awarded for the proper answers.
Thanks in advance.
vasu.

Hi Vasuvasu
Once the edit is done and reloade the sata it wont show u the records in Red..
Hope itz Helps..!
Regards
KISHORE M REDDY
**Winners Don't Do Different things,They Do things Differently...!**
> I dont whink this is with Disk space Y because after
> every full load we are deleting data.

Flat File Load error on ODS

Hi Guru's,
I am loading a Multiple Flat files to ODS in 3.5.
first i loaded a flat file with the following.
Calweek , SS, Mat, Cust   Item ,Commentof Item
11/2004 , MD, 101, YU23   pen,   good
after loading this i am able to these data on ODS
second file am loading file with
Calweek , SS, Mat, Cust Price , commentofprice.
11/2004 , MD, 101, YU23   2.00, average.
when i checked the data on ODS i am able to see only second
file data . with selection conditions 11/2004 , MD, 101, YU23
I can use Cube for loding this but my design is on ODS.
i want to see all the data on ODS, can anyone give me idea how to write any routine for this
Regards
Rao VS

Hi Yogesh & Shambhu,
Thanks for your support. and what i did currently is
i kept the keyfields as same and changed the ITEM,PRICE as ADDITION in the update rule.
But for commentonitem, CommentonPrice there fields are Char.
so i cann't find Addition option to this.
By doing this :
1) when i loaded 1st file i am able to see the original file.
and
2) when i loaded second file i am able to see the second file values also.
But the issue is after loading two files i am able to see on the ods as
Calweek,SS,Mat,Cust, Item,Price,CommtofItem, Commprice.
11/2004 , MD, 101, YU23 pen,2.00,    -               ,average
I am not able to see Commentof Item Value and can see only the last loaded Comments filed.
If i loaded second file first and then first file secondly then i can see only Comment of Item .
So can you pls help in written routine for these fileds in update rule (commentson item,commentson price)
Thanks & Regards
Rao VS

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.

Error while loading data to ODS in BI7

Getting such following errors when loading data to ODS through DTP(Data Transfer Process) in BI7.
Runtime error while executing rule -> see long text RSTRAN
Record filtered because records with the same key contain errors     RSM2
and many so on...
source system is ok no problem with the connection part.
plz help.

Hi Anup.
Probably your records are not Unique, while you have told the system they should be.
Try to move a discrimination characteristic from data fileds to key fileds.
Or
Try to set the "duplicate reords allowed" setting in your datasource (tab "General Settings" Delivery of Duplicate Data Recs. = Allowed)
Udo

Error while loading data to ODS

Hello BW folks ,
I am getting an error while loading data to ODS from R/3 data source.
The error message is " Error in PSA".
We have deleted yesterday data from PSA for the related infosource/data source successfully .
Since then this error is occuring. Previously data upload was successful.
In Detail tab of monitor we are getting error message in Request option ( red Mark )
and the same request is not going to R/3 .
The related Job itself is not present in R/3 .
This looks very strange and new to me .
Could anyone help me in rectifying this issue ?
Thanks in Advance.
Best Regards ,
Amol.

Hello All,
Thanks for reply.
I tried to replicate the data source once again and activate the transfer rules in BW Production by running program in SE38 = RS_TRANS* activate all tranfer sturctures , then I got an error message that one infoobject is added to transfer rules in BW Production .
But interestingly the same Transfer rules do not have this infoobject in BW Development server . So I create once again a request for Transfer rules in Dev and transported it to BW production.
and This solved the problem
The error message in Monitor was " Error in PSA " and then request itself was not going to R/3 . But the real issue was with Transfer rules. So after rectifying it we have solved the problem of data upload.
Best Regards ,
Amol Kulkarni.

"Error While loading data from ODS to Target "

Hi All,
I am loading masterdata from ODS to infoobject as data target, I am getting an error message as
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 Service API .
Refer to the error message.
DataSource 80BP_ID does not have the same status as the source system in the Business Information Warehouse.
The time stamp in the source system is 09.08.2006 10:17:24.
The time stamp in the BW system is 15.03.2006 16:44:34.
But we are getting Data till ODS, when we manually load from ODS to infoobject this error is coming up.
Please help in resolving this,
Thanks,
Sairam.

You are welcome Sairam
The generated objects are export datasources based on the ODS objects. These are automatically generated because ODS objects are a key component to a data model or datawarehouse strategy where their role is to stage the data for consolidation or harmonization purposes. The generated datasource helps you to load data into further data targets. The use of a cube as an export datasource is not as common, and so the datasource is not automatically generated for them.
Hope this helps...

Error While Loading data from ODS to Infocube

I am trying to load data from ODS to Infocube thru Update ODS data into data target. My requirement was to take a small subset of fields from ODS and design IC and load the data.
My load fails at Extraction process as I get 0 records from total number of records sent in each package. Please let me know if you need more information.
Please advise.
Thanks,
RR

In Details tab of monitor, in extraction step,
Extraction(messages): Errors occured
Green Light for Data Request Received
Green Light for Data Selection Scheduled
Yellow for 25000 Records sent(0 records received)
Yellow for 25000 Records sent(0 records received)
Yellow for 15000 Records sent(0 records received)
Green Light for Data Selection Ended
Please let me know, If you need more information.
Thanks,
R R

Error while loading data from ODS to IC.

Hi Experts,
             I am trying to load data from ODS to IC using Initial load. I failed first time. Then when I am trying to schedule it again I am getting a error message. I deleted the intial request. Even after that, I am getting the following message. Am I missing something?
Delete init. request
REQU_BQQCBQV5ZK9YEBB416C8QXXLC before running
init. again with same selection
Also can any one provide me a document that contians the lenght of all teh technames? I know I can find it out by looking into each one of the Tech Names. But I would be nice if anyone of you can provide me a document.
Can anyone of you please help me.
Thanks,
Nandini.

Hi,
By reading the error:
No transfer structure for InfoSource 8ZYNA_ODS and source system B3TCLNT800
I think the problem is actually with a Datamart. You can try to regenerate the export datasource and activate it.
Also, you can try to activate only the transfer structure again using the report "RS_TRANSTRU_ACTIVATE_ALL".
I hope this helps!
Pietro

Error while loading data from ODS to CUBE.

Hi friends,
When l am loading data from ODS to Cube with help of data mart, I am getting error in QA system , IN DM system ,every thing went well.IF i see the detail tab in monitor under Processing .
Its is showing like this .
Transfer Rules : Missing Massage.
Update PSA : missing massage.
Processing end : missing message.
I have checked the coding in update rules, everything is ok.
Plz any inputs.
hari
Message was edited by:
hari reddy

Might means that IDocs flow is not defined properly in your QA system for myself-SourceSystem.
Regards,
Vitaliy

Error in ODS data load

Hi,
I am trying to load data to ODS from CSV file but one of the field is not getting updated.
Although, that field has data in PSA. Why is it happening???

Hi,
Is the request loaded without errors to the ODS? Check the mapping for the field in the update rules, if you are doing it in 3.x or check the Tranformations.
Hope it helps.
Veerendra.

Error when trying to load data from ODS to CUBE

hi,
Iam getting a short dump when trying to load data from ODS to CUBE. The Run time error is 'TYPELOAD_NEW_VERSION' and the short text is 'A newer version of data type "/BIC/AZODS_CA00" was found than one required.please help me out.

Hi,
Check this thread.........Ajeet Singh has given a good solution here.........
Re: Error With Data Load-Getting Canceled Right Away
Also check SAP note: 382480..................for ur reference............
Symptom
A DART extraction job terminates with runtime error TYPELOAD_NEW_VERSION and error message:
Data type "TXW_INDEX" was found in a newer version than required.
The termination occurs in the ABAP/4 program "SAPLTXW2 " in "TXW_SEGMENT_RECORD_EXPORT".
Additional key words
RTXWCF01, LTXW2U01, TXW_INDEX
Cause and prerequisites
This problem seems to happen when several DART extraction jobs are running in parallel, and both jobs access table TXW_INDEX.
Solution
If possible, avoid running DART extractions in parallel.
If you do plan to run such jobs in parallel, please consider the following points:
In the DART Extract configuration, increase the value of the parameter "Maximum memory allocation for index (MB)" if possible. You can estimate reasonable values with the "File size worksheet" utility.
Run parallel DART jobs on different application servers.
As an alternative, please apply note 400195.
It may help u.........
Regards,
Debjani.......

Error During Load Infocube from ODS

Hi guys i hae an infocube and an ODS i load data to the ODS directly from SAP and its OK but i have an error when i try to load data from ODS to infocube, i`ve created an update rule from ODS to infocube theres an error in the load request "Load Request is invalid" i try to load to infocube from ODS in many ways Full, Init Delta but i have the same error in all of them.....i need to do something before or i need to change in any way the data targets.....
I hope somebody could help me with this.......

HI,
Activate the data in ur ODS. Then right click on ur ODS n choose "create export datasource". Now right click ur ODS and go to "Manage" and make sure that the QM status is green and the Datamart status is checked with a green mark. Now carry on the load from ODS to infocube.
Hope this helps...Let me know
Regards,
R.Ravi

Error in ODS data loading

Hi Gurus
I am extracting data from R/3 which as Material movement.
every thing i am using standard objects only.
now i am loading 2lis_03_bf to ODS, i got error as
" InfoOject SOLD_TO does not contain alpa-conforming value 104090...
How can i change standard SOLD_TO_PARTY
detailed Analysis as follows
Diagnosis
 The system checked whether the loaded InfoObject value conforms to the
 conversion exit.The check failed.
 For example:
 The value '1' was loaded into an InfoObject with alpha exit, even thoug
 the value '0000000001' was expected.
System Response
 The load process has failed or the erroneous records are displayed in
 the monitor. This does not depend on how error handling is set up.
Procedure
 Find out why the data does not conform to the conversion exit, and, if
possible, correct the cause. Possible causes are errors in BI Content or
an error in a customer exit in the source system.
If you cannot correct the problem, you have the option of removing the
conversion exit on the InfoObject. However, since the system has already
been converted, duplicates appear in the system again.
Immediate Reply highly appreciatable
Thanks in Advance

Hi Sudheer,
Go to your transfer rule.
in the right-hand side.
Select 0SOLD_TO and move the horizontal scrollbar till end..you find one conversion..check that..
Hope i m clear.
Regards,
San!

Two load errors for a standard SRM Contract ODS

We've just installed standard business content for SRM Contract ODS. The standard InfoSource we installed is 0BBP_TD_CONTR_1. Two loading errors occur:
1st error:
No return value <> 0 allowed in update routines in transfer mode
Diagnosis
The return code was set to <> 0 in routine 'r0063_0SR_TARGVDC ', but the corresponding data field is updated with MOVE. You therefore can not prevent the update of a single data field for certain key values.
System Response
The load process is terminated.
Procedure
When you update with MOVE, you do not have to update all the data records. In this case you should use a start routine in the update rules in which you delete the data records that you do not want to update from table DATA_PACKAGE. Set the return code for all routines affecting a data field that is updated with MOVE to 0 (also the corresponding key field routines).
Procedure for System Administration
2nd error:
Error converting currency to standard currency (see long text!) RSBCTBBP
Diagnosis
Record number 1 : Error during currency conversion to standard currency.
The currency JPY of field 0OUTAGTARGT could not be determined.
Procedure
 Possible causes are listed below:
 - Could not find currency tables RSCURTRT or TCURR
 - Could not determine conversion date
 - Could not find an exchange rate for currency JPY in table TCURR
 Check the erroneous data record, currency unit, and date.If all data is
 available, check whether the standard currency was created correctly.
You can change it in transaction <rscur> by changing the settings for InfoObject 0SR_DEFCUR.
Furthermore, the global settings must be transferred from the source system in order to get the currency keys of the currencies (maintained for currency JPY in table TCURR). Use transaction <rsa1> to transfer the global settings. Select 'Source Systems' and choose the entry 'Transfer Global Settings' for the respective source system.
Note: we've transfer the global settings at currency from our SRM source system already, but we still get the same error msgs.
Any idea/solution?
Thanks

Hello All,
As I have already mentioned the condition types in SRM are identically matched to ERP condition type hence the data is flowing correctly and even the idoc has the z-condition type Z123.The IDOC in backend ERP has status 53.
On trial and error method we did unchecked the manual indicator check in the pricing schema for the relevant condition type and because of that now the Z-condiiton type can be seen in the backend ERP contract.
If the indicator was checked, this means that this condition can be maintained only manually (directly in the transaction
ME32K in ECC) and nothing can be transfer from other source.
Note: If the same condition type is being used in more than one pricing procedure then ensure that the check bok is unchecked for agianst the relevant condition type.
Thanks,
Yatin

Load error in ODS

Similar Messages

Maybe you are looking for