1. Implementing Order Management
  2. Collect Planning Data for Order Management

Collect Planning Data for Order Management

You collect planning data so you can select the data that you need during set up. You can collect planning data for organizations, items, structures, routings, suppliers, transit times, and so on.

Assume you create a new item, the AS54888, and you must add the AS54888 to the Item attribute in your Sourcing Rule, but how do you get the AS54888 to show up in the pick list that you use when you set the Item attribute? You must collect it first.

Try it.

  1. Do your setups in various work areas. For example:

    Work Area

    Description

    Product Information Management

    • Use the Manage Items task and Create Item Structure task to set up the AS54888 item.

    • Use the Manage Catalogs task to set up catalogs for the AS54888.

    Setup and Maintenance

    • Use the Manage Units of Measure task to set up the units of measure you need for the AS54888.

    • Use the Create Workday Pattern task and the Create Work Schedule task to set up calendar data for the AS54888.

    Work Definition

    Use the Manage Work Definitions task to set up the work definitions that manufacturing will use to build the AS54888.

  2. Go to the Plan Inputs work area, then click Tasks > Collect Planning Data.

    • You use the Collect Planning Data task to collect the set ups you made in step 1. This task makes the objects that you set up available to other Oracle Applications.

    • Don't use the Plan Inputs task that's available in the Setup and Maintenance work area. Use the Plan Inputs work area instead.

  3. In the Collect Planning Data dialog, set the values.

    Attribute

    Value

    Source System

    Select the source system that your implementation uses for planning, such as OPS (Oracle Order Orchestration and Planning).

    If you're not sure, here's how you identify the source system that your implementation uses.

    1. In the Setup and Maintenance work area, go to the task.

      • Offering: Order Management

      • Functional Area: Orders

      • Task: Manage Upstream and Fulfillment Source Systems

    2. On the Manage Upstream and Fulfillment Source Systems page, in the Destination System area, notice that you can use a destination system where the Enable for Oracle Fusion Distributed Order Orchestration option contains a check mark.

    3. In the Source Systems area, notice that the Collect Planning Data dialog gets values for the Source System attribute from source systems where the Order Orchestration attribute contains Order Orchestration.

    Collection Type

    Set a value.

    • Targeted. Delete all data in the repository for the entities that you select, collect new data for these entities, then save it in the repository.

    • Net Change. Collect data in increments, and collect only changed or new data. This choice is faster than using Targeted. Use Net Change when you already performed a targeted collection and now must keep your planning data current with data in your run time environment.

    • Automatic Selection. Let the server decide.

    Templates are available, such as Static Data for Supply Planning. For this example, to help you learn how it works, do the steps instead so you can more clearly visualize the flow.

  4. On the Reference Data tab, move entities from the Supply Entities list to the Selected Entities list.

    Select the entities you need. Here are the entities that you typically collect for an Order Management implementation.

    • Calendars

    • Currencies

    • Items

    • Item Structures

    • Order Orchestration Reference Objects

    • Organizations

    • Sub Inventories

    • Units Of Measure

    For the complete list, see Overview of Collecting Promising Data for Order Management.

  5. Optional. Click Schedule, then set a schedule to collect automatically.

    You might need to collect some entities periodically. For example, the conversion rate between currencies, such as the Euro and the Dollar, might change each day. If you sell in markets that use different currencies, and if you don't use a currency conversion list, then you might need to collect the Currencies entity one time each day so Order Management can use the current conversion rate.

  6. Click Submit.

    The Plan Inputs work area automatically starts the Collection Job Set scheduled process.

  7. In the Status dialog, note the process number. For this example, assume its 50465.

  8. Go to the Scheduled Processes work area.

  9. Locate the value 50465 in the Process ID column. Monitor the process until the Status column displays Succeeded.

    Collection Job Set might automatically start other scheduled processes, such as Extract Oracle Fusion Entity. You can examine the log for Collection Job Set to monitor them too. For example, here's the log for a Collection Job Set that finished successfully.

    Is Attribute Based Planning Enabled = 1
Is User Defined Attribute Based Planning Enabled = 1
The Extract Oracle Fusion Entity process started for entity ITEM_ORGS with refresh number 262023.
The Extract Oracle Fusion Entity process processed the following number of records: 1319.

  10. Use Oracle Applications to continue your set up.

    For example, use the Create Assignment Set task in the Global Order Promising work area to specify the AS54888 item that you set up in the Product Information Management work area.

Related Topics