Hi Bill

Simon is right... in program DB511, LF MSP05L01 is used and the key is
populated from MSP04.
This means that a MSP05 record with the costing route as in MSP04 must
exist. It ignores all other costing routes in MSP05.

Also, check what you are entering in the item type parameter fields. If
these are left blank, only item type M and X will updated. So if you want to
update Purchased items, you should enter a P there.



date: Wed, 2 Jan 2008 08:44:46 -0000
from: "Simon Sherwood" <Simon@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
subject: Re: [SYSTEM21] Transfer Costs to Inventory - 4/MDC


It will be worth checking in production details (MSP04) what is the
route. It is only for that route that costs by default are transferred
inventory. Are the Items set up as manufactured? Do you record costs
operational level?

Are you getting any exception reports.

I have used this part of the system extensively and it always works and
there is normally some obscure reason why it is not working!!

Good luck

Simon Sherwood
----- Original Message -----
From: <Bill.Geissinger@xxxxxxxxxxxxxxxxx>
To: <system21@xxxxxxxxxxxx>
Sent: Monday, December 31, 2007 7:28 PM
Subject: [SYSTEM21] Transfer Costs to Inventory - 4/MDC

Our company is updating their standard costs on their parts. We have
company that is having problems. When looking at Indented inputs
it shows new costs, but when we run the program to transfer the costs
inventory, DB047, the costs are not being updated. I see that it
looks at
the MSP05 file (Item Cost file) and updates the cost in that file to
stockroom balance file, but the costs don't match those on the
inputs report.

Can anyone shed some light on what might be causing our problem?


This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].