Search Results contracts




The OKE_K_DELIVERABLES_B table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical data structure within the Oracle Contracts Core module, specifically supporting the management of contract deliverables. This table stores the base transactional data for deliverables associated with contract agreements, ensuring proper tracking, fulfillment, and compliance with contractual obligations. Below is a detailed technical and functional breakdown of this table.

Table Overview

The OKE_K_DELIVERABLES_B table is part of the Oracle Contracts Core schema and serves as the foundation for deliverables tracking in contract management. It is linked to other key tables like OKE_K_HEADERS_B (contract headers) and OKE_K_LINES_B (contract lines) to maintain relational integrity. The "_B" suffix indicates it is a base table, meaning it stores raw transactional data without UI-specific attributes, which are typically housed in "_TL" (translated) or "_VL" (view) tables.

Key Columns and Structure

The table includes columns that define deliverable attributes, relationships, and statuses. Notable columns include:
  • DELIVERABLE_ID: Primary key uniquely identifying each deliverable.
  • CONTRACT_ID: Foreign key linking to OKE_K_HEADERS_B, associating the deliverable with a contract.
  • LINE_ID: Optional foreign key linking to OKE_K_LINES_B if the deliverable is tied to a specific contract line.
  • DELIVERABLE_NUMBER: User-assigned identifier for the deliverable.
  • DESCRIPTION: Detailed description of the deliverable.
  • STATUS_CODE: Tracks lifecycle status (e.g., "DRAFT," "APPROVED," "COMPLETED").
  • DUE_DATE: Scheduled fulfillment date.
  • ACTUAL_COMPLETION_DATE: Timestamp when the deliverable was fulfilled.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE: Standard Oracle audit columns.

Functional Role

This table supports core contract management processes:
  1. Deliverable Tracking: Captures contractual obligations (e.g., reports, milestones, goods) and their fulfillment status.
  2. Compliance Monitoring: Enables alerts for overdue deliverables via STATUS_CODE and date fields.
  3. Integration: Serves as a source for downstream systems like Oracle Projects or Procurement, ensuring alignment with execution workflows.

Integration Points

The table interacts with:
  • Workflow Engine: Triggers notifications for pending deliverables based on DUE_DATE and STATUS_CODE.
  • Oracle Projects: Links deliverables to project tasks via PROJECT_ID or TASK_ID columns, if configured.
  • Reporting: Feeds data to Oracle BI Publisher for contract performance dashboards.

Technical Considerations

  • Indexing: Key columns like DELIVERABLE_ID, CONTRACT_ID, and STATUS_CODE are typically indexed for performance.
  • Partitioning: In high-volume environments, partitioning by CONTRACT_ID or DUE_DATE may be implemented.
  • API Support: Oracle provides PL/SQL APIs (e.g., OKE_DELIVERABLES_PUB) for programmatic access to this table.

Customization and Extensions

Organizations often extend this table with custom columns (e.g., ATTRIBUTE1-15) to capture industry-specific data. However, such modifications require careful testing to avoid conflicts with standard Oracle patches.

Conclusion

The OKE_K_DELIVERABLES_B table is a pivotal component in Oracle EBS Contracts Core, providing the structural foundation for managing contractual deliverables. Its design ensures seamless integration with other EBS modules while offering flexibility for customization. Proper utilization of this table enhances contract compliance, reduces manual tracking efforts, and improves operational visibility.