Skip to main content

SBT_BinInventories EDBL

Distributor reference for the SBT_BinInventories EDBL import: set Scan Based Trading inventory in customer-type bins via InventoryAdjust BinTrans. Advanced, outside standard support. Needs setting 445 and BinInventoryEdit; v22.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 22.01

Pre-Conditions

  • This routine is specifically for SBT (Scan Based Trading) systems only. It will only run if system setting 445 is enabled.
    ​
    ​

  • User must have BinInventoryEdit permission to use this routine.
    ​
    ​

  • Bins and Products referenced in the import file should already exist in the system or have their translation values provided.
    ​
    ​

  • This routine is designed for managing inventory levels in customer-type bins

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


  1. The system first processes location translations to identify the proper locations for inventory operations.
    ​
    ​

  2. Product and Bin translations are then processed to match external identifiers with internal system IDs.
    ​
    ​

  3. If PurchaseID is provided but PurchaseTransID is not, the system will attempt to find the corresponding PurchaseTransID.
    ​
    ​

  4. The system automatically determines the appropriate adjustment bin for each location if not specified.
    ​
    ​

  5. WholesaleUnitsPerCase will be populated from product data if not provided in the import.
    ​
    ​

  6. The routine calculates inventory differences between current bin inventory and the provided values.
    ​
    ​

  7. Inventory is moved between bins using BinTrans records of type InventoryAdjust to match the specified values.
    ​
    ​

  8. The system specifically focuses on Customer-type bins (BinZoneType = Customer) when processing inventory adjustments.
    ​
    ​

  9. The routine will not create bins that don't exist; you must first create bins using the Bins EDBL routine.

Fields And Definitions

  • LocationID_Translation: External identifier for the Location
    ​
    ​

  • LocationID: Internal Encompass ID for the Location (defaults to user's current location if not specified)
    ​
    ​

  • BinID_Translation: External identifier for the Bin
    ​
    ​

  • BinID: Internal Encompass ID for the Bin
    ​
    ​

  • AdjBinID: The adjustment bin ID used for inventory movements (system will determine if not provided)
    ​
    ​

  • ProductID_Translation: External identifier for the Product
    ​
    ​

  • ProductID: Internal Encompass ID for the Product
    ​
    ​

  • Inventory: The quantity to be set for this Product in this Bin
    ​
    ​

  • PurchaseID: Related Purchase ID for tracking product origin
    ​
    ​

  • PurchaseTransID: Related Purchase Transaction ID for tracking product origin and lot information
    ​
    ​

  • WholesaleUnitsPerCase: Number of retail units in a case for this product

Best Practices

  • Always include LocationID_Translation or LocationID to ensure inventory is assigned to the correct location.
    ​
    ​

  • Provide BinID_Translation or BinID to specify which bins should contain the inventory.
    ​
    ​

  • Include ProductID_Translation or ProductID to identify which products are being managed.
    ​
    ​

  • Always specify the Inventory amount for each bin and product combination.
    ​
    ​

  • If tracking batch/lot information, include PurchaseTransID to maintain proper batch tracking.
    ​
    ​

  • Verify WholesaleUnitsPerCase matches product configuration to avoid quantity conversion issues.
    ​
    ​

  • When possible, use BinID_Translation instead of BinID to improve data portability between systems.
    ​
    ​

  • Run the import in "Update Only" mode if you want to modify existing bin inventory without creating new entries

Did this answer your question?