No commit-message (FRM-40400) == Bug in Headstart

Question

Hello,
On committing on or more business rules are violated the 'message-window' appear.
After correcting the errors and committing the changes i'm not getting the usual
'commit-message' (FRM-40400). This only happens after on or more business rules are violated.
This is caused by a bug in the procedure 'QMS$FORMS_ERRORS.PUSH'. Below the solution i have implemented (the complete procedure is displayed). I'm using version 6.5.4.0 of the library 'qmslib65.pll.
PROCEDURE Push
( p_msg IN VARCHAR2
, p_error IN VARCHAR2 DEFAULT 'I'
, p_msg_type IN VARCHAR2 DEFAULT ''
, p_msgid IN NUMBER DEFAULT 0
, p_loc IN VARCHAR2 DEFAULT '') IS
-- Purpose Show message to the end-user, standard procedure for the Oracle Forms
-- Generator of Designer/2000 to pass the display and handling of a message
-- to a user created procedure.
-- Usage Called by the Oracle Forms Generator code
-- Parameters : msg Text message
-- error ERRor or WARNing
-- msg_type ORA, API or user TLA
-- msg_id Id of message
-- loc Location where error occured
-- Remarks
v_msg VARCHAR2(2000) := p_msg;
v_error VARCHAR2(2000) := p_error;
v_servermsg VARCHAR2(2000) := DBMS_ERROR_TEXT;
l_empty_errorrec hil_Message.message_rectype;
BEGIN
IF p_msgid != 0
THEN
g_errorrec.severity := p_error;
ELSIF ((SUBSTR (v_msg, 1, 11) = 'API Error: ')) OR
((INSTR (v_servermsg, 'ORA-20999') <> 0) AND (v_msg IS NULL)) OR
(INSTR (v_msg, 'ORA-20999') <> 0)
THEN
-- error returned from the API, just display no further action required ?
HandleServerAPIError (p_msg);
-- M. Kappel
/* 11-apr-2001
- Allow check of v_servermsg even if v_msg contains data.
- With new-style cdm ruleframe, v_msg contains 'ORA-20998'.
We never looked at v_servermsg because v_msg was not null.
- With old-style database trigger business logic, v_msg contains only text.
If we still never look at v_servermsg, we don't identify that the error is
a 20998 and therefore we raise an alert 'Transaction Failed' instead of
showing the 'Errors in this Transaction' window.
-- ELSIF ((INSTR (v_servermsg, 'ORA-20998') <> 0) AND (v_msg IS NULL)) OR
-- (INSTR (v_msg, 'ORA-20998') <> 0)
-- THEN
On committing on or more business rules are violated the 'message-window' appear.
After correcting the errors and committing the changes i'm not getting the usual
'commit-message' (FRM-40400). This only happens after on or more business rules are violated.
When one or more business rules are violated application error ORA-20998 is raised. To
detect this DBMS_ERROR_TEXT is used ==> DBMS_ERROR_TEXT contains ALWAYS the text of the
LAST (dbms-)error (the text contains 'ORA-20998').
Even when no business rules are violated it's possible that DBMS_ERROR_TEXT contains 'ORA-20998'.
In that case no FRM-, MNU-, PLS-, SRW-, ORA- or REP-messages are displayed, because the error is
treated as a voilation of one or more business rules. To avoid this 'v_error = E' is added to the IF-clause:
when one or more business rule are violated this procedure is called to display an error (p_error ==> E);
for displaying the FRM-, MNU-, PLS-, SRW-, ORA- and REP-messages this procedure is called to display an
information (p_error ==> I).
When Designer generates code to validate p.e. check-constraints it will call this procedure too. See the example
below:
IF (:FUNCTIES.MIN_LEEFTIJD < :FUNCTIES.MAX_LEEFTIJD) THEN
NULL;
ELSE
qms$forms_errors.push('CBB-00219', 'E', 'OFG', 0);
qms$forms_errors.raise_failure;
END IF;
In this case the procedure is called to display an error. To avoid that the error is incorecctly treated as a
violation of one or more business rules '(p_msg_type != 'OFG' or p_msg_type is null)' is added to the IF-clause.
ELSIF v_error = 'E'
AND (p_msg_type != 'OFG' or p_msg_type is null)
AND ( INSTR (v_servermsg, 'ORA-20998') <> 0
OR INSTR (v_msg, 'ORA-20998') <> 0
THEN
HandleServerApplError (p_msg);
-- error returned from the API, just display no further action required ?
ELSIF ((INSTR (v_servermsg, 'ORA-20000') <> 0) AND (v_msg IS NULL)) OR
(INSTR (v_msg, 'ORA-20000') <> 0)
THEN
-- error was raised by old Headstart code with raise_application_error
-- strip ora-20000 : , check if code (get message) or message
HandleOldHeadstart (v_servermsg);
ELSIF (SUBSTR (v_msg, 1, 3) IN ('FRM', 'MNU', 'PLS', 'SRW', 'ORA', 'REP'))
THEN
HandleOracleError (v_msg, v_error);
ELSE
     HandleApplError(v_msg, v_error);
END IF;
Display_Error (g_errorrec);
g_errorrec := l_empty_errorrec;
END Push;

Answer 1

you can create a KEY-COMMIT form level trigger with the following :
declare
msglvl varchar2(3) := :system.message_level ;
begin
:system.message_level := 5 ;
commit_form ;
:system.message_level := msglvl ;
end ;
or put instruction : clear_message; before the commit_form ;