MIDRANGE dot COM Mailing List Archive



Home » BPCS-L » December 2002

Re: Globally or by Facility



fixed

Judi,

The Facility Planning Data will be populated if the system parameter for
multiple facilities is turned to yes.  Most companies have this set to "Yes"
and abide by the requirements.  The effect is that most of the planning data
can be set for each facility.  For things like minimum balance, primary
vendor, and order policies, it makes sense that each plant probably would be
different.  Companies with multiple facilities would most likely set the
fields in the item master and then go to the facility and copy the data
through MRP140.  If necessary, they would copy additional records for each
facility and maintain any fields that are different

If you had never turned on the multiple facility flag and had not defined
your facility in the Facility Master, then I don't think you would have a
problem.  I have never tried to turn the flags off, so I can't say that you
could turn the system flag off and delete the Facility Master(s).

Be careful, though, of trying to delete the MRP140 records (CIC file).  The
records are populated manually, as stated above.  They are also created
whenever a transaction is performed for that item. (The system will validate
that there is a CIC record and if there is not one, the system will create
it).  The records are also created whenever a cost change is performed.  The
system stores the Standard and Actual costs in the record.  (They are the
fields displayed in INV300).  If a cost roll is performed, the system will
insure that there is a facility record and if there is not, it will be
created.  There may be other instances where the CIC is created by other
programs.  For example, AP may create a record (if needed) to calculate PPV.

Please note, the system uses the planning data in the facility record as a
default.  If a change is needed and it is made in the item master only, the
planning systems will continue to use the old data in the facility record.
All changes to planning data must be performed to the CIC file, usually
through MRP140.  If you choose to keep the item master in synch, that's OK,
but not necessary.

Since most of my clients have more than one plant, I usually tell them that
keeping these file in synch is just part of BPCS maintenance.   (Including
Al Mac, who doesn't always listen to me).

Sorry this is so long, but I hope it helps you,

Ed DeHarde
Unbeaten Path International

www.unbeatenpathintl.com
edeharde@execpc.com

----- Original Message -----
From: "Judi Svoboda" <Judis@ridewellcorp.com>
To: <bpcs-l@midrange.com>
Sent: Tuesday, December 17, 2002 1:09 PM
Subject: Globally or by Facility


> On BPCS 4.05CD      Globally is all that is needed at this plant.
> Facility Planning Data (MRP 140) contains data.   Can the Facility
> Planning Data (MRP 140) be inactivated, so that information no longer
> gets transferred there upon creation of new parts?  At what point does
> information get transferred automatically to Facility Planning Data (MRP
> 140)?  If Facility Planning Data (MRP 140) were inactivated, would it be
> best to do a mass deletion of information currently in there?  Where in
> BPCS would (MRP 140) be turned off:?
>
>  MRP reads from IIM to plan.  When looking in BOM the lead time is not
> being read from IIM but from Facility Planning Data (MRP 140).  IF
> Facility Planning Data (MRP 140) is blank, then  MRP rules for BOM info.
> What besides BOM is effected by Facility Planning Data (MRP 140) when
> not set up by Facility?      Thanks  --  Judi
>
>
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
> or email: BPCS-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
>








Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact