As explained before, the Logisticbus Interface in Autoline will create an export file with parts movements over a certain period of time. It is possible to run the Logisticbus interface manually or set it up to run in the End of Day routine. Below the running in manual mode is explained.
To enter the Logisticbus Interface, you must:
The grid on the Transmission procedure tab displays all Stock Management companies for which a Logisticbus parameter file is set up. If the Transmit column of a Stock Company is ticked, it is possible to create a Logisticbus Export file for that Stock Management Company.
To run the Logisticbus Interface manually, you must:
If a dealer is using the Logisticbus Interface for the first time, an initial load file is created. In this case the Date selection from is displayed after the Start transmission procedure icon is selected.
The Date selection form enables users to enter a start date from which all parts movements in Autoline are transmitted.
Note: Be aware that parts movements are present if a dealer is using (selling and purchasing parts) the Autoline system. These file are not converted in case a dealer has just started using Autoline. In that case you can still the start date but if no movements are present, they cannot be exported in the Logisticbus Interface file.
By default the Start date is set one-year back, a user is able to change this manually. If this program is running in the End of Day routine, the default calculated date is taken as start date.
In case an initial file is created, all parts movements from the Start date are translated to Logisticbus codes, for all parts a STL record is created (more stock information) and for all parts a BES record is created (contains stock quantities).
Every file is started with a header record; this is the
Ones a year a Synchronisation file is created. This synchronisation file contains above the parts movements for all parts a STL record is created (more stock information) and for all parts a BES record is created (contains stock quantities).
The program keeps track of when the synchronisation file must be send with help of the parameter, which contains the date the last time a synchronisation file is sent.
A synchronisation file starts with the header. The daily parts movements, are written below the header. After that a
Because this file is a synchronisation file, the
A 'normal' Logisticbus file contains the parts movements from the period between the previous time the interface was run and the moment the interface is run again.
If changes are made on the stock record, STL records are written for that particular part.
Also are BES records created for parts with movements, if the nonstock flag of a part changes and in case of changes in the reserved stock of a part.