Department in HQ, but not on Detailed Sales report

I have a department that shows on the HQ Department & Category list, but does not show up on the Detailed Sales Report. All the items show up in the "no Department" department on the report.

Reply to
JimE
Loading thread data ...

Couple of things to check:

1) Are the dept and cats defined on the actual item card? 2) Did you delete a dept/cat and recreate (that would not force it to realign with the item) 3) Do the stores create their own items? 4) Do stores have ability to delete/change: a) Depts and Cats from Dept/Cat list? b) Dept and Cats from Item Cards?
Reply to
jocelynp

Reply to
JimE

Hi Jim, Here is what I would suggest - do a test on one item. If we test one ILC, this might let us know if the Dept was deleted and recreated. If this test works, there is some stuff we can do to quickly script changes. Let me know how this goes.....

Generate your report, where the items are listed by blank dept> Mouse over the first ILC> Double Click on first ILC> Note the Dept/Cat> Click the 'x' to delete the Dept from the item (will also delete Cat)> Click the mag glass next to the Dept> Select proper Dept> Mag glass next to Cat> Select proper Cat> Here is where I would mouse over and Copy the ILC> OK to save changes> Refresh report (F5):

1) Is the item you just changed listed under blank dept, or is it under the actual dept name 2) If you just can not find the item on the report after the refresh, I would then open the filter and set Item (or ItemLookup) = (paste in the ILC)> Add> OK> is it listed with the Dept now assigned???
Reply to
jocelynp

Reply to
JimE

Woops - sorry - I mean Item Lookup Code.

Reply to
jocelynp

Jocelyn, When I run the Detailed Sales Report, there are no Item Lookup Codes listed for the items in the blank department. There is a column for it, but no code. Just Qty., Price and Store Thanks! Jim

"JimE" wrote:

Reply to
JimE

Jim, I think there are two possible things going on (and I just now saw how long this is - sorry):

1) You might be going through the same thing we are just getting past ourselves: Our Items were not centralized.

While this company was creating and issuing items fro the HQ level, stores were able to create new, edit, delete and copy items at their level. What this did was block the view of the store sold items because they only resided at the individual store level. To see if the store(s) are creating their own items, you can query their SO Admin by the following steps:

SO Admin>

File>

Connect>

Enter Password>

OK>

Database>

BACKUP>

Query>

New>

Copy and Paste: SELECT * FROM Item WHERE HQID = 0

This will return any items created at the store level You can then do a File> Export and move the data to a destination for further review, etc.

To exit SO Admin> Just File> Exit

2) Possibility #2: Items are being deleted instead of inactivated at the HQ level. I never recommend deleting an item and instead inactivating. But - should I have to delete an item from HQ that has already been issued via a WS 250, I have to issue parallel SQL statements to delete the item from the SO side (simply deleting the WS250 will not delete the items on the store side if they have already processed)

An example of when I have had to delete an item (all stores have processed the WS in this example): Created and issued item from HQ yesterday>

Stores processed WS250> Realized today, item was 100% mistake> Stores have not had any movement on item at all>

Note the ILCs (Item Lookup Code) of the sku or skus>

Delete from HQ>

Create and issue scripts to all stores to delete the items (based on the ILCs)

If only some stores have processed the WS250, I note the stores that have processed, delete the WS250 (thus preventing other stores from processing) and issue the scripts only to the stores that had processed.

Do you see what I am saying here, I know this is kind of long. Basically either stores are creating their own ILCs, or HQ has deleted items, but not yet removed or inactivated from stores.

Reply to
jocelynp

Reply to
JimE

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.