Search Results arxtw_format_address

Overview

ARP_ADDR_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified in the ETRM metadata as an "OTHER" API type. It is a foundational utility for the Oracle Receivables (AR) module, handling address-related processing logic for customer sites and locations. In releases 12.1.1 and 12.2.2, the package operates within the broader architecture of Oracle Trading Community Architecture (TCA) and Receivables, where customer addresses are stored in the HZ (Trading Community) model but must be consumed by Receivables-specific processing such as transactions, invoices, and EDI interfaces. ARP_ADDR_PKG provides the reusable address parsing, formatting, validation, and row-management routines that other Receivables packages and forms depend upon.

Key Procedures and Functions

The documented 11 procedures and functions fall into four functional groupings:

• Address formatting: FORMAT_ADDRESS, ARXTW_FORMAT_ADDRESS, and FORMAT_LAST_ADDRESS_LINE produce a display-ready, concatenated address string from site components. These are essential for printed invoices and reports that must present a properly ordered, jurisdiction-aware address rather than raw column values.
• Uniqueness validation: CHECK_UNIQUE_ORIG_SYSTEM_REF, CHECK_UNIQUE_EDI_LOCATION, and LOCATION_EXISTS verify that an originating system reference, an EDI location identifier, or a physical location does not already exist, preventing duplicate customer site records.
• Row management: INSERT_ROW, UPDATE_ROW, and LOCK_ROW provide the standard insert-update-lock triad used at the site-use level. LOCK_ROW obtains a concurrency lock so that conflicting updates to a customer address are serialized, while INSERT_ROW and UPDATE_ROW persist validated changes.
• Site flag and reference checks: UPDATE_SITE_USE_FLAG maintains the active/inactive state of a site use, and TRANSACTION_EXISTS determines whether referenced transaction activity exists, which governs whether a site may be modified or deleted.

Tables Accessed

The ETRM dependency listing identifies HZ_CUST_ACCT_SITES as the primary table accessed through APPS synonyms. This table stores the customer account site-level records that link a customer account to a physical location. All row insertion, updating, and locking operations described above operate against this entity. The package body also references FND_MESSAGE for retrieval of translatable error and warning messages, and APP_EXCEPTION for standard error-raising and exception-handling behavior. STANDARD is referenced for Oracle-supplied standard PL/SQL routines. No other database objects are documented as referenced by ARP_ADDR_PKG itself.

Usage Notes

ARP_ADDR_PKG is not documented as being referenced by any other database object, indicating it sits near the top of the dependency chain as a callable utility rather than a shared internal dependency. However, the package is referenced by 19 other packages, so it is widely invoked by higher-level Receivables components that require address validation and persistence. Typical invocation pathways include the Receivables customer and transaction entry forms, concurrent programs that import or validate customer site data, and EDI processing routines. Custom code should call these documented entry points rather than writing directly to HZ_CUST_ACCT_SITES, because the package enforces locking, uniqueness, and site-use flag consistency that direct DML would bypass. Developers extending Receivables functionality should treat ARP_ADDR_PKG as the supported interface for site-level address manipulation.