Results for “okc_outcome_arguments_h_u1”

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

Overview

OKC.OKC_OUTCOME_ARGUMENTS_H is a history (audit) table in the Oracle Contracts (OKC) schema, maintained as part of the Oracle E-Business Suite Release 12.1.1 / 12.2.2 ETRM data model. The ETRM documentation identifies the object as VALID and describes it explicitly as a "mirror image of base table OKC_OUTCOME_ARGUMENTS." Its purpose is to preserve prior and current versions of the outcome argument records that drive contract outcome (rule) evaluation, so that argument values captured at a given point in time remain queryable after the operative record is modified or superseded. Column-level semantics therefore follow the base table OKC_OUTCOME_ARGUMENTS, and the physical table is stored in the APPS_TS_TX_DATA tablespace with PCT Free 10; its indexes reside in APPS_TS_TX_IDX.

From a Data Vault modeling perspective, the heuristic classification mined from the FK structure is standalone — the table carries no chained foreign keys to other OKC transactional objects in the documented relationship data. Because it nests a MAJOR_VERSION attribute within the same physical table, it behaves more like a versioned satellite (a multi-active, historized satellite on the base hub OKC_OUTCOME_ARGUMENTS) than a conventional link or hub. This is a modeling suggestion only; the authoritative definition remains the base table.

Key Information Stored

The table contains 16 documented columns. The most important are summarized below.

• ID — Surrogate identifier of the outcome argument, inherited from the base table record. Together with MAJOR_VERSION it forms the primary key OKC_OUTCOME_ARGUMENTS_H_PK and the unique index OKC_OUTCOME_ARGUMENTS_H_U1.
• MAJOR_VERSION — The version discriminator. Combined with ID it identifies a specific historical edition of the argument row, making (ID, MAJOR_VERSION) the business-key candidate surfaced by the unique index.
• OCE_ID — Reference to the outcome/contract event context to which the argument belongs.
• PDP_ID — Reference to the associated process/package definition that evaluated the argument.
• AAE_ID — Reference to the associated argument/attribute element definition.
• DNZ_CHR_ID — The contract (Denormalized Character ID) context; a non-unique index OKC_OUTCOME_ARGUMENTS_H_N1 serves this column for contract-scoped lookups.
• VALUE — VARCHAR2(2000); the actual argument value captured for the outcome evaluation, and the principal payload of the row.
• OBJECT_VERSION_NUMBER — Optimistic locking token used by the Applications framework.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last touched each historical row.
• SECURITY_GROUP_ID — Reference to FND_SECURITY_GROUPS, supporting multi-org/security-group data isolation.
• APPLICATION_ID and SEEDED_FLAG — Ownership and seed/origin indicators distinguishing delivered versus customer-created rows.

Common Use Cases and Queries

Typical usage is version comparison and audit reporting: reconstructing which argument values were in force when a contract outcome was evaluated, or tracing changes across MAJOR_VERSION. A representative pattern retrieves the current version of each argument for a contract:

• SELECT id, major_version, value FROM okc.okc_outcome_arguments_h WHERE dnz_chr_id = :chr_id ORDER BY id, major_version DESC;
• SELECT id, major_version, value FROM okc.okc_outcome_arguments_h WHERE id = :id; — full version history for one argument.
• Change-tracking joins use last_updated_by, last_update_date, and major_version to report deltas between versions.
• Rule-execution forensics join OCE_ID, PDP_ID, and AAE_ID to the corresponding base and definition tables to explain why an outcome fired.

Related Objects

The documentation records no outbound references other than the SECURITY_GROUP_ID dependency, and the table is referenced only by the view OKC_OUTCOME_ARGUMENTS_H#. Its most significant logical relationships are to the following objects.

• OKC_OUTCOME_ARGUMENTS — The base table of which this is the history mirror; join on ID and MAJOR_VERSION.
• OKC_OUTCOME_ARGUMENTS_H# — The EBS-internal view wrapper over this table, used by the framework for secured access.
• OKC_OUTCOME_ARGUMENTS_H_U1 / _N1 — Supporting unique (ID, MAJOR_VERSION) and non-unique (DNZ_CHR_ID) indexes.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for security-group isolation.
• OKC_CONTRACTS (DNZ_CHR_ID) — Logical parent providing contract context; also queried through the contract identifier used in the _N1 index.