Custom data restriction for initial syncs in the ERP on HANA Connector
Answered
Which connector?: ERP on HANA, possibly others.
Additional details: This is an on-behalf request for Hitachi Energy. They are asking us to build a feature that allows loading one or multiple tables from a specified point in time instead of performing full initial sync. For example - by using a date column to apply a restrict condition, then continue replication from there. (similar to a customizable Restrict --> RefreshCondition in HVR).
This request can probably be divided into two parts:
- Show a suitable column for a restriction in the SAP table explorer OR allow a customer to specify a column on a per-table basis
- Allow this restriction to take place during initial syncs.
Thank you,
Marton
-
Hi Marton,
The SAP ERP on HANA connector already supports row filtering, configured in the Schema tab. Depending on the columns available in each table, customers can use a date or fiscal year condition to load only records from a specified date onward. The availability of such columns differ prt the table.
Filtering happens at the source, so excluded records are not extracted. However, the filter applies to both the initial sync and ongoing change data capture (CDC). Filtering only the initial sync, while subsequently replicating all changes, is currently not planned.
Separately, an internal project is exploring skipping the initial sync entirely and replicating only changes. Would either existing row filtering or this proposed option meet Hitachi Energy’s needs?
Best regards,
Edwin -
Hi Edwin,
The customer is hoping to have an option for e.g. ACDOCA where they could init-load the last few fiscal periods (202606-10), then append it on top of their existing data in the destination warehouse (loaded with a previous tool) and then to keep synchronization going, but without the filter.
So they do not want to have an ongoing row filtering, just filtering on the initial load.Thanks,
Marton
Please sign in to leave a comment.
Comments
2 comments