Introduction
In a multi-instance environment, two or many environments can share Planon data.
This is only possible if both parties agree to share business object data, thus safe-guarding data integrity and ownership.
This could be two or many Planon environments sharing data, or an external party sharing data with a Planon environment.
In this situation, both parties that share data have a common understanding about the data and its identity.
This situation would be applicable if, for example, one organization serves as a business partner to another organization, to unburden the latter by assuming responsibility for services such as asset or property maintenance, or personnel management.
To support integrations with external applications, Planon offers two TSIs that work together: one that configures how an external system is set up, and one that maintains the links between individual Planon objects and their external counterparts.
External BO links
This TSI works at the individual object level. Each record represents a mapping between a specific Planon BO instance and its corresponding object in an external system.
• The link is defined by the BO definition and syscode of the Planon object.
• The connection to the external object is established through a shared External ID.
• Optional local storage fields allow you to store additional integration-related data for that specific object.
External system configuration
This TSI operates at the system and BO-type level. It defines how an external system is represented and managed within Planon.
• It specifies which external systems exist and how they are configured.
• It determines which BO definitions and fields are controlled by the external system.
• It governs the direction of data exchange, such as whether Planon is leading, following, or synchronizing data.
How the two TSIs work together
Both TSIs refer to the same external systems and are used within the same integration landscape, but they serve different roles:
• External BO links: stores the per-record identity mappings between Planon objects and external objects.
• External system configuration: stores the overall integration setup, including data ownership and synchronization rules that apply to those mappings.