Results for “okc_outcome_arguments”

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

Overview

OKC_OUTCOME_ARGUMENTS is a Contracts Core (OKC) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the values passed to process definition parameters. It functions as the binding layer between an outcome defined in the Contracts repository and the process logic that the outcome is intended to invoke. Each row associates an outcome with a specific process definition parameter and supplies the literal VALUE that should be delivered to that parameter at runtime.

From a data modeling perspective, and based on the foreign key structure documented in the ETRM metadata, OKC_OUTCOME_ARGUMENTS is best classified heuristically as a link table. It resolves the many-to-many style relationship between outcomes, action attributes, and process definition parameters, and it carries descriptive payload (the VALUE column) alongside that linkage. Because the table also holds audit and editioning columns, it resembles a link with satellite-style attributes in a Data Vault model, but the dominant role is connectivity rather than standalone entity management.

Key Information Stored

The table contains sixteen documented columns. The most significant include:

• ID — the surrogate primary key, enforced by OKC_OUTCOME_ARGUMENTS_PK. It uniquely identifies each argument binding record.
• OCE_ID — foreign key to OKC_OUTCOMES_B, identifying the outcome to which the argument belongs.
• PDP_ID — foreign key to OKC_PROCESS_DEF_PARMS_B, identifying the target process definition parameter.
• AAE_ID — foreign key to OKC_ACTION_ATTRIBUTES_B, linking the argument to an action attribute.
• VALUE — the actual argument value delivered to the process parameter. This is the principal payload of the table.
• DNZ_CHR_ID — the Contracts repository or contract header identifier associated with the outcome argument.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Framework to detect concurrent updates.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org and access control partitioning.
• APPLICATION_ID — identifies the owning application, typically OKC.
• SEEDED_FLAG — indicates whether the row is a seeded (delivered) record versus a user-created one.
• ZD_EDITION_NAME — editioning column introduced for online patching in EBS 12.2, present in both unique indexes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Two unique indexes are documented and serve as business-key candidates: OKC_OUTCOME_ARGUMENTS_U1 on (ID, ZD_EDITION_NAME) and OKC_OUTCOME_ARGUMENTS_U2 on (OCE_ID, PDP_ID, ZD_EDITION_NAME). The U2 constraint is the meaningful business key, since it prevents duplicate argument bindings for the same outcome and parameter pair.

Common Use Cases and Queries

Typical scenarios involve tracing which values an outcome supplies to a process parameter, auditing outcome configuration, and reconciling seeded versus custom arguments.

To retrieve all argument values for a specific outcome:

• SELECT a.ID, a.OCE_ID, a.PDP_ID, a.AAE_ID, a.VALUE FROM OKC.OKC_OUTCOME_ARGUMENTS a WHERE a.OCE_ID = :outcome_id;

To join arguments to their process definition parameters and outcomes for reporting:

• SELECT o.NAME outcome_name, p.NAME parameter_name, a.VALUE FROM OKC.OKC_OUTCOME_ARGUMENTS a JOIN OKC.OKC_OUTCOMES_B o ON o.ID = a.OCE_ID JOIN OKC.OKC_PROCESS_DEF_PARMS_B p ON p.ID = a.PDP_ID WHERE a.SEEDED_FLAG = 'Y';

To detect duplicate bindings, query the U2 business key group by OCE_ID and PDP_ID with HAVING COUNT(*) > 1. Reporting use cases include outcome configuration extracts, impact analysis before modifying process definitions, and migration validation when moving contract terms between environments.

Related Objects

• OKC_OUTCOMES_B — parent outcome definition, joined on OKC_OUTCOME_ARGUMENTS.OCE_ID = OKC_OUTCOMES_B.ID.
• OKC_PROCESS_DEF_PARMS_B — process definition parameter, joined on OKC_OUTCOME_ARGUMENTS.PDP_ID = OKC_PROCESS_DEF_PARMS_B.ID.
• OKC_ACTION_ATTRIBUTES_B — action attribute, joined on OKC_OUTCOME_ARGUMENTS.AAE_ID = OKC_ACTION_ATTRIBUTES_B.ID.
• FND_SECURITY_GROUPS — security group reference, joined on OKC_OUTCOME_ARGUMENTS.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
• OKC_OUTCOMES_TL — translatable outcome names, useful for multilingual reporting joins.
• OKC_PROCESS_DEF_PARMS_TL — translatable parameter names.
• OKC_ACTION_ATTRIBUTES_TL — translatable action attribute names.
• Contracts Open Interfaces and the OKC API layer — consume this table when executing outcome-driven process logic.