Full Load Always

Indicates the specified ETL process will always execute a full load.

Keep Separate Refresh Dates

Used for micro ETL processes. Indicates refresh dates are kept separate for each run of the execution plan.

Prune Days

When the source system is Oracle's Siebel CRM applications, the LAST_UPD column in the transactional database tables is used for incremental change capture. This timestamp reflects the actual event time. It is therefore possible for a data row to be committed to the transactional database with a LAST_UPD date that is older than the date on which the last refresh was executed. This will cause the data row to be missed in the subsequent extract (if based purely on LAST_UPD date).

However, the LAST_UPD date column still provides an opportunity to improve the change capture process by overlapping the extraction date window by the number of days set in this parameter. The records extracted in the overlapped window are filtered by comparing this information with information in the Image table.

The Prune Days setting ensures that the rows that had values in LAST_UPD older than values in LAST_REFRESH_DATE are not missed. This is a parameter that can be set based on experience with processes, such as remote sync, that potentially can cause records to be missed. This parameter cannot be less than 1.

For example: Assume the table W_PERSON_D was refreshed on January 15th by querying the table S_CONTACT. And, the Prune Days setting was set to 5. The next time S_CONTACT is queried to load W_PERSON_D, the records that have a LAST_UPD value since January 10 are compared with the ROW_ID of the Image table to cover for any missing records between January 15 and January 10 (the overlap period).

For source systems other than Siebel, the Prune Days setting is used in the same way except that the DAC substracts the number of prune days from the LAST_REFRESH_DATE of a given source and supplies this as the value for the $$LAST_EXTRACT_DATE parameter.

Last Designed

Date this execution plan was last designed.

Analyze

Indicates the tables associated with this execution plan will be analyzed.

Analyze Truncated Tables Only

Indicates only truncated tables will be analyzed.

Drop/Create Indices

Indicates indices of the tables associated with this execution plan will be dropped and created.

Subject Areas

Displays the subject areas associated with the selected execution plan. You can also add subject areas to the selected execution plan.

Parameters

Displays the selected execution plan's parameters for database connections and Informatica folders. It includes the following properties:

• Type. Possible values are:
  • Folder. Indicates an Informatica folder.
  • Datasource. Indicates a database connection parameter.
• Name. Logical name of the folder or database connection.
• Value. Physical name of the folder or database connection.
• Source System. Name of the source system associated with the parameter.

Preceding Tasks

Displays the tasks that must be completed before an ETL process is executed. Also allows you to add preceding tasks.

It includes the following properties:

• Priority. Indicates the order in which the task runs. If two or more tasks have the same priority, the DAC will run them in parallel.
• Inactive. Indicates the task is inactive.
• Command. Command associated with the task.
• Source System. Source system container from which the task extracts data.

Following Tasks

Displays the tasks that must be completed after an ETL is executed. Also allows you to add tasks.

It includes the same properties as the Preceding Tasks child tab.

Ordered Tasks

Displays tasks associated with the selected execution plan and the order in which they can be executed. It includes the following properties:

• Depth. The level of the task's dependency. Tasks that have no dependencies are depth 0. Tasks that depend on other tasks of depth 0 are depth 1, and so on.
• Primary Source. Primary source table from which the task extracts data.
• Primary Target. Primary target table into which data is loaded.
• Folder Name. Name of the Informatica folder in which the task resides.
• Task Phase. Task phase of the ETL process. The DAC server uses the task phase to prioritize tasks and to generate a summary of the time taken for each of the phases.
• Command. Command associated with the task
• Source System. Source system container from which the task extracts data.

The Details button opens a dialog box that contains the following information about the selected task:

• All Predecessors
• All Successors
• Immediate Predecessors
• Immediate Successors
• Source Tables
• Target Tables
• Conditional Tables

Immediate Dependencies

Displays the immediate dependent relationship between tasks that are generated during the automatic task generation process.

It includes the following properties:

• Task (Calculated). Shows the named task's source and target.
• Predecessor Name. Predecessor task for the named task.
• Predecessor (Calculated). Shows the source and target of the predecessor task.

All Dependencies

Displays the dependent relationship for all tasks. The columns are the same as the Immediate Dependencies child tab.

Refresh Dates

Applies to micro ETL execution plans (indicated by selecting the Keep Separate Refresh Dates check box in the Execution Plans tab).

• Connection. Logical name for database connection.
• Refresh Date. Last refresh time of the execution plan. This applies only when separate refresh dates are maintained. Used for micro ETL processing.