Ansicht
Dokumentation

V_SMI_CNSNTCNFG - Configuring Social Consent Management

V_SMI_CNSNTCNFG - Configuring Social Consent Management

TXBHW - Original Tax Base Amount in Local Currency   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

You use this Customizing activity to configure the consent type for a social post. The consent is configured based on the social media group and the country. Different countries have different policies for data privacy. Consent configuration helps to manage the social data for social media group and country according to the data privacy laws.

The social media group is defined in the Social Media Group Definition.

  1. Choose New Entries.
  2. Enter the social media group.
  3. Enter the country.
  4. Select the consent type. The consent type can be any of the following:
  • No Consent Required Store Anonymously -The social post data and sentiment associated with post is retained. The BAdI SMI_FILL_ANONYMIZED_USRNAME, if implemented, is used to:
  • Retrieve pseudo names for social media users.

  • The pseudo name returned by the BAdI is filled in CREATEDBYUSER field.

  • A record is created in the SOCIALUSERINFO table with the SOCIALUSER field equal to pseudo name.

  • In the pseudo user record, the fields that can lead to the actual user, such as SOCIALUSERPROFILELINK, SOCIALUSERACOUNT, SOCIALUSERNAME, SOCIALUSEREMAILADDRESS, SOCIALUSERNAME_UC, SOCIALUSERIMAGELINK are cleared off.

  • The ISPSEUDOUSER checkbox is selected to indicate that the user is not an actual social media user.

Note:
  • If the BAdI is not implemented or the BAdI returns an empty string as the pseudo name, the following user information fields are deleted from the SOCIALDATA table: CREATEDBYUSER, CREATIONUSERNAME, and SOCIALPOSTLINK and the pseudo user record is not created.

If the social media user has other social media posts in which the SOCIALPOSTACTIONSTATUS is not equal to '0', the social media user record is not deleted from the SOCIALUSERINFO table.
  • You can select the flag "No Pseudoanonymization", to disable pseudoanonymization.

  • Consent Required -The social post data, sentiment associated with post, and the social user information is stored if explicit consent is received from social user through the BAdI (SMI_BADI_CNSNTMGNT_EXPLCTCNSNT). If the consent is not received and the wait time has expired, the consent-based action on the post is executed. Three consent-based actions are supported by this consent type: Delete the Social Post, Delete the Social Post and Sentiment Associated with Post, and Save the Social Post Anonymously. No action is taken on the post if the wait time has not expired.
  • Note:You cannot save the social post anonymously for the consent type Consent Required.
  • Social Data Processor Decision -The social post data, the sentiment associated with post, and the social user information are stored if implicit consent is received from the user through the BAdI (SMI_SCL_CNSNT_MGNT_USR_DCSN). If the consent is not received and the wait time has expired, the consent-based action on the post is executed. Three consent-based actions are supported by this consent type: Delete the Social Post, Delete the Social Post and Sentiment Associated with Post, and Save the Social Post Anonymously. No action is taken on the post if the wait time has not expired.
  • No Consent Required Store Complete User Information -The social post data, the sentiment associated with post, and the social user information are stored.
  1. Enter the wait time. This indicates the maximum number of days to wait for consent for the social data.
  2. Select the action to be performed on the social post. This field is enabled only for the consent types Consent Requiredand Social Data Processor Decision.Three consent-based actions are available:
  • Save the Social Post Anonymously - The social post data and sentiment associated with post are retained. The user information fields deleted from the SOCIALDATA table are: CREATEDBYUSER, CREATIONUSERNAME, and SOCIALPOSTLINK. The corresponding user information is not deleted from the SOCIALUSERINFO table.

  • Delete the Social Post - The social post data is deleted from the SOCIALDATA table. The corresponding user information is not deleted from the SOCIALUSERINFO table.

  • Delete the Social Post and Sentiment Associated with Post -The social post data is deleted from the SOCIALDATA table and the corresponding sentiments associated with post are deleted from the SMI_VOICE_CUST table. The corresponding social user information is not deleted from the SOCIALUSERINFO table.

Note: If the consent configuration is not maintained for a social post, it remains in the database and is not processed.






TXBHW - Original Tax Base Amount in Local Currency   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 6646 Date: 20240523 Time: 193847     sap01-206 ( 113 ms )