Abbadabba's Item Number and ALU Sequencing Issue and Resolution

ABBADABBAS

How to copy Item# to ALU or ALU to Item#

Overview:  Abbadabba’s is on Retail Pro 9 and they use a third party custom program that generates Retail Pro Item#s, just like Retail Pro 8.  They also have ALUs being generated automatically, and the goal is for the ALU and the Item# to always be the same for each item (for various reasons we won’t go into in this article)

 

If a ticket comes in about the sequencing being off, sometimes it can be because the ALU didn’t increment, or that the Item# duplicated somewhere.

ALU AND ITEM# FIELDS SHOULD BE IDENTICAL FOR AN ITEM, BUT SHOULD BE UNIQUE AMONG ALL ACTIVE ITEMS!

Steps to resolve:

1.      Determine if the issue is with the ALU or the Item# is off or missing.

a.      Log into the Abbadabba’s head office server (AbbaCorpServer) and log into Retail Pro 9

b.     Go into Merchandise – Inventory and sort the inventory by Item# highest to lowest (this will require you to click on the column heading once, then click OK to confirm the sort, THEN click on the column heading AGAIN, and click OK to confirm the sort again – this sorts the inventory highest to lowest.

c.      You will get a screen like this:

 

2.      If you find out that Item# is higher, and therefore ALU is off, you will need to copy Item# to ALU in TechToolKit:

a.      Launch TechToolKit on the server

b.     Go to SQL Shell

c.     Type in:              update invn_sbs set alu=item_no where active=1

d.     Click the thunderbolt to run that statement

e.      You can check your work before you commit by clicking the down arrow in SQL Shell and then type this in and then clicking the thunderbolt:

SELECT item_no, alu
FROM invn_sbs
WHERE active=1
ORDER By item_no DESC

f.        When you confirm it looks correct, type in:               Commit

g.      Click the thunderbolt to run that statement

h.      Close TechToolkit

i.        In Retail Pro, determine the last ALU number by sorting the Item # column by the highest to lowest number

j.        Go into System Preferences and set the Last ALU to the last ALU you saw when sorting by Item# - this will ensure that that next ALU will match the next Item#

3.      If you find out that ALU is higher, and therefore Item# is off, you will need to copy ALU to Item# in TechToolKit:

a.      Launch TechToolKit on the server

b.     Go to SQL Shell

c.      Type in:              update invn_sbs set item_no=alu where active=1

d.     Click the thunderbolt to run that statement

e.      You can check your work before you commit by clicking the down arrow in SQL Shell and then type this in and then clicking the thunderbolt:

SELECT item_no, alu
FROM invn_sbs
WHERE active=1
ORDER By item_no DESC

f.        When you confirm it looks correct, type in:               Commit

g.      Click the thunderbolt to run that statement

h.      Close TechToolkit

i.        In Retail Pro, determine the last ALU number by sorting the Item # column by the highest to lowest number

j.        Go into System Preferences and set the Last ALU to the last ALU you saw when sorting by Item# - this will ensure that that next ALU will match the next Item#

A screenshot of a computer

AI-generated content may be incorrect.

k.      Close Retail Pro

l.        You now need to make sure the custom program that generates the Item#’s is reset properly.  You only need to do this when Item# is off, not when ALU is off.

                                                              i.      Browse to C:\POS\RetailPro9 and double click on MMItemNum.exe

A screenshot of a computer

AI-generated content may be incorrect.

                                                            ii.      This will come up:

                                                          iii.      Click Run

                                                          iv.      The program goes really fast, and you’ll see “Done” show up in the Status box:

                                                            v.      Close the program, close all open programs and windows you were working in and exit the remote access – you’re all done!

4.       

 

Did you find this article useful?

';