CL_CRM_PRD_UPG_MV_ATTR_50 - Conversion of Multiple-Value Attributes in CRM 5.0

RFUMSV00 - Advance Return for Tax on Sales/Purchases   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Functionality

As of CRM 5.0, multiple-value attributes are no longer stored in the Product Modeling Environment (PME). Instead, when a multiple-value attribute is created, a table is generated in CRM in which the values can be stored.

The class CL_CRM_PRD_UPG_MV_ATTR_50 is called as part of the reportCOM_PRODUCT_UPGRADE, which has to be executed after an upgrade. It converts the following data:

• The tables and classes required for storing values in CRM must be generated for those attributesfor which the Multiple Values Poss. indicator has been set (transaction COMM_ATTRSET).

• The values of multiple-value attributes are read from the PME and saved in the new database table.
  In product maintenance, the values of multiple-value attributes will no longer be read from the PME but from the generated table.

Relationships

Example

Notes

If you want to use multiple-value attributes in future, you no longer have to set the ExtendedMaintenance (PME) indicator in hierarchy maintenance. This means that categories no longer have to be created in the PME.

However, value range restrictions and default values are still stored in the PME. To use these functions, you must set the Extended Maintenance (PME) indicator for the relevant hierarchy.

Although the class CL_CRM_PRD_UPG_MV_ATTR_50 converts the multiple- value attributes after upgradingto CRM 5.0, the categories are still stored in the PME (the Extended Maintenance(PME) indicator is set). The categories cannot be deleted in the PME, as value range restrictions or default values may have been maintained.

Further information

ROGBILLS - Synchronize billing plans   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.


Length: 1954 Date: 20120526 Time: 131908     triton ( 87 ms )