Search Results get_startup_values

Overview

RCV_SETUP_S2 is a setup utility package body in the Oracle E-Business Suite Receiving (RCV) product family, owned by the APPS schema. Its purpose is to centralize the retrieval of Receiving organization setup attributes so that other receiving APIs, forms, and concurrent programs do not query the underlying setup tables directly. In EBS 12.1.1 and 12.2.2 the receiving module stores its organization-level options in the RCV_PARAMETERS table, keyed by ORGANIZATION_ID. RCV_SETUP_S2 provides a stable, error-handled access layer over that table and over organization name resolution, insulating callers from schema-level details and from the message-handling conventions used by the receiving and purchasing stack.

Key Procedures and Functions

The ETRM metadata documents two callable units within the package:

• get_org_name — A function that returns the descriptive name of a receiving organization for a supplied organization identifier. It resolves the value from the HR organization definition rather than from the receiving tables, so that error messages and diagnostics can display a human-readable organization name. The function returns a VARCHAR2 and traps all exceptions by returning NULL, which prevents setup-lookup failures from aborting the calling process merely because a name could not be resolved.
• get_receiving_flags — A procedure that returns the core Receiving parameter flags for a given organization: the blind receiving flag, the allow express delivery flag, the allow cascade transactions flag, and the allow unordered receipts flag. Each value is returned through a separate OUT parameter carrying the flag value as a VARCHAR2. Internally the procedure selects the corresponding columns from RCV_PARAMETERS for the supplied organization and raises NO_DATA_FOUND when no parameter row exists. On the no-data condition it invokes the message utility to raise the RCV_NO_OPTION application error, passing the organization identifier through get_org_name so the message text identifies the offending organization by name; the exception is then re-raised to the caller. Any other error is reported through the message utility with a progress indicator before being re-raised.

Tables Accessed

• RCV_PARAMETERS — The documented table referenced by this package. It stores receiving setup options at the organization level. RCV_SETUP_S2 reads the BLIND_RECEIVING_FLAG, ALLOW_EXPRESS_DELIVERY_FLAG, ALLOW_CASCADE_TRANSACTIONS, and ALLOW_UNORDERED_RECEIPTS_FLAG columns for the requested organization. The package performs read-only access; no inserts, updates, or deletes are documented.
• HR_ORGANIZATION_UNITS — Accessed through get_org_name to obtain the NAME of the organization. Although not listed among the package synonyms in the ETRM entry, the source explicitly selects from HR_ORGANIZATION_UNITS, and the value is used only for message text and diagnostics.

Usage Notes

RCV_SETUP_S2 is an internal receiving utility rather than a public integration API; the ETRM classification is OTHER. It is invoked by receiving forms, by receiving and purchasing APIs, and by concurrent programs whenever organization-level receiving behavior must be determined at run time — for example, to decide whether blind receiving or unordered receipt entry is permitted for the current organization. The package is also referenced by one other package in the APPS schema, indicating a layered dependency within the receiving code family. Custom code may call get_receiving_flags to validate setup prerequisites before performing receipt transactions, and get_org_name to render organization identifiers in user-facing messages. Because get_receiving_flags raises and re-raises exceptions after registering a message, callers should expect both NO_DATA_FOUND (missing setup) and general SQL errors to propagate and should handle them accordingly. The package header, RCV_SETUP_S2, should be referenced rather than the body, and direct queries against RCV_PARAMETERS should generally be avoided in favor of this wrapper to preserve consistent error handling across the receiving application.