Yes, Infor is adding a whole bunch of extension files to their master
files. These files have various numbers of fields of different types and
sizes for clients to use. The purpose of this is, I believe, is so that
their product IDF will keep this information as part of the "Object" it
belongs to, in this case and Item without the user having to build and
maintain the relationship. The extension files are not affected by
upgrades which is a huge advantage. Infor will never use the extension
files themselves, so they are always safe to use.
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
rob@xxxxxxxxx
Sent by: bpcs-l-bounces+bmartin=c-sgroup.com@xxxxxxxxxxxx
01/20/2011 04:16 PM
Please respond to
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
To
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
cc
Subject
Re: [BPCS-L] IIM fields
I think LX is coming out with some new feature to handle stuff like this
(user additional fields). I believe my boss mentioned something from the
last Infor conference about this. I didn't quite understand how you do
all the querying and all.
Failing that, there are tools from vendors like Hawkeye and what not to
show you all the places where various fields get updated.
Another option is to write a trigger against the IIM and that can do
multiple things:
- log who from what program and what job modified that field.
- if someone mucked with the data from INV100 and only your custom program
should modify it then change the record buffer back
Then you could journal the file and see where it gets updated. If you're
already a Mimix shop then your files are already journaled. However, if
you are only journalling to Mimix then your journal retention may be
minuscule.
Another option commonly done (as replied by another poster) is to add a
new file (like IIM2) and have new fields in that table.
I would avoid trying something like the following in RPG:
myds ds
bpcsNbrField
CustomAlpha overlay(bpcsNbrField)
The reason being is that the operating system is getting much more picky
about trying to store alphanumeric data into numeric fields. Some people
are running into problems upgrading to 6.1 and 7.1 because of that.
http://archive.midrange.com/midrange-l/201101/msg00606.html
http://archive.midrange.com/midrange-l/201101/msg00619.html
Rob Berendt
midrange.com
