Identity Columns Using Sequences and Identity Columns

12-26 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator substringGET_MONTH_NAMECUSTOMER.LAST_ORDER_DATE, 1, 3, Oracle Data Integrator will generate code similar to the following, depending on your execution technology: A function can be created as a global function or in a project. In the first case, it is common to all projects, and in the second, it is attached to the project in which it is defined. User functions can call other user functions. Table 12–9 User Function Translated into Code for Different Technologies Example 2 Implementation for Oracle substringInitcapto_charCUSTOMER.LAST_ORDER_ DATE MONTH , 1, 3 Implementation for Teradata substringcase when extractmonth from CUSTOMER.LAST_ ORDER_DATE = 1 then ‘January’when extractmonth from CUSTOMER.LAST_ORDER_DATE = 2 then ‘February’...end, 1, 3 Implementation for Microsoft SQL substringdatenamemonth, CUSTOMER.LAST_ORDER_ DATE , 1, 3 13 Working with Scenarios 13-1 13 Working with Scenarios This chapter describes how to work with scenarios. A scenario is designed to put a source component interface, package, procedure, variable into production. A scenario results from the generation of code SQL, shell, etc for this component. This chapter includes the following sections: ■ Section 13.1, Introduction to Scenarios ■ Section 13.2, Generating a Scenario ■ Section 13.3, Regenerating a Scenario ■ Section 13.4, Generating a Group of Scenarios ■ Section 13.5, Exporting Scenarios ■ Section 13.6, Importing Scenarios in Production ■ Section 13.7, Encrypting and Decrypting a Scenario

13.1 Introduction to Scenarios

When a component is finished and tested, you can generate the scenario corresponding its actual state. This operation takes place in Designer Navigator. The scenario code the language generated is frozen, and all subsequent modifications of the components which contributed to creating it will not change it in any way. It is possible to generate scenarios for packages, procedures, interfaces or variables. Scenarios generated for procedures, interfaces or variables are single step scenarios that execute the procedure, interface or refresh the variable. Scenario variables are variables used in the scenario that should be set when starting the scenario to parameterize its behavior. Once generated, the scenario is stored inside the work repository. The scenario can be exported then imported to another repository remote or not and used in different contexts. A scenario can only be created from a development work repository, but can be imported into both development and execution work repositories. Scenarios appear in a development environment under the source component in the Projects tree of Designer Navigator, and appear - for development and production environments - in the Scenarios tree of Operator Navigator. Scenarios can also be versioned. See Chapter 18, Working with Version Management for more information. Scenarios can be launched from a command line, from the Oracle Data Integrator Studio and can be scheduled using the built-in scheduler of the run-time agent or an