Fusion Distributed Order Orchestration Overview

October 10, 2010 in Fusion Distributed Order Orchestration

Fusion Distributed Order Orchestration

Distributed Order Orchestration (DOO) is one of the new module that oracle consider as part of Fusion Applications suite. Fusion Applications is a new version Oracle ERP that is considered as migration path for Oracle Apps, JD Edwards, Siebel and other e-business applications oracle acquired over the last few years.

Often every business have multiple order entry systems to capture orders that goes through multiple ERP systems. Businesses spend considerable IT efforts to build complex interfaces. Oracle Distribution Order Orchestration provides consolidated order capture system that receives orders from multiple sources and routes it to multiple manufacturing plants/systems through flexible business rules.

Complex Order fulfillment without DOO:

Order Orchestration without Fusion DOO

Order Orchestration without Fusion DOO



Simplified Order fulfillment with DOO:

Order Orchestration with Fusion DOO

Order Orchestration with Fusion DOO

DOO features:

  • Decomposition:
  • Rules workbench that can decompose one sales order into multiple sales orders across different  fulfillment (ERP/Manufacturing systems).
  • Manage order changes
  • Provides consolidated order status

  • Orchestration:
  • Business Process Management (BPM) Administration
  • Managing order related tasks and execution (installation, notifications etc)
  • Simulation order changes and cost implications.
  • Integration:
  • Global order Promising by out of the box integration with GOP module. GOP provides sourcing rules and promise dates
  • Integration with oracle fulfillment modules
  • AIA integration

Oracle Distributed Warehouse Management System Overview

October 3, 2010 in Oracle Distributed Warehouse Management System

Oracle Distributed WMS is a new module released in R12 that can support the WMS features in a stand alone system. This architecture is similar to Oracle Advanced Supply Chain Planning system where APS can be implemented as a separate instance. Distributed WMS can also be implemented as separate instance that will collect the data from ERP system and feed the inventory back to ERP system. Distributed WMS can be integrated with non-Oracle ERP systems.

Distributed WMS will be of tremendous help for a customers who need 24 x 7 availability of WMS systems. WMS can still process transactions while ERP system is down. Apart from this it also comes with Light weight Purchasing & Light weight Order Management that supports basic features of OM & PO modules without implementing them fully.

Distributed WMS inbound data collections from ERP:

  • Advanced Shipment Notices (ASN)
  • Purchase Orders
  • Items
  • Customers
  • Suppliers
  • Shipment Requests

Distributed WMS outbound data collections to ERP:

  • PO Receipts
  • Onhand quantities
  • Inventory Adjustments
  • Ship Confirmation

Oracle Rapid Planning Overview

September 28, 2010 in Oracle Rapid Planning

Oracle Rapid Planning Module is a new addition to Oracle Value Chain Planning suite (a.k.a Oracle APS – Advanced Planning and Scheduling).

Oracle Rapid Planning key features

  • Rapid simulations / alternatives
  • Multiple planners can work concurrently on the same plan
  • Compares the plans / alternatives and recommends best alternative
  • Integrated with other Oracle value chain applications & Demantra

Main differentiation between Oracle Rapid Planning and Oracle Advanced Supply Chain Planning is time it takes to simulate changes. Using Rapid Planning you can simulate any changes and run plan to see recommendations without lengthy data collections.

Scenarios supported:

Hot demand:

Any emergency / rush order is considered as hot demand. Whenever hot demand orders are received, the order information is manually entered in Rapid planning plan and planning recommendations can be reviewed and released by planners.

Engineering change cut-in:

Any ECO changes that results new items introduced or existing items phased out, we can update the same information in entered rapid planning server, plan is run to review/release the recommendations

Yield Bust:

When their is production change that would affect the potential onhand, it is considered as yield bust.

Resource downtime:

Resource downtime information can be entered in plan to do simulations on the supply/demand changes.