Search Results fm_text_tbl




Overview
Explore in AI Chat

Overview

GMD_ROUTING_DESIGNER_PKG is the Oracle Process Manufacturing (OPM) package body that provides the server-side engine behind the Routing Designer form in Oracle E-Business Suite 12.1.1 and 12.2.2. A routing defines the ordered sequence of operations, resource requirements, and step-level dependencies that a product or process follows during manufacturing. The Routing Designer is the maintenance UI through which planners create routing headers, add and sequence steps, attach step dependencies, and copy or version an existing routing. GMD_ROUTING_DESIGNER_PKG encapsulates the validation, sequencing, and persistence logic that those form actions execute against the GMD_ROUTINGS tables and the legacy FM_ routing detail tables, and it contains the documented entry points calling forms use through the GMD_API_GRP wrapper.

Key Procedures and Functions

The package exposes 25 documented procedures and functions organized around routing maintenance operations:

Tables Accessed

The package operates primarily on GMD_ROUTINGS and its _B (base) table for header data, and on FM_ROUT_DTL for routing step detail lines. Step dependency rows are held in FM_ROUT_DEP. The user search term, FM_TEXT_TBL, is the legacy OPM text table referenced by the package to persist step-level and routing-level descriptive text blocks associated with the designer form. GEM5_ROUTING_ID_S, GEM5_ROUTINGSTEP_ID_S, and GEM5_TEXT_CODE_S supply primary key values for headers, steps, and text records. GMD_ROUTING_CLASS provides routing class validation, and MTL_UNITS_OF_MEASURE (via INV_CONVERT) is read for unit-of-measure conversions on operation quantities.

Usage Notes

GMD_ROUTING_DESIGNER_PKG is not a public integration API; its documented signature set is consumed by the Routing Designer form through GMD_API_GRP, and it is referenced by one other package. Custom code should not invoke these routines directly. Instead, integrations should use the public routing APIs in GMD_ROUTINGS_PUB and GMD_ROUTING_STEPS_PUB, which internally call the designer package. Because the package reads FND_PROFILE and uses FND_MSG_PUB for error handling, it must run with a valid EBS session and Apps initialization (FND_GLOBAL). The absence of inbound database references confirms it is an internal implementation package for form-driven routing maintenance.