Cloud Support Dashboard Service Requests Knowledge ...docshare03.docshare.tips/files/24953/249532867.pdf · Entries You can use Oracle Subledger Accounting to view information on

12/8/2014 Knowledge

https://support.oracle.com/cloud/faces/DocumentDisplay?_afrLoop=174761004160205&_afrWindowMode=0&id=1375017.1&parent=DOCUMENT&sourceId=… 1/23

Knowledge

In this Document

PurposeTroubleshooting Steps

1. HOW DOES CREATE ACCOUNTING WORK? 1.1 Overview of Create Accounting Program 1.2 Creating Accounting Entries in Payables 1.3 Submitting the Create Accounting Program 1.4 Creating Accounting Entries from Transaction Windows 1.5 Adjusting Accounting Entries 1.6 Viewing Accounting Entries 1.7 Oracle Subledger Accounting Program Report 1.8 The Create Accounting Program Parameters

2. HOW DOES THE TRANSFER JOURNAL ENTRIES TO GL WORK? 2.1 Overview of Transfer Journal Entries to GL Program 2.2 Transfer Journal Entries to GL Program 2.3 Transfer Journal Entries to GL Report 2.4 Posting in Oracle General Ledger

3. WHAT ARE THE STEPS TO CLOSE THE PERIOD IN PAYABLES? 3.1 Invoices 3.2 Payment Batches 3.3 Future Dated Payments 3.4 Transactions 3.5 Transfer 3.6 Closing 3.7 Reconciliation 3.8 Purchasing 3.9 Assets 3.10 Reconcile to GL

4. HOW TO PROCESS THE PAYABLES RECONCILIATION? 4.1 Reconciling Payables Activity 4.2 Reconciling Accounts Payable Trial Balance for a given period 4.3 Reconciling Payables Activity to General Ledger

5. USING ORACLE SUBLEDGER ACCOUNTING PROGRAM REPORT TO CHECK EXCEPTIONS

R12: Master Troubleshooting Guide (MTG) for Accounting Issues in Oracle Payables (Doc ID 1375017.1) To Bottom

Modified: 04May2014 Type: TROUBLESHOOTING

Cloud Support

[email protected] to My Oracle Support

Dashboard Service Requests Knowledge Communities

12/8/2014 Knowledge


5. USING ORACLE SUBLEDGER ACCOUNTING PROGRAM REPORT TO CHECK EXCEPTIONS 5.1 Overview of the Subledger Accounting Program Report 5.2 Use the Error Message to Resolve the Issue

6. USING THE ACCOUNTING REPORTS TO CHECK EXCEPTIONS 6.1 Period Close Exceptions Report 6.2 Posted Invoice Register 6.3 Posted Payment Register 6.4 Unaccounted Transactions Report 6.5 Accounts Payable Trial Balance Report

7. RESOLVING ERRORS 7.1 Apply the Recommended patches Strongly Recommended Patches for Accounting Release 12.1 Release 12.0 Recommended patches 7.2 Searching in 'My Oracle Support' 7.3 Data Corruption issues The Use of GDF 7.4 Documents to Investigate and Resolve Errors

8. USING DIAGNOSTICS TO CHECK SETUP AND DATA a. R12.0.6+ : XLA Setup Diagnostics R12.0.6+ : Subledger Accounting (Subledger Accounting): XLA Setup Diagnostics Test Data Collection Test Note 942252.1 b. R12.0[34] : XLA Setup Diagnostics R12.0.[34] : Subledger Accounting (Subledger Accounting): XLA Setup Diagnostics Test Note 942262.1 c. R12.0.6+ : Oracle Payables Invoice Data Data Collection Test (Aplist) 12.0.6/12.1 Legacy: Oracle Payables (SQLAP): Invoice Data Data Collection Test Note 732163.1 d. R12.0.[34] : Oracle Payables Accounting Health Check Setup Test R12.0.[34] : Oracle Payables (SQLAP): Accounting Health Check Note 463727.1 e. R12.0.6+ : Oracle Payables Trial Balance Diagnostics For An Invoice Activity Test R12 Subledger Accounting (XLA): Trial Balance Diagnostics For An Invoice Activity Diagnostic Test Note 829180.1 f. Oracle Payables Trial Balance Diagnostics For An Invoice Details Test R12.0.[34] : Oracle Payables (SQLAP): Trial Balance Diagnostics For An Invoice Note 882682.1

9. SUBLEDGER ACCOUNTING SETUP IN PAYABLES Accounting Methods Builder (AMB) Overview Accounting Methods Builder Process 9.1 Define custom sources 9.2 Define journal line types 9.3 Define journal entry descriptions 9.4 Define mapping sets 9.5 Define account derivation rules 9.6 Define journal lines definitions 9.7 Define application accounting definitions 9.8 Define subledger accounting method 9.9 Assign each subledger method to a ledger using the Accounting Setup Manager.

https://support.oracle.com/cloud/faces/DocumentDisplay?parent=DOCUMENT&sourceId=1375017.1&id=463727.1






12/8/2014 Knowledge


10. THE PREDEFINED SETUP ELEMENTS FOR ORACLE SUBLEDGER ACCOUNTING INTERACTIVE DOCUMENTATION VIEWER: Predefined Elements for Payables Accounting

11. Still Have Questions? Modification HistoryReferences

APPLIES TO:

Oracle Payables Version 12.0.0 and laterInformation in this document applies to any platform.

PURPOSE

Oracle Payables (AP): Create Accounting Process > Generic Setup and Troubleshooting Resources > Note This note is intended to walk you through a set of sequential steps that will facilitate troubleshooting Create Accounting issues in Releases 12.0 through 12.1.

**NEW** The August 2014 RPC patches are now available.

Please see the following document for more information:

EBS: R12.1 Oracle Financials Recommended Patch Collection (RPC), Aug 2014 (Doc ID 954704.1),

** NEW ** NEW Troubleshooting Assistant

New R12: Troubleshooting Assistant for AP Accounting is now available Doc ID 1573154.2

** New Diagnostic Analyzers :

R12: Payables Trial Balance Analyzer Diagnostic to Validate Data for APTB issues Doc Id 1553507.1 Diagnostic to help with period close issues : Doc ID 1489381.1 R12: Period Close Analyzer Diagnostic to Validate Data BeforePeriod Close

** New Accounting Info Centers Check for useful and interesting updates :

Information Center: Oracle Payables Accounting R12 (Doc ID 1476284.2)

Information Center: Using Oracle Payables Accounting (Doc ID 1478842.2)

Information Center: Troubleshooting Oracle Payables Accounting ( Doc ID 1478863.2)

NEW !! To identify upgraded data issues please run Doc ID 1460241.1 R12: Upgrade GDF Diagnostic to Validate Data Related to Invoices,Payments, Accounting and Suppliers

How to Get the Most of This Document ?

1.

Apply the recommended patches discussed in Section #7.1

** New ** New Updated from Sep2013 : Sep2013 Recommended Patches for R12.1

These patches will prevent many known issues in your system.

2. Run carefully the steps to close the period described in

Section #3

.

It will solve basic issues.

3. For remaining errors:




http://support.oracle.com/rs?type=doc&id=954704.1#aref_section116






12/8/2014 Knowledge


3. For remaining errors:

Rerun the Create Accounting process, review the errors and try to solve using the error message. See Section #5.

Find the error message details then review Section #7.4 , try to find the document relevant to your issue and submit it. Use the diagnostics in Section #8 to investigate the invoice or payment.

4. For data corruption errors run the GDF diagnostics described in Section #7.3. Review the GDF diagnostics report then run the GDF script suggested in this report. It will solve the data corruption issues.

5. Do you expect to see further details in this document that will help you to quickly solve errors ? Kindly enter your recommendations and comments in the "Rate this Document" window opened from the right corner. Thank you!

TROUBLESHOOTING STEPS

1. HOW DOES CREATE ACCOUNTING WORK?

1.1 Overview of CreateAccounting Program

The Create Accounting program processes eligible accounting events to create subledger journal entries. To create the subledger journal entries, theCreate Accounting program applies application accounting definitions that are created in the Accounting Methods Builder (AMB).

The Create Accounting program:

Validates and creates subledger journal entriesGenerates the Subledger Accounting Program Report, which documents the results of the Create Accounting program.

1.2 Creating AccountingEntries in Payables

You can create accounting entries for Payables accounting events in two ways:

Submit the Create Accounting program.Create online accounting entries for a single transaction or batch.

In both cases, you can view the generated accounting entries in the following locations:

View Accounting and View Accounting Entries windows.Subledger Accounting Program Report. This report is automatically generated when you create accounting entries.

1.3 Submitting the CreateAccounting Program Use the Create Accounting program to create accounting entries for multiple transactions. You can also use this program to generate detailed error reports

if you could not successfully create accounting entries from the transaction windows.

Submit the Create Accounting program in Draft mode, if you want to view the accounting results before you create the final accounting, or Final mode.

1.4 Creating AccountingEntries from TransactionWindows

From a transaction window, you can create accounting entries for a selected invoice, payment, invoice batch, or payment batch. For a single invoice orpayment, the accounting completes online. For batches, the accounting process is submitted as a request, and you can view its completion status in theRequests window.

To create accounting entries for an invoice, payment, or payment batch:

1. Query and select the invoice, payment, or payment batch in the Invoices, Payments, or Payment Batches window. Choose the Actionsbutton.

2. The actions window for the transaction opens. Choose the Create Accounting check box.

Choose one of the following options:

DraftFinalFinal and Post

3. Choose OK.

To create accounting entries for an invoice batch:

1. In the Invoice Batches window, query the invoice batch.

12/8/2014 Knowledge


1. In the Invoice Batches window, query the invoice batch.

2. Choose the Create Accounting button.

1.5 Adjusting AccountingEntries

Accounting entries are automatically generated for transactions based on your accounting setup in Oracle Subledger Accounting and Oracle GeneralLedger.You can only adjust accounting entries in Payables if you ran the Create Accounting program in Draft mode. To adjust accounting entries, adjust the transaction details and rerun the Create Accounting program.

1.6 Viewing AccountingEntries You can use Oracle Subledger Accounting to view information on accounting events, journal entries, and journal entry lines.

You can perform the following subledger accounting inquiries:

View information about an accounting event or journal entry error.View detailed information about the subledger journal entry headers for an accounting event.Compare subledger journal entry information for any two journal entriesView subledger journal entry lines for multiple documents or transactionsView subledger journal entries in a taccount formatView transactions for an accounting event or journal entry

You can use the following reports to review accounting information:

Journal Entries reportAccount Analysis reportThird Party Balances reportMultiperiod Accounting reportsSubledger Period Close Exceptions reportsOpen Account Balances Listing

1.7 Oracle SubledgerAccounting Program Report

The Subledger Accounting Program Report is generated by the Create Accounting program. It lists the following:

Successful events and the subledger journal entries created for those eventsErrors for failed events

Users can run the report in summary or detail mode which are described as follows:

Summary mode provides a summary of events processed and detailed information about their errors.Detail mode provides details of subledger journal entries generated from the processing of completed events and a detailed error report.

Back to Top

1.8 The Create Accounting Program Parameters

The Create Accounting program creates and transfers journal entries. In general, the parameters described in the table below determine which accounting events areprocessed.

12/8/2014 Knowledge


Parameter DescriptionLedger Required. Limits accounting events selected for processing to those of a particular ledger.

Subledger Accounting lists ledgers that have events that the responsibility can access due to transactionbased security. If the profile option SLA: Enable Data Access Security in Subledgers is set to Yes, only those ledgers that are included in General Ledger Access Sets assigned to theresponsibility appear in the list of values.

If the application is a valuation method application as defined in the AMB, then both primary and secondary ledgers within the access sets are displayed. If the application is not a valuation method application, then only primary ledgers are displayed.

Process Category Optional. Restricts the events selected for accounting to a particular process category.

The Create Accounting program selects events with event types falling into the event classes assigned to the process category.Only process categories established by development teams as part of the seed data are included in the list of values.

End Date Required. End date for the Create Accounting program; processes only those events with event dates on or before the end dateMode Required. Determines whether the subledger journal entries are created in Draft or Final mode.

If Draft mode is selected, then the Transfer to GL, Post in General Ledger, and General Ledger Batch Name fields are disabled. Draft entries cannot be transferred toGeneral Ledger.

Errors Only Required. Limits the creation of accounting to those events for which accounting has previously failed.If Yes is selected, the Create Accounting program processes all events with a status of Error.

Report Required. Determines whether to generate a report showing the results of the Subledger Accounting program in summary or detail format.Transfer to GeneralLedger

Required if Mode is set to Final. Determines whether to transfer the subledger journal entries to General Ledger.Journal import is not launched if the profile option SLA: Disable Journal Import is set to Yes.

Post in GeneralLedger

Required if Mode is set to Final or Create Accounting is set to No. Determines whether to post subledger journal entries in General Ledger.

If there is a primary ledger with secondary ledgers attached to it and the application is a nonvaluation method application, the journal entries of the secondary ledgers areautomatically posted. This is based on the application accounting definition that the user sets up.

If the application is a valuation method application, then there is a different event for that secondary ledger and the accounting is not created in the same run for bothledgers.

General Ledger BatchName

Optional. Userentered batch name that appears on the transferred General Ledger subledger journal entries. Transfer to GL option must be set to Yes.

Include UserTransaction Identifiers

Required. Controls whether the report displays user identifiers' names and values.

Back to Top

2. HOW DOES THE TRANSFER JOURNAL ENTRIES TO GL WORK?

2.1 Overview ofTransfer JournalEntries to GL Program

The Transfer Journal Entries to GL program enables you to transfer any eligible journal entries to General Ledger, including those from previous batch runs thathave not yet been transferred to General Ledger.If you already created accounting in Final Mode but have not transferred them over to GL, and you run the Create Accounting program with Transfer to GL option,then the application does not pick up events that are already created in the final mode. You run the Transfer Journal Entries to General Ledger program to do that.

After you create accounting entries, transfer those entries to General Ledger. You can transfer accounting entries in the following ways:

If you create accounting entries from the transaction window, select the Create and Post option. This automatically creates accounting entries, transfersthe entries to General Ledger, and posts them.

If you run the Create Accounting program, set the Transfer to General Ledger parameter to Yes. This creates the accounting entries and transfers them tothe General Ledger. If you selected Yes for the option to Post the entries, the entries are transferred and posted. Otherwise, after the entries aretransferred to General Ledger, you can review and post them manually.

Run the Transfer Journal Entries to General Ledger program. This program transfers journal entries from Oracle Subledger Accounting to the GeneralLedger.

12/8/2014 Knowledge


You can then post these journal entry batches, headers, and lines within General Ledger to update your General Ledger account balances.

If you do not use General Ledger, you can use the data in the GL_INTERFACE to create and post journal entries in your general ledger.You can view the accounting entries in Payables. Also, after you post journal entries in Oracle General Ledger, you can drill down to the related accountingentries or transactions in Payables.

2.2 Transfer JournalEntries to GL Program

The Transfer Journal Entries to GL program consists of a subset of parameters used in the Create Accounting program as listed below:

LedgerProcess CategoryEnd DatePost in General LedgerGeneral Ledger Batch Name

2.3 Transfer JournalEntries to GL Report

The Transfer to Journal Entries to GL Report is generated by the Transfer Journal Entries to GL program and lists the following:

Transfer to GL SummaryGeneral Errors

2.4 Posting in OracleGeneral Ledger

After you submit Journal Import, you can post journal entries in Oracle General Ledger. You can post journal entries in Summary or Detail.

Back to Top

3. WHAT ARE THE STEPS TO CLOSE THE PERIOD IN PAYABLES?

You close a Payables period after you have completed accounting for transactions for the period and you have transferred the accounting entries to general ledger.You cannot close a period in Payables if any of the following conditions exist:

Outstanding payment batches. Confirm or cancel all incomplete payment batches. Future dated payments for which the Maturity Date is within the period but that still have a status of Issued.Submit the Update Matured Future Payment Status Program.Unaccounted transactions. Submit the Create Accounting program to account for transactions, or submit the Unaccounted Transaction Sweep to move anyremainingunaccounted transactions from one period to another.Accounted transactions that have not been transferred to general ledger. Transferaccounting entries to General Ledger.

To complete the close process in Payables:

Period Close Step Period Close Step Description

3.1 Invoices Validate all invoices.

3.2 Payment Batches Confirm or cancel all incomplete payment batches.

3.3 Future DatedPayments

If you use future dated payments, submit the Update Matured Future Dated Payment Status Program. This will update the status of matured future dated payments to Negotiable so you can account for them.

3.4 Transactions Resolve all unaccounted transactions.

Submit the Create Accounting program to account for all unaccounted transactions. Review the Unaccounted Transactions Report. Review any unaccounted transactions and correct dataas necessary. Then resubmit the Create Accounting program to account for transactions you corrected. Or move any unresolved accounting transaction exceptions to another period (optional). Submit the Unaccounted Transactions Sweep Program

3.5 Transfer Transfer invoices and payments to the General Ledger and resolve any problems you see on the outputreport.

3.6 Closing In the Control Payables Periods window, close the period in Payables.

3.7 Reconciliation Reconcile Payables activity for the period. You will need the following reports:

12/8/2014 Knowledge


Accounts Payable Trial Balance Report Posted Invoice Register Posted Payment Register

3.8 Purchasing If you use Oracle Purchasing, accrue uninvoiced receipts

3.9 Assets If you use Oracle Assets, run the Mass Additions Create Program transfer capital invoice line distributions from Oracle Payables to Oracle Assets

3.10 Reconcile to GL Post journal entries to the general ledger and reconcile the trial balance to the General Ledger.

Back to Top

4. HOW TO PROCESS THE PAYABLES RECONCILIATION?

4.1 Reconciling PayablesActivity

Use the following reports to reconcile your posted invoices and payments to your Accounts Payable Trial Balance to ensure that your Trial Balanceaccurately reflects your accounts payable liability:

Posted Invoice RegisterPosted Payment RegisterAccounts Payable Trial Balance (last period and current period)

Note: Before you run your reports, transfer the journal entries to General Ledger for all transactions in the period that you are reconciling.

Note: When reviewing your Accounts Payable Trial Balance report, you may notice that the remaining amount for a given invoice is less than youexpect or even negative. This may be caused by recording invoice payments in a GL period that precedes the GL period used to record some or all of your invoice distributions.

For example: You enter an invoice with one distribution of $200 that uses a GL date of 04JAN2011. You pay the full invoice, and thepayment date is 20DEC2010. If you submit the Accounts Payable Trial Balance report as of 31DEC2010, then the invoice will correctlyshow an amount remaining of <$200>.

In the reports parameter, if you do not enter an as of date, then the report shows all paid and unpaid invoices from the start date.

Payables allows the payment date to precede the invoice GL date to support certain accounting methods (e.g. recording prepaid items).

4.2 Reconciling AccountsPayable Trial Balance for agiven period

Add the current period's posted invoices (total invoice amount from the Posted Invoice Register) and subtract the current period's posted payments(total cash plus discounts taken from the Posted Payments Register) from the prior period's Accounts Payable Trial Balance.This amount should equal the balance for the current period's Accounts Payable Trial Balance.

For example, you are closing your accounting period for April and you have just posted your final invoice and payment batches to your general ledgersystem.To reconcile your accounts payable activity for April, make the following calculation:

March Accounts Payable Trial Balance

+ April Posted Invoice Register

April Posted Payment Register

= April Accounts Payable Trial Balance

4.3 Reconciling PayablesActivity to General Ledger

Use the Accounts Payable Trial Balance report to reconcile your accounts payable liability in your general ledger. Compare the Accounts Payable Trial Balance to the accounts payable balance in your general ledger system for a given period.

Because the Trial Balance presents the outstanding accounts payable liability information, it is only valid for an accrual ledger.

Back to Top

5. USING ORACLE SUBLEDGER ACCOUNTING PROGRAM REPORT TO CHECK EXCEPTIONS

5.1 Overview of the Subledger Accounting Program Report

12/8/2014 Knowledge


6.1 Period CloseExceptionsReport

Submit this report to review a complete list of exceptions that are preventing you from closing a Payables accounting period. This report lists, for each organization within the ledger, the following exceptions:

Outstanding Payment BatchesAccounting Entries not Transferred to General LedgerBills Payable Requiring Maturity Event and AccountingUnaccounted Invoices

The Subledger Accounting Program Report is generated by the Create Accounting program. It lists the following

Successful events and the subledger journal entries created for those eventsErrors for failed events

Users can run the report in summary or detail mode which are described as follows:

Summary mode provides a summary of events processed and detailed information about their errors.

Detail mode provides details of subledger journal entries generated from the processing of completed events and a detailed error report.

5.2 Use the Error Message to Resolve the Issue

Review the detailed error description and try to resolve.For remaining issues search in "My Oracle Support" with the error number then review selected solution documents.

Back to Top

6. USING THE ACCOUNTING REPORTS TO CHECK EXCEPTIONS

12/8/2014 Knowledge

https://support.oracle.com/cloud/faces/DocumentDisplay?_afrLoop=174761004160205&_afrWindowMode=0&id=1375017.1&parent=DOCUMENT&sourceId… 10/23

Unaccounted InvoicesUnaccounted Payments

To submit the Period Close Exceptions Report:

1. In the Control Payables Periods window if you try to close a period that has exceptions, the period status cannot be changed. Payables displays a message telling you this, and enables the Exceptions button.

2. Choose the Exceptions button in the Control Payables Periods window.Payables opens a message window. From the window you can choose the following buttons:

Review Sweep (unaccounted transactions to the next period)

3. Choose the Review button to submit the report. You can access the report output in the Requests window.

6.2 PostedInvoice Register

Use the Posted Invoice Register to review accounting lines for invoices that have been transferred and posted to your generalledger. Because it presents amounts that havebeen charged to liability accounts, this report is valid only for an accrual ledger.

The Posted Invoice Register is primarily a reconciliation tool. Use this report along with the Posted Payment Register and theAccounts Payable Trial Balance Report to reconcile balances between Payables and your general ledger.

To make their output easier to read, each of these reports can be generated for a single liability account. For example, if you are using Automatic Offsets and the liability for your invoices is allocated across multiple balancingsegments, then you can use the Liability Account parameter to limit your reports to a single balancing organization.

You can generate the report in summary or in detail. When generated in detail, the report displays invoices charged to liabilityaccounts and the accounting informationthat has been transferred to the general ledger. Also included is the supplier and amount information for each invoice listed.Payables displays the total invoice amountin the invoice currency, and the transferred distribution amount in both the invoice currency and accounted currency for easierreconciliation with your general ledger.

Note: The posted distribution amount only includes distribution lines that have been transferred to general ledger.

When generated in summary, the report lists totals for each liability account and does not include any invoice detail.The report always sorts first by liability account. If the report is submitted in detail, it then sorts in the following order:

The report sorts using the Order By parameter, either Journal Entry Batch or Entered Currency. The default value isEntered Currency, and you can change theparameter value only if the report includes journal entry batch names (the Include Journal Entry Batch parameter isYes)The report then sorts by supplier name, invoice number, and invoice date.

6.3 PostedPaymentRegister

Use the Posted Payment Register to review accounting lines for payments that have been transferred and posted to generalledger. Because it presents amounts that havebeen charged to liability accounts, this report is valid only for an accrual ledger. You can submit the Posted Payment Registerfor one payment journal entry batch or allpayment journal entry batches.

The Posted Payment Register is primarily a reconciliation tool. Use this report along with the Posted Invoice Register and theAccounts Payable Trial Balance Report toreconcile balances between Payables and your general ledger. To make the output easier to read, each of these reports canbe generated for a single liability account.

For example, if you are using Automatic Offsets and the liability for your invoices is allocated across multiple balancingsegments, then you can use the Liability Accountparameter to limit your reports to a single balancing organization.

You can generate the report in summary or in detail. When generated in detail, the report displays payments that relieveliability accounts and that have had their accounting information transferred to the general ledger. Also included is the supplierand amount information for each payment listed. Payables displays the payment amount in the entered currency and the liability amount relieved in the accounted currency. In detail mode, the report also displays the payment document and disbursement type for each batch of payments. It providesa report total and subtotals for each payment document and bank account.

When generated in summary, the report lists totals for each liability account and does not include any payment detail.The report always sorts first by liability account. If the report is submitted in detail, it then sorts in the following order

The report sorts using the Order By parameter, either Journal Entry Batch or Bank Account. The default value is BankAccount, and you can change the parametervalue to Journal Entry Batch only if the report includes journal entry batch names (the Include Journal Entry Batchparameter is Yes).The report then sorts by payment number, payment date, and supplier name.

6.4 UnaccountedTransactionsReport

Use this report to identify and review all unaccounted invoice and payment transactions and see the reason that Payablescannot account for a transaction.Payables sorts the report by transaction type (invoice or payment), exception, supplier,transaction currency, and transactionnumber.

Run this report after you create accounting entries. The report will then show only transactions that had problems thatprevented accounting. You can then correct theproblems and resubmit the accounting process. Note that this report does not include invoices that have no distributions.

Prerequisites

(Recommended) Validate invoices to reduce the number of unvalidated invoices on the report.(Recommended) If you use bills payable (future dated payments), submit the Update Matured Future Payment StatusProgram to update the status of any futuredated payments with a maturity date on or before today's date.(Recommended) Create accounting entries.

Exception. The report displays one or more of the following exception conditions for invoices and/or payments:

12/8/2014 Knowledge


Dist Acct Invalid. The account on the invoice distribution is invalid.Dist Variance. The sum of the invoice distributions is not equal to the invoice amount.Funds Check. You are using budgetary control and Payables cannot check funds for an invoice.Insufficient Funds. You are using budgetary control and you have insufficient funds available in your budget for aninvoice.No Rate. You have not entered an exchange rate for a foreign currency transaction.Unaccounted. The Create Accounting process has not been submitted for the transaction.Other Hold Names. This invoice has a hold applied to it that prevents accounting.You define holds using the Invoice Holds and Release Names window.Unvalidated. You have not submitted Invoice Validation for the invoice.Withholding Tax. The invoice distribution has a withholding tax group assigned to it. Payables could not withhold taxand applied a Withholding Tax hold on this invoice. Several conditions cause this hold including: the withholding tax group is inactive, a Withholding Tax type tax codewithin a withholding tax group is inactive, an account segment assigned to a Withholding Tax type tax code is invalid, a rate has not been defined for aWithholding Tax type tax code, a period has not been defined for a Withholding Tax type tax code, or a tax rate for aWithholding Tax type tax code has been defined using an invalid date range.

6.5 AccountsPayable TrialBalance Report

Use the Accounts Payable Trial Balance Report to verify that total accounts payable liabilities in Payables equal those in thegeneral ledger.

To reconcile these balances you can compare the cumulative total liability provided by this report with the total liabilityprovided by your general ledger.

The Accounts Payable Trial Balance report is a Payablesspecific version of the Open Account Balances Listing report. By running this report from Payables, you can run this report for a specific operating unit. The Open Account Balances Listing identifies General Ledger accounts with outstanding balances and displays the subledgertransactions that contribute to that balance. Users can create their own layout and publish their reports using Oracle XML Publisher.

For more details about the Trial Balance report please review Doc ID 1372288.1 R12: Master Troubleshooting Guide for theAccounts Payable Trial Balance report

Back to Top

7.RESOLVING ERRORS

7.1 Apply the Recommended patches

Many of the accounting errors been resolved with high patches. The recommended patches include solutions to the issue described in their abstracts and also prior solutions entered earlier to the patch files.Make sure the Accounting recommended patches already applied in your system! You may also review Note 954704.1 EBS: R12.1 Oracle FinancialsRecommended Patches

Strongly Recommended Patches for Accounting

Release 12.1

**New**New**

The following Sept 2013 RPC for AP, IBY and ZX are released:

Apply the RPC patches to solve known issues in the following products:

Patch 17176017:R12.AP.B R12.1: Payables Recommended Patch (Core AP) Collection (AP RPC), Sep2013 Doc Id 1397581.1

Patch 17167654:R12.IBY.B R12.1: Payments Recommended PatchCollection (IBY RPC), Sep 2013 Doc Id 1481221.1

Patch 17176034:R12.AP.B R12.1: Payables Recommended Patch Collection (ISP)(AP RPC), Sep 2013 Doc Id 1397581.1

Patch 17176060:R12.AP.B R12.1: Payables Recommended Patch Collection(WF/PCARD) (AP RPC), Sep 2013 Doc Id 1397581.1

Patch 17202262:R12.ZX.B R12.1: EBusiness Tax Recommended Patch Collection(ZX RPC), Sep 2013 Doc Id 1481235.1

March2013 RPC Recommended Patch Collection are now released Patch 16213642:R12.AP.B (AP Core) Details in Note 1397581.1Patch 16060007:R12.XLA.B (SLA) Details in Note1481222.1Patch 16213660:R12.AP.B (AP WF/PCARD) Note 1397581.1 Patch 16213657:R12.AP.B (AP ISP) Note 1397581.1











12/8/2014 Knowledge


Patch 16213660:R12.AP.B (AP WF/PCARD) Note 1397581.1 Patch 16213657:R12.AP.B (AP ISP) Note 1397581.1

Patch 16009960:R12.ZX.B (EBTax) Note 1481235.1 Patch 16234880:R12.OIE.B (Internet Expenses) New Note 1534509.1 Patch 16242196:R12.CE.B (Cash Manegament) Note 1367845.1 Patch 16052604:R12.IBY.B (IBY) Note 1481221.1

For details on RPC for all financial products please refer to Financial Master Note 954704.1

Applying these patches will prevent many of the known data corruption issue

Release 12.0 Recommended patches

R12.0

Update from 30Apr2012 Additional new Accounting Recommended Patches:

Patch 12710754:R12.XLA.A



You may also review Doc ID 557869 BS: R12.0 ORACLE FINANCIALS CRITICAL AND RECOMMENDED PATCHES

Patch Abstract DateRecommended

<Patch 12622734>:R12.AP.A PAYMENT PROCESS VALIDATIONS IMPROVEMENTS 28Nov2011

<Patch 13040251>:R12.AP.A Performance issue in upgrade accounting 15Nov2011

<Patch 8613357>:R12.AP.A 1OFF:8549479:12.0.6:DATA FIX FOR TAX TOLERANCE UPGRADE 18Oct2011

<Patch 11071399>:R12.AP.A RCA UPGRADED PAYMENT XDL HAS INCORRECT APPLIED TO COLUMS 18Oct2011

<Patch 9586498>:R12.AP.A RCA: UPGRADE SCRIPT DOES NOT UPDATE THE BATCHES CORRECTLY 18Oct2011

<Patch 12344218>:R12.AP.A Invoice lines upgrade (APLNUPGB.PLS) taking longer time to complete 18Oct2011

<Patch 12990345>:R12.AP.A Invoice lines upgrade (APLNUPGB.PLS) taking longer time to complete 18Oct2011

<Patch 7535635>:R12.AP.A SEED DATA CHANGE REQUEST FOR AP_SUPPLIERS TABLE 18Oct2011

7.2 Searching in 'My Oracle Support'

Search in "My Oracle Support" with the error number or issue description. Refine the search term with expressions unique to your issue.

Webcast Review the following Webcast for more details about how to improve your searching in the knowledge Base

Searching in My Oracle Support Best practices for Best Results

Back to Top

7.3 Data Corruption issues The Use of GDF

https://updates.oracle.com/ARULink/PatchDetails/process_form?patch_num=13811614:R12.XLA.A





https://support.oracle.com/cloud/faces/INLINE_NOTE:740964.1







12/8/2014 Knowledge


Around 60% of the data corruption issues been resolved with available GDF patches.

Study about GDF with the document: What is a Generic Datafix Patch (GDF) and what GDFs are available for Payables? (Doc ID 874903.1)

How to use GDF ?

1. Review and run the script from Doc ID 1360390.1 R12: Diagnostic Script to Validate Data Related to Invoice and Payment Transactions The script will identify when available GDF's are needed: for Accounting, Invoices and Payments issues. Or for Supplier issues.

2. You can run this script for specific invoice, Payment or supplier or for all transactions within a date range.

3. You may quickly register the script as a concurrent program so that you can schedule it as part of your regular maintenance tasks. For more details please review Doc ID 1361255.1 How to Register the AP Data Validation Script as a Concurrent Program.

4. NEW !! To identify upgraded data issues please run Doc ID 1460241.1 R12: Upgrade GDF Diagnostic to Validate Data Related to Invoices, Payments, Accounting andSuppliers

5. Review the output reports and submit the GDF's scripts identified by the diagnostics. Review the GDFs patches ReadMe files.

6. Every GDF delivers 2 scripts

ap_xxxxxxxxxxxx_sel.sql The Select script is used to find and report the problem data. The script create a temporary table with the affected transactions and create a report which shows affected transactions.

ap_xxxxxxxxxxxx_fix.sql The Fix script used to fix the problem data.

7. Check the Select script report to identify and review the affected transactions.

8. Update process_flag in the temporary table to 'N' for transactions that should not be operated on.

9. If the identified events have to be corrected, then execute the Fix script.

10. Check the results.

11. Apply the RCA patch to prevent issue in future.

7.4 Documents to Investigate and Resolve Errors

Many of the issues described in Service Requests have solution documents in the system. Review the following documents to try and find a solution to your issue.

Document When to use

** NEW ** New Accounting Info Centers :Information Center: Oracle Payables Accounting R12 (Doc ID 1476284.2) Information Center: Using Oracle Payables Accounting (Doc ID 1478842.2) Information Center: Troubleshooting Oracle Payables Accounting ( Doc ID 1478863.2)

Oracle Payables (AP): Create Accounting Information Center (Doc ID 1330739.1)

For assistance in every issue related to Accounting: Accounting errors, Period close issues, Transfer issue , TB Report , Performance, Reconciliation and Budget.

Troubleshooting Create Accounting Master Note for Oracle Payables Release 12 (Doc ID 1313324.1) Create Accounting issue

R12 Troubleshooting Accounting Errors (Doc ID 1112504.1) Accounting errors

How to troubleshoot the R12 Create Accounting process (Doc ID 551504.1) Create Accounting issue R12 Troubleshooting Accounting Issues (Doc ID 732928.1) Accounting errors

R12: Consolidated Note for Create Accounting Error: ORA01403, XLA_AP_ACCT_HOOKS_PKG.MAIN (Doc ID 1311364.1)

Error: ORA01403

R12: Consolidated Note for Create Accounting Error "This line cannot be accounted until the accounting event for the application Payables that it references has been fully accounted." (Doc ID 1312852.1)

Error: "This line cannot be accounted..."

R12: Consolidated Note For Create Accounting Error 95353 Subledger Accounting was Unable to Derive an Accounting Code Combination Using the Account Derivation Rule (Doc ID 1305187.1)

Error: 95353

R12: Consolidated Note for Create Accounting Error 95340: The Total Debits And The Total Credits Do Not Balance (Doc ID 1309860.1)

Error: 95340

R12 Troubleshooting Period Close in Payables (Doc ID 437422.1) Issue with Period Close process

R12: PeriodEnd Procedures for Oracle Financials EBusiness Suite (Doc ID 961285.1) Issue with Period Close




















12/8/2014 Knowledge


Troubleshooting Accounts Payable Trial Balance (Open Account AP Balance Listing) issues in R12 (Doc ID 553484.1)

Issue with Trial Balance report

What is a Generic Datafix Patch (GDF) and what GDFs are available for Payables? (Doc ID 874903.1) Data corruption issue

R12: Frequently Asked Questions (FAQ) on the Oracle Payables Generic Data Fixes (GDF's) Available [VIDEO] (Doc ID 1327956.1)

Data corruption issue

R12: FAQ on Transfer to GL in R12 (Doc ID 876190.1) Issue with GL Transfer process

R12 Unable to Transfer Journal Entries to General Ledger (Doc ID 459002.1) Issue with GL Transfer process

How to Use and Troubleshoot the Financial Tax Register in Release 12 EBusiness Tax (Doc ID 1073468.1) Issue with the Financial Tax Register

R12: Payables Invoices Search Helper (Guided Resolution) (Doc ID 1345557.1) Issue with Invoices

Payables Invoice Info Center (Doc ID 1321090.1) Issue with Invoices

R12: Master Troubleshooting Guide for Issues in the (AP) Payments Workbench (Doc ID 1320497.1) Issue with Payments

R12: Comprehensive Listing of Errors and Solutions for Payables Payment Reports (Doc ID 1318577.1) Issue with Payments

R12 Payables Posted Invoice/Payment Register FAQs (Doc ID 735520.1) Issue with posted Invoices/Payments

EBusiness Suite: Oracle Payables Information Center (Doc ID 1196096.1) Issue in Payables

Create Accounting Accounting Program Performance Issue (Doc ID 1098185.1) Performance issue

Create Accounting Performance Issue (xla_accounting_pkg.unit_processor_batch) (Doc ID 1136906.1) Performance issue

R12 XLAACCPB Create Accounting "Hash Unique" Performance Issue (Doc ID 869323.1) Performance issue

EBS: R12.0 ORACLE FINANCIALS CRITICAL AND RECOMMENDED PATCHES (Doc ID 557869.1) Recommended Patches

Back to Top

8. USING DIAGNOSTICS TO CHECK SETUP AND DATA

a. R12.0.6+ : XLA Setup Diagnostics

R12.0.6+ : Subledger Accounting (Subledger Accounting): XLA Setup Diagnostics Test Data Collection Test Note 942252.1

Diagnostics Description Usage Instructions Layout ContainsR12.0.6 Apply patch8722364:R12.XLA.A. R12.1.1 8761390:R12.XLA.B .

This test provides all the relevantsetup for an event class.

Show the relevant setup for an eventclass

No validation will be done on the datacollected, therefore no error or warningmessages will be provided.

EBS Applicable Releases: 12.0.6 12.1.xApplication Name: SubledgerAccountingTest Group: Setup DiagnosticsTest Name: XLA Setup DiagnosticsTestImportant: R12.0.6 Apply patch8722364:R12.XLA.A. R12.1.1 8761390:R12.XLA.B .

To execute the test, do thefollowing:

1. Start Oracle EBusiness Suite2. Connect to responsibilityApplication Diagnostics3. Select the Diagnose menu option4. Click button Select Applicationand select Application "SubledgerAccounting"5. Scroll down to group "SetupDiagnostics"6. Select test name "XLA SetupDiagnostics Test"7. Input Parameters (* required) Responsibility Id (LOV) * Ledger Id (LOV) * Application Id (LOV) * Event Class (LOV)

InstallationLedger DetailsLegal Entity InformationSubledger OptionsSubledger Accounting Methodsand AADSubledger DetailsAll available Entity Types forthis ApplicationEntity Mapping for all Entitiesbelonging to this ApplicationEvent ClassesPredecessors for the EventClassEvent TypesTransaction Identifiers andReporting ViewEvent Class OptionsJournal Line DefinitionsAssigned to the AccountingDefinitionJournal Line Types Assigned toEach Event ClassJournal Line Type ConditionsAccount Derivation Rules


















12/8/2014 Knowledge


Account Derivation RulesAssociated to the Journal LineDefinitionsAccount Derivation RuleConditions

b. R12.0[34] : XLA Setup Diagnostics

R12.0.[34] : Subledger Accounting (Subledger Accounting): XLA Setup Diagnostics Test Note 942262.1

Diagnostics Description Usage Instructions Output ContainsR12.0.6 Apply patch8722364:R12.XLA.A. R12.1.1 8761390:R12.XLA.B

This test provides all the relevantsetup for an event class.

Show the relevant setup for an eventclass


EBS Applicable Releases: 12.0,12.0.1, 12.0.2, 12.0.3,12.0.4Application Name: SubledgerAccountingTest Group: Setup DiagnosticsTest Name: XLA Setup DiagnosticsTestImportant: R12.0.6 Apply patch8722364:R12.XLA.A. R12.1.1 8761390:R12.XLA.B


1. Login to Oracle EBusiness Suite2. Select the responsibility "OracleDiagnostics Tool" (see Note358831.1 for details)3. Select application "SubledgerAccounting" from the "Application"list of values4. Click the "Advanced" tab5. Scroll down to group "SetupDiagnostics"6. Select test name "XLA SetupDiagnostics Test"7. Input Parameters (* required) Responsibility Id (LOV) * Ledger Id (LOV) * Application Id (LOV) * Event Class (LOV)

InstallationLedger DetailsLegal Entity InformationSubledger OptionsSubledger Accounting Methodsand AADSubledger DetailsAll available Entity Types forthis ApplicationEntity Mapping for all Entitiesbelonging to this ApplicationEvent ClassesPredecessors for the EventClassEvent TypesTransaction Identifiers andReporting ViewEvent Class OptionsJournal Line DefinitionsAssigned to the AccountingDefinitionJournal Line Types Assigned toEach Event ClassJournal Line Type ConditionsAccount Derivation RulesAssociated to the Journal LineDefinitionsAccount Derivation RuleConditions

c. R12.0.6+ : Oracle Payables Invoice Data Data Collection Test (Aplist)

12.0.6/12.1 Legacy: Oracle Payables (SQLAP): Invoice Data Data Collection Test Note 732163.1

Diagnostics Description Usage Instructions Layout ContainsThis diagnostic test will display all ofthe data for all of the tables used toprocess an invoice in Payables.

This test is applicable for all Payablesinvoice and payment issues.


EBS Applicable Releases: 12.0.6 12.1.xApplication Name: Oracle PayablesTest Group: InvoiceTest Name: Invoice Data


1. Start Oracle EBusiness Suite2. Connect to responsibilityApplication Diagnostics3. Select the Diagnose menu option4. Click button Select Applicationand select Application "OraclePayables"5. Scroll down to group "Invoice"6. Select test name "Invoice Data"7. Input Parameters (* required) Responsibility Id (LOV) * Search Criteria (LOV) Supplier Name (LOV) Invoice Id (LOV) * Include GL Tables (Yes or No)(LOV) Include Related Data (Yes or No)(LOV) Max Rows Displayed

Ledger DefinitionSecondary LedgersSetupSummaryTrial BalanceInvoicePaymentTaxAccounting11.5 AX Accounting ( if exists )11.5 AP Accounting ( if exists )General Ledger11.5 MRC ( if exists )SupplierPurchasingEncumbrancePrepaymentPayment Document and BankCash ManagementTreasury ConfirmationCurrencyArgentina Localizations (ifapplicable)

d. R12.0.[34] : Oracle Payables Accounting Health Check Setup Test




12/8/2014 Knowledge


d. R12.0.[34] : Oracle Payables Accounting Health Check Setup Test

R12.0.[34] : Oracle Payables (SQLAP): Accounting Health Check Note 463727.1

Diagnostics Description Usage Instructions Layout ContainsApply patch 8513126 to get the latestversion of this diagnostic test.

This diagnostic test will display all thecorrupted accounting data inaccounting and transaction tables.

This test is applicable for all Payablesaccounting issues.

Error and warning messages, followedby suggested actions, identifypossible problem areas.

EBS Applicable Releases: 12.0,12.0.1, 12.0.2, 12.0.3, 12.0.4Application Name: Oracle PayablesTest Group: AccountingTest Name: Accounting Health CheckImportant: Apply patch 8513126 toget the latest version of thisdiagnostic test.


1. Login to Oracle EBusiness Suite2. Select the responsibility "OracleDiagnostics Tool" (see Note358831.1 for details)3. Select application "OraclePayables" from the "Application" listof values4. Click the "Advanced" tab5. Scroll down to group "Accounting"6. Select test name "AccountingHealth Check"7. Input Parameters (* required) Responsibility ID Operating Unit ID Data Updated On Or After (ddmmyyyy) Display Problem Details Max Rows Returned

Accounting Event DataInvoice Distribution DataPayment Accounting EventDataPayment History Event DataEvent is Accounted andPosted_Flagis not equal to YOut of Sync Posted Flags(Invoices)Out of Sync Posted Flags(Payments)Unaccounted Invoices inClosed PeriodUnaccounted Payments inClosed PeriodUnaccounted Historytransactions in Closed PeriodUnaccounted Events in ClosedPeriodTransactions MissingAccounting EventsTransactions MissingAccounting Events but HeadersexistAccounting for Payments withmultiple invoices Out of SyncAccounting DatesOut of Balance HeadersLarge Rounding LinesLarge Writeoff LinesInvalid CCIDsPrepayments with InvalidAmounts RemainingInconsistencies within apayment transactionType 1 6 Orphans

e. R12.0.6+ : Oracle Payables Trial Balance Diagnostics For An Invoice Activity Test

R12 Subledger Accounting (XLA): Trial Balance Diagnostics For An Invoice Activity Diagnostic Test Note 829180.1

Description Usage Instructions Layout ContainsThis test will collect and displaytransactional and accounting data fora given invoice and its payments. Itwill also attempt to diagnose the dataand provide information on correctiveactions if there is any issue found.

Use this test when an invoice appearsin the Trial Balance and its notexpected. Or if an invoice does notappear in the Trial Balance and itsexpected to be listed.


EBS Applicable Releases: 12.0.6 12.1.xApplication Name: SubledgerAccountingTest Group: Trial BalanceDiagnosticsTest Name: Trial Balance DiagnosticsFor An InvoiceNote: R12.0.x Patch8517685:R12.XLA.A R12.1.x Patch8310456:R12.XLA.B


1. Start Oracle EBusiness Suite2. If using release 12.0.6 or above a. Connect to responsibilityApplication Diagnostics b. Select the Diagnose menuoption c. Click button Select Applicationand select Application "SubledgerAccounting"

3. If using releases 12.0 12.0.4 a. Select the responsibility OracleDiagnostics Tool b. Select application SubledgerAccounting c. Click the Advanced tab

4. Scroll down to group "Trial BalanceDiagnostics"5. Select test name "Trial BalanceDiagnostics For An Invoice"6. Input Parameters (* required) Responsibility ID (LOV) * Operating Unit (LOV) * Ledger Id (LOV) * Invoice ID (LOV) * Trial Balance Definition Code(LOV) *

AP Transaction Table Details

R11i (Upgraded) AccountingTable Details

R12 Accounting Table Details

Identify problems in R11i(Upgraded) Data

Identify problems in R12 Data

f. Oracle Payables Trial Balance Diagnostics For An Invoice Details Test




12/8/2014 Knowledge


R12.0.[34] : Oracle Payables (SQLAP): Trial Balance Diagnostics For An Invoice Note 882682.1

Description Usage Instructions Layout ContainsUse this test when an invoice appears in the Trial Balance and its notexpected. Or if an invoice does not appear in theTrial Balance and its expected to belisted.

This test will collect and displaytransactional and accounting data fora given invoice and its payments. Itwill also attempt to diagnose the dataand provide information on correctiveactions if there is any issue found.



1. Login to Oracle EBusiness Suite2. Select the responsibility "OracleDiagnostics Tool" (see Note358831.1 for details)3. Select application "OraclePayables" from the "Application" listof values4. Click the "Advanced" tab5. Scroll down to group "Accounting"6. Select test name "Trial BalanceDiagnostics For An Invoice "

This test is available in OracleDiagnostics 2.5 which introduces anew security model for test execution.See Note 409141.1 for more details.

Input Parameters (* required) Responsibility ID (LOV) * Operating Unit (LOV) * Ledger Id (LOV) * Invoice ID (LOV) * Trial Balance Definition Code(LOV) *

AP Transaction Table Details

R11i (Upgraded) AccountingTable Details

R12 Accounting Table Details

Identify problems in R11i(Upgraded) Data

Identify problems in R12 Data

Back to Top

9. SUBLEDGER ACCOUNTING SETUP IN PAYABLES

You can optionally define your own accounting rules in Subledger Accounting to create accounting that meets your business requirements. In Subledger Accounting, you use the Accounting Methods Builder (AMB) to define the way subledger transactions are accounted. To do this, you create and modifysubledger journal line setups and application accounting definitions. These definitions define the journal entries that enable an organization to meet specific fiscal, regulatory, and analytical requirements.These definitions are then grouped into subledger accounting methods and assigned collectively to a ledger.

Accounting Methods Builder (AMB) Overview

The AMB enables you to create and modify subledger journal line setups and application accounting definitions. These definitions define the journal entries that enable anorganization to meet specific fiscal, regulatory, and analytical requirements.These definitions are then grouped into subledger accounting methods and assigned collectively to a ledger.By using the AMB, you can define the way subledger transactions are accounted.

The different elements of a subledger journal and their relationships to the AMB are displayed in the diagram below and explained in the subsequent text.



12/8/2014 Knowledge


Accounting Methods Builder Process

The Components for Building Accounting Definitions figure below shows the components in the Accounting Methods Builder process for building accounting definitions andis described in the succeeding text.

9.1 Define custom sources

12/8/2014 Knowledge


9.2 Define journal line types

9.3 Define journal entry descriptions

9.4 Define mapping sets

12/8/2014 Knowledge


9.5 Define account derivation rules

9.6 Define journal lines definitions

12/8/2014 Knowledge


9.7 Define application accounting definitions

9.8 Define subledger accounting method

9.9 Assign each subledger method to a ledger using the Accounting Setup Manager.

For more details see: Using Accounting Setup Manager in the Oracle Financials Implementation Guide.

Back to Top

10. THE PREDEFINED SETUP ELEMENTS FOR ORACLE SUBLEDGER ACCOUNTING

Oracle Payables provides predefined data for Oracle Subledger Accounting that you can use to integrate the two applications. When you run the Create Accounting program, the program uses the predefined data to determine how to create the accounting. Payables predefines setup for Subledger Accounting so that the Create Accounting program accepts the default accounting information from AutoAccounting withoutchange. Subledger Accounting transfers the final accounting to Oracle General Ledger.

12/8/2014 Knowledge


Subledger Accounting transfers the final accounting to Oracle General Ledger.

You can optionally define your own subledger accounting rules to overwrite the default accounts from the accounting events.

Note: You must use an Oracle Payables responsibility to query predefined data that is associated with the Oracle Payables application.

For more details about the Predefined Elements for Payables Accounting, review the Oracle Payables Reference Guide, Release 12.1, Part Number E1279604 below:

The following sections describe the data that Payables predefines in Subledger Accounting:

ApplicationsEvent EntitiesEvent Classes and Event TypesProcess CategoriesAccounting Event Class OptionsSources, Source Assignments, and Accounting Attribute AssignmentsJournal Line TypesAccount Derivation RulesJournal Lines DefinitionsApplication Accounting DefinitionsSubledger Accounting Methods

INTERACTIVE DOCUMENTATION VIEWER: Predefined Elements for Payables Accounting

Use the scroll bar on the right (in the window below) to move up and down the page:

Back to Top

11. Still Have Questions?

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support PayablesCommunity.

Modification History

https://community.oracle.com/community/support/oracle_e-business_suite/payables

12/8/2014 Knowledge


Modification History

14Dec2011 Added latest AP Recommended Patches for 12.0 and 12.129Dec2011 Added Minimum set of patches that cover all the critical fixes after RPC release in Nov1003Jan2012 Updated the Recommended patches for 12.1 06Feb2012 Update the AP RPC (Recommended Patch Collection)30Aug2012 Updated with Aug2012 new RPCs30Nov2012 Updated with new Upgraded data GDF Diagnostics05May2014 Removed old patches + Updates

R12: Payables Trial Balance Helper Diagnostic to Validate Data for APTB issues Doc Id 1553507.1

RelatedProducts

Oracle EBusiness Suite > Financial Management > Procure to Pay > Oracle Payables > Accounting Issues in AP

KeywordsACCOUNTING; ACCOUNTS PAYABLE TRIAL BALANCE; BUDGET; BUDGETARY CONTROL; CREATE ACCOUNTING; ENCUMBRANCE; GL TRANSFER; IMPORT; JOURNAL

ENTRIES; JOURNAL IMPORT; PAYMENT; PERFORMANCE; PERIOD STATUS; POSTED INVOICE REGISTER; POSTED PAYMENT REGISTER; R12; RECONCILIATION;SECONDARY LEDGER; TAX REGISTER; TRIAL BALANCEErrorsAP_IBY_PMT_MISMATCH; FRM40654; ORA1403; ORA1422; ORA937; XLA_AP_ACCT_HOOKS_PKG.MAIN

Translations

English Source Korean 한국어

Back to Top

Need an explanation of Support Policies? Learn more...

About Contact Legal Terms of Use PrivacyCopyright (c) 2013 Oracle and/or its affiliates. All rights reserved.

http://www.oracle.com/us/corporate/contracts/cloud-services/index.html

http://www.oracle.com/legal/index.html

http://www.oracle.com/corporate/contact/index.html

http://www.oracle.com/legal/terms/index.html


http://www.oracle.com/corporate/index.html

http://www.oracle.com/legal/privacy/index.html