For us, it is not true that you can only have one item class per item. It
may seem that way if you are only looking at IIM item master file.
We can have a different item class per item per facility, using the CIC
file. However, we have largely abandoned that feature of BPCS, since some
areas involved more maintenance overhead than the benefits justified.
We have a different set of profit cost centers for each facility.
So for example, all activity with a part:
in warehouse 21 in facility 20 ends up in profit center 200 series;
in warehouse 51 in facility 50 ends up in profit center 500 series.
We have also developed some programs that show consolidated picture all
We use item classes of 2 letters for the type of product.
We use item classes of 2 digits for the type of customer order activity,
such as reason for credit memo.
[mailto:bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx] On Behalf Of
Robert A Brown
Sent: Tuesday, March 24, 2009 12:49 PM
Subject: [BPCS-L] CEA Changes
We are on 6.04 and have setup our CEA to focus on the item class for
determining account segments. We are now considering running the same part
in multiple plants but this causes another issue in CEA. Since we can only
have one item class per part, is there a way to redirect the transaction
based on additional criteria? I was thinking of the Account rules but have
had little success. I have created new macros and aliases but it only
works correctly for that item that is produced in multiple plants. In our
original setup we are using ILCLASREVA in the plant segment, then the
alias directs to the appropriate segment values. In the setup below I have
created the macro ILWHS2 and ILCLAS2 that is looking at the warehouse of
the transaction and then places the appropriate Plant value based on the
warehouse, and then the item class that is then resolved to the correct
Oper, Acct, and Cls. Can I use an Account Rule in some manner to achieve
the same thing?
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.