View source for Parameters of processing PNR with duplicate segments

The order of actions with found duplicate bookings is set in the subsection '''Processing'''.

[[File: Parameters_of_processing_PNR_with_duplicate_segments.png|center]]

The following action with respect to found PNR with duplicate segments is set:

*cancel;
*add to queue;
*cancel and add to queue.

Criteria:

*with the cheapest booking class;
*with the earliest departure day;
*with the latest departure day;
*with the most expensive booking.

Using the mark '''Do not cancel segment with ticket''' you may configure the system behaviour so that even if cancellation of detected segments is selected, the status of ticketed segments will not change.

All found duplicate bookings are preserved by default but a notification of such bookings is sent to the queue of an inventory system user (Queue 302).

When setting is complete press the button '''Save'''.

==See also:==

*[[Duplicate segments/Analysis by City of Departure and Nearby Airports|Analysis by City of Departure and Nearby Airports]]

==Other Integrity sections:==

*[[Time-limit for Flight Segments]]
*[[Time Limit for Special Services]]
*[[Duplicate PNR]]
*[[Black and White lists]]
*[[Fictitious names]]
*[[NO-SHOW postprocessing]]
*[[Churning]]
*[[Implicit Groups]]
*[[Time-limit for Group Names]]
*[[Mandatory PNR Elements]]

[[Category:Revenue Integrity]]