Risk Categories in credit management
Hello Gurus,
How can I get the configuration details for the different risk categories that are defined in an sap systems for credit controlling area?
Thank you.
Hi
Risk categories are defined in OB01.
Regards
Sowmya
Similar Messages
-
Risk category in credit management
Hi,
What is the role of risk category in credit management?
RegardsHi,
It enables the credit manager to classify customers according to commercial risk. Along with the document type, the risk category helps to determine which kind of credit check the system automatically carries out. For example, you may want to carry out stringent checks at order receipt for high risk customers, but waive a credit check for customers with a very strong payment history.
Regards
SD -
Risk category field is missing in dso for 0fiar_o09 credit management.
Hi BI Experts,
I am using the standard extractor for the credit management dso 0fiar_o09. The field for risk category originates from our R3 system in table knkk-ctplc. It displays correctly in the psa. The transformation rsds 0fi_ar_9 maps it to 0risk_categ. It appears as an infoObject in the infoSource. The trcs transformation maps the rule also.
However, when I try to display the data in the dso, the risk category field does not display at all.
Please help with any possible suggestions to display the missing field.
Kind regards,
Cheryl AdamonisI resolved this issue by removing the check in the 'attribute only' selection on the general tab of the infoObject.
-
Difference between credit management and risk management
Hi friends,
can any one please explain about difference between creditmanagement and risk management.
Thanks®ardsHi Madhusudhan,
The payment guarantee for the value to be billed plays a central role within Sales. Credit management effectively allows you to minimise the credit risk.
Risk management for receivables is another useful tool for setting a payment guarantee to cover the credit risk.
Hope this Clairifies your Doubt and Please Reward If Really helpful.
Thanks and Regards,
Sateesh.Kandula -
Credit Management requirement for cash business
Hi Gurus,
Actually my client business is a cash business, there is no credit concept for the customers.
My requirement is when i create a sales order, system should check the credit balance of the customer(Business receives the payment through cheque and entry is made in f.28 transaction) and should compare with the current document value and if it exceeds, then system should through the error.
And if any open sale orders exists for this customer, system should even consider those values while credit check is happening.
And the exceptions for this requirement is
1.Credit check option should be there only for specific case of customers i,e based on account group of customers.
2.There are very few customers(around 5) where they give credit.
Pls guide me, early resposes woould be highly appreaciable.
Thanks in advance
Regards
Mahendar.hello, friend.
you can consider using the payment guarantee scenario in credit management. the customer advance payment could be treated sort of as a financial document or payment card.
as for the selective application of credit controls based on customer group, i believe you do this be configuring risk categories and assigning them to the appropriate credit account master data.
regards.
Edited by: jonathan y on Apr 24, 2009 12:57 PM -
Credit management configuration in Third party sales
Dear All,
Please let me know , what are the configuration setting for Credit Management in Third Party Sales.
Regards
SKumarHi...
For Third Party, since there is no Delivery and PGI, the block can be at Billing.
however the total outstanding value from the customer at the time of billing along with the days as set in the credit limit shall be basis of blocking.
Config Steps:
u2022 Assigned the credit control area to the company code
Financial Accounting (New) Accounts Receivable and Accounts Payable Credit management Credit Control Account Assign Permitted Credit Control Area to Company Code
u2022 Assign Sale Document and Delivery Document, The credit limit check for the selected sales document type is set to automatic control.
Sales and Distribution Basic Functions Credit management / Risk management Credit Management Assign Sales Documents and Delivery Document Credit limit check for order types
u2022 Assigning Risk Category to Credit Control Area
Financial Accounting (New) Accounts Receivable and Account Payable Credit management Credit Control Account Define Risk Categories
u2022 Defining Automatic Credit Control
Financial Supply Chain Management Credit Management Integration with Accounts Receivable Accounting and Sales and Distribution Integration with Sales and Distribution Define Automatic Credit Control -
Relation Between Interest and Risk Categories for Customers
Hi
Can somebody tell me if there is a relationship between interest rates and risk categories. We have not implemented neither treasury nor Hedging.
Would like to link the interest as per the risk categories. As the risk changes, interest should also vary.
Can this be achieved
PrasadHi Prasad,
It is all AR functionality: Dunning/Interest Calculation/Credit Management/Risk Categories; I think it is doable to adjust interest on late payments based on customer risk category; but I doubt you will get detailed answer on this forum. FICO forum may be better.
Manish -
Dear sap gurus,
after implementing credit management in middle or not from beginning and if you want to have the history a particular customer updated in LIS or if we want to know about his credit exposure.
What should be done.Kindly help me.
regards,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.
Difference Between Simple and Automatic Credit Check Types
In automatic check, difference between static and dynamic checks.
SIMPLE CREDIT CHECK : Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value : Sales Order Has been saved but not delivered
Open Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received the payment from the customer.
Eg: Customer Credit Limit is Rs.1,00,000/-
Suppose Doc.Value + Open Item Value is Rs.1,10,000/-
Here credit limit exceeds then system reacts.
Options : A) Warning Message
B) Error Message (Sales Order won't be saved)
C) Error Message with Delivery Block
AUTOMATIC CREDIT CHECK : Give extra credit facilities to the particular customer.
STATIC CREDIT LIMIT DETERMINATION :Checking Group + Risk Catageory + Credit Control Area.
A) Credit Checking Groups : Types of Checking Groups.
01) Sales
02) Deliveries
03) Goods Issue
At all the above 3 levels orders can be blocked.
B) Risk Catageory : Based on the risk catageories company decide how much credit has to give to the customer.
HIGH RISK (0001) : LOW CREDIT
LOW RISK (0002) : MORE CREDIT
MEDIUM RISK(0003) : Average Credit
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value : Which is save but not delievered
2) Open Delivery Doc.Value : Which is delivered but not billed
3) Open Billing Doc.Value : Which is billed but not posted to FI
4) Open Item : Which is transfered to FI but not received from the customer.
DYNAMIC CREDIT CHECK : 1) Open Doc
2) Open Delivery
3) Open Billing
4) Open Items
5) Horizon Period = Eg.3Months
Here the System will not consider the above 1,2,3& 4 values for the lost 3 months
Then assign the Sales Doc & Del Documents.
Sales Doc.Type(OR) + credit Check(0) + Credit Group (01)
Credit Limit Check for Delivery Type : Del.Type (LF) + Del Credit
Group (02) + Goods Issue Credit Group (03)
Set Up for Credit Card Payment Processing
Given below is the set up for credit card payment processing:
Set Up Credit Control Areas:
Define Credit Control Area
Transaction: OB45
Tables: T014
Action: Define a credit control area and its associated currency. The Update Group should be u201800012u2019. This entry is required so the sales order will calculate the value to authorize
Assign Company Code to Credit Control Area
Transaction: OB38
Tables: T001
Action: Assign a default credit control area for each company code
Define Permitted Credit Control Area for a Company
Code
Transaction:
Tables: T001CM
Action: For each company code enter every credit control area that can be used
Identify Credit Price
Transaction: V/08
Tables: T683S
Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax. Make the following entries:
Sub to: u201CAu201D
Reqt: u201C2u201D
AltCTy: u201C4u201D
Automatic Credit Checking
Transaction: OVA8
Tables: T691F
Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed. You need to mark the field u201Cno Credit Checku201D with the valid number for sales documents.
Set Up Payment Guarantees
Define Forms of Payment Guarantee
Transaction: OVFD
Tables: T691K
Action: R/3 is delivered with form u201C02u201D defined for payment cards. Other than the descriptor, the only other entry should be u201C3u201D in the column labeled u201CPymtGuaCatu201D
Define Payment Guarantee Procedure
Transaction:
Tables: T691M/T691O
Action: Define a procedure and a description.
Forms of Payment Guarantee and make the following entries Sequential Number u201C1u201D
Payment Guarantee Form u201C02u201D
Routine Number u201C0u201D Routine Number can be used to validate payment card presence.
Define Customer Payment Guarantee Flag
Transaction:
Tables: T691P
Action: Define a flag to be stored in table.
Create Customer Payment Guarantee = u201CPayment Card Payment Cards (All Customers can use Payment Cards)u201D.
Define Sales Document Payment Guarantee Flag
Transaction:
Tables: T691R
Action: Define the flag that will be associated with sales document types that are relevant for payment cards
Assign Sales Document Payment Guarantee Flag
Transaction:
Tables: TVAK
Action: Assign the document flag type the sales documents types that are relevant for payment cards.
Determine Payment Guarantee Procedure
Transaction: OVFJ
Tables: T691U
Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure
Payment Card Configuration
Define Card Types
Transaction:
Tables: TVCIN
Action: Create the different card types plus the routine that validates the card for length and prefix (etcu2026)
Visa , Mastercard, American Express, and Discover
Create the following entries for each payment card
AMEX American Express ZCCARD_CHECK_AMEX Month
DC Discover Card ZCCARD_CHECK_DC Month*****
MC Mastercard ZCCARD_CHECK_MC Month
VISA Visa ZCCARD_CHECK_VISA Month
The Routines can be created based on the original routines delivered by SAP.
*****SAP does not deliver a card check for Discover Card. We created our own routine.
Define Card Categories
Transaction:
Tables: TVCTY
Action: Define the card category to determine if a
payment card is a credit card or a procurement card.
Create the following two entries
Cat Description One Card Additional Data
CC Credit Cards No-check No-check
PC Procurement Cards No-check Check
Determine Card Categories
Transaction:
Tables: TVCTD
Action: For each card category map the account number range to a card category. Multiple ranges are possible for each card category or a masking technique can be used. Get the card number ranges from user community. Below is just a sample of what I am aware are the different types of cards.
Visa Credit Expires in 7 days.
400000 405500
405505 405549
405555 415927
415929 424603
424606 427532
427534 428799
428900 471699
471700 499999
Visa Procurement Expires in 7 days.
405501 405504
405550 405554
415928 415928
424604 424605
427533 427533
428800 428899
Mastercard Credit Expires in 30 days
500000 540499
540600 554999
557000 599999
Mastercard Procurement Expires in 30 days
540500 540599
555000 556999
American Express Credit Expires in 30 days
340000 349999
370000 379999
Discover Card Credit Expires in 30 days
601100 601199
Set Sales Documents to accept Payment Card Information Transaction:
Tables: TVAK
Action: Review the listing of Sales Document types and enter u201C03u201D in the column labeled u201CPTu201D for each type which can accept a payment card
Configuration for Authorization Request
Maintain Authorization Requirements
Transaction: OV9A
Tables: TFRM
Action: Define and activate the abap requirement that determines when an authorization is sent. Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP).
Define Checking Group
Transaction:
Tables: CCPGA
Action: Define a checking group and enter the
description. Then follow the below guidelines for the remaining fields to be filled.
AuthReq Routine 901 is set here.
PreAu If checked R/3 will request an authorization for a .01 and the authorization will be flagged as such. (Insight does not use pre-authorization check).
A horizon This is the days in the future SAP will use to determine the value to authorize
(Insight does not use auth horizon period).
Valid You will get warning message if the payment card is expiring within 30 days of order entry date.
Assign Checking Group to Sales Document
Transaction:
Tables: TVAK
Action: Assign the checking group to the sales order types relevant for payment cards
Define Authorization Validity Periods
Transaction:
Tables: TVCIN
Action: For each card type enter the authorization validity period in days.
AMEX American Express 30
DC Discover card 30
MC Master card 30
VISA Visa 7
Configuration for clearing houses
Create new General Ledger Accounts
Transaction: FS01
Tables:
Action: Two General Ledger accounts need to be created for each payment card type. One for A/R reconciliation purposes and one for credit card clearing.
Maintain Condition Types
Transaction: OV85
Tables: T685
Action: Define a condition type for account determination and assign it to access sequence u201CA001u201D
Define account determination procedure
Transaction: OV86
Tables: T683 / T683S
Action: Define procedure name and select the procedure for control. Enter the condition type defined in the previous step.
Assign account determination procedure
Transaction:
Tables:
Action: Determine which billing type we are using for payment card process.
Authorization and Settlement Control
Transaction:
Tables: TCCAA
Action: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each.
Enter Merchant IDu2019s
Transaction:
Tables: TCCM
Action: Create the merchant idu2019s that the company uses to process payment cards
Assign merchant idu2019s
Transaction:
Tables: TCCAA
Action: Enter the merchant idu2019s with each clearinghouse account
Reward points if useful.
Regards,
Anbu -
Grace period in Credit Management
Hi All,
Can any one let me know how are grace periods in Risk categories maintained in Credit Management .
For Instance Low risk category:5days
Medium Risk Category :2days
And where does the effect can be seen ?
Regards,RajneeshHi...
Grace periods are configured based ipn risk category. Risk category is alloacted to the customer based on his past history. Like you dont want to block the customer who has good credit history but could not pay his last invoice on time and you want to give him 7 days grace period rather blocking the deliervy for the same. -
Risk Categories in OVA8 - New Customers
Hello,
We recently set up new risk categories in OVA8. One of the things we would like to do is put an overall block on any account in a risk category New Customer status. Our intentions were to block users from entering orders before we were able to complete the Credit Management set-up so that we can prevent orders from going in on accounts that we have not approved. Is anyone aware of a setting that would accomplish this?
Thanks, KevinMaintain billing block in the sales order type's Billing section in tcode VOV8.
To brief you on billing block - It indicates if the item is blocked for billing. The system can automatically propose a billing block for sales documents that must be checked before billing. If the system proposes a block, you can change the block manually for each item. If the system does not propose a block, enter one of values predefined for your system. If the item has more than one schedule line, the block applies to each line. You can change the block for individual schedule lines.
Simply, it can be controlled by giving authorization for VA01(CREATE), VA02(CHANGE) and VA03(DISPLAY). Give authorization to VA02 to one whom you want it to be controlled by. Give authorization VA01 and VA03 one who creates sale order. By doing so billing block can be removed by one who is authorization to access VA02.
OR
Maintain authorisation object.
Then auth object V_VBAK_AAT Activity 43 in Tcode SU21.
You need to create the object for field FAKSK ie. Billing block in VBAK.
Then you need to assign the same in respective roles.
Assign the same to the respective users.
Thanks & Regards
JP -
Hi,
Can anyone tell me where the risk categories are configured in Credit Management? Transaction code and Menu path.
Thanks
Raghu.Hi,
Risk categories are not linked to Credit Control Area. Risk Categories are assigned to Credit Master in Transaction Code FD32 / FD33.
Further for each risk category in Automatic credit control ?(T.code OVA8), the different checks to be carried out and the message (error / warning) is configured.
Thanks
Murali. -
What is credit management how should we tell
hi
gurus my question is what is credit management.
2) If one customer exceeds his credit limit the sales order is blocked in the enduser system. WHO will release that order. Whether enduser called his higher authority by telephone or mailed or it is automatically knows by the superior means who is working in the managerial level working in n.s.o.
thanks in advancehi
The customers credit limit is assigned to the customer by going to the Logistics overview screen, Accounting, Financial accounting, Accounts receivable, Master records, Credit management, Change.
A credit control area is an organizational unit that is comprised of one or more company codes.
Create a credit control area and assign it to a company code in the Enterprise structure under financial accounting.
A customers risk category is a grouping category that controls the credit checks when automatic credit control takes place.
In SD credit check can occur in only three places: sales order, delivery and goods issue.
The system can use a simple credit check, static credit check or a dynamic credit check.
The simple credit check is set at the document type level e.g., sales order, delivery etc.
Simple Credit Check
Assign credit limit check to the sales doc type:
A warning message
B Error message
C Delivery block
D Automatic credit control
SAP enables static and dynamic credit checks so that a sales order for a good customer with a low risk credit rating is created and a sales order for a high risk customer with a high risk rating for the same doc type is blocked.
Automatic credit control divides the sales doc types, delivery doc types, and goods issue into specific credit groups.
An outcome procedure is defined using the credit group, the customers risk category along with the credit control area.
Risk categories are defined in the FI module.
Create the different credit groups e.g., for sales order, delivery, goods issue.
Assign the credit groups to the sales and delivery doc types.
Now define the settings for automatic credit control -> combination of credit control area, customers risk category, and credit group.
All that remains is the assignment of the risk category to the customer master record. This occurs in Finance by going to the Logistics overview screen -> Accounting, Financial Accounting, Accounts receivable, Master records, Credit management, Change or FD32.
The static credit check is a check comparing the credit limit assigned to the customer to the total value of open sales orders, plus the total value of open deliveries not yet invoiced, plus the total value of open billing documents not yet passed on to accounting, plus the total value of billing documents that have been passed on to accounting, but which have not been paid by the customer.
The dynamic credit check is a check comparing the credit limit assigned to the customer to the total value of open sales orders not yet delivered, plus the total value of open deliveries not yet invoiced, plus the total value of open billing documents not yet passed on to accounting, plus the total value of billing documents that have been passed on to accounting, but which have not been paid by the customer. The dynamic credit check has an attached time period that states that the system is not to include sales orders in the total of outstanding items created after the specified time period.
The credit relevant data is updated into an information structure, where it is accessed and updated. Thus each automatic credit control must be assigned an update group. The system allows for no update, and update group 000012, 000015 and 000018. However, update group 000012 is thorough and used in most businesses.
To view the customers credit master sheet, proceed from the logistics screen and go to accounting, financial accounting, accounts receivable, environment, credit management, check, credit master sheet [F.35].
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.
Reward if USeful
Thanx & Regrads.
Naren.. -
How will i configure credit management
how will i configure credit management....
Hello Prasanta
Following r the steps to configure for credit mgmt
1)First of all you hv to maintain CCA.If u want to maintain the same credit limit to all customers by default wen they r creatd, u hv to define it wen u create CCA.tcode:OB45
2)In OB38 u hv to assign CCODE to CCA
3)In OBFL , assign Sorg-DistChannel-Div-CCA
4)In OBZK assign CCODE -CCA
5)In OVAK, assign Sales doc type to Credit Gr and credit check
6)In OVAD , assign Delvry Doc type to the Credit Gr
7)In OVA6 , assign credit gr for diff doc types
8) In OB01 define risk categories
9)In FD32 , U CAN SET Credit limit to customers.
10) In OVA8 U CAN DO THE SETTINGS FOR AUTOMAtic credit check.The combination of CCA , rISK CATEGORY AND DOC TYPES helps to determine the kind of credit check the system automatically carries out.
Hope the above steps will help u out.
Plz reward pts if helpful
Regds,
Pallavi -
Link between sales order to Credit management
Where can we link between sales order to Credit management?
HI Gopala rao.,
In VOV8 sales document type there is <b>credit limit & Credit group</b> Where we asign the credit mage,ment data to Order
The configuration part of credit managemnt is
CREDIT MANAGEMENT:
A credit limit may be a customers credit limit, which is the permitted limit of value of open items, such as invoices not yet paid, plus the value of open sales orders.
The credit limit is the total combined value of the following documents:
Net value of sales order
Open Sales order: order created, but not delivered
Open deliveries: delivered, but not invoiced
Open billing doc: value of billing doc, which has not yet been forwarded to accounting
Open items: forwarded to accounting, but not settled.
Types of Credit Check
Simple Credit Check
Automatic Credit Check
o Static
o Dynamic
Simple Credit Check:
SPRO- IMG- SD- Basic Functions- Credit Mgmt/ Risk Mgmt- Simple Credit Check- Assign Credit Check to Doc Types.
Based on sales doc types
It will check all the above-mentioned docs & if the credit limit exceeds, the system responds in the way defined by you in the configuration menu.
Cannot differentiate according to customer
3 ways to Control the Simple Credit Check:
A: warning
B: error message: the doc cannot be saved
C: warning message with delivery block: the doc can be saved but is automatically blocked for delivery.
Automatic Credit Check:
This credit mgmt control is maintained by using the automatic credit control functionality. The automatic credit control divides the sales doc types, the delivery doc types, & goods issue into specific credit groups. It also uses the customers risk category as assigned to the CMD of the payer & assigns an outcome proc to the combination of the above 2 objects, i.e. the credit group & customer risk category along with the credit control area. The definition of customers risk category is carried out in the fin accounting module.
A customers risk category is a grouping category that controls the credit check when automatic credit control takes place. Thus one can assign high-risk customers to risk category for e.g. A01, medium risk to B01 and low risk to C01.
Automatic credit check divides customers in to 3 categories:
High-risk customers,
Low risk customers &
Medium risk customers.
A credit check can only occur at 3 places: Credit Group
Sales order: for high risk customers
Delivery: for medium risk customers
Goods Issue: for low risk customers
Credit Control Area (CCA): highest organizational element in credit management. A credit control area is an organizational unit that is comprised of one or more company codes. A company code can have no more than one credit control area. Defined by FI.
Menu Path to create Credit Control Area: OB45: FI people.
SPRO- IMG- Enterprise Stru- Definition- Fin Accounting- Define Credit Control Area
Credit Control Area Description
0001 Credit control area 0001
1000 Credit control area Europe
Menu Path to Assign Company Code to Credit Control Area: OB38: FI people.
SPRO- IMG- Ent Stru- Assignment- Fin Accounting- Assign Comp Code to CCA
It is possible to assign Credit Control Area to a Sales Area. This is more specific assignment than the assignment to Company Code.
Company code Company name City Credit Control Area Over write CCA
Menu Path for Defining Risk Categories: OB01: FI people
SPRO- IMG- Fin Accounting- Account Receivables & Payables- Credit Mgmt- Credit Control Account- Define Risk Categories.
Risk Category CCA Name
001 4500 Low risk
002 4500 Medium risk
003 4500 High risk
Menu Path for defining Credit Groups: OVA6
SPRO- IMG- SD- Basic Function- Credit Mgmt/ Risk Mgmt- Credit Mgmt:
Define Credit Groups: OVA6
Assign Credit Groups to Sales Docs & Delivery Docs
o Credit Limit check for Order Types: OVAK
o Credit Limit check for Delivery Types: OVAD
Define Automatic Credit Control: OVA8
Define Credit Croups: OVA6
One merely creates a credit group for each differentiation in the doc type. You enter the credit groups when you configure the sales doc types for credit management & define the automatic credit check. The following credit groups are contained in the standard R/3 system:
01: credit group for sales order
02: credit group for delivery
03: credit group for goods issue
CG (Credit Group) Doc Credit Group
01 Credit group for sales order
02 Credit group for delivery
03 Credit group for goods issue
Assign Sales Documents & Delivery Documents:
Sales Doc Type Descp Check Credit Credit Group
OR Std Order D 01
Delivery Type Descp Del Credit Group GI Credit Group
LF Delivery 02 03
Define for each sales doc type whether a credit check should be carried out. Enter D if an automatic credit check should be carried out.
Specify a Credit Group
Specify a Credit Group for the Delivery Type for which you want to carry out a credit check
Specify a Goods Issue Credit Group for the Delivery Type for which a credit check is to be carried out for goods issue.
SIMPLE CREDIT CHECK CANNOT BE ASSIGNED TO DOCUMENTS.
Define Automatic Credit Control:
One can now assign settings to the combination of the Credit Control Area, the Customer Risk Category & the Credit Group.
CCA Risk Cat Credit Group Credit Control
4500 001 01 Low risk sales orders
4500 001 02 Low risk deliveries
4500 001 03 Low risk goods issue
4500 002 01 Medium risk sales orders
4500 002 02 Medium risk deliveries
4500 002 03 Medium risk goods issue
4500 003 01 High risk sales orders
4500 003 02 High risk deliveries
4500 003 03 High risk goods issue
Select line item and go to details, you can decide whether to do Static or Dynamic Credit Check. Credit Horizon can also assigned here. Additional function checks can be performed here:
A credit check when the maximum document value is exceeded.
A credit check when changing critical fields.
The risk category assignment occurs in the same place as the customers credit limit, which is the customers credit management screen. That is, the risk category is assigned to the customer by the Finance in transaction code FD32.
The customer credit master record is divided in to 5 views:
Overview Screen: gives an overview of credit settings in relation to the customer, including his credit limit, credit exposure, the %tage of credit limit used, his payment data & his risk category.
Address: view gives the customers address details as they appear in CMD
Central Data: is a view that shows the total credit limit the customer can receive across all credit control areas as well as the maximum limit he can receive in one credit control area.
Status: view shows the customers actual individual details according to particular CCA being investigated. This includes his credit limit, percentage used, credit exposure, risk category, whether he is blocked due to credit or not.
Payment history: view displays the payments made by the customer for a particular credit control area where a comp code is assigned.
Static Credit Check Dynamic Credit Check
Net Doc Value Net Doc Value
Open Order Open Order
Open Delivery Open Delivery
Open Billing Open Billing
Open Item Open Item
Compares the total combined values of the above-mentioned documents to credit limit. Plus credit horizon. Compares the values of the following documents to credit limit + credit horizon.
Credit horizon has an attached time period that states that the system is not to include sales orders in the total of outstanding items created after that specified period i.e. for the purpose of evaluating credit, you want the system to ignore all open orders that are due for delivery after the horizon date. Maintained for low & medium risk customers.
Update Groups
Basically it is a info structure where system stores all the data about credit limit. The credit relevant data is updated in a info structure, where it is accessed & updated. Thus each automatic credit control must be assigned an update group.
Update Group 000012
Update Group 000015: delivery & billing
Update Group 000018: sales order, delivery & billing.
Update group 000012, updates at:
Sales doc: increased order value
Delivery: decreased order value & increased delivery value
Billing: decreased delivery value & increased billing amount
Invoice: decreased billing amount & increased open item value.
Release Blocked Sales Order/ Deliveries:
VKM3: sales order
VKM5: delivery
VKM4: both
One can see the offending document. Note on the right hand side, the Status Field. This shows the check, the doc failed. If this field is empty, the doc did not fail a credit check, even though it may be in the list of SD documents that are required to be released.
To release the doc, one indicates the doc to be released and then clicks on the Release Button. The result is the offending doc entry, highlighted green. One then proceeds to save, after which you are informed the doc number has been released.
Net value with sub total A, in pricing proc, will be the basis for credit limit.
REWARD if helpfull
Thanks & Regards
Narayana
Message was edited by:
manam narayana -
Credit Management - Maximum time overdue limit for open item
Dear all,
I've this scenario to configure for automatic credit control. A customer is billed on Jan 22nd '10 and now the account receiveable shows an open item. This customer is allowed 52 calendar days to make payment for this invoice, hence no credit block yet. As such, the customer can still make orders.
In my existing configuration, I've already enable "static" credit check on "open orders" and "open deliveries". The static check is to check against the customer's credit limit.
So, if I were to add in the earlier mentioned overdue open items check, is it sufficient to just maintain the field "Days oldestItem" with "52" within the automatic credit control screen?
Thanks.
StevenHi
The sytstem will shows oldest open items depending on the payment terms from the invoice date.
Once it crosses the days of payment then it will show in oldest open items
if you want to extend some more days for that then you need to maintain the days in "Days oldestitem" the automatic credit control area
Prerequisites for credit management to work in Sales and Distribution:
1.Assign credit control area to company code
2.Maintain the credit limit in FD32 with details of risk category and the credit limit value
3.Do the settings in OVA8 -automatic credit control area with combination of Credit control area/Risk category /credit group.
4.Assign the credit groups to the sales and delivery document types.
5.Maintain the Subtotal 'A' in the pricing procedure against which value the sytem should check the credit limit.
If you have any further clarifications on above let me know
Regards
Damu
Maybe you are looking for
-
How to filter parent and child tables data in impdp?
Hi Friends, i hope everyone doing good.. I have two tables in my schema like below. STUDENT_DTLS:- SID Sname CID 1 venkat 001 2 uppy 002 3 deepu 003 4 trinath 003 5 naveen 004 6 ramesh 005 COURSE_DTLS:-
-
CS3/Designer ES - PDF Form Fields
Hello, I currently create my flyers through AI and convert to pdf for electronic distribution. I am hoping to have end user inputted information through form fields in my pdfs. Is there a way to create form fields in AI that will be exported as such
-
[b] bad magic number [/b]
hallo, first sorry for my bad english but i'm from austria. i wrote a html-page in which a applet is called using object tag. if i click on this page open it with ie there is no problem, but when i return this page with an servlet i get the following
-
How to Query/Lookup Data Target HFM Application in FDMEE Import / Validation Step
Hi Experts, We are using FDMEE 11.1.2.3.500 to load 2 sets of Flat Files - ICP Trial Balances and Non-ICP Trial Balances. The ICP Trial Balances will be loaded to Target HFM Application first using FDMEE and then the remaining Non-ICP Trial balances
-
What is the major difference between two Mac Minis?
Hello, I noticed the differences between the Mac mini MC815LL/A and MC816LL/A do not add up to $200 price difference. They both are I5 (with different versions of course) and they have different memory (which is realatively easy and cheap to modify).