Setting Up and Using the Message Dashboard

This chapter provides an overview of the message dashboard and discusses how to:

Set up the message dashboard.
Receive notifications using XML messages.
Search and use the message dashboard.
Create message notifications for new processes and categories.
Identify the processes and categories delivered in the message registry.

Understanding the Message Dashboard

The Message Dashboard is a central place to view information related to messages, warnings and errors that occur within many batch or online processes throughout the system. In addition to viewing information within the Message Dashboard, a user can receive notifications when these messages occur via an email, a worklist entry, or a XML message. The message dashboard provides information such as descriptive text, links, and context information, which enable the user to make a decision easier when certain conditions occur during batch and online processes.

PeopleSoft batch and online processes that send information (messages, warnings, and errors) to the message dashboard are:

PeopleSoft Inventory
PeopleSoft Order Management
PeopleSoft Purchasing
PeopleSoft Production Management
PeopleSoft Work Order Management

This diagram illustrates the process flow of the message dashboard:

Message Dashboard process

A batch or online process creates a message, which is automatically sent to the message dashboard. If you have notifications enabled (set up in the message, system-level registry or business-unit level registry, the system notifies the appropriate person using an email, a worklist entry, or an XML message. If the notification is sent using an email or a worklist entry, a link is provided to take the individual to the message detail page of the message dashboard.

See Identifying the Processes and Categories Delivered in the Message Registry.

Setting Up the Message Dashboard

This section discusses how to:

Set up the message registry.
Set up registry notifications at the system level.
Set up registry notifications at the business-unit level.

Understanding Message Dashboard Setup

All messages from predefined batch and online processes can be viewed in the message dashboard with the delivered product. However, you can define two levels of notification overrides within the system. These two levels are:

System Level Notifications
Business-unit Level Notifications

System-level notifications are defined by the process name and the category. They enable you to override a notification for a specific process name and category for the entire system. For example, if Bob receives all of the notifications for the OM_PEGGING / RECEIPT process and he goes on an extended vacation, you can set up an override at the system level, which routes all of these specific messages to Steve.

Business-unit level notifications are defined by the process name, the category, and the business unit. They enable you to override a notification for a specific process name, category, and business unit within the system. For example, if Bob receives all of the notifications for the OM_PEGGING / RECEIPT process and he goes on an extended vacation, you can set up an override at the business-unit level, which routes all of the specific messages for business unit US001 to Steve and routes all of the specific messages for business unit US008 to Ralph.

When you set up system and business-unit level notifications you determine who should be notified when an error or warning occurs, and how they should be notified.

Pages Used to Set Up the Message Dashboard

Page Name	Object Name	Navigation	Usage
Message Registry	SAC_EWN_REGISTRY	Set Up Financials/Supply Chain, Common Definitions, Errors and Warnings, Message Registry	Set up the message registry, which defines the delivered notification processes and categories in the system.
System-Level Notifications	SAC_EWN_REG_SYS	Set Up Financials/Supply Chain, Common Definitions, Errors and Warnings, System-Level Notifications	Set up system-level notifications, which defines notification overrides at the system level for each process name and process category. This level of notification is optional.
BU-Level Notifications	SAC_EWN_REG_BU	Set Up Financials/Supply Chain, Common Definitions, Errors and Warnings, BU-Level Notifications	Set up business-unit level notifications, which defines notification overrides at the business-unit level for each process name, process category, and business unit. This level of notification is optional.

Setting Up the Message Registry

The message registry contains all delivered processes and categories. If you have customized your system with additional processes and categories, you can add to the message registry.

Access the Message Registry page.

The message registry is defined by process name and process category.

Process Name	An application batch or online process.
Category Name	A logical partition of the application process. Category names are defined when the process is developed. For example, when the Reservation process runs, there are multiple messages related to item ID. All of these item ID-type messages are grouped into one category, so that one user can be notified when a message occurs. For each delivered process, the PeopleSoft system has categories that are delivered with the PeopleSoft product. Note. If you are not making changes to the delivered processes, you do not need to add to the Message Registry.
Description	The description in the text box is considered the extended text description. This extended text description is accessed from the message dashboard when you click on the View Extension Text button.
Worklist Notifications, Email Notifications, and XML Notifications	Select to enable overrides at the system and business-unit levels for this message.
Enable Custom Action, Application Class Path and Application Class ID	Select to enable a customized action. Use this option if you have written your own application class for a customized action. Enter the Application Class Path and Application Class ID fields, which are extensions of the SCM_SAC_EWN_MVC:SCM_SAC_EWN_MODEL:EWN_PostProcessingUserExit class.
Pre-Processing User Exit - Application Class Path and Pre-Processing user Exit - Application Class ID	Enter the Application Class Path and Application Class ID fields. A preprocessing user exit tells the system to run another process before it determines who to notify. For example, a purchase order approval process is created that is based on the purchase order value. Purchase orders under 500.00 USD are approved by the department manager, and purchase orders over 500.01 USD are approved by the department director. The preprocessing user exit tells the system to run the purchase order approval process before determining who to notify, which are extensions of the SCM_SAC_EWN_MVC:SCM_SAC_EWN_MODEL:EWN_PreProcessingUserExit class.

See Identifying the Processes and Categories Delivered in the Message Registry.

Setting Up Registry Notifications at the System Level

Access the System-Level Notifications page.

The Override Notification sections of this page are determined by the options selected on the Message Registry page.

Disable All Notifications	Select to disable all notifications for this message.
Disable Worklist Notification	Select to disable only worklist notifications for this message.
Role and User ID	Select a role or a user ID that determines the person to notify for this message. Note. If the Worklist Notifications check box is selected on the Message Registry page and the Role & User ID fields are not entered on the System Level Notifications page, then the worklist notification for the original message object (either UserID or Role) is used.
Disable Email Notification	Select to disable only email notifications for this message.
Email Option	Select Address or UserID. Depending on which option you select, the field to the right will change to Email Address or User ID. You may add multiple rows if needed. Note. If the Email Notifications check box is selected on the Message Registry page, and you do not enter an Email Address on the System-Level Notifications page, then the Email Address notification for the original message object is used.
Disable XML Notification	Select to disable only XML notifications for this message.
Node	Select the Node Name for the XML notification. Note. If the XML Notifications check box is selected on the Message Registry page, and you do not enter a Node on the System-Level Notifications page, then the XML notification (node) for the original message object is used.

Note. The notification of some processes are controlled by the owner of the transaction. For example, notification messages for pegging purchase orders goes to the buyer on the purchase order. Therefore, overriding notifications at the business-unit or system level is not enabled.

Setting Up Registry Notifications at the Business-Unit Level

Access the BU-Level Notifications page.

The BU-Level Notifications page operates exactly like the System-Level Notifications page except that it enables you to specify a business unit as a key for notifications.

Receiving Notifications Using XML Messages

The PeopleSoft Application Messaging functionality provides a method for communication between external systems and PeopleSoft using industry standard XML-formatted messages. The error and warning framework can generate the application message, SAC_EWN_NOTIFY_MSG, to notify an external system that an error or warning has occurred in the PeopleSoft system.

To use this application message, use PeopleTools to:

Activate the SAC_EWN_NOTIFY_MSG message.
Set up an outbound asynchronous transaction defining the SAC_EWN_NOTIFY_MSG message on each node that receives the transaction.
Verify the SAC_EWN_MSG_CHNL message channel is in Run mode.

The previous setup instructions assume that the message environment has been set up in PeopleSoft Integration Broker.

Searching and Viewing the Message Dashboard

This section discusses how to:

Search for a message.
View message details.

Pages Used to Search and View the Message Dashboard

Page Name	Object Name	Navigation	Usage
Message Dashboard	SAC_EWN_DSH_SRCH	Set Up Financials/Supply Chain, Common Definitions, Errors and Warnings, Message Dashboard	Search for a message that is created from a batch or online process.
Message Details	SAC_EWN_DASHBRD	Set Up Financials/Supply Chain, Common Definitions, Errors and Warnings, Message Details	View message details that are created from a batch or online process.

Searching for a Message

Access the Message Dashboard page.

The Message Dashboard page is used to search for messages based on selected search criteria.

Viewing Message Details

Access the Message Detail page.

The Message Detail page provides valuable information for the user to take action regarding the message, which includes valuable links.

View Transaction Detail	Select this link to see the actual transaction page, and all the details of the transaction. This link is dependant on the employee servlet setup on the URL Maintenance page. See Setting Up the Message Dashboard.
View Context Values	Select this link to view the technical information about the message.
View Explanation Text	Select this button to view the long text description that is entered on the Message Registry page.
Process Instance	Select this button to view the process monitor information.

Creating Message Notifications for New Processes and Categories

This section discusses how to create new message notifications for processes and categories that are not delivered with the PeopleSoft system.

If you have customized application processes that are delivered with the PeopleSoft system, you can add new processes and categories to the message registry.

Follow these steps to add to the message registry:

Add your process name and category to the message registry page.
1. Add the description and long text description, which describes the functionality of the message that is logged into the registry so that you can assign the appropriate user to the notification classification.
2. Disable any notification feature that your application does not allow you to override at the system and business-unit levels. These are notifications that are handled within the object interface directly.
Create a message context record to pass all transactional data through the message framework.
1. All context records must include the SAC_EWN_LOG_KEY.
2. Any additional transactional fields can be added to the context record.
Implement the EWN class within your application process by using the SCM_SAC_EWN_MVC:SCM_SAC_EWN_MODEL:EWN_INTERFACE class.

Identifying the Processes and Categories Delivered in the Message Registry

This table lists the processes and categories that are delivered in the Message Registry.

Application	Process Name	Process Category	Description
Inventory	IN_DEMAND	OM_BATCH_TRANSACTION	Provide notification to both an Inventory manager and a PeopleSoft Order Management sales order owner that changes have been made to a sales order and/or demand, and that a log of changes is ready for review.
Inventory	IN_DEMAND	OM_ONLINE_TRANSACTION	Provide notification to an Inventory manager of requested updates from PeopleSoft Order Management demand transactions. These are updates that must be performed via stock request Maintenance component because the demand change configuration does not allow PeopleSoft Order Management to update demand directly.
Inventory	IN_DEMAND	IN_OM_ONLINE_TRANSACTION	Provide notification to the owner of an PeopleSoft Order Management sales order that changes were made to the sales order demand via stock request Maintenance component. The notification lets the sales order owner know that either (1) the demand data has been updated to be in sync with the associated sales order, or (2) a change was made in demand that needs to be applied to the associated sales order.
Inventory	IN_PEGGING	XFER_DMND_QTY_INCREASE	Supply quantity pegged to a transfer demand has been increased.
Inventory	IN_PEGGING	XFER_DMND_QTY_DECREASE	Supply quantity pegged to a transfer demand has been decreased.
Inventory	IN_PEGGING	XFR_SPLY_BREAK	The peg chain between a demand and a transfer supply has been broken.
Inventory	IN_PEGGING	XFER_DMND_RECEIPT	Pegged supply has been received / completed for a pegged stock request.
Inventory	IN_PEGGING	XFER_DMND_DTE_RESCH_OUT	Supply date pegged to a transfer demand has been rescheduled out past the ship date.
Inventory	IN_PEGGING	XFER_DMND_DTE_RESCH_IN	Supply date pegged to a transfer demand has been rescheduled in.
Inventory	IN_PEGGING	XFER_DMND_PUTAWAY	Pegged supply has been putaway for a pegged transfer demand.
Inventory	IN_PEGGING	XFR_SPLY_QTY_DECREASE	Demand quantity pegged to a transfer supply has been decreased.
Inventory	IN_PEGGING	XFR_SPLY_DTE_RESCH_OUT	Demand date pegged to a transfer supply has been rescheduled out.
Inventory	IN_PEGGING	XFR_SPLY_QTY_INCREASE	Demand quantity pegged to a transfer supply has been increased.
Inventory	IN_PEGGING	XFR_SPLY_CLOSE	Demand pegged to a transfer supply has been closed.
Inventory	IN_PEGGING	XFR_SPLY_CANCEL	Demand pegged to a transfer supply has been canceled.
Inventory	IN_PEGGING	XFR_SPLY_DTE_RESCH_IN	Demand date pegged to a transfer supply has been rescheduled in earlier than the transfer arrival date.
Inventory	IN_PEGGING	STK_RQST_DTE_RESCH_IN	Supply date pegged to a stock request has been rescheduled in.
Inventory	IN_PEGGING	STK_RQST_CLOSE	Supply pegged to a stock request has been closed short.
Inventory	IN_PEGGING	STK_RQST_PUTAWAY	Pegged supply has been putaway for a pegged stock request.
Inventory	IN_PEGGING	STK_RQST_DTE_RESCH_OUT	Supply date pegged to a stock request has been rescheduled out past the ship date.
Inventory	IN_PEGGING	STK_RQST_BREAK	Supply pegged to a stock request has been broken.
Inventory	IN_PEGGING	BATCHEMAIL	Provide notification to an inventory manager that pegging changes have been made and that a log of changes is ready for review.
Inventory	IN_PEGGING	STK_RQST_CANCEL	Supply pegged to a stock request has been canceled.
Inventory	IN_PEGGING	XFER_DMND_CANCEL	Supply pegged to a transfer demand has been canceled.
Inventory	IN_PEGGING	XFER_DMND_BREAK	Supply quantity pegged to a transfer demand has been broken.
Inventory	IN_PEGGING	XFER_DMND_CLOSE	Supply quantity pegged to a transfer demand thas been closed short.
Inventory	IN_PEGGING	STK_RQST_QTY_INCREASE	Supply quantity pegged to a stock request has been increased.
Inventory	IN_PEGGING	STK_RQST_QTY_DECREASE	Supply quantity pegged to a stock request has been decreased.
Inventory	IN_PEGGING	STK_RQST_RECEIPT	Pegged supply has been received / completed for a pegged stock request.
Inventory	IN_RESERVATIONS	RESERVE_RULES	Notifications generated to an Inventory Manager from the reservation rules for non-VMI (vendor-managed inventory) orders.
Inventory	IN_RESERVATIONS	RESERVE_RULES_VMI	Notifications generated to an Inventory Manager from the reservation rules for VMI orders.
Inventory	IN_RESERVATIONS	BACKORDER	Manual backorder notification sent to Inventory Manager.
Order Management	OM_BILLING	FULFILLMENT_INCOMPLETE	Some portion of the goods ordered on a counter sales order, and picked up by the customer, have not successfully completed the fulfillment process in Inventory. This activity is passed through the fulfillment process within a single EIP_CTL_ID. PeopleSoft Order Management_BILL cannot pass any customer pick up order activity for a given EIP_CTL_ID to billing until all of the goods that the EIP_CTL_ID represents are marked as depleted in inventory. You must correct the situation in Inventory so that all the goods associated with the EIP_CTL_ID are depleted before PeopleSoft Order Management_BILL will interface the activity to billing.
Order Management	OM_PEGGING	HARD_TO_SOFT	A hard peg chain for a sales order has been changed to a soft peg chain.
Order Management	OM_PEGGING	PUTAWAY	Pegged supply has been putaway for a pegged sales order.
Order Management	OM_PEGGING	HARD_PEG_QTY_CHANGE	The pegged quantity changed on a sales order that is hard pegged to a supply.
Order Management	OM_PEGGING	QTY_INCREASE	Supply quantity pegged to a sales order has been increased.
Order Management	OM_PEGGING	RECEIPT	Pegged supply has been received / completed for a pegged sales order.
Order Management	OM_PEGGING	QTY_DECREASE	Supply quantity pegged to a sales order has been decreased.
Order Management	OM_PEGGING	CANCEL	Supply pegged to a sales order supply has been canceled.
Order Management	OM_PEGGING	CLOSE	Supply quantity pegged to a sales order supply has been closed short.
Order Management	OM_PEGGING	BREAK	A peg chain between supply and a sales order has been broken.
Order Management	OM_PEGGING	DTE_RESCH_OUT	Supply date pegged to a sales order has been rescheduled out past the ship date.
Order Management	OM_PEGGING	DTE_RESCH_IN	Supply date pegged to a sales order has been rescheduled in.
Order Management	OM_RESERVATIONS	RESERVE_RULES	Notifications generated to the sales order owner from the reservation rules for non-VMI orders.
Order Management	OM_RESERVATIONS	RESERVE_RULES_VMI	Notifications generated to the sales order owner from the reservation rules for VMI orders.
Order Management	OM_RESERVATIONS	BACKORDER	Manual backorder notification to the sales order owner.
Purchasing	PO_PEGGING	HARD_PEG_QTY_CHANGE	The pegged quantity changed on a purchase order that is hard pegged to a sales order.
Purchasing	PO_PEGGING	DTE_RESCH_OUT	Demand date pegged to a purchase order has been rescheduled out.
Purchasing	PO_PEGGING	QTY_INCREASE	Demand quantity pegged to a purchase order has been increased.
Purchasing	PO_PEGGING	QTY_DECREASE	Demand quantity pegged to a purchase order has been decreased.
Purchasing	PO_PEGGING	CANCEL	Demand pegged to a purchase order has been canceled and the peg chain status set to Cancel.
Purchasing	PO_PEGGING	BREAK	The peg chain between a demand and a purchase order has been broken.
Purchasing	PO_PEGGING	DTE_RESCH_IN	Demand date pegged to a purchase order has been rescheduled in earlier than the PO due date.
Purchasing	PO_PEGGING	CLOSE	Demand pegged to a purchase order has been closed.
Purchasing	PO_VRBT_NOTIFY	NOTIFY_REBATE_MGR	Rebate Manager Notification.
Purchasing	PO_VRBT_NOTIFY	NOTIFY_SETTLEMENT_MGR	Settlement Manager Notification.
Purchasing	PO_VRBT_NOTIFY	NOTIFY_CLAIMS_MGR	Claims Manager Notification.
Manufacturing	PRDN_PEGGING	DTE_RESCH_OUT	Demand date pegged to a production order has been rescheduled out.
Manufacturing	PRDN_PEGGING	DTE_RESCH_IN	Demand date pegged to a production order has been rescheduled in earlier than the PO due date.
Manufacturing	PRDN_PEGGING	QTY_INCREASE	Demand quantity pegged to a production order has been increased.
Manufacturing	PRDN_PEGGING	QTY_DECREASE	Demand quantity pegged to a production order has been decreased.
Manufacturing	PRDN_PEGGING	CANCEL	Demand pegged to a production order has been canceled.
Manufacturing	PRDN_PEGGING	BREAK	The peg chain between a demand and a production order has been broken.
Manufacturing	PRDN_PEGGING	CLOSE	Demand pegged to a production order has been closed short.
Purchasing	REQ_PEGGING	HARD_PEG_QTY_CHANGE	The pegged quantity changed on a requisition that is hard pegged to a sales order.
Purchasing	REQ_PEGGING	DTE_RESCH_OUT	Demand date pegged to a requisition has been rescheduled out.
Purchasing	REQ_PEGGING	QTY_INCREASE	Demand quantity pegged to a requisition has been increased.
Purchasing	REQ_PEGGING	QTY_DECREASE	Demand quantity pegged to a requisition has been decreased.
Purchasing	REQ_PEGGING	CANCEL	Demand pegged to a requisition has been canceled and peg chain status set to cancel.
Purchasing	REQ_PEGGING	BREAK	The peg chain between one or more demands and a requisition has been broken.
Purchasing	REQ_PEGGING	DTE_RESCH_IN	Demand date pegged to a requisition has been rescheduled in earlier than the requisition due date.
Purchasing	REQ_PEGGING	CLOSE	Demand pegged to a requisition has been closed.
Maintenance Management	WM_PEGGING	QTY_DECREASE	Supply quantity pegged to a work order has been decreased.
Maintenance Management	WM_PEGGING	QTY_INCREASE	Supply quantity pegged to a work order has been increased.
Maintenance Management	WM_PEGGING	PUTAWAY	Pegged supply has been received / completed for a pegged work order.
Maintenance Management	WM_PEGGING	REQ_UPDATE	Peg work order supply has been decreased and reopening on requisition.
Maintenance Management	WM_PEGGING	RECEIPT	Pegged supply has been received / completed for a pegged work order.
Maintenance Management	WM_PEGGING	CANCEL	Supply pegged to a work order has been canceled.
Maintenance Management	WM_PEGGING	CLOSE	Supply quantity pegged to a work order has been closed short.
Maintenance Management	WM_PEGGING	BREAK	The peg chain between a supply and a work order demand have been broken.
Maintenance Management	WM_PEGGING	DTE_RESCH_OUT	Supply date pegged to a work order has been rescheduled out past the ship date.
Maintenance Management	WM_PEGGING	DTE_RESCH_IN	Supply date pegged to a work order has been rescheduled in.