Use to generate new scenarios.
A scenario is designed to put a source component (mapping, package, procedure, variable) into production. A scenario results from the generation of code (SQL, shell, and so forth) for this component.
Notes:
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.
The scenario code (the language generated) is frozen, and all subsequent modifications of the components that contributed to creating it will not change it in any way.
The Name and Version fields of the Scenario are preset with the following values:
Name: The same name as the latest scenario generated for the component
Version: The version number is automatically incremented, if the latest version number ends with an integer. If the latest version does not end with an integer, the latest version number is displayed in the Version field. Please change the version number according to your needs. Note that you cannot use the same version number and version name for a scenario.
If no scenario has been created yet for the component, a first version of the scenario is automatically created.
New scenarios are named after the component according to the Scenario Naming Convention user parameter.
Specify the following parameters for the scenario generation:
Name: Name of scenario.
Version: Version of the scenario.
Physical Mapping Design: Physical Mapping Design defined in the mapping. Used for mappings only.
Select Generate scenario as if all underlying objects were materialized to generate the scenario as if the shortcuts were real objects.
Note: The logical schema of the model containing the shortcut(s) is used for the scenario generation.
The scenario properties are displayed and can be configured in the Scenario Editor.
"Generating a Scenario" in the "Using Scenarios" chapter in Oracle Fusion Middleware Developing Integration Projects with Oracle Data Integrator