Results for “bus_doc_type”

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

Overview

OKC_BUS_DOC_EVENTS_B is a foundational setup table within the Oracle Contracts Core (OKC) module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores the valid business document events that the Contracts application recognizes for each business document type. These events are seeded per business document type, meaning the table acts as a controlled reference list of lifecycle milestones — such as document creation, approval, signature, and termination — that can occur against a contract, quotation, or other business document.

The table resides in the OKC schema and holds status VALID, confirming it is a supported and active dictionary object. Because its rows are seeded during implementation rather than entered by end users, the table is generally treated as read-only reference data by functional users, while extensibility is controlled through the standard Oracle configuration and patching process.

From a Data Vault modeling perspective, the mined FK structure classifies this table as hub-leaning. In practice, this suggests treating BUS_DOC_EVENT_ID as a durable business key hub, with the surrounding descriptive columns (such as BEFORE_AFTER and START_END_QUALIFIER) modeled as satellite attributes if a vault-style warehouse is constructed. This is a modeling recommendation rather than an Oracle-mandated design.

Key Information Stored

The table contains twelve documented columns. The most significant are summarized below.

• BUS_DOC_EVENT_ID — The surrogate primary key, enforced by OKC_BUS_DOC_EVENTS_B_PK. It uniquely identifies each business document event.
• BUS_DOC_TYPE — Identifies the business document type to which the event belongs. This is a foreign key to OKC_BUS_DOC_TYPES_B and is the principal grouping column for the seeded event list.
• BUSINESS_EVENT_CODE — The internal code representing the specific event, used by application logic and integrations to reference a given milestone.
• BEFORE_AFTER — Indicates whether the event occurs before or after the referenced document milestone, supporting ordering and eligibility rules.
• START_END_QUALIFIER — Distinguishes whether the event qualifies a start or an end point, which is relevant for date and deliverable calculations.
• ZD_EDITION_NAME — The edition marker used by Oracle's edition-based redefinition (EBR) framework, which supports online patching in 12.2.x.
• OBJECT_VERSION_NUMBER — The optimistic locking column used to detect concurrent modifications.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle audit columns recording who created and last modified each row and when.

The unique index OKC_BUS_DOC_EVENTS_B_U1 is defined on (BUS_DOC_EVENT_ID, ZD_EDITION_NAME), making it a business-key candidate in the edition-aware sense. The true surrogate identifier remains BUS_DOC_EVENT_ID.

Common Use Cases and Queries

Typical usage centers on resolving which events exist for a given document type and joining those events to deliverables for scheduling and date computation.

• Listing all valid events for a contract type: SELECT BUSINESS_EVENT_CODE, BEFORE_AFTER, START_END_QUALIFIER FROM OKC_BUS_DOC_EVENTS_B WHERE BUS_DOC_TYPE = :p_type;
• Resolving deliverable start and end event references: join OKC_DELIVERABLES on RELATIVE_ST_DATE_EVENT_ID and RELATIVE_END_DATE_EVENT_ID to this table's BUS_DOC_EVENT_ID.
• Validation and lookup queries in concurrent programs or interfaces that translate a BUSINESS_EVENT_CODE into its owning BUS_DOC_TYPE.
• Reporting on event configuration by document type to audit which milestones have been enabled in a given environment.

Related Objects

The relationships below derive from the documented FK structure.

• OKC_BUS_DOC_TYPES_B — Referenced by OKC_BUS_DOC_EVENTS_B.BUS_DOC_TYPE; defines the parent business document type for each seeded event.
• OKC_DELIVERABLES — References this table through RELATIVE_ST_DATE_EVENT_ID and RELATIVE_END_DATE_EVENT_ID, using events to derive relative start and end dates.
• OKC_BUS_DOC_EVENTS_B_PK — The primary key constraint on BUS_DOC_EVENT_ID.
• OKC_BUS_DOC_EVENTS_B_U1 — The unique index on (BUS_DOC_EVENT_ID, ZD_EDITION_NAME).
• OKC Contracts Core APIs — Contract lifecycle and deliverable APIs consume event definitions from this table when processing documents.