Search Results recipe_cust_exists

Overview

GMD_RECIPE_VAL is a public PL/SQL validation package in the Oracle E-Business Suite Process Manufacturing (OPM) module, owned by the APPS schema. Its stated function, per the embedded header comments, is to "validate entities within a recipe." The package bundles the referential, temporal, and quantitative integrity checks that must succeed before a recipe and its component relationships are accepted as valid. It is classified as an OTHER API within ETRM, meaning it is intended primarily for internal consumption by OPM forms and sister packages rather than as a formally versioned open interface.

The header identifies the package as Version 1.0, with a change history that includes a Bug 2099699 modification by Sukarna Reddy dated 03/14/02, which introduced routing validity checking. ETRM 12.2.2 documents 16 procedures and functions in total, with six other packages depending on it, confirming its role as a shared validation utility across the recipe sub-schema.

Key Procedures and Functions

The documented callable units cover the principal validation categories required by recipe maintenance:

• RECIPE_EXISTS — the routine associated with the user search term "recipe_cust_exists" and its sibling existence check. It verifies that a recipe identified by ID, number, and version combination resolves to a valid row, returning the recipe ID on success.
• RECIPE_CUST_EXISTS — validates whether a given recipe-to-customer association exists for a specified recipe ID and customer ID, returning success or failure. This supports customer-specific recipe assignments in the GMD_RECIPE_CUSTOMERS entity.
• RECIPE_NAME — resolves a recipe from its name and version input against an action code, returning the recipe ID.
• RECIPE_FOR_UPDATE — acquires a row lock on a recipe using the recipe ID and last update date, honoring either asynchronous or form invocation context.
• RECIPE_DESCRIPTION — validates the recipe description attribute and reports success or failure.
• RECIPE_ORGN_CODE — validates organization code against user context and returns a plant indicator.
• PROCESS_LOSS_FOR_UPDATE — locks the process loss row for a recipe and organization combination.
• CHECK_ROUTING_VALIDITY — introduced by Bug 2099699, returns true or false for routing validity based on routing ID and recipe status.
• VALIDATE_START_DATE / VALIDATE_END_DATE / EFFECTIVE_DATES — enforce effective date range integrity for recipe validity rules.
• STD_QTY / MAX_QTY / CALC_INV_QTYS / CALCULATE_PROCESS_LOSS — validate and compute standard quantity, maximum quantity, inventory quantities, and process loss values.
• CHECK_FOR_DUPLICATE — detects duplicate recipe definitions.

Tables Accessed

Through APPS synonyms, the package reads and writes GMD_RECIPES and its _B (base) table plus the GMD_RECIPE_ID_S sequence for identifier resolution and existence checks. Customer-specific validation touches GMD_RECIPE_CUSTOMERS. Parameter and process loss validation reference GMD_PARAMETERS_HDR, GMD_PROCESS_LOSS, and GMD_RECIPE_PROCESS_LOSS. Effective date and validity rule enforcement use GMD_RECIPE_VALIDITY_RULES. Routing checks consult GMD_ROUTINGS_B, while GMD_STATUS supplies status code decoding. DUAL supports simple single-row lookups.

Usage Notes

GMD_RECIPE_VAL is normally invoked from OPM recipe maintenance forms and from the six dependent packages documented in ETRM, rather than from external integrations. Custom code may call it where a recipe, customer association, effective date range, or routing validity must be confirmed before a DML operation. Because the procedures follow FND_API messaging conventions—p_api_version, p_init_msg_list, p_commit, p_validation_level, and x_return_status/x_msg_count/x_msg_data outputs—callers should inspect x_return_status and drain the message stack on failure. Row-locking routines such as RECIPE_FOR_UPDATE and PROCESS_LOSS_FOR_UPDATE should be called in a transactional context immediately preceding the intended update.