Share your Success!

[IBPIT]

Hope this is what you are looking for in this area.

We have a web-based application running in SQL that was developed in-house for our sales and receivables.  Since the company has invested so much time and money  in it, they are not interested in giving it up to switch to any other systems for this part.  This software does not include an Inventory Module and the company does not want to invest that much into the software, as most of our branches do not need it.

We use MAS200 for posting Accounts Payable and GL Journal Entries.  We had a couple acquisitions that were outside out normal product line and they were keeping a perpetual inventory.

The decision was made to tie MAS200 to our web-based application so sales from the app would decrement inventory in MAS.

We implemented the Purchase Order and Inventory Management Modules in MAS and used a file generated in the SQL database to import the activity to relieve the quantities from MAS.  We set up a field in SQL that cross-references the item number in MAS with the items in SQL.  Any activity for a specific branch is exported to a file that is then imported into Inventory Management - Inventory Transaction Entry.  This process is set up to run every night through a chain of scheduled tasks.  Once the import is run in MAS, an email with the VI import log is sent to the branch personnel in charge of the inventory.  They then review the log to make sure there were no errors and then they update the transactions.

The users also receive a report from SQL that is similar to the Stock Status Report in MAS.  It includes activity from the SQL database as well as the activity from MAS.

We have successfully implemented this for two separate GLs in MAS.

[gmasini]

Hi Kemp-

Great stuff--this is exactly what we are looking for here-innovations and tricks that you've come up with or implemented that others can learn from and potentially adopt to save time or money or add functionality to their Sage MAS 90 or Sage MAS 200 products.

Thank you for your contribution!

[morps]

Hey Kemp,

Thanks for sharing. That is a very cool solution.

Mike

[levanoff]

Hi Kemp,

How are you automating the emailing of the VI job log?

Larry

[IBPIT]

I use a perform logic attached to the VI job to create a txt file of the log.  I then have a scheduled task that converts the file to the proper ASCII format and then emails the file using a command line email program.  The program we use is Febooti command line email.  It cost us less than $100.

[levanoff]

Kemp,

Do you mind sharing the perform logic? 

Larry

[IBPIT]

Not at all.  Got it from a reference site that is no longer available.  You will need to add it on job success and job failure.  Also, make sure you name the file with the .pl extension.

log_file$="../HOME/textout/{We use a subdirectory}/{name of import job}.log"
erase log_file$,err=*next
serial log_file$
open (hfn)log_file$
log_chn=lfo
lock(log_chn)
read (59,key="",dom=*next)
read record (59,end=*next)rec$; translate rec$," ",sep; write record (log_chn)rec$; goto *same
close (log_chn)
exit

Message Edited by IBPIT on 06-05-2009 11:09 AM