on 12-09-2008 9:04 AM
Dear All
We need to maintain the PERIOD WISE as well as CUSTOMER WISE Credit Management , If it is possible ,please sent us the complete config document of the same.
Regards
Animesh Chakraborty
Dear Animesh,
Can you be still more clear on your requirement, so that we can discuss the issue on this forum.
Best regards,
Shivanand
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
period wise u can use in ova8 .in sesional factor can be used .u have to do customer wise u can do with FD-32 .
PLEASE REFF THE NOTES IT MAY USEFULL FOR U.
How To Do Configuration For Credit Management
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.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
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.
Best regards,
venkataswamy.y
Edited by: yanamadala venkataswamy on Dec 10, 2008 3:11 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Venkataswamy,
Thanks for your reply. I was not well, so sorry for the late reply. As per your advice I have configured and it's working perfectly for value based i.e using FD32 (Customer wise credit limit). But I want the system should carry out a check which will take into consideration both the value and credit limit days.
For Example : Party : A Credit Limit : Rs. 1000/- Credit Limit days : 2
We have made one invoice of value Rs. 600/- Credit Exposure : 60% Remaining Credit Limit : Rs. 400/- on 06.01.2009.Now after 2days i.e. on 08.01.2009 I want the system to stop generation of sale order by setting the credit check block at the Sale Order level even though the sale order value will not exceed the remaining Credit Limit i.e. Rs.400 and the order will get blocked as a result of Credit Check being carried out on the basis of Credit Limit days.
The configurations which are at present prevailing in OVA8 are as follows -
CCA RkC CG Credit control Curr. Update
1000 001 01 High Risk Sale Orders INR 000012
No credit check 1
Item check (Check Box is marked on)
Checks
Reaction Status / Block Open Orders / Open Deliveries
Static C (Check Box is marked on) (Check Boxes are marked on)
Horizon - M
Oldest Open Item C (Check Box is marked on) Days oldest item - 30
All other check boxes and fields remain empty / blank.
Now considering the above scenario please suggest what other configurations are requiered to attain my requierement.
Looking forward to your kind suggestions.
Thanks & Regards
Animesh
Dear Animesh
the customer wise credit management can be handled with T. Code FD32 provided all configuration is being done for credit management. Regarding the period wise you can control with with FD32 and OVA8.
Any query please raise.
Thanks
Edited by: SUSHANT KRISHEN on Dec 9, 2008 11:40 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
107 | |
12 | |
10 | |
5 | |
5 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.