Prev
Next
Forums Supply Chain Management Lawson S3 Supply Chain

Identifying Special Items

 5 Replies
 2 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
JonA
Veteran Member
Posts: 1163
Veteran Member
2/9/2015 8:00 PM
    When we implemented Lawson 8.0.3, the consultant recommended that we instructed end users to add a # to the beginning of the item number for X type items.  There was a bug in RSS where if the requester entered an item number that was in the item master on the Special/Service screen the cost and source information from the nonstock item would default.  So by putting a # in front of the item number we worked around this issue.  That bug was fixed quite a while ago but we still use the # for specials and I see no reason to keep doing this.  Anyone else using some way to segregate specials other than just the item type? And for what reason?
    Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
    Kat V
    Veteran Member
    Posts: 1020
    Veteran Member
    2/9/2015 8:50 PM
      We instruct the users to put only the part number in the ITEM field for specials, because RQC has a setting that will check against itemmast and povenitem and catch unnecessary specials. So we're definitely on the same page as you and wouldn't have a special character in the item fields.
      JonA
      Veteran Member
      Posts: 1163
      Veteran Member
      2/11/2015 1:02 PM
        Kat- Is that setting you mentioned in the rqcconfig file?
        Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
        Kat V
        Veteran Member
        Posts: 1020
        Veteran Member
        2/11/2015 1:30 PM
          Yes - we implemented when it was RSS so at that time it was called "special_item_validation" value = "warn" and we've just told IT every upgrade to make sure it "checks for specials" - so I'm not sure it's still exactly that. But it had three values - Skip (the default), Warn - takes them to the item, but allows them to go back and Deny which takes them to the item and does not allow them to override it.

          We picked Warn as vendor mergers and sometimes just dumb luck mean there are items with the same part number from completely different vendors.

           

           

          Edit: But if the user puts #1234 and the item is 1234 - it will not find a match.  Ditto for dashes, dots, etc.  It must be an exact match.  Still, the number of "unnecessary" specials dropped 80% the moment we turned it on

          Scott Perrier
          Veteran Member
          Posts: 39
          Veteran Member
          2/11/2015 2:40 PM
            We were also advised to place a "." as the first character of special item number back on 8.1 in 2006. I have since adviced the supply chain group to discontinue that practice in favor of the "WARN" setting in RQC. Also this practice prevents the new RQ2XX report in 9.0.1 and up, that compairs special item to the item master, from matching. It is difficult to remove a practice once it is implemented for some time.
            Kat V
            Veteran Member
            Posts: 1020
            Veteran Member
            2/11/2015 2:47 PM
              We now have the buyers in the req approval flow for specials. We had to consistently unrelease the reqs and/or cancel POs to get the users to change their habits. Needless to say, this is not a popular option and tends to be implemented a department at a time with the support of our VP to talk with the manager involved.

              But usually the third or fourth time the department doesn't get the item, the requisitions become cleaner.