APPS.NTN dependencies on FND_MESSAGE

Line 64: * We should be selecting from the fnd message dictionary api's.

60: *
61: * This causes too many rows to be returned in a translated install
62: * since we are not joining on language_code. Thus in any translated
63: * db notifications were not working.
64: * We should be selecting from the fnd message dictionary api's.
65: * So using the fnd_message.get_string api. It returns the translated
66: * message or null if the message can't be found. The null is what
67: * we need to check for.
68: */

Line 65: * So using the fnd_message.get_string api. It returns the translated

61: * This causes too many rows to be returned in a translated install
62: * since we are not joining on language_code. Thus in any translated
63: * db notifications were not working.
64: * We should be selecting from the fnd message dictionary api's.
65: * So using the fnd_message.get_string api. It returns the translated
66: * message or null if the message can't be found. The null is what
67: * we need to check for.
68: */
69:

Line 78: xxx_msg := fnd_message.get_string(x_app_short_name, p_message_name);

74: where application_id = p_application_id;
75:
76: dbms_output.put_line('Application short name found');
77:
78: xxx_msg := fnd_message.get_string(x_app_short_name, p_message_name);
79: x_progress:='020';
80:
81: dbms_output.put_line('xxx_msg =' || xxx_msg);
82: