Results for “network_location_code”

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

Overview

CUN_LOCATIONS_V is a reporting view within the Oracle E-Business Suite (EBS) Network Logistics module (product code CUN, covering Network Logistics – NATS). This view consolidates location master data drawn from three distinct sources into a single, denormalized projection, allowing callers to retrieve CUN network location attributes alongside Human Resources (HR) location detail and Fixed Assets (FA) key flexfield concatenated segments without writing multi-table joins themselves.

The view is documented in the ETRM 12.2.2 metadata, and the same definition applies to the 12.1.1 codebase. It is intended for read-only reporting and integration purposes — typically to supply network location reference data to downstream logistics, shipping, or trading processes. Notably, the metadata records that the object is not implemented in this database, indicating that CUN_LOCATIONS_V is a legacy or conditionally deployed object, present only in environments where the obsolete NATS functionality has been installed. Developers should therefore validate its existence in the target instance before relying on it in custom code.

Underlying Base Objects

The view is defined over three base objects, joined as follows:

• CUN_LOCATIONS (CL) — the primary (driving) table holding CUN-specific network location records. The view filters this table with CL.ENABLED_FLAG = 'Y', so only active network locations are exposed.
• HR_LOCATIONS (HR) — the HR location view supplying address and descriptive attributes. It is joined with an outer join (CL.LOCATION_ID = HR.LOCATION_ID(+)), meaning CUN records are retained even when no matching HR location exists.
• FA_LOCATIONS_KFV (FA) — the Fixed Assets location key flexfield view, joined on CL.FA_LOCATION_ID = FA.LOCATION_ID, providing the fully concatenated flexfield segment string.

The relationship is a classic master-reference pattern: CUN_LOCATIONS stores the network-specific identity and optional foreign keys to the shared HR and FA location definitions, while the view flattens those references into descriptive columns. Because the HR join is outer and the FA join is inner, any CUN row with a null FA_LOCATION_ID will be excluded from the result set.

Key Columns

• CUN_LOCATION_ID — primary identifier for the CUN network location record.
• FA_LOCATION_ID — foreign key to the Fixed Assets location.
• FA_LOCATION (alias for FA.CONCATENATED_SEGMENTS) — the concatenated FA location key flexfield value.
• NETWORK_LOCATION_CODE — the CUN-specific short code used to identify the network location.
• LOCATION_ID — foreign key linking the record to the HR location definition.
• LOCATION_CODE — the HR location code.
• DESCRIPTION — resolved via DECODE(CL.LOCATION_ID, NULL, CL.DESCRIPTION, HR.DESCRIPTION), preferring the HR description when a location link exists, otherwise the CUN description.
• ADDRESS_LINE_1, ADDRESS_LINE_2, ADDRESS_LINE_3 — address lines sourced from HR.
• TOWN_OR_CITY, COUNTRY, POSTAL_CODE — locality attributes from HR.
• REGION_1, REGION_2 — free-form regional attributes from HR.

Common Use Cases and Queries

Typical scenarios include populating network location lists in custom reports, validating CUN locations against FA flexfield segments, and feeding external logistics interfaces. A basic lookup of active network locations is shown below.

• List all enabled network locations with addresses:
  SELECT network_location_code, fa_location, description, town_or_city, country FROM cun_locations_v ORDER BY network_location_code;
• Retrieve a single location by its network code:
  SELECT location_code, description, postal_code FROM cun_locations_v WHERE network_location_code = :code;
• Audit records lacking an HR address (outer-join nulls):
  SELECT cun_location_id, network_location_code FROM cun_locations_v WHERE town_or_city IS NULL;
• Reconcile CUN locations against FA concatenated segments:
  SELECT cun_location_id, fa_location FROM cun_locations_v WHERE fa_location IS NOT NULL;

Because the object is flagged obsolete and not implemented in all instances, queries should be guarded by existence checks or migrated to supported HR and FA location sources where equivalent data can be sourced directly.