Steps as required for year End Close in Oracle EBS.

These are the some of the standard steps performed for year-end processing in Oracle General Ledger.

1. Set the status of the first accounting period in the new fiscal year to Future Entry. Generally the first period of the new fiscal year should not be opened until all of the year-end processing for the last period of the current year has completed.

2. (Optional) Create reversing entries at the beginning of every period, generate and post accruals from the prior period now.

3. If you have other source make transfer data from all of subledgers and feeder systems to the GL_INTERFACE table.

4. Then ,run the Journal Import process to populate the GL_JE_BATCHES, GL_JE_HEADERS, and the GL_JE_LINES tables. This can be done automatically from the subledger systems, or manually from Oracle General Ledger.

5. Now the next is review the Journal Import Execution Report to check the status of all imported journal entries.

6. If there is any error journal entry batches, delete it.

7.a. If you encounter a small number of errors, make the necessary corrections in the GL_INTERFACE table using the Correct Journal import Data window. Run Journal Import.

7.b . If you encounter a large number of errors, delete the Journal Import data from the GL_Interface table, correct the information in the feeder or subledger system and run Journal Import.

8. Close the period for each subledger. This prevents future subledger transactions from being posted to General Ledger in the same period as part of regular month end close process.

9. Review the imported journal entries in Oracle General Ledger. These can be reviewed online or in reports. Reviewing journal entries before posting minimizes the number of corrections and changes that need to be made after posting.Normally these Reports are run for review.

• Journal Batch Summary Report
• General Journal Report
• Journal Entry Report
• Journal Line Report
• Journal Source Report
• Journals by Document Number Report (This is when document sequencing is used)
• Unposted Journals Report.

10. Then the Post all the imported journal entries.

11. Perform reconciliations of ledgers by reviewing and correcting balances.The following reports are useful to help with the reconciliation:

• Account Analysis with Payables Detail
• Account Analysis with Subledger Detail
• Account Analysis with Subledger Detail II
• General Ledger Report
• Posted Journals Report
• Journals Report with Subledger Detail
• Accrual Reconciliation Report
• Other Reports

12. Generate all recurring journals.

13. (Optional) If you did not generate and post your prior period reversals at the beginning of this period, be sure to generate reversals now.

14. Running the revaluation process to get revalue balances to update foreign currency journals to the functional currency equivalents.

15. Then the posting all journal wheather its is manual, recurring, step-down allocations, and reversals.

16. Review your posting results. The following reports are helpful:

• Posting Execution Report
• Error Journals Report

17. Update any unpostable journal entries and then post them again. Common reasons for unpostable batches include:

• Control total violations
• Posting to unopened periods
• Unbalanced journal entries

All errors in the journal entry batches must be corrected and resubmitted for posting.

18. Run General Ledger reports, such as the Trial Balance reports, Account Analysis reports, and Journal reports.

19. Consolidate the other sets of books if you instance is having multiple Operating units.

20. If using a calendar with an adjusting period that represent the last day of the fiscal year, close the current period and open the adjusting period.

21. Create and post adjusting entries and accruals in the adjusting period.

22. Run Trial Balance reports and other General Ledger Reports in the adjusting period after adjustments are made.

23. Post the Balance Sheet Closing Journal by submitting the Create Balance Sheet Closing Journals program, once this is done balance sheet will now reflect zero balances which is same as mention above.

24. Close the last period of the fiscal year using the period window.

25. Open the first period of the new fiscal year to launch a concurrent process to update account balances. Opening the first period of a new year automatically closes our your income statement and posts the difference to your retained earnings account specified in the Set of Books form.

26. Run FSG reports for the last period of the year.

Impact on Reporting due to 11i to R12 Upgrade

Tables/views Dropped:
1.How the retro fitment will work for the report having 11i data objects which have been dropped in R12. For eg: A report fetching data from 11i PO_VENDORS
table which has been dropped in R12 and replaced by a view.

New functionality Impact:
2.What is the impact of new functionalities on the retro fitment. For eg: Report currently fetching data from ra_cust_trx_line_gl_dist_all. In such a case, should
the report point to new SLA tables or continue to point to the transaction distribution tables. Is there any impact, if the report continues to fetch data from the
distribution tables instead of SLA tables.

3. Are there any new table joins as part of R12 new functionality For eg: Whether an AP report pointing to AP_INVOICE_DISTRIBUTIONS_ALL will show the
correct picture with the introduction of new invoice lines model in AP in R12 OR a join would be required between the new lines table with the distribution table
to fetch the same set of records.

Coexisting tables:
4.There are some coexisting tables in R12. For eg: Oracle Payments is a new module in R12. Whether a report which is fetching data from AP_INV_SELECTION_CRITERIA_ALL
in 11i should continue to fetch the data from the same table or it should point to the new IBY tables in R12.

Queries to Check All SL Entries for an AP Invoices

--XLA_EVENTS

SELECT DISTINCT xe.*

FROM ap_invoices_all ai,

xla_events xe,

xla.xla_transaction_entities xte

WHERE xte.application_id = 200

AND xte.application_id = xe.application_id

AND ai.invoice_id = '188101'

AND xte.entity_code = 'AP_INVOICES'

AND xte.source_id_int_1 = ai.invoice_id

AND xte.entity_id = xe.entity_id

ORDER BY

xe.entity_id,

xe.event_number;

--XLA_AE_HEADERS

SELECT DISTINCT xeh.*

FROM xla_ae_headers xeh,

ap_invoices_all ai,

xla.xla_transaction_entities xte

WHERE xte.application_id = 200

AND xte.application_id = xeh.application_id

AND ai.invoice_id = '188101'

AND xte.entity_code = 'AP_INVOICES'

AND xte.source_id_int_1 = ai.invoice_id

AND xte.entity_id = xeh.entity_id

ORDER BY

xeh.event_id,

xeh.ae_header_id ASC;

--XLA_AE_LINES

SELECT DISTINCT xel.*,

fnd_flex_ext.get_segs('SQLGL','GL#', '50577' ,xel.code_combination_id) "Account"

FROM xla_ae_lines xel,

xla_ae_headers xeh,

ap_invoices_all ai,

xla.xla_transaction_entities xte

WHERE xte.application_id = 200

AND xel.application_id = xeh.application_id

AND xte.application_id = xeh.application_id

AND ai.invoice_id = '188101'

AND xel.ae_header_id = xeh.ae_header_id

AND xte.entity_code = 'AP_INVOICES'

AND xte.source_id_int_1 = ai.invoice_id

AND xte.entity_id = xeh.entity_id

ORDER BY

xel.ae_header_id,

xel.ae_line_num ASC;

--XLA_DISTRIBUTION_LINKS

SELECT DISTINCT xdl.*

FROM xla_distribution_links xdl,

xla_ae_headers xeh,

ap_invoices_all ai,

xla.xla_transaction_entities xte

WHERE xte.application_id = 200

AND xdl.application_id = xeh.application_id

AND xte.application_id = xeh.application_id

AND ai.invoice_id = '188101'

AND xdl.ae_header_id = xeh.ae_header_id

AND xte.entity_code = 'AP_INVOICES'

AND xte.source_id_int_1 = ai.invoice_id

AND xte.entity_id = xeh.entity_id

ORDER BY

xdl.event_id,

xdl.a_header_id,

xdl.ae_line_num ASC;

--XLA_TRANSACTION_ENTITIES XLA_EVENTS

SELECT DISTINCT xe.*

FROM ap_invoices_all ai,

xla_events xe,

xla.xla_transaction_entities xte

WHERE xte.application_id = 200

AND xte.application_id = xe.application_id

AND ai.invoice_id = '188101'

AND xte.entity_code = 'AP_INVOICES'

AND xte.source_id_int_1 = ai.invoice_id

AND xte.entity_id = xe.entity_id

ORDER BY

xe.entity_id,

xe.event_number;

XLA_AE_HEADERS

SELECT DISTINCT xeh.*

FROM xla_ae_headers xeh,

ap_invoices_all ai,

xla.xla_transaction_entities xte

WHERE xte.application_id = 200

AND xte.application_id = xeh.application_id

AND ai.invoice_id = '188101'

AND xte.entity_code = 'AP_INVOICES'

AND xte.source_id_int_1 = ai.invoice_id

AND xte.entity_id = xeh.entity_id

ORDER BY

xeh.event_id,

xeh.ae_header_id ASC;

--XLA_AE_LINES

SELECT DISTINCT xel.*,

fnd_flex_ext.get_segs('SQLGL','GL#', '50577' ,xel.code_combination_id) "Account"

FROM xla_ae_lines xel,

xla_ae_headers xeh,

ap_invoices_all ai,

xla.xla_transaction_entities xte

WHERE xte.application_id = 200

AND xel.application_id = xeh.application_id

AND xte.application_id = xeh.application_id

AND ai.invoice_id = '188101'

AND xel.ae_header_id = xeh.ae_header_id

AND xte.entity_code = 'AP_INVOICES'

AND xte.source_id_int_1 = ai.invoice_id

AND xte.entity_id = xeh.entity_id

ORDER BY

xel.ae_header_id,

xel.ae_line_num ASC;

--XLA_DISTRIBUTION_LINKS

SELECT DISTINCT xdl.*

FROM xla_distribution_links xdl,

xla_ae_headers xeh,

ap_invoices_all ai,

xla.xla_transaction_entities xte

WHERE xte.application_id = 200

AND xdl.application_id = xeh.application_id

AND xte.application_id = xeh.application_id

AND ai.invoice_id = '188101'

AND xdl.ae_header_id = xeh.ae_header_id

AND xte.entity_code = 'AP_INVOICES'

AND xte.source_id_int_1 = ai.invoice_id

AND xte.entity_id = xeh.entity_id

ORDER BY

xdl.event_id,

xdl.a_header_id,

xdl.ae_line_num ASC;

--XLA_TRANSACTION_ENTITIES

SELECT DISTINCT xte.*

FROM ap_invoices_all ai,

xla.xla_transaction_entities xte

WHERE xte.application_id = 200

AND ai.invoice_id = '188101'

AND xte.entity_code = 'AP_INVOICES'

AND xte.source_id_int_1 = ai.invoice_id;

--XLA_ACCOUNTING_ERRORS

SELECT DISTINCT xae.*

FROM ap_invoices_all ai,

xla_events xe,

xla.xla_transaction_entities xte,

xla_accounting_errors xae

WHERE xte.application_id = 200

AND xae.application_id = xte.application_id

AND xte.application_id = xe.application_id

AND ai.invoice_id = '188101'

AND xe.event_id = xae.event_id

AND xte.entity_code = 'AP_INVOICES'

AND xte.source_id_int_1 = ai.invoice_id

AND xte.entity_id = xe.entity_id;

SELECT DISTINCT xte.*

FROM ap_invoices_all ai,

xla.xla_transaction_entities xte

WHERE xte.application_id = 200

AND ai.invoice_id = '188101'

AND xte.entity_code = 'AP_INVOICES'

AND xte.source_id_int_1 = ai.invoice_id;

--XLA_ACCOUNTING_ERRORS

SELECT DISTINCT xae.*

FROM ap_invoices_all ai,

xla_events xe,

xla.xla_transaction_entities xte,

xla_accounting_errors xae

WHERE xte.application_id = 200

AND xae.application_id = xte.application_id

AND xte.application_id = xe.application_id

AND ai.invoice_id = '188101'

AND xe.event_id = xae.event_id

AND xte.entity_code = 'AP_INVOICES'

AND xte.source_id_int_1 = ai.invoice_id

AND xte.entity_id = xe.entity_id;