Oracle Forms Personalization – Validating a Record Input

Introduction: 

The waybill number is a key reference for tracking shipments. To avoid errors and maintain consistency, the field will now be restricted to accept only alphanumeric characters and dashes.

Cause of the issue:

Currently, the waybill number field does not restrict input, allowing special characters, symbols, or extra spaces to be entered. These often result from manual entry mistakes or copying from unformatted sources. Such inconsistencies cause issues in shipment tracking, system matching, and data processing, leading to delays and additional manual corrections.

How do we solve:

Data base steps:

Step 1: Create a function that will return only the alphanumeric and dashes

CREATE OR REPLACE FUNCTION XX_waybill_number_update (
p_waybill_number IN VARCHAR2
)
RETURN VARCHAR2
AS
lc_waybill_number VARCHAR2(150);
BEGIN
SELECT REGEXP_REPLACE(p_waybill_number, ‘[^a-zA-Z0-9-]’, ”)
INTO lc_waybill_number
FROM dual;

RETURN lc_waybill_number;

EXCEPTION
WHEN OTHERS THEN
RETURN NULL;
END xx_waybill_number_update;

Application Steps

Step 1: Login to EBS Application>> Navigate to Shipping responsibility >> Pick release form.

Step 2: Click on Appointments

Step 3: To validate the input record Place the cursor on waybill >> Help >> Diagnostics >> Custom Code >> Personalize.

Step 4: Create a sequence >> To validate the waybill number field upon saving

4.1 Actions page

Step 5: Create a sequence to validate the waybill number field when you hit tab.

5.1 Actions Page

Step 6: Click On tools >> Validate all.

Step 7: Save and close

Conclusion:

Implementing this validation will standardize the waybill number format across all entries, ensuring cleaner data, faster processing, and fewer tracking errors. By restricting inputs to only alphanumeric characters and dashes, we enhance data integrity, reduce operational issues, and improve the overall efficiency of shipment management.

 

Recent Posts