12-Inspirage Training - Demantra - Security v2

Demantra Data and
Function Security
Copyright © Inspirage LLC, 2008. Private and confidential. All rights reserved Page 1
The Oracle APS and Demantra Specialists

Session Objectives
• User security features and configuration steps
within Demantra
• Feature/Object security features and
configuration steps
• What is a “Component” within Demantra?
• Data security and implementation
considerations

User
Security

Users and Groups
• Users are created through business modeler
• For e-business suite users, creation of users in e-business
automatically creates corresponding users in Demantra
• Groups are a collection of users

• One user can belong in many groups
• Workflows refer to Users and Groups to tie process

and people together

User Creation/Modification Access from
business
modeler
Create / Modify
users
Implementation Tip:
Create one representative
user per stakeholder first.
Use that user as a template
to create other users in the
stakeholder group.

User Creation / Modification
• User create /
modify main
screen
• Define permission
levels
• Email address,
etc.
In an 11i/R12 integrated version, user is

automatically created in Demantra

• Administrative and
software tools that
the users have
access to.
• (This is Different
from components)

• Series that the

users have
access to.
Implementation Tip: Reduce clutter

• Data filters that

restrict what the
users can and
cannot see.
• How can two business groups co-exist without

stepping on each other?
• How can you create read-only users?

• Groups that the
users belong to.
Implementation Tip: Create a group for every

distinct stakeholder sets for easy management

Groups Creation / Modification

Feature
Security

Feature Security
• Demantra features are secured through permission
levels
– There are 4 pre-defined permission levels that
can be customized
• Permission levels control administrative tools and to
menu items. For example:
– Menus on Collaborator Workbench menu bar
– Menus on Demand Planner menu bar
– Right click menu options from each level
• Menu options can be controlled at user level or
group level
– There are pre-defined program groups that can
be customized

Collaborator Workbench Admin

Define Menus
• Define menus
available for a
component

Define Program Permission
• Define which
users have
what
permissions.
• Permissions
flow through a
hierarchy

• Programs are
hidden, Disabled
or Inherited
through the
hierarchy
Implementation Tip: Remove edit and delete from

Demantra menu options. The source of truth
should be ERP or execution systems

• Optionally group programs
into program groups and
control permission at the
program group level

Define who can access what features of worksheet

Remove certain privileges for certain
stakeholders..

Define content security
• Define what
content is
available to
which user

Define Pane Layout and Content
• Select
worksheets
available in
wide and
narrow pane

Demantra
Components

“Component” definition
• Component is an application developed using Demantra as
a toolkit
– Demantra is often referred to as a toolkit capable of
building many different applications
– Demand Management is a component as is Sales and
Operations Planning.
• Levels, hierarchies and dimensions are common across all
components but certain levels/hierarchies can be made
invisible to selective components
– Sales & Operations planning component’s levels and
hierarchies are a super set of DM levels and hierarchies
• Users and groups are specific to components
– For example, S&OP users could be different from DM
users

Component Creation/Modification
• Access from
business
modeler
• Component
visible only to
component
owner

Component Setup
• Component
setup main
screen

Component Setup
• Define what
series are
available to a
component

Component Setup
• Preference to
indicate/display
notes icon, plan
scenarios, etc
defined on
series’
item/location
intersections

Component Setup
• Levels
permissions
within the
components

Component Setup
• Units
available for
a component

Component Setup
• Exchange
rates visible
in a
component

Component Setup
• Worksheets for
levels setup
• Default
worksheet
opens when
clicked on
“Open” from
level member
• All other
worksheets
available as list
of options for
“Open With”

Component Setup
• Engine profiles
available for a
component

Component Setup
• Component
owner and
password

Data
Security

Data Security
• Confluence of all the previous security setups
• Users are attached to components
– Components restrict what series and levels are available to
it.
– For example, Production Plan is available only to S&OP
component.
– Only S&OP users even have the possibility to see the
Production Plan series and Plan Scenario level
• The users that have access to a series are setup in the series
definition and also through the user setup
• Data filters
– Level filters at the user setup level control what levels and
level members the user has access to.
– All other levels and level members are not visible to the user

Implementation Considerations
• Who needs access to what components?
– Demand management, S&OP or both?
• Who needs access to what programs?
– Chaining, Member Management, etc.
– Add, delete, modify, etc program options
• Who needs access to what series? Read only Series?
• Who needs access to what data sections?
– Who has override authority when two planners have
access to same data sections?
– Should multiple series be setup to transfer data from
planner to manager – for example, planner forecast is
one series, manager forecast is a series that starts
with planner forecast but manager adds/modifies the
planner forecast?

Cross functional collaboration scenario..
• For example, collaboration between demand planners,
sales, marketing, finance and operations
• All stakeholders should be able to see real time others’

edits but not be able to change others’ data
• Typical Implementation Solution:
– Create a set of series for each stakeholder for
baseline, override and final
– Create read only series using server expressions
based on the read-write columns
– Assign the read-only series to other stakeholders who
need to see but not change the data

Summary
• Flexible but powerful security mechanism.
• Review requirements thoroughly and design
security right from the get go.
• When something is missing, review security 
Questions:
srini.subramanian@inspirage.com

12-Inspirage Training - Demantra - Security v2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

12-Inspirage Training - Demantra - Security v2

Uploaded by

Copyright:

Available Formats

Demantra Data and

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

• Groups are a collection of users

• Workflows refer to Users and Groups to tie process

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

In an 11i/R12 integrated version, user is

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

• Series that the

Implementation Tip: Reduce clutter

The Oracle APS and Demantra Specialists

• Data filters that

• How can two business groups co-exist without

The Oracle APS and Demantra Specialists

Implementation Tip: Create a group for every

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

Implementation Tip: Remove edit and delete from

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

• All stakeholders should be able to see real time others’

The Oracle APS and Demantra Specialists

The Oracle APS and Demantra Specialists

You might also like