Search Results oke_dependencies




Overview
Explore in AI Chat

Overview

The OKE_DEPENDENCIES table is a core data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. Its primary function is to model and store dependency relationships between contract deliverables. In the context of project contract management, deliverables often have logical or sequential dependencies—where the start, completion, or approval of one deliverable is contingent upon the status of another. This table provides the structural foundation for defining and enforcing these business rules, enabling accurate scheduling, milestone tracking, and fulfillment workflows for complex contractual agreements in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is purposefully simple, designed to capture the essential link between two deliverables. As defined by its primary key constraint (OKE_DEPENDENCIES_PK), the table is centered on two critical columns: DELIVERABLE_ID and DEPENDENT_ID. Both columns store identifiers that reference records in the OKE_K_DELIVERABLES_B table. The DELIVERABLE_ID represents the prerequisite or predecessor deliverable, while the DEPENDENT_ID represents the deliverable that is contingent upon it. This relationship allows for the modeling of various dependency types, such as finish-to-start, which are typically managed by application logic built upon this foundational data store.

Common Use Cases and Queries

This table is central to processes involving deliverable scheduling and status propagation. A common use case is generating a report of all dependencies for a specific contract to analyze the critical path. Application logic will query this table to validate if a user can mark a deliverable as complete, checking that all its prerequisite deliverables (as defined in OKE_DEPENDENCIES where it is the DEPENDENT_ID) are satisfied. A typical analytical query might join OKE_DEPENDENCIES to OKE_K_DELIVERABLES_B twice to fetch the names and details of both the prerequisite and dependent deliverables:

  • SELECT d.deliverable_id, pre.name prerequisite_name, dep.name dependent_name
  • FROM oke_dependencies d,
  • oke_k_deliverables_b pre,
  • oke_k_deliverables_b dep
  • WHERE d.deliverable_id = pre.deliverable_id
  • AND d.dependent_id = dep.deliverable_id
  • AND pre.contract_id = :p_contract_id;

Related Objects

The OKE_DEPENDENCIES table has a tightly coupled relationship with the core deliverables table. As documented in the provided metadata, it maintains two foreign key relationships to the OKE_K_DELIVERABLES_B table, ensuring referential integrity for both sides of the dependency link.

  • OKE_K_DELIVERABLES_B (via DELIVERABLE_ID): This foreign key constraint ensures that every prerequisite deliverable ID stored in OKE_DEPENDENCIES exists as a valid record in the master deliverables table.
  • OKE_K_DELIVERABLES_B (via DEPENDENT_ID): This foreign key constraint ensures that every dependent deliverable ID is also a valid record in OKE_K_DELIVERABLES_B.

This table is primarily accessed and managed through the OKE Project Contracts application interface, which provides screens for defining deliverable dependencies. Direct data manipulation should be performed with caution and typically only via supported APIs to maintain business rule integrity.