Re: MRP540 - cd405

The settings needed are somewhat different if you have everything in one
facility, or if you use several facilities. We have several facilities on
405CD.

In SYS800 (BPCS System Parameters) there's a place to set your default
warehouse for MRP540 PUR640 DRP540 JIT540, around screen 16 for us: screen
SYS800-09. At time of shop order release you can over-ride this, but it can
be a major pain, if different warehouses are needed for different kinds of
items. When starting, use INV110 to get warehouse setup, then come back
here and make sure it has the correct warehouse.

That's our case ... we have facilities 20 30 40 50 60
Warehouses starting digit is what facility it is in
Warehouses last digit is what type of item goes there
Warehouse 21 is completed items (type 1) ready to ship from facility 20
Warehouse 22 is WIP (work in progress) not yet ready to ship.
We create shop orders to make end items into warehouse 21, but want all
components consumed from warehouse 22

To get BPCS to work according to our needs, we wrote MRP80W program to run
before after MRP500 MRP600. There are switches in the CL to tell the RPG
what facility is being processed, U2 for facility 20, etc.

Our MRP80W program uses matching records on CIC (item planning by facility)
and KFP (current orders planned by MRP) to find items currently active in
MRP, then gets item type from IIM (item master) to determine what the
warehouse should be for CIC.ICPLN and KFP.FWHSE making corrections as
needed.

Items need to be coded as manufactured, or purchased.
Item type in IIM Item Master via INV100
Manufactured flag in Item type ZPA via INV171 (Y-manufactured N-Purchased
blank if neither, such as phantoms you do NOT want showing up in BOM of
order release ... we use phantoms in our BOM to record history of
engineering changes on an item.)

Be careful, when changing this for some item, to check costs as well as
engineering particulars, because different cost buckets are involved. If
you don't replace costs associated with old way of getting an item, then it
can end up with costs doubled up, both the costs to manufacture, and the
costs to purchase.

-
Al Mac
-----Original Message-----
From: bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx] On Behalf Of Don
Cavaiani
Sent: Wednesday, December 02, 2009 1:15 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] MRP540 - cd405


We have coded our End Items as item type = E. We did not use shop orders
before - for the final assembly of the end items in the our warehouse 30 (we
have warehouse 10, 20, and 30). I see in the ZPA file that the TPMFG flag
for the E Item Types was set to "N" which caused the error message "This
item is not a manufactured item type" when I tried to release it to a Shop
Order in MRP540. We are looking into creating Shop orders now for our
warehouse 30 as well.

I then changed the ZPA value for Item Type "E" to show manufactured - TPMFG
= "Y". Now I see them in MRP540 and can release them. The only problem I
see is that the warehouse defaulted to 10, and it should be 30.

Do you see any other issues which I may create by changing the system this
way?

TIA,
Don
Don F. Cavaiani
IT Manager
Amerequip Corp.
920-894-7063

"It's amazing what you can accomplish if you don't care who gets the
credit." Harry S. Truman