Planon REM4SAP : Planon REM4SAP : Implementation : Settings TSI External BO Links
Settings TSI External BO Links
This section lists specific settings that are set in the External BO Links TSI. The selection level or step within this TSI is mentioned.
Level: External Systems
Field
Description
Code
SAP
Endpoint URL
Required, but default: https://www.sap.com/
Level: External BO Links
Automatically created after Insert by either Planon or SAP. Within this selection step jumps to the Event Connector TSI are preconfigured:
• Processed Inbound Messages
• Sent Raw Outbound Messages
• Transformed Outbound Messages
• Transformed Raw Inbound Messages
Level: Externally managed functionality
Add logic to the standard Planon business logic with the following functions. These functions can be activated by selecting Yes in the field Applicable?
Field
Description
Conditional contract parties
Inactivates mandatory relation of Contract Parties when changing Contract to System status ‘Active’
Skip contract Calculations
Prevent creation of Financial Commitments for Contract Lines.
Prevent overlap of RU usage and space usage in property
Prevents having one RU with both RU Usages and Space Usages linked to the same RU in the same Property in the same period. This is not allowed for Rentable Objects in SAP.
Prevent overlap of space usages with same space category
Prevents having multiple Space Usages linked to the same Space Category in the same Space and linked to the same Rentable Unit in the same period. This is not allowed for Rentable Objects in SAP.
Block deletion of last rentable unit usage
When deleting RU Usages, it will not be possible to delete the last one, since at least one usage is required.
Block deletion of last space usage
When deleting Space Usages, it will not be possible to delete the last one, since at least one usage is required within a rentable unit.
Ignore contract line date range with rentable unit
When a contract line is linked to a rentable unit, the contract line date range will not be verified against given rentable unit.
Level: Externally managed BO configurations
For the Planon Real Estate Management for SAP S/4HANA app several BOs require configuration. These BOs are:
• Cost Centers
• Cost Center Period
• Floors
• Spaces
• Type of Property
• Properties
• Purpose
• Usage
• Units of Measurement
• Space Categories
• Rentable Units- Application types
• Rent to/Rent from units
• Contracts
• Contract Lines
• Contracting parties
Field
Description
External code
Required for floors and spaces. Floors: mapped to SAP code list for floor Space: mapped to SAP code list for space
Owner owns all instances
Yes, for Cost Centers, Contracts, Contract Lines and Contracting parties as this will make sure they are marked with owner ‘SAP’.
No, for all BOs that Planon provides.
Owner Allows Updates
Yes, for Cost Centers, as this will give options for individual fields of BO which are managed by SAP, to be updated in Planon.
No for BOs where individual fields should not be updated.
Prevent Delete If Externally Linked
Yes, for all BOs that would be shared with SAP (either consumed or provided) and should not be deleted.
No, for BOs that are just part of the mapping, but must be able to be deleted.
Level: Externally managed BO field configurations
Default values for fields that are not available in the integration can be set on this level. This means that Planon will take these default values when specific codes are received from SAP.
Level: External field mapping – Non-code lists
...
Level: Event logs
...
Level: External system – sub event log
...