Search Results insert_line_cover




Overview
Explore in AI Chat

Overview

ARP_INSERT_LINE_COVER is a public PL/SQL package body owned by APPS that supports the Oracle Receivables transaction line creation infrastructure. Its single documented procedure, INSERT_LINE_COVER, is a utility routine that converts a large set of scalar column parameters into a properly structured line record and inserts that record into the appropriate Receivables transaction line table. The package header carries the version string $Header: ARTCTLIB.pls 120.6 2005/10/07 17:44:30 ralat ship $, indicating that this code has been part of the Receivables transaction library since early releases and remains shipped in Oracle EBS 12.1.1 and 12.2.2.

The business purpose of the package is to centralise the mechanics of line insertion for callers that already hold line attribute values as discrete parameters. Rather than forcing every caller to construct and populate a RA_CUSTOMER_TRX_LINES%ROWTYPE manually, INSERT_LINE_COVER accepts the individual columns and performs the record assembly and DML, allowing shared validation, defaulting, and debug tracing to occur in one place. The only external procedure documented as being accessed is arp_util.debug, which confirms the procedure participates in the standard Receivables debug tracing convention.

Key Procedures and Functions

  • INSERT_LINE_COVER — The sole documented procedure in the package. Per the ETRM description, it "converts column parameters to a line record and inserts a line." It is scoped as PUBLIC, making it callable from other APPS packages and custom code. The parameter interface is extensive and grouped logically: form context parameters (p_form_name, p_form_version), line identity and classification (p_memo_line_type, p_trx_class, p_line_number, p_line_type), accounting flexfield references (p_ccid1, p_ccid2), amount and quantity columns (p_amount, p_amount2, p_quantity_credited, p_quantity_invoiced, p_quantity_ordered, p_unit_selling_price, p_unit_standard_price, p_revenue_amount, p_extended_amount), parent/child linkage keys (p_customer_trx_id, p_memo_line_id, p_initial_customer_trx_line_id, p_link_to_cust_trx_line_id, p_previous_customer_trx_id, p_prev_customer_trx_line_id), item and inventory references, revenue recognition attributes (p_accounting_rule_id, p_autorule_complete_flag, p_autorule_duration_processed), sales order references, tax attributes, unit of measure, and interface line context/attribute columns.

Tables Accessed

  • RA_CUSTOMER_TRX_LINES — The principal target of the line insertion performed by INSERT_LINE_COVER.
  • AR_MEMO_LINES — Supports credit memo and memo line handling associated with the memo line type parameter.
  • RA_CUSTOMER_TRX — Parent transaction header, read for transaction context and linkage validation.
  • RA_CUST_TRX_LINE_GL_DIST — Distribution rows associated with the transaction line.
  • RA_CUST_TRX_TYPES — Transaction type definition, consulted for class and defaulting information.
  • AR_SYSTEM_PARAMETERS — System-level Receivables settings used for defaulting and validation.
  • GL_CODE_COMBINATIONS — Resolves the accounting flexfield code combination identifiers supplied as p_ccid1 and p_ccid2.
  • FND_CURRENCIES — Currency validation for the transaction amounts.

Usage Notes

INSERT_LINE_COVER is an internal Receivables library routine rather than an end-user facing API. The ETRM metadata records zero packages referencing it, which indicates it is not part of a documented public API surface consumed by other shipped packages, but it remains callable from Oracle Forms transaction entry logic, concurrent programs, and custom extensions that need to create transaction lines programmatically. Typical invocation occurs during manual or imported transaction entry, credit memo creation, and adjustments where line attributes are already available as individual columns. Because the procedure performs a direct insert rather than full validation and derivation, callers are expected to supply complete and consistent values, including the customer transaction identifier, line number, and accounting references. The inclusion of arp_util.debug means callers can enable Receivables debug logging to trace parameter and SQL activity when troubleshooting line creation. Custom code invoking this procedure should treat the parameter list as version-sensitive across patch levels and should avoid hard-coding assumptions about the package body, since Oracle may revise the implementation while preserving the documented behaviour of converting parameters to a line record and inserting the line.