Results for “csp_notifications”

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

Overview

CSP_NOTIFICATIONS is a table in the CSP (Spares Management) product module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2 releases. The table holds parts loop notifications, which are generated when a parts loop monitoring or replenishment process identifies a condition requiring attention from a planner. It forms the transactional core of the CSP notification framework, capturing the item, organization, planner, and loop context of each notification together with a reason, type, status, and quantity.

From a data modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table is anchored by a single-column surrogate primary key and carries many descriptive and historical attributes that describe a business event rather than defining a standalone business entity or a pure many-to-many relationship. It is best understood as an event or document header record that is joined to master data such as planners, items, and parts loops.

Key Information Stored

The table contains 38 documented columns. The most significant are:

• NOTIFICATION_ID — the surrogate primary key, defined by CSP_NOTIFICATIONS_PK and enforced uniquely by CSP_NOTIFICATIONS_U1. This is the sole documented business-key candidate.
• PLANNER_CODE — the planner to whom the notification is directed; foreign key to MTL_PLANNERS (combined with ORGANIZATION_ID).
• PARTS_LOOP_ID — the parts loop instance associated with the notification; foreign key to CSP_PARTS_LOOPS_B.
• INVENTORY_ITEM_ID — the inventory item in scope, foreign key to MTL_SYSTEM_ITEMS_B (combined with ORGANIZATION_ID).
• ORGANIZATION_ID — the inventory organization context used by the item and planner joins.
• NOTIFICATION_DATE and NEED_DATE — when the notification was raised and when action is required.
• NOTIFICATION_TYPE and REASON — classification of the event and the underlying cause.
• STATUS — the workflow or processing state of the notification.
• QUANTITY — the affected or recommended quantity.
• SUPPRESS_END_DATE — the point at which the notification should no longer be surfaced.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant data isolation.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — concurrency and audit lineage.

Common Use Cases and Queries

The primary use case is a planner worklist showing open parts loop notifications with item, loop, and date context. Notifications issued by concurrent programs can be reconciled back to the originating request and program. Aging and suppression analysis uses NOTIFICATION_DATE against NEED_DATE and SUPPRESS_END_DATE, while type and reason distributions support exception reporting.

Typical query patterns include joining to CSP_NOTIFICATION_DETAILS on NOTIFICATION_ID to expand header-level notifications into detail lines; joining to CSP_PARTS_LOOPS_B on PARTS_LOOP_ID for loop definitions; and joining to MTL_SYSTEM_ITEMS_B and MTL_PLANNERS on INVENTORY_ITEM_ID and PLANNER_CODE with ORGANIZATION_ID. A representative extraction filters by STATUS and NOTIFICATION_DATE range, or groups by NOTIFICATION_TYPE and REASON to size the planning exception workload. Because SECURITY_GROUP_ID is present, reporting SQL should generally be augmented with the appropriate security-group predicate.

Related Objects

• CSP_NOTIFICATION_DETAILS — the principal child table, joined on CSP_NOTIFICATION_DETAILS.NOTIFICATION_ID = CSP_NOTIFICATIONS.NOTIFICATION_ID.
• CSP_PARTS_LOOPS_B — loop master referenced through PARTS_LOOP_ID.
• MTL_SYSTEM_ITEMS_B — item master referenced through INVENTORY_ITEM_ID and ORGANIZATION_ID.
• MTL_PLANNERS — planner master referenced through PLANNER_CODE and ORGANIZATION_ID.
• FND_SECURITY_GROUPS — security group referenced through SECURITY_GROUP_ID.

Together these relationships place CSP_NOTIFICATIONS at the junction of CSP loop configuration and standard inventory master data, making it the central header for parts loop notification processing and reporting.