Configuring the CO-PA Object for Title Data
Transfer
When billing documents for rights acquisition and sales are transferred to Financial Accounting, the attributes in the split ledger that are relevant for splitting are determined from the characteristics of the CO-PA object. This means that the CO-PA object must contain the information required.
...
1. The title data can only be transferred to CO-PA if the titles have been uploaded into the SAP R/3 system from the SAP CRM system (see Settings for Title Upload and Title Attributes in SAP R/3).
2. You should have configured the rights dimensions as follows for one of the business scenarios Intellectual Property Management, License Sales and Incoming Royalties, or License Acquisition and Outgoing Royalties: the standard attribute Market is the 1st rights dimension, the standard attribute Territory is the 2nd rights dimension, and the standard attribute Language is the 3rd rights dimension. If you have made different assignments, you must map the extractors for the value tables (Plug-In) and the InfoObjects in BW.
3. You must create the characteristics IPMT1, IPMT2, IPMT3, IPMTE, and IPMLA so that you can add them to the operating concern. To do this, copy the predefined characteristics from the template table PACRMIPM in the IMG activity Controlling ® Profitability Analysis ® Structures ® Define Operating Concern ®Maintain Characteristics.
4. You should have made the settings described in Middleware Connection to SAP R/3 Accounting. This means the data from the SAP CRM system is available for your use in profitability analysis.
...
1. Set up the Profitability Analysis application according to your requirements. You must make the settings regardless of whether or not you want to use the functions. For example, determine which operating concerns you require. You may require one or more operating concerns depending, for example, on whether you want to use Profitability Analysis and whether or not you use more than one controlling area. The procedure below only includes steps where special settings are required to integrate IPM rights acquisition and IPM rights sales.
2. Add the characteristics IPMT1, IPMT2, and IPMT3, which are available in the template, to the relevant operating concerns. By doing this, you ensure that the CO-PA object is created according to the title data.
3. If you use a title hierarchy that contains more than 3 levels and you want this hierarchy to be taken into account in CO-PA, please proceed as follows:
a. Maintain the corresponding entries in the SAP CRM system in table CRMM_IPM_TTLLV for the additional title levels using transaction SM30.
b. In the SAP CRM system, create an append structure for structure CRMT_IPM_TITLE_GUID_HIER and add a field IPM_TITLE0x for each additional title level x to the append. Use the data element COMT_PRODUCT_GUID.
c. In the SAP CRM system, create an append structure for structure CRMT_IPM_TITLE_ID_HIER and add a field IPM_TITLE0x for each additional title level x to the append. Use the data element CRMT_IPM_IP_ID.
d. In the SAP CRM system, create an append structure for structure CRMT_IPM_TITLE_HIER and add a field IPM_TITLE0x for each additional title level x to the append. Use the data element CRMT_IPM_TITLE0x.
e. In the SAP CRM system, create an append structure for structure BAPI_CO_SALES_CUSTOMER_IPM and add a field IPM_TITLE0x for each additional title level x to the append. Use the data element CRMT_IPM_TITLE0x.
f. In the SAP CRM system, create an append structure for structure BAPI_CO_SALES_CUSTOMER in the customer name range and include structure BAPI_CO_SALES_CUSTOMER_IPM in it (.INCLUDE BAPI_CO_SALES_CUSTOMER_IPM). This adds the fields to the interface structure BAPISDCO. You may already have performed this step.
g. In the SAP R/3 system, add a field IPM_TITLE0x for each additional title level to structure BAPI_CO_SALES_CUSTOMER_IPM. Use the data element CRMT_IPM_TITLE0x_CO.
h. In the SAP R/3 system, create an append structure for structure BAPI_CO_SALES_CUSTOMER in the customer name range and include structure BAPI_CO_SALES_CUSTOMER_IPM in it (.INCLUDE BAPI_CO_SALES_CUSTOMER_IPM). This adds the fields to the interface structure BAPISDCO. You may already have performed this step.
i. To enter the data from a settlement document for outgoing royalties in structure BAPISDCO, use IAT service mapping in the IPMO Billing Engine application. Choose: Customer Relationship Management ® Industry-Specific Solutions ® Media ® Intellectual Property Management ® Billing and Settlement ® Outgoing Royalties ® Adjust Billing Engine Application for Settlement of Outgoing Royalties In this Customizing activity (BE Navigator), choose the application IPMO ® Object DL ® Feature ® IAT, and in the context menu, Service Mapping ® Display List. Create additional entries for the additional title levels similarly to the entries for the title levels 1 to 3. You should also read the documentation on the feature (choose Switch to this Feature in the context menu and then, again in the context menu, Documentation ® Display).
4. To ensure that the additional attributes Market, Territory, and Language are also taken into account, please proceed as follows
a. In the SAP CRM system, create an append structure for structure BAPI_CO_SALES_CUSTOMER_IPM in the customer name range and add the data element CRMT_IPM_MARKET for the rights dimension Market, CRMT_IPM_TERRI for the dimension Territory, and CRMT_IPM_LANGU for the dimension Language to the append structure.
b. In the SAP CRM system, create an append structure for structure BAPI_CO_SALES_CUSTOMER in the customer name range and include structure BAPI_CO_SALES_CUSTOMER_IPM in it (.INCLUDE BAPI_CO_SALES_CUSTOMER_IPM).
Display the data type BAPI_CO_SALES_CUSTOMER in transaction SE11. Choose Append Structure... and confirm the name proposed by the system. Add a short description, for example CRM-CO Interface: Sales Fields (Customer Enhancement).
Add an entry .include in the Component field and BAPI_CO_SALES_CUSTOMER_IPM in the Component type field. Then save and activate the structure.
This adds the fields to the interface structure BAPISDCO. Check whether the include BAPI_CO_SALES_CUSTOMER for structure BAPISDCO contains the fields CRMT_IPM_MARKET, CRMT_IPM_TERRI, and CRMT_IPM_LANGU.
c. In the SAP R/3 system, add the corresponding data elements to structure BAPI_CO_SALES_CUSTOMER_IPM.
Display the data type BAPI_CO_SALES_CUSTOMER_IPM in transaction SE11. Choose Append Structure... and confirm the name proposed by the system. Add a short description, for example CRM-CO Interface: Sales Fields (Customer Enhancement).
The data elements here are CRMT_IPM_MARKET_CO, CRMT_IPM_TERRI_CO, and CRMT_IPM_LANGU_CO. Enter a name of your choice in the Component field for each data element and enter the data element in the Component Type field. Then save and activate the structure.
d. In the SAP R/3 system, create an append structure for structure BAPI_CO_SALES_CUSTOMER in the customer name range and include structure BAPI_CO_SALES_CUSTOMER_IPM in it (.INCLUDE BAPI_CO_SALES_CUSTOMER_IPM). This adds the fields to the interface structure BAPISDCO.
e. From the template (table PACRMIPM), add the characteristics IPMMA, IPMTE, and/or IPMLA to the relevant operating concerns under Controlling ® Profitability Analysis ® Structures ® Define Operating Concern ® Maintain Operating Concern in the Implementation Guide.
5. To ensure that the additional attribute Format, which is not delivered by SAP, is taken into account, please proceed as follows:
a. In the SAP CRM system, add the data element for the rights dimension Format to the append structure you just created for the structure BAPI_CO_SALES_CUSTOMER_IPM (see above).
b. In the R/3 system, add data element ZZFORMAT to the append structure for structure BAPI_CO_SALES_CUSTOMER_IPM, which you just created (see above). Before doing this, make sure that the data elements under a) and b) have the same definition.
c. Create a characteristic WWFOR with reference to data element ZZFORMAT, which you just created.
d. Add the characteristic WWFOR to the operating concern under Controlling ® Profitability Analysis ® Structures ® Define Operating Concern ® Maintain Operating Concern in the Implementation Guide.
e. To ensure that the values for the format are transferred to CO-PA, you must implement the following logic in subroutine CRMINTEG--CHANGE_CHARTAB of program RKECRM40, so that the value in the Format field in the interface is entered in characteristic WWFOR:
■ Import the value VALUE from the imported table T_CHARTAB for DATA_ELEMENT = ‘ZZFORMAT’.
■ Create a record in the exported table T_COPADATA for FNAM = ‘WWFOR’ and the value determined above in FVAL.
6. Once you have added the object type to the special purpose ledger (ZZBUSTYP), you must also perform the following steps so that the object type is determined for the activity type.
a. Create the characteristic WWTRT so that you can insert it in the operating concern. To do this, copy field AUART from the template table VBAK in the IMG under Controlling ® Profitability Analysis ® Structures ® Define Operating Concern ® Maintain Characteristics and assign it the name WWTRT.
b. Add the characteristic WWTRT to the corresponding operating concern.
c. Create a BAdI implementation of IAOM_ATTRIBUTES with a new filter value using transaction SE19. For example, you could name the filter value ‘ZIPM_ATTRIBUTES’. Implement the method CHANGE_ATTRBTS so that a new entry is added to table C_OBJECT_ATTRIBUTES with the following values:
■ STRUC_NAME_COPA = ‘VBAK’
■ FIELD_NAME_COPA = ‘AUART’
■ The activity type is assigned to VALUE. Structure BAPISDCO is imported in the parameter I_DATA. The activity type is transferred in the field PROCESS_TYPE.
d. Then use transaction SM30 to maintain the business scenario CRM_SALES and a sort value for this filter value in table IAOM_BS_MAI.
e. Create a BAdI implementation for ISM_BYTITLE_PP_ACCIT using transaction SE19. Implement the method ACCIT_FIELDVAL_SET as follows:
If the import parameter PV_ACCIT_FIELDNAME has a value of ‘ZZBUSTYP’, the system ready the value for the transaction type (FNAM = ‘WWTRT’) from the imported table of characteristic attributes, PT_COPADATA, and exports the corresponding business object type ‘BUS2000230’ for rights sales or ‘BUS2000231’ for rights acquisition in the parameter PV_ACCIT_FIELDVAL.
7. Check whether you need to add logic for additional fields to the implementation for BAdI ISM_BYTITLE_PP_ACCIT. In the standard delivery, entries for fields relevant to splitting and whose data elements correspond to data elements in CO-PA (according to table TKREF) are automatically made in ACCIT.
8. To make all the configuration settings necessary for Profitability Analysis, you must assign CO-PA value fields to the CRM conditions (Controlling ® Profitability Analysis ® Flows of Actual Values ® Transfer of Incoming Sales Orders ® Assign Value Fields). You must execute the Customizing activityMaintain Assignments of CRM Conditions ® CO-PA Value Fields both for rights acquisition and rights sales contracts.
The conditions 17CO for rights acquisition contracts and 17RI for rights sales contracts are supplied for this purpose.
The data transferred from the billing documents for IPM rights acquisitions and IPM rights sales are enriched with data on the title level 1, title level 2, title level 3, market, territory, language, business object type, the order number and item number in the original document, and, if applicable, the format for the special purpose ledgers.