Show TOC

Function documentationExploitation Frequency

 

You can restrict the exploitation frequency in license acquisition and license sales contracts.

Rights exploitation (rights usage) is entered using a counter and settled accordingly on the basis of data values that you define (such as number of transmissions for a television film, subscriptions sold for Pay TV, and so on).

Example Example

A licensor has the right to 20 transmissions (runs) of a film.

The licensor sells a licensee the right to this film. It is agreed that the licensee can show the film five times during the validity period. The licensee confirms six transmissions. The system establishes that the contract has been over-fulfilled on the basis of the confirmations received and sets the item status accordingly.

End of the example.

Prerequisites

You have created a corresponding data value (of the type quantity), to which you have assigned an exploitation frequency type. You do this by way of the Define Data Values Customizing activity (in SAP Customizing for Customer Relationship Management, choose Start of the navigation path Industry-Specific Solutions Next navigation step Media Next navigation step Intellectual Property Management Next navigation step Basic Functions Next navigation step Pricing Next navigation step Define Data Values End of the navigation path).

The standard system is shipped with cumulation rule 13 (Transmission) assigned to the Transmission data value (4RUN).

The 4RUN data value with the cumulation rule origin and the exploitation frequency type Items (ST) is delivered by SAP and has to be used to enter rights usage using a counter.

If necessary, you can change the description for the data value 4RUN.

Note Note

If no exploitation frequency type is needed, delete the data value 4RUN. In this case, the field does not appear on the user interface.

End of the note.

Features

You can enter a number (or quantity) to describe the rights exploitation frequency of an IP (for example, the number of transmissions) during rights maintenance from one of the following applications:

  • License Acquisition Contract

  • License Sales Contract

  • Rights Availability Analysis

For a license acquisition contract, the right to an IP is acquired with a specific exploitation frequency.

For a license sales contract, the right to an IP is sold with a specific exploitation frequency.

Example Example

If you have agreed to five transmissions from April 1 to December 31 for the US territory, Free TV market exclusively for $100,000, and eight transmissions from July 1 to March 31 (of the next year) for the Canada territory, Pay TV market exclusively for $80,000, you must enter these values in two separate items.

End of the example.

You can view the number (or quantity) that describes the rights exploitation frequency of an IP (for example, the number of transmissions) as follows:

  • During rights availability analysis, if an IP has a granting reference to a license acquisition contract, you can access the contract to view the exploitation frequency (for example, the number of transmissions remaining), the validity period and cost associated with exploiting the IP.

  • During License Usage Confirmation, you can view the number (quantity) of times the IP was exploited. Note that the quantity is cumulated in the Transmission (4RUN) data value.

  • During rights availability analysis, you can view the number (quantity) of times the IP was exploited.

  • When creating License Sales Contracts, you can run the extended collision check, which determines if the exploitation frequency specified in the corresponding license sales contract allows for the sale of the current rights

Note Note

At each confirmation, the Business Add-In (BAdI) BAdI to Check Exploitation Frequencies compares the confirmed quantity with the agreed quantity sold in the license sales contract. item. You can create an implementation to modify the behavior of this check. You access this BAdI by way of SAP Customizing for Customer Relationship Management by choosing Start of the navigation path Industry-Specific Solutions Next navigation step Intellectual Property Management Next navigation step Transactions Next navigation step Settings for IPM Transactions Next navigation step BAdIs Next navigation step BAdI to Check Exploitation Frequencies End of the navigation path.

End of the note.

The system also sets the item status during this check in the standard system.

If the system establishes during the confirmation that the film has been shown more often than agreed, it sets the item status to Oversold.

If the license end has been reached and the system establishes during the confirmation that the film has been shown less than the agreed number of times, it sets the status to Undersold.

You can use the BAdI for status management in the business transaction to respond to these status changes. You do this in Customizing for Customer Relationship Management by choosing Start of the navigation path Transactions Next navigation step Basic Settings Next navigation step Status Management Next navigation step Business Add-In for Status Management End of the navigation path.

Possible responses to over or under-fulfillment of a sales item include:

  • Trigger an action and send an e-mail.

  • Activate a condition type for the item.

The following diagram shows the process flow described above:

More Information

Calculating Transmissions in the Rights Availability Analysis