Search Results okc_outcome_arguments_v




Overview
Explore in AI Chat

Overview

OKC_OUTCOME_ARGUMENTS_V is a dictionary-defined view owned by the APPS schema in Oracle E-Business Suite, registered under the OKC – Contracts Core product. The view is documented as VALID in both ETRM 12.1.1 and ETRM 12.2.2 and exists to provide a stable, read-oriented access layer over the OKC_OUTCOME_ARGUMENTS transactional table. Its stated purpose is simply to present the columns of OKC_OUTCOME_ARGUMENTS for query, reporting, and integration consumption.

Within the Contracts Core data model, outcome arguments represent the parameter values supplied to outcome expressions evaluated during contract authoring, clause generation, and contract lifecycle events. Rather than exposing consumers directly to the base table, the view gives report developers and interface builders a controlled projection that can be referenced without embedded DML privileges on the underlying object. It also carries the ROWID of the base row as ROW_ID, which preserves row-level identification for downstream processing.

The view contains no filtering predicate, no join, and no aggregation: it is a straight projection of the base table, which means it inherits the base table's volume and performance characteristics.

Underlying Base Objects

According to the documented metadata, the view is defined over a single referenced base object: OKC_OUTCOME_ARGUMENTS, exposed in the APPS schema as a SYNONYM. The view text confirms this relationship explicitly, selecting from OKC_OUTCOME_ARGUMENTS with the alias OATB and mapping each base column to an identically named view column, with the sole exception of the base ROWID, which is published as ROW_ID.

Because the definition is a one-to-one projection, all business rules, defaults, and referential constraints reside in the base table and its parent entities. The columns PDP_ID, OCE_ID, AAE_ID, and DNZ_CHR_ID indicate upward relationships into contract and outcome definition structures, while OBJECT_VERSION_NUMBER and the standard WHO audit columns preserve concurrency control and auditability at the base-table level. No additional objects, views, or functions are documented as contributing to this view.

Key Columns

  • ROW_ID — the ROWID of the underlying OKC_OUTCOME_ARGUMENTS row, useful for direct row addressing.
  • ID — primary identifier of the outcome argument record.
  • PDP_ID — foreign key linking the argument to its parent outcome/process definition context.
  • OCE_ID — reference to the outcome expression or outcome entity to which the argument belongs.
  • AAE_ID — reference to the associated application entity used when resolving the argument.
  • DNZ_CHR_ID — contract identifier, connecting the argument to a specific contract.
  • OBJECT_VERSION_NUMBER — optimistic locking version for concurrent update detection.
  • VALUE — the argument value itself, supplied to the outcome evaluation.
  • APPLICATION_ID — owning application identifier, supporting multi-application coexistence.
  • SEEDED_FLAG — indicates whether the record is Oracle-seeded (Y) or customer-created (N).
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording creation and last modification context.

Common Use Cases and Queries

The view is typically used for diagnostics, data extraction, and reporting on outcome argument configuration for a contract or expression. A representative query retrieves all arguments for a given contract identifier:

  • SELECT id, oce_id, aae_id, value FROM okc_outcome_arguments_v WHERE dnz_chr_id = :contract_id ORDER BY id;
  • SELECT oce_id, COUNT(*) FROM okc_outcome_arguments_v WHERE seeded_flag = 'N' GROUP BY oce_id;
  • SELECT v.id, v.value, v.last_updated_by, v.last_update_date FROM okc_outcome_arguments_v v WHERE v.object_version_number < :expected_version;

Because the view is an unfiltered projection, queries should always be constrained by indexed base columns such as ID, DNZ_CHR_ID, or OCE_ID. For high-volume extraction, direct reads from OKC_OUTCOME_ARGUMENTS via the synonym may be preferable, but the view remains the documented, supported interface for read-only access to outcome argument data.