Limitations and considerations

When using SAP Extractor as a source connector in a Data Movement gateway task, the following limitations apply.

Limitations and considerations for all data tasks

• 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 Data Movement gateway.
• Table transformations and filters may impact performance as they are not propagated to the extractors.
• Source lookup is not supported.

• Data Movement gateway 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.

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

Limitations and considerations for replication tasks only

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