Rent To units
For Rent To units, it is recommended to create a difference between intercompany Rent To units, Internal Rent To units, Vacant Rent To units and External Rent To units.
UdBOs must be configured for this difference to show relevant fields and authorize them. Intercompany Rent To units are completely consumed and will always be a sub of a Rent From unit (regular or intercompany) and a parent for an Intercompany Rent From unit. Rent To units (Internal, Vacant or External) are created in Planon and must be activated with a status change to be sent to SAP. They should be a sub of the Rent From unit (either regular or intercompany).
Field
Mandatory for integration
Description
Purpose
Yes
Reference to a user-defined list that must be connected to SAP code list mapping.
Company
Yes
Could be set-up as derived from the parent Rent From unit
Occupancy code
Will be updated if there are linked Contracts in the Preparation (Option) or Active (Rented) status of a Contract, which is relevant of External and Intercompany Rent To units. Will remain ‘Vacant’ if no Contract is linked or in case the application type (see next) is (V). For Rent To unit Internal the value is updated to ‘Occupied’ when they are activated and linked to space usages.
Application type - rentable unit
Yes
System picklist which is used to determine the difference between Intercompany (R), External (E), Vacant (V) and Internal (I). Could be hidden as part of the UdBO-for Internal and External. For Intercompany, the value is consumed.
System status (only relevant for Internal, Vacant and External Rent To units)
For Intercompany Rent To units, it is recommended to change the initial status to ‘Active’ in Fielddefiner)
System status
Description
Initial
Changes can be done, no exchange to SAP.
Active
Exchange to SAP.
Inactive
Checks whether the End date field has a value as this date ends the validity in SAP. No updates are sent.