Oracle Financials E-Business Suite Release 12 Period End Procedures
This document has been put together by members of Oracle's internal EMEAFinancials Professional Community, acknowledging that every Financials customerneeds to successfully close the accounting books each period. Before the first externalpublication, various people from EMEA Applications Consulting and FinancialsProduct Development have reviewed and enriched the content. Read the paragraph‘Status and Feedback’ below, if you have any comments or feedback.
This document provides guidance on period end procedures in Release 12 for OraclePayables, Oracle Purchasing, Oracle Inventory, Oracle Order Management, OracleReceivables, Oracle Assets, Oracle Projects, Oracle Cash Management, OracleTreasury and Oracle General Ledger. It is intended to be generic, and does not relateto a specific organization. Both mandatory and optional steps are included herein.Procedures particular to year-end processing are also described.This document intends to provide a reference for planning period-end procedures for‘real-life’ implementations. It describes the fundamental period-end steps involvedfor each, with particular emphasis on balancing the subledger applications to OracleGeneral Ledger, and attempts to provide an overview of the relative timing of theseprocedures for all installed Oracle applications.It is therefore the intention of this document to provide content from which relevantsections can be extracted, according to the applications installed for a particularorganization. Any organization may choose to customize their period-end and year-end processes, for example opting to run additional reports, particular to theorganization.Although this document particularly refers to ‘Period-End Procedures’, many of theprocesses can be performed more regularly throughout the accounting period, asrequired. Each subledger application provides control as to when and how often datais transferred from the subledger application to the General Ledger.
These ‘Period-End Procedures’ were written with the assumption that OracleFinancials was implemented for a single operating unit. Where an organization hasimplemented the ‘Multi-Org’ features of Oracle Financials, these procedures wouldneed to be performed for each operating unit individually unless Multi-Org AccessControl is enabled.
: R12 requires multi-org functionality to be used. For further details refer toOracle® Applications Upgrade Guide: Release 11i to Release 12 Oracle Workflow is incorporated in the Release 12 applications. It is assumed thatthese Workflow Processes will be monitored and attended to by a SystemAdministrator on a regular basis. Some Workflow Processes like the RequisitionApproval Workflow or the Purchase Order Approval Workflow will require a directresponse from a message recipient rather than a System Administrator.
This white paper contains twelve chapters and one appendix where you can findinteresting links to more information.