Customer Credit Management Change
Hello Gurus,
I am trying to implement credit management and when i am using FD32, i am not able to enter anything in the fields other than Horizon. What should i do in order to maintain credit management completely. Please help. Thanks.
Regards,
Pranava
Dear,
Please go via this link,
[http://www.sap-img.com/sap-sd/credit-management.htm]
please search the thread before posting your question.
Regards,
Sandip
Similar Messages
-
Customer credit management IDOC
Hi,
I am using scenario: if a customer credit management document is changed in R/3. Send the change as an IDOC to CRM. Can you please identify any standard IDOC for customer credit management or I will have to use customer master IDOC DEBMAS (but I do not have DEBMAS idoc type in CRM).
Thanks in advance!
Regards,
FaiqA new Credit Control Area is created in the Configuration menu (IMG - transaction SPRO). Path: Enterprise Structure>Definition>Financial Accounting>Define Credit Control Area.
There are also additional tasks like assigning the Credit Control Area to the Company code........etc.
If you do not have access to the IMG then your SAP support team will be able to do it.
Once created you can do what you need to do as per previous posts. -
AR Report Requirement - Customer Credit Management - 0FI_AR_9
HI There,
We have a requirement in AR report to add the below fields from Customer Credit Management Datasource 0FI_AR_9
KNKLI - Credit Control Account- 0CRED_ACCNT
KLIMK - Credit Limit - 0CRED_LIMIT
CTLPC - Risk Category - 0RISK_CATEG
Except KNKLI (Credit control account), remaining two fields are master data.
Can we use the data from 0FI_AR_9 by writing look up? Please suggest.
Thanks
VandanaHi,vandana_ir
i don't know what's your requirement else,if you wanna add those fields to the report
those below solution may be can help you
1.data loading into InfoObject etc.0customer
2.using virutal key figure tech to read customer value from infoObject. -
Bapi for customer credit management
Dear Gurus,
Can u tell me the bapi for FD32 .ie. customer cedit management.
If u have any customised bapi then do send me the same.
Points will be awarded for every try.
Regards,
Mohan.Hi,
There is a standard function module 'CREDITLIMIT_CHANGE' which can be used to insert or update credit limits and therefore credit master data.
Two indicators, UPD_KNKA and UPD_KNKK are available to indicate whether you want to create credit master data or update or delete existing data. UPD_KNKA is for central data and the other for credit control area data.
There may be technical differences between BAPI and a normal function module, but for all functional purposes this FM can be used just like a BAPI.
Cheers,
KC
SAP SD -
SD CREDIT MANAGEMENT - CUSTOMER AND PERIODWISE
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 ChakrabortyHi,
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 -
I want to set dynamic customer credit limit for a customer
Hi,
I want to set a dynamic credit limit for a customer which should trigger during the time of Sales Order Creation.
Can anyone please let me know the settings one has to do to implement this process in the system ?Hi Below is the whole process for confign.
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.
Regds
MM -
Regarding open items in credit management
Dear friends
My query is that is it possible to restrict credit management for credit and debit open items? See i am using oldest open item blocking in my scenario. Now credit and debit amounts are both considered as open item for credit management. I want only invoice (Debit entry) for consideration and not his payment(credit entry).
Please advise is it possible or not and if possible where to define that???
With regards
InderHi,
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
V_TVTW Define Distribution Channel
V_TVTA_KKB Assign sales area to credit control area
V_T014 FI - Define Credit Control Area
T001CM - FI Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel Division Distribution Channel Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
Check Credit
A Credit limit check and warning message
B Credit limit check and error message (no sales order can be created)
C Credit limit check and delivery block (block delivery if hit credit limit)
Options B and C -> used for checking open order values (when you create/change the sales order)
D Automatic credit control with open order values
More control in transaction OVA8 - Automatic credit control
You check for open orders and deliveries, or just open deliveries.
or open order values with other options
Credit group
Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D automatic credit check).
SAP default credit groups
01 credit group for sales order
02 credit group for delivery
03 credit group for goods issue
OVA8 - Automatic credit control Double click on the line items
You can have the followings credit limit check :-
Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
Oldest open items
If you dont want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.
You can use the NextReview date and Number of days fields and combined it with the Last int.review field in customer credit master Status view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
regards,
Siddharth. -
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 -
Credit Management System - Update of SD Documents after CMS start
Hi,
we are starting CMS functionality in our SD module. CMS (Credit Management System) works remotely by an XI connection. When we switch to use CMS in production system, we have to transfer all opened orders (not yet invoiced) to CMS system.
How can we achieve it? Can program RFDKLI20 (t-code F.28) be used for this purpose? Does it require any settings to point out the CMS connection?
Thank you
/BRHi Wojciech
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.
Reward if useful to u -
Credit management static check
Hi all,
i want to configure STATIC CHECK in my organization. My organization is operating with one sales org but many sales area. i want to configure static check to only export customers served by only one sales area xxxx/yy/zz. yy is distribution channel specially for exports & zz is specially export division with products specifically to be sold to export customers.There are almost 28 export customers. will static check be configured customer based or sales area based or sales org based.
Please guide.
regards
vikas chhabra
098714 88 718
[email protected]hi,
pl check this ;
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.
Hope it helps.
Thanks
Sadhu Kishore -
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.. -
Credit management....sales area data
hi gurus,,
I have some doubts in Credit Management>
1. In my development Server....Customer Master data > Sales Area Data > Billing Tab Page>CREDIT CONTROL AREA...is not reflecting.
using version 4.7... why is was not reflecting... any configaration settings is required??.
Anybody having configuration material of CREDIT MANAGEMENT and FREE GOODS DETERMINATION..
MAIL ID::: [email protected]Hi ravi,
Notes on Credit mangement
SAP SD Credit Management
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
V_TVTW - Define Distribution Channel
V_TVTA_KKB - Assign sales area to credit control area
V_T014 - FI - Define Credit Control Area
T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel
Division
Distribution Channel
Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
Check Credit
A - Credit limit check and warning message
B - Credit limit check and error message (no sales order can be created)
C - Credit limit check and delivery block (block delivery if hit credit limit)
Options B and C -> used for checking open order values (when you create/change the sales order)
D - Automatic credit control with open order values
More control in transaction OVA8 - Automatic credit control
You check for open orders and deliveries, or just open deliveries.
or open order values with other options
Credit group
Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
SAP default credit groups
01 - credit group for sales order
02 - credit group for delivery
03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
Oldest open items
If you don't want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.
You can use the "NextReview date" and "Number of days" fields and combined it with the "Last int.review" field in customer credit master "Status" view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
Free goods determination
Free Goods Determination in Sales Order
Free goods has the following limitations:
- Free goods can only be supported on a 1:1 ratio. This means that an order item can lead to a free goods item. Agreements in the following form are not supported: With material 1, material 2 and material 3 are free of charge or If material 1 and material 2 are ordered at the same time, then material 3 is free of charge.
- Free goods are not supported in combinations with material structures (for example, product selection, BOM, variants with BOM explosion).
- Free goods are only supported for sales orders with document category C (for example, not quotations).
- Free goods are not supported for deliveries without reference to a sales order.
- Free goods cannot be used in make-to-order production, third-party order processing and scheduling agreements.
- If you defined a free goods for variants in a generic article (only SAP Retail), you can only process the variants in the purchase order and goods receipt individually (as single articles). In other words, you cannot process them using the generic article matrix.
4.6x
Not all Sales Order can be used for free goods determination. You have to check the SD document category if it does not work. Only category 'C' are supported. Check transaction VOV8.
Assume that you want to configure an inclusive FREE goods routine. Customers must order a minumum quantity of 5 before any free goods can be assign. For every quantity of 3, the customer will be given 1 free goods.
WC07 - Maintain Number Range Intervals
e.g.
No From number To number
01 0000010000 0000099999
IMG -> Sales and Distribution -> Basic Functions -> Free Goods ->
Maintain Access Sequences
New Entries
Acsq
NA00
Save
Maintain Condition Types
New Entries
Ctyp Name AcSq
FREE Free Goods NA00
Save
Maintain Pricing Procedures
Procedures
New Entries
Procedure Description
FREE Free Goods
Select Procedure FREE then click Control data
Step Cntr Ctyp
10 10 FREE
V/N6 - Activate Free Goods Determination
Assign Order Type OR with Document Procedure A with Procedure FREE
VBN1 - Create free goods determination
e.g. FREE inclusive
Material Min qty From are free good Calc Rule Free Goods
5 3 1 1 1
In this example, if you create a Sales Order for a quantity of 10, SAP will prompt you 7 as the customer order qty and 3 will be free. Customer only pay for the 7 quantity.
Reward points if it helpful -
hi
How the system calculate credit limit in sales order. mean how it pickup the previuos vales and add with net doc value.
regards
muraliHI Murali
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.
Reward if useful to u -
HI,
APART FROM GLEN WILLIAMS CAN ANYONE TELL ME MORE OF CREDIT MANAGEMENT & BILLING ?
RAJARSHIHi,
Notes on Credit mangement
SAP SD Credit Management
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
V_TVTW - Define Distribution Channel
V_TVTA_KKB - Assign sales area to credit control area
V_T014 - FI - Define Credit Control Area
T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel
Division
Distribution Channel
Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
Check Credit
A - Credit limit check and warning message
B - Credit limit check and error message (no sales order can be created)
C - Credit limit check and delivery block (block delivery if hit credit limit)
Options B and C -> used for checking open order values (when you create/change the sales order)
D - Automatic credit control with open order values
More control in transaction OVA8 - Automatic credit control
You check for open orders and deliveries, or just open deliveries.
or open order values with other options
Credit group
Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
SAP default credit groups
01 - credit group for sales order
02 - credit group for delivery
03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
Oldest open items
If you don't want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.
You can use the "NextReview date" and "Number of days" fields and combined it with the "Last int.review" field in customer credit master "Status" view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
Reward points if it helpful
Sree -
Sales value filed in Customer credit limit
Hi Friends,
User is asking about the details of the amount which is there in the sales value field in (customer credit management T-code FD33) , with this field i come to know it is coming from Total of all order values which have not been transferred to FI, but which are taken into consideration when checking the credit limit.
But i am not able to identify the amount.from where it is coming and wht to check, how to find the open sales orders wht is the table name.
Please let me know how can i find the value, where to check and wht is the table, t-code.Please its bit important.
Regards
SreeHi,
if you don't get a list of sales documents for this particular customer when executing RVKRED88
1: check your selection parameters
2: maybe there are no open sales orders / deliveries / billing docs (if you want to be sure, create a new sales order in test environment and run RVKRED88 again)
3: maybe your credit-management customizing does not consider the sales documents you expect as relevant for credit management.
Follow SAPNET note 18613 (especially point 7 and 8), this note is a checklist for credit management settings.
best regards, Christian
Maybe you are looking for
-
JQuery/Javascript not working on Firefox and Chrome
Hi guys, I've had this Jquery/Javascript on my page for a long time. This has stopped working. If the user clicks on buttons on the Apex page, nothing happens. It works on IE but doesn't work on Firefox and Chrome. It used to work fine. Is there anyt
-
Still in trial mode despite use of redemption code
I was given a year subscription by an adobe employee as they are trying to convert all the editors at my job to Premiere Pro from FCP. I received the email with the code and entered it, then I downloaded a bunch of apps but they all ask for a serial
-
Help: AM Agent working with load balancing AM Server
Hi, We are trying to set up the policy agent to work with two AM Servers behind a load balancer. The agent deployment document said that in the AMAgent.properties we must set com.sun.am.loadBalancer_enable=true According to the AM deployment guide(ht
-
Auto Answer will NOT stay on after power cycle or reset - C20 TC7.3.0 UCM 10.5SU1 registration
As the title suggests, I've got 2 C20 codecs running the latest 7.3.0 code I can download registered to UCM 10.5.1 SU1. Power cycling or resetting them causes the auto-answer to default to off. There is still no way to change auto-answer from withi
-
Add Video to Site. Looking for basic tutorials
Thanks to a lot of help from this forum I have cobbled together a reasonable web site. Now I am adding some video and am confused as to some best practices. I have had some reels of 8mm film converted to digital and are now individual *.mov files. Us