Results for “gl_acct_map”

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

Overview

FM_ROUT_HDR is the routing header table within the Oracle E-Business Suite Process Manufacturing Product Development (GMD) module. A routing defines the sequenced set of operations, resources, and steps required to manufacture a product, and FM_ROUT_HDR serves as the master record holding the identity, classification, version, and unit-of-measure context for each routing. Individual operations and step-level detail are stored in the companion detail table, FM_ROUT_DTL, which references the header through the ROUTING_ID column. The header therefore acts as the anchor point for routing definitions consumed by formula effectiveness, batch manufacturing, and costing processes.

The ETRM metadata notes that this object is "Not implemented in this database," indicating the specific instance from which the documentation was mined does not carry the Process Manufacturing routing schema. The table exists architecturally but may require the GMD product to be installed and configured before use. From a Data Vault modeling perspective, the mined foreign-key structure classifies FM_ROUT_HDR as hub-leaning: it carries a stable surrogate key and serves as the referenced parent for multiple dependent tables, with relatively few outbound dependencies of its own.

Key Information Stored

The documented metadata identifies three indexed columns. ROUTING_ID is the surrogate primary key defined by the FM_ROUT_HDR_PK constraint. The unique key FM_ROUT_HDR_UC1 comprises ROUTING_NO and ROUTING_VERS, which together form the business-key candidate: a routing number combined with its version identifier. This composite structure supports versioned routing definitions, allowing multiple iterations of the same routing number to coexist.

Beyond the keys, the documented foreign-key columns reveal the principal descriptive attributes:

• ROUTING_CLASS — references FM_ROUT_CLS, categorizing the routing for selection and reporting purposes.
• TEXT_CODE — references FM_TEXT_HDR, linking narrative or instructional text maintained against the routing.
• ITEM_UM — references SY_UOMS_MST, the unit of measure in which routing quantities and yields are expressed.

These three columns define the routing's classification, documentation, and measurement context, and they are the attributes most frequently joined when building routing reports.

Common Use Cases and Queries

The most common access pattern resolves a routing number and version to its surrogate key, then retrieves dependent detail. A representative query joins the header to its detail lines:

• SELECT h.routing_id, h.routing_no, h.routing_vers, d.* FROM fm_rout_hdr h, fm_rout_dtl d WHERE h.routing_id = d.routing_id AND h.routing_no = :routing_no AND h.routing_vers = :version;

Classification and unit-of-measure lookups are frequently embedded in reporting extracts:

• Joining FM_ROUT_HDR to FM_ROUT_CLS on ROUTING_CLASS to report routings by class.
• Joining to SY_UOMS_MST on ITEM_UM to display the routing's measurement basis.
• Joining to FM_TEXT_HDR on TEXT_CODE to retrieve routing instructions.

Because PM_BTCH_HDR references FM_ROUT_HDR through ROUTING_ID, batch genealogy and production reporting commonly traverse from batch headers back to the originating routing to confirm which routing version governed a batch. Formula effectiveness queries similarly join FM_FORM_EFF, GMP_FORM_EFF, and GL_ACCT_MAP on ROUTING_ID to associate formulas, regulatory effectiveness data, and costing account mappings with the routing.

Related Objects

The following objects are the most significant dependents and references, based on the documented foreign-key relationships:

• FM_ROUT_DTL — references FM_ROUT_HDR.ROUTING_ID; holds the operation and step-level routing detail.
• FM_FORM_EFF — references FM_ROUT_HDR.ROUTING_ID; formula effectiveness entries tied to the routing.
• GMP_FORM_EFF — references FM_ROUT_HDR.ROUTING_ID; regulatory formula effectiveness data.
• GL_ACCT_MAP — references FM_ROUT_HDR.ROUTING_ID; general ledger account mapping for costing.
• PM_BTCH_HDR — references FM_ROUT_HDR.ROUTING_ID; batch headers executed against the routing.
• FM_ROUT_CLS — referenced by ROUTING_CLASS; provides routing classification values.
• FM_TEXT_HDR — referenced by TEXT_CODE; supplies routing text and instructions.
• SY_UOMS_MST — referenced by ITEM_UM; supplies unit-of-measure definitions.

Together these objects form the routing cluster within Process Manufacturing, with FM_ROUT_HDR functioning as the hub around which detail, effectiveness, costing, and batch execution data are organized.