Ansicht
Dokumentation

ISM_TLM_ATTRMAP - Define Attribute Mapping

Vendor Master (General Section)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

In addition to the title master or intellectual property (IP), you must update other data on business transactions for by title financial processing and reporting, as well as for updating SD sales 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 each business transaction.

You must determine the IP and the attributes of the royalty key for the SD business transaction before product sales data can be updated to the settlement data collector. You can use the attribute mapping function described here to determine the attributes of the royalty key.

The attributes defined in attribute mapping must match the attributes of the royalty key in IPM. Make sure that the order is the same.

There must be a value table for each attribute. Value tables are delivered (with CRM and ERP) for the attributes/rights dimensions Territory, Market and Language. If your royalty key contains further attributes, you must first create value tables that have the same structure as the corresponding value table in IPM for these attributes.

During account assignment, the values of the controlling attributes must be determined for each relevant transaction in the ERP system. To minimize the amount of work involved in customer projects, a generic framework is delivered with the standard system. This IMG step is part of this framework.

Besides the title and its higher level titles, costs and revenues are also cumulated for each value combination of additional attributes, such as Territory, Market, and Language. You define the additional attributes you want to use by making enhancements and settings in the Accounting counting module. In addition, you must include the fields in the structure RJP_BY_TITLE_ATTRIBUTES, without changing their names.

There must be a value table for each controlling attribute. Value tables are delivered (with CRM and ERP) for the controlling attributes/rights dimensions Territory, Market and Language. If you use other controlling attributes/rights dimensions, you must first create value tables for them.

To enrich the data for account assignment, you must call a function module to evaluate these Customizing settings for each desired business transaction in a customer enhancement. A function module is provided for this purpose for individual transactions (for example, SD billing).

1. In a first step, define up to 6 attributes and assign each of them a value table containing all the values allowed for the attribute. If you want to use an attribute when updating SD product sales to the settlement data collector in IPM, select the corresponding indicator. If you want the attribute to be taken into account in by title financial processing and reporting, assign the relevant field to the structure RJP_BY_TITLE_ATTRIBUTES.
2. In a second step, define the relevant field (for example, in the SD document) from which the value of the attribute is to be read for one or more transactions in the ERP system.
3. In a third step, define how the value of the attribute is to be determined from the value in the source field. To do this, maintain the corresponding attribute value for each combination of source field and attribute and for every possible source field value.

The royalty key contains the three attributes Market, Territory and Language.

The attributes are to be determined from the material master field ISMMEDIATYPE, from field LAND1 in the billing document header and from the material master field ISMLANGUAGES respectively for the transaction SD billing.

In a first step, you define the three attributes and set the royalty key indicator for each of them:

Attribute	Value table
1	CRMM_IPM_MRKCO
2	CRMM_IPM_TRRCO
3	CRMM_IPM_LNGCO

In a second step, you define the source field for each attribute for the transaction:

Attribute	Transaction	Source table	Source field
1 (Market)	VBRK	MARA	ISMMEDIATYPE
2 (Territory)	VBRK	VBRK	LAND1
3 (Language)	VBRK	MARA	ISMLANGUAGES

In a final step, you must define the value mapping:

Attribute	Source table	Source field	Source value	Target value
1 (Market)	MARA	ISMMEDIATYPE	0001	THEATRICAL
1 (Market)	MARA	ISMMEDIATYPE	0002	VIDEO
1 (Market)	MARA	ISMMEDIATYPE	0003	TERRTV
1 (Market)	MARA	ISMMEDIATYPE	0004	CABLETV
2 (Territory)	VBRK	LAND1	DE	GERMAN
2 (Territory)	VBRK	LAND1	FR	FRANCE
2 (Territory)	VBRK	LAND1	GB	UNITED
3 (Language)	MARA	ISMLANGUAGES	01	DE
3 (Language)	MARA	ISMLANGUAGES	02	FR
3 (Language)	MARA	ISMLANGUAGES	03	EN

03

The relevant controlling attribute in this example is the Territory. For this purpose, fields including ZZTERRI (data element CRMT_IPM_TERRI_CO) are included in the structures RJP_BY_TITLE_ATTRIBUTES and ACCIT.

The territory for the transaction SD Billing is to be determined from the field 'Delivery Country' (LAND1) in the billing document header.

In a first step, you define the attribute and select the royalty key indicator:

Attribute	Value table	Target field
1	CRMM_IPM_TRRCO	ZZTERRI

In a second step, you define the source field for the transaction and attribute:

Attribute	Transaction	Source table	Source field
1 (Territory)	VBRK	VBRK	LAND1

In a final step, you must define the value mapping:

Attribute	Source table	Source field	Source value	Target value
1 (Territory)	VBRK	LAND1	DE	GERMAN
1 (Territory)	VBRK	LAND1	FR	FRANCE
1 (Territory)	VBRK	LAND1	GB	UNITED
1 (Territory)	VBRK	LAND1	US	USA

General Data in Customer Master   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 10108 Date: 20240419 Time: 040205     sap01-206 ( 108 ms )