Laddawn.com : Programming Spec - MOD Item Number Matches

Created by Judy Ascensao, last modified on Feb 17, 2014

This new program will look for and return the MOD Item Number(s) that are:

  1. A close match to data entered in the Shop Widget (for the MOD Item Search - Godzilla)
  2. An exact match to data entered in the Shop Widget (when return MOD results, switch the generic 'made on demand' to the actual MOD Item# that they've searched for in the past)

Add Missing MOD.ITMMST.USR fields:

Before writing the new program, add missing fields to MOD.ITMMST.USR (FD and SYS3002) and update when creating a new MOD Item:

  1. Add four new fields to MOD.ITMMST.USR:
    1. QTY.PER.CSRL in <42> from SHOP.PACKOUT
    2. PACKAGING in <43> from SHOP.PKG
    3. High Slip in <44> from SHOP.HIGHSLIP
    4. Sheet Slit in <45> from SHOP.SHEETSLIT
  2. Modify LDLIB RPC$CONTACTITEM_SAVE and RPC$MODITEM_CREATE to update these new fields when creating a new MOD Item.

 

New BP WEB.MODITEM.MATCH:

We will start with the MOD.ITMMST.USR records for the billto customer, comparing it against the SHOP. variables to see if we have close matches or an exact match.  The calling program will pass an 'exact match' flag if it requires an exact match.  If the flag isn't set, then a list of close matches will be returned.

  1. Accept two argument passes:
    1. EXACT.MATCH - this will be set to "1" if only an exact match is needed
    2.  MODREC - this should be sent in as null.  This program will pass info back to the calling program in this variable.
  2. SELECT MOD.ITMMST.USR with:
    1. BILLTO.NBR = BILLTO.NBR (NAMED PARAM)
    2. CATALOG.GROUP = PROD.TYPE[1,1]  *** MUST CREATE A NEW CATALOG.GROUP DICT THAT STRIPS OFF FIRST CHARACTER OF CATALOG.CD
    3. WIDTH = SHOP.WIDTH
    4. DEPTH = SHOP.DEPTH
    5. LENGTH = SHOP.LENGTH
  3. Read each selected record and look for matches on the remainder of the shop widget fields.  If the EXACT.MATCH is set, you can stop searching once an exact match is found.  If not looking for an exact match, you must return a list of the MOD Items, noting the differences for each MOD item.  These are sequenced so that the more important options are first.  This way you can rule out an exact match quicker without having to go through the secondary fields.
    1. MOD.ITMMST.USR<11> = SHOP.GAUGE
    2. MOD.ITMMST.USR<12> = SHOP.FULLGAUGE
    3. MOD.ITMMST.USR<13> = SHOP.MATERIAL
    4. MOD.ITMMST.USR<23> = SHOP.COLOR
    5. MOD.ITMMST.USR<24> = SHOP.OPACITY
    6. MOD.ITMMST.USR<25> = SHOP.PLATENBR
    7. MOD.ITMMST.USR<32> = SHOP.HOLETYPE
    8. MOD.ITMMST.USR<42> = SHOP.PACKOUT(when called by MODITEM_GETBYFILTER, SHOP.PACKOUT will be the default quantity at first.  If packout is changed, this search s/b re-executed).
    9. MOD.ITMMST.USR<43> = SHOP.PKG
    10. MOD.ITMMST.USR< 39> = SHOP.FOLDED
    11. MOD.ITMMST.USR<14> = SHOP.ASRESIN
    12. MOD.ITMMST.USR<15> = SHOP.SPECAS
    13. MOD.ITMMST.USR<16> = SHOP.MILSPEC
    14. MOD.ITMMST.USR<17> = SHOP.ASPCT
    15. MOD.ITMMST.USR<18> = SHOP.METALLOCENE
    16. MOD.ITMMST.USR<19> = SHOP.METALPCT 
    17. MOD.ITMMST.USR<20> = SHOP.ANTIBLOCK
    18. MOD.ITMMST.USR<21> = SHOP.UVI
    19. MOD.ITMMST.USR<22> = SHOP.UVIPCT
    20. MOD.ITMMST.USR<44> = SHOP.HIGHSLIP
    21. MOD.ITMMST.USR<45> = SHOP.SHEETSLIT
    22. MOD.ITMMST.USR<26> = SHOP.PLATEDESC
    23. MOD.ITMMST.USR<27> = SHOP.IMAGEHGT
    24. MOD.ITMMST.USR<28> = SHOP.IMAGEWID
    25. MOD.ITMMST.USR<29> = SHOP.INKCOLOR
    26. MOD.ITMMST.USR< 31> = SHOP.READORIENT
    27. MOD.ITMMST.USR< 33> = SHOP.HOLEPLACE
    28. MOD.ITMMST.USR< 34> = SHOP.HOLESIDE
    29. MOD.ITMMST.USR< 35> = SHOP.NBRHOLES
    30. MOD.ITMMST.USR< 36> = SHOP.FROMBTM
    31. MOD.ITMMST.USR< 37> = SHOP.FROMSIDE
    32. MOD.ITMMST.USR< 38> = SHOP.BTWNHOLES

  4. Return in MODREC:
    1. If 'exact match' was requested and one was found, set MODREC<1> = MOD Item# and return to calling program.  The UI side will display this MOD Item# in the results area instead of the generic 'Made of Demand'.   If no exact match is found, leave MODREC=''
    2. If exact.match is not "1", pass back a list of the MOD Item(s) that were a close match, listing their differences from the shop widget data:
      1. MODREC<1> = mv list of MOD Item Nbrs
      2. MODREC<2> = sub-mv list of differences (in # form) for each MOD Item in field 1. This is a summary of the differences that the UI will display.  The calling process will turn these numbers into something readable after inserting more differences ** see below
      3. *** DON'T NEED TO DO THIS ANY LONGER *** MODREC<3> = mv list of SHOP. variables that were different, comma-delimited. The UI side will use this information to highlight the detailed differences when the user hovers over the differences column in Godzilla.  When going through the MOD.ITMMST.USR to SHOP. comparisons above, start accumulating the SHOP. variables when there is a difference.  Strip off the SHOP. prefix and just pass the suffix.  For example, if SHOP.FULLGAUGE # MOD.ITMMST.USR<12>, add FULLGAUGE to the MODREC< 3,X>.  If SHOP.COLOR # MOD.ITMMST.USR<23>, add ",COLOR".

** Differences:

Differences will be listed in the following order, delimited by a comma.

  1. Gauge & Full Gauge: If MOD.ITMMST.USR<11> # SHOP.GAUGE or MOD.ITMMST.USR<12> # SHOP.FULLGAUGE then difference = 2
  2. Count per Case/Roll (packout):  If MOD.ITMMST.USR<42> # SHOP.PACKOUT then difference = 4
  3. Materials/Additives: If any differences found in Material, Antistatic fields, Metallocene fields, Antiblock, UVI fields, or High Slip, then difference = 6
  4. Color/Opacity: If any differences found in Color or Opacity, difference = 7
  5. Printing/Plate#: If any differences found in Plate/Print fields, difference = 8
  6. Venting: If any differences found in Hole fields, difference =9
  7. Packaging/Folded in Half: If any differences found in Packaging or Folding, difference = 10

When done, you may end up with something like:  3^10 (subvalued)

LD.INCLUDES PRODUCTITEM.READ:

Call this new matching program from LD.INCLUDES PRODUCTITEM.READ before it sets PART.NBR to "MOD".  If we found an exact match, this program should send this MOD part# back to the UI for display.  If none found, the UI will continue to display the generic "Made on Demand":

  • Before calling the SYSCON "CONFIG.SETTINGS.LAD" (around line 34), add a call to WEB.MODITEM.MATCH passing EXACT.MATCH=1 and MODREC='' in the argument list.
  • If MODREC<1> # "", set PARTNBR to MODREC<1>.  If MODREC<1> = '', execute the SYSCON logic as it does today.
  • The program already sets named param PART.NBR = PARTNBR, so no further changes should be needed.