Search Results mtl_ci_xrefs_interface

Overview

The RA_ADDRESSES_ALL table is a core data structure within Oracle E-Business Suite (EBS) Receivables (AR) module, versions 12.1.1 and 12.2.2. It serves as the central repository for storing detailed address information associated with customer sites. Its primary role is to maintain the physical and mailing locations for customers, enabling critical business functions such as invoicing, shipping, and customer relationship management. The table's "ALL" suffix indicates it is a multi-organization enabled table, storing data partitioned by the ORG_ID column to support multiple operating units within a single installation. As evidenced by its extensive foreign key relationships, RA_ADDRESSES_ALL is a fundamental entity integrated with numerous modules beyond Receivables, including Advanced Collections, Order Management, Projects, and Inventory.

Key Information Stored

The table's primary key is the ADDRESS_ID, a unique system-generated identifier for each address record. Key columns establish relationships and define the address attributes. The CUSTOMER_ID column links the address to a specific customer in the RA_CUSTOMERS table. The TERRITORY_ID associates the address with a sales territory from RA_TERRITORIES, while the LOCATION_ID links to a tax location in AR_LOCATION_COMBINATIONS for tax calculation purposes. Standard address components such as ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4, CITY, STATE, POSTAL_CODE, and COUNTRY are stored. Critical functional columns include SITE_USE_CODE, which defines the address purpose (e.g., 'BILL_TO', 'SHIP_TO'), and STATUS to indicate if the address is active ('A') or inactive ('I'). The ORG_ID column is essential for multi-org data segregation.

Common Use Cases and Queries

A primary use case is retrieving all active bill-to addresses for a specific customer to generate invoices or statements. Another common scenario involves identifying ship-to addresses for order fulfillment processes. Data from this table is also crucial for tax reporting, customer communications, and territory-based sales analysis. Sample SQL patterns include joining to the RA_CUSTOMERS table to get customer details and filtering by SITE_USE_CODE and STATUS.

• Fetch active bill-to addresses for a customer: SELECT * FROM RA_ADDRESSES_ALL WHERE CUSTOMER_ID = :cust_id AND SITE_USE_CODE = 'BILL_TO' AND STATUS = 'A' AND ORG_ID = :org_id;
• List all addresses with customer name: SELECT c.CUSTOMER_NAME, a.ADDRESS1, a.CITY, a.STATE, a.POSTAL_CODE FROM RA_ADDRESSES_ALL a, RA_CUSTOMERS c WHERE a.CUSTOMER_ID = c.CUSTOMER_ID AND a.ORG_ID = :org_id;

Related Objects

As per the provided metadata, RA_ADDRESSES_ALL has extensive integration across the EBS suite. Its primary foreign key relationships are with RA_CUSTOMERS, RA_TERRITORIES, and AR_LOCATION_COMBINATIONS. It is referenced as a parent table by numerous objects in other modules, highlighting its central role. Key referencing tables include:

• AS_LEADS_ALL, AS_SALESFORCE (CRM): For storing prospect and sales team address data.
• MTL_CUSTOMER_ITEMS, MTL_INTERCOMPANY_PARAMETERS (Inventory): For defining customer-specific item and inter-company relationships.
• PA_DRAFT_INVOICES_ALL, PA_PROJECT_CUSTOMERS (Projects): For storing project-specific bill-to and ship-to addresses.
• AS_ACCESSES_ALL_ALL, AS_TERRITORY_VALUES_ALL (Advanced Collections): For managing customer contact points and territory assignments.

This wide array of dependencies underscores that RA_ADDRESSES_ALL is a critical shared entity within the Oracle EBS customer data model.