Who's On?

	Membership:
	Latest: Mauchk
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5244

	People Online:
	Visitors: 312
	Members: 0
	Total: 312

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chesca	1042

LOGAN edsubtbl - unique contraints

3 Replies

0 Subscribed to this topic

1 Subscribed to this forum

Sort:

Author

Messages

jdl

New Member

Posts: 0

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

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

New Member

Posts: 0

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: 1163

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.