A lumber yard buys lumber and on the PO it has to read like this:

102 PC of 1X6X18 (the item) at $1.429/BF = $1,311,82

This item measures 9 board feet per piece - that's what makes the calculation work (102PC * 9BF/PC * $1.429/BF = $1,311.82)

How can I get to the result where they enter a quantity of 102 on the PO, and the PO reads as they want?

I can do this when selling the item in OrderEntry but I'm blanking out on how to do it when purchasing it in PO.

Steve

Steve:
What unit(s) of measure do you have for this item? How are you selling these items in OE?

The stocking unit is PC. The pricing unit is actually MBF (thousand board feet), that way the conversion factor is greater than 1 (Adagio won't allow the factor to be less than 1), and in any case MBF is what they really use, not BF, but I wanted to simplify.

You can sell an item in OE for quantity 102 PC at $1,429/MBF and it will display properly on the invoice.

I know this doesn't answer your question, but how come the stocking unit is "Piece" rather than "Board feet"? If it was BF then cutting a board in half could be supported. I guess they only ever sell a whole board (perhaps 100's at a time more accurately)?

Piece is how they count and sell the item. These are not boards, they are pieces of wood such as poles, studs, etc. But the costing language is MBF (thousand board feet).

Hi Steve:
Sorry, I didn't get any further than you. I set up an item and I can sell it as you described. However the PO screen uses only one unit of measure. OE has the concept of "Selling" and "Pricing" units of measure that can be different. Maybe Brian would have a suggestion?

I am bringing this back to life, hoping someone has an answer after all of these years. The client is deciding whether to switch to a custom lumber software package instead of using Adagio, and getting this to work would really help convince them to stick with Adagio.

I have their data and I would like to review this with someone at AOC. Who would be the best person?

Steve

Steve:

I took a look at PO but nothing has changed in this regard.

You could use PrintBoss to make the PO document read the way it should.

Order 102 PC at the per piece price. On the PO document print out we could get PrintBoss to divide the per piece price by the MBF factor (which would have to be stored in an optional amount field). I don't think we have done this with 3 decimal place prices before so we would need to do some testing to make sure rounding doesn't become a problem.

Hi Steve

What is the
Costing Unit
Pricing Unit
and
Purchasing Unit
for the 1X6X18

Hi Steve,

There is a solution that our client paid for the development several years ago, that we helped design with Softrak and was in production for several years (in Adagio OE).

At Softrak, it is called "Catchweights", but we called it OE Alternate Shipments. It worked with OE, IC, and PO, and was really sweet. We can't get a price from Softrak on this OE Add-on. Maybe you can. We think it could sell into easily 100 sites.

We can show you as we still have a demo version. It works the same way as you can receipt items in PO in alternate shipment units of measure.

What it provides, is a solution that will work for most meat processors (ours was a meat packing plant), lumber yards, and bulk shipments (aggregates or mulch).

As an example, it allows you to accept sales orders in cases but ship in pound or kilos, or whatever. Or for Lumberyards, you can take order in LIfts or packages, and ship with pricing based upon sq.feet or linear feet. It calculates backorder quantities based upon the original unit of measure. It was called Catchweights because in Meatpacking plants, you ship cases but need to invoice the catchweight or the weight of the packaged product (on a scale) and no one would be able to fill a carton to an exact weight, but would invoice the carton based upon the actual weight.

There are many sites that could use this product module.

Call us and we can show you a demo remotely, after you return from AOC.

Best,
Brian