Last updated on OCTOBER 18, 2016
This was first discovered when an xai inbound service was configured using the base service CILCSVAP. When using it to do a read of an SA, it returned the details of the SA requested, but also returned the contract terms for other SAs unrelated to the requested SA.
Further investigation reveals that calling the SA Maintenance Page via the Online application also has the same result. Viewing the SA via the UI does not show the erroneous contract terms, but the debug logs do show that the extra SAs are indeed returned (the UI filters out those not for the current SA).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms