Rob is correct about LX8.3.4 User Defined Field functionality. 
UDF functionality provides the authorized user the ability to create extension files for the following master files: Company, Warehouse, Item, Item Warehouse, Lot, Customer, Ship To/Address,, Vendor, Salesperson, Item Vendor, Item Facility, Item X-Ref/Vendor X-Ref, Location and Product Life Cycle.
UDF was created to allow users to add new fields without database changes or modifications to maintenance programs. UDF allows the user to create up to 999 sets of user defined fields. There are 19 standard fields on each sequence.
Each user defined file has the same data fields and additionally, the key fields of the file being extended. There are standard validations and prompts available. For example, when adding a 3rd or 4th Vendor to a CIC record, the user can prompt for Vendors from the Vendor Master. Field Types for Prompt and Validation are :
	System Code Tables
	Item Master
	Vendor Master
	Customer Master
	Warehouse Master
	Facility Master
	Currency Master	
	Date
	Language
Best Regards,
Gerry Duhon, CPIM | Sr. Application Consultant, Supply Chain & Manufacturing, ERPLX & BPCS | Infor Professional Services | Cell:832.335.9872 |Gerry.Duhon@xxxxxxxxx
SAVE THE DATE | System i User Conference 2011 | Gaylord Opryland | Nashville, TN | October 2 - 5 | 
-----Original Message-----
From: bpcs-l-bounces+gerry.duhon=infor.com@xxxxxxxxxxxx [mailto:bpcs-l-bounces+gerry.duhon=infor.com@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, January 20, 2011 3:17 PM
To: BPCS ERP System
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
 
As an Amazon Associate we earn from qualifying purchases.