Kontakt

Ansicht
Dokumentation

CRM_IPM_TRANSTIERCON - Configure Transaction Tiering

CRM_IPM_TRANSTIERCON - Configure Transaction Tiering

TXBHW - Original Tax Base Amount in Local Currency   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

You can use transaction tiering to calculate outgoing royalties when the system must consider the order of the transactions to assign them to scale levels (tiers).

If you wish to use transaction tiering, the royalty agreement in the license acquisition contract must be defined as follows:

  • Indicate that the royalty rate be calculated using one of the following methods:
  • As a percentage of the sales volume, whose value is scaled according to the number of units sold (for example, royalties of 8% are awarded for sales of the 1st to 1000th unit, while royalties of 10% are awarded for sales of the 1001st unit onward

  • As a percentage of the sales volume, whose value is scaled according to the total money received (for example, royalties of 8% are awarded for saled up to $10,000, while royalties of 10% are awarded for sales above $10,000)

  • As an amount whose value is scaled according to the number of units sold (for example, royalties of $0.80 per unit are awarded for sales of the 1st to 1000th unit, while royalties of $1.00 per unit are awarded for sales of the 1001st unit onward.

  • You have created the data values needed for royalties calculation in Customizing activity Define Data Values.
  • You have created the condition types to use in the royalties calculation in Customizing activity Create Condition Types. For transaction tiering, the condition type must use scale type Graduated-to interval scale.

In the standard system, the following condition types are available for transaction tiering:

  • 17TG (License Fee Gross Retail Price Transaction Tiering)
  • 17TN (License Fee Net Retail Price Transaction Tiering)
  • 17TV (License Fee Net Value Transaction Tiering)

These condition types are included in the condition groups 1703 (IPM Trans Tier Head) and 1704 (IPM TransTiering Itm), and the pricing procedure 17IP16 (PM Trans. Tiering Bill. Doc.) in the standard system.

General Settings

  • Condition types that use transaction tiering

  • Data values used as the royalty basis and the scale basis

  • When the system resets the scale basis

To do so, proceed as follows:
  1. Create an entry for each condition type that uses transaction tiering.
  2. Enter a data value for the royalty scope.
  3. Enter a cumulation scope for the scale basis. This defines when the system resets the scale basis.
Note
If you enter ITD: Inception to Date, the system never resets the scale basis.
  1. Enter a data value for the scale basis.

Settings for License Acquisition Contracts

  • In Customizing activity Define and Assign Groups of Condition Tables and Types, define the condition groups and assign the condition groups to the transaction types and item categories relevant for transaction tiering. If they suit your business requirements, we recommend using the condition groups available in the standard system:
  • 1703 (IPM Trans Tier Head)for the header

  • 1704 (IPM TransTiering Itm)for the item

Otherwise, you can create your own condition groups and assign the condition types the user can enter in the license acquisition contract. Assign the condition groups to the transaction types or item categories.
  • If you wish to use tiering groups, you must activate the Tiering Groupfield. This allows several scopes in a contract to share the same scale basis. To activate this field, proceed as follows:
  1. In the BSP WD Workbench (transaction BSP_WD_CMPWB), enter component IPMRIRO and the enhancement set you are using.
  2. Choose Display.
  3. Ensure that Component Structure Browser is selected, and expand Views.
  4. Double-click the IPMRIRO/EPGenData view and select the Configuration tab page.
  5. Select the Choose Configurationbutton to display the Configuration Selection window.
  6. Double-click on the configuration key BT231_ACQC (Object Type) RIRO_ROY (Object Subtype).
  7. When you return to the main window, choose Show Available Fields.
  8. When the Available Fieldspane is displayed, expand the RCTRLIcontext node.
  9. Add the Tiering Group field from the RCTRLI context node.
  10. Repeat the above steps to add the Tiering Group field for the following additional configuration keys:
Object Type Object Subtype
BT231_ACQC RIRO_ROY_DIST
BT231_ACQC ROSCOPE_ROY
BT231_ACQC ROSCOPE_ROY_DIST

  1. Save your settings when you are finished.

Settings for Billing

  • In Customizing activity Configure Application, activate the IPM: Transaction Tiering (IPM_TIER) feature in the Billing Engine application IPMO and generate the Billing Engine application.
  • Within the IPM_TIER feature, you can determine where the condition types for transaction tiering appear within the pricing procedures used for billing due list items (typically the same pricing procedure is used for the billing due list and billing document). In the standard system, the condition types for transaction tiering appear in levels 100 - 105.

    If you want to use more than or fewer than six condition types for transaction tiering or if you want to start at a different level, change the values of the feature variables TIER_STEPand TIER_STEPS accordingly. To do so, proceed as follows:

  1. Open the Billing Engine Navigator (transaction CRM_IPM_BEFN).
  2. Go to IPMO → Object → DL → Feature.
  3. In the Context Menu for Feature, select Switch to All Features.
  4. To access the feature variables for the IPM_TIER feature, select the node feature below IPM_TIER. Switch to change mode if required.
    1. For the feature variable TIER_STEP, enter the value of the first level in a pricing procedure in which a condition type for transaction tiering appears.
    2. For the feature variable TIER_STEPS, enter the number of levels in which condition types for transaction tiering appear, starting with the first level defined above.
    3. Save your settings.
    4. Generate the Billing Engine application IPMO.
  • In Customizing activity Create Pricing Procedure, you define the pricing procedure used for billing documents that use transaction tiering for royalties calculation. When you create the pricing procedure, you must take into account the settings made for the feature variables described above. If you use more than one pricing procedure, ensure that the condition types for transaction tiering are assigned to the same levels in all pricing procedures used for billing due list items.
  • In the standard system, transaction sorting is based on the date field (DATE_TX). To change the sorting, proceed as follows:

  1. Open the Billing Engine Navigator (transaction CRM_IPM_BEFN).
  2. Go to IPMO → Object → DPL → Container → DPLI → Usages → IPMTSRT.
  3. In the context menu for Usages, select Switch to All Usages.
  4. Select Usages and switch to edit mode, if required.
  5. To create a new usage, select Createin the context menu for Usages.
  6. Enter an ID for the new usage (example: ZIPMSRT).
  7. Enter A in the Attribute Assignmentfield.
  8. Enter X in the Relevant to Generation field.
  9. Enter IPMTSRT in the Enhanced Usage field.
  10. Enter a description for the new usage (example: IPM: Changed Sorting of DPLI entries TT).
  11. Save your settings.
  12. Go back to the Metadata Entityview.
  13. In the context menu for Usages, select Field List.
  14. Switch to change mode if required.
  15. Create new entries for all fields that the system must recognize during sorting.
  16. Enter the new usage in the Usage field.
  17. Enter a sorting sequence.
  18. The lowest value is considered first for sorting. If you do not enter a value in the Sorting Sequence field, the system does not consider this field during sorting.
  19. If the system should no longer consider the DATE_TX field, remove the value 1for the sorting sequence for this entry.
  20. Save your settings.
  21. Generate the Billing Engine application IPMO.
BT231_ACQC

The example below demonstrates a simple case of transaction tiering and how the royalty calculation differs from the standard calculation:

Royalty agreement:

  • For up to 1,000 units, it is 8% of the sales.
  • For more than 1,000 units, it is 10% of the sales.

Sales:

  • You initially sell 600 units for 20 USD each.
  • You then sell 600 units for 10 USD each.

If transaction tiering is inactive, you can still use scales in the system, but the system does not take into account the order of the transactions. Instead, a sort of averaging is performed in the calculation. In this case, the calculation is as follows:

  • Total number of units: 1,200
  • Condition basis (total sales): 600 (units) * 20 (price) + 600 (units) * 10 (price) = 18,000
  • Royalties calculation: 15,000 USD (sales) * 8% + 3,000 USD (sales) *10% = 1,500 USD (total royalties)

If you activate the transaction tiering feature, the system then takes the order of the transactions into account. For the same royalty agreement and sales, the calculation is now as follows:

  • Condition basis (total sales) for the first 1,000 units: 600 (units) *20 USD (price) + 400 (units) *10 (price) = 16,000
  • Condition basis (total sales) for the next 200 units: 200 * 10 = 2,000
  • Royalty calculation: 8% of 16,000 + 10% of 2,000 = 1,480 USD (total royalties)






General Material Data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 14783 Date: 20240523 Time: 164623     sap01-206 ( 172 ms )