Results for “gmd_recipe_orgn_activities”

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

Overview

GMD_RECIPE_ORGN_ACTIVITIES is a Process Manufacturing Product Development table within the GMD schema of Oracle E-Business Suite. It stores updates to operation activity details at the recipe level, capturing recipe-, organization-, routing step-, and operation-line-specific activity information used in process manufacturing execution and costing. In the context of Oracle EBS 12.1.1 and 12.2.2, this table supports the definition and revision of manufacturing recipes across multiple organizations, ensuring that activity factors and textual qualifications can be maintained per recipe and per organization without altering the master routing or operation definitions.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. This suggests that, from a modeling perspective, the table functions independently rather than as a hub, link, or satellite in a strict Data Vault sense, though its composite primary key does reference four business dimensions (recipe, organization code, routing step, and operation line).

Key Information Stored

The table contains 43 documented columns. The composite primary key GMD_RECIPE_ORGN_ACTIVITIES_PK consists of RECIPE_ID, ORGN_CODE, ROUTINGSTEP_ID, and OPRN_LINE_ID. The unique index (business-key candidate) is documented as GMD_RECIPE_ORGN_ACTIVITIES_PK over OPRN_LINE_ID, ORGANIZATION_ID, RECIPE_ID, and ROUTINGSTEP_ID, indicating that the combination of these columns uniquely identifies a row.

The most significant columns include:

• RECIPE_ID — identifies the recipe to which the activity detail belongs.
• ORGN_CODE — the organization code for the recipe-organization combination.
• ROUTINGSTEP_ID — the routing step associated with the activity.
• OPRN_LINE_ID — the operation line identifier.
• ORGANIZATION_ID — the numeric organization identifier used in the unique index.
• ACTIVITY_FACTOR — the activity factor value applied at the recipe level.
• TEXT_CODE — a code used for textual qualification or reference.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the standard Oracle EBS descriptive flexfield columns, providing extensibility for customer-specific attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical use cases include retrieving all activity overrides for a given recipe and organization, comparing activity factors across routing steps, and reporting on flexfield-based custom attributes. A representative query is:

• SELECT RECIPE_ID, ORGN_CODE, ROUTINGSTEP_ID, OPRN_LINE_ID, ACTIVITY_FACTOR FROM GMD.GMD_RECIPE_ORGN_ACTIVITIES WHERE RECIPE_ID = :recipe_id AND ORGANIZATION_ID = :org_id;
• Joining to routing step and operation line tables to report activity details by operation.
• Extracting ATTRIBUTE_CATEGORY and ATTRIBUTE1–30 for custom reporting on recipe-level activity modifications.
• Auditing changes using CREATION_DATE and LAST_UPDATE_DATE for compliance and traceability.

Related Objects

The table is classified as standalone, so no explicit foreign-key relationships were mined. However, in practice it references and is referenced by several Process Manufacturing objects, including:

• GMD_RECIPES — via RECIPE_ID.
• GMD_ROUTING_STEPS — via ROUTINGSTEP_ID.
• GMD_OPERATION_LINES — via OPRN_LINE_ID.
• HR_OPERATING_UNITS or ORG_ORGANIZATION_DEFINITIONS — via ORGANIZATION_ID or ORGN_CODE.
• GMD_OPERATIONS and related routing and activity definition tables that supply the operation activity master data.
• PL/SQL APIs and concurrent programs in the Process Manufacturing Product Development module that maintain recipe operation activities.