108 ERP606 Process Overview en XX

7/30/2019 108 ERP606 Process Overview en XX

http://slidepdf.com/reader/full/108-erp606-process-overview-en-xx 1/7

Credit Management

SAP Best Practices



© 2013 SAP AG. All rights reserved. 2

Purpose, Benefits, and Key Process Steps

Purpose

A credit limit check can be carried out when sales documents are created or changed.

Benefits

Reduce risk of bad debt

Focus on reliable and profitable customers

Faster credit-worthiness check

Accelerate the process of checking a customer credit limit

Identify the overall credit risk of your company

Key Process Steps

Enter Sales Order

Check Credit Limit

Block Sales Order

Release Sales Order

Delivery Sales Order




Required SAP Applications and Company Roles

Required SAP Applications

Enhancement package 6 for SAP ERP 6.0

Company Roles

Billing Administrator

Accounts Receivable Manager




Detailed Process Description

Credit Management The credit limit check is carried out within one credit control area. When changing a

document, the check is repeated, if changes regarding quantity or value are made. A creditcontrol area consists of one or more company codes. A sales document belongs to onecredit control area depending on the allocation of the sales organization to a companycode. The SAP System checks the credit limit which was granted to the customer in thiscredit 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 SAPSystem totals the receivables, the open items and the net value of the sales order for everyitem of a sales document. The open items take into account obligations bound by contractwhich are not recorded for accounting purposes but which involve expenses throughdiverse business transactions. The total is compared with the credit limit. If the limit isexceeded, the system responds in the way defined by you in the configuration menu.

We are using 'simple' credit limit check in this solution. During the simple credit limit check,you can only configure one system reaction ('A' warning, 'B' error, 'C' delivery block) when

the credit limit is exceeded, we have chosen to use option 'C' (delivery block). The system provides a transaction to list all of the sales documents that have been blocked

for delivery, with information about what has caused the block. The Customer's currentcredit situation is manually reviewed by credit department, and when the sales order isapproved, the delivery block is removed from the sales order. You go directly from the list toan individual sales document by placing the cursor on the relevant document and choosingEdit sales doc.




Process Flow DiagramCredit Management

A c c o u n t s R e c e i v a b

l e

M a n a g e r

E v e n t

Review BlockedSales Orders

Sales Order Failed Credit

Check

ResolveCredit

Credit ApprovedFeedback from

Customer

Sales Order Processing: Sale from

Stock(109)

Sales of Nonstock Item

with Order specific

Procurement(115)

Make-to-Order Production w/o

VariantConfiguration

(148)

Sales Order Processing: Sale from

Stocka(109)

Sales of Nonstock tem

with Order specific

Procurement(115)

CreditCheck for a SpecificCustomer Desired

Set CreditLimit

Sales:Period End

ClosingOperations

(203)

Make-to-Order Production w/o

VariantConfiguration

(148)

B i l l i n g

A d m i n i s t r a t o r




Legend

Symbol Description Usage Comments

To next / From last Diagram: Leadsto the next / previous page of theDiagram

Flow chart continues on the next /previous page

Hardcopy / Document: Identifies aprinted document, report, or form

Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines

Financial Actuals: Indicates afinancial posting document


Budget Planning: Indicates abudget planning document


Manual Process: Covers a taskthat is manually done

Does not generally correspond toa task step in a document;instead, it is used to reflect a taskthat is manually performed, suchas unloading a truck in thewarehouse, which affects theprocess flow.

Existing Version / Data: This blockcovers data that feeds in from anexternal process

Does not generally correspond toa task step in a document;instead, this shape reflects datacoming from an external source;this step does not have anyincoming flow lines

System Pass / Fail Decision: Thisblock covers an automaticdecision made by the software

Does not generally correspond toa task step in the document;instead it is used to reflect anautomatic decision by the systemthat is made after a step has beenexecuted.

E x t e r n a l

t o S A P

BusinessActivity / Event

Unit Process

ProcessReference

Sub-Process

Reference

ProcessDecision

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProcess

ExistingVersion /

Data

SystemPass/FailDecision

Symbol Description Usage Comments

Band: Identifies a user role, such as Accounts

Payable Clerk or Sales Representative. This band

can also identify an organization unit or group,

rather than a specific role.

The other process flow symbols in this table go

into these rows. You have as many rows as

required to cover all of the roles in the scenario.

Role band contains

tasks common to that

role.

External Events: Contains events that start or end

the scenario, or influence the course of events in

the scenario.

Flow line (solid): Line indicates the normal sequence

of steps and direction of flow in the scenario.

Flow line (dashed): Line indicates flow to

infrequently-used or conditional tasks in a

scenario. Line can also lead to documents involved

in the process flow.

Connects two tasks ina scenario process or a non-step event

Business Activity / Event: Identifies an action thateither leads into or out of the scenario, or anoutside Process that happens during the scenario

Does not correspondto a task step in thedocument

Unit Process: Identifies a task that is covered in astep-by-step manner in the scenario

Corresponds to a taskstep in the document

Process Reference: If the scenario referencesanother scenario in total, put the scenario number and name here.


Sub-Process Reference: If the scenario referencesanother scenario in part, put the scenario number,name, and the step numbers from that scenariohere


Process Decision: Identifies a decision / branchingpoint, signifying a choice to be made by the enduser. Lines represent different choices emergingfrom different parts of the diamond.

Does not usuallycorrespond to a taskstep in the document;Reflects a choice tobe made after stepexecution

< F u n c t i o n >


http://slidepdf.com/reader/full/108-erp606-process-overview-en-xx 7/7© 2013 SAP AG. All rights reserved. 7

© 2013 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.

National product specifications may vary.

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

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx




Documents

108 ERP606 Process Overview en XX