Results for “requested_quantity_uom”

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

Overview

The view APPS.OKE_BILLABLE_DELIVERABLES_V belongs to the OKE – Project Contracts product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes contract deliverables that are eligible for billing, filtering the deliverable base records to those marked both billable and ready to bill. The view therefore acts as a consolidated reporting and integration surface for downstream billing processes, allowing receivables, project billing, and custom extensions to retrieve deliverable-level billing candidates without reapplying the eligibility predicates.

The presence of the derived column SHIPPED_QUANTITY makes the view particularly valuable where billing is driven by actual shipment activity. Rather than storing a shipped quantity natively, the view computes it at runtime from delivery records linked back to the contract deliverable, applying UOM conversion where the requested unit of measure differs from the deliverable's own UOM. This design keeps the view aligned with live shipping data maintained in the Order Management delivery tables.

Underlying Base Objects

The documented base objects referenced by the view are:

• OKE_K_DELIVERABLES_B (synonym) – the primary deliverable table supplying the driving rows.
• OKC_K_LINES_B (synonym) – supplies contract line information such as LINE_NUMBER.
• MTL_PARAMETERS (synonym) – outer-joined to provide the inventory organization context and code.
• MTL_ITEM_FLEXFIELDS (view) – outer-joined to expose item descriptive flexfield attributes and the item number.
• WSH_DELIVERY_DETAILS (synonym) – queried in a correlated subquery to derive SHIPPED_QUANTITY.
• INV_CONVERT (package) – invoked within the subquery via INV_UM_CONVERT to normalize shipped quantities to the deliverable UOM.

The deliverable table is joined to OKC_K_LINES_B on L.ID = D.K_LINE_ID. The inventory organization and item joins are outer joins, so deliverables without a valid organization or item assignment are still returned. The shipped-quantity subquery restricts delivery details to SOURCE_CODE = 'OKE' and matches SOURCE_HEADER_ID to K_HEADER_ID and SOURCE_LINE_ID to DELIVERABLE_ID.

Key Columns

• ROW_ID – the rowid of the underlying deliverable record.
• K_HEADER_ID / K_LINE_ID – contract header and line identifiers that anchor the deliverable.
• LINE_NUMBER – the contract line number from OKC_K_LINES_B.
• DELIVERABLE_ID / DELIVERABLE_NUM – the unique deliverable key and its user-facing number.
• PROJECT_ID / TASK_ID – the project and task to which the deliverable belongs.
• INVENTORY_ORG_ID / INVENTORY_ORG_CODE – the shipping inventory organization.
• ITEM_ID / ITEM_NUMBER – the shipped or deliverable item.
• DELIVERY_DATE – the scheduled or actual delivery date.
• QUANTITY – the contractual deliverable quantity.
• SHIPPED_QUANTITY – the summed shipped quantity from delivery details, converted to the deliverable UOM. Where REQUESTED_QUANTITY_UOM is null, the raw shipped quantity is used; otherwise the conversion package normalizes it.
• UOM_CODE, UNIT_PRICE, CURRENCY_CODE – pricing and unit-of-measure attributes used in billing calculations.

Common Use Cases and Queries

Typical use cases include identifying deliverables ready for invoice generation, reconciling contractual versus shipped quantities, and building custom billing reports. A simple retrieval of billable deliverables with shipment status follows:

• SELECT deliverable_num, line_number, item_number, quantity, shipped_quantity, uom_code, unit_price, currency_code FROM apps.oke_billable_deliverables_v WHERE k_header_id = :p_contract_id;
• SELECT deliverable_id, SUM(shipped_quantity) FROM apps.oke_billable_deliverables_v GROUP BY deliverable_id;
• Filtering for under-shipped deliverables: WHERE shipped_quantity < quantity.

Because eligibility predicates (BILLABLE_FLAG = 'Y' and READY_TO_BILL = 'Y') are embedded in the view definition, consumers can rely on the result set directly rather than reproducing these conditions. The outer joins preserve deliverables lacking organization or item data, so reporting logic should account for potentially null organization and item columns.