New features and enhancements

You can configure application ingestion and replication tasks and database ingestion and replication tasks to trigger Data Integration taskflows that process and transform the ingested data. This feature is available for initial load and incremental load tasks that have any supported source type and a Snowflake target. When you define an ingestion and replication task, you can select the Execute in Taskflow option for the task to become available to add to taskflows in Data Integration. For incremental load jobs, you can also select the Add Cycle Id option to include cycle ID metadata in the target table. When you configure the taskflow in Data Integration, you can select a deployed ingestion and replication task as an event source. You can also include any appropriate transformation type to transform the ingested data. The taskflow is automatically triggered to start when either the initial load task successfully completes or after each CDC cycle in an incremental load operation. If a CDC cycle ends but the previous taskflow run is still running, the data is queued and waits for the previous taskflow to complete.

The April 2025 release of Application Ingestion and Replication includes the following new features and enhancements:

You can use SAP OData V2 Connector in application ingestion and replication initial load jobs to transfer data from OData V2-compliant SAP applications to compatible data warehouse and data lake targets. The connector uses the OData V2 API to ensure seamless data transfer between SAP systems and your target endpoints.

You can configure basic authentication to connect to specific SAP services or the catalog service on the SAP Gateway.

When you configure an application ingestion and replication task of any load type that uses Netsuite Mass Ingestion Connector or SAP Mass Ingestion Connector to transfer data from a Netsuite or SAP source to a target, you can select the columns you need from the Netsuite or SAP source.

You can use the Soft Deletes apply mode with Google BigQuery targets in application ingestion and replication incremental load and combined initial and incremental load jobs. This mode causes hard delete operations on the source to process as soft deletes on Google BigQuery targets. Application Ingestion and Replication marks the soft-deleted records with a "D" in the INFA_OPERATION_TYPE column on the target without deleting the records.

You can use Bulk API 1.0 in application ingestion and replication initial and combined initial and incremental load jobs to handle large-scale data from Salesforce. Bulk API 1.0 uses primary-key chunking to achieve parallel processing in Salesforce and optimizes the performance and speed of the task.

You can configure row-level filtering for a Salesforce source in an application ingestion and replication task of any load type that uses Salesforce Mass Ingestion Connector. Row-level filtering filters data rows for selected source tables and columns before the data is applied to the target. You can create Basic filters or more complex Advanced filters for columns in a selected table.

The April 2025 release of Database Ingestion and Replication includes the following new features and enhancements:

For database ingestion and replication initial load jobs that have a SAP HANA source, you can now enable partitioning of source tables and distribute the records read from the source across the partitions for parallel processing. Database Ingestion and Replication determines the range of partitions by using the ROWID as the partition key. Use this feature to improve the performance of jobs with large source tables. You can enable partitioning and configure the number of partitions as you configure the source in the database ingestion and replication task definition.

The April 2024 release of Streaming Ingestion and Replication includes the following new feature and enhancement:

For streaming ingestion and replication tasks with a JMS source, you can use JMS version 3.0 with the Oracle Weblogic JMS provider. Specify the JMS version in the JMS source advanced properties in the task. The default version remains 2.0, which is applicable to other compatible JMS providers.