Search Results transaction_exists




Overview

The APPS.ARP_ADDR_PKG package is a Receivables (AR) utility package within Oracle E-Business Suite that centralizes address handling and validation logic for customer addresses, site uses, and related account-site records. Its header date and naming conventions (AROADDRS.pls) identify it as an older, long-standing AR module object that has been carried forward through the 12.1.1 and 12.2.2 releases. The package belongs to the APPLSYS/APPS schema, is compiled AUTHID CURRENT_USER, and is classified under the ETRM documentation scheme as "OTHER" rather than a public/private API. Its principal responsibilities include formatting postal addresses according to an address style, checking the uniqueness of originating-system references and EDI location references, maintaining site-use flags, and performing low-level DML against customer address rows. Because it is referenced by approximately 19 other packages, it functions as a shared internal library rather than as an entry point intended for direct customer invocation.

Key Procedures and Functions

  • FORMAT_ADDRESS — Returns a formatted address string for a given address style, accepting the individual address elements (address lines, city, county, state, province, postal code, territory, country code) plus optional attributes such as customer name and contact names, default country information, and printing flags for home country and default attention. Width and minimum/maximum height parameters control the layout output.
  • ARXTW_FORMAT_ADDRESS — A variant formatter that returns a formatted address string from the core address elements, used where a lighter signature than FORMAT_ADDRESS is required.
  • FORMAT_LAST_ADDRESS_LINE — Returns the final line of a formatted address, composed from the address style together with the city, county, state, province, country, and postal code values.
  • CHECK_UNIQUE_ORIG_SYSTEM_REF — Validates that an originating-system reference is unique, typically raising an error when a duplicate reference is found.
  • UPDATE_SITE_USE_FLAG — Updates the site-use flag for a given address and site-use code, controlling whether a particular site use is active for that address.
  • INSERT_ROW — Inserts a new customer address row, returning the row identifier and the address identifier along with audit columns.
  • LOCK_ROW — Locks the target address row for update, supporting concurrency control during modification.
  • UPDATE_ROW — Updates an existing customer address row with new column values.
  • LOCATION_EXISTS — Determines whether a location already exists, used as a guard before inserting new address data.
  • TRANSACTION_EXISTS — Determines whether transactions exist for the address in question. This function is the object matching the user's search term. It is used to prevent disruptive changes to addresses that are already referenced by transaction data.
  • CHECK_UNIQUE_EDI_LOCATION — Validates the uniqueness of an EDI location reference, ensuring that EDI-related identifiers are not duplicated across locations.

Tables Accessed

The documented table reference for this package is HZ_CUST_ACCT_SITES, accessed through an APPS synonym. The package reads and writes this customer account site table to support address validation, site-use flag maintenance, and row-level inserts, updates, and locks. The existence checks (LOCATION_EXISTS, TRANSACTION_EXISTS, CHECK_UNIQUE_ORIG_SYSTEM_REF, and CHECK_UNIQUE_EDI_LOCATION) rely on related Receivables and Trading Community data to determine whether an address or location is already in use or already referenced, which is why such checks are coupled with the account-site records maintained through this table.

Usage Notes

ARP_ADDR_PKG is typically invoked indirectly. Oracle Receivables forms and concurrent programs that create or maintain customer addresses and site uses call the package for formatting, validation, and DML. Because it is referenced by 19 other packages, custom code should prefer supported Receivables or Trading Community public APIs for address creation and instead regard ARP_ADDR_PKG as an internal implementation dependency. When called, the invoking session must have appropriate privileges on the underlying APPS synonyms, consistent with the AUTHID CURRENT_USER compilation. The TRANSACTION_EXISTS and LOCATION_EXISTS functions are useful for pre-change validation, allowing callers to detect whether an address is already referenced before attempting modification or deletion.