Period Close best practice for Oracle Fusion PPM

  1. Resolve current cost transaction exceptions.
  2. Load all cost transactions from external systems into the cost transaction interface table.
  3. Import and process cost transactions for all business units and transaction sources. Select ‘All statuses’ and enter the period end date as the process through expenditure item date. Review the output and resolve any exceptions.
  4. Import all external commitment transactions. Enter ‘All’ as the source type and ‘All transactions’ as the process mode. Review the output and resolve any exceptions.
  5. Distribute borrowed and lent amounts for all business units. Be sure to enter the parameters for both the ‘Identify Cross-Charge Transactions’ and the ‘Distribute Borrowed and Lent Amounts’ processes. Enter the period end date as the process through expenditure item date. Review the output and resolve any exceptions.
  6. Generate burden transactions for each business unit. Select ‘All’ as the transaction status. Review the output and resolve any exceptions.
  7. Navigate back to the cost work area and verify there are no exceptions or unreleased expenditure batches.
  8. Resolve current revenue transaction exceptions.
  9. Generate revenue for all business units. Enter the period beginning and end dates as the from and to dates. Select ‘No’ for pending adjustments only and ‘Summary’ for generating ineligible data. If additional information is needed about ineligible data, the process can be run again with the option to generate ineligible data set to ‘Detail’; however, it should initially be run in summary mode to minimize potential BIP issues. Review the output and resolve any exceptions using the Manage Billing Transaction Exceptions page.
  10. Verify all invoices have been generated, approved, and released.
  11. Transfer the invoice details to receivables for each business unit. Review the output and resolve any exceptions.
  12. Submit AutoInvoice in Oracle Fusion Receivables process the project contract invoices.
  13. Update the invoice details from receivables for each business unit. Review the output and resolve any exceptions.
  14. Navigate back to the invoice work area to verify all invoices have been accepted in the Released tab. Resolve any problems with invoices added to the Exception tab with a status of transfer rejected and return to the step to transfer invoice details to receivables. Recalculate currency conversion for any invoices added to the Exception tab with a status of accepted.
  15. Manage and reclassify billing offset balances as needed for each business unit. Review the output and resolve any exceptions.
  16. Create accounting for each ledger from the cost or revenue work area. Leave the process category blank and enter the period end date in the process end date. Select ‘Final’ as the process mode and ‘No’ in the process errors only parameter. Select the summary report style. If additional exception information is needed, the create accounting process can be run again in detail; however, it should initially be run in summary mode to minimize potential BIP issues. Review the output and resolve any exceptions. If there are exceptions that cannot be resolved, unaccounted transactions can be swept to the next period.
  17. Post any remaining journal entries to each general ledger. Selecting the Subledger Application ‘Project Costing’ will transfer both cost and revenue journal entries. Enter the period end date as the process end date. Review the output and resolve any exceptions.
  18. Review the Subledger Period Close Exceptions Report to verify all accounting issues are resolved and all journal entries are transferred. Review the output and resolve any exceptions. If there are technical issues and some transactions cannot be accounted, the transactions can be swept to the next period.
  19. Review the Project Accounting Period Close Exception Report for each business unit. Select the summary report style. At this point, the number of exceptions should be minimal. If there is an unusually large number of exceptions, new transactions may have been entered after the previous steps were completed. Repeat the previous steps until the number of exceptions is reduced. If additional exception information is needed, the report can be run again in detail; however, it should initially be run in summary to minimize potential BIP issues. Review the output and resolve any exceptions. If there are exceptions that cannot be resolved, unaccounted transactions can be swept to the next period.
  20. Review the Accounting Period Close Exception Report for each ledger. Select the summary report style. At this point, the number of exceptions should be minimal. If there is an unusually large number of exceptions, new transactions may have been entered after the previous steps were completed. Repeat the previous steps until the number of exceptions is reduced. If additional exception information is needed, the report can be run again in detail; however, it should initially be run in summary to minimize potential BIP issues. Review the output and resolve any exceptions. If there are exceptions that cannot be resolved, unaccounted transactions can be swept to the next period.
  21. If there are technical issues preventing transactions from being accounted, the unaccounted transactions can be swept to the next period. The sweep cannot be reversed, so this should be the last step before closing the period.
  22. Run the Project Accounting Period Close Exception Report and the Accounting Period Close Exception Report again to verify that nothing is preventing the period from being closed and that there aren’t any new warnings.
  23. Close the project accounting period from Manage Project Accounting Periods. Review the output and resolve any exceptions.
  24. Close the accounting period from Manage Accounting Periods. Review the output and resolve any exceptions.

Leave a Comment

Social media & sharing icons powered by UltimatelySocial