Thomas,
Once you get everyone on up to LX 8.3.4, the extension files/fields mentioned by others is probably the best way forward.
But I would guess that still leaves you looking for a solution with the subsidiaries still on 6.04. Are they looking to operate for some time with this new data in 6.04 or are they just looking for fields to slam the data into during the conversion journey from 6.04 to LX?
I am a little concerned about the fields selected from IIM. Two of the five may be safe to designate for other purposes so long as they are not using the Configurator module. The remaining may carry varying degrees of liability. For example Bracket Group Code could have a profound effect on order pricing.
Using BPCS Item maintenance would validate the Bracket code and prevent entry of a code not previously defined. But if you wrote a private screen and entered values without validation , then I would expect "Unexpected Results" during order processing and or billing. And lastly - do these subsidiaries each operate on their own copy of BPCS or do they share a single database as different facilities? That may call into the question the use of IIM as part of the solution.
Since you have 8.3 it is likely you are on support so check with Infor or find a competent local consultant. They address these issues on a regular basis.
Best Regards,
Larry Costain
-----Original Message-----
From: Gerry Duhon <Gerry.Duhon@xxxxxxxxx>
To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Sent: Thu, Jan 20, 2011 4:27 pm
Subject: Re: [BPCS-L] IIM fields
Rob is correct about LX8.3.4 User Defined Field functionality.
UDF functionality provides the authorized user the ability to create extension
iles for the following master files: Company, Warehouse, Item, Item Warehouse,
ot, Customer, Ship To/Address,, Vendor, Salesperson, Item Vendor, Item
acility, 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
odifications to maintenance programs. UDF allows the user to create up to 999
ets 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
f the file being extended. There are standard validations and prompts
vailable. For example, when adding a 3rd or 4th Vendor to a CIC record, the
ser can prompt for Vendors from the Vendor Master. Field Types for Prompt and
alidation 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,
RPLX & 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-----
rom: bpcs-l-bounces+gerry.duhon=infor.com@xxxxxxxxxxxx [mailto:bpcs-l-bounces+gerry.duhon=infor.com@xxxxxxxxxxxx]
n Behalf Of rob@xxxxxxxxx
ent: Thursday, January 20, 2011 3:17 PM
o: BPCS ERP System
ubject: 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
ast Infor conference about this. I didn't quite understand how you do
ll the querying and all.
Failing that, there are tools from vendors like Hawkeye and what not to
how you all the places where various fields get updated.
Another option is to write a trigger against the IIM and that can do
ultiple 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
hould modify it then change the record buffer back
Then you could journal the file and see where it gets updated. If you're
lready a Mimix shop then your files are already journaled. However, if
ou are only journalling to Mimix then your journal retention may be
inuscule.
Another option commonly done (as replied by another poster) is to add a
ew file (like IIM2) and have new fields in that table.
I would avoid trying something like the following in RPG:
yds ds
bpcsNbrField
CustomAlpha overlay(bpcsNbrField)
The reason being is that the operating system is getting much more picky
bout trying to store alphanumeric data into numeric fields. Some people
re running into problems upgrading to 6.1 and 7.1 because of that.
ttp://archive.midrange.com/midrange-l/201101/msg00606.html
ttp://archive.midrange.com/midrange-l/201101/msg00619.html
Rob Berendt
-
roup Dekko
ept 1600
ail to: 2505 Dekko Drive
Garrett, IN 46738
hip to: Dock 108
6928N 400E
Kendallville, IN 46755
ttp://www.dekko.com
-
his is the BPCS ERP System (BPCS-L) mailing list
o post a message email: BPCS-L@xxxxxxxxxxxx
o subscribe, unsubscribe, or change list options,
isit:
http://lists.midrange.com/mailman/listinfo/bpcs-l
r email: BPCS-L-request@xxxxxxxxxxxx
efore posting, please take a moment to review the archives
t
http://archive.midrange.com/bpcs-l.
Delivered-To: cfgwizard@xxxxxxx
midrange.com
