In this blog I will give an overview about extracting Datasources with the DeltaQ component to extract

and give some tips how to troubleshoot errors that may occur.

A Datasource is a set of fields that provide the data for a business unit (e.g. Customer, Material). Datasources are one of the data retrieval mechanisms in the SAP source system. Generally Datasources are used to transfer data from SAP ERP / ECC into SAP BW / BI. Export Datasources are used to transfer data from one SAP BW / BI system to another one.

With the DeltaQ component you can extract those Datasources to any third-party destination system supported by the Theobald Software products, even if you don’t have an SAP BW / BI system.

Many standard Datasources supports the Delta update mode, that only requests data that has appeared in the source system since the last load. With large volumes of data, you can only ensure a performance-optimized extraction from the source system if you use a delta process.
You need to initialize a delta process before you can execute it. The initialization selections are copied to load the delta records.
To extract a Datasource from the OLTP system, you have to activate it in the OLTP system:
- Transfer the application component hierarchy. Use transaction SBIW or alternatively RSA9 in the OLTP system.
- Go to transaction SBIW, and choose Business Content Datasources and Transfer Business Content Datasources. Alternatively, you may also use transaction RSA5. The procedure is the same.
- Activate the Datasource.
There are four types of DataSources:
  • DataSource for transaction data
  • DataSource for master data
    • DataSource for attributes
    • DataSource for texts
    • DataSource for hierarchies

Troubleshooting errors

If an error occurs while extracting a Datasource with the DeltaQ component, please go through the following steps:

  1. Be sure that you have the necessary authority objects: Typically you will get an error with the message text ‘No authorization‘ if you don’t have the right authority objects.
  2. Use SAPGUI to test the Datasource with the Extraction Checker (transaction RSA3) and be sure that the Datasource runs successfully and delivers data
  3. Do the customizing steps:
  4. Customizing Check: Click on the Button Check Customizing in the DeltaQ Component and be sure that the check comes back all green.
  5. Activation: Click on the Activate button or select alternatively the option ‘Automatic Synchronisation’. If the Datasource metadata changes, e.g. new columns are added, or if you have changed the SAP system, a new activation is required.
  6. If Datasource parameters are used (refer to the Extraction Checker step), be aware of the SAP syntax, e.g. a SAP date has the following syntax yyyymmdd (20121225)
  7. If you are using the setting ‘automatic data conversion’, check if the error disappears by deselecting the setting. The error may occur because invalid SAP values could not be converted.
  8. If the error is ‘The transfer structure for object OBJECTNAME must be regenerated‘, then go to the settings and change the transfer type from tRFC to IDoc
  9. If you are using the Delta update mode and you get the error: ‘Error in data selection‘, please delete all requests in the data queue: Settings -> Request Maintenance. Alternatively you can delete the requests in the transaction RSA7. After deleting the requests initialize the Datasource again with the Delta Initialization mode.
  10. If all Datasources get the error, go to step 1, alternatively
  11. If you can’t fix the error, send us the SSIS log and the SAP trace files:
    1. SSIS log: The SSIS log can be found e.g. in the output window or in the progress tab.
    2. SAP trace: Activate tracing, execute the Task and go to the log folder and send us all the log files: Xtract IS Connection Manager

Written by Khoder Elzein

Khoder is responsible for presales and always has an attentive ear for our customers, prospectives and partners. When travelling in Germany or abroad, he provides customer support at PoCs, workshops and on training courses. He also looks after the further development of our software solutions. Khoder has been working in IT since the turn of the millennium; he has been a member of team Theobald since 2009. When it comes to private interests, family, nature and reading feature at the top of his list – along with innovative fusion cuisine, as you may infer from his favourite dish of Swabian cheese noodles with tabouleh.