Académique Documents
Professionnel Documents
Culture Documents
-1-
Table of Contents
INTRODUCTION ..................................................................................................4 SCOPE .................................................................................................................4 FEATURES ..........................................................................................................4 Visibility of the WorkFlow errors to Functional Users.....................................4 Message Status to keep track of the actions....................................................4 Ability to Retry WF activity from the Window...................................................4 Enhanced WF notification ..................................................................................5 Automatic generation of the Diagnostics .........................................................5 SETUP REQUIREMENTS ....................................................................................5 PROFILE OPTION................................................................................................5 EXCEPTION MANAGEMENT FLOW DIAGRAM.................................................6 SIMPLE BUSINESS SCENARIOS .......................................................................6 Flow #1: View Open Messages (Context based) for an Order .......................................6 Flow #2: Find Orders Using Message Status .....................................................................10 Flow #3: Retry the WF Activity in Error From Window ..............................................12 Flow #4: Retry WF activity in Error from Notification.........................................14 Flow #5: Review the Diagnostics: OM Order Information .................................20 Flow #6: Adding New Message Statuses .......................................................................23 Flow #7: Adding the OMERROR Flow to the Customized Activity ..................24 Flow #8: View Transaction Details from WF Notification ..................................25 TROUBLESHOOTING .......................................................................................27 Diagnostics: OM Order Information is not generated .........................................27 Not able to find Diagnostics: OM Order Information for Order .....................27 Not able to open the message window ........................................................................27 Not able to see the option for Retry Activities in Error.......................................28 Not able to access OMERROR WF for the Flow in Error......................................28 TECHNICAL CONSIDERATIONS......................................................................29
-2-
Data Purge Issues .............................................................................................29 Performance Issues ..........................................................................................29 CONCLUSION....................................................................................................30 DEFINITIONS .....................................................................................................31 APPENDIX .........................................................................................................32 Appendix 1: ..................................................................................................................................32
Figure 1: Open Message check box is checked .......................................................................................................7 Figure 2: Right Click mouse and select View Open Messages....................................................................................8 Figure 3: Message Window with an open message ..................................................................................................9 Figure 3.1: Note to indicate no open message ......................................................................................................10 Figure 4: Select Open message status to query the orders with open messages ................................................................11 Figure 5: Orders with open messages .................................................................................................................12 Figure 6: Use right mouse button and select Retry Activities in Error........................................................................13 Figure 7: Select the Activity in Error to retry ......................................................................................................14 Figure 8: Select Workflow Administrator Web Applications Responsibility................................................................15 Figure 9: Select Find Notification....................................................................................................................16 Figure 10: Query on notification of type OM Error. You can use the Order Number in the subject with percent sign(%) as it is part of the subject.........................................................................................................................................17 Figure 11: The query shows the notification. .......................................................................................................18 Figure 12: View the transaction details in notification. Use the Retry button to retry the WF activity. ...............................19 Figure 13: OMERROR WF. .......................................................................................................................20 Figure 13: Note to display the Diagnostics reports request ID. ...............................................................................21 Figure 14: Notification contains the request ID for the Diagnostics report...................................................................22 Figure 15: Message for the Order line in Diagnostics report. ...................................................................................23 Figure 16: Adding new message Status. ............................................................................................................24 Figure 17: OM ERROR flow. ......................................................................................................................25 Figure 18: Assigning OMERROR flow to an activity. .........................................................................................25 Figure 19: Notification contains the request ID for the Diagnostics report...................................................................26 Figure 20: Order Information from notification ...................................................................................................27
-3-
INTRODUCTION
With Exception Management feature, you can view and take action on the errors occurring in a particular workflow (WF) activity. You can use Sales Orders, Order Organizer, Quick Sales Orders and the Quick Order Organizer for this feature. You can view the errors related to the Order header or Order Line by using the new action View Open Messages, available from both the right mouse click and Action button. You can open the Message window and check the status of the Message for that order header/line. You can take action on these messages and close them. After taking the action for the messages, you can use the Retry Activities in Error function available in mentioned order windows (available via the right mouse click and the Action button) as well as workflow notifications to retry the activity.
SCOPE
This document provides you with details of the major features, the setup required and the dataflow diagram. Later sections provide troubleshooting steps.
-4-
After correction of the issues recorded in the Message Framework, you can Retry the WF activity. Retry is also available in Sales Orders window/Organizer and Quick Sales Orders window/Organizer. Retry action closes all the previous open messages for the activity. This is a protected function, please contact you system administrator for access.
Enhanced WF notification
You can see the following functional information related to a sales order in WF notification.. Order Number Order Type Line Number Shipment Number Sales Rep Operating Unit Version Number Flow Status You can use this information to identify the order or line flow in error. You will also have the link to the Transaction Detail of the Order Information Portal.
SETUP REQUIREMENTS
You should be on release 11.5.9 of the application or OM family Pack I. Apply Patch 3731146 to obtain Exception Management functionality. You should get the privilege to access Retry Activities in Error. Contact your system administrator for the privilege.
PROFILE OPTION
OM: Generate Diagnostics for Error Activities This new OM Profile Option OM: Generate Diagnostics for Error Activities is introduced to control the automatic generation of Diagnostics: OM Order Information concurrent request whenever the activity is in error. The system administrator should set it at the site level. It has two settings. 1. 2. No: Means, No Automatic generation of the Diagnostic report. Yes: Means, Automatic generation of the Diagnostic report.
-5-
This existing OM Profile Option OM: Show Process Messages Flag is used to indicate if the system should display the Open Message checkbox or not. Set the profile value to Yes, to use the indicator message_exists_flag . The checked value of this field indicates that at least one message exists for the order.
Is WF activity in Error?
NO Cool! Proceed Further. Retry Activity from Sales Orders window or WF notification.
SIMPLE BUSINESS SCENARIOS Flow #1: View Open Messages (Context based) for an Order
You can use the Sales Orders/Quick Sales Orders window to see the messages associated with that order header or line. 1. 2. 3. Query the Order for which you want to see the Open Messages. Click the right mouse button or Action button. Select View Open Messages. It will open the Messages window if there are open messages associated with that context e.g. if you are on the Line tab and your cursor is at Line# 1, it will show you messages associated with that line only. If there is no message, in that case a note is shown to indicate that there is no message associated instead of Message window
Query an Existing Order Go to Line Tab Mouse/Click Right Mouse or Action button Select View Open Messages Message window open Or No message associated info. should be displayed.
-6-
-7-
-8-
-9-
If you have added new codes for the message status, you can use them in query too. Please check the flow for Adding New Message Status for more details.
- 10 -
Figure 4: Select Open message status to query the orders with open messages
- 11 -
- 12 -
Figure 6: Use right mouse button and select Retry Activities in Error
- 13 -
- 14 -
- 15 -
- 16 -
Figure 10: Query on notification of type OM Error. You can use the Order Number in the subject with percent sign(%) as it is part of the subject.
- 17 -
- 18 -
Figure 12: View the transaction details in notification. Use the Retry button to retry the WF activity.
- 19 -
b. Find the message, which has information of the concurrent request ID.
- 20 -
3.
Using Flow #4, you can obtain the request ID of the Diagnostics report.
- 21 -
Figure 14: Notification contains the request ID for the Diagnostics report.
- 22 -
- 23 -
2.
3. 4. 5. 6.
- 24 -
To modify the activity to use this error flow, then open the activity in the WF builder and put OMERROR as the Error Item Type. Save the workflow. The workflow that started after the changed WF is loaded will use this error flow.
- 25 -
Open WF notification
Figure 19: Notification contains the request ID for the Diagnostics report.
- 26 -
- 27 -
- 28 -
Performance Issues
- 29 -
CONCLUSION
The Oracle Order Management Exception Management feature provides context based message handling and WF retry capability. Using this feature, you can query, review and take action to resolve the error associated with the order header and line. You can retry the error activity from window and notification after the correction of the errors. The ability to automatically launch the Diagnostics: OM Order Information report; gives you the flexibility to get order information as soon as an error happens. You can later review this report and send it to support if requested during a TAR resolution.
- 30 -
DEFINITIONS
WF Flow Workflow Process Workflow SubProcess Retry Activities v/s Progress Order Workflow A Flow is what the application starts for an order or line. A flow starts using a specific workflow process. A workflow process is made of workflow activities and/or workflow sub-processes. A workflow process should be runnable as defined in the workflow builder. A Workflow sub-process is made of workflow activities and/or more workflow subprocesses. A workflow sub-process is not runnable, which means that you cannot start a flow using it. The Retry Activities in Error action is different from the existing Progress Order action. The existing Order Management workflow processes contain eligible states for most activities (e.g. Schedule Eligible, Invoice Interface Eligible). If such an activity fails due to an expected error, the workflow goes to the eligible state and the user can manually select the Progress Order action after taking corrective steps. However, the new Retry Activities in Error allows the user to retry a particular activity when the workflow itself is in an error state due to an unexpected error. In other words, Progress Order applies to activities in the eligible state whereas Retry Activities in Error refers to activities that are in an error state.
- 31 -
APPENDIX Appendix 1:
- 32 -
Oracle Order Managment Exception Management August 2004 Author: Alok K Singh Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 Web: www.oracle.com This document is provided for informational purposes only and the information herein is subject to change without notice. Please report any errors herein to Oracle Corporation. Oracle Corporation does not provide any warranties covering and specifically disclaims any liability in connection with this document. Oracle is a registered trademark, and Oracle Order Management (are) a trademark(s) or registered trademark(s) of Oracle corporation. All other names may be trademarks of their respective owners. Copyright Oracle Corporation 2000 All Rights Reserved
- 33 -