Results for “initiate_shipment_date”

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

Overview

The APPS.OKE_K_DELIVERABLES_VLH view is a reporting and integration object within the Oracle E-Business Suite Project Contracts (OKE) module. Its documented description identifies it as a "Contract deliverable infomation history view." In practice, the view exposes the full attribute set of contract deliverables — items, schedules, shipping details, billing flags, and descriptive flexfields — joined to project, task, and status reference data, so that downstream processes, concurrent programs, and custom reports can retrieve a single flattened row per deliverable instead of assembling the constituent tables themselves.

The _VLH suffix reflects the view-family naming convention in OKE, where a view is layered over a base table (typically _B), a translation table (_T), and a historical or "audit" table. This view serves as a read-only projection intended for inquiry, not transaction entry; the underlying deliverable rows are maintained by the Project Contracts deliverable workflows. Because it is owned by APPS and marked VALID in the ETRM 12.2.2 repository, it is safe for direct querying by reporting tools, OBIEE/BI Publisher extracts, and PL/SQL integration code.

Underlying Base Objects

The documented referenced base objects for the view are:

• OKE_K_DELIVERABLES_BH (SYNONYM) — the base deliverable history table, supplying the primary deliverable attributes. The alias B in the view text corresponds to this object.
• OKE_K_DELIVERABLES_TLH (SYNONYM) — the translation/history table holding the descriptive fields and SFWT_FLAG, accessed via alias T.
• OKC_STATUSES_V (VIEW) — the status lookup view, joined to resolve STATUS_CODE into the descriptive MEANING.
• PA_PROJECTS_ALL (SYNONYM) — the Projects table, providing SEGMENT1 and NAME for the deliverable's project.
• PA_TASKS (SYNONYM) — the Tasks table, providing TASK_NAME, TASK_NUMBER, and DESCRIPTION.

The view therefore joins one governing business entity (the contract deliverable) to three reference dimensions (project, task, status) plus its own translation row. It does not independently persist data; all columns are projected from these base objects.

Key Columns

The view exposes the complete deliverable column set. The most significant columns include:

• DELIVERABLE_ID — primary key of the deliverable, the join key for all related transaction tables.
• DELIVERABLE_NUM — user-facing deliverable number.
• K_HEADER_ID / K_LINE_ID — foreign keys to the contract header and line, anchoring the deliverable to its contractual context.
• PROJECT_ID / TASK_ID — the project and task to which the deliverable is assigned; expanded via SEGMENT1, NAME, TASK_NAME, and TASK_NUMBER.
• SUB_REF_ID — the sub-reference identifier that ties the deliverable to its associated sub-entity (for example, a submission or shipment reference), and the column most commonly used to correlate deliverables with downstream references.
• DELIVERY_DATE, START_DATE, END_DATE, NEED_BY_DATE, AS_OF_DATE — the scheduling attributes driving deliverable timing and history.
• STATUS_CODE / MEANING — the deliverable status, resolved to a readable value via OKC_STATUSES_V.
• DIRECTION, SHIP_TO_ORG_ID, SHIP_FROM_ORG_ID, INVENTORY_ORG_ID — the direction of the deliverable and the shipping/inventory organizations involved.
• BILLABLE_FLAG, BILLING_EVENT_ID, READY_TO_BILL — billing indicators used by revenue and invoicing processes.
• WF_ITEM_KEY — the workflow item key used to locate the deliverable in the Oracle Workflow engine.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — the descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

Common Use Cases and Queries

The view is typically queried to report deliverable status, to reconcile deliverables against contract lines, and to feed shipping, billing, or workflow integrations. Because SUB_REF_ID is frequently the search term, a common pattern is to locate all deliverables sharing a sub-reference value:

SELECT deliverable_id, deliverable_num, k_header_id, k_line_id,
       project_id, task_id, sub_ref_id, status_code, deliveRY_date
FROM   apps.oke_k_deliverables_vlh
WHERE  sub_ref_id = :p_sub_ref_id;

Another routine use is to list open, billable deliverables for a given project and contract:

SELECT d.deliverable_num, p.segment1, p.name project_name,
       t.task_number, t.task_name, d.meaning status_meaning,
       d.need_by_date, d.unit_price, d.quantity
FROM   apps.oke_k_deliverables_vlh d,
       apps.pa_projects_all p,
       apps.pa_tasks t
WHERE  d.project_id = p.project_id
AND    d.task_id = t.task_id
AND    d.billable_flag = 'Y'
AND    d.status_code NOT IN ('CLOSED','CANCELLED');

Because the view is a simple projection rather than a stored snapshot, queries reflect the current state of the base deliverable tables and their translations. For point-in-time comparisons, the underlying _BH and _TLH history objects should be consulted directly.