Delta initalization

I am taking a flat file into ODS everytime request is failing in the process chain but i can see the data in PSA. So i did the techinal request to red and deleted the data from PSA and tried the process again but i am getting 2 errors as DATA IS NOT INITALIZED and SOURCE FILE ERROR (dont remember the exact error statement) . when i check i can see the tick marks missing for the delta upload in the ODS , i think i need to do initalization again can anybody please suggest me the approach i am going is the correct way.
Can you please let me know how to do the initalization.
Thanks a lot in advance,
Komal.

Hello Bhanu Gupta,
Thanks for your immediate response... Actually in my process chain there are levels of ODs and CUBES where the data is coming from the flatfile but there are some full and delta loads in the process
depending upon the items, the process is as such that we need to go for delta loads and as i mentioned before i tried to repeat the steps by deleting the request from PSA .I have checked in rsrq and deleted all the before request and loaded the data gain but the same error mentioned above repeats.
thanks,
Komal.

Similar Messages

Missing messages or warning in Monitor

Hi,
I am doing delta initilation from R/3 . In monitor the respective Request is turned into yellow. In the detail tab i found something wrong under 'processing' of a specific datapackage. In this step,upto update rules is OK,The remaining things( Upate and Processing end) are in yellow state.
The step by step analysis is given as follows:
It is possible that data packets must be processed manually.
How can i rectify this problem. If i rectify this by manually uploading, should i need to do manually upload by specific package(where the eroor occurs) or should i complete uploading from PSA.
With rgds,
Anil

Hi Tom,
Thank you very for much for immediate reply.
As you said I used the transactions ST22 and SM21. I found that the dead lock was occured on this fact table( at the same time of Excution of delta initalization).
So I have the data in PSA >how can i upload data from PSA to Datatarget. Is it complete loading(manual) of all packets from PSA tree OR package specific manual uploading.
With rgds,
Anil

Some basic clarification

Hi
Can u explain the basic mechanisum of early delta initalization.
Sorry we can not..Please search the forum before posting a thread
Edited by: Pravender on Sep 3, 2010 11:14 AM

Hi,
Early initialisation is not supported by all the datasources. Datasources which support it, for them if you do the early initialisation, then you can unlock all the users for posting while the initialisation is running. Otherwise in case of normal initialisation, you need to keep all users locked till the time initialisation finishes.
1. Initialize Early delta in the BI system.
2. Go and fill setup tables
3. Do a full load to BI
4. Run delta job in BI Info package

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

Deltas are not mooving to Next ODS

Hi,The process chain tirggered job is not updating deltas from one ODS to next ODS.
Please help me to understand this.
Thanks,
Vasu

Check whether u have the proper Initalization has happend from the ODS1 to ODS2.
If not then u need to check for the same from which date that this issue has raised and then underlying data in ODS1. And u need to make sure that the data in ODS1 is available in ODS2 before taking the Init-Without data transfer....
Let us know the details..
thanks

Negative values in report for delta

Hello,
I am getting negative values for service level report metrics in delta loading, intresting thing is metrics is giving correct values for almost all the order but for around 40 order I am getting -ve values in metrics (i am getting -100 % and correct value should be 100 %, it is for around 40 records only for other records I am getting it correctly), If I do the full initalization again it brings me the correct poistive values but again get some -ve values when I run the new delta loads.
Please give your suggestion on comments on this. I will assign point to all the answers and full point to right answer.
if you need any further information pl let me know
Hitesh

Hello Manga, Kedar and Eric,
Thanks for your quick replies,
Manga, I am checking the orders on r/3 how they were processed thanks for your suggestions
Kedar, yes these are custom extractor using 2lis_11_v_ssl and 2lis_11_vaitm going to ods and then to infocube and I am reporting it on infocube. can you please specify in detail what exactly I should check on extracotr side/ do I need to check at first level ODS anthing specific ??
as these metrics calculation are done using RKFs and CKFs in query designer and those all are correct.
Pl advise
Any other suggestions/ comments are most welcome
Note: I have assigned points to all the answers
Hitesh
Message was edited by: Hitesh Asknani
Message was edited by: Hitesh Asknani

2LIS_02_ITM DELTA NOT WORKING

Hi,
I deleted the setup tables in LBWG, I filled up the setup tables again.I set the InfoPackage on Delta after the initial extraction. However the delta is not updating any new records. It has been updating 0 records consistantly for one week. I went ahead and deleted the setup tables in LBWG (2nd time), I filled up the setup tables again (2nd time), suddently it updated almost 30000 more records. How can I set this up so that it will update the records atomatically on a daily basis? so that i dont have to redo these steps again and again.
Thanks

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 on MCHB Table

Hi,
We have a requirement to generate the report on Batch Stocks and Quality Results. We can use the data available in MCHB/MCHBH table and the Quality Results can be extracted using 2LIS_05_QE2 DataSource. If we use the Generic DataSource for MCHB(using View), for the delta we only have the option of using either ERSDA (Created on) or LAEDA (Date of Last Change) field. But we can use ether one of the field ERSDA or LAEDA for the delta.
If some one has already done the delta on MCHB Generic DataSource, could you please share your views. Or, do we need to use the Function Module Extractor instead of using the view on MCHB and there we can use either ERSDA or LAEDA.
Thanks,
MN

Hi Mohan,
We have encountered a similar error but with Equipment extraction. The problem was that we could easily create a datasource based on view but if a new equipment is created then change date remains blank and hence if we create ds based on change date it will not pull the newly created records. On the other hand if we create the datasource based on create date then only new created records were extracted and not the changed records.
Here is how we solved the problem:
1. We created FM based datasource and delta was on change date. Lower saftey limit = 2.
2. In related FM, we do not do anything if he extraction is based on selection or FULL/INIT mode. Meaning when the selection based or FULL/INIT mode extraction was done we did not tamper with the selection criteris.
3. Now when the initalization was done successfully then in Deltas always the selection criteria was 'change date' only. So in code of our FM, we checked if the seleciton criteria is 'change date' then we added one more selection field of 'create date' in the selection. Meaning if selection criteria to FM comes as 'AEDAT" then we also inserted 'ERDAT' with same exact dates as of AEDAT. So considering the safety limit it was a full proof solution.
I think you can do similar solution to your problem.
Thanks
Amit

Master Data Object Delta goes wrong ?

Hello Experts,
Delta for the Master Data Infobject went wrong and we are planning to initalize it. Which is a better idead, delete data from the Master Data Object Or initialze the delta without deleting the data from the Master Data Object.
Thanks,

Hi Sweatha,
If the InfoObject which you are planning to delete data is used in any of the queries, users will have problems if they are running those queries. And, you can not delete the InfoObject data completly if it was used in any InfoCubes. You have to completly delete the data in InfoCubes before you can delete all InfoObject data.
I would simply init again without deleting the data, then activate the InfoObject data. I do not see any problem in doing this.
Thanks
John
Thanks
Gova

K7N2 Delta lock ups

Hi there,
I've got a MSI k7N2 Delta sitting in my PC atm. But with a nasty problem. I have to keep the cpu sitting in it (AMD Barton 3000) underclocked for me to use my PC for more then 40 mins at a time. After that time, it just freezes, and the sound card (not system speaker) emits a nasty high pitched sound. Using a more intensive game, i.e. planetside speeds up the process, somethimes running for a mere 5 mins. To use the pc atm, the cpu is clocked at 1.4Ghz, instead of the over 2ghz it should be at.
Any suggestions anyone?
Specs:
K7N2 Delta
AMD Barton 3000+
512Mb Kingston DDR (on compatibilty list)
ATI Radeon 7500
SB! 128
Antec 400Watt PSU

ok, after some more testing (man i love CS ) it still locks up, but it took longer initially. It now just freezes, with no beeeep from the sound card. It may be temperature related though, as after the intial freeze, it will now only take a few minutes before it does it again. Straight after it freezes I'm getting temperature of around 50 on all monitors.
Ill whip out that TV card and give it a whirl now
p.s. case fans, i think one is in the wrong way, is the spinny side supposed to facing in the case, or out the case? cheers

Error while resetting the delta in ODS (BI 7.0)

Hi all,
I face a problem in delta resetting...need your help... Thanks..
I have an ODS-1 which has target cube1, cube2, cube3....One week back a new target has been added as ODS-2....All complete data from ODS1 has been piped into ODS 2..(Note.. ODS2 has many more inputs from other cubes/ODS too)
NO issues till now....
I found a data problem in ODS-1 which got loaded 15 days back..... I have removed all 15 requests from cube1, cube2 and cube3... Now I am trying to reset the delta in ODS1...
I am getting the following error....Infoprovide ODS2 still contains request... Delete this first....
Since ODS2 has many other data alongwith ODS1... If I try deleting request from ODS2,, I need to clean it totally and redo... I dont want to do this...
Is there any way to disconnect this delta link between ODS1 - ODS2..... So that I will reload the data in ODS1 and populate into all targets...
Let me know your suggestions.... Thanks!
Regards
Ayyappan.V

Is there any way to disconnect this delta link between ODS1 - ODS2..... So that I will reload the data in ODS1 and populate into all targets...
I dont think you can disconnect the link. just delete the requests originating from ODS1 in ODS2 and you can leave all other requests intact that are from other dataproviders and do a reinit.

About delta loading for master data attribute

Hi all,
We have a master data attribute loading failed which is a delta loading. I have to fix this problem but I have two questions:
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
2. Could you please let me know the detailed procedures to perform this delta loading again ?
Thanks a lot

Hi...
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
Look.....for master data.....no need to delete request from the target..........just make the status red.......and repeat the load.....But problem is that master data sometimes does'nt support Repeat delta..........if u repeat......then load will again fail with Update mode R.........in that case u hav to do re-init.......
1) delete the init flag.......(In the IP scheduler >> in the top Scheduler tab >> Initialization option for source system)
2) Init with data transfer(if failed load picks some records)..........otherwise .....init without data transfer.....if the last delta failed picking 0 records.......
3) then Delta.......
2. Could you please let me know the detailed procedures to perform this delta loading again ?
1) Make the QM status red.........to set back the init pointer.......
2) Repeat the load.....
After that.........if again load failed with Update mode R.....
1) delete the init flag.......
2) Init with data transfer(if failed load picks some records)..........otherwise init without data transfer.....
3) then Delta.......
Regards,
Debjani.....

Not getting delta master data after refresh

Hello,
We have just refreshed our QA (BW and R/3) environments from our production environments. It was a synchronized restore. We have done this multiple times in the past and have not run into this problem before.
Everything checks out fine - full master data loads fine, and delta transaction data loads fine, but our master data loads that are deltas retreive no data and produce the following message:
Selection conditions replaced by last init. selection conditions
Message no. RSM1036
Diagnosis
Selection conditions replaced by init. selection conditions.
No new selections can be made when requesting delta data from a 2.0 extractor.
Delta selections are composed of the total quantity of all the selections of all the sucessful init. requests for this DataSource.
I have looked this up here and in OSS. What I have found would indicate that we have multiple inits. However, when I look at the Initialization Options for Source System from within the infopkg, there is only one. Also, RSA7 appears to be fine on R/3.
Is there table or setting that may have been missed or some other place I need to check?
Any ideas or suggestions would be appreciated.
Thanks,
Kelley

Thanks, but I do not understand what exactly to look for in that table. What fields in that table should I check and for what?
I have compared rssdlinit on BW with roosprmsc on R/3 and they match. I have checked other tables too and they look fine.
There was a mistake made when the system was refreshed that may have caused this problem. That would at least explain why we are having this problem now and did not before.
I tested one of our delta master data objects (0material_text). I deleted the init from within the infopkg. Then I ran the infopkg to init with no data transfer. That appeared to work - resulting in 1 record which is normal for an init delta with no data. Then changed material text on R/3 and ran the infopkg with delta update. It still gave the same message that I listed in my first post, and it retrieved 0 records.
Any ideas?
Thanks,
Kelley

View data in Delta Queue (RSA7)

Hi,
We want to see data records available for extraction in delta queue.
Data source is 0CO_OM_NWA_2. In RSA7 it is showing 5 in total column for this datasource. When we select "Diaplay Data Entries (F2) , select update mode Delta and execute it is displaying "List contains no data"
How to view this data ?
Regards
SS

Hi,
Once you schedule the infopackage , it will pick up the data from RSA7 . Afterwards when you check the data in RSA7 by selecting update mode as delta - you won't find any records . but you can see the data in by selecting update mode - delta repetition - execute it. It will show the records which has been already transferred to BW side.
Update mode - repetition , will hold the data until the next delta is successful..
Hope i am clear..
Regards,
Siva.

ODS Delta Process, DataSource and Delta Queue

Hi to all,
loading data from a SAP source system into SAP BW 7.0 via generic 3.x datasource causes problems.
Here is a short description:
The data flow is from a source table using a generic extractor into a target ODS in full update mode.
Update rules should move data from table structure into ODS structure in this way:
Source table structure
CustKey1     Key2
13386          C23
13386          B14
13387          A13
13387          E25
ODS structure
CustKey1     col1     col2
13387          A13     E25
This works pretty well - as long as all records with the same CustKey1 are transfered in the same data package. Data Browser (SE16) shows the situation in ODS-"New data" view (data is not activated):
Request    Data_packet_number     Data_record_number      CustKey1
112           000003                  1.061              0000013386
112           000004                      1              0000013386
112           000004                      2              0000013387
There are two records for CustKey1 0000013386 with
data record 1.061 in data packet 000003   and
data record       1 in data packet 000004.
The obove constellation is the cause for errors in the ODS Delta Queue and subsequent data processing.
I think there may be one solution to solve the problem by changing the Delta Process of the Data Source.
The properties are:
- Record type: Full, delta, before, after images
- Delta type: Delta from delta queue or from extractor
- Serialization: No serialization, serialization of request, serialization of data packages
But how can I change these settings? Transactions RSA2 RSO2 RSO6 RSO8 don't do this.
What is the right delta process to use?
I have tried changing the delta process generating several 3.x datasources with the following delta processes (see table RODELTAM)
- " " (Full-upload)
- AIE
- ADD
Unfortunately with no effect.
Who can help?
Regards
Josef
Edited by: Josef L. on Mar 20, 2009 7:44 PM

hi venkat,
whenever you load a delta from ods to cube , whatever the data changed in ods since last delta will be updated, hence from you case, both req1 and req2 will be loaded to cube.
Assign Points if useful
Ramesh

Delta initalization

Similar Messages

Maybe you are looking for