MAN_Flight History

Owned by lmauro@kiusys.com (Deactivated)
Last updated: Oct 02, 2023 by ana herradon
4 min read

Flight History

Flight History keeps a record of all the actions taken during the check-in process. Use the following entry to display

PH4112/17MARAEP

Description:

PH

Fixed command

4112

Flight

/    

Slash

17MAR

Date

AEP

Board Point

Response:

Displays a record of the actions taken and the agent signing who took the action

Example:

** HISTORY ** FLT: 4112 BRD: AEP WED 17MAR10 CHK OPEN PCI4112 DEFAULT VALUES -> ETKT:Y , BRDP:Y , BAGT:Y , BOARDING: OPEN AEPXX-JF 1836 17MAR10 REG MODIFY FROM /C22.Y90 TO LV-SSS /Y34 AEPXX-JF 1836 17MAR10 TGA MODIFY FROM TO 10 AEPXX-JF 1836 17MAR10 CRW ADD MARTINEZ/PEDRO-ROMERO/FELIPE-VALENCIA/PAULA AEPXX-JF 1838 17MAR10 RMK ADD ** VUELO EN HORARIO ** AEPXX-JF 1838 17MAR10 OPT SET WEB CHECK-IN ALLOWED:Y AEPXX-JF 1838 17MAR10 PU #001 GOMEZ/MARIA DNI 56434 CC:YY SEAT:3A » KIU WEB CHECK-IN 190.210.7.237 NETXX-WW 1839 17MAR10 PU #002 GONZALEZ/ANA DNI 565 CC:YB SEAT:8C BAG:0/0 BT: FF:54258 MS:*PAX VIP* 9992200022115C1 AEPXX-JF 1839 17MAR10 PE #002 BAG:+ADD 1/10 125412 AEPXX-JF 1840 17MAR10 PB PBA4112-AEP00XX457 AEPXX-JF 1840 17MAR10 PB PB1,2 AEPXX-JF 1840 17MAR10 FLT TYPE SET FROM J TO C AEPXX-LL 1800 17MAR10 FLT TYPE SET FROM C TO J AEPXX-LL 1840 17MAR10 BRD CLOSE AEPXX-JF 1840 17MAR10 CHK CLOSE AEPXX-JF 1840 17MAR10 MVT DEPARTURE SEND CDT: 22:05 COT: 22:08 ADT: 22:15 DLY:5 min. / AEPXX-JF 1841 17MAR10 PD 4112/17MAR10 AEP AEPXX-JF 1842 17MAR10

Each PU command for passenger acceptance shows the data entered at the Check-in, the ticket number and the flight coupon.

Passengers accepted on the Web Check-in will be Identified with:>> KIU WEB CHECK-IN followed by the IP address from the location were the request was done.

Flight History allows to add the following filter to the PH entry:

/ETD

Estimated time of departure

/BTD

Boarding Time

/RMK

Comments

/TGA

Barding Gate

/REG

Registration

/CRW

Crew

/SMP

Seat Map

/AVW

Maximum weight to take off

/STD

Scheduled time of departure

/OPT

Operating flight indicatiors  (ETKT, BRDP, etc.)

/MVT

Movement messages

/CNL

Flight Cancelation 

/CLS

Open/Close of availability

/OSL

Oversale

/BRD

Boarding Stutus

/CHK

Check-in Status

/PE

Passenger edited

/PEP

Boarding Pass re-printed

/CWL

Removed from Wait List 

/FLT

Operating flight / flight type

/PW

Movement Manifest 

/PR

Rush Baggage 

/BS

Block Space

/PU

Passenger Accepted 

/PA

APIS Data

/PD

Flight Close

/PB

Boarded Passenger 

/PED

Wait List Deletion 

Considerations

  • Filters cannot be combined 

  • Filters can be applied before or after flight close 

  • PH can be exported to a spreadsheet including a filter  (ALT+ENTER).

  • PH can be printed including a filter(CTRL+ENTER).

 

 

 

 

 

PH filter

A filter can be applied to PH command (flight history for check-in)

The filter can apply to all the entries involving passenger acceptance and update (PU and PE)

 

Command:

PH4520/18JULAEP/#<order item or boarding pass>

Note

  • The zeros corresponding to the boarding pass number should preceed when appropriate.

  • Example: 006

Example:

PH4444/20JUL/#006

** HISTORY **
* FILTER APPLIED *
FLT: XX4444    BRD: AEP    THU 20JUL17
PU  #006 OLARTE/MARIA PP 34784907 CC:YY SEAT:12C BAG:0/0 9990210005150C1
    AEPXX-AS 1227 18JUL17
PE  #006 ST: 12C -> 12B
    AEPXX-AS 1230 18JUL17
PE  #006 DEL
    AEPXX-AS 1230 18JUL17



 

 

Filter by User

This new option allows viewing only the actions performed by the user signing indicated in the filter from the flight history.

Description:

Indicator

Description

Indicator

Description

<flight>

Flight number

<date>

Flight date 

<bpt>

Boarding point

US

User-id filter

<user>

  • User id name

  • User id or new user id can be indicated

<filter>

Any current filter 

Current filters can be combined:

Considerations

  • This filter applies to any status of the flight as long as it is within the check-in period

  • It allows combining with another filter, as long as the flight is not in final closure status (that is, once the PD has been performed)

Examples

Filtering all the actions of a user:

Filtering all the actions of a user combined with another filter: