Search Results get_process_loss_max_qtys

Overview

GMDRTVAL_PUB is a public PL/SQL package in the Oracle EBS Process Manufacturing (OPM) application, owned by APPS and classified as a PUB (public) API within the ETRM (Enterprise Transaction and Reference Model) documentation set. Its primary business function is to provide centralized validation services for routing definitions used in process manufacturing. Routings describe the sequence of operations, steps, and dependencies that a product or batch must follow during production, and the integrity of this data is critical to scheduling, costing, and batch execution.

The package consolidates business-rule validation logic so that both the Oracle Forms user interface and programmatic callers apply identical rules. It validates routing headers, routing classes, step numbers, operations, date ranges for validity rules, and ownership/organization codes, and it also computes process-loss metrics and derives step dependencies. By exposing these checks through a PUB API, Oracle allows customers and partners to invoke the same validation that forms and concurrent programs rely on, ensuring data consistency across interfaces, conversions, and custom extensions.

Key Procedures and Functions

• GET_THEORETICAL_PROCESS_LOSS — Returns the theoretical process-loss quantity for a given routing class and quantity.
• GET_FIXED_PROCESS_LOSS — Returns the fixed process-loss value defined for a routing class.
• CHECK_ROUTING_CLASS — Validates that a supplied routing class is valid; returns an error code constant such as GMD_INV_ROUTING_CLASS when invalid.
• CHECK_ROUTINGSTEP_NO — Verifies that a routing step number is not duplicated within a given routing.
• CHECK_OPRN — Validates an operation and version against the routing, including start and end dates and operation identifier.
• CHECK_ROUTING — Validates a routing by number and version, returning the routing identifier and a return status.
• CIRCULAR_DEPENDENCIES_EXIST — Detects circular step dependencies for a parent key, optionally in a batch context.
• GENERATE_STEP_DEPENDENCIES — Creates dependency records for the steps of a routing.
• GET_PROCESS_LOSS_MAX_QTYS — Retrieves maximum quantity thresholds used in process-loss calculations.
• GET_ROUTINGSTEP_INFO — Returns descriptive information for a routing step.
• VALIDATE_ROUTING_DETAILS — Performs consolidated validation of routing detail records.
• VALIDATE_ROUTING_VR_DATES — Validates the date ranges of routing-related validity rules, ensuring effective periods are consistent and correctly ordered.
• UPDATE_VR_WITH_RT_DATES — Updates validity-rule dates using routing dates.
• CHECK_ROUTING_OVERRIDE_EXISTS — Determines whether a routing override already exists.
• CHECK_DELETE_MARK — Checks whether a record is marked for deletion.
• CHECK_OWNERORGN_CODE — Validates the owner organization code against authorized organizations.
• CHECK_DEPROUTING — Validates dependent routing relationships.

The package also declares error return-code constants, including GMD_ROUTING_EXISTS, GMD_INV_ROUTING_CLASS, GMD_DUP_ROUTINGSTEP_NO, and GMD_INV_OPRN, which callers compare against returned status values.

Tables Accessed

The package reads and writes routing and recipe structures through APPS synonyms: GMD_ROUTINGS and GMD_ROUTINGS_B (routing headers and base rows), FM_ROUT_HDR, FM_ROUT_DTL, FM_ROUT_DEP, and FM_ROUT_CLS (routing headers, details, dependencies, and classes), and GMD_RECIPE_ROUTING_STEPS and GMD_RECIPE_STEP_MATERIALS (recipe-to-routing step links and step materials). Validity rules are validated against GMD_RECIPE_VALIDITY_RULES, which is the table central to VALIDATE_ROUTING_VR_DATES and UPDATE_VR_WITH_RT_DATES. Operations are checked in GMD_OPERATIONS and GMD_OPERATIONS_B, process-loss values are drawn from GMD_PROCESS_LOSS, and recipe references come from GMD_RECIPES_B. Step dependency records are managed in GME_BATCH_STEP_DEPENDENCIES, and user/organization authorization is confirmed using SY_ORGN_USR.

Usage Notes

GMDRTVAL_PUB is invoked primarily from Oracle Forms during entry and maintenance of routings, validity rules, and recipe steps, where it enforces duplicate, class, operation, and date-range checks before records are saved. Concurrent programs that import or generate routing data also call the validation procedures to apply the same rules. Because the package is classified as PUB and is referenced by nine other packages, it is the supported entry point for custom PL/SQL, conversions, and interfaces that need to validate routing or validity-rule dates programmatically. The pcalledby_form parameters on several functions allow callers to indicate whether validation originates from a form, enabling appropriate handling of error codes and messages. Custom code should call the documented functions and procedures rather than updating the underlying tables directly, and should interpret the standard error constants returned by the check routines.