| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| sidebar:products_solutions:automation:actions:start [2020/09/03 08:40] – [Ticketing and Pricing specific parameters] Peter Lagnerud | sidebar:products_solutions:automation:actions:start [2020/09/11 09:26] (current) – Peter Lagnerud |
|---|
| {{ :sidebar:action_start.png?nolink&200 }} | {{ :sidebar:action_start.png?nolink&200 }} |
| |
| High level: | **Available in scheme types:** |
| |
| 1. Click or drag the Start icon from left menu and place anywhere in the edit area (need to be in edit/draft mode) | Mid-Office\\ |
| | Non-pricing\\ |
| 2. Double click the Start icon to access the configurations | PNR redirector\\ |
| | Pricing and Ticketing\\ |
| 3. Click Add new source | Ticket processing |
| | |
| 4. Enter appropriate configurables | |
| | |
| 5. If applicable; click Add new source to another source | |
| | |
| 6. When all is completed; click Save (don´t forget to Save the entire scheme as well) | |
| |
| === Sources === | === Sources === |
| | |
| | You can have multiple sources in the Start step (but only one GDS per scheme). |
| |
| |{{ :sidebar:sources.png?nolink&600 }}|| | |{{ :sidebar:sources.png?nolink&600 }}|| |
| {{ :sidebar:start_pcc_new.png?direct&600 }} | {{ :sidebar:start_pcc_new.png?direct&600 }} |
| |
| Specify from which OfficeID/PCC the scheme should fetch PNRs for processing. To see all available PCCs for your setup click Manage OfficeID/PCCs or use the arrow down to see a list. Only one OfficeID/PCC may be used per source, but you can add multiple sources (but the GDS must be the same in a scheme). | Specify from which OfficeID/PCC the scheme should fetch PNRs for processing. To see all available PCCs for your setup click Manage OfficeID/PCCs or use the arrow down to see a list. Only one OfficeID/PCC (and PIC/Category) may be used per source, but you can add multiple sources (note: you must have the same GDS for all sources in a scheme. If you have the same scheme/process for several GDS: create separate schemes). |
| |
| Applicable to source:\\ | Applicable to source:\\ |
| |
| === === | === === |
| |
| |
| === Ticketing and Pricing specific parameters === | === Ticketing and Pricing specific parameters === |
| {{ :sidebar:ticketingpricing_base.png?direct&600 }} | {{ :sidebar:ticketingpricing_base.png?direct&600 }} |
| |
| |**General Ticketing and Pricing parameters** \\ \\ **Limit processing to reservations created only in following OfficeIDs/PCCs (optional)** \\ \\ {{ :sidebar:ttkprice_1limit_processing.png?direct&600 }} \\ Specify exact OfficeIDs/PCCs allowed to process reservations. Eg, if a reservation is created in an OfficeID/PCC that is not in the list it will not be processed. \\ Separate OfficeIDs/PCCs with a comma or semi-colon. \\ \\ \\ **Process reservations only if FQ, PQ, TST has been created by a user listed in the list below (optional)** \\ \\ {{ :sidebar:ttkprice_2processres.png?direct&600 }} \\ Price has to be stored by an agent specified in the list otherwise the reservation will not be processed. \\ \\ **Use any/private/published fares for PNR pricing.** \\ \\ {{ :sidebar:ttkprice_3useforpricing.png?direct&200 }} \\ \\ \\ Choose which type of fares that will be allowed to be processed. \\ \\ \\ **Refresh FQ, PQ, TST on a daily basis.** \\ \\ {{ :sidebar:ttkprice_4refreshpq.png?direct&200 }} \\ \\ \\ Update the stored price on a daily basis \\ \\ **Keep previously stored fare within the same reservation class - This disables change of fare or fare basis at time of pricing if a lower fare is found within the same reservation class.** \\ \\ {{ :sidebar:ttkprice_5keepprevstoredfare.png?direct&400 }} \\ Make sure a re-pricing/re-storing of a fare/price is using the same reservation class, fare or farebasis as the current stored fare/price. \\ \\ \\ //(– for Fare increase rules, see next row below –)// \\ \\ **Disable fare evaluation for PNRs with following segment status codes: enter codes, for example UX, HX** \\ \\ {{ :sidebar:tktprice_06.png?direct&400 }}Enter codes that will be excluded from a check of alternative fares. \\ \\ **Stop processing PNR if any part of the routing has been modified.** \\ \\ {{ :sidebar:tktprice_07.png?direct&400 }} \\ **Stop processing PNR if the fare brand could not be matched to the farebasis in original FQ, PQ, TST.** \\ \\ {{ :sidebar:tktprice_08.png?direct&400 }} \\ \\ **Send notification if mid-office reference cannot not be determined.** \\ \\ {{ :sidebar:tktprice_09.png?direct&400 }}If reference cannot be determined send an email to the email address defined in System Settings => E-mail => System e-mail settings => System e-mail To address. \\ \\ **Create FQ, PQ, TST and continue processing PNR if no FQ, PQ, TST exists for the class booked.** \\ \\ {{ :sidebar:tktprice_10.png?direct&400 }} \\ \\ **Stop processing if the total fare currency is different from the currency set in the scheme properties.** \\ \\ {{ :sidebar:tktprice_11.png?direct&400 }} \\ Ensures the fare in the stored total price is the same as specified in the scheme properties. Example: \\ \\ {{ :sidebar:schemepropertiescurr.png?direct&400 }} \\ \\ **Send notification if no valid segments were detected in PNR.** \\ \\ {{ :sidebar:tktprice_12.png?direct&400 }}If no valid segments found send an email to the email address defined in System Settings => E-mail => System e-mail settings => System e-mail To address. \\ \\ **Process split PNRs by the same scheme when detected.** \\ \\ {{ :sidebar:tktprice_13.png?direct&400 }} \\ \\ If the PNR has been split the scheme will also process the split PNRs. \\ | | |**General Ticketing and Pricing parameters** \\ \\ **Limit processing to reservations created only in following OfficeIDs/PCCs (optional)** \\ \\ {{ :sidebar:ttkprice_1limit_processing.png?direct&600 }} \\ Specify exact OfficeIDs/PCCs allowed to process reservations. Eg, if a reservation is created in an OfficeID/PCC that is not in the list it will not be processed. \\ Separate OfficeIDs/PCCs with a comma or semi-colon. \\ \\ \\ **Process reservations only if FQ, PQ, TST has been created by a user listed in the list below (optional)** \\ \\ {{ :sidebar:ttkprice_2processres.png?direct&600 }} \\ Price has to be stored by an agent specified in the list otherwise the reservation will not be processed. \\ \\ **Use any/private/published fares for PNR pricing.** \\ \\ {{ :sidebar:ttkprice_3useforpricing.png?direct&200 }} \\ \\ \\ Choose which type of fares that will be allowed to be processed. \\ \\ \\ **Refresh FQ, PQ, TST on a daily basis.** \\ \\ {{ :sidebar:ttkprice_4refreshpq.png?direct&200 }} \\ \\ \\ Update the stored price on a daily basis \\ \\ **Keep previously stored fare within the same reservation class - This disables change of fare or fare basis at time of pricing if a lower fare is found within the same reservation class.** \\ \\ {{ :sidebar:ttkprice_5keepprevstoredfare.png?direct&400 }} \\ Make sure a re-pricing/re-storing of a fare/price is using the same reservation class, fare or farebasis as the current stored fare/price. \\ \\ \\ //(– for Fare increase rules, see next row below –)// \\ \\ **Disable fare evaluation for PNRs with following segment status codes: enter codes, for example UX, HX** \\ \\ {{ :sidebar:tktprice_06.png?direct&400 }}Enter codes that will be excluded from a check of alternative fares. \\ \\ **Stop processing PNR if any part of the routing has been modified.** \\ \\ {{ :sidebar:tktprice_07.png?direct&400 }} \\ **Stop processing PNR if the fare brand could not be matched to the farebasis in original FQ, PQ, TST.** \\ \\ {{ :sidebar:tktprice_08.png?direct&400 }} \\ \\ **Send notification if mid-office reference cannot not be determined.** \\ \\ {{ :sidebar:tktprice_09.png?direct&400 }}If reference cannot be determined send an email to the email address defined in System Settings ⇒ E-mail ⇒ System e-mail settings ⇒ System e-mail To address. \\ \\ **Create FQ, PQ, TST and continue processing PNR if no FQ, PQ, TST exists for the class booked.** \\ \\ {{ :sidebar:tktprice_10.png?direct&400 }} \\ \\ **Stop processing if the total fare currency is different from the currency set in the scheme properties.** \\ \\ {{ :sidebar:tktprice_11.png?direct&400 }} \\ Ensures the fare in the stored total price is the same as specified in the scheme properties. Example: \\ \\ {{ :sidebar:schemepropertiescurr.png?direct&400 }} \\ \\ **Send notification if no valid segments were detected in PNR.** \\ \\ {{ :sidebar:tktprice_12.png?direct&400 }}If no valid segments found send an email to the email address defined in System Settings ⇒ E-mail ⇒ System e-mail settings ⇒ System e-mail To address. \\ \\ **Process split PNRs by the same scheme when detected.** \\ \\ {{ :sidebar:tktprice_13.png?direct&400 }} \\ \\ If the PNR has been split the scheme will also process the split PNRs.| |
| |**Fare increase rules** \\ \\ {{ :sidebar:ticketingpricing_02.png?direct&600 }} \\ \\ \\ Fare rule increase section allows you to detect and manage unexpected increase of Base, Equivalent, Tax or Total Fare every time reservation is processed by the Start element. Create one or multiple rules specifying the fare increase level and suitable action to be taken if such increase is detected. If multiple rules are set, the sequence that they are created in will determine the order how rules are applied. \\ \\ Create one or multiple rules to track fare increase. \\ \\ Compare reservation total value/passenger total value with original value/value from valid PQ, FQ, TST/value from last attempt \\ \\ Check the following conditions: \\ \\ value increase more (enter than amount or %) \\ reason for value increase is any/increase of currency exchange rate/not currency exchange rate \\ valid FQ, PQ, TST from today exists does not matter/yes/no \\ \\ If conditions are met, perform following actions: \\ issue tickets \\ notify by e-mail \\ do not create new FQ, PQ, TST \\ stop processing of PNR and notify by e-mail | | |**Fare increase rules** \\ \\ {{ :sidebar:ticketingpricing_02.png?direct&600 }} \\ Fare rule increase section allows you to detect and manage unexpected increase of Base, Equivalent, Tax or Total Fare every time reservation is processed by the Start element. \\ Create one or multiple rules specifying the fare increase level and suitable action to be taken if such increase is detected. \\ If multiple rules are set, the sequence that they are created in will determine the order how rules are applied. \\ \\ Create one or multiple rules to track fare increase. \\ \\ **Compare reservation total value/passenger total value with original value/value from valid PQ, FQ, TST/value from last attempt** \\ \\ **{{ :sidebar:farerules_1compare.png?direct&400 }}** \\ \\ **Check the following conditions:** \\ \\ **value increase more (enter than amount or %)** \\ {{ :sidebar:farerules_2valueincrease.png?direct&400 }} \\ **reason for value increase is any/increase of currency exchange rate/not currency exchange rate** \\ \\ **{{ :sidebar:farerules_3reasonforvalue.png?direct&400 }}** \\ **valid FQ, PQ, TST from today exists does not matter/yes/no** \\ \\ {{ :sidebar:farerules_4validpq.png?direct&400 }} \\ \\ **If conditions are met, perform following actions:** \\ **issue tickets** \\ \\ {{ :sidebar:products_solutions:automation:actions:farecond_1issue.png?direct&400 }} \\ **notify by e-mail** \\ \\ {{ :sidebar:products_solutions:automation:actions:farecond_2notify.png?direct&400 }} \\ **do not create new FQ, PQ, TST** \\ \\ {{ :sidebar:products_solutions:automation:actions:farecond_3donotcreate.png?direct&400 }} \\ **stop processing of PNR and notify by e-mail** \\ \\ **{{ :sidebar:products_solutions:automation:actions:farecond_4stopprocessing.png?direct&400 }}** | |
| | |
| |
| __ | ---- |
| | [[:sidebar:products_solutions:automation:schemes:actions|Back to Actions]] |
| |
| [[:sidebar|Back to main page]] | [[:sidebar|Back to main page]] |
| |
| |