Search Results gmd_routing_class_b




Overview
Explore in AI Chat

Overview

The GMD_ROUTING_CLASS_B table is a core master data table within the Oracle E-Business Suite Process Manufacturing (GMD) module, specifically for Product Development. Its primary function is to serve as a base table for defining and storing routing classes, which are logical groupings used to categorize and organize routings. A routing defines the sequence of operations required to manufacture a product. By classifying routings, organizations can efficiently manage, report on, and apply standard process rules to groups of similar manufacturing procedures. This table is fundamental to the setup and maintenance of the production process hierarchy in Oracle Process Manufacturing.

Key Information Stored

While the provided metadata does not list specific columns, the structure of a base table in Oracle EBS typically includes key identifiers and descriptive attributes. Based on standard patterns and the documented primary key, the table centrally stores the ROUTING_CLASS code, which uniquely identifies each classification. It is highly probable the table also contains columns for a description (e.g., DESCRIPTION), an enabled flag (e.g., DISABLE_DATE), and audit fields such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY. The TEXT_CODE column, referenced by a foreign key, links the routing class to descriptive text blocks stored in the FM_TEXT_HDR table for more extensive notes.

Common Use Cases and Queries

This table is primarily accessed during setup, master data maintenance, and reporting. Common operational use cases include creating new routing classes via the application interface, querying for a list of all active classes, or validating a class code during routing definition. For reporting, it is frequently joined to routing detail tables to analyze production processes by class. A typical query to retrieve basic routing class information would be:

  • SELECT routing_class, description, disable_date FROM gmd_routing_class_b WHERE disable_date IS NULL ORDER BY routing_class;

Another common pattern is joining to the routings table to list all routings within a specific class:

  • SELECT r.routing_no, rc.description FROM gmd_routings_b r, gmd_routing_class_b rc WHERE r.routing_class = rc.routing_class AND rc.routing_class = '&CLASS_CODE';

Related Objects

The GMD_ROUTING_CLASS_B table maintains defined relationships with other critical Process Manufacturing tables, as per the provided foreign key metadata.

  • Primary Key Reference: The table's primary key, GMD_ROUTING_CLASS_B_PK, is defined on the ROUTING_CLASS column, ensuring its uniqueness.
  • Referenced by GMD_ROUTINGS_B: The GMD_ROUTINGS_B table (which stores routing headers) has a foreign key (GMD_ROUTINGS_B.ROUTING_CLASS) referencing this table. This enforces that every routing must belong to a valid, pre-defined routing class.
  • References FM_TEXT_HDR: The GMD_ROUTING_CLASS_B.TEXT_CODE column is a foreign key to the FM_TEXT_HDR table. This allows lengthy descriptive text to be associated with a routing class, separate from the short description.