Skip to main content Skip to complementary content

tSAPBapi Standard properties

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

The Standard tSAPBapi component belongs to the Business family.

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

Information noteNote: When prompted that this component requires sapjco.jar, download the module and refer to the instructions at SAP Java Connector.

Basic settings

Property Type

Either Built-in or Repository.

 

Built-In: You create and store the schema locally for this component only.

 

Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

Use an existing connection

Select this check box and from the list displayed select the relevant connection component to reuse the connection details you have already defined.

When a Job contains a parent Job and a child Job, the list displayed presents only the connection components in the same Job level.

Server Type

Select the type of the server to be connected, either Application Server or Message Server.

Client

Specify the SAP system client ID.

UserId and Password

Specify the user connection ID and password.

To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, and click OK to save the settings.

Language

Specify the language of the SAP system.

Host name

Enter the name or IP address of the host on which the SAP server is running.

System number

Enter the system number.

This field appears only when Application Server is selected from the Server Type drop-down list.

System ID

Enter the system ID.

This field appears only when Message Server is selected from the Server Type drop-down list.

Group Name

Enter the group name.

This field appears only when Message Server is selected from the Server Type drop-down list.

SAP Function

Specify the name of the BAPI function to be called.

tick it to enable multiple input/output;not tick it to enable document

Select this check box to use multiple input and output parameters when calling the SAP function.

Clear this check box to use the document type input and output parameters when calling the SAP function.

Schema and Edit schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

  • View schema: choose this option to view the schema only.

  • Change to built-in property: choose this option to change the schema to Built-in for local changes.

  • Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

    If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

The Schema list and the Edit schema button appear only when the tick it to enable multiple input/output;not tick it to enable document check box is cleared.

Input

Click the [+] button below the table to add as many rows as needed, each row for an input parameter, and set the following attributes for each input parameter:

  • Name: Enter the input parameter name between double quotation marks.

  • Type: Click the cell and select an input parameter type Single, Structure, or Table from the drop-down list.

  • Schema: Select the cell and click the [...] button in the cell to open the schema editor to define the input parameter's schema. For the input parameter of Single or Structure type, the value for each column is defined in the Value column in the schema editor.

  • Source Row: For the input parameter of Table type, click the cell and from the drop-down list select an incoming link through which the input data for the parameter is transferred.

  • Changing: select this check box if the input parameter is a changing parameter.

This table appears only when the tick it to enable multiple input/output;not tick it to enable document check box is selected.

Output

Click the [+] button below the table to add as many rows as needed, each row for an output parameter, and set the following attributes for each output parameter:

  • Name: Enter the output parameter name between double quotation marks.

  • Type: Click the cell and select the output parameter type Single, Structure, or Table from the drop-down list.

  • Schema: Select the cell and click the [...] button in the cell to open the schema editor to define the output parameter's schema.

This table appears only when the tick it to enable multiple input/output;not tick it to enable document check box is selected.

Die on error

Select this option to stop the execution of the Job when an error occurs to the component.

If this option is not selected, errors occur to the component are logged and the Job continues.

By default, this option is not selected.

Advanced settings

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 establish a Unicode connection between the SAP system and Talend Studio, you need to add the property jco.server.unicode and set its value to 1. Note that this property works if you are using SAP Java Connector 2.x and is unnecessary for SAP Java Connector 3.0 and higher versions.

  • to set up an SAP connection with Secure Network Communications (SNC), you need to add and set the following properties in this field.

    • jco.client.snc_mode
    • jco.client.snc_myname
    • jco.client.snc_lib=.../sapcrypto/sapcrypto.dll
    • jco.client.snc_partnername
    • jco.client.snc_qop
    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.

    For more information about setting the SNC parameters, see Configuring SNC: External Programs to AS ABAP Using RFC and Communication Paths that Support SNC.

This property is not visible when the Use an existing connection check box is selected.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at a Job level as well as at each component level.

Global Variables

Global Variables

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it.

For more information about variables, see Using contexts and variables.

Usage

Usage rule

This component is usually used as a start component together with other output component(s) or an intermediate component together with other input and output components.

Support

tSAPBapi should be used to interact with the ERP part of SAP, including S4/HANA.

Connections

  • Outgoing links (from this component to another):
    • Row: Main

    • Trigger: On Subjob Ok, On Subjob Error

  • Incoming links (from one component to this one):

    • Row: Main, Iterate

    • Trigger: On Subjob Ok, On Subjob Error, On ComponentOK, On Component Error

For further information about connections, see Using connections in a Job.

Limitation

Specific JAR and DLL files provided by SAP must be added to Talend Studio and the workstation hosting Talend Studio. The exact procedure varies among platforms such as 32-bit or 64-bit Windows or Linux.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!