The what , why and the how !


Lifecycle of HR business integrations is very similar to any other software development lifecycle - complete with specification, development testing and deployment. Notwithstanding the fact that it is one of the most critical aspects of SuccessFactors® implementations, integration hasn’t seen a great deal of standardization/process either in the whole software lifecycle or in terms of tooling e.g. Integrated Development Environment (IDE) or accelerators that aid in agile development. Net result: a SDLC stuck in the 90s. Prone to errors, rework, high costs and long development lifecycles.

What is integrtr?

Integrtr is a citizen integrator cloud service that manages the life cycle of SuccessFactors® integrations. It aims at becoming the IDE for all SuccessFactors® integrations – to and from.
Business process experts and power users can use integrtr with little or no training and get to the core of their work – the all important field/code mapping between the SF data models and their counterparts in the ERP system. As integrtr is always connected to the data models on the participatory systems, the fields and their codes are always at their disposal. Ease of work and error-reduction starts right at the spec phase.

Why integrtr?

integrtr is an integration lifecycle manager. That means a lot of things

  • it is the first cloud integration tool that offers an out of the box access to the SuccessFactors and ERP systems right at the first phase of integration development - the integration spec phase
  • by the virtue of being connected and being in sync with the participating systems, integrtr makes the all important, also oft frustrating, field and code mapping exercise a breezy affair. No more copy- paste or excel formatting errors, no disconnected out of sync excel sheets and no more sweat about developers perceiving your spec incorrectly! A single source of truth for all people and data connected to the project.
  • integrtr auto generates mappings that are mandatorily required for integration, so that you can, you know, slay the dragons. The plethora of code maps that have to be filled in ERP with 100s of code maps are automatically generated! Your developers can now focus only on the stuff that really need their coding expertise.
  • no integration is without changes. Changes need collaboration. Collaboration doesn't mean sending out newer versions of the spec spreadsheet around in mails! The state of the art collaboration and version management features that integrtr packs offers project, field and value level collaborations - no decisions are lost, no work is redone, no more
  • and the post go live support? A well maintained integrtr project means little or no know-how transfer and hand holding!
  • How integrtr?


    Integrtr needs the data models of the participatory systems to function. The two participatory systems i.e., Employee Central and ERP have to connected to integrtr. Integrtr connects to both these systems in a decoupled mode

    Connect to SuccessFactors®

    To obtain the metdata details about Employee Central Entities and fields, integrtr utilized the OData Metadata.xml file.
    For this download the metadata.xml from your SuccessFactors System

    Connect to ERP

    Since ERP systems are usually well secured behind a fire walls, for the current and near future, integrtr takes a pragmatic approach to connect to ERP – with a decoupled approach.

  • Run our report ZINTGTR_GET_INFTY_META* for the participating infotypes on your ERP system. The result is a .json file. The .json file contains only the metadata information of the Infotype – not the data that the Infotype holds.
  • Upload the unchanged .json file to integrtr
  • Build

    Once the connect step is successful, business experts can immediately get cracking with their field and value mapping. For starters, the mandatory field and value maps for a country are already filled in. Creating new field maps and their value maps is very easy. As integrtr is connected to the participating systems, portlets, fields, infotypes and infotype fields can be found easily via value helps.


    The ERP system can be seeded with integration content at any point. Integration content is basically the field map extensions, code maps, wage type maps etc that have to be maintained in the PAOCFEC_* custom views on the ERP side. Again, integrtr takes the decoupled approach here. Integration content is downloaded as a .csv files and uploaded to the ERP system. Upload to the ERP system can be done with our report ZINTGTR_UPLOAD_INTG_DATA*.
    For field maps that need coding in the ERP system, tasks are created for the developers associated with the project.

    *Consultants at integrtr will help you with this.