Ansicht
Dokumentation
CRMC_IPMO_SRVUSE - Adjust Billing Engine Application for Settlement of Outgoing Royalties
General Material Data Vendor Master (General Section)This documentation is copyright by SAP AG.
The IPMO Billing Engine application provided must be modified for specific customers to perform settlement for outgoing royalties (license settlement). (This modification affects all clients).
Attributes (such as market, territory, language), which are used to characterize the rights sold and to define outgoing royalties, are customer-specific elements in this application. In conjunction with the IP sold, these attributes form the royalties key. Each 'raw line', which describes a right sold, contains the transaction key for the business transaction that is relevant to royalties and a date in addition to the royalties key. These three components identify the raw lines and therefore create the logical key to a raw line in the settlement data collector. Each raw line contains several assigned data values (that are distinguished by the data value key field) in the non-key part. They also contain the transaction key for the preceding document if the IPMDPLIDP feature has been activated. A customer-specific application is only ever distinguished from other applications by the attributes for the royalties key.
Attributes are created during product master data maintenance. The attributes that belong to the royalties key must be defined as rights dimensions. The system assigns them a number between 1 and 6 for order processing.
To include attributes for the royalties key in the application, create a customer specific feature and a usage in the following six steps.
- Choose the application IPMO -> Object DPL -> Feature from the "Meta data entity" tree structure in the BE Framework Navigator and "Change for all features" in the context menu. Choose the feature node and "Create" in the context menu to create a customer-specific feature with the IPMROYKEY predecessor feature without a service (enter a description in the customer name space in the feature field). To include the market, territory and language attributes, as they appear in the BW content, in the royalties key, you can also use IPMROYKEZ as a predecessor feature.
- Choose the feature attributes node in the tree structure below the feature you have just created and "Display List" in the context menu. Insert the IP attribute that is inherited from the IPMROYKEY predecessor feature and your customer-specific attributes for the royalties key in the table displayed. Choose field names from the customer name space and specify the attribute names that were used to define the rights dimensions as a data element. Save your entries.
- After pressing the "Refresh" button, choose the feature node [feature created] -> Feature attribute [feature attribute added] -> -> Container in the tree structure for every feature attribute that was added in this manner. Choose "Display List" in the context menu to add an entry with the DPLI Container.
- Navigate back to the previous "Application" tree structure using the blue arrow situated to the left above the tree structure and choose the node Application IPMO -> Object DPL -> Feature and "Create Assignment" in the context menu to enter the feature you have just created (leave the Inactive field blank).
- Choose the node Application IPMO -> Object DPL -> Container DPLI -> Usages and "Change for all usages" in the context menu. Choose the "Usages" node and "Create" in the context menu to create a customer-specific usage with A attributes assignments, generation relevant X and enhanced usage IPMROYK (enter a description in the customer name space in the Usage field, and leave the Selection and blocking relevance field blank).
- Navigate back to the previous "Application" tree structure using the blue arrow situated to the left above the tree structure and choose the node Application IPMO -> Object DPL -> Container DPLI ->Usage IPMROYK -> Usages, and "List of Fields" in the context menu. Insert entries with the usage that you created in step 5 in the table displayed. You should insert one entry with each of the field names that you added to the feature attributes in step 2. Assign the DPLI container in each case here (you can use any sort sequence). Save your entries.
If you want to distribute license fees that have been settled between several expense accounts or CO-PA objects during transfer to accounting via Service Mapping IAT), you should assign the account assignment attributes to an additional customer-specific feature. Creation of this additional feature is optional and is only necessary if several expense accounts are to be used. Steps 1 to 6 described above should be repeated here, but with the following changes:
- Choose the DL object instead of DPL.
- Use the IPMROYACS predecessor feature instead of the IPMROYKEY feature. Use the DLSI container instead of DPLI.
- Enhance the IPMROYA usage instead of using the IPMROYK usage.
- (You also need to choose different descriptions in the customer name space for the feature and usage from those for the royalties key.)
It is possible to have more than one client in a system, with each client using (partially) different attributes for their royalty key or accounting set key.
In such cases, you configure the IPMO Billing Engine application with the attributes of all clients combined. If one client for example, has a royalty key consisting of the attributes IP and MARKET, and another client has a royalty key consisting of the attributes IP and TERRI, then you set up a royalty key (usage IPMROYK) consisting of IP, MARKET and TERRI. You do the same for the accounting set key.
After generation of the IPMO Billing Engine application, the database table /1BEA/IPMO_DPLI will contain each of the attributes that you specified.
However, if an attribute has not been specified for a particular client, it will not be included in that client's royalty/accounting set key.
Remember that attributes are specified for clients indirectly, by way of the
Define Rights and Royalties Dimensions
Therefore if the attribute /1BEA/IPMO_DPLI-MARKET has the data type CRMT_IPM_MARKET for example, then it is included in the royalty/accounting set keys of those clients where CRMT_IPM_MARKET is maintained as a rights or royalty dimension. Clients who do not maintain this rights dimension will not have this attribute included in their royalty/accounting set keys.
The attributes in the accounting set key are obtained from the attributes of the royalty key, where the data types (and not the attribute names) are compared.
If the accounting set database table contains the key attribute /1BEA/IPMO_DLSI-ZMARKET of data type CRMT_IPM_MARKET for example, it will be mapped to the royalty key attribute /1BEA/IPMO_DPLI-MARKET. In clients where CRMT_IPM_MARKET is not used as a royalty key attribute, the accounting set key will remain initial.
Because attributes are matched by their data type, you must ensure that all royalty key attributes and accounting set key attributes use distinct data types, even across clients.
Additional optional features
The IPMPRIPROC feature is assigned to the BD and DL objects inactively. If you activate this feature for both objects, you can specify the pricing procedure to be used during outgoing royalties settlement (on the "Rights Control" tab page) for each item in license acquisition contracts. (The pricing procedure specified in the billing type is then ignored here.) If this feature is not active, the pricing procedure specified in the billing type is used and the pricing procedure entered in the contract is ignored.
Once you have made all the customer-specific changes, choose the node Application -> IPMO and a generation function in the context menu.
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 10269 Date: 20240523 Time: 162811 sap01-206 ( 211 ms )
