Oracle Fusion: Order Orchestration
What is Distributed Order Orchestration?
- DOO is Oracle Fusion’s Order Management Module.
- DOO is a system to manage orders from multiple “Order Capture” and “Order Fulfillment” systems.
- DOO provides visibility to the status of all the orders and highlights’ orders requiring attention based on predefined business rules.
- DOO has the capability to reorganize and reprioratize deliveries based on “Global Order Promising” information to optimize resource utilization.
- DOO is not an order capture system.
Oracle Fusion Features
- There are no forms in Fusion. Everything in jsp based.
- There are no underlying tables. Fusion tries to leverage the SOA architecture and works on “objects”.
- There is ‘UPK’ integrated in Fusion.
Pre-requisites for DOO
- Define the enterprise structure and enable security features
- Define Product Model – This ensures that items are synchronized between the external system and DOO.
- Define Customer Model – This ensures that the customer information is synchronized between the external system and DOO.
Features of DOO
- DOO allows you to capture the Order information in one system and fulfill it in another.
- Different Lines on the order could be fulfilled in different systems.
- Allows you to process change orders. An additional feature here is the ability to quantify the change using the “Cost of Change” feature and then decide weather to go ahead with the change or not.
- Has the feature to highlight “jeopardy” orders. Jeopardy is a feature which tells the users that certain milestones in the order will not be met. The criteria for setting this up is business driven and can be configured.
- Provides you a dashboard view of the orders. This eliminated the need for running a lot of reports.
- Can be used to define Processing Constraints and Holds.
Key Components of DOO
- Functional Setup Manager – Used to implement all Oracle Fusion Application Suite.
- Common Application Configuration – Accessing tasks that are available in multiple offerings e.g. security and enterprise structures
- Common Order Orchestration Configuration – Define Product Model and Customer Model
- Sales Order Fulfillment – Manage source system and define the mappings.
- Transformation Details
- Orchestration process
- Processing Constraints
- Hold Codes
- Global Order Promising – Used to provide the best scheduling option for the order
- Collect Order Promising Reference and Transaction Data
- Manage Order Promising Rules
- Provides single window to all orders across multiple systems.
- Allows you to change the deliveries based on business needs and availability.
- Can be implemented without any impact on the existing systems.
- Provides a user friendly look and feel.
- Will be required only by companies which have multiple order entry and fulfillment systems.
- If there is an existing ERP in place, there might be a case to evaluate the cost benefit of implementing DOO vs migrating other systems to the existing ERP. Implementing DOO could lead to remodeling the existing ERP system.
- No integration with Oracle EBS. If EBS is one of the order capture and order fulfillment system in the scheme of things, we can’t integrate it seamlessly with DOO.
- No provision yet for loading bulk data (something similar to a data loader).
- There will always be the risk of maintaining multiple systems.