Restrictions Concerning Commands Used On The Target Tab Of An ODI Procedure Or Knowledge Module Step

(Doc ID 555013.1)

Last updated on MARCH 16, 2018

Applies to:

Oracle Data Integrator - Version 3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 13-06-2013***

Goal

An Oracle Data Integrator (ODI) Procedure or Knowledge Module step executes a SELECT statement on the 'Command On Source' tab.

The result of this query is used on the 'Command on Target' tab.

This is called the Bind mechanism in ODI.

For example, one Procedure step with:

Command on Source:

select 'book' as ITEM_NAME,
       0      as ITEM_ID,
       0      as IS_NEW_ITEM
from dual

Command on Target:

insert into <%=odiRef.getObjectName( "L" , "TABLE_NAME", "LogicalSchema" , "D" )%>
values (
     :ITEM_NAME, :ITEM_ID, :IS_NEW_ITEM
)

Does the table under Command on Target tab always need to be prefixed with its physical schema name?

Do we always use the ":" to bind the column alias from Command on Source tab?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms