# tSAPADSOOutput

Writes data to an active Advanced Data Store Object (ADSO) through SAP Java Connector version 3. Note that data written by this component is actually staged in SAP and needs to be activated for being retrieved by tSAPADSOInput.

## tSAPADSOOutput Standard properties

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

The Standard tSAPADSOOutput component belongs to the Business family.

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

Information noteNote:

* This component is available only when you have installed the 8.0.1-R2022-04 Talend Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator.
* When prompted that this component requires sapjco.jar, download the module and refer to the instructions at [SAP Java Connector](https://support.sap.com/en/product/connectors/jco.html).

## Basic settings

| Properties | Description |
| --- | --- |
| Property Type | Either Built-In or Repository.<br><br><ul> <li> <p> <span>Built-In</span>: No property data stored centrally.</p> </li> <li> <p> <span>Repository</span>: Select the repository file where the            properties are stored.</p> </li> </ul> |
| Use an existing connection | Select this check box and from the Connection configuration drop-down list displayed, select the component<br>in which the relevant reused database connection is configured.<br><br>When a Job contains a parent Job and a child Job, the list<br>displayed presents only the connection components in the same Job level. |
| Server Type | Select the type of the SAP server to be connected, either Application Server or Message Server. |
| Client | The SAP system client ID. |
| UserId and Password | The user connection ID and password.<br><br>To enter the password, click the [...] button next to the password field, and then in the pop-up dialog box enter the password between double quotes and click OK to save the settings. |
| Language | The language of the SAP system. |
| Host name | The name or IP address of the host on which the SAP server is running. |
| System number | The SAP system number.<br><br>This option is available when Application<br>Server is selected from the Server Type<br>drop-down list. |
| System ID | The SAP system ID.<br><br>This field is available when Message Server is<br>selected from the Server Type drop-down list. |
| Group Name | The SAP group name.<br><br>This field is available when Message Server is<br>selected from the Server Type drop-down list. |
| 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 schema to make changes to<br>the schema. If you make changes, the schema automatically becomes built-in.<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> |
| ADSO name | The name of the active Advanced Data Store Object to write data to. |
| Batch size | The maximum number of records allowed to be written to the active Advanced<br>Data Store Object in one batch. |
| Specify a shared destination | Select this check box and specify the shared destination in the<br>Shared destination name field<br>displayed. The shared destination allows the SAP components to use the<br>shared destination on the Talend Runtime when they are executed as part of<br>an ESB Route or ESB Data Service within the Talend Runtime<br>container OSGi Environment.<br><br>Besides specifying the shared destination name in the component, you also need<br>to setup the SAP DataSource for the Talend Runtime. What you need to do to define the SAP DataSource and how to configure it<br>are described in the readme.txt provided in the Talend ESB package in the /add-ons/datasource/sap folder.<br><br>Note that if you use the component's own connection configuration,<br>your SAP connection will be closed at the end of the component. To prevent<br>this from happening, use a shared destination with its name specified. |

## Advanced settings

| Properties | Description |
| --- | --- |
| SAP Properties | If you need to use custom configuration for the SAP system being used, complete this table with the property or properties to be customized. For example, to set up an SAP connection with Secure Network Communications (SNC), you need to add and set the following properties in this field.<br><br><ul> <li> <span>jco.client.snc_mode</span> </li> <li> <span>jco.client.snc_myname</span> </li> <li> <span>jco.client.snc_lib=.../sapcrypto/sapcrypto.dll</span> </li> <li> <span>jco.client.snc_partnername</span> </li> <li> <span>jco.client.snc_qop</span> </li> </ul><br><br>Information noteNote: The values of the above properties vary with the system environment. Contact your SAP system administrator if you are not sure how to set the properties.<br><br>If you are using the 8.0.1-R2024-01 monthly update or a previous one, to enable<br>support for SAP BW on HANA, you need to install the<br>CB4K900207.zip transport and set the<br>api.use\_bw\_on\_hana property to true. Note<br>that currently, ADSO field only supports data that is of<br>Character and Date types. See [SAP function modules shipped with Talend Studio](https://help.qlik.com/talend/en-US/components/8.0/sap/sap-function-modules-shipped-with-talend-studio)<br>for information about the CB4K900207.zip transport.<br><br>If you are using the 8.0.1-R2024-02 monthly update or a later one, to enable<br>support for SAP BW on HANA, you need to install the<br>DHBK900344.zip transport and the<br>S4HK902231.zip deletion-transport. Note that more data<br>types are supported, but there is a limitation when writing dynamic length<br>fields STRING and SSTRING. Only the default max string length of 1000 is<br>supported.<br><br>SAP Business Warehouse powered by HANA (referred to as BW on HANA or BWoH) and<br>SAP BW/4HANA are two application suites running on SAP HANA. BW on HANA is an<br>SAP tool built on HANA database for data modeling, warehousing, and reporting.<br>It runs on HANA database and therefore is simpler and faster. You can use BW on<br>HANA through two ABAP function modules: Z\_TLDBI\_GET\_ADSO and Z\_TLDBI\_GET\_ADSO\_DETAIL. See [SAP function modules shipped with Talend Studio](https://help.qlik.com/talend/en-US/components/8.0/sap/sap-function-modules-shipped-with-talend-studio)<br>for related information.<br><br>BW/4HANA is a data warehouse solution with agile and flexible data modeling. It<br>provides processes and user interfaces highly optimized for the SAP HANA<br>platform. It only requires standard SAP functions.<br><br>Information noteNote: The support for SAP BW on HANA is available when you have installed the<br>8.0.1-R2022-12 Talend Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator.<br><br>For more information about setting the SNC parameters, see [Configuring SNC: External Programs to AS ABAP Using RFC](https://help.sap.com/viewer/10977ac76c531014a966b3f130d4f853/7.0.36/en-US/d9e8a740bbaa4d8f8bee6f7b173bd99f.html) and [Communication Paths that Support SNC](https://help.sap.com/viewer/10977ac76c531014a966b3f130d4f853/7.0.36/en-US/76128150317a47b6a326e63a17017729.html). |
| 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<br>occurs. This is an After variable and it returns a string. |

## Usage

| Usage guidance | Description |
| --- | --- |
| Usage rule | This component is usually used as an end component of a Job or<br>subJob and it always needs an input link. |