How Order-to-Cash Works with Order Capture Systems

Use an order capture system that resides outside of Order Management, such as Oracle Configure, Price and Quote Cloud, to send a source order to Order Management.

For the most part, Order Management uses the order-to-cash flow. For details, see How Order-to-Cash Works in Order Management. Note these important differences.

1. An order capture system that resides outside of Order Management captures a source order. For example, a user might use your legacy application to enter a source order.

2. You set up a that the capture system can use to send the source order to Order Management. If the source system and Order Management use different domain values, then the connector transforms the structure and values from the domain that the source system uses to the domain that Order Management uses.

   For details, see Integrate Order Management with Source Systems.

3. Supply Chain Planning collects data about the source order, then uses it to create cross-references and planning data.

   Use a cross-reference help to manage the representation of data across systems. A cross-reference relates business data between your order capture system, order fulfillment system, and Order Management. For example, an item cross-reference can create a relationship between an item, such as Widget x, that resides in your source system, and a representation of Widget x in Order Management.

   You can cross-reference across warehouses, units of measure, carriers, currencies, shipping methods, payment terms, accounting rules, invoicing rules, service levels, tax classification codes, and so on.

4. An orchestration process references business rules to transform each source order into a sales order that Order Management can understand and fulfill.

5. Order Promising gets item details from Product Information Management, customer details from Trading Community Architecture, and planning data from Supply Chain Planning to promise the sales order.

6. Order Management uses the order-to-cash flow to continue processing.

Note

• Order Management updates the order status, fulfillment line status, and invoice status during the flow, and communicates each update to your order capture system.

• Order Management can use an order capture service to communicate updates to the source system. To receive these updates, the source system must subscribe to the events. If Order Management receives an update from the source system, then it replans the orchestration process. It replans every time it receives an update.

• Here are the attributes that Order Management uses to calculate the planned dates for each step and task, starting with the first step it does in chronological order.

  • Default Lead Time

  • Lead Time UOM

  • Lead-Time Expression

• Order Management doesn't do the same amount of transformation for a sales order that a user creates in the Order Management work area because these orders already include the data and use the structure that Order Management requires.

• A single source order might contain order lines that include one-time charges, and other order lines that include recurring charges. If Order Management receives a source order that includes a recurring charge, then Oracle Receivables creates a recurring billing invoice for these lines.

• Order import typically uses the same flow that this topic describes, except you import source orders from a spreadsheet or through a web service.