This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
Is anyone else having an issue with Concur tickets in Sabre saying CTP edits on hold and that there is no hold line --- also notice ticket line is different now. I have a ticket in but Concur open shows no disruption in travel
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
@jennymc79 Thanks for posting in the SAP Concur Community.
This error ‘’ CTP EDITS ON HOLD ‘’comes directly from the Reservation System Sabre and is set up by the Travel Agency in the GDS (Sabre).
The error CTP EDTS ON HOLD is a GDS error. To explain a bit more:
This is an issue related to how things are set up within Sabre. CTP Edits are something the agency creates that is required information in the PNR. If a booking is created in Concur and some required information is missing we get this edit message from the GDS. Kindly verify the ''CTP EDITS'' directly with Sabre/Sabre representative on the individual Pseudo-City to confirm if the GDS Edits are set up correctly.
Remember to tag me if you respond or feel free to mark this post as Solved if you don't have further questions or comments. To tag me on your response, you click the Reply button, first thing to type is @. This should bring up the username of the person you are replying to.
This content from the SAP Concur Community was machine translated for your convenience. SAP does not provide any guarantee regarding the correctness or completeness of this machine translated text. View original text custom.banner_survey_translated_text
This actually was a concur issue -- Concur unceremoniously moved us to the T2 New Travel Experience platform - once I turned that off everything was fixed. Just in case this happens to anyone else.