Skip to main content

Pallets EDBL Setup Guide

Distributor guide to the Pallets EDBL import in Encompass: create or update outbound pallets linked to invoices (SSCC18, status, units, picker) for integrations or data migration.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 20.01

Steps

The Pallets EDBL is an import used to map, update, and manage pallet-related data in the system. This guide walks users through the available fields, their functions, prerequisites, and important 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."
    ​
    ​

  • Invoice Mapping: InvoiceNum or InvoiceID must be provided.
    The corresponding invoice must exist in the system for the pallet to be added, and InvoiceTransID must be accurate.
    If it is missing or incorrect, the pallet will not link to any invoice transaction, rendering it meaningless.

3. Import Actions
​
​

Only the following import actions are respected:

  • UpdateOnly

  • UpdateOrAdd

If other import actions are used, the process cannot link InvoiceTrans or update any other data.

4. Special Cases
​
​

  • Creating New Pallets:
    If only PalletID_Translation is mapped, and not PalletID, a new pallet will be created.
    ​
    ​

  • NumUnits Discrepancies:
    If the NumUnits in the provided InvoiceTransID does not match the system’s current value, the system will adjust the values.
    The latest provided value will overwrite and become the new NumUnits. This is how cuts can be communicated via the EDBL.

5. Additional Notes
​
​

There are no scheduled tasks that need to run after this EDBL. Pallet records are immediately updated, along with their related invoice trans data.

Fields And Definitions

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

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

  • PalletID_Translation: Maps to PalletID through table translation; if not found, a new pallet is created.
    ​
    ​

  • PalletID: Directly provides the PalletID.
    ​
    ​

  • InvoiceNum: Maps to InvoiceID through table translation using InvoiceNum. (Required*)
    ​
    ​

  • InvoiceID: Links the pallet to an existing invoice via Pallet.InvoiceID. (Required*)
    ​
    ​

  • ProductID_Translation: Maps to ProductID through table translation, in the end providing InvoiceTrans.ProductID.
    ​
    ​

  • ProductID: Directly provides InvoiceTrans.ProductID.
    ​
    ​

  • NumUnits: Updates InvoiceTrans.NumUnits.
    ​
    ​

  • SSCC18: Updates the SSCC18 value for pallets, which is the serialized shipping container code used universally for pallet recognition across systems.
    ​
    ​

  • Status: Updates pallet status; defaults to "New" if no value is provided.
    ​
    ​

  • PalletSeq: Updates InvoiceTrans.PalletSequence.
    ​
    ​

  • InvoiceTransID: Links a related invoice transaction with the pallet.
    ​
    ​

  • PickedByUserID: Updates the PickedByUserID field for the pallet, indicating the User ID of the person that completed the pallet pick.

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

Best Practices

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

Did this answer your question?