Search Results g_msg_medium

Overview

AR_ADJVALIDATE_PUB is a public PL/SQL package in the Oracle E-Business Suite Receivables module (APPS schema) that centralizes the validation logic applied to manual adjustments before they are created or applied against a transaction. The package exposes a public API (PUB classification), meaning its procedures are intended to be callable from external code such as forms, concurrent programs, and custom integrations, rather than being restricted to internal package use.

Its primary business role is to enforce the business rules that govern whether an adjustment is permissible: checking the adjustment type and reason code, verifying that the operator has approval authority for the requested amount, confirming that the associated payment schedule and receipt are valid, validating accounting date ranges against open GL periods, and validating the accounting flexfield (code combination) as well as the USSGL transaction code. In effect, it is the gatekeeper that prevents invalid adjustments from being posted and provides consistent, reusable validation across all entry points.

The package header version identifier (115.9, dated 2003) reflects the long-standing lineage of this code, which has been carried forward largely unchanged into the 12.1.1 and 12.2.2 releases. Because the logic is packaged rather than embedded in individual forms, the same rules apply whether an adjustment is entered interactively or through an interface.

Key Procedures and Functions

The documented API comprises fifteen procedures and functions, each addressing a discrete validation or setup concern:

• INIT_CONTEXT_REC — Initializes the internal context record that caches profile option settings controlling validation behavior, such as the USSGL option, the override-activity option, and unique sequence number handling. This is typically the first call made by a client.
• AAPI_MESSAGE — Retrieves and returns API messages accumulated in the FND message stack, enabling callers to surface validation errors to the user or log them.
• CACHE_DETAILS — Populates internal cache tables (lookups, adjustment types, reasons, receivables transaction types, USSGL codes, and GL periods) to reduce repetitive database queries during a validation cycle. The package uses flags such as G_caching_done and the G_MSG_LEVEL constants (G_MSG_HIGH, G_MSG_MEDIUM, G_MSG_LOW, G_MSG_UERROR, G_MSG_ERROR) to manage debug and error reporting during caching.
• WITHIN_APPROVAL_LIMITS — Determines whether the adjustment amount falls within the approval authority granted to the user, referencing AR_APPROVAL_USER_LIMITS. This is the function most closely associated with approval enforcement.
• VALIDATE_TYPE — Validates the adjustment type against receivables transaction types.
• VALIDATE_PAYSCHD — Validates the payment schedule to which the adjustment is applied.
• VALIDATE_AMOUNT — Confirms the adjustment amount is acceptable.
• VALIDATE_RCVTRXCCID — Validates the receivables transaction and its associated code combination.
• VALIDATE_DATES — Checks adjustment dates against open accounting periods (GL_PERIOD_STATUSES).
• VALIDATE_REASON_CODE — Validates the adjustment reason code from AR_LOOKUPS.
• VALIDATE_DOC_SEQ — Validates document sequence assignment via FND_DOCUMENT_SEQUENCES.
• VALIDATE_ASSOCIATED_RECEIPT — Validates the associated cash receipt (AR_CASH_RECEIPTS).
• VALIDATE_USSGL_CODE — Validates the USSGL transaction code used for budgetary accounting.
• VALIDATE_DESC_FLEXFIELD — Validates descriptive flexfield segments.
• VALIDATE_CREATED_FROM — Validates the origin (created-from) of the adjustment.

Tables Accessed

The package touches a broad set of reference and transactional tables:

• AR_ADJUSTMENTS and AR_PAYMENT_SCHEDULES — the core adjustment and payment schedule records being validated.
• AR_APPROVAL_USER_LIMITS — source of user approval thresholds.
• AR_RECEIVABLES_TRX — receivables transaction type definitions.
• AR_CASH_RECEIPTS and AR_SYSTEM_PARAMETERS — receipt validation and system configuration.
• RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES — the transactions to which adjustments apply.
• GL_CODE_COMBINATIONS, GL_PERIOD_STATUSES, GL_USSGL_TRANSACTION_CODES — accounting flexfield, period, and USSGL validation.
• FND_PROFILE_OPTION_VALUES, FND_DESCRIPTIVE_FLEXS, FND_DOCUMENT_SEQUENCES — profile options, flexfield definitions, and document sequencing.
• PLITBLM — the standard EBS message/table handler utility used for multi-row error communication.

Usage Notes

AR_ADJVALIDATE_PUB is invoked whenever a manual adjustment must be validated. The most common caller is the Receivables Adjustments form, which calls the validation procedures interactively as the user completes the adjustment. The package is also referenced by one other package, indicating it is embedded within the standard adjustment processing flow. Custom code and interfaces should call INIT_CONTEXT_REC first to populate the profile-driven context, then the individual VALIDATE_* procedures, and finally AAPI_MESSAGE to retrieve any errors. Because the package caches lookup and period data internally, it is best used within a single logical validation session rather than across long-running batch processes without re-initialization. The G_MSG_HIGH constant observed in the source maps to FND_MSG_PUB.G_MSG_LVL_DEBUG_HIGH, confirming that the package emits high-severity debug messages through the standard FND message stack.