This document is being delivered to you via Oracle Support's Rapid Visibility (R aV) process and therefore has

not been subject to an independent technical revie w.

Applies to: Oracle Payables - Version: 12.06 Information in this document applies to any platform. Symptoms Create Adjusting Documents in payable program not relieving Price Variance line on invoice. Steps To Reproduce: 1) 2) 3) 4) 5) 6) 7) Profile PO:Allow Retroactive Pricing of POs should be set to 'ALL RELEASES' Created a PO with quantity 10 and price10. Created a matched invoice with price 12 and validated invoice. There is one IPV distribution gets created with 20. Now going back to PO and change price to 12. Run the program Create Adjusting Documents from Payables Document Program. No change in invoice status.Still IPV of 20 and Accrual of 100.

Cause In AP_RETRO_PRICING_PKG (apretrob.pls), FUNCTION -Import_Retroprice_Adjustments () is the main Public procedure called from the Payables Open Interface Import P rogram ("import") which treats the records in the interface tables as "invoice i nstructions" rather than each record as an individual invoice. For recods with s ource='PPA' the program makes all necessary adjustments to original invoices and will create the new adjustment documents. The Funtion Insert_Zero_Amt_Adjustments is the one to relieve Price Variance lin e on invoice. This function is called like in a FOR LOOP that is dependent on a PL/SQL table: FOR i IN 1..l_base_match_lines_list.COUNT LOOP The problem with this is that we are already deleting the PLSQL table earlier in the code in Step 4. Also it makes no sense to call it outside the instruction_l ines loop as a set of base match lines is fetched for each row of the instructio n_lines cursor. This issue is explained in Bug 9010175 Solution To implement the solution, please execute the following steps: 1. Download and review the readme and pre-requisites for Patch.9010175:R12.AP.A Log a SR with support if patch is password protected. 2. Ensure that you have taken a backup of your system before applying the recom mended patch.

3. Apply the patch in a test environment. 4. Confirm the following file versions: For 12.0 apretrob.pls 120.25.12000000.12 For 12.1 apretrob.pls 120.29.12010000.8 You can use the commands like the following: strings -a $AP_TOP/patch/115/sql/apretrob.pls |grep '$Header' 5. Retest the issue. 6. Migrate the solution as appropriate to other environments.