Format of Error Codes With Parameters

The format of error codes can include parameters and the scope, log severity level, subsystem, and the unique error number.

Additionally, the system message codes might include parameters, such as:

Scope.Subsystem.Name={0}000110020789{3}

The format used is parsed and described in the same manner as messages without parameters.

For example, this is an EDIFACT deenveloping system message with a parameter:

EDI.EDI_EDIFACTDEENVELOPING.EDI.EDI_EDIFACTDEENVELOPING.
DEB_DeenvelopeEDIFACTServiceImpl_ExceptionFindingContract={0}000520040010{3}

The format used in this message (to the left of the equals sign) is parsed and described in the following table:

Parameter	Description
Scope	EDI
Subsystem	EDI_EDIFACTDEENVELOPING (the EDIFACT deenveloping subsystem, which is a subset of EDI in the system)
Name	EDI.EDI_EDIFACTDEENVELOPING.DEB_DeenvelopeEDIFACTServiceImpl_Exception FindingContract This is the name of the error message which, when translated into the system log, reads `[DeenvelopeEDIFACTServiceImpl] Exception finding contract {0}` Note: The first parameter [DeenvelopeEDIFACTServiceImpl], indicates the service implementation. The second parameter {0}, indicates the specific contract.

The format used is in this message (to the right of the equals sign) parsed and described in the following table:

Number of Error Code Number Digits	Description
1 - 4	The first four digits (0005) specify the scope of the component (EDI).
5	The next one digit (2) specifies the log severity level, indicating that this is a debug message (DEB).
6 - 8	The next three digits (004) specify the subsystem of the component (EDI_EDIFACTDEENVELOPING).
9 -12	The next four digits (0001) specify the unique error number (this number is unique with the entire error code format.