02 initial setup.pdf

1 Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Proprietary and Confidential - Distributed to Authorized Customers. Subject to Safe Harbor.

Initial Setup

ORACLE SALES CLOUD

IMPLEMENTATION PARTNER WORKSHOP

Oracle Sales Cloud

Oracle Product Development

2014


The following is intended to outline our general product direction. It is intended

for information purposes only, and may not be incorporated into any contract.

It is not a commitment to deliver any material, code, or

functionality, and should not be relied upon in making

purchasing decisions. The development, release, and timing of

any features or functionality described for Oracle’s products

remains at the sole discretion of Oracle.

Safe Harbor Statement


The information in this presentation is correct as of the presentation date.

However, Oracle Sales Cloud continues to evolve and software patches are

applied frequently; therefore this information is subject to

change. Check with your Oracle Representative for updates.

This content is not warranted to be error-free.

Content Subject to Change


Initial Setup Topics

How do I get Oracle Sales Cloud?

Once I have it, what do I do on day 1?

How do I setup users and security?

How can I get data from other systems into Sales

Cloud?


How do I get Oracle Sales

Cloud?


Provisioning Feedback

Partners and customers told us…

It takes too long to provision an environment.

We listened…

Recently, we have automated all of the processes which

means that provisioning takes less than a week.


Initial Data Setup Feedback


Setting up geography data in Sales Cloud requires either a

costly license from a 3rd party or days of manual and complex

data entry.

We listened…

In R8, we are including the geography data for 19 countries

which can be loaded with a single click in the application.

What else?

In R9, we will add another 34 countries.


Getting Oracle Sales Cloud

Production and Non-Production Environments

Communication from Oracle

Scheduled Maintenance: Patches and Upgrades

Topics

Get Oracle Sales Cloud

Initial SetupLearn

about Data Shapes

Extend the Application

Administer Key Areas

Tweak the Core SFA

Areas


Getting Oracle Sales Cloud – STEP 1

To get Sales Cloud, you

could either:

Sign up for a free 30

day trial, or

Contact your Oracle

Sales Representative to

order Sales Cloud


Getting Oracle Sales Cloud – STEP 2

The customer completes the questionnaire.


Sales Cloud Environment

Within 5 business days, Oracle provisions two environments:

1 Production Environment

1 Non-Production Environment

NOTE: Customers can use any client with no additional expense:

Desktop UI, Simplified UI, Sales Cloud Mobile, CRM for Microsoft Outlook

ProductionNon-Production

(Stage / Test )


Production Environment

Environment for Production-level activities

Sized for Production user loads

Monthly scheduled maintenance

Production


Non-Production Environment

Environment for training, configuration,

and testing activities

One Non-Production environment

included with contract

Environment to apply and test configurations and data

prior to migrating them to Production

Environment can be refreshed per request

Monthly scheduled maintenance Non-Production

(Stage / Test )


How do I know when Sales Cloud ready?

Once the environments are provisioned,

the customer will receive emails with:

A welcome message

Sales Cloud Credentials for the initial

administrator

Credentials for the Sales Cloud

administration portal

For additional environments, customers

can contact their Oracles sales rep.

For additional language support,

customers should file a service request.


Sales Cloud Administration Portal

Allows you to track usage and receive notifications for OSC


My Account

Provides a macro view of systems to which you have access

Provides Metrics on users, data and system uptime

Allows Account Administrators to have the Welcome Email

resent.


My Services

Provides a micro view of a single system

Provides Metrics on users, data and system uptime


Identity Self Service

Allows you to change user names and passwords for

cloud.oracle.com services.


Application Services Notifications

Access patch and upgrade notifications through cloud.oracle.com

Initially only the administrator will receive notifications. Additional

users to be notified can be set up here…


Notifications

Proactive Communication

Scheduled and unscheduled

maintenance

Patch bundle documentation

My Oracle Support: Master

Note Listing Functional

ReadMes for Fusion CRM

Patch Bundles (My Oracle

Support Doc ID #1540801.1)

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1540801.1


Scheduled Maintenance: Patches and Upgrades

Targeted to the statistically lightest

utilization

Once a month application patching

cycle

Non-Production environments

patched on first Friday of the month

Production environments patched on

third Friday of the month


Production to Test Refresh

A refresh of your test environment

from your production environment is

accomplished by requesting it via a

Service Request

Can request 4 times in a 12 month

period

All metadata is moved, however,

some territory management data

needs to be regenerated based upon

that metadata.


Once I have Sales Cloud,

what do I do on the first day?


Verify Provisioned Settings

Configure Initial Settings

Topics


Initial SetupLearn

about Data Shapes



Tweak the Core SFA

Areas


General Implementation Process

Setup Tasks for

Specific

Modules

Initial Setup

Tasks

Import DataCreate

Territories

Migrate Setup

Data

Migrate

Customizations

Extend and

Customize

Validate Setup

and

Customizations

Deploy Mobile

& Desktop

Clients


Quick Steps Guide

Use the Getting Started guide to continue setting up a simple

instance for users to become familiar with the application

http://docs.oracle.com/cloud/latest/trial_paid_subscriptions/CSGSG/index.html


Functional Setup Manager

Functional Setup Manager is used throughout this training. You get to

FSM via the Classic UI Navigator item called Setup and Maintenance.


Verify Provisioned Settings

Review and update, if necessary, the provisioned settings when you

first receive the application.

You do this by accessing setup tasks:

– Manage Enterprise HCM Information

– Manage Legal Address

– Manage Legislative Data Group

– Manage Legal Entity

– Manage Legal Entity HCM Information

– Manage Business Unit

– Manage Users (only one initial user provided)

– Manage Administrator Profile Values (Set default business unit)

For instructions, see the “Setup Process Overview” chapter of the

Getting Started with your Sales Cloud Implementation guide.

http://docs.oracle.com/cloud/latest/salescs_gs/FASMC/F1271541AN1083C.htm


Configuring Initial Settings

You must set up some enterprise-wide data, such as:

Accounting Calendar

Currencies

Geographies

Sales Catalog/Products

Customer Center

Sales Dashboard

For instructions, see the “Setup Process Overview” chapter of the Getting

Started with your Sales Cloud Implementation guide.

http://docs.oracle.com/cloud/latest/salescs_gs/FASMC/F1271541AN1083C.htm


Accounting Calendar

You must set up the accounting calendar

The calendar breaks down your fiscal year into accounting periods

It is used across your enterprise for territory management and

forecasting

You want to set it up correctly because it cannot be changed once you

have entered data


Accounting Calendar: Start Date

Specify the first date of the period of the oldest historical data on

which you will be reporting

Example: If you select January 1, 2010 as your first calendar date, then

you would only be able to enter or import historical data associated with

this date or more current

You cannot add previous years once the first calendar period has

been opened


Accounting Calendar: Start Date

Use one of these methods to determine your Start Date:

Set the Start Date to one year before the date that your organization was

created.

Base it on your opportunities:

1. Find the earliest date of your open opportunities (or closed, if you want to capture

closed opportunity history)

2. Then determine the beginning of your fiscal calendar for

that year

3. Add one or two years before that to use as your start date


Accounting Calendar: Period Frequency

The system generates periods based on your selection

Options: 4-4-5, 4-5-4, 5-4-4, 4 Week, Weekly, Monthly, Quarterly,

Yearly, or Other to set up a custom calendar.

Set this to the lowest period you care about for forecasting, but no

lower. This determines:

The level of granularity available within analytics

The level at which users view and adjust forecasting aggregates by

the time dimension

Calendar

breaks down

periods

within a

year.


Accounting Calendar: Setup Tasks

Go to the “Manage Account

Calendar” to set up your

accounting calendar

Go to the “Manage Calendar

Profile Option” to specify the

Accounting Calendar for your

organization

Specifies which

accounting calendar to

use


Currencies

All currencies are enabled by default

Disable the currencies that your company will not use

You cannot change a currency code after you enable the currency,

even if you later disable that currency

You can enter start and end dates to set a date range for the

currency to be available to users

If you leave Start Date

blank, the currency is

valid immediately.

If you leave End Date

blank, the currency is

valid indefinitely.


Currencies: Default

Specify the default currency for your enterprise


Currencies: Exchange Rates

Set up conversion (exchange) rates for your enabled

currencies.

You can set up daily rates as well as historical rates.

If you do not set up conversion rates for enabled currencies,

then you might have issues when:

• Converting leads to opportunities, if the records are using

different currencies

• Reporting on Opportunities which have multiple currencies


Currencies: Setup Tasks

Go to “Manage Currencies” to disable the currencies that

you will not be using

Go to “Manage Currency Profile Options” to specify the

default corporate currency

Go to “Manage Conversion Rate Types” to set up exchange

rates


Geographies

Geographies are reference data used to:

Validate addresses

Specify the geography component of a territory

Country names and their codes are seeded data.


Geographies: Country by Country

For each country, you must:

Define the structure

Define the specific values to match the structure (hierarchy)

Specify validation

USA

New York

New

York

California

Los

Angeles

Albany San

Francisco

Country

State

City


Geography Data Load

There are 3 ways to enter Geography Structure and Data:

1. Use Native Sales Cloud data

2. Use structure and data that you already own (or get from a 3rd

party)

3. Manually enter the data


Geography Data Load: Native Data

For R8, structure and data for the following countries is

provided as part of the base Sales Cloud License. Another 34

countries will be released with R9.

Countries Supported

United States

Austria

Hungary

Russia

Canada

BelgiumIceland

Romania

Denmark

Mexico

Switzerland

Finland

Turkey

France

Norway

Germany

Poland

Greece

Portugal


Geography Data Load: Native Data

Steps:

1. Manage Geographies

2. Select the Country for which you want to import data

3. Actions Import Nokia Data

4. Process runs in the background


Geography Data Load: Import

Geographies can be imported using the file import functionality

Data must be licensed from a 3rd party or already owned by the

customer

For details about importing geographies, see the Importing Master

Reference Geography Data implementation note (My Oracle Support

Doc ID #1481758.1).



Geography Data Load: Manual Setup

Define all the geography types for each country that will be

used in your geography.

For example for United States:

– States have counties, which have cities, which have postal codes



Define the specific hierarchy values to match the structure

As you enter the values, you are setting up the hierarchy for that

country’s geography

– Example: New York (state), Albany (county), Albany (city),

12262 (postal code)



Define the level of validation.



Specify if a list of values is available to users

The list of values is generated from the geography data you

have entered



Specify if addresses that do not pass validation can be saved

TIP: Always set this to “Error” to prevent bad data from being

saved

Set to “Error” so data cannot be

saved if validation fails


Geography: Alternate Geo Names

You can store alternate names for geographies.

Some geo data that you purchase might contain references in a

localized context.

– Example: Copenhagen (primary name), København (alternate name)

– This is not part of the translation functionality.

The system searches against both the primary and the alternate

names.

TIP: Most global organizations use the name in English as the

primary name.


Geography: Alternate Geo Names Considerations

Alternate names appear in the UI along with the primary names in

these areas:

Admins will see both names in the Detail pages for adding geographies.

End users will see both names in the list of values when entering

addresses (if you enable the LOVs).

– This can cause some confusion and clutter, so decide if you want to include

alternate names.

– Avoid alternate names if you want to force name consistency across your

organization.


Geographies: Setup Tasks

Go to “Manage Geographies” to define the structure,

manually enter the values for the hierarchy, and specify the

address validation

Go to “Manage Address Formats” to specify the format of

an address for a geography

Go to “Manage File Import Activities” to start importing your

geo data


Tips for Success: Geographies

Include all the geography types (state, county, city, etc.) that

you may need in your geography structures, even if you do not

expect to upload data for all of those geography types

immediately

If you must modify geography structures after your geography data

is initially loaded, you will need to delete the data first


Tips for Success: Geographies

Specify Geography Validation at the appropriate level (level that you

want to validate)

Ensures that records will be properly assigned based on your territory

definition

Prevents users from entering incomplete addresses

– Example: With the North America address style format, the address must have

the correct country, state, and postal code combination based on the geography

hierarchy data to be considered geographically valid.


Tips for Success: Geographies - Validations

Set the “Geography Validation Control for Country” to “Error”

This prevents users from saving an address that does not pass

validation during address entry


Tips for Success: Geographies - LOVs

Select the Enable List of Values option, if you are sure that the data

is complete.

This renders the values as a list of values (LOV) in the user interface.

Select this at the appropriate level, such as State or Region.


Tips for Success: Geographies - LOVs

Consider the pros and cons of enabling LOVs

LOVs at levels such as City or Zip Code can produce a long list

of values that might be cumbersome for end users

Using LOVs can prevent users from saving the address, if the

address does not appear in the LOV


Sales Catalog and Products

Three primary objects are related to Products:

Product Items

Product Groups

Sales Catalog


Product Groups and Items

Product Groups/Items can be:

Used in your territory definition

Associated with leads

Product Groups/Items must be associated with opportunities.

Each associated product group/item creates a separate revenue

item, which drives territory-based assignment and forecasts.


Products: Terminology

Be aware of terminology inconsistency, depending on context

Different areas of the UI use the word “Products” to refer to

“Product Items” and/or “Product Groups”

Sometimes the terms “Products” and “Items” are used

interchangeably

This simplifies the UI for end users wherever the distinctions are

not relevant to themRevenue Items have

“Product” column to capture

both “Group” and “Item.”

Admin column displays

“Products” for only product items.



A sales catalog organizes product

groups/items into a meaningful, nested

hierarchy

Product Groups are any collection of

sales products that you define when

setting up your sales catalog

Product Groups can be defined in a

hierarchy

Product Groups can be children of

another Product Group

Product Items can be children of a

Product Group


Sales Catalog: Product Group and Item Hierarchy

Product

Groups

Product

Items



Do not try to import product groups/items; instead, set them up

manually

For your sales catalog, create the top-level product group and then

build any number of subgroups in a hierarchy

NOTE: Sales catalogs are not available to end users in the Simplified

UI, only in the Desktop UI.


Product Group vs. Product Item

Product Groups are generally sufficient for all the tasks that your

company will want to perform

Adding product items is only beneficial when capturing orders and pricing

– “Items” are those exact products that are sold to customers; product groups

are granular enough for estimating revenue

Setting up groups requires less configuration than items

– For items, you must set up prerequisite data, such as item organization, item

classes, unit-of-measure classes, etc., as well as create items in a separate

module of Oracle Sales Cloud


Tips for Success: Sales Catalog/Products

Include product items only if your business

requires it:

You might base territories on product items

to ensure assigning opportunities to the

correct salesperson.

Your organization might want to include

items because you have only a few, stable

products, so frequent updates would not be

necessary



Generally, you do not want product groups or items to appear

in multiple branches

To prevent this, make sure the “Allow Duplicate Children” option

is not selected when setting up product groups

This is critical to follow if you base forecasting on products

Consult with Oracle Support before deviating from a strict

product hierarchy

Do not select

check box.



Be aware that changes to your product list are done in real-time.

No versioning exists for products

If your territory includes the Product dimension,

you need to activate a new territory

proposal to capture changes

in your product list

Don’t forget to publish your catalog

and add it to your base catalog!

This is a separate step in the

“Manage Product Groups” task

The “Getting Started with Oracle Sales Cloud”

guide contains complete instructions for setting

up and publishing your sales catalog.

http://docs.oracle.com/cloud/latest/salescs_gs/FASMC/index.html


Customer Center

You can configure the customer tree

You might want to hide nodes that are not relevant to your end users.

– Reminder: Revisit these settings after you add custom objects or make other

changes to objects and attributes

You can set the node that you want users to land on when they drill into

the tree

The “Getting Started with Oracle Sales Cloud” guide contains instructions for

performing this task.

http://docs.oracle.com/cloud/latest/salescs_gs/FASMC/index.html


Customer Center: Additional Settings

You might want to make additional changes after you get started.

You can set up 3rd party integration so that the data appears in the tree

node.

– To leverage the built-in integration with OneSource, buy the service and turn

it on; integration is off by default.


Sales Dashboard

Configure the Sales Dashboard layout

The dashboard can display Sales Analytics content, 3rd party content

(URLs, external widgets), or content such as your Calendar, Tasks, and

Key Contacts

Go to Navigator > Sales Dashboard. Then click Administration >

Customize Home Pages

– For further instructions, see the Setting Up the Sales Dashboard

implementation note (My Oracle Support #1483093.1)



Additional Tasks

You might want to set up other areas, such as:

Sales Methods

Sales Campaigns

Again, review these documents to see more tasks and

instructions for setting up initial configurations:

Getting Started with Oracle Sales Cloud Service


Guides

Sales Cloud Upgrade Guide

Introduction Video Series – Doc ID 1482685.1

Implementation Notes - Doc ID 1482696.1


Practices: Initial Setup Tasks

Practice 02A covers the following topics:

Review/Update some initial data set up by Oracle

– Manage Enterprise HCM Information

– Define Default Proposal Owner

Enable validation for Australian geography

Set up geography structure, hierarchy, and validation for New

Zealand geography

Practice 02B covers the following topics:

Schedule a process to synchronize the database search indexes

for the objects in your Oracle Sales Cloud practice environment


How do I set up users and

security?


Topics

RBAC

Components of RBAC

Technical Implementation of RBAC Components

Data Sharing Modes

Customization Tips and Upgrade Considerations


RBAC

Industry standard security mechanism

Uses role centric approach to grant access to the users

Provides modular security configuration through privileges

and role hierarchies


Components of RBAC

User

Job / Abstract Role

Duty Role

Privileges


Components of RBAC: Privileges

Basic building block of the security model

Controls the access to the system resources

Privileges are wired to the code

Privilege types – Function, Data

Function security - what actions can be performed on which

user interface pages

Examples: Create Opportunity, Delete Opportunity, View

Opportunity

User Job / Abstract Role Duty Role Privileges


Components of RBAC: Privileges

Data security - what action can be taken against which data.

Example:

Role Aux

Verb

Verb Business

Object

Attribute Condition Privilege

Opportunity

Administration

Duty

Can Manage Opportunity Opportunity

Team

For all opportunities in the

business units that they are

authorized within

Manage

Opportunity

Team Data



Components of RBAC: Duty Role

Grouping of various tasks a user can perform as part

of a specific duty

One or more privileges are mapped to the duty role (Role –

Privilege Mapping)

One or more duty roles can be mapped to a duty role (Role

Hierarchy)

Examples: Opportunity Administration Duty, Lead

Registration Management Duty, Marketing Analysis Duty



Components of RBAC: Job / Abstract Role

Grouping of various duties an employee performs in a

job

An abstract role is a type of enterprise role that is not

specific to a particular job.

One or more duty roles are mapped to each job / abstract

role (Role Hierarchy)

Examples: Sales Representative, Contract Administrator,

Employee (abstract), Manager (abstract)



Components of RBAC: User


Can be a human being, machine, network or intelligent

autonomous agent needing access to the system

One or more job / abstract roles are mapped to each user

Role provisioning rules can be used to automatically map

job roles to users based on pre-determined criteria


Lisa Jones

Sales Representative

Components of RBAC: Summary with Example

EmployeeJob Role Abstract Role

Sales Representative DutyRelated Duty Roles

User

Duty Role(s)Duty Role(s)

Create Opportunity

Delete Opportunity

View Opportunity

View Opportunity Notes

Privileges

Related PrivilegesPrivileges

Opportunity Sales Representative Duty


Lisa Jones

Sales Representative

Components of RBAC: Summary with Example

EmployeeJob Role Abstract Role

Sales Representative DutyRelated Duty Roles

User

Duty Role(s)Duty Role(s)

Create Opportunity

Delete Opportunity

View Opportunity

View Opportunity Notes

Privileges

Related PrivilegesPrivileges

Opportunity Sales Representative Duty

Role

Hierarchy

Role - Privilege

Mapping


Components of RBAC

User

Job / Abstract Role

Duty Role

Privileges


Technical Implementation of RBAC Components

Functional Technical Tool

Job Role Enterprise / External Role OIM

Duty Role Application Role APM

Role Hierarchy Application Role Hierarchy APM

Privilege Entitlement or Permission APM

Role – Privilege

Mapping

Functional Security Policy

Data Security Policy

APM


External Role - OIM

User

Job / Abstract Role

Duty Role

Privilege


External Role - APM

User

Job / Abstract Role

Duty Role

Privilege


Application Role - APM

User

Job / Abstract Role

Duty Role

Privilege


Function Security Policy - APM

User

Job / Abstract Role

Duty Role

Privilege


Function Security Privileges - APM

User

Job / Abstract Role

Duty Role

Privilege


Data Security Policy - APM

User

Job / Abstract Role

Duty Role

Privilege


Manage Users

User

Job / Abstract Role

Duty Role

Privilege


Manage Users – Resource Role, Provisioning

User

Job / Abstract Role

Duty Role

Privilege


Role Provisioning


Data Sharing Modes

RBAC

Team

Resource Hierarchy

TerritoryPartners

View All


Team Member Role (Team Function) Access

David Murphy Primary Sales Rep Full

Caren Carson Overlay Representative Edit

Tim Horton Product Specialist Edit

Opportunity

Users who are explicitly on the team can see the Opportunity record.

John Doe is manager of Caren Carson.

John Doe can see the Opportunity record.

These users can also see Interaction records of the opportunity.

John Doe

Manager of

Opportunity Team

Sharing Mode: Opportunity Team

Interactions

10

0

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Proprietary and Confidential - Distributed to Authorized Customers. Subject to Safe Harbor.

Team Member Role (Team Function) Access

Steve Parker Primary Sales Rep Full

Amanda Sykes Overlay Representative Edit

Ram Arjun Product Specialist Edit

Opportunity

Users who are explicitly on the Account team can see the read-only Opportunity

record and Interactions records.

Tom Hopkins is manager of Amanda Sykes.

Tom Hopkins can see the read-only Opportunity record and Interactions record.

Account Team

Tom

Hopkins

Manager of

Sharing Mode: Account Team

Interactions

10

1


Opportunity is associated with an Account. The Account is associated with the

CA territory.

John Doe and Matt Lopez can see the read-only Opportunity record.

John Doe and Matt Lopez can see the Interaction child record.

Mark Twain cannot see the Opportunity record nor the Interaction record.

Opportunity

West

CA

East

USA John Doe

Matt Lopez

Mark Twain

Account

Interactions

Sharing Mode: Account Territory

10

2


RBAC Data Security Rules for Sharing ModesWhere they are an opportunity sales team member with

view, edit, or full access

Where they are in the management chain of an

opportunity sales team member with view, edit, or full

access

Where they are a member of the opportunity sales

account team

Where they are in the management chain of an

opportunity sales account team member

Where they are a territory resource in the opportunity

territory team or a territory resource with a descendant

territory in the opportunity territory team

Where they are a territory resource in the opportunity

sales account territory team or a territory resource with a

descendant territory in the opportunity sales account

territory team

Where they are a member of the account team of a

partner organization on the opportunity

Where they are a member of a partner resource

organization whose partner organization is on the

opportunity

RBAC

Team

Resource Hierarchy

TerritoryPartners

View All

10

3


Customizing Access Control: Tips for Success

This guidance assumes that after due diligence, you have concluded that the reference roles

provided do not meet your security needs.

10

4


Customizing Access Control: Scenarios

Scenario 1

Increasing the scope of what a user can do

Adding a new duty role

Scenario 2

Reducing the scope of what a user can do

Removing a duty role

Removing a privilege

Scenario 3

Custom Duty Role

10

5


Leverage the default security settings whenever possible.

Use this best practice if you must make changes to the defaults:

Define the requirement clearly and determine the gaps.

Analyze the effect of changes that need to be made.

Record all changes in writing using ‘before’ and ‘after’ tags.

Discuss those changes with Oracle Support.

Understand how territory contributes to visibility and set up

territories with that in mind.

Customizing Access Control: Tips for Success

10

6


Changes to the reference implementation provided by Oracle Sales Cloud creates conflicts.

Conflicts are detected by the Oracle Sales Cloud operations team and reported to the customer

Upgrade Considerations

MODIFICATION CONFLICTS

Artifact type: Application Role

Artifact Name: MOO_SALES_REPRESENTATIVE_DUTY

Description: This artifact is modified at attribute level in patch version and also in production.

Customer must accept or reject changes that caused the conflicts

Rejection of changes overwrites the customization

Acceptance of changes keeps the customization

10

7


Other Resources

Fusion OER has a list of Roles and details about those roles per

application per version.

https://fusionappsoer.oracle.com/ - Select Role and Sales

Security Concepts and Examples in the Getting Started with

Oracle Sales Cloud guide

http://docs.oracle.com/cloud/131/user_services/FASMC/F1012266A

N10741.htm#FASMC1012266

https://fusionappsoer.oracle.com/

http://docs.oracle.com/cloud/131/user_services/FASMC/F1012266AN10741.htm

10

8


Practices: Users and Security

Practice 02C Covers User Setup

Review the provisioning rule for all employees

Set up provisioning rules for sales reps

Add a sales rep

Review the resource organization for the new sales rep

Practice 02D Covers the Review of Roles

Explore enterprise roles

Explore the Sales Representative Duty role

Explore security policies for the Sales Representative Duty role

Creating a Resource Role

10

9


Practice: Users and Security

Practice 02E consists of a take-home exercise that builds on

the previous practice exercise

Create a custom job role

Create a custom duty role and associate it with the new job role

Create a custom resource role

Create a provisioning rule that uses the custom resource role and

new job role

Update an existing user by applying auto provisioning

Verify the user’s access customization meets the business

requirements

11

0


How do I learn the data

shapes involved with Sales

Cloud?

How can I get data from

other systems into Sales

Cloud?

11

1


Mappings Feedback


Mapping standard objects is painful and slow.

We listened…

In R8, there are multiple seeded mappings for each of the

core SFA objects and their children so there is no need to

start from scratch.

11

2


Mappings Feedback


You don’t have nearly enough example templates for

import and getting to them requires downloading them from

an external system.

We listened…

R8 allows you to generate templates based upon seeded,

generated and custom mappings. There is no need to

manually create a template ever again.

11

3


Mappings Feedback


Understanding why an import is unsuccessful required trial

and error.

We listened…

In R8, we have greatly improved the logging and error

handling such that the administrator can understand what

happened at each record.

11

4


File Import Introduction

General Process

Perform Data Comparisons

Customize Oracle Sales Cloud

Prepare Source Data

Import Data

Validate Data

Topics


Initial SetupLearn

about Data Shapes



Tweak the Core SFA

Areas

11

5


File Import

Populates relevant

interface tables and

then loads the data

into tables

Is the only UI-based

bulk import option

for Cloud

deployments

Allows you to import records from external files into the

application

11

6


File Import Features

File import supports multiple file formats

Standard text files with delimiters such as:

– Commas

– Semi-colon

XML files

A file import job can be:

Run immediately

Scheduled to run once at a later time

Scheduled to run at a regular interval

11

7


Tips for Success: Planning Your Import Tasks

Keep a clear scope and plan your overall approach

Which objects, attributes, relationships you will import

Sequence and timeline dependencies – imports may be phased

Start EARLY and be as COMPLETE as possible

Build enough time into your project plan to import historical data

Plan a top-down import sequence

Parents before children

11

8


Tips for Success: Planning Your Import Tasks

Start with simple import cases and build incrementally

1. A single or a few rows with required fields only

2. Expanded for all standard fields to be used in migration

3. Custom fields, if you are using them

4. Object relationships

5. Volume

11

9


Import Resources to Help You

File-Based Data Import Templates available on My Oracle

Support (Doc ID 1503223.1)

Oracle Fusion Applications File-Based Import Guide

Oracle Enterprise Repository (OER)

Top level object information

Detailed Spreadsheets based upon interface tables that are

applicable to Cloud and On Premise – Use type ‘File-Based Data

Import’

Interface tables – available now (only applicable for on-premise

implementations)

Help topics


12

0


Oracle Enterprise Repository (OER)https://fusionappsoer.oracle.com/oer/

Oracle Apps

Unlimited

Oracle

Fusion

Applications

• CRM

• HR

• Financials

• Supply Chain

• Projects

Oracle

Enterprise

Repository

Catalog of Integration Assets:

Import Info by object

Web Services

Service Data Objects

SOA Composites

Interface Tables

Events

And more…

Custom

Applications

• Legacy

• Third Party

• ISV

• SaaS

Oracle Fusion Middleware

https://fusionappsoer.oracle.com/oer/

12

1


General ProcessPerform Data

Comparison

Customize Oracle

Sales Cloud

Prepare Source

Data

Import Data

Validate Data

• Compare the fields from source data with the

available fields in Oracle Sales Cloud

• Add custom fields, custom objects, choice list

values to Oracle Sales Cloud

• Cleanse the source data

• Remove duplicate and orphan records

• Save data in TEXT or XML format

• Use file-based import tool to import data

• Observe correct order of object imports

• Verify the imported data

• Fix import errors and re-import if needed

12

2


Import Objects

Represent the structure of the interface tables into which data

from a source file can be imported Consist of a set of related objects and their attributes that can be populated

together

Example: Customer import object includes: OrganizationProfile

SalesAccountProfile

SellToAddress

PrimaryPhone

Fax

URL

And so forth

Perform Data

Comparison

12

3


Generate Import and Export Artifacts

1. Create custom fields and objects

in Application Composer

2. Generate the artifacts needed for

import manually before

performing a file-based import

In Application Composer,

select the application for

which you want to generate

the artifacts

Generate the artifacts

In Oracle Application Composer, click Import and

Export and then click the Generate button to generate

import and export artifacts for an application.

Customize Oracle

Sales Cloud

12

4


Custom Object Containers in File

Import Tool

Three custom object containers are

available in the import Object list:

Marketing Custom Object

Opportunity Custom Object

Sales Account Custom Object

Available in Import Object list if:

There is a custom object in that

container

You run the Generate Artifacts task

flow for that container

Customize Oracle

Sales Cloud

12

5


Custom Object Containers in File

Import Tool

After selecting a custom object container

from the import Object list:

Map a custom object from within that

container

Map the custom attributes available in

each custom object

Customize Oracle

Sales Cloud

12

6


Custom Lookup Values

Review lookup values:

Geography

Opportunity Win/Loss Reasons

Contact Buying Role

And so on

Adopt standard lookups or modify

lookups to meet your business

You will use the Lookup Codes in your

source import file

Customize Oracle

Sales Cloud

12

7


Tips for Success – Preparing Source Data

Clean the data

Eliminate unnecessary records

Do you need that much history?

Prepare a file for each object

Include unique identifiers

Check that your data matches

the application lookup code

values

12

8


Tips for Success – Unique Identifiers

Decide how you will handle keys and relationships

Populate as many Source System and External Key

pairs as possible

These keys are critical to supporting subsequent updates

to your data for many objects

Ensure uniqueness

Create intelligent keys

Include object reference, for example ORG, LOC, SITE,

REVLINE

Dates

Sequential Numbers

BILLSITEUSE-03112013102





12

9


Record Unique Identifiers

Manually added records:

System generates the record identifiers

Export records to find these keys

Imported records:

You define the record identifiers

Keep track of your unique identifiers for

reuse

Prepare Source

Data

13

0


Source System References

For Oracle Sales Cloud:

We recommend that you include unique identifiers for all records

imported using file-based import

For some records (trading community objects), the unique identifiers

are compound keys consisting of:

– An identifier of the source system

– A unique identifier for the record in the source system

Source system reference

in source data file

Prepare Source

Data

13

1


Managing Source System References

Use the Manage Trading Community Source Systems task to:

Create a record for a new source system

Review seeded values

Prepare Source

Data

For Trading Community Objects

13

2


Mappings for File-Based Import

File-based import requires a mapping that associates each

column or element in the source file with a target object and

target attribute.

Example mapping for importing a

customer with an address.

Prepare Source

Data

Mappings are

created:

Manually

Automatically

Seeded

13

3


Automatically Created Mappings

Mappings that are created during job submission are saved and:

Are named using the job name plus the submission time.

Can be referenced in subsequent jobs.

Specify the saved mapping on the Set Up page.

Select the saved mapping

Import Mappings

13

4


Seeded Mappings

Seeded Pre-Defined

Mappings allow for…

A starting point for new

Sales Cloud users to ‘get

their feet wet’ before

creating their own

mappings

Less manual effort in that

some percentage of the

mapping is done for you

13

5


Generated Templates

CSV Templates can be generated for you based upon your

saved (seeded, automatically generated or manually

created) mapping files

JUST ADD DATA!

13

6


Source File

Use the approach seen in the templates of having

TargetObject_TargetAttribute as the Header Row in the input files

– makes mapping much easier.

ContactPersonProfile_PartyOrigSystem ContactPersonProfile_PartyOrigSystemReference ContactPersonProfile_PersonFirstName ContactPersonProfile_PersonLastName

CSV Contact-OSR0000006 Tom Cat

CSV Contact-OSR0000007 Jerry Mouse

CSV Contact-OSR0000008 Kevin Turvey

CSV Contact-OSR0000009 Martin John

CSV Contact-OSR0000010 Harry Carry

Prepare Source

Data

13

7


Tips for Success – 1:M Relationships

Handling 1:M relationships within an Object

Such as multiple Contacts for an existing Organization

Expectation might be to repeat the key header data for the Organization

on each relevant row

However this will cause errors, so you need to eliminate any repetition of

the key header data for the Organization

OrganizationProfile_PartyOrigSystem OrganizationProfile_PartyOrigSystemReference ContactPersonProfile_PartyOrigSystem ContactPersonProfile_PartyOrigSystemReference ContactPersonProfile_PersonFirstName

CSV OrgKey-0000003 CSV Contact-OSR0000006 Tom

CSV OrgKey-0000003 CSV Contact-OSR0000007 Jerry

CSV OrgKey-0000004 CSV Contact-OSR0000008 Kevin

CSV OrgKey-0000004 CSV Contact-OSR0000009 Martin

CSV OrgKey-0000004 CSV Contact-OSR0000010 Harry

OrganizationProfile_PartyOrigSystem OrganizationProfile_PartyOrigSystemReference ContactPersonProfile_PartyOrigSystem ContactPersonProfile_PartyOrigSystemReference ContactPersonProfile_PersonFirstName

CSV OrgKey-0000003 CSV Contact-OSR0000006 Tom

CSV Contact-OSR0000007 Jerry

CSV OrgKey-0000004 CSV Contact-OSR0000008 Kevin

CSV Contact-OSR0000009 Martin

CSV Contact-OSR0000010 Harry

13

8


Tips for Success – Preparing Source Data

Start with a template

Generate templates from seeded or customer created mappings

Oracle Sales Cloud File-Based Data Import Templates are

available on My Oracle Support (Doc ID 1503223.1)

Be very familiar with the Oracle Sales Cloud application

Information Library:

http://docs.oracle.com/cd/E37187_01/homepage.htm


http://docs.oracle.com/cd/E37187_01/homepage.htm

13

9


Tips for Success – Record Delete

Use the DELETE value in the ActionCode attribute to delete:

Parties (e.g. Sales Accounts)

Relationships (e.g. Account Contacts)

Contact Points (e.g. phone, email, URL)

Appointments

Opportunities

Interactions

Tasks

Notes

Must include the unique identifiers for records in your source file

14

0


Tips for Success – Deleting Parties

Only parties with these usage types can be deleted

Sales Account

Customer Contact

Organization Contact

Sales Contact

Group Member

Group Contact

Related Person

Party with any unconditional party usage e.g. Contact, Sales Prospect,

External Legal Entity, and Party of Interest. Unconditional party usages are

not a fixed list, some are seeded out of box, and some are created by

customer.

The party being deleted can NOT be a root node of a hierarchy.

14

1


Tips for Success – Null Value Indicator

Use #NULL to erase a value in a record

14

2


Tips for Success – File Management

TEXT/CSV or XML?

Recommend using CSV unless XML is only option

Keep your files organized

Self document as much as possible

Keep every file used during file import – in sequence

– File used during the imports are not currently accessible from Oracle Sales

Cloud

– Try to avoid updating an earlier file and re-running it with new data and/or

mapping

14

3


Running a File-Based Import Job

1. Create the import job

2. Select or Create the mapping

3. Submit the import job

4. Check the status

5. Verify the import

You will see the detailed steps for these tasks in

your practice labs.

Import Data

14

4


NEW: Debugging

Error Handling No Cascading Error Messages makes for easier determination of the core issue

Uses input file column names in error messages

Shows standardized error messages for common scenarios

Logging

Provide additional details in import logging output

Ability to refresh process log without reloading page

Improve user ability to identify point of failure via enable export and filtering of

log information

14

5


Practice Tip: Working with CSV files in Microsoft

Excel Microsoft Excel may change the formatting of cells so that numbers and

dates are corrupted

To avoid this, do not resave the CSV file without correcting the format of

number-only or date cells. Either:

Change format of cells containing number only values to Number format,

and remove the decimal places (.00) before saving to CSV file format, or

Save the CSV file as an Excel Workbook file first, make the changes, then

resave as a CSV file

14

6


Templates and Import Guide

Oracle Sales Cloud File-Based Data Import

Templates (Doc ID 1503223.1)

Oracle Sales Cloud File-Based Data Import

Guide (Doc ID 1564536.1)



14

7


Practice: Importing Customer Data

Practice 02F covers using file-based import to import customer records

Importing Sales Account records

Enriching the data by importing additional Address records for the Sales

Account records

Importing contact records for the Sales Account records

Practice 02G covers

Exporting data to locate Employee Resource IDs

Importing Opportunity Records and Revenue Items

Practice Files @ BeehiveOnline -> Practice Files -> File Import

Oracle Fusion CRM File Based Data Import Guide (pdf)

14

8


Practice: Webservices Practice 02H covers webservices for standard OSC Objects:

Review Oracle Enterprise Repository

Review ‘How-to’ find web service and the corresponding WSDL for

different OSC objects

Review SOAP UI usage in calling web services

Review request and response payloads for different methods on the

opportunity object

Practice 02I (take home) covers OSC Custom object web services Review Custom objects and Custom attribute naming conventions

Review ‘How-to’ find web service and the corresponding WSDL for

different OSC Custom objects

Review creation of a Custom object and adding it to a standard object

using relationships

Review request and response payloads for different methods on the

Custom object using SOAPUI

14

9


02 initial setup.pdf

Documents