SAP CRM 2007 SP01 and SP02 Release Notes ______________________________________________________________ Copyright Copyright(c) 2008 SAP AG. All rights reserved. Neither this document nor any part of it may be copied or reproduced in any form or by any means or translated into another language, without the prior consent of SAP AG. The information contained in this document is subject to change without notice. SAP is a registered trademark of SAP AG. All other products which are mentioned in this documentation are registered or not registered trademarks of their respective companies. Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.8.1 1.8.2 1.8.2.1 1.8.2.2 1.8.2.3 1.8.2.4 1.8.2.5 1.8.2.6 1.8.2.7 1.8.2.8 1.8.2.9 1.8.2.10 1.8.2.11 1.8.3 1.8.3.1 1.8.3.2 1.8.3.3 1.8.3.4 1.8.3.5 1.8.4 1.8.4.1 1.8.4.2 1.8.4.3 1.8.5 1.8.5.1 1.8.5.2 1.8.6 1.8.6.1 1.9 1.9.1 1.9.2 CRM Customer Relationship Management Uniform User Interface in CRM (New) Enterprise Services (Changed) Help Center for SAP CRM (New) Terminology in CRM (Changed) New, Changed and Removed IMG Activities in SAP CRM 5.2 New, Changed and Removed IMG Activities in SAP CRM 2007 New, Changed and Removed Customizing Activities in SAP CRM 2007 (Enhanced for SP02) CRM-MD Master Data New, Changed and Removed IMG Activities in SAP CRM 5.1 and SAP CRM 5.2 CRM-MD-BP Business Partners Account Life Cycle (New) Account Management Functions (New) Internet User in Account (new) Billing Account Hierarchies (New) Rule-Based Assignment of Employees (New) Business Partner Fields (New) Data Quality Administration (New for SP02) Account Fact Sheet: BI 7.x Templates (Enhanced for SP02) Business Partners: Qualification Requirements (New for SP02) Authorization Object CRM_BPROLE (New) CRM WebClient UI for IS-M Processes in Interaction Center CRM-MD-PRO Products Up-Selling and Cross-Selling via Interlinkages (New) Package Group Maintenance (Enhanced) Interlinkage Maintenance User Interface (New) Interlinkage Types (Enhanced) Packages and Products with Dependent Components (New) CRM-MD-PCT Product Catalog Product Catalog Staging (New) Programming Interface SAP TREX API (New) Additional Product Category Information (New) CRM-MD-PPR Partner/Product Range Partner/Product Ranges (PPRs) (Enhanced in SP02) Partner/Product Ranges (PPRs) (New) CRM-MD-CON Condition Technique Terminology in Condition Maintenance (Changed) CRM-BF Basic Functions Worklist (New) Authorization Check at Field Level (Enhanced) 1 1 3 3 4 6 9 33 33 48 48 49 50 51 51 52 53 54 55 55 56 58 58 59 59 61 62 64 64 66 66 67 67 68 69 69 70 70 70 ______________________________________________________________ SAP AG iii Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1.9.3 1.9.4 1.9.5 1.9.6 1.9.7 1.9.7.1 1.9.8 1.9.8.1 1.9.8.2 1.9.9 1.9.9.1 1.9.9.2 1.9.9.3 1.9.9.4 1.9.9.5 1.9.9.6 1.9.9.7 1.9.10 1.9.10.1 1.9.10.2 1.9.10.3 1.9.10.4 1.9.11 1.9.11.1 1.9.12 1.9.12.1 1.9.12.2 1.9.12.3 1.10 1.10.1 1.10.2 1.10.3 1.10.4 1.10.5 1.10.5.1 1.10.6 New, Changed and Removed IMG Activities in SAP CRM 5.1 and SAP CRM 5.2 Worklist (Enhanced for SP02) Worklist (Enhanced) Worklist (New) CRM-BF-PD Partner Processing Partner Processing: Alternative Partner Proposal (New for SP02) CRM-BF-COU Counter Language-Dependent Counter Descriptions (New in SP02) CRM-BF-CFG Product Configuration Display Options for Characteristics and Characteristic Values (Enhanced) Display of Messages when Loading a New Knowledge Base (New) Comparison of Product Configurations (New) Performing Standard Configuration in the Background (New) Product Config: Using Sales Order Fields as Object Characteristics (New) Characteristics for Display of Messages (New) Product Modeling (Enhanced) CRM-BF-PR Pricing Terminology in Condition Maintenance (Changed) Credit Analyst Workbench (New) Approval Process for Price Changes in Sales Orders (New Display Price List(s) for an Account (New) CRM-BF-COM Content Management Enhancements for Content Management (Changed) CRM-BF-WST Web Services Tool Web Services Tool (New) Web Service Consumption Tool (New for SP02) Web Services Tool (Enhanced) CRM-BE Billing Transfer of Accounting Indicator to Billing (New) Intercompany Billing (Enhanced) Transfer of Billing Data to SAP GTS for Intrastat Declarations (New) Claim Settlements (New) CRM-BE-DL Billing Due List Reference to Letter of Credit in Billing Documents (New) CRM-BE-FI Transfer to Accounting 71 86 87 88 89 89 89 89 90 90 90 92 93 94 94 97 99 100 100 101 102 103 103 103 104 104 105 105 107 107 107 108 108 111 111 111 ______________________________________________________________ SAP AG iv Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1.10.6.1 1.11 1.11.1 1.11.2 1.11.3 1.12 1.12.1 1.13 1.13.1 1.13.2 1.13.3 1.13.4 1.13.5 1.13.6 1.13.7 1.13.8 1.13.8.1 1.13.9 1.13.9.1 1.13.9.2 1.13.9.3 1.13.9.4 1.13.10 1.13.10.1 1.13.10.2 1.13.10.3 1.13.10.4 1.13.10.5 1.13.10.6 1.13.10.7 1.13.10.8 1.13.10.9 1.13.10.10 1.13.10.11 1.13.10.12 1.13.10.13 1.13.10.14 Controlling Integration for Intercompany Billing (New) CRM-RB Rebate Processing Terminology in Condition Maintenance (Changed) SAP CRM Rebate Processing WebClient UI (Enhanced) CRM-EM CRM Entitlement Management Entitlements Management (Enhanced ) CRM-BTX Business Transactions Use of the Maintenance Framework for Business Transactions (New) Sale of External Products (New) Sold-To Party Profiles in Sales Orders (New) Different Actions in Sales Orders Depending on Transaction Mode (New) Displaying Customer-Specific Fields/Business Transaction Components in Subsequent assignment of transactions Business Object Layer and Web Services (Enhanced) CRM-BTX-LEA Lead Management Duplicate Check for Leads (New) CRM-BTX-OPP Opportunities Opportunity Assessment Determination Based on Expected Sales (New) Transfer Buying Center Between Opportunity and Account (New) Competitor Information for an Opportunity (Enhanced) Enhancements to Opportunities in CRM (Changed) CRM-BTX-SLO Sales Transaction Use of Product Proposals (Enhanced) Use of Provider Orders (New) Automatic Creation of Provider Orders for Lock/Unlock Services (New) Settlement of Recurring and One-Time Fees (Enhanced) Status Management in Provider Order Maintenance (Enhanced) Abnormal Demand in Sales Order Items (New) Assignment of Internal Orders to Sales Orders (New) Integration of Letters of Credit in the Sales Order (New) Mass Changes at Header Level (New) Maximum Number of Locations in Availability Check (New) Determine Maximum Partial Deliveries (New) Use of Objects in Service Recall Orders (Enhanced) Third-Party Order Processing with Consolidation (New) Third-Party Order Processing with Supersession (New) 111 112 112 113 114 117 117 118 118 119 121 121 121 122 123 123 123 124 124 125 125 126 127 127 129 131 131 133 134 134 135 136 136 137 138 139 140 ______________________________________________________________ SAP AG v Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1.13.10.15 1.13.11 1.13.11.1 1.13.12 1.13.12.1 1.13.12.1.1 1.13.13 1.13.13.1 1.13.14 1.13.14.1 1.13.15 1.13.15.1 1.13.15.2 1.13.15.3 1.13.15.4 1.13.15.5 1.13.15.6 1.13.16 1.13.16.1 1.13.16.1.1 1.13.16.2 1.13.16.2.1 1.13.16.3 1.13.16.3.1 1.13.17 1.13.17.1 1.14 1.14.1 1.14.2 1.14.3 1.15 1.15.1 1.16 1.16.1 1.16.2 1.16.3 Using Grid Products in the Sales Order (New for SP02) CRM-BTX-ERP BSP for ERP Sales Order Creating and Changing ERP Sales Transactions in SAP CRM (New) CRM-BTX-SVO Service Processes CRM-BTX-SVO-QUT Service Inquiries / Quotations Packages in Service Order Quotations (New) CRM-BTX-SCO Service Confirmation Serial Number Entry in Confirmations (New) CRM-BTX-BRQ Billing Request Transfer of Accounting Indicator to Billing (New) CRM-BTX-COM Complaints / Returns / In-House Repair Use of Complaints and Returns to Update Sales Contracts (New) Complaint with reference to trade promotion (New) Exchange Group for Used Part Returns (New) Complaints for External Products (New) Complaint Creation with Reference to a SAP ECC Handling Unit (New) Inventory Adjustment for Complaints (New) CRM-BTX-CTR Contracts CRM-BTX-CTR-CCO Sales Contract Provider Contracts (New) CRM-BTX-CTR-SCO Service Contract Provider Contracts (New) CRM-BTX-CTR-UCO Usage-Based Service Contract CRM-BTX-PRV Provider Transactions New Functions in the Provider Contract and Dispute Management (New) CRM-CMG Case Management Automatic Case Notes in Case Management (New) Case Management (Enhanced) Case Management (Enhanced) CRM-ACP Account Planning Account Planning (Enhanced) CRM-FM Funds Management Funds Management (New) Funds Analytics (New) CRM-FM-ACL Accruals 141 142 142 143 143 143 144 144 145 145 145 145 147 149 150 151 152 153 153 153 156 156 158 158 159 159 161 161 161 163 165 165 166 166 167 167 ______________________________________________________________ SAP AG vi Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1.16.3.1 1.16.4 1.16.4.1 1.16.5 1.16.5.1 1.16.6 1.16.6.1 1.16.7 1.16.7.1 1.16.8 1.16.8.1 1.16.8.2 1.16.9 1.16.9.1 1.16.10 1.16.10.1 1.17 1.17.1 1.17.2 1.17.3 1.17.4 1.17.5 1.17.5.1 1.18 1.18.1 1.18.2 1.18.3 1.18.4 1.18.5 1.18.6 1.18.7 1.18.8 1.18.9 1.18.10 1.18.10.1 1.18.11 1.18.11.1 1.18.11.2 1.18.12 1.18.12.1 Accruals (new) CRM-FM-AVC Availability Control Availaibility Control (New) CRM-FM-BER Budget Expiration Budget Expiration (new) CRM-FM-BFW Batch Framework Batch Processing Framework (new) CRM-FM-BPO Budget Posting Budget Postings (New) CRM-FM-FND Fund Plans and Funds Fund Determination (Enhanced for SP02) Funds Plans and Funds (New) CRM-FM-FPO Fund Posting Fund Postings (New) CRM-FM-FU Fund Usages Fund Usage (New) CRM-CLA Claims Management Claims Management for SP02 (Enhanced) Claims Management (New) Claim Settlements (New) Aggregation and Distribution of Amounts in Marketing Projects for Claims CRM-CLA-BI BI Integration Claims Management: BI Extractors CRM-ISA Internet Sales Shopping Basket (Enhanced) Enabling Links to Web Channel Applications from CRM WebClient UI (New) Improved Usability (Enhanced) Multiple Campaign Assignment (New) Campaign Enrollment (New) Dynamic Field Control for Orders (New) Generic Filter Solution (Enhanced) Customer Role (New) Collaborative Views: Search and Create (New) CRM-ISA-CAT Internet Sales Catalog Basic Eye-Catcher Text in Web Shop (New) CRM-ISA-CFG Product Configuration Internet Sales Configurable Products Attribute Display (Enhanced) Comparing Products (New) CRM-ISA-BCS Business-to-Consumer Sales Provider Shop and Interaction Center Mode (New) 167 169 169 170 170 171 171 172 172 173 173 173 174 174 175 175 176 176 178 179 181 183 183 184 184 184 186 187 188 189 191 192 192 193 193 194 194 195 196 196 ______________________________________________________________ SAP AG vii Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1.18.12.2 1.18.12.3 1.18.12.4 1.18.13 1.18.13.1 1.18.13.2 1.18.13.3 1.18.14 1.18.14.1 1.18.14.2 1.18.14.3 1.18.14.4 1.18.14.5 1.18.14.6 1.18.15 1.18.15.1 1.18.16 1.18.16.1 1.18.17 1.18.17.1 1.18.18 1.18.18.1 1.19 1.19.1 1.19.1.1 1.19.2 1.19.2.1 1.19.2.2 1.19.2.3 1.20 1.20.1 1.20.2 1.20.3 1.21 1.21.1 1.21.2 1.21.3 1.21.4 1.21.5 Price Eye-Catcher Text (New) Recurring Prices in the Provider Web Shop (New) Special Price Display in the Web Shop (New) CRM-ISA-CNT Contracts Contract Duration in Web Shop (New) Contract Negotiation: User Status Profiles (New) Contract Negotiation: Status Display (New) CRM-ISA-BAS Shopping Basket and Order Entry Block View Format in Web Shop (New) Direct Debit Payment Method in Web Shop (New) Save and Upload Shopping Baskets (Enhanced) Separate Payment Methods for Web Shop Purchases Shopping Basket (Enhanced) Technical Data in Provider Web Shop Order CRM-ISA-AUC Web Auction B2C Checkout in Selling Via eBay (Enhanced) CRM-ISA-UM User Management Internet User in Account (new) CRM-ISA-TEC Technical Infrastructure Extended Product Detail Page (New) CRM-ISA-SHA Shop Management Verification Word for Web Shop Assistance CRM-ISE Internet Service CRM-ISE-COM Complaints and Returns E-Service: Extended Complaints and Returns (Enhanced) CRM-ISE-WBF Web Forms New Link Type for Web Requests (Changed) External Interface for Web Requests with Attachments (New) CRM-RPL Resource Planning for Personnel Resources Resource Planning (Enhanced for SP02) Project-Based Resource Planning (New for SP02) Service Resource Planning (New) CRM-MKT Marketing Pertinent Master Data Changes (New) Personalized Mail (Changed) Trade Promotion Upload Using SAP Exchange Interface (New) Deals TPM and Account Planning: BI 7.x Templates (Enhanced for SP02) 196 198 199 200 200 200 201 202 202 204 205 206 207 208 209 209 209 209 210 210 211 211 212 212 212 213 213 214 214 215 215 216 217 218 218 219 219 220 221 ______________________________________________________________ SAP AG viii Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1.21.6 1.21.7 1.21.8 1.21.9 1.21.10 1.21.11 1.21.12 1.21.13 1.21.14 1.21.15 1.21.16 1.21.17 1.21.18 1.21.19 1.21.20 1.21.21 1.21.22 1.21.23 1.21.24 1.21.25 1.21.25.1 1.21.25.2 1.21.25.3 1.21.25.4 1.21.25.4.1 1.21.25.4.2 1.21.25.5 1.21.25.5.1 1.21.25.5.1.1 1.21.25.6 1.21.25.6.1 1.21.25.7 1.21.25.7.1 1.21.25.7.2 1.21.25.7.3 1.21.25.7.4 1.21.25.7.5 1.21.25.8 Purchasing Products and Services in Marketing Projects (New for SP02) Trade Promotion Agreements (New) Mass Copy, Mass Change, Mass Approval (New) Enhancements in CRM Marketing (New and changed) Overlap Checks (New) Scheduled Claims (New) Trade Promotion Templates (New) Tiered Growth Rebates (New) Enhancements in Trade Promotion Management (New) Take Rates (new) Attribute Filters (New) Causals (New) Trade Promotion Critical Changes (new) Editable Overview Pages (Enhancement) TPM Funds Integration (New) Long-Term Trade Promotion Planning (New) Price Simulation Within a Trade Promotion (New) Trade Promotion Guidelines (new) Trade Promotion Versions (new) CRM-MKT-MPL Marketing Planner Enrolling for Marketing Projects (New) Enhancements to Campaigns and Trade Promotions Mass Generation of Sales Orders via Campaigns or Trade Promotions (New) CRM-MKT-MPL-CAL Marketing Calendar Marketing Calendar (Enhanced in SP02) Marketing Calendar (Enhanced) CRM-MKT-MPL-ST Basic Functions CRM-MKT-MPL-ST-KFP Key Figure Planning Free Goods in Trade Promotions (Enhanced) CRM-MKT-MPL-DEF Customer Defaults Trade Promotion Management - Product Hierachy Promotions (Enhanced) CRM-MKT-MPL-MDF Marketing Development Funds MDF BI Extractors (Enhanced in SP02) Market Development Funds (Changed) Authorization and User Management (Enhanced) Market Development Funds: Extractors Determination of Reimbursement Rates in the MDF Process (New) CRM-MKT-MPL-TPM Trade Promotion Management 221 222 223 224 224 225 226 227 227 229 230 231 231 232 233 234 234 235 236 236 236 237 238 239 239 239 241 241 241 242 242 245 245 245 248 250 251 252 ______________________________________________________________ SAP AG ix Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1.21.25.8.1 1.21.25.8.2 1.21.25.8.3 1.21.25.8.4 1.21.25.8.5 1.21.25.8.6 1.21.25.8.7 1.21.25.8.8 1.21.26 1.21.26.1 1.22 1.22.1 1.22.2 1.22.2.1 1.23 1.23.1 1.23.2 1.23.3 1.23.4 1.23.5 1.23.6 1.23.7 1.23.8 1.23.8.1 1.23.9 1.23.9.1 1.23.9.2 1.23.9.3 1.23.9.4 1.23.9.5 1.23.9.6 1.23.9.7 1.23.10 1.23.10.1 1.23.10.2 1.23.11 1.23.11.1 Product Planning Basis for Trade Promotions and Deals (Enhanced for Key Figure Planning Enhancements (New for SP02) Effective Dates in Trade Promotions and Deals (New) TPM BI Extractors Indirect Relationships (New) Listings in Product Proposals (New) Cross-Order Caps for Discounts in TPM (New) Significant Uplifts and Transfer to APO (New) CRM-MKT-SEG Segmentation Product Segments (New) CRM-ANA CRM Analytics Integration of PPM into SAP CRM (New) CRM-ANA-OR Operative Reporting CRM Interactive Reports (New) CRM-IC Interaction Center WebClient Interaction Center WebClient in CRM WebClient UI Framework (New) Intent-Driven Interaction Guidance (New) Client Switch (New for SP02) Selection Dialog Boxes (New) Listing Based Product Proposals (New) Multi Chat (New for SP02) Cancel Button in Business Transactions (New) CRM-IC-MDB Manager Dashboard Monitoring of Statistics from Multiple Telephony Systems (New) CRM-IC-SEA Account Identification Account Identification (Enhanced) Index Table for Simple Business Partner Searches (New) Mixed Business-to-Business and Business-to-Consumer Scenario (New) Related Business Partners (New) CRM WebClient UI for IS-M Processes in Interaction Center Registered Products (Enhanced) Account Identification (Enhanced) CRM-IC-PRO Products Product Search in the Interaction Center (New) Product Catalog Search (New) CRM-IC-FCA Financial Contract Accounting Financial Customer Care and Dispute Management (Enhanced) 252 253 254 254 256 257 258 259 259 259 260 260 261 261 261 262 262 263 264 264 265 265 266 266 267 267 268 268 269 270 272 272 273 273 274 274 274 ______________________________________________________________ SAP AG x Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1.23.11.2 1.23.12 1.23.12.1 1.23.13 1.23.13.1 1.23.13.2 1.23.13.3 1.23.13.3.1 1.23.13.3.2 1.23.13.4 1.23.13.4.1 1.23.14 1.23.14.1 1.23.14.2 1.23.14.3 1.23.14.3.1 1.23.14.4 1.23.14.4.1 1.24 1.24.1 1.24.2 1.24.3 1.24.4 1.24.4.1 1.24.4.2 1.24.5 1.24.5.1 1.24.6 1.24.6.1 1.24.6.2 1.24.6.3 1.24.7 1.24.7.1 1.24.7.2 1.24.8 Financial Customer Care for Insurance (Enhanced) CRM-IC-ALT Alert Alert Editor (New) CRM-IC-CHA Communication Channels Display and Maintenance of Contact Attached Data (New) Presence - Availability of Agents When Transferring Contacts (New) CRM-IC-CHA-TEL Telephony Integration Dual Tone Multi Frequency Tones (New) Simple Computer Telephony Integration (New) CRM-IC-CHA-EMA E-Mail Integration Inserting Agent Signatures and Standard Responses in E-Mail Editor (New) CRM-IC-EMS E-Mail Response Management System Pushing E-Mails to Agents (New) Rules Policies (Enhanced) CRM-IC-EMS-RUL Rule Maintenance Transport of Rule Policies and Rules (New) CRM-IC-EMS-CAT Categories Merge and Import of Categorization Schemas (New) CRM-MSA Mobile Sales CSDT and Infocenter (Deleted) Security Enhancements for CRM Mobile Applications (Enhanced in SP02) Trade Promotion Management Enhancements (Enhanced) CRM-MSA-BP Business Partner Life Cycle Stage for Business Partners (New) Account Classification for Business Partners (New) CRM-MSA-PAS Products & Services Using Configurable Products Created in the CRM Server (Enhanced) CRM-MSA-ACT Activity Activity Scheduling Functions (Enhanced) Synchronization of Attachments in Activities with MS Outlook (New) Attachment of Account Fact Sheet to Activities (New) CRM-MSA-OPP Opportunities Assessments in Opportunities Based on Expected Sales Volume (New) Maintenance of Competitor Product Information in Opportunities (New) CRM-MSA-AMT Authorization Management Tool 277 278 278 278 278 279 280 280 281 281 281 282 282 282 283 283 284 284 285 285 285 286 288 288 289 290 290 291 291 292 293 294 294 294 295 ______________________________________________________________ SAP AG xi Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1.24.8.1 1.24.8.2 1.24.9 1.24.9.1 1.24.10 1.24.10.1 1.25 1.25.1 1.25.2 1.25.3 1.25.4 1.25.5 1.25.6 1.26 1.26.1 1.26.2 1.26.3 1.26.4 1.26.4.1 1.26.4.2 1.26.5 1.26.5.1 1.26.5.2 1.26.6 1.26.6.1 1.26.6.2 1.26.6.3 1.26.7 1.26.7.1 1.26.7.2 1.26.7.3 1.26.7.4 1.27 1.27.1 1.27.2 1.27.3 1.28 1.28.1 1.28.2 Mass Assignment and Unassignment of Roles to Users in AMT (New) Authorization in AMT for Pricing Details (New) CRM-MSA-SAD Sales Document Comparing Product Configurations (New) CRM-MSA-PAC Campaigns & Promotions Product Planning Basis for Trade Promotions and Deals (New) CRM-MSE Mobile Service Mobile Service Functions (Changed) Security Enhancements for CRM Mobile Applications (Enhanced in SP02) Local Stock Information Update (New in SP02) Goods Movement (New) Reservations and Purchase Requisitions (New) Stock Overview (New) CRM-FRW Framework Portal Integration (Enhanced) Portal Integration (New) Working Context (New) CRM-FRW-AFP Application Frame Central Search (New) Central Search (New) CRM-FRW-CON UI Configuration Tool UI Configuration (Enhanced) UI Configuration Tool (Enhanced) CRM-FRW-ROL Roles Management User roles (changed, new) Business Role Customizing (Enhanced) User Role IPM Rights Manager (New) CRM-FRW-UI User Interface User Interface Personalization (Enhanced) UI Configuration: Usability (Enhanced) CRM WebClient User Interface (Enhanced) Personalization (Enhanced) CRM-CHM Channel Management Partner Channel Management (Changed) Partner Channel Management (Enhanced) Partner Channel Management: SAP NetWeaver Portal (New) CRM-LAM CRM Leasing Functions No Longer Available in Leasing Mass Change Processes (New) 295 295 296 296 297 297 298 298 298 299 300 302 305 306 306 307 308 309 309 310 310 310 312 312 312 314 315 316 316 316 317 318 319 319 319 321 321 321 322 ______________________________________________________________ SAP AG xii Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1.28.3 1.28.4 1.28.5 1.28.6 1.28.7 1.28.8 1.28.9 1.28.10 1.28.11 1.28.12 1.28.13 1.28.14 1.28.15 1.28.16 1.28.17 1.28.18 1.28.19 1.28.20 1.28.21 1.28.22 1.29 1.29.1 1.30 1.30.1 1.30.2 1.30.3 1.30.4 1.30.5 1.30.6 1.30.7 1.30.8 1.30.9 1.30.10 1.30.11 1.30.12 1.30.13 1.30.14 1.30.15 1.30.16 Integration of Contractual Services (New) Unique Item Identifier (UIID) (New) Management of Third-Party Relationships (New) Grouping Leasing Documents und FS Documents (New) Functions for Lease Payment Structures (New) Change Processes (New) Classification (New) Management of Billing Request Items (New) Asset Handling and Depreciation (New) Collections Function (New) Calculation of Late Fees (New) Changing the Status of Objects (New) Pricing (New) One-Time Taxes and Fees (New) Termination Quotation (New) Modification of the CRM WebClient UI for Leasing Manager (New) Selection for Floating Rate Adjustment (Changed) Partial Processing of Leases (New) Floating Rate Adjustment (New) New Functions for SAP Leasing (New) CRM-IFS Financial Services Installment Loans (Changed) CRM-IPS Public Sector Case Management for Grantor (Enhanced) Business Rule Framework in CRM (Enhanced) Business Rule Framework in CRM (Enhanced) Event-Driven CRM Activities (New) BRF Action Types for Social Services (New) Case Assignment for Social Applications and Social Service Plans (New) Change Processes in Social Service Plans (New) Item Proposal for Social Applications (New) Business Object Social Application (New) Business Intelligence Analysis of Social Services Data (New) User Role Social Services (New) Social Services Eventing (New) Business Object Social Service Plan (New) Successor Processing of Public Sector Business Transactions (New) Financial Customer Care and Dispute Management (Enhanced) Financial Customer Care for Insurance (Enhanced) 323 328 329 330 330 332 335 336 338 339 340 342 342 343 344 345 347 348 349 350 351 351 352 352 354 355 355 356 357 357 358 359 360 361 361 362 363 364 367 ______________________________________________________________ SAP AG xiii Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1.30.17 1.30.18 1.30.19 1.30.19.1 1.30.19.1.1 1.30.20 1.30.20.1 1.30.20.1.1 1.31 1.31.1 1.31.2 1.31.3 1.31.3.1 1.31.4 1.31.4.1 1.32 1.32.1 1.32.1.1 1.32.1.2 1.32.1.3 1.32.1.3.1 1.32.1.3.2 1.32.1.3.3 1.32.1.3.4 1.32.1.3.5 1.32.1.4 1.32.1.4.1 1.32.1.4.2 1.32.1.4.2.1 1.32.1.4.3 1.32.1.4.3.1 1.32.1.5 1.32.1.5.1 1.32.1.5.1.1 1.32.1.6 1.32.1.6.1 1.33 Financial Customer Care for Public Sector (Enhanced) Grantor Claims CRM-IPS-MD Master Data CRM-IPS-MD-PRG Grantor Programm Grantor Delivery Customizing (New and Enhanced) CRM-IPS-BTX Business Transaction CRM-IPS-BTX-AGR Grantor Agreement Change Request (New) CRM-IHT High Tech High Tech: Mass Search and Replace (New for SP02) High Tech: Partner Manager Role (New for SP02) CRM-IHT-PP Price Protection High Tech: Reverse Price Protection (Enhanced for SP02) CRM-IHT-PDP Partner Design Projects High Tech: Design Registration (Enhanced for SP02) CRM-IM Media CRM-IM-IPM Intellectual Property Management Applications Available Through the Transaction Launcher (New) Uniform User Interface for Intellectual Property Management (New) CRM-IM-IPM-MD Master Data Intellectual Property Rights Maintenance Check (Enhanced) Intellectual Property Maintenance from SAP GUI (Changed) Rights Templates (New) Rights Consumption (New) Rights Maintenance for Intellectual Property Management (Changed) CRM-IM-IPM-BTX Business Transactions Licensing Rights Consumption (New) CRM-IM-IPM-BTX-PUR License Acquisition License Contract Maintenance (Changed) CRM-IM-IPM-BTX-SAL License Sales License Contract Maintenance (Changed) CRM-IM-IPM-RO Royalty Accounting CRM-IM-IPM-RO-ROO Outgoing Royalties Outgoing Royalties Settlement Without Differential Billing (New) CRM-IM-IPM-RIN Rights Inventory Analysis Rights Availability Analysis (Changed) CRM-IPH Pharmaceuticals 367 368 369 369 369 371 371 371 372 372 373 374 374 375 375 376 376 376 377 379 379 379 380 381 382 383 383 384 384 385 385 386 386 386 388 388 390 ______________________________________________________________ SAP AG xiv Release-Informationen Inhaltsverzeichnis SAP AG ______________________________________________________________ 1.33.1 1.33.2 1.33.3 1.33.4 1.33.5 1.33.5.1 1.34 1.34.1 1.34.2 1.34.3 1.34.4 1.34.4.1 1.35 1.35.1 1.35.1.1 1.35.1.2 1.36 1.36.1 1.36.1.1 1.36.2 1.36.2.1 1.37 1.37.1 1.37.2 Account Hierarchy Affiliation and Class of Trade (New) Contract Management for Life Sciences (Enhanced) Products: Pharmaceutical Attributes and NDC (New) Time Dependencies for Business Partners (Telco) - New CRM-IPH-CB Chargebacks Chargeback Claims BI Extractors (New) CRM-IT Telecommunications Functions in Dispute Management (New for SP02) Financial Customer Care and Dispute Management (Enhanced) Financial Customer Care for Insurance (Enhanced) CRM-IT-CI Billing Dispute Management (Enhanced) CRM-IU Utilities Industry CRM-IU-IC Utilities Industry: Interaction Center Financial Customer Care and Dispute Management (Enhanced) Financial Customer Care for Insurance (Enhanced) CRM-MW Middleware CRM-MW-MON Monitoring Data Integrity Manager (Enhanced for SP02) CRM-MW-GWI Groupware Integration Migration of GWI Data from the Java-Based MapBox to the ABAP-Based CRM-CA CRM Cross-Application Components Survey Suite (Enhanced) Multilevel Categorization (Enhanced) 390 392 394 396 397 397 398 398 399 402 403 403 403 403 403 406 406 407 407 407 408 408 408 409 ______________________________________________________________ SAP AG xv SAP-System ______________________________________________________________ 1 CRM Customer Relationship Management 1.1 Uniform User Interface in CRM (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. With the CRM WebClient UI, a uniform and clearly arranged user interface is now available. The Web-based user interface has been completely remodeled and simplified following the example of SAP CRM on-demand solution. The user interface has the following advantages: Clearly arranged page layout Flexible and convenient interface configuration Simple and intuitive navigation Easy to handle personalization Advanced search concept Function bars with icons Terminology adjusted to the new user interface User-centered online help and online tutorials You can now use functions from all areas of CRM and the most important industries, all in a single user interface. Note SAP GUI is only supported for administrative tasks. The People-Centric UI (PC UI) is no longer supported. For more information, see SAP Note 1118231. Effects on Customizing For trouble-free functioning of SAP CRM, you must use transaction HTTP Service Tree Maintenance (SICF) to activate BSP services on the SAP Web Application Server. You can configure the SAP CRM user interface yourself with the new configuration tool, for example, hide or show fields on pages, rename them or put them in new groups. In the Implementation Guide, use IMG activity UI Framework-> UI Framework Definition -> Maintain Design Layers and/or Configure User Interface. You can configure business roles in SAP CRM yourself, for example, you can define the navigation framework, the navigation structure, and the role content. In the Implementation Guide, use the following IMG activity: UI Framework -> Technical Role Definition -> Define Navigation Bar Profile ______________________________________________________________ SAP AG 1 SAP-System ______________________________________________________________ - Business Roles -> Define Navigation Frame Business Roles -> Define Business Role You can assign exactly one authorization role to each business role. In the implementation Guide, use IMG activity UI Framework -> Technical Role Definition -> Define Authorization Role. You can use the transaction launcher to include external Internet addresses or call different transactions in the SAP GUI via the SAP Internet Transaction Server (ITS). In the Implementation Guide, use IMG activity UI Framework -> Technical Role Definition -> Configure Transaction Launcher. See also For more online information about the new user interface, see Jump Start in the Help Center. ______________________________________________________________ SAP AG 2 SAP-System ______________________________________________________________ 1.2 Enterprise Services (Changed) Use This release note is only relevant if upgrading from SAP CRM 5.0. As of SAP CRM 5.1 SP02, the XI content for enterprise services previously delivered is available in a new namespace, http://sap.com/xi/CRM/SE/Global (SAP CRM ABAP 5.1). The existing XI content has been designated as "deprecated". Other changes made are as follows: All Web service definitions have been renamed, by replacing the prefix "CRMXI" with "CRM". For example, CRMXI_BPBASICDATABYCOMQR has been renamed CRM_BPBASICDATABYCOMQR. A number of Web service definitions have been renamed altogether: CRMXI_CUSTOMERQUOTEACCEPTACKRC -> CRM_CUSTQTACCEPTACKRC CRMXI_CUSTOMERQUOTEBYIDQR -> CRM_CUSTQTBYIDQR CRMXI_CUSTOMERQUOTECHGRC -> CRM_CUSTQTCHGRC CRMXI_CUSTOMERQUOTECRTRC -> CRM_CUSTQTCRTRC CRMXI_SRVCONF_CONFCRTRC -> CRM_SRVCONFSRVPROVCRTRC - Message types have been given a suffix "sync". For example, BusinessPartnerBasicDataByIDQuery has been renamed BusinessPartnerBasicDataByIDQuery_sync. 1.3 Help Center for SAP CRM (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The Help Center for users is now available to you. You can access it from the interface using the link to the Help Center. Specific information on a certain application can be directly accessed using a help symbol in the application. The Help Center offers the following content: Jump Start Guide: All the information you need to quickly find your way around the user interface. Online-Tutorial: Supplements the jump start guide and gives an overview of the CRM user interface. ______________________________________________________________ SAP AG 3 SAP-System ______________________________________________________________ - Tell Me About...: Application overview for all CRM functions, such as sales orders, opportunities, and campaigns. Note that the Help Center is not available in the E-Commerce applications. Adjustment of User Documentation You can adjust the SAP user documentation to be company- and process-specific. In order to do this, use the authoring-, translation- or administrator environments in the SAP NetWeaver Knowledge Warehouse (KW), with which you can create, translate and manage documentation content. Prerequisite: You have installed SAP GUI as well as the appropriate components of SAP NetWeaver KW on the computers being used. You can find information on working with SAP NetWeaver KW in the SAP Help Portal under SAP NetWeaver -> SAP NetWeaver 2004s -> SAP NetWeaver Library -> Power User Guide -> Enterprise Knowledge Management. The user documentation was created with XML. Pay attention therefore, to the notes on working with XML content. You can find information about connecting the user documentation to the CRM system in SAP Note 1038204. 1.4 Terminology in CRM (Changed) Use This release note is only relevant if upgrading from SAP CRM 5.0. The following terms on the new CRM WebClient user interface were changed: Master Data Use Current English New English Current German New German Accounts Address Usage Address Type Adressverwendung Adressart Accounts Account Corporate Account / Individual Account Account Unternehmens -Account / Privat-Account Accounts BP Group Hierarchy Account Hierarchy Geschäftspartnergruppenhierarchie Account-Hierarchie Products Vendor Supplier Lieferant (unchanged) Products Category Hierarchy Product Hierarchy Kategoriehierarchie Produkthierarchie ______________________________________________________________ SAP AG 4 SAP-System ______________________________________________________________ Objects Marketing Use Individual Object Object Individuelles Objekt Objekt Current English New English Current German Verantwortlicher Feldtrennzeichen Maskierungszeichen Mastergruppe Segmenttyp Segmentkategorie New German Zuständiger Trennzeichen All Areas Person Responsible Employee Responsible Mitarbeiter ELM Type of Field Separator Delimiter ELM Escape Character Text Qualifier Texterkennungszeichen Segment Builder Master Group Segmentation Basis Segmentierungsbasis Segment Builder Segment Type Usage Segment Builder Segment Category Usage Category Sales Verwendung Verwendungstyp Use Current English New English Current German Opportunities Phase Sales Stage Phase Contracts Sales Contract (unchanged) Verkaufskontrakt Activities Owner Employee Responsible Verantwortlicher Mitarbeiter Service New German Verkaufsphase Verkaufsvertrag Zuständiger Use Current English New English Current German New German Service Order Contract Service Contract Vertrag Servicevertrag Service Order Retroactive Assignment Subsequent Assignments Nachträgliche Verknüpfungen Nachträgliche Zuordnungen Contracts Listing Product List Listung Produktliste Cross Functions Use Current English New English Current German New German Business Transactions Document Flow Transaction History Belegfluss Vorgangshistorie Sales and Distribution,Service SurveyQuestionnaire Survey Fragebogen All Areas Contact Person Contact Ansprechpartner (unchanged) All Areas R/3 ECC R/3 ECC All Areas Administrative Data Administration Administrative Daten Administration All Areas Organization Organizational Data Organisation Organisationsdaten All Areas Texts Notes Texte Notizen All Areas Partner Parties Involved Partner Beteiligte Personen/Organisationen Note For information on terminology changes in condition maintenance, see the release note Terminology in Condition Maintenance (Changed). ______________________________________________________________ SAP AG 5 SAP-System ______________________________________________________________ 1.5 New, Changed and Removed IMG Activities in SAP CRM 5.2 Use Master Data - Product Catalog New IMG activities: Customer Relationship Management -> Master Data -> Product Catalog -> Define Catalog Variant Indexing Customer Relationship Management -> Master Data -> Product Catalog -> Maintain IMS Server for Catalog Indexing Customer Relationship Management -> Master Data -> Product Catalog -> Business Add-Ins for Product Catalog -> Implementation: Indexing New Product Category Information Master Data - Business Partner New IMG activity: Customer Relationship Management -> Master Data -> Business Partner -> Basic Settings -> Define Profiles. Transactions New IMG activity: Customer Relationship Management -> Transactions -> Additional Settings -> Assign Marketing Usage Types to Transaction Types Moved IMG activity: Customer Relationship Management -> Transactions -> Assign Amount Allocation Profile to Transaction Type and Item Category can now be found under Transactions -> Additional Settings. Renamed node and activities: The IMG node Customer Relationship Management -> Transactions -> Settings for Complaints -> Integration -> Business Add-Ins for Document Referencing is renamed to Transaction Referencing The IMG activities under the node Customer Relationship Management -> Transactions -> Settings for Complaints -> Integration -> Transaction Referencing are renamed: Business Add-In: Create Complaints with Reference to External Document is renamed to BAdI: Create Complaint with Reference to External Transaction ______________________________________________________________ SAP AG 6 SAP-System ______________________________________________________________ Billing Define Object Types for Document Reference is renamed to Define Object Types for Transaction Reference Assign Business Object Types to Transaction Types is renamed to Assign Business Object Types to Transaction Types Business Add-In: Create Document Flow for Subsequent Document Reference is renamed to BAdI: Create Transaction History for Subsequent Transaction Reference Define Business Object Type for Subsequent Document Reference is renamed to Define Business Object Type for Subsequent Document Reference New IMG section: Billing -> Integration -> Transfer of Billing Documents to Foreign Trade -> Transfer to SAP GTS 3.0 and Later Releases -> Transfer of BiIling Data for Intrastat Declarations. Rebate Processing New IMG Activities: Customer Relationship Management -> Rebate Processing -> Configure Application Customer Relationship Management -> Rebate Processing -> Set Up Rebate Determination -> Assign Maintenance Group for Mass Processing Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Settlement Profiles -> Define Filters for Cancellation Requirements Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Consumable Rebate Profiles -> Define Filters for Consumable Value Calculation Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Consumable Rebate Profiles -> Define Consumable Rebate Profile Customer Relationship Management -> Rebate Processing -> Reason Codes -> Define Reason Codes Customer Relationship Management -> Rebate Processing -> Reason Codes -> Assign Reason Codes to Process Types Customer Relationship Management -> Rebate Processing -> System Enhancements -> Business Add-Ins -> BAdI: Cancellation Requirements Customer Relationship Management -> Rebate Processing -> System Enhancements -> Business Add-Ins -> BAdI: Calculation of Consumable Rebate Value Changed IMG Activities: Customer Relationship Management -> Rebate Processing -> Set Up Rebate Determination -> Create Condition Types Customer Relationship Management -> Rebate Processing -> Define Settlement Document Type Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Define Rebate Profile Renamed IMG Activities: ______________________________________________________________ SAP AG 7 SAP-System ______________________________________________________________ - Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Filters for Base Calculation Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Filters for Scale Base Calculation Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Filters for Payment Value Calculation E-Commerce New IMG activities: Customer Relationship Management -> E-Commerce -> Basic Settings for E-Commerce -> Define Authorizations Customer Relationship Management -> E-Commerce -> Basic Settings for E-Commerce -> Business Add-Ins (BAdIs) for E-Commerce -> BAdI: Additional Search Filter Entitlement Management New IMG Activities: Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Intercompany Related Customizing Setup Customer Relationship Management -> Entitlement Management -> Basic Functions -> Inbound/ Outbound Processing -> Inbound Number Range Object Maintenance Customer Relationship Management -> Entitlement Management -> Basic Functions -> Inbound/ Outbound Processing -> Outbound Number Range Object Maintenance Customer Relationship Management -> Entitlement Management -> System Enhancements -> Assign Workflow Events to Business Workflow Events Renamed IMG Activites: From : Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Assign Pricing Procedure for Automatic Deposit Determination To: Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Setup Application Parameters From: Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Define Document Types To: Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Define Entitlement-Specific Transaction Categories - Removed IMG Activities: Customer Relationship Management -> Entitlement Management -> System Enhancements -> Maintain Appearance of Selection and Results Screens ______________________________________________________________ SAP AG 8 SAP-System ______________________________________________________________ - Customer Relationship Management -> Entitlement Management -> System Enhancements -> Business Add-Ins -> BAdI: User Interface Toolbar Enhancements Customer Relationship Management -> Entitlement Management -> System Enhancements -> Business Add-Ins -> BAdI: Customer Exits for Serial Number Basic Functions New IMG Activities: Customer Relationship Management -> Basic Functions -> Pricing -> Pricing in the Business Transaction -> Define Mapping for Condition Types from Application BBP to Application CRM Effects on Existing Data 1.6 New, Changed and Removed IMG Activities in SAP CRM 2007 Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The following IMG activities were moved from Marketing to Trade Promotion Management: Customer Relationship Management -> Trade Promotion Management -> Basic Data for Trade Promotion Management -> Define Default Buying Pattern Types Customer Relationship Management -> Trade Promotion Management -> Basic Data for Trade Promotion Management -> Assign Planning Account Hierarchy Tree Customer Relationship Management -> Trade Promotion Management -> Basic Data for Trade Promotion Management -> Define Product Planning Basis Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Product Assignments -> Assign Product Hierarchies Customer Relationship Management -> Trade Promotion Management -> Basic Data for Trade Promotion Management -> Listings and Partner/Product Ranges -> Map Listing Fields Customer Relationship Management -> Trade Promotion Management -> Basic Data for Trade Promotion Management -> Listings and Partner/Product Ranges -> Assign Listing Procedures and Set PPR Indicator Customer Relationship Management -> Trade Promotion Management -> Basic Data for Trade Promotion Management -> Listings and Partner/Product Ranges -> BAdI: Define Listing Checks - ______________________________________________________________ SAP AG 9 SAP-System ______________________________________________________________ - Customer Relationship Management -> Trade Promotion Management -> Basic Data for Trade Promotion Management -> Business Add-Ins -> BAdI: Advanced Checks for Additional Date Ranges Customer Relationship Management -> Trade Promotion Management -> Key Figure Planning -> Define Planning Profile Groups Customer Relationship Management -> Trade Promotion Management -> Trade Spends -> Define Trade Spends for Values Customer Relationship Management -> Trade Promotion Management -> Trade Spends -> BAdI: Trade Spends in Marketing Planning Customer Relationship Management -> Trade Promotion Management -> Condition Maintenance -> Assign Condition Maintenance Group Customer Relationship Management -> Trade Promotion Management -> Condition Maintenance -> Define Condition Generation Customer Relationship Management -> Trade Promotion Management -> Condition Maintenance -> Assign Condition Generation Type Customer Relationship Management -> Trade Promotion Management -> Condition Maintenance -> Check Data Volumes for Condition Generation Customer Relationship Management -> Trade Promotion Management -> Condition Maintenance -> Define Currency Units for Cross-Order Caps Customer Relationship Management -> Trade Promotion Management -> Condition Maintenance -> BAdI for Generating Conditions Customer Relationship Management -> Trade Promotion Management -> Check Data Volume for Deal Generation - Trade Promotion Management - Basic Data New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Define Status Driven Events Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Define Uplift Customer Relationship Management -> Marketing -> General Settings -> Define Rates Origin Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Products -> Select Item Category Groups for Display Pallets Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Add TPM-Specific Fields in Segmentation Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Versions -> Define Version Based on Status Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Versions -> Define Versions User Interface ______________________________________________________________ SAP AG 10 SAP-System ______________________________________________________________ - Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Versions -> Business Add-Ins -> BAdI: Versioning Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Rules Setup -> Define Rule Contexts Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Rules Setup -> Define Rule Events Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Rules Setup -> Business Add-Ins -> BAdI: Rule Messages Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Rules Setup -> Business Add-Ins -> BAdI: Critical Change Runs Trade Promotion Management - Key Figure Planning New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Key Figure Planning -> Settings for Display of BI Key Figures -> Define Key Figure Queries Customer Relationship Management -> Trade Promotion Management -> Key Figure Planning -> Settings for Display of BI Key Figures -> Map BI Key Figures to List Fields Customer Relationship Management -> Trade Promotion Management -> Key Figure Planning -> Settings for Display of BI Key Figures -> Maintain Design Layers Trade Promotion Management - Trade Promotions - Funds Integration New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Funds Integration -> Define Settings for Funds Integration Trade Promotion Management - Trade Promotions - Claims Integration New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Claims Integration -> Maintain Transaction Types for Invoice Claims Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Claims Integration -> Business Add-Ins > BAdI: Data Modifications for Scheduled Claims Trade Promotion Management - Trade Promotions - Causals New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Causals -> Define Causal Profiles, Causal Types and Default Values Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Causals -> Assign Causal Profiles for Marketing Planning Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Causals -> Maintain Attributes and Key Values for Causals Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Causals -> Map Key Figures for Causals ______________________________________________________________ SAP AG 11 SAP-System ______________________________________________________________ - Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Causals -> Maintain Customer Fields for Causals Trade Promotion Management - Trade Promotions - Trade Spends New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Define Trade Spends for Values Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Tiered Growth Rebates -> Define Tiered Growth Rebate Types Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Tiered Growth Rebates -> Define Trade Spend Combinations for Tiered Growth Rebates Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Tiered Growth Rebates -> Define BI Content Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Tiered Growth Rebates -> Business Add-Ins > BAdI: Performance Evaluation Criteria and Calculation Method Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Businesss Add-Ins: BAdI: Trade Spends in Marketing Planning - - Trade Promotion Management - Trade Promotions - Promotion Guidelines New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Promotion Guidelines -> Define Parameters Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Promotion Guidelines -> Define Pricing Level Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Promotion Guidelines -> Rule Categories -> Define Rule Sets Trade Promotion Management - Trade Promotions - Indirect Relationships New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Indirect Relationships -> Define Business Line Levels Trade Promotion Management - Trade Promotions - Overlap Checks New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Overlap Checks -> Define Attributes Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Overlap Checks -> Define Additional Date Ranges for Overlap Checks Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Overlap Checks -> Define Overlapping Trade Promotion Types ______________________________________________________________ SAP AG 12 SAP-System ______________________________________________________________ - Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Overlap Checks -> Business Add-Ins -> BAdI: Overlap Checks Trade Promotion Management - Agreements New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Agreements -> Define Attributes for Agreement Overlap Check Customer Relationship Management -> Trade Promotion Management -> Agreements -> Define Statuses to Ignore for Overlap Check Customer Relationship Management -> Trade Promotion Management -> Agreements -> Define Planning Transactions for Agreements Customer Relationship Management -> Trade Promotion Management -> Agreements -> Business Add-Ins -> BAdI: Agreement Overlap Check Customer Relationship Management -> Trade Promotion Management -> Agreements -> Business Add-Ins -> BAdI: Automatic Agreement Determination Customer Relationship Management -> Trade Promotion Management -> Agreements -> Business Add-Ins -> BAdI: Agreement Validation Marketing - Marketing Planning and Campaign Management Changed IMG Activities Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Basic Data -> Define Types/Objectives/Tactics Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Basic Data -> Define Additional Date Ranges Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Businesss Add-Ins: BAdI: Trade Spends in Marketing Planning Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Partner Processing -> Assign Partner Determination Procedure Marketing - Marketing Calendar Enhancements New IMG Activities Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Field Catalog Attributes for Marketing Project Display Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Selection of Calendar Attributes Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Permitted Row Context Attributes Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Split Calendar Options - Funds Management ______________________________________________________________ SAP AG 13 SAP-System ______________________________________________________________ New IMG Activities Customer Relationship Management -> Funds Management -> Define Fiscal Year Variant Funds Management - Funds Determination New IMG Activities Customer Relationship Management -> Funds Management -> Fund Determination -> Define Fund Determination Profiles Funds Management - Funds Plan and Funds New IMG Activities Customer Relationship Management -> Funds Management -> Funds Plan and Funds -> Define Fund Types Customer Relationship Management -> Funds Management -> Funds Plan and Funds -> Define Funds Plan Types Customer Relationship Management -> Funds Management -> Funds Plan and Funds -> Define Expense Types Customer Relationship Management -> Funds Management -> Funds Plan and Funds -> Assign Expense Types to Fund Types Customer Relationship Management -> Funds Management -> Funds Plan and Funds -> Define Number Ranges for Funds Plan Customer Relationship Management -> Funds Management -> Funds Plan and Funds -> Define Number Ranges for Funds Funds Management - Fund Usages New IMG Activities Customer Relationship Management -> Funds Management -> Fund Usage -> Maintain Residence Time for Archiving Customer Relationship Management -> Funds Management -> Fund Usage -> Define Number Ranges for Fund Usages Customer Relationship Management -> Funds Management -> Fund Usage -> Business Add-Ins -> BAdI: Define Archiving Actions for Fund Usages Customer Relationship Management -> Funds Management -> Fund Usage -> Business Add-Ins -> BAdI: Define Additional Functions for Fund Usages Funds Management - Checkbooks New IMG Activities Customer Relationship Management -> Funds Management -> Checkbooks-> Define Calculated Key Figures for Funds Checkbook Customer Relationship Management -> Funds Management -> Checkbooks -> Define Calculated Key Figures for Fund Usages Checkbook Customer Relationship Management -> Funds Management -> Checkbooks-> BAdI: Calculated Key Figures ______________________________________________________________ SAP AG 14 SAP-System ______________________________________________________________ Funds Management - Fund Postings New IMG Activities Customer Relationship Management -> Funds Management -> Fund Postings -> Fund Posting Archiving -> Maintain Residence Time Customer Relationship Management -> Funds Management -> Fund Postings -> Fund Posting Archiving -> Business Add-Ins -> BAdI: Archiving Actions for Fund Postings. Funds Management - Budget Postings New IMG Activities Customer Relationship Management -> Funds Management -> Budget Postings -> Assign Funds Management AVC Profile Customer Relationship Management -> Funds Management -> Budget Postings -> Fund Determination -> Assign Fund Determination Profiles Customer Relationship Management -> Funds Management -> Budget Postings -> Fund Determination -> Business Add-Ins -> BAdI: Fund Determination Parameters Customer Relationship Management -> Funds Management -> Budget Postings -> Fund Determination -> Business Add-Ins -> BAdI: Fund Determination Logic Customer Relationship Management -> Funds Management -> Budget Postings -> Business Add-Ins -> BAdI: Budget Posting Class Actions Customer Relationship Management -> Funds Management -> Budget Postings -> Business Add-Ins -> BAdI: Enhancement for New Business Transaction Components Customer Relationship Management -> Funds Management -> Budget Postings -> Business Add-Ins -> BAdI: Budget Posting Search Fund Management - Availability Control (AVC) New IMG Activities Customer Relationship Management -> Funds Management -> Availability Control (AVC) -> Define Availability Control (AVC) Check Rules Customer Relationship Management -> Funds Management -> Availability Control (AVC) -> Define Availability Control (AVC) Tolerance Profiles Customer Relationship Management -> Funds Management -> Availability Control (AVC) -> Define Availability Control (AVC) Authorization Levels Customer Relationship Management -> Funds Management -> Availability Control (AVC) -> Define Availability Control (AVC) Profiles Customer Relationship Management -> Funds Management -> Availability Control (AVC) -> Business Add-Ins -> BAdI: Fund Postings and AVC Message Variables Fund Management - Approvals New IMG Activities Customer Relationship Management -> Funds Management -> Approvals -> Define Approver Groups and Thresholds ______________________________________________________________ SAP AG 15 SAP-System ______________________________________________________________ - Customer Relationship Management -> Funds Management -> Define Approval Settings -> Business Add-Ins -> BAdI: Approval Procedure Definition Funds Management - Workflow Settings New IMG Activities Customer Relationship Management -> Funds Management -> Workflow Settings -> Implement Workflow Assignment for Funds Management Fund Management - Accruals New IMG Activities Customer Relationship Management -> Funds Management -> Accruals -> Define Accrual Reference Data Types Customer Relationship Management -> Funds Management -> Accruals -> Define Accrual Calculation Methods Customer Relationship Management -> Funds Management -> Accruals -> Define Accrual Profiles Customer Relationship Management -> Funds Management -> Accruals -> Define SAP Sales Volumes Validity Period Customer Relationship Management -> Funds Management -> Accruals -> Integration -> Transfer Accrual Documents to Accounting Customer Relationship Management -> Funds Management -> Accruals -> Business Add-Ins -> BAdI: Accrual Processes Fund Management - Batch Processing Framework New IMG Activities Customer Relationship Management -> Funds Management -> Batch Processing Framework -> Define Batch Processing Framework Component Types Customer Relationship Management -> Funds Management -> Batch Processing Framework -> Define Job Types Changed IMG Activities Customer Relationship Management -> Funds Management -> Workflow Settings -> Maintain Standard Settings for SAP Business Workflow Transactions - Basic Settings Changed IMG Activities Customer Relationship Management -> Transactions -> Basic Settings -> Define Transaction Types New IMG Activities Customer Relationship Management -> Transactions -> Basic Settings -> Define Analyzer Views for Transaction Analyzer Billing (Settlement) New IMG Activity ______________________________________________________________ SAP AG 16 SAP-System ______________________________________________________________ Billing -> Integration -> Transfer of Billing Documents to Accounting -> Transfer to Accounts Receivable (FI-AR) and Accounts Payable (FI-AP) -> Define Parameters for Prepayment UI Framework - Technical Role Definition New IMG Activities Customer Relationship Management -> UI Framework -> Technical Role Definition -> Define Working Context Profiles Customer Relationship Management -> UI Framework -> Technical Role Definition -> Define Central Search Changed IMG Activities Customer Relationship Management -> UI Framework -> Technical Role Definition -> Define Navigation Bar Profile UI Framework - Portal Integration New IMG Node Customer Relationship Management -> Portal Integration -> Overview Customer Relationship Management -> Portal Integration -> Upload Business Role Customer Relationship Management -> Portal Integration -> Map Portal Theme to CRM Skin Business Roles Changed IMG Activities Business Roles -> Define Business Role Partner Channel Management - Market Development Funds New IMG Activities Customer Relationship Management -> Partner Channel Management -> Market Development Funds -> Causals for MDF -> Define Causal Profiles, Causal Types, and Default Values Customer Relationship Management -> Partner Channel Management -> Market Development Funds -> Causals for MDF -> Assign Causal Profiles for Marketing Planning Customer Relationship Management -> Partner Channel Management -> Market Development Funds -> Causals for MDF -> Define Values for MDF Standard Causals Customer Relationship Management -> Partner Channel Management -> Market Development Funds -> Causals for MDF -> Maintain Customer Fields for Causals Interaction Center WebClient New IMG Activities Customer Relationship Management -> Interaction Center WebClient -> Business Transaction -> ERP Sales Order -> Business Add-Ins -> BAdI: Change DDLB Values for Product Proposals Customer Relationship Management -> Interaction Center WebClient -> Business Transaction -> ERP Sales Order -> Business Add-Ins -> BAdI: Determine Product Proposal in ERP Sales Order Changed IMG Activities ______________________________________________________________ SAP AG 17 SAP-System ______________________________________________________________ - Customer Relationship Management -> Interaction Center WebClient -> Business Transaction -> Define Business Transaction Profiles Customer Relationship Management -> Interaction Center WebClient -> Basic Functions -> Communication Channels -> Define Toolbar Profiles Customer Relationship Management -> Interaction Center WebClient -> Customer-Specific System Modifications -> Define Toolbar Buttons Usage-Based Service Contract Processing New IMG Node: Customer Relationship Management -> Usage-Based Service Contract Processing Workforce Deployment New IMG Node: Customer Relationship Management -> Workforce Deployment Master Data Removed IMG Activities Customer Relationship Management -> Master Data -> Partner/Product Range -> Sort Routines -> Define Sort Routines for Business Partners Customer Relationship Management -> Master Data -> Partner/Product Range -> Sort Routines -> Define Sort Routines for Products New IMG Activity Customer Relationship Management -> Master Data -> Business Partner -> Accounts and Contacts -> Business Add-Ins -> Implementation: Filtering of BP Roles by Authorization Check Channel Sales for High Tech The IMG activities for Channel Sales and Channel Sales for High Tech were moved from Customer Relationship Management -> Channel Sales and Customer Relationship Management -> Channel Sales -> Industry Specific Channel Sales -> Channel Sales for High Tech to: Customer Relationship Management -> Industry-Specific Solutions -> High Tech. This section has been partly restructured and includes two new activities: Maintain Business Partner Settings Assign Business Partner Functions to Business Partner Types Media - Intellectual Property Management New IMG Activities Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Basic Functions -> Pricing -> Define Scale Retroactivity Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Master Data ->Product -> Basic Settings -> Define Characteristics of IPM IP Check Messages Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Master Data ->Define Rights Templates Types Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Transactions ->Define User Interface Scenarios - ______________________________________________________________ SAP AG 18 SAP-System ______________________________________________________________ - Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights and Royalties Dimensions -> Define Rights Maintenance Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights Availability Analysis -> CRM WebClient UI -> Define Number Ranges for Rights Availability Requests Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights Availability Analysis -> CRM WebClient UI -> Configure Rights Availability Wizard Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights Availability Analysis -> CRM WebClient UI -> Define Rights Availability Scenarios Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Master Data ->Product -> Settings for Rights Generation -> Define Inheriting Relationship Types for Generation Formulas Customer Relationship Management -> Industry-Specific Solutions -> Utilities Industries -> Settings for User Interfaces -> General Functions -> Define Object Hierarchy and Object Attributes Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Master Data ->Product -> BAdIs -> Activate Copying of Interlinkages - - - - - Moved IMG Activities: Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Basic Functions -> Pricing -> BAdI for Additional Quantity-Type Fields in Pricing is now found under Pricing ->BAdIs. Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Basic Functions -> Pricing -> BAdI Used to Calculate Additional Data Values is now found under Pricing ->BAdIs. - Removed IMG Activity: Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights and Royalties Dimensions -> Generate People Centric UI for Rights and Royalties Dimensions Sales Transactions New IMG Activities User Management New IMG Activities Customer Relationship Management -> Basic Functions -> Actions -> Actions in User Management -> Create Actions with Wizard Customer Relationship Management -> Transactions -> Settings for Sales Transactions -> Define Profile for ERP Sales Transactions ______________________________________________________________ SAP AG 19 SAP-System ______________________________________________________________ - Customer Relationship Management -> Basic Functions -> Actions -> Actions in User Management -> Define Change Actions and Conditions -> Define Action Profiles and Actions Customer Relationship Management -> Basic Functions -> Actions -> Actions in User Management -> efine Change Actions and Conditions -> Define Start and Schedule Conditions Customer Relationship Management -> Master Data -> Business Partner -> Basic Settings -> Define Settings for E-Mail Notifications 1.7 New, Changed and Removed Customizing Activities in SAP CRM 2007 (Enhanced for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The following IMG activities were moved from Marketing to Trade Promotion Management: Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Define Default Buying Pattern Types Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Assign Planning Account Hierarchies Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Products -> Define Product Planning Basis Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Product Assignments -> Assign Product Hierarchies Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Listings and Partner/Product Ranges -> Map Listing Fields Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Listings and Partner/Product Ranges -> Assign Listing Procedures and Set PPR Indicator Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Listings and Partner/Product Ranges -> BAdI: Listing Checks Customer Relationship Management -> Trade Promotion Management -> Basic Data -> BAdI: Advanced Checks for Additional Date Ranges ______________________________________________________________ SAP AG 20 SAP-System ______________________________________________________________ - Customer Relationship Management -> Trade Promotion Management -> Key Figure Planning -> Define Planning Profile Groups Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Define Trade Spends for Values Customer Relationship Management -> Trade Promotion Management -> Trade Promotions ->Trade Spends -> BAdI: Trade Spends in Marketing Planning Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Condition Maintenance -> Assign Condition Maintenance Group Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Condition Maintenance -> Define Condition Generation Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Condition Maintenance -> Assign Condition Generation Types Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Condition Maintenance -> Check Data Volumes for Condition Generation Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Condition Maintenance -> Define Currency Units for Cross-Order Caps Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Condition Maintenance -> Business AddIns (BAdIs) -> BAdI for Condition Generation Customer Relationship Management -> Trade Promotion Management -> Check Data Volume for Deal Generation Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> BAdI: Trade Spends in Marketing Planning Trade Promotion Management - Basic Data New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Define Status Driven Events Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Define Uplifts Customer Relationship Management -> Trade Promotion Management -> Basic Data-> Define Rates Origin Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Products -> Select Item Category Groups for Display Pallets Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Add TPM-Specific Fields in Segmentation Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Versions -> Define Version Based on Status Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Versions -> Define Versions User Interface ______________________________________________________________ SAP AG 21 SAP-System ______________________________________________________________ - Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Versions -> Business Add-Ins (BAdIs) -> BAdI: Versioning Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Rules Setup -> Define Rule Contexts Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Rules Setup -> Define Rule Events Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Rules Setup -> Business Add-Ins (BAdIs) -> BAdI: Rule Messages Customer Relationship Management -> Trade Promotion Management -> Basic Data -> Rules Setup -> Business Add-Ins (BAdIs) -> BAdI: Critical Change Runs Trade Promotion Management - Key Figure Planning New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Key Figure Planning -> Settings for Display of BI Key Figures -> Define Key Figure Queries Customer Relationship Management -> Trade Promotion Management -> Key Figure Planning -> Settings for Display of BI Key Figures -> Map BI Key Figures to List Fields Customer Relationship Management -> Trade Promotion Management -> Key Figure Planning -> Settings for Display of BI Key Figures -> Maintain Design Layers Changed IMG Activities Customer Relationship Management -> Trade Promotion Management -> Key Figure Planning -> Define Parameters for SAP NetWeaver BI Analysis Trade Promotion Management - Trade Promotions - Funds Integration New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Funds Integration -> Define Settings for Funds Integration Trade Promotion Management - Trade Promotions - Claims Integration New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Claims Integration -> Maintain Transaction Types for Invoice Claims Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Claims Integration -> Business Add-Ins (BAdIs) -> BAdI: Data Modifications for Scheduled Claims Trade Promotion Management - Trade Promotions - Causals New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Causals -> Define Causal Profiles, Types and Default Values ______________________________________________________________ SAP AG 22 SAP-System ______________________________________________________________ - Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Causals -> Assign Causal Profiles for Marketing Planning Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Causals -> Maintain Attributes and Key Values for Causal Fields Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Causals -> Map Key Figures for Causals Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Causals -> Maintain Customer Fields for Causals Trade Promotion Management - Trade Promotions - Trade Spends New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Define Trade Spends for Values Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Tiered Growth Rebates -> Define Tiered Growth Rebate Types Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Tiered Growth Rebates -> Define Trade Spend Combinations for Tiered Growth Rebates Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Tiered Growth Rebates -> Define BI Content Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> Tiered Growth Rebates -> Business Add-Ins > BAdI: Performance Evaluation Criteria and Calculation Method Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Trade Spends -> BAdI: Trade Spends in Marketing Planning - - Trade Promotion Management - Trade Promotions - Promotion Guidelines New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Promotion Guidelines -> Define Parameters Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Promotion Guidelines -> Define Pricing Levels Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Promotion Guidelines -> Define Rule Sets Trade Promotion Management - Trade Promotions - Indirect Relationships New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Indirect Relationships -> Define Business Line Levels Trade Promotion Management - Trade Promotions - Overlap Checks New IMG Activities ______________________________________________________________ SAP AG 23 SAP-System ______________________________________________________________ - Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Overlap Checks -> Define Attributes Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Overlap Checks -> Define Additional Date Ranges for Overlap Checks Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Overlap Checks -> Define Overlapping Trade Promotion Types Customer Relationship Management -> Trade Promotion Management -> Trade Promotions -> Overlap Checks -> Business Add-Ins (BAdIs) -> BAdI: Overlap Checks Trade Promotion Management - Agreements New IMG Activities Customer Relationship Management -> Trade Promotion Management -> Agreements -> Define Attributes for Agreement Overlap Check Customer Relationship Management -> Trade Promotion Management -> Agreements -> Define Statuses to Ignore for Overlap Check Customer Relationship Management -> Trade Promotion Management -> Agreements -> Define Planning Transactions for Agreements Customer Relationship Management -> Trade Promotion Management -> Agreements -> Business Add-Ins (BAdIs) -> BAdI: Agreement Overlap Check Customer Relationship Management -> Trade Promotion Management -> Agreements -> Business Add-Ins (BAdIs) -> BAdI: Automatic Agreement Determination Customer Relationship Management -> Trade Promotion Management -> Agreements -> Business Add-Ins (BAdIs) -> BAdI: Agreement Validation Marketing - Marketing Planning and Campaign Management Changed IMG Activities Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Basic Data -> Define Types/Objectives/Tactics Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Basic Data -> Define Additional Date Ranges Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Partner Processing -> Assign Partner Determination Procedure Account Planning Changed IMG Activities Customer Realtionship Management -> Account Planning -> Key Figure Planning -> Define Parameters for SAP NetWeaver BI Analysis Marketing - Marketing Planning and Campaign Management - Marketing Calendar New IMG Activities ______________________________________________________________ SAP AG 24 SAP-System ______________________________________________________________ - Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Field Catalog Attributes for Marketing Project Display Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Selection of Calendar Attributes Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Permitted Row Context Attributes Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Split Calendar Options Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Add KPI to Views in the Marketing Calendar Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Map Input Variable for SAP NetWeaver BI Query Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define KPI for KPI Grouping in a View Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Ranges for KPI Grouping - Changed IMG Activities Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Views for Marketing Calendar Marketing - Digital Asset Management Changed IMG Activities Customer Relationship Management -> Marketing -> Digital Asset Management -> Maintain General Settings in DAM Customer Relationship Management -> Marketing -> Digital Asset Management -> Security and Authorization Concept -> Security and Authorizations Customer Relationship Management -> Marketing -> Digital Asset Management -> Settings in Portal Customer Relationship Management -> Marketing -> Digital Asset Management -> Conversion Service -> Define Converter Customer Relationship Management -> Marketing -> Digital Asset Management -> Conversion Service -> Define Server Customer Relationship Management -> Marketing -> Digital Asset Management -> Conversion Service -> Assign Additional Information to a File Format Customer Relationship Management -> Marketing -> Digital Asset Management -> Conversion Service -> Create Parameters for Conversion Service Claims Management This node is completely new for CRM 2007. ______________________________________________________________ SAP AG 25 SAP-System ______________________________________________________________ Funds Management New IMG Activities Customer Relationship Management -> Funds Management -> Define Fiscal Year Variant Funds Management - Funds Determination New IMG Activities Customer Relationship Management -> Funds Management -> Fund Determination -> Define Fund Determination Profiles Funds Management - Funds Plan and Funds New IMG Activities Customer Relationship Management -> Funds Management -> Funds Plan and Funds -> Define Fund Types Customer Relationship Management -> Funds Management -> Funds Plan and Funds -> Define Funds Plan Types Customer Relationship Management -> Funds Management -> Funds Plan and Funds -> Define Expense Types Customer Relationship Management -> Funds Management -> Funds Plan and Funds -> Assign Expense Types to Fund Types Customer Relationship Management -> Funds Management -> Funds Plan and Funds -> Define Number Ranges for Funds Plans Customer Relationship Management -> Funds Management -> Funds Plan and Funds -> Define Number Ranges for Funds Funds Management - Fund Usages New IMG Activities Customer Relationship Management -> Funds Management -> Fund Usages -> Maintain Residence Time for Archiving Customer Relationship Management -> Funds Management -> Fund Usages -> Define Number Ranges for Fund Usages Customer Relationship Management -> Funds Management -> Fund Usages -> Business Add-Ins (BAdIs) -> BAdI: Define Archiving Actions for Fund Usages Customer Relationship Management -> Funds Management -> Fund Usages-> Business Add-Ins (BAdIs)-> BAdI: Define Additional Functions for Fund Usages Funds Management - Checkbooks New IMG Activities Customer Relationship Management -> Funds Management -> Checkbooks-> Define Calculated Key Figures for Funds Checkbook Customer Relationship Management -> Funds Management -> Checkbooks -> Define Calculated Key Figures for Fund Usages Checkbook ______________________________________________________________ SAP AG 26 SAP-System ______________________________________________________________ - Customer Relationship Management -> Funds Management -> Checkbooks-> Business Add-Ins (BAdIs) -> BAdI: Calculated Key Figures Funds Management - Fund Postings New IMG Activities Customer Relationship Management -> Funds Management -> Fund Postings -> Maintain Residence Time for Archiving Customer Relationship Management -> Funds Management -> Fund Postings -> Business Add-Ins (BAdIs) -> BAdI: Archiving Actions for Fund Postings. Funds Management - Budget Postings New IMG Activities Customer Relationship Management -> Funds Management -> Budget Postings -> Assign Funds Management AVC Profile Customer Relationship Management -> Funds Management -> Budget Postings -> Fund Determination -> Assign Fund Determination Profiles Customer Relationship Management -> Funds Management -> Budget Postings -> Fund Determination -> Business Add-Ins (BAdIs) -> BAdI: Fund Determination Parameters Customer Relationship Management -> Funds Management -> Budget Postings -> Fund Determination -> Business Add-Ins (BAdIs) -> BAdI: Fund Determination Logic Customer Relationship Management -> Funds Management -> Budget Postings -> Business Add-Ins (BAdIs) -> BAdI: Budget Posting Class Actions Customer Relationship Management -> Funds Management -> Budget Postings -> Business Add-Ins (BAdIs) -> BAdI: Enhancement for New Business Transaction Components Customer Relationship Management -> Funds Management -> Budget Postings -> Business Add-Ins (BAdIs) -> BAdI: Budget Posting Search Funds Management - Availability Control (AVC) New IMG Activities Customer Relationship Management -> Funds Management -> Availability Control (AVC) -> Define Availability Control (AVC) Check Rules Customer Relationship Management -> Funds Management -> Availability Control (AVC) -> Define Availability Control (AVC) Tolerance Profiles Customer Relationship Management -> Funds Management -> Availability Control (AVC) -> Define Availability Control (AVC) Authorization Levels Customer Relationship Management -> Funds Management -> Availability Control (AVC) -> Define Availability Control (AVC) Profiles Customer Relationship Management -> Funds Management -> Availability Control (AVC) -> Business Add-Ins (BAdIs) -> BAdI: Fund Postings and AVC Message Variables Fund Management - Approvals New IMG Activities ______________________________________________________________ SAP AG 27 SAP-System ______________________________________________________________ - Customer Relationship Management -> Funds Management -> Approvals -> Define Approver Groups and Thresholds Customer Relationship Management -> Funds Management -> Business Add-Ins (BAdIs) -> BAdI: Approval Procedure Definition Funds Management - Workflow Settings New IMG Activities Customer Relationship Management -> Funds Management -> Workflow Settings -> Implement Workflow Assignment for Funds Management Fund Management - Accruals New IMG Activities Customer Relationship Management -> Funds Management -> Accruals -> Define Accrual Reference Data Types Customer Relationship Management -> Funds Management -> Accruals -> Define Accrual Calculation Methods Customer Relationship Management -> Funds Management -> Accruals -> Define Accrual Profiles Customer Relationship Management -> Funds Management -> Accruals -> Define SAP ERP Sales Volumes Validity Period Customer Relationship Management -> Funds Management -> Accruals -> Transfer Accrual Documents to Accounting Customer Relationship Management -> Funds Management -> Accruals -> Business Add-Ins (BAdIs)-> BAdI: Accrual Processes Master Data - Counters and Readings All IMG activities for counters and readings are grouped into the sub-section Counters and Readings, which you can find in the following sections of the IMG: Customer Relationship Management -> Master Data (replacing the section Counters) Customer Relationship Management -> Usage-Based Service Contract Processing Basic Functions - Batch Processing Framework New IMG Activities Customer Relationship Management -> Basic Functions -> Batch Processing Framework -> Define Batch Processing Framework Component Types Customer Relationship Management -> Basic Functions -> Batch Processing Framework -> Define Job Types Changed IMG Activities Customer Relationship Management -> Funds Management -> Workflow Settings -> Maintain Standard Settings for SAP Business Workflow Transactions - Basic Settings Changed IMG Activities ______________________________________________________________ SAP AG 28 SAP-System ______________________________________________________________ - Customer Relationship Management -> Transactions -> Basic Settings -> Define Transaction Types New IMG Activities Customer Relationship Management -> Transactions -> Basic Settings -> Define Analysis Views Basic Functions - Access Control Engine Removed IMG Activity Customer Relationship Management -> Basic Functions -> Access Control Engine -> Delivered ACE Rights and Their Uses Billing (Settlement) New IMG Activity Customer Relationship Management -> Billing -> Integration -> Transfer of Billing Documents to Accounting -> Transfer to Accounts Receivable (FI-AR) and Accounts Payable (FI-AP) -> Define Parameters for Prepayment UI Framework - Technical Role Definition New IMG Activities Customer Relationship Management -> UI Framework -> Technical Role Definition -> Define Working Context Profiles Customer Relationship Management -> UI Framework -> Technical Role Definition -> Define Central Search Customer Relationship Management -> UI Framework -> UI Framework Definition -> Business Add-Ins (BAdIs) -> Define Configuration Access -> BAdI: Configuration Access Determination New IMG Node Customer Relationship Management -> UI Framework -> Technical Role Definition -> Transaction Launcher Changed IMG Activities Customer Relationship Management -> UI Framework -> Technical Role Definition -> Define Navigation Bar Profile Customer Relationship Management -> UI Framework -> Technical Role Definition -> Define Parameters UI Framework - Portal Integration New IMG Node Customer Relationship Management -> Portal Integration -> Overview New IMG Activities Customer Relationship Management -> Portal Integration -> Upload Business Role Customer Relationship Management -> Portal Integration -> Map Portal Theme to CRM Skin UI Framework - UI Framework Definition ______________________________________________________________ SAP AG 29 SAP-System ______________________________________________________________ New IMG Activity Customer Relationship Management -> UI Framework -> UI Framework Definition -> Web Services -> Web Service Consumption Tool: Create BOL Objects Business Roles Changed IMG Activities Customer Relationship Management -> Business Roles -> Define Business Role Partner Channel Management - Basic Settings Removed IMG Activities Customer Relationship Management -> Partner Channel Management -> Basic Settings -> Access Control Engine New IMG Activities Customer Relationship Management -> Partner Channel Management -> CRM ACE Rights Delivered for PCM Scenarios Partner Channel Management - Market Development Funds New IMG Activities Customer Relationship Management -> Partner Channel Management -> Market Development Funds -> Causals for MDF -> Define Causal Profiles, Causal Types, and Default Values Customer Relationship Management -> Partner Channel Management -> Market Development Funds -> Causals for MDF -> Assign Causal Profiles for Marketing Planning Customer Relationship Management -> Partner Channel Management -> Market Development Funds -> Causals for MDF -> Define Values for MDF Standard Causals Customer Relationship Management -> Partner Channel Management -> Market Development Funds -> Causals for MDF -> Maintain Customer Fields for Causals Interaction Center WebClient New IMG Activities Customer Relationship Management -> Interaction Center WebClient -> Basic Functions -> Client Switch -> Define Work Client Settings Customer Relationship Management -> Interaction Center WebClient -> Basic Functions -> Client Switch -> Define Client Switch Profile Customer Relationship Management -> Interaction Center WebClient -> Business Transaction -> ERP Sales Order -> Business Add-Ins -> BAdI: Change DDLB Values for Product Proposals Customer Relationship Management -> Interaction Center WebClient -> Business Transaction -> ERP Sales Order -> Business Add-Ins -> BAdI: Determine Product Proposal in ERP Sales Order Changed IMG Activities Customer Relationship Management -> Interaction Center WebClient -> Business Transaction -> Define Business Transaction Profiles ______________________________________________________________ SAP AG 30 SAP-System ______________________________________________________________ - Customer Relationship Management -> Interaction Center WebClient -> Basic Functions -> Communication Channels -> Define Toolbar Profiles Customer Relationship Management -> Interaction Center WebClient -> Customer-Specific System Modifications -> Define Toolbar Buttons Usage-Based Service Contract Processing New IMG Node: Customer Relationship Management -> Usage-Based Service Contract Processing Workforce Deployment New IMG Node: Customer Relationship Management -> Workforce Deployment Master Data Removed IMG Activities Customer Relationship Management -> Master Data -> Partner/Product Range -> Sort Routines -> Define Sort Routines for Business Partners Customer Relationship Management -> Master Data -> Partner/Product Range -> Sort Routines -> Define Sort Routines for Products New IMG Activities Customer Relationship Management -> Master Data -> Business Partner -> Data Quality Administration Customer Relationship Management -> Master Data -> Business Partner -> Business Add-Ins -> Implementation: Filtering of BP Roles by Authorization Check Channel Sales for High Tech The IMG activities for Channel Sales and Channel Sales for High Tech were moved from Customer Relationship Management -> Channel Management -> Channel Sales and Customer Relationship Management -> Channel Management -> Channel Sales -> Industry Specific Channel Sales -> Channel Sales for High Tech to: Customer Relationship Management -> Industry-Specific Solutions -> High Tech. This section has been partly restructured. Media - Intellectual Property Management New IMG Activities Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Basic Functions -> Pricing -> Define Scale Retroactivity Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Master Data ->Product -> Basic Settings -> Define Characteristics of IPM IP Check Messages Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Master Data ->Define Rights Templates Types Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Transactions ->Settings for IPM Transactions -> Define User Interface Scenarios - ______________________________________________________________ SAP AG 31 SAP-System ______________________________________________________________ - Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights and Royalties Dimensions -> Define Rights Maintenance Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights Availability Analysis -> CRM WebClient UI -> Define Number Ranges for Rights Availability Requests Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights Availability Analysis -> CRM WebClient UI -> Configure Rights Availability Wizard Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights Availability Analysis -> CRM WebClient UI -> Define Rights Availability Scenarios Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Master Data ->Product -> Settings for Rights Generation -> Define Inheriting Relationship Types for Generation Formulas Customer Relationship Management -> Industry-Specific Solutions -> Utility Industries -> Settings for User Interfaces -> General Functions -> Define Object Hierarchy and Object Attributes Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Master Data ->Product -> BAdIs -> BAdI: Activate Copying of Interlinkages - - - - Moved IMG Activities: Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Basic Functions -> Pricing -> BAdI for Additional Quantity-Type Fields in Pricing is now found under Pricing ->BAdIs. Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Basic Functions -> Pricing -> BAdI Used to Calculate Additional Data Values is now found under Pricing ->BAdIs. - Removed IMG Activity: Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights and Royalties Dimensions -> Generate People Centric UI for Rights and Royalties Dimensions Sales Transactions New IMG Activities Customer Relationship Management -> Transactions -> Settings for Sales Transactions -> Define Profile for ERP Sales Transactions User Management New IMG Activities Customer Relationship Management -> Basic Functions -> Actions -> Actions in User Management -> Create Actions with Wizard Customer Relationship Management -> Basic Functions -> Actions -> Actions in User Management -> Change Actions and Conditions -> Define Action Profiles and Actions ______________________________________________________________ SAP AG 32 SAP-System ______________________________________________________________ - Customer Relationship Management -> Basic Functions -> Actions -> Actions in User Management -> Change Actions and Conditions -> Define Start and Schedule Conditions Customer Relationship Management -> Master Data -> Business Partner -> Basic Settings -> Define Settings for E-Mail Notifications 1.8 CRM-MD Master Data 1.8.1 New, Changed and Removed IMG Activities in SAP CRM 5.1 and SAP CRM 5.2 Use This release note is only relevant if upgrading from SAP CRM 5.0. Layout of User Interface (People Centric CRM) Removed IMG activities: Customer Relationship Management -> Layout of User Interface (People-Centric CRM) All activities under this node have been removed. Basic Functions New IMG activities: o Customer Relationship Management -> Basic Functions -> Worklist -> Define Alert Inbox and Workflow Inbox -> Define Task-Specific Navigation o Customer Relationship Management -> Basic Functions -> Worklist -> Define Alert Inbox and Workflow Inbox -> Define Alert-Specific Navigation o Customer Relationship Management -> Basic Functions -> Pricing -> Pricing in the Business Transaction -> Define Mapping for Condition Types from Application BBP to Application CRM Master Data - Organizational Management New IMG node: Customer Relationship Management -> Master Data -> Organizational Management -> Assignment of ______________________________________________________________ SAP AG 33 SAP-System ______________________________________________________________ Organizational Units from SAP ECC All the activities under this node are new. They have been isolated from the activities Organizational Model -> Create Organizational Model and -> Change Organizational Model so that you can maintain only the mapping of the organizational units between SAP ECC and SAP CRM. The organizational model itself can now be maintained in the CRM Web UI. If you have already made settings for a former release, you do not need to make any further changes. Master Data - Product New IMG nodes: o Customer Relationship Management -> Master Data -> Products -> Settings for Configurable Products o The activity Define Settings for Product Models is new. Customer Relationship Management -> Master Data -> Products -> Settings for Packages The activity Assign Product Roles to Categories is new. Removed IMG activities: o Customer Relationship Management -> Master Data -> Products -> Settings for Product Type -> Define Product Template for Configurable Products o Customer Relationship Management -> Master Data -> Products -> Objects -> Specify Display Option for Object Structure o Customer Relationship Management -> Master Data -> Products -> Objects -> Define Available Catalogs for Object Structure o Customer Relationship Management -> Master Data -> Products -> Objects -> BAdI: Include External Catalogs for Object Structure o Customer Relationship Management -> Master Data -> Products -> Objects -> Activate Map Visualization of Location Master Data - Partner/Product Range Removed IMG activity: o Customer Relationship Management -> Master Data -> Partner/Product Range -> Assign PPR Types to PPR Listings Master Data - Business Partner New IMG activity: o Customer Relationship Management -> Master Data -> Business Partner -> Basic Settings -> Define Profiles. Removed IMG activity: o Customer Relationship Management -> Master Data -> Business Partner -> Basic Settings -> Assign Templates for Content Management Folder to BP Roles Master Data - Product Catalog New IMG activities: ______________________________________________________________ SAP AG 34 SAP-System ______________________________________________________________ o Customer Relationship Management -> Master Data -> Product Catalog -> Define Catalog Variant Indexing o Customer Relationship Management -> Master Data -> Product Catalog -> Maintain IMS Server for Catalog Indexing o Customer Relationship Management -> Master Data -> Product Catalog -> Business Add-Ins for Product Catalog -> Implementation: Indexing New Product Category Information o Customer Relationship Management -> Master Data -> Product Catalog -> Define Templates for Folders Account Planning New IMG activity: Customer Relationship Management -> Account Planning -> Product Assignments -> Define Product Planning Basis Removed IMG activity: Customer Relationship Management -> Account Planning -> General Settings -> Define Field Selection Transactions New IMG activity: o Customer Relationship Management -> Transactions -> Additional Settings -> Assign Marketing Usage Types to Transaction Types Moved IMG activity: o Customer Relationship Management -> Transactions -> Assign Amount Allocation Profile to Transaction Type and Item Category can now be found under Transactions -> Additional Settings. Renamed node and activities: o The IMG node Customer Relationship Management -> Transactions -> Settings for Complaints -> Integration -> Business Add-Ins for Document Referencing is renamed to Transaction Referencing o The IMG activities under the node Customer Relationship Management -> Transactions -> Settings for Complaints -> Integration -> Transaction Referencing are renamed: Business Add-In: Create Complaints with Reference to External Document is renamed to BAdI: Create Complaint with Reference to External Transaction Define Object Types for Document Reference is renamed to Define Object Types for Transaction Reference Assign Business Object Types to Transaction Types is renamed to Assign Business Object Types to Transaction Types Business Add-In: Create Document Flow for Subsequent Document Reference is renamed to BAdI: Create Transaction History for Subsequent Transaction Reference Define Business Object Type for Subsequent Document Reference is renamed to Define Business Object Type for Subsequent Transaction Reference ______________________________________________________________ SAP AG 35 SAP-System ______________________________________________________________ Removed sections (for functions not supported in this release): Customer Relationship Management -> Transactions -> Settings for Service Processes -> Settings for Service Resource Planning IMG activity moved: Customer Relationship Management -> Transactions -> Settings for Product Service Letters -> Define Object Reference Profile can now be found under Transactions -> Basic Settings. Grantor Program Management New IMG activities: Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Program Management -> General Settings -> Define Program Profile Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Program Management -> General Settings -> Define Availability Control Profile Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Program Management -> General Settings -> Define Tolerance Profile Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Change Process Management -> Define Input Field Control Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Change Process Management -> Define Change Processes Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Change Process Management -> Customer Enhancements for Change Process Management Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Change Process Management -> BAdI: Customer Enhancements for Web Requests Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Basic Functions for Grantor Processing Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Financial Transactions -> Define Financial Execution Type Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Financial Transactions -> Pricing -> Define Value Type Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Financial Transactions -> Define Billing Plan Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Actions in Grantor Processing Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Web Requests for Grantor Management ______________________________________________________________ SAP AG 36 SAP-System ______________________________________________________________ Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Business Add-Ins -> BAdI: Customer Enhancements for Grantor Agreement Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Business Add-Ins -> BAdI: Customer Enhancements for Grantor Application Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Business Add-Ins -> BAdI: Customer Enhancements for Grantor Claim Changed IMG activities Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Transactions in Grantor Processing Removed IMG activities Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Program Management -> Content Management Case Management New IMG activities: Customer Relationship Management -> Case Management -> Process Partners -> BAdI: Reassign Business Partners in Linked Objects Customer Relationship Management -> Case Management -> Basic Settings -> Define Search Scenario Customer Relationship Management -> Case Management -> Basic Settings -> Define Case Closing Profile Customer Relationship Management -> Case Management -> Basic Settings -> BAdI: Define Additional Tasks for Case Closing Profile Customer Relationship Management -> Case Management -> Extended Customizing -> Case Archiving -> CRM Data Archiving Process Customer Relationship Management -> Case Management -> Extended Customizing -> Case Archiving -> Display Archived Case Data Customer Relationship Management -> Case Management -> Extended Customizing -> Case Archiving -> BAdIs for Case Archiving -> BAdI: Define Checks Prior to Case Archiving Customer Relationship Management -> Case Management -> Extended Customizing -> Case Archiving -> BAdIs for Case Archiving -> BAdI: Archive Case Table Entries Customer Relationship Management -> Case Management -> Extended Customizing -> Case Archiving -> BAdIs for Case Archiving -> BAdI: Delete Case Table Entries from the Database Customer Relationship Management -> Case Management -> Extended Customizing -> Special Settings -> BAdI: BAPIs for Case Parameters -> BAdI: Change BAPI Parameters Customer Relationship Management -> Case Management -> Extended Customizing -> Special Settings -> BAdI: BAPIs for Case Parameters -> BAdI: BAPI Change Case - Change Import Parameters ______________________________________________________________ SAP AG 37 SAP-System ______________________________________________________________ Customer Relationship Management -> Case Management -> Extended Customizing -> Special Settings -> BAdI: BAPIs for Case Parameters -> BAdI: BAPI Create Case - Change Import Parameters Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> Case Import and Export with XI Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> Monitor XI Case Exports Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> Manually Export Cases Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Export Case XI Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Import Case XI Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Map XI Case Export Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Map XI Case Import Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Export Case During Save Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Export Case at Business Partner Update Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Export Case at Postal Code Update Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> Case Management Customer Enhancements in XI Customer Relationship Management -> Case Management -> Extended Customizing -> ACE Implementation for Case Management (Note: This activity describes how the delivered sample ACE implementation has been configured in case you want to create your own ACE implementation.) Removed IMG activities The following BAdIs were removed under Customer Relationship Management -> Case Management -> Extended Customizing -> Special Settings -> Define Processes -> Business Add-Ins (BAdIs): Business Add-In: Data Transfer When Creating a Case Business Add-In: Filling Customer-Specific Dropdown Lists Business Add-In: Copying Cases BAdI: Attributes for Links in Case Record BAdI: Process Control in Case Management BAdI: Process Control for Case Notes BAdI: Process Control of Derived Case Management Applications ______________________________________________________________ SAP AG 38 SAP-System ______________________________________________________________ BAdI: Enhancement for BSP Case Framework Customer Relationship Management -> Case Management -> Extended Customizing -> Special Settings -> Create Profiles -> Notes About the Function Profile and Terminology Profile All of the informational nodes were removed under Customer Relationship Management -> Case Management -> Integration in the User Interface (People-Centric UI). Customer Relationship Management -> Case Management -> Extended Customizing -> Special Settings -> Create Profiles - > Assign Profile for Document Templates to a Case Type Billing New IMG activity: Customer Relationship Management -> Billing -> Intercompany Billing -> Determine Sales Area Data for Determination of Invoice Currency New IMG section: Billing -> Integration -> Transfer of Billing Documents to Foreign Trade -> Transfer to SAP GTS 3.0 and Later Releases -> Transfer of BiIling Data for Intrastat Declarations. Usage-Based Billing This section has been removed since usage-based billing is not supported in this release. Removed IMG activities: Customer Relationship Management -> E-Commerce -> Basic Settings for E-Commerce -> Business Add-Ins (BAdIs) for E-Selling -> BAdI: Change Target System for Calling Up Availability Check in ERP Interaction Center WinClient, and Interaction Center WebClient 2005 These sections have been removed. Prior to SAP CRM 5.1, Interaction Center WebClient 2005 section was Interaction Center WebClient. Interaction Center WebClient This section is new. As of Service Pack 02 a new configuration activity was added under Interaction Center WebClient -> Basic Functions -> Communication Channels -> Configure E-Mail for SAPconnect. Marketing Planning and Campaign Management Changed IMG activities: Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Key Figure Planning -> Version Management -> Define Versions Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Key Figure Planning -> Version Management -> Define Version for System Status ______________________________________________________________ SAP AG 39 SAP-System ______________________________________________________________ Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Key Figure Planning -> Version Management -> Define Version for User Status Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> System Landscape -> Activate SAP NetWeaver BI Update Removed IMG activities: Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Key Figure Planning -> Define Parameters for BW Analyses Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Key Figure Planning -> Assign Success Key Figures to Campaign Type and Objective Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> General Settings -> Define Field Assignment for Microsoft Project Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> General Settings -> Define User Settings Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Search Tables Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Search Criteria Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Assign Search Criteria Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Field Settings for Table View Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Business Add-Ins -> Extend Standard Functions in Query for Calendar Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> User Interface Settings (all activities) Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Personalized Mail -> Maintain Print Profile Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Personalized Mail -> Define Status Profile for User Status Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Additional Fields and Business Add-Ins (BAdIs) for Marketing Planning -> Define Additional Fields: Set Types IPM Solution Management Removed IMG activities: SAP Implementation Guide -> Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights and Royalties Dimensions -> Generate People Centric UI for Rights and Royalties Dimensions ______________________________________________________________ SAP AG 40 SAP-System ______________________________________________________________ Telecommunications New IMG node: o Customer Relationship Management -> Industry-Specific Solutions -> Telecommunications -> Dispute Management Hi-Tech Moved The entire node under Customer Relationship Management -> Channel Management -> Channel Sales -> Industry-Specific Channel Sales -> Channel Sales has been moved and renamed to Customer Relationship Management -> Industry-Specific Solutions -> High Tech. Transactions being used in common with Pharma have been copied to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry. Pharma New: o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Incompleteness Procedure o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Incompleteness Procedure -> Define Incompleteness Procedure o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Evaluation and Calculation Profiles -> Define Profiles o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Evaluation and Calculation Profiles -> Assign Attributes to Profiles o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs Evaluation and Calculation Profiles -> Maintain Profile Attribute Values o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Authorizations o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Authorizations -> Define Authorization Group o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ ______________________________________________________________ SAP AG 41 SAP-System ______________________________________________________________ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance -> Define Condition Generation o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance -> Assign Condition Maintenance Group o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance -> Conflict Resolution o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance -> Activate Staging and History o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance -> Define Condition History Table o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance -> Activate History for Usage and Condition Type o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Determination of Incentive Programs -> Determine Incentive Program in Contracts o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Enhancements for Eligibility Rules o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Enhancements for Eligibility Rules -> Business Add-In: Implement Data Supply o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Enhancements for Eligibility Rules -> Enhance Rule Attribute Structures o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Enhancements -> Business Add-In: Authorization Check o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Product Assignments -> Assign Product Hierarchy o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargebacks and Sales Tracking -> Entitlement Document -> Maintain Relevancy for Claim Document Creation o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargebacks and Sales Tracking ______________________________________________________________ SAP AG 42 SAP-System ______________________________________________________________ -> Reconciliation -> Assign Outbound EDI - NWDA Codes New Textual Nodes (no activity, only reference to the actual activity): o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Text Management - Define Text Objects and Text Types o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs ->Text Management -> Define Text Determination Procedure o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Status Profile -> Change User Status Profile o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Notification Manager -> Maintain Condition Type for Notification Renamed: o Industry-Specific Solutions -> Pharmaceuticals -> Master Data is renamed to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry-> Field Sales Moved: o Activate Pharma-Specific Applications has been moved from under Industry-Specific Solutions -> Pharmaceuticals -> Master Data to Customer Relationship Management -> Life Sciences/ Pharmaceuticals Industry-> o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Channel Sales for Pharma Industry All nodes under Channel Sales for Pharma Industry that are still being used have been moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences o Customer Relationship Management -> Channel Management -> Channel Sales -> Basic Functions -> Configure Business Rules has been moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Configure Business Rules Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Configure Business Rules -> Configure Schema Access Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Configure Business Rules -> Configure Prerequisites for Process Step Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Configure ______________________________________________________________ SAP AG 43 SAP-System ______________________________________________________________ Business Rules -> Validation Classes/-Bits Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Configure Business Rules ->Configure Reconciliation-/Duplicate Check Rules -> Maintain Field Groups Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Configure Business Rules ->Configure Reconciliation-/Duplicate Check Rules -> Assign Field Groups to System Steps o Activities under the Customer Relationship Management->Channel Management-> Channel Sales - > Industry-Specific Channel Sales ->Chargeback have been moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Channel Sales for Pharma Industry -> Settings for Claim Contract Claim Contracts has been renamed and all activities under it, moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts -> Maintain Relevancies for Contracts -> Maintain Transaction Type Mapping Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts -> Maintain Relevancies for Contracts -> Maintain Partner Function Mapping Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts -> Maintain Relevancies for Contracts -> Maintain Condition Type Mapping Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts -> Maintain Relevancies for Contracts -> Maintain Date Type Mapping Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts -> Maintain Relevancies for Contracts -> Maintain Status Mapping Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts -> Enhancements -> BAdI: CMS Extract Preparation o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks -> Business Logic Enhancements is moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Enhancements for Business Logic Flow o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargeback -> Map Additional Transaction Types is moved to ______________________________________________________________ SAP AG 44 SAP-System ______________________________________________________________ Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Map Additional Transaction Types o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargeback -> Claim Processing -> Unit of Measurement Selection Method is renamed and moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Selection Method -> Selection Method for Unit of Measure o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargeback -> Claim Processing -> Contract Selection Method is moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Selection Method -> Contract Selection Method Removed: o Customer Relationship Management->Channel Management-> Industry-Specific Channel Sales ->Contracts and Chargeback for the Pharmaceutical Industry has been removed. o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks ->Duplicate Check -> Maintain Fieldgroups Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks -> Duplicate Check -> Maintain Duplicate Check Rules o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks ->Enhancement -> User Interface Enhancements -> Configure Selection Screens for Chargeback Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks ->Enhancement -> User Interface Enhancements -> Maintain screen labels for Chargeback Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks ->Enhancement -> User Interface Enhancements -> Configure Header grid display for Chargeback Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks ->Enhancement -> User Interface Enhancements -> Configure Claim Grid Display for Chargeback Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks ->Enhancement -> User Interface Enhancements -> Toolbar Enhancements Renamed nodes and activities: o The IMG node Customer Relationship Management -> E-Commerce is renamed to Web Channel o The IMG node Customer Relationship Management -> E-Commerce -> E-Selling is renamed to Customer Relationship Management -> Web Channel -> E-Commerce ______________________________________________________________ SAP AG 45 SAP-System ______________________________________________________________ o The IMG node Customer Relationship Management -> Channel Management is renamed to Customer Relationship Management -> Partner Channel Management CRM Web Channel New IMG activities: o Customer Relationship Management -> Web Channel -> Basic Settings -> Define Authorizations o Customer Relationship Management -> Web Channel -> Basic Settings -> Business Add-Ins (BAdIs) for Web Channel -> BAdI: Additional Search Filter Rebate Processing New IMG Activities: o Customer Relationship Management -> Rebate Processing -> Configure Application o Customer Relationship Management -> Rebate Processing -> Set Up Rebate Determination -> Assign Maintenance Group for Mass Processing o Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Settlement Profiles -> Define Filters for Cancellation Requirements o Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Consumable Rebate Profiles -> Define Filters for Consumable Value Calculation o Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Consumable Rebate Profiles -> Define Consumable Rebate Profile o Customer Relationship Management -> Rebate Processing -> Reason Codes -> Define Reason Codes o Customer Relationship Management -> Rebate Processing -> Reason Codes -> Assign Reason Codes to Process Types o Customer Relationship Management -> Rebate Processing -> System Enhancements -> Business Add-Ins -> BAdI: Cancellation Requirements o Customer Relationship Management -> Rebate Processing -> System Enhancements -> Business Add-Ins -> BAdI: Calculation of Consumable Rebate Value Changed IMG Activities: o Customer Relationship Management -> Rebate Processing -> Set Up Rebate Determination -> Create Condition Types o Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Settlement Profiles -> Define Settlement Document Type o Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Define Rebate Profile Renamed IMG Activities: o From: Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Base Calculation ______________________________________________________________ SAP AG 46 SAP-System ______________________________________________________________ To: Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Filters for Base Calculation o From: Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Scale Base Calculation To: Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Filters for Scale Base Calculation o From: Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Payment Value Calculation To: Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Filters for Payment Value Calculation Entitlement Management New IMG Activities: o Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Intercompany Related Customizing Setup o Customer Relationship Management -> Entitlement Management -> Basic Functions -> Inbound/ Outbound Processing -> Inbound Number Range Object Maintenance o Customer Relationship Management -> Entitlement Management -> Basic Functions -> Inbound/ Outbound Processing -> Outbound Number Range Object Maintenance o Customer Relationship Management -> Entitlement Management -> System Enhancements -> Assign Logical Events to Business Workflow Events Renamed IMG Activites: o From : Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Assign Pricing Procedure for Automatic Deposit Determination To: Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Setup Application Parameters o From: Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Define Document Types To: Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Define Entitlement-Specific Transaction Categories Removed IMG Activities: o Customer Relationship Management -> Entitlement Management -> System Enhancements -> Maintain Appearance of Selection and Results Screens o Customer Relationship Management -> Entitlement Management -> System Enhancements -> Business Add-Ins -> BAdI: User Interface Toolbar Enhancements ______________________________________________________________ SAP AG 47 SAP-System ______________________________________________________________ 1.8.2 CRM-MD-BP Business Partners 1.8.2.1 Account Life Cycle (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use a life cycle stage to record the different stages of an account as it progresses through its life cycle, with each stage representing a different view at a particular point in time. For example, an account might start off as a potential, move on to an intermediate stage as a prospect, before finally becoming a customer. A life cycle stage is closely related to a role. However, an account can have multiple roles at the same time, whereas a life cycle stage is a specific status at a particular point in time. Technically, a life cycle stage is implemented as a role within a role exclusion group, which serves to define the roles which cannot be assigned to an account at the same time, but only as a sequence. The life cycle stage can be selected in the account header and made available as a search criterion. It is delivered as hidden function and has to be activated in the configuration tool. Effects on Customizing Define Account Life Cycle, Stages, and Sequence You can specify the initial stages which can be set when an account is created, and the various subsequent life cycle stages which are allowed. To do this, choose Cross-Application Components -> Business Partner -> Basic Settings -> Business Partner Roles -> Define BP Role Exclusion Groups. A business partner role exclusion group specifies the roles that may not be assigned to a business partner at the same time. You have to create a role exclusion group for the account life cycle. You assign the relevant roles to the exclusion group. These are the life cycle stages. You define the transitions between the roles to establish a permitted sequence of life cycle stages. In this way, you can also prevent an account from returning to a previous stage. ______________________________________________________________ SAP AG 48 SAP-System ______________________________________________________________ Define Life Cycle Stage Views You can define views for each life cycle stage. This enables you to specify which fields are displayed within the header for each stage, and what types of field they are (editable, read-only, or mandatory). You can make field modifications using the BAdI for Configuring Views. You can attach or detach assignment blocks dependent on specified criteria using the BAdI for Configuring Assignments. You can preassign default values to fields at the header level of the account using the BAdI for Setting Attribute Defaults. 1.8.2.2 Account Management Functions (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Account Classification An account classification enables you to classify accounts using freely configurable criteria. This is particularly useful for large companies where, for example, different business units can be classified based on different criteria. For a certain combination of country, sales organization, and business unit, for example, the attribute role has the one value, and for another combination of the same criteria, a different value. A company could be, for example, a customer in the business unit "Automation", but a competitor in the business unit "Mobile Phones". The function is available as a separate assignment block on the Account overview page and can be integrated as a search criterion in the search function. It is also integrated in SAP NetWeaver BI and enables reporting to be performed based on the classification. Customizing The criteria you require can be flexibly combined. Each classification category consists of a maximum of five criteria, and any number of attributes. You define these in the Customizing activity Define Classification. Also see Note 1045146. Account Plans The Account Plans assignment block has been integrated in the corporate accounts overview page. It displays all accounts plans available for the account, regardless of time period and status. They are sorted by planning period, with the most recent first. You can create new account plans, and edit and delete existing account plans. The assignment block is delivered as a hidden function for individual accounts and groups. Buying Center ______________________________________________________________ SAP AG 49 SAP-System ______________________________________________________________ A buying center, representing contacts and contact relationships as already available in opportunity mangement, can now be created directly for accounts. Unlike opportunities, however, more than one buying center can be created for an account: The buying center can be used as a basis for creating this data in the opportunity. The buying center in an opportunity can be modified without this affecting the account buying center. The buying center in an opportunity can be saved as an account buying center. Using the assignment block Buying Center on the Account page, you can create a buying center for any related sales organization. Each specific buying center contains the contacts related to the account, with their respective function or functions: Each contact can be described in more detail by a selection of characteristics and values. Each contact can have relationships with other contacts involved in the same buying center. The relationships between contacts can be described in more detail by a selection of characteristics and values. The relationships between contacts can be displayed and edited in a graphical view. Copying Nodes Between Account Hierarchies Using a copy function, you can copy and paste or cut and paste hierarchy nodes between hierarchies. This means that you are able to quickly reflect changes to your organizational structure, and have the means to deal with situations such as mergers and acquisitions. You can copy and paste or cut and paste: Hierarchy nodes with all related accounts from the hierarchy you are working in to another Cut and paste hierarchy nodes with the category "Pricing" with all related accounts and pricing conditions to another hierarchy You can copy hierarchy nodes from either the overview page or edit page by clicking Copy To. This opens a dialog box in which you can select the appropriate target hierarchy. After selecting the correct target hierarchy, you navigate to a screen which displays both the source and target hierarchy. You select the relevant nodes in the source hierarchy and copy and paste or cut and paste them to the relevant point in the target hierarchy. 1.8.2.3 Internet User in Account (new) Use ______________________________________________________________ SAP AG 50 SAP-System ______________________________________________________________ This release note is only relevant if upgrading from SAP CRM 5.0. You can now create and maintain Internet users in the Account. Previously, you assigned the role Internet User to a user in the business partner transaction, in your backend SAP CRM system. This function has been moved ito the Account data maintenance in the new user interface. 1.8.2.4 Billing Account Hierarchies (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can structure accounts for billing. You do so by sorting accounts in a hierarchy. You can assign more than one subordinate account to an account, which you can then assign to sub-accounts. You can use this to split enterprises into several sub-accounts (for example, by regional organizations or subsidiaries). For example, you can insert separate accounts (with different addresses) for billing and service provision into the hierarchy. This function is primarily aimed at customers in service industries, such as the telecommunications industry, where it is normal for enterprises to deliver different services to different physical addresses or locations for the same customer. Similarly, it is possible to perform differentiated billing by enterprise area. Effects on Customizing You create roles for billing account hierarchies in Customizing for Customer Relationship Management under Industry-Specific Solutions -> Telecommunications -> Master Data -> Define Customizing Roles for Billing Account Hierarchies. 1.8.2.5 Rule-Based Assignment of Employees (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. ______________________________________________________________ SAP AG 51 SAP-System ______________________________________________________________ You can assign employees to accounts automatically based on a set of rules, which can be freely defined. These rules could, for example, be based on geography, such as country or region, or classification, such as account role or industry. They enable you to assign employees with different relationship types, together with the relevant partner functions and sales areas. Similarly, they can be used to replace existing employee relationships with the necessary data. You set up the rules you require using the rule modeler. A new context, "Account and Contact Management", is available for this purpose. When assigning employees automatically based on rules, you have two options: You can trigger rule processing directly when working with an account. This calls a fixed rule policy, which has already been customized. The proposed employee assignments are created directly and shown in the Relationships assignment block. You can accept the assignments by saving your data. Note that you do not have the option of selecting the relevant rule policy, as is the case in other areas which use the rule modeler, such as lead distribution. You can assign employees to a selection of accounts using the report CRM_BUPA_ASSIGN_EMPLOYEE. The report can be scheduled to run as frequently as required and enables you to ensure employee assignments are up-to-date. It does the following: Deletes existing relationships with the relevant categories, including partner function and sales area, where only one assignment is allowed. Creates new relationships, including partner function and sales area, based on the list returned by the rule engine. The Standard indicator is set where applicable. - You also have the option of specifically excluding accounts from assignment. The Excluded indicator is delivered as a hidden field, which can be activated for specific user roles, such as the administrator. Effects on Customizing Before you can create rule policies using the rule modeler, make the necessary settings in Customizing for Customer Relationship Management, by choosing Master Data -> Business Partner -> Accounts and Contacts -> Rule-Based Assignment of Employees. 1.8.2.6 Business Partner Fields (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The following fields are available for service parts management in the sales and shipping data on the Account page: Letter of Credit Required ______________________________________________________________ SAP AG 52 SAP-System ______________________________________________________________ This field indicates that business transactions involving the account in question require a letter of credit (LoC). The field is evaluated in order processing and passed to Global Trade Services (GTS). A check is made during clearance as to whether a letter of credit is required, and if so whether it exists and whether the conditions specified in it are met. See also Integration of Letters of Credit in the Sales Order. Maximum Number of Partial Deliveries The Partial Delivery Allowed indicator currently available in the account sales data has been enhanced by a numeric field indicating the maximum number of partial deliveries allowed to satisfy the order quantity for an item. This value is defaulted in the sales order from the ship-to party and can be overwritten. The maximum number controls the following: The deliveries from each facility independently: If an item is shipped, for example, from three different locations, and the maximum number is two, this could result in six shipments for the item. The overall limit of two is only met when the item is shipped from one location. The number of deliveries in SAP ECC: When the delivery is passed to warehouse management, the warehouse is not allowed to perform further splits. - SAP NetWeaver Business Intelligence To enable the new sales and shipping data to be integrated in SAP NetWeaver BI, the existing extractors have each been extended by a new attribute. Two new InfoObjects have been created and added to the existing InfoObject 0CRM_BP_SAL, which contains the sales-area-dependent business partner data: Characteristic: 0CRM_LOCF (Letter of Credit Required) Key Figure: 0CRM_BP_SAL (Max. Number of Deliveries) Similarly, the transfer rules between each of the DataSources and the relevant InfoSource have been extended. The relevant business content is available as of BI Content Release 7.03, support package 05. Effects on Data Transfer The Maximum Number of Partial Deliveries field is exchanged between SAP ECC and SAP CRM. The data exchange with SAP ECC is available for this field as of ERP 2005, but is not supported in releases prior to this. Since the Maximum Number of Partial Deliveries field is already available in SAP ECC, you must run the report CRM_BUPA_ANTLF_ADD after upgrading to download the contents of this field to SAP CRM. ______________________________________________________________ SAP AG 53 SAP-System ______________________________________________________________ 1.8.2.7 Data Quality Administration (New for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The data quality administration framework provides you with a set of tasks designed to eliminate duplication of data records and ensure a consistently high standard of data. The functions are available in the business partner area, and integrate the data cleansing functions already available in earlier releases. Data quality administration provides the following types of validation: Duplicate check as a technically integrated solution, including duplicate identification and duplicate merge, using SAP software or a third-party add-on. Duplicate check by a service provider (agency), including export of data records, upload of results, and post-processing of results (merge). External postal address validation (syntax validation) using an external service provider, with export of data records and upload of results, as above. Content validation for relocation and necrology using a service provider (agency), with export of data records and upload of results, as above. Effects on System Administration Data quality administration is delivered as a hidden function and has to be integrated into the role you want to use. You do this in Customizing for Customer Relationship Management under UI Framework -> Technical Role Definition. Effects on Customizing A number of standard task types are delivered, which have to be adjusted to meet your requirements. You can make the necessary settings in Customizing for Customer Relationship Management under Master Data -> Business Partner -> Data Quality Administration. 1.8.2.8 Account Fact Sheet: BI 7.x Templates (Enhanced for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The integration of BI reports into the CRM WebClient UI and therefore the account fact sheet is no longer restricted to BI 3.x templates, but now also includes BI 7.x templates. BI 7.x templates are executed by the Java runtime environment and were introduced with NetWeaver 2004s. Reports that have been migrated to BI 7.x templates are stored in the same namespace as previously. ______________________________________________________________ SAP AG 54 SAP-System ______________________________________________________________ To use 7.x templates in the account fact sheet, you need to do the following: 1. In Customizing, you define the BI report with a report ID and the BI template 7.x, under Customer Relationship Management -> UI Framework -> UI Framework Definition -> -> Display SAP NetWeaver BI Reports in CRM. In configuration, you can specify the report ID and the additional parameters to be used for filtering purposes. You do this in the BSP WD Workbench (transaction BSP_WD_CMPWB) for the component BSP_DLC_FS (BP_ACCOUNT_FS). 2. 1.8.2.9 Business Partners: Qualification Requirements (New for SP02) Use This release note is relevant if upgrading from SAP CRM 5.2. Using qualification requirements, you can specify the qualifications a business partner requires an employee to have to perform a certain task. Qualification requirements are used in service resource planning to find employees who are suitably qualified to perform a particular service. The Qualification Requirements assignment block is available for business partners with the Sold-To role. Effects on System Administration The Qualification Requirements assignment block is available in the configuration tool as a hidden assignment block. Effects on Customizing You make the Customizing settings required for using qualifications under Customer Relationship Management -> Workforce Deployment -> General Settings for Service Resource Planning -> Qualifications. ______________________________________________________________ SAP AG 55 SAP-System ______________________________________________________________ 1.8.2.10 Authorization Object CRM_BPROLE (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use the new authorization object CRM_BPROLE (CRM Business Partner: BP Roles) instead of the object B_BUPA_RLT (Business Partner: BP Roles) to check a user's authorization for working with roles in the CRM WebClient UI. The authorization object CRM_BPROLE and authorization check have been adapted to the CRM WebClient UI. It checks whether a user is allowed to assign a certain role and which activities are permitted. This means, for example, that if a user is not allowed to display a certain role, they are also not able enter it as a search parameter in the search, nor can they see that it is assigned when displaying the business partner concerned. Unlike B_BUPA_RLT, the authorization object CRM_BPROLE provides the following: Check for the deletion activity Only updated BP roles can be specified for the BP Role field in the authorization object 1.8.2.11 CRM WebClient UI for IS-M Processes in Interaction Center Use This release note is only relevant if upgrading from SAP CRM 5.0. As of release 7.0, certain IS-M-specific processes now offer a UI based on the CRM WebClient in the CRM Interaction Center. The following IS-M-specific processes have been affected, with the changes listed below: Business Partner Maintenance You maintain the media-specific roles Sales Customer, Retailer and Media Customer in the Roles table at the bottom of the edit page of the Sales Area Data assignment block. This table is visible only if media-specific roles are defined in Customizing. (These roles are not to be maintained in the Roles assignment block on the overview page, as they depend on the sales area). Note: You can maintain roles in this table only after you have specified attributes (for example, Billing -> Customer Pricing Procedure) for a sales area. A sales area assignment without attributes cannot be ______________________________________________________________ SAP AG 56 SAP-System ______________________________________________________________ created. Account Identification In the Account Identification screen, media -specific enhancements have been made to search for business partners. On the right hand side of the search screen, media -specific selection criteria have been created. The following search criteria have been added for advertising management: Advertising Order Advertising Billing Document Advertising Box Number Publication (this is visible only if BAdI CRM_ICWC_ISM_FILTER_BPSEARCH is implemented) The following search criteria have been added for sales and distribution: Subscription Order Subscription Billing Document Subscription Reference Document Publication The search result is displayed as usual in the lower part of the search screen. Order Lists from the IS-M Back End You use the Transaction Launcher, a new tool in this UI, to access ERP-based advertising or subscription data. Methods of BOR object types as well as BSP applications can be called this way. You can use the following methods of the BOR object type BUSISMCIC to access Media data in ERP: ShowMSDOrderList: interactive list of subscription orders ShowMAMOrderList: interactive list of advertising orders ShowBPOverview: access to BP-related data as used in the ERP Interaction Center in the application and/or navigation area. You can perform address changes with method AddressChangeWithDialog of object type BUSISM007. Order Creation with Reference to an IS-M Campaign The BSP applications ISMCAMPAIGNPICK and ISMSD_SOCREATE for creating advertising or subscription orders have been enhanced so that they can be used in the Interaction Center WebClient. Maintenance of IS-M-Specific Data for CRM Campaigns The BSP application ISMCAMPAIGNMGNT for maintaining the media-specific data for CRM marketing campaigns has been enhanced so that it can be used in the Interaction Center WebClient. ______________________________________________________________ SAP AG 57 SAP-System ______________________________________________________________ Effects on Customizing You can use the activity Define BP Roles to define media-specific roles with the role categories ISM000 (Sales Customer), ISM001 (Retailer) or ISM020 (Media Customer). If an additional filtering of accounts (for example, by publication) is required, you can implement BAdI CRM_ICWC_ISM_FILTER_BPSEARCH (in enhancement spot CRM_ICWC_ISM_FILTER_BPSEARCH). 1.8.3 CRM-MD-PRO Products 1.8.3.1 Up-Selling and Cross-Selling via Interlinkages (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now define up-selling and cross-selling products using interlinkage maintenance. This feature can be used as an alternative to the definition of cross-selling and up-selling products in the Marketing application. Maintaining up-selling and cross-selling products via interlinkage maintenance has the following features: Maintenance is product related and there is no complex integration to marketing and analytics Complex qualifying rules are possible, including the use of BRF events Rules to propagate configuration from one product to another are available You can set up up-selling from a single rate plan to a whole package while preserving relevant data (configuration, IBase etc.) Please note, the up-selling and cross-selling via interlinkages functions are not available in the CRM Web Channel Web shop. See also For more information, see Packages and Products with Dependent Components and Interlinkage Types. ______________________________________________________________ SAP AG 58 SAP-System ______________________________________________________________ 1.8.3.2 Package Group Maintenance (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can maintain groups for use in packages directly in the CRM application. Previously, you could only maintain the groups in Customizing. You use groups to structure products within packages. For example, you want to create a package of products to sell in your provider Web shop. The package should contain one rate plan, nine mobile phones, and two types of handsets. You want to display the products so that the rate plans, the mobile phones, and the handsets are displayed separately from one another. You create three separate groups called rate plan, mobile phones, and handsets. In package maintenance you assign these nodes to the package hierarchy and assign the various products accordingly under these nodes. In the provider Web shop the products are then shown in their correct groupings, so the customer has a better overview of the products involved in the package. 1.8.3.3 Interlinkage Maintenance User Interface (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The interlinkage maintenance UI has been enhanced to create an improved overview of the various maintenance processes, ensuring easier and quicker maintenance for packages and products with dependent components. The following features have been included in the new UI: Sales Component Maintenance screen Hierarchical display of package and components. You can set the sequence of the hierarchy, and the sequence defined at design time will be shown at run time. The hierarchy has three elements, regular product, group nodes, and products in a group. Grouping is displayed in the hierarchy, with the group products being available later for the customer's selection Optional flag for products. Meaning a customer can later deselect a product. - ______________________________________________________________ SAP AG 59 SAP-System ______________________________________________________________ - Validity period for products Price Level field. This is an additional criterion which can later be used for price determination. Prerequisite Product field, used to denote which product must be selected, before this product can be chosen. You can also enter a product group here meaning that any product of this group must be selected. Language-dependent explanation texts field - Dependent Components Maintenance screen Hierarchical display of package and components. You can set the sequence of the hierarchy, and his sequence will be defined at run time. The hierarchy has three elements, regular product, group nodes, and products in a group. Grouping is displayed in the hierarchy, with the group products being available later for the customer's selection Validity period for products BRF Event fields to denote BRF events which must return "true" as a condition. The BRF events can contain formulas which access the configuration result, or any other type of data such as the business partner. Process Type field, to denote which type of process, for example contract change, or order create, should be triggered when the product is selected. Language-dependent explanation texts field Value Propagation table to enable characteristic copying from superordinate to subordinate products Generation Quantity assignment block to determine the number of dependent products which are generated - - Rate Plan Combinations Maintenance screen Rate Plan ID assignment to a combined rate plan - Up-Selling Maintenance screen Target product display Validity period for products BRF Event fields to denote the complex configuration conditions, and configuration check result Process Type field, to denote which type of process, for example contract change, or order create, should be triggered when the product is selected. Value Propagation and Product Selection table to enable characteristic copying from superordinate to subordinate products Language-dependent explanation texts field - Cross-Selling Maintenance Screen Target product display ______________________________________________________________ SAP AG 60 SAP-System ______________________________________________________________ - Validity period for products BRF Event fields to denote the complex configuration conditions, and configuration check result Process Type field, to denote which type of process, for example contract change, or order create, should be triggered when the product is selected. Generation Quantity assignment block to determine the number of dependent products which are generated Language-dependent explanation texts field See also For more information, see Up-Selling and Cross-Selling via Interlinkages, Packages and Products with Dependent Components, and Intelinkage Types. 1.8.3.4 Interlinkage Types (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can create product packages using new interlinkage types. You use packages and products with dependent components to sell groups of products to customers in certain industries. For example, in the telecommunications industry, it makes sense to sell a rate plan with a mobile phone. You use these separate products to create a package and sell this as a whole to your customers. You model packages and products with dependent components using interlinkage types. The following interlinkage types are available to you for this product modeling: Sales components Dependent components Rate plan combinations The new interlinkage types supplement the previous product modeling options that are based on, among other things, the relatively complex modeling of configurable products and thereby offers enhanced functions for product determination within order and contract management. The interlinkage types are defined in the processing of the respective products and you can assign corresponding components. In this way, products such as activation charges, accessories, incentives, and so on, can be combined in an enhanced product model into a service product and in every order and contract process, automatically included in the corresponding documents. You can thereby combine flexible packages and yet devise well-defined product sets. The simplest form of this new product model is a package, which is sold as a service and can, for example, consist of a ______________________________________________________________ SAP AG 61 SAP-System ______________________________________________________________ service contract (rate plan), for which required hardware and extras are added for strategic marketing reasons. This product set is implemented by using the interlinkage type Sales Components. The package is only relevant in the process of order entry. In a provider contract, which results from a provider order created with the package, only package components are applied. As a rule, this is only the service contract (rate plan). You can influence the explosion of the package in the order entry by means of appropriate interlinkage type attributes. The interlinkage type Dependent Components facilitates the defining of product relationships by using attributes in which you can formulate conditions that you can then use to control the explosion of the products in the provider order. The product is created in the provider order only when all conditions are fulfilled. This interlinkage type is used, for example, for charges that accrue with contract changes for products in the provider order. You can also use the interlinkage type Rate Plan Combinations, in which case you are dealing with a fixed rate plan combination without further dependencies. You can offer a special price for rate plans when they are sold combined and you want to offer additional products in a package as incentives. The individual rate plans result in the provider contract with individual document items. The solution configurator processes the relationships and dependencies that are defined with these interlinkage types between the more loosely (in comparison to the product configuration) linked products in the background. It checks the conditions and releases the package components in the provider order only when the fixed conditions are fulfilled. The loose interlinkage of products in a package is chiefly significant for the distribution and further processing of the data contained inside and the information in the provider contract, which would not be possible in this way with product modeling using configurable products. Effects on Existing Data Any models you created with the product bundling function in SAP CRM 5.0 cannot simply be upgraded. Before you can continue working with them, you must remodel them appropriately using the enhanced product packages functionality now available. See also For more information, see Up-Selling and Cross-Selling via Interlinkages, Interlinkage Maintenance User Interface, and Packages and Products with Dependent Components. 1.8.3.5 Packages and Products with Dependent Components (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now create various products combinations for use in service provider business processes. The following modeling options are available to you: Sales Package ______________________________________________________________ SAP AG 62 SAP-System ______________________________________________________________ Sales components which form a sales package typically have the following characteristics: Commercially driven That is to say, rate plans are packaged with incentive products, for example a top of the range mobile phone, to drive the sales process, but can also be sold separately Dependencies between products are relatively simple For example, if you buy Rate Plan 1, you can pick the mobile phone A. Components selection, for example choose one cell phone from ten different phones, is possible, as are optional package components Components can have validity dates. That is to say, a phone is only offered for a certain period of time. - Prices of components can depend on the superordinate product . For example, Mobile Phone A has a different price when sold with Package B , as to when it is sold with Package A.. In this package type the superordinate package product has the product role sales package. The interlinkage between the superordinate package product and the package components on level one for the package hierarchy, must be the sales component interlinkage type. For example, your package product, Gold Package, is linked to the package components Rate Plan 1 and Mobile Phone 2 using the sales component interlinkage type. Combined Rate Plan Package A combined rate plan has the following characteristics: Fixed combinations That is to say, no conditions, no time-dependencies, no components selection, no choice of components Commercially driven to offer a special price for rate plans, compared to prices when sold separately Pricing can be done on top level, as a package price, or at individual rate plan level. - Results in one contract with an individual contract line item per rate plan. In this package type the superordinate package product is a combined rate plan. The interlinkage between the superordinate package product and the package components must be the rate plan combinations interlinkage type. Only rate plans may be assigned to a combined rate plan. For example, your package product Combined Rate Plan Silver, is linked to package components Rate Plan 1 and Rate Plan 2 using the rate plan combinations interlinkage type. Product with Dependent Components Dependent components which form this combination of products typically have the following characteristics: Enabling products That is to say, they are needed for the selling process. For example an activation fee is necessary for a rate plan. They are not commercially driven, for example as an extra to the main product, they are driven by technical or process requirements. Complex conditions These products are determined using complex Business Rules Framework (BRF) events and/or configuration dependencies. Generation rules are also possible for these products Charged and fulfilled with the sale of a new contract or a change of an existing contract. They - - ______________________________________________________________ SAP AG 63 SAP-System ______________________________________________________________ do not become part of the contract. The products are generated based on a simple hierarchy, but optional or alternative components are also possible. They usually appear on the lowest level of the product hierarchy. In this case you can define products with components assigned only via the interlinkage type dependent components. For example, your product Rate Plan 1, is linked to the dependent component Activation Fee 2 using the dependent components interlinkage type. See also For more information, see Interlinkage Types, Up-Selling and Cross-Selling via Interlinkages, and Interlinkage Maintenance UI. 1.8.4 CRM-MD-PCT Product Catalog 1.8.4.1 Product Catalog Staging (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Catalog staging has been introduced in the product catalog of the B2B and B2C Web shop. Catalog staging means the process of creating, validating, and activating a product catalog for productive use. According to this process, you can verify if a product catalog is correct, before it is released for general access. Prior to this release, usually one version of a catalog variant was available on the TREX server. In this context, catalog variant version is used as an equivalent for a set of TREX indexes, that means, A-index for Area, P-index for Products, and S-index for additional information. When the indexing of a catalog variant was started, existing indexes were overwritten by delta indexing or deleted by initial indexing. As of this release, a versioning of catalog variants including indexes is available. That means that indexing no longer touches existing indexes. Instead, a new version of a catalog variant creates a new set of indexes. As a result, there is no longer any downtime of the productive Web shop while the indexing process is running. Versioning allows the use of the master/slave principle on the TREX server, which makes the product catalog permanently up-to-date and available in the Web shop. For more information about the new programming interface, see release note Programming Interface SAP TREX API (New). ______________________________________________________________ SAP AG 64 SAP-System ______________________________________________________________ Catalog Variant Versioning To manage catalog variant versions and make them available in the productive Web shop, the following four version states have been introduced: The active status can be applied to exactly one version of a catalog variant The active status is to be applied to a catalog variant version to be used by standard users in the productive Web shop. The inactive status can be applied to several versions of a catalog variant A new catalog variant version is always inactive. It is used by internal users (external users have no access) to check completeness and correctness before the catalog variant is released. Therefore, the inactive variant version already looks the same as it does after it has been activated and made available for customers. This also means that current and future Internet Pricing and Configurator (IPC) information is already available. After the version has been checked, it can be activated. That means that the status of the existing active version of the same catalog variant automatically changes to obsolete. For users of the productive Web shop, activation has two effects: Users who start the product catalog after the inactive catalog variant version has been activated directly access the new catalog variant version. Users who have already started the product catalog before the inactive catalog variant version has been activated stay connected to the obsolete version. This guarantees consistent catalog browsing with no Web shop downtime. - - The obsolete status can be applied to several versions of a catalog variant Obsolete catalog variant versions are former active catalog variant versions that enable consistent catalog browsing. These catalog variant versions can be removed manually from the TREX server. Removal can also be performed automatically by a batch program after a predefined period of time. The erroneous status is only applied if errors occur during indexing - Effects on Customizing You define the product catalog indexing in Customizing at Customer Relationship Management -> Master Data -> Product Catalog -> Define Catalog Variant Indexing. You define the RFC destinations for the initial- or delta indexing of the product catalog in Customizing at Customer Relationship Management -> Master Data -> Product Catalog -> Maintain IMS Server for Catalog Indexing. In Extended Configuration Management (XCM), for productive Web shops, you can specify application configurations that always use active catalog variant versions. Additionally, you can define application configurations that allow selection of active, inactive, or obsolete versions of a catalog variant for a preview in the Web shop. Log on to Extended Configuration Management (XCM) for your Web shop at: http://<servername:port>/<b2c>or<b2b>/admin/xcm/init.do. Choose Start -> Components -> Customer -> webcatalog and create your own component - ______________________________________________________________ SAP AG 65 SAP-System ______________________________________________________________ configuration for inactive catalog variants. Select Active or Inactive in the dropdown-box of the parameter catalogstatus under Component Configuration Details. Assign the component configuration to the application configuration 1.8.4.2 Programming Interface SAP TREX API (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The programming interface SAP TREX API has been introduced to product catalog management. This new programming interface replaces the SRET API interface that was used previously. SAP TREX API supports UNICODE, which allows all characters to be displayed in the product catalog of the Web shop. SAP TREX API enables indexing to be performed with the new catalog staging, which guarantees consistent catalog browsing with no Web shop downtime. However, you can also use this programming interface to perform indexing without catalog staging. For more information about the new catalog staging process, see release note Product Catalog Staging (New). Effects on Customizing To select how you want to index the product catalog, you need to make the necessary settings in Customizing at Customer Relationship Management -> Master Data -> Product Catalog -> Define Catalog Variant Indexing. 1.8.4.3 Additional Product Category Information (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Additional product category information is now available in the product catalog of the B2B Web shop. This additional product category information is indexed to the Index Management Service (IMS) server and then displayed on the Product Details page in the product catalog. Indexing Additional Product Category Information The index consists of multiple documents that are described and characterized by attributes. One of these ______________________________________________________________ SAP AG 66 SAP-System ______________________________________________________________ documents can be a product catalog item that belongs to a certain product catalog area. The already existing attributes for a product catalog item are now enhanced by additional product category information. As of this release, the product category information consists of four additional attributes: Product Category, Product Hierarchy, Category Description, and Hierarchy Description. These attributes are designed as multi-value attributes. These four new multi-value attributes are indexed to the IMS server via an initial - or delta indexing process. During the indexing, the product category information is retrieved from master data and send as multi-value attributes to the IMS server. The Product Category and Product Hierarchy are expected to be always available. If the Category Description and the Hierarchy Description are missing in a catalog variant language, a placeholder is sent to the IMS server instead. Displaying Additional Product Category Information For every item that is displayed on the Product Details page in the product catalog, it is checked if the attribute Product Category is set. If the Product Category is set, it depends on the number of entries what is displayed on the Product Details page. If there is only one entry, the Category Description and the Hierarchy Description are shown in two separate rows. If there are more entries, the data is shown in a table with the Category Description in the first and the Hierarchy Description in the second column. If the Product Category is not set, nothing is displayed on the Product Details page. - Effects on Customizing To enable the indexing of product category information, you need to meet the following prerequisites: Activate the parameter Enable Indexing of Product Category Data in the section IMS Indexing of the corresponding product catalog type in Customizing at Customer Relationship Management -> Master Data -> Product Catalog -> Define Catalog Types. Activate the BAdI implementation Indexing New Product Category Information (COM_CATHIER_MNT_PCAT) in Customizing at Customer Relationship Management -> Master Data -> Product Catalog -> Business Add-Ins for Product Catalog. - 1.8.5 CRM-MD-PPR Partner/Product Range 1.8.5.1 Partner/Product Ranges (PPRs) (Enhanced in SP02) Use This release note is only relevant if you are upgrading from SAP CRM 5.2. ______________________________________________________________ SAP AG 67 SAP-System ______________________________________________________________ The following enhancements for PPRs are available: PPR Rules PPR rules are customer-defined function modules that fill PPR items with new or additional entries. You can define rules for products, accounts, and validity periods. Rules can be executed in two ways: automatically whenever the relevant PPR is used in an application either to carry out a PPR check or to generate product proposals manually using a report Additional attributes for validity periods and organizational data You can use additional attributes to extend PPRs with your own fields. Previously this function was only available at PPR item level for product and account assignment blocks (for example, Product Categories or Account Hierarchy Nodes). Now additional attributes can also be defined for validity period assignment blocks and for organizational data assignment blocks (Partner Functions, Transaction Types, Sales Organization, and Service Organization). Multiple descriptions in the same language For PPRs and PPR items, you can now create more than one description in the same language. - Effects on Customizing You make the necessary settings for PPRs in Customizing for Customer Relationship Management under Master Data -> Partner/Product Range. 1.8.5.2 Partner/Product Ranges (PPRs) (New) Use This release note is only relevant if upgrading from SAP CRM 5.2. A partner/product range is a combination of products and accounts that is valid for a particular time in a particular business transaction or application. You can use a partner/product range to: check whether a product is valid in a business transaction at a particular point in time For example, in a sales order, you can use PPRs to check whether a particular product can be sold to the relevant customer. This also allows you to prevent products from being sold at unsuitable times (for example, you do not want to sell Easter bunnies in winter). Other applications in which you can carry out PPR checks are service contracts, account planning and marketing project. generate time-dependent product proposals for business transactions For example, in a product catalog view, you can use PPRs to propose a suitable set of products for - ______________________________________________________________ SAP AG 68 SAP-System ______________________________________________________________ sale to particular customers during a particular period. Other application for which you can generate product proposals based on PPRs are sales orders, service contracts and top n product lists. Effects on Customizing You make the necessary settings for partner/product ranges in Customizing for Customer Relationship Management under Master Data -> Partner/Product Range. 1.8.6 CRM-MD-CON Condition Technique 1.8.6.1 Terminology in Condition Maintenance (Changed) Use As of release CRM 5.1, the terms 'condition type' and 'condition maintenance group' (or 'maintenance group'), previously used on the CRM Web Client UI will be replaced with a term that is more specific to the respective use. The following terms replace the previous term 'condition type': Use Rebate processing Pricing Free goods New Description Rebate element Price element Free goods element The superordinate term for all uses on the Web UI is: 'condition element'. The following terms replace the previous term 'condition maintenance group': Use Rebate processing Pricing Free goods New Description Rebate type Price type Free goods type The superordinate term for all uses on the Web UI is: 'condition type'. The previous terminology ('condition type' and 'condition maintenance group') will be kept in the Customizing of the affected uses. Note that 'condition type' on the Web UI indicates something different than in Customizing. ______________________________________________________________ SAP AG 69 SAP-System ______________________________________________________________ 1.9 CRM-BF 1.9.1 Worklist (New) Use Basic Functions As of SAP Customer Relationship Management (SAP CRM 5.1), a combined workflow and alert inbox is available in the Worklist application. This means that these two functions are now integrated into the user interface for CRM. You can navigate from the workflow and alert list to the detailed view for alerts and workflow tasks, or to alert personalization. Effects on Customizing You can find the Customizing activities for the worklist in Customizing for Customer Relationship Management by choosing Basic Functions --> Worklist. 1.9.2 Authorization Check at Field Level (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use this function to permit certain authorization groups to change fields in a business transaction such as Sales- or Service Order. You may want to allow only those employees with special authorization to, for example, subsequently change quantities after the sales order has been delivered. You can also use the authorization check for business transaction components, and so make your authorization check even more precise. The following business transaction components are supported: Order item (ORDERADM_I) For example, you can permit certain authorization groups to delete or create order items, for example. Partner (PARTNER) - ______________________________________________________________ SAP AG 70 SAP-System ______________________________________________________________ For expample, you can allow only a specific authorization group to change the appropriate fields of the object Partner that relate exclusively to the partner function Ship-To Party (logical key: 00000002). Transaction history (DOC_FLOW) For example, you can also control actions for campaigns and trade promotions using the object Transaction History (DOC_FLOW), and define whether a certain authorization group can delete or create campaigns or trade promotions if you have activated the function Multiple Campaigns or Trade Promotions. Effects on Customizing You have created an authorization that applies to authorization object CRM_FLDCHK, assigned this authorization to an authorization profile and then allocated this profile to the appropriate user. When you create the authorization that applies to the authorization object CRM_FLDCHK, you can only specify one value (an integer) for the field Authorization Level. Intervals (1-12, for example) or multiple values (such as 5,7,9) cannot be processed in the authorization check. You have defined authorization groups and allocated fields to them in Customizing. An authorization group is a type of field group and consists of a collection of fields. You make the entries for this in the Customizing for Customer Relationship Management under Define Authorization Group. For performance reasons, you should determine the rules for the authorization check very carefully. In the IMG activity Maintain Authorizations at Field Level, you should only use the value Asterisk ( * [=all transaction types]) in the column Transaction Type when you really want all transaction types to be analyzed in the authorization check for this authorization rule. You have granted an authorization level for each authorization group in connection with the key fields Transaction Type, Item Category and Delivery Status. These entries are manually made in the Customizing for Customer Relationship Management under Maintain Authorizations at Field Level. You fill the control table CRMM_AUTH_FIELD with these entries. - - Note: The control table CRMM_AUTH_FIELD is created as a master data table and therefore cannot be transported. You should maintain this control table in your productive system. 1.9.3 New, Changed and Removed IMG Activities in SAP CRM 5.1 and SAP CRM 5.2 Use ______________________________________________________________ SAP AG 71 SAP-System ______________________________________________________________ This release note is only relevant if upgrading from SAP CRM 5.0. Layout of User Interface (People Centric CRM) Removed IMG activities: Customer Relationship Management -> Layout of User Interface (People-Centric CRM) All activities under this node have been removed. Basic Functions New IMG activities: o Customer Relationship Management -> Basic Functions -> Worklist -> Define Alert Inbox and Workflow Inbox -> Define Task-Specific Navigation o Customer Relationship Management -> Basic Functions -> Worklist -> Define Alert Inbox and Workflow Inbox -> Define Alert-Specific Navigation o Customer Relationship Management -> Basic Functions -> Pricing -> Pricing in the Business Transaction -> Define Mapping for Condition Types from Application BBP to Application CRM Master Data - Organizational Management New IMG node: Customer Relationship Management -> Master Data -> Organizational Management -> Assignment of Organizational Units from SAP ECC All the activities under this node are new. They have been isolated from the activities Organizational Model -> Create Organizational Model and -> Change Organizational Model so that you can maintain only the mapping of the organizational units between SAP ECC and SAP CRM. The organizational model itself can now be maintained in the CRM Web UI. If you have already made settings for a former release, you do not need to make any further changes. Master Data - Product New IMG nodes: o Customer Relationship Management -> Master Data -> Products -> Settings for Configurable Products o The activity Define Settings for Product Models is new. Customer Relationship Management -> Master Data -> Products -> Settings for Packages The activity Assign Product Roles to Categories is new. Removed IMG activities: o Customer Relationship Management -> Master Data -> Products -> Settings for Product Type -> Define Product Template for Configurable Products o Customer Relationship Management -> Master Data -> Products -> Objects -> Specify Display ______________________________________________________________ SAP AG 72 SAP-System ______________________________________________________________ Option for Object Structure o Customer Relationship Management -> Master Data -> Products -> Objects -> Define Available Catalogs for Object Structure o Customer Relationship Management -> Master Data -> Products -> Objects -> BAdI: Include External Catalogs for Object Structure o Customer Relationship Management -> Master Data -> Products -> Objects -> Activate Map Visualization of Location Master Data - Partner/Product Range Removed IMG activity: o Customer Relationship Management -> Master Data -> Partner/Product Range -> Assign PPR Types to PPR Listings Master Data - Business Partner New IMG activity: o Customer Relationship Management -> Master Data -> Business Partner -> Basic Settings -> Define Profiles. Removed IMG activity: o Customer Relationship Management -> Master Data -> Business Partner -> Basic Settings -> Assign Templates for Content Management Folder to BP Roles Master Data - Product Catalog New IMG activities: o Customer Relationship Management -> Master Data -> Product Catalog -> Define Catalog Variant Indexing o Customer Relationship Management -> Master Data -> Product Catalog -> Maintain IMS Server for Catalog Indexing o Customer Relationship Management -> Master Data -> Product Catalog -> Business Add-Ins for Product Catalog -> Implementation: Indexing New Product Category Information o Customer Relationship Management -> Master Data -> Product Catalog -> Define Templates for Folders Account Planning New IMG activity: Customer Relationship Management -> Account Planning -> Product Assignments -> Define Product Planning Basis Removed IMG activity: Customer Relationship Management -> Account Planning -> General Settings -> Define Field Selection Transactions ______________________________________________________________ SAP AG 73 SAP-System ______________________________________________________________ New IMG activity: o Customer Relationship Management -> Transactions -> Additional Settings -> Assign Marketing Usage Types to Transaction Types Moved IMG activity: o Customer Relationship Management -> Transactions -> Assign Amount Allocation Profile to Transaction Type and Item Category can now be found under Transactions -> Additional Settings. Renamed node and activities: o The IMG node Customer Relationship Management -> Transactions -> Settings for Complaints -> Integration -> Business Add-Ins for Document Referencing is renamed to Transaction Referencing o The IMG activities under the node Customer Relationship Management -> Transactions -> Settings for Complaints -> Integration -> Transaction Referencing are renamed: Business Add-In: Create Complaints with Reference to External Document is renamed to BAdI: Create Complaint with Reference to External Transaction Define Object Types for Document Reference is renamed to Define Object Types for Transaction Reference Assign Business Object Types to Transaction Types is renamed to Assign Business Object Types to Transaction Types Business Add-In: Create Document Flow for Subsequent Document Reference is renamed to BAdI: Create Transaction History for Subsequent Transaction Reference Define Business Object Type for Subsequent Document Reference is renamed to Define Business Object Type for Subsequent Transaction Reference Removed sections (for functions not supported in this release): Customer Relationship Management -> Transactions -> Settings for Service Processes -> Settings for Service Resource Planning IMG activity moved: Customer Relationship Management -> Transactions -> Settings for Product Service Letters -> Define Object Reference Profile can now be found under Transactions -> Basic Settings. Grantor Program Management New IMG activities: Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Program Management -> General Settings -> Define Program Profile Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Program Management -> General Settings -> Define Availability Control Profile Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Program Management -> General Settings -> Define Tolerance Profile ______________________________________________________________ SAP AG 74 SAP-System ______________________________________________________________ Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Change Process Management -> Define Input Field Control Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Change Process Management -> Define Change Processes Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Change Process Management -> Customer Enhancements for Change Process Management Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Change Process Management -> BAdI: Customer Enhancements for Web Requests Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Basic Functions for Grantor Processing Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Financial Transactions -> Define Financial Execution Type Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Financial Transactions -> Pricing -> Define Value Type Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Financial Transactions -> Define Billing Plan Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Actions in Grantor Processing Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Web Requests for Grantor Management Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Business Add-Ins -> BAdI: Customer Enhancements for Grantor Agreement Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Business Add-Ins -> BAdI: Customer Enhancements for Grantor Application Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Business Add-Ins -> BAdI: Customer Enhancements for Grantor Claim Changed IMG activities Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Transactions in Grantor Processing Removed IMG activities Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Program Management -> Content Management Case Management New IMG activities: ______________________________________________________________ SAP AG 75 SAP-System ______________________________________________________________ Customer Relationship Management -> Case Management -> Process Partners -> BAdI: Reassign Business Partners in Linked Objects Customer Relationship Management -> Case Management -> Basic Settings -> Define Search Scenario Customer Relationship Management -> Case Management -> Basic Settings -> Define Case Closing Profile Customer Relationship Management -> Case Management -> Basic Settings -> BAdI: Define Additional Tasks for Case Closing Profile Customer Relationship Management -> Case Management -> Extended Customizing -> Case Archiving -> CRM Data Archiving Process Customer Relationship Management -> Case Management -> Extended Customizing -> Case Archiving -> Display Archived Case Data Customer Relationship Management -> Case Management -> Extended Customizing -> Case Archiving -> BAdIs for Case Archiving -> BAdI: Define Checks Prior to Case Archiving Customer Relationship Management -> Case Management -> Extended Customizing -> Case Archiving -> BAdIs for Case Archiving -> BAdI: Archive Case Table Entries Customer Relationship Management -> Case Management -> Extended Customizing -> Case Archiving -> BAdIs for Case Archiving -> BAdI: Delete Case Table Entries from the Database Customer Relationship Management -> Case Management -> Extended Customizing -> Special Settings -> BAdI: BAPIs for Case Parameters -> BAdI: Change BAPI Parameters Customer Relationship Management -> Case Management -> Extended Customizing -> Special Settings -> BAdI: BAPIs for Case Parameters -> BAdI: BAPI Change Case - Change Import Parameters Customer Relationship Management -> Case Management -> Extended Customizing -> Special Settings -> BAdI: BAPIs for Case Parameters -> BAdI: BAPI Create Case - Change Import Parameters Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> Case Import and Export with XI Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> Monitor XI Case Exports Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> Manually Export Cases Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Export Case XI Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Import Case XI Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Map XI Case Export Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Map XI Case Import Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Export Case During Save ______________________________________________________________ SAP AG 76 SAP-System ______________________________________________________________ Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Export Case at Business Partner Update Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> BAdI: Export Case at Postal Code Update Customer Relationship Management -> Case Management -> Extended Customizing -> Case Import and Export with XI -> BAdI: Perform Customer Enhancements -> Case Management Customer Enhancements in XI Customer Relationship Management -> Case Management -> Extended Customizing -> ACE Implementation for Case Management (Note: This activity describes how the delivered sample ACE implementation has been configured in case you want to create your own ACE implementation.) Removed IMG activities The following BAdIs were removed under Customer Relationship Management -> Case Management -> Extended Customizing -> Special Settings -> Define Processes -> Business Add-Ins (BAdIs): Business Add-In: Data Transfer When Creating a Case Business Add-In: Filling Customer-Specific Dropdown Lists Business Add-In: Copying Cases BAdI: Attributes for Links in Case Record BAdI: Process Control in Case Management BAdI: Process Control for Case Notes BAdI: Process Control of Derived Case Management Applications BAdI: Enhancement for BSP Case Framework Customer Relationship Management -> Case Management -> Extended Customizing -> Special Settings -> Create Profiles -> Notes About the Function Profile and Terminology Profile All of the informational nodes were removed under Customer Relationship Management -> Case Management -> Integration in the User Interface (People-Centric UI). Customer Relationship Management -> Case Management -> Extended Customizing -> Special Settings -> Create Profiles - > Assign Profile for Document Templates to a Case Type Billing New IMG activity: Customer Relationship Management -> Billing -> Intercompany Billing -> Determine Sales Area Data for Determination of Invoice Currency New IMG section: Billing -> Integration -> Transfer of Billing Documents to Foreign Trade -> Transfer to SAP GTS 3.0 and Later Releases -> Transfer of BiIling Data for Intrastat Declarations. Usage-Based Billing This section has been removed since usage-based billing is not supported in this release. ______________________________________________________________ SAP AG 77 SAP-System ______________________________________________________________ Removed IMG activities: Customer Relationship Management -> E-Commerce -> Basic Settings for E-Commerce -> Business Add-Ins (BAdIs) for E-Selling -> BAdI: Change Target System for Calling Up Availability Check in ERP Interaction Center WinClient, and Interaction Center WebClient 2005 These sections have been removed. Prior to SAP CRM 5.1, Interaction Center WebClient 2005 section was Interaction Center WebClient. Interaction Center WebClient This section is new. As of Service Pack 02 a new configuration activity was added under Interaction Center WebClient -> Basic Functions -> Communication Channels -> Configure E-Mail for SAPconnect. Marketing Planning and Campaign Management Changed IMG activities: Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Key Figure Planning -> Version Management -> Define Versions Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Key Figure Planning -> Version Management -> Define Version for System Status Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Key Figure Planning -> Version Management -> Define Version for User Status Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> System Landscape -> Activate SAP NetWeaver BI Update Removed IMG activities: Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Key Figure Planning -> Define Parameters for BW Analyses Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Key Figure Planning -> Assign Success Key Figures to Campaign Type and Objective Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> General Settings -> Define Field Assignment for Microsoft Project Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> General Settings -> Define User Settings Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Search Tables Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management ______________________________________________________________ SAP AG 78 SAP-System ______________________________________________________________ -> Marketing Calendar -> Define Search Criteria Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Assign Search Criteria Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Define Field Settings for Table View Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Marketing Calendar -> Business Add-Ins -> Extend Standard Functions in Query for Calendar Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> User Interface Settings (all activities) Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Personalized Mail -> Maintain Print Profile Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Personalized Mail -> Define Status Profile for User Status Customer Relationship Management -> Marketing -> Marketing Planning and Campaign Management -> Additional Fields and Business Add-Ins (BAdIs) for Marketing Planning -> Define Additional Fields: Set Types IPM Solution Management Removed IMG activities: SAP Implementation Guide -> Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights and Royalties Dimensions -> Generate People Centric UI for Rights and Royalties Dimensions Telecommunications New IMG node: o Customer Relationship Management -> Industry-Specific Solutions -> Telecommunications -> Dispute Management Hi-Tech Moved The entire node under Customer Relationship Management -> Channel Management -> Channel Sales -> Industry-Specific Channel Sales -> Channel Sales has been moved and renamed to Customer Relationship Management -> Industry-Specific Solutions -> High Tech. Transactions being used in common with Pharma have been copied to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry. Pharma New: o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ ______________________________________________________________ SAP AG 79 SAP-System ______________________________________________________________ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Incompleteness Procedure o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Incompleteness Procedure -> Define Incompleteness Procedure o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Evaluation and Calculation Profiles -> Define Profiles o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Evaluation and Calculation Profiles -> Assign Attributes to Profiles o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs Evaluation and Calculation Profiles -> Maintain Profile Attribute Values o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Authorizations o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Authorizations -> Define Authorization Group o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance -> Define Condition Generation o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance -> Assign Condition Maintenance Group o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance -> Conflict Resolution o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance -> Activate Staging and History o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance -> Define Condition History Table o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Condition Maintenance -> Activate History for Usage and Condition Type ______________________________________________________________ SAP AG 80 SAP-System ______________________________________________________________ o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Determination of Incentive Programs -> Determine Incentive Program in Contracts o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Enhancements for Eligibility Rules o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Enhancements for Eligibility Rules -> Business Add-In: Implement Data Supply o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Enhancements for Eligibility Rules -> Enhance Rule Attribute Structures o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Enhancements -> Business Add-In: Authorization Check o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Product Assignments -> Assign Product Hierarchy o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargebacks and Sales Tracking -> Entitlement Document -> Maintain Relevancy for Claim Document Creation o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargebacks and Sales Tracking -> Reconciliation -> Assign Outbound EDI - NWDA Codes New Textual Nodes (no activity, only reference to the actual activity): o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Text Management - Define Text Objects and Text Types o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs ->Text Management -> Define Text Determination Procedure o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Incentive Programs -> Status Profile -> Change User Status Profile o Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Notification Manager -> Maintain Condition Type for Notification Renamed: o Industry-Specific Solutions -> Pharmaceuticals -> Master Data is renamed to Customer ______________________________________________________________ SAP AG 81 SAP-System ______________________________________________________________ Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry-> Field Sales Moved: o Activate Pharma-Specific Applications has been moved from under Industry-Specific Solutions -> Pharmaceuticals -> Master Data to Customer Relationship Management -> Life Sciences/ Pharmaceuticals Industry-> o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Channel Sales for Pharma Industry All nodes under Channel Sales for Pharma Industry that are still being used have been moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences o Customer Relationship Management -> Channel Management -> Channel Sales -> Basic Functions -> Configure Business Rules has been moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Configure Business Rules Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Configure Business Rules -> Configure Schema Access Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Configure Business Rules -> Configure Prerequisites for Process Step Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Configure Business Rules -> Validation Classes/-Bits Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Configure Business Rules ->Configure Reconciliation-/Duplicate Check Rules -> Maintain Field Groups Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Configure Business Rules ->Configure Reconciliation-/Duplicate Check Rules -> Assign Field Groups to System Steps o Activities under the Customer Relationship Management->Channel Management-> Channel Sales - > Industry-Specific Channel Sales ->Chargeback have been moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Channel Sales for Pharma Industry -> Settings for Claim Contract Claim Contracts has been renamed and all activities under it, moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals ______________________________________________________________ SAP AG 82 SAP-System ______________________________________________________________ Industry -> Contract Management for Life Sciences -> Contracts -> Maintain Relevancies for Contracts -> Maintain Transaction Type Mapping Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts -> Maintain Relevancies for Contracts -> Maintain Partner Function Mapping Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts -> Maintain Relevancies for Contracts -> Maintain Condition Type Mapping Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts -> Maintain Relevancies for Contracts -> Maintain Date Type Mapping Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts -> Maintain Relevancies for Contracts -> Maintain Status Mapping Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Contracts -> Enhancements -> BAdI: CMS Extract Preparation o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks -> Business Logic Enhancements is moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Enhancements for Business Logic Flow o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargeback -> Map Additional Transaction Types is moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Map Additional Transaction Types o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargeback -> Claim Processing -> Unit of Measurement Selection Method is renamed and moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Chargeback and Sales Tracking -> Selection Method -> Selection Method for Unit of Measure o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargeback -> Claim Processing -> Contract Selection Method is moved to Customer Relationship Management -> Industry-Specific Solutions -> Life Sciences/ Pharmaceuticals Industry -> Contract Management for Life Sciences -> Selection Method -> Contract Selection Method Removed: o Customer Relationship Management->Channel Management-> Industry-Specific Channel Sales ->Contracts and Chargeback for the Pharmaceutical Industry has been removed. o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks ->Duplicate Check -> Maintain Fieldgroups ______________________________________________________________ SAP AG 83 SAP-System ______________________________________________________________ Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks -> Duplicate Check -> Maintain Duplicate Check Rules o Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks ->Enhancement -> User Interface Enhancements -> Configure Selection Screens for Chargeback Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks ->Enhancement -> User Interface Enhancements -> Maintain screen labels for Chargeback Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks ->Enhancement -> User Interface Enhancements -> Configure Header grid display for Chargeback Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks ->Enhancement -> User Interface Enhancements -> Configure Claim Grid Display for Chargeback Customer Relationship Management -> Channel Management -> Channel Sales - > Industry-Specific Channel Sales -> Chargebacks ->Enhancement -> User Interface Enhancements -> Toolbar Enhancements Renamed nodes and activities: o The IMG node Customer Relationship Management -> E-Commerce is renamed to Web Channel o The IMG node Customer Relationship Management -> E-Commerce -> E-Selling is renamed to Customer Relationship Management -> Web Channel -> E-Commerce o The IMG node Customer Relationship Management -> Channel Management is renamed to Customer Relationship Management -> Partner Channel Management CRM Web Channel New IMG activities: o Customer Relationship Management -> Web Channel -> Basic Settings -> Define Authorizations o Customer Relationship Management -> Web Channel -> Basic Settings -> Business Add-Ins (BAdIs) for Web Channel -> BAdI: Additional Search Filter Rebate Processing New IMG Activities: o Customer Relationship Management -> Rebate Processing -> Configure Application o Customer Relationship Management -> Rebate Processing -> Set Up Rebate Determination -> Assign Maintenance Group for Mass Processing o Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Settlement Profiles -> Define Filters for Cancellation Requirements ______________________________________________________________ SAP AG 84 SAP-System ______________________________________________________________ o Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Consumable Rebate Profiles -> Define Filters for Consumable Value Calculation o Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Consumable Rebate Profiles -> Define Consumable Rebate Profile o Customer Relationship Management -> Rebate Processing -> Reason Codes -> Define Reason Codes o Customer Relationship Management -> Rebate Processing -> Reason Codes -> Assign Reason Codes to Process Types o Customer Relationship Management -> Rebate Processing -> System Enhancements -> Business Add-Ins -> BAdI: Cancellation Requirements o Customer Relationship Management -> Rebate Processing -> System Enhancements -> Business Add-Ins -> BAdI: Calculation of Consumable Rebate Value Changed IMG Activities: o Customer Relationship Management -> Rebate Processing -> Set Up Rebate Determination -> Create Condition Types o Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Settlement Profiles -> Define Settlement Document Type o Customer Relationship Management -> Rebate Processing -> Rebate Profiles -> Define Rebate Profile Renamed IMG Activities: o From: Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Base Calculation To: Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Filters for Base Calculation o From: Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Scale Base Calculation To: Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Filters for Scale Base Calculation o From: Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Payment Value Calculation To: Customer Relationship Management -> Rebate Processing -> Calculation Profiles -> Define Filters for Payment Value Calculation Entitlement Management New IMG Activities: o Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Intercompany Related Customizing Setup o Customer Relationship Management -> Entitlement Management -> Basic Functions -> Inbound/ Outbound Processing -> Inbound Number Range Object Maintenance ______________________________________________________________ SAP AG 85 SAP-System ______________________________________________________________ o Customer Relationship Management -> Entitlement Management -> Basic Functions -> Inbound/ Outbound Processing -> Outbound Number Range Object Maintenance o Customer Relationship Management -> Entitlement Management -> System Enhancements -> Assign Logical Events to Business Workflow Events Renamed IMG Activites: o From : Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Assign Pricing Procedure for Automatic Deposit Determination To: Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Setup Application Parameters o From: Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Define Document Types To: Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Program Types -> Define Entitlement-Specific Transaction Categories Removed IMG Activities: o Customer Relationship Management -> Entitlement Management -> System Enhancements -> Maintain Appearance of Selection and Results Screens o Customer Relationship Management -> Entitlement Management -> System Enhancements -> Business Add-Ins -> BAdI: User Interface Toolbar Enhancements 1.9.4 Worklist (Enhanced for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can now simultaneously forward several items from the workflow inbox of your worklist. In the workflow inbox, you select the workflow tasks in question and click Forward. In the dialog box that appears, you can search for the relevant employee or partner contact and click Forward again. The forwarded tasks appear in the worklist of the recipient, for whom they are simultaneously reserved. The workflow tasks are therefore removed from your worklist. ______________________________________________________________ SAP AG 86 SAP-System ______________________________________________________________ Effects on Customizing For more information, see Customizing for Customer Relationship Management under Worklist -> Define Alert Inbox and Workflow Inbox -> Define Forwarding and Substitution. 1.9.5 Worklist (Enhanced) Use This release note is only relevant if you are upgrading from SAP CRM 5.2. The following functions are now available in the worklist: Business object inbox The business object inbox provides a single point of entry for calling up the business objects that you have to process. The inbox offers a comprehensive search for business objects and a corresponding result list. You can access the business objects from the result list. In the standard system, the business object inbox is enabled for business transactions. However, you can configure the inbox to support other types of business objects as well, such as cases or fax messages. Maintenance of substitutes in workflow inbox You can now define substitutes to process your workflow tasks in your absence. Depending on your business role, you can assign employees of your company, partner contact persons or both. Triggering of workflow steps for multiple workflow tasks You can simultaneously trigger workflow steps, such as confirm or reject, from the workflow task result list for multiple workflow tasks. - - Effects on Customizing You have configured the buiness object inbox in Customizing for Customer Relationship Management, by choosing Basic Functions -> Worklist -> Define Business Object Inbox. For the substitute function in the workflow inbox, you have defined the forwarding of tasks and alerts. You do this in Customizing for Customer Relationship Management, by choosing Basic Functions -> Worklist -> Define Alert Inbox and Workflow Inbox -> Define Forwarding and Substitution. ______________________________________________________________ SAP AG 87 SAP-System ______________________________________________________________ 1.9.6 Worklist (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now use the worklist as a central point of access for your alert, workflow and business object inboxes. Each inbox offers various functions and navigation options: Alert inbox The result list offers an overview over the priorities and due dates of the various alerts. You can execute follow-up activities from the alert list or from the details page. You can personalize the delivery of alerts, define substitutes and cancel predefined subscriptions to alert categories. You can reserve, complete, forward, or reject an alert. Workflow inbox The result list offers an overview over the priorities and due dates of the various workflow tasks. You can execute, reserve, forward, or confirm a workflow task. You can trigger workflow steps, such as confirm or reject, from the workflow task result list for multiple workflow tasks. You can add an attachment to a workflow task. For workflow tasks that require a decision from you, various decision options are available that influence the rest of the business process. You can define substitutes to process your workflow tasks in your absence. - Business object inbox The business object inbox provides a single point of entry for calling up the business objects that you have to process. The inbox offers a comprehensive search for business objects and a corresponding result list. You can access the business objects from the result list. In the standard system, the business object inbox is enabled for business transactions. However, you can configure the inbox to support other types of business objects as well, such as cases or fax messages. Effects on Customizing You have to configure the alert-, workflow-, and business object inboxes in Customizing for Customer Relationship Management, by choosing Basic Functions -> Worklist. ______________________________________________________________ SAP AG 88 SAP-System ______________________________________________________________ 1.9.7 CRM-BF-PD Partner Processing 1.9.7.1 Partner Processing: Alternative Partner Proposal (New for SP02) Use This release note is relevant if upgrading from SAP CRM 5.2. The Propose Alternatives function is available in the Parties Involved assignment block and allows you to trigger partner determination within business transactions to redetermine and reassign the relevant parties. It enables you to do the following: Change previously automatically determined partners quickly and easily within the application itself. This means you no longer have to search manually for partners you want to replace. Redetermine partners in saved documents. Trigger partner determination for empty partner functions already saved in a document. 1.9.8 CRM-BF-COU 1.9.8.1 Short text. Counter Customizing for Counters and Readings (Changed in SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. All Customizing activities for counters and readings are grouped into the sub-section Counters and Readings, which you can find in the following sections of the Implementation Guide (IMG) for Customer Relationship Management: Master Data (replacing the section Counters) Usage-Based Service Contract Processing The settings for counters and readings are relevant both for general use and for usage-based billing of service contracts. ______________________________________________________________ SAP AG 89 SAP-System ______________________________________________________________ 1.9.8.2 Language-Dependent Counter Descriptions (New in SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. You can create language-dependent descriptions for counters in addition to the previously supported language-independent description for a counter. You create the language-independent description in the Description field in the counter details. You create language-dependent descriptions in the Descriptions assignment block, which is available on the Counters page. If you create a language-dependent description in your current logon language, this replaces (for display purposes) the description in the Description field in the counter details. The Counter Description search criterion searches for both language-dependent and language-independent descriptions. If a language-dependent description exists in your logon language, this is displayed in the search results and in the Description field in the counter details. Otherwise, the language-independent description is displayed. 1.9.9 CRM-BF-CFG Product Configuration 1.9.9.1 Display Options for Characteristics and Characteristic Values (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can decide if the long text (more than 30 characters) should be available on the user interface of the product configuration for characteristics and characteristic values. In some cases, the characteristic could not be described in a sufficiently meaningful manner with the previous character length of 30 characters ______________________________________________________________ SAP AG 90 SAP-System ______________________________________________________________ for the characteristic description (short text). In addition, it is difficult to formulate a question as user help with this character length. Until now the long texts, that is, the detailed descriptions of the characteristics or characteristic values, could only be displayed on request and only one long text could be displayed at any one time. Therefore the previous display for long texts was not suitable for the interactive product configuration. By setting appropriate parameters in Extended Configuration Management (XCM) you can configure the application in such a way that instead of the short text for characteristics and characteristic values, the long text is displayed as the description. The long text is thereby displayed on the user interface in the same way as short texts, that is, the long texts behave like the short texts in the way they are displayed on the user interface. Various display options are offered, for example, you can either display ID and long text or short text and long text. In addition, you can restrict the display length of the long text. The length is restricted to 80 characters by default. If the characteristic or characteristic value has no long text, the corresponding short text is displayed. Effects on Customizing You can make the settings for this function in XCM by using the parameters characteristics.descriptiontype and values.descriptiontype. The following parameter values are available: Value Description ShortDescription The short text of the characteristic or characteristic value, at most 30 characters long, is displayed on the user interface. This is the standard display. LongDescription The first line of the long text is displayed instead of the short text. If the characteristic values are displayed collapsed, that is, in a dropdown listbox, the short text is displayed. ShortAndLongDescription The short text and the long text of the characteristic are displayed in different lines. The short text and long text are displayed in two different columns for characteristic values. IDAndShortDescription The ID and the short text are displayed in one line. IDAndLongDescription The ID and the long text of the characteristic or characteristic value are displayed in different lines or columns. IDAndShortAndLongDescription The ID and the short text are displayed in one line. The long text of the characteristic or characteristic value is displayed in another line or column. ID The ID of the characteristic or characteristic value is displayed instead of the short text. You can restrict the display of the long text by using the parameters values.maxdescriptionlength and characteristics.maxdescriptionlength. The standard value for these parameters is 80 characters. ______________________________________________________________ SAP AG 91 SAP-System ______________________________________________________________ 1.9.9.2 Display of Messages when Loading a New Knowledge Base (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. When loading a saved product configuration, various messages can arise if a new knowledge base is used. These messages give information on which parts of the saved configuration could not be loaded or have errors. You can display these messages, which give information on changes in the knowledge base. These messages are displayed on the user interface for the configuration comparison if problems arise from a saved product configuration being applied to a new knowledge base. The messages inform the user of the following: Characteristics and instances that cannot be loaded Instances that have an unknown type Values that have the wrong format You can adjust the way these messages are displayed on the user interface by setting appropriate parameters in Extended Configuration Management (XCM). Effects on Customizing You can activate or deactivate this function by using the XCM parameter messagearea.loadingmessages.show. With the value T, the system searches for messages. This function is deactivated if the value used is F, and the display of messages is completely switched off. You can control the display type by using the XCM parameter behavior.fordwardtocomparison. The following options are offered for this: Value Description F If messages are created when a saved configuration is loaded with a new knowledge base, these messages do not automatically appear. You are, however, notified of them on the product configuration's user interface and you can display these messages by means of a corresponding pushbutton. onmessages If messages are created when a saved configuration is ______________________________________________________________ SAP AG 92 SAP-System ______________________________________________________________ loaded with a new knowledge base, these messages are displayed directly on the user interface for the configuration comparison. This is the standard setting. always The user interface for the configuration comparison always opens with this value, even when no messages exist. 1.9.9.3 Comparison of Product Configurations (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can compare the states of different product configurations with each other and thereby make the characteristic values of two product configuration states available for comparison. In this way you help your customers to decide which product configuration best fits their requirements and is therefore more suitable. The comparison of product configurations can be carried out by using various pushbuttons on the user interface of the product configuration. The following options are available: Comparison of the current product configuration with an initial product configuration When processing a new sales order during the product configuration, an initial product configuration is automatically stored as a snapshot when the user interface is called. You can compare this snapshot with a current product configuration at a later point. This comparison is possible as long as you have not yet stored a snapshot during the session. The product configuration is saved to the database only when you have created the new sales order. Comparison of the current product configuration with a product configuration already saved on the database When you want to re-process a sales order with which a product configuration was saved, because your customer wants a different product configuration, you can compare the previously saved product configuration with that which the customer now wants. This comparison serves as decision support for the choice of the new product configuration. Comparison of the current product configuration with a snapshot, that is, a product configuration that you have stored in a session before the call for comparison. The snapshot is not saved on the database, but its data is temporarily saved during the session. When you leave the session, the snapshot is no longer available. - - The result of the comparison is displayed on a dedicated page. A table compares the corresponding characteristic values for the saved or initial product configuration with the characteristic values for the current product configuration. In addition, a table column is available for notes on the comparison of the product configurations. If the values differ, an explanation for the cause is specified. If a comparison is displayed with a snapshot then the user has the option to go back to this snapshot by use of a pushbutton. ______________________________________________________________ SAP AG 93 SAP-System ______________________________________________________________ Effects on Customizing You can activate or deactivate the function "Comparison of Product Configurations" by using the XCM parameter behavior.enablecomparison . If you have set the value "T" for this parameter, you can compare the current product configuration with the snapshot as well as with a saved product configuration. You can determine if a snapshot of a certain product configuration can be stored by the user during the product configuration with the XCM parameter behavior.enablesnapshot. The value "T" should also be set for the parameter behavior.enablecomparison so that the differences in comparison to the snapshot can be displayed. 1.9.9.4 Performing Standard Configuration in the Background (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can set up the product configuration so that the default configuration is directly applied to the sales order for a configurable product. In the case of multilevel product configuration, the corresponding subitems are also immediately created in the sales order. In order to apply the default configuration, you no longer need to call the user interface of the product configuration, that is, the default configuration is performed in the background. The default configuration is a product configuration with which characteristic values are already set as default values for the respective characteristic. If you want to define another product configuration for the corresponding configurable product, you can switch to the user interface of the product configuration and re-perform a configuration for this product. The previous system response was to display a message in the application log of the sales order to say that you had to copy the default configuration to the sales order using the product configuration . You also had to switch to the user interface of the product configuration in the case of existing default values. Only there could you apply the default configuration to the sales order, by means of a pushbutton. You can avoid this additional navigation step with the new function, which makes the application easier to handle and thus more user-friendly. Effects on Customizing You can determine the desired system response in the definition of the item category in the field Configuration Background. You perform the settings in SAP CRM Customizing by choosing Customer Relationship Management -> Transactions -> Basic Settings -> Define Item Categories. If you perform the product configuration in the background and want to apply the default configuration, choose the value "Perform Standard Configuration in Background" in the Configuration in Background field. ______________________________________________________________ SAP AG 94 SAP-System ______________________________________________________________ 1.9.9.5 Product Config: Using Sales Order Fields as Object Characteristics (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The Configuration Engine requires relevant information from the sales order to edit the product configuration. You can use object characteristics for this, in order to copy values from the sales order to the product configuration or to transfer values from the configuration to the sales order. In contrast to the ordinary characteristics of a configurable product, an object characteristic always relates to a table field. When the product configuration is called this information, that is, the values of context parameters (table names and field names), is sent from the sales order to the Configuration Engine, and corresponding values are returned from the Configuration Engine to the sales order. The context parameter values are thus transferred to the object characteristic defined for the respective field and then used as characteristic values in the product configuration. Fields in SAP CRM must be mapped to fields in SAP ECC for this data exchange. Additional object characteristics - Enhancement of CRM context Further sales order fields, which you can use as object characteristics, are available in the product configuration. The enhancement of the context parameter is, for example, necessary for the editing of complex products in provider contracts. The Configuration Engine data, which is also essential for the product configuration of more complex products, is thus retrieved from the sales order for processing. You can, for example, transfer additional necessary input parameters to the Configuration Engine. The following fields are available in the enhanced CRM context: *) Field that can also be described: CRM table ORDERADM_H ORDERADM_I PRODUCT_I PRICING Field name in SAP CRM CHANGED_AT CHANGED_AT PROD_HIERARCHY CURRENCY REF_CURRENCY EXCHG_DATE EXCHG_RATE PRICE_GRP PRICE_LIST CUST_GROUP TAX_DEST_CITY REGION INDUSTRY CUST_GROUP1 CUST_GROUP2 CUST_GROUP3 Field name in SAP ECC VBAK-AEDAT VBAP-AEDAT VBAP-PRODH VBAK-WAERK KOMK-HWAER VBKD-KURSK_DAT VBKD-KURSK VBKD-KONDA VBKD-PLTYP VBKD-KDGRP VBAK-STCEG_L VBKD-J_1AREGIO KNA1-BRSCH VBAK-KVGR1 VBAK-KVGR2 VBAK-KVGR3 SALES ______________________________________________________________ SAP AG 95 SAP-System ______________________________________________________________ CUST_GROUP4 CUST_GROUP5 *) REQ_DLV_DATE PARTNER (Sold-to party) POSTL_COD1 POSTL_COD2 SEX PARTNER (Ship-to party) POSTL_COD1 POSTL_COD2 SEX ORGMAN DIVISION SALES_OFFICE SALES_GROUP SHIPPING *) INCOTERMS1 *) INCOTERMS2 *) SHIP_COND *) DLV_PRIO APPOINTMENT *) CONTSTART *) CONTEND VBAK-KVGR4 VBAK-KVGR5 VBAK-VDATU KNA1-PSTLZ KNA1-PSTL2 NVK-PARGE KNA1-PSTLZ KNA1-PSTL2 KNVK-PARGE VBAK-SPART VBAK-VKBUR VBAK-VKGRP VBKD-INCO1 VBKD-INCO2 VBAK-VSBED VBAP-LPRIO VEDA-VBEGDAT VEDA-VENDDAT Object characteristics with read and write access to database content You have both read and write access to many sales order fields in the product configuration by means of object characteristics with SAP CRM 5.1. You can, for instance, edit the order quantity directly on the product configuration user interface. When you confirm the product configuration, the changed values are transmitted to the sales order and it is then updated with these values. The object characteristics in the product configuration could previously only be displayed, not edited. If you have changed an object characteristic value in the product configuration and it was applied to the sales order, you can only change this value again in the product configuration and you need to switch to the product configuration user interface to do so. It is no longer possible to change values in the sales order field. A mutual change of values is not permitted because the main system in this case is the Configuration Engine. The following fields are editable and can be changed in the product configuration: CRM table ORDERADM_I PRODUCT_I Field name in SAP CRM DESCRIPTION GROSS_WEIGHT NET_WEIGHT WEIGHT_UNIT VOLUME VOLUME_UNIT REQ_DLV_DATE ORDER_QTY Field name in SAP ECC VBAP-ARKTX VBAP-BRGEW VBAP-NTGEW VBAP-GEWEI VBAP-VOLUM VBAP-VOLEH VBAK-VDATU VBAP-KWMENG SALES SCHEDLIN ______________________________________________________________ SAP AG 96 SAP-System ______________________________________________________________ SHIPPING APPOINTMENT INCOTERMS1 INCOTERMS2 SHIP_COND DLV_PRIO CONTSTART CONTEND VBKD-INCO1 VBKD-INCO2 VBAK-VSBED VBAK-LPRIO VEDA-VBEGDAT VEDA-VENDDAT You can also use this new function in the multilevel product configuration and set values for the characteristics of subitems. Multilevel product configurations are configurable products with subitems that can contain yet more subitems. The number of levels in such a hierarchy is unrestricted. You can enhance the functions in the product configuration with the Business Add-In (BAdI) CRM_CONFIG_BADI. You can find this BAdI in SAP CRM Customizing by choosing Customer Relationship Management -> Basic Functions -> Product Configuration -> BAdI: Enhancements for Product Configuration. You can set values for user-defined object characteristics that relate to table fields with the method SET_CONTEXT in the BAdI CRM_CONFIG_BADI and add more object characteristics at runtime. However, you can only use object characteristics that relate to a table field. You can use the method SET_VALUE for user-defined fields and set corresponding values. You can also transfer values from product- and individual object attributes to the Configuration Engine with the new method SET_Iobject_Context. In addition, you can update the sales order fields with data returned from the Configuration Engine using the method CHANGE_FIELDS_AFTER_CONF. Effects on Customizing You have determined an object characteristic for the field, the value of which you want to use in the configuration model. To do so, you call the transaction CT04 in SAP ECC and enter the table and field names for the field that you want to assign to the object characteristic, on the tab page Additional Data. If you only want to allow read access to the context parameters you need to set the indicator Not Ready for Input on the tab page Additional Data . 1.9.9.6 Characteristics for Display of Messages (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use characteristics with a certain naming convention in order to display messages on the characteristic value assignment screen. In this way, you can display additional information in the ______________________________________________________________ SAP AG 97 SAP-System ______________________________________________________________ Configuration Engine, depending on the current state of the configuration. For example, you can use this function to make further information such as explanations of derived values or technical recommendations, available to the user. The long text for the characteristic value that represents the message is always displayed. The characteristic description (short text) is only displayed when there is no long text available. The messages can be grouped into the following types: Information Warning messages Error messages These message types are all shown differently on the user interface. The text is displayed up to a maximum of 80 characters. If the text is longer than 80 characters, dots after the text indicate that more information is available. The complete text can be displayed by means of a link. Note: The function is only supported if the characteristic name was created with a corresponding prefix. This prefix is "UIMESSAGE_" by default. You can change this prefix with the parameter characteristics.messagecstics.prefix in Extended Configuration Management (XCM) and adjust it to your requirements. If you deactivate the function using the parameter characteristics.messagecstics.enable, then the characteristic is shown on the user interface like the other characteristics, that is, using the regular display type. It is not hidden, however. Effects on Customizing You need to have created the desired dependency in product modeling for the characteristic and you must be able to display the characteristic. In addition, call transaction CT04 in SAP ECC, define the corresponding dependency and choose the value Blank Character for the indicator No Display on the tab page Additional Data. You can make the settings for this function in XCM by using the following parameters: Parameter Default Value Description characteristics.messagecstics.enable T You can activate or deactivate the function with this parameter. If you set the value "F", then the characteristic is shown using the regular display type. characteristics.messagecstics.prefix "UIMESSAGE_" You can determine the prefix for the characteristic with this parameter. If this function should be used for a characteristic, the characteristic description needs to have this prefix. characteristcs.messagecstics.showid F You use this parameter to determine whether the ID of the message, that is, the characteristic value, should also be shown in the display. ______________________________________________________________ SAP AG 98 SAP-System ______________________________________________________________ 1.9.9.7 Product Modeling (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. The changed Product Modeling Environment (PME) is available. The following changes and enhancements are included: New interface A new, browser-based interface is available. Transport product models between different CRM systems You can use this to create a product model in a test system, for example, and later transport it to a production system. Active and inactive versions To avoid defect or incomplete product models, you can make changes to an inactive version. When you are finished with your changes you replace the active version with the version you changed and then release it. You cannot release an inactive version. Configurable components The product structure contains all possible components. You can define rules that determine under which conditions a component can be chosen. Structure with multiple levels A component can be reconfigured and have a customer-defined product structure. Relationships in the product structure A product with components can transfer characteristic value assignments to these, or vice versa. The data type Date is possible for characteristics. Static and dynamic characteristic attributes A characteristic can have a value that is read-only and is therefore only displayed. Characteristic groups Characteristics can be bundled into groups for better structuring. The characteristic groups are shown on the interface as tab pages. The use of custom functions in relationships is possible. There are multiple types of dependencies based on tables, such as default values, assigned values and value range restrictions. There is a hierarchy tree that displays products, classes, characteristics, values and product structures as well as their relationships to each other. It is possible to start the configurator with one click, to test the current configuration rules. Integration with the maintenance of other master data around the product. - - - - ______________________________________________________________ SAP AG 99 SAP-System ______________________________________________________________ Effects on Data Transfer The data model was not changed. However, manual adjustments to the new options and means of expression are necessary for the upgrade of CRM 4.0 or CRM 5.0. Effects on Customizing Define the settings for product models under Define Settings for Product Models. See also For information about product modelling, see SAP Library under SAP Customer Relationship Management -> Components and Functions -> Master Data -> Products -> Functions -> Modeling Configurable Products. 1.9.10 CRM-BF-PR Pricing 1.9.10.1 Terminology in Condition Maintenance (Changed) Use As of release CRM 5.1, the terms 'condition type' and 'condition maintenance group' (or 'maintenance group'), previously used on the CRM Web Client UI will be replaced with a term that is more specific to the respective use. The following terms replace the previous term 'condition type': Use Rebate processing Pricing Free goods New Description Rebate element Price element Free goods element The superordinate term for all uses on the Web UI is: 'condition element'. The following terms replace the previous term 'condition maintenance group': Use Rebate processing Pricing Free goods New Description Rebate type Price type Free goods type The superordinate term for all uses on the Web UI is: 'condition type'. The previous terminology ('condition type' and 'condition maintenance group') will be kept in the ______________________________________________________________ SAP AG 100 SAP-System ______________________________________________________________ Customizing of the affected uses. Note that 'condition type' on the Web UI indicates something different than in Customizing. 1.9.10.2 Credit Analyst Workbench (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use the Credit Analyst Workbench to check and further process sales transactions that were blocked as the result of the credit- and credit rating check . You can display blocked as well as released sales orders in an overview list. In addition, you can display sales orders that have no valid letters of credit assigned to them. The sales transactions are arranged together and displayed for each payer. You can check the credit situation for each customer and then decide, based on your credit policy, how the sales orders should be further processed. You have the following options: Check transactions for credit rating and credit worthiness Release transactions after credit rating- and credit check Reject all items Navigate to documents and make changes there You can also perform the following actions immediately: Release all of a payer's transactions Reject all of a payer's transactions Check all of a payer's transactions ______________________________________________________________ SAP AG 101 SAP-System ______________________________________________________________ 1.9.10.3 Approval Process for Price Changes in Sales Orders (New Use This release note is only relevant if upgrading from SAP CRM 5.0. You can prevent employees from manually changing prices that are automatically calculated using pricing. You can allow certain employees to manually change prices in the sales order. If the employee does not have the authorization to change prices, the system triggers an approval process. If an employee wants to manually change the price of an order item that was automatically assigned in the sales order or complaint using pricing, the system checks if he or she is authorized to change prices. If the employee has no authorization, this change must be approved by someone entitled to grant approval, such as the head of department. An approval process is triggered by the system. The changes made by the employee are examined by the head of department, and then approved. If price changes are made by someone not entitled to make them, the follow-up transactions billing and shipping are not triggered. Depending on the customer type, a billing- and shipping block is set in the sales order. When the head of department approves the price change, the approval process is complete, and the statuses Blocked for Billing and Blocked for Shipping are cleared. The follow-up transactions can then be triggered again. The person entitled to grant approval (head of department) can change prices without triggering the approval process, provided that the authorization object CNDAPPROVE is assigned to him or her. Effects on Customizing In SAP CRM Customizing, assign the action profiles STOP_SHIPPING and STOP_BILLING, delivered as standard by SAP, to the transaction type in which you want to use this function. The system checks, with the help of these action profiles, if manual price changes have been performed. The system also checks if the user can change prices without triggering the approval process. You can make the settings in SAP CRM Customizing under Assign Action Profile to the Business Transaction Type. Create appropriate status profiles. Use the status profiles CRMSTSHP and CRMSTBILL, available as standard, as templates. You can find further information in the SAP CRM Implementation Guide (IMG) under Customer Relationship Management -> Transactions -> Basic Settings -> Status Management -> Change Status Profile for User Status. Assign this status profile to the transaction type that you want to use. The user who clears the status must have authorization for the authorization object CNDAPPROV. The person entitled to grant approval must be assigned to the authorization object CNDAPPROV so that they can change prices without triggering an approval process. Activate the workflow template CNDDAPPR, delivered as standard by SAP. - - - ______________________________________________________________ SAP AG 102 SAP-System ______________________________________________________________ 1.9.10.4 Display Price List(s) for an Account (New) Use This release note is only relevant if upgrading from SAP CRM 5.2. You can display the price list(s) for an account on the account overview page by choosing More -> Price List Preview. Your sales employees can then search for the price list for an account and find out the price of a specific product. If multiple price lists are assigned to an account, a dialog box appears on the user interface in which you can select the required list. A PDF document then opens which displays the respective price list for the account with the products and their net prices. Effects on Customizing You use the action profile NETPRICELIST in default Customizing for actions in the price list. You can find more information in the SAP Implementation Guide (IMG) by choosing Customer Relationship Management -> Basic Functions -> Actions -> Actions in the Price List -> Change Actions and Conditions -> Define Action Profiles and Actions. 1.9.11 CRM-BF-COM Content Management 1.9.11.1 Enhancements for Content Management (Changed) Use The following enhancement has been added to Content Management: Template Designer You can use Template designer to draw CRM data from a Web service and insert it in a document, either in Microsoft Word format, or in Adobe PDF format.. Adobe DPF documents are read-only. You can add these documents as attachments to a business object in Content Management by: Selecting the attachment from Content Management or local hard disk Entering a corresponding URL Selecting a document template ______________________________________________________________ SAP AG 103 SAP-System ______________________________________________________________ 1.9.12 CRM-BF-WST Web Services Tool 1.9.12.1 Web Services Tool (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use this tool to create basic Web services based on the BOL design layer. The design layer tool already available enables UI objects to be modeled. A new entity referred to as a service object, similar to a UI object but with additional attributes, has been introduced to allow Web service objects to be created. The Web services tool transforms the finalized service objects into a function module, which is then used by NetWeaver to generate the corresponding Web services. The tool comprises a wizard that guides you through the service definition process, which consists of four main steps: 1. Select the service object and the operations required. The following are supported: 2. 3. 4. Basic queries Read operations Create operations Change operations Select the attributes required based on the BOL tree displayed for the object. By navigating through the tree, you can select the relevant attributes for the relationships you require. Maintain the attributes for the relationships of the selected object and the attributes of the query object. Enter certain technical information, save and activate the service object, and then set to Productive. Note that to use your services in other systems you have to transport them manually. For more information, see Transport Service Objects. ______________________________________________________________ SAP AG 104 SAP-System ______________________________________________________________ Effects on System Administration To improve performance, you should apply the Basis corrections in Note 964749. This correction speeds up the deletion of Web services, which results in faster activation, as deletion is part of this process. You might also need to apply Note 954604 (Timeout during creation of a service definition). 1.9.12.2 Web Service Consumption Tool (New for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The Web service consumption tool enables you to create a new BOL object, that is, a BOL component with a root BOL object and search objects, in the business object layer. This means that if you need to retrieve data from locations other than SAP CRM using Web services, the BOL object enables you to make this data available on the UI using the same tools provided for standard CRM functionality. The Web service consumption tool reuses standard SAP NetWeaver tools. The CRM tool currently supports the consumption of read and query services. The tool is available in Customizing for Customer Relationship Management under UI Framework -> UI Framework Definition -> Web Services -> Web Service Consumption Tool: Create BOL Objects. 1.9.12.3 Web Services Tool (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The tool has been included in the Service Professional role (work center "Service Operations") and enhanced with the following features: Compound Services When you create a Web service, you are restricted to one root object of the specified component (business object). This means that when you select a root object such as BTOrder (Business Transaction), you are restricted to the dependent objects within that component, and you cannot create relationships to objects contained in other components, such as Business Partner. By selecting a component set, however, you can use data from different components contained ______________________________________________________________ SAP AG 105 SAP-System ______________________________________________________________ within the component set. To do this, you create relationships from the source component to the additional components, that is between the relevant access objects, thus enabling more than one root object to be processed. This type of service is referred to as a compound service, and is available for read and change services. Note that when working with change compound services, you can make any changes provided they do not involve creating a new root object. For example: You can create a new address for an existing business partner, or change an existing priority or contact in a sales order. If you are working with the sales order, you cannot create a new contact When creating a service object, you select a business object and root object as before. However you also decide whether the service object is to constitute a compound service and, if this is applicable, you select the relevant component set. The objects this set contains are shown in the Included Objects field. Error Handling The status of a service object was previously changed from Active to Draft if errors occurred during the generation process following an import into another system, while, confusingly, the Productive status remained as it was. Now the status is not changed, but the system indicates that an import generation error has occurred, enabling you to manually trigger regeneration directly from the UI. Authorization Object In addition to the existing authorization checks (for activating Web services, for example), a new authorization object CRM_WST is available specifically for the Web services tool. It is currently only used to check the authorization for transporting service objects. Service-Enablement Information This indicates for which operations a selected BOL object has been enabled. The information is available on wizard screen 2 in expert mode only. Backend Clients The clients in which the Web service has been released are listed on wizard screen 4 in expert mode. Mandatory Information in Node Attributes An indicator available in the node attributes on wizard screen 2, expert mode, shows that an attribute is mandatory for create operations.This means that even if it is not explicitly selected, it will be generated in the input structure of the create operation. Knowing this, you have the option of selecting the attribute and specifying a default value for it on wizard screen 3. Export of Tree Structure to Excel This provides a documentation of the service object in an Excel-based form. The selected attributes are shown hierarchically with their position within the BOL structure, together with information contained on wizard screen 3, such as excluded information and defaults. This function is available on wizard screens 2 and 3. - - - - ______________________________________________________________ SAP AG 106 SAP-System ______________________________________________________________ 1.10 CRM-BE Billing 1.10.1 Transfer of Accounting Indicator to Billing (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The accounting indicator field in service transactions can be transferred to billing, where it is used for pricing and account determination. Effects on Customizing To enable transfer of the accounting indicator, activate one of the following features in the IMG under Customer Relationship Management -> Billing -> Configure Application: Integration with Contract Accounting Enhanced Attributes for Pricing 1.10.2 Intercompany Billing (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. The currency and exchange rate of an intercompany invoice is derived from settings in a new Customizing activity. This is because the invoice currency is not necessarily the same as the currency of the sales order. You assign a reference sales area (sales organization, distribution channel, and division) to each business unit that issues intercompany invoices. The system then determines the relevant currency and exchange rate type for intercompany billing from the partner master data of the payer. This setting also enables the system to determine the appropriate credit control area for intercompany invoices from the IMG activity Customer Relationship Management -> Master Data -> Cross-System Assignment of Organizational Units -> Assign Credit Control Areas to Sales Organizational Units. ______________________________________________________________ SAP AG 107 SAP-System ______________________________________________________________ Effects on Customizing You specify the reference sales area in Customizing for CRM, by choosing Billing -> Intercompany Billing -> Specify Sales Area Data for Determination of Invoice Currency. 1.10.3 Transfer of Billing Data to SAP GTS for Intrastat Declarations (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can transfer billing data from SAP CRM to SAP Global Trade Services (SAP GTS) in order to create Intrastat declarations. You can find the data transfer report in the SAP Easy Access menu under Sales -> Billing -> Transfer Data for Intrastat to SAP GTS. According to the settings you make for data selection, the report filters and transfers billing data that meets the following criteria: The billing document was created for an Intrastat-relevant business transaction Relevant transactions are those in which goods movement takes place and those in which billing amounts are adjusted (for example, complaints). The departure and destination countries are such that the transaction is relevant for Intrastat declarations The billing document has been transferred to accounting The report only selects documents that can no longer be changed, since they have been transferred to accounting. This ensures that only final values are transferred to SAP GTS, and that values in SAP GTS are always consistent with values in accounting. - Effects on Customizing You determine which item categories correspond to which Intrastat codes for business transaction types and statistical procedures. You do this in the IMG under Customer Relationship Management -> Billing -> Integration -> Transfer of Billing Documents to Foreign Trade -> Transfer to SAP GTS 3.0 and Later Releases -> Transfer of Billing Data for Intrastat Declarations. If required, you can use the Business Add-In in the above IMG section to modify how the data transfer report selects billing documents and maps data to SAP GTS. ______________________________________________________________ SAP AG 108 SAP-System ______________________________________________________________ 1.10.4 Claim Settlements (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Claims related to trade promotion management (TPM) and market development funds (MDF) are settled in the SAP CRM billing component and transferred to the following integrated applications: SAP ERP Financials (accounts payable and receivable, controlling) SAP ERP Dispute Management (dispute cases for deduction claims, prepayments, and write-offs) The following is an overview of the claim settlement functions in SAP CRM billing. Claims and Prepayments When a claim is approved or a prepayment triggered, items from the claim or prepayment transaction are transferred to the billing due list. Settlement takes place either during a scheduled settlement run or is triggered manually. During settlement, credit memos are created for the payable amount. In the case of deduction claims, which do not require a payout, the credit memo clears a dispute case in SAP ERP Dispute Management. You can activate an availability check to determine whether the fund budget is sufficient to reimburse each claim item. If the budget is insufficient, the billing due list item remains open. You can also make partial payouts for claims if the fund budget is insufficient for a full payment. Write-Offs Amounts that are written off because they have been overpayed to a claiming account or are unresolved are also processed in billing. These amounts are posted as expenses in accounting. Cancellation and Correction You can cancel and correct settlements. For more information, see the application help for settlements in claims management. Note: You cannot use the following functions for claim transactions: Intercompany billing Supplementary invoice Retroactive billing Condition-based invoice split Effects on Customizing You need to make the following settings in Customizing for Customer Relationship Management, under Billing: Activate the following features (activity Configure Application): ______________________________________________________________ SAP AG 109 SAP-System ______________________________________________________________ - Enhanced Account Determination Funds Management Integration Marketing Set Set the billing relevance of all claims-related item categories to Value-Based Billing After Approval (activity Define Billing Relevance of Item Categories) Define the billing types that you require for settling claims (activity Define Billing Types): Assign one of the predefined billing categories for prepayments or claims. Assign any cancellation copy requirements that you require. You can use a predefined copy requirement, or create your own in the activity Define Copy Requirements and implement it in the activity System Enhancements -> Business Add-Ins ->Copy Requirements for Cancellation. If required, assign an account determination type for the billing type. Note that account determination types assigned to billing types override the account determination type assigned to the entire application (in the IMG section Integration -> Transfer of Billing Documents to Accounting). - - Define the billing item categories that you want to use for claim settlements (activity Define Billing Item Categories) Assign each transaction type and item category for claims to the corresponding billing item categories (activity Item Category Determination -> Assign Item Categories) You need to make the following settings in Customizing for Customer Relationship Management, under Billing -> Integration -> Transfer of Billing Documents to Accounting -> Transfer to Accounts Receivable (FI-AR) and Accounts Payable (FI-AP): Specify symbolic accounts for determining the following in SAP ERP Financials : Expense and accrual accounts for claims, depending on the sales organization and expense type Balance sheet accounts for prepayments, depending on the sales organization and expense type You do this in the activity Enhanced Account Determination -> Assign Symbolic Account Key. Specify the document types that you want to use to post billing data in accounting (activity Assign Document Types) Specify the dunning block and payment terms for prepayments (activity Define Parameters for Prepayment) You also need to set up data exchange according to SAP Note 883162 to enable vendor-based integration with accounts payable in SAP ERP. In particular, you need to make settings for the following: See also For an overview of claims management functions, see the release note Claims Management (New). For detailed information on claims and claim settlement, see the application help for claims management. The billing type that you use for integration with accounts payable The billing category Claim Settlement (Accts Payable) ______________________________________________________________ SAP AG 110 SAP-System ______________________________________________________________ 1.10.5 CRM-BE-DL Billing Due List 1.10.5.1 Reference to Letter of Credit in Billing Documents (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Information relating to letters of credit is transferred from relevant sales orders to the billing due list, and subsequently to billing documents. The following information is transferred: Letter of credit GUID (globally unique ID) Indicator showing whether a letter of credit is required for the sales order If a letter of credit is issued for a sales transaction, the name and address of the business partners stored in the letter of credit must be printed on an invoice, instead of the details of the sold-to party in the sales order. The letter of credit information is, therefore, passed to the Smart Forms interface for printing. Note The letter of credit ID is a split criterion for billing documents. For each billing due list item with a separate letter of credit assigned, a separate billing document is created. You need to adjust your Smart Forms setup to enable the address of the letter of credit partner to be printed on invoices. Effects on Customizing To enable the letter of credit reference to be transferred to billing documents, you need to activate the feature Integration with SAP GTS from 3.0. You do this in the IMG under Customer Relationship Management -> Billing -> Configure Application. 1.10.6 CRM-BE-FI Transfer to Accounting 1.10.6.1 Controlling Integration for Intercompany Billing (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. ______________________________________________________________ SAP AG 111 SAP-System ______________________________________________________________ Data from intercompany invoices is transferred to accounting and controlling in an integrated SAP ERP system. Data from the relevant order is used in SAP ERP to derive account assignments for both the seller and supplier. Controlling objects are created in profit center accounting and profitability analysis when an order is created or changed. Revenue and cost of goods sold are posted in controlling. Note: Controlling integration is supported as of ERP 2005, SAP_APPL, Support Package 08. Controlling integration for intercompany billing is only supported if you use service parts management (see "Customizing" below). Controlling integration is not supported if you usemulti-level intercompany billing. Effects on Customizing You have activated the system configuration for service parts management, by choosing Customer Relationship Management -> Transactions -> Basic Settings -> Activate System Configuration for Service Parts Management. 1.11 CRM-RB Rebate Processing 1.11.1 Terminology in Condition Maintenance (Changed) Use As of release CRM 5.1, the terms 'condition type' and 'condition maintenance group' (or 'maintenance group'), previously used on the CRM Web Client UI will be replaced with a term that is more specific to the respective use. The following terms replace the previous term 'condition type': Use Rebate processing Pricing Free goods New Description Rebate element Price element Free goods element The superordinate term for all uses on the Web UI is: 'condition element'. The following terms replace the previous term 'condition maintenance group': ______________________________________________________________ SAP AG 112 SAP-System ______________________________________________________________ Use Rebate processing Pricing Free goods New Description Rebate type Price type Free goods type The superordinate term for all uses on the Web UI is: 'condition type'. The previous terminology ('condition type' and 'condition maintenance group') will be kept in the Customizing of the affected uses. Note that 'condition type' on the Web UI indicates something different than in Customizing. 1.11.2 SAP CRM Rebate Processing WebClient UI (Enhanced) Use The following functions of SAP CRM rebate processing are now available in the WebClient UI: Rebate agreements Display of rebate activity details On the agreement item detail page, you can navigate from the assignment block Rebate Activity Summary to the new page Rebate Activity Details which contains the following information: Activity summary Period details Condition details Adjustment details Settlement details Rebate due list Note the following differences between the rebate due list in the WebClient UI and SAP GUI: WebClient UI Rebate activity detail view available Background processing not available Setting up of variants for batch processing not available SAP GUI Rebate activity detail view not available - Manual processing and adjustment support ______________________________________________________________ SAP AG 113 SAP-System ______________________________________________________________ - Mass processing 1.11.3 Use This release note is only relevant if upgrading from SAP CRM 5.0. The following functions are now available in rebate processing: Mass maintenance for rebate agreements You can use this function to carry out mass changes for rebate agreements at header, item or condition level. For example, you can further edit rebate agreements that have been created using mass generation. Moreover, you can track your mass changes in the mass change logs. You can use a new administrative function, available via the SAP Easy Access screen, to mass generate rebate agreements from either template rebate agreements or other productive rebate agreements. The agreements can be generated for one or more business partners. Rebate activity details The new rebate activity details page offers information about a particular rebate activity. A rebate activity, generally speaking, is a rebate due list item. The following information is available on the rebate activity details page: Display of activity summary with information on total values to date Display of rebate activities by cumulation period Display of information on rebate conditions, adjustment details, settlement details, and invoices from sales - Free-goods rebates You can now realize free-goods rebate programs using rebate processing in CRM. The free-goods capability provides the possibility to pay out earned rebates in the form of free products. The calculation methods for the quantity of free products to be shipped to the customer could either be value-based or quantity-based: Value-based: For $X of product A purchased, Y units of product B are earned Quantity-based: For N units of product A purchased, M units of product B are earned This new capability is also delivered with the ability to automatically generate a sales order for free-goods rebates at the time of settlement. SPM functions in rebate processing ______________________________________________________________ SAP AG 114 SAP-System ______________________________________________________________ Consumable rebates When you activate the system configuration for service parts management (SPM), you can additionally integrate consumable rebate programs into rebate processing. Consumable rebate processing is only available within service parts management. Consumable rebate programs consist of sequences of earning-, waiting- and consumption periods, which you can define according to your business needs. The sales volume for a customer is accumulated within a defined earning period and the resulting earned rebate balance is calculated. The customer can return products against this earned rebate balance within a defined consumption period. If a waiting period has been defined, the customer may be required to wait before he is allowed to return products. When the customer requests to return products, the return value is validated against the earned rebate account balance. The total value of the customer's returns is restricted to the amount of the earned rebate balance for a particular earning period. Rebates earned in one particular earning period can only be consumed in the corresponding consumption period. Any remaining rebate balance at the end of a consumption (return) period can be rolled-over for use in the next consumption period, settled in the form of a credit memo, or closed. Rebate activity details page for consumable rebates The rebate activity details page offers the following additional information and functions for consumable rebate programs: Display of current and future consumable balance These figures allow you to answer customer inquiries concerning their current account balance: The current consumable value includes rebates that have been earned to date, have not yet been consumed or closed, and can currently be consumed because the corresponding consumption periods are open. The future consumable value includes rebates that have been earned to date and can be consumed in future consumption periods. The current and future consumable values amount to the earned rebates to date that have not yet been consumed or closed. Rebate activity values on period level On period level, you can carry out partial settlements, post base adjustments and balance adjustments, close periods, or roll over the balance from one consumption period to the next. - Effects on Customizing To use the free-goods rebate program, you must make the following settings in Customizing for SAP Customer Relationship Management (SAP CRM): Activate free-goods rebate processing under Rebate Processing -> Configure Application. Define the corresponding condition types as relevant for free-goods rebates under Rebate Processing -> Set Up Rebate Determination -> Create Condition Types. ______________________________________________________________ SAP AG 115 SAP-System ______________________________________________________________ - Assign the condition type to a condition maintenance group under Rebate Processing -> Set Up Rebate Determination -> Create Condition Maintenance Group. Assign the condition maintenance group to the corresponding item category under Transactions -> Basic Settings -> Define Item Categories. Ensure that the standard action settings for the creation of the sales order for free-goods rebates are in line with your business processes. You do this by choosing Basic Functions -> Actions -> Actions in Rebate Processing: You have ensured that the correct transaction type and condition for discount are assigned for generating the sales order. You have ensured that the sales order is generated at the correct time in rebate processing. In the standard delivery, the sales order for free-goods rebates is created when the settlement document has been transferred to financial accounting and the corresponding action has been executed via the WebClient UI or via the selection report in the Post Processing Framework. Note that you have to set up the report in the Post Processing Framework if you would like to execute the action via the report, for example on a regular basis. For more information on the Customizing settings for free-goods rebates, see the application help for SAP Customer Relationship Management in the SAP Library under Components and Functions -> Sales -> Rebate Processing -> Free-Goods Rebates. To use the consumable rebate program, you must make the following settings in Customizing for SAP CRM: Configure service parts management. Specifically, ensure that the complaints and returns entitlement integration is configured to support your program returns. Mark the item categories that you want to use for the processing of consumable rebates as rebate-relevant in entitlement management under Entitlement Management -> Integration -> Integration to Complaints and Returns -> Assign Relevance of Returns Entitlements to Compl. and Returns. Mark the products that can be returned in the context of consumable rebate programs as relevant for the rolling purchase history in entitlement management. You do this in the CRM WebClient UI on the page Entitlement Profiles: In the dropdown box Entitlement Profile Category select Rolling Purch. Hist In the dropdown box Entitlement Profile Set select Product ID Create an entry for the product, and in the dropdown box Profile ID select Eligible - - Activate consumable rebate processing under Rebate Processing -> Configure Application. Define the sequences of earning, waiting and consumption under Rebate Processing -> Rebate Profiles -> Define Consumable Rebate Profile. If applicable, use a BAdI implementation to influence the calculation of the consumable value. Define the BAdI implementation under Rebate Processing -> System Enhancements -> BAdI: Calculation of Consumable Rebate Value. For more information on the Customizing settings for consumable rebates, see the aplication help for SAP Customer Relationship Management in the SAP Library under Components and Functions -> Sales ______________________________________________________________ SAP AG 116 SAP-System ______________________________________________________________ -> Rebate Processing -> SPM Functions in Rebate Processing. 1.12 CRM-EM CRM Entitlement Management 1.12.1 Entitlements Management (Enhanced ) Use This release note is relevant only if upgrading from SAP CRM 5.0 Entitlement management will now be available on the Web-based user interface. You can use entitlement management to Maintain deposit entitlements to keep track of liabilities of customers, including deposit invoicing, deposit deferral, defer clearing and deposit credit Maintain return entitlements, to keep track of the products that the customer is allowed to return, Use automatic consumption to reduce entitlement quantities to the desired extent, Maintain inbound due-lists, which help you capture information from external documents that either affect existing entitlements or determine how you create entitlements, Maintain settlement due-lists to initiate either CRM Billing or an FI posting, to settle the liabilities triggered by entitlements Set expiration dates and activation periods for entitlements and also determine if and which partners/products are eligible for schemes such as the rolling purchase history or deposit credit or direct purchase program all on the new Web interface. Intercompany Entitlements Processing (New) Entitlements management helps you track entitlements for internal companies or organizations also. This function allows you to track intercompany entitlements and lets you know of positive or negative balances, so you can settle liabilities between companies and subsidiaries. When inter-company liabilities are processed, intercompany entitlements are both created and consumed automatically, depending on whether the entitlement involves a positive or negative balance. Consumable Rebates (Enhanced) Rebates are now integrated into Entitlement Management. Consumable rebates are what was previously known as non-core volume-based entitlements. This function focuses on the value of sales and returns, rather than their quantity. It works around new or unused parts. It operates like a returns entitlement, which works with values; but unlike rolling purchase history, which works with quantities. With consumable rebates, accumulated values can be used to return new or ______________________________________________________________ SAP AG 117 SAP-System ______________________________________________________________ unused parts to the manufacturer. Effects on System Administration The new UI role: Service Parts Management (SPL) This provides authorization for the use of entitlement management in user administration. The authorization profile: SAP_CRM_UIU_SPL_PROFESSIONAL, use transaction PFCG Effects on Customizing To use entitlement management, you have activated the system configuration for service parts management. To do this, see Prerequisite for Entitlement Management You also have to make the corresponding settings in Customizing For business logic enhancements in Customizing, under Customer Relationship Management -> Entitlement Management -> System Enhancements -> Define Business Logic Enhancements and Customer Relationship Management -> Entitlement Management -> Basic Functions -> Entitlement Programs -> Define Number Range and Residence Time for Programs For information about new activities and existing activities that have been changed, renamed or deleted, see New, Changed and Removed IMG Activities in SAP CRM 5.2 1.13 CRM-BTX Business Transactions 1.13.1 Use of the Maintenance Framework for Business Transactions (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The maintenance framework for business transactions (BTMF) is a tool with which you can execute change processes in any sales transaction. For now, it is used only for the provider contract as standard and offers a number of actions that the user can select on the user interface by using pushbuttons. The possible change processes are executed with the corresponding methods, as follows: Method EXECUTE FINISH CANCEL Change process Execute process Finish process Cancel process ______________________________________________________________ SAP AG 118 SAP-System ______________________________________________________________ REJECT RELEASE Reject process object Release process object The navigation connected with the action is specified by the system. In the standard system, these methods are implemented for the following change processes that you can choose in the provider contract: Extend contract and undo extension Cancel contract and undo cancellation Change product configuration Change product Change technical data (SIM card, for example) Change bank address Change customer address Corresponding classes of the interface IF_CRM_BTMF are implemented for these processes as standard. You can use these example implementations to define dedicated change processes and adjust them to the requirements of your business. The Business Rule Framework (BRF) is used to check the change processes. The CHECK method of the BTMF is available for this and is always called by the BTMF first and, with the help of the BRF, checks if the change process may be executed. 1.13.2 Sale of External Products (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. In service parts management, you can sell products for which there is no product master available in your SAP CRM. You may not manage them in your stock because, for example, the product does not fit in with your product assortment. Such products are called external products. Significantly, in a similar way to regular third-party order processing, the delivery of the external products is taken on by an external supplier, who then delivers the products directly to the customer. External products can be service parts such as car tires, or other products, like promotional gifts. To sell the external products, you need to determine the required conditions with the external supplier using a purchasing contract. Among other conditions, you determine the external products and their prices in the purchasing contract. ______________________________________________________________ SAP AG 119 SAP-System ______________________________________________________________ The external supplier transfers the sales order data for external products to your SAP CRM using EDI, and the system then automatically creates the sales orders. The sales order is linked with the purchasing contract, so you can use the condition types from the SAP ECC purchasing contract in the SAP CRM sales order. The condition types are then incorporated into the sales order in the pricing. This is dependent on your customizing settings. You can bill the external products as usual. In SAP ECC, the system automatically creates a credit memo for the external supplier and in SAP CRM, the system creates a debit memo for the customer. In addition, complaints about external products can also be handled using this process and are always based on customer invoices as follow-up transactions. Note: Billing amounts cannot be recalculated for external products. If you want to change the unit of measure in the sales order for which billing has already taken place, you have to cancel the billing document and create a new sales order. Effects on Customizing General Effects The system configuration for service parts management is activated. You can find further information in the SAP Implementation Guide (IMG) for Customer Relationship Management under Activate System Configuration for Service Parts Management. You have set the indicator External Products Allowed in the definition of the transaction type. You can make these settings in SAP CRM Customizing under Define Transaction Types. In the sales order, the External Product indicator must be set at item level. The sales order is linked with a valid purchasing contract. You have determined the customizing settings for pricing. See Define Mapping for Condition Types from Application BBP to Application - Effects on Billing To enable tax to be calculated correctly for external products during billing, you need to activate the feature Product Tax Group (Third-Party Order). You do this in Customizing for CRM by choosing Configure Application. Select the feature and save your settings. You need to ensure that the correct revenue accounts are determined for external products . You do this in Customizing for CRM by choosing Assign Revenue Accounts for Sales Transactions. Make sure that you have at least one entry without an account assignment group assigned (in the field AccountGrp). See also Release note: Complaints for External Products (New) ______________________________________________________________ SAP AG 120 SAP-System ______________________________________________________________ 1.13.3 Sold-To Party Profiles in Sales Orders (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can indicate a sold-to order profile in a sales order. This profile depends on the sold-to party and contains predefined values for fields in the sales order. If the system determines a sold-to party profile for a sold-to party, it copies these predefined values into the sales order. Using the sold-to party profiles, you can predefine field values in the shipping and availability check areas in the sales order. For example, if some customers often require prompt shipment of goods, you can create a sold-to party profile "Quick Delivery" that contains respective settings to ensure fast delivery. Similar to the sales area data, sold-to party profiles are a way of predefining values for fields in the sales order. This function is only available if the system configuration for service parts management is active. 1.13.4 Different Actions in Sales Orders Depending on Transaction Mode (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can set up the system to trigger different action profiles depending on the transaction mode (meaning, whether you are creating or editing a sales order). For example, you can print the order when you create it, but send an e-mail when you are changing it. 1.13.5 Displaying Customer-Specific Fields/Business Transaction Components ______________________________________________________________ SAP AG 121 SAP-System ______________________________________________________________ in the CRM WebClient UI (New for SP02) Use This release note is relevant if upgrading from SAP CRM 5.2. If you have enhanced the business transaction components Customer_H for customer-specific header data, or Customer_I for customer-specific item data, you can easily display the new fields in the CRM WebClient UI. You do this by using the UI Configuration Tool in the Customizing activity at Customer Relationship Management -> UI Framework -> UI Framework Definition -> Configure User Interface. By default, the corresponding BSP components BTCUSTOMER_H for customer-specific header data, or BTCUSTOMER_I for customer-specific item data, are available in the respective overview pages of the header- or item components of the business transactions, as available assignment blocks. For example, the view SOHOverView of BSP component BT115H_SLSO, which depicts the overview page for the sales order header, contains the BSP component BTCUSTOMER_H. The view SOIOverView of BSP component BT131I_SLS, which depicts the overview page at item level, contains the BSP component BTCUSTOMER_I. So that the new fields in the CRM WebClient UI can be displayed in the Customer Fields assignment block, you must still transfer these BSP components to the list of displayed assignment blocks, in the respective overview pages. You must also create at least one configuration, with which you define the layout, for the view CustomerI of BSP component BTCUSTOMER_I, or for the view CustomerH of BSP component BTCUSTOMER_H. You thereby define how the fields in the assignment block are displayed. 1.13.6 Subsequent assignment of transactions Use This release note is only relevant if upgrading from SAP CRM 5.2. You can now assign subsequent transactions to transactions from header to item level and vice versa. You do this under the Transaction History assignment block, by choosing the Subsequent Assignment pushbutton. You can assign all transactions subsequently which have been defined in the object releationship profile ______________________________________________________________ SAP AG 122 SAP-System ______________________________________________________________ under Define Object Reference Profile. You can also assign multiple transactions subsequently, and you can delete assignments. Additionally, the Business Add-In (CRM_DOCFLOW_FILTER) is available if you want specific transactions to appear for subsequent assignment in the Transaction History assignment block. You can access this Business Add-In via transaction SE18. 1.13.7 Business Object Layer and Web Services (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.2. The key structure CRMST_DOCFLOW_LOG_KEY of the business object layer (BOL) node BTDocFlow has been enhanced. This affects Web services that have been generated using the Web services tool. Effects on Existing Data If the Web service has the status Active you can regenerate the structures. If the status is already set to Productive you need to copy the existing Web service to create a new version. 1.13.8 CRM-BTX-LEA Lead Management 1.13.8.1 Duplicate Check for Leads (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You use the duplicate check for leads to identify lead duplicates when a new lead is created (but not yet saved) or an existing lead is changed. Duplicate leads can then be merged either automatically or manually to reduce the cost and effort of processing them. ______________________________________________________________ SAP AG 123 SAP-System ______________________________________________________________ Lead deduplication is channel-independent, and can be triggered manually or automatically when saving data. An optional workflow informs the lead owner about merges. This workflow is defined via the partner function. Standard settings are Employee Responsible, Sales Representative, and Employee Responsible at Partner. Effects on Customizing To enable the duplicate check for leads, you have made the necessary settings in Customizing for Customer Relationship Management, by choosing Transactions -> Settings for Leads -> Assign Classes for Deduplication. 1.13.9 CRM-BTX-OPP Opportunities 1.13.9.1 Opportunity Assessment Determination Based on Expected Sales (New) Use This release note is only relevant if upgrading from SAP CRM 5.2 . You can now qualify an opportunity by timely completion of an assessment (questionnaire). The system prompts the user with an assessment when either the expected sales volume, or the expected total value, crosses a threshold value. The threshold value is defined in Customizing. The expected sales volume is maintained at the opportunity header level. The expected total value is the sum of the expected sales values maintained at the opportunity item level. Effects on Customizing You define threshold value for either expected sales volume, or expected total value, and the assessment determination criteria in the Customizing under: 1. Customer Relationship Management -> Transactions -> Settings for Opportunities -> Sales Methodology -> Questionnaire for Opportinities -> Define Determination Criteria for Questionnaires 2. Customer Relationship Management -> Transactions -> Settings for Opportunities -> Sales Methodology -> Questionnaire for Opportinities -> Define Determination for Questionnaires ______________________________________________________________ SAP AG 124 SAP-System ______________________________________________________________ 1.13.9.2 Transfer Buying Center Between Opportunity and Account (New) Use This release note is only relevant if upgrading from SAP CRM 5.2. You can transfer the buying center from the account (to which the opportunity pertains) to the opportunity. In this case, the account buying center replaces any buying center you may have defined for the opportunity. When the related account has more than one buying center, the user can choose which buying center to transfer to the opportunity. When the buying center has been defined in the opportunity, you can save the buying center to the relevant account. The feature allows a two-way transfer of buying center between opportunity and account. The options are provided under More in the Contacts area of the opportunity overview page. Note: This feature is applicable for opportunities of type sales methodology. 1.13.9.3 Competitor Information for an Opportunity (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.2. You can maintain competitor information for opportunities in one of the following modes: o o At the opportunity header level (for the opportunity as a whole) At the opportunity item level (for opportunity products) For an opportunity, you can also maintain the following competitor information: o o o Competitor products relevant to the opportunity The expected sales volume (with currency) for each competitor The probability of the competitor succeeding ______________________________________________________________ SAP AG 125 SAP-System ______________________________________________________________ o o The strength and weakness of each competitor The successful competitor(s) when the opportunity is lost Input help from master data is available for competitor and competitor product information. The competitor product information, however, need not be a part of master data. When applicale, input help and hyperlinks to access competitor and product master data are available. Effects on Customizing In Customizing, you can define whether opportunity competitor information will be maintained at the opportunity header level, or at the opportunity item level. This setting is done in Customizing for CRM by choosing Customer Relationship Management -> Transactions -> Basic Settings -> Define Transaction Types . You define this in the Competitor area of the Customizing header dialog box. for the selected transaction type. 1.13.9.4 Enhancements to Opportunities in CRM (Changed) Use This release note is only relevant if upgrading from SAP CRM 5.0. The following functions have been enhanced: Opportunity hierarchies You can link a subopportunity directly to a product in the Master Opportunity, rather than to the opportunity itself. You can also link a new subopportunity directly to a product, rather than directly to the Master Opportunity itself. Document flow on item level The Transaction History assignment block has been incorporated into the subproduct overview page. You can create assignments of existing transactions, and the Transaction History is automatically updated when the opportunity is a follow-up transaction. CPro link You can create a row in the Transaction History assignment block to search and create a link directly to a CProject project and launch the CProject application. ______________________________________________________________ SAP AG 126 SAP-System ______________________________________________________________ 1.13.10 CRM-BTX-SLO Sales Transaction 1.13.10.1 Use of Product Proposals (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use additional product proposal types to boost sales of certain products in the sales order. These will enhance your scope in sales negotiations, as these product proposals contain specific knowledge about the respective customers. To begin with, you can determine product proposals based on previous sales orders, that is, the transaction history for the respective customers. You can then use a previous sales order as a template for a new sales order. You can also support follow-up actions by using information on which marketing projects (campaigns or trade promotions) the customer is involved in and directly recommend appropriate products to them. Previously, with the exception of top n product lists, you could only display product proposals that were directly related to the respective product, such as accessories, cross-selling products, up-selling products, and down-selling products. Further product proposals can be determined with this new function which more efficiently supports the sale of certain products to the respective customers. The additional product proposals can be determined based on the following: Transaction history (Previous sales orders from the respective customers for a certain time period) This type of product proposal has a header-data-based- and immediate display, depending on the settings made in your company. In the header-data-based display, the individual header data from the sales order is displayed. You can view this data and select the corresponding sales orders. The products are also determined from the selected data. In the immediate display, all products from the selected sales orders are directly suggested for selection. These settings can be made in SAP CRM Customizing under Customer Relationship Management -> Transactions -> Settings for Sales Transactions -> Product Proposals in Quotation and Order -> General Settings for Product Proposals. Marketing projects (Campaigns and trade promotions) This type of product proposal also has a header-data-based display or an immediate display, depending on the settings made in your company. In the header-data-based display, the individual marketing projects are displayed in detail. You can view the marketing projects such as campaigns and trade promotions and select those that suit you. In addition, all products from the selected marketing projects are proposed for selection. In the immediate display, all products from the relevant marketing projects are directly proposed for selection. You can make these settings in SAP CRM Customizing under Customer Relationship Management -> Transactions -> Settings for Sales Transactions -> Product Proposals in Quotation and Order ->General Settings for Product Proposals - ______________________________________________________________ SAP AG 127 SAP-System ______________________________________________________________ Note: These new product proposal types are not supported in: Interaction Center WebClient Interaction Center WinClient CRM E-Commerce Display of transaction history You can also set the application so that the transaction history is displayed for every proposed product and so that order data is displayed for a certain period of time for the respective customers. In this way, you will get information on when and in which sales order the product was already ordered by the customer and be able to factor the customer's previous buying pattern into your sales strategy. You can make these settings in SAP CRM Customizing under Customer Relationship Management -> Transactions -> Settings for Sales Transactions - > Product Proposals in Quotation and Order -> Transaction History Pricing The calculated product price is displayed for the product proposal in the simulation area. The following options are available with SAP CRM 5.1 for pricing. You can turn off the pricing completely. The prices can be transmitted from net price lists. The system will execute a complete price determination only at the point when the product is transferred to the sales order, so the price displayed with the product proposal can differ from the final price. Calculation of the current price using the Internet Pricing and Configurator (IPC). Campaign determination is also included. - Availability Check An availability check is carried out and a quantity is proposed for the product. The result of this check is likewise displayed with the product proposal. This is not a "real" availability check because, for instance, no product reservation takes place. You can only carry out a "real" availability check when the products are applied to the sales order. Note: Product proposals that are based on a partner/product range are not addressed in this function. Effects on Customizing You have determined top n products and cross-/up-/down-selling rules in the SAP Easy Access Menu under Marketing -> Product Proposals. You have entered the product as an accessory in product maintenance under Relationships. You have set the product proposals in sales transactions in SAP CRM Customizing under Customer ______________________________________________________________ SAP AG 128 SAP-System ______________________________________________________________ Relationship Management -> Transactions -> Settings for Sales Transactions -> Product Proposals in Quotation and Order. 1.13.10.2 Use of Provider Orders (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now create and edit provider orders (business transaction category BUS2000265). The provider order is a special sales order with which you can sell products and services within the provider industry. It supports the sale of specific products and services, in particular the way they are combined and offered in the telecommunications industry or by electricity suppliers. The provider order is closely connected with the provider contract, which is automatically created from the provider order. With every change process , for example contract extension, that can only be carried out through the provider contract, a provider order is created. When you release the provider order, the provider contract is updated with the changes. The entry of the provider order can take place by using the dealer portal as well as the Interaction Center. The following functions are available in the provider order: Search for customers and provider orders You can search for provider orders that have already been entered. You can then select these orders for further editing, as far as the order is modifiable. You can also create new customers from the search screen. Order entry and entry of additional technical data As well as customer and product data, you can enter additional information in the provider order that is necessary for the sale and consequent operation of the service. You can determine the additional information with which the provider order should be entered yourself and adjust it to the requirements of your enterprise. In the telecommunications industry, technical connection data such as telephone number or SIM card number is entered in the provider order. The entry of such data in, for example, the dealer portal, enables a simple search for provider orders by telephone number. Entry of product data - New product model using interlinkage types In a provider order in particular, you can use products and services that are modeled for the specific sales process of provider services. The following interlinkage types are available to you for this product modeling: Sales components Dependent components - - Rate plan combinations The new interlinkage types supplement the previous options for product modeling, which is based on, among other things, the relatively complex modeling of configurable products and thereby offers enhanced functions for product determination within order and contract management. The interlinkage types are defined in the processing of the respective products and you can assign corresponding components. In this way, products such as activation charges, accessories, incentives, and so on can be combined in an enhanced product model into a service product and in every order ______________________________________________________________ SAP AG 129 SAP-System ______________________________________________________________ and contract process, automatically included in the corresponding documents. You can thereby combine flexible packages and yet devise well-defined product sets. The simplest form of this new product model is a package, which is sold as a service and can, for example, consist of a service contract (rate plan), for which required hardware and extras are added for strategic marketing reasons. This product set is implemented by using the interlinkage type Sales Components. The package is only relevant in the process of order entry. In a provider contract, which results from a provider order created with the package, only package components are applied. As a rule, this is only the service contract (rate plan). You can influence the explosion of the package in the order entry by means of appropriate interlinkage type attributes. The interlinkage type Dependent Components facilitates the defining of product relationships by using attributes in which you can formulate conditions that you can then use to control the explosion of the products in the provider order. The product is created in the provider order only when all conditions are fulfilled. This interlinkage type is used, for example, for charges that accrue with contract changes for products in the provider order. You can also use the interlinkage type Rate Plan Combinations, in which case you are dealing with a fixed rate plan combination without further dependencies. You can offer a special price for rate plans when they are sold combined and you want to offer additional products in a package as incentives. The individual rate plans result in the provider contract with individual document items. The solution configurator processes the relationships and dependencies that are defined with these interlinkage types between the more loosely (in comparison to the product configuration) linked products in the background. It checks the conditions and releases the package components in the provider order only when the fixed conditions are fulfilled. The loose interlinkage of products in a package is chiefly significant for the distribution and further processing of the data contained inside and the information in the provider contract, which would not be possible in this way with product modeling using configurable products. Automatic creation of a provider contract When you sign and confirm a provider order, a provider contract is automatically created by the system based on the information from the provider order, into which all contract-relevant data from the provider order is copied. The provider order is closely connected with the provider contract. Changes to the provider contract can only be carried out by means of the provider orders. Further functions that are supported through the provider order: Ensuring integration in all subsequent systems Automation and coordination of the order across different systems Update and control of contract changes Basic functions that you also use in the sales order. These include: Pricing Product configuration Campaign determination ______________________________________________________________ SAP AG 130 SAP-System ______________________________________________________________ See also Release Information: Provider Contracts (New) Status Management in Provider Order Maintenance (Enhanced) Automatic Creation of Provider Orders for Lock/Unlock Services (New) Settlement of Recurring and One-Time Charges (Enhanced) 1.13.10.3 Automatic Creation of Provider Orders for Lock/Unlock Services (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. When your customer requests a lock for a service if, for example, they lose their cell phone or want to prevent a potential misuse of the service at their cost whilst on vacation, you can set a lock for this service. In the same way, you unlock the phone again and activate the service when the customer wants this service to be available again. You can perform the locking and unlocking of contract items in the provider contract as a change process. Particular services represent the locking and unlocking of contract items and they can be differentiated by lock statuses, which are defined in Customizing. Previously, you could only use this function in the Interaction Center WebClient. This function is independent of the user interface and can therefore be integrated by all user interfaces. In addition, you can charge your customers for the costs that are connected with locking and unlocking. These lock- and unlock prices can be calculated by using the lock reason and the contract item. Provider orders with corresponding order items and prices are automatically created for the individual lock- and unlock services. Effects on Customizing You perform the settings for this function in SAP CRM Customizing by choosing Customer Relationship Management -> Industry-Specific Solutions -> Telecommunications -> Lock Processing See also Release Information:Use of Provider Orders (New) ______________________________________________________________ SAP AG 131 SAP-System ______________________________________________________________ 1.13.10.4 Settlement of Recurring and One-Time Fees (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. As a rule, a provider order contains periodically recurring fees as well as one-time fees. A provider order can contain a sales package that consists of a cell phone contract, for which monthly fees occur, and a cell phone, that is paid for once. These fees are displayed separately, on the user interface of the provider order at item level and in brief at header level, in different columns. This function was adjusted by using CRM standard functions and thereby offers more flexibility when settling periodically recurring fees. In this way you can, for instance, calculate the prices monthly but invoice the corresponding items with a different settlement frequency, only every two months, for example. The option to more flexibly execute settlements is realized by means of the billing plan and the basic function, date management. Effects on Customizing You can make the appropriate settings for the billing plan in SAP CRM Customizing under Customer Relationship Management -> Transactions -> Basic Settings -> Billing Plan. You can make the appropriate settings for the definition of duration types, date profiles and date rules in SAP CRM Customizing under Customer Relationship Management -> Basic Functions -> Date Management. The following description gives you an overview of SAP's standard and recommended Customizing for the function: Use the condition type 0PMR Assign the calculation rule M (Quantity - Monthly Price) to the condition type 0PMR Add the condition type 0PMR to the pricing procedure 0IST01 Use the item categories IST1 (recurring order items) and IST2 (recurring contract items). Use the item category group IST for item category determination Assign the item category group IST to the corresponding product in the product master data. Use the transaction types ISTO (provider order) and ISTC (provider contract) for provider transaction processing. Use the date profiles IST_HEADER, IST_CONTITEM and IST_ORDITEM to determine the dates. Assign the date profiles to the transaction types ISTO and ISTC. The date profiles contain the duration BILLFREQ with which you can decide on the frequency for billing plan settlement and which is determined monthly in the delivered Customizing. ______________________________________________________________ SAP AG 132 SAP-System ______________________________________________________________ - The duration BILLFREQ is contained in the date rule BILL009 (dynamic billing plan frequency) as a variable and must be assigned to the date profile. This date rule must also be assigned to the billing plan. Create a billing plan type and assign it to the transaction types ISTO and ISTC as well as to the item categories IST1 and IST2. - Note: When you use an external system for billing, you can stop the creation of billing request items for performance reasons. You can make the settings in SAP CRM Customizing under Customer Relationship Management -> Transactions -> Basic Settings -> Billing Plan. In the corresponding billing plan type, for example, IST-CI, Bill Cycle 01, in the group box Billing Plan-Explosion, set the indicator Do not generate billing request items. See also Release Note Use of Provider Orders (New) 1.13.10.5 Status Management in Provider Order Maintenance (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. Further system statuses are available for provider order maintenance. These statuses inform you of the processing status of the provider order items or provider contract items. You can control the subsequent processes in the maintenance of provider orders and contracts , that is, the distribution of data to external systems or change processes. Each status informs you at main- and subitem level that a certain status has occurred and determines which step may be executed next. Previously, statuses were only displayed at main item level. These statuses are now also available for subitems. At main item level, a higher-level status is displayed which is calculated depending on the status of the subitems. A higher-level status is always calculated for the different statuses of the individual subitems and gives information on the general activation process. Only one status is active at any one time. When a succeeding status is set, the previous status is deleted. The higher-level status is used for the processes in the provider order and contract so that you can determine the follow-up transactions allowed. Corresponding actions can only be executed when the provider sales transactions have a certain status. For example, when one of the subitems in the provider order receives the status "Activated", it means that the subitem is distributed to external systems. If only one of the subitems has the status "Activated", the main item receives the status "Activation of Main Item Started". The provider order can no longer be changed with this status. Further functions that are provided in status management: Error messages can be transferred from the external systems to the provider contract and written in the application log of the provider contract. This makes it possible for you to handle errors that occur and potentially re-execute the distribution of subitems independently of one another. ______________________________________________________________ SAP AG 133 SAP-System ______________________________________________________________ - Contract items can be distributed until the confirmed activation date, that is, messages with contract data can still be transferred for a certain time before the actual activation date. It is therefore possible to make changes until the first distribution process actually starts. You can create additional customer-specific statuses for confirmations from external systems with the Business Add-In CRMXIF_ISTSERVCONF_C. - See also Release Note Use of Provider Orders (New) 1.13.10.6 Abnormal Demand in Sales Order Items (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can classify items in a sales order as abnormal demand. If you classify them as abnormal demand, they will not be taken into account in forecasting. This function allows you to indicate that an unusually high or low demand in a sales order should be considered abnormal and needs to be ignored for future planning. You can also classify campaigns and trade promotions as abnormal demand. If you classify them as such, all sales order items referenced to this marketing program will be classified as abnormal demand, too. This function is only available if the system configuration for service parts management is active. 1.13.10.7 Assignment of Internal Orders to Sales Orders (New) Use ______________________________________________________________ SAP AG 134 SAP-System ______________________________________________________________ This release note is only relevant if upgrading from SAP CRM 5.0. You can assign an internal order, which exists in SAP ERP, to a sales order. If you do so, the costs and revenues resulting from a sales order are not booked into mass controlling but to this internal order instead. This function is only available if the system configuration for service parts management is active. 1.13.10.8 Integration of Letters of Credit in the Sales Order (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can integrate a letter of credit (LoC) in the sales order and thereby restrict financial risks in global retail. You manually enter the letter of credit directly in the sales order. You can display all permitted LoCs using input help and select them as appropriate. You also have the option of displaying all the sales orders that have invalid letters of credit assigned to them, in the Credit Analyst Workbench. In the sales order, you can assign letters of credit at header level. When selecting the LoC, you should use the input help, as the possible selections in the input help are based on a logic that only proposes permitted letters of credit. The system checks if the following is valid: Current sold-to party Payment terms Incoterms Sales organization After selecting the letter of credit, the system also checks if it is permitted for the current order value. If the check is negative, an internal status is set that prevents further follow-up transactions such as billing and delivery. The system also deletes all confirmations calculated by SAP APO. If the check is positive, SAP ECC creates an unchecked delivery. SAP ECC transfers the assigned letter of credit IDs to Extended Warehouse Management (EWM) in SAP SCM. You can then no longer change the LoC for partially- and completely-delivered order items. In EWM it is possible to ensure that orders with different LoCs are not packed together. This can be implemented by using a BAdI. ______________________________________________________________ SAP AG 135 SAP-System ______________________________________________________________ Effects on Customizing You use SAP Global Trade Services (SAP GTS). The system configuration for service parts management has been activated. For more information about this, see the SAP Implementation Guide (IMG) for Customer Relationship Management at Activate System Configuration for Service Parts Management The indicator GTS Relevance must be set for the transaction type. You can make these settings in SAP CRM Customizing under Define Transaction Types. The indicator GTS Relevance must be set for the delivery and billing relevant item category. You can make these settings in SAP CRM Customizing under Define Item Categories. - 1.13.10.9 Mass Changes at Header Level (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. In addition to mass changes at item level, it is possible to make mass changes at header level . You can choose whether you want to make a mass change at item level or at header level. Therefore, this function reduces the amount of effort usually associated with making several data changes at header level, for example changing the sold-to party. Similarly to mass changes at item level, you can execute mass changes at header level online or in the background. In background mode, you start off in online mode and switch to background processing to make the changes. Effects on Customizing You have assigned the fields for mass changes according to your requirements in Customizing. For more information, see the Implementation Guide (IMG) for SAP CRM under Assign Fields for Mass Changes. ______________________________________________________________ SAP AG 136 SAP-System ______________________________________________________________ 1.13.10.10 Maximum Number of Locations in Availability Check (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can restrict the number of locations from which a sales order item is delivered. For example, if you enter '3', the availability check returns a maximum of three locations from which the item is being delivered. This function is only available if the system configuration for service parts management is active. 1.13.10.11 Determine Maximum Partial Deliveries (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can determine the maximum number of partial deliveries for each order item and so limit the subdivision of an order item to a defined number of deliveries. The system creates schedule lines for each order item with the respective quantity and delivery date and therefore creates the partial deliveries for your customers. The number of schedule lines or deliveries created by the system will not exceed the maximum number you have determined. You can either set the maximum number of partial deliveries manually in the sales order, or in the business partner master data. When creating the order item, the system transfers the value determined in the business partner master record to the sales order. SAP APO calculates the value for the maximum number of confirmations. It does this by using the maximum number of partial deliveries and previously existing deliveries. When you trigger an ATP check in the sales order, the maximum number of deliveries and confirmations is transferred to SAP APO. This ensures that when SAP APO returns confirmations to the order item from each of the locations from which the product can be delivered, it does not exceed the maximum number of partial deliveries that you have defined. When you save the sales order, the system creates an unchecked delivery for each individual confirmed schedule line. ______________________________________________________________ SAP AG 137 SAP-System ______________________________________________________________ Effects on Customizing The system configuration for service parts management is activated. You can find further information in the SAP Implementation Guide (IMG) under Activate System Configuration for Service Parts Management. SAP SCM Extended Warehouse Management is activated. You use the availability check with SAP SCM Advanced Planning and Optimization (SAP APO). - 1.13.10.12 Use of Objects in Service Recall Orders (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. In regular service recall processing, you can use objects only once. This ensures that one fixed list of service parts and the maximum permitted quantity of these parts are made available to the customer for each object. A special authorization now allows you to use objects in service recall orders multiple times. If you try to re-use an object in the service recall order, you get an error message. If you have special authorization, you can override the error message by setting a special user status created for this function. The error message is then overridden and the service recall order can be saved without errors. This function gives you the advantage of being able to re-use the same product service letter within a recall action. For example, if some service parts sent in exchange were again delivered to the customer in a damaged state, and these objects must be replaced once more. Effects on Customizing You have made the following settings in Customizing for Customer Relationship Management : You have created a subject profile with category Y Individual Object (Sales Order) for the use of reference objects and entry of objects' product IDs in the service recall order. You can find further information in the SAP CRM Implementation Guide (IMG) under Define Subject Profiles. You have created a custom transaction type for service recall processing, to which you have assigned this subject profile under External Reference Object. You can find further information in the SAP CRM Implementation Guide (IMG) under Define Transaction Types. You have defined an authorization key for the definition of a user status. You make this setting in SAP CRM Customizing under Customer Relationship Management -> Transactions -> Basic Settings -> Status Management -> Define Status Authorization Keys. - - ______________________________________________________________ SAP AG 138 SAP-System ______________________________________________________________ - You have created a status profile. Assign the defined authorization key to the user status. You can find further information in the SAP CRM Implementation Guide (IMG) under Customer Relationship Management -> Transactions -> Basic Settings -> Status Management -> Change Status Profile for User Status. Note: When defining the status profile ensure, for the definition of the user status, that you assign the value Duplicate VIN Check (technical name: DUVI) to the Business Transaction and set the indicator Prohibited. This prevents the execution of this business transaction. Use the status profile CRMRECOR (Text: CRM Recall Order), available in the standard system, as a template for this. Assign this status profile to the transaction type that you want to use. The user who sets this user status must have authorization for the authorization object B_USERSTAT. This authorization object has the attribute BERSL = <authorization key>. If you use the status profile CRMRECOR, delivered as standard by SAP, assign BERSL = ORIDEVIN. - 1.13.10.13 Third-Party Order Processing with Consolidation (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can define, within the sales order, that the customer is supplied from a consolidation location. Third-party order processing with consolidation is a variant of regular third-party processing. In the case of processing with consolidation, the external supplier does not directly take over the delivery of the goods to the customer, but instead delivers the goods to a consolidation location. The consolidation location is the place from which a consolidated delivery to the customer takes place. In the consolidation location, deliveries are merged from various locations. The customer is supplied only from the consolidation location. In this way, all confirmed products are delivered from external suppliers to the consolidation location and then from there to the customer. This means that in the case of third-party order processing with consolidation, the ship-to location does not receive the goods directly, but rather the goods are first consolidated in another location. Reasons for this can be that the ship-to location is in another country, or that the goods must be consolidated for legal reasons. In SAP APO, the consolidation location is defined with the type Plant, and can therefore be viewed as an internal location. Characteristics in Comparison with Regular Third-Party Order Processing: The order triggered by SAP CRM is an ordinary warehouse order and not, as in regular third-party order processing, a third-party purchase order. The stock segment is sales order stock, however. The process includes the delivery of products from the consolidation location to the customer. The order confirmations do not directly update the confirmed schedule lines in the sales order, because the confirmed dates relate to the delivery to the consolidation location but are transferred to SAP APO. SAP APO triggers a rescheduling and then updates the sales order with the newly calculated dates. ______________________________________________________________ SAP AG 139 SAP-System ______________________________________________________________ - The delivered quantities and the delivery status in the sales order are not updated using the shipping notification of the external supplier. They are updated by the delivery from the consolidation location instead. The goods receipt for the order updates the sales order stock in the consolidation location. Effects on Customizing The system configuration for service parts management is activated. You can find further information in the SAP Implementation Guide (IMG) under Activate System Configuration for Service Parts Management. SAP SCM Extended Warehouse Management is activated. You use the availability check with SAP APO. The consolidation location can be calculated using the rules-based availability check (rules-based ATP) in SAP Advanced Planning and Optimization (SAP APO). In this case, a rule must be determined for the calculation of a consolidation location. You can find further information in the documentation for these fields; in the SAP Easy Access Menu for SAP Supply Chain Management, choose Advanced Planning and Optimization -> Master Data -> Rule Maintenance -> Integrated Rule Maintenance. You have created the consolidation location as a business partner in the business partner master data. You have also set up the customizing of the transaction types, item categories, and the required copying control in SAP ECC. This is because unchecked deliveries are created in SAP ECC. In regular third-party order processing, no unchecked deliveries are created in SAP ECC, so this customizing is not necessary there. - - 1.13.10.14 Third-Party Order Processing with Supersession (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. In third-party order processing, you can, with certain prerequisites, allow external suppliers to replace one product with another if it is not available in their stock. It is essential, in service parts management, to be able to substitute products in order to react to continuous changes in product design, -form or -function. For example, it must be possible to substitute obsolete service parts with new versions of the same part. ______________________________________________________________ SAP AG 140 SAP-System ______________________________________________________________ Effects on Customizing The system configuration for service parts management is activated. You can find further information in the SAP Implementation Guide (IMG) under Activate System Configuration for Service Parts Management. SAP SCM Extended Warehouse Management is activated You use the availability check with SAP SCM Advanced Planning and Optimization (SAP APO). You must have created an interchangeability group in SAP APO for the product that the external supplier can replace with another product. The product, substitute product, and the quantity are all defined in the interchangeability group. Both SAP ECC and SAP APO use these definitions to check, when creating the sales order in SAP CRM, whether the external supplier is authorized to substitute the product with another. In the SAP Easy Access Menu for SAP SCM, select Advanced Planning and Optimization -> Master Data -> Application-Specific Master Data -> Product and Location Interchangeability -> Maintain Interchangeability Group (Transaction /INCMD/UI). You can find more information about interchangeability groups in the SAP Library for SAP SCM under SAP Advanced Planning and Optimization (SAP APO) -> Master Data -> Application-Specific Master Data -> Master Data for Product and Location Interchangeability. - 1.13.10.15 Using Grid Products in the Sales Order (New for SP02) Use This release note is relevant if upgrading from SAP CRM 5.2. You can process grid products in the sales order. When you enter a grid product in the sales order, the Grid assignment block is available for processing grid products. This replaces the Configuration assignment block for conventional configurable products. In a grid, characteristics combinations such as size and color are displayed, into which you enter the required order quantities. The system automatically finds the appropriate product variants, for which the system creates corresponding subitems. This not only facilitates the processing of order items for easily configurable products, but also avoids the complex handling for configurable products, which would unnecessarily burden the system. This way, you can quickly and easily process the sales order and automatically create subitems for the many product variants of a grid product. Effects on Customizing ______________________________________________________________ SAP AG 141 SAP-System ______________________________________________________________ The product must be available in the SAP CRM product master data as a grid product, that is the configuration type of the product must be set to the value G in table COMM_PRODUCT. 1.13.11 CRM-BTX-ERP BSP for ERP Sales Order 1.13.11.1 Creating and Changing ERP Sales Transactions in SAP CRM (New) Use This release note is only relevant if upgrading from SAP CRM 5.2. You can directly create or change ERP sales transactions such as ERP quotations, ERP sales orders, or ERP quantity contracts, in SAP CRM. You can also create follow-up transactions, for example, directly creating an ERP quotation from a CRM opportunity in SAP ERP. This means that you can perform your pre-sales activities in SAP CRM and then process the follow-up transactions, like quotation creation and sales order processing, in SAP ERP, without leaving SAP CRM. You can thereby execute your quotation- and order processing in SAP ERP and also use SAP CRM in an integrated manner. This function particularly supports sales employees who work mostly in SAP CRM and do not use SAP ERP, thereby allowing the user to utilize a single user interface to work with both SAP CRM and SAP ERP. For example, sales assistants can use this functionality to create lean orders directly in SAP ERP. Effects on Customizing The direct creation and change of an SAP ERP sales order from SAP CRM is only supported if you have carried out the following Customizing. You have assigned a profile for the ERP sales transaction. Using this profile, you define which ERP sales transactions are permitted for processing, that is, which ones you can create and change. You make the settings for this in SAP CRM Customizing by choosing Customer Relationship Management -> Transactions -> Settings for Sales Transactions -> Define Profile for ERP Sales Transactions. The profile SALESPRO is available for this purpose as standard, but it is delivered without input of the RFC destination. Therefore, you must still assign the RFC destination for SAP ERP to this profile. Prerequisite: You have defined an RFC destination (by choosing Customer Relationship Management -> CRM Middleware and Related Components -> Communication Setup -> Define RFC Destinations in the SAP Implementation Guide (IMG) or using transaction SM59). You have assigned this profile to the business role SALESPRO. You make this setting in SAP CRM Customizing by choosing Customer Relationship Management -> Business Roles -> Define Business Role. ______________________________________________________________ SAP AG 142 SAP-System ______________________________________________________________ In the standard customizing the group links for calling up the ERP sales transactions are not visible. To make them visible in the work area of the CRM WebClient UI, you have made the necessary settings.in SAP CRM Customizing by choosing Customer Relationship Management -> Business Roles ->Define Business Role. Select the SALESPRO role and choose the Visible Work Center Group Links folder. Set the Visible indicator for the following group IDs: SLS-ERC-CR SLS-ERC-SR SLS-ERP-CR SLS-ERP-CR SLS-ERP-SR SLS-ERP-SR Set the In Menu indicator for the following group IDs: SLS-ERP-SR SLS-ERP-SR Save your entries. For follow-up sales transactions you must make additional settings. For example, creation of an ERP quotation from an opportunity is only supported if you have defined a cross-system copy control of transaction types. You make the settings required for this in the SAP Implementation Guide (IMG) under Customer Relationship Management -> Transactions -> Settings for Opportunities -> Cross-system Copy Control for Opportunity and SAP-ECC Quotation (Cross-System Copying of Transaction Types andCross-System Copying of Item Categories). 1.13.12 CRM-BTX-SVO 1.13.12.1 CRM-BTX-SVO-QUT Service Processes Service Inquiries / Quotations 1.13.12.1.1 Packages in Service Order Quotations (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can include packages in a service order quotation item. When you select a package, the package components are displayed in the items in a hierarchical structure (with the sub-components as subitems). You can deselect components that are not required. ______________________________________________________________ SAP AG 143 SAP-System ______________________________________________________________ Effects on Customizing The standard transaction type SRVP (Package Quotation) is available. To enable packages to be included in items and their subitems, you need to select the Package Explosion indicator in both of the following activities in Customizing for Customer Relationship Management: Transactions -> Basic Settings -> Define Transaction Types and Define Item Categories. See also For more information about packages, see the SAP Library under SAP Customer Relationship Management -> Components and Functions -> Master Data -> Products -> Functions -> Packages and Products with Dependent Components. 1.13.13 CRM-BTX-SCO Service Confirmation 1.13.13.1 Serial Number Entry in Confirmations (New) Use As of SAP CRM 5.0, you can create serial numbers for service parts in service confirmations. The serial numbers that are entered can be validated. It is possible to enter serial numbers in the following SAP Customer Relationship Management (SAP CRM) channels: SAP GUI for Windows, Interaction Center (IC) WinClient, mobile service, and the People-Centric UI (PC-UI). You can define how the serial numbers that were entered should be checked. To do so, you can either define it in the product master in the field for serial number processing, or you can replicate this information from SAP ERP Central Component (SAP ECC) to SAP Customer Relationship Management (SAP CRM). In the standard system, the following checks take place after the serial numbers are entered: When entering a product, the system checks whether serial number entry is optional or mandatory. After the serial number is entered, the system ensures that the product is not changed any more. Quantity check: The system validates the number of entered serial numbers by comparing it to the item quantity. Check for accuracy of the serial numbers: Depending on the field for serial number processing, this check is either run against the individual object in SAP CRM, against SAP ECC, or a combination of both. After the service confirmation is saved (status completed) the system transfers the service confirmation, along with the service parts, quantities, and corresponding serial numbers, to SAP ECC. ______________________________________________________________ SAP AG 144 SAP-System ______________________________________________________________ Effects on Customizing You can tailor the serial number checks to your needs by using BAdI: Check Reference Objects. See also For more information about serial number entry in confirmations, see the SAP Library (help.sap.com) under SAP Customer Relationship Management -> Components and Functions -> Service -> Service Confirmations -> Creation of Service Confirmations -> Serial Number Entry in Service Confirmations. 1.13.14 CRM-BTX-BRQ Billing Request 1.13.14.1 Transfer of Accounting Indicator to Billing (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The accounting indicator field in service transactions can be transferred to billing, where it is used for pricing and account determination. Effects on Customizing To enable transfer of the accounting indicator, activate one of the following features in the IMG under Customer Relationship Management -> Billing -> Configure Application: Integration with Contract Accounting Enhanced Attributes for Pricing ______________________________________________________________ SAP AG 145 SAP-System ______________________________________________________________ 1.13.15 CRM-BTX-COM Complaints / Returns / In-House Repair 1.13.15.1 Use of Complaints and Returns to Update Sales Contracts (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. If the customer (dealer) creates a complaint or return, depending on the Customizing settings, it is possible for the system to find a sales contract and update the values for Released Quantity and Released Value. This occurs as follows: If there is a return, the contract values are updated depending on the quantity of the returns authorization item. The sales contract is assigned to the main item and the returns request item. If there are no returns, such as in the case of an underdelivery or overdelivery without a returns request, the contract values are updated after the invoice correction item is created. The sales contract is assigned to the main item. This ensures that the customer gets the price that was agreed upon in the contract for the exact quantity or value in the contract. In addition, if the price cannot be determined using a billing document as the preceding transaction, the price is determined in this contract. This is the case for complaints and returns that were not created with reference to a billing document, such as surplus returns or rapid returns. The price is the basis for the invoice correction. If you create a complaint or return without reference to a billing document, the system cannot determine a sales order or a sales contract. In this case, for each returns request item, the system searches for contract items with the criteria customer (dealer), product, and sales organization. In this search, the fulfilment of the contract, the status, the contract duration, and the returns request item's creation date play the following roles: The system searches for contract items that are not yet fulfilled, that do not have status Completed, and whose contract duration has not yet expired. The system searches for contract items whose contract duration expired before the creation date of the returns request item, but were valid at least one day within the time period that you defined in Customizing. If you make the appropriate settings in Customizing, the system searches for contract items that have status Completed. - Assignment block Release History is available in the sales contract, at both header and item level. In this assignment block, you can see the release list with the corresponding sales orders as well as the corresponding complaints and returns. ______________________________________________________________ SAP AG 146 SAP-System ______________________________________________________________ Effects on Customizing Use the IMG activity Define Copying Control for Item Categories to define the copying control for copying conditions from sales contracts to complaints and returns. To update sales contracts, you must make the following settings in the IMG activity Define Transaction Types: Define that when a complaint or return is created, the system runs contract determination. To do so, in the General section of the screen, in the Contract Determ. field, select an appropriate value for contract determination, such as Only at Item Level: Assign Immediately if Unique. Specify that a sales contract should be found when a returns request item is created in a return transaction or a complaint transaction without reference to an invoice. To do so, in the Customizing Header for business transaction category Complaints, select value Sales Contract in the Determination field. This selection makes two new fields appear on the screen, in which you can make the following settings: Duration (Days): Define a time interval before the creation date of the returns request item. The system searches for contract items that were valid on at least one day in this time interval. Completed Sales Con.: Define whether contract items with status Completed should be found. - See also For information about complaints and returns, see SAP Library under SAP Customer Relationship Management -> Components and Functions -> Service -> Complaints and Returns. 1.13.15.2 Complaint with reference to trade promotion (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Within the context of complaints processing, you can now create the new transaction Complaint with reference to trade promotion. This scenario is called Complaint-Based Marketing Program. You can create complaints with reference to a trade promotion in the CRM WebClient UI, in the dealer portal or by using EDI. You create a complaint with reference to a trade promotion in the following case: You ordered a product and realize afterwards that the same product was sold at a lower price in connection with a trade promotion. The complaint results in the system creating a credit memo for the original amount and a debit memo based on the product price that is valid for the trade promotion. Effects on Existing Data The trade promotion must be marked for this scenario. If you want to use an existing trade promotion, in the Usage Type field, you must select value Complaint-Based Marketing Program. ______________________________________________________________ SAP AG 147 SAP-System ______________________________________________________________ If you want to use an existing trade promotion type for this scenario, in the implementation guide (IMG) activity Define Types/Objectives/Tactics, you must assign the corresponding Usage Type to the trade promotion type (Campaign Type). Effects on Customizing In Customizing for Customer Relationship Management, you must make the following settings: Use the IMG activity Define Transaction Types to define a transaction type for Complaints with reference to trade promotion. Use the transaction type CLRP - Complaint with billing reference in the standard delivery as a template to create a new transaction type. All required settings are available for this transaction type. Set the Creation with Ref. Possible indicator. Define the associated item category for complaints with reference to trade promotion. The standard system contains the item category CLBM - Complaint w/Ref. to Trade Promotion. If you want to create your own item category, use the IMG activity Define Item Categories. Assign business object types to the transaction types. The business object type is CBMP - Complaint-Based Marketing Programs. For assignment, use the IMG activity Assign Business Object Types to Transaction Types. In the standard system, business object type CBMP is for the transaction type for complaints with reference to a trade promotion. A trade promotion is defined as the preceding object for the complaint transaction and the data is copied from the trade promotion into the complaint transaction. If you want to change the preceding reference to the trade promotion, you must create your own implementation using Business Add-In: Create Complaint with Reference to External Transaction. Define an action profile for the item category with two action definitions: one for credit memo and one for debit memo. The standard delivery contains the following action profile and actions: Technical Name of Action Profile Description of Action Profile Action Definition Description COMPL_MKT_PRG Complaint-Based Marketing Program COMPL_MKT_PRG_CREDIT Complaint-Based Marketing Program - Credit COMPL_MKT_PRG_DEBIT Complaint-Based Marketing Program - Debit If you want to define your own action profiles and actions, use the IMG activity Define Action Profiles and Actions. Assign the action profile COMPL_MKT_PRG to the item category CLBM. Use the IMG activity Assign Action Profile to the Item Category. Define the usage type. Use the IMG activity Define Usage Type. Assign marketing usage types to transaction types. Use the IMG activity Assign Marketing Usage Types to Transaction Types. - - - ______________________________________________________________ SAP AG 148 SAP-System ______________________________________________________________ - Assign the usage type to the trade promotion type (campaign type). Use the IMG activity Define Types/Objectives/Tactics. See also For information about complaints, see SAP Library under SAP Customer Relationship Management -> Components and Functions -> Service -> Complaints and Returns . 1.13.15.3 Exchange Group for Used Part Returns (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now use exchange groups when you create a used part returns request item in the following context: Customers (dealers) pay a deposit when they buy an exchange part. When they pay the deposit amount, customers receive an entitlement for deposit refund when they return the part to the manufacturer as a used part. The deposit amount is determined using entitlement management. When you create a used part returns request, you can enter the following alternative IDs in the Product ID field: Product ID of the used part ID of the exchange group, for instance, if you do not know the product ID Product ID of the exchange group used part that is assigned to the exchange group In entitlement management, the appropriate exchange group is determined using the product in the request item. Then, the system uses the product and the exchange group to search for valid entitlements for deposit refund. Technically, the exchange group is a product category with a 1:1 relation to an exchange group used part (product master record). The exchange group used part is necessary because a product is required for the logistical subsequent process. At the same time, the relationship between the exchange group and the exchange group used part is an alternative ID of type EXGRP, which can be used for entering the request item in the Product ID field. The ID of the exchange group is displayed. When an exchange group is assigned to different used parts in the product master record in the assignment block Category, these used parts are bundled into a logical group. Effects on Customizing ______________________________________________________________ SAP AG 149 SAP-System ______________________________________________________________ To use the new functions, you must do the following in the Implementation Guide (IMG) under Customer Relationship Management: Use the IMG activity Assign Category Hierarchies to Applications to assign the Hierarchy ID, which you created for entitlement management and used part returns in the product master via Product Hierarchies, to the Application A2 (Entitlements). In the standard system, the ID Type EXGRP (Exchange Group) is defined as an alternative ID type. Check this assignment in the IMG activity Define ID Types. In the standard system, value EXGRP is assigned for Object Type BUS1178 as a Profile for Alternative IDs, and in the Sequence of ID Types view, value "1" is assigned to ID Type EXGRP. Check these assignments in the IMG activity Define Profiles. In the Product Determination section, value EXGRP is assigned to the transaction type for used part returns (UPRR) as the Profile for Altern. Identif.. If you have created your own transaction type for used part returns, you must use the IMG activity Define Transaction Types to make this assignment yourself. - - See also For more information about exchange groups, see SAP Library under SAP Customer Relationship Management -> Components and Functions -> Service -> Complaints and Returns -> Used Part Returns. 1.13.15.4 Complaints for External Products (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. In service parts management, you can now create complaints for external products. External products are parts that are not in your inventory and therefore have no product master data record in SAP Customer Relationship Management (SAP CRM). For more information about purchasing and billing external products, see release note Sale of External Products (New). As you can see from this release note, you trigger billing for both the customer (debit memo) as well as for the supplier (credit memo). In turn, complaints about these parts are also generated by you. The following types of complaints are supported: Complaint due to underdelivery Complaint due to overdelivery Complaint due to damage Complaint due to incorrect invoice A complaint can only be created with reference to a billing item that in turn has a reference to a sales order item. ______________________________________________________________ SAP AG 150 SAP-System ______________________________________________________________ The complaint triggers an invoice correction. Additionally, depending on the type of complaint, the parts can also be returned to the external supplier. Depending on the parameters that are defined, the parts may also be scrapped at the customer instead of returned. The invoice correction is made up of two transactions: In SAP CRM, an invoice correction for the customer In SAP ERP Central Component (SAP ECC), a correction of the supplier invoice for the supplier The invoice correction is not based on the actual returned quantity, since it is not known; it is instead based on the approved quantity. The differences to third-party order processing (TPOP) with products that have a product master, are as follows: After returns authorization, there is no inbound delivery created in SAP ECC. SAP Advanced Planning and Optimization (SAP APO) is not called to determine the location to which the part should be returned, because in this case, the products always go back to the external suppliers. Effects on Customizing The system configuration for service parts management is activated. Check this in the IMG activity Activate System Configuration for Service Parts Management. In IMG activity Define Transaction Types, for transaction type Complaint with Reference to Invoice, in section External Products, you have: Set the indicator External Products Allowed Selected an appropriate value for item category determination in field Item Category Group For External Products See also For information about complaints for external products, see SAP Library under SAP Customer Relationship Management -> Components and Functions -> Service -> Complaints and Returns -> Additional Functions for SPM for Complaints and Returns. ______________________________________________________________ SAP AG 151 SAP-System ______________________________________________________________ 1.13.15.5 Complaint Creation with Reference to a SAP ECC Handling Unit (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can create a complaint with reference to a billing document by using the handling unit (HU) ID to find the billing document via the SAP ERP Central Component (SAP ECC) delivery. You use the HU ID (external HU ID) when creating a complaint if your customer complains that an HU is damaged or is missing some parts, for example. The customer finds the HU ID on the packaging unit (such as the box it came in) and passes the HU ID on to you. When you use the HU ID to search for the billing document, all the items of the corresponding billing document appear in the result list. You select the appropriate billing document items and create the complaint. The basis for determining the quantity involved in a complaint is the HU quantity rather than the quantity in the billing document. After you create the complaint, in the Transaction History assignment block, you can use the HU ID to go to the SAP ECC packing transaction HUMO and view the HU data. 1.13.15.6 Inventory Adjustment for Complaints (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. To correct discrepancies between the invoice quantity and delivered quantity, you can use the POD Message action to trigger an inventory adjustment from a CRM complaint item that has a unique reference to a delivery item (determined via a sales order, billing document, or delivery). This inventory adjustment is made in SAP ERP Central Component (SAP ECC) or in SAP Supply Chain Management (SAP SCM). The proof of delivery (POD) message contains the reason for the shipping discrepancies, the outbound delivery quantity and the quantity received by the customer. For example, if 100 pieces were billed in the invoice, but only 80 were delivered, there is a difference in inventory that leads to a stock check in the issuing storage location in SAP ECC or SAP SCM. If the physical check results in a difference, an inventory adjustment is made. The POD Message action is available in the following cases: ______________________________________________________________ SAP AG 152 SAP-System ______________________________________________________________ - Underdelivery Overdelivery Incorrect delivery Effects on Customizing To update data to match the adjustment, use Business Add-In (BAdI) BAdI: Definition for Mapping of Proof of Delivery Message. For example, you can change the RFC destination or check data such as sold-to party or delivery quantity. In the standard system, you will find the action definition with action method COMPL_TRIGGER_POD in the action profile for Underdelivery, Overdelivery, and Incorrect Delivery. If you want to make changes, such as changing the schedule conditions, use activities Define Action Profiles and Actions and Define Conditions. - See also For more information about customizing in SAP ECC, see release note Proof of delivery linked to the Proof of Delivery node in SAP ECC under SAP Customizing Implementation Guide -> Logistics Execution -> Shipping -> Deliveries -> Proof of Delivery. For information about complaints and returns, see SAP Library under SAP Customer Relationship Management -> Components and Functions -> Service -> Complaints and Returns. - 1.13.16 CRM-BTX-CTR 1.13.16.1 CRM-BTX-CTR-CCO Contracts Sales Contract 1.13.16.1.1 Provider Contracts (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use the contract type provider contract. In a provider contract, you can map long-term agreements for services and products from telecommunications. The contract contains the following information: ______________________________________________________________ SAP AG 153 SAP-System ______________________________________________________________ - Contract duration Contract object (cell phone, for example) Services and rate plans Regular fees Creation of Provider Contracts You can create provider contracts by creating a provider order that also contains contract-relevant items. The provider contract is automatically created as a follow-up document to a provider order. The contractrelevant items are thereby copied from the order to the contract. You can create corresponding provider orders by using the dealer portal, the Interaction Center or a Web shop. You can make changes to existing contracts only by using the dealer portal or the Interaction Center. Changing Provider Contracts You can make the following changes in the provider contract: Contract extension You can also undo a planned contract extension. Changes to product configuration Product change This can relate to an object change (for example, a newer model) or a rate plan change (for example, a change from a standard rate plan to a weekend rate plan). SIM card exchange - In addition, you can still make the following changes in the Interaction Center: Locking and unlocking of connections Your customers can use this function when they want to prevent an unauthorized person from using their connection, for example, when they are on vacation. Number change Cancellation You can also undo cancellations that have already taken place. Master data changes Address change (after moving, for example) Explosion of a rate plan combination Many customers take advantage of competitive prices through combined rate plans (DSL and a cell phone rate plan, for example). If necessary, you can explode such rate plan combinations into their individual components, to end the validity period of one of these rate plans earlier, for instance. - In order to make changes to a provider contract you must create a change request (provider order). When you save this change request you can release these changes or reject them. You can also temporarily store the change request and release or reject the items later. All released changes are applied to the contract. The execution of the contract changes takes place through change processes, to which process types are assigned: ISTA - for business changes to the contract, for example extension, cancellation. ______________________________________________________________ SAP AG 154 SAP-System ______________________________________________________________ - ISTB - for changes to technical data such as SIM card or telephone number. ISTC - for the locking and unlocking of contracts. A custom change request is created for every process type. You can find further information in the release note Use of the Maintenance Framework for Business Transactions. The provider order contains the current products, rate plans and validity periods. You can reproduce the contract history by using the contract's change requests. When making changes to contracts, fees often occur (change fees) or existing rate plans change. You can find more information on the settlement of these one-time or recurring fees in the release note Settlement of Recurring and One-Time Charges. Effects on Customizing You can make the basic settings for provider contracts in transaction customizing under CRM -> Transactions -> Basic Settings. The following transaction types are available here for provider orders and contracts in the standard system: ISPR - Provider order using E-Commerce PRVO - Provider order for call center PRVR - Provider order for dealer PRVC - Provider contract In addition there are the item categories: TAP PRCN PRCP PRON PROP Sales item for packages Free provider contract item (for rate plan combinations) Provider contract item (for rate plans) Free provider order item (for rate plan combinations) Provider order item (for rate plans) The previously offered transaction type and item category ISTC - Telco Contract are also available. You can use the following item category groups for item category determination: LUMF- Structure below (for example, with packages) NORM - Sales item PRNP - Provider rate plan, not relevant for pricing PRRP - Provider rate plan PRSV - Provider fee ______________________________________________________________ SAP AG 155 SAP-System ______________________________________________________________ You can make specific settings for the provider contracts, for example, for the contract change processes and pricing for contract changes, in CRM Customizing under Transactions -> Settings for Provider Contracts. See also Provider Orders Use of Maintenance Framework for Business Transactions Settlement of Recurring and One-Time Charges 1.13.16.2 CRM-BTX-CTR-SCO Service Contract 1.13.16.2.1 Provider Contracts (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use the contract type provider contract. In a provider contract, you can map long-term agreements for services and products from telecommunications. The contract contains the following information: Contract duration Contract object (cell phone, for example) Services and rate plans Regular fees Creation of Provider Contracts You can create provider contracts by creating a provider order that also contains contract-relevant items. The provider contract is automatically created as a follow-up document to a provider order. The contractrelevant items are thereby copied from the order to the contract. You can create corresponding provider orders by using the dealer portal, the Interaction Center or a Web shop. You can make changes to existing contracts only by using the dealer portal or the Interaction Center. Changing Provider Contracts You can make the following changes in the provider contract: Contract extension You can also undo a planned contract extension. Changes to product configuration Product change This can relate to an object change (for example, a newer model) or a rate plan change (for example, ______________________________________________________________ SAP AG 156 SAP-System ______________________________________________________________ a change from a standard rate plan to a weekend rate plan). SIM card exchange In addition, you can still make the following changes in the Interaction Center: Locking and unlocking of connections Your customers can use this function when they want to prevent an unauthorized person from using their connection, for example, when they are on vacation. Number change Cancellation You can also undo cancellations that have already taken place. Master data changes Address change (after moving, for example) Explosion of a rate plan combination Many customers take advantage of competitive prices through combined rate plans (DSL and a cell phone rate plan, for example). If necessary, you can explode such rate plan combinations into their individual components, to end the validity period of one of these rate plans earlier, for instance. - In order to make changes to a provider contract you must create a change request (provider order). When you save this change request you can release these changes or reject them. You can also temporarily store the change request and release or reject the items later. All released changes are applied to the contract. The execution of the contract changes takes place through change processes, to which process types are assigned: ISTA - for business changes to the contract, for example extension, cancellation. ISTB - for changes to technical data such as SIM card or telephone number. ISTC - for the locking and unlocking of contracts. A custom change request is created for every process type. You can find further information in the release note Use of the Maintenance Framework for Business Transactions. The provider order contains the current products, rate plans and validity periods. You can reproduce the contract history by using the contract's change requests. When making changes to contracts, fees often occur (change fees) or existing rate plans change. You can find more information on the settlement of these one-time or recurring fees in the release note Settlement of Recurring and One-Time Charges. Effects on Customizing You can make the basic settings for provider contracts in transaction customizing under CRM -> Transactions -> Basic Settings. The following transaction types are available here for provider orders and contracts in the standard system: ______________________________________________________________ SAP AG 157 SAP-System ______________________________________________________________ ISPR - Provider order using E-Commerce PRVO - Provider order for call center PRVR - Provider order for dealer PRVC - Provider contract In addition there are the item categories: TAP PRCN PRCP PRON PROP Sales item for packages Free provider contract item (for rate plan combinations) Provider contract item (for rate plans) Free provider order item (for rate plan combinations) Provider order item (for rate plans) The previously offered transaction type and item category ISTC - Telco Contract are also available. You can use the following item category groups for item category determination: LUMF- Structure below (for example, with packages) NORM - Sales item PRNP - Provider rate plan, not relevant for pricing PRRP - Provider rate plan PRSV - Provider fee You can make specific settings for the provider contracts, for example, for the contract change processes and pricing for contract changes, in CRM Customizing under Transactions -> Settings for Provider Contracts. See also Provider Orders Use of Maintenance Framework for Business Transactions Settlement of Recurring and One-Time Charges 1.13.16.3 CRM-BTX-CTR-UCO 1.13.16.3.1 Use Usage-Based Service Contract This release note is only relevant if upgrading from SAP CRM 5.2 You can process service contracts based on usage to bill your customers for services with a certain usage volume (for example, number of copies) as defined in a service contract. This allows you as the service ______________________________________________________________ SAP AG 158 SAP-System ______________________________________________________________ provider to react more flexibly to customer demands while reducing costs for the end customer. You can model the entire usage-based service contract process in SAP CRM, including creating a service quotation and contract, entering and calculating the usage volume through counters and readings, and billing. For usage-based service contract processing, a quantity consumed is agreed upon in the service contract, and the services for the quantity consumed are defined under certain conditions. You can link various contracts together in a pool contract for pricing and billing purposes. You can use pool contracts to periodically recalculate the usage of all assigned contracts (single pool contracts) or perform usage billing for all assigned contracts in the pool contract (aggregate contract). Usage volume determination can occur in the following ways: Taking counter or meter readings Estimating Period-end closing Making entries manually Entering usage externally using an interface Usage-based billing occurs on a periodic basis, using billing plans. You can bill the service contract separately from usage-based billing. For example, if customers pay the contractual services monthly, but the usage-based component quarterly, several different billing plans are available. There is also a schedule for pool redistribution. This schedule exists as long as a contract is assigned to a pool contract. Effects on Customizing You make the necessary settings for usage-based service contract processing in Customizing for Customer Relationship Management, in the section Usage-Based Service Contract Processing. You make settings for counters, readings, and usage entry in Customizing for Customer Relationship Management, in the section Master Data -> Counters. See also For more information about usage-based service contract processing, see the SAP Library (help.sap.com) under SAP Customer Relationship Management -> Components and Functions -> Service -> Usage-Based Service Contract Processing. ______________________________________________________________ SAP AG 159 SAP-System ______________________________________________________________ 1.13.17 CRM-BTX-PRV Provider Transactions 1.13.17.1 New Functions in the Provider Contract and Dispute Management (New) Use Editing Disputes (New) This release note is only relevant if upgrading from SAP CRM 5.2. You can create disputes in the Interaction Center to react to customer complaints such as missed payments, credit memos, or incorrect invoices. For example, you can create a dispute with reference to an invoice that a customer disputes. You can also enter notes for a dispute. In addition, you can track a disputed invoice or you can create adjustment requests for completed disputes. Additional Change Processes in the Interaction Center (New) This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. Until now, you could make the following changes in the provider contract (Interaction Center): Contract extension Changes in product configuration Product switch Blocking and releasing connections Your customers can use these functions if they want to prevent unauthorized use of their telephone connection during their vacation, for example. Changing phone number Cancellation Master data change Example: Address change after moving - As of this release, the following additional change processes are available in the Interaction Center: Change SIM Card Revoke cancellation Revoke extension ______________________________________________________________ SAP AG 160 SAP-System ______________________________________________________________ 1.14 CRM-CMG Case Management 1.14.1 Automatic Case Notes in Case Management (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. As of Release SAP CRM 5.1, the automatic creation of case notes is supported. This makes it possible to have T100 messages or manually created notes automatically created as case notes in the relevant case. Additionally, you can use the Business Add-In CRM_CMG_NOTES_ADD to manipulate the automatically created case notes before saving. See also For more information, see the funtion module CRM_CMG_ADDNOTES and the Business Add-In CRM_CMG_NOTES_ADD. 1.14.2 Case Management (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. Case Management contains an expanded set of functions listed below: Enhanced authorization control for case access: By connecting the CRM case to the Access Control Engine (ACE) tool, flexible access control is available. By default, access is granted only to cases assigned to the same organizational unit. You can define additional authorization rules using the ACE tool. For example, you may want to assign case access to a certain level of employee, such managers, who are in different organizational units or territories. Automatic creation of case notes: A case note can now be created automatically to inform a case worker about events that occurred and affect the case. You can define additional attributes for your case notes to store additional information, for example, a note status. Creating e-mails from cases: You can create an e-mail from a case and append any necessary documentation about the case to send to another case processor or person responsible. This streamlines the case handling process. - - ______________________________________________________________ SAP AG 161 SAP-System ______________________________________________________________ - Customizing Case Note Attributes: You can customize note attributes by modifying the structure delivered for Case Management notes. You do this by adding fields for data types in the ABAP Dictionary in the delivered customer include CI_CMG_NOTE_ATTR. Reassignment of business partners in linked objects: If you transfer an ongoing case to another case processor or department, all outstanding case business partners and their associated activities are automatically transferred with the case. You can use the delivered BAdI Reassign Business Partners in Linked Objects to influence this behavior. Repetitive tasks: You can flag tasks and activities contained in a case as 'repetitive' and maintain the parameters for the repetition of this task. When you complete a repetitive task, the follow-up task of the same type will be created automatically. A default repetitive task is part of the standard delivery, however, you can configure your own repetitive task. To see how the default is configured and use it as a reference for your own configuration, see the explanation of the process in the IMG. Linking related cases: In addition to the existing hierarchical case structures (sub-cases, superior cases), you can link cases which are related, but do not form a hierarchy. This can give case processors a different overview of how cases may be related. Case closing profiles: The case closing profile lets you define how open dependent transactions should be handled that are contained in a case that is to be closed. In addition, you can define case closing profiles for specific business transactions that may differ from standard business transactions. A BAdI is also provided so you define additional tasks for the case closing profile. Case archiving: After cases are closed, you can extract cases from the database and archive the information. You can also call up archived information for various case types if you want to analyze archived case information. Enhanced case categorization: You can define attributes and link types to extend your case categories. You do this in transaction EEWB when you want add attributes or linked objects that will be added to the category modeler. The EEW business object CATEGORY_ENHANCEMENT gives you the option of creating category attributes and/or object links to the category. Case APIs and data exchange: APIs and BAPIs are provided to search, read and modify cases, and to export and import cases via SAP XI in an XML format. This allows access to case information from other applications, as well as importing cases and case information from one CRM system to another via an XI server. Case Search Scenario: You can set the search scenario for searching cases by choosing between Standard and SAF/TREX. The SAF/TREX scenario is faster and allows the system to handle more complicated search requests. Application / Form Processing: The CRM WebRequest component supports the online form-based processing of claims and applications. When an application (WebRequest) is created based on an inbound (XML) message, this message must be added as the original document to the created WebRequest. Therefore, the external interface for the CRM WebRequest provides an additional parameter to add this document. - - - - - - - - - Effects on Customizing ______________________________________________________________ SAP AG 162 SAP-System ______________________________________________________________ - Case Management -> Extended Customizing -> Define Case Closing Profile Case Management -> Extended Customizing -> BAdI: Define Additional Tasks for Case Closing Profile Case Management -> Process Partners -> BAdI: Reassign Business Partners in Linked Objects Case Management -> Extended Customizing -> Case Archiving -> CRM Data Archiving Process - Here you find several BAdIs and an archiving activity and an explanation of the archiving process. Case Management -> Extended Customizing -> Special Settings -> BAdI: BAPIs for Case Parameters ->BAdI: Change BAPI Parameters - Here you find several BAdIs that influence the BAPI import parameters Case Management -> Extended Customizing -> Case Import and Export with XI - Here you find activities for manually exporting cases to XI, monitoring cases exported to XI as well as multiple BAdIs for customer enhancements with XI and mapping and import and export functions. Case Management -> Extended Customizing -> Define Search Scenario Customer Relationship Management -> Transactions -> Settings for Activities -> Configure Repetitive Tasks Case Management -> Extended Customizing -> ACE Implementation - - - 1.14.3 Case Management (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. The following functions are available: Enhanced authorization control for case access: By connecting the CRM case to the Access Control Engine (ACE) tool, flexible access control is available. By default, access is granted only to cases assigned to the same organizational unit. You can define additional authorization rules using the ACE tool. For example, you may want to assign case access to a certain level of employee, such managers, who are in different organizational units or territories. Automatic creation of case notes: A case note can now be created automatically to inform a case worker about events that occurred and affect the case. You can define additional attributes for your case notes to store additional information, for example, a note status. Creating e-mails from cases: You can create an e-mail from a case and append any necessary documentation about the case to send to another case processor or person responsible. This streamlines the case handling process. Customizing Case Note Attributes: You can customize note attributes by modifying the structure delivered for Case Management notes. You do this by adding fields for data types in the ABAP Dictionary in the delivered customer include CI_CMG_NOTE_ATTR. - - - ______________________________________________________________ SAP AG 163 SAP-System ______________________________________________________________ - Reassignment of business partners in linked objects: If you transfer an ongoing case to another case processor or department, all outstanding case business partners and their associated activities are automatically transferred with the case. You can use the delivered BAdI Reassign Business Partners in Linked Objects to influence this behavior. Repetitive tasks: You can flag tasks and activities contained in a case as 'repetitive' and maintain the parameters for the repetition of this task. When you complete a repetitive task, the follow-up task of the same type will be created automatically. A default repetitive task is part of the standard delivery, however, you can configure your own repetitive task. To see how the default is configured and use it as a reference for your own configuration, see the explanation of the process in the IMG. Linking related cases: In addition to the existing hierarchical case structures (sub-cases, superior cases), you can link cases which are related, but do not form a hierarchy. This can give case processors a different overview of how cases may be related. Case closing profiles: The case closing profile lets you define how open dependent transactions should be handled that are contained in a case that is to be closed. In addition, you can define case closing profiles for specific business transactions that may differ from standard business transactions. A BAdI is also provided so you define additional tasks for the case closing profile. Case archiving: After cases are closed, you can extract cases from the database and archive the information. You can also call up archived information for various case types if you want to analyze archived case information. Time-dependant data visualization: You can access and maintain information about the primary person of a case directly within the case without navigating to the business partner record for this person. This is used, for example, if the critical, case-dependent information about the primary person changes, thus affecting a case or claim. You can flexibly define the set of information available in a specific case depending on the case type. Enhanced case categorization: You can define attributes and link types to extend your case categories. You do this in transaction EEWB when you want add attributes or linked objects that will be added to the category modeler. The EEW business object CATEGORY_ENHANCEMENT gives you the option of creating category attributes and/or object links to the category. Case APIs and data exchange: APIs and BAPIs are provided to search, read and modify cases, and to export and import cases via SAP XI in an XML format. This allows access to case information from other applications, as well as importing cases and case information from one CRM system to another via an XI server. Case Search Scenario: You can set the search scenario for searching cases by choosing between Standard and SAF/TREX. The SAF/TREX scenario is faster and allows the system to handle more complicated search requests. Application / Form Processing: The CRM WebRequest component supports the online form-based processing of claims and applications. When an application (WebRequest) is created based on an inbound (XML) message, this message must be added as the original document to the created WebRequest. Therefore, the external interface for the CRM WebRequest provides an additional parameter to add this document. - - - - - - - - - ______________________________________________________________ SAP AG 164 SAP-System ______________________________________________________________ Effects on Customizing Case Management -> Extended Customizing -> Define Case Closing Profile Case Management -> Extended Customizing -> BAdI: Define Additional Tasks for Case Closing Profile Case Management -> Process Partners -> BAdI: Reassign Business Partners in Linked Objects Case Management -> Extended Customizing -> Case Archiving -> CRM Data Archiving Process - Here you find several BAdIs and an archiving activity and an explanation of the archiving process. Case Management -> Extended Customizing -> Special Settings -> BAdI: BAPIs for Case Parameters ->BAdI: Change BAPI Parameters - Here you find several BAdIs that influence the BAPI import parameters Case Management -> Extended Customizing -> Case Import and Export with XI - Here you find activities for manually exporting cases to XI, monitoring cases exported to XI as well as multiple BAdIs for customer enhancements with XI and mapping and import and export functions. Case Management -> Extended Customizing -> Define Search Scenario Customer Realtionship Management -> Transactions -> Settings for Activities -> Configure Repetitive Tasks Case Management -> Extended Customizing -> ACE Implementation - - - 1.15 CRM-ACP Account Planning 1.15.1 Account Planning (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use the following features in Account Planning: Change history You can use standard change documents to track changes to account plans. Batch job to generate conditions In the previous release, the application generates conditions for an account plan when you release the account plan. You can generate conditions in a batch job. This can make it quicker to release account plans. Territory management enhancements for product and business partner input help - ______________________________________________________________ SAP AG 165 SAP-System ______________________________________________________________ In the previous release, the input help for product, product category, and planning customer lists all existing results for the master data. From here it is, for example, possible to select a non-assigned product in a territory. In this case, the application validates the selection and rejects the selected product. You can filter the possible values in the input help by territory. This can significantly reduce the number of results in the input help, and accordingly the scrolling required for retrieving the desired entry. 1.16 CRM-FM Funds Management 1.16.1 Funds Management (New) Use This release note is only relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. Funds management is an application that allows brand owners to manage the distribution, consumption, and administration of funds. It provides one of the basic building blocks for the market development funds (MDF) and trade promotion management (TPM). Funds management enables brand owners to track the status of the money in funds from the time it is budgeted to the time it is paid out to the corresponding partners and customers. Funds management is fully integrated with sales planning, forecasting, SAP NetWeaver Business Intelligence (SAP NetWeaver BI), SAP ERP, and financial systems. As of this release, the following functions are available with funds management: Funds plans and funds Fund usages Fund postings Budget postings Availability control Accruals Budget expiration Batch processing workbench Funds analytics ______________________________________________________________ SAP AG 166 SAP-System ______________________________________________________________ 1.16.2 Funds Analytics (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. Funds analytics provide extractors to analyze funds and related objects for funds management (FM). Together with claims analytics, funds analytics provide the analytical basis for market development funds (MDF) and trade promotion management (TPM). BI extractors contain information about the funds management objects that are used in MDF and TPM. You can use extractors for funds to transfer data from the source system to the SAP NetWeaver Business Intelligence (SAP NetWeaver BI) system so that, if needed, you have a basis on which to build your BI Content. The following extractors are available for funds: Funds Plan Fund Fund Posting Budget Posting Fund Usage Accrual Staging Area Expense Forecast Staging Area Many corresponding text extractors are also available. ______________________________________________________________ SAP AG 167 SAP-System ______________________________________________________________ 1.16.3 CRM-FM-ACL 1.16.3.1 Accruals (new) Use Accruals This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can calculate accruals in fund management (FM) for trade promotion management (TPM) and account planning fund usages to ensure that trade-related expenses are posted in the fiscal period in which they occur. An accrual is an amount that represents a liability or non-cash-based asset on an accounting statement. These amounts include, among many others, accounts payable, accounts receivable, goodwill, future tax liability, and future interest expense. There are five standard delivery processes: Accrual calculation This process determines accrual amounts for fund usages that represent expected expenses on a balance sheet. Several accrual calculation methods are provided that calculate accrual amounts based on a fixed date or spread over various periods of time. Accrual posting This process retrieves the accrual amounts from the accrual calculation and determines if there is a difference from the previous period for a funds plan ID. The difference between the amounts is posted to FM. Accrual reversal Since accrual postings are financial documents, they cannot simply be deleted. This process collects accrual postings and submits additional postings with reversed posting keys (equal negative amounts). Sales volume load This process retrieves the total amount of sales achieved during a specified period from SAP ECC. The sales volume load is required to perform accrual calculation. SAP ECC discount load This process imports off-invoice discounts from SAP ERP Central Component (ECC) into FM and posts them as external settlements. There are no accrual postings for discounts; they are expensed in SAP ECC as they occur. - - - - The standard functions available for accruals in the batch processing framework are: Start accrual process Display results Edit results Provide external data for accrual process Display external data Display rebate agreement volumes Display distribution reference curve ______________________________________________________________ SAP AG 168 SAP-System ______________________________________________________________ - Edit distribution reference curve Effects on Customizing You can define settings for accruals in Customizing for Customer Relationship Management, by choosing Funds Management-> Accruals. See also Batch Processing Framework Direct Scan Based Accrual Rates 1.16.4 CRM-FM-AVC Availability Control 1.16.4.1 Availaibility Control (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use availability control (AVC) in funds management and claims management to control fund consumption. You define an AVC profile that includes: Check rules that indicate the values which are included in the availability calculations. A check rule defines the value categories in a fund or fund usage that are added or subtracted to derive the available amount for a business transaction, for example, claim. Tolerance profiles that define details such as : Triggering usage rate, for example, consumption over 90% of fund budget or consumption over 95% of fund budget Triggering absolute variance, for example, less than USD 50 left in the fund or fund over-consumed by USD100 Currency of absolute variance Message issued to the user when budget is not available in the selected fund Authorization level, as different users may have different tolerance levels - You link an AVC profile to a transaction type in claims and funds to specify the control mechanisms for this specific type of business transaction. ______________________________________________________________ SAP AG 169 SAP-System ______________________________________________________________ Effects on Customizing Define Availability Control (AVC) Check Rules Define Availability Control (AVC) Tolerance Profiles Define Availability Control (AVC) Authorization Levels Define Availability Control (AVC) Profiles Assign Funds Management AVC Profile 1.16.5 CRM-FM-BER Budget Expiration 1.16.5.1 Budget Expiration (new) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use the budget expiration process to manage the expiration of budget postings based on expiration dates in fund management (FM) for market development funds (MDF). You can view expired, or expiring, budget postings based on the expiration periods. You can extend a budget after it has been posted if the expiry date has not yet passed. For example, the partner is not able to consume the budget in the expected timeframe due to reasons beyond his control or due to delays on the part of the brand owner. You can also renew a budget that has expired but needs to be made available to the fund again. For example, the partner may not have been able to consume the budget in time due to valid business conditions or because of delays on part of the brand owner. The renewed budget is available again until the next budget expiration process is run. The expiration process does not expire a budget that is in the process of being consumed due to reservation or claim approval. However, if the reservation or claim that is preventing the budget posting from being expired is cancelled after the expiration run, the budget expires immediately. The standard functions available for budget expiration in the batch processing workbench are: Schedule budget expiration process Manually perform budget expiration process Display budget expiration schedule for a fund Renew budget ______________________________________________________________ SAP AG 170 SAP-System ______________________________________________________________ - Extend budget Approve budget Brand owner approval of partner initiated budget renewal or extension. Effects on Customizing You can define settings for budget expiration in Customizing for Customer Relationship Management, by choosing Transactions -> Basic Settings -> Define Transaction Types. See also Batch Processing Framework Budget Postings Funds Plans 1.16.6 CRM-FM-BFW Batch Framework 1.16.6.1 Batch Processing Framework (new) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use batch processing framework in funds management (FM) to create, schedule, monitor and search jobs. Jobs can run unattended, and possibly simultaneously, in the background. Effects on Customizing You can define settings for the batch processing framework in Customizing for Customer Relationship Management, by choosing Basic Functions ->Batch Processing Framework. See also Accruals Budget Expiration Budget Postings ______________________________________________________________ SAP AG 171 SAP-System ______________________________________________________________ 1.16.7 CRM-FM-BPO Budget Posting 1.16.7.1 Budget Postings (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Trade promotion management (TPM) professionals and channel managers can use budget postings in funds management (FM) to manage budgets in funds. You can create budget postings manually or by using an external planning application. You can use workflow functionality, for example, for budget approval processes. There are different types of budget postings. You can use: Budget updates to fill or remove budget from a fund, initially or at a later point in time Budget transfers to distribute budget between funds Budget expiration runs to automatically update the validity of the posted budget Budget renewals to make budget available after it has expired Budget extensions to extend the validity of budget, that have not yet expired In the marketing development funds (MDF) scenario, budget postings may have an expiration date. For more information on the budget expiration process, see Budget Expiration. You can approve budget postings either without a threshold value or with a check against the threshold value for the validated amount. Effects on Data Transfer All budget postings are recorded in fund postings once the budget posting has been approved and the availability of the posting amount has been verified. Effects on Customizing In addition to the standard budget posting transaction types, you can define additional transaction types in Customizing for Customer Relationship Management by choosing Transactions -> Basic Settings -> Define Transaction Types. In the IMG activity Define Transaction Types, a new transaction category Budget Postings is available. You can use it to differentiate between the different posting types and to indicate whether: Expiration logic is used for this transaction type Multi-stage approval is activated for this transaction type ______________________________________________________________ SAP AG 172 SAP-System ______________________________________________________________ See also Budget Expiration Accruals Fund Postings Funds Management 1.16.8 CRM-FM-FND Fund Plans and Funds 1.16.8.1 Fund Determination (Enhanced for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Fund determination is used to automatically assign funds to different business objects, for example, budget transfers. You define fund determination profiles and assign them to transaction types to ensure that budget from the appropriate fund is used in specific transactions. You can now use top-down fund determination to distribute budget to subaccounts in the account hierarchy, for example, in budget transfers. Effects on Customizing You define fund determination profiles in Customizing for Customer Relationship Management under Funds Management -> Fund Determination -> Define Fund Determination Profiles. 1.16.8.2 Funds Plans and Funds (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. You can create and maintain funds plans, which are groupings of funds, for example, by fiscal year. You can have several independent funds plans. You may, for example, set up different funds plans for different areas in your organization or for different functions. All the funds associated with a funds plan share the same currency. A fund is a container for a budget. You give the fund a name, a description, a status, and a number of ______________________________________________________________ SAP AG 173 SAP-System ______________________________________________________________ attributes that describe its purpose. In trade promotion management (TPM), a fund is uniquely identified by the funds plan, the fund type, and the fund attributes. There cannot be two funds in a funds plan that have exactly the same values for these fund attributes for the same fund type. In marketing development funds (MDF), this is not the case. Two funds may have the same values as the funds plan, fund type, and fund attributes. With funds plans and funds, you can use the following new functions to help you manage them: Mass creation and change of funds Budget postings Budget expiration Assignment of funds to funds plans Mass copy of funds from one funds plan to another Checkbook (funds) Managing statuses (funds plans and funds) Archiving Effects on Customizing You can customize the following: Fund types Fund plan types Fund determination Expense types Key figures in the checkbook 1.16.9 CRM-FM-FPO Fund Posting 1.16.9.1 Fund Postings (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use fund postings with funds management (FM). Fund postings automatically capture all value flows that occur in FM as transactions are processed. For example, fund postings capture changes to budgets, planned and reserved values, prepayment and ______________________________________________________________ SAP AG 174 SAP-System ______________________________________________________________ accrual balances, and expensed and paid amounts, and produce a line item-based audit trail as in a financial system. You can: Search for a fund posting and display its details, for example, the posting transaction, posting period and funds plan ID You can verify the source details of the posting by clicking on the hyperlink to the specific transaction that has triggered the posting. Note that it is not possible to link to fund postings created by accruals. - View the line items related to the posting and link to the fund information Archive fund postings according to the SAP CRM standard data archiving process See also Funds Management Budget Postings Fund Usage 1.16.10 CRM-FM-FU 1.16.10.1 Fund Usage (New) Use Fund Usages This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. Fund usages in funds management (FM) can be used to reserve parts of fund budgets for trade promotions, account plans, or market development fund (MDF) initiatives. The funds can be reserved for claims, settlements, prepayments, direct payments, and fund-based chargebacks and write-offs. Fund usages can then be claimed against, accrued and balanced after the last claim is made to return unconsumed budget and accruals. All fund consumptions are represented by fund usage objects. For example, for each trade spend planned in trade promotions or account plans, a corresponding fund usage object is created by the system once the trade promotion or account plan reaches a defined status, such as Released. A fund usage item is created for each product category or group. Each fund usage item lists the corresponding fund attributes, fund, and amount. The following functions are available for fund usage: Search ______________________________________________________________ SAP AG 175 SAP-System ______________________________________________________________ - Display Balance Effects on Customizing You can define settings for fund usage in Customizing for Customer Relationship Management, by choosing Funds Management -> Fund Usage. 1.17 CRM-CLA Claims Management 1.17.1 Claims Management for SP02 (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Enhancements in Claim Submissions Updates to amounts on the following business transactions are reflected in the amounts displayed on the claim submission to which they belong: Deduction claims Fund-based chargebacks Project-based chargebacks Carried-over prepayments To complete claims or claim submissions, you cannot now set the status manually, but you must use report CRM_CLA_CLOSE, which checks the amounts for consistency. You can call the report using transaction CRMD_CLA_CLOSE. Similarly, to write off claim submissions, you must use report CRM_CLA_WRITE_OFF, which you can call using transaction CRMD_CLA_WRITE_OFF. Search Enhancements When adding trade promotions to an invoice claim, you can use trade promotion search. Customer fields added via the Easy Enhancement Workbench (EEW) can be included both as search fields and as columns in the search result list with searches for business transactions. ______________________________________________________________ SAP AG 176 SAP-System ______________________________________________________________ Optional Territory Check in Claim-Related Authorizations Authorizations for the following kinds of business transaction can be customized to take territory assignment into account so that you can easily grant users access to business transactions in their territory: Claims Claim Submissions Chargebacks Budget Reservations Prepayments Moreover, where the territory check for a business transaction is enabled, partners and marketing projects that a user can assign to the business transactions are restricted to those in the user's territory. You can use report CRM_TERR_REL_OBJ to increase the performance of the territory check. You can run the report using transaction SE38 or as a scheduled job. Enhancements to the Resolution Assignment Block in Claims In claims that can be assigned to trade promotions (invoice claims), the Resolution assignment block allows you to add target group members. In addition, it can be customized to use different indentation patterns for the information under each assigned trade promotion depending on customizing settings for the type and planning account of the trade promotion. Collective Prepayments For purposes such as end-of-year processing, you can consolidate several prepayments into a single collective prepayment and assign the collective prepayment to a fund that is different from the funds of the original prepayments. This allows you to close the funds of the original prepayments. Partial Rejection for Correction of Partially Settled Claims (New) Previously, rejection for correction of partially settled claims resulted in rejection of all correction line items in a chain of linked settlement documents. Partial rejection for correction of partially settled claims allows you to cancel individual correction line items in a settlement document chain, with the aim of reactivating the predecessor claim. New data source for SAP NetWeaver Business Intelligence Information from both fund-based and project-based chargebacks can be extracted to SAP NetWeaver Business Intelligence with the data sources described in Claims Management: BI Extractors. Effects on Customizing ______________________________________________________________ SAP AG 177 SAP-System ______________________________________________________________ See also - Territory Check checkbox in Define Transaction Types Define Layout of Claims Resolution Tree Assign BI Info Objects to MDF Programs and MDF Special Programs Corresponding Release Note for SP01 Release Note for Scheduled Claims for SP01 Claims Management: BI Extractors SAP Note 1122014 ("Currency in MDF claim") SAP Note 1132136 ("CSD Amount changes made in CRM 2007 SP02") 1.17.2 Claims Management (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. A claim is a request for reimbursement. A claim potentially includes information about proof-of-performance as a means of justifying the claim. A claim is submitted for audit and reimbursement (settlement). You can manage claims related to trade promotion management (TPM) and market development funds (MDF). For more information about the functional possibilities of claims management, see the application help. Variety of Claim Types You can use the following claim types: Claim Type MDF claim Direct payment Deduction claim Invoice claim Scheduled claim Chargeback Recommended Area MDF TPM TPM TPM TPM TPM - Deduction A deduction is any situation where the channel reseller or distributor has reduced the manufacturer's invoice amount because of a charge taken against advertising, marketing or any other activity. ______________________________________________________________ SAP AG 178 SAP-System ______________________________________________________________ - Invoice claim Invoice claims are sent from the account (retailer, wholesaler, indirect) claiming an amount that has been agreed on in a trade promotion/account plan. Invoices can be either very structured providing the activities and performances as well as the claimed amount for each including proof of performance or there is the invoice amount with some explanatory note. Direct payment Direct payments are typically used to payout to various number of accounts/stores without a direct business relationship. Therefore there is no marketing project planned for these accounts/stores. Chargebacks A chargeback is a way of requesting money from the customer who has deducted from the manufacturer's invoice without performing. Integration with Funds Management - - The fund determination function controls which funds can be used for a claim. Fund budgets are consumed when claims are validated. If a claim is canceled, the corresponding fund budget is also reset. Approval, Validation and Settlement You can use SAP Business Workflow tool to control the approval process. The process supports manual approval and automatic approval, and notification. Availability checks determine whether a claim or combination of claims can exceed the available budget. You can use the validation worksheet function to determine, for example, how much is owed. The settlement process is triggered after finally approving the claims. Integration with SAP ERP Claims management is integrated with SAP ERP and can be integrated with SAP ERP Dispute Management (ERP FSCM). See also Funds Management (New) Market Development Funds (Changed) Trade Promotion Management (Enhanced) 1.17.3 Claim Settlements (New) Use ______________________________________________________________ SAP AG 179 SAP-System ______________________________________________________________ This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Claims related to trade promotion management (TPM) and market development funds (MDF) are settled in the SAP CRM billing component and transferred to the following integrated applications: SAP ERP Financials (accounts payable and receivable, controlling) SAP ERP Dispute Management (dispute cases for deduction claims, prepayments, and write-offs) The following is an overview of the claim settlement functions in SAP CRM billing. Claims and Prepayments When a claim is approved or a prepayment triggered, items from the claim or prepayment transaction are transferred to the billing due list. Settlement takes place either during a scheduled settlement run or is triggered manually. During settlement, credit memos are created for the payable amount. In the case of deduction claims, which do not require a payout, the credit memo clears a dispute case in SAP ERP Dispute Management. You can activate an availability check to determine whether the fund budget is sufficient to reimburse each claim item. If the budget is insufficient, the billing due list item remains open. You can also make partial payouts for claims if the fund budget is insufficient for a full payment. Write-Offs Amounts that are written off because they have been overpayed to a claiming account or are unresolved are also processed in billing. These amounts are posted as expenses in accounting. Cancellation and Correction You can cancel and correct settlements. For more information, see the application help for settlements in claims management. Note: You cannot use the following functions for claim transactions: Intercompany billing Supplementary invoice Retroactive billing Condition-based invoice split Effects on Customizing You need to make the following settings in Customizing for Customer Relationship Management, under Billing: Activate the following features (activity Configure Application): Enhanced Account Determination Funds Management Integration ______________________________________________________________ SAP AG 180 SAP-System ______________________________________________________________ - Marketing Set Set the billing relevance of all claims-related item categories to Value-Based Billing After Approval (activity Define Billing Relevance of Item Categories) Define the billing types that you require for settling claims (activity Define Billing Types): Assign one of the predefined billing categories for prepayments or claims. Assign any cancellation copy requirements that you require. You can use a predefined copy requirement, or create your own in the activity Define Copy Requirements and implement it in the activity System Enhancements -> Business Add-Ins ->Copy Requirements for Cancellation. If required, assign an account determination type for the billing type. Note that account determination types assigned to billing types override the account determination type assigned to the entire application (in the IMG section Integration -> Transfer of Billing Documents to Accounting). - - Define the billing item categories that you want to use for claim settlements (activity Define Billing Item Categories) Assign each transaction type and item category for claims to the corresponding billing item categories (activity Item Category Determination -> Assign Item Categories) You need to make the following settings in Customizing for Customer Relationship Management, under Billing -> Integration -> Transfer of Billing Documents to Accounting -> Transfer to Accounts Receivable (FI-AR) and Accounts Payable (FI-AP): Specify symbolic accounts for determining the following in SAP ERP Financials : Expense and accrual accounts for claims, depending on the sales organization and expense type Balance sheet accounts for prepayments, depending on the sales organization and expense type You do this in the activity Enhanced Account Determination -> Assign Symbolic Account Key. Specify the document types that you want to use to post billing data in accounting (activity Assign Document Types) Specify the dunning block and payment terms for prepayments (activity Define Parameters for Prepayment) You also need to set up data exchange according to SAP Note 883162 to enable vendor-based integration with accounts payable in SAP ERP. In particular, you need to make settings for the following: See also For an overview of claims management functions, see the release note Claims Management (New). For detailed information on claims and claim settlement, see the application help for claims management. The billing type that you use for integration with accounts payable The billing category Claim Settlement (Accts Payable) ______________________________________________________________ SAP AG 181 SAP-System ______________________________________________________________ 1.17.4 Aggregation and Distribution of Amounts in Marketing Projects for Claims (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. As brand owner, you can add a marketing project to an invoice claim or deduction claim in the Resolution assignment block. This marketing project is exploded in the respective levels. You can then enter claimed, validated, or rejected amounts for the expense type or the entire marketing project. You do this at the highest level of the marketing project or at expense type level. You manually enter the amount claimed in the bill in the Claimed Amount column. You enter the corresponding amounts in the Validated Amount and Rejected Amount columns. If you accept the claimed amount, the Rejected Amount column stays empty. If you accept only part of the amount due to complaints (for example, because the marketing promotion did not go as expected), you enter the remaining amount in the Rejected Amount column. The amounts are then distributed to the respective subitems within a column, according to the predefined distribution logic. The remaining amount of the fund is used as the distribution key, and the relationships in these remaining amounts are considered in the distribution logic. The relationships of the remaining amounts correspond to the relationships of the claimed-, validated-, and rejected amounts. As brand owner, you then have the opportunity to checkyour partner's claims and you can get an overview of the spending valuesfor certain marketing promotions and also analyze the promotions. Note: The distribution- and summation logic of the amounts is used as an example and implemented as a pricing user exit. You can therefore adjust this implementation to your requirements without modification. Effects on Customizing You use pricing procedure 26CSR0, which contains formula 2610. The cumulation- and distribution logic are implemented in this formula. You use the following condition types with the condition functions: Description Condition Type Condition Function Condition Function for the Distribution Key Claimed Costs 26C1 26C1 Approved Costs 26C4 26C4 Rejected Costs 26C7 26C7 Condition Type for the Distribution Key 26D2 26D1 26D3 26D2 26D1 26D3 Check whether the condition functions named above are assigned to the condition types. You can maintain the condition functions in SAP CRM Customizing by choosing Customer Relationship Management -> Financial Services -> Basic Functions -> Pricing -> Define Condition Functions. Note: If you want to create your own condition types, you must assign the condition functionsto the condition types in accordance with default Customizing. When you create your own pricing procedure, you must include the three condition types for the distribution key 26D1, 26D2, and 26D3, in addition to the condition types for validated amounts (26C4), claimed amounts (26C1), and rejected amounts (26C7). You can find more information in SAP CRM Customizing by choosing Customer Relationship Management -> Basic Functions -> Pricing -> Define Settings for Pricing -> Create Pricing Procedure and Create Condition Types. ______________________________________________________________ SAP AG 182 SAP-System ______________________________________________________________ You have assigned the respective condition types to the pricing procedure 26CSR0 in the correct sequence, in easy condition entry. The condition type in the first field is connected to the Claimed Amount column, the condition type in the second field to the Validated Amount column, and the condition type in the third field to the Rejected Amount column. You can find more information in SAP CRM Customizing by choosing Customer Relationship Management -> Basic Functions -> Pricing -> Pricing in the Business Transaction -> Set Up Easy Condition Entry. 1.17.5 CRM-CLA-BI BI Integration 1.17.5.1 Claims Management: BI Extractors Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Extractors for Claims Management (New) This document provides information about BI extractors for the following business transactions in claims management: Claims Claim Submissions Reservations Prepayments Chargebacks You can use BI extractors to transfer data from the source system to the SAP NetWeaver Business Intelligence (SAP NetWeaver BI) system so you have a basis on which to build your BI content. The following are the attribute extractors: 0CRM_CLAIM: Attributes for claims (invoice claims, deduction claims, reimbursement claims, and direct payments) Reimbursement claims were previously known as MDF claims. 0CRM_CSD: Attributes for claim submissions 0CRM_RESERV: Attributes for MDF reservations Attributes for prepayments Attributes for chargebacks (fund-based chargebacks and project-based 0CRM_PREPAYMENT: 0CRM_CHARGEBACK: chargebacks) The following are the text extractors: 0STAONESYSB_TEXT: Extraction of texts for status group ONE Extraction of priority texts for reimbursement claims 0CRM_CLAIM_PRIO_TEXT: ______________________________________________________________ SAP AG 183 SAP-System ______________________________________________________________ - 0CRM_CLAIM_REASON_TEXT: Extraction of reason texts for reimbursement claims Effects on Existing Data These extractors fill the extraction structure of a DataSource with data from business objects. You can extract data from CRM claims management by performing a full extraction or by performing a delta extraction. These requests may be made with specific data filtering criteria. Effects on Customizing For the 0STAONESYSB_TEXT text extractor, you need to have status object group ONE and BW status object SYSB defined in Customizing for Integration with Other mySAP Components under Data Transfer to the SAP Business Information Warehouse -> Settings for Application-Specific DataSources (PI Basis) -> Status Concept for BP/Product/CRM Objects -> Display system status. 1.18 CRM-ISA Internet Sales 1.18.1 Shopping Basket (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. The Requested Delivery Date field has been removed from the shopping basket in the provider shop. The Requested Contract Start Date is still available. 1.18.2 Enabling Links to Web Channel Applications from CRM WebClient UI (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. ______________________________________________________________ SAP AG 184 SAP-System ______________________________________________________________ You can now access CRM Web Channel applications direct from the Partner Channel Management and Web Channel roles in the CRM WebClient user interface (UI): E-Commerce Manager Partner Manager Channel Manager The following Web applications will be opened in a new browser window, when you select the appropriate links on the UI: E-Commerce Manager Shop Management application User Management application B2B and B2C Extended Configuration Management (XCM) applications Web Crawler application Channel Manager Shop Management application User Management application Partner Manager Shop Management application User Management application Collaborative Views application ICSS application Customer Shop Partner Shop Effects on Customizing To enable links to the CRM E-Commerce Web applications from the SAP CRM UI, based on the standard customizing delivery, you need to carry out the following activity in Customizing Define the Protocol, Host Name, Port, and XCM Application Configuration: For the E-Commerce Manager role: In Customizing for Customer Relationship Management, choose E-Commerce -> Basic Settings for E-Commerce -> Enable Links from the SAP CRM UI to E-Commerce Web Applications -> Define the Protocol, Host name, Port, and XCM Application Configuration. ______________________________________________________________ SAP AG 185 SAP-System ______________________________________________________________ - For the Partner Manager and Channel Manger roles: In Customizing for Customer Relationship Management, choose Channel Management -> Basic Settings -> Enable Links from the SAP CRM UI to E-Commerce Web Applications -> Define the Protocol, Host name, Port, and XCM Application Configuration. If you wish to modify the standard delivered customizing and define additional URL links for E-Commerce Web applications, you need to carry out the following additional steps in Customizing: 1. Define URLs and Parameters. For the E-Commerce Manager role: In Customizing for Customer Relationship Management, choose E-Commerce -> Basic Settings for E-Commerce -> Enable Links from the SAP CRM UI to E-Commerce Web Applications -> Define URLs and Parameters. For the Partner Manager and Channel Manger roles: In Customizing for Customer Relationship Management, choose Channel Management -> Basic Settings -> Enable Links from the SAP CRM UI to E-Commerce Web Applications -> Define URLs and Parameters. - 2. Create a transaction of type URL using the Transaction Launcher wizard. In Customizing for Customer Relationship Management, choose UI Framework -> Technical Role Definition -> Configure Transaction Launcher. Define logical links in transaction CRMC_UI_WEBAPPL. The descriptions entered here will be displayed as links on the SAP CRM UI. When creating the links you enter in the Parameter field the transaction parameter you defined in the Launch Transaction wizard. For the Parameter Class select the entry CL_CRM_UI_LTX_NAVBAR_PARAM from the field entry help. Define URLs. SAP delivers standard links to the various E-Commerce applications. If you need more than one link to an application, for example, you wish to create one link for a search, and one link for create, enter an additional URL parameter for the transaction ID. For the E-Commerce Manager role: In Customizing for Customer Relationship Management, choose E-Commerce -> Basic Settings for E-Commerce -> Enable Links from the SAP CRM UI to E-Commerce Web Applications -> Define URLs. For the Partner Manager and Channel Manger roles: In Customizing for Customer Relationship Management, choose Channel Management -> Basic Settings -> Enable Links from the SAP CRM UI to E-Commerce Web Applications -> Define URLs. 3. 4. - ______________________________________________________________ SAP AG 186 SAP-System ______________________________________________________________ 1.18.3 Improved Usability (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. Usability of SAP CRM Web Channel has been improved. There are two major improvements: The usability of the transaction flow: The appearance of links between orders, quotations, order templates, invoices, and deliveries has been harmonized. On header and item level, the links to preceding and follow-up transactions now look the same in all transaction types. The usability of the result list: Additionally, you can now search for items of orders, quotations, order templates, and complaints and returns. Because items are usually displayed with more fields than headers, you can now expand the result list, which is displayed in the navigation bar, to the work area. For more information about how the search has been enhanced with additional search criteria, see release note Generic Filter Solution (Enhanced). - 1.18.4 Multiple Campaign Assignment (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Campaign assignment to orders has been improved in SAP CRM Web Channel: When you create or change an order, you can now enter multiple campaigns manually on header - as well as on item level of orders. If you click on the icon next to the Campaign field under Additional Order Data, five additional fields appear, in which you can enter additional campaigns on header level. On item level, this icon can be found next to the Campaign field in the item details. If you click on the hyperlink under these additional fields, more fields are available to assign even more campaigns. If multiple campaigns are found by campaign determination, all determined campaigns are now added to the list of campaigns of an item. Prior to this release, you could only select one campaign, even if several campaigns were found by campaign determination. The selected campaign was then assigned to the item. As of this release, if more than one campaign is found by campaign determination, all determined campaigns are added to the list of campaigns that can be changed manually. On item level, a quick info text informs you that the system has automatically assigned campaigns to an item. This quick info appears, when you scroll over the flag icon next to the product in the - ______________________________________________________________ SAP AG 187 SAP-System ______________________________________________________________ Description field. If you now expand the item, you can see in the item details which campaigns the system automatically assigned to this item. Effects on Customizing You can enable the assignment of multiple campaigns and the manual entry of campaigns with the following two parameters in the Shop Management: Parameter Allow Multiple Campaigns in the Marketing tab page If you enable this parameter, multiple campaigns can be assigned to an order on header and item level. Parameter Allow Manual Entry of Campaigns in the Marketing tab page If you enable this parameter, all assigned campaigns are displayed and can be changed manually. If you disable this parameter, the manual entry of campaigns is not allowed and campaign fields cannot be changed in the order. In this case, you can only see campaigns that were assigned in the CRM backend system or found in campaign determination. The icon next to the Campaign field is only displayed if more than one campaign is assigned to an item. - 1.18.5 Campaign Enrollment (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now enroll yourself and business partners below your hierarchy level to a campaign in SAP CRM Web Channel. Additionally, you can see your enrollment status and the enrollment status of business partners below your hierarchy level of a campaign to which you have already enrolled. For some campaigns enrollment is required before you can place orders with reference to campaigns. You start the campaign enrollment on the Welcome page of the Web shop. Here you need to enter the ID of the campaign to which you are assigned. Then you select the business partners who are to be enrolled for this campaign. Here you can choose between the following options: Option Myself: You can only enter a campaign that is assigned to you if you are a business partner. Option Specific Business Partners: An additional dropdown box - with all business partners in the business partner hierarchy is displayed. If the number exceeds a certain threshold value, an input help opens instead. Option All Business Partners: The list of business partners is generated from all business partners in the business partner hierarchy and from the business partners who are in the target group of the selected campaign. - ______________________________________________________________ SAP AG 188 SAP-System ______________________________________________________________ The campaign is displayed on a separate page with the following details: Campaign Type, Campaign Start Date and Campaign End Date, Enrollment Start Date, and Enrollment End Date and a description of the campaign. The list of business partners is displayed below. Now you can activate the Enroll indicator of those business partners who are to be enrolled. You can only change the enrollment data during the enrollment period. After that period, the enrollment data is only displayed and cannot be changed anymore. If the enrollment period has not yet started, you cannot change the enrollment data either. Effects on Customizing You need to restrict or select business partners in the business partner hierarchy in Customizing under Customer Relationship Managment -> Web Channel -> Basic Settings -> Define Business Partner Hierarchy. To enable the enrollment of business partners, you can activate the parameter Allow transaction management for other business partners in hierarchy in the General section of the Transactions tab page in the Web Shop Management. See also For more information about campaign enrollment in the CRM Marketing application, see release note Enrolling for Marketing Projects. If you enable this parameter, you can also enroll other business partners in the business partner hierarchy. If you disable this parameter, you can only enroll yourself as a business partner. - To enable campaign enrollment, you need to activate the parameter Enrollment for Campaigns Allowed in the Marketing tab page in the Shop Management. 1.18.6 Dynamic Field Control for Orders (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Dynamic field control for orders is now available in SAP CRM Web Channel. This function controls the visibility and changeability of order fields in the Web shop depending on a user's authorizations and on the field control of the CRM order. The dynamic field control for orders is based on: ______________________________________________________________ SAP AG 189 SAP-System ______________________________________________________________ - The UI control in the Web shop The UI control depends on the definition of order fields, that is, if order fields are visible and changeable in the Web shop. On order pages in the Web shop, the field control adopts the settings of the UI control in the Web shop. Fields that are not to be displayed can be hidden or disabled in Extended Configuration Management (XCM) of the Web shop. With the authority check, the visibility or changeability of order fields can be restricted even more. The authority check of the order The underlying authorization customizing depends on transaction type, item category and delivery status. To become independent from item category and delivery status, you can enter ' * ' in the customizing of both fields. As a consequence, certain order fields are not visible for a certain transaction type. In this case, these fields are not displayed on the order entry pages of the Web shop. - The dynamic field control for orders offers the following functions: Hide, disable or generate fields dynamically You can now hide, disable, or generate fields dynamically on header and item level on the order entry and status pages in the Web shop. Highlight additional fields If new fields are available when you change an order item, the corresponding items are highlighted so that you are aware of these new fields. Example When you enter an order in the Web shop and change the item data of this order, for example, the item type or the product number, an additional field, which was hidden earlier, is now displayed. You are then informed by a system message that this additional field is now displayed. Support field control for empty line items Prior to this release, all fields were available in empty lines, regardless of a user's authorizations. As of this release, only those fields that are visible according to field control and authority check are displayed. - - Effects on System Administration For more information about how to hide or disable fields, see SAP Service Marketplace at service.sap.com/crm-inst -> CRM Catford Project -> CRM Server and Standalone Components -> Development and Extension Guide for SAP CRM Web Channel -> Web Channel Framework -> Dynamic Field Control. Effects on Customizing Select the UI elements for the fields in the header or items of an order that you want to hide or disable. To do so, use the file uicontrol-config.xml in Extended Configuration Management (XCM). Define the authorizations for display and modification of order fields. For more information, see the IMG activity under Customer Relationship Management -> Web Channel -> Basic Settings -> Define Authorizations. - ______________________________________________________________ SAP AG 190 SAP-System ______________________________________________________________ 1.18.7 Generic Filter Solution (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. The generic search framework in SAP CRM Web Channel now supports additional search criteria. In addition to the search for headers, you can now search for items of orders, quotations, order templates, and complaints and returns. Because items are usually displayed with more fields than headers, usability of the result list has been improved. You can now expand the result list, which is displayed in the navigation bar, to the work area. You can now search for CRM orders with campaign ID or delivery ID For one order transactions, the generic search framework is based on the reporting framework. Because the reporting framework does not support the search with reference transactions, the generic search framework has been enhanced. For more information about the usability improvements, see the release information Improved Usability (Enhanced). With BAdI implementations, you can now implement additional search criteria, for example, other reference transaction types for orders or other one order types. - You can now search for CRM invoices with reference transaction ID Since the prior release, the search for invoices with order numbers in SAP CRM Web Channel only works if the order is saved as the directly preceding transaction in CRM Billing. This does not work in delivery-based invoicing, where the delivery note is the directly preceding transaction. Therefore, the search for invoices has been enhanced and now also takes into account orders that are indirectly preceding transactions. Effects on Existing Data Effects on System Administration For more information about how to implement additional search criteria via BAdI, see SAP Service Marketplace at service.sap.com/crm-inst -> CRM Catford Project -> CRM Server and Standalone Components -> Development and Extension Guide for SAP CRM Web Channel -> Web Channel Framework -> Further Services -> Generic Search Framework. For more information about how to enable the expansion of the result list, see SAP Service Marketplace at service.sap.com/crm-inst -> CRM Catford Project -> CRM Server and Standalone Components -> Development and Extension Guide for SAP CRM Web Channel -> Web Channel Framework -> Further Services -> Generic Search Framework. - Effects on Customizing The BAdIs to search for orders with campaign ID or delivery ID have already been implemented and activated. ______________________________________________________________ SAP AG 191 SAP-System ______________________________________________________________ - To define additional search criteria via BAdI, see BAdI: Additional Search Filter in Customizing under Customer Relationship Management -> Web Channel -> Basic Settings -> Business Add-Ins for Web Channel. The BAdIs to search for items of orders, order templates, and quotations have already been implemented and activated. - 1.18.8 Customer Role (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The Customer portal role contains different iViews from CRM Web Channel, SAP NetWeaver Business Intelligence (BI), and SAP NetWeaver Knowledge Management (KM). The navigation structure of this portal role has not been changed since SAP CRM 5.0; with the exception of the iViews for Internet Telephony (IT) and Callback, two methods of Live Support, that are no longer available. The Password Change iView has been removed from the setup page; this function is now available on the central Personalization page. All iViews, for example, for Ordering or Payment, are shown in the same browser window. That means that no separate browser window opens when an iView is started. Effects on System Administration You have installed SAP NetWeaver 7.0 (2004s). 1.18.9 Collaborative Views: Search and Create (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. The collaborative views application is now available in the CRM WebCient UI. The collaborative views application is linked in the Partner Manager business role and now provides two different entry points: search and create. If the user selects Collaborative Views under Search on the Administration work center, the Java application opens in a new window directly on the search page for collaborative views. If the user selects Collaborative View under Create on the Administration work center, the Java application is started in a new window directly on the page in which the user can create collaborative views. ______________________________________________________________ SAP AG 192 SAP-System ______________________________________________________________ Effects on Customizing You have made the necessary settings in Customizing for Customer Relationship Management, by choosing Web Channel -> Basic Settings -> Activate Links from CRM WebClient UI to Web Channel Applications -> Define Protocol, Host Name, Port, and XCM Application Configuration. 1.18.10 CRM-ISA-CAT Internet Sales Catalog 1.18.10.1 Basic Eye-Catcher Text in Web Shop (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now display basic eye-catcher text for products in the Web shop. The basic eye-catcher text enables you to highlight important information about a product or package, for the user to see and read at a quick glance. You can display the basic eye-catcher text in the following views, if you are using the block view format in your Web shop: Home page special offers and personalized product recommendations views Product details page for package components and associated products Cross-selling, up-selling, and accessory lists You can maintain the basic eye-catcher texts in the product master and display them in the catalog in the Web shop. In the product detail page for packages, the basic eye-catcher text is only displayed for package components. Effects on Customizing To enable the basic eye-catcher texts for products in your Web shop you need to carry out the following activities: 1. Maintain basic eye-catcher texts for the products as a basic text in the Notes area of the product master, or in the Text area for the product in the product catalog. Note, you should maintain the basic eye-catcher texts for packages in the product catalog. You should maintain the basic eye-catcher text for package components in the product master. ______________________________________________________________ SAP AG 193 SAP-System ______________________________________________________________ 2. Maintain Text Objects for the basic eye-catcher texts in Customizing for Customer Relationship Management under Basic Functions -> Text Management -> Define Text Objects and Text Types. Note, SAP delivers four standard text objects for your use: Text ID: EYEC - for the PRODUCT object Text ID: 0004 - for the PCAT_ITM object for the main product Text ID: 0005 - for the PCAT_ITM object for the package components and associated products Text ID: ECSA - for the PROD_SALES object 3. Create a text determination procedure in Customizing for Customer Relationship Management under Basic Functions -> Text Management -> Define Text Determination Procedure. Note, SAP delivers the following standard text determination procedures for your use: For text object PCAT_ITEM: S2 - for manual product assignment in the catalog S3 - for automatic product assignment in the catalog S4 - for automatic and manual product assignment in the catalog For text object PROD_SALES: PR_0004 - for products with the type material For text object PRODUCT: PR_0001 - or products with the type material 4. Assign an access sequence to the text determination procedure in Customizing for Customer Relationship Management under Basic Functions -> Text Management -> Define Text Determination Procedure. Note, SAP delivers the standard access sequence A3 for your use. See also For more information about the block view format, see Block View Format in Web Shop. 1.18.11 CRM-ISA-CFG Product Configuration Internet Sales 1.18.11.1 Configurable Products Attribute Display (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now determine how many characteristics should be displayed for configurable products in the Web shop. This function is already available in the shopping basket, but has now been extended to the catalog in the Web shop. You can enable this function now for the home page, product details, and product comparison pages. This means you can control how many of the maintained characteristics are displayed for the product. This means you have more control over what customers sees and enables you ______________________________________________________________ SAP AG 194 SAP-System ______________________________________________________________ to display important information for customers at a glance. Effects on System Administration You can only use this function if you have created a configurable product in the product master and set up configuration. Effects on Customizing To determine how many characteristics should be shown in the view for the configurable product you must carry out the following Customizing steps in Extended Configuration Management (XCM) for your Web shop. 1. 2. 3. Log on to XCM at http://<server:port>/b2c/admin/xcm/init.do. Choose Start -> General Settings -> Customer -> ui . Enter a value for the parameter configinfo.catalog.view to determine how many characteristics can be displayed in this view. For example, choose * to display all characteristics, or enter the value 2 to display only two characteristics. 1.18.11.2 Comparing Products (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Your Web shop customers can now see a side-by-side comparison of a group of products in a package. In this way you can support customers by giving them a summarized overview of the product features, and so help them to make a purchase that best meets their needs. The compare function is available in the product details page for the package, in the comparison window for products selected for comparison, and in the product overview page if you are using the list view format. When comparing package components the compare function is only available for comparison of products within one group. For example, a customer selects a package in the Web shop. Ten mobile phones are available in the package, but the customer does not know which mobile phone best suits his needs. To compare the details of these mobile phones, the customer selects the phones and chooses Compare Selection. The system displays those mobile phones selected with their various attributes and characteristics in a separate window. The customer uses the simplified overview and detailed product information to compare the phones. The customer then decides that only five of the ten phones are of interest to him. He selects these five phones and chooses New Comparison. The system then removes the other five phones, so the customer has a better overview of those products he is really interested in. ______________________________________________________________ SAP AG 195 SAP-System ______________________________________________________________ 1.18.12 CRM-ISA-BCS Business-to-Consumer Sales 1.18.12.1 Provider Shop and Interaction Center Mode (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now enable Interaction Center agents to log on to the provider shop to help customers who have a problem. The agent logs on using his own credentials, for example this could be an email address and password, selects the business partner he wishes to help, and enters the shop in the same mode as the customer. The agent can then determine what error has occurred during the customer session, and either help the customer to resolve the problem himself, or act on behalf of the customer to rectify the problem. If the customer has saved a shopping basket and is in change mode, he must log off from the shop for the agent to log on. If the customer is simply viewing a document, for example an order, then he just needs to close the document, but can remain logged on whilst the agent checks what has happened and makes the necessary changes to the order. This is not a co-browsing function, the customer cannot observe what the agent is doing in the Web shop. Effects on System Administration The Interaction Center agent must have the necessary authorizations assigned to his user, to enable the logon to the provider shop and customer selection. Effects on Customizing You enable the use of Interaction Center mode in Extended Configuration Management (XCM) for the provider shop: 1. 2. 3. Log on to http://<server:port>/b2c/admin/xcm/init.do. Choose Start -> Components -> Customer -> user -> callcentermode. Set the parameter CallCenterMode to True. See also The customer must have maintained a verification word to identify himself to the Interaction Center agent. For more information, see Verification Word for Web Shop Assistance. ______________________________________________________________ SAP AG 196 SAP-System ______________________________________________________________ 1.18.12.2 Price Eye-Catcher Text (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now display a price eye-catcher text for products in the Web shop, in addition to the basic eye-catcher text. The price eye-catcher text enables you to highlight important price information about a product or package, for the user to see and read at a quick glance. For example, if you have a package with various prices, depending on contract length, you can display the cheapest price for the package in the price eye-catcher text, to get the customer's attention. For example, From Euro 1 per month only! You can display the price eye-catcher text if you are using the block view and list view formats in your Web shop. The price eye-catcher text is always displayed above the normal price information in the block view, list view, and in the cross-selling, up-selling, and accessories list. If a price eye-catcher text is not maintained, the text will not be displayed. Effects on Customizing To enable the price eye-catcher texts for products in your Web shop you need to carry out the following activities: 1. Maintain Text Objects for the eye-catcher texts in Customizing for Customer Relationship Management under Basic Functions -> Text Management -> Define Text Objects and Text Types. Note, SAP delivers four standard text objects for your use: Text ID: PREY - basic price eye-catcher text for the PRODUCT object Text ID: 0006 - price eye-catcher text for the PCAT_ITM object for the main product Text ID: EPSA - price eye-catcher text for the PROD_SALES object Create a text determination procedure in Customizing for Customer Relationship Management under Basic Functions -> Text Management -> Define Text Determination Procedure. Note, SAP delivers the following standard text determination procedures for your use: For text object PCAT_ITEM: S2 - for manual product assignment in the catalog S3 - for automatic product assignment in the catalog S4 - for automatic and manual product assignment in the catalog For text object PROD_SALES: PR_0006 For text object PRODUCT: PR_0005 2. 3. Assign an access sequence to the text determination procedures in Customizing for Customer Relationship Management under Basic Functions -> Text Management -> Define Text Determination Procedure. Note, SAP delivers the standard access sequence A4 for your use. ______________________________________________________________ SAP AG 197 SAP-System ______________________________________________________________ 1.18.12.3 Recurring Prices in the Provider Web Shop (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now maintain recurring prices for package components in your Web shop. The advantage to this is that packages often consist of a cell phone, that is paid for once, and a contract, for which monthly charges occur. With the new flexible recurring prices option you can now maintain this different type of price for your products and display the two price types separately in your Web shop. For example, for the cell phone you maintain a one-time price and for the contract you maintain a recurring price. In the Web shop the two price types will be displayed independent of each other on the user interface. Products can only have one price type, either recurring or one-time. Effects on System Administration With this new pricing option, the basic pricing functionality offered in the Web shop is not changed. The information contained in SAP Note 824085 is still valid. Effects on Customizing You need to carry out the following Customizing settings to enable the use of recurring prices in your Web shop: 1. Create a condition type and assign a calculation type. In Customizing for Customer Relationship Management choose Basic Functions -> Pricing -> Create Condition Types. SAP delivers a standard condition type, 0PMR, for your use. This condition type is defined for a monthly payment. However, the following calculation types are also available for your use: M - Quantity - Monthly Price N - Quantity - Yearly Price O - Quantity - Daily Price P - Quantity - Weekly Price Depending on whether you have chosen List Price or IPC price determination for your Web shop you need to carry out the following Customizing settings: IPC Pricing Assign the condition type to a pricing procedure. In Customizing for Customer Relationship Management choose Basic Functions -> Pricing -> Create Pricing Procedures. SAP delivers a standard pricing procedure, 15lSAP, for your use. Condition type 0PMR is already assigned to pricing procedure 15ISAP. 2. ______________________________________________________________ SAP AG 198 SAP-System ______________________________________________________________ List Pricing Assign the recurring condition type, for example OPMR, to your product catalog variant. You do this in product catalog variant maintenance. You can assign more than one condition type to your catalog variant. This means that if the catalog variant contains products of different price types, for example one-time, monthly recurring, and yearly recurring, all these pricing types will be shown in the Web shop. 1.18.12.4 Special Price Display in the Web Shop (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now maintain special prices for products in your Web shop. The advantage to this is that you may wish to have two prices for a product; the normal sale price, and a special offer price. You want to promote this special price by showing customers the amount they can save in comparison to the special offer price. When this function is maintained the two prices for the product will be displayed alongside each other in the Web shop, with the normal price striked-through. Although both prices are displayed in the Web shop, only the special price will be sent by the system into the follow-on processes in the order and invoice. The normal price has no further relevance in the follow-on processes, the system simply disregards it. Effects on System Administration The special price function replaces the previous two-price functionality in the Web shop. In Shop Management you can only select either IPC or List prices for use in the Web shop, and not both at the same time. Other than this, there have been no changes made to the basic pricing functionality offered in the Web shop. The information contained in SAP Note 824085 is still valid. Effects on Customizing Depending on whether you have chosen List Price or IPC price determination for your Web shop you need to carry out the following Customizing settings: IPC Pricing Assign a calculation formula to a pricing procedure. In Customizing for Customer Relationship Management choose Basic Functions -> Pricing -> Create Pricing Procedures. SAP delivers a standard calculation formula, 1001, and a standard pricing procedure, 15lSAP, for your use. Assign the calculation formula, 1001, to an appropriate calculation level, in this pricing procedure. ______________________________________________________________ SAP AG 199 SAP-System ______________________________________________________________ This pricing procedure is assigned to the product catalog variant to determining pricing in the Web shop catalog. By assigning this calculation formula, the value will be displayed in the Web shop as a striked-through price. List Pricing Assign the attribute Special Price to a condition type you have already maintained for your product catalog variant. You do this in product catalog variant maintenance. You can now assign maintain two condition type with the catalog price type List Price for a catalog variant. One must, however, have the attribute Special Price assigned to it. 1.18.13 CRM-ISA-CNT Contracts 1.18.13.1 Contract Duration in Web Shop (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now display a contract duration field for customers to select the appropriate contract duration for their rate plans. The customer selects the length of the contract in the product detail page. The product prices are updated automatically by the system according to the contract duration selected by the customer. The contract duration is also displayed in the order status, print version, and order confirmation screens. Effects on System Administration You maintain the contract duration options, for example one year, two years, and so on, in the product master data for the rate plan. 1.18.13.2 Contract Negotiation: User Status Profiles (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. The button Change Status to Quotation and the according function has been added to the assignment block of sales contract items in the CRM WebClient UI. This button now allows the user to change the ______________________________________________________________ SAP AG 200 SAP-System ______________________________________________________________ user status of all selected items in the item list of a sales contract from 'Inquiry' to 'Quotation'. In the contract negotiation process, the vendor needs to verify and change the status of sales contract items and sales contract header. The status handling has been enhanced by two user status profiles for sales contract header and contract items in the CRM WebClient UI. Therefore, the status of contract items can now be displayed and changed in the contract item list and in the item details in the CRM WebClient UI. The following statuses are now available: 'Inquiry', 'Quotation', 'Accepted by Customer' and 'Rejected'. Effects on System Administration The following user status profiles are delivered with the standard system: CRMECOCN for sales contract header CRMECN_I for sales contract items Effects on Customizing You have made the necessary settings in Customizing for Customer Relationship Management, by choosing Transactions -> Basic Settings -> Define Transaction Type and Define Item Categories. See also For more information about the user status profiles, see Customizing for Customer Relationship Management at Web Channel -> E-Commerce -> Contracts -> Contract Negotiation. 1.18.13.3 Contract Negotiation: Status Display (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. The rejection status, quotation status, and inquiry status of a sales contract can now be displayed in the CRM WebClient UI. They can be displayed under any header on the header block of the sales contract overview page. The employee can now see if any items of the sales contract have been rejected, or if any items have been or are still in the quotation status or inquiry status. Effects on System Administration To make the fields Rejection Status, Quotation Status, and Inquiry Status visible in the header block on the sales contract overview page, you need to configure the application component BT121H_SLSC in the UI Configuration Tool. ______________________________________________________________ SAP AG 201 SAP-System ______________________________________________________________ See also For more information about new user status profiles in the CRM WebClient UI, see release note Contract Negotiation: User Status Profiles (New). 1.18.14 CRM-ISA-BAS Shopping Basket and Order Entry 1.18.14.1 Block View Format in Web Shop (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can adapt the display of products in your Web shop to create a block view of the products on sale, instead of the standard list view. The block view can be used for products displayed in the special offers, personalized recommendations, and product catalog area views. The block view is especially useful for the display of packages in the provider shop. The following functions are available: Display of package and package components in one view Separate hyperlink to package details pages Paging functionality for easy user navigation Field customizing by stylesheet definitions Each field in the block view has been defined as a separate area, allow you to customize the layout much more easily. You can, for example, hide and show these individual fields to meet you own specific requirements. Package details page grouping In the details page you can group package components in specific blocks to give the customer a better overview of the products involved in the package. You can label the group areas accordingly, for example you can create separate blocks for mobile phones and associated products. Eye Catcher text This text is displayed in the block view so that you can give your customers useful information to be read at a glance. For example, if the product is on special offer you can highlight this to the customer using the eye-catcher text. Use of Trex Server In this case the package components are read from the TREX server and not from the solution configurator. This speeds up performance in your Web shop. Display of one-time and recurring payments, and special prices You can display the various prices for products in the block view. For example, you can display the original and special offer price for a product. - - - - ______________________________________________________________ SAP AG 202 SAP-System ______________________________________________________________ Effects on System Administration You should be using the stylesheet b2c.css for your shop. The stylesheet b2c.css has been especially adapted to enable the use of the blockview and the customizing layout. Effects on Customizing The following customizing settings are avaialble for the block view in Extended Configuration Management (XCM): 1. 2. 3. Log on to XCM http://<server:port>/b2c/admin/xcm/init.do. Choose Start -> Components -> Customer -> ui. Adjust the following parameters to suit your requirements: CatalogArea.ShowAsBlockView Controls whether the products of a catalog area are displayed in a block view, or in a list view CatalogArea.BlockView.MaxRows Maximal number of rows used to display products in the catalog area CatalogSearch.ShowAsBlockView Controls whether the products of a catalog search are displayed in a block view, or in a list view CatalogSearch.BlockView.MaxRows Maximal number of rows used to display products in the catalog search PersonalRecommendations.ShowAsBlockView Controls whether the personal recommendations are displayed in a block view, or in a list view PersonalRecommendations.BlockView.MaxRows Maximal number of rows used to display the personal recommendations in the block view GlobalRecommendations.ShowAsBlockView Controls whether the global recommendations are displayed in a block view, or in a list view GlobalRecommendations.BlockView.MaxRows Maximal number of rows used to display the global recommendations in theblock view Catalog.BlockView.MaxColumns Maximal number of columns used to display the products in the block view Catalog.ListView.MaxItems Maximal number of items rows to be displayed in the list oriented view of the catalog Catalog.Page.MaxPageLinks Maximal number of page links displayed in the page link area - See also Basic Eye-catcher Text in Web Shop Recurring Prices in Provider Web Shop ______________________________________________________________ SAP AG 203 SAP-System ______________________________________________________________ Special Prices in the Web Shop Packages and Products with Dependent Components 1.18.14.2 Direct Debit Payment Method in Web Shop (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now enable a direct debit payment method in the provider shop. The new payment method is displayed alongside other payment methods in the Web shop checkout area. This function is enabled using business agreements. When the customer selects the direct debit payment method in the Web shop the system automatically creates a business agreement in the backend system, and enters the payment information into the business agreement. When the customer saves the order the system stores the payment information in the business partner master data and in the business agreement attached to the order in the backend system. At order header and item level, the system provides a reference to the business agreement where the payment data is stored. Effects on System Administration You must be using the standard SAP delivered provider order BUS2000265. Effects on Customizing To enable the use of direct debit in the provider Web shop you need to carry out the following Customizing steps: 1. 2. Enable the FICA flag in the business partner master data. Enable the storage of payment data in the business partner record and the use of business agreements. In the Web Channel Shop Management application for the provider shop, on the Transactions tab page, enable the flag Store payment information in business partner master data record. This flag enables the system to store the direct debit payment data in a business agreement, and then in the business partner master data. Enable the direct debit confirmation function in the Web shop bank transfer page. In certain countries, for legal reasons, the customer must confirm that he authorizes the direct debit . In the Web Channel Shop Management application for the provider shop, on the Transactions tab page, enable the flag User has to confirm collection authorization for debit memo payment. This flag enables the direct debit confirmation flag in the provider shop. 3. ______________________________________________________________ SAP AG 204 SAP-System ______________________________________________________________ 1.18.14.3 Save and Upload Shopping Baskets (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. The save shopping basket has been enhanced to include a new option for saving shopping baskets in the provider shop only. Previously, when you saved a shopping basket the system would create an order template and copy the basket items to the template. The customer could then reopen a saved basket, in the form of an order template. The system then transferred the products to a new basket for the customer to continue shopping. Now you can choose, instead, to enable the saving of the shopping basket itself, without the creation of an order template. The basket is saved in the CRM system and when the customer uploads the saved basket, the system reopens the saved basket for the customer to continue shopping. This function is particularly useful if a customer has selected and configured a package before saving the basket. If this is the case, the system automatically checks the items for configurability and pricing and updates the items accordingly. For example, if the customer selected an item on special offer when creating the basket, and the special offer is no longer available, the item will be updated accordingly. The following enhancements have been made in the user interface to support this enhanced function: The Save Shopping Basket As button has been renamed to Save Shopping Basket to underline the fact that the basket itself is being saved, and not a copy of the basket. Customers can maintain a description for the saved basket in the basket header to find saved baskets more easily. Saved baskets are displayed in the mini basket when a customer is logged on. Before the customer logs on, a link to the logon screen is displayed in the mini basket under the Saved Shopping Basket area. The customer simply clicks on the link to the appropriate basket to upload and open it. A trash icon is displayed next to each saved basket link in the mini basket, so that customers can delete the entire saved basket if necessary. If the save and upload basket function is enabled, there is no display of the My Shopping Basket link in the My Account page in the provider shop. - Effects on Customizing You enable the use of the new save and upload function for the shopping basket in the Shop Management application for your provider shop: 1. 2. Log on to the Shop Management application and navigate to the Transactions tab page. Select the flag Storing and loading of baskets allowed. ______________________________________________________________ SAP AG 205 SAP-System ______________________________________________________________ 1.18.14.4 Separate Payment Methods for Web Shop Purchases Use This release note is only relevant if upgrading from SAP CRM 5.0. Your Web shop customers have the choice of using more than one payment method for goods in their shopping basket. You can assign a category to products, and based on this the system determines whether one or two payment methods should be enabled for the purchase. You can assign one of the following two categories to your products: Goods These products are supplier-relevant. Rate Plan These products are contract-relevant. This function is useful if you are using packages in your provider shop, for example in the telecommunication area, where purchases often contain various items. For example, a customer selects a package, containing a mobile phone and a rate plan. The customer may wish to pay for the mobile phone by credit card, and for the rate plan, which is a recurring payment each month, by direct debit. In your product master you have maintained the mobile phone as an item which is supplier-relevant, and the rate plan as an item which is contract-relevant. In this case the system will offer the customer the choice of paying for the goods with two separate payment methods. The item categories of the chosen products are displayed in the Web shop in the checkout area. If only one category is available, only one payment method will be displayed. If both categories are available, a choice of two payment methods is offered for the items. Effects on System Administration This function is only available for provider shops. When you create and maintain your Web shops in Shop Management, make sure you select the provider shop scenario. Effects on Customizing 1. Assign item categories to usage types. In Customizing for Customer Relationship Management choose Industry-Specific Solutions -> Telecommunications -> Settings for Telecommunications Transactions -> Define Settings for Item Categories. Assign a usage type to each item category. You can choose between Item relevant to Supplier and Item Relevant to Contract. These categories are displayed as Goods and Rate Plan, respectively, in the Web shop checkout, check order, and print order pages. Note, if a product has the business type BUS 2000155 maintained in the product master, the system will automatically override any settings you make in this table. In this case, all items with this ______________________________________________________________ SAP AG 206 SAP-System ______________________________________________________________ business type will be regarded by the system to be contract-relevant. 2. Assign item categories to products in the product master data. 1.18.14.5 Shopping Basket (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. The shopping basket in the provider shop has been enhanced in the following ways: Save and upload of shopping basket function. For more information, see Save and Upload Shopping Baskets. A New Shopping basket button. Enables the customer to close the current basket and open a new one. Note, any unsaved items in the current open basket will be deleted. A Delete All button in shopping basket header. Enables customers to delete all items in the basket in one go, and continue shopping in the same basket. Saved Shopping Basket link in mini basket. Saved baskets are displayed in the mini basket when a customer is logged on. Before the customer logs on, a link to the logon screen is displayed in the mini basket under the Saved Shopping Basket area. The customer simply clicks on the link to the appropriate basket to upload and open it. The Your Description field has been moved to shopping basket header. The field Requested Delivery Date items has been added to the shopping basket header. Two price columns, one for basic fees and one for one-time payments, are displayed in the shopping basket according to the goods the customer selects. For example if a customer selects a package which contains a mobile phone, which is paid in a one-off payment, and a rate plan, which is paid on a recurring monthly basis, the prices will displayed in separate columns in the shopping basket. A Change link for packages products, package components, products with dependent components, and dependent components is available in the shopping basket. In the shopping basket there is no Delete buttons or Add to Favorites button for sub items. If you are in a package or package component and select the link to Product Options, the system will open an extended product details page. For more information, see Extended Product Detail Page. You cannot delete package components in the mini basket. You can only delete entire packages or individual products. - - - ______________________________________________________________ SAP AG 207 SAP-System ______________________________________________________________ 1.18.14.6 Technical Data in Provider Web Shop Order Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now use additional technical data in the order in the provider Web shop to store further useful technical information. This technical data is necessary for the sale and follow-up service processes. You determine which additional technical data is stored in the order, according to your company requirements. For example, in the telecommunication industry connection data, telephone number or SIM card number, would be useful additonal information to have. The technical data is displayed in the shopping basket during order creation and in the check order, print order, and order status pages. Effects on System Administration Enable the use of the standard delivered provider order (BUS2000265). Effects on Customizing To enable the use of additional technical data in the provider Web shop you need to carry out the following Customizing steps: 1. Assign set types and service types. The service type defines which set types and attributes are used for technical data maintenance. In customizing for Customer Relationship Management choose Web Channel -> E-Commerce -> Settings for Technical Data -> Assign Set Types to Service Types. Enter the service type in the product master data for each product which should contain additional technical data. Enable technical data for the provider Web shop in Extended Configuration Management (XCM): a) b) c) Log on to http://<server:port>/b2c/admin/xcm/init.do. Choose Start -> General Settings -> Customer -> ui -> uidata. Set the parameter technicalDataSupport to True. 2. 3. ______________________________________________________________ SAP AG 208 SAP-System ______________________________________________________________ 1.18.15 CRM-ISA-AUC Web Auction 1.18.15.1 B2C Checkout in Selling Via eBay (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. The checkout via B2C Web shop in Selling via eBay allows vendors to use their existing B2C Web shop infrastructure to provide their customers with a secure checkout environment. The checkout process of won auctions in the B2C Web shop has been enhanced. The B2C checkout now allows the vendor to use the B2C Web shop marketing features like displaying cross-selling items and accessories together with the won auction items to be checked out. This means that that customer can now add additional products from the product catalog to the shopping basket and define the quantity and unit of quantity of these products. Effects on Customizing You have made the necessary settings for the pricing procedure in Customizing for Customer Relationship Management, by choosing Basic Functions -> Pricing -> Define Settings for Pricing -> Create Pricing Procedure and Create Condition Types. 1.18.16 CRM-ISA-UM User Management 1.18.16.1 Internet User in Account (new) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now create and maintain Internet users in the Account. Previously, you assigned the role Internet User to a user in the business partner transaction, in your backend SAP CRM system. This function has been moved ito the Account data maintenance in the new user interface. ______________________________________________________________ SAP AG 209 SAP-System ______________________________________________________________ 1.18.17 CRM-ISA-TEC Technical Infrastructure 1.18.17.1 Extended Product Detail Page (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The product detail page has been extended to enable different user interface (UI) displays according to the types of products being displayed or changed. This function is necessary for the new package and products with dependent componentsmodeling, which is used, above all, in the telecommunications industry. These newly modeled products require a special configuration, which needs to be displayed on the UI. The UI displays for the product details have been enhanced as follows to meet the configuration requirements: Display of sales packagesand combined rate plans Display of package components and groupings. All package components are displayed for the package product. However, only the cross-selling products, up-selling products, and accessories, for the main package product are displayed, and not those for the package components. Display of hierarchical dependent components Radio buttons for component selection Update Selection button and automatic update selection function for the recall of the Solution Configurator when component selection is changed. You can determine automatic or manual package explosion using the update selection and automatic update selection function in Customizing. For more information, see Customizing key block below. Current Total display for selected products Display of prices for all alternative products in the component list. For example, three mobile phones are available in a package. The price for each phone is displayed in the product details page, not only the price for the current selected mobile phone. - - - Display of package components No display of cross-selling, up-selling, down-selling products, and accessories No Add to Basket function No Add to Favorites function Display of Back button Display of information as to which main product the displayed component is assigned ______________________________________________________________ SAP AG 210 SAP-System ______________________________________________________________ - Change mode for sales packages and combined rate plans from the basket A special UI is displayed when a customer selects the Change button for these products whilst in the shopping basket. No Add to Basket function No Add to Favorites function Display of Back to Shopping Basket button Effects on Customizing You can determine whether a package explosion is automatically carried out by the system, when the solution configurator is called, or manually carried out using the Update Selection button. You set this in Extended Configuration Management (XCM) as follows: 1. 2. 3. See also For more information about the new product modeling, see Packages and Products with Dependent Components. Log on to http://<server:port>/b2c/admin/xcm/init.do. Choose Start -> Components -> webcatalog -> webcatdefault. Set the parameter Catalog.Package.AutomaticExplosion to True for automatic explosion, and to False for manual explosion of a package. 1.18.18 CRM-ISA-SHA Shop Management 1.18.18.1 Verification Word for Web Shop Assistance Use This release note is only relevant if upgrading from SAP CRM 5.0. Your customers can maintain a verification word in their personal data in the Web shop. This verification word enables them to identify themselves to an Interaction Center agent when they call for advice or information when using the Web shop. The customer maintains the verification word when registering, or at a later time when updating their personal data. Effects on Customizing ______________________________________________________________ SAP AG 211 SAP-System ______________________________________________________________ To enable the use of a verification word for Web shop customers, you need to make the following customizing settings: 1. Define the identification type to be used to identify customers when calling the Interaction Center. In Customizing for Customer Relationship Management choose Web Channel -> Basic Settings for E-Commerce -> Define Identification Type for Verification Word. Enable the verification word field in the Web shop using the Extended Configuration Management (XCM) application for your provider shop: a) b) c) Log on to XCM at http://<server:port>/b2c/admin/xcm/init.do. Choose Start -> General Settings -> Customer -> ui. Set the parameter ShowVerificationWord to True. 2. 1.19 CRM-ISE 1.19.1 CRM-ISE-COM Internet Service Complaints and Returns 1.19.1.1 E-Service: Extended Complaints and Returns (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. The following enhancements to the Extended Complaints and Returns application of E-Service are now available: Attachments in complaints and returns For example, the manufacturer requests justification of a complaint to speed up the approval process, and the customer wants to submit a digital image of the damaged part or other evidence to support his or her case. The customer can now attach files on item level when creating a complaint or a return. If a complaint item or return item was rejected, no matter whether it was rejected manually or automatically, the customer can add further attachments before resubmitting it. Reference to handling unit in complaints For example, a customer receives a handling unit (HU) that is damaged or incomplete, and he or she wants to create a complaint with reference to that HU. When creating a complaint, the customer can now reference an HU. He or she can either enter the HU items directly into the complaint or display the complete HU list and copy all or some of the HU items from that list into the complaint. In both cases, the system checks whether the HU belongs to the customer or to the business partner hierarchy of the customer. It then determines the item and item quantity from the invoice that corresponds to the HU. When copying from a list, the customer can select a complaint type, complaint item type, and reason code as defaults for all complaint - ______________________________________________________________ SAP AG 212 SAP-System ______________________________________________________________ items. Display of inspection results in complaints and returns If the customer returns new or used parts to the manufacturer, the manufacturer inspects the parts and enters the inspection results in an inspection confirmation. Depending on the inspection results, the customer is refunded in full or in part, which is why he or she is interested in viewing the inspection results, especially those that are pricing-relevant. When displaying a return, the customer can now view the inspection results for each return authorization item and check decision codes, defect codes, and effort codes. Entry of exchange group in used part returns For example, a customer wants to create a used part return for an engine and is not sure of the correct product ID, so he or she wants to enter a collective term rather than a specific ID. The manufacturer can now group several products into an exchange group, thus allowing the customer to enter the name of the exchange group only. From the name of the exchange group, the system then determines the corresponding product. Entry of handling unit and packaging material in used part returns When creating a used part return, the customer can now enter, on item level, the handling unit that he or she intends to use for returning the parts, as well as the packaging material. Scrapping confirmations To reduce costs or to avoid shipping of hazardous parts, a manufacturer may prefer scrapping of items to take place at the customer's site rather than at the manufacturer's site. In that case, the manufacturer issues a scrapping authorization rather than a return authorization. Not until the customer confirms the scrapping is he or she credited. From the Welcome page, the customer can now call up a list that may contain scrapping items from different transactions. In this list, he or she can select the items that were scrapped and submit this information to the manufacturer. SPL-requested returns Due to a delivery bottleneck for a certain part, the service parts logistics (SPL) owner, that is, the manufacturer, searches for this part among the customers using a campaign. Each customer who has this part in stock can create a return request with reference to this campaign and get a refund for the returned parts. To find such a campaign, the customer can now search the reference transactions for the SPL return request and create a return with reference to the desired request, using the Copy function. He or she can also create a return of type SPL-Requested Return from the Welcome page and enter the ID of the SPL return request directly in the new return. - - - - ______________________________________________________________ SAP AG 213 SAP-System ______________________________________________________________ 1.19.2 CRM-ISE-WBF Web Forms 1.19.2.1 New Link Type for Web Requests (Changed) Use This release note is only relevant if upgrading from SAP CRM 5.0. As of SAP CRM 5.1, the link type for the associated CRM transaction is changed in the Web Requests component. The migration program CRM_WEBREQ_LINKS_MIGRATE is provided to migrate already productive Web requests to Release CRM 5.1. Effects on Existing Data This change affects Web requests that you created in the releases prior to Release 5.1 (for example, CRM 4.0, CRM 5.0). Once you upgrade to CRM 5.1, the call of the Web request data linked with a CRM transaction is no longer supported. After migration to the new link type, this error situation is corrected. See also SAP Note 983481 1.19.2.2 External Interface for Web Requests with Attachments (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. As of Release SAP CRM 5.1, you can include files as attachments for Web requests that are created using the external interface, in other words offline. The attachments are linked with the generated CRM business transaction and can be called from there. The sample program CRM_WEBREQ_EXTERN_WITH_UPLOADA is provided for test purposes. For more information, see the function module CRM_WEBREQ_EXTERN_CREATE_DOC. ______________________________________________________________ SAP AG 214 SAP-System ______________________________________________________________ 1.19.2.3 Short textSAP Interactive Forms by Adobe for Web Requests (New)UseAs of this Release with SP02, the use ofSAP Interactive Forms by Adobe is supported in the Web Requests component. This means thatyou can use request forms that are based on Adobe Software as analternative to BSP-based request forms (that are still available) forrequest category views.SAP Interactive Forms by Adobe is completely integrated in SAP NetWeaver.You perform layout processing usingthe Adobe LifeCycle Designer that isintegrated in the SAP System. Processing is user-friendly and does notrequire any specialist programming knowledge. The Adobe-based requestform is displayed in a Web Dynpro framework program.EXISTING_DATAEffects on Data TransferSYSTEMADMINISTRATIONEffects on Customizing#11;&SEE_ALSO&For more information about SAP Interactive Forms by Adobe for WebRequests, see SAP Library under Web Requests. 1.20 CRM-RPL Resources Resource Planning for Personnel 1.20.1 Resource Planning (Enhanced for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The following Business Add-Ins (BAdIs) are now available in resource planning: The connection of resource planning to the scheduling engine is now influenced by BAdI Connecting RPA to Scheduling Engine (CRM_WFD_RPA), in addition to the existing BAdI Interface to Scheduling Engine (CRM_SRV_SDL): BAdI Connecting RPA to Scheduling Engine connects the resource planning application (RPA) to the scheduling engine WFM Add-On or, optionally, to an external scheduling engine. BAdI Interface to Scheduling Engine connects other SAP CRM applications to the WFM Add-On or to an external scheduling engine. For example, service order information that is relevant for resource planning is transferred to the scheduling engine via this BAdI. - You can use BAdI Service Arrangements (CRM_WFD_ARR) to publish service arrangement information for service providers and employees for other components and external systems at saving. You can use BAdI Context Menus for Resource Views (CRM_WFD_CTXT) to integrate the following context menus in the weekly resource view and the Gantt chart of the resource planning application: Weekly view Context menu for resources Gantt chart - ______________________________________________________________ SAP AG 215 SAP-System ______________________________________________________________ Context menu for resources and for assignments Effects on Data Transfer Resource planning requires elements from the workforce deployment server that is part of the WFM Add-On 2.0. Note that as of SAP CRM 2007 SP02 service-order-based and project-based resource planning requires the WFM Add-On 2.0 SP12. For more information, see the SAP note 1115278. Effects on Customizing For more information, see Customizing for Customer Relationship Management under Workforce Deployment -> General Settings for Service Resource Planning -> Business Add-Ins (BAdIs). 1.20.2 Project-Based Resource Planning (New for SP02) Use This release note is only relevant if upgrading from SAP CRM 5.2. You can now use resource planning to schedule resources for cProject role demands. This means, you can use resource planning to carry out either service-order-based scheduling or project-based scheduling with a number of resources. You can do the following: Maintain the availability, skills, job function, and service area of the internal and external resources that you can schedule for a job Locate the resources that best meet the demands You can use resource planning to comply with promised service level agreement (SLA) dates, meet emergencies, and maximize resource use. Once you have assigned the resource to a demand, you can notify the resource through: Groupware The groupware notification is only available for internal employees. Any available channel; telephone, text message, or e-mail SAP CRM Mobile Service Note that you can use resource planning either for project- or for service-order-based scheduling, but not for both. The following features are additionally available to fullfill project-based scheduling: You can create capacitive and concrete assignments for cProject roles. When creating concrete assignments for cProject roles, you can either create assignments for a single instance or define a recurring appointment. ______________________________________________________________ SAP AG 216 SAP-System ______________________________________________________________ - Before you create an assignment, you can define possible candidates in candidate management. This is especially useful for long-term projects. You can create concrete assignments from your groupware calendar. This function is only available for internal employees. You can use multilevel staffing. You can navigate from the SAP CRM WebClient UI to the cProjects application, by choosing Resource Planning -> cProjects in the navigation bar. You can navigate from the resource planning application to the role details in cProjects by clicking the project number in the demand search result list and in the project demand details in the proposal list for resources. Effects on Data Transfer The service resource planning solution requires elements from the workforce deployment server that is a part of the WFM Add-On 2.0. Note that as of SAP CRM 2007 SP02 service-order-based and project-based resource planning requires the WFM Add-On 2.0 SP12. For more information, see the SAP note 1115278. Effects on Customizing To use service resource planning, you have to make the settings in Customizing for Customer Relationship Management under Workforce Deployment -> WFD Server, Service Resource Planning and General Settings for Service Resource Planning. 1.20.3 Service Resource Planning (New) Use This release note is only relevant if upgrading from SAP CRM 5.2. You can use the resource planning solution to carry out service order-based scheduling with a limited pool of resources by: Maintaining the availability, skills, job function, and service area of the internal and external resources that you can schedule for a job Locating the resources that best meet the demands of your service order You can use resource planning to comply with promised service level agreement (SLA) dates, meet emergencies, and maximize resource use. Once you have assigned the resource to a demand, you can notify the resource through: Groupware Any available channel; telephone, text message, or e-mail ______________________________________________________________ SAP AG 217 SAP-System ______________________________________________________________ - SAP CRM Mobile Service Effects on Data Transfer The service resource planning solution requires elements from the workforce deployment server that is a part of the WFM Add-On 2.0. Effects on Customizing To use service resource planning, you have to make the settings in Customizing for Customer Relationship Management under Workforce Deployment -> WFD Server, Service Resource Planning and General Settings for Service Resource Planning. 1.21 CRM-MKT Marketing 1.21.1 Pertinent Master Data Changes (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use the function for pertinent master data changes (PMDC) to evaluate changes to certain master data, and apply these changes to certain marketing objects. The system monitors changes to master data in SAP CRM and to master data in SAP ERP that is replicated to SAP CRM. You evaluate whether you want to apply the changes to the affected marketing objects, or not. You can also exclude marketing objects from being updated in this manner by the system. The PMDC function allows you to do a test run, so that you can simulate the updates to the marketing objects. The system generates a log that records the updates that it makes, and also an error log. You can use the PMDC function to reflect changes to the following: Product master data Product hierarchies List prices Price lists Partner/product ranges (PPRs) Listings You can use the PMDC function for the following object types: Trade promotions (object types TPM, TPT) ______________________________________________________________ SAP AG 218 SAP-System ______________________________________________________________ 1.21.2 Personalized Mail (Changed) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can create personalized mail for use with internet mail, fax, and short message service (SMS). 1.21.3 Trade Promotion Upload Using SAP Exchange Interface (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. There is a new function available to upload trade promotion management (TPM) data from a non-SAP system to SAP CRM using SAP Exchange Infrastructure (SAP XI) technology. You require the following software components for this new function: SAP_BW 700 BBPCRM 5.1 SAP_XI To create new trade promotions, new TPM data is transferred from the non-SAP system using SAP XI to SAP CRM. Planning services in SAP NetWeaver Business Intelligence (SAP NetWeaver BI) and Remote Function Call (RFC) destinations enable the transfer of both planning data and master data from SAP CRM to SAP NetWeaver BI. The data flow is a one way pull scenario from the non-SAP system to SAP CRM. Should the upload fail, an error message is available in the application log (transaction SLG1), and the file has to be corrected and reprocessed. Following the successful upload of new trade promotions, the system status is set to Created. SAP XI uses a file adapter to collect the data in flat files in a specific folder using File Transfer Protocol ______________________________________________________________ SAP AG 219 SAP-System ______________________________________________________________ (FTP). The source documents are converted into XML format. You can upload the following TPM data that has been created or deleted in a non-SAP system to SAP CRM: Basic data Products Product categories Business partners System status (is set to Created) Trade spends Planning data Notes Easy Enhancement Workbench (EEW) customer fields that you can add to existing field structures If the data contains errors or is missing information (for example, if the product is not valid), SAP CRM rejects the entire marketing object and returns an error message to SAP XI, which you can handle in SAP CRM. You can also check for errors in the upload logs in SAP CRM. We recommend you schedule an upload once a week or once a month, for example. Effects on Customizing To enable the data flow between SAP XI and SAP CRM, you complete the following activities: Define the master data in SAP CRM Define the master data in SAP BI Complete the relevant Customizing activities for trade promotions in the SAP Implementation Guide (SAP IMG) for SAP CRM Define the BI Content in SAP BI for layouts and profiles. There are no new or modified IMG activities with this new function. An HTTP connection has to be established from SAP XI to SAP CRM. The creator of the trade promotion is the user assigned to the HTTP connection. 1.21.4 Deals Use ______________________________________________________________ SAP AG 220 SAP-System ______________________________________________________________ This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can now assign product categories and product groups to a deal. 1.21.5 TPM and Account Planning: BI 7.x Templates (Enhanced for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The integration of BI reports into the CRM WebClient UI, and therefore into trade promotion management (TPM) and account planning, is no longer restricted to BI 3.x templates, but now also includes BI 7.x templates. BI 7.x templates are executed by the Java runtime environment and were introduced with NetWeaver 2004s. Reports that have been migrated to BI 7.x templates are stored in the same namespace as previously. To use BI 7.x templates in TPM, you need to enter a BI report ID in Customizing for Customer Relationship Management under Trade Promotion Management -> Key Figure Planning -> Define Parameters for SAP NetWeaver BI Analysis. You can find this ID in Customizing for Customer Relationship Management under Trade Promotion Management -> Key Figure Planning -> Display SAP NetWeaver BI Reports in CRM. To use BI 7.x templates in account planning, you need to enter a BI report ID in Customizing for Customer Relationship Management under Account Planning -> Key Figure Planning -> Define Parameters for SAP NetWeaver BI Analysis. You can find this ID in Customizing for Customer Relationship Management under UI Framework -> UI Framework Definition -> Display SAP NetWeaver BI Reports in CRM. ______________________________________________________________ SAP AG 221 SAP-System ______________________________________________________________ 1.21.6 Purchasing Products and Services in Marketing Projects (New for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. In marketing projects, you can purchase products and services. By default, a purchase requisition is created directly in SAP ERP, when you set the status of the marketing project to Released. When purchasing products and services, the following options are available to you: You can enter the supplier and the delivery address, for example. You can enter both internal and external products. You are informed about the current status of the purchase requisition. The actual costs are displayed at header level in the assignment block. You can use the purchase requisition ID in SAP CRM to go to the purchase requisition. You can use the purchase order ID in SAP CRM to go to the purchase order. Budget Check Depending on your Customizing settings, you can compare the costs when purchasing products and services in a trade promotion or a campaign, with the respective planning costs. You can thereby perform a budget check. If the order costs are higher than the planning costs, you receive a warning. 1.21.7 Trade Promotion Agreements (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use trade promotion agreements with trade promotion management (TPM). A trade promotion agreement is a non-binding document that outlines proposed events and activities for a specific account, product, and date range. For example, you could create a trade promotion agreement for 2008 for a key account at the regional account level. The agreement would reflect an individual product, product group, or product hierarchy. Growth rebates and everyday low pricing, for example, could be explained in the agreement. Once you have created the trade promotion agreement, you can: ______________________________________________________________ SAP AG 222 SAP-System ______________________________________________________________ - Use the agreement as the basis for creating a new trade promotion Create a trade promotion and assign it to an existing agreement Copy and paste the agreement to Microsoft Word® or Microsoft Excel® When you save the trade promotion agreement or change the agreement status, the system performs an overlap check to ensure that there are no overlapping trade promotion agreements. 1.21.8 Mass Copy, Mass Change, Mass Approval (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can perform mass copy, mass change, and mass approval in marketing for trade promotions. Advanced copy and mass change are available for campaigns and marketing plans. For campaigns and marketing plans, you can use mass change and advanced copy to modify attributes such as product, status, date, and employee responsible. For trade promotions, you can use mass change and mass copy to change or copy selected trade promotions based on trade promotion date, status, product, employee responsible, planning account, spend value, and causal. For example, a key account manager (KAM) wants to copy last year's trade promotions for a given account as the basis for the coming year's activities. The KAM would conduct a search for all relevant trade promotions. From the search results list, the KAM would select the desired trade promotions, perform a mass copy, and then shift the dates. The KAM could also schedule mass copy and mass change batch jobs, which run in the background. The KAM could monitor the batch jobs using monitoring tools. The one-click integration of trade promotions in the Marketing Calendar allows you to view them from within the Marketing Calendar. You can mass change dates by selecting bars in the Gantt chart and dragging. The relative time displacement between bars does not change. For increased efficiency, you can view the search results in the editable list, allowing you to make edits from within the results list. Mass approvals are achieved in a separate screen. This screen allows you to drill down into an object for more information, as well as view key figures. The system runs a promotion guideline check to ensure that trade promotions stay within established guidelines, and also checks for fund availability. You can approve trade promotions by selecting several and then clicking a single pushbutton. ______________________________________________________________ SAP AG 223 SAP-System ______________________________________________________________ See also Trade Promotion Guidelines 1.21.9 Enhancements in CRM Marketing (New and changed) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The following enhancements are available for CRM Marketing in this release: You can now add an existing campaign to an existing marketing plan both from the hierarchy tree as well as from the assignment block. The top-level field in a hierarchy tree can also now be edited and you can assign marketing projects at this level as well. It is possible to link directly from a marketing project to cFolders. Campaign response recording is available as an improved and more streamlined application. It is possible to do response recording, for example, based on entering a personalized response code. In this case, the business partners contacted are assigned automatically. It is also possible to assign 'unknown' business partners based, for example, on response inlays from magazines. You can search for coupons using a clearing house as a search criteria for your coupon code. You can make mass changes and mass copies of campaign or marketing plans using the Mass Change and Advanced Copy buttons and choosing the criteria by which you want to make the changes. - - The following enhancements have also been made in Leads: You can now search Leads by Partner Function, Partner Name, and Partner ID You can assign partners to products within the lead object, and can search by products and in leads in the search screen You can now make subsequent assignments in the Transaction History assignment block of Leads ______________________________________________________________ SAP AG 224 SAP-System ______________________________________________________________ 1.21.10 Overlap Checks (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use overlap checks with trade promotion management (TPM). Overlap functionality compares a selected trade promotion against other trade promotions in the system to check for overlaps. The checks are triggered when you save a trade promotion and when you change the trade promotion status. Checks are made against a customizable set of attributes, such as account, product, or dates. There are two kinds of overlap check: Direct A comparison of a selected trade promotion and other trade promotions in the system The system checks only direct matches in the account and product attributes. Hierarchical A comparison of a selected trade promotion with other trade promotions in the system that considers hierarchical dependencies within account and product attributes, in addition to direct matches This kind of overlap check can be run as a batch job, due to the potentially considerable amount of data to be processed. - 1.21.11 Scheduled Claims (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use scheduled claims with trade promotion management (TPM). A scheduled claim is a regular payment where the payment schedule is determined by the business user. This is useful for automating the claims process in cases where the brand owner expects to perform regular payments. It is also useful for controlling when claims balances appear in financial accounting figures. A scheduled claim is always an invoice claim. The scheduled claims assignment block lists all scheduled claims created for a trade promotion. Each line in the assignment block represents one scheduled claim, which itself is composed of one or more trade spends. You can do the following with scheduled claims: Define the payment schedule Set the time period and the interval (in units of days, weeks, or months) for scheduled claim ______________________________________________________________ SAP AG 225 SAP-System ______________________________________________________________ processing. Create the scheduled claim either immediately or in the background as part of a batch process A batch process is useful when there are a number of scheduled claims to create for the specified period. Delete or cancel scheduled claims - Effects on Customizing To create scheduled claims in trade promotion management, you must make the following setting in Customizing for Customer Relationship Management: Define the process type you want to use for scheduled claims by choosingMaintain Process Types for Invoice Claims. 1.21.12 Trade Promotion Templates (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use trade promotion templates with Trade Promotion Management (TPM). You use templates to accelerate the creation of trade promotions. Rather than simply creating a new trade promotion from an existing one, you can create a template as separate object for the sole purpose of expediting the creation of trade promotions. For example, if you create a significant number of trade promotions every year for a given account, you could create a trade promotion template that contains the account information. You can use the template maintenance application in the following ways: Create a template in the template creation application. Create a new template from an existing template. Generate a new template from a trade promotion. Create a trade promotion from a template. Create a trade promotion from a template using the Marketing Calendar. ______________________________________________________________ SAP AG 226 SAP-System ______________________________________________________________ 1.21.13 Tiered Growth Rebates (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use tiered growth rebates with trade promotion management. A tiered growth rebate is an incentive scheme offered to retailers based on performance levels. For example if sales revenue increases by 10% over last year, the retailer receives a rebate of 1,000 USD; if sale revenue increases by 8% over last year, the retailer receives a rebate of 2,000 USD. Each tiered growth rebate uses a calculation method and consists of a set of tiers. The calculation method defines how the rebate amount is obtained, and each tier associates a range of performance values with a specific rebate amount. Effects on Customizing Tiered growth rebates require the following customizing settings in the Implementation Guide (IMG) of SAP Customer Relationship Management (SAP CRM): Add a tiered growth rebate type to the list currently defined for tiered growth rebates, or modify the combination of variables associated with a tiered growth rebate type. A tiered growth rebate type is a unique identifier for a specific combination of base dimension, comparison dimension, tier type, rate type, and calculation method. Add a tiered growth rebate type by choosing Define Tiered Growth Rebate Types. Associate a trade spend combination (spend type, spend category, spend method) with a tiered growth rebate type, or modify the trade spend combination associated with a tiered growth rebate type. Do this by choosing Define Trade Spend Combinations for Tiered Growth Rebates. Associate the names of the key figures retrieved from SAP NetWeaver Business Intelligence (SAP NetWeaver BI) for tiered growth rebates with the corresponding names used in SAP CRM. Do this by choosingDefine BI Content. - - 1.21.14 Enhancements in Trade Promotion Management (New) Use ______________________________________________________________ SAP AG 227 SAP-System ______________________________________________________________ This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. Roles There are three preconfigured business user roles that are available for trade promotion management. These enable you to clearly identify the different tasks that are involved in the trade promotion management processes in a large consumer goods organization. The three roles are: 1. 2. 3. Trade Claims Professional (New) Models the claims and deductions analyst role Trade Finance Professional (New) Models the trade finance/sales finance role TPM Professional (Enhanced) Models a key account manager role Functions and Features The following are the enhancements to trade promotion management: Funds Management and Funds Integration Claims Management and Claims Integration Pricing Simulation Indirect Relationships Marketing Calendar Enhancements Planning Services You can now view planning information not only in the CRM WebClient User Interface (UI) but also in the new planning UI based on Flex technology. There are two planning components available on the same page. This functionality is used by the validation sheet, for example. Target Groups and Product Segments You can specify a target group for a trade promotion and view the hierarchy node associated with that target group. After you release a trade promotion, you can track any changes to target groups and product segments during the validity dates of the trade promotion through new change log assignment blocks. Attribute Filters Listings in Product Proposals Significant Uplifts and Transfer to Advanced Planning and Optimization Effective Dates in Trade Promotions and Deals Agreements Causals Trade Promotion Critical Changes Promotion Guidelines Trade Promotion Versions - - ______________________________________________________________ SAP AG 228 SAP-System ______________________________________________________________ - Cross-Order Caps for Off-Invoice Trade Spends Date Ranges and Trade Spends You can define additional search date ranges and extract date ranges to use with trade promotions and deals. You can relate a date range to a trade spend so that they can be pre-populated in the trade promotion planning page when you create a trade promotion. Planning for Display Pallets You can include display pallets in trade promotion planning. Direct Scan-Based Accrual Rates Trade Promotion Editable List You can use the Trade Promotion Editable List search to edit individual trade promotions from the list of search results. Working Context Long-Term Trade Promotions Mass Change, Copy, and Approval of Marketing Objects Overlap Checks Templates for Trade Promotions Tiered Growth Rebates Scheduled Claims Editable Overview Pages for: Account Defaults Deals Trade Promotion Elements Trade Promotions - - - TPM BI Extractors Effects on Customizing For more information on IMG changes to Customizing for Customer Relationship Management, see New, Changed and Removed IMG Activities in SAP CRM 2007. ______________________________________________________________ SAP AG 229 SAP-System ______________________________________________________________ 1.21.15 Take Rates (new) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. Take rates enable you to plan and accrue variable billback trade spends based on an expected volume rather than a shipped volume. See also Accruals Batch Processing Framework 1.21.16 Attribute Filters (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. When you plan a trade promotion, the values you select in specific fields affect which values you can select in the other fields of the object. The value selections in one field filter the values that are available in other fields. This is dependent on the settings you make in Customizing. The fields whose values you can filter through your Customizing settings are: Planning profile groups The selection of planning profile groups that is available for end users is based on the selection they make for the account type and the product planning basis. The Indirect checkbox also filters the planning profile groups that are relevant for indirect trade promotions. Trade spends (spend type, spend method, and spend category combination) The selection of trade spends that is available for end users is based on the selection they make for the trade promotion type. It is only possible to select trade spends that have been configured for condition generation. For example, if an everyday low price discount has been configured only for a trade promotion type of #Long-Term#, it will only be visible for trade promotions of this type. Which status values the user can see in marketing planning and account planning Search results The search results lists in marketing planning and account planning show statuses that are relevant to the user such as statuses that describe the lifecycle of the trade promotion. Trade promotion and account plan details The details pages of the trade promotion and the account plan show statuses that are relevant to - - - ______________________________________________________________ SAP AG 230 SAP-System ______________________________________________________________ the user such as statuses that describe the lifecycle of the trade promotion. Statuses in general You can customize which statuses are shown to the user in general so that whereever the status of the marketing object is shown, the user sees only those statuses that are relevant. Effects on Customizing The following IMG activities are enhanced to filter selection options: Define Planning Profile Groups Define Condition Generation Assign Condition Generation Type 1.21.17 Causals (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. Causals are used in trade promotion management (TPM) or market development fund (MDF) initiatives to capture how products are promoted to customers. Therefore, causals capture consumer-facing data such as promotional price (for example, two for $3.99), feature ad, store display (type and location), media, and so on. Causals are grouped into a set of data and appear in a new assignment block on the user interface. This set of data is created for the product(s) that are assigned to a trade promotion and can be maintained at the individual product, category, group, or segment level. A causal can have many types, and each causal type captures a different way of promoting a product. The causal type is mapped to an expense type. ______________________________________________________________ SAP AG 231 SAP-System ______________________________________________________________ 1.21.18 Trade Promotion Critical Changes (new) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. A trade promotion critical change is assessed when changes are made to an approved version of a promotion's attributes or key figures to an extent that the basis upon which the approval status was granted no longer applies. Critical changes are assessed based on defined business rules to ascertain if changes made to a trade promotion's attributes since the last time it was approved, are critical or not. The new trade promotion attribute values are compared to the values in the last approved version of the trade promotion. If the values have changed and are deemed critical according to the established rules, the trade promotion will be subject to re-approval. Effects on Customizing You can define settings for trade promotion critical changes in Customizing for Customer Relationship Management, by choosing Trade Promotion Management -> Basic Data-> Rules Setup. See also Trade Promotion Guidelines Trade Promotion Versions 1.21.19 Editable Overview Pages (Enhancement) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. There are editable overview pages for the following Marketing objects: Account Defaults Deals Trade Promotion Elements Trade Promotions Lead Lead Templates There is an editable overview page for the following Sales object: Opportunity ______________________________________________________________ SAP AG 232 SAP-System ______________________________________________________________ There are editable overview pages for the following Partner Channel Management objects: Activity (Appointment) Activity (Sales Call) Activity (Task) Lead Opportunity Display and Edit When you display any of the above objects, the Save and Cancel pushbuttons are inactive. You switch to edit mode by clicking Edit in the assignment blocks. If you enter data and do not save it, or if you switch from display to edit, the Save and Cancel pushbuttons are active. Hierarchy View You can view the hierarchies for deals, trade promotion elements, and trade promotions under General Data on the Details page by clicking Show Hierarchy. 1.21.20 TPM Funds Integration (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. Funds integration provides extensions to the SAP CRM trade promotion management (TPM) solution to incorporate CRM trade claims and funds management functions into the TPM solution. You can associate funds to a trade promotion for planning purposes. You have the option of automated or manual funds association. In automated funds association, the system uses rules set up in the funds determination and availability check profiles to pick the relevant funds for the promotion. You can also associate the funds manually at the root, product, trade spend, or trade spend product level. When you associate the funds manually, the system enforces the same rules used for automated association to restrict the set of funds that can be associated to a promotion. Additionally, you can: Associate a funds plan to the trade promotion The funds plan association applies a filter to the fund determination profile to determine the set of funds available when planning the trade promotion. It also ensures that the currencies of the ______________________________________________________________ SAP AG 233 SAP-System ______________________________________________________________ trade promotion and the funds plan match. Reserve fund budget for a trade promotion When the trade promotion reaches a certain pre-defined status, the system begins to reserve budget for the promotion from the funds. Maintain mapping between the funds type, expense type, and trade spends - Effects on Customizing You can maintain settings for funds integration in Customizing for Customer Relationship Management, by choosing Trade Promotion Management -> Trade Promotions -> Funds Integration. 1.21.21 Long-Term Trade Promotion Planning (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. SAP recommends you perform long-term trade promotion planning using a trade promotion as opposed to an account plan. You generate conditions for a trade promotion in the same manner as for account plans. Trade spends are filtered depending on the type of trade promotion you select in the General Data assignment block. In the Discounts assignment block only conditions that were created using the trade promotion are shown. There are many new features that are only available for trade promotions, such as mass copy, mass change, mass approval, causals, editable lists, enhancements to the calendar. SAP strongly recommends you plan long-term trade promotions using trade promotions. Effects on Customizing The standard delivery Customizing in the IMG activity Define Condition Generation has been enhanced to include a condition generation type for long-term trade promotion planning. ______________________________________________________________ SAP AG 234 SAP-System ______________________________________________________________ 1.21.22 Price Simulation Within a Trade Promotion (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can simulate prices for the products in a trade promotion before they are released for the field sales employees. This supports manufacturer's work scheduling and enables the account manager to determine the effect of promotional discounts on the final price of products quickly and in a step-by-step manner. Effects on Customizing You have made the necessary settings in SAP CRM Customizing by choosingDefine Condition Generation. First select the required condition generation type. Then navigate to folder Pricing Simulation and open the Customizing view for processing. 1.21.23 Trade Promotion Guidelines (new) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Promotion guidelines provide trade spend programming guidance to key account managers (KAM) based on rules and thresholds that are determined at a sales organization level within the manufacturer. Promotion guidelines can: 1. 2. 3. Issue non-compliance alert messages if a promotion guideline is violated during the trade promotion creation process Trigger a status based approval workflow. For example, change the trade promotion status to Awaiting Approval. Prevent further changes that could impact the status of the trade promotion Effects on Customizing You can define settings for trade promotion guidelines in Customizing for Customer Relationship ______________________________________________________________ SAP AG 235 SAP-System ______________________________________________________________ Management, by choosing Trade Promotion Management -> Trade Promotions -> Promotion Guidelines. See also Trade Promotion Versions Trade Promotion Critical Changes 1.21.24 Trade Promotion Versions (new) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. Versions in Trade Promotion Management (TPM) enable you to keep a historical record of changes to trade promotion attributes and numerical figures (key figures). Versions can be generated over a trade promotion's lifecycle by a status change. Effects on Customizing You can define settings for trade promotion versions in Customizing for Customer Relationship Management, by choosing Trade Promotion Management -> Basic Data -> Versions. See also Batch Processing Framework Trade Promotion Critical Changes Trade Promotion Guidelines 1.21.25 CRM-MKT-MPL Marketing Planner 1.21.25.1 Enrolling for Marketing Projects (New) Use This release note is only relevant if upgrading from SAP CRM 5.0 To control and manage the participation in marketing projects, you can now indicate that for a particular marketing project enrollment is required. The enrollment function is mainly designed for use in SAP CRM Web Channel. Web shop users can enroll themselves and accounts below their hierarchy level for marketing projects and can display their enrollment status. If you set the indicator Enrollment Required for a marketing project, a new assignment block containing ______________________________________________________________ SAP AG 236 SAP-System ______________________________________________________________ the enrollment list is displayed. This list shows all accounts who enrolled for the marketing project via the Web shop or were enrolled by an internal user. You can edit the list to enroll accounts or withdraw the enrollment of certain accounts. Only accounts belonging to the target group or planning account of the marketing project can enroll or be enrolled for the marketing project. You can set a start date and an end date for the enrollment period. After this period, enrollment via the Web shop is no longer possible. Internal users can still edit the enrollment list after the end date. Effects on Customizing To provide entry fields for the enrollment start and end date, you have to maintain an additional date range in Customizing (Define Additional Date Ranges). See also For more information about enrollment in SAP CRM Web Channel, seeCampaign Enrollment. 1.21.25.2 Enhancements to Campaigns and Trade Promotions Use This release note is only relevant if upgrading from SAP CRM 5.0 Campaigns and trade promotions have been enhanced by the following functions: Abnormal Demand Indicator For materials management you need to be able to anticipate peaks in demand. You have to analyze whether peaks are "normal" sales patterns and should be considered as a basis for future planning, or if the demand is considered "abnormal" and should not be considered for future planning. With a new indicator in the campaign and trade promotion you can define whether the sales orders referencing these campaigns or trade promotions are reported as abnormal demand. Complaint-Based Trade Promotions Trade promotions can be set up to be applied to complaints. Within these complaints your dealers can retroactively claim a discount with reference to a trade promotion. The field Usage Type shows that complaints can be created with reference to this trade promotion. Plausibility Check To provide a flexible framework for plausibility checks within campaigns and trade promotions, a new BAdI is provided. With this BAdI it is possible to develop plausibility checks based on any data in SAP CRM, in particular based on attributes of the marketing program. If the BAdI is implemented, the user is able to trigger the plausibility check by clicking the Check button in the menu bar of the marketing project. - - ______________________________________________________________ SAP AG 237 SAP-System ______________________________________________________________ Effects on Customizing Complaint-Based Trade Promotions To define a usage type for complaints, chooseDefine Usage Types. To define which transaction types can reference a trade promotion based on their usage type, you need to assign the usage type to the transaction type. You do this in the IMG activity Assign Marketing Usage Types to Transaction Types. If you want to default a usage type for complaint-based trade promotions, you need to assign this usage type to the relevant campaign type in Define Types/Objectives/Tactics Plausibility Check The new BAdI can be found underDefine Plausibility Checks. See also For more information about the abnormal demand indicator seeClassifying Sales Order Items as AbnormalDemand. For more information about complaint-based trade promotions see Complaint with reference to a trade promotion. 1.21.25.3 Mass Generation of Sales Orders via Campaigns or Trade Promotions (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now mass generate sales orders for a predefined group of accounts. This function is particularly useful if you have mandatory stocking requirements, for example if you want all your dealers to have a particular new product in stock. To generate sales orders via a campaign or trade promotion, you assign a target group, one or more products and a quantity for each product. You then select a communication medium that generates sales orders and, if required assign a sales order template. When you execute the campaign or trade promotion, a sales order is created for each member of the target group. The sales order contains a reference to the campaign. Additionally, you can to set up your communication medium so that when sales orders are generated e-mails are sent to the target group members informing them about the sales orders. ______________________________________________________________ SAP AG 238 SAP-System ______________________________________________________________ Effects on Customizing To generate sales orders you need to customize a communication medium,that triggers the generation of sales orders. This communication medium must have the new communication method Generate Sales Orders assigned.You do this by choosing Define Communication Medium. 1.21.25.4 CRM-MKT-MPL-CAL Marketing Calendar 1.21.25.4.1 Marketing Calendar (Enhanced in SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. As of CRM 2007 SP02, the marketing calendar is enhanced to display key performance indicators (KPI) of marketing objects. So you can view and compare say, trade promotions against factors that measure the progress or degree of fulfillment for important objectives. You can customize the calendar to include KPI-related columns in the calendar, while also defining which of the business key figures feature as KPIs for your organization. Effects on Customizing To view KPI columns or group marketing objects by KPI values, you have to complete the following Customizing steps: Define Views for Marketing Calendar Add KPI to Views in the Marketing Calendar Map Input Variable for SAP NetWeaver BI Query Define KPI for KPI Grouping in a View Define Ranges for KPI Grouping ______________________________________________________________ SAP AG 239 SAP-System ______________________________________________________________ 1.21.25.4.2 Marketing Calendar (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The marketing calendar can handle many marketing objects and plays a central role in Trade Promotion Management (TPM). It is now enhanced with the following features, to complement the whole process of trade planning which includes creation and maintenance of agreements, activities and events: - View agreement structures Provide a reference from the trade promotion to the agreement to view the structure of the agreement in the marketing calendar. This helps you see how activities, promotions and agreements are related. You can also use this reference when searching, copying and printing. Specify calendar attributes Use various calendar attributes to specify how you want to group or view or narrow down on the marketing projects that you work with. They will be especially useful when you have to set default values or set available attributes with values directly in the marketing calendar. Prefill attributes Use the new working context feature to prefill the calendar with suitable attributes. Compare projects and values Split the marketing calendar into a main and a second calendar, which will appear just below the main calendar. Enable the Split Calendar Option to do this. You can for example split the calendar and show all related campaigns in the second half of the screen, or show the same trade promotions from this time last year. View fiscal year variants View the fiscal year variant as well as calendars of potential customers in the form of time ribbons in the calendar. Display holidays Distinguish between working and non-working days in your calendar at a quick glance, and display holidays in a different color. This helps you keep public holidays and special holidays in mind, when you schedule events. Synchronize calendars Match your calendar with say, that of a planning customer. This is the Smart Day Mode at the bar level of the marketing calendar. You can have your calendar start on the start day of a planning customer. For this you have to maintain the default day for that customer, as part of the Account Defaults application. Change and save trade promotion details Make changes to trade promotion details and save them in the marketing calendar itself. Create trade promotions using templates Use trade promotion templates, which help you quickly create predefined trade promotions.You can filter the list of templates in a calendar so that only relevant templates appear on your screen. - - - - - - ______________________________________________________________ SAP AG 240 SAP-System ______________________________________________________________ - Export to Excel Export the marketing calendar to a Microsoft ® Excel Worksheet. This offline excel sheet keeps your account managers and sales managers informed so they can present and discuss their promotional and marketing plans with their customers. Effects on Data Transfer To export data from the marketing calendar to a worksheet, we recommend you use Microsoft ® Office Excel 2007 ®. Effects on Customizing To enable the split calendar option in the marketing calendar, complete the Define Split Calendar Options step To view holidays, complete the Maintain Calendar step by choosing Factory Calendar (defines working and non working days and is referring to a holiday calendar) - To view calendar attributes, complete steps: Define Field Catalog Attributes for Marketing Project Display Define Selection of Calendar Attributes Define Permitted Row Context Attributes 1.21.25.5 CRM-MKT-MPL-ST Basic Functions Key Figure Planning 1.21.25.5.1 CRM-MKT-MPL-ST-KFP 1.21.25.5.1.1 Free Goods in Trade Promotions (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0 Trade promotions can now be set up to provide free goods based on accumulated volumes. This function is based on the SAP CRM rebate application. The rules can be defined based on monetary values or quantities. The free goods are calculated periodically at defined settlement dates and at the end of the settlement period. A sales order free of charge with the free good as a line item will be generated for each dealer who reached the volumes within the last period. You have two options to define your free goods: ______________________________________________________________ SAP AG 241 SAP-System ______________________________________________________________ - Product-dependent free goods You can define one free good for each product in the trade promotion. Product-independent free goods You can define free products that are valid for all products in a trade promotion. This way you do not have to assign the free products for every single product. Effects on Customizing To work with product-independent free products you need a planning profile group with a planning profile of the type Product-Independent Free Goods. You define this planning profile group in Customizing for Customer Relationship Management , by choosing Marketing -> Marketing Planning and Campaign Management -> Key Figure Planning -> Define Planning Profile Groups. To calculate free goods based on accumulated volumes you need to define a condition type that has the indicator Cond Type FrGds set. You do this in Customizing for Customer Relationship Management , by choosing Rebate Processing -> Set Up Rebate Determination -> Create Condition Types. 1.21.25.6 CRM-MKT-MPL-DEF Customer Defaults 1.21.25.6.1 Trade Promotion Management - Product Hierachy Promotions (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can map trade promotions at product category and product group level and no longer have to assign promotions to individual products. There are a lot of trade promotion management (TPM) customers who generally run promotions for product categories or product groups as oppose to single products. An example would be that they typically run promotions involving a percentage discount on all 330 ml bottles of sodas. So rather than differentiating in a promotion between cola, lemonade and juice, the customer simply promotes an entire product category or product group. Up until SAP CRM 5.0, the marketing planner was based on individual products. You could enter the product category or group to search for a specific product, but the system always exploded the product category or group into its individual products and then stored the products of that product category or group as assignments to the marketing element. You can now plan and execute promotions, deals, and campaigns at product category and group level. This brings a significant improvement to the performance ______________________________________________________________ SAP AG 242 SAP-System ______________________________________________________________ and usability for consumer products customers. This functionality improves the overall performance of TPM by reducing the number of products assigned, reducing significantly the volumes/trade spends planning layout and the generation of campaign determination records. Overview of New and Enhanced TPM Features Assigning a Product/Product Category/Product Group to a Trade Promotion You can assign individual products in combination with product categories or groups to trade promotions. However, you cannot assign both product categories and product groups in the same promotion. If the individual product is a structure product, you cannot explode to the product items. If you want to explode the structure product, you can either implement a Business Add-In (BAdI) or assign the structure's product items individually. You can assign a product category or group without exploding to the individual products. You can enter any level of the product hierarchy as long as there is no overlap between the products categories that are assigned. After you assign products, product categories or product groups, the system checks the assigned product category or group against the territory, the partner/product range, and the listing for the SAP CRM product hierarchy. It also checks for any overlaps between individual products and product categories. If there are any overlaps, the system produces an error message and you cannot complete the assignment to the trade promotion. Finally the system checks for any overlapping product category assignments, which would also produce an error message. You can define in Customizing to what level you want to be able to explode the product category assignments. If there are no settings in Customizing, then the system explodes by default to the lowest level of the product hierarchy. In addition, the system retrieves a list price or price list for a product category or group. Generating Conditions at Product Category or Group Level You can generate condition records for variable and fixed trade spends as well as campaign determination at product category or group level. You can determine and assign a rebate product. The rebate product is selected arbitrarily from the list of products that belong to the product category or group. You can implement a BAdI if you want to use your own product determination. Volumes/Trade Spends You can plan volumes and trade spends without any specific product dimension. However, if you want to plan for product categories or groups, then you must specify a product category or group. The system must also be able to retrieve the list price and/or the price list for any new product assignments. Managing Trade Promotions Enhancements to managing trade promotions include the following: Print Functionality The print functionality of the marketing planner lists the product category or group that is assigned. Advanced Search The marketing planner advanced search enables you to search for trade promotions by product category or group. You can also save your own queries with the relevant product category or group in the selection criteria and use these in the marketing calendar. It is still possible to search for trade promotions by product. The system determines the product category or group and retrieves the relevant trade promotions. However, searching by product can be performance-intensive due to the distribution chain dependency. - - - - ______________________________________________________________ SAP AG 243 SAP-System ______________________________________________________________ - Change Document Change documents are enhanced to include the new product category or group assignment to promotions. Archiving Archiving is enhanced to include the new product category or group assignment. - CRM Mobile Sales Integration The product category or group assignment is added to the messaging BDoc type and then transferred to the marketing element. Trade Promotion Execution and Order Entry The campaign determination process in SAP ERP and SAP CRM has been modified to enable the product category or group to be referenced in the campaign determination condition records. - Effects on Existing Data There is a standard master role available for TPM. Effects on Customizing Note the following prerequisites, which must be fulfilled to enable you to plan and execute trade promotions at product category and group level: The price list must contain the product category or group to enable the system to retrieve a price list for a promotion that has been planned at product category or group level. All the products that belong to a product category or group must have the same base and sales unit as well as the same list price or price list. Only the sales-dependent product hierarchy is supported. In a SAP CRM and SAP Enterprise Resource Planning (SAP ERP) integration scenario, the only hierarchy SAP supports is R3PRODHIER. This is due to consistency and reporting reasons. Condition records do not have the unit as a key field. Therefore,there is only one row for each product category or group in the planning layout. SAP does not support several rows for several units for each product category or group. SAP does not support condition records of usage free goods (FG) for product categories or groups. In SAP ERP, listings are maintained at product level only. In SAP CRM, there is no listing check at product level as products are not assigned to the promotion. The listing check is executed at product category level. You can no longer report on individual products for promotions that are planned at product category or group level unless the planned data is disaggregated to products. New customizing to define the explosion level for mass assignment of product categories. If no level is maintained, then the system explodes to the lowest level of the product hierarchy. - - - ______________________________________________________________ SAP AG 244 SAP-System ______________________________________________________________ - New planning profile groups are available for trade promotion analyses in SAP NetWeaver Business Intelligence (SAP NetWeaver BI). You no longer define these analyses in the IMG for Marketing but in transaction CRMC_UI_BI. New planning layouts are available in BI-BPS to plan at product category and/or group without any product dimension. - 1.21.25.7 CRM-MKT-MPL-MDF Marketing Development Funds 1.21.25.7.1 MDF BI Extractors (Enhanced in SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. This document provides information about additional functions of the existing Market Development Fund (MDF) BI extractors for the following objects in the Marketing Planner: 0CRM_MKTMDF_CP_ATTR - provides channel partner enrollment information for an MDF program and MDF special program. This allows you to extract information about the relationship between channel partners and MDF programs and special programs. 0CRM_MKTPGM_ATTR - provides funds plan information for an MDF program. This existing MDF Program extractor is now enhanced to allow extraction of funds plan information assigned to an MDF program. - You can use BI extractors to transfer data from the source system to the SAP NetWeaver Business Intelligence (SAP NetWeaver BI) system so you have a basis on which to build your BI content. Extractors fill the extraction structure of a DataSource with data from business objects. You can extract data from CRM MDF applications, by performing a full extraction or by performing a delta extraction. These requests may be made with specific data filtering criteria. ______________________________________________________________ SAP AG 245 SAP-System ______________________________________________________________ 1.21.25.7.2 Market Development Funds (Changed) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Market development funds (MDF) are resources that you make available to channel partners for cooperative marketing. A variety of features enable you to more efficiently manage the MDF process, from planning, through enrollment of channel partners, through settlement of claims in SAP ERP. MDF uses functions from funds management and claims management. For more information about the functional possibilities of MDF, see the application help. MDF Programs You use an MDF program as the basis for managing cooperative marketing with a set of channel partners. An MDF program has one or more marketing goals, for example, higher awareness of a particular range of products and increased market share in a particular market sector. You define which channel partners are eligible to participate in the particular MDF program, what money is available for them, and which products are involved. You also define the rate at which the channel partners are reimbursed when they execute as agreed. MDF Special Programs An MDF special program is a part of an MDF program with more specific marketing goals, for example, promoting a subset of products or targeting a subset of accounts. An MDF special program allows you to assign a specific subset of channel partners, granting them specific terms and conditions. Mass Creation of Funds A fund generation function enables you to mass create funds for many channel partners at the same time without having to create each fund individually. This could be a one-time process or a repetitive process that needs to be executed often for new channel partners. MDF Initiatives An MDF initiative is a plan for marketing activities proposed by one of your channel partners. It specifies certain marketing activities that your partner undertakes to promote your products. It thus provides the basis for you, as a brand owner, to contribute funding to them. You make your contribution by reimbursing channel partners for their expenses in this collaborative project. MDF initiatives provide a means for you to manage your contributions ahead of claims in a number of ways: MDF initiatives come with an approval workflow that enables you to negotiate the project plan, including estimated costs and causals. You can also allow for partial approval and partial rejection by structuring the MDF initiative into MDF initiative elements, for instance, to deal with different phases of the project. ______________________________________________________________ SAP AG 246 SAP-System ______________________________________________________________ - MDF initiatives enable you to reserve certain amounts of money in funds for upcoming reimbursement claims by channel partners. If a claim is created from the same MDF initiative as the reservation, it must consume the reservation. An MDF initiative is created under a specific MDF program or MDF special program. This determines the funds available for reservations and claims based on the initiative as well as the terms and conditions for them. MDF Initiative Templates An MDF initiative template is assigned to an MDF program or MDF special program to control and speed up the creation of MDF initiatives under that MDF program or MDF special program. MDF initiative templates are more than a copy-and-modify mechanism. They enable you, as a brand owner, to constrain the choices available in MDF initiatives and to provide default values for specific fields. Thus they implement your policy of what kinds of marketing activities you want to encourage. MDF initiative templates have the same structure (fields and assignment blocks) as MDF initiatives, but you cannot create reservations or claims from them. Reservations and claims can only be created from an MDF initiative. Reservations A reservation ensures that the funds for an MDF initiative still contain enough money when an expected reimbursement claim arrives. The reservation prevents the required amount from being spent for purposes other than those stated in the MDF initiative. If the required amount is not available in a single fund, but your MDF initiative is in an MDF program or MDF special program that has multiple funds, you can break the amount down into smaller amounts in the reservation and reserve each of them in a different fund. Channel Partner Hierarchies A channel partner hierarchy is the hierarchical grouping of family members of a channel partner corporate family. Technically speaking, it is a type of account hierarchy. Your channel partners map their organizational structures in relationship to you, the brand owner, in channel partner hierarchies and use these to assign and manage funds, and to pass them on to lower levels. The modeling used here is freely definable. Both geographic modeling (for example, according to international subsidiaries) as well as segmentation into divisions or subsidiaries is possible. The type of modeling used is dependent on the way in which your channel partners wish to distribute and manage the market development funds granted to them by your organization within their corporate family. Authorizations and User Management Effects on Existing Data ______________________________________________________________ SAP AG 247 SAP-System ______________________________________________________________ Not compatible with previous releases of MDF. See also Market Development Funds: Extractors (New) Claims Management (New) Funds Management (New) 1.21.25.7.3 Authorization and User Management (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The brand owner offers MDF as a resource to partners funding marketing related activities. A channel partner is an external company and not part of the organizational model of the brand owner. But since the channel partner still uses the brand owner's CRM system to carry out market development-related activities, you as a brand owner can use special rights to control or determine the kind of information your channel partners will be allowed to see and create. Working at the brand owner is the channel manager. He or she manages partner relationships, collaborates with partners, and optimizes channel operations. A channel manager would need access to operational and analytical data to manage and optimize the indirect sales channel, from partner recruiting and planning to monitoring transactions within the channel. This includes modeling and maintaining the corporate family and the channel partner hierarchy. The channel manager works with the partner manager on the channel partner side. As part of authorization and user management, you can use the following features that have been enhanced and delivered as standard, for MDF: Roles (Enhanced) Business Roles In order to restrict access to documents and applications to authorized personnel, you can define and assign appropriate roles. The standard partner channel management roles have been enhanced for use with MDF applications. So part of the standard delivery is CHM-CM for the channel manager CHM-PM for the partner manager Business roles, that is the channel manager and partner manager roles, define applications, objects, workcenter pages that the user can see. PFCG Roles (Enhanced) ______________________________________________________________ SAP AG 248 SAP-System ______________________________________________________________ Each business role has at least one PFCG role, which specifies its authorization profile. You use this role to grant specific rights to a user, for example, a super-user function. The standard delivery for partner channel management provides the following PFCG roles For the brand owner: SAP_CRM_UIU_CHM_CHANNELMANAGER For the channel partner : SAP_CRM_UIU_CHM_PARTNERMANAGER SAP_CRM_CHM_CORPORATEPARTNER SAP_CRM_CHM_CORPORATEPARTNER is a new authorization profile for the corporate channel partner. For this there is no direct 1:1 relationship to a business role. Access Control Engine (Enhanced) This controls access to and use of business objects. Access control is based on rules and rights that can be modified individually to match internal organizational structures. The ACE allows you to restrict a partner user's access to MDF objects and business partners. ACE Rules and Rights Rules serve as the principle on which to base your rights. Rights in turn are composed of rules, groups of users they apply to and the kind of control you want to implement. It is practical to use ACE when you want to control, on object level, which users are to have read-, write-, and/or delete access. For a detailed list of the rules that are delivered specifically for MDF objects, refer to the customizing document ACE Rules for MDF. In addition to the standard ACE rights, you can use the SAP CRM delivered rights for MDF. For a detailed list of the ACE rights delivered for MDF, refer to the customizing document ACE Rights for MDF Notes and Attachments (Enhanced) You can use notes and add attachments to your MDF business documents. If your channel partner has access to a particular MDF object, such as a program or initiative, he or she will be able to access all notes and attachments under that object. Attachments Channel partners have display access to all attachments uploaded by the brand owner. Channel partners can change attachments, if they have change access to the associated MDF object. However, they cannot change attachments created by the brand owner. Notes Channel partners having display or change access to an MDF object, will also have display or change access to all the notes associated with that object - respectively. User Management User Assignment Block on Company Contact Overview Page (Enhanced) ______________________________________________________________ SAP AG 249 SAP-System ______________________________________________________________ You can now use the user assignment block on the company contact overview page in the partner manager business role to create, change and delete users for company contacts. E-Mail Notifications (Enhanced) You can now automatically send e-mails to business partners to inform them about a user that has been created or changed for them via a user assignment block on the partner contact or company contact overview page. The e-mail can contain information about the user ID, password, and status of the user. The e-mail can automatically be sent if a user gets created, the password of the user gets changed, or if the user gets locked, unlocked or deleted. When sending notifications, you can either use the standard template as it gets predelivered, or copy and adapt the standard template to meet your requirements. Effects on Customizing Maintain roles for the partner manager. For this, complete step Set Up Business Partner Roles for Web-Based User Management Maintain reference users. For this, complete step Enter Reference Users for Web-Based User Management. Enable ACE rights,. For this, complete stepActivate/Deactivate Work Packages and Rights. To automatically send e-mail notifications, complete step Define Settings for E-Mail Notifications. To define actions and action profiles, which are required for action processing in user management, with respect to the business partner complete the corresponding steps, Create Actions With Wizard, Define Action Profiles and Actions, and Define Start and Schedule Conditions. 1.21.25.7.4 Market Development Funds: Extractors Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Extractors for MDF Objects (New) This document provides information about BI extractors for the following Market Development Fund (MDF) objects in the Marketing Planner: MDF Programs, MDF Special Programs and MDF Initiatives and MDF Initiative Elements. You can use BI extractors to transfer data from the source system to the SAP NetWeaver Business Intelligence (SAP NetWeaver BI) system so you have a basis on which to build your BI content. The following are the attribute extractors: ______________________________________________________________ SAP AG 250 SAP-System ______________________________________________________________ - 0CRM_MKTPGM_ATTR: 0CRM_MKTSPG_ATTR: 0CRM_MKTINI_ATTR: 0CRM_MKTINT_ATTR: Attributes for MDF Program Attributes for MDF Special Program Attributes for MDF Initiative Attributes for MDF Initiative Elements The following are the text extractors: 0CRM_MKTPGM_TEXT: 0CRM_MKTSPG_TEXT: 0CRM_MKTINI_TEXT: 0CRM_MKTINT_TEXT: Extraction of Texts for MDF Program Extraction of Texts for MDF Special Program Extraction of Texts for MDF Initiative Extraction of Texts for MDF Initiative element BI Extractors for Channel Partner Hierarchy in MDF (New) The partner hierarchy in SAP CRM contains funds, purchase locations and additional business partner information. You can use the BI extractor function and extract data from partner hierarchy to the SAP NetWeaver Business Intelligence (SAP NetWeaver BI) system so you have a basis on which to build your BI content. We provide the following extractors for the channel partner hierachy: 0CRM_MDF_BPGH_HIER (not time dependant) 0CRM_MDF_BPGH_NAME_HIER (time dependant hierarchy name) 0CRM_MDF_BPGH_STRUCT_HIER (time dependant hierarchy structure) Effects on Existing Data These extractors fill the extraction structure of a DataSource with data from business objects. You can extract data from CRM MDF applications, by performing a full extraction or by performing a delta extraction. These requests may be made with specific data filtering criteria Effects on Customizing For the channel partner hierarchy, you have to specify which partner functions have to be extracted with the data source. To define the partner functions for MDF objects, complete step Define Extraction of Partner Functions. ______________________________________________________________ SAP AG 251 SAP-System ______________________________________________________________ 1.21.25.7.5 Determination of Reimbursement Rates in the MDF Process (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Cost sharing for marketing activities, brand owners, and channel partners is entered and distributed in the market development funds (MDF) process. This happens when the partner first defines the marketing activities that he or she wants to use to advertise for the product or service of the brand owner. The partner wants to bill the brand owner for the costs of these marketing actions in advance. In addition, the partner wants to be able to create transactions even if claims for marketing activities cannot be reimbursed in full by the brand owner. In the MDF process, the brand owner can confirm the claims that were submitted by the partner. For example, if the brand owner has an objection about marketing activities, he or she can react immediately by manually not confirming the full amounts that were requested. Alternatively, the brand owner could define in advance the expense types that are automatically reimbursed at a reduced rate. This is accomplished by using the automatic determination of reimbursement rates, which are used to calculate certain expense types. The result is normally a reduced reimbursement amount. You edit the reimbursement rates either in the MDF Program or in the MDF Special Program in assignment block Reimbursement Rate Conditions and create condition records for the price types that are available in this process. Usually, the partner creates an initiative that describes the marketing activity and forwards the estimated costs to the brand owner for confirmation. Then, the partner creates a reservation to ensure that sufficient funds from the brand owner are available to execute the initiative. This reservation means that the partner reserves a certain amount of money in his or her fund for this initiative. When an MDF claim or MDF reservation is created, reimbursement rates for certain expense types are determined automatically in assignment block Resolution. These reimbursement rates are used to calculate claim amounts such as actual costs. In the MDF reservation, the reimbursement rate is used to specify the amount that should be reserved for the marketing project in the fund. The partner specifies the expected costs, which are used by the reimbursement rate to determine the amount that should be reserved. When the brand owner confirms the reservation, the brand owner must also be able to change the amounts, which in turn influences amount determination. ______________________________________________________________ SAP AG 252 SAP-System ______________________________________________________________ 1.21.25.8 CRM-MKT-MPL-TPM Trade Promotion Management 1.21.25.8.1 Product Planning Basis for Trade Promotions and Deals (Enhanced for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can assign product groups or product categories to a trade promotion. You can also assign one or more products from these product groups or product categories to the trade promotion. You can now also: Exclude one or more products, so that the trade spend of the trade promotion is applied to all the products in the product groups or product categories except to the excluded products Define one or more products as exceptions, so that the trade spend of the trade promotion is the same for all the products in the product groups or product categories except for the exception products for which you can define different trade spends and volumes Effects on Data Transfer To transfer uplift volumes to SAP Advanced Planning and Optimization (SAP APO): If your product planning basis includes product categories, you must implement the Business Add-In (BAdI)SCM Integration. The example implementation of the BAdI takes into account exception products and excluded products for a promoted product category. If your product planning basis includes product groups, you must change and implement this BAdI - Effects on Customizing You can find the example implementation of the SCM Integration BAdI in Customizing for Customer Relationship Management under Marketing -> Marketing Planning and Campaign Management -> System Landscape -> Business Add-Ins -> BAdI: SCM Integration. 1.21.25.8.2 Key Figure Planning Enhancements (New for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can view and enter key figure totals for a trade promotion, such as total volume and trade spend data, on the Trade Promotion Overview page, in the new Totals assignment block, as well as on the Trade Promotion Editable List Overview page. The distribution of the data from the aggregated level to the lower levels is done either on navigating to the Planning grid or on saving the trade promotion. You define which key figures you want to display on the Trade Promotion Overview page and the Trade Promotion Editable List Overview page in Customizing activity Map BI Key Figures to List Fields. You ______________________________________________________________ SAP AG 253 SAP-System ______________________________________________________________ maintain the descriptions for the key figures in the Customizing activity Maintain Design Layers. Using the UI Configuration Tool, you define the field labels and the position of these fields on the Trade Promotion Overview page. Effects on Customizing You define which key figures you want to display in Customizing for Customer Relationship Management under Trade Promotion Management -> Key Figure Planning -> Settings for Display of BI Key Figures -> Map BI Key Figures to List Fields. You maintain the descriptions for the key figures in Customizing for Customer Relationship Management under Trade Promotion Management -> Key Figure Planning -> Settings for Display of BI Key Figures -> Maintain Design Layers. 1.21.25.8.3 Effective Dates in Trade Promotions and Deals (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. You can: Add a product/product category/product group/ product segment to a trade promotion and specify effective start and end dates that could be different from the trade promotion buying start and end dates Logically delete a product/product category/product group/product segment from a trade promotion by specifying an end date that is different from the trade promotion end date Modify the discount rate (any trade spend) as of any date for all or for a subset of products that are associated to the trade promotion - 1.21.25.8.4 TPM BI Extractors Use ______________________________________________________________ SAP AG 254 SAP-System ______________________________________________________________ This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use BI extractors to transfer data from the source system to the SAP NetWeaver Business Intelligence (SAP NetWeaver BI) system so you have a basis on which to build your BI content. You can extract data from CRM TPM applications, by performing a full extraction or by performing a delta extraction. These requests may be made with specific data filtering criteria. This document provides information about BI extractors for the following Trade Promotion Management objects: Indirect Relationships Causals Extractors for Indirect Relationships The purpose of the BI extractor for Indirect Relationships is to get data from the indirect relationship applications to use it for aggregation and further reporting. Indirect relationship data contains the details about the indirect consumption from different wholesalers, for a particular product dimension and period. Extractor 0CRM_MKTINDREL_ATTR Type of DataSource: ATTR Application Component: 0CRM_MKT-IO Extract Structure: SCRMMKT_INDR_BW Extractors for Causals Causals capture information about how retailers advertise trade promotions for consumers. They have attributes like feature ad, display location, display type, media, retail price and so on. The following are the attribute extractors: (Type of DataSource: ATTR; Application Component: 0CRM_MKT-IO) 0CRM_MKTPL_CAU_ATTR, to extract the main causal table Extract Structure: SCRMMKT_CAU_BW 0CRM_MKTPL_CAU_TYPE_ATTR, to extract causal types from TPM types Extract Structure: ROXA9G0113 0CRM_MKTPL_CAU_CFLDL_ATTR, to extract mapping links of related fields Extract Structure: CRMC_MKTPL_CFLDL The following are the text extractors: (Type of DataSource: ATTR; Application Component: 0CRM_MKT-IO) 0CRM_MKTPL_CAU_CFLD_TEXT, to extract fields related to causal types Extract Structure: RSTEXTTRSF ______________________________________________________________ SAP AG 255 SAP-System ______________________________________________________________ 0CRM_MKTPL_CAU_DISLO_TEXT, to extract the causal field display location Extract structure: CRMC_MKTPL_DSLOT 0CRM_MKTPL_CAU_DISTY_TEXT, to extract the causal field display type Extract Structure: CRMC_MKTPL_DSTYT 0CRM_MKTPL_CAU_FEAD_TEXT, to extract the causal field feature ad Extract Structure: CRMC_MKTPL_FEADT 0CRM_MKTPL_CAU_MEDIA_TEXT, to extract causal field media Extract Structure: CRMC_MKTPL_MEDIT 0CRM_MKTPL_CAU_SLOSK_TEXT, to extract causal field slotted Skus Extraction structure: CRMC_MKTPL_SLSKT 0CRM_MKTPL_CAU_SPCLO_TEXT, to extract the causal field space location table Extraction Structure: CRMC_MKTPL_SPCLT 1.21.25.8.5 Indirect Relationships (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2 Indirect relationships help you manage your indirect lines of business, by allowing you to ______________________________________________________________ SAP AG 256 SAP-System ______________________________________________________________ - Link an indirect account to the respective wholesaler(s), as well as specify a percentage split in case of multiple wholesalers and track indirect accounts Indirect accounts might buy different product categories from different wholesalers. Here, the product dimensions of relationships help you work with different product categories of the same indirect account. For example, a customer might buy chilled products from a wholesaler, while the other product categories are sourced directly from the manufacturer. Develop a total trade spending and sales volume plan for a wholesaler Establishing indirect relationships allows you to trace incremental sales volumes originating from promotions with indirect accounts, back to the corresponding wholesaler. This helps you delineate the effectiveness of your trade spending. Manage different funding levels for indirect promotions Indirect promotions draw their funding either from a specific fund for the indirect customer or from the fund of the corresponding wholesaler. Validate claims of indirect promotions Claims might be raised either by the indirect account or the corresponding wholesaler (claims-on-behalf). Indirect relationships help you associate claims raised by wholesaler with the appropriate indirect promotion. - - - Effects on Customizing Indirect relationships are formed with respect to product dimensions, which are specified at sales area levels. To do this, complete step Define Business Line Levels. 1.21.25.8.6 Listings in Product Proposals (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. You can now generate a product proposal that is based on the list of products that you can sell to an account as specified in listings. You can then select a subset of products for a specific account and generate a sales order in SAP ECC for those items. There is a new selection option in the Product Proposal field called Listings. In addition, master data and listings administrators can search for listings using the value of the Description field of the listings. ______________________________________________________________ SAP AG 257 SAP-System ______________________________________________________________ Effects on Customizing You require: At least one listing that is valid for the account and product validity dates when the sales order is being made Appropriate cross-selling and up-selling or down-selling rules (optional) 1.21.25.8.7 Cross-Order Caps for Discounts in TPM (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can define a currency- or quantity unit-based upper limit, or a cap, that cannot be exceeded for the discounts in a trade promotion. This ensures that the price reductions defined in this trade promotion are limited to a certain amount or quantity and cannot be used past this limit. All affected invoices are included and cumulated in the upper limit. Note: You can only use the function if you have created condition types in SAP ERP and if you enter the sales documents in SAP ERP. Effects on Customizing You have made the necessary settings in Customizing: You have set the CondUpdate (Condition Update) indicator for the condition type in SAP ERP. This marks the condition type as cap-relevant. You can find more information in Customizing for SAP ERP under Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define Condition Types. The condition record must be maintained in SAP CRM. Therefore you have to shift the maintenance right for this condition type to SAP CRM. This shift is done in Customizing for SAP ERP under Integration with Other mySAP.com Components -> Customer Relationship Management -> Basic Funcitons -> Data Exchange Conditions. This customizing and the condition type must be downloaded to SAP CRM using transaction R3AS in SAP CRM. You have defined the cap type. You can find more information in Customizing for SAP CRM by choosingDefine Condition Generation. Select the Pricing Condition Types step, and then in the Cross-Order Cap Type column, choose the required cap type. There are two types: currency-based or quantity unit-based. - - ______________________________________________________________ SAP AG 258 SAP-System ______________________________________________________________ - You can assign appropriate currency units to your sales organizations. This customizing activity is optional. You can find more information in Customizing for SAP CRM by choosing Define Currency Units for Cross-Order Caps. 1.21.25.8.8 Significant Uplifts and Transfer to APO (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. This feature bridges the gap between demand planners and sales persons regarding the uplift that is generated for a specific trade event. Demand planners typically incorporate regular trade events into their demand plan and these events are planned by sales teams as creating uplifts. The feature supports enforcing a business process across the enterprise that would enable sales persons to identify only trade events that cause a significant uplift. The assumption is that the volume impact of other trade events has already been incorporated into the demand planner's plan. 1.21.26 CRM-MKT-SEG Segmentation 1.21.26.1 Product Segments (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The existing segmentation functionality has been enhanced to enable the segmentation of products. ______________________________________________________________ SAP AG 259 SAP-System ______________________________________________________________ Analogous to the creation of target groups, you can combine product-related selection criteria in a profile and can then build a product segment based on this profile. Product segments can be used in trade promotions. They considerably reduce the maintenance effort for conditions because you can assign a whole product segment to a condition record. This means you do not have to link each individual product with the condition. In campaigns, product segments can be used to streamline your planning: By assigning a product segment to a campaign, you can do the planning for all products in this segment. Before creating a segment, you now have to indicate whether you will be segmenting products or business partners. You can also create product segments manually, to which you can add products individually. Product segments can be intersected with, added to, and removed from other products segments. On the edit page, you can see the product segment details and can display a preview of the target group member list, if required. Effects on Customizing To work with the Graphical Modeler and to create product segments, you must create a data source that supports the segmentation of product data (Maintain Data Sources and Attribute Lists). This data source has to be based on an InfoSet. SAP delivers several InfoSets as examples. 1.22 CRM-ANA CRM Analytics 1.22.1 Integration of PPM into SAP CRM (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Pipeline performance management (PPM) is a new and highly interactive analytic application designed to help sales managers and sales representatives plan quotas and manage pipeline activity to achieve targets. Presenting opportunity data in context with pipeline analytics allows easy identification of gaps and critical opportunities, resolving issues before it is too late. Sales managers can prioritize, reassign or modify opportunities to drive immediate action and help sales representatives maintain focus on the right deals. Simulation capabilities provide the ability to run what-if scenarios and visualize the outcome without affecting the underlying data. Sales managers and sales representatives can monitor and analyze opportunities in the following pages: Target to Date Closing Date Sales Pipeline ______________________________________________________________ SAP AG 260 SAP-System ______________________________________________________________ - Sales Pipeline Change Sales managers with the appropriate authorizations can manage quotas and opportunity churn rates in the Options page. 1.22.2 CRM-ANA-OR Operative Reporting 1.22.2.1 CRM Interactive Reports (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can create, edit and view reports in SAP CRM. These CRM-based reports retrieve data in real-time and are called "CRM interactive reports". You create these reports in the CRM WebClient using a guided wizard. You can then publish these reports to a selection of users. You can display reports in tables and charts. The following chart types are available: Column Line Pie Bar Stacked Column Using the reports, you can analyze data in ample ways, including drilldown to individual documents. The report data is retrieved in real-time. You can export report data to Microsoft Excel and print reports. To use CRM interactive reports, you do not need a separate BI system. You do need an additional SAP NetWeaver Business Intelligence client to be installed on the CRM server. ______________________________________________________________ SAP AG 261 SAP-System ______________________________________________________________ 1.23 CRM-IC Interaction Center WebClient 1.23.1 Interaction Center WebClient in CRM WebClient UI Framework (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The Interaction Center (IC) WebClient uses the new, unified CRM WebClient user interface (UI) framework. Effects on Customizing For the IC WebClient, choose Customizing for Customer Relationship Management -> Interaction Center WebClient. 1.23.2 Intent-Driven Interaction Guidance (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Intent-driven interaction guidance is available to intelligently guide agents through interactions in a highly automated manner based on rules and events you define. Intent-driven interaction ensures interactions are processed according to corporate standards. Intent-driven interaction consists of: Rules You use the rule modeler to define business rules that determine how agents are intelligently guided. Rules react to events and other relevant information. Alerts You can provide alerts to agents with customized text and optional navigational hyperlinks. There are new actions in the repository for the IC Rules context for raising, triggering, and terminating alerts. For more information, see Alert Editor (New). Events Events can be used to raise alerts and for logging purposes. You can define events based upon user interface events, such as clicking a button or confirming a business partner. Automatic navigation and navigating to other CRM screens The system can automatically navigate agents to different page areas in the IC WebClient, and an - - - ______________________________________________________________ SAP AG 262 SAP-System ______________________________________________________________ agent can now navigate to any CRM screen, not just to screens within the IC WebClient. There are new actions in the repository for the IC Rules context for determining this automatic navigation. Automatic data population The system can automatically pre-populate data based upon configuration. There are new actions in the repository for the IC Rules context for automatically populating fields. Event logging and reporting Aggregated event reporting, analysis, and process optimization is available. You can log how many times events occurred within interactions, and use Business Intelligence (BI) to analyze the data. For example, you can analyze how many events occurred for specific agents, groups, profiles, and so on. - Effects on Customizing A new folder, Intent-Driven Interaction, is created with the following new Customizing activities: Define Business Data Context (BDC) Attributes Define Events in Repository Define Business Data Context (BDC) Objects for Event Logging Define Event Logging Profiles Define Intent-Driven Interaction Profiles The following existing Customizing activities are reused and included in the new folder: Define Services Define Service Manager Profiles Define Repository Define Wrap-Up Types 1.23.3 Client Switch (New for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can now use client switch in the interaction center (IC) to optimize resources in business process outsourcing and shared service center scenarios. The client switch function uses the SAP client concept to segregate data of different outsourcing accounts of the business process outsourcing provider or the shared service center in the CRM system. For example, separate SAP CRM system clients can be set up to store data for different business process outsourcing accounts. These clients are called work clients. ______________________________________________________________ SAP AG 263 SAP-System ______________________________________________________________ IC agents can access this environment by logging on to a single IC in a main client. From this main client, IC agents can be guided automatically to the appropriate work client. When an agent receives an incoming call, for example, the system proposes a work client based on data from the incoming call, such as the number dialed. 1.23.4 Selection Dialog Boxes (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. You can now enable dialog boxes in the Interaction Center (IC) for organizational units, business partners, service contracts, or transaction types. The dialog box gives the user selection options when the system identifies more than one organizational unit, business partner, service contract, or transaction type. You can set up the dialog boxes to appear automatically, or you can choose to make them accessible when the user clicks on an informational message. Effects on Customizing You can now make settings for automatic dialog boxes in the previously existing IMG activity in Customizing for Customer Relationship Management, by choosing Interaction Center WebClient -> Business Transaction -> Define Business Transaction Profiles. 1.23.5 Listing Based Product Proposals (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. ______________________________________________________________ SAP AG 264 SAP-System ______________________________________________________________ In the Interaction Center (IC), you can now generate product proposals for the confirmed account that contain only products and product categories that are listed for the account. You can then generate an Enterprise Resource Planning (ERP) sales order for any items the customer selects from the listed product proposals. 1.23.6 Multi Chat (New for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can now use multi chat in the interaction center (IC) to optimize resources. IC agents can now chat with more than one business partner at a time. They can therefore maximize efficiency by replying to a chat with one business partner while waiting for a response in another open chat session. 1.23.7 Cancel Button in Business Transactions (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The Cancel button is available in the Interaction Center (IC) WebClient, in all business transactions except for the interaction record. When you chosse this button, all entries that were made since the last saved version are reset. ______________________________________________________________ SAP AG 265 SAP-System ______________________________________________________________ 1.23.8 CRM-IC-MDB Manager Dashboard 1.23.8.1 Monitoring of Statistics from Multiple Telephony Systems (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The Interaction Center (IC) Manager Dashboard can support multiple computer telephony integration (CTI) servers. This means that: All CTI related information (such as channels, queues, and key figures for channels and queues) can come from different CTI servers To distinguish the information, the IC manager dashboard automatically prefixes the CTI server name to the channel, queue, and key figures. For example, CTI1 Hotline and CTI2 Hotline. You can monitor statistics generated via multiple telephony systems within a location and/or across several locations - You can group together queues into one or more queue groups, containing queues from the same or different CTI servers. For each queue group, you can select the following key figures when personalizing the IC manager dashboard: Sum Total volume of all selected queues in the queue group. For example, if CTI1 has four customers waiting in the queue, and CTI2 has six customers waiting in the queue, the sum is ten. Average Average volume of all selected queues in the queue group. For example, if CTI1 has four customers waiting in the queue, and CTI2 has six customers waiting in the queue, the average is five. - When you access the IC manager dashboard, the agent group is displayed that you were monitoring when you last used the IC manager dashboard. Because you are likely to be focused on a specific queue, you can filter the display by individual queues or queue groups, or show all queues for the agent group. Effects on Customizing You can restrict the agent groups and queues that each manager can monitor in the IC manager dashboard. As a result, when the manager accesses the IC manager dashboard, only these agent groups and queues are displayed. You do this as follows, depending on whether you are using the IC WebClient ______________________________________________________________ SAP AG 266 SAP-System ______________________________________________________________ or the IC WebClient 2005: IC WebClient Assign the function profile CONTACTCENTER to the relevant business role in Customizing for Customer Relationship Management -> Business Roles -> Define Business Role. IC WebClient 2005 1. 2. Assign the function profile CONTACTCENTER to the relevant IC WebClient profile in Customizing for the Interaction Center WebClient -> Define IC WebClient Profiles. Assign the IC WebClient profile to the IC manager organizational unit at position level. In the SAP Menu, choose Interaction Center -> Supporting Processes -> IC Structure -> Change Organization and Staffing (or Create Organization and Staffing). 1.23.9 CRM-IC-SEA Account Identification 1.23.9.1 Account Identification (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. The Identify Account page in the Interaction Center (IC) WebClient contains the following enhancements: Address Validation A search help is available for the following fields: Street City Postal code This enables agents to search for and validate addresses against a database of valid addresses. You can import data in Customizing for SAP Web Application Server -> Application Server -> Basis Services -> Address Management -> Regional Structure/City File -> Import Reference Data. For example, in some countries, you can buy a CD from your postal service containing all addresses. Duplicate Checking You can configure the system so that, when an agent creates an account or contact person and chooses Save, the system checks for duplicates and displays them. 1. In Customizing for Customer Relationship Management, choose Interaction Center WebClient -> Master Data -> Accounts -> Define Account Identification Profiles and select the Check Account for Duplicates indicator or Check Contact Person for Duplicates indicator as required. Implement the following Business Add-Ins: ADDRESS_SEARCH 2. ______________________________________________________________ SAP AG 267 SAP-System ______________________________________________________________ - ADDRESS_UPDATE Do Not Contact Indicator A Do Not Contact indicator is available via the More Fields link. Agents can set this indicator if a customer does not wish to be contacted at a given telephone number, fax number, or e-mail address. 1.23.9.2 Index Table for Simple Business Partner Searches (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can define a simple index table containing a set of fields, which can be used instead of the standard business partner search. Searching for business partners against a simple index table provides a very fast search, and is useful if your interaction center agents do not need to carry out complex searches. This new index table search differs from the TREX high-speed business partner search in cases where the agent always searches on the same one or two fields. The performance is better than using the TREX search, however for more complex searches using wildcards and multiple, varying criteria the TREX high-speed business partner search is faster. Effects on Customizing You can define an index table in Customizing for Customer Relationship Management -> Interaction Center WebClient -> Customer-Specific System Modifications -> Define Search Index for Business Partner Search. 1.23.9.3 Mixed Business-to-Business and Business-to-Consumer Scenario (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can search for consumers and related business partners (for example, contact person of organization, ______________________________________________________________ SAP AG 268 SAP-System ______________________________________________________________ legal representative, tax adviser). If the Interaction Center (IC) WebClient determines that the business partner is a related business partner, it displays the organization and the related business partner. By default, the organization is flagged as the main business partner. If you flag the related business partner as the main business partner, Customizing determines whether: The IC WebClient uses the related business partner and, as additional information, the organization (for example, in the sales order), or The IC WebClient uses only the related business partner, and hides the organization because it is considered not relevant. If the account does not yet exist in the system, you can create it as: Individual person (that is, a consumer), or Individual person, organization, or group With this option, you can create one or more related business partners for each individual person, organization, or group. Effects on Customizing In Customizing for the Interaction Center WebClient -> Master Data -> Accounts -> Define Account Identification Profiles: See also Release note Related Business Partners Set the Scenario field to Mixed B2B and B2C Set or cancel the Hide Corporate Account indicator as required By default, this indicator is not set. 1.23.9.4 Related Business Partners (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can: Search for and identify persons in their business partner relationship (for example, contact person of organization, legal representative, tax adviser) Display all or specific business partner relationships in a hierarchy after identifying the customer Create new business partners in their business partner relationship ______________________________________________________________ SAP AG 269 SAP-System ______________________________________________________________ Effects on Customizing In Customizing for the Interaction Center WebClient -> Master Data -> Accounts -> Define Account Identification Profiles: See also Release note Mixed Business-to-Business and Business-to-Consumer Scenario Set the Scenario field to Business-to-Business (B2B) or Mixed B2B and B2C Define which business partner relationships you want agents to be able to search for and use when creating business partners 1.23.9.5 CRM WebClient UI for IS-M Processes in Interaction Center Use This release note is only relevant if upgrading from SAP CRM 5.0. As of release 7.0, certain IS-M-specific processes now offer a UI based on the CRM WebClient in the CRM Interaction Center. The following IS-M-specific processes have been affected, with the changes listed below: Business Partner Maintenance You maintain the media-specific roles Sales Customer, Retailer and Media Customer in the Roles table at the bottom of the edit page of the Sales Area Data assignment block. This table is visible only if media-specific roles are defined in Customizing. (These roles are not to be maintained in the Roles assignment block on the overview page, as they depend on the sales area). Note: You can maintain roles in this table only after you have specified attributes (for example, Billing -> Customer Pricing Procedure) for a sales area. A sales area assignment without attributes cannot be created. Account Identification In the Account Identification screen, media -specific enhancements have been made to search for business partners. On the right hand side of the search screen, media -specific selection criteria have been created. The following search criteria have been added for advertising management: Advertising Order Advertising Billing Document Advertising Box Number ______________________________________________________________ SAP AG 270 SAP-System ______________________________________________________________ - Publication (this is visible only if BAdI CRM_ICWC_ISM_FILTER_BPSEARCH is implemented) The following search criteria have been added for sales and distribution: Subscription Order Subscription Billing Document Subscription Reference Document Publication The search result is displayed as usual in the lower part of the search screen. Order Lists from the IS-M Back End You use the Transaction Launcher, a new tool in this UI, to access ERP-based advertising or subscription data. Methods of BOR object types as well as BSP applications can be called this way. You can use the following methods of the BOR object type BUSISMCIC to access Media data in ERP: ShowMSDOrderList: interactive list of subscription orders ShowMAMOrderList: interactive list of advertising orders ShowBPOverview: access to BP-related data as used in the ERP Interaction Center in the application and/or navigation area. You can perform address changes with method AddressChangeWithDialog of object type BUSISM007. Order Creation with Reference to an IS-M Campaign The BSP applications ISMCAMPAIGNPICK and ISMSD_SOCREATE for creating advertising or subscription orders have been enhanced so that they can be used in the Interaction Center WebClient. Maintenance of IS-M-Specific Data for CRM Campaigns The BSP application ISMCAMPAIGNMGNT for maintaining the media-specific data for CRM marketing campaigns has been enhanced so that it can be used in the Interaction Center WebClient. Effects on Customizing You can use the activity Define BP Roles to define media-specific roles with the role categories ISM000 (Sales Customer), ISM001 (Retailer) or ISM020 (Media Customer). If an additional filtering of accounts (for example, by publication) is required, you can implement BAdI CRM_ICWC_ISM_FILTER_BPSEARCH (in enhancement spot CRM_ICWC_ISM_FILTER_BPSEARCH). ______________________________________________________________ SAP AG 271 SAP-System ______________________________________________________________ 1.23.9.6 Registered Products (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can search for installed bases and objects for a certain business partner in the Interaction Center (IC) WebClient on the Account Identifcation page. Effects on Customizing For more information, see Customizing for Customer Relationship Management and choose Interaction Center WebClient --> Master Data --> Define Object Profiles. 1.23.9.7 Account Identification (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. The Account Identification page of the Interaction Center WebClient has been enhanced. You can now replace the upper right page area with your own views that enable you to search for business partner-related business objects. You can define your own object components so that the agent can search for: Objects based on the confirmed business partner Business partners based on the confirmed object Effects on Customizing You can define object components to embed in the upper right page area of the Account Identification page in Customizing by choosing Customer Relationship Management -> Interaction Center WebClient -> Customer-Specific System Modifications -> Define Object Components. You can then assign these components to the relevant Account Identification Profile in Customizing by choosing Customer Relationship Management -> Interaction Center WebClient -> Master Data ______________________________________________________________ SAP AG 272 SAP-System ______________________________________________________________ -> Define Account Identification Profile. 1.23.10 CRM-IC-PRO Products 1.23.10.1 Product Search in the Interaction Center (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can search for products in the Interaction Center using one of two methods: Search based on product master data Search based on product catalog data Product Master Data Search When an agent starts a search for a product in the Interaction Center, the system runs the search based on all products maintained in the product master data. All products maintained in your system will be found using this search method. This method has its advantages in that you do not have to maintain product catalogs and you do not need to worry that product catalogs are incorrectly maintained. The search will find any product maintained in your system. Product Catalog Search When an agent starts a search for a product in the Interaction Center, the system runs the search based on the products maintained in a particular product catalog. This method has several advantages: The system only runs the search within a particular group of products enhancing the runtime of the search. You can limit the search to the catalogs that are relevant for the Interaction Center, and the search can be narrowed further using list of characteristic attributes and catalog variants and areas. An agent can browse the product hierarchy to locate a product. For example, if the customer is on the web shop looking at a particular product and the customer has a question about the product, or is having difficulty placing an order, the agent can locate the product that the customer is looking at and provide the customer with information or help Effects on System Administration Product Master Data Search You have maintained products in your product master. ______________________________________________________________ SAP AG 273 SAP-System ______________________________________________________________ Product Catalog Search You have created a product catalog and catalog variant. You have replicated your product catalog variants. Effects on Customizing To determine the search method used in the Interaction Center you need to carry out Customizing activities. Product Master Data Search In Customizing for Customer Relationship Management choose Interaction Center WebClient -> Master Data -> Products -> Activate Product Search In Product Master Data Product Catalog Search In Customizing for Customer Relationship Management choose Interaction Center WebClient -> Master Data -> Products -> Define Catalog Profiles for Product Search 1.23.10.2 Product Catalog Search (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The product catalog search is available in the Interaction Center (IC) WebClient. The search in product catalogs allows your agents to search specifically for certain products during sales negotiations, for example, and then call up product information directly. In addition to being in the product search, the product catalog search is also available in the master data. Effects on Customizing For more information about the necessary settings for the product search in the IC WebClient, in Customizing for Customer Relationship Management, choose Interaction Center WebClient --> Master Data --> Products. ______________________________________________________________ SAP AG 274 SAP-System ______________________________________________________________ 1.23.11 CRM-IC-FCA Financial Contract Accounting 1.23.11.1 Financial Customer Care and Dispute Management (Enhanced) Use This release note is only relevant if you are upgrading your system from SAP CRM 5.0. The business scenario includes the following new or enhanced processes: New with SAP CRM 5.2 or SAP CRM 2007: Note: All the functions listed here require SAP FI-CA based on SAP ERP 6.0 Enhancement Package 2 at the lowest as the back-end system. However, SAP ERP 6.0 ist still supported as the back-end system. For further information on release dependency, see SAP notes 1075410 and 746475. Payments in the Interaction Center for Financial Customer Care Maintain payment methods If you use SAP ERP 6.0 Enhancement Package 2, the payment methods are no longer defined in the FI-CA profile for the user role but in SAP FI-CA. You can define the payment methods for each country for the following payment types: Payment Installment plan Promise to pay Payment specification or payment request Payment requests Grouping of items for which payment orders are to be made to form one payment request in the ERP system Payment specification Grouping of items in a payment specification in the ERP system - Installment Plan You can define payment data for installment items. Payment Search As of SAP ERP 6.0 Enhancement Package 2, you can restrict a payment search to a certain number of payments. You can also limit the maximum number of payments on which the search is to be run. This allows you to avoid long waits when executing the search. You can define standard values for this function in Customizing for the FI-CA profile. The agent can adjust these parameters on the interface for the payment search. Account Balance Display new flexible FI-CA balances Display configurable additional data ______________________________________________________________ SAP AG 275 SAP-System ______________________________________________________________ - Enhanced support for contract data in the account balance Display processing locks for contracts Dunning history Display collection strategy and collection step Payment Data You can define bank details for a specific period in a business partner's payment data. Miscellaneous Display enhanced user data You can display details on a user for the user IDs (for example Created By) in the user interface in the Interaction Center for Financial Customer Care even if the user is not known in the CRM system. You can define which data is to be displayed in FI-CA event 2836. Fact sheets Display FI-CA data in an account or business agreement overview Alerts Convert FCC alerts to the new CRM Alert Framework User interface Convert FCC interfaces to the new CRM WebClient user interface For further information on converting the user interface, see the release note Uniform User Interface in CRM (New). - Financial Customer Care As Frontend for FI-CA Collections Management Display and edit worklists and work items Display, create, and change promises to pay Display collection fact sheet, display collection-relevant data Display a customer's collection history and details of the objects it contains For further information on Collections Management in SAP FI-CA, see the SAP ERP 6.0 Enhancement Package 2 release note Collections Management in the ERP system. Financial Customer Care Integration with Adjustment Request and Dispute Management You can integrate Dispute Management with Financial Customer Care. For further information on Dispute Management in SAP CRM 2007, see the release note New Functions in the Provider Contract and Dispute Management. Credit Management Integration You can integrate the Financial Customer Care Interaction Center with various credit management systems. The following functions are available in each case: SAP Credit Management (FIN-FSCM-CR) in SAP ERP Central Component (SAP ECC); the two systems are connected using SAP NetWeaver - Exchange Infrastructure (XI) Credit Management (FI-AR-CR, SD-BF-CM) in SAP ECC External credit management system connected using XI ______________________________________________________________ SAP AG 276 SAP-System ______________________________________________________________ - External credit management system not connected using XI If you use SAP Credit Management (FIN-FSCM-CR) or another external credit management system that is connected using XI, the following functions are available: Display and use a business partner's credit risk rating Automatic credit check and commitment notification Process transactions with credit locks If you use Credit Management (FI-AR-CR, SD-BF-CM) in SAP ECC, the following checks are available: Business partner valuation and credit rating check in SAP CRM Automatic credit check and commitment notification Process transactions with credit locks If you use an external credit management system that is not connected to SAP CRM using XI, the automatic credit limit check and commitment notification functions are available. For further information on Credit Management integration, see the SAP Library documentation on SAP CRM 2007 on the SAP Help Portal at http://help.sap.com -> Documentation -> SAP Business Suite -> SAP Customer Relationship Mgmt. -> SAP CRM 2007 -> Components and Functions -> Basic Functions -> Credit Management. Effects on Customizing For further information on Customizing and on how to configure this business scenario, see SAP Solution Manager. See also For further information on the functions in the individual business processes in the business scenario Financial Customer Care & Dispute Management, see the SAP Library documentation on SAP CRM 2007 on the SAP Help-Portal at http://help.sap.com -> Documentation -> SAP Business Suite -> SAP Customer Relationship Mgmt. -> SAP CRM 2007 -> Components and Functions -> SAP CRM for Industries -> Telecommunications Industry -> Functions in the Interaction Center for Financial Customer Care. 1.23.11.2 Financial Customer Care for Insurance (Enhanced) Use This release note is only relevant if you are upgrading from CRM 5.0. ______________________________________________________________ SAP AG 277 SAP-System ______________________________________________________________ Refer also to the release note for Financial Customer Care, which also applies to this industry variant. As of SAP CRM 2007, the business scenario contains the following process: Account Identification If you are implementing SAP ERP 6.0 with Enhancement Package 3 in the back-end system, you can call the transaction for editing the insurance object after the insurance object has been confirmed. Effects on Customizing For more information about Customizing and configuration of this business scenario, refer to SAP Solution Manager. 1.23.12 CRM-IC-ALT 1.23.12.1 Alert Editor (New) Use Alert This release note is only relevant if upgrading from SAP CRM 5.0. You can create and maintain alerts in a new alert editor. Alerts are considered part of the new intent-driven interaction guidance. The triggering and termination of alerts is configured in the existing rule modeler by using rules. There is a new action available to trigger alerts in the intent-driven interaction guidance context. The rule modeler provides business users with more flexibility in triggering alerts because rule modeler attributes can be used to trigger alerts based not only on events, but also on business information such as business partner, product, and business transactions. Previously, alerts were maintained in the alert modeler or in Customizing activity Define Alerts and Alert Profiles. See also Intent-Driven Interaction Guidance (New) ______________________________________________________________ SAP AG 278 SAP-System ______________________________________________________________ 1.23.13 CRM-IC-CHA Communication Channels 1.23.13.1 Display and Maintenance of Contact Attached Data (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can view contact attached data (CAD) in the Interaction Center (IC) WebClient. If the interaction with the customer is via phone, agents can view the CAD on the Identify Account screen or on the Contact Attached Data screen, which they can access from the navigation bar. If the interaction is via e-mail or chat, agents can view the CAD on the Contact Attached Data screen. The CAD comprises: CAD group Attributes Values For example, if the attribute is City, the value might be San Francisco. In Customizing (see below), you can specify whether agents can edit the values of individual attributes in the IC WebClient. The CAD is provided by the communication management software (CMS) as an XML string. In the IC WebClient, the XML data is transformed into an internal table containing attribute and value pairs. Effects on Customizing In Customizing for Customer Relationship Management: 1. Define a CAD profile. Choose Interaction Center WebClient -> Basic Functions -> Communication Channels -> Define Profiles for Contact Attached Data. Assign your CAD profile to a business role. Choose Business Roles -> Define Business Role. 2. 1.23.13.2 Presence - Availability of Agents When Transferring Contacts (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. When an interaction center agent transfers a contact (for example, a telephone call), a tab page in the Transfer dialog box shows which agent groups are available to take the contact. This can significantly ______________________________________________________________ SAP AG 279 SAP-System ______________________________________________________________ reduce the number of unsuccessful transfers, and ensure more timely customer service. This tab page is populated only if: Your communication management software (CMS) supports the exposure of this information to your SAP system In your CMS, you can model a hierarchical structure of the transfer targets, which is shown as a tree structure in the Transfer dialog box. Agents are available in the agent group to take the contact - The tree structure is channel-specific, that is, it displays only agent groups assigned to the current channel. 1.23.13.3 CRM-IC-CHA-TEL Telephony Integration 1.23.13.3.1 Dual Tone Multi Frequency Tones (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can send dual tone multi frequency (DTMF) tones through a standard communication management software (CMS) interface, thereby flexibly supporting: Private branch exchange (PBX) specific commands Automatic call distribution (ACD) specific commands Computer telephony integration (CTI) specific commands For example, you might want to send a DTMF tone for *8 to trigger the switch to put a call back in the queue. You define the DTMF tone in Customizing (see Effects on Customizing below). You then assign the DTMF tone to a toolbar button in a toolbar profile. A button can either be dedicated to sending tones or it can have this function in addition to another function (for example, Hold). Effects on Customizing You define DTMF tones in Customizing for Customer Relationship Management -> Interaction ______________________________________________________________ SAP AG 280 SAP-System ______________________________________________________________ Center WebClient -> Customer-Specific System Modifications -> Define Dual Tone Multi Frequency (DTMF) Tones. 1.23.13.3.2 Simple Computer Telephony Integration (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can restrict computer telephony integration (CTI) in the Interaction Center (IC) WebClient to the following features: Soft phone Screen pop (ANI, DNIS) Screen transfer (handling of contact attached data) This is useful if you want to use the IC WebClient in an environment where simple telephony support and an inbox for asynchronous communication channels are sufficient. The communication management software (CMS) connects the IC WebClient directly to a switch. This means that an IC WebClient session is associated only with an extension or device. The logon process uses a lean version of the free seating logon. A cookie stores the extension information for the user so that it can be defaulted the next time the user logs on. This requires the CMS to check if the user is authorized to use this extension or device number. If the user is not authorized to use it, the CMS returns an error code. When the user is logged on, the ready/not ready states are not transferred to the CMS. 1.23.13.4 CRM-IC-CHA-EMA E-Mail Integration 1.23.13.4.1 Inserting Agent Signatures and Standard Responses in E-Mail Editor (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The name of the current agent (or employee responsible) is available as an attribute in the mail form tool so that agents can create generic signatures with agent name and department name, which they can insert at the end of an e-mail in the e-mail editor. ______________________________________________________________ SAP AG 281 SAP-System ______________________________________________________________ Agents can insert standard responses at the cursor position in the e-mail editor. 1.23.14 CRM-IC-EMS E-Mail Response Management System 1.23.14.1 Pushing E-Mails to Agents (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use communication management software and the ERMS to push and screen pop e-mails to agents. E-mails can be aligned in a universal queue and routed, similar to telephone calls. E-mails are received by SAPconnect, processed by ERMS, and then routed by the communication management software. After e-mails are routed, agents receive a request to process e-mails in the context area. Agents use the toolbar to accept or reject the request. After accepting the request, the e-mail is displayed. A new action, PUSH_EMAIL (Push E-Mail to IC WebClient Agent), is available in the repository. It allows e-mail routing through the communication management software instead of directly going to an inbox. E-mails that are pushed to agents by the ERMS Push action will also be routed to the Agent Inbox by the ERMS default routing, unless another routing destination is specifically maintained. Therefore we recommend directly specifying a Route E-Mail action after the PUSH_EMAIL action, allowing all pushed e-mails to be monitored by a supervisor or special organizational unit, and avoiding misrouting of push e-mails to the default routing that are already completed. See also Release note Inserting Agent Signatures and Standard Responses in E-Mail Editor Release note Transport of Rule Policies and Rules ______________________________________________________________ SAP AG 282 SAP-System ______________________________________________________________ 1.23.14.2 Rules Policies (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. The following enhancements have been made for editing rule policies. You can now use two new operators for rule processing: IsLike IsNotLike These operators can be used to evaluate wildcard expressions. You can now hide actions while editing rule policies by deselecting the checkbox in a new column called Show Actions. You can use this to hide activities that are not relevant to your business needs. By default all actions are shown, so you do not need to perform any additional upgrade activities. 1.23.14.3 CRM-IC-EMS-RUL Rule Maintenance 1.23.14.3.1 Transport of Rule Policies and Rules (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. A new program, Transport Rule Policies (CRM_RULE_TRANS), is available for initiating transports of rule policies and rules to other clients or systems. All associated rule modeler data, such as actions and conditions, is also included in the transport. You can transport rule policies and rules from any rule modeler context, such as ERMS, Order Routing, and so on. This program saves you from manually recreating rule policies and rules in each target system. A new entry is available in the SAP Easy Access Menu under Interaction Center -> E-Mail Response Management System -> Utilities. ______________________________________________________________ SAP AG 283 SAP-System ______________________________________________________________ See also Program documentation 1.23.14.4 CRM-IC-EMS-CAT Categories 1.23.14.4.1 Merge and Import of Categorization Schemas (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Themultilevel categorization component now supports the import and merge of schemas. When you merge two schemas, the object assignments and category assignments are updated in a leading schema based on a lower-level schema. The specific categories or objects that exist in the leading schema are also not lost. Use example: This function enables you to maintain general enhancements centrally in a leading schema as a template schema in order to make them available for a number of productive schemas. The merge mechanism supports the update of categories and object links. In addition, an RFC-enabled function is provided for importing schemas, categories, and object links from other clients or other CRM systems. Note that the functions for merging and importing for CRM systems are supported only as of CRM Release 5.10 or higher. Furthermore, it is necessary to ensure the import of the related objects using other functions (for example, SAP Transport Organizer). The following objects support the import and merge of schemas and categories: Interface method IF_CRM_ERMS_CATEGO_MANAGER~ADD_ASPECT_IMPORT Interface method IF_CRM_ERMS_CATEGO_ASPECT~MERGE Interface method IF_CRM_ERMS_CATEGO_CATEGORY~MERGE Business Add-In (BAdI) CRM_ERMS_CATEGO_OBJECT_BADI IMG activity Maintain RFC Destinations for Schema Import Program CRM_ERMS_CAT_AS_IMPORT Effects on Existing Data The standard system contains BAdI implementations for importing and merging the following objects: Object Search Query Standard Responses Problems and Solutions Service Order Templates Products Merge x x x x x Import x x x ______________________________________________________________ SAP AG 284 SAP-System ______________________________________________________________ Accounts x Enhanced Attributes x Document Template Profile x Activity Template x Subject Code x x x x x x Note that for technical reasons 'Search Queries' cannot be imported or merged using the BAdI. A customer-specific enhancement is not supported. See also For more information see Import Categorization Schemas and Merge Categorization Schemas in SAP Library. 1.24 CRM-MSA Mobile Sales 1.24.1 CSDT and Infocenter (Deleted) Use This release note is only relevant if upgrading from SAP CRM 5.0 The following mobile client features/functions are not supported: o o Central Software Deployment Tool Infocenter 1.24.2 Security Enhancements for CRM Mobile Applications (Enhanced in ______________________________________________________________ SAP AG 285 SAP-System ______________________________________________________________ SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Security features for CRM mobile applications have been enhanced. This enables the system administrator to secure access to mobile applications and to view a log of events related to security. These security features are: In Mobile System Maintenance (MSY), the system administrator can select the security related events that are required to be logged. In MSY, details of the logged security related events can be viewed. In the CRM Server, the system administrator can lock or unlock a user's access to mobile applications. Passwords are now case-sensitive and enforced by the system. Single-sign-on information for integration of Mobile Sales with Mobile Time and Travel is encrypted to protect such information. Effects on Data Transfer The following replication objects must be downloaded from the CRM Server to the consolidated database (CDB): EVNT_LOG_WRITE EVNT_STG_WRITE In addition, the mobile clients must be subscribed to the publication "Customizing Objects 2007". Effects on System Administration This function helps system administrators control and manage security related to mobile applications. 1.24.3 Trade Promotion Management Enhancements (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. ______________________________________________________________ SAP AG 286 SAP-System ______________________________________________________________ Date range enhancements in TPM You can now set the pre-populate flag in Customizing for CRM Server so that when a trade promotion is saved, the trade spend validity dates are automatically defaulted from the corresponding additional date range of the trade promotion. Note: It is now a possibility to define more than five additional date ranges for TPM in CRM Server. As in SAP CRM 5.0, only the first five additional date ranges defined in Customizing for CRM Server will be supported in CRM Mobile Sales. Date ranges are determined for specific combinations of 'Spend Type', 'Spend Category' and 'Spend Method' If the determined date range is not supported in CRM Mobile Sales, the corresponding start and end dates cannot be edited and are display only Changes to the date range (start and end dates) in the trade promotion are automatically reflected in the corresponding trade spend, provided you have not already manually modified the corresponding trade spend validity dates. When you have manually modified the defaulted validity dates for a trade spend, a modified flag is displayed for that trade spend. A warning message will be issued in case the manually maintained dates are outside the corresponding date range. Default list price of reference products So far, the list price of a particular product was getting automatically defaulted. Now, if a particular product does not have a list price and is linked to a reference product, the list price of the reference product is used as the default value. Trade Promotions causing Significant Uplift A new Customizing setting allows you to choose from two integration scenarios between trade promotion planning in CRM and demand planning in SCM. This setting is done on sales organization level. The two integration scenarios are: All promotional uplifts are transferred to demand planning. You can choose this scenario in case you want all promotions created in CRM to be replicated to demand planning in SCM, and the incremental sales volume originating from these promotions to be added to the total demand plan. In this case, the Signif. Uplift flag for trade promotions created within the corresponding sales organization is selected by default. It cannot be manually edited. This scenario was supported in earlier releases as well. You can decide to transfer only trade promotions, which have Signif. Uplift flag selected, to demand planning in SCM. These trade promotions could be one-off promotions with a substantial impact on the total sales volume with the corresponding account. You can choose this scenario in case all regular business, including the sales volume connected to promotions which are repeated every year, would already be included into the demand plan in SCM. In this case, account managers would use the Signif. Uplift flag on promotions to denote the system of exceptional promotions which need to be added to the total demand plan. - - - Note: Through Customizing, you can define the All Uplift settings for sales organizations. ______________________________________________________________ SAP AG 287 SAP-System ______________________________________________________________ Effects on Data Transfer The following objects must be downloaded from CRM Server to the consolidated database (CDB): CRMC_MKTPL_TSDT CRMC_MKTPL_COS3 CRMC_MKTPL_DATE CRMC_MKTPL_UPLIF This enhancement does not effect the publications to which the mobile clients must be subscribed to. The following existing publications can be reused: "Customizing Objects 40" - for trade promotions "Customizing Objects 2007" - for significant uplift Effects on Customizing Date Range: Define date ranges in Customizing for CRM by choosing Marketing -> Marketing Planning and Campaign Management -> Basic Data -> Define Additional Date Ranges - Define spend types in Customizing for CRM by choosing Marketing -> Marketing Planning and Campaign Management -> Key Figure Planning -> Define Marketing Spend Types Significant Uplifts To check the All Uplift flag for a sales organization, you make the settings in Customizing for CRM by choosing Trade Promotion Management -> Basic Data -> Define Uplifts 1.24.4 CRM-MSA-BP Business Partner 1.24.4.1 Life Cycle Stage for Business Partners (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. ______________________________________________________________ SAP AG 288 SAP-System ______________________________________________________________ You can maintain information about the current stage of a business partner's relationship (potential, qualified prospect, and so on) with the organization. To allow users to maintain this information, a new field, Life Cycle Stage, is included in the following areas of Mobile Sales: Business Partners/Details and Business Partners/Search tile sets Business Partner Search dialog box, which appears when users search for business partners in the Contacts/Details tile set Users can also search for business partners based on the life cycle stage. Effects on Existing Data See SAP Note 1050311. Effects on Customizing The values for the Life Cycle Stage field and the permitted sequence of life cycle stages are defined in Customizing for Cross-Application Components by choosing SAP Business Partner -> Business Partner -> Basic Settings -> Business Partner Roles -> Define BP Role Exclusion Groups. 1.24.4.2 Account Classification for Business Partners (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can now assign certain predefined attributes (such as role and rating) to a business partner based on predefined criteria (such as sales organization, distribution channel, division, and country). A business partner can, for example, have the role 'customer' in one sales organization and the role 'competitor' in another. Similarly, a business partner can have the ranking 'gold customer' in one country and the ranking 'silver customer' in another. Effects on Data Transfer The following objects must be downloaded from CRM Server to the consolidated database (CDB): Customizing objects: CRM_DNLBPCLASS CRM_DNLRATING ______________________________________________________________ SAP AG 289 SAP-System ______________________________________________________________ - Replication objects: CRM_DNLBPCLASS CRM_DNLRATING In addition, the mobile clients must be subscribed to the publications, "Customizing Objects 2007" and "Customizing Publications for General Objects". Effects on Customizing The classification categories, attributes, and criteria are defined in Customizing for CRM by choosing Master Data -> Business Partner -> Define Classification. One category 'Account Classification' is delivered in the standard. Customers can define new categories. In the standard, four classification criteria are delivered and they are assigned to the Account Classification category. Customers can assign one more criterion to this category. Customers can define new criteria. In the standard, two classification attributes are delivered and they are assigned to the Account Classification category. Customers can assign additional attributes to this category. Customers can define new attributes. - 1.24.5 CRM-MSA-PAS Products & Services 1.24.5.1 Using Configurable Products Created in the CRM Server (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can now create configurable products in the CRM Server and use them when creating sales transactions in CRM Mobile Sales. For example, when you choose a configurable product in the sales order, the possible characteristics for the product are displayed automatically at item level. You can choose the characteristic values you want and so determine a specific attribute for the configurable product. In case of a personal computer (PC), for example, the characteristics monitor, memory space, or keyboard can vary. ______________________________________________________________ SAP AG 290 SAP-System ______________________________________________________________ Effects on Data Transfer You can download the product configuration information (Knowledge Base), created in the CRM Server, to CRM Mobile Sales by subscribing to the publication: "Configuration Model (by Name + Version)" Note: Only configured products with status released and activated are transferred from CRM Server to CDB. You activate a Knowledge Base in the CRM Server by using Apply Changes button. Only the latest Knowledge Base is considered when you create a new item. 1.24.6 CRM-MSA-ACT Activity 1.24.6.1 Activity Scheduling Functions (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. Scheduling activities as follow-up transactions for open tasks Until now, users could schedule activities based on open tasks, but there was no link between the task and the activity. Users can now schedule activities as follow-up transactions for open tasks. While scheduling an activity based on an open task in the Activity Scheduling tile set, the user can choose to either close the preceding task or leave it in its current state. The follow-up activity has, by default, the same goal, campaign, opportunity, and priority as the preceding task; users can, however, change these attributes. The follow-up activity has a hyperlink, which users can use to navigate from the activity to the preceding task. The preceding task has a note containing information about the follow-up activity. Scheduling activities for contacts In the Activity Scheduling tile set, in addition to scheduling activities based on open tasks, pending activities, and so on, users can now schedule activities for contacts. The behavior of this function is the same as the behavior while scheduling activities for business partners. Checking for business hours while scheduling activities When users schedule activities for business partners and contacts, the application proposes time slots for ______________________________________________________________ SAP AG 291 SAP-System ______________________________________________________________ the activities after checking the visiting hours that are defined in Mobile Sales for the selected business partners and contacts. If the selected business partner has a contact and, If visiting hours are maintained for the contact, the application generates activity proposals based on the visiting hours of the contact. If visiting hours are not maintained for the contact, the application generates activity proposals based on the visiting hours of the business partner. If visiting hours are maintained neither for the contact nor for the business partner, the application generates activity proposals based on the working hours of the logged-in sales representative. - If the selected business partner does not have a contact and, If visiting hours are maintained for the business partner, the application generates activity proposals based on the visiting hours of the business partner. If visiting hours are not maintained for the business partner, the application generates activity proposals based on the working hours of the logged-in sales representative. Status-based coloring of activities in the calendar Activities in the calendar appear in different colors based on their status. Effects on System Administration Business hours check: By default, this function is disabled because it affects performance. If this check is required, the administrator must enable it in Mobile System Maintenance (MSY) by setting the ACTBUSHOURCHECK application parameter to ON. Status-based coloring of activities in the calendar: The color that appears in the calendar depends on the following settings that the system administrator defines in Mobile System Maintenance (MSY): Values for the STATUSCOL (activity status) choice field Values for the COLORCOL (status color) choice field Mapping (hierarchy) between the STATUSCOL and COLORCOL choice fields - 1.24.6.2 Synchronization of Attachments in Activities with MS Outlook (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. ______________________________________________________________ SAP AG 292 SAP-System ______________________________________________________________ You can synchronize attachments to activities from the mobile client to the MS Outlook calendar and vice versa. To enable synchronization of attachments, users must select the Include Attachments indicator in the SAP CRM Calendar Synchronization Properties dialog box. Note: The SAP CRM Calendar Synchronization Properties dialog box appears when users choose: Tools -> Options -> SAP CRM Calendar Properties tab page -> Options# pushbutton in MS Outlook Tools -> Options for Synchronization in the mobile application Effects on Data Transfer When users synchronize activities between mobile clients and MS Outlook, files that are attached to activities are also copied from the mobile application to MS Outlook and vice versa. 1.24.6.3 Attachment of Account Fact Sheet to Activities (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. When you as a user create or maintain an activity for a business partner, you can attach the PDF file of the related account fact sheet to the activity. This is possible if the related fact sheet is available offline. If the fact sheet is not available offline, you can create a request in Mobile Sales for the fact sheet to be generated in the CRM Server. Note: At the next synchronization, the request is processed and the fact sheet is downloaded to the mobile clients. These functions (requesting for and downloading fact sheets) are the same as in previous releases and have not changed in SAP CRM Mobile Sales 2007. Effects on Data Transfer When the activity is uploaded to the CRM Server, it is saved in the CRM database. In the CRM Server, if a user attaches a new fact sheet to the same activity, then this fact sheet is stored as a separate attachment distinct from the fact sheet that the mobile user attached. A different naming convention differentiates these fact sheets. ______________________________________________________________ SAP AG 293 SAP-System ______________________________________________________________ 1.24.7 CRM-MSA-OPP Opportunities 1.24.7.1 Assessments in Opportunities Based on Expected Sales Volume (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can configure the application to automatically prompt users to fill an assessment for an opportunity when the expected sales volume or expected total value exceeds a predefined threshold. Further, you can specify whether the assessment is mandatory or optional. Effects on Customizing The settings for this new function are defined in Customizing for CRM by choosing Transactions -> Settings for Opportunities -> Sales Methodology -> Questionnaire for Opportunities. 1.24.7.2 Maintenance of Competitor Product Information in Opportunities (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can maintain the following information about competitor products in opportunities: Competitor product ID and description Expected sales volume of the competitor product Currency for expected sales volume of the competitor product Note: The currency that the user enters for the opportunity as a whole (header) appears, by default, as the currency for the individual competitor products. Users can change the currency for the competitor ______________________________________________________________ SAP AG 294 SAP-System ______________________________________________________________ products. Indicator showing whether the competitor won the deal for the product Probability of the competitor winning the deal Notes about the strengths and weaknesses of the competitor Effects on Customizing The competitor product information can be maintained either for the opportunity at the header level, or for individual products in the opportunity depending on the competitor mode that you define in Customizing for CRM by choosing Transactions -> Basic Settings -> Define Transaction Types. 1.24.8 CRM-MSA-AMT Authorization Management Tool 1.24.8.1 Mass Assignment and Unassignment of Roles to Users in AMT (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. As a system administrator, you can assign multiple roles to multiple mobile users, and vice versa, in a single action. You can also unassign multiple roles from users in a single action. Before this release, system administrators could only assign one role-user combination at a time. Effects on System Administration This function helps improve the efficiency of system administrators. 1.24.8.2 Authorization in AMT for Pricing Details (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. ______________________________________________________________ SAP AG 295 SAP-System ______________________________________________________________ You can impose access restrictions on the following additional tile sets of Mobile Sales: Sales Transactions -> Item: Price Details Sales Transactions -> Price Details Effects on System Administration The system administrator can control access to the Sales Transactions -> Item: Price Details and Sales Transactions -> Price Details tile sets, by assigning access rights for these tile sets to only the required roles. 1.24.9 CRM-MSA-SAD Sales Document 1.24.9.1 Comparing Product Configurations (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can now compare the characteristic values of two product configuration states. This is useful when a sales item is a configured product. This makes it easier for you to decide which product configuration is more suited to your requirements. In the change mode, you have the following options for configuration comparison: Take Snapshot You can store a chosen product configuration at a certain point as a snapshot. The snapshot is not saved to the database. Compare Snapshot You can compare the currently selected product configuration with a snapshot. Compare to Stored Version If you want to reprocess a sales order with which a product configuration was saved, you can compare the new configuration with the previously saved product configuration. ______________________________________________________________ SAP AG 296 SAP-System ______________________________________________________________ 1.24.10 CRM-MSA-PAC Campaigns & Promotions 1.24.10.1 Product Planning Basis for Trade Promotions and Deals (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can, while planning a trade promotion/deal for an entire product category or product group, assign the product category or product group to the trade promotion/deal, instead of assigning individual products one at a time. This improves operational efficiency. To allow users to assign product groups or product categories to trade promotions/deals, a new field, Prod. Plng Basis, is available in the Marketing/Details tile set of Mobile Sales. It appears in the header for deals and trade promotions. In this field, users can choose the basis for planning volumes and trade spends when they create trade promotions and deals. The possible values for this field are: Product Product group Product category Product group and product Product category and product Depending on the planning basis that the users choose, the Products, Product Categories, and Product Groups tile sets are then available for selection. Effects on Existing Data See SAP Note 1050311. Effects on Customizing The values that users must be able to select (based on the business needs) and the default value for the Planning Basis field are defined in Customizing for Customer Relationship Management (CRM) by choosing Marketing -> Marketing Planning and Campaign Management -> Product Assignments -> Define Product Planning Basis. ______________________________________________________________ SAP AG 297 SAP-System ______________________________________________________________ 1.25 CRM-MSE Mobile Service 1.25.1 Mobile Service Functions (Changed) Use This release note is only relevant if upgrading from SAP CRM 5.0. The following mobile service functions are disabled because they are not in scope: Usage-based billing Assignments for service orders Object structure In product service letters (PSLs), the subject data is made read-only. 1.25.2 Security Enhancements for CRM Mobile Applications (Enhanced in SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Security features for CRM mobile applications have been enhanced. This enables the system administrator to secure access to mobile applications and to view a log of events related to security. These security features are: In Mobile System Maintenance (MSY), the system administrator can select the security related events that are required to be logged. In MSY, details of the logged security related events can be viewed. In the CRM Server, the system administrator can lock or unlock a user's access to mobile applications. Passwords are now case-sensitive and enforced by the system. Single-sign-on information for integration of Mobile Sales with Mobile Time and Travel is encrypted to protect such information. ______________________________________________________________ SAP AG 298 SAP-System ______________________________________________________________ Effects on Data Transfer The following replication objects must be downloaded from the CRM Server to the consolidated database (CDB): EVNT_LOG_WRITE EVNT_STG_WRITE In addition, the mobile clients must be subscribed to the publication "Customizing Objects 2007". Effects on System Administration This function helps system administrators control and manage security related to mobile applications. 1.25.3 Local Stock Information Update (New in SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. Stock information for service parts is updated on the mobile client when service technicians process goods movements or service confirmations in an offline mode. This enables service technicians to use latest stock information when fulfilling service requests. When a service technician creates a service confirmation with a serial number relevant service part, stock information on the mobile client is updated depending on the serialization option for that service part as maintained in the CRM product master. In this case, for the local stock to get updated, the only relevant serialization options are: 3 - Check in CRM Against Individual Object and Serial Number 4 - Check in ERP Against Serial Number Note: When a service technician creates a service confirmation with a batch relevant service part, stock information on the mobile client is not updated. Effects on Existing Data This section is only relevant if you are upgrading from any previous release of SAP CRM Mobile Service 2007. 1. In SAP NetWeaver Mobile, choose the path Data Orchestration Engine -> Data Orchestration Admin and Monitoring Portal ______________________________________________________________ SAP AG 299 SAP-System ______________________________________________________________ 2. Choose Recover Device option on the Device Administration screen for: Device Name with value CRM Data Objects as MSV_STOCK and MSV_GM Effects on System Administration The system administrator can enable or disable the local stock update function by making appropriate settings in the CRM Mobile System Maintenance (MSY) application. To enable this feature, Choose Cross-Component Settings Select the Choice Field ENABLELOCALSTOCK and set the Choice Field Value to True 1.25.4 Goods Movement (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. As a service representative, you can maintain goods movement (movement of stock) transactions so that stock information is accurate. You can enter the following details on the mobile client: Goods receipt Leads to an increase in stock Goods issue Leads to a reduction in stock - Transfer posting Leads to stock transfers and changes in stock type or stock category of a material In addition, you can cancel goods movement documents created in CRM Mobile Service. Effects on Data Transfer You have installed SAP ECC 2005 (ERP Central Component - Enhancement pack 3) and SAP NetWeaver Mobile 7.1 SP03 as these systems exchange data with SAP CRM Mobile Service. ______________________________________________________________ SAP AG 300 SAP-System ______________________________________________________________ As a prerequisite to data exchange, the system administrator should have: Mapped the SAP CRM Mobile Service user to an existing CRM Server user Created a user in SAP ECC with the same username as in CRM Server Ensured that mobile clients are subscribed to the following publications: Goods Movement (by Issuing Plant and Storage location) Goods Movement (by Receiving Plant and Storage location) Customizing_Vanstock Downloaded the following Customizing objects to consolidated database (CDB): System From SAP ECC Customizing object CUST_STLOC : Storage location From SAP ECC using SAP NetWeaver Mobile 7.1 SP03 MSV_PLANT: Plant data MSV_FLDCUST: Field customization MSV_MVT_TYPES : Goods movement types MSV_MVT_REASONS : Goods movement reasons Effects on System Administration The system administrator must make the following settings in CRM Mobile System Maintenance application: Stock Management Assign plant and storage location with employees Cross-Component Settings Select the Choice Field ENABLEVANSTOCK and set the Choice Field Value to True Use Choice Fields to change the description of movement types, if required Note: CRM Mobile Service 2007 supports the following goods movement types: Movement Type (choice field value) 101 into warehouse 102 into warehouse 301 (one-step) 302 (one-step) Goods Movement (choice field description) GR goods receipt Reversal of GR TF tfr.plnt.to plnt. TR tfr.plnt.to plnt. Description Goods receipt for purchase order or stores Goods receipt for purchase order - reversal Transfer posting plant to plant Transfer posting plant to plant reversal ______________________________________________________________ SAP AG 301 SAP-System ______________________________________________________________ 303 remove from 304 remove fm 305 place in storage 306 place in storage 311 (one-step) 312 (one-step) 313 to storage 314 to storage reversal 315 to storage 316 to storage reversal 561 balances into 562 balances to TF rem.fm.stor.to pl TR rem.fm.stor.to pl TF pl.in stor.in pl. TR pl.in stor.in pl. TF tfr. within plant TR transfer in plant TF rem.fm.str.toSLoc TR rem.fm.str.toSLoc Transfer posting plant to plant storage (two - step) Transfer posting plant to plant storage - reversal (two - step) Transfer posting plant to plant (two - step) Transfer posting plant to plant reversal (two - step) Transfer posting storage location Transfer posting storage location reversal Transfer posting storage location location - remove from storage Transfer posting storage location location - remove from storage Transfer posting storage location location - place in storage Transfer posting storage location location - place in storage Receipt per initial entry of stock unrestricted - use Receipt per initial entry of stock unrestricted. - reversal TF pl.in str.in Sloc TR pl.in stor.inSLoc GI entry of st. bals RE entry of st.bals. Effects on Customizing You should have made all relevant Customizing settings related to this feature in SAP ECC. 1.25.5 Reservations and Purchase Requisitions (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. This feature enables you to replenish depleted stock items, or order for new stock items. The following options are available to you: Create reservation against existing stock Create purchase requisitions to request for stock items you want ______________________________________________________________ SAP AG 302 SAP-System ______________________________________________________________ Reservations You can replenish stock by creating a reservation to reserve another service representative's stock or that of another storage location. The reservation is then processed in one of the following ways: The second service representative (or another storage location) creates the transfer posting, with reference to the reservation, to move the reserved stock item to unrestricted stock. You can create (on behalf of the second service representative or another storage location) the transfer posting, with reference to the reservation, to move the reserved stock item to unrestricted stock. You can also: Select the Deletion Indicator to cancel reservations Purchase Requisitions You can create purchase requisitions and then synchronize with SAP ECC where follow-up purchase orders and delivery transactions are created. These reference documents are then synchronized to the CRM Mobile Service client. Note: When the purchase requisition goods are received, you create (in the Goods Movement component) a goods receipt with reference to the delivery or purchase order. On synchronization, stock gets updated. In addition, you can do the following: View reference (follow-up) purchase orders or deliveries Search for purchase orders or deliveries, including those associated with purchase requisitions, using flexible search View purchase order or delivery details using search and appropriate links Set the deletion indicator flag when you wish to cancel the requisition Effects on Data Transfer You have installed SAP ECC 2005 (ERP Central Component - Enhancement pack 3) and SAP NetWeaver Mobile 7.1 SP03 as these systems exchange data with SAP CRM Mobile Service. As a prerequisite to data exchange, the system administrator should have: Mapped the SAP CRM Mobile Service user to an existing CRM Server user Created a user in SAP ECC with the same username as in the CRM Server ______________________________________________________________ SAP AG 303 SAP-System ______________________________________________________________ - Ensured that mobile clients are subscribed to the following publications: Requisitions / Reservations (by Doc Type & Created By) Requisitions / Reservations (by Req.Plant & SL, Doc Type) Requisitions / Reservations (by Sup.Plant & SL, Doc Type) Purchase Order (by Requesting plant and Storage location) Deliveries (by Requesting Plant, Requesting Storage Location) Goods Movement (by Issuing Plant and Storage location) Goods Movement (by Receiving Plant and Storage location) Customizing_Vanstock - Downloaded the following Customizing objects to consolidated database (CDB): System From SAP ECC combination CUST_PURGRP - purchase groups CUST_PURORG - purchase organizations From SAP ECC using SAP NetWeaver Mobile 7.1 SP03 MSV_PLANT: Plant data MSV_FLDCUST: Field customization MSV_PD_TYPES - purchase document types MSV_MVT_TYPES: Goods movement types MSV_MVT_REASONS: Goods movement reasons Customizing object CUST_STLOC: Storage location CUST_POPLANT - purchase org. and plant Effects on System Administration The system administrator must make the following settings in CRM Mobile System Maintenance application: Stock Management Assign plant and storage location with employees Cross-Component Settings Select the Choice Field ENABLEVANSTOCK and set the Choice Field Value to True Maintain the list of applicable purchase document types in the Choice Field MSVPURDOCTYPE Maintain the list of applicable requisition document types and categories in the Choice Fields MSVREQDOCUMENTTYPE and MSVREQDOCUMENTCAT Effects on Customizing ______________________________________________________________ SAP AG 304 SAP-System ______________________________________________________________ You should have made all relevant Customizing settings related to this feature in SAP ECC. You have made settings for purchasing document types in Customizing for SAP ECC by choosing SAP Customizing Implementation Guide -> Materials Management -> Purchasing -> Purchasing Documents 1.25.6 Stock Overview (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. As a part of the service organization, you can view stock information. This helps, for example, service representatives have the right service parts at the customer site, or know where the right service parts can be found. With CRM Mobile Service, you can view stock overview information including: Quantity of own stock items Quantity of stock items with other service representatives Quantity of stock items with the team Quantity of stock items with another storage location Using flexible search facilities, you can selectively view stock information. Effects on Data Transfer You have installed SAP ECC 2005 (ERP Central Component - Enhancement pack 3) and SAP NetWeaver Mobile 7.1 SP03 as these systems exchange data with SAP CRM Mobile Service. As a prerequisite to data exchange, the system administrator should have: Mapped the SAP CRM Mobile Service user to an existing CRM Server user Created a user in SAP ECC with the same username as in the CRM Server Ensured that mobile clients are subscribed to the following publications: Customizing_Vanstock Stock By Material Stock By Plant ______________________________________________________________ SAP AG 305 SAP-System ______________________________________________________________ - Stock By Plant range Stock By Plant-SL Stock By Plant-SL range Downloaded the following Customizing objects to consolidated database (CDB): System From SAP ECC Customizing object CUST_STLOC: Storage location From SAP ECC using SAP NetWeaver Mobile 7.1 SP03 MSV_PLANT: Plant data MSV_FLDCUST: Field customization MSV_MVT_TYPES : Goods movement MSV_MVT_REASONS : Goods types movement reasons Effects on System Administration The system administrator must make the following settings in CRM Mobile System Maintenance application: Stock Management Assign plants and storage locations with employees Cross-Component Settings Select the Choice Field ENABLEVANSTOCK and set the Choice Field Value to True Effects on Customizing You should have made all relevant Customizing settings related to this feature in SAP ECC. 1.26 CRM-FRW Framework 1.26.1 Portal Integration (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. ______________________________________________________________ SAP AG 306 SAP-System ______________________________________________________________ You can use the transaction launcher to call applications that are to be executed outside of the CRM WebClient. When you are working in the CRM WebClient integrated in SAP NetWeaver Portal, and you want to navigate from a CRM application to native portal pages that contain applications or content, the transaction launcher supports direct navigation to those pages that are loaded to the portal content area. The navigation is carried out as an object-based navigation (OBN) in the portal. You can use the Universal Worklist (UWL), which is a SAP NetWeaver application, instead of the CRM worklist to manage your open workflow tasks and alerts. The cross-navigation from the UWL to CRM target applications is supported. To enable this navigation, you need to configure your workflow tasks and alerts. Effects on Customizing To enable the portal integration, you have made the necessary settings in Customizing for Customer Relationship Management, by choosing UI Framework -> Technical Role Definition -> Transaction Launcher -> Define URLs and Parameters. 1.26.2 Portal Integration (New) Use This release note is relevant if upgrading from SAP CRM 5.0. The CRM WebClient UI has been integrated in SAP NetWeaver Portal. You can now run the CRM WebClient UI in a full page iView in the portal. On every portal page only one iView with CRM content is displayed. The portal integration offers the following features: Aligned session management When the first navigation to SAP CRM is executed in the portal, a logon to SAP CRM is started; when a portal session is finished, all open CRM sessions are closed; a data loss popup informs the users that they first need to save their changes. Portal navigation with navigation highlighting The portal highlights the navigation target, if you navigate from the portal navigation frame to SAP CRM, from SAP CRM to portal content, or from one CRM iView to another (cross-component navigation). A tool to export role definitions to XML You can use the upload tool to generate an XML file of your business role. This XML file can be imported into SAP NetWeaver Portal to generate a portal role. Central search You can search for CRM applications in the central search that is located in the header area of the portal desktop. For more information, see release note Central Search (New). - - - ______________________________________________________________ SAP AG 307 SAP-System ______________________________________________________________ - Mapping of a portal theme to a CRM skin To align the look and feel of SAP NetWeaver Portal and SAP CRM, you can map a portal theme to its most similar CRM skin. You can select the additional CRM skin Follow Portal Theme to display the CRM skin mapped to the portal theme in the mapping table. Note The portal roles supported in SAP CRM 5.0 are replaced by portal roles that you can generate by using the role upload tool. Effects on Customizing You have made the necessary settings. For more information, see Portal Integration Overview. See also For more information about the upgrade from SAP CRM 5.0 to the current release, see the introduction and the section 'Portal Integration' in the Migration Guide for SAP CRM 2007. 1.26.3 Working Context (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use the working context with trade promotion management (TPM). The working context is assigned to the business role, and it allows users to preset values for certain attributes. These values are then used as defaults when the user performs an advanced search or creates a new object. For example, if a key account manager (KAM) works primarily with a particular account and product category, the KAM could create a working context for these values. This would make the values appear by default on search pages and when creating, for example, a new trade promotion. You can determine whether the working context for a business role is strict or flexible. Strict means that the user can disable the working context, but cannot use values outside it. This prevents the user from accidentally leaving the working context. Flexible control allows the user to disable the working context, as well as enter values other than those of the working context. ______________________________________________________________ SAP AG 308 SAP-System ______________________________________________________________ 1.26.4 CRM-FRW-AFP Application Frame 1.26.4.1 Central Search (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Central Search in CRM WebClient Standalone The central search is now available in the header area of the CRM WebClient. When you open the search menu you see Saved Searches in first position and below, a hierarchical list of object types. If you select an object type in the list with mouseover, a cascading menu with the search attributes assigned to that object type opens. After you have selected a search attribute, you can enter the search value in the input field. The field label changes accordingly, for example, to Search for Accounts by Category. When you select Saved Searches, the search menu contains all your saved searches and the field label changes to Saved Searches. You can use the Advanced link to navigate to the advanced search for a selected object type, for example, to the Account search page or to a saved search. Central Search in the Portal-Integrated CRM WebClient The central search in the portal-integrated CRM WebClient has been changed. The look and feel of the central search is similar to that in the CRM WebClient standalone application. The search menu only consists of the hierarchical list of object types. You can additionally search for Documents, which means that a KM search is started instead of a search in the CRM application. Saved searches are available at the top of the work area. Effects on System Administration To make the central search visible, you need to make the necessary configuration settings in the UI Configuration Tool. For more information, see documentation about the header area configuration at business role level in the SAP Help Portal. Effects on Customizing To define the central search in the CRM WebClient standalone and in the portal-integrated CRM WebClient, you have made the necessary settings in Customizing for Customer Relationship Management, by choosing UI Framework -> Technical Role Definition -> Define Central Search. To make business objects invisible at business role level in the central search in the CRM WebClient standalone and in the portal-integrated CRM WebClient, you have made the necessary settings in Customizing for Customer Relationship Management, by choosing Business Roles -> Define Business Role. ______________________________________________________________ SAP AG 309 SAP-System ______________________________________________________________ 1.26.4.2 Central Search (New) Use This release note is relevant if upgrading from SAP CRM 5.0. You can use the central search to search for CRM business objects and documents in the CRM WebClient integrated in SAP NetWeaver Portal. It is located in the header area of the portal desktop and hence visible and accessible at all times. Via Customizing, you can define what the central search looks like for every business role and what it is for: If the central search is customized with two dropdown boxes and an entry field, the user can search for a business object type, such as 'Employee' in the first dropdown box and an attribute, such as 'Last Name' in the second dropdown box. In the entry field, the user can enter a search value, such as 'Smith'. If the central search is customized with a single dropdown box and an entry field, the user can select a combination of business object type and attribute from this dropdown box and enter a search value in the entry field. If you search for documents, a document search with the Search and Classification tool (TREX) is started instead of a search in the CRM application. - - After the user has executed the search, the system navigates to the search page of the corresponding business object where the search result is displayed in the result list. Effects on Customizing You have made the necessary settings in Customizing for Customer Relationship Management, by choosing UI Framework -> Technical Role Definition -> Define Central Search. You have made the necessary settings in the UI configuration of the UI components and views via the UI Configuration Tool. For more information how to start the UI Configuration Tool, see release UI Configuration Tool. You have activated the search for documents in the SAP NetWeaver Portal. For more infomation, see Adapting the Header Area of the CRM Portal Desktop -> CRM Tools in Portal Integration Overview. - ______________________________________________________________ SAP AG 310 SAP-System ______________________________________________________________ 1.26.5 CRM-FRW-CON UI Configuration Tool 1.26.5.1 UI Configuration (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Direct Access from the CRM WebClient UI You can directly access the UI configuration of pages from the CRM WebClient. You can configure home pages, work center pages, and overview pages, by choosing the corresponding icon at the top of the page. To show the configurable areas on a page, you can choose the corresponding icon. If you click the icon, all configurable views on this page are displayed and you can start the configuration of every displayed configurable view. You can directly access the UI configuration from the F2 help. To find out the name of an application component or view, you can click F2. The Technical Details dialog with the technical information is started. By clicking the 'Configure' icon at the bottom of the dialog, you can directly access the UI configuration of this component. You can directly access the fact sheet configuration from the CRM WebClient. All configuration changes that you have made in an application are automatically visible in the application. You can create a new transport request or select an existing transport request in the CRM WebClient. Configuration Based on Enhancement Sets If you select an application component and view in the CRM WebClient for which an enhancement set has been previously created in the SAP GUI, you can perform configuration based on the enhanced component. Configuration Access Sequence You can change the standard access sequence that is used to determine configurations. The actual configuration that is used for a certain configurable view is determined on the basis of a search key and the available configurations that exist for a specific view. The configuration can either be a standard SAP configuration or a customer-specific configuration. Effects on Customizing To use your own access sequence, you need to implement the Business Add-In (BAdI) BSP_DLC_ACCESS_ENHANCEMENT in Customizing for Customer Relationship Management, by choosing UI Framework -> UI Framework Definition -> Business Add-Ins (BAdIs) -> Define Configuration Access -> BAdI: Configuration Access Determination. ______________________________________________________________ SAP AG 311 SAP-System ______________________________________________________________ 1.26.5.2 UI Configuration Tool (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. You can now access the UI Configuration Tool directly in the CRM WebClient UI via hyperlinks in the navigation bar. However, you can still use the BSP Component Workbench (transaction BSP_WD_CMPWB) to access the UI Configuration Tool. The UI Configuration Tool offers the following features in the CRM WebClient UI: View Configuration The system administrator can configure form views, overview pages, search pages, tables, and work centers. Fact Sheet Configuration The system administrator can configure fact sheets. - If you want to configure views and fact sheets in the CRM WebClient UI and need to create a transport request, you can use report BSP_DLC_TRANSPORT_CONFIG_TEXT. Effects on Customizing To make the UI Configuration Tool accessible in a system administrator role in the CRM WebClient UI, you have made the necessary settings in Customizing for Customer Relationship Management, by choosing UI Framework -> Technical Role Definition -> Define Navigation Bar Profile. See also For more information about the UI Configuration Tool, see SAP Library at Customer Relationship Management -> Components and Functions -> Basic Functions -> UI Configuration. 1.26.6 CRM-FRW-ROL Roles Management 1.26.6.1 User roles (changed, new) Use As of Release SAP CRM 5.1, the following user roles are available: Marketing ______________________________________________________________ SAP AG 312 SAP-System ______________________________________________________________ - Service Sales IC Manager IC Agent E-Commerce Manager Channel Manager Partner Manager Leasing Manager Grantor Program Manager Life Sciences: Contract Manager Provider-IC Agent Provider-Dealer The contents of all user roles named above were adjusted to the new user interface, that is, they offer a uniform page layout, simple and intuitive navigation, and ease of personalization. Effects on Customizing To set up new user roles, make the following settings in the Implementation Guide (IMG): Define logical links as jump destinations to CRM components Use IMG activity UI Framework -> Technical Role Definition -> Define Navigation Profile. Define link groups for work centers and assign to them all logical linksthat contextually belong together from the process viewpoint. Use IMG activity UI Framework -> Technical Role Definition -> Define Navigation Profile. Define work centers and assign to them the work center link groups you want. Use IMG activity UI Framework -> Technical Role Definition -> Define Navigation Profile. Define groups for direct links and assign to them all logical links that are to appear in the shortcuts in the navigation bar. Use IMG activity UI Framework -> Technical Role Definition -> Define Navigation Profile. Define a navigation profile and assign work centers and groups of direct links to it. Use IMG activity UI Framework -> Technical Role Definition -> Define Navigation Profile. Define an authorization profile for your business role. Use IMG activity Technical Role Definition -> Define Authorization Profile. Assign the navigation profile you created and the authorization profile to your business role. Use IMG activity Business Roles -> Define Business Role. - - ______________________________________________________________ SAP AG 313 SAP-System ______________________________________________________________ - Determine the links to be displayed in the work center and in the navigation bar for your business role. Use IMG activity Business Roles -> Define Business Role. Assign your business role to an organizational unit. Use IMG activity Business Roles -> Define Organizational Assignment. 1.26.6.2 Business Role Customizing (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Business role Customizing is now available in the CRM WebClient UI. You can start the Customizing directly in the navigation bar of your business role. You can search for an existing business role, copy an existing business role, or create a new one. All necessary information assigned to your business role is displayed in an editable overview page. The Business Role Details block contains general data and the assigned profiles. In the following assignment blocks, you can perform the same Customizing activities as in business role Customizing in the SAP GUI: Navigation Bar Direct Link Groups Keyboard Shortcuts Central Search Function Profiles If you save your business role data, you can create a new transport request or select an existing one. You can directly access the translation of your business role and select the languages into which your business role is to be translated. You can directly access the PFCG transaction launcher to define the authorization role (PFCG role) for your business role. Additionally, the Customizing activities for business roles in SAP GUI have been enhanced. These functions are also available in the CRM Web Client UI. You can do the following: Rename work centers and change the sorting of work centers in the navigation bar of a business role. Rename logical links and change the sorting of logical links within a work center of a business role. Rename direct link groups and change the position of a direct link group in the navigation bar of a business role. Assign icons to work centers and to some links in a direct link group of a business role. Make objects that are used in the central search visible or not visible. Additionally, you can define in Customizing via a parameter in the IMG customizing, whether the sorting of logical links on work center pages and home pages should be alphabetical or not. ______________________________________________________________ SAP AG 314 SAP-System ______________________________________________________________ 1.26.6.3 User Role IPM Rights Manager (New) Use The following user role is now available: IPM Rights Manager The contents of the user role were adapted for the CRM WebClient user interface. The user interface now offers a uniform page layout, simple and intuitive navigation, and ease of personalization. Effects on Customizing To set up new user roles, make the following settings in the Implementation Guide (IMG): Define logical links as jump destinations to CRM components. Use IMG activity Define Navigation Bar Profile. Define link groups for work centers and assign to them all logical links that contextually belong together from the process viewpoint. Use IMG activity Define Navigation Bar Profile. Define work centers and assign to them the work center link groups you want. Use IMG activityDefine Navigation Bar Profile. Define groups for direct links and assign to them all logical links that are to appear in the shortcuts in the navigation bar. Use IMG activityDefine Navigation Bar Profile. Define a navigation profile and assign work centers and groups of direct links to it. Use IMG activityDefine Navigation Bar Profile. Define an authorization profile for your business role. Use IMG activityDefine Authorization Role. Assign the navigation profile you created and the authorization profile to your business role. Use IMG activityDefine Business Role. Determine the links to be displayed in the work center and in the navigation bar for your business role. Use IMG activityDefine Business Role. Assign your business role to an organizational unit. Use IMG activityDefine Organizational Assignment. ______________________________________________________________ SAP AG 315 SAP-System ______________________________________________________________ 1.26.7 CRM-FRW-UI User Interface 1.26.7.1 User Interface Personalization (Enhanced) This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The personalization of the overview page in the CRM WebClient has been enhanced. In the personalization dialog on the overview page of an application you can select if you want to display assignment blocks directly in an open state, by choosing the indicator Display Directly. The load options Direct, Lazy, and Hidden of assignment blocks are initially configured in the UI configuration tool. You can now adapt these attributes to your personal needs and override the initial configuration in the personalization dialog. You can return to the initial configuration, by clicking Reset to Default in the personalization dialog. 1.26.7.2 UI Configuration: Usability (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The following usability enhancements are now available in the UI configuration in the CRM WebClient: The configuration block in the UI configuration in the CRM WebClient UI now contains a table. All configurations that are available for a selected view are displayed in this table. A Search button is provided to start the search for application components and fact sheets. In the table configuration the number of visible rows and the number of visible rows before paging can be defined. You can directly start the configuration of dependent views from the fact sheet configuration. The different fact sheet page types and layouts are shown in the fact sheet configuration. The colors of the tiles shown in the fact sheet configuration now depend on the skin. ______________________________________________________________ SAP AG 316 SAP-System ______________________________________________________________ 1.26.7.3 CRM WebClient User Interface (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. The CRM WebClient UI has been enhanced with the following features: Editable Overview Page The editable overview page has been introduced for all CRM business objects with overview pages. This includes most of the assignment blocks in which information is displayed in form views and tables. Here the user can now directly change the information on the overview page without navigating to a separate edit page. The overview page contains the most important information about a business object. Note The existing overview pages and concept are still fully supported within this release. However, because the new concept (editable overview pages) is seen as 'go-to-concept', support for the previous overview page concept could be ended in a future release. Central Search The central search has been introduced in the CRM WebClient integrated in SAP NetWeaver Portal. The user can now search for CRM applications and documents with a centrally located and easily accessible search function. For more information, see release note Central Search (New). Drag and Drop The drag and drop function supports easy and intuitive personalization of the CRM WebClient UI. You can now rearrange information blocks on the home page, on work center pages, and on report pages in your business role. You can define the sequence of assignment blocks on overview pages and the sequence of columns in tables. You can define the column width in tables. Filter in Tables You can adapt the display of information in tables to your personal needs. If you click on the column header, you can now filter and sort the table records in ascending and descending order. You can reset the filter and also set manual filters. An icon indicates which columns the user has sorted or filtered. Portal Integration The CRM WebClient has been integrated in SAP NetWeaver Portal. The user can carry out portal navigation and other portal functions. For more information, see release note Portal Integration. Personalization The personalization of the CRM WebClient UI has been enhanced by a central personalization page that offers several features for users to adapt their working environment to their personal - - - - - ______________________________________________________________ SAP AG 317 SAP-System ______________________________________________________________ requirements. For more information, see release note Personalization (Enhanced). Miscellaneous You can activate or deactivate the central personalization page and the personalization in the work area. You can select the logon language in the logon screen. You can highlight mandatory fields with a background color directly in the field via style sheet Customizing. You can collapse and expand the navigation bar. A new skin named NOVA is delivered. 1.26.7.4 Personalization (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. You can use the personalization functions to personalize your working environment easily regarding settings, layout, and content provided in the CRM WebClient UI. The personalization page is accessible via a hyperlink that is centrally located in the header area of the CRM WebClient UI. It consists of information blocks with hyperlinks; every hyperlink leads to a separate dialogue in which the user can make his or her settings. The personalization page consists of the following information blocks: My Data You can change your personal data, such as address data, communication data, and organizational information. You can also change your password. Settings You can personalize general settings, such as time zone, time format, and screen reader mode. Groupware Integration You can synchronize the groupware integration, such as setting up your e-mail transfer with Microsoft Outlook, synchronizing the settings for your personal calendar, tasks, and contacts with SAP CRM, and installing a new version of groupware synchronization settings on your local computer. Layout You can personalize the layout, such as skin and text size, and enable fast performance mode with fewer UI features and visual effects. You can personalize the links in the navigation bar, which - - ______________________________________________________________ SAP AG 318 SAP-System ______________________________________________________________ means you can select which links that are available for your business role are to be displayed in the navigation bar, such as 'Appointment', 'E-Mail', or 'Task'. Shortcuts You can personalize the keyboard shortcuts for your business role. With the focus shortcuts you can set focus to specific areas, such as header area or navigation bar. You can use the navigation shortcuts to navigate to other views or components. Effects on Customizing You can activate or deactivate the personalization page and the work area personalization independently in your business role. You can use the function profile 'Personalization' and its predefined profile values in Customizing for Customer Relationship Management, by choosing Business Roles -> Define Business Role. You can define the keyboard shortcuts for the central personalization page in your business role in Customizing for Customer Relationship Management, by choosing Business Roles -> Define Business Role. You can deactivate the Groupware Integration via the parameter GWS_DISABLED in a function profile in Customizing for Customer Relationship Management, by choosing UI Framework -> Technical Role Definition -> Define Parameters. - - 1.27 CRM-CHM Channel Management 1.27.1 Partner Channel Management (Changed) Use This release note is only relevant if upgrading from SAP CRM 5.0. The key capability "channel management" is now called "partner channel management". ______________________________________________________________ SAP AG 319 SAP-System ______________________________________________________________ 1.27.2 Partner Channel Management (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. Market Development Funds For more information about market development funds (MDF), see the separate release note Market Development Funds. Roles Channel Manager (CHM-CM) We now deliver the following additional features for this business role: Market development funds Use of marketing attributes to maintain values for product recommendations. This function supersedes the My Marketing Profile function. Indexed catalog variants Partner Manager (CHM-PM) We now deliver the following additional features for this business role: Market development funds Enhanced contact maintenance, including maintenance of marketing attributes Overview of presales activities Display of products and employees responsible at brand owner (Relevant if upgrading from SAP CRM 5.2) Request to brand owner - Partner Manager - Channel Commerce and Partner Employee These two portal roles are no longer available. Their content has been integrated into the Partner Manager business role. All BI reports formerly contained in the portal roles of Partner Manager Channel Commerce and Partner Employee are still available. Lead Processing with SAP Interactive Forms Software by Adobe (Relevant if upgrading from SAP CRM 5.2) You can distribute leads by e-mail to channel partners. See also Partner Channel Management: SAP NetWeaver Portal (New) ______________________________________________________________ SAP AG 320 SAP-System ______________________________________________________________ 1.27.3 Partner Channel Management: SAP NetWeaver Portal (New) Use This release note is only relevant if upgrading from SAP CRM 5.2. The features for partner channel management (PCM) are available on the SAP NetWeaver Portal. In addition, the SAP NetWeaver Portal offers the following extra features for PCM: Facts and reminders (note: you can display presales activities directly in the CRM WebClient) Provides an overview and access to presales activities done in the Portal, such as activities, leads, and opportunities, where the channel partner is the contact person and the partner manager is responsible. Knowledge management and document management Enables access to information, such as marketing collateral or product data, that you have categorized as being relevant for your channel partners. Live support Assists channel partners who cannot find solutions to their problems in the information that you have provided them. Enables channel partners to request support by, for example, e-mail or telephone call back. - - 1.28 CRM-LAM CRM Leasing 1.28.1 Functions No Longer Available in Leasing Use This release note is only relevant if upgrading from SAP CRM 5.0. The user interface has been simplified to improve usability. It now displays only the most frequently used functions. You use the Leasing Manager role to access the new user interface. The following leasing-specific functions were not adapted on the new user interface but can be called from the Leasing Manager role: Simulate Financing Products (transaction: FIMANTEST) ______________________________________________________________ SAP AG 321 SAP-System ______________________________________________________________ - Adjust Interest Rates (transaction: CRM_FS_INTADJ) Evaluate Interest Rate Adjustment Runs (transaction: CRM_FS_INTADJ_DISP) Edit Depreciations (transaction: CRMD_ORDER_LEAS_WOFF) Change Status of Individual Objects (transaction: CRMC_IOBJ_FIN_STATE) The following leasing-specific functions are no longer available on the new user interface: Simulation tool in the lease quotation Fast entry for lease quotations with one financing item only Upgrade in leases Object list (IBase) in the object item for the lease quotation and lease Business agreement Survey: Not available in lease quotation at item level 1.28.2 Mass Change Processes (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. You can execute contract changes involving a large number of contracts in a mass run. To do this, SAP provides a defined interface for calling the mass change and the mass change processing workbench that has the following features: Processing of Mass Changes To start a mass change run, call the interface module CRM_FS_CHANGE_MASS_UI. The system uses the data transferred from the module to construct the mass change user interface. With each mass change run, the system generates a mass processing ID, which you need for the cancellation of change processes. You can schedule the processing of mass changes in the background and also start the process online. Process Control The system logs the changes made to each contract in a message log that you can call via the mass change workbench (transaction: CRMC_FS_MASS_CHANGE). Each contract is assigned a status that indicates whether processing was successful or not. If processing was not successful, the system details the cause of the error in a message. To display the log, you need to enter the mass run ID; this has already been assigned by the system for the change run. In the log display, you can perform reprocessing or cancellation. Reprocessing and Cancellation Reprocessing: You can reprocess contracts that were not processed correctly in a mass change process (after you have eliminated the cause of the error) Cancellation: You can undo change processes that have already been successfully executed - - ______________________________________________________________ SAP AG 322 SAP-System ______________________________________________________________ You can execute mass change processes for the following change processes: Bankruptcy without return (BANC) Bankruptcy with return (BANK) Base lease extension (BLEX) Purchase at end-of-lease (BUYO) Termination without return (CONC) Continuation (CONT) Early buyout (EBUY) Early termination without return (ECON) Early termination with return (ETER) Insolvency (INSO) Change of location (LCOL) Change of ownership (LCOO) Change of other partners (LCOP) Repossession (REPO) Restructuring with display of full payment schedule (RESC) Renewal (RNEW) Stop accounting (STAH, STAI) Reset stop accounting (USAH, USAI) Stop billing (STBH, STBI), reset stop billing (USBH, USBI) Termination with return (TERM) Undo insolvency (UNIN) 1.28.3 Integration of Contractual Services (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. You can integrate service contract items in leases and this means you can offer leasing customers the following services: Vehicle maintenance and repair Tire service (tire replacement and storage) Service card (for fuel, tolls, car wash, and so on) ______________________________________________________________ SAP AG 323 SAP-System ______________________________________________________________ Furthermore, the Unique Item Identifier (UIID) in SAP Leasing provides you with a new identification number that enables the unique identification of contracts across the entire contract cycle. For more information, see the release note Unique Item Identifier (UIID) (New). The following areas of SAP Leasing have been adapted for full service business processes and enhanced with the corresponding functions. Lease: Integration of Contractual Services Services and financing products always refer to an object (for example, a vehicle). You can offer services with or without a financing product. You create services as service contract products in the master data in the CRM system. You can also group services in product bundles that you have defined to match your product range. You can select the service products in a lease quotation or lease. This enables you to create a service contract item in the quotation/lease. A payment schedule is assigned to the service contract item. This schedule is used to bill the customer regularly for the agreed amounts. There are processes available that enable you to offset payments/fees paid by the customer in advance against the actual operational service costs (open billing). Individual Services and Determination of Product Lists You can use individual services to manage service contract items in a lease, from both a business and a technical perspective. To enable you to structure your service offering flexibly and offer your customers individualized contracts, in the master data you can subdivide a service contract product into different sales-relevant attributes. You compile the relevant individual services for a service contract product in a product list in the master data. Depending on your business requirements, you can link the sales-relevant attributes with the individual services. In the master data, these two parameters (attribute and individual service) are assigned to each other. Within your product range you specify the level of detail to which you want to subdivide a service into attributes or individual services. You can offer some of the individual services to the lessee as an option, while others are a fixed part of a product list or service. You can use the condition technique to define specific individual services as default, mandatory or optional parts of a service contract item. When you structure the contract together with a customer, you can add or remove one or more individual services by adding or removing an attribute. All the individual services in the product list are contractually agreed and allowed. Individual services not included in the product list, receive the status Manual Postprocessing in the service confirmation. Price agreements that mirror the degree of coverage are generated for all individual services in the product list: Coverage: 100% Coverage: 0% Example: In the contract, the lessee selects the service Tire Service. This contains the attributes Summer Tires, Winter Tires, and Tire Replacement. These attributes are linked to the individual services Summer Tires, Winter Tires, and Tire Replacement. When the lessee chooses these attributes in the contract, the system automatically selects the corresponding product list in which these individual services are compiled. The service Tire Service also contains the optional attribute Tire Storage. If the customer selects this attribute as well, then the corresponding individual service is also included in the product list. Change Processes for Financing and Service Contract Items You can also execute change processes for service contract items. It is also possible to synchronize ______________________________________________________________ SAP AG 324 SAP-System ______________________________________________________________ service contract items and financing product items in Customizing with regard to date, status, and change processes. The following change processes are provided as default: At header level: Change of ownership (LCOO) At item level: Early termination with return (ETER) Termination with return (TERM) Base lease extension (BLEX) Change of attributes (CHOA) It is only possible to enter sales-relevant attributes on the user interface for the change process without additional effort in the SAP GUI. Change of other partners (LCOP) As well as executing individual change processes, you can make changes in a mass run. You can use the Change Process Engine (CPE) to do this. For more information, see the release note Mass Change Processes (New). - Synchronization of Object Lists When you create a quotation/contract and assign a service contract item to the reference object item, the system copies the reference object (reference product or object) or the object list for the reference object item to the object list for the service contract item. The system performs this synchronization automatically and ensures that the service covers all items contained in the object list. Summarized JIT Call The summarized JIT call function in CRM Service is available with the full service business processes in SAP Leasing. This enables you to use releasable items to control fixed quantities (in the case of tires, for example). Pricing for Service Contract Items The pricing of service contract items is determined by the following criteria: The object/reference product (for example, a vehicle) and the related attributes and conditions. The quantity of objects/reference products. The quantity of selected services and their related attributes. In Customizing you define which of the above criteria affect and control automatic pricing. In doing so, you specify the pricing procedure to be used by the system when determining the sales price of a service from the underlying list price. Using the list price you can include any values in costing as discounts or surcharges. In the following cases the system can determine the relevant sales price as a cumulative value (provided you have entered the corresponding conditions in pricing): The quantity of object items is greater than one: The system calculates a cumulative price that corresponds to this quantity. ______________________________________________________________ SAP AG 325 SAP-System ______________________________________________________________ - The quantity of service contract items and object items is greater than one: The system calculates a cumulative price that corresponds to the product for both quantities. The system displays the list price and the sales price for a service at item level. Service Billing Through Agency Business You can check individual and collective invoices from dealers and service providers (for example, service stations/petroleum companies, workshops) before billing. This enables you to differentiate between those invoice items that are agreed as individual services in the lease and those that are not covered by the lease. If individual services are not contractually agreed, you can reject the invoiced amounts or forward these to the lessee. SAP Leasing supports two scenarios for invoice verification: Planned services The lessee or the service company informs the lessor that it wishes to use a service. The lessor creates a service order. This is used as the reference document for checking the subsequent invoice for the service company. Unplanned services The lessee or the service company does not inform the lessor that they have used a service. In this case, the incoming invoice is checked according to the contractual agreements. SAP Leasing supports the creation and checking of invoices for services as follows: Maintenance and repair You can enter individual invoices manually in the system. This enables you to enter service-specific data. When you save the invoice, the data is sent to the CRM system in which the service contract data is stored. The CRM system checks the invoice data in the form of a service confirmation and returns the result. The system checks whether the invoiced services are covered by the contract and the degree to which these are covered. Tire and rim service You can enter individual invoices manually. You can also automatically transfer collective invoices to the CRM system via an IDoc interface. The CRM system checks (in the form of a service confirmation) whether the quantity specified in the invoice is covered by the contract. Quantities that are not covered in the contract can be invoiced to the lessee. Fuel and service cards You can transfer the invoice data electronically via an IDoc interface. To enable you to check and process the large number of invoice items efficiently, the checks are performed automatically by the system. During these checks, the system checks the validity of the fuel card. If the system cannot define a fuel card as an identification object (for example, the card number is wrong), it assigns the item to a dummy customer. You can then process the item at a later date. If fuel cards or contracts are invalid, the system sets a blocked status. You can use agency business to post both operational services and contract elements to be settled periodically (fees and annuities) in FI-CA (Contract Accounts Receivable and Payable). - - - - - Controlling To analyze the profitability of your contracts and/or your products you can choose between a mass-object and a single-object controlling scenario. The single-object controlling scenario takes place at item level and is represented by internal orders. ______________________________________________________________ SAP AG 326 SAP-System ______________________________________________________________ Business Partner Distribution CRM Middleware is used to distribute the general business partner between the CRM and ERP system. In the case of general business partners, roles are part of the business partner master data; business partners are distributed to each role in the ERP system. The specific roles for the general business partner in the ERP system determine whether a business partner in the ERP system is synchronized with customer or vendor master data. The general business partner is synchronized and assigned with the customer and vendor master data in the ERP system through Customer Vendor Integration (CVI). The distribution between the CRM system and ERP system as well as the synchronization of the general business partner with customer or vendor master data occurs in both directions. Distribution of Identification Objects (Fuel Card, Vehicle License Plate) You can include a fuel card in the object list for a service contract item (for example, fuel card management) in a lease. To do this, you create the card as an object in the CRM system. As soon as the fuel card is included in the lease and this lease is incepted, the card is distributed to the ERP system as an identification object for the business partner. When it checks the invoice, the system checks the existence and validity of the identification object and verifies the invoice item. When you incept the lease, the system also distributes the vehicle license plate of an object for the object item to the ERP system where it can be used for legitimization and invoice verification. Effects on Existing Data The introduction of these functions does not affect existing data. Data is not converted. Note: If you implement the SAP CRM Service function at a later date in an existing leasing scenario, all contracts must contain the service organization. Effects on Data Transfer The introduction of these functions does not affect data transfer. You can transfer leases to the system using standard SAP CRM functions. No system adjustments are required. Effects on Customizing Before you use the SAP CRM Service function, you must make the necessary settings in Customizing for the leasing scenario. This includes setting the service processes, adjusting the organizational data (the service organization is a required entry), and determining the product lists. SAP Implementation Guide: Settings in the CRM System Set service processes Make the standard settings for CRM Service. Adjust organizational data Make the CRM standard settings. Determine product lists SAP Implementation Guide -> Customer Relationship Management -> Financial Services -> Leasing -> Settings for Service Processes -> Determination of Product Lists: Create Field Catalog ______________________________________________________________ SAP AG 327 SAP-System ______________________________________________________________ - Create Condition Tables Create Access Sequences Create Condition Types Define Determination Procedure Assign Determination Procedure SAP Implementation Guide: Settings in the ERP System (Agency Business) SAP Customizing Implementation Guide -> Logistics - General -> Agency Business: Standard settings for agency business Agency Business -> Enhancements for Full Service Leasing: Define Payment Types Assign Identification Objects Define User Status for Document Items 1.28.4 Unique Item Identifier (UIID) (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. You can use a new identification number that enables the unique identification of contracts across the entire contract cycle. When you create a new contract in the CRM system, the system generates an identification number for each contract item and allocates this number to the respective item. Every contract item is then uniquely identifiable. This number remains the same across the entire contract cycle and is replicated with every action in the Lease Accounting Engine (LAE). You use the UIID to assign invoice items and contract items to each other. You create the number range used by the system to generate the UIID in Customizing. You can use the UIID in the LAE explorer as a search parameter for all types of contract items. The system then displays all the contracts that contain an item with the UIID that you used. Effects on Existing Data During migration, the system does not assign a UIID to the existing dataset. You do not need to perform this conversion to ensure the continued operation of the solution in line with the features of CRM 5.0 in the new system. If you want to assign a UIID to existing contracts, you need to use a user-defined conversion program. You can, for example, use a special number range for legacy data that you have already configured in Customizing. Effects on Data Transfer ______________________________________________________________ SAP AG 328 SAP-System ______________________________________________________________ The data transfer processes delivered by SAP have not been adjusted. Provided the number ranges have been configured accordingly, it makes sense to transfer contract numbers from the legacy system to the new system for each customer, for example. However, this data should not be too heavily fragmented. For system administration purposes, as with each number range, it makes sense to monitor the number range volume. Effects on Customizing You must first create one or more number range intervals for the UIID by choosing transaction snro, number range object CRM_UIID. You can assign the number range interval to the combination of transaction type and item category in the IMG activity Transaction-Dependent Settings for Change Processes. 1.28.5 Management of Third-Party Relationships (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. When you create a leasing transaction, in addition to the business partners Lessor, Lessee, and Vendor, you can also integrate other business partners, such as Dealer or Insurer. You can use third-party programs to include in your business processes those third parties that contribute as multipliers in the sale of your financings. Third-party programs support the financing of specific products over a fixed time period. You can create different programs in the system to suit your sales strategy. These programs assist the sale of one or more products and support business partners, or a combination of business partner and product. The third-party program contains the outline agreements for third parties concerning additional payments (for example, subsidies or commission payments). When you create a lease contract, you enter the required business partner, the product to be financed, and the financing product. If you have entered any third-party programs in the system for a specific combination of business partner, product, and financing product, the system displays these programs for selection. If you select one of these programs for contract creation, the system incorporates the default payment conditions for the third party into the contract calculation (pricing). When you create a contract, you can include additional payments to or from third parties in the contract item. When you incept the contract, the system transfers all accounting-relevant data to Lease Accounting in SAP ERP. Lease Accounting forwards the items that are relevant for the third-party account to the Leasing Payment Engine. This engine regularly posts the payables and receivables due to and from third parties to the relevant contract accounts in Contract Accounts Receivable and Payable (FI-CA). Effects on Customizing ______________________________________________________________ SAP AG 329 SAP-System ______________________________________________________________ In SAP CRM you make the settings in Customizing for Customer Relationship Management, by choosing Financial Services -> Leasing -> Settings for Third-Party Business Relationships. 1.28.6 Grouping Leasing Documents und FS Documents (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and you want to use the technology connected with the new item object type BUS2000301. The item object type BUS2000301 is now available to you for SAP Leasing. This item object type combines account origination functions with leasing management functions: based on the same concept, you can link account origination- and leasing tools and use them with each other. The changeover to item object type BUS2000301 offers you: More flexibility in the areas of pricing and financial mathematics Subsequent costing of leases Different bill-to parties and payers for each billing request item A new item object type for billing request items New product data segments, also partly used in the contract The CRM WebClient UI as a new user interface Note that the SAP GUI is not available in connection with item object type BUS2000301. 1.28.7 Functions for Lease Payment Structures (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. Item object type BUS2000301 gives you greater flexibility, especially for pricing and financial mathematics (FIMA). You can use the following functions: Payment structures with annuities Installment repayment structures ______________________________________________________________ SAP AG 330 SAP-System ______________________________________________________________ - Deferral of repayments and interest in payment structures Broken periods with settings for pro-rated calculations Different payment frequencies for interest payments and repayments Weekly payments in the payment schedule Up to three concurrent fees in the payment schedule Working day shift based on financial mathematics Extendable framework for mapping views on financing, such as the processing of subsidies and participations Simplified and enhanced functions for alternative financial mathematics calculations Enhancement concept for the calculation of results key figures Open concept for pricing during change processes This has been done by adding new segments and set types to the following FIMA functions: Payment structure variant: The financing product (product master) can contain any number of payment steps. You define the variant in Customizing. You can then access the variant in the product master for financing products. You assign the variant to a pricing process, which the system then uses to call the correct payment structure variant. FIMA conditions and one-time flows: The system now contains a separate segment that you use to store FIMA conditions and one-time flows. This segment contains the settings for annuities, repayments, fee conditions, and one-time payments. You define the data in the master data for the product, and the system copies the data to the lease quotation. Splitting of interest: If a FIMA condition is linked to a floating rate adjustment, a new segment contains the history of all the interest rates that are to be used. Calculation procedure: The new FIMA Customizing settings focus on the calculation procedure. You use the procedure to define the sequence in which the various financing views and calculation types (such as the calculation of the payment or the interest rate) are calculated. In the master data for products, you can define any number of calculation procedures for each pricing process, and assign them. You can then choose the calculation procedure required from those that you created. You can also use calculation procedures to configure alternative financial mathematics calculations, which you can then choose online in the CRM transaction. Cash flow: This new segment is used with the FIMA conditions and billing request items. This segment can be used in particular when transferring legacy data, which simplifies the data transfer process considerably. FIMA results: The key figures from FIMA results are stored in an extended segment of the business transaction. SAP provides the following fields: First Payment Normal Payment Final Payment Special Payment Internal Interest Calculation ______________________________________________________________ SAP AG 331 SAP-System ______________________________________________________________ - Rate per Thousand Profit Key Figures Financing Views: In Customizing (customer namespace) you can configure the financing views to meet your requirements. In the master data for the financing product, you specify the number of financing views that you want to use. You can activate the views you want either manually or using an Application Programming Interface (API). In Customizing, you have to assign subsidy and participation processes to the financing views. In the master data you assign interest calculation methods and attributes to the financing views. In previous releases you had to define them in Customizing. Effects on Customizing Customizing for Financial Mathematics Settings has been restructured to incorporate the new functions. In Customizing for Customer Relationship Management, make settings for the following IMG activities under Financial Services -> Leasing -> Financial Mathematics Settings: Define Flow Categories Define Pricing Conditions for Cash Flow Values Variants and Additional Flows Settings for FIMA Conditions Financing Views Configure FIMA Calculation Schema Floating Rate Adjustment You execute all the IMG activities under Financial Mathematics Settings. 1.28.8 Change Processes (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. Item object type BUS2000301 combines certain change processes for the leasing scenario in SAP CRM. This reduces the number of business transactions and change processes in the CRM application without restricting the range of functions. The function for certain change processes is covered by change processes that are similar. For example, the ETER process is handled by the TERM process by means of a specific assignment rule. In the Lease Accounting Engine (LAE, SAP ERP), none of the change processes have been changed. A Business Add-In (BAdI) (enhancement spot CRM_FS_ACC_CHANGE_PROC) is used to assign the extended business transactions and change processes from SAP CRM to the processes in the Lease Accounting Engine. The rules used to assign the processes correctly are defined in the BAdI. When a change process is executed, the BAdI is called. In CRM, the BAdI writes the result to data segment CHNGPROC_I, from where it is read by the CRM ______________________________________________________________ SAP AG 332 SAP-System ______________________________________________________________ middleware, and transferred to SAP ERP. You can use your own custom BAdI implementations to change the way in which the LAE processes are assigned. Definition of the Initial Change Process The initial change process used to be defined for the financing item in the financing profile. This setting was made in Customizing for item categories. You now define the initial change process in the product master data. When you create a financing product, you define an initial change process. When you create a financing option, you define which change process is triggered by the option. Using Change Processes During the Period You can now use some change processes during the period. Previously, you could execute these processes at the end of the period only. Changes to and Extension of the User Interface The following fields have been added to the user interface for change processes: Payment Structure Variant: You use variants to use different payment structures ( VTBKOND). You define payment structure variants in Customizing. You then assign them in the product master. Calculation Procedure: You use calculation procedures to define which steps are to be carried out in the financial mathematics calculation. Contract End Date: You can now enter either the term or the new contract end date. However, you cannot enter a value in both fields. In previous releases you could specify the term only. Object list: You can no longer edit the object list. Overview of the Business Transactions The following enhanced business transactions and change processes are available in the CRM system in the application LEAS for the item object type BUS2000301: Business Transaction Change Process BANK: Bankruptcy with return BANK BUYO: Purchase at end-of-lease BUYO CHOP: Change of partner CHOP CONT: Continuation CONT INSO: Insolvency INSO NEWL: New leasing document NEWL RESC: Restructuring with display of full payment schedule RESC RNEW: Renewal RENW ROLF: Insurance rollover financing ROLF STBH: Stop billing STBH STAH: Stop accounting STAH TERM: Termination with return TERM TERM: Termination quotation TERQ UNIN: Undo insolvency UNIN USBH: Reset stop billing (header level) USBH ______________________________________________________________ SAP AG 333 SAP-System ______________________________________________________________ USAH: Reset stop accounting SPLT: Contract split USAH SPLT Overview of the Business Transactions Assigned to Change Processes in the CRM System The following table provides an overview of the assignments between the business transactions and change processes. You can map the processes marked with an asterix (*) from SAP CRM to SAP ERP. These processes no longer exist in SAP CRM because they are covered by the generic processes. You map these processes as follows: Create a change process that is derived from the required process and assign it to the corresponding generic process. You then assign the required ERP process. Example: REPO Process Create the derived change process ZREP (Repossession) and assign it to the business process TERM To assign the ERP process: Assign the ZREP change process in the delivered BAdI assignment to the REPO ERP process Business Transaction in SAP CRM BANK: Bankruptcy with return Assigned Change Processes BANK BANC* BUYO: Purchase of leased object BUYO EBUY INBY* CHOP: Change of partner CHOP LCOL LCOO LCOP SWAC* SWAO* CONT: Continuation CONT INSO: Insolvency INSO NEWL: New leasing document NEWL RESC: Restructuring with display of full payment schedule RESC BLEX EXFC* REST ROFF* RNEW: Renewal RNEW ROLF: Rollover financing ROLF INRL* STBH: Stop billing STBH STBI ______________________________________________________________ SAP AG 334 SAP-System ______________________________________________________________ STAH: Stop accounting SPLT: Contract split TERM: Termination with return UNIN: Undo insolvency USBH: Reset stop billing (header level) USAH: Reset stop accounting STAH STAI SPLT TERM TERQ CONC* ECON* ETER EXFT* INTE* REPO* ROLT* UNIN USBH USBI USTH USTI USAH USAI Effects on Customizing In SAP CRM, the IMG activity Make Settings for Change Processes contains a new Customizing table in which you define item-specific Customizing for items of the category BUS2000301. For more information, see the Implementation Guide (IMG) for Customer Relationship Management -> Financial Services -> Leasing -> Change Processes -> Basic Settings for Change Processes -> Make Settings for Change Processes. See also For more information, see the release note Termination Quotation. 1.28.9 Classification (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. In SAP CRM, you can now assign accounting principles to the sales organization, and define the values for the classification process in product processing and in transaction processing. This is done using the new set type CRM_FS_CLASSIF, which has the attributes External Default, Accounting Principle, and Classification Value. You can define the values in the product master data and in the financing contract. ______________________________________________________________ SAP AG 335 SAP-System ______________________________________________________________ By defining the classification directly in SAP CRM, in many cases you can prevent the system from raising the query Classification in SAP ERP. In previous releases you had to search for the classification in SAP ERP. If you have defined the classification in the product master or when processing the transaction, the system has to prompt the user to specify the classification during pricing outside of ERP, for instance. The prompt for the classification has been created as action FS_CLASSIF_CALL in action profile LEASING_HEADER_QUOTATION. Effects on Customizing Settings in SAP CRM To use the classification in SAP CRM, you have to make the following settings in Customizing for Customer Relationship Management, by choosing Financial Services -> Leasing -> Financing Product -> Classification: Classifications from the ERP System: In CRM you create the classifications that you created in the ERP system. Note that the accounting principles in ERP and CRM must be synchronous. Assign Accounting Principles to Sales Organizations: You assign the accounting principles to sales organizations. Note that the accounting principles in ERP and CRM must be synchronous. Assign Classification to Sales Organization and Accounting Principle: You assign the classification to the sales organization and accounting principles. Define Classifications for Each Business Process: You define for which processes the classification in the document can be changed, and for which processes you want to use the classification from the ERP system. - - Settings in SAP ERP To transfer the classification values from the CRM system to the ERP system, you have to make the settings in Customizing for Financial Accounting (New), by choosing Lease Accounting -> Value Determination -> Settings for Value Transfer -> Adopt Values from Contract Classification. 1.28.10 Management of Billing Request Items (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. You use the new item object type BUS 2000171 to create billing request items (BRIs). You can also use the following additional functions: Assign Different Payment Methods and Payers and/or Bill-To Parties You can use the new functions to bill all types of cash flows (such as down payments, repayments, and interest) separately, using different payment methods and business partners. The system creates a separate billing request item for each cash flow. The system creates the billing request items by using the ______________________________________________________________ SAP AG 336 SAP-System ______________________________________________________________ payment method and business partners that are assigned in the FIMA conditions. Processing of Payment Methods and Business Partners When Creating Billing Request Items In the FIMA conditions, you can assign different business partners (bill-to party and payer) and different payment methods. All the cash flows are assigned to business partners. If you do not assign any payment methods in the FIMA conditions, the old function is used: All billing request items are created with the same payment method. If you do not assign any business partners in the FIMA conditions, the old function is used: The same payer and bill-to party is used for each billing request item. This means that the cash flow cannot be split across multiple business partners. Effects on the User Interface (CRM WebClient UI) The user interface for FIMA condition items contains the following fields: Payment Method Payer Bill-To Party In the detailed view of billing request items, the system displays the payment method under Sales Accounting Data. In the Billing Request Item - Partner assignment block, the system displays all the business partners that are assigned. Creation of Billing Request Items from the Condition Types of Financing Items If the new Customizing contains an entry for the financing item, then a billing request item is created for each condition type in the financing item. The system reads the attributes stored in Customizing to create the billing request item. If the parameters of the lease are changed (for example, the term, or the business partner), the billing request item is also adjusted. If the classification of the financing item changes, you can add a condition type to the financing item, or delete a condition type from it. The system either creates or deletes a billing request item accordingly. Generation of Billing Request Items for Time Horizons Billing request items used to be generated up until the end of the lease. Now they are generated only up to a given key date, which is calculated using a date rule (Customizing). The key date is recalculated periodically for the remaining term. Effects on Customizing Make settings for the following activities in Customizing for Customer Relationship Management: Use of Different Payment Methods and Payers/Bill-To Parties Payment methods: Customer Relationship Management -> Master Data -> Business Partner -> Business Agreement -> Define Parameters for Business Agreement -> Define Payment Methods. Note that you must configure the payment methods in both SAP CRM and SAP ERP at the same time. Item category FS45 (BUSS2000171): Partner schema FINSRV31 has been added to item category FS45 (Customer Relationship Management -> Transactions -> Basic Settings -> Define Item Categories). - ______________________________________________________________ SAP AG 337 SAP-System ______________________________________________________________ Generation of Billing Request Items There are two ways of generating billing request items: You can generate billing request items from the condition type: Customer Relationship Management -> Financial Services -> Leasing -> Billing Request Items: BRI: Define Item Categories That Are Relevant for Generating BRIs Generation of BRIs from Conditions: Define Attributes You can generate billing request items from the cash flow: The system generates a billing request item for each cash flow that is to be billed. This depends on the external cash flow type and the cash flow grouping (Customer Relationship Management -> Financial Services -> Leasing -> Financial Mathematics Settings -> Define Flow Categories -> step: Define External Flow Categories). Note that the item category for billing request items generated from cash flows must be used differently to the item category for billing request items generated from conditions. Time horizon To use the time horizon function, in Customizing for the billing plan type you define a date rule for the time horizon: Customer Relationship Management -> Transactions -> Basic Settings -> Billing Plan -> Define Billing Plan Types. The date rule must contain a baseline date and a timeframe. 1.28.11 Asset Handling and Depreciation (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. Object Management (SAP CRM) and Asset Handling (FI-AA, SAP ERP) contain the following new functions for SAP Leasing. Depreciation Using CRM Objects, and for All Leasing Scenarios As the lessor, you can create a leased object as an object in the CRM application, and depreciate it before a lease has been created for it. The standard Asset Accounting (FI-AA) component is used to post the depreciation. When you create the fixed asset in FI-AA, the system takes the data for the object from the CRM system. To post the depreciation of the asset, you have to enter the following data in SAP CRM: Organizational unit Acquisition and production costs Scrap value (residual value) of the asset Delivery date ______________________________________________________________ SAP AG 338 SAP-System ______________________________________________________________ Depreciation in the Lease When a lease is concluded, the current depreciation of the object can be considered. Depreciation History/Object Life Cycle You can display the life cycle of a given object. On the user interface, you can enter various search parameters (such as the object ID, product, serial number, or delivery date) in a search screen to find objects. The system displays a list of all the objects that match your search parameters. You can double click an object to select it, and display all the depreciation phases assigned to this object. You can display the following information for each object depreciation phase: Lease number Asset number Leasing status (is the object assigned to a lease? (yes/no)) Start date for depreciation End date for depreciation Duration of depreciation Depreciation start value Residual value Start date of the depreciation postings for each accounting principle 1.28.12 Collections Function (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. In SAP Leasing, you can use enhanced functions to track overdue open items. The system also provides easy-to-use functions for processing lease contracts for which payments are overdue. These functions are integrated in SAP CRM and SAP ERP Contract Accounts Receivable and Payable (FI-CA). The open items that clear incoming payments are a central part of Contract Accounts Receivable and Payable. If a customer suspends payment, the open items are not cleared. You can use the new collections function to group open items on specified dates and according to your criteria, and to assign these open items automatically to the worklist of an employee (collector) in an internal or external collection center. The Interaction Center contains a suitable role for the collector that comprises all the necessary functions. The worklist is generated by the system and provides the collector with an overview of the most important data for those customers whose payments are overdue and who the collector must therefore contact. The collector enters the results of all contact with the customer as comments for the entries in the worklist. If payment for the open items is not received despite a reminder from the collector, the system can automatically assign the status Non-Accrual. The system uses this status to execute the Stop ______________________________________________________________ SAP AG 339 SAP-System ______________________________________________________________ Accounting change process for the corresponding financing contract in SAP CRM. The system incepts the contract and triggers in the Lease Accounting Engine the functions for asset accounting and depreciation. If the defaulting customer restarts payment, the system can reset the Non-Accrual status in Contract Accounts Receivable and Payable and restart accounting for the contract in SAP CRM. This means that the system re-executes a change process in SAP CRM, incepts the contract, and transfers the data to the Lease Accounting Engine again. Note that to be able to use the collections function, you must assign a business agreement to each contract item in the financing contract in SAP CRM. Effects on Customizing Settings in SAP ERP You find the settings for the collection function in the Implementation Guide (IMG) for ERP under Financial Accounting (New) -> Contract Accounts Receivable and Payable -> Enhancements for Leasing: Arrears Non-Accrual Status Worklist In Contract Accounts Receivable and Payable, you must activate the following Business Transaction Events (BTEs): 0020: Document/Clearing Completed (No Number) 0350: Dunning: Dunning Activities - Print Dunning Form 1205: Account Balance: Supplement Data 1799: Mass Activity: Event After Very Last Interval For more information, see the IMG for ERP under Financial Accounting (New) -> Contract Accounts Receivable and Payable -> Program Enhancements -> Define Customer-Specific Function Modules. Settings in SAP CRM You find the settings for the collector's role ( IFS_FCC_AG, Leasing Interaction Center Agent) in the IMG for SAP Customer Relationship Management under Business Roles -> Define Business Role. 1.28.13 Calculation of Late Fees (New) Use You can now use the Dunning component in Contract Accounts Receivable and Payable (FI-CA, SAP ERP) to calculate late fees, and the Billing component (SAP CRM) to bill for the fees. For a lease containing several different contract items, you can define different late fees for each item, and configure the late fees matrix to define how the system calculates the fees. ______________________________________________________________ SAP AG 340 SAP-System ______________________________________________________________ How you configure the late fees matrix in FI-CA depends on the type of item (for instance, annuity, or general fee) and the jurisdiction in question. The matrix comprises four possible calculation parameters and two calculation methods. Calculation parameters: Minimum amount: Defined as the threshold: If the fees calculated are below the minimum amount defined, no late fees are charged. Defined as the base amount: If the fees calculated are below the minimum amount defined, the minimum amount is charged as the late fee. Maximum amount: If the fees calculated are above the maximum amount defined, the maximum amount is charged as the late fee. Fixed amount: A fixed amount is charged as the late fee. Percentage of the amount outstanding: A fixed percentage of the amount that is outstanding is charged as the late fee. Calculation methods: One-time late fee: The late fee for an overdue receivable is charged only once, even if the payment has not been made for more than one period. Recurring late fee: The late fee for an overdue receivable is charged for each period in which no payment was made. The system can also include any grace periods that have been agreed in the calculation of late fees. When you configure the function, you also define which of these parameters and calculation methods are used to calculate late fees. Once the system has determined from the key date check that a payment is late, it checks which parameters from the late fees matrix are to be used in this case to calculate the late fees. The late fees are calculated in FI-CA, and appropriate statistical receivables are created. By means of a user exit you can connect a suitable application to calculate tax for late fees. The late fees that were calculated can then be processed as follows: Billing The Billing component is used to bill the fees to the lessee. In FI-CA you can also create an account statement that shows the late fees. Waiver of fees You can reverse fees before you bill them, or after the lessee has received the bill. - Effects on Customizing In SAP ERP you activate Business Transaction Event (BTE) 360. Execute the following IMG activities in Customizing for SAP ERP: Financial Accounting (New) -> Contract Accounts Receivable and Payable -> Enhancements for Leasing Arrears: ______________________________________________________________ SAP AG 341 SAP-System ______________________________________________________________ - Define Delinquency Statuses Define Delinquency Processes Assign Delinquency Statuses to Company Codes Define Tax Jurisdiction-Dependent Parameters for Late Fees Non-Accrual Status: Exclude Main Transactions and Subtransactions As Triggers Define Revocation Criteria for "Non-Accrual" Status Assign Revocation Criteria to Company Codes Worklist: Define Standard Tasks 1.28.14 Changing the Status of Objects (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. You can now use item object type BUS2000301 to start leasing transactions for the financing item. The object that is to be financed (item object type BUS200017) is now assigned to this item object type. This leads to the following change for the internal statuses of leased objects: the status of the leased object changes from Available to On-Lease only after you have activated the lease by choosing Contract Inception. The object assignment (item object type BUS2000170) is unchanged for leasing transactions that you continue to process using item object type BUS2000138 for the financing item. As was previously the case, when you release the certificate of acceptance, the status of the object changes from Available to On-Lease. 1.28.15 Pricing (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. The system can now generate all prices for leasing processing using the pricing function in the Internet Pricing and Configurator (IPC) tool. You can no longer use the contract added pricing implement (CAI). In previous releases, the system could not use IPC to calculate fees, for instance, as the financial mathematics cash flow or information about previous documents was required. This meant that CAI had to be used to calculate the prices for financing. ______________________________________________________________ SAP AG 342 SAP-System ______________________________________________________________ By using item object type BUS2000301, you use condition types to map the calculations that previously had to be done using CAI. These condition types can then be processed by IPC. Examples of prices that were previously mapped using CAI and that are now available as condition types include outstanding payments and discounting rates. Calculation formula 4102 is assigned to the condition types so that IPC can be used to calculate the prices. The calculation procedure for financing also contains the new condition types, which are those that are typical for financing. In financing, certain prices and calculations are interdependent. In previous releases, you mapped these relationships by assigning the item business object. By using item object type BUS2000301, you create the links between the conditions by using search strategies that are based on item relationships. Effects on Customizing To use search strategies to calculate prices, you have to define the strategies in Customizing for Customer Relationship Management, by choosing Financial Services -> Basic Functions -> Cross-Item Functions -> Search Strategies. You make the Customizing settings for pricing for item object type BUS2000301 in Customizing for Customer Relationship Management, by choosing Financial Services -> Basic Functions -> Pricing: Assign ABAP Functions to Condition Types: You make settings for the functions previously executed by CAI. You define conditions, whose values are then calculated by ABAP functions. Note that you have to assign calculation formula 4102 to these condition types in the calculation schema. Define Condition Mapping Using Search Strategies: You assign target condition types and source condition types to each other. - - 1.28.16 One-Time Taxes and Fees (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. You can now use a standard concept for mapping and calculating one-time taxes and fees in financing contracts. One-time taxes and fees comprise one-time payments required for legal or tax purposes, and that cannot be mapped using the financing product or financial mathematics. SAP provides the following categories for one-time taxes and fees: OTAX One-Time Tax Payment OFEE Legal Transaction Fee The classification of the contract governs whether a financing is subject to one-time taxes and fees. For example, in a capital lease, a one-time, up-front tax payment at the start of the lease is the rule. ______________________________________________________________ SAP AG 343 SAP-System ______________________________________________________________ In the business transaction, one-time taxes and fees are stored as conditions in the financing item. To calculate their base amounts, you use the Internet Pricing and Configurator (IPC) tool. For the conditions for the one-time taxes and fees, IPC calls ABAP functions that then calculate the base amounts. If base conditions have been stored, the system generates the relevant billing request item, for which it then calculates the relevant amounts for the one-time taxes and fees. Effects on Customizing You can find the settings for processing one-time taxes and fees in Customizing for Customer Relationship Management, by choosing Financial Services -> Leasing -> Pricing -> Tax Calculation. You can find the settings for defining the pricing process for one-time taxes and fees in Customizing for Customer Relationship Management, by choosing Financial Services -> Basic Functions -> Pricing -> Assign ABAP Functions to Condition Types. You can find the settings for defining the relevant attributes for the generation of billing request items in Customizing for Customer Relationship Management, by choosing Financial Services -> Leasing -> Billing Request Items -> Generation of BRIs from Conditions: Define Attributes. - - 1.28.17 Termination Quotation (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. You can now create a termination quotation that contains all open items (such as outstanding fees and receivables). To do this, you use the business transaction TERM: Termination Quotation and the change process TERQ (Termination Quotation). Termination Quotation for Termination of Contract Items You execute a change process for a given activated lease. The system displays all the items for the lease. You then choose the items in question, including all the quantities specified. You execute the change process TERQ for this item. At the same time, the application in FI-CA uses the following values to calculate the termination total: Overdue receivables Fees Penalty surcharge The application uses the values calculated in FI-CA and the information from the contract to create the termination quotation. The standard calculation methods for operating and capital leases are used. The quotation contains all the receivables, fees, and so on, from FI-CA as open items. You send the termination quotation containing all the data for the termination to your customer. If the customer accepts the quotation and pays the outstanding total, the application compares the amounts. If the amounts match, the contract is posted in FI-CA and the contract items in question are terminated. The termination quotation is set to the status Accepted. If the amount of the incoming payment does not match the ______________________________________________________________ SAP AG 344 SAP-System ______________________________________________________________ amount that cancels the contract, the payment is posted to an interim account until the matter is clarified. If no payment is received by the expiry date of the termination quotation, the quotation can be set to inactive. In this case the contract items are not terminated. Termination Quotation for Termination of a Contract You execute a change process for an active lease at header level to terminate the contract completely (for example, ETER, EBUY, ECON). The system calculates and creates a termination quotation in the same way as described under Termination Quotation for Termination of Contract Items. Creating Mass Termination Quotations You can also create termination quotations in mass processing. You can do so online, or schedule a job in background processing. Effects on Customizing In SAP ERP you activate the relevant Business Transaction Events (BTE). In SAP ERP you execute the IMG activities in Customizing for Financial Accounting (New) -> Contract Accounts Receivable and Payable -> Enhancements for Leasing -> Termination Quotation -> Assign CRM Condition Types to Main Transactions and Subtransactions. In SAP CRM, the IMG activity Make Settings for Change Processes contains a new Customizing table in which you define item-specific Customizing for items of the category BUS2000301. Here you find the new business transaction TERM: Termination Quotation and the change process TERQ (Termination Quotation) for the application LEAS. For more information, see the Implementation Guide (IMG) for Customer Relationship Management -> Financial Services -> Leasing -> Change Processes -> Basic Settings for Change Processes -> Make Settings for Change Processes. - See also For more information, see the release note Change Processes (New). 1.28.18 Modification of the CRM WebClient UI for Leasing Manager (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. In SAP Leasing, you can now map financing items in quotations and contracts by using item object type BUS2000301. You can also use a new technology and architecture. However, to do so you have to enter settings for the CRM WebClient user interface (UI). Effects on Customizing Use of Item Object Type BUS2000301 If you use item object type BUS2000301 to map your financing products for leasing, and therefore use product type 07 Financial Services, do the following: ______________________________________________________________ SAP AG 345 SAP-System ______________________________________________________________ - Deactivate product type 03 Financing, and make sure product type 07 Financial Services is active. For more information, see the Implementation Guide (IMG) for Customer Relationship Management under Cross-Application Components -> SAP Product -> Settings for Product Type. To display only product type 07 Financial Services on the user interface, and to hide product type 03 Financing, you have to modify the user role LEASING (Leasing Manager), which is delivered with the system. You make the settings in Customizing for Customer Relationship Management, by choosing Business Roles -> Define Business Role. Select the LEASING (Leasing Manager) role and choose Visible Work Center Group Links. Deselect the indicators In Menu and Visible for the following logical link IDs: LAM-BTC-CR (Create Financing Contract) LAM-BTC-SR (Find Financing Contract) LAM-BTO-CR (Create Financing Quotation) LAM-BTO-SR (Find Financing Quotation) - Make sure that at least the Visible indicator is set for the following logical link IDs: IFS-FSQ-CR (Create FS Quotation) IFS-FSQ-SR (Find FS Quotation) IFS-FSC-CR (Create FS Contract) IFS-FSC-SR (Find FS Contract) Use of the FS Business Partner If you use Contract Accounts Payable and Receivable (FI-CA) to handle leasing, and use item object type BUS2000301, make sure your business partner data contains the following information: Business agreements Factory calendar This data is stored in the Business Partner for Financial Services (FS Business Partner). If you want the user interfaces to display only the FS Business Partner, you must change the Leasing Manager role delivered by SAP and hide the CRM Business Partner. You make the settings in Customizing for Customer Relationship Management, by choosing Business Roles -> Define Business Role. Select the LEASING (Leasing Manager) role and choose Visible Work Center Group Links. Deselect the indicators In Menu and Visible for the following logical link IDs: LAM-SBC-CR (Create Corporate Business Partner) LAM-SBP-CR (Create Individual Business Partner) LAM-SBP-SR (Find Business Partners) Make sure that at least the Visible indicator is set for the following logical link IDs: LAM-BP-SR (Find FS Business Partners) ______________________________________________________________ SAP AG 346 SAP-System ______________________________________________________________ - LAM-BPP-CR (Create FS Business Partner: Person) LAM-BPO-CR (Create FS Business Partner: Organization) LAM-BPG-CR (Create FS Business Partner: Group) Note the following regarding the distribution of business partner data to back-end systems: You can distribute the data for business agreements to connected back-end system only by means of CRM Middleware. You cannot use SAP NetWeaver Exchange Infrastructure. This means that you have to use CRM Middleware to distribute FS business partner data for leasing if you use item object type BUS2000301. See also For more information, see the following release notes for CRM WebClient User Interface: Functions No Longer Available in Leasing CRM WebClient User Interface (Enhanced) Central Search (New) UI Configuration Tool (Enhanced) Personalization (Enhanced) Portal Integration (New) 1.28.19 Selection for Floating Rate Adjustment (Changed) Use This release note is relevant only if: You have implemented SAP CRM 2007 You are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301 As of SAP CRM 2007 SP02, you can use the new index table CRMD_FS_FRA when you execute a floating rate adjustment to select the documents that are relevant for adjustment. You can add customer-specific fields to this table. Previously, the system had to read several database tables to select the documents relevant for adjustment. Now all the relevant documents are contained in the new index table. This increases the speed and flexibility of the selection process. On the Execute Floating Rate Adjustment selection screen (transaction CRM_FS_FRA), a logical database, which links to the index table, provides both freely definable standard fields (such as Object ID, Reference Interest Profile) and freely definable customer-specific fields (such as Status). If you want to use customer-specific selection criteria, you have to implement these using the customer-specific fields of the index table CRMD_FS_FRA and the Business Add-In Fill Customer-Specific Fields in Index Table (BADI_CRM_FS_FRA_INDEX). The selection function does not entail any additional development work. ______________________________________________________________ SAP AG 347 SAP-System ______________________________________________________________ Effects on Customizing If you want to use customer-specific fields in the index table CRMD_FS_FRA, you have to use the Business Add-In Fill Customer-Specific Fields in Index Table: Customer Relationship Management -> Financial Services -> Leasing -> Financial Mathematics Settings -> Floating Rate Adjustment -> Business Add-Ins (BAdIs) -> Fill Customer-Specific Fields in Index Table. 1.28.20 Partial Processing of Leases (New) Use This release note is relevant only if: You have implemented SAP CRM 2007 You are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301 As of CRM 2007 SP02, you can open and edit leases in partial processing mode. The partial processing of leasing documents is useful if leases contain multiple items (such as 10 and more) with substantial transaction histories. In partial processing mode you can select and edit individual items and the application does not have to open the entire document with all the items contained therein plus the transaction history. This improves system performance because the system has to store temporarily in the buffer only the data actually required. In Customizing you first specify whether partial processing is permitted for the business transaction FS Contract. You then enter a limit in Customizing that stipulates how many main items must be contained in a lease before you can open this document in partial processing mode. If you have permitted partial processing and the number of active main items in a document exceed the limit, you proceed as follows: Select the required lease. Before it processes the document, the system opens a dialog box. This contains all the active main items and you can select individual items. The following display variants are available: All active items without transaction history All active items with transaction history Individual items without transaction history Individual items with transaction history ______________________________________________________________ SAP AG 348 SAP-System ______________________________________________________________ The system then opens the document only with the previously selected items, in other words in partial processing mode. You cannot view and edit all the document items in partial processing mode. It also restricts the actions and change processes that you can execute at document header level. For example, in partial processing mode you cannot execute the actions Contract Inception and Cancellation, as well as end-of-lease processes and change processes. However, you can execute change processes at item level. You can also use the function Mass Processing of Change Processes in partial processing mode. Effects on Customizing If you want to use partial processing for leasing documents, you have to make the following settings in Customizing: Allow Partial Processing for Transaction Type under Customer Relationship Management -> Transactions ->Define Transaction Types Customer Relationship Management -> Financial Services -> Leasing -> Partial Processing of Leasing Documents ->Define Limit for Partial Processing of Leasing Documents 1.28.21 Floating Rate Adjustment (New) Use This release note is only relevant if you are upgrading from SAP CRM 5.0 and want to use the associated technology with the new item object type BUS2000301. With the conversion to item object type BUS2000301, you can adjust nominal interest rates more flexibly to the changes made to the reference interest rate. You can change the reference interest rate on any date in a settlement period, and therefore several times in a settlement period. The nominal interest rate is adjusted on the date on which the reference interest rate is changed. The various nominal interest rates that can occur in a settlement period as a result are settled to the day. You can adjust documents ad hoc (to any date) or periodically. You do not have to individually process the contracts that need to be adjusted; instead you can execute mass document processing. In addition to these functions, you can adjust the nominal interest rate periodically. You can use the reference interest profile to make specific settings for the adjustment type, and so on. The error log is improved as a result of the connection of the Postprocessing Office. You can continue to use the analysis report to analyze successfully adjusted documents. Effects on Customizing Make the following settings in Customizing for Customer Relationship Management, by choosing Financial Services -> Leasing -> Financial Mathematics Settings -> Floating Rate Adjustment -> Edit Reference Interest Rate: Define Reference Interest Rates ______________________________________________________________ SAP AG 349 SAP-System ______________________________________________________________ - Enter Reference Interest Rates Define Reference Interest Profile In the financing product you define the reference interest profile to which the adjustment is linked. In the set of financing views you assign the reference interest profile to the base financing view. The system checks these conditions before adjustment. It selects only documents with this reference interest profile. You can use the Business Add-Ins (BAdIs) to influence the adjustment of floating rates for a specific customer. See also For more information, see SAP Note 1079199. 1.28.22 New Functions for SAP Leasing (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. As of CRM 2007, SAP Leasing provides the item object type BUS2000301 containing a new contract category with enhanced features. Note: There is no function for upgrading the data of the old item object type (BUS2000138) to the technology used by the new item object type (BUS2000301). Furthermore, you cannot use documents based on the old technology in processes that use the new technology. Note that at header level in a document you must not combine any items based on the old technology with items that use the new technology. If you use item object type BUS2000301, you have to use Contract Accounts Receivable and Payable (FI-CA). For more information about the new functions, see Integration of Contractual Services (New) Grouping Leasing Documents and FS Documents (New) Modification of the CRM WebClient UI forLeasing Manager (New) Functions for Lease Payment Structures (New) Management of Billing Request Items (New) Change Processes (New) Termination Quotation (New) Changing the Status of Objects (New) One-Time Taxes and Fees (New) ______________________________________________________________ SAP AG 350 SAP-System ______________________________________________________________ - Pricing (New) Classification (New) Management of Third-Party Relationships (New) Asset Handling and Depreciation (New) Collections Function (New) Calculation of Late Fees (New) Effects on Existing Data Existing data is not affected. Effects on Data Transfer You have to reconfigure the process for transferring legacy data. System administration is not affected. Effects on Customizing Since the change is a major one, you have to check all IMG activities described in Solution Manager for the Lease Operations scenario and, if appropriate, change the existing settings or enter new settings for the new functions. See also For more information, see the following release notes for CRM WebClient User Interface: Functions No Longer Available in Leasing WebClient User Interface (Enhanced) Central Search (New) UI Configuration Tool (Enhanced) Personalization (Enhanced) Portal Integration (New) 1.29 CRM-IFS Financial Services 1.29.1 Installment Loans (Changed) Use This release note is only relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can now create installment loans in the Account Origination scenario. For this purpose, we have added to the XI interfaces LoanCalculationQuery and LoanContractCreateRequest some attributes ______________________________________________________________ SAP AG 351 SAP-System ______________________________________________________________ that are required by the system to calculate or create an installment loan. These include One-Time Balloon Amount or Interest Calculation Method. The Interest Calculation Method field is available in the FS product. It is copied to the interface for loans management. The following fields are available on the interface for loan origination: Field for an increased balloon amount Two fields for entering the maximum change in interest rates in the case of variable interest calculation Note that these XI interfaces use the latest versions of the global data types (SAPGLOBAL20). When you connect a loans system that is based on the older interface versions, you have to use the interface mapping defined in XI. Effects on Customizing You have to make the following settings for the installment loans product in Customizing for Customer Relationship Management: CRM Standard Customizing Define action profiles and actions Define conditions Define item category groups Define item categories Define item category determination Copying control for item categories Prices and conditions Customizing for Financial Services Customer Relationship Management -> Financial Services -> Basic Functions: Cross-Item Functions: Execute all the IMG activities under this node Connection of External Systems: Execute all the IMG activities under this node Customer Relationship Management -> Financial Services -> Account Origination -> Financial Service Product (FS Product): Define Flow Categories Edit Reference Interest Rate ______________________________________________________________ SAP AG 352 SAP-System ______________________________________________________________ 1.30 CRM-IPS Public Sector 1.30.1 Case Management for Grantor (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0 Case Management for Grantor has been enhanced to allow you to link claim objects and change request (agreement) objects to a case. Automatically linking a grantor claim and related 'Account' documents to a case. Once a claim has been saved and submitted, PPF is configured in such a way that the claim is then automatically added to a case, if it is not already linked. It also looks to see if an account document has been created in PSCD and if so, this is also added to the case. In addition, the FI-CA billing document is linked, containing data from ERP. The relevant case is determined automatically by the system, which searches for all cases that have a specific grantor agreement (The grantor agreement is assigned to the grantor claim) already linked to that case. If only one case is found, the unique case GUID is used to link the grantor claim. If there are no results, then it is assumed that the agreement has not been linked to a case and that therefore also the grantor claim should not be linked to a case. If more than one case is linked to an agreement, only the first case on the list is processed and the claim is linked to this case. Once the object is linked, the following information is displayed on the Linked Objects tab page. Grantor Claim Currency Transaction ID Description Status Due Date Approved Amount Automatically linking a grantor change request and related 'Account' documents to a case Once a change request with reference to an agreement has been saved and submitted, PPF is configured in such a way that the claim is then automatically added to a case, if it is not already linked. It also looks to see if an account document has been created in PSCD and if so, this is also added to the case. In addition, the FI-CA billing document is linked, containing data from ERP. The relevant case is determined automatically by the system, which searches for all cases that have a specific grantor agreement already linked to that case. If only one case is found, the unique case GUID is used to link the grantor change request. If more than one case is linked to an agreement, only the first case on the list is processed and the change request is linked to this case. Once the object is linked, the following information is displayed on the Linked Objects tab page. Object Attribute 5 Attribute 1 Attribute 2 Attribute 3 Attribute 4 ______________________________________________________________ SAP AG 353 SAP-System ______________________________________________________________ Grantor Change Request Transaction No. Valid To Requested Amount Description Valid From 1.30.2 Business Rule Framework in CRM (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. As of Release SAP CRM 5.1, the following additional functions are provided for the Business Rule Framework (BRF) supported in Customer Relationship Management: Generation of tags for business partner-, product-, and customer fields The program CRM_BRF_TAG_CUST_GENERATE supports user-friendly tag generation for standard fields of the business partner and product, as well as for customer fields of your enhancements to the business partner and product. Multi-instance logic: Event filtering of tag expressions using formula editor As standard, you can filter the results of a tag with multi-instance logic using criteria. Alternatively, you can now also use the formula editor for filtering the results of certain tag expressions. The formula editor enables you to define considerably more complex conditions for event filtering, for example, if you wish to process time-dependent data records with the formula editor's time-dependent functions. Search expressions The BRF now supports the definition of search expressions for the search objects case, transaction, and transaction item. The search result can be restricted using search attributes. The fields from customer enhancements in Case Management and those of the CRM transaction can be incorporated as search attributes. You can enhance search expressions using the Business Add-In CRM_BRF_SEARCH. - - Effects on Customizing You generate customer field tags in the IMG activity Generate Tags for Business Partner-, Product- and Customer Fields. ______________________________________________________________ SAP AG 354 SAP-System ______________________________________________________________ You enhance search expressions using the BAdI CRM_BRF_SEARCH (see IMG activity Enhancement of Search in Search Expression). 1.30.3 Business Rule Framework in CRM (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can now activate a check for tags that provide no result for CRM-based BRF rules. This means that rules whose tag expressions do not provide a result can still be executed and the system can react by taking appropriate action. Without this check, rules are not executed when the related tag does not produce a result. You activate this check logic in two steps: 1. 2. In the respective BRF rule, set the Check no Tag Result indicator. For the respective tag, select ' 1 Existence Check' in the Purpose field. 1.30.4 Event-Driven CRM Activities (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Event-driven CRM activities are supported in the Social Services component. This enables you to support automated notifications or tasks in the Social Services environment when a particular event occurs in the course of processing. The CRM activity call is BRF -based. You can define the necessary events and the BRF expressions to be processed in the BRF. The CRM activities are created using the function module CRM_PS_ACTIVITY_CREATE. ______________________________________________________________ SAP AG 355 SAP-System ______________________________________________________________ See also For more information, see the specified function module and the topic entitled Event-Driven CRM Activities in the SAP Library. 1.30.5 BRF Action Types for Social Services (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The following BRF action types are provided in the Social Services component for defining actions in the Business Rule Framework: BRF Action Type 0EVT_A001 0EVT_A002 0EVT_A003 business partner 0EVT_A004 Use Generate Social Services Eventing events Create CRM case notes Data changes in customer enhancements (EEW) to Create CRM activities For the definition of your own BRF action types, the following maintenance classes and runtime classes are provided for theitem proposal, the eligibility check, and for change processes: Item proposal Runtime class Maintenance class CL_CRM_PS_IPS_BRF CL_CRM_PS_IPS_MNT_BRF Eligibility check Runtime class Maintenance class Change processes Runtime class Maintenance class CL_CRM_PS_ECC_MSG_BRF CL_CRM_PS_ECC_MSG_MNT_BRF CL_CRM_BRF_CONIN_AC CL_CRM_BRF_CONIN_AC_MNT2 See also Release Notes for SAP CRM 5.10: Business Rule Framework in CRM (Enhanced) ______________________________________________________________ SAP AG 356 SAP-System ______________________________________________________________ - Business Rule Framework for Social Services in the SAP Library 1.30.6 Case Assignment for Social Applications and Social Service Plans (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The organization of your business transactions in cases of Case Management is supported in the Social Services component. In Customizing, you can define case determination strategies and case creation strategies based on a case assignment profile. The system then uses these strategies to automatically organize new social applications or social service plans in cases. Either the assignment is made to matching existing cases, or the system creates new cases of the relevant case type. In connection with the case assignment, you can use the business partner function mapping to map partner functions in the business transaction to the partner functions in the case. Customizing also enables you to flexibly tailor this function to satisfy your requirements. Customer-definable BAdI implementations enable you to make customer-specific enhancements to the SAP standard settings for case assignment. Effects on Customizing You make the case assignment settings for the social application and the social service plan respectively in Customizing for CRM by choosing: Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Social Services -> Social Application or Social Service Plan -> See also For more information, see the relevant IMG documentation and the topic entitled Assign Social Applications and Social Service Plans to Cases in the SAP Library. Define Settings for Case Assignment Define Case Assignment Profile 1.30.7 Change Processes in Social Service Plans (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Social service plans can be updated by means of change processes in the Social Services component. ______________________________________________________________ SAP AG 357 SAP-System ______________________________________________________________ Change processes ensure the predefined, integrated processing of an existing social service plan whenever a change in the requester's circumstances (for example, change in salary, new key date) necessitates the recalculation of benefits. Change processes can be started automatically as part of successor processing, or can be started manually by the caseworker in the Social Service Plan application. Effects on Customizing You define change processes (or you can use the standard SAP change processes) in Customizing for CRM by choosing Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Social Services -> Social Services Plan -> Change Processes. (See, among others, IMG activity Make Settings for Change Processes). See also For more information, see the IMG and the topic Change Processes in Social Service Plans in the SAP Library. 1.30.8 Item Proposal for Social Applications (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use an item proposal strategy for social applications in the Social Services component. In this kind of strategy you stipulate according to which criteria a social application-specific automatic selection of benefits applied for in the request form are transferred associal application items. You define item proposal strategies as Business Rule Framework events or as Business Add-In implementations. You assign a strategy to the relevant transaction type of your social application using an item proposal profile. Effects on Customizing You define item proposal strategies and profiles in Customizing for CRM by choosing Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Social Services -> Social Application -> Item Proposal -> See also Define Item Proposal Profile BAdI: Define Item Proposal Strategy ______________________________________________________________ SAP AG 358 SAP-System ______________________________________________________________ For more information about using this function, see Item Proposal for Social Applications in the SAP Library. 1.30.9 Business Object Social Application (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The new business object Social Application is provided in the Social Services component. It enables you to process the business transactions of submitted social applications in Customer Relationship Management. The following functions are supported for the social application: Social Applications application You process social applications in the Social Applications application. This application is part of the user role CASEWORKER provided for Social Services. Case assignment and categorization To ensure that Social Services business transactions are managed comprehensively and efficiently, social applications can be organized in existing or new cases of Case Management in the system (see Release Note Case Assignment for Social Applications and Social Service Plans). Transfer of request form data The Business Add-In CRM_PS_APPLICATION_BADI enables you to transfer the application data, which has been submitted or created, to non-SAP systems. Item proposal The item proposal supports the social application-specific automatic transfer of benefit parts requested in the request form as social application items (see Release Note Item Proposal for Social Applications). Eligibility check The system evaluates requested benefits with regard to the submitted requester data. As a result of this evaluation, social application items are given the status 'Eligible' or 'Not Eligible'. The evaluation is based on rules you define in the Business Rule Framework (see IMG activity Define Eligibility Check Profile). Item assessment Item assessment accommodates an additional check instance in the form of a manual or automatic assessment of social application items. As a result of this assessment, items are given the status 'Accepted (SOA)' or 'Rejected (SOA)' (see IMG activity Create Item Assessment Strategy). Approval check You define the criteria of the approval check for the respective social applications in an approval strategy (see IMG activity Create Approval Strategy). Manual approval is carried out in the Social Application application. Depending on a caseworker's authorization level, he or she can approve an application directly, or forward it to his or her superior for approval. Automatic approval is also possible for Web request-based social applications. Successor processing - - - - - - - ______________________________________________________________ SAP AG 359 SAP-System ______________________________________________________________ Successor processing supports the creation or the update of a social service plan after the related social application has been approved or changes to the social application data make an update necessary (see Release Note Successor Processing of Public Sector Business Transactions). Effects on Customizing You define the settings for your social applications in Customizing for CRM by choosing Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Social Services -> Social Application . See also For more information, see the documentation on the business object Social Application in the SAP Library. 1.30.10 Business Intelligence Analysis of Social Services Data (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. An interface for Business Intelligence (BI) is supported in the Social Services component. This makes it possible to retrieve the data for social applications and social service plans from CRM in SAP BI. The related BI content has to be configured in parallel in the customer's Business Intelligence system. For the analysis of Social Services transaction data, the CRM system provides the following DataSources for transferring header and item transaction data: DataSource 0CRM_PS_SOA_H 0CRM_PS_SOA_I 0CRM_PS_SSP_H 0CRM_PS_SSP_I Use Social Application Header Data Social Application Item Data Social Service Plan Header Data Social Service Plan Item Data The Social Services-specific system statuses with the BW object status group SOC are provided for mapping BW status objects. For more information, see Customizing for CRM under SAP Implementation Guide -> Integration with Other mySAP Components -> Data Transfer to the SAP Business Information Warehouse -> Settings for Application-Specific Datasources (PI-Basis) -> Status Concept for BP / Product / CRM Objects -> Display System Status. Effects on Customizing ______________________________________________________________ SAP AG 360 SAP-System ______________________________________________________________ For the transfer of Social Services data to SAP BI, you need to activate the DataSources in the source system (CRM): 1. In Customizing for CRM, choose SAP Implementation Guide -> Integration with Other mySAP Components -> Data Transfer to the SAP Business Information Warehouse -> Business Content Datasources -> Transfer Business Content Datasources. Activate the four Social Services DataSources mentioned above by choosing BW DataSources -> Root -> 0CRM -> 0CRM_SERVICE. 2. 1.30.11 User Role Social Services (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The user role CASEWORKER is provided for the productive use of the Social Services component in the CRM WebClient UI. You can use the role SAP_CRM_UIU_CASEWORKER as a copy template for defining the required authorization profiles in Social Services in the transaction PFCG. 1.30.12 Social Services Eventing (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. You can use Social Services Eventing (SSE) in the Social Services component. SSE supports the asynchronous execution of SSE subscriptions (parameterized BRF rules). The subscriptions can be incorporated at any exit (BAdI exit, PPF action, and so on) of the respective application components. This makes it possible to define the triggering of automated actions in the Social Services environment whenever a particular event occurs. Such actions include the creation of automatic case notes, the notification of caseworkers, and the changing of business partner data. Social Services Eventing is based on the Business Rule Framework, which it enhances with its specific functions. The control parameters of SSE events are set in a separate Customizing activity independently of the BRF settings. ______________________________________________________________ SAP AG 361 SAP-System ______________________________________________________________ Effects on Customizing You make the relevant settings in Customizing for CRM by choosing Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Social Services -> Common Functions ->Social Services Eventing. See also For more information, see Social Services Eventing in the SAP Library. 1.30.13 Business Object Social Service Plan (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The new business object social service plan (SSP) is provided in the Social Services component. In a social service plan, you map the contractual agreement for benefits for an approved social application in Customer Relationship Management. The following functions are supported for the social service plan: Social Service Plan application You process social service plans in the Social Service Plans application. This application is part of the user role CASEWORKER delivered for Social Services. Change processes Definable change processes enable you to support standardized changes to social service plans (in cases of changed scheduling, for example). Change processes are automatically started within successor processing, or can be manually selected in the Social Service Plan application (see IMG activity Make Settings for Change Processes). Case assignment and categorization To ensure that Social Services business transactions are managed comprehensively and efficiently, social service plans can be organized in existing or new cases of Case Management in the system (see Release Note Case Assignment for Social Applications and Social Service Plans). Eligibility check The system evaluates requested benefits with regard to the submitted requester data. As a result of this evaluation, social service plan items are given the status 'Eligible' or 'Not Eligible'. The evaluation is based on rules you define in the Business Rule Framework (see IMG activity Define Eligibility Check Profile). Item assessment Item assessment accommodates an additional check instance in the form of a manual or automatic assessment of social service plan items. As a result of this assessment, items are given the status 'Released (SSP)' or 'Rejected (SSP)' (see IMG activity Create Item Assessment Strategy). Approval check You define the criteria of the approval check for the respective social service plans in an approval strategy (see IMG activity Create Approval Strategy). Manual approval is carried out in the Social - - - - - ______________________________________________________________ SAP AG 362 SAP-System ______________________________________________________________ Service Plan application. Depending on a caseworker's authorization level, he or she can approve an SSP directly, or forward it to his or her superior for approval. Alternatively, you can stipulate the automatic approval of an SSP in successor processing. Activation of a social service plan The activation of a social service plan and the respective items identifies the currently valid and complete SSP version (see IMG activity Configure SSP Activation). Effects on Customizing You define the settings for your social service plans in Customizing for CRM by choosing Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Social Services -> Social Service Plan . See also For more information, see the documentation for the business object Social Service Plan in the SAP Library. 1.30.14 Successor Processing of Public Sector Business Transactions (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Successor processing (SUPR) is supported in the Social Services component. Successor processing is executed as a PPF action before the predecessor document is saved. On the basis of a Web request-basedsocial application (predecessor document), the following functions are supported within successor processing: Create a new social service plan (successor document) based on an approved social application. Change or update of an existing social service plan (SSP) based on changed request data. The update can be performed in new SSP versions. You can stipulate in a change processing profile which change processes are to be applied to the SSP version. Copy document items of a social application to a social service plan by means ofitem copy strategies. You can supplement the item copy strategies provided by SAP with your own (customer-defined) strategies. - In addition to the successor processing functions, a >social service plan determination strategy supports the search for existing social service plans that match new or changed social applications. If a matching social service plan is found, the SSP assignment profile creates the document chain linking these two documents. The determination strategy is started directly before successor processing. Depending on the result, successor processing is then executed in create mode or in change mode. ______________________________________________________________ SAP AG 363 SAP-System ______________________________________________________________ Effects on Customizing You define the successor processing settings in a successor processing profile, and assign this profile to the relevant business transaction types. You make the settings in Customizing for CRM under Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Social Services -> Successor Processing. See also For more information about successor processing in Social Services, see Successor Processing in the SAP Library. 1.30.15 Financial Customer Care and Dispute Management (Enhanced) Use This release note is only relevant if you are upgrading your system from SAP CRM 5.0. The business scenario includes the following new or enhanced processes: New with SAP CRM 5.2 or SAP CRM 2007: Note: All the functions listed here require SAP FI-CA based on SAP ERP 6.0 Enhancement Package 2 at the lowest as the back-end system. However, SAP ERP 6.0 ist still supported as the back-end system. For further information on release dependency, see SAP notes 1075410 and 746475. Payments in the Interaction Center for Financial Customer Care Maintain payment methods If you use SAP ERP 6.0 Enhancement Package 2, the payment methods are no longer defined in the FI-CA profile for the user role but in SAP FI-CA. You can define the payment methods for each country for the following payment types: Payment Installment plan Promise to pay Payment specification or payment request Payment requests Grouping of items for which payment orders are to be made to form one payment request in the ERP system Payment specification Grouping of items in a payment specification in the ERP system - Installment Plan ______________________________________________________________ SAP AG 364 SAP-System ______________________________________________________________ You can define payment data for installment items. Payment Search As of SAP ERP 6.0 Enhancement Package 2, you can restrict a payment search to a certain number of payments. You can also limit the maximum number of payments on which the search is to be run. This allows you to avoid long waits when executing the search. You can define standard values for this function in Customizing for the FI-CA profile. The agent can adjust these parameters on the interface for the payment search. Account Balance Display new flexible FI-CA balances Display configurable additional data Enhanced support for contract data in the account balance Display processing locks for contracts Dunning history Display collection strategy and collection step Payment Data You can define bank details for a specific period in a business partner's payment data. Miscellaneous Display enhanced user data You can display details on a user for the user IDs (for example Created By) in the user interface in the Interaction Center for Financial Customer Care even if the user is not known in the CRM system. You can define which data is to be displayed in FI-CA event 2836. Fact sheets Display FI-CA data in an account or business agreement overview Alerts Convert FCC alerts to the new CRM Alert Framework User interface Convert FCC interfaces to the new CRM WebClient user interface For further information on converting the user interface, see the release note Uniform User Interface in CRM (New). - Financial Customer Care As Frontend for FI-CA Collections Management Display and edit worklists and work items Display, create, and change promises to pay Display collection fact sheet, display collection-relevant data Display a customer's collection history and details of the objects it contains For further information on Collections Management in SAP FI-CA, see the SAP ERP 6.0 Enhancement Package 2 release note Collections Management in the ERP system. Financial Customer Care Integration with Adjustment Request and Dispute Management ______________________________________________________________ SAP AG 365 SAP-System ______________________________________________________________ You can integrate Dispute Management with Financial Customer Care. For further information on Dispute Management in SAP CRM 2007, see the release note New Functions in the Provider Contract and Dispute Management. Credit Management Integration You can integrate the Financial Customer Care Interaction Center with various credit management systems. The following functions are available in each case: SAP Credit Management (FIN-FSCM-CR) in SAP ERP Central Component (SAP ECC); the two systems are connected using SAP NetWeaver - Exchange Infrastructure (XI) Credit Management (FI-AR-CR, SD-BF-CM) in SAP ECC External credit management system connected using XI External credit management system not connected using XI If you use SAP Credit Management (FIN-FSCM-CR) or another external credit management system that is connected using XI, the following functions are available: Display and use a business partner's credit risk rating Automatic credit check and commitment notification Process transactions with credit locks If you use Credit Management (FI-AR-CR, SD-BF-CM) in SAP ECC, the following checks are available: Business partner valuation and credit rating check in SAP CRM Automatic credit check and commitment notification Process transactions with credit locks If you use an external credit management system that is not connected to SAP CRM using XI, the automatic credit limit check and commitment notification functions are available. For further information on Credit Management integration, see the SAP Library documentation on SAP CRM 2007 on the SAP Help Portal at http://help.sap.com -> Documentation -> SAP Business Suite -> SAP Customer Relationship Mgmt. -> SAP CRM 2007 -> Components and Functions -> Basic Functions -> Credit Management. Effects on Customizing For further information on Customizing and on how to configure this business scenario, see SAP Solution Manager. See also For further information on the functions in the individual business processes in the business scenario Financial Customer Care & Dispute Management, see the SAP Library documentation on SAP CRM 2007 on the SAP Help-Portal at http://help.sap.com -> Documentation -> SAP Business Suite -> SAP ______________________________________________________________ SAP AG 366 SAP-System ______________________________________________________________ Customer Relationship Mgmt. -> SAP CRM 2007 -> Components and Functions -> SAP CRM for Industries -> Telecommunications Industry -> Functions in the Interaction Center for Financial Customer Care. 1.30.16 Financial Customer Care for Insurance (Enhanced) Use This release note is only relevant if you are upgrading from CRM 5.0. Refer also to the release note for Financial Customer Care, which also applies to this industry variant. As of SAP CRM 2007, the business scenario contains the following process: Account Identification If you are implementing SAP ERP 6.0 with Enhancement Package 3 in the back-end system, you can call the transaction for editing the insurance object after the insurance object has been confirmed. Effects on Customizing For more information about Customizing and configuration of this business scenario, refer to SAP Solution Manager. 1.30.17 Financial Customer Care for Public Sector (Enhanced) Use This release information is only relevant if you want to perform an SAP CRM 5.0 upgrade. Note: All functions listed here need back-end system SAP ECC Industry Extension Public Sector Collection and Disbursement (PSCD) at least on basis SAP ERP 6.0, Enhancement Package 3. However, SAP ERP 6.0 is still supported as back-end system. Read release note for Financial Customer Care that is also valid for the industry variant Public Sector. As of SAP CRM 2007 the business scenario contains the following enhanced processes. Request Processing in the Interaction Center for Public Sector If you are using SAP ERP 6.0 with Enhancement Package 3 in the back-end system, you can also display the assigned facts for a contract object. The same processing options are available as in the back-end system. For more information, see the SAP Library in the SAP Help Portal under the Internet address ______________________________________________________________ SAP AG 367 SAP-System ______________________________________________________________ http://help.sap.com -> SAP Solutions -> SAP ERP -> SAP ERP Central Component -> SAP enhancement package 3 for SAP ERP 6.0 -> SAP Public Sector Collection and Disbursement (PSCD) -> Basic Functions -> Facts. Inbound Correspondence Processing If you are using SAP ERP 6.0 with Enhancement Package 3 in the back-end system, you can use the enhanced functions for inbound correspondence. For example, you can define rules for generating inbound correspondence and alternative periods when processing a contract object. For more information, see the SAP Library in the SAP Help Portal under the Internet address http://help.sap.com -> SAP Solutions -> SAP ERP -> SAP ERP Central Component -> SAP enhancement package 3 for SAP ERP 6.0 -> SAP Public Sector Collection and Disbursement (PSCD) -> Business Transactions -> Inbound Correspondence. Moreover, you can also process the enhanced inbound correspondence in the correspondence history. Effects on Customizing For more information on Customizing and the configuration of this Business Scenario, see SAP Solution Manager. See also For more information on the functions of the individual business processes for Business Scenario Financial Customer Care for Public Sector, see SAP Help Portal under Internet address http://help.sap.com -> SAP Business Suite -> SAP Customer Relationship Mgmt. -> SAP CRM 2007 -> Components and functions -> SAP CRM for Industries -> Public Sector -> Functions in Interaction Center for Financial Customer Care. 1.30.18 Grantor Claims Use This release note is relevant if upgrading from SAP CRM 5.0. You can now manage claims submitted by a grantee for services to be rendered or already performed. A grantor claim is a request from the grantee for payment or reconciliation of payment based on accounting for incurred expenses, or for meeting other terms or conditions of an agreement. Grantor Claims Management includes a web-based claim form (web request) linked to a new grantor object, the grantor claim. After a claim is submitted, it is assigned to a relevant, valid agreement, and then individual claim items are assigned to agreement line items. Claim items can then be checked manually for eligibility, for example, if the claim has been submitted during the proper submission period. You can also use availability checking against the agreement and any cleared advances. This determines if sufficient funds are available to pay the claim providing it meets specific criteria. If these checks are successful, the ______________________________________________________________ SAP AG 368 SAP-System ______________________________________________________________ claims are then approved, released and paid. The claims management process performs the following: Programs can include more than one type of claim, such as an advance, an expense and a holdback Claims can be a combination of more than one type, such as, expenses and milestone payments and advances Claim evaluation may include manual and/or automated processing The following payment types are available to the grantor or grantee to process a claim: Advance: A payment made in advance of actual work or costs incurred Payment: Funds granted to a grantee for costs incurred. If a grantee submits proof of expenses incurred that offset an advance, this is called a clearing payment. Effects on Customizing Two new transactions have been created for Grantor Claims Management, GCL and GCR, which are part of the standard delivery. See Customer Relationship Management -> Transactions -> Basic Settings See also Case Management for Grantor (Enhanced) Customizing Enhancements for Grantor Management 1.30.19 CRM-IPS-MD 1.30.19.1 CRM-IPS-MD-PRG Master Data Grantor Programm 1.30.19.1.1 Grantor Delivery Customizing (New and Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. There are various changes to the standard delivery customizing that affect the Grantor Management program. Two new Claim Web Request categories have been added: SAPGCLDEMO: Sample claim submission form that is linked to the BAdI CRM_SERVICE_WEBREQ for the implementation CRM_WR_SAPGCLDEMO ______________________________________________________________ SAP AG 369 SAP-System ______________________________________________________________ - SAPGCR: Sample change request form that is linked to the BAdI CRM_SERVICE_WEBREQ for the implementation CRM_WR_SAPGCRDEMO See Define Request Categories for more information. New Business Rules Framework (BRF) validation rules for claim have been created for Grantor Claims Management. The BRF is a runtime and maintenance environment for processing, implementing and configuring technical and business rules. It is a central building block for each social services solution. It can be used for automated decision-making, for example, process control for case management. The BRF is enhanced with the following features: New expressions and events to validate claims (dates, valid submission periods) and claim forms New actions to alert the user about maximum number of hours permitted for architect when making a claim New expressions to check that hours for work claimed do not exceed maximum amounts determined in the program definition New events to assess the claim (both header and claim items) New PPF action profiles have been created, which you can use with their default settings or customize using the Define Action Profiles and Actions activity and Define Conditions activity GRM_GAG: Default grant awards action profile, containing action definitions for - printing agreement contracts - displaying the change request form - automatic linking of an agreement to Grantor Management cases - automatic linking of pre-commitment, commitment and billing documents to Grantor Management cases GRM_GAG_ITEM: Grantor agreement item, containing the action definitions for inception of changes GRM_GAP: Default grant applications action profile, containing the action definitions for - checking the grantor application / applicant eligibility using rules within BRF - executing change requests - printing rejection letters - automatic creation of a Grantor Management case and linking it to the program, application and business partners - automatic linking of pre-commitment, commitment and billing documents to Grantor Management cases GRM_GCL: Default grantor claims action profile, containing the action definitions for - automatically linking the claim to the case - checking budget availability - printing rejection letters GRM_GCR: Default grantor change request action profile, containing the action definitions for - automatic linking of the agreement change request to the case - manual and automated execution of change processes - - - ______________________________________________________________ SAP AG 370 SAP-System ______________________________________________________________ Effects on Customizing Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Program Management -> General Settings -> Define Program Profile Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Program Management -> General Settings -> Define Availability Control Profile Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Program Management -> General Settings -> Define Tolerance Profile Customer Relationship Management -> E-Commerce -> E-Service -> Web Requests -> Define Request Categories Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing- > Financial Execution -> Pricing -> Define Financial Execution Type Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Define Value Type Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Change Process Management -> Define Input Field Control Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Change Process Management -> Define Change Processes Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Business Add-Ins: There are three new BAdIs - BAdI: Customer Enhancements for Grantor Agreement - BAdI: Customer Enhancements for Grantor Application - BAdI: Customer Enhancements for Grantor Claim See also Case Management for Grantor (Enhanced) 1.30.20 CRM-IPS-BTX 1.30.20.1 CRM-IPS-BTX-AGR Business Transaction Grantor Agreement 1.30.20.1.1 Change Request (New) Use ______________________________________________________________ SAP AG 371 SAP-System ______________________________________________________________ This release note is only relevant if upgrading from SAP CRM 5.0. You can now use a change request to manage the process of changing your agreements. Commonly, the agreement is a legally binding document, and restrictions exist on the changes that can be made once it has been approved and released. However, since changes are still possible in certain circumstances, a change management system with predefined processes is available. Custom settings determine which fields on the agreement invoke the change management process. Some fields, for example agreement description, may not require the triggering of a review and assessment effort. If a grantee requests a change to the authorized amount or the validity date after the agreement has been released, the grantee or a responsible grantor employee can fill out a change form and submit it as a Web request. Additionally, the employee responsible is determined via a workflow. The employee receives a workflow message that contains the change request ID and the instruction to check the request and to release or reject it. The employee can either manually check whether the required criteria are met or, if the appropriate rules are implemented, trigger a check using the Business Rule Framework (BRF). Alternatively, a completely automated check of the request using the Business Rule Framework (BRF) is possible. For this purpose, the BRF rule 7CHANGE_REQUE is delivered in the application class 7GRANTOR, which checks whether a newly changed date is still within the validity period of the program, for example. You can define additional rules for checking the change request yourself. Once the request has been approved or rejected, a message is sent to the author of the change request via a workflow, an action sets the change request status to Released, and approved changes are displayed in the agreement. If the effective date of the change request is in the future, the original and the changed amounts remain visible as items in the agreement until the effective date is reached. Agreement versions are generated as PDF documents for internal tracking. A sample PDF for external processing of agreements and agreement amendments is also provided. Effects on Customizing Example processes for changing the validity date and authorized amount are delivered in Customizing under Customer Relationship Management -> Industry-Specific Solutions -> Public Sector -> Grantor Management -> Grantor Processing -> Change Process Management. To define processing for additional fields, you need to enter them here and implement them using a BAdI. 1.31 CRM-IHT High Tech 1.31.1 High Tech: Mass Search and Replace (New for SP02) ______________________________________________________________ SAP AG 372 SAP-System ______________________________________________________________ Use This release note is only relevant if upgrading from SAP CRM 5.2. A search and replace function is available for resale and claim reports and inventory reports, enabling mass corrections to be made where the same errors have occurred. From the edit list screen within the two applications, the following can be performed for the selected items: Search for numeric, alphanumeric, dates, text, and blank fields. Replace field values with numeric, alphanumeric, dates, text, and blank fields. 1.31.2 High Tech: Partner Manager Role (New for SP02) Use This release note is only relevant if upgrading from SAP CRM 5.2. A role is available for partner managers, HT-CHM-PARTNERMANAGER, and is a restricted version of the role already available for channel managers, HT-CHM-CHANNELMANAGER. In design registration, channel partners can: Create a new design registration opportunity directly in the channel manager's system and use the standard functions. Work on existing design registrations, with the following restrictions: Fields in projects and assemblies are displayed only and cannot be changed. Projects and assemblies cannot be created. Brand owner information cannot be changed, and there are no hyperlinks to brand owner partner functions. For projects, there are no Project Stage History and Organization assignment blocks. For assemblies, only the assembly details and milestones are displayed. In resale tracking, channel partners can: View channel inventory data and display logs and history details. View inventory report data and display the logs. View the price buckets in which they are involved and display the logs. View resale and claim message details, and display the logs. ______________________________________________________________ SAP AG 373 SAP-System ______________________________________________________________ You define the role navigation in Customizing for Customer Relationship Management, by choosing UI Framework -> Technical Role Definition -> Define Navigation Bar Profile. 1.31.3 CRM-IHT-PP Price Protection 1.31.3.1 High Tech: Reverse Price Protection (Enhanced for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The reverse price protection function has been enhanced to support the same process steps available for normal price protection. When a price increase is detected by a reverse price protection run, debit memos are created, and you can update the price protection records and affected channel inventory records. Prior to SAP CRM 2007 SP02, a price protection record was generated with the status "Not Eligible" if a price increase was detected by a reverse price protection run. Two modes are available for running reverse price protection: Classic Limited function, as previously available. In this mode, reverse price protection behaves as before. This feature has been retained to provide flexibility to those customers who want to run reverse price protection as available prior to SAP CRM 5.2. Enhanced Full processing, as for normal price protection. In this mode, the reverse price protection behavior is extended to generate debit memos based on the price difference and the quantity held by a certain distributor/reseller on the effective date. The debit claim amount is calculated based on this data, and a debit memo request is generated reflecting the calculated claim amount. - Effects on Customizing You select the mode in which you want to run reverse price protection in Customizing for Customer Relationship Management, by choosing Industry-Specific Solutions -> High Tech -> Resale Tracking -> Price Protection -> Configure Application Parameter for Price Protection. You specify ______________________________________________________________ SAP AG 374 SAP-System ______________________________________________________________ either "CLASSIC" or "ENHANCED". 1.31.4 CRM-IHT-PDP Partner Design Projects 1.31.4.1 High Tech: Design Registration (Enhanced for SP02) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The Channel Sales for High Tech application was made available in the CRM WebClient UI in SAP CRM 2007 SP01. The following changes were made in design registration: Standard opportunity management functionality is reused fully. Different business objects are therefore used and certain Customizing objects have changed. The Customizing activities previously available under Customer Relationship Management -> Channel Management -> Channel Sales -> Industry Specific Channel Sales -> Channel Sales for Hi-Tech Industry -> Partner Design Projects have been moved to: Customer Relationship Management -> Industry-Specific Solutions -> High Tech -> Design Registration. The activities under Settings for Opportunities are reused from standard Customizing for opportunity management. Design registration attributes are no longer stored as partner/product range types (PPR types). Design registration attributes are now provided as follows: You define the design registration attributes in High Tech Channel Management Customizing. You assign design registration attributes to the relevant products on the Product page in the CRM WebClient UI in the distribution chain data. Two new assignment blocks are available for this purpose; "Activity Status" and "Registration Status". The assignment blocks are based on the set type functionality available in the product master. The two new set types are as follows. - CRM_CSDR_ACTS (Activity Status) - CRM_CSDR_REGS (Registration Status) The set types have to be assigned to the product category being used for products relevant for design registration. Note that the set types are distribution-chain-dependent, and the registration status is also time-dependent. - - - BI reports for design registration can now be accessed directly from the CRM Web Client UI. ______________________________________________________________ SAP AG 375 SAP-System ______________________________________________________________ 1.32 CRM-IM 1.32.1 CRM-IM-IPM Media Intellectual Property Management 1.32.1.1 Applications Available Through the Transaction Launcher (New) Use The five applications listed below are available through the transaction launcher and can be accessed from the Web-based user interface, the CRM WebClient UI: Incoming royalty billing due list Incoming royalty billing document Outgoing royalty billing due list Outgoing royalty billing document Usage confirmation Effects on Existing Data The billing due list and billing document for incoming royalties are available from the work center of the Sales Contracts. The billing due list and billing document for outgoing royalties are available from the work center of the Acquisition Contracts. Usage Confirmation is available from the work center of Operations. Effects on System Administration You require support package SAP_ABA SP12 to use the tranaction launcher . Check if the entries for OWNLOGSYS are correct in the table for the transcation launcher. Use transaction CRMS_IC_CROSS_SYS to maintain the entries for the client-dependent view. There must be one entry for OWNLOGSYS similiar to the example below: OWNLOGSYS <system> <client> The URL of the ITS should be similar to http://<server><port>sap/bc/gui/sap/its/webgui/!?~transaction=IC_LTX& ~okcode=ICEXECUTE If the CCMP_RABOX is maintained, the transactions will not work. ______________________________________________________________ SAP AG 376 SAP-System ______________________________________________________________ 1.32.1.2 Uniform User Interface for Intellectual Property Management (New) Use A Web-based user interface, the CRM WebClient UI, is now available for Intellectual Property Management. For more information about the features and functionality offered in the new user interface, see the release note Uniform User Interface in CRM (New). . The following functionality has now been removed: Maintenance of products other than IPs, such as materials, in the license acquisition and the license sales contracts. Effects on Existing Data With the exception of migration, system management functions in this release are in the SAP GUI, which you access as before through the SAP Easy Access menu. Effects on Customizing You can find Customizing information for the SAP CRM Web-based user interface in the release note Uniform User Interface in CRM (New). The Implementation Guide includes the following changes for Intellectual Property Management: New IMG activities: Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Basic Functions -> Pricing -> Define Scale Retroactivity Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Master Data ->Product -> Basic Settings -> Define Characteristics of IPM IP Check Messages Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Master Data ->Define Rights Templates Types Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Transactions ->Settings for IPM Transactions -> Define User Interface Scenarios Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights and Royalties Dimensions -> Define Rights Maintenance - - ______________________________________________________________ SAP AG 377 SAP-System ______________________________________________________________ - Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights Availability Analysis -> CRM WebClient UI -> Define Number Ranges for Rights Availability Requests Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights Availability Analysis -> CRM WebClient UI -> Configure Rights Availability Wizard Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights Availability Analysis -> CRM WebClient UI -> Define Rights Availability Scenarios Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Master Data ->Product -> Settings for Rights Generation -> Define Inheriting Relationship Types for Generation Formulas Customer Relationship Management -> Industry-Specific Solutions -> Utilities Industries -> Settings for User Interfaces -> General Functions -> Define Object Hierarchy and Object Attributes Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Master Data ->Product -> BAdIs -> Activate Copying of Interlinkages - - - - - Moved IMG activities: Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Basic Functions -> Pricing -> BAdI for Additional Quantity-Type Fields in Pricing is now found under Pricing ->BAdIs. Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Basic Functions -> Pricing -> BAdI Used to Calculate Additional Data Values is now found under Pricing ->BAdIs. - Removed IMG activities: Customer Relationship Management -> Industry-Specific Solutions -> Media -> Intellectual Property Management -> Rights and Royalties Dimensions -> Generate People Centric UI for Rights and Royalties Dimensions See also You can find more information about which roles are now available for Intellectual Property Management in release note User Role IPM Rights Manager (New). You can find information about which applications are available through the transaction launcher in release note Applications Available Through the Transaction Launcher (New). For more information about new functions available in Intellectual Property Management, see the following release information: Rights Templates (New) Rights Consumption (New) ______________________________________________________________ SAP AG 378 SAP-System ______________________________________________________________ - Outgoing Royalties Settlement without Differential Billing (New) For application-specific information, see the following release information: Intellectual Property Maintenance from SAP GUI (Changed) Intellectual Property Rights Maintenance Check (Enhanced) Rights Availability Analysis (Changed) License Contract Maintenance (Changed) Rights Maintenance Check (Enhanced) 1.32.1.3 CRM-IM-IPM-MD Master Data 1.32.1.3.1 Intellectual Property Rights Maintenance Check (Enhanced) Use The check within the rights maintenance of an intellectual property (IP) is now enhanced. You have more flexibility in the checks performed for a right within an IP. For example, in the previous release, the system always generated an error message if the release dates were not a subset of the rights owned. You can now define the settings in the Customizing so that a warning message displays instead of an error message in certain cases, or so that the system will not perform a check at all in other instances. Effects on Customizing See also For more information about rights maintenance, see Rights Maintenance in Intellectual Property Management (Changed). In the IMG activity Define Characteristics of IPM IP Check Messages, you can determine the types of messages the user receives during the rights maintenance check. 1.32.1.3.2 Intellectual Property Maintenance from SAP GUI (Changed) Use ______________________________________________________________ SAP AG 379 SAP-System ______________________________________________________________ You can no longer use the SAP GUI for Intellectual Property (IP) maintenance. This functionality is now available for IPs in a Web-based user interface, the CRM WebClient UI. Rights (Rights Owned, Release Dates, Release Restriction) were displayed in table format when accessed from the SAP Easy Access menu. This display format meant that the overview was quickly lost if several rights groups were required to define the rights owned for an IP. In the new UI, the rights now display in a hierarchy. For more information about rights maintenance for the Web-based user interface, see the release note for Rights Maintenance for Intellectual Property Management. Effects on Existing Data The new UI also supports IPs that were created in an earlier release. Once you edit this type of IP in the new UI, the system converts this IP to the new display format. During this process, the system assigns each rights group to a new rights scope created. Effects on System Administration Two additional set types (IPM_RGHT_SCP and IPM_RGHT_S_I) are required for the new rights scope grouping level. Both of these set types must be assigned to all IP product categories, which previously already contained the rights set types (IPM_RIGHTSOWN, IPM_RELDAT, IPM_RELRES, IPM_ROWN_GRANT). Add these set types to the IP product categories in the categories and hierarchy maintenance. All IP relationships were previously assigned to a category implicitly if an IP relationship was not explicitly assigned to a category. This rule is no longer supported for the current release. You must assign all relationships that you want to use for this IP to a category. See also For more information, see the main release note for Intellectual Property Management. 1.32.1.3.3 Rights Templates (New) Use You can define master data objects called rights templates that allow you to restrict the rights to an Intellectual Property (IP) to varying levels. A rights template specifies certain markets, territories, languages, or values in other rights dimensions, but does not specify the IP or the validity period. You can use a rights template to quickly create contracts, maintain IPs, or perform a rights availability analysis in which the rights to an IP are restricted according to the information defined in the rights template. ______________________________________________________________ SAP AG 380 SAP-System ______________________________________________________________ Effects on Customizing You use IMG activity Define Rights Template Types to classify the rights templates into different rights template types. 1.32.1.3.4 Rights Consumption (New) Use In license acquisition contract items, you can specify a quantity ("number of runs") that has been acquired. These numbers are copied into the intellectual property (IP) when the system carries out the rights generation if the generation rule for the IP specifies Union with contract reference (operation type R instead of +). If you consume or sell numbered runs, it is necessary to identify the acquisition contract the consumed runs belong to with a granting reference to the contract. This is important if you have several acquisition contracts with different conditions (royalties, validity period, etc.). In this instance, the granting reference allows you to choose the acquisition contract it is most advantageous to use. If underlying IPs should also be considered for rights availability and royalty calculation, you need to use the new relationship type Underlying Component (Granting Ref.) in the IP. The system only considers the subordinate IPs assigned as Underlying Component (Granting Ref.) in the royalty calculation when you select the contract linked to the subordinate IP by the granting reference. The granting reference to the license acquisition contract then appears in any license sales contract that includes IPs assigned with this relationship type. (With the old relationship type, Underlying Component, all acquisition contracts for the related IPs were included in the royalties calculation and benefited from the sales.) In order to resolve the ambiguity in the license sales contract, the system carries out an extended collision check that allows you to select rights from particular license acquisition contract items for consumption. The system displays the following for the IP sold and the included IPs: Open rights Available acquisition contracts Assigned acquisition contracts As soon as you select certain rights for consumption, the system removes them from the available rights (if they were also available from another license acquisition contract), so that overlapping acquired rights cannot be consumed more than once. The collision check completes successfully when there are no more missing rights and open rights have been assigned. ______________________________________________________________ SAP AG 381 SAP-System ______________________________________________________________ Effects on System Administration In order to execute the extended collision check, the user needs authorization for the new "Authorization object for Collision Check" (CRM_IPM_CC). It supports the activities Display (03) and Execute (16). Effects on Customizing In the IMG activity Define Formulas for Generating the Rights Owned, you can assign the availability profile 0DEF in the dialog box Generation rules. You can also use the operation Contract reference in the dialog box Generation steps. These two settings mark IPs with this generation rule for the extended collision check in the license sales contract. The BAdI for Availability Profile allows you to override the standard calculation of available rights. (The default is given by the fallback implementation.) - 1.32.1.3.5 Rights Maintenance for Intellectual Property Management (Changed) Use You can no longer use the SAP GUI for rights maintenance in Intellectual Property Management (IPM). This functionality is now available in a Web-based user interface, the CRM WebClient UI, from the following applications: IP maintenance License acquisition contracts License sales contracts Rights availability analysis The IP contains different types of rights (Rights Owned, Rights Owned (Granting ref), Release Dates, Release Restriction). Rights are displayed in a hierarchy in which the rights scope contains the validity dates and other attributes. The group contains all the dimensions used with their respective attribute values. All groups within one scope share the same global properties of their common scope. For most rights types, you can maintain new rights through the templates or by creating them manually. The templates are only supported for the Rights Owned. You can only assign the Rights Owned (Granting ref.) through the rights generation tool in the IP overview. Effects on Customizing In the IMG activity Define Rights Maintenance, you can define the separator used between attribute values and also if the attribute ID or description displays. ______________________________________________________________ SAP AG 382 SAP-System ______________________________________________________________ - In the IMG activity Define Object Hierarchy and Object Attributes, you can define the tree profiles that are used to display data for rights maintenance. In the IMG activity Define Rights Template Types, you can set up a mapping between the rights template types and the rights types. Rights types are specific to the application, whereas you can define a new template type in addition to the two types delivered for other needs. See also For information about rights templates, see the release note for Rights Templates (New). 1.32.1.4 CRM-IM-IPM-BTX Business Transactions Licensing 1.32.1.4.1 Rights Consumption (New) Use In license acquisition contract items, you can specify a quantity ("number of runs") that has been acquired. These numbers are copied into the intellectual property (IP) when the system carries out the rights generation if the generation rule for the IP specifies Union with contract reference (operation type R instead of +). If you consume or sell numbered runs, it is necessary to identify the acquisition contract the consumed runs belong to with a granting reference to the contract. This is important if you have several acquisition contracts with different conditions (royalties, validity period, etc.). In this instance, the granting reference allows you to choose the acquisition contract it is most advantageous to use. If underlying IPs should also be considered for rights availability and royalty calculation, you need to use the new relationship type Underlying Component (Granting Ref.) in the IP. The system only considers the subordinate IPs assigned as Underlying Component (Granting Ref.) in the royalty calculation when you select the contract linked to the subordinate IP by the granting reference. The granting reference to the license acquisition contract then appears in any license sales contract that includes IPs assigned with this relationship type. (With the old relationship type, Underlying Component, all acquisition contracts for the related IPs were included in the royalties calculation and benefited from the sales.) In order to resolve the ambiguity in the license sales contract, the system carries out an extended collision check that allows you to select rights from particular license acquisition contract items for consumption. The system displays the following for the IP sold and the included IPs: Open rights Available acquisition contracts Assigned acquisition contracts As soon as you select certain rights for consumption, the system removes them from the available rights (if they were also available from another license acquisition contract), so that overlapping acquired rights cannot be consumed more than once. The collision check completes successfully when there are no more ______________________________________________________________ SAP AG 383 SAP-System ______________________________________________________________ missing rights and open rights have been assigned. Effects on System Administration In order to execute the extended collision check, the user needs authorization for the new "Authorization object for Collision Check" (CRM_IPM_CC). It supports the activities Display (03) and Execute (16). Effects on Customizing In the IMG activity Define Formulas for Generating the Rights Owned, you can assign the availability profile 0DEF in the dialog box Generation rules. You can also use the operation Contract reference in the dialog box Generation steps. These two settings mark IPs with this generation rule for the extended collision check in the license sales contract. The BAdI for Availability Profile allows you to override the standard calculation of available rights. (The default is given by the fallback implementation.) - 1.32.1.4.2 CRM-IM-IPM-BTX-PUR License Acquisition 1.32.1.4.2.1 License Contract Maintenance (Changed) Use You can no longer use the SAP GUI to maintain license acquisition contracts and license sales contracts. This functionality is now available in a Web-based user interface, the CRM WebClient UI. The full contract structure is displayed in an overview tree grouped by the intellectual property (IP), where you can find the most important information at one glance. Under each IP, you can see the related advance groups, rights scopes, and royalty scopes with detailed information. The items are grouped by category. For example, items which are only rights-relevant are displayed as rights scopes, items which are only royalty-relevant are displayed as royalty scopes, and so on. This means that when you create a new scope, you have more guidance when you assign item categories for a specific scope type. For example, if you create a new scope for flat fee royalties, the system only allows you to select the item categories that are classified for flat fee royalties. Also, the system now creates the final invoice for an advance group automatically. Therefore, a new Customizing activity is necessary in which you can define different UI scenarios and assign them to the transaction types. In this Customizing activity, you can select which scope types are supported and which item categories are allowed for these scope types. For example, if you have a contract type where you need only advance groups and variable rights and royalty scopes, you can define a scenario that only includes the information you need. If you use reserves for license acquisition contracts, the assignment delivered for reserves expects that the standard condition types delivered for reserve rates, 17R1 and 17R2, are available in the condition group assigned to the relevant item category. If you use other condition types, the assignment is not displayed. ______________________________________________________________ SAP AG 384 SAP-System ______________________________________________________________ Effects on Customizing In the IMG activity Define User Interface Scenarios, you can define the different UI scenarios, including the tree profile for the overview tree. In the standard the UI scenario IPM is available. This contains all possible item group types and can be used for license sales contracts and license acquisition contracts. In the IMG activity Define Object Hierarchy and Object Attributes, you can create your own tree profile for the overview tree. Otherwise, you can use the standard tree profile IPM_LICCON. In the IMG activity Define Scale Retroactivity, you can set the scale retroactivity type and assign item categories allowed for each type. In the IMG activity Define Rights Maintenance, you can define the separator used between attribute values and also if the attribute ID or description displays. In the IMG activity Define Rights Template Types, you can set up a mapping between the rights template types and the rights types. Rights types are specific to the application, whereas you can define a new template type in addition to the two types delivered for other needs. - See also For more information, see the main release note for Uniform User Interface for Intellectual Property Management (New). In the license sales contract an extended collision check is supported. For more information, see release note Rights Consumption (New). For more information about the new rights maintenance, see Rights Maintenance for Intellectual Property Management (Changed). 1.32.1.4.3 CRM-IM-IPM-BTX-SAL License Sales 1.32.1.4.3.1 License Contract Maintenance (Changed) Use You can no longer use the SAP GUI to maintain license acquisition contracts and license sales contracts. This functionality is now available in a Web-based user interface, the CRM WebClient UI. The full contract structure is displayed in an overview tree grouped by the intellectual property (IP), where you can find the most important information at one glance. Under each IP, you can see the related advance groups, rights scopes, and royalty scopes with detailed information. The items are grouped by category. For example, items which are only rights-relevant are displayed as rights scopes, items which are only royalty-relevant are displayed as royalty scopes, and so on. This means that when you create a new scope, you have more guidance when you assign item categories for a specific scope type. For example, if you create a new scope for flat fee royalties, the system only allows you to select the item categories that are classified for flat fee royalties. ______________________________________________________________ SAP AG 385 SAP-System ______________________________________________________________ Also, the system now creates the final invoice for an advance group automatically. Therefore, a new Customizing activity is necessary in which you can define different UI scenarios and assign them to the transaction types. In this Customizing activity, you can select which scope types are supported and which item categories are allowed for these scope types. For example, if you have a contract type where you need only advance groups and variable rights and royalty scopes, you can define a scenario that only includes the information you need. If you use reserves for license acquisition contracts, the assignment delivered for reserves expects that the standard condition types delivered for reserve rates, 17R1 and 17R2, are available in the condition group assigned to the relevant item category. If you use other condition types, the assignment is not displayed. Effects on Customizing In the IMG activity Define User Interface Scenarios, you can define the different UI scenarios, including the tree profile for the overview tree. In the standard the UI scenario IPM is available. This contains all possible item group types and can be used for license sales contracts and license acquisition contracts. In the IMG activity Define Object Hierarchy and Object Attributes, you can create your own tree profile for the overview tree. Otherwise, you can use the standard tree profile IPM_LICCON. In the IMG activity Define Scale Retroactivity, you can set the scale retroactivity type and assign item categories allowed for each type. In the IMG activity Define Rights Maintenance, you can define the separator used between attribute values and also if the attribute ID or description displays. In the IMG activity Define Rights Template Types, you can set up a mapping between the rights template types and the rights types. Rights types are specific to the application, whereas you can define a new template type in addition to the two types delivered for other needs. - See also For more information, see the main release note for Uniform User Interface for Intellectual Property Management (New). In the license sales contract an extended collision check is supported. For more information, see release note Rights Consumption (New). For more information about the new rights maintenance, see Rights Maintenance for Intellectual Property Management (Changed). 1.32.1.5 CRM-IM-IPM-RO Royalty Accounting Outgoing Royalties 1.32.1.5.1 CRM-IM-IPM-RO-ROO ______________________________________________________________ SAP AG 386 SAP-System ______________________________________________________________ 1.32.1.5.1.1 Outgoing Royalties Settlement Without Differential Billing (New) Use The Customizing delivered includes the contract item category IPM Rgt+Roy PBP (IEM4). This category is for usage-dependent outgoing royalties settlement with accruals that do not require differential billing. The (statistical) condition types on which a percentage royalty calculation is based, such as the sales volume, must carry the total values from the current billing or settlement period. This is demonstrated in the example below, which assumes a royalty rate of 10%, increasing to 15% after 20,000 sold pieces, and sales of 10,000 pieces (for $1 per piece) in January and 5,000 in each subsequent month. Billing Period First quarter First quarter another 500 First quarter liquidated Second quarter Second quarter another 750 Second quarter liquidated Month Jan Feb March Basis 10,000 15,000 20,000 Royalties 1,000 1,500 2,000 Result Accrued for 1,000 Accrued for Accruals Royalties 2,000 Accrued for 750 Accrued for Accruals Royalties 2,250 For such basis values, a new cumulation scope (Per billing period - C) is available. April May June 5,000 10,000 15,000 750 1,500 2,250 Effects on System Administration To use the Per billing period cumulation scope (C), adjust the settings in IMG activity Adjust Billing Engine Application for Settlement of Outgoing Royalties under IPMO -> Object -> DL -> Container -> DLI -> Usage. See also the usage documentation. Effects on Customizing The example Customizing contains the following entries: Define Item Categories: The IPM Rgt+Roy PBP (IEM4) item category is now available for this scenario. In IMG activity Define Settings for IPM Item Categories, this item category is rights-relevant and the difference relevance is set to PBP: In this billing period (C). Also evaluate the additional settings for the new item category in the following IMG activities: Define Item Category Determination ______________________________________________________________ SAP AG 387 SAP-System ______________________________________________________________ - Define Copying Control for Item Categories Assign Billing Plan Type to Item Categories Define Condition Type: Two new condition types are now available for this scenario: NetValuePBPOR (17B0): This holds the cumulative value over one billing period (of the data value 1IR1), which can be used as the condition basis for condition type 17PO in a scenario where the scale basis is the cumulative ITD value. Note: In this case, the scale basis of 17PO must be set to the value of 17B0 by a customer-specific scale basis formula. PBP Per. w/ Qty OR (17PB): This is a percentage condition which also can have 17BO as condition basis. But, unlike 17PO, the scale basis of 17PB is the price quantity, which in pricing procedure 17IP14 is the cumulative quantity of value type 1IR3. - - Create Maintenance Group: The condition group IPM Acq. Item PBP (1702) is now available for this scenario. Define Data Values: The new cumulation scope PBP: In this billing period (C) and condition type NetValuePBPOR (17B0) are assigned to data value Confirmed Sales Volume (1IR1). Define Scale Retroactivity: An entry for item category IPM Rgt+Roy PBP (IEM4) is maintained for Per Period scale retroactivity (C). Create Pricing Procedure: A new pricing procedure, IPM Billing Purchasing PBP (17IP14), is now available. Define Billing Types for IPM License Settlements (IPM Outgoing Royalties): Two new billing types are available for the IPM Billing Purchasing PBP pricing procedure. Assign one of the following billing types: OR Per Billing Period (PBP) (OR04) OR Per Billing Period Accruals (OR05) 1.32.1.6 CRM-IM-IPM-RIN Rights Inventory Analysis 1.32.1.6.1 Rights Availability Analysis (Changed) Use You can no longer use the SAP GUI for the rights availability analysis (RAA). This functionality is now available in a Web-based user interface, CRM WebClient UI. The RAA offers functions for searching and analyzing the rights situation of Intellectual Properties (IPs). It is designed like a wizard or guided activity. The wizard typically consists of four steps. The user can navigate to each subsequent or preceding step. Step 1 - General Request ______________________________________________________________ SAP AG 388 SAP-System ______________________________________________________________ In the first step you can maintain the request's header data, for example, the request ID and description. Step 2 - Availability Criteria In this step you maintain the rights criteria you are interested in. In contrast to the old RAA, you can now enter more than one rights group and the number of runs. In this step you also select the status profile, which defines the type of calculations the RAA will perform. In the current release, only the status profile Available Rights is supported. Step 3 - IP Search In this step, you search for IPs that will be analyzed in the calculations. You have the following search options: Search in IP Master Search in license acquisition and sales contracts Filter the IPs by rights Add related IPs to the search result From the list of found IPs, you can select the IPs that are relevant for your analysis. Step 4 - Availability In this step, you see a hierarchy of IPs for which the rights situation is calculated. After the execution, you see the rights situation indicated by a status icon. For example, a green status icon indicates that the requested rights for the IP are available, while a red status icon indicates that they are not available. You also see a status vector for each IP in the hierarchy, showing sets of existing or missing rights. These sets are called detail statuses. The following detail statuses are currently supported: Available rights Missing rights Not owned rights Not released rights Restricted rights Sold rights Acquired rights In the overview hierarchy, you can also create license acquistion contracts or license sales contracts. From the overview hierarchy you can navigate to a detail view, which shows you the rights situation for an IP in detail. For each calculated detail status, you see the list of rights grouped into that status. You can use the status to determine why a requested right is not available or which rights are available in detail. In addition to the detail view that displays all detail statuses for one IP, an overview for the available rights of all IPs exists. ______________________________________________________________ SAP AG 389 SAP-System ______________________________________________________________ Effects on System Administration In order to use the RAA, a user needs authorizations for object CRM_IPMRAA.. The object includes the fields Scenario and Activity. In the Scenario field, you define the RAA-Scenario that the user is allowed to use, and in the Activity field you define the action the user can perform with a request. The following actions are supported: Create / Change Display Delete Effects on Customizing In the IMG activity Define Rights Availability Scenarios, you can change the default descriptions and icons for a rights availability scenario. In the IMG activity Configure Rights Availability Wizard, you can customize the Rights Availability Analysis wizard by changing the steps. For example, you can add or delete a step, or change the description of the steps. In the IMG activity Define Number Ranges for Rights Availability Requests, you can maintain the number ranges for the rights availability requests through transaction SNRO. The application needs two number ranges: 01: This is for internal numbers given from the system. AB: This can have the range from 'A' to 'ZZZZZZZZZZZZZZZZZZ' and must be flagged for external use. - You cannot save a request without these number ranges. See also For information about rights maintenance, see the release note for Rights Maintenance for Intellectual Property Management (Changed). 1.33 CRM-IPH Pharmaceuticals 1.33.1 Account Hierarchy Affiliation and Class of Trade (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. Account Hierarchy Affiliation The account hierarchy incorporates new features specifically for the Life Sciences industry. ______________________________________________________________ SAP AG 390 SAP-System ______________________________________________________________ When contracting organizations, such as group purchasing organizations (GPOs), negotiate pricing for certain products on behalf of their members (pharmacies, hospitals), the contracting organization maintains a membership list that identifies the customers that belong to the contracting organization. A member of a membership list can be a customer, another buying group or a subdivision of a buying group, often referred to as a shareholder. This information can be represented in the system using the account hierarchy, the nodes being used to denote the individual shareholders. This is also known as account hierarchy affiliation. As part of the business process, it is possible to denote that certain accounts belonging to the hierarchy are not valid for certain contracts or not eligible for special pricing. Since members can be part of multiple hierarchies, a particular member may not be active for a certain time period on certain hierarchies for contracting purposes. The account affiliation details can be displayed and maintained on the account master screen in the Hierarchy Affiliation assignment block. It provides the following information: Hierarchy Tree: The hierarchy tree to which the account is attached Hierarchy Top Node: Text of the top node, generally denoting the owner for the whole hierarchy Hierarchy Node: Name of the node to which the account is attached Valid From: Date from which the account is active in the hierarchy Valid To: Date up to when the account is active in the hierarchy Blocked: Active or blocked status of the account An account can be activated and deactivated on the hierarchy, as required. For example, an account is currently valid from 01.01.2005 to 31.12.2006 and has the status "Active". You now decide to deactivate the account as of 01.01.2006. In the Hierarchy Affiliation assignment block on the account master screen, you set the valid-to date for this hierarchy to 31.12.2005, then add a new line and define the additional validity from 01.01.2006 until 31.12.2006 with the status "Blocked". When changes are made, records are merged if the statuses of the records are the same and the dates sequential. A hierarchy affiliation history is available and shows the entire history of the account assignment. Class of Trade (COT) This classifies customers and is used to segment pricing and drive pricing policies. Contracts may be established for specified COTs, which are used as filters for contract partner eligibility. In multi-divisional companies, each division may use their own COT designation. A Class of Trade can be assigned to an account in account maintenance under Classification in the Group and Subgroup fields. ______________________________________________________________ SAP AG 391 SAP-System ______________________________________________________________ 1.33.2 Contract Management for Life Sciences (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or SAP CRM 5.2. Contract Management for Life Sciences (CM for LS) is a scenario tailored for pharmaceutical, medical device, and diagnostic companies that builds on the Contract Management scenario delivered with CRM 5.0. Starting with events that trigger contract creation activities such as negotiation, acceptance and execution, contract management in CRM leverages the SAP platform to better collaborate, streamline and automate routine steps in your business process, and improve overall productivity. The CM for LS solution covers enhancements and new functionality in the following business processes: Contract Development Contract Administration Chargebacks and Distributor Rebates Contract Development Contract development begins with initiation, through negotiation, acceptance and execution of a contract. This involves negotiating and capturing contract product prices, determining contract member eligibility and modelling prices. Once the contract is agreed upon by both parties, the manufacturer will notify the wholesaler / distributor (channel partner) of the contract prices and eligible parties by sending a bid award document via EDI. The following are the new and enhanced features supporting this process: Incentive Program Management (New) You can Model prices in a contract by using incentive programs. This gives you an open and flexible structure for defining price and rebate incentives that are attached to an item on the contract and also allows you to capture processing and tracking attributes. Attach pre-defined or custom incentive programs to contracts, making it an effective way of developing competitive contracts where complex pricing models are involved. Use condition generation for price and rebate incentives. Condition records indicate what form your incentives will take. This means that you define the scope of your concession and the incentive program uses condition generation to translate it to the business document. - Incentive programs are integrated with the CRM Business Rules Framework (BRF), this gives you the flexibility to add rules to evaluate customer and product eligibility - when considering a concession. The scenario is shipped with two incentives (that is, floating and fixed prices), illustrating how the Incentive Program object can be used to add new incentives during the implementation project. ______________________________________________________________ SAP AG 392 SAP-System ______________________________________________________________ Contract Administration and Monitoring This scenario covers processes that begin with contract activation, continue with ongoing maintenance, and end with the expiration of a contract. This includes automating processes that manage contract eligibility by cascading source data changes onto contracts and rebate agreements or adding business partner exceptions with varying validity dates. The following are the new features supporting this process: Cascade Manager (New) Since business in the life sciences industry is largely through indirect channels, that is, via distributors, operational data in business documents such as contracts and rebate agreements have to be updated regularly. The cascade manager captures changes in operational data such as list prices, business partner hierarchy etc., evaluates them and identifies the affected business documents before cascading these changes on to the appropriate business documents and generating triggers to notify affected stakeholders. Business Partner Exceptions (New) Long-term agreements in life sciences are primarily, with Group Purchasing Organizations (GPO) who negotiate and administer contracts for their members. GPO or member affiliation is maintained through the business partner group hierarchy (BPH). BPH hierarchy nodes can be attached to a contract thus making linked business partners like hospitals, eligible for the contract. It might be necessary to exclude some of the individual business partners belonging to the hierarchy node attached to the contract. Or, individual business partners may have to be added to a contract with validity dates that differ from the contract header. The Business Partner Exceptions application (BPE) supports this requirement. BPE allows a user to include or exclude a business partner with validity dates that differ from the contract header. Notification Manager (Enhanced) This helps you inform the channel partner of changes in business documents. For example, you could inform your channel partner of changes in prices or products. You can also use the On-Demand report feature, to inform partners of changes in business documents. Unlike the notification manager, you can use this feature inform any other partner such as a buying partner, or a hierarchy node partner also - and not just the channel partner. Since the wholesaler invoices the end-customer at the contract rate, the notification process will continue through the life of the contract as prices change and customers are added or expired from a contract. Chargebacks and Distributor Rebates This scenario covers handling and payment of claims submitted by distributors and wholesalers. Chargeback and distributor rebate management functions enable you to: Automatically correct chargeback discrepancies Validate claims in a timely fashion Reduce disputes and resubmissions The following are the enhanced features supporting this process: Resale Tracking Engine (Enhanced) ______________________________________________________________ SAP AG 393 SAP-System ______________________________________________________________ - Receive Claims Chargebacks have been enhanced to handle submissions of the EDI 867 document. This contains both claim and resale report transactions that are also known as sales tracings. The RTE also allows you to define edit rules by transaction type. Validate Claims You can support service or administrative fees that are calculated when claim lines are submitted. You can use predefined condition types to include service fees in a contract. Condition types support a variety of calculation types that is, dollar per unit, percent of contract price and so on. In addition to supporting service fee calculations, you have additional options to edit lines especially in the context of overriding a contract and/or a WAC price as well as contract number. Claim lines where the manufacturer pays a different amount or rejects due to submission errors (with respect to contract eligibility, or a missing shipping date ) are sent back to the wholesaler in a reconciliation report via EDI. - Effects on Data Transfer Once the contract is agreed upon by both parties, the manufacturer will notify the wholesaler / distributor (channel partner) of the contract prices and eligible parties by sending a bid award document via EDI. Since the wholesaler invoices the end-customer at the contract rate, the notification process will continue through the life of the contract as prices change and customers are added or expired from a contract. Claim lines where the manufacturer pays a different amount or rejects due to submission errors (with respect to contract eligibility, or a missing shipping date ) are sent back to the wholesaler in a reconciliation report via EDI. - Effects on Customizing You have made all the relevant customizing settings under Life Sciences/ Pharmaceutical Industry by choosing transaction SPRO, Customer Relationship Management -> Industry-Specific Solutions . See also Account Hierarchy Affiliation and Class of Trade (New) Products: Pharmaceutical Attributes and NDC (New) BI Extractors for Chargebacks (New) ______________________________________________________________ SAP AG 394 SAP-System ______________________________________________________________ 1.33.3 Products: Pharmaceutical Attributes and NDC (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. The product master now provides set types designed specifically for the pharmaceuticals industry. These are the set types CMS_PROD_ATTR, which contains the pharmaceutical attributes, and the set type CMS_NDC_ALTID, which is used as the alternative ID for pharmaceutical products, the National Drug Code (NDC). Pharma Attributes CRM delivers only a number of predefined attributes as examples, allowing further attributes to be defined according to company-specific requirements. The attributes provided are limited to the standard values available with the FDB's NDDF file (First Data Bank National Data Drug File). The following attributes are available in the set type CMS_PROD_ATTR: CMS_THERA_CODE: Therapeutic Class Code (Drug Category) The American Hospital Formulary Service (AHFS) code is a six-digit hierarchical classification that refers to a specific type of therapeutic activity for a drug. The AHFS therapeutic class code represents a three-level hierarchy, where level 1 is the anatomical group and other groups, level 2 the drug group, and level 3 the drug class. CMS_GENERIC_CODE: Generic Code A random number (six digits) representing the generic formulation specific to the ingredient combination, route of administration, dosage form, and drug strength. CMS_PROD_STR: Product Strength For products with a single active ingredient, the strength may be comprised of a single metric strength value and unit of measure, or an ingredient metric strength, unit of measure, and a liquid dilution. For multiple active ingredient products, the strength comprises multiple metric strength values and units of measure,with or without a liquid dilution. Up to five separate ingredient strengths are possible. CMS_DOSAGE: Dosage Form This is an abbreviation for the product dosage form. The dosage form is how the product is delivered, that is liquid, solid, or gas. CMS_ROUTE_ADM: Route of Admin Identifies how the product, in the defined dosage form, is administered to the patient. CMS_HICL: HICL: HICL The six-position hierarchical ingredient code list (HICL) contains a maximum of nine sequenced ingredient codes, hierarchical ingredient codes (HICs). Each six-character HIC identifies a specific ingredient, therapeutic class, pharmacological class, and organ system to which the drug is targeted. CMS_UNITDOSE: Unit Dose Indicates if the product is provided in a single unit dose packaging. - - - - - Package size and package quantity are represented as units of measure: ______________________________________________________________ SAP AG 395 SAP-System ______________________________________________________________ - Package Size: The unit or number of units that make up a package. This represents the number of raw units contained in a package, for example the number of tablets in a bottle. Package Quantity: This is a unit of measure. For example, a package contains six bottles that in turn contain raw units. Pharmaceutical attributes can be defined using the standard set types and attributes functionality in Customizing. Alternative IDs CRM delivers a predefined alternative ID type 'NDC'. Each listed drug product is assigned a unique 10-digit, 3-segment number, the NDC. This number can be represented in the product master using alternative IDs. The NDC can be represented in the various different formats shown below: N1 - National Drug Code in 4-4-2 Format N2 - National Drug Code in 5-3-2 Format N3 - National Drug Code in 5-4-1 Format N4 - National Drug Code in 5-4-2 Format The NDC is divided into three segments. The first segment is the labeler code that identifies any firm that manufactures, re-packs, or distributes a drug product. The second segment is the product code. It identifies the strength, dosage form, and formulation. The third segment is the package code. This segment identifies package size. The 11-position format 5-4-2 (N4) has been adopted as the standard in the CRM system. The different formats are converted during communication between the various parties involved. The NDC codes used by manufacturers to maintain their own products are specified in Customizing, those used by channel partners are specified in the business partner master data in the IDs Used for Communication assignment block. The alternative ID is available as a search criterion. 1.33.4 Time Dependencies for Business Partners (Telco) - New Use This release note is only relevant if upgrading from SAP CRM 5.0. Previously it was only possible to maintain current data for a business partner. However, it is now ______________________________________________________________ SAP AG 396 SAP-System ______________________________________________________________ possible to maintain data in advance if that information is already known and available. For example, a business partner may be changing address or changing bank account. This information is particularly important for those working in a call center where it needs to be readily available. The following information is time-dependent and can therefore be maintained in advance. General data such as names Address data Address usage Bank details Multiple changes are possible for one date in the future. But it is only possible to maintain one future date. 1.33.5 CRM-IPH-CB Chargebacks 1.33.5.1 Chargeback Claims BI Extractors (New) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. You can use BI extractors to transfer data from the source system to the SAP NetWeaver Business Intelligence (SAP NetWeaver BI) system so you have a basis on which to build your BI content. This document provides information about BI extractors for the Contract Management for Life Sciences scenario. In the chargebacks / distributor rebate business process, chargeback claims occur when the wholesaler sells the manufacturer's material at a contract price, which is lower than the wholesaler acquisition cost (WAC). The chargeback requested by the wholesaler is the difference between the WAC and the contract price paid by the customer at the time of sale. The SAP CRM and SAP ECC systems perform various system edits and processes to validate claims, process claims for credit approval, generate chargeback credit memo requests and reconciliations, and store chargeback data for historical purposes. Extractor Name: 0CMS_CB_TRAN ______________________________________________________________ SAP AG 397 SAP-System ______________________________________________________________ - Type of Datasource - TRAN Application Component - 0CRM_PH Extract Structure - CMST_CB_BW You can extract data from the chargeback application, by performing a full extraction or by performing a delta extraction. These requests may be made with specific data filtering criteria. 1.34 CRM-IT Telecommunications 1.34.1 Functions in Dispute Management (New for SP02) Use Link Objects to Disputes For certain objects, such as bills, you can create a relationship with a dispute by clicking the pushbutton Link to Dispute, and so enter additional information for the dispute. As long as the dispute for a confirmed account is being processed, each new document is assigned to this dispute, even when you create a document using the navigation frame. The interlinkage of objects with the dispute is saved in the transaction history. The following business object types are supported as standard: Billing document (BUS20810) Billing item (BUS20820) Event detail record (EDR) (CRM_EDR_12) CRM complaint (BUS2000120) Correspondence (SOFM, CRMICLETTR, CRMICFAX) You can find more information in SAP CRM Customizing, at Customer Relationship Management -> Industry-Specific Solutions -> Telecommunications -> Dispute Management -> Define Profiles for Dispute Management. Displaying Related Objects Objects related to a dispute can be displayed in the detail view of the dispute by pushing the button Related Objects. If you click the link in the column Object ID of the list you can display the detail of the related object. Correspondence like e-mails, letters, and fax related to a dispute are listed under Correspondence. ______________________________________________________________ SAP AG 398 SAP-System ______________________________________________________________ - Maintaining Correspondence By clicking the More pushbutton in the dispute header overview, you can create documents such as e-mails, faxes, or letters, and so manage your correspondence directly in the dispute. For example, if you want to create a letter, the system opens a Word document in which appropriate data from the dispute is already available. Document templates can be made available for you to use. When you save the document, the system automatically creates a link between the dispute and the document, and the document is assigned to the open dispute. If you choose the Correspondence pushbutton in the detail view, the newly created document is displayed in the list. As long as a dispute for a confirmed account is being processed, each new document can assigned to this dispute, even when you create a document using the navigation frame. In each detail view in which documents (e-mails, faxes, or letters) are displayed for the confirmed account, you can create an assignment to the respective dispute by using the Link to Dispute pushbutton. Using the Correspondence pushbutton, you can display the previous correspondence for the respective dispute. If you click the document link you can go to the corresponding document and, for example, submit documents that are still in process. Using Different Currencies In a dispute, you can enter items with different currencies. If the currency in the disputed bill differs from the currency defined at header level, the system automatically translates the amounts for the currency specified at header level. The currency at header level is determined using the sales area data. You can manually change the currency at header level. If you change the currency at header level, the system also automatically translates the amounts at item level if the currency there differs from the header level currency. - 1.34.2 Financial Customer Care and Dispute Management (Enhanced) Use This release note is only relevant if you are upgrading your system from SAP CRM 5.0. The business scenario includes the following new or enhanced processes: New with SAP CRM 5.2 or SAP CRM 2007: Note: All the functions listed here require SAP FI-CA based on SAP ERP 6.0 Enhancement Package 2 at the lowest as the back-end system. However, SAP ERP 6.0 ist still supported as the back-end system. ______________________________________________________________ SAP AG 399 SAP-System ______________________________________________________________ For further information on release dependency, see SAP notes 1075410 and 746475. Payments in the Interaction Center for Financial Customer Care Maintain payment methods If you use SAP ERP 6.0 Enhancement Package 2, the payment methods are no longer defined in the FI-CA profile for the user role but in SAP FI-CA. You can define the payment methods for each country for the following payment types: Payment Installment plan Promise to pay Payment specification or payment request Payment requests Grouping of items for which payment orders are to be made to form one payment request in the ERP system Payment specification Grouping of items in a payment specification in the ERP system - Installment Plan You can define payment data for installment items. Payment Search As of SAP ERP 6.0 Enhancement Package 2, you can restrict a payment search to a certain number of payments. You can also limit the maximum number of payments on which the search is to be run. This allows you to avoid long waits when executing the search. You can define standard values for this function in Customizing for the FI-CA profile. The agent can adjust these parameters on the interface for the payment search. Account Balance Display new flexible FI-CA balances Display configurable additional data Enhanced support for contract data in the account balance Display processing locks for contracts Dunning history Display collection strategy and collection step Payment Data You can define bank details for a specific period in a business partner's payment data. Miscellaneous Display enhanced user data You can display details on a user for the user IDs (for example Created By) in the user interface in the Interaction Center for Financial Customer Care even if the user is not known in the CRM system. You can define which data is to be displayed in FI-CA event 2836. ______________________________________________________________ SAP AG 400 SAP-System ______________________________________________________________ - Fact sheets Display FI-CA data in an account or business agreement overview Alerts Convert FCC alerts to the new CRM Alert Framework User interface Convert FCC interfaces to the new CRM WebClient user interface For further information on converting the user interface, see the release note Uniform User Interface in CRM (New). Financial Customer Care As Frontend for FI-CA Collections Management Display and edit worklists and work items Display, create, and change promises to pay Display collection fact sheet, display collection-relevant data Display a customer's collection history and details of the objects it contains For further information on Collections Management in SAP FI-CA, see the SAP ERP 6.0 Enhancement Package 2 release note Collections Management in the ERP system. Financial Customer Care Integration with Adjustment Request and Dispute Management You can integrate Dispute Management with Financial Customer Care. For further information on Dispute Management in SAP CRM 2007, see the release note New Functions in the Provider Contract and Dispute Management. Credit Management Integration You can integrate the Financial Customer Care Interaction Center with various credit management systems. The following functions are available in each case: SAP Credit Management (FIN-FSCM-CR) in SAP ERP Central Component (SAP ECC); the two systems are connected using SAP NetWeaver - Exchange Infrastructure (XI) Credit Management (FI-AR-CR, SD-BF-CM) in SAP ECC External credit management system connected using XI External credit management system not connected using XI If you use SAP Credit Management (FIN-FSCM-CR) or another external credit management system that is connected using XI, the following functions are available: Display and use a business partner's credit risk rating Automatic credit check and commitment notification Process transactions with credit locks If you use Credit Management (FI-AR-CR, SD-BF-CM) in SAP ECC, the following checks are available: Business partner valuation and credit rating check in SAP CRM Automatic credit check and commitment notification Process transactions with credit locks If you use an external credit management system that is not connected to SAP CRM using XI, the ______________________________________________________________ SAP AG 401 SAP-System ______________________________________________________________ automatic credit limit check and commitment notification functions are available. For further information on Credit Management integration, see the SAP Library documentation on SAP CRM 2007 on the SAP Help Portal at http://help.sap.com -> Documentation -> SAP Business Suite -> SAP Customer Relationship Mgmt. -> SAP CRM 2007 -> Components and Functions -> Basic Functions -> Credit Management. Effects on Customizing For further information on Customizing and on how to configure this business scenario, see SAP Solution Manager. See also For further information on the functions in the individual business processes in the business scenario Financial Customer Care & Dispute Management, see the SAP Library documentation on SAP CRM 2007 on the SAP Help-Portal at http://help.sap.com -> Documentation -> SAP Business Suite -> SAP Customer Relationship Mgmt. -> SAP CRM 2007 -> Components and Functions -> SAP CRM for Industries -> Telecommunications Industry -> Functions in the Interaction Center for Financial Customer Care. 1.34.3 Financial Customer Care for Insurance (Enhanced) Use This release note is only relevant if you are upgrading from CRM 5.0. Refer also to the release note for Financial Customer Care, which also applies to this industry variant. As of SAP CRM 2007, the business scenario contains the following process: Account Identification If you are implementing SAP ERP 6.0 with Enhancement Package 3 in the back-end system, you can call the transaction for editing the insurance object after the insurance object has been confirmed. Effects on Customizing For more information about Customizing and configuration of this business scenario, refer to SAP Solution Manager. ______________________________________________________________ SAP AG 402 SAP-System ______________________________________________________________ 1.34.4 CRM-IT-CI Billing 1.34.4.1 Dispute Management (Enhanced) Use As of CRM 5.1, you can use dispute management to create adjustment requests for invoices, invoice items, or event detail records (EDRs). Previously, you could do this for invoices only. In addition, you can do the following: Search for invoices and EDRs in an external system Display invoices and EDRs originating from an external system Effects on Customizing You make settings for dispute management in Customizing for Customer Relationship Management (CRM), by choosing Industry-Specific Solutions -> Telecommunications -> Dispute Management. 1.35 CRM-IU 1.35.1 CRM-IU-IC Utilities Industry Utilities Industry: Interaction Center 1.35.1.1 Financial Customer Care and Dispute Management (Enhanced) Use This release note is only relevant if you are upgrading your system from SAP CRM 5.0. The business scenario includes the following new or enhanced processes: New with SAP CRM 5.2 or SAP CRM 2007: Note: All the functions listed here require SAP FI-CA based on SAP ERP 6.0 Enhancement Package 2 at the lowest as the back-end system. However, SAP ERP 6.0 ist still supported as the back-end system. For further information on release dependency, see SAP notes 1075410 and 746475. ______________________________________________________________ SAP AG 403 SAP-System ______________________________________________________________ Payments in the Interaction Center for Financial Customer Care Maintain payment methods If you use SAP ERP 6.0 Enhancement Package 2, the payment methods are no longer defined in the FI-CA profile for the user role but in SAP FI-CA. You can define the payment methods for each country for the following payment types: Payment Installment plan Promise to pay Payment specification or payment request Payment requests Grouping of items for which payment orders are to be made to form one payment request in the ERP system Payment specification Grouping of items in a payment specification in the ERP system - Installment Plan You can define payment data for installment items. Payment Search As of SAP ERP 6.0 Enhancement Package 2, you can restrict a payment search to a certain number of payments. You can also limit the maximum number of payments on which the search is to be run. This allows you to avoid long waits when executing the search. You can define standard values for this function in Customizing for the FI-CA profile. The agent can adjust these parameters on the interface for the payment search. Account Balance Display new flexible FI-CA balances Display configurable additional data Enhanced support for contract data in the account balance Display processing locks for contracts Dunning history Display collection strategy and collection step Payment Data You can define bank details for a specific period in a business partner's payment data. Miscellaneous Display enhanced user data You can display details on a user for the user IDs (for example Created By) in the user interface in the Interaction Center for Financial Customer Care even if the user is not known in the CRM system. You can define which data is to be displayed in FI-CA event 2836. Fact sheets Display FI-CA data in an account or business agreement overview - ______________________________________________________________ SAP AG 404 SAP-System ______________________________________________________________ - Alerts Convert FCC alerts to the new CRM Alert Framework User interface Convert FCC interfaces to the new CRM WebClient user interface For further information on converting the user interface, see the release note Uniform User Interface in CRM (New). Financial Customer Care As Frontend for FI-CA Collections Management Display and edit worklists and work items Display, create, and change promises to pay Display collection fact sheet, display collection-relevant data Display a customer's collection history and details of the objects it contains For further information on Collections Management in SAP FI-CA, see the SAP ERP 6.0 Enhancement Package 2 release note Collections Management in the ERP system. Financial Customer Care Integration with Adjustment Request and Dispute Management You can integrate Dispute Management with Financial Customer Care. For further information on Dispute Management in SAP CRM 2007, see the release note New Functions in the Provider Contract and Dispute Management. Credit Management Integration You can integrate the Financial Customer Care Interaction Center with various credit management systems. The following functions are available in each case: SAP Credit Management (FIN-FSCM-CR) in SAP ERP Central Component (SAP ECC); the two systems are connected using SAP NetWeaver - Exchange Infrastructure (XI) Credit Management (FI-AR-CR, SD-BF-CM) in SAP ECC External credit management system connected using XI External credit management system not connected using XI If you use SAP Credit Management (FIN-FSCM-CR) or another external credit management system that is connected using XI, the following functions are available: Display and use a business partner's credit risk rating Automatic credit check and commitment notification Process transactions with credit locks If you use Credit Management (FI-AR-CR, SD-BF-CM) in SAP ECC, the following checks are available: Business partner valuation and credit rating check in SAP CRM Automatic credit check and commitment notification Process transactions with credit locks If you use an external credit management system that is not connected to SAP CRM using XI, the automatic credit limit check and commitment notification functions are available. For further information on Credit Management integration, see the SAP Library documentation on SAP ______________________________________________________________ SAP AG 405 SAP-System ______________________________________________________________ CRM 2007 on the SAP Help Portal at http://help.sap.com -> Documentation -> SAP Business Suite -> SAP Customer Relationship Mgmt. -> SAP CRM 2007 -> Components and Functions -> Basic Functions -> Credit Management. Effects on Customizing For further information on Customizing and on how to configure this business scenario, see SAP Solution Manager. See also For further information on the functions in the individual business processes in the business scenario Financial Customer Care & Dispute Management, see the SAP Library documentation on SAP CRM 2007 on the SAP Help-Portal at http://help.sap.com -> Documentation -> SAP Business Suite -> SAP Customer Relationship Mgmt. -> SAP CRM 2007 -> Components and Functions -> SAP CRM for Industries -> Telecommunications Industry -> Functions in the Interaction Center for Financial Customer Care. 1.35.1.2 Financial Customer Care for Insurance (Enhanced) Use This release note is only relevant if you are upgrading from CRM 5.0. Refer also to the release note for Financial Customer Care, which also applies to this industry variant. As of SAP CRM 2007, the business scenario contains the following process: Account Identification If you are implementing SAP ERP 6.0 with Enhancement Package 3 in the back-end system, you can call the transaction for editing the insurance object after the insurance object has been confirmed. Effects on Customizing For more information about Customizing and configuration of this business scenario, refer to SAP Solution Manager. ______________________________________________________________ SAP AG 406 SAP-System ______________________________________________________________ 1.36 CRM-MW 1.36.1 CRM-MW-MON Middleware Monitoring 1.36.1.1 Data Integrity Manager (Enhanced for SP02) Use The Data Integrity Manager (DIMa) is a tool that helps you detect and repair inconsistencies between objects across components within the SAP CRM system landscape. As of Release CRM 2007 SP02: You can use accelerated data extractors for the following business objects: Customer Contacts Material master Service master Business partner Business partner relationships Partner functions Sales documents (Quotes and Orders) Sales contracts You can filter contacts based on the sales area of the customer. For example, extract only contacts for customers with sales area values VKORG, VTWEG, SPART; filtering is possible for single values also. You can directly navigate to the monitoring transactions R3AR2 and R3AR3 after the creation of DIMa requests. You can manually number DIMa requests. - ______________________________________________________________ SAP AG 407 SAP-System ______________________________________________________________ 1.36.2 CRM-MW-GWI Groupware Integration 1.36.2.1 Migration of GWI Data from the Java-Based MapBox to the ABAP-Based MapBox (New) Use This release note is only relevant if upgrading from SAP CRM 5.0. In server-based Groupware integration, you can perform data conversion of BDoc messages to the standard Groupware formats (iCalendar and vCard) by using the ABAP-based MapBox. The ABAP-based MapBox framework thereby replaces the Java-based MapBox framework and is completely integrated in the CRM server. If you use the Java-based MapBox, you can migrate your data to the ABAP-based MapBox. It is therefore no longer necessary to separately install the Java MapBox or the SAP NetWeaver Application Server Java, and so you can considerably reduce installation- and support effort for server-based Groupware integration. This data migration is largely based on the conversion of XML data in DDIC structures. The Userlist data and BUPA (business partner relevant) data are transferred from table MDMANDTSTORE, used by the Java-based MapBox, to tables CRMD_MBA_GUISTOR and CRMD_MBA_MSGSTOR. To process the migration you call transaction MIGRATE. An application opens in which you can choose whether you want to migrate activities or business partners as well. You can either transfer all activities or just activities within a defined period. If you want to migrate activities, you must also select the Userlist indicator. Otherwise, you cannot synchronize the activities with the Groupware system. Note: After the data migration (transaction MIGRATE), you must perform an initial load for all Customizing objects. 1.37 CRM-CA CRM Cross-Application Components 1.37.1 Survey Suite (Enhanced) Use This release note is relevant if upgrading from SAP CRM 5.0 or from SAP CRM 5.2. The Survey Suite is available for the following roles: ______________________________________________________________ SAP AG 408 SAP-System ______________________________________________________________ - Marketing Professional Service Professional Sales Professional The Survey Suite has been enhanced with the following features: Search The Search function has been enhanced so you can select search criteria from dropdown lists. You can add or remove selection criteria to refine your search. Editable overview page You can use the editable overview page to edit the details of existing surveys. 1.37.2 Multilevel Categorization (Enhanced) Use This release note is only relevant if upgrading from SAP CRM 5.0. Multilevel categorization has been enhanced to include flexible category labels. You can now customize the labels of the categories you have defined in the category modeler to suit your business needs. Once you have defined the labels in Customizing, you can then assign your new label texts to different category levels using the Categorization Schema in the Interaction Center WebClient under the IC Manager role. Effects on Customizing You can define the categorization labels in Customizing for SAP CRM by choosing Customer Relationship Management -> CRM Cross-Application Components -> Multilevel Categorization -> Define Categorization Labels. ______________________________________________________________ SAP AG 409