Planon REM4SAP : Planon REM4SAP : Implementation : Settings TSI External system configuration
Settings TSI External system configuration
This section lists specific settings that are set in the External system configuration TSI. The selection level or step within this TSI is mentioned.
Level: External Systems
Automatically created by installing the app.
Field
Description
Code
SAP (automatically generated)
Inbound account
Typically the admin user such as SUPERVISOR (automatically generated by the user installing the app)
Inbound user account group
Admin user group (automatically generated by the user installing the app)
Partner identifier
Planonsoftware.com (read-only)
App name
Planonrealestatemanagementforsap (read-only)
App module name
Servermodule (read-only)
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 both Offering and Accepting 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 contract
When a contract line is linked to a contract, the contract line date range will not be verified against the date range of the given contract and when the contract date range is adjusted, it will not be verified against the date range of the contract line.
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 the date range of the given rentable unit and when the rentable unit date range is adjusted, it will not be verified against the date range of the contract line.
Level: Externally managed BO configurations
For the Planon Real Estate Management for SAP S/4HANA app several BOs require configuration.
BO definitions are created for three purposes:
1. Consuming BOs (consume data from the external system)
2. Providing BOs (provide data to the external system)
3. Picklist or referred BOs that are required to create a mapping while consuming or providing
For each BO, specific settings can be edited. In a new system, for Consuming BOs, the following should be used:
1. Owner owns all instances?
Yes (this prevents from creating instances in Planon which do not come from the external system)
2. Owned by external system?
Yes
3. Owner allows updates?
No, if no editable fields are required in Planon.
Yes, if some fields are really required to be edited to support additional Planon functionality.
4. Prevent deleting when externally linked?
Yes (this prevents from deleting objects that are probably not deleted in the external system, so could create mismatch)
When working with multiple external systems or in an older Planon environment, the option ‘Owner owns all instances = No’ can be used to continue working in the existing BO (which is not shared with the External system), to support a migration path.
It is possible to add customer-specific picklist or UdBO-configurations. It also depends which type of objects are required for the integration scenario.
The following list can be considered a best-practice:
Purpose
BO
Description
Owner owns all in­stances?
Owned by external system?
Owner allows updates?
Prevent deletion when externally linked?
Consume
Company
Specific SAP table
Yes
Yes
Yes
Yes
Consume
Cost Center
Generic Planon table, but very relevant to be consumed from SAP.
Yes
Yes
Yes
Yes
Consume
Cost Center Period
Specific SAP table to store valid periods and references to company.
Yes
Yes
Yes
Yes
Consume
ProjectControlling­ Object
Specific SAP table, similar to Cost Centers, but usually in context of Projects (formerly known as WBS items)
Yes
Yes
Yes
Yes
Consume
Address
To consume Business Partner
No
Yes
Yes
Yes
Mapping
UsrOrganization
Mapping for Address to consume in specific UdBO
Yes
Yes
Yes
Yes
Consume
Personnel
To consume Business Partner
No
Yes
Yes
Yes
Mapping
UsrPerson
Mapping for Personnel to consume in specific UdBO
Yes
Yes
Yes
Yes
Provide
Property
To provide Properties as Architecture Objects and add potential additional fields
No
No
No
Yes
Mapping
Type of Property
Mapping for Properties to provide specific codes for UdBO’s
No
No
No
No
Provide
Floor
To provide Floors and add specific external code as Architecture Object Type
No
No
No
Yes
Provide
Space
To provide Spaces and add specific external code as Architecture Object Type
No
No
No
Yes
Consume & Provide
Base Rentable Unit
To consume and provide Rent From and Rent To units
No
No
No
Yes
Consume
Lettable Unit
To consume Usable objects (SubSystem BO required)
No
Yes
Yes
Yes
Mapping
UsrRentFromUnit
Mapping for Lettable Unit to consume in specific UdBO
Yes
Yes
Yes
Yes
Consume & Provide
Rentable Unit Accounting Object
To consume or provide links between Cost Center or PCO items and Rentable Units
No
Yes
Yes
Yes
Consume
Rentable Unit LinkedFloor
To consume links between Rent From units and Property, Floor or Spaces
Yes
Yes
Yes
Yes
Mapping
OwnershipType
Mapping to picklist values for field on Rent From unit that is consumed from SAP
No
No
No
No
Mapping
AUTHGROUP SAP
Mapping to picklist values for (free) field on Rent From unit that is consumed from SAP
No
No
No
No
Consume & Provide
Rentable Unit
To consume intercompany rent to units & provide internal/external rent to units to SAP (SubSystem BO required)
No
No
No
Yes
Mapping
UsrRent To Unit External
Mapping for Rentable Unit to provide specific UdBO
No
No
No
Yes
Mapping
UsrRent To Unit Internal
Mapping for Rentable Unit to provide specific UdBO
No
No
No
Yes
Mapping
UsrRentToUnit
Mapping for Rentable Unit to consume in specific UdBO
Yes
Yes
Yes
Yes
Mapping
Rentable Unit Application Type
Mapping to system type-values for field on Rent To units that is consumed or should be provided to SAP
No
No
No
No
Mapping
Purpose
Mapping to BO for field on Rent From or To units that is consumed or should be provided to SAP
No
No
No
No
Mapping
Usage
Mapping to BO for field on Rentable Unit Usage that should be provided to SAP (linked to same codes as Space Categories)
No
No
No
No
Mapping
Unit Of Measure
Mapping to BO for field on Usage that should be provided to SAP
No
No
No
No
Mapping
Unit Of Time
Mapping to BO for field on Usage that should be provided to SAP
No
No
No
No
Mapping
Space Category
Mapping to BO for field on SpaceUsage that should be provided to SAP as part of Rent to Units (linked to same codes as Usages)
No
No
No
No
Consume
Base Contract
To consume Contracts from SAP and add required field mapping or filters to Contract Types
No
Yes
Yes
Yes
Consume
Lease Contract
To consume Contracts (SubSystem BO required)
Yes
Yes
Yes
Yes
Mapping
UsrLease Contract
Mapping for Contracts to consume in specific UdBO
Yes
Yes
Yes
Yes
Mapping
Contract_Form
Mapping to BO for field on Contract that is consumed from SAP
No
No
No
No
Consume
Base Contract Line
To consume Contract Conditions & Object Assignments from SAP as Contract Lines
No
Yes
Yes
Yes
Consume
Lease Contract Line
To consume Contractlines (SubSystem BO required)
Mapping
UsrContractLines
Mapping for ContractLines to consume in specific UdBO with a default value to create an Object Assignment
Yes
Yes
Yes
Yes
If user-defined BOs are available, they must be mapped on User-defined BO level. It’s important to also register the base SystemBO.
If there are base SystemBOs with subSystemBOs (such as BaseContracts and BaseContractlines), they are also required to be added. Settings will apply from the UDBO level up to BaseBO:
• UdBO specific configuration, which will be applied (mandatory for UdBOs)
• SubSystemBO can have specific configuration that would work for all sub-UdBOs. On this level, also the Delta-link is requested from SAP
• BaseSystemBO can have generic configuration that would apply for all subSystemBOs and UdBOs.
For the External system configuration to be managed via the app, the following BO definitions are also added by default (these can’t be edited):
Purpose
BO
Description
Owner owns all instances ?
Owned by external system?
Owner allows updates?
Prevent deletion when externally linked?
App
Externally Managed BO Definition
No
Yes
Yes
No
App
Externally Managed BO Field Definition
No
Yes
Yes
No
App
Externally Managed Functionality
No
Yes
Yes
No
The Planon Real Estate Management for SAP S/4HANA app will already create initially BO definitions, which can then be configured and updated.
When a BO definition is created, it will create a delta link which is a unique key with the SAP external system. When that system is changed for some reason, the delta-links must be updated.
One way to do that is to re-create the BO definition. This means, to remove it and re-create the complete definition. It will try to retrieve for the items that are consuming, a mass or initial sync.
Level: Externally managed BO field definitions
Partly mandatory and optional configuration for fields on a BO that must be used for mappings or must be able to be editable on a BO that is consumed from SAP.
The mandatory fields for now are:
Field
BO
Description
Field updates allowed by owner
Payment contract?
BaseContract
To be able to create a mapping to Yes/No
Yes
ContractType
BaseContract
To be able to hardcode the systemtype of Contracts
No
External code
Externally managed BO definitions
Yes
OwnerOwnsAll­Instances
Externally managed BO definitions
Yes
Prefix
Externally managed BO field definitions
Yes
Level: External BO code mapping
For a BO definition that was set up for Mapping purposes, here the values within the Planon database can be linked to External Codes coming from SAP. Where some values need to be manually aligned (like Country-codes), in this list, the codes can actually be different within the two systems.
As the mapping can be used for both consuming as providing values to SAP, it’s not possible to add two different External Codes to the same Business Objects system code or use two different Business Object system codes for the same External Code in the same External Business object definition.
When the codes are perfectly matched, it means there was no existing coding in Planon available, so we recommend to align them 1:1. This could be different in a customer implementation as both sides are configurable. Some examples that could or should be used.
External business object definition
Business Object system code
SAP code-mapping list
ExternalCode
Purpose
SU06
RealEstateRental­ObjectUsageType
SU06
Contract category
YS10
RealEstate­ContractType
YS10
Space categories
070
RealEstate­MeasurementType
SE01
Rentable units - application types (system managed picklist)
G
RealEstate­RentableObjectType
G
Types of properties
003
RealEstate­ArchitectureObjectType
S2LA
Ownership types (system picklist)
02 (Owned)
RealEstate­UsableObject­OwnershipType
S002
AUTHGROUPSAP (user-defined picklist)
B
RealEstate­AuthorizationGroup
GROUP_B
Units of measurement
m2
Unit of Measures
M2
Level: External field mapping – Non-code lists
For the external field mapping – non-code lists, the following mapping types are available:
1. External code – BO definition (refers to a BO, so typically used to create a certain UdBO)
2. External code – Boolean (refers to an External Business object field definition that is (based on the value of the External code) either Yes or No)
3. External code – No mapping (External Business object field definition that can be completely consumed or provided to the external system)
4. External code – Code mapping (External Business object field definition that can only be consumed if there is a mapping available in the External BO Code mapping)
The following table can be used as an example for each type:
Mapping type
External object type
External field name
External Code
External business object – field definition
Yes/No value
Planon external business object definition
1
Business­Partner
businessPartner­Type
person
UsrPerson
2
RealEstate­Contract.­contractType
code
YI10
Payment contract?
Yes
Contracts
3
RealEstate­Contract.­authorizationGroup
code
Authorization group
Contracts
4
RealEstate­Contract.­contractType
code
Contract category
Contracts
1 (special case)
RealEstate­Contract.­conditions.conditionType
code
Object­Assignment (hardcoded value)
UsrLease ContractLine