August 15, 2023

Scenario: Checking number format using a stored procedure – Docs for ESB 6.x

Scenario: Checking number format using a stored procedure

The following job aims at connecting to an Oracle Database containing Social Security
Numbers and their holders’ name, calling a stored procedure that checks the SSN format
of against a standard ###-##-#### format. Then the verification output results, 1 for
valid format and 0 for wrong format get displayed onto the execution console.

  • Drag and drop the following components from the Palette: tOracleConnection,
    tOracleInput, tOracleSP and tLogRow.

  • Link the tOracleConnection to the tOracleInput using a Then
    connection as no data is handled here.

  • And connect the other components using a Row
    link as rows are to be passed on as parameter to the SP
    component and to the console.

  • In the tOracleConnection, define the details
    of connection to the relevant Database. You will then be able to reuse this
    information in all other DB-related components.

  • Then select the tOracleInput and define its

  • Select the Use an existing connection check
    box and select the tOracleConnection component
    in the list in order to reuse the connection details that you already

  • Select Repository as Property type as the Oracle schema is defined in the DB Oracle
    connection entry of the Repository. If you haven’t recorded the Oracle DB
    details in the Repository, then fill in the
    Schema name manually.

  • Then select Repository as Schema, and retrieve the relevant schema
    corresponding to your Oracle DB table.

  • In this example, the SSN table has a four-column schema that includes
    ID, NAME,

  • In the Query field, type in the following
    Select query or select it in the list, if you stored it in the

    select ID, NAME, CITY, SSNUMBER from SSN

  • Then select the tOracleSP and define its
    Basic settings.

  • Like for the tOracleInput component, select
    Repository in the Property type field and select the Use an
    existing connection
    check box, then select the relevant entries
    in the respective list.

  • The schema used for the tOracleSP slightly
    differs from the input schema. Indeed, an extra column
    (SSN_Valid) is added to the Input schema. This column
    will hold the format validity status (1 or
    0) produced by the procedure.

  • In the SP Name field, type in the exact name
    of the stored procedure (or function) as called in the Database. In this use
    case, the stored procedure name is is_ssn.

  • The basic function used in this particular example is as follows:

  • As a return value is expected in this use case, the procedure acts as a
    function, so select the Is function check box.

  • The only return value expected is based on the ssn_valid
    column, hence select the relevant list entry.

  • In the Parameters area, define the input and
    output parameters used in the procedure. In this use case, only the
    SSNumber column from the schema is used in the

  • Click the plus sign to add a line to the table and select the relevant column
    (SSNumber) and type (IN).

  • Then select the tLogRow component and click
    Sync Column to make sure the schema is passed on from the preceding tOracleSP component.

  • Select the Print values in cells of a table
    check box to facilitate the output reading.

  • Then save your job and press F6 to run it.


On the console, you can read the output results. All input schema columns are
displayed even though they are not used as parameters in the stored procedure.

The final column shows the expected return value, whether the SS Number checked is
valid or not.


Check Scenario: Inserting data in mother/daughter tables if you want to analyze a set of records from a
database table or DB query and return single records.

Document get from Talend
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x