Results for “loc_id”

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

Overview

HZ_LOC_ASSIGNMENTS_OBS is a legacy table owned by the AR (Receivables) schema in Oracle E-Business Suite. Its name carries the "_OBS" suffix, denoting an obsolete or superseded object retained in the data dictionary for backward compatibility. Per the Oracle ETRM documentation for releases 12.1.1 and 12.2.2, the table is marked VALID at the database level, yet the documented description states plainly that it is "No longer used in R12." This apparent contradiction is common in EBS: the physical object survives because dropping it could break dependent grants, synonyms, or upgrade scripts, even though the application logic that once populated and consumed it has been replaced by the HZ (Trading Community Architecture) location model.

Functionally, the table historically associated a location with an organization and, through its LOC_ID column, with a receivables location combination. Metadata mined from the foreign-key structure classifies this object, as a modeling suggestion, as a link table — it resolves many-to-many style associations between locations and location combinations rather than acting as a hub of business entities or a satellite of descriptive attributes.

Key Information Stored

The documented physical schema contains 16 columns. The most consequential are:

• LOCATION_ID — Foreign key to HZ_LOCATIONS, identifying the location party record involved in the assignment.
• LOC_ID — Foreign key to AR_LOC_COMBINATIONS_OLD, tying the row to a legacy receivables location combination.
• ORG_ID — The operating unit (organization) identifier that scopes the assignment.
• OBJECT_VERSION_NUMBER — Optimistic locking counter, indicating the table once participated in the standard EBS concurrency-control pattern.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard WHO audit columns.
• LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent-program provenance columns recording which request and program last touched the row.
• WH_UPDATE_DATE — Warehouse update timestamp, used to flag changed rows for incremental data extraction.
• APPLICATION_ID, CREATED_BY_MODULE — Application and module registration identifiers.

The documented unique index HZ_LOC_ASSIGNMENTS_U1 spans (LOCATION_ID, ORG_ID), making that pair the business-key candidate. The unique index does not include LOC_ID, which is notable: the legacy key tied a location to an organization, while the LOC_ID association appears in the foreign-key structure without being part of the enforcing uniqueness constraint.

Common Use Cases and Queries

Because the table is documented as unused in R12, there is no supported functional or reporting use case. It should not be joined into new customizations, and any legacy code referencing it should be remediated. Its principal practical role is forensic: DBAs and upgrade analysts query it to confirm whether stale rows remain and whether dependencies still exist before archiving or dropping it.

• Inventory of legacy rows: SELECT ORG_ID, COUNT(*) FROM AR.HZ_LOC_ASSIGNMENTS_OBS GROUP BY ORG_ID;
• Referential check against surviving locations: SELECT a.LOCATION_ID FROM AR.HZ_LOC_ASSIGNMENTS_OBS a JOIN HZ_LOCATIONS l ON a.LOCATION_ID = l.LOCATION_ID WHERE l.LOCATION_ID IS NULL;
• Dependency scan prior to retirement: inspect DBA_DEPENDENCIES for views, synonyms, and packages referencing HZ_LOC_ASSIGNMENTS_OBS.
• Change auditing via WH_UPDATE_DATE for last-recorded modification.

Related Objects

• HZ_LOCATIONS — joined on HZ_LOC_ASSIGNMENTS_OBS.LOCATION_ID = HZ_LOCATIONS.LOCATION_ID.
• AR_LOC_COMBINATIONS_OLD — joined on HZ_LOC_ASSIGNMENTS_OBS.LOC_ID = AR_LOC_COMBINATIONS_OLD.LOC_ID.
• HZ_LOC_ASSIGNMENTS — the current R12 assignment table that superseded this obsolete object.
• HZ_LOC_ASSIGNMENTS_U1 — the unique index enforcing (LOCATION_ID, ORG_ID).
• AR_LOC_COMBINATIONS / HZ_LOCATIONS_V — the live location and combination objects to which new development should be directed.