Re: Re: MRP-MPS query

MRP500 (MPS Generation) uses the Requirements represented by Forecast 
and/or Customer Orders that reside in the KMR file and creates planned 
Supply Orders in the KFP file. The KMR Requirements file used by MRP500 is 
specifically for Items that are flagged as Master Scheduled items 
(CIC/ICMRP field equal "M"). MRP500 creates the KFP Supply planned orders 
for the Master Scheduled items, and also generates the KMR Requirements 
for the Level 1 child in the Bill-of-Material for the Master Scheduled 
item. 

MRP600 (MRP Generation) uses the Requirements  created for the Child Item 
in the KMR file, and generates Resupply planned orders (KFP file) that 
satisfy unsatisfied requirements (netted requirements) for the Child, AND 
passes demand for these unsatisfied requirements to its Childern (B/M 
level 2). This process is repeated by MRP600 untill the program reaches 
the end of the bill-of-material, or untill a child requirement has 
sufficient stock on hand to cover the requirement (so no additional supply 
order would be needed). 

I hope this helps you.




"p d" <prd2005@xxxxxxxxxxxxxx> 
Sent by: bpcs-l-bounces+amkavoulakis=sealinfo.com@xxxxxxxxxxxx
08/11/2005 06:21 AM
Please respond to
"SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>


To
"SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>
cc

Subject
Re: Re: [BPCS-L] MRP-MPS query






Thanks Dave.

So I think my understanding that, MPS run (MRP500) creates KFP as well as 
KMR for all level MPS items & MRP run (MRP600) creates KFP as well as KMR 
for all level non-MPS items, is incorrect.

>From your explanation, I think, MPS run (MRP500) creates only KFP records 
for MPS, whereas MRP run (MRP600) creates only KMR for MPS & KFP as well 
as KMR for non-MPS items.

Am I right in this understanding ?

I am sorry, but I did not mean any child for non-MPS item. What I meant 
was the process continues till all level non-MPS items are taken care.


Regards,
Prashanth


On Thu, 11 Aug 2005 Dave Murvin wrote :
>Sounds pretty good to me, except I would change the last sentence (which 
may have been a typo) to "This continues till end of explosion of all 
non-MPS items.".
>
>For this to work correctly, you need to be sure that your non-MPS items 
do not have any children that are MPS items.  If a non-MPS item has a 
child that is an MPS item, MRP600 will generate requirements for the MPS 
Item, but since MRP500 (that plans the MPS items) has already been run, 
there will not be any planned orders generated for that MPS item.  I have 
seen this happen occasionally.  The Item low level codes (which should be 
maintained automatically during BOM maintenance) must also be correct.  If 
not, you could generate requirements for items that have already been 
planned.
>
>At 09:37 PM 8/9/2005, you wrote:
>>        Hi, Would like to have your feedback on following (my 
understanding of MPS-MRP processes in BPCS): Forecast (in case of 
make-to-stock) or Customer Order (in case of make-to-order or 
assemble-to-order scenario) creates Demand or Requirement for FG (Finished 
Goods) MPS item i.e. KMR record for FG MPS item. Upon running MPS 
(MRP500-Master Schedule), this Demand or Requirement (KMR) drives & 
creates Planned Order (KFP record) for this FG MPS item which further 
drive & creates Demand or Requirement (KMR) for next (Child) MPS item 
which in-turn creates Planned Order (KFP) for that MPS item. This 
continues till the end of BOM structure. Upon running MRP (MRP600-Explode 
Requirements) which takes MPS item Planned Order (KFP) as Input & 
generates Demand or Requirement for next (Child) non-MPS item which 
in-turn creates Planned Order (KFP) for the same non-MPS item. This 
continues till end of explosion of all MPS items. Pl. correct me wherever 
I am wrong. Regards, Prashanth
>
>Dave Murvin
>DRM Enterprises, Inc.
>
>
>-- This is the SSA's BPCS ERP System (BPCS-L) mailing list
>To post a message email: BPCS-L@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
>or email: BPCS-L-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/bpcs-l.
>
>Delivered-To: prd2005@xxxxxxxxxxxxxx