Compilation errors when compiling qmslib*.pll against a 10g database

Question

In some cases compiling qmslib50.pll or qmslib65.pll with Forms 6.0, Forms 6i or
Forms 9i gives errors like
PL/SQL ERROR 201 at line 47, column 36
identifier 'HIL_MESSAGE.MESSAGE_RECTYPE' must be declared
or
PL/SQL ERROR 905 at line 47, column 36
object'HST65.HIL_MESSAGE' is invalid
The cause of this is in procedure hil_message.get_message where argument P_LANGUAGE is defaulted to a value collected from hil_profile.get_profile_value ('LANGUAGE', user)). This confuses the forms compiler.
The workaround for this problem is to replace the call to HIL_PROFILE by default value NULL and to change the code in the procedure,
as shown below.
procedure Get_Message ( p_errorrec in out hil_message.message_rectype
, p_errcode in varchar2 := null
, p_constraint in varchar2 := null
, p_language in varchar2 := NULL
is
-- Purpose returns all error/message information from qms_message_properties
-- and qms_message_text table for a specified error message or
-- constraint name.
-- Either the error code (p_errcode) or the constraint name must be specified
-- Usage Parameters
-- p_errorrec : returns the error/message information in a PL/SQL record
-- p_errcode : error/message code
-- p_constraint : constraint name
-- p_language : language in which the message text is required
-- Remarks -
l_language varchar2(3);
begin
if p_language is null
then
-- get the value for the language from HIL_PROFILE
l_language := hil_profile.get_profile_value ('LANGUAGE', user) ;
else
-- use the parameter value
l_language := p_language;
end if;
qms_message.Get_Message ( p_errorrec
, p_errcode
, p_constraint
, l_language); -- use l_language instead of p_language
end Get_Message;

Answer 1

HIL_MESSAGE is a database package under headstart, Headstart package owner.
Check the status of the package. Recompile the package or recreate it with the script provided or generate the ddl from designer under qms65 application under headstart.