Sage 100

Does anyone have a client using Sage 100 with Doc-Link and Doc-Link Smart forms?

@JimWoodhead ????

Yes we have one . What questions do you have?

Yes. We have several. What are your challenges?

Doc-Link is writing the data from the Smart Form to a SQL staging table. From there I will pick it up in VI and import into PO data entry. Is this the way you have handled it and were you able to automate the process? Sage 100 Advanced BTW. TIA.

Altec provides a set of tools that uses BOI to push AP invoices or Purchase Orders directly into Sage 100 with out VI. We have had problems in the past with Smart Link due to speed issues with BOI calling the Altec web tools. Smart LInk runs from Sage 100 and calls Doclink to pull data from providex. The GL Smart form works from doclink and pushes data into providex using the BOI interface and is both faster and more efficient. In a recent implementation, we had to pull the resident BOI / Providex expert @AlnoorCassim in to help resolve a configuration issue in Sage 100 that caused some problems. I don't recall the details but in the end, Alnoor spent 2 hours searching and finally found a config setting that wasn't set properly by the Sage 100 installation routine. Once corrected, the GL Smart Form or GL Stamp started working like a champ.

@JaneCavanaugh what I have done is to create a SQL script that is run upon completion of the VI Job. I do this via a batch file.. The SQL Script sets a flag in the Staging table that the PO's have been imported then the next time the VI is run it won't reimport the PO's. Note the key to this is that SQL server must see the PO Header table. If you are using premium then it is no issue. If you are running PVX as you are then you will need to set up linked servers via ODBC to allow SQL to MAS table. If you create these scripts to set the status to imported then I don't see any issue with you setting the VI job to be run on a timed basis.