Search Results postal_code_high

Overview

RA_REMIT_TOS_ALL is an Oracle Receivables (AR) table that links remit-to addresses to the state, country, and postal code ranges in which they apply. In Oracle EBS 12.1.1 and 12.2.2 it functions as the configuration bridge between a customer's remit-to address and the geographic jurisdiction for which that address is valid. Receivables uses this mapping during receipt application, automatic receipt creation, and remittance banking so that the correct remit-to address is selected based on the customer's location, state, and postal code.

Under the Multi-Org architecture, the table carries an ORG_ID column and is partitioned by operating unit through the standard _ALL convention. The heuristic Data Vault classification for this object, mined from its foreign key structure, is link. This is consistent with its role: it does not store the descriptive attributes of an address itself, but rather resolves the relationship between an existing address record and a geographic scope. As a modeling suggestion, the link classification implies that the durable business identifier for this association is the combination of state, country, and postal code range rather than the row's surrogate key.

Key Information Stored

The table contains 28 documented columns. The most significant are the address and geographic scope attributes:

• ADDRESS_ID — Foreign key to HZ_CUST_ACCT_SITES_ALL, identifying the remit-to address that participates in the mapping.
• COUNTRY — The country to which the remit-to mapping applies.
• STATE — The state or province within the country.
• POSTAL_CODE_LOW and POSTAL_CODE_HIGH — The inclusive postal code range for which the mapping is valid.
• STATUS — Active or inactive indicator for the mapping.
• ORG_ID — The operating unit that owns the row in the Multi-Org model.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns available for client-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

The documented primary key is RA_REMIT_TOS_PK, defined on STATE, COUNTRY, POSTAL_CODE_LOW, and POSTAL_CODE_HIGH. These four columns, together with ORG_ID, form the unique index RA_REMIT_TOS_U1, which represents the business-key candidate. Distinguishing between the two is important: the unique index is the logical identifier used in multi-org contexts, whereas the primary key is the narrower database constraint. The ADDRESS_ID column is not part of either key, meaning a single address may be associated with multiple geographic scopes and, conversely, a given geographic scope may resolve to one address per operating unit.

Common Use Cases and Queries

The primary use case is remit-to address resolution. When a receipt or remittance instruction needs an address for a customer located in a specific state and postal code, the application queries RA_REMIT_TOS_ALL to find the matching remit-to address. A typical lookup pattern is:

• Query by ORG_ID, COUNTRY, STATE, and a postal code falling between POSTAL_CODE_LOW and POSTAL_CODE_HIGH.
• Filter on STATUS = 'A' to restrict results to active mappings.
• Join ADDRESS_ID to HZ_CUST_ACCT_SITES_ALL to retrieve the formatted address and site details.

Common reporting scenarios include reconciling configured remit-to mappings by operating unit, identifying addresses mapped to overlapping postal code ranges, and auditing mappings that are inactive but still referenced by active receipt activity. Because the table carries a DFF, attribute columns are frequently queried in client-specific reports that use ATTRIBUTE_CATEGORY to segment mappings by configuration purpose.

Related Objects

RA_REMIT_TOS_ALL sits at the junction of remit-to address configuration and customer site data. The most significant related objects are:

• HZ_CUST_ACCT_SITES_ALL — Referenced through RA_REMIT_TOS_ALL.ADDRESS_ID; supplies the customer account site and formatted address details.
• HZ_CUST_SITE_USES_ALL — Commonly joined to determine site use and remit-to usage flags for the referenced address.
• RA_CUSTOMER_TRX_ALL and AR_CASH_RECEIPTS_ALL — Transaction and receipt objects that drive remit-to selection during receipt application.
• RA_BATCH_SOURCES_ALL and AR_BANK_ACCT_USES_ALL — Configuration objects used alongside remit-to data in remittance banking setup.
• RA_REMIT_TOS_ALL itself is validated against the receipts and remittance processing logic in the AR module, so any purge or archiving activity should account for active references from receipt processes.

Because the table is a link rather than a hub, maintenance operations should treat the ORG_ID plus geographic scope combination as the stable identifier, and avoid deleting rows that are still required for remit-to resolution by active operating units.