Dispo Book / Bookings
Introduction
When the opportunity products are created in MediaVelox, the corresponding bookings / dispo book entries are automatically generated.
In other words, the reservation is only transferred to ad scheduling once the offer has been synchronized with the opportunity - either manually or when the offer is sent by e-mail.
If availabilities have changed between the time of saving the offer and the synchronization process, they will also be validated and the synchronization process will be aborted if the availability is too low.
A dispo book entry contains all relevant information about a reservation or booking - from the opportunity, the associated offer to the reserved placement and the handling status in the after sales process.
Due to the complex references to availability and pricing within a dispo book entry, manual creation of bookings without a quotation process is not recommended. However, if required, the "New" button can be displayed again on the object.
Technical description
Bookings stand as details in a master-detail relation to the object availability (f42_dispo__AdPosCatalog__c).
API Name | Label EN |
f42_dispo__DispoBook__c | Booking |
Name | Label EN | Type | Comment |
Name | Booking Number | Auto Number | Each booking entry is assigned a number |
f42_dispo__Order_Processing__c | Order Processing | Picklist | In order to better monitor the processing status of a booking from reservation to settlement, the after-sales process is divided into phases. These are displayed in the page layout as a path. |
f42_dispo_AdPos_Catalog__c | Ad Position Placement | Master-Detail(Ad Position Placement) | The booking is in detail relation to the higher-level availability. |
f42_dispo__Quote__c | Quote | Lookup(Quote) | From this offer comes the reservation. |
f42_dispo__QuoteLineItem__c | Angebotsposition | Lookup (Position) | Reference to the exact offer position |
f42_dispo__ValidDate__c | Valid Until | Date | At this point, you can specify a validity date for a reservation. Is currently not yet filled automatically. |
f42_dispo__Nettoumsatz__c | Amount Net | Currency(16, 2) | the lowest unit price less all discounts |
f42_dispo__grossMediaValue__c | Gross Media Value | Currency(16, 2) | List price |
f42_dispo__customerNet__c | Customer Net | Currency(16, 2) | The final price for the opportunity account |
f42_dispo__Issue__c | Issue | Lookup (Issue) | The booking appears in this issue. |
f42_dispo__IssueName__c | Issue Name | Formula (Text) | Returns the name of the output using a calculation field. Can be used for reports. |
f42_dispo__AdPositionPublicationId__c | Ad Position Publication Id | Formula (Text) | the publication on which the booking is based |
f42_dispo__IssuePubDate__c | Publication date (Issue) | Formula (Text) | the publication date of an issue |
f42_dispo__PublicationDate__c | Publication Date | Date | In the case of period-based bookings, the publication date of the ad booked may differ from the publication date of the corresponding issue. This field indicates the publication of the ad placement. |
f42_dispo__PublicationDateUntil__c | Publication Date Until | Date | Specifies the end date of the posting (period-based posting) |
f42_dispo__AdPosition__c | Ad Position | Lookup (Ad Position) | The booking refers to this placement. |
f42_dispo__PageNumber__c | Seitennummer | Number | optional specification of a page number, is currently not filled automatically |
f42_dispo__Opportunity__c | Opportunity | Lookup (Opportunity) | The posting is made via this opportunity. |
f42_dispo__OpportuniyLineItemID__c | Opportunity Line Item ID | Text(21) (External ID) | associated opportunity product |
f42_dispo__Account__c | Account | Lookup (Account) | Relation zum Opportunity-Account |
f42_dispo__AdditionalAccount__c | Additional Account | Lookup (Account) | Displays the second account for multi-level sales, for example, the agency |
f42_dispo__Product__c | Product | Lookup (Product) | the product belonging to the booking |
f42_dispo__OpportunityProduct__c | Opportunity Position | Text(255) | Name of the opportunity product. If it was changed in the quotation process, it differs from the original product name |
f42_dispo__Volume__c | Voume | Number | booked volume |
f42_dispo__VolumeType__c | Volumen Type | Picklist | e.g. CPC, AID |
f42_dispo__CountBlocked__c | Count Block Positions | Roll-Up Summary (COUNT Blocked Position) | Number of lock entries triggered by the posting |
f42_dispo__VolumeBlocked__c | Volume Block Positions | Roll-Up Summary (SUM Blocked Position) | the volume belonging to a lock entry (regarding runtime-based postings) |
f42_dispo__confirmed__c | Confirmed | Checkbox | Is set when the offer is accepted and indicates that the reservation has been confirmed. |
f42_dispo__BillingType__c | Billing type | Picklist | Here you can define to which of the accounts in multi-level sales and distribution the invoice should be issued, e.g. agency or end customer. This is important, for example, for integration with billing. Is not yet set automatically at present. |
f42_dispo__Calculated_Archive__c | Calculated Archive | Formula (Checkbox) | A posting is set to archived if The posting has been canceled (status for the Dispo book entry) the publication period is in the past, for print publications: f42_dispo__Issue__r.f42_dispo__ClosingDate__c for digital: publications f42_dispo__Issue__r.f42_dispo__PublicationDateUntil__c the validity of the offer has expired the opportunity is lost |
f42_dispo__archive__c | Archived | Checkbox | Is set automatically and outputs the value of formula f42_dispo__Calculated_Archive__c as a checkbox. This means that the field can be referenced using rollup summaries for the Availability object. |
f42_dispo__Notice__c | Comment | Text(255) | Optional |
f42_dispo__Description__c | Description | Long Text Area(32000) | Optional |
f42_dispo__ignorePagePlanning__c | Ignore for Page Planning | Checkbox | Optional information for integration with a CMS system |
f42_dispo__isMovable__c | Is Movable | Checkbox | You have the option of manually marking a posting as "postponable", for example, if the customer is not committed to a particular issue. |
f42_dispo__ExternalDispoID__c | External dispo ID | Text(50) (External ID) (Unique Case Sensitive) | May be required for integration |
f42_dispo__External_ID__c | External ID | Text(255) (External ID) (Unique Case Sensitive) | May be required for integration |
RecordTypeId | Record type | Record Type | associated record type |
For bookings, two types of data records are used, depending on whether runtime or time-based bookings are made for the publication. You will also find a separate page layout with the relevant fields.
Record Type | Checkbox “Digitalprodukt” an der Publikation |
|---|---|
Fixed Publication Date | False |
Time Period | True |
The order processing
Dispo book entries not only contain all information on opportunity, offer and prices, placement and availability, they are also the basis for the entire after-sales process: The handling of bookings has many facets - it starts with the order and ends with the successful publication. In this context, there are various work steps and linked processes that must be taken into account.
MediaVelox offers you the option of dividing your booking into different phases similar to the opportunity and displaying them as a path in the page layout via the field Processing status, f42_dispo__Order_Processing__c.
The following processing statuses are defined as standard for each data record type:
Status - Fixed Publication Date | Description |
|---|---|
reserved | is set automatically, if the related opportunity has not yet been won |
booked | is set automatically as soon as the related opportunity is won |
canceled | is not set automatically and may have to be configured in the project |
Motive available | Is set manually once the ad spec has been received |
Motive tested | is set manually once the ad spec has been checked and released |
Proof sent | is selected manually once the proof has been sent. To generate this status automatically, you must make project adjustments in conjunction with the associated data records for voucher copies. |
invoiced | is not set automatically and must be configured in the project if necessary |
Status - Time Period | Beschreibung |
|---|---|
reserved | is set automatically, if the related opportunity has not yet been won |
booked | is set automatically as soon as the related opportunity is won |
canceled | is not set automatically and may have to be configured in the project |
Motive available | is not set automatically. Ad spec is ready for transfer to the AdServer |
Motive tested | is not set automatically. Ad spec is being delivered by the AdServer. |
Proof sent | is not selected automatically. Booked playout is complete. |
invoiced | Is not set automatically and may need to be configured in the project |
A connection of the booking to third-party systems, e.g. for page planning, ad server or invoicing, or to other processes within your Salesforce instance are not part of MediaVelox, but can be implemented in the project.