Results for “edw_load_progress_log_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view EDW_LOAD_PROGRESS_LOG_V is a reporting object within the BIS (Business Intelligence System) product family of Oracle E-Business Suite. It exposes the progress-tracking records maintained by the Enterprise Data Warehouse (EDW) load framework, presenting the status of individual load operations performed against warehouse objects. The view joins the EDW load progress log to the EDW relations metadata view, resolving the technical object name into a descriptive long name for the related warehouse relation.

In Oracle EBS 12.1.1 and 12.2.2, this view serves as a read-only interface for monitoring EDW load activity, providing DBAs and integration developers with a stable, queryable surface over the underlying logging table. Because it is defined with a WITH READ ONLY clause, it is intended strictly for retrieval and reporting, not for transactional maintenance of load records. The documentation notes that the view is not implemented in the reference database, meaning availability depends on the deployment of the EDW/BIS schema in a given environment.

Underlying Base Objects

The view text is defined over two objects: EDW_LOAD_PROGRESS_LOG, a base table that stores the load log rows, and EDW_RELATIONS_MD_V, a metadata view that maps relation names to their descriptive long names. The join condition is LOG.OBJECT_NAME = REL.RELATION_NAME, so each row in the result set represents a load progress entry enriched with the relation long name as OBJECT_NAME. The documented ETRM metadata lists no referenced base objects beyond these, and provides no explicit owner. Note that the supplied view text contains a duplicated SELECT keyword and appears truncated; the operative definition is the join described above, with the projection list enumerating the columns shown in the column section.

Key Columns

• LOAD_FK — Foreign key linking the progress row to a parent load header record.
• OBJECT_NAME — The relation long name obtained from EDW_RELATIONS_MD_V, identifying the warehouse object being loaded.
• SEQ_ID — Sequence identifier ordering the steps or rows within a load.
• OBJ_ID — Identifier of the specific object instance involved in the load step.
• LOAD_PROGRESS — The progress or status value for the load step.
• START_DATE / END_DATE — Timestamps marking the beginning and completion of the load step.
• CATEGORY / OPERATION — Classification and operation type describing the load activity.
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATE_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each row.

Common Use Cases and Queries

Typical usage focuses on monitoring warehouse load runs, diagnosing stalled or failed steps, and reporting on load durations. A minimal query retrieves the latest activity:

• SELECT load_fk, object_name, load_progress, start_date, end_date FROM edw_load_progress_log_v ORDER BY start_date DESC;
• SELECT object_name, operation, category, load_progress FROM edw_load_progress_log_v WHERE load_progress <> 'COMPLETE';
• SELECT load_fk, object_name, (end_date - start_date) * 24 duration_hours FROM edw_load_progress_log_v WHERE end_date IS NOT NULL;
• SELECT created_by, COUNT(*) FROM edw_load_progress_log_v GROUP BY created_by;

These patterns support load-status dashboards, root-cause analysis of failed loads, and audit reporting. Because the view is read-only, all maintenance must target the base logging table directly through the EDW framework.