integracion lan tam

Páginas: 11 (2625 palabras) Publicado: 23 de abril de 2013



















Copyright © 2004 PROS Revenue Management
All information contained within this document is the confidential property of PROS Revenue Management. It is submitted with the understanding that it shall not be disclosed to any third party either in whole or in part without the prior written consent of PROS Revenue Management.
No part of this publication may bereproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior
written permission of PROS Revenue Management.
PROS Revenue Management makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability for any partic­ularpurpose. Furthermore, PROS Revenue Management reserves the right to revise this publication and to make changes in content hereof without obligation of PROS Revenue Manage­ment to notify any person of such revision.
Trademarks
All other brands and their products are trademarks or registered trademarks of their respective holders and should be noted as such.
PROS Revenue Management
3100 Main StreetSuite 900,
Houston, TX 77002-9312 USA
Product Information
Phone 713-225-5151
FAX 713-335-8144
Email info@prosrm.com
Web Address http://www.prosrm.com

Change History
VERSION
DATE
PERSON
REASON FOR CHANGE

6/15/2001
Julie Niknafs
Created.

6/29/2001
Srikanth Ranganathan
Revision:
1. Page 21. Set the OvlpType field to optional.
2. Page 29. SegClsFlag. Added “Not used in anyprocessing” for the description.

7/11/2001
Julie Niknafs
InvMapNum in Schedule Segment General is optional. Updated to include SIA’s comments.

8/21/2001
Srikanth Ranganathan
Revision:
1. Changed the order of listing in the example
On page 22.
2. Changed the snapshot requirements in
Page31/32


8/27/2001
Srikanth Ranganathan
Revision:
1. Added comments on missingflight time info on page 36/37.
2. Added comments on Open Segments on page 37.

10/15/2004
John Salch
Updated after review.

10/18/2004
John Salch
Reference Class Mapping moved to standard document. Removed Airports, as they are in the standard document, also. Similar for Reference Time of Day Range. Removed PNR records.

10/25/2004
John Salch
Converted to standard format..01/03/2005
John Salch
Small corrections to wording in the following sections: Mandatory Fields, Optional Fields, Reference Data.

01/11/2005
John Salch
Change to wording of optional fields section.

03/07/2005
Clayton Cutshall
Removed “Reference” from Inventory example description

10/10/2005
Ed L’Heureux
Update processing rule related to inventory PostedFlag.

05 Jan 2006
Ed L’HeureuxUse PROS term SubClsCode instead of the term RGT.

13 Mar 2006
Ed L’Heureux
The SSG TffcRstrFlag (schedule segment record, traffic restriction flag) is mandatory for carriers with segment inventory.

19 Jul 2007
Tommy Schmal
ArcfType for the inventory loader’s BLG record is now CHAR10 instead of CHAR06.
Modified inventory map and inventory examples to reflect the possibility of nosubclasses; also modified the note for SubClsCode and PrntSubClsCode in the RIG and BSB records for this possibility.

15 August 2007
Ian Penfold
Rename FixCfg to ArcfCfgId in the BLG.

15 November 2007
Tommy Schmal
Add InvTime and InvDate to the BFG record.

04 January 2008
Ed L’Heureux
ArcfCfgId is now CHAR(05), not NUM(03).

11 January 2008
Ed L’Heureux
Change WtlLim to NUM 04 to matchstandard SID.

11 January 2008
Ed L’Heureux
SubClsCode is not a mandatory field.

28 January 2008
Ed L’Heureux
Inventory ArcfType is not mandatory unless the flight is a CV flight.

05 Feb 2008
Ed L’Heureux
BLG.VarCfg is not mandatory.

20-June-08
Ed L’Heureux
A class must appear in an inventory map before all of its nested child classes.

24-June-08
Ed L’Heureux
Subclass...
Leer documento completo

Regístrate para leer el documento completo.

Estos documentos también te pueden resultar útiles

  • Lan y tam
  • Lan-tam
  • Fusion Lan-Tam
  • Caso fusión lan
  • Fusión Lan-Tam Airlines
  • Caso Lan TAM
  • Lan Tam
  • Fusion Lan y Tam (Latam)

Conviértase en miembro formal de Buenas Tareas

INSCRÍBETE - ES GRATIS