| Article Index |
|---|
| Restrictions of SAP CRM 2007& 7.0 |
| SAP CRM Sales |
| SAP CRM Services |
| SAP CRM Marketing |
| All Pages |
Following are the some of the functionalities of SAP CRM 5.0 and previous versions which are not supported in SAP CRM 2007 onwards.If current application uses any of the following elements, a migration or work around would be required.
Click on the article index on the right to browse to relevant areas->
| MASTER DATA->SAP CRM 6.0& SAP CRM 7.0 | ||
Function in SAP CRM 5.0 | 5.0 UI | Restrictions of SAP CRM 2007 & SAP CRM 7.0 |
| Accounts & Contacts | ||
| Field- and table-like enhancements are generated with the Easy Enhancement Workbench (EEW) | SAP GUI, PCUI | Business Data Toolset (BDT) not supported(no reusable) in SAP CRM 2007;field and screen modification has changed. |
| Postal validation | SAP GUI, PCUI | PCUI If a customer uses third party software for postal validation, the implementation of interfaces for postal validation popups is necessary. |
| Restriction for Products | ||
| Display of Related Business Documents (BDOCs) | SAP GUI | No longer supported |
| Recategorization of Products | SAP GUI | Only avalable in SAP GUI. |
| Display data for date/time in the past (this does not refer to change documents | SAP GUI | No longer supported.The change history allows a detailed view about the changes. |
| UI generation of relationships between products and business partner/product. | SAP GUI | BOL entries are generated for the CRM WebClient UI; the user interface is not generated. |
| Restrictions for Product Hierarchies | ||
| Definition of default values and value restrictions with regard to the maintenance of product categories. | For the definition of default values the new template functionality can be used to define default values on category level; to define value restrictions, values can only be set in the attribute definition. | |
| Restrictions for Partner/Product Ranges | ||
| Listing functionality for Partner/Product Ranges (PPRs): Specific view on PPR reporting and maintenance adapted to the specific needs of the Consumer Products (CP) industry. | SAP GUI | Only generic PPR maintenance can be used. |
| Restrictions for Installed Bases | ||
| Display of detail data of the products | SAP GUI,PCUI | You can navigate via hyperlink to the complete Data |
| Maintenance of certain data of the (individual) object. | SAP GUI,PCUI | You can navigate via hyperlink to the complete data. |
| No display of installed bases at a specific point in time. | SAP GUI | Not available |
| The structure of an installed base — assigned as component — is not visible in the installed base in focus. | SAP GUI | You can navigate via hyperlink to the complete data. |
| Parallel display of two installed bases, one beside the other, and moving objects between both (transaction IB54) | SAP GUI | Not available |
| Fact Sheet | PCUI | The reporting is done in different assignment blocks in the application. |
| Attachments | PCUI | The following functions are not supported: *Document versioning *Where-used list |
| SALES->SAP CRM 6.0& SAP CRM 7.0 | ||
| Function in SAP CRM 5.0 | 5.0 UI | Restrictions in SAP CRM 2007 & SAP CRM 7.0 |
| Sales Order Management, CRM Billing | ||
| Inquiry Processing | SAP GUI | Not Available |
| Partial transaction processing (sales order, sales quotation, and sales contract) | SAP GUI | Not Available |
| Combination of quotation and order items in one document . | SAP GUI | Not Available |
| Commodity Pricing | SAP GUI,PCUI | Not Available |
| Incentive and Commission Management | SAP GUI,PCUI | Not Available |
| Reference Objects on Sales Order Item Level. | SAP GUI | Not available in CRM WebClient UI |
| Partners on Sales Order Item Level | SAP GUI | Ship-To Party, Payer, and Bill-To Party are available in the business context (assignment blocks Shipping and Billing; no separate assignment block for Parties Involved. |
| Account Fact Sheet (AFS) Grid | SAP GUI | Not available in CRM WebClient UI |
| Restriction in Opportunities, Listings, Territory Management | ||
| Organizational Management | SAP GUI, PCUI | The following functions are not supported: * The hierarchy on item-header level; only the hierarchy on header-header level is supported, which is visualized as a simple list. *Competitor products * Document flow on item level * Project integration with Product Lifecycle Management (PLM) in Collaboration Projects (cPro) |
| Listings | SAP GUI, PCUI | *Listing Maintenance: Personalization of dynamic fields is not supported *Listing Reports: The function Save Search As is not supported . |
| Territory Management | SAP GUI | * It is not possible to assign employees to a territory when you use the input help of the Employee field; this is now possible with an input help of the Position field. *The number of objects for a territory is not displayed . |
| Organizational Management | SAP GUI | * New territories cannot be assigned from the organizational model; assignment is only possible via territory management; from the organizational model you can only see the existing assignments. * On the assignment block, the corresponding ERP sales organization is no longer displayed; this is now done in CRM Customizing. |
| Restriction in Account Planning | ||
| BAdI CRM_ACC_PL->AUTHORITY CHECK | PCUI | The BAdI AUTHORITY_CHECK is not longer called for the result list ; there is no workaround possible at the moment; instead, use the Easy Enhancement Workbench (EEW). |
| BAdI CRM_ACC_PL | SAP GUI, PCUI | New BAdI methods CHECK_BEFORE_SAVE and GET_DROPDOWNBOX_VALUE |
| Customizing | SAP GUI, PCUI | The delivery Customizing for planning profile groups has been changed; ’Plan Basis’ is no longer used; it has been replaced by ’Product Planning Basis’. |
| Partner/product range (PPR) check on person responsible. | The PPR check is only performed on the planning customer and product/product category; it is no longer performed on the person responsible | |
| Restriction of Mobile Sales | ||
| Account Planning | Mobile Client | The Account Planning data persists only in SAP NetWeaver Business Intelligence (BI); there is no data present in the CRM server; there is no automatic conversion of previous account plans created in SAP CRM 4.0; these account plans are only accessible via reporting. |
| SERVICES->SAP CRM 6.0& SAP CRM 7.0 | ||
| Function in SAP CRM 5.0 | 5.0 UI | Restrictions in SAP CRM 2007 & SAP CRM 7.0 |
| Restriction of Service Orders, Service Contracts, Warranty Claim Processing scenarios | ||
| Item Hierarchy Tree | SAP GUI,PCUI | Not supported |
| Service Monitor | SAP GUI | Only supported in SAP GUI |
| Action Monitor | SAP GUI | Only supported in SAP GU |
| Subject Code | SAP GUI,PCUI | Not supported; subject code catalogs have been replaced by the categorization modeler. |
| Service Order Quotations | SAP GUI,PCUI | Converting service order quotations to service orders by using statuses is not supported; to create a service order from a service order quotation, a follow-up needs to be created. |
| Service Level Agreement (SLA) Profile Administration. | SAP GUI,PCUI | The administration transaction (CRMD_SERV_SLA) Maintain SLA Profle and Maintain Availability and Response Times remains in SAP GUI. |
| MARKETING->SAP CRM 6.0& SAP CRM 7.0 | ||
| Function in SAP CRM 5.0 | 5.0 UI | Restrictions in SAP CRM 2007 & SAP CRM 7.0 |
| Marketing Plans and Campaigns | ||
| BAdI CRM_MKTPL | SAP GUI,PCUI | Due to changes in architecture (object layer) the old BAdI CRM_MKTPL is not supported any longer; it is replaced by the two BAdIs CRM_MKTPL_OL_APP and CRM_MKTPL_OL_OBJ.The example implementation CL_EXM_CRM_MKTPL_WRAPPER can help you to convert the old implementation to the new implementation; this implementation can even be used to connect the new BAdIs to the old BAdI;however, this is not recommended. |
| BAdI CRM_MKTPL->AUTHORITY CHECK | PCUI | CHECK The BAdI AUTHORITY_CHECK is no longer used for the result list for performance reasons; you can either use the Access Control Engine (ACE) or BAdI method CHANGE_QUERY_RESULT in CRM_MKTPL_SEARCH instead. |
| BAdI CRM_MKTPL_KPI_BADI | SAP GUI,PCUI | Because the key figure planning integration has been redesigned, the BAdI CRM_MKTPL_KPI_BADI is not called anymore; it has been replaced by BAdIs CRM_KFP_BADI and CRM_KFP_COMP_BADI. |
| Business Intelligence (BI) Reports | SAP GUI,PCUI | BI reports assigned to planning profile groups are not evaluated anymore for Marketing plans and campaigns. |
| Customizing | SAP GUI | The Customizing settings for column number, column width and text width for distributions are not evaluated anymore. |
| ERP Integration | SAP GUI | The ERP integration type ’Online’ is not available anymore. Only the ERP integration via middleware is supported. |
| Customizing | SAP GUI,PCUI | The standard Customizing for planning profile groups has changed: * Workflow profiles from 4CO1 and 4CO2 removed * Business partner planning profile moved from 4MKT to 4CP1 *Planning profile group SAP1 removed *The new key performance indicator(KPI)hasbeen removed. |
| Key Figure Planning | SAP GUI,PCUI | Old style key figure planning in the SAP List Viewer (ALV) is not supported anymore. |
| Budgeting | SAP GUI | Top-down budgeting in Microsoft Excel is not supported anymore. |
| Success Key Measure Planning | SAP GUI,PCUI | Success key measure planning is not supported |
| Hierarchy | SAP GUI,PCUI | The creation of a campaign or campaign elements below campaign elements is no longer possible. |
| Segment Partner Function | SAP GUI,PCUI | The segment partner function is no longer available (BOL/GENIL exists, but no UI component) |
| Search Function | SAP GUI,PCUI | Search results do not include objects of the following types: Campaign element, marketing plan element, and trade promotion element. |
| Mail Forms | ||
| Letter as direct channel | SAP GUI | Letter is not supported as a direct channel anymore; sending letters is supposed to be performed via export channel |
| PDF Format | SAP GUI | PDF format is no longer supported. |
| Mail Templates | SAP GUI | Mail templates are no longer supported. |
| Address Administration | SAP GUI,PCUI | Automatic address administration via address node is no longer supported |
| SAP Smart Forms | SAP GUI,PCUI | Not supported.Use Mail Forms. |