JDE A/R Sales Order Inquiry may be getting slower over years

Guideline of how to tackle this issue :

a) what is the significant action the user perform on SO inquiry?  i.e. just put order number and click find button?

(b) what the form name of P4210 the user stay

(c) had you try to reproduce and this is reproducible? only specific user(s) or else?

(d) did you capture jdedebug.log on your fat client?

(e) did you capture web server log on your web server?

(d) Is there any Zombie Kernel or Batch Process or Web Server CallObject Errors? or any error log captured from other system (i.e. SQL server or Windows server)

Some attempts :

(1) re-add  indexes into table F4201 and F4211 using OMW - Table Operation

(2) enable sales update to purge to sales order history records  

To enable R42800 Sales Update to purge sales order records from the open files (F4201/F4211) to history (F42019/F42119), go to Tab 2-Update and ensure the following two processing options are BLANK:

• 6. Purge to Sales Detail History (F42119)
• 7. Purge to Sales Header History (F42109)

In this instance, "purge" really means "move".  Since SO Inquiry queries against the open and history files, you may still experience slowness when performing queries against closed orders.  You may also want to consider deleting or archiving records from the history files.  While Oracle has UBEs to do delete records, they do not maintain the referential integrity between files.  (For example, the UBEs would let you delete sales records when the AR is still open.)

The P4210 and P42101 Sales Order Entry applications can inquire on open records (F4201/F4211) and/or closed records (F42019/F42119).  However, the P43070 Held Order Release application can only inquire on records in the F4201/F4211.

Hope that helps....