Maximize the value of your SAP ERP information by delivering integrated, social business context to your Digital Experience
platform users. Attend this session to understand the business value you can achieve as ERP managed processes are an
integral part of your digital experience solution. Learn how to technically interweave your SAP processes as an integral part of the community and surface the results in business context; bringing the information when and where your users need it. We'll outline technical best practices approaches used in customer deployments where WebSphere Portal and Connections become the dashboard where information managed by SAP is integrated and delivered in business context to Digital Experience users. Consider how you can achieve greater, more productive results for users through integrated SAP ERP, Digital Experience and Connections services.
Designing IA for AI - Information Architecture Conference 2024
SOCIALIZE YOUR SAP ERP THROUGH INTEGRATE D DIGITAL EXPERIENCE PLATFORMS
1. IBM Digital Experience 2015
13-16 October, 2015
Dublin, Ireland
Tech-‐P22
Socialize
your
SAP
ERP
through
Integrated
Digital
Experience
pla=orms
Andrea
Fontana,
CTO
–
ICS
&
WebSphere
Architect
,
SOWRE
SA
#IBMDX2015
4. SocializaAon
is
according
to
a
Dic=onary:
a
con?nuing
process
whereby
an
individual
acquires
a
personal
iden?ty
and
learns
the
norms,
values,
behaviour,
and
social
skills
appropriate
to
his
or
her
social
posi?on.
according
to
Philosophy:
the
process
by
which
human
infants
begin
to
acquire
the
skills
necessary
to
perform
as
a
func?oning
member
of
their
society;
it
is
the
most
influen?al
learning
process
one
can
experience
What’s
SocializaAon?
5. Enterprise
Resource
Planning
is
according
to
a
Dic=onary:
accoun?ng-‐oriented
informa?on
systems
for
iden?fying
and
planning
the
enterprise
wide
resources
needed
to
collect,
make,
distribute,
and
manage
accoun?ng
for
customer
orders.
ERP
systems
were
originally
extensions
of
MRP
II
systems
according
to
Wikipedia:
is
business
management
so`ware,
typically
a
suite
of
integrated
applica?ons,
that
a
company
can
use
to
collect,
store,
manage
and
interpret
data
from
many
business
ac?vi?es,
including:
•
Product
planning,
cost
•
Manufacturing
or
service
delivery
•
Marke?ng
and
sales
•
Inventory
management
•
Shipping
and
payment
What’s
Enterprise
resource
planning
(ERP)
?
6. What’s
Company
management
Company
management
involves
iden?fying
the
mission,
objec?ves,
procedures,
rules
and
management
of
the
human
capital
of
an
enterprise
to
contribute
to
the
success
of
the
enterprise.
Management
does
not
need
to
be
seen
only
from
an
enterprise
point
of
view,
because
management
is
an
essen?al
func?on
to
improve
one's
life
and
rela?onships.
This implies effective communication.
7. Typical
use
of
ERP
System
in
decision
process
is
based
on
the
fact
that
humans
must
search
each
informa?on
they
need
for
that
process.
Humans
must
run
inquiries
in
the
ERP
System
to
collect
each
informa?on.
Usually
an
employee
each
morning
must
connect
to
the
ERP,
and
execute
some
ac?vi?es
to
extract
reports
and
prints,
and
use
them
in
his
decision
processes
Typical
decision
process.
In other words, the standard use of ERP
is in PULL mode, the ERP contains the
information.
But you must pull data from it.
8. Typical
decision
process.
• each
actor
must
search
and
extract
informa?on
• many
informa?on
will
be
show
in
a
report
or
a
document
• only
human
can
extract
data
and
analyse
it
to
make
a
decision
The
most
important
"actor"
is
a
Document.
9. What’s
the
link
?
Between
Enterprise
Resource
Planing
and
Company
Management,
each
component
involved
in
running
your
business,
produces
finally
documents;
but
this
need
also
to
pass
through
human
ac?vi?es,
to
achieve
the
goals.
Human is also a main focus in your Business Activities
Why
don’t
try
to
shi`
the
focus
from
Documents
to
Persons ?
10. Next
Step
Imagine
this
scenario:
I
am
a
Member
of
a
set
of
Communities
These
Communi?es
work
to
define
a
new
strategy
to
sell
a
new
product.
In
this
Communi?es
we
have
some
Actors
like:
Project
Manager
Product
Manager
Marke?ng
Expert
Designer
Each
actor
working
together
to
join
in
goal,
and
some?me
they
needs
some
data
find
in
Company
ERP
or
CRM
11. We
have
a
new
Actor
!
The
new
concept
is:
Permit
a
Socializa?on
process
of
your
ERP
The
leading
idea
is:
SAP
can
send
some
informa?on
to
the
communi?es,
to
help
members
to
complete
decisional
process.
So you have a new
colleague: Mr SAP.
12. The
new
Scenario
is
ready
Human are the main focus in a new decisional process where my ERP
collaborates with them in Decisional Communities.
We have completed in this way our transformation to :
Social Enterprise
Collaboration
13. Behind
the
scenes,
First
Step
(to
CNX)
Some
SAP
func?on
have
a
special
workflow
step
to
publish
some
alert
in
the
Connec?ons
Ac?vity
Stream
or
Blog
post
using
a
specific
SAP-‐Bapi:
basic
idea
is:
SAP-‐BAPI,
when
a
specific
situa?on
happens,
create
a
json/xml
data
and
POST
it
on
Connec?ons,
like
an
alert
to
user
14. Behind
the
scenes,
Next
Step
(to
CNX)
One
module
creates
an
Interface
gateway
with
SAP
Bapi
(cnx
Bapi)
and
uses
Cnx
API
to
publish
informa?on
to
Connec?ons.
This
Module
receives
a
request
from
SAP
and
via
Cnx
API
publishes
on
Ac?vity
Stream
or
Blog
Post
that
informa?on;
it
can
also
receive
requests
from
Connec?ons
and
invoke
SAP
Bapi.
15. SemanAc
Role
Used
in
AcAvity
Stream
ConnecAons
API
“Duke
Ellington
posted
a
new
song
to
iTune”
actor:
En?ty
performing
the
ac?vity
(for
instance,
“Duke”)
verb:
Ac?on
of
the
ac?vity
(for
instance,
“post”-‐ing)
object:
The
primarity
object
of
the
ac?on
(for
instance,
“song”)
target:
Target
of
the
ac?on
(for
instance,
“iTune”)
Ac?vi?es/events
can
be
represented
in
2
formats:
─
JSON
document
─
ATOM
document
JSON
is
the
primary
format
supported
by
Connec?ons.
Atom
is
only
supported
on
retrieval
–
not
to
post
events
21. SemanAc
details
Filed
Type:
Ac?vity
Object
Describes
the
primary
object
of
the
ac?vity,
for
instance,
in
the
ac?vity:
“Duke
Ellington
posted
a
new
song
to
iTune”,
the
object
ac?vity
is
“Song”.
An
Ac?vity
SHOULD
contains
am
object
property
whose
value
is
a
single
Object
25. Use
of
Template
keywords
IBM
Connec?ons
allows
two
kinds
of
Template
in
the
?tle
of
a
connec?ons.
Object substitutions
-‐
where
an
appropriate
representa?on
of
a
known
object
within
the
event
is
subs?tuted
into
the
?tle.
Title template substitutions
-‐
these
use
the
above
object
subs?tu?ons,
providing
a
full
?tle
that
is
appropriately
resourced.
Object Substitution.
Number
of
subs?tu?on
values
are
supported
within
a
submiked
event.?tle:
${Actor}
-‐
this
is
converted
into
appropriately
marked
up
HTML
which
displays
the
Actors
name
and
links
to
a
Business
Card
corresponding
to
the
Actor
${Object}
-‐
if
this
is
a
person
we
display
as
with
the
Actor
above,
otherwise
the
displayName
with
a
link
to
the
url
${Target}
-‐
if
this
is
a
person
we
display
as
with
the
Actor
above,
otherwise
the
displayName
with
a
link
to
the
url
28. Where
can
I
send
my
Json?
Now
we
have
a
Json
ready
to
publish
on
our
Connec?ons
but
how
can
we
do
it?
ctxRoot/opensocial/basic/rest/ac?vitystreams/@me/@all/@all
ctxRoot
is
the
context
root
of
the
Connec?ons
FQDN
AuthenAcaAon
scheme
Specify
the
auth.
Scheme
intendend
to
be
used:
“basic”:
basic
authen?ca?on
“form”:
form
based
authen?ca?on
“oauth”
User
id
The
stream
returns
all
events
that
are
related
to
the
given
user.
@me
is
an
alias
represen?ng
the
currently
authen?cated
user.
CommunityUUID
represen?ng
specific
Community
Group
Id
Events
for
the
group
related
to
the
user
id.
@all
(wild
card)
in
most
cases.
@friends
–
events
from
user
network
@following
–
events
from
people
followed
@self
–
own
events
App
id
Events
for
a
given
applica?ons.
@all
corresponds
to
top
level
view
ApplicaAon
name:
“ac?vi?es”,
“blogs”,
…
29. IntegraAon
with
Digital
Experience
(Portal
XDX)
This
is
an
overview
of
how
XDX
can
effec?vely
integrate
SAP
applica?ons.
Such
as:
• Customer
rela?onship
management
(CRM)
• Supplier
rela?onship
management
(SRM)
• Supply
chain
management
(SCM)
• Product
Lifecycle
Management
(PLM)
• Enterprise
resource
planning
(ERP)
It
also
integrates
with
non-‐
SAP
enterprise
and
cloud
applica?ons.
30. WebSphere
Portal
(XDX)
helps
organiza?ons
create
highly
engaging,
personalized,
and
differen?ated
digital
experiences
that
meet
the
evolving
needs
of
customers
and
employees.
It
can
help
organiza?ons
deliver
excep?onal
digital
experiences:
• ︎
Interact
with
the
appropriate
back-‐end
applica?ons,
such
as
SAP
applica?ons,
to
extend
core
business
processes
to
all
users
and
customers.
• ︎
Provide
relevant,
highly
personalized
experience
according
to
the
user’s
preferences,
behaviors,
loca?on,
and
device.
• ︎
Deliver
consistent
experiences
across
mul?ple
online
channels.
• ︎
Engage
through
online
communi?es,
social
interac?on,
and
collabora?on.
• ︎
Empower
business
owners
to
manage
the
crea?on
and
delivery
of
rich
content.
• ︎
Deliver
engaging
experiences
without
sacrificing
flexibility,
scalability,
or
security.
IntegraAon
with
Digital
Experience
(Portal
XDX)
31. We
have
some
way
to
complete
this
path:
• IBM
WebSphere
Portal
Integrator
for
SAP
• IBM
Digital
Data
Connector
• IBM
Script
Portlet
• IBM
Web
Experience
Factory
IntegraAon
with
Digital
Experience
(Portal
XDX)
32. The
IBM
WebSphere
Portal
Integrator
for
SAP
is
a
feature
of
WebSphere
Portal.
It
is
not
a
new,
but
it’s
available,
star?ng
from
version
7.0.0.1
(CF6)
onwards,
that
provides
interoperability
with
the
SAP
NetWeaver
Portal
component.
It
is
based
on
new
public
SAP
applica?on
programming
interfaces
(APIs)
and
new
features
introduced
in
SAP
NetWeaver
Portal
7.3,
and
is
jointly
supported
by
IBM
and
SAP.
This
feature
no
charge
to
all
WebSphere
Portal
customers,
and
is
available
in
the
IBM
Business
Solu?ons
Catalog.
SAP
NetWeaver
Portal
7.3
(Enterprise
Portal
Core
minimum)
customers
and
WebSphere
Portal
(version
7.0.0.1
CF6
and
later)
customers
can
implement
this
solu?on
today
without
having
to
purchase
any
addiAonal
so]ware.
IntegraAng
with
IBM
WebSphere
Portal
Integrator
for
SAP
33. IntegraAng
with
IBM
WebSphere
Portal
Integrator
for
SAP
The
portal
interoperability
solu?on
addresses
several
main
technical
requirements
for
seamless
portal
interoperability:
• ︎
SSO
• ︎
Naviga?on
federa?on
• ︎
Session
management
SSO
between
WebSphere
Portal
and
the
SAP
NetWeaver
Portal
component
are
handled
by
WebSphere
Portal
Integrator
for
SAP
through
either
basic
authen?ca?on
(using
the
creden?al
vault)
or
with
SAML
2.0.
The
user
logs
in
to
WebSphere
Portal
and
appears
to
be
working
in
a
single
integrated
applica?on.
In
reality,
the
user
is
actually
logged
in
to
two
different
systems
34. IntegraAng
with
IBM
Digital
Data
Connector
(DDC)
for
DX
You
can
use
the
IBM®
Digital
Data
Connector
(DDC)
for
WebSphere®
Portal
framework
to
integrate
data
from
external
data
sources
on
your
portal
pages
by
using
IBM
Web
Content
Manager
presenta?on
components.
External
data
means
that
the
data
does
not
need
to
be
stored
directly
in
IBM
Web
Content
Manager
or
must
use
live
data.
With
Digital
Data
Connector,
your
website
designers
can
use
Web
Content
Manager
presenta?on
components
to
generate
the
web
page
markup
for
your
external
data.
They
can
use
all
the
Web
Content
Manager
data
management
facili?es
for
managing
your
external
data
visualiza?ons
35. The
Digital
Data
Connector
is
a
secret
weapon
from
IBM!
It
gives
you
the
possibility
to
use
WCM
and
WCM
design
components
to
render
any
external
data,
with
likle-‐
to-‐no
java
coding
or
deployment.
A
DDC
profile
is
used
to
define
the
transforma?on
from
your
specific
XML
into
a
generic
list
data
structure
and
enumerate
the
data
akributes
available
in
your
list
items.
How
cool
is
that!
IntegraAng
with
IBM
Digital
Data
Connector
(DDC)
for
DX
36. One
module
creates
an
Interface
gateway
with
SAP
Bapi
(xdx
Bapi)
and
can
answer
via
WebServices
with
a
json/xml
data,
This
data
can
be
rendering
via
WCM
presenta?on
template
in
our
Portal
Experience.
It
can
also
receive
requests
from
Portal
and
invoke
SAP
Bapi,
to
perform
an
Ac?on,
as
confirm
an
Order
or
similar.
IntegraAng
with
IBM
Digital
Data
Connector
(DDC)
for
DX
37. The
major
benefits
of
this
approach
include
the
following:
• Your
Web
Content
Manager
designers
can
fully
control
the
visual
appearance
of
the
integrated
data.
• They
can
visualize
the
external
data
in
the
same
way
in
which
they
visualize
data
that
is
stored
in
Web
Content
Manager.
• As
a
result,
they
can
visualize
the
external
data
in
a
way
that
is
consistent
with
the
corporate
design
of
your
overall
website
by
reusing
exis?ng
Web
Content
Manager
components.
• To
quickly
adjust
exis?ng
visualiza?ons
of
your
data
or
create
new
visualiza?ons
for
new
kinds
of
external
data,
you
no
longer
need
the
help
of
so`ware
developers
or
the
IT
department.
Your
website
designers
can
start
working
on
the
presenta?on
templates
directly
from
your
portal
pages
that
show
the
data.
They
use
the
inline
edi?ng
capabili?es
of
Web
Content
Manager.
• Your
website
designers
make
updates
to
the
Web
Content
Manager
design
components
in
project
scope.
This
way,
they
can
keep
updates
in
dra`
stage
un?l
all
updates
to
the
project
are
completed,
approved,
and
finally
published.
IntegraAng
with
IBM
Digital
Data
Connector
(DDC)
for
DX
38. Use
Digital
Data
Connector
in
the
following
ways:
• You
can
code
a
Java
plug-‐in,
a
so-‐called
DDC
plug-‐in,
that
hooks
into
the
DDC.
The
plug-‐in
loads
the
external
data
and
transforms
it
into
a
generic
DDC
data
structure,
so-‐called
bean
lists.
You
can
then
have
the
bean
lists
rendered
on
your
portal
pages
by
using
standard
Web
Content
Manager
rendering
methods.
• You
can
use
the
generic
XML
DDC
plug-‐in
that
is
built
into
Digital
Data
Connector.
You
can
use
this
plug-‐in
to
integrate
remote
XML
data
without
wri?ng
or
deploying
extra
Java
code.
• You
can
also
use
a
combina?on
of
the
two
approaches.
IntegraAng
with
IBM
Digital
Data
Connector
(DDC)
for
DX
39. Use
Digital
Data
Connector
can
be
integrate
remote
data
in
two
format:
• .
•
DDC
plug-‐in
that
is
ready
to
use
for
integra?ng
external
JSON
data
of
your
choice.
You
can
use
this
plug-‐in
to
render
external
JSON
data
on
your
portal
pages
without
having
to
write
custom
Java
code.
DDC
plug-‐in
that
is
ready
to
use
for
integra?ng
external
XML
data
of
your
choice.
You
can
use
this
plug-‐in
to
render
external
XML
data
on
your
portal
pages
without
having
to
write
custom
Java
code.
CF06(required)
IntegraAng
with
IBM
Digital
Data
Connector
(DDC)
for
DX
40. IntegraAng
wit
IBM
Script
Portlet
(SP)
for
DX
The
IBM
Script
Portlet
enables
a
script
developer
to
create
portlets
for
IBM®
WebSphere®
Portal
with
HTML,
JavaScript,
and
CSS.
The
Script
Portlet
is
designed
for
front-‐end
developers
to
make
por?ng
applica?ons
to
WebSphere
Portal
easy.
You
can
import
an
applica?on
that
you
developed
already.
The
components
are
saved
in
Web
Content
Manager.
You
can
also
edit
the
HTML,
JavaScript,
and
CSS
in
the
Script
Portlet.
The
Script
Portlet
makes
it
easy
to
develop
portlets
with
HTML,
JavaScript,
and
CSS,
without
Java
or
the
JSR
286
portlet
specifica?on.
41. The
following
key
WebSphere
Portal
and
IBM
Web
Content
Manager
features
are
available
with
the
Script
Portlet:
• Content
targe?ng
based
on
devices
or
loca?ons
• Access
to
user
login
informa?on
• Adap?ve
design
that
uses
condi?onal
rendering
• Access
to
shared
render
parameters,
portlet
preferences,
and
live
text
The
Script
Portlet
has
the
following
advantages:
• Users
have
more
autonomy
and
less
dependence
on
central
IT
for
portlet
development,
which
decreases
the
?me
to
market.
• Users
need
less
skill
to
be
produc?ve
WebSphere
Portal
developers.
• Users
control
access
and
workflow
processes
in
enterprise
seyngs.
• Users
can
create
reusable
assets
and
contents.
• Users
can
render
exis?ng
portlets,
such
as
those
developed
with
IBM
Web
Experience
Factory
or
IBM
Ra?onal
Applica?on
Developer
IntegraAng
wit
IBM
Script
Portlet
(SP)
for
DX
43. IntegraAng
wit
IBM
Web
Experience
Factory
(WEF)
for
DX
Direct
integra?on
with
SAP
applica?ons
using
SAP
Java
connector
(SAP
JCo)
to
access
SAP
RFC-‐enabled
BAPIs.
This
is
a
quick
and
easy
approach
to
create
portlets
that
work
with
SAP
applica?ons.
Anyone
with
access
to
an
SAP
server
can
browse
and
directly
access
the
SAP
RFC-‐
enabled
BAPIs.
New
user
experiences
can
be
rapidly
created
and
deployed
to
meet
changing
business
requirements.
44. This
approach
offers
flexibility
because
you
can
reuse
the
data
as
you
refine
the
user
experience
and
build
new
ones.
By
separa?ng
SAP
applica?on
integra?on
from
the
user
experience,
it
also
buffers
the
user
experience
from
any
changes
on
the
back-‐end
SAP
system
User
creden?als
can
be
passed
to
SAP
applica?ons
through
the
IBM
Web
Experience
Factory
builders,
thereby
enabling
you
to
create
a
custom
experience
that
accesses
SAP
without
the
user
even
knowing
it.
This
token-‐passing
infrastructure
can
use
SSO
infrastructure
solu?ons
as
provided
by
SAML,
or
other
token-‐passing
SSO
solu?ons,
such
as
IBM
Security
Access
Manager
IntegraAng
wit
IBM
Web
Experience
Factory
(WEF)
for
DX
45. Web
Experience
Factory
Designer
is
a
plugin
to
Eclipse-‐based
integrated
development
environments
(IDEs).
Working
in
the
Web
Experience
Factory
perspec?ve
in
Eclipse,
you
create
projects,
for
which
you
use
builders
and
profile
sets
to
develop
models
and
generate
the
resul?ng
Web
applica?ons
from
those
models.
Each
builder
has
a
wizard
user
interface
through
which
you
specify
input.
The
builder
automa?cally
generates
or
modifies
part
of
the
applica?on.
IntegraAng
wit
IBM
Web
Experience
Factory
(WEF)
for
DX
46. Web
Experience
Factory
expose
five
Builder
for
SAP
• SAP
Batch
Input
builder
• SAP
FuncAon
Call
builder
• SAP
Help
Values
builder
• SAP
ProperAes
builder
• SAP
TransacAon
builder
IntegraAng
wit
IBM
Web
Experience
Factory
(WEF)
for
DX
47. SAP
Batch
Input
builder
Use
the
SAP
Batch
Input
builder
to
execute
an
exported
SAP
batch
input.
Using
features
in
the
builder,
you
can
parameterize
values
of
the
batch
process.
Addi?onally,
values
of
the
batch
can
be
designated
user
inputs.
This
builder
parses
a
recorded
SAP
batch
transac?on
that
has
been
exported
to
a
file.
The
builder
displays
the
transac?on
steps
in
a
table
and
you
can
specify
inputs
for
the
Value
field
for
each
transac?on
step
within
the
table.
The
builder
creates
a
Java™
method
that
can
be
called
to
execute
the
batch
opera?on
using
SAP.
IntegraAng
wit
IBM
Web
Experience
Factory
(WEF)
for
DX
48. SAP
FuncAon
Call
builder
This
builder
is
typically
used
in
a
service
provider
model
to
implement
a
service
opera?on.
With
it,
you
can
invoke
any
BAPI
or
remote-‐
enabled
func?on
from
SAP.
This
builder
is
typically
used
when
crea?ng
a
service
provider
model
that
accesses
data
from
SAP.
One
or
more
SAP
Func?on
Call
builders,
to
retrieve
or
store
data
from
SAP.
IntegraAng
wit
IBM
Web
Experience
Factory
(WEF)
for
DX
49. SAP
Help
Values
builder
The
SAP
Help
Values
builder
provides
access
to
the
help
values
associated
with
the
fields
present
in
an
SAP
func?on.
Help
values
are
a
list
of
valid
choices
for
a
given
func?on
field.
This
builder
can
be
used
to
populate
a
select
input
control
from
which
a
user
can
select
an
input
to
the
SAP.
A
benefit
of
using
this
builder
is
the
ease
with
which
its
output
can
be
used
to
populate
controls,
such
as
a
radio
bukon
group
or
a
select
list,
with
value
help
informa?on.
IntegraAng
wit
IBM
Web
Experience
Factory
(WEF)
for
DX
50. SAP
Help
Values
builder
The
proper?es
you
establish
in
this
builder
can
be
shared
by
other
SAP
builders
that
use
proper?es
(for
example,
SAP
Batch
and
SAP
Func?on
Call).
In
addi?on,
the
proper?es
set
in
this
builder
can
apply
across
mul?ple
SAP
servers
in
a
cluster,
as
well
as
to
a
single-‐server
environment.
IntegraAng
wit
IBM
Web
Experience
Factory
(WEF)
for
DX
51. SAP
ProperAes
builder
The
proper?es
you
establish
in
this
builder
can
be
shared
by
other
SAP
builders
that
use
proper?es
(for
example,
SAP
Batch
and
SAP
Func?on
Call).
In
addi?on,
the
proper?es
set
in
this
builder
can
apply
across
mul?ple
SAP
servers
in
a
cluster,
as
well
as
to
a
single-‐server
environment.
The
order
of
SAP
property
resolu?on
for
all
SAP
builders
that
require
proper?es
is
as
follows:
Use
proper?es
set
in
the
Advanced
sec?ons
of
SAP
Batch
and
SAP
Func?on
Call
builder
call
editor.
Look
for
connec?on
proper?es
supplied
by
an
SAP
Proper?es
builder.
Locate
the
SAP
Proper?es
file
specified
in
the
SAP
builder
input.
IntegraAng
wit
IBM
Web
Experience
Factory
(WEF)
for
DX
52. SAP
TransacAon
builder
This
builder
allows
you
to
call
mul?ple
SAP
func?ons
within
the
context
of
a
single
SAP
connec?on
or
transac?on.
You
might
need
to
do
this
if
the
BAPI
you
are
working
with,
or,
if
the
transac?on
you
are
performing,
requires
this
approach
to
calling
func?ons.
For
example,
this
situa?on
might
arise
if
you
call
BAPI_PERSDATA_CHANGE
to
update
employee
data.
In
this
case
you
must
call
the
following
three
BAPIs
on
the
same
SAP
connec?on:
BAPI_EMPLOYEE_ENQUEUE
BAPI_PERSDATA_CHANGE
BAPI_EMPLOYEE_DEQUEUE
IntegraAng
wit
IBM
Web
Experience
Factory
(WEF)
for
DX
53. Biometric
RecogniAon
SoluAon
(DDC
SAP
BRS)
BRS
is
the
solu?on
dedicated
to
Retail.
Integra?ng
specific
technologies
in
the
field
of
biometric
measurement.
BRS
includes
sensors
for
biometric
recogni?on
so`ware
and
data
collec?on,
analysis,
modeling
and
repor?ng
capabili?es
that
enable
customer
segmenta?on
(for
ages',
gender,
ethnicity,
aken?on
span)
and
measuring
their
buying
behavior
within
the
point
of
sale
in
order
to
evaluate
the
effec?veness
of
the
store.
The
?ming
of
aken?on
also
allows
you
to
measure
for
the
first
?me
the
direct
effect
of
shop
windows,
mannequins,
displays,
etc.,
And
ul?mately
the
effec?veness
of
In
store
marke?ng.
54. Biometric
RecogniAon
SoluAon
(DDC
SAP
BRS)
Significance
and
quality
of
the
informa?on
BRS
is
designed
to
provide
high
quality
measures
and
data:
Precision
counts
of
the
inflowing
visitors
and
their
demographic
profile;
• Gender
• Age
• Ethnic
group
Store
personnel
is
not
counted.
Aken?on
?me
is
calculated
exactly,
with
no
distor?ons
or
errors
Mul?ple
passages
of
a
customer
are
detected
and
managed
Complete
path
and
direc?on
tracking,
interest
points,
queues,
area
occupancy
and
heat
maps
55. Biometric
RecogniAon
SoluAon
(DDC
SAP
BRS)
The
result
is
guaranteed
to
be
significant,
clean
traffic
and
accurate
profile
informa?on.
Reliability
To
guarantee
service
con?nuity
all
the
components
used
for
BRS
are
first
class,
heavy
duty
proof
components.
BRS
runs
in
full
automated
mode:
no
need
of
administra?on
effort
for
the
solu?on.
Privacy
To
deal
with
even
the
most
restric?ve
privacy
rules,
as
it
is
typically
the
case
in
European
countries,
BRS
is
designed
to
operate
as
a
standard
with
a
maximum
degree
of
privacy
compliance:
No
pictures
and
no
personal
data
are
stored;
traced
and
closed
processes
avoid
any
possibility
of
misuse
56. Biometric
RecogniAon
SoluAon
(DDC
SAP
BRS)
All
experience
data
will
be
combine
with
Business
transac?on.
Usually
we
mix
data
collected
using
BRS
with
Cash
Transac?on
(receipt)
and
integrate
in
in
SAP.
We
can
iden?fy
which
type
of
user
have
purchased
and
how
much
spent
divided
by
• Gender
• Age
• Etnia
57. Taste
it
Scenario 1 : Mr Sap
sends
to
me
an
Ac?vityStream
Scenario 2 : Mr Sap
publishes
a
report
on
a
Community
Scenario 3 : Mr Sap
sends
to
me
an
Ac?vityStream
directly
from
an
incoming
order
Scenario 4 : Mr Sap with
BRS
show
me
my
Shop
averages