Search Results okc_bus_doc_events_b




Overview
Explore in AI Chat

Overview

The OKC_BUS_DOC_EVENTS_B table is a foundational data dictionary table within the Oracle E-Business Suite Contracts Core (OKC) module. It functions as a master repository for valid business document events, which are predefined, system-recognized occurrences within the lifecycle of a contract or agreement. These events are not user-generated but are seeded by the application, with a distinct set of events defined for each type of business document (e.g., Sales Contract, Purchase Agreement). The table's primary role is to provide a standardized, referential list of events that other application components, such as deliverable scheduling, can utilize to trigger or anchor business logic and date calculations.

Key Information Stored

While the full column list is not detailed in the provided metadata, the documented relationships and primary key reveal the core structure. The central column is BUS_DOC_EVENT_ID, which serves as the primary key and unique identifier for each seeded event. Another critical column is BUS_DOC_TYPE, which acts as a foreign key linking to the OKC_BUS_DOC_TYPES_B table. This relationship ensures that each event is explicitly associated with a specific business document type. Typical data would include seeded rows for events like "Contract Signed," "Effective Date," "Termination Notice," or "Renewal Date," each tied to its applicable document type.

Common Use Cases and Queries

The primary use case for this table is to support the definition and management of deliverables and milestone dates in contracts. When configuring a deliverable, users can select a business document event as a relative anchor point for the start or end date. For example, a deliverable's start date could be configured as "30 days after the Contract Signed event." Common queries involve listing all available events for a given document type or validating event IDs used in configuration. A typical reporting query might join this table to deliverables to understand date dependencies.

  • List all seeded events for a specific business document type: SELECT * FROM okc_bus_doc_events_b WHERE bus_doc_type = 'SALES_ORDER';
  • Find deliverables anchored to a specific event: SELECT d.* FROM okc_deliverables d WHERE d.relative_st_date_event_id = <EVENT_ID>;

Related Objects

The table maintains defined relationships with other core Contracts tables, as per the provided metadata.

  • OKC_BUS_DOC_TYPES_B: This table is referenced via the foreign key on the BUS_DOC_TYPE column. It defines the valid business document types for which events are seeded.
  • OKC_DELIVERABLES: This table references OKC_BUS_DOC_EVENTS_B twice. The columns RELATIVE_ST_DATE_EVENT_ID and RELATIVE_END_DATE_EVENT_ID are foreign keys to BUS_DOC_EVENT_ID, allowing deliverables to use these seeded events as relative date anchors for scheduling.