This section shows how to use the integration type SAP Table or View.

Warning! Missing Authorization To use the Table component, access to the designated authority objects (RFC) in SAP must be available. For more information, see the knowledge base article on SAP User Rights: Table.

Look Up an SAP Table or View #

  1. Create a new Service of type SAP Table or View.
  2. Click [Save and edit]. The Search SAP Table or View menu opens.
  3. Enter the name of the Table or View to be extracted in the field Search by name (1) or search for a Table description. Use wildcards ( * ) if needed. SAP-Table-or-Views
  4. Click [Search] (2) to display the search results.
  5. Select a source file from the list of available search results (3). The extraction settings of SAP Table and Views open automatically.

The SAP Table or View settings consist of the following subsections:

yunIO-table

Table or View #

The name and description of the selected Table or View is displayed in the Table or View section.
To select a different source file, click Select in the upper right corner of the section.

Advanced Settings #

Function Name

Specifies the name of the function module used for data extraction. This field is filled automatically depending on what function modules are installed on your SAP system. Custom function modules are supported.

The following function modules can be used to extract tables:

  • RFC_READ_TABLE (TAB512)
  • /BODS/RFC_READ_TABLE (TAB2048)
  • /SAPDS/RFC_READ_TABLE (TAB2048)
  • /BODS/RFC_READ_TABLE2
  • /SAPDS/RFC_READ_TABLE2
  • Z_THEO_READ_TABLE

Warning! Duplicates in the target environment!
The SAP standard modules for table extraction do not have pointers for table fields. In larger tables this may cause low performance and duplicates in the target environment. Use the function module Z_THEO_READ_TABLE from Theobald Software to ensure smooth extractions.

Note the necessary authorization for SAP tables:

S_TABU_NAM ACTVT=03; TABLE=ENLFDIR

Row Limit

Specifies the maximum number of extracted records. 0 extracts the entire table.

Rows per Package

The extracted data will be split into packages of the defined size. The default value is 50000 lines.
A package size between 20000 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.

Warning! RFC_ERROR_SYSTEM_FAILURE - No more storage space available for extending an internal table:
To avoid a memory overflow on the SAP source system and to avoid huge overheads, choose a package size that suits your memory capacity.

Run in background

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

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

Output Columns #

You can select either all or only individual columns for extraction.
Per default all columns are selected to be extracted. Deselect the ones you don’t want to extract.

WHERE Clause #

Use a WHERE clause to filter your data.

Syntax Rules

  • Enter a space before and after the equal sign:
    Correct: YEAR = ‘1999’
    Wrong: YEAR= ‘1999 ‘, YEAR =’1999’ or YEAR=’1999’

  • Set floating point numbers in single quotation mark:
    Correct: KMENG > ‘10.3’
    Wrong: KMENG > 10.3

Note: The WHERE clause doesn’t need any line break (return key).

  • Values must have the internal SAP representation:
    • The date 01.01.1999 has the internal representation 19990101 (YYYYMMDD)
    • The year period 001.1999 has the internal representation 1999001 (YYYYPPP)
    • Numbers must contain the leading zeros, e.g., customer number 1000 has the internal representation 0000001000.
Operator Meaning
=, EQ True if the content of operand1 is equal to the content of operand2
<>, NE True if the content of operand1 is not equal to the content of operand2
<, LT True if the content of operand1 is less than the content of operand2
>, GT True if the content of operand1 is greater than the content of operand2
<=, LE True if the content of operand1 is less than or equal to the content of operand2.
>=, GE True if the content of operand1 is greater than or equal to the content of operand2
(NOT) LIKE True if the value of the operand operand1 matches (does not match) the pattern in the operand operand2.
(NOT) BETWEEN True if the content of the operand operand (not) lies between the values of the operands operand1 and operand2.

For more information on the OpenSQL syntax see SAP help site - Select WHERE.