Shipment has started

The carrier picks up the shipment that was created in the previous. Now we want that our order as well as our shipment reflect the new status.

To do so, we send an event to the shipment, the event then propagates to the corresponding order event, because of our master data configuration. See Master Data.

receiveTrackingEvent

{
  "metaData": {
    "senderID": "SwabCloth_ERP",
    "receiverClient": "SwabCloth",
    "receiverRole": "SUPPLIER",
    "senderRole": "SUPPLIER",
    "sendDate": {
      "dateInTimezone": "2020-10-10 17:04:20",
      "timezone": "Europe/Berlin"
    },
    "messageReferenceNumber": "ERP_2851408",
    "updateMode": "STANDARD",
    "idRefScheme": "SUPPLIER"
  },
  "head": {
    "identCode": "Shipped",
    "actualDate": {
      "dateInTimezone": "2020-10-10 17:04:20",
      "timezone": "Europe/Berlin"
    },
    "actualLocation": {
      "city": "Ludwigsburg",
      "countryISOCode": "DE",
      "postcodeStreet": "71634",
      "timezone": "Europe/Berlin",
      "globLocationNo": "SW_CLOTH_1"
    },
    "actualSender": {
      "globalLocationNumber": "SW_CLOTH",
      "name": "Swabian Clothes"
    }
  },
  "references": [
    {
      "trackingObjectType": "CONS",
      "referenceFields": [
        {
          "referenceField": "CONS_NO",
          "referenceNumber": "ERP_2851406_1"
        }
      ]
    }
  ]
}

Result

Order Status

Shipment Status

Track & Trace App

Shipments can also be viewed in the mobile friendly Track & Trace Webapp, which is reachable by adding /track-and-trace to the end of the engine url.

Explanations

references

trackingObjectType: Here we enter CONS for consignment, because we want to update the shipment.
referenceFields.referenceField: We want to send the event to the shipment with the provided number.