Results for “notification_date”

50+ results




Overview
Explore in AI Chat

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

Overview

CSP_MINMAX_NOTIFS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the CSP – Spares Management product family and serves as the reporting interface for warehouse min-max replenishment notifications. The view consolidates notification header data, item master descriptions, item cost information, and lookup-driven notification type meanings into a single denormalized result set, allowing operational users, concurrent programs, and integration endpoints to retrieve warehouse notification records without navigating the underlying normalized transaction tables.

Because the view restricts output to notifications whose STATUS equals 1 (active or open records), it is best understood as a work-queue style reporting object rather than a historical archive. It is commonly consumed by replenishment planners, warehouse supervisors, and custom OAF or BI Publisher reports that need visibility into excess and repair sources driving replenishment decisions.

Underlying Base Objects

The view is defined over several referenced objects, each accessed through synonyms or views in the APPS schema:

Key Columns

  • NOTIFICATION_ID – Primary identifier of the replenishment notification.
  • ORGANIZATION_ID / INVENTORY_ITEM_ID – Warehouse and item keys.
  • ITEM_NUMBER / ITEM_DESCRIPTION – Concatenated item segment and description from the item master.
  • ITEM_COST – Extended cost (unit item cost multiplied by notification quantity).
  • PLANNER_CODE – Owning planner responsible for the notification.
  • NOTIFICATION_TYPE – Code value from the CSP_NOTIF_SOURCE_TYPE lookup; this is the column most frequently searched by users referencing "notification_type".
  • NOTIFICATION_TYPE_MEANING – Translated, display-ready meaning of the notification type.
  • NOTIFICATION_QTY / NOTIFICATION_DATE / NEED_DATE – Quantity, creation date, and required-by date.
  • EXCESS_QTY / REPAIR_QTY – Aggregated available quantities contributed by detail lines tagged EXCESS or REPAIR.
  • ORDER_BY_DATE – Earliest order-by date across detail records.

Common Use Cases and Queries

Typical usage includes replenishment dashboards, planner worklists, and integration extracts. Filtering by NOTIFICATION_TYPE is the most frequent access pattern.

Example query returning open notifications of a given type:

  • SELECT notification_id, organization_id, item_number, notification_type, notification_type_meaning, notification_qty, excess_qty, repair_qty FROM csp_minmax_notifs_v WHERE notification_type = 'EXCESS' ORDER BY need_date;

Additional scenarios include aggregating extended item cost by planner for budget reviews, comparing NOTIFICATION_QTY against EXCESS_QTY and REPAIR_QTY to determine net replenishment exposure, and extracting records by NEED_DATE or ORDER_BY_DATE for scheduling reports. Because the view already joins lookup meanings and item descriptions, it is well suited to direct reporting use, though large extracts should be constrained by organization or date to limit the aggregation performed over CSP_NOTIFICATION_DETAILS.