Click the Extraction Settings link to open the Extraction Settings dialog.


Transfer Mode
The raw data packages can be send by SAP by a tRFC call or a Data-IDoc. Normally the tRFC is optimal for the default setting. If it is necessary, e.g. to examine the raw data packages for debugging reasons, you can change the transfer mode to IDoc. Then you can examine the data packages in the transaction WE02 (IDoc-Monitoring).

Automatic Synchronisation
Depending on the system landscape it could happen that developments only be performed in a test system. If SSIS packages should be used later in the productive environment, the data source has to be enabled there. To avoid manual changes in the transactional system you can activate this option. In this case the activation will be automatically done and the timestamp of the data source will be changed that it will be consistent to the SAP system setting.
If the DataSource was modified in the SAP system, e.g. a field’s name, data type or length was changed or a field was excluded from data transfer, you will still have to manually activate the DataSource in the DeltaQ component, even if Automatic Synchronisation is switched on. Otherwise data load will fail. This behaviour is by SAP design and is described in SAP help.

Add Serialization Info to Output
Adds the two columns DataPackageID and RowCounter to the output.
In this Case the following 3 columns will be available in the output:
RequestID, DataPackageID and RowCounter, which are a composite key of the records delivered by SAP.
Newer data have a higher PackageID. In the same package newer data have a higher RowCounter.

Automatic Data Type conversion
SAP data types (e.g. date YYMMDDDD) will be converted to an appropriate (e.g. date) data type.

Accept Gaps in DataPackage Id
The Delta Q component makes at the end of each extraction a consistency check. Only when all packets have arrived correctly, the extraction is considered consistent. In the case that the customer has built a filter function in the user exit of an OLTP source that causes certain data packets to not be sent, the consistency check must be mitigated. Otherwise the customer filter function would be seen as inconsistency. If this option is activated, gaps in the packet numbering will not be counted by the DeltaQ as inconsistency but as intentionally withheld information. The option should only be used if a corresponding filter function exists in the user exit.

Defines the time period within the Xtract Universal server should wait for a “Notify” from the SAP system (in seconds).

Request Maintenance
To show and delete the Init Requests (Requests in RSA7).

  • Delete Request
    delete the initialisation requests (requests in RSA7).

  • Allow BW requests deletion
    allow the deletion of the initialisation requests of the export datasources in BW.

Hierarchy Settings

For a Hierarchy DataSource Extraction you can use the following hierarchy settings on the Hierarchy tab.


Defines the Language, if a Hierarchy is extracted.

Hierarchy Name
Defines the Hierarchy Name.

Hierarchy Class
Defines the Hierarchy Class.


  • ParentChild: The hierarchy has the SAP parent-child format.


  • Natural: The parent child hierarchy will be transformed in a regular hierarchy.

Level Count

Defines the maximum number of levels if the representation natural is selected. In the following screenshot you see the hierarchie shown in the previous screenshot with five levels in the representation natural.


Fill empty levels

If the representation natural is selected the bottom element of the hierarchy will be copied until the last level. In the following screenshot you will see the hierarchy from above with the option Repeat Leaves activated.


Description texts for levels
Means, that the output has a field LevelTextN for each field LevelN, that contains the text based on the system language settings.

Leaves only
Delivers only the leaves as data records.