Skip to main content

Test Home
You & IATA

Search

You are here: Home » Services » Financial Services » Simplified Interline Settlement » SIS Forums
  • Print this page
  • Share this page

Numeric fields on MISC XML

This is a read-only copy of the discussions. To view the original, where you can reply, go here. For info on how to log in, please see the instructions.

Created by Peter W on 2010-10-07 03:52:44 Back to Topics

Numeric fields on MISC XML

Where a numeric field is defined as say 18,4 (such as unit price), do you expect 4 digits after the decimal point.
for example if the unit price was 10.99 (as our system holds values such as this to 2 decimal places), would we populate this as 10.9900 or just 10.99
Replied by James S on 2010-10-07 06:51:56
Hi.
 
The number of digits after the decimal point (a constraining factor called "fractionDigits" in the XML standard) is the maximum number of digits that might be provided.  So you could provide (and would have to accept, when being billed) 10.9900, 10.990, or 10.99.
From your previous question, I get the sense that you're creating the XML data file manually, one element at a time. Obviously, every carrier has different systems/constraints, but I'd suggest you might look into an XML library. Many languages have these available, and you can provide a hash table / array / etc, and let the library take care of creating the XML as per XML spec. (After all, the fractionDigits is just part of the XML spec.)
 
James
Replied by Peter W (British Airways) on 2010-10-07 08:12:52
James,
Thanks for that. We are using some trick application where we import the XSD into the application & then map our data into the correct fields, unfortunately this software isn't fantastic at handling the data types, so as you say I am having to make sure each field is the correct format


From: IATA
Posted: Thursday, October 07, 2010 6:51 AM
Subject: Numeric fields on MISC XML

Hi.
 
The number of digits after the decimal point (a constraining factor called "fractionDigits" in the XML standard) is the maximum number of digits that might be provided.  So you could provide (and would have to accept, when being billed) 10.9900, 10.990, or 10.99.
From your previous question, I get the sense that you're creating the XML data file manually, one element at a time. Obviously, every carrier has different systems/constraints, but I'd suggest you might look into an XML library. Many languages have these available, and you can provide a hash table / array / etc, and let the library take care of creating the XML as per XML spec. (After all, the fractionDigits is just part of the XML spec.)
 
James
 
ADVERTISEMENT


Additional information

© International Air Transport Association (IATA) 2014. All rights reserved.