Generic Delta on RSO2 to populate new & past updated record

[former_member646598]

Dear Experts,

I need to create a data source from the z table with delta extraction. I have a BADAT field representative for a date, but the questions are how to populate the past records that had been changed. For example, if today is 29 September and there is a change on 20 September, how I can populate it? Because what I know if using generic delta with the BADAT field and I select the calendar day radio button it only populates the current record.

Below is the field structure from my table,

Thanks,

Jo

[sdsunny372 · Accepted solution]

Hi Johanes,

You have select the calendar day radio button and generic delta with the BADAT field it's correct.

In addition you need to do below setting in same window where you have selected Calender day radio button.

Safety Interval Lower Limit = 2.

After that you need to initialize delta in SAP BW system for related data source.By doing so every day ,current day and previous 2 days data(newly created and changed data) will be automatically store in that data source's Delta queue in ECC/S4 system.

So when you trigger delta load in BW ,it will get all the records which are there in delta queue.

FYI: Delta load should be done in daily basis after delta initialization to get updated/inserted records into your into your target info provider of BW system.

Best regards,

Sagarkumar Darji

SAP BW Consultant

Organization: Stridely solutions

[former_member646598 · Accepted solution]

Hi Sargakumar,

Thanks for your answer and explanation.

Why i need to pick safety interval lower level to 2?

Anyway is it possible to create delta based on PO Doc Number? If it possible then how?

Regards,

Johanes

[sdsunny372]

Hi Johanses,

Answer of your 1st question:-

1st question:-

Why i need to pick safety interval lower level to 2 ?

Answer:

Safety Intervals are used to avoid data inconsistency.

Reason behind safety interval lower limit 2 is to get today's and 2 days back data based on selected date field.

Example:-

Safety interval lower limit = 2. (Leave upper limit blank)

Already delta initialized.

Load delta update today 10/02/2020 - In delta it will fetch data for 10/02/2020 ,10/01/2020 and 09/30/2020 (because safety interval lower limit is set to 2 ).

By doing so you never miss delta records based on selected date field even if sometime you delta load get failed.

Note: This thing also get achieve by upper limit but I suggest to use lower limit as per my experience.

If you use lower limit, it results in duplicate records. So you should not load this data directly from Data source to Info Cube. It is mandatory to use DSO in your data flow and then load the data to Info Cube.

Now coming to your 2nd question:-

2nd question:-

Anyway is it possible to create delta based on PO Doc Number? If it possible then how?

Answer:

PO Number on the PO Header table (EKKO- EBELN) would be considered a potential Numeric Pointer for generic delta, even though it has been defined as a character (data type of C or CHAR) of 10-bytes because it contains all numeric data. This type of generic delta can only be used for new records. It will not be able to determine if changes have been made to an existing Number Pointer field.

So ,yes based on PO number-Numeric pointer you will get delta records for only newly created PO but thn what about changed PO number? - You will miss those records.

Based on table's functionality ,we need to choose delta field.

If you are looking for PO related data ,I suggest to use standard LO Extractor,which is having standard delta functionality ,so you need to define delta field.

Here are some standard LO Extractor for purchasing.

2LIS_02_HDR - PO Header data .

2LIS_02_ITM - PO Item Data.

2lis_02_SCL - PO Schedule line item data.

Have a fantastic friday.

Best regards,

Sagarkumar Darji | Stridely solutions.