Search Results date_requested_fk

Overview

ISC_EDW_BOOKINGS_F_FCV is a flat-view construct within the Oracle E-Business Suite Order Management (ONT) schema, part of the Oracle Supply Chain (ISC) Enterprise Data Warehouse (EDW) family of database objects. Its name follows the EDW naming convention: "ISC_EDW" identifies the supply chain EDW layer, "BOOKINGS" identifies the business subject area (sales order bookings), "F" denotes a fact-style table, and "FCV" denotes the flattened, conformed view that presents the fact with surrogate key foreign-key resolution already applied. The view consolidates order header and order line data from the Order Management tables into a single denormalised row per booking line, joining in instance, currency, and set-of-books context. This positions it as a reporting and integration interface rather than a transactional object.

In Oracle EBS 12.1.1 and 12.2.2, the view is documented in the ETRM metadata with the note "Not implemented in this database," which indicates that the object is delivered as part of the EDW data-model definition but is created only in environments where the EDW build or extract process has been run. It is not a standard seeded runtime view in all ONT installations.

Underlying Base Objects

The ETRM metadata records no documented referenced base objects for ISC_EDW_BOOKINGS_F_FCV. The view text does, however, reference several underlying sources, including order header and line entities (aliased H and L) and the line instance (INST.INSTANCE_CODE). It also invokes EDW package functions — EDW_LOOKUP_PKG, EDW_TRD_PARTNER_PKG, EDW_GEOGRAPHY_PKG, EDW_TIME_PKG, EDW_CURRENCY, EDW_BIM_CMPGNS_PKG, EDW_BIM_EVTOFFERS_PKG, and EDW_DEMAND_CLASS_PKG — to resolve foreign keys to the EDW dimension tables. Because no base objects are formally documented in the ETRM entry, the authoritative source of lineage for a specific deployment is the view text stored in the data dictionary.

Key Columns

• BOOKINGS_PK — Concatenation of LINE_ID and INSTANCE_CODE, forming the composite primary key for a booking fact row.
• AGREEMENT_ID / AGREEMENT_TYPE_FK — Source agreement identifier and its resolved agreement-type lookup code.
• BILL_TO_CUST_FK / BILL_TO_LOC_FK / CUSTOMER_FK — Trade-partner and geography foreign keys derived from the invoice-to and sold-to organisation identifiers.
• CAMPAIGN_ACTL_FK / CAMPAIGN_INIT_FK / EVENT_OFFER_ACTL_FK — Marketing campaign and event offer keys resolved from line and header marketing source codes.
• CONFIGURATION_ITEM_FLAG — 'Y' where the line item type is a configuration, otherwise 'N'.
• CONVERSION_DATE / CONVERSION_RATE / CONVERSION_TYPE / CURRENCY_TRN_FK — Currency conversion context, including transactional currency and the user-defined or derived rate date.
• CANCEL_REASON_FK — Resolved cancellation reason, populated when a cancelled quantity exists.
• CUST_PO_NUMBER — Customer purchase order reference carried on the line.
• DATE_BOOKED_FK / DATE_PROMISED_FK / DATE_REQUESTED_FK / DATE_SCHEDULED_FK — EDW time-dimension keys for booked, promise, request, and schedule-ship dates.
• DEMAND_CLASS_FK — Resolved demand class for the line.

Regarding the searched term qty_ordered: this column is not shown in the excerpted view text, but a bookings fact of this type conventionally exposes ordered, cancelled, and fulfilled quantity measures. In a full deployment, quantity_ordered would be expected adjacent to the CANCELLED_QUANTITY reference used in the cancel-reason derivation.

Common Use Cases and Queries

The view supports bookings analysis — order intake, booking-to-book ratio, demand class and campaign attribution, and promised-versus-requested-date trending. A representative query aggregates ordered quantity by booked date key:

• SELECT DATE_BOOKED_FK, DEMAND_CLASS_FK, SUM(QTY_ORDERED) FROM ISC_EDW_BOOKINGS_F_FCV GROUP BY DATE_BOOKED_FK, DEMAND_CLASS_FK;
• SELECT BOOKINGS_PK, CUSTOMER_FK, CURRENCY_TRN_FK, CONVERSION_RATE FROM ISC_EDW_BOOKINGS_F_FCV WHERE CANCELLED_QUANTITY IS NOT NULL;
• SELECT CONFIGURATION_ITEM_FLAG, COUNT(*) FROM ISC_EDW_BOOKINGS_F_FCV GROUP BY CONFIGURATION_ITEM_FLAG;

Because the view resolves foreign keys through package functions, queries against it can be costly; filtering on keys and restricting the analysed date range before aggregation is recommended.