Error in Inventory Data loads:"2LIS_03_BF_Delta"

Hi,
We are loading transaction data via 2LIS_03_BF_Delta & 2LIS_03_UM_Delta using process chains to two data targets(Cubes).
Yesterday the delta failed & we forcefully added the data via P.S.A after deleting it from the cube.
Today the delta failed again with a message "Last Delta Incorrect, repeat not possible". Also the data today for 2LIS_03_BF_Delta has not arrived to BW but the info package shows failed status.
In RSA7 the data is available. The 2LIS_03_UM is working fine.
Pls Help.
Thanks in Advance.
Praveen

You can try this way:
Check the request number in BW for the latest green request, this should match with the one you find in source system table ROOSPRMC and field DELTARNR. If the numbers match this means r/3 keeps a track of the deltas. Now make QM status red for the failed deltas, delete tehm from ODS and take the delta again. Just make sure you have the records in RSA7 for the failed deltas.
Also refer OSS notes 873694.
Assign points if this helps!
Regards,
Manasa.

Similar Messages

How to rectify the errors in master data loads & transactional data loads?

hy,
please any one tell me
How to rectify the errors in master data loads & transactional data loads?
thnQ
Ravi

Hi,
Please post specific questions in the forum.
Please explain the error you are getting.
-Vikram

Error in Master data load because of ###

Hello,
I am getting an error in master data load.
The problem is ####### symbols are encountered in few records.
We have defined a formula to replace the ### with S in transfer structure.
But still it does not replace the #### symbols and gives error.
But when I insert the ####### symbols manually in PSA and try to load it is replaced with the formula definition and loads the data.
Suggestions required urgently
Thanks in advance
Ram

Hello srikanth,
Check the code below.
I have used it in the update rule to replace the #### symbol with A.
But when i check in debug mode it is not recognizing this symbol and sy-subrc ia always 4.
GV_STRING = COMM_STRUCTURE-/BIC/XXX
FIND '#' in R_STRING.
IF SY-SUBRC = 0.
REPLACE ALL OCCURRENCES OF '#' in R_STRING with 'A'.
ENDIF.
result value of the routine
RESULT = R_STRING
Thanks
Ram

Inventory data loads

Hi All,
I am new to BI and I have dought about inventory data loads u201Ccan I load BF data source with out loading BX data source and compress with marker update? Yes or NO; if yes justify reasons.
Regards,
Krish

Hi,
Read the document "How to handle Inventory Management Scenarios in BW (NW2004)" at http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328?quicklink=index&overridelayout=true
This will clear all your doubts.

Error Message after data load (error is "1130610")

We load data using a data load rule. The data seems to load fine except we get the error message "ERROR - 1241101 - Unexpected Essbase error 1130610" on last line below? Any thoughts? Is there a guide somewhere that explains in details all the various error codes and what they refer to? We're using Essbase 6.5.1. Thanks!======================================= OK/INFO - 1003037 - Data Load Updated [364875] cells. OK/INFO - 1003024 - Data Load Elapsed Time : [428.323] seconds. ERROR - 1241101 - Unexpected Essbase error 1130610.=======================================

The explanation of error 1130610 is the following:Possible Problems - Essbase cannot open a file. Possible Solutions - If you are using an error file, make sure that the error file is being created in a directory that already exists. Make sure you are using the ESSCMD IMPORT command correctly. Put all files the ESSCMD script needs in the $ARBORPATH\APP\applicationName\databaseName directory. Run the ESSCMD script from the $ARBORPATH\APP\applicationName\databaseName directory. Check the ESSCMD script for invalid paths. Make sure every folder that the script is pointing to exists. If you are using an error file, make sure that the error file is being created in a directory that already exists.

Error while starting data loading on InfoPackage

Hi everybody,
I'm new at SAP BW and I'm working in the "Step-By-Step: From Data Model to the BI Application in the web" document from SAP.
I'm having a problem at the (Chapter 9 in the item c - Starting Data Load Immediately).
If anyone can help me:
Thanks,
Thiago
Below are the copy of the error from my SAP GUI.
<><><><><><><><><><<><><><><><><><><><><><><><><><><><><><><><>
Runtime Errors MESSAGE_TYPE_X
Date and Time 19.01.2009 14:41:22
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
Batch - Manager for BW Processes ***********
Long text of error message:
Technical information about the message:
Message class....... "RSBATCH"
Number.............. 000
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSBATCH" or "LRSBATCHU01"
"RSBATCH_START_PROCESS"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 701
Application server... "sun"
Network address...... "174.16.5.194"
Operating system..... "Windows NT"
Release.............. "5.1"
Hardware type........ "2x Intel 801586"
Character length.... 8 Bits
Pointer length....... 32 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "localhost"
Database type..... "ADABAS D"
Database name..... "NSP"
Database user ID.. "SAPNSP"
Terminal.......... "sun"
Char.set.... "English_United State"
SAP kernel....... 701
created (date)... "Jul 16 2008 23:09:09"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQLDBC 7.6.4.014 CL 188347 "
Patch level. 7
Patch text.. " "
Database............. "MaxDB 7.6, MaxDB 7.7"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 8112
EM...... 11498256
Heap.... 0
Page.... 65536
MM Used. 6229800
MM Free. 1085264
User and Transaction
Client.............. 001
User................ "THIAGO"
Language key........ "E"
Transaction......... "RSA1 "
Transactions ID..... "CD47E6DDD55EF199B4E6001B782D539C"
Program............. "SAPLRSBATCH"
Screen.............. "SAPLRSS1 2500"
Screen line......... 7
Information on where terminated
Termination occurred in the ABAP program "SAPLRSBATCH" - in
"RSBATCH_START_PROCESS".
The main program was "RSAWBN_START ".
In the source code you have the termination point in line 340
of the (Include) program "LRSBATCHU01".
Source Code Extract
Line
SourceCde
310
endif.
311
l_lnr_callstack = l_lnr_callstack - 1.
312
endloop. " at l_t_callstack
313
endif.
314
315
*---- Eintrag für RSBATCHHEADER -
316
l_s_rsbatchheader-batch_id = i_batch_id.
317
call function 'GET_JOB_RUNTIME_INFO'
318
importing
319
jobcount = l_s_rsbatchheader-jobcount
320
jobname = l_s_rsbatchheader-jobname
321
exceptions
322
no_runtime_info = 1
323
others = 2.
324
call function 'TH_SERVER_LIST'
325
tables
326
list = l_t_server
327
exceptions
328
no_server_list = 1
329
others = 2.
330
data: l_myname type msname2.
331
call 'C_SAPGPARAM' id 'NAME' field 'rdisp/myname'
332
id 'VALUE' field l_myname.
333
read table l_t_server with key
334
name = l_myname.
335
if sy-subrc = 0.
336
l_s_rsbatchheader-host = l_t_server-host.
337
l_s_rsbatchheader-server = l_myname.
338
refresh l_t_server.
339
else.
>>>>>
message x000.
341
endif.
342
data: l_wp_index type i.
343
call function 'TH_GET_OWN_WP_NO'
344
importing
345
subrc = l_subrc
346
wp_index = l_wp_index
347
wp_pid = l_s_rsbatchheader-wp_pid.
348
if l_subrc <> 0.
349
message x000.
350
endif.
351
l_s_rsbatchheader-wp_no = l_wp_index.
352
l_s_rsbatchheader-ts_start = l_tstamps.
353
l_s_rsbatchheader-uname = sy-uname.
354
l_s_rsbatchheader-module_name = l_module_name.
355
l_s_rsbatchheader-module_type = l_module_type.
356
l_s_rsbatchheader-pc_variant = i_pc_variant.
357
l_s_rsbatchheader-pc_instance = i_pc_instance.
358
l_s_rsbatchheader-pc_logid = i_pc_logid.
359
l_s_rsbatchheader-pc_callback = i_pc_callback_at_end.

Hi,
i am also getting related this issue kindly see this below short dump description.
Short text
 The current application triggered a termination with a short dump.
What happened?
 The current application program detected a situation which really
 should not occur. Therefore, a termination with a short dump was
 triggered on purpose by the key word MESSAGE (type X).
What can you do?
 Note down which actions and inputs caused the error.
 To process the problem further, contact you SAP system
 administrator.
 Using Transaction ST22 for ABAP Dump Analysis, you can look
 at and manage termination messages, and you can also
 keep them for a long time.
Error analysis
 Short text of error message:
 Variant RSPROCESS0000000000705 does not exist
 Long text of error message:
 Diagnosis
 You selected variant 00000000705 for program RSPROCESS.
 This variant does not exist.
 System Response
 Procedure
 Correct the entry.
 Technical information about the message:
 Message class....... "DB"
Number.............. 612
 Variable 1.......... "&0000000000705"
 Variable 2.......... "RSPROCESS"
 Variable 3.......... " "
 Variable 4.......... " "
How to correct the error
 Probably the only way to eliminate the error is to correct the program.
 If the error occures in a non-modified SAP program, you may be able to
 find an interim solution in an SAP Note.
 If you have access to SAP Notes, carry out a search with the following
 keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSPC_BACKEND" or "LRSPC_BACKENDU05"
"RSPC_PROCESS_FINISH"
 If you cannot solve the problem yourself and want to send an error
 notification to SAP, include the following information:
 1. The description of the current problem (short dump)
 To save the description, choose "System->List->Save->Local File
(Unconverted)".
 2. Corresponding system log
 Display the system log by calling transaction SM21.
 Restrict the time interval to 10 minutes before and five minutes
 after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
 3. If the problem occurs in a problem of your own or a modified SAP
 program: The source code of the program
 In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
 4. Details about the conditions under which the error occurred or which
 actions and input led to the error.
System environment
 SAP-Release 701
 Application server... "CMCBIPRD"
 Network address...... "192.168.50.12"
 Operating system..... "Windows NT"
Release.............. "6.1"
 Hardware type........ "16x AMD64 Level"
 Character length.... 16 Bits
 Pointer length....... 64 Bits
 Work process number.. 0
 Shortdump setting.... "full"
 Database server... "CMCBIPRD"
 Database type..... "MSSQL"
 Database name..... "BIP"
 Database user ID.. "bip"
 Terminal.......... "CMCBIPRD"
Char.set.... "C"
SAP kernel....... 701
created (date)... "Sep 9 2012 23:43:54"
create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 196
Patch text.. " "
Database............. "MSSQL 9.00.2047 or higher"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
 NT 6.0, Windows NT 6.1, Windows NT 6.2"
Memory consumption
Roll.... 16192
EM...... 4189840
Heap.... 0
Page.... 16384
MM Used. 2143680
MM Free. 2043536
User and Transaction
Client.............. 001
User................ "BWREMOTE"
 Language Key........ "E"
Transaction......... " "
 Transactions ID..... "9C109BE2C9FBF18BBD4BE61F13CE9693"
Program............. "SAPLRSPC_BACKEND"
Screen.............. "SAPMSSY1 3004"
 Screen Line......... 2
 Information on caller of Remote Function Call (RFC):
System.............. "BIP"
 Database Release.... 701
 Kernel Release...... 701
 Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
 Call Type........... "asynchron without reply and transactional (emode 0, imode
 0)"
 Inbound TID.........." "
 Inbound Queue Name..." "
 Outbound TID........." "
 Outbound Queue Name.." "
Information on where terminated
 Termination occurred in the ABAP program "SAPLRSPC_BACKEND" - in
"RSPC_PROCESS_FINISH".
 The main program was "SAPMSSY1 ".
 In the source code you have the termination point in line 75
 of the (Include) program "LRSPC_BACKENDU05".
Source Code Extract
Line SourceCde
 45 l_t_info TYPE rs_t_rscedst,
 46 l_s_info TYPE rscedst,
 47 l_s_mon TYPE rsmonpc,
 48 l_synchronous TYPE rs_bool,
 49 l_sync_debug TYPE rs_bool,
 50 l_eventp TYPE btcevtparm,
 51 l_eventno TYPE rspc_eventno,
 52 l_t_recipients TYPE rsra_t_recipient,
52 l_t_recipients TYPE rsra_t_recipient,
53 l_s_recipients TYPE rsra_s_recipient,
54 l_sms TYPE rs_bool,
55 l_t_text TYPE rspc_t_text.
56
57 IF i_dump_at_error = rs_c_true.
58 * ==== Dump at error? => Recursive Call catching errors ====
59 CALL FUNCTION 'RSPC_PROCESS_FINISH'
60 EXPORTING
61 i_logid = i_logid
62 i_chain = i_chain
63 i_type = i_type
64 i_variant = i_variant
65 i_instance = i_instance
66 i_state = i_state
67 i_eventno = i_eventno
68 i_hold = i_hold
69 i_job_count = i_job_count
70 i_batchdate = i_batchdate
71 i_batchtime = i_batchtime
72 EXCEPTIONS
73 error_message = 1.
74 IF sy-subrc <> 0.
>>> MESSAGE ID sy-msgid TYPE 'X' NUMBER sy-msgno
76 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
77 ELSE.
78 EXIT.
79 ENDIF.
80 ENDIF.
81 * ==== Cleanup ====
82 COMMIT WORK.
83 * ==== Get Chain ====
84 IF i_chain IS INITIAL.
85 SELECT SINGLE chain_id FROM rspclogchain INTO l_chain
86 WHERE log_id = i_logid.
87 ELSE.
88 l_chain = i_chain.
89 ENDIF.
90 * ==== Lock ====
91 * ---- Lock process ----
92 DO.
93 CALL FUNCTION 'ENQUEUE_ERSPCPROCESS'
94 EXPORTING
If we do this
Use table RSSDLINIT and in OLTPSOURCRE: enter the name of the data source
And in the logsys enter the name of the source system and delete the entry for that info package. what will happen is process chain will run suceesfully and short dump will not come or what kindly give the detail explanation about this RSSDLINIT.
Regards,
poluru

BW ERROR while doing data loading

1)while doing data load error--Processing data packet- No Data,
2)Data Package 1 : arrived in BW ; Processing : 2nd processing step not yet finished.
3) Also in some cases there are 0 from 0 records and request is still Yellow i can't delete that too .what option are there to resolve such request.
What can be possible solution.

Hi
First the data is come to PSA?If yes then u r problem is from PSA to Data Target.In this case Manually change the request status to red and then delete load the data.
Second If the data not at come to PSA also then check in RSA3 whetehr Data avialble or Not.If it is Delta load then check the entries in RSA7.
Regards
Ram.

Inventory data load from Inventory Cube to another Copy Cube

Hello Experts,
I am trying to load Inventory data from the Inventory cube(say YCINV) to a copy cube say YCOPY_CINV(copy of Inventory cube), but the results appear inconsistant when I compare the reports on these 2 cubes. I am trying to populate a fiield in copy cube so that I can populate the same data back to the original cube with the new field in it, I am doing this reload back and forth for historical data purpose only.
I have seen lot of posts as how to run the setups for Inventory data, but my case does not need to perform set up runs.
Does the note 1426533 solve the issue of loading from one cube to another ? we are on SAP BI 7.01 with SP 06 ,but the note specifies SP 07 ?
I have tried note 375098 to see if it works, but I do not see the options as mentioned from step "Using DTP (BW 7.x)" in BI to perform this note
Please advise on whether to go with implementing note 1426533 or is there any other way to load inventory data from one cube to other.
Regards,
JB

Hi Luis,
Thanks for your reply,
I do not see any setting like Intial stock in DTP except "initial non-cumulative for non- cumulative". I did try using the option "initial non-cumulative for non- cumulative" ,but the results still do not match with the inventory cube data.I do not see the check box for marker in the copy cube (under roll up tab). Please let me know if we can really implement this solution ,i.e. copying from inventory cube to copy cube and then re-loading it back to inventory cube for historical data. Currenlty, I am comparing the queries on these 2 cubes, if the data matches then I can go ahead and implement it in Production, other wise it would not be wise to do so .
Regards,
JB

Sql loader error in offline data load

Hi,
I have done an offline schema creation using existing tablespace.
I am trying to do an offline data load using sql loader.The CTL and DAT file are generated by the work bench.
This is my CTL file code generated by workbench.
load data
infile 'Import.dat' "str '<EORD>'"
into table IMPORT
fields terminated by '<EOFD>'
trailing nullcols
When I am running the ctl file with DAT file in sql loader I am getting the following error
SQL*Loader-350: Syntax error at line 4.
Expecting single char, found "<EOFD>".
fields terminated by '<EOFD>'
^
My Sql Loader version is Release 8.0.6.3.0
Please help if anyone has came across this issue.
Thanks in advance.
Regards
Saravanan.B

Saravanan,
Its a long time since I have seen 8 sql loader. Check the doc. Is it resrticted to a single character delimter??
Barry

Error is Master Data load.

Hi Experts,
From last 1 month the ( 0MAT_UNIT ) master data load is getting failed. Its a full load. So the the target is not updated from last one month( August)
Now the problem is , when I am checking a report. The materials which are new or changed are not getting the data properly. It is because of the master data got stucked at PSA level.And I cant rectify at PSA level because, There is 673 errorneous record in 1 package.
I tried to find the invalid character , but didn't get anything.
Please suggest.
Thanks,
TapuKumar

Hi Anand,
        This is the long text msg
Data records in the PSA were marked for data package 1 . Here there were
673 errors. The system wrote information or warnings for the remaining
data records.
                                                                                System response
The data package was not updated.
Procedure
Correct the incorrect data records of the data package (for example by
     manually editing them in the PSA maintenance). You can find the error
     message for each of the records in the PSA by double-clicking on the
     status of the record.
Note
Note that you are only allowed to edit and manually update the request
     if it is contained in the request list in the data target. Where
     necessary, first delete it from the data target.
And it is a master data load( Full ), The data target is a INFO OBJECT.
Please suggest, I can't rectify each and every reecord. Because the number of record id very high..
Thanks,
Tapu Kumar.
Edited by: NewToBW on Sep 2, 2010 1:42 PM

Error while activating data loaded into DataStore Object in BI 7.0

Hi Guys,
I am facing the following problem :
When I load data into a Datastore Object, all the records get loaded but the job fails during activation of the data.
Below is the job log :
Activation is running: Data target 0RPM_DS07, from 77 to 77
Overlapping check with archived data areas for InfoProvider 0RPM_DS07
Check not necessary, as no data has been archived for 0RPM_DS07
Data to be activated successfully checked against archiving objects
SQL-END: 14.06.2007 12:33:25 00:00:00
SQL Error: ORA-20000: Insufficient privileges
Parallel processes (for Activation); 000003
Timeout for parallel process (for Activation): 000300
Package size (for Activation): 020000
Task handling (for Activation): Backgr Process
Server group (for Activation): No Server Group Configured
All data fields updated in mode "overwrite"
Resource error. No batch process available. Process terminated
Time limit exceeded. No return of the split processes
Resource error. No batch process available. Process terminated
Request you to kindly help me resolve this issue.
I am runnning the infopackage manually. Should I run it by a process chain??
If I run by process chain, I get the following error in 1st step:
You do not have authorization for InfoSource 0RPM_ITEM_FIN_PLANNING.
Awaiting your replies,
Thanks,
punkuj...

Hi,
I think this problem remains unanswered.
The issue behind this problem is, during parellel activation the child jobs acknowledge the parent job about status. If the child job takes long time to read data from active data table, then it times out and fails.
Check the primary index on Active data table and it should be missing in your case. See the se11 index or db02 missing indexes. That is the reason that causes time out. Rebuild the primary index by asking your basis folks and repeat the activation. It should succeed.
Thanks,
Sri.

Error in Master data load

hello gurus,
where my service order attribute had loaded successfully
But now i got strucked in loading text for the same,
request got all the data but shows still running
where in detail tab it is showing mess as follows
>Extraction (messages): Errors occurred
 90909 Records sent ( 90909 Records received )
>Transfer (IDocs and TRFC): Missing messages or warnings
 Data Package 3: arrived in BW; Processing : Processing not yet finished, entry 70 still missi
>Processing (data packet): Warning received
>Transfer rules ( 90909 -> 90909 Records ):No errors
 Data Package 3 ( 90909 Records ) : Missing messages
 Update ( 0 new / 0 changed ) : Missing messages
can u plz refer to slove this issue
Thank's
SAP

hello Arun ,
Thanks for ur replay
where all the error message for the error was as shown in pervious message,
where in the setp by step analysis mess is as below
It is possible that data packets must be processed manually.
INBOX
The process is probably still running.
REDS
SAP

Error in heirarchy data load

Hi
While loading Hierarchy data getting error The node for id 5478952 contains Invalid characters.
Please update its urgent
Thanks
sunil
Edited by: sunil chowdary on Aug 21, 2008 1:16 PM

Hi,
Please identify the invalid characters and add them in the system via transaction: RSKC.
You can also, try to check those values in the source system (e.g. R/3).
Hope it helps.
AT

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.

Inventory data load

Hi guru,
i am new in extracting BI inventory's data.
In the process, it is said : " take down time according to the of data" before initializing stock (using transaction MCNB ) for 2LIS_03_BX data source.
My question : how to take down time ?
Thanks in advance

Hi Firman,
First check your current system loading process for other modules.Means how much system taking for loading data.Based on that you need to take the downtime.But you need to make sure that loads should be completed by specified downtime.
Normally we will the downtime weekends in the latenights.So it will not effect the business.
Regards
Ram.

Error in Inventory Data loads:"2LIS_03_BF_Delta"

Similar Messages

Maybe you are looking for