Results for “action_code”

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

Overview

GMD_COMMON_VAL is a shared validation package body owned by the APPS schema in Oracle E-Business Suite Process Manufacturing (GMD). Its documented purpose is to centralize validation functions and procedures consumed by more than one area of GMD, specifically Routings, Operations, Formula, Quality Control, Recipes, and Laboratory modules. The package header comment explicitly notes that certain common validation routines (validate_um, validate_orgn_code, validate_type) reside instead in GMA_VALID_GRP, establishing GMD_COMMON_VAL as one node in a family of shared validation utilities rather than a module-specific API.

The package is classified as OTHER under the ETRM documentation taxonomy for 12.1.1 and 12.2.2. It exposes 18 documented procedures and functions and is referenced by 25 other packages, confirming its role as a low-level shared service invoked broadly across Process Manufacturing. The header carries a $Header tag from GMDPCOMB.pls (version 120.15.12010000.2, last modified 2008/11/06), indicating a long-lived, stable code base. A debug flag mechanism introduced under Bug 3222090 uses FND_LOG.LEVEL_PROCEDURE against FND_LOG.G_CURRENT_RUNTIME_LEVEL to toggle trace output.

Key Procedures and Functions

The documented callable units fall into recognizable functional clusters:

• Date validation: CHECK_FROM_DATE, CHECK_DATE, and CHECK_DATE_RANGE. These return a numeric status and accept a form-context indicator; in the visible source excerpt the date checks are stubbed to return 1, consistent with reused control-flow contracts.
• Party and user validation: GET_CUSTOMER_ID, CUSTOMER_EXISTS, CHECK_USER_ID, and CHECK_PROJECT_ID provide lookup and existence checks against customer, user, and project entities used across formulas, routings, and recipes.
• Quantity and loss calculations: CALCULATE_PROCESS_LOSS, CALCULATE_TOTAL_QTY, CALCULATE_TOTAL_PRODUCT_QTY, and GET_ROUTING_SCALE_FACTOR support process yield, scaling, and recipe quantity roll-ups.
• Charge computation: CALCULATE_CHARGES and CALCULATE_STEP_CHARGES compute resource and operation-level charges from routing and resource master data.
• Workflow and status control: GET_STATUS, ACTION_CODE, VERSION_CONTROL_STATE, RUN_STATUS_UPDATE, and UPDATE_ALLOWED govern recipe/routing versioning, status transitions, and whether a record may be modified.
• Access control: CHECK_FORMULA_ITEM_ACCESS verifies whether a user may reference a given formula item.

Parameter lists are intentionally not reproduced here; callers should reference the package specification for exact signatures.

Tables Accessed

The package reads and writes the following tables via APPS synonyms. Routing structures (FM_ROUT_HDR, FM_ROUT_DTL, FM_ROUT_DEP) supply header, detail, and dependency data for routing validation and scaling. Resource and operation definitions (CR_RSRC_MST, CR_RSRC_DTL, CR_RSRC_MST_B, GMD_OPERATIONS, GMD_OPERATION_ACTIVITIES, GMD_OPERATION_RESOURCES) back the charge and resource calculations. Recipe and composition records (GMD_RECIPES, CM_CMPT_DTL, CM_MTHD_MST, CM_CLDR_DTL) are consulted during formula, recipe, and validity-window checks; CM_CLDR_DTL and CM_MTHD_MST specifically support calendar and method/validity lookups. GMD_PROCESS_LOSS and GMD_STATUS provide loss percentages and lifecycle status codes used by the calculation and status procedures.

Usage Notes

GMD_COMMON_VAL is not an end-user-facing interface; it is invoked programmatically. Typical callers are Process Manufacturing forms (Routings, Operations, Formula, Recipe) that require consistent validation of dates, customers, users, quantities, and status transitions. It is also called by concurrent programs and by the 25 other PL/SQL packages that reference it, forming part of the internal validation layer. Custom extensions should invoke the documented functions rather than duplicating validation logic, respecting the return-code convention used across the package. Debug tracing can be enabled by raising the FND_LOG runtime level to LEVEL_PROCEDURE, which sets the internal l_debug flag to 'Y'. Because behavior is shared across modules, changes to this package carry broad regression risk and should be validated against all dependent modules.