Results for “status_code”

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

Overview

EGO_PUB_BAT_STATUS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the EGO — Advanced Product Catalog product family. It exposes the runtime status of batch operations executed by the Advanced Product Catalog batch framework. The EGO module relies on a batch architecture to process large, long-running catalog and item operations asynchronously, such as bulk item imports, catalog category assignments, attribute enrichment, and mass updates driven by the Product Information Management (PIM) workbench.

Because batch processing is asynchronous, callers need a stable reporting surface to determine whether a submitted request has succeeded, failed, or is still in progress, and to retrieve any error text. EGO_PUB_BAT_STATUS_V provides exactly that surface, presenting one row per batch entity tracked by the framework. It is a public interface view, indicated by the _PUB_ naming segment, and is intended for both internal EGO processing logic and external integration consumers that submit batch requests and poll for completion. Its read-only definition enforces that status information is consumed, never modified, through this object — all writes occur against the underlying base table.

Underlying Base Objects

The documented metadata for ETRM 12.2.2 identifies the view as defined solely over the table EGO_PUB_BAT_STATUS_B, accessed through a synonym in the APPS schema. The view text is a direct, unfiltered projection:

• SELECT BATCH_ID, SYSTEM_CODE, BATCH_ENTITY_OBJECT_ID, STATUS_CODE, MESSAGE FROM EGO_PUB_BAT_STATUS_B WITH READ ONLY

There is no join, aggregation, translation, or decode logic. The WITH READ ONLY clause guarantees that no DML is possible through the view, which simplifies security review: consumers granted SELECT on the view cannot mutate batch data. Because the view maps one-to-one with the base table, it carries the same row cardinality and grain as EGO_PUB_BAT_STATUS_B. The same structure is documented for both Oracle EBS 12.1.1 and 12.2.2, so query logic written against this view is portable across those releases.

Key Columns

• BATCH_ID — Identifier of the batch run to which the row belongs. This is the primary grouping key used to correlate a submitted batch with all of its constituent entity rows.
• SYSTEM_CODE — Short code identifying the source system or product context that owns the batch operation, allowing multiple consumers to share the status table without collision.
• BATCH_ENTITY_OBJECT_ID — Identifier of the individual entity processed within the batch, expressed as the object ID of the entity type being handled. This is the column most frequently referenced in troubleshooting queries, since it links a status record back to the specific item, catalog, or other catalog object being processed. Users searching for "batch_entity_object_id" typically trace a failing or stalled entity through this column.
• STATUS_CODE — Coded outcome of the entity's processing, distinguishing states such as success, failure, warning, or in-progress. Application logic branches on this value to determine whether reprocessing or correction is required.
• MESSAGE — Free-text detail accompanying the status, typically carrying error messages or informational diagnostics when STATUS_CODE indicates a non-success outcome.

Common Use Cases and Queries

Typical scenarios include monitoring the progress of a submitted batch, diagnosing individual entity failures, and reporting batch success rates. Because the view is a direct projection of the base table, queries should always filter on BATCH_ID or SYSTEM_CODE to avoid full-table scans on large status histories.

To retrieve the full status of a known batch:

• SELECT batch_id, system_code, batch_entity_object_id, status_code, message FROM ego_pub_bat_status_v WHERE batch_id = :p_batch_id;

To isolate failures within a batch:

• SELECT batch_entity_object_id, message FROM ego_pub_bat_status_v WHERE batch_id = :p_batch_id AND status_code <> 'SUCCESS';

To trace the batch history of a specific entity, the column users most often search for is used directly:

• SELECT batch_id, status_code, message FROM ego_pub_bat_status_v WHERE batch_entity_object_id = :p_entity_id ORDER BY batch_id DESC;

Joining the view to EGO item or catalog entities on BATCH_ENTITY_OBJECT_ID allows reconciliation reports that pair each entity's descriptive attributes with its processing outcome. For integration polling, a periodic query filtered by BATCH_ID and aggregated on STATUS_CODE provides the completion status without exposing the base table.