Search Results update_line_cover




Overview
Explore in AI Chat

Overview

ARP_UPDATE_LINE_COVER is an Oracle Receivables (AR) PL/SQL package body owned by APPS that provides the public procedure UPDATE_LINE_COVER within the E-Business Suite R12 (12.1.1 / 12.2.2) environment. The package's core purpose is to take a collection of scalar column parameters supplied by a caller and convert them into a customer transaction line record, then persist updates to the corresponding RA_CUSTOMER_TRX_LINES row. In other words, it abstracts the mechanics of line maintenance on an Oracle Receivables transaction — invoice, debit memo, credit memo, chargeback, or deposit — behind a single programmatic entry point, so that forms-level or batch logic does not need to construct line-level DML statements directly.

The header comment (ARTCTLUB.pls 120.7, dated 2005) identifies the procedure as PUBLIC and lists arp_util.debug as the only external programmatic dependency. The argument list is extensive, spanning tax, AutoAccounting, sales order, memo line, inventory, UOM, and exchange rate attributes — which is consistent with the package's broad "cover" role of supporting line-level updates across the diverse set of Receivables line types.

Key Procedures and Functions

  • UPDATE_LINE_COVER — The single documented procedure in the package. Per the ETRM metadata and header comment, its description is "Converts column parameters to a line record and updates a line." It accepts the caller's column-level values (form name, form version, transaction line ID, foreign currency code, exchange rate, recalculate-tax flag, rerun-AutoAccounting flag, transaction ID, line number and type, quantity credited/invoiced/ordered, unit selling and standard price, extended amount, memo line ID, inventory item ID, exception rate ID, description, item context, link attributes, Accounting Rule ID, AutoRule completion and duration values, reason code, last period to credit, sales order details, VAT/sales tax IDs, tax exemption details, tax rate, UOM code, autotax, movement ID, default USSGL codes, and interface line context/attribute columns) and writes the resulting line back to the database. It is classified as OTHER in the ETRM API classification scheme, which means it is an internal supporting utility rather than a formally published open interface or public API.

Tables Accessed

The package reads from and writes to the following tables via APPS synonyms:

  • RA_CUSTOMER_TRX_LINES — the primary target. The procedure's line record is applied against the row identified by p_customer_trx_line_id (or inserted relative to p_customer_trx_id) when the line-type-specific update is executed.
  • RA_CUSTOMER_TRX — the parent transaction header, consulted for transaction context (currency, transaction class, and related control attributes) that govern line behaviour.
  • RA_CUST_TRX_LINE_GL_DIST — the line-level GL distribution table. Because the procedure accepts USSGL default codes, accounting rule ID, and AutoAccounting flags, distribution rows are adjusted to keep the line's accounting consistent with the changed attributes.
  • AR_SYSTEM_PARAMETERS — supplied to drive system-level defaults such as accounting and tax behaviour.
  • FND_CURRENCIES — used where the foreign currency code parameter must be validated or translated against the defined currency set.

Usage Notes

UPDATE_LINE_COVER is a form-layer utility: it exists to serve Oracle Receivables transaction workbenches and related forms that allow users to amend line attributes and then commit them through PL/SQL rather than through direct DML. Because the procedure takes a form name and form version parameter, it is designed to be called from form triggers with a consistent, version-aware contract.

The ETRM metadata records no referencing packages, which indicates that the procedure is not a general-purpose integration API and should not be invoked from external interfaces. Customisations that need to alter Receivables lines programmatically should consider the supported open interfaces (for example, AR_INVOICE_API_PUB or the AutoInvoice interface tables) instead. For diagnostics, the sole instrumented dependency is arp_util.debug, so callers should set the standard Receivables debug profile option if trace output is required. As with all form-driven utilities, changes must respect the concurrent-program and _WHO column conventions maintained by the enclosing form transaction.