Consider the following rules and guidelines when you configure delta extraction for SAP table reader mappings:
You can perform delta extraction only for a single SAP table. You can't use native joins to join data from two or more SAP tables.
You can't configure delta extraction to look up data from SAP tables.
You can't configure delta extraction with partitioning.
You can't configure delta extraction for multiple pipelines within the same mapping.
When the Secure Agent performs a delta extraction, it does not retrieve the records in the same order in which they were inserted or updated in the SAP table. For example, record 10 might have been updated first in the SAP table before record 20. However, while extracting the data, the Secure Agent might fetch record 20 first and then record 10.
The Secure Agent does not print any information in the session log to indicate whether the records extracted through delta extraction were part of an insert or update operation in SAP.
During delta extraction, if there are multiple entries for a key between the current and last updated date and time, the Secure Agent fetches only the latest entry for the key.
For example, consider that a record was inserted into a Customer table in SAP with the customer name set to
John
. The record was later updated and the name was changed to
Bill
. The Secure Agent fetches the name value as only
Bill
.
You can't use the QUAN and CURR data types in delta extraction mappings.
You can't configure delta extraction in
data transfer
tasks.
To fetch the inserted or updated delta records to the target table, select
Upsert
as the operation and
Update Else Insert
as the update mode in the Target transformation. Otherwise, data corruption occurs in the target.
ASK INFAPreview
