REST API Not Fetching AR Transactions Using Transaction Numbers.
(Doc ID 2759045.1)
Last updated on MARCH 24, 2021
Applies to:Oracle Fusion Receivables Cloud Service - Version 11.13.20.04.0 and later
Information in this document applies to any platform.
On : 11.13.20.04.0 version, Webservice / REST API
REST API not fetching AR Transactions using Transaction Numbers.
For few cases users will need to use REST API AR Transactions using Transaction Number.
This Results in Error as Transaction number is not queriable.
"The attribute(s) [TransactionNumber] are not queriable."
Is there any alternative?
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