SLS: When Subledger Security Is Used When Query the Same Invoice In Two Different Responsibilities It Shows Different Validation And Account Status
(Doc ID 1935243.1)
Last updated on MAY 04, 2020
Applies to:
Oracle Public Sector Financials (International) - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
When querying one invoice with 2 responsibilities, the information retrieved is not the same.
The same invoice is showing a different status at the same time in separate responsibilities.
Example: Invoice number AB123 shows a status of "Never Validated" and "Not Accounted" using the First Payables Inquiry Responsibility when using the invoices inquiry screen.
The same invoice AB123 shows a status of "Validated" and "Accounted" when using the Second Payables Support Responsibility when using the invoices inquiry screen.
This invoice has been paid already
OPSFi Subledger security is used.
EXPECTED BEHAVIOR
-----------------------
When querying one invoice with 2 responsibilities, expect to see the same information.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Use First Payables Inquiry Responsibility
2. Query invoice_num AB123 (shows as "Never Validated" and "Not Accounted")
3. Use Second Payables Support Responsibility
4. Query invoice_num AB123 (shows as "Validated" and "Accounted")
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |