Collection - Management - Config Sarva PDF

Collection Management
© 2012 sapficoconsultant.com All rights reserved. No part of this material should

be reproduced or transmitted in any form, or by any means, electronic or
mechanical including photocopying, recording or by any information storage
retrieval system without permission in writing from www.sapficoconsultant.com
“SAP” is a trademark of SAP AG, Neurottstrasse 16, 69190 Walldorf, Germany.

SAP AG is not the publisher of this material and is not responsible for it under
any aspect.
Warning and Disclaimer
This product is sold as is, without warranty of any kind, either express or implied.
While every precaution has been taken in the preparation of this material,
www.sapficoconsultant.com assumes no responsibility for errors or omissions.
Neither is any liability assumed for damages resulting from the use of the
information or instructions contained herein. It is further stated that the publisher
is not responsible for any damage or loss to your data or your equipment that
results directly or indirectly from your use of this product.
Page 2 of 125 www.sapficoconsultant.com

TABLE OF CONTENTS
1. Basic Settings for Collections Management................................................... 4
1.1 Basic Data ................................................................................................... 4
1.1.1 Define Company Codes for SAP Collections Management .................. 4
1.2 Collection Strategies ................................................................................... 6
1.2.1 Define Basic Rules for Collection Strategies......................................... 6
1.2.2 Collection Rules .................................................................................... 9
1.2.3 Process Strategies .............................................................................. 15
1.2.4 Define Priorities .................................................................................. 29
1.2.5 Define Derivation of Priority ................................................................ 30
1.3 Organizational Structure ............................................................................ 32
1.3.1 Define Collection Segments................................................................ 32
1.3.2 Define Collection Profiles .................................................................... 36
1.3.3 Define Collection Groups .................................................................... 39
1.3.4 Assign Collection Groups to Collection Segments .............................. 42
1.4 Promise to Pay .......................................................................................... 44
1.4.1 Create RMS ID ................................................................................... 44
1.4.2 Create Attribute Profile........................................................................ 54
1.4.3 Create Text Profile ............................................................................ 62
1.4.4 Create Status Profile ........................................................................... 67
1.4.5 Define Number Range Interval for Case ............................................. 73
1.4.6 Create Function Profile ....................................................................... 75
1.4.7 Define Case Types ............................................................................. 79
1.4.8 Define Automatic Status Changes ...................................................... 81
1.4.9 Define Text ID for Notes ..................................................................... 84
1.5 Customer Contacts.................................................................................... 86
1.5.1 Define Result of Customer Contact .................................................... 86
1.6 Resubmit ................................................................................................... 87
1.6.1 Define Resubmission Reason............................................................. 87
1.7 SAP Dispute Management Integration ...................................................... 89
1.7.1 Define Status for Dispute Cases to Be Collected................................ 89
1.8 Worklist...................................................................................................... 92
1.8.1 Define Distribution Procedure ............................................................. 92
2. Integration with Accounts Receivable Accounting........................................... 93
2.1 Activate SAP Collections Management ..................................................... 93
2.2 Master Data Distribution ............................................................................ 95
2.2.1 Activate/Deactivate Standard Implementation for Mapping in FI-AR .. 95
2.2.2 BAdI: Mapping of Master Data ............................................................ 97
2.3 Distribution of Data in Collections Management ...................................... 120
2.3.1 Activate Distribution per Company Code .......................................... 120
2.3.2 Define Relevant Fields for Document and Master Record Changes . 122
2.3.3 Harmonize Dunning Levels ............................................................... 123
2.4 Promise to Pay ........................................................................................ 124
2.4.1 Make Settings for Promise to Pay ..................................................... 124

1. Basic Settings for Collections Management
1.1 Basic Data
1.1.1 Define Company Codes for SAP Collections Management
SAP Customizing Implementation Guide Financial Supply Chain Management

Collections Management Basic Settings for Collections Management
Basic Data Define Company Codes for SAP Collections Management
Here we define the company codes that will be using the SAP Collections
Management.

Click on
Update the following:-
Click on

1.2 Collection Strategies
1.2.1 Define Basic Rules for Collection Strategies

Collection Strategies Basic Rules Define Basic Rules
Here we can define new basic rules in addition to the basic rules delivered.
These basic rules are then used to define collection rules.
We work with the SAP standard rules.

Let us check a few rules:-
Double Click


1.2.2 Collection Rules

Collection Strategies Collection Rules Define Collection Rules
Here we create the collection rules to be used later for the definition of collection
strategies
When work lists are created, the collection rules lead to a prioritization of the
business partners. The system checks the conditions of all basic rules that make
up the individual collection rule. If all conditions are fulfilled, the priority in the
worklist increases accordingly.
We work with the standard collection rules.


Double Click




1.2.3 Process Strategies

Collection Strategies Process Strategies
Here we create the collection strategies.
Collection strategies are used to
• Prioritize customers on the work list

• Define the currency in which the amounts are to be displayed in the work
list
• Determine the time intervals with which the customers payables are to be
sorted
• Define the type of integration with dunning
• Determine the influence of the terms of payment on Collections

Management
All specialists in a collection group collect open receivables from customers with
the same strategy. Therefore, you have to assign a collection strategy to each
collection group.
Click

Click


Update the valuation points:-
Further click

Likewise also update all other collection rules as follows:-

Double Click

Double Click
Select

Double click

Click
Double Click

Click
Double Click
Double click in the field

Select

Click
Double Click
Click

Click on

1.2.4 Define Priorities

Collection Strategies Priorities Define Priorities
Here we can define priorities possible for work list items.
We work with SAP standard priorities.

1.2.5 Define Derivation of Priority

Collection Strategies Priorities Define Derivation of Priority
Valuation points are calculated from the key figures of the customers in
accordance with the strategy.
The system calculates the valuation points automatically based on the maximum
points derived.
Here we define the percentage valuation which leads to which priority of the
related work list item.

In the SAP standard, the priorities are distributed to the percentage valuation on
a linear basis:
Let us understand how the system will derive the priority:-
For example, in the strategy we have defined we assign the valuation points in
accordance with the importance of each rule.
Collection Rule Valuation Name of condition

CR00000008 20 Total amount to be collected larger than 0.00
INR
CR00000013 20 Broken promises to pay with level higher than 0:
Total amount larger than 0.00 INR
CR00000019 20 No successful customer contact since one day
CR00000003 20 Individual items overdue since one day: Amount
larger than 0.00 INR
CR00000002 10 Total of all items overdue since one day: Total
amount larger than 0.00 INR
CR00000008 10 Total amount to be collected larger than 0.00
INR
If a customer fulfills the first 4 rules the valuation determined by the system is 80.
The priority determined will be 1 – Very High.

1.3 Organizational Structure
1.3.1 Define Collection Segments

Organizational Structure Define Collection Segments
Here we define which collection segments are to be used in SAP Collections

Management.
Collection segments group company codes of a company from the view of SAP
Collections Management so that transaction data (open items, dispute cases,
promise to pay) of a business partner from these company codes can be
considered together.
The collection segment also determines which data from SAP Credit
Management is to be considered for customers in this segment. For each

collection segment, specify the credit segments from which the system is to
determine, for example, the credit limit utilization of the customer.
Click on
Click on
Select
Double Click

Click on
Click on
Click
Click

Click on
Click

1.3.2 Define Collection Profiles

Organizational Structure Define Collection Profiles
Here we define the collection profiles that can be assigned to the business
partners in SAP Collections Management.
Collection profiles are a grouping of collection segments and thus split the
company codes that participate in SAP Collections Management. We can
determine how the company codes are split in a profile and which company
codes are not included in a profile in the view Assign Collection Segments to
Profile using the function Assignment Status of Company Codes.
Once we have assigned a profile to a business partner, we can define, for each
collection segment, the (group of) collection specialists that are to contact the
business partner in this segment.

Click on
Click on

Select
Double Click
Click on

Click on
1.3.3 Define Collection Groups

Organizational Structure Define Collection Groups
Here we define the groups of collection specialists that are to contact customers.
We assign collection specialists to each group using their user names.
All specialists in a collection group collect open receivables from customers with
the same strategy. We therefore assign a collection strategy to each group.

Click on
Click on
Click

Click on
Click on

1.3.4 Assign Collection Groups to Collection Segments

Organizational Structure Assign Collection Groups to Collection Segments
Here we define which contact groups are to contact business partners in the
respective collection segments.
We define one of the groups as default group. The system proposes this per
related segment when we enter a profile in the business partner master record.
This ensures that in each segment, a group of collection specialists is
responsible for the customer.

Select
Double Click
Click on
Click on

1.4 Promise to Pay
1.4.1 Create RMS ID

Promise to Pay Create RMS ID
Here we define one or more Records Management Systems (RMS) for promises
to pay.
The standard delivery contains the RMS UDM_COLLECTIONS.
We can use the UDM_COLLECTIONS unmodified or create our own RMS.

Double Click
Click to expand

Click on

Click on
Click on


Position the cursor on


Click on

Click on

Click on

1.4.2 Create Attribute Profile

Promise to Pay Create Attribute Profile
Here we define the properties of the attributes in the case that represents the
promise to pay.
.
We copy from the sample attribute profile FIN_PPAY.
Select

Click

Click

Click

Click

Click on
Select

Double click
Double click


1.4.3 Create Text Profile

Promise to Pay Text Profile Create Text Profile
Here we define which text IDs we want to use for your notes for a promise to pay.
This text profile is assigned to the case type for promises to pay later.
We copy the sample customizing text profile FIN_PPAY
Select
Click

Click

Click

Click

Click on
Select
Double Click

1.4.4 Create Status Profile

Promise to Pay Create Status Profile
Here we create a status profile for the promise to pay.
The status profile for the promise to pay must contain at least the following 3
statuses:
• Status for the active promise to pay: System status 001 or 002
• Status for the confirmed promise to pay: System status 008
• Status for the voided promise to pay: System status 009

When you create the promise to pay, it receives the status with the lowest
number. Assign system status 001 or 002 to this status.
The status for the confirmed promise to pay is set automatically only.
The status profile is assigned to the case type for promises to pay
We copy from the sample status profile FIN_PPAY that contains the above-
mentioned obligatory system statuses.

Select
Click


Click
Click

Click on
Select
Double Click

1.4.5 Define Number Range Interval for Case

Promise to Pay Define Number Range Interval for Case
Here we can define number range intervals for case.
We use the existing number range interval.


1.4.6 Create Function Profile

Dispute Management Dispute Case Processing Function Profile Create
Function Profile
We copy the standard function profile FIN_PPAY.
Here we can also determine the sequence of the pushbuttons, create separators
between them, and group pushbuttons for dropdown menus.
Select
Click

Click

Click
Click

Click on

1.4.7 Define Case Types

Promise to Pay Define Case Types
Here we define the case types for the promise to pay.
The sample Customizing contains the case type F_PP.
We create a new case type.
Click on

Click on

1.4.8 Define Automatic Status Changes

Promise to Pay Process Integration Define Automatic Status Changes
Here we define a status for the automatic confirmation of promises to pay.
The status is used in the following cases:

When the promise to pay is withdrawn
When a promise to pay is replaced by a new one
When the invoice that the promise to pay referred to has been cleared
and, as a result, program FDM_P2P_AUTO_CONFIRM confirms the
promise to pay
In the status profile for the promise to pay, we must have defined a status with
system status 008.
Click on

Take a drop down in auto. Confirmation
Select

Click on

1.4.9 Define Text ID for Notes

Promise to Pay Process Integration Define Text ID for Notes
Using the transaction UDM_SPECIALIST - My Worklist, you can add notes to a

promise to pay. Here we define which note category is used.
Click on

Click on

1.5 Customer Contacts
1.5.1 Define Result of Customer Contact

Customer Contacts Define Result of Customer Contact
Here we can define the values allowed for the Result of Customer Contact.
We use the SAP standard values.
When we create a customer contact, we select one of the values defined here for
the result.
Explanation for each result:-
Remove indicator: If we create a customer contact with a result for which

we have set this indicator, the system changes the status of the work list
item to Completed.
Reached indicator: The basic rules BR00000019 or BR00000020

valuate a customer contact as successful if you have set the Reached
indicator for the result.
The worklist statistics provide information about the number of customer
contacts where the customer was reached or not reached. For this
purpose, the Reached indicator of the result is also evaluated.

1.6 Resubmit
1.6.1 Define Resubmission Reason

Resubmit Define Resubmission Reason
When we create a resubmission, we enter a reason for resubmission.
Here we can define the possible values for the resubmission reason.
We work with SAP standard values.


1.7 SAP Dispute Management Integration
1.7.1 Define Status for Dispute Cases to Be Collected

SAP Dispute Management Integration Define Status for Dispute Cases To Be
Collected
Here we 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.
Click



Click on
1.8 Worklist
1.8.1 Define Distribution Procedure

Worklist Distribution Method Define Distribution Procedure
We work with the standard distribution method.

We can also define a distribution procedure in the customer name range through
customer enhancement.
2. Integration with Accounts Receivable Accounting
2.1 Activate SAP Collections Management

Collections Management Integration with Accounts Receivable
Accounting Activate SAP Collections Management
Here we activate the component SAP Collections Management.
In SAP standard delivery, SAP Collections Management is not activated.


2.2 Master Data Distribution
2.2.1 Activate/Deactivate Standard Implementation for Mapping in FI-

AR

Accounting Master Data Distribution Mapping of Master Data
Activate/Deactivate Standard Implementation for Mapping in FI-AR
Here we deactivate the standard implementation and activate our own

implementation

Click

2.2.2 BAdI: Mapping of Master Data

Accounting Master Data Distribution Mapping of Master Data BAdI:
Mapping of Master Data
We use this Business Add-In (BAdI) in the component SAP Collections

Management (FIN-FSCM-COL).
It maps the keys of the master data in Financial Accounting to the keys of the
master data of Collections Management.
The BAdI provides four methods for mapping the master data keys:
• MAP_PARTNER_2_CUSTOMER:
Mapping of business partner number (Partner-ID) to customer number
(KUNNR)
• MAP_CUSTOMER_2_PARTNER:
Mapping of customer number (KUNNR) to business partner number
(Partner-ID)
• MAP_CONTACTPARTNER_2_CONTACT:
Mapping of business partner number (Partner-ID) to contact person
number (PARNR)
• MAP_CONTACT_2_CONTACTPARTNER:
Mapping of contact person number (PARNR) to business partner number
(Partner-ID)
We create and activate our own implementation; the whole implementation is

based on the fact that the customer number and the business partner are the
same. Once

Click


Double Click


Click on

Click on

Double Click

Select the partner number from table BUT000 according to the imported partner
GUID and return partner number on export parameter E_CUSTOMER.

Click on
Click
Double Click
Mapping of customer number (KUNNR) to business partner number (partner-ID)
Select the Partner GUID from BUT000 according to provided customer number.
As it is assumed that the numbers of business partner and customer are equal,
the selected entry for BUT000 will be the identical. Return the partner GUID with
export parameter E_PARTNER_GUID.


Click on

Click

Double Click
Mapping of business partner number (partner-ID) to contact person number

(PARNR)
Copy the standard implementation for this method.

Click on

Click
Double Click
Method MAP_CONTACT_2_CONTACTPARTNER: Mapping of contact person

number (PARNR) to business partner number (partner-ID)
Copy the standard implementation for this method.


Copy and update from the standard implementation.
Click on

Click
Double click

Method MAP_CUSTOMER_2_PARTNERID
As it is assumed that the number is equal for customer and business partner, the
numbers need to be mapped with import and export parameter

Click on

Click on to activate the BADI (Business Add-In).

The BADI is now active as can be seen below.

2.3 Distribution of Data in Collections Management
2.3.1 Activate Distribution per Company Code

Accounting Distribution of Data in Collections Management Activate
Distribution per Company Code
Here we activate data distribution for those company codes that participate in
Receivables Processing using the component SAP Collections Management.
The data of the company codes affected is transferred with the program
Distribution of FI-AR Data in Collections Management
(FDM_COLL_SEND_ITEMS).

Click on

Click on
2.3.2 Define Relevant Fields for Document and Master Record

Changes

Accounting Distribution of Data in Collections Management Define Relevant
Fields for Document and Master Record Changes
Customer master records that are important for Collections Management are
logged (the relevant fields in the standard are defined in system table
FDM_COLL_SFIELD).

Configuration here is needed if there are changes to other fields in the customer
master and we want to transfer this additional information to Collections
Management and display it in the worklist
Data is recreated in collections management through report FDM_COLL_SEND_ITEMS
We do no do any configuration here.
2.3.3 Harmonize Dunning Levels

Accounting Distribution of Data in Collections Management Harmonize
Dunning Levels
Here we can define harmonized dunning levels for each dunning procedure.
If we use different dunning procedures in Accounts Receivable Accounting, we

may have to harmonize the dunning levels of the corresponding dunning
procedures so that the dunning levels can be compared in Collections
Management and can be used uniformly in basic rules.

We do not have different dunning levels and hence do not need this
configuration.
2.4 Promise to Pay
2.4.1 Make Settings for Promise to Pay

Accounting Promise to Pay Make Settings for Promise to Pay
Here we define which case type the system is to use for promises to pay.
We can also define the number of tolerance days to be considered in the

valuation of the state of the promise to pay.
Click on

Click on
Congrats, you are now ready with the collections management configuration!

Collection - Management - Config Sarva PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Collection - Management - Config Sarva PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Collection Management

© 2012 sapficoconsultant.com All rights reserved. No part of this material should

“SAP” is a trademark of SAP AG, Neurottstrasse 16, 69190 Walldorf, Germany.

Warning and Disclaimer

Page 2 of 125 www.sapficoconsultant.com

Page 3 of 125 www.sapficoconsultant.com

1. Basic Settings for Collections Management

1.1 Basic Data

1.1.1 Define Company Codes for SAP Collections Management

SAP Customizing Implementation Guide Financial Supply Chain Management

Page 4 of 125 www.sapficoconsultant.com

Update the following:-

Page 5 of 125 www.sapficoconsultant.com

1.2 Collection Strategies

1.2.1 Define Basic Rules for Collection Strategies

SAP Customizing Implementation Guide Financial Supply Chain Management

We work with the SAP standard rules.

Page 6 of 125 www.sapficoconsultant.com

Let us check a few rules:-

Page 7 of 125 www.sapficoconsultant.com

Page 8 of 125 www.sapficoconsultant.com

1.2.2 Collection Rules

SAP Customizing Implementation Guide Financial Supply Chain Management

We work with the standard collection rules.

Page 9 of 125 www.sapficoconsultant.com

Page 10 of 125 www.sapficoconsultant.com

Page 11 of 125 www.sapficoconsultant.com

Page 12 of 125 www.sapficoconsultant.com

Page 13 of 125 www.sapficoconsultant.com

Page 14 of 125 www.sapficoconsultant.com

1.2.3 Process Strategies

SAP Customizing Implementation Guide Financial Supply Chain Management

Here we create the collection strategies.

Collection strategies are used to

• Prioritize customers on the work list

Page 15 of 125 www.sapficoconsultant.com

• Define the type of integration with dunning

• Determine the influence of the terms of payment on Collections

Page 16 of 125 www.sapficoconsultant.com

Update the following:-

Page 17 of 125 www.sapficoconsultant.com

Page 18 of 125 www.sapficoconsultant.com

Update the following:-

Update the valuation points:-

Page 19 of 125 www.sapficoconsultant.com

Likewise also update all other collection rules as follows:-

Page 20 of 125 www.sapficoconsultant.com

Page 21 of 125 www.sapficoconsultant.com

Page 22 of 125 www.sapficoconsultant.com

Page 23 of 125 www.sapficoconsultant.com

Page 24 of 125 www.sapficoconsultant.com

Update the following:-

Update the following:-

Double click in the field

Page 25 of 125 www.sapficoconsultant.com

Page 26 of 125 www.sapficoconsultant.com

Update the following:-

Page 27 of 125 www.sapficoconsultant.com

Page 28 of 125 www.sapficoconsultant.com

1.2.4 Define Priorities

SAP Customizing Implementation Guide Financial Supply Chain Management

Here we can define priorities possible for work list items.

We work with SAP standard priorities.