Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Lock Protected Fields problem (v7.6.100 P.SQL)

Status
Not open for further replies.

rustylee

Programmer
Sep 11, 2001
59
US
This is from Macola's help file:

"With this [standard cost] method, Progression calculates the value of your inventory by multiplying the quantity of the item received by the item's standard cost, ignoring the item’s average and last costs. Progression does not update the item’s standard cost when you receive a quantity into inventory. To update the standard cost, you must enter a cost adjustment type transaction through the Enter Inventory Transactions option, or manually change the standard cost through Item/Location Maintenance."

Macola provides a "lock protected fields" option that will disable some fields from being changed, mainly calculated fields and accumulators. Three fields that are locked with this option are "Average Cost", "Last Cost", and "Standard Cost". In the PO module we use standard cost to create POs. This is because we have agreements with our vendors to purchase a product at a fixed price and the standard cost field is where we store that information. Last cost doesn't work because we add landed costs, which adds to the standard cost when it is receieved.

We use Average Cost to cost our inventory, and like I mentioned, we use Standard Cost for POs. Our process for setting up an item includes entering the Standard Cost (purchase price) once it is known. When lock protected fields is set, it is impossible to enter the initial standard cost in the field since is disabled. It is impossible to make a cost adjustment using the Inventory Transactions application because it only allows a change to the Average Cost, since that is how inventory is configured.

In my mind we are either not using the system correctly per its design or there is a design flaw that does not address our configuration options.

Any ideas out there?
 
Rusty,

I have submitted this one to Macola TS and we will see what they say, however I do have a solution for you so that your POs default to the right cost.

Rather than using Standatd cost as a vehicle to do this, go into PO->Maintain->Item Vendor Master. This is where vendor contract information, including effectivity dates and pricing, are supposed to be entered.

Other options available here are Vendor Item Numbers, (Optionally printable on POs) and Receipt tolerance codes.

Let me know if you have any questions Software Training and Support for Macola, Crystal Reports and Goldmine
714-348-0964
dgilsdorf@mchsi.com
 
Now that sounds reasonable. It seems to point to a problem with our understanding of the system than an actual design flaw. We are using the Item Vendor Master for this very thing so I will explore that avenue.

Thanks Don!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top