Prev
Next
Forums Lawson S3 Procurement

LOGAN edsubtbl - unique contraints

Sort:
You are not authorized to post a reply.
Author
Messages
jdl
Advanced Member
Posts: 20
Advanced Member
12/9/2008 8:31 PM
    300 STRM       803EDI 1105 LO_O_SHIPTO
    CAST STRM       803EDI 1105 LO_O_SHIPTO
    Can someone explain why uniqueness (is that a word?) is not enforced on the Logan edsubtbl?  I have a couple of duplicatre entries and it just made me wonder why this is permitted?

    Sam Simpson
    Veteran Member
    Posts: 239
    Veteran Member
    12/9/2008 10:03 PM
      There are only three fields in this table and they are all part of the key hence they are unique. In your example I don't see any duplicate at all. 300 and CAST are not the same.
      jdl
      Advanced Member
      Posts: 20
      Advanced Member
      12/10/2008 2:22 PM
        Okay, I see your point. What these two rows means to me is that it's possible to have 2 ship to locations set up for the same "ship-to, vendor, purchase from and LO_O_SHIPTO" combination. I guess the edi app uses the first row returned. If the uniqueness was just enforced on the LIST-NAME and LAWSON-VALUE, this state could not occur. This is what I was expecting anyways.
        Thanks
        JonA
        Veteran Member
        Posts: 1162
        Veteran Member
        12/12/2008 12:18 PM
          I would agree that the system should give a message that *_O_SHIPTO already exists.  But I can think of at least one instance where you might need *_I_SHIPTO set up this way.  Maybe the Lawson didn't want to complicate the ED40 programming by setting up edits/rules on some and not others.
          Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
          You are not authorized to post a reply.