FpML Issues Tracker

162: Error codes for MessageRejected should be defined as coding scheme

February 15, 2006

Status

closed

Severity

Minor

Reproducibility

Always

Summary

The Messaging Architecture sections defines a list of error codes to be used in a MessageRejected message. However a coding scheme containing the error codes is not defined in FpML. The reasonCode element is defined as a token.

Notes:

mgratacos

02/15/06 10:23 am

The Architecture Working Group decided to make the error codes a scheme. The reasonCode element (within MessageRejected) will use this new scheme instead of being defined as xsd:token.

Leave an update

You must be logged in to post an update.

Report an Issue

The FpML Issues Tracker is designed to facilitate public interaction in the standard.

By registering you will be able to submit corrections and comments, generate reports, and view the complete issues archive for FpML.

Report Issue

Recent Open Issues

March 13, 2025

[FpML 6] inflationRateIndex wrong default scheme

February 26, 2025

Request to add a new code value to the businessCenterScheme to correspond to the proposed ISDA defined term for “New Zealand Business Day” being introduced in the 2021 ISDA Interest Rate Derivatives Definitions

February 25, 2025

FpML Attributes for Non Deliverable Cross currency swaps

February 25, 2025

Request to add a new code value (e.g. ILS-SHIR) to the businessCenterScheme to correspond to the SHIR Publication Calendar Days

All Issues