Document Distribution Schema

The document distribution schema is the model of the document distribution which consists of document distribution schema steps. Each distribution step within a schema can have an individual description (which is displayed in the end user UI) and is linked to a distribution type. You can define the same distribution type several times within a schema using different distribution step IDs.

Within the distribution schema, the execution sequence of the different distribution steps can be defined using the Step Sequence field. You can also define dependencies between distribution steps using the Prerequisite Step field. The distribution step then is only executed if the distribution step with the distribution step sequence defined in the Prerequisite Step field have all been executed completely. This can be used to branch the distribution process and merge it later.

Distribution steps can be marked as inactive to enable the deactivation of distribution steps for a certain time period or for testing purposes. If the distribution step is marked as inactive, it is ignored at runtime. If the step is used as a prerequisite step for another distribution step, this step is also ignored.

If the assigned distribution type of a distribution step is defined as an asynchronous (batch) step, the Asynchronous field is also marked at distribution step level and the field is disabled. You cannot mark a distribution step as synchronous if the corresponding distribution type is already marked for asynchronous execution. Nevertheless, you can mark a distribution step as asynchronous if its distribution step type is marked for synchronous execution. With this mechanism, distribution types can be registered for batch processing for certain distribution schemas only.

The distribution schema contains all existing distribution steps for a document item. The current execution of the single distribution steps can be controlled using the distribution category implementation class or the distribution schema implementation class. For example, you can exclude some steps depending on the document status and reschedule them later when the document status has changed. The implementation class for the document distribution schema is used to implement logic similar to the distribution category but for the whole distribution schema. This means you can set a document status that is dependent on all distribution steps, or influence the distribution in addition to the distribution type or category implementations.

Standard Schema

The standard schema for the provider contract is PERP. It contains the categories and steps that replicate the provider contract to SAP ERP. For more information, see Distribution of Data to SAP ERP.