Results for “identifying_address_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.ARH_ADDR_PKG package is a shared address-handling utility within the Oracle E-Business Suite Receivables (AR) module. Its principal business function is to provide reusable PL/SQL logic for formatting, validating, and maintaining customer address data stored in the Oracle Trading Community Architecture (TCA) and Oracle Receivables schema. The package name prefix "ARH" reflects its historical role as the Receivables "Address" helper library, and it sits beneath a broad layer of Receivables views and concurrent logic that depend on consistent address representation.

In Release 12.1.1 and 12.2.2, customer address information is modeled across TCA entities such as HZ_LOCATIONS, HZ_PARTY_SITES, HZ_CUST_ACCT_SITES_ALL, and HZ_CUST_SITE_USES_ALL. ARH_ADDR_PKG bridges the gap between those normalized tables and the flattened, display-oriented address strings required by invoices, billing views, and reporting. The package holds a VALID status in the APPS schema and is documented in ETRM as an OTHER-classification API rather than a formal public API, meaning it is intended primarily for internal Receivables and dependent-module consumption.

Key Procedures and Functions

ETRM documents twenty procedures and functions within the package. The formatting routines — FORMAT_ADDRESS, ARXTW_FORMAT_ADDRESS, and FORMAT_LAST_ADDRESS_LINE — assemble address lines into a printable or storable form, with FORMAT_LAST_ADDRESS_LINE handling the terminal line (typically city, state, postal code) separately. THE_AR_MISS_CHAR and THE_AR_NULL_CHAR are utility constants/functions used to represent missing or null address elements consistently.

The validation and lookup routines include LOCATION_EXISTS, which determines whether a given location already exists; CHECK_UNIQUE_ORIG_SYSTEM_REF and CHECK_UNIQUE_EDI_LOCATION, which enforce uniqueness for original-system references and EDI trading-partner locations; and CHECK_ADDR_MODIF_ALLOWED, which governs whether an address may still be modified. Transaction-related checks include TRANSACTION_EXISTS, TRANSACTION_MORG_EXISTS, CHECK_TRAN_FOR_ALL_ACCTS, and CHECK_PRINTED_TRX, which collectively prevent address changes once dependent transactions, operating-unit assignments, or printed invoices exist.

The maintenance procedures INSERT_ROW, UPDATE_ROW, DELETE_CUSTOMER_ALT_NAMES, UPDATE_SITE_USE_FLAG, and IDENTIFYING_ADDRESS_FLAG perform the actual data manipulation on address and site-use records. GET_LOCATION_DATA and COMPARE_LOCATION_EXISTING retrieve and compare address records, supporting both display and duplicate detection.

Tables Accessed

The package reads and writes a range of Receivables and TCA tables through APPS synonyms. Address storage is handled via HZ_LOCATIONS, HZ_LOC_ASSIGNMENTS, HZ_PARTY_SITES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and the corresponding base views HZ_CUST_ACCT_SITES and HZ_CUST_SITE_USES. Location history is supported through HR_LOCATIONS_S. Transaction safeguards depend on RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_TYPES, and the RA_CUSTOMER_TRX view. System-level configuration is read from AR_SYSTEM_PARAMETERS and AR_SYSTEM_PARAMETERS_ALL, supplying default country and formatting behavior.

Usage Notes

ARH_ADDR_PKG is referenced by twenty-three other packages and views, including AR_CSU_PKG, HZ_ADDR_ISPEED_PKG, HZ_GNR_UTIL_PKG, CSP_SHIP_TO_ADDRESS_PVT, and the Receivables reporting views AR_BILL_TO_ADDRESSES_ACTIVE_V, AR_SHIP_TO_ADDRESSES_ACTIVE_V, and AR_REMIT_TO_ADDRESSES_V. In practice it is invoked indirectly through the Receivables customer and transaction forms, through concurrent programs that print invoices, and through TCA address-validation flows. Custom code should treat it as an internal dependency: direct calls are possible but must not assume stable signatures across patches, and all address changes should respect the transaction and printed-invoice checks the package enforces.