In this scenario, when the hub receives a new purchase order from the ordering application, the GUID of the XLANG schedule is extracted and stored in the CustomCorrelation database along with the PO number as a TransactionID. When the supplier receives the purchase order and activates an XLANG schedule of its own, the GUID of the supplier's XLANG schedule is stored along with the invoice number as the TransactionID. The supplier system stores this pair of values in its own SupplierCustomCorrelation database. These initial correlation values are used to associate the remaining incoming and outgoing documents to the correct running XLANG schedule instance as the transaction progresses until the XLANG schedule completes.
Previous Next |