Workflow - Planning Exception Messages

Planning Exception Messages Workflow

This appendix provides detailed information about planning exception messages generated through the workflow process in Oracle MRP.

The Planning Exception Messages workflow allows you to automate the processing of reviewing exceptions in order to take corrective action quickly when generating materials and resource plans. This allows you to identify potential conflicts and the status of resources. You can then take appropriate action to resolve these issues.

Exception messages are routed to key contacts for specific responsibilities. Recipients can be supplier and customer contacts as well as internal personnel. Suppliers and customers can use Oracle Supply Management Portal or Oracle Web Customers to see detailed information related to the exception condition. The process for resolving exceptions could involve following established procedures, routing information, obtaining authorization, and updating information concerning materials. This workflow consists of processes viewable in the Workflow Builder as a diagram, some of whose objects and properties can be modified. The Planning Exception Messages workflow lets you do the following tasks:

You can view or modify this workflow in the Oracle Workflow Builder. See Oracle Workflow Guide.

See Also

Customizing the Planning Exception Messages Process

Use the Oracle Workflow Builder to customize workflows. You can also use the Workflow Builder to create unique planning exception messages workflows for different parts of your organization and associate particular workflows with certain activities.

To display the process in Oracle Workflow Builder:

  1. Choose Open from the File menu, and connect to the database. See: Opening and Saving Item Types, Oracle Workflow Guide.

    The display name of the exception messages workflow is Planning Exception Messages. The name of its Workflow definition file is mrpexpwf.wft

  2. Expand the data source, then the Exception Message branch within that data source.

  3. Expand the Processes branch, then choose the Exception Process activity to display the diagram.

Creating a New Custom Process

Customize the default (original) workflow that Oracle MRP provides after creating a backup. This allows you to have your backup while testing customizations.

Required Modifications

There are no required modifications you need to make to this workflow.

Supported and Unsupported Customizations

Although you can use the Planning Exception Messages process as is, you may wish to customize the process further to accommodate your organization's specific needs.

You could create new functionality in the PL/SQL procedures and add the nodes to the workflow diagram. Or you could modify the activities and redirect the process in the workflow, such as sending notification to people other than the planner.

Attributes

You can add new item type attributes to the workflow, but it is not advisable to modify the existing attributes.

Processes

If you modify a process, it is essential that the basic flow remain intact in order to maintain data integrity in the database. However, you could add additional checks (processes or function activities) before allowing data to be inserted into the tables.

If you modify any process, either by replacing a portion of its flow or by adding additional function activities, remember the following:

Notifications

All of the notifications can be modified to meet your individual business needs. However, if the notification has a reply code, you must make sure that the Result Type of your customized notification matches the Result Type of the default notification.

Messages

All of the messages can be modified to meet your individual business needs. For a list of the types of exceptions that may occur when you run your plan. See: Reviewing Planning Exceptions.

Messages are sent to particular recipients depending on the exception type. For example, in Process 3 of the Planning Exception Messages workflow, exception types 13 and 15 are sent at Node 5 after a planner is found. See:Summary of Exception Process 3. To view messages by exception types, select Messages in the navigator tree, and expand the file. A listing of all the messages in the Planning Exception Messages workflow displays in order of the exception type. Select the message, you can see the text of the message in the Description box.

Lookup Types

All of the lookup types can be modified to meet your individual business needs.

Note: If you change a lookup type, you must be sure that all notifications and processes that use the lookup type allow for the change. For example, if you change the lookup type from Yes/No to something else, the activities that use that lookup type should also change their Result Type from Yes/No to whatever new lookup type you created.

Planning Exception Messages Item Type

The Exception Messages process is associated with an item type called Planning Exception Messages, MRPEXPW. This item type identifies all workflow processes available. All exception types are grouped into four workflow processes:

If you examine the property page of Planning Exception Messages, you see that it calls a selector function named MRP_EXP_WF. This selector function is an example PL/SQL stored procedure that returns the name of the process to run when more than one process exists for a given item type.

The Planning Exception Messages workflow item type also has a listing of attributes associated with it. These attributes reference information in the demonstration application tables. The attributes are used and maintained by function activities as well as notification activities throughout the process.

To view descriptions of each item type attribute, select the attribute in the Workflow Builder and choose Properties from the Edit menu. Look in the Description field.

Workflow Planning Exception Messages Workflow Type Attributes

Display Name Description Type
Found/Not Found Message sent to Username of this person. Text
Order Type Type of order for the planning exception - values include work order, purchase requisition, purchase order, or other order type. Number
Proceed/Stop Indicates it the workflow process should continue or terminate -
Reschedule Action Indicates if the order is rescheduled, or not rescheduled Text

Summary of Planning Exception Messages Activities

To view the properties of the Planning Exception Messages processes, select the process in the navigator tree, then choose Properties from the Edit menu. The Planning Exception Messages process has no result type, indicating that when the process completes, it has no defined result corresponding to any lookup type in the navigator tree.

This process activity is runnable, indicating that it can be initiated as a top-level process to run by making calls to the Workflow Engine CreateProcess and StartProcess APIs.

The Details property page of the process activity indicates that the Planning Exception Message Top Process has an error process called DEFAULT_ERROR associated with it, which gets initiated only when an error is encountered in the process. For example, if you attempt to initiate the Planning Exception Message Top Process indicating a planner who is not listed as a valid planner, the Workflow Engine would raise an error when it tries to execute the Select Planner activity. This error would initiate DEFAULT_ERROR, which is associated with the System:Error item type. Currently the process simply executes the standard Default Error Notification activity to provide information associated with the error. You can customize the process further to suit your needs.

Summary of Exception Process 1

The process begins at Node 1.

After your MRP, MPS, or DRP plan has completed its run, the function at Node 2 determines if the workflow process should proceed. If the plan is marked as production, it will proceed. Otherwise, it will continue to Node 3 and terminate.

At Node 4 the process attempts to select a planner based on plan, organization, and item. If a planner is not found, the process ends at Node 5.

If the planner is selected, at Node 6 the workflow process directs the exception message to that person.

When the message is sent, the activity is complete and the process ends at Node 7.

Exception Process 1 Activities

The following is a description of each activity in the Planning Exception Messages Process 1, listed by the activity's display name.

Start (Node 1)

This is a standard function activity that simply marks the start of the subprocess.

Workflow Process Forward (Node 2)

This function activity determines if the workflow process should proceed. If the plan option Production is checked on the MRP, MPS, or DRP Names window; the process continues. If not, it is terminated.

End (Node 3, 5, 7)

This is a standard function activity that marks the end of the process.

Select Planner (Node 4)

This function activity determines the planner who will receives notification based on plan, organization and item. This activity also selects the appropriate message to be sent based on exception type.

Notify Exception (Node 6)

This function activity calls a standard function which allows dynamic selection of messages under one notification activity. The required activity attribute MESSAGE is set to item attribute MESSAGE_NAME which was previously selected in Select Planner node.

Summary of Exception Process 2

The process begins at Node 1.

After your MRP, MPS, or DRP plan has completed its run, the function at Node 2 determines if the workflow process should proceed. If the plan is marked as production, it will proceed. Otherwise, it will continue to Node 3 and terminate.

At Node 4, the order type is determined to see which direction in the process the workflow will branch. If the order type is a value other than work order, purchase order, or purchase requisition; the process ends at Node 5.

If the order is a work order, the process continues to Node 6 and attempts to select a planner. If a planner is not found, the process ends at Node 7.

If the planner is selected, at Node 8 an exception message about the work order is sent. From this point, the planner can reschedule the order, the workflow proceeds to Node 27 for rescheduling procedures, and completes at Node 28. Otherwise, the workflow terminates at Node 9 and the process ends.

At Node 4, if the order is a purchase requisition, the process continues to Node 10 and attempts to select a planner. If a planner is not found, the process attempts to find a buyer at Node 13. Otherwise, the process ends at Node 14.

If a planner is selected, at Node 11 the workflow process directs the exception message to that person. The planner can move the information to the buyer at Node 13, or end the process at Node 12.

If a planner is not found and the buyer is selected at Node 13, the reschedule information is directed to that person at Node 15. If the buyer reschedules the order, the workflow proceeds to Node 27 for rescheduling procedures and completes at Node 28. Otherwise, the process end at Node 16.

At Node 4, if the order is a purchase order, the process continues to Node 17 and attempts to select a planner. If a planner is not found, the process attempts first to find a buyer at Node 20. And if that fails, attempts to find a supplier contact at Node 23. Otherwise, the the process ends at Node 21.

If a planner is selected, at Node 18 the planner can move the exception message to the buyer at Node 20, or end the process at Node 19.

The buyer receives exception information at Node 21, and moves the information to the supplier contact at Node 23. Or the supplier contact can receive the information directly from Node 4. Otherwise, the process ends at Node 24. If the workflow proceeds, at Node 25, the reschedule information is sent to Node 27 for rescheduling procedures and completes at Node 28. Otherwise, the process ends at Node 26.

Exception Process 2 Activities

The following is a description of each activity in the Planning Exception Messages Process 2, listed by the activity's display name.

Workflow Process Forward (Node 2)

This function activity determines if the workflow process should proceed. If the plan option Production is checked on the MRP, MPS, or DRP Names window; the process continues. If not, it is terminated.

End (Node 3, 5, 7, 9, 12, 14, 16, 19, 21, 24, 26, 28)

This is a standard function activity that marks the end of the process.

Determine Order Type (Node 4)

This function determines the order type defined in the current exception, and serves as a branching point. Valid values for order types are work orders, purchase requisitions, purchase order, and others.

Select Planner (Node 6, 10, 17)

This function activity determines the planner who will receives notification based on plan, organization and item. This activity also selects the appropriate message to be sent based on exception type.

Select Buyer (Node 13, 20)

This function activity determines the buyer who will receives notification, based on plan, organization, and item. This activity also selects the appropriate message to be sent based on exception type, thus overriding the message selected in Select Planner function.

Select Supplier Contact (Node 23)

This function activity determines the supplier contact who will receives notification. This activity also selects the appropriate message to be sent based on exception type, thus overriding the message selected in Select Buyer function type.

Notify Exception/Reschedule - Work Order (Node 8)

This function activity calls a standard function which allows dynamic selection of messages under one notification activity. The required activity attribute MESSAGE is set to item attribute MESSAGE_NAME which was previously selected in Select Planner node. Only the messages which contain information related to work orders are selected from this activity. When the notification is reviewed, the recipient responds to it by selecting either Reschedule or Do Not Reschedule.

Notify Exception - Purchase Requisition (Node 11)

This function activity calls a standard function which allows dynamic selection of messages under one notification activity. The required activity attribute MESSAGE is set to item attribute MESSAGE_NAME which was previously selected in Select Planner node. Only the messages which contain information related to purchase requisitions are selected from this activity. When the notification is reviewed, the recipient responds to it by selecting either Proceed or Stop.

Notify Exception/Reschedule - Purchase Requisition (Node 15)

This function activity calls a standard function which allows dynamic selection of messages under one notification activity. The required activity attribute MESSAGE is set to item attribute MESSAGE_NAME which was previously selected in Select Planner node. Only the messages which contain information related to purchase requisitions are selected from this activity. When the notification is reviewed, the recipient responds to it by selecting either Reschedule or Do Not Reschedule.

Notify Exception - Purchase Order (Node 18, 22)

This function activity calls a standard function which allows dynamic selection of messages under one notification activity. The required activity attribute MESSAGE is set to item attribute MESSAGE_NAME which was previously selected in Select Planner node. Only the messages which contain information related to purchase orders are selected from this activity. When the notification is reviewed, the recipient responds to it by selecting either Proceed or Stop.

Notify Exception/Reschedule - Purchase Order (Node 25)

This function activity calls a standard function which allows dynamic selection of messages under one notification activity. The required activity attribute MESSAGE is set to item attribute MESSAGE_NAME which was previously selected in Select Planner node. Only the messages which contain information related to purchase orders are selected from this activity. When the notification is reviewed, the recipient responds to it by selecting either Reschedule or Do Not Reschedule.

Rescheduling Procedure (Node 27)

This function activity performs a rescheduling/cancellation of work order and purchase entities generated by the planning process. For order types Work order and Purchase Requisition, both rescheduling and cancellation can be performed. See: Implementing Planned Orders. For Purchase Orders, only rescheduling is performed by launching an Oracle Purchasing workflow. See: Oracle Purchase Order Approval Workflow: page NO TAG.

Summary of Exception Process 3

The process begins at Node 1.

After your MRP, MPS, or DRP plan has completed its run, the function at Node 2 determines if the workflow process should proceed. If the plan is marked as production, it will proceed. Otherwise, it will continue to Node 3 and terminate.

At Node 4 the process attempts to select a planner based on plan, organization, and item. If a planner is not found, the workflow proceeds first to Node 7 to select a sales representative, and if that fails to Node 9 for a customer contact. Otherwise, it will continue to Node 10 and terminate.

If the planner is selected, at Node 5 the workflow process directs the exception message to that person. The planner has the choice of stopping notification and terminating the process at Node 6. Or proceeding and sending notification to the sales representative at Node 7.

When the sales representative receives exception information at Node 8, the workflow moves the information to the customer contact at Node 9. If a customer contact is found, the message is sent at Node 11 and the activity is complete and the process ends at Node 12. Otherwise, it will continue to Node 10 and terminate.

Exception Process 3 Activities

The following is a description of each activity in the Planning Exception Messages Process 3, listed by the activity's display name.

Start (Node 1)

This is a standard function activity that simply marks the start of the subprocess.

Workflow Process Forward (Node 2)

This function activity determines if the workflow process should proceed. If the plan option Production is checked on the MRP, MPS, or DRP Names window; the process continues. If not, it is terminated.

End (Node 3, 6, 10, 12)

This is a standard function activity that marks the end of the process.

Select Planner (Node 4)

This function activity determines the planner who will receives notification based on plan, organization, and item. This activity also selects the appropriate message to be sent based on exception type.

Notify Exception (Node 5, 8, 11)

This function activity calls a standard function which allows dynamic selection of messages under one notification activity. The required activity attribute MESSAGE is set to item attribute MESSAGE_NAME which was previously selected in Select Planner node.

Select Sales Representative (Node 7)

This function activity determines the sales representative who will receives notification based on plan, organization and item. This activity also selects the appropriate message to be sent based on exception type.

Select Customer Contact (Node 9)

This function activity determines the customer contact who receives notification.

Summary of Exception Process 4

The process begins at Node 1.

After your MRP, MPS, or DRP plan has completed its run, the function at Node 2 determines if the workflow process should proceed. If the plan is marked as production, it will proceed. Otherwise, it will continue to Node 3 and terminate.

At Node 4 the process attempts to select a planner based on plan, organization, and item. If a planner is not found, the workflow proceeds first to Node 6 to select a task/project manager, and if that fails to Node 8 for other recipients. Otherwise, it will continue to Node 9 and terminate.

If the planner is selected, at Node 5 the workflow process directs the exception message to either the task or project manager. If both a task and project manager are found, the notification is only sent to the task manager. At Node 7 the information is passed to Node 8 to determine if more than one task/project manager should receive notification. If another recipient is found at Node 10, the workflow proceeds to Node 12. the message and the activity is complete and the process ends at Node 13. If no other recipient is found, the workflow proceeds directly to Node 13, the activity is complete and the process ends.

Exception Process 4 Activities

The following is a description of each activity in the Planning Exception Messages Process 4, listed by the activity's display name.

Start (Node 1)

This is a standard function activity that simply marks the start of the subprocess.

Workflow Process Forward (Node 2)

This function activity determines if the workflow process should proceed. If the plan option Production is checked on the MRP, MPS, or DRP Names window; the process continues. If not, it is terminated.

End (Node 3, 9, 11, 13)

This is a standard function activity that marks the end of the process.

Select Planner (Node 4)

This function activity determines the planner who will receives notification based on plan, organization and item. This activity also selects the appropriate message to be sent based on exception type.

Notify Exception (Node 5, 7, 12)

This function activity calls a standard function which allows dynamic selection of messages under one notification activity. The required activity attribute MESSAGE is set to item attribute MESSAGE_NAME which was previously selected in Select Planner node.

Select Task/Project Manager (Node 6)

This function activity determines the task manager or the project manager who will receives notification based on plan, organization F - 22 and item. This activity also selects the appropriate message to be sent based on exception type.

Across Projects (Node 6)

This function activity determines if more than one task or project manager should receive notification This activity also selects the appropriate message to be sent based on exception type.

See Also