Credit Management

[Former Member]

Dear all,

Please give me information about Credit Management. How to do it? When to use? And explain for me about functions: Release, Reassign and Reject.

Thank you!

Regards,

Quang

[Former Member]

Hi All,

Any one can tell me the diffenrence between total amount and Individual limit ?

Thnks & rgdrs

[Former Member]

>

> Hi All,
> 
> Any one can tell me the diffenrence between total amount and Individual limit ?
> 
> Thnks & rgdrs

HI Quang...

A customer can be defined in multiple credit control areas....

Total limit is the total credit a customer can get in all CCA(Credit Control Area's) combined.

Individual limit is the limit for the particular CCA for which you are maintaining FD32 (you specify a CCA in the first screen that appears for TCode FD32) the individual limit for this CCA

Reward if helpful

Regards

Abhishek

[Former Member]

Pls explain for me about functions: Release, Reassign and Reject (VKM3).

[Former Member]

HI Quang,

As in any real time situation if any of your customer exceeds credit limit, you prohibit him from receiving any further credit. But let us say the customer has got very good track record or an administrative error or any other excusable reason he has exceeded his credit limit or he has exceeded his limit but still you feel you can go ahead and honour his further orders. In such a case due to credit management settings the System will block the order for delivery but you still want to deliver it. This is when you use VKM3 put the Sales Order number Blocked for delivery in that and execute once you execute you need to click the green flag which means you are releasing that order for delivery.

After that you should save the same.

This will release the Order Blocked for delivery and you can continue as normal.

Hope it clarifies to some extent.

Post for further clarification

Regards

Abhishek

[Former Member]

hi,

i haven't understaned yet. For example, when i set credit limit for a customer is 1000$. And then i create a sales order with net value is 2000$. Is it allow? and when do it warn or block?

thanks

[Former Member]

>

> hi,
> 
> i haven't understaned yet. For example, when i set credit limit for a customer is 1000$. And then i create a sales order with net value is 2000$. Is it allow? and when do it warn or block?
> 
> thanks

HI Quang,

sorry for the late reply...

In your example if you set Credit limit for customer as 1000$ and try to create a sales order of 2000$. There are multiple ways to configure

1) You use a Simple Credit check TCode OVAK.

Here in the field "Check Credit"

a)if you choose A a warning message will be popped saying credit limit exceed do you still want to save.

b) If you choose B it will pop an error message and would not let yoyu save the sales Order.

c) If you choose C it will let you save the sales order but BLOCK it for DELIVERY.

d) If you choose D you are configuring Automatic credit management.

SO apart from Chossing D you also choose "Credit Group"

01 -Order Level

02-Delivery Level

03-PGI level

SO depending on this choice the action will be taken on the respective level i.e. choosing 02 will mean Delivery will not be created or warned for.

Once this is over if you have chosen D i.e. Automatic Credit Management you need to goto OVA8 and define actions for Credit groups over there for the combination of

Credit Control AreaRisk Category(FD32 for Customer)Credit Group(From OVAK).

Inside this you can further configure it for Blocking or warning for each combination

Hope it helps to clarify

Post for further clarification

Reward if helpful

Regards

Abhishek

[Former Member]

Thanks for your support!

Regards,

[Former Member]

Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.

An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.

For example, if your credit management is centralized, you can define one credit control area for all of your company codes.

If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.

Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.

Configuration :

1. Transaction OB38

Check which credit control area is assigned to the company code.

Company code:

Credit control area:

2. Transaction OVFL

Check which credit control area is assigned to the sales area.

Sales area:

Credit control area:

3. Transaction XD02 or VD02

Check which credit control area is assigned to the payer.

Payer:

Credit control area:

4. Transaction SE37

Is user exit EXIT_SAPV45K_001 being used?

5. Transaction OBZK

For the settings under items 2 - 4, field "All company codes" must be marked in Transaction

OB45, or the credit control area must be entered under the relevant company code in table

T001CM of the credit control areas allowed.

Company code:

Credit control areas allowed:

6. Settings for the credit checks

7. Transaction OVAK

Which settings do exist for the sales document type used?

Sales document:

Check credit:

Credit group:

8. Transaction OVAD

Which settings do exist for the delivery type used?

Delivery type:

Credit group for delivery:

Credit group for goods issue:

9. Transaction OB01

Credit management/Change risk category

Definition of the risk category for each credit control area. This risk category can be

assigned to a credit account by using Transaction FD32.

10. Transaction OVA8

Here, the individual credit checks for key fields

o credit control area

o risk category

o credit group are set. Take these key fields from the above settings and go to the detail

screen. In particular, check whether fields "Reaction" and "Status/block" are set

correctly. To carry out follow-up actions in case of a credit block, the credit check

status must be set (field "Status/block").

11. Transaction FD32

Credit master data for the payer of the relevant document.

Credit account:

Credit limit:

Risk category:

Currency:

12. Settings for updating the credit values Update of the credit values is required for the limit

check (static or dynamic credit limit check).

13. Transaction OVA7

Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to

field "Active receivable" in Transaction VOV7.

Item type:

Active receivable:

14. Transaction V/08, Pricing

In the pricing procedure used for pricing, subtotal "A" must be entered in a line for

determining the credit value (mark the pricing procedure and doubleclick on "Control").

Usually, the net value plus taxes is used. This way the system is determined to use this

subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for

update and credit check.

You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".

Pricing procedure:

Line with subtotal = 'A':

15. Transaction OB45

Which update group (field "Update") do you use in the relevant credit control area? The

default setting is "12". If you use another update group, check whether this is fine with

you. If you open an OSS message, please tell us the alternative update group.

Credit control area:

Update:

16. Transaction OMO1

Which kind of update did you choose for structure S066?

In any case, "Synchronous update (1)" has to be chosen as the kind of update.

All other settings will lead to errors.

hope this helps

Reward if helps

Rgds