108_erp606_bb_configguide_en_in.doc

7/29/2019 108_ERP606_BB_ConfigGuide_EN_IN.doc

http://slidepdf.com/reader/full/108erp606bbconfigguideenindoc 1/10

EHP6 for SAP ERP6.0

March 2012

English

Credit Management (108)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Building Block Configuration Guide



SAP Best Practices Credit Management (108): Configuration Guide

Copyright

© 2012 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, SAP HANA, 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 wellas 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 andservices mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Datacontained in this document serves informational purposes only. National product specifications mayvary.

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

© SAP AG of 10




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 andoptions.

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 keywords 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 asnames of installation, upgrade and database tools.

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

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

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

© SAP AG of 10




Contents

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

2 Prerequisites ..........................................................................................................................53 Configuration ..........................................................................................................................5

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

3.2 Assigning Sales Documents and Delivery Documents ....................................................6

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

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

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

3.4 Defining Automatic Credit Control................................................................................... 7

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

3.6 Checking Control Data for Your Pricing Procedures ........................................................9

3.7 Checking Update Group .................................................................................................9

3.8 Checking Type of Update for Sales Info Structure .........................................................10

© SAP AG of 10




Credit Management

1 Purpose

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

2 PrerequisitesBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix (Prerequisites_Matrix_[ xx ]_[yy ]_ [zz ].xls; the placeholder [ xx ] depends on the SAP Best Practices version you use, for example, BL refers to the SAP Best Practices Baseline Package, [yy ] depends on thelanguage version, for example, EN for English language, and [zz ] depends on the countryversion, for example, IN for India: Prerequisites_Matrix_BL_EN_IN.xls). This document canbe found on the SAP Best Practices documentation DVD in the folder ..\

[ xx ] _[zz ]\Documentation\; ( [ xx ] depends on the SAP Best Practices version and [zz ] dependson the country version).

3 Configuration

3.1 Assigning Permitted Credit Control Areas toCompany Code

Use

In 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

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.

© SAP AG of 10




3.2 Assigning Sales Documents and DeliveryDocuments

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


Transaction code OVAK

IMG menu Sales and Distribution→Basic Functions→Credit

management / Risk management → Credit Management

→ Assign Sales Documents and Delivery Documents→Credit

limit check for order types2. On the Change View Sales Document Types – Credit Limit Check screen 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.

3.2.2 Assigning Credit Limit Check to Delivery type

Procedure


Transaction code OVAD

IMG menu Sales and Distribution→Basic Functions→Credit

management / Risk management → Credit Management →

Assign Sales Documents and Delivery Documents→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>

© SAP AG of 10




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


Transaction code OB01

IMG menu Financial Accounting (New)→Accounts Receivable and Account

Payable →Credit management →Credit Control Account →Define Risk Categories

2. Choose New entries and make the following entries:


Risk Category 001 Sales org. 1000

CCAr 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 riskcategory.

Procedure


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 New Entries.

Credit controlArea

Risk category Document creditgroup

Credit control

© SAP AG of 10




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

Staticcheck

C (Warning +value by whichthe credit limithas beenexceeded)

CheckDocumentvalue

C (Warning +value by whichthe credit limithas beenexceeded)

9,999,999.00

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


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 for example, TAN, TAS, YBAB set the credit active indicator .

4. Choose Save.

Result

The item categories are relevant for credit check.

© SAP AG of 10




3.6 Checking Control Data for Your Pricing

Procedures

Use

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

Procedure


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 ZINFAC from previous action:

Field Name Description User action and values CommentPricing Procedures ZINFAC

3. Double-click Control data.

4. Choose Position.

5. Enter the following values:


Step Number 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

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

3.7 Checking Update Group

Use

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

Procedure


Transaction code OB45

IMG menu Enterprise Structure→Definition→Financial Accounting →Define Credit Control Area

© SAP AG of 10




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


Credit Control Area 1000

3. Check the following details:


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

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


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