Skip to main content

Bins EDBL

Distributor reference for the Bins EDBL import in Encompass: bulk-create or update warehouse bins with BinID_Translation, Location and Bin Zone fields. Advanced, outside standard support. Needs Bin Edit permission; v22.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 22.01

Pre-Conditions

  • User must have the "Bin Edit" permission to import bins
    ​
    ​

  • Bin Zones and Bin Types must already exist in the system
    ​
    ​

  • Locations must already exist in the system
    ​
    ​

  • At least one RouteCountType must exist in the system (will use the minimum RouteCountTypeID if not specified)

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 Bins EDBL import routine allows you to create and update bin records in your warehouse management system. Each bin represents a physical location in your warehouse where inventory can be stored.

The routine works by:

  1. Validating that you have the required permissions

  2. Translating any external IDs to internal system IDs

  3. Creating or updating bin records based on your chosen import action

  4. Automatically populating certain fields if not provided in the import file
    ​
    ​

By default, if the LocationID is not provided, the system will use the current user's LocationID. If importing new bins, the RouteCountTypeID will be automatically set to the minimum RouteCountTypeID in the system if not specified in the import file.

Fields And Definitions

Required Fields:

  • BinID_Translation: The external ID or name of the bin (defaults to "Unslotted" if not provided)
    ​
    ​

Optional Fields:

  • LocationID: The ID of the location where the bin exists (defaults to current user's LocationID)
    ​
    ​

  • LocationID_Translation: The external ID or name of the location
    ​
    ​

  • BinZoneID: The internal ID of the bin zone
    ​
    ​

  • BinZoneID_Translation: The external ID or name of the bin zone
    ​
    ​

  • RouteCountTypeID: The ID of the route count type (auto-populated if not provided)
    ​
    ​

Additional Available Fields:

  • Any field from the Bins table
    ​
    ​

  • Any field from the BinZones table
    ​
    ​

  • Any field from the BinTypes table

Best Practices

  • Always include a unique BinID_Translation value for each bin to avoid duplicate bins
    ​
    ​

  • Specify the BinZoneID or BinZoneID_Translation to ensure bins are created with the correct zone type
    ​
    ​

  • Include the LocationID or LocationID_Translation if importing bins for multiple locations
    ​
    ​

  • Use the "Add or Update" import action if you're not sure whether bins already exist in the system
    ​
    ​

  • Check for warnings after import, as these may indicate issues that need to be resolved
    ​
    ​

  • Consider setting up a small test file with a few records before importing a large number of bins
    ​
    ​

  • When updating existing bins, make sure to include the correct BinID_Translation values to match existing records

Did this answer your question?