C38_BPP_EN_DE

SAP CRM 7.0

September 2010

English

Complaints and Returns Management (C38)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices Complaints and Returns Management (C38) - BPD

Copyright

© 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 16


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents

1 Purpose.................................................................................................................................. 5

2 Prerequisites........................................................................................................................... 5

2.1 Master Data and Organizational Data.............................................................................5

2.2 Preceding Process..........................................................................................................6

2.3 Roles............................................................................................................................... 6

2.4 Preliminary Steps............................................................................................................6

2.4.1 Log on to CRM WebClient UI...................................................................................6

3 Process Overview Table.........................................................................................................8

4 Process Steps........................................................................................................................ 9

4.1 Create Complaint............................................................................................................9

4.2 Create Credit Memo......................................................................................................10

4.3 Create Return Request..................................................................................................10

4.4 Complete Complaint......................................................................................................11

4.5 Create Billing Document (ERP).....................................................................................11

4.6 Check Return Request (ERP).......................................................................................12

4.7 Process Delivery (ERP).................................................................................................12

4.8 Process Goods Receipt (ERP)......................................................................................14

4.9 Process Goods Movement (ERP).................................................................................15

4.10 BI Reporting...............................................................................................................16



Complaints and Returns Management

1 PurposeThe purpose of this document is to describe how a customer complaint is processed within your sales and service organizations. A complaint is an expression of dissatisfaction that a customer makes in relation to a service or product.

This document summarizes several activities in a logical sequence. Generally, the completion of one activity is the prerequisite for the next activity. Depending on the configuration carried out in your project, some titles of tab pages and screen elements might appear differently to the description in this document.

2 Prerequisites

2.1 Master Data and Organizational Data

UseEssential master and organizational data were both created in and/or replicated to your CRM system during the implementation phase, such as the data that reflects the organizational structure of your company and master data that suits its operational focus, for example, master data for materials and customers.

Use your own master data (or the following Baseline Package scenario data listed below if you have installed an SAP Best Practices Baseline Package) to go through the business process procedure:

Master / org. data

Value Master / org. data details

Comments

Sold-To Party 100000 Customer Domestic 00

Contact Person Monika Ziegler

Installed Base YBP_IB01 Best Practices IBase 01

External ID

Component <No of installed base component for <Product>>

PC Standard External ID

Product H11 Trading Good... PC Standard

Contract <number of newly created service contract>

Contract assigned to <Component> (for contract creation: see the Configuration Guide of building block C26 - CRM Service).

Warranty BP_WTY BP Warranty Time Dependent



2.2 Preceding Process

UseThe scenario described in this Business Process Documentation is part of a bigger chain of integrated scenarios. So, you have the option of first completing the following business processes and conditions before you start any activities in this scenario:

Business condition Scenario

A number of complaints that might have been created by a customer using the Internet Customer Self Service (ICSS) can now be further processed.This scenario would then start with process step Complete Complaint.

E-Service: Complaints and Returns Management (C76)

2.3 Roles

UseThe following roles must have been created in order to test this scenario using the SAP CRM WebClient UI. The roles in this Business Process Documentation need to be assigned to the system user(s) testing this scenario.

(1) Log on to the CRM WebClient UI with the following users:

System User Business Role Bus. Role ID Employee Password

SERV_EMPL BP Service Employee BP_SRV_EMPL Barbara Lee welcome

SERV_MAN BP Service Manager BP_SRV_MAN Ryan Reval welcome

If the password is invalid, try the password initial.

(2) Log on to the ERP system with the following user:

System User Employee Password

SERV_EMPL Barbara Lee welcome

(3) Log on to the BW system with any valid user.

2.4 Preliminary Steps

2.4.1 Log on to CRM WebClient UI

UseThe purpose of this activity is to describe how the service employee gets first-time access to the SAP CRM WebClient UI. There are two options: Access from SAPGUI or via URL.



PrerequisitesThe appropriate SAP CRM WebClient role for the service employee has been assigned to the service employee user (SERV_EMPL) in the CRM system.

Procedure1. Close all open browser windows.

2. Access the SAP CRM WebClient UI:

Option 1: Access from SAP GUI via Transaction:1. In the input field for transactions, enter transaction CRM_UI and press Enter.

Option 2: Access from SAP GUI via BSP Application:1. Log on to the CRM system with the user for the BP Service Employee.

2. From the SAP menu, choose Favorites. From the context menu, choose Add Other Objects.

3. Select URL type BSP Application.

4. Enter the following data:

Field name User action and values

BSP Applicat. CRM_UI_START

Description CRM WebClient UI

Start Page default.htm

5. Choose Continue:

6. Choose CRM WebClient UI from the Favorites.

7. In the dialog box SAP Web Application Server; enter the following data and choose OK:


User name SERV_EMPL

Password welcome

Option 3: Access via URL:The CRM WebClient UI can also be accessed using a Uniform Resource Locator (URL). The CRM WebClient UI URL has the following structure (default configuration):

http://<Host Name>.<Domain Name>.<Extension>:<Port Number>/sap/crm_logon?sap-client=<client number>

For example: http://uxcirsz.wdf.sap.corp:50028/sap/crm_logon?sap-client=100

Host Name, Domain Name and Extension can be derived from the message server of the underlying CRM system.

The port can be determined as follows:

1. Call transaction SMICM.

2. Choose Goto Services.

3. From the Active Services list, choose the port for the HTTP service.



ResultYou have entered the SAP CRM WebClient user interface as BP Service Employee with user SERV_EMPL.

3 Process Overview TableProcess step Business condition Business role Expected resultsCreate Complaint Service Employee Complaint

Create Credit Memo Complaint Service Employee Credit Memo Item

Create Return Request Complaint Service Employee Return Request Item

Complete Complaint Complaint Service Employee Released Complaint Items

Create Billing Document (ERP)

Released Complaint Service Employee Billing Document

Check Return Request (ERP)

Return Request in ERP Service Employee

Process Delivery (ERP) Return Request in ERP Service Employee Inbound Delivery

Process Goods Receipt (ERP)

Inbound Delivery Service Employee Goods Issue

Process Goods Movement (ERP)

Goods Issue Service Employee Material Movement

BI Reporting Complaints Service Manager Service Quality Analysis



4 Process Steps

4.1 Create Complaint

UseYou can display the whole complaints process within your company, from the receipt of a complaint, the technical analysis, as well as ongoing tasks and activities, right up to the preparation of statistical analysis.

PrerequisitesAll necessary configuration steps have been carried out.

A <Contract> has been created and both a corresponding Installed Base <Component> for a <Product> and at least one service product have been assigned (for contract creation: see the Configuration Guide of building block C26 - CRM Service).

Make sure that in the ERP back-end client the descriptions of all objects, which are relevant for copying the complaint document into ERP (for example, transaction types, item categories, divisions etc.), have been maintained for the language used.

You are logged on to the CRM WebClient UI with user serv_empl and password welcome.

Procedure1. Access the transaction choosing one of the following navigation options:

SAP CRM WebClient menu Complaints & Returns Create: Complaint

2. In the appearing web dialog box select transaction type BP Complaint if necessary.

3. In assignment block Complaint Details enter following data:

Field name User action and values Comment

General Data

Description Product defective Any order description

Sold-To Party <Sold-To Party> In the appearing web page dialog select Service Organization BP Service Back Office if necessary.

Contact <Contact Person> If not prefilled

Employee Responsible 10210 Barbara Lee

4. Press Enter.

You can use button Personalization from the application toolbar in order to adapt the screen. In the Personalization web page dialog, you can select and deselect all available assignment blocks that are available for your overview screen (for example, Organizational Data).

You can also directly maintain all necessary organizational units for Sales and Service in assignment block Organizational Data.



5. In assignment block Items, enter the following data:

Field name User action and values Comment

Product ID <Product>

Quantity 1

6. Press Enter.

7. On the new item entry choose action Edit.

8. Check the entry for the <Warranty> being determined.

ResultThe complaint is now prepared to create both a credit memo and a return request.

4.2 Create Credit Memo

UseYou can create a credit memo request if customers are charged too much, a defective product has been delivered, or a complaint is made about a bad service performed.

By creating a credit memo, the system replicates the billing-relevant item of the complaint to the billing due list of the ERP backend system.

Procedure1. In assignment block Complaint Item Details choose Credit Memo from the application

toolbar.

ResultA credit memo request has been created as a new complaint item.

4.3 Create Return Request

UseYou can create a return request if the customer wants to return a defective product.

In the ERP backend system a return delivery will be created for the return request item created in the CRM system.

Procedure1. In assignment block Complaint Item Details choose Returns from the application toolbar.

2. Choose Back.

ResultOn the complaint header level in assignment block Items, you can see that two new items have been added.



Note that the two created items will be handled differently in the ERP system . The return item will be processed in the returns delivery, whereas only the credit item will be processed in the billing document (credit memo).

4.4 Complete Complaint

Procedure1. In assignment block Items, switch the status of the complaint item to Released.

The status of the other items switches to Released automatically.

2. Choose Save and take a note of the complaint document’s number:

___________________________

3. You can now log off the CRM WebClient UI as service employee.

ResultYou have created a complaint document. Check that the document is free of errors in order to proceed with the next steps.

4.5 Create Billing Document (ERP)

UseWith this step an invoice document is created in SAP ERP based on the new complaint’s credit memo item.

Procedure1. Log on to the ERP backend system with system user serv_empl (Barbara Lee) and

password welcome.

2. To prepare the invoice, access the billing due list choosing one of the following navigation options:

Transaction code VF04

SAP ERP menu Logistics Sales and Distribution Billing Billing Document Process Billing Due List

3. On tab Selection in screen area Documents to be selected select checkbox Order-related.

4. Choose Display billing list (F8).

5. Highlight the entry of the new complaint document and choose Collective billing doc./online.

6. The screen switches to Credit Memo (G2) Create: Overview of Billing Items (with temporary document number $000000001).

7. Check the billing items.Double-click the item to change values afterwards.

8. Choose Save.



9. The document status switches to Document Successfully Processed.

Note down the document number displayed as a system message in the status bar for further reference:

_________________________________________

Note that the returns item with item category REN is not processed in the credit memo.

4.6 Check Return Request (ERP)

UseAfter the complaint items have been transferred to the ERP system, order processing is finished there. You can view the document, check the document flow, and create follow-up documents (for example, delivery, billing document).

PrerequisitesYou have created a return request before (the customer wants to return the sold and delivered product) by generating the action Returns within the complaint document.

The document has been saved without errors in order to be transferred to the corresponding ERP system. No distribution lock has been set for the document.

The system should have created a return request for the sales item with the same number as the complaint in CRM.

You are logged on to the corresponding ERP system with user serv_empl and password welcome.

Procedure1. Access the transaction choosing one of the following navigation options:

Transaction code VA03

SAP ERP SAPGUI menu Logistics Sales and Distribution Sales Order Display

2. Enter the order number (same number as the complaint created in the CRM system) and press Enter.

3. The system has created a return request for the sales item (item category REN).

4.7 Process Delivery (ERP)

UseWithin the complaint process it is possible to create return deliveries for a product that have been complained about by the customer.

Only return requests and substitute delivery items (REN and TANN respectively) are replicated to the ERP system.



Only one complaint/return document is replicated to the ERP system even if the complaint/return contains different items. This is because the ERP document is used primarily to trigger subsequent logistics processes

The ERP system transfers some logistical information back to the CRM Server so that you can display the following for a complaint/return:

Status information (return/substitute delivery is shipped/partially shipped)

Document flow (shipping, goods issue/receipt)

Quantity delivered

You can only make changes to return items/substitute deliveries in the system in which they were created

In the CRM system you can change documents for which data has already been transferred. Your changes are then transferred automatically to the ERP system

Create a return delivery as a follow-up document of the return request.

PrerequisitesA complete and error free sales document with sales item (return) must be available before a delivery document can be created.

Procedure1. Create a Return Delivery as follow-up activity from the sales document or use the following

navigation options:

Transaction code VL01N

SAP ERP menu Logistics Logistics Execution Inbound Process Goods Receipt for Inbound Delivery Inbound Delivery Create Customer Returns

2. Select the required data in the screen:

Field name Field Entry

Shipping point <Shipping point (e.g. 1000)>

Selection date <Date (e.g. today)>

Order <Order number (of new complaint)>

3. Press Enter.

You can also create a return delivery directly from the document display (transaction VA03) using the following menu path:Sales document Deliver

4. Save your entries.

5. Note the number of the newly created inbound delivery document:

_______________________

6. Choose Back.



ResultThe system contains a complete delivery document (inbound delivery - although the term in the system is called ‘outbound delivery’!).

4.8 Process Goods Receipt (ERP)

UseThe customer has sent back the defect product and you want to enter the material back in stock. Therefore we have to post a ‘goods receipt’.

PrerequisitesAn inbound delivery document has been created before.

Procedure1. To post a goods receipt access the transaction, choose one of the following navigation

options:


SAP ERP menu Logistics Logistics Execution Inbound Process Goods Receipt for Inbound Delivery Inbound Delivery Change Customer Returns

2. Enter the inbound delivery number created in the step before (‘8xxxxxxx’).

3. Press Enter.

4. Choose Post Goods Receipt.

5. The system responds with the message Returns Delivery 8xxxxxxx has been saved.

If you get an error message that posting is not possible in the current period for company code 1000, you need to run the period closing program:

Transaction code MMPV

Enter the following values and choose Execute:


From company code 1000

Period <current month, e.g. 03 for March>

Fiscal year <current year>

ResultThe goods receipt for the delivery has been posted.



4.9 Process Goods Movement (ERP)

UseA physical movement of materials (e.g. return of product) means a change in stock levels.

PrerequisitesAn inbound delivery with posted goods issues has been created.

Procedure1. To change the Inbound Delivery, access the transaction by choosing one of the following

navigation options:


SAP ERP menu Logistics Logistics Execution Inbound Process Goods Receipt for Inbound Delivery Inbound Delivery Change Customer Returns

2. Enter the inbound delivery number created before and choose Enter.

3. To check the previously created documents choose Document Flow in the application toolbar.

4. You will find entries for:

BP CRM Complaint <no>

Returns Delivery <no>

GD ret.del. returns <no>

5. Highlight the line GD ret.del. returns <no> and choose button Display document.

6. You will be switched to transaction MB03 (display material document).

7. Find the document which was created for your goods receipt.

8. Highlight the item for the material and choose Details from Item.

9. Ensure that the material document shows correct entries (e.g. concerning movement type, quantity, storage location, etc.).

ResultThe material movement took place and the product is back in stock (check transaction MMBE for <Product> and <Plant>).



4.10 BI Reporting

UseThis section describes which reports exist for Complaints and Returns Management and briefly describes the content of the reports.

For an overview of how to navigate within the reports, refer to the Business Process Documentation (User Guide) of the relevant BI Analytics scenario.

PrerequisitesYou have implemented the BI Analytics scenario.

Opening the reports from the WebClient UI is only possible if you have carried out all the necessary configuration steps described in the BS4 Basic Configuration CRM Analytics Configuration Guide.

Alternatively you can log on to the BI system and open the business user role I15_03U. In this business user role you will find a broad range of BI reports for all areas.

Procedure1. Log on to the CRM WebClient UI as service manager with user serv_man and password

welcome.

2. In the Work Center Link Group Reports you can find the available reports. Choose the report you want to display.

From the WebClient UI the following BI reports are available for Complaints and Returns Management:

Complaint Ratio by Product:

This query shows the service products with the highest complaint ratio.

Number of Service Complaints:This query shows the reasons for service-related complaints, and the number of complaints made.
