ADM forwarding to GDS - BSPlink · PDF fileADM forwarding to GDS - Functionality Guide 2 3 December 2010 ÊThis functionality was developed following discussions with GDSs, in order

ADM forwarding to GDSFunctionality Guide

3 December 2010ADM forwarding to GDS - Functionality Guide 2

This functionality was developed following discussions with GDSs, in order to facilitate the communication flow between agents and the GDSs concerning ADMsAgents receive ADMs from Airlines, which may be caused by a wrong guaranteed fare quote. An agent can now simply forward these ADMs to the GDS in question for further investigation, rather than by mail or faxThis functionality does not affect the settlement process, but is a simple forward of an ADM, that will continue to be processed as per the existing procedures


The ADM will have to be settled by the agent through the BSP. The forwarding does not result in a liability of the GDS for the ADM. However, the agent has the possibility to forward the Debit Memo received from the Airline to the GDS as a proof of error

This new development, released in June, will provide the agent with a button in the ADM screen through which the original document was issued, to send it to the GDS for verification purposes


BSP browser

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


BSPs can activate this option in the Basic configuration


Once enabled, a new module is added to BSP browser: “ADM forward to GDS”, and it has two sub-options:

Block GDS per agent

Block GDS


Block GDS per agent

Through this option, the BSP can decide to disable the “forward to GDS” function for a particular agent


BSP needs enter the IATA agent code for which ADM forwarding is to be blocked, and click on ‘submit’


Once submitted, the below screen appears. Any GDS displayed can be blocked, thus restricting the agent to forward ADMs to those blocked


The BSP user is required to confirm the actionBSPlink confirms the action and no ADM can be forwarded by the selected agent to the selected GDS


Block GDS

Through this option, the BSP can block a particular GDS for the whole market


Once the option is selected, the system displays the list of available GDSs which can be blocked, thus disabling all agents to forward ADMs to the blocked GDS(s)


The BSP user is required to confirm the actionBSPlink confirms the action and no ADM can be forwarded to the selected GDS


Agent browserAgents, while querying ADMs, will have the option to forward ADMs to active BSPlink GDS users for verification purposesOnly ADMs within the latency period can be forwardedThe ADMs can not be forwarded to blocked or non active GDSsAgents should select the GDS and the forwarding reason in the “Remark” field and then, click the “forward to GDS”button


The Agent should select the GDS and forwarding reason in the “remark” field


BSPlink confirms that the Agent has successfully forwarded the ADM to the GDS


The Agent can query the forwarding reason, for reference purposes


Likewise, the Agent is informed when the function is denied:

Because the GDS in question has been blockedBecause the Agent tries to forward an ADM to a non active BSPlink GDS userBecause the Agent is forwarding an ADM to the same GDS for a second time (it is possible to resend to a different GDS)

Reason will be displayed


GDS browserThe GDS users will have the new function to query the forwarded ADMs, namely:

ADM->ADM Query


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


Details can also be downloaded or saved (right click)


The forwarding reason is shown at the bottom of the document


File ready for download appears in .txt format


The File is pipe delimited. ADMs are available in the Query for 13 months


The GDSs have the option to set an e-mail alert to receive a notification whenever a new ADM is forwarded to them

Documents

ADM forwarding to GDS - BSPlink · PDF fileADM forwarding to GDS - Functionality Guide 2 3 December 2010 ÊThis functionality was developed following discussions with GDSs, in order