Delta Missing

hi all,
we r running PCA delta daily background but today we checked the delta records in the infocube, we found no delta , even we checked in the job overview for this..no job was scheduled as a message.
Same problem we r facing for the profit center master data hierarchy ,attr & text
daily loading..it is not loading, same message in the job overview as no job scheduled. y it is not loaded daily . plz give me the solution
regards,
pinky reddy

Hi,
How have you scheduled this data load? Through process chain or direct scheduling of infopackage?? Check if they have not been removed from schedule for any reason.
Sumit

Similar Messages

2LIS_02_ITM delta missing after good receipts

Hi everybody:
We are using 2LIS_02_ITM for extracting purchase order, in some cases, delta changes are not uploading to BW, it seems, when good receipt is posted.
We have found the note
Note 485650 - BW: Missing entries in delta queue after goods receipt.
But this note is for SAP_APPL 4.6 and our version is SAP_APPL 4.7 patcht level 14.
We have no be able to find a note for our release but we think that the poblem should be similar than described in that note, but any other clue is good received.
Thank you.

LBWE -- maintain Lo **** pit
Step by step
Go to RSA6 and check the availability of the data source
if data source is not available then go to RSA5 (all business content object available here) make a copy of the required DS.
RSA6 - check the DS is available or not..
lbwe - lo customising **** pit...
select required fields - hide - inversion...
do statistical setup run
login to bi
replicate DS..
go to info package
do initalization delta (Delta Q will be generated only after a successfull delta initializtion done. when you do the same system will load historical data from setup table after loading from set up table (init delta) delta Q will be get posted with records for all changes/creation which is happening in R/3 (related to MM) through events. )
i suggest you should go for unserialized v3 (store and transffer on demand )
1. V3 Unserealized ---unsort records
Unserialized V3 -> Update Q> (V3 Coll. Run)---> Delta Q
[When a transaction happends those delta will be get posted in Update Q, in order to transfer those record from update Q to Delta Q you should do V3 collective Run, (the process of loading data from update Q to delta Q is known as V3 Collective Run) ]
2. Qued Delta [SAP recommended]--
It will not sort record or stop record while transferring to to delta q but will continue until the whole record finish. it will have the track of failure record
3. Direct Delta --->Delta Q
it will directly post records to delta Q when transaction happends
hope it will help you
binu v. rajan

Delta Missing for Billing Cube

Data goes missing only for 25th dec 08 in Billing cube , rest is available in the cube
Data modeling:
DataSource: 2LIS_13_VDITM & 2LIS_13_VDHDR
Load type : Delta
Target : Infocube
System: BW3.1
Possible solution is to delete the deltas since 25th dec 08 till today and perform repair full request for the concerned period (since target is cube so we have to delete the previous loads to avoid duplicate records)
then,
delete the init
initilize w/o data transfer
schedule the load back to delta
Before going for this method,do we have to delete/fillup setup table in R/3 ??? I dont think so as we are performing full repair load in BW for the given range of date/period...
Guys, lets me know whether i m right or not,,,will it be okay to delete delta loads since 25th till today??
Do u have any better method to get the missing billing data for 25th??

Alok,
1. Delete data in BW for the period from 25th Dec. one doubt is there whether we have to delete all the requests since 25th till date or just to delete 25th data?
2. Dont touch the exisiting init as ait adds unnecessary work
3. Delete the setup table in R3 fisrt (in case thr is some old data)
4. Fill the setup table fro Appl 13 for the date range you have deleted. it will be filled up for missing documents
5. Do a repair full request for this selection. (P.S : Stop the billing delta until you complete this correction) i think we have to borrow help from functional consultant to stop the posting
6. Restart the billing delta
--> Alok, if delta queue getting updated and same time setup also performing while postings happening till current date, chances of same record available in setup table and delta queue.
As you are loading into a cube(addition), after setup tables data loding through repair full, same record may come again via delta(due to new postings). It creates a redundancy of data.
So, as you have problem with one day data on 25th Dec, its better to delete data for that day or for that week and reload by selectively. As you are loding historic data, no postings happens to those records, no need to worry for delta queue. Or
Find out missing records, setup and load. Bit tidious job.... but 100% safe...
P.S: Deleting entire data from 25th onwards and reloading is not a wise decision, as you are loding into a cube.
Hope its Clear
Srini

2LIS_04_P_ARBPL; incorrect Delta; missing personnel number in confirmation

Hi
I'm facing following problem. I made a new setup of LO-extraction 2LIS_04_P_ARBPL just for one order. The order has one operation "10" with one quantitiy confirmation from person "123".
INIT-Load: I get the data correct .
Delta-Load: I get the quantity confirmation correct but without personnel number.
I made a new quantity confirmation for user 123 and operation 10. My delta load books the quantity correct but without personnel number. The field PERNR is initial.
I didnt' found any reason. please help.
regards
Pascal

Mapping errors. Solved on own.

Delta Missing quick help needed

Hi,
Yesterday we have upgaraded the R/3 4.6C to ECC. Upgrade was succesful.
After upgrade without changing the delta setting of the datasource, we loaded the data into R/3 from legacy system. Then BW did not find any delta data, it is bringing 0 records to BW.
How to enable last load as again delta in R/3 and Is there any possibilities to recall the entire data which was posted last day?
Quick answer will be helpful.
Thanks & Regards
Srinivas

Hi,
in general you should always empty all delta tables for doing an upgrade on the source system. Chances are high that the extract structure and with that those tables (mainly LO-extracts) will change and wont be accessible anymore.
You could try to delete that day from your ODS and try a full repair update with the appropriate data. You need to make sure that the other deltas dont delive those again afterwards.

Purchasing Delta Issue

Hello,
We were loading purchasing delta from the extractor 2LIS_02_SCL.
2 Days back there were support pack applied in R/3 and after that we are having failure of a job RMBWV302 and delta extraction to BW have stopped.
RMBWV302 is no longer running on the R/3 side that populates an extraction queue and it gives the error message
"Queue processing started (MCEX02, 100, , 0)
Extraction queue processing started MCEX02 with 27,184 LUWs
ABAP/4 processor: MESSAGE_TYPE_X"
Does anyone know how to fix, or can point me to a resource to get me back on my feet?
Thank you,

Hi,
You should follow the proper process to stop the LIS jobs and empty the delta queue and take the help of Basis in that.
Seems one of the queue was not maintained properly before patch application.
Now you can activate the extract structure for this data source again by activating it in the development system and doing the transports or if in production you have the authorization to do so.
Once done
Do a new initialization again to the target from R/3.
Do a full repair to the target for the days of the delta missed if possible by filling the set up tables before that.
Hope it helps
Thanks
Ajeet

The delta update for the InfoCube ZCUBE is invalidated

Hi BI Experts,
I am working on BW 3.5.
For the datasource 2LIS_13_VDITM there were some requests(deltas) missing for 3 days. So I got all the documents there were missing or not updated in BW. I deleted the setup tables and filled them with the new document numbers.
I did a full repair request from the Infopackage level and the data got updated in ODS.
But the DM Status is missing for all the requests in the ODS.
And the data for the full repair request didnt get updated in the Cube and I got the following error:-
The delta update for the InfoCube ZCUBE is invalidated. The can be due to one of the following:
1. A request, which was already retrieved from the target system, was deleted from the InfoCube.
2. A request, which was not yet retrieved from the target system, was compressed in the InfoCube.
And the following delta was also not successfull.. How can I clear up this mess and ensure smooth flow of deltas. How can I set the DM status.
Thanks
Kumar

Thanks for your reply.
When I did a Full Repair Request on the ODS the data is in the New table and the DM status got reset(vanished). And the following day delta got failed( data for that request did not get updated in ODS and Cube)
How can we bring back the DM Status and make the deltas successfull.
Thanks
Kumar

Data Extraction Approach

Hi ,
I have 2 BW system BW01 and BW02, and source system SS01.
BW 01 connected to Sorce system SS01 and In operation for some years.
Now i need the same SS01 data(Logistics,Financial etc) to be modelled in BW02 which has its own list of source system.
Now 2 approach can be used
1.Connecting BW01 to BW02
2.Connecting BW02 to Source system SS01.
What is the advantage and disadvantage of both the approach?
PS:I know better would be connected to BW system rather than source system but i need all pro's and cons of both approach.
Thanks and Regards,
MuraliManohar

Hi ,
BW2 connected to source system :-
you would have to setup all the data sources in the source system.
The entire flow has to be maintained in BW2, from DWH layer to the Data warehouse Layer.
In addition to setting up these data sources, the master data also has to be extracted to BW2 from source system.
In case of debugging, you would directly compare the values with those in R/3.
BW2 connected to BW1 :-
readily available processed data.
However, recent data in BW2 would be available only after the data is loaded into BW1.
Also, in case of any issues, you would have to debug through 3 layers now. Bw2, the in between BW1 and then the source system. So, analysis of issue will become a little time taking.
Also, any issues with data in BW1, would be replicated in BW2. Which means and discrepancies in BW1(delta misses, double data) would reflect in BW2 and hence the resolution of the issue would be dependent on data correction in BW1.
All said and done, the solution to choose should be decided on the scope of the requirement. In case, the requirement consists of getting all the data from the logistics cockpit, then connection to the source system is recommended. However, if you would need to manipulate and work with smaller sets of data, then data can be fetched from BW1.
The higher the amount of data, the more complex the situation would be.
Best Regards,
Rahul

Process Chain Failed for Perticular day, want to take load from R/3 for day

Hi Experts,
While monitoring the process chain i found that on 16 Nov2010 the schedule got failed then i checked but that was due to rfc connection to R/3 failed then again i repeated the process in RSPCM. But toady in the morning when i was checking i found that for 17 nov scheduled got run successful but when i drilled down on date for 16th data but it was failed for 16. Now please guid me how to bring the data for 16nov from R/3. My process chain contains both Master Data/ Transaction Data and Deltas / Full loads ???

Hi,
As you have mentioned in your post, the process chain for 17th has finished successfully, can you confirm if all the dataload also finished successfully?
If the dataload also has finished successfully, then ther is not much to be done from your side. Pplease note below points
1. For Delta Loads- No need to worry about them. For standard datasources, the system would have automatically fetched all the deltas since your last successful delta load. For generic datasources as well, based on previous delta pointer in RSA7, all the delta records would have got fetched.
2. For full dataloads- Check the selection criteria in your infopackages. If its based on date, then you would have to do dataload again.
The selection criteria for this dataloads should include the dates for 16th & 17th dataload. Everything else should be fine.
Else, if your dataload did not finish succesfully on17th, though the process chain has finished. You need to do below
1. For all the delta loads- Carry out Repeat Delta loads. This would fetch all the deltas missed. After this load, all the deltas would continue to come normally.
2. For full loads, perform same as mentioned in point 2 above.

How to get missing data in Delta's

Hi
I will try to explain the problem, but I am not sure how successful I will be. Here is the scenario. We did fill the setup tables over weekend, but ran the initialization on BW side on Monday evening. It seem when I see the data later, we are missing Monday data in BW, and changes are being picked up for Monday, hence it is showing negative PO values. Is there anyway I can bring only missing day data as repair delta? Any suggestions would be highly appreciated.
Thanks
Pandiri

Hi,
Take a look at OSS note 739863. It has steps to repair Delta data in such situations.
Quite a few discussion happened on this before. One of the interesting discussion is in the link below.
A BW puzzle for you...I'll Award POINTS!
Regards,
Sree
Message was edited by: Sree Damodararaj

Repair request for Delta load? Orders missing in Billing line Items

Hi
I am using BW 3.5; Some Orders are missing in BW for Billing line item reports (2LIS_13_VDITM) according to the users.
The report is based on Cube directly, ODS is not used. I planned to do a repair full request for this month's data so as to get the missing orders.
Could you please advice me on correct procedure to do that? Delta loads runs every day and todays delta is completed.
Thanks and BR
P.B

While it's usually recommended to execute setups during "quiet time", it's not required. Especially in this case. Since you're going to be restricting the setup to only extract a range of Billing Documents that are representative of the dates of data missing (or purely the identified missing documents), there is no need to wait for "quiet time" because you'll pick up the data either in your Full Repair extract or in the delta extract. Depending on how the target InfoProvider for this data is setup (cumulative v. non-cumulative), you may have to look out for duplicate data.
My recommendation would be to run your setup for only those documents that have been identified as missing. That way, you're limiting the amount of data that's required to be extracted to the setup table and then into BW, but also will remove any risk of duplicate data in your target InfoProviders.

Missing V2 records using Unserialized V3 deltas in Logistics

We have been experiencing missing Deltas in our Material Movement transactions feeding BW. This always occurs between 5:30AM and 6:00AM. When we examine the intermediate queues we notice the Deltas are not present in the V2 queue. I have read several articles describing the process by which SAP moves Deltas through its arthitecture in order to get Deltas from ECC all the way to the Delta Queue in BW using the Unserialized V3 update method of extraction. All the articles state very clearly that if the V2 update fails, then the transactions are not going to make it through to the Delta queue - that makes sense.
What none of the articles explain, and what doesn't make sense, is why the V2 updates would fail in the 1st place. So...that is my question - Under what circumstances would the system not complete a V2 update? As a result of messing around with this problem for a couple of weeks and not getting anywhere, we have abandoned the Unserialized V3 Delta process in favor of using the Direct Delta technique. The up side is we will be getting all the Deltas into BW. The down side is that we have not solved our problem - we've only circumvented it, and the next time we attempt to implement the Unserialized V3 update technique, we most likely will go through a similar period of frustration.
I'm NOT looking for info on "where to look". I'm looking for "concepts" - whiy would a V2 udpate fail? If I know the answer to that question, then the answer to "where to look" should be obvious.
Thanks in advance for someone's help.

Hello,
Here are some useful tips (in my opinion) to this problem:
- Refer to transaction SM13 to view the 'V2' requests which aren't made into 'V3' Queue. Choose the status option 'V2 Executed', user as '*" and select the appropriate time. This transaction would provide all the V2 requests which wern't updated. It's also possible to re-post the failed updates using the "Repeat update" option
- Normally there will be a dump recorded to respective failed update and this can be check using the transaction ST22. If you analyze the problem then you might be able to find the root cause of this failure.
We are using the 'Queued' delta method for application '03' and this method is working fine and never missed any documents. May be it's worth checking this update method.
Hope the above tips will help you.
Cheers
Bala Koppuravuri

Missing Delta Records for 2LIS_02_ITM & SCL

Hi Experts,
this is how my problem goes.
i have done my set up table filled on 12th Dec 2010 and from that time onwards the delta were running everyday and filling the DSO and Cube.
Accidently by some others PC in prod all my delta loads and the setup table load is being deleted except yesterday in PSA for these 2 extractors and now because of some change i have to do a full load to DSO.
But as the PSA is emply and have only yesterday's request i have, deleted that one as well and done a Init Delta to it and i found out that only the Set up table is comming now and all the deltas in between are missing.
i have tried a full LOAd to PSA and the result is same.
How can i get those missing delta records from 12th Dec last year till today with out doing another set up table fill or Do i have to have fill the set up table again till today and thats the only way? i will set the delta again after that.
Do we have to have all the user locked for the setup table fill (for Queued Delta type) ? Lot of people says yes you have to and others says no you don't require. i got one white paper and it clearly says no user locking is required. please find the link below. what is the correct way?
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d019f683-eac1-2b10-40a6-cfe48796a4ca?quicklink=index&overridelayout=true]

Hi,
As per my knowledge you want load particular period of data try repair request may issue solve.
Regards
Sivaraju

2LIS_11_VAITM delta extraction missing line items

Group,
I'm having a bit of troubles with the 2LIS_11_VAITM extractor. We've been using this extractor for some time now to do daily delta loads and it seems to work fine 99% of the time, but recently we noticed a few orders here and there from the last 7 months that were missing line items. If a full repair load is done now on these orders, we are able to extract the missing line items. This seems to suggest that for some reason the R3 delta job is not processing these line items or not picking up changes to these line items when they occur. I've found a few notes that seem to apply, but wanted to know if anyone else had this problem before.
This extractor feeds into a custom ODS, but no records should be dropped since there are only straight mappings in the update rules and transfer rules and no start routines used.
Thanks for any help offered!

Hi,
I feel it would be better to check first for these records in PSA table. If the records are there in PSA but not there in ODS . Check the value for the field 0STORNO(ROCANCEL) in all those records.
IF the field ROCANCEL does not has value R or D , then you can think about REPAIR request.
For few more information on REPAIR search the forum.
With rgds,
Anil Kumar Sharma .P

Issue in tRFC - missed delta records

Hi All,
There was a load failure few days ago in BI and we can see entries in tRFC. Mistakenly the request status was set to green in BI and so subsequent loads completed successfully. Now we found that the records are missing in BI. When we try to execute LUWs in tRFC, it gives message in BI monitor screen "request that can not be processed since request properly ended".
Is there a way that we can process the data in tRFC or re-extract data?
Cheers,
Sai

HI,
You can go for Full repair request .
It wont affect your delta.
Just run the Full infopasckage with Full repair request and give the selection criteria.
Hope it is helpful.
Thanks,
Saveen Kumar

Delta Missing

Similar Messages

Maybe you are looking for