Search Results get_next_word

Overview

ARP_STANDARD (source file ARPLSTDS.pls, version 120.4) is a foundational shared utility package in the Oracle Receivables (AR) module of Oracle E-Business Suite. It is not a business-transaction API in its own right; instead it functions as a common library of constants, record types, global variables, and helper routines on which the majority of Receivables PL/SQL objects depend. The ETRM classification of "OTHER" reflects this supporting role. The package is declared in the APPS schema, and its currency is evidenced by the fact that it is referenced by 345 other packages across Receivables and adjacent modules.

The package body opens by declaring public constants that recur throughout Receivables logic: MAX_END_DATE (31-12-2199) and MIN_START_DATE (01-01-1900), which establish the effective date boundaries used in date-range validation, and AR_ERROR_NUMBER (-20000), the standard error token raised through application error handling. It also defines the PROFILE_TYPE and PRV_MESSAGE_TYPE record structures, which respectively capture FND session context (application, program, request, user, login, and language) and preserve the parameters of the last message raised through FND_MESSAGE, allowing a calling block to inspect or re-emit that message. Public variables such as sysparm AR_SYSTEM_PARAMETERS%ROWTYPE and the profile record expose this shared state to callers.

Key Procedures and Functions

The package exposes 60 documented procedures and functions. Among them, GET_NEXT_WORD is the routine most frequently queried by developers; it performs word-level parsing of an input string, typically used to tokenize or step through delimited text within Receivables message and string processing. The remainder fall into recognizable utility families:

• Numeric and logical helpers: CEIL, EVEN, ODD, CHECK_FLAG, CLEAR_FLAG, SET_FLAG. These provide rounding and flag-manipulation services used consistently across AR code instead of ad hoc logic.
• Message handling: FND_MESSAGE, PREVIOUS_MESSAGE, MD_MSG_NUMBER, MD_MSG_TEXT, MD_MSG_NAME, MD_MSG_TOKENS, MD_MSG_EXPLANATION, and MD_MSG_FIND_NUMBER. These wrap or extend the FND_MESSAGE facility, capturing and retrieving message names, tokens, and explanatory text.
• Financial and calendar helpers: FUNCTIONAL_AMOUNT, GL_DATE_RANGE_OPEN, GL_PERIOD_INFO, GL_PERIOD_NAME, and AR_LOOKUP, which support currency conversion context, open GL date-range checks, period derivation, and flexfield lookup value retrieval.

These routines are called internally rather than exposed to end users, and their signatures should always be verified against the installed package specification before custom use.

Tables Accessed

The package reads and writes several core Receivables and shared tables through APPS synonyms. AR_SYSTEM_PARAMETERS supplies the sysparm global row that governs Receivables-wide defaults. RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, and RA_CUST_TRX_TYPES underpin transaction-type and transaction-line validation. AR_VAT_TAX supports tax-determining logic. GL_PERIOD_STATUSES is consulted by GL_PERIOD_INFO and GL_PERIOD_NAME for period name and status resolution. FND_NEW_MESSAGES supports message retrieval through the MD_MSG family. MO_GLOB_ORG_ACCESS_TMP is an organization-access temporary table used in multi-org filtering, and PLITBLM, UTL_FILE, and DBMS_SQL are referenced for table-based array handling, file I/O, and dynamic SQL respectively.

Usage Notes

ARP_STANDARD is invoked indirectly rather than by end users. Oracle Receivables forms, concurrent programs, and the AutoInvoice, Automatic Receipts, and dunning pipelines call its helpers through the standard Receivables APIs that depend upon it. Custom PL/SQL should call ARP_STANDARD only for its genuinely reusable utilities (for example, GET_NEXT_WORD for string parsing or GL_PERIOD_NAME for period derivation), and should rely on the public specification rather than direct table access. Because 345 packages reference it, any customization should treat the package as read-only; modifications risk wide-ranging regressions across Receivables. Session context should always be populated in the profile record before calling message- or profile-dependent routines.