How to design functional architecture.ppt

<Insert Picture Here>
Functional Architecture – Business Intelligence
Briefing - Architecture Fly By
Feb 2010

2
© 2008 Oracle Corporation – Proprietary and Confidential
Fly By

3
Architecture Fly By
• The Functional Architecture Website
• Anatomy of Fusion Applications
• The Case Topics
• Reference Data Sharing (a.k.a. Set ID)
• Enterprise Structure
• Chart of Accounts
• Date Effectivity
• Navigation
• Services
• Security

4

5
Architecture Fly By
• The Case Topics
• Navigation
• Services
• Security

6
J2EE Application
Instance 1
HCM
Instance 2
FSCM
Instance 3
CRM
Logical Business Area
Entity
Objects
View
Objects
SES
View
Objects
View
Objects
RPD
Table
Application
Module
Table
Table Table
Table
Table Table
Table
Table
J2EE Application
Logical Business Area
Entity
Objects
View
Objects
SES
View
Objects
View
Objects
RPD
Application
Module
Product
Product Family
Pillar
Replication
Replication

7
Product to Application Overview

8
Product Homepage

9
Pillar Homepage

10
Architecture Fly By
• The Case Topics
• Navigation
• Services
• Security

11
EBS Perspective: From R12 EBS….
Reference Data
Transactions
OU Partitioned Tables
Operating Unit
• Operating Unit splits into two concepts. From…

12
EBS Perspective: …To Fusion
Reference
Data Set
Business Unit
(was: Operating Unit)
Business Unit (previously Operating Unit) Partitioned Tables
Reference Data Set Partitioned Tables
Reference Data
Transactions
• To this:
• Business Unit (previously Operating Unit) partition Transaction Data
• New “Reference Data Set” partition Reference Data

13
Developer Experience

14
Customer Experience

15
Resources
• SetID Functional Architecture Case portal page
• Business Unit / Set ID Functional Uptake Document
• Working Group email list: apps-wg-setid_ww@oracle.com

16
Architecture Fly By
• The Case Topics
• Navigation
• Services
• Security

17
The Enterprise Structure Umbrella
• Enterprise
• Business Unit
• Shared Service Centers
• Legal Entity and Legal Employer
• Cost Center and Department

18
Business Unit

19
Service Providers

20
Resources
• Business Unit Functional Architecture Case portal page
• See Deliverables section for FUD, Wireframe, TOI and FDD
• Working Group email list: apps-wg-bu_ww@oracle.com

21
• Enterprise
• Business Unit
• Cost Center Administration
• Reorganizations

22
Legal Entity
Objectives
• Provide a single user experience for definition of legal
entities without changing the underlying data model.
• Unify terminology across HCM and Financials

23
Legal Entity
Solution in Fusion v1
• Legal Entity (LE) Definition
• All legal entities will be defined in Legal Entity Configurator (XLE)
UI
• XLE data model available on all pillars
• Use pattern 1 for propagation
• Data can be entered in any pillar, but must be propagated to
master before propagating to the rest of the pillars
• No impact to teams using the XLE model in R12
• The UI and services will change to accommodate the
additional HCM attribution

24
Resources
Information
• Solution Provider Website
• Functional design is the responsibility of the solution provider
• The Legal Entity Configurator team (XLE) is the solution provider
• The Legal Entity Functional Architecture Case Website
• The Functional Solution Approach
• Legal Entity mail list: apps-legal-entity_ww@oracle.com

25
What is Legal Entity Time Zone ?
• What is it NOT :
• User Preferred Time Zone
• Location Based Time
• What it is :
• Scope : Automatically adjusts any transaction with legal reporting
implications to the relevant period and reporting date based on
legal entity time zone conversion and display consistent
information on all interactive UIs, reports and Business
Intelligence KPIs
• Any legal period : Accounting (majority), but ALSO Costing (PAC),
Intrastat (EU), Tax , …
• Reporting date : GL Date, Accounting Date, …

26
Example
• International customer with operations in US and China
• Server Time Zone = Pacific Time (SF)
• Vision China (Inv. Org / OU) attached to the China LE with Time zone = Hong Kong
• Jan 1st 10:00AM (China) = Dec 31st 6:00 PM (SF)
• Business Flow in China on Jan 1st :
• Sales order booked & shipped confirmed (O2C)
• PO receipt and delivery transaction (P2P)
• Close Inventory December 2006 period
• Sales VP review Dec 2006 Bookings (BI)
Operations (China)
Jan 1 10:00am
Local Office (SF)
Dec 31 6:00pm

27
Resources
• Timezone FA Website
• Whitepaper
• Business Requirements document
• Working Group email list: apps-wg-timezone_ww@oracle.com

28
• Enterprise
• Business Unit
• Reorganizations

29
Fusion v1.1 Solution Approach
Cost Center Administration: Hierarchy Example

30
Fusion Solution Approach
Cost Center Administration: Process Flow
• There will be a single process (UI) used to setup and
maintain cost centers
• It will be possible to flag cost centers for automatic
department creation from this UI
• Alternatively, users can setup cost centers first, and later
assigned them to departments
• Cost centers can be assigned many attributes based
on which additional hierarchies can be built
• Manager, product, legal entity, external code….

31
Fusion v1.1 Solution Approach
Cost Center Administration: Process Flow Example

32
• Enterprise
• Business Unit
• Reorganizations

33
Reorganizations Process Manager

34
Reorganizations Process Manager

35
Resources
• Cost Center FA Website
• UI Designs
• Working Group email list: apps-wg-cc_ww@oracle.com

36
Architecture Fly By
• The Case Topics
• Navigation
• Services
• Security

37
General Electric
GE - A Global Chart of Accounts implemented in 11 structures
Business Entity with 1 value shared across 13 structures
Cost Center with 13 value sets
CDR Account with 1 value shared across 13 structures
Sub Account with 12 value sets
Analysis 1 with 12 value sets
Analysis 2 with 11 value sets
With two structures carrying one or more of these additional segments
Analysis 3
Tax
Product
Structure Name
UK Account Code 01
Germany Account Code 01
Ireland Account Code 01
Igroup Account Code 01
Czech Republic Account Code 01
Norway Account Code 01
Sweden Account Code 01
Denmark Account Code 01
Stamford Account Code 01
GIB Account Code 01
Scan Consol Account Code 01
Consolidated Book Account Code

38
• Separate Chart of Accounts Structure from
Value Sets
• Separate hierarchies from the value sets
• Allow range of accounts to be specified using
a node in a hierarchy
Fusion Chart of Accounts

39
Resources
• Chart of Accounts FA Website
• Whitepaper
• Working Group email list: apps-wg-coa_ww@oracle.com

40
Architecture Fly By
• The Case Topics
• Navigation
• Services
• Security

41
What is Date Effectivity
• Date Effectivity in PeopleSoft is a mechanism for
versioning reference data.
• Allows users to change the attributes of an object over
time and store the older versions of that object
• Applications join to the correct version of the object
based on the date of the transaction which references
that object
• Allows users to enter future dated versions of an object
• Allows users to view a history of all the changes to an
object and see when those changes took effect

42
What is Date Effectivity
Transaction
Reference Ref. Over Time
Reference at Date
Transaction
Ref. Over Time

43
Resources
• Date Effectivity FA Website
• Working Group email list: apps-wg-effdate_ww@oracle.com

44
Architecture Fly By
• The Case Topics
• Navigation
• Services
• Security

45
The Fusion V1 Navigation Umbrella
• Navigator
• Task Pane
• Worklists and Watchlist
• Dashboards
• Secure Enterprise Search
• Tag Cloud

46
Overview
The Navigation System – Anatomy of the UI Shell
Worklist
Watchlist
Homepage
Work Area
Tag Cloud
Dashboard
Global Search

47
• Navigator
• Task Pane
• Dashboards
• Tag Cloud

48
Overview
How users access their tasks – Menu Example
Invoices Employee Resources
Employee Growth
Employee Info
Expenses
Menu for Accounts Payable Specialist
Invoices Employee Resources
Employee Growth
Employee Info
Expenses
Manager Resources
Recruiting
Performance Mgmt
Time
Absence
Overtime
Suppliers
Menu for Accounts Payable Manager

49
• Navigator
• Task Pane
• Dashboards
• Tag Cloud

50
• Next level in the menu
• Displayed at the top of the
regional area
• Depending on the tabbing model
of the Work Area, the selected
task can:
• Replace the local area
contents
• Open a dynamic tab, or
navigate to a previously
opened tab
• Launch a dialog
Task Pane
How it works

51
• Navigator
• Task Pane
• Dashboards
• Tag Cloud

52
Global Watchlist Menu
• Available everywhere as a
global menu
• Complete at a glance view of
what the user needs to do

53
• Navigator
• Task Pane
• Dashboards
• Tag Cloud

54
Sales Dashboard

55
General Accounting Dashboard

56
• Navigator
• Task Pane
• Dashboards
• Tag Cloud

57
Secure Enterprise Search

58
If you know
You know Fusion Applications -
If you know
you know CRM -

59
Use Case
Joe attended a trade show in Las Vegas (Consumer Electronics Show,
say). He procured business cards, illuminated display signs, brochures,
handouts, moving signs, pens, small gift items from several suppliers.
One supplier he liked a lot was ABC. Terry Green from ABC was in
regular touch with Joe keeping him informed of the order status, and as
a courtesy had even met with him in person for dinner at the hotel.
Besides delivering all shipments on time, ABC was one of the few
suppliers who had made special arrangements to ship items to Joe’s
hotel accommodation at Downtown Marriott in Las Vegas. Months later,
while preparing for the next trade show, Joe is trying to remember
contact info for supplier ABC.

60
• Apps and SES are two separate instances.
Apps SES
Apps data is selectively moved to SES.
Searchable, Display, Security attributes
Use simple search UI to find information.
Security
Policy
•My authorized
business units
•My authorized
cost center
•My Privileges

61

62
Architecture Fly By
• The Case Topics
• Navigation
• Services
• Security

63
The Fusion V1 Services Umbrella
• Data Model Control
• AIA Reconciliation
• Approvals and Workflow
• Coexistance Strategy
• Services Discovery Strategy

64
Data Model Control
Tables 20,000
Logical Entities 6000
Business Objects 2000
Shared
Business Objects 500
Replicated
Service
Enabled
Reference Entities
4000
Transactional Entities
2000
• To make any sense out of what we have we really need to relate core
concepts. To make the relation (only) in the Build Phase/in our code is too late
to effectively perform data reviews at lowest cost.
Seeded Entities 3000

65
AIA EBO Development Methodology
Stage 2: Reference Structure
Validation
Requirement
Review
Application
Mapping
EBO
Development
EBM
Definition
EBO
Design
Reference
Structure
LBO Reconciliation
Journal Entry
Journal Entry Line
EBO
LBO
Journal
Journal Line
LBO EBO
Business Component
LE

66
 All Oracle Applications
 Extensible to Third Party and Legacy Applications
 Built on Open, Standards Based Middleware
 Upgradeable
 Common Object Model
 Process Integration Packs
4 Acquisitions
17 Acquisitions*
Legacy
Applications ISV Partners
Products
Customers
Employees
Suppliers
…
Oracle Item Object
= Fusion Item
= AIA Item
A Common Data Model
Oracle Customer Object
= Fusion Customer
= AIA Customer
Oracle Supplier Object
= Fusion Supplier
= AIA Supplier

67
Approvals and Workflow
Purpose
• Ensure a consistent user experience for approval
management across products and product families
• Provide functional guidance for teams incorporating
approval or workflow features into their Fusion products
• Support teams writing functional designs to upgrade
• AME/AWE features to AMX or
• Workflow features to the SOA suite of tools

68
Approvals and Workflow
Resources
1. Functional Uptake Document for approvals
management:
2. Requirement Document for the business analyst UI
for approval rule definition now in review.
3. Functional Uptake Document for the use of other
SOA Components in Fusion:
4. Enhancements to FDD template: Approvals Section
complete.

69
Coexistence Objectives
• Goals
• Easily position, demonstrate and support Fusion V1 apps/flows
implemented alongside existing Apps Unlimited applications.
• Define the Fusion/Apps Unlimited prioritized coexistence scenarios and
the underlying artifacts needed to effect them (services, integrations,
portlets)
• Coexistence Objectives
1. Define the Fusion/Apps Unlimited prioritized coexistence scenarios by
product family
• Differentiate between on-premise and on-demand; and between
various AU offerings such as EBS, PeopleSoft, Siebel and their
releases.
2. Define which of the prioritized scenarios should be “packaged
integrations” and which ones should be “enabled” through the a service
offerings
• Identify services required: Fusion, AU, and AIA (EBOs)
3. Define which coexistence scenarios should be enabled in our demo
environments.

70
Coexistence Scenarios Priority Rank
1. Fusion Talent Mgt On Demand to Non-Fusion (HCM)
2. Fusion DOO to Non-Fusion Order Entry/Fulfillment (SCM)
3. Fusion A/C Hub to Non-Fusion (FIN)
4. Fusion Territory Management to Non-Fusion CRM (CRM)
5. Fusion PPM to Non-Fusion PPM (PPM)
6. Fusion Shared Spend, Sourcing and Contracts to Non-Fusion
Requisitioning (PROC)
7. Fusion Incentive Comp to Non-Fusion CRM (CRM)
8. Fusion Workforce Directory Mgmt to Non-Fusion HR (HCM)
9. Fusion Workforce Lifecycle Mgmt to Non-Fusion Fin and CRM
(HCM)
10.Fusion Procure-to-Pay to Non-Fusion GL (PROC)
Packaged Integrations at GA

71
Fusion A/C Hub to Non-Fusion
In this integration scenario Accounting events occur in Non Fusion Systems and are accounted
for in Fusion

72
Architecture Fly By
• The Case Topics
• Navigation
• Services
• Security

73
The Fusion V1 Security Umbrella
• Function Security
• Data Security
• Privacy
• Identity Management
• Enforcement Across tools and
transforms
• Segregation of Duties
• Enforcement across the Information
Lifecycle

74
Fusion Security In use
Job, Duty and Privilege

75
Fusion Security In use
The “Data Security Policy”
link

76
Function Security – JAAS Policy Store
Payables Invoice Processing Duty
is a member of
Accounts Payable Specialist
Job
Role
Accounts Payable
Specialist
Role
Membership
Duty
Role
Payables Invoice
Processing Duty
Grant
Grant action View for
RegionPermission resource
InvoiceDashboardPageDef
To Payables Invoice
Processing Duty
Role
Membership
User
John Smith
John Smith is member of
Permission
Target
(secured
resource)
Action
Class
oracle.apps.<lbaTop>.
<lbaCore>.ui.page.
RegionPermission
View

77
is a member of
Job
Role
Accounts Payable
Specialist
Role
Membership
Duty
Role
Payables Invoice
Processing Duty
Grant
To Payables Invoice
Processing Duty
Role
Membership
User
John Smith
Permission
Target
(secured
resource)
Action
Class
<lbaCore>.ui.page.
RegionPermission
View

78
is a member of
Job
Role
Accounts Payable
Specialist
Role
Membership
Duty
Role
Payables Invoice
Processing Duty
Grant
To Payables Invoice
Processing Duty
Role
Membership
User
John Smith
Permission
Target
(secured
resource)
Action
Class
<lbaCore>.ui.page.
RegionPermission
View

79
is a member of
Job
Role
Accounts Payable
Specialist
Role
Membership
Duty
Role
Payables Invoice
Processing Duty
Grant
To Payables Invoice
Processing Duty
Role
Membership
User
John Smith
Permission
Target
(secured
resource)
Action
Class
<lbaCore>.ui.page.
RegionPermission
View

How to design functional architecture.ppt

Recommended

Recommended

More Related Content

Similar to How to design functional architecture.ppt

Similar to How to design functional architecture.ppt (20)

More from ssuser50762b

More from ssuser50762b (8)

Recently uploaded

Recently uploaded (20)

How to design functional architecture.ppt

Editor's Notes