OracleEBSLOV Speed Optimization

OracleEBSLOV Speed Optimization

I. symptom

When the SQL statements of our EBS LOV are complex, or the data volume is large, the LOV pop-up display speed, or directly fill in the ticket number and move it to another input box (when the Validate from List is opened) the Busy status is displayed. You need to wait!

Ii. Analysis

1. Click the LOV button to bring up the selection box:

Query all data of lov SQL directly. When the data volume is large or the SQL is complex, query is slow + data transmission is slow.

2. Fill in the ticket number and move the cursor to another input box:
The Forms interface is stupid. First query all the data and then filter the ticket number to determine whether the ticket number exists or whether there is a duplicate ticket number.

Ii. Optimization Methods

Set the attribute Filter Before Display: Yes of LOV.

Result 1: No query is automatically performed when LOV is enabled. Wait for the user to enter the query conditions. % indicates to query all

Result 2: The input ticket number is fast when it is moved to another location. (Originally: Query all data first, and then filter the ticket number. Now: directly import the document number into SQL)