Search Results okc_outcomes_b_pk

Overview

The OKC_OUTCOMES_B table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module. It serves as a critical junction table that establishes and manages the relationship between contract conditions and business process definitions. Specifically, it indicates the use of a defined process by a condition, enabling the automation of actions or workflows when a specific contractual condition is triggered or evaluated. This table is fundamental to the operational logic of the Contracts module, linking declarative business rules (conditions) to executable process logic, thereby supporting complex contract management and compliance automation within Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary function is to store foreign key references that link a condition to a process. The most critical columns, as indicated by its foreign key constraints, are the Condition Header ID (CNH_ID) and the Process Definition ID (PDF_ID). The CNH_ID column references the OKC_CONDITION_HEADERS_B table, identifying the specific contract condition. The PDF_ID column references the OKC_PROCESS_DEFS_B table, identifying the process definition to be invoked. The table's primary key is a surrogate ID column, ensuring each condition-process association is uniquely identifiable. This structure allows a single condition to potentially be associated with multiple process outcomes.

Common Use Cases and Queries

A primary use case is tracing which automated processes are configured to execute for a given contract condition, such as sending an approval notification when a financial threshold is met or generating a report upon a milestone date. Common reporting and integration queries involve joining this table to condition and process definition tables. For instance, to list all processes linked to a specific condition header, a query would join OKC_OUTCOMES_B to OKC_PROCESS_DEFS_B on PDF_ID. Conversely, to find all conditions that trigger a particular process, the join would be to OKC_CONDITION_HEADERS_B on CNH_ID. This table is also central for data validation during configuration, ensuring that referenced processes and conditions exist.

Related Objects

• OKC_CONDITION_HEADERS_B: The parent table for contract conditions, referenced via the foreign key on CNH_ID.
• OKC_PROCESS_DEFS_B: The parent table for process definitions, referenced via the foreign key on PDF_ID.
• OKC_OUTCOME_ARGUMENTS: A child table that stores specific parameter values to be passed to the linked process definition for a given outcome, referenced via the OCE_ID column.
• OKC_OUTCOMES_B_PK: The primary key constraint on the ID column, ensuring uniqueness of each record.