Orchestration fulfillment patterns can have dependencies across functions and products or orchestration product specifications.
Dependencies can exist between different functions for an orchestration fulfillment pattern and can be based on completion. For example, the Billing function can be started only after the Provisioning function completes, and the SyncCustomer function, Collections function, and Marketing function can be started only after the Billing function completes. Orchestration fulfillment patterns can have dependencies between order components within the corresponding fulfillment pattern or between order components on other fulfillment patterns. For example, the fulfillment pattern determines to which order component an order item must be added.
Dependencies Across Products or Orchestration Product Specifications
Fulfillment patterns can have dependencies across many conceptual model products or OSM orchestration product specifications. For example, different sales products can be added to the same conceptual model product or OSM orchestration product specification, which can map to the same fulfillment pattern.