tSAPIDocInput (deprecated)
Extracts IDoc data set that is used for asynchronous transactions between SAP
systems or between a SAP system and another application.
tSAPIDocInput connects to an RFC
destination in the SAP system through authentication of the SAP
gateway server and outputs IDoc files (Intermediate Documents in XML
or HTML format) to the user-defined location.
tSAPIDocInput Standard properties
These properties are used to configure tSAPIDocInput running in the Standard Job framework.
The Standard
tSAPIDocInput component belongs to the Business family.
The component in this framework is available in all subscription-based Talend products.
Basic settings
Property type |
Either Built-in or |
 |
Built-in: No property data stored |
 |
Repository: Select the Repository file |
Click this icon to open a connection wizard and store the Excel For more information about setting up and storing file |
|
Connection configuration |
Client: Enter your SAP usual connection
Userid: Enter the user connection Password: Enter the password. To enter the password, click the […] button next to the Language: Specify a language.
Host name: Enter the SAP system IP
System number: Enter the system
Program ID: Enter the program ID of the
Gateway service: Enter the name of your
C:WINDOWSsystem32driversetc folder; or execute |
Output format |
Select one or both of the check boxes to decide the format of
|
Die on error |
By default, this check box is cleared. Therefore the rows on |
Advanced settings
Activate logs |
Select this check box to enable the generation of log files and |
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,
|
tStatCatcher Statistics |
Select this check box to gather the Job processing metadata at a Job |
Global Variables
Global Variables |
ERROR_MESSAGE: the error message generated by the A Flow variable functions during the execution of a component while an After variable To fill up a field or expression with a variable, press Ctrl + For further information about variables, see |
Usage
Usage rule |
Usually used independently or in a subJob. Once executed, it |
Support |
SAP S4/HANA provides limited support for IDoc. |
Connections |
Outgoing links (from this component to another):
Trigger: Run if, On Component Ok, On Incoming links (from one component to this one):
Trigger: Run if, On Component Ok, On For further information regarding connections, see |
Limitation |
Specific jar and dll files provided by SAP must be added to your
Studio and the workstation hosting your Studio. The exact procedure varies among platforms such as 32-bit or 64-bit Windows or Linux.
|
Connecting to a given SAP R/3 system for listening the creation of
IDoc files (deprecated)
This scenario applies only to subscription-based Talend products.
In this scenario, an one-single-component Job uses the tSAPIDocInput component to keep listening to the creation of IDoc files
in a given SAP R/3 system.
To replicate this scenario, you need to:
-
Create an RFC Destination on the given SAP R/3 system.
-
Configure tSAPIDocInput to listen to the
invocation from this SAP R/3 system.
Creating an RFC Destination for the listener component tSAPIDocInput
Logon to a given SAP R/3 system and then proceed as follows to create the required
RFC Destination:
-
Execute the transaction SM59 to open the Display and
maintain RFC destinations view. -
In this view, select the TCP/IP
connections option and click Create.Then the RFC Destination view
displays. -
In RFC destination field of this view,
type in the name of this RFC Destination to be used. As this field is
case-sensitive, it is recommended to use upper case characters. In this
example, we name it as IDOC_TALEND. -
In the Connection type field, select the
T type meaning to start an external
program via TCP/IP. -
In the Description field, type in a short
text to describe this RFC Destination being created. In this example, we
enter simply TALEND IDOC LISTENER. -
In the Logon area, select the Current user check box and then click the
Save button on the top toolbar.Then the RFC Destination IDOC_TALEND view is
opened. -
In this view, click Registration to
display the Program ID field and type in
the program ID. This program ID must use the same name as this created RFC
Destination, that is, IDOC_TALEND. Then again, click
the save button on the top toolbar to validate this configuration. -
Still on the top toolbar, click the back button several times to go back
to the SAP Easy Access view (SAP main
screen) and execute the transaction SMGW to open the
gateway monitor view. -
From the menu bar of the gateway monitor view, select Goto > Parameters > Display. Then an table
like the following one displays, where you can find the gateway service of
this given SAP R/3 system.
In this example, the gateway service to be used is
sapgw00.
Now, the required RFC Destination has been created.
Configuring the listener component tSAPIDocInput
In the
Integration
perspective of your Studio, proceed as
follows:.
-
Drop the tSAPIDocInput component from the
Palette onto the design
workspace. -
Double-click this component to open its Component view.
-
In the Client field, type in the client
number of this given SAP R/3 system. In this scenario, it is
000.. -
In the Userid and Password fields, type in the authentication information in
the corresponding field. -
In the Language field, type in the
language used by this given SAP R/3 system. In this example, it is
EN. -
In the Host name field, type in the IP
address of the hosting server of this given SAP R/3 system. -
In the System number field, type in the
system number of this given SAP R/3 system. -
In the Gateway service field, type in the
used gateway service name. -
In the Program ID field, type in the
program ID you have defined when creating the required RFC Destination. In
this example, it is IDOC_TALEND. -
In the XML-IDoc file output field, enter
the path or browse to the location where you need to store the received SAP
IDoc file.
Job execution
-
Press CTRL+S to save your Job and press F6 to run it.
From this console, you can read that the tSAPIDocInput component is listening to this given SAP R/3
system. -
Back to the created RFC Destination in this SAP R/3 system, click
Test connection.
The test result indicates that the connection between this given SAP R/3 system
and the listener component tSAPIDocInput component
succeeds.
Now the tSAPIDocInput component is
listening to your SAP R/3 system and wait for the invocation of the previously
defined RFC Destination.