| Excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Restrictions and points to take care of
The prices are set-up exactly in the same way as before.
The price grid displays one column for each seat category for which a quota has been defined.
Setting up the price breakdown
The price breakdown uses the price components defined in the season. Please refer to Define flexible price breakdowns for the definition of the price components.
You can enter a price breakdown for each fixed price season ticket price. The definition of the price breakdown is optional.
The set-up process is exactly the same as for the other product families. You can find more detailed information on Define flexible price breakdowns.
Reporting
The sold amounts of the price components defined above (that may need to be shared among the different stakeholders) are provided by the reporting domain "Summary of fees". An example is given below:
Documents
You can display the price components on order related documents as well as on the file summary. You will find more details here.
Data migration
...
| Warning | ||
|---|---|---|
| ||
A given mapping table allows to map a target season to a single origin season only. As a result, if you need to map the same target season to several origin seasons because of memberships with different validity duration, you will have to create several batches, each for one origin season. For instance, if you have to handle the 4 cases illustrated in the figure above, you would need:
|
| Warning | ||
|---|---|---|
| ||
Taking the example above, consider that you run the batch on the 20.12.2021 and you have defined an expiry date of 05.01.2022 (either directly or through a duration). Since the schedule requires to select a target season, the batch will either:
As a result, you will need to create 2 schedules during this transition period. |