Results for “gmd_formula”

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

Overview

APPS.GMD_FORMULA_DETAIL_PUB is a public PL/SQL API package within the Oracle E-Business Suite Process Manufacturing (OPM) product family. It is the published interface for managing the detail lines of a formula — the specification of ingredient, material, and component quantities that make up a formula header definition. In OPM, a formula constitutes the master manufacturing definition that drives product consistency, batch scaling, and cost rollup; the detail records that this package maintains represent the individual component lines, their quantities, units, and validity context.

The package is classified as a public (PUB) API, performing the standard EBS multi-tier validation and error-handling pattern through its dependency on FND_API. It delegates shared formula-level logic to GMD_FORMULA_COMMON_PUB, which centralizes common validations, processing, and cross-entity consistency checks. This separation allows detail-line maintenance to reuse the same business rules applied to formula headers, ensuring that detail operations remain consistent with the parent formula state, recipe associations, and validity rules.

Key Procedures and Functions

The ETRM metadata documents three procedures exposed by this package:

• INSERT_FORMULADETAIL — Creates a new formula detail line against an existing formula header. It validates the referenced material/item, quantity, unit of measure, and effective context, applies shared formula validations via GMD_FORMULA_COMMON_PUB, and writes the detail record.
• UPDATE_FORMULADETAIL — Modifies an existing formula detail line. It revalidates any changed attributes, enforces formula-status rules, and updates the detail row while preserving reference integrity to the parent formula and related recipe definitions.
• DELETE_FORMULADETAIL — Removes a formula detail line, subject to business rules governing whether a formula line may be deleted given its status, recipe usage, or validity constraints.

All three procedures return status and message information through the EBS API convention, allowing callers to distinguish success, warning, and error outcomes. Parameter lists are deliberately not reproduced here; only the documented purpose of each procedure is described.

Tables Accessed

The package reads and writes the following documented tables (via APPS synonyms):

• FM_FORM_MST_B — The formula master/header table, providing the parent formula context and status.
• FM_MATL_DTL — The material detail table storing the individual formula component lines.
• MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, MTL_SYSTEM_ITEMS_KFV, IC_ITEM_MST — Item master data used to validate and resolve the component items and their description/key flexfield values.
• GMD_RECIPES_B, GMD_RECIPE_VALIDITY_RULES — Recipe definitions and validity rules that constrain formula detail behavior.
• GMD_STATUS — Status code lookups used to derive and validate formula/record states.
• FND_USER — User identity, used for standard who-column auditing.
• PLITBLM — A PL/SQL index table type used internally for bulk processing and array handling.

Usage Notes

GMD_FORMULA_DETAIL_PUB is the supported programmatic entry point for maintaining formula detail lines. It is typically invoked from the OPM Formula Designer form logic through GMD_FORMULA_DESIGNER_PKG, and from higher-level formula processing in GMD_FORMULA_PUB. Both packages list it among their dependencies, confirming its role as a subordinate detail API within the formula subsystem. Custom extensions and integrations that must insert, change, or remove formula components should call this API rather than writing directly to FM_MATL_DTL, because the package enforces validation, status, and recipe-consistency rules. Because it relies on GMD_FORMULA_COMMON_PUB and FND_API, callers should initialize the FND global variables and check the returned API status before committing work. The package exists in both EBS 12.1.1 and 12.2.2 with the same public interface and is documented as VALID in the APPS schema.