Scenarios in Oracle ODI -

Scenarios in Oracle Data Integrator

A scenario is designed to put source components (mapping, 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.

Note: Once generated, the scenario's code is frozen, and all subsequent modifications of the package and/or data models which contributed to its creation will not affect it. If you want to update a scenario - for example because one of its mappings has been changed - then you must generate a new version of the scenario from the package or regenerate the existing scenario.

More Info >> >
An ODI Scenario is the generated code of an ODI object at a specific point in time.

1. Represents the snapshot of an object.
2. Has a name and a version.

If the source object is modified, the scenario is not changed. 

A Scenario can be run in different contexts

1. The recommended method to move objects to production and other environments.
2. Can be scheduled 

Scenarios can be generated from the following ODI objects:

1. Packages.
2. Mappings.
3. Procedures.
4. Variables

Generation Options for ODI Scenarios 
we have 2 options to generate ODI Scenarios

1. Generation
2. Regeneration.

Generation - 

1. Process to create a new scenario or a group of new scenarios.
2. Creates a new version for new and existing scenarios .
3. Existing schedules for the current version will need to be recreated 

Regeneration - Regeneration is different from generation .

1. Process to regenerate compiled code for current scenario version .
2. Compiled code is overwritten.
3. Existing schedules continue to function as before 

Source : ODI user Guide.