Search Results set_token

Overview

APPS.RCV_ERROR_PKG is the central error-handling utility for the Oracle E-Business Suite Receiving (RCV) module. Its primary business function is to provide a consistent, standardized mechanism for capturing, storing, and reporting error and warning messages generated during receiving transactions, particularly those flowing through the RCV_TRANSACTIONS_INTERFACE table and the associated PO_INTERFACE_ERRORS structure. Rather than allowing each receiving program to raise and format messages independently, this package centralizes the logic for raising errors, accumulating an error stack, and writing interface-level diagnostics back to the purchasing interface error tables.

The package is classified under the "OTHER" API category in ETRM for release 12.2.2 and maintains the same core behavior across 12.1.1 and 12.2.2. It has wide reuse across the application, being referenced by 31 other packages, which confirms its role as foundational infrastructure rather than a business-facing API. The source header (RCVERRB.pls, version 120.1) shows it is marked "noship," indicating it is an internal utility not intended for direct customer invocation, though it remains visible and callable within the EBS schema.

Key Procedures and Functions

The package exposes 31 documented procedures and functions. The most relevant to the "set_token" search are the message-construction routines:

• SET_TOKEN — Substitutes a value into a previously defined named token within a message string, supporting the standard FND_MESSAGE token substitution model before the message is retrieved.
• SET_ERROR_MESSAGE — Establishes the current error message text and name that subsequent calls will push onto the error stack.
• SET_SQL_ERROR_MESSAGE — Records an Oracle database SQL error (SQLCODE/SQLERRM) into the error framework.
• LOG_INTERFACE_ERROR / LOG_INTERFACE_ERROR_MESSAGE — Write a fatal-level error against the purchasing interface error tables, populating the interface identifiers.
• LOG_INTERFACE_WARNING / LOG_INTERFACE_MESSAGE — Non-fatal counterparts that record warnings or informational messages without aborting processing.
• TEST_IS_NULL — Validation helper used to detect null inputs before logging occurs.
• CHECK_AND_RESET_RESULT / CHECK_AND_NORESET_RESULT / CHECK_AND_NORESET_RESULT — Inspect the accumulated result status and optionally reset the internal pg_current_result flag.
• HAS_ERRORS — Returns whether any errors have been accumulated during the current run.
• INITIALIZE — Resets package-level state (error count, stack, identifiers) prior to a new processing cycle.
• CLEAR_MESSAGES — Empties the pending message stack.
• GET_LAST_MESSAGE — Retrieves the most recently recorded message.
• DEFAULT_AND_CHECK — Applies defaults to incoming arguments and performs validation checks.

Tables Accessed

The package operates against two documented tables through APPS synonyms:

• PO_INTERFACE_ERRORS — The primary write target. Interface errors, warnings, and messages are inserted here, keyed by interface type, batch ID, interface header ID, and interface line ID. The package-level constants pg_transactions_interface and pg_default_interface_type ('RCV-856') govern which interface records are affected.
• FND_NEW_MESSAGES — Used to resolve message names and text, particularly when the package sets and retrieves messages through the Oracle Application Object Library message framework.

Usage Notes

RCV_ERROR_PKG is typically invoked from receiving concurrent programs, interface loaders, and correction screens rather than from end-user forms directly. Callers open processing with INITIALIZE, log errors or warnings via the LOG_INTERFACE_* routines, use SET_TOKEN and SET_ERROR_MESSAGE to build tokenized messages, then evaluate the outcome with HAS_ERRORS or CHECK_AND_RESET_RESULT. Because it is referenced by 31 other packages, custom code that processes RCV_TRANSACTIONS_INTERFACE records should mirror this pattern to keep interface errors consistent with standard EBS behavior.