Purpose Developments Provided with Oracle Data Integrator

7-2 Oracle Fusion Middleware Getting Started with Oracle Data Integrator cannot load the TRG_CUSTOMER table if the TRG_CITY table has not been loaded first. In the Section 7.2, Load Sales Administration Package Example , you will create and run a package that includes interfaces that are included in the Demo project and interfaces that you’ve created in Chapter 6, Working with Integration Interfaces .

7.1.2.1 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, and so forth for this component. Once generated, the code of the source component is frozen and the scenario is stored inside the Work repository. A scenario can be exported and then imported into different production environments. See Working with Scenarios in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator for more information. In Chapter 9, Deploying Integrated Applications , you will generate the LOAD_ SALES_ADMINISTRATION scenario from a package and run this scenario from Oracle Data Integrator Studio.

7.2 Load Sales Administration Package Example

This section contains the following topics: ■ Purpose ■ Developments Provided with Oracle Data Integrator ■ Problem Analysis ■ Creating the Package

7.2.1 Purpose

The purpose of the Load Sales Administration package is to define the complete workflow for the loading of the Sales Administration application and to set the execution sequence.

7.2.2 Developments Provided with Oracle Data Integrator

The demo repository is delivered with a number of developments. The Demo project now contains the following developments as shown in Figure 7–1 : ■ Seven interfaces: ■ Pop. TRG_CITY : an interface that populates the TRG_CITY table. This interface is delivered with the demo repository. Note: Once generated, the scenarios code is frozen, and all subsequent modifications of the package andor data models which contributed to its creation will not affect it. If you want to update a scenario - for example because one of its interfaces has been changed - then you must generate a new version of the scenario from the package. Working with Packages 7-3 ■ Pop. TRG_COUNTRY : an interface that populates the TRG_COUNTRY table. This interface is delivered with the demo repository. ■ Pop. TRG_CUSTOMER : an interface that populates the TRG_CUSTOMER table. This interface is created in Section 6.1, Pop. TRG_CUSTOMER Interface Example . ■ Pop. TRG_PRODUCT : an interface populates the TRG_PRODUCT table. This interface is delivered with the demo repository. ■ Pop. TRG_PROD_FAMILY : an interface that populates the TRG_PROD_ FAMILY table. This interface is delivered with the demo repository. ■ Pop. TRG_REGION : an interface that populates the TRG_REGION table. This interface is delivered with the demo repository. ■ Pop. TRG_SALES : an interface that populates the TRG_SALES table. This interface is created in Section 6.2, Pop. TRG_SALES Interface Example . ■ One procedure: The Delete Targets procedure empties all of the tables in the Sales Administration application. This operation is performed by using a Delete statement on each table. Figure 7–1 Demo Project

7.2.3 Problem Analysis