sd credit management 108 bb configguide en zh 20080403

SAP ECC 6.00

March 2008

English

Credit Management (108)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Credit Management (108): Configuration Guide

Copyright

© Copyright 2008 SAP AG. All rights reserved.

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

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

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

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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

Oracle is a registered trademark of Oracle Corporation.

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

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

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

Java is a registered trademark of Sun Microsystems, Inc.

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

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, 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 11


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

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 11


Content

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

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

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

3 Configuration........................................................................................................................... 5

3.1 Assigning Sales Documents and Delivery Documents..................................................5

3.1.1 Assigning Credit Limit Check to Sales document type..............................................5

3.1.2 Assigning Credit Limit Check to Delivery type...........................................................6

3.2 Assigning Risk Category to Credit Control Area............................................................6

3.3 Defining Automatic Credit Control.................................................................................7

3.4 Determining Active Receivables per Item Category......................................................8

3.5 Checking control data for your Pricing Procedures........................................................9

3.6 Checking update group.................................................................................................9

3.7 Checking type of update for sales info structure..........................................................10

© SAP AG of 11


Credit Management

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

2 Preparation

2.1 PrerequisitesBefore you start installing this scenario, you must install prerequisite building blocks. For more information, see the Building Block Prerequisites Matrix for SAP Best Practices Baseline Package .

3 Configuration

3.1 Assigning Sales Documents and Delivery Documents

3.1.1 Assigning Credit Limit Check to Sales document type

UseThis activity defines the settings for the credit checks for sales orders:

Procedure 1. Access the activity using one of the following navigation options:

IMG menu Sales and Distribution Basic Functions Credit management / Risk management Credit Management Assign Sales Documents and Delivery Document Credit limit check for order types

Transaction code OVAK

2. On the Change View ‘Sales Document Types – Credit Limit Check’ screen, set the Credit Limit to D – Credit Management: Automatic credit control:

3. Make the following entries:

Field name Description User action and values Comment

Sales Document Type OR

Credit Check D

Credit Group 01

4. Choose Save.

5. Choose Back.

© SAP AG of 11


Result The credit limit check for the selected sales document type is set to automatic control.

3.1.2 Assigning Credit Limit Check to Delivery type1. Check the settings for the deliveries. Access the activity using one of the following navigation

options:

IMG menu Sales and Distribution Basic Functions Credit management / Risk management Credit Management Assign Sales Documents and Delivery Document Credit limit check for delivery types

Transaction code OVAD

2. On the Change View ‘Delivery Types – Credit Limit Check’ set the Credit Limit to <bank> – Credit Management: Automatic credit control:



Delivery Type LF

Delivery credit group <blank>

GI credit group <blank>

4. Choose Save.

5. Choose Back.

Result The credit limit check for the selected delivery document type takes place on sales order document only.

3.2 Assigning Risk Category to Credit Control Area

Use This activity assigns the Risk Category to the company code.


IMG menu Financial Accounting (New) Accounts Receivable and Account Payable Credit management Credit Control Account Define Risk Categories

Transaction code OB01

2. Choose the New entries button and make the following entries:


Risk Category 001 Sales org. 1000

© SAP AG of 11



CCAr 1000 See step #1

3. Choose Save.

4. Choose Back.

Result The risk category has been assigned to the credit control area.

3.3 Defining Automatic Credit Control

Use In this activity, assign the document credit group to the credit control area and risk category.


IMG menu Financial Supply Chain Management Credit Management Integration with Accounts Receivable Accounting and Sales and Distribution Integration with Sales and Distribution Define Automatic Credit Control

Transaction code OVA8

2. Choose the New Entries button.

Credit control Area

Risk category Document credit group

Credit control

1000 001 01 High Risk Sales Orders

Document controlling

Field name Check

Item Check

Checks

Field name

Check Reaction Status/Block

Open Orders

Open delivery

Max.doc.value

Static check

C (Warning + value by which the credit limit has been exceeded)

© SAP AG of 11


Check Document value

C (Warning + value by which the credit limit has been exceeded)

9.999.999

3. Choose Save.

4. Choose Back.

Result The automatic credit control has been set up.

3.4 Determining Active Receivables per Item Category

Use In this activity, you assign the Active Receivables to the relevant item categories.


IMG menu Sales and Distribution Basic Functions Credit management / Risk management Determine Active Receivables Per Item Category

Transaction code OVA7

2. Check the entries for your item categories:

3. For item category, for example, TAN, TAS, YBAB set the credit active indicator.

4. Choose Save.

ResultThe item categories are relevant for credit check.

3.5 Checking control data for your Pricing Procedures

UseThis activity checks the control data settings automatic credit control.


IMG menu Sales and Distribution Basic Functions Pricing Pricing Control Define and Assign Pricing Procedures Maintain pricing procedures

© SAP AG of 11


Transaction code V/08

2. Choose Position… and enter the result from previous action, step #3 (ZVAA01)


Pricing Procedures YBAA01 result from previous action, step #3

3. Double-click Control.

4. Choose Position… and enter the following values:


Step Number 920

5. For step 920 check set the sub total indicator to ‘A - Carry over price to KOMP-CMPRE (credit price)’

6. Choose Save.

7. Choose Back.

Result The subtotal from standard price

Usually, the net value plus taxes are used. This way the system is determined to use subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for update and credit check

3.6 Checking update group

Use In this activity, you check the activity group for your credit control area.


IMG menu Enterprise Structure Definition Financial Accounting Define Credit Control Area

Transaction code OB45

2. Select the credit control area as follows and choose Details.


Credit Control Area 1000

3. Check the following details:


Update 000012 – Open order value on time axis, delivery and bill. Doc value.

© SAP AG of 11


4. Choose Save.

5. Choose Back.

Result The update group is set to standard.

3.7 Checking type of update for sales info structure

Use In this activity, you check the type of update for the relevant sales info structure-


IMG menu Logistics General Logistics Information System Logistics Data Warehouse Updating Updating Control Activate Update Sales and Distribution

Transaction code OMO1



Info structure S066

3. Double-click the structures name and check the entry update group.


Update group 1 - Synchronous Updating (V1 Update)

4. Choose Save.

5. Choose Back.

© SAP AG of 11


A credit limit check can be carried out when sales documents are created or changed. The check is carried out by the system within one credit control area. If you change quantities or values in a document, the check is repeated. A credit control area consists of one or more company codes. A sales document belongs to one credit control area depending on the allocation of the sales organization to a company code. The SAP System checks the credit limit that was granted to the customer in this credit control area. The credit control areas and the credit limit of a customer are defined in financial accounting and entered in the customer master record. During the check, the SAP System totals the receivables, the open items and the net value of the sales order for every item of a sales document. The open items take into account obligations bound by contract that are not recorded for accounting purposes but involve expenses through diverse business transactions. After that, it compares the total with the credit limit. If the limit is exceeded, the system responds in the way you defined in the configuration menu.

We are using automatic credit control in this solution. During the automatic credit control, you can configure a system reaction (A: warning, B: error, C: A + value by which the credit limit is exceeded, D: B + value by which the credit limit is exceeded). When the credit limit is exceeded, we use option C (warning + value by which the credit limit is exceeded).

The system provides a transaction to list all sales documents that have been blocked for delivery, with information about what has caused the block. The customer's current credit situation is manually reviewed by the credit department, and when the sales order is approved, the delivery block is removed from the sales order. You can jump directly from the list to an individual document.

Process FlowThis scenario consists of the following steps:

← A credit limit is set

← Blocked sales orders are reviewed and released

Key Points← Reduce risk of bad debt

← Focus on reliable and profitable customers

← Faster credit-worthiness check

← Fasten the process of checking a customer credit limit

← Identify the overall credit risk of your company

© SAP AG of 11