How Can I Find Out Which Invoices Are Matched To A Purchase Order?
A: In Payables, run the Matching Detail Report from Other > Request > Run.
This report will show you detail of how an invoice, purchase order, or receipt was matched. This report is especially helpful when an invoice is on hold and you are trying determine why the hold was placed.
What Reports Are Available To Check If A Credit Memo Is Matched To An Invoice?
A: In Payables, run the Credit Memo Matching Report from Other > Request > Run
Why does the Error App-Sqlap-10715 Appear when Attempting to Match an Invoice to a PO?
A: Matching an invoice to a PO for the entire quantity closes the PO for invoicing. If the invoice line is discarded (using the Discard button), reversing the PO match the Match button is again available, so the invoice is matched again to the same PO for a different quantity. At that time, the following message occurs: APP-SQLAP-10715: This purchase order line is closed for invoicing. You may want to review the purchase order before continuing with this match.
In R12, when we discard the line, the status is updated only at validation time. Similarly, we update the quantity billed and amount billed for PO's when we match or reverse, but the status is affected ONLY when we validate the invoice. So, after pressing the Discard button, validate the invoice before proceeding with any other actions on the invoice. See Doc ID 456370.1 and Bug 5927520 for more information.
Why Can An Invoice Be Matched To A PO Without A Receipt Being Needed?
A: If the match option on PO shipment is set to Purchase Order then the invoice can be matched directly to the PO. However, if the PO is setup with 3-way matching, then after invoice validation, if a tolerance is defined then a QTY REC hold will be placed on the invoice which will need a receipt to be entered in order for the hold to be released. See Doc ID 433545.1 for more information.
Is there a maximum number of receipts that should be matched to one invoice?
A: There is no restriction about the receipt match to invoice, however, if you match to too many receipts, there will be performance issue when you matching or invalidating so this is not encouraged.
Why Does The PO Number Disappear From The Invoice Header After Matching To A PO?
A: When you are using the match button you never know how many times to how many PO's or receipts users are going to match the invoice to, hence, we do not store the PO number at the header level. See Doc ID 738788.1 for more information.
When Entering An Invoice, The Match Button Becomes Disabled When The Line Item Is Selected. Users Are Unable To Match An Invoice To A Purchase Order Or Receipt Without This Option Enabled. Is This correct?
A: This is standard functionality but once users are done adding/updating in the Lines tab, if the General Tab is selected again, the Match button will be available.
When Matching A PO To An Invoice, The Match Basis Is Not As Expected. How Does This Field Relate To The PO Line Type?
A: Match Basis will be either Quantity or Amount. The value of this field is based on the value basis of the purchase order line's type. See Doc ID 428303.1 for more information.
How Do You Match An Invoice To A PO With Two Lines, One With Match Level Receipt (3-Way), And One With Match Level PO (2-Way)?
A: First match the invoice to the PO setup with match level receipt. Then requery the invoice and match the second line to the PO. See Doc ID 181736.1 for more information.
Why does PO Match Comes Over as Exclusive Tax Lines?
A: In PO, taxes are always exclusive as per the PO application/product design. So in AP, an invoice matched to a PO would also calculate taxes as exclusive taxes. Please see Bug 6748767 R12: APXINWKB - JAPAN INCLUSIVE TAX, PO MATCH COMES OVER AS EXCLUSIVE TAX LINES for details. See Doc ID 549988.1 for more information.
Why Can Users Not Drilldown To A PO From The Invoice During Matching Without Encountering A 'Function Not Available For This Responsibility' Message?
A: This is due to incorrect menu setup. The submenu AP_PO_VIEW_PURCHASE_ORDERS_GUI needs to be added to the menu for the responsibility used to perform the match. See Doc ID 1350427.1 for more information.
Does The Purchase Order Number Get Populated On Freight, Miscellaneous And Tax Lines When Using The Allocations Window?
A: The purchase order number will not get populated on freight, miscellaneous and nonrecoverable tax lines. PO information is populated for recoverable tax lines.
Why Does Matching An Invoice To PO Default The Accrual Account To The Invoice Distributions?
A: If Accrue on Receipt is selected (checked) on the shipment line to which the invoice is matched, then the functionality is to default the PO accrual account on the invoice distributions. The PO Charge Account will default to the invoice distributions only if Accrue on Receipt is not checked. This is intended functionality.
After Matching An Invoice To A PO, The Distribution Shows As The PO Charge Account But We Were Expecting To See The Accrual Account Displayed. What Happened?
A: If the Accrue on Receipt option is set to Yes for the shipment, then the Accrual Account will be used on the Invoice Distribution. Shipments for inventory items will always be set to Accrue on Receipt. There is no way to change that. In other words the PO matched distributions for inventory items will always have the PO Accrual account as the Distribution account. Shipments for Expense items can be set to Accrue at Period End. In that case the Charge account defined on the PO distribution will be used as the distribution account. The system works as designed.
How Do I Remove A Final Matching Hold, So I Can Pay The Invoice?
A: This hold is in effect because the invoice was matched to a PO shipment that has a status of Final Closed. In 11.5.10 and above, there is no way to manually remove the hold, reverse distributions or cancel the invoice. Please see Doc ID 1447955.1 for more details.
What Do The Codes For The Final Match Flag Mean?
A: After you match an invoice to a purchase order, you can look at the AP_INVOICE_DISTRIBUTIONS_ALL table and observe different codes in the FINAL_MATCH_FLAG column. The FINAL_MATCH_FLAG has the following quickcodes:
1. N - No. The PO shipment line has not been matched.
2. Y - Yes. The PO shipment line has been matched, and one of the invoices for this PO has been final matched. When a PO is final matched to an invoice, all other invoices matched to that PO are updated, too. So, you cannot tell from this flag, which invoice was final matched.
3. D - Done. The PO shipment line is closed. You cannot invoice this distribution line.
What Does Final Match Do?
A: When you final match an invoice to a PO, you can never match another invoice to that PO. The PO lines that have been final matched are permanently closed. In 11.5.10 and above, invoices matched to a Finally Closed PO cannot be updated or canceled. Please see Doc ID 1447955.1 for help processing invoices with final match holds.
Why are Matched, Project Related Invoice Incorrectly Placed on Dist Variance Hold?
A: This was addressed via Bug 6682104 UNABLE TO VALIDATE PROJECT RELATED INVOICES BECAUSE OF UNCLEAR and fixed in the following versions:
apiindib.pls 120.59.12000000.5
apinlinb.pls 120.56.12000000.6
APXINWKB.fmb 120.496.12000000.113
The fix is included in Patch 6887291:R12.AP.A. Alternately apply the latest RUP patch identified in Doc ID 423541.1. See Doc ID 556663.1 for more information and the recommended solution.
How Does Descriptive Flexfield Information From The PO Line Get To AP During Invoice Matching?
A: Enable the Transfer PO Descriptive Flexfield Information Payables Option. With this enabled, descriptive flexfield information will automatically transfer from the purchase order distribution to the invoice distribution when match an invoice to a purchase order is done. The flexfield structure for purchase order distributions and invoice distributions should be same. Note, for ERS invoices, PO will always populate the flexfield information in the AP Invoice Interface tables, so AP will always import these value irrespective of this setup.
How Does The RCV_TRANSACTION_ID Column Get Populated In The AP_INVOICE_DISTRIBUTIONS_ALL Table?
A: The RCV_TRANSACTION_ID column is only populated when the Invoice Match Option is set to Receipt on the PO Shipment line.
It Is Possible To Match A Purchase Order To An Invoice Even If Receiving Date Is Earlier Than Invoicing Date. In Practice, It Is Illogical That You Pay Before Receiving. Does Oracle Allow Us To HOLD Invoices In Which 'INVOICING DATE' Is Earlier Than 'RECEIVING DATE'?
A: There is no such Standard seeded hold for this. If you want to make a hold on this case, you have to create and apply manual holds. See Doc ID 1427975.1 for more information.
Why Do I Get An Invoice Price Variance (IPV) Line When I Match An Invoice To A PO With Nonrecoverable Tax?
A: Nonrecoverable taxes are considered part of the "landed" cost of the items purchased when the non recoverable tax is not already included in the purchase order. See Doc ID 281505.1 for more information.
Unable To Match To A Specific Distribution On A Release. How Can This Be Fixed?
A: Enable the Allow Distribution Level Matching Payables Option, if you want to allow matching to purchase order distributions. If you enable this option, you can match an invoice to one or more purchase order distributions. If you do not enable this option, Payables only allows you to match an invoice to a purchase order shipment.
Why does Invoice Match to PO Error with ORA-24347 WARNING OF A NULL COLUMN IN AN AGGREGATE FUNCTION?
A: The application is trying to covert quick_po_number to a number. Bug 6637551 was logged for this issue and it has been confirmed fixed in patch 6641690. The readme for this patch will not mention this issue directly. However, this is the patch that Development indicated will fix this bug. Apply the latest Rup patch identified in Doc ID 423541.1. See Doc ID 473239.1 for more information.
Why does a PO Matched Invoice Status Change to 'Needs Revalidation'?
A: This issue was reported as Bug 6874994 R12 DISCARD NEVER VALIDATED INVOICE LINE - INV STATUS SHOWS NEEDS and fixed in 12.0 patch/115/sql/apinvutb.pls 120.44.12000000.7 or higher. Apply the latest Rup patch identified in Doc ID 423541.1. See Doc ID 557694.1 for more information.
Why does a PO Matched Invoice w/Invalid CCID Error with ORA-1400 in DIST_CODE_COMBINATION_ID?
A: This was reported as Bug 6887089 ORA-1400 VALIDATING PO MATCHED INVOICE W/INVAILID CCID and deemed to be a code bug which was fixed in zxmwrecdmsrvpubb.pls 120.117.12000000.14 or higher. The fix is included in Patch 6887089. With this fix, a message indicating the account is invalid will appear. See Doc ID 560763.1 for more information.
Purchasing Encumbrances Are Not Reversed By Invoice Matching. Why Is This?
A: If PO Encumbrance Type and Invoice Encumbrance Type are the same, AP will encumber only for variances. Only when the Accounting Entries have been created for AP, would the encumbrance be relieved. Once the 'Create Accounting Entries' process is run, encumbrance is relieved. This is the standard functionality and as per design.
Why is Encumbrance Wrong after Matching, Reversing and Matching to PO again?
A: This is due to Bug 6009101 ENCUMBERED AMOUNT ON PO DISTRIBUTIONS IS INCORRECT. Code changes needed to be made to disallow the cancellation or discard of line or reversal of distribution of the invoice, if the purchase order is in an unapproved or unreserved state. This bug is fixed in the following versions:
APXINWKB.fmb 120.496.12000000.26
apicancb.pls-120.28.12000000.5
apilnutb.pls-120.28.12000000.2
ap12amg.ldt120.38.12000000.3
Apply the latest Rup patch identified in Doc ID 423541.1. See Doc ID 467436.1 for more information.
There Are Differences Between The PO And Invoice Billed/Received/Invoiced Quantities. They Should Have The Same Values If Viewed In Payables Or Purchasing. What Could Be The Problem?
A: This is a classic data corruption issue. Run the MasterGDF diagnostic Doc ID 1360390.1 for your invoice to determine if you are experiencing any corruption for that invoice and find the solution for your specific situation.
User Discards Invoice Lines On PO Matched Invoice And Cancels The Invoice, However, The PO Still Shows An Amount Billed. This Means The PO Cannot Be Cancelled Due To Mismatch Between The AP And PO Tables. Why Is This Happening?
A: This is a data corruption issue. Run the MasterGDF diagnostic Doc ID 1360390.1 for your invoice to determine if you are experiencing any corruption for that invoice and find the solution for your specific situation.
Unable To Validate Matched Invoice And Unable To Cancel Invoice. How Can This Invoice Be Processed?
A: The chances are high that this specific invoice has some data corruption. Run the MasterGDF diagnostic Doc ID 1360390.1 for your invoice to determine if you are experiencing any corruption for that invoice and find the solution for your specific situation.
Invoice That Was Matched To Receipt, Discarded And Rematched Has Doubled Matching Amounts. Unable To Cancel The Invoice And Line Cannot Be Discarded As This Would Result In Negative Quantities On The PO. What Is The Problem?
A: This is a data corruption issue. Run the MasterGDF diagnostic Doc ID 1360390.1 for your invoice to determine if you are experiencing any corruption for that invoice and find the solution for your specific situation.
Why does the Quickmatch of Invoice to Receipt Error with APP-SQLAP-10000 ORA-6502 PL/SQL Numeric or Value?
A: Lines and Distributions are not created. This was reported as Bug 5929800 ADS120.GA:FIN:QUICK MATCH BY RECEIPT FAILS AND CAUSES FORMS ERROR and was fixed in 12.0 patch/115/sql/apmatchb.pls-120.54.12000000.2 or higher. Apply the latest Rup patch identified in Doc ID 423541.1. See Doc ID 467106.1 for more information.
Attempting To Match To A PO That Was Previously Matched And Unmatched, Incorrectly Shows Negative Value For Billed Quantity. What Is The Problem?
A: This is a data corruption issue. Run the MasterGDF diagnostic Doc ID 1360390.1 for your invoice to determine if you are experiencing any corruption for that invoice and find the solution for your specific situation.
Why does the Asset_Tracking_Flag Remain 'N' for PO Matched Invoice Lines?
A: For a PO matched invoice, if the PO has the accrue on receipt checked and the PO charge account is asset type, then after matching, the distribution line created has assets_tracking_flag set to 'N' (instead of assets_tracking_flag set to 'Y').
This was logged as Bug 6014884 ASSET_TRACKING_FLAG NOT SET IN INVOICE DISTRIBUTION LINES AS EXPECTED and fixed in 12.0 patch/115/sql/apmatchb.pls-120.54.12000000.3 or higher.
Apply the latest Rup patch identified in Doc ID 423541.1. See Doc ID 467442.1 for more information.
Why does Receipt Matched or ERS Invoices have the assets_tracking_flag Set to N?
A: Receipt matched invoices and ERS created invoices do not have the assets_tracking_flag populated to Yes, when accrue on receipt and charge account is set up as an asset account. This was reported as Bug 6683010 ASSET_TRACKING_FLAG NOT SET FOR RECEIPT MATCH AND ERS INVOICES and was fixed in 12.0 patch/115/sql/aprcvmtb.pls 120.59.12000000.2 or higher. Development has created one-off patch 6683010 for this bug. Please see Doc ID 548975.1 for more information.
Create Adjusting Documents (APXCADIP) Program Is Not Creating PPA Invoices When The PO# Parameter Is Not Provided. There Are Four Parameters: PO#, Supplier, Supplier Site And Resubmit Interface Import And None Of These Are Mandatory Yet The Program Does Not Create The Invoice For The Standard PO That References The Global Blanket Purchase Agreements (GBPA) That Got Updated If The PO# Is Not Entered. Why Is This?
A: The Purchase Order for which the price is to be adjusted must be specified so that the application knows which PO should be adjusted. An ER was logged to allow a global Blanket PO agreement number to be entered as a parameter so that all POs linked to this would be updated. See Doc ID 1378388.1 for more information.
Why does Matching a Credit Memo to a PO Matched Invoice Error with FRM-40212?
A: An incorrect match option is used. Bug 6674082 R12 CAN'T MATCH CREDIT MEMO TO PO MATCHED INVOICE USING CORRECTION BUTTON. To correct a PO Matched Invoice Line, use the Match Option 'PO' and hit 'Correct' button. To correct an unmatched Invoice Line, use the Match Option 'Invoice' and hit the 'Correct' button. See Note.471725.1 for more information.
Is It Possible To Enter A Different Tax Classification Code For The Return Tax Code During A Price Correction?
A: No different taxes in the original transaction and price correction is not feasible because a price correction will alter the item price on the original invoice, without changing the total quantity billed. Accordingly, the matching portion of tax (either positive or negative) needs to be the same tax as on the original invoice. If you want to rematch the item with different price and tax, you will need to discard the originally matched item line, so its tax will be reversed, and rematch the shipment, this time with the correct price and tax.
Automatic Debit Memo Creation Failed When Creating a RTS Transaction. What Could Be Wrong?
A: For an Automatic Debit Memo to be created in AP, the following must be true:
The supplier site has to be marked to allow RTS transactions.
There must be an original invoice already in AP for the item being returned.
The PO and the original Invoice must be to the same Supplier Site.
The Supplier Site must be marked as both a Pay Site and a Purchasing Site.
The return quantity cannot cause the quantity invoiced to go negative.
The return quantity must be equal to or less than the quantity invoiced.
The Create Debit Memo checkbox must also be turned on in the Receipt form.
The return must be to the Supplier, and not to Receiving.
If the debit memo is not created automatically, you should create the debit memo manually in the Payables application.
Debit Memo Created For A RTS Transaction Has Terms From The Supplier Site. Is This Correct?
A: The payment terms for a supplier site default to the invoices you enter for the site except in the following circumstances:
You enter a PO Default or QuickMatch invoice in the Invoice Workbench, in which case the terms default from the purchase order.
You import an invoice record that has payment terms specified on the record, or the import process can derive terms from purchase order matching. You can override the default payment terms on any invoice.
So, the debit memo is correctly picking up payment term from the supplier site.
Create Debit Memo From RTS Transaction Is Not Created When The RCV: Processing Mode Profile Option Is Set To Online. Why?
A: When the system profile option, RCV: Processing Mode is set to Online, no Debit Memo is created in Payables. Set the option to Immediate so the debit memo will be generated in Payables.
Create Debit Memo From RTS Errors AP_CANNOT_ASSIGN_DOC_SEQ. What Is The Problem?
A: Ensure that the seeded Document Category is the one assigned to the set of books for successful creation of automatic / RTS Debit memos
Price Hold Not Released When Entering Credit Memo. How Can This Be Released?
A: Use one of the following methods to resolve this issue:
Match the credit memo to the PO with price correction enabled and the related invoice selected.
Match the credit memo to the invoice which is matched to the PO in question and validate both the invoice and the credit memo.
Why Are Users Unable to Pay RTS Debit Memo?
A: Bug 5583430 RTS DEBIT MEMO BEEN CREATED WITH PAY ALONE FLAG. The bug is fixed in apcrtdmb.pls version 120.14.12000000.3 or higher. Apply the latest Rup patch identified in Doc ID 423541.1. See Doc ID 466707.1 for more information.
Why does the Invoice Validation Process Error ORA-1403 in Procedure ZX_TRD_INTERNAL_SERVICES_PVT.get_variance_related_columns for Some Operating Units?
A: Bug 6967515 INV VALIDATION FOR APA RUNS IN ERROR ORA-1403. A root cause has not been identified. The problem invoices were successfully validated online. See Doc ID 565877.1 for more information and the recommended solution.
Why does a User-Defined Exception Error Occur when Attempting to Run Invoice Validation?
A: On PO matched invoices, if recoverability is 100% then zero (0) amount Non recoverable distribution does not get copied to invoice distributions. This causes the invoice validation to fail. Specifically, because of condition "zd.rec_nrec_rate = 100" in CURSOR insert_tax_dist of function Return_Tax_Distributions of package body AP_ETAX_UTILITY_PKG. This occurred after upgrading from 11i to R12. This was logged as Bug 6906867 INVOICE VALIDATION FOR APA AND FINOTECH RUNNING IN ERROR. See Doc ID 561418.1 for more information and the recommended solution.
Knowledge source: Oralce Metalink.
