Completing the Destinations in SAP BTP
The application and the technical destination, the identity mode they decide, the optional Joule, notifications and Fiori-link settings, and how to check the connection.
Draft brief for authors. Section page. When the subaccount subscribed, MDM created four template destinations; two connect to SAP and must be completed, two are optional. MDM reads destinations from the subscriber's own subaccount only and never overwrites one.
Source in the product repository: customer guide §3 and §7; srv/lib/tenant-destination-status.js.
In this section
- The Application Destination (RIKAISO_MDM_DESTINATION)The destination used for reads and processing; its authentication type decides whose SAP user the changes run under.
- The Technical Destination (RIKAISO_MDM_TECH_DESTINATION)The destination for work without a signed-in user: the custom-field synchronization and background runs of integration-user tables; it must be technical and name the same SAP system.
- Choosing the Identity ModeNamed user (SAP applies each person's authorizations) or integration user (SAP applies the communication user's, MDM's roles are the boundary), and the background opt-in between them.
- Optional: The Joule Button (RIKAISO_MDM_JOULE)Enter the URL of your Joule web client and the MDM launchpad shows a Joule button; leave the template as it is to show none.
- Optional: Notifications (RIKAISO_MDM_NOTIFICATIONS)Connect your SAP Alert Notification service instance so that every finished upload and processing run reaches the channels you configure there.
- Optional: Links into Your SAP Fiori LaunchpadAnswers of the assistants and the lists can link to the same records in your SAP Fiori launchpad; MDM derives the address for a Public Edition system, and you can set it and the intents yourself.
- Checking the ConnectionEvery app shows a warning strip with the first problem it finds for what it shows; assistants read the same checks; a broken destination never blocks the subscription.
Last updated: