Need to Catch Invalid Project Costing and COA Segments on AP invoice prior to Accounting
(Doc ID 2714515.1)
Last updated on OCTOBER 05, 2020
Applies to:Oracle Fusion Payables Cloud Service - Version 11.13.20.04.0 and later
Information in this document applies to any platform.
The subledger accounting method is setup such that if there is a mismatch between distribution and project fields on an invoice, accounting errors will occur downstream.
The requirement is that a warning or error occur when "mismatching" info is entered, or the invoice should not be allowed to be validated. This would allow for correction of data before accounting is attempted.
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