problem with data load

[Former Member]

Hi All,

there are 2 currency types B0 and 10

and for B0 currency type we have versions D,Q,Y for daily quarterly and yearly which are are already active and daily deltas are loading for this versions  from 2001 to till date

Now we have a new requirement to add the versions A,B,C(daily,quarterly,annually) for the other currency type 10 from 2001 to till date

When i try to Initialize the data(INIT with Data Transfer)  for the new versions A,B,C from 2001 till date it says INIT is not possible and i am unable to load the data

kindly help me, how should i load the new versions for the 10 currency type..

its an urgent issue, please respond ASAP...

thank you very much

[Former Member · Accepted solution]

Hi Prince,

As per my understanding of your problem, you can try below procedures:

1. First run a full repair for (A,B,C) from 2001 to till date.

2. Run a delta for (D,Q,Y) data.

3. Delete the existing init (This will not delete existing data)

4. Run an init without data transfer with entire selections(A,B,C,D,Q,Y) and Currency type B0,10 so that the next deltas will pick data for entire selections.

Or

If the data of existing versions is less (D,Q,Y) then delete the existing data and run init with data transfer with entire selections (A,B,C,D,Q,Y) and Currency type B0,10 so that the next deltas will pick data for entire selections.

Remember to delete the existing init flag before starting a new init.

Hope it helps.

Regards,

Vijay

[Former Member · Accepted solution]

Hi Vijay,

Thanks for the update..

but i've a question

1) If you want me to do Full repair for ABC..how can we do that, because these versions A,B,C are new to the BW system, so do you think we can make a full repair w/o initialization?

2) The currency types B0 and 10 aren't included in the selection screen of the IP..so we can't include them, instead, i am restricting in the query designer..so no problem for currency types

thank you

[Former Member · Accepted solution]

Hi Prince,

Fullrepair is nothing but a full load(but marked as "Repair full") which can be performed even without initialization.

As you said you are managing the currency types in query designer, then it is fine.

Regards,

Vijay

[Former Member · Accepted solution]

Hi Vijay,

one more question in between

After running the full repair, you suggested to run delta for the old versions D,Q,Y and run INITI w/o data transfer... so if there are any postings before we make an INIT with data transfer, how shall we retrieve those postings?

thank you

[Former Member · Accepted solution]

Hi Prince,

Run an INIT w/o data transfer immediately after running a delta and it takes very less(hardly a minute) but if you expect postings in that time better to delete all the existing data and run an init with data transfer with entire selections.

Regards,

Vijay

[Former Member · Accepted solution]

Hi,

If you are taking care currency type in your QUERY, I will suggest to delete all data in your cube and load it again with no restriction.

or as Vijay said Run an INIT w/o data inmediately after delta and FULL REPAIR.

Regards.

[Former Member · Accepted solution]

Hii All,

Somehow, Customer isn't convinced with the procedure..

what Customer suggest is to run an INIT with Data Transfer for the selections

a)FISCPER --> 001.2007 to 016.2099

b) VERSION --> A,B,C

But as there is already INITs loaded from 001.2007 to 016.2099, the IP doesn't allow me to go for another INIT with for the same month and for the  Version A,B,C

how shall i fix this problem?

thank you very much

[Former Member · Accepted solution]

Hi Prince,

In that case you have to go for below procedure:

1. First run a full repair for (A,B,C) from 2001 to till date.

2. Run a delta for (D,Q,Y) data.

3. Delete the existing init (This will not delete existing data)

4. Run an init without data transfer with entire selections(A,B,C,D,Q,Y) so that the next deltas will pick data for entire selections.

But if any postings happen in between running the init you may lose them, so you have to plan this at sometime where there will be no postings or if your ODS is "Overwrite", run a full repair for that entire day.

[Former Member · Accepted solution]

Hi Vijay,

Everything is fine except for

1) why should we run INIT w/o for all versions(Point 4), i guess it will suffice if we run for the new versions A,B,C..isn't?

2) the data feeds the cube directly w/o and DSO in b/w... .. so in this case, how shall we check the missing records?

thank you very much

[Former Member · Accepted solution]

Hi Prince,

1. By running init w/o data transfer for all versions, next delta loads will pick data for all versions else you will again get data only for (D,Q,Y).

2. As you are directly loading data to cube, if any postings happen will running init you will definitely lose them.

One questions from my side:

1. Do you expect postings all the day?? (Note that init w/o data transfer takes only 2mins)

Regards,

Vijay

[Former Member · Accepted solution]

Hi Prince,

1. By running init w/o data transfer for all versions, next delta loads will pick data for all versions else you will again get data only for (D,Q,Y).

2. As you are directly loading data to cube, if any postings happen will running init you will definitely lose them.

One questions from my side:

1. Do you expect postings all the day?? (Note that init w/o data transfer takes only 2mins)

Regards,

Vijay

[Former Member · Accepted solution]

Hi Vijay,

yes, i know that INIT w/o data transfer will take less than a min...

but the problem is that the users are all over the world and we never know, its a hypothetical scenario to conclude

At the other point, why is it necessary to run INIT w/o data transfer for all the versions, because, when we run INIT w/o data transfer with the selections for A.B.C , they will be included automatically in the delta Ip along with the existing D,Q,Y... it is where i''ve lil confusion...isn't it? are sure about this.. cos, we dont have a dev system.. thts the pblm

thanks for all your prompt responses

[Former Member · Accepted solution]

Hi Prince,

Regarding init when you run a new init for A,B,C they will not include automatically to the existing D,Q,Y rather it will replace the existing init. So you should run init for whole versions and about loading old data for A,B,C.

Hope your confusion is cleared now regarding init.

And about the postings that occur while running init, as you are loading data directly to cube you can go for reconciliation, Go through the below doc for reconciliation procedure:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0931642-1805-2e10-01ad-a4fbec846...

In the meantime i'll try to find out a better solution if possible.

Regards,

Vijay

[Former Member · Accepted solution]

Hi Prince,

The only option you are left with is locking the systems from users which will avoid postings and continue your activity. You can do this during weekends(Non-business hours).

Going for reconciliation will become an extra work too.

If your data source is LIS then we could've stopped them from reaching delta queue but it is not possible in your case.

Regards,

Vijay

[Former Member]

Hi,

I did not understood clearly, but where are you loading please specify source & target, If init is already made then go to Menu option in infopackage and make Initialisation option for source system and delete inti selection and rerun again.

Thanks & Regards

Deepak Chavan.

[Former Member]

Hi Deepak,

Sorry,

am loading the data from R/3 to Cube

Now.. my question is, if i delete the INIT, the existing data for the other Planned Versions will also be deleted..

What i want is the new versions A,B,C should also exists along with the existing versions D,Q,Y

Because these versions are different for both Currency Types..i hope you understand

thanks for your quick reply

[Former Member]

Hi All,

Any inputs from your side, how to proceed with the data load in in this scenario

thank you very much