Results for “object_level”

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

Overview

OE_FLOW_STATUS_AIA_SYNC_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ONT – Order Management product family. According to its documented description, the view exists specifically to support the AIA UI (AIA Sales Order Status Synchronization) integration layer, allowing external applications and integration flows to query the FLOW STATUS field of a sales order without accessing the underlying transactional tables directly.

The view exposes a compact, denormalized result set that combines flow status codes with their descriptive lookup meanings. It is registered in the ETRM repository with a status of VALID and is intended to be referenced by integration middleware, business intelligence extracts, and diagnostic queries that need to reconcile order flow status between EBS and an AIA-driven service-oriented architecture.

Underlying Base Objects

The view is defined over two documented objects:

• OE_FLOW_STATUS_AIA_SYNC (SYNONYM) — the primary source of flow status records, including the object level, synchronization flag, and standard audit columns.
• OE_LOOKUPS (VIEW) — a lookup view used to resolve the FLOW_STATUS_CODE into a user-facing MEANING value.

The join condition links OFS.FLOW_STATUS_CODE to LKUP.LOOKUP_CODE, restricted by the predicate LKUP.LOOKUP_TYPE = 'LINE_FLOW_STATUS'. This constrains the result set to line-level flow statuses only, which is significant when filtering or grouping by OBJECT_LEVEL, since the lookup restriction prevents unrelated lookup codes from appearing in the output.

Key Columns

• FLOW_STATUS_CODE — the internal status code for the order flow, joined to the lookup table.
• OBJECT_LEVEL — indicates the level of the object to which the flow status applies (for example, header or line), and is the column most commonly used for filtering and grouping.
• SYNC_REQD_FLAG — a flag indicating whether the record requires synchronization by the AIA integration layer. This is central to incremental extract routines.
• FLOW_STATUS — the descriptive meaning of the flow status code, derived from the OE_LOOKUPS lookup join.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard who-columns supporting audit, delta extraction, and change tracking.

Common Use Cases and Queries

The view is typically queried to drive AIA synchronization jobs, to report on pending flow status changes, or to validate order status values presented in integrated user interfaces. A representative query filtering on the object level and outstanding synchronization is:

SELECT FLOW_STATUS_CODE, OBJECT_LEVEL, FLOW_STATUS, SYNC_REQD_FLAG, LAST_UPDATE_DATE FROM APPS.OE_FLOW_STATUS_AIA_SYNC_V WHERE SYNC_REQD_FLAG = 'Y' AND OBJECT_LEVEL = 'LINE' ORDER BY LAST_UPDATE_DATE;

A summary query used for reconciliation reporting might group by status and level:

SELECT OBJECT_LEVEL, FLOW_STATUS, COUNT(*) AS STATUS_COUNT FROM APPS.OE_FLOW_STATUS_AIA_SYNC_V GROUP BY OBJECT_LEVEL, FLOW_STATUS ORDER BY OBJECT_LEVEL, FLOW_STATUS;

Delta extraction for downstream integration can use the audit columns: SELECT FLOW_STATUS_CODE, OBJECT_LEVEL, SYNC_REQD_FLAG FROM APPS.OE_FLOW_STATUS_AIA_SYNC_V WHERE LAST_UPDATE_DATE >= :last_run_date AND SYNC_REQD_FLAG = 'Y';

Because the view already resolves lookup meanings through OE_LOOKUPS, reports and integration interfaces avoid the need to join the lookup table separately, simplifying both SQL and the mapping definitions used in AIA.