Search Results shipment_quantity




Overview
Explore in AI Chat

Overview

OKE_DD250_LINES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE – Project Contracts product family. It exposes stored line-level information captured by the DD250 form, the U.S. Government material inspection and receiving report used in government contracting and contract deliverables management. The view is defined as a join between the DD250 header view (OKE_DD250_HEADERS_V) and the underlying DD250 line storage object (OKE_K_FORM_LINES), producing a flattened, report-friendly record set in which header attributes are denormalized onto each line.

Because the DD250 line data physically resides in a generic key-flexfield style storage table (OKE_K_FORM_LINES, with generic TEXT01–TEXT07 and NUMBER01–NUMBER03 columns), the view's principal role is to present those generic attribute slots under meaningful business column names such as SHIPMENT_QUANTITY, PART_NUMBER, NATIONAL_STOCK_NUMBER, and UNIT_PRICE. This abstraction shields report developers and integration interfaces from the physical DFF-style column layout and provides a stable projection for downstream reporting. Status is VALID, indicating the view compiles successfully in the supported releases (12.1.1 and 12.2.2).

Underlying Base Objects

The view definition is a single equi-join on FORM_HEADER_ID:

The join predicate L.FORM_HEADER_ID = H.FORM_HEADER_ID links each stored line to its parent DD250 header. Because the header side is itself a view, the lineage ultimately traces to the Project Contracts contract and deliverable structures, while the line side remains a physical key-form table. The dependency on a synonym rather than a table name means the actual line table resolves through the APPS synonym definitions and may point to an OKE base table at runtime.

Key Columns

The documented column list combines projection expressions and alias-named attributes. Notable columns include:

  • FORM_HEADER_ID / FORM_HEADER_NUMBER / FORM_LINE_NUMBER — the primary relational keys identifying header and line.
  • FORM_DATE, STATUS_CODE — header-level date and workflow/processing status.
  • CONTRACT_NUMBER, ORDER_NUMBER, SHIPMENT_NUMBER — contractual context carried down from the header, used to reconcile lines to the procurement or contract shipment.
  • K_HEADER_ID, K_LINE_ID, DELIVERABLE_ID — internal identifiers linking the DD250 record to Project Contracts deliverable structures.
  • PART_NUMBER, NATIONAL_STOCK_NUMBER, ITEM_DESCRIPTION, LINE_NUMBER, LINE_DESCRIPTION, LINE_COMMENTS — item identification and descriptive attributes mapped from the generic TEXT slots.
  • SHIPMENT_QUANTITY, UOM_CODE, UNIT_PRICE, AMOUNT — the quantitative and pricing metrics mapped from the generic NUMBER slots; SHIPMENT_QUANTITY is the searched attribute and represents the quantity shipped for the DD250 line.

Common Use Cases and Queries

Typical use is quantitative and item-level reporting on DD250 submissions, reconciliation of shipment quantities against contract shipments, and extraction feeds for government reporting or interface programs. A representative query returning shipment quantities with their contractual context:

  • SELECT form_header_number, form_line_number, contract_number, shipment_number, part_number, shipment_quantity, uom_code, unit_price, amount FROM apps.oke_dd250_lines_v WHERE shipment_quantity IS NOT NULL ORDER BY form_header_number, form_line_number;
  • SELECT contract_number, part_number, SUM(shipment_quantity) total_shipped FROM apps.oke_dd250_lines_v GROUP BY contract_number, part_number;
  • Filter by STATUS_CODE to restrict results to accepted or processed DD250 forms.

Because the view performs no aggregation or filtering, it is suitable as a base for both detail and summary extracts; performance is governed by the join on FORM_HEADER_ID, and appropriate indexes on the underlying line storage table support efficient retrieval.