Search Results arp_trx_defaults




Overview

ARP_TRX_DEFAULTS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Receivables. Its role is to centralize the derivation of default values used when a receivable transaction (invoice, credit memo, debit memo, chargeback, or deposit) is created, either interactively through the Receivables transaction forms or programmatically through the AutoInvoice and public API layers. Rather than forcing every caller to re-implement the same lookup logic against customer, site, batch source, transaction type, and system parameter tables, the package exposes a single, consistent entry point for assembling the header-level defaults that populate a new RA_CUSTOMER_TRX record. In the ETRM 12.2.2 metadata the package is classified as an OTHER API, is currently VALID, and consists of a specification and body with one documented callable: GET_HEADER_DEFAULTS. It is referenced by one other package (AR_DEPOSIT_API_PUB) and is largely self-referenced, indicating it functions primarily as an internal utility consumed by the Receivables distribution.

Key Procedures and Functions

  • GET_HEADER_DEFAULTS — The single documented procedure in the package. Its purpose is to return the set of default values applicable to the header of a customer transaction. Conceptually it consolidates the standard Receivables defaulting hierarchy: transaction type, batch source, agreement, customer and customer site, currency, payment terms, and rule set, so that a caller receives a coherent header default structure rather than performing multiple independent queries. No parameter list is documented in the ETRM metadata, so specific input and output arguments are not enumerated here; callers should reference the package specification in the target instance to confirm the exact signature before invoking it directly.

Tables Accessed

The package reads from the core Receivables and Trading Community tables that supply defaulting data:

  • RA_CUST_TRX_TYPES — transaction type definitions, used to derive header attributes such as creation sign and accounting rules.
  • RA_BATCH_SOURCES — batch source attributes that govern numbering, defaulting, and AutoInvoice behavior.
  • RA_TERMS — payment terms defaults for the transaction header.
  • RA_RULES — revenue recognition rule sets associated with the transaction.
  • RA_CUSTOMER_TRX and RA_CUST_TRX_LINE_GL_DIST — the transaction and distribution tables consulted for existing header context and distribution defaults.
  • HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES — customer account and site-use records that drive bill-to, ship-to, and site-level defaults.
  • AR_SYSTEM_PARAMETERS — system-level settings that influence default values.
  • FND_CURRENCIES and AR_LOOKUPS — currency validation and lookup-based default resolution.

Usage Notes

ARP_TRX_DEFAULTS is not a user-facing program; it is invoked internally when a transaction header is initialized. The standard Receivables Transactions form and the AutoInvoice concurrent program rely on equivalent defaulting logic, and the package is referenced by AR_DEPOSIT_API_PUB, which uses it when creating deposit transactions. Customer and partner integrations that build transactions through the Receivables public APIs (AR_INVOICE_API_PUB and related) may implicitly trigger this defaulting path. Because the package is internal and its signature is subject to change across patch levels, custom code should not call ARP_TRX_DEFAULTS directly as a substitute for the supported public APIs. When troubleshooting unexpected header defaults in 12.1.1 or 12.2.2, DBAs typically query the package specification and body in the APPS schema, since the ETRM entry documents only the object name and its single procedure without a parameter list. All objects should be accessed through the APPS synonyms, as is standard practice in an EBS environment.