Great Plains Support: web sessions and remote access technology

Jun 24
07:51

2008

Andrew Karasev

Andrew Karasev

  • Share this article on Facebook
  • Share this article on Twitter
  • Share this article on Linkedin

Microsoft Dynamics GP ERP could be pretty efficiently supported remotely on the case by case basis and via such technologies as web session, remote desktop connection, VPN.

mediaimage

Great Plains is based on Microsoft technologies: .Net,Great Plains Support: web sessions and remote access technology Articles SQL Server, Dexterity, SRS, Sharepoint and all these are hosted in Windows Server platform, where remote support is natural.  Let’s review technologies and remote support options:

1.       Application Consulting support, also referred as functional consulting.  This is where you need help with GP functionality: entering and posting transactions, such as SOP invoices, POP receipts, GL transactions; master records creation: customer, vendor, employee; modules setup: AR, AP, Inventory, etc.  This job could be efficiently done via such web session technologies as gotomeeting, that allow you to create efficient targeted training environment for remote GP functional consultant and your accounting personnel

2.       Great Plains Dexterity Customization support.  GP modifications are typically distributed via so-called chunk files and it highly recommended that Dex custom modules be tested in your test company environment – you simply copy your production company into test one and then run Dex alternative logic there.  Assuming these scenarios, we recommend you to enable either RDC (remote desktop connection) or VPN to your Server – then Dex developer doesn’t need your IT people to babysit him to do chunk deployment and beta testing and QA phases

3.       Microsoft Dynamics GP Integrations support.  Integrating with your legacy systems is very popular programming routine; this scenario may deploy such tools as GP Integration Manager, SQL stored procedures, eConnect applications (written in C#, or VB and deployed via Microsoft Visual Studio).  As IM currently relies on such new technologies as eConnect, we recommend you to allow remote integration programmers to install integration tools and test integration via remote desktop connection technologies

4.       EDI or Electronic Document Interchange.  There are a lot of articles written on EDI technical aspects, however if you think through them – they are about either exporting in fixed field text format EDI documents or import fixed field text file as Edi source to GP SOP, RM or POP modules.  Both routines could be programmed in SQL stored procedure – some challenge here is to find SQL developer, who is familiar with EDI technologies and formats

5.       GP reporting remote support.  SRS development and reports design is typically done through MS Visual Studio snap in and considering this we recommend you to allow report designer to have VPN connection or RDC to your server.  If you have historical Crystal Reports or prefer reports to be implemented in Crystal Reports, then install Crystal Reports Designer on your server, accessible for CR designer