ODS to ODS initialization and delta

Hi All BW Gurus,
We have recently started our BW implementation for COPA module and after successfully loading all the historical data, started running into issues with delta loads. Here is the scenario. R/3 --> PSA --> ODS1 --> ODS2/Cubes. Even though ODS1 and ODS2 are exactly the same, the reason for having ODS2 was to restrict drill down reporting to transaction level detail only for the last 6 months of data. The other advantage (I think) was to do a direct update instead of going through all the logic in the start routine again.
R/3 --> PSA --> ODS1 has been succesful so far with the full loads, initialization and delta updates. Full loads from ODS1 to ODS2 and Cubes have been successful too. Once we triggered initialization without data transfer from ODS1, it errors out with a message that ODS2 already has a full update and hence we cannot trigger an initialization. Researching OSS notes, found a note (689964) for the same issue but the solution was to change all full request loads to repair requests and then trigger the initialization. At the same time they mention that we could end up with other issues with this procedure where we might have duplicate records or even loose data if we ever have to run initialization again.
Any one face this issue? Solutions or work arounds?
Thank You.
Shri

Hi Sreedhar,
It would have been simplar to have followed the OSS 689964 by changing the full loads to repair requests. I ve done it in our production boxes and have not faced any issues yet. If an administrator takes good care of his dataloads then why would a question of duplicate records come in to picture.
But since data has been deleted from ODS2 already, you could follow the step1 and step2 as mentioned, it would work. If you see the Selection Criteria completely greyed out, then please right click on the Infopackage and choose the CHANGE option, this will enable the selection criteria for that Infopackage.
But if you ask my suggestion I would advice you to load the ODS2 using Full Loads from ODS1 and then use the OSS to change full to Repair Full, then run an Init Without Data transfer.
Hope this helps.
Thanks and Regards,
Praveen Mathew

Similar Messages

How to catch Delta Initialization and Delta Update in a Function Module

Hi Experts:
I'm developing a FM to extract data from R3. I wonder if anybody knows how to catch when i'm making a delta initialization and a delta update in my FM, because i have different parameters and routines from each one.
Thanks in advanced.
Points for helpfull answers.

Hi,
Keep one dummy date field in the structure. Make this dummy date field as delta enabled field. When you do Init load this date field value will be blank and next time when you do load it will have the last upload (in this case init load) date. You have to write a code before open cursor as below:
      LOOP AT s_s_if-t_select INTO l_s_select.
                              WHERE fieldnm = '(dummy date field name)'.
         l_date = l_s_select-low.
      ENDLOOP.
l_date will have the last upload date. This you can use to select the delta records from the table or for the further processing.
If you want to check the value during Init or delta load, go to RSA3 and debug it(Don't use F - Full load. Use I or D in the update field).
Hope this helps.
PB

Mixed Full and Delta from ODS to Cube

Hi,
we're facing the following problem:
We're loading data from an ODS to a Cube via Delta, every night. Due to reporting needs it's
nessesary we have to write some Infoobject-attributes to the cube.
This attributes will change sometimes. To display the current truth, we have to delete the old
assignments from the cube and update them with the new attribute values.
My idea was the following:
1. Identify the lines in the cube with the old attributes
2. Delete them via "selective deleting"
3. Load the lines with the new attributes from the ODS to the Cube
4. Proceed with delta upload from the ODS.
Is it a possible way or any better ideas.
Kind regards
Lars

Hi,
thanx for your reply. Of course we update the attributes:
For example:
Today Infoobjekt IO (Value IO-Value) has Attribute A with the value B.
Row in Cube: IO-Value, B, Keyfigure.
Tomorrow: Today Infoobjekt IO (Value IO-Value) has Attribute A with the value C.
So I have to correct the value of the attribute in the Cube.
Navigation Attributes can't be used.
Lars

Selective deletion of request from ODS which is activated and updated

Hi all,
I would like to delete the request from ODS which is activated and updated into data targets, i.e if i have three resquests 1,2,3 which are activated and loaded into cube..now i would like to delete the between (2) request from ods, it says we have to delete latest first(3) , cant we delete this 2 nd request by doing some sort of settings plz let me know if any body got come to know this...plz
Many thanks in advance,
BRB

Hi
Did you look at the Online-Docu (link above)? In the administration of the ODS (I think menue 'Manage' in an english environment -> I've none at the moment) where you see each loaded package there you have a button right of the request id (status of data mart). If you press on this a dialog screen appears. There you can press on the trash icon. This resets the delta queue for the specific request.
You have to do this for request 3 and 2. Then you can delete the request nr. 2. The bw system will then delete this request from the active data and from the change log. After this you can schedule the delta load again. This process will load request nr. 3 to the connected InfoCubes.
If you do not reset the delta queue you will not be able to load request nr. 3 from the change log.
As I supose you want not to delete request nr. 3 because of some long duration to upload and activate the whole request again.
This works fine. I've done the last weeks often because we loaded request with 3 million records and more.
Regards,
H.J.

How to create a cube/ods/infoobjects etc..and also why to create the same

Dear Friends
how to create a cube/ods/infoobjects etc..and also why to create the same objects.
thanks & Regards
Ramana

Hi Friend,
Creating Infoobjects
1. Go to RSA1 -> Modelling tab.
2. Click on Infobjects.
3. Create a new Infoarea.
4. Now create Infoobject Catalog for Characterstics and Key Figures.
5. Now create Char Infoobject under Char Catalog and Key figure Infoobject under Key Figure catalog.
Creating Cubes:
1. Right click the info area and choose create info cube.
2. Select the type of cube you wish to create and comnfirm your selections.
3. The next screen is where you actually define the cube.
4. Now you will notice the difference.
5. Place your cursur on key fig and right click and chose infio object direct input; chose your key fig for the cube.
6. Similarly for the dimension; right click the dimension and chose inbfo object direct input, chose your chars and out them in dimension.
7. Activate the cube.
Creating a ODS is also the same.(in step 1 choose create ODS)
Creating Multicube/Multiprovider
1. Right click the info area - chose create multi provider.
2. select the cubes , DSOs, info objects that you need for the multi provider.
3. On the right side of the screen, you will see all the objects that you selected and open the key fig and dimension and drag the ones you need to define the multi provider.
4. Identify the chars and key figs.
5. Acvitate the mullti provider.
Why we create them ?
Infobjects : They are fields in R/3. As we require fields in R/3 tables we require infoobjects in BI.
ODS : This actually is like a table in R/3.
Cube : This contain the Key figures.(e.g Sales quantity, Amount etc)
Hope it helps.
Regards
Hemant Khemani

Update data from ODS to ODS with infopackage selection

Hi,
I am trying to update data from one ODS to another ODS with selection criteria in InfoPackage which is created manually.For Full load I can give selection criteria in InfoPackage. When I initialize data Selection is greyed out even selections for Full load exists. Please advise me how to give selections for delta loads from ODS to ODS loads.
Thanks in advance.
Ram

Once you started an ODS as destination in FULL mode from a DS you cannot get back.
So if you want to update from ODS to ODS using Change Log but considering only some data records you could create an Update Routine with a Start Routine that DELETES undesired records (e.g. DELETE DATA_PACKAGE WHERE ...) and then start an Init-Delta Loading.
Hope it helps
GFV

Initialization of delta loads possible with process chain?

hello all,
followed situation:
i load data from file and sap extractor to ods 1. from this ods i have an automatic delta load to another ods 2, where the data are filtered and aggregated.
its possible that some of the data change their state from filtered out to in but are not in ods 2 because of the earlier criterias they had have. now i want a weekly load (initial load) from ods 1 to ods 2 and a daily delta load if new data arrived ods 1 to the no 2.
i tried to create a process chain for that but i cant! i cannot use the info package for the initialization of the load from ods 1 to 2 because it is generated info package. and if i use the process "update ods object data" there is always tried to make a delta load! at first step i delete all data of ods 2, so i need an initialization with data as next step.
how can i do what i want?
thanks for any idea
Frank

Hello Tom,
ok, i understand but i dont know how...
The only way i know to create an InfoPackage between ODS is to use "Update ODS Data in Data Target" of the context menu of an ODS. Then i chose between full/delta/init load and the infopackage will be generated. How else can i create it?
Frank

Need suggestions in doing my Init and Deltas

Hello Experts,
I am using the standard SALES OVERVIEW cube to store the sales data. I have introduced the custom built ODS to store the order level data in my flows. I am about to test my flows but I am afraid if the custom built ODS in the flows will create any problem while doing deltas as the standard Datasources are designed to update the cube directly.
One more thing is, If I do the init and deltas now for my testing, is it possible to delete all the data from ODS and the cibe and do the init again and start the deltas? Will the custom ODS be a problem in such scenarios? I am assigning the 0RECORDMODE to 0STORNO in the transfer rules.
Rgds,
Nene.
Message was edited by:
Nene BW

Hi
You can test init and delta loads in both the ODS and Cube
You can later on delete all the requests in the ODS and cube if you want to
init again
Assign points if useful
Regards
N Ganesh

Two Extractor logics for full and delta?

Hi,
I have a situation where in the logics for full upload and delta uploads are drastically dfifferent!
What is best way to deal it?
shuould i have two different extractors for full and delta ?
Raj

Hi Raj,
I hope that u are working with the Generic Extractors. If the volume of the posting is too high then u need to restrict the data definitely from R3 side interms of the performance. And u need to maintain the Delta Functionality for the same.
If u cannt maintain the Delta from the R3 side then atleast try to restrict the same from BW side at the infopack level where u can extract the data based on the changed on and created with the two different IP's and update the same to the ODS(here make sure all the objects are with the overwrite).... and then u can maintain the Delta load from ODS to the Cube easily..
If the volume of the data is pretty less then u can use Full load to the ODS and then Delta to the Cube.
Thanks
Hope this helps..

Data load from ods to ods

Hi All,
I have loaded data from ods1 to ods2...its a delta update.
In ods2 the request has failed due to short dump. I deleted the request in ods2 hoping to reconstruct it. But i couldn't find the request in reconstruction tab.
I tried to run the infopack but its not taking the delta.
Please help me out...its urgent
Thanks & Regards
AP

hi,
Reconstruct will only work incase you use pas for loading. By default ods to ods does not have PSA, that is why you cannot reconstruct. your option is to either delete all data in ODS2 and init from ODS1 or reset datamart status in ODS1 and then run normal delta for ods2.
Award points if helpful
Sachin

Record mode from ODS to ODS

Hello All.
We are during a logical partitioning in the system, so we one to have a single ODS to load from R/3 and then sent the deltas to other reginaol ODS. From the Regional ODS we will move the deltas to Regional cube.
My concern is about moving the deltas from the initial ODS to to the Regional ODS´s. Really the Regional ODS should kee the delta record from the initial ODS, but I am wondering if this will work, since the initial ODS will sent an before and after image to the regional ODS, and the regional ODS will do also a delta (before and after) base on the data they have.
Any ideas if this will work fine?
Thanks a lot.

Hello Oscar.
That was my initial thougt, but I don´t want to do that, because of I have to reload data, then I won´t be able to do that.
What I am planning is to delete in the start routine of the update rules the Before Image (recordmode X) records.
What do you think about that?
Regards,
Alfonso.

Delta Initialization vs Delta Update

We're having some issues with performance when loading our GL cube. What I would like to do is perform many delta initializations, each delta inititialization containing one month/period.
My confusion is in the fact that the last time I attempted this, when I subsequently went to run my delta UPDATE the same selection criteria was automatically inserted into my delta update.
So for example my INIT may look like this;
REQUEST1: Selection = 001.2005
REQUEST2: Selection = 002.2005
etc........etc...
REQUEST12: Selection = 012.2005
Next the UPDATE info package seems to inherit the same criteria... doesn't this mean it will not update anything beyond that criteria??
I'm just wondering if it is possible to do an incremental initialization and still be able to enable delta updates for future periods?
Thanks!

Hi Patrick,
The delta update will load the data as per the selections made in the Init run. A delta requested after several initializations, contains the sum of all the successful initial selections as a selection condition. This selection condition can then no longer be changed for the delta.
Take a look here for more info:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/content.htm
Hope this helps...

Delete the initialization of delta on open hub table

HI Gurus
I have loaded data from cube to open hub table using DTP with full update, later on i have loaded the data using a DTP with delta update. Now i am thinking that delta has been initialized on the open hub table, so now want to delete the initialization of delta on the open hub table. It would be great if some one could send me the response.
Thanks
Rohit

Hi Sam,
If I understand you correctly,
You have removed your Initialisation by going InfoPackage --> Scheduler --> Initialization Options for Source --> Removed the Request
Then you did Init without Data Transfer
Then you have the option from init withoout Data transfer to Delta in InfoPackage and Loaded the Data.
Check in the Process Chain the InfoPackage you have mentioned in the selections may pointing towards Init load instead of Delta.
Sudhakar.

Setup table and delta mechanisim

Hi,
Can anyone explain in detail setup table concept in LO extraction and
Delta mechanisim?
Sridhar

Hi
LO Cockpit Step By Step
Here is LO Cockpit Step By Step
LO EXTRACTION
- Go to Transaction LBWE (LO Customizing Cockpit)
1). Select Logistics Application
       SD Sales BW
            Extract Structures
2). Select the desired Extract Structure and deactivate it first.
3). Give the Transport Request number and continue
4). Click on `Maintenance' to maintain such Extract Structure
       Select the fields of your choice and continue
             Maintain DataSource if needed
5). Activate the extract structure
6). Give the Transport Request number and continue
- Next step is to Delete the setup tables
7). Go to T-Code SBIW
8). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 u2013 Sales & Distribution) and Execute
- Now, Fill the Setup tables
9). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Filling the Setup tables
vi. Application-Specific Setup of statistical data
vii. SD Sales Orders u2013 Perform Setup (T-Code OLI7BW)
        Specify a Run Name and time and Date (put future date)
             Execute
- Check the data in Setup tables at RSA3
- Replicate the DataSource
Use of setup tables:
You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
Full loads are always taken from the setup tables
1. Data Flow
Relevant T-Codes
a) Initializtion
LBWE: Maintain Extract Structure, DataSource, Active Status, Job Control, Update Mode
SBIW, then follow tree menu path: Settings for App-Specific DS(PI) -> Logistics -> Managing Extract Structures -> Initialization -> App-Specific Setup of Statistical Data -> Choose XX Application -> Delete/Fill Setup(reconstructing) Table content
RSA3: Check content of setup table
b) Delta upload
SM13: Display update table/Extraction Queue content
RSA7: Display Delta Queue content
Edited by: Tapashi Saha on Jul 24, 2008 7:33 AM

I want to load from two datasources to ODS then ODS to infocube

Hi Experts,
I want to load the data from Two datasources to one ODS.
Once i completed ODS loading i need to load to infocube.
Please anybody tell me what're the steps to complete this task.
Regards
Suresh

Hi,
Once you are done creating the ODSs and InfoCube, create an update rule by right clicking the ODS -> create update rule and there you give your InfoSource1 name and create routines if necessary, likewise you would do the same for your InfoSource2 and load the data...
After successful load from two sources do the samething in Cube, right click on the cube and create update rule but this time you have to mention ODS name instead of InfoSource name. create the routines if necessary then save & activate.
then come out of the cube then go to ODS generate datasource and once it is done again right click on the ODS -> update ods data into targets -> Full / Initial -> InfoPackage will pop up and you are good to go with your load.
Hope that helps!!
~ Vaishnav

ODS to ODS initialization and delta

Similar Messages

Maybe you are looking for