Standard Costs

[Chris Kelleher]

MFG-PRO V8.6E

We currently manufacture our products on one site. Our finished goods
contain sub-assemblies. We wish to manufacture these sub-assemblies
on a sister site and are planning to use DRP to do this.

Can anyone explain what we need to do to the costs for these sub-assemblies
which will be going from "M" to "D" on primary site and will become "M" on new
site. We realise all the "P" items used on the sub-assemblies will have to be
copied
to the new site but don't understand how routing and product structure cost
rollups
will work on the new set up.

If we want to create the sister site on the same MFG-PRO database, how do we
control the costs
of these "D" items and there parents.


Regards

Mel North
Business Analyst

 

[Chris Kelleher]

We use DRP to provide manufactured goods between sites on a single
database. This is how we decided to handle it.

The type "D" is on the receiving site and the "M" would be on the
source site.
The source site's cost would be rolled as normal (after the P goods
are costed there).
The total cost is then manually added under this level material to the
receiving site.
The cost of the parent using the sub-assembly would then be rolled in
the primary site. The sub-assembly's cost would be wholly contained
in lower level material.

I have created some cim loads for the necessary cost copying that we
use when doing major rollups. If you would like, I will be happy to
provide any of this information in more detail.

If you are running MRP, I have one further note concerning using "D"
parts in a single database
mode. Inter-site requests are created by MRP in a planned status.
There is even an approval screen for these planned inter-site
requests. However, MRP on the source site does not consider the
approval status. The minute an inter-site request is created (planned
or not), the other site sees it as a valid demand.

Debi Loope
PI Inc.
8.5e

 

[JEMERSON]

Chris, after some years, do you know if the QAD found a solution for this case?

 

[dwjones]

I solved this issue when I was with QAD. If you have the DRP module, when you upgrade to eB2 or above you get Linked Site Costing (LSC). This dynamically links the in_mstr at the target site to the cost detail at the source site. Prior to eB2 you have to copy the cost set from the source site(s) to all the target sites. Now you just define rules for what items you get from where, and LSC does the rest.

The cost copying process creates sct_det records for every item/ site combination. LSC eliminates these redundant records. Standards are created at the manufacturing sites as usual, and then any inventory transactions simply use those cost records to evaluate themselves.