172275575 sample-fscm-config-user-guide (2)

www.sapcustomization.com

[email protected]

SAP FSCM Configuration & User Guide

This Copy is Owned By: [email protected] of 233

TABLE OF CONTENT

TABLE OF CONTENT ..................................................................................................................................... 1

FINANCIAL SUPPLY CHAIN MANAGEMENT ............................................................................................. 5

CHAPTER – 1 - BUSINESS PARTNER ............................................................................................................. 0

Overview of Business Partner .............................................................................................................. 2

Define BP Roles ...................................................................................................................................... 5

Define Number Ranges: ........................................................................................................................ 8

Define Groupings and Assign Number Ranges: ............................................................................. 10

Synchronization Objects ...................................................................................................................... 11

Activate Synchronization Options: .................................................................................................... 13

Set BP Role Category for Direction BP to Customer: ...................................................................... 14

Define BP Role for Direction Customer to BP: ................................................................................. 15

Define Number Assignment for Direction BP to Customer .......................................................... 16

Define Number Assignment for Direction Customer to BP: ......................................................... 18

Activate/Deactivate Standard Implementation for Mapping in FI-AR: ...................................... 19

CHAPTER – 2 - DISPUTE MANAGEMENT ................................................................................................... 21

Overview of Dispute Management ................................................................................................... 25

BAdIs for Dispute Case Processing ............................................................................................... 26

Create RMS ID: ..................................................................................................................................... 28

Create Element Type: .......................................................................................................................... 30

Attribute Profile: .................................................................................................................................. 34

Attribute Priority: ................................................................................................................................. 38

Create values for Attribute Escalation Reason: ............................................................................... 39

Assign Escalation Reason to Attribute Profile: ................................................................................ 40

Create Profile for Case Search: ........................................................................................................... 41

Create Function Profile: ....................................................................................................................... 43

Create Text Profile:............................................................................................................................... 47

Create Status Profile: ........................................................................................................................... 49


[email protected]



Define Number Range Interval for Case: ......................................................................................... 50

Define Case Type: ................................................................................................................................ 51

Create values for Attribute Category in Case Type: ....................................................................... 53

Create values for Attribute Reason in Case Type: ........................................................................... 55

Create values for Attribute Root Cause Code in Case Type: ......................................................... 56

Define Derivation of Element Types ................................................................................................. 57

Define Automatic Status Changes: .................................................................................................... 59

Activate Process Integration for SAP Dispute Management: ........................................................ 61

Define Default values for creation of Dispute cases: ...................................................................... 62

Automatic Write-off of Dispute cases: .............................................................................................. 64

Define Posting Keys for Clearing....................................................................................................... 66

Assignment of Open Credits and Payments: ................................................................................... 68

CHAPTER – 3 - COLLECTION MANAGEMENT ........................................................................................... 71

Overview of Collection Management ............................................................................................... 74

Define Company Codes for SAP Collections Management: .......................................................... 87

Collection Strategies - Basic Rules: .................................................................................................... 88

Collection Strategies - Collection Rules: ........................................................................................... 90

Collection Strategies – Process Strategies: ........................................................................................ 92

Collection Strategies – Priorities: ....................................................................................................... 96

Collection Strategies – Derivation of Priority: ................................................................................. 97

Collection Segments:............................................................................................................................ 99

Collection Profile: ............................................................................................................................... 100

Collection Groups: ............................................................................................................................. 101

Assign Collection Groups to Collection Segments: ....................................................................... 104

Create Status Profile for Promise to Pay: ........................................................................................ 105

Define Number Range Interval for Case: ....................................................................................... 107

Promise to Pay - Define Case Types ................................................................................................ 109

Promise to Pay – Define Automatic Status Changes: ................................................................... 111


[email protected]



Define Result of Customer Contact: ................................................................................................ 111

Define Resubmission Reason: .......................................................................................................... 112

Define Status for Dispute Cases To Be Collected: ......................................................................... 113

Activate SAP Collection Management: ........................................................................................... 114

Mapping of Master Data: .................................................................................................................. 115

Activate Distribution per Company Code: .................................................................................... 116

Make Settings for Promise to Pay: ................................................................................................... 116

Activate Assignment of Contact Persons:....................................................................................... 117

CHAPTER – 4 - IN-HOUSE CASH .............................................................................................................. 119

Overview of In-house Dispute Management ................................................................................. 119

CHAPTER – 5 – DISPUTE MANAGEMENT – USER GUIDE ........................................................................ 120

FLB5N-Creating Dispute Cases from the Line Item List: ............................................................. 121

UDM_DISPUTE - View dispute case: ............................................................................................. 124

FB03 - Creating Dispute Cases from the Document Display: ...................................................... 128

Creating Dispute Cases during Processing of Account Statements: .......................................... 130

F-28 - Creating Dispute Cases during Clearing of Open Items: .................................................. 131

UDM_DISPUTE - Adding Open Items to Dispute Cases: ............................................................ 135

FDM_AUTO_CREATE - Automatic Creation of Dispute Cases: ................................................ 140

UDM_AUTOWRITEOFF - Automatic Write-Off of Dispute Cases ............................................ 147

CHAPTER – 6 – BUSINESS PARTNER – USER GUIDE ................................................................................ 151

FD01 - Create Customer Master: ...................................................................................................... 151

UDM_BP - Business Partner Master Data: ..................................................................................... 155

CHAPTER –7 – COLLECTION MANAGEMENT – USER GUIDE................................................................. 161

Collection Strategies .......................................................................................................................... 163

Collection Groups: ............................................................................................................................. 166

Assign Groups to Segments .............................................................................................................. 167

Distribution of Data to Collections Management: ......................................................................... 168

Creation of Worklists ......................................................................................................................... 170


[email protected]



My Worklist: ....................................................................................................................................... 172

All Worklists ....................................................................................................................................... 180

Evaluation of Promise to Pay: .......................................................................................................... 181

CHAPTER –8 – IN-HOUSE CASH – USER GUIDE ..................................................................................... 184

CHAPTER –9 – BUSINESS PROCESSES ...................................................................................................... 185

BUSINESS SCENARIO - 1: ............................................................................................................... 187



BUSINESS SCENARIO – 4: ............................................................................................................... 191






BUSINESS SCENARIO – 10: ............................................................................................................. 200



CHAPTER –10 – QUESTIONS AND ANSWERS: ......................................................................................... 212

QUESTION- 1 ..................................................................................................................................... 213

QUESTION-2 ...................................................................................................................................... 213

QUESTION-3 ...................................................................................................................................... 214

QUESTION-4 ...................................................................................................................................... 217

CHAPTER – 11 – ISSUES AND RESOLUTIONS ........................................................................................... 218

ISSUE - 1 .............................................................................................................................................. 218

ISSUE - 2 .............................................................................................................................................. 219

ISSUE – 3 ............................................................................................................................................. 220

ISSUE - 4 .............................................................................................................................................. 221

ISSUE – 5 ............................................................................................................................................. 221


[email protected]



OSS Note: ............................................................................................................................................ 222

Knowledge Base Articles: ................................................................................................................. 222

Tables: .................................................................................................................................................. 222

OSS Note: Business Partner: ............................................................................................................. 222

OSS Note: Dispute Management: .................................................................................................... 222

Tables: Business Partner Master Data: ............................................................................................ 222

The authors assume no responsibility for errors or omissions. You should use this

information as you see fit and at your own risk. Your particular situation may not be

exactly suited to the examples illustrated here and you should adjust your use of the

information and recommendations accordingly.

This book and authors are not affiliated with, sponsored by, or approved by SAP AG. Any

trademarks, service marks, product names or named features are assumed to be the

property of their respective owners, and are used only for reference. There is no implied

endorsement if we use one of these terms.

This Copy is Owned By: [email protected] Page 0 of 233

Refer Our Other eBooks -

SAP FICO Configuration and User Guide [Classic]

SAP FICO Configuration and User Guide [SAPGL]

SAP BPC 10.0 Configuration and User Guide [ NW]

Visit www.SAPCustomization.Com


FINANCIAL SUPPLY CHAIN MANAGEMENT

SAP Financial Supply Chain Management (SAP FSCM) set of applications provide a complete, integrated solution for managing electronic customer billing disputes, receivables, collections, and customer credit risk. SAP FSCM helps us to effectively control our company's account receivable processes and ensure cash flows through online billing, more streamlined handling of billing disputes, and collections. Customer can utilize this FSCM module for the option of viewing and paying bills via the Internet; or creating inquiries, comments or disputes to which the Business can reply or resolve online. Collections Management: If accounts receivable is not proactively addressed, the impact on the cash flow of a business can be adversely affected as increase the risk from customer default on outstanding invoices and increase the cost of operations for the receivables function. SAP Collections Management helps business proactively manage receivables, thus improving the overall financial performance. Dispute Management: Disputes are the nightmare of receivables function across business. In appropriate and inefficient dispute management process not only affect the financial performance in the short-run but also adversely affect customer relationship in the long-run. SAP Dispute Management can help business improve their management of short payments. SAP Dispute Management is fully integrated with sales and distribution, accounts receivable, collection management, credit control modules / sub-modules, and supports centralized case processing. Credit Management: Credit management is a process which increases the risk of receivables portfolio management but also reduces potential sales loss. An efficient credit management process becomes always necessary in tougher economic times. SAP Credit Management can help businesses proactively manage credit. Its tight integration with core SAP ERP modules, like Sales and Distribution, enables credit managers to effectively implement credit limits.

Biller Direct: Electronic Invoice Presentment and Payment (EIPP) helps business cut costs by moving to a paperless process, improve customer service by providing customer self-service, decrease billing errors. SAP Biller Direct is an EIPP solution that is fully integrated with the backend SAP ERP system eliminating redundancies and inconsistencies in data. In-House Cash: If our company has multiple corporate bank accounts spread across its global organizational structure, we are either paying an extra fee or providing free money to the banks by maintaining minimum cash balances. And we may be taking expensive loans for some part of our business whereas; we can be having extra cash to


[email protected]



spare within our organization. We would like to get optimum benefit of our cash position across multiple company codes, geographies, product lines, and business units by using SAP’s In-House Cash. In this eBook we have described how we can configure and use all these modules / sub-modules which revolve around optimum utilization of cash resources in an organization. For easy understanding, we have divided this eBook into following chapters; Chapter – 1 – Business Partner: In this chapter we will learn how to configure business

partner and its integration with accounts receivable module of FI.

Chapter – 2 – Dispute Management: SAP Dispute Management is used to manage and

resolve customer disputes efficiently. This chapter covers configuration of SAP Dispute

Management.

Chapter – 3 – Collection Management: Collections Management means customer

centric receivables management. To use this SAP application component we need to

configure SAP application which is covered in this chapter.

Chapter – 4 – In-house Cash: The SAP® In-House Cash application, one of the financial

supply chain management components of the mySAP™ ERP Financials solution, can

help cut the costs of processing transactions for internal payments, external payments,

and international payments while reducing the number of external bank accounts you

must handle. Following configuration steps are described in this chapter.

Chapter – 5 – Dispute Management User Guide: For effective use of configuration and

SAP Application, user community should be aware of various available functionalities

within the component. In this chapter we will learn how effectively we can use SAP

Dispute Management.

Chapter – 6 – Business Partner User Guide: Creation and maintenance of business

partner is a functionality of master data maintenance. Since Business partner master

data in integrated with customer master data, it is very important to understand how

various SAP function are delivered.


[email protected]



Chapter – 7- Collection Management User Guide: For effective use of SAP collection management functionality, collection representative should be well aware of various available options and its integration with other SAP components. Learn how to use effectvly SAP collection Management.

Chapter – 8 – Inhouse Cash User Guide: In-House Cash user Guide describes, how we

can get best result out of SAP In-House Cash.

Chapter – 9 – Business Processes:In this chapter we will learn few integrated business

process of SAP Financial Supply Chain Management.

Chapter – 10 – Questions & Answers:In this chapter we will learn few questions and

answers in the area of SAP FSCM.

Chapter – 11 – Issues and Resolutions: Issues and reolution chapter describes few real

time issues and its probable solution.

Chapter – 12 – References: This chapter covers various references for example OSS

Note, SAP Knowledge Base Areticles Etc.

Hope this eBook keep your expectation to the level.....


CHAPTER – 1 - BUSINESS PARTNER

Business Partner may be a person, organization, group of persons, or group of organizations in which a company has a business interest. We use this business object for a variety of business transactions. Refer “Overview of Business Partner” for more details. In order to use business partner functionality, we need to configure following steps;

• Define BP Roles: In this IMG activity, we define one or more Records Management Systems (RMS). We use the registry maintenance for these settings.

• Define Number Ranges: In this activity, we define number ranges for business partners. The defined number ranges are assigned to groupings in the Define groupings and assign number ranges activity. Number ranges for business partners are valid throughout a client.

• Define Groupings and Assign Number Range: In this activity, we maintain groupings for business partners.

• Activate Synchronization Options: Use this IMG activity to specify which SAP synchronization options we want to activate.

• Set BP Role category for Direction BP to Customer: In this IMG activity, we can define which BP role categories enable customer integration in the direction from the business partner to the customer. We can determine how the system creates a corresponding customer in Financial Accounting, when we process a business partner.

• Define BP Role for Direction Customer to BP: In this IMG activity, we assign BP roles to the account group for the customer master record in which the business partner is to be created when processing the customer.

• Define Number Assignment for Direction BP to Customer: In this IMG activity, we assign account groups for the customer master record to business partner groupings, to ensure that the customer is updated at the same time as the business partner is processed as part of customer integration.

• Define Number Assignment for Customer to BP: In this IMG activity we assign the groupings for the business partner to the account groups for the customer master records to ensure that when we process customers as part of customer integration the system also updates the business partner at the same time.

• Activate/Deactivate Standard Implementation for Mapping in FI-AR: With this IMG activity, we can deactivate the standard implementation of the Business Add-In


[email protected]



Mapping: Business Partner - Customer/Contact Person without making any modifications, in order to activate our own implementation of this BAdI.

References:

• Tables: Business Partner Master Data. Once we completed the above configuration steps, system automatically creates BP when we create customer and vice versa. This configuration is also valid for changes to customer and BP master, system automatically updates master records. Refer Chapter –

2 – Dispute Management.

All the above business processes are comes with screen prints and detail explanations.

Hope you will enjoy it… For any question please mail us [email protected]


[email protected]



Overview of Business Partner

Business Partner may be a person, organization, group of persons, or group of organizations in which a company has a business interest. We use this business object for a variety of business transactions. We create and manage centrally our business partners (BPs) and the roles they assume for our company. For this purpose, we define the general data of the business partner once and we assign business partner roles (BP roles) to the business partner. Specific data is stored for each business partner role. In this way we do not store redundant data, since the general data is independent of a business partner’s function or of application-specific extensions. When we first create a business partner in the system, the BP role General Business Partner is automatically assigned to the business partner. SAP Business Partner is designed to utilize technical benefits such as data integrity and freedom from data redundancy, and to place greater emphasis on aspects relating to customer maintenance and acquisition of new customers. We can create a business partner in different business partner roles, and during the course of the business relationship the business partner can assume other business partner roles. No new data has to be created each time, meaning that redundant data creation and retention is avoided, and there can be no inconsistencies. We need to integrate customers with business partners when we are using FI along with the new dimensional components of the SAP ERP system for example Financial Supply Chain Management (FSCM), Customer Relationship Management (CRM), Supply Chain Management (SCM), and Advanced Planning and Optimization (APO). In FI, we use AR to manage accounting data for all customers. FI does not use the concept of business partners; instead it uses its own customer master records. In FSCM, collection management and credit management uses SAP Business Partner (BP) functionality. SAP systems require BPs that is managed as customers in FI and as business partners in other applications. We use synchronization to replicate customer / business partner. The benefit of synchronization is that we need not update master records separately. After creating the customer master, the system automatically creates the BP and vice versa, which then


[email protected]



reflects any subsequent change to the customer master record. Due to this, the system maintains master data consistency and avoids duplication. Customer integration with BP is bi-directional. While the direction for creation of master data is one-sided (either from customer to BP or BP to customer), any subsequent changes to customer master records are reflected in BP and vice versa. It also applies to the company code level. When the customer master data at company code level is changed, BP master data is also changed at company code level, which means that the same BP can have different payment terms for different company codes.

Business Partner vs. SAP FSCM Collection Management:

We maintain business partner master data specific to collection management by

assigning collection profile. For a business partner to be able to participate in

Collections Management, a collection profile must be assigned to the business partner.

The collection profile determines the list of the collection segments contained therein.

Against collection segment we assign collection group and specialist in charge of

business partner.

Business Partner vs. SAP FSCM Credit Management:

We manage all credit-relevant master data of a business partner in SAP Credit Management (FIN-FSCM-CR). This data includes the current credit limit; one or more externally determined rating values, the risk class, and an order limit. Each of the master data fields has a change history that gives information about the time of the change, the user, and the old and new value. There is also a note function that the credit analyst can use to enter additional information about the business partner. Alternatively, he or she can use a document storage function to store information such as press articles, correspondence, bank information, and rating information. SAP Credit Management (FIN-FSCM-CR) also enables us to include collateral defined for a business partner in the calculation of the credit exposure, meaning that we can also monitor our own company’s risk.


[email protected]



1). SAP Business Partner (SAP BP): The component SAP Business Partner enables

us to create and manage business partners centrally. This is of prime interest if a business partner

plays different roles for a company, such as contract partner and prospect. SAP Business Partner

is designed to utilize technical benefits such as data integrity and freedom from data redundancy,

and to place greater emphasis on aspects relating to customer maintenance and acquisition of new

customers.


[email protected]



Define BP Roles

In this IMG activity we define the business partner roles and their attributes. We also define the role categories with other relevant data. The BP role categories are stored in a table that has the delivery class E. SAP comes with pre-delivered BP Roles, those we will use in this eBook.

• We can configure through IMG // Cross-Application Components // SAP Business

Partner // Business Partner // Basic Settings // Business Partner Roles // Define

BP Roles or Transaction Code: SPRO.

• On Change View “BP Roles”: Overview screen, choose position and enter BP Role

we want view.

Figure - 1-1 – Business Partner Role



[email protected]



SAP comes with pre-delivered BP roles for SAP FSCM Collection Management and

Credit Control. In our eBook, we will use following three business partner roles;

• FLCU00 – CVI : FI Customer

• FLCU01 – CVI : FI Customer

• UDM000 – BP Collection Mgm

Business partner role contains;

• Assignment of business partner role category;

• Assignment of business partner view;

• Assignment of additional business partner role category.

The Business Partner Role Category describes the function of the business partner in a transaction and determines the rights and obligations of the business partner. We can call up various screens (views) in business partner maintenance based on the role category. The Role-View-Allocation takes place in business partner customizing under Role-View-Determine allocation. The business partner must have been created in the corresponding role in order to carry out a certain transaction with a business partner.



[email protected]



F

The above screen contains following important fields;

• BP Role: Function that a business partner takes on, depending on a business transaction

• BP Role Cat: The role category makes it possible for SAP and customer programs to program on the BP role.

• BP View: Controls the screens in the business partner dialog. The BP view enables the screen sequence and the selection of data sets that should be displayed to be established in the context of the Business Data Toolset (BDT). The


[email protected]



BP view is defined in the area menu of the Business Partner in the SAP Easy Access Menu.

Figure - 1-4 – Business Partner Role Collection Management

Define Number Ranges:

In this activity, we define number ranges for business partners. The defined number ranges are

assigned to groupings in the Define groupings and assign number ranges activity. Number

ranges for business partners are valid throughout a client.

• We can configure through IMG // Cross-Application Components // SAP Business Partner

// Business Partner // Basic Settings // Number Ranges and Groupings // Define

Number Ranges or Transaction Code: BUCF.

• Once Create Business Partner screen, choose on Change Interval and

on maintain “Number Range Interval” screen click on Insert Intervals and input

the required number range details. Here we are creating an external number range for our

business partners.

Figure - 1-5 – Business Partner Number Range


[email protected]



• In our business process creation BP should create customer and vice versa, we need create

and assign external number range for both business partner and customer. We can create an

external number range by checking check box against a number range in “Ext” col.

• On “Insert Interval” window choose to insert number range interval.

Figure - 1-6 – Maintain Number Range

Refer Questions and Answers chapter for more information on number ranges.


[email protected]



In this step we have created an external number range and in the subsequent step we will

assign number range to BP grouping. Business partner number ranges are stored in table NRIV

under number range object BU_PARTNER.

Define Groupings and Assign Number Ranges:

In this activity, we maintain groupings for business partners. Business partner grouping

determines (1) business partner number range and (2) The data that is relevant for the

master record

• We can configure through IMG // Cross-Application Components // SAP Business

Partner // Business Partner // Basic Settings // Number Ranges and Groupings //

Define Groupings and Assign Number Ranges or Transaction Code: SPRO.

• Click “New Entries” button and enter following information as indicated below;

Figure - 1-7 – Business Partner Group

The above screen contains following important fields;

• Grouping: Business Partner Grouping. Assign each business partner to a grouping

when you create the business partner. This grouping determines the number range.

For example CUST

• Short Name: Short name of business partner name. For example CUST FSCM BP.

• Description: Descriptions of business partner group. For example CUST FSCM BP.

• Number Range: BP Number Range. Select or choose number range that we have

created in our earlier step. For example CF.

• Ext.Std.Grping: Standard Grouping for External Number Assignment. Means that

this external grouping is used as the standard grouping. The BDT selects this


[email protected]



remove any check mark, (e.g., against source object BP to customer), then changes to the

BP do not reflect in the customer master.

Set BP Role Category for Direction BP to Customer:

In this IMG activity we can define which BP role categories enable customer integration in the

direction from the business partner to the customer. We can determine how the system creates a

corresponding customer in Financial Accounting when we process a business partner.

The BP role categories entered in this IMG activity are customer-based, this means that the

system has to consider customer integration when it processes business partners with a

corresponding BP role. In the IMG activity we can define whether the business partner role

assigned to the BP role category is a mandatory or optional customer business partner role.

In the case of mandatory customer business partner roles the system automatically creates

corresponding customers. In the case of optional customer business partner roles we can

determine whether we want to create a corresponding customer during business partner

processing.

• We can configure through IMG // Cross-Application Components > Master Data

Synchronization // Customer/Vendor Integration // Business Partner Settings // Settings

for Customer Integration // Set BP Role Category for Direction BP to Customer

Figure - 1-11 – Category Direction from BP to Customer


[email protected]



• Same Number: Same Number When Creating Customer/Vendor from a BP. Determines

that when we create a customer master record/ vendor master record as part of

Customer/Vendor Integration we use the same number as the business partner number that

is currently being processed.

In this step we have maintained what would be the customer number when create a business

partner. As per our scenario we want have same number of customer as BP, that’s reason we

have checked same number.

Define Number Assignment for Direction Customer to BP:

In this IMG activity we assign the groupings for the business partner to the account groups for

the customer master records to ensure that when we process customers as part of customer

integration the system also updates the business partner at the same time. With this assignment

we choose whether the customer master record is to be created with an account group with

internal or external number assignment or with identical numbers.

• We have defined and assigned number ranges and groupings for the business partner.

We make these settings in the following IMG activities:

o Define Number Ranges

o Define Groupings and Assign Number Ranges

• We have determined the account groups and the number ranges assigned to the account

groups for creating customer accounts in Customizing for Financial Accounting. We

make these settings in the following IMG activities:

o Define Account Groups with Screen Layout (Customers)

o Create Number Ranges for Customer Accounts

o Assign Number Ranges to Customer Account Groups

• We can configure through IMG // Cross-Application Components // Master Data

Synchronization // Customer/Vendor Integration // Business Partner Settings // Settings

for Customer Integration // Field Assignment for Customer Integration // Assign Keys //

Define Number Assignment for Direction Customer to BP

• On Change View of Number Assignment for Direction Customer to BP”: Overview screen,

choose New Entries.

• On New Entries: Overview of Added Entries, enter data as shown below;

Figure - 1-15 – Define Number Assignment Direction Customer > BP


[email protected]



Overview of Dispute Management

SAP Dispute Management is used to manage and resolve customer disputes efficiently.

Managing disputes is going to involve multiple departments like sales, finance, logistics etc.

SAP Dispute Management allows integration between all these departments along with dispute

case tracking and managing in a centralized system. The whole process of dispute case

management can be automated to reduce manual intervention and easier collaboration between

multiple departments.

SAP Dispute Management supports the processing of receivables related disputes. Because

customers typically do not notify their suppliers in advance about payment reductions or

nonpayment, many vendors must deal with huge numbers of payment deductions or delays.

The result is declining cash-collection percentages and eroding day sales outstanding (DSO)

averages.

SAP Dispute Management is an industry-leading solution for integrating dispute resolution into the order-to-cash cycle. By helping we resolve disputes earlier in the settlement process, SAP Dispute Management can significantly reduce collection costs. It can also facilitate cooperation across department boundaries, considerably increasing operational efficiency. Customer disputes arise for many reasons, including damaged goods or incorrect bills. SAP Dispute Management lets we process these disputes using a different reason code for each type of business transaction that may cause a complaint. These reason codes could include differences in price, quantity, quality, or delivery time. The system logs the status of a dispute as either open or completed. The status, along with the reason codes, controls subsequent actions on the dispute – such as notifying employees via workflow processes or generating an e-mail to the customer.

With SAP Dispute Management, all information related to a dispute is summarized in one central business object: the dispute case. This new SAP object is like an electronic folder for bundling all the information related to a customer dispute. In a single view, we can see the reason code, processor, disputed amount, and amount paid. We can also see all actions that have been taken to resolve the dispute, as well as all customer correspondence. SAP Dispute Management allows our finance department to analyze a dispute case and examine the invoices, notes, and accounting records that are linked to a particular customer. The drill-down capabilities of this application allow users to view information from other SAP FSCM applications – such as SAP Biller Direct, SAP Credit Management, and SAP Collections Management.


[email protected]



• In this step we want to create a new element type for search profile. Choose

UDM_SPS_MY_CASES and right click. Choose copy option to create our own element

type.


[email protected]



• By check and un-checking “Sel.Opt” field on above scree we can decide what field should

be available for selection.

• Now navigate to modifiable field. On Change View Modifiable Fields Overview screen we

can see modifiable fields. Here we can enter additional fields by choosing New Entries.

Figure: 2- 20: Search Profile – Modifiable Fields

In this step we have created a case search profile and maintained its attributes such as what

fields are available for selection and what fields can modifiable.

Create Function Profile:

We can use this IMG activity to assemble the functions that we want to provide for our function profile. All case types to which we then assign this function profile provide the corresponding functions and display the relevant case components. We can also determine the sequence of the pushbuttons; create separators between them, and group pushbuttons for dropdown menus. If we have not defined and customer-defined functions, we recommend that we use the following function profile:

• FIN_DISPUTE, if we use Accounts Receivable Accounting (FI-AR)

• FICA_FKT, if we use Contract Accounts Receivable and Payable (FI-CA)


[email protected]



The collection specialist can access an overview of open resubmissions, which serves as a reminder to deal with activities still outstanding. Promises to Pay, Dispute Cases, Resubmissions, and Customer Contacts The collection specialist documents the outcome of a customer contact in the collections management system. The collections specialist can use various options, depending on the progress of the contact. The collection specialist creates promises to pay submitted by the customer by selecting the invoice(s) for which payment is promised and then entering the promised payment day, the promised amount, the contact person, and a note (optional). The application determines and proposes the promised amount automatically from the parts of the invoice that are still open. The user can over - write the amount. If the customer proposes a different amount, the collection specialist can enter this amount and automatically distribute it to the invoices, for example, by using the due date. The collections specialist can also enter an amount for each invoice manually. The application creates a separate promise to pay for each invoice when the collections specialist saves it and monitors whether the promise is kept. If we have configured the application appropriately, it excludes invoices with open promises to pay from dunning up to the promised payment day plus any days’ grace granted. The application supports users by having incoming payments update promises to pay in real time as follows: • If the customer pays the agreed-upon amount within the time promised, the

promise to pay receives the status of Kept. • If the customer pays only part of the amount promised within the time agreed, the

promise to pay receives the status of partially kept. For payments that come in after the promised payment date, the promise to pay updates only the Paid and Paid on fields.

• If no incoming payment is posted within the time agreed for the invoice, a daily valuation run assigns the promise to pay the status of Broken. Broken promises to pay mean the assignment of a corresponding collection rule in the collection strategy and that the customer appears repeatedly in the work list and is contacted again. The collection specialist can use the information available to notify the customer of


[email protected]



o Resubmission reason

o Reason for note

• We can configure through IMG // FSCM // Collections Management // Basic Settings for

Collections Management // Resubmit // Define Resubmission Reason.

• On Change view Maintenance of Resubmission Reasons: Overview of Selected screen enter

following data.

Figure 3 – 34 : Resubmission Reason

In this configuration step we have maintained resubmission reason for resubmission reason codes.

Define Status for Dispute Cases To Be Collected:

In this IMG activity we will define the status for dispute cases to be collected. When calculating the amount to be collected, the system considers the status of the dispute cases involved by transferring the amount of the dispute cases to be collected to the amount to be collected.

• We can configure through IMG // FSCM // Collections Management // Basic Settings for

Collections Management // SAP Dispute Management Integration // Define status for

dispute cases to be collected.

• In Determine Work Area: Entry window, enter case type

Figure 3 – 35 : Status for Dispute Case 1


[email protected]



2. Choose Create Dispute Case.

3. In the dialog box, enter the required data (attributes, notes).

4. If the sub ledger accounting document contains exactly one residual item, enter

the required data on the detail screen for creating dispute cases.

5. If the sub ledger accounting document contains several residual items, we can

decide in the dialog box which dispute cases we want to create. Choose Detail

View: Dispute Case to enter notes and additional attributes on the respective

detail screen.

6. Save the dispute case(s).

F-28 - Creating Dispute Cases during Clearing of Open Items:

When we clear open items and simultaneously create residual items, we can create dispute

cases for the resulting residual items.

Prerequisites

The open item to be cleared has not been included in a dispute case as a disputed object.

In other cases, the new residual item is removed from the existing dispute case using the same

procedure. We recognize this situation from the title of the dialog box: Split instead of Create.

For more information about splitting dispute cases, see Effects of Clearing on Dispute Cases.

Procedure

1. Start the clearing transaction (for example, incoming payment, transfer posting) as

usual, select the open items to be cleared, and on the tab page Residual Items,

create the required residual items (there may be several for one item selected).

2. Choose Create Dispute Case.

3. The subsequent dialog is dependent on the number of residual items created:

a. If we have created one residual item, the detail screen for creating dispute

cases appears. Enter the required data and choose Continue.


[email protected]



• Now to we can choose SAVE icon to save the addition of open items to an existing dispute

case.

FDM_AUTO_CREATE - Automatic Creation of Dispute Cases:

With this program we can create dispute cases for residual items that have arisen from

automatic incoming payments (account statement, lockbox), from check deposits, or in post

processing. For more information, see the documentation for this program.

Activities

1. Call up the program:

With effect from mySAP ERP 2004, the program is in the application menu. From

the SAP Easy Access menu, choose Accounting → Financial Supply Chain

Management → Dispute Management → Periodic Processing in Accounting → Automatic Creation of Dispute Case or Transaction code : FDM_AUTO_CREATE.


[email protected]



• Promised by: is meant for customer representative who promised to pay

Figure: 9 - 14 Process Receivable / Promise To Pay

Once we created promised to pay, we can see promise to line item in “Promise to Pay” tab

pages.


[email protected]



Business Partner Tables

BUT000_BCS Persistence of a BAS Address

BUT000_EBP_G Table for Lock Object EBP_G

BUT000_TD BP: General Data I, Shadow Table Time Depe

BUT001 BP: General data II

BUT010 GP: old, do not use ==> BUT020

BUT020 BP: Addresses

BUT021 BP: Address usages

BUT021_FS Time-Dependent Address Usage

BUT030 BP Where-Used List: Usages

BUT030G BP Where-Used List: Generic Nodes

BUT030GT BP Where-Used List: Generic Nodes, Text

BUT030T BP Object Usage: Application Table, Texts

BUT050 BP relationships/role definitions: General

BUT050_ADGUID46C BP Rel Addr Display -> AddrGuid

BUT050_CD BP Rel./Role Determination:Index Table for

BUT051 BP Relationship: Contact Person Relationship

BUT052 BP Relationship: Addresses

BUT053 BP Relationship: Company Interest

BUT054 BP Relationship (not used yet)

BUT0BANK Business Partner: Bank Data

BUT0BK BP: Bank Details

BUT0BK_SHD Shadow table for BUT0BK (IBAN only)

BUT0BKU BP: Bank Details Usages

BUT0CC BP: Payment Cards

172275575 sample-fscm-config-user-guide (2)

Economy & Finance

Transcript of 172275575 sample-fscm-config-user-guide (2)