Business Central Integration
In general, integration between Lagersystem and Business Central (BC) can happen in two ways. It can either be done using the Lagersystem extension or via OData alone. The integration with Lagersystem offers the same functionality with both solutions. The advantage of using the Lagersystem extension is that it doesn't require custom development, and that the system will be faster.
The details of the two options are described below.
Integration via the Lagersystem extension
This solution requires a standard BC Cloud platform version 17 and runtime version 7.1. If you're unsure whether you have this version of BC, you can ask your BC consultant.
Hint: if you log in at businesscentral.com or businesscentral.dynamics.com, you have a Microsoft-hosted version, which will be kept updated to the correct version.
The latest version of the Lagersystem extension can be downloaded from releases.lagersystem.dk/business-central-integration.
Processing sales orders
This method is used if orders are not partially delivered, but the entire sales order is sent at once. This method is often used for web sales.
- Sales orders from BC are automatically imported into Lagersystem once the order is released. Must be done manually or automated via a job queue entry
- Posting of sales orders in BC happens automatically
Processing picks
This method is used if orders are partially delivered.
- Creation of picks in BC must be done manually or automated via a job queue entry
- Posting of picks in BC happens automatically once the order has been dispatched at the warehouse
- Option to have the sales order posted automatically in BC once all lines have been delivered
Processing purchase orders
This method is used if a purchase is completed and posted as a goods receipt.
- Purchase orders from BC are automatically imported into Lagersystem once the order is released. Must be done manually or automated via a job queue entry
- Posting of purchase orders in BC happens automatically once the order has been received at the warehouse and is ready for posting
Processing put-away
This method is used if purchase orders are partially received.
- Creation of put-away in BC must be done manually or automated via a job queue entry
- Posting of put-away in BC happens automatically once the order has been dispatched at the warehouse and is ready for invoicing. Lines that have not been received at the warehouse are automatically transferred to a new put-away
- Option to have the purchase order posted automatically in BC once all lines have been delivered
See here for guidance on Installing the Lagersystem Extension
Integration via OData
This solution can be used for older versions of BC and Microsoft Dynamics NAV. OData has been implemented since NAV 2013 (7.0), including all versions of Business Central, which is why Lagersystem can be integrated from this version onward. In some older versions of NAV, it may be necessary to install a backport FOB, which can be provided by Lagersystem.
This method requires setup in BC, which must be carried out by a BC consultant.
Note: it is important to ensure that all the necessary OData endpoints are available in BC. Check this together with your BC consultant.
Processing sales orders
This method is used if orders are not partially delivered, but the entire sales order is sent at once. This method is often used for web sales.
For this function to work via OData, the following must be handled in BC:
- Sales orders are automatically imported into Lagersystem once the order is released. Must be done manually or automated via a job queue entry.
- Posting of sales orders in BC must be done manually or automated via a job queue entry. Lagersystem adds track and trace information in the "External Document No." and "Quantity Shipped" fields on the sales order in BC once the order has been dispatched at the warehouse and is ready for invoicing
Processing picks
This method is used if orders are partially delivered.
For this function to work via OData, the following must be handled in BC:
- Creation of picks in BC must be done manually or automated via a job queue entry
- Posting of picks in BC must be done manually or automated via a job queue entry. Lagersystem adds track and trace information in the "External Document No." field on the pick order in BC once the order has been dispatched at the warehouse and is ready for invoicing
- Posting of the sales order in BC must be done manually or automated via a job queue entry
Processing purchase orders
This method is used if a purchase is completed and posted as a goods receipt.
- Purchase orders from BC are automatically imported into Lagersystem once the order is released. Must be done manually or automated via a job queue entry
- Posting of purchase orders in BC must be done manually or automated via a job queue entry. Lagersystem adds the date and time of receipt, e.g. "LS:2020-02-02 10:00:00", in the "Vendor Shipment No." and "Quantity Received" fields on the purchase order in BC once the order has been received at the warehouse and is ready for invoicing
Processing put-away
This method is used if purchase orders are partially received.
- Creation of put-away in BC must be done manually or automated via a job queue entry
- Posting of put-away in BC must be done manually or automated via a job queue entry. Lagersystem adds the date and time of receipt, e.g. "LS:2020-02-02 10:00:00", in the "External Document No." and "Quantity Received" fields on the purchase order in BC once the order has been received at the warehouse and is ready for invoicing
- Posting of the purchase order in BC once all lines have been received must be done manually or automated via a job queue entry