...
Please refer to the “VSS 4.0 Configuration Guide” for more detail on how to configure the plugins.
VMS Vehicle: VMS Action Mapping
Prerequisites
The following is required before setting up the mapping:
VMS action is configured in customizing.
Communication event ID is configured in customizing
Functionalities
This customizing describes the mappings that can be defined between SAP VMS actions and the Communication Events. The objective is to build the relationship between VMS actions and Communication Event ID. For example, when a particular VMS action is executed, it will automatically fire the Communication Event ID, which in turn may result in a notification being triggered or a task being executed (depending on how the process is defined).
Transaction code: /DBE/SPRO or
In Customizing for Logistics Execution, choose Vehicle Sales and Service (VSS) > Framework Components > Communication Framework > Plugins > VMS Vehicle > VMS Action Mapping.
...
Please refer to the “VSS 5.0 Configuration Guide” for more detail on how to configure the plugins.
Task Substitution and Delegation
VSS Communication Framework supports the ability to route task or notification in case of for example, absence or vacation. Standard SAP functionality (transaction RMPS_SET_SUBSTITUTE) can be used to determine a substitute. Substitution can be appointed, and duration of the substitution can be maintained and activated. Communication Framework will validate the substitution determination and duration. If the condition matches, Communication Framework will assign the relevant task to the substitute.
...
Support multi-language notification
SAP Email Template functionality allows selection of language and creation of email template in multiple languages.
...
The following attributes are used to determine the communication language depending on the target recipient:
Business Partner
In case of sending notification to a business partner or customer, Communication Framework validates the customer’s “corresponding language” (defined in transaction BP) with the language defined in the email template and delivers the notification accordingly.
...
SAP User
In case of sending notification to an SAP User ID, Communication Framework validates the SAP User’s “language” (defined in transaction SU01) with the language defined in the email template and delivers the notification accordingly.
...
Employee ID
In case of sending notification to an Employee ID, Communication Framework validates the Employee’s “language” (defined in transaction PA30) with the language defined in the email template and delivers the notification accordingly.
...
| Info |
|---|
Important: Communication Framework notification must have templates defined in target language, otherwise no message will be sent. To minimize this error, you can also define a substitution language in Communication Framework customizing. Substitution language is used as a fallback when there is no notification template available in target communication language. Refer to the configuration guide for more detail. |
Integration with Messaging Applications
Communication Framework supports bi-directional integration with popular messaging applications (internet communicators, like WhatsApp or Line). This integration is realized as one of the communication channels.
Customers are free to integrate with any messaging applications of their choice. To do so, customers must refer to the integration documentation provided by the messaging application of choice and perform the required account creation, technical setups, and customizing steps. Setups and customizing may differ between messaging applications as they may be using different technologies. In any case, Communication Framework offers BAdIs where customer can implement dedicated logic to realize the integration.
Communication Framework offers out-of-box integration with Whatsapps and LINE. Refer to the Communication Framework Cookbook for implementation detail.
Adherence to GDPR requirement
The system allows for customer to define allowed communication methods with regards to clearly defined purposes. The consents are recorded together with the exact description that is presented to the customer.
The consents are stored within the following objects:
Business Partner/Customer
Service Resource Scheduling Order header
Online Appointment Scheduling (OAS) User master data
The consents can be updated by customers directly or on their behalf by authorized employees in the following applications:
Business Partner Maintenance (BP)
VSS Order processing
OAS user maintenance
To-Do basket order maintenance
Mobile Service Advisor
The Communication Framework respects communication preferences by not sending notifications in case consent was not given.