× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Cost bucket 0 will be off by some rounding differences.     You increase
this exposure by increasing the number of buckets.     The procedure
averages / calculates a new cost by level by bucket.      Purchased items
( A/P Invoice entry)  will only deal with Material bucket this level.
Cst900 will deal with every bucket, every level separately.

When you have an item that goes from made to purchases, the result is a
mess.   If BPCS would change the A/P Invoice entry to average the total
cost(of all buckets all levels)  with the purchased cost,  then update this
level material and zero out all the other levels/buckets.   This would
avoid the problems with incoming mixed cost.     Since this is probably not
a possibility,   you should move all the cost to this level material before
entering the invoice.       Moving from  purchased to manufactured is also
a problem.      The pat answer of two separate items is not an acceptable
answer for the shop floor inventory.     When the item is in inventory it
is treated as the same part and not issued separated.

With the rounding opportunities of each level and bucket there will always
be some differences.   We have a program the reads all the buckets/level
and updates bucket 0 each level to match..


Roger Henady
Thorco Industries
(417) 682-1340



>  Hi,
>       (V6.04, Apr Cum, Mixed mode)
>       I know there has been discussion on cost bucket 0 not the sum of
cost
>  buckets 1 - 99 in the past. When we have had this mismatch in the past,
the
>  only way to fix it was a fix program to re-sync the buckets. Now
something
>  strange has happened.
>       In mid December, an item changed from purchased with an outside
>  operation, no BOM to purchased with an inside operation. After the cost
>  build, the cost looked like this:
>             3        0            .24363             .00000
>             3        1           7.06280             .00000
>             3        3            .11074             .00000
>             3        4            .13289             .00000
>       There was no inventory for this item, so it didn't stand out in any
>  reports.
>       Last week, we had a PO receipt for the item, and it received it at
>  .24363.  When the cost build ran on Sunday, the costs now look like
this:
>             3        0           7.30643             .00000
>             3        1           7.06280             .00000
>             3        3            .11074             .00000
>             3        4            .13289             .00000
>       Any ideas on why the cost build correctly calculated cost bucket 0
>  now, and not before? We do a cost build weekly, so it isn't the first
build
>  that occurred. The only difference I can see is that now we have
inventory
>  on hand.
>  Thanks for any ideas.
>  <===================================================>
>
>  Terri Harteau

_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
or email: BPCS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.









As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.