EDI - Basis for unit price

[ntmurphy]

Hello,

I was wondering if anyone knows why this field is even here. All it seems to do is add the price basis on to my 810s. For instance, if a customer is sending a product through EDI with a unit of measure of "FT" and a price basis of "HP" (per hundred feet), Macola completely ignores the price basis code on the inbound. On the outbound, it will tack on an "HP" code in Gentran, but no actual conversion takes place. Since the price would be per hundred feet, the order has to be walked through the system manually.

It seems to me this would be a big issue, considering that many companies would need to deal with price units other than each. This limitation is starting to be a problem; is there any workaround that anyone knows about?

Thank you!
Nick

 

[dgillz]

What has Exact said about this?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"What version of URGENT!!! are you using?

 

[ntmurphy]

I contacted Exact and they said I had to go through my reseller. The rep that handles our account didn't really know and I was unable to get a satisfactory answer, so I'm asking here. I would think surely that someone else has run into this problem.

 

[nickavila]

Nick,

What is your stocking and selling unit of measure?

Nick

http://www.infospring.com

 

[ntmurphy]

Hi Nick,

Thanks for the reply. Stocking and selling in this case would be FT. I don't think I've ever used the ratios in IM; however I do use the conversions in EDI. I guess there may be a way to use the ratios to accomplish this, but I have no experience with them.

Thanks,
Nick

 

[nickavila]

Nick,

I do not believe Macola EDI handles UOM price conversions. If your customer orders in feet and you stock or sell in HP than you can use the EDI Item x-ref UOM conversion set-up.

You would just divide the amount ordered (feet) by 100 to get the HP amount.

To round to the nearest whole number you can use the Rounding Method drop down box to either round up or down.

If you stock in feet, but your selling unit of measure is HP, than use then check the Sales UOM? box to use the selling unit of measure instead of the stocking.

As you discovered the Basis of Unit Price is only to overwrite the code.

If that doesn't work you may have to go to automated flat file munipulation or some kind of SQL script, trigger or procedure to automate the process.

Nick

http://www.infospring.com

 

[ntmurphy]

Nick,

Thanks for the reply. That's similar to what my reseller said as well. I realize the practices in all industries are different, but I don't think the solution would work for my application. In the example I gave, I'm not doing a UOM conversion because my customer's UOM and my UOM are the same. What I'm referring to is the price UOM (or price basis) which my customers and suppliers treat as an entirely different unit. The customer's order is for qty 100 FT of wire, priced at 200.00/hundred feet. It just seems that this functionality was left out of Macola and that the software assumes you are pricing everything per each, regardless of the UOM.

In the example I gave, when the order is imported into Macola I just set my price as 2.00 (UOM is FT). This works until I create the invoice. What I was hoping was that when I set the Price basis code to HP that Macola would convert just the price on the oubound. What I end up with is an invoice that says 100 FT of wire, priced at 2.00/hundred feet (because it just sets the price basis code as HP, but does no conversions). In any event I think having the HP code available is misleading and useless. If the program can't convert, then why have it? I can't think of any situation in which that would be useful.

I also have many suppliers that deal in small parts and price per hundred, thousand, etc. The UOM is still EA, but they are priced per hundred to keep from using long decimal numbers. Actually, every entity I deal with, whether customer or supplier, seems to be able to do this. I have to have all of my customers set up the items priced per each so I don't have to manually edit every invoice. It's just a pain to not have the functionality that everyone else does.

Thank you,
Nick

 

[nickavila]

Nick,

I better understand what you need. If you want to automate the process I can think of three possible solutions.

1. Have Exact build a custom 810 format to convert the price unit of measure.

2. Build a custom Gentran Template to handle the conversion. This can be done by Exact or your VAR if they have the tools to build templates

3. Munipulate the flat file before it is imported into Gentran. This is low tech, but something you may be able to do yourself.

Nick

 

[ntmurphy]

Nick,

Thanks for the suggestions. I'll speak with my VAR about this.

Nick