Search Results override_routing

Overview

RCV_SETUP_S is a Receiving setup utility package in the Oracle E-Business Suite APPS schema. Its purpose is to centralize the retrieval of Receiving configuration and profile option values so that other Receiving modules can determine runtime behavior consistently. Rather than embedding profile lookups throughout the application, the Receiving code base delegates these decisions to small, dedicated functions within RCV_SETUP_S. Each function encapsulates a single setup question — such as whether routing may be overridden, or how transactions should be processed — and returns a normalized value that callers can rely upon. Because the package abstracts profile options behind well-defined functions, the underlying configuration model can change without forcing every caller to be rewritten. The package is classified as OTHER in the ETRM metadata, indicating it is a supporting utility rather than a public or user-facing API. Its source header dates back to the early 11i era (115.1, 2002), and the package remains in use across 12.1.1 and 12.2.2.

Key Procedures and Functions

• get_override_routing — Returns the Override Routing Option. It reads the OVERRIDE_ROUTING profile option via FND_PROFILE and, when the retrieved value is NULL, defaults to 'N'. The function documents that this default ensures a deterministic behavior when the profile has not been explicitly set.
• get_trx_proc_mode — Returns Receiving's Transaction Processor Mode, governed by the RCV_TP_MODE profile option. When the profile value is NULL, the function defaults the mode to 'ONLINE'. This is the object associated with the searched term "get_trx_proc_mode" and represents the primary entry point for determining whether Receiving transactions are processed online or through the concurrent manager.

Both functions follow an identical defensive pattern: an internal progress flag is initialized, the profile value is fetched, a NULL result is coerced to a documented default, and the value is returned. Both also include an EXCEPTION handler that, on any error, logs the failure through PO_MESSAGE_S.SQL_ERROR with the function name and progress indicator before re-raising the exception. The metadata records six functions in total, though only the two above are described in the available excerpt.

Tables Accessed

The ETRM metadata documents MTL_PARAMETERS as the only table referenced by this package (via APPS synonyms). MTL_PARAMETERS is the Inventory organization parameters table and holds organization-level receiving controls that complement profile-based settings. Access is read-only; the package does not write configuration data. Where profile retrieval is insufficient, MTL_PARAMETERS supplies the organization-scoped defaults that influence receiving behavior.

Usage Notes

RCV_SETUP_S is invoked internally rather than by end users directly. It is called by Receiving forms, Receiving concurrent programs, and the Receiving transaction APIs whenever the runtime mode or routing behavior must be established. The metadata indicates the package is referenced by five other packages, confirming its role as a shared dependency within the Receiving subsystem. Custom code that extends Receiving should follow the same convention and call these functions instead of querying FND_PROFILE directly, which preserves the NULL-defaulting behavior and keeps error logging consistent. Because the functions are lightweight, single-purpose profile readers, they are safe to call frequently, but callers should be aware that a NULL profile value is never returned — the documented defaults ('N' for override routing, 'ONLINE' for transaction processor mode) are always applied.