LO extraction fails and enabling the delta queue back to capture the delta

[Former Member]

Hi All,

We have the BI system and the LO extractions have been done 6 months back and all the data is in BI now for 2lis_02_itm (Purchase order line items). Right now, we have a requirement for few enhancement fields in the 2lis_02_itm and hence after the enhancement we need to perform the LO extraction again.

As the LO extraction must be done in a down time and as it takes a longer hours, in a worst case scenario if the set up table is not filled by the stated down time, we might need to stop it and make sure there is no impact to the existing data in BI.

In case if the set up table extraction is partial, and if we delete the setup table and do a INIT without data transfer, will the changes to PO after the init will be captured and go in to BI system without any problems. In this case we will not able to get our new enhancements but just make sure we do not cause any impact to the existing system which is up and running. As the existing data will still remain in BW side and we can get the changed data in the delta queue after the down time...?

Kindly help to answer this as this blocks my mind!!

[Former Member]

Are you able to check with LO-Functional colleagues to see how you can reduce the subset of data for downtime i.e. records which can be changed? If so consider these as part of the downtime and subset again since each subset will use one background process

Therefore:

1. Set of data which can be changed Set A for example within doc/posting date range eg. current posting period/month - 2

2. Break Set A if possible into subsets for example Sets B - D

3. All non changing data sets subset these for example Sets E - K

When Sets A - D are complete you can open the system

Ideally carry out the init w/o data once sets A - D complete to avoid any missing docs if a collection run takes place

You can bring all sets as Full repair loads