'init load' & 'full load'??

[Former Member]

Hi all,

Can anyone correct this if i am wrong?

--My question is that I need to delete 'init load' & re-load it with 'full load' and then create the 'process chain' to transfer data periodically after I loaded data first time with 'init load' and the data was tested, right?

--If not, what it is after I loaded data successfully with 'init load' in the first time?

--Do I always need to use 'init load' for first time data load? If not, what is the situation that I need to use 'full load' for the first time data load?

Thank you

[Former Member · Accepted solution]

U cannt use an Init load as a load in the Process chain. As u have deltas in ur requirement, then u have to do either Full upadte and then do the init with out data transfer or u can do the Initilization. Once this step has finished then u can include the delta load as a load process in ur Process chain. then only it will work.

u shud not include any init load infopackages in the process chain..

Hope it helps.

Regards-

MM

[Former Member · Accepted solution]

Hi MM,

Thank you. But my first load was 'full load', I used the 'full load' infopackage to run the process chain and got an error message. I am wondering if it is the problem to cause the error because I ran the 'full load' instead of 'init load' for the first tiem data load. Thank you for help.

[Former Member · Accepted solution]

Hi John,

The black line that you see between the start process and the load is not an issue. That line is always black. Doing a full load through the process chian is not an issue at all. There must be somethign else...what is the message if you check the chain?

[Former Member · Accepted solution]

Hi Bhanu,

For the processing option, I chose 'PSA and then intodata targets (package by package). <b>I intend to load data into ODS and then load from ODS into Cube.</b>

For the data targets, I only chose the 'ODS'. Do I also need to choose the Cube in this tab?

The error message is 'the request xxxxxx is still not uptdated in any infocube.

Thank you

[Former Member · Accepted solution]

John,

You need to check if updates rules are maintained from the ODS to the Cube. If you are loading to ODS and then from ODS to cube, you cannot choose the cube and ODS in the same InfoPackage. Either use another infopackage from ODS to Cube or use the further update process type.

Hope this helps...

[Former Member · Accepted solution]

Hi Bhanu,

Thank you.

Yes, the updates rules is from the ODS to the Cube. I used "update ODS data in Data Target" but I cannot find any information about it. (because the error shows: it cannot load into the cube)

I would like to re-load from the ODS to the Cube by using "generate export datasource". If so, I am wondering if i need to delete the 'update rule' before I re-load it again? I try not to affect BW too much by re-loading.

Thank you.

[Former Member · Accepted solution]

Even if your ODS is set to update into further data target, if you are using a process chain, you need to use the process for further update, else it will not be loaded in to the cube.

Sames goes for the PSA and Subsequent update option in the Infopackage. Even though you have checked this option, you will need a separate Update from PSA method in the process chain. The process chain needs each step to be spelt out clearly.

There is no harm in regenerating the Export DataSource, just check that the update rules are active before attempting the load.

Hope this helps...

[Former Member · Accepted solution]

Bhanu,

According to your information, I found that in the ODS dataflow I see the dataflow including the cube but i didnt' see the cube included in the planning view. Did I miss somthing here? If so, can you point out the steps for loading ODS data into the Cube periodlically?

Thank you

[Former Member · Accepted solution]

The method I usually follow makes my process chain look like this:

Start > InfoPackage to Load to ODS (on the Processing tab in the infopackage choose the first or second option, not the third one) > Process to Activate the ODS data > InfoPackage to load from ODS to Cube.

These InfoPackages load the delta data and scheduled to run once a day.

Hope this helps...

[Former Member · Accepted solution]

Bhanu,

Here is my planning view: start -> Load data-> ODS data (activated)-> futher processing(generated from ODS) I missed from the ODS to the Cube.

I need help to setup the dataload from ODS to the cube. I alread created the updates rules for the cube and ran the "update ODS data in data target". I don't know what else i need to do to make it work. Thank you.

[Former Member · Accepted solution]

What did you maintain in the variant for the Update ODS data (further update) process?

[Former Member · Accepted solution]

Bhanu,

It is 'generated from ODSACTIVAT ZPAK_XXXXXXXXXX. I saw one option- avtivate_all_ODS. Do I need to use that one or create one.

[Former Member · Accepted solution]

Bhanu,

I am not sure if this will help you to find a clue. I deleted the process chain and try to create new one. It shows "<b>invalid TID passed:monitoring contenxt not found in the System BWP</b>.

[Former Member · Accepted solution]

Just log out and log in again and then try to create the new chain...the message is not really relevant to our case.

[Former Member · Accepted solution]

Hi Bhanu,

I re-created the process chain again. I got an error message: infoObject* is inconsistent when I double click on the "further processing". Any clue? Thank you

[Former Member · Accepted solution]

Any details on this error message?

[Former Member · Accepted solution]

Bhanu,

Do I have to transport the 'further process'(process maintenance-updata ODS Object Data)? Thank you.

[Former Member · Accepted solution]

Transport..? Is the process chain working now, and you want to transport it?

[Former Member · Accepted solution]

Bhanu,

Is there any way that I can check if my process chain works after I create it? I usually know when I check PSA next day.

For the process chain, I used 'check' buttom and it shows OK. Then I activated it.

[Former Member · Accepted solution]

Yes you can certainly do that. Set the Start Variant to Run Immediate. Save and then Activate and Schedule it. It will start running immediately and then you can take a look at the logs to see its progress.

Hope this helps...

[Former Member · Accepted solution]

Bhanu,

Thank you for sharing your knowledge with a new man in this area.

Yes, I looked at the log and I saw it shows that I activated it in the specific time. But I cannot find any information regarding if is loading successfully. Last time I found the loading unsuccessfully <b>in the infopackage with yellow warning sign on when I went to PSA.</b> (that is how I found it didn't load into the Cube). Thank you.

[Former Member · Accepted solution]

So what does the message in the monitor details tab show?

[Former Member · Accepted solution]

Hi Bhanu,

Tahnk you for all the help. I found that I omit one process which you mentioned (the process between the ODS and the Cube). I am going to give it a try again. However, I have another problem before I work on the process chain. I am going to post this question online. Please help, you know the solution.

I reward you for sharing your experience.

Thank you

[Former Member]

Hi john..

I think you guys are confused with init/delta load and full loads. Lte me try to clear the concept.

There are two kinds of loads.

1. Delta.

In case of delta, first load should be a init, which tells the source system to keep the track of changes/new records in order to send only these changed/ new records into BW which flows as delta.

2. Full

In this case ererytime all the records will flow into BW system so init is not required.

So in your case, the answer is :once you have loaded the full data, now u want to get back to delta, you have an option called init without data transfer in which no data is transfered into BW as all the records have come in full update but still u can go ahead with delta. So after your full load run init without data transfer and your system will be ready for delta.

for the second case : Init loads is only once takes place. So first time you run init and then you put your delta infopackage into process chain and it will run successfully.

Third : once you have done an init, there is no need for full. Delta infopackage has to be designed and should be used in further process chains.

Hoep i have cleared some points. If u feel ur further confused, post it. Once again ill try to clear

Sriram

[Former Member]

Hi Sriram,

Thank you for contributing your experience. According to your information, no matter what method (full load/ init load) I used for the fist time dataload, I can use that infopackage (I created for the first time dataload )to run the process chain without creating another infopackage. If I am wrong, please correct me. If not, please explain it. Thanks

[Former Member]

Hi John,

If the first time load was an Init, then your InfoPackage would have this option selected. If you include this in a process chain then it will not work, because you would not want to do another init (anyway you will not be able to do another init without deleting the previous one).

If the first time load was a full load and you include this InfoPackage in the process chain, then each load would be a full load. You need to see what the objective is.

If however you have done an Init, you can change the <i>same</i> InfoPackage to choose the delta option and include it in a process chain.

Hope this helps...

[Former Member]

Hi Bhanu,

Thank you for the information. I'm worndering if you can help me to solve this issue.

--I used 'full load' infopackage to run the process chain but I got an error message: processing chain error occurred- transactional data load. <b>The line color (the link) between "start" and "load data" is black in the planning view.</b> Do you know what is the problem?

--The above process chain didn't work so I tried to create the 'init load' and and run the process chain with 'delta load' but it didn't allow me to run the 'init load' infopackage. Do I need to delete the 'full load' infopackage with uning the process chain unsuccessful before I run the 'init load' infopackage? Do you know why?

Thank you for help

[salnuaimi]

Nicely described. thanks

[Former Member]

Hi John,

No. First you initialize the delta load. From there on you do a delta load only. Its like this. When you do a initialize delta load it is like a full load i.e it loads into the Data Target all the data for the datasource. The difference being the initialization load which will have additional settings to take care of the delta loads. So when you do a delta load only the changed/updated records are extracted into BW. Hope I have made things clear.

Bye

Dinesh

[Former Member]

John,

Dinesh's second answer tells in detail. dinesh, could you please write some of the steps how do you set up on process chain. i would really appreciate it

thanks

JR

[Former Member]

Hi Dinesh,

Thank you for the information. But I need to know

-- <b>Is is ok that I used 'full load' in the first dataload to test data or it is necessary to delete it and re-create 'init load' after I already used 'full load'</b>. Will it caurse any errors to crated the 'process chain'?

--If I want to create the process chain for the 'init load' infopackage, do I need to crated 'delta load' infopackage? (Some said: 'delta load' has to be done after 'init load')

--After I created 'init load' to test data in the infopackage for one ODS, do I need to create 'delta load' or 'full load' infopackage for it?

Thank you

[Former Member]

Hi John,

Ideally you would do an "Init" load and then delta loads from there on. So as part of the Process Chain you would have the delta load step.

Full load is generally used for data sources which are not delta enabled.

Bye

Dinesh

[Former Member]

Hi Dinesh,

Do you suggest that I need to use 'initialize dalta process' first and delte it and then use 'delta update' to load from the infosource to data target again in the 'update mode' of the infopackage? If I am wrong, please correct me. Thank you.