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

Excess Baggage source code during migration

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 2010-09-08 22:16:42 Back to Topics

Excess Baggage source code during migration

Can you clarify what source code will be populated on the old IDEC for excess baggage during migration?
 
1) non-migrated billing carrier should use s/c 01 or separate invoice?
 
Will IS transform this to s/c 25 on old IDEC output for migrated billed carriers?
 
2) migrated billing carrier should use s/c 25 on IS-IDEC/IS-XML.

What s/c will be provided on old-IDEC output to non-migrated billed carrier?
Replied by James S on 2010-09-20 09:20:57
Hi.
 
There will be no conversion of source codes from old to new IDEC or vice versa.
 
So:
 
  1. Non migrated should use SC 01 as today. Migrated carriers will receive an old IDEC file with SC 01.
  2. Migrated carriers should use SC 25. Non-migrated carriers will receive an old IDEC (down-converted from IS-IDEC/IS-XML) with SC 25.

Please note that field 15 of the old IDEC invoice header record (Currency Conversion Indicator) will be used to flag down-converted old IDECs. Thus, your system will be able to identify these situations.

James


From:
Posted: Wednesday, September 08, 2010 10:16 PM
Subject: Excess Baggage source code during migration

Can you clarify what source code will be populated on the old IDEC for excess baggage during migration?
 
1) non-migrated billing carrier should use s/c 01 or separate invoice?
 
Will IS transform this to s/c 25 on old IDEC output for migrated billed carriers?
 
2) migrated billing carrier should use s/c 25 on IS-IDEC/IS-XML.

What s/c will be provided on old-IDEC output to non-migrated billed carrier?
Replied by Konda R (Qantas) on 2010-10-21 23:27:07
Hi
 
in the first case (Non migrated carrier billing Migrated carrier) - if Non migrated carrier provides Type Code '1' on old IDEC, will this be passed through by IS on old IDEC output?

Konda
From: IATA
Posted: Monday, September 20, 2010 9:20 AM
Subject: Excess Baggage source code during migration

Hi.
 
There will be no conversion of source codes from old to new IDEC or vice versa.
 
So:
 
  1. Non migrated should use SC 01 as today. Migrated carriers will receive an old IDEC file with SC 01.
  2. Migrated carriers should use SC 25. Non-migrated carriers will receive an old IDEC (down-converted from IS-IDEC/IS-XML) with SC 25.

Please note that field 15 of the old IDEC invoice header record (Currency Conversion Indicator) will be used to flag down-converted old IDECs. Thus, your system will be able to identify these situations.

James


From:
Posted: Wednesday, September 08, 2010 10:16 PM
Subject: Excess Baggage source code during migration

Can you clarify what source code will be populated on the old IDEC for excess baggage during migration?
 
1) non-migrated billing carrier should use s/c 01 or separate invoice?
 
Will IS transform this to s/c 25 on old IDEC output for migrated billed carriers?
 
2) migrated billing carrier should use s/c 25 on IS-IDEC/IS-XML.

What s/c will be provided on old-IDEC output to non-migrated billed carrier?
Replied by Ashley H on 2011-02-02 17:25:43
Hi Konda,
 
To pick this question up again, in the first case above, if non-migrated carriers provide type code 1 on old IDEC, it will be passed through IS on old IDEC output.

Rgds

From:
Posted: Thursday, October 21, 2010 11:27 PM
Subject: Excess Baggage source code during migration

Hi
 
in the first case (Non migrated carrier billing Migrated carrier) - if Non migrated carrier provides Type Code '1' on old IDEC, will this be passed through by IS on old IDEC output?

Konda
From: IATA
Posted: Monday, September 20, 2010 9:20 AM
Subject: Excess Baggage source code during migration

Hi.
 
There will be no conversion of source codes from old to new IDEC or vice versa.
 
So:
 
  1. Non migrated should use SC 01 as today. Migrated carriers will receive an old IDEC file with SC 01.
  2. Migrated carriers should use SC 25. Non-migrated carriers will receive an old IDEC (down-converted from IS-IDEC/IS-XML) with SC 25.

Please note that field 15 of the old IDEC invoice header record (Currency Conversion Indicator) will be used to flag down-converted old IDECs. Thus, your system will be able to identify these situations.

James


From:
Posted: Wednesday, September 08, 2010 10:16 PM
Subject: Excess Baggage source code during migration

Can you clarify what source code will be populated on the old IDEC for excess baggage during migration?
 
1) non-migrated billing carrier should use s/c 01 or separate invoice?
 
Will IS transform this to s/c 25 on old IDEC output for migrated billed carriers?
 
2) migrated billing carrier should use s/c 25 on IS-IDEC/IS-XML.

What s/c will be provided on old-IDEC output to non-migrated billed carrier?
Replied by Benjamin R (Lufthansa) on 2011-02-03 01:43:44
Hi All,
 
Don't want to interrupt this discussion. However, in the ISPG para 11.3.6.6 'Source Code Changes' it reads:

"A new prime Source Code 25 has been added to represent Excess Baggage coupon billings. This change is applicable even for non migrated Participants. All excess baggage coupons will have to be grouped separately from Passenger coupons and reported under Source Code 25."

From my understanding this means that SC25 shall be used for both migrated as well as non-migrated carriers when billing Excess Baggage coupons.

Could please clarify which statement is correct?
 
Thank you and regards,
Benjamin (LH)


From:
Posted: Wednesday, February 02, 2011 5:25 PM
Subject: Excess Baggage source code during migration

Hi Konda,
 
To pick this question up again, in the first case above, if non-migrated carriers provide type code 1 on old IDEC, it will be passed through IS on old IDEC output.

Rgds

From:
Posted: Thursday, October 21, 2010 11:27 PM
Subject: Excess Baggage source code during migration

Hi
 
in the first case (Non migrated carrier billing Migrated carrier) - if Non migrated carrier provides Type Code '1' on old IDEC, will this be passed through by IS on old IDEC output?

Konda
From: IATA
Posted: Monday, September 20, 2010 9:20 AM
Subject: Excess Baggage source code during migration

Hi.
 
There will be no conversion of source codes from old to new IDEC or vice versa.
 
So:
 
  1. Non migrated should use SC 01 as today. Migrated carriers will receive an old IDEC file with SC 01.
  2. Migrated carriers should use SC 25. Non-migrated carriers will receive an old IDEC (down-converted from IS-IDEC/IS-XML) with SC 25.

Please note that field 15 of the old IDEC invoice header record (Currency Conversion Indicator) will be used to flag down-converted old IDECs. Thus, your system will be able to identify these situations.

James


From:
Posted: Wednesday, September 08, 2010 10:16 PM
Subject: Excess Baggage source code during migration

Can you clarify what source code will be populated on the old IDEC for excess baggage during migration?
 
1) non-migrated billing carrier should use s/c 01 or separate invoice?
 
Will IS transform this to s/c 25 on old IDEC output for migrated billed carriers?
 
2) migrated billing carrier should use s/c 25 on IS-IDEC/IS-XML.

What s/c will be provided on old-IDEC output to non-migrated billed carrier?
 
ADVERTISEMENT


Additional information

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