Use export values in price agreements
Scenario: you want to set up special prices for situations the standard filters in the price agreements don't let you filter.
Using the standard filters in the price agreements, it's simple to create special prices or discounts for:
But to do other thinks, like setting up special prices for:
- client groups ('gold' clients who get special rates)
- aircraft types (helicopters, or vintage aircraft
- airport or country specific noise categories
You'll need export values to make it happen. Below we'll explain how to do it for blue tailed aircraft. If you situation is different, the way to go should be very similar.
How to do it
1) Choose clear names for export codes and export values. Examples of good names are:
| export code |
possible export value |
| Blue tailed aircraft |
TAILCOLOR |
blue, orange, yellow |
| Gold clients |
DISCOUNTGROUP |
none, silver, gold, platinum |
| aircraft types |
ACTYPE |
helicopter, prop, jet, amphibian, balloon |
| number of engines |
ENGINECOUNT |
0, 1, 2, 3, 4 |
| airport specific noise cat |
LFPB NOISE CAT |
1, 2, 3a, 3b, 4 |
The lesson here is to try and think of other possible values you might use in the future, and name the export code after the property you're describing and set values for the ones you need and some you might in the future.
Also, its important to figure out what exactly the property is thats important. If you regularly handle police helicopters and need a special price, is it because its blue, because its an helicopter, because its a special service, because its just another client getting 10% off or because the debtor is de local city counsil? Depending on he answer your export code could be ACCOLOR, ACTYPE, SPECIALSERVICE (medical, police, firefighters), DISCOUNTGROUP (none, silver, gold OR 5, 10, 15, 20) or none at all because filtering on debtor can be done in without using export codes. If you make the setup just for this case, the result is the same, but by making the right choise you're prepared for future cases as well.
Because FBO One internaly uses ID's and not the names of export codes and values, renaming them later is no problems (as long as no reports or exports rely on the names) but removing them is no longer possible as soon as they have been used. So its good practice to think twice before actually creating new export codes and values.
2) Now define the export code and values using the export code screen in the admininstration. In our blue tailed example, the result should be something like this:
The important thing here is de 'AllowDuplicates' checkbox in the exportcode. In our example we don't allow duplicates, because every aircraft can have only one tailcolor. Unually duplicates won't be what you want.
3) Allocate the export values to the entities they apply too. In our case, we'll set the 'TAILCOLOR blue' to the debtor 'KLM', but 'TAILCOLOR orange' to the registration PH-KBX. Also, we could set the 'TAILCOLOR blue' export value to any registration we know has a blue tail, or even an aircraft type (if there would be a type that's only flying with blue tails, but it does make sense for engine count for example)
A way of looking at it, is we're actually adding new fields to FBO One on the fly. There will probably never be a 'tailcolor' field in the aircraft registration, but if a type of export value is used often enough it will be replaced by a real field in FBO One.
4) Now we can use the export value in price agreements, and for example set up a special price for blue tailed aircraft, so it will work for KLM but not if they use the KBX. (because thats orange)
Of course, in a real life it would probably be a bit more complicated because we'll setup price agremeents for the blue tailed aircraft for every category, or define it as a percentage discount, but using export values, everything is possible.
See also
Configuring a service discount