EDX - Warehouse Management System Integration#

General#

The EDX AddOn WMS provides a basic WMS (Warehouse Management System) interface.

With the WMS interface, logistics companies can be connected to Microsoft Dynamics Business Central™.

The message exchange is bidirectional. This means that goods receipts/issues can be reported to the logistics company and confirmations processed accordingly in Microsoft Dynamics Business Central™. Inventory reconciliation is possible via the invtur message.

The EDX WMS intermediate documents can be retrieved via the user search with the term "WMS".

Requirements EDX version#

EDX19 .0.17051.0
EDX WMS 19..016994.0

Establishment#

EDX Setup Wizard#

After the app installation, the setup is performed with the EDX setup wizard. This setup wizard can be called up via the EDX Setup menu ribbon ("More options" > "Action" > "Setup" > "EDX setup wizard"). The EDX setup wizard is started. Via the selection "General" the required document types as well as number series are created. see EDX manual chapter "EDX setup wizard".

EDX Setup WMS#

In the WMS info tab, the following parameters can be set for the interface:

EDX Partner#

An EDX partner must be created for the data exchange between BC and the logistics company. The EDX partner is created e.g. of the type "Contact". Within this documentation the EDX partner "WMS" is used.

EDX Document types#

The following EDX documents are assigned to the previously created EDX partner:

KUMAVISION Inhouse Format#

GS1 Warehousing Messages (Subset Raben)#

The following GS1 messages may differ from the original GS1 messages, as they contain adaptations for the logistics company RABEN!

After the test phase is completed, all EDX documents should be set to automatic processing.

Storage location#

The EDX partner set up must be entered in the associated storage location. Within this documentation, the EDX partner "WMS" is assigned to the storage location "YELLOW". Hereby, goods receipts as well as goods issues for the storage location "YELLOW" are reported to the logistics company "WMS".

The selected storage location should have the following options:

In the storage location the creditor, which corresponds to the logistics company, can be stored. In the field "Our account number" of the vendor, the customer number assigned by the logistics company must be entered.

Logistics facility#

For posting goods receipt/goods issue, it is necessary to change the goods receipt/goods issue posting method in the "Logistics setup" to "Cancel and show first posting error".

If the posting method is set to "Posting errors are not processed" and an error occurs during posting, then it will not be registered by EDX and all related interface records will get the status "NAV document created" even though no posting has taken place.

Goods issue from BC to WMS (Outbound Instruction)#

General#

Excerpt from Microsoft Dynamics Business Central™ Helpsite (F1):
[...] If you ship items from a storage location that has been set up to require goods issue processing, you can only record goods issue based on origin documents that other departments in your company have approved for processing.

Normally, the employee who is responsible for the delivery creates a goods issue. The following procedure describes how to create the shipment manually in the standard version of Business Central.

• Select the icon , enter goods issues, and then select the associated link.
• Select the New action. Fill in the fields on the General info tab. When retrieving the origin document rows, some of the information is copied to each row.
• Select the Get origin documents action. The Origin documents page opens. From a new or open goods issue, you can use the Filter to get origin document lines that define which items are to be delivered. [...]

Procedure User/EDX#

After entering the storage location code "YELLOW" in the General info tab, the fields in the EDX info tab are initialized.

The following conditions must be met for automatic EDX document dispatch:

The following origin documents are supported by the EDX WMS interface:

• Sell orders
• Outgoing stock transfers
• Purchasing complaints
• Service orders

After the goods issue has been released, the message is sent to the logistics company. If the document "WMS WHSE SHIPMENT EXP" is not configured for automatic processing, then the goods issue can be sent manually with the action "Send EDX goods issue".

When sending messages, one message is created in the EDX outbox for each origin document/origin number. The created EDX output can be retrieved with the action Line->EDX->Output.

In another transaction, the outgoing item is transferred.

Serial number/batches#

The serial numbers/batches are reported back by the logistics company. An entry in the goods issue is generally not required. If serial numbers or batches are recorded in the goods issue, then these are reported to the logistics company.

Assembly of the final article in the logistics company#

If the assembly of the final article takes place in the WMS, then the article BOM can be sent to the logistics company using the WMS interface.

The BOM is exported if the "Send article BOM" checkbox is activated in the EDX setup and the current article has an assembly or production BOM.

Proforma delivery bill / invoice#

Within the interface PDF files can be transmitted as base64 encoded characters. The transmission is currently only possible for sales orders.

For the transmission, the switch "Include the associated PDF document" must be activated in the EDX document facility (WMS WHSE SHIPMENT EXP). In the "Report selection sales" the reports to be transferred must be marked with the switch "Use for WMS".

Storage location / storage place#

When using the KUMAVISION QM App, position locations are used. The WMS interface reports the goods issue storage bin to the logistics company.

WMS order number / transport number#

The order number and transport number used by the logistics company are displayed in the EDX info register.

Send goods issue from BC to WMS again#

If it is necessary to send a goods issue to the WMS again, this can be done with the actions "Reset EDX status". If the document "WMS WHSE SHIPMENT EXP" is not configured for automatic processing, then the goods issue can be sent manually with the action "Send EDX goods issue".

Exclude goods issue from transmission#

In some cases, the created goods issue may not be sent to the WMS. This is the case, for example, if the goods issue was created for internal processing purposes only.

For this purpose, the status of the goods issue must be set to "Open". Then the switch "External WMS" in the EDX info register can be set to "Off". When switching over, the following query is displayed:

"When releasing the goods issue, there is no transfer to the external WMS. Are you sure?"

Assembly order#

If an assembly order exists for the goods issue line, then the components of the assembly order are transferred to the logistics company with the "Outbound Instruction" message. The transfer is made according to the following conditions:

• EDX setupThe "Transfer parts list" configuration switch must be switched on.
• Sales lines

The sales line in the goods issue must be linked to an assembly order.

Goods issue status from WMS to BC (Outbound State Notification)#

General#

With the message "WMS WHSE SHIPMENT STATUS IMP" the status confirmations are processed by the logistics company.

The message can be processed with the WMS intermediate document "WMS Goods issue status".

Currently, the following status confirmations are available:

WMS Intermediate document#

Check action#

The following tests are performed:

Update action#

The confirmed status is transferred to the goods issue line.

Outgoing goods#

The reported WMS processing status is displayed in the goods issue line with the "WMS Status" field.

Goods issue from WMS to BC (outbound notification)#

General#

With the message "WMS WHSE SHIPMENT IMP" the deliveries are processed by the logistics company.

The message can be processed with the WMS intermediate document "WMS Goods issue".

Procedure User/EDX#

The following diagram shows the automatic sequence of message processing.

Prerequisite EDX occupancy device:

• Automatic processing is enabled.
• BC Release document is enabled.
• BC Post document is activated. The posting date should be set to "Receipt document date". In this case the posting date will be used by the logistics company.

WMS Intermediate document#

Serial number/batches#

The serial numbers/batches assigned by the logistics company can be retrieved using the "Item tracking" action within the rows.

Assembly order#

If the logistics company performs the assembly of the finished article, then the components used by the logistics company can be retrieved with the action "Bill of material" within the lines.

Packing material#

The packing materials used by the logistics company can be retrieved with the action "Packing materials" within the lines. The overview contains the SSCC/NVE and the respective package tracking number.

Packing list#

With the packing list, the returned packing materials are displayed in hierarchical form. For this representation, the logistics company must report back which packaging material is contained in which packaging material.

If outer packaging is used for several origin documents, it is sufficient to report the outer packaging when it is first used. For the subsequent origin documents, only the corresponding outer packaging is referred to (Contained in SSCC/NVE).

Example:

Storage location / storage place#

When using the KUMAVISION QM App, position locations are used.

The storage bin reported back by the logistics company is not processed. Within the interface it is assumed that the storage bin specified in the goods issue corresponds to the delivery storage bin.

Check action#

The following tests are performed:

Action booking#

• The posting date of the logistics document is set according to the document setup.
• WMS order number / transport number is transferred to the logistics document.
• Quantity to be delivered is transferred to logistics document line.
• Serial number/batches are transferred to the origin document.
• Goods issue is posted if this is set in the document facility.
• Packing materials are transferred to the booked sales delivery.

Outgoing goods#

WMS order number / transport number#

The order number and transport number used by the logistics company are displayed in the EDX info register.

Goods receipt from BC to WMS (Inbound Instruction)#

General#

Excerpt from Microsoft Dynamics Business Central™ Helpsite (F1):
[...] When items arrive at a warehouse set up for goods receipt processing, you must retrieve the rows of the released origin document that triggered their goods receipt. If you are using storage bins, you can either accept the default bin entered or, if the item has never been used in this warehouse before, enter the bin into which the item is to be placed. You must then enter the quantities of the items you have received and post the goods receipt.

The following explains how items are received with an order. The steps for sales complaints and stock transfer orders are similar.

• Select the icon , enter goods receipts, and then select the associated link.
• Select the New action.
  Fill in the fields on the General info tab. When retrieving the origin document lines, some of the information is copied to each line.
  For warehouse configurations with controlled putaway and picking: if the storage location has a default zone and a default bin for goods receipts, the Zone code and Bin code fields are filled in automatically, but you can change them if necessary.
• Select the Get origin documents action. The Origin documents page opens. From a new or open goods receipt, you can use the Filter to get origin document lines that define which items are to be received or delivered.
  a) Select the Use filters to fetch Herc. documents action.
  b) To set up a new filter, enter a descriptive code in the Code field and click Edit Actions.
  c) Specify the type of origin document rows you want to retrieve by filling in the respective filter fields.
  d) Select the Execute action.[...]

Procedure User/EDX#

After entering the storage location code "YELLOW" in the General info tab, the fields in the EDX info tab are initialized.

The following conditions must be met for automatic EDX document dispatch:

The following origin documents are supported by the EDX WMS interface:

• Purchase orders (not external work)
• Incoming stock transfers
• Sales complaints

After the goods receipt has been released, the message is sent to the logistics company. If the document "WMS WHSE RECEIPT EXP" is not configured for automatic processing, then the goods receipt can be sent manually with the action "Send EDX goods receipt".

When sending messages, one message is created in the EDX outbox for each origin document/origin number. The created EDX output can be retrieved with the action Line->EDX->Output.

In another transaction, the outgoing item is transferred.

Serial number/batches#

The serial numbers/batches are reported back by the logistics company. An entry in the goods receipt is generally not required.

Storage location / storage place#

When using the KUMAVISION QM App, position locations are used. The WMS interface reports the goods receipt storage bin to the logistics company.

Send goods receipt from BC to WMS again#

If it is necessary to send a goods receipt to the WMS again, then this can be done with the actions "Reset EDX status". If the document "WMS WHSE RECEIPT EXP" is not configured for automatic processing, then the goods receipt can be sent manually with the action "Send EDX goods receipt".

Exclude goods receipt from transmission#

In some cases, the created goods receipt may not be sent to the WMS. This is the case, for example, if the goods receipt was created for internal processing purposes only.

For this purpose, the status of the goods receipt must be set to "Open". Then the switch "External WMS" in the EDX info register can be set to "Off". When switching over, the following query is displayed:

"When the goods receipt is released, there is no transmission to the external WMS. Are you sure?"

Goods receipt from WMS to BC (inbound notification)#

General#

With the message "WMS WHSE RECEIPT IMP" the goods receipts are processed by the logistics company.

The message can be processed with the EDX intermediate document "WMS Goods receipt".

Procedure User/EDX#

The following diagram shows the automatic sequence of message processing. Prerequisite EDX occupancy device:

• Automatic processing is enabled.
• BC Release document is enabled.
• BC Post document is activated. he posting date should be set to "Receipt document date". In this case the posting date will be used by the logistics company.

WMS Intermediate document#

Serial number/batches#

The serial numbers/batches assigned by the logistics company can be retrieved using the "Item tracking" action within the rows.

Packing material#

The packing materials used by the logistics company can be retrieved with the action "Packing materials" within the lines. The overview contains the SSCC/NVE and the respective package tracking number.

Packing list#

With the packing list, the returned packing materials are displayed in hierarchical form. For this representation, the logistics company must report back which packaging material is contained in which packaging material.

If outer packaging is used for several origin documents, it is sufficient to report the outer packaging when it is first used. For the subsequent origin documents, only the corresponding outer packaging is referred to (Contained in SSCC/NVE).

Example:

Storage location / storage place#

When using the KUMAVISION QM App, position locations are used. The storage bin reported back by the logistics company is not processed. Within the interface it is assumed that the storage bin specified in the goods receipt corresponds to the delivery storage bin.

Check action#

The following tests are performed:

Action booking#

• The posting date of the logistics document is set according to the document setup.
• WMS order number / transport number is transferred to the logistics document.
• Quantity delivered is transferred to logistics document line.
• Serial number/batches are transferred to the origin document.
• Goods receipt is posted if this is set in the document facility.
• Packing materials are transferred to the booked sales delivery.

Goods receipt#

WMS order number / transport number#

The order number and transport number used by the logistics company are displayed in the EDX info register.

Stock from WMS to BC (Inventory Notification)#

General#

The message can be processed with the EDX intermediate document "WMS Stock".

Excerpt from Microsoft Dynamics Business Central™ Helpsite (F1):
[...] You can perform an inventory of items using the Inventory Order and Inventory Capture documents. The Inventory Order page is used to organize the complete inventory collection project, for example, one per location. The Inventory Capture page is used to communicate and record the actual count of items. You can create multiple records for one order, for example, distributing groups of items to different employees.

The Inventory Capture report can be printed from any capture and contains blank quantity fields for entering counted inventory. When a user is finished capturing and the quantities have been entered on the Inventory Capture page, select the Finish action. This will transfer the quantities to the appropriate rows on the Inventory Order page. This feature ensures that no item count can be entered twice.[...]

Procedure User/EDX#

The following diagram shows the automatic sequence of message processing.

Prerequisite EDX occupancy device:

• Automatic processing is enabled.
• BC Release document is enabled.
• BC Post document is activated. The posting date should be set to "Receipt document date". In this case the posting date will be used by the logistics company.

Confirmation of the article stock for all storage bins#

WMS Intermediate document#

Serial number/batches#

The serial numbers/batches assigned by the logistics company are displayed directly in the line.

Check action#

The following tests are performed:

Action booking#

• Creating an inventory order
• The posting date of the inventory order is set according to the document setup.
• Create inventory record for all items
• Inventory order is posted if this is set in the document setup.

GS1 Application Receipt Acknowledgement#

General#

With the message "GS1 Application Receipt Acknowledgement" a receipt confirmation can be transmitted back to the message sender. The receipt acknowledgement can be used bidirectionally.

Example:
Message from WMS to BC
WMS sends the stock level.
BC sends the acknowledgement of receipt after receiving the stock

Example:
Message from BC to WMS
BC sends the goods issue.
WMS sends the acknowledgement of receipt after receipt of the goods issue

Establishment#

As described in chapter „EDX Documemt Types“, the message "GS1 APP REC ACK EXP" must be assigned to the WMS partner. Then the option "Receipt Acknowledgement" is activated in the document setup.

Guideline for GS1 Application Receipt Acknowledgement#

The message description can be obtained directly from GS1.

Application Receipt Acknowledgement - XML Application Receipt Acknowledgement | GS1

Example acknowledgement of receipt from BC to WMS#

In the following example, the stock was received by the WMS with the transmission id {B7E627FD-C00F-4826-93ED-B2D32D9F48E2}. The receipt confirmation was sent to the WMS with the transmission id {8415449F-E9BB-40DF-A459-5170F20E9AB4}.

Extract from the XML message:

Example acknowledgement of receipt from WMS to BC#

In the following example, the goods issue was sent from BC to the WMS with the transmission ID {970cd006-f6f5-4aff-b152-c2d92f29a661}. The receipt confirmation was sent with the transmission ID {897D7F20-265F-4A16-8D32-17565A62FFE4} from the WMS.

Extract from the XML message:

WMS API Reference#

The following chapters describe the EDX-WMS events and their functionality.

For the EDX WMS Integration Events, the "Sender" is always transmitted as the first parameter. In the following description this parameter is not listed, because the documentation is from the event publisher's point of view.

For all following events the Event Publisher CodeUnit "EDX WMS AddOn" can be used.

Integration of project-specific WMS messages#

The registration of project-specific messages is to be implemented according to the "EDX API Reference".

Registration can be performed according to the examples below. "Object Type" and "Object ID" must be changed to the project-specific object accordingly. Attention: When using an XMLPort for the export of goods in/goods out, it must be ensured that the XMLPort has a table element for the goods in/goods out line. If this element is not present in the XMLPort, then an error will occur during the export!

When using a CodeUnit for the export of goods in/goods out, the field KVSEDXOutbound. "Record Id" can be used to determine which goods in/goods out is currently being exported. With the field KVSEDXOutbound. "KVSEDX WMS Detail RecordId" the current origin document (sales order, purchase order, etc.) is reported.

OnBeforeInitializeWarehouseShipmentHeader#

The event is triggered before the WMS data (External WMS, EDX Partner) are initialized in the goods issue.

OnAfterInitializeWarehouseShipmentHeader#

The event is triggered after the WMS data (External WMS, EDX Partner) has been initialized in the goods issue.

OnBeforeInitializeWarehouseReceiptHeader#

The event is triggered before the WMS data (External WMS, EDX Partner) are initialized in the goods receipt.

OnAfterInitializeWarehouseReceiptHeader#

The event is triggered after the WMS data (External WMS, EDX Partner) has been initialized in the goods receipt.

OnAfterPostSalesDocPackages#

The event is triggered after the sales delivery is posted and the packages are transferred to the sales delivery line.

OnAfterPostPurchaseDocPackages#

The event is triggered after the purchase delivery is posted and the packages are transferred to the purchase delivery line.

OnBeforeCreateWarehouseReceipt#

The event is triggered before the intermediate document "EDX goods receipt" is processed.

OnAfterCreateWarehouseReceipt#

The event is triggered after the intermediate document "EDX goods receipt" has been processed.

OnBeforeCreateWarehouseShipment#

The event is triggered before the intermediate document "EDX goods issue" is processed.

OnAfterCreateWarehouseShipment#

The event is triggered after the intermediate document "EDX goods issue" has been processed.

OnBeforeCreateInventory#

The event is triggered before the intermediate document "EDX Stock" is processed.

OnAfterCreateInventory#

The event is triggered after the intermediate document "EDX Stock" has been processed.

OnBeforeCreateWarehouseShipmentState#

The event is triggered before the intermediate document "EDX goods issue status" is processed.

OnAfterCreateWarehouseShipmentState#

The event is triggered after the intermediate document "EDX goods issue status" has been processed.

OnBeforeCheckWarehouseReceipt#

The event is triggered before the intermediate document "EDX goods receipt" is checked.

OnAfterCheckWarehouseReceipt#

The event is triggered after the intermediate document "EDX goods receipt" has been checked.

OnBeforeCheckWarehouseShipment#

The event is triggered before the intermediate document "EDX goods issue" is checked.

OnAfterCheckWarehouseShipment#

The event is triggered after the intermediate document "EDX goods issue" has been checked.

OnBeforeCheckInventory#

The event is triggered before the intermediate document "EDX Stock" is checked.

OnAfterCheckInventory#

The event is triggered after the intermediate document "EDX Stock" has been checked.

OnBeforeCheckWarehouseShipmentState#

The event is triggered before the intermediate document "EDX goods issue status" is checked.

OnAfterCheckWarehouseShipmentState#

The event is triggered after the intermediate document "EDX goods issue status" has been checked.