Search Results booked_date

Overview

The GMP_SR_BOOKING_DATA_V view resides in the APPS schema and belongs to the GMP – Process Manufacturing Process Planning product family. It serves as a placeholder view within the Oracle E-Business Suite 12.1.1 and 12.2.2 technical stack. The view exposes a set of columns representing booking data — quantities ordered, dates, customer, item, sales channel, and sales representative attributes — yet its defining query is structurally empty. The view definition selects a series of strongly typed NULL literals from SYS.DUAL and applies the predicate WHERE 1 <> 1, guaranteeing that no rows are ever returned.

This pattern identifies GMP_SR_BOOKING_DATA_V as a stub or interface contract. In Process Manufacturing Process Planning, such views are frequently created to establish a stable column signature that downstream reports, concurrent programs, or integration adapters can reference before the physical implementation is finalized, or as a deliberately suppressed data source in configurations where booking data is not populated. Because the object is marked VALID, it compiles successfully and can be queried without error, though it yields an empty result set.

Underlying Base Objects

According to the documented ETRM metadata, the only referenced base object is DUAL, the standard Oracle single-row pseudo-table owned by SYS. The view does not join to any Process Manufacturing, Order Management, or Advanced Supply Chain Planning tables. Each projected column is the result of either TO_NUMBER(NULL), TO_DATE(NULL), or a bare NULL, meaning the column list is defined purely to establish datatypes and aliases rather than to retrieve persisted data.

Consequently, the view has no dependency on booking, order, or inventory base tables. The absence of real base objects confirms that no business logic is implemented within the view. Any application code or user query relying on this view will receive zero rows, and the metadata gives no indication of a companion table from which it will later be sourced.

Key Columns

The view exposes twenty-four columns spanning identifiers, descriptive attributes, dates, and measures:

• SR_INV_ORG_PK / INV_ORG – Inventory organization identifier and name.
• SR_ITEM_PK / ITEM – Item surrogate key and item identifier.
• SR_CUSTOMER_PK / CUSTOMER – Customer surrogate key and customer reference.
• SR_SALES_CHANNEL_PK / SALES_CHANNEL – Sales channel key and description.
• SR_SALES_REP_PK / SALES_REP – Sales representative key and name.
• SR_SHIP_TO_LOC_PK / SHIP_TO_LOC – Ship-to location key and value.
• BOOKED_DATE, REQUESTED_DATE, PROMISED_DATE, SCHEDULED_DATE – Date milestones associated with a booking.
• AMOUNT – Monetary amount for the booking.
• QTY_ORDERED – Numeric quantity ordered; this is the column most commonly matched during keyword searches such as the user's "qty_ordered" query.
• SR_USER_DEFINED1_PK / USER_DEFINED1, SR_USER_DEFINED2_PK / USER_DEFINED2 – Flexible user-defined attribute pairs for extensibility.
• SR_ORIGINAL_ITEM_PK / SR_PARENT_ITEM_PK – Keys supporting parent and original item relationships.

All columns are declared through NULL casts, so no default value, constraint, or derivation is applied. The SR_ prefix denotes the source structure from which the eventual data would be drawn.

Common Use Cases and Queries

Because the view returns no rows, the primary practical uses are schema discovery, column-contract validation, and dependency auditing rather than reporting. Developers may query ALL_TAB_COLUMNS to confirm the expected interface, or test whether customizations reference a populated booking source. A representative query is:

• SELECT item, customer, qty_ordered, booked_date FROM apps.gmp_sr_booking_data_v WHERE qty_ordered > 0; — returns no rows given the WHERE 1 <> 1 predicate.
• SELECT column_name, data_type FROM all_tab_columns WHERE table_name = 'GMP_SR_BOOKING_DATA_V' ORDER BY column_id; — inventories the column contract.
• SELECT object_name, status FROM all_objects WHERE object_name = 'GMP_SR_BOOKING_DATA_V'; — verifies the VALID compilation state.

Any requirement for actual booked-quantity reporting must therefore target the physical order or planning tables underlying the intended data, not this placeholder view.