Search Results ar_adjvalidate_pub




Overview
Explore in AI Chat

Overview

AR_ADJVALIDATE_PUB is a public PL/SQL package in the APPS schema of Oracle E-Business Suite (documented in ETRM for both 12.1.1 and 12.2.2). It provides the centralized validation layer for Oracle Receivables adjustments — the credit memos, debit memos, write-offs, claims, and other manual or automatic adjustments that reduce or increase a customer's outstanding balance. Rather than embedding validation logic inside each calling program, Receivables exposes this package so that any API, form, or custom routine can confirm that an adjustment is legal before it is written to the base tables.

The "PUB" (public) prefix indicates that the package is a supported, callable interface, so it can be referenced directly from custom code. Internally, it is used by AR_ADJUSTAPI_PUB, the adjustments API package, which is listed among its referencing objects. The package also references FND_MSG_PUB for standardized message retrieval and message-stack token handling, so that validation failures are reported in the same way as native Receivables errors.

Key Procedures and Functions

Fifteen documented subprograms form the validation surface of the package:

  • INIT_CONTEXT_REC — Initializes the session context record required by the remaining routines.
  • AAPI_MESSAGE — Handles error/warning message generation and message-stack interaction.
  • CACHE_DETAILS — Populates an in-memory cache of adjustment and related reference data to reduce repeated table lookups during validation.
  • WITHIN_APPROVAL_LIMITS — Checks whether the adjustment amount falls within the approval limits configured for the user.
  • VALIDATE_TYPE — Verifies the adjustment type/reason against valid Receivables transaction types.
  • VALIDATE_PAYSCHD — Confirms the referenced payment schedule line (installment) is valid and eligible for adjustment.
  • VALIDATE_AMOUNT — Validates the adjustment amount (sign, currency precision, and residual balance rules).
  • VALIDATE_RCVTRXCCID — Validates the receivables transaction and code combination associated with the adjustment.
  • VALIDATE_DATES — Checks GL date, adjustment date, and open-period rules.
  • VALIDATE_REASON_CODE — Confirms the adjustment reason code is defined and active.
  • VALIDATE_DOC_SEQ — Validates document sequence assignment where required.
  • VALIDATE_ASSOCIATED_RECEIPT — Ensures any cash receipt linked to the adjustment is legitimate and consistent.
  • VALIDATE_USSGL_CODE — Validates the USSGL transaction code used for federal/GL accounting.
  • VALIDATE_DESC_FLEXFIELD — Validates the descriptive flexfield segments attached to the adjustment.
  • VALIDATE_CREATED_FROM — Checks the "created from" indicator so the adjustment originates from a supported source.

Tables Accessed

The package reads (and in some cases derives values from) the following documented tables via APPS synonyms: AR_ADJUSTMENTS and AR_PAYMENT_SCHEDULES for adjustment and installment data; AR_APPROVAL_USER_LIMITS for approval thresholds; AR_CASH_RECEIPTS for associated receipts; AR_RECEIVABLES_TRX for receivable transaction types; AR_SYSTEM_PARAMETERS for system options; FND_DESCRIPTIVE_FLEXS for flexfield definitions; FND_DOCUMENT_SEQUENCES for sequence validation; FND_PROFILE_OPTION_VALUES for profile-driven behavior; GL_CODE_COMBINATIONS and GL_USSGL_TRANSACTION_CODES for accounting combinations; GL_PERIOD_STATUSES for open/closed period checks; RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES for the parent transaction and its lines; and PLITBLM, the PL/SQL table used for message/error buffering.

Usage Notes

AR_ADJVALIDATE_PUB is normally invoked indirectly. The Receivables Adjustments form and the AR_ADJUSTAPI_PUB adjustments API call it before committing an adjustment, so developer code that uses AR_ADJUSTAPI_PUB automatically inherits its validation coverage. Direct invocation is appropriate in custom integration code (for example, interfaces loading adjustments from an external system) where adjustments must be validated prior to insertion, and in diagnostic routines that reproduce the standard validations. Callers should set context with INIT_CONTEXT_REC, load reference data via CACHE_DETAILS for batch scenarios, and inspect the message stack (through AAPI_MESSAGE) to report failures in a receivables-standard format.