Show TOC

Background documentationMessage ID Locate this document in the navigation structure

 

Message ID is a unique identifier assigned to each log/trace message that is generated in AS Java. The uniqueness of the concept does not allow two identical log/trace entries to have one and the same message ID assigned. One entry (event) can be found more than once in the log/trace files but each time it has the same message ID.

Each message ID leads you to a single troubleshooting page, which:

  • Gives detailed information about the problem occurred.

  • Explains the possible reasons that have caused the problem.

  • Provides next steps you can take to resolve the problem.

  • Provides additional information (if any).

Structure

A message ID represents a string as follows:

[prefix].[range][number], where:

prefix – a meaningful word, abbreviation or a combination of symbols.

range – a two-symboled combination that consists of a number and a lowercase Latin alphabet character.

number – a number from 0 to 9999. The first number is ‘0000’ and the last possible number in a range is ‘9999’.

Note Note

The prefix itself consists of [vendor].[product name].[additional prefix]. Example: com.sap.ASJ.web

  • vendor (com.sap) – follows the rules for indicating the vendor in Java specification.

  • product name (ASJ) – consists of 2–3 uppercase Latin alphabet letters indicating the SAP product.

  • additional prefix (web) – consists of 3-10 lowercase Latin alphabet letters, including the Arabic numbers and the symbol “_” as a delimiter. This combination is a meaningful description of the AS Java component (service, library, interface, manager or application), which produces the log message.

End of the note.

Example for a complete message ID string:com.sap.ASJ.web.0a0067

Features

  • The message IDs are published and can be accessed by both internal and external SAP customers.

  • You can perform an online search for a particular message ID in a search engine.

  • Each message ID combination is unique and once published it is locked (reserved) and cannot be used by another log message.

More Information

You can see the message IDs of many Java log records via, for example, the Log Viewer tool.

For more information, see Log Viewer