Search Results arp_update_adj_cover




Overview
Explore in AI Chat

Overview

ARP_UPDATE_ADJ_COVER is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. It belongs to the Oracle Receivables (AR) module and is classified in the ETRM repository under the generic API category designated as OTHER, indicating that it is an internal utility routine rather than a formally published public API. The package carries a VALID status in the ETRM 12.2.2 dictionary, and the same object is also catalogued for the 12.1.1 code line, where the Receivables adjustment architecture is unchanged.

The business function of the package is narrow and specific: it maintains the "cover" application of an adjustment against a receivable. In Receivables terminology, an adjustment may be applied directly to a transaction (for example, a write-off or a debit memo reversal) or it may be applied as a cover against another adjustment, thereby reducing or offsetting the amount of that parent adjustment. The UPDATE_ADJ_COVER routine exists to establish or refresh that relationship in the AR_ADJUSTMENTS table so that the adjustment hierarchy and the underlying accounting remain consistent.

Key Procedures and Functions

ETRM documents a single entry point on this package: UPDATE_ADJ_COVER. No formal parameter signature is published in the metadata, and none should be assumed. Based on its name and its single documented dependency, the procedure accepts identifying information for an adjustment and the amount or reference used to cover it, then writes the resulting cover relationship back to the adjustment record. It should be treated as an internal helper called by the Receivables adjustment form logic and by the standard adjustment processing flow whenever a cover is created, modified, or removed. Because the API classification is OTHER rather than a supported public interface, Oracle does not warrant its signature across releases, and callers should not bind to it directly in custom code without a documented compatibility review.

Tables Accessed

The package references exactly one documented table through APPS synonyms: AR_ADJUSTMENTS. This is the core Receivables table that stores every adjustment applied to a transaction, including the adjustment number, type, amount, applicable date, status, and the linkage columns that identify the parent adjustment when one adjustment covers another. ARP_UPDATE_ADJ_COVER reads and updates rows in AR_ADJUSTMENTS to set or clear the cover linkage on the child adjustment. No other application tables, views, or sequences are listed in the ETRM dependency extract, and the only external references are to the SYS STANDARD package used for standard PL/SQL constructs. Writes to this table directly affect Receivables reporting, the adjustment register, and any downstream accounting entries generated from the adjustment, so the procedure is considered data-modifying rather than read-only.

Usage Notes

In normal operations the package is invoked indirectly. The Adjustments window in the Receivables responsibility, and the underlying adjustment processing logic, rely on this routine when a user creates an adjustment that covers another adjustment or when an existing cover must be revised. It is not exposed as a standalone concurrent program and no request group is documented for it in ETRM.

  • Custom code should call the supported Receivables adjustment APIs, such as the AR_ADJUSTMENT_API family, rather than ARP_UPDATE_ADJ_COVER directly.
  • Because the procedure writes to AR_ADJUSTMENTS, any direct invocation must be followed by a commit under the calling application's transaction control.
  • Adjustment records altered without corresponding subledger accounting must be reconciled, since cover relationships influence the accounting performed by Receivables.
  • ETRM lists no packages that reference ARP_UPDATE_ADJ_COVER, confirming its role as a leaf-level internal utility rather than a shared component.
  • Customers upgrading between 12.1.1 and 12.2.2 should verify the signature through the ETRM browser, as only the procedure name is guaranteed by the documentation.