# tELTSAPInput

Provides the SAP table schema that will be used by the tELTSAPMap component to generate the SQL SELECT statement.

## tELTSAPInput Standard properties

These properties are used to configure tELTSAPInput running in the Standard Job framework.

The Standard tELTSAPInput component belongs to the ELT family.

The component in this framework is available in all subscription-based Talend products.

## Basic settings

| Properties | Description |
| --- | --- |
| Schema and Edit schema | A schema is a row description. It defines the number of fields<br>(columns) to be processed and passed on to the next component. When you create a Spark<br>Job, avoid the reserved word line when naming the<br>fields.<br><br><ul> <li> <p> <span>Built-In</span>: You create and store the schema locally for this component                only.</p> </li> <li> <p> <span>Repository</span>: You have already created the schema and stored it in the                Repository. You can reuse it in various projects and Job designs.</p> </li> </ul><br><br>Click Edit<br>schema to make changes to the schema. If the current schema is of the Repository type, three options are available:<br><br><ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                choose this option to change the schema stored in the repository and decide whether                to propagate the changes to all the Jobs upon completion.</p> <p>If you just want to                propagate the changes to the current Job, you can select <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul> |
| Default Table Name | Enter the name of the input table between double quotation marks. |
| Mapping | Specify the metadata mapping file<br>for the database to be used. The metadata mapping file is used for the data<br>type conversion between database and Java. For more information about the<br>metadata mapping, see the related documentation for Type mapping.<br><br>Information noteNote: You can use Hive mapping to support Databricks Delta<br>Lake.<br><br>Note that this drop-down list is disabled, and by default, Mapping<br>SAP is selected and the SAP metadata mapping file is used. |

## Advanced settings

| Properties | Description |
| --- | --- |
| tStatCatcher Statistics | Select this checkbox to gather the Job processing metadata at the Job level<br>as well as at each component level. |

## Global Variables

| Variables | Description |
| --- | --- |
| ERROR\_MESSAGE | The error message generated by the component when an error occurs. This<br>is an After variable and it returns a string. |

## Usage

| Usage guidance | Description |
| --- | --- |
| Usage rule | The tELTSAPInput component is more commonly used along with<br>the tELTSAPMap component. The name of the link from<br>tELTSAPInput to tELTSAPMap must be<br>same as the table name specified in the Default Table Name<br>field of tELTSAPInput. |
| **Support** | tELTSAPInput should be used to interact with the ERP part of<br>SAP, including S4/HANA. |

**Related concepts**

* [Aggregating and filtering data in multiple SAP tables](https://help.qlik.com/talend/en-US/components/8.0/sap/teltsapmap-teltsapinput-tfileoutputdelimited-teltsapinput-tfileoutputdelimited-aggregating-and-filtering-data-in-multiple-sap-tables "This example demonstrates how to use the tELTSAPInput and tELTSAPMap components to aggregate data from two SAP tables and filter the columns and rows of data, finally write the filtered data into a local CSV file using a tFileOutputDelimited component.")