Configure Settlement (SAP Library - SAP for Media: Documentation for Solution Manager Content)

Configure Settlement

You can use this procedure to implement the Author Relationship Management scenario and create a system landscape for this scenario, which covers the general requirements of a book publisher described in the Best Practices for the Author Relationship Management document. The configuration steps required for royalties settlement using the Billing Engine are listed here. Any additional requirements require additional configuration steps.

Adjust BE Application for Settlement of Outgoing Royalties

To perform the royalties settlement, you must make customer-specific adjustments to the IPMO Billing Engine application supplied. (These adjustments apply to all clients.)

The customer-specific aspects of the application are the rights type and market attributes and the royalties dimensions, which define the royalties to be paid. In conjunction with the IP sold, these attributes make up the royalties key. Each ‘raw line’, which describes a right or physical product sold, also contains the transaction key of the royalties-relevant business transaction and a date in addition to the royalties key. These three components identify the raw lines, and therefore create the logical key for a raw line in the settlement data collector. Each raw line is assigned several data values in the non-key part, (which are distinguished by the data value). A customer-specific application is only distinguished from other applications by the selection of the attributes for the royalties key.

Prerequisites

Attributes for the Royalties Key

Attributes are created during product master data maintenance. The attributes that belong to the royalties key must be defined as rights dimensions, and are assigned a number between 1 and 6 for order processing.

Procedure

...

1. Include Attributes for the Royalties Key (CRM)

To include the attributes of the royalties key in the application, you must create a customer-specific feature and a usage.

To make this setting, choose the following path in the SAP Implementation Guide (IMG):Customer Relationship Management ® Industry-Specific Solutions ® Media ® Intellectual Property Management ® Billing and Settlement ® Outgoing Royalties ® Adjust Billing Engine Application for Settlement of Outgoing Royalties

Proceed as follows:

a. In the BE Framework Navigator, select the node IPMO -> Object DPL -> Feature from the Metadata Entity tree structure, and Switch to All Features in the context menu. Select the node Feature and Create in the context menu to create a customer-specific feature with a preceding feature IPMROYKEY (enter a name in the Feature field, which is ZIPMROYKEY in the customer namespace).

Table 1: Royalties Key Feature (ZIPMROYKEY)

Field	Value
Feature	ZIPMROYKEY
Preceding feature	IPMROYKEY
Service
Can be inherited

b. Select the Feature Attribute node in the tree structure below the feature you have just created and Display List in the context menu. Insert the IP attribute, which is inherited from the preceding feature IPMROYKEY in the table shown, and add your customer-specific attributes for the royalties key. Choose field names in the customer namespace and specify the attribute name that was used to define the rights dimensions as the data element. Save your entries.

Table 2: Attributes for Feature ZIPMROYKEY

Feature	Field Name	Data Element
ZIPMROYKEY	RIGHTSTYPE	ZRIGHTSTYPE
ZIPMROYKEY	MARKET	CRMT_IPM_MARKET
ZIPMROYKEY	ROYDIM	ZROYDIM
IPMROYKEY	IP	COMT_PRODUCT_GUID

c. After pressing Refresh in the tree structure for every feature attribute added, choose the Feature node [feature you have just created] -> Feature Attribute [feature attribute added] -> Container and Display List in the context menu to add an entry with the container DPLI.

Table 3: DPLI Container for Feature Attribute

Container	Feature	Field Name
DPLI	ZIPMROYKEY	RIGHTSTYPE
DPLI	ZIPMROYKEY	MARKET
DPLI	ZIPMROYKEY	ROYDIM

d. Use the blue arrow in the top left hand section of the screen above the tree structure to navigate back to the previous tree structure Application, and choose the node Application IPMO -> Object DPL -> Feature and Create Assignment in the context menu to enter the feature you have just created (do not make an entry in the Inactive field).

Table 4: Assign Feature ZIPMROYKEY to Object DPL

Field	Value
Application	IPMO
Object	DPL
Feature	ZIPMROYKEY
Inactive

e. Choose the following node: Application IPMO -> Object DPL -> Container DPLI -> Usages, and Switch to All Usages in the context menu. Choose the Usages node and Create in the context menu to create a customer-specific usage with Attribute Assgmt. A, Rel.to Generation X and Enhanced Usage IPMROYK (enter the name of the royalties key in the Usage field. Do not make an entry in the Sel./Block Relevance field).

Table 5: Create Customer-Specific Usage in the DPLI Container

Field	Value
Use	ZIPMROY
Attribute Assgmt.	A
Rel.to Generation	X
Sel./Block Relevance
Enhanced Usage	IPMROYK
Description	Royalties key

f. Use the blue arrow in the top left hand section of the screen above the tree structure to navigate back to the previous tree structure Application, and choose the node Application IPMO -> Object DPL -> Container DPLI -> Usages and Field List in the context menu. Add entries to the table displayed with the usage that you created in step 5. You should add an entry for every field name that you added to the feature attributes in step 2, and assign the DPLI container in each case (you can use any sort sequence here, but do not use the value 0). Save your entries.

Table 6: Attributes for Usage ZIPMROY

Applic.	Object	Usage	Container	Field Name	Sort Seq.
IPMO	DPL	ZIPMROY	DPLI	IP	1
IPMO	DPL	ZIPMROY	DPLI	RIGHTSTYPE	2
IPMO	DPL	ZIPMROY	DPLI	MARKET	3
IPMO	DPL	ZIPMROY	DPLI	ROYDIM	4

3. Assign Account Assignment-Relevant Attributes (CRM)

If you want to distribute the license fees you have settled between several expense accounts or CO-PA objects during the transfer to Accounting (via Service Mapping IAT), you should also assign the account assignment-relevant attributes to an additional customer-specific feature. Creating this additional feature is optional and is only required if several expense accounts are to be used.

To make this setting, choose the following path in the IMG: Customer Relationship Management ®Industry-Specific Solutions ® Media ® Intellectual Property Management ® Billing and Settlement ® Outgoing Royalties ® Adjust Billing Engine Application for Settlement of Outgoing Royalties

Repeat the steps a) to f) listed above with the following variations:

a. In the BE Framework Navigator, select the node IPMO -> Object DL -> Feature from the Metadata Entity tree structure, and Switch to All Features in the context menu. Choose the Feature node and Create in the context menu to create a customer-specific feature ZIPMROYACS with a preceding feature IPMROYACS.

Table 7: Account Assignment Key Feature (ZIPMROYACS)

Field	Value
Feature	ZIPMROYACS
Preceding feature	IPMROYACS
Service	[initial]
Can be inherited	[initial]
Description	Account assignment

a. Select the Feature Attribute node in the tree structure below the feature you have just created and Display List in the context menu. Insert the IP attribute, which is inherited from the preceding feature IPMROYACS, and add your customer-specific attributes for the account assignment set according to the table below. Save your entries.

Table 8: Attributes for Feature ZIPMROYACS

Feature	Field Name	Data Element
ZIPMROYACS	RIGHTSTYPE	ZRIGHTSTYPE
ZIPMROYACS	MARKET	CRMT_IPM_MARKET
ZIPMROYACS	ROYDIM	ZROYDIM

b. After pressing Refresh in the tree structure for every feature attribute added, choose the Feature node [feature you have just created] -> Feature Attribute [feature attribute added] -> Container and Display List in the context menu to add an entry with the container DPSI.

Table 9: DLSI Container for Feature Attribute

Container	Feature	Field Name
DLSI	ZIPMROYACS	RIGHTSTYPE
DLSI	ZIPMROYACS	MARKET
DLSI	ZIPMROYACS	ROYDIM

c. Use the blue arrow in the top left hand section of the screen above the tree structure to navigate back to the previous tree structure Application, and choose the node Application IPMO -> Object DL -> Feature and Create Assignment in the context menu to enter the feature you have just created (do not make an entry in the Inactive field).

Table 10: Assign Feature ZIPMROYACS to Object DL

Field	Value
Application	IPMO
Object	DL
Feature	ZIPMROYACS
Inactive	[initial]

a. Choose the following node: Application IPMO -> Object DL -> Container DLSI -> Usages, and Switch to All Usages in the context menu. Choose the Usages node and Create in the context menu to create a customer-specific usage with Attribute Assgmt. A, Rel.to Generation X and Enhanced Usage IPMROY (enter the name of the account assignment key in the Usage field. Do not make an entry in the Sel./Block Relevance field).

Table 11: Create Customer-Specific Usage in the DLSI Container

Field	Value
Use	ZIPMACS
Attribute Assgmt.	A
Rel.to Generation	X
Sel./Block Relevance
Enhanced Usage	IPMROYA
Description	Account assignment key

b. Use the blue arrow in the top left hand section of the screen above the tree structure to navigate back to the previous tree structure Application, and choose the node Application IPMO -> Object DL -> Container DLSI -> Usages and Field List in the context menu. Add entries to the table displayed with the usage that you created in step 5. You should add an entry for every field name that you added to the feature attributes in step 2, and assign the DPLI container in each case (you can use any sort sequence here, but do not use the value 0). Save your entries.

Table 12: Attributes for Usage ZIPMACS

Applic.	Object	Usage	Container	Field Name	Sort Seq.
IPMO	DL	ZIPMACS	DLSI	IP	1
IPMO	DL	ZIPMACS	DLSI	RIGHTSTYPE	2
IPMO	DL	ZIPMACS	DLSI	MARKET	3
IPMO	DL	ZIPMACS	DLSI	ROYDIM	4

Transfer Media Issue and Profit Center

During account assignment of royalties during the Profitability Analysis, you want perform a distribution between the media issues for the Intellectual Property. The settings that you need to make to ensure that the media issue and profit center are observed in the settlement data collector and the account assignment block are described below.

Caution The functions described here assume use of note 887990.

...

1. Include Media Issue and Profit Center in the Billing Engine (CRM)

Repeat the steps a) to f) listed above with the following variations:

a. In the BE Framework Navigator, select the node IPMO -> Object DL -> Feature from the Metadata Entity tree structure, and Switch to All Features in the context menu. Select the node Feature and Create in the context menu to create a customer-specific feature ZIPMROYAC2 (enter a name from the customer namespace in the Feature field).

Table 13: Account Assignment Key Feature (ZIPMROYAC2)

Field	Value
Feature	ZIPMROYAC2
Preceding Feature	[initial]

Service	[initial]
Can be inherited	[initial]

b. Select the Feature Attribute node in the tree structure below the feature you have just created and Display List in the context menu. Insert the attributes inherited from the preceding feature ZIPMROYACS in the table shown, and add your customer-specific attributes for the account assignment set according to the table below. Save your entries.

Table 14: Attributes for Feature ZIPMROYAC2

Feature	Field Name	Data Element
ZIPMROYAC2	ZZMATNR	ZZMATNR
ZIPMROYAC2	ZZPRCTR	PRCTR

Table 15: DPLI and DLSI Containers for Feature Attribute

Container	Feature	Field Name
DPLI	ZIPMROYAC2	ZZMATNR
DPLI	ZIPMROYAC2	ZZPRCTR
DLSI	ZIPMROYAC2	ZZMATNR
DLSI	ZIPMROYAC2	ZZPRCTR

d. Use the blue arrow in the top left hand section of the screen above the tree structure to navigate back to the previous tree structure Application, and choose the node Application IPMO -> Object DL -> Feature and Create Assignment in the context menu to enter the feature you have just created (do not make an entry in the Inactive field).

Table 16: Assign Feature ZIPMROYAC2 to Object DL

Field	Value
Application	IPMO
Object	DL
Feature	ZIPMROYAC2
Inactive	[initial]

e. Choose the following node: Application IPMO -> Object DL -> Container DLSI -> Usages, and Switch to All Usages in the context menu. Choose the Usages node and Create in the context menu to create a customer-specific usage with Attribute Assgmt. A, Rel.to Generation X and Enhanced Usage ZIPMACS (enter the name of the account assignment key with the SD data in the Usage field. Do not make an entry in the Sel./Block Relevance field).

Table 17: Create Customer-Specific Usage in the DLSI Container

Field	Value
Use	ZIPMAC2
Attribute Assgmt.	A
Rel.to Generation	X
Sel./Block Relevance	[initial]
Enhanced Usage	ZIPMACS
Description	Account assignment key with SD data

f. Use the blue arrow in the top left hand section of the screen above the tree structure to navigate back to the previous tree structure Application, and choose the node Application IPMO -> Object DL -> Container DLSI -> Usages and Field List in the context menu. Add entries to the table displayed with the usage that you created in step 5. You should add an entry for every field name that you added to the feature attributes in step 2, and assign the DPLI container in each case (you can use any sort sequence here, but do not use the value 0). Save your entries.

Table 18: Attributes for Usage ZIPMAC2

Applic.	Object	Usage	Container	Field Name	Sort Seq.
IPMO	DL	ZIPMAC2	DLSI	ZZMATNR	11
IPMO	DL	ZIPMAC2	DLSI	ZZPRCTR	12

g. Use the blue arrow in the top left hand section of the screen above the tree structure to navigate back to the previous tree structure Application, and choose the node Application IPMO -> Object DPL -> Feature and Create Assignment in the context menu to enter the feature you have just created (do not make an entry in the Inactive field).

Table 19: Assign Feature ZIPMROYAC2 to Object DPL

Field	Value
Application	IPMO
Object	DPL
Feature	ZIPMROYAC2
Inactive	[initial]

2. Enter Media Issue and Profit Center in Settlement Data Collector

To use this transaction, choose the following path from the SAP Easy Access menu: Architecture and Technology ® ABAP Workbench ® Development ® ABAP Editor.

a. Create a program ZDPL_ADD_FIELDS. Enter the program name ZDPL_ADD_FIELDS and choose Create. Now enter a description and select the Include Program type. Choose Save. Now enter the package you are using here and choose Save.

Create the following program implementation, save, and activate the program.

*&---------------------------------------------------------------------*

*& Include ZDPL_ADD_FIELDS

*&---------------------------------------------------------------------*

* * Copies the additional fields material and profit center into

* * settlement data collector structure

* *

* ls_dpli_com-zzmatnr = <ls_item>-data-zzmatnr.

* ls_dpli_com-zzprctr = <ls_item>-data-zzprctr.

To make additional settings for the media issue and the profit center in the settlement data collector, choose the following path in the IMG: Customer Relationship Management ®Industry-Specific Solutions ® Media ® Intellectual Property Management ® Billing and Settlement ® Outgoing Royalties ® Adjust Billing Engine Application for Settlement of Outgoing Royalties

b. In the BE Framework Navigator, select the node IPMO -> Object DPL -> Feature -> MWC -> Function Group -> O – Object Layer -> Function Module -> UPLOAD2 -> Event -> DPLOMWC0 -> Subscription from the Metadata Entity tree structure, and Switch to All Subscriptions in the context menu. Choose the Subscriptions node and Create in the context menu to create a customer-specific subscription ZDPLADDFLD with the program name ZDPL_ADD_FIELDS, feature ZIPMROYAC2 and subscription type [initial] .

Table 20a: Assign Feature ZIPMROYAC2 to Object DPL

Field	Value
Subscription	ZDPLADDFLD
Program name	ZDPL_ADD_FIELDS
Feature	ZIPMROYAC2
Replaced Subscr.	[initial]
Subscription type	[initial]
Description	Media issue and profit center in DPLI

d. Use the blue arrow in the top left hand section of the screen above the tree structure to navigate back to the previous tree structure Application, and choose the node you previously selected Application IPMO -> Object DPL -> Feature -> MWC -> Function Group -> O – Object Layer -> Function Module -> UPLOAD2 -> Event -> DPLOMWC0 -> Subscription and Create Assignment in the context menu to enter the subscription you have just created ZDPLADDFLD and sort sequence 900.

e. Save your entries.

3. Enter Media Issue and Profit Center in Account Assignment (CRM)

a. Choose the following path in the IMG: Customer Relationship Management ® Industry-Specific Solutions ® Media ® Intellectual Property Management ® Billing and Settlement ® Outgoing Royalties ® Maintain Business-Add-Ins.

b. Double click on the IPMO application to select it.

c. Double click on the BAdI for the Billing Due List BadI definition to select it.

d. Choose Implementation ® Create in the menu.

e. Enter Z_ADD_FIELDS_DL as the implementation name.

f. Select the Interface tab page and access the editor by double clicking on ACCOUNT_KEY method.

g. Enter the following coding for the ACCOUNT_KEY method, save and activate it:

method /1BEA/IF_EX_IPMO_DL~ACCOUNT_KEY.

cs_royacs-zzmatnr = is_dpli-zzmatnr.

cs_royacs-zzprctr = is_dpli-zzprctr.

h. Endmethod.

i. Save and activate the implementation.

Incorporate Unit Tiering Functions

Incorporate the functions for sales-based royalties settlement with a quantity scale (unit tiering) according to note 906946. Creating condition types, pricing procedures and configuring data values is described below.

Activate Enhanced Account Determination Feature (CRM)

You activate the Enhanced Account Determination Feature (ACD) for the Billing Document (BD) object, if you want to use enhanced revenue account determination instead of standard revenue account determination to transfer billing documents to Accounting.

Enhanced revenue account determination uses the condition technique to determine a symbolic account key. It overrides standard revenue account determination.

...

1. In the BE Framework Navigator, select the node Application IPMO -> Object BD -> Feature -> ACD from the Metadata Entity tree structure, and Activate Feature in the context menu.

2. Save your entries.

Generate Application (CRM)

Once you have made all customer-specific changes, choose the node Application -> IPMO and a generation function in the context menu.

Organizational Management for Royalties Settlement

Prerequisites

You have already created your organizational structure in CRM. For more information, see Configure Organizational Data .

Procedure

...

1. Create Billing Unit

In this step, you create your billing unit. See the general notes on Represent License Acquisition Scenario for IPM.

To execute this transaction, choose the following path in the SAP Easy Access menu: Master Data ® Business Partners ® Maintain Business Partner.

Proceed as follows:

a. Create a new business partner of the Organization type.

b. Choose Create in BP Role Billing Unit.

c. Maintain the address and control data.

d. Save your billing unit.

2. Assign Billing Units to Sales Organizations (CRM(

In this step you define which billing unit is determined from the respective sales organization.

To make this setting, choose the following path in the IMG: Customer Relationship Management ® Master Data ® Organizational Management ® Cross-System Assignment of Organizational Units® Assign Billing Units to Sales Organizations

Assign the sales organization for royalties acquisition to your billing unit.

3. Assign Company Codes to Billing Units (CRM)

In this activity you define which company code is determined from the respective billing unit. This applies to royalties contracts in CRM, which are billed in CRM and posted as billing documents in SAP ERP Financial Accounting (FI).

Pricing

...

1. Create Condition Types (CRM)

In this step you use the condition type to define the features, field combinations and commercial significance of condition records.

To make this setting, choose the following path in the IMG: Customer Relationship Management ® Basic Functions ®Pricing ® Define Settings for Pricing ® Create Condition Types.

You create the condition types listed in the following table in addition to the condition types supplied by SAP. You should only create the condition types ZZZY and ZZZZ if you want to prevent settlement being performed for negative royalties as described in note 909000.

Note Note that you can create the condition types ZTP1, ZTP2 and ZTP3 as a copy of condition type 17PO. However, you must the modify the data record source, access sequence and condition class.

Table 20: Additional Condition Types

Condition Type	Copying From	DR Source	Access Sequence	Condition Class	Calculation Type	Leading Sign
ZTB1	17B1	IPM: Basic value (J)	None	Surcharges and discounts (A)	Fixed amount (B)	Positive and negative ( )
ZTB2	17B1	IPM: Basic value (J)	None	Surcharges and discounts (A)	Fixed amount (B)	Positive and negative ( )
ZTB3	17B1	IPM: Basic value (J)	None	Surcharges and discounts (A)	Fixed amount (B)	Positive and negative ( )
ZTP1	17PO	Customer reserve 1 (X)	None	Surcharges and discounts (A)	Percentage (A)	Positive (A)
ZTP2	17PO	Customer reserve 1 (X)	None	Surcharges and discounts (A)	Percentage (A)	Positive (A)
ZTP3	17PO	Customer reserve 1 (X)	None	Surcharges and discounts (A)	Percentage (A)	Positive (A)
ZZZX	ZZZZ	IPM: Basic value (J)	None	Surcharges and discounts (A)	Fixed amount (B)	Positive and negative ( )
ZZZY	17G3	Condition technique (new) (A)	None	Surcharges and discounts (A)	Percentage (A)	Positive and negative ( )
ZZZZ		IPM: Basic value (J)	None	Surcharges and discounts (A)	Fixed amount (B)	Positive and negative ( )

2. Create Pricing Procedure (CRM)

In this step, you define the pricing procedures for the royalties contract and royalties settlement. The pricing procedure defines valid condition types and the sequence in which they are calculated in the transaction.

To make this setting, choose the following path in the IMG: Customer Relationship Management ® Basic Functions ®Pricing ® Define Settings for Pricing ® Create Pricing Procedure.

Create a pricing procedure in the customer namespace according to note 906946. Perform the following steps:

a. Copy the pricing procedure supplied by SAP IPM Fee Billing Document(17IP13) by selecting 17IP13 and choosing Copy As … .

b. Enter a 6 digit key for your pricing procedure in the customer namespace (e.g. ZIPM13) and an explanatory text and choose Copy.

c. Choose Copy All in the dialog box that appears.

d. Select the new entry and choose Control in the dialog structure.

e. Select all entries with a level less than 200 and choose Delete.

f. Choose New Entries and enter these for the levels 10 to 190 according to the following table. You should only enter the levels 180 to 190 (condition types ZZZX, ZZZY and ZZZZ) if you want to prevent settlement being performed for negative royalties as described in note 909000.

g. The system makes entries in the counter and usage fields automatically when the data release as part of the condition technique.

h. Save the pricing procedure.

Table 21: Pricing Procedure

Level	Condition Type	From	Statistical	Subtotal	Calculation Formula	Basic Formula
10	ZTB1		X
20	ZTB2		X
30	ZTB3		X
110	ZTP1	10
120	ZTP2	20
130	ZTP3	30
160	17PV		X
161	17PN		X
162	17PG		X
180	ZZZX		X
185	ZZZY	180				28
190	ZZZZ			1	15
200	17V1
210	17V3		X	3
220	17V4		X
250	17V2
270	17S2
400	17FO
900	17CO		X		2
920					4

3. Define Data Values (CRM)

In this step, you define the data values. You can use data values to convert data from external systems, such as the gross retail price of the book sold from SAP SD to pricing in the CRM System.

To make this setting, choose the following path in the IMG: Customer Relationship Management ®Industry-Specific Solutions ® Media ® Intellectual Property Management ® Basic Functions ® Pricing ® Define Data Values.

SAP provides the following data values:

○ External: Gross Retail Price Prod.Sold (/PGP)

○ External: Net Retail Price Prod.Sold (/PNP)

○ External: Net Value of the Product Sale(/SD0)

○ External: Number of Product Sales (/SD1)

○ Gross Retail Price for Product Sold (3PGP)

○ Net Retail Price for Product Sold (3PNP)

○ Net Value of the Product Sale (3PS0)

○ Number of Product Sales (3PS1)

Check that the data values 3PGP, 3PNP, 3PS0 and 3PS1 have the value Relevant or Relevant to Division in the Accounting Set field.

To ensure that royalties are distributed between the media issues involved during the transfer to Profitability Analysis (see also Transfer Media Issue and Profit Center), you must define one of the data values as Relevant to Division.

Choose the data value (such as Gross Retail Price for Product Sold (3PGP)) and then Details. Choose Relevant to Division for the Accounting Set and save your entries.

Note If you want to select several data values as being relevant to division to represent different scenarios, you should restrict to the corresponding billing item category in each case.

Check that the data values 3PGP, 3PNP, 3PS0 and 3PS1 have entries assigned for the ITD and PP scopes under Usage of Values.

Describe Price Basis:

The Gross Retail Price of Product Sold (3PBP)describes the price printed on the book. The gross retail price is significant for end customers.

The Net Retail Price of Product Sold (3PNP) describes the price printed on the book with the VAT deducted.

The Net Value of the Product Sale (3PS0) describes the net price that the bookshop has to pay to purchase the book. This price is defined by the discount granted to the bookshop.

4. Assign Condition Types to Data Values

You have created a maintenance dialog according to note 906946. Access this using transaction SM30 and assign condition types for usage with unit tiering to the data values according to the following table:

Table 22: Pricing Procedure

Data Value	Scope	Condition Type
3PGP	ITD: From inception to date (A)	17PG
3PNP	ITD: From inception to date (A)	17PN
3PS0	ITD: From inception to date (A)	17PV

Billing and Settlement

...

1. Number Ranges: Define Number Range for Billing Documents/Define Number Range for Collective Runs (CRM)

In this step, you define the number range intervals in the number range for billing documents and the number range for collective runs.

To make this setting, choose the following path in the IMG: Customer Relationship Management ® Billing ® Number Ranges ® Define Number Range for Billing Documents or.

Customer Relationship Management ® Billing ® Number Ranges ® Define Number Range for Collective Runs

To define a number range, you must insert a new number interval. To do this, proceed as follows:

a. Choose the application IPM Outgoing Royalties (IPMO).

b. Create a new interval. Enter an alphanumeric key with a maximum of two digits.

c. Specify the limits for the number interval. Individual number intervals must not overlap. Each number can therefore only appear once.

d. If the number range is intended for external number assignment, indicate this accordingly.

e. Now enter the key for the number range in the billing types, see also Define Billing Types for Royalties Settlement.

2. Define Billing Types for Royalties Settlement (CRM)

In this step you define the billing types for royalties settlement to define the features and characteristics of a settlement document (such as an invoice, credit or debit memo).

a. Create a new billing type OR Royalties Settlement (ZOR1).

b. Choose the application IPM Outgoing Royalties (IPMO). Copy the standard billing type OR Standard (OR01). Maintain the number range intervals and assign the pricing procedure you have created (e.g. ZIPM13).

3. Define Item Categories for Royalties Settlement (CRM)

In this step you define the item categories for royalties settlement.

Create new item categories.

Choose the application IPM Outgoing Royalties (IPMO). Copy the item categories in the system and create new ones according to the table below. Make the following changes:

○ Billing type = OR royalties settlement (ZOR1)

○ Pricing procedure = <Pricing procedure you created (e.g. ZIPM13)>

Table 21: Item Categories for Royalties Settlement

Template Item Category	Template Description	Target Item Category	Target Description
IEA1	Advance item (purchasing)	ZEA1	Advance item (royalties)
IEA2	Final Inv.Trgt Advance (Acqu.)	ZEA2	Final Inv.Trgt Advance (Royalties.)
IEB1	BRI (Purchasing)	ZEB1	BRI (royalties)
IEB2	BRI (DiffCalc) (Purchasing)	ZEB2	BRI (DiffCalc) (royalties)
IEM1	Royalties Item (Purchasing)	ZEM1	Royalties item (royalties)

4. Determine Item Categories for Royalties Settlement (CRM)

In this step you assign a combination of the transaction type (process type for the source application and the item category of the relevant royalties contract to the item category in CRM Billing.

Choose the application IPM Outgoing Royalties (IPMO). Copy the entries supplied for the SAP IPM Acquisition Contract (IPME) transaction type to your new royalties contract transaction type (ZIME) according to the following table.

Table 22: Item Category Determination for Royalties Settlement

Source Process Category	Source Item Category	Billing Item Category
ZIME	IEA1	ZEA1
ZIME	IEA2	ZEA2
ZIME	IEB1	ZEB1
ZIME	IEB2	ZEB2
ZIME	IEB3	ZEA1
ZIME	IEM1	ZEM1

5. Edit Clearing Control

In this step you define the way in which advances and minimum guarantees are handled during royalties settlement.

Choose the application IPM Outgoing Royalties (IPMO). Create entries for read rules, update rules, clearing, referenced item categories, and clearing: sort sequence according to the following tables:

Table 23: Read Rules

BItmCat.	Data Value	ItmCatRef	SourceItemCat	Requirement
ZEA1	2OA1	Current billing due list item ('self')
ZEA1	2OA2	Originating item for clearing ('orig')
ZEA2	2OA4	Current billing due list item ('self')
ZEB2	2OA2	Originating item for clearing ('orig')

Table 24: Update Rules

BItmCat.	Field Name	Condition	Data Value	ItmCatRef	SourceItemCat	Requirement
ZEA1	NET_VALUE		2OA1	Current billing due list item ('self')		1OA1
ZEA1	NET_VALUE		2OA2	Originating item for clearing ('orig')
ZEA1	NET_VALUE		2OA4	BEA item category	ZEA2
ZEB2	NET_VALUE		2OA2	Current billing due list item ('self')

Table 25: Clearing: Referenced Item Categories

BItmCat.	ItmCatRef	RefitmCat	Sort Prio.
ZEA2	BEA item category	ZEA1	0
ZEB2	BEA item category	ZEA1	20
ZEB2	Originating item for clearing ('orig')		10

Table 26: Clearing: Sort Sequence

BItmCat.	BDL Item Field Name	Sort Prio.	Sort Direction
ZEB2	BILL_DATE	20	Ascending
ZEB2	NET_VALUE	10	Descending