OE Duplications - Check for same PO Number for Customer

[Stamina007]

Hi all

We use Advantage version 5.0 on MSSQL . We have a callcenter and experiencing problems from time to time when the same (not so clever) customer phones/faxes/emails through the same order more than one time. They do however supply the same Purchase Order number, but Accpac have no mechanism build in to warn you when you type the same Purchase Order Number for the same customer. The PO field is basically just a reference field nothing more.

Is there some way that we can put a trigger /check /macro /application in place to run (for instance when the user tabs off the PO field to check the OEINVH Table to see if the PO number for the customer already exist). I can write an app that works separate from the OE screen but then the user needs to copy and paste the Customer Number and the PO number everytime. Since its a callcenter environment this will not work. It would therefore be awesome to have it intergrated with the OE capturing screen.

ANY HELP would be much appreciated!
JayCee

 

[DjangMan]

As you are on version 5.0 you could consider "macro-izing" the order entry screen. You could capture the exact event you described above and check your list of POs either through an ODBC link or an ADO link.

You need to be using the version 5.0 entry screens instead of the 5.2 screens.

Cheers,

Djangman

 

[chitrsen]

Hi Stamina007,

if you are using AAS 51a or greater, you can use GETCONTROL(), method in VB application and get reference of control
( i.e, PO field ) and use its events to check the PO number.
hope it helps

cheers
Chitrsen