Limitations and considerations

When using SAP Extractor as a source endpoint in a Replicate task, the following limitations apply.

• DDLs are not supported. Should you need to change the extractor:

  1. Stop the task and remove the extractor from it.
  2. Replace the extractor and activate it.
  3. Add the extractor to the task again and resume.
• Each extractor can be associated with a single task only. Additionally, the extractor should be exclusively run by Replicate.
• Table transformations and filters may impact performance as they are not propagated to the extractors.
• Source lookup is not supported.

• Replicate supports only one instance of each extractor. Consequently, each extractor should be associated with only one Logical System.

• SAP Extractor uses the metadata extracted from the extractor's Z-table. Consequently, the target tables will be created with this table's columns and without a Primary Key/Unique Index.

• All changes are captured as INSERT operations.

• The Log Stream feature is not supported with this endpoint.

• Replicating data with 4-byte emoji characters is not supported.

• SAP tables with rows that exceed 8192 bytes are not supported. If you need to replicate such tables, you can work around this limitation by excluding columns until the row size is less than 8192 bytes.

• The Apply Changes and Store Changes replication options cannot be enabled without the Full Load replication option.
• The "Start from timestamp" and "Start from position" options for running tasks are not supported.
• Replicate header fields are not supported.
• The Allow unlimited LOB size and Optimize handling when LOB size is less than LOB handling options are not supported.