Search Results ar_conc_request_messages_s

Overview

ARP_MESSAGE is a utility package body in the APPS schema that provides the Oracle Receivables module with a centralized message-handling and debug-logging facility. Its principal business function is to standardize how Receivables programs, concurrent requests, and Oracle Forms-based routines record diagnostic output, accumulate informational and error messages, and surface those messages back to the user or to the concurrent manager log. Rather than relying on ad hoc use of DBMS_OUTPUT or FND_MESSAGE individually, ARP_MESSAGE wraps both into a single, controllable interface.

The package is classified as OTHER in the ETRM metadata, meaning it is not a published public API but an internal Receivables utility. It is highly embedded in the application: ARP_MESSAGE is referenced by 90 other packages, confirming that it is a foundational infrastructure component widely reused across Receivables processing logic. The package body is valid and resides in the APPS schema in both Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented interface exposes 16 procedures and functions, which fall into three functional groups: message assembly, debug output, and message retrieval/purge.

• INITIALIZE — Establishes package-level state (name, tokens, sequencing) at the start of a runtime session.
• SET_NAME — Assigns a name or identifier to the message context, typically the calling program.
• SET_LINE — Sets the current output line to which subsequent content is appended.
• SET_TOKEN — Binds a value to a named token, enabling parameter substitution into message text.
• PUT_LINE — Appends a line of text to the message buffer.
• FLUSH — Writes accumulated buffered output to the target destination (log or output device).
• DEBUG — Conditionally emits diagnostic text, typically gated by a profile-based debug flag.
• GET — Retrieves the current message content.
• SET_ERROR — Registers an error condition for subsequent reporting.
• PUT_DB_ERROR — Captures and formats a database error for logging and display.
• CLEAR — Resets the message buffer and associated state.
• MESSAGE_COUNT — Returns the number of messages currently held.
• PURGE_MESSAGES — Removes stored messages, used to clean up the message repository.
• LAST_MESSAGE_SEQUENCE — Returns the highest sequence number assigned, supporting ordered retrieval.
• GET_LAST_FEW_MESSAGES — Returns the most recently recorded messages, typically for display after a request completes.

Tables Accessed

ARP_MESSAGE reads and writes the following tables through APPS synonyms:

• AR_CONC_REQUEST_MESSAGES — the Receivables concurrent request message store; messages assembled by the package are persisted here so they can be viewed against a concurrent request.
• AR_CONC_REQUEST_MESSAGES_S — the sequence-bearing companion table that supplies ordered identifiers used by LAST_MESSAGE_SEQUENCE and GET_LAST_FEW_MESSAGES.
• PLITBLM — the standard PL/SQL table (index-by table) type owned by PUBLIC, referenced for procedural bulk collection handling rather than as a business data source.

Additional dependencies include FND_GLOBAL, FND_MESSAGE, and FND_PROFILE for session context, message lookup, and debug-level profile options, and HZ_UTILITY_V2PUB for Trading Community Architecture utility calls.

Usage Notes

ARP_MESSAGE is invoked internally by Receivables concurrent programs and Oracle Forms to record progress and error information. Calling code typically executes INITIALIZE, then issues PUT_LINE and DEBUG calls during processing, and finally FLUSH or PURGE_MESSAGES. Because it is referenced by 90 packages, developers modifying it must account for broad downstream impact. It is not referenced by any database object outside this dependency set, and it is not intended as a customer-facing extension point; custom code should prefer documented public APIs and invoke ARP_MESSAGE only for parity with standard Receivables logging behavior.