Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

Note: 335.1
How to use this Period Close Advisor:

This Period Close Advisor provides guidance on

recommended period end procedures for E-Business Release
12.x. The subledger application tabs are listed in the
recommended order of closing based on the data flow
dependency as shown in the diagram. Step by step best
practices with tips and troubleshooting references are
provided to assist you through each phase. Review the
'Using the Period Close Advisor' section under the 'Intro' tab
for more details on how to use this advisor.

Payables:

This tab describes the processes and activities required for a

successful period close in Oracle Payables Release R12.
Oracle Payables improves margins, instills corporate and
fiscal discipline, and optimizes business relationships.
Accounts Payable activity must be reconciled for the accounting period that is to be closed.

Evaluate & Prepare

Preparing for Period Close begins with thorough product training to establish proper application setup and
usage. User Guides, Product Information Centers, and other key documents are linked within this advisor and
provide detailed product information that should be reviewed.

Evaluating and maintaining current code levels is also essential to a successful period close. As a Best
Practice, you should always ensure you are on the latest code with recommended patches applied. This will
help avoid known issues, prevent potential data corruption and provide the latest features and functionality.
Having a proactive patching plan and periodic proactive patching process is the best way to stay current.
Please review the following documents for guidance in this area:

Document: 313.1 Patching & Maintenance Advisor: E-Business Suite (EBS) 11i and R12

Document: 976188.1 Patch Wizard Utility

To search for recommended patches within My Oracle Support:

Navigation:
1. Login to 'My Oracle Support' (MOS)
2. Click on the 'Patches & Updates' tab
3. In the Patching Quick Links box on the left, click 'Recommended R12 Patches' under the Oracle
E-Business Suite heading

1 of 13 12/17/2019, 12:18 PM
Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

4. In the Maintenance Release LOV, select your version

5. Under Product or Family, select your product area
6. Select your Platform, then click 'Go'

Attention: Critical Patches will be marked with and exclamation mark '!' and Recommended
Patches will be marked with a 'check'

For more details, see Document: 1400757.1 12.1.3 How to Find E-Business Suite Recommended
Patches

In addition, many E-Business Suite products have diagnostics and health checks that can proactively look for
issues within your data so they can be resolved as soon as they are detected. Those proactive diagnostics are
linked where relevant within the steps in this advisor. The link to the full catalog is below:

Document: 421245.1 E-Business Suite Diagnostics References for R12

1. Review Training Material

Document: Oracle Payables User's Guide Release 12.0 / Release 12.1 / Release 12.2

Document: Oracle Payments User's Guide Release 12.0 / Release 12.1 / Release 12.2

Document: 1196096.1 Payables Product Information Center

2. Validate Setup

Incorrect or incomplete setup within the product can cause data issues. Run the setup diagnostic listed and
review the recommendations in the output to see if there are corrections that need to be made.

Diagnostic: 463525.1 Oracle Payables General Setup Test

Detail vs. Summary Level Accounting and Posting

The level of detail during accounting and level of detail during GL Transfer for Oracle Payables must be
determined when planning period-end procedures. Where detail level accounting transactions are required to
be posted to the General Ledger using subledger accounting (SLA), there may be technical constraints
involved, relating to the physical data storage volume, and posting and report processing speed degradation
caused by the sheer volume of posted transactions.

In Release 12 the detailed level of posting can be controlled by GL summarize options and also at SLA
journal line type level. Subledger Accounting can contain all of the detailed subledger accounting level
analysis, so that the general ledger can remain 'thin'. Then, Subledger Accounting online inquiry and BI
Publisher reports can be utilized to report and analyze balances, and their transactions.

Document: 876190.1 R12: FAQ on Transfer to GL in R12

3. Apply Recommended Patches

To help ensure data consistency, apply the latest recommended patches. The following document is updated
frequently with the latest patches recommended by development as they are released.

2 of 13 12/17/2019, 12:18 PM
Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

Document: 954704.1 EBS: R12.1 Oracle Financials Recommended Patches

Tip: All recommended patches are very important for period close being smooth, if time is a
constraint ensure at least the Payables Core RPC (Doc Id 1397581.1) applied. This patch is highly
targeted for Period Close and in addition it eliminates 80% of the GDF type Data Issues reducing
significantly Period Close exceptions and issues.

To allow for smooth period close, it is recommended to uptake the latest patch specific to Period Close
processes and reports.

Document: 437422.1 R12 Troubleshooting Period Close in Payables

4. Ensure Data Consistency

Payables development has created Generic Data Fix (GDF) patches for data issues detected from fixes to
application code. These GDF patches can be downloaded through My Oracle Support and can detect and fix
issues within your Payables data before they cause problems with processing or period close. Identifying in
advance which GDFs you may need to apply to avoid Period Close exceptions and issues could be a daunting
task. To radically simplify the task the Master GDF Diagnostic was created. This diagnostic which you can
easily install as a Concurrent Process allows for range scanning of transactions that will post in the current
period. Should any of the transactions have data issues the diagnostic will point out the exact GDF to run to
address the problem. This way you will be ahead of the exceptions addressing them before they actually
happen.

Document: 1446628.1 R12: Experience Smoother Accounting and Period Close By

Proactively Eliminating Data Integrity Issues (COLLAB12)

Diagnostic: 1360390.1 R12: Master GDF Diagnostic to Validate Data Related to Invoices,
Payments, Accounting and Suppliers [VIDEO]

Document: 1361255.1 How to Register the Master GDF Diagnostic as a Concurrent

Program

Document: 874903.1 What is a Generic Datafix Patch (GDF) and what GDFs are available
for Payables?

Tip: The general recommendation is to run periodically the Master GDF Diagnostic through
the month as you go accounting transactions. Run with date range based on how much data
volume your business has (more volume > run often with a shorter date range). Create
Accounting is recommended to be done throughout the month such that if problems occur there
is time to address them.

Tip: Run the Master GDF Diagnostic proactively before large processes such as Create
Accounting, PPR, Trial Balance.

Tip: Run the Master GDF Diagnostic re-actively for a single transaction that does not
progress as expected: Invoice that wont cancel, Invoice with holds that do not clear, Invoice
refusing to account and showing in the Period Close Exception report and others.

3 of 13 12/17/2019, 12:18 PM
Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

5. Get Proactive!

The Period Close Advisor is just one of many proactive tools available. Please review the following
documents for a complete list of the proactive tools available and how to get training and accreditation for
using those tools.

Document: 432.1 Oracle Premier Support: Get Proactive!

Document: 1580100.1 Oracle Support Accreditation Series - E-Business Suite

Process Transactions
Ensure that all transactions have been entered for the period being closed.

1. Complete Invoices and Credits

Process all Invoices, Debit Memos, Credit Memos, Prepayments, Expense Reports, etc.

Tip: Should problems occur progressing a specific invoice, verify if the same has any data issues
that can be addressed quickly by running the Master GDF Diagnostic (Doc Id 1360390.1) in Single
Transaction Mode for the problem invoice.

Document: 1321090.1 Payables Invoice Info Center

Diagnostic: 732163.1 Oracle Payables Invoice Data Collection Test

2. Complete Invoice Import

The Payables Open Interface Import Program (APXIIMPT) is used to create Payables invoices from invoice
data entered in the Payables Open Interface tables AP_INVOICES_INTERFACE and
AP_INVOICE_LINES_INTERFACE.

Note: If you have any AGIS Intercompany Payables invoices, make sure you run the import
program for Source = Global Intercompany to import and process those invoices. For more
information on setup and transaction processing for AGIS, please review Document 418649.1. That
document includes an AGIS whitepaper and training viewlets to assist with setup and complete
processing of intercompany transactions in AGIS.

Document: 1321090.1 Payables Invoice Info Center: Open Interface Import

3. Import from external system or Internet Expenses

4 of 13 12/17/2019, 12:18 PM
Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

If you import transactions from an external system, or you are using Internet Expenses or Xpense Xpress,
ensure you have imported all transactions, and reviewed all audit trails for completeness.

4. Run Invoice Validation

The Invoice Validation process checks the matching tax, period status, exchange rate, and distribution
information for invoices you enter and automatically applies holds to exception invoices.

Document: 1321090.1 Payables Invoice Information Center: Validation

5. Review the Invoice on Hold Report

This report enables review of any holds currently applied to invoices that would prevent the payment and/or
posting of these invoices. The report details all invoices that Oracle Payables cannot select for posting and
therefore cannot create journal entries.

Tip: If invoices keep holds even after performing the necessary functional steps to clear them, run
the Master GDF diagnostic from Document 1360390.1 in single transaction mode for the invoices
affected. Address the data issues as the diagnostic indicates as data issues often cause holds that can't
be released.

Document: 1321090.1 Payables Invoice Information Center: Check Holds

Tip: Run frequently and resolve any identified holds which will prevent posting to GL, and then
re-run the Payables Approval process to approve these invoices.

6. Complete Payments

Process all payments (Manual, Quick, Refunds and Payment Process Requests)

Tip: Transactions that will be picked by the PPR can be health checked through the month
by periodically running the Master GDF Diagnostic (Doc Id 1360390.1) in date range chunks
(e.g weekly). The program will scan transactions that will be processed in the current month for
potential data issues that may affect the PPR negatively. Address issues as the MGD identifies
them.

Document: 1320497.1 Payables Payments Info Center: Master Troubleshooting Guide for
Issues in the (AP) Payments Workbench

Tip: Use templates created in the Templates tab of the Payments Manager to simplify pay
run processing.

Diagnostic: 1587455.1 R12: EBS Payments (IBY) Funds Disbursement Analyzer - Use to
prevent/troubleshoot Payment issues

7. Run a Payment Process Request at the month end (Optional)

By running a month end Payment Process request, you may create a payment for as many due invoices as
possible.

5 of 13 12/17/2019, 12:18 PM
Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

Document: 1305001.1 R12: Master Troubleshooting Guide for Payment Process Requests
(PPRs) in Oracle Payments

8. Confirm all Payment Instructions

Run the Payment Instruction Register for the period that is to be closed, or finalize any outstanding payments.
Use Oracle Payments to confirm any payment instructions. Check the status of the Payment Process
Request/Payments/Payment Instructions to ensure that all payments have been processed.

The Payment Instruction Register lists each payment created for a payment process profile or for a manual
payment. Actual payments can be compared against this register to verify that Oracle Payables/Oracle
Payments has recorded payments correctly. The report lists each payment in a payment process request,
including setup and overflow payment documents, in ascending order, by payment number. This report is
automatically submitted when payment instructions are being created and can also be submitted from the
standard report submission (SRS) screen.

Attention: Unconfirmed payments will prevent the period from closing.

Document: 1318577.1 R12: Comprehensive Listing of Errors and Solutions for Payables Payment
Reports

9. Reconcile Payments to Bank Statement Activity for the Period

Payables payments can be reconciled through the Cash Management application. See the Cash Management
tab in this Period Close Advisor as well as the document below.

Document: 1196096.1 Payables Info Center: Cash Management

10. Run the Payments Register (Optional)

The Payment Register details payments printed in a particular accounting period. This report can be used to
review payment activity for each bank account used during the specified time period.

Attention: The report total only shows the net (less discounts) payment amount, whereas the
Posted Payment Register total is the total payment amount, including discounts. If only verifying report
totals, these two reports would not balance. Therefore it is necessary to subtract the Discounts Taken
from the Posted Payment Register report total and then compare this calculated amount to the total
displayed on the Payments Register Report.

Document: 1318577.1 R12: Comprehensive Listing of Errors and Solutions for Payables Payment
Reports

11. Submit the Update Matured Bills Payables Status Process

This will process any future dated payments still to mature in the period.

6 of 13 12/17/2019, 12:18 PM
Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

Create Accounting

Subledger Accounting (SLA) & Create Accounting Process

In Release 12, Subledger Accounting (SLA) architecture was implemented, creating a common repository of
all your accounting information to maintain a common link between General Ledger (GL) balances and
underlying transactions automatically, for internal and external audit purposes, and for ease of drilldown.

Create Accounting is the new process in Release 12 that creates the accounting in the subledger accounting
tables and offers flexibility in how you generate your accounting. Accounting can be created immediately
online or run as a process and can be generated 3 different ways:

1. Draft: The transactions accounted in draft mode can be included on accounting reports but
cannot be transferred to the General Ledger. This mode is for informational purposes only
allowing you to review the accounting entries via the output report or using the Subledger
Accounting Inquiry screen prior to creating final entries.

2. Final: The transactions that have been accounted in Final Mode are accounted but not yet
transferred to General Ledger.When using Final mode, you have the option to transfer and post
to General Ledger based on the settings of the "Transfer to General Ledger" and "Post in GL"
parameters.

3. Final Post: Transactions that have been accounted in Final Post are transferred to and posted
in the General Ledger.

For more details on SLA and Create Accounting, see the following Document:

Document: 876190.1 R12: FAQ on Transfer to GL in R12

1. Run Create Accounting

The Create Accounting process creates the accounting in the subledger accounting tables. It can also transfer
and post that data to the General Ledger tables based on the parameters submitted. The "Transfer to General
Ledger" and "Post in GL" parameters which are set during Create Accounting determine whether that
accounting is transferred and posted to the General Ledger.

Attention: If Create Accounting is run without selecting Transfer to GL, you will have to
manually submit the Transfer Journal Entries to GL program. For more details, see
Document 459002.1.

Diagnostic: 1665706.1 R12: EBS Payables Create Accounting Analyzer - Diagnostic to

troubleshoot issues preventing accounting for invoices/checks

Document: 1330739.1 Payables Create Accounting Info Center: Create Accounting

Tip: Transactions that will be picked by Create Accounting can be health checked through
the month by periodically running the Master GDF Diagnostic from Document 1360390.1 in
date range chunks (e.g weekly). The program will scan transactions that will be processed in the

7 of 13 12/17/2019, 12:18 PM
Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

current month for potential data issues that may affect Create Accounting negatively. Address
issues as the MGD identifies them before running Create Accounting as most causes for failure
are data integrity related issues.

Tip: If you have foreign currency transactions, submit the “AutoRate” program in the
Submit Request window BEFORE running Create Accounting. “AutoRate” uses exchange rate
information in the GL Daily Rates table to enter exchange rates for any foreign currency invoices
or payments that have no exchange rates. “AutoRate” cannot update exchange rates unless you
have first defined exchange rates in the GL Daily Rates table that match the invoice or payment
currency, rate date, and rate type. For more details, see Document 834251.1.

Tip: For large companies, this process should be run and errors addressed daily.

2. Review the Transfer Journal Entries to GL

If Create Accounting was run with the Transfer to GL option, then this report will be generated as part of that
program and list details of the Payables journal entries created and any errors that may have occurred. If you
manually submit the Transfer to GL program, it will be generated from that process.

This report enables review and analysis of accounting entries in the Payables subledger, as accounted by
SLA. Using the report parameters, you can produce a detailed or summary listing of the accounting
information you want to review. This report is owned by SLA.

The report also lists, in detail, transactions that have been accounted with error and all entries that could not
be transferred to the General Ledger. When a transaction is accounted with errors, review the details and
make necessary changes. By altering the parameters, the report also lists those transactions which have been
posted in the General Ledger, and those which have not been posted but have been accounted.

SLA groups the report by ledger, ledger currency, source, category, and event class. Data is then sorted by
accounting date, event type, supplier name, document number, and voucher number.

Document: 1330739.1 Payables Create Accounting Info Center: Create Accounting

Tip: Promptly resolve any errors listed on this report promptly to avoid delay of period close.

3. Run and Review the Unaccounted Transactions Report

This report enables review of all unaccounted invoice and payment transactions and a view of the reason that
Payables cannot account for a transaction. Accounts Payable sorts the report by transaction type (invoice or
payment), exception, supplier, transaction currency, and transaction number.

Run this report after you have run the Create Accounting Process to show only the transactions that had
problems that prevented accounting. Correct the problems and resubmit the accounting process.

Document: 1330739.1 Payables Create Accounting Info Center: Create Accounting

Note: This report does not include invoices that have no distributions.

4. Transfer All accounted Invoices and Payments to the General Ledger

8 of 13 12/17/2019, 12:18 PM
Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

Release 12 provides 3 modes of accounting: Final, Final Post and Draft. The transactions that have been
accounted in Final Post have already been transferred to, and posted in the general ledger. The transactions
that have been accounted in the Final Mode are accounted but not yet transferred to General Ledger. The
transactions in draft accounting mode can be included on accounting reports but cannot be transferred to the
general ledger. The accounting in draft mode is for informational purposes only.

There are two ways to transfer journal entries to GL:

a) Submit Transfer Journal Entries to GL concurrent request. or

b) Choose to transfer the accounting created during Create Accounting by selecting Yes for Transfer to
GL parameter.

Attention: The Create Accounting process ran with the Transfer to GL parameter = Yes will only
transfer the accounting created by that run. The Transfer Journal Entries to GL program needs to be ran
separately to transfer any accounting that was created, but not transferred during previous runs of the
Create Accounting process or from Online Accounting that was not Final Post.

When accounting mode is Final and transfer to GL is set to No, then the Transfer Journal Entries to GL
program needs to be run from the Standard Report Submission (SRS) window. Please review the Transfer
Journal Entries to GL report generated by this program; make sure there are no errors reported on this report.

Invoice journal entries debit the expense or other account entered on an invoice distribution line, and credit
the liability account specified on the invoice, unless you have modified the SLA rules to create alternative
accounting entries to address your specific business needs.

Payment journal entries relieve liability on the invoice(s) that it pays and credit cash or cash clearing account
depending on your setup.

Attention: The generated journal batch needs to be posted from within Oracle General Ledger if
the mode of accounting was Final, Transfer to General Ledger was Yes and Post in GL was set to No.
The journal batch will be automatically posted in General Ledger if the mode of accounting was
FINAL and Post in GL was set to Yes.

Diagnostic: 878891.1 Oracle GL Transfer Diagnostics Test

5. Review the Transfer Journal Entries to GL Report generated from step 4

This report provides any errors that may have occurred during transfer of the journal entries.

Attention: Make sure there are no errors on this report before proceeding

Document: 459002.1 R12 Unable to Transfer Journal Entries to General Ledger

Document: 883557.1 Subledger Accounting: How To Avoid and Fix Corruption in Data Transfer
from SLA - Negative Ledger_ID, Not Reached GL, Duplicate in GL

Diagnostic: 1349298.1 AP and SLA Reconciliation Diagnostics Data Collection Test

6. Run the Posted Invoices Register

This report is used to review invoices for which information has been posted to Oracle General Ledger to

9 of 13 12/17/2019, 12:18 PM
Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

create journal entries, and can be used to verify that the total invoice amount equals the total invoice
distribution amount. The report lists each Accounts Payable Liability Accounting Flexfield and the invoices
posted to the account.

Document: 735520.1 R12 Payables Posted Invoice/Payment Register FAQs

7. Run the Posted Payments Register

This report is used to review the payments posted to Oracle General Ledger during a particular accounting
period, and can be used to review the payment activity for each bank account used during that period.

Attention: When posting to the General Ledger is performed multiple times throughout each
accounting period, the Posted Invoices Register and Posted Payments Register reports must be run after
each posting run, for reconciliation of Oracle Payables liabilities with Oracle General Ledger's Trade
Creditor Control Account.

Reconcile

Subledger Accounting (SLA) - Reconciliation

SLA introduced changes in the way reconciliation is performed:

In Release 11i, you reconciled transactions and distributions to GL through transactional reports. In the
accounting reports in Release 11i, the balances are displayed but not the transactional information.

In Release 12, there is no reason to reconcile distributions on transactions to GL, but you can still reconcile
transaction reports to accounting reports. The new accounting reports in Release 12 now also contain more
comprehensive information - not just on balances but also on suppliers, customers and transactions.

Note: When you do account balance reconciliation, you should ignore distributions in
Release 12, especially if you have altered your subledger accounting rules.

1. Run the Accounts Payable Trial Balance

The Accounts Payable Trial Balance should be used in conjunction with the Posted Invoice and Posted
Payment Registers for reconciliation. The correct method for reconciling AP to GL is as follows:

Last Months Accounts Payable Trial Balance

+ This months Payables Posted Invoice Register

- This months Payables Posted Payment Register

= This months Accounts Payable Trial Balance

10 of 13 12/17/2019, 12:18 PM
Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

Attention: The Accounts Payable Trial Balance report output shows a GL total. That GL total
includes manual and non Liability class entries from the Payables subledger, and non-Payables source
entries in GL. Use the given method to reconcile, and the Trial Balance amount remaining total should
equal the GL total excluding the manual and non Liability class entries from the Payables subledger,
and non-Payables source entries in GL.

Document: 553484.1 Troubleshooting Accounts Payable Trial Balance (Open Account AP

Balance Listing) issues in R12

Diagnostic: 1553507.1 R12: Payables Trial Balance Analyzer - Diagnostic to Validate Data for
APTB issues

Document: 1330739.1 Payables Create Accounting Info Center: Trial Balance

Diagnostic: 829180.1 Oracle Payables Trial Balance Diagnostics For An Invoice Activity Test

Note: To obtain the most up-to-date trial balance for a given period, journal entries should be
posted for the invoice and payment activity for the period, prior to running the report

Close Period

Closing the Period

When you attempt to update the period status to Closed for one ledger, the system checks for unposted
transactions in all operating units within the ledger. If there are unposted transactions in any of the operating
units, you will need to resolve the unposted transactions for those operating units before you can close the
period for that ledger. See the referenced documents and diagnostics within this advisor to troubleshoot these
types of issues.

Attention: Closing is always executed at a ledger level and not at operating unit. You can only
execute close from the responsibility which has access to all operating units within a ledger.

Note: In Release 11i, GL automatically created the balancing lines for journals posted to GL when
you closed your periods in each of the subledgers. In Release 12, subledger accounting creates the
balancing lines at the time you account for the subledger transactions. The subledger accounting
journal represents the actual accounting and the balancing lines are created as part of these subledger
accounting journals.

1. Close the Current Oracle Payables Period

Close the accounting period by using the Control Payables Periods window to set the Period Status to Closed.
If there are exceptions, there will be a message that the period cannot be closed and an Exceptions button will
be available. Click on this and then click on Review. This will submit the Payables Period Close Exceptions
Report which lists all the transactions, accounting events and headers that fail period close validation. If the

11 of 13 12/17/2019, 12:18 PM
Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

Period Close Exception report shows "Other Exceptions", no exceptions, or unable to resolve normal
exceptions by running standard programs, then, you can run the Period Close Analyzer(PCA) with Master
GDF (MGD) which will display the potential transactions stopping period closed and solutions to resolve it.

Tip: Transactions that appear on the Period Close Exception Report have often failed
accounting and validation because of data issues. Periodically running the Master GDF
Diagnostic from Document 1360390.1 will reduce or eliminate the number of these
transactions. If transactions still appear on this report, use the Master GDF Diagnostic to
validate them in 'Single Transaction mode.' If data issues are identified, address them as the
diagnostic indicates.

Tip: If any data issues were identified and resolved after running the Trial Balance during
the Reconcile phase, you will need to rebuild the Trial Balance Report so any transactions that
were fixed and posted to GL will be reflected in the correct accounts. See Document 553484.1
for instructions on how to rebuild the Trial Balance.

Document: 437422.1 R12 Troubleshooting Period Close in Payables

Diagnostic: 1360390.1 R12: Master GDF Diagnostic (MGD) to Validate Data Related to
Invoices, Payments, Accounting, Suppliers and EBTax

Diagnostic: 1489381.1 R12: Payables Period Close Analyzer

2. Submit the Unaccounted Transactions Sweep Program

If any transactions remain that cannot be accounted successfully, are not material, and your accounting
process allows it, use the Sweep Program. This program transfers unaccounted transactions to the next open
period so you can close the current period. Sweeping changes the accounting date on unaccounted
transactions to the first day of the next open period. This should only be done after due diligence to resolve
unaccounted transactions is completed by going through the steps and troubleshooting notes in the Process
Transactions section.

To submit the Unaccounted Transactions Sweep Program, navigate to the Control Payables Periods window.
If the period has exceptions, then the Exceptions button will be visible. Click on that button and choose
Review to submit the Unaccounted Transactions Sweep report. This will list the transaction that will be
swept. After review, if you want to sweep, set the period status to Closed and choose the Sweep button to
move the unaccounted transactions to the next period.

Attention: Sweep cannot be undone!

Attention: Swept transactions are not posted to General Ledger, the GL dates are changed to the
first day of the next open period so they can be accounted, transferred and posted in that next open
period. Promptly resolve issues with swept transactions to keep your accounting current.

Attention: There are certain types of issues that the Sweep will not move to the next period and
must be resolved prior to saving in a Closed status. Please refer to: Release 12 Oracle® Payables
Implementation Guide "Closing an Accounting Period".

Document: 560378.1 Unaccounted Transactions Sweep Program

12 of 13 12/17/2019, 12:18 PM
Note: 335.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=30...

Note: Before running the sweep program, you will need to open the next accounting period, see
step 5 below.

3. Accrue Uninvoiced Receipts

Refer to the Purchasing tab in this Period Close Advisor as well as the document below.

Document: 1350498.1 Oracle Purchasing: Accounting Information Center

4. Run Mass Additions Transfer to Oracle Assets

After you have completed all Payables transaction entries, and confirmed all invoice holds, and carry
forwards, submit the Mass Additions Create program to transfer capital invoice line distributions from Oracle
Payables to Oracle Assets. For foreign currency assets, Payables sends the invoice distribution amount in the
converted functional currency. The mass addition line appears in Oracle Assets with the functional currency
amount. After you create mass additions, you can review them in the Prepare Mass Additions window in
Oracle Assets.

It is recommended to do a final Mass Additions Create after the period close to ensure that all Payables
invoices are included in the correct period. Any additional invoicing will become part of the next period.

Document: 567690.1 White Paper on Mass Additions Create Process in R12

Diagnostic: 1162973.1 Oracle Payables (SQLAP): Invoice Mass Additions Activity Diagnostic
Test

Tip: If the volume of transactions in Accounts Payable requiring Assets update is large, you should
consider running the Mass Additions Create process on a more regular basis.

5. Open the Next Oracle Payables Period

Open the next accounting period by using the Control Payables Periods window to set the Period Status to
Open.

13 of 13 12/17/2019, 12:18 PM