Adm Forwarding to Gds

8/2/2019 Adm Forwarding to Gds

1/25

ADM forwarding to GDS

Functionality Guide


2/25

3 December 2010ADM forwarding to GDS - Functionality Guide 2

This functionality was developed following discussions

with GDSs, in order to facilitate the communication flowbetween agents and the GDSs concerning ADMs

Agents receive ADMs from Airlines, which may be

caused by a wrong guaranteed fare quote. An agent cannow simply forward these ADMs to the GDS in questionfor further investigation, rather than by mail or fax

This functionality does not affect the settlement process,but is a simple forward of an ADM, that will continue tobe processed as per the existing procedures


3/25


The ADM will have to be settled by the agent through theBSP. The forwarding does not result in a liability of theGDS for the ADM. However, the agent has the possibilityto 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 theoriginal document was issued, to send it to the GDS forverification purposes


4/253 December 2010ADM forwarding to GDS - Functionality Guide 4

BSP browser

In the BSP browser, there is an option called ADM GDSforwardunder the header brw_acdmsin the Mastertables - basic configuration, which, when enabled,activates this new functionality


5/25


BSPs can activate this option in the Basic configuration


6/25


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


7/25


Block GDS per agent

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


8/25


BSP needs enter the IATA agent code for which ADM

forwarding is to be blocked, and click on submit


9/25


Once submitted, the below screen appears. Any GDSdisplayed can be blocked, thus restricting the agent to

forward ADMs to those blocked


10/25


The BSP user is required to confirm the action

BSPlinkconfirms the action and no ADM can beforwarded by the selected agent to the selected GDS


11/25


Block GDS

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


12/25


Once the option is selected, the system displays the listof available GDSs which can be blocked, thus disabling

all agents to forward ADMs to the blocked GDS(s)


13/25


The BSP user is required to confirm the action

BSPlinkconfirms the action and no ADM can be

forwarded to the selected GDS


14/25


Agent browser

Agents, while querying ADMs, will have the option toforward ADMs to active BSPlinkGDS users forverification purposes

Only ADMs within the latency period can be forwarded

The ADMs can not be forwarded to blocked or non activeGDSs

Agents should select the GDS and the forwarding reasonin the Remark field and then, click the forward to GDSbutton


15/25


The Agent should select the GDS andforwarding reason in the remark field


16/25


BSPlinkconfirms that the Agent hassuccessfully forwarded the ADM to the GDS


17/25


The Agent can query the forwarding reason, forreference purposes


18/25


19/25


GDS browser

The GDS users will have the new function to query theforwarded ADMs, namely:

ADM->ADM Query


20/25


21/25


Details can also be downloaded or saved (right click)


22/25


The forwarding reason is shown at the bottom of the document


23/25


File ready for download appears in .txt format


24/25


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


25/25


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

to them

Documents

Adm Forwarding to Gds