Results for “csp_notif_source_type”

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

Overview

APPS.CSP_MINMAX_NOTIFS_V is a reporting view in Oracle EBS Release 12.1.1 and 12.2.2 that consolidates min-max planning notification data generated by the inventory replenishment engine. It joins notification header records to their detail lines, resolves the inventory item flexfield and description, and derives item valuation from the item cost view. The result is a denormalized, presentation-ready rowset describing each min-max notification, its replenishment driver, and the aggregated quantities attributed to each notification source type.

The view is a core reporting object for the Min-Max Planning and Replenishment functionality. Because min-max notifications pass through a lifecycle (created, reviewed, released or cancelled), the view applies fixed filters that restrict output to active notifications: only rows where the notification status code equals 1 are returned, and the notification type and status codes are translated into their user-facing meanings through FND_LOOKUPS. The csp_notif_source_type lookup type referenced in this view is the seeded FND lookup CSP_NOTIF_SOURCE_TYPE, whose lookup codes classify each notification detail line by its replenishment origin — for example EXCESS and REPAIR — and which the view pivots into separate quantity columns.

Underlying Base Objects

The view is defined over the following documented objects, all referenced through APPS-owned synonyms or views:

• CSP_NOTIFICATIONS — the notification header table (aliased CN in the view definition). Supplies notification ID, organization, item, planner, notification type, quantity, notification date, need date, and status.
• CSP_NOTIFICATION_DETAILS — the notification detail lines (aliased CND), outer-joined to the header on notification_id. Supplies source_type, available_quantity, and order_by_date.
• MTL_SYSTEM_ITEMS_KFV — the item key flexfield view (aliased MSIV), joined on inventory_item_id and organization_id to resolve concatenated_segments and description.
• CST_ITEM_COSTS_FOR_GL_VIEW — the item cost view (aliased CIC), outer-joined on item and organization, used to compute the extended item cost value.
• FND_LOOKUPS — referenced twice (aliased FL and FL2) to translate notification_type via lookup type CSP_NOTIF_SOURCE_TYPE and status via lookup type CSP_NOTIFICATION_STATUS.
• FND_GLOBAL — the standard EBS session context package, used to determine the effective organization and user context under which the view is queried.

Key Columns

• NOTIFICATION_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID — the composite identifier of the notification and its inventory context.
• ITEM_NUMBER, ITEM_DESCRIPTION — item flexfield concatenated segments and description from MTL_SYSTEM_ITEMS_KFV.
• ITEM_COST — extended value, computed as CIC.ITEM_COST multiplied by the notification quantity CN.QUANTITY.
• PLANNER_CODE — the planner responsible for the item and its replenishment.
• NOTIFICATION_TYPE, NOTIFICATION_TYPE_MEANING — the raw code and its FND_LOOKUPS meaning, resolved through lookup type CSP_NOTIF_SOURCE_TYPE.
• NOTIFICATION_QTY, NOTIFICATION_DATE, NEED_DATE — the notified replenishment quantity and the notification and required-by dates.
• EXCESS_QTY, REPAIR_QTY — pivoted sums of CND.AVAILABLE_QUANTITY using SUM(DECODE(cnd.source_type, ...)) for the EXCESS and REPAIR source types respectively.
• ORDER_BY_DATE — the minimum order_by_date across the notification's detail lines.
• STATUS, STATUS_DESC — the numeric status code and its meaning from lookup type CSP_NOTIFICATION_STATUS.

Common Use Cases and Queries

Typical uses include open min-max notification reporting for a given planner or organization, replenishment workload review, and item valuation of pending notifications. A representative query filtering by notification source type is:

• SELECT notification_id, item_number, notification_type_meaning, notification_qty, need_date, excess_qty, repair_qty FROM apps.csp_minmax_notifs_v WHERE notification_type_meaning IS NOT NULL ORDER BY need_date;
• SELECT planner_code, item_number, item_cost, order_by_date FROM apps.csp_minmax_notifs_v WHERE organization_id = :org_id AND planner_code = :planner;

Because the view hard-codes the status filter (status = 1), reports requiring closed or cancelled notifications must query CSP_NOTIFICATIONS directly rather than this view.