2/4/13

Document Display

Period Close Procedures And Exceptions in Oracle Projects Release 12 [ID 1336233.1]
Modified: Jul 10, 2012 Type: REFERENCE Status: PUBLISHED Priority: 2

In this Document Purpose Scope Details Overview Period Close Validation Enhanced Period Processing Maintain Common PA and GL Periods Period Close Exceptions The EXC: Transaction Exception Reports EXC: Transaction Exception Detail Reports EXC: Transaction Exception Summary Reports Exception Category Details The Subledger Period Close Exceptions Report References

Applies to:
Oracle Project Foundation - Version 12.0.3 to 12.1.3 [Release 12.0 to 12.1] Information in this document applies to any platform. Form:PAXSUMPS.FMB - PA Periods Form:PAXPAGLP.FMB - GL Periods Report:PAXEXCPD.RDF - EXC: Transaction Exception Details by PA Period Report:PAXEXCPS.RDF - EXC: Transaction Exception Summary by PA Period ConcurrentProgram:PAXEXGLD - EXC: Transaction Exception Details by GL Period ConcurrentProgram:PAXEXGLS - EXC: Transaction Exception Summary by GL Period ConcurrentProgram:XLAPEXRPT - Subledger Period Close Exceptions Report

Purpose
This document is intended to provide information and resources to assist you in performing period end close activities in Oracle Projects and to provide some guidance for handling exceptions that may prevent your period from closing.

Scope
This information is specifically addressing the period close process in Oracle Projects Release 12.0 and 12.1.

Details Overview
The basic steps involved in closing periods in Oracle Projects are as follows: 1. Change the Current Oracle Projects Period Status from Open to Pending Close 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. Open the Next Oracle Projects Period Complete all Maintenance Activities Run Maintenance Processes Complete All Transactions for the Period Being Closed Run the Cost and Borrowed and Lent Distribution Processes Run the Generate Cost and Cross Charge Accounting Events Programs Interface Cost and Cross Charge Transactions to Other Applications Generate Draft Revenue for All Projects Review and Release Revenue for All Projects Run the Generate Revenue Accounting Events Process Run the Create Accounting to Process Revenue Accounting Events Generate Invoices Transfer Invoices to Oracle Receivables Run Period Close Exceptions and Tieback Reports Run Final Project Costing and Revenue Management Reports Change the Current Oracle Projects Period Status from Pending Close to Closed Advance the PA Reporting Period (Optional) Update Project Summary Amounts Restore Access to User Maintenance Activities Reconcile Cost Distribution Lines with General Ledger (Optional) Permanently Close the Oracle Projects Period (Optional)

The full details of the activities associated with each of these steps are described in the EBusiness Suite (EBS) Period close advisor under the Projects tab. (Note 335.1). This list and the detailed activities provided in the aforementioned advisor note provide an excellent guideline for the activities that are required for a successful period close in Projects.

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=x4kiva9xq_246

1/7

2/4/13
Period Close Validation

Document Display

The table below illustrates the validations that are performed by the system when you change the status of a PA or GL period to 'Closed' in Oracle Projects. The validations and the results will depend on whether you use enhanced period processing (EPP) and whether you maintain common PA and GL Periods. Enhanced Period Processing This feature controls (among other things) whether or not the user has the ability to open and close GL periods at the subledger application level for Projects. If it is not enabled, then GL periods for projects are maintained in GL only. The use of this feature is controlled at the site level by the profile option PA: Enable Enhanced Period Processing as illustrated below:

Maintain Common PA and GL Periods If PA Periods and the GL Accounting periods are of the same type, and the user wishes to maintain their status in a single operation rather than independently opening and closing PA and GL periods, he may enable this option. This option is only available if EPP is also enabled. The use of this feature is controlled by the operating unit level implementation option setting illustrated below (Navigation: Setup -> System -> Implementation Options -> System Tab)

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=x4kiva9xq_246

2/7

2/4/13

Document Display

In the table "EPP = Y/N" indicates whether or not enhanced period processing is enabled, and "Common Periods = Y/N" indicates whether or not common PA and GL periods are being maintained. The validation for transactions whose accounting events are not generated in Subledger Accounting (SLA)--the first item in the table--includes events for the following types of transactions: Pre-approved batch cost distributions Cost distributions for expenditure items imported to Projects as unaccounted Supplier Invoice and Expense report cost adjustments made in Projects Revenue distributions Cross charge distributions Total Burdened cost distributions

EPP=N

EPP = Y EPP = Y Common Periods Common Periods =N =Y

GL Period Error None None None Warning PA Period N/A N/A N/A N/A N/A GL Period Error Warning Warning Error Warning

PA Period Accounting Events for Projects Transactions are not Generated in SLA Projects-related supplier invoices or expense reports in Payables not Interfaced to Projects Receipts for project-related purchase orders in Purchasing not interfaced to Projects Project-related transactions in Project Manufacturing/Inventory are not interfaced to Projects Transactions in Projects are not cost distributed Error

GL Period N/A

PA Period None Warning Warning Warning Warning

Warning N/A Warning N/A Warning N/A Warning N/A

Period Close Exceptions https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=x4kiva9xq_246

3/7

2/4/13 Period Close Exceptions

Document Display

Projects includes a number of standard reports to assist with the identification and correction of exceptions that may interfere with your period close procedures. These include: EXC: Transaction Exception Details by GL Period (PAXEXGLD) EXC: Transaction Exception Details by PA Period (PAXEXCPD) EXC: Transaction Exception Summary by GL Period (PAXEXGLS) EXC: Transaction Exception Summary by PA Period (PAXEXCPS) Subledger Period Close Exceptions Report (XLAPEXRPT) To close GL and PA periods in Projects it is only required that you have generated accounting events for all of your subledger transactions. These do not need to be finally accounted and transferred to GL. The Subledger Period Close Exceptions Report will provide details of what accounting events have been generated, but not finally accounted and imported into GL.

The EXC: Transaction Exception Reports The EXC: Transaction Exception reports should be used when attempting to close a PA Period or GL Period for Projects. These reports search for and report on transactions in a specific range of PA or GL periods which would result in a warning or error during period closure. When you attempt to close a PA or GL period, the system will perform the validations described above, and if exceptions are found, it will report them either as a warning (which will still allow you to close the period):

or as an error (which will not)

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=x4kiva9xq_246

4/7

2/4/13

Document Display

In either case you can see that the system will refer the user to the EXC: Transaction Exception reports to obtain the details of the transactions that have generated the warning or error. There are two types of transaction exception reports, detailed and summary, and the two should be used in tandem to help determine what transactions are causing the warning or error and what needs to be done to clear it. EXC: Transaction Exception Detail Reports The detail reports provide specific transaction details grouped by the exception category (discussed in more detail below) and the specific exception encountered within that category. These reports (there is one for PA and one for GL periods) can be run for a range of periods, and you can limit the report to a particular type of exception. They allow the user the ability to pinpoint the specific transactions that are encountering some kind of issue in the period close validation. EXC: Transaction Exception Summary Reports The summary reports do not provide specific transaction information, but rather a summary count of transactions and a total amount for each exception type. For each exception type found on the report, the summary report additionally suggests a corresponding corrective action to assist with clearing this type of exception. As such these reports should be used in conjunction with the detail reports. The latter providing the details of what transactions have issues, and the former to indicating the corrective actions for clearing those exceptions.

Exception Category Details

The table below lists the various exception categories reported on by these reports. These exception categories are defined in PA_LOOKUPS with lookup_type = 'EXCP_LEVEL_TYPE'. A detailed description of each type of exception, and how the report determines these exceptions follows: Category Code COST_EXCP REV_EXCP CC_EXCP UNCOST_EXCP AP_INV_EXCP RECEIPT_EXCP MFG_EXCP Costing Exceptions Revenue Exceptions Cross Charge Accounting Exceptions Uncosted Transactions Accounts Payable Invoice Exceptions Receipt Accrual Exceptions Project Manufacturing/Inventory Exceptions Description

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=x4kiva9xq_246

5/7

2/4/13

Document Display

Costing Exceptions: Although the category name would seem to imply it, these are not exceptions with cost distribution. When expenditure items are cost distributed in Projects, distribution records (cost distribution lines, or CDL's) are created in the table PA_COST_DISTRIBUTION_LINES_ALL. Costing exceptions refer to issues with the subsequent processing and accounting of these cost distribution lines. They are items that are already cost distributed and therefore have cost distribution lines, but these distributions have either not been interfaced to SLA and accounted or they have not been processed for burdening. This category applies to all types of expenditure items and adjustments that generate cost distribution lines in Projects. The process which interfaces these distribution lines to SLA is the "PRC: Generate Cost Accounting Events" process. Costing exceptions will be reported either if this process has not been run, or if there is some error or exception in the process for a distribution line. When exceptions occur while generating the cost accounting events, a value is stored in the column TRANSACTION_REJECTION_REASON for the cost distribution line. This is the value that will be used to report the exception. If there is no transfer rejection reason, but the items transfer status indicates that it has not been processed, then the exception reported will simply be "New line not yet processed by Oracle Projects" The burdening process is "PRC: Create and Distribute Burden Transactions". If an item is eligible for burdening and has not been processed, or an exception has occurred during it's burden processing, a costing exception will also result result. When an issue occurs during burdening a value will be stored in the distribution line's BURDEN_SUM_REJECTION_CODE column, and this value will be used to report the specific exception on the report. If there is no rejection code, but the eligible distribution line has not been processed for burdening, the report will again give the exception "New line not yet processed by Oracle Projects" Revenue Exceptions Revenue exceptions refer to issues found with existing revenues in PA_DRAFT_REVENUES_ALL (not with the generation of revenue). These exceptions refer to revenues which have been generated, but have not been transferred to SLA/GL. The process which interfaces revenue distributions to SLA is "PRC: Generate Revenue Accounting Events". When there is a problem with this process, the reason for the problem will be stored in the column TRANSFER_REJECTION_REASON on the draft revenue. The exceptions reported will be based this value. If there is no rejection reason, but the revenue has not been transferred to SLA, it will be reported as a "New line not yet processed by Oracle Projects" Cross Charge Accounting Exceptions Cross charge exceptions refer to issues with cross charge distributions in PA_CC_DIST_LINES_ALL for which accounting events have not been successfully created in SLA. The process which transfers cross charge distributions to SLA is "PRC: Generate Cross Charge Accounting Events". When there is an issue generating the accounting event for a cross charge distribution, the cause of the issue will be indicated in the TRANSFER_REJECTION_CODE of the distribution line. The exception reported is based on this value. If this code is blank or is not found, the report will indicate an "Undefined" exception. An "Undefined" exception could simply indicate that the distribution has not been processed or it could mean that some issue has occurred which has not been mapped to an exception reason. When receiving an "Undefined" exception in this category, you should first run the "PRC: Generate Cross Charge Accounting Events" process, and if any exceptions occur in this process, you should address them. Once that process is reporting no exceptions, you can re-run the period close exception reports and the exceptions should be cleared. Uncosted Transactions These exceptions refer to expenditure items which have not yet been cost distributed. (That is: PA_EXPENDITURE_ITEMS_ALL.COST_DISTRIBUTED_FLAG = 'N'). If cost distribution was attempted but there was a problem, the distribution process will populate the reason for the error in the expenditure items' COST_DIST_REJECTION_CODE column. This value will be used to report the exception. Otherwise it will simply be reported that the item is not cost distributed, in which case you should simply run the appropriate cost distribution processes for the types of transactions being reported. The process which distributes a particular transaction will depend on the type of the expenditure item. Depending on the transaction you may have to run any or all of: PRC: PRC: PRC: PRC: Distribute Distribute Distribute Distribute Labor Costs Usage and Miscellaneous Costs Supplier Cost Adjustments Expense Report Adjustments

Accounts Payable Invoice Exceptions These exceptions result from project-related invoices and expense reports in Oracle Payables which have not been transferred to Projects. The process which interfaces these expenditures to projects is "PRC: Interface Supplier Costs". The specific exceptions reported are based on the value of the PA_ADDITION_FLAG column in AP_INVOICE_DISTRIBUTIONS_ALL. The values in this column are maintained by the interface process and reflect whether or not the item has been interfaced to Projects, and if not, why not. For each, an appropriate exception reason and corrective action are reported. In some cases the reason may simply be that the interface process (PRC: Interface Supplier Costs) has not been run for the transactions. In this case the item will be reported as a "New line not yet processed by Oracle Projects". Receipt Accrual Exceptions Receipt accrual exceptions also refer to eligible project-related transactions which have not been interfaced into Oracle Projects. In this case the transactions are receipt accruals. The process which interfaces these transactions to Projects is the same one used to interface supplier invoices: "PRC: Interface Supplier Costs". The exceptions are based on the PA_ADDITION_FLAG in the table RCV_RECEIVING_SUBLEDGER. This flag is maintained by the interface process, but the values are not as varied as those for supplier invoices. The values which represent exceptions are 'N', meaning that the receipt accrual has not been interfaced to Projects, or 'I', indicating that the tax amount for the receipt accrual is not interfaced to Projects. Project Manufacturing/Inventory Exceptions

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=x4kiva9xq_246

These exceptions also represent eligible project-related transactions in an external application which have not been transferred to Projects. In this case the

6/7

2/4/13

These exceptions also represent eligible project-related transactions in an external application which have not been transferred to Projects. In this case the transactions are material and wip transactions from Project Manufacturing and Inventory. This type of transaction is interfaced to Projects by running the Cost Collector process in Inventory, and then interfacing the transactions to Projects via the PRC: Transaction Import process. For these types of transactions, the report will indicate either a. the Cost Collector process in inventory has not been run for the transaction b. The Cost Collector encountered an error when processing the transaction c. The transaction has been transferred to Projects, but is still in the PA_TRANSACTION_INTERFACE table awaiting import to Projects. In the first two cases the issue will need to be addressed in the source application. Items which are pending import into Projects can be imported using the PRC: Transaction Import process.

Document Display

The Subledger Period Close Exceptions Report This report should be used when trying to close your GL period in General Ledger. Periods in Projects can be closed once your transactions have been successfully transferred to SLA (which is equivalent to saying that the accounting events have been successfully generated for them). However, before they will be reflected in the General Ledger, these events need to be accounted by running the PRC: Create Accounting process. This process can also interface the accounted events to GL, or that can be done at a later time by running the "PRC: Transfer Journal Entries to GL" process. The Subledger Period Close Exceptions report will report exceptions in these last steps between SLA and GL. It will report all unprocessed accounting events, that is, accounting events which have not been processed by the Create Accounting program to generate journal entries, as well as those that have been accounted in Draft mode, and those that have been accounted in Final mode, but which have not yet been transferred to the General Ledger.

For more information on the parameters and outputs of the various exception reports: The "EXC: Transaction Exception" reports above are fully documented, including the parameters, and complete output details in the Oracle Projects Fundamentals User Guide Chapter: "Reports and Listings". The "Subledger Period Close Exceptions Report" is documented including all parameters and output data elements in the Oracle Subledger Accounting Implementation Guide Chapter: "Subledger Accounting Reports"

References
NOTE:335.1 - Period Close Advisor: E-Business Suite (EBS) NOTE:961285.1 - R12: Period-End Procedures for Oracle Financials E-Business Suite

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=x4kiva9xq_246

7/7