Results for “gmd_activities_b”

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

Overview

GMD_ACTIVITIES_B is the base table within the Oracle E-Business Suite Process Manufacturing Product Development module (GMD) that defines the activities performed during manufacturing operations. In the process manufacturing model, an activity represents a discrete unit of work executed at an operation step, such as charging, mixing, heating, or packaging. The table resides in the GMD schema and is owned by Oracle Process Manufacturing, with a status of VALID in the ETRM reference for releases 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the heuristic Data Vault classification derived from the foreign key structure is satellite-leaning. This suggests that GMD_ACTIVITIES_B functions primarily as a descriptive attribute store attached to a business key, rather than as a transactional hub or an associative link. Its foreign keys point outward to reference and text tables, reinforcing the interpretation that it carries descriptive context rather than pure event data.

Key Information Stored

The table contains 11 documented columns. The most significant are:

• ACTIVITY — the primary key column and the business identifier for the activity definition. It is enforced through the unique index GMD_ACTIVITIES_B_PK, making ACTIVITY both the surrogate and business-key candidate in this design.
• ACTIVITY_DESC — the descriptive name of the activity, used in user-facing screens and reports.
• COST_ANALYSIS_CODE — a foreign key to CM_ALYS_MST, linking the activity to a cost analysis definition used in costing rollups.
• TEXT_CODE — a foreign key to FM_TEXT_HDR, associating free-form descriptive text (such as standard operating instructions) with the activity.
• TRANS_CNT — a transaction counter typically used for concurrency control and change tracking.
• DELETE_MARK — a soft-delete flag; records are logically removed rather than physically deleted.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / CREATION_DATE / CREATED_BY / LAST_UPDATE_LOGIN — standard EBS audit columns tracking who created and modified the record and when.

Common Use Cases and Queries

Typical scenarios include resolving activity descriptions on routings and operation reports, validating that an operation references a valid activity, and joining cost analysis and text attributes for process documentation.

A basic lookup of activities and their descriptions:

SELECT activity, activity_desc FROM gmd.gmd_activities_b WHERE delete_mark = 0 ORDER BY activity;

Joining to the operation detail table to report activities used per operation:

SELECT o.operation_id, o.activity, a.activity_desc FROM gmd.pm_oprn_dtl o, gmd.gmd_activities_b a WHERE o.activity = a.activity AND a.delete_mark = 0;

Resolving the cost analysis and text attributes for a given activity:

SELECT a.activity, a.activity_desc, c.*, t.* FROM gmd.gmd_activities_b a, gmd.cm_alys_mst c, gmd.fm_text_hdr t WHERE a.cost_analysis_code = c.cost_analysis_code(+) AND a.text_code = t.text_code(+) AND a.delete_mark = 0;

Reporting use cases frequently filter on DELETE_MARK = 0 to exclude logically retired activities and join ACTIVITY_DESC for presentation layers in OPM reporting or custom concurrent programs.

Related Objects

• PM_OPRN_DTL — references GMD_ACTIVITIES_B via PM_OPRN_DTL.ACTIVITY → GMD_ACTIVITIES_B.ACTIVITY; the primary operational consumer, linking activities to operation steps.
• CM_ALYS_MST — referenced by GMD_ACTIVITIES_B.COST_ANALYSIS_CODE; defines cost analysis attributes applied to the activity.
• FM_TEXT_HDR — referenced by GMD_ACTIVITIES_B.TEXT_CODE; holds descriptive text headers associated with the activity.
• GMD_ACTIVITIES_B_PK — the primary key / unique index enforcing uniqueness on ACTIVITY.
• GMD_RECIPE_OPERATIONS / PM_OPERATIONS — process operation headers that ultimately reference operation details and, transitively, activity definitions used in routings and recipes.