Skip to content

Table Settings

This page contains an overview and description of all available Table settings.

Open the Table Settings

To open the service settings of an existing Table service:

  1. Open the Services menu
  2. Select a service of type Table.
  3. Click [ Edit].

The settings of the Table service open.

Table

The Table tab contains settings related to the source tables in SAP.

Table or View

The Table or View section displays the names of the tables or views used in the service.

Add Table

Add a new table to the Table service. You can add multiple tables and join them into a single dataset, see table joins.

Refresh metadata

Performs a new lookup on the table(s). Existing mappings and field selections are kept, which is not the case when re-adding the table to the service. Use this function to resolve data inconsistencies that can occur in the following situations:

  • the structure of the source table has been changed in SAP
  • another SAP source system has been connected
  • the SAP source system has been updated

Output Columns

The Output Columns section shows which table columns are included in the output of the service. You can select either all or only individual columns. By default all columns are selected and included in the output. Deselect the columns you want to remove from the output.

If multiple tables are used in the service, use the table selector at the top to switch between tables.

Joins

The Joins section displays all table join conditions. For more information on how to use joins, see Table Joins.

Filters

The Filters tab contains settings to filter table records. For information, see WHERE Clause.

Custom Parameters

The Custom Parameters tab contains user-defined placeholders for values that are passed at runtime. They can be used to create dynamic WHERE Clauses. For more information, see Parameters.

Service Settings

The Service Settings tab contains settings specific to the service type.

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 (deprecated)
  • /THEO/READ_TABLE (recommended)

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 THEO/READ_TABLE from Theobald Software to ensure smooth extractions.

Note the necessary SAP Authority Objects:

S_TABU_NAM ACTVT=03; TABLE=ENLFDIR

Run in Background

When Extract data in background job is active, the table extraction is executed as a background job in SAP. This setting is only supported in combination with the custom function module THEO/READ_TABLE.

Use SAP background jobs for long-running extractions that process large data volumes and may run into a timeout error ("Time limit exceeded"). Background jobs bypass the SAP timeout limit, but they incur more overhead and require more SAP resources. Overall extraction time is longer for background jobs.

Background jobs are only supported in combination with the custom function module THEO/READ_TABLE.

Tip

Extraction jobs are listed in the SAP JobLog (SM37) under the JobName theo_read_table.

Warning

Shared Memory ran out of memory!
If this error appears when running a background extraction, increase the Shared Memory size. SAP recommends 800MB~1.5GB for production or test system and 2GB~4GB for S/4 systems, see SAP Support: How to solve SYSTEM_NO_SHM_MEMORY runtime error.

Row Limit

Specifies the maximum number of extracted records. 0 extracts all data. You can use this option to perform tests with a small amount of data by entering a row limit of e.g., 1000.

Rows per package

The extracted data is 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 extractions.

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.

Destination Settings

The Destination Settings tab contains settings specific to the destination assigned to the service.

The destination settings define how and where a service saves its output data. The settings vary depending on the destination.

Last update: June 24, 2026