Skip to main content

BinTrans EDBL

Distributor reference for the BinTrans EDBL: import bin transactions (typically type 14 Moved) between bins in WMS warehouses, with mappable fields, AddOnly/UpdateOrAdd actions and Bin Lot handling. Advanced; v20.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 20.01

Pre-Conditions

The BinTrans EDBL is typically only needed for warehouses where WMS is enabled. Non-WMS warehouses have simplified inventory management that generally does not call for imported Bin Trans.

Steps

EDBL Routines Disclaimer: This EDBL routine represents advanced functionality primarily intended for use by Encompass technical staff. While technically proficient customers may utilize these routines, please be aware that they fall outside the scope of standard support. Assistance with EDBL routines is not covered under standard support agreements and may require billable services from our Professional Services team. Please ensure you thoroughly understand this routine before implementation in your production environment

The BinTrans EDBL is designed to update, manage, and process bin transactions—records of inventory movement—in the system. This guide provides a detailed breakdown of the mappable fields, their purposes, prerequisites, and key considerations for running the EDBL successfully.

1. Review data & map fields


Ensure that all required and desired fields are properly mapped in the import data. See Fields & Definitions for more information about each field in the EDBL.

2. Before running the EDBL, ensure the following:
​
​

  • Location Mapping: Either LocationID or LocationID_Translation must be mapped.
    If no matching LocationID is found in the system, a warning will appear: "LocationID not mapped."

3. Import Actions
​
​

Only the following import actions are respected:

  • AddOnly

  • UpdateOrAdd

If other import actions are used, no data will be processed.

4. Special Cases
​
​

  • Updating PurchaseTransID:
    If PurchaseTransID is mapped, BinInventory.PurchaseTransID will be updated for the related product and bin combination.
    ​
    ​

  • Adding Bin Lot Data:
    If PurchaseTrans is not null, Bin Lot data will be added under these conditions:
    - The bin's BinZones.TrackBinLots field is set to Required or Optional
    - The product's tracking flags are enabled for Code Dates, Batch Codes, or Vintages.

5. Additional Notes
​
​

There are no scheduled tasks that need to run after this EDBL. BinTrans records are immediately created and impacting the system, though they may take up to 15 minutes to be visible in the Bin Trans table. Immediate impact can be seen in the Bin Audit tool, where changes to bin inventory over time can be reviewed for a specified product and bin.

Fields And Definitions

  • LocationID_Translation: Maps to LocationID through table translation. (Required*)
    ​
    ​

  • LocationID: Directly provides the LocationID. (Required*)
    ​
    ​

  • BinID_Translation: Maps to the BinID through table translation.
    ​
    ​

  • ProductID_Translation: Maps to the ProductID through table translation.
    ​
    ​

  • ProductID: Directly provides the ProductID.
    ​
    ​

  • BinTransType: Specifies the transaction type (BinTrans.BinTransType).
    Values: 1,Received;2,Unreceived;3,Put Away;4,Replenished;5,Pick Complete;6,Pick Uncompleted;7,Loaded;17,Add Ons;8,Unloaded;9,Returned;10,Unreturned;11,Return Put Away;12,Invoiced;13,Inventory Adjust;14,Moved;15,Skip;16,Picker Cut;18,Production Queue;19,Reverse Production Queue;20,Equipment Transfer;21,Re-picked
    ​
    ​

  • NumUnits: Specifies the number of units involved in the transaction (BinTrans.NumUnits).
    ​
    ​

  • BinID: Specifies the target bin ID.
    ​
    ​

  • LoadSheetID: Links the transaction to a load sheet (BinTrans.LoadSheetID).
    ​
    ​

  • PalletID: Links the transaction to a pallet (BinTrans.PalletID). This is only for picking outbound pallets, not for the pallet inventory is stored on while it resides in the warehouse.
    ​
    ​

  • InvoiceTransID: Links the transaction to a specific invoice transaction (BinTrans.InvoiceTransID).
    ​
    ​

  • PurchaseTransID: Links the transaction to a specific purchase layer of inventory (BinTrans.PurchaseTransID). This is how specific expiration dates, batch codes, or vintages are noted during a move, translating to a Bin Lot, if that data is being tracked.
    ​
    ​

  • BoxID: Links the transaction to a box used in unit or bottle picking. (BinTrans.BoxID).
    ​
    ​

  • Date: Specifies the transaction date. Defaults to the current date (LocalToday()) if not provided.

*Only one of the noted fields must be mapped, but both are not simultaneously required.

Best Practices

  • When to use: The BinTrans EDBL is best suited for situations where the "from bin" and the "to bin" need to be specified, as opposed to allowing inventory to always shift into an adjustment bin. If inventory is moving from one on-floor bin to another, for example, the BinTrans EDBL is the right choice.
    ​
    ​

  • The BinTrans EDBL is primarily intended for use within integrations or during the data migration process.
    ​
    ​

  • In most imports, the Bin Trans Type should be 14, Moved which simply notes that inventory is shifting from one bin to another, without involving more specific processes like receiving.

Did this answer your question?