Search Results mrd_pk
Overview
The OKC_MASSCHANGE_REQ_DTLS table is a core data repository within the Oracle E-Business Suite Contracts Core (OKC) module, specifically for versions 12.1.1 and 12.2.2. It functions as the detailed transactional log for mass change operations performed on contracts. When users initiate a mass update to modify a specific attribute across multiple contracts or contract lines, this table stores the granular change request details for each individual item being processed. Its primary role is to persist the operational data that drives the mass change engine, enabling tracking, auditing, and processing of these bulk modifications.
Key Information Stored
While the provided metadata does not list specific columns beyond key relationships, the table's structure is designed to capture the essence of a change request. Based on its description and foreign key relationships, the table's critical columns typically include a unique identifier (ID), foreign keys to the operation instance (OIE_ID) and the specific operation line (OLE_ID) being changed. It would also store the actual change data, such as the attribute being modified (e.g., a price, a date, a party), its old value, and its new requested value. The primary key constraint MRD_PK ensures each detail record is unique, maintaining data integrity for the mass change process.
Common Use Cases and Queries
This table is central to auditing and troubleshooting mass change operations. Common use cases include generating reports on the status and history of mass updates, identifying errors in specific change requests, and analyzing the volume of modifications. A typical query might join this table to its parent operation tables to list all details for a given mass change request. For example:
- Audit Report:
SELECT mrd.id, mrd.attribute_name, mrd.old_value, mrd.new_value, oie.request_id FROM okc_masschange_req_dtls mrd, okc_operation_instances oie WHERE mrd.oie_id = oie.id AND oie.request_date > SYSDATE - 30; - Error Analysis: Queries often filter on status columns (implied but not listed) to find failed or pending change details, joining to
OKC_OPERATION_LINESto get the contract line context.
Related Objects
The table maintains defined foreign key relationships with two primary operational tables, as documented in the metadata:
- OKC_OPERATION_INSTANCES: Joined via
OKC_MASSCHANGE_REQ_DTLS.OIE_ID. This links each change detail to a specific instance or execution of a mass change operation, providing high-level request context (e.g., requester, submission time). - OKC_OPERATION_LINES: Joined via
OKC_MASSCHANGE_REQ_DTLS.OLE_ID. This critical relationship ties the requested change to the precise contract line item being modified, anchoring the transactional detail to the actual business object in the Contracts Core.
These relationships position OKC_MASSCHANGE_REQ_DTLS as a child table in the mass change data model, dependent on the operational framework tables for its context and execution lifecycle.
-
Table: OKC_MASSCHANGE_REQ_DTLS
12.1.1
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_MASSCHANGE_REQ_DTLS, object_name:OKC_MASSCHANGE_REQ_DTLS, status:VALID, product: OKC - Contracts Core , description: This table contains the details of the change requested in the mass change operation. , implementation_dba_data: OKC.OKC_MASSCHANGE_REQ_DTLS ,
-
Table: OKC_MASSCHANGE_REQ_DTLS
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_MASSCHANGE_REQ_DTLS, object_name:OKC_MASSCHANGE_REQ_DTLS, status:VALID, product: OKC - Contracts Core , description: This table contains the details of the change requested in the mass change operation. , implementation_dba_data: OKC.OKC_MASSCHANGE_REQ_DTLS ,