My Oracle Support Banner

WS: FIN: How to Post Transactions to a Prior Period or Prior Year without Affecting the General Ledger (P09800) (Doc ID 798195.1)

Last updated on JULY 03, 2018

Applies to:

JD Edwards World Accounts Receivable - Version A7.3 cume 4 and later
JD Edwards World Accounts Payable - Version A7.3 cume 4 and later
JD Edwards World General Ledger - Version A7.3 cume 4 and later
Information in this document applies to any platform.

Goal

Questions on this document?  Click here for a quick response.

 

Occasionally, unposted batches are discovered after the Accounts Receivable (A/R), Accounts Payable (A/P), or General Accounting (G/L) periods are closed. The transactions must be posted to a closed period without affecting financial statements or reports that have been processed for it. Often you can reopen the period, void the transaction, and reenter it into the correct period; however, if the transaction is paid and you do not want to void the payment, this document provides a solution for posting to a closed period without affecting the financial statements or reports that have been processed for it.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 Step 1 - Review Accounts and G/L Dates
 Step 2 - Open the Prior Period or Prior Year
 Step 3 - Approve and Post the Batch
 Step 4 - Create Reversing Journal Entries
 Step 5 - Post the Journal Entry
 Step 6 - Reopen the Current Period
 Step 7 - Create Journal Entries to the Current Period
 Step 8 - Run the Batch Integrity Reports
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.