cancel
Showing results for 
Search instead for 
Did you mean: 

Recover Green Delta 2LIS_02_SCL

Former Member
0 Kudos

Hi Gurus,

We have ODS Purcashing which delta update from 2LIS_02_SCL.

unfortunetly, we got some serious problem. lets say:

1. a repeat delta request has succesfull dan QM status already set to green but it is not activated yet.

    it brings whole 6 days data. around 40.000 records.

2. by accidently, this green delta request has been deleted without making to the red status in QM.

3. in PSA, the data was deleted too.

4. in source system RSA7, as we know delta repetition is missing the 6 days delta which is

    around 40.000 before and changed into new delta today which only around 2.000 records.

5. looking for other chance, we go to RSMO and hope that change the green status to red

    will bring the lost delta to BW (keep in mind that no data in PSA again)

6. then we check in RSA7, but it still show 2.000 records, we try to pull delta using info package

    but it still have 2.000 records.

we already search over the forums and some ppl said that we must do full repair request.

now, my question is, could we recover the whole 6 days data again without doing full repair request?

I also wondering if we fill the delta in RSA7 again then do repeat delta request to BW?

we believe your oppinion / suggestion will help us alot, Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

As the delta request was turned green once, hence the source system assumes that the delta successfully reached BW and deletes the previous 6 days data and started bringing new delta.

It is better to perform the repair full request for the missing period and let the regular delta run.

Repeat delta will not solve your problem.

Former Member
0 Kudos

Hi Yashuba,

Thanks for your fast response,

yes,now we trying to get the exact period of missing 6days and plan to full repair.

i think thats the only way :

1. we plan to fill table 2LIS_02_SCL in source system RSA3.

2. extract data by using full update info package to ODS purcashing (dummy)

    its is like another ODS that support full update before the entry go up to ODS purcashing.

is that the correct step?

Former Member
0 Kudos

Yes you are correct.. Delete the setup table. Fill setup table with the missing entries in source system. Then you can check your data in RSA3 using full update.

This data can be loaded to the ODS by full update.

Once the data comes in, you can validate if all the required data is available in BW or not.

Former Member
0 Kudos

Hi Yashuba,

Again, thanks for your fast response,

yes, we're found to fill setup table is using TCode OLI3BW,

on the other hand, in our ODS, selection for document date is always

set to 01.01.2011 - 31.12.9999. which makes we cant use this criteria to fill the setup tables.

ideally, to fill table with the whole 6days data, it must be pull by something like

'changed on date', but I found the selection in OLI3BW is only permitted for doc. date.

this lead us to another stuck : how could we full repair then?

please throw some light...

former_member186082
Active Contributor
0 Kudos

Hi

Identify the Purchasing Docs that were deleted as part of the request. You can fill tables for those Docs and proceed

Hope this helps you

Regards

Chandu

Former Member
0 Kudos

Hi,

While filling the setup table you will get Document Date. You can check the data from EKKO table. Field BEDAT is used for document date, and give the required date which are missing.

Fill setup table and extract the data to BW using an adhoc infopackage. No need of giving any selection. Even if the date selection is 01.01.2011 - 31.12.9999 given, no problem.

If there are some records which will get loaded extra, ODS should overwrite and there will be no duplicate entries

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Chandra,

yes, we're on this step. thanks for giving input.

Hi Yashubha,

Sorry for late reply

anyway, my ODS was schedule line level.

I found some link about this data source:

http://help.sap.com/saphelp_nw04s/helpdata/en/58/f6383fdb800804e10000000a114084/frameset.htm

which tell us that we could check the data from the 2LIS_02_SCL

in EKET (Delivery Schedule Lines) and EKBE (Purchase Order History).

oh y, sorry I mean the range is from 01.01.2001 not 01.01.2011.

this was the real problem which makes the selection

is kinda huge to fill the setup tables.

for one month we could have about 170.000 records.

and lastest delta update still contain doc date from one year ago..

so we're dunno that 6 days data is having doc year from...?

until this step, we're planning to do:

1. still fill setup table for whole doc year 2001-2012,

    maybe we'll update starting from 2012, 2011, 2010,.. 2001.

2. or, could we just check the entry in table EKET/ EKBE,

    and search entry that created&changed in that 6 days range?

    in your opinion, could this will cover the missing data?

Thanks alot

former_member186082
Active Contributor
0 Kudos

Hi Lim,

Go ahead with second option, filling data based of Created&Changed on dates.

Search entries in the range of 8 days, including previous and next day of those 6 days. This will ensure that the data is not missed.

Make sure that ODS has overwrite property.

Regards

Chandu

Former Member
0 Kudos

Hi Chandra,

Thanks for your response,

yes, we trying 2nd option now and see whether the entry

has document date older than 2011.

if not, then we will fill setup tables based on doc date

starting from 2011 - now. Thanks.