Tebus Import

The Tebus import can only be used for upfront bookings (yearly).

The file provided by the agency must be supplied in ISO-8859-1 format and comply with the Tebus specifications. Only in this file format it can be ensured that the special characters contained in the file (e.g. in the customer name) can be processed correctly.

The Tebus files contain data about the spots to book. The files sent by agencies may not contain information like customer, order and suborder ID (step 1 in the process). Before you can import this file in S4AdSales the ID's have to be inserted (manually) or with an appropriate tool in order to have all following information so that an import can be done as well as the insert/update/delete process.

One file contains the spot data for one order within a specific period and the price for the spot, the period is indicated in the flight periods (see below). These flight periods are not relating to the suborder flight periods but to the time range of the spots contained in the file. E.g. if flight period is 01.01.-15.01. only the spots in this time range will be matched.

Note: flight periods are not imported; they are only used as search criteria and can be adjusted manually.

Due to Tebus format request we cannot remove unnecessary fields from the format; they have to stay empty.

The following attributes must be submitted by the agency in the Tebus file:

  • Agency name;
  • Advertiser name;
  • Medium (according to medium identifier in MYDAS);
  • Product.

However, it is important to note that the respective data must always be transmitted at the exact same place. E.g. if the name of the agency starts already at line 17 instead of 18, the file cannot be imported correctly.

On the MYDAS side, the above Master data record as well as a corresponding order and a product for the year of the upfront bookings should be available.

The file is imported into MYDAS under Interfaces > Tebus Import.

The Tebus file is uploaded here accordingly and in the following imported via the action 'Import'.

Since agencies generally only include the aforementioned minimum attributes in the Tebus file and for instance no IDs through which a clear allocation in MYDAS is possible, in the next steps the system will (in the course of the import) query whether the names of the respective master data match the data available in MYDAS. This matching is carried out for the following master data:

  • Agency;
  • Advertiser;
  • Order / suborder*;
  • Product**.

In the respective queries, the corresponding master data can be confirmed.

Through the (wildcard) search function can be searched individually for e.g. the advertiser if there are several similarly named master data records in MYDAS.

* Since no order or suborder is usually mentioned in the Tebus file, MYDAS searches for all orders in the period in which the advertiser and agency are available and outputs the corresponding orders and suborders for selection.
If there is only one order / suborder for the corresponding combination, MYDAS automatically assigns it, so that no manual selection is necessary here. However, if MYDAS finds several orders / suborders, the corresponding selection must be made manually.

** The same logic applies to the allocation of the product.
If the combination of the product name and the advertiser in the Tebus file is unique, MYDAS will recognize this and assign it accordingly. If the product in the file does not exist in MYDAS or is not linked to the advertiser, the bookings will be booked on 'open product'.

Deletion of Tebus files (including the imported dates) via the import interface

These steps are necessary if a file for instance due to incomplete data could be imported only partly and a new import is needed after changing the file.

  1. Use the 'Garbage can' symbol to delete the imported appointments.
  2. Delete the corresponding file via 'Delete'.
  3. Delete any data that may have been cached in the background via 'Reset'.