For external interfaces that require mappings to get internal product's prices, the current way it is done depends on the tariff mapping.
However, a tariff cannot represent a specific price since it is defined differently with specific rate types for a single product, a package, an advantage, etc..
The current tariff mapping in the interface makes it stressful for back-end processing as it must define a correct price for a mapping product.
Solution
Thanks to the new pricing model that each product comes with a specific rate table, a new price mapping is introduces to simplify properly the back-end process.
Limitation: for the moment this new price mapping supports 2 external interfaces
Does the existing Tariff mapping still work?:
- Yes, the tariff mapping is still supported for overall external interface mapping.
- If there exists the new price mapping (in TeamAxess and Skidata interfaces), the system will use the price mapping instead.
How to get started
In order to configure the new price mapping, please refer this figure below and its' description to select correct data in the Price mapping Screen:
- Couple "Rate table - Rate type": depends on above Season filter, only VALID rate tables are listed. The couple "Rate table - Rate type" is available to select if it was already defined in GRID_AMOUNT
- "Tariff: price amount": depends on above "Rate table - Rate type" filter, available to select if it is defined in GRID_AMOUNT
- Secutix Price_ID: it is the GridAmount_ID in GRID_AMOUNT