w23 credit dispute amp collections management

SAP ECC 5.00

March 2006

English

W23: Credit, Dispute, and Collections Management

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

Building Block Configuration Guide

SAP Best Practices W23: Credit / Dispute / Collections Management: Configuration Guide

© SAP AG of 23

Copyright

© Copyright 2006 SAP AG. All rights reserved.

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

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

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

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

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

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

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

Java is a registered trademark of Sun Microsystems, Inc.

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

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

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


© SAP AG of 23

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

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

Cross-references to other documentation.

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

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

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

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

ENTER key.

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

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


© SAP AG of 23

Contents

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

2 Preparation ............................................................................................................................... 5

2.1 Prerequisites .................................................................................................................. 5

3 Customizing .............................................................................................................................. 6

3.1 Make Settings for Promise to Pay .................................................................................. 6

3.2 Basic Config - Credit Management 1 ............................................................................. 6

3.2.1 BDT: Event Function Modules ................................................................................... 6

3.2.2 BDT: Object Parts ...................................................................................................... 7

3.2.3 BDT: Screen Sequences ........................................................................................... 7

3.2.4 SAP GP Dialog: Sequence of Dialog Extensions ...................................................... 8

3.2.5 Define BP Roles ......................................................................................................... 8

3.2.6 Define Application Transactions ................................................................................ 9

3.2.7 Configure Field Attributes per BP Role .................................................................... 10

3.3 Basic Config - Credit Management 2 ........................................................................... 10

3.3.1 Applications .............................................................................................................. 10

3.3.2 Define Events and Follow-On Processes ................................................................ 11

3.3.3 Define Formulas ....................................................................................................... 12

3.3.4 Define Info Categories ............................................................................................. 13

3.3.5 Create Rule for Scoring and Credit Limit Calculation .............................................. 14

3.3.6 Define Rating Procedure ......................................................................................... 15

3.4 Credit Management 3 ................................................................................................... 17

3.4.1 Create Credit Segments .......................................................................................... 17

3.4.2 Define Customer Credit Group ................................................................................ 18

3.4.3 Create Risk Classes ................................................................................................ 18

3.4.4 Define Blocking Reasons ......................................................................................... 19

3.4.5 Define Checking Rules ............................................................................................ 20

3.4.6 Define Events and Follow-on Processes ................................................................. 21

3.4.7 Activate SAP Collections Management ................................................................... 22

3.5 Master Data .................................................................................................................. 22

3.5.1 Pricing Condition Maintenance ................................................................................ 22

3.6 Miscellaneous .............................................................................................................. 23

3.6.1 Activate FSCM Programs (RFOSXEXTEND, BALVBUFDEL) ................................ 23


© SAP AG of 23

W23: Credit, Dispute, and Collections Management

This scenario demonstrates several business processes in Credit Management, Dispute Management, and Collections Management within the SAP Financial Supply Chain Management (FSCM) module. The processes show how a company can optimize the financial and information flows with its business partners.

1 Purpose

This configuration guide provides the information you need to set up the configuration of this building block manually.

If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the installation guide of this building block.

2 Preparation

2.1 Prerequisites

If you want to use this building block, you must first install the following building blocks:

Building Block Description

B32 Best Practices R/3 Installation

J02 Organizational Structure

N70 Financial Accounting

N71 Basic Cost Accounting

N74 Cost of Sales Accounting

J05 Materials Management

J04 Sales and Distribution

J30 Master Data

W21 Dispute Management

W40 Order to Cash


© SAP AG of 23

3 Customizing

3.1 Make Settings for Promise to Pay

Use

In this IMG activity, you define which case type the system is to use for promises to pay.

You can also define the number of tolerance days to be considered in the valuation of the state of the promise to pay.

Procedure

1. Access the activity as follows:

Transaction Code SM30 using Customizing Object V_TFDM_P2PCC

IMG Menu Financial Supply Chain Management → Collections Management → Receivables Processing in Accounts Receivable Accounting → Make Settings for Promise to Pay

2. On the Display View “Settings for Promise to Pay”: Overview screen, choose New Entries, and make the following entries:

CoCd Company name Case Type Tolerance Days

BP01 Company Code BP01 Promise to Pay 5

3. Choose Save.

3.2 Basic Config - Credit Management 1

3.2.1 BDT: Event Function Modules

Procedure


Transaction Code SM30 using Customizing Object V_TBZ1F

2. On the Determine Work Area screen enter the values for the following data from the table below: - BDT Object - Event - Application Object

3. On the Change View “Assign Event -> Function Module” Overview screen enter the following data:

BDT Object Event

Application Object

Item number Function module name Appl Call


© SAP AG of 23

BUSS ARCH3 BUPA 105000 UKM_BUPA_EVENT_ARCH3 UKM X

BUSS AUTH1 BUPA 105000 UKM_BUPA_EVENT_AUTH1 UKM X

BUSS DCUAC BUPA 1005000 UKM_BUPA_EVENT_DCUAC UKM X

BUSS DINP1 BUPA 105000 UKM_BUPA_EVENT_DINP1 UKM X

BUSS DINP2 BUPA 1005000 UKM_BUPA_EVENT_DINP2 UKM X

BUSS DLVE1 BUPA 1005000 UKM_BUPA_EVENT_DLVE1 UKM X

BUSS DLVE1 BUPA 1005100 UKM_BUPA_BP1012_EVENT_DLVE1 UKM X

BUSS DLVE2 BUPA 1005000 UKM_BUPA_EVENT_DLVE2 UKM X

BUSS DSAVC BUPA 1005000 UKM_BUPA_EVENT_DSAVE UKM X

BUSS DTAKE BUPA 1005000 UKM_BUPA_EVENT_DTAKE UKM X

BUSS ISDST BUPA 105000 UKM_BUPA_EVENT_ISDST UKM X

4. Choose Save (Ctrl+S).

5. Choose Back (F3).

3.2.2 BDT: Object Parts

Procedure


Transaction Code SM30 using Customizing Object V_TBZ0C

2. On the Determine Work Area screen enter the values for the following data from the table below: - Application Object - Object part

3. On the Change View “Assign Object Part-> CallingApplication” Overview screen enter the following data:

Application Object

Object part Application

Call only?

BUPA UKM000 UKM



3.2.3 BDT: Screen Sequences

Procedure


Transaction Code SM30 using Customizing Object V_TBZ3K

2. On the Determine Work Area screen enter the values for the following data from the table below: - Application Object - Screen sequence


© SAP AG of 23

3. On the Change View “Assign Screen Sequence -> Screens” Overview screen enter the following data:

Application Object

Screen sequence Item Screen

BUPA BUP001 4000000 UKM100



3.2.4 SAP GP Dialog: Sequence of Dialog Extensions

Procedure


Transaction Code SM30 using Customizing Object V_TBZJ1C

2. On the SAP GP Dialog: Sequence of Dialog Extension screen enter the following data:

Key of Additional Header Data Item Number Extension Active

UKM110 001 X



3.2.5 Define BP Roles

Use

In this IMG activity you define the business partner roles and their attributes.

You also define the role categories with other relevant data.

Procedure


Transaction Code SM34 using Customizing Object BUPA_TB003

IMG Menu Flexible Real Estate Management (Enterprise Extension) → Business Partner → General Settings for Business Partner → Business Partner → Basic Settings → Business Partner Roles → Define BP Roles

2. On the Change View “BP Roles”: Overview screen, choose New Entries and enter the following:

BP Role UKM00

Title Credit Mgt Business Part.


© SAP AG of 23

Description Credit Mgt Business Partner

BP Role Cat. UKM000

Std. Assignment BP Role -> BP Role Cat.

X

BP View UKM000

3. Choose Save, and choose Back.

4. Select the row just entered, and choose Details (Ctrl+Shift+F2).

5. On the Change View “BP Roles”: Details screen, choose New Entries and enter the following:

BP Role Cat. UKM00

Title Credit Mgt Business Part.


Diff. Type 9

Organization X

Person X

Group X

6. Choose Save.

3.2.6 Define Application Transactions

Use In this IMG activity you define the business partner application transactions. This allows you to establish the context with which you start business partner maintenance, depending on the required activity and the assigned business partner roles.

Procedure


Transaction Code SM30 using Customizing Object V_TB109

IMG Menu Flexible Real Estate Management (Enterprise Extension) → Business Partner → General Settings for Business Partner → Business Partner → Basic Settings → Business Partner Roles → Define Application Transactions

2. On the Change View “SAP BP: Application Transactions”: Overview screen, choose New Entries and enter the following:

Transaction Code UKM_BP


© SAP AG of 23

Transaction text Credit Management Business Partner

3. On the New Entries: Details of Added Entries screen enter the following data:

Transaction Code UKM_BP

BP Role Category UKM000

4. Choose Save.

3.2.7 Configure Field Attributes per BP Role

Use

In this activity you define fields in master record maintenance for the BP Role.

Procedure


Transaction Code SM30 using Customizing Object V_TB108

IMG Menu Flexible Real Estate Management (Enterprise Extension) → Business Partner → General Settings for Business Partner → Business Partner → Basic Settings → Field Groupings → Configure Field Attributes per BP Role

2. On the Change View “Field Group BP Role”: Overview screen, choose New Entries and enter the following:

BP Role UKM000


3. Choose Save.

3.3 Basic Config - Credit Management 2

3.3.1 Applications


Transaction Code SM30 using Customizing Object V_TBZ0A

2. On the Determine Work Area screen enter the values for the following data from the table below: - Application Object

3. On the Change View “Assign Screen Sequence -> Screens” Overview screen enter the following data:


© SAP AG of 23

Application Object Application Active

BUPA UKM X



3.3.2 Define Events and Follow-On Processes

Use In this IMG activity you define the dependencies required between different events that can occur in the processing of SAP Credit Management and processes of SAP Credit Management that are to be triggered when these events occur. For example, if a business partner's score changes, the risk class should also be changed accordingly.

Procedure


Transaction Code SM34 using Customizing Object VC_UKM_PROCESS

IMG Menu Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Processes → Define Events and Follow-On Processes

2. On the Change View “Events”: Overview screen, choose New Entries.

3. Make the following entries:

Activity Type of Event

Name of Event Type Publish Externally

Update of Credit information Triggered Externally

EC External Rating Changed X

Business Partner Maintenance EC External Rating Changed

Business Partner Maintenance ES External Rating Invalid

Business Partner Maintenance IC Score Changed

Business Partner Maintenance LC Credit Limit Changed X

Business Partner Maintenance XC Risk Class Changed X

Master Data Update via Mass Processing

IC Score Changed


LC Credit Limit Changed


RC Rule for Calculating Score and Credit Limit

Liability Update UC Credit Exposure Changed

Credit Request CL Credit Limit Invalid


© SAP AG of 23

Credit Request UU Credit Exposure over 100%

4. Choose Save.

5. Select the row with the first Activity, Update of Credit Information Triggered Externally, and double-click on the folder, Follow-on Processes.

6. Choose New Entries and enter the Process and Process Name from the table below that correspond to the Type of Event of selected activity.

7. Repeat steps 5 and 6 for all different types of events listed below:

Type of Event Process

CL EVL_LIMIT

EC EVL_RATING

ES INV_RATING

IC EVL_LIMITS

EVL_RISK_C

RC EVL_RATING

8. Choose Save.

3.3.3 Define Formulas

Use In this IMG activity, you define the formulas for calculating the score and the credit limit.

Procedure


Transaction Code SM30 using Customizing Object V_UKM_FORMULAS

IMG Menu Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Master Data → Define Formulas

2. On the Change View “SAP Credit Management: Formulas”: Overview screen, choose New Entries and enter the following:

Formula Formula Name Result Type

LIMIT_B2B Credit Limit for Business Customers Calculation of Credit Limit

LIMIT_B2C Credit Limit for Private Customers Calculation of Credit Limit

SCORE_B2B Score for Business Customers Calculation of Score

SCORE_B2C Score for Private Customers Calculation of Score

3. Choose Save.


© SAP AG of 23

3.3.4 Define Info Categories

Use

In this IMG activity, you defined the info categories required for SAP Credit Management.

Procedure


Transaction Code SM34 using Customizing Object VC_UKM_INFOCAT

IMG Menu Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Credit Limit Check → Define Info Categories

2. On the Change View “Info Category”: Overview screen, choose New Entries.

3. On the New Entries: Overview of Added Entries screen, and make the following entries:

Information Category Name of Information Category

Collateral Collateral/Securities

Negative Characteristic Negatives

Check Exception Credit checks to bypass

Credit Insurance Export credit insurance

4. Choose Save, and Back.

5. For each of the Information Categories entered in step 4, select the Information Category, double-click the folder Info Type, make the entries shown in the corresponding tables below, and choose Save.

Collateral

Information Type Name of Information Category

10 Letter of Credit

20 Guarantee

Negative Characteristic


10 Bankruptcy

20 Fraud

30 Legal Dunning Procedure

40 Denied by Credit Insurance

Check Exception



© SAP AG of 23

10 Regular Customer

20 New Customer

Credit Insurance


10 Insurance - Default Risk

20 Insurance - Country Risk

30 Tender, Bid Bonds

3.3.5 Create Rule for Scoring and Credit Limit Calculation

Use

In this IMG activity you create the new rule for calculating the score and credit limit or you change an existing rule.

Procedure


Transaction Code SM34 using Customizing Object VC_LIMIT_RULE

IMG Menu Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Master Data → Define Rule for Scoring

2. On the Change View “Rule for Scoring and Credit Limit Calculation”: Overview screen, choose New Entries and enter the following:

Rules Name Default

B2B-EXIST Existing B2B Customer X

B2B-NEW Rule for New Business Customers

B2C-EXIST Rule for Existing Customers - Private

B2C-NEW Rule for New Private Customers

3. Choose Save.

4. Select row with Rule B2B-EXIST.

5. Double-click folder Score. Make the following entries:

Rule Name of Rule Score Formula Formula Name

Validity (Days)

Trace

B2B-EXIST Existing B2B Customer

SCORE_B2B Score for Business Customer

365 X

6. Choose Save.


© SAP AG of 23

7. Select the row with Rule set to B2B-EXIST, and double-click folder Credit Limit.

8. On the Change View “Credit Limit”: Overview screen, make the following entries:

Credit Segment

Credit Limit Formula

Formula Name Validity (Days)

Trace

00 LIMIT_B2B Credit Limit for Business Cust

365 X


365 X


365 X


365 X

BP01 LIMIT_B2B Credit Limit for Business Cust

365

9. Choose Save.

10. Double-click the Rating Procedure Selection folder.

11. On the Change View “Rating Procedure Selection”: Overview screen, choose New Entries and enter the following:

Rating Procedure

Name (Language Independent)

Name (Language Specific)

Validity (Days)

Identification Type

D&BCap D&B Cap D&B Capital Rating

365 BUP001

12. Choose Save.

3.3.6 Define Rating Procedure

Use In this IMG activity you define the rating procedures that you can use to process external credit information for your business partners.

Procedure


Transaction Code SM34 using Customizing Object VC_UKM_RATING

IMG Menu Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Master Data → Define Rating Procedure

2. On the Change View “Rating Procedure”: Overview screen, choose New Entries and enter the following:


© SAP AG of 23

Rating Procedure Name (Language Independent) Name (Language Specific)

D&BCap D&B Cap D&B Capital Rating

3. Choose Save.

4. Select the row just entered, double-click folder Results of Ratings, and choose New Entries.

5. On the Change View “Results of Ratings”: Overview screen, choose New Entries and enter the following:

Rating

Procedure

Rating Rank Description Description

D&BCap 1A1 2 To 749K $ High To 749K $ High

D&BCap 1A2 3 To 749K $ Good To 749K $ Good

D&BCap 1A3 7 To 749K $ Fair To 749K $ Fair

D&BCap 1A4 8 To 749K $ Limited To 749K $ Limited

D&BCap 2A1 2 To 999K $ High To 999K $ High

D&BCap 2A2 4 To 999K $ Good To 999K $ Good

D&BCap 2A3 6 To 999K $ Fair To 999K $ Fair

D&BCap 2A4 8 To 999K $ Limited To 999K $ Limited

D&BCap 3A1 1 To 9 Mio $ High To 9 Mio $ High

D&BCap 3A2 4 To 9 Mio $ Good To 9 Mio $ Good

D&BCap 3A3 6 To 9 Mio $ Fair To 9 Mio $ Fair

D&BCap 3A4 8 To 9 Mio $ Limited To 9 Mio $ Limited

D&BCap 4A1 1 To 49 Mio $ High To 49 Mio $ High

D&BCap 4A2 4 To 49 Mio $ Good To 49 Mio $ Good

D&BCap 4A3 6 To 49 Mio $ Fair To 49 Mio $ Fair

D&BCap 4A4 7 To 49 Mio $ Limited To 49 Mio $

Limited

D&BCap 5A1 1 over 50 Mio $ High over 50 Mio $ High

D&BCap 5A2 3 over 50 Mio $ Good over 50 Mio $ Good

D&BCap 5A3 5 over 50 Mio $ Fair over 50 Mio $ Fair

D&BCap 5A4 7 over 50 Mio $ Limite over 50 Mio $

Limited

D&BCap BA 4 300K to 499K 300K to 499K

D&BCap BB 5 200K to 299K 200K to 299K

D&BCap CB 6 125K to 199K 125K to 199K

D&BCap CC 7 75K to 124K 75K to 124K

D&BCap DC 8 50K to 74K 50K to 74K

D&BCap DD 9 35K to 49K 35K to 49K


© SAP AG of 23

D&BCap EE 9 20K to 34K 20K to 34K

D&BCap FF 10 10K to 19K 10K to 19K

D&BCap GG 10 5K to 9K 5K to 9K

D&BCap HH 10 Up to 4K Up to 4K

6. Choose Save.

3.4 Credit Management 3

3.4.1 Create Credit Segments

Use In this IMG activity, you define the credit segments for SAP Credit Management that are useful for your company or your branches. You define the corresponding credit segments later in the master record of your business partner.

Credit segments are required for calculating the credit limit and enable you to carry out detailed checks at business partner level.

When you define a credit segment, you also decide on each currency in which all credit-relevant checks are to be carried out.

Procedure


Transaction Code SM30 using Customizing Object V_UKMCRED_SGM0C

IMG Menu Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Master Data → Create Credit Segments

2. On the Change View “SAP Credit Management: Segment Data”: Overview screen, choose New Entries.

3. On the New Entries: Overview of Added Entries screen, enter the following:

Credit Segment BP01

Name BP01 Credit Segment

Currency EUR

Exch. Rate Type M

Add. Contribution to Main Credit Segment X

4. Choose Save.


© SAP AG of 23

3.4.2 Define Customer Credit Group

Use In this IMG activity you can define the customer credit groups required.

Procedure


Transaction Code SM30 using Customizing Object V_UKM_CUST_GRP

IMG Menu Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Master Data → Define Customer Credit Group

2. On the Change View “Customer Credit Group”: Overview screen, choose New Entries.


Credit Group Name of Credit Group

1 Key customer

2 Large Business

3 Small/Medium size business

4 Individual

9999 Affiliate Company

4. Choose Save.

3.4.3 Create Risk Classes

Use In this IMG activity, you define the required risk classes for SAP Credit Management. You can define any number of risk classes.

The system can then determine the risk class of a business partner from the partner's score automatically or you can define it manually. You can also change the risk class determined automatically in the business partner master data record. In this case, the manual change overwrites the risk class determined automatically.

Procedure


Transaction Code SM30 using Customizing Object V_UKM_RICL_ASSL

IMG Menu Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Master Data → Create Risk Classes”

2. On the Change View “SAP Credit Management: Assignment of Risk Class to Score” screen, choose New Entries.



© SAP AG of 23

Risk Class Name of Risk Class Score From Score To

001 High risk 1 20

002 Medium risk 21 70

003 Low risk 71 90

004 Bluechip/Affiliate 91 100

005 Watchlist

006 Automatic monitoring

A No Default Risk

B Low Default Risk

C Medium Default Risk

D High Default Risk

E Very High Default Risk

4. Choose Save.

3.4.4 Define Blocking Reasons

Use In this IMG activity, you can define the reasons required for a credit assignment block. You can define the block reasons as required. When you block a business partner, the credit analyst can see the block reason in the master data record in the screen area Control.

Procedure


Transaction Code SM30 using Customizing Object V_UKM_BL_REASON

IMG Menu Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Credit Limit Check → Define Blocking Reasons

2. On the Change View AP Credit Management: Reason for Locks in the Credit Management screen, make the following entries:

Block Reason Name of Block Reason

01 Bankruptcy filing

02 Legal judgment

03 Collection

3. Choose Save.


© SAP AG of 23

3.4.5 Define Checking Rules

Use In this IMG activity, you define the check rules for the credit checks. A check rule can consist of several individual checks (check steps); in addition, you can define which parameters are relevant for each check step.

Procedure


Transaction Code SM34 using Customizing Object VC_UKM_CHCK_RULE

IMG Menu Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Credit Limit Check → Define Checking Rules

2. On the Change View “Check Rule”: Overview screen, choose New Entries, and make the following entries.

Check Rule Name of Check Rule Logging Check Exceptions Default

Z001 High Extensive X

Z002 Medium Extensive

Z003 Low Extensive

3. Choose Save.

4. Select the row with the first Check Rule, Z001, in the table above, and double-click on the Checks folder.

5. On the Change View ”Checks”: Overview screen, enter the following values:

Individual Step Name of Individual Step

020 Check for Maximum Document Value

030 Dynamic Limit Check with Credit Horizon

110 Check for Age of Oldest Open Item

6. Choose Save.

7. Select the row with Individual Step 020, and then double-click on Credit Segment.

8. On the Change View “Credit Segment”: Overview screen, enter the following values:

Credit Segment Maxim Document Value Currency

BP01 2,500 EUR

9. Choose Save, and double-click on the Check Rule folder.

10. Select the row with the first Check Rule, Z002, and double-click on the Checks folder.



© SAP AG of 23





12. Choose Save.




BP01 10,000 EUR

15. Choose Save and double-click on the Check Rule folder.

16. Select the row with the first Check Rule, Z003, and double-click on the Checks folder.






18. Choose Save.




BP01 50,000 EUR

21. Choose Save.

3.4.6 Define Events and Follow-on Processes

Use In this IMG activity, you can define the reasons required for a credit assignment block. You can define the block reasons as required. When you block a business partner, the credit analyst can see the block reason in the master data record in the screen area Control.

Procedure


Transaction Code SM34 using Customizing Object VC_UKM_PROCESS


© SAP AG of 23

IMG Menu Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Processes → Define Events and Follow-on Processes

2. On the Change View “Events”: Overview screen, choose New Entries, and make the following entries:

Activity Type of Event

Business Partner Maintenance EC

3. Choose Save

3.4.7 Activate SAP Collections Management

Use

In this IMG activity you activate the component SAP Collections Management.

Procedure


Transaction Code FDM_CUST08

IMG Menu Financial Supply Chain Management → Collections Management → Receivables Processing in Accounts Receivable Accounting → Activate SAP Collections Management

2. On the Help – Deactivate Collections Management dialog box, choose Continue.

3. On the Display View “BTE Application Indicator”: Overview screen, select the first row

identified by Appl.value FI-CM, and click on the check box in column A to set the Activation

flag.

4. Choose Save.

3.5 Master Data

3.5.1 Pricing Condition Maintenance

Procedure


Transaction Code VK11

SAP Menu Logistics → Materials Management → Purchasing → Master Data → Subsequent Settlement → Vendor Rebate Arrangements → Environment → Condition /Arrangement → Conditions: Sales → Prices → Other → Create

2. On the Create Condition Records screen enter Condition Type KF00.


© SAP AG of 23

3. On dialog box Key Combination select Incoterms (Parts 1 and 2) and select Choose (Enter).

4. On the Create Freight Condition (KF00) – Fast entry screen enter the following data:

Sales Organization BP01

Distribution Channel 01

Division 01

Incoterms EXW

Amount 50

Unit USD

Per 200

UoM LB

Valid From 01.10.2005

Valid To 31.12.9999



3.6 Miscellaneous

3.6.1 Activate FSCM Programs (RFOSXEXTEND, BALVBUFDEL)

Procedure


Transaction Code SE38

SAP Menu Tools → ABAP Workbench → Development → ABAP Editor

2. On the ABAP Editor: Initial Screen in field Program enter value RFPOSXEXTEND.

3. Choose Execute (F8).

4. Confirm dialog box Changing and Activating a structure in the Data Dictionary with Yes.

5. Confirm the information dialog box.

6. On the ABAP Editor: Initial Screen in field Program enter value BALVBUFDEL.

7. Choose Execute (F8).

8. Message %F buffer of EUINFO/LTEX has been reset is displayed.


w23 credit dispute amp collections management

Documents