Credit Management
EHP5 for SAP ERP
6.0
September 2011
English
Credit Management (108)
Building Block Configuration Guide
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices Credit Management (108): Configuration Guide
Copyright
© 2011 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 BusinessObjects Explorer,
StreamWork, 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 Software Ltd.
Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of
Sybase, Inc. Sybase 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 Page 2 of 11
SAP Best Practices Credit Management (108): Configuration Guide
Icons
Icon Meaning
Caution
Example
Note or Tip
Recommendation
Syntax
Typographic Conventions
Type Style
Example text
Example text
EXAMPLE TEXT
Example text
EXAMPLE TEXT
Example text
<Example text>
Description
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.
Emphasized words or phrases in body text, titles of graphics and tables.
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.
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.
Keys on the keyboard, for example, function keys (such as F2 ) or the
ENTER key.
Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
© SAP AG Page 3 of 11
SAP Best Practices Credit Management (108): Configuration Guide
Content
Assigning Permitted Credit Control Areas to Company Code ................................. 5
Assigning Sales Documents and Delivery Documents ............................................ 6
Assigning Credit Limit Check to Sales document type ........................................ 6
Determining Active Receivables per Item Category ................................................ 8
Checking Control Data for Your Pricing Procedures ............................................... 9
Checking Type of Update for Sales Info Structure ................................................ 10
© SAP AG Page 4 of 11
SAP Best Practices
Credit Management
Credit Management (108): Configuration Guide
1 Purpose
This configuration guide provides the information that you need to set up the configuration of this building block manually.
2 Prerequisites
Before 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 Permitted Credit Control Areas to
Company Code
Use
In this activity, you assign a credit control area to a company code.
Procedure
Carry out the following steps:
1. Access the activity using one of the following navigation options:
IMG Menu Financial Accounting (New)
Accounts Receivable and
Accounts Payable
Credit management
Credit Control
Account
Assign Permitted Credit Control Area to Company
Code
Transaction Code SM30 (Customizing Object T001CM)
2. On the Change View “Permitted Credit Control Areas per Company Code”: Overview screen choose New Entries.
3. Make the following entries:
Company Code
1000
4. Choose Save .
5. Choose Back .
Cred.contr.area
1000
Result
You have assigned the credit control area to the company code.
© SAP AG Page 5 of 11
SAP Best Practices Credit Management (108): Configuration Guide
3.2 Assigning Sales Documents and Delivery
Documents
3.2.1 Assigning Credit Limit Check to Sales document type
Use
In this activity, you define the settings for the credit checks for sales orders:
Procedure
Carry out the following steps:
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
Sales Document Type
Description User action and values
OR
Comment
Credit Check
Credit Group
D
01
4. Choose Save .
5. Choose Back .
Result
The credit limit check for the selected sales document type is set to automatic control.
3.2.2
Assigning Credit Limit Check to Delivery type
Procedure
Carry out the following steps:
1. 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
© SAP AG Page 6 of 11
SAP Best Practices Credit Management (108): Configuration Guide
2. On the Change View “Delivery Types – Credit Limit Check” set the Credit Limit to <bank>
– Credit Management: Automatic credit control:
3. Make the following entries:
Field Name
Delivery Type
Delivery credit group
GI credit group
Description User action and values
LF
<blank>
<blank>
Comment
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 Assigning Risk Category to Credit Control Area
Use
This activity will assign the Risk Category to the company code.
Procedure
Carry out the following steps:
1. Access the activity using one of the following navigation options:
IMG Menu Financial Accounting (New)
Accounts Receivable and
Account Payable
Credit management
Account
Define Risk Categories
Credit Control
Transaction Code OB01
2. Choose the New entries button and make the following entries:
Field Name
Risk Category
CCAr
Description User action and values
001
1000
Comment
Sales org. 1000
See step #1
3. Choose Save .
4. Choose Back .
Result
The risk category has been assigned to the credit control area.
3.4 Defining Automatic Credit Control
Use
In this activity, you assign the document credit group to the credit control area and risk category.
© SAP AG Page 7 of 11
SAP Best Practices
Procedure
Credit Management (108): Configuration Guide
1. Access the activity using one of the following navigation options:
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
2. Choose New Entries.
OVA8
Credit control
Area
1000
Risk category
001
Document credit group
01
Credit control
High Risk Sales Orders
Document controlling
Field name Check
Item Check
Checks
Field name
Check Reaction Status/B lock
Open
Orders
Open Max. delivery doc.value
Static check
Check
Document value
C (Warning + value by which the credit limit has been exceeded)
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.5 Determining Active Receivables per Item Category
Use
In this activity, you assign the Active Receivables to the relevant item categories.
Procedure
Carry out the following steps:
© SAP AG Page 8 of 11
SAP Best Practices Credit Management (108): Configuration Guide
1. Access the activity using one of the following navigation options:
IMG Menu Sales and Distribution → Basic Functions → Credit management / Risk management → Credit Management/Risk
Management Settings → Determine Active Receivables Per
Item Category
Transaction Code OVA7
2. Check the entries for your item categories:
3. For item category i.e. TAN, TAS, YBAB set the credit active indicator .
4. Choose Save .
Result
The item categories are relevant for credit check.
3.6 Checking Control Data for Your Pricing
Procedures
Use
This activity will check the control data settings automatic credit control.
Procedure
Carry out the following steps:
1. Access the activity using one of the following navigation options:
IMG Menu Sales and Distribution
Basic Functions
Pricing
Pricing
Control
Define and Assign Pricing Procedures
Maintain pricing procedures
Transaction Code V/08
2. Choose Position … and enter the result from previous action, step #3 (ZVAA01)
Field Name
Pricing Procedures
Description User action and values Comment
YBAA01 result from previous action, step #3
3. Double-click on Control
4. Choose Position.
5. Enter the following values:
Field Name
Step Number
Description User action and values Comment
920
6. For step 920 set the sub total indicator to A - Carry over price to KOMP-CMPRE (credit price).
7. Choose Save .
8. Choose Back .
Result
The subtotal from standard price
© SAP AG Page 9 of 11
SAP Best Practices Credit Management (108): Configuration Guide
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 Checking Update Group
Use
In this activity, you check the activity group for your credit control area.
Procedure
Carry out the following steps:
1. Access the activity using one of the following navigation options:
IMG Menu Enterprise Structure
Definition
Financial Accounting
Define Credit Control Area
Transaction Code OB45
2. Select the credit control area as follows and click on (Details)
Field Name Description User action and values
1000 Credit Control Area
3. Check the following details:
Field Name
Update
Description User action and values
000012 – Open order value on time axis, delivery and bill.
Doc value.
Comment
Comment
4. Choose Save .
5. Choose Back .
Result
The update group is set to standard.
3.8 Checking Type of Update for Sales Info Structure
Use
In this activity, you check the type of update for the relevant sales info structure-
Procedure
Carry out the following steps:
1. Access the activity using one of the following navigation options:
IMG Menu Logistics General
Update
Logistics Information System
Sales and Distribution
Logistics
Data Warehouse
Updating
Updating Control
Activate
Transaction Code OMO1
© SAP AG Page 10 of 11
SAP Best Practices
2. Make the following entries:
Credit Management (108): Configuration Guide
Field Name
Info structure
Description User action and values
S066
3. Double click on the structures name and check the entry update group.
Field Name Description User action and values
Update group 1 - Synchronous Updating (V1
Update)
Comment
Comment
4. Choose Save .
5. Choose Back .
© SAP AG Page 11 of 11
