Defining Condition Types for IPM
The following table contains the SAP Customizing settings supplied for Intellectual Property Management. These settings provide you with examples of the Customizing requirements and ensure that the functions run correctly.
If you want to modify these settings according to the requirements of your media company, choose the following path in the SAP Implementation Guide (IMG): Customer Relationship Management ® Basic Functions ® Pricing ® Define Settings for Pricing ® Create Condition Types
...
1. Analyze the SAP Customizing settings provided.
2. Copy the Customizing settings provided and create your own Customizing entries in the customer namespace.
All IPM-specific objects in pricing start with 17*.
Table 1:
Condition Type |
Description |
17B0 |
Basis: NetValuePBPOR |
17B1 |
Basis: Net Value OR |
17B2 |
Basis: Sales Vol. IR |
17B3 |
Basis: Adv.Costs IR |
17CO |
Costs OR |
17FI |
Fixed License Fee IR |
17FO |
Fixed License Fee OR |
17G1 |
Target License Total OR |
17G2 |
Actual License Total OR |
17G3 |
Negative Target License Total OR |
17G4 |
Negative Actual License Total OR |
17G5 |
Target License Total IR |
17G6 |
Actual License Total IR |
17G7 |
Negative Target License Total IR |
17G8 |
Negative Actual License Total IR |
17PB |
PBP Per. w/ Qty OR |
17PI |
License Fee (Perc.) IR |
17PO |
License Fee (Perc.) OR |
17PS |
Basis: ProdSale OR |
17QI |
License Fee (Qty.) IR |
17QO |
License Fee (Qty.) OR |
17R1 |
Reserve Rate OR |
17R2 |
Reserve Release Rate OR |
17R3 |
Reserve to be Released OR |
17R4 |
Released Reserve OR |
17R5 |
Remaining Reserve OR |
17RI |
Revenue IR |
17S2 |
Retention Unrecouped AD OR |
17S6 |
Retention Unrecouped AD IR |
17SI |
License Fee (Scale) IR |
17SO |
License Fee (Scale) OR |
17TI |
Quantity Price (Scale) IR |
17TO |
Quantity Price (Scale) OR |
17V1 |
Advance OR |
17V2 |
Recouped AD OR |
17V3 |
Unrecouped AD OR |
17V4 |
Roy.for Clrg OR |
17V5 |
Advance IR |
17V6 |
Recouped AD IR |
17V7 |
Unrecouped AD IR |
17V8 |
Roy.for Clrg IR |
17V9 |
Recouped Advance Stat. |
17VA |
Recouped Advance |
Condition Types With Scales and Interval Scales
Scales can be recorded for the condition types 17PI License Fee (Perc.) IR and 17QI License Fee (Quantity) IR for percentage or quantity-dependent prices. This increases or reduces the condition amount according to the condition agreement. This is the percentage rate from the gross value – with the gross value (the price per quantity can also be increased or reduced).
This type of condition only produces one amount, i.e.
● 17PI) x % of the total gross value or
● 17QI) x $ for each unit for the total quantity
If a scale level is exceeded, a scale jump occurs, since the higher or lower amount is applied to the entire scale base.
If condition amounts in the individual scale levels are only to be applied to a proportion of the respective scale level, you should use condition types 17SI License fee (scale) IR or 17TI Quantity price scale IR with interval scales instead. This creates conditions such as:
● (17SI) x % for the first $10 000, y % for the share of the gross value that exceeds $10 000 or
● (17TI) x $ for the first 100 units, y $ for each additional unit.
Condition types have the value D (interval scale) in the Scale Type field.
You cannot enter this value manually. You should therefore copy the example condition types provided if you require your own condition types with interval scales.
The gross value is used as the scale base for a sales volume scale (17PI or 17SI). This is the total of all conditions (including statistical), which are found at a lower level than the sales volume scale condition type in the pricing procedure.
It is not possible to only include specific condition types (such as from level x to level y) in the sales volume scale base.
The quantity that was transferred to pricing is used as the scale base for a quantity scale (17QI or 17TI). This is provided from a data value that is defined in Customizing. The pricing interface also contains fields for the gross and net weight etc., which can also be used as a scale base in other condition types, if these condition types have a corresponding value in the Reference Value field. Entries can be made in these fields in the pricing interface specifically in the BAdI Influence Technical Communication Structure for Pricing (CRM_PRIDOC_COMM_BADI) from the license sales contract.
If interval scales are used, the scale base cannot be negative. A negative condition type is handled in the same way as its (positive) absolute amount.
In addition to the condition types described here for incoming royalties (whose description ends in I), there are also similar condition types for outgoing royalties (whose description ends in O).
Use the BAdI Pricing Map Billing Document (/1BEA/IPMO_BD_PRC) for outgoing royalties (similar to the BAdI CRM_PRIDOC_COMM_BADI for incoming royalties.
Statistical Condition Types for SAP CO-PA
If you have activated SAP CO-PA, proceed as follows to update the billing values in Profitability Analysis:
● Conditions that are relevant to revenue 17FI Fixed License Fee IR, 17PI License fee (Percentage) IR, 17QI License Fee (Quantity) IR etc. are posted from license revenues to a balance sheet account for accrued revenues during billing if you are using the Accrual Engine. They are only entered in profit and loss accounting (to the P&L account for revenues) after revenue recognition has been performed. Since the assigned balance sheet account cannot be created as a revenue cost element (it can only be created as a statistical cost element, these conditions cannot be directly allocated to the Revenues value field in SAP CO-PA.
An additional statistical condition type 17RI Revenue IR, which is evaluated in the price document using the total for all revenues, is therefore also available. This is the only condition that is allocated to the Revenues value field in SAP CO-PA. Since this condition is statistical, it is not admissible without an assignment to a revenue cost element. It would also be possible to use several of these statistical condition types, which allocate several subtotals from the price document to different SAP CO-PA value fields.
If you are not using the Accrual Engine, and conditions that are relevant to revenue are posted directly to revenue cost elements, these condition types must be assigned to a value field for revenues in SAP CO-PA. In this case, the condition type 17RI Revenue IR cannot be assigned to the value field either.
The same applies to the expense-relevant cost elements 17FO, 17PO, 17QO and the statistical condition type 17CO, if the account to be posted has been created as the revenue cost element. If you have created the accounts to be posted as primary cost elements, you cannot assign the cost elements 17FO, 17PO and 17QO to a value field in SAP CO, since primary cost elements cannot be posted from billing. You must always use the statistical condition type 17CO in this situation.
The condition types listed in the following table are also supplied for the Author Relationship Management scenario. For more information, see Best Practices for the Author Relationship Management Scenario.
Table 2:
Condition Type |
Description |
17P1 |
Gross retail price OR |
17P2 |
Net retail price OR |
17PG |
Lcnse Fee Gr.Lpr. OR |
17PN |
Lcnse Fee Net Lpr.OR |
17PV |
Lcnse Fee Net Value OR |