For example: offices EEE1S2104 and MSP1S212U Entry: EODEWR1S2104-MSP1S212U 2. There is no EOS agreement: If there is no EOS agreement between Office EEE1S2104 and MSP1S212U, the error message can be displayed. The EOS RMO and CRP agreement identifiers are established at the enterprise level between Corporate `1S2` and Office MSP1S212U, as shown in the history. Example: 3. There is an EOS agreement at the company level: if the EOS agreement between Office EWR1S2104 and MSP1S212U indicates the letter C for an identifier, it means that these offices have an agreement at the company level (for example. B for RMO and CPR identifiers). Letter C states that the EOS agreement for this qualification has been established at the company level. In the example above, there is no EOS agreement between the offices. 4. Update the EOS agreement at the desktop level using access mode B (for both). Entry: EOUEWR1S2104-MSP1S212U-BQUE Access is shown in reading and writing mode. The update should solve the problem. 5.

If the problem persists and you are certain that the request is valid, contact your Amadeus Help Desk (or representative). Please provide the following information to support the investigation and expedite the processing time: the receiving office does not have an EOS (Extended Ownership Security) agreement with the mailing office to view PNR data. There is no extended Ownership Security (EOS) agreement between your office and the PNR data recovery office requested 1. View the EOS agreement between the two offices. 2. Queues 25 and 26 are for list queues that can only be used for LP/LM/LPO entries with Q option. Don`t try to put a PNR in these queues. 3. View the EOS agreement between the two offices.

Note: You can only update existing EOS agreements if you have set the “Amadeus Extended Ownership” mark on JA (sign) in your local security profile. If you don`t have an LSA, talk to your Amadeus Help Desk (or representative). This error message may appear when you try to remove an EOS agreement between the owner and the recipient offices (z.B. EOXEWR1S2104-MSP1S212U). Possible cause: 4. Update the EOS agreement at the office level with the N access mode (meaning ACCESS IS DENIED). Contact your local security administrator (LSA) to implement a new EOS agreement or update an existing agreement.