0CA_TS_IS_1 - No Delta Update

[Former Member]

I have been working with this extractor for the last couple of weeks, I have reviewed notes and forums and still do not have delta's coming through the extractor as it should. I am about to post an OSS Note to SAP but I wanted to check and see if anyone new how this extractor works and why I am not retrieving data.

We are on SAP 3.5 and our R3 system is ECC 6.0, we have completed entry of the reporting time types and have pulled an initial. We are not enhancing, just using standard content, do you still have to setup the Badi? How long is the Safety Interval for pulling data? We entered data a week ago and I did not actually get it until yesterday from this extractor.

Thank you for any assitance you can give.

Caroline

[Former Member · Accepted solution]

Delta Update

When transferring time sheet data to the Business Information Warehouse (BW), you must note the connection between the following data sources:

· CA_TS_IS_1 (Time Sheet Data (Approved))

Documents are written in the SAP R/3 system for Time Sheets with status 30 (approved). The documents log the changes that have been made to data records.

Therefore, the SAP R/3 system can perform a delta update for this data source. The system only transfers newly approved data records and changes that have been made to existing data records. At the same time, the SAP R/3 system notes the date of the last delta transfer.

Linking DataSources

During the complete transfer of data records that have been released for approval, the system performs the following steps:

1. Determines the time of the last delta transfer of approved data records.

2. Transfers data records that have been released for approval if the last changed on date is further in the past than the determined date.

The system performs the following steps whilst transferring data records that have been changed in the source system after the transfer to the Business Information Warehouse:

...

1. Determines data records that were transferred as approved data records during the last delta transfer, but that have since been changed in the source system and released.

Note

By changing data records in the source system, two new data records have been created. One data record with status 20 (released for approval) and one data record with status 50 (changed after approval).

2. Transfers the data record with status 50 with a negative sign to the BW so that the data record that was originally transferred is deleted.

3. Transfers the data record with status 20 with a positive sign to the BW so that the changed value can be included in the relevant analysis.

During the next delta transfer (after the data records that were changed in the source system have been approved), the system transfers the original value (status 60 (Canceled)) with a negative sign and the changed value with a positive sign as approved data records to the BW. During the next complete transfer of data records that have been released for approval, the system overwrites the data record with status 50.

This ensures that data in the BW always reflects the dataset in the database table for the Time Sheet (CATSDB) as accurately as possible. This is provided that you always transfer approved data records and data records that have been released for approval together, and in the same order.

Please check the data in PSA and see if it is complying with the above mentioned rules

[Former Member · Accepted solution]

Thank you so much for this info. I have read this already but can you tell me what date they are speaking of when they say determine data? see below sentence.

Transfers data records that have been released for approval if the last changed on date is further in the past than the determined date.

Thanks

Caroline

[Former Member]

Thank you everyone

[former_member345199]

Hi,

Try the link

http://help.sap.com/saphelp_nw70/helpdata/EN/c7/565f3ce4dd3370e10000000a114084/frameset.htm

It says that to use this DataSource you must have implemented Support Package SAPKH46C32, or have made the relevant corrections in SAP Note 509592.

Thanks,

JituK

[Former Member]

We are on ECC 6.0 so this note does not apply. Thanks!

Caroline

[Former Member]

What this sentence "Transfers data records that have been released for approval if the last changed on date is further in the past than the determined date."

actually means

is that if the Last changed on date is lesser than the approval date, then, the data transfer takes place to BW. However the same records will not be updated in the next delta load. The old requests would have to be deleted for a successful delta load.

There can be two records in R/3. Say for example

One says released for approval and the other one is changed after approval.

If the last changed on date is not released for approval then no udpate takes place.

It took me a while to analyze this sentence but this is probably the best explanation I could give .

[Former Member]

Please check this link as well:

http://econsultantresources.com/index.php?view=article&catid=48%3Asap-business-intelligence&id=114%3...

[Former Member]

Hi Coroline,

Can you please check the entries in LBWQ for this Data source, there might be a jam happend in this R/3 delta Queue.

This has a Direct Delta meathod and the posting has to run directely from LBWQ to RSA7 by on its own once you successfully initialize.

At the same time can you check in the RSA7 whether the Data source is having any records(no of LUW's).

This should give some info to solve your issue.

Best Regards,

VNK.

[Former Member]

I thought the LBWQ was only for the Logisitics Extractors?

Caroline