Technical Background: Integration of SD Product Sales with IPM
When a billing document is created, the data required is stored in the OR data collector in the SAP ERP system. When initial data transfer is executed for the object IPMBEAPRDSLS
, the data is transferred to the settlement data collector in Intellectual Property
Management (IPM). Once processing has been carried out successfully, the system deletes the data in the OR data collector so that it then only contains the data not yet transferred.
The following figure illustrates the data flow from Sales and Distribution (SD) to the IPM system:
Data Flow from SD in SAP ERP System to IPM in SAP CRM System
The following billing data is transferred to the OR data collector as standard:
Logical system
Header and item number of billing document
Date of services rendered
Intellectual property
Time stamp
To transfer the following data, you must make the appropriate Customizing settings or define a Business Add-In (BAdI) implementation:
Rights dimension 1-6
Value with currency or unit of measure for each billing item and data type
Reversal of a billing item leads to the reversal of the corresponding entries in the settlement data collector. For this purpose, the billing item is transferred to the OR data collector with a reversal indicator.
Note
The current release supports the transfer of billing documents for SD product sales to the settlement data collector. However, if the solution is implemented accordingly in a customer project, it is also possible to transfer other documents to the settlement data collector.
Attribute Mapping
The product sales data is stored in the OR data collector exactly as it is transferred from the SAP adapter to the settlement data collector. This means the data required is read and mapped to the values for processing in the settlement data collector before it is stored in the OR data collector.
An entry is created in the OR data collector for each data type and billing item. This is only possible if a condition record is created for the billing type used, in combination with the standard output type JINV in a media system and the output type IPMO in a non-media system. The media issue
or material must reference an IP (see Integration
).
External data types are used when transferring values and quantities. These are then converted to the corresponding internal data types in the settlement data collector. If you want to distribute values and quantities for a billing item between several royalty keys, you can do this using an
implementation of the BAdI ISM_IPM_MAP_BILL_DOC
in a media system and BAdI IPM_ENHANCE_RAW_RECORD
in a non-media system.
Integration
Technical Settings for Defining SAP CRM/SAP ERP Attribute Mapping
Media System
To make the settings in a media system, you can do either of the following:
Define the mapping in Customizing for
SAP Media
under
Title Lifecycle Management
IPM Integration
Define Attribute Mapping
Define an implementation of the BAdI
ISM_ATTRIBUTE_MAP
Non-Media System
To make the settings in a non-media system, you can do either of the following:
Define the mapping in Customizing for
Integration with Other mySAP.com Components
under Customer Relationship Management
Settings for Intellectual Property Management (IPM)
Define Attribute Mapping
Define an implementation of the BAdI
IPM_MAP_RIGHTS_ATTRIBUTES
Technical Settings for Transferring Intellectual Property to OR Data Collector
To determine the intellectual property (IP), you must integrate a specific subscreen of a function group in the maintenance transaction for the material master:
Subscreen 2060 of function group
JPMM
(in a media system)Subscreen 2014 of function group
MGD1
(in a non-media system)
You can do this in Customizing for Logistics — General
under Material Master
Configuring the Material Master
Define Structure of Data Screens for Each Screen Sequence
The intellectual property for the billing item is determined from the intellectual property recorded in the material or media product master in the billing item.
If the Intellectual Property
field does not contain an entry in the material master or media product master, the corresponding billing item is ignored in outgoing royalties calculation. In this case, no data is transferred to the OR data collector.
Technical Settings for Values and Quantities in the OR Data Collector
To determine the values and quantities, create an implementation for one of the following BAdIs, depending on the type of system:
ISM_IPM_MAP_BILL_DOC
(in a media system)IPM_ENHANCE_RAW_RECORD
(in a non-media system)
You can use the sample implementation where the net value is entered in the data type /SD0
, the billed quantity in the data type /SD1
, the net retail price is entered in the data type /PNP
and the gross
retail price in the data type /PGP
(assuming that the later two are stored in the subtotal 1 and 2 of the pricing procedure) as a template for your implementation.
Note
To process credit memos correctly, you must transfer them with negative values and quantities
The data types used must be defined in Customizing for
Intellectual Property Management
Technical Settings for Output Control
When you save after creating, changing, or deleting a billing document, the output control function triggers transfer of the billing document to the OR data collector. SAP provides the standard output types JINV
(in a media system) and IPMO
(in
a non-media system) for integration with the OR data collector. This output type is used in the output determination procedure V10000
. To activate the OR data collector, you must create a message condition record for each billing type for which data is to be transferred
to IPM. You do not create message condition records for billing types that are not to be transferred to IPM.
Note
You do not usually create condition records for invoice lists, since these are not usually included in royalty calculation.