Results for “ap_exp_locations”

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

Overview

AP_EXP_LOCATIONS is the Payables (AP) schema table that stores physical address information used throughout Oracle E-Business Suite Release 12.1.1 and 12.2.2. In the ETRM metadata the object is described simply as "Physical Address," and it functions as the address master for expense and credit-card related location data consumed by the Payables module. Each row represents a distinct mailing or physical location, keyed by a system-generated identifier and cross-referenced by an alternate address key.

The table is owned by the AP schema and is documented as VALID with 18 columns in the 12.2.2 physical schema. Its primary key constraint, AP_EXP_LOCATIONS_PK, is defined on the LOCATION_ID column, and two unique indexes are documented: AP_EXP_LOCATIONS_U1 on LOCATION_ID and AP_EXP_LOCATIONS_U2 on ADDRESS_KEY. From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as hub-leaning: it holds a stable, uniquely identified business entity (the address/location) with relatively few inbound dependencies, which is characteristic of a hub rather than a transaction link or a descriptive satellite.

Key Information Stored

Among the 18 documented columns, the most operationally significant are listed below.

• LOCATION_ID — The surrogate primary key (AP_EXP_LOCATIONS_PK, AP_EXP_LOCATIONS_U1). This is the internal identifier that child tables use to reference a location.
• ADDRESS_KEY — The alternate unique business key (AP_EXP_LOCATIONS_U2), providing a second, deterministic way to identify an address row.
• ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4 — The structured address line fields that hold the formatted mailing address.
• CITY — The city or locality component of the address.
• PROVINCE_STATE — The state, province, or regional designation.
• POSTAL_CODE — The postal or ZIP code element used for mailing and validation.
• COUNTRY — The country value qualifying the address, important for global Payables operations.
• ORG_ID — The operating unit (multi-org) discriminator that scopes the location to a specific organization.
• GEOMETRY_STATUS_CODE and GEOMETRY — Spatial attributes used for geocoding and geographic processing of the address; these columns are associated with the system-managed LOB indexes SYS_IL0000322921C00024$$ and SYS_IL0000322921C00025$$.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS who-columns providing audit and concurrency information.

The distinction between the surrogate key (LOCATION_ID) and the business-key candidates (ADDRESS_KEY, and LOCATION_ID itself as a uniqueness anchor) is important when writing joins, because downstream tables reference the surrogate value rather than the natural address attributes.

Common Use Cases and Queries

The primary practical dependency on AP_EXP_LOCATIONS is resolving the location referenced by credit-card transactions in Payables. A typical analytical join retrieves the full address for each transaction:

SELECT t.trx_number, l.address1, l.city, l.province_state, l.postal_code, l.country
FROM ap_credit_card_trxns_all t, ap_exp_locations l
WHERE t.location_id = l.location_id;

Reporting use cases include address validation and standardization audits, mailing-list or remittance-address reports by operating unit (filtering on ORG_ID), and geocoding completeness checks driven by GEOMETRY_STATUS_CODE. Because ADDRESS_KEY is uniquely indexed, de-duplication and reconciliation queries can group rows by ADDRESS_KEY to detect inconsistent address components. Multi-org security should always constrain queries by ORG_ID where the operating unit context applies.

Related Objects

The documented foreign-key relationship shows that AP_CREDIT_CARD_TRXNS_ALL references this table through AP_CREDIT_CARD_TRXNS_ALL.LOCATION_ID → AP_EXP_LOCATIONS.LOCATION_ID. This is the principal dependent object, linking expense and credit-card transaction records to their physical addresses. The unique indexes AP_EXP_LOCATIONS_U1 and AP_EXP_LOCATIONS_U2 enforce the integrity of LOCATION_ID and ADDRESS_KEY respectively and are integral to join performance. At the schema level, the AP owner and the ORG_ID column tie the object to the broader Payables and multi-organization model, making it a reference point whenever location context is required for transactional or reporting data in the AP module. Beyond the credit-card transaction table, the location values are generally consumed through the same LOCATION_ID join pattern, so any query surface that exposes a location reference in Payables can be traced back to this hub-like address table.