SAP provides master data finance objects such as companies, cost centers and project controlling objects (PCO) that then can be consumed and linked to relevant objects, such as Rent from and Rent to units.

Planon provides new Properties, by default Sites, Buildings, and Land, which could be more detailed with Floors and Spaces. By a status change on Property-level, these are consumed by SAP as Architecture objects to become part of a Usable object. A Usable object is needed in SAP to create accounting relations, and if the Usable object is marked for Lease-In, it is used to create a Lease-In Contract. The Usable object could be the parent structure of various companies, that lease out and in to each other in an intercompany-relation, which is managed in SAP.

After the creation of Usable objects and potentially the Intercompany objects, Planon consumes this as Rent from and Rent to units, in the hierarchy that could reach five different companies deep. When Contracts are created, they are also consumed and linked to the relevant Rent from or Rent to units.

Planon could then continue to create Rent to units for external or internal use as a sub of one of the Rent from units (depending to which Company it belongs). The Rent to unit External or Internal should be linked to either Space usages or Rentable unit usages.

When activated by a status change, SAP consumes them as Rentable Objects and potentially links them to Lease-Out contracts. As Lease-Out contracts are also consumed in Planon, a specific Contract line is created to link the Rent to Unit and Property, which will update the Occupancy of the Rent to unit.

Business Partners can also be consumed, which will be part of a Contract as well. They are consumed as Addresses or as Persons and when they take part in a Contract, linked to a contract party.

To easily see related or additional information in either Planon or SAP, jumps or deep links have been enabled to jump from an object to a related object in the other system.