Oracle ERP Cloud Guided Path and Best Configuration Practices - Financials Jan 2017

Oracle ERP Cloud Guided Path and Best Configu
Applies to Oracle Fusion Cloud Financial Produc

Version: 1.0 Last Updated: 6-Dec-16
PLEASE READ THIS PAGE FIRST
This guided path of Oracle ERP Cloud resources(documentation) and best configuration practices should be leveraged
Objective
Oracle provides several resources (MOS, Customer Application Connection, OU webinars) to SI partners and customers
and expand upon existing resources, the following workbook has been created to a "guided" experience for your ERP C
Scope & Assumptions

This is the first version of this workbook. The initial focus will concentrate on Oracle ERP Financials Cloud service. Addi
Budgeting) in the future. The Guided Path and Best Configuration Practices are not a comprehensive list of every availa
information/knowledge required for main implementation scenarios.
How to best leverage the worksheets (Guided Path, Best Configuration Practices)
Guided Path: Highlight key Oracle resources/best practices in the context of the Oracle Cloud Services Lifecycle. Majori
a checklist to ensure that the project team is leveraging available resources effectively. There are several resources spe
Best Configuration Practices: Practices are by Module, Component (Setup, Feature), and Type (Configuration, Caution,
handy reference during configuration design sessions. A best practice includes reviewing the best configuration practi
Copyright 2016, Oracle and/or its affiliates. All rights reserved.
This document is provided for information purposes only, and the contents hereof are subject to change without notice
conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability o
document, and no contractual obligations are formed either directly or indirectly by this document. This document ma
without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respe
Path and Best Configuration Practices for Financials
on Cloud Financial Products and current GA releases.
on practices should be leveraged by SI partners and customers during their ERP cloud implementation.
rs) to SI partners and customers to guide their ERP Cloud implementations. To further streamline the flow of information
ided" experience for your ERP Cloud implementation.
P Financials Cloud service. Additional content will be added for the other ERP cloud services (PPM, Procurement, Planning &
omprehensive list of every available resources/configuration best practice but rather a "critical path" of key
Cloud Services Lifecycle. Majority of resources will require access to My Oracle Support (MOS). Guided Path can be used as
There are several resources specifically defined for troubleshooting and configuration validation.
nd Type (Configuration, Caution, Validation, Performance, Data Conversion, etc). The Best Configuration Practices can be a
ing the best configuration practices against agreed upon configuration decisions.
ubject to change without notice. This document is not warranted to be error-free, nor subject to any other warranted or
d conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this
s document. This document may not be reproduced in any form by any means, electronic or mechanical, for any purpose,
may be trademarks of their respective owners.

Life Cycle
Service Startup
Project Design
Configure
Validate
Transition
Realization
Upgrade
Activity
Establish Project Scope, Objectives and Approach
Finalize Project Plan and Key Milestones/Deliverables

Conduct SaaS Overview and ERP Foundational Workshop(s)
Perform Security, Reporting, Integration & Data Conversion Workshops
Perform Delivered Content Reviews and Mapping
Conduct Implementation Checkpoint (Planning)
Create Enterprise Structures and Functional Setups

Import Demographic/Indicative Data and Transaction History
Configure OOTB Security, Approvals, Notifications, Reports & Integrations
Conduct Functional Review and Validation Test - CRP 1 & 2
Map delivered Business Process Models to high priority processes

Conduct Implementation Checkpoint (Design)
Develop, Test and Deploy Complex Integrations
Migrate Critical Historical Data
Develop, Test and Deploy High Priority Extensions
Load & Validate Data

Conduct End-to-End Review
Develop, Test and Deploy Critical Custom Reports

Assess Solution Completeness
Validate Production Environment Configuration

Migrate Functional Setups from Test to Production
Migrate/Configure Security and OOTB Reports & Integrations
Assess Solution Readiness
Obtain Final Cut Over Approvals

Conduct End-User Training
Perform User Acceptance

Assess Operational Readiness
Go-Live
Prepare
Plan
Complete
Artifacts
System Requirements for Oracle Application Cloud

Browser Best Practices
SaaS Cloud Delivery Policies
Oracle Financials Cloud Intro for CFOs and SIs
Service Administrator Action List
Oracle Enterprise Resource Planning Cloud Service Implementation Leading Practices

Getting Started with Your Implementation
Getting Started - Financials Cloud (Webinars)
Has the customer formally approved the project plan?
Welcome to Fusion ERP Cloud Applications - Getting Started
Cloud Known Issues and Update
Oracle Fusion General Ledger Hierarchies: Recommendations and Best Practices
Oracle Fusion Applications Implementation and Configuration Considerations Webcasts
Best Practices: Implementation and Configuration Consideration in Fusion Payments
Best Practice: CRP or Prototyping to gather/validate requirements
Oracle ERP Cloud Reporting Overview
Introduction to External Data Integration
Oracle ERP Cloud Integration with Receivables: Overview
Best Practice: Data Conversion Plan
Best Practice: Integration Plan
Security Reference for Oracle Common Features
Security Reference for Oracle Financials Cloud
Upgrade Guide for Oracle Cloud Applications Security
Cloud Application Security Architecture and Configuration: Role Privileges
Functional Setup Manager
Modern Business Processes for Finance
Logical & Relational Data Model Diagrams
Financials Cloud Delivered Reporting
Steps to set up Financial Reporting Center, Smart View in Oracle ERP Cloud
Scanner Specifications for Invoice Imaging
Setup Instructions for Printing from Oracle Cloud
Cloud Security: Federated SSO for Fusion-based SaaS
Sign-off: Project Plan & Scope
Minimum Steps for Financial Enterprise structures and GL Setup

How To ERP Fusion Expenses, Receivables, General Ledger, Payables, Fixed Assets; Procurement,
Project Costing; Mobile Expenses, SLA
Rapid Template - Enterprise Structures
Rapid Template - Cross Validation Rules
Configure Basic Enterprise Structure for Procurement ( Shared Service)
Define Taxes for Rapid Implementation
Cash Management Rapid Templates
Invoice and Payment Configuration for Rapid Implementation
Financials File-Based Data Imports
Procurement File-Based Data Imports
Project Portfolio Management Data Imports
How to Verify Data Conversion Results
Mapping of Job Role, Duty Role with Entitlements in Fusion Apps (Security Console)
Cloud Applications Security Simplified Reference Role Model
Oracle Cloud: Using External Data Integration
Using External Data Integration Services for ERP: Quick Start
Execute Enterprise Structures Setup Report
Diagnostic Tests for Fusion Procurement
Diagnostic Tests for Fusion Financials
Diagnostic Tests for
Troubleshooting FusionFinancials,
Guides: Project Portfolio Management
GL, Payables, Payments, Receivables, Assets, Tax, Subledger,
Expenses, Essbase & Financial Reporting
Troubleshooting Notes - Recently published Troubleshooting notes to help you diagnose and
resolve your issues
Debug & Tracing - Use these documents to capture debug logs and trace files
Guided Resolutions-Guided help resolving issues using diagnostic scripts
Diagnostics- Diagnostic tools, scripts, and notes to pinpoint product issues
Troubleshooting Guide for Cloud Printer
Troubleshooting Guide for Integrated Invoice Imaging
Fusion Applications Business Process Models
Is Project Governance effectively applied (meetings, steering committees, etc)
Best Practice: Configuration, Extensions, Reporting been documented
Best Practices: Solution Design Document, User Security been defined and signed-off
Documentation and signoff
Best
SizedPractice:
correctly,User
P2TTraining PlanCloud Maintenance data conflicts, turning off email notifications for
scheduled,
data conversion, SSO-enablement
Configurations, Extensions, Reports, Security, Environment, Interfaces

Tailoring Fusion Applications in the Cloud Explained
Utilize Functional Setup Manager to migrate Oracle ERP Cloud Reference Data
How to Verify Data Conversion Results
Best Practice: Test plan for requirements
Customer sign-off on UAT test plan (Go Decision)
Will a single UAT cycle be sufficient for this implementation?
Execute Enterprise Structures Setup Report
All UAT test scripts executed and differences explained.
Have all open issues been assigned to a specific party to resolve (SI, Oracle, Customer)?
Working Effective
Has the list of Openwith
SRsOracle Support - Best
been prioritized Practices
as Show Stoppers for Go Live and assigned for action by all
parties (SI, Oracle, Customer etc)? If not, what is the plan to address this?
Best Practice: Go Live communicated to Oracle Support & Development
Functional Setup Manager (New Compare Feature)

Utilize Functional Setup Manager to migrate Oracle ERP Cloud Reference Data
Diagnostic Tests for Fusion Procurement
Diagnostic Tests for Fusion Financials
Diagnostic Tests for Fusion Project Portfolio Management
How to Report on Users and Roles Assigned to Them
Guidance for Managing Customizations in Oracle Cloud: Flexfield Migration
Guidance for Managing Customizations in Oracle Cloud: BI Migration
How can I use BI Publisher to run SQL against Fusion Database
ERP Cloud Service Checklist
Performance Questionnaire and Best Practices
Is performance acceptable?
Based on user experiences so far, does the user training appear to be adequate?
Is the Help Desk effective in responding to user needs?
Best Practice: Cut Over Plan Developed and Approved

End User Training Completed
Best Practice: User Training and Communication
Best Practice: Testing Log to capture results.
Internal Help Desk created and staffed
Best Practice:
Is there Post Production
a contingency Support
plan in place Plan of the Show Stopper issues are not resolved in time? If
if some
yes, what is it? If not, what is the plan to address this?
Is the customer live on the service?
Oracle ERP Cloud Period Close
Intercompany Balancing Checklist
Fusion Receivables Close Checklist
Upgrade guide for Oracle Cloud Applications Security

Spotlight Videos
Release Content Documents (RCDs)
What’s New
Release Training
Product Documentation
Release 11 Release Readiness Page
Upgrade Guide for Oracle Cloud Applications Security
Oracle Applications Cloud - Release Upgrade Planning
Sample Upgrade Project Plan
Preparing for you Oracle ERP Cloud Release 11 Upgrade Webinar
Oracle Cloud Applications Removal of Functionality or Features
Performing Your Release 11 Upgrade
Location Type Target Audience
Link Checklist Customer, SI

Link Whitepaper Customer, SI
Link MOS Note Customer, SI

Link Oracle Help Center Customer, SI
Link Applications Customer Connect Customer, SI
OUM Checklist Customer, SI
Link Short OU Webinars Customer, SI
Link Oracle.com Customer, SI
Link Oracle Blog Customer, SI
Link Oracle A-Team Blog Customer, SI

Link MS Excel Template Customer, SI
Link Oracle Learning Center Customer, SI
Link Information Center (MOS) Customer, SI

Link Oracle Blog SI


Link MOS Document Customer, SI

Link Webinar Customer, SI
Link User Document Customer, SI
Link Applications Customer Connect Customer, SI
Link Webinar Customer, SI
Comments
Source: Oracle.com
Source: Oracle.com
Source:
IncludedOracle.com
in MOS Doc Key White Papers and Articles for Oracle Enterprise Resource Planning
Cloud
Perform these(Doc
Service ID 1970326.1).
critical Dated:
tasks as soon 2014
as possible after receiving your Environment Access
email. Your temporary password to log into your environment expires in 60 calendar days.
Included in Oracle Cloud Featured White Papers on cloud.oracle.com

Included in Oracle Cloud Featured White Papers on cloud.oracle.com
ERP: Advanced Collections,
Complementary Oracle Cloud Assets, Enterprise
ERP overview byStructures, Expenses, Financial Reporting and
Oracle University
The purpose
Analysis, of this document
Consolidation is to provide
and Budgeting, you,
Fusion the Service
Account Hub -Administrator, and your
Accounting Transformation,
Certified
Fusion SI partners
implementation
Accounting team can
Hub - leverage
with links toadditional
Overview, materials guidance in OUM,
to helpHyperion
General Ledger, you if needed.
get started
Data with your implementation
Relationship Mgmt
of the Oracle
Integration ERPFAH,
with Cloud Service
Intercompany, Payables, Payments, Receivables, Tax Approval
Management
Covers both CloudEnterprise
Updatesscheduler, SecurityKnown
and Functional PROCUREMENT:
Issues. Procurement, Enterprise
Contracts, PO and Supplier Agreements, Requisitions, Supplier Negotiations PPM: Project
An Oracle White
Contracts, Billing,Paper - April,
Project 2012.
Control, MOSCosting,
Project (Doc ID Project
1520970.1)
Foundation, Project Performance
Reporting
Additional guidance that compliments the knowledge provided in the Oracle Fusion
Applications Implementation and Configuration Considerations Webcasts
Certified SI partners can leverage additional guidance in OUM, if needed.
ERP Cloud Integrations, Receivables Web Services List, Usage Notes on Customer Profile
Contains
Services, overview
Usage Notesfor external data integration
on Receivables services
Invoice Service, for ERP
Usage Notesandfor
integration with
Receivables Financial
Create and
external systems: point to consider
Apply Receipt Service, Using External Data Integration Services, Receivables Excel Integration
Templates
Oracle Support Document 2016990.1 (Upgrade Guide for Oracle Cloud Applications Security
(white paper))
Simplified Role Hierarchy in Release 10
Simplified Business Process Maps
Scanner Specifications for Invoice Imaging To Automatically Scan And Capture Payable Invoice
In Oracle Fusion Cloud. Also provides additional knowledge resources for scanner
Overview, HowBest
configuration. it works, Configuration
practice is to reference this guide before Implementation Automated
Imaging Processing
This post explains how to setup Federated Single Sign-on with Oracle SaaS to enable users
present in existing Identity Management solutions to work with the Oracle SaaS offerings
Chart of accounts, including value sets, value set values, structures, and structure instances
Certified
Account SI hierarchies
partners can leveragetrees
including additional guidance
and tree versionsin OUM, if needed.
Accounting calendars (monthly type only)
Legal entities including legal addresses, jurisdictions, and identifiers
Search knowledge
Primary baselegal
ledgers with in MOS with
entity the convention
assignments "How to
to primary Oracle Fusion
balancing %%%%"
segment values.
Compliments
Business unitsthe content available in the Oracle Implementation Guides and Oracle Fusion
Applications
Document Implementation and Configuration Considerations Webcasts
and journal sequencing.
Uniquely identifies cross-validation rules in a deployment. Best practice is to define and enable
cross-validation
Prepare rules
your bank, beforeand
branch, anyaccount
accountinformation
combinations are created.
to enter into the spreadsheet template.
Bankyour
When information requires
organization is the country, the
implementing name, and number.
Purchasing optional module
you can upload
Branch your tax
information setupsname,
requires to create tax regimes,
number, taxes,
BIC code, andtax rates,
alternate tax thresholds, and tax
name.
recovery rates
Account information requires name, number, currency, legal entity, type, and IBAN.
Automatic offsets
Currency
Auto invoice,conversion
Billing, Budget, Cash Position, CM External Trans, Customer, Fixed Asset Made
Expense accruals
Additional, Fixed Asset Mass Adjustments, Fixed Assets Mass Retirements, Fixed Asset Mass
Self-billed
Transfers, GLinvoices
Budget Balances, Previous Year Tax Report, Segment Values and Hierarchies, Units
of Production,information
Legal
Award, entity
Project Billingrates,
Daily Events, Project budgets,
Intercompany Project
Transition, forecasts,
Journal Project
Import, Plan, Standard
Payables Project Resource
Invoice,
assignments,
Physical Project
Inventory, resource
Receivables request,
Standard Resource
Receipt, actual
Revenuehours, Expense
basis Data, Type Resources,
Supplier Bank Account,
Blanket PO Project
Resources, agreements, Contract
Import, ProjectPO agreements,
tasks Requisitions,
import, Project Supplier
transaction Addresses,
controls, Supplier
Unprocessed
Tax Entry Clarification,
Business Repository Data
Supplier Contacts, Supplier Productsexpenditure
and Serviceitem
Categories,
expense report expenditure item, Unprocessed Inventory import,Supplier
Site Assignments,
Unprocessed Labor Supplier Sites, Item,
expenditure Suppliers, PO Import
This MOS article provides guidance onUnprocessed
how to verifymiscellaneous
Oracle ERP Cloudexpenditure item,
Service data conversion
Unprocessed
results for most common conversion items. BI Tutorials, OTBI, R11 ERP OTBI Subject item
nonlabor expenditure item, Unprocessed supplier invoice expenditure Area
Mapping to Fusion Database Tables
Included
This paperindescribes
MOS DochowKey to
White
use Papers and
External Articles
Data for Oracle
Integration Enterprise
Services Resource
for Oracle Planning
ERP Cloud to
Cloud Service (Doc ID 1970326.1)
load data into Oracle Fusion Applications from external sources, such as legacy systems and
third-party applications.
New in R11, we provide an Enterprise Structures Setup Report to view your enterprise
structure and validate your upload from the Rapid Implementation Spreadsheet.
Purchasing, Self Payments,

General Ledger, Service Procurement,
Receivables,Sourcing, Supplier Portal/Supplier
Assets, Intercompany, Payables, Model
Cash Management,
Subledger Accounting
Project Foundations, Project Costing, Project Billings, Project Revenue, Project Control,
Project
IncludedPerformance
in MOS DocReporting,
Key WhiteProject
Papers Summarization, ProjectEnterprise
and Articles for Oracle Contract Summarization
Resource Planning
Purpose of this document is to list some of the common errors seen when using a cloud printer
and solution
Purpose to document
of this these issues.
is to list some of the common errors seen when using a cloud printer
and solution to these issues.
Business Publisher Model ( Read Only)

(Fusion Apps Dev Relations Blog) – Developer Focused
This MOS article provides guidance on how to verify Oracle ERP Cloud Service data conversion
results for most common conversion items. BI Tutorials, OTBI, R11 ERP OTBI Subject Area
Mapping to Fusion Database Tables
New in R11, we provide an Enterprise Structures Setup Report to view your enterprise
Certified
structureSI partners
and can
validate leverage
your uploadadditional
from the guidance in OUM, if needed.
Rapid Implementation Spreadsheet.

This resource should be referenced multiple times during the service lifecycle.
Purchasing, Self Service Procurement, Sourcing, Supplier Portal/Supplier Model

General Ledger, Payments, Receivables, Assets, Intercompany, Payables, Cash Management,
Subledger
Project AccountingProject Costing, Project Billings, Project Revenue, Project Control,
Foundations,
Document describes how to get a report that lists all users and their assigned roles. This report
Project
is not Performance Reporting, Project Summarization, Project Contract Summarization
seeded in Oracle Fusion Applications.
Step-by-step instructions on how to migrate flexfields
Step-by-step instructions
How a user can make useonofhow to migrate
BI Publisher BI migration
functionality to run a SQL query against the Fusion
Applications Database and review the result set.


AP Imaging Checklist
Reporting: checklist
Functional checklist
Included in MOS Doc Key White Papers and Articles for Oracle Enterprise Resource Planning
Oracle Support Document 2016990.1 (Upgrade Guide for Oracle Cloud Applications Security
(white paper))
Included in the Oracle ERP Cloud: Performing Your Release 11 Upgrade (Doc ID 2106763.1)
Master Document for ERP Upgrade Guidance

Module
Advanced Collections
Advanced Collections
Allocation Manager
Allocation Manager
Application Toolkit
Approval Management (AMX)
Budgeting and Planning

Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Cash Management
Enterprise
Enterprise
Enterprise
Enterprise
Enterprise
Enterprise Structures
Expenses
Expenses
Expenses
Expenses
Expenses
Expenses
Expenses
Expenses
Expenses
Expenses
Financial Reporting
Financial Reporting
Financial Reporting
Financial Reporting
Financial Reporting
Financial Reporting
Financial Reporting
Financial Reporting
Financial Reporting
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
Fixed Assets
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
General Ledger
Integration with Financial External Systems
OBIEE
OTBI
OTBI
OTBI
OTBI
Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments

Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments

Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments

Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments

Payables & Payments
Payables & Payments
Payables & Payments
Payables & Payments

Payables & Payments
Payables & Payments
Payables & Payments

Payables & Payments
Payables & Payments
Payables & Payments
Planning and Budgeting
Receivables
Receivables
Receivables
Receivables
Receivables
Receivables
Receivables
Security
Security
Security
Security
Security
Security
Security
Security
Security
Security
Security
Security
Security
Security
Security
Security
Security
Security
Security
Security
Security
Transaction Taxes
Transaction Taxes
Transaction Taxes
Transaction Taxes
Transaction Taxes
Transaction Taxes
Transaction Taxes
Enterprise
Payables & Payments
General Ledger
General Ledger
General Ledger
Transaction Taxes
Component Best Practice Type
Scoring formula Configuration
Scoring formula Configuration
Calculation Manager Performance
Intercompany Allocations Configuration

Watchlist Caution
All Approvals Performance
Amount-Based Approvals Configuration
Approval Groups Configuration
DFF-Based Approvals Configuration
Non-Amount approval rules Configuration
Supervisory Hierarchy-Based Approvals Configuration
Loading Budgets Caution

Ad Hoc Payments FYI
Automatic Reconciliation Maintenance
Bank Accounts Configuration

Bank Accounts FYI
Bank Statement Formats FYI
Banks, Branches and Accounts Data Conversion
CM Cube Management FYI
Importing Bank Statements Caution
Intraday Statements FYI
Parse Rule Sets Configuration
Reconciliation Rule Set Configuration
Reconciling Bank Statements Caution

Transaction Codes Configuration
Transactions from 3rd Party Configuration
Transmission Configuration Configuration
Transmission Protocols FYI
Enterprises Configuration
Excel Data Templates Caution
Item Master Configuration
Item Master Configuration
Outbound Integration Performance

Currency Caution
Currency Caution
Document Sequence Caution
Document Sequence Performance
Flexfields Caution
Legal Entity Configuration

Natural Languages Caution
Profile Options Configuration
Profile Options Configuration
Reference Data Configuration
Setup Report Validation
Tree Structure Configuration

Tree Structure Caution
Tree Structure Validation
Tree Structure Performance
Approval Rules Validation

Audit Validation
Audit Configuration
Audit Configuration
Audit Configuration
Expense Categories Validation
Expense Tolerances Validation
Expense Types Caution
Travel and Policies Configuration
Travel Data Quality Validation
Financial Reporting Center Configuration
Financial Reporting Center Configuration
Smartview Caution
Account Monitor Configuration
Account Monitor, Account Inspector, and Sunburst Maintenance

BI Publisher Maintenance
Financial Reporting in the Financial Reporting Center Maintenance
OTBI Maintenance
Smartview Maintenance
Asset Book Configuration
Asset Book Configuration
Asset Category Configuration

Asset Category Configuration
Asset Corporate Book Configuration
Transfers Caution
Asset Locations Configuration
Asset Locations Configuration
Calendar Periods Configuration

Calendar Periods Configuration
Close Period Caution
Create Accounting for Tax Books Validation

Fiscal Year Configuration
Loading Fixed Assets Configuration
Payables to Assets Configuration
Payables to Assets Configuration
Implementation Projects Configuration
Implementation Users Validation
Implementation Users Configuration
Account Combinations Maintenance

Account Groups Configuration
Account Segment Caution

Accounting Calendars Configuration
Accounting Calendars Caution
Accounting Calendars Performance
Adjusting Ledger Configuration
Adjusting Periods Configuration
Approval Rules Configuration

Approving Journals Configuration

Auto Reverse Caution
Balancing Segments Configuration

Balancing Segments Caution
Budget Uploads Validation
Budget Uploads Validation
Business Unit Configuration
Business Unit Caution
Chart of Accounts Configuration
Chart of Accounts FYI
Chart of Accounts FYI

Close Monitor FYI
Closing Journals Configuration

COA Value Loading Configuration
Company Configuration
Cost Center Segment Configuration
Cross Validation Rules Configuration

Essbase Caution
Essbase Cube Maintenance
Financial Close Caution
Financial Close Configuration
Financial Close Configuration
Financial Close Validation
Financial Close Validation
Future Segments Configuration

GL Balance Cube Performance
Hierarchy Configuration
Hierarchy Caution
Hierarchy Validation
Hierarchy Validation
Hierarchy Caution
Intercompany Segment Configuration
Intercompany Segment Caution
Intercompany Segment Configuration
JE Rules Sets Performance
Journal Batches Configuration

Journal Entry Caution
Journal Import Process Configuration
Journal Import Process Maintenance

Journal Lines FYI
Journals Upload Spreadsheet Caution
Ledger Configuration
Ledger Configuration
Ledger Set Configuration
Period Data Conversion
Project Segments Caution
Reporting Security FYI
Reversing Journals Caution
Secondary Ledger Performance

Secondary Ledger Performance
Secondary Ledger Caution
Segment Configuration
Segment Caution
Segment Caution
Segment Caution
Segment Security Caution
Segment Security Configuration
Segment Security Validation
Segment Security Caution
Segment Security Configuration
Segment Security Roles Configuration
Translation Caution
Value set Configuration
Year-end Processing - Close Out for Specific Industries Maintenance
Year-end Processing - Close Out Retained Earnings Maintenance
Foreign Exchange Rates Maintenance
Page Display (# of Rows) Configuration
COA Segments Caution
Subject Areas Caution

Immediate Payment vs Scheduled Payment Caution
Immediate Payment vs Scheduled Payment Configuration
Invoice Creation Maintenance
Invoice Groups Caution
Invoice Imaging Configuration
Invoice Imaging Caution

Invoice Imaging Validation
Invoice Imaging FYI

Invoice Imaging FYI

Invoice Tolerances Configuration
Payables Cash Requirement Report Maintenance

Payables Unaccounted Transactions and Sweep Report Maintenance
Payment Process Request Template Configuration

Payment Validations Validation
Payment Validations Caution

Control Data Sync Caution
Activity GL Accounts Caution
Intercompany Balancing Rules Configuration
Manage Reference Data Sets Configuration

Open Account Period Caution
Receivables to Ledger Reconciliation Report Configuration
Receivables to Ledger Reconciliation Report Configuration
Custom Roles vs Data Roles Performance

Data Access Sets Performance
Data Roles Performance

Data Security FYI
Duty Roles Configuration
HCM data Security policies Configuration
Job Roles Configuration
Predefined Roles Caution
Predefined Roles Configuration
Privileges Caution
Privileges Caution
Provisioning Security FYI
Roles Caution
Roles Configuration
Roles Configuration
Roles Caution
Roles Performance
Roles Performance
Security Console Configuration
Accounting Program Validation
Accounting Program Configuration
Accounting Program Performance
Accounting Rules Configuration
Accounting Rules Configuration
External Feeds Configuration

Reporting Configuration
Addresses Configuration
Business Categories Configuration
Fiscal Classifications Configuration

Tax Geographies Configuration
Tax Regime Caution

Tax Zone Configuration
Tax Zone Configuration
Essbase Caution
Cross Validation Rules FYI
Cross Validation Rules Caution
Tax Setup Configuration

Best Practice
A data point is a component of a scoring formula. It must be defined prior to creating a scoring formula. (NOTE:
Configuring data points requires SQL access which is not available in Oracle Cloud implementations). Requires a SR. The
values calculated by a data point are weighted and used in the scoring formula. You should test all data points and
scoring formulas in a test environment using a portion or all of your production data.
Use the Oracle provided samples.

• Copy and change from the provided sample strategies.
Adobe Flash Player 10 or above is a required component for the Calculation Manager. Upgrade your Adobe Flash Player
if the Calculation Manager's performance slows down after upgrading your browser.
Intercompany allocations must have either one debit line or one credit line. The other side can have as many lines as
required. (One to Many).
You should not set a Watchlist item refresh interval that is less than five minutes.
Test rules using real-life volume (load via spreadsheet) to ensure effective cloud sizing.
For Amount-Based approvals, make sure you define rules to cover all amounts from $0 to ∞ (infinity)
Only static groups are allowed in the cloud (no dynamic groups). The Supervisory Hierarchy is the one that is most
commonly used. Starting with the requester or a given approver, it generates a chain that has a fixed number of
approvers in it.
If Approvals are based on DFFs, then you should make DFFs required or train your users to enter them.
For approvals NOT based on amounts, then include a catch-all rule.
If Supervisory Hierarchy is used, make sure every employee has at least one supervisor assigned. The same is true for
Job level. Make sure you have a hierarchy of job levels.
When the GL Balances Cube is rebuilt, the process retains the budget balances as well as the actual balances. Only the
budget balances loaded using the spreadsheet or flat file through the GL Budget Balances interface table are retained.
Release 11 Ad Hoc Payments only support electronic payments

Use auto reconciliation when processing a large volume of bank statements or wanting to automate the reconciliation
process.
Make sure that any bank accounts that will be used for Ad Hoc Payments or Bank Transfers are designated for use with
Cash Management.
When setting up your bank accounts, name it uniquely and use some defining attributes in the name. This will be the
first thing your users will search a bank account by.
You should also assign a unique GL cash account to each bank account to facilitate bank reconciliation. You don’t want
multiple bank accounts associated to the same GL account.
Determine the Legal Entity for each bank account. The Legal Entity must be associated to a primary ledger.
Determine the Cash and Cash Clearing account for each bank account. Enter the entire account combination based on
your chart of accounts, for example 01-000-1110-0000-000.
We support 4 formats out of the box: BAI2, SWIFT, FINSTA, and ISO20022 (Specifically the CAMT version of he
ISO20022).At this time we do NOT support custom formats, but it is planned for a future release.
Use the Rapid Implementation spreadsheet. You must have theses defined before you can start loading and importing
your bank statements.
The cube maintenance processes performs automatic updates when new bank statements are loaded or external
transactions are created.
The name of the bank statement zip file, including the '.zip' extension, must not be more than 50 characters long.
We natively support ISO 20022 CAMT052 V2, SWIFT MT942, BAI2, and EDIFACT FINSTA formats.
Parse Rule Sets allow you to parse information on the bank stmt onto named attributes which is used for reconciliation.
Typically, there is a descriptive text field on the bank statement that contains a lot of information that is sometimes used
for reconciliation. Best Practice: Get some sample statements from your bank, verify which text information you want to
be able to extract and use for reconciliation in order to build your Parse Rule Sets.
You should order the rules to achieve a greater reconciliation success rate. You want to place the strictest rule, the one
that is most accurate, as your first rule. And then keep relaxing the criteria to cast your net wider to find possible
matches for that transaction.
There is no system enforcement that prevents GL from closing the period if the bank reconciliation is not completed.
Reconciling bank statements before closing GL period is best practice.
You can map transaction types to statement lines and the Transaction Codes setup. You need to define Transaction
Codes for both manual and electronic bank statement processing. You have to do this so the system will know which
Subledger source to look for when reconciling a transaction to a bank statement line.
Out of the box, the Subledger Accounting Method for Cash Management supports external transactions. If you are
bringing in transactions from a 3rd party system, then you must modify the Subledger accounting rules so that the
accounting is generated correctly. You need to modify the rules for the accounting method and application source. One
side of the transaction will always affect the cash account, but the offset is unknown unless you tell the system.
You should define a transmission configuration to specify the parameters for transmitting a bank statement file. We seed
one format for each bank statement. But you can tweak the format or add a format.
We support a number of transmission protocols to load your electronic bank statements, such as HTTP, HTTPS, AS2, etc.
There is normally a single enterprise organization in a production environment. Multiple

enterprises are defined when the system is used to administer multiple customer companies, or
when you choose to set up additional enterprises for testing or development. Consider deployment on a single
instance, or at least, on as few instances as possible, to simplify reporting and consolidations for
your global enterprises.
The columns that you do not intend to use can be hidden, but not reordered or deleted. Deleting or reordering columns
will cause the load process to fail and result in an unsuccessful data load.
Have a single item master; Include an item and its definition of form, fit, and function only once in
the item master; Separate the item master organization from organizations that store and
transact items. If you manage your subsidiaries as separate businesses, there may be reduced value in a single item
master.
Create Items in Item Master with default asset category and category’s Clearing Account as charge Account.
In case of PO without item specify the asset clearing account as PO Charge Account.
BI Publisher is the recommended reporting tool for outbound integration as it can handle high transaction volumes and
the report formats can be saved as .csv files. To ensure good report performance, it is advisable to use only seeded BI
Publisher XML extracts which come with seeded report templates to create new report templates. Ensure you confirm
performance and load balancing on the BI server on the non-production environment before migrating the reports to
the production environment.
You cannot change a currency code after you enable the currency, even if you later disable that currency.
If you do not enter a start date, then the currency is valid immediately. If you do not enter an end date, then the
currency is valid indefinitely.
Avoid changes to the options after you saved your work on the Manage Document Sequences and Manage
Document Sequence Categories pages. Once a document sequence category is created, you cannot change the
application, the category code, or the table name.
Gapless Sequencing: Use this type of sequencing only if necessary because it may affect the
performance of the system and slow down transaction processing.
You can enable key flexfield segment instances and descriptive flexfield segments for business intelligence if the flexfield
is registered in the database as an Oracle Business Intelligence-enabled flexfield.
Each registered company (with it’s own tax ID) should be defined as a legal entity in Fusion. Each legal entity is
accounted for in only a one ledger, but one ledger can serve multiple legal entities.
Once you add a language, it cannot be deleted, just disabled.
Establish profile at the site, product and user level. Set site-level profile option values before specifying values at any
other level. The profile option values specified at the site-level work as defaults until profile
option values are specified at the other levels.
Define profile option categories first and assign new profile options to existing categories rather than defining profile
options first and then defining categories to categorize them.
Reference data sharing facilitates sharing of configuration data such as jobs and payment terms, across organizational
divisions or business units. A common reference data set is available as the default set, which can be assigned to
several business units sharing the same reference data. There are 3 options: Assignment to one set only, no common
values allowed, Assignment to one set only, with common values, Assignment to multiple sets, no common values
allowed. Oracle ERP Cloud applications contains a reference data set called Enterprise.
New in R11, we provide an Enterprise Structures Setup Report to view your enterprise structure and validate your
upload from the Rapid Implementation Spreadsheet. If you uncover errors then you can run the appropriate individual
diagnostic tests.
Creation Mode: Indicates the source where the tree structure is being defined. For predefined tree
structures select Oracle and for custom structures, select Customers.
If you delete a tree structure, all the associated trees and tree versions are automatically deleted.
Use the tree structure audit results to verify the tree structure's correctness and data integrity.
Tree structures are heavily loaded with data. As a tree management guideline, use the following settings to improve
performance of data rendering and retrieval: row flattening, column flattening, column flattered entity objects, ADF
Business Component View Objects.
Each expense report can satisfy only one rule within a rule set. If an expense report does not satisfy any rule in a rule
set, an error occurs during the approval process and an incident is reported in Oracle Enterprise Manager Grid Control.
Implement audit rules to audit sub-set of expense reports.
Set up images as required to expedite auditing.
Enable bar code for convenient receipt package check in.
To enable audit of expense reports, you must define audit rules in addition to approval rules.
Define policies and rates for expense categories.
Define tolerances for policies.
You cannot set up varying receipt types by expense types.
Setup centrally-billed travel cards for high value travel charges, such as airfare.
Improve travel data quality by (a) enable automatic creation of trip-based expense reports, (b) define itinerary validation
rules.
Store the financial reports in My Folder/ or Shared/Custom directories to access them in Financial Reporting Center.
Ledger setup has to be completed before the database connection can be created. Oracle ERP Cloud General Ledger
balances cubes are created as part of ledger setup. There is a separate cube for each combination of chart of accounts
and accounting calendar. A database connection is needed for each cube.
Since Smart View is an add-in to Microsoft Office products, you can install Smart View only on a Windows operating
system.
Define tolerance rules to create self-monitoring accounts. Tolerance rules can optionally be set using criteria of a
comparative measurement between two selected balances This Automatically monitor your key accounts in real time
on an exception or permanent basis
Best suited for Exception-based account monitoring with multidimensional analysis and drill-down capability
Best suited for High volume operational reporting with configurable templates
Best suited for Boardroom ready financial statements with drill-down to your source transactions
Best suited for Ad hoc queries of transactions.
Best suited for Spreadsheet financial reports with multidimensional analysis, pivoting, and drill down capability .
The Fixed Assets Subledger is an Asset Book rather than a BU. Each asset is recorded in one book for
valuation according to accounting principles, and in others for tax or regulatory/statutory purposes.
Depreciation rules are maintained for each book.
Multiple depreciation and accounting representation are available for an asset using the Tax Book.
(1) Tax depreciation books are commonly used for accelerated depreciation and statutory reporting
(2) Tax Books are associated with a Corporate Book. The tax book uses the assignment and source lines information from
the corporate book Tax Book can be optionally mapped to the primary ledger or its secondary ledger (Sec ledger must
be associated with the primary ledger of the Corporate Book).
(3) Secondary ledger must have the same COA and Currency as the primary ledger.
It can however have it’s own calendar and Sub-ledger accounting method (independent of the Corporate Book).
(4) An Asset must exist in Corporate Book before it is added to Tax Book. You cannot add an asset directly in an asset tax
book.
(5) GL Accounting entries may be optionally posted to GL using a check box in the Asset Book Definition. Typically you’d
post accounting entries for the corporate asset book but not necessarily for the asset tax book.
Utilize asset category to group assets for financial reports and defaulting depreciation rules, tax rules, retirement rules
and GL accounts. Category is flexfield – can have up to 7 segments – you can decide how many segments you want to
have for your business. For most of our customers, at least have two segments – major category/minor category. Please
note that You cannot modify the structure after recording an asset addition.
Item can be mapped to asset category (optionally) in the item master.
At least one Corporate Book is defined for each Primary Ledger. Security in FA is striped by Corporate Book.
It is possible to track different BSVs within a Book. GL Accounting entries may be optionally posted to GL using a check
box in the Asset Book. Reporting currency can be set up for a ledger for global operations/reporting. Automatic
reporting currency conversion for asset books mapped to a ledger which has reporting currencies.
Reference Data Set allows sharing of setup data across books or to restrict by book.
ERP Cloud does not allow Transfers across Asset Books. This restriction should be carefully considered while designing
your Book/ BSV Structure.
If the locations are spread across countries then country should be one of the segments, other segments may include
state, city, and site.
If specific location detail is required e.g. for Bar-Coding then segments for building and room number should also be
created.
All calendar periods have to be set up from the period corresponding to the oldest date placed in service to the last day
of current fiscal year.
At least one period has to be setup after the current period. This is necessary to close the current period.
Currently, No way to reopen a closed period or rollback depr for a closed period.
Run the create accounting for all tax books even if the accounting entries are not required to be transferred to General
Ledger because many standard report will show the amounts correctly only after the accounting entries are created.
Fiscal years should be defined from the oldest Date Placed in Service through the current fiscal year.
Before starting an implementation, prepare a list of all the assets which have to be entered. Sort the assets in the order
of Data Placed in service. Create a Fiscal Year from the earliest Data Place in Service.
Payables BU must be tied to the same ledger as the corporate book for which you want to interface the asset invoices.
Multiple Payables Business Units tied to the same ledger can interface to a single corporate book or multiple corporate
books.
Allow or restrict the transfer of invoice distributions to Assets based on invoice line type by configuring the Create Mass
Additions program in the Accounting Class Usage in Subledger.
Consider segmenting implementation projects based on product family, timing of projects, and resources (e.g., different
people implementing Financials, Projects, etc.).
Best practice: Run the process “Retrieve Latest LDAP Changes” if assigning or removing roles to existing users.
Best practice: The Application Implementation Consultant has broad access to any enterprise structure. If you want to
limit access, use the Create Data Roles for Implementation Users task to create a data role based on a job role with
limited access, such as the HCM Application Administrator job role.
Utilize the Inherit Segment Value to reduce maintenance. Running the process eases chart of accounts maintenance by
automatically replicating changes to segment value attributes of the account combinations that contain that segment
value.
Account groups are easy-to-use reporting components that save queries on account balances that require regular
monitoring. With Account Groups, you define tolerance rules to create self-monitoring accounts. Tolerance rules are set
using criteria comparing two balances. The comparison looks for an increase or decrease that is above or below a
percentage or constant amount threshold. When the criteria are met, the Account Monitor, General Accounting Infolets,
and Financial Reporting Center display the balance information for the account specified.
Making sure that you implement the lowest level of detail for accounts is important. It may appear to be additional
configuration overview , but rest assured that it’s better to have more detailed accounts in the long run. It’s easy to
summarize accounts, it’s difficult to break an account down.
Specifying all the options makes defining a correct calendar easier and more intuitive with fewer errors.
it is difficult to change your accounting calendar after a period status is set to open or future enterable.
If you plan to run translation, specify a calendar start date that is a full year before the start date of the year of the first
translation period for your ledger. Translation requires that the first period that is ever translated for the ledger must be
at least the second defined period in the ledger's calendar because it derives an opening balance based on the prior
period's ending balance.
It is best practice to “pad” your calendar. In fact, Oracle recommends a start date that is a full year before the start date
of the year of the first period you plan to upload balances for or run translation
For an accounting calendar that is associated with a ledger, changing period names or adding a year updates the
accounting period dimension in the balances cubes.
When an enterprise has multiple ledgers, they may have a need to create an additional adjusting ledger for things like
intercompany eliminations or other adjustments that they do not want reflected in the local ledgers. Another option is
just to define additional balancing segment values in existing ledger to capture the adjustments/eliminations.
Adjusting periods are recommended to avoid large balance fluctuations in your standard accounting periods.
There is one predefined approval rule. If you enable the ledger and the source for approval, then the journal entry is
sent for one level of approval by default. AMXList Builder: Human Resources (HR) Supervisory (this method uses the HR
Supervisory hierarchy levels and specifies the number of levels available for approval); Job Level (A relative dollar
amount can be attached to a job. The approval list moves up the HR Supervisory hierarchy to the point it finds a job with
the necessary approval amount); Position (A relative dollar amount can be attached to a position); Approval Group
(Approver groups represent functional or subject matter experts outside the transaction's managerial chain of
authority); Dual Chain (Processed at the same time).
Best practice is to select Job Level, HR Supervisory, or Position list builders for your journal approval rules.
Approval is enabled at the ledger and source level. Both the ledger and journal source must be enabled for the approval
process
Select the Skip creator for Approval List option on the journal approval rules configuration page to prevent the submitter
from approving a journal batch.
Journals posted by the Auto Reverse process always bypass approval.
Consider this option carefully as it provides more granular reporting but requires more processing resources. Ensure
that balances are immediately maintained in accordance with the necessary balancing actions to produce consistent
financial reporting . Multiple balancing segment ledgers that are not maintained from the beginning of time require
extensive manual balance adjustments to catch up and realign the balances in accordance with the multiple balancing
segments.
The balancing segment should map to the legal entities. Many of our customers have a 1-1 mapping of legal entity to
Balancing Segment Value.
Once a segment has been enabled and designated as a balancing segment, you must not change the segment. These
settings must be consistently maintained throughout the life of the chart of accounts to control the accuracy and
integrity of the financial data.
Do not set a segment already qualified as a natural account or intercompany segment as any of the three balancing
segments.
When uploading budgets, you should use the ADFdi spreadsheet that is accessed from the General Accounting
Dashboard (GAM) because it has built in validations to prevent data entry errors. The File Based Loader does not have
these built-in validations.
Budget data is uploaded directly to the Essbase Cube. It never passes GL_Balances table or the Account Combinations
Table. So if customers upload budgets to a bad combination, they will quickly know because no actuals will be shown in
reports since transactions and journals cannot be posted to accounts that violate the above rules.
3 common options (a) a BU for each of the businesses (revenue streams), (b) for each of the registered companies, and
(c) even for the business as operated by the companies.
You cannot have one accounting BU process transactions that have an accounting impact for multiple ledgers
Use a common global chart of accounts for all entities. This will facilitate consolidations and minimize maintenance
efforts.
You must deploy your chart of accounts before use.
Chart of Account Changes

Once a chart of accounts has been deployed, only the following changes are supported, and they require redeployment.
The first two (enable/disable BI, associate a tree) may also impact the flex mapping for OTBI.
Enable or disable BI for a value set
Associate a tree in segment instance
Change the 'default value' for a value set
Enable or disable segment value security
Change prompt name for segment name
It is strongly recommended you use the Data Type of “Character” and Subtype of “Text”. This allows for better flexibility
in extending your chart of accounts to use both characters and numbers. If you use the Subtype of Numeric Digits Only,
you will be stuck with your decision and never be able to add characters values later.
You should just have one chart of accounts instance to one structure
Take a top down approach to configuring chart of accounts: (1) Reporting Requirements, (2) Allocations.
The list of managers available for assignment contains the persons defined in the Human Capital Management (HCM)
module of Oracle ERP Cloud Applications.
If you use secondary ledgers or reporting currencies, you must define a conversion rule to prevent replication of your
year-end closing journals from your primary ledger. Replication can cause unbalanced journal entries if different
currencies and conversion rates are used in the ledgers. Instead, run your closing journal processes directly in your
reporting or secondary ledgers to ensure that the balances are reduced to zero.
It is best practice to use the Rapid Implementation spreadsheets instead. Just query the task called “Rapid
Implementation for Financials” from FSM.
Align FAS 131 (IFRS 8) Segment Reporting with their business reporting and company code segment design.
Unless your customer is really small, they generally have an idea of their cost center structure. However, in global cases,
they may have to align/re-assign their cost centers. For example, the “Finance Department” cost center code is
probably different in every company. The most straightforward way is to build a master cost center list, eliminate the
duplicates by mapping the old for each company to the new global set.
Best practice is to define and enable cross validation rules before: (1) Balances are loaded,
(2) Transactions or journal entries are imported or entered and (3) Account combinations are created.
Do not place spaces at the beginning or end of names. Essbase ignores such spaces.
Once the P2T is complete there is one manual step you have to execute, and that is to submit the ‘Create Cube’ report
program to rebuild the Essbase Balances Cube in the non-production environment. It is recommended that you submit
the ‘Create Cube’ report program during non-business hours to minimize possible performance impact.
Run the Payables and Receivables to Ledger Reconciliation reports only after the Receivables and Payables periods are
closed to additional Subledger transactions.
Reconcile receivables or payables accounts in one of these ways:

- For the entire ledger, by running the reports for your ledger.
- For more control, by running the reports for your individual primary balancing segment values within the ledger. Your
primary balance segments must be implicitly mapped to your payables and receivables business units in your enterprise.
Restrict receivables and payables accounts in your general ledger by designating a control account and not allowing
other sources to post to them.
Review warnings raised in the general ledger close period request log files. Verify that exceptions such as unposted
journals, are intended to be left out for the period.
The Payables to Ledger Reconciliation report integrates with the AP Trial Balance report. Use the AP Trial Balance report
to obtain the beginning and ending payables accounting balances and drill down to the details.
Because it is impossible to predict the future, and because it’s difficult to change your COA structure post-
implementation, it’s a good idea to consider implementing one or two additional segments for future use. These
segments can have a single “0” value that shouldn’t interfere much with your users ability to enter journals &
distributions quickly.
Only rebuild the GL Balance cube during off hours.
Adding or changing COA values will automatically call the GL Balance Cube rebuild when a Subledger posts to General
Ledger.
Use the on demand programs to rebuild dimension members for each dimension and to refresh balances to the cubes
rather than rebuilding the cube. Always run the rebuild GL Balance cube after an upgrade.
Consider requirements for financial reporting, allocations, cross validation rules, revaluations, and chart of accounts
mapping.
Create two tree versions of the same tree before creating any financial reports or allocations to force the fully qualified
name to be generated.
Keep the two tree versions in sync always to guarantee fully qualified names are used in financial reports and
allocations.
Use the same tree version names over time to avoid breaking your reports or configurations.
Use different hierarchies if you have requirements to roll the same child to more than one parent.
If you want to keep an audit history, it is recommended that you copy the hierarchy version and use the copy as the
version for audit history. After you copy the hierarchy version, modify that same version to use as the latest version. You
do not have to change reports.
Hierarchies you create for reporting or allocations may not be suitable for setting up cross validations, revaluation, and
chart of accounts mapping rules.
Run Process Account Hierarchies to perform the following: tree audit, tree activation, tree row flattening, Tree column
flattening, maintain value sets, maintain account hierarchies, and publish hierarchies.
Use Smart View to verify that the account hierarchies were correctly published.
When using hierarchies for reporting and allocations, you must publish them to create the associated Essbase cubes.
When creating hierarchies, it is best practice to create a top-most root node (Level 0). This allows you to more easily
select the entire hierarchy. For hierarchies not used for reporting & analysis and allocations (in other words hierarchies
for cross validations, revaluations, chart of accounts mapping, and segment value security rules), you should create one
hierarchy with multiple level 0 nodes.
For any company that has more than one balancing segment value, it’s a good idea to have an intercompany segment.
A key gotcha is that if your customer is or may in the future use segment value security on the balancing segment, you
should create two value sets, one for the BSV and one for the Intercompany segment, because segment value security is
based on the value set not the segment itself.
If you have a high volume of primary BSVs, and you want to easily track intercompany activity for eliminations, consider
including an Intercompany segment in your chart of accounts.
Journal Entry Rule Sets can be defined at the event class or accounting event type level. As a general rule of thumb, it is
better to define them at the event class level because it reduces setup and maintenance (and potentially improves
performance). If a Journal Entry Rule Set applies only to an event class, Journal Line conditions can be used to determine
for which type of event the journal line and account rule are used.
You can record a set of journal entries in a single batch. For example, all of your statistical entries or monthly accruals
can be entered in one batch for easy reference, querying, and posting. Use multiple batches when it is important for
each journal entry to be reversed separately or to document a specific transaction or adjustment.
Currency can only be changed on an unposted journal entry.
Configure the following settings before running the Journal Import process.
(1) Set up your General Ledger to accept journal import data by defining your ledger, currencies, accounts, journal
sources, and categories.
(2) Optionally, run the Optimizer program to ensure optimal system performance.
(3) Define your import program parameters and schedule if using automatic processing.
(4) Set the period status to either future enterable or open. Journals can be created by the Journal Import process in a
future enterable period, but not posted. Posting requires an open period.
(5) Export data from your Subledgers and populate the General Ledger Interface table.
(6) Optionally, enable encumbrance accounting.
Utilize Oracle Help Center -> Using General Ledger -> Journal to get a listing of possible Journal Import Error Codes.
When you are reviewing a journal, 500 journal lines can be exported to MS Excel. To review the details of a journal larger
than 500 lines, run the General Ledger Journals Report for the journal batch.
If any of the journals on the worksheet aren't balanced, then none of the journals on the worksheet are uploaded.
Enable the ledger option Notify When Prior Period Journal to display a warning when you create a journal in an open
prior period.
Use a Thin approach when GL is used with a enterprise profitability management (EPM) solution - example: Oracle
Projects. In the thin general ledger, business units, divisions, and individual departments are
not represented in the chart of accounts. A general ledger, with segments representing all aspects and capturing every
detail of your business, with frequent posting, many values in each segment, and many segments, is called a thick
general ledger. A thick general ledger is designed to serve as a repository of management data for a certain level of
management. A ledger determines the currency, chart of accounts, accounting calendar, ledger processing options, and
accounting method for its associated Subledgers. Companies account for themselves in primary ledgers, and, if
necessary, secondary ledgers and reporting currencies. Your transactions from your Subledgers are posted to your
primary ledgers and possibly, secondary ledgers or reporting currencies.
Utilize a Ledger Set to facilitate a unified closing and GL operations. Generate General Ledger Allocations: Allows you to
create journals to allocate amounts in a single ledger or across different ledgers in a ledger set.
Select a period before the first period you plan to load history or perform translations to enable running translation. You
cannot run translation in the first defined period of a ledger calendar.
While possible, we do not recommend implementing a project segment in the COA. First, projects tend to change
frequently, and this will require additional overhead maintenance. Second, if the customer is project-focused, they
would be better off implementing ERP Cloud PPM with its robust project-related reporting.
If you want segment value security to apply for reports, you should consider using the reporting hierarchy that has been
published to Essbase Cubes. All of our reports look at Essbase cubes. You may need 2 different hierarchies: One for
Reporting users & another for data entry folks if the rules are not the same.
Journals that have already been reversed once cannot be reversed again. If a journal was reversed in error, copy the
original journal entry and then edit it, as needed.
Journals entered directly into the primary ledger are automatically replicated to one or more secondary ledgers in a
separate batch. However when your reverse the original journal in the primary ledger, the corresponding secondary
ledger journal is not reversed. Reverse the secondary ledger journal separately, either manually or by using reversal
criteria sets.
The AutoReverse process does not check that the reversal date is a valid business day for an average balance ledger.
The journal validation in the journal pages or import process does the check and if necessary, rolls the date to the next
business day.
A secondary ledger is an optional ledger linked to a primary ledger for the purpose of tracking alternative accounting.
Conversion Levels: Balance, Journal, Subledger, Adjustments. Secondary ledger will require additional
resources/performance. For secondary ledgers, the least costly level is the adjustment data conversion level because
it produces the smallest amount of additional data. The balance data conversion level is also relatively inexpensive,
depending upon how often the balances are transferred from the primary to the secondary ledger. Ex: since most of
the accounting is identical between US GAAP and IFRS, a better solution is to use the adjustment only level for your
secondary ledger.
Secondary ledgers provide functional benefits, but produce large volumes of additional journal entry and balance data,
resulting in additional performance and memory costs
Use the same currency for primary and secondary ledgers to avoid difficult reconciliations. Do not use Secondary
Ledger for Conversions, Translations, Revaluations.
To facilitate intercompany matching and elimination, use an Intercompany segment. Examples of segments that may be
found in a chart of accounts are company, cost center, department, division, region, account, product, program, and
location.
To plan for future growth in the business organization that requires additional segments in the chart of accounts, extra
segments can be added to the chart of accounts structure during your original implementation. Since all segments of
the chart are required and have to be enabled, these unused segments can be assigned a default value (zeros).
Oracle Cloud ERP applications allows up to three balancing segments. A balancing segment should represent a P/L or a
ROI responsibility. Oracle Cloud General Ledger supports up to three balancing segments. Best
practices recommend that one of these segments represents your legal entity to ease your requirement to account for
your operations to regulatory agencies, tax authorities, and investors. Accounting for your operations means you must
produce a balanced trial balance sheet by legal entity.
Once you assign one balancing segment value in a ledger, then all your balancing segment values must be assigned. This
recommended best practice facilitates reporting on assets, liabilities, and income by legal
entity.
Implementing multiple balancing segments requires every journal entry that is not balanced by division or business unit,
to generate balancing lines.
You cannot change to multiple balancing segments easily after you have begun to use the ledger because your historical
data is not balanced by the new multiple balancing segments. Restating historical data must be done at that point.
If you make an acquisition or are preparing to dispose of a portion of your enterprise, you may want to account for that
part of the enterprise in its own balancing segment even if it is not a separate legal entity.
In setup UIs, if Segment Value Security is enabled, you will see account combinations with those secured values but if
you try to update the field, you won't be able to use those secured values. Bottom line: You should complete all your
setups before enabling segment value security.
We are recommend using data access security to secure your primary balancing segment values, and segment value
security to secure all other segment values.
Run the deploy process by clicking the Deploy Flexfield button on the Manage Key Flexfields page before security is
enabled for the chart of accounts.
You should NOT share the same value set for the Company and Intercompany Segment IF you plan to implement
segment value security rules.
Segment security rules are defined at the value set level. Typically we recommend you define one value set that is used
for both the primary balancing segment and the intercompany segment. However, if you use segment security rules to
secure primary BSVs, this will cause problems if you use the same value set for the Intercompany segment; therefore,
we recommend you define a different value set for the Intercompany segment that has the same values as the value set
for the primary balancing segment.
For segment value security roles, the best practice is to give them a common suffix, such as SVS (segment value
security), to more readily identify them.
Important: If you post additional journal entries or change your translation rates after running translation for a period,
you must retranslate.
Oracle ERP Cloud General Ledger best practice is to define the values for the value set after the value set is assigned to a
chart of accounts structure instance. Otherwise you are not able to define the mandatory value attributes, such as
summary flag, posting allowed, and account type for natural account segment.
We also have a Balance Sheet Closing Journal program that is only used by specific industries. Most customers won't
care to use that one.
When you open the first period of the new fiscal year, we will close out the P&L and post the net income or loss to the
Retained Earnings account. We also have the Income Statement Closing Journal process that will create a physical
closing journal entry that you post if you want a physical journal entry to close out your revenues and expenses.
If you are loading a few foreign currency transactions: Use the spreadsheet loader. If you are loading many foreign
currency transactions: Use a supplier for a direct load into the Daily Rates open interface. The application validates the
rows in the interface table and then makes changes in the Daily Rates table.
Oracle Business Intelligence Enterprise Edition has a setting that controls the number of rows that display on a page. For
more information on manually configuring settings for data in views, see the Oracle ERP Cloud Middleware System
Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
Post implementation, there is a step that is required to map the COA segments to the report so that the users will see
the individual segments. If one of the following changes occurs after a chart of account has been deployed, the
COA/report mapping may need to be updated.
- Enable or disable BI for a value set
- Associate a tree in segment instance
Most importantly, you should know only to use subject areas ending in “Real-Time”. There are additional subject area
without “Real-Time” but those subject areas are used by OBIA (data warehouse).
While it is possible to build a report with multiple subject areas, it is only recommended if you have a valid
understanding of the related subject areas. We suggest using caution when building these reports.
Custom Subject Areas not supported in OTBI.
Immediate Payment may create more payment files than necessary. Immediate payment file creation precludes
grouping of similar payments that originated in different payment process requests into a single payment file.
Consider scheduling payment file creation as part of a business process where payment selection is local or
decentralized, and payment processing is centralized.
Consider using the spreadsheet to:

(1) Expedite high volume invoice entry for simple invoices that don't require extensive validation.
(2) Create invoices with similar lines.
(3) Maximize the use of spreadsheet features, such as copy and paste, or hide and unhide.
If you implemented centralized payment processing, the service provider setup and your business unit access affect the
list of values in the Invoice Group field. The invoice groups are from the invoice business units that are serviced by the
payment business units that you have access to.
Review the Imaging User Guide before configuring Imaging. The guide explains how enable exception routing,
additional language support, PO number formatting, tips for optimal recognition rates, etc. The guide is available on
MOS, Doc ID 1966280.1.
Scan invoices in black and white using the TIFF image format with International Telegraph and Telephone Consultative
Committee (CCIT) Group IV compression at 300 dpi for the optimal balance between scan quality and image size.
Avoid the JPEG format because the compression logic results in log of image details affecting recognition accuracy.
Enable Adaptive Thresholding technology on scanners to remove background colors, gray scaling,
and gradients for pure black and white images. It is critical that invoices are digitized using the Adaptive Thresholding
technology to remove gray scaling, otherwise the image size can go up to 300 KB per page.
Schedule the Import Payables Invoices and Validate Payables Invoices processes to run every 15
to 30 minutes.
Define distribution sets for your supplier sites so the validation process can automatically generate distribution
combinations for invoices that are not matched to a purchase order.
Email - Group the images into a single e-mail, depending on the size of each scanned image, to ensure that
an optimal number of e-mails are sent for processing. Note that the total size limit of attachments is 10MB per e-mail
and each invoice must be separated by a blank page.
Reconcile the actual number of invoices sent for processing with the number of invoices that
appear in the Scanned Invoices Queue region in the Invoices work area.
Oracle Document Capture, Oracle Forms Recognition and Image Process Management are imbedded as components for
the Automated Invoice Processing Cloud Service and are NOT CONFIGURABLE BY THE CUSTOMER OR IMPLEMENTATION
TEAM. If there something that imaging doesn’t do to meet customer requirements out of the box it CANNOT be
configured to meet the requirement. You CANNOT replace any components with Customer 3rd party products. This is a
preconfigured out of the box solution.
Scanners: Enterprise Class Scanners. Should support ISIS or Kodak Adrenaline/Virtual Rescan. you want a scanner
capability of dynamic thresholding to produce a high-quality black/white image. recommend document imaging
scanners from Fujitsu, Kodak or Canon; Note: We have had issues with HP Scanners. HP make wonderful printers but
their scanners did not produce high enough quality images.
We recommend less than 25 images in a batch to avoid delay caused by recognition exceptions.
If Supplier sends printed invoices then, If possible, the customer should advise the supplier to use a laser printer, do not
use a dot matrix printer.
For all invoice formats, handwriting should be avoided especially when it obscures important invoice details such as
invoice date, amount, etc.
We have a designated supporting document cover page, you can place between the main invoice and the supporting
documents.
Our solution is not template-based, so there is no specific layout for imaging to work. Invoices in a standard format with
an invoice header section and a lines section in a tabular format should have the best recognition result.
Supplier Cleanup
Invoices should have the supplier address as suppliers are recognized based on the supplier address available on the
Image. The Supplier should have the same address that is shown on the invoice setup in Fusion for better recognition.
Suppliers are valid only when they have active pay sites and site assignments
Ensure supplier setup is clean and there are no duplicates. Suppliers created in Fusion will not be available immediately
in imaging. The Fusion supplier data base will be synced with OFR once a day @9PM server time.
Purchase Order Format
It is recommended to have a PO number which is in alphanumeric format as this will result in a higher recognition rate.
For example, if you define the PO in a numeric format like a 7-digit number, it is very likely that the phone number will
be picked up as the PO number.
A format of 9-10 characters should work best. The system default format is 3 characters + 6 digits. E.g. ABC123456. The
words “PO” or “NO” should not be used as they are system reserved words.
Log a service request to disable PO capture if the customer is not implementing procurement.
BU Derivation
The BU is derived by first checking to see if the invoice is a PO matched invoice. If it is a PO matched invoice, the BU will
be derived from the PO. If the invoice is an unmatched invoice, and if the supplier site is recognized and the site has
only 1 BU site assignment, the BU will be derived from the site assignment. If the invoice cannot be matched to a PO or
a supplier site assignment, the BU will be derived from the user profile option of the user who has executed or
scheduled the import process. Now, if the customer has centralized their procurement process across multiple BUs, for
unmatched invoices, the BU cannot be derived and is defaulted with the user profile option value. Often this is not the
correct BU so you then have to change the defaulted BU to the correct BU. There is an easy way to ensure the correct
BU is derived in these cases. You can enter the BU ID in the email subject as routing attribute 1 so that the system can
directly stamp this BU on all the invoices sent in this email. There is a screen shot in the imaging guide to show how to
get the BU ID.
Utilize the WebCenter Image Process Management to check for the invoice. IPM is the most useful tool for trouble
shooting but should not be needed after the implementation is completed.
If you specify a percentage tolerance of zero, variance isn't allowed. If you want a low tolerance, specify a small
percentage. If an active tolerance doesn't have a value, then infinite variance is allowed.
The report identifies the cash required for making a payment in a payment batch. Utilize this report Before every
payment process request to determine cash requirements for that request.
Use the information to configure multiple payment process request templates.
Forecast cash requirements for a specific period, such as 30 days, by defining a payment process request template with
the applicable parameters.
Before running this report: Validate invoices to reduce the number of unvalidated invoices on the report. Create
payables accounting entries. The report then shows only problem transactions that couldn't be accounted. You can
correct the problems, and resubmit the create accounting process.
If you use bills payables, submit the Update Matured Bills Payable Status process. The process updates the status of any
bills payable with a maturity date on or before today's date.
By using a template, you can:
(1) Minimize date entry for frequently used payment processing settings.
(2) Identify cash requirements by running the Payables Cash Requirement report against the template before submitting
the template for processing.
(3) Schedule payment process requests to run on a regular basis.
Payment validations are rules that ensure disbursements are correct before they are printed or transmitted to your bank
or financial institution. Validations help find problems early in the payment process and decrease costs by preventing
invalid data from reaching your bank.
If the validation is attached to a payment method, it can't be applied to a payment file, because one payment file may
span multiple payment methods.
To achieve optimal load balancing among specialists, and to avoid task reassignment, set up routing rules that assign
invoices to a user group instead of an individual accounts payable specialist.
Invoice Images as Email: A single invoice cannot be represented by multiple attachments.
Routing of Invoice Image Based on Invoice Amount: Rules must be granular such that one rule must be evaluated to
true at run time.
Set up an exception rule for incomplete invoices. Referring to the invoice image and gather external information where
necessary to complete the invoice. NOTE: Routing is for exception invoices only, if the invoice is successfully created, it
will show under the Recent Infotile.
For Cloud implementations, we have integration with Hyperion Planning and Budgeting for the Cloud. However, there is
no out-of-the-box integration directly with ERP Cloud GL. You will need to maintain charts of accounts and hierarchies
in 2 places. The Essbase cube in GL does not talk to the Hyperion Planning and Budgeting in the Cloud cube.
Note: It is important to assign the correct Activity GL Account for the various Receivables activities. A common mistake
is setting up customer systems with AR trade or AR control accounts for activities that should be set up with revenue or
expense accounts. The incorrect accounting or misuse of AR trade (Invoice Receivables ) or AR control accounts will
cause over or understating of your open receivables, which will display as reconciling items on the Reconciliation report.
This will also require redoing the setup and potentially entering additional journals the alleviate the mistakes.
Note: You should not change the Primary Ledger on the Business Unit after defining Receivables System options for the
Business Unit. Once the primary ledger has been set for the System Options, you will not be able to change it, so due
care is required when creating the System Options.
Set up Intercompany Balancing Rules to correctly generate balancing accounting entries when more than one balancing
segment value exists on a receivables document or activity.
Allows sharing of the same reference (setup data) data across Business Units. Since you cannot use the Common data
set for Customer Site and Customer Relationships, you have to define at least one here.
Remember to open Receivables accounting period before entering transactions.
To include GL accounts in the Reconciliation report, you need to assign the Accounts Receivable Financial Category to
each account. Otherwise, differences may appear as reconciling items on the report. During chart of account setup, the
Financial Category is assigned to the natural account value of all the receivables accounts to be reconciled.
It is also recommended that you create unique GL accounts for Unapplied, Unidentified and On-Account receipts and
assign the Financial Category to these accounts as well if these receipts statuses need to be included in reconciliation.
Custom roles can be introduced to grant access to all Business Units / Ledgers / etc
Instead of multiple data roles, user only needs to be assigned 1 role.
Accessing the same subset of Business Units / Ledgers for multiple users. Typical in Shared Service Center
environments.
Accessing the same Business Units across multiple functions. e.g. AP Manager w/ Procurement Inquiry access
Custom roles can be introduced to combine the 2 accesses, eliminating the need for one set of the data roles
Implement this as last resort as we are moving away from generated data role model.
General Ledger’s Data Access Sets can be used to grant access to a group of ledgers. While a new Data Access Set is
automatically created whenever a new Ledger is created, you can create your own Data Access Sets.
A user may need to access data in a large number of Business Units / Ledgers / etc. The most straightforward way is to
assign all the corresponding data roles (1 data role per Business Unit / Ledger).
By default, users are denied access to all data.
Use only the predefined duty roles, unless you have added new applications functions. The predefined duty roles fully
represent the functions and data that must be accessed by application users and contain
all appropriate entitlement. The predefined duty roles are inherently without segregation of duty violations of the
constraints used by the Application Access Controls Governor.
Review but do not modify HCM data security policies in APM except as a custom implementation. Use the HCM Manage
Data Role And Security Profiles task to generate the necessary data security policies and data roles.
Don’t Assign Job Roles AND corresponding Data Roles. There is no need to separately assign the job role to the user if
you are assigning the corresponding data roles. Only assign job roles directly for job roles that don’t utilize data roles to
provide data security. Examples include Cash Manager, Application Implementation Consultant.
You must not customize predefined roles. You can identify these predefined roles by the ORA_ prefix in the Role Code
field. During each upgrade, predefined roles may be updated to the specifications for that release, so any
customizations would be overwritten.
Copy Predefined Roles before Customizing. Copy Role and Compare Roles are supported in the Security Console.
Don’t Customize Predefined Privileges. During each upgrade, predefined privileges may be updated to the specifications
for that release, so any customizations would be overwritten.
Avoid Creating Custom Privileges. Resources are designed to work as a cohesive unit, granted via predefined privileges.
Granting only a subset of these resources to a user may result in unexpected and erroneous behaviors.
If the Employee and Contingent Worker roles are provisioned automatically, pending workers acquire them when their
periods of employment or placements start. If they need roles before then, you create a separate role mapping for the
pending worker system person type.
It’s Easier to Add than to Remove. You can always add more privileges to a role while isolating the predefined content,
but you cannot remove privileges from a role without modifying the predefined content.
If you need to add more privileges to a predefined role, group all the added privileges in one or more custom duties, and
then assign the custom duties to the job role.
Consider Segregation of Duties when creating Custom Roles.
Don’t Grant Resources Directly to Roles. Granting resources directly to roles complicates auditing.
In general, assigning a large number of roles to a user might impact performance, particularly when the system needs to
check the authorization policies for the user.
There is no need to assign these incremental roles to the same user; assigning the role with the most access is sufficient.
For example: in Fusion General Ledger, General Accountant includes all capabilities granted to Financial Analyst, and
General Accounting Manager includes all capabilities to granted to General Accountant.
Use Security Console to customize security instead of APM whenever possible.
Use Draft Accounting to test accounting rule changes. Draft accounting means that a set of representative transactions
can be used over and over again to refine and test accounting rule changes
Use Substitute Accounts to prevent delays at month end. Substitute accounts help prevent delays at month end when
disabled segments (for example, cost center) come through on source transactions. When SLA builds an account
combination in the accounting program that is disabled and assigned a substitute combination, SLA uses the substitute
combination for the journal line. It also stores the original combination derived by the account rule for audit purposes.
Use multiple Create Accounting Workers to improve accounting program performance.

The SLA Accounting Program is inherently multi-threaded. Running multiple workers allows the accounting program to
take advantage of multi-processor environments to improve performance. You can define the number of workers that
will process an application’s accounting events in the Create Accounting Processing Option. The optimal number of
workers will depend on a number of factors including transaction volume and transaction complexity.
Use seeded accounting rules as the basis for your own rules
Using seeded journal entry rule sets has the advantage that only components (journal line rules, account rules etc.) that
are modified are not supported by development. All components that are unchanged are shared with seeded rules and
continue to be supported / upgraded automatically.
Make Accounting Rules more user friendly

This applies only to external feeds. When transaction and reference data objects are imported into FAH, the source
name is, by default, the column name. The source name should be changed to be more user friendly (mixed case, etc.)
and, if appropriate, associated with a lookups or value set. Lookups or value sets are useful for sources that contain
“codes” for the following reasons:
(1) In accounting rules, a LOV is displayed to users (for example, in a condition where “Source Name is equal to Value”,
the user will be presented with a LOV of possible values – and the meaning / description will be displayed instead of the
lookup code.
(2) In description rules, the LOV meaning / description is included in place of the code. For example, a source which
contains “Y” which is associated with a “Yes / No” lookup will display “Yes” in a description that uses the source.
Best practice is to implement separate source systems as separate Subledger applications. Factors to take into account
include:
(1) Subledger Applications offer a degree of autonomy for definition and maintenance of setups. If the accounting rules
are to be defined and maintained by different owners, then it will be easier if they are in separate Subledger
applications.
(2) Most Subledger Application data is stored in separate database partitions which facilitates processing independence
and improved performance. However, Subledger Accounting Method components (for example, Account Rules) are,
generally speaking, not shared across applications. If distinct source systems generate transactions that should be
subject to a single, (i.e. shared) set of accounting rules (for example, there are two source systems that deal in bonds),
then it will be easier if they are defined in a single Subledger Application.
Use OTBI for ad hoc reporting requirements. BI Publisher for high volume, highly formatted reports.
OTBI is the standard solution for ad hoc transactional reporting. Users can define their own queries using predefined
business views. SLA delivers two OTBI subject areas: Subledger Accounting – Journals Real Time and Subledger
Accounting – Supporting References Real Time.
BI Publisher is the standard solution for pre-defined, high volume and highly formatted transactional reports. Report
analysts can author, manage, and deliver all types of highly formatted documents by copying existing report templates
and modifying them using Microsoft Word or Adobe PDF. SLA delivers several BI Publisher data models and example
templates including Subledger journal line level Account Analysis, Journal Book and Third Party Control Accounts.
When address elements are needed for tax purposes, such as country and city for US Sales and Use Tax, set these
address levels as mandatory within Trading Community Model geography. This ensures that these elements are always
present on all applicable addresses.
While setting up the transaction business categories, use different levels so that you can define all of the necessary tax
rules at the highest level possible. This facilitates in minimizing the needed number of tax rules. Specify the country
name while creating business categories to improve searching.
While setting up the document fiscal classification, use different levels so that all the necessary rules are defined at the
highest level possible. This facilitates in minimizing the needed number of tax rules. Specify the country name while
creating business categories to improve searching.
Use the highest level of geography, typically country, wherever possible.
Once you select a feature (Recovery, Exceptions, Offset) for a tax regime, you cannot disable it. You can enable the
feature later if you do not enable it initially for a tax regime.
Create a generic tax zone so that you create a tax zone type that can be used in multiple situations
You can also use the tax zone functionality to group postal codes to provide useful groupings that can identify some
higher-level tax regions such as, cities or counties.
Do not use these types of words as dimension or member names: Calculation script commands, operators, report writer
commands, function names, generation names, level names.
Best Practice: Log an SR (at least 1 week or more in advance of testing) to request a “QA heath check” for your AP
invoice scanning service prior to go-live.
Note: Do NOT use periods, dashes, commas or special characters in your Business Unit Name, such as ABC Co.-BU. This
causes issues generating data roles. For more information, see MOS Note: Cannot Verify Data Role Generation For
Business Unit with Name Containing Special Characters (Doc ID 1632528.1).
Cross Validation Rules are used if you have Dynamic combination creation allowed for your chart of accounts and want
to prevent certain combinations of segment values from automatically being created during data entry.
If you do not enable Dynamic combination creation allowed, then you must upload all the different account
combinations that you want your users to use.
Note: In practice, most users tend to use consolidated spreadsheets like the Tax Configuration Workbook and Tax
Implementation Workbook to efficiently manage their initial and recurring tax setups.

Oracle ERP Cloud Guided Path and Best Configuration Practices - Financials Jan 2017

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

Oracle ERP Cloud Guided Path and Best Configuration Practices - Financials Jan 2017

Uploaded by

Copyright:

Available Formats

Oracle ERP Cloud Guided Path and Best Configu

Applies to Oracle Fusion Cloud Financial Produc

PLEASE READ THIS PAGE FIRST

Scope & Assumptions

Copyright 2016, Oracle and/or its affiliates. All rights reserved.

on Cloud Financial Products and current GA releases.

may be trademarks of their respective owners.

Establish Project Scope, Objectives and Approach

Finalize Project Plan and Key Milestones/Deliverables

Perform Security, Reporting, Integration & Data Conversion Workshops

Perform Delivered Content Reviews and Mapping

Conduct Implementation Checkpoint (Planning)

Create Enterprise Structures and Functional Setups

Configure OOTB Security, Approvals, Notifications, Reports & Integrations

Conduct Functional Review and Validation Test - CRP 1 & 2

Map delivered Business Process Models to high priority processes

Develop, Test and Deploy Complex Integrations

Migrate Critical Historical Data

Develop, Test and Deploy High Priority Extensions

Load & Validate Data

Develop, Test and Deploy Critical Custom Reports

Validate Production Environment Configuration

Assess Solution Readiness

Obtain Final Cut Over Approvals

Perform User Acceptance

System Requirements for Oracle Application Cloud

Oracle Enterprise Resource Planning Cloud Service Implementation Leading Practices

Minimum Steps for Financial Enterprise structures and GL Setup

Configurations, Extensions, Reports, Security, Environment, Interfaces

Functional Setup Manager (New Compare Feature)

Best Practice: Cut Over Plan Developed and Approved

Upgrade guide for Oracle Cloud Applications Security

Link Checklist Customer, SI

Link Whitepaper Customer, SI

Link MOS Note Customer, SI

Link MOS Note Customer, SI

OUM Checklist Customer, SI

Link MOS Note Customer, SI

OUM Checklist Customer, SI

Link Whitepaper Customer, SI

Included in Oracle Cloud Featured White Papers on cloud.oracle.com

Simplified Business Process Maps

Purchasing, Self Payments,

Certified SI partners can leverage additional guidance in OUM, if needed.

Certified SI partners can leverage additional guidance in OUM, if needed.

Purchasing, Self Service Procurement, Sourcing, Supplier Portal/Supplier Model

Certified SI partners can leverage additional guidance in OUM, if needed.

Certified SI partners can leverage additional guidance in OUM, if needed.

Master Document for ERP Upgrade Guidance

Approval Management (AMX)

Approval Management (AMX)

Approval Management (AMX)

Approval Management (AMX)

Approval Management (AMX)

Budgeting and Planning

Functional Setup Manager

Functional Setup Manager

Functional Setup Manager

Integration with Financial External Systems

Payables & Payments

Payables & Payments

Payables & Payments

Payables & Payments