Results for “fe_type_name”

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

Overview

XNC_FESW_REST_V is a reporting view owned by the XNC – Sales for Communications module in Oracle E-Business Suite. The XNC product line historically provided telecommunications-specific extensions to Oracle's order-to-cash flows, particularly for wireless and wireline service providers managing product catalogs, switch restrictions, and feature/equipment mappings. In ETRM metadata the view is flagged as Obsolete, meaning Oracle no longer actively maintains or enhances it, though the definition may still persist in legacy 12.1.1 or 12.2.2 environments that were upgraded from earlier releases.

The view's stated purpose is to expose switch restrictions associated with a particular inventory product. Switch restrictions define the telecommunications network elements (switches, adapters) to which a given product may or may not be provisioned. By joining the switch-restriction entity to master item information, the view gives report writers and integration developers a single, denormalized source that pairs restriction rules with human-readable item names and descriptions.

The view is documented as not implemented in the reference ETRM database, which indicates it is a legacy or customer-specific object rather than one shipped and patched in every environment. Architects performing impact analysis on fe_type_name queries should confirm presence in the target instance before relying on it.

Underlying Base Objects

The view text defines it as an inner join between two objects:

• XNC_FESW_REST_VL – the multilanguage (VL) base entity holding the actual switch-restriction rows, including FESW_RESTRICTIONS_ID, FE_TYPE_NAME, SW_GENERIC, ADAPTER_TYPE, active-date ranges, DFF attributes, and the DESCRIPTION column.
• MTL_SYSTEM_ITEMS_VL (aliased MSIV) – the seeded Inventory item view supplying PADDED_CONCATENATED_SEGMENTS (concatenated key flexfield segments) and DESCRIPTION.

The join predicate is composite: B.INVENTORY_ITEM_ID = MSIV.INVENTORY_ITEM_ID and B.ORGANIZATION_ID = MSIV.ORGANIZATION_ID. This ensures the restriction is resolved against the item definition in the same operating unit / inventory organization context. Because the join is an equijoin, restrictions without a matching item row in the same organization are excluded. ETRM notes no additional documented base objects beyond these two.

Key Columns

• ROW_ID – surrogate identifier propagated from the VL table.
• FESW_RESTRICTIONS_ID – primary key of the underlying restriction record; useful for drill-down or debugging.
• INVENTORY_ITEM_ID, ORGANIZATION_ID – composite item/organization key.
• ITEM_NAME – RTRIM(MSIV.PADDED_CONCATENATED_SEGMENTS), the user-facing concatenated item flexfield.
• ITEM_DESCRIPTION – item master description.
• FE_TYPE_NAME – the feature/equipment type name. This is the column most frequently searched, as it categorizes the switch-restriction rule (for example, by network feature or switch class).
• SW_GENERIC – indicates whether the restriction applies generically to the switch rather than to a specific adapter.
• ADAPTER_TYPE – the adapter classification for the restricted switch.
• START_ACTIVE_DATE / END_ACTIVE_DATE – effective dating window for the restriction; queries should typically filter to the current date.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 – descriptive flexfield segments.
• DESCRIPTION – the restriction record's own description.

Common Use Cases and Queries

Typical uses include generating a catalog of switch restrictions by feature type, validating that a product is not blocked from provisioning to a target switch, and feeding downstream provisioning or order-management interfaces. A sample query filtering on the feature type is shown below.

SELECT fe_type_name,
       item_name,
       item_description,
       sw_generic,
       adapter_type,
       start_active_date,
       end_active_date
  FROM xnc_fesw_rest_v
 WHERE fe_type_name = :p_fe_type_name
   AND TRUNC(SYSDATE)
       BETWEEN NVL(start_active_date, TRUNC(SYSDATE))
           AND NVL(end_active_date, TRUNC(SYSDATE));

Because the object is obsolete and not universally implemented, always verify existence via ALL_VIEWS before incorporating it into custom reporting, and consider whether a supported alternative such as the XNC feature/equipment tables directly should be used for new development.