Results for “csp_notification_status”

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

Overview

APPS.CSP_NOT_TYSTAT_NAV is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It belongs to the CSP (Spares Management / Service Parts) module and serves as a navigation-oriented presentation layer that resolves notification status and notification type lookup codes into user-readable values. The view combines node-type configuration from the CSP navigation hierarchy with Oracle Application Object Library (FND) lookup definitions, producing a flattened, navigational dataset suitable for reporting and integration.

The object name itself signals its purpose: "NOT" (notification), "TY" (type), "STAT" (status), and "NAV" (navigation). Its primary users are typically CRM/Field Service (CS) and Service Parts modules that drive notification-driven navigation flows, allowing reports and integrations to map raw lookup codes to their descriptive meanings. The view is defined under the APPS schema, which means it is accessible through standard EBS responsibilities without additional grants.

Underlying Base Objects

The view is defined over four documented base objects:

• CSP_NAV_NODE_TYPES (VIEW) — provides the navigation root key and node type classification. The view filters records where ROOT_KEY = 'CSP_NOTIF' and NODE_TYPE = 'NOTIF_STATUS', restricting the output to the notification status branch of the navigation tree.
• CSP_PARTS_LOOPS_B (SYNONYM) — supplies the PARTS_LOOP_ID, which identifies the parts loop association for each notification navigation entry. This links the notification navigation to the parts loop configuration.
• FND_LOOKUPS (VIEW) — the standard Oracle lookup view, joined twice. The first alias (FL1) resolves the CSP_NOTIFICATION_STATUS lookup type, and the second alias (FL2) resolves the CSP_NOTIFICATION_TYPES lookup type.
• FND_GLOBAL (PACKAGE) — the FND session package, referenced for environment and user context (e.g., ORG_ID, USER_ID) used within the underlying CSP_NAV_NODE_TYPES definition.

Relationships are established through lookup_type filtering and the navigation root key, effectively producing a cross-product of notification statuses and notification types for each parts loop.

Key Columns

The view exposes seven columns, several of which are concatenated expressions:

• MEANING — the descriptive meaning of the notification status lookup code (from FND_LOOKUPS FL1.MEANING).
• NODE_TYPE — the node type classification (e.g., 'NOTIF_STATUS') from CSP_NAV_NODE_TYPES.
• Concatenated Expression 1 — a CSV-style concatenation of the notification status lookup code, notification type lookup code, and parts_loop_id, formatted with double quotes and commas. This is the navigation target/identifier string.
• ICON_NAME — the icon associated with the navigation node, used for UI rendering.
• Literal 'N' — a static flag value.
• Literal 'NOTIF_TYPES' — a static type identifier used by the consumer to route the navigation entry.
• Concatenated Expression 2 — a second CSV-style string combining the notification type lookup code and parts_loop_id.

These concatenated strings are especially important for downstream applications that require preformatted navigation keys rather than raw lookup codes.

Common Use Cases and Queries

The view is typically queried during configuration reviews of notification-driven navigation, during data extraction for integration with external field service systems, and when validating that lookup codes are correctly maintained against the parts loop configuration.

A representative query retrieving notification statuses for a specific parts loop:

• SELECT meaning, node_type, icon_name FROM apps.csp_not_tystat_nav WHERE 1=1 ORDER BY meaning;
• SELECT * FROM apps.csp_not_tystat_nav WHERE node_type = 'NOTIF_STATUS' ORDER BY 1;
• SELECT DISTINCT meaning, node_type FROM apps.csp_not_tystat_nav ORDER BY meaning;

Because the view pre-joins FND lookups, it eliminates the need to write multi-table joins against FND_LOOKUPS and CSP_NAV_NODE_TYPES manually. Reporting tools and concurrent programs can consume the CSV-formatted identifier columns directly to drive navigation menus or notification routing logic, making the view a compact, purpose-built access point within the CSP notification framework.