12/2/12 Document

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=cpui3951s_2074

11i ACCTG - Create Accounting Entries Troubleshooting Guide [ID 131225.1]

Modified: Feb 18, 2011 Type: BULLETIN Status: PUBLISHED Priority: 3

Troubleshooting Guide 11i

Oracle Payables Create Accounting Entries

The information in this document has been reviewed and is current as of 19-May-2008.

1. Script: R11.5 Payables Closing Diagnostic Script (180165.1)2. Script: R11.5 Payables Accounting Diagnostic Script (180164.1)3. Script: R11.5 Payables Trial Balance Diagnostic Script (180167.1)4. Script: APList Debug Data Script (148388.1)5. Prob: Cannot create Accounting for VOIDED payment6. Prob: Zero Dollar Invoice Payment creating Additional Write and Liability Accounting Lines and Invalid Accounts.7. Prob: Create Accounting Errors with APP-FND-00756 When Using Security Rules.8. Prob: Unable to Close AP Period or Sweep Unposted Transactions.9. Prob: The accounting process in AP creates single sided enteries which fail with an error code of debits not

equal to credits.10. Prob: When you attempt to run the Create Accounting process you receive REP-1419 error11. Prob: Payables Accounting Process Fails with error: ORA-01006: bind variable does not exist occurred in

AP_ACCOUNTING_ENGINE_PKG.do_accounting<-APXAEREP.12. Prob: The Transfer to General Ledger errors with MSG-00999: ORA-20100: File o0000021.tmp creation for

FND_FILE failed.13. Prob: When running the Create Accounting Process you receive MSG-00004: After the call to

AP_Accounting_Engine_Pkg.Do_Accounting.14. Prob: While running the Create Accounting Process, receive error paramter ORG ID is not entered and the

process cannot be started.15. Prob: When drilling down to AP details, no records are returned.16. Prob: What articles, white papers, or manuals should I read for more information on Create Accounting Process

issues?17. Prob: What are the MetaLink keywords I should use when searching for Create Accounting Process issues on

MetaLink?18. Prob: The problems and solutions listed in this guide do not answer my question.

1. Script: R11.5 Payables Closing Diagnostic Script.

Sol: Please download this script from note 180165.1 to assist in the resolution of this issue. Thisscript provides information on invoices or payments that have not yet been accounted, oraccounting information that needs to be transferred to GL before closing is possible.

[top]

2. Script: R11.5 Payables Accounting Diagnostic Script.

Sol: Please download this script from note 180164.1 to assist in the resolution of this issue. Thisscript will go through the accounting for an invoice or payment and provide additional informationon an error with the accounting.

[top]

12/2/12 Document

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=cpui3951s_2074

3. Script: R11.5 Payables Trial Balance Script.

Sol: Please download this script from note 180167.1 to assist in the resolution of this issue. Thisscript will provide detailed information on why a particular invoice is on the Trial Balance reportwhen it should not be.

[top]

4. Script: APList Debug Data Script.

Sol: Please download the script from note 148388.1 to provide detailed data information on aninvoice or payment.

[top]

5. Prob: Cannot create Accounting for VOIDED payment

Sol: Example:

1. Create and approve an invoice.2. Create accounting for the invoice.3. Pay the Invoice.4. Create accounting for the Payment5. Void the Payment.6. You don't want to pay the invoice yet, so you place a manual hold on the invoice.7. Try to create accounting for the Payment.

In this example the system cannot create accounting for the voided payment because the payment was placed on a manual hold i.e. the invoice is not approved. Payment Accounting will not be created unless the invoices paid on that Payment are approved.

To resolve the issue do the following:

1. Release the hold/Fix the reason for the hold2. Approve the invoice. Verify that the invoice is approved, NO HOLDS.3. Create accounting for the payment4. Create accounting for the invoice.

[top]

6. Prob: Zero Dollar Invoice Payment creating Additional Write and Liability Accounting Lines andInvalid Accounts.

Sol: Please reference note 163308.1 to assist in the resolution of this issue.

[top]

7. Prob: Create Accounting Errors with APP-FND-00756 When Using Security Rules.

Sol: This is a setup issue. Please reference note 178551.1 to assist in the resolution of this issue.

[top]

8. Prob: Unable to Close AP Period or Sweep Unposted Transactions.

Sol. Please reference note 174638.1 to assist in the resolution of this issue and run the script tohelp identify the unposted or untransferred transactions that are preventing closing.

[top]

12/2/12 Document

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=cpui3951s_2074

9. Prob: The accounting process in AP creates single sided enteries which fail with an error code ofdebits not equal to credits.

Sol: The upgrade process did not take into consideration the use of Automatic Offsets. This isfixed with patch 1450552 available in 11i.AP.C 1476751. Please contact support for the details ofthe associated sql script data fix and patch instructions.

[top]

10. Prob: When you attempt to run the Create Accounting process you receive the following errors:

REP-1419: 'beforereport': PL/SQL program aborted. ORA-6502: PL/SQL: numeric or value error: character to number conversion

Error occurred in AP_ACCOUNTING_ENGINE_PKG.init_accounting_definitions<-AP_ACCOUNTING_ENGINE_PKG.do_accounting<-APXAEREP with parameters (&PARAMETERS) while performing the following operation:&DEBUG_INFO

Sol: This is bug 1320184. Apply patch 1320184 for the fix.

[top]

11. Prob: Payables Accounting Process fails with the following error: ORA-01006: bind variable doesnot exist occurred in AP_ACCOUNTING_ENGINE_PKG.do_accounting<-APXAEREP.

Sol: This can be a setup issue. Please reference note 120659.1 to assist in the resolution of thisissue.

[top]

12. Prob: The Transfer to General Ledger errors with the following:

MSG-00999: ORA-20100: File o0000021.tmp creation for FND_FILE failed.

You will find more information on the cause of the error in request log.

ORA-06512: at "APPS.FND_FILE", line 419 ORA-06512: at "APPS.FND_FILE", line 536 ORA-06512: at "APPS.XLA_GL_TRANSFER_PKG", line 78 ORA-06512: at "APPS.XLA_GL_TRANSFER_PKG", line 1657 MSG-00005: Transfer to GL Failed. MSG-00000: User-Defined Exception REP-1419: 'beforereport': PL/SQL program aborted.

Sol: This is not a bug. This is a setup issue.

1) Make sure that you have defined a directory for the utl_file_dir in your init.ora file $ORACLE_HOME/dbs.

2) Make sure that you have defined the SAME directory for $APPLPTMP in your environment file $APPL_TOP/XXX.envi.

3) This directory is on your database server and everyone should have read, write and execute permission on it.

4) Bounce your database and concurrent manager.

[top]

12/2/12 Document

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=cpui3951s_2074

13. Prob: When running the Create Accounting Process you receive the following errors:

MSG-00004: After the call to AP_Accounting_Engine_Pkg.Do_Accounting MSG-00005: Error occured in the accounting process MSG-00006: Error Message: ORA-20100: File o0000002.tmp creation for FND_FILE failed

Sol: You must check the following two environment variables:

APPLTMP and APPLPTMP

Make sure these environment variables list a directory path that is valid and has write access(permissions are 777 in a Unix environment).

You must also check the init.ora parameter for the parameter:

utl_file_dir

Make sure this is a correct path and the path has write access as well.

[top]

14. Prob: While running the Create Accounting Process, after entering the parameters, you get theerror message that paramter ORG ID is not entered and the process cannot be started.

Sol: As a workaround, change the parameter org_id to not required. In the System Administratorresponsibility, go to -> Concurrent -> Program -> Define. Query up the short name APACCENG.Select the Parameters button. Scroll down to the Org ID parameter, and mark it as not required.

[top]

15. Prob: When drilling down to AP details, no records are returned, even though you can verify thatposted Payables Invoice and Payment transactions have been properly

Sol: You must perform the AP post-upgrade step of running apgllink.sql and apallink.sql This stepis required to be able to drilldown for AP pre-11i journals. The latest patch for the post-upgradestep is available through bug 1384602.

[top]

16. Prob: What articles, white papers, or manuals should I read for more information on AccountingProcess issues?

Sol: Payables - Accounting in 11i Oracle Payables User's Guide - Release 11i

[top]

17. Prob: What are the MetaLink keywords I should use when searching for Accounting Process issueson MetaLink?

Sol: APACCEG, Accounting, create accounting, APGLTRANS, payables transfer to GL

[top]

18. Prob: The problems and solutions listed in this guide do not answer my question.

Sol: If the Troubleshooting guide list for Create Accounting Process does not answer yourquestion, please provide the information for an aplist data script and a debug log file and uploadthis information when you click here to log an iTar.

12/2/12 Document

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=cpui3951s_2074

[top]

IMPORTANT: If you did not find the information you were searching for, please review the following Payables CreateAccounting 11i documents Payables Create Accounting 11i Current Issues Payables Create Accounting 11i One-Off Patches Payables Create Accounting 11i Setup and Usage Instructions Payables Create Accounting 11i Troubleshooting Guide Payables Create Accounting 11i Frequently Asked Questions (FAQ’s)

Copyright © 2002 Oracle. All rights reserved. O racle is a registered trademark of O racle C orporation. V arious product and serv ice names referenced herein may be trademarks of O racle C orporation. A ll otherproduct and serv ice names mentioned may be trademarks of their respectiv e owners.

Disclaimer: This document is prov ided for information purposes only and the contents hereof are subject to change w ithout notice. O racle C orporation does notwarrant that this document is error-free, nor does it prov ide any other warranties or conditions, whether expressed orally or implied in law , including impliedwarranties and conditions of merchantability or fitness for a particular purpose. O racle C orporation specifically disclaims any liability w ith respect to this document andno contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any

means, electronic or mechanical, for any purpose, w ithout the prior w ritten permission of O racle C orporation.