Transferring SD Product Sales to the Settlement Data Collector 

Use

To ensure that SAP SD (Sales and Distribution) product sales data from billing documents can be transferred to the settlement data collector, you must perform the configuration steps listed below.

Prerequisites

The system in which SAP SD product sales are entered is connected to an SAP CRM-System as a back-end system.

The back-end system must be an SAP Media System with Release 4.71 or above.

Procedure

Settings in the back-end system

If billed values and quantities from SAP SD product sales are to be used as the basis for calculating outgoing royalties in Intellectual Property Management (IPM), you must make the following settings in the OLTP System:

...

       1.      Subscreen 2060 in function group JPMM must be incorporated in the material master maintenance for all screen sequences used. Position the subscreen on a suitable position on one of the data screens with the Basic data 4v maintenance status.

You make this setting in the SAP Implementation Guide under: SAP Media ® Master Data ® Product ® Media Product Master ® Configure Material Master ® Define Structure of Data Screens for Each Screen Sequence.

In doing so, you can assign an Intellectual Property during maintenance of the material or media product master. The Intellectual Property for the billing item is determined from the Intellectual Property recorded in the material or media product master for the billing item.

       2.      Edit the value tables for the rights and royalties dimensions in the SAP Media System according to the rights and royalties dimensions in the SAP CRM System. SAP supplies the following value tables:

Technical Key	Description
CRMM_IPM_MRKCO	IPM: Rights dimension value table (market)
CRMM_IPM_TRRCO	IPM: Rights dimension value table (territory)
CRMM_IPM_LNGCO	IPM: Rights dimension value table (language)

If you want to use other rights dimensions, you must define your own value tables.

You edit the tables using the Table View Maintenance transaction (SM30).

 

       3.      To determine the following data, you must perform a corresponding Customizing or BAdI implementation:

·         Attributes for the Royalties Key

Two options are available to you for determining attributes:

-          You can define the rules for determining attribute values in the following IMG activity: SAP Media ® Title Lifecycle Management ® Intellectual Property Management (IPM) Integration ® Define Attribute Mapping (ISM_TLM_ATTRMAP).

-          You can define the rules in an implementation of the ISM_ATTRIBUTE_MAP Business Add-In.

 

If the rule for an attribute is not defined in the Define Attribute Mapping IMG activity, the system accesses the Business Add-In.

·         A value or quantity with a currency and unit of measure for each billing item and data value

To determine values and quantities, create an implementation for the Business Add-In ISM_IPM_MAP_BILL_DOC. You can use the example implementation for the data values /SD0 “Net value for product sale” and /SD1 “Number of units for product sale” as a template.

If the BAdI implementation is not created, it is not possible to transfer values or quantities to the OR data collector in CRM.

 

When SAP SD billing documents are updated, the system determines the data required and enters this in the OR data collector.

       4.      SAP provides message type JINV, which is used to control the OR data collector. The message type is used in message procedure V10000. To activate the OR data collector, you must create an output condition record for each billing type for which data is to be transferred to IPM. Do not create output condition records for billing types that are not to be transferred to IPM. You do not for instance create them for invoice lists, since these are not usually included in the royalties calculation.

During saving following Creation, Change or Deletion of a billing document, output control triggers timely transfer of billing documents to the OR data collector.

You edit the output type, output determination procedure and output condition records in the Implementation Guide under: SAP Media ® Basic Functions ® Output Determination ® Output Determination in Media Sales and Distribution ® Define Access Sequences, Output Types and Determination Procedures.

You assign the billing type to the output determination procedure in the Implementation Guide under Sales and Distribution ® Basic Functions ® Output Control ® Output Determination ® Output Determination Using the Condition Technique ® Maintain Output Determination for Billing Documents ® Assign Output Determination Procedures.

For the initial load of the product sales data from the SAP ERP system to the SAP CRM system, the adapter must be maintained in the subscription table for the upload and download. Check that the following entry is maintained in the view “Subscription Table for Upload and Download Objects” (CRMSUBTAB). If the entry is missing, use view maintenance transaction SM30 to enter it manually.

Field Name	Value
User	CRM
Objectn. Download	IPMBEAPRDSLS
Up- or Down	Download
Object Class	IPMBEABDC_CL
Function
Object Type
Function Module	IPMBEARAWREC_EXTRACT
Inactive

 

Settings in the CRM System

If billed values and quantities from SAP SD product sales are to be used as the basis for calculating outgoing royalties in Intellectual Property Management (IPM), you must make the following settings in the CRM System:

       5.      To transfer data from the OR data collector to the IPM settlement data collector, access the initial data transfer for the IPMBEAPRDSLS business object from the SAP Easy Access Menu in the SAP CRM System under: Architecture and Technology ® Middleware ® Data Exchange ® Initial Load ® Start.

...

       1.      The quantities and values that you have entered in the external data values /SD0 “External: Net value for product sale” and /SD1 “External: Number of units for product sale” must be mapped to internal data values in IPM. SAP supplies the internal data values 3PS0 “Net value for product sale” and 3PS1 “Number of units for product sale”.
You perform mapping in the Implementation Guide for the SAP CRM System under Customer Relationship Management ® Industry-Specific Solutions  ® Media ® Intellectual Property Management ® Basic Functions® Pricing ®Define Data Values. The external data value /SD0 or /SD1 is entered in the “Origin from external system” column under “Origin of Values” in the 3PS0 or 3PS1 data values.

       2.      To use these internal data values during pricing for the OR settlement, you must specify a condition type for values in the "Use as a Condition Basis" column and a pricing procedure for quantities in the "Use as a Price Quantity" column in the "Usage of Values“ section in the Implementation Guide for the SAP CRM System under Customer Relationship Management ® Industry-Specific Solutions  ® Media ® Intellectual Property Management ® Basic Functions® Pricing  ®Define Data Values.

If "Use as a Price Quantity" contains a sample with an asterisk (*), this is used as the quantity in all pricing procedures whose name matches this sample.

 

       3.      Create a condition type with the following parameters for values in the SAP CRM System under Customer Relationship Management ® Basic Functions ® Pricing ® Define Settings for Pricing ® Create Condition Types:

Application	CRM
Use	PR
Condition type	ID
Description	Description
Source System	Origin: CRM
DS source	IPM: Basic value
Access date	Pricing date
Condition class	Discounts or surcharges
Calculation type:	Fixed amount
Rounding rule	Commercial
Manual entries	Not possible to process manually

       4.      Now create the pricing procedure for OR settlement in the SAP CRM Implementation Guide under Customer Relationship Management ® Basic Functions ® Pricing ® Define Settings for Pricing ® Create Pricing Procedure:

...

                            a.      Assign the condition type for a value to the pricing procedure for OR settlement. Define the condition type as being “statistical”.
This condition is used as a basis for an additional condition type, such as the condition type supplied 17PO “License Fee (Per) OR”. This pricing procedure could appear as follows:

Level	CType	Description	From	To	Statistical
100	XXXX	Description			x
200	17PO	License Fee (Perc.) OR	100
300		Royalties	200

Example:
The net value of the product sale was $10 000. This value is entered in the condition type XXXX. You have entered a price agreement for the condition type “License Fee (Perc.) OR” (17PO) of 10% in the license acquisition contract. This means that the licensor is to receive 10% of the net value of the product sale (10% of $10 000). Royalties of $1000 are therefore calculated.

                            b.      If you are using the price document as a quantity in the pricing procedure for OR settlement, you require a condition type that uses this price quantity as a basis, such as the 17QO condition type supplied. This pricing procedure could appear as follows:

Level	CType	Description	From	To	Statistical
200	17QO	License Fee (Perc.) OR
300		Royalties	200

Example:
The number of units for the product sale was 5000. This quantity is entered as a pricing quantity in the pricing procedure used during OR settlement. You have entered a price agreement for the condition type “License Fee (Qty) OR” (17QO) of $0.50 for each unit in the product sale in the license acquisition contract. This means that the licensor is to receive $0.50 for each unit in the product sale ($0.50 * 5000 units). The system calculates royalties of $2500.