- Open the Object Editor:
- In Designer Navigator, double-click the Package, Mapping, Procedure, or Variable under the project for which you want to generate the scenario.
- The corresponding Object Editor will open.
- Select Generate Scenario:
- On the ODI menu, select Generate and then Scenario.
- Alternatively, you can right-click the Package, Mapping, Procedure, or Variable in the Designer Navigator and select Generate Scenario....
- Enter Scenario Name and Version:
- The New Scenario dialog will appear.
- Enter the Name and Version of the scenario.
- The Name will be automatically uppercased, and special characters will be replaced with underscores (since it may be used in operating system commands).
- Preset Name and Version Fields:
- The Name is preset to the same name as the latest scenario generated for the component.
- The Version is automatically incremented, or set to 001 if no prior numeric version exists.
- If no previous scenario exists for the component, the first version will be created automatically.
- Scenario Naming Convention:
- New scenarios are named after the component according to the Scenario Naming Convention user parameter.
- To set this naming convention:
- Click Preferences from the Tools menu.
- Expand the ODI node, then the System node, and select the Scenarios node.
- Click OK:
- After entering the name and version, click OK.
- Define Scenario Variables (Optional):
- If your scenario uses variables, you can define them in the Scenario Variables dialog:
- Select Use All: To make all variables parameters.
- Select Use Selected: To choose specific variables to be used as parameters.
- Select None: To deselect all variables.
- Confirm and Finalize:
- Click OK to finalize the scenario generation.
- View the Generated Scenario:
- The generated scenario will now appear:
- Under the Scenarios tab.
- Under the Scenarios node of the source object within the project.
This sequence outlines the steps required to generate a scenario from an ODI component in the Designer Navigator, including setting variables and naming conventions.
No comments:
Post a Comment