Figure 2.1 Define Messages

Type- Use the message type to classify your messages. The message type does not affect how your messages can be called in your code.

In Oracle Applications, the message type is used to help translators translate messages within length expansion constraints that vary by message type. For certain message types, this form enforces message byte length limits smaller than 1800. The message length limits (in bytes) are 60 for Menu Entry, 250 for Hint, and 80 for Title (note that these limits are for translated messages, so messages in English should be 30% shorter if they will be translated).

Maximum Length - In Oracle Applications, the maximum length (in bytes) is used to help translators translate messages within length expansion constraints imposed by the form or program that uses the message. Specifying a maximum length is particularly important where the expansion constraint is tighter than would otherwise be expected for a particular type of message. If your message is in English, the maximum length you specify should be at least 30% longer than your actual English message to allow for expansion during translation.

Figure 2.2 Define Messages

Description - You should enter information in this field that would help explain the context of this message to translators. This field is required if the message is of type Token or Other.

After defining your message you need to run “Generate Messages” program to build your message file. Your new messages take effect as soon as your concurrent request finishes successfully and you have placed the new file in the appropriate directories.

Navigation – Application Developer->Other->Requests->Run

Figure 3 Running Generate messages Navigation

Figure 4 Running Generate messages parameters

Next Page: Oracle Apps Message Dictionary - Page 3