understanding UPC codes … buggy ? or lack of our knowledge

Our 3 stores have been pushing ahead to try to learn UPC info and see how if effects our operations.  Recently ( like yesterday ) we were loading a fair sized file and realize how much grief UPC codes can cause …and how some re-writes to the DFIU program for loading X lines could help …

Summary of problem …. Installed data into store #8315 …. went to install into store #8316 and had problem with what appears to be a duplicate UPC code  … first UPC # ( see image below )

776479380

71

3 is assigned to part XAS 931-120-BP

One has t
o remember – this error doesn’t show until the VERY LAST …. not smart enough to point out problem in the beginning ,,, hmm

 

 

 

 

 

 

 

Removed the UPC and re-did the process … got a similar error on a similar part #

 

At this point we gave up –and instead of using DFIU for store #2 and Store #3 — we used INVENTORY>MULTI-STORE-MASS UPDATE … and NO problems seemed to be reported ?  We would normally use the mass update — but this file was bits of various sub lines in XAS and we wanted to see what happens when we re-loaded data thru DFIU … now we know

Suggestions for IMPROVEMENT of DFIU

1) train us on how to manage UPC codes in product file

-awaiting a request from 12 months ago to get UPC data in a SAP report or EXPLORIS report that can dump to excel

-explain how we shpould handle UPC codes we trimmed to 11 digits to match what CQ loads (originally we could not get scanner to handle BOTH 11 and 12 digit UPC codes – have since figured this out …note — CQ continues to load 11 digit UPC codes … ?

2) have DFIU handle errors in UPC better … at the START of the process – NOT at the tail end of the process …..

-have the system look for HOW many UPC code issues there are –not just stop at the first