ODI12C Defining Load Plan Step Sequence FAQS

1. What is meant by Load Plan Step Sequence?

The Load Plan Step Sequence refers to how steps are organized and executed within a Load Plan. It defines whether steps run:

·        Sequentially (series)

·        In parallel

·        Conditionally (based on variables)

 

2. How is the execution flow of a Load Plan defined?

The execution flow is configured at two stages:

·        Design-time → While creating and organizing steps

·        Run-time / Design-time → By enabling or disabling steps

 

3. How is execution flow controlled at design-time?

At design-time, execution flow is controlled by:

·        Selecting the step type (Serial, Parallel, Case)

·        Defining the step hierarchy

·        Positioning steps correctly within the hierarchy

 

4. How does step type affect execution?

The step type determines execution behavior:

·        Serial Step → Executes child steps one after another

·        Parallel Step → Executes child steps simultaneously

·        Case Step → Executes steps conditionally based on variables

 

5. How do you decide where to place a step in a Load Plan?

When adding a step, you can insert it as:

·        A child step (inside another step)

·        A sibling step before the selected step

·        A sibling step after the selected step
This determines the execution sequence and hierarchy.

 

6. Can the order of steps be changed after creation?

Yes. You can reorganize steps by:

·        Dragging and dropping steps to a new position

·        Using toolbar arrows (Move Up, Move Down, Move In, Move Out)

 

7. What is the importance of step hierarchy?

The step hierarchy:

·        Defines parent-child relationships

·        Controls execution flow and dependencies

·        Determines whether steps run sequentially, in parallel, or conditionally

 

8. How can steps be enabled or disabled?

In the Steps Hierarchy table:

·        Each step can be enabled or disabled manually

·        Disabled steps are skipped during execution

 

9. What happens when a step is disabled?

When a step is disabled:

·        It is not executed during Load Plan run

·        All its child steps are also automatically disabled

 

10. Can step enabling/disabling be done at runtime?

Yes. Steps can be enabled or disabled:

·        At design-time

·        At run-time (before execution)
This allows flexibility in controlling execution behavior.

 

11. Why would you disable steps in a Load Plan?

Common reasons include:

·        Skipping certain processes temporarily

·        Testing specific parts of the Load Plan

·        Handling partial executions in production

·        Avoiding unnecessary processing

 

12. What is the benefit of defining step sequence properly?

Proper step sequencing ensures:

·        Correct execution order

·        Better performance optimization

·        Efficient parallel processing

·        Accurate conditional logic handling

 

13. Can step sequencing impact performance?

Yes. Proper sequencing:

·        Enables parallel execution where possible

·        Reduces total execution time

·        Improves resource utilization

 

14. What is the relationship between step sequence and execution logic?

Step sequence directly defines:

·        Execution order

·        Dependencies between steps

·        Conditional branching logic

 

15. What are best practices for defining step sequence?

·        Use Parallel Steps for independent tasks

·        Use Serial Steps for dependent tasks

·        Use Case Steps for conditional logic

·        Keep hierarchy clean and readable

·        Avoid unnecessary nesting