1. A computer system comprising: one or more processors; a non-transitory memory in data communication with said processor, said memory storing distributed order orchestration software functional layers comprising computer readable instructions which when executed by said processor perform the steps of: receiving process definitions, process configuration information and metadata from a web-based administration environment, with processes defined in business terms and configured to be executed at runtime as executable processes, with process configuration information including a sequence of services on a data table and where defined processes are executable and reusable; utilizing a task functional layer configured to receive, analyze, and provide encapsulated services used to control processing logic for orchestration software functional layers by wrapping specific business logic around a selected request to associate specific logical tasks with the selected request; utilizing a decomposition functional layer configured to capture a sales order, analyze parameters of the sales order to determine which orchestration process to apply to the sales order with respect to a customer associated with the sales order and use transformation processes to transform the captured sales order, in a form of a source data object, received from one of a plurality of order capture systems, with the plurality of order capture systems generating source data objects having different data formats, to a generic source order object being a generic data structure, based on a canonical data model, for internal processing by distributed order orchestration software thereby making the distributed order orchestration software agnostic to the different data formats of the source data objects and converting, in accordance with business rules, the functional attributes of one or more products included in the generic source order object into a plurality of purchase orders, where the business rules are applied to generate a first purchase order for a product and a second purchase order to a supply-side partner for a second product, specified by the business rules, necessary for fulfillment of captured sales order, each of which is in a purchase order format; utilizing an orchestration layer to provide external task functionality to support creation, update, release and monitoring of external tasks carried out by fulfillment systems; utilizing a task functional layer to generate and send an internally formatted goods and/or services message including specific business logic wrapped around a selected request to associate specific logical tasks with the selected request and metadata; and utilizing an external interface functional layer configured to receive, analyze, and translate a first request included in a first internally formatted goods and/or services message received from the task functional layer into a first external message having a first external format utilized by a first external fulfillment system of a plurality of external fulfillment systems to provide flexible routing to route the first request to the first external fulfillment system, where metadata is used to route the first external message and to determine the first external format, wherein the first external format includes one or more common signatures used to invoke one or more services provide by the external fulfillment system, wherein the one or more common signatures define a data structure for reuse of the one or more services in a plurality of different business processes, and wherein the one or more services include configurable services and non-configurable services which include different input arguments formulated for different services used in different executable processes, wherein the input arguments are formatted such that a service can read different sets of data and invoke the one or more services.