Delta on generic extractor based on functional module

[Former Member]

Hi Experts,

I have created a generic exctractor using functional module.

Data is coming from following tables:

PRPS

COEP

COBK

EKBE

EKPO

BKPF

BSEG

COSS

Key figures are coming from COEP, BSEG and COSS.

- I need to setup delta now, I do have a time stemp field in COEP, should I use it?

- What code I need to put in the functional module in order to setup delta

- If I use time stamp from COEP, what will happen if there is change only in BSEG or COSS or any other tables, will it be picked up in delta?

- Instead of delta, is full load another option in this situation?

Please advice.

Thanks.

[Former Member]

Hi,

Before creating generic function module, you can simply create a document in QA system and analyse the timestamp fields whcih are all effected during new document and change document and determine the timestamp fields.

-Jijo

[Former Member]

Hi,

Key figures are coming from COEP, BSEG and COSS.

- I need to setup delta now, I do have a time stemp field in COEP, should I use it?

You can use that field and in your extractor it will be populated automatically based on the last extraction time. You simply need to setup your delta using delta option on tool bar and set this field for delta.

- What code I need to put in the functional module in order to setup delta

Now you have last extraction time in the delta field based on this value you can select data from other tables.

- If I use time stamp from COEP, what will happen if there is change only in BSEG or COSS or any other tables, will it be picked up in delta?

Actually this delta field will have the value of last extraction which will be populated automatically so you can use this field for fetching delta from any table. So simply need to formulate your select statements accordingly and compare the timestamp field of every table with delta time stamp field.

- Instead of delta, is full load another option in this situation?

You can simply use delta option.

Regards,

Durgesh.

[former_member199691]

To add what Durgesh said,

you also need to take care that you pick delta on the basis of change as well. I am not sure if TIMSTMP field in COEP table will be affected by the change in the record or not. Same holds true for other tables as well.

Regards,

Gaurav

[Former Member]

Hi Durgesh,

I try to build a datasource to get the CO doc for sales orders.

So this datasource uses a view based on COEP.

I want it to be in delta, so I'd like to use the timestamp field as a delta-specific field.

However I always get 0 record when I run a delta...

I wonder if it could be because of the timestamp format.

Indeed in COEP this field is formated like '8,346,903,030,000' (data element RKE_HZSTMP, Seconds since 1.1.1990,0:00 GMT * 10000) and not like '20160613192503' (YYYYMMDDHHMMSS).

Could it be the reason of my issue ?

If yes, is there any solution ?

Thank you very much !