Update Fulfillment Date According to Completion Step

Update the fulfillment date according to the step that you specify as the fulfillment completion step in your orchestration process.

Get more flexibility in how you use the fulfillment date in your implementation.

You might have specific requirements to calculate the invoice date according to the fulfillment date, or to send the fulfillment date to one of your downstream systems.  

For example, tie the dates to when:

  • Your customer actually receives delivery.
  • A pause step in your orchestration process finishes according to the completion date.
  • A subscription begins and ends.
  • An asset's life begins and ends.

Steps to Enable

Try it:

  1. Open your orchestration process for editing, then set up a step.

    To Set the Fulfillment Date To

    You Set Up

    Delivery date

    The SAC_SYSTEM_EVENT_POD_PAUSE event on a pause step in your orchestration process.

    Use this event to set your invoice date according to the delivery date.See Overview of Pausing Orchestration Processes.

    Completion date

    One of these events on your pause step:

    • SAC_SYSTEM_EVENT_IPC_PAUSE
    • SAC_TYPE_TIMER
    • SAC_TYPE_EVENT

    Completion date for a subscription

    The task type on a step to DOO_Subscription.

    Order Management will set the fulfillment date only for each subscription that's eligible. It won't set the date for any shippable item that's associated with the subscription. Assume you buy the Glorious Bouquet shippable item and it comes with a one year subscription to Better Flowers magazine. Order Management will set the fulfillment date for the bouquet but not for the magazine.

    See Overview of Integrating Order Management with Subscription Management.

    Completion date for an asset

    The task type on a step to DOO_AssetManagement.

    See Track Items as Assets in Order Management.
  2. Enable the step as the fulfillment completion step.
  3. Set the ORA_FOM_SET_FULFILLMENT_DATE administrator profile to Y. See Use Order Profiles to Control Order Management Behavior.

Tips And Considerations

Use different pause events for different purposes.

Event

Example

SAC_SYSTEM_EVENT_IPC_PAUSE

Use an interprocess communication (IPC) to pause according to an event across orchestration processes.

You want to use the same fulfillment date for an order line that you ship and a line that you don't ship, and then invoice them together.

For example, use the same fulfillment date for the Glorious Bouquet item that you ship and a one month subscription to the online Better Flowers magazine that you don't ship, and then invoice them at the same time on the same invoice.

SAC_TYPE_TIMER

Pause the orchestration process until the date and time that you specify happens.

Pause all order lines until 1:00 PM.

When the current time is after 1:00 PM, release the pause and set the fulfillment date to the step's completion date.

SAC_TYPE_EVENT

Pause the orchestration process until an event happens.

You want to use the same fulfillment date for an order line that you ship and a line that you don't ship, invoice them together, but you need to control when to send the lines to invoicing. For example, you need to manually release them or use a web service or scheduled process to release them.

The fulfilled quantity will be the shipped quantity or the ordered quantity according to the quantity that's available when the step finishes. Shipped quantity takes precedence over ordered quantity.

Key Resources

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

  • Manage Orchestration Process Definition (DOO_MANAGE_ORCHESTRATION_PROCESS_DEFINITION_PRIV)

These privileges were available prior to this update.