Results for “deliverable_id”

50+ results




Overview
Explore in AI Chat

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

Overview

OKE_DEPENDENCIES is a Project Contracts (OKE) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores dependency relationships related to contract deliverables. In the OKE schema, a single deliverable can support, precede, or trigger one or more other deliverables, and this table captures those linkages so the application can enforce sequencing, validate contract fulfillment logic, and report on downstream impacts when a deliverable is completed, revised, or cancelled.

The table is a pure intersection (junction) structure. It contains no descriptive business attributes beyond an optional DESCRIPTION column; its purpose is to bind two rows of OKE_K_DELIVERABLES_B together. Under the heuristic Data Vault classification mined from its foreign key structure, OKE_DEPENDENCIES is best modeled as a link table — a many-to-many relationship resolving two references to the same parent hub. This classification is a modeling suggestion derived from the FK topology, not an Oracle-declared designation.

Key Information Stored

  • DELIVERABLE_ID — Foreign key to OKE_K_DELIVERABLES_B. Identifies the primary deliverable in the relationship, i.e., the deliverable that carries or governs the dependency.
  • DEPENDENT_ID — Foreign key to OKE_K_DELIVERABLES_B. Identifies the deliverable that depends on, follows, or is constrained by the primary deliverable.
  • DESCRIPTION — Free-text explanation of the dependency, useful when reporting or auditing why two deliverables are linked.
  • CREATION_DATE, CREATED_BY — Standard WHO columns recording when and by whom the dependency row was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification and the login under which it occurred.

The table is defined with eight documented columns in total. The surrogate row identity is enforced by the primary key constraint OKE_DEPENDENCIES_PK, which is composed of (DELIVERABLE_ID, DEPENDENT_ID). Because the PK is itself a composite of the two business identifiers, the business-key candidate is the same pair, additionally guaranteed by the unique index OKE_DEPENDENCIES_U1 on (DELIVERABLE_ID, DEPENDENT_ID). There is no separate synthetic sequence column; uniqueness is entirely natural-key based, which also prevents a deliverable from being declared dependent on itself more than once.

Common Use Cases and Queries

Typical uses include dependency validation before a deliverable status change, impact analysis when a deliverable slips, and reporting on deliverable networks within a contract or project.

  • Direct dependents of a deliverable: SELECT DEPENDENT_ID FROM OKE_DEPENDENCIES WHERE DELIVERABLE_ID = :p_deliverable_id;
  • Predecessors of a deliverable: SELECT DELIVERABLE_ID FROM OKE_DEPENDENCIES WHERE DEPENDENT_ID = :p_deliverable_id;
  • Join to deliverable detail: join OKE_DEPENDENCIES to OKE_K_DELIVERABLES_B twice — once on DELIVERABLE_ID and once on DEPENDENT_ID — to resolve both names for a dependency report.
  • Impact/closure analysis: traverse the table recursively to find all deliverables transitively dependent on a given deliverable before closing or cancelling it.
  • Audit and orphan checks: filter on LAST_UPDATE_DATE to find recently created dependencies, and use the two foreign keys to detect rows referencing deleted or inactive deliverables.

Related Objects

  • OKE_K_DELIVERABLES_B — Referenced twice: via OKE_DEPENDENCIES.DELIVERABLE_ID and OKE_DEPENDENCIES.DEPENDENT_ID. This is the primary parent table and the principal join target.
  • OKE_K_DELIVERABLES_TL — Translation table supplying the language-specific deliverable name and description for reporting joins.
  • OKE_DELIVERABLES — The operational view/entity layer over the deliverable base tables, commonly queried alongside dependency data.
  • OKE_DEPENDENCIES_PK / OKE_DEPENDENCIES_U1 — The primary key constraint and unique index that enforce the composite natural key.
  • OKE_CONTRACTS / OKE_K_HEADERS — Contract header structures that own the deliverables participating in these dependencies, used for contract-level rollups.
  • OKE Project Contracts APIs — Deliverable maintenance and contract management APIs that insert, update, or delete dependency rows as deliverables are added or reordered.