Show TOC

Function documentationDistribution in License Acquisition Contracts

 

Similarly to revenue distribution (BTA) in the license sales contract, you can use distribution in the License Acquisition Contract to distribute a rights acquisition item between various account assignment objects, such as the IP or market.

If you assign the distribution to an exploitation-dependent item, this overrides the distribution that is produced in the OR data collector from the assigned sales.

Constraints

Once an item has been billed, changes can no longer be made.

Distribution in the license acquisition contract is not transferred to SAP NetWeaver Business Intelligence (BI). This means that contract values for advances and fixed amounts are not distributed. Follow-on applications, such as the Billing Engine, transfer the distributed values to BI.

Prerequisites

Before you can use distribution in the license acquisition contract, you must make the following settings in Customizing:

Activity

Menu Path

Define billing plan types and assign these to item categories

Start of the navigation path Customer Relationship Management Next navigation step Transactions Next navigation step Basic Settings Next navigation step Billing Plan End of the navigation path

Include distribution item in item category determination

Start of the navigation path Customer Relationship Management Next navigation step Transactions Next navigation step Basic Settings Next navigation step Item Category Determination End of the navigation path

If the license acquisition contract contains distribution lines, the system performs the same checks that it performs for revenue distribution (business transaction allocation):

  • The total for all distributed percentage rates must equal 100%.

  • Rights dimensions within distribution must match the rights dimensions in the rights scope. You can influence this check using the Business Add-In CRM_IPM_REVPLAN_DFLT.

  • The product must be part of the product hierarchy for the item product. You can influence this check by implementing the BAdI CRM_IPM_REVPLAN_CHK. This check does not affect existing contracts.

    Note Note

    The product hierarchy check is part of the default implementation. Each implementation of your own changes this.

    End of the note.

  • If a rights dimension contains multiple values, you must enter a distribution.

Note Note

The system only performs the checks above in this situation if a distribution plan is assigned to the item in the license acquisition contract. In contrast to this, the system always performs these checks in the license sales contract, even if no distribution plan is assigned.

End of the note.