My Oracle Support Banner

E1: 3P: How To Clear Quasi Static Tables Cached for WTS Environments (Doc ID 626188.1)

Last updated on AUGUST 31, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version SP23 and Prior and later
Information in this document applies to any platform.
*** check for relevance 7-MAY-2012 ***



Symptoms

Title: How To Clear quasi static tables Cached for WTS (Windows Terminal Server) environments

Abstract: The purpose of this document is to allow changes to specific quasi static tables (Ex: AAIs {F0012}, Company Constants {F0010}, etc.) to be read from WTS environments without recycling services on the Enterprise Server.


The caching problem occurs when a E1/OneWorld user is modifying data within designated OneWorld tables that are commonly filled with quasi static data. If there are OneWorld users who are connected to a Windows Terminal Server (WTS) and logged into a WTS based (W) environment they will not see the changes in the data until OneWorld Services on the Enterprise Server are stopped and restarted.
 


 

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
 Title: How To Clear quasi static tables Cached for WTS (Windows Terminal Server) environments
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.