Search Results create_operation

Overview

APPS.GMD_VERSION_CONTROL is a PL/SQL package in the Oracle E-Business Suite Process Manufacturing (OPM) product family. It manages the creation and versioning of process manufacturing entities — formulas, recipes, routings, operations, and substitutions — by generating the appropriate surrogate keys and inserting the header and detail rows that constitute each object version. The package status is documented as VALID in ETRM for both 12.1.1 and 12.2.2, and it is classified under the "OTHER" API classification, indicating that it is an internal support package rather than a published, externally supported integration API such as GMDFMVAL_PUB.

Version control is central to process manufacturing because formula, recipe, and routing definitions must be revised without destroying the prior approved definition. The package supplies the mechanism through which a validated object becomes a new versioned record, including the associated text blocks and attached documents that describe the object.

Key Procedures and Functions

The package exposes six documented procedures, each aligned to one process manufacturing entity:

• CREATE_FORMULA — creates a formula header and its associated material detail lines, drawing the new formula identifier from the GEM5_FORMULA_ID_S sequence.
• CREATE_RECIPE — creates a recipe record that links a formula version to its production context.
• CREATE_ROUTING — creates a routing header, using the GEM5_ROUTING_ID_S sequence for the routing identifier.
• CREATE_OPERATION — creates an operation within a routing step, obtaining identifiers from GEM5_OPRN_ID_S and GEM5_OPRNLINE_ID_S.
• CREATE_SUBSTITUTION — creates a substitution definition against a formula, writing to GMD_FORMULA_SUBSTITUTION.
• POPULATE_TEMP_TEXT — populates the temporary text table used to stage translatable descriptive text before it is committed to the text tables.

Parameter lists are not exposed in the ETRM metadata and are therefore not reproduced here. Callers should treat the signatures as internal and version-specific.

Tables Accessed

The package reads and writes the core OPM formula and routing tables through APPS synonyms. Formula data is stored in FM_FORM_MST and FM_FORM_MST_B (base and translated header rows), with material lines in FM_MATL_DTL. Routing headers reside in FM_ROUT_HDR and routing detail steps in FM_ROUT_DTL. Substitution data is held in GMD_FORMULA_SUBSTITUTION. Descriptive text is handled through FM_TEXT_TBL_TL and the temporary staging table populated by POPULATE_TEMP_TEXT. Attachments are recorded in FND_ATTACHED_DOCUMENTS, and FND_DUAL is used for single-row PL/SQL SELECT constructs. Key generation relies on the GEM5_* sequences covering formulas, formula lines, routings, routing steps, operations, and operation lines. FND_PROFILE is referenced for site or user profile option values.

Usage Notes

GMD_VERSION_CONTROL is not a public integration API. It is referenced by GMDFMVAL_PUB — the published formula validation API — and by itself, and it is only referenced by one other package in the documented dependency set. Consequently it is normally invoked indirectly: a user action in the OPM formula, recipe, or routing forms triggers validation or versioning logic that calls into this package. Custom code should call GMDFMVAL_PUB rather than GMD_VERSION_CONTROL directly, because Oracle does not guarantee the internal signatures or behavior of this package across patch levels or releases. Where customization is unavoidable, the invoking code must run in the APPS schema context with the standard EBS initialization, supply the GEM5_* sequence values consistently with the standard form behavior, and avoid bypassing the validation steps that GMDFMVAL_PUB performs.