Laddawn.com : Programming Specs - Customer Item Numbers

Purpose: Allow access and/or display of customers item numbers by using either their item number or Laddawn item number.

Note: ** changes as of 1/2/14 are highlighted in RED below

Overview: Currently customer item numbers are only used to print on Branit Labels. In addition, we now need the ability to view or retrieve customer item information using either the customer item number or Laddawns.  The addition of the MOD item reqires a change to the file KEY for CUSTPART.USR.  The new key to the CUSTPART.USR file will now be COMPANY*CUSTOMER*Laddawn CPN or MOD item number (for web MOD items) or COMPANY*CUSTOMER*CcustomerItemNumber (for NS items).

Currently we store customer Item Numbers in the CUSTPART.USR file with the key of either COMPANY*CUSTOMER*CPN (01*014127*02099)or COMPANY*CUSTOMER*Ccustomeritemnumber (01*014127*CS-11085)

The file layout is as follows:

Field 1     =     Customer Item Number

Field 2     =     Customer Item Description 1

Field 3     =     Upload Error Message

Field 4     =     Upload Update Flag

Field 5     =     UPCA Code

Field 6     =     UPCA Internal Code

Field 7     =     Type

Field 8     =     Item number

Field 9     =     Customer Description 2

Field 10     =   Customer Description 3

To be able to read the customers item from the database, we will need to create a new cross reference file called CUSTPARTXRF.USR to link the customer item number to the MOD item number or stock item number or NS configured item.

The key to this new file and the layout is as follows (these examples are using Uline as a model):

KEY = COMPANY*CUSTOMER*CUSTOMER ITEM NUMBER (S-3039 or S-11085 or S-10404)

Field 1     =     Laddawn CPN or MOD item number or NS item (ie... 02099, MOD123, CS-10404) **Note: currently there are not MOD item numbers so for the initial pass the MOD123 will be the existing key which is "C":customeritemnumber CS-11085.

Avante: 

Changes Part I: - create a separate PRC task for these changes  (pre web release changes)

The following changes will use the exising customer custom item numbers of "C":customer item number.  All modifications need to be done with this in mind.  We would like to roll these changes live to begin the updating of records.  A conversion program will be written in part two to convert the "C":customer item numbers to the customers MODnnnn item number for all CUSTOM items except NS items

Create New Crossreference File - CUSTPARTXRF.USR - 3 HOURS

      • Create file, system dictionaies and file dictionaries
      • Write a utility program to update the new crossreference file for the existing customer item numbers
      • Test and run utility program on DEV
      • Run utility program on LIVE  -  do not do this step until we decide on the appropriate date/time to do so

Modify SOP9031 - Customer Item Number Mainenance - 2 HOURS

      • Modify the above process
      • create/update/delete the new crossreference file

Modify SOP9052 - Upload Customer Item Numbers - 2 HOURS

** Note: This process is a clear and replace of the customers item numbers - the spreadsheet they give us must include all items that they want updated or added.

        • Modify the above process
        • Create/update/delete the new crossreference file

 

Changes Part II: - create a separate PRC task for these changes (changes needed for the web)

In part two the Avante programs must be changed as needed to work the new CUSTPARTXREF.USR file using the appropriate key depending upon if the item is a Stock, MOD or NS item.

The existing processes must be evaluated and changed if needed to work with the new key of the CUSTPART.USR file and use the CUSTPARTXREF.USR file.  There may be instances where you may need only one of the files and other times you may need to use both files.  If a process is only using/passing the customer item number, then the CUSTPARTXREF.USR file will have to be read to get the Laddawn CPN, NS or MOD item number from field<1>.  If the process is using/passing the Laddawn item number (stock, NS or MOD) then the CUSTPART.USR file can be read directly.  Please make sure that changes work with add/update/delete where needed and the all processes, screens etc. are considered.

 

Modify the Following Avante Processes for New Key and New File - 16 HOURS

INV9029 - Label Print

INV9800.STAPELS - Delimited Inventory File

QUO4000 - Maintain Quotations

SOP4000 - Enter Sales Orders

SOP4007 - Create Pickslips

SOP9031 - Customer Item Number Maintenance

SOP9034 - Create Product Price ASCII File

SOP9052 - Upload Customer Item Numbers

SOP9060 - Customer Item Number Report

SOP9084 - Customer Item Info Download

SOP9800 - Create EDI Advanced Shipping Notice

SOP9801.STAPLES - Staples Invoice XML File

SOP9802 - Create 855 Change Ack for EDI

SOP9803 - EDI Invoices