Book Image

Oracle E-Business Suite Financials R12: A Functionality Guide

By : Mohan Iyer
Book Image

Oracle E-Business Suite Financials R12: A Functionality Guide

By: Mohan Iyer

Overview of this book

<p>Oracle EBS Financials provide organizations with solutions to a wide range of long- and short-term accounting system issues. Oracle E-Business Suite is the most comprehensive suite of integrated, global business applications that provides the most complete, integrated business intelligence portfolio<br /><br />Oracle E-Business Suite: A Functionality Guide – helps in binding the two skill sets together – knowledge of the software and the business knowledge of the user.<br /><br />This guide contains everything you need to know to maximize your implementation payback or return on investment.<br /><br />This book starts with an overview of Oracle E-Business Suite R12 where we cover the foundation features of Oracle Financial Management modules which include Navigation within Oracle E-Business Suite Release 12, Multiple Organization Access Control (MOAC), key aspects of Application Security and much more. The book then covers in detail General Ledger, Sub Ledger Accounting, Assets, Cash Management, Treasury, E-Business Tax, and much more.</p>
Table of Contents (24 chapters)
Oracle E-Business Suite Financials R12: A Functionality Guide
Credits
Foreword
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Accounting Policy Management


There are management initiatives that would be best served if these were tightly integrated with the transactional system. The following tasks highlight these aspects to ensure that this control is enforced.

Comprehensive Accounting

In pre-R12 versions the subledgers all transferred to GL and the balancing lines were created after they were transferred to GL. The balancing transactions were primarily a GL activity. Thus, if you had intercompany transactions you would not see the balancing entries in the subledgers. This has changed in R12 and the balancing entries are created in the SLA, which is part of the subledgers.

Access to the SLA journal functionality is through the subledgers and not the GL. You do not have a separate product (or responsibility) that allows access to the SLA; there are functions within the subledger products that allow access to the relevant capabilities, forms, and reports in SLA.

You cannot close the subledgers unless these SLA journals...