Search Results create_text_row

Overview

GMD_RECIPE_DESIGNER_PKG is an Oracle EBS Application Object Library package owned by the APPS schema. It belongs to the Oracle Process Manufacturing (OPM) product family and is classified as an "OTHER" API (that is, it is not a formally published public API, but rather an internal designer/utility package). It exists to support the Recipe Designer and Routing Designer functionality, providing the server-side logic that the OPM Recipe/Routing design forms require when creating, updating, and deleting recipe header records, recipe routing steps, step material links, and supplementary text rows.

The package is the transactional engine behind recipe authoring. Recipes define the formula (materials, quantities, charges) and the routing (steps, operations) used to manufacture a product. GMD_RECIPE_DESIGNER_PKG encapsulates the DML and the calculation logic that keeps those two structures synchronized, allowing the designer UI to commit individual changed rows without writing SQL directly. In ETRM documentation the package is listed with STATUS VALID in both 12.1.1 and 12.2.2, and the dependency map confirms it references the FM_* tables while being referenced by the sibling package GMD_ROUTING_DESIGNER_PKG.

Key Procedures and Functions

The documented interface exposes 32 procedures and functions, which fall into several functional clusters:

• Text maintenance: CREATE_TEXT_ROW, UPDATE_TEXT_ROW, and DELETE_TEXT_ROW manage the descriptive text records associated with a recipe, routing, or step.
• Recipe header maintenance: CREATE_RECIPE_HEADER and UPDATE_RECIPE_HEADER insert and modify the recipe master record, including its alternate (version) and organization context.
• Routing step maintenance: CREATE_RECIPE_ROUTING_STEP_ROW and UPDATE_RECIPE_ROUTING_STEP_ROW add or change the sequential process steps that make up the routing.
• Step material link maintenance: CREATE_STEP_MATERIAL_LINK, UPDATE_STEP_MATERIAL_LINK, and DELETE_STEP_MATERIAL_LINK maintain the association between a routing step and the materials consumed at that step.
• Quantity and charge calculations: CALCULATE_STEP_QUANTITIES, CALCULATE_STEP_CHARGES, CALCULATE_CHARGES, UPDATE_STEP_QUANTITIES, DELETE_RECIPE_STEP_QUANTITIES, and GET_ROUTING_STEP_QUANTITIES derive and refresh the scaled quantities and cost charges for steps when the recipe size or material usage changes.
• Customer assignment: ADD_RECIPE_CUSTOMER and DELETE_RECIPE_CUSTOMER maintain the customer-specific recipe associations.
• State and mode helpers: GET_RECIPE_MODE and IS_RECIPE_USED_IN_BATCHES report whether a recipe is still in a draft/design mode and whether it has already been consumed by production batches, governing whether the record may still be edited or deleted.

No parameter signatures are published in the ETRM metadata; callers should treat the procedures as internal designer contracts. Because the package is not a formal public API, its signatures may change between releases without the compatibility guarantees that apply to published PL/SQL APIs.

Tables Accessed

The package reads and writes the core OPM recipe and FM (FM = "Formula/Routing") tables, referenced through APPS synonyms:

• GMD_RECIPES / GMD_RECIPES_B: the recipe header (base and translated tables), used by the header create/update and mode/usage checks.
• GMD_RECIPE_CUSTOMERS: customer-specific recipe assignments.
• GMD_RECIPE_ID_S: the sequence that supplies new recipe IDs.
• GMD_RECIPE_ORGN_ACTIVITIES: organization-level activity validation for the recipe.
• GMD_PROCESS_LOSS: process-loss percentages applied during quantity calculation.
• FM_ROUT_DTL, FM_ROUT_DEP: routing step detail and step dependency rows.
• FM_FORM_MST, FM_FORM_MST_B: the formula master (base and translated), defining the material structure behind the recipe.
• FM_MATL_DTL: the material detail lines linked to steps.
• FM_TEXT_HDR, FM_TEXT_TBL: the text header and text-line tables used by the text-row procedures.
• GEM5_TEXT_CODE_S: the OPM text-code sequence used when new text blocks are created.
• FND_DUAL: the standard Oracle Application Object Library dual table used for single-row calculations and sequence fetches.

Usage Notes

GMD_RECIPE_DESIGNER_PKG is invoked indirectly rather than directly. Its primary caller is the OPM Recipe Designer form and the related Routing Designer form; the forms call these procedures to persist row-level changes made in the designer blocks. It is also referenced by the sibling package GMD_ROUTING_DESIGNER_PKG, which orchestrates routing-level operations and delegates recipe-side work here.

Because the package is classified as OTHER rather than a published API, customizations and extensions should call it with caution and should preferably be routed through supported APIs or form-based transactions. Typical safe usage patterns are:

• Form-driven inserts, updates, and deletes of recipe headers, steps, material links, and text rows.
• Recalculation of step quantities and charges when a recipe is saved or when the recipe size/customer is changed.
• Validation before delete or warehouse release, using IS_RECIPE_USED_IN_BATCHES to prevent removal of a recipe already consumed in production.

Custom code that calls these procedures must supply the recipe identifier, organization, and step context expected by the internal designer model, and should commit within the form's transaction boundary. The package is version-stable across 12.1.1 and 12.2.2 in terms of status, but its detailed signatures are undocumented in ETRM and should be verified against the deployed database before use.