Results for “batch_entity_object_id”

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

Overview

The EGO_PUB_BATCH_STATUS_VL view is a public, translation-enabled (_VL) database object owned by the APPS schema within the Oracle E-Business Suite Advanced Product Catalog (EGO) module. It exposes the publication status of batch entities processed through the catalog publication framework. Each row represents the combination of a publication batch, the individual entity object belonging to that batch, and the current processing status recorded for that entity.

The view is primarily consumed by reporting, diagnostics, and integration components that require visibility into whether catalog items, attributes, or related entities were successfully published, failed, or are awaiting processing. Because it joins to FND_LOOKUPS for status translation and to HZ_ORIG_SYSTEMS_VL for the originating system, the view is well suited for cross-system publication auditing in multi-source environments. The user search for status_description corresponds directly to a column exposed here; that column returns the descriptive text associated with the lookup meaning of STATUS_CODE, providing a human-readable status narrative alongside the code.

Underlying Base Objects

The view definition joins five documented objects:

• EGO_PUB_BAT_ENT_OBJS_B — the batch entity objects table, supplying entity object identifiers and primary key values.
• EGO_PUB_BAT_HDR_B — the batch header table, supplying batch name, type, responsibility, and creation metadata.
• EGO_PUB_BAT_STATUS_B — the batch status base table, supplying status codes, messages, and per-entity status rows.
• HZ_ORIG_SYSTEMS_VL — the origin systems view, supplying system code and system name for the source of the publication.
• FND_LOOKUPS — the standard lookup view, filtered to lookup type EGO_PUBLICATION_STATUS, providing the meaning and description for each status code.

The join is anchored on BATCH_ID across the header, entity objects, and status tables, with a further match on BATCH_ENTITY_OBJECT_ID between entity objects and status. This means each output row is uniquely scoped to a single entity within a single batch at a single status. Note that the metadata also references FND_GLOBAL as a package dependency in the documented object list; while it does not appear in the excerpted SQL, it is commonly used to supply session context such as user or responsibility, and its presence confirms a dependency recorded at compile time.

Key Columns

• BATCH_ID, BATCH_NAME, BATCH_TYPE — identify and classify the publication batch.
• STATUS_CODE — the raw lookup code from EGO_PUBLICATION_STATUS.
• STATUS — the lookup MEANING, a user-facing status label.
• STATUS_DESCRIPTION — the lookup DESCRIPTION; this is the column matching the user's search term and provides extended context for the status.
• MESSAGE — the diagnostic or error text recorded against the entity status row.
• SYSTEM_CODE, SYSTEM_NAME — the originating system that produced the published entity.
• ENTITY_TYPE_ID, BATCH_ENTITY_OBJECT_ID — classify the specific catalog entity being published.
• PK1_VALUE … PK5_VALUE — the composite key identifying the underlying entity record.
• PUBLISHED_BY, BATCH_CREATION_DATE, CREATED_BY — audit and ownership attributes.
• USER_ENTERED, RESPONSIBILITY_ID — indicate manual entry and the responsibility under which the batch was created.

Common Use Cases and Queries

Typical scenarios include monitoring publication outcomes for a specific batch, isolating failed entities with explanatory messages, and reconciling published content against source systems.

To list status distribution for a batch:

• SELECT b.batch_name, s.status, s.status_description, s.system_name, COUNT(*) FROM ego_pub_batch_status_vl s, ... grouping by status.

To retrieve failures with detail:

• SELECT batch_id, pk1_value, status, status_description, message FROM ego_pub_batch_status_vl WHERE status_code = 'FAILED';

To filter by the searched term directly:

• SELECT batch_name, status_description FROM ego_pub_batch_status_vl WHERE status_description IS NOT NULL;

Because the view is translation-enabled, queries run under an appropriate language context return localized lookup descriptions where available.