Results for “okc_masschange_req_dtls”

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

Overview

The OKC_MASSCHANGE_REQ_DTLS table resides in the OKC schema and forms part of the Oracle Contracts Core module within Oracle E-Business Suite releases 12.1.1 and 12.2.2. As its name implies, the table stores the detail records associated with a mass change request executed against one or more contract records. Each row captures a single attribute-level modification — that is, the specific field that was targeted, its value before the mass change, and its value after the operation completed. This granular level of storage allows Oracle Contracts to maintain an auditable, attribute-by-attribute history of bulk contract updates performed through the mass change feature.

From a Data Vault modeling perspective, the heuristic classification for this table is link. This reflects the fact that OKC_MASSCHANGE_REQ_DTLS sits at the intersection between an operation instance and an operation line, and its rows are essentially associative records that describe a discrete change event spanning those two parent entities, enriched by attribute name and value payloads.

Key Information Stored

The table is physically implemented with 13 documented columns. The most significant are summarized below.

• ID — Surrogate primary key (MRD_PK). Uniquely identifies each mass change detail record; this is a system-generated identifier rather than a business key.
• OIE_ID — Foreign key to OKC_OPERATION_INSTANCES; ties the detail to the parent mass change operation instance.
• OLE_ID — Foreign key to OKC_OPERATION_LINES; links the detail to the specific operation line (typically one contract or contract line) being processed.
• ATTRIBUTE_NAME — Name of the contract attribute targeted by the mass change, such as a status, term, or descriptive field.
• OLD_VALUE — The value of the attribute prior to the change, supporting before/after auditing.
• NEW_VALUE — The value applied by the mass change operation.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org and data-security partitioning.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications Framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE — Standard WHO columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking the most recent modification.

The table does not document any additional unique business key indexes beyond the primary key on ID; the natural business identity of a row is effectively the combination of OIE_ID, OLE_ID, and ATTRIBUTE_NAME.

Common Use Cases and Queries

Typical uses of this table include auditing mass change outcomes, reconstructing before/after states for compliance reporting, diagnosing failed or partially applied mass changes, and feeding downstream analytics on contract attribute volatility.

A common query joins the detail rows back to the parent operation instance and operation line to obtain a complete picture of a mass change run:

• Retrieve all changes for a given operation: SELECT d.* FROM okc_masschange_req_dtls d WHERE d.oie_id = :p_oie_id;
• Reconstruct before/after values: SELECT d.attribute_name, d.old_value, d.new_value FROM okc_masschange_req_dtls d WHERE d.ole_id = :p_ole_id;
• Audit by user and date range: filter on created_by and creation_date to isolate changes performed within a specific window.
• Security-scoped reporting: constrain by security_group_id to respect operating unit boundaries.

Related Objects

• OKC_OPERATION_INSTANCES — referenced via OKC_MASSCHANGE_REQ_DTLS.OIE_ID; the parent operation instance.
• OKC_OPERATION_LINES — referenced via OKC_MASSCHANGE_REQ_DTLS.OLE_ID; the individual line processed in the operation.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs data access partitioning.
• OKC_MASSCHANGE_REQUESTS — logically related header-level table describing the overarching mass change request.
• OKC_CONTRACTS (OKC_K_HEADERS) — the underlying contract records whose attributes were modified.
• OKC Contract Management APIs — such as the mass change program and OKC_CONTRACT_PUB packages, which populate these rows.

Understanding this table is essential for anyone performing mass maintenance audits or building reporting on contract change history within Oracle Contracts Core.