Planon REM4SAP : Planon REM4SAP : Implementation : Settings Planon Real Estate Management for SAP S/4HANA app
Settings Planon Real Estate Management for SAP S/4HANA app
For general information on the Planon Real Estate Management for SAP S/4HANA integration App, please see Planon Marketplace (see documentation on the Support tab).
Most relevant module settings to be provided on the servermodule:
Field
Description
Example value
account
User for authorization
SUPERVISOR
accountGroup
User group for authorization
SystemAdministrator
businessPartnerRoles
To filter Business Partners
FLVN00,FLCU00,FLVN01,FLCU01
assetClassCodes
To filter Fixed Assets
00001000,00001100
ClientId
ID of SAP
xxxx
ClientSecret
Secret of SAP
xxxx
costAllocationAccountingNotificationLogicalSystem
Identifier for the Planon system which sends the data to SAP for Cost Allocation
PLANON_123
entityArchitectureObjectVersion
9.0.0
entityCompanyVersion
4.0.0
entityContractPartyVersion
3.3.0
entityContractVersion
7.0.0
entityCostCenterVersion
3.1.0
entityProjectControllingObjectVersion
3.1.0
entityRentableObjectVersion
9.0.0
entityUsableObjectVersion
9.0.0
f001FinanceObjects
Consume finance objects
Yes
f002BusinessPartners
Consume Business Partners
Yes
f003ArchitectureObjects
Provide Architecture Objects
Yes
f004RentableObjects
Consume and Provide Rentable (Rent From and Rent To units) Objects
Yes
f005LeaseContracts
Consume Contracts and Contract lines
Yes
f006FinancialCollections
Provide Cost Allocations to SAP
Yes
f007FixedAssets
Consume Fixed Assets
Yes
f008PurchaseRequisitionCollections
Provide Purchase Requisitions to SAP
odmPath
v1/odm
serviceRoot
SAP info
……/http/oxo
tokenurl
SAP info
….../oauth/token
servicePeriodPostingDateReservation
Setting to specify the date which should be mapped to ProposedDateTime and ValueDateTime for Reservations
StartDate
servicePeriodPostingDateSpaceCharge back
Setting to specify the date which should be mapped to ProposedDateTime and ValueDateTime for Space Charge back
TransactionDate
useiFlowsForNavigation
When this is true, the multi-backend features are required. When false the S/4HANA url and Notification system are required.
s4hanaInstanceURL
S4HanaSystemFor
Notifications
Required setting to identify the SAP system where Cost Allocations are consumed
QJ7XXXXX
accountingNotificationIflow
Complete URL of the iflow Notification service, required for Financial Collection
../http/logsys/AcctgNotification
purchaseRequisitionIflow
Complete URL of the iflow Notification service, required for Purchase Requisition
deeplinkNavigationIFlow
Enable to navigate multibackend environment
companyCodeLogsysIFlow
Provides the logsys information for Companies
The app contains settings based on the SAP environment, which need to be provided by the customer. These settings connect the Planon touchpoints to the correct SAP environment by populating the clientID, clientsecret, serviceroot, tokenURL in the Servicemodule settings.
General settings
Status
Enable user extensions
Yes
More information on General settings (System settings).
Task
Status
SYSTASKUSEREXTENSION
Active
For the touchpoints that Planon needs in order to consume data from the SAP environment, it is required to set up Task user extensions (System Settings).
Task user extension
Status
com.planon.sap.scheduledtask.­PersonOrAddressUpdateTask
Active
com.planon.sap.scheduledtask.­FinancialObjectsUpdateTask
Active
com.planon.sap.scheduledtask.­SyncVersionIdsTask
Active
com.planon.sap.scheduledtask.­ContractUpdateTask
Active
com.planon.sap.scheduledtask.Lettable­UnitUpdateTask
Active
com.planon.sap.scheduledtask.Financial­ObjectsUpdateTask
Active
com.planon.sap.scheduledtask.Post­FinancialCollectionsTask
Active
com.planon.sap.scheduledtask.PostRequisitionLine
Active
The task triggers the Task user extensions. By system default the schedule minimum is 5 minutes (even if you can set a lower value).
It is recommended to keep a certain sequence in when which task runs, so they don’t overlap or might conflict. For example:
• Generic SYSTASKUSEREXTENSION (start 00.00) – 5 minutes
• FinancialObjectsUpdateTask (start 00.00) – 5 minutes
• PersonOrAddressUpdateTask (start 00.01)- 5 minutes
• LettableUnitUpdateTask (start 00.02) (5 minutes)
• ContractUpdateTask (start 00.04) (5 minutes)