PNL/ADL Settings

PNL/ADL message processing is provided in the operator host for “Codeshare - Block space” agreements only. The reference to the “Class mapping” record in the agreement description is required for PNL/ADL message processing. If received data does not correspond to the “Class mapping” record, then the message processing is rejected, and the notification is generated in the reject queue.

Seat Booking by PNL/ADL from Marketing Carrier

After the passenger PNL/ADL message is received, the following booking operations are performed:

1. PNR creation
2. PNR update

Seat booking is performed in the cabin/class that correspond to the “Class mapping” record. Seat booking in other cabin/class is not performed.

If some booking data from the message can not be processed ofr any reason, the they are moved to the reject queue.

The processing of ADL messages before the passenger PNL message is not allowed.

All message data is included in the booking by PNL:

• names
• tickets
• EMD
• SSR.

Block Automatic Adjustment by PNL/ADL from Marketing Carrier

The block adjustment is performed using the CFG and AVAIL parameters by the following method:

1. If the AVAIL parameter value >0, then the cabin block capacity is set equal to the CFG value for this cabin. The seat difference between old and new block size is transferred to free sale.
2. If the AVAIL parameter value <0, then the cabin block capacity is set equal to the CFG value + AVAIL absolute value. The seat difference between old and new block size is transferred to free sale.

If the resulted cabin block capacity is larger than the specified block size, then the block adjustment is not performed, and the PNL processing is rejected. The carrier notification will be send in queue.

For the ADL messages, the following processing is performed (based on the tag):

• additional seat booking (the ADD tag)
• update of already created PNR (the CHG tag)
• PNR voiding (the DEL tag)
• block capacity adjustment (using the CFG and AVAIL parameters).

PNL/ADL Sending to Operator Host

Seat sale data on the marketing carrier flight is sent to the flight operator. The lists are generated and sent automatically at the specified time to the carrier operator host (using PNL settings) by RQL request or manually from the inventory screen.

The sending process includes the following two parts:

1. Automatic cabin capacity adjustment at the specified time on the marketing carrier side (it is recommended the last adjustment level a little earlier than passenger list is sent to the flight operator).
2. PNL/ADL sending to the operator host.

If only one of mentioned settings is applied, then it is processed by the System at the specified time.

If the adjustment is successful, then the following check is performed: PNL sending to the operator host has been processed even once. If PNL or ADL was sent, then the message corresponding to the settings at the adjustment time is sent to the operator host:

• If the PNLconfig setting is 'minimal PNL', then the minimal PNL (without surnames) is sent to the operator.
• If the PNLconfig setting is 'Full PNL', then the passenger PNL is sent.
• If minimal and full PNL are set, then the minimal PNL is sent automatically when the applied adjustment level has the “Continue seat adjustment” setting. The block adjustment is set on the operating carrier side for this PNL.
• After full PNL is sent automatically, the operator will receive the ADL messages only.
• ADL messages are sent as by booking updates (based on names), as by change of the following parameters: CFG, AVAIL, TRANSIT, RBD ('minimal ADL').
• The CFG parameter in PNL/ADL corresponds to the cabin block size at message sending time.

Including information on services into PNL/ADL

To include the services of a marketing carrier into PNL/ADL for their subsequent sending to a flight operator or in DCS one should create a configuration in the section Agreements → Codeshare → BSMktSSR. An entry may be created both on behalf of a marketing and an operating carrier.

The form of searching for existing settings is provided first.

For the purpose of searching, indicate a carrier's code and the name of pre-set configuration and press Search. As a result, a list of existing configurations will appear.

To view the entry data, select it in the presented list and perform double left-click or use the Open command from the entry context menu by the right-click or click Actions → Open in the section menu.

The section's entries are available for editing only for users with the appropiate access rights. Without these rights, users can only view the entries.

To edit the selected entry, use one of the following ways:

• Click Actions → Edit in the section's menu.
• Use the Edit command from the entry context menu by the right-click.
• Open the entry for viewing and click on the Edit link.

To create a new configuration, press the button Create. As a result, a new entry creation form will be displayed.

One of the earlier created configurations may be duplicated by its highlighting in the table and selecting in the context menu or menu Actions item Duplicate

To add an entry press the button «Plus» . Specify codes of services and click OK. A new entry will be created and saved.

The entry of a table is valid only if a table of codeshare flights refers to it upon creation of an agreement (field BSMktSSR).

Please note:

1. the table will indicate only SSR codes that are determined in the carrier's settings as Confirmation needed / value Yes and specified in the в таблице представлены только те коды SSR, которые определены в RFISC Codes reference guide
2. the table will indicate only SSR+RFISC pair codes that are specified in the table Setting of Additional Services
3. system SSR codes that do not need any confirmation will be translated to both carriers.

Services with the HN status will be sent to DCS or to the host of the operating carrier only with active option Send SSR with HN status in PNL Configuration. All the statuses of ASVC element are transferred to PNL/ADL.

Processing of PNL/ADL with services on the operating partner part

On the operating partner part, reference to the BSMktSSR entry stated in the Codeshare agreement will be a filter for incoming messages about services received from a marketing partner.

In the event of receiving PNL/ADL from the marketing partner, services in the operator's host will be processed as follows:

1. If there is a reference to the BSMktSSR entry in the Codeshare agreement, only services indicated in the table will be processed. All other services will be ignored.
2. If the BSMktSSR field remained empty, all received messages about services will be processed.

The common logic of the operator's processing of services follows the parameters of the business rule SSR & RFISC Quota (business rule settings prevail). If there is no business rule, then the processing will be performed as provided in the Special Services Settings section.

Services from PNL/ADL with the «To be paid» status in the ASVC element will have a time limit.

Next:

• Codeshare Flights Inventory Management
• Configuring Codeshare Flight
• Configuring Integration between Carriers' Inventory Systems
• Codeshare Flight or Agreement Parameters Modification
• Codeshare Flights Synchronization
• Codeshare Agreement Information Publication
• Codeshare Flights Passenger Re-accommodation
• Confirmation of Services by Marketing Carrier

See also:

• Managing Franchise Agreements

Other sections:

• Schedule Management
• Inventory Management
• PNR Management
• Passenger Re-accommodation
• Carrier Settings
• Seatmaps and Sale with Seat Numbers
• System Queue Management
• Reports
• Dictionaries
• User Rights and Roles
• Viewing Operation Archive
• Messages Searching and Viewing
• Charter Flight Creation