Company: Link Technologies
Case No: L11868. Project: 12.10: LinkSOFT version 12.1
Logged By: Sanjay (Link Technologies) on 19 Dec 2019 11:25AM
Priority: Medium
Product: Framework
Group: Change Request
Time Taken: 101.00 (Weight: 300.00)
Version: 12.10.1020
Assigned To: Rashna (Edge Business Solutions)
Circulation: Alvis, Development, Rashna, Sanjay
Resolve By: Tuesday, 10 March 2020 04:13 PM [1590 days since logged date]
Status: Closed
Subject: SAGE300 (2019)/ LinkSOFT Integration for VMS and Full Integration(Similar to Linksoft to JIWA/Epicor)  
Summary:    

Meeting Attendees

Ateen Kumar (General Manager) Datec (Fiji) Limited. 

Phone: (679) 331 4411  l Mobile: (679) 999 8280  | Skype id: ateen.kumar


Sanjay Singh (MD) Link Technologies

Phone: 0XXX-XXX-XXX  | Skype id: Sanjay.LinkTechnologies


Asheel Singh (Head of Development and Professional Services) Datec (Fiji) Limited. 

Phone: 9995 757

Objective: Build LinkSOFT Integration to SAGE so Datec can implement LinkPOS at their existing Sage Customers.

Agreed on the following:

  1. Datec and Link would work together to get the SAGE API set up on Link development environment so Link can build the POS Integration
  2. Combined effort will be used and Datec will get exclusive access to sell and implement LinkPOS with SAGE since Datec is assisting with the integration Development
  3. Standard LinkSOFT Licencing will apply to the Sage Integration. The current licence price is estimated at $2500 per site We will review the cost of integration once we know the effort required to build and maintain the SAGE integration
  4. The Integration needs to work similarly to the current ORION POS integration to Sage
  5. The integration is built with Vodafone in mind, however, the integration should be able to handle Cash and Credit sales (unlike Orion which handles only cash sales)
  6. Kirit will assist from a user functional since Link does not have expertise in SAGE. Link and Datec will work closely to validate LinkPOS data flow between LinkSOFT and Sage and implement controls to ensure data integrity is endorced
  7. Link will use the Standard Sage WEB API to push and pull data from Sage
  8. Link will provide VM required to install Sage and Sage SDK
  9. Timeline for the first round of testing is 31st Jan 2020. Link will build this integration for LinkSOFT V11 only (Current version) and will  maintain support for Current Version - 1 for future releases
  10. Sanjay has confirmed that he is happy to discuss pricing that best suits the market provided we follow Reseller agreement controls established and agreed on 1st August 2019.

Support assistance: Sage 300 ERP DPP support cases to DPPSupport.300ERP@sage.com with your partner account #4000265310

-------------------------------------------------------------------------------------------------------------------------------------------------------
## Web API Samples

The Admin user does not have Sage 300 Web API privileges. In order to make various Sage 300 Web API
requests, you will need to configure a new user and give it the proper user authorizations. Documentation
for the samples will assume you use **SAMLTD** as the database and **WEBAPI/WEBAPI** as the credentials.

Configuring a new user can be accomplished as follows:

* In Sage 300, navigate to Administrative Services -> Users
* Enter **WEBAPI** as the User ID, **WEBAPI** as the User Name, **WEBAPI** as the Password and **WEBAPI** in Verify
* Click Save when finished
* Go to Administrative Services -> Security Groups
* Ensure that for each application that has Sage 300 Web API rights that there is a group ID associated with it
* Go to Administrative Services -> User Authorizations
* For the WEBAPI user, assign the group ID that has Sage 300 Web API rights to each corresponding application
-------------------------------------------------------------------------------------------------------------------------------------------------------

SDK Login details:

http://dppwiki.sage300erp.com/wiki/Main_Page

username : datec.com.fj

password : 4000265310


SQL Server username sa
Password sa
Sage Accountright 2019.3 username ADMIN ADMIN
-------------------------------------------------------------------------------------------------------------------------------------------------------


Audit Notes:Edited by sanjay on 18/03/20 13:30. Edited by sanjay on 17/02/20 11:08. Edited by sanjay on 06/02/20 16:51. Edited by sanjay on 29/01/20 20:54. Edited by sanjay on 29/01/20 20:54. Edited by sanjay on 21/01/20 15:33. Edited by sanjay on 21/01/20 15:29. Edited by sanjay on 21/01/20 15:28. Edited by sanjay on 15/01/20 11:26. Edited by sanjay on 15/01/20 11:08. Edited by sanjay on 15/01/20 09:45. Edited by sanjay on 15/01/20 08:47. Edited by sanjay on 08/01/20 08:35. Edited by sanjay on 08/01/20 08:17. Edited by sanjay on 07/01/20 17:10. Edited by sanjay on 06/01/20 17:20. Edited by sanjay on 06/01/20 17:13. Edited by sanjay on 19/12/19 11:25. 
19 Dec 201911:28AM Comment 1 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 20-12-2019 11:27 AM Time Taken: 6.00

Completed the following tasks:

  1. Datec have installed Sage on QA6 and taken Alvis and I through the SAGE systems including Database elements
  2. Datec is organising the API SDK

06 Jan 202005:27PM Comment 2 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 07-01-2020 05:20 PM Time Taken: 8.00

Completed the following:

  1. GTM session with Krishneil to install the Sage SDK. We chose to exclude Visual Basic 6 components as we will not be developing OCX components. We only need the the Web API for Integration
  2. Tested the Web API at this URL on QA6 Development Environment: http://localhost/Sage300WebApi/v1.0/-/SAMLTD/AR/ARCustomers  API call failed with invalid Credentials
  3. Downloaded documents for Sage 300 2019 ADK into QA6 D:\Sage300-SDK-Master
  4. Sanjay to continue with research and email support if we are unable to get this working

SDK Login details:

http://dppwiki.sage300erp.com/wiki/Main_Page

username : datec.com.fj

password : 4000265310


SQL Server username sa
Password sa
Sage Accountright 2019.3 username ADMIN ADMIN

06 Jan 202006:02PM Comment 3 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 07-01-2020 05:59 PM Time Taken: 7.00

Completed the following tasks:

  1. WEB API call to SAGE completed successfully using this URL: http://localhost/Sage300WebApi/v1.0/-/SAMLTD/AR/ARCustomers
  2. Admin user access to WEB API was given via the SAGE Security module and the D:\Sage 300 Program\Online\WebApi\web.config (AppSettings) parameter: <add key="AllowWebApiAccessForAdmin" value="true" /> was set to true
  3. 100 customer records were returned
  4. Further testing will continue tomorrow before we architect the API calls between LinkSOFT and SAGE

24 Jan 202003:36PM Comment 4 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 29-01-2020 03:34 PM Time Taken: 12.00
Completed the following tasks
  1. Completed VMS Signing requirements for Sage
  2. Scripted and packaged 11.5

Next Step:

  1. User training for Rashna on Monday 27th Jan 2020
  2. Rashna to perform UAT and Documentation
  3. Alvis to perform User Training and Testing with Datec Staff

29 Jan 202010:02AM Comment 5 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 31-01-2020 09:58 AM Time Taken: 6.00
Tested case with Alvis.
QA Results
Tests carried out according to requirements specified on the case header

Test Results Summary

Table 1 - Summarised list of issues
NoTest DescriptionPass/Fail
1Request licence and the licence should be imported for module APIPass
2Create LINKSOFT and SAGE integration, this should be completed without errorsPass
3Invoices from SAGE should be integrated in LINKSOFT. Invoices should be signed with VMSPass

Environment Details

  1. OS version: Windows Server 2012
  2. Application version: 11.5.0128
  3. Setup: Demo
  4. Server : 10.0.0.16
  5. Database: LINKSOFT_SAGE
Completed documentation under below sections:
  • Licence Registration
  • Integration Setup
  • LinkPOS and SAGE Integration

Next Step: 

  1. Closure

    29 Jan 202008:49PM Comment 6 by Sanjay (Link Technologies) Assigned To: Alvis (Link Technologies) Followup Date: 31-01-2020 08:48 PM
    Hi Alvis, proceed with the build for LinkSOFT to Sage Integration

    03 Feb 202004:46PM Comment 7 by Sanjay (Link Technologies) Assigned To: Alvis (Link Technologies) Followup Date: 04-02-2020 04:44 PM Time Taken: 4.00

    Added quotations to SAGE integration.

    Demo server has been setup:

    Server: LinkQA6

    To access LinkWEB portal for SAGE use this link: http://localhost/LinkWEB-SAGE
    Username: admin
    Password: admin
    VMS Email will be sent to: priti.kumar@datec.com.fj

    12 Feb 202011:36AM Comment 8 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 13-02-2020 10:27 AM Time Taken: 4.00
    QA Results
    Tests carried out according to requirements specified on the case header

    Test Results Summary

    Table 1 - Summarised list of issues
    NoTest DescriptionFRCS ResponseLink Invoice LayoutPass/Fail
    1

    Quotation
    "Image has been removed to reduce document size."


    		"Image has been removed to reduce document size."
    		"Image has been removed to reduce document size."
    		Pass
    2

    Invoice
    "Image has been removed to reduce document size."

    		"Image has been removed to reduce document size."
    		"Image has been removed to reduce document size."
    		Pass
    3Credit Note of Invoice created in 2. above
    "Image has been removed to reduce document size."
    		"Image has been removed to reduce document size."
    		"Image has been removed to reduce document size."
    		Pass
    4AR Invoice
    "Image has been removed to reduce document size."
    		"Image has been removed to reduce document size."
    		"Image has been removed to reduce document size."
    		Pass
    5

    Credit Note for AR Invoice created in 4. above
    "Image has been removed to reduce document size."

    		"Image has been removed to reduce document size."
    		"Image has been removed to reduce document size."
    		Pass

    Environment Details

    1. OS version: Windows Server 2012
    2. Application version: 11.5.0212
    3. Setup: Sage integration to LinkSOFT
    4. Server : 10.0.0.16
    5. Database: LINKSOFT
    6. Company: 1002

    Next Step: 

    1. Review

      06 Mar 202004:26PM Comment 9 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 10-03-2020 04:13 PM Time Taken: 48.00

      Development work for this case has been completed.

      The change will be available in version:11.5.0306

      1. The following changes were made(Include Database object names, Program classes and any other relevant information):

      1. Built LinkSOFT integration to Sage in the following areas:
        1. POS Sales, Returns and Payments
        2. Payroll Journals
        3. Customer is synchronised both ways
        4. Supplier synced both ways
        5. AP Invoices are created when LinkSOFT Purchase orders are posted and from Payroll Creditor Payments
        6. LinkSOFT Adjustment (Void Payment, refund etc) 

      2. Affected Areas:

      1. This integration allows LINKSOFT Inventory Mode only 

      3. The issue was caused by:

      1. New Feature

      4. Notes: This integration is similar to LinkSOFT / JIWA Integration
      5. Next Step      : UAT. QA6 environment has Sage installation. Please install and configure LinkSOFT for testing in QA1,2 or 3


      18 Mar 202001:30PM Comment 10 by Sanjay (Link Technologies) ETC was changed from 04/02/2020 to 10/03/2020
      18 Mar 202003:47PM Comment 11 by Rashna (Edge Business Solutions) Assigned To: Rashna (Edge Business Solutions) Followup Date: 19-03-2020 03:18 PM Time Taken: 4.00
      QA Results
      Tests carried out according to requirements specified on the case header

      Test Results Summary

      Table 1 - Summarised list of issues
      NoTest DescriptionPass/Fail
      1Setup SAGE and LinkSOFT integration.Pass
      2Process Cash Sale, Credit Sale, Returns and Layby. This should be successfully integratedPass
      3

      Create a customer in LinkSOFT as CU0001. This should be integrated to Sage.

      Customers in SAGE should be integrated to LinkSOFT.

      		Pass
      4

      Create a supplier in LinkSOFT as SL001. This should be integrated to Sage.

      Suppliers in SAGE should be integrated to LinkSOFT.

      		Pass
      5

      Create a inventory adjustment in LinkSOFT. Post this to FMIS. This created a journal in SAGE.
      Create a stock take in LinkSOFT. Post this to FMIS. This created a journal in SAGE.
      Create a Purchase Order in LinkSOFT. Post this to FMIS. This created a journal and AP Invoice in SAGE.

      		Pass
      6

      Process following transactions in POS

      1. Account Payment
      2. Void Payment
      3. Refund Payment
      4. Credit Note

      These should create AR Adjustments

      Pass

      7Integrate Payroll JournalsPass

      Environment Details

      1. OS version: Windows Server 2012
      2. Application version: 11.5.0318
      3. Setup: Demo
      4. Server : 10.0.0.16
      5. Database: LINKSOFT-SAGE

      Next Step: 

      1. Documentation

        23 Apr 202010:05AM Comment 12 by Rashna (Edge Business Solutions) Assigned To: Rashna (Edge Business Solutions) Followup Date: 24-04-2020 10:02 AM Time Taken: 2.00

        Hi Sanjay, 

        Documentation has been updated at:

        1. Framework\Integration\SAGE_Integration.htm
        2. Framework\Integration\LinkSOFT_Inventory_Integration_to_SAGE.htm
        3. Framework\Integration\LinkSOFT_Payroll_Integration_to_SAGE.htm
        4. Framework\Integration\SAGE FRCS VMS Integration.htm

        Thanks
        Rashna


        If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L11868 in the subject line of all emails regarding this issue.

        Document size: 29.3 KB
        For call complaints, please contact the Managing Director of the company using this form.