AP Invoice Was Rejected By AP Payables Open Interface Import With Supplier Site With Hold Reason
(Doc ID 2230058.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Payables - Version 12.2.5 and later
Information in this document applies to any platform.
Formerly it has been discussed this issue with the Product Management team and explained
that the current existing behavior after fix bug 15978920 is the correct behavior.
Actually the hold reasons at supplier site level, cannot be translated and
are free texts as entered by user. This causes issues for customers having
multi-language environment. Thus we have fixed bug 15978920 (R12) and
8199946(11i) to always show translated hold reason from lookup as per
application user's preference.
There currently exists an Enhancement Request Bug 19126295 - PAYMENT HOLD REASON HAS NOT BEEN TAKEN FROM SUPPLIER SITE FOR MANUAL INVOICE
to implement the functionality that as per your update it existed in 11i (but that would work in the multi-language environment).
On : 12.2.5 version, Open Interface and Inv Import
AP Invoice Was Rejected By AP Payables Open Interface Import With supplier site with hold reason.
Import the invoice.
The issue can be reproduced at will with the following steps:
1.Import data to AP Interface table: ap_invoices_interface and ap_invoice_lines_interface
Invoice number 'ZZZZ'.
Supplier site YYY
(at supplier site) Hold_Future_payments_flag = 'Y'
(at supplier site) HOLD_REASON = '<string of characters longer than 100>'
This invoice number is unique.
2.Payables Responsibility,Request-> Payables Open Interface Program
3. Rejection shows 'Duplicate invoice Number' --> Invoice number for this supplier or party already exists
Once the concurrent 'Payables Open Interface Import' ends, the invoice ''ZZZZ'' is with REJECTED status in the AP interface, however the 'Payables Open Interface Import' has created an invoice in ap_invoices_all table without lines with the number ''ZZZZ''
(The test in 11i is working).
The issue has the following business impact:
Due to this issue, users cannot .
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