Oracle ERP Cloud Guided Path and Best Configuration Practices 2018 - R13 Final

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

Version: 2.0 Last Updated: 1-Aug-18
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
expand upon existing resources, the following workbook has been created to a "guided" experience for your ERP Cloud
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 2018, 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.
n 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 and
" 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
ng 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 Activity
Service Startup
Project Design
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 Worksh
Perform Delivered Content Reviews and Mapping
Conduct Implementation Checkpoint (Planning)

Configure
Create Enterprise Structures and Functional Setups
Import Demographic/Indicative Data and Transaction History
Configure OOTB Security, Approvals, Notifications, Reports & Integra
Conduct Functional Review and Validation Test - CRP 1 & 2

Map delivered Business Process Models to high priority processes
Conduct Implementation Checkpoint (Design)
Validate
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
Transition
Validate Production Environment Configuration
Migrate Functional Setups from Test to Production
Migrate/Configure Security and OOTB Reports & Integrations

Assess Solution Readiness
Realization
Obtain Final Cut Over Approvals
Conduct End-User Training
Perform User Acceptance

Assess Operational Readiness
Go-Live
Updates
Prepare
Execute
Complete
Artifacts
Getting Started with Your Implementation

System Requirements for Oracle Application Cloud
Browser Best Practices
SaaS Cloud Delivery Policies
Oracle Financials Cloud Intro for CFOs and SIs
Modern Business Processes for Finance
Service Administrator Action List
Oracle Enterprise Resource Planning Cloud Service Implementation Leading Practices

Introductions to Oracle Cloud Financials
Has the customer formally approved the project plan?
Welcome to Fusion ERP Cloud Applications - Getting Started
Oracle Financials Cloud: Enterprise Structures
Oracle Fusion General Ledger Hierarchies: Recommendations and Best Practices
Oracle Financials Cloud: Shared Service Centers (SSC)
Cloud Known Issues and Update
Best Practice: CRP or Prototyping to gather/validate requirements
Information Center: Fusion Applications BI & Reporting - Essbase and Financial Reporting
Introduction to External Data Integration
SOAP Web Services for Oracle Cloud Financials
REST Web Services for Oracle Cloud Financials
Oracle Financials - View Financials Reports and Analyses
Best Practice: Data Conversion Plan
Best Practice: Integration Plan
Security Reference for Oracle Common Features
Security Reference for Oracle Financials Cloud
Cloud Application Security Architecture and Configuration: Role Privileges
Functional Setup Manager
Logical & Relational Data Model Diagrams
Financials Cloud Delivered Reporting
Steps to set up Financial Reporting Center, Smart View in Oracle ERP Cloud
Oracle Integrated Invoice Imaging Guide for Cloud
Setup Instructions for Printing from Oracle Cloud
Cloud Security: Federated SSO for Fusion-based SaaS
Information Centers: General Ledger, Expenses, Receivables, Sub Ledger Accounting, Procurement, PPM.
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 Implementation for Financials
Rapid Implementation for Procurement
Rapid Implementation for Project Portfolio Management
Configure Basic Enterprise Structure for Procurement ( Shared Service)
Rapid Implementation Troubleshooting Guide

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)
Information Center: Oracle Fusion Applications - Fusion Security
Information Center: Fusion Applications BI & Reporting - Essbase and Financial Reporting
Using External Data Integration Services for Oracle ERP Cloud

Oracle Fusion Applications Extensibility Guide for Developers
Financials Report Sharing Center
Idea Lab - Financials
Execute Enterprise Structures Setup Report

Diagnostic Tests for Fusion Procurement
Diagnostic Tests for Fusion Financials
Diagnostic Tests for Fusion Project Portfolio Management
Troubleshooting Guides:
Troubleshooting Financials
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
Troubleshooting Guide for Intercompany Transactions
How to Get the Most from Fusion Applications Diagnostic Logging

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 data
scheduled,
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?
All UAT test scripts executed and differences explained.
Have all open issues been assigned to a specific party to resolve (SI, Oracle, Customer)?
My Oracle Support Resource Center
Has the list of Open SRs been prioritized 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)
Create a resizing request for Production environment. Note: this requires a 4 week lead time.
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 yes,
if some
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
Troubleshooting Assistants
Request a Production-to-Test entitlement to sync up Test environment(s) with Product environment after
go-live.
Release Readiness
Sample Upgrade Project Plan
Oracle Cloud Applications Removal of Functionality or Features
Subscribe to Oracle Cloud Customer Connect: Idea Lab and Shared Reporting Center
Oracle Applications Cloud Service Entitlements

Lessons Learned
Location Type Target Audience
Link Oracle Help Center Customer, SI

Link Checklist Customer, SI
Link Checklist Customer, SI
Link Document Customer, SI
Link Whitepaper Customer, SI
Link Oracle.com Customer, SI
Link MOS Note Customer, SI

Link Oracle University - Learning Subscriptions Customer, SI
OUM Checklist Customer, SI
Link MS Excel Spreadsheet Customer, SI
Link Oracle Blog Customer, SI
Link Oracle A-Team Blog Customer, SI
Link MOS Notes Customer, SI





Link Oracle Cloud Customer Connect Customer, SI
Link Oracle Cloud Customer Connect Customer, SI

Link Information Center (MOS) Customer, SI



Link Oracle Blog SI








Link MOS Document Customer, SI
Link Website Customer, SI

Link Oracle Cloud Customer Connect Customer

Comments
Included
Customers in are
Oracle Cloud
advised Featured
not White
to assume thatPapers on cloud.oracle.com
a platform, device, or release is supported if it is not
listed on this site. Please contact Oracle Support if you have any questions.
Provides guidance
Documentation on how to
of Oracle's execute
and a speed
Customer's test for your for
responsibilities browser.
Oracle Cloud Service.
Recommended reading for Cloud Service Administrators and Cloud Account Owners.
Included in MOS Doc Key White Papers and Articles for Oracle ERP.
Simplified Executive
Perform these Business
critical tasks Process
as soonMaps
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

Select the Getting Started and Onboarding Channel (Free).
The purpose of this document is to provide you, the Service Administrator, and your
Certified SI partners
implementation teamcan leverage
with links toadditional
materialsguidance in OUM,
to help you if needed.
get started with your implementation
Describes
of the theERP
Oracle bestCloud
practices
Serviceof maintaining and publishing the account hierarchies. Account
Overview
hierarchies are used throughout Oracle Fusion General Ledger for creatingcommon
of the principal Oracle Cloud Applications enterprise structures financialto all
reports,
product
Smart families
View ad hoc including charts
inquiries, of accounts, ledgers, business units and legal entities.
This document is intended toallocation
offer high definitions, cross
level guidance validation
about rules, and
how different revaluation
enterprise
definitions.
structures and transaction processing features can be brought together to meet common
shared service center scenarios.
Covers both Cloud Updates and Functional Known Issues.
Certified SI partners can leverage additional guidance in OUM, if needed.
News,
ContainsAnnouncements and Latest
overview for external datapublications
integration from MOS.
services for ERP and integration with Financial
external systems: point to consider
List of all SOAP web services for Oracle Cloud Financials
List of all REST web services for Oracle Cloud Financials. Oracle is moving from SOAP to REST.
List of all OOTB Reports and Analyses with report samples
Out-of-the-box seeded roles for cloud service administration.
Out-of-the-box seeded roles for financial users.
Simply
Highlightthethe
best one-stop-shop
features for allSetup
of Functional thingsManager
applications security.
that can be used to make the migration of
reference data as smooth as possible.
Logical Data Model Diagrams for Oracle ERP Cloud
Guidance on running reports and inventory of delivered reports.
Scanner
Overview, Specifications
How it works,forConfiguration
Invoice Imaging To Automatically Scan And Capture Payable Invoice
In Oracle Fusion Cloud. Also provides additional knowledge resources for scanner
configuration. Best practice is to reference this guide before Implementation Automated
Imaging Processing
The purpose of this document is to assist Fusion Applications customers with printing directly
from the cloud to a on premise printer
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
Single MOS portal for most up-to-date high impact and urgent issues and MOS documents for
your products. Search MOS knowledge base with the convention "Information Center: %"
where % is the Fusion product name.
How to set up Financial Enterprise Structures and General Ledger with the minimum steps.
Search knowledge base in MOS with the convention "How to Oracle Fusion %" where % is the
product (i.e. General Ledger, Payables, etc.). Compliments the content available in the Oracle
Implementation Guides and Oracle Fusion Applications Implementation and Help Center.
Rapid Implementation for General Ledger workbook template to rapidly implement the
common setup objects for core financials.
Procurement rapid implementation task list to implement the Procurement offering if your
organization has simple setup requirements. The task list reduces the number of tasks to those
which are required or commonly used.
Financials Project rapid implementation task list to implement the Financials Project offering if
your organization has simple setup requirements. The task list reduces the number of tasks to
those which are required or commonly used.
Set up for an enterprise with several lines of business, operating in several jurisdictions, and
whose sourcing and procurement transactions are conducted through a shared service center.
Troubleshooting guide for known issues found while using Financials Rapid Implementation
spreadsheet.
Inventory list of all File-Based Data Imports for Oracle Financials Cloud.
This MOS article provides guidance on how to verify Oracle ERP Cloud Service data conversion
results
Initiallyfor most for
created common
Releaseconversion
9 but still items.
applies for today. Discusses the best practice of role
mapping for application security configuration.
View the most up-to-date high impact and urgent issues for Fusion Security. Includes most
popular knowledge documents and community discussions.
View the most up-to-date high impact and urgent issues for Financial Reporting. Includes most
popular
This paperknowledge
describesdocuments
how to useand community
External discussions.Services for Oracle ERP Cloud to
Data Integration
load data into Oracle Fusion Applications from external sources, such as legacy systems and
third-party applications.
Customize and extend the standard functionality provided by Oracle Fusion Applications.
Shared Financials reports available to all customers.
Idea Lab allows you to contribute to our product roadmap.
Validate your enterprise structures configuration using the Enterprise Structures Setup Report.
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 Performance Reporting, Project Summarization, Project Contract Summarization
MOS Troubleshooting Guides - One Stop Shop.
Complete guide of Oracle Financials Cloud diagnostic tests.
Purpose of this document is to list some of the common errors seen when using a cloud printer
and solution to these issues.
Purpose of this document is to list some of the common errors and FAQ for Invoice Scanning.
This document describes troubleshooting tips for the intercompany transactions flow.
This document explains how to understand and leverage the application logging configuration
and processes that occur in Fusion Applications. Complements the Fusion Applications
Administrators Guide.
Business Process Maps in Visio.

(Fusion Apps Dev Relations Blog) – Developer Focused
Developed for Release 12 but still applies for Release 13.
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
If a P2T is performed then best practice is to rerun in Test environment after refresh.
Key resources for utilizing Oracle Support.

After transfer you should perform a compare between function setup in Test vs Production
Resize your environment configuration to provide optimal performance for both your planned
number of users and your Oracle Applications Cloud services.
Re-use configuration to create additional setup within the environment but also to be able to
copy reference data to the production environment to save time and increase productivity.
Production cutover best practice - validation configurations.
Document describes how to get a report that lists all users and their assigned roles. This report
is not seeded in Oracle Fusion Applications. This should be performed after user setup to
confirm configuration in Production.
Step-by-step instructions on how to migrate Flexfields
Step-by-step instructions on how to migrate BI migration - apply to both HCM and ERP.
How a user can make use of BI Publisher functionality to run a SQL query against the Fusion
Applications Database and review the result set. May be required for Production configuration
validation.
This checklist document has been created to help our customers as they get ready to go-live
This document will walk the user through the steps to collect initial information regarding
Performance issues in Fusion Applications.

This whitepaper provides guidance on the period-end close procedures for Oracle Cloud
Application modules, across Financials, Procurement, Projects, Inventory, and Payroll.
Intercompany Checklist
Functional checklist
Interactive guide to troubleshoot Payables disbursements, Expense reports, and process

payment files. Search the MOS knowledge base with the convention Troubleshooting
Assistant".
Environment Refresh is the service entitlement that you should request to migrate data from a
source environment to a target environment.
Spotlights, New Feature Summary, What's New, Readiness Training, Documentation for
quarterly update.
Detail Upgrade Plan for Quarterly Updates.
Pursuant to the Oracle Cloud Enterprise Hosting and Delivery Policies (Section 5.2) Oracle is
giving notification that the features referenced in this document will be removed from future
versions. Oracle makes commercially reasonable efforts to post notices of feature deprecations
one quarter in advance of their removal
Learn and share from the Oracle Cloud customer community.

This article provides an overview of the technical services, such as environment refresh and
environment resizing, that you can request for your Oracle Applications Cloud.
Module Component
Advanced Collections Scoring formula
Advanced Collections Scoring formula
Allocation Manager Calculation Manager
Allocation Manager Intercompany Allocations

Application Toolkit Watchlist
Approval Management (AMX) All Approvals
Approval Management (AMX) Amount-Based Approvals
Approval Management (AMX) Approval Groups
Approval Management (AMX) DFF-Based Approvals
Approval Management (AMX) Non-Amount approval rules
Approval Management (AMX) Supervisory Hierarchy-Based Approvals
Budgeting and Planning Loading Budgets

Cash Management Ad Hoc Payments
Cash Management Automatic Reconciliation
Cash Management Bank Accounts

Cash Management Bank Statement Formats
Cash Management Banks, Branches and Accounts
Cash Management CM Cube Management
Cash Management Importing Bank Statements
Cash Management Intraday Statements
Cash Management Parse Rule Sets
Cash Management Reconciliation Rule Set
Cash Management Reconciling Bank Statements

Cash Management Transaction Codes
Cash Management Transactions from 3rd Party
Cash Management Transmission Configuration
Cash Management Transmission Protocols
Enterprise Excel Data Templates
Enterprise Item Master
Enterprise Item Master
Enterprise Outbound Integration

Enterprise Structures Currency
Enterprise Structures Currency
Enterprise Structures Document Sequence
Enterprise Structures Document Sequence

Enterprise Structures Flexfields
Enterprise Structures Legal Entity

Enterprise Structures Languages
Common Features Profile Options
Common Features Profile Options
Enterprise Structures Reference Data
Enterprise Structures Setup Report
Enterprise Structures Tree Structure

Expenses Approval Rules

Expenses Audit
Expenses Audit
Expenses Audit
Expenses Audit
Expenses Expense Categories
Expenses Expense Tolerances
Expenses Expense Types
Expenses Travel and Policies
Expenses Travel Data Quality
Financial Reporting Financial Reporting Center
Financial Reporting Financial Reporting Center
Financial Reporting Smartview
Financial Reporting Account Monitor

Financial Reporting Account Monitor, Account Inspector, and Sunburst
Financial Reporting BI Publisher
Financial Reporting Financial Reporting in the Financial Reporting Center
Financial Reporting OTBI
Financial Reporting Smartview
Fixed Assets Asset Book
Fixed Assets Asset Book
Fixed Assets Asset Category

Fixed Assets Asset Category
Fixed Assets Asset Corporate Book
Fixed Assets Transfers
Fixed Assets Asset Locations
Fixed Assets Asset Locations
Fixed Assets Calendar Periods

Fixed Assets Calendar Periods
Fixed Assets Close Period
Fixed Assets Create Accounting for Tax Books

Fixed Assets Fiscal Year
Fixed Assets Loading Fixed Assets
Fixed Assets Payables to Assets
Fixed Assets Payables to Assets
Functional Setup Manager Implementation Projects
Functional Setup Manager Implementation Users
Functional Setup Manager Implementation Users
General Ledger Account Combinations
General Ledger Account Combinations
General Ledger Account Groups
General Ledger Account Segment
General Ledger Accounting Calendars

General Ledger Adjusting Ledger

General Ledger Adjusting Periods
General Ledger Approval Rules
General Ledger Approving Journals

General Ledger Auto Reverse
General Ledger Balancing Segments
General Ledger Budget Uploads
General Ledger Budget Uploads
General Ledger Business Unit

General Ledger Chart of Accounts


General Ledger Close Monitor
General Ledger Closing Journals
General Ledger COA Value Loading

General Ledger Company
General Ledger Cost Center Segment
General Ledger Cross Validation Rules

General Ledger Essbase
General Ledger Essbase Cube
General Ledger Financial Close

General Ledger Future Segments
General Ledger GL Balance Cube
General Ledger Hierarchy


General Ledger Intercompany Segment
General Ledger JE Rules Sets
General Ledger Journal Batches
General Ledger Create Accounting and Post Journals

General Ledger Journal Entry
General Ledger Journal Import Process

General Ledger Journal Import Process
General Ledger Journal Lines
General Ledger Journals Upload Spreadsheet
General Ledger Ledger
General Ledger Ledger
General Ledger Ledger Set
General Ledger Period
General Ledger Project Segments
General Ledger Reporting Security
General Ledger Reversing Journals

General Ledger Secondary Ledger
General Ledger Segment
General Ledger Segment Security

General Ledger Segment Security Roles
General Ledger Translation
General Ledger Value set
General Ledger Year-end Processing - Close Out for Specific Industries
General Ledger Year-end Processing - Close Out Retained Earnings
Integration with Financial External Systems Foreign Exchange Rates
OBIEE Page Display (# of Rows)
OTBI COA Segments
OTBI Subject Areas
OTBI Subject Areas

OTBI Subject Areas
Payables & Payments Immediate Payment vs Scheduled Payment
Payables & Payments Immediate Payment vs Scheduled Payment
Payables & Payments Invoice Creation
Payables & Payments Invoice Groups

Payables & Payments Invoice Imaging



Payables & Payments Invoice Tolerances
Payables & Payments Payables Cash Requirement Report

Payables & Payments Payables Unaccounted Transactions and Sweep Report

Payables & Payments Payment Process Request Template
Payables & Payments Payment Validations
Payables & Payments Payment Validations

Planning and Budgeting Control Data Sync
Receivables Activity GL Accounts
Receivables Business Unit
Receivables Intercompany Balancing Rules
Receivables Manage Reference Data Sets

Receivables Open Account Period
Receivables Receivables to Ledger Reconciliation Report
Receivables Receivables to Ledger Reconciliation Report
Security Data Roles

Security Data Security
Security Duty Roles
Security Job Roles

Security Predefined Roles
Security Privileges
Security Privileges
Security Provisioning Security
Security Roles
Security Roles
Security Roles
Security Roles
Security Roles
Subledger Accounting Accounting Program
Subledger Accounting Accounting Rules

Subledger Accounting Accounting Rules
Subledger Accounting External Feeds
Subledger Accounting Reporting
Transaction Taxes Addresses
Transaction Taxes Business Categories
Transaction Taxes Fiscal Classifications

Transaction Taxes Tax Geographies
Transaction Taxes Tax Regime

Transaction Taxes Tax Zone
Transaction Taxes Tax Zone

Enterprise Essbase
Transaction Taxes Tax Setup
Project Foundation Project Calendars and Periods

Project Foundation Project Types and Categories

Project Foundation Expenditure Type Classes
Project Foundation Service Type
Project Foundation Work Type
Project Foundation Project Types

Project Foundation Project Templates
Project Costing Planned Dates
Project Costing Project Costing Flexfield(s)
Project Costing Project Costing Flexfield(s)
Project Costing Multipliers on Burden Structures

Project Costing Accounting Methods
Project Costing Accounting Methods
Project Costing Accounting Rules
Project Costing Accounting Rules
Project Contracts Contracts
Project Billing User-Defined Invoice & Revenue Methods
Project Billing Invoice Work Area
Project Billing Manage billing transaction exceptions
Project Billing Project Type
Project Billing Billing Indicator on Work Type
Project Billing Event Types
Budgetary Controls Tree Labels
Project Financial Management Control Budget Names
Project Foundation Projects Business Unit

Project Foundation Project Expenditure Organization
Project Foundation Person Rate Schedules
Project Foundation Planning Resource Breakdown Structure
Project Foundation Planning Resource Breakdown Structure

Project Foundation Project Type
Project Financial Management Separate Line Burdening
Project Financial Management Set
Project Financial Management Revenue Method
Project Execution Management Project Roles
Project Execution Management Labor Resource

Project Execution Management Labor Resource
Project Execution Management Project and Task Codes
Project Execution Management Resource Pool

Project Execution Management Project Number & Name

Revenue Management Standalone Selling Prices (SSP)
Revenue Management Contract Identification Rules
Revenue Management Performance Obligation Templates
Revenue Management Selling Prices

Revenue Management Item Group
Revenue Management Implementing IFRS 15/ASC 606
Fixed Assets Asset Clearing
General Ledger Beginning Trail Balance

Receivables Manage Customer
Receivables Rapid Implementation
Receivables Rapid Implementation

Receivables Cash Management
Receivables Document Sequence
Revenue Management Contract Identification Rules
Revenue Management Performance Obligation Identification Rules
Revenue Management Standalone Selling Prices (SSP)

Revenue Management Account Derivation
Revenue Management Extracting Data from Revenue Management

Best Practice Type
Configuration
Configuration
Performance
Configuration
Caution
Performance
Configuration
Configuration
Configuration
Configuration
Configuration
Caution
FYI
Maintenance
Configuration
Configuration
Configuration
Configuration
FYI
FYI
Data Conversion
FYI
Caution
FYI
Configuration
Configuration
Caution
Configuration
Configuration
Configuration
FYI
Caution
Configuration
Configuration
Performance
Caution
Caution
Caution
Performance
Caution
Configuration
FYI
Configuration
Configuration
Configuration
Validation
Configuration
Caution
Validation
Performance
Validation
Validation
Configuration
Configuration
Configuration
Validation
Validation
Caution
Configuration
Validation
Configuration
Configuration
Caution
Configuration
Maintenance
Maintenance
Maintenance
Maintenance
Maintenance
Configuration
Configuration
Configuration
Configuration
Configuration
Caution
Configuration
Configuration
Configuration
Configuration
Caution
Validation
Configuration
Configuration
Configuration
Configuration
Configuration
Validation
Configuration
Maintenance
Performance
Configuration
Caution
Configuration
Caution
Configuration
Configuration
Performance
Configuration
Configuration
Configuration
Configuration
Configuration
Configuration
Caution
Configuration
Configuration
Caution
Configuration
Validation
Caution
Configuration
Caution
Configuration
FYI
Caution
Configuration
Configuration
Configuration
FYI
Configuration
Configuration
Configuration
Configuration
Configuration
Caution
Maintenance
Caution
Configuration
Configuration
Validation
Validation
Configuration
Performance
Performance
Performance
Configuration
Configuration
Configuration
Configuration
Configuration
Configuration
Caution
Validation
Validation
Caution
Configuration
Configuration
Caution
Configuration
Performance
Configuration
Configuration
Caution
Configuration
Maintenance
FYI
Caution
Configuration
Configuration
Configuration
Data Conversion
Caution
FYI
Caution
Caution
Caution
Performance
Performance
Caution
Caution
Configuration
Caution
Configuration
Configuration
Caution
Caution
Configuration
Caution
Configuration
Validation
Caution
Configuration
Configuration
Caution
Configuration
Maintenance
Maintenance
Maintenance
Configuration
Caution
Caution
Caution
Caution
Caution
Configuration
Maintenance
Caution
Configuration
Configuration
Caution
Configuration
Configuration
Configuration
Configuration
Validation
FYI
Configuration
Configuration
Configuration
Caution
Configuration
FYI
Validation
Caution
Configuration
Validation
Configuration
Maintenance
Maintenance
Maintenance
Maintenance
Configuration
Validation
Caution
Configuration
Caution
Caution
Configuration
Caution
Caution
Caution
Configuration
Configuration
Caution
Configuration
Configuration
Performance
FYI
Configuration
Configuration
Configuration
Caution
Caution
FYI
Caution
Configuration
Configuration
Caution
Performance
Validation
Configuration
Performance
Configuration
Configuration
Configuration
Configuration
Configuration
Configuration
Configuration
Configuration
Caution
Configuration
Configuration
Caution
Validation
Caution
FYI
Caution
Configuration
Configuration
Configuration
Configuration
Configuration
Caution
FYI
FYI
FYI
FYI
Configuration
FYI
Caution
Caution
FYI
Caution
FYI
Configuration
Configuration
Configuration
Configuration
Maintenance
Maintenance
FYI
FYI
FYI
Caution
Maintenance
FYI
Configuration
FYI
Caution
FYI
Caution
Caution
FYI
FYI
FYI
FYI
FYI
Caution
FYI
Caution
Caution
Caution
FYI
Configuration
FYI
FYI
Configuration
Configuration
Configuration
Data Conversion
Configuration
Configuration
Configuration
Configuration
Configuration
Caution
Caution
Caution
FYI
FYI
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.
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 the ISO20022
Note: Our load process is designed to support all versions of 53.001).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 statement into 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 in 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.
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".
Oracle Financials Cloud 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.
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 Business Unit. 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 a 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 depreciation 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.
Execute the "Optimize Journal Import Performance" to ensure optimal performance of loading journals into Oracle
Financials Cloud. It should be run after the COA configuration is completed and before or after large initial journal
uploads. Once in production it doesn't need to be run very often however, note that, other than the time it takes to run
which should not coincide with journal import, posting etc., there is no issue with re-running it.
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 (Budgetary control only, Start Date, Period Frequency, Adjusting Period Frequency, Period
Name Format) 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 primary 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. Best configuration practice is that Business Units should not
cover multiple countries.
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 Financials Cloud service.
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 Functional Setup Manager.
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.
With this approach, 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 are 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.
Schedule to run Create Accounting and Post Journals on a daily basis to get up to date Financial reports and identifying
any exceptions.
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 can 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.
Secondary ledger created at a later date does not get past data from the primary ledger. Create a secondary ledger at
the same time as Primary if required in future.
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. 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 additional balancing
segments (ex. 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 from Oracle Cloud Marketplace 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 areas
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 are 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 to 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. Note: You will need to log a Service Request to set additional language support, PO number
formatting or to turn off PO number formatting if Procurement is not being implemented. It is best practice to disable
PO recognition if Procurement is not being implemented, it can always be reenabled later if procurement is
implemented.
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.
If paper invoices are being manually scanned and emailed - 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 and you can also use the Imaging Audit Report.
Refer to MOS note 2210741.1 for instructions on how to install and use this on demand audit report.
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. Note: This is not to be confused with applying settings such as language
support, currency support, PO Recognition, etc. Out of the box Imaging only supports English and USD but can be set to
other supported languages and currencies by logging a service request.
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. Support can provide that for you or you can provide your own. Just log a service request.
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 must contain a supplier address. Suppliers are matched based on the supplier address
available on the Image for Non-PO invoices. The Supplier should have the same exact address on the invoice that is
setup in Fusion for that Supplier for that site. Suppliers are valid only when they have active pay sites and site
assignments. If there is an exact match between the address on the invoice and the address set up on the supplier, you
will have a much better recognition success rate.
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 local 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, bill of
lading number could be picked up as the PO number and if that is recognized as a valid PO number then you match and
pay an incorrect supplier.
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. You will need to log a service request to set
the PO number format.
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 (IPM) to check for the invoice. IPM and the Imaging Audit Report are
the most useful tools for trouble shooting. You but should not need to use IPM post go-live but you can use the Audit
Report any time as it is an on-demand report that will give you the status of all imaged invoices from the time it is
emailed into imaging until it hits AP under the Scanned Infotile.
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 Scanned 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 for configurations. 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,
they are reconciled separately.
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 roles. 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.
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.
Copy Predefined Roles before Customizing. Copy Role and Compare Roles are supported in the Security Console.
Don’t Customize Predefined Privileges. During each quarterly update, 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 customer-specific Segregation of Duties requirements 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.
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.
Best practice is to maintain common accounting and project accounting periods. This will minimize configuration
maintenance. It is however, quite common for customers - who want to report project information more frequently - to
define project accounting periods that are shorter than the accounting periods: In this case, it is best practice to
synchronize the periods so they do not overlap. A good example of this is customers with a weekly project accounting
period and 4-4-5 week pattern of accounting periods. Note: Project accounting periods are used by Project Financial
Management applications for project planning, budgeting, costing, forecasting, billing, and performance reporting.
Create revenue categories to group expenditure types and event types for revenue recognition
Assign one revenue category to each expenditure type and event type.
Create expenditure categories to group expenditure types. Use expenditure categories for
budgeting, transaction controls, when you define organization overrides, and in accounting rules and reporting.
.
If you save an expenditure type, you cannot subsequently update the following attributes:
• Expenditure and revenue categories
•Unit of measure
• Rate required option
•Expenditure type class
Controls which expenditure types are available when entering a transaction.
Use the service type value at the task level as a source in Oracle Fusion Subledger Accounting to derive accounts.
Utilize Work Type to indicate if work is billable or nonbillable. Work Type derived from Expenditure Item Type.
Project types are used to default eligible work type, billing option, capitalization options, classifications, burdening
options and reference set for a specific project instance.
Utilize project templates to quickly create projects that share common features, attributes, and options.
Note: Planned date options are disabled if you decide to use third-party scheduling.
Project Costing flexfields do not change their behavior across Ledgers unlike Accounting chartfields.
Project Costing flexfields do not have account shorthand alias feature unlike Accounting chartfields.
Note that an organization multiplier schedule hierarchy is really a hierarchy of exceptions. Define the multipliers for
an organization only to override the multipliers of its parent organization .
Seeded methods cannot be used for Oracle Fusion Projects.
Method assigned to the ledger must specify the COA.
Share the same account rules across applications.
Use value set rules if source contains segment values.
Establish hard and soft limits at contract and contract line levels, with or without billing resources. This flexibility
eliminates the need to manually track and enforce limits, and reduces downstream adjustments.
Reduces the effort required for creating and maintaining billing extensions and invoice and revenue
recognition methods. Changes/customizations to seeded billing extensions is not supported in the Cloud.
View, adjust, and finalize invoices from a single location. Use the invoice work area to easily create and adjust
invoices, which can reduce the billing errors that result in increased workload.
Utilize the Manage Billing Transaction Exceptions page. Transactions considered eligible for processing but not
invoiced or recognized for revenue are captured in a table and displayed in a UI for easier fixing.
Enable the billing option on a project type in order to create projects that can be used for invoicing and recognizing
revenue. Only projects with a project type that is enabled for billing can be associated with a contract line.
If using work types to determine whether an expenditure item is billable, set the profile option Work Type Derived for
Expenditure Item to Yes.
Event type can be used to derive accounting in subledger accounting for event based invoice and
revenue entries.
Use unique label names across budget segment values. For example, use segment specific labels for each budget
segment, such as Fund-level1 for Fund and Department-level1 for Department. Otherwise you may cause problems for
the Budgetary Control Dashboard.
After you change the control budget name, run the Rebuild Control Budget Dimension program to update the control
budget names in the budgetary control cube.
The default set of the business unit is assigned to each reference data object. You must perform the Manage Business
Unit Set Assignment task. Even if you don't change any of the sets assigned, the assignment isn't complete until the
record is saved.
Generally the project expenditure organizations will also be departments.
he application uses the most detailed information available to determine the rate. For example, If you assign a rate to a
person and job combination, that rate has precedence over the person rate. If you assign a rate to a person, job and
organization combination, that rate has precedence over the person rate or person and job combination.
When you create a project template, it's selected as the primary planning resource breakdown structure. You can
designate another planning resource breakdown structure as primary if required, but you can't remove the default
planning resource breakdown structure from the project or template.
Where a resource breakdown structure is not centrally controlled, changes against the resource breakdown structure on
a project are not reflected in the parent planning resource breakdown structure. Deselect the 'Allow resource changes
at the project level' option to ensure all projects using the planning resource breakdown structure use the same
resources.
After you create a project using a project type, you can't edit the project type.
Create burdened cost accounting journal entries. If you select this option for Project Burdening, the raw cost may be
accounted twice if separate journal lines are created for the raw cost and for the total burdened cost.
To make financial plan types available more widely across your organization, you can assign them to a common set.
You can use a revenue method with the As Billed or As Incurred revenue method classification only when combined
with an invoice method that has the Rate Based invoice method classification. In this situation, the bill rate, burden, or
transfer price schedule type selected for that invoice method is used for both invoicing and revenue recognition.
Project manager and project team member are two predefined project roles that you can't edit or delete as they have
specific functions in a project.
If you create a project enterprise labor resource from an employee in Oracle Fusion HCM, the employee or contingent
worker must have a unique email address in a valid format and an active primary assignment in HCM.
Customers who are implementing Project Resource Management but do not want to search by qualifications and
proficiency levels - maybe searching by availability only or directly assigning resources - don't have to create managed
project enterprise labor resources from HCM persons. The application can maintain resource available capacity for
resources that are not HCM employees or contingent workers.
You can't assign the same code to both project and task codes because they share the same definition. As a result, you
have a total of 70 codes available to use as project or task codes.
You must select a resource pool if you select the Manage resource availability and staffing option. The default resource
pool value is Resources with No Pool Membership.
Pool membership dates for a resource must be contiguous and can't overlap.
Deleting a parent pool also deletes the child pools.
There currently are no capabilities to delete a project. The ability to update the Project Number is dependent on the
following: (1) the Project Unit is using Manual Numbering, (2) there are no actual cost transactions or billing events for
the project, (3) a budget enabled for Budgetary Controls has not be created, (4) the Action Controls assigned to the
import source of the project do not preclude name/number update. The Project Name can always be updated, unless
an Action Control prevents it.
It is assumed that the standalone selling prices were approved offline before uploading.
Note: You cannot deactivate the predefined rules. You can however define new Contract Identification Rules with a
Priority that means Revenue Management will process the new rules first.
Because performance obligation templates are specific to each business, there are no predefined performance
obligation templates.
A good or service can have multiple standalone selling prices if the standalone sales pool of the good or service contains
multiple pricing dimension combinations.
Usage of item groups is recommended when the representation type is Discount Percentage.
Complete the following steps: (1) Identify the contract(s) with the customers, (2) Identify the separate performance
obligations, (3) Determine the transaction price, (4) Allocate the transaction price, (5) Recognize revenue when a
performance obligation is satisfied.
Best practice should be to recommend multiple Asset Clearing accounts based on asset category/book. The clearing
accounts should also be excluded from balance sheet CVR rules so the correct CC can be applied at PO stage. Doing both
of these means that the only thing that needs to be selected by the user is the location
The best practice is to migrate in entered currency and functional currency. Leave the journal created from the
subledger data conversion in the general ledger and manually correct the GL balances with a journal. This will ensure
that the sub ledger and the General Ledger will reconcile after the conversion and will prevent the issue you have with
only the functional currency being un-available on the control account.
Customer Account Site/Relationship does not currently support Common Set. Although the system allows sharing of the
same reference (setup data) data across Business Units, you cannot use the Common data set for Customer Site and
Customer Relationships, you have to define at least one here. Receivables Set enabled reference objects:
- Revenue Scheduling Rules
- Auto Cash Rules
- AutoMatch Rule Sets
- *Customer Account Relationships (TCA)
- *Customer Site
- Payment Terms
- Receipt Application Exception Rules
- Remit to Address
- Revenue Contingencies
- Sales Persons (TCA)
- Standard Memo Lines
- Transaction Sources
- Transaction Types
- Lockbox
Simplified enterprise structure implementation via GL RI Upload that can auto-create AR setups
Following AR setups automatically created from GL RI Upload:
- Manage Receivables System Options
- Manage Receivables Activities
- Manage AutoAccounting Rules
- Manage Remit to Addresses
- Manage Statement Cycles
Following setups have seeded values:

- Manage Standard Memo Lines
- Manage Transmission Formats for Lockbox
In some cases, you may only have 4 remaining manual setups to be performed to make the system operational:
- Manage Receipt Class/Methods and associate Bank Accounts
- Manage Lockbox
- Manage Approval Limits
- Manage Customer Uploads
After the Rapid Implementation Enterprise Structures spreadsheet upload process completes, whenever user navigates
to any of the following setup pages, the system automatically defaults the corresponding reference accounts:
- Transaction Type Reference Accounts
- Memo Lines Reference Accounts
- Salesperson Reference Accounts
- Customer Site Reference Accounts
- Receivables Activities
- Receipt Method Bank Accounts
- Receivables System Options
Use Cash Management Rapid Implementation task to (Upload) Create Bank, Branches and accounts
Many customers that do not have statutory document sequencing requirements, still want their transaction numbers to
not have gaps between them. You must configure gapless document sequencing to achieve this.
Select Automatic transaction numbering checkbox to automatically number new transactions you create using this
source, check the Automatic Transaction Numbering box and enter a Last Number. You can use automatic transaction
numbering with both Imported and Manual sources.
If you select Copy document number to transaction number, you can control whether the document number and
transaction number are the same for manually entered or imported transactions assigned to a specific batch source. The
transaction batch source option Copy Document Number to Transaction Number determines whether these attributes
are the same when the transaction is completed or if they are assigned different values.
To ensure contracts are created based on contract identification rules, especially if you are using new user configured
source document types make sure to: 1) check that contract identification rules are defined for "Source document
type" you are processing. 2) Check that a "Default contract identification rule" is defined on "Document line Id" for any
new "Source document type" you are processing.
3) Review the execution report for "Validate Customer contract" program and fix any errors reported using "Correct
contract document errors in spreadsheet" (ADFdi) task.
To ensure performance obligations are created within contracts based on performance obligation identification rules,
especially if you are using new user configured source document types make sure to: 1) Check that performance
obligation identification rules are defined for new "Source document type" your are processing. 2) Check that a "Default
obligation identification rule" is defined on "Document line Id" for any new "Source document type" you are processing.
3) Review the execution report for "Validate Customer contract" program. Fix any errors reported using "Correct
contract document errors in spreadsheet" (ADFdi) task.
If you are uploading Standalone Selling Prices via the Create Standalone Selling Prices spreadsheet (ADFdi) make sure
there are no blank spaces anywhere in the fields that you populated. You can verify if your upload was successful via the
Manage Standalone Selling Prices ADFdi via the Task Pane.
When reviewing the Manage Standalone Selling Prices spreadsheet check that you populated the correct Effective
Period to match the date within the contract / performance obligation, also check that you filled in the UOM values, the
pricing dimension combinations (to match the pricing dimension combination on the performance obligations), and the
SSP/ESP amounts correctly.
If you find some errors then correct them and re-upload the SSP/ESP via Manage Standalone Selling Prices spreadsheet
again, and re-run the Identify Customer Contracts process again.
All the seeded SLA accounting rules for Revenue Management for Contract Liabilities and Contract Assets are derived
from Revenue Management System Options, except for the Revenue account, where the account combination is derived
in the following priority order:
1) Items – assign a sales account combination (In order to be able to assign a sales account (revenue) to an item, you
must first assign a management business unit, and then assign a ledger to the inventory organization).
2) Customer Bill-To-Site (In the Manage Customer UI, go to the customer site Reference Accounts and update the
Revenue account combination)
3) Customer Bill-To Header (In the Manage Customer UI, go to the customer Reference Accounts and update the
Revenue account combination)
So ensure that an account combination for the sales account or revenue account has been assigned to at least one of
the above. Then run the Identify Customer Contracts again with Accounting mode set to 'Draft' to validate that
accounting is generated and to validate if the accounting is as expected.
If you want to extract data from Revenue Management to third party systems, you can extract smaller volumes of data
via custom BI Publisher reports, refer to MOS Doc IDs:
Doc ID 2145444.1: Oracle BI Publisher Best Practices for SaaS Environments
Doc ID 2199494.1: Oracle Fusion BI Publisher: How to request changes for the BI Publisher Memory Guard settings
If extracting very high volumes of data and data size related issues are encountered consider using an actual extraction
which is actually designed to do such tasks, by reviewing the documentation on Creating BI Cloud Extracts:
https://docs.oracle.com/en/cloud/saas/applications-common/r13-update17d/biacc/creating-business-intelligence-
cloud-extract.pdf
Count of Best Practice
Module Total
Advanced Collections 2
Allocation Manager 2
Application Toolkit 1
Approval Management (AMX) 6
Budgetary Controls 1
Budgeting and Planning 1
Cash Management 19
Common Features 2
Enterprise 5
Enterprise Structures 13
Expenses 10
Financial Reporting 9
Fixed Assets 17
Functional Setup Manager 3
General Ledger 103
Integration with Financial External Systems 1
OBIEE 1
OTBI 4
Payables & Payments 36
Planning and Budgeting 1
Project Costing 1
Project Billing 6
Project Contracts 1
Project Costing 7
Project Execution Management 8
Project Financial Management 4
Project Foundation 16
Receivables 12
Revenue Management 11
Security 13
Subledger Accounting 7
Transaction Taxes 8
Grand Total 331

Oracle ERP Cloud Guided Path and Best Configuration Practices 2018 - R13 Final

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Oracle ERP Cloud Guided Path and Best Configuration Practices 2018 - R13 Final

Caricato da

Copyright:

Formati disponibili

Oracle ERP Cloud Guided Path and Best Configu

Applies to Oracle Fusion Cloud Financial Produc

PLEASE READ THIS PAGE FIRST

Scope & Assumptions

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

on Cloud Financial Products and current GA releases.

may be trademarks of their respective owners.

Finalize Project Plan and Key Milestones/Deliverables

Perform Security, Reporting, Integration & Data Conversion Worksh

Perform Delivered Content Reviews and Mapping

Conduct Implementation Checkpoint (Planning)

Configure OOTB Security, Approvals, Notifications, Reports & Integra

Conduct Functional Review and Validation Test - CRP 1 & 2

Migrate Critical Historical Data

Develop, Test and Deploy High Priority Extensions

Load & Validate Data

Develop, Test and Deploy Critical Custom Reports

Assess Solution Completeness

Migrate Functional Setups from Test to Production

Migrate/Configure Security and OOTB Reports & Integrations

Perform User Acceptance

Getting Started with Your Implementation

Oracle Enterprise Resource Planning Cloud Service Implementation Leading Practices

Oracle Integrated Invoice Imaging Guide for Cloud

Setup Instructions for Printing from Oracle Cloud

Cloud Security: Federated SSO for Fusion-based SaaS

Minimum Steps for Financial Enterprise structures and GL Setup

Rapid Implementation for Financials

Rapid Implementation for Procurement

Rapid Implementation for Project Portfolio Management

Configure Basic Enterprise Structure for Procurement ( Shared Service)

Rapid Implementation Troubleshooting Guide

How to Verify Data Conversion Results

Information Center: Oracle Fusion Applications - Fusion Security

Using External Data Integration Services for Oracle ERP Cloud

Execute Enterprise Structures Setup Report

Troubleshooting Guide for Cloud Printer

How to Get the Most from Fusion Applications Diagnostic Logging

Configurations, Extensions, Reports, Security, Environment, Interfaces

How to Verify Data Conversion Results

Functional Setup Manager (New Compare Feature)

How to Report on Users and Roles Assigned to Them

How can I use BI Publisher to run SQL against Fusion Database

Performance Questionnaire and Best Practices

Best Practice: Cut Over Plan Developed and Approved

Oracle ERP Cloud Period Close

Oracle Cloud Applications Removal of Functionality or Features

Oracle Applications Cloud Service Entitlements

Link Oracle Help Center Customer, SI

Link Whitepaper Customer, SI

Link MOS Note Customer, SI

Link MOS Note Customer, SI

Link Oracle A-Team Blog Customer, SI

Link MOS Notes Customer, SI

Link MOS Note Customer, SI

Link Oracle Help Center Customer, SI

Link Oracle Help Center Customer, SI

Link Oracle Help Center Customer, SI

Link MOS Note Customer, SI

Link MOS Note Customer, SI

Link MOS Note Customer, SI

Link MOS Note Customer, SI

Link MOS Note Customer, SI