1. Modeling OSM Orchestration
  2. Working with Fulfillment State Maps
  3. About Configuring Fulfillment States

About Configuring Fulfillment States

Fulfillment state maps are a key part of configuring fulfillment states. The fulfillment state management configuration consists of the following:

  1. External fulfillment states: External fulfillment states relate to the status information sent to OSM by fulfillment systems. An external fulfillment state defined on one order component is available on that component and on any order component that extends that order component. The external fulfillment state is an input to the fulfillment state mappings. See "Order Component Specification Editor External Fulfillment States Tab" for more information.

  2. Fulfillment State Maps: This entity provides the normalization of the external system's states into mapped fulfillment states. This is also where common fulfillment states are created. See "About Fulfillment State Maps" for more information.

  3. Order Item Fulfillment State Composition Rule Sets: This entity provides the composition of these mapped fulfillment states into composite fulfillment states reflecting fulfillment states for order items. See "About Order Item Fulfillment State Composition Rule Sets" for more information.

  4. Order Fulfillment State Composition Rule Sets: This entity provides the same function as the Order Item Fulfillment State Composition Rule Sets, but at the order level instead of the order-item level. See "About Order Fulfillment State Composition Rule Sets" for more information.

Note:

If you are adding fulfillment state processing to cartridges that were created in a pre-7.2 version of OSM, you also need to add data elements to the Data Dictionary for fulfillment state. See the discussion of modeling order template structures for fulfillment states in the OSM Developer's Guide.

In addition to providing order item and order fulfillment state information to upstream systems, fulfillment states may also be used to restrict processing of order amendments from the upstream system. This is done using the point of no return processing in the orchestration fulfillment pattern. See "About Points of No Return" for more information.