R12 PAAPIMPB: PO_DISTRIBUTIONS_ALL ACCRUE_ON_RECEIPT_FLAG = Y but Invoices are Interfaced to Projects and not Receipts
(Doc ID 2072292.1)
Last updated on AUGUST 09, 2018
Applies to:Oracle Project Costing - Version 12.1.3 and later
Information in this document applies to any platform.
In Release 12, PO_DISTRIBUTIONS_ALL ACCRUE_ON_RECEIPT_FLAG = Y but invoices are sent to projects instead of the receipt.
In 11i, when the accrue on receipt flag was checked for a receipt, the system would send either the receipt or the invoice based upon which was interfaced first. If the receipt was interfaced first, then receipts would move to PA but if the invoice was interfaced first, the invoices would interface to PA. Once the first transaction was interfaced, that determine the type of transactions sent for the remainder of the project, i.e. if receipts are sent, then receipts will always be sent and not invoices. This functionality changed in R12. In R12, when the accrue on receipt flag is Y on the po distribution, then receipts go to PA, when it is N, invoices go to PA. But if the ap_invoice_distributions_all.HISTORICAL_FLAG = Y for any of the invoices attached to the po distribution, this indicates this PO/invoice was upgraded from 11i and the behavior will continue based upon what was interfaced first in 11i. Thus in R12, we see the PO_DISTRIBUTIONS_ALL ACCRUE_ON_RECEIPT_FLAG = Y but invoices are sent to projects instead of the receipt. This is intended behavior.
A code issue was introduced through bug 20467904 and is fixed in Bug 21369500 - DATAFIX: RECEIPT NOT ITNERFACING TO PROJECT. In bug 21369500, the developer indicates this code issue resulted in receipts marked with a pa_addition_flag = G (historical invoices matched to the same PO distribution were interfaced to projects in 11i, i.e., ap_invoice_distributions_all.HISTORICAL_FLAG = Y) and the invoice distributions were also marked with a pa_addition_flag = G due to this bug. Both a code fix and data fix were given to allow these invoices to once again flow to PA.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|