Skip to content

Table CDC Settings

This page contains an overview and description of all available Table CDC settings.

Open the Table CDC Settings

To open the service settings of an existing Table CDC service:

  1. Open the Services menu
  2. Select a service of type Table CDC.
  3. Click [ Edit].

The settings of the Table CDC service open.

Table CDC

The Table CDC tab contains settings related to the source table and log table in SAP.

Table

The Table section displays the name of the SAP table that is used for data extractions.

Select Table

Select a table from your SAP system. The Table CDC service tracks any changes made to the table.

Extract full table on first run

When active, Xtract Universal.iQ reads the whole table on the first service run.

Output Columns

The Output Columns section shows which table columns are included in the output of the service. You can select either all or only individual columns. By default all columns are selected and included in the output. Deselect the columns you want to remove from the output.

CDC Resources

The CDC Resources section provides an overview of all CDC resources in the connected SAP system for the table used in the service.

Manage all CDC Resources

Opens the "Manage CDC Resources" menu where you can view and delete all active CDC (Change Data Capture) resources on the connected SAP system, see Delete Log Tables.

Log Table State

Indicates the state of the log table in SAP that records any changes made to the selected table.

  • Not initialized: No log table exists in SAP for the selected table and Xtract Universal.iQ does not track changes to the source table.
  • Initialized: A log table exists in SAP for the selected table and Xtract Universal.iQ tracks changes to the source table. Xtract Universal.iQ extracts data based on the changes recorded in the log table.

To delete the initialized log table and all associated triggers of the selected table from your SAP system, click . The status changes to Not initialized.

Log Table

Name of the log table in SAP that records any changes made to the selected table.

Log Table Row Limit

Defines the maximum number of rows that the log table in SAP can contain. When the limit is reached, the service run fails with an exception. The maximum row limit of a log table is 500.000. The row limit is disabled by default (value 0).

Note

Once a log table is initialized, you cannot change the size limit anymore.

Filters

The Filters tab contains settings to filter table records. For information, see WHERE Clause.

Service Settings

The Service Settings tab contains settings specific to the service type.

Package Size

The extracted data is split into packages of the defined size. The default value is 50000 lines.
A package size between 20000 and 50000 is advisable for large amounts of data. 0 means no packaging. Not using packaging can lead to an RFC timeout for large data extractions.

Warning

RFC_ERROR_SYSTEM_FAILURE - No more storage space available for extending an internal table
To avoid a memory overflow on the SAP source system and to avoid huge overheads, choose a package size that suits your memory capacity.

Run as an SAP Background Job

Use SAP background jobs for long-running extractions that process large data volumes and may run into a timeout error ("Time limit exceeded"). Background jobs bypass the SAP timeout limit, but they incur more overhead and require more SAP resources. Overall extraction time is longer for background jobs.

Background jobs are only supported in combination with the custom function module THEO/READ_TABLE.

Mode

  • None, dialog mode only: All data extractions are executed as a dialog job in SAP (default). When extracting large amounts of data you may run into a timeout error.
  • Background mode only for initial load: The initial table extraction is executed as a background job in SAP. This option only applies if the checkbox Extract table on first run is active in the main window. Subsequent delta extractions are executed as dialog jobs.
  • Background mode only: Both initial and delta extractions are executed as a background job in SAP.

Tip

Extraction jobs are listed in the SAP JobLog (SM37) under the JobName theo_read_table.

Warning

Shared Memory ran out of memory!
If this error appears when running a background extraction, increase the Shared Memory size. SAP recommends 800MB~1.5GB for production or test system and 2GB~4GB for S/4 systems, see SAP Support: How to solve SYSTEM_NO_SHM_MEMORY runtime error.

Background Job Timeout (seconds)

Sets a timeout period for extractions that run in background mode.
The default value is 180 seconds. The maximum timeout value is 3600 seconds.

Note

The background job timeout setting only takes effect if the extractions run in background mode using /THEO/READ_TABLE.

Destination Settings

The Destination Settings tab contains settings specific to the destination assigned to the service.

The destination settings define how and where a service saves its output data. The settings vary depending on the destination.

Last update: June 24, 2026