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

Memo Number format - why 11 Alphanumeric?

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 Konda R (Qantas) on 2011-06-02 01:10:36 Back to Topics

Memo Number format - why 11 Alphanumeric?

re Passenger Rejection Memo Number and Billing/Credit  Memo Number

Memo Numbers have been defined as 11 Alphanumeric for IS-IDEC.  What is the background for this choice in format?

During our SIS development we have found this has created challenges because of length and attribute. 

Many pax revenue and associated systems use a 10 Numeric field for ticket number, so the 11Alphanumeric format for Memo Number means Memo Number can not share the ticket number field.

Unlike ticket number, Memos are not governed by resolutions, so there is no standard for memo numbers across the industry.  The 11Alphanumeric format for Memo numbers is going to cause issues for many carrier's systems, especially for inward billings. 

I think a 10 Numeric format for Memo Number would be much simpler for many carriers' systems. 

What is the process for requesting a change in specification?

Konda/QF

Replied by Ashley H on 2011-06-03 10:00:27

Dear Konda,

 

During the WG meetings, the format of the BM number was discussed. The first proposal was indeed 10N. But then the Cargo WG requested 11A/N and also the RAM at that time was stating a format of 11.

 

As the fields between Cargo and Pax need to be aligned, the WGs decided to have in both record structures (Pax and Cargo) 11 A/N.

 

This topic will be brought to the attention of the RAWG.

Best regards


From:
Posted: Thursday, June 02, 2011 1:10 AM
Subject: Memo Number format - why 11 Alphanumeric?

re Passenger Rejection Memo Number and Billing/Credit  Memo Number

Memo Numbers have been defined as 11 Alphanumeric for IS-IDEC.  What is the background for this choice in format?

During our SIS development we have found this has created challenges because of length and attribute. 

Many pax revenue and associated systems use a 10 Numeric field for ticket number, so the 11Alphanumeric format for Memo Number means Memo Number can not share the ticket number field.

Unlike ticket number, Memos are not governed by resolutions, so there is no standard for memo numbers across the industry.  The 11Alphanumeric format for Memo numbers is going to cause issues for many carrier's systems, especially for inward billings. 

I think a 10 Numeric format for Memo Number would be much simpler for many carriers' systems. 

What is the process for requesting a change in specification?

Konda/QF

 
ADVERTISEMENT


Additional information

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