Routing tables form the basis for the automatic selection of a 'route' for a specific business object.

A routing table consists of a set of objects of type Routing table entry, that may or may not be considered 'applicable' in a specific data context depending on Association criteria.

Each entry in a routing table defines criteria that must be met in order for a particular route to be assigned – if necessary, in conjunction with additional value assignments for attributes of the business object.

A route is a directional connection between two 'areas' (from/to), whereby the affiliation to an area is derived from the characteristics 'country' and 'postal code' of selected company or address attributes of the business object.

In the routing table entry, either one-sided (from or to) or two-sided (from and to) criteria can be defined which always sets a certain range for the postal code (string comparison from/to) for precisely one 'country'. The routing table entry links these criteria with the freely selectable name of the route. Several routing table entries can also refer to the same route, for example, if this route is to apply to several unrelated postal code areas.

The determination of the route for a business object must be triggered by event handling with the event action Routing: Determine route.

More details:

Overview

images/download/attachments/51151445/image2020-3-17_14-28-57-version-1-modificationdate-1584451739475-api-v2.png

The basic relationships when determining routes are shown schematically here:

A business object contains specifications for the 'Consignor' (CNR, company attribute) and 'Consignee' (CNE, address attribute), which are used to determine the route via event handling.
In the 'applicable routing table' on the right, a 'matching routing table entry' for the country/zip details is identified from the addresses provided.
The name of the route is adopted from the routing table entry in a text attribute of the business object.
In addition, values for some route attributes (company attribute 'Forwarder', numerical attributes 'transit time' and 'cost factor') are adopted in the business object.