Third Party Integration
We have vast experience integrating Enterprise Resource Planning (ERP) systems with multi-national organisations including companies with more than 40,000 employees.
The most common requirement is for pushing HR data into myosh on a daily basis. This typically requires both parties to agree on the most appropriate file format and where to post to. Since there is no requirement to write back into your system, there are no real security risks to provide for.
myosh asks that other systems produce a file in an agreed format (this can be csv, xml, etc.) and myosh takes that information and populates the myosh system with the information.
Examples of these types of data include: Employee/Contractor details, Work Hours, Workers Compensation Claim data, Organisational Structure etc. As long as a system can export data in some industry standard format, myosh can integrate with it.
myosh has looked at the capabilities of most of the top 21 ERP systems and has concluded that there are no issues in integration with most versions of SAP, Peoplesoft, Pronto, Oracle, IBM Domino, Microsoft Dynamics, Sage, Infor, Epicor, Exact Globe, intacct, netsuite, Aptean, Friedman, Epicor, Plex, Global Shop, IFS, UNIT4, CDC Software, Acumatica, CHRIS, IQMS and Apptricity.
Examples of Methods currently in production:
Normally integration is achieved in a secure and non-invasive way, by having an encrypted file from the ERP system transferred to the myosh server, on a periodic basis, via File Transfer Protocol (FTP). Once this file is transferred, the myosh server processes the file. Contact or personnel information updates, in the transferred file, are updated within myosh. Deletions or omissions are archived and new records are created. myosh is flexible with the type of file format generated.
Information is pushed to myosh via web services. If required, we can also develop a web service consumer that can pull the information from the client database if the client has an API available to do so. All web service requests (REST API) are done via HTTPS, so all communications are encrypted. Some of our clients also use asymmetric cryptography to further secure the data being transmitted via web services.
Single Sign on (SSO) functionality via Active Directory (AD) requires ADFS or TFIM. Both IdP-initiated and SP-initiated modes are supported.