Re: RE: Ok, where is it?

[rob@xxxxxxxxx]

Actually, as I sent it I wondered about that.  Mostly the item number 
field.

Quantity ordered has a totally different meaning than quantity shipped. 
Generally, while none of their attributes may be the same, except for 
their size attributes, there is nothing that says their size attributes 
must match.  Therefore I would argue that your reference file should have 
a separate field for quantity ordered and quantity shipped.  That you want 
to cascade these down from a common "quantity" field is ok.

Perhaps this is were we need to start taking more advantage of DB2.  For 
example on those multiple item number fields in the transaction file we 
should have referential constraints pointing back to the item master file. 
 Then, either by displaying the constraints on the master file, or by 
using iSeries Navigator to draw a nice navigator, you can see all the 
places where item number is referenced.

I fail to see how renaming the field helps in knowing wherever the item 
number is referenced in the traditional FREF file scheme.  For example I 
look at ITMNBR in the FREF file.  Now, how do I know what fields, in what 
files, would be impacted by a change in item number size?

I wonder how BPCS addressed this when they changed their item number size 
when they went to BPCS 8?  Check the database cross reference files for 
anything that was 15A?

There are vendor written applications that actually use the same field 
name.  Like LOCATION for the location field, regardless of which file it 
is in.  Software Plus is one example.  I suppose if Software Plus and 
SSA's BPCS ever get together they're in for a culture shock.  We've 
written feeds between the two because we like the Software Plus 
financials.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





"Michael Naughton" <mnaughton@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/11/2003 01:35 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: RE: Ok, where is it?


How do you handle situations where you want to use the same (base) field
more than once in the same file?

e.g. material requirements file might have finished product item and raw
material item. Sales order line might have qty ordered, qty shipped, qty
back-ordered. Many files have multiple date fields. Etc.

Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> writes:
>If not, then that is a great enhancement.  I am in the camp that ITMNBR 
>should be ITMNBR in all files.


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@xxxxxxxxxxxx


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.