hybris Marketing

Marketing Data Management

Technical Information
February 2015

Marketing Data Management

hybris Marketing Data Management within hybris Marketing is the new name for SAP Social Contact
Intelligence.

The menu in the UI has been changed, the

workset items of the former Social Contact
Intelligence can be found under Customer Data
Management.

The configuration is now

located at SAP hybris
Marketing, Data
Management

Customer

Part I: Application Features

Contact Engagement
Contact Fact Sheet
Sentiment Engagement

Objectives

At the end of this presentation, you will be able to:

Explain the data model of the Interaction Contact and the
Interaction
Understand how data is loaded and how additional sources
can be added for Contacts and Interactions
Understand how BAdIs in Social Contact Intelligence can
be used to adapt to your specific customer needs
Explain how additional data sources can be added to the
data harvesting for the sentiment engagement.

*Note: Marketing Data Management within SAP hybris Marketing is the new name for SAP
Social Contact Intelligence
Customer

Marketing Data Management

Data Sources

ADT
(Segmentation)

Mobile

Interaction
Contact

ERP
Contact

CRM
Contact

hybris
Commerce

Contact
Fact Sheet

Social Sources
Connectors to Twitter, Facebook and Google+
RDS package available (see next slide)

Interaction Analysis
External interface to load interactions from 3rd party tools for e.g.,
Clickstream Monitoring, Email Execution, etc.
External data needs to be matched to import structure
RDS package available (see next slide)

Operational business documents

SAP CRM: Activities, Leads, Opportunities
SAP C4C: Leads, Opportunities

Interaction

C4C
Contact

Web
Interaction

Tweets,
Posts

ERP Contacts (replicated via SLT)

CRM Business Partner of role Contact (replicated via SLT)
hybris Commerce Clickstream
C4C Contact

Events

Survey

Email

Phone

etc.

Customer

Marketing Data Management

Interaction Data Model

Interactions (including posts) and

CRM business documents
form the transaction data
for Social Contact Intelligence

Interactions are structured to

answer the questions
Who did (contact attributes)
What (interaction type)
By which means (communication medium)
Why (item of interest)
When (time stamp)

External systems for clickstream monitoring, email

campaign execution etc. store their data as
interactions to allow a holistic view and evaluation

Customer

Marketing Data Management

External Interfaces for Interactions From 3rd Party Tools

Interactions are pushed to Social Contact Intelligence by calling RFCenabled function module CUAN_CE_INTERACTIONS_POST
For details refer to function module documentation

Import data structure CUAN_S_CE_IA_EXT which contains

Interaction information
Contact information
Extension include
Attributes for codes as well as free text
(for example COUNTRY, COUNTRY_FT)

Customer

Marketing Data Management

External Interfaces for Interactions From 3rd Party Tools

Since SP04 interactions can also be posted to CEI using either

web service CUANPostInteractions or
OData service CUAN_IMPORT

Customer

Marketing Data Management

External Interfaces for Interaction Contacts From 3rd Party Systems

Interaction Contacts can be posted to SAP hybris Marketing using:

OData service CUAN_IMPORT
Web service CUANPOSTINTERACTIONCONTACT
RFC enabled function module CUAN_CE_IC_POST_FLAT
CSV Upload accessible from SAP Customer Engagement Intelligence user interface

Additional information available under http://sap.help.com/cei

Customer

Marketing Data Management

Lifecycle of Interaction Contacts
Deletion of interaction contacts
We follow a two step approach, first step is to set the
data to cold and the second step is to delete this data.
We support for both steps a test and productive mode.
Set interaction contacts to cold
Transaction CUAN_CE_IC_SET_COLD

The database attribute CUAND_CE_IC_ROOT_DATAAGING will set to 00010101. Cold data are not
visible in the application.
Delete cold interaction contacts:
Transaction CUAN_CE_IC_DEL_COLD

The data records with cold data will be removed from

the database with all dependent objects.
To reduce manual effort, it is possible to schedule it as
periodic job.
Customer

Marketing Data Management

RDS Package for Rapid Data Load

RDS Package for Rapid Data Load

service.sap.com/rds-dlh
Highlights:

Social media load - The solution

allows you to load data from
social media channels such as
Twitter, Facebook, and Google+
Interactions load - The solution
allows you to load interactions
from different sources, such as
clickstream, e-mail, and other
documents.

Customer

Marketing Data Management

Interaction: Influencing Content
You receive new interactions using function module
CUAN_CE_INTERACTIONS_POST.
You can influence the complete list of interactions that are to be
created by implementing the BAdI Revise and Manage Interactions
While Uploading
You can influence which data is displayed in the timeline on the
Interactions facet by implementing the BAdI Revise Interaction Data
before Display

Customer

Marketing Data Management

Interaction Contact: Influencing Content
Interaction contacts can be created direct via the offered interaction contact
API or indirect from interactions. To ensure that only one interaction contact
per natural person is created, the system tries to determine an already
existing matching interaction contact.
You can influence the search result implementing a corresponding BAdI

Every new interaction can improve data quality of interaction contacts

You can influence how existing data is changed by new interactions via BAdI
including mapping of free texts to code values
You can define which data is taken into account to determine interaction contact
attributes

You can periodically apply changes of business partner or contact person

data to their corresponding interaction contacts via ABAP program
You can extract CRM business partner and ERP contact person data via full
upload after system setup program CUAN_IC_MASTERDATA_EXTR_DELT
You can schedule delta upload for periodic check for changes Program
CUAN_IC_MASTERDATA_EXTR_FULL

Customer

Marketing Data Management

Interaction Contact: Influencing Content
BAdI: Search Interactions Contacts to Match New Interactions
-

Will be executed when newly imported interactions or interaction contacts are

uploaded

Tries to match the newly provided interaction contact information to an existing one

BAdI: Interaction Contact Update

-

Determine the common data for the interaction contact

Influenced the facet data, e.g. marks a facet as invalid or adds an additional facet based
on a field from extension include

Calculates additional attributes for interaction contact root data, like validation status

BAdI: Trigger Read of Historic Interactions

-

Enables or disables the read of historic interaction data, please consider it influences
the performance to store interaction contact data

Customer

Marketing Data Management

Scoring Integration -1For details regarding score definition in the Predictive
Model Management workset and the integration to ADT,
please refer to the respective presentation.
A detailed configuration help is provided via the CEI
Extensibility Guide available on help.sap.com.
In order to integrate scores into Contact / Consumer and
Account Fact Sheets you need to perform three in the
configuration of Predictive Scenarios:
You define application anchors for those fact sheets in which
you want the scores to be displayed
In the step Define Predictive Scenarios you assign scores to
the respective fact sheet in which they shall be displayed.
E.g. a profile score is specific for a contact, hence it is
assigned to the application anchor of the Interaction Contact
fact sheet.

Customer

Marketing Data Management

Scoring Integration -2-

In the step Define Settings for Display of Predictive

Scenarios on User Interface you assign the SAPUI5 Icon
you want to symbolize the score in the UI. In the case of
scores with ranks, you define the color the SAPUI5 Icon
shall take in the UI depending on the score rank and also
which text to display depending on the score rank.

Customer

Marketing Data Management

hybris Web Shop Personalization based on Customer Segments
For details regarding installation, please refer to the respective
installation guides
CEI: help.sap.com
hybris: hybris wiki

Both during design time and run time, hybris calls the CUAN_COMMON
OData service provided by CEI:
During design time, hybris assigns the campaign of the respective customer
segment to the rule definition for the personalization
During run time, hybris uses the customers login credentials to establish the
customer segment and respective campaign that person is assigned to. Then
the web shop is personalized according to whatever was defined for that
customer segment.
For this, hybris needs a technical user in CEI with the necessary read
authorization assigned in order to access the CUAN_COMMON OData
service and underlying objects (Target Group, campaign) in read-only mode.

Customer

Marketing Data Management

hybris Web Shop Clickstream in Customer Journey
For details regarding installation, please refer to the respective installation
guides
CEI: help.sap.com
hybris: hybris wiki

Interactions are pushed to Social Contact Intelligence by calling RFC-enabled

function module CUAN_CE_INTERACTIONS_POST
For this, hybris needs a technical user in CEI with the necessary write authorization
assigned in order to create Interactions in CEI.

Customer

Marketing Data Management

CEI - Adobe Experience Manager (AEM) Integration
For details regarding installation, please refer to the respective installation
guides
CEI: help.sap.com
Adobe: http://docs.adobe.com/content/docs/en/aem/6-0.html

Both during design time and run time, AEM calls the CUAN_COMMON
OData service provided by CEI:
During design time, AEM assigns the CEI campaign to AEM segments for which
then web personalization is created
During run time, AEM uses the visitor login credentials to establish the segment
and respective campaign that person is assigned to. Then the web page is
personalized according to whatever was defined for that segment.
For this, AEM needs a technical user in CEI with the necessary read
authorization assigned in order to access the CUAN_COMMON OData service
and underlying objects (Target Group, campaign) in read-only mode.

Customer

Marketing Data Management

Customizing the Filter Attributes

You can define filter criteria that the end user can select to
appear on user interface (UI) for Contact Engagement
You can define the filter criteria based on the attributes of the
interaction contact.
The following options for a filter are available:
Drop down
Search
Slider
After defining the filter attributes the end user is able to
define his/her personalized view by selecting/deselecting
filter in the focus area of the Contact Engagement UI.

Customer

Marketing Data Management

Segmentation Profile Assignment

You can handover segmentation profiles to

ADT.
This allows you to make the filter criteria
available as a segmentation model in the
workset Audience Discovery and Targeting
If you assign a profile to Contact
Engagement, you must maintain the
mapping between all the filter attributes of
Contact Engagement and the attribute of
the profile.
In addition, you have to define and map
any attributes that are used implicitly e.g.
IA_DATE, CHANNEL, INTEREST_ITEM
etc.

Customer

Marketing Data Management

Sentiment Engagement Data Sources
Data can be harvested from public social media or
internal sources and is loaded into the inbound tables
of the Social Intelligence data model for further
processing by choosing one of the following options:

Implement own data crawling logic, e.g. use

script language to access provider APIs and pass
data via ODBC into HANA inbound tables or
ABAP program to pass data via respective API
classes.

For test purposes this direct twitter connection

can be used

Refer to the installation guide of SAP Customer

Engagement Intelligence for more details.

Customer

Marketing Data Management

Sentiment Engagement BAdI: Definition of Actions for Post Groups

There is a BAdI available for defining actions that are to be carried out for a post group. You can either activate
one of the default BAdI implementations or create your own.
The following implementations are available:

MENTION_GROUP_ACTION_SEND_MAIL
In this implementation all the posts listed in a post group are sent to the user as an email when the user
triggers the action assigned to the group.

CREATE_TARGET_GROUP
Create target group based on interaction contacts created from / matched with social media accounts of social
posts.

CREATE_JAM_GROUP
To share and discuss posts with external partners you can create a SAP Jam group into which posts of a post
group are passed.

To implement your own action in BAdI Builder, use enhancement spot EH_CSAN_MENTION_GROUP_ACTION.
Please check out the IMG documentation for further details such as requirements, parameters, etc.

Customer

Marketing Data Management

Sentiment Engagement Demo Program Harvesting from RSS Feeds

In order to support a quick start for proof of concepts or demos,

we provide a program which retrieves articles from RSS feeds
and stores these as social posts in foundation layer for further
processing as interactions in Social Contact Intelligence.
As it has limited functionality, it is not supposed to be used in
a productive environment. Nevertheless you might want to use
it as a template for implementation in your customer project.

Program: CSAN_DEMO_RSS_HARVEST

Customizing of relevant feeds: single feed via selection screen or list

of feeds according to view CSANV_DEMO_RSS

See inline documentation at program coding for details on features,

limitations, pre-requisites and setup

We recommend to schedule a job to harvest the delta regularly (e.g.

every hour) and thereby have up-to-date data in the application.

Customer

Part II: Configuration of Foundation

Valid for SAP_BS_FND 7.47 SP05
Layer for Social

Prerequisites
Data Privacy Features
Text Analysis
Social Intelligence Data Management
using APIs
Authorization

Objectives

At the end of this module, you will be able to:

Set up the supported data privacy features for the data

harvested from the social media channels

Understand the possibility of defining text analysis and

assess the results

Identify the APIs for managing data in the tables related to

Social Intelligence

Customer

Business Example

John is a technical consultant who needs to set up the

harvesting of Social Data and also the related features. He
has set up the Data Harvesting Connector for Datasift. He
needs to set up the Data Privacy aspects to adhere to Legal
Requirements and also understand the possibilities available
for managing the harvested data.

Customer

Agenda
Prerequisites
In this session, you will learn the prerequisites for the consumption of Social Intelligence features
Data Privacy Features
In this session, you will learn how to configure the Data Privacy features
Text Analysis
In this session, you will learn how to trigger text analysis and assess the results
Social Intelligence Data Management using APIs
In this session, you will learn how to consume the APIs to manage data

Authorization Objects
In this session, you will learn about the authorization objects available for managing data

Customer

Prerequisites
In this session, you will learn the prerequisites for the consumption of Social
Intelligence features

Prerequisites
1. You must have Package BS_SOMI_MAIN in your ABAP system. (SAP_BS_FND 7.47
SP05)
2. You must know the schema name of the underlying HANA database of the ABAP system.
3. If you are using the Datasift, you can find information about the installation of the
Connector in the RKT Material RKT - Social Data Harvesting Connectors for DataSift.
4. The configuration of the Search Query is done as defined in the session Configure Social
Search Query of RKT - Social Data Harvesting Connectors for DataSift.

Customer

Data Privacy Features

In this session, you will learn how to configure the Data Privacy features

Components
The following are the components of the data privacy implementation in
Social Intelligence

Consent Management
Defining consent mechanism
for social media posts based
on retrieval mechanism,
channel, and country
Scheduling background jobs
and work on the harvested
data

ILM Features
Archiving allows for clean-up
of data in the database tables
based on residence time
Handling retention time Legal
Hold (features supported by
ILM) with ILM Objects

Customer

Configuring Consent Management Prerequisites (1/2)

Activation of Business Function
To activate the business function for Consent Management, proceed as follows (you might
need additional authorization for the following steps):
1.

Enter the transaction SPRO.

2.

Navigate to Activate Business Functions.

3.

Navigate to ENTERPRISE_BUSINESS_FUNCTIONS FND_SOMI_CM

4.

Go through the documents and Activate.

After successful activation of business function, the following node is visible in IMG
Cross-Application Components Processes and Tools for Enterprise Applications
Social Intelligence Social Consent Management

Customer

Configuring Consent Management Prerequisites (2/2)

Maintenance of Social Media Group
Social Media Group is a combination of the Channel (such as Facebook, Twitter and so on) with the retrieval mode.
Navigate to the following node in IMG
Cross-Application Components Processes and Tools for Enterprise Applications Social Intelligence Basic
Settings Define Social Media Group
1. Create a new Social Media Group by maintaining the Group and Description
For example,
Social Media Group TDS
Social Media Group Description Group for Datasift harvesting for Twitter data
2. Assign the channel and retrieval mode to the Social Media Group*
Assign a Social Media Channel (such as Twitter) and Data Retrieval Mode (such as Datasift) to the Social Media Group

* - Prerequisite is that the Social Media Channel and Data Retrieval Mode should already be defined in Cross-Application Components Processes and Tools
for Enterprise Applications Social Intelligence Basic Settings
Customer

Configuring Consent Management (1/5)

Consent Management can be configured using the following option:
Cross-Application Components Processes and Tools for Enterprise Applications Social Intelligence
Social Consent Management Configuring Social Consent Management
The configuration is based on the combination of social media group and country.

Settings for Consent Management

No Consent Required,
Store Anonymously
Data is always stored
anonymously

Consent Required
Also called as Explicit
Consent
Consent is requested
from Social User

Social Data Processor

Decision
Also called as Implicit
Consent
Consent information is
provided by an
application user

No Consent Required,
Store Complete User
Information
User information is
always stored

Parameters from Social Data

Social
Media
Country
Channel
Data Retrieval
Mode

Customer

Configuring Consent Management (2/5)

No Consent Required, Store Anonymously
To make the harvested data anonymous, proceed as follows:

Impact on Social Data table

Clear fields CREATEDBYUSER, SOCIALPOSTLINK, and CREATIONUSERNAME
If the BAdI SMI_REPLACE_ANONYMIZED_USRNAME is implemented, then the value returned
by the BAdI is stored in CREATEDBYUSER

Impact on Social User Info table

Delete (if there is no other reference of the user in Social Data table)
If the BAdI SMI_REPLACE_ANONYMIZED_USRNAME is implemented, the following actions are
taken
o Copy the old Social User Info instance and change the SOCIALUSER to the value from Badi
o Flag to indicate that the Social User is an anonymized version (and not a real Social User)
o Delete the old Social User Info instance (if there is no other reference)

Customer

Configuring Consent Management (3/5)

Consent Required

Getting Consent Information

Consent from a social media user is received with the help of a BAdI implementation

The BAdI is SMI_BADI_CNSNTMGNT_EXPLCTCNSNT and the corresponding method is

GET_EXPLICIT_CONSENTS

The method receives the posts that needs explicit consent as importing parameters and returns the consent
information

Action on no consent

A wait time (in days) can be configured that defines the maximum period the social media post can be kept before we
get a consent

If we do not receive a consent and if the wait time is elapsed, the post is deleted

It is possible to specify whether the post alone has to be deleted or the post and analysis data

BAdI call on deletion due to lack of consent

If a post is deleted, a BAdI call is made enabling the clean up of dependent data

The BAdI is SMI_BADI_CNSNT_ACTION_ON_POST and the methods are CLEAN_UP_SOCIALPOSTS and

CLEAN_UP_SOCIALUSERINFO
Customer

Configuring Consent Management (4/5)

Social Data Processor Decision

Getting Consent Information

Consent from a social media user is received with the help of a BAdI implementation

The BAdI is SMI_SCL_CNSNT_MGNT_USR_DCSN and the corresponding method is GET_USER_DECISIONS

This method receives the social media posts that need implicit consent as importing parameters and returns the
consent information

Action on no consent

A wait time (in days) can be configured that defines the maximum period the social media post can be kept before we
get a consent

If we do not get a consent and if the wait time is elapsed, the post can either be deleted (it is possible to specify
whether the post alone has to be deleted or the post and analysis data) or stored anonymously based on the consent
management configuration

BAdI call on deletion due to lack of consent

If a post is deleted, a BAdI call is made enabling the clean up of dependent data

The BAdI is SMI_BADI_CNSNT_ACTION_ON_POST and the methods are CLEAN_UP_SOCIALPOSTS and

CLEAN_UP_SOCIALUSERINFO

Customer

Configuring Consent Management (5/5)

No Consent Required, Store Complete User Information
The user information is always stored and no consent is requested from the social media user

Customer

Executing Consent Management (1/3)

Social media posts for consent processing

Consent Management Report 1
Anonymize data
Consent Management Report 2
Explicit consent

Implicit consent

Posts processed for consent

Customer

Executing Consent Management (2/3)

First, the report mentioned in the following IMG path should be
scheduled
Cross-Application Components Processes and Tools for
Enterprise Applications Social Intelligence Social Consent
Management Managing Consent
The report takes care of anonymizing the data and preparing the data
for the second report.
Posts for consent processing
Consent Management Report 1
Anonymize data
Consent Management Report 2

Please note that this report

should always be run first.

Explicit consent

Implicit consent

Posts processed for consent

Customer

Executing Consent Management (3/3)

Second, the report mentioned in the following IMG path should be
scheduled
Cross-Application Components Processes and Tools for
Enterprise Applications Social Intelligence Social Consent
Management Additional Consent Management for Consent Type
(1,2)
Posts for consent processing

The report takes care of the BAdI calls for getting consent
information and taking the appropriate action.

Consent Management Report 1

Anonymize data
Consent Management Report 2
Explicit consent

Please note that this report should always be run

after the first report.

Implicit consent

Posts processed for consent

Customer

ILM Archiving Objects

Two archiving objects are available for archiving data from the database tables
SMI_SD Archiving object used for archiving SOCIALDATA table and all related tables (SMI_VOICE_CUST and
SMI_IMPLIEDCNSNT)
SMI_SUI Archiving object used for archiving SOCIALUSERINFO table

BADI call on archiving data

If a post is archived, a BAdI call is made enabling the clean up of dependent data

The BAdI is SMI_SOCIAL_ARCH_DES and the methods are ARCHIVING_SOCIALDATA and

ARCHIVING_SOCIALUSERINFO (depending on the archiving object)

Please refer the documentation on ILM Archiving Objects in help.sap.com for more
information on configuring and executing archiving runs.
Customer

ILM Objects
Two ILM objects are available for maintaining data as per the ILM rules:
SMI_SD ILM object corresponding to the archiving object SMI_SD
SMI_SUI ILM object corresponding to the archiving object SMI_SUI

Please refer the documentation on ILM objects in help.sap.com for

more information on configuring retention times and legal hold.
Customer

Destruction Objects
Two destruction objects are available for maintaining data as per the ILM rules
SMI_SOCIALDATA_DESTRUCTION Destruction object for deleting data from database
table SOCIALDATA and SMI_IMPLIEDCNSNT
SMI_USERINFO_DESTRUCTION Destruction Object for deleting data from database table
SOCIALUSERINFO

BADI call on destruction of data

If a post is destroyed, a BAdI call is made enabling the clean up of dependent data

The BAdI is SMI_SOCIAL_ARCH_DES and the methods are DESTRUCT_SOCIALDATA

and DESTRUCT_SOCIALUSERINFO (depending on the destruction object)

Please refer the documentation on Destruction Objects in

help.sap.com for more information.
Customer

Text Analysis
In this session, you will learn how to trigger text analysis and assess the results

Text Analysis
HANA Text Analysis is used to calculate the sentiment information for the social media posts
The result of HANA Text Analysis is stored in the table SMI_VOICE_CUST and can also be linked to the SearchTerm defined
for harvesting
The steps involved in Text Analysis are as follows:

Generate the Text Analysis Index

Defining Entity Types for Sentiment Assignment

Sentiment Assignment

Please refer to the documentation on HANA Text analysis in help.sap.com to

understand the feature and the list of languages supported.
Customer

Generate the Text Analysis Index

Generate the Text Analysis Index using the following option
Cross-Application Components Processes and Tools for Enterprise Applications
Social Intelligence Text Analysis Generating Text Analysis Index
The report can work in two scenarios:
1. Suite on HANA In this case, HANA is the primary database and you can choose the
Database Connection as DEFAULT and leave the Schema Name as blank.
2. HANA as secondary database In this case, choose the corresponding Database
Connection and also select the appropriate Schema Name of the database table
SOCIALDATA.

The index generated is INDEXVOICEOFCUST.

Customer

Defining Entity Types for Sentiment Assignment

HANA Text Analysis identifies a wide range of entity types. The entity types relevant for
sentiment assignment can be defined in the following IMG location
Cross-Application Components Processes and Tools for Enterprise Applications
Social Intelligence Text Analysis Selecting Entity Types to Process for Sentiment
Assignment

You have the option to either include the entity type alone or include all subtypes. The included
entity types will be used during Sentiment assignment.
It is also possible to exclude entity types from Sentiment assignment.

Customer

Sentiment Assignment
Sentiment assignment takes the output of HANA Text Analysis and populates
SMI_VOICE_CUST table. The report can be scheduled at the following location
Cross-Application Components Processes and Tools for Enterprise Applications
Social Intelligence Text Analysis Assigning Sentiment to Entity
The database connection to be used can be specified in the General Settings option.
The report has 2 options:
1. Process Sentiment Assignment This option retrieves the entities and entity types and
all related information from the output of text analysis and populates the table
SMI_VOICE_CUST.
2. Copy Search Terms This option ensures that a link is established between the Search
Terms defined (and used to harvest data) and the sentiment information.

Customer

Social Intelligence Data

Management using APIs
In this session, you will learn how to consume the APIs to manage data

APIs for Maintaining Data

CL_SMI_SOCIALDATA
Used to maintain data in SOCIALDATA table
Singleton class
Also used for mass data maintenance
CL_SMI_SOCIALUSERINFO
Used to maintain data in SOCIALUSERINFO table
Singleton class
Also used for mass data maintenance

Customer

Class CL_SMI_SOCIALDATA (1/2)

Method

Description

GET_INSTANCE

Gets an instance of the class

CREATE_SOCIAL_POS
T_DATA

Creates or modifies a row corresponding to social

media data in the buffer

UPDATE_SOCIAL_POS
T_DATA

Updates a row in buffer corresponding to social media

data

DELETE_SOCIAL_POS
T_DATA

Marks a row in the buffer for deletion

SAVE_SOCIAL_POST_
DATA

Saves the buffered social media data instance to the

database. Commit depends on the parameter

GET_SOCIAL_POST

Retrieves data corresponding to one social data row

GET_SOCIAL_POSTS

Retrieves data corresponding to multiple social data

rows
Customer

Class CL_SMI_SOCIALDATA (2/2)

Method

Description

QUERY_SOCIAL_P
OST_DATA

Queries social media data based on single query

parameters

QUERY_POST_DAT Queries social media data based on multiple

A_BY_RANGE
query parameters
MARK_SOCIAL_PO
ST_OBSOLETE

Marks a single social media data entry as relevant

for deletion

CREATE_MULTIPLE Creates multiple instances of social media data

_SOCIALDATA
UPDATE_MULTIPLE Updates multiple instances of social media data
_SOCIAL_DATA
SAVE

Saves all the data in buffer (Commit depends on

parameter)

CANCEL

Clears the buffer

Customer

Class CL_SMI_SOCIALUSERINFO (1/2)

Method

Description

GET_INSTANCE

Gets an instance of the class

CREATE_USER_INFO

Creates a row corresponding to social media

user information in the buffer

UPDATE_USER_INFO

Updates a row in buffer corresponding to social

user information

DELETE_FROM_BUFF
ER

Marks a row in the buffer for deletion

DELETE_SURROGATE Marks a row in the buffer which is a surrogate

_USER_INFO
user for deletion
GET_USER_INFO

Retrieves data corresponding to one social

media user information row

GET_USER_INFO_TAB Retrieves data corresponding to multiple social

media user information rows
Customer

Class CL_SMI_SOCIALUSERINFO (2/2)

Method

Description

QUERY_USER_INFO

Queries social user information based on single

query parameters

QUERY_USER_INFO
_BY_RANGE

Queries social media user information based on

multiple query parameters

CLEANUP

Refreshes the buffer

CREATE_MULTIPLE_
USERS

Creates multiple instances of the social user

information

UPDATE_MULTIPLE_
USERS

Updates multiple instances of the social user

information

SAVE

Saves all the data in buffer (Commit depends on

parameter)

CANCEL

Clears the buffer

Customer

Authorization Objects
In this session, you will learn about the authorization objects available for
managing data

Authorization Objects
Two authorization objects are delivered

SMI_AUTH controls access to all Social Media data using APIs, Consent Management
Reports etc.

SMI_DSAUTH controls access to the transaction SOMI_DS_CONFIG used for

configuring searchterms in Datasift

Customer

Summary

You should now be able to

Set up the data privacy features

Understand the text analysis capability
Identify the APIs for managing data
Identify the authorization objects required for
various operations

Customer

 2015 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
http://global12.sap.com/corporate-en/legal/copyright/index.epx
for additional
trademark
information and notices.
SAP
company)
and other
in Germany
SAP products
and other
andcountries.
services mentioned
Please seeherein
as well as their respective logos are trademarks or registered
trademarks
of SAP SE
(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark
Some software
information
and products
notices. marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National
productproducts
specifications
mayby
vary.
Some
software
marketed
SAP SE and its distributors contain proprietary software components of other software vendors.
These materials
provided bymay
SAP
SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
National
product are
specifications
vary.
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
These
services
materials
are those
arethat
provided
are setby
forth
SAP
in SE
theor
express
an SAP
warranty
affiliate statements
company foraccompanying
informational purposes
such products
only, and
without
services,
representation
if any. Nothing
or warranty
hereinof
should
any kind,
be construed
and SAP as
SE or its
affiliated
constituting
companies
an additional
shall warranty.
not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or
SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing
In particular,
SE or its affiliated
companies
have no warranty.
obligation to pursue any course of business outlined in this document or any related presentation, or to develop
herein
shouldSAP
be construed
as constituting
an additional
or release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies strategy and possible future
In
developments,
particular, SAP
products,
SE or its
and/or
affiliated
platform
companies
directions
have
and
nofunctionality
obligation toare
pursue
all subject
any course
to change
of business
and may
outlined
be changed
in this by
document
SAP SEor
orany
its affiliated
related presentation,
companies atorany
to develop
time
or
release
for any reason
any functionality
without notice.
mentioned
The information
therein. This
in this
document,
document
or any
is not
related
a commitment,
presentation,
promise,
and SAP
or legal
SEsobligation
or its affiliated
to deliver
companies
any material,
strategy
code,
and or
possible
functionality.
future All forwarddevelopments,
products,
and/ortoplatform
and functionality
all subject
to change
and
changedfrom
by SAP
SE or its affiliated
at any
for
looking statements
are subject
various directions
risks and uncertainties
thatare
could
cause actual
results
to may
differbe
materially
expectations.
Readerscompanies
are cautioned
nottime
to place
any
undue
reason
reliance
without
on these
notice.
forward-looking
The information
statements,
in this document
which speak
is not only
a commitment,
as of their dates,
promise,
andorthey
legalshould
obligation
not be
to relied
deliverupon
any material,
in makingcode,
purchasing
or functionality.
decisions.All forwardlooking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

Customer