Results for “validate_dates”

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

Overview

GMD_ROUTINGS_PVT is a private PL/SQL package in the Oracle E-Business Suite Process Manufacturing (OPM) module. It provides the underlying implementation logic for maintaining routing definitions within the GMD (Process Manufacturing Development / Routings) schema. Routings in OPM describe the sequence of operations, resources, and steps required to manufacture a product, and this package encapsulates the insert and update operations against the routing entities, together with validation logic that enforces date-related business rules. The package is declared with AUTHID CURRENT_USER and carries an internal API version constant (m_api_version := 1) and a package name constant, following the standard EBS private-API conventions. It is classified as a PVT (private) API, meaning it is not intended as a directly callable public interface; instead it is wrapped and invoked by companion public packages such as GMD_ROUTINGS_PUB and by the OPM routing forms and concurrent processes. Four other packages reference it, confirming its role as a shared internal worker routine. The header revision identifier (GMDVROUS.pls 120.2) places the last substantive source change at 2010, consistent with the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

• INSERT_ROUTING — Accepts a full row image of the GMD_ROUTINGS record (p_routings) and performs an insert of a new routing. It returns standard EBS API outputs: message count, message list, and return status, allowing the caller to evaluate success or failure through the conventional x_return_status / x_message_list pattern.
• UPDATE_ROUTING — Performs an update against an existing routing identified by routing_id. Rather than requiring a full row, it accepts an update table type (gmd_routings_pub.update_tbl_type) so that only the columns supplied by the caller are modified. As with INSERT_ROUTING, it returns message count, message list, and return status.
• VALIDATE_DATES — A function (added under Bug 5197863) that validates the effective start and effective end dates for a given routing. It accepts the routing identifier along with the proposed start and end dates and returns a numeric result indicating validity. This enforces the effective-dating rules that govern routing versions.

Tables Accessed

The package operates against the core OPM routing tables and their supporting entities through APPS synonyms:

• GMD_ROUTINGS — the primary routing entity; the target of INSERT_ROUTING and source of the row type used by both DML procedures.
• GMD_ROUTINGS_B — the base (language-independent) routing table, holding the routing header attributes.
• FM_ROUT_DTL — routing detail lines, i.e. the operations/steps belonging to a routing.
• GEM5_ROUTING_ID_S — the sequence used to generate routing identifiers.
• GMD_OPERATIONS_B — operation definitions referenced when building routing steps.
• GMD_RECIPES_B and GMD_RECIPE_VALIDITY_RULES — recipe and recipe effective-date rules used to validate that a routing's validity window is consistent with associated recipes.
• PLITBLM — the standard EBS message table used to accumulate and return API error and warning messages.

Usage Notes

GMD_ROUTINGS_PVT is not intended for direct invocation by end users or external integrations. It is called indirectly through the public routing API layer and from the OPM routing maintenance forms in Oracle EBS 12.1.1 and 12.2.2. Custom code that needs to create or modify routings should call the corresponding public package (GMD_ROUTINGS_PUB) rather than this private package, because the private package assumes the caller has already performed the validation and setup handled by the public wrapper. When invoked, callers must inspect x_return_status and, on failure, read x_message_list for the diagnostic text assembled from PLITBLM. The VALIDATE_DATES function is useful before committing a routing change, since it confirms that the effective start and end dates do not conflict with existing recipe validity rules. Because the source header dates to 2010 and the package is designated PVT, its signature should be treated as internal and subject to change; any dependence on it from custom code carries upgrade risk.