WebADI: Uploading Previously Saved Spreadsheets Invalidates the Session and Any Open Application Form Errors: Your log on session has become invalid. Exiting Oracle Applications
(Doc ID 2959110.1)
Last updated on JULY 07, 2023
Applies to:
Oracle Web Applications Desktop Integrator - Version 12.2.6 and laterInformation in this document applies to any platform.
E-Business Suite (EBS) Forms
Symptoms
Uploading previously saved WebADI spreadsheets causes the whole EBS session to become invalid and an error is displayed on the screen/any form opened. The users have to close out of everything in order to re-log into Oracle and relaunch Java to be able to use the Applications again.
Creating a new WebADI document from scratch and uploading it to the Application directly works fine. The issue replicates only for previously saved Excel sheets.
ERROR
Your log on session has become invalid. Exiting Oracle Applications
STEPS TO REPRODUCE
1. WebADI Desktop Integrator responsibility > Use the 'Create Document' menu link
2. Enter all the parameters and have the spreadsheet created in Excel
3. Fill in the data in the spreadsheet and upload it to the Applications using the 'Upload' button from the Oracle ribbon
4. Verify the upload is correctly executed (the confirmation is displayed on the screen)
5. Save this spreadsheet for later use and close Excel
6. Log out of the Applications then log back in
7. Navigate to any module using forms, for example General Ledger (GL) using a specific responsibility (for example: 'General Ledger Super User')
8. Open any form (such as Journal Entry form: Journals > Enter) and leave this one opened so that Java would stay active
9. From the machine, reopen the Excel spreadsheet saved in Step5
10. Attempt to upload the spreadsheet to the Applications using the 'Upload' button from the Oracle ribbon
11. Observe the request to log in which is expected > Enter the credentials
12. Return to the form left opened in Step8 above
13. See error on the form and note this forms session can no longer be used. The only way to proceed further is to close everything out and start over
Changes
None
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 |