General information about important MYDAS Settings

This chapter is only to show the important MYDAS Setting which are required for iteration 1 but are already configured that the iteration 1 workflow will work without problems. No user actions are required in that case. The records only need to be there.

Currency

The currency is required for the price definitions as well as for the campaigns.

Rate types

Rate types are reqired for pricing information. Without these information the system wouldn´t be able to display breaks propper in the system. They will get more important in interation 2.  

The rate type is basically only a number that helps to handle different types of ratecards (=Listprices) on break level. In the starhub workflow as is seems for now only one Rate type is required.

List Prices

For the list prices the same applyes as for the rate types. They are only to display breaks properly in iteration 1. In interation 2 they will represent the multipliers for fringe and prime time.

A list price is linked to a rate type and a price folder which is described in the next sequence.

The important value is the price group which is displayed together with the rate type in the break identifiers that are generated for each break.

Price Folder

The price folder is required to link the pricing information to a media combination. For iteration 1 testing only one price folder is required. The price folder holds inforamtion about the currency and the price model which is userd for length weighted pricing.

Media Combi(nation)

The mediacombination is required for Suborders and Bundles. In iteration 2 it will be relevant for the Tiers and the pricing.

Order tpye

The Order type is one of the most important settings in the system. It is required as well for suborders as for placements.

The order type defines if a suborder or a placement is generationg a gross value or if it is a free value which generates no gross.

Break tpye

The break type is required for the WON Import and to identify which kind of break it is. Currently there is only one tpye of breaks delivered from WhatsOn which is Commerical.

For interface purposes the Identifier of the break type needs to be the same like the ones that are delivered from WhatsON.