Initialization Load for LO Extractor

[Former Member]

Hi,

I am having trouble on missing some documents for specific dates for my LO extractors.

I don't get data for Jan 27 - feb 4, 2015.

This is what I have done:

I have loaded setup table for company code A on Jan 25 then company code B and C on Jan. 26.

But i have deleted the PSA data and have loaded a full init on Feb. 4, 2015. upon checking the data request for Feb 4, 2015 on the PSA, there are no records pulled for Jan. 27 - Feb.4. I do not know why is this happening.

Is this caused of a late full init?

Thanks

[RafkeMagic]

Anne Ong wrote:

This is what I have done:
I have loaded setup table for company code A on Jan 25 then company code B and C on Jan. 26.

If you have not loaded the data from the setup tables (immediately) afterwards, it means that orders for company code A created as of Jan 25 as of the time you started filling the setup tables are "lost" ('cause you haven't done any init yet).

Same reasoning for Jan 26 and company codes B and C.

Anne Ong wrote:

But i have deleted the PSA data and have loaded a full init on Feb. 4, 2015. upon checking the data request for Feb 4, 2015 on the PSA, there are no records pulled for Jan. 27 - Feb.4. I do not know why is this happening.

Why would you start your init more than a week later? You should only do such a thing if you were sure that no sales orders would be created/changed in such a time frame...

You may want to read up on how to initialize a logistics extractor...

[Former Member]

I am not sure on the approach. but I'll have to re-do again the setup table to make it clean and have delta load requested.

is it okay to have the early delta initialization when i have deleted the setup table already?

[RamanKorrapati]

Hi,

Full init - mean init with data transfer? if yes then have you deleted previous init?

Even why you need to do reinit?

If you missed delta data from Jan 27 to Feb 4,2015, you need to fill setup tables for those data and run repair full request with proper selections.

with help of source team you need to find the records which are created/chnaged existing records from jan 27 to feb 4 2015. later you can fill setup tables on possible selections. After that you can use same selections at info pack level which can pulls only missed data.

Thanks

[Former Member]

Hi Mr. Korrapati,

Yes, it is init with data transfer and i have already deleted the previous init.

But when running a setup table, there is no date restriction for setting up the table. do you mean the document numbers?

Thanks

[RamanKorrapati]

Hi,

Yes.

but why you thought to do reinit to get missed records?

thats not the process to recover the missing records.

Missed delta records can be loaded thru repair full request without disturbing existing delta.

First with help of source team find ther doc numbers which are created/changed between jan 27 to feb 4, 2015.

Ddelete and refil setup tables.Later fill setup tables by using doc number selections.

After that if delta exist tehn run repair full request with same selections which used to fill.

Comng to your steps:

You filled setup tables based on comp code a,b and c. Is those comp codes have new or changed records between jan 27 to feb?

Even all doc numbers have been part of your comp codes?

first theoritically think about how to fill setup tables which can have your missed records only. later check setup tables data at NPRO or SE11. once you got what you need, later load them into bw.

Thanks

[Former Member]

Ok, but this mean I will delete the setup table so all the data in setup table will be deleted? and i need to do a full initialization of setup table again?

[RamanKorrapati]

Delete setup tables and refill it.later check what data setup tables have.

later you can load them into bw.

setup tables - You need to fill the records which you need. use possible selections.

[Former Member]

I have read an option of doing early delta initialization. is it safer to have this? then when will I schedule the job in LBWE? is it before or after loading the infopackage?

[RamanKorrapati]

Early delta was not useful in your case.

Early delta was usrful when we do first time load without down time.

But your case is missing delta records.

First lets find missed records. later apply possible selections fill setup tables and load them into bw.

[Former Member]

I see, but I can do re-initilization of setup table since there's little data in the system. will this be more accurate than filling the missing records?

[RamanKorrapati]

if you have less data  and client will accept to lock ecc system for a while then delete(think twice and do this activity) your data at cube(if have less data) and data source levels which feeds data from your data source.

Lock ecc system.

Later delete and fill setup tables without selections.

run full load info pack.

now run info pack init without data transfer(if any init exist, delete init and later do reinit)

unlock ecc systems.

continue your delta loads further. please check about V3 update as well.

That will be clear and up to date data you will get into bw.