Two questions.. 1

[pronet74]

First one. Within Macola our company would like me to implement something that will add a $10.00 surcharge to certain customers due to fuel increases. We were going to use a line item for this, but some inside sales forget to include this. But I can't add this onto any backorders, or can't charge it twice for one order.

Is there any easy way to do this? I have PSQL with flexability.

Second question, when we do a lookup on Order History by Customer PO, we have to type in the exact PO, otherwise a partial search doesn't bring up anything close to what the PO is. Due to inside sales misspellings, etc.. this can cause a problem. Can I modify this to allow partial searches?

 

[kscheeler]

For #1. I would use a field on the customer master to designate that the customer should have the additional line item added to their orders. Using flex, I would add a function on the order save event checking to see if the customer meets this requirement and if they do check the items on the order to see if the "surcharge" item is there. If not, don't allow them to exit the order and put in a message box mentioning that they need to add the "surcharge" item.

For #2, you can't change the actual function Macola is using to find the PO's in history but that field has a lookup button which you can customize. They should be able to do the search through the F7 function and could change the field to a contains to find all PO's that have the portion of the PO number that you are looking for.

Kevin Scheeler

 

[MacolaHelp]

#2 is a really wierd situation. If you key in the customer first, then hit the spyglasses & choose "start with", enter the first few digits of the PO #, then POs are returned from that point on in ascii sort order. If you don't put a customer # in, then that same method returns the POs in customer #/purch ord # ascii order. The % wildcard searches do not work in this search screen (F7 lookup first). The %wild card does not work in the choice of identifying the customer & % wildcard without F7 lookup. If you select all customers, F7 search in PO #, use % wildcard search, it returns customers who contain your wildcard sorted in customer #/purch ord # ascii order. I tested this in 7.6.100a pervasive.

Peak's Best of OE has a power inquiry by PO # that works great. Put in 500 for PO without selecting a specific customer, it returns all POs that begin with 500 & sorts them in ascending ascii sort order. Peak uses its own data files to build these views, searches, etc, & they have obviously keyed their file to return the data this way. I tried to replicate their search in the macola oe-hist-cust-po search & no dice. Macola has all those segmented keys in the oehdrhst, so it just doesn't work.

Suggestions: move to sql & use search edit there if the keys in the file are improved. Add Peak Best OE, but it is source code & the future is uncertain of source code mods in Macola ES. Modify your ddfs to add another key that includes PO# & some other unique identifier(s) so you can build your search.

 

[crystalreporting]

How about creating a tax code for those customers you want to add the surcharge to?

Peter Shirley

http://www.linkcorp.com

 

[dgillz]

Peter,

Tax codes can work 3 ways:

% of Cost
% of Sale/Purchase Amt
Cost per unit

I am not sure how this would help pronet74, but I like your thinking out of the box....please elaborate for us.

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

http://www.trianglepartners.com

 

[vbajock]

This really is a Flex problem. You would need to add a field to the Customer Master Maintenance screen, based on a User defined field, to flag the customer as a surcharge customer. Then you would have to add code to the order entry screen that would automatically check to see if the customer is a surcharge customer, and add a line item if it is.

 

[pronet74]

Or I was thinking instead of that, use flex to check an Access database with all the customer numbers in it. If there is a match then display a message box saying you need to add a surcharge line item.

I also noticed in the Billing Information you can add a freight charge. Which way would you go?

 

[vbajock]

I'd stay away from freight, those fields write to GL accounts that usually are set up by the controller specifically for freight, and you might mess his accounting up. The Access database would be the easiest, since you would only pop a message box based on a simple ADO Select command. The drawbacks are that you now have a new place to maintain customer information. Where are you located?

 

[pronet74]

Where am I located? In Selinsgrove, PA. We have a main access database that has about 100 different reports that we have linked to Macola. I'll just add that in there, when they add a new customer they'll have to add them into Access as well.

We are going to be expanding probably down south in about 2 years from now, and another thing I have to work out is the ERP system we have now going to be enough? We sell doors, windows, etc.. to modulars and contractors. We are looking into getting into manufacturing as well. I'm thinking of a dual broadband connection (for redunancy) by VPN to connect the two sites, so that they can work on the same database system (want them to be clustered as well at each location).

We are using PSQL Macola 7.5.103, and wanted to upgrade but we have mods programmed by macola that would have to be redone. They want another $5,000 for them to do that.

 

[vbajock]

Send me your email addr to kwvining@hotmail.com, I'll send you the ADO code frags and my opinion on the above post.

 

[crystalreporting]

To answer dgillz - I have a customer in WV that charges a flat amount for each order - they use a tax code to achieve this - however, they make custom furniture, and always sell in quantities of 1. They use the U=Amt Per Unit option to achieve this.

Peter Shirley

http://www.linkcorp.com