Planon REM4SAP : Planon REM4SAP : Implementation : Setting SAP Integration app
Setting SAP Integration app
For general information on the SAP integration App, see Planon Marketplace (see documentation on the Support tab).
Most relevant module settings to be provided on the server module:
Field
Description
Example value
Account
User for authorization
SUPERVISOR
AccountGroup
User group for authorization
SystemAdministrator
Accounting Notification Iflow
Complete URL of the iflow Notification service, required for Financial Collection
../http/logsys/AcctgNotification
Asset Class Codes
To filter Fixed Assets
00001000,00001100
Business Partner Roles
To filter Business Partners
FLVN00,FLCU00,FLVN01,FLCU01
Client Id
ID of SAP
xxxx
Client Secret
Secret of SAP
xxxx
Company Code Logsys iFlow
Provides the logsys information for Companies
Financial Notification Logical System
Identifier for the Planon system which sends the data to SAP for Cost Allocation
PLANON_123
Create Billing Document Request iFlow
Complete URL of the iflow Notification service, required for External billing requests
Deep Link Navigation iFlow
Enable to navigate multi backend environment
Entity Architecture Object Version
9.0.0
Entity Company Version
4.0.0
Entity Contract Party Version
3.3.0
Entity Contract Version
7.0.0
Entity Cost Center Version
3.7.0
Entity Fixed Asset Version
9.1.0
Entity Organizational Unit Version
3.0.0
Entity Project Controlling Object Version
3.7.0
Entity Rentable Object Version
9.1.0
Entity Usable Object Version
9.0.0
Entity Workforce Person Version
3.8.0
F001: Finance Objects
Consume finance objects
Yes
F002: Business Partners
Consume Business Partners
Yes
F003: Architecture Objects
Provide Architecture Objects
Yes
F004: Rentable Objects
Consume and Provide Rentable (Rent From and Rent To units) Objects
Yes
F005: Lease Contracts
Consume Contracts and Contract lines
Yes
F006: Accounting Notification Collections
Provide Cost Allocations to SAP
Yes
F007: Fixed Assets
Consume Fixed Assets
Yes
F008: Purchase Requisition Collections
Provide Purchase Requisitions to SAP
F009: Billing Document Request Collections
Provide Billing Document Requests to SAP
Yes
F010: Organizational Unit
Consume Organizational Units from SAP SuccessFactors
Yes
F011: Workforce Person
Consume Workforce Persons from SAP SuccessFactors
Yes
odmPath
v1/odm
Purchase Requisition iFlow
Complete URL of the iflow Notification service, required for Purchase Requisition
Reject Billing Document Request iFlow
Complete URL of the iflow Reject service, required for External billing requests
S/4HANA Instance URL
S/4HANA System
Required setting to identify the SAP system where Notifications are consumed
QJ7XXXXX
Service Period Posting Date Reservation
Setting to specify the date which should be mapped to ProposedDateTime and ValueDateTime for Reservations
StartDate
Service Period Posting Date Space Charge back
Setting to specify the date which should be mapped to ProposedDateTime and ValueDateTime for Space Charge back
TransactionDate
Service Root
SAP info
……/http/oxo
Token URL
SAP info
….../oauth/token
Use iFlows For Navigation
When this is true, the multi-backend features are required. When false the S/4HANA url and Notification system are required.
No
The app contains settings based on the SAP environment, which need to be provided by the customer. These settings connect the Planon touch points 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)