An InputDispatcher job takes many tasks. First, all documents and interchange documents must be extracted from the entities and stored in original state for security reasons. Furthermore, the receipt of the documents has to be noted in the eBiss database. The EntityAnalyzer takes these tasks as the first jobstep of the job The next step is to distinguish the incoming documents using EntitySelector according to their type and to carry out corresponding processing steps.

Normally, a data base is created for a partner in the eBiss database. The information about the articles for the data base comes from a PRICAT document For this purpose, an EntitySelector (Selector to TradeItemDocuments) was installed in this job, which extracts PRICAT documents. The EntityLoader loads all the necessary documents for further processing into the main memory. In order for the articles to be written to the eBiss database by the TradeItemManager, they must first be converted to a processable format. The EntityTransformer (Transform to TradeItemDocument) applies the rules in the mapping documents, which are specified in the properties of the EntityTransformer, and converts the documents. The TradeItemManager further processes the converted documents, extracts the articles and their properties, and writes them as data bases in the eBiss database. In order for the document not to be processed once more, it is necessary to assign the status “processed” to the document. For this purpose an EntityStatusSetter was installed parallel to the TradeItemManager.

This job example should also consider OrderResponse and DespatchAdvice documents for processing. The next branch in the InputDispatcher job handles all OrderResponse documents. These are to be extracted from documents and compared with the data base, which was previously created by a PRICAT document in the eBiss database, for further processing (inventory numbers, etc.). In the rain, the processing is carried out by external systems (merchandisers, etc.). All OrderResponse documents are selected with the EntitySelector (Selector to Retail.OrderResonse). The selected entities are loaded into the memory by the EntityLoader. The EntityTransformer (Transform to Retail.OrderResponse) converts this into the Format Retail.OrderResponse document for further processing by means of rules in the mapping documents which are entered in the properties of the EntityTransformer. The conversion allows a later reconciliation of the items contained in the document with the eBiss database and the updating of the document in the eBiss database. These tasks are processed in another job. The EventRouter (Route to Import.OrderResponse) forwards the documents to this job (Import.OrderResponse).

This branch is analogous to the one described above, and thus performs the same processing steps, but it extracts and processes the DespatchAdvice documents instead of the OrderResponse.