E1: 44H: P44H601 | W44H601C Enter Bids Header Does Not Allow the HBAREA Field To Use the Wildcard Asterisk Search (Doc ID 3042745.1)

Last updated on JANUARY 03, 2025

Applies to:

Symptoms

Enter an asterisk into the Area (alias HBAREA) field on form W44H601C (Enter Bids) instead of the blank value, and press find, the application issues the error 0003: 'Blanks Invalid'.

Steps To Duplicate: 
1. Navigate to menu G44H23 and select Enter Bids (P44H601). This opens form W44H601A version ZJDE0001.
2. On form W44H601A, the Area (alias HBAREA) field is populated with the wildcard / asterisk '*'. (Note: In the data dictionary, HBAREA has an edit rule on the Edit Rule tab of UDC 00 / 05, where that UDC has one of the values as Codes = *, Description = All Codes - Search Only)
3. On form W44H601A, take the Form Exit to "Bid Header Browse" which opens up form W44H601C. When Form W44H601C loads, the Bid Number / Type / Co fields each load with *. However, the Area (HBAREA) field does not load with an asterisk and is currently a blank field.
4. At this point, enter an asterisk into the Area (alias HBAREA) field on form W44H601C instead of the blank value, and press find, the application issues the error: 'Blanks Invalid'.
5. Exit the P44H601 to the menu. On the P44H601 processing options, change the Defaults tab option # 1 Area = *. That is, input an asterisk into the processing option #1 on the Defaults tab of the P44H601 for Area.
6. Repeat step 3, and the W44H601C now loads with an asterisk in the HBAREA field of form W44H601C, press find, and receive the 'Blanks Invalid' error.

Cause

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