Search Results gmp_form_eff




Overview
Explore in AI Chat

Overview

The GMD_ROUTINGS_B table is the core routing header base table within Oracle E-Business Suite Process Manufacturing (GMD) Product Development. It serves as the master definition table for manufacturing routings, which are the detailed sequences of operations required to produce a formula or product. A routing defines the flow of materials through work centers or resources, specifying the order of steps, resource requirements, and associated costs. This table is fundamental to production planning, scheduling, and costing processes in Process Manufacturing, acting as the parent record for all detailed operation steps and linking to formulas, batches, and accounting setups.

Key Information Stored

The table stores essential header-level attributes for each routing. Its primary identifier is the system-generated ROUTING_ID. The unique combination of ROUTING_NO and ROUTING_VERS enforces business-level uniqueness, allowing for version control of routing definitions. Other critical columns typically include a description, effective dates (start and end), status (e.g., active, inactive), and a reference to a ROUTING_CLASS for categorization. It also links to descriptive text via the TEXT_CODE foreign key to the FM_TEXT_HDR table. This structure enables the management of routing lifecycles and revisions.

Common Use Cases and Queries

A primary use case is retrieving active routings for a specific product or formula during production batch creation. For instance, a report listing all routings with their current version and status is common for master data maintenance. The user's search for "gmp_form_eff" directly relates to a key integration point, as the GMP_FORM_EFF table references ROUTING_ID to associate routings with formula effectivity. A typical query pattern involves joining GMD_ROUTINGS_B with detail and related tables:

  • Identifying routings used by a specific formula: SELECT r.routing_no, r.routing_vers FROM gmd_routings_b r, gmp_form_eff f WHERE r.routing_id = f.routing_id AND f.formula_id = :formula_id;
  • Fetching routing header information for a batch: SELECT * FROM gmd_routings_b WHERE routing_id = (SELECT routing_id FROM pm_btch_hdr WHERE batch_id = :batch_id);

Related Objects

GMD_ROUTINGS_B is a central hub with numerous dependencies. The detail operations for a routing are stored in FM_ROUT_DTL, which references ROUTING_ID. It is classified via GMD_ROUTING_CLASS_B. Crucially, it is referenced by execution and planning modules: GMP_FORM_EFF links routings to formulas, PM_BTCH_HDR stores the routing used for a production batch, and GL_ACCT_MAP associates it with accounting rules. The link to FM_TEXT_HDR manages descriptive notes. This network of relationships underscores the table's critical role in connecting product development with manufacturing execution and financial integration.