Results for “cop_id”

50+ results




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

Overview

OKS_MASSCHANGE_CRITERIA_V is an APPS-owned database view within the Oracle E-Business Suite Service Contracts (OKS) module. It is documented as VALID in both release 12.1.1 and 12.2.2. Its stated purpose is to support the Mass Change user interface by abstracting the underlying join logic between operation instances and mass change request details, thereby avoiding coding and querying complexity in the front-end forms and concurrent programs that drive the Mass Change feature.

The view exposes one row per operation instance, optionally enriched with mass change request detail attributes. Because it consolidates several related entities into a single flattened structure, it serves as a convenient reporting and integration surface for administrators and developers who need to inspect mass change activity without reconstructing the full relational model.

Underlying Base Objects

The view is defined over two documented base objects, both themselves views in the APPS schema:

  • OKC_OPERATION_INSTANCES_V (OIE) — the driving source, which supplies the operation instance header information including identifiers, status, request reference, and object references.
  • OKC_MASSCHANGE_REQ_DTLS_V (MRD) — the mass change request detail lines, joined to the operation instance on OIE.ID = MRD.OIE_ID.

The join is an outer join (MRD is the optional side, indicated by the (+) notation on MRD.OIE_ID), and the query further restricts results with the predicate MRD.OLE_ID IS NULL. This means rows are returned for every operation instance, and mass change detail columns are populated only where a matching request detail exists. The OLE_ID IS NULL filter excludes records associated with the object-level execution path, leaving the criteria-oriented rows that the Mass Change UI requires.

Key Columns

  • OIE_ID — Identifier of the underlying operation instance, inherited from OKC_OPERATION_INSTANCES_V. Acts as the primary correlation key to the detail rows.
  • NAME — Descriptive name of the operation instance.
  • COP_ID — Identifier linking the instance to its operation definition/context.
  • STATUS_CODE — Current status of the operation instance (for example, pending, processed, or failed).
  • REQUEST_ID — Concurrent request that produced the operation instance, useful for tracing batch activity.
  • JTOT_OBJECT1_CODE, OBJECT1_ID1, OBJECT1_ID2 — Object type code and the composite key values identifying the entity the operation acts upon, such as a contract, subscription, or line.
  • MRD_ID — Identifier of the matching mass change request detail line; NULL when no detail applies.
  • ATTRIBUTE_NAME, OLD_VALUE, NEW_VALUE — The attribute targeted by the mass change and its before/after values, supplied from the request detail.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns describing row ownership and change history.

Common Use Cases and Queries

Typical uses include auditing mass change operations, diagnosing why an attribute was or was not updated, and powering custom reports or interfaces that need a denormalized view of operation instances and their criteria. A representative query listing active instances with their pending attribute changes is shown below.

  • Audit pending changes: SELECT oie_id, name, status_code, attribute_name, old_value, new_value FROM oks_masschange_criteria_v WHERE attribute_name IS NOT NULL ORDER BY creation_date DESC;
  • Trace by concurrent request: SELECT oie_id, name, object1_id1, status_code FROM oks_masschange_criteria_v WHERE request_id = :p_request_id;
  • Locate target object activity: SELECT oie_id, jtot_object1_code, object1_id1, object1_id2, attribute_name FROM oks_masschange_criteria_v WHERE jtot_object1_code = :p_object_code;

Because the view is owned by APPS and built on the Service Contracts operation framework, queries should generally be executed with the APPS schema or through a responsibility whose MO data group grants access to OKS objects.