►
From YouTube: Recent Innovations and Roadmap - SAP Procurement
Description
In this session, you will see the roadmap of different SAP solutions for the Procurement function. You will see what is cooking in terms of functionalities and user interface innovations.
#SAPAriba #UserInterface #Innovation #procurement #productRoadmap
A
Good
afternoon,
thank
you
for
joining
and
thanks
for
the
monthly
joining
the
monthly
sig
session.
So
basically,
this
is
our
special
interest
group
for
procurement,
where
we
are
like
handling
the
webinars
on
a
monthly
basis
on
different
topic
across
across
portfolio
of
sap
products,
and
I'm
myself
priya.
I
think
most
of
you
would
know
me
so
I'm
part
of
the
regional
strategy,
team
handling
india,
market
unit
related
like
road
map
items
and
also
like
I
work
on
the
strategic
escalations
as
well.
A
So
today
we
are
going
to
discuss
about
or
that
webinar
is
about
the
roadmap
on
the
source
to
contract,
as
well
as
the
buy
and
deliver
topics.
So
we
have
two
speakers
with
us
today
to
present
the
topic,
and
I
would
let
kirtan
and
jaydeep
introduce
themselves
and
we
will
get
started
with
the
session
and
also
like.
If
you
have
any
questions
in
the
middle
of
the
session,
you
can
post
them
in
the
chat
or
feel
free
to
unmute
yourself,
and
you
can
ask
the
questions.
B
A
A
C
A
A
A
C
C
However,
before
that,
what
I
would
like
to
do
is
also
give
an
understanding
of
the
high
level
sap
strategy
in
the
area
of
procurement
talk
a
little
bit
about
the
intelligent
enterprise
and
give
you
some
background
as
to
where
our
company
is
going
and
these
part
of
the
solutions
so
again
just
a
legal
disclaimer
at
the
beginning.
There
are
certain
features
here
which
are
planned
out
in
the
future,
so
things
may
change
this.
This
is
how
it
stands
at
the
current
moment
with
regards
to
planning
okay.
C
Then
we
will
take
a
look
at
the
end-to-end
source
to
pay
processes
that
are
covered
as
part
of
the
solution
portfolio.
Next,
I
will
talk
about
the
buy
and
deliver
innovations.
A
few
of
them
that
were
recently
delivered
and
which
we
feel
are
important
and
then
look
at
the
roadmap
in
terms
of
again
the
key
features
that
we
are
planning
to
deliver
and
then
I
will
also
quickly
go
into
and
share
the
details
as
to
how
you
can
get
more
information
on
on
the
sap
procurement
roadmap.
Okay.
C
C
C
C
There
are
issues
around
integration,
so
certain
functionalities
have
limited
integration
and
we
will
take
a
look
at
what
are
the
areas
that
that
we
are
focusing
on
at
this
point
and
then,
as
I
said
earlier,
we
have
a
fragmented
stack
and
there
are
multiple,
multiple
platforms,
so
this
was
the
main
motivation.
Why
sap
looked
at
it
holistically
about
an
year
or
more
ago
and
and
decided
to
move
on
on
a
strategy
that
that
we
will
take
a
look
at
now?
C
Now,
when
we
look
at
this
particular
graphic,
it
shows
that
intelligent
enterprise
solution
portfolio
that
that
sap
has
and
how
all
of
these
pieces
fit
together.
Now.
A
key
part
of
this
strategy
is
how
the
integration
works
end
to
end
across
different
solutions
and
for
sap
making
integration
work
is
the
top
most
priority.
C
C
C
The
next
piece
here
is
I'll
talk
about
is
the
business
technology
platform,
which
really
is
the
core
or
the
foundation
to
all
of
this,
and
this
provides
data
management
and
analytics
and
supports
application.
Development
and
integration
of
these
solutions
end
to
end
right.
So
it
also
allows
customers
to
use
end-to-end
or
intelligent
technologies
in
end-to-end
business
processes,
so
these
could
be
ai
ml
internet
of
things
basically
to
drive
innovation
and
adoption
within
their
organization.
So
this
is
a
very
core
foundation
of
this
overall
strategy.
C
The
next
part
is
the
business
network
right.
So
we
have
a
unique
opportunity
to
build
a
new
kind
of
business
network
to
digitize
cross-company
business
processes
within
the
ecosystem
right,
so
the
business
network
can
build
on
on
your
procurement,
travel
or
contingent
workforce
solution.
So
we
already
have
the
ariba
network,
which,
which
basically
allows
buyers
and
suppliers
to
collaborate
on
different
transactions,
and
we
want
to
further
enhance
the
value
of
it
for
both
buyers
and
suppliers.
C
So
this
is
the
overall,
I
would
say,
architecture
that
sap
has
for
helping
our
customers
be
an
intelligent
enterprise,
and
it
would
really
help
customers
be
more
resilient,
successful
and
sustainable
and
be
the
best
run
businesses.
So
this
is
just
to
give
you
guys
a
high
level
picture
of
where
we
are
and
what
are
the
different
components
involved.
C
Next,
we'll
just
I'll
quickly
go
over
the
different
scenarios
that
we
are
building
as
part
of
the
intelligent
enterprise
for
integrated
enterprise.
It
can
start
it
starts
off
with
the
lead
to
cash
for
the
customer.
Then
we
have
the
source
to
pay
for
finance
and
procurement,
which
is
what
we
are
mainly
talking
about
here.
Then
there
is
a
scenario
around
recruit
and
retire
focused
primarily
around
human
resources
and
then
designed
to
operate,
which
is
more
catered
towards
manufacturing
and
supply
chain.
C
So
all
of
these
different
business
applications
are
kind
of
built
as
part
of
this
overall
solution
portfolio,
but
we
want
to
ensure
that
there
are
certain
sweet
qualities
that
are
common
across
all
of
these
solutions
and
and
which
we,
which
really
fit
very
well
and
help
our
customers
optimize
their
end-to-end
business
processes.
So
just
a
couple
of
examples
here
I
want
to
give
is
one:
is
seamless
user
experience
right?
So
what
do
we
need
for
that?
C
We
need
a
harmonized,
look
and
feel
and
navigation
patterns
across
all
of
these
solutions,
be
it
sap,
ariba
or
sap,
s4
or
sap
field
loss.
I'm
not
talking
about
source
to
pay
specifically.
So
only
when
we
have
this
harmonized,
look
and
feel
is
when
a
customer,
when
a
user
would
get
a
seamless
user
experience
or
we
need
to
have
consistent
security
and
identity
management.
C
So
you
need
to
have
a
central
identity,
provisioning,
an
authentication
mechanism
for
users
in
these
different
systems
or
which
users
which
operate
across
systems
to
be
able
to
use
more
effectively
or
we
need
embedded
and
cross
product
analytics
to
give
the
customers
a
360
degree,
business
and
customer
view.
So
there
are
a
number
of
sweet
qualities
which
are
defined
as
part
of
this
overall
intelligent
enterprise
and-
and
I
will
show
you-
what
are
some
of
those
that
we
have
achieved
as
part
of
our
intelligent
enterprise
strategy
within
source
to
pay
in
the
next
few
slides.
C
So,
let's
get
into
the
details
around
source
to
pay.
So
what
are
the
different
end-to-end
processes?
Or
what
is
the
terminology
that
we
typically
use
when
we
refer
to
source
to
pay
right?
So
this
is
the
overall
view
of
source
to
pay
process
so
starts
with
source
to
contract.
Right
from
your
category
strategy
to
managing
your
legal
contracts
with
trading
partners
includes
sourcing
of
your
materials
and
services.
A
C
Goods
and
services,
once
you
have
done
that
you
would
also
do
initiation
of
request
for
purchasing
those
goods
and
services,
execute
the
orders
and
then
deliver
and
receive
those
goods
and
services
when
once
your
suppliers
are
fulfilled
on
those
and
then
finally,
on
the
buying
side,
you
have
the
invoice
and
payment
where
you
create
and
manage
invoices
and
credit
memos
and
then
have
early
payment
options
and
then
do
the
payment.
So
this
is
pretty
much
the
buy
side
of
the
source
to
pay.
C
So
all
of
these
different
business
partners
or
trading
partners
need
to
work
together
with
your
companies
in
order
to
make
this
an
efficient
process
right.
So
there
are
different
aspects
again
here,
which
is
the
trading
partner
collaboration
on
the
the
trading
partner
and
risk
management,
so
understanding
the
risks
that
are
involved
in
are
doing
business
with
many
of
these
suppliers
also
analytics
and
intelligence,
and
then
for
certain
larger
organizations
which
have
multiple
entities
or
which,
which
need
to
be
managed
using
multiple
backend
drp
systems.
C
We
have
certain
capabilities
around
central
procurement,
so
think
of
it
like
like
the
srm
or
the
supply
relationship
management
system
which
sap
had
which
which
allowed
customers
to
connect
to
say
multiple
backend
drp.
So
that's
pretty
much
what
what
we
say
when
we
have
a
central
procurement
function,
helping
customers
to
manage
their
procurement
processes
across
different
backend
drps.
So
so
that's
like
the
overall
view
of
the
entire
source
to
pay
process
and
let's
now
take
a
look
into
what
are
some
of
these
processes
in
in
different
types
of
spend
channels.
C
So
when
we
say
s
to
p
or
source
to
pay,
we
categorize
these
into
into
different,
spend
channels,
starting
with
say,
indirect,
mro,
direct
and
then
services
are
contingent
labor.
So,
within
each
of
these
pen
types
we
have
identified
various
scenarios-
and
I
won't
go
into
all
of
these
here,
but
what
I
would
say
is
as
part
of
our
intelligent
enterprise
strategy.
C
We
have
started
executing
on
these
one
by
one
and
and
we've
almost
kind
of
completed
with
executing
on
the
indirect
spend
scenarios
which
is
around
integration
between
ariba,
guided
buying
and
s4
to
attain
a
seamless,
end-to-end
process.
Similarly
with
sourcing
and
contract
management,
commerce,
automation
and
code
automation.
A
C
And
more
scenarios
so
moving
forward.
I
just
want
to
now
give
a
quick
flavor
of
some
of
the
important
innovations
that
we
have
launched
in
the
last
few
months,
and
I
want
to
start
off
by
just
listing
down
what
are
the
different
integration
scenarios
that
we
have
launched,
which
I
mentioned
as
part
of
the
previous
slide.
So
these
are
just
the
identifiers
for
these
different
integration
scenarios.
C
C
Now
when
I
was
initially
talking
about
the
sweet
qualities,
these
are
some
of
the
technology
guidelines
or,
you
can
say,
sweet
qualities
that
have
been
achieved
as
part
of
as
part
of
these
different
releases,
so
reference
architectures
having
a
common
online
business
apis
across
solutions,
identification,
identity,
authentication
and
sso.
So
you
you,
don't
really
need
to
log
into
each
of
the
solution.
Your
single
sign
on
enable
you
to
seamlessly
navigate
across
solutions,
identity,
provisioning
and
life
cycle
management
having
a
consistent
user
experience.
C
So
that
was
a
big
one
where
we
basically
made
the
look
and
feel
of
these
solutions
very
similar
in
terms
of
the
shell
bar
or
the
button
styles
or
the
fonts,
and
so
on.
So
it
is.
It
is
basically
a
single
solution
that
experience
that
you
would
get
in
as
you
navigate
through
these
different
solutions
as
part
of
your
end-to-end
business
processes,
integration,
monitoring
and
automated
provisioning
are
also
some
that
we
are
working
on
and
continue
to
work
on
in
our
future
releases.
C
C
You
can
find
a
lot
of
information
on
the
sap
business
best
practices
hub,
where
you
will
see
all
of
these
scenarios
named
in
this
similar
way.
So
you
can
get
more
details.
You
can
see
the
exact
architecture
as
what
is
the
exact
business
process
that
you
are
looking
at
and
what
is
the
business
problem
and
the
benefits
that
you
would
get
out
of
each
of
these
different
scenarios.
C
So
I
wanted
to
only
put
in
one
important
one
which
is
specific
to
this
particular
topic:
around
buy
and
deliver,
which
is
the
guided
buying
integration
for
central
procurement
and
this.
How
does
this
integrate
with
arriba
buying?
So
this
is
a
this
is
a
customer
landscape
where
they
have
multiple
back
end
systems,
so
you're,
looking
at
an
sap,
erp
or
an
s4
or
other
back
ends
with
with
an
s4hana
central
procurement
hub,
which
is
used
by
the
customers
to
monitor
their
their
individual
back-end
systems.
C
And
then
you
have
a
reba
guided
buying
user
interface
to
actually
for
the
users
to
do
the
shopping
right.
So
the
process
starts
off
with
the
user,
coming
in
from
the
guided
from
the
s4
on
a
central
procurement
on
to
the
guided
buying
ui
selecting
items
from
the
catalog
submitting
the
requisition,
the
requisition
gets
validated.
C
C
Okay,
so
let's
move
on
to
the
next
innovation
that
we
recently
launched.
So
in
q1
of
this
year,
we
released
support
for
inventory
visibility
and
stock
reservation
for
our
sap
erp
customers.
So
what
does
this?
Do?
This
actually
greatly
improves
your
capability
to
manage
mro
spend
or
any
category
where
some
items
may
be
stocked,
so
be
it
spare
parts
or
lab
lab
equipment
or
clothing.
Just
a
few
examples.
C
So
user
can
basically
mix
the
regular
catalog
items
with
inventory
items
on
the
same
requisition
in
ariba
and
once
they
are
added
to
the
shopping
cart,
the
items
are
can
be
ordered
directly
from
your
supplier
once
the
once
the
requisition
is
approved
or
the
request
is
approved,
one
order
can
be
created
for
the
first
item
and
then
the
two
separate
reservation
documents
can
be
created
for
the
reservation
of
these
inventory
items.
So
in
this
particular
screen.
C
So
that's
a
big
feature
that
we
launched
in
q1
of
this
year.
We
are
planning
to
introduce
the
same
feature
also
for
guided
buying
in
in
early
2021.
So
I
just
wanted
to
mention
this
one.
The
second
one
that
I
wanted
to
mention
is
about
viewing
purchase
orders
in
guided
buying,
so
previously
users
could
view
purchase
orders
only
in
the
sap
area,
procurement
solutions,
meaning
the
classical
p2p
ui
or
p2o
ui.
C
C
It
also
has
details
around
what
is
the
confirmed:
quantity
or
the
ship
quantity,
etc.
It
just
gives
you
a
more
simplified
view
of
your
purchase
or
purchase
order
and
the
purchase
requisition
in
general,
so
this
was
again
a
very
important
feature
that
was
consistently
requested
by
many
of
our
customers
and
again
it
kind
of
flows
seamlessly
into
how
a
requisition
looks
as
well
in
your
guided
buying
ui.
C
C
So
some
of
you
may
be
familiar
with
the
sourcing
projects
and
the
concept
of
teams,
documents,
tasks
etc,
which
are
governed
by
the
flexible
project
templates
in
ariba
sourcing.
So
a
procurement
workspace
is
very
similar
to
it.
It
works
in
a
similar
manner,
but
here
the
documents
are
extended
to
kind
of
include
requisitions
purchase,
orders
and
invoices
as
well
from
ariba
buying
and
invoicing.
C
So
what
what
we
have
done
is
we
have
enhanced
the
guided
buying
user
interface
to
introduce
this
concept
of
procurement
workspace,
specifically
so,
with
the
concept
of
tiles
and
guided,
buying
and
forms
these
strength
of
procurement,
workspaces
can
be
really
brought
to
the
end
user
and
and
it
will
allow
customers
to
specifically
address
complex
buying
scenarios
categories
where
such
as
marketing
and
events
that
require
careful
planning
or
vendor
quotes
and
tracking
of
budgets.
So
this
is
a
very
exciting
functionality
that
will
really
vastly
improve
capabilities
to
kind
of
model.
This
complex
requirement.
C
C
This
capability
is
around
improved
user
experience
through
intelligent
approval,
so
as
part
of
our
initiative
to
embed
really
the
intelligent
capabilities
in
our
suite,
we
are
introducing
the
intelligent
approval
for
requisitions,
and
this
this
capability
is
planned
to
come
in
2021.
I
believe
so
what
what
this
does
is
it
this
initially
I
mean
this
is
introducing
the
concept
of
something
like
confidence.
C
So
if
a
user
wants
he
or
she
will
be
able
to
expand
into
that
score
and
get
more
details
into
as
to
what
are
the
attributes
that
are
contributing
to
making
that
score,
and
this
will.
This
will
basically
allow
users
to
make
quick
decisions
without
really
going
into
details
of
each
and
every
pr
and
understanding
and
approving
it
and
making
a
decision.
C
This
will
give
a
quick
view
of,
depending
on
the
confidence
score,
how
likely
this
pr
is
likely
to
be
approved
so,
and
this
again
touches
different,
has
different
touch
points
starting
with
reba
buying
or
guided
buying.
It
will
also
kind
of
go
into
say,
email
based
approvals
and
mobile
mobile
app
approvals
as
well.
So
this
is
one
capability
where
we
are
using
intelligent
technology
as
part
of
the
new
sap
ariba
procurement
mobile
app.
C
We
are,
firstly
revamping
the
user
interface
based
on
the
theory
standards
and
then
we
are
also
introducing
sourcing
and
contract
task
management,
which
will
also
be
now
available
from
our
q4
release,
and
we
are
introducing
the
concept
of
push
notification
part
of
the
mobile
app.
So
these
are
the
three
capabilities
that
that
are
planned
to
be
introduced
as
part
of
our
q4
mobile
app
release.
C
C
So
this
is
especially
tailored
for
service
estimates.
Where
really,
you
need
a
non-binding
code
from
from
one
or
many
vendors
right.
So
these
responses,
the
vendors,
could
give
could
include
like
really
line
level
information
containing
goods
containing
catalog
items
or
contracted
items
or
service
elements,
and
these,
then
the
awarded
bit
could
result
into
creating
a
requisition
or
a
contract
for
a
later
release.
Right.
So
that's
something
that
that
will
come,
and
this
is
really
going
to
help
us
completely
digitize
end-to-end
process
from
a
project
engagement
spend.
A
C
C
So,
as
I
mentioned
earlier,
we
are
working
on
tightly
integrating
s4hana
with
ariba
as
well,
so
this
functionality,
basically
routes
external
purchases
of
goods
and
services
on
work,
orders
through
ariba
buying
solution
and
the
riba
network.
So
this
will
allow
customers
to
drive
more
compliance
through
catalog
prices
and
contracts,
while
continuously
tracking
the
sap
work
order
id
across
the
reba
solution.
C
So
that's
that's
quite
beneficial
to
understand
where
it
is
originating
from
also
this
can
be
tracked
across
the
procurement
operations
desk,
the
pod,
where
they
can
then
edit
the
request
and
and
collaborate
between
different
team
members.
So
this
is
also
another
feature
that
is
around
services
procurement,
so
those
were
just
a
few
of
the
important
ones
that
I
highlighted.
C
I
want
to
just
quickly
in
the
interest
of
time.
I
want
to
just
quickly
go
in
and
just
show
you
the
content.
I
think
many
of
you
may
be
very
familiar
with
the
release
readiness
section
on
the
reebok
connect
where
you
can
find
different
details
of
the
different
releases
and
where
you
can
find
content
related
to
each
and
every
feature.
A
B
I'm
kirtan
ray,
and
I
part
of
the
regional
solution
strategy
group
and
to
go
through
an
overview
just
to
give
you
an
highlight
on
the
agenda,
so
the
edge
has
already
covered
where
you
can
find
information
on
the
existing
roadmap,
as
well
as
processors
on
release
readiness.
So
I'm
not
going
to
cover
that
aspect.
Also,
some
of
the
recent
innovations
that
we
have
launched
you
can
find
that
information
readily
available.
B
The
core
of
this
presentation
is
going
to
be
some
of
the
large
marquee
innovations
that
we
are
planning
for
sourcing
and
contracts
in
the
upcoming
quarters.
Now
some
of
these
features
as
we
go
along,
even
though
most
of
them
are
planned
for
future.
Some
of
them
might
have
already
been
released,
but
they
are,
they
are
a
small
percentage
and
they
are
in
context
to
some
of
the
larger
features
that
are
coming
up
later
on
in
the
quarter.
So
bear
with
me
on
that
side,
legal
disclaimer.
B
So
let's
start
with
the
sourcing
innovations
first,
so
we've
been
for
those
of
you
that
are
aware
that
are
already
customers
of
sap,
reba
and
so
and
are
aware
of
sourcing.
This
is
one
of
our
marquee
solutions
in
the
in
our
solution.
Portfolio
and
we've
been
working
on
a
brand
new
sourcing
ux
for
the
past
few
quarters
and
for
the
last
in
in
2020,
starting
to
in
q1
of
this
year,
that
is
jan
feb
march
of
this
year.
B
B
So
the
bulk
of
what
you'll
see
on
sourcing
future
roadmap
innovations
will
be
related
to
the
guided
sourcing
ux.
Now,
what
is
the
guided
sourcing
ux?
So
this
is
a
new
layer
of
functionalities
that
we
have
built
upon
the
existing
sourcing
engine
that
provides
several
new
enhancements
to
the
way
that
the
user
would
interact
with
the
system
in
terms
of
creating
the
sourcing
project
in
terms
of
managing
it.
Awarding.
B
Navigating
through
various
elements
of
the
sourcing
life
cycle
itself,
right
from
creation,
inviting
suppliers
line
item
management,
and
so
it
is
not
just
going
to
be
a
new
skin
on
the
old
product.
That,
of
course,
is
there,
but
at
the
same
time
there
are
also
some
net
new
functionalities
that
we'll
be
introducing
in
guided
sourcing
with
this
release
and
to
give
you
an
example,
closer
home
is
that
of
guided
buying
that
we
launched
several
three
years
back.
B
B
So
we
are
making
this
opt-in
capability,
which
means
that
customers
can
opt
to,
depending
on
the
capabilities
that
are
available
at
that
point
in
time,
customers
can
opt
in
for
guided
sourcing
and
then
evaluate
and
based
on
that
they
can
adopt
it.
Roll
it
out
to
multiple
users
doesn't
mean
that
the
old
sourcing
ux
is
switched
off
and
the
new
one
is,
and
it's
it's
not
binary,
so,
which
means
both
the
sourcing
ux
can
co-exist.
B
Take
you
through
some
of
the
capabilities
over
here,
but
just
to
give
you
an
idea,
some
of
based
on
the
current
observations
with
our
customers.
We've
released.
We've
realized
almost
a
50
reduction
in
the
number
of
clicks
or
the
time
taken
to
create
a
sourcing
event
with
the
new
sourcing
ux.
This
is
because
of
the
various
enhancements
that
have
happened
in
in
terms
of
the
way
assist
user
interacts
with
the
system
and
you'll
see
some
of
these
capabilities.
As
I
walk
you
through,
but
some
of
these
capabilities
is
number
one.
B
Is
the
brand
new
the
ux
in
terms
of
the
sourcing
creation
process
itself?
There
are
capabilities
on
the
line
item
management
side
wherein,
instead
of
having
to
go
through
a
separate
tab
and
managing
these
line
items
one
by
one,
there's
bulk
line
item
management
capabilities.
There
is
enhanced
ux
to
manage
that
there
are
capabilities
on
even
exporting
importing
the
line
items
through
unstructured
files
and
and
so
on,
and
we've
also
introduced
some
intelligence
into
the
system
wherein
users
can
now.
B
Instead
of
sticking
to
a
very
rigid
form
of
line
item
import
which
we
used
to
through
a
standard
template.
We
have
introduced
unstructured
file
template
wherein
users
can
pretty
much
enter
line
item
details
through
a
file
of
their
format,
an
excel
file
of
their
format,
and
the
system
will
read
through
that
parse
through
that
and
generate
the
line
items
in
the
ariba
format
and
then
present
it
in
the
ui
for
the
user
to
approve
or
accept
and
so
on.
B
So
that's
that's
the
intelligence
part
that's
been
introduced
in
the
first
phase
of
release
and
then
we've
also
introduced
some
new
sourcing
capabilities,
core
functionalities
itself,
for
example,
multi-round
sourcing
ability
to
have
a
single
sourcing
event
have
multiple
rounds
of
bidding
between
suppliers.
So
you
can
include
a
set
of
suppliers
to
get
a
better
price
all
within
the
same
sourcing
event.
B
B
B
All
right,
perfect,
okay,
so
here
is
the
first
of
all.
What
we
have
introduced
is
a
tab
called
for
you,
which
is
a
separate
screen
within
ariba
itself.
You
have
sourcing
entitlement,
but
you
can
also
embed
it
within
your
familiar
ariba
sourcing,
page
as
a
portlet,
so
the
sourcing
for
you
page
is
a
stream
of
is
like
a
facebook
timeline
of
all
the
events
that
you,
as
a
user,
is
involved
in
and
provides
real-time
updates
on.
B
Approvals
can
be
managed
within
the
portlet
itself,
so
this
is
like
a
scrolling
timeline
that
you
would
see
on
the
on
the
page.
In
this
case,
we
made
it
as
a
portlet,
which
is
a
miniature
version,
but
there
is
a
separate
tab
which
details
all
the
information
that
you
would
want
to
see.
So,
let's
skip
through
that
and
go
through
the
the
event
creation
mode.
So
here
I'm
going
to
create
an
event.
B
So,
as
you
see
the
whole
event,
creation
page
itself
has
completely
changed,
but
with
all
the
familiar
items
that
you
would
see
in
a
normal
event,
creation
page
with
nariba.
Today,
for
example,
you
enter
the
metadata
fields
and,
based
on
that,
the
template
is
selected.
You
can
look
up
for
template
now.
There
is
a
search
window
for
the
template
itself.
I
go
ahead
and
select
this
and
now
we
are
launched
to
the
sourcing
creation
page.
So
what
is
different
here
is,
and
this
is
the
crux
of
the
the
development
here.
B
What
you
would
see
here
is,
unlike
in
the
past,
where
you'd
had
to
go
through
multiple
different
tabs,
such
as
project
documents,
team
documents,
suppliers
line
items
all
within
separate
tabs,
which
reflect
required
multiple
clicks
to
get
through
this
entire
event
is
on
a
rolling
screen
scrolling
screen
view.
So
all
the
processes,
starting
from
questions
adding
of
suppliers
adding
of
items
even
duration
management
line,
item
headers
teams,
rules.
Everything
is
mentioned
in
the
same
page,
which
means
that
you
don't
need
to.
B
You
have
saved
several
clicks
back
and
forth
and
all
of
these
items,
starting
from
the
header
item
etc
are
in
line
in
are
in
an
inline
editable
mode.
Assuming
that
you
don't
need
to
again
go
into
edit
attributes,
then
change
the
item,
level,
details
and
so
on
not
going
to
go
into
that
specifically.
But
let's
go
through
the
invite
supplier.
So
I'm
going
to,
and
this
this
view
process
flow
shows
what
stage
you're
in
exactly
in
in
your
sourcing
life
cycle.
So
you
go
ahead
and
invite
suppliers.
B
So
in
the
invite
screen
which
is
familiar,
you
can
filter
your
suppliers
based
on
multiple
parameters
coming
in
from
slp
and
so
on.
But
some
new
things
that
we've
introduced
is
say:
you
have
a
supplier,
and
now
you
have
an
info
card
for
that
supplier
that
pops
up
with
all
the
information
coming
in
from
slp
on
what
is
the
vendor
id
their
status
address
and
so
on
contacts,
their
qualifications,
certifications
if
any,
and
you
also
have
qualified
info
which,
whatever
they're
qualified
for
if
they're
preferred
for
some
other
commodity.
B
B
But
let
me
go
ahead
and
invite
the
supplier,
so
we've
invited
three
suppliers.
Next
item
in
the
in
the
process
would
be
to
add
the
items
now
here.
There
are
multiple
ways
you
can
add
items
to
the
traditional
way
of
adding
items
one
by
one
and
you
we
have
erp
integration,
just
the
way
we
had
in
the
old
ux,
but
another
novel
way
of
doing
this
is
through
the
unstructured
excel.
So
this
is
a
feature
that
I
mentioned.
You
mentioned
briefly
in
the
slide
as
well.
B
So
typically
today
we
have
a
rigid
form
of
excel
import
and
export
of
line
items
wherein
alibaba
provides
that
information.
The
information
has
to
be
in
that
exact
form
and
format,
and
you
upload
it
and
the
forms
are
populated
and
the
line
items
are
populated
in
the
ui
with
the
terms.
So
what
we've
introduced
is
you
can
actually
create
a
line
item
excel
sheet
based
on
your
own
format,
and
that's
why
the
term
unstructured.
B
So
with
with
some
of
these
item
ids
plans
and
quantity,
you
upload
that
file
onto
the
system
and
the
system
reads
through
that
and
populates
the
line
items
with
the
corresponding
terms.
Now
this
is
machine,
read
output,
so
as
a
user,
you
can
go
ahead
and
even
change
them
or
modify
update
it
as
you
as
you
please,
but
in
this
case
let's
go
ahead
and
import
the
items
into
the
event.
B
So
now
all
these
items
with
their
item,
ids
based
on
the
material
number,
is
imported,
and
you
now
want
to
add
and
how
to
want
to
make
some
edits
on
this
thing.
Another
feature
that
we've
introduced
is
notice.
All
these
items
have
full
screen
views,
which
means
that
if
you
want
to
manage
a
particular
component
of
the
sourcing
creations
or
items
questions
supplier,
you
can
slip
into
a
full
screen
mode
and
within
the
full
screen
mode.
B
There
is
bulk
edit
options,
which
means
so
you
can
actually
have
say,
add
terms
on
bulk,
select,
multiple
items
that
are
part
of
your
sourcing
event
or
select
all
or
select
few
and
selectively
add
terms
in
bulk.
So
I'm
going
to
add
a
term
in
this
case
for
manufacturer
name
and
now
that
it's
added
it's
available
on
all
the
line
item
terms,
I
want
to
go
ahead
and
say,
select
a
few
more
terms
and
make
some
edits
on
some
of
the
line
items.
B
So
in
this
case
I
am
going
to
all
the
terms
that
are
available
for
that
sourcing
event
is
available
here.
I
simply
go
ahead
and
search
what
term
I
need
to
make,
and
I
say
I
want
to
add
acme
as
the
manufacturer
name
as
default
for
all
the
items.
Now
you
could
have
selected
it
only
for
a
num
only
for
a
subset
of
these
items
and
that's
perfectly
fine
as
well.
In
fact,
you
would
even
have
the
option
to
edit
it
in
line.
B
So
a
lot
of
effort
saved
here
again
in
terms
of
managing
line
items,
managing
importing
line
items
and
editing
those.
I
like
line
items
on
the
go,
so
we
go
ahead,
go
back
to
the
screen
and
the
same
ways
for
questions.
Also,
these
questions
are
coming
in
from
the
ux
from
the
template,
but
as
with
line
items,
you
could
have
gone
ahead
and
created
a
in
fact
done
any
edits
on
the
line
items
on
the
questions
inline
or
you
could
have
added
those
questions
within
the
full
screen
mode.
B
Pretty
much
the
same
experience
as
going
through
the
line
item
experience
so
go
ahead
and
submit
the
event.
We
start
monitoring
it.
So
there
is
a
new
monitoring
interface
with
a
lot
more
visual
indicators
on
how
the
line
item,
how
the
event
is
progressing.
As
you
can
see,
let's,
let's
see
how
the
as
the
event
progresses
so
number
of
suppliers
respond.
There
is
change
in
the
graphs,
so
this
indicators
on
how
many
have
responded.
B
What
is
the
status
of
the
supplier
participation
at
any
given
point
of
time
and
the
item
coverage
and
so
on
and
as
well
as
the
event
duration
indicator?
So
now
we
see
now
all
the
suppliers
have
participated.
You
see
that
again,
the
line
item
console
here,
a
very
visually
appealing
indicator
on
which
is
leading
what
suppliers
are
qualified
for
age.
What
is
the
rank
of
that
supplier
for
that
given
item?
What's
what's
the
percentage
who's,
the
lowest,
so
all
of
them
listed
in
the
ui
itself,
without
having
to
do
the
comparison
through
multiple
charts?
B
But
the
other
aspect
is
I
go
ahead,
and
so
what
you
see
here
is
it's
showing
as
a
round
one.
So
this
is
another
feature
that
we've
introduced,
which
allows
users
to
do
multiple
rounds
of
events,
so
which
means
that
you
don't
have
to
close
this
event.
Suppliers
typical
customers
typically
want
to
engage
with
suppliers
in
multiple
rounds
of
events
within
the
same
sourcing
event,
so
that
they
realize
better
prices
than
the
current
event.
So
in
this
case,
I'm
going
to
stop
the
event,
I'm
going
to
start
a
new
round.
B
So
you
just
you-
can
have
this
multiple
rounds
using
various
combinations
of
not
just
suppliers
but
also
of
the
event
items
itself,
some
items
that
you
feel
that
you've
realized
the
lowest
price.
You
exclude
them
for
the
that
round
and
probably
want
to
introduce
it
for
the
next
round
and
so
on.
So
all
of
those
rounds
of
information
will
be
available
as
part
of
reporting
will
be
available
as
part
of
your
sourcing
award
decision,
which
means
that
you
can.
B
You
can
have
that
multiple
iterations
within
a
common
event
without
having
to
create
multiple
sourcing
events.
So
we
see
that
now,
after
two
rounds
supply
responses
have
come
in
and
we
submit
for
award
for
approval
and
all
the
event
information
at
that
point
is
now
available.
You
can
also
have
initially,
we
will
only
have
some
out
of
the
box
scenarios
for
optimization
and
but
the
ones
that
you
currently
see
in
your
ux
for
conditional
optimization
scenarios.
B
So
once
all
of
this
is
done,
you're
going
back
to
the
dashboard
say
you
are
an
approver
for
event,
awarding
you
go
back
to
the
for
you
screen
and
you
see
that
not
only
has
the
timeline
of
those
event
updated,
but
you
also
have
an
action
awaiting
your
approval
and
you
can
do
this
approval
within
a
single
click
itself,
or
actually
you
can
go
to
the
event.
So
in
this
case
we
go
ahead
and
approve
the
event,
and
then
we
come
on
to
the
next
feature.
That
is
there,
which
is
the
bid
comparison.
B
So
we've
introduced
this
new
feature.
This
is
currently
uvic
currently
generally
available
as
we
speak,
but
in
this
case
we
have
some
additional
information
across
multiple
rounds.
So
all
the
information
that
is
available
in
the
sourcing
event
would
now
be
the
bit.
The
comparison
report
itself
will
be
completely
configurable,
including
what
type
of
highlights
you
want
to
include?
What
is
the
type
of
terms
you
want
to
include?
B
What
are
the
visual
indicators
for
high
and
low
and
winning
bid
that
you
want
to
include
in
the
report?
All
of
those
can
be
managed
and
in
addition,
if
it's
a
multi-round
event,
what
is
the
kind
of
what
are
the
number
of
rounds
of
information
that
you
would
want
to
include?
So
you
will
see
here
that
there
are
various
tabs
or
various
tabs
that
you
can
use
to
configure
like
terms
rolling
up
highlighting
of
certain
values
based
on
their
weightage
or
their
win
ability
and
sorting
and
so
on
and
so
forth.
B
So
this
is
a
new
feature.
That's
already
ga.
I
strongly
suggest
that
you
explore
this,
but
I
am
just
highlighting
it
in
the
new
ux
as
well,
because
it
includes
some
additional
features,
such
as
multi-round
reporting
as
well.
You
export
the
feature
and
all
the
information
is
then
available
in
your
excel
sheet,
as
well
for
for
auditability,
as
well
as
for
circulation
within
the
team
for
next
rounds
of
approval.
B
B
So
we
are
planning
for
a
guided
beta
with
a
minimum
set
of
minimum
set
of
features.
That's
in
when
it
goes
in
q4
note
that
not
all
the
capabilities
will
be
available
right
on
day
one,
and
as
we
progress
through
multiple
phases,
we
will
bring
in
scope
several
other
functionalities
from
the
legacy
to
the
new
sourcing.
Ux,
such
as
auctions
will
be
available
in
q3
in
phase
3.
B
Erp
integrations
full
projects,
and
some
additional
capabilities,
such
as
intelligent
recommendation,
multi-stage
events
and
so
on,
will
will
be
added
as
we
make
progress
in
the
upcoming
rounds.
But,
like
I
said
it
is
not
all
or
nothing
at
this
point
of
time,
which
means
that
even
in
q4,
when
it's
released,
you
can
roll
it
out
to
a
select
set
of
suppliers,
a
select
set
of
buyers
in
your
organization.
There
is
no
cost
and
you
can
determine
it.
Ways
by
simple
group
allocation
and
users
can
start
using
it
without
without
any
disruption.
B
B
A
B
It
could
be
a
word
document,
a
pdf
and
even
an
image
file
which
has
been
scanned
as
an
ocr,
a
jpeg
file
or
a
tif
image,
and
the
system
will
go
through
that
and
parse
through
and
you
can
search
for
clauses
or
terms
in
that
contract
document.
So
ability
to
do
such
intelligent
repository
search
will
be
made
available
as
part
of
the
contract
repository
feature.
This
is
planned
for
21
2021
release
again
part
of
our
overall
partnership
with
ibm
watson.
B
B
But
what
happens
is
that,
even
even
when
you
load
them
as
attachments,
somebody
needs
to
physically
go
through
those
documents
to
understand
what
is
the
header
level
data?
What
is
the
supplier
starting
date
ending
date?
Any
custom
terms
that
you
maintain
for
the
contract
has
to
be
manually
read
through,
which
becomes
a
manually,
tedious
task
for
a
user
to
create
truly
digital
contract
migration.
B
What
typically
customers
end
up
doing
is
having
those
documents
as
attachments
in
their
contract
workspaces
and
the
data
within
the
files
in
the
contract
file
itself
does
not
match
with
the
data
in
the
actual
electronic
contract
workspace.
So
what
we
are
bringing
what
we
are
planning
to
bring
with
this
feature
is
ability
for
the
system
to
read
through
any
unstructured
document
and
extract
all
the
elements
of
that
extract,
all
the
elements
from
their
document
and
create
a
contract
workspace
within
ariba.
B
The
system
reads
through
the
document
and
creates
all
the
metadata
headers
on
the
document
extracts
all
the
metadata
headers
like
what
is
the
agreement
name?
What
are
the
effective
dates
termination?
What
is
the
contract
amount?
What
is
the
supplier
and
so
on
and
so
forth?
All
the
standard
out
of
the
box
metadata,
as
well
as
any
custom
metadata,
would
be
extracted
and
populated
in
the
ui.
Now
the
buyer
would
go
through
that,
and
the
system
would
also
assign
the
confidence
score
based
on
matching.
B
In
some
cases
it
would
be
high
and
others
it
would
be
low
system.
The
user
has
the
option
to
override
or
update
any
of
these
fields
based
on
his
discretion,
but
once
he's
done
that
an
agreement
contract
workspace
is
created
within
arrival.
So
this
is
a
regular
contract
workspace,
as
you
would
create
within
the
ui
itself
today,
going
through
all
of
the
header
and
inputting
all
the
fields
manually
so
a
same
way.
B
A
contract
workspace
is
also
created
within
by
through
by
reading
through
the
document,
and
once
that
is
done,
the
document
itself
that
was
used
as
an
input
resides
within
the
contract.
Workspace
and
the
users
can
then
create
a
first
class
contract
workspace
document
that
ref
that
is
accurate
and
reconciles
with
the
data
that
is
actually
in
the
legacy
document.
B
So
do
you
want
to
change
it
so
things
like
that,
so
all
of
the
ability
to
read
those
files
and
create
those
auto
creation
of
workspace
from
documents.
That
is
also
a
feature
that
we
currently
slaughtered
in
21
as
part
of
our
intelligence
embedded
intelligence
within
contracts,
some
so
moving
on.
The
next
set
of
features
is
the
contract
apis
over
the
last
few
quarters,
starting
from
q2,
which
is
the
may
release
of
this
year.
B
Workspace
update
a
contract
workspace
as
well
as
retrieve
it
from
ariba,
so
we've
already
released
the
first
phase
in
which
users
are
able
to
update
contract
workspace,
header
you're,
able
to
extract
workspace,
metadata,
headers,
metadata
fields
create
metadata
as
well
as
update
it.
As
we
move
along
in
subsequent
releases,
we
will
also
expand
in
the
scope
of
those
api's
ability
to
add
documents,
ability
to
extract
documents,
ability
to
have
update
teams
and
tasks
using
those
apis
update,
create
clid
documents
and
so
on.
B
So
pretty
much
imagine
if
you
were
to
create
doc
create
a
contract
from
an
external
system.
You
could
use
this
api
to
trigger
the
creation
of
the
apis
or,
if
you
want
to
retrieve
all
of
the
contract
information
from
ariba
into
your
system
for
archival
or
other
references,
you
can
extract
all
of
that
across
all
the
objects
that
is
available
in
the
contract
in
a
typical
contract.
Workspace.
B
B
The
same
status
can
be
set
up
for
publishing,
also,
which
means
that
prior
to
publishing
the
system
will
check
if
your
required
status
is
being
met
by
the
supplier
or
not.
If
a
supplier
is
not
saying
in
this
example,
not
qualified
for
a
particular
product
for
a
particular
commodity,
the
system
will
prevent
the
user
from
publishing
that
contract
and
until
and
unless
that
supplier
has
been
actually
qualified
as
one
for
in
the
slp.
B
The
system
will
not
allow
the
user
to
publish.
So
there
will
be
three
tasks
that
will
be
that
the
system
can
configure
based
on
this
eligibility
criteria.
One
is
contract
creation,
one
is
contract
publishing
and
the
third
is
integration
of
contract
with
the
erp
all
based
on
integration
status
that
is
coming
in
from
the
slp
product.
So
you
can
see
all
of
these
status
that
is
maintained
in
slp,
like
qualification,
qualified
in
disqualification
restricted
and
so
on.
B
Some
other
features
that
are
currently
already
available
in
contracts
today,
clid
ability
to
embed
clid
in
in
main
agreement.
So
the
line
item
document
is
a
very
rich
functionality.
It
contains
a
lot
of
heavy
duty
information
online
items,
so
users,
typically
as
part
of
their
contract
negotiation
process,
want
to
include
some
sort
of
information
about
that
line,
items
and
the
terms
in
the
main
agreement
so
that
it
is
sent
for
signature
to
the
suppliers.
B
So
any
items
that
you
any
columns
that
you
pick
up
from
line
item
document
will
be
available
along
with
their
respective
data
provided
by
the
supplier
or
maintained
by
the
user,
for
example,
pricing,
quantity
or
any
other
terms
and
embedded
within
the
main
agreement.
You
can
insert
this
at
any
point
in
the
main
agreement
and
multiple
times
within
the
main
agreement
as
well.
Just
like
you
would
add
a
clause
from
your
clause
library,
so
that
capability
is
currently
available
as
part
of
our
contracts
process
as
part
of
a
contract
offering
for
strategic
sourcing
suite
customers.
B
We
also
made
some
enhancements
on
the
excel
based
import
of
line
items.
I'm
not
going
to
go
through
this
much
because
this
is.
This
is
very
similar
to
the
feature
that
was
released
in
sourcing.
A
couple
of
quarters
back
so,
instead
of
having
multiple
tabs
for
line
item
import
and
export,
we
provide
a
simplified
excel
utility
that
simplified
excel
format.
That
users
can
use
to
update,
as
well
as
create
new
line
items
on
clid.
B
We
also
coming
to
the
last
feature
in
contracts
we've
taken
a
step
up
in
our
current
integration
with
sourcing.
In
that
now,
users
can
use
all
all
the
sourcing
questions
if
a
user
is
creating
a
contract
workspace
from
a
sourcing
event.
All
the
sourcing
questions
that
are
available
as
part
of
that
sourcing
event
would
now
be
visible
within
contracts
workspace
and
these
cons
questions
themselves
can
be
again
embedded
within
the
main
agreement.
B
They
can
be
used
also
as
conditions
to
drive
other
parameters
such
as
team
member
inclusion,
such
as
document
inclusion
tasks
and
so
on
so
based
on.
Instead
of
having
to
maintain
several
thousands
of
templates
for
each
kind
of
a
varying
parameter,
users
can
now
based
on
the
suppliers,
responses
actually
trigger
actions
within
the
contract,
workspace
itself.
So
if
a
supplier
says
that
they
are
in
the
sourcing
event,
if
you
ask
a
question,
are
you
certified
for
information
security?
B
And
the
answer
is
no,
and
you
still
awarded
him
though,
but
you
would
like
to
include
additional
controls
or
additional
clauses
in
your
main
agreement
as
part
of
your
contract
process,
which
means
that,
based
on
the
response,
those
clauses
will
be
automatically
included
or
an
additional
team
member
can
be
added
or
additional
workflow
can
be
triggered,
and
so
on.
So
a
tighter
integration
between
the
sourcing
and
contracts.
Workflow,
basically,
is
what
this
feature
is
again
currently
generally
available
is
part
of
our
strategic
sourcing
suite
offering
for
contracts
and
sourcing
customers.
B
A
B
A
B
A
Yeah,
okay,
so
I
think
then
we'll
go
ahead
and
close
the
session
and
thank
you
so
much
for
your
time
and
the
session.
It
was
quite
informative
and
we
will
be
sharing
this
recording
with
all
the
participants
and
probably
like
if
there
is
any
additional
questions
on
the
email
or
the
whatsapp
group,
what
we
have
for
sig
we'll
keep
you
updated
yeah.