Results for “fa_dist_hist”

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

Overview

CUN_SERIALIZED_UNITS_V is a reporting view within the Oracle E-Business Suite CUN (Network Logistics – NATS) product family. CUN supported network and logistics functionality associated with the Network Asset Tracking System (NATS), a module that is now classified as obsolete in the Oracle EBS 12.1.1 and 12.2.2 release streams. The view is described in the ETRM metadata as presenting NL (Network Logistics) serialized item information, exposing a consolidated, denormalized picture of serialized units tracked by the application together with their inventory, asset, project, vendor, and location context.

Its role is purely read-oriented. It does not store data; instead it joins the CUN serialized units transaction table to descriptive master data so that serialized units can be reported without repeatedly joining the underlying transactional and reference tables. Because the CUN module is obsolete, the view is of interest primarily for legacy reporting, data migration analysis, historical auditing, and understanding the design of the NATS data model rather than for active transactional use.

Underlying Base Objects

The ETRM documentation lists no formal referenced base objects for this view, and expressly notes that the object is "Not implemented in this database." However, the documented view text shows the complete set of base objects used in the definition. The primary driving table is CUN_SERIALIZED_UNITS (aliased CSU), which supplies the serialized unit identifier, item, organization, quantity, status, subinventory, locator, revision, lot number, serial and vendor serial numbers, network number, vendor, project and task, asset grouping elements, and audit columns.

• CUN_SERIALIZED_UNITS (CSU) — the central NL serialized units table.
• MTL_SYSTEM_ITEMS_KFV (ITEM) and HR_ORGANIZATION_UNITS (INV_ORG) — item and inventory organization descriptions.
• MTL_ITEM_LOCATIONS_KFV (LOC) — locator (subinventory location) details.
• PO_VENDORS (VEND) — supplier information.
• PA_PROJECTS_ALL (PROJ) and PA_TASKS (TASK) — project and task context.
• CUN_LOCATIONS_V (CUL) — CUN location descriptions.
• FA_ADDITIONS_V (FA_ADD) and FA_DISTRIBUTION_HISTORY (FA_DIST_HIST) — Fixed Assets additions and distribution history for asset information.
• FND_LOOKUP_VALUES (FND_LOOK) — lookup values used to decode the unit status.

Most descriptive joins are outer joins (for example INV_ORG, LOC, VEND, TASK, and FND_LOOK), meaning a serialized unit row is retained even where reference data is missing.

Key Columns

The view exposes identifiers, descriptive attributes, and status information:

• SERIALIZED_UNIT_ID, ITEM_ID, ORGANIZATION_ID — primary keys linking back to the base CUN and inventory entities.
• INV_ITEM, DESCRIPTION — concatenated item segments and item description.
• INV_ORGANIZATION_NAME — inventory organization name.
• QUANTITY, STATUS, STATUS_NAME, STATUS_DESCRIPTION — on-hand quantity and the decoded unit status, resolved through FND_LOOKUP_VALUES where LOOKUP_TYPE = 'CUN_UNIT_STATUS'.
• SUBINVENTORY, LOCATOR_ID, LOCATOR — storage location information.
• REVISION, LOT_NUMBER, SERIAL_NUMBER, VENDOR_SERIAL_NUMBER, NETWORK_NUMBER — serialization and traceability attributes.
• FA_DISTRIBUTION_ID, ASSET_ID, ASSET_NUMBER, ASSET_DESCRIPTION, TAG_NUMBER, SERIAL_NUMBER, ASSET_TYPE, CURRENT_UNITS, CATEGORY_TYPE, MANUFACTURER_NAME — Fixed Assets attributes joined through FA_ADDITIONS_V.
• HZ_LOCATION_ID, LOC_DESCRIPTION — location description from CUN_LOCATIONS_V.
• PROJECT_ID, PROJECT_NUMBER, TASK_ID, TASK_NUMBER — project and task context.
• VENDOR_ID, VENDOR_NAME — supplier details.
• ASSET_GROUPING_ELEMENT1–3, LAST_TRANSACTION_ID, REFERENCE_DATA — CUN-specific grouping and transaction references.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Note the FND_LOOK join also constrains LANGUAGE to USERENV('LANG'), which is a common source of confusion when investigating the "fnd_look" lookup behavior, since the row returned depends on the session language.

Common Use Cases and Queries

Because the CUN module is obsolete, typical use cases are investigative or migration-oriented: extracting a historical inventory of serialized network units; reconciling CUN serialized units against Fixed Assets additions; confirming which project or task a unit was assigned to; and tracing a vendor serial number or network number back to a supplier. A representative query follows:

• SELECT serialized_unit_id, inv_item, description, inv_organization_name, quantity, status_name, serial_number, vendor_serial_number, network_number, asset_number, project_number, task_number, vendor_name FROM cun_serialized_units_v WHERE organization_id = :org_id;
• SELECT serial_number, network_number, quantity, asset_number, tag_number FROM cun_serialized_units_v WHERE vendor_id = :vendor_id;
• SELECT status, status_name, COUNT(*) FROM cun_serialized_units_v GROUP BY status, status_name;

Before any of these queries can run, the view must actually exist in the target instance. The metadata explicitly states that CUN_SERIALIZED_UNITS_V is "Not implemented in this database," so on many EBS 12.1.1 and 12.2.2 environments the object will not be present, and references to it will raise ORA-00942. Verification via DBA_VIEWS or FND_LOOKUPS (for the CUN_UNIT_STATUS lookup type) is recommended prior to relying on it in custom reporting.