Results for “cun_locations”

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

Overview

CUN_LOCATIONS is a Network Logistics location mapping table belonging to the CUN – Network Logistics – NATS product family. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 release streams, CUN is documented as obsolete, and the ETRM metadata explicitly records the table as "Not implemented in this database." As a result, CUN_LOCATIONS should be treated as a legacy schema artifact that persists in the data dictionary for backward compatibility but carries no active application logic, no seeded rows in a fresh installation, and no supported extension points in current releases.

The object's functional purpose was to serve as a cross-reference between Network Logistics internal location identifiers and Oracle Assets location records, enabling logistics transactions to resolve physical and asset-associated locations consistently. The heuristic Data Vault classification derived from its foreign key structure is hub-leaning. In Data Vault modeling terms this suggests the table behaves primarily as a hub: a stable, uniquely keyed registry of location business entities, with attribute changes pushed to associated satellites rather than stored on the hub record itself. This classification is a modeling suggestion only and does not reflect an Oracle-delivered Data Vault implementation.

Key Information Stored

The documented metadata identifies a small set of columns central to the table's structure and relationships:

• CUN_LOCATION_ID – The primary key column for the CUN_LOCATIONS_PK constraint. This is the surrogate identifier assigned by Network Logistics to represent a single location mapping entry. It is the column referenced by dependent unit tables and is the anchor for any join into the table.
• FA_LOCATION_ID – The foreign key column pointing to FA_LOCATIONS in Oracle Assets. This column establishes the mapping between the Network Logistics location record and its corresponding Oracle Assets location definition, and it is the principal business-relevant attribute documented for this table.
• HZ_LOCATION_ID – Although not listed as a column on CUN_LOCATIONS itself, this identifier is documented as the join column on the two child tables that reference CUN_LOCATIONS. It represents the Trading Community Architecture (HZ) location association used by the serialized and non-serialized unit records.

Because the metadata provides only the primary key and foreign key definitions, no additional attribute columns can be confirmed. The surrogate key CUN_LOCATION_ID is distinct from any business-key candidate; the ETRM excerpt documents no unique index other than the primary key constraint, so no natural business key is attested for this table.

Common Use Cases and Queries

Given that CUN_LOCATIONS is not implemented, practical use cases are limited to legacy data investigations, schema archaeology during upgrades, and impact analysis before dropping obsolete CUN objects. Typical scenarios include:

• Upgrade impact assessment. Determining whether any custom code, reports, or interfaces still reference CUN_LOCATIONS before an 11i-to-12.1.1 or 12.1.1-to-12.2.2 migration.
• Data lineage tracing. Establishing how Network Logistics units resolve to Assets locations through the FA_LOCATION_ID linkage.
• Repository reconciliation. Confirming the table exists in the data dictionary via ALL_TABLES while validating that it contains no rows.

Representative query patterns follow the documented relationship structure:

• Verify existence and emptiness: SELECT COUNT(*) FROM CUN_LOCATIONS; together with SELECT * FROM ALL_TABLES WHERE TABLE_NAME = 'CUN_LOCATIONS';
• Trace mapping to Assets: SELECT cl.CUN_LOCATION_ID, cl.FA_LOCATION_ID, fl.* FROM CUN_LOCATIONS cl JOIN FA_LOCATIONS fl ON cl.FA_LOCATION_ID = fl.LOCATION_ID;
• Trace dependent units: SELECT su.* FROM CUN_SERIALIZED_UNITS su JOIN CUN_LOCATIONS cl ON su.HZ_LOCATION_ID = cl.CUN_LOCATION_ID;

Related Objects

The documented foreign key topology identifies the following significant dependencies:

• FA_LOCATIONS – Referenced by CUN_LOCATIONS.FA_LOCATION_ID. The parent object supplying Oracle Assets location definitions that CUN_LOCATIONS maps to.
• CUN_SERIALIZED_UNITS – References CUN_LOCATIONS through HZ_LOCATION_ID. Child table holding serialized logistics units tied to a mapped location.
• CUN_NON_SERIALIZED_UNITS – Also references CUN_LOCATIONS through HZ_LOCATION_ID. Child table for non-serialized units sharing the same location mapping.
• CUN_LOCATIONS_PK – The primary key constraint enforcing uniqueness on CUN_LOCATION_ID.

No views or public APIs are attested for CUN_LOCATIONS in the supplied metadata. Because the product is flagged obsolete, integrators should treat the table and its dependents as deprecated and avoid new development against them.