Re: SYSTEM21 Digest, Vol 7, Issue 3

Thanks Otto, 

No demand is created for items at a specific level. i.e. a subassembly at
level 5 shows demand, but the inputs/components to the sub assembly which
are at level 6 do not. At MPS runtime, we set the "Lowest Level to review"
to 9 which should capture our level 6 components. Any ideas ? 
 

-----Original Message-----
From: system21-bounces-Zwy7GipZuJhWk0Htik3J/[email protected] [mailto:system21-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]]
On Behalf Of Otto A Ritter Jr
Sent: Tuesday, January 13, 2009 10:31 AM
To: system21-Zwy7GipZuJhWk0Htik3J/[email protected]
Subject: Re: [SYSTEM21] SYSTEM21 Digest, Vol 7, Issue 3

Jim,

This document may be of some help for you.
Anatomy of the MRP run:

MENU option: 11/MRP 

MRP task code: MReee037020 (where "eee" is the environment code)

JOB name: MRP_MAIN):
    MR002P (interactive)
    The interactive program's main purpose is to update the RUN
Parameters on the QUOTED model record on file MRP70.

    MR002CLP (batch)
    The batch program creates duplicate objects of the main MRP work
files in QTEMP and calls the MRP Main Processing CL:
        MR002CL1 (MRP Main Processing)
        This is the CL that calls all the MRP extracts and planning
routines:
            MR002CL2 (allocate applications)
            MR036 (determine next assigned Joint supply number)
            DB079CLP (Calculate Low Level Codes)
            MR003 (Print Control Details) 
            MR120CLP (Net change run only)
            MR122CLP (Net change run only)
            MR005 consolidate stock (work files MSPWI and MSPWJ)
            MR140 extract component items triggered parents (Net
change only)
            MR009 (extract forecasts)
            MR006 (extract sales orders)
            MR002CL2 (de-allocate OE application)
            MR011 (extract Customer Schedules)
            MR002CL2 (de-allocate AC application)
            MR018CLP (extract Purchase orders)
            MR002CL2 (de-allocate PM application)
            MR025 (Inter model extract) Multi-plant/sourcing
related
            MP001 (check if MPS installed) 
            MR220 (extract WIP balances) 
            MR026 (extract item overrides) Multi plant related
            MR012 (extract critical resources) Multi-sourcing
            MR245 (del stat 1 WStn sched rec's (PCP97)) Multi
plant bug
            MR007 (extract MPS suggestions)
            MR008 (extract Work Orders details)
            MR144 (extract dependent demand)
            MR010 (extract MRP confirmed Schedules)
            MR030 (main planning routine) This is where the
planning takes              place !! It loops through all the
low levels from lowest to zero (end             items)
            MR004 (delete records from live files (MRP71/2/3
MSP89))
            MR032 (copy STOCK from workfile MSPWI to live MRP71)
            MR033 (copy Demand/supply from work file MSPWJ to
live                MRP72/73 and MSP89)
            MR035 (copy MPS to MRP model (msp72/3 to mrp72/3))
            MR142 (reset triggers)
            MR002CL2 (allocate / de-allocate applications)


How to submit MRP in a Test environment while jobs in Production are
blocking it:

1) Take option 11/MRP and hit F3 when the request problem message comes up
(sets your library list)
2) On the command line, type: CALL MR002P
3) Enter your parameters as usual and hit F17 (does not submit but saves the
file changes and LDA values)
4) On the command line, type: SBMJOB (and prompt with F4)
5) Command to run:   CALL MR002CLP
   Job name: whatever you want, I usually put my initials and MPS (AMS_MPS)
to know it was submitted manually
   Job Queue/Library: change if you don't wish to crowd QBATCH
6) Hit enter


MPS :

The above can be used to submit MPS as well but take option 11/MPS, call
MP002P and submit MP002CLP

The MPS flow is very similar to the MRP one, and many of the programs are
actually the same or twin versions prefixed MP instead of MR.

Machine Manager consideration:

Given that MPS and MRP are jobs that require parameters that will vary from
Run to run, their respective tasks cannot be added to machine manager as is.

The best way to automate them is to have a small custom routine that updates
the relevant model record (MRP70 or MSP70) with the Run parameters (current
date, end date, etc. that are usually entered in the interactive program)
AND store the necessary values in the LDA prior to calling MR002CLP in batch
mode.

Otto A Ritter Jr

   1. [SYSTEM21] MRP issues (Jim Kerr)


----------------------------------------------------------------------

message: 1
date: Mon, 12 Jan 2009 12:01:50 -0800
from: "Jim Kerr" <JKerr-FaIC0pVkSM6w7v2zf2itdNJR4SXAr38/@public.gmane.org>
subject: [SYSTEM21] MRP issues

I have two issues that have just come to light.

 

1.  No MRP demand created for items on a bill of material where the
parent does have a forecast demand. I've checked the production details and
the item looks to be defined correctly. Other item on the BOM do show the
necessary demand but a couple of items lower down the BOM are not showing
demand.  What program do I need to look at that builds the MRP73 file ?

 

2.  The MRP Planner report (MR045) all of a sudden has started showing
duplicate entires for purchase orders. No surprise there as there are
duplicate records in the MRP73 file. So again, where is the best place to
look (program) that creates these MRP73 records. I think this isuue must be
a bug, surely ? 

 

Regards.

 

Jim Kerr.




_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.