Demystifying Oracle Cloud ERP Financials

Post on 21-Aug-2015

81 views 9 download

Tags:

Transcript of Demystifying Oracle Cloud ERP Financials

Demystifying Cloud ERP Financials

2

ABOUT PERFICIENT

Perficient is a leading information technology and

management consulting firm serving clients

throughout North America.

We help clients implement digital experience, business optimization,

and industry solutions that cultivate and captivate customers, drive

efficiency and productivity, integrate business processes, improve

productivity, reduce costs, and create a more agile enterprise.

3

PERFICIENT PROFILEFounded in 1997

Public, NASDAQ: PRFT

2014 revenue $456.7 million

Major market locations:

Allentown, Atlanta, Ann Arbor, Boston, Charlotte, Chicago,

Cincinnati, Columbus, Dallas, Denver, Detroit, Fairfax, Houston,

Indianapolis, Lafayette, Milwaukee, Minneapolis, New York City,

Northern California, Oxford (UK), Southern California, St. Louis,

Toronto

Global delivery centers in China and India

>2,600 colleagues

Dedicated solution practices

~90% repeat business rate

Alliance partnerships with major technology vendors

Multiple vendor/industry technology and growth awards

4

SPEAKER

Samantha German 18 years of Oracle Applications experience EBS since 1997Focus on Cloud ERP

4

5

AGENDA• Cloud Application Myths

• Screen Shots

• EBS vs. Cloud

• Functional Setup Manager (FSM)

• Rapid Implementation

• Implementation Expectations

• What to Expect After Purchase

• Preparation

• Differentiators

• Questions

6

CLOUD APPLICATION MYTHS

7

Cloud Application Myths

1. What is Cloud ERP?

2. Is EBS going away?

3. Limited functionality

4. Is my data secure?

8

SCREEN SHOTS

9

10

11

12

13

14

15

16

17

18

19

20

21

FSM Terminology (Offering, Option & Features)

Financials (Offering)

Payables(Option)

Expenses(Option)

Fixed Assets(Option)

Receivables(Option)

Collections (Option)

Intercompany(Option)

Corporate Cards with Expenses(Feature)

Expense Receipt Image Processing

(Feature)

22

23

24

25

26

27

28

29

30

31

Payables Invoice

32

Receivables Invoice

33

Receivables Lines

34

Purchasing

35

Warehouse Operations

36

What to Look Forward to… R11

cloud.oracle.com

37

cloud.oracle.com

38

cloud.oracle.com

39

cloud.oracle.com

40

cloud.oracle.com

41

cloud.oracle.com

42

EBS vs. CLOUD

43

Components

EBS Components Cloud Components

Product-Specific Setup Centralized Setup Across All Products Using Functional Setup Manager

Responsibility Data Role (automatically generated when BUs and Ledgers are defined)

Legal Entity Configurator Legal Entity Configurator accessed from Functional Setup Manager

Business Group Term Change: Enterprise

Establishment Term Change: Legal Reporting Unit

HCM Legal Entities defined in the HR Organizations page

HCM and Financial Legal Entities can be shared and are defined in the same page

44

Components

EBS Components Cloud Components

Operating Unit Term Change: Business Unit

No Spreadsheet to upload LEs, BUs, COA Values, COA Hierarchies, Ledgers, Banks and Bank Accounts

Integrated Spreadsheets to upload all via Functional Setup Manager

Supports Rapid Implementation Timelines

45

General Ledger

EBS GL Cloud GL

Segment Value Security does NOT use conditions Segment Value Security uses conditions, such as Equal to, Not Equal to, Between, etc.

Relational Balances (balances stored in tables) Multi-dimensional balances (embedded Essbase cube)

Summary Templates required to stored summarized balances

Balances pre-aggregated and stored at every summarization level

No ability to assign parent values (hierarchies) to:• Cross-validation rules• COA Mapping

Can leverage trees (hierarchies) for:• Segment Value Security Rules• Cross-validation rules• COA Mapping • Revaluations

Note: Use a different hierarchy than reporting, analysis, and allocations

No condition filters on cross validation rules (enabled or not enabled)

Cross validation rules use both a condition filter and validation filter

46

Reference Data Set 2

Reference Data Set 1

Org 1

Reference Data Set 2

Org 2

Reference Data Set 3

Org 3 Org 1 Org 2 Org 3

Reference Data Set 1“Enterprise”

Reference Data Set 1

Org 1 Org 2 Org 3

Reference data set per org.

(same as EBS)Reference data set shared by all orgs.

Note: “Enterprise” shipped for seed data.

Selected sharing of reference data sets

across organizations

“Common” Reference Data

“Common” reference data set shared by all but retain

organization-specific data where appropriate

Reference Data Set 1

Org 1 Org 2 Org 3

Reference Data Set 2

Cloud Model: Implementation Options

47

FUNCTIONAL SETUP MANAGER

48

Guided Process for Implementation Lifecycle

49

FSM Links

50

FSM Screen Shots

51

• Specify Scope Value to set the context for subtasks

• Applies to:

– Legal Entities

– Business Units

– Accounting Configuration

– Tax Regimes

– Legislative Data Roles

Tasks with a Scope Value

52

53

FSM Screen Shots

54

Rapid Implementation

55

Example: Chart of Accounts, Calendar, and Ledger

56

Example: Business Unit

57

58

ACCOUNTS PAYABLE

59

60

Considerations

• Images can be routed based on captured attributes

o Supplier, PO #, Invoice #, date and amount

o Plus additional user defined attributes

• Invoices can be sent through fax or email

o Manual intervention involved when attachments contains

multiple invoices

• User defined attributes captured during imaging are not

stored in Payables data model

• Turn off supplier validation in OFR if supplier does not exist

• Use TIFF format and not JPEG due to lossy compression

• User configurable image routing rules

• ODC can be de-centralized while OFR can be centralized

• No need for supplier specific templates

• If there is an issue with any invoice image, OFR rejects the

entire invoice batch

Imaging

• Only standard invoices are supported on spreadsheet

invoice entry

• Only non-PO invoices entered through supplier portal

go through approval

• On BU setup, ensure that Sold-to and Requisition BU

are the same. Else the system creates intercompany

entries when inventory is used

Invoices

61

IMPLEMENTATION

EXPECTATIONS

62

Enterprise Structure Discovery

Standard Processes

Oracle Transactional Business Intelligence (OTBI)

Packaged Quick Starts

Master Data & Open Transaction Loads

Land and Expand

Mobile Expenses

Oracle Social Network

Implementation Expectations

63

64

WHAT TO EXPECT AFTER

PURCHASE

65

Email – Provision Instance

Oracle Implementation Success Manager – ISM

Production & Stage (TEST)

Production to Test Patching (P2T)

Patching 1st & 3rd Weekend

After Purchase

66

PREPARATION

67

Workshops Enterprise Structures

Chart of Accounts

Map/ Gap Assessment

Internal Reviews

Legacy Data/ Open Transactions

Data Clean Up

Webinars/ Training

Online

Oracle University

Preparation

68

DIFFERENTIATORS

69

Estimation Tool – direct tie to Implementation package.

Sales > Delivery > Support

Over 250 Best Practice Test Scripts templates

OTBI Rapid Reference Guide. Detail of 24 Subject areas consisting of over 7100 fields

Prototype instance as soon as 2 days from Enterprise Structure workshop

Map/Gap offering

SupportNet

Differentiators

70

QUESTIONS?

Please enter your question in the

chat box

71

FOLLOW US ONLINE

• Twitter.com/Perficient_ORCL

• Blogs.perficient.com/oracle

• Linkedin.com/company/Perficient

72

THANK YOU!