Deltas already loaded for request REQU_XXXX init. sele

[Former Member]

Hi friends,

We deleted the BI outbound queues in ECC side.So we identified the missed records and executed in set up table so that the same can be laoded in BI side.

We used existing(that was already used for loading data for first time in BI)  infopackage with option 'Init with data transfer' to load the missed records. However DTP is in delta mode.

Please correct me if I am wrong.

But while I tried to execute the infopackage it showed the message as "Deltas already loaded for request REQU_XXXX init. sele".

So my question is:

1) Is it mandatory to delete previous init request to further use the same infopackage with same selections.

2)Is it possible to create another 'Init' infopackage with the same selections in ' Data selection Tab'. Will it prevent from deleting the previous init request?

3) Is there any effect if we delete the previous init request.

4) Pls suggest if there is any way to upload missed records without deleting the previous init request?

Thanks

Niku

[RamanKorrapati · Accepted solution]

Hi Niku,

You done wrong thing here. we need to load missed delta records thru repair full request only. not with init info pack.

Init info pack - its runs only once, next time onwards delta info pack only.

1. Never touch existing init. as you said to load missed delta records. you need to sue repair full request option from info pack-->scheduler.

2. No and not possible to create init with same selections.

3. mean time if any new records or changing of existing records happens then those will won't be part of your next delta load. so records will be missing

4. Yes, find  missed records, load into psa by using repair full request option. create new info package, go to Scheduler---> repair full request, provider proper selections and load data into bw.

Thanks

[Former Member · Accepted solution]

Hi Raman,

Thanks for your reply.

Just few doubts.

1)What option should the infopackage that needs to be created should be? Is it Full or Delta

2)If the infopackage is full,how to make it delta enabled?

[RamanKorrapati · Accepted solution]

Hi,

1. Create new info pack with full update mode, go to Menu Scheduler--> repair full request.

2. Your delta already running, then why you want make delta again?

see by running repair full request, you existing delta won't be disturbed.

Thanks

[Former Member · Accepted solution]

Hi Raman,

So you mean to say if we run the full load infopackage today, the system will run the delta infopackage the next day..No need of any other setting

[former_member182516 · Accepted solution]

Hi Niku,

You need to create a new IP, from the IP menu go to Scheduler---> repair full request ( tick mark the repair full option).

By doing this your delta will not be disturbed.

As you are not touching you delta IP , from next load on wards it will run as usual.

Imp point to be noted.

Here as you are performing a repair full load inorder to capture the missed delta entries -- you need to do a selective deletion for the selection from IC in order to avoid duplication.

if you have DSO in middle no need to drop the data in DSO as the data get over written here.

[RamanKorrapati · Accepted solution]

Hi,

Why your comparing full and delta.

if your delta was existed, you just run repair full request(as stated above) with proper selections. remaining everything in alright.

Thanks

[Former Member · Accepted solution]

Hi Prashanth,

So if we use full repair there is a chance of duplication in IC .However I am not so comfortable in deleting IC data at PRD environment.

Pls let me know if the alternative(without using full repair) following steps are correct so that there is no duplication in IC.

1.Execute the set up table with few records.

2.Schedule the infopackage with full load(without any repair option).It will pick all the records from set up table

3.Then load those data into BI with delta DTP.

4.Then schedule the delta infopackage and load the data again.This would help to mark the delta pointer.Moreover no need of deletion of previous init requets. 

[RamanKorrapati · Accepted solution]

Hi Niku,

In your case no duplication will happen. because you didn't deleted records at infocube/dso level. you lost records at ecc delta queues.

so no duplication issue. just load thru repair full request once you fill the setup tables thru proper selection.

@ Prashant,

He delete records at ecc side SMQ1/SM13 or LBWQ. so no duplication issue if he reloads those missed delta records.

Thanks

[Former Member · Accepted solution]

Hi Raman,

I am really confused..Pls help me in this regard.

I think duplication will be there for full repair

For example

We missed the records for 05.11.2013.

For some PO suppose 'X' there is a line item 10 with qty field as 30(already existing from before).

On 05.11.2013

Purchase order'X'

Line item 10------Changed with qty field 50(Delta missed)

On 06.11.2013

Purchase Order'X'

Line item 20-----Changed with Price(Picked)

So in this case in

ECC side:

For Line item 10----Qty field is 50

But in BI side

For Line item 10----Qty field is still as 30 with the updated(on 06.11.2013) price.

So when we load the same with IP having full repair it will pick qty '50' for line item 10.

In the IC level it will be (30+50)=80.

So without deleting that PO in IC we cannot proceed

Correct me if I am wrong .

[RamanKorrapati · Accepted solution]

Hi Niku,

If you have change date at info cube level then qty will be won't be added

05.11.2013   ---- 30

06.11.2013 ------50.

Even if you delete the record(30) at cube level, you may get record(50 qty only). because record 30 is not delta record, it was loaded days before.

Once you  fill the setup tables, you need to use proper selections to load data at info pack level.

Example take above scenario:

need selections on PO, changed/posting date, line item,

XYZ(PO)      06.11.2013          50.

like that way you need to find proper selections to load data into bw side. if you choose wrong selections data will miss  match.

Thanks

[Former Member · Accepted solution]

Hi Raman,

Thanks for the reply.

So if we have changed date in IC level, even the characteristic values will be classified on 'changed date' basis.Or the old/missed records(that of 05.11.2011) will overwrite the updated characteristic records(delta for next dys) with same key combination. 

[RamanKorrapati · Accepted solution]

Hi Niku,

DSO -  is overwrite

Cube is additive if all key chars have the same values.

Thanks

[Former Member · Accepted solution]

Hi Raman,

Thanks a lot.

Now I would give the selections in infopackage and load acoordingly.

[former_member182516 · Accepted solution]

@RK: He is talking about delta records,Delta records can be new of existing entry changes...

Lets say if that delta records belongs to the already existing entry changes then at that time there is chance of duplication in IC( here he did not change KFs but he changed some other parameters then there is a chance).

i had considered all other scenarios as he did not mention what data source n what entries is he referring. to be on safer side we need to check in IC before going for repair full.

Even if he deleted Queues in ECC there is a chance ...

[former_member182516]

1) Is it mandatory to delete previous init request to further use the same infopackage with same selections.

--> If you delete the existing init , you will lose delta pointer. In your case you are trying to load the missed delta records create a new infopackage with Repair full and load the data.

2)Is it possible to create another 'Init' infopackage with the same selections in ' Data selection Tab'. Will it prevent from deleting the previous init request?

--> Its not possible to create INIT with same selections. you can create once more init with different selections.

3) Is there any effect if we delete the previous init request.

--> yes definitely, if you delete the previous init you will loose the delta pointer.

if you delete the old init request and now you are trying to create a INIT with the current selection then you won't get the delta entries for the other selection for which entries might get created in this mean time.

4) Pls suggest if there is any way to upload missed records without deleting the previous init request?

The only way to load the missed entries is to create a new IP with repair full set.

This will not distrub the delta pointer. from next load on wards your delta IP can be used as it is.

Here as you are performing a repair full load inorder to capture the missed delta entries -- you need to do a selective deletion for the selection from IC in order to avoid duplication.

Regards

KP