Opening Extraction Settings #

Within the window “Define data source for SAP Tables” click Settings. The window “Table Settings” opens.

Extraction-Settings-01

Table Settings #

The window “Table Settings” consists of two subsections:

  • Extraction Settings
  • Function Module

Extraction Settings #

Package Size
Specifies the number of records retrieved per data package. Optimal values can be found by trying out. The default value is 20000 lines. A package size between 15000 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 extracts.

Recommendation: Especially when executing a table extraction as a background job (see Extract data in background job), the package size plays an important role and should be chosen with regard to the total amount of data.

Row limit
Specifies the maximum number of extracted records. 0 Extracts the entire table.

Function Module #

Specifies the name of the function module used for data extraction. The field is filled automatically depending on which function modules are installed on your SAP system.

Recommendation: For better performance and restriction avoidance use the function module from Theobald Software Z_THEO_READ_TABLE. See also SAP Customizing.

Extract data in background job
If this checkbox is checked, the table extraction is executed as a background job in SAP. Extract data in background job setting is optional and is supported in combination with function module Z_THEO_READ_TABLE as of version 2.0. Activate the setting Extract data in background job for long-running extractions with a very large amounts of data that run into a timeout error (“Time limit exceeded”), when using the standard method.

Tip: the extraction jobs can be found in the SAP JobLog (SM37) under the JobName theo_read_table.

Custom Properties #

Table-XIS-Properties

ConvertsDates
The default value of this property is True. Setting this property to True does two things:

  1. SAP date fields (YYYYMMDD) are typed to SSIS pipeline type DT_DBDATE (instead of DT_WSTR).
  2. The following date conversions are applied in case of invalid data in SAP date fields: InvalidDateReplacement, MaxDateReplacement and MinDateReplacement. For the date conversions to apply, the UseLegacyDateConversion propery must be set to False.

InvalidDateReplacement

  • Enter a replacement value for invalid SAP dates, such as ‘20190132’ (January 32nd 2019).
  • Enter the replacement value in the following format: yyyy-mm-dd
  • The value NULL is supported
  • The default value of this property is 1970-01-02

MaxDateReplacement

  • Enter a replacement value for SAP dates that contain the year ‘9999’. Example: ‘99990101’ (January 1st 9999)
  • Enter the replacement value in the following format: yyyy-mm-dd
  • The value NULL is supported
  • The default value of this property is 2099-12-31

MinDateReplacement

  • Enter a replacement value for SAP dates that contain the year ‘0000’. Example: ‘00000000’
  • Enter the replacement value in the following format: yyyy-mm-dd
  • The value NULL is supported
  • The default value of this property is 1970-01-01

UseLegacyDateConversion
This property is meant for migration of table extractions from Xtract IS versions < 5.0.0. The default value of this property is False. As a prerequisite for using this property, the ConvertsDates property must be set to True. Setting UseLegacyDateConversion to True does the following:

  • Invalid SAP date values are replaced with the value entered in the InvalidDateReplacement property.
  • There is no replacement for SAP dates that contain the year ‘9999’. The value entered in the MaxDateReplacement property is not considered.
  • SAP dates that contain the year ‘0000’ are replaced with NULL. The value entered in the MinDateReplacement property is not considered.

Use Field Exits
Defines whether the conversion routines stored in the ABAP Data Dictionary are used for the respective fields. Typical examples are the language key (for example, D in the database, but DE after conversion) or the project number (for example, T000012738GT in the database, T/12738/GT after conversion). After the conversion, the value is always displayed as it would appear in a transaction in the SAP GUI.