Ad Hoc Move Module

Skip to main content

Ad Hoc Move Module

You are here:

Journal Batch Options

There are three ways to configure and choose a Journal Batch to use when performing a Reclass entry with the scanner:

Option 1: Have the system match the login Username to a user-specific journal batch (RECOMMENDED).

Option 2: Have the system match the Device Name to a device-specific journal batch (Available for Warehouse Insight version 2.5 and up).

Option 3: Have the system use a hardcoded journal batch (shared across all scanners).

Option 1: User-specific batch matched through a login

For Business Central versions, logins are enabled by default. For further instructions on using logins with pre-Business Central versions of NAV, please see documentation on the Warehouse Insight Overview page.

  1. Create a Transfer Journal Batch for each user logging in on the scanner:
    1. Navigate to the Item Reclassification Journal in Business Central.
    2. Select the ellipse on the Batch Name field (opens Item Journal Batches).
    3. Create a new batch for each user logging on the scanner, using their Business Central username as the new batch name (do not include the Domain if one exists).
  1. Navigate to the Device Configuration Card that matches the Device Code the scanner is using and ensure one of the following:
    1. Reclass Journal Batch field on the Warehouse tab is blank.
    2. Whse. Reclass Journal Batch field is blank for Locations that use Directed Picks and Put-Aways.

Option 2: Device-specific batch matched to the Device Name

  1. Give each device a unique name
    1. Select the Menu icon in Warehouse Insight and select Configure.
    2. Select the Menu icon on the System screen and select Device.
    3. Input a unique name in the Device Field for each of the devices:
  2. Create a Transfer Journal Batch for each of the named devices in use. The system uses the batch that corresponds to the name of the device being used (see Option 1: User-specific batch matched through a login above for instructions on creating batches).
  3. Ensure the Reclass Journal Batch field on the Warehouse tab is left blank on the Device Configuration Card matching the Device Code the scanner is using (see Option 1: User-specific batch matched through a login above for instructions on setting this field).

Option 3: Hard-coded batch

  1. Navigate to the Device Configuration Card that matches the Device Code the scanner is using in Business Central.
  2. Select a Reclass Journal Batch on the Warehouse tab (for Locations that use Directed Picks and Put-Aways, set the Whse Reclass Journal Batch instead).

Error: The Item Journal Batch does not exist

Cause: This is due to a non-specified journal batch in the Device Configuration for the scanner for Reclassification entries through the Ad Hoc Move module.

Solution: On the Device Configuration Card (1.8.x versions and older called PDA Configuration Card), choose a Reclass Journal Batch to use.  If the Location is configured to use Directed Pick and Put-Aways, choose a Whse. Reclass Journal Batch instead.

Fix the error

  1. Navigate to the Warehouse Insight Device Configurations in Business Central.
  2. Open the Card that matches the Device Code the scanner is using.
  3. Open the Warehouse tab and choose a batch to use for the Reclass Journal Batch
  1. Perform a Reload Config on the scanner.
  2. Select Menu in the top left corner of the main application screen and choose the Reload Config option (scanner refreshes and the new setting takes effect).
Was this article helpful?
1 out Of 5 Stars

1 rating

5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 100%
5
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Need help?
Tags:

2 Comments

  1. Nick W
    Nick W February 12, 2026 at 11:46 am

    I found quite a bit of concurrency issues with Ad Hoc Move. If your application requires more than one scanner to use Ad Hoc Move concurrently, you’ll likely run into No. Series issues. If a second scanner (or office user for that matter) starts an item reclass before a first scanner has completed an item reclass, both scanners will fill in the same item reclass journal number on their reclass lines. Whoever posts first is the lucky winner to claim the number, and then the other scanner gets a No. Series “Number already used” error and must delete its item reclass line and start again.

    I’d recommend using Option 2 to set up a device specific batch. Then in Item Journal Batches, assigned each device-specific batch it’s own unique item reclass No. Series. This way every scanner has its own No Series.

    (In theory, you could use Option 1, but then you would need to create and assign a No. Series for every user batch, and aside from being a little excessive, it’d be hard to maintain)

    • Terri Vaive February 17, 2026 at 3:18 pm

      Hello Nick,

      To avoid this expected behavior, it is best to use journal batches that are User ID specific.

      In the Warehouse Insight Device Configurations, leave the Reclass Journal Batch field empty to ensure the batch selected matches the User ID of each scanner.

      Thank you,

Leave A Comment

Table of Contents
Go to Top