Show TOC

Component documentationOrchestration Framework

 

In certain scenarios, deliveries or goods movements occur prior to an order having been generated (unplanned scenarios), or require mirroring of existing documents (intercompany scenarios). In these cases, many documents may need to be created to ensure that a full document trail exists for the quantity moved. These documents may be generated manually, but a level of automatic generation is required to support timeliness and to reduce manual intervention.

The Orchestration Framework (OF) is a tool that automates the logistics process. A configurable framework governed by business rules, the Orchestration Framework is used to determine the business scenarios in question. On event completion, the OF is called. Using information derived from the Load Data Capture (LDC) screen, the nomination screen, or the Manual Application Workcenter screen, the OF validates the quantities involved and determines the applicable scenario. It then calls the stack of services configured for that scenario to create logistical documents, as well as the application document that is used for settling payment with the vendor or customer. If the document postings fail, the Recovery Report retriggers the process. Note that the OF is run as a background processing engine. There is no user interface.

Integration

  • Load Data Capture is the front-end to the OF. The OF determines logistical documents for each application instructions defined during LDC. On event release, the OF reads the application instruction defined for an LDC and determines various possible scenarios.

  • The OF supports 3rd Party Purchase, 3rd Party Sales, Back-to-Back, Inter/Intra Company Sales, and Returns scenarios.

  • The OF uses standard TSW ticketing functionality to create downstream documents. The TSW ticket type identifies from which application or source (LDC, nomination, or application document) a ticket originates or is created.

Features

  • Orchestration Execution

    Based on the data in the LDC screen, the OF determines the business scenario type, transaction type, title transfer, and whether a new vendor is required.

  • Orchestration Determination

    During execution, the OF oversees the creation of follow-on documents, determines the material, and updates the LDC status.

  • Recovery Report

    If a service stack fails at any point, the recovery report reprocesses the follow-on stack and completes the document postings.