Search Results attribute_level

Overview

The view APPS.OKS_MSCHG_OPERATIONS_DTLS_V is a Service Contracts (OKS) reporting and integration object in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description states simply that it is "the view for OKS_MSCHG_OPERATIONS_DTLS," identifying it as a synonym-style pass-through defined over the base table of the same name. The view belongs to the mass change / operations details area of Service Contracts, where mass change operations apply bulk modifications to contracts, contract lines, or related service entities. Because the view exposes every column of the underlying table without filtering, joins, or transformations, it functions as a stable, query-safe read interface for reports, extracts, and integrations while insulating consumers from direct dependency on the base table.

The object is owned by the APPS schema and is documented as VALID. Its role is consistent with standard EBS practice: internal application code writes to the base table, while external consumers, custom reports, and interface programs read through the view to obtain a supported access path.

Underlying Base Objects

ETRM documents a single referenced base object: OKS_MSCHG_OPERATIONS_DTLS, which is accessed through a SYNONYM. The view text selects all thirty-three columns from that table with no WHERE clause, aggregation, or join, so row counts and values in the view match the base table exactly. Because the reference is a synonym rather than a hard-coded schema-qualified table, the definition remains portable across environments and is unaffected by the underlying physical object name.

No additional tables or views are referenced in the documented metadata. Any business meaning derived from foreign key columns such as MRD_ID, OIE_ID, and OLE_ID is therefore resolved by joining this view to the respective parent entities rather than by logic embedded in the view itself.

Key Columns

• ID — Primary identifier for the mass change operation detail record.
• MRD_ID — Reference to the mass change / mass return detail context associated with the operation.
• OIE_ID and OLE_ID — References to the operation input and operation line entities processed by the mass change.
• MSCHG_TYPE — Mass change type, indicating the category of operation being applied.
• ATTRIBUTE_LEVEL — The level at which the mass change applies (for example, contract header versus line level), which is the attribute most frequently used to qualify operation detail rows.
• QA_CHECK_YN — Quality assurance check indicator controlling whether validation is enforced for the operation.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• SECURITY_GROUP_ID — Legacy multi-organization security column.
• ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield (DFF) segments available for customer-specific extension.

Common Use Cases and Queries

The view is typically used to report mass change operation details, to diagnose failed or pending mass change activity, and to drive integration extracts. A representative query filters operation details by mass change type and attribute level:

• SELECT id, mrd_id, oie_id, ole_id, mschg_type, attribute_level, qa_check_yn FROM oks_mschg_operations_dtls_v WHERE mschg_type = :p_type;
• SELECT id, mrd_id, attribute_level, last_update_date FROM oks_mschg_operations_dtls_v WHERE qa_check_yn = 'Y' ORDER BY last_update_date DESC;
• SELECT id, attribute1, attribute2 FROM oks_mschg_operations_dtls_v WHERE object_version_number = 1;

Best practice is to join MRD_ID, OIE_ID, and OLE_ID to their parent entities, to treat the view as read-only, and to use the WHO and OBJECT_VERSION_NUMBER columns for incremental extracts and concurrency-aware processing.