Oracle SLA Concepts

s a
)ha
c om
m ini ide
R12 Oracleca pge nt GuNew
de
Financials
r la@Fundamentals
tu
k a
Features
is S
a h
bash use t
anu to I • Student Guide
bh ens e
a (
l e lic
Volume
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
D49298GC20
Edition 2.0
July 2009
D61425
Unauthorized reproduction or distribution prohibited Copyright© 2009, Oracle and/or its affiliates
Copyright © 2009, Oracle. All rights reserved.
Disclaimer
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS
a
The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted
by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
as
Trademark Notice
m )h
c o
ini ide
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
m
e Gu
owners.
p g
a ent
c
@ tud
a
Author
a r l S
a k h is
sh se t
Richard Sears, Dee Fairbanks Simpson
b a u
n
Technical Contributors and Reviewers
a u to
( b en se Gardipe, Theresa Hickman, Anant Iyer, Thierry
h Wallace
ar la Macisaac,
lic Vic Mitchell, Christine Rudd, Kathryn Wohnoutka
David Barnacle, Melanie Featherstone,
e
ak rab
Javelle, Ruth Kukla, Robert
l
s h
u n sfe using: Oracle Tutor
Bawasapublished
an on-tr
This book
Bh n
Unauthorized reproduction or distribution prohibited Copyright© 2009, Oracle and/or its affiliates
Table of Contents
R12 Overview...................................................................................................................................................1-1
Oracle Financials Overview ..........................................................................................................................1-3
Objectives ......................................................................................................................................................1-4
Why R12?......................................................................................................................................................1-5
Architecture ...................................................................................................................................................1-6
Multi-Org Access Control (MOAC)..............................................................................................................1-8
Subledger Accounting ...................................................................................................................................1-9
Ledger............................................................................................................................................................1-11
Ledger Sets ....................................................................................................................................................1-12
Ledger Architecture.......................................................................................................................................1-13
Legal Organization ........................................................................................................................................1-14
Enhanced Legal Support................................................................................................................................1-15
Benefits of Legal Entities ..............................................................................................................................1-16
s a
Oracle E-Business Tax ..................................................................................................................................1-17
)ha
Advanced Global Intercompany System .......................................................................................................1-18
c o m
ini ide
Centralized Banking ......................................................................................................................................1-19
m
Bank Model Example ....................................................................................................................................1-20
g e Gu
Four Ways to Consolidate Information .........................................................................................................1-21
p
c a ent
Multi-Dimensional Analysis & Reporting.....................................................................................................1-22
@ tud
Financial Consolidation Hub .........................................................................................................................1-23
a r la S
Data Management..........................................................................................................................................1-24
a k h i s
XML Publisher ..............................................................................................................................................1-25
ash use t
New Standard Reports ...................................................................................................................................1-26
u b
Other New Features .......................................................................................................................................1-27
a n e to
Summary........................................................................................................................................................1-29
a (bh icens
Multi-Org Access Control lOverview.............................................................................................................2-3
Multi-Org Access Control Overview..............................................................................................................2-1
k a r le l
ha ferab
Objectives ......................................................................................................................................................2-4
a s
Agenda...........................................................................................................................................................2-5
s Description..........................................................................................................2-7
u B Access
Multi-Org
a n
Control
a n - t r
nonAccess Control Setup ...................................................................................................................2-11
Bh Multi-Org
Multi-Org Access Control Benefits ..............................................................................................................2-9
Multi-Org Access Control Process Summary................................................................................................2-10
Multi-Org Access Control Setup – Create Operating Unit ............................................................................2-12

Multi-Org Access Control Setup – Define Security Profile ..........................................................................2-14
Multi-Org Access Control Setup – Run System List Maintenance ...............................................................2-15
Multi-Org Access Control Setup – Set Profile Options.................................................................................2-16
Implementation Considerations .....................................................................................................................2-17
Agenda...........................................................................................................................................................2-18
Multi-Org Preferences Description................................................................................................................2-19
Multi-Org Preferences Benefits .....................................................................................................................2-20
Multi-Org Preferences Process Summary.....................................................................................................2-21
Multi-Org Preferences Setup .........................................................................................................................2-22
Multi-Org Preferences Setup – Add to SubMenu..........................................................................................2-23
Multi-Org Preferences Setup – Set Preferences............................................................................................2-24
Agenda...........................................................................................................................................................2-25
Enhanced Multi-Org Reporting Description..................................................................................................2-26
Enhanced Multi-Org Reporting Benefits......................................................................................................2-27
Enhanced Multi-Org Reporting Process ........................................................................................................2-28
Enhanced Multi-Org Reporting Process – Run Report.................................................................................2-29
Summary........................................................................................................................................................2-30
Copyright © Oracle 2009. All rights reserved.
R12 Oracle Financials New Features Fundamentals Table of Contents

Unauthorized reproduction or distribution prohibited
i Copyright© 2009, Oracle and/or its affiliates
Subledger Accounting Overview ....................................................................................................................3-1
Subledger Accounting Overview...................................................................................................................3-3
Objectives ......................................................................................................................................................3-4
Agenda...........................................................................................................................................................3-5
Subledger Accounting ...................................................................................................................................3-7
Subledger Accounting Description................................................................................................................3-8
Agenda...........................................................................................................................................................3-10
Business Benefits...........................................................................................................................................3-11
Business Benefits – Global Example.............................................................................................................3-12
Business Benefits - Auditability ....................................................................................................................3-15
Business Benefits – Transaction Example.....................................................................................................3-16
Business Benefits - Accounting Reconciliation.............................................................................................3-18
Agenda...........................................................................................................................................................3-19
Key Concepts.................................................................................................................................................3-20
Event Classes.................................................................................................................................................3-21
s a
)ha
Events ............................................................................................................................................................3-22
m
Transaction Objects and Sources...................................................................................................................3-23
c o
Agenda...........................................................................................................................................................3-24
ini ide
Major Features...............................................................................................................................................3-25
m
e Gu
Accounting Methods Builder.........................................................................................................................3-27
g
p
a ent
Online Accounting.........................................................................................................................................3-31
c
@ tud
Inquiries.........................................................................................................................................................3-32
r la
Offline Accounting ........................................................................................................................................3-34
a S
k is
Standard Reports ...........................................................................................................................................3-35
a h
ash use t
Agenda...........................................................................................................................................................3-36
b
Setup..............................................................................................................................................................3-37
nu to
Setup - Journal Line Type..............................................................................................................................3-38
a
bh ens e
Setup – Journal Line Type.............................................................................................................................3-39
a (
l e lic
Setup - Journal Line Type..............................................................................................................................3-40
ar
k abl
Setup - Account Derivation Rule...................................................................................................................3-41
h a
as nsfer
Setup – Account Derivation Rule ..................................................................................................................3-42
B
Setup - Account Derivation Rule...................................................................................................................3-43
anu -tra
Setup – Journal Entry Description .................................................................................................................3-44
Bh non
Setup – Journal Line Definition.....................................................................................................................3-45
Setup - Journal Line Definition .....................................................................................................................3-46
Setup – Application Accounting Definition ..................................................................................................3-47
Setup - Application Accounting Definition ...................................................................................................3-48
Setup – Subledger Accounting Method .........................................................................................................3-49
Setup - Subledger Accounting Method..........................................................................................................3-50
Ledger Setup and SLAM Assignment ...........................................................................................................3-51
Setup – Set Key Profile Options....................................................................................................................3-53
Agenda...........................................................................................................................................................3-54
Summary........................................................................................................................................................3-56
Oracle E-Business Tax Overview ...................................................................................................................4-1
Oracle E-Business Tax Overview..................................................................................................................4-3
Objectives ......................................................................................................................................................4-4
Agenda...........................................................................................................................................................4-5
What is Oracle E-Business Tax (eBTax) .......................................................................................................4-7
Agenda...........................................................................................................................................................4-8
Business Requirements Met by eBTax..........................................................................................................4-9
Business Needs Solutions ..............................................................................................................................4-11
Agenda...........................................................................................................................................................4-15
Key Concepts: Tax Authority........................................................................................................................4-16

ii Copyright© 2009, Oracle and/or its affiliates
Key Concepts: Tax Regime ...........................................................................................................................4-17
Key Concepts: Tax ........................................................................................................................................4-18
Key Concepts: Tax Jurisdiction.....................................................................................................................4-19
Agenda...........................................................................................................................................................4-20
Architecture Overview ..................................................................................................................................4-21
Agenda...........................................................................................................................................................4-22
Processing Taxes for Transactions ................................................................................................................4-23
Tax Determination Services Example ...........................................................................................................4-25
Agenda...........................................................................................................................................................4-29
User Interface ................................................................................................................................................4-30
Agenda...........................................................................................................................................................4-32
Upgraded and Redesigned Features...............................................................................................................4-33
Upgraded and Enhanced Features .................................................................................................................4-34
Tax Definition Hierarchy...............................................................................................................................4-35
Tax Configuration Ownership .......................................................................................................................4-37
Tax Defaulting Hierarchy ..............................................................................................................................4-38
System Options for Tax.................................................................................................................................4-39
s a
)ha
Tax Groups ....................................................................................................................................................4-40
m
Tax Jurisdiction Handling..............................................................................................................................4-41
c o
Tax Compounding .........................................................................................................................................4-43
ini ide
Tax Inclusiveness ..........................................................................................................................................4-44
m
e Gu
Tax Recovery.................................................................................................................................................4-46
g
p
a ent
Tax Rounding ................................................................................................................................................4-48
c
@ tud
Tax Overrides ................................................................................................................................................4-49
r la
Offset Taxes...................................................................................................................................................4-51
a S
k is
Party Tax Attributes.......................................................................................................................................4-52
a h
ash use t
Multiple Tax Registrations ............................................................................................................................4-53
b
Tax Exemptions.............................................................................................................................................4-55
nu to
Tax Exceptions ..............................................................................................................................................4-57
a
bh ens e
Tax Formulas.................................................................................................................................................4-58
a (
l e lic
Global Descriptive Flexfields ........................................................................................................................4-60
ar
k abl
Transaction Tax Upgrade ..............................................................................................................................4-61
h a
as nsfer
New Features .................................................................................................................................................4-63
B
Content and Services Subscription ................................................................................................................4-64
anu -tra
Events and Configuration Owner Options.....................................................................................................4-65
Bh non
Tax Jurisdictions............................................................................................................................................4-67
Tax Rules.......................................................................................................................................................4-68
Fiscal Classifications: Product.......................................................................................................................4-69
Fiscal Classifications: Party...........................................................................................................................4-70
Fiscal Classifications: Transaction ................................................................................................................4-72
Tax Repository ..............................................................................................................................................4-74
Tax Simulator ................................................................................................................................................4-75
Guided Configuration ....................................................................................................................................4-76
Profile Options for Tax..................................................................................................................................4-78
Upgrade Considerations ................................................................................................................................4-79
Implementation Information..........................................................................................................................4-80
Summary........................................................................................................................................................4-81
Oracle General Ledger....................................................................................................................................5-1
Oracle General Ledger...................................................................................................................................5-3
Objectives ......................................................................................................................................................5-4
Agenda – Part 1 .............................................................................................................................................5-5
Agenda – Part 2 .............................................................................................................................................5-6
Agenda – Part 1 .............................................................................................................................................5-7
Accounting Setup ..........................................................................................................................................5-8
Accounting Setup Benefits ............................................................................................................................5-11
Accounting Setup Manager ...........................................................................................................................5-12

iii Copyright© 2009, Oracle and/or its affiliates
Accounting Setup Manager Benefits .............................................................................................................5-14
Accounting Setup Process .............................................................................................................................5-15
Agenda – Part 1 .............................................................................................................................................5-18
Multiple Currency Support For General Ledger Data From All Sources ......................................................5-19
Multiple Currency Support For General Ledger Data From All Sources Benefits........................................5-22
Multiple Currency Support For General Ledger Data From All Sources Process.........................................5-23
Agenda – Part 1 .............................................................................................................................................5-25
Entered Currency Reporting and Analysis Description.................................................................................5-26
Entered Currency Reporting and Analysis Description................................................................................5-27
Entered Currency Reporting and Analysis Benefits .....................................................................................5-28
Entered Currency Reporting and Analysis Setup ..........................................................................................5-29
Agenda – Part 1 .............................................................................................................................................5-30
Foreign Currency Recurring Journals Description .......................................................................................5-31
Foreign Currency Recurring Journals Benefits.............................................................................................5-32
Foreign Currency Recurring Journals Process...............................................................................................5-33
s a
)ha
m
Agenda – Part 1 .............................................................................................................................................5-35
c o
Data Access to Multiple Legal Entities and Ledgers Description .................................................................5-36
ini ide
Data Access to Multiple Legal Entities and Ledgers Benefits.......................................................................5-39
m
e Gu
Data Access to Multiple Legal Entities and Ledgers Process.......................................................................5-40
g
p
a ent
Data Access to Multiple Legal Entities and Ledgers Setup..........................................................................5-41
c
@ tud
Data Access to Multiple Legal Entities and Ledgers Setup – Assign Data Access Set .................................5-42
r la
a S
k is
Agenda – Part 1 .............................................................................................................................................5-44
a h
ash use t
Multi-Ledger Processing Description............................................................................................................5-45
b
Multi-Ledger Processing Benefits ................................................................................................................5-47
nu to
Multi-Ledger Processing ...............................................................................................................................5-48
a
bh ens e
Multi-Ledger Processing Process – Simultaneous Opening and Closing of Periods.....................................5-49
a (
l e lic
Multi-Ledger Processing Process – Simultaneous Year-End Closing Journals.............................................5-50
ar
k abl
Multi-Ledger Processing Process – Simultaneous Currency Translation.....................................................5-51
h a
as nsfer
Multi-Ledger Processing Process – Financial Reporting Across Ledgers ...................................................5-52
B
Multi-Ledger Processing Setup ....................................................................................................................5-53
anu -tra
Agenda – Part 1 .............................................................................................................................................5-54
Bh non
Financial Reports Across Ledgers Description.............................................................................................5-55
Financial Reports Across Ledgers Benefits..................................................................................................5-56
Financial Reports Across Ledgers Process ...................................................................................................5-57
Financial Reports Across Ledgers Setup ......................................................................................................5-58
Agenda – Part 1 .............................................................................................................................................5-59
Cross-Ledger and Foreign Currency Allocations Description......................................................................5-60
Cross-Ledger and Foreign Currency Allocations Benefits ...........................................................................5-61
Cross-Ledger and Foreign Currency Allocations Setup and Process ...........................................................5-62
Agenda – Part 1 .............................................................................................................................................5-63
Streamlined Automatic Posting/Reversal Description...................................................................................5-64
Streamlined Automatic Posting/Reversal Benefits .......................................................................................5-65
Streamlined Automatic Posting/Reversal Setup and Process .......................................................................5-66
Agenda – Part 1 .............................................................................................................................................5-67
Integrated Web-based Spreadsheet Interface Description .............................................................................5-68
Integrated Web-based Spreadsheet Interface Benefits...................................................................................5-70
Integrated Web-based Spreadsheet Interface Setup and Process...................................................................5-71
Agenda – Part 1 .............................................................................................................................................5-72
Journal Copy Description ..............................................................................................................................5-73
Journal Copy Benefits ...................................................................................................................................5-74
Journal Copy Setup and Process....................................................................................................................5-75
Agenda – Part 2 .............................................................................................................................................5-76
Streamlined Consolidation Mappings Description .......................................................................................5-77

iv Copyright© 2009, Oracle and/or its affiliates
Streamlined Consolidation Mappings Benefits ............................................................................................5-80
Streamlined Consolidation Mappings Setup and Process.............................................................................5-81
Agenda – Part 2 .............................................................................................................................................5-82
Replacement for Disabled Accounts Description .........................................................................................5-83
Replacement for Disabled Accounts Benefits ..............................................................................................5-84
Replacement for Disabled Accounts Setup and Process...............................................................................5-85
Agenda – Part 2 .............................................................................................................................................5-86
Management Reporting and Security Description........................................................................................5-87
Management Reporting and Security ............................................................................................................5-88
Management Reporting and Security Benefits .............................................................................................5-91
Management Reporting and Security Setup .................................................................................................5-92
Agenda – Part 2 .............................................................................................................................................5-93
Data Access Security for Legal Entities and Ledgers Description ................................................................5-94
Data Access Security for Legal Entities and Ledgers Description ...............................................................5-98
Data Access Security for Legal Entities and Ledgers Benefits......................................................................5-100
Data Access Security for Legal Entities and Ledgers Setup and Process.....................................................5-101
a
Agenda – Part 2 .............................................................................................................................................5-103
s
Journal Reversal Enhancements Description and Benefits...........................................................................5-104
)ha
m
Journal Reversal Enhancements Setup .........................................................................................................5-105
c o
Agenda – Part 2 .............................................................................................................................................5-106
ini ide
Control Accounts Description and Benefits ..................................................................................................5-107
m
e Gu
Control Accounts Setup and Process .............................................................................................................5-108
g
p
a ent
Agenda – Part 2 .............................................................................................................................................5-109
c
@ tud
Security for Definitions Description..............................................................................................................5-110
r la
Security for Definitions .................................................................................................................................5-112
a S
k is
Security for Definitions - Example................................................................................................................5-113
a h
ash use t
Security for Definitions Benefits ..................................................................................................................5-114
b
Security for Definitions Setup and Process ..................................................................................................5-115
nu to
Agenda – Part 2 .............................................................................................................................................5-116
a
bh ens e
Accounting and Reporting Sequencing Description......................................................................................5-117
a (
l e lic
Accounting and Reporting Sequencing Benefits ..........................................................................................5-118
ar
k abl
Accounting and Reporting Sequencing Setup and Process ..........................................................................5-119
h a
as nsfer
Agenda – Part 2 .............................................................................................................................................5-120
B
Journal Line Reconciliation Description .......................................................................................................5-121
anu -tra
Journal Line Reconciliation Benefits............................................................................................................5-122
Bh non
Journal Line Reconciliation Setup and Process ............................................................................................5-123
Agenda – Part 2 .............................................................................................................................................5-124
Enhanced Intercompany Description.............................................................................................................5-125
Enhanced Intercompany Benefits ..................................................................................................................5-126
Enhanced Intercompany Accounting and Balancing Rules Process.............................................................5-127
Enhanced Balancing Process – Intracompany Journals................................................................................5-128
Enhanced Intercompany Accounting and Balancing Rules Setup................................................................5-130
Summary........................................................................................................................................................5-132
Oracle Fixed Assets .........................................................................................................................................6-1
Oracle Fixed Assets .......................................................................................................................................6-3
Objectives ......................................................................................................................................................6-4
Agenda...........................................................................................................................................................6-5
Subledger Accounting Architecture Description ...........................................................................................6-7
Subledger Accounting Architecture Benefits ................................................................................................6-8
Subledger Accounting Process ......................................................................................................................6-9
Subledger Accounting Architecture Summary ..............................................................................................6-10
Subledger Accounting Setup .........................................................................................................................6-11
Agenda...........................................................................................................................................................6-12
Enhanced Mass Additions for Legacy Conversions Description...................................................................6-13
Enhanced Mass Additions for Legacy Conversions Benefits ........................................................................6-15

v Copyright© 2009, Oracle and/or its affiliates
Agenda...........................................................................................................................................................6-17
Automatic Preparation of Mass Additions Description .................................................................................6-18
Automatic Preparation of Mass Additions Benefits ......................................................................................6-19
Automatic Preparation of Mass Additions Process.......................................................................................6-20
Automatic Preparation of Mass Additions Process .......................................................................................6-21
Automatic Preparation of Mass Additions Setup..........................................................................................6-22
Automatic Preparation of Mass Additions Setup Quickcodes......................................................................6-23
Agenda...........................................................................................................................................................6-24
Flexible Reporting Using XML Publisher Description .................................................................................6-25
Benefits..........................................................................................................................................................6-27
Flexible Reporting Using XML Publisher Setup...........................................................................................6-28
Flexible Reporting Using XML Publisher Example XML Output...............................................................6-29
Agenda...........................................................................................................................................................6-30
Automatic Depreciation Rollback Description..............................................................................................6-31
Automatic Depreciation Rollback Benefits ...................................................................................................6-32
a
Agenda...........................................................................................................................................................6-33
s
Enhanced Functionality for Energy Industry Description .............................................................................6-34
)ha
m
Summary........................................................................................................................................................6-35
c o
ini ide
Oracle Purchasing ...........................................................................................................................................7-1
m
Oracle Purchasing..........................................................................................................................................7-3
pge Gu
Objectives ......................................................................................................................................................7-4
c a ent
Agenda Part 1 ................................................................................................................................................7-5
a@ tud
Agenda Part 2 ................................................................................................................................................7-6
r l
k a is S
Agenda Part 1 ................................................................................................................................................7-7
a h
ash use t
Professional Buyer's Work Center Description .............................................................................................7-8
Professional Buyer's Work Center Benefits...................................................................................................7-9
u b
to
Professional Buyer's Work Center Overview ................................................................................................7-10
an e
bh ens
Professional Buyer's Work Center Requisition Management........................................................................7-11
a (
Professional Buyer's Work Center Requisition Management – Key Profile Options...................................7-13
l e lic
ar
k abl
a
Agenda Part 1 ................................................................................................................................................7-17
h
as nsfer
Enhanced Catalog Access Description ..........................................................................................................7-18
B
Enhanced Catalog Access Benefits................................................................................................................7-19
u -tra
an Enhanced Catalog Access Setup Preferences ................................................................................................7-20
Bh non
Agenda Part 1 ................................................................................................................................................7-21
Document Styles Description ........................................................................................................................7-22
Document Styles Benefits .............................................................................................................................7-23
Document Styles Process – Source Document Reference .............................................................................7-24
Agenda Part 1 ................................................................................................................................................7-25
Procurement for Complex Services Description............................................................................................7-26
Procurement for Complex Services High Level Business Flow....................................................................7-27
Procurement for Complex Services New Purchasing Features.....................................................................7-28
Procurement for Complex Services Benefits................................................................................................7-30
Agenda Part 1 ................................................................................................................................................7-34
Multi-Org Access Control Description..........................................................................................................7-35
Multi-Org Access Control Benefits ...............................................................................................................7-36
MOAC Effects – Forms and Pages................................................................................................................7-37
Multi-Org Access Control Public APIs ........................................................................................................7-38
Agenda Part 1 ................................................................................................................................................7-39
E-Business Tax Description .........................................................................................................................7-40
E-Business Tax Benefits................................................................................................................................7-41
E-Business Tax Process – Tax Calculation ..................................................................................................7-42
E-Business Tax Setup...................................................................................................................................7-43

vi Copyright© 2009, Oracle and/or its affiliates
Agenda Part 1 ................................................................................................................................................7-45
Document Publishing Enhancements Description.........................................................................................7-46
Document Publishing Enhancements Benefits ..............................................................................................7-48
Document Publishing Enhancements Setup and Process .............................................................................7-49
Document Publishing Enhancements Setup – PDF Template ......................................................................7-50
Document Publishing Enhancements Setup – RTF Template ......................................................................7-51
Document Publishing Enhancements Setup – Upload Template..................................................................7-52
Document Publishing Enhancements Process – Printing in Procurement Flow ...........................................7-53
Document Publishing Enhancements Process – Print Purchasing Document ..............................................7-54
Agenda Part 1 ................................................................................................................................................7-56
Document Attachments Description.............................................................................................................7-57
Document Attachments Benefits ..................................................................................................................7-59
Document Attachments Process ...................................................................................................................7-60
Document Attachments Setup .......................................................................................................................7-61
Document Attachments Setup – Define Purchasing Options .......................................................................7-62
a
Agenda Part 1 ................................................................................................................................................7-63
s
Oracle Supplier Network Description............................................................................................................7-64
)ha
m
Transacting Over Oracle Supplier Network ..................................................................................................7-65
c o
Oracle Supplier Network Support Transactions with Purchasing..................................................................7-66
ini ide
Oracle Supplier Network Benefits.................................................................................................................7-67
m
e Gu
Oracle Supplier Network New Features ........................................................................................................7-68
g
p
a ent
c
@ tud
Agenda Part 2 ................................................................................................................................................7-70
r la
Maintain Sourcing Rules/ASLs for Agreement Items ...................................................................................7-71
a S
k is
Maintain Sourcing Rules/ASLs for Agreement Items Benefits.....................................................................7-72
a h
ash use t
Maintain Sourcing Rules/ASLs for Agreement Items - Define Rules for a Specific Plant ...........................7-73
b
Agenda Part 2 ................................................................................................................................................7-75
nu to
Support for Contractor Purchasing Users Description...................................................................................7-76
a
bh ens e
Support for Contractor Purchasing Users Benefits ........................................................................................7-77
a (
l e lic
Support for Contractor Purchasing Users Setup ...........................................................................................7-78
ar
k abl
Support for Contractor Purchasing Users Setup – Set Profile Option ..........................................................7-79
h a
as nsfer
B
Agenda Part 2 ................................................................................................................................................7-81
anu -tra
Compliance to Packaging Constraints Description........................................................................................7-82
Bh non
Compliance to Packaging Constraints Benefits.............................................................................................7-84
Compliance to Packaging Constraints Process Summary..............................................................................7-85
Compliance to Packaging Constraints Process – Apply Order Modifiers .....................................................7-86
Compliance to Packaging Constraints Process – Perform UOM Conversion ...............................................7-87
Compliance to Packaging Constraints Process – Perform Quantity Rounding..............................................7-88
Compliance to Packaging Constraints Setup and Process .............................................................................7-89
Agenda Part 2 ................................................................................................................................................7-92
Auto-Approval Tolerances for Change Orders Description ..........................................................................7-93
Auto-Approval Tolerances for Change Orders Setup and Process................................................................7-94
Agenda Part 2 ................................................................................................................................................7-95
EAM Support for Services Procurement Description....................................................................................7-96
EAM Support for Services Procurement Setup and Process .........................................................................7-97
Additional Considerations .............................................................................................................................7-99
Agenda Part 2 ................................................................................................................................................7-101
Model Complex Pricing for Blanket Line Items Description ........................................................................7-102
Model Complex Pricing for Blanket Line Items Benefits .............................................................................7-104
Model Complex Pricing for Blanket Line Items Setup and Process..............................................................7-105
Model Complex Pricing for Blanket Line Items Pricing Hierarchy ..............................................................7-106
Model Complex Pricing for Blanket Line Items Profile Options ..................................................................7-107

vii Copyright© 2009, Oracle and/or its affiliates
Agenda Part 2 ................................................................................................................................................7-112
Mass Re-pricing of Purchasing Documents Description ...............................................................................7-113
Mass Re-pricing of Purchasing Documents Benefits ...................................................................................7-114
Mass Re-pricing of Purchasing Documents Process.....................................................................................7-115
Agenda Part 2 ................................................................................................................................................7-117
New User Interface for Oracle Purchasing Setups Description .....................................................................7-118
New User Interface for Oracle Purchasing Setups Benefits .........................................................................7-120
Agenda Part 2 ................................................................................................................................................7-121
Advanced Approval Support for Requisitions Description ...........................................................................7-122
Advanced Approval Support for Requisitions Benefits.................................................................................7-123
Advanced Approval Support for Requisitions Parallel Approvals ...............................................................7-124
Advanced Approval Support for Requisitions Voting Method.....................................................................7-125
Advanced Approval Support for Requisitions Position Hierarchy Support .................................................7-126
Advanced Approval Support for Requisitions Setup and Process .................................................................7-127
a
Summary........................................................................................................................................................7-129
s
Oracle Accounts Payable ................................................................................................................................8-1
)ha
om
Oracle Accounts Payable...............................................................................................................................8-3
c
ini ide
Objectives ......................................................................................................................................................8-4
m
Agenda...........................................................................................................................................................8-5
pge Gu
Suppliers in the Trading Community Architecture (TCA) ...........................................................................8-7
c a ent
TCA Security by Functional Areas................................................................................................................8-8
a@ tud
Payment Banks, Branches, and Accounts......................................................................................................8-9
r l
k a is S
Supplier Bank Accounts ................................................................................................................................8-10
a h
ash use t
Collaboration with Suppliers to Resolve Disputes ........................................................................................8-11
Invoice Requests............................................................................................................................................8-12
u b
to
an e
bh ens
Agenda...........................................................................................................................................................8-14
a (
Deferred Recoverability ................................................................................................................................8-15
l e lic
ar
Deferred Recoverability Features ..................................................................................................................8-16
k abl
a
Deferred Recoverability Benefits ..................................................................................................................8-17
h
as nsfer
Deferred Recoverability Process Part 1: Set Up and Invoice .......................................................................8-18
B
Deferred Recoverability Process Part 2: Set Up and Payment .....................................................................8-19
u -tra
an Setup Taxes with Deferred Recoverability ....................................................................................................8-20
Bh non
Agenda...........................................................................................................................................................8-22
Enhanced Asset Tracking ..............................................................................................................................8-23
Enhanced Asset Tracking Benefits ................................................................................................................8-24
Enhanced Asset Tracking Process .................................................................................................................8-25
Invoice Lines .................................................................................................................................................8-26
Agenda...........................................................................................................................................................8-28
Payment Requests Key Concepts ..................................................................................................................8-29
Payment Requests Description ......................................................................................................................8-30
Payment Requests Benefits............................................................................................................................8-32
Payment Requests Process.............................................................................................................................8-33
Oracle Receivables – Refund Example .........................................................................................................8-34
Funds Disbursement Process - Loans ............................................................................................................8-35
Payment Request – Additional Payables Actions..........................................................................................8-36
Payment Requests: Synchronizing Between Products..................................................................................8-37
Payment Requests Reporting.........................................................................................................................8-38
Payment Requests Optional Setup.................................................................................................................8-39
Payment Requests Miscellaneous Set up.......................................................................................................8-40
Agenda...........................................................................................................................................................8-42

viii Copyright© 2009, Oracle and/or its affiliates
Payment Method Controls and Enhanced Payment Information...................................................................8-43
Key Concepts.................................................................................................................................................8-44
Evaluate Payment Choices – Reporting and Payment Instruction Requirements..........................................8-47
Enhanced Payment Method Controls Description.........................................................................................8-51
Enhanced Payment Method Controls Benefits ..............................................................................................8-52
Enhanced Payment Method Controls Process – Enter Payables Document ..................................................8-53
Expanded Payment Attribute Availability and Defaulting – Definition ........................................................8-56
Expanded Payment Attribute Availability and Defaulting Description.........................................................8-57
Expanded Payment Attribute Availability and Defaulting – Benefits ...........................................................8-58
Expanded Payment Attribute Availability and Defaulting – Enter Payables Document ...............................8-59
Expanded Payment Attribute Availability and Defaulting - Payment Attributes Defaulting ........................8-60
Expanded Payment Attribute Availability and Defaulting - UI.....................................................................8-61
Configurable Payment Attribute Validation Description...............................................................................8-62
Configurable Payment Attribute Validation Benefits....................................................................................8-63
Configurable Payment Attribute Validation Invoice: Scheduled Payment Holds .........................................8-64
Configurable Payment Attribute Validation Invoice: Invoice on Hold Report .............................................8-65
Configurable Payment Attribute Validation Payment: Payment Processing Choices ...................................8-66
s a
Expanded Payment Attribute Availability Payment Instruction Formats and Reporting - Benefits..............8-70
)ha
m
Expanded Payment Attribute Availability Payment Instruction Formats and Reporting ..............................8-71
c o
Payment Instruction Formats and Reporting XML Publisher Templates ......................................................8-72
ini ide
Payment Instruction Formats & Reporting XML Publisher Templates.........................................................8-73
m
e Gu
Expanded Payment Attribute Availability Payment Instruction Formats and Reporting .............................8-74
g
p
a ent
Formats & Reporting Payment Process .........................................................................................................8-75
c
@ tud
Formats and Reporting Payment Process ......................................................................................................8-76
r la
a S
k is
Formats and Reporting Payment Process ......................................................................................................8-78
a h
ash use t
b
Setup Payment Method Controls and Enhanced Payment.............................................................................8-80
nu to
Configurable Payment Attribute Validation Setup .......................................................................................8-81
a
bh ens e
Configurable Payment Attribute Validation Setup Consideration................................................................8-82
a (
l e lic
Configurable Payment Attribute Validation Setup: View Available Validations..........................................8-84
ar
k abl
Configurable Payment Attribute Validation Setup – Payment Methods .......................................................8-85
h a
as nsfer
Configurable Payment Attribute Validation Setup: Payment Process Format ..............................................8-86
B
Configurable Payment Attribute Validation Setup: Payment Process Profile ...............................................8-87
anu -tra
Expanded Payment Attribute Availability Payment Instruction Formats and Reporting Setup ....................8-88
Bh non
Enhanced Payment Method Controls Setup ..................................................................................................8-89
Expanded Payment Attribute Availability and Defaulting - Setup................................................................8-90
Agenda...........................................................................................................................................................8-92
Self Assessed Tax Description ......................................................................................................................8-93
Self Assessed Tax Features ...........................................................................................................................8-94
Self Assessed Tax Benefits............................................................................................................................8-95
Self Assessed Tax Predetermined Process.....................................................................................................8-96
Self Assessed Tax Process – 1. Predetermined..............................................................................................8-97
Self Assessed Tax: Predetermined Process – Invoice Entry..........................................................................8-98
Self Assessed Tax: Predetermined Process – Calculate Tax .........................................................................8-99
Self Assessed Tax: Predetermined Process – Calculate Tax Example .........................................................8-100
Self Assessed Tax: Predetermined Process – Calculate Tax .........................................................................8-101
Self Assessed Tax Process – Account ...........................................................................................................8-102
Self Assessed Tax Setup – Reporting Choices ..............................................................................................8-104
Self Assessed Tax Process – Report ..............................................................................................................8-106
Self Assessed Tax Manual Determination Process........................................................................................8-107
Self Assessed Tax Process – 2. Manual Determination.................................................................................8-108
Self Assessed Tax: Manual Determination Set Up - E-Business Tax Controls.............................................8-109
Self Assessed Tax: Manual Determination Process – Invoice Entry.............................................................8-110
Self Assessed Tax: Manual Determination Process – Calculate Tax ............................................................8-111
Self Assessed Tax: Manual Determination Process – Calculate Tax Example .............................................8-112

ix Copyright© 2009, Oracle and/or its affiliates
Setup Self Asessed Tax .................................................................................................................................8-114
Self Assessed Tax: Predetermined Set Up First Party, Party Tax Profile......................................................8-115
Self Assessed Tax: Predetermined Set Up – First Party, Party Tax Profile...................................................8-116
Self Assessed Tax: Predetermined Set Up – Supplier Party Tax Profile .......................................................8-117
Agenda...........................................................................................................................................................8-119
Oracle Payables For Complex Contract Terms .............................................................................................8-120
Oracle Payables for Complex Contract Terms Benefits ................................................................................8-121
Complex Contract Terms Key Concepts .......................................................................................................8-122
Oracle Procurement to Payables: High Level Business Flow.......................................................................8-124
Integrated Products: High Level Business Flow............................................................................................8-130
Oracle e-Business Tax Setup: Tax Configuration .........................................................................................8-131
Business Flow: Payables Distinction.............................................................................................................8-132
Contract Delivery Invoicing ..........................................................................................................................8-133
Invoice Workbench: Contract Delivery Invoices ..........................................................................................8-134
Oracle Payables: Ensure Billing Compliance ................................................................................................8-135
Oracle Payables: Tolerances and Holds.........................................................................................................8-136
s a
Oracle Payables: Holds Notification Options ................................................................................................8-138
)ha
m
Oracle Payables for Complex Contract Terms Benefits ................................................................................8-139
c o
Oracle Procurement to Payables: Setup Overview ........................................................................................8-140
ini ide
Oracle Procurement Setup .............................................................................................................................8-141
m
e Gu
Payables Setup: Financial Options ................................................................................................................8-143
g
p
a ent
Payables Setup – Payables Options ...............................................................................................................8-144
c
@ tud
Payables Setup: Invoice Tolerances ..............................................................................................................8-145
r la
Shared Setup: Supplier Terms & Controls ....................................................................................................8-146
a S
k is
Oracle Approvals Management Setup Approval Rules .................................................................................8-147
a h
ash use t
Oracle eBusiness Tax Setup: Tax Configuration...........................................................................................8-148
b
Prepayments: Tax Configuration Example....................................................................................................8-149
nu to
a
bh ens e
Agenda...........................................................................................................................................................8-152
a (
l e lic
Multi-Org Access Control in Payables Description.......................................................................................8-153
ar
k abl
Multi-Org Access Control in Payables Benefits............................................................................................8-156
h a
as nsfer
Multi-Org Access Control Process ................................................................................................................8-157
B
Multi-Org Access Control Process, Invoice Entry ........................................................................................8-158
anu -tra
Multi-Org Access Control Process, Payment Templates...............................................................................8-160
Bh non
Multi-Org Access Control Process, Controlling Payables Periods...............................................................8-161
Multi-Org Access Control Process, Submitting Concurrent Request ...........................................................8-162
Multi-Org Access Control Process, Submitting Standard Report..................................................................8-163
Multi-Org Access Control Process, Open Account Balances Listing Report................................................8-164
Multi-Org Access Control Setup ...................................................................................................................8-165
Multi-Org Access Control Payables Setup ....................................................................................................8-166
Summary........................................................................................................................................................8-168
Oracle Receivables...........................................................................................................................................9-1
Oracle Receivables ........................................................................................................................................9-3
Objectives ......................................................................................................................................................9-4
Agenda...........................................................................................................................................................9-5
New and Changed Features for Balance Forward Billing .............................................................................9-7
Balance Forward Billing Description ............................................................................................................9-8
Balance Forward Billing Benefits .................................................................................................................9-11
Balance Forward Billing Setup and Process..................................................................................................9-13
Balance Forward Billing Setup Define Billing Cycle....................................................................................9-15
Balance Forward Billing Setup Define Payment Term .................................................................................9-17
Balance Forward Billing Setup Customer Profile Class................................................................................9-19
Balance Forward Billing Setup Account & Site Profile ................................................................................9-21
Balance Forward Billing Setup Account Level Bill Example .......................................................................9-23

x Copyright© 2009, Oracle and/or its affiliates
Balance Forward Billing Setup Site Level Bill Example .............................................................................9-24
Oracle BPA Rules Setup................................................................................................................................9-25
Balance Forward Billing Process Enter Transaction ....................................................................................9-27
Balance Forward Billing Process Imported Transactions.............................................................................9-28
Balance Forward Billing Process Creating Bills ..........................................................................................9-29
Balance Forward Billing Process Generating Bill Logic..............................................................................9-30
Balance Forward Billing Use Cases ..............................................................................................................9-32
Balance Forward Billing Process Generate Bill Program.............................................................................9-33
Balance Forward Billing Process Confirm Bill .............................................................................................9-35
Summary Balance Forward Bill Example .....................................................................................................9-37
Detail Balance Forward Bill ..........................................................................................................................9-38
Balance Forward Billing Process BPA Print Program..................................................................................9-39
Balance Forward Billing Process Disable Payment Terms ...........................................................................9-41
Balance Forward Billing Process Change Payment Terms ..........................................................................9-42
Balance Forward Billing Dependencies and Interactions .............................................................................9-43
Balance Forward Billing Functional Upgrade Script....................................................................................9-44
a
Agenda...........................................................................................................................................................9-47
s
Credit Card Chargeback Description.............................................................................................................9-48
)ha
m
Credit Card Chargeback Benefits ..................................................................................................................9-50
c o
Credit Card Chargeback Process ...................................................................................................................9-51
ini ide
Credit Card Chargeback Process Receive Receipt .......................................................................................9-54
m
e Gu
Credit Card Chargeback Process Record Credit Card Chargeback ..............................................................9-56
g
p
a ent
Credit Card Chargeback Process Validate Credit Card Chargeback ............................................................9-57
c
@ tud
Credit Card Chargeback Process Validate Credit Card Chargeback .............................................................9-58
r la
Credit Card Chargeback Process Validate Credit Card Chargeback ............................................................9-59
a S
k is
Credit Card Chargeback Setup ......................................................................................................................9-60
a h
ash use t
Agenda...........................................................................................................................................................9-61
b
Legal Entity Background...............................................................................................................................9-62
nu to
Legal Entity Model........................................................................................................................................9-63
a
bh ens e
Legal Entity Background...............................................................................................................................9-64
a (
l e lic
Legal Entity Description................................................................................................................................9-65
ar
k abl
Legal Entities and Accounting.......................................................................................................................9-66
h a
as nsfer
Legal Entities and Shared Accounting...........................................................................................................9-67
B
Legal Entity Description Defaulting for Transactions...................................................................................9-68
anu -tra
Legal Entity Description Defaulting for Transactions..................................................................................9-69
Bh non
Legal Entity Description Defaulting for Receipts ........................................................................................9-70
Legal Entity Benefits .....................................................................................................................................9-72
Legal Entity Setup and Automated Process...................................................................................................9-73
Legal Entity Setup Update Transaction Type...............................................................................................9-75
Legal Entity Setup Update Batch Source .....................................................................................................9-76
Legal Entity Process - AutoInvoice ...............................................................................................................9-77
Legal Entity Setup and Manual Process ........................................................................................................9-80
Legal Entity Process – Manual Transaction ..................................................................................................9-82
Legal Entity Process – On Account Credit Memos .......................................................................................9-83
Legal Entity Process – Bills Receivable ........................................................................................................9-84
Legal Entity Process - Receipts .....................................................................................................................9-85
Legal Entity Process – Claim LE Defaulting.................................................................................................9-86
Agenda...........................................................................................................................................................9-88
E-Business Tax ..............................................................................................................................................9-89
Receivables E-Business Tax Integration Key Benefits.................................................................................9-90
E-Business Suite Tax Prior to Release 12 .....................................................................................................9-92
E-Business Suite Tax Integration 12.0 ..........................................................................................................9-93
Architecture of a Tax Line in E-Business Tax...............................................................................................9-94
Example of US Sales Tax in 12.0..................................................................................................................9-96
Example of UK VAT Tax in 12.0 .................................................................................................................9-97
Migrating Taxes from 11.5 to 12.0 ................................................................................................................9-98

xi Copyright© 2009, Oracle and/or its affiliates
Migrating of Tax Codes and Tax Group Codes.............................................................................................9-100
Use of Tax Rate Codes in Receivables..........................................................................................................9-102
Use of Tax Classifications in Receivables.....................................................................................................9-103
Setting Up New Taxes in E-Business Tax.....................................................................................................9-104
Receivables Specific Tax Setups ...................................................................................................................9-106
System Options..............................................................................................................................................9-107
Customer Tax ................................................................................................................................................9-108
Transaction Type ...........................................................................................................................................9-109
Receivables Activity......................................................................................................................................9-110
Adjustments, Receipt Discounts, and Recoverable Tax ................................................................................9-111
Standard Memo Lines....................................................................................................................................9-112
Legal Entity and Ship To...............................................................................................................................9-113
Transactions and Migrated Taxes ..................................................................................................................9-115
Transactions and Migrated Taxes: Key Differences.....................................................................................9-116
Transactions and New Taxes .........................................................................................................................9-118
Transactions and Manual Taxes ....................................................................................................................9-119
s a
)ha
Agenda...........................................................................................................................................................9-121
m
Subledger Accounting Overview...................................................................................................................9-122
c o
Subledger Accounting Benefits .....................................................................................................................9-123
ini ide
Subledger Accounting in Receivables Overview ..........................................................................................9-124
m
e Gu
Subledger Accounting in Receivables Benefits.............................................................................................9-125
g
p
a ent
Subledger Accounting in Receivables Process Submit Accounting Program ...............................................9-126
c
@ tud
Subledger Accounting in Receivables Process Create/View Accounting ....................................................9-127
r la
Subledger Accounting in Receivables Process Online Create Accounting ...................................................9-128
a S
k is
Subledger Accounting in Receivables Setup .................................................................................................9-129
a h
ash use t
Subledger Accounting in Receivables Setup Ledgers and SLAMs ...............................................................9-130
b
Subledger Accounting in Receivables Setup Sources for Accounting Definitions........................................9-131
nu to
Subledger Accounting in Receivables Setup Predefined Event Classes/Types .............................................9-132
a
bh ens e
Subledger Accounting in Receivables Setup AR Predefined Event Classes/Types .....................................9-133
a (
l e lic
Subledger Accounting in Receivables Setup Anatomy of a Journal Entry....................................................9-134
ar
k abl
Subledger Accounting in Receivables Setup Journal Line Types .................................................................9-135
h a
as nsfer
Subledger Accounting in Receivables Setup Account Derivation Rule ........................................................9-136
B
Subledger Accounting in Receivables Setup Journal Line Definition of Invoices ........................................9-137
anu -tra
Subledger Accounting in Receivables Setup Assigning the JLD to the AAD...............................................9-138
Bh non
Subledger Accounting in Receivables Setup Assigning the AAD to the SLAM...........................................9-139
Subledger Accounting in Receivables Setup Assigning the SLAM to the Ledger ........................................9-140
Subledger Accounting in Receivables Setup Predefined SLAMs ................................................................9-141
Subledger Accounting in Receivables Process Invoice Accounting..............................................................9-142
Subledger Accounting in Receivables Process Multi-Fund Receivables Accounting ...................................9-143
Subledger Accounting in Receivables Process Adjustment Accounting .......................................................9-144
Subledger Accounting in Receivables Process Receipt Application Accounting..........................................9-145
Agenda...........................................................................................................................................................9-148
Obsolescence and Replacement of Features Description ..............................................................................9-149
Obsolescence and Replacement of Features Benefits....................................................................................9-157
Transition to New Features Collections Workbench ....................................................................................9-158
Transition to New Features Collections Workbench - Menu and Forms......................................................9-159
Transition to New Features Collections Workbench - Account Details .......................................................9-161
Transition to New Features Collections Workbench - Dunning Reprint ......................................................9-162
Transition to New Features Bills Receivable.................................................................................................9-163
Transition to New Features Trade Accounting..............................................................................................9-164
Transition to New Features Customer Standard Form..................................................................................9-165
Transition to New Features Tax Setup and Calculation ...............................................................................9-166
Transition to New Features Tax Reporting...................................................................................................9-167
Transition to New Features Subledger Accounting ......................................................................................9-168
Transition to New Features COGS and Revenue Matching .........................................................................9-169

xii Copyright© 2009, Oracle and/or its affiliates
Transition to New Features AR Customer Supplier Netting ........................................................................9-170
Transition to New Features On Account Credit Memo Refund ...................................................................9-171
Transition to New Features Consolidated Billing.........................................................................................9-172
Agenda...........................................................................................................................................................9-173
Centralized Payment Process Description .....................................................................................................9-174
Centralized Payment Process Setup and Process...........................................................................................9-177
Centralized Payment Process Setup Create Receipt Class/Method ...............................................................9-178
Centralized Payment Process Process Invoice Payment...............................................................................9-180
Centralized Payment Process Error Handling................................................................................................9-181
Centralized Payment Process Setup Customer's Payment Details.................................................................9-182
Agenda...........................................................................................................................................................9-184
Automated Refunds Description....................................................................................................................9-185
Automated Refunds Setup and Process .........................................................................................................9-186
Automated Refunds Setup Receivables Activity...........................................................................................9-187
Automated Refunds Setup Transaction Sources............................................................................................9-188
Automated Refunds Process Applications Form ...........................................................................................9-190
s a
Automated Refunds Process New Refund Attributes Form ..........................................................................9-191
)ha
m
Automated Refunds Process View Refund Status .........................................................................................9-192
c o
ini ide
Agenda...........................................................................................................................................................9-194
m
e Gu
AP/AR Netting Description...........................................................................................................................9-195
g
p
a ent
AP/AR Netting Benefits ................................................................................................................................9-196
c
@ tud
AP/AR Netting Process Access .....................................................................................................................9-197
r la
AP/AR Netting Process Accessing ................................................................................................................9-198
a S
k is
Agenda...........................................................................................................................................................9-199
a h
ash use t
Daily Revenue Description............................................................................................................................9-200
b
Daily Revenue Setup and Process .................................................................................................................9-205
nu to
Daily Revenue Setup Accounting Rules........................................................................................................9-206
a
bh ens e
Daily Revenue Process Create Invoice Line..................................................................................................9-207
a (
l e lic
ar
k abl
Agenda...........................................................................................................................................................9-209
h a
as nsfer
Revenue Contingencies Overview.................................................................................................................9-210
B
Revenue Contingencies Description..............................................................................................................9-211
anu -tra
Revenue Contingencies Setup and Process....................................................................................................9-214
Bh non
Revenue Contingencies Setup Policy Threshold ...........................................................................................9-215
Revenue Contingencies Setup Seeded Contingencies ..................................................................................9-216
Revenue Contingencies Setup Contingency Codes/ID..................................................................................9-217
Revenue Contingencies Setup Create Rules ..................................................................................................9-218
Revenue Contingencies Process Contingency Assignment ..........................................................................9-219
Revenue Contingency Process Manage Contingencies ................................................................................9-220
Agenda...........................................................................................................................................................9-222
COGS and Revenue Matching Description ...................................................................................................9-223
COGS and Revenue Matching Benefits ........................................................................................................9-224
COGS and Revenue Matching Process COGS Recognition ........................................................................9-225
Agenda...........................................................................................................................................................9-227
Multi-Org Access Control Description..........................................................................................................9-228
Multi-Org Access Control Benefits ...............................................................................................................9-229
Receivables & Multi-Org Access Control .....................................................................................................9-230
Multi-Org Access Control Process ................................................................................................................9-233
Multi-Org Access Control Reporting ............................................................................................................9-234
Multi-Org Access Control Reporting Process ...............................................................................................9-235
Summary........................................................................................................................................................9-237
Oracle Cash Management...............................................................................................................................10-1

xiii Copyright© 2009, Oracle and/or its affiliates
Oracle Cash Management..............................................................................................................................10-3
Objectives ......................................................................................................................................................10-4
Agenda...........................................................................................................................................................10-5
Bank Account Model Definition ...................................................................................................................10-7
Bank Account Model Integration ..................................................................................................................10-8
Bank Account Model Benefits.......................................................................................................................10-9
Cash Management Security Components ......................................................................................................10-10
Bank Account Model Summary ....................................................................................................................10-12
Bank Account Model Setup and Process.......................................................................................................10-13
Agenda...........................................................................................................................................................10-15
Bank Account Balances and Interest Calculations Description.....................................................................10-16
Bank Account Balances and Interest Calculations Benefits ..........................................................................10-17
Bank Account Balances and Interest Calculations Maintenance..................................................................10-18
Bank Account Balances and Interest Calculations Summary .......................................................................10-19
Bank Account Balances and Interest Calculations Setup .............................................................................10-20
s a
)ha
Agenda...........................................................................................................................................................10-22
m
Bank Account Transfers Description............................................................................................................10-23
c o
Bank Account Transfers Benefits .................................................................................................................10-25
ini ide
Bank Account Transfers Process ...................................................................................................................10-26
m
e Gu
Bank Account Transfers Dependencies and Interactions ..............................................................................10-27
g
p
a ent
Bank Account Transfers Summary................................................................................................................10-28
c
@ tud
Bank Account Transfers Setup ......................................................................................................................10-29
r la
Bank Account Transfers Setup – Set System Profile....................................................................................10-30
a S
k is
a h
ash use t
Agenda...........................................................................................................................................................10-32
b
Subledger Accounting Description...............................................................................................................10-33
nu to
Subledger Accounting Benefits ....................................................................................................................10-35
a
bh ens e
Subledger Accounting Key Concepts ............................................................................................................10-36
a (
l e lic
Subledger Accounting Key Concepts Flow..................................................................................................10-37
ar
k abl
Subledger Accounting Summary...................................................................................................................10-38
h a
as nsfer
B
Agenda...........................................................................................................................................................10-40
anu -tra
Bank Statement Reconciliation Description ..................................................................................................10-41
Bh non
Bank Statement Reconciliation Benefits ......................................................................................................10-42
Bank Statement Reconciliation Setup............................................................................................................10-43
Agenda...........................................................................................................................................................10-44
Multi-Org Access Control and Security Description....................................................................................10-45
Multi-Org Access Control and Security Benefits ..........................................................................................10-47
Multi-Org Access Control and Security Summary ........................................................................................10-48
Agenda...........................................................................................................................................................10-50
Cash Pooling Description ..............................................................................................................................10-51
Creating Cash Pools.......................................................................................................................................10-52
Viewing and Updating Cash Pools ................................................................................................................10-53
Summary........................................................................................................................................................10-55

xiv Copyright© 2009, Oracle and/or its affiliates
Preface
Profile
Before You Begin This Course
• Functional knowledge of Oracle General Ledger
• Functional knowledge of Oracle Payables
• Functional knowledge of Oracle Purchasing
a
• Functional knowledge of Oracle Receivables
as
• Functional knowledge of Oracle Cash Management
m )h
c o
Prerequisites
m ini ide
p g e Gu
• There are no prerequisites for this course.
c a ent
r la@ tud
How This Course Is Organized
k a is S
a h
sh issiseant instructor-led course featuring
b a
R12 Oracle Financials New Features Fundamentals
u and written practice sessions reinforce the
lecture and hands-on exercises. Onlineudemonstrations
a n t o
concepts and skills introduced. h
( b e n se
a r la e lic
h a k abl
B as nsfer
a n u -tra
Bh non

xv Copyright© 2009, Oracle and/or its affiliates
Related Publications
Additional Publications
• System release bulletins
• Installation and user’s guides
• Read-me files
• International Oracle User’s Group (IOUG) articles
Oracle Magazine
a
•
as
m )h
c o
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

xvi Copyright© 2009, Oracle and/or its affiliates
Typographic Conventions
Typographic Conventions in Text
Convention Element Example
Bold italic Glossary term (if The algorithm inserts the new key.
there is a glossary)
Caps and Buttons, Click the Executable button.
lowercase check boxes, Select the Can’t Delete Card check box.
triggers, Assign a When-Validate-Item trigger to the ORD block.
windows Open the Master Schedule window.
Courier new, Code output, Code output: debug.set (‘I”, 300);
case sensitive directory names,
a
Directory: bin (DOS), $FMHOME (UNIX)
(default is filenames, Filename: Locate the init.ora file.
as
lowercase) passwords, Password: User tiger as your password.
m )h
pathnames,
c o
ini ide
Pathname: Open c:\my_docs\projects
URLs,
m
URL: Go to http://www.oracle.com
e Gu
user input,
usernames
User input: Enter 300
p
a entg
Username: Log on as scott
c
@ tud
Initial cap Graphics labels
r la
Customer address (but Oracle Payables)
a S
(unless the term is a
a k th is
ashchanges e
proper noun)
Italic Emphasized words
b
Do not save s
u see Oracle7 Server SQL Language
to the database.
a n ufurther information,
to
seManual.
and phrases, For
titles of books andh Reference
courses, a (b c e n
r l li
ka elements
Enter user_id@us.oracle.com, where user_id is the
a
variables
ab le name of the user.
h
s sfenames r
marks Ba with long
Quotation Interface Select “Include a reusable module component” and click Finish.
a n u -trthatanhave only
h n
This subject is covered in Unit II, Lesson 3, “Working with
B no initial caps;
lesson and chapter
Objects.”
titles in cross-
references
Uppercase SQL column Use the SELECT command to view information stored in the
names, commands, LAST_NAME
functions, schemas, column of the EMP table.
table names
Arrow Menu paths Select File > Save.
Brackets Key names Press [Enter].
Commas Key sequences Press and release keys one at a time:
[Alternate], [F], [D]
Plus signs Key combinations Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]

xvii Copyright© 2009, Oracle and/or its affiliates
Typographic Conventions in Code
Convention Element Example
Caps and Oracle Forms When-Validate-Item
lowercase triggers
Lowercase Column names, SELECT last_name
table names FROM s_emp;
Passwords DROP USER scott

IDENTIFIED BY tiger;
PL/SQL objects OG_ACTIVATE_LAYER
(OG_GET_LAYER (‘prod_pie_layer’))
a
Lowercase Syntax variables CREATE ROLE role
italic
as
Uppercase SQL commands and SELECT userid
m )h
functions FROM emp;
c o
m ini Paths
ide
Typographic Conventions in Oracle Application Navigation
ge
p nt G u
c a
la @ example,
This course uses simplified navigation paths, such as the following
tu de to direct you
k a r s S
i
through Oracle Applications.
a th
(N) Invoice > Entry > Invoice Batches Summary
b as(M)h Query
u s e
> Find (B) Approve
a n u t o
( b
This simplified path translates to the
e n se
h following:
a r la window,
e licselect Invoice then Entry then Invoice Batches
ak rab
1. (N) From the Navigator l
s h
Ba ansfe
Summary.
u
2. n(M) Fromtrthe menu, select Query then Find.
a on-
Bh n
3. (B) Click the Approve button.
Notations:
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
(I) = Icon
(H) = Hyperlink
(ST) = Sub Tab

xviii Copyright© 2009, Oracle and/or its affiliates
Typographical Conventions in Oracle Application Help System Paths
This course uses a “navigation path” convention to represent actions you perform to find
pertinent information in the Oracle Applications Help System.
The following help navigation path, for example—
(Help) General Ledger > Journals > Enter Journals
—represents the following sequence of actions:
1. In the navigation frame of the help system window, expand the General Ledger entry.
2. Under the General Ledger entry, expand Journals.
s a
3. Under Journals, select Enter Journals.
)ha
c om
ini ide
4. Review the Enter Journals topic that appears in the document frame of the help system
window.
g m
e Gu
c p
a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

xix Copyright© 2009, Oracle and/or its affiliates
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

xx Copyright© 2009, Oracle and/or its affiliates
s a
)ha
c om
m ini ide
pge Gu
R12 Overview c a ent
r la@ tud
k a is S
a
Chapter 1
h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Copyright © Oracle, 2009. All rights reserved.
R12 Overview
Unauthorized reproduction or distribution prohibited Copyright©
Chapter 1 - Page 1 2009, Oracle and/or its affiliates
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
R12 Overview
Oracle Financials Overview
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
R12 Overview
Objectives
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
R12 Overview
Why R12?
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a n uR12? -tra
Bh Release n is defined as “The Global Business Release.” Global is not just a geographic
Why
no12
perspective, but also a comprehensive perspective; release 12 functionality spans across both
industries and business functions.
• Flexible, centralized, global accounting structure
• 300+ enhancements to best practice business processes
• Comprehensive governance, risk and compliance platform
• Truly integrated performance management
• Real-time profitability analysis
• Unified financial and operational analytic applications
• Integration with core industry applications
• Self-service report formats and publication
• Superior ownership experience
R12 Overview
Architecture
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
a n u -tra
on components of the new architecture include:
Bh The nmajor
Architecture
• Multi-Org Access Control

• Ledger and Ledger Sets
• Subledger Accounting
• Tax Engine
• Intercompany
• Bank Model
Benefits of the new architecture include:
• Maintain 1 Ledger with 1 OU for each Company (LE)
- Get privacy for each company’s data
- Manage each company’s national and local compliance
• Combine many companies’ ledgers in a set
- Share GL services and workload
- Get combined data
R12 Overview
• Use MOAC to enable access to many OUs
- Process in and report across many Companies’ Operating Units
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
R12 Overview
Multi-Org Access Control (MOAC)
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu Multi-Org
- tra Access Control
h n
MOAC:
noprovides role based access to Operating Units, and allows you to perform multiple
B MOAC
tasks across operating units without changing responsibilities.
R12 Overview
Subledger Accounting
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -Accounting
tra
h n
Subledger
no accounting provides centralized rules and a common repository, and global control
B Subledger
of your accounts. Features include:
• Accounting Rules
- SarBox & 8th Dir.
- User Editable
• Subledger Daybooks (Journals)
• Subledger Balancing
• Reports, inquiries, open items, et cetera
• Multiple Representations
• Common Posting to GL Ledgers
• Real time or Periodic
Benefits of subledger accounting are:
• Faster, Easier Reconciliation
• Corporate Rules = Accounting Standardization
R12 Overview
• Local Rules = Improved Local Compliance
• Automate “Apples to Apples” Adjustments
• Improved Audit- ability
• Improved Internal Control
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
R12 Overview
Ledger
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
R12 Overview
Ledger Sets
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a n u Sets-tra
Bh Ledger n provide global information at a glance. Ledger sets share a chart of accounts and a
Ledger
nosets
calendar.
The key benefits to many Ledgers in one set are:
• Decision-driving business information always available
• Simpler processing and General Ledger management
• Data and definitions that can be shared and secured
R12 Overview
Ledger Architecture
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Architecture
- tra
h n
Ledger
noLedger Sets:
B Typical
• All IAS/IFRS or US GAAP ledgers
• 26 Subs in 1 country
• 35 countries in 1 region
R12 Overview
Legal Organization
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an uOrganization
- tra
h n
Legal
B LegalnoEntities (Les) such as Parent companies, own or control subsidiaries. There are no group
entities
• LEs pay the taxes and therefore need tax registrations
• Trade between LEs needs intercompany
• LEs own the money and bank accounts
• LEs file the accounts and take care of accounting
• LEs comply with whatever needs compliance: “legal” in LE
R12 Overview
Enhanced Legal Support
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu -Legal
tra Support
h n
Enhanced
o not replace GRE/LE - employer
B • nDid
• Added TCA parties for the Authorities
• Added a Legal Entity Configurator
• Introduced the following new terms:
- Jurisdiction: A legislative category and territory, has legal rules
- Legal Authority: Legal body who enforces legislation, collects fees / taxes, etc
- Legal Function: Functions that companies are required to perform (e.g. produce
yearly report, pay taxes, etc.)
- Legal Associations: Mapping companies to Ledgers, BSVs, OUs and other system
entities
R12 Overview
Benefits of Legal Entities
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u of-Legal
tra Entities
h n
Benefits
no of using Legal Entities:
B Examples
• Accounting Setup Manager: Assign books, bookkeeping rules and currency
management to your registered companies
• EBusiness Tax: Have your registered companies calculate, file, and pay the transaction
taxes they owe
• Intercompany: Do business between and across your registered companies with full legal
documentation
• Bank Model: Have your registered companies use their money to pay their bills, etc.
R12 Overview
Oracle E-Business Tax
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
an u -trOverview
a
h n
Architecture
noE-Business Tax (eBTax) consists of a tax knowledge base, a variety of tax services that
B Oracle
respond to specific tax events, a set of repositories (for tax content and tax recording) that
allow customers to manage their local tax compliance needs in a proactive manner, as well as
the ability to integrate with external tax content providers through a single integration point.
R12 Overview
Advanced Global Intercompany System
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -Global
tra Intercompany System
h n
Advanced
o
B • nAddresses the Top Barrier to a Fast Close
• Generates subledger invoices
• Controls transaction entry with Intercompany Calendar
• Has a Fully Configurable Approval Rules
• Has a Flexible Security Model
• Has a Centrally defined Intercompany Accounts
R12 Overview
Centralized Banking
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -tBanking
ra
h n
Centralized
o account is now associated with the LE instead of the Operating Unit
B • nBank
• A single bank account serves multiple Operating Units
• Any and all Operating Units associated with a ledger can be permitted to use the bank
account
• There is a centralized Credit Card Model
• There is Credit Card Encryption
• The Supplier & Customer Banks are in TCA
R12 Overview
Bank Model Example
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
an uModel-trExample
a
h n
Bank
o from different OUs with 1 instruction
B Pay ninvoices
• New Payments Module
• New Bank Module
• New Bank & Credit Card Features
R12 Overview
Four Ways to Consolidate Information
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
R12 Overview
Multi-Dimensional Analysis & Reporting
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
R12 Overview
Financial Consolidation Hub
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
a nu Consolidation
- tra
h n
Financial Hub
o interactive spreadsheet reporting with live drill down to transactions
B R12nincludes
R12 Overview
Data Management
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uManagement
- tra
h n
Data
o
B R12nleverages a centralized data model
R12 Overview
XML Publisher
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uPublisher
- tra
h n
XML
no you to format, manage, and deliver documents
B Enables
• Meets business requirements such as:
- Removes complexity
- Reduces maintenance cost
- Reduces TCO
• Integrated with: R9 CRM, ESA, FMS, HCM, and SCM
R12 Overview
New Standard Reports
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uStandard
- traReports
h n
New
no of the new standard reports are:
B Benefits
• You can create report formats using desktop tools (Adobe Acrobat, MS Word, MS Excel,
and XML Editors)
• You can publish in any format, to the web and electronically
• Reporting is consistent, with one source of data
R12 Overview
Other New Features
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uNew-Features
tra
h n
Other
B Therenoare over 300 new Financial features in Oracle E-Business release 12.
R12 Overview
Other New Features
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
R12 Overview
Summary
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
R12 Overview
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
R12 Overview
s a
)ha
c om
m ini ide
pge Gu
Multi-Org Accessc t
a enControl
r la@ tud
k a
Overview
is S
a
Chapter 2 t h
bash u se
a u
n et o
( bh ns
a
rl le li c e
k a
asha sferab
u B an
ha on-tr
n
B n
Multi-Org Access Control Overview

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Objectives
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Multi-Org Access Control Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u Access
- tra Control - Description
h n
Multi-Org
nowhen users had to enter or process data for multiple operating units, they had to login to
B In 11i,
different responsibilities because each responsibility could only access one operating unit. So if
there were a centralized payment processing center where users processed payments for
multiple organizations, they would have to keep logging in and out of different responsibilities
to process payments for a different organization or operating unit.
Now in Release 12, Multi-Org Access Control enables companies that have implemented a
Shared Services operating model to efficiently process business transactions by allowing users
to access, process, and report on data for an unlimited number of operating units within a
single application’s responsibility.
This increases the productivity of Shared Service Centers as users no longer have to switch
application responsibilities when processing transactions for multiple operating units. Data
security and access privileges are still maintained using security profiles that will now support
multiple operating units.

s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Access
- tra Control – Description (continued)
h n
Multi-Org
no if you have three operating units in the center you were managing, such as a
B For example,
Belgium Operating Unit, a Holland Operating Unit, and a Denmark operating unit, in 11i you
needed to define three different responsibilities. If you had one user who processed payables
invoices across all three operating units, then you would need to assign the three
responsibilities to that user and then the user would need to log in and out of each
responsibility to process invoices.
In Release 12, you can create a Security Profile and assign as many operating units as you want
to that security profile. So in this example, you could assign all three operating units to the
same security profile. Then, you can tie that security profile to a single responsibility using a
profile option called MO: Security Profile. For example, you could assign the security profile
to the EMEA Payables responsibility to allow that responsibility to process invoices across all
three operating units.
Processing payables invoices is just one example, with Multi-Org Access Control, you can
efficiently perform other processes, such as processing receivables invoices, viewing
consolidated requisitions, performing collections using Advanced Collections, and process
receiving and drop shipments.

Multi-Org Access Control Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a i s S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Access
- tra Control - Benefits
h n
Multi-Org
no Access Control provides improved processing efficiency because it takes time to
B Multi-Org
switch in and out of different responsibilities. As more and more companies move to shared
service centers, their users will be able to process data and transactions faster for multiple
operating units. It also provides better information for decision making.
Much information in the E-Business Suite is striped by operating unit, for example, customer
account sites and supplier sites. MOAC gives you the ability to view all of that information
across different OUs. So if your security profile has access to three operating units, you can
view all of the supplier sites across all three operating units. By viewing data from multiple
operating units from a single responsibility, you have more information which enables you to
make better decisions. For example, in Oracle Purchasing, you can now view global
consolidated requisition demands for each supplier. With this view, you are armed with the
information to negotiate purchase discounts.
You’re ultimately going to reduce costs because you can enter data across operating units
faster and you will not have the overhead of setting up and maintaining tons of responsibilities.

Multi-Org Access Control Process Summary
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Access
- tra Control Process Summary
h n
Multi-Org
o
B EachnFinancials product team has implemented MOAC to best suit their business process
flows. For example, in AP, there’s a new operating unit field on their Invoice Workbench. The
OU list of values reads from the Security Profile assigned to the responsibility to determine
which OUs should be displayed in the LOV. In general, when a user logs in to a responsibility
and opens an application, the application will determine which operating units can be accessed
and used for processing. The user can then view or process transactions for multiple operating
units.

Multi-Org Access Control Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Access
- tra Control Setup
h n
Multi-Org
o
B • nResponsibility: Human Resources
• Navigation: Security > Profile
In Release 12, when you define your security profile in HR using the Security profile form or
the Global Security profile form, you must:
• Assign all of the operating units that you want a responsibility to access.
• Run a concurrent request called “Run Security List Maintenance” from HR which makes
those security profile available and allows you to assign them to a responsibility via a
profile option called MO: Security Profile.

Multi-Org Access Control Setup – Create Operating Unit
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Access
- tra Control – Setup – Create Operating Unit
h n
Multi-Org
o
B • nResponsibility: General Ledger
Navigation: Accounting Setup Manager > Financials : Accounting Setup :
Accounting Setup Manager
• Responsibility: Human Resources:
Navigation: Work Structures : Organization > Description
In Release 12, you can define your operating units in two places. You can continue to define
them in the Oracle HRMS Organization Form or you can define them in the new Accounting
Setup Manager feature in General Ledger. The Accounting Setup Manager streamlines the
setup and implementation of Oracle Financial Applications. It centralizes the setup and
maintenance of common financial components, such as legal entities, operating units, and
ledgers. So when you create an accounting setup, assign a legal entity and create the ledgers
that will perform the accounting for that legal entity, you can also define and assign the
relevant operating units. By leveraging Accounting Setup Manager to define your OUs, you
can streamline your setup.

In R12, is instead of attaching an OU to a LE, you assign it to a default legal context.
All Release 11i HR Organizations classified as “Operating Units” will be preserved in Release
12. If operating units are assigned to a set of books, then they will be associated to a primary
ledger in an accounting setup. You will be able view all operating units assigned to an
upgraded primary ledger using Accounting Setup Manager.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Multi-Org Access Control Setup – Define Security Profile
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Access
- tra Control – setup Define Security Profile
h n
Multi-Org
o
• Navigation: Security : Profile or
• Navigation: Security : Global
Using Oracle HRMS, you can define your security profile using two forms:
• The Security Profile form, which allows you to select operating units from only one
Business Group
• The Global Security Profile form, which allows you to select operating units from
multiple Business Groups
Enter a name, and select the Security Type called “Secure organizations by organization
hierarchy and/or organization list”. This allows you to assign multiple OUs.
When assigning operating units, first select classification Operating Unit, and then select the
organization or Operating Unit name.
You can assign multiple operating units.

Multi-Org Access Control Setup – Run System List Maintenance
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Access
- tra Control – Setup – Run System List Maintenance
h n
Multi-Org
o
• Navigation: Processes and Reports : Submit Processes and Reports

Multi-Org Access Control Setup – Set Profile Options
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Access
- tra Control – Setup – System Profile Options
h n
Multi-Org
B • nTheo MO Security Profile controls the list of operating units that a responsibility or user
can access. If you set the security profile at the responsibility level, then all users using
that responsibility will have access to only the operating units available in the security
profile. If you set the security profile at the user level, then the user will have access to
only those operating units, irrespective of application responsibility that they log into.
• The MO: Default Operating Unit is optional and allows you to specify a default operating
unit that defaults when you open different subledger application pages. Because you can
access multiple operating units, you may want to set up a default one instead of forcing
users to constantly have to choose one. User Preferences allows you to specify a default
operating unit at the user level. Use the MO: Default Operating Unit profile option to set
the operating unit context or default operating unit when accessing an applications.
• The last profile option is for backwards compatibility and to support products that do not
use Multiple Organizations. The release 11i setting was for this is preserved during
upgrade. The Release 11i MO: Operating Unit profile option is supported in Release 12
as not all customers of Oracle products require multiple organizations.

Implementation Considerations
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu -tra Considerations
ondefine operating units using the HRMS organization form or you can define them in
Bh Youncan
Implementation
the new Accounting Setup Manager while you define other common financial components,
such as legal entities, and ledgers. Then, you use HRMS to define your Security Profile and run
the concurrent program.
• You can also use Accounting Setup Manager to define operating units while you define
other common financial components, such as legal entities, and ledgers. From Accounting
Setup Manager, you can view all operating units assigned to a primary ledger.
• Multi-Org Access Control integrates with all E-Business Suite products that use operating
units.

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Multi-Org Preferences Description
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Access
- tra Control Preferences - Description
h n
Multi-Org
no Preferences allows you to control the list of operating units to which you have
B Multi-Org
access. For example, a system administrator may create a security profile that has ten operating
units assigned to it and assign it to your responsibility. But, you may only deal with five of the
operating units on a daily basis and do not want work space cluttered with extraneous operating
units. You could set up Multi-Org preferences to restrict the list of operating units; you have
complete control over this and can change it at anytime. In addition, you can specify a default
operating unit.

Multi-Org Preferences Benefits
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Access
- tra Control Preferences - Benefits
h n
Multi-Org
no Preferences allows you to be more efficient by allowing you to set up your own
B Multi-Org
preferences and optimize your setup based on how you work.
This means faster data entry and cost reduction.

Multi-Org Preferences Process Summary
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u Access
- tra Control Preferences Process Summary
h n
Multi-Org
o
B The nprocessing of transactions is the same if you never specify user preferences.

Multi-Org Preferences Setup
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Access
- tra Control Preferences Setup
h n
Multi-Org
o
B Mostnproducts have added the Preferences user interface to their responsibility menus. You can
select preferred operating units which represent a subset of operating units assigned to your
responsibility’s security profile. You can also set a default operating unit.

Multi-Org Preferences Setup – Add to SubMenu
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Access
- tra Control Preferences – Setup – Add to SubMenu
h n
Multi-Org
o
B • nNavigation: System Administrator > Application > Menu
• Navigation: Application Developer > Application > Menu
Most applications have added the Preferences function to their menus. However, if it does not
appear, the system administrator can add it. To enable and display Preferences in your menu,
request your System Administrator to add the function, FNDMOPREFS to your menu
definition. The System Administrator should use either the System Administrator or
Application Developer responsibility and select the Menu (Application) option. Select your
product’s menu and add the function named User Preferences (FNDMOPREFS).

Multi-Org Preferences Setup – Set Preferences
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Access
- tra Control Preferences – Setup – Set Preferences
h n
Multi-Org
o
B • nResponsibility: Payables, Vision Operations
• Navigation: Setup > Options > User Operating Unit Preferences
Multi-Org Preferences page:
• The header displays: the user name that you are logged in as is displayed, the
responsibility name, and the Security Profile that you are currently assigned to as defined
by the MO: Security Profile profile option.
• The Default Operating Unit region is where you select a default OU. The List of values
displays all operating units assigned to your security profile.
• The region called Preferred Operating Units is where you select the subset of operating
units you want to work with.

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Enhanced Multi-Org Reporting Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -Multi-Org
tra
h n
Enhanced Reporting - Description
no Multi-Org reporting is not the same as cross-organization reports that allow you to
B Enhanced
run a report at the ledger level to obtain results for all operating units assigned to that ledger or
obtain results for all the operating units for a GRE/LE.
Multi-Org Reporting which allows a user to select any operating unit from a list of accessible
operating units. This allows user to report on data for multiple operating units from a single
application responsibility.

Enhanced Multi-Org Reporting Benefits
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Enhanced Multi-Org Reporting Process
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
anu -Multi-Org
tra
h n
Enhanced Reporting Process
o
B OncenMulti-Org Access Control has been set up, you can run reports for any operating unit you
have access to.

Enhanced Multi-Org Reporting Process – Run Report
s a
)ha
c om
m ini ide
p ge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -Multi-Org
tra
h n
Enhanced Reporting - Process
B Herenisoan example of an Accounts Payable report called Supplier Audit. When submitting this
report, you can select any operating unit that they have access to.

Summary
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
a ent
SubledgercAccounting
r la@ tud
k a
Overview
is S
a
Chapter 3 t h
bash u se
a u
n et o
( bh ns
a
rl le li c e
k a
asha sferab
u B an
ha on-tr
n
B n
Subledger Accounting Overview

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Objectives
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -Accounting
tra
h n
Subledger
no accounting is a new product in R12 which significantly enhances the accounting
B Subledger
support across the E-Business Suite products. Subledger Accounting includes new ledger
support and enhances the legal entity and intercompany accounting features.
Subledger Accounting is a new set of tools, accounting engine, and repository that you can use
to:
• Support multiple accounting requirements concurrently in a single instance through
configurable rules
• Increase transparency and have full auditability of the transaction and accounting data,
through a common user interface and data model
• Facilitate accounting reconciliation, especially for inter-transactional accounts
• Improve accounting reporting and analysis

Subledger Accounting Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -Accounting
tra
h n
Subledger Description
no Accounting is mainly a rule-based accounting engine that centralizes accounting for
B Subledger
Oracle E-Business Suite products in R12 as well as provide an accounting toolset and
repository for third-party applications. It is not a separate product in itself, but is Oracle’s
engine catering to the accounting needs of both Oracle and external modules.
Together with the new ledger support, it enables support of multiple accounting requirements
concurrently in a single instance. Different accounting regulations can be satisfied by
maintaining and applying different sets of rules to different sets of transactions; or accounting
for the same transaction with multiple methods.
By maintaining a full link between the transaction and accounting data, it allows powerful
reconciliation and auditing capabilities.
Since it provides the setup and inquiry UI and data model for accounting across modules, it
enables consistency in reporting, analysis, and user experience.
• Rule-based accounting engine, toolset and repository supporting both Oracle E-Business
Suite and external modules

• Allows multiple accounting representations for a single business event, resolving conflicts
between corporate and local fiscal accounting requirements
• Retains the most granular level of detail in the subledger accounting model, with different
summarization options in the General Ledger, allowing full auditability and reconciliation
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Business Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u Benefits
- tra
h n
Business
o
B The nflexibility of the accounting rule setup allows meeting different requirements in different
legislative, geographic or industry contexts. Assuming operations in multiple countries, each
with its own legal requirements and accounting standards, you are able to define a setup to
meet each of the requirements. SLA allows for multiple accounting requirements for a single
transaction or business event.

Business Benefits – Global Example
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Benefits
- tra – Global Example
h n
Business
o assumes a US-based corporation with operations in the UK and France.
B Thisnexample
• The French operation is subject to the French accounting regulations, and thus has to
report its activities to the local authorities denominated in Euros, according to the French
business calendar, French chart of accounts, and the French interpretation of IFRS
(International Financial Reporting Standards).
• The UK operation, similarly, is subject to the UK regulations, which for this example’s
sake are not as restrictive as the French ones. Thus, the UK operation does its local
reporting in the local currency, the British Pound, but according to the US business
calendar, US COA, and US GAAP.
• The US operation reports in the USD per the US business calendar, US COA, and GAAP.
In the R12 ledger setup, all of these operations are defined as three separate ledgers to satisfy
local reporting requirements. However, the headquarters/parent company wants to have a
consolidated global visibility of the worldwide operations. It is not very meaningful to
consolidate or compare each of these entities with each other for a few reasons:

• The reporting currencies are different
• The COA and the method of accounting for the French activities may be considerably
different than those in UK and US. For example, in FR, purchases or inventory are
reported as expenses, whereas in the other instances as inventory items. Hence, a mere
currency conversion will not be sufficient.
With R12 ledger architecture and SLA, the following model can be implemented to solve this
business need:
• For the UK operation, converting the activities to the US equivalent requires a currency
conversion since the calendar, COA, and accounting methods are common. This is
accomplished through the addition of a reporting currency to the UK ledger.
• For the French operation, conversion only is not sufficient. A secondary ledger must be
defined for the French ledger, which shares the same currency, COA, calendar, and
a
accounting method as the HQ.
as
)h
Through the definition of reporting currency and secondary ledgers, the three operations can
om
satisfy local regulations, and also allow comparison and consolidation.
c
ini ide
In above definition, SLA allows you to:
• Define multiple accounting methods
g m
e Gu
c p
a ent
• Use separate accounting methods on different ledgers
r la@ tud
S
• Create journal entries on multiple ledgers for a single business event (French activities
a k a is
h
ash use t
being accounted for on the primary ledger per IFRS method, and on the secondary ledger
b
per US GAAP method)
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Business Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u Benefits
- tra
h n
Business
noaccounting information and the tie back to the underlying transaction is maintained
B In 11i,
differently for each module.
Different subledgers/modules have their own model as to how and what they capture in terms
of accounting data. Some allow capturing more details and some link between the journals and
the underlying transactions. Some do not have the same flexibility or detail. This causes
difficulty and inconsistency in reporting for auditing, reconciliation or whichever purpose
across modules.
In R12, SLA provides the ability to retain the full link between transaction and accounting data
for all modules, and thus allow auditability. The accounting SLA creates is strongly tied to the
underlying transactions.

Business Benefits - Auditability
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Business Benefits – Transaction Example
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Benefits
- tra – Transaction Example
h n
Business
o tracks how the journal entry is built from a transaction.
B • nSLA
• On the left side of the screen, there is an invoice for two items, freight and tax.
• On the right, there are two entries created: one on the US corporate ledger and on the FR
statutory ledger.
• The expense entry is created for the two item lines of the invoice.
• The following two lines for freight and tax respectively.
• The rules have been setup to summarize all and create a single liability entry. We can also
configure the rule so that three or four separate liability lines are created.
• SLA stores and tracks how each line of the invoice contributed to the journal entry.

Business Benefits
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u Benefits
- tra
h n
Business
no benefit is the support for business flows in accounting within and across modules. In
B Another
flows where accounting for multiple transactions need to be tied together, SLA provides
standard features to recognize multi-transactional flows. This is very important in especially
reconciling accounts inter-transactional accounts.

Business Benefits - Accounting Reconciliation
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u Benefits
- tra - Accounting Reconciliation
h n
Business
B Goingnoback to the previous example and looking at a payment that pays off the invoice, the
SLA data model not only allows keeping the transaction-to-accounting link, but the inherent
features also allow to reflect the transaction flows in the accounting side. So here, a particular
payment is applied to a particular invoice liability.
Through the usage SLA Business Flows functionality, at the time of accounting for the
payment, we can to go back to the journal created for invoice and back out from the exact
liability account, at the exact rate that the invoice was converted at, if it was a foreign currency
one. Because the feature ensures accuracy itself, the need for reconciliation is reduced.

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Key Concepts
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
a n u -tra
onmodel defined in SLA for each subledger represents the transaction/document types
Bh The nevent
Key Concepts
and the lifecycle of each transaction:

• Event class classifies transaction types. An invoice, for example, would be an event class.
• Event type defines possible actions on each event class with potential accounting
significance, for example, validation of an invoice.
• The journal creation rules are defined per event class/event type.

Event Classes
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an uClasses- tra
h n
Event
o shows event classes for Payables, Purchasing and Receivables.
B The nslide

Events
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
a n u -tra
non event for a payables invoice, for example, is the validation, adjustment or the
Bh An accounting
Events
cancellation of the invoice. Similarly, for an AR receipt, accounting events are the creation,
application, or reversal of the receipt. When one of these actions is taken on a receipt
transaction, an accounting event is created. Based on the rule setup, there may or may not be a
resulting journal entry. You can set up rules to generate journal entries for some events, but not
for others.

Transaction Objects and Sources
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
a nu -trObjects
a
h n
Transaction and Sources
no object and sources are the data model for each subledger that contains the
B Transaction
transaction attributes/information made available to be used during journal rule setup and
journal entry generation.

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Major Features
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uFeatures
- tra
h n
Major
B SLAnisoa toolset, engine, and repository for centralized accounting processing. This means that
SLA provides the ability to set up journal creation rules and creates journal entries according to
multiple different accounting methods simultaneously. However, there are many options and
advanced features that facilitate the entire accounting process, including:
• Converting foreign currency journals into the functional currency
• Calculating exchange rate gain/loss
• Scheduling the automatic recognition of deferred revenue and expenses across the relevant
accounting periods
• Supporting automatic accrual reversals
• Tracking versions and effective dates on rules
• Processing a subset of transactions at a time, based on transaction type
• Enabling straight through accounting processing generating journal entries straight from
the transaction view to posting to general ledger at the single click of a button
• Allowing testing of rule setup by what-if type of analysis with draft accounting

Major Features
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uFeatures
- tra (continued)
h n
Major
o to use inquiry pages and customizable reports
B • nEasy
• Intelligible errors reporting and tools to troubleshoot
• Ability to copy rules in and between environments
• Manual adjustment entries in each subledger application
• Auto-maintenance of rules when accounts are disabled
• Various geography-specific requirements such as journal entry sequencing, and control
accounts reporting

Accounting Methods Builder
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a i s S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
anu -tMethods
ra
h n
Accounting Builder
no Methods builder is the toolset enabling the creation of journal entry rules that
B Accounting
allows multiple sets of rules to be defined.

s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -tMethods
ra
h n
Accounting Builder (continued)
no to make rule setup as flexible as possible, journal entries are split into components:
B In order
Descriptions, Line Types, and Account Derivation rules. The description can be on the entry or
its individual lines. You set up descriptions, as many as you want, by using pieces of data from
the transaction and constant values. For example, you might have an invoice showing the
event (invoice validation), the invoice number, type, date, description etc.
The Line Type is another component, actually one of the two main components of the entry.
The line type defines whether this is a debit or a credit, what the accounting class is, where the
amount should come from etc. Again, you set up as many as you need of these for a particular
entry. You can have a single invoice line or distribution create as many debits or credits as
needed.
The third major piece is the account derivation rule, which determines to which GL account a
line should be booked. There is a lot of flexibility around the account derivation rules. You
can simply set up a rule for each flexfield to be used, or you can make it more complex and
build each flexfield segment by segment by combining multiple rules. These rules can be
setup to derive the accounts or segment values from transactional data, including conditions of
when to use a particular rule versus another.

s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -tMethodsra
h n
Accounting Builder (continued)
o
B The ntransaction objects and the sources carry transaction information into the rules defined for
each component of an entry.
These components, for example, journal line type, account derivation rule, journal entry
descriptions, are attached together as a journal line definition for a particular event. For
example, you set up a JLD for an invoice validation event, another one for a payment creation,
another one for payment clearing. The set of such rules for a particular subledger application is
called the application accounting definition. And the set of AADs for multiple applications is
called the subledger accounting method.
Note that it is possible to maintain multiple accounting methods. You can set up as many
components as you like, and use them for different accounting methods. You can set up an
accounting method that creates entries in compliance with US GAAP, and another one with
IFRS. Because the JE components are modular, these two methods could share components,
such as entry descriptions.

The accounting methods is assigned to each ledger, which determines which rules are applied
when accounting is being generated for a particular ledger. If you have a setup with a primary
and a secondary ledger, you could have different accounting methods attached to and used for
each.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Online Accounting
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Accounting
- tra
h n
Online
o invoice entry window might show, for example an invoice that has been recorded
B The npayables
and validated. To generate the journal entries, access the actions button and select Create
Accounting options. You can:
• Create a draft entry generation
• Create the entry and post to GL straight off this window. This creates entries for the
invoice on all the related ledgers of this operating unit, that is, the primary ledger and any
associated reporting and secondary ledgers.
The invoice amount is converted to each of the ledger currencies, any exchange rate variance
on any of the ledgers is calculated and posted. Through the usage of business flows feature,
during accounting, you can to track back to the purchase order or receipt, and back out from
the same accrual accounts that were hit originally. By also getting the conversion rate from
that original booking, you can calculate the exchange rate variance accurately.

Inquiries
s a
)ha
c om
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu -tra
on
Bh • nNavigation:
Inquiries
Transaction view > Tools: View Accounting > JE inquiry
Transaction security in inquiries, reports, creating accounting

Inquiries
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Offline Accounting
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
a n u Accounting
- tra
h n
Offline
noaccounting is processed on a ledger basis. When submitted for the ledger Vision
B Offline
Operations (USA) all related ledgers, that is, reporting currencies and secondary ledgers are
also processed at the same time. When processing transactions for a ledger, you can also
enforce transaction security model of the subledger to accounting. When a user submits the
accounting process, you can have either all the transactions of the ledger process, or only the
transactions of the operating units/inventory organizations that the user has access to.

Standard Reports
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu Reports
- tra
h n
Standard
B Thisnisoa sample report created by the offline accounting program. It shows any errors
encountered during the process, and suggests the ways to correct the errors.
The Accounting report and other standard reports provided, such as journal entries report,
account analysis report, and third party balances report all utilize the XML technology and
allow you to change the layout of the reports, change the default sorting and grouping,
customize further by adding company logos and other things.

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Setup
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
a n u -tra
nonentry has three components: the description, line type, and account derivation rule.
Bh A journal
Setup
To setup your own rules, you can either define your components from scratch or you can copy
the components seeded by Oracle, and modify them. Note that rules and components seeded
by Oracle cannot be modified. Similarly, rules that you as a customer define will not be
overwritten or impacted at all during a future upgrade or patching.
When you want to modify the rules, after defining your own component, you must define all
the other components hierarchically above that specific component all the way to the subledger
accounting method so that you can supersede Oracle defined rules.

Setup - Journal Line Type
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Setup – Journal Line Type
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u – Journal
- tra Line Type
h n
Setup
o line type determines what kind of an entry to generate. It also determines the
B The njournal
accounting class and sets the conditions under which the rule creates a line. It also specifies the
values needed for line generation and controls behavior for certain feature, such as multiperiod
accounting.

Setup - Journal Line Type
s a
)ha
c o m
m ini ide
p ge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u – Journal
- tra Line Type (continued)
h n
Setup
o
B • nNavigation: Setup > Accounting Setups > Subledger Accounting Setup > Accounting
Methods Builder >Journal Entry Setups > Journal Line Types
1. Journal line type determines whether to create a debit entry, a credit entry, or an entry for
exchange gain/loss.
2. It also identifies the accounting class on the entry, such as Expense or Trade Liability.
3. It defines the conditions under which the rule will be executed to create a line.
4. It determines the values needed for entry line generation, such as amount, currency,
conversion rate information, which are called accounting attributes. That is, it defines
where the values for the entry should come from, which transaction data should be used.
5. It also controls behavior for certain features i.e. multiperiod accounting, business flows,
line merging and summarization

Setup - Account Derivation Rule
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Setup – Account Derivation Rule
s a
)ha
c o m
m ini ide
p ge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u – Accounting
- tra
h n
Setup Derivation Rule
o set up a separate rule for each flexfield to be used, or you can make it more complex
B Youncan
and build each flexfield segment by segment by combining multiple rules. These rules can be
setup to derive the accounts or segment values from transactional data, including conditions
under which to use a particular rule versus another.

Setup - Account Derivation Rule
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u – Account
- tra Derivation Rule
h n
Setup
o
Methods Builder > Journal Entry Setups > Account Derivation Rules
Multiple output values can be defined in a single rule, each with a condition and evaluation
order of the conditions, so that one value is returned under specific situations versus others. For
example, use a particular account if invoice distribution type is accrual, versus another account
if it is not.

Setup – Journal Entry Description
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u – Journal
- tra Entry Description
h n
Setup
o
Methods Builder > Journal Entry Setups > Journal Entry Descriptions
The final component that makes up a journal entry is the description. A description can be
assigned to the journal entry header itself, to the set of debits and credits; or different
descriptions can be assigned to each of the lines of the entry. For example, a description on the
liability entry containing information about the supplier, and a description on the item expense
line containing information about the item or expense itself.
Similar to the other journal entry components, you can define multiple descriptions and attach
conditions to each. The description can be built by using constants, transaction attributes, or a
combination of the two.

Setup – Journal Line Definition
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u – Journal
- tra Line Definition
h n
Setup
o components of a journal entry are grouped together as a journal line definition to
B The nthree
create the rule for a particular event type.

Setup - Journal Line Definition
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u – Journal
- tra Line Definition
h n
Setup
o
Methods Builder > Methods and Definitions > Journal Lines Definitions
The journal line type, its description, and its account derivation rules are all attached together
on the Journal line definition to define the rule creating an entry.
Here, we are looking at a sample definition for AP invoice validation event. We have several
line types defined to create each of the possible entry lines for an invoice validation, such as
backing out of the accrual, tax, exchange rate variance, freight expense, and liability. To each
of these, we have assigned a description, and one or more account derivation rules. Note that
for the liability line, we have two account derivation rules: one that generates the flexfield for
the liability account, and the other to overwrite the balancing segment on the flexfield derived.
This is an example of how multiple account derivation rules can be used to build complex
flexfield generation rules.

Setup – Application Accounting Definition
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u – Application
- tra
h n
Setup Accounting Definition
o define the rules for each event type of an application that you want to generate
B Afternyou
journal entries for, group them together under an application accounting definition. The
application accounting definition or AAD, is the collection of journal entry rules for an
application per specific accounting requirements or standards. For a corporation with activities
in multiple geographies, for example, US and Europe, there are separate AADs for, say
Payables, per the accounting standards in these geographies. There is a US GAAP AP AAD
and an IFRS AP AAD. If the standards are the same for a particular event type, for example,
for an invoice validation, then the same rule or JLD can be used under both the US GAAP and
IFRS AP AADs.

Setup - Application Accounting Definition
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u – Application
- tra
h n
Setup Accounting Definition
o
Methods Builder > Methods and Definitions > Application Accounting Definitions
After the definition is completed, the AAD is validated which basically ensures that the
mandatory setup to generate an entry is defined appropriately.

Setup – Subledger Accounting Method
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u – Subledger
- tra Accounting Method
h n
Setup
o
B The nsubledger accounting method is the collection of accounting definitions for all the
applications that you generate accounting for. Each primary and secondary ledger is associated
with a SLAM, which determines the accounting rules and standards that are applied when
generating entries for that ledger.
Oracle seeds a number of accounting methods to support standard accrual, cash basis
accounting, as well as accrual and cash basis encumbrance accounting and US Federal
accounting.

Setup - Subledger Accounting Method
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u – Subledger
- tra Accounting Method
h n
Setup
o
Methods Builder > Methods and Definitions > Subledger Accounting Methods
In the hierarchy of the SLA Accounting methods builder, each component under a SLAM must
share the same COA as the SLAM or be generic to COAs.

Ledger Setup and SLAM Assignment
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Ledger Setup and SLAM Assignment
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a n u Setup
- traand SLAM Assignment
h n
Ledger
nois a secondary ledger defined, as the transaction is being processed for accounting,
B If there
there is a separate journal entry generated for the primary and secondary ledgers, both
according to the accounting method on each ledger.

Setup – Set Key Profile Options
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u – Key - a Options
trProfile
h n
Setup
B Therenoare also a few key profile options that impact how accounting is generated through SLA
in R12. These are mainly options that impact data access and security. For example:
Should the general ledger data access set security be enforced when generating accounting, that
is, should journal entries be created if the user does not have ledger clearance even if the user
has multiorg access to the operating unit?.
Should the transaction security model be applied when drilling down from GL; that is, should
the user be allowed to inquire on journal entries of a certain operating units if the user does not
have MO access, but has ledger clearance?
If there are secondary ledgers and data access set security is enforced in the subledger module,
then you must assign an additional data access set to the user to enable access to the secondary
ledger.
Should the user be able to run certain reports across the data of multiple subledger
applications?
In addition to these, there are other new profile options introduced in R12 for subledger
accounting processing, that are mainly around troubleshooting. You can refer to the user
documentation for more information.

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
a n u -tra Considerations
onshows the flow of information from a subledger application to General Ledger
Bh The nslide
Implementation

Summary
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
c
Oracle E-Business a entTax
r la@ tud
k a
Overview
is S
a
Chapter 4 t h
bash u se
a u
n et o
( bh ns
a
rl le li c e
k a
asha sferab
u B an
ha on-tr
n
B n
Oracle E-Business Tax Overview

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Objectives
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

What is Oracle E-Business Tax (eBTax)
s a
)ha
c om
m ini ide
p ge Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
anuis E-Business
- tra Tax (eBTax)
h n
What
nois a new product that provides the infrastructure for tax knowledge management and
B eBTax
delivery using a global system architecture that is configurable and scalable for adding country
specific tax content. As the single point solution for managing transaction-based tax, Oracle E-
Business Tax uniformly delivers tax services to all E-Business Suite business flows through
one application interface.
Note to 11i customers: eBTax replaces the transaction tax solutions of Release 11i built into
the Oracle Payables and Oracle Receivables products. It also eliminates the need for Brazilian
Payables Tax solution (Brazilian AP/PO Tax). Latin Tax Engine of Release 11i for Order-to-
Cash transactions of Brazil, Argentina and Colombia is still supported in Release 12. From an
end users point of view, eBTax and the Latin Tax Engine are two mutually exclusive tax
engines, but the Latin Tax Engine does leverage some services of Oracle E-Business Tax
internally. Similar to Oracle E-Business Tax, tax lines calculated by Latin Tax Engine are also
stored in eBTax Tables. Tax Reporting of Latin Taxes is now being done using eBTax’s tax
reporting ledger interface tables.
Though eBTax is an entirely new product, customers upgrading from Release 11i are not
required to re-implement their tax setup. You can continue to get the same tax calculation
results as in Release 11i.

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Business Requirements Met by eBTax
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Requirements
- tra
h n
Business Met by eBTax
o Use Tax in Procurement
B Salesnand
• Allows the definition of jurisdiction-based taxes, such as US Sales and Use Tax
• Allows you to leverage US Sales Tax setup configured in Receivable in 11i to be used in
Payables
Self-Assessed Tax in Payables
• Allows you to self-assess (reverse-charge) taxes on your Payables invoices
Multiple Registrations
• Allows you to define multiple registrations for a Party or site for different taxes or
jurisdictions
Deferred Tax in AP
• eBTax allows you to account for recoverable taxes at the time and to the extent of
payment in Payables, similar to behavior in Receivables in 11i
Enhanced Handling of Tax on Freight
• Enhances handling of tax on Freight, with the ability to define different rules for freight

Enhanced Exemptions and Exceptions
• Allows you to define exemptions specific to a regime, tax or jurisdiction for a party
• Allows you to define exceptions specific to a regime, tax or jurisdiction by product fiscal
classifications
Multiple Inclusive, Compounding
• Allows you to define multiple inclusive taxes as well as supporting compounding taxes
and surcharges (i.e., tax on tax)
Quantity Based Rates in Procurement
• Allows the use of Quantity based Tax Rates to be unit based, e.g., $0.25 per US Gallon
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Business Needs Solutions
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Key Concepts: Tax Authority
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
a n u -tra Tax Authority
on is a government entity that regulates tax law, administers, and/or audits one or
Bh Tax nAuthority
Key Concepts:
more taxes. Some examples of Tax Authority:

• Brazil - Secretaria da Fazenda Estadual (State Revenue Office)
• Brazil - Secretaria da Receita Federal (Federal Revenue Office)
• California, USA - California State Board of Equalization
• Canada -Canadian Customs and Revenue Agency
• France - Ministry of Economy, Finance and Industry
• Germany - Federal Ministry of Finance
• India - Central Board of Customs and Excise
• Singapore -Inland Revenue Authority of Singapore
• United Kingdom - HM Customs and Excise

Key Concepts: Tax Regime
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
a n u -tra Tax Regime
on is the set of tax rules that determine the treatment of one or more taxes
Bh Tax nRegime
Key Concepts:
administered by a tax authority. Some examples of Tax Regime:

• Brazil - RICMS -> ICMS Regulation
• Brazil - RIPI -> IPI Regulation
• California, USA - California Sales Tax
• Canada - Canadian Goods and Services Tax
• India - Excise Tax
• Singapore - Singapore Goods and Services Tax
• United Kingdom - UK VAT

Key Concepts: Tax
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
a nu -tra Tax
Bh We can n Tax by a classification of a charge imposed by a government through a fiscal or
Key Concepts:
nodefine
tax authority. Some examples of tax:
Tax Regime: Taxes:

------------------------------------------------ ----------------------------------------------------
RICMS - Regulamento do ICMS ICMS, ICMS-ST (Tributary Substitution)
RIPI - Regulamento do IPI IPI
California Sales Tax State Sales Tax
California Sales Tax District Sales tax
Canadian Goods and Services Tax GST
Canadian Sales Tax PST
India Excise and Customs Excise Tax
Singapore Goods and Services Tax GST
UK VAT UK VAT

Key Concepts: Tax Jurisdiction
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a n u -tra Tax Jurisdiction
on
Bh Tax nJurisdiction
Key Concepts:
is a geographic area where a tax is levied by a specific tax authority. Some
examples of Tax Jurisdictions:
Tax Geographic Zone Jurisdiction
-------------- ----------------------- --------------------------------
ICMS São Paulo Sao Paulo ICMS
IPI Brazil Brazil IPI
State Sales Tax California (State) California State Sales Tax
County Sales tax San Francisco (County) SFO County Sales Tax
GST Canada Canada GST
PST Ontario Ontario PST
Excise Tax India India Excise Tax
GST Singapore Singapore GST
UK VAT UK UK VAT

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Architecture Overview
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
an u -trOverview
a
h n
Architecture
noE-Business Tax consists of a tax knowledge base, a variety of tax services that respond
B Oracle
to specific tax events, a set of repositories (for tax content and tax recording) that allow
customers to manage their local tax compliance needs in a proactive manner, as well as the
ability to integrate with external tax content providers through a single integration point.

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Processing Taxes for Transactions
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -tTaxes ra for Transactions
h n
Processing
no
B At transaction time, transactional applications within the Oracle E-Business Suite such as
Purchasing, Payables, Sales, Receivables etc. pass determining factors to eBTax. Determining
factors can also be derived from information available on the transaction and are the key
building blocks of the tax rules. They fall into four groups:
• Parties: Information about the party such as party classification, registration, exemptions.
For example:
- Legal Entities
- First and Third Party Ship From/To, Bill From/To, etc.
- First and Third Party Tax Registrations, Classifications
• Places: Information on the geography of places associated with the transactions such as:
- Party Locations
- Define and Validate Party Locations
• Products: Information on the types of goods and services on the transaction such as:
- Product Type (Physical Nature)
- Item Categories

- Fiscal Classifications
- Intended Use
• Processes: The types of transactions for which tax services are being requested, for
example:
- Document Type
- Transaction Business Categories
- Transaction Fiscal Classifications
This information is passed to Oracle E-Business Tax through a single and uniform product
interface. Then, eBTax:
• Determines tax regimes and applicable taxes.
• Determines Tax status.
a
• Identifies the appropriate tax rate belonging to the tax status and/or tax jurisdiction
as
)h
• Calculates tax amount by multiplying the taxable basis by the tax rate.
om
• Stores calculated taxes the form of tax lines in the tax repository. These tax lines have all
c
ini ide
necessary information needed for tax reporting.
g m
e Gu
At this point you can extract tax reports from the repository and display the date in formats
such as PDF, HTML and RTF as required.
c p
a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Tax Determination Services Example
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
u -tra Services Example
TaxnDetermination
a
Bh Shown n is a Receivables transaction. This example shows how Oracle E-Business Tax
nohere
answers some basic business questions during its Tax Determination process.
• Tax Regimes are identified based on the countries of the parties involved.
• A default value or a Place of Supply rule indicates the Place of Supply.

s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
TaxnDetermination
a
nonparty type value or a tax registration rule determines from which party (1st party or
Bh A default
3rd party) to evaluate tax registration status.
The party classification is derived from the parties available in the transaction (1st and 3rd
parties) and that classification can be compared to the ones used as tax determining factor in
any rule type.

s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
TaxnDetermination
a n
Bh In thenoTransaction Lines window, other types of information are relevant for tax calculation:
• Quantity times Unit Price is the default seeded Taxable Basis formula, but other formulas
can be defined.
• The item available in a given transaction line can potentially have one or more product
classifications, and these classifications can be used as a tax determining factor in any rule
type. The item itself or its classifications can also be used as part of Tax Exceptions
definition.

s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
TaxnDetermination
a n Tax Lines window, the Tax Rate times Taxable Basis is the default seeded Tax
Bh In thenoDetail
Amount formula, but other formulas can be defined.

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

User Interface
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an uInterface
- tra
h n
User
o Displays shortcuts to all required configuration set up tasks, including external
B • nHome:
dependencies.
• Tax Configurations: Use this tab to configure Tax Regimes, Taxes, Tax Statuses, Tax
Jurisdictions, Tax Recovery Rates, Tax Rates, Tax Rules
• Products: Create and/or modify Product Classifications, Intended Use Classifications, and
Tax Exceptions. A product fiscal classification is a classification of products, according to
their tax requirements, for tax determination and tax reporting purposes. A product fiscal
classification is based either on Oracle Inventory category sets or E-Business Tax product
categories.
• Parties: Create and/or modify Party Tax Profiles, Party Classification, and Legal
Classification Tax Usage
• Transactions: View and update Transaction Business Categories, Transaction Fiscal
Classifications, Document Classifications, User Defined Transaction Classifications,
Event Class Settings
• Defaults and Controls: Create and/or update Country Defaults, Tax Reporting Types,
Configuration Owner Tax Options, and Application Tax Options

• Provider Services: Create and view Service Mappings and Extensions
• Advanced Setup Options: View and modify Tax Lookup Codes, Tax Determining Factor
Sets, Tax Condition Sets, Tax Formulas, Tax Zone Types, Tax Determining Factors
• Requests: Schedule Requests or Request Sets, or Monitor Requests.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Upgraded and Redesigned Features
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Upgraded and Enhanced Features
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Tax Definition Hierarchy
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -traHierarchy
TaxnDefinition
a on
Bh • nResponsibility: Tax Managers
• Navigation: Tax Configuration > Tax Regimes
You can now define an entire tax setup hierarchy, starting from the definition of tax regimes,
then the taxes belonging to those regimes, the tax statuses belonging to each tax and lastly, the
tax rates associated to each tax status. In addition, tax jurisdictions and jurisdiction rates, can
also be defined for those taxes. The hierarchy gives ease of navigation, visualization and
maintenance.
• Instead of replicating choices for different Operating Units (OUs), you define which
regimes need to support recovery / Exemptions / Exceptions / Overrides
• Define Tax Regime level defaults that are common across all associated taxes. They can
be overridden at the tax level.
• A Tax is defined by a Configuration Owner. Though multiple OUs can share data by using
data defined by a common content owner, the upgrade process creates one content owner
for each tax
• A Tax is defined with a geography type (country / state, etc.) level to understand the
hierarchy across taxes

• Define granular controls at the tax level, instead of controlling the behavior at highest
level (OUs) or too low levels such as tax rate codes. They can be overridden at lower
levels.
• Instead of repeating taxes, define multiple jurisdictions for the same tax. e.g. US State
Sales Tax can have several state level jurisdictions
• A default Tax Status can de defined for a tax having one or more tax statuses. In the
absence of a Tax Status determination rule, the default Tax Status will be picked up. All
upgraded rate codes are associated with ‘Standard’ Tax Status
• Tax Rate Codes are upgraded with null jurisdiction. Jurisdiction based rates in US will be
upgraded in the context of Tax Status and Jurisdiction
• Define date effective period and/or navigate to details for Account information / lowest
level controls / defaults
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Tax Configuration Ownership
s a
)ha
c o m
m ini ide
p ge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
u -tra Ownership
TaxnConfiguration
a onRegimes created for 11i US (jurisdiction) based taxes, are made available as Common
Bh • nTax
Configuration to share data across OUs
• Tax Regimes created for 11i non US based taxes are made available as Party Specific
Configuration

Tax Defaulting Hierarchy
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
u -traHierarchy
TaxnDefaulting
a n Code/Group Code (defaulted) on taxable lines drives the applicability of tax rates
Bh The n11ioTax
for the given taxable line. In R12, the tax classification code (defaulted) on taxable lines drives
the applicability of one or more taxes using Direct Rate Determination rules.
For each OU, define the defaulting hierarchy for AP, PO, Projects, AR, and Expenses. Choose
a tax classification code for each source, such as customer account, item. Classify:
• Inventory Items
• Parties, Party Sites
Define Registrations for your Establishments and Third parties specific to Regime, tax, or
jurisdictions:
• Avoid replication of customer or supplier sites
• Define Product categories
• Define Transaction business categories
• Use combinations of the above factors and more in rules instead of a single drop through
hierarchy

System Options for Tax
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u Options
- tra for Tax
h n
System
o
B • nResponsibility: Tax Managers
• Navigation: Tax Managers > Defaults and Controls > Configuration Owner Tax
Options
11i Receivables System Options for Tax such as Rounding Options, Allow Overrides, etc.
upgrade to Configuration Owner Tax Options and Tax Attributes
• Provides more granular control
• Enables the definition of different values for different taxes under the same OU

Tax Groups
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
u -tra
TaxnGroups
a
non of tax codes that are grouped under tax group code in 11i is upgraded by creating
Bh Applicability
direct rate determination rules using condition based on the tax classification code that is same
as tax group code
• 11i Tax Codes are upgraded as Tax Rates under the appropriate Tax Regime, Tax, and
Tax Status
• 11i Tax Group Codes are not directly associated with tax rate %. They are used on taxable
lines to indicate applicability of multiple tax rates for the given taxable line.

Tax Jurisdiction Handling
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -tra Handling
TaxnJurisdiction
a on
• Navigation: Tax Configurations > Tax Jurisdiction
In 11i, geography, tax jurisdiction, and jurisdiction rates information were coupled together as
Location Values and Rates. The Sales Tax Key Flexfield was used for address validation but
also to obtain Sales Tax Location tax rates.
In 12, the upgrade process creates:
• Tax Zone Types based on 11i sales tax location structure and Geography types associated
with the structure
• Data to allow tax zones to include geographies within country and specific geography
types
• Tax Zones based on geography values for the geography type supported by the Zone
Type. The geographies that form the tax zone are then specified, based on the geography
types defined for the Tax Zone Type
Inner City jurisdictions can be specified, and are usually based on tax zones formed by postal
code ranges.

This new model allows for definition of “true” jurisdictions. For example, in the US, there are
more than 60,000 geographies, but only 7,000 jurisdictions. You can:
• Define multiple rates for a jurisdiction, for different statuses and rates
• Define zones for tax
• Define jurisdictions for zones
• Use zones for defining conditions, such as “Ship-to country in EU Zone”, etc.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Tax Compounding
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
ha
Bas nsfer
u -tra
TaxnCompounding
a
Bh In 11i,
noTaxn Compounding is supported for O2C flow transactions by turning ON the flag at AR
System Options. 11i Tax Groups in AR define the exact order of precedence in which taxes
(codes) are calculated and compounded.
In 12:
• From O2C tax codes/groups Regimes are upgraded to indicate cross Regime
compounding.
• Compounding precedence is stamped at tax level during upgrade based on the O2C tax
group level precedence.

Tax Inclusiveness
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -tra
TaxnInclusiveness
a on
• Navigation: Tax Configurations > Tax Jurisdiction > Set Invoice Values as Tax
Inclusive checkbox
The Customer and Customer Site Use level inclusive tax flag is maintained ‘as is’ and it is
displayed in the context party tax profile that is equivalent to customer / Customer Site Use
associated TCA Party / Party site.
In 11i for AP transactions, support for Inclusive Tax computation is turned ON at System
Options level. The Tax Inclusive flag is defined at the suppliers / sites level. The Inclusive flag
from supplier / site level gets defaulted to taxable lines and all applicable taxes are considered
inclusive / exclusive.
In 11i for O2C transactions, each tax code carries inclusive flag. Additionally, the customer
account / site uses also indicate whether taxes should be calculated inclusively.
In 12:
• The Tax code level inclusive flag is upgraded to corresponding tax rate code and also
taken to higher levels to Tax Regime, tax, and Tax Status.

• Taxes are upgraded as Inclusive / Exclusive based on P2P system option level indicator.
• Tax Rate Codes are upgraded as Inclusive / Exclusive based on O2C Tax Code level
indicator.
• Tax inclusive is defined at Regime, Taxes and Tax Rates levels
• Standard Inclusive Handling, Special Inclusive Handling and Standard Non-Inclusive
handling
• Tax Inclusiveness at Party / Party Site levels, in addition to account / site levels. Event
Class options level define order in which parties / registrations need to be checked for
inclusiveness
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Tax Recovery
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -tra
TaxnRecovery
a on
Bh • nResponsibility: Payables and Receivables
• Navigation: Payables > Invoices : Entry > Invoices > (B) All Distributions > (B) Tax
Distributions
• Navigation: Receivables > Transactions > Transactions > (B) Distributions
Tax recovery is the partial or full reclaim of taxes paid on the purchase or movement of a
product.
• In 11i, recoverable taxes are calculated using recovery rate % or rules specified at the tax
code level
• In 11i, recovery rate % is either directly associated with tax codes as default rates or
indirectly associated with tax codes using recovery rules
• 11i recovery determination applies one recovery % for each applicable tax. Since eBTax
supports applicability of two recovery rates, the 11i recovery rate % is upgraded as
recovery rate code for Primary recovery type and Secondary recovery type is kept null.

• In 11i, the Enable Recoverable flag and Default Recovery Rate are defined at Financials
System Options. This definition is upgraded as Recovery Controls at the Regimes, Tax,
Status and Rates levels
• Default Recovery Settlement can be defined at Tax, Status and Rates levels
• 11i recovery % is upgraded as % associated with recovery rate codes with ‘Standard’
Recovery Type.
• There are several recovery controls at the tax level. The 11i recovery rate % are upgraded
for Primary Recovery Type. The default recovery % associated at the 11i tax code level is
upgraded as default recovery rate code at tax and rate code levels
In R12, you can:
• Optionally define a Secondary recovery type for a tax and create recovery rates under it
• Leverage Intended Use and other determining factors to define recovery rules, rather than
using accounting based rules
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Tax Rounding
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -tra
TaxnRounding
a on
• Navigation: Parties > Party Tax Profiles
In 11i for P2P transactions, Rounding Rule and Rounding Level are defined at Supplier and
Supplier Site levels. In 11i for O2C transactions, Rounding Rule and Rounding Rule Override
are defined at Receivables System Options, Customers and Customer Site Use levels.
In R12:
• Rounding Rule and Rounding Level defined at Party Tax Profile for any 3rd party
• Rounding Rule and Rounding Rule Override defined at Regime and Tax levels,
independent of product
• Configuration Owner Tax Options have 4 levels of rounding precedence to indicate the
order in which party (ship from / ship to) level rounding options need to be evaluated.
The Default Rounding Level can also be defined at the Configuration Owner Tax Option
level.

Tax Overrides
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -tra
TaxnOverrides
a on
Bh • nResponsibility: Tax Manager
• Navigation: Defaults and Controls > Application Tax Options
Receivables System Options level control for allowing customer exemptions override are
upgraded to Applications Tax Options in the context of AR OU and receivables application.
• Override controls are specific to a configuration owner and event class.
• Overrides can be controlled at tax level, such as override for inclusive tax lines, tax
rounding and for calculated tax lines
• Allow Tax Rate Override setup defined in Tax Codes is upgraded to Tax Status
- Allow Tax Rate Override is defined at the Status level
• Allow Tax Rounding Override defined in Receivables System Options, Customer and
Customer Sites are upgraded to Party Tax Profile for first and third parties
- Allow Tax Rounding override can be defined at the Party Tax Profile level for any
party

• Inclusive Tax Override flag at tax code level in 11i is upgraded to tax rate code, Tax
Status, tax, and Tax Regime levels
• Override setup specific to a Configuration Owner and Application is defined at
Configuration Owner Tax Options
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Offset Taxes
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu Taxes
- tra
h n
Offset
o
B • nResponsibility: Tax Manager
• Navigation: Defaults and Controls > Configuration Owner Tax Options
Offset tax is a negative-rate tax used to fully or partially reduce another tax.
• ‘Tax’ level indicator is upgraded from 11i, based on the associated offset tax rate codes
• The Configuration Option indicates which event classes allow offset taxes. The Party Tax
Profile for the party indicated in offset tax base, carries the indicator from supplier/sites
• Taxes marked as “Set as Offset Tax” can be defined under the same Tax Regime where
regular tax is defined
• A Tax can be defined normally under the same Regime where the offset tax is created.
Either one can be defined first
• Any unassociated offset taxes are upgraded from 11i
• Applicable taxes for a Regime (whether regular or offset taxes) are identified

Party Tax Attributes
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an uTax Attributes
- tra
h n
Party
o
eBTax provides one single entity Party Tax Profile to hold party tax attributes. In R12, First
Parties information such as LE and Establishment is also upgraded to TCA. Customer Account,
Account Site, Site Uses, Suppliers, and Supplier Sites are associated with TCA Party / Party
Sites.
Tax attributes for third parties are either carried to party tax profile in the context of third party
/ third party site LE or displayed from the Party Tax Profile in the context of third party / third
party site.
All Party Tax attributes are upgraded as tax attributes belonging to Party Tax Profile or they
are classifications / reporting codes of Party Tax Profile

Multiple Tax Registrations
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -tra
TaxnRegistrations
a on
Tax registrations:
• Are usually issued for a company or establishment, by a legal/tax authority, for an specific
tax and within a certain tax jurisdiction
• Can be defined for 1st and 3rd parties. It is very important information since it can be used
in tax rules and tax reporting
• Can be defined at Regime, tax or tax jurisdictions levels.
• Tax registration numbers are usually validated to ensure accuracy and/or comply with
legal requirements.
• Single Tax Reporting Registration Number and Type can be defined at Party Tax Profile
for Vendors and Vendor Sites for backward compatibility
• Single Tax Registration:
- Is defined at Customer and Customer Site Uses levels for backward compatibility
- Is defined at Party tax profile for Legal Establishments for backward compatibility

• You can define:
- Multiple registrations for the same party and different regimes, taxes, or jurisdictions
- As complete tax registration information as needed for each registration
- A user-definable registration status value
• Use the registration status value in tax rules such as Place of Supply rules, Tax Status
rules, etc.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Tax Exemptions
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -tra
TaxnExemptions
a on
Bh • nResponsibility: Receivables
• Navigation: Transactions > Transactions > (T) Tax Exemption > (B) Lines
11i Exemptions definitions are upgraded to the newly defined Exemptions entity in Oracle E-
Business Tax.
• Exemptions always apply to a Party and a Tax Regime. They can optionally apply to a
Tax, Tax Jurisdiction, Tax Status and Tax Rate
• A tax Exemption usually has a certificate number, exemption reason, and status. It is
created in the context of Party/Site. 11i Item exemptions without the context of Party are
upgraded as Item Exceptions
• Exemptions are usually a discount or surcharge on the tax rate, but a special rate is also
possible. Upgraded Exemptions are created with discount on tax rate
• The Allow Exemptions flag is defined at Configuration Owner Tax Options
• The Allow Tax Exemptions is defined at Regime and Tax levels

• Party Exemptions are defined in the Exemptions page flow for the Party Tax Profile
• Item Exceptions can be defined under Exceptions page flow, outside the realm of tax
exemptions
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Tax Exceptions
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -tra
TaxnExceptions
a on
• Navigation: Defaults and Controls > Configuration Owner Tax Options
A tax exception is a special rate that applies to an item. A Tax exemption certificate is a
document obtained from a tax authority which certifies that a party, party site, or product is
either partially or fully exempt from a tax. Exceptions are defined for a Tax Regime and tax,
for an specific product item or to a product classification. It can optionally apply to a Tax
Jurisdiction, Tax Status, and Tax Rate.
• The Item Tax Rate Exception flag is obsolete in R12.
• The Allow Exemptions flag is defined at Configuration Owner Tax Options
• Item Exceptions are defined in the Exceptions page flow, under Products tab
• Item Exceptions apply to the Tax Regime and tax, for an specific product item or to a
product classification. It can also apply to a tax jurisdiction, status and tax rate
• Item Exceptions can be defined under Exceptions page flow, outside the realm of tax
exemptions
• Exceptions can apply to items or item classification

Tax Formulas
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -tra
TaxnFormulas
a on
• Navigation: Advanced Setup Options > Tax Formulas > (B) Create
The Taxable basis formula created during the upgrade indicates the usage of quantity as a
taxable basis instead of taking the line amount as the taxable basis.
A tax formula is a special calculation not covered by the standard calculations available in the
system. Examples of tax formulas are:
• To Calculate Taxable Basis
• To Calculate Complex Compounding Rules
• To Calculate Tax Amounts
You can define several formula types, including taxable basis, calculate tax amounts, tax
compounding formula, etc.
In R12:
• PL/SQL formulas defined in previous releases are not upgraded to the new model
• The PL/SQL formulas defined in 11i are obsolete
• Formulas can be defined for Regime and Tax

• Certain rule types such as Taxable Basis and Tax Amount are based on tax formulas
• During Upgrade Tax formulas are created for applying discounts or to indicate
compounding taxes.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Global Descriptive Flexfields
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Descriptive
- tra Flexfields
h n
Global
B • nTaxo related GDFs associated with first parties are upgraded as reporting codes with reporting type
as GDF segment name and they are created in the context of upgrade LE / Establishment
equivalent Party Tax Profile.
• Because the Latin Tax Engine still exists as a globalization solution, most of the LTE
related GDFs are maintained ‘as is’.
• Transaction (Header / Lines / Distributions) level GDFs (including LTE related) are
upgraded as named column in the context of the transaction (line / header / Distributions).
• Tax Line Level GDFs (including LTE related) are upgraded as named columns
• EMEA VAT reporting related GDFs that are meant to control preliminary / final reporting
modes will be detailed in EMEA solution.

Transaction Tax Upgrade
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu -trTax a Upgrade
h n
Transaction
notransactions, eBTax holds detail tax lines, summary tax lines and detail tax
B For AP
distributions in the context of AP transactions. For PO transactions, eBTax holds tax lines and
tax distributions.
In R12:
• There is one single repository with detail/fully allocated tax lines
• There is a Common Single repository for tax distributions in for procure to pay
transactions
• There are document level summary tax lines for Payables transactions
• Tax line IDs/Tax Distribution IDs are stamped on AR/AP tax lines for reconciliation with
product transactions
• Tax line IDs/Tax Distribution IDs from product transactions are carried to SLA for
Accounting reconciliation
• Calculated taxes are propagated to documents created in downstream flow

• Effective variance calculations are performed for AP transactions
• Consistent validations and controls for overrides are enforced on tax lines and
distributions
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

New Features
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Content and Services Subscription
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u and- a
trServices
h n
Content Subscription
o
• Navigation: Provider Services > Service Mappings
• Navigation: Provider Services > Service Extensions
Content Subscription
• Under Tax Regimes you can define the content subscription per tax regime, legal entity
and operating unit.
Services Subscription
• Tax services subscription can be configured under Services Mappings and Services
Extensions flows

Events and Configuration Owner Options
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
ha
Bas nsfer
an u and-tConfiguration
ra
h n
Events Owner Options
o
B • nResponsibility: Tax Manager
• Navigation: Tax Configuration > Tax Regimes
You can now define whether a Legal Entity or an Operating Unit will become a “content
owner” for a given Tax Content hierarchy and be responsible for defining and maintaining tax
content separately. When it makes sense to share and maintain tax content centrally to
streamline maintenance, tax content can be owned by a “Global Content Owner” and therefore
be shared among specified legal entities and operating units.
Configuration Owner Options:
• Hold tax configuration information for the configuration owner, application and tax event
class. Upgraded data comes from:
- Financial System Options for Tax such as Rounding Rule, Precision, Minimum
Accountable Unit, Default Tax Code, Default Recovery Rate, etc.
- AP System Options for Tax such as Enforce Tax from Account, Enforce Tax from
Reference Document, etc.
- AR System Options for Tax such as Rounding Options, Allow Overrides, etc.

• Can be defined for a Legal Entity or Operating Unit in the Tax Regimes flow
• For Product Exceptions can be defined as Common or Party Specific
• For Taxes and Rules can be defined as Common, Common w/ Party Overrides and Party
Specific
Based on the Configuration Options for the Regime, the user must select the Configuration
Owner, which can be ‘Global’ in case the configuration option is ‘Common’ or a party name,
when the option is ‘Party Specific’
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Tax Jurisdictions
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -tra
TaxnJurisdictions
a on
• Navigation: Tax Configuration > Tax Jurisdictions
Geography information is now defined in TCA’s Geography Hierarchy model. Tax
Jurisdictions are defined for taxes and geography information defined in TCA. Party locations
are also based and validated against the same Geography information. Geography information,
including geo-political geographies and user-defined geographies, is defined in TCA’s
Geography model.
Tax Jurisdictions are created for a geography type. Rates having different effective periods can
be defined in the same flow, and multiple jurisdictions can be define for a tax, as well as a
default one.

Tax Rules
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -tra
TaxnRules
a on
• Navigation: Tax Configuration > Tax Rules
Both guided and expert configuration flows are available

Fiscal Classifications: Product
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu Classifications:
- tra
h n
Fiscal Product
o
B • nResponsibility: E-Business Tax Manager
• Navigation: Tax Managers > Product > Product Classification > (B) Create
Several types of Product Fiscal Classifications can be defined for different purposes. Oracle E-
Business Tax can link Fiscal Classification Types with existing inventory categorization or the
user can create non-inventory classification types and codes. User can also define intended use
classifications.
• Variety of Fiscal Classifications being modeled
- Product (classification of goods or services for tax purposes)
• Integrated with other classifications within Oracle E-Business Suite
- Inventory Category Set to model Product Fiscal Classification and Intended Use
Defaults
• Fiscal Classification as a Tax Determining Factor
- An input that affects the outcome of a process. Tax determining factors are grouped
into tax determining factor sets and they are used to define tax condition sets and tax
rules.

Fiscal Classifications: Party
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
- tra
h n
Fiscal Party
o
• Navigation: Tax Managers > Parties > Party Classification > (B) Create
Several types of Party Fiscal Classifications can be defined for different purposes. Oracle E-
Business Tax can link Fiscal Classification Types with existing party categories in TCA and
associate those with specific tax regimes.
• A party fiscal classification is linked to TCA’s party classification
• The codes belonging to the party classification are displayed in a tabular format
• Variety of Fiscal Classifications being modeled:
- Party (classification of parties for tax purposes). For example, SIC (Standard Industry
Classification), NAICS (North American Industry Classification System), etc.

• Integrated with other classifications within Oracle E-Business Suite:
- TCA Party Classification to model Party Fiscal Classification
• Fiscal Classification as a Tax Determining Factor
- An input that affects the outcome of a process. Tax determining factors are grouped
into tax determining factor sets and they are used to define tax condition sets and tax
rules.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Fiscal Classifications: Transaction
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
- tra
h n
Fiscal Transaction
o
• (N) Tax Managers > Transactions > Transaction Fiscal Classification > (B) Create
Several types of Transaction Fiscal Classifications can be defined for different purposes.
Classifications such as Transaction Business Category can hold generic classifications whereas
Document Type or User-Defined classifications can be very specific to a tax regime.
• Transaction Fiscal Classifications can have one or more levels and must be associated to a
tax regime
• The classification codes are defined and displayed in a tabular format
Variety of Fiscal Classifications being modeled:
Classifications entered on Transaction
Intended Use
User Defined

Transaction Business Category
Derived from Transaction Business Category
Fiscal Classification as a Tax Determining Factor
An input that affects the outcome of a process. Tax determining factors are grouped into tax
determining factor sets and they are used to define tax condition sets and tax rules.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Tax Repository
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
u -tra
TaxnRepository
a ontax repository is a single source of transactional tax information (tax lines) for all
Bh • nThe
taxes calculated by E-Business Tax. It holds information about the calculated taxes, the
parties involved, etc. The repository is used to support processes such as tax reporting, tax
accounting and tax reconciliation. The repository is also the underlying infrastructure for
users to see and/or modify (override) the tax lines.
• An invoice line can have one or more tax lines associated to it, where detailed information
related to calculated taxes is captured

Tax Simulator
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
u -tra
TaxnSimulator
a on
Bh • nResponsibility: Oracle Tax Simulator
• Navigation: Oracle Tax Simulator > Tax Simulator
Tax Simulator is a very powerful tool where users can simulate different types of transactions
and immediately see the tax calculation results. This gives more flexibility and confidence to
test new or changed tax rules.
• It gives flexibility to test new and/or changed tax rules
• Simulator has the relevant fields available in a transaction but with much less validations
• Once the transaction lines are entered and taxes get calculated, they can be seen in the tax
lines summary page for each transaction line
• More detailed information can be seen for each tax line in the Detail Tax Line window
• All the rule types and rules that were invoked to generate each tax line can also be seen in
the Rules window
• For each process, the corresponding conditions can also be seen
Note: Tax Simulator emulates transactions, but does not trigger any real transactions

Guided Configuration
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u Configuration
- tra
h n
Guided
o belonging to multiple pre-defined rule types can be defined for a given tax
B • nRules
• Rules can be defined via guided (step by step) or expert (faster) flows
• Most rule types allow definition of default values, which get selected in case there are no
rules defined for the rule type
• The rules defined for all rule types can be seen in a hierarchical fashion, turning
maintenance easier and faster
• There are 5 general guided steps to define a tax rule:
1. General Information: A rule is usually generic, but it can be defined as being specific
to a transaction or geography as well.
2. Rule Conditions: User selects the various determining factors and values that will
form the rule conditions
3. Rule Results: User then selects the rule result for the rule type in question and all
previously selected rule conditions

4. Rule Order: User then defines the order in which this rule will be evaluated for the
rule type in question
5. Rule Templates
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Profile Options for Tax
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Options
- tra for Tax
h n
Profile
o
B • nResponsibility: System Administrator
• Navigation: System Administrator > Profile > System
11i Features carried into 12 include:
• Allow Ad Hoc Changes
• Allow Manual Tax Lines
• Allow Override of Customer Exemptions
• Allow Tax Classification Code Override
• Allow Tax Recovery Rate Override
• Inventory Item for Freight
• Invoice Freight as Revenue

Upgrade Considerations
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
anu Cosiderations
- tra
h n
Upgrade
B • n11ioTax Code/Name are used to name the R12 Tax, after removing any numeric portion
(i.e. VAT10 => VAT)
• Tax Status for upgraded records are derived as “Standard”
• 11i Tax Code is used to name the R12 Tax Rate

Implementation Information
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Summary
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
Oracle General c e t
a Ledger
n
r la@ tud
k a is S
a
Chapter 5
h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle General Ledger

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Objectives
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda – Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda – Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda – Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Accounting Setup
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -tSetupra – Description
h n
Accounting
o is a new fundamental concept in Release 12. The ledger replaces the 11i concept of
B The nledger
a set of books. It provides an accounting representation for one or more legal entities or for a
business need such as consolidation or management reporting.
Business enterprises can now clearly and efficiently model their legal entities and their
accounting representations. This is critical to the success of the shared service center and single
instance initiatives where many or all legal entities of an enterprise are accounted for in a
single instance, and data, setup, and processing must be effectively secured but also possibly
shared.
Legal Entities can be mapped to entire Ledgers or, if accounting for more than one legal entity
within a ledger, you can map a legal entity to balancing segments within a ledger.
While a set of books is defined by three components - chart of accounts, functional currency,
and accounting calendar, the ledger is defined by a fourth component: the accounting method.
This component allows you to assign and manage a specific accounting method for each
ledger. Therefore, when a legal entity is subject to multiple reporting requirements, separate
ledgers can be used to record the accounting information.

Accounting Setup
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u -tSetup
ra – Description (continued)
h n
Accounting
nocases, there is a primary ledger to act as the main record keeping ledger and one or
B In such
more secondary ledgers to retain alternate representations for the different reporting
requirements. Each secondary ledger can differ from the primary ledger by the chart of
accounts, calendar, currency, and accounting method.
Secondary ledgers can also be created with one of three levels of detail to fulfill your
accounting requirements. The subledger level records detail subledger transactions using the
Subledger Accounting functionality. The journal level records General Ledger journals in the
secondary ledger using General Ledger consolidation and posting, and balances only using
General Ledger consolidation.

Accounting Setup
s a
)ha
c o m
m ini ide
p ge Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu -tSetup
ra – Description (continued)
h n
Accounting
no Ledger is integrated with Subledger Accounting (SLA) to enable a unified process to
B General
account for subledger transactions and post data to General Ledger, and to provide a consistent
view when drilling down from General Ledger to subledger transactions.

Accounting Setup Benefits
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -tSetup
ra – Benefits
h n
Accounting
no support for
B Inherent
• Legal entity mapping
• Secondary ledgers
Increased efficiency
• Secondary ledgers are automatically populated from General Ledger functionality or
With SLA, data is populated into general ledger from subledgers from a centralized system.
This increases the consistency of how subledger data is being accounted for in General Ledger
as well as how you can drill down from General Ledger back into subledger transactions.

Accounting Setup Manager
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu -tSetup
ra Manager – Description
h n
Accounting
o
• Navigation: Setup : Financials : Accounting Setup Manager > Accounting Setups
The Accounting Setup Manager is a new feature that streamlines the setup and implementation
of Oracle Financial Applications. The Accounting Setup Manager facilitates the setup required
for simultaneous accounting for multiple reporting requirements.
With the Accounting Setup Manager, you can perform and maintain the following common
setup components from a central location:
• Legal Entities
• Ledgers, primary and secondary
• Operating Units, which are assigned to primary ledgers
• Reporting Currencies
• Subledger Accounting Options. This is where you define the accounting methods for each
legal entity subledger transaction and associate them to the ledger where the accounting is
stored.
• Intercompany Accounts and Balancing Rules

• Accounting and Reporting Sequencing
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Accounting Setup Manager Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
anu -tSetupra Manager – Benefits
h n
Accounting
no Setup Manager provides a centralized setup for Financials, providing increased
B Accounting
efficiency during setup and maintenance.

Accounting Setup Process
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u -tSetup
ra Process
h n
Accounting
noyou can use Accounting Setup Manager, you must complete the required General
B Before
Ledger setup steps.
Creating an accounting setup consists of the following steps:
1. Define Legal Entities. If you are not integrating with Oracle subledgers or are defining an
accounting setup that does not require a legal entity context, then you can skip this step.
2. Assign none, one or multiple legal entities to an accounting setup.
3. Define a primary ledger by specifying a name, chart of accounts, calendar, currency, and
optionally a subledger accounting method.
4. Optionally assign one or more secondary ledgers. Secondary ledgers can differ from the
primary ledger in any or all of the following:
- Chart of accounts
- Calendar
- Currency
- Subledger Accounting Method

5. Optionally, you can create reporting currencies and assign to the primary and/or the
secondary ledger if you want to maintain multiple currency representations.
6. Define the Accounting Options by specifying the journal processing options and
transaction processing options for the setup components in this accounting setup.
7. Mark the accounting setup complete. This prevents certain changes to your accounting
setup and launches the GL Accounting Setup Program that makes your setup components
ready for data entry.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
Bh Before n can use Accounting Setup Manager, you must complete the required General
Implementation
noyou
Ledger setup steps. At the very least, you must define a chart of accounts, accounting calendar,
and enable currencies.

Agenda – Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Multiple Currency Support For General Ledger Data From All
Sources
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
an u -tra
BhMultiple n
noCurrency Enhancement
In Release 11i, Multiple Reporting Currencies (MRC) were used to maintain subledger
transactions and General Ledger journals in a different reporting currency.
In Release 12, this has been renamed the feature to “Reporting Currencies” and simplified the
setup. Reporting Currencies are integrated with ledgers. Instead of creating an additional ledger
for each reporting currency, you specify the reporting currency as a part of the ledge.
You can now maintain additional currency representations at three different levels:
• Balance level: Maintains translated balances. When running translation in General
Ledger, balances are stored in a balance level reporting currency.
• Journal level: Balance Journal level is a currency representation of only your General
Ledger journals and balances. When posting a journal in General Ledger, the journal will
be converted to one or more journal level reporting currencies.

• Subledger level: Subledger level is a complete currency representation of your subledger
transactions, General Ledger journals entries and balances. Every time you enter a
subledger transaction or enter and post a journal directly in General Ledger, the same
transaction and journal are converted to one or more associated subledger level reporting
currencies.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Sources
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
an u -tra
BhMultiple n
noCurrency Enhancement (continued)
Reporting Currencies are not the same as secondary ledgers. As mentioned before, ledgers
consist of a chart of accounts, calendar, accounting method, and currency.
• If you only need multiple currencies to support your reporting requirements, use reporting
currencies.
• If you need to account for your data using different calendars, charts of accounts,
accounting methods in addition to currency, use a secondary ledger.

Sources Benefits
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
an u -tra
BhMultiple n
noCurrency Enhancements (continued)
The new multiple currency enhancements provide increased visibility and support more
flexible reporting capabilities.

Sources Process
s a
)ha
c o m
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
an u -tra
BhMultiple n
noCurrency Support For General Ledger Data From All Sources Process
When you define a journal level reporting currency, the journal conversion rules determine
which journals will be converted to the reporting currency by the General Ledger Posting
program. For example, journal conversion rules are defined to have the source/category
combination “Manual/Adjustment” be converted to the reporting currency, then any journal
that uses that source/category combination will automatically be converted to the associated
reporting currency.
Balance level reporting currencies are different. Balance level reporting currencies obtain their
balances from the General Ledger Translation program. Thus, every time translation is run, the
translated balances are reflected in the balance level reporting currency.

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u -tra Considerations
on
Bh • nResponsibility:
Implementation
General Ledger
• Navigation: Setup > Financials > Accounting Setup Manager > (T) Accounting
Setups >Primary Ledger > Add Reporting Currency
The first step is to define a reporting currency for a primary ledger or secondary ledger.

Agenda – Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Entered Currency Reporting and Analysis Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Currency
- tra Reporting and Analysis
h n
Entered
no 11i, when you performed an account inquiry or ran a report using the currency
B In Release
assigned to the ledger, you viewed balances for amounts entered in the ledger currency as well
as foreign currencies that were converted to the ledger currency.
Now in Release 12, the entered ledger currency balances are tracked separately from the
foreign entered and converted balances.
You can use the entered ledger currency amounts for viewing balances for the purposes of
currency valuation and hedging
• FSG reporting
Navigation: Reports > Request > Standard, Submit the request called Program -
Publish FSG Report
• Online account inquiry
Navigation: Inquiry > Account
• Recurring Journals
Navigation: Journals : Define > Recurring
• Mass Allocations
Navigation: Journals : Define > Allocation

Entered Currency Reporting and Analysis Description
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Currency
- tra Reporting and Analysis (continued)
h n
Entered
no Assume a ledger and the ledger currency is USD.
B Example:
Two journals are entered and posted; one in 1,000 US Dollars, and another in 500 British
Pounds that gets converted to 1200 US Dollars.
In Release 11i, you can review the 500 GBP and the 1200 USD that results from converting the
500 GBP, and the total 2200 USD which is the USD balance in the Cash Account. The $2200
is the sum of the $1000 entered in USD and the $1200 converted from the 500 British Pounds.
However, you view that a 1000 USD were entered directly in USD.
In Release 12, you can view the 1000 USD by performing an account inquiry on the Cash
account for balances entered only in the ledger currency. The amounts entered in foreign
currencies that were converted to the ledger currency are not included in the balance. You can
still retrieve all balances in USD, both the entered as well and the converted.

Entered Currency Reporting and Analysis Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u Currency
- tra Reporting and Analysis (continued)
h n
Entered
o have better information about your currency to perform currency valuations and
B Younnow
hedging.
You also have more flexibility in creating allocations because now you can allocate amounts
based on entered ledger currency balances instead of only total ledger currency balances.

Entered Currency Reporting and Analysis Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
Bas nsfer
an u Currency
- tra Reporting and Analysis – Setup and Process
h n
Entered
noup is required to use this feature.
B No set
Oracle General Ledger automatically tracks balances that have been entered in the ledger
currency separate from balances converted to the ledger currency. The entered ledger currency
balances are available immediately once balances are posted.

Agenda – Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Foreign Currency Recurring Journals Description
s a
)ha
c o m
m ini ide
p ge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Currency
- tra Recurring Journals
h n
Foreign
no 11i, you could define recurring journals using the functional currency or STAT
B In Release
currency.
In Release 12, you can create recurring journals using foreign currencies. This is useful if you
need to create foreign currency journals that are recurring. For example, assume a subsidiary
that uses a different currency from its parent borrows money from the parent. The subsidiary
can now generate a recurring entry to record monthly interest payable to the parent company in
the parent’s currency.

Foreign Currency Recurring Journals Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Currency
- tra Recurring Journals - Benefits
h n
Foreign
o currency recurring journals, you are no longer restricted to using the ledger
B Withnforeign
currency or stat. You can use any currency which means more flexibility in defining recurring
journals and generating your allocations and journals more efficiently.

Foreign Currency Recurring Journals Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
on
Bh • nNavigation:
Implementation
Journals > Define > Recurring
You must set up foreign currency recurring journals, define a recurring journal, and a foreign
currency and conversion rate type.

Agenda – Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Data Access to Multiple Legal Entities and Ledgers Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uAccess- trtoa Multiple Legal Entities and Ledgers
h n
Data
B In 11inoyou had to have one responsibility per set of books and could not restrict read or write
access. You also saw two main configurations of legal entities: one legal entity in a set of
books or multiple legal entities in a set of books. The single legal entity - single set of books
model excelled in data security, and the multiple legal entity - single set of books model
excelled in information sharing and processing efficiency. In R12, Data Access Sets were
created to enhance information access sharing and security in both configurations in order to
combine the benefits of both configurations.
Data Access Sets provide new access and security features that allows you to grant and secure
access to ledgers, or portions of the ledger, by its balancing segment values or management
segment values. If a balancing segment value is assigned to a ledger, then you can secure
access to specific balancing segment values. Furthermore, if you have balancing segment
values assigned to a legal entity, then you can secure access to specific legal entities.
Data Access Sets allow you to access multiple legal entities and ledgers from a single
responsibility. Securing Data Access Sets is covered later in this presentation.

s a
)ha
c o m
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uAccess- trtoa Multiple Legal Entities and Ledgers (continued)
h n
Data
no more than one ledger to a Data Access Set, you can access multiple ledgers from
B By assigning
a single responsibility.
Here, you see two ledgers assigned to a single Data Access Set, a European ledger and an Asia-
Pacific ledger. With this configuration you can view, enter and post journals, view and update
balances, and view and run reports, among other processes, for both ledgers.
This type of implementation is useful for a shared service centers where you have accountants
entering data for multiple subsidiaries that each use their own ledger.

s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uAccess
- trtoa Multiple Legal Entities and Ledgers (continued)
h n
Data
o search, view, modify, and create journals for any ledger for which you have access as
B Youncan
defined in your responsibility’s Data Access Set.
When modifying a journal batch, you must have write access to all ledgers that are used in the
particular batch.
Note: Once a journal is saved, you cannot change the ledger associated with the journal.

Data Access to Multiple Legal Entities and Ledgers Benefits
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uAccess- trtoa Multiple Legal Entities and Ledgers - Benefits
h n
Data
no multiple ledgers to a Data Access Set provides increased efficiency because you do
B Assigning
not have to change responsibilities to access different ledgers within the Data Access Set. The
ability to access multiple ledgers enables cross-ledger account inquiry, reporting, and journal
processing.

Data Access to Multiple Legal Entities and Ledgers Process
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uAccess
- trtoa Multiple Legal Entities and Ledgers Process
h n
Data
no to use a Data Access Set, you must assign it to a General Ledger responsibility using
B In order
the GL: Data Access Set profile option.
A Data Access Set may be used in various processes.

Data Access to Multiple Legal Entities and Ledgers Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uAccess
- trtoa Multiple Legal Entities and Ledgers Setup
h n
Data
o
B • nNavigation: Setup : Financials > Data Access Sets
There are two different methods to define and use Data Access Sets:
• Whenever you define a ledger, such as a primary ledger or secondary ledger, or define a
journal-level or subledger-level reporting currency, the system automatically creates a
Data Access Set that includes full read and write access to the ledger or reporting
currency.
• You can also define your own Data Access Set. This option allows you to grant broader
access to multiple ledgers and restrict access to ledger data at a more granular level.
In order to use a Data Access Set, you must assign it to a General Ledger responsibility using
the GL: Data Access Set profile option.

Data Access to Multiple Legal Entities and Ledgers Setup –
Assign Data Access Set
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
an u -tra
on to Multiple Legal Entities and Ledgers – Setup and Process
BhData nAccess
In order to use a Data Access Set in General Ledger, you must assign it to the new profile
option called GL: Data Access Set.
Note: If a user is responsible for General Ledger and Oracle subledgers, the Data Access Set
should include the ledger that is assigned to the GL Ledger Name profile option, which
controls ledgers used by subledger applications. This will ensure that subledger transactions
will be transfer data to the appropriate ledger in Genera Ledger.

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Agenda – Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Multi-Ledger Processing Description
s a
)ha
c o m
m ini ide
p ge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -trProcessing
a
h n
Multi-Ledger - Description
o of multi-ledger processing resides in a new feature called Ledger Sets. Conceptually,
B The nheart
a ledger set is merely a grouping of ledgers that share the same chart of accounts and
calendar/period type combination. Ledger sets should not be confused with Data Access Sets.
Ledger sets merely group ledgers together for processing; you cannot specify read-only or read
and write access to the ledgers in a ledger set. You can assign a ledger set to a Data Access Set
if you want more options for securing access to a ledger set.
By defining a ledger set, you can perform the following GL processes across multiple ledgers
simultaneously:
• Opening and closing periods
• Creating period-closing journals, mass allocations, and recurring journals
• Translating balances
• Viewing journals and balances using account inquiry
• Financial Reporting, including both standard reports and FSG reports.

In the previous section we saw a preview of “multi-ledger” processing for manual journal
processing; with journals you can create, view, and modify journals for multiple ledgers for
which you have access in your Data Access Set. The Ledger Set feature enhances Data Access
Sets by allowing you to run processes for multiple ledgers simultaneously.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Multi-Ledger Processing Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u -trProcessing
a
h n
Multi-Ledger
B • nYouo can save time because you are able to perform operations such as opening and closing
periods, producing year-end closing journals and running translations across multiple
ledgers simultaneously.
• You have greater control of your processes because now you can control your processes
for multiple ledgers regardless of your accounting setup.
• You can keep all ledgers in sync by keeping them on the same close schedule by closing
all the ledgers in a Ledger Set at the same time.

Multi-Ledger Processing
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
an u -trProcessing
a
h n
Multi-Ledger (continued)
o is executed as follows:
B The nprocess
1. Open the Submit Requests form and select a program to run.
Responsibility: General Ledger
Navigation: Reports : Request > Standard
2. Select a ledger set and fill in all other options as desired; if you do not have sufficient
access to all of the ledgers in the ledger set you will not be able to select the ledger set for
processing. If you do not have sufficient access privileges, choose a different concurrent
program or select another responsibility that has full access to all the ledgers in the ledger
set.
3. Submit your request.
Note: When generating programs for a ledger set, multiple child requests are spawned, one for
each ledger in the ledger set.

Multi-Ledger Processing Process – Simultaneous Opening and
Closing of Periods
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
an u -tra
non Processing (continued)
BhMulti-Ledger
• Responsibility: System Administrator
• Navigation: Concurrent > Requests > (B) Submit a New Request > Choose Open
Period
You can open and close periods across multiple ledgers simultaneously by using ledger sets.
Several enhancements have been made to the open and close periods programs:
• You can now submit open and close processes from the Concurrent Manager or the
Submit Request form. When specifying the open or close program, you can specify a
ledger set to have the periods for all ledgers in the ledger set be opened or closed in a
single
• A new gapless close period program has been created. This program allows you to specify
a target period to close. Any open periods between the last closed period and the target
period are closed
• A Permanently Close Period program has been created. In order to permanently close a
period, the period’s status must be closed

Multi-Ledger Processing Process – Simultaneous Year-End
Closing Journals
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
an u -tra
non Processing – Simultaneous Year-End Closing Journals
BhMulti-Ledger
• Navigation: Concurrent > Requests > (B) Submit a New Request > Close Process -
Create Income Statement Closing Journals
• Navigation: Concurrent > Requests > (B) Submit a New Request > Close Process -
Create Balance Sheet Closing Journals
Through the use of ledger sets, you can now run the two closing journals programs for one or
more ledgers simultaneously.
• Run the Income Statement Closing Journals program to transfer year-end revenue and
expense accounts to the Retained Earnings account for multiple ledgers in a single
submission.
• Run the Balance Sheet Closing Journals program to close out the YTD balances of
balance sheet accounts across multiple ledgers at once.
Data Access Set security ensures that only users with full read and write access to ledgers can
successfully submit the programs.

Multi-Ledger Processing Process – Simultaneous Currency
Translation
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
an u -tra
non Processing – Simultaneous Currency Translation
BhMulti-Ledger
• Navigation: Currency: Translation
Another feature you can leverage through the use of Ledger Sets is Translation, which allows
you to translate balances for multiple ledgers simultaneously. You can do this through the
Translate balances form or by submitting the Translation program from the Submit Request
form. This allows you to more efficiently schedule your translation process during your critical
close.

Multi-Ledger Processing Process – Financial Reporting Across
Ledgers
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
an u -tra
non Processing – Financial Reporting Across Ledgers
BhMulti-Ledger
• Navigation: Reports : Request : Financial -> Individual Reports
From the Run Individual Reports form you can specify a single ledger or a ledger set at
runtime when generating FSG reports. To leverage the use of ledger sets with FSG reports, you
must define a ledger set with a default ledger assigned. Running standard reports with ledger
sets does not require a default ledger be assigned to the ledger set.
When you submit your FSG or standard report request, specify the ledger set and a separate
report will be run for each ledger in the ledger set. You can also run reports in the Single
Request Submission (SRS) form.
• Navigation: Concurrent : Request : (submit a new request) Program - Run Financial
Statement Generator
The parameters for the Run Financial Statement Generator program that you submit from the
Submit Request form are the same as in the Run Individual Reports . You can specify a single
ledger or a ledger set when submitting FSG reports from the Submit Request form.

Multi-Ledger Processing Setup
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -trProcessing
a
h n
Multi-Ledger Setup
o a Ledger Set. Only ledgers that share the same chart of accounts and accounting
B • nDefine
calendar can be grouped in a ledger set.
- Navigation: Setup : Financials > Ledger Sets
• Assign the Data Access Set to the profile option, GL: Data Access Set. The system
automatically creates a Data Access Set with the same name as your Ledger Set’s name.
- Responsibility: System Administrator
Navigation: Profile > System

Agenda – Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Financial Reports Across Ledgers Description
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu Reporting
- tra Across Ledgers - Description
h n
Financial
noSets allow you to aggregate data across multiple ledgers in the ledger set.
B Ledger
Here is an example of the output from an FSG report. The total column represents the
aggregated or summarized balances across multiple ledgers. This report is generated with the
rows representing the accounts and the columns representing the ledgers; the total column
represents the total across the ledgers using a ledger set.

Financial Reports Across Ledgers Benefits
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
a nu Reporting
- tra Across Ledgers - Benefits
h n
Financial
o instantly summarize data across multiple ledgers in a single FSG report. This provides
B Youncan
greater control and visibility into your global operations because you can easily spot check the
performance of your entities by running one report.
Another added benefit with ledger sets is that they essentially allow you to perform real-time
consolidation. If you have fairly simple consolidation needs, then you could use ledger sets.
For example, if you are only using Oracle Financials on a single database instance and you do
not acquire or dispose of companies on a regular basis or have partial ownerships, then you can
use ledger sets to perform real-time consolidation. All you need to do is use a different
balancing segment value or ledger to house your consolidation entries and then group that
ledger into a ledger set.

Financial Reports Across Ledgers Process
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
a nu Reporting
- tra Across Ledgers Process
h n
Financial
B Whennoyou submit your FSG report, specify the ledger set and the report will aggregate the data
for the ledger set. The difference between running individual reports and an aggregate report
using a ledger set lies in the FSG report definition. When the column or row of the report
definition includes a ledger set, the system automatically aggregates the data across ledgers in
that ledger set for you.

Financial Reports Across Ledgers Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu Reporting
- tra Across Ledgers Setup
h n
Financial
o
• Navigation: Set up: Financials > Ledger Set
To leverage the use of ledger sets with FSG reports, you must have a ledger set defined with a
default ledger.
You must then define an FSG report that includes data from multiple ledgers in a single report.
The data in each ledger can be displayed in a separate row or column. Data can also be
aggregated across multiple ledgers into a single row or column by specifying the ledger set for
that row or column.

Agenda – Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Cross-Ledger and Foreign Currency Allocations Description
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a n u -traand Foreign Currency Allocations - Description
n been several enhancements to MassAllocations.
Bh Therenohave
Cross-Ledger
As mentioned earlier, a single responsibility can now access data for multiple ledgers.
Therefore MassAllocations has been enhanced to allow you to create cross-ledger allocations
where the data from one or more source ledgers can be allocated to one or more target ledgers.
One example of this is allocating corporate or regional expenses to local subsidiaries when
each subsidiary has its own ledger.
Support for foreign currency allocations is also expanded. You can now create allocations in
foreign currencies. When specifying the calculation lines, you can also choose different
currency options. One currency option is to allocate existing converted amounts for the foreign
currency balance. The second option is to calculate the converted amount for allocation based
on a rate type provided.

Cross-Ledger and Foreign Currency Allocations Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu -traand Foreign Currency Allocations - Benefits
onsave time by creating a single allocation definition that can be executed for multiple
Bh Youncan
Cross-Ledger
ledgers instead of creating a different allocation for each ledger individually.

You now have more flexibility when defining MassAllocations. You can allocate amounts
across different ledgers. You also have more flexibility when allocating foreign currency
amounts because now you can select the treatment for converted amounts. These features allow
you to manage your allocation process across your entire enterprise rather than according to
your accounting setup.

Cross-Ledger and Foreign Currency Allocations Setup and
Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -tra
non and Foreign Currency Allocations – Setup and Process
BhCross-Ledger
• Responsibility: General Ledger
• Navigation: Journals : Define > Allocation
The setup and processing of MassAllocations in R12 is similar to the setup process in 11i,
except that you have a few additional options that you can specify when defining and
generating your allocation.

Agenda – Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Streamlined Automatic Posting/Reversal Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
a nu -trAutomatic
a
h n
Streamlined Posting and Reversal
no Posting has been streamlined to allow you to share AutoPost Criteria Sets across
B Automatic
multiple ledgers that share the same chart of accounts, calendar, and period type. This allows
you to reuse a single AutoPost definition to post journals for multiple ledgers.
In the same manner, AutoReversal has been streamlined to allow you to share AutoReversal
Criteria Sets across multiple ledgers. This allows you to reuse a single AutoReversal definition
to reverse or to reverse and post journals for multiple ledgers.
Note: Autoreversal Criteria sets can be shared across ledgers regardless of the COA and
calendar.

Streamlined Automatic Posting/Reversal Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
a nu -trAutomatic
a
h n
Streamlined Posting and Reversal - Benefits
o of streamlined automatic posting/reversal include less setup and maintenance.
B The nbenefits
Instead of defining a different AutoPost or AutoReversal Criteria Set for each ledger, you can
just define one and reuse it for multiple ledgers.

Streamlined Automatic Posting/Reversal Setup and Process
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
a nu -trAutomatic
a
h n
Streamlined Posting and Reversal – Setup and Process
no the AutoPost feature, you must define an AutoPost Criteria Set and assign multiple
B To utilize
ledgers or ledger sets to the AutoPost Criteria. When you run or schedule the AutoPost
program, the program posts journals for multiple ledgers.
• Navigation: Setup : Journal > AutoPost
To utilize the AutoReversal feature, you define the AutoReversal Criteria Set and then assign it
to each ledger using Accounting Setup Manager. When you run the AutoReverse program, the
program reverses journals based on the reversal criteria defined.
• Navigation: Setup : Journal > AutoReverse

Agenda – Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Integrated Web-based Spreadsheet Interface Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
a n u -Web-based
tra
h n
Integrated Spreadsheet Interface - Description
no the integration with Web ADI (Application Desktop Integrator), you can now
B Through
leverage spreadsheet functionality in Oracle General Ledger via a web-based interface. Launch
the spreadsheet interface from a General Ledger responsibility.
Using the Journal Wizard, you leverage spreadsheet functionality to create actual, budget, or
encumbrance journals. You can take advantage of spreadsheet data entry shortcuts such as
copying and pasting or dragging and dropping ranges of cells, or even using formulas to
calculate journal line amounts. You can then upload your journals to Oracle General Ledger.
Before uploading, you can save and distribute your journal worksheets for approval.
You can also import data from text files into spreadsheets, where it can be further modified
before uploading to Oracle. This functionality is useful when migrating data from legacy
systems, or from any source that can produce delimited files.

Using the Budget Wizard, you can download budget amounts to a spreadsheet, modify the
amounts, and then upload them back. You can also choose to download the actual amounts to
compare it with the budget amount. Budget Wizard also allows you to plot graphs and do a
graphical comparison on the amounts. Budget Wizard also provides budget notes. You can add
descriptions to accounts and amounts in your budget and explain your budget within the budget
worksheet, avoiding the clutter of external documentation.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Integrated Web-based Spreadsheet Interface Benefits
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
a n u -Web-based
tra
h n
Integrated Spreadsheet Interface - Benefits
o use all the features in Excel to create journals or enter budgets. You can customize
B Youncan
layouts to configure the information you want displayed in your spreadsheet. Spreadsheets can
be saved to the desktop, worked on when not connected to the network, and uploaded to Oracle
Applications when back on the network. In addition, spreadsheet data can be easily saved and
redistributed, making it easier to share and review work. You can also enter recurring journal
entries by saving a journal worksheet, then uploading it whenever appropriate, such as every
month.
Another benefit is reduced costs. Because users are already familiar with Excel, you can reduce
training costs because they never need to leave their desktop environment to enter journals or
budgets. You can also keep IT costs down because Web ADI is centrally deploy and managed
over the web. You do not have to install any client/server applications.

Integrated Web-based Spreadsheet Interface Setup and Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
a n u -Web-based
tra
h n
Integrated Spreadsheet Interface – Setup and Process
o
• Navigation: Journals > Launch Journal Wizard
• Navigation: Budgets > Launch Budget Wizard
To use the new Web ADI Journal Wizard and Budget Wizard feature, you need to set the
profile option for Default Desktop Viewer to the Excel version that you are using. You can
launch both the Journal Wizard and the Budget Wizard from a General Ledger responsibility.
You can then select a layout to determine the data entry screen to be displayed. For the Budget
Wizard, you also need to select a budget to download. After the excel spreadsheet is launched,
you can enter the data into the spreadsheet and upload it.

Agenda – Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Journal Copy Description
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -Journal
tra Copy
h n
Automatic
o now copy:
B Youncan
• Entire journal batches
• Journal batches with any status
The system creates a new journal batch containing the same journal entries.You may also
change the batch name, period, and/or effective date while copying the journal batch. After
copying the journal batch, you may modify the unposted journals in the same manner as any
manually created journals.

Journal Copy Benefits
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -Journal
tra Copy - Benefits
h n
Automatic
no of the automatic journal copy include:
B Benefits
• Increased journal entry speed
• Reduced data entry errors

Journal Copy Setup and Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u Copy
- tra
h n
Journal
o
• Navigation: Journals > Enter > Select Journal Batch > (B) Autocopy
There is no setup required. To copy a journal batch you need to select the journal batch, select
the AutoCopy Batch button, and then specify the new batch name, period, and effective date.
You can then make changes to the copied batch and journal.

Agenda – Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Streamlined Consolidation Mappings Description
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
a nu -trConsolidation
a
h n
Streamlined Mappings
o
B • nNavigation: Setup : Accounts > Chart of Accounts Mapping
Chart of Accounts Mapping replaced the Release 11i Consolidation Mappings feature. A chart
of accounts mapping is a set of instructions for mapping accounts or entire account segments
from one chart of accounts to another chart of accounts. You can use chart of accounts
mapping for consolidation purposes and for secondary ledgers.
The enhancement in R12 allows you to define mappings between charts of accounts instead of
between sets of books, so that they can be shared across multiple Consolidation Definitions.
Therefore, if you have multiple Consolidation Definitions for parent and subsidiary ledgers that
share the same chart of accounts pair, and their mapping rules are the same, you only have to
define a single Chart of Accounts Mapping.
You can also secure access to chart of accounts mappings using definition access set security.
This allows you to secure which users can view, modify, and/or use chart of account mappings
in consolidation definitions.

s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
a
h n
Streamlined Mappings - Description
B Chartnofo accounts mappings may be used with the Global Consolidation System for the
purposes of consolidation, or they may be used to propagate journals and balances from the
primary ledger to secondary ledgers defined in the Accounting Setup Manager.

s a
)ha
c om
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a
h n
Streamlined Mappings - Description
no of the options you have when mapping two charts of accounts.
B Example
• You can assign a single value that will be used for the target segment.
• You can copy all values from a source chart of accounts segment to the same values in
your target segment
• And you can use rollup rules to map a range of values from one chart of accounts segment
to a target segment value.

Streamlined Consolidation Mappings Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
a
h n
Streamlined Mappings
o of Accounts Mappings you can reduce setup and maintenance for increased
B WithnChart
efficiency.

Streamlined Consolidation Mappings Setup and Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
ha
B as nsfer
a
h n
Streamlined Mappings – Setup and Process
o
• Navigation: Setup : Accounts > Chart of Accounts Mapping
The setup consists of defining the chart of accounts mapping. If you are using the chart of
accounts mapping to map data from a primary ledger to its secondary ledger, then you must
assign the chart of accounts mapping to the secondary ledger using Accounting Setup
Manager. Subledger Accounting and General Ledger reference the chart of accounts mapping
when propagating data from the primary ledger to the secondary ledger. If you are using a chart
of accounts mapping for consolidating data using the Global Consolidation System, then you
must assign the mapping to the Consolidation Definition. Global Consolidation System uses
the chart of accounts mapping assigned to the consolidation definition when transferring data
from a subsidiary ledger to its parent ledger.

Agenda – Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Replacement for Disabled Accounts Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a n u -trafor Disabled Accounts - Description
onfeature helps prevent errors due to disabled or end-dated accounts when interfacing
Bh Thisnnew
Replacement
data to General Ledger and creating the accounting in Subledger Accounting. You may
designate an alternate account for your disabled or end-dated accounts. Subledger accounting
and General Ledger will then use the alternate account when processing.

Replacement for Disabled Accounts Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
a n u -trafor Disabled Accounts - Benefits
n accounts increases processing efficiency by reducing processing errors from
Bh Usingnoalternate
Replacement
disabled or end-dated accounts.

You no longer need to manually correct journal import errors caused by disabled accounts;
disabled accounts are automatically replaced by the Create Accounting program in Subledger
Accounting and the General Ledger Journal Import program.

Replacement for Disabled Accounts Setup and Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u -trafor Disabled Accounts – Setup and Process
on
Replacement
General Ledger
• Navigation: Setup : Accounts > Combinations
When you disable or end-date an account in the General Ledger Accounts window, you can
provide an alternate account. Subledger Accounting and General Ledger Journal Import
automatically use the alternate account if they encounter a disabled or end-dated account.

Agenda – Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Management Reporting and Security Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
a n u -traReporting Security – Description
Bh Therenois na new management segment qualifier for the chart of accounts. Typically, you would
Management
qualify a segment to be the management segment if that segment has management

responsibility. For example, a line of business, cost center, or product line. The added benefit
of using a management segment is that you can now secure management segment values using
data access sets. So you can grant read only or read and write access to specific management
segment values to prevent certain managers from viewing and updating data for cost centers,
lines of business, or product lines outside of their management authority.

Management Reporting and Security
s a
)ha
c o m
m ini ide
p ge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu -traReporting Security – Description (continued)
non This is the cost center organizational hierarchy. Director A has cost center OU97,
Bh Example:
Management
Director B has OS69 and Director C has OX53.

By assigning the cost center segment as the management segment, read and write access can be
secured to certain management segment values based on the cost center manager.
For example, Director A has read and write access to only cost center OU97. Director A does
not have access to Director B’s or Director C’s cost center or to the Vice President’s cost
center.

s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
a n u -traReporting Security – Description (continued)
onPresident, on the other hand, would have full read and write access to cost center
Bh The nVice
Management
0683 which is the parent of the direct reports. Thus, the Vice President has full access to all
direct reports’ data.

s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a n u -traReporting Security – Description (continued)
on the way for the management ledger. By utilizing a management segment, you can
Bh Thisnpaves
Management
now leverage a management ledger that could be used to enter management adjustments.
The primary ledger holds the day-to-day transactions for cost centers OU97, OS69 and OX53.
The management ledger only holds management adjustments.
Many companies prefer to keep their day-to-day operational accounting data pristine. By
having a separate management ledger to enter the management adjustments, you can preserve
the integrity of your operational ledger.
The management ledger has cost centers OU97, OS69 and OX53 owned by different cost
center managers. By securing management segment values using data access sets, you can
ensure that each cost center manager can only enter adjustments or view data for the cost
center that he is responsible for.
The management ledger by itself would not be very meaningful because it only holds the
management adjustments. By combining the results of the primary ledger with the management
ledger using a ledger set, you can obtain a complete management view of your results for use
in management reporting and analysis.

Management Reporting and Security Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
a n u -traReporting Security - Benefits
onmanagement segment qualifier in combination with data access sets paves the way for
Bh The nnew
Management
management reporting and analysis.

You can restrict access to different management segment values and assign them to different
managers in your organization.

Management Reporting and Security Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu -traReporting Security – Setup
on
Management
General Ledger
• Navigation: Setup : Financials : Data Access Sets
Designate a segment of your chart of accounts as your management segment. Define a data
access set secured by management segment values within a ledger or across ledgers in a ledger
set. Assign the data access set to a responsibility, and the security will take effect for that
responsibility.

Agenda – Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

Data Access Security for Legal Entities and Ledgers Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uSecurity
- traand Access to Multiple Legal Entities and Ledgers - Description
h n
Data
o sets allow you to limit access to the data by legal entity, ledger, or portions of the
B Datanaccess
ledger, such as its balancing segment values or management segment values. If a balancing
segment value is assigned to a ledger, then you can secure access to specific balancing segment
values. If you assigned balancing segment values to legal entities, then securing access to
balancing segment values essentially secures access to the legal entities.
• Full Ledger Access means you have access to the entire ledger. You could choose to grant
read-only or read and write access to ledgers.
• Specific BSVs means you can only access one or more balancing segment values for that
ledger. You can specify read-only, read and write access, or a combination of the two for
different balancing segment values.
• Specific MSVs means you can only access one or more management segment values for
that ledger. You can specify read-only, read and write access, or a combination of the two
for different management segment values

Note that Segment Value Security Rules provide similar functionality that restricts access to
segment values. The main difference between segment value security and data access set
security is the granularity of security. Segment Value Security can be used for any segment and
allows you to include or exclude segment values from a responsibility. Segment Value Security
is defined at the chart of accounts level so if a responsibility has access to multiple ledgers that
share the same chart of accounts, then all ledgers will need to follow the same security rules.
For example, if you exclude access to BSV 01 for one ledger, then it will affect all ledgers
assigned to the same responsibility that use the same chart of accounts.
Data Access Sets provide much more flexibility and granularity by allowing you to grant read
only or read and write access to ledgers and balancing segment values or management segment
values assigned to the ledger. If a responsibility has access to multiple ledgers that share the
same chart of accounts, then you can tailor the access to restrict the balancing segment values
for one ledger but allow it for another ledger.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uSecurity
- traand Access
h n
Data to Multiple Legal Entities and
B no
Ledgers – Description (continued)
Example of data access set security in the context of entering a journal:
• If you have read and write access to the entire ledger, then you can enter and post journals
to all Balancing Segment Values for the ledger.
• If you have read and write access to only some Balancing Segment Values for the ledger,
then you will only be able to enter and post journals for those Balancing Segment Values.
When viewing a journal, you only need read access to the Balancing Segment Values
contained in the journal lines. Any journal lines that contain Balancing Segment Values that
you do have read access to will not appear in the journal entry, but the credits and debits will
still display the correct totals and balances.
When modifying a journal batch, you must have write access to all ledgers or Balancing
Segment Values that are used in that batch.

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uSecurity
- traand Access
h n
B no
Note: Access is granted at the responsibility-level by assigning the GL: Data Access Set
profile option to each GL responsibility.
Example 1: A Data Access Set having full ledger access to a ledger. The ledger called US
Corporate has three balancing segment values assigned to it that represent each of the three
different legal entities for this ledger, US East, US West, and US South.
Here, we have specified read-only access for this ledger, so you are only able to view existing
journals, view balances, and view reports for all three balancing segment values. You cannot
update balances for this ledger.

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uSecurity
- traand Access
h n
B no
Example 2: A Data Access Set that secures access by Balancing Segment Values. The same
ledger called US Corporate is assigned to this Data Access Set. You can specify read-only
access to Balancing Segment Value 01, but specify read and write access to the other two
balancing segment values.
Thus, for US East (Balancing Segment Value 01), you can only view journals, view balances
and view reports. You cannot enter journals or update balances for Balancing Segment Value
01.
For Balancing Segment Values 02 and 03, for which you have full read and write access, you
can do everything.

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uSecurity
- traand Access
h n
B no
By assigning more than one ledger to a Data Access Set, you can access multiple ledgers from
a single responsibility.
Example 3: Two ledgers assigned to a Data Access Set, a European ledger and an Asia Pacific
ledger. By assigning read and write privileges to both ledgers, you can do everything for both
ledgers.
You can also secure each ledger by assigning read-only or read and write access to different
ledgers assigned to the same Data Access Set.

Data Access Security for Legal Entities and Ledgers Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uSecurity
- traand Access to Multiple Legal Entities and Ledgers - Benefits
h n
Data
o sets provide greater flexibility and control in securing access to ledger
B DatanAccess
information. You can control which users can access data in ledgers or portions of the ledger,
such as its balancing segment values or management segment values at a more granular level.
You can grant read only or read and write privileges.
This feature is especially beneficial for shared service centers where a single group of users
enter data for multiple ledgers. You could limit access to a legal entity’s or ledger’s data for
one user but grant broader access to another user.

Unauthorized reproduction or distribution Chapter
prohibited
5 - PageCopyright©
100 2009, Oracle and/or its affiliates
Data Access Security for Legal Entities and Ledgers Setup and
Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -tra
on and Access to Multiple Legal Entities and Ledgers – Setup and
BhData nSecurity
Process
Every time you create a ledger or assign journal level or subledger level reporting currency to a
ledger using Accounting Setup Manager, the system automatically creates a data access set for
you with full read and write privileges to the ledger and its balancing segment values and
management segment values. You cannot modify the system-generated data access sets.
You only need to define your own Data Access Set if you want to restrict access to a legal
entity’s or ledger’s data.
• Responsibility: General Ledger
Navigation: Navigation: Setup : Financials > Data Access Sets
To use a data access set, you must assign it to a General Ledger responsibility using the GL:
Data Access Set profile option.
Navigation: Profile > System

prohibited
5 - PageCopyright©
You can assign either the system generated data access set or the one you manually created.
Navigation: Security : User> Define
If you assign multiple General Ledger responsibilities to a user that accesses different data
access sets, then that user has access to the superset of all combined Data Access Sets.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

prohibited
5 - PageCopyright©
Agenda – Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

prohibited
5 - PageCopyright©
Journal Reversal Enhancements Description and Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Reversal
- tra Enhancements – Description
h n
Journal
o no longer reverse journals from frozen sources defined in the journal sources form.
B Youncan
If the journal is created from a frozen source, the journal cannot be modified even if the source
is subsequently unfrozen in the future.
This provides streamlined data reconciliation with subsystems. Not being able to reverse
journals that originated in subledgers ensures that the account balances will always tie out with
General Ledger. If you need to reverse a subledger journal, then you should do so in Subledger
Accounting or the subledger application.
You also can no longer reverse unposted journals. This ensures data integrity and better
auditability. In the past, there was a risk that the original journal could be deleted so you could
end up reversing something that didn't exist. Now, all reversals can be tied back to the original
posted journal.

prohibited
5 - PageCopyright©
Journal Reversal Enhancements Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Reversal
- tra Enhancements - Setup
h n
Journal
no is required.
B No setup

prohibited
5 - PageCopyright©
Agenda – Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

prohibited
5 - PageCopyright©
Control Accounts Description and Benefits
s a
)ha
c o m
m ini ide
p ge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Accounts
- tra – Description and Benefits
h n
Control
noaccounts are accounts that can only be used by Oracle subledgers, such as Oracle
B Control
Payables, Receivables, and Inventory. Control accounts cannot be used to enter manual entries
in GL. By specifying an account as a control account, you can ensure that their balances are
consistent with General Ledger balances for the same account combination.
This allows you better control by ensuring that only the authorized sources are using specific
accounts.
This should also improve reconciliation because it prevents imbalances from occurring
between the subledger balances and GL balances.

prohibited
5 - PageCopyright©
Control Accounts Setup and Process
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Accounts
- tra – Setup and Process
h n
Control
B Whennodefining your natural account values in the Segment Values form, you can designate an
account as a control account. You can select the journal source for which data can originate
from for each control account. SLA and GL verify that only data from the specified source can
be posted to the control account.

prohibited
5 - PageCopyright©
Agenda – Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

prohibited
5 - PageCopyright©
Security for Definitions Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u for-tDefinitions
ra
h n
Security - Description
B Manynoof General Ledger’s definitions and setup components can be shared across multiple
users, ledgers and charts of accounts. For some customers, this is highly desirable because they
only need to define the definition or setup component once and then share it across the
organization.
Other customers would prefer to secure specific setup components and definitions from users.
For example, FSG reports can be shared across ledgers that share the same chart of accounts.
Any user could view and make changes--even delete FSG reports as long as they have access
to the FSG report components in their menu function. Today, companies have no way to
prevent users from changing an FSG report.
Thus, in R12 there is a security feature called Definition Access Sets that allow you to secure
setup components and definitions, such as FSG reports, Mass Allocations, Recurring Journals,
and Calendars to name a few. For each definition, you can grant one of three privileges:
Use Access allows a user to use or generate a definition. For each definition, use access means
a little something different. For example, in FSG, use access refers to submitting the FSG
report. For Recurring Journals, use access means generating the recurring journal.

prohibited
5 - PageCopyright©
View Access allows a user to view the definition. So using Recurring Journals as an example, a
user may be able to view the recurring journal formulas and amounts, but they may not
necessarily be able to generate it to update balances for a ledger.
Modify Access allows a user to modify or change the definition. By default, if you have
Modify access, then you also get view access.
Note that the definition access set security feature is independent from Data Access Sets.
Definition Access Sets secure definitions while data access sets secure access to data. Both
work together. For example, a user may be able to generate a recurring journal based on his
Definition Access Set but must also write access to the ledger and balancing segment values
contained in that journal in order to generate a valid journal entry.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

prohibited
5 - PageCopyright©
Security for Definitions
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
ra
h n
Security
no and setup components that can be secured using definition access sets.
B Definitions

prohibited
5 - PageCopyright©
Security for Definitions - Example
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
ra
h n
Security - Example
B Herenisoan example where you can secure some definitions, such as allocations and recurring
journals.
You can assign privileges such that the General Ledger Clerk can use the Rent Allocation
definition but doesn’t have the privilege to view or modify it. He can also use and view the
Recurring Rent definition but doesn’t have the privilege to modify it. On the other hand, the
controller can view and modify both definitions, without having the privilege to generate it.

prohibited
5 - PageCopyright©
Security for Definitions Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
ra
h n
Security - Benefits
no Access Sets provide you greater control. You can limit users from using, viewing,
B Definition
and modifying definitions. By only granting access to definitions to selected individuals, there
is less change of errors or accidental deletions of important definitions, such as FSG reports.
Because Definition Access Sets are independent of Data Access Sets, you can secure access to
definitions independently of the data access.
You now have more flexibility in securing your definitions. If you want a definition to be
shared then you don’t need to secure it using definition access sets. On the other hand, if you
want to restrict access, then you can optionally secure the definition using Definition Access
Sets.
Definition Access Sets enable companies that have implemented a Shared Service Center to
better secure key setups and definitions that are shared by default.

prohibited
5 - PageCopyright©
Security for Definitions Setup and Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
ra
h n
Security – Setup and Process
o
• Navigation: Setup : Financials : Definition Access Set > Assign
To use this feature, you need to first define a definition access set and assign it to
responsibilities in the Definition Access Set page. When you want to secure a definition, check
the Enable Security checkbox on the definition form, and click on the Assign Access button to
assign it to a definition access set and grant the level of access you want. When a user tries to
access a definition or setup, General Ledger checks the level of access the user has.

prohibited
5 - PageCopyright©
Agenda – Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

prohibited
5 - PageCopyright©
Accounting and Reporting Sequencing Description
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -tand ra Reporting Sequencing - Description
h n
Accounting
no 11i, document sequencing sequentially numbered documents upon creation.
B In Release
In Release 12, sequential numbering has been enhanced to better support sequencing
requirements in countries, such as Asia, Latin America, and Europe.
There are now two new Journal Sequencing options:
• Accounting Sequencing: Automatically assigns a sequence number to General Ledger
journal entries that are posted in General Ledger. There’s also an option to sequence
subledger journals when they are completed in Subledger Accounting.
• Reporting Sequencing: Use to sequence both General Ledger journals and subledger
journals when the General Ledger period is closed. This feature replaces the Accounting
Engine (AX) legal sequencing and Libro Giornale features.
You can assign mutually exclusive sequences based on ledgers or reporting currencies, journal
sources, journal categories, and balance types.

prohibited
5 - PageCopyright©
Accounting and Reporting Sequencing Benefits
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -tand ra Reporting Sequencing - Benefits
h n
Accounting
o new journal sequencing options, you can now better meet legal requirements in
B Withnthe
different countries, such as Europe, Asia and Latin America. Fiscal authorities can now easily
verify the completeness of a company’s accounting records.
You have much more flexibility in choosing how they want to sequence journals based on
different criteria.
You no longer need to worry about localizations. The former Accounting Engine (AX) legal
sequencing and Libro Giornale features have now been included in the base product. This
allows more customers to take advantage of this new feature.

prohibited
5 - PageCopyright©
Accounting and Reporting Sequencing Setup and Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu -tand ra Reporting Sequencing – Setup and Process
h n
Accounting
o
• Navigation: Setup : Financials : Sequences : Accounting > Define
You can define the accounting sequence in the context of a ledger in Accounting Setup
Manager. Or, you can also create and manage your sequencing rules using the new Accounting
Sequencing menu function. For Accounting Sequences (posting event), the General Ledger
journals are sequenced when they are posted in General Ledger and Subledger journals are
sequenced when completed in Subledger Accounting. For Reporting Sequences (period close
event), General Ledger journals and subledger journals are sequenced when a General Ledger
period is closed.

prohibited
5 - PageCopyright©
Agenda – Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

prohibited
5 - PageCopyright©
Journal Line Reconciliation Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Line - a
trReconciliation
h n
Journal - Description
o feature, you can reconcile journal lines that should net to zero, such as suspense
B Withnthis
accounts, or payroll and tax payable accounts in countries like Norway, Germany, or France.
You can selectively cross-reference transactions in General Ledger with each other by entering
reconciliation reference information at the journal line level. When the balance for a group of
journals is zero, the journals can be automatically marked as reconciled.
This feature was formerly known as General Ledger Entry Reconciliation feature, which was
part of the Oracle Financials Common Country Features in Release 11i. It has now been
incorporated into the core product in Oracle General Ledger for Release 12.

prohibited
5 - PageCopyright©
Journal Line Reconciliation Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
an u Line- a
trReconciliation
h n
Journal - Benefits
o Line Reconciliation, journal lines that should net to zero can be reconciled
B WithnJournal
automatically. This results in faster close cycles because it eliminates the need to perform
manual reconciliations. No country-specific localizations are needed because we’ve included
this feature in the base General Ledger product. This means many more customers can take
advantage of this feature.

prohibited
5 - PageCopyright©
Journal Line Reconciliation Setup and Process
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Line- a
trReconciliation
h n
Journal – Setup and Process
o the feature by first selecting the Journal Reconciliation option when defining the
B Younenable
ledger, and then setting the Reconciliation flag to ‘Yes’ on the natural account value that needs
to be reconciled. To reconcile journal lines, you need to provide the reconciliation reference
either when creating accounting in Oracle Subledger Accounting (SLA) or when entering the
journal in General Ledger. You can then reconcile the lines automatically or manually in the
Reconcile Journal Lines form in General Ledger.

prohibited
5 - PageCopyright©
Agenda – Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

prohibited
5 - PageCopyright©
Enhanced Intercompany Description
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -Intercompany
tra
h n
Enhanced - Description
o R11i Global Intercompany System and Intercompany Balancing features have been
B Bothnthe
enhanced in R12. The previous ‘Global Intercompany System’ feature in General Ledger is
now a separate product called Advanced Global Intercompany System and includes many
enhancements. With Advanced Global Intercompany System, you can continue to enter
intercompany transactions at the GL level as well as create intercompany invoices in AP and
AR.
The previous ‘Intercompany Balancing’ feature in General Ledger is now called Intracompany
Balancing and is used consistently across Subledger Accounting and General Ledger to
balance journals within a legal entity. You can also balance cross-entity journals by defining
Intercompany Accounts for the legal entities that act as trading partners.
The balancing rules now support encumbrance journals too. Unbalanced encumbrance journals
can be automatically balanced using intercompany and intracompany balancing rules.

prohibited
5 - PageCopyright©
Enhanced Intercompany Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -Intercompany
tra
h n
Enhanced - Benefits
nouser interface is provided for defining balancing rules. You now have better control in
B A new
defining intercompany and intracompany balancing rules through consistent application of
Intercompany Accounts and Intracompany Balancing Rules in both Subledger Accounting and
General Ledger. The balancing rules now support encumbrance journals too. Efficiency is
increased since unbalanced encumbrance journals can be automatically balanced using
intercompany and intracompany balancing rules.

prohibited
5 - PageCopyright©
Enhanced Intercompany Accounting and Balancing Rules
Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

prohibited
5 - PageCopyright©
Enhanced Balancing Process – Intracompany Journals
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u -Intercompany
tra
h n
Enhanced – Intracompany Journals
no
B For Intracompany journals, the Journal Mode is used to determine the interaction between
balancing segment values on a journal. In this example, companies refer to balancing segment
values.
• 1 to 1: Is where only two companies or balancing segment values are used in the journal.
One with a net debit balance and the other with a net credit balance.
• 1 to Many: Is where one company has a net debit balance, and two or more companies
have a net credit balance. The debit balancing segment is the driving segment, or the
segment with which all the other balancing segments are trading.
• Many to 1: Is where one company has a net credit balance, and two or more companies
have a net debit balance. The credit balancing segment is the driving segment.
• Many to Many: Is where two or more companies have a debit balance and two or more
companies have a credit balance. Because there is no automated way to determine the
trading relationships on this type of journal, Many to Many journals must balance using a
clearing company (another balancing segment with which each balancing segment
balances) or using the Default Rule.

prohibited
5 - PageCopyright©
The balancing API handles all situations, even if there is a mixture of both Intercompany and
Intracompany lines on the transaction, it follows the correct rules when it generates the
balancing lines (balancing the Intercompany accounts first, and then any Intracompany
accounts after).
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

prohibited
5 - PageCopyright©
Enhanced Intercompany Accounting and Balancing Rules Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
anu -Intercompany
tra
h n
Enhanced Accounting and Balancing Rules Setup Responsibility:
B no
General Ledger
• Navigation: Setup > Financials > Flexfields > Key > Segments > (B) Segments >
Position cursor on the Description line > (B) Open > (B) Flexfield Qualifiers >
Intercompany Segment Enabled
Create a legal entity, assign it to a Ledger in Accounting Setup Manager. Assign Balancing
Segment Values to the Legal Entities to take advantage of the new Advanced Global
Intercompany System. You can also map Balancing Segment Values directly to the ledger,
where BSVs are used to represent organizations with no legal entity context.
• Enable Intracompany Balancing under the Ledger setup option in Accounting Setup
Manager.
• Create Intercompany Accounts to generate Intercompany accounting entries for cross-
legal entity journals.
• Create Intracompany Balancing Rules to balance journals with BSVs that belong to the
same legal entity or ledger.

prohibited
5 - PageCopyright©
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
Bh The nGLonPosting program and the Create Accounting program in Subledger Accounting call the
Implementation
AGIS Balancing API to balance journal lines across balancing segment values. If the balancing
segment values represent different legal entities, then the Intercompany Accounts are used. If
the balancing segment values are assigned to the same legal entity or ledger, then
Intracompany Balancing Rules are used to balance the journal.

prohibited
5 - PageCopyright©
Summary
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non

prohibited
5 - PageCopyright©
s a
)ha
c om
m ini ide
p ge Gu
Oracle Fixed c a Assets
en t
r la@ tud
k a is S
a
Chapter 6
h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Oracle Fixed Assets
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Objectives
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Subledger Accounting Architecture Description
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Subledger Accounting Architecture Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u -Accounting
tra
h n
Subledger Architecture Benefits
o
B The nflexibility of the accounting rule setup allows meeting different requirements in different
legislative, geographic or industry contexts within a single instance. Assuming operations in
multiple countries, each with its own legal requirements and accounting standards, you are able
to define a setup to meet each of the requirements. SLA allows for multiple accounting
requirements for a single transaction or business event.
The accounting data that is generated is viewable and provides full auditability.
Oracle Fixed Assets

Subledger Accounting Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -Accounting
tra
h n
Subledger Process
o is executed as follows:
B The nprocess
• Enter transactions in Oracle Assets
• Run the Create Accounting Program to process accounting.
• Inquire and drilldown from SLA Pages
Oracle Fixed Assets

Subledger Accounting Architecture Summary
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Subledger Accounting Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u -Accounting
tra
h n
Subledger Architecture Setup and Process
o
B • nResponsibility: Assets
• Navigation: Create Accounting
The key setup steps are:
• Compile the Application Accounting Definition in SLA (Optionally modify the
Application Accounting Definition)
• Complete the Accounting Setup flow in General Ledger
Oracle Fixed Assets

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Enhanced Mass Additions for Legacy Conversions Description
s a
)ha
c om
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -Mass tra Additions for Legacy Conversions Description
h n
Enhanced
no have been added to the FA MASSADDITIONS interface table to enhance the mass
B Attributes
additions functionality.
Oracle Fixed Assets

Enhanced Mass Additions for Legacy Conversions Description
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Enhanced Mass Additions for Legacy Conversions Benefits
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu -Masstra Additions for Legacy Conversions Benefits
h n
Enhanced
o use the mass additions process to convert data from a previous asset system. Instead
B Youncan
of loading the asset information into multiple Oracle Assets tables, load it into the
FA_MASS_ADDITIONS table. The Post Mass Additions process can then be used to move
the asset information from the table to Oracle Assets. After placing your data in this table, you
run the Post Mass Additions program to perform the data import.
Oracle Fixed Assets

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Automatic Preparation of Mass Additions Description
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Automatic Preparation of Mass Additions Benefits
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -Preparation
tra
h n
Automatic of Mass Additions Benefits
o benefits of this feature are that you can:
B The nmajor
• Avoid manual intervention during the Mass Additions prepare process
• Avoid customization and use public APIs to effect custom business logic
Oracle Fixed Assets

Automatic Preparation of Mass Additions Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Automatic Preparation of Mass Additions Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Automatic Preparation of Mass Additions Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u -Preparation
tra
h n
Automatic of Mass Additions Setup
o
B • nResponsibility: Assets
• Navigation: Setup:Asset System > QuickCodes
Setup Quickcodes in Oracle Assets.
Oracle Fixed Assets

Automatic Preparation of Mass Additions Setup Quickcodes
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u -Preparation
tra
h n
Automatic of Mass Additions Setup Quickcodes
nothe Rules to Prepare Mass Additions in Quickcodes:
B Set up
• Use Default: The Asset Category is derived based on the Asset Clearing Account if there
is a one to one match in the Asset Category setup. The Expense account is derived based
on the Clearing Account by replacing the natural account segment from the Asset
Category.
• Use Custom: The Prepare Mass Additions program will use the custom logic coded in the
Public API
• Use Custom Energy: Energy industry specific custom rule.
Oracle Fixed Assets

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Flexible Reporting Using XML Publisher Description
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Flexible Reporting Using XML Publisher Description
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Benefits
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Flexible Reporting Using XML Publisher Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Flexible Reporting Using XML Publisher Example XML Output
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu Reporting
- tra Using XML Publisher Example XML Output
h n
Flexible
B Thisnisothe new output using the XML publisher.
Oracle Fixed Assets

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Automatic Depreciation Rollback Description
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -Depreciation
tra
h n
Automatic Rollback Description
o 11i, users have been able to run depreciation for an asset book without closing
B Sincenrelease
the period. If additional adjustments are required in the current period, then the user submits a
process to roll back depreciation for the entire book, performs the necessary adjustment(s) and
then resubmits the depreciation program.
In Release 12, the intermediate manual step of rolling back depreciation for the entire book in
order to process further adjustments on selected assets is no longer necessary. As before, you
can submit depreciation for the entire book prior to closing the period. If it becomes necessary
to process financial adjustments on one or more assets, you may proceed with the transaction
normally via the asset workbench or mass transactions. Oracle Assets automatically rolls back
the depreciation on just the selected assets (instead of the whole book) and allows the
transactions to be processed normally. The assets for which depreciation was rolled back is
automatically picked up during the next depreciation run or at the time that the depreciation
period is finally closed.
Oracle Fixed Assets

Automatic Depreciation Rollback Benefits
s a
)ha
c om
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a n u -Depreciation
tra
h n
Automatic Rollback Benefits
B It is nnoolonger required to run depreciation rollback program manually.
Depreciation rollback is executed only on select assets as required and not on the entire Asset
Book, thereby enhancing performance of the program.
Oracle Fixed Assets

Agenda
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

Enhanced Functionality for Energy Industry Description
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu -Functionality
tra
h n
Enhanced for Energy Industry Description
o is now support for ‘Units of production’ method for group asset.
B • nThere
• Another depreciation method for energy industry is Energy Straight line Method.
- The Depreciation calculation formula is:
Net Book Value/Remaining Life
Oracle Fixed Assets

Summary
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Fixed Assets

s a
)ha
c om
m ini ide
pge Gu
c
Oracle Purchasing a ent
r la@ tud
k a is S
a
Chapter 7
h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Oracle Purchasing
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Objectives
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Agenda Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Agenda Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Agenda Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Professional Buyer’s Work Center Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -trBuyer’s
a
h n
Professional Work Center – Description
o
B The nProfessional Buyer’s Work Center speeds up daily purchasing tasks by providing buyers
with a central launch pad from where they can efficiently perform their daily tasks, such as:
• Viewing and acting upon requisition demand
• Creating and managing orders and agreements
• Managing contract deliverables
• Running negotiation events, including auctions and RFxs
• Managing supplier information
Note that the forms based interface for requisitions, orders, and agreements exist in release
12.0. Therefore, you have the option to either keep using the forms interface for their current
business interface, or migrate over to the web-based interface.
Oracle Purchasing
Professional Buyer’s Work Center Benefits
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -trBuyer’sa
h n
Professional Work Center – Benefits.
B Therenoare several advantages to using the buyer’s work center.
First, purchasing departments that operate as shared service centers can take advantage of
accessing documents across the multiple operating units that they service without having to
switch responsibilities.
In addition, the web-based interface of the work center is designed to enable buyers to perform
their tasks easily and quickly. One of the ways that this is achieved is by reducing the number
of drilldowns buyers need to access to create purchasing documents.
The work center helps buyers prioritize their tasks through the use of views. Oracle Purchasing
provides several pre-seeded views, such as the ability to view all documents that are
incomplete or all schedules that are past due. However, buyers can also create their own views
based on their particular responsibilities.
Oracle Purchasing
Professional Buyer’s Work Center Overview
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u -trBuyer’s
a
h n
Professional Work Center – Overview
o
B • nResponsibility: Purchasing
• Navigation: Buyer Work Center > Orders
The tab structure in the work center is:
• From the Requisitions tab, buyers can process requisition demand into purchase orders or
sourcing events. In addition, buyers can view existing requisitions that are in the system.
• Standard Purchase Orders are created and managed in the Orders tab, while Blanket and
Contract Purchase Agreements are created and managed in the Agreements tab.
• The Deliverables tab allows the buyer to manage deliverables from Procurement
Contracts.
• The Negotiations tab allows the buyer to quickly and easily access Oracle Sourcing.
• The Suppliers tab houses information about your supply base.
Oracle Purchasing
Professional Buyer’s Work Center Requisition Management
s a
)ha
c om
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
an u -trBuyer’s
a
h n
Professional Work Center – Requisition Management
no Buyer’s Work Center offers requisition management capabilities similar to those
B Professional
currently available via the AutoCreate and the requisition summary forms. Note that these
forms still exist in R12 and can be used. In 11i10+ the first release of requisition management
was released with Oracle Sourcing. The first release of requisition management did not support
all of the R12 features. Examples: Creating Purchase Orders, Splitting Requisition Lines, and
Integrating with the Catalog.
In R12 buyers can:
• Create a solicitation (auction/RFx) for bids (requires Oracle Sourcing), create a purchase
order, and add to an existing purchase order.
• Return requisitions to requesters to solicit additional information.
• Reassign requisition lines to other buyers including unassigned requisition lines.
• Split a requisition line in order to source from multiple suppliers.
• Replace requisition lines referencing a non-standard item with one or more items in the
catalog.
Oracle Purchasing
• Use the requisition summary page to view unapproved, approved, and historical
requisition lines.
• Access the catalog and favorites lists.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Professional Buyer’s Work Center Requisition Management –
Key Profile Options
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
an u -tra
non Buyer’s Work Center – Requisition Management Profile Options
BhProfessional
• Responsibility: Human Resources
The setup steps include defining values for 2 new profile options. The first step is:
PO: Document Builder Default Document Type – The document type that is defaulted into the
document builder region within the Demand Workbench.
Oracle Purchasing
Professional Buyer’s Work Center Requisition Management –
Key Profile Options
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
an u -tra
non Buyer’s Work Center – Requisition Management Profile Options
BhProfessional
PO: Default Requisition Grouping – The value ‘Requisition’ or ‘Default’ indicates if the
default requisition grouping for requisition lines onto a Negotiation Document or Purchase
Order.
• For the value Default: You can combine requisition lines for the same item, revision, line
type, unit of measure, supplier item number, and transaction reason onto one purchase
order line. You can add need–by date or ship–to organization and location to the default
grouping by using the profiles PO: Use Need–by Date for Default Autocreate grouping or
PO: Use Ship–to Organization and Location for Default Autocreate grouping.
Oracle Purchasing
• For the value Requisition: You can create a document with one line for each requisition
line. Used only when you select lines on a single requisition.
Note: If Oracle Sourcing is implemented; requisition lines with the same item, revision,
description, line type, UOM, and ship–to (based on deliver–to) are grouped into individual
negotiation document lines.
Note: If Oracle Services Procurement is implemented, only Requisition is supported for
fixed price with temp labor requisition.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
on
Bh The nProfessional
Implementation
Buyer’s Work Center tightly weaves Oracle Purchasing with other products
in the procurement family, such as Oracle Sourcing, Oracle Procurement Contracts, and Oracle
Services Procurement. Buyers can now easily navigate from purchasing to sourcing
documents, and vice-versa, using a single, friendly user interface. The work center also
provides seamless integration with Procurement Contracts to add clauses and deliverables to
purchasing documents, as well as manage these deliverables. Using Services Procurement,
buyers can accurately capture complex contracts and manage the procurement activities for the
services covered by these contracts.
Oracle Purchasing
Agenda Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Enhanced Catalog Access Description
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
Bas nsfer
anu -Catalog
tra Access – Description
h n
Enhanced
o
• Navigation: Buyer Work Center > Requisitions
Release 12.0 of Oracle Purchasing builds on the popularity of Oracle iProcurement’s search
capabilities by offering professional buyers a similar search interface to easily find the items
they need to procure.
From the Demand Workbench, buyers can access the catalog and favorites to find negotiated
alternatives to non-catalog requests.
While authoring orders and agreements, buyers can use the catalog or favorites to quickly add
items, thereby accelerating the document creation process.
Oracle Purchasing
Enhanced Catalog Access Benefits
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -Catalog
tra Access – Benefits
h n
Enhanced
o catalog access provides easy access to pre-negotiated items. This reduces
B The nenhanced
spending by leveraging negotiated pricing. Also, user productivity is increased due to the
Oracle Purchasing
Enhanced Catalog Access Setup Preferences
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu -Catalog
tra Access – Setup Preferences
h n
Enhanced
o the option to customize your catalog access by modifying your preferences. Using
B Younhave
the Shopping Purchasing Preferences you can define your view into the catalog including your
default store, search results per page, and your search results layout. Using the Favorites Lists
Preferences you can default your default favorites list.
Oracle Purchasing
Agenda Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Document Styles Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu -Styles
tra - Description
h n
Document
no Styles is a new feature in R12. It allows buying organizations to control the look
B Document
and feel of the application to match the needs of different purchasing documents. Through
reusable document styles, deploying organizations can enable or disable various Oracle
Purchasing features, thereby simplifying the user interface.
Oracle Purchasing
Document Styles Benefits
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -Styles tra - Benefits
h n
Document
B Therenoare several benefits of using document styles.
• Document styles provide the ability to appropriately name purchasing documents to align
more closely with the naming conventions of the deploying organization’s business. The
same purchasing document type (e.g. Standard Purchase Order) can assume different
names based on the style applied.
• Some features on the purchasing document, such as price breaks in global agreements or
services line types, can be enabled or disabled as part of the style setup.
• When a purchasing document is created using a style, disabled features are hidden to
simplify the user interface. For example, organizations can create a document style for a
specific commodity, such as temporary labor. This document style optimizes field labels
and display for that commodity, simplifying purchase order entry by hiding
regions/attributes that are only relevant for goods purchases.
Oracle Purchasing
Document Styles Process – Source Document Reference
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu -Styles
tra – Process Source Document Reference
h n
Document
o
• Navigation: Setup > Purchasing > Document Styles
Style of the source document should be taken into account when selecting a source document
for a requisition line, otherwise a mismatch can occur. For example, a requisition line for
services should not be sourced from contracts for Goods purchases.
Similarly, a purchase document should have the same style as its source document; for
example: a Standard Purchase Order created as an execution document of a Global Blanket
Agreement should have the same style as the agreement.
Oracle Purchasing
Agenda Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Procurement for Complex Services Description
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu -trafor Complex Services - Description
nonServices Procurement is an integrated solution for Oracle Services Procurement used
Bh Complex
Procurement
to model complex work contracts that involve advanced payment terms. These contracts tend
to have high dollar values, often running into several millions of dollars. They also tend to be
long lead time contracts, sometimes extending over multiple years. These contracts are
characterized by progress payments that are governed by the complex payment terms, and
which are released based on completion of work. Additionally, complex work contracts can
also have provisions for Contract Financing.
Oracle Purchasing
Procurement for Complex Services High Level Business Flow
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a n u -trafor Complex Services – High Level Business Flow
Bh Thisnisothen high level business flow that the Complex Services Procurement solution
Procurement
encompasses. The business flow can originate with a services request which the buying
organization determines needs complex payment terms to manage and fulfill. The sourcing
process allows negotiation of the complex payment terms and these are carried forward to the
Contract after the award.
The Contract, once approved and signed off by the involved parties is now in a state ready for
execution. The Supplier can report progress on the work specified on the Contract, which the
buying organization can certify as complete. Subsequently, payments can be processed for the
progress made on the contract. The payment terms specified on the contract are used to
compute the payment due to the supplier.
Oracle Purchasing
Procurement for Complex Services New Purchasing Features
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
a n u -trafor Complex Services – New Purchasing Features
non complex services, several features have been added to the Purchasing application.
Bh To support
Procurement
• You can define a Document Style for procurement of complex services. Using the
Document Style, the available functionality on the contract can be configured to best suit
the business need, such as making provisions for advances, contract financing, or
retainage.
Responsibility: Purchasing
Navigation: Setup : Purchasing > Document Styles
• You can create a contract with or without a requisition, define a progress payment
schedule for the work to be completed, define complex payment terms such as retainage,
and make provisions for advances and contract financing.
Navigation: Buyer Work Center > Agreements > Create (Choose agreement type) >
(B) Go
Oracle Purchasing
• Monitoring and tracking progress on the contract is essential to minimize delays.
Purchasing and iSupplier Portal provide both the Buyer and the Supplier complete
visibility to the current status and progress on the Contract. Suppliers can submit Work
Confirmations to report progress made on the contract. These can be approved by
representatives from the Buying Organization before payments can be released.
Navigation: Buyer Work Center > Agreements > View (Choose agreement status) >
(B) Go
• The ability to manage change with ease is critical for complex services contracts since
these contracts extend over a long period of time and changes to project schedules and
budgets can happen in that duration. Change requests can be created by both Suppliers and
Buyers as necessary and these are included in the contract upon approval.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Procurement for Complex Services Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
a n u -trafor Complex Services - Benefits
on Complex Services Procurement feature gives you a competitive edge by
Bh The nend-to-end
Procurement
bringing the Services Procurement Spend category under the purview of automated, online
processes. Leveraging this integrated online flow reduces errors and delays associated with
paper-based processes.
It provides the capability to ensure compliance to the contract and the project budgets by
giving the Contracting Organization 360 degree visibility to all aspects of the Contract
Lifecycle. Project Managers can see the impact of these contracts on the project via
commitment and actuals reporting.
Project Managers, Buyers, Contractors, Architects, Field Engineers can collaborate seamlessly
to ensure smooth execution through the contract lifecycle – from negotiation to completion.
The ability to manage, control, and track these contracts keeps lead times and costs in check,
and prevents project cost overruns. This is crucial in such high dollar value contracts.
There are significant acquisition risks associated with such high dollar value contracts. By
using negotiated payment terms such as retainage, the buying organization can mitigate these
risks.
Oracle Purchasing
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
Bh Oracle n
Implementation
noPurchasing and Oracle Services Procurement are required for the majority of the
functionality to work. Oracle Purchasing provides the functions that allow you to author, track
execution of the complex services contract, and create and submit work confirmations. Note
that only buyers can create and submit work confirmations using Oracle Purchasing.
Oracle Services Procurement is required for the use of the fixed price services and temp labor
line types, as well as their associated functionality.
Oracle Purchasing
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
a n u -tra Considerations (continued)
on products are optional:
Bh The nfollowing
Implementation
• Oracle Payables
- Create and submit invoices for progress payments, Advances and financing, retainage
release
• Oracle Sourcing
- Negotiate with suppliers on payment terms and payment schedule
• Oracle Procurement Contracts
- Use clauses and deliverables on contract
• Oracle iProcurement
- Create Service Requests
- Create Work Confirmations (Project Manager)
• Oracle iSupplier Portal
- Track Execution of Contract
- Create Work Confirmations (Contractor)
Oracle Purchasing
• Oracle E-Tax
- Tax Engine with rules for tax calculation on Payment Schedule, Advances, and
Contract Financing
• Oracle Enterprise Asset Management
- Carry Work Order Reference on Requisition
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Agenda Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Access
- tra Control - Description
h n
Multi-Org
no Access Control, or MOAC, enables you to access multiple operating units from a
B Multi-Org
single application responsibility.
MOAC allows companies that want to implement a shared services model to efficiently
process business transactions because users are allowed to enter, process, view, and report on
data for an unlimited number of operating units from a single responsibility.
Operating unit security is preserved such that companies can effectively implement security
and shared services at the same time.
Oracle Purchasing
Multi-Org Access Control Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a i s S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Access
- tra Control - Benefits
h n
Multi-Org
B MOACnostreamlines Shared Service Center Operations. This feature enables the user to access,
process and report on data for multiple operating units from within a single application
responsibility. This would have required switching responsibilities in prior releases.
Oracle Purchasing
MOAC Effects – Forms and Pages
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la @ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Effects- tra– Forms and Pages
h n
MOAC
o of having MOAC implemented is that there is a new Operating Unit field on many
B The neffect
pages and forms. Buyers can use this field to select an operating unit from the list that is
approved for their responsibility. For example:
• Responsibility: Purchasing
• Navigation: Buyer Work Center > Orders > Create (Select type of Purchase Order)
> (B) Go > (T) Header > Operating Unit
Oracle Purchasing
Multi-Org Access Control Public APIs
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u Access
- tra Controls – Public APIs
h n
Multi-Org
noAPIs take Operating Unit as a parameter. Operating Unit is an optional parameter. If it
B Public
is not provided, the default operating unit from setup is used to set the desired context.
Oracle Purchasing
Agenda Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
E-Business Tax Description
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -tTaxra –Description
h n
E-Business
o E-Business Tax is a new infrastructure for tax knowledge management and
B • nOracle
delivery using a global system architecture that is configurable and scalable for adding
country specific tax content.
• As the single point solution for managing transaction-based tax, Oracle E-Business Tax
delivers tax services uniformly to Oracle E-Business Suite business flows through one
application interface.
• Oracle E-Business Tax provides a comprehensive solution to configure, maintain, manage,
and access transaction-based taxes. Organizations will have the ability to effectively
address multiple tax needs, from global tax requirements to local compliance.
Oracle Purchasing
E-Business Tax Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u -tTaxra - Benefits
h n
E-Business
noE-Business Tax significantly enhances the tax solution within the Procure to Pay
B Oracle
business flow. Previously, only basic tax code and tax group based tax computation capabilities
were supported. By integrating with Oracle E-Business Tax, the Procure to Pay business flow
will be able to address complex tax requirements. Another benefit of the integration is the
ability to utilize a single point tax solution across the E-Business Suite, which greatly
simplifies maintenance and tax management.
Oracle Purchasing
E-Business Tax Process – Tax Calculation
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -ttax ra – Process
h n
E-Business
B Tax nisocalculated for the following purchase documents:
• Purchase and Internal Requisitions, at the requisition line level
• Standard and Planned Purchase Orders, at the PO shipment level
• Blanket and Scheduled Releases, at the Release shipment level
Tax is calculated whenever a purchase transaction is created and tax is recalculated when any
tax determination attributes on the transaction is updated. So any saved purchase document
should have its applicable tax already calculated.
Oracle Purchasing
E-Business Tax Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u -tTaxra – Setup
h n
E-Business
o
• Navigation: Tax Managers > Home
Because all existing tax setups prior to R12 are migrated to E-Business Tax, you can continue
using any existing tax setup after the upgrade without performing any further setup. However,
with this setup, only tax codes or tax groups based tax computation capabilities are supported.
If you have an existing tax setup and want to utilize the full E-Business Tax functionalities,
additional setup is necessary.
Oracle Purchasing
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Agenda Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Document Publishing Enhancements Description
s a
)ha
c o m
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -Publishing
tra
h n
Document Enhancements - Description
no 11i, Oracle Advanced Procurement Suite supported XSL-FO stylesheet based layout
B In release
templates. In release 12, you can use layout templates created in Microsoft RTF and Adobe
PDF formats.
Oracle Purchasing
Document Publishing Enhancements Description
s a
)ha
c o m
m ini ide
p ge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -Publishing
tra
h n
Document Enhancements - Description (continued)
no 11.5.10, purchasing administrators had to specify the layout template for each
B In release
document type using the document types setup form. With Release 12, buyers can print
purchasing documents on demand using any of the pre-defined layout templates.
Oracle Purchasing
Document Publishing Enhancements Benefits
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu -Publishing
tra
h n
Document Enhancements - Benefits
no printing enhancements enable organizations to make use of RTF and PDF templates
B Document
that you can design and configure. It also allows buyers to print a purchasing document in
multiple formats.
Many Government organizations are required to print Government Forms during various
phases of the procurement process. These Forms are mostly in Adobe PDF format and
published on Government websites. For example, US Federal Agencies need to print standard
forms like SF30 and SF33. Release 12 provides an infrastructure based on which such Forms
can be printed out of the application.
Oracle Purchasing
Document Publishing Enhancements Setup and Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -Publishing
tra
h n
Document Enhancements – Setup and Process
B Setupno
1. Create a layout for the purchasing document in either PDF or RTF format.
2. Upload the layout to Oracle XML Publisher.
Responsibility: XML Publisher Administrator
Navigation: Home > Templates > (T) Templates > (B) Create Template > Template
file (B) Browse to upload template
Process
1. Create a purchasing document. If Oracle Procurement Contracts is enabled, optionally
add contract terms and conditions.
2. Navigate to the request submission form and search for “PO Output for Communication.”
3. Specify the purchase order number and Purchase Order Layout. If Oracle Procurement
Contracts is enabled, specify the Contract Terms Layout.
4. Submit the request.
5. The output of the request will be an Adobe PDF formatted document in the layout
specified at run time.
Oracle Purchasing
Document Publishing Enhancements Setup – PDF Template
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu -Publishing
tra
h n
Document Enhancements – Setup PDF template
o the PDF template in Adobe Professional.
B • nOpen
• Enable the option so that you can view the tags associated with each field.
• Replace the field tags with the corresponding system code. The system codes for the
purchase order XML is published in the ‘Document Printing and Communication’ white
paper, available from Oracle Metalink.
All of these steps must be performed offline. You can also use Adobe Professional to create
your own, custom layout using PDF format.
Oracle Purchasing
Document Publishing Enhancements Setup – RTF Template
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u -Publishing
tra
h n
Document Enhancements – Setup RTF Template
noXML Desktop enables purchasing administrators to design purchase order layouts in
B Oracle
RTF format.
Oracle Purchasing
Document Publishing Enhancements Setup – Upload Template
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu -Publishing
tra
h n
Document Enhancements Setup – Upload Template
o
B • nResponsibility: XML Publisher Administrator
• Navigation: Home > Templates > (T) Templates > (B) Create Template > Template
file (B) Browse to upload template
Oracle Purchasing
Document Publishing Enhancements Process – Printing in
Procurement Flow
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu -tra
non Publishing Enhancements - Process
BhDocument
This figure depicts the capabilities of document printing through various phases of the
procurement cycle. While reviewing the draft document, the buyer can generate the purchasing
document in Adobe PDF format. When the purchase order is submitted for approval, the
application generates the purchase order PDF and attaches it to the approval notification.
From iSupplier Portal, suppliers can view the purchase order in Adobe PDF format during
signature and when the purchase order is ready for execution.
Oracle Purchasing
Document Publishing Enhancements Process – Print Purchasing
Document
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu -tra
non Publishing Enhancements – Process
BhDocument
• Responsibility: Purchasing
• Navigation: Purchasing > Requests
Navigate to the Requests form to launch the ‘PO Output for Communication’ concurrent
program. This program allows buyers to generate purchasing documents in Adobe PDF format
using pre-defined layout templates.
The concurrent program has been enhanced to include two additional parameters: Purchase
Order Layout and Contract Terms Layout. To generate a purchase order PDF using a certain
layout, provide the layout names as runtime parameters. The program prints the purchase order
in Adobe PDF format using the specified layout.
If the purchase order PDF was generated using a fillable PDF template, the buyer can use
Adobe Reader to enter values for the fields that were not populated by the program. However,
if the buyer wants to save the changes on the purchase order PDF, they must use Acrobat
Professional to do so.
Oracle Purchasing
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a nu -tra Considerations
onhave Oracle XML Publisher installed to use this feature. The infrastructure provided
Bh Younmust
Implementation
by Oracle XML Publisher is utilized to store layout templates. If you have enabled Oracle
Procurement Contracts, you can print contract terms and conditions as well.
Oracle Purchasing
Agenda Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Document Attachments Description
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -Attachments
tra
h n
Document - Description
o to attach notes and files to purchase orders has been available for many years.
B The nability
However, once these attachments were added, buyers and suppliers had limited access to view
them. The printed purchase order report and the purchase order notification only showed notes
and text attachments. In order to view the other types of attachments, buyers and suppliers had
to be logged into the application.
In this release, the PDF that is generated for each purchasing document lists all of the related
attachments – not just the notes and text attachments.
In addition, buyers can email these attachments to suppliers. The attachments are sent as a .zip
file along with the PDF. Built-in error handling assists buyers and suppliers if there are
problems communicating the attachments.
Oracle Purchasing
Document Attachments Description
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -Attachments
tra
h n
Document – Description (continued)
B Priorntoorelease 12, only a small subset of the available attachment types were communicated to
the supplier.
In release 12, there are no limitations to the types of attachments that can be sent to the
supplier.
Oracle Purchasing
Document Attachments Benefits
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Document Attachments Process
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
anu -Attachments
tra
h n
Document - Process
o the purchasing document, such as a standard purchase order or blanket purchase
B 1. nCreate
agreement.
2. Attach all necessary files and notes at the header, line, or delivery schedule/price break
level.
3. Approve the purchasing document.
4. Assuming no errors are encountered, the attachments will be sent to the supplier along
with the PDF of the purchasing document.
5. If the compressed attachments exceed the maximum allowable size specified as part of
setup, or if any other error is encountered, the attachments are not sent. Both the buyer
and the supplier are notified if either of these situations occurs.
Oracle Purchasing
Document Attachments Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu -Attachments
tra
h n
Document Setup
o
• Navigation: Setup > Organizations > Purchasing Options
• Specify that PDF is the preferred method for displaying the purchase order.
• Define the maximum allowable size for the compressed files.
• Optionally provide the filename for the compressed attachments.
Oracle Purchasing
Document Attachments Setup – Define Purchasing Options
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu -Attachments
tra
h n
Document Setup – Define Purchasing Options
o
• Navigation: Setup : Organizations > Purchasing Options
Oracle Purchasing
Agenda Part 1
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Oracle Supplier Network Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Supplier
- tra Network - Description
h n
Oracle
o expedites supplier enablement activities for buying organizations, providing a
B The nnetwork
community of pre-integrated suppliers for electronic transaction delivery. The Oracle-hosted
service offers centralized messaging management and monitoring, as well as message
transformation for six procure-to-pay transaction types. Trading partners have access to two
messaging hubs allowing them to exchange end-to-end test transactions separate from actual
live transactions.
Oracle Purchasing
Transacting Over Oracle Supplier Network
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
a nu -trOver
a Oracle Supplier Network
h n
Transacting
o Organizations exchange OAG XML messages with the Oracle SN
B • nBuying
• Transformation maps allow suppliers the option to support cXML or OAG format
• Supported transmission protocols for message delivery: HTTP/S, OXTA, SMTP
Purchasing customers utilize the E-Business Suite’s standard messaging tools to connect and
transact over the OSN. OSN provides guides on how to setup the Oracle XML Gateway to
send and receive transactions in the required OAG XML format, which is the native XML
format used by Oracle Purchasing and AP. Suppliers have a choice; they can support the
cXML or OAG format standard, depending on preference of their internal systems. The OSN
automatically converts transactions between cXML and OAG XML formats and delivers them
using any of the supported delivery methods selected by the trading partner. Providing a choice
of formats and protocols reduces trading partners’ messaging support cost. For example, the
supplier doesn’t need to invest in supporting the OXTA protocol, which is Oracle’s proprietary
transmission protocol, in order to exchange electronic transactions with Oracle customers.
Oracle Purchasing
Oracle Supplier Network Support Transactions with Purchasing
s a
)ha
c o m
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Supplier
- tra Network Support Transactions with Purchasing
h n
Oracle
o shows points at which Purchasing can use OSN to communicate with Suppliers.
B Thisnexample
Oracle Purchasing
Oracle Supplier Network Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Supplier
- tra Network - Benefits
h n
Oracle
o companies to enable faster electronic transaction delivery with suppliers than is
B OSNnallows
the case when forced to negotiate with each supplier individually to establish direct messaging
relationships. When buyers and suppliers manage their own, single connection to the network,
a significant amount of redundant work is removed as each additional supplier enabled. OSN’s
centralized message monitoring and error notifications reduce the IT.
As more suppliers convert from paper and fax transactions, suppliers are able to realize error-
free order processing to drive down PO fulfillment cycle times and provide process savings for
both parties.
Many of the higher volume commodity suppliers offer price discounts for electronic PO
transaction delivery, particularly when they’re already transacting over the OSN and can
leverage the same messaging channel. Advanced organizations leverage this best practice in
renegotiating contracts.
Oracle Purchasing
Oracle Supplier Network New Features
s a
)ha
c om
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Supplier
- tra Network New Features
h n
Oracle
o
B R12nconnectivity includes testing certification of all transaction types with the OSN as well as
documentation updates covering the required setups to connect R12.
Multi-user accounts allow functional and technical users to access their company’s OSN
account. With role security you have the option to restrict IT resources to messaging
configuration and functional users to only view transactional information.
With iSupplier Portal Punch-in integration suppliers can now access customers’ iSupplier
Portal instances through their OSN account. To enable, buying organizations associate their
iSP instance with their OSN account. Suppliers can then request accounts and ,once approved,
they’re able to leverage the OSN for easy one-click access to multiple customers.
Companies can now utilize diagnostic tools to send and receive test documents with the OSN.
These self-testing tools allow trading partners to correct errors for enabling support of new
document types before having to test with a live trading partner.
Oracle Purchasing
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Agenda Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Maintain Sourcing Rules/ASLs for Agreement Items
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u Sourcing
- tra Rules/ASLs for Agreement Items
h n
Maintain
B Priorntoothis release, system-generated sourcing rules and ASLs were only created at the time
of blanket agreement approval. These rules were enabled for all organizations, which might not
have mirrored actual business processes.
In this release, you create sourcing rules and ASL entries for a specific inventory organization.
You can create these rules for agreements that you manually create, or for agreements that you
import through the open interface.
In addition, the dependency of rules creation with the approval process has been removed. As a
result, you can create rules for existing agreements that have already been approved.
This concurrent program allows you to automatically create rules for all of the operating units
in which a blanket agreement is enabled.
Oracle Purchasing
Maintain Sourcing Rules/ASLs for Agreement Items Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u Sourcing
- tra Rules/ASLs for Agreement
h n
Maintain
o allows you to specify exactly how you expect supplier and document sourcing to
B Thisnfeature
occur.
The bigger benefit, however, is that you no longer need to manually setup sourcing rules and
ASLs every time you create or update your blanket agreements.
For blanket agreements that are enabled in multiple operating units, you can automatically
create rules for all of the enabled operating units to streamline your order creation process.
Oracle Purchasing
Maintain Sourcing Rules/ASLs for Agreement Items - Define
Rules for a Specific Plant
s a
)ha
c o m
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
an u -tra
nonSourcing Rules/ASLs for Agreement Items - Define Rules for a Specific
BhMaintain
Plant
Example: Defining rules for a specific region, plant, or business unit.
Assume Company A has operations on both the west coast and the east coast, and some of the
items used at these facilities are sourced regionally. Specifically, when ordering for the San
Diego plant, Advanced Network Devices delivers the goods. However, when ordering for the
Boston plant, Prouty Industrial Supply provides the materials. This scenario can be modeled in
the Oracle Purchasing by performing the following steps:
1. Create and approve a blanket agreement for each of plants.
2. Define Rules for a Specific Plant
Navigation: Purchasing > Requests
Launch the concurrent request for each of the blanket agreements. The name of the concurrent
request is ‘Generate Sourcing Rules and ASLs from Blanket Agreements’ and can be launched
from the Requests link in the main menu. When the concurrent program is launched for
Advanced Network Devices (the west coast supplier), the sourcing level is set to Item-
Organization and the inventory organization is set to San Diego Manufacturing. If the sourcing
Oracle Purchasing
level were set to ‘Item’, global rules would have been created. When the concurrent program is
run for Prouty Industrial Supply (the east coast supplier), the sourcing level is again set to
Item-Organization, but the inventory organization is set to Boston Manufacturing.
• The sourcing rules for both plants should be assigned to the same Assignment Set,
Supplier Scheduling.
• Once the programs finish running, local sourcing rules are created for both plants.
• Local ASL entries are also created for each plant and assigned to the corresponding
blanket purchase agreement.
3. Update Rules After Renewing Blanket Agreements
Navigation: Purchasing > Requests
This concurrent request can also be used to update sourcing rules and ASL entries after
extending the effective dates on a blanket agreement. Once the changes have been made to the
blanket agreement, run this program with the parameter ‘Select Blanket Lines’ set to ‘All’.
s a
)ha
This ensures that rules are updated for all of the lines on the blanket agreement. If you only
om
want to create or update rules for the lines that have changed since the last time the agreement
c
ini ide
was archived, set the parameter ‘Select Blanket Lines’ to ‘New’.
m
e Gu
4. Create Rules for All OUs Buying off an Agreement
g
c p
a ent
This concurrent request can be used to automatically create sourcing rules and ASL entries for
la@ tud
all of the operating units that a blanket agreement covers. For example, consider a blanket
r
k a is S
agreement that is enabled in several operating units.
a h
ash use t
• Prior to this release, it was possible to automatically create rules for the owning operating
u b
to
unit upon approving the agreement. However, rules were not automatically created for the
an e
bh ens
enabled operating units. These rules had to be manually created.
a (
l e lic
r
• In release 12.0, the concurrent program allows you to create rules for each of the enabled
a a
k abl
operating units. This is accomplished by selecting the purchasing operating unit of the
h
as nsfer
requesting operating unit for which you want to create the rules.
B
u -tra
an
Bh non
Oracle Purchasing
Agenda Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Support for Contractor Purchasing Users Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an u for-tContract
ra
h n
Support Purchasing Users
norelease, contingent workers can perform the same actions as requesters and buyers who
B In this
are employees.
These actions include creating requisitions, purchase orders, and receipts. In addition,
contingent workers can approve both requisitions and purchase orders.
Oracle Purchasing
Support for Contractor Purchasing Users Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a i s S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u for-tContract
ra
h n
Support Purchasing Users - Benefits
no these capabilities to contingent workers provides the following benefits:
B Extending
• Companies can outsource their procurement functions to third parties, allowing them to
focus on their core competencies.
• For the many companies that utilize the services of contingent workers, these workers can
raise requisitions on their own behalf.
• Companies can meet compliance requirements because they no longer have to define
contingent workers as employees for contingent workers to perform their jobs.
Oracle Purchasing
Support for Contractor Purchasing Users Setup
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu for-tContractor
ra
h n
Support Purchasing User – Set Up
o
1. Set the profile option, HR: Expand Role of Contingent Worker
2. Define the contingent worker in HR
3. Provide a user login for the contingent worker
4. Assign the appropriate responsibilities to the contingent worker
5. Assign the buyer role to the contingent worker
6. Once these steps are completed, the contingent worker can follow the same purchasing
processes as employees.
Oracle Purchasing
Support for Contractor Purchasing Users Setup – Set Profile
Option
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu -tra
non
BhSupport for Contractor Purchasing User – Setup
The profile option, HR: Expand Role of Contingent Worker, allows companies to control the
tasks contingent workers can perform in the application.
System administrators can set this profile option by navigating to Profiles : System
Oracle Purchasing
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
nonfor contingent workers has been extended to other products within the procurement
Bh Support
Implementation
family, such as Oracle iProcurement and Oracle Sourcing.

• In Oracle iProcurement, contingent workers can create and manage requisitions, including
change requests. Contingent workers with managerial responsibilities can approve
requisitions and change requests.
• In Oracle Sourcing, contingent workers can conduct and manage negotiations.
• In addition, the performance of contingent workers as buyers in the purchasing department
is reported in Daily Business Intelligence along with the performance of buyers who are
employees.
Oracle Purchasing
Agenda Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Compliance to Packaging Constraints Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu -trtoaPackaging Constraints - Description
onconsidering a supplier’s shipping and packaging constraints can result in orders being
Bh • nNot
Compliance
placed for fractional quantities or erroneous packaging units.

• This can result in shipping delays or sometimes even rejection of orders, which adds to
cost of procurement in additional order processing costs.
• Inventory Planning systems seldom consider supplier lot size or minimum order quantity
requirements resulting in over/under-shipment, or even rejection of the order.
In this example, a Min-Max replenishment request from Inventory is created for 116 eaches of
an item. There is no visibility to the Minimum Order Quantity (MOQ) or Unit of Measure
(UOM) required by the supplier during requisition import. Therefore a purchase order is
created for 116 eaches and communicated to the supplier. Since this does not meet the
supplier’s packaging constraints, it is rejected.
Oracle Purchasing
Compliance to Packaging Constraints Description
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
a n u -trtoaPackaging Constraints - Description
Bh Oracle n
Compliance
noPurchasing can now automatically apply supplier-specific order modifiers
(fixed lot multiple and minimum order quantity) and UOM to replenishment requests that
originate in Inventory planning processes. Supplier packaging constraints are setup, stored and
then used to modify replenishment requests originating from Inventory planning processes.
Taking the example from the previous slide, the request from Inventory for 116 eaches is
modified during Requisition Import as follows:
• The quantity is below the minimum order quantity which is 10 Cases of 12 or 120.
Therefore the quantity is increased to 120.
• Supplier UOM is cases of 12. Therefore the quantity and UOM are changed to 10 Cases of
12.
• A purchase order for 10 Cases of 12 is created, which is now fully compliant with supplier
packaging constraints.
Oracle Purchasing
Compliance to Packaging Constraints Benefits
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
anu -trtoaPackaging Constraints - Benefits
on compliance to supplier shipping and packaging constraints
Bh • nIncreases
Compliance
• Reduces and eliminates:

- Order processing and inventory Costs
- Shipment delays
- Decimal order quantities on order lines
Oracle Purchasing
Compliance to Packaging Constraints Process Summary
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
B as nsfer
a n u -trtoaPackaging Constraints Process Summary
on at a high level during requisition import consists of:
Bh The nprocess
Compliance
• Application of order modifiers

• UOM Conversion
• Quantity Rounding
Oracle Purchasing
Compliance to Packaging Constraints Process – Apply Order
Modifiers
s a
)ha
c o m
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
anu -tra
non to Packaging Constraints – Process: Apply Order Modifiers
BhCompliance
If the requisition quantity is less than the minimum order quantity, then it is increased so it
becomes equal to the minimum order quantity. If it is equal to or greater than the minimum
order quantity, then it is left unchanged.
• Supplier-sourced Requisitions: Use Order Modifiers set-up on the ASL
• Internally-sourced Requisitions: Use Order Modifiers set-up in Org-Item setup for the
Source Organization
Oracle Purchasing
Compliance to Packaging Constraints Process – Perform UOM
Conversion
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
anu -tra
non to Packaging Constraints – Process: Performing UOM Conversion
BhCompliance
• If the item is sourced internally, the UOM used for conversion is the unit of issue in the
source organization.
• If the item is sourced from a supplier and the requisition has a source document reference,
then the UOM on the source document is used for conversion.
• If the item is sourced from a supplier and the requisition has no source document
reference, then the Purchasing UOM in the ASL is used for conversion.
• UOM conversion is performed if the unit of issue or purchasing UOM is different from the
UOM on the requisition.
Oracle Purchasing
Compliance to Packaging Constraints Process – Perform Quantity
Rounding
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
anu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
anu -tra
non to Packaging Constraints – Process: Performing Quantity Rounding
BhCompliance
• If the decimal value is less than the rounding factor, the quantity is rounded down
• If the decimal value is greater than or equal to the rounding factor, the quantity is rounded
up.
In this example, the decimal value of 0.65 is compared to the rounding factor – when it is set to
0.4, the requisition quantity is rounded down and when it is set to 0.7, the requisition quantity
is rounded up.
Oracle Purchasing
Compliance to Packaging Constraints Setup and Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
a n u -trtoaPackaging Constraints – Setup and Process
onfor internally sourced items consists of:
Bh The nsetup
Compliance
• Setting up of order modifiers for the item in the source organization.

• Setting up the enforce full lot quantity purchasing option.
Navigation: Setup : Organizations > Purchasing Options > Document Control >
Enforce Full Lot Quantity
• Setting up the unit of issue in the source organization.
Navigation: Setup : Items > Attribute Controls > Unit of Issue
• Setting up the rounding factor.
Navigation: Setup : Items > Attribute Controls > Rounding Factor
The setup for supplier sourced items consists of
• Setting up of order modifiers for the item in the ASL
• Setting up the supplier UOM in the source document or ASL
Oracle Purchasing
• Setting up the rounding factor
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
onsetup of Order Modifiers and Unit of Issue for Internally Sourced Items is done in
Bh • nThe
Implementation
Oracle Inventory
• The setup of Rounding Factor for items is done in Oracle Inventory
• Order Modifiers are applied only to requisitions imported from Oracle Inventory. These
can come from Min/Max, Par Replenishment and other inventory planning processes.
Oracle Purchasing
Agenda Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Auto-Approval Tolerances for Change Orders Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
a n u -traTolerances for Change Orders
onUI also exposes many new attributes compared to the tolerance control attributes
Bh The nnew
Auto-Approval
available within the approval workflow definition. You can now implement more granular
tolerance control by leveraging these new attributes. Tolerance values setup for attributes in
this page take precedence over those corresponding attributes within the workflow definition.
Use of this feature is optional. If you do not set up values, the application still honors tolerance
configuration as defined in the workflow.
Oracle Purchasing
Auto-Approval Tolerances for Change Orders Setup and Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u -traTolerances for Change Orders – Setup and Process
on
Auto-Approval
Purchasing
• Navigation: Setup : Tolerances and Routing > Change Order
Auto-Approval Tolerances are defined on Setup screen or in Workflow Attributes.
Once a Purchasing Document is submitted for approval, in the Approval Workflow a check is
done to ensure that all changes are within tolerance. If they are then main approval is bypassed
otherwise the document is routed through main approval process in workflow.
Oracle Purchasing
Agenda Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
EAM Support for Services Procurement Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
an uSupport
- trafor Services Procurement - Description
h n
EAM
o module is used to identify, schedule and track all work activities/costs related to
B The neAM
assets throughout an organization.
Organizations often hire contract service providers to perform some of their maintenance work
because the maintenance dept may not have the necessary skills or manpower. Such contract
services include: Painting a building, copier repair services or database upgrade.
In Release 12, the integration between Oracle Services Procurement and eAM supports the
integration of fixed price services requisitions/purchase orders with work orders created in
eAM, to provide better tracking of all related activities.
Oracle Purchasing
EAM Support for Services Procurement Setup and Process
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uSupport- trafor Services Procurement
h n
EAM
o setup step for this feature is to Create Work Orders in the eAM application for the
B The nonly
work required. There are 2 ways the integration works between eAM and Oracle Advanced
Procurement. The first process flow originates in either Oracle iProcurement or Oracle
Purchasing:
• It starts with the creation of a Requisition in iProcurement or Oracle Purchasing for Fixed
Price Services
Navigation: Requisitions > Requisitions > (T) Lines > In the Type field, choose Fixed
Price Services
• The Work order reference can be entered on the requisition and the Requisition can be
submitted for approval.
• Subsequently, the Requisition is approved with the Work Order information.
Alternately, you can directly create a Purchase Order without a backing requisition in Oracle
Purchasing and enter a work order reference.
The second process flow originates in the eAM application:
Oracle Purchasing
• From eAM, you can launch Oracle iProcurement from the work order form
Responsibility: Enterprise Asset Management
Navigation: Work Orders > Work Orders
• You can then create a requisition with a Fixed Price Services line
• The Work order information is populated automatically on the requisition based on the
work order form
• Now the Requisition can be submitted for approval.
• Subsequently, the requisition is approved with the work order information and processed
into a PO and released to the contractor for execution.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
Additional Considerations
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
an u -Considerations
tra
h n
Additional
o for Services Procurement entering work order for requisition (with fixed price
B EAMnsupport
service line) considerations.
Oracle Purchasing
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
Bh Oracle n
Implementation
noEnterprise Asset Management module is required for the integration.
Oracle Services Procurement is required to support this business process flow.
Oracle Purchasing
prohibited
7 - PageCopyright©
Agenda Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
prohibited
7 - PageCopyright©
Model Complex Pricing for Blanket Line Items Description
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an u Complex- tra Pricing for Blanket Line Items - Description
h n
Model
B Priorntoorelease 12, pricing for items in blanket agreements could either be specified in the form
of a price on the line or in the form of one or more price break records. The price break records
could either represent a volume discount region/location specific pricing for different
effectivity periods (old, current, future), or any combination thereof. For example: pricing for
California starting in the third quarter 2006.
While these pricing capabilities are sufficient for a large section of the business scenarios, there
are a few others where pricing requirements are a little more involved.
To handle these scenarios, Oracle Purchasing also offers a Custom Pricing Hook that you can
leverage to incorporate their own business specific pricing rules. These rules when available
would override any price calculated based on pricing data in the Agreement.
With Release 12, Oracle Purchasing provides an additional option to model complex pricing
for Blanket line items. In this release Oracle Purchasing has built an integration with the Oracle
Advanced Pricing product. Oracle Advanced Pricing provides a set of tools in the form of price
lists, formulas and modifiers to model complex pricing scenarios.
This integration may eliminate the need for existing Oracle Purchasing customers to
incorporate custom code into the product in the form of the custom pricing hook.
Oracle Purchasing
prohibited
7 - PageCopyright©
Formulas let you define rules to dynamically determine price on a transaction based on
attribute values on the transaction, and modifiers let you keep track of a wide range of
discounts and surcharges that would help price the transactions accurately without needing any
manual override on the transaction.
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
prohibited
7 - PageCopyright©
Model Complex Pricing for Blanket Line Items Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu Complex
- tra Pricing for Blanket Line Items - Benefits
h n
Model
o now negotiate the best possible agreement without worrying about your system’s
B Youncan
capability to handle complex pricing structures.
The integration with advanced pricing allows dynamic calculation of prices providing
significant additional flexibility to complement the existing blanket agreement functionality.
Companies can now accurately price all requests and purchases, thus reducing their
dependence on the supplier’s billing capabilities.
It also allows them to take advantage of all available discounts and/or promotions.
Oracle Purchasing
prohibited
7 - PageCopyright©
Model Complex Pricing for Blanket Line Items Setup and Process
s a
)ha
c om
m ini ide
p ge Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u Complex
- tra Pricing for Blanket Line Items – Setup and Process
h n
Model
nothis feature, you must have Oracle Advanced Pricing setup.
B To use
• Responsibility: Oracle Pricing Manager
• Navigation: Setup > Profile
To model complex pricing for Agreement lines:
• Create an agreement using existing process
• Create price lists, modifiers or formulas as necessary for the scenario in the Oracle
Advanced Pricing product.
Responsibility: Oracle Pricing Manager
Navigation: Price Lists > Price List Setup
The pricing attributes or qualifiers on these price lists or modifier lines let you link them back
to the Agreement or a specific agreement line item.
Oracle Purchasing
prohibited
7 - PageCopyright©
Model Complex Pricing for Blanket Line Items Pricing Hierarchy
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
anu Complex
- tra Pricing for Blanket Line Items – Pricing Hierarchy
h n
Model
B • nIfothe transaction references an item from the item master, the list price of the item in the
item master is first defaulted into the transaction.
• If the transaction references an approved and active blanket agreement, the pricing engine
then determines the price from the applicable agreement price breaks if there’s any.
• If there isn’t any price break defined, it picks up the price from the agreement line.
• If there’s pricing information available in Oracle Advanced Pricing in the form of price
list lines and/or modifiers, these pricing rules are then applied to arrive at the net price.
• It is important to note that if you have defined custom pricing rules in the custom hook
provided, those rules override any other pricing that the system may have derived.
Oracle Purchasing
prohibited
7 - PageCopyright©
Model Complex Pricing for Blanket Line Items Profile Options
s a
)ha
c om
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu Complex
- tra Pricing for Blanket Line Items – Profile Options
h n
Model
o
B • nResponsibility: Oracle Pricing Manager
Set QP: Pricing Transaction Entity to Procurement.
Oracle Purchasing
prohibited
7 - PageCopyright©
s a
)ha
c om
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu Complex
h n
Model
o
Set QP: Source System Code to Oracle Purchasing.
Oracle Purchasing
prohibited
7 - PageCopyright©
s a
)ha
c om
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu Complex
h n
Model
o
Set QP: Licensed for Product to Purchasing
Oracle Purchasing
prohibited
7 - PageCopyright©
s a
)ha
c om
m ini ide
pg e Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
anu Complex
h n
Model
o
Set QP: Item Validation Org to the same inventory organization defined in Supplier –
Purchasing Financial Options
Oracle Purchasing
prohibited
7 - PageCopyright©
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
Bh Oracle n
Implementation
noAdvanced Pricing must be installed and configured.
Oracle Purchasing
prohibited
7 - PageCopyright©
Agenda Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
prohibited
7 - PageCopyright©
Mass Re-pricing of Purchasing Documents Description
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
an uRe-pricing
- tra of Purchase Documents - Description
h n
Mass
o
B The nretroactive price update program was introduced in 11i9 so that pricing rule updates on
Blanket Agreements could be efficiently rolled down to re-price existing releases. Release 12
Extends Mass Re-Pricing Support beyond Blanket Agreement releases.
You can now be able to re-price orders in batch using the existing “Retroactive Price Update”
concurrent program even if the orders were not sourced from Blankets.
This Concurrent Program is now capable of re-pricing transactions based on pricing rules
defined:
• On Oracle Advanced Pricing Price Lists/Modifiers
• And on Custom Pricing Hooks
Oracle Purchasing
prohibited
7 - PageCopyright©
Mass Re-pricing of Purchasing Documents Benefits
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
anuRe-pricing
- tra of Purchase Documents – Benefits
h n
Mass
no pricing scenarios outside of Blanket Purchase Agreement can be modeled, and then
B Complex
automatically apply any price changes with retroactive effect on existing documents.
It takes care of any required automatic reconciliation of prior accounting transactions and
adjustments to prior invoices and thus effectively reduces administrative cost by minimizing
manual interventions that would have been required to process invoice holds or other manual
adjustments.
Oracle Purchasing
prohibited
7 - PageCopyright©
Mass Re-pricing of Purchasing Documents Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
prohibited
7 - PageCopyright©
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a nu to
bh ens e
a (
l e lic
a
k ablr
h a
B as nsfer
on
Implementation
Oracle Pricing Manager
• Navigation: Price Lists > Price List Setup
• Navigation: Pricing Formulas > Formulas Setup
• Navigation: Modifiers > Modifier Setup
Oracle Advanced Pricing must be installed and setup.
Oracle Purchasing
prohibited
7 - PageCopyright©
Agenda Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
prohibited
7 - PageCopyright©
New User Interface for Oracle Purchasing Setups Description
s a
)ha
c om
m ini ide
p g e Gu
c a ent
r la @ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uUser Interface
- tra
h n
New
nothe majority of the forms setup pages have been redesigned with a new HTML UI. The
B In R12
new UI offers the same functionality as forms. Included is a list of setup pages that have an
HTML UI in R12:
• Purchasing Options
Navigation: Setup : Organizations > Purchasing Options
• Receiving Options
Navigation: Setup : Organizations > Receiving Options
• Hazard Classes
Navigation: Setup : Purchasing > Hazard Classes
• UN Numbers
Navigation: Setup : Purchasing > UN Numbers
• Quality Inspection Codes
Navigation: Setup : Purchasing > Quality Inspection Codes
• Line Types
Navigation: Setup : Purchasing > Line Types
Oracle Purchasing
prohibited
7 - PageCopyright©
• Document Types
Navigation: Setup : Purchasing > Document Types
• Control Purchasing Periods
Navigation: Setup : Financials : Accounting > Control Purchasing Periods
• Expense Account Rules
Navigation: Setup : Financials : Accounting > Expense Account Rules
• Buyers
Navigation: Setup : Personnel > Buyers
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
prohibited
7 - PageCopyright©
New User Interface for Oracle Purchasing Setups Benefits
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an uUser Interface
- tra - Benefits
h n
New
no layout increases user productivity.
B Intuitive
For the setup pages that are multi-org access enabled, you can now define setup attributes for
different operating units without having to switch responsibilities.
Oracle Purchasing
prohibited
7 - PageCopyright©
Agenda Part 2
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
prohibited
7 - PageCopyright©
Advanced Approval Support for Requisitions Description
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
ha
B as nsfer
anu -Approval
tra Support - Description
h n
Advanced
o Approvals
B • nParallel
• Support for Viewers
• Position Hierarchy Support
Oracle Purchasing
prohibited
7 - PageCopyright©
Advanced Approval Support for Requisitions Benefits
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
a n u to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
anu -Approval
tra Support – Benefits
h n
Advanced
o up the approvals process.
B • nSpeeds
• With the need to involve more approvers, it may take a long turnaround time for the
requisition to be approved. Parallel Approvals can alleviate the turnaround time.
• Increase Flexibility for setting up approval Routes
• Voting regime provides flexibility for an organization to define approval rules, it can also
help to speed up the turnaround time.
• Reduce Setup Efforts
• If an organization has already set up Rules for other product, the same rules can be applied
to Requisitions approvals.
Oracle Purchasing
prohibited
7 - PageCopyright©
Advanced Approval Support for Requisitions Parallel Approvals
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -Approval
tra Support
h n
Advanced
no with the Sarbanes Oxley Regulation requirements, organizations may need more
B To comply
approvers in requisition approvals. Parallel approvals allow several approvers to act
simultaneously. Parallel approvals can be set up for individuals or approval groups
Oracle Purchasing
prohibited
7 - PageCopyright©
Advanced Approval Support for Requisitions Voting Method
s a
)ha
c o m
m ini ide
p g e Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
h a
B as nsfer
an u -Approval
tra Support – Voting Method
h n
Advanced
no
B As sometimes it is necessary both to seek approvals in parallel and also to choose how that
group asserts an approval, AME makes it possible to define approval rules so that:
• Any single person can approve on behalf of an approval group (First responder wins)
• All approvers within an approval group must approve the requisition even when the group
is being notified in parallel (Consensus)
• Multiple approval groups should also be able to be notified in parallel, each with their own
order number with each contributing to the final approval process
• The voting method can also be setup for chain of authorities. A chain of authority is a set
of approvers returned based on position hierarchy/employee-supervisory rules.
Oracle Purchasing
prohibited
7 - PageCopyright©
Advanced Approval Support for Requisitions Position Hierarchy
Support
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
an u to
bh ens e
a (
l e lic
a r
k abl
h a
Bas nsfer
anu -tra
non Approval Support – Position Hierarchy Support
BhAdvanced
Human Resources typically use positions and position hierarchies to define management line
reporting. Positions and position hierarchies allow customers to define approval routing
structures that remain stable regardless of how frequently individual employees leave their
organization or relocate within it. Also, position hierarchies offer increased flexibility and
allow customers to define separate hierarchies for procuring various commodities.
The rules can be based on individual positions or specified hierarchy within an organization.
Position Hierarchies represent how many levels AME should climb in the given position
hierarchy from a given starting point position to complete the approver list. The positions are
always relative to a HR Position in question and are calculated at run-time.
Oracle Purchasing
prohibited
7 - PageCopyright©
Advanced Approval Support for Requisitions Setup and Process
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
B as nsfer
anu -Approval
tra Support – Setup and Process
h n
Advanced
o AME Conditions
B 1. nSetup
2. Setup AME Action Types
3. Setup AME Approver Groups (this step is optional)
4. Create AME Rules
5. Setup Requisition Approvals to use AME
The process is then executed as follows:
1. A requisition is created
2. At Step 2 of the checkout process, the approval list is generated by AME.
3. Based on the approval list generated, the notifications are sent to the corresponding
approvers.
Oracle Purchasing
prohibited
7 - PageCopyright©
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
b ash use t
a n u to
bh ens e
a (
l e lic
a r
k abl
ha
Bas nsfer
Bh Oracle n
Implementation
noApprovals Management is required.
Oracle Purchasing
prohibited
7 - PageCopyright©
Summary
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
prohibited
7 - PageCopyright©
s a
)ha
c om
m ini ide
pge Gu
c a ent
r la@ tud
k a is S
a h
bash use t
anu to
bh ens e
a (
l e lic
ar
k abl
h a
Bas nsfer
anu -tra
Bh non
Oracle Purchasing
prohibited
7 - PageCopyright©

Oracle SLA Concepts

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle SLA Concepts

Uploaded by

Copyright:

Available Formats

s a

Restricted Rights Notice

U.S. GOVERNMENT RIGHTS

Multi-Org Access Control Setup – Create Operating Unit ............................................................................2-12

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

• Functional knowledge of Oracle General Ledger

• Functional knowledge of Oracle Payables

• Functional knowledge of Oracle Purchasing

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

• System release bulletins

• Installation and user’s guides

• International Oracle User’s Group (IOUG) articles

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Passwords DROP USER scott

(ST) = Sub Tab

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

The following help navigation path, for example—

(Help) General Ledger > Journals > Enter Journals

—represents the following sequence of actions:

2. Under the General Ledger entry, expand Journals.

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle 2009. All rights reserved.

R12 Oracle Financials New Features Fundamentals Table of Contents

Copyright © Oracle, 2009. All rights reserved.

Copyright © Oracle, 2009. All rights reserved.

Copyright © Oracle, 2009. All rights reserved.

Copyright © Oracle, 2009. All rights reserved.

Copyright © Oracle, 2009. All rights reserved.

• Multi-Org Access Control

Copyright © Oracle, 2009. All rights reserved.

Copyright © Oracle, 2009. All rights reserved.