configuration guide for sap dispute management for fi-ar

PUBLICDocument Version: SAP S/4HANA 1809 – 2018-08-09

Configuration Guide for SAP Dispute Management for FI-AR

© 2

018

SAP

SE o

r an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 SAP Dispute Management Configuration Guide for FI-AR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 SAP Dispute Management for FI-AR (FIN-FSCM-DM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 Documentation Landscape for SAP Applications and Business Scenarios . . . . . . . . . . . . . . . . . . . . . 61.3 See Also. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4 System Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

One System and Multiple-System Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.5 Business Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Customizing for Dispute Case Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Customizing of the Process Integration with Accounts Receivable . . . . . . . . . . . . . . . . . . . . . . . 28

1.6 SAP Dispute Management Authorization Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Mapping Separate Organizational Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

2 P U B L I CConfiguration Guide for SAP Dispute Management for FI-AR

Content

1 SAP Dispute Management Configuration Guide for FI-AR

Purpose

This configuration guide applies to the business process FI-AR: Dispute Resolution with the corresponding release of the related SAP application components. You can find more information on this on SAP Help Portal under Product Lifecycle Mgmt SAP Apparel and Footwear SAP Apparel and Footwear 6.4 FI-AR: Dispute Resolution

CautionNote that you can only use specific functions of the component SAP Dispute Management if you have activated the following business functions:

In the dispute case processing system

● FSCM, Enablement of Financial Shared Services (FIN_FSCM_SSC_AIC_1)● FSCM Functions 3 (FIN_FSCM_CCD_3)● FSCM Functions 2 (FIN_FSCM_CCD_2)● FSCM Functions (FIN_FSCM_CCD)

In the Accounts Receivable System (FI-AR)

● FSCM Integration 2 (FIN_FSCM_CCD_INTEGRATION)● FSCM Integration (FIN_FSCM_INTEGRATION)

For more information about the business functions, see transaction SFW5, which you can access from the first node in Customizing of the respective SAP system.

Contents

The configuration guide describes which Customizing structures and activities you have to process to implement the business process. For more information about these structures, see Business Customizing [page 14].

NoteYou can find information on the individual activities in Customizing of your SAP system. This configuration guide provides additional contexts and background that may be useful for Customizing.

Configuration Guide for SAP Dispute Management for FI-ARSAP Dispute Management Configuration Guide for FI-AR P U B L I C 3

Target Audience

● Technical consultants● Application consultants● Project team members during the implementation of an SAP solution● IT department of the SAP customer

Integration

Documentation Landscape of SAP Solutions, Business Scenarios, and Business Processes

The system landscape has already been set up using the Master Guide and other documentation. For information on further documentation and where the latest versions are published, see Documentation Landscape of SAP Solutions and Business Scenarios [page 6].

Feedback on Configuration Guide

We would appreciate your feedback with a view to continually improving the usefulness of this configuration guide. If you find errors in the configuration guide, please enter a message for the component Dispute Management (FIN-FSCM-DM) in SAP Service Marketplace at service.sap.com/message.

1.1 SAP Dispute Management for FI-AR (FIN-FSCM-DM)

Purpose

This component contains functions for processing receivables-related dispute cases. It supplements the logistics process chain Purchase Order – Delivery – Invoice – Payment in the stage between invoice and payment if there are discrepancies with the customer.

Implementation Considerations

In business relationships, business partners frequently reduce the amounts of payments. These reductions have usually not been agreed with the payment recipient and therefore, the payment recipient has to investigate and resolve them.

SAP Dispute Management is therefore particularly interesting if one or more of the following factors apply to your company:

● Numerous underpayments by customers● Long processing times for these cases● Complex company and communication structure


SAP Dispute Management Configuration Guide for FI-AR

As coordinator for dispute cases, the component enables you to structure your investigations, and to distribute and manage the results for all parties involved in your company.

Integration

SAP Dispute Management for FI-AR (FIN-FSCM-DM) is part of SAP Financials Financial Supply Chain Management and consists of two subareas:

● Dispute Case Processing● Process Integration of Dispute Case Processing with Accounts Receivable

Integration with Other SAP Components

Function Required Required Component Integration Obligatory

Create dispute cases from accounting Accounts Receivable(FI-AR) from SAP R/3 4.6C

Yes

Links to documents from accounting

Links to the business partner (customer) from accounting

Update attributes in accounting document

Accounts Receivable Accounting (FI-AR) from Enhancement Package 2 for SAP ERP 6.0

No

Link billing documents with the dispute cases

● Sales and Distribution (SD)● Customer Relationship

Management (CRM)

No

Create dispute cases from SAP Biller Direct

SAP Biller Direct(FIN-FSCM-BD) from Release 3.0

No

Create dispute cases from SAP Collections Management

SAP Collections Management(FIN-FSCM-COL) from Release 3.0

No

Consider dispute cases to be collected in the collection strategy

SAP Collections Management(FIN-FSCM-COL) from Release 6.0

No

Analyze data from SAP Dispute Management

SAP Business Information Warehouse (SAP BW) from Release 3.2

No

Work center for dispute manager SAP NetWeaver Portal from Release 7.0 or SAP NetWeaver Business Client from Release 7.0

No

Create claims submissions as dispute cases

CRM Claims Management (CRM-CLA) from Release SAP CRM 2007

No


Function Required Required Component Integration Obligatory

Use SAP Dispute Management from the Interaction Center of SAPCustomer Relationship

SAP Customer Relationship Management (CRM) from SAP Enhancement Package 1 for SAP CRM 7.0

No

NoteIf you use SAP R/3 4.6C, SAP R/3 Enterprise 4.70 , or mySAP ERP 2004 for your Accounts Receivable Accounting, accounting and dispute case processing are in different systems.

If you use SAP ERP 6.0 or a later release for your Accounts Receivable, then you can run accounting and dispute case processing in one system or in different systems.

For more information about the multiple system scenario, see the SAP Dispute Management Configuration Guide for FI-AR . You can view the configuration guide as a PDF file on SAPService Marketplace at service.sap.com/fscm . Choose SAP Dispute Management Media Library .

Features

In the case of an underpayment, you can create a dispute case in the system. Here you can collect all of the data and information required for processing the case. This involves data that already exists in accounting and new data that you enter for a dispute case.

During processing of a dispute case, you can use the functions for the workflow and for creating correspondence.

You can create a dispute case from the accounting transactions where you determine the underpayment, for example, postprocessing of an account statement or analysis of overdue open items. When you create the dispute case, the system copies information from the accounting document (for example, disputed amount ) into the dispute case automatically.

You can also create a dispute case in different accounting transactions and enter the customer-disputed amount as soon as a customer has notified a future payment deduction.

However, you can also create a dispute case independently of the transactions in accounting in dispute case processing .

1.2 Documentation Landscape for SAP Applications and Business Scenarios

This documentation gives you an overview of the most important sources of information that you need in connection with SAP applications, business scenarios, and business processes. Make sure that you always use the most up-to-date documents for your implementation.



Document Storage Location

Document Location

Master Guide, Installation Guide, and Upgrade Guide service.sap.com/instguides

Customizing SAP System

Business Scenario Description, Business Process Description

SAP Solution Manager

SAP Library help.sap.com

Comment: Also available under Help SAP Library in the SAP system

SAP Notes service.sap.com/notes to search for notes

service.sap.com/instguides listed by installation and upgrade guide

Platforms service.sap.com/platforms

Sizing service.sap.com/sizing

Security service.sap.com/security

Description of the Documents

● Master Guide, Installation Guide, and Upgrade GuideThese documents describe how you install or upgrade the system landscape required for a business scenario. The central initial access document for every SAP application is the Master Guide . For each business scenario, it lists the SAP application components and third-party applications required, and refers to their installation and upgrade guides. These guides are Component Installation Guides, Business Scenario Upgrade Guides, and Component Upgrade Guides.

● CustomizingThis tool enables you to adapt SAP systems to meet specific customer requirements. Customizing contains the Customizing activities for all SAP components with general documentation. The structure is component-oriented, and has no reference to a business scenario. If this reference is required, it is created as follows: By the configuration documentation, with a textual link to Customizing, and by the content of SAPSolution Manager that links to the Customizing activities for each business scenario and process.

● Business Scenario DescriptionThis document describes how a business scenario runs once all components have been installed and configured. For each business process of a business scenario there is a business process description and a component view as graphical representation. This shows the process steps in the respective SAP component.

● SAP LibraryThis documentation describes the different SAP components.


1.3 See Also

Use

The following list contains information that could be useful during configuration:

See Also

Documentation in SAP Library

In SAP Help Portal, Internet address help.sap.com: SAP

Solutions SAP ERP SAP ERP Central Component SAP

ERP Enhancement Packages . Choose the release and the language.

SAP Dispute Management SAP ERP Central Component Financials SAP

Financial Supply Chain Management (FIN-FSCM) SAP

Dispute Management for FI-AR (FIN-FSCM-DM)

Contains link to Case Management

Business Content of SAP Dispute Management SAP NetWeaver Library SAP NetWeaver by Key

Capability Information Integration by Key Capability BI

Content Financials SAP Financial Supply Chain

Management SAP Dispute Management (FIN-FSCM-

DM) .

Work Center for Dispute Manager Cross-Application Functions in SAP ERP Roles

Business Packages (Portal Content)

Application Link Enabling (ALE) SAP NetWeaver Library Application Link Enabling (ALE)

SAP NetWeaver by Key Capability Application Platform

by Key Capability Platform-Wide Services Connectivity

Components of SAP Communication Technology Classic

SAP Technologies (ABAP) IDoc Interface/ALE

Introduction Application Link Enabling (ALE)



Documentation in SAP Library

In SAP Help Portal, Internet address help.sap.com: SAP

Solutions SAP ERP SAP ERP Central Component SAP

ERP Enhancement Packages . Choose the release and the language.

Use of SAP Dispute Management from the Interaction Center of SAP Customer Relationship Management

SAP Business Suite SAP Customer Relationship

Management . Choose the release and the language under Application Help.

SAP Customer Relationship Management Interaction

Center Interaction Center WebClient Shared Services

Framework Integration with SAP ERP Accounting

Interaction Center Integration with SAP Dispute

Management

NoteFamiliarize yourself with the documentation landscape for SAP solutions, business scenarios, and business processes. For information on the type of documentation SAP provides and where the latest versions are published, see Documentation Landscape of SAP Solutions and Business Scenarios [page 6].

Caution

SAP Collections Management 6.05 is documented in Release SAP Enhancement Package 5 for SAP ERP 6.0 of SAP Library.


If you use a two-system scenario, note the following special features for the installation of your SAP Library:

Constellations in the two-system scenario

Variant Example System Software Release Relevant SAP Library

1 ACC (contains Accounts Receivable Accounting)

● SAP S/4HANA 4.6C● SAP S/4HANA Enter

prise 4.70● SAP S/4HANA 2004● SAP ERP 6.0● SAP Enhancement

Package 2, 3, or 4 for SAP ERP 6.0

● SAP S/4HANA 4.6C● SAP S/4HANA Enter

prise 4.70● SAP S/4HANA 2004● SAP ERP 6.0● SAP Enhancement

Package 2, 3, or 4 for SAP ERP 6.0Release SAP Enhancement Package 5 for SAP ERP 6.0 in SAP Library is not available in these systems.

DIS (contains SAP Dispute Management)

Financial Basis 6.05 ● SAP Enhancement Package 5 for SAP ERP 6.0If you want to access SAP Enhancement Package 5 for SAP ERP 6.0 in SAP Library in this system, install the corresponding documentation DVD for this system.

2 ACC (contains Accounts Receivable Accounting)

SAP Enhancement Package 5 for SAP ERP 6.0

● SAP Enhancement Package 5 for SAP ERP 6.0Release SAP Enhancement Package 5 for SAP ERP 6 in SAP Library is usually available in this system.

DIS (contains SAP Dispute Management)

Financial Basis 6.05 ● SAP Enhancement Package 5 for SAP ERP 6.0If you want to access SAP Enhancement Package 5 for SAP ERP 6.0 of SAP Library in this system, connect this system with the installed SAP Library.



1.4 System Connections

Purpose

This section contains information about connecting the systems in a SAP system landscape.

This involves, for example:

● Defining logical systems and assigning clients in the Online Transaction Processing System (OLTP)● Determining the systems, servers, clients, distribution models and so on, in the system in which the SAP

application component is installed● Completing the configuration settings and performing other activities required for the interactions in a SAP

system landscape

Procedure

Perform the steps in these guidelines in the sequence in which they appear.

1.4.1 One System and Multiple-System Scenario

Use

SAP Dispute Management consists of two subareas, Dispute Case Processing and Process Integration with Accounts Receivable. Both of these areas are delivered via separate software components and can be installed in separate systems, which means that you can use SAP Dispute Management as a one-system scenario or a multiple-system scenario.

If you use several accounts receivables systems, you can run Dispute Case Processing centrally in one system and integrate the different accounts receivable systems with this Dispute Case Processing.

Integration

If you use Accounts Receivable with SAP Dispute Management and with SAP Collections Management, the Dispute Case Processing of SAP Dispute Management must be in the same system as Collections Management.

Prerequisites

You have installed the relevant components for the required scenario.


Key Features

One-system scenario

You can use a one-system scenario if you use one accounts receivable system that you want to integrate with Dispute Case Processing using the process integration of SAP Dispute Management, and if this accounts receivable system has at least release status SAP ECC 6.0. In this case, you can run Dispute Case Processing in the system of your Accounts Receivable.

Multi-System Scenario

You use SAP Dispute Management as a multiple-system scenario in the following cases:

● You want to run Dispute Case Processing in a different system from Accounts Receivable.● The accounts receivable system is Release R/3 4.6C, SAP R/3 Enterprise 4.70, or SAP ECC 5.0. Due to the

different installation requirements of the software component containing Dispute Case Processing, you have to use a multiple-system scenario.

● You want to integrate several accounts receivable systems with Dispute Case Processing but run Dispute Case Processing centrally in one system. Dispute Case Processing can run in one of the accounts receivable systems concerned if this has at least release SAP ECC 6.0.

You integrate Dispute Case Processing and Accounts Receivable in a multiple-system scenario with the ALE scenario that SAP Collections Management provides (see Configuring the ALE Scenario [page 13]).

Example

You can create dispute cases in various transactions in Accounts Receivable and Dispute Case Processing. You can also process dispute cases in different ways. The following example shows the creation and processing of dispute cases in a multi-system scenario:

1. When posting incoming payments in the Accounts Receivable system, the Accounts Receivable accountant discovers an underpayment. He creates a residual item, and for this residual item, he creates a dispute case in the transaction Post Incoming Payment. He enters an SD employee as processor.When he posts the residual item, the dispute case is created in the Dispute Case Processing system.

2. In the Dispute Case Processing system, the SD employee sees the list of dispute cases to which he is assigned as processor. In this list, he also sees the dispute case created in step 1. He displays the dispute case, determines the telephone number of the contact person at the customer, and calls him. According to the customer, the goods were damaged on delivery, and he has deducted the amount of the damages from the payment.The SD employee checks this statement by calling the quality department. He receives confirmation of the customer's statement. He grants a credit in the amount of the invoice deduction, and documents the results in the dispute case. He defines Damaged goods as the reason, and enters a note.

3. The Accounts Receivable accountant checks the status of the dispute case. To do this, he calls the dispute case for the open residual items in the line item display.

4. The credit granted in SD is cleared with the residual item in Accounts Receivable. This clearing simultaneously updates the dispute case in Dispute Case Processing automatically. The disputed amount in the dispute case is now zero.

5. In Dispute Case Processing, the coordinator selects all remaining open dispute cases with a disputed amount of zero and closes them.



1.4.1.1 Configuring ALE Scenarios

Use

In order to implement SAP Dispute Management as a multi-system scenario, you have to make all the settings required for the ALE scenario of SAP Dispute Management in both the system for Dispute Case Processing, and in the Accounts Receivable systems involved.

Requirements

When you set up the RFC destinations for the ALE scenario, check whether the option of trust/trusting system relationship is relevant for you. Using an RFC trusted/trusting system relationship between two SAP systems means that in the case of an RFC (Remote Function Call) from the trusted to the trusting system, no password is sent for the logon to the trusting system. You can configure the RFC destinations in such a way that the call in the target system occurs with the current user from the calling system without a password being specified or entered on the logon screen. This has the following advantages, for example:

● When changes to objects or data are logged in the called system, this logging takes place with the current user from the calling system. This makes it easier to track changes that occurred through RFC.

● You can assign individual authorizations to the users in the called system. This means that you can differentiate which actions or functions are accessible to the user in the called system dependent on the user.

With this procedure, you must create the users that are to be allowed to execute using RFC functions in the called system as well. Note that in the ALE scenario of SAP Dispute Management, RFC calls take place from the Accounts Receivable system to the Dispute Case Processing system and vice versa. A trust relationship between SAP systems is not mutual. This means that you can choose whether one system is to be designated as trusted for the other system and vice versa, or whether you want to define the trust relationship only in one direction.

In the Customizing of ALE (Application Link Enabling), you can also define different RFC destinations for dialog calls, for BAPI calls, and for sending IDocs. As such you can also define an RFC destination for the dialog calls that use the trusted/trusting system relationship and use the current user from the calling system for the RFC calls in the target system, whilst you define an RFC destination for BAPI calls and for the sending of IDocs that does not use the trusted/trusting system relationship and in which you enter a communication user.

NoteNote the following if your Accounts Receivable system is known as a trusted system by the Dispute Case Processing system and you want to configure the RFC destination used for sending IDocs so that it uses the trusted/trusting system relationship and the RFC calls in the target system with the current user from the calling system:

Idocs are not only sent to the Dispute Case Processing when creating dispute cases from the Accounts Receivable system. When items are cleared in the Accounts Receivable system, the clearing of items is reversed or partial payments on items are executed that are included in a dispute case, IDocs are also sent to the Dispute Case Processing system. If the corresponding RFC destination uses the trusted/trusting system relationship and carries out the call in the target system with the current user from the calling system, this means that the user who executes the clearing, the reset of the clearing, or the partial


payment must also be created in the Dispute Case Processing system. You must therefore create all users who carry out clearing, resets of clearing, or partial payments in the Accounts Receivable system, and therefore affect dispute cases, in the Dispute Case Processing system.

For general information on the trusted/trusting system relationship, see the SAP Library, under SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Platform-Wide Services Connectivity Components of SAP Communication Technology Classical SAP Technologies (ABAP) RFC RFC Programming in ABAP Maintain Remote Destinations Trusted System: Trust Relationships between SAP Systems .

Procedure

In Customizing for Dispute Case Processing , perform the IMG activities under the node ALE Business Process . For more information on setting up the ALE scenario, see the documentation on these IMG activities.

CautionIn connection with the ALE scenario, see also the information in SAP Dispute Management Security Guide .

You can access the security guide on SAP Service Marketplace at service.sap.com/securityguide .

1.5 Business Customizing

Purpose

This section contains information about the Customizing settings in each system. Business Customizing adjusts the company-neutral functions delivered to the specific requirements of the company.

Process Flow

For the business Customizing for SAP Dispute Management, the SAP Implementation Guide (IMG) contains two structures that you have to process completely. These structures are in different systems if you use SAP Dispute Management in a multiple system scenario.



Structure System Menu Path

Dispute Case Processing System for Dispute Case Processing Financial Supply Chain Management

Dispute Management Dispute Case

Processing

Process Integration with Accounts Receivable Accounting

The Accounts Receivable (FI-AR) system

SAP S/4HANA 4.6C and 4.70:

Financial Accounting Accounts

Receivable and Accounts Payable

Financial Supply Chain ManagementSAP Dispute Management Process

Integration

As of SAP S/4HANA 2004:

Financial Supply Chain Management

Dispute Management Integration

with Accounts Receivable Accounting

NoteIf you use SAP Dispute Management in a multiple system scenario, first perform the settings for the ALE scenario for SAP Dispute Management before starting the business Customizing. For more information, see Configuring ALE Scenarios [page 13].

Regardless of whether you use SAP Dispute Management in a one-system or multiple system scenario, first configure the case types in the system for Dispute Case Processing before you start the Customizing of the process integration of SAP Dispute Management with Accounts Receivable Accounting.

For information about Customizing for the individual activities, see the IMG structures. The following sections of the configuration guide provide additional information to supplement the documentation in the IMG; this additional information does not replace the documentation in the IMG. The sections explain the relationships and background of business Customizing and should help you to adjust these to benefit your organization in the best possible way.

1.5.1 Customizing for Dispute Case Processing

Use

The following sections contain the special features for business Customizing for Dispute Case Processing.

NoteIf you have activated the business functions FSCM Functions (FIN_FSCM_CCD) and FSCM Integration (FIN_FSCM_INTEGRATION) and want to use the functions for Customer-Disputed Objects in Dispute Cases , you have access to standard Customizing in the form of the following Business Configuration Set (BC set): Dispute Cases with Customer-Disputed Objects (UDM_CUST_CDIS).


1.5.1.1 Creating a Records Management System (RMS).

Use

Using the Records Management System (RMS), you can define the visibility section in Dispute Case Processing of SAP Dispute Management.

Once you are in Dispute Case Processing you can choose the RMS in which you would like to work. You will then only be able to view the dispute cases that relate to this RMS. There is no cross-RMS search function for dispute cases in Dispute Case Processing. It is similarly not possible to use dispute cases or other elements of an RMS as linked objects in a dispute case relating to a different RMS.

If you are using several RMSs this will entail a relatively wide-ranging separation of data in Dispute Case Processing. It is not possible to subsequently merge the data of different RMSs into one RMS. Defining separate RMSs will as a result entail some loss of flexibility.

RecommendationYou can define one or more RMSs for SAP Dispute Management. However, in most cases it makes sense to define only one RMS for SAP Dispute Management.

Integration

The reports that you create in SAP NetWeaver BI can be cross-RMS.

The RMS is also involved in the definition of authorizations for a role. For more information, see Authorization Concept of SAP Dispute Management [page 37].

Activities

SAP Dispute Management delivers an RMS:UDM_DISPUTE. You can either use this RMS or create your own. It usually makes sense and saves effort when configuring the application to use the RMS UDM_DISPUTE that is delivered. If you want to use element types from the standard delivery you have to use RMS UDM_DISPUTE. For more information on creating element types, see Creating Element Types [page 17].

If you want to create your own RMS, in Customizing of Dispute Case Processing choose the Customizing activity Create RMS ID.



1.5.1.2 Creating Element Types

Use

For SAP Dispute Management , you need certain element types in the Dispute Case Processing system. When you create the element types, you define which types of elements can be used and which properties the individual element types have.

Element types are, for example:

● Dispute cases● SAP business objects (for example, line item, accounting document, account statement item, customer

billing document)● Documents● SAP ArchiveLink objects

Procedure

SAP Dispute Management delivers different element types. You can usually use these element types without changing them. In this way you reduce the effort needed to configure SAP Dispute Management . However, if you want to make changes to the element types delivered, copy them and then change your copy. Changing the template would be a modification.

NoteAlways use the element type delivered for the case record as a copy template and create your own element type for the case record. SAP reserves the right to make non-compatible changes to the element type deliverd for the case records.

Creating Element Types

In the Implementation Guide (IMG) for Dispute Case Processing , check which element types you need and create them.

Activity Menu Path

Create Element Type Element Types and Case Record Model Create

ElementType

Create Element Type for Case Record Element Types and Case Record Model Create Element

Type for Case Record

Create Element Type for Case Search Case Search Create Element Type for Case Search

For more information about creating the individual element types, see the documentation for the IMG activity in question.


1.5.1.3 Configuring Document Storage

Use

In SAP Dispute Management , you can save documents (for example, Word documents) as linked objects in the dispute case. These can be ArchiveLink documents, or documents that you file using the Knowledge Provider (KPro). If you store these documents using the Knowledge Provider , in a content model, configure whether these documents are to be saved in a content server or in the database of the SAP system. The content server can be SAP Content Server or a content server from another provider (archive system).

You define which content model you use for documents that you save as linked objects in the dispute case in the corresponding element type for documents in SAP Dispute Management

SAP Dispute Management delivers element type UDM_SPS_DOCUMENT as a sample element type for documents stored using the Knowledge Provider .The content model UDM_DOC01 that is entered in this element type is configured such that the documents are stored in the database of the SAP system.

However, for productive operations, we recommend that you generally store the documents in a content server and not in the database of the SAP system.You should only consider saving the documents in the database of the SAP system if the number and volume of the documents will be quite low.

Procedure

To store the documents in a content server, create your own content model and configure it.You can do this using the Content Model Wizard that you can access in Customizing for SAP NetWeaver under Application Server → Basis Services → Records Management → Customizing for Record Models, Records, and Documents → KPro Repository: Create Content Model.

You also have to configure the content server.For more information, see the Implmentation Guide (IMG) for SAP Content Server under SAP NetWeaver → Application Server → Basis Services → Knowledge Provider → Content Management Service.

The Content Model Wizard merely prepares the content model for the connection of such a server.

Create your own element type for documents.You can do this by copying the standard element type UDM_SPS_DOCUMENT.

In this element type, on the tab page Connection Parameter Values , enter your content model in the parameter DOCUMENT_CLASS.

In contrast to the documents, we recommend that you store the document templates in the database of the SAP system. The content model UDM_DOC02 that is entered in the sample element type for document templates in SAP Dispute Management (UDM_SPS_DOCUMENT_TEMP) is configured such that the documents templates are stored in the database of the SAP system.

The system also saves documents for case records. In this case the documents are XML documents. In contrast to the documents mentioned above, we recommend that you store the XML documents for case



records in the database of the SAP system for performance reasons. The content model SCMG01 that is entered in the sample element type for case records in SAP Dispute Management (UDM_SPS_CASE_RECORD) is configured such that the XML documents of the case records are stored in the database of the SAP system.

1.5.1.4 Creating Case Record Models

Use

The case record model determines the structure of the dispute case record that contains all objects that are either part of the case or that contribute to the resolution of the case. These objects are, for example, SAP business objects such as residual items, invoices, credit memos, and billing documents, but also objects such as ArchiveLink documents. With different node types, you can define the type and order of the objects for each case record (also linked objects) in the case record models.

The following different node types exist:

● Structure nodesStructures the linked objects for a case record similar to a file structure.

● Model nodesDefines which types of elements can be added to the case record at the point in question.

ExampleIn the case records model, you define a model node with the name Customer. In the definition of this model node, you enter the element type that you have created for the SAP business object type KNA1. In this way you ensure that links to customers can be added to the case records at this point.

● Instance nodesDefines that a specific instance of an element type always appears at the point in question in the case records.

ExampleIn the case records, you want to provide users with a node where they can branch to the customer line item list. To do this, in your record model, you define an instance node with a suitable description and enter the element type that you have created for general transactions in the definition of this instance node.

Select transaction FBL5 as the instance. In the case record, the users can double-click on this node to display the customer line item list.

You can add further information for dispute case processing to the case record model in accordance with the requirements of your company. You can include new structure nodes for this, and assign model or instance nodes to them.


Procedure

You create or edit a case record model in the Customizing for SAP Financial Supply Chain Management under Dispute Management Dispute Case Processing Element Types and Case Record Models Create and Process Case Record Model.

SAP delivers the case record models UDM_DISPUTE and UDM_DISPUTE_CDIS as copy templates. They contain the following structure nodes:

● Business Partner● Customer-Disputed Objects (only in UDM_DISPUTE_CDIS)● Disputed objects● Resolved objects● Items assigned during clearing● Other objects

NoteThe case record models delivered are merely examples. Use it as a copy template for your own case record model. SAP reserves the right to make non-compatible changes to the sample case record model.

Copy the model, and adjust the copy to meet your requirements.

CautionMake sure that you set the status Released in the case record model before you use it. This avoids the error message that appears when you create a dispute case if the case record model still has the status Initial.

Note, however, that you can only make restricted changes to a case record model once you have released it and created cases with it. You cannot make any non-compatible changes since this would mean that you would not be able to use the cases that you have already created. Non-compatible changes would be deleting nodes or subtrees in the case record model and changing an element type in a model node, for example. You can still add and deactivate nodes.

This procedure for copying the case record model depends on the whether you use the Records Management system (RMS) UDM_DISPUTE or your own Records Management system.

Copy case record model UDM_DISPUTE or UDM_DISPUTE_CDIS in RMS UDM_DISPUTE

1. Choose the Customizing activity Element Types and Case Record Model → Create and Edit Case Record Model.The Case Management screen appears.

2. On the left side of the screen, choose with the quick info text Change RMS.3. Enter RMS UDM_DISPUTE in the dialog box that follows and choose Continue.4. On the left side of the screen, choose SAP Dispute ManagementRecord and Case Record Models, with the

second mouse key click on Modeler for Case Records in Dispute Management, and choose Find.

NoteIf your element type has a different name for the record modeler, a different name to Modeler for Case Records in Dispute Management appears here.



The dialog box Search in Element Type "Modeler for Case Records in Dispute Management appears.5. Choose Execute Search, and then double-click on the entry Dispute Management (UDM_DISPUTE) or

Dispute Management with Customer-Disputed Objects (UDM_DISPUTE_CDIS) in the results list.The system creates an entry for the case record model in the screen area History on the left.

6. In the area History, click on this entry with the second mouse button and choose Other Functions → Copy Model.

7. To change the name of the case record model you have copied, click on the icon with the quick info text Model Attributes in the center of the screen, and overwrite the proposed texts for the fields Short Description and Unique ID.

8. Confirm your entries and then save.The system creates an entry for your copy in the screen area History on the left.

9. Adjust the copied case record model to suit your requirements.10. Once you have completed and saved your adjustments, in the central area of the screen choose

ModelChange Status. In the dialog box that appears, choose Status Released and confirm this entry by clicking Continue. You do not have to set the status Final in the record model.

11. If you want to transport your case record model, in the central area of the screen choose ModelAdministrationTransport Entry. In the subsequent dialog box, choose the relevant transport request or create a new one.

NoteRemember that you have to transport the case record model that you want to use in productive operations to your productive system.

12. When you create your element type for the case records, enter the case record model ID of your case record model in this element type. Choose the Customizing activity Element Types and Case Record ModelCreate Element Type for Case Record. You must also enter the ID of your case record model in the case type you use (Customizing activity Case TypesDefine Case Types).

Copy case record model UDM_DISPUTE or UDM_DISPUTE_CDIS into your own RMS

1. Choose the Customizing activity Element Types and Case Record Model → Create and Edit Case Record Model.

2. The Case Management screen is displayed.

3. On the left side of the screen, choose with the quick info text Change RMS.4. Enter RMS UDM_DISPUTE in the dialog box that follows and choose Continue.5. On the left side of the screen, choose SAP Dispute ManagementRecord Models and Case Record Models,

with the second mouse key click on Modeler for Case Records in Dispute Management, and choose Find.

NoteIf your element type has a different name for the record modeler, a different name to Modeler for Case Records in Dispute Management appears here.

6. The dialog box Search in Element Type "Modeler for Case Records in Dispute Management appears.7. Choose Execute Search, and then double-click on the entry Dispute Management (UDM_DISPUTE) or

Dispute Management with Customer-Disputed Objects (UDM_DISPUTE_CDIS) in the results list.8. The case record model appears in the middle of the screen.9. In the center of the screen, choose ModelSave as Local File. On the dialog box that appears, enter where

and under which file name the case record model should be saved as a local file and save.


10. A dialog box appears with the message Download executed; confirm with Continue.

11. On the left side of the screen, choose with the quick info text Change RMS.12. In the next dialog box, enter your own RMS into which you wish to copy the case record model

UDM_DISPUTE or UDM_DISPUTE_CDIS and choose Continue.13. From the left of the screen, choose Record and Case Record Model. Click on the secondary mouse button

on Modeler for Case Records in Dispute Management and choose Create.14. In the middle of the screen, choose ModelLoad as Local File. Choose the local file where you saved the case

record model from the dialog box that appears.15. The message Upload executed appears in a dialog box. Confirm this dialog box with Continue.16. In the central screen area, you now see a copy of the case record model that was created in your own RMS.

First save this copy before you make any adjustments to this case record model. Choose Save. Enter a short description and a unique name in the dialog box that appears.

17. Adjust the copied case record model to suit your requirements. You must replace the element types used in the copy of the case record model with your own element types since the element types from RMS UDM_DISPUTE are not included in your own RMS.

18. Once you have completed and saved your adjustments, in the central area of the screen choose ModelChange Status. In the dialog box that appears, choose Status Released and confirm this entry by clicking Continue. You do not have to set the status Final in the record model.

19. If you want to transport your case record model, in the central area of the screen choose ModelAdministrationTransport Entry. In the subsequent dialog box, choose the relevant transport request or create a new one.

NoteRemember that you have to transport the case record model that you want to use in productive operations to your productive system.

20.When you create your element type for the case records, enter the case record model ID of your case record model in this element type. Choose the Customizing activity Element Types and Case Record ModelCreate Element Type for Case Record. You must also enter the ID of your case record model in the case type you use (Customizing activity Case TypesDefine Case Types).

21. For more information on creating and editing case record models, see the documentation for the Customizing activity Element Types and Case Record ModelCreate and Process Case Record Model.

1.5.1.5 Define Case Types

Use

The case type is a central Customizing object in SAP Dispute Management and controls the structure and properties of the dispute cases.

When a user creates a case in Dispute Case Processing, he has to select a case type manually if the relevant RMS contains several case types. When you create dispute cases from Accounts Receivable Accounting transactions, the case type is determined automatically.



ExampleIn your company, you want to use different number range intervals for assigning numbers to dispute cases for each company code. You also want the company codes to have different attributes in the dispute case.

For this requirement you create two different case types. You assign different number range intervals and attribute profiles to the case types. For each company code you define a different case type as default value.

Prerequisites

Different settings are grouped for each case type. Make sure that you have made the following settings in Customizing:

Parameter Explanations

Case Record Model ID See Creating Case Record Models [page 19]

RMS ID See Creating a Records Management System (RMS) [page 16]

Element Type ID (Case)

Element Type ID (Record)

Element Type ID (Notes)

See Creating Element Types [page 17]

Internal Number Range The dispute case number is automatically determined via internal number assignment.

You define the internal number ranges in Customizing of Dispute Case Processing under Define Number Range for the Case.

Attribute Profile In the attribute profile you define which attributes are used in a dispute case, which properties they have, and where they appear in a dispute case.

You create the attribute profile in Customizing of Dispute

Case Processing under Attribute Profile Create Attribute

Profile .

Function Profile In the function profile you define which functions are to be available in the dispute case.

You create the function profile in Customizing of Dispute

Case Processing under Function Profile Create Function

Profile .


Parameter Explanations

Status Profile A status profile contains the status values that can be assigned to a case.

You define the status profile in Customizing of Dispute Case

Processing under Status Management Create Status

Profile .

Text Profile In the text profile, you define which text IDs you want to use for your case notes.

You create the text profile in Customizing of Dispute Case Processing under Text Profile.

Procedure

1. Consider whether you need different case types in your company. You need different case types if the dispute cases (grouped per case type) have different Customizing settings or if you want to differentiate between dispute cases with regard to authorizations.For more information, see Authorization Concept of SAP Dispute Management.

2. Create the case type. To do this, copy the case type template F_DM (Dispute Management) or F_D2Dispute Management with Customer-Disputed Objects) delivered by SAP Dispute Management and adjust your copy.For more information, see the Customizing of Dispute Case Processing under Case Types Define Case Types .

3. To have the case type determined automatically during the creation of dispute cases in Accounts Receivable, assign the required case types to the company codes in your Accounts Receivable system.For more information, see Customizing of the Process Integration with Accounts Receivable under Define Default Values when Creating Dispute Cases.

1.5.1.6 Customer Enhancements for SAP Dispute Management

SAP Dispute Management provides several Business Add-Ins (BAdIs) that you can use to implement customer-specific requirements that do not require modifications.

The SAP Dispute Management BAdIs can be divided into two categories:

● Business Add-Ins (BAdIs) in dispute case processingIn Dispute Case Processing there is a series of BAdIs that are called by the system when you create or change dispute cases. Most of these BAdIs are called irrespective of whether the creation or change was made in Dispute Case Processing or through the process integration with SAP Dispute Management.Moreover, both the correspondence function and the workflow integration of SAP Dispute Management provide BAdIs for customer-specific adaptations.



For more information, see BAdIs for Dispute Processing [page 25].● Business Add-Ins (BAdIs) in process integration

In process integration of SAP Dispute Management with Accounts Receivable Accounting there is a series of BAdIs that are called up when creating dispute cases in Accounts Receivable (FI-AR) or when changing dispute cases by process integration. They are not called up if dispute cases are created or changed in dispute case processing. BAdI FDM_AR_DISP_COMPLETE is an exception.In addition, the automatic write-off of dispute cases provides a BAdI for customer-specific adaptations (see Setting Up Automatic Write-Off of Dispute Cases [page 30]).For more information, see BAdIs for Process Integration [page 31].

1.5.1.6.1 BAdIs for Dispute Case Processing

Use

SAP Dispute Management provides several Business Add-Ins (BAdIs) that you can use to implement customer-specific requirements that do not require modifications (see also Customer Enhancements for SAP Dispute Management [page 24]).

Key Features

The Dispute Case Processing of SAP Dispute Management provides you with the following BAdIs:

Business Add-In Description

SCMG_INITIALIZE_C Change cases during initialization

This BAdI is called up when you create a case. Here you can implement a customer-specific initialization of the case.

The BAdI is only called when you create a case in Dispute Case Processing, and not when you create a case from Accounts Receivable.

SCMG_BEFORE_VALID_C Change cases before validation

This BAdI is always called before the system checks whether case data is correct. Here you can change the relevant case attributes according to your requirements.

This BAdI is called when both when you create and change a case in Dispute Case Processing and when you create and change a case through process integration with Accounts Receivable.



SCMG_VALIDATE_C Customer-defined validation of cases

This BAdI is always called when the system checks the case data. You can carry out customer-defined checks in this BAdI.


SCMG_CHNG_BFR_STR_C Change cases before saving

This BAdI is called before the case data is saved to the database. Here you can change the relevant case attributes according to your requirements.


SCMG_VLDT_BFR_STR_C Customer-defined validation before saving

This BAdI is called before the case data is saved to the database. Here you can carry out customer-specific checks.


SCMG_STORE_S Save customer-defined data when saving cases

This BAdI is called when the case data is saved to the database. Here you can save customer-specific data in other tables on the database if you want to save this data with the case.





SCMG_AUTHORITY_C Customer-defined authorization checks in the case

You can implement customer-defined authorization checks in the case in this BAdI, if you have requirements that go beyond the standard authorization checks for the case.

This BAdI is called when both when you create, change and display a case in Dispute Case Processing and when you create, change and display a case from Accounts Receivable.

SCMG_CASE_FCODE_S Customer-defined functions

This BAdI is called if a function code that is not implemented in the standard system is called in Dispute Case Processing. To implement customer-specific functions for case processing, you have to define a customer-specific function key in the IMG activity Define Functions, and in this BAdI you have to implement a customer-specific function for the corresponding function code.

UDM_LOC_MASSACT_C Mass activities on dispute cases

In this BAdI you can define mass activities for dispute cases. These mass activities are then available as function keys in the dispute case search and you can use them on a number of dispute cases in the results list for the search.

For more information, see the documentation for the individual BAdIs.

In addition to the BAdIs listed here, both the correspondence function and the workflow integration of SAP Dispute Management provide BAdIs for customer-specific adaptations. You can find information about these BAdIs in the IMG for Dispute Case Processing under the following paths:

● Correspondence Customer Enhancements

● WorkflowBAdI: Trigger Events

Examples for Using BAdIs

ExampleYou want to make sure that when you close the case, the root cause code is entered in the case. In the BAdI SCMG_VLDT_BFR_STR_C (Customer-Defined Validation of Cases), you can check whether the Root Cause Code case attribute has been incorrectly set to initial when the case is closed.

ExampleIn the dispute case, you want to offer a function key that enables the user to set the payment lock in the customer master record. To implement this, you would define your own function key and implement the corresponding function in the BAdI SCMG_CASE_FCODE_S (Customer-Defined Functions).


Activities

To implement the customer enhancements, call up the corresponding BAdIs in Customizing for Dispute Case Processing:

Content System Menu Path

Customer Enhancements System for Dispute Case Processing Customer Enhancements

Function Profile Customer-Defined

Functions

Correspondence Customer

Enhancements

Correspondence Define and

Configure Actions

Workflow BAdI: Trigger Events

1.5.2 Customizing of the Process Integration with Accounts Receivable

Use

The following sections contain the special features for business Customizing for the Process Integration with Accounts Receivable.

1.5.2.1 Defining Default Values

Use

When you create a dispute case from Accounts Receivable transactions, the system displays a dialog box in which you can enter the dispute case attributes. You can define default values for these attributes in Customizing. You can also define the basic values for creating a dispute case (such as case type) in this Customizing activity that are not ready for input in the dialog box.

Using default values simplifies the creation of dispute cases from Accounts Receivable, and reduces the risk of input errors.

NoteYou can override all of the default values given above by implementing customer rules in Business Add-Ins (see Customer Enhancements for SAP Dispute Management [page 31]).



Procedure

Navigation




In Customizing of the Process Integration with Accounts Receivable: Define Default Values for Creating Dispute Cases

Here you define the default values for each company code. You can define the following default values:

Case Type

Define the required Case Type for each company code. You can use differing Case Types for individual company codes.

For more information, see Defining Case Types [page 22].

Category

If you are using Categories in dispute cases, you can define the required default value for the Dispute Case Category for each company code. You can use differing Categories for individual company codes.

Reason

You can define the required default value for the Reason for each company code.

If dispute cases for residual items due to underpayments are created in your company, and the reason is not normally known by the employee processing the case, you should define Unknown as the Reason

In this Customizing activity, you can also link the Reason to the Reason Codes of the accounts receivable accounting system. To do this, first analyze the Reason Codes in Accounts Receivable. Create Reasons for such Reason Codes as are likely to be the reason for dispute cases. For each Reason Code, define the corresponding Reason from Dispute Case Processing

Result: If you have a residual item, the Reason Code of which has a Reason assigned, and you create a dispute case for the residual item in Accounts Receivable, then the system proposes the Reason that you have defined in Customizing.

Priority

You can define the required default value for the Priority for each company code. In addition, you can assign a Priority for each reason code. You do this in the same view in which you assign the Reasons to the Reason Codes.

Result: When you create dispute cases in Accounts Receivable the system behaves as follows: If you have assigned a default value to the Reason Code for the Reason or for the Priority, then the system transfers the values for the Reason and for the Priority from the Customizing settings to the Reason Code as default values. If you have not done this, the system transfers the default values from the company code.


This means you can give higher priority to dispute cases with the Reason 'late delivery' than you do to dispute cases with the Reason 'price problem'.

External Reference

In the External Reference in Dispute Case field, you can define an ID that can be used to identify the message.

You can define three line item fields for the External Reference that are then used as default values.

The system first tries to fill the External Reference field with the value in the line item field that you have assigned Priority 1 to in Customizing. If this field is not filled, the field that you assigned under Priority 2 is used. If this is also empty, the field assigned under Priority 3 is copied.

An external reference can be the number of the invoice that was underpaid.

1.5.2.2 Configuring the Automatic Write-Off of Dispute Cases

Use

For dispute cases where the customer does not receive a credit memo and the disputed amount is deemed to be uncollectible, you can write off the disputed amount automatically in Dispute Case Processing. The dispute case is then closed automatically. You can also use the automatic write-off function to write off and close dispute cases with small amounts.

Procedure

Navigation




In Customizing of the Process Integration with Accounts Receivable: Automatic Write-Off of Dispute Cases

Here you define the account assignment of offsetting entries that the system should use for automatic write-offs.

In Customizing, you can configure the general ledger account for each company code, case type, and reason. You can also define the cost center to be posted to for each company code and person responsible. This Customizing setting is interpreted by one of the default implementations of the BAdI FDM_AR_DISP_WRITEOFF that is delivered by SAP. If you require other rules for the account assignment, you can create a customer-specific implementation of BAdI FDM_AR_DISP_WRITEOFF and then implement your customer-specific rules in it (see BAdIs for Process Integration [page 31]).



Navigation


Status for closure with automatic write off of dispute cases

System for Dispute Case Processing SAP Financial Supply Chain Management SAP Dispute Management Process Integration Define Automatic Status Changes

Here you define a Status that the system should use when automatically writing off dispute cases at closure.

1.5.2.3 Customer Enhancements for SAP Dispute Management

SAP Dispute Management provides several Business Add-Ins (BAdIs) that you can use to implement customer-specific requirements that do not require modifications.

The SAP Dispute Management BAdIs can be divided into two categories:

● Business Add-Ins (BAdIs) in dispute case processingIn Dispute Case Processing there is a series of BAdIs that are called by the system when you create or change dispute cases. Most of these BAdIs are called irrespective of whether the creation or change was made in Dispute Case Processing or through the process integration with SAP Dispute Management.Moreover, both the correspondence function and the workflow integration of SAP Dispute Management provide BAdIs for customer-specific adaptations.For more information, see BAdIs for Dispute Processing [page 25].

● Business Add-Ins (BAdIs) in process integrationIn process integration of SAP Dispute Management with Accounts Receivable Accounting there is a series of BAdIs that are called up when creating dispute cases in Accounts Receivable (FI-AR) or when changing dispute cases by process integration. They are not called up if dispute cases are created or changed in dispute case processing. BAdI FDM_AR_DISP_COMPLETE is an exception.In addition, the automatic write-off of dispute cases provides a BAdI for customer-specific adaptations (see Setting Up Automatic Write-Off of Dispute Cases [page 30]).For more information, see BAdIs for Process Integration [page 31].

1.5.2.3.1 BAdIs for the Process Integration

Use

SAP Dispute Management provides several Business Add-Ins (BAdIs) that you can use to implement customer-specific requirements that do not require modifications (see also Customer Enhancements for SAP Dispute Management [page 31]).


Key Features

The process integration of SAP Dispute Management provides you with the following BAdIs:

BAdIs for Default Values when Creating Dispute Cases

With the BAdIs listed below, you can define default values for creating dispute cases in Accounts Receivable. These default values then appear in the dialog box that appears when the user creates a dispute case. The user can then overwrite this default value as long as the field in question is modifiable.


FDM_AR_DEF_CASE_TYPE Customer-defined default values for the case type

FDM_AR_DEF_CATEGORY Customer-defined default values for the category

FDM_AR_DEF_REASON Customer-defined default values for the reason

FDM_AR_DEF_PRIORITY Customer-defined default values for the priority

FDM_AR_DEF_EXT_REF Customer-defined default values for the external reference

FDM_AR_DEF_PROCESSOR Customer-defined default values for the processor

FDM_AR_DEF_FIN_COORD Customer-defined default values for the coordinator

FDM_AR_DEF_RESPONSIB Customer-defined default values for the person responsible

FDM_AR_DEF_CASE_TITLE Customer-defined default values for the title

FDM_AR_DEF_DUE_DATE Customer-defined default values for the processing deadline

FDM_AR_DEF_PLAN_END Customer-defined default values for the planned closing date

FDM_AR_DEF_NOTE Customer-defined default values for the notes

Additional BAdIs




FDM_AR_DISP_COMPLETE Completion of the dispute case

With this BAdI, you can determine SAP business objects, attributes, and notes based on the business data from FI (for example, documents, business partner) and add them before you save the dispute case.

The BAdI is called up by the system as follows:

● When you create a dispute case in Accounts Receivable● When the dispute case changes due to the process inte

gration with Accounts Receivable● When disputed items are released from an existing dis

pute case and transferred to a new dispute case (dispute case is split)

● When you include open items in a dispute case in Dispute Case Processing

FDM_AR_UI_FIELDSTATUS Control of attribute maintenance properties

With this BAdI you can influence the field status of the dialog for creating dispute cases in Accounts Receivable. Irrespective of the Customizing, you can also use this BAdI to define whether fields are required, visible, or modifiable in the dialog box when you create dispute cases in Accounts Receivable.

FDM_USER_SCREEN Customer-defined subscreen

With this BAdI you can implement a customer-defined screen area that appears in the dialog box for creating dispute cases in Accounts Receivable. The data that you enter there can be transferred to the dispute case as SAP business objects or as attributes.

You can also implement a validation of this dispute case.

FDM_AR_DISP_WRITEOFF Customer enhancement for automatic write-off of dispute cases

If you use the function for writing off dispute cases automatically, you can use this BAdI to determine the posting data for the general ledger item with automatic write-offs.

FDM_AR_CDIS_ASSIGNMENT Implement customer enhancement for assignment of open items to dispute cases

This BAdI valuates existing dispute cases that should be considered for the assignment of open items to these dispute cases.



FDM_AR_CDIS_AMOUNT Implement customer enhancment for calculation of customer-disputed amount

FDM_AR_BD_DEF_CASE_TYPE Implement customer enhancement for defining the case type for SAP Biller Direct

Activities

To implement the customer enhancements, call up the corresponding BAdIs in the Implementation Guide for SAP Dispute Management:



System with the software component Accounts Receivable (FI-AR)

In Customizing of the Process Integration with Accounts Receivable: Customer Enhancements

In Customizing of the Process Integration with Accounts Receivable:

Automatic Write-Off of Dispute Cases

Implement Customer Enhancement .

Examples

● When you create a dispute case in Accounts Receivable, you want to define a default value for the priority irrespective of the total amount of the items to be included.To do this, you would implement the BAdI (FDM_AR_DEF_PRIORITY( customer-defined default values for the priority ).

● In the dispute case, you have included a customer-defined attribute in the attribute profile and want to enable the user to enter this attribute when creating the dispute case from Accounts Receivable.To do this, you would implement the BAdI (FDM_USER_SCREEN ( customer-defined subscreen ).



1.5.2.4 Including Fields in the Line Item List

Use

The process integration of SAP Dispute Management with Accounts Receivable enables a process to see which items in the customer line item list are included in a dispute case as disputed or resolved objects. To enable this, define which dispute case attributes should appear in the line item list:

● The attributes Case ID, Processor, Status , and Priority , and the field Customer-Disputed , as defined in the standard deliveryThe Customer-Disputed field shows whether the invoice belonging to a residual item is already included in a dispute case as customer-disputed object .

● Additional dispute case attributes from the structure FDM_UI_ATTRIBUTES● Dispute case attributes that are not contained in the structure FDM_UI_ATTRIBUTES. In particular, these

can be customer-specific dispute case attributes.● A combination of the above variants

NoteIn the line item list you can create a dispute case for an item or navigate to a dispute case that has already been created in order to process it.

Procedure

Which of the following steps you must execute depends on whether you only want to provide the dispute case attributes Case ID , Processor , Status , and Priority in the line item list or also additional dispute case attributes.

CautionNote that you always have to carry out the steps under Providing Dispute Case Attributes in the Line Item List , even if you only use the standard delivery.

Include Additional Dispute Case Attributes in the Line Item List

If you want to provide additional dispute case attributes in addition to Case ID , Processor , Status , and Priority in the line item list, carry out the following steps:

1. Add an Append Structureto structures RFPOS and RFPOSX.2. Include any additional dispute case attributes in this append structure that you want to provide in the line

item list. In particular, these can be customer-specific dispute case attributes.If you have included dispute case attributes in the append structure mentioned and these are not included in the FDM_UI_ATTRIBUTES structure, add an append structure to the structure FDM_UI_ATTRIBUTES and include the attributes in this append structure.Provide Dispute Case Attributes in the Line Item List

Irrespective of whether you only want to provide the dispute case attributes Case ID , Processor , Status , and Priority and the field Customer-Disputed in the line item list or also additional dispute case attributes, you must execute the following steps.


NoteCarry out the steps described below in your development and Customizing system and in your test and productive system.

1. Choose transaction SE41, Menu Painter .1. Enter SAPLFI_ITEMS as the program.2. Select Status , and then enter the status ALV_ITEMS_AR in this line.

3. From the menu, choose Screen Generate .4. Select Status , and then enter the status GRID_ITEMS_AR in this line.

5. Choose Interface Generate.You have generated the screen status ALV_ITEMS_AR and GRID_ITEMS_AR again.

2. Run the program RFPOSXEXTEND.You have regenerated the line item structure.

3. Run the program BALVBUFDEL.You have reset the ALV ( SAP List Viewer ) buffer.

1.5.2.5 Additional Fields for Assignment of Open Credit Memos/Payments

Use

In the function Assignment of Open Credit Memos and Payments , you can display additional fields in the overview of the items. You can display additional fields from the following areas:

● Customer invoice● Dispute case

Activities

The structure FOAP_S_CDITEM ( Debit/Credit Item for Assignment ) defines the display of the items. It contains the customer include CI_FOAP_S_CDITEM to which you can add the fields of the structures specified by append. You can use all fields from the following structures:

● SCMG_CASE_ATTR● UDM_S_DCATTR● BSID

When you enhance the customer includes listed above, always use the same field name as in the source strucure for an additional field. In doing this you ensure that when you display the items, the data is automatically transferred from the source structures.



1.6 SAP Dispute Management Authorization Concept

Use

You can use the authorization concept partly in combination with Customizing settings to control which SAP Dispute Management data is visible or modifiable for different users, and which activities the user can carry out in SAP Dispute Management.

● For more information about the authorization concept, in particular about the standard users and standard roles of SAP Dispute Management, see SAP Dispute Management Security Guide.You can access the security guide on SAP Service Marketplace at service.sap.com/securityguide.

● For more information about organizational aspects, see Mapping Separate Organizational Areas [page 37].

1.6.1 Mapping Separate Organizational Areas

Use

Companies frequently have separate organizational areas that should also have separate areas in Dispute Case Processing. This means that employees in one area normally do not have access to the dispute cases in other areas. Using Customizing and the authorization concept, there are various ways that you can reflect this.

Procedure

Map Authorizations in One Records Management System (RMS)

You can manage the different areas in one Records Management System, and within this RMS, reflect the different areas using separate element types and case types.

In the authorization objects of the component SAP Records Management, you can assign authorizations per element type.

In the component Case Management, you can assign authorizations per case type.

If you create different element types and case types for the different areas, you can use the authorizations to control which of these areas a user can access.

NoteHowever, the following element types are exceptions to the procedure described:

In the element types of SAP business objects added to the dispute case automatically from Process Integration with Accounts Receivable, Process Integration requires that only one element type is used for each business object type and logical accounting system For more information, see the Implementation Guide (IMG) of Dispute Case Processing, under SAP Financial Supply Chain Management SAP Dispute ManagementCreate Element Type.


You cannot create different element types for different organizational areas for these business object types if the business object type and the logical accounting system are the same. However, you can protect the business object data for SAP business objects from unauthorized access via the authorization protection of the business object concerned.

For the element type for dispute cases (in the standard system this is the element type UDM_SPS_CASE), due to the authorization protection you do not necessarily have to create a separate element type for each organizational area. This is because for the dispute case, you can use the authorization objects of the component Case Management to control which activities a user can carry out for each case type.

Map Authorizations in Several Records Management Systems (RMS)

You can set up different Records Management systems for the different areas. In the SAP Records Management component, you can use the authorization object S_SRMSY_CL to control whether a user is to have access to the data of a Records Management system.

The authorization objects of the Case Management component also allow you indirectly to assign authorizations dependent on the Records Management system: In Case Management, you can assign authorizations to the user depending on the case type. Each case type is assigned to just one Records Management system in Customizing.

NoteAs described under Creating a Records Management System (RMS) [page 16], SAP recommends that you use only one Records Management system for SAP Dispute Management. Although the alternative with several Records Management systems is possible, it is not advisable in most cases.

Examples

You manage several company codes in Accounting. The employee of one company code should not have access to the dispute cases of other company codes.

As described above, this can be reflected in two different ways:

Authorizations in One Records Management System

Create different case types that belong to one Records Management system for the different company codes.

In the Customizing of the default values for creating dispute cases in Accounts Receivable, assign different case types to the company codes.

Create different element types for the various company codes apart from the exceptions mentioned above.

Limit the authorizations of a user to certain case types and element types. This controls in which company codes a user can access dispute cases.

Authorizations in Several Records Management Systems

Create different Records Management systems for the different company codes. This means that you manage different case types for the different Records Management systems.

In the Customizing of the default values for creating dispute cases in Accounts Receivable, assign the case type from the relevant Records Management system to the company codes.



Limit the authorizations of a user to certain Records Management systems and case types. This controls in which company codes a user can access dispute cases.

NoteAs already mentioned, the second procedure is possible, but only useful in a few cases (see also Creating a Records Management System (RMS) [page 16].


Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.


Important Disclaimers and Legal Information

Configuration Guide for SAP Dispute Management for FI-ARImportant Disclaimers and Legal Information P U B L I C 41

www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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 and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html