airlines - bsplink - iata

ADM FORWARD TO GDS

‘ADM FORWARD TO GDS’

functionality guide

ADM FORWARD TO GDS

This development was requested by one of the major GDSs to facilitate the communication flow between agents and the GDSs with regard to ADMs. Agents receive ADMs from Airlines which may be caused by a wrong net fair quote. An agent can now simply forward these ADMs to the GDS in question for further investigation. This functionality will not involve any settlement but a simple forward of an ADM that will continue to be processed as per the existing procedures.

ADM FORWARD TO GDS

The ADM will have to be settled by the agent through the BSP, however the agent has the possibility to forward the Debit Memo received from the Airline to the GDS as a proof of error.

ADM FORWARD TO GDS

The new development to be released in June will provide the agent with a button in the ADM to send it to the GDS through which the original document was issued for verification.

ADM FORWARD TO GDS

In the BSP browser there is an option called ADM GDS forward under the header brw_acdms in the Master tables - basic configuration, which when enabled activates this new functionality.

ADM FORWARD TO GDS

BSP can activate this option in the Basic configuration

ADM FORWARD TO GDS

Once enabled a new module is added to BSP browser namely “ADM forward to GDS” having two sub-options:

Block GDS per agentBlock GDS

ADM FORWARD TO GDS

Block GDS per agentThrough this option the BSP can decide to block GDS for a particular agent.

ADM FORWARD TO GDS

BSP should enter the IATA agent code for which ADM forwarding needs to be blocked, andclick on ‘submit’.

ADM FORWARD TO GDS

Once submitted, the screen shown appears where the available GDS could be blocked thus restricting the agent to forwards ADMs

ADM FORWARD TO GDS

The BSP user is required to confirm the action

ADM FORWARD TO GDS

The system confirms the action and no ADM can be forwarded by the selected agent to the selected GDS

ADM FORWARD TO GDS

Block GDSThrough this option the BSP can block a particular GDS for the whole market.

ADM FORWARD TO GDS

Once submitted the screen shown above appears where the available GDS can blocked thus restricting all agents from forwarding ADMs to the blocked GDS.

ADM FORWARD TO GDS

The BSP user is required to confirm the action

ADM FORWARD TO GDS

The system confirms the action and no ADMs can be forwarded to the selected GDS

ADM FORWARD TO GDS

Agent Browser

Agents while querying ADMs will have an option to forward ADMs to an active BSPlink user GDS for verification purposes. Only ADMs within the latency period can be forwarded.The ADMs can not be forwarded to blocked or non active GDS.

ADM FORWARD TO GDS

Agent Browser

Agents should select the GDS and the forwarding reason in the Remark field and the click the ‘Forward to GDS’ button.

ADM FORWARD TO GDS

The Agent should select the GDS and forwarding reason in Remark field

ADM FORWARD TO GDS

This screen appears when the Agent successfully forwards the ADM to the GDS

ADM FORWARD TO GDS

The Agent can query the forwarding reason for reference purposes

ADM FORWARD TO GDS

This screen appear when the Agent tries to forward an ADM to a blocked GDS

ADM FORWARD TO GDS

This screen appears when the Agent tries to forward an ADM to a non active BSPlink GDS user

ADM FORWARD TO GDS

This screen appears when the Agent tries to forward an ADM to a particular GDS for a second time

ADM FORWARD TO GDS

GDS Browser

The GDS user will have an additional feature to query theforwarded ADMs namely:

ADM->ADM Query

ADM FORWARD TO GDS

The GDS can query the forwarded ADMs selecting any of the optional fields

ADM FORWARD TO GDS

In the query the GDS can consult the forwarded ADM and the forwarding reason entered by the Agent

ADM FORWARD TO GDS

Additionally, the GDS have the option to set an e-mail alert to receive a notification whenever there are new forwarded ADMs