Configure SD
Integration
You want to use 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 to transfer product sales data from SD billing documents to royalties settlement in IPM are described in this document.
The system in which SAP SD product sales are entered, is connected to a SAP CRM-System as a back-end system. You have already configured SAP SD for product sales and are using the media product master.
The backend system is available to you with the SAP ECC Industry Extension for Media 6.0.
If billed values and quantities from SAP SD product sales are to be used as the basis for calculating the royalties settlement in Intellectual Property Management (IPM), you must make the following settings in the ERP System:
...
1. Add Subscreen for Intellectual Property to Media Issue (ERP)
You can use the media issue as a master data object for physical products (such as books). To make this setting, choose the following path in the SAP Implementation Guide: SAP Media ® Master Data ® Product ® Media Product Master ® Configure Material Master ® Define Structure of Data Screens for Each Screen Sequence.
a. If you previously used the standard screen sequence M2 or have not previously used the media product master, copy the screen sequence M2. To do so, choose the screen sequence M2 and Copy as... . Overwrite M2 with the key for the new screen sequence (such as Z2) and enter a name. Choose Copy. Save the new screen sequence.
b. Incorporate the subscreen used to assign the Intellectual Property to the media issue in the screen sequence used (such as Z2).
c. Select the screen sequence used (such as Z2) and Data Screens in the dialog structure. Select the screen M3 (Media Basic Data 2) and Subscreens. Change the entry for the screen M3 and subscreen number 4 sequentially by entering the program SAPLJPMM and 2060 as the screen number.
d. Save your entries.
2. Assign Screen Sequence Transaction (ERP)
To make this setting, choose the following path in the IMG: SAP Media ® Master Data ® Product ® Media Product Master ® Configure Material Master ® Assign Screen Sequences to User/Material Type/Transaction/Industry Sector.
a. Choose Transaction screen reference in the dialog structure, and check that the screen reference M2 has been assigned to the transactions JP27, JP28 and JP29 for creating, changing and displaying a media issue.
b. Choose Screen sequence control in the dialog structure and change the value for the screen sequence to the screen sequence you created previously (e.g. Z2) in the entry for the SRef: Trans = M2, SRef: User = *, SRef: Mtrl.Type = * and SRef:.Industry = *.
c. Save your entries.
During maintenance of the media issue, you can now assign an Intellectual Property on the Media Basic Data 2 tab page. The Intellectual Property for the billing item is determined from the Intellectual Property recorded in the media issue for the billing item.
To ensure
that you can assign an Intellectual Property, you must first make the setting
described in the following activity in the SAP Implementation Guide: Customer Relationship Management ®
CRM
Middleware and Associated Components ®
Communication Set Up ®
Define R/3 Backend
Parameters..
3. Create Value Tables and Value Text Tables for the Rights and Royalties Dimensions
In this step you create the value tables and the value text tables for your rights and royalties dimensions in ERP according to the rights and royalties dimensions in the SAP CRM System.
Choose the ABAP Dictionary (SE11) transaction from the SAP Easy Access menu.
a. Create the following value tables:
○ ZZRIGHTSTYPE
○ ZZROYDIM
You can use the CRMM_IPM_MRKCO value table supplied in the system for the Market rights dimension. Proceed as follows and see the tables below for further information:
○ Copy the value table CRMM_IPM_MRKCO supplied by SAP to a new value table.
○ Change the new value table.
○ Replace the Field Names and the Data Element for the market according to the following table. Since the data element does not exist in the ERP System yet, you must first create it using forwards navigation. Create the data element according to the data element in the CRM System or the details in the following table.
○ You must edit a domain when you edit the data element: Since the domain does not exist in the ERP System yet, you must first create it using forwards navigation. Create the domain according to the domain in the CRM System or the details in the following table. Activate the new domain.
○ Go one step back to the data element. Edit the field name. Having done so, activate the data element.
○ Go one step back again to the value table and activate this table.
b. Create the following value text tables:
○ ZZRIGHTSTYPE_T
○ ZZROYDIM_T
Proceed as follows and see the tables below for further information:
○ Copy the value text table CRMM_IPM_MRKCO _T supplied by SAP to a new value text table.
○ Change the new value text table.
○ Replace the Field Names and the Data Element for the market according to the following table.
○ Change the foreign key relationship for the new field. Position the cursor on the field names and choose Foreign Keys. Replace the CRMM_IPM_MARKT entry in the Check Table field with a new value table. Now choose Generate Proposal and transfer the changes.
○ Activate the table.
c. Generate a maintenance view for the following value tables:
○ ZZRIGHTSTYPE
○ ZZROYDIM
Proceed as follows and see the tables below for further information:
○ Access the value table in change mode.
○ Choose Utilities à Table Maintenance Generator in the menu.
○ Choose &NC& or customer-specific group as the authorization group, CRM_IPM_CO_ATTR as the function group, customer-specific package as the package, one-step as the maintenance type and no, or user recording routine as the recording routine.
○ Choose Create to generate the maintenance dialog.
Table 1: Value Tables for the Rights and Royalties Dimensions
Parameter |
Rights type |
Royalties dimension |
Transp.table |
ZZRIGHTSTYPE |
ZZROYDIM |
Short text |
Rights type |
Royalties dimension |
Field |
RIGHTSTYPE |
ROYDIM |
Data element |
ZRIGHTSTYPE |
ZROYDIM |
Table 2: Rights Type Data Element (ZRIGHTSTYPE)
Parameter |
Value |
Data element |
ZRIGHTSTYPE |
Description |
Rights type |
Domain |
ZRIGHTSTYPE |
Table 5: Rights Type Data Element Field Names (ZRIGHTSTYPE)
|
Length |
Field Name |
Short |
10 |
Rights type |
Medium |
15 |
Rights type |
Long |
20 |
Rights type |
Heading |
18 |
Rights type |
Table 3: Rights Type Domain (ZRIGHTSTYPE)
Parameter |
Value |
Domain |
ZRIGHTSTYPE |
Description |
Rights type |
Data type |
Character sequence (CHAR) |
Number of characters |
18 |
Output length |
18 |
Table 4: Royalties Dimension Data Element (ZROYDIM)
Parameter |
Value |
Data element |
ZROYDIM |
Description |
Royalties dimension |
Domain |
ZROYDIM |
Table 5: Royalties Dimension Data Element Field Names (ZROYDIM)
|
Length |
Field Name |
Short |
10 |
Royaltiesdim |
Medium |
15 |
Royaltiesdim. |
Long |
20 |
Royalties dimension |
Heading |
18 |
Royalties dimension |
Table 6: Royalties Dimension Domain (ZROYDIM)
Parameter |
Value |
Domain |
ZROYDIM |
Description |
Royalties dimension |
Data type |
Character sequence (CHAR) |
Number of characters |
18 |
Output length |
18 |
Table 7: Value Text Tables for the Rights and Royalties Dimensions
Parameter |
Rights type |
Royalties dimension |
Transp. Table |
ZZRIGHTSTYPE_T |
ZZROYDIM_T |
Short text |
Rights type (text) |
Royalties dimension text |
Field |
RIGHTSTYPE |
ROYDIM |
Data element |
ZRIGHTSTYPE |
ZROYDIM |
Foreign key table |
ZZRIGHTSTYPE |
ZZROYDIM |
4. Maintain Values for Rights and Royalties Dimensions in ERP
In this step you can maintain the values in the value tables for the rights and royalties dimensions in ERP according to the attribute hierarchies for the rights and royalties dimensions in the SAP CRM System (SAP menu à Industries ® Media: Intellectual Property Management ® Master Data ® Products ® Maintain Hierarchical Attributes).
Choose the Maintain Table Views (SM30) transaction from the SAP Easy Access menu.
Edit the entries for the following value tables/maintenance views:
○ ZTRIGHTSTYPE
○ CRMM_IPM_MRKCO
○ ZZROYDIM
You must create an entry for every relevant attribute value in the corresponding hierarchies in the CRM System. For more information, see the Create Hierarchies for Rights and Royalties Dimensions section of Rights and Royalties Dimensions for the Author Relationship Management Scenario.
You
only need to maintain the characteristics of the rights dimensions for which
you want to confirm SD product sales to the IPM System here. You do not need
to maintain the characteristics for ancillary rights for example.
5. Make Customizing Settings to Determine the Royalties Key
In addition to the Intellectual Property (IP), you must also update other information from the business transactions for the SD sales update to the settlement data collector in the SAP CRM scenario Intellectual Property Management (IPM). You can use this tool to define which attributes are to be updated for the SD billing document.
Choose the following IMG path: SAP Media ® Title Lifecycle Management ® IPM Integration ® Define Attribute Mapping
The royalties key contains the three attributes Rights Type, Market, and Royalties Dimension.
The attributes are to be determined from the material master field ISMMEDIATYPE, from field LAND1 in the billing document header and from the field VTWEG in the billing document header respectively for the SD Billing transaction.
Make the corresponding settings in three steps. See the details in the tables below:
a. Define three attributes and select the Royalties Key indicator in each case:
b. Define the source field for the transaction for each attribute.
c. Define value mapping for the attribute characteristics you are using.
Table 8: Royalties Key
Sequence |
Value Table |
Royalties |
Target Field |
Attribute 1 |
ZZRIGHTSTYPE |
X |
[initial] |
Attribute 2 |
CRMM_IPM_MRKCO |
X |
[initial] |
Attribute 3 |
ZROYDIM |
X |
[initial] |
Table 9: Rights Type – Source Field per Transaction
Object Type Transaction |
Source Table |
Source Field |
VBRK |
MARA |
ISMMEDIATYPE |
Table 10: Market – Source Field per Transaction
Object Type Transaction |
Source Table |
Source Field |
VBRK |
VBRK |
LAND1 |
Table 11: Royalties Dimension – Source Field per Transaction
Object Type Transaction |
Source Table |
Source Field |
VBRK |
VBRK |
VTWEG |
6. Create BAdI Implementation to Determine the Values and Quantities for each Billing Item
To determine the values and quantities, you can create an implementation for the Business Add-In ISM_IPM_MAP_BILL_DOC. If you are using the data values described in the document Configure Settlement and make the values for the data values External: Gross Retail Price of Product Sold (/PGP) and External: Net Retail Price of Product Sold (/PNP) available as a subtotal in the pricing procedure for the SD billing document, you can use the example implementation but may need to adjust this for the subtotals used. In the example implementation, subtotal 1 is entered in the data value External: Net Retail Price of Product Sold (/PNP), subtotal 2 is entered in the data value External: Gross Retail Price of Product Sold (/PGP),and the net value of the billing item is entered in the data value External: Net Value for Product Sale (/SD0). The actual quantity billed is updated in the data value External: Number of units for product sale (/SD1).
To make this setting, choose the BAdI Implementation (SE19) transaction from the SAP Easy Access menu.
Proceed as follows:
a. Choose Classic BAdI under Create Implementation and enter the BAdI nameISM_IPM_MAP_BILL_DOC. Choose Create Impl.
b. Enter the implementation name (e.g. ZZ_ISM_IPM_MAP_BILL) and choose Copy.
c. Choose Goto ®Sample Code® Copy.
d. Enter the package you are using here and choose Save.
e. Access the implementation by double clicking on the method MAP_BILL_DOC and modify the implementation according to your requirements.
f. Save and activate the implementation for the method.
g. Go back to the BAdI implementation and activate it.

If the BAdI implementation is not created, it is not possible to transfer values or quantities to the OR data collector in CRM.
SAP provides output type JINV, which is used to control the OR data collector. The output type is used in output determination 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.
...
1. Maintain Output Type, Output Determination Procedure and Output Condition Records
In this step you edit the output type, output determination procedure and output condition records. Choose the following path in the IMG: SAP Media ® Basic Functions ® Output Determination ® Output Determination in Media Sales and Distribution ® Define Access Sequences., Output Types and Det.Procedures)
Proceed as follows:
a. Choose the Billing application (V3).
b. Choose Output Types and check that the output type IPM: OR Data Collector (JINV) has been assigned.
c. Go one step and select the Billing application (V3) again.
d. Choose Procedures.
e. Select the procedure Billing Output (V10000) and Control in the dialog structure.
f. Check that the condition type JINV has been assigned to the output determination procedure.
g. Go one step and select the Billing application (V3) again.
h. Choose Condition Records and access the output type IPM: OR Data Collector (JINV) by double clicking on it.
i. Choose Execute.
j. Enter the billing type you are using, and assign a role, e.g. Payer (RG), a medium, e.g. Special function (8) and a time, e.g. send immediately (when application is saved) (4).
k. Save your entries.
2. Maintain Output Type, Output Determination Procedure and Output Condition Records
In this step, you can assign the billing type to the output determination procedure. To do so, choose the following path in the IMG: 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.
Check that the Billing Output (V10000) output determination procedure (V10000) and an output type (e.g. Invoice (RD00)) have been assigned for the billing type that you are using.
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 transfer information on the media issue and profit center from SD to the settlement data collector are described below.

The functions described here assume use of note 887990.
...
1. Include Fields in the OR Data Collector (ERP)
To make this setting, choose the following transaction from the SAP Easy Access menu: Tools ® ABAP Workbench ® Development ® ABAP Dictionary.
Proceed as follows:
a. Choose Database Table, enter the database table JPTRAWREC and choose Display.
b. Choose Goto ®Append Structure….in the menu.
c. Enter ZAJPTRAWREC as the append name and choose Execute.
d. Enter a short description.
e. Make entries in the fields on the Components tab page according to the table below.
f. Choose Extras ® Enhancement Category in the menu.
g. Choose Can be enhanced and character-based or numerical and then Copy.
h. Save your entries.
Table 12: Customer Fields in the OR Data Collector
Component |
Component Type |
ZZMATNR |
MATNR |
ZZPRCTR |
PRCTR |
2. Make Entries in Fields in the OR Data Collector (ERP)
To transfer values for the media issue and profit center from the sales document to the OR data collector, you must extend the BAdI implementation described under Create BAdI Implementation to Determine Values and Quantities for Each Billing Item.
Choose the following in the SAP Easy Access menu: Tools ® ABAP Workbench ® Utilities ® Business Add-Ins ® Implementation.
Now extend the implementation for the BadI definition ISM_IPM_MAP_BILL_DOC, so that the value from VBRP-MATNR is entered in the field ZZMATNR and the value from VBRP-PRCTR is entered in the ZZPRCTR field for each line transferred to the OR data collector (changing parameter RAWREC).
3. Create Data Element for Media Issue (CRM)
To make this setting, choose the following transaction from the SAP Easy Access menu: Tools ® ABAP Workbench ® Development ® ABAP Dictionary.
Proceed as follows:
a. Choose Data Type, enter the data type MATNR and choose Copy…
b. Change the entry in the field after the data element to ZZMATNR.
c. Enter the package you are using here and choose Save.
d. Enter a suitable short description.
e. Save and activate your entries.
4. Include Fields in the Transfer Structure for Product Sales (CRM)
To make this setting, choose the following transaction from the SAP Easy Access menu: Architecture and Technology ® ABAP Workbench ® Development ® ABAP Dictionary.
Proceed as follows:
a. Choose Data Type, enter the data type CRMT_IPM_BEA_TS_PRDSL and choose Display.
b. Choose Goto ®Append Structure….in the menu.
c. Enter ZACRMT_IPM_BEA_TS_PRDSL as the append name and choose Execute.
d. Enter a short description.
e. Make entries in the fields on the Components tab page according to the table below.
f. Choose Extras ® Enhancement Category in the menu.
g. Choose Can be enhanced and character-based or numerical and then Copy.
h. Save and activate your entries.
Table 13: Customer Fields in the Transfer Structure for Product Sales
Component |
Component Type |
ZZMATNR |
ZZMATNR |
ZZPRCTR |
PRCTR |
5. Include Fields in the External Interface for License Settlement Single Items (CRM)
To make this setting, choose the following transaction from the SAP Easy Access menu: Architecture and Technology ® ABAP Workbench ® Development ® ABAP Dictionary.
Proceed as follows:
a. Choose Data Type, enter the data type CRMT_IPM_BEA_BDCI_EI_DATA and choose Display.
b. Choose Goto ®Append Structure….in the menu.
c. Enter ZACRMT_IPM_BEA_BDCI_EI_DATA as the append name and choose Execute.
d. Enter a short description.
e. Make entries in the fields on the Components tab page according to the table below.
f. Choose Extras ® Enhancement Category in the menu.
g. Choose Can be enhanced and character-based or numerical and then Copy.
h. Save and activate your entries.
Table 14: Customer Fields in the External Interface for License Settlement Single Items
Component |
Component Type |
ZZMATNR |
ZZMATNR |
ZZPRCTR |
PRCTR |
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.
...
1. Pricing (CRM)
For information on the settings for pricing in the CRM System, see the Pricing section of Configure the Royalties Contract
2. Start Initial Data Transfer (CRM)
To make this setting, choose the following path in the SAP Easy Access menu: Architecture and Technology ® Middleware ® Data Exchange ® Initial Load ® Start.
To transfer the data from the OR data collector to the settlement data collector in IPM, access initial data transfer for the business object IPMBEAPRDSLS.
You
must run the data transfer in a batch job in the production system.
3. Perform DIMa Data Alignment Between SD Product Sales and the OR Data Collector (CRM)
To make this setting, choose the following transaction from the SAP Easy Access menu: Architecture and Technology ® Middleware ® Data Exchange ® Synchronization ® Data Integrity Manager.
You can use the Data Integrity Manager (DIMa) to check whether data from the SD product sale in ERP has been transferred to the OR data collector correctly. The DIMa object Objekt IPM_BEA_PRDSLS is available for this, for which you can start the comparison in transaction SDIMA.
You have the option of performing a header and a detailed comparison. During the header comparison, the system only checks whether an entry is available in the data collector for the corresponding ERP document. The detailed comparison also checks whether the IP, rights attributes, data values and associated values are also identical.
The following filter values are possible:
○ Billing document number
○ Billing type
○ Billing creation date
The system displays the items that exist in both systems and the items that only exist in ERP as a result of the header comparison.
It also displays which items are identical in both systems and which are different as the result of the detail comparison.
If there are differences between the two systems, you can start a comparison directly by transferring the ERP data to the CRM System again.
For general information on the Data Integrity Manager, see the documentation on the middleware.