Delta-Specific Field for Generic DataSource

[#1]

Hi,

I have defined a Generic DataSource for Transaction data on R/3-Side.

This DataSource is based on View/Table EKKO (Purchasing Document Header) for some specific customer requirements. Delta-Specific Field is AEDAT (Calend. Day). Safety Interval Upper Limit is set 1 Cal. Days. No Safety Interval Lower Limit has been defined. "New Status for Changed Records" has been marked.

When we see this DataSource in Extractor Checker (RSA3), this data source

Extracted all delta data where AEDAT is not blank.

When I see the content of table EKKO, I can find few records where AEDAT is blank.

These records are missing in Extractor Checker.

How I can solve this problem? Which delta-specific field can be used in

this generic Datasource? Should I define an additional Generic DataSource with

Delta-Specific Field BEDAT (as BEDAT is filled when AEDAT is blank in table EKKO)?

Thanks for the answer.

[Former Member · Accepted solution]

Hi,

I checked EKKO table. You should be good with AEDAT as it is Created On "Date on Which Record Was Created". It will be always populated with a date. You should not face any problem. Check with your ECC person why the dates are blank on some Purchasing Document.

Let me know what you find out.

Hope it helps.

Regards,

Tej Trivedi

[moha_nan · Accepted solution]

Hi Tej,

You are right!! There is no problem with table EKKO and field AEDAT.

But we have similar issue with the table EKAB and field AEDAT (changed on).

Do you have some idea here?

Thanks

[Former Member · Accepted solution]

Hi,

In order to capture delta on EKAB table, you will have to create two generic datasource, one having a delta on "BEDAT" i.e. "Purchase Order Date" and other having a delta on "AEDAT" i.e. "Changed On". This is because when a record gets created in this table, "BEDAT" is populated and "AEDAT" is blank. When a change occurs, "AEDAT" is populated. So, your first generic datasource will capture the records created and the second will capture the records changed.

Hope it helps.

Regards,

Tej Trivedi

[Former Member · Accepted solution]

Taj, I am seeing scenario where the AEDAT, BEDAT has never changed, but the record has updated information for KDATE & KDATB.

I am looking for Outline Agreements. I suppose some batch proccess cause this? What is the delta column on this table - EKKO ?

[Former Member]

As AEDAT is delta field it will take up only those records for which AEDAT date is greater that last execution date. Record for which AEDAT is coming blnk for them it is obvious that their date will be 00.00.0000 which can not be greater than any date. hence it is missing those records