108 bb configguide en us credit management

EHP4 for SAP ERP 6.0

June 2010

English

Credit Management (108)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Credit Management (108): Configuration Guide

Copyright

© Copyright 2010 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, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

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.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

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 or Tip

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 TEXTKeys 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

Credit Management........................................................................................................................ 5

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

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

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

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

3.1 Assign Permitted Credit Control Areas to Company Code............................................5

3.2 Assign Sales Documents and Delivery Documents.......................................................6

3.2.1 Assign Credit Limit Check to Sales document type...................................................6

3.2.2 Assign Credit Limit Check to Delivery type................................................................7

3.3 Assign Risk Category to Credit Control Area.................................................................7

3.4 Define Automatic Credit Control....................................................................................8

3.5 Determine Active Receivables per Item Category.........................................................9

3.6 Check Control Data for your Pricing Procedures...........................................................9

3.7 Check Update Group...................................................................................................10

3.8 Check Type of Update for Sales Info Structure...........................................................11

© SAP AG of 11


Credit Management

1 PurposeThis configuration guide provides you with 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 SAP Best Practices Quick Guide, located on the SAP Note.

2 Preparation

2.1 PrerequisitesBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix for Baseline. The matrix (an Excel file) is linked on the solution's DVD/website in one of the following two locations:

Content Library

Site Map

3 Configuration

3.1 Assign Permitted Credit Control Areas to Company Code

UseIn this activity, you assign a credit control area to a company code.

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

Transaction Code SM30 (Customizing Object T001CM)

IMG Menu Financial Accounting (New) Accounts Receivable and Accounts Payable Credit management Credit Control Account Assign Permitted Credit Control Area to Company Code

© SAP AG of 11

SAP Best Practices Credit Management (108): Configuration Guide 2. On the Change View ”Permitted Credit Control Areas per Company Code”: Overview screen

choose New Entries.

3. Make the following entries:

Company Code Cred.contr.area

1000 1000

4. Choose Save.

5. Choose Back.

Result You have assigned the credit control area to the company code.

3.2 Assign Sales Documents and Delivery Documents3.2.1 Assign Credit Limit Check to Sales document type

UseIn this activity, you define the settings for the credit checks for sales orders:


Transaction Code OVAK

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

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


Field name Description User action and values Comment

Sales Document Type OR

Credit Check D

Credit Group 01

4. Choose Save.

5. Choose Back.

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

© SAP AG of 11


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

options:

Transaction Code OVAD

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

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.3 Assign Risk Category to Credit Control Area

Use This activity will assign the Risk Category to the company code.


Transaction Code OB01

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

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


Risk Category 001 Sales org. 1000

CCAr 1000 See step #1

© SAP AG of 11


3. Choose Save.

4. Choose Back.

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

3.4 Define Automatic Credit Control

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


Transaction Code OVA8

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

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)

Check Documentvalue

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

9,999,999

© SAP AG of 11


3. Choose Save.

4. Choose Back.

Result The automatic credit control has been set up.

3.5 Determine Active Receivables per Item Category

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


Transaction Code OVA7

IMG Menu Sales and Distribution → Basic Functions → Credit management / Risk management Credit Management/Risk Management Settings → Determine Active Receivables Per Item Category

2. Check the entries for your item categories:

3. For item category that is TAN, TAS, YBAB, set the credit active indicator .

4. Choose Save.

ResultThe item categories are relevant for credit check.

3.6 Check Control Data for your Pricing Procedures

UseThis activity will check the control data settings automatic credit control.


Transaction Code V/08

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

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

Field name Description User action and values

Comment

Pricing Procedures

YBAA01 result from previous action, step #3

© SAP AG of 11

SAP Best Practices Credit Management (108): Configuration Guide 3. Double-click on 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 is 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.7 Check Update Group

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


Transaction Code OB45

IMG Menu Enterprise Structure Definition Financial Accounting Define Credit Control Area

2. Select the credit control area as follows and click on (Details)


Credit Control Area 1000

3. Check the following details:

Field name

Description User action and values Comment

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

4. Choose Save.

5. Choose Back.

Result The update group is set to standard.

© SAP AG of 11


3.8 Check Type of Update for Sales Info Structure

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


Transaction Code OMO1

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



Info structure S066

3. Double-click on 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