Results for “loc_last_update_date”
26 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AR_REMIT_TO_ADDRESSES_V is a Receivables (AR) view owned by the APPS schema that presents the "remit to" addresses associated with customer accounts. Remit-to addresses are the sites to which customer payments and related receivables correspondence are directed, and they are frequently distinct from a customer's primary billing or shipping locations. The view denormalizes the customer account site, party site, and location data into a single, report-friendly projection that exposes both the individual address components and a pre-formatted, concatenated address string. This makes it directly consumable by Oracle Reports, BI Publisher, OAF pages, and outbound EDI or interface programs that need to print or transmit a mailing address.
The ETRM documentation records this object as a VIEW in the APPS schema with VALID status, carrying the description "(Release 11.5 Only)." In the Oracle E-Business Suite 12.1.1 and 12.2.2 architectures, the underlying data model was migrated from the legacy AR customer tables to the Oracle Trading Community Architecture (TCA) model, in which customers and their addresses are represented through HZ_ tables. Consequently, the 11.5-only designation reflects the fact that this specific view belonged to the pre-TCA regime; equivalent 12.x functionality is provided through TCA-based views and the HZ_CUST_ACCT_SITES / HZ_PARTY_SITES hierarchy. The column layout nonetheless remains instructive for understanding how remit-to address data is assembled and formatted in EBS.
Underlying Base Objects
The documented base objects for the view are:
- ARH_ADDR_PKG (PACKAGE) — the Receivables address formatting package. The view invokes
ARH_ADDR_PKG.FORMAT_ADDRESS(...)to render theCONCATENATED_ADDRESScolumn from the discrete location attributes, applying the territory's address style. - HZ_CUST_ACCT_SITES (SYNONYM) — the TCA customer account site entity. It supplies the account-site identifier and links the customer account to a party site.
- HZ_PARTY_SITES (SYNONYM) — the TCA party site entity that associates a party with a physical location.
- HZ_LOCATIONS (SYNONYM) — the TCA location entity holding the actual address elements: address lines, city, county, state, province, postal code, and country.
- FND_TERRITORIES_VL (VIEW) — the multilingual territory view providing the territory short name and address style used to drive formatting and to resolve the country.
The view therefore joins the account site to its party site and location, and derives formatted and descriptive attributes from the territory and address-formatting package. This places it firmly on the TCA side of the 12.x data model, consistent with the documented base-object list.
Key Columns
- ROW_ID — the ROWID of the underlying account-site record, useful for identifying the source row.
- ADDRESS_ID — the customer account site identifier (CUST_ACCT_SITE_ID), the primary key of the address site.
- CUSTOMER_ID — the customer account identifier to which the remit-to address belongs.
- STATUS and ORIG_SYSTEM_REFERENCE — the site's status and its originating system reference, supporting validation and reconciliation.
- COUNTRY, TERRITORY_SHORT_NAME, ADDRESS_STYLE — territory attributes that describe and format the address.
- ADDRESS1–ADDRESS4, CITY, COUNTY, STATE, PROVINCE, POSTAL_CODE — the discrete address components.
- CONCATENATED_ADDRESS — the fully formatted address produced by ARH_ADDR_PKG.FORMAT_ADDRESS, ready for printing or transmission.
- EDI_LOCATION (ECE_TP_LOCATION_CODE) — the location code used in EDI trading-partner processing.
- ATTRIBUTE1–ATTRIBUTE15, GLOBAL_ATTRIBUTE_CATEGORY, GLOBAL_ATTRIBUTE1–7 — descriptive flexfield and global descriptive flexfield columns available for customer-specific extensions.
Common Use Cases and Queries
Typical uses include remittance-advice and statement printing, dunning and collections correspondence, and outbound EDI/interface extracts that must supply a correct remit-to mailing address per customer. The pre-formatted CONCATENATED_ADDRESS column simplifies report layout, while the discrete columns support sorting, country-specific formatting, and validation.
The following query returns remit-to addresses for a given customer:
SELECT address_id, customer_id, territory_short_name, concatenated_address, statusFROM apps.ar_remit_to_addresses_vWHERE customer_id = :p_customer_idAND status = 'A';
Because the object is documented as 11.5-only, on 12.1.1 and 12.2.2 environments the address data should be sourced from the TCA entities directly — joining HZ_CUST_ACCT_SITES, HZ_PARTY_SITES, and HZ_LOCATIONS, and formatting with ARH_ADDR_PKG.FORMAT_ADDRESS — rather than relying on this view. Where a legacy 11.5 view is referenced in custom code, confirming the target release and substituting the TCA equivalent is recommended.
-
(Release 11.5 Only)
APPS.AR_REMIT_TO_ADDRESSES_V·↳ ARH_ADDR_PKG·↳ FND_TERRITORIES_VL·↳ HZ_CUST_ACCT_SITES·Explore AR module →
-
(Release 11.5 Only)
APPS.AR_REMIT_TO_ADDRESSES_V·↳ ARH_ADDR_PKG·↳ FND_TERRITORIES_VL·↳ HZ_CUST_ACCT_SITES·Explore AR module →
-
View: AR_ADDRESSES_V 12.1.1
This view is used in the customer form address block
APPS.AR_ADDRESSES_V·↳ ARP_ADDR_PKG·↳ AR_LOOKUPS·↳ FND_LANGUAGES_VL·Explore AR module →
-
View: AR_ADDRESSES_V 12.2.2
This view is used in the customer form address block
APPS.AR_ADDRESSES_V·↳ ARP_ADDR_PKG·↳ AR_LOOKUPS·↳ FND_LANGUAGES_VL·Explore AR module →
-
View: RA_ADDRESSES 12.2.2
Not implemented in this database·Explore AR module →
-
View: RA_ADDRESSES 12.1.1
Not implemented in this database·Explore AR module →
-
View: ASF_ADDRESSES_V 12.2.2
Not implemented in this database·Explore ASF module →
-
View: ASF_ADDRESSES_V 12.1.1
Not implemented in this database·Explore ASF module →
-
VIEW: APPS.AR_ADDRESSES_V 12.2.2
-
VIEW: APPS.AR_ADDRESSES_V 12.1.1
-
View: RA_ADDRESSES_MORG 12.1.1
Customer address information
Not implemented in this database·Explore AR module →
-
View: RA_ADDRESSES_MORG 12.2.2
Customer address information
Not implemented in this database·Explore AR module →
-
eTRM - AR Tables and Views 12.1.1
Territory information
-
eTRM - AR Tables and Views 12.2.2
Territory information