Quality Notifications (QM Module)
Quality notifications can be used to document issues regarding insufficient quality of goods or services. That includes complaints against a vendor, complaints made by customers, or internal quality problems. Quality notifications can, of course, also be linked with a catalog profile.
The transactions that are used to create and manage quality notifications are QM01 / QM02 / QM03. Apart from that, the exact same transactions that are available in the PM module are also there for QM. These include notification lists such as QM10 (change list), QM11 (display list), and QM19 (multi-level list). The detail lists for tasks (QM12 / QM13), items (QM14 / QM15) and activities (QM16 / QM17) are also available. One additional transaction that PM doesn’t have is QM50, the graphical overview of notification creation that allows quick insights about quality problems.
Service Notifications (CS Module)
Service notifications are deduced from maintenance notifications and, in fact, share a lot of their functionality – not surprising since the CS module is built on top of PM. Service notifications are designed as a place to record customer enquiries that can lead to service orders. It is possible to record tasks and activities, and create service orders to trigger follow-up action. It also has some unique functionality, such as the linkage to service contracts (SD contracts) or the triggering of advance shipment for CS orders.
Service notifications share some transactions with maintenance notifications, but they have their own transactions to create (IW51), edit (IW52) and display (IW53) them. They also have their own list transactions for change (IW58) and display mode (IW59). When it comes to notification content however, they share the lists with the PM module: IW64/IW65 (activities), IW66/IW67 (tasks) and IW68/IW69 (items) are used here. Also, the multi-level list for service notifications (IW30) is the same as for plant maintenance.
Change Notifications (LO-ECH Module)
Change notifications are used to request and/or document changes to product data that is controlled by Engineering Change Management (LO-ECH), such as recipes or bills of material. An Engineering Change Order (ECO) can be created out of a change notification.
LO-ECH does not have its own transactions to manage notifications. Instead, it uses the generic IQSx transactions discussed above to create, edit and display notifications.