Completing shipping order data

If a shipping order is created manually or automatically, it goes through a data aggregation process that creates a Data Transfer Object (DTO). The DTO is then forwarded to the Carrier Connect web service.

The data aggregation process essentially consists of three steps:

  1. AEB default population
  2. Determination of functional values based on configurable rules or mapping tables (see Configuring rules for delivery and shipment)
  3. BAdI extension implementation

After these components have populated the DTO in the AEB add-on for SAP, it is transferred to the Carrier Connect web service interface. There, a shipping order is generated from the DTO.

The interface description "Interface description Carrier Cloud for SAP" represents the DTO: It provides information whether there is an AEB standard population for the respective field or not. You can download the document in the download area of the AEB Service Portal.

If some values are not determined by the AEB standard logic, you can implement your own logic for determining these values via BAdI.

Some functional values must be converted because either the carriers themselves or Carrier Connect use alternative values for standardization that differ from the host system. An example is the spelling of pc. vs. PC.

For details, see the section Maintaining master data in Carrier Connect.