Ansicht
Dokumentation

SAP Media: Intellectual Property Management (New) ( RELNBW_320_BCT_IPM )

SAP Media: Intellectual Property Management (New) ( RELNBW_320_BCT_IPM )

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

SAP Media: Intellectual Property Management (New)

Use

The mySAP Media Intellectual Property Management solution (shipped with SAP CRM 4.0) can be used to represent the acquisition of rights to Intellectual Properties (IPs), management of the IP rights owned, which are acquired or generated and the sale of Intellectual Properties in your media company.

The Business Content for Intellectual Property Management in SAP BW Release 3.20 provides you with the following functions for reporting:

  • DataSource, Data targets and queries for the license sales contract
  • DataSource, Data targets and queries for license usage confirmations
  • DataSource, Data targets and queries for incoming royalties (license revenues)
  • DataSources, InfoObjects and data targets for representing various master data and master data relationships (e.g. interlinkage relationships to the IP, hierarchical attributes for IP rights dimensions)

License sales contract

A right to an IP is sold using a license sales contract. Billing items in the license sales contract are represented for evaluation in SAP BW. Available rights dimensions (maximum of six), define the rights characteristics for a right to be exploited in a license sales contract item. Any combinations of (admissible) rights characteristics can be recorded for an item. Recording these types of combinations requires the contract value to be distributed between the actual characteristics available, so that a unique statement can be made on the value within an item. The same applies if several IPs are recorded for an item. A revenue plan is available in the CRM System for both cases, which specifies the distribution rate for item values. Distribution of values according to the revenue plan is based on the evaluation in SAP BW.

Data targets for the license sales contract

  • InfoCube: ,,0IPM_C01,,License sales contract
  • ODS Object: ,,,,0IPM_DS01,,License sales contract (billing item)
  • MultiCube: ,,0IPM_MC01,,Incoming royalties and license sales contract

The InfoCube on the license sales contract (0IPM_C01) contains all items in a license sales contract and their characteristics by IP and rights dimensions and additional attributes (e.g validity range). Meaningful statements on the value of a contract can only be made using the items for which revenue distribution has been performed. These items are represented using a revenue object, whose attributes (rights characteristics and IP) reflect the actual rights characteristics in the respective item.

Values for which revenue distribution has been performed from the license usage confirmation (see license usage confirmation section) are available for evaluation of the InfoCube. The net item value can be used for items that are not relevant to confirmation (pro rata license fees, single payments). Confirmation values in the license sales contract are PP values (confirmed data refers to a current period). The net value of the billed item must be used to evaluate the net value of confirmation items for which revenue distribution has been performed, since the net contract value only contains ITD values (confirmed data is cumulated over all periods) for technical reasons. The ITD value is converted to a PP value using the difference calculation for billing where it can then be evaluated in a meaningful way.

The Incoming Royalties and License Sales Contract (0IPM_MC01) MultiCube, which connects key figures and characteristics from the license sales contract and incoming royalties, is available for collective evaluation of the billed net value and the values confirmed in the contract.

The License sales contract (billing item) (0IPM_DS01) ODS object is mandatory as a result of the After Image/Delete (AIMD) delta procedure for updating item data in the delta mode.

In addition to update of the License sales contract (0IPM_C01), master data for the revenue object and the license sales contract is also updated from the License sales contract (billing item) ODS object (0IPM_DS01).

License sales contract InfoSource and DataSource

  • DataSource: ,,0IPM_SALES_CONTR_I,,IPM license sales contract (billing item)
  • InfoSource:,,0IPM_SALES_CONTR_I,,IPM license sales contract (billing item)

The License sales contract (billing item) DataSource (0IPM_SALES_CONTR_I) contains all billing items in a license sales contract for which revenue distribution has been performed. Customizing settings for adding your own partner functions, date types and cumulation rules (confirmation values) to the license sales contract are available for the DataSource in the SAP CRM System under: Customer Relationship Management → Industries → Media: Intellectual Property Management → Business Information Warehouse → Settings for Date Types, Cumulation Rules and Partner Functions. These settings can be used to connect these enhancements to SAP BW quickly in a flexible manner.

License usage confirmation

Confirmations are used to report the actual data, which a licensee exploits (e.g sales volumes, advertising costs, audience figures), for a license sales contract to the licensor. This information is used to check the exploitation success of a rights sale and forms the basis for calculating license fees according to the contract type.

Data targets for license usage confirmation

  • InfoCube ,,0IPM_C03,,,,License usage confirmation (item)
  • ODS object,,0IPM_DS03,,,,,License usage confirmation (item)

The License usage confirmations InfoCube (0IPM_C03) can be used to perform a detailed analysis of the confirmation data for a license sales item from the license sales contract (if confirmation relevant item = billing request item).

Note the following here: The license sales contract and the license usage confirmation can have different rights characteristics, since confirmation can take place at a more detailed level than that defined in the license sales contract.
Example: The license sales contract was signed for the Europe region. However, confirmations are made at the level of the individual country, such as Germany, England, France etc.

SAP BW represents the IPM-specific Customizing settings for confirmations. However, values to be confirmed can be made available according to your requirements using the Customizing settings for Intellectual Property Management. Individual enhancements also require the corresponding objects to be post-edited in SAP BW.

Two different procedures for handling values are available for confirmations. The confirmed data either refers to a current period (PP, per period), or it is cumulated across all periods (ITD, inception to date) from the start of the contract validity period to the current point in time. Both procedures are supported by the License usage confirmations (item) InfoCube (0IPM_C03), in which separate key figures are created according to the procedure used.

Note the following: Key figures of the ITD type cannot be handled in a cumulative way during the evaluation.

Since confirmations are made in a specific way for a billing request item in the license sales contract, revenue-dependent distribution of confirmation values is not required.

The License usage confirmation (item) (0IPM_DS03) ODS object is mandatory as a result of the After Image/Delete (AIMD) delta procedure for updating item data in the delta mode.

The License usage confirmation (item) InfoCube (0IPM_C03) is updated from the License usage confirmation (item) ODS object (0IPM_DS03)

License usage confirmation InfoSource and DataSource

  • DataSource: ,,0IPM_CONFIRM_I ,,IPM License usage confirmation (item)
  • InfoSource: ,,,,0IPM_CONFIRM_I ,,IPM License usage confirmation (item)

The IPM License usage confirmation (item) DataSource (0IPM_CONFIRM_I) contains all items in a license usage confirmation. Customizing settings for adding your own partner functions, date types and cumulation rules (confirmation values) to the confirmation document are available for the DataSource in the SAP CRM System under: Customer Relationship Management → Media: Intellectual Property Management → Business Information Warehouse → Settings for Date Types, Cumulation Rules and Partner Functions. These settings can be used to connect these enhancements to SAP BW quickly in a flexible manner.

Incoming royalties (billing documents)

Incoming royalties are license revenues, which the licensor receives as a result of their license sale (controlled by the license sales contract) from the licensee, in return for transferring the usage of an IP for a defined period.

As is the case for the license sales contract, various IP characteristics and/or several IPs, which require revenue distribution to be performed for the billed value, can be recorded for a billing item.

Incoming royalties data targets

  • InfoCube:,,0IPM_C02,,Incoming royalties (billing items)
  • ODS-Objekt:,,0IPM_DS02,,Incoming royalties (billing items)
  • MultiCube: ,,0IPM_MC01,,Incoming royalties and license sales contract

The Incoming Royalties (billing items) InfoCube (0IPM_C02) contains all billed items in the license sales contract and enables the billed net value, for which revenue distribution has been performed, to be evaluated by various characteristics, such as the IP and rights dimensions and by additional attributes. As is the case in the license sales contract, the revenue objects is used to split revenues.

The Incoming royalties and license sales contract MultiCube (0IPM_MC01), which connects key figures and characteristics from the license sales contract and incoming royalties, is available for collective evaluation of the billed net value and the values confirmed in the contract.

Attributes in the license sales contract, which are not found in the billing document, are made available using navigation attributes for a master data object in the license sales contract.

The Incoming royalties (billing items) ODS object (0IPM_DS02) is mandatory as a result of the After Image/Delete (AIMD) delta procedure for updating item data in the delta mode.

The Incoming royalties (billing items) InfoCube (0IPM_C02) is updated from the Incoming royalties (billing items ODS object (0IPM_DS02).

Incoming royalties InfoSource and DataSource

  • DataSource:,,,,0IPM_BEA_IPMI_I,,IPM Incoming royalties (billing items)
  • InfoSource:,,,,0IPM_BEA_IPMI_I,,IPM Incoming royalties (billing items)

Extraction of billing items by the IPM Incoming royalties (billing items) DataSource (0IPM_BEA_IPMI_I) makes all billing items for incoming royalties (IPMI Billing Engine Application IPMI) available (revenue distribution has been performed for these items). No Customizing settings are available for the DataSource.

IPM master data

Interlinkages

Interlinkages provide detailed information on the product, since they enable a relationship to be made between various product components. They are used to determine all materials or IPs, which have been recorded for an additional IP.

Example of IP package part interlinkage: Interlinkages can be used to represent individual episodes and scales for a TV series.

DataSources for representing Interlinkages

  • 0IPM_IL_IPACC_ATTR,,IP part
  • 0IPM_IL_IPMAT_ATTR,,IP related material
  • 0IPM_IL_IPPAC_ATTR,,IP package part
  • 0IPM_IL_IPTTL_ATTR,,IP title
  • 0IPM_IL_IPUCO_ATTR,,IP underlying component

The interlinkage for the relationship with partners, for which the 0CRM_IL_PRDBP_ATTR DataSource is available, is also used for the partner relationship.

Revenue object

The revenue object (InfoObject 0IPM_REVOBJ) adopts all actual rights characteristics that appear and/or several IPs recorded for a rights item. The rights characteristics and IP are managed as attributes for the revenue object, which can also be updated from the transaction data for the 0IPM_SALES_CONTR_I InfoSource (using ODS 0IPM_DS01). Attributes in the revenue object are defined as navigation attributes and made available as such in the InfoCubes for the license sales contract, incoming royalties and the collective Multicube for the license sales contract and incoming royalties.

Master data for an item in the license sales contract

Master data for this item (InfoObject 0IPM_ITMEX) can be used to represent attributes in the license sales contract for the billing document, which are not found in this document. Attributes in the revenue object are made available as navigation attributes in the InfoCube for incoming royalties and the collective Multicube for the license sales contract and incoming royalties. Attributes are updated using the 0IPM_SALES_CONTR_I InfoSource (from ODS 0IPM_DS01) when the transaction data is loaded.

Hierarchical attributes for IP rights dimensions

Any hierarchical attributes can be assigned to the IP rights dimensions in the IPM Customizing settings to define the rights characteristics. To make these available for the evaluation, hierarchy DataSources are provided, which determine the associated hierarchy for a dimension dynamically according to the Customizing settings. The same dynamic procedure applies for attribute texts for the IP rights dimensions

DataSources for the IP rights dimensions hierarchies

  • 0IPM_RDIM01_HIER,,IP rights dimension 1
  • 0IPM_RDIM02_HIER,,IP rights dimension 2
  • 0IPM_RDIM03_HIER,,IP rights dimension 3
  • 0IPM_RDIM04_HIER,,IP rights dimension 4
  • 0IPM_RDIM05_HIER,,IP rights dimension 5
  • 0IPM_RDIM06_HIER,,IP rights dimension 6

DataSources for extracting descriptions of hierarchical attributes

  • 0IPM_RDIM01_TEXT,,IP rights dimension 1
  • 0IPM_RDIM02_TEXT,,IP rights dimension 2
  • 0IPM_RDIM03_TEXT,,IP rights dimension 3
  • 0IPM_RDIM04_TEXT,,IP rights dimension 4
  • 0IPM_RDIM05_TEXT,,IP rights dimension 5
  • 0IPM_RDIM06_TEXT,,IP rights dimension 6

The description of InfoObjects for IP rights dimensions (0IPM_DIM01 - 0IPMDIM06) is based on the IPM Customizing settings for dimensions 1-3. These should be adjusted as required in SAP BW according to the way in which the rights dimensions are used:

  • 0IPM_RDIM01,,IP rights dimension (language)
  • 0IPM_RDIM02,,IP rights dimension (market)
  • 0IPM_RDIM03,,IP rights dimension (territory)






ABAP Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 17651 Date: 20240520 Time: 232910     sap01-206 ( 329 ms )