Results for “csp_notification_types”

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

Overview

APPS.CSP_NOT_PLTYPES_NAV is a reporting view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases that supports the Service (CSP) module's navigation framework, specifically the notification and parts-loop tree structures used by the Service Technician and Field Service applications. The view name reflects its purpose: it presents the notification lookup codes ("NOT_PLTYPES" as a contraction of notification and parts-loop types) in a format consumed by a navigation or menu-building process.

The view does not store data of its own. Instead, it is a presentation layer over transactional lookup values and navigation node metadata, joining them so that the Service module can render the correct notification types against the appropriate parts loop. This makes the view relevant to reporting and integration work where the business needs to understand how notifications map to parts loops, and where downstream systems must retrieve the same lookup presentation that the EBS navigation framework uses at runtime.

Underlying Base Objects

The view is defined over three principal sources, all resolved through APPS synonyms and views:

• CSP_NAV_NODE_TYPES (VIEW) — Supplies the navigation node metadata. The view filters on root_key = 'CSP_NOTIF' and node_type = 'NOTIF_TYPES', restricting the output to notification type nodes within the notification root of the CSP navigation tree.
• FND_LOOKUPS (VIEW) — Supplies the user-visible lookup meaning and lookup code. The join restricts rows to lookup_type = 'CSP_NOTIFICATION_TYPES', which is the seeded lookup type that enumerates the notification types available in the Service module.
• CSP_PARTS_LOOPS_B (SYNONYM) — Supplies the parts loop identifier, parts_loop_id, which anchors each returned record to a specific parts loop definition.

The documented dependency list also references the FND_GLOBAL package, which typically provides session context (such as the current user or organization) within the standard EBS security model, though the view text itself performs no explicit call in the snippet provided.

Key Columns

The view exposes a small, purpose-built set of columns derived from the underlying joins:

• meaning (from FND_LOOKUPS) — The descriptive, user-facing name of the notification type.
• node_type (from CSP_NAV_NODE_TYPES) — The navigation node type, fixed to NOTIF_TYPES for the rows returned by this view.
• Composite navigation string — A constructed value concatenating the quoted lookup code and the quoted parts-loop identifier, producing a form such as "CODE","parts_loop_id". This is a navigation or parameter string intended for consumption by the calling framework rather than by end users.
• icon_name (from CSP_NAV_NODE_TYPES) — The icon associated with the notification type node in the navigation tree.
• Literal flags — Fixed values 'N' and 'NOTIF_PARTS_LOOP' that mark the row's role and the target navigation context.
• parts_loop_id (from CSP_PARTS_LOOPS_B) — The identifier linking the notification type to its parts loop, repeated from the composite string as a standalone column.

Rows are ordered by the first column (ORDER BY 1), so output is alphabetized by lookup meaning.

Common Use Cases and Queries

Typical use cases include auditing which notification types are active for a given parts loop, reproducing the exact navigation URL or parameter strings generated by the Service module, and feeding reporting extracts that reconcile the CSP_NOTIFICATION_TYPES lookup against the navigation tree configuration.

A basic query lists all notification type to parts loop assignments:

SELECT meaning, node_type, parts_loop_id, icon_name
FROM   apps.csp_not_pltypes_nav;

Filtering for a specific parts loop isolates the notification types available for one loop:

SELECT meaning, parts_loop_id
FROM   apps.csp_not_pltypes_nav
WHERE  parts_loop_id = :p_parts_loop_id;

To retrieve the generated navigation parameter string, select the unnamed composite expression positionally, for example SELECT meaning, "…" using the column's positional index, which is useful when reconstructing navigation links in custom forms or concurrent programs.