Search Results gmd_operation_activities_pk

Overview

GMD_OPERATION_ACTIVITIES is a Process Manufacturing Product Development table owned by the GMD schema. The ETRM documentation describes its purpose as "Operation Activity details," indicating that it stores the discrete activities that make up a routing operation within an Oracle Process Manufacturing (OPM) recipe or routing definition. In Oracle EBS 12.1.1 and 12.2.2, this table sits beneath the operation header level and captures how individual activities are sequenced, offset, and factored within an operation, including whether they are material-related or sequence-dependent.

The table is documented with 47 columns and a single-column primary key, GMD_OPERATION_ACTIVITIES_PK, defined on OPRN_LINE_ID. Validated as VALID in the GMD schema, it is a base configuration table that participates in the definition of process routings used by production and costing. From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as standalone; that is a heuristic suggestion only, and no hub, link, or satellite role is formally asserted. In practice, the presence of OPRN_ID as a parent reference suggests it behaves as a dependent child table of the operation header rather than an independent hub.

Key Information Stored

The most business-significant columns documented in the ETRM schema are:

• OPRN_LINE_ID — the surrogate primary key and sole unique-index column, uniquely identifying each operation activity line.
• OPRN_ID — the parent operation identifier, linking the activity to its routing operation header.
• ACTIVITY — the activity code or description associated with the operation step.
• OFFSET_INTERVAL — the timing offset applied to the activity relative to the operation or preceding step.
• ACTIVITY_FACTOR — a multiplier applied to the activity, commonly used for scaling quantities or durations.
• SEQUENCE_DEPENDENT_IND — indicates whether the activity depends on sequence ordering.
• BREAK_IND and MAX_BREAK — control break behavior and the maximum break value permitted for the activity.
• MATERIAL_IND — flags whether the activity is material-related.
• TEXT_CODE — reference to descriptive text associated with the activity.
• DELETE_MARK — the standard soft-delete flag.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the standard EBS descriptive flexfield columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.

No business-key candidate is documented other than the primary key; OPRN_LINE_ID therefore serves as both surrogate and unique identifier.

Common Use Cases and Queries

Typical reporting scenarios include retrieving all activities belonging to a routing operation, auditing sequence-dependent or material-related steps, and reconciling activity factors used in production scheduling. A representative query joins activities to their parent operation:

• SELECT a.OPRN_LINE_ID, a.OPRN_ID, a.ACTIVITY, a.OFFSET_INTERVAL, a.ACTIVITY_FACTOR FROM GMD.GMD_OPERATION_ACTIVITIES a WHERE a.OPRN_ID = :operation_id AND NVL(a.DELETE_MARK,0) = 0 ORDER BY a.OPRN_LINE_ID;
• Filtering on SEQUENCE_DEPENDENT_IND = 'Y' or MATERIAL_IND = 'Y' to isolate specific activity categories.
• Reporting on BREAK_IND and MAX_BREAK to identify operations with break constraints.
• Extracting ATTRIBUTE_CATEGORY and ATTRIBUTE columns for descriptive flexfield reporting, joining to FND descriptive flexfield views.

All queries should observe the DELETE_MARK flag and the WHO audit columns when determining current versus historical records.

Related Objects

The following objects are most significant in relation to GMD_OPERATION_ACTIVITIES:

• GMD_OPERATION_ACTIVITIES_PK — the primary key constraint on OPRN_LINE_ID.
• The parent operation header table in the GMD routing schema, joined via OPRN_ID, which supplies operation-level context.
• GMD routing and recipe definition tables that reference operation lines within the same process definition.
• OPM production and costing tables that consume operation activities for scheduling and cost roll-up.
• Standard EBS flexfield and lookup views (for example FND lookups and descriptive flexfield views) referenced through TEXT_CODE and ATTRIBUTE_CATEGORY.

Because the documented relationship classification is standalone, the authoritative linkage is through the OPRN_ID column and the GMD_OPERATION_ACTIVITIES_PK constraint rather than any explicitly documented foreign key.