Results for “okc_outcomes”

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

Overview

OKC_OUTCOMES_HV is a history view in the Oracle E-Business Suite Contracts Core (OKC) module, owned by the APPS schema and shipped in a VALID state in both Oracle EBS 12.1.1 and 12.2.2. The "_HV" suffix follows the standard EBS naming convention for history views, which expose the versioned (audit) records kept for a business entity rather than only its current state. In this case, the view presents the historical versions of contract outcome definitions, the reusable outcome records that describe the result of contract-related activities such as fulfillment events, clause processing, or workflow-driven contract status changes.

Its role in reporting and integration is to allow concurrent programs, Oracle Reports, Oracle XML Publisher templates, and external interfaces to query every stored version of an outcome — not just the most recent one — while automatically resolving the descriptive text (such as comments) to the caller's session language. This makes OKC_OUTCOMES_HV the appropriate data source for audit-style reports, reconciliation extracts, and custom integrations that must reproduce an outcome exactly as it existed at a given point in time.

Underlying Base Objects

The view is defined over two documented base objects in the APPS schema, exposed as synonyms:

• OKC_OUTCOMES_BH — the "base history" table holding the versioned outcome rows, including all descriptive, attribute, and who-column information, keyed by ID and MAJOR_VERSION.
• OKC_OUTCOMES_TLH — the "translation history" (TL) table holding the language-dependent text for each outcome version.

The two objects are joined on OCEB.ID = OCET.ID and OCEB.MAJOR_VERSION = OCET.MAJOR_VERSION, and the translation side is further filtered by OCET.LANGUAGE = USERENV('LANG'), so callers see only the row for the language of their current EBS session. The view also projects OCEB.ROWID as ROW_ID and selects SFWT_FLAG and COMMENTS from the translation table.

Key Columns

• ROW_ID / ID / MAJOR_VERSION — Row identity, the outcome's unique identifier, and the version number that makes this a history (multi-version) view.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the underlying OAF/BC4J layer.
• PDF_ID, CNH_ID, DNZ_CHR_ID — Foreign keys linking an outcome to the related contract document/fulfillment, contract header, and contract line context.
• SUCCESS_RESOURCE_ID, FAILURE_RESOURCE_ID — Reference resources used when an outcome represents a success or failure result in contract workflow processing.
• ENABLED_YN, SEEDED_FLAG — Status indicators distinguishing active outcomes and Oracle-seeded versus user-defined records.
• COMMENTS, SFWT_FLAG — Descriptive text and a seeded "standard fulfillment/workflow terminology" flag, both sourced from the translation table.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — The standard EBS descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, APPLICATION_ID — Standard audit columns for change tracking and multi-org/multi-application separation.

Common Use Cases and Queries

Typical scenarios include auditing how an outcome's comments or flexfield values changed across versions, extracting a point-in-time snapshot for reconciliation, and joining outcomes to contract headers for customized contract-result reporting.

• All versions of a specific outcome:
  SELECT id, major_version, enabled_yn, comments, last_updated_by, last_update_date FROM okc_outcomes_hv WHERE id = :p_id ORDER BY major_version;
• Latest-enabled outcomes:
  SELECT h.id, MAX(h.major_version) last_ver FROM okc_outcomes_hv h WHERE h.enabled_yn = 'Y' GROUP BY h.id;
• Outcomes linked to a contract header:
  SELECT h.id, h.major_version, h.comments FROM okc_outcomes_hv h WHERE h.dnz_chr_id = :p_chr_id;
• Change history by date range:
  SELECT id, major_version, last_updated_by, last_update_date FROM okc_outcomes_hv WHERE last_update_date BETWEEN :p_from AND :p_to;

Because filtering is applied on USERENV('LANG'), queries run from a session in a language with no translated rows return no data for those versions; reports intended for multilingual environments should confirm that translation history exists for the session language or join directly against the translation table when a specific language is required.