2LIS_02_ITM and FULL extraction

[Former Member]

Good morning,

I have a question regarding the full mechanism for 2LIS_02_ITM extractor. Does it extract data directly from source tables (EKPO / EKKO ) or from setup tables? I expect that a full load execute a query on EKPO/EKKO.

Thank you for support!

Luca

[RamanKorrapati · Accepted solution]

Hi,

All LO(starts name with 2LIS_*) data sources load data from set up tables only in case of Full load or repiar full load.

in delta load it pulls data from SM13/LBWQ -->RSA7--> PSA(BW).

With google help please explore more about LO Extraction.

Thanks

[Former Member · Accepted solution]

Hi Ramanjaneyulu,

thank you for your answer. I am checking different threads about it, my doubt is:

After deleting setup tables and filling again, if I want to proceed with a daily full load do I have to:

• schedule a delta job R/3 side? (lbwe/job control...)
• launch a infopackage with "init without data transfer"?
  

Thank you.

[RamanKorrapati · Accepted solution]

Hi,

Full load will be loaded only once. not daily.

Daily purpose we handle delta loads.

See without missing or duplicating record we have to follow like below.

Assumed as data flow was designed.

1. Lock ECC system

2. Delete and fill setup tables.

3. Run full load info pack and load full data into PSA and then into bw targets.

4. Run info pack init without data transfer.

5. Set delta pointer.

6. Schedule V3 job control

7. un lock ecc system.

8.Schedule Delta info pack as per needs.

Thanks

[Former Member · Accepted solution]

Hi,

thank you a lot for your help. I have one last doubt:

3. Run full load info pack and load full data into PSA and then into bw targets.

Is possible, in this step, to avoid the BW targets load? To clarify, can I do:

1....

2....

3. Run full load info pack and load full data into PSA

4. Run info pack init without data transfer into PSA

5.....

6....

7....

8....

And after it, I define a DTP that takes all data from PSA and full load into DSO ? The delta mechanism will be active from R/3 to PSA, and then I do a FULL DTP upload into data target.

Thank you.

[RamanKorrapati · Accepted solution]

Yes, that's also fine.Mine motto is to have all full load upto PSA.

From PSA we can handle as we need. that's not an issue.

Your steps also good. No issues.

[former_member202718 · Accepted solution]

Hi Mare,

how many records do you have in PRD..and how have you planned to load the Data.Do you have the DOc numbers in Excel sheet..so that you can load them using Set up table and Do a full load.

When you start Init Delta without Data load then be sure that you lock the users in ECC during..esp  your last set of Load....Else you will end up messing the PO Doc Numbers..

Rgds

SVU

[former_member202718 · Accepted solution]

Hi Luca,

The 2LIS_02_ITM is from EKPO table..but the Data for Full Load comes from Set up table..the set up table has to be filled manually.. the PO Flow to BW is this way,

ME23N->EKPO table

further the Delta will come from

ME23N->LBWQ->RSA7->PSA->DSO->CUBE->Query.

rgds

SVU

[Former Member · Accepted solution]

Yes, I agree with this approach, because there is always the chance to recover a loading from psa without impacts on source system. If I set "Direct Delta" in extractors, "schedule V3 job control" should be avoided, is it true?

I read that Direct Delta can be used with no high data volumes, and it should be better because there is no need to monitor V3 job.

Thanks,

Luca

[RamanKorrapati · Accepted solution]

Monitoring is not required. just schedule them frequently those will be updated data to RSA7.

But SAP preferred one is Queue delta.

If your delta volume will be less then you can direct delta. But it may impacts ECC system.