Results for “orig_system_reference_id2”

46 results




Overview
Explore in AI Chat

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

Overview

OKC_TERMS_SECTIONS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKC – Contracts Core product. The view exposes the section-level structure of contract terms, presenting the physical section rows that make up the terms and conditions of a contract document. In Oracle Contracts (OKC), terms are organized hierarchically into a document, sections within that document, and individual terms or clauses within each section. This view surfaces the middle layer of that hierarchy — the sections themselves — along with their sequencing, headings, labels, referencing information, descriptive flexfield attributes, and amendment audit data.

Because it includes the LAST_AMENDED_BY column, the view is frequently referenced when auditing or reporting on who last modified a contract section. This is the column most commonly matched against searches for last_amended_by, which is used to attribute contractual changes to specific users or application responsibilities. The view is read-only with respect to application logic and is intended for query, reporting, and integration purposes rather than as a maintenance surface.

Underlying Base Objects

The view is defined over a single documented base object: OKC_SECTIONS_B, which is referenced through a synonym. The view definition aliases this table as SCNB and performs a direct projection of its columns, including the ROWID exposed as ROW_ID. No joins, unions, or filtering predicates are documented; the view is a straightforward column-level projection of the base table.

This design means the view inherits the transactional and DDL characteristics of OKC_SECTIONS_B. It does not aggregate or transform data, and it carries the same row cardinality as the base table. The absence of joins simplifies both performance considerations and troubleshooting, but it also means no denormalized descriptive information (such as document number or party name) is included; consumers must join to additional OKC objects to enrich section data for reporting.

Key Columns

The columns of the view fall into several functional groups:

Common Use Cases and Queries

A principal use case is determining who last amended a contract section, commonly phrased as a last_amended_by lookup. A representative query is:

SELECT id, document_id, heading, last_amended_by, last_amendment_date FROM okc_terms_sections_v WHERE document_id = :p_document_id ORDER BY section_sequence;

Other recurring scenarios include listing all sections of a contract document in sequence for clause review, extracting sections flagged for printing, and auditing amendment activity across a date range. For example, filtering by LAST_AMENDMENT_DATE and AMENDMENT_OPERATION_CODE supports change-monitoring reports, while joining CREATED_BY or LAST_AMENDED_BY to FND_USER resolves user identifiers to names. Because the view exposes the raw base table, queries should generally constrain DOCUMENT_ID to keep result sets selective and efficient.