Lot Costing Blank Title 76653

Yahoo Archive
1
That's my understanding as well. Make Direct Jobs are more sensitive to timing issues of COS/WIP processing and can show zero cost if not timed perfectly.

Rob




________________________________
From: Kathleen Tyrrell <ktyrrell@...>
To: vantage@yahoogroups.com
Sent: Wednesday, May 20, 2009 1:29:34 PM
Subject: RE: [Vantage] Lot Costing





Hello Bruce,

There has been some other discussion recently that cost when shipping
directly from the job is dependant on your timing of Capture COS/WIP
function.

Thanks~

Kathleen

360/ 453-3445

____________ _________ _________ __

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
Of Butler, Bruce
Sent: Wednesday, May 20, 2009 9:20 AM
To: vantage@yahoogroups .com
Subject: [Vantage] Lot Costing

We are a standard cost environment for 90% of what we build. The other
10% we would like to setup as lot costing. With some background with
working within a Vantage average cost environment, I assumed lot costing
would work the same. This would provide the added benefit of tracking
differences in build costs (lots) in inventory. After testing I found
there were no costs transacted at the time of shipment. From my Average
Cost experience I know you need a completed quantity and material /
burden cost entered prior to shipment. Even with this, I am unable to
get the system to show the transactional cost of shipping direct from
the job.

Any suggestions as to what I am missing?

Thank you,

Bruce B.

[Non-text portions of this message have been removed]

NOTICE OF CONFIDENTIALITY: This e-mail message, including attachments, is for the sole use of the intended recipients and may contain confidential and privileged information. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this message, including attachments. Any unauthorized review, use, disclosure or distribution is prohibited.

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]
2
Looking for some ideas on solving some 8.03.4x issues with security. We are currently on 6.1 and implementing 8.03. The new version doesn't allow setting allow/disallow cost data down in the tracker level (Job, Part, etc.). I have been trying muliple methods to replicate what we currently have in 6.1 but nothing really solves to issue fully. Here's what I've run into...

Field level security -

Beyond the fact that it is a slow and cumbersome process and there are a TON of fields that need changed, it still allows costs to be view via the 'retrieve' function. Also, the total fields often still show values. There is also a problem with the field security allowing field updates when the restricted user updates the record. (I can prevent the 'retrieve' function with Process security)

Customization -

I can create custom tracker forms, hide the fields and grids views that need removed and assign users/groups to two different trackers. One with costs, one without. This requires a lot of menu manipulations as these trackers are all over the place. It also brings up an issue with the context menu. I can add the custom tracker to the context menu but it shows both trackers availble. The context menu does not take permissions into account allows viewing of all availble on the menu. Thankfully, it will raise an exception if the user is not authorized)

BPM-

I hoped to use BPM to apply a trackerform (custom or otherwise) based on the specified user/group. This seems as if it would be the best solution but I can't seem to apply a BPM to a tracker. Is there an object for trackers?

Has anyone run into this issue and found a workable solution? I've been round and round with support and they haven't very helpful on this one.

Thanks,
Chris
3
We are a standard cost environment for 90% of what we build. The other
10% we would like to setup as lot costing. With some background with
working within a Vantage average cost environment, I assumed lot costing
would work the same. This would provide the added benefit of tracking
differences in build costs (lots) in inventory. After testing I found
there were no costs transacted at the time of shipment. From my Average
Cost experience I know you need a completed quantity and material /
burden cost entered prior to shipment. Even with this, I am unable to
get the system to show the transactional cost of shipping direct from
the job.



Any suggestions as to what I am missing?



Thank you,



Bruce B.








[Non-text portions of this message have been removed]
4
Hello Bruce,

There has been some other discussion recently that cost when shipping
directly from the job is dependant on your timing of Capture COS/WIP
function.



Thanks~



Kathleen

360/ 453-3445

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Butler, Bruce
Sent: Wednesday, May 20, 2009 9:20 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Lot Costing








We are a standard cost environment for 90% of what we build. The other
10% we would like to setup as lot costing. With some background with
working within a Vantage average cost environment, I assumed lot costing
would work the same. This would provide the added benefit of tracking
differences in build costs (lots) in inventory. After testing I found
there were no costs transacted at the time of shipment. From my Average
Cost experience I know you need a completed quantity and material /
burden cost entered prior to shipment. Even with this, I am unable to
get the system to show the transactional cost of shipping direct from
the job.

Any suggestions as to what I am missing?

Thank you,

Bruce B.

[Non-text portions of this message have been removed]




NOTICE OF CONFIDENTIALITY: This e-mail message, including attachments, is for the sole use of the intended recipients and may contain confidential and privileged information. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this message, including attachments. Any unauthorized review, use, disclosure or distribution is prohibited.


[Non-text portions of this message have been removed]