Financial Management provides a mechanism for error handling that offers the following benefits:
Error message localization – Error messages will be translated into whatever languages has been Financial Management.
Centralized location – Previous Financial Management releases stored error messages in the event logs of application servers. To overcome the limitations of that approach, error messages are now stored in the database.
Dynamic error messages – For certain errors, the specific item involved in the error is dynamically specified. For example, instead of a vague error message that says “invalid account”, a dynamic error message would specify the name of the invalid account. For example, if the invalid account name was Sales1, the message would read something like this:
Sales1 is not a valid account.
Additional technical information – To aid in debugging, technical information such as the source file and the line number are returned in addition to the traditional user-readable error messages.
To accomplish these objectives, Financial Management error handling works as follows:
In the IErrorInfo interface, Financial Management returns an XML string as the error description, and the HRESULT as the error number. The XML string contains a wealth of information that is not normally included in an error description.
You pass the XML string and the HRESULT to the HsvResourceManager object, which returns the applicable error message strings.