Search Results delete_line_cover




Overview
Explore in AI Chat

Overview

ARP_DELETE_LINE_COVER is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is classified in the ETRM repository as an OTHER API, meaning it is not exposed as a formally published public interface but is invoked internally by the Receivables transaction line-processing layer. Its sole documented responsibility is to convert a set of scalar column parameters into a customer transaction line record and then delete the associated distribution line. The header comment in the package source identifies the unit as delete_line_cover, with the explicit description "Converts column parameters to a line record and delete a dist line." The package therefore acts as a low-level utility that shields callers from the mechanics of constructing a RA_CUSTOMER_TRX_LINES style record and removing the corresponding accounting distribution. The source header (ARTCTLDB.pls, version 115.6, dated 2004/05/04) indicates the object has been stable since the pre-R12 code line and was carried forward unchanged into the 12.1.1 and 12.2.2 file systems.

Key Procedures and Functions

The package exposes a single documented procedure:

  • DELETE_LINE_COVER — The public entry point. It accepts a large set of IN parameters that mirror the columns of a Receivables transaction line, assembles them into an in-memory line record, and performs the deletion of the related distribution row. The argument list includes transactional identifiers such as p_customer_trx_line_id, p_customer_trx_id, p_line_number, and p_memo_line_id; financial attributes such as p_trx_amount, p_exchange_rate, p_revenue_amount, p_extended_amount, and p_unit_selling_price; quantity fields (p_quantity_credited, p_quantity_invoiced, p_quantity_ordered); accounting rule attributes (p_accounting_rule_id, p_rule_start_date, p_accounting_rule_duration, p_autorule_complete_flag); tax attributes (p_vat_tax_id, p_sales_tax_id, p_tax_rate, p_taxable_flag, p_tax_exempt_flag, p_tax_exemption_id, p_tax_precedence, p_autotax); and sales order references (p_sales_order, p_sales_order_line, p_sales_order_source, p_sales_order_revision). Control flags p_complete_flag and p_recalculate_tax_flag govern whether the deletion is treated as final and whether tax must be recalculated after the line is removed. The procedure also references arp_util.debug for diagnostic tracing. No other procedures or functions are documented for this package body.

Tables Accessed

ETRM documents the following base tables, reached through APPS synonyms, as being referenced by this package:

  • RA_CUSTOMER_TRX_LINES — The transaction line table that is the primary subject of the deletion. The procedure's parameter set corresponds directly to its columns.
  • RA_CUST_TRX_LINE_GL_DIST — The distribution (accounting) table from which the "dist line" referenced in the package description is deleted.
  • RA_CUSTOMER_TRX — The transaction header, consulted to maintain header-level consistency when a line and its distribution are removed.
  • AR_SYSTEM_PARAMETERS — Read for Receivables system-level setup and defaulting behaviour that affects how the deletion is processed.
  • FND_CURRENCIES — Consulted for currency validation and exchange-rate handling associated with the monetary parameters.

Usage Notes

ARP_DELETE_LINE_COVER is not intended for direct invocation by end users. Because ETRM records zero packages referencing it, the caller relationship is not exposed through the documented API graph; in practice it is invoked from within the Receivables transaction maintenance code path, typically when a user deletes or credits a transaction line from the Transactions form and the underlying line and distribution must be removed together. Customizations that need identical behaviour should call the supported Receivables APIs (such as ARP_PROCESS_LINE or the AutoInvoice interfaces) rather than this internal utility, since its parameter contract is long, positional, and subject to change without an externalized API commitment. Any custom code that does invoke it must supply the complete argument set, including the tax, accounting-rule, and sales order columns, and must honour the p_complete_flag and p_recalculate_tax_flag semantics so that downstream tax and revenue recognition remains consistent. As with all APPS-owned package bodies, modifications in a supported environment should be avoided; extensions belong in a custom schema that references the object only where Oracle's documented interfaces permit.