Results for “ar_location_combinations_u1”

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

Overview

AR_LOC_COMBINATIONS_OLD is a Receivables (AR) module table owned by the AR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM documentation, its business description is that it "defines each distinct tax authority." In practice, the table stores location-based accounting key combinations that were used to associate a tax authority (a location) with a general ledger accounting flexfield structure. The "_OLD" suffix indicates this is a legacy or superseded structure; the current location/tax authority model in EBS relies on the Oracle Human Resources (HZ) location tables and the Tax (ZX) module. This object therefore persists largely for backward compatibility and historical reporting.

From a Data Vault modeling perspective, the heuristic classification mined from its foreign key structure is hub-leaning. The table holds a stable, unique business identifier (LOCATION_ID) with relatively few mutable descriptive attributes, which is characteristic of a hub entity rather than a transactional satellite. It should be treated as a reference/entity table serving as the target of foreign keys from dependent transactional tables.

Key Information Stored

The table contains 40 documented columns. The most significant are:

• LOCATION_ID — the surrogate primary key and the business-key candidate, enforced by both the AR_LOCATION_COMBINATIONS_PK primary key constraint and the AR_LOCATION_COMBINATIONS_U1 unique index. It uniquely identifies each location combination (tax authority).
• LOCATION_STRUCTURE_ID — identifies the accounting flexfield structure used to define the location combination.
• LOCATION_ID_SEGMENT_1 through LOCATION_ID_SEGMENT_10 — the individual accounting flexfield segment values that together constitute the location key.
• ENABLED_FLAG — indicates whether the location combination is active and usable.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range during which the combination is valid.
• SUMMARY_FLAG — denotes whether the record is a summary (parent) vs. detail entry.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns for capturing client-specific extension data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard EBS WHO (audit) columns.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrency program context captured at maintenance time.

The surrogate key is LOCATION_ID; the unique index AR_LOCATION_COMBINATIONS_U1 on LOCATION_ID confirms it as the business-key candidate. The remaining segment and attribute columns are descriptive or denormalized.

Common Use Cases and Queries

Typical scenarios involve reconciling legacy tax-authority location data, validating accounting flexfield combinations, and auditing foreign-key references from sales tax records. A representative query lists active location combinations:

• SELECT LOCATION_ID, LOCATION_STRUCTURE_ID, ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE FROM AR.AR_LOC_COMBINATIONS_OLD WHERE ENABLED_FLAG = 'Y' AND SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE + 1);
• Joining to sales tax records to inspect which tax authority is assigned: SELECT t.TAX_ID, t.LOCATION_ID, l.LOCATION_ID_SEGMENT_1 FROM AR.AR_SALES_TAX t, AR.AR_LOC_COMBINATIONS_OLD l WHERE t.LOCATION_ID = l.LOCATION_ID;
• Identifying orphaned or disabled combinations for data-cleanup initiatives prior to migration.

Related Objects

Foreign key metadata identifies the following dependents and related objects:

• AR_SALES_TAX — references this table via AR_SALES_TAX.LOCATION_ID = AR_LOC_COMBINATIONS_OLD.LOCATION_ID.
• HZ_LOC_ASSIGNMENTS_OBS — references this table via HZ_LOC_ASSIGNMENTS_OBS.LOC_ID = AR_LOC_COMBINATIONS_OLD.LOCATION_ID.
• Related AR/HZ accounting and location objects in the AR schema that share the location structure and segment model.

Because this is a superseded ("_OLD") object, consultants should confirm whether the current 12.2.2 data model still populates it before relying on it for functional reporting.