Search Results arp_delete_dist_cover




Overview
Explore in AI Chat

Overview

The APPS.ARP_DELETE_DIST_COVER package is a technical utility package within the Oracle Receivables (AR) module of Oracle E-Business Suite. Its documented purpose is to support the deletion of accounting distribution records associated with receivables transactions, specifically those stored in the RA_CUST_TRX_LINE_GL_DIST table. The package name itself — combining "ARP" (the Receivables product prefix), "DELETE", and "DIST_COVER" — indicates that it acts as a coverage or wrapper routine for distribution deletion logic. Such packages are typically used internally by the Receivables application to remove general ledger distribution rows when transactions, lines, or associated adjustments are modified or reversed, ensuring that the subledger accounting entries remain consistent with the underlying business transaction. In the context of Oracle EBS 12.1.1 and 12.2.2, the package resides in the APPS schema, has a status of VALID, and is documented in the E-Business Suite Technical Reference Manual (ETRM) as an OTHER-classified API. It is not a public, customer-facing interface but rather a backend component relied upon by standard Receivables processing.

Key Procedures and Functions

The ETRM documentation records a single documented program unit within this package:

  • DELETE_DIST_COVER — The sole documented procedure. Its name indicates it serves as a cover or entry-point routine that orchestrates the deletion of distribution records. In practice, such a procedure is invoked to remove or clean up rows in the receivables distribution table when distributions must be regenerated, reversed, or otherwise invalidated. As a "cover" routine, it likely encapsulates the deletion logic so that standard Receivables processes can call a single, controlled interface rather than issuing direct DML against the distribution table. The documentation does not expose a parameter list, and no parameters should be assumed; the procedure is documented only by name and existence.

No functions are documented for this package, and the documented procedure count is one. The package also exposes package-level and package body units as part of its standard PL/SQL structure.

Tables Accessed

The package references a single documented table through the APPS synonym layer:

  • RA_CUST_TRX_LINE_GL_DIST — The Receivables customer transaction line general ledger distribution table. This table stores the accounting distribution lines (the debit and credit entries) generated for each customer transaction line. The ARP_DELETE_DIST_COVER package reads and/or deletes records from this table as part of its distribution-cleanup function. By operating on this table, the package directly affects the subledger accounting data that flows to the General Ledger, which is why its use is tightly controlled within standard Receivables processing.

The dependency information confirms that the package references RA_CUST_TRX_LINE_GL_DIST and that it is not referenced by any other documented package (zero referencing packages), suggesting it is a terminal utility invoked by internal Receivables logic rather than a shared foundation object.

Usage Notes

Given its classification as an OTHER API and its zero inbound package references, ARP_DELETE_DIST_COVER is not intended for direct invocation by customers or custom extensions. It is typically called by standard Oracle Receivables forms, concurrent programs, or internal PL/SQL routines when transaction distributions must be removed — for example, during transaction updates, reversals, or regeneration of accounting entries. Custom code should avoid calling this package directly, as doing so bypasses standard business logic and validation that normally accompany distribution changes. Because the package manipulates the RA_CUST_TRX_LINE_GL_DIST table, any improper use risks leaving subledger accounting data inconsistent. Developers investigating this object should focus on identifying the standard Receivables process that invokes DELETE_DIST_COVER and rely on supported APIs (such as the Receivables transaction APIs) rather than this internal cover routine. The ETRM documentation is limited to object metadata and dependency information; no parameter signatures or detailed procedural logic are published.