Delta Load Error in the Data Extraction

Hi BI Guru`s,
The issue is with the extractor 2LIS_13_VDKON (Pricing conditions), The regular delta till 22.07.2010 has run successfully, But on 23.07.2010 the delta got failed with the error message " Data Package 58 : arrived in BW ; Processing : Processing not yet finished, entry 70 still missi" for one of the Datapacket. We have repeated the load even though we got the same error message, Since the client is retailer we will be having the delta records of 200 million ( approx. 23369612) in a day. Since because of this error we could't load any of the delta from that day onwards.
Need Help on this:
1. How to get the old delta
2. How to re-initialize the process for delta. (Pls keep it in mind the volume of the records).
Thanks in Advance,
Venkat

Hi,
Here we need decrease the datapacket size as well as prallel proceesing .
than we need to load the historical data through dalta repetition
hope..helpful for you!
Regards!
Malli.

Similar Messages

Invalid data status error during the data extraction

Hi,
while extracting capacity data from the SNP Capacity view to BW. i get the "invalid data status error" and the data extraction fails.
when debugged the bad requests of the ODS object, i found that for a certain product(which has both positive and negative input and out qtys) co-product manufacturing orders were created. but this product was not marked as the co-product and functionally its fine.
how can i rectify the data extraction problem..can you advice.
Thanks,
Dhanush

Sir,
In my company for some production order status some are having "errors in cost calculation" ie "cser" .how to deal these kind of errors.

How the data extraction happens from HR datasources from R/3 to BW system.

Hello All
How the data extraction happens from HR datasources from R/3 to BW system.Incase of delta records ( for CATS datasources ) ,Is there any flow like LO .
Incase of Full and delta loads how does the data will be taken from R/3 to BW,DO we need to fill setup tables ?
Searched forum but couldnt able to find the relevant one.
Thankyou
Shankar

Hi Shankar.
HR Datasources do not have setup tables . Though before implementation, certain customizations should be done and the delta loads have dependency on other data sources. Also you must have implemented Support Package SAPKH46C32, or have made the relevant corrections in SAP Note 509592.
Follow this link for details on customization and dependencies for all CATS datasources.
http://help.sap.com/saphelp_nw70/helpdata/en/86/1f5f3c0fdea575e10000000a114084/frameset.htm
Regards,
Swati

MAster Data - Delta Load Error?

Hi,
I am having error in 0COSTCENTER delta load. In the Info Package of 0COSTCENTER, it was not selected to PSA. It was selected to InfoObject directly.
Since this is a delta load for Master data, how can i correct this error?
Thanks!
Venkata

Hi Venkat,
You can done a full upload without affecting Delta upload. Make a test on Dev or Qual and you will see that a full on Master Data does not stop delta process.
Ciao.
Riccardo.

'Error 8 occurred when starting the data extraction program'

Hello Experts,
I am trying to pull master data (Full upload) for a attribute. I am getting an error on BW side i.e. 'The error occurred in Service API .'
So I checked in Source system and found that the an IDOC processing failure has occurred. The failure shows 'Error 8 occurred when starting the data extraction program'.
But when I check the extractor through RSA3, it looks fine.
Can someone inform what might be the reason of the failure for IDOC processing and how can this be avoided in future. Because the same problem kept occurring later as well.
Thanks
Regards,
KP

Hi,
Chk the idocs from SM58 of source system are processing fine into ur target system(BI system)...?
Chk thru Sm58 and give all * and target destination as ur BI system and execute and chk any entries pending there?
rgds,
Edited by: Krishna Rao on May 6, 2009 3:22 PM

Error in the Data Selection - Errors in Source System RSM 340

Hey Everyone,
I'm having an issue with loading a Delta for 0MAT_PLANT_ATTR. This is the second night it has happened, where I get the error "Error in the Data Selection". This error happens in the EXTRACTION part of the Monitor. And, we cannot run another Delta to see if it'll work, we have to delete the old Delta Init, and run a new one. The other error is "Errors in Source System - RSM340". That's as much it gives.
Could anyone suggest why this would be happening? I checked RSA3 in R/3, and no errors on the extraction. I also checked sm37 against the job that loads that data, and it completed successfully. I honestly don't think there's an issue with the data. We cannot have this happen often, and I just need to know if this is something that can be corrected.
Thanks,
John

There is nothing wrong with the TID's or anything like that. There is also no selection criteria in the infopackage.
When the Delta fails, the error occurs under EXTRACTION in the monitor. It seems to be successful under TRANSFER and PROCESSING in the monitor, which I find strange. Also, I run a new Delta Init with Data Transfer, and that works just fine.
So, I'm not sure what it could be?

0COORDER - Delta Load Error

Hi,
We are having 0COORDER as a regular delta load. Today we are facing error message: <b>68 duplicate records found in the master data</b>. I am updating data in series from PSA to data target.
Can you please let me advice, how can i correct this data load error in Master data?
Best Regards,
Venkat.

You should choose the option of ignore duplicate records to let this master data complete sucsessfully. I wouldnt recommend this until you find the root cause for the duplicate records. If you ignore the duplicate records, it is only going to load the first record and the ignore the records with the same key combination. What if the record with correct values came in after the incorrect record. This may lead to some inconsistency. So please check with functional folks and try to analyze the root cause.

CO-PA Delta load - Errors in source system RSM 340

Hi,
We are facing a unique error when we do a CO-PA delta load. The error message is as follows:
"Errors in source system RSM 340,The selected data source is locked by another process RD 156"
The load completes successfully with 0 delta records fetched. When we re - trigger this after sometime, the load goes through.
Can anyone explain as to why this issue occurs ? Basically, looking at the root cause.
We are pulling data from CE1XXXX table, the delta for which is pulled into BW with the setting of 30 minutes safety delta. Just wanted to understand how is it that in this scenario we are faced with a lock issue ? It is also confirmed that while the delta load is initiated the transactions are being passed into the CE1XXXX table.
Thanks,
Amit Mitra

Hi PK,
caller 09 error mainly because of source(target system) and destination(bw system) not configured correctly.
i think you get the error message as follows. file is in the client workstation as like.
better you contact basis people. they will resolve this.
hope this help you
Regards
Harikrishna N

Error reading the data from the remote cube

Hi all,
When we try to get the data for remote cube from LISTCUBE, we are getting the following msg.
1) Messages for DataSource 9AUPA_DP_HK_01 from source system AD1CLNT100
2) 224(/SAPAPO/TSM): No planning version selected
3) Errors have occurred while extracting data from DataSource 9AUPA_DP_HK_01
4) Error reading the data of InfoProvider UICHKRMTC.
Any Inputs?

Hi,
Check whether the sourcesystem is responding.
And also in the error mesg: 224(/SAPAPO/TSM): No planning version selected
It seems you have not selected any planning version. Give any planning version in the listcube selection screen and execute.
Regards,
Ravi Kanth

Can't open aperture 3, warning box comes up," warning there was an error opening the data base for the library /pictures/aperture library .aplibrary Whats up?

I have had Aperture 3 loaded on my computer for a while now. Never had any problems till tonight. Restarted my computer and went to open Aperture and a "warning" box poped up, There was an error opening the data base for the library /picture/aperture library ap library. Then a "quit" button.
What is going on and how can I open my aperture. I have pictures that need worked for clients. Help!

Have you run through the steps in Aperture 3: Troubleshooting Basics. If not that's always a good place to start.
If that doesn;t resolve the problem when you post back describe your hardware and software setup.
good luck

EVDRE encountered error retrieving the data from web Server

Hi,
I know this is the common/generic error message, following is our scenario:
We installed BPC NW 7.5 on our production box and configured F5 load balancing for two .NET servers.
We are getting the error "EVDRE encountered error retrieving the data from web Server"when we run the report EVDRE on APSHELL (original Appset). This is the fresh installation:
The workaround "Clear Local application information". Even this works only sometimes.
Is there anything else we should have configured on using two .NET servers?
Please suggest.
Thanks

hi Nagesh sorry for the delayed reply..
We changed some of the parameters at F5 switch like sticky time, timeout..
And the MDXPARSER connection to one of out application server was failling, thats why we did not had this issue consistently.
When ever the request goes to that app server fails. It took a lot effort to notice this since we were assuming the F5 switch was only causing the issue.
Thanks

BEX query error---Error reading the data of InfoProvider

Hello all,
we are getting the following msg when we execute the query-
Error reading the data of InfoProvider ZEUDPR01
Errors occurred when extracting data from DataSource 9AEU_DOM
Short Text: Error for COM routine using application program (return c
Parameter: 1028533- LC kernel
Message in Source System: E102(/SAPAPO/OM) ...
Short Text: COM - error Unknown
Parameter: Unknown
Message in Source System: E001(/SAPAPO/OM) ...
Messages for DataSource 9AEU_DOM from source system PA1CLNT100
Errors occurred during parallel processing of query 4, RC: 3
Error while reading data; navigation is possible
Row: 54 Inc: WRITE_MESSAGES Prog: CL_RSDR_AT_QUERY
Found
This is the error observed for a particular selection only..for rest of the selection we get the data correctly.
Please help with the possible causes of error.
Thanks,
Pallavi

Hi Pallavi,
How did you manage the pb?
we have the same error after Stack 21 (SP23)
we could not run query.
Thanks.
John

How to identify whether the data extracted is direct, queued, unserialized

hi,
how to identify whether the data extraction from r/3 is direct, queued and unseralized data.
can anyone let me know abt it
regds
hari

hI,
Direct Delta: With this update mode, the extraction data is transferred with each document posting directly into the BW delta queue. In doing so, each document posting with delta extraction is posted for exactly one LUW in the respective BW delta queues.
This update method is recommended for the following general criteria:
a) A maximum of 10,000 document changes (creating, changing or deleting documents) are accrued between two delta extractions for the application in question. A (considerably) larger number of LUWs in the BW delta queue can result in terminations during extraction.
b) With a future delta initialization, you can ensure that no documents are posted from the start of the recompilation run in R/3 until all delta-init requests have been successfully posted. This applies particularly if, for example, you want to include more organizational units such as another plant or sales organization in the extraction. Stopping the posting of documents always applies to the entire client.
Queued Delta: With this update mode, the extraction data is collected for the affected application instead of being collected in an extraction queue, and can be transferred as usual with the V3 update by means of an updating collective run into the BW delta queue. In doing so, up to 10000 delta extractions of documents for an LUW are compressed for each DataSource into the BW delta queue, depending on the application.
new queued delta
This update method is recommended for the following general criteria:
a) More than 10,000 document changes (creating, changing or deleting a documents) are performed each day for the application in question.
b) In future delta initializations, you must reduce the posting-free phase to executing the recompilation run in R/3. The document postings should be included again when the delta Init requests are posted in BW. Of course, the conditions described above for the update collective run must be taken into account.
Non-serialized V3 Update:With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.
unserialized v3 update
This update method is recommended for the following general criteria:
a) Due to the design of the data targets in BW and for the particular application in question, it is irrelevant whether or not the extraction data is transferred to BW in exactly the same sequence in which the data was generated in R/3.
take a look Roberto's weblog series
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
https://weblogs.sdn.sap.com/pub/wlg/126 [original link is broken] [original link is broken] [original link is broken]
doc
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
and oss note 505700
Re: delta methods
go throuth the previous thread
Delta types
hope it helps..

Standard SAP program name for the data extraction

Please tell me the stadard SAP program for the data extraction for Material, Vendor and Customer.

you might want to explore tx. SXDA.

Error in the Data Transfer phase

Dear all,
During the Data Transfer phase, we get 117 errors.
The error for each failed process is:
Execution of program /1CADMC/OLC_500000000043327 failed, return code 3
Message no. DMC_RT_MSG046
RC = 3: Error writing the data
I compared the table structures in source and target system, and they are the same.
Therefore I suspect that something went wrong during the Data Selection phase.
Does anyone else have this problem?

Hi Nicolas,
Error code 3 suggests that there was a problem writing data to the receiver system. This may happen due to various reasons (For example: No tablespace available in the target system). To be sure, please check the System Logs (SM21) and Error Logs (ST22).
In oder to check if something went wrong during data selection, you may refer to the selection logs for the tables for which data transfer is aborted.
In case you are not able to identify the issue, kindly open an OSS Message for faster resolution of the problem.
Regards,
Suman

Delta Load Error in the Data Extraction

Similar Messages

Maybe you are looking for