DBA Data[Home] [Help]

APPS.HR_UTILITY dependencies on FND_MESSAGE

Line 118: the message on the FND message stack.

114: name is formed as 'PAY'.
115:
116: D Kerr 22-SEP-1997 Fix to get_message to ensure it works in
117: the same way as R10. ie calling it still leaves
118: the message on the FND message stack.
119:
120: D Kerr 27-JUL-1997 R11 changes.
121: WARNING : Not compatible with R10
122:

Line 125: or both. The code now uses FND_MESSAGE routines rather than

121: WARNING : Not compatible with R10
122:
123: Removed most of the code from message routines as it
124: was either accessing obsoleted tables or was non NLS compliant
125: or both. The code now uses FND_MESSAGE routines rather than
126: accessing tables directly. Package globals are still maintained
127: for use in get_message and get_message_details.
128:
129: Removed : show_error, get_token_details.

Line 133: fnd_new_messages and then fnd_messages

129: Removed : show_error, get_token_details.
130:
131: 110.1 10-JUL-1997 M.J.Hoyes Bug 513048. Switched the cursors in the
132: 10.7 version 40.14 set_message procedure to validate against
133: fnd_new_messages and then fnd_messages
134: rather than vice versa. Re coded the
135: set message token procedure to use cursors
136: rather than PLSQL blocks and switched the
137: first table to drive off to fnd_new_messages.

Line 148: in fnd_messages. Behave as normal if not in

144: 2. read_trace_pipe routine moves the pipe
145: handling code from PYUPIP to this package.
146: T Mathers 18-Aug-1996 Changed message and message token code
147: to use fnd_new_messages id there is no row
148: in fnd_messages. Behave as normal if not in
149: both.
150: D Kerr 08-Jul-1996 Set a message in the case of pipe timeout
151: D Kerr 03-Jul-1996 Added timeout parameter to send_message calls
152: in trace and set_location.

Line 156: for fnd_messages cursor in set_message

152: in trace and set_location.
153: D Harris 24-Jun-1995 merged trace with set_location to improve
154: performance.
155: T Mathers 28-Jun-1995 Added joins to fnd_current_language_view
156: for fnd_messages cursor in set_message
157: and set_message_token. WWBUG#288067
158: D Harris 22-Jun-1995 Increased g_message_text from 240 to
159: 2048 (max length required for use
160: in dbms_standard.raise_application_error).

Line 161: P Gowers 28-NOV-1994 G1682: Always call fnd_message.set_name()

157: and set_message_token. WWBUG#288067
158: D Harris 22-Jun-1995 Increased g_message_text from 240 to
159: 2048 (max length required for use
160: in dbms_standard.raise_application_error).
161: P Gowers 28-NOV-1994 G1682: Always call fnd_message.set_name()
162: D Harris 07-OCT-1994 Increment length of set_location pipe
163: details from 40 to 72.
164: D Harris 16-SEP-1993 Changes made for 10x compatibility for
165: forms 4 and aol api's.

Line 208: g_msg_prefix varchar2(30) := fnd_message.get_string('FND','AFDICT_APP_PREFIX');

204: -- These variables are needed to support get_message and get_message_details
205: g_message_name varchar2(30);
206: g_message_number number;
207: g_message_applid number;
208: g_msg_prefix varchar2(30) := fnd_message.get_string('FND','AFDICT_APP_PREFIX');
209:
210: -- NAME
211: --
212: -- who_called_me

Line 391: -- null value but instead raises an ORA-1400 with no fnd_message

387: who_called_me(l_caller,4);
388:
389: -- A couple of modules call hr_trace('') in order to separate groups of
390: -- related trace() calls. As it stands fnd_log.string won't accept a
391: -- null value but instead raises an ORA-1400 with no fnd_message
392: -- context back to forms. fnd_log.string will accept a ' ' however
393: -- it seems risky to leave that in case the routine rtrims. For now
394: -- we pass a '.' and may file bug.
395:

Line 416: fnd_message.set_name('PAY','HR_51356_UTILITY_PIPE_TIMEOUT');

412: if ( l_x <> 0 ) then
413:
414: -- Don't call other functions here if they call trace
415: -- Set a message so that the error is visible in forms.
416: fnd_message.set_name('PAY','HR_51356_UTILITY_PIPE_TIMEOUT');
417: fnd_message.raise_error ;
418:
419: end if;
420:

Line 417: fnd_message.raise_error ;

413:
414: -- Don't call other functions here if they call trace
415: -- Set a message so that the error is visible in forms.
416: fnd_message.set_name('PAY','HR_51356_UTILITY_PIPE_TIMEOUT');
417: fnd_message.raise_error ;
418:
419: end if;
420:
421: elsif g_trace_dest = 'DBMS_OUTPUT' then

Line 634: fnd_message.set_name('PAY','HR_51356_UTILITY_PIPE_TIMEOUT');

630: ,timeout => PIPE_PUT_TIMEOUT);
631: IF (hr_utility.g_sl_x <> 0) THEN
632: -- Don't call other functions here if they call trace
633: -- Set a message so that the error is visible in forms.
634: fnd_message.set_name('PAY','HR_51356_UTILITY_PIPE_TIMEOUT');
635: fnd_message.raise_error ;
636: END IF;
637: ELSIF hr_utility.g_trace_dest = 'DBMS_OUTPUT' THEN
638: dbms_output.put_line(hr_utility.g_sl_mess_text);

Line 635: fnd_message.raise_error ;

631: IF (hr_utility.g_sl_x <> 0) THEN
632: -- Don't call other functions here if they call trace
633: -- Set a message so that the error is visible in forms.
634: fnd_message.set_name('PAY','HR_51356_UTILITY_PIPE_TIMEOUT');
635: fnd_message.raise_error ;
636: END IF;
637: ELSIF hr_utility.g_trace_dest = 'DBMS_OUTPUT' THEN
638: dbms_output.put_line(hr_utility.g_sl_mess_text);
639: --

Line 730: fnd_message.clear ;

726: begin
727:
728: hr_utility.g_message_number := null;
729: hr_utility.g_message_name := null;
730: fnd_message.clear ;
731:
732: end clear_message;
733: -------------------------------- set_message --------------------------------
734: /*

Line 738: Calls FND_MESSAGE.SET_NAME and sets the message name and application id as

734: /*
735: NAME
736: set_message
737: DESCRIPTION
738: Calls FND_MESSAGE.SET_NAME and sets the message name and application id as
739: package globals.
740:
741: */
742: procedure set_message (applid in number, l_message_name in varchar2) is

Line 749: fnd_message.set_name( hr_general.get_application_short_name(applid),

745:
746: g_message_name := l_message_name;
747: g_message_applid := applid;
748: --
749: fnd_message.set_name( hr_general.get_application_short_name(applid),
750: l_message_name );
751:
752: end set_message;
753: --

Line 765: fnd_message.set_token(l_token_name, l_token_value, translate => false );

761: procedure set_message_token (l_token_name in varchar2,
762: l_token_value in varchar2) is
763: begin
764:
765: fnd_message.set_token(l_token_name, l_token_value, translate => false );
766:
767: end set_message_token;
768: ------------------------------ set_message_token ------------------------------
769: /*

Line 774: Note that the application id passed a parameter is ignored. The FND_MESSAGE

770: NAME
771: set_message_token
772: DESCRIPTION
773: Overloaded: Sets up a translated message token
774: Note that the application id passed a parameter is ignored. The FND_MESSAGE
775: routine uses the application of the last message that was set.
776: */
777: procedure set_message_token (l_applid in number,
778: l_token_name in varchar2,

Line 783: fnd_message.set_token(l_token_name,l_token_message, translate => true );

779: l_token_message in varchar2)
780: is
781: begin
782:
783: fnd_message.set_token(l_token_name,l_token_message, translate => true );
784:
785: end set_message_token;
786: -------------------------------- get_message --------------------------------
787: /*

Line 792: FND_MESSAGE.GET in that it prefixes the text with 'APP-nnnnn' where

788: NAME
789: get_message
790: DESCRIPTION
791: Assembles the current message text and returns it. This is different to
792: FND_MESSAGE.GET in that it prefixes the text with 'APP-nnnnn' where
793: nnnnn is the zero padded message number
794:
795: Note that after calling the FND get routines we put the message back
796: onto the 'stack' so that the routine can be called more than once.

Line 814: l_msg_encoded := fnd_message.get_encoded ;

810:
811: -- After retrieving the message it mut be set again so that
812: -- subsequent calls to 'get' routines work.
813: --
814: l_msg_encoded := fnd_message.get_encoded ;
815: fnd_message.set_encoded(l_msg_encoded);
816:
817: if ( l_msg_encoded is null )
818: then

Line 815: fnd_message.set_encoded(l_msg_encoded);

811: -- After retrieving the message it mut be set again so that
812: -- subsequent calls to 'get' routines work.
813: --
814: l_msg_encoded := fnd_message.get_encoded ;
815: fnd_message.set_encoded(l_msg_encoded);
816:
817: if ( l_msg_encoded is null )
818: then
819: return null;

Line 831: l_msg_number := fnd_message.get_number(l_msg_appl,l_msg_name);

827: l_msg_appl := substrb(l_msg_encoded,1,l_pos1 -1 );
828: l_msg_name := substrb(l_msg_encoded,
829: l_pos1 +1,
830: l_pos2 - l_pos1 - 1);
831: l_msg_number := fnd_message.get_number(l_msg_appl,l_msg_name);
832:
833:
834: if ( l_msg_number is null or l_msg_number = 0 ) then
835:

Line 836: l_msg_text := fnd_message.get ;

832:
833:
834: if ( l_msg_number is null or l_msg_number = 0 ) then
835:
836: l_msg_text := fnd_message.get ;
837:
838: else
839:
840: -- Assemble the message in the form 'APP-nnnnn : message text'

Line 843: ||fnd_message.get;

839:
840: -- Assemble the message in the form 'APP-nnnnn : message text'
841: -- The number of zeros is AFD_MSG_NUM_BYTES
842: l_msg_text := g_msg_prefix||'-'||to_char(l_msg_number,'FM00000')||' '
843: ||fnd_message.get;
844:
845: end if;
846:
847: -- Put the message back so that it is available in other contexts

Line 848: fnd_message.set_encoded(l_msg_encoded);

844:
845: end if;
846:
847: -- Put the message back so that it is available in other contexts
848: fnd_message.set_encoded(l_msg_encoded);
849:
850: return(l_msg_text) ;
851:
852: end get_message;

Line 859: Ideally would use FND_MESSAGE.RETRIEVE but this is AOL only at present.

855: NAME
856: get_message_details
857: DESCRIPTION
858: Gets the name and the application short name of the message last set
859: Ideally would use FND_MESSAGE.RETRIEVE but this is AOL only at present.
860: */
861: procedure get_message_details (msg_name in out nocopy varchar2,
862: msg_appl in out nocopy varchar2) is
863: begin