108_BB_ConfigGuide.doc

(216 KB) Pobierz
BB Configuration Guide



 

EHP3 for SAP ERP 6.0

June 2009

EnglishEnglish

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Credit Management (108)

 

 

 

 

 

 

 

 

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany 

Building Block Configuration Guide


SAP Best Practices              Credit Management (108): Configuration Guide

 

Copyright

 

© Copyright 2009 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.


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.


Contents

 

Credit Management              5

1              Purpose              5

2              Prerequisites              5

3              Configuration              5

3.1              Assigning Permitted Credit Control Areas to Company Code              5

3.2              Assigning Sales Documents and Delivery Documents              5

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 Pricing Procedures              9

3.7              Checking Update Group              9

3.8              Checking Type of Update for Sales Info Structure              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        Prerequisites

Before you start installing this building block, you must install prerequisite building blocks. For more information, see the building block prerequisite matrix (Prerequisites_Matrix_[xx]_EN_PL.xls; the placeholder [xx] depends on the SAP Best Practices version you use, for example BL refers to the SAP Best Practices Baseline Package: Prerequisites_Matrix_BL_EN_PL.xls). This document can be found on the SAP Best Practices documentation DVD in the folder: ..\BBLibrary\General\.

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

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.

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

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

Zgłoś jeśli naruszono regulamin