Table of Contents

Addresses

Address master data contains all the essential information about delivery, shipping, and business locations in the WMS system. This includes standard Business Central address functionality plus WMS-specific fields for warehouse operations.

In this article

To create an address manually

  1. Select Search (Alt+Q) in the upper-right corner, enter Addresses, then choose the related link.
  2. Choose the New action.
  3. In the No. field, enter a number for the address.
  4. Fill in the remaining fields as required. Hover over a field to read a short description.

WMS-Specific Fields

In addition to standard Business Central address fields, the WMS module includes several warehouse-specific fields. The following are the most important WMS fields that you should be aware of:

Address Types & Classification

Important for system functionality - These fields determine how the address is used in warehouse processes. Make sure to review and fill in the appropriate address types as needed.

Warehouse & Logistics

Important for warehouse operations - These fields affect warehouse layout and operations. Review these fields to ensure proper warehouse configuration.

Geographic & Coordinates

Important for route planning - These fields are used for mapping and route optimization. Fill in coordinates for better route planning.

Forwarding & Customs

Important for international shipping - These fields are required for customs and forwarding. Review these fields for international operations.

Operational

Important for scheduling - These fields affect delivery scheduling and requirements. Configure these fields based on your operational needs.

Add an address to a route

Addresses that are delivered on a fixed schedule are planned through routes: a route consists of route lines, one per address, and Calculate Trip Plan turns those lines into trips. You can link an address to a route directly from the Address card, without opening the route first.

Routes and trips on the Address card

The General FastTab of the Address card shows in how many routes and trips the address is used:

  • No. of Routes - the number of routes that contain a route line for this address.
  • No. of Trips - the number of trips that contain this address, within the date filter when one is set.

Both fields are hidden by default. Add them to the card with Personalize if you want to see them.

To add an address to a route

  1. Open the address on the Address card.
  2. Choose Functions > Add to Route.
  3. In the Route List, select the route and choose OK. Blocked routes are not offered. Choose Cancel to stop; no route line is created.
  4. 3PL Dynamics adds a new route line at the bottom of the route with the address in Address No., and fills Area Code and Description from the address. The Recurring System of the new line is copied from the last line of the route; on a route that has no lines yet, it stays empty.
  5. The message Address added to Route <code>. Check Recurring System and Route Day/Date on the new line before calculating the trip plan. is shown and the Route card opens.
  6. On the new line in Route Lines, check the Recurring System and fill in Day or Date. Then choose Calculate Trip Plan to include the address in the trips of the route.
Note

The action only adds the route line. Complete the line before you calculate the trip plan: a route line without a Recurring System and Day or Date cannot be planned.

TODO(verify): confirm what Calculate Trip Plan does with a route line whose Recurring System is still empty - does it stop with an error on that line, or does it skip the line and create no trips for it? The review of the change describes both.

Resource Availability

Resource Availability calculates when a resource, currently a WMS Address, becomes available again after one or more planned absences. The calculation uses working days and a calendar. The result can be used to select a scan layout based on the resource's availability on a specific date.

Entity Short Description
Resource Absence (table 73310576) Stores an absence period for a resource. Each entry is linked to a resource entity by its type and System ID. The starting date is required; the ending date can be left empty for an open-ended absence. A reason code is optional.
Resource Availability Cache (table 73310577) Stores the calculated availability for a resource: its status, next available date, number of working days until availability, calendar code and last calculation date/time. This is a calculated cache, not the source of the absence data.
Resource Entity Type Identifies the type of resource to which an absence or cache entry belongs. The current implementation includes WMS Address and the enum can be extended.
WMS Calendar Determines which dates count as working days when calculating the next available date and the number of days until availability.

Resource Absence

Create a Resource Absence entry for each period during which a resource is unavailable. The entry contains:

  • Resource Entity Type and Source System ID to identify the resource.
  • Starting Date and Ending Date to define the absence period.
  • Reason Code as optional supporting information.

The starting date cannot be after the ending date, and the ending date cannot be before the starting date. Leave the ending date empty for an open-ended absence.

When an absence is inserted, modified or deleted, the system recalculates the resource's availability using the system defaults. The default threshold is 7 working days.

Resource Availability Cache

The cache contains one calculated record per resource entity type and System ID. Its status is one of the following:

Status Meaning
Available The resource is available on the evaluation date.
Leave Within Threshold The resource becomes available again within the configured number of working days.
Leave After Threshold The resource becomes available after the threshold, or has an open-ended absence.

Next Available Date is the next working day on which the resource is available again. Days Until Available is calculated in working days. For an open-ended absence, the status is Leave After Threshold and no next available date is stored.

The Resource Availability page on the WMS Address shows the cached result. The cache can also be recalculated with the CALC RESOURCE AVAIL function set.

Function Set: CALC RESOURCE AVAIL

Use this function set to calculate and store resource availability.

Parameter Description
SCOPE 0 calculates the resource represented by the source record. 1 recalculates all known resources, or the resources selected by the table filter.
THRESHOLD Number of working days used to distinguish Leave Within Threshold from Leave After Threshold. The default is 7.
CALENDAR CODE Working-day calendar used for the calculation.
ENTITYTABLENO Table number for the entity table filter. The default is 11191181, WMS Address.
TABLE FILTER Optional filter on the resource entity table when SCOPE is 1.

With SCOPE = 1 and no table filter, the function recalculates resources that have an absence entry or an existing cache entry. With a table filter, it calculates the matching resource records. With SCOPE = 0, the source record must be a supported resource entity.

Scan Function 81: Get Resource Layout on Date

Scan Function 81 evaluates a WMS Address's availability for a target date and returns a layout code. It uses the resource's absence entries and does not read or update the persistent availability cache.

Parameter Description
1 - ADDRESSNO Required WMS Address number.
2 - DATE Optional evaluation date. If empty, the Work Date is used.
3 - THRESHOLD Optional threshold in working days. If zero or empty, 7 is used.
4 - CALENDAR CODE Optional working-day calendar.
5 - LAYOUT AVAILABLE Layout returned when the resource is available on the evaluation date.
6 - LAYOUT WITHIN Layout returned when the resource becomes available within the threshold.
7 - LAYOUT AFTER Layout returned when the resource becomes available after the threshold or has an open-ended absence.
10 - LAYOUT Return value containing the selected layout code.

This scan function is useful when the layout must be selected dynamically for a particular evaluation date. Use CALC RESOURCE AVAIL when the persistent cache must be refreshed.

Note

Set the calendar explicitly when weekends or non-working days must be excluded. The function-set parameter description says an empty calendar uses the base calendar, while the current helper treats an empty calendar code as every day being a working day. Verify the intended configuration for your environment.

Resource Absences via RCV-ADDRESS

Add one ResourceAbsence element for each absence period inside the relevant Address. The address number links each absence to the address. You do not need to send an entry number or resource System ID; the import derives these from the address.

Element Required Description
StartingDate Yes First day of the absence.
EndingDate No Last day of the absence. Leave empty for an open-ended absence.
ReasonCode No Reason for the absence. The code must exist in WMS Reason Codes.

The import matches an existing absence by address and starting date. If a match is found, it updates the ending date and reason code; otherwise, it creates a new absence. Sending an absence with a different starting date creates a separate entry.

Absences comitted from a later message are not deleted. To remove an existing absence, delete it through the appropriate resource-absence maintenance process.

<?xml version="1.0" encoding="UTF-8"?>
<ns0:Message xmlns:ns0="www.boltrics.nl/address:v1.00">
  <ns0:Header>
    <ns0:MessageID>3</ns0:MessageID>
    <ns0:CreationDateTime>2026-07-30 13:09:43.203</ns0:CreationDateTime>
    <ns0:ProcesAction>INSERT</ns0:ProcesAction>
    <ns0:FromTradingPartner>SLS</ns0:FromTradingPartner>
    <ns0:ToTradingPartner>SLS</ns0:ToTradingPartner>
  </ns0:Header>
  <ns0:Addresses>
    <ns0:Address>
      <ns0:No>C55555</ns0:No>
      <ns0:ResourceAbsences>
        <ns0:ResourceAbsence>
          <ns0:StartingDate>2026-08-19</ns0:StartingDate>
          <ns0:EndingDate>2026-08-21</ns0:EndingDate>
          <ns0:ReasonCode>ITEMJRNL</ns0:ReasonCode>
        </ns0:ResourceAbsence>
        <ns0:ResourceAbsence>
          <ns0:StartingDate>2026-09-01</ns0:StartingDate>
          <ns0:EndingDate>2026-09-01</ns0:EndingDate>
          <ns0:ReasonCode>ITEMJRNL</ns0:ReasonCode>
        </ns0:ResourceAbsence>
      </ns0:ResourceAbsences>
    </ns0:Address>
  </ns0:Addresses>
</ns0:Message>