Search Results pmits_operation_activities_v

Overview

The PMITS_OPERATION_ACTIVITIES_V view is an Oracle E-Business Suite dictionary object owned by the APPS schema and shipped as part of the PMI – Process Manufacturing Intelligence product family. It is a reporting and integration view whose header identifies it as the "GMD Operation Activities View." Its purpose is to present operation activity definitions used within Process Manufacturing (GMD) routings, enriched with descriptive text drawn from the activity master. The view combines the operational detail rows held against an operation with the master activity descriptions required to interpret them, so that downstream reporting, process intelligence extracts, and interface programs can consume activity data without performing the join themselves.

In 12.1.1 and 12.2.2 the object is registered as status VALID, confirming that the view compiles successfully against its base objects in a standard installation. Because PMITS views are typically consumed by Process Manufacturing Intelligence reporting rather than by core transaction processing, the view functions as a read-only projection layer over the underlying operational tables.

Underlying Base Objects

The documented ETRM 12.2.2 metadata records two referenced base objects, both surfaced as synonyms: GMD_OPERATION_ACTIVITIES and FM_ACTV_MST. The view text joins these directly:

• GMD_OPERATION_ACTIVITIES OA — the driving table, supplying operation line and activity assignment records.
• FM_ACTV_MST AM — the activity master, supplying the descriptive activity text.

The join predicate is OA.ACTIVITY = AM.ACTIVITY, an equi-join on the activity code. This is an inner join, so rows in GMD_OPERATION_ACTIVITIES whose activity code has no matching master record are excluded from the view result set. No outer join or filter clause is applied in the documented view text.

Key Columns

The view exposes eight columns:

• OPRN_LINE_ID — the unique identifier of the operation activity line; effectively the primary key of a row in the source table.
• OPRN_ID — the parent operation identifier, linking the activity line to its operation.
• ACTIVITY — the activity code assigned to the operation, and the join key to the activity master.
• OFFSET_INTERVAL — the offset interval for the activity, expressing the scheduling or timing offset associated with the operation activity. This is the column most often sought when users search on "offset_interval," as it is not exposed on all activity-related objects.
• ACTIVITY_FACTOR — a numeric factor applied to the activity, typically a scaling or quantity multiplier used in capacity, cost, or scheduling calculations.
• DELETE_MARK — the standard Oracle EBS soft-delete indicator; rows with a non-zero value represent logically deleted records.
• TEXT_CODE — the code referencing a text or note stored in the standard text tables.
• ACTIVITY_DESC — the activity description sourced from FM_ACTV_MST, providing the human-readable label for the activity code.

Common Use Cases and Queries

Typical uses include listing all activities for a given operation, retrieving descriptions for activity codes, and isolating offset interval values for scheduling analysis. Users investigating offset timing against operation activities should query the view rather than the base table when the activity description is also required.

Activities for a specific operation:

• SELECT oprn_line_id, oprn_id, activity, activity_desc, offset_interval, activity_factor FROM apps.pmits_operation_activities_v WHERE oprn_id = :oprn_id AND NVL(delete_mark, 0) = 0 ORDER BY oprn_line_id;

Locating offset interval values across activities:

• SELECT activity, activity_desc, offset_interval, activity_factor FROM apps.pmits_operation_activities_v WHERE offset_interval IS NOT NULL AND NVL(delete_mark, 0) = 0 ORDER BY activity;

Validating activity codes against the master:

• SELECT DISTINCT activity, activity_desc FROM apps.pmits_operation_activities_v ORDER BY activity;

Because the view performs an inner join, a query returning fewer rows than expected may indicate activity codes in GMD_OPERATION_ACTIVITIES that are absent from FM_ACTV_MST. Applications should also filter on DELETE_MARK unless logically deleted rows are explicitly required.