Search Results cun_locations_pk

Overview

The CUN_LOCATIONS table is a core data object within the now-obsolete Network Logistics (CUN) module, specifically part of the NATS (Network Asset Tracking System) component in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its primary function was to serve as a mapping and reference table for location data. It acted as a central point to correlate and translate location identifiers between the Network Logistics module and other core EBS applications, most notably Fixed Assets (FA) and the Trading Community Architecture (TCA). The metadata explicitly notes that this table is "Not implemented in this database," indicating it was a defined but inactive object in standard deployments, likely reserved for custom or specific implementations of the NATS functionality.

Key Information Stored

Based on the provided structure, the table's primary purpose was to maintain relationships between different location identifiers. The key column is CUN_LOCATION_ID, which serves as the table's unique primary key. The most critical foreign key column is FA_LOCATION_ID, which establishes a direct link to the FA_LOCATIONS table in the Fixed Assets module. This mapping allowed Network Logistics to reference and utilize physical asset locations defined in Fixed Assets. The table's design suggests it may also have stored or referenced HZ_LOCATION_ID values from the TCA (HZ) schema, as indicated by its foreign key relationships with the CUN_NON_SERIALIZED_UNITS and CUN_SERIALIZED_UNITS tables.

Common Use Cases and Queries

Given its role as a mapping table, common use cases would involve joining asset or unit information from Network Logistics to standardized location data in other modules. For reporting, a typical query would retrieve the Fixed Assets location description for units tracked in NATS. A sample SQL pattern would join through this mapping table:

• SELECT csu.unit_number, fa.location_description
• FROM cun_serialized_units csu,
• cun_locations cl,
• fa_locations fa
• WHERE csu.hz_location_id = cl.cun_location_id
• AND cl.fa_location_id = fa.location_id;

This table would be essential for any integration point requiring a unified view of asset location across the logistics and financial asset registers.

Related Objects

The CUN_LOCATIONS table sits at a nexus between several key objects. Its primary foreign key relationship is with the FA_LOCATIONS table, linking it to the Fixed Assets module. It is referenced by two core inventory tracking tables within the obsolete NATS system: CUN_NON_SERIALIZED_UNITS and CUN_SERIALIZED_UNITS. These tables use the CUN_LOCATIONS table to resolve their HZ_LOCATION_ID values to a consistent location key. The existence of the CUN_LOCATIONS_PK primary key constraint enforces data integrity for the CUN_LOCATION_ID column across these relationships.