Best Practices For Custom Order Entry Workflow Design
By gaurav.verma on Mar 12, 2007
Every organization's way of doing business is unique and this prompts customers to extend the seeded Oracle supplied order management workflow definition.
Unfortunately, there is a lack of authoritative documents on following best practices for workflow customization. In the absence of such documents, customization practices vary and become person dependent.
A recently published Note 402144.1 -- FAQ: Best Practices For Custom Order Entry Workflow Design can help you change all that. As the name suggests, it enumerates best practices which can help you manage your workflow design risks well ahead in advance.
Some example FAQs answered are:
Question 6: How is an infinite loop situation created for FNDWFBG concurrent program?
Question 7: How can we avoid Infinite loop situations while executing workflow activities in the background?
Related suggested readings..
- Note 312535.1 - Oracle Order Management Workflow Validation
The experience has been that extensions and customizations sometimes lead to imperfect and faulty workflow designs that cause problems, errors, and even data corruption which is not readily apparent and can only be corrected by data fix scripts provided by Oracle Support or, even more often, Oracle Development.
To help OM customers evaluate and validate their proposed workflow extensions and customizations before they are used in order processing, Development is introducing functionality called "OM Workflow Validation".