Results for “ar_location_combinations_pk”

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

Overview

AR_LOCATION_COMBINATIONS is a Receivables (AR) reference table in Oracle E-Business Suite 12.1.1 and 12.2.2 that defines each distinct tax authority recognized by the application. The table functions as a registry of location combinations that the tax engine uses to determine the jurisdictional source of a transaction, and it is referenced throughout the order-to-cash flow wherever a tax authority must be resolved for a receivable, invoice, or adjustment.

According to the ETRM metadata, the object is documented under the AR – Receivables product with the description "Defines each distinct tax authority" and is classified as "Not implemented in this database." This indicates the table is a seeded or EBS-internal repository rather than a customer-configured transaction table; customer data is normally created and maintained indirectly through Receivables tax setup rather than through direct DML. In a Data Vault 2.0 heuristic model, the FK structure suggests a hub-leaning classification: the table anchors one row per tax authority identity and is referenced by downstream associations, making it a natural business hub candidate rather than a link or satellite. A hub-leaning interpretation is a modeling suggestion only and should be validated against the actual column semantics and grain of the live instance.

Key Information Stored

The documented metadata identifies the following structural elements:

• LOCATION_ID — the single documented column and the primary key of the table. It is the surrogate primary key defined by constraint AR_LOCATION_COMBINATIONS_PK and uniquely identifies each distinct tax authority registration.
• AR_LOCATION_COMBINATIONS_PK — the primary key constraint enforcing uniqueness on LOCATION_ID.

Because the metadata lists only LOCATION_ID as a documented attribute, LOCATION_ID serves simultaneously as the surrogate identifier and as the referenced business key for foreign-key traffic from dependent tables. In practice, tax-authority reference data is seeded by Oracle EBS and the location identifier acts as the join point for party-site and address assignments; readers should inspect the live table definition under SYS or AR schemas in their environment before assuming the presence of additional columns. No unique indexes beyond the primary key are documented in the supplied metadata.

Common Use Cases and Queries

The most common use is resolving a tax authority for a given location or address during tax calculation, invoicing, and reporting. Typical SQL patterns join the referenced dependent tables back to LOCATION_ID.

• Location assignments for a tax authority: join AR_LOCATION_COMBINATIONS to HZ_LOC_ASSIGNMENTS on LOC_ID to enumerate the assignment records pointing at each authority.
• Address resolution: join to RA_ADDRESSES_ALL on LOCATION_ID to retrieve the address row associated with a given tax authority location.
• Reference lookups for reporting: drive AR tax-authority reports by selecting LOCATION_ID from AR_LOCATION_COMBINATIONS and outer-joining the assigned address combinations for display.

Because the table is not implemented in the database, queries should be treated as read-only reference lookups and never as a target for direct inserts or updates. Where custom reporting is required, use the seeded reads and, if new assignments are needed, use the supported Receivables setup forms or APIs rather than running DML against this object.

Related Objects

The ETRM metadata documents two foreign-key relationships into this table, which form the core of any integration or reporting join:

• HZ_LOC_ASSIGNMENTS — references AR_LOCATION_COMBINATIONS through HZ_LOC_ASSIGNMENTS.LOC_ID. This is the primary association table linking a location or party site to the tax authority.
• RA_ADDRESSES_ALL — references AR_LOCATION_COMBINATIONS through RA_ADDRESSES_ALL.LOCATION_ID. This supplies the address detail for the location combination.

In a typical EBS Receivables environment, these two dependents are the most significant objects to examine alongside AR_LOCATION_COMBINATIONS. Broader context comes from the associated HZ (Trading Community Architecture) tables reached through HZ_LOC_ASSIGNMENTS, and from AR tax and address setup where the location combination is ultimately consumed. Analysts should confirm the exact set of dependents in their instance, since additional references may exist that are not represented in the supplied metadata excerpt.