ERP sites and zones

For managers and administrators: choose which customer, branch, or depot records of your SoftOne, Entersoft, SAP Business One, or SAP S/4HANA Cloud ERP become zones on the fleet map, and keep them current. Part of the documentation.

Choose the site source
Map the columns
Zone settings
Sync
Sites without coordinates
Rules

Choose the site source

Open Organization → ERP and select the connection. The Workflow panel holds all settings on this page. Click Save workflow after a change. The next sync uses the new settings.

SoftOne. Filodos reads one browser. Type the object (default CUSTOMER). Optional: a browser list name and filters, for example CUSTOMER.ISACTIVE=1. Use the filters to read only the delivery customers.
Entersoft. Filodos reads one Public Query. Type its group (for example ESGOPerson) and its filter id. Optional: parameters, one Name=Value for each line. Your Entersoft partner makes the Public Query in the Scroller Designer.
SAP Business One. Filodos reads one entity of the Service Layer. Type the entity (default BusinessPartners) and an OData filter (default CardType eq 'cCustomer'). See Sites from SAP.
SAP S/4HANA Cloud. Filodos reads one entity of the tenant OData API. Type the entity (default A_BusinessPartner) and an OData filter (default BusinessPartnerCategory eq '2'). See Sites from S/4HANA.
CSV file. Filodos reads the uploaded file — no ERP login. Set the delimiter and map the columns to the file headers. See Import sites from a CSV file.

A sync refuses more than 5000 sites. Use a filter or a narrower Public Query for large customer lists.

Map the columns

Type the ERP column for each value. Each installation has its own column names. Ask your partner for them. For a CSV file, type the file header for each value instead.

Value	SoftOne default	Entersoft default	SAP default	S/4HANA default	CSV default	Note
Record key	empty: the record key of the browser row	`GID`	`CardCode`	`BusinessPartner`	`key`	Required for Entersoft, SAP, and CSV. Visit notes use it to find the record.
Code	`CUSTOMER.CODE`	`Code`	`CardCode`	`BusinessPartner`	`code`	Shown before the name of the zone.
Name	`CUSTOMER.NAME`	`Description`	`CardName`	`BusinessPartnerFullName`	`name`	Required.
Address, City, Postal code	`CUSTOMER.ADDRESS`, `CUSTOMER.CITY`, `CUSTOMER.ZIP`	`Address1`, `City`, `ZipCode`	`Address`, `City`, `ZipCode`	`StreetName`, `CityName`, `PostalCode`	`address`, `city`, `zip`	Shown as the zone description.
Latitude, Longitude	empty	empty	empty (user-defined fields, for example `U_Latitude`)	empty (customer-specific fields, for example `YY1_Latitude`)	`latitude`, `longitude`	Set both or neither. A decimal comma (`37,9838`) is accepted.

Without coordinate columns, every site waits for a location. See Sites without coordinates.

Zone settings

Zone type: Customer, Depot, or No-go. The map colors the zone by type.
Radius: 25 to 5000 meters (default 150). Each ERP site becomes a circle with this radius.
Link every vehicle: on by default. The fleet reports zone arrivals and departures only for linked vehicles. Keep it on if you want visit notes.

Sync

Click Sync sites now in the Connection panel.
Read the answer: how many sites are new, changed, unchanged, waiting for a location, and gone from the ERP, and how many zones Filodos wrote.
Open the Sites panel to see each site and its state.

Filodos also syncs automatically every 6 hours. The connection list shows the time of the last sync. A failed sync shows its reason there. A CSV connection never syncs on its own: upload a new file instead (see Import sites from a CSV file).

Sites without coordinates

A site without valid coordinates gets no zone. It waits in the Need a location tab of the Sites panel.

Open the Need a location tab.
Find the coordinates of the site, for example from a map application.
Type the latitude and the longitude in the row. Example: 37.9838 and 23.7275.
Click Set. The zone appears on the map.

A location that you set holds while the ERP has no coordinates for the site. When the ERP gets valid coordinates, the ERP coordinates replace it. The value 0, 0 counts as no coordinates.

Rules

A sync never deletes a zone. A site that leaves the ERP moves to the Gone from the ERP tab, and its zone stays. Delete the zone on the Geofences page if you do not need it.
A changed name, code, address, or position in the ERP updates the zone at the next sync.
Each zone carries the ERP record key. The zone and the ERP record stay linked when the name changes.
A site that comes back into the ERP becomes active again.