Results 1 to 5 of 5

Thread: SAW Cache clear issue

  1. #1
    Member Rauf's Avatar
    Join Date
    Jan 2012
    Location
    Kerala, India
    Posts
    724

    SAW Cache clear issue

    We are on TR 8.96.40, and uses Server Administration Workbench (SAW) for JAS Servers.

    Usually, we clear the below caches if there is any update on user role revisions, new tasks added to JDE menu or especially if previous financial period is opened for adjustments ( audit or other adjustments)

    Now, the issue begins. Usually we open the previous financial period in fat client. And users can use Fat Client's web to enter. BUT some times, some users can also enter using the server's web.

    It gives headache as some tricky user's eagle eyes catches that the period is opened and they enter the transactions which spoil the previous period trial balance.

    Is there any known issue in JAS for cache clearing ? How I can ensure that the period is not opened globally ?
    RAUF
    JDE Techno-Functional
    JDE E1 8.12 | TR 8.96.40 | Windows XP SP 3

  2. #2
    Try clear the Database Cache on the Enterprise Server. That's where the company info is being cached when accessed by business functions.

    From a FAT client open WSJ , select the server and take the row exit to clear cache, and select database cache and hit OK. It may take a few seconds depending on how busy the server is at that time.

    If your WSJ does not show you the intermediate screen to select the server but rather takes you directly to the submitted job view, then there should be a Form Exit called Advanced which will take you to the server selection screen.
    EnterpriseOne Xe to 9.2
    Windows/ Unix / AS400
    Oracle , SQL Server, DB2
    WAS , WLS
    AppWorx, Tidal , SmartScheduler

  3. #3
    Senior Member peterbruce's Avatar
    Join Date
    Jan 2004
    Location
    NSW Australia
    Posts
    2,164
    Rauf,

    I'm not sure that the timing of clearing the cache is impacting your efforts to restrict the opening of previous periods. Here is my understanding of the situation, please correct me if I'm wrong.

    To open a previous period you update the F0010 which is normally cached on the enterprise server. I don't think it is cached on the web server (JAS cache). If the cache is cleared, it will be repopulated from the table on the next call. Caches are also cleared when they expire. You seem to be relying on the cache expiry time by changing the data in the table and before the current F0010 cache expires do what needs to be done in the previous period. To me this is a very risky way of making these types of changes.

    When we need to do this we wait till the quiet part of the day and re-open the previous period and do what is needed and then change it back again. There are limited people who can approve batches to post.

    Other options are mentioned in https://www.jdelist.com/vb4/showthread.php?t=51229
    Thanks, Peter

    "Give a person a fish, feed them for a day, teach them how to fish, feed them for a lifetime."

    E9.1 TR9.1.2.1, Enterprise Server: Sun, Database Server: Sun, Oracle DB: 11g, Weblogic.
    Create!form 7

  4. #4
    Senior Member peterbruce's Avatar
    Join Date
    Jan 2004
    Location
    NSW Australia
    Posts
    2,164
    Rauf,

    I found out that the F0010 may be cached in the JAS service cache.
    Thanks, Peter

    "Give a person a fish, feed them for a day, teach them how to fish, feed them for a lifetime."

    E9.1 TR9.1.2.1, Enterprise Server: Sun, Database Server: Sun, Oracle DB: 11g, Weblogic.
    Create!form 7

  5. #5
    Member Rauf's Avatar
    Join Date
    Jan 2012
    Location
    Kerala, India
    Posts
    724
    Thanks Peter and Ice Cube.

    Yes. Peter.
    It always cache in the JAS also. But please let me try the WSJ method.
    RAUF
    JDE Techno-Functional
    JDE E1 8.12 | TR 8.96.40 | Windows XP SP 3

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.