Open Billing Doc value table in Credit management

Hello All,
I am having the open billing document vaule in credit management,
I need the details that from which billing document, what value has come.
Is there any table for get these details.
Advance thanks
Thanks and Regards
Sridhar

Hi,
the system updates open values for credit management. These are:
Open sales order credit value (S066-OEIKW)
Open delivery credit value (S067-OLIKW)
Open billing document credit value (S067-OFAKW)
The system updates the open values in standard SIS structures S066 and S067. Technically, the structures are transparent tables. You can display the contents using transaction SE16 or using table maintenance.
The S067-OLIKW will give the open delivery credit values credit.Check in you system whether this table is updated with the delivery values for the credit account(customer number)
RVKRED77 u2013 Reorganize SD credit data
When updating errors occur, it enables you to reorganize the open credit, delivery and billing document values.
If the table is not updated run this report in background.
Regards,
Saju.S

Similar Messages

Tables of credit Management

HI!!,
Please let me know list of tables in Credit management.
-AKASH

Hi Akash Tambi
T691F Control of Automatic Credit Control
KNKA Customer master credit management: Central
KNKK Customer master credit management: Control
KNKKF1 Credit Management: FI Status Data
KNKKF2 Credit Management: Open Items by Days in A
KLPARAM Credit Limit: Tab for Controlling Ext. Def
KLSDCPARAM Credit Limit: Controlling External Default
UKM_TRANSFER_AR Data from AR for SAP Credit Management
UKM_TRANSFER_ARV Data from AR for SAP Credit Management
VBKK SD Doc.Export Letter of Credit
VBUK Sales Document: Header Status and Administ
VBUP Sales Document: Item Status
T014 Credit control areas
T014N New credit control areas to be set up
T014T Credit control area names
T024B Credit management: Credit representative g
T024P Credit Management: Credit Representatives
T042U Block Entries for Debit Customers/Credit V
T5UDO Benefit credit grouping
Reward if useful to u

Open sales orders and open deliveries and open billing doc to sap from legesy

Dear all
i have some open sales orders and open deliveries and open billing doc are there in the legesy system
so i want to know how to transfer the doc to sap by using lsmw plz tell me

Hi Amith,
it is always good to search in Google before posting .LSMW is very old topic and i am sure you will get lots of Documents on this .Please go through the below link .you will get some idea on this.
http://scn.sap.com/thread/1012472
there are 14 steps in LSMW and it is same for all (master data and Transaction Data)
Pls practice this in your sand box or quality system before working it in the client requirement.
Hope this helps to you
Regards
Sundar

CREDIT MANAGEMENT-- Not Considering open S.O. value while checking Credit

Dear all,
I have an issue in credit manangenet i have configure credit manangement in SD at Sales order level it is like if Customer does not have credit balance it will not allow to save the order.
But issue is that if Customer have RS.10000 as his credit limit or advances in FD32. I am able to raise order for less that Rs.10000
and it will allow me to save and it is ok but the issue is that if I go agian to raise an order for less than credit limit it is allowing me to save means it is not cosidering the open sales order value which I want.
Please suggest me what to do for this issue.your reply will be highlt appriciable.
Regards
AJIT K SINGH

Hi
First check in the FD32 the risk category isassigned or not
check the sale document type credit group should be 01.
check in the ova8 select the static button and selct the open order field should be activate
and also check the open order field selct the B otpion and status butoon should be activated
NOte: In OVA8 deactivate the dyanmic field and dont maintin the horizon period.
Thanks.
Vasu
Edited by: Vasu Enaguthi on Apr 12, 2010 9:08 AM
Edited by: Vasu Enaguthi on Apr 12, 2010 9:09 AM
Edited by: Vasu Enaguthi on Apr 12, 2010 9:14 AM

Where is Open Sales Order Value coming in Credit Master sheet?

We have a customer whose credit exposure is below credit limit. I'm in Customer Credit Management overview screen and I ran Credit Master sheet report (for this CMR) under Environment -> Reporting -> Credit Master Sheet.
I see value in Receivables and Open Sales Order Value which sums up to Credit Exposure Value. I'm wondering which sales orders are considered to calculate open sales order value?
I ran different order reports like VA05 and some custom reports available, but I could not find a direct report that matches the open sales order value.
I manually compared Open Sales orders based on Horizon date, the value that I'm arriving is kind of close of Open Sales Order Value in Credit master sheet report.
Update rule used is 000012 in automatic credit control screen.
Please let me know if there is an easiest way to find data behind Open Sales Order Value in Credit master sheet report.
Appreciate any help!

. I'm wondering which sales orders are considered to calculate open sales order value?
Those customer orders which are relevant for credit limit. Please let me know if you are talking about something different?
I ran different order reports like VA05 and some custom reports available, but I could not find a direct report that matches the open sales order value
.You can not compare the VA05 open sales order report with FD32 open sales order report.
You can find out the open order values of Credit manangement(FD32) in S066 table.
Please let me know if there is an easiest way to find data behind Open Sales Order Value in Credit master sheet report.
For open sales order you can find out in S066 table and sales values in KNKK table

"Sales value" in FD33, credit management

Hi Experts,
I have configured Credit management.
After creating a sales order. The field "Sales value" (RF02L-SAUFT) in FD33 is NOT getting updated. It remains 0,00.
After I have created a bill, field "Receivables" gets updated.
Could you please advise how field "Sales value" could be correctly updated (i.e. with values of the sales orders that have not yet been transferred to FI )?
Because of the above, I can not get a warning or error message, at creation of sales order stage, when credit exposure > credit limit.
PS - I have tried VKM3, releasing sales orders, but issue still persists.
I have also executed RVKRED77

Hey!
Go to transaction VOV7 and make sure of the following:
n item is relevant for billing
n item is relevant for credit
n the item does not have a check mark in ‘item relv for delv’. This is for text and value items which have no value in R/3 – see note 67748
n the item is not statistical
If these are not configured correctly, the item will have no value.
Go to the sales order and make sure that the items have a confirmed schedule line. Without a confirmed schedule line, the item will have no credit value. Next check the pricing procedure. You can go to the analysis button to find out which pricing procedure is being used. Go to transaction V/08 and go to the details level of the pricing procedure. Make sure that an ‘A’ is set in the ‘Sub to’ column for something reasonable like the total of the document.
Hope it helps.

Open Billing doc.in VF05

Hi,
We have created some Invoices in period 01/05/2011 to 10/05/2011 for acoounting document has not been cleared for payer X.
When we are taking the report for open billing document in VF05 for that payer for that period system is not showing any values giving the message no worklist is find.
But system should show all those billing dicument numbers whose accounting document has not been clear but not showing those documents.
why system is not showing thosse document numbers?
how to resolve this? since this is standard report it should not be happen.
thnaks,
anup

Hi,
If you want see the List of Open Billing document and also those documents already been generated accounting document but payment not yet cleared
Use the following T-Code VF05N
other try to follow if you want to release the billing documents go to T-Code VFX3
Regards,
Prasanna

Difference in Billing doc value & MCSI report

Hi Gurus,
What could be the difference in value between the billing value & the MCSI report?
Regards,
Kumar

Hello,
MCSI is based on infostructure and updated on the execution of transaction.If at the time of creation of billing document ,you have not configure the billing doc type,item category and not assign the proper update group to them then MCSI will not be updated and later on you will find the difference in MCSI nad total billing value.
Sunil

Generating both 'G2' and 'IG' billing docs from a single credit memo req.

We have a need to generate both a 'G2' (customer credit memo) and an 'IG' (inter-company credit memo) from a single Credit Memo Request.
Is this possible with config and/or user exits in R/3 4.7?
<u>Background</u>
We have cases where all sales by a given Sales Org. (related to Company 'A') are supplied by plant(s) related to Company 'B'. When a standard order is processed through billing, both an 'F2' (customer invoice) and an 'IV' (inter-company invoice) are generated, with the value of the 'IV' derived from the value of the 'F2'.
In the event that there was a pricing error on the 'F2', we are required to create a Credit Memo Request, which leads to a 'G2' (customer credit memo) correcting the customer's account.
We want to be able to also generate an 'IG' (inter-company credit memo) from this same Credit memo Request to adjust the 'Sales Org's account').

Hi
Customer credit memo is created with reference to Customer credit memo request
Internal credit memo is created with reference to customer returns delivery.
so process the flow
Credit memo request -->returns delivery
Credit memo request-->customer credit memo(order releated)
Returns delivery-->internal credit memo.(as internal credit memo is delivary related)
Let me know if issues exists,
Reward if this helps
Regards
Simu

Regarding Open items in Tcode OVA8 in Credit Management

Assignment of Credit control area to sales area is not maintained& Item category is not credit active. But it is blocking some customers for open items for order. I want to know the reason. and also. Credit limit is defined for all customers &Credit control area is defined for all Customer master data. But blocking only 2 customers for open items . I will be thankful if any one answer to the reply . And i want to know the implication of open items in OVA8.
Regards
Madhav

01.12.2008
Hi madav,
Try executing check_cm thru SE38. You should get a clue.
Regards,
Uday

Credit management urgent

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

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: Difference Between Static and Dynamic Credit Check

Hi,
Could anyone tell the difference Between Static and Dynamic Credit Check?
According to website: http://www.sap-basis-abap.com/sd/difference-between-static-and-dynamic-credit-check.htm ... this is the answer:
====================
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.
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.
====================
Question 1: Could you further explain the above information, if there is any?
Question 2:: What is the Tcode to customize settings of:
a) Simple Credit Check (isn't this same with b) below?)
b) Static Credit Check
c) Dynamic Credit Check

Hi Tanish,
Diff between Static and Dynamic Filters.
Example One at report Level.
Create a variable for a Infoobject say ,Material .
1)In the Query Designer and if u restrict it to some 10 materials at query level, the report will display for only those 10 materials only.This is Static Filter.UR AHrdcoding it to those materials.You cant change them at Query Run time.i.e not changeable by user.
2)If u give the variable as input ,and when u run the query ,u can can choose the material,may 10 may be 1 or may 20 .It is dynamic.Changeable by user at run time
Example Two at DTP and Start Routine Level,say Document Type.
1)If u give filters in Start routine it is Static as u cannot change it in Production,not changeable by user.
2)f u give filters in DTP it is Dyanamic as u can change it in Production.U can give any doc type,Changeable by user at run time.
Hope it is Understood.
Rgds
SVU

Credit Management-Sales value updated in FD32 even though credit set up is not active

Dear Team,
We are facing an issue where, for a sample order - sales value got updated as open sales order value against a customer in FD33.
Credit set up is not active for the sales order type (OVAK) or the delivery type (OVAD). Since this has occurred in 2003, we have no clue what exactly has happened. We cannot locate any change logs in the configuration level.
1) What is the possibility for credit management to be active for a document type, which was not meant for credit set up?
2) How to remove the open order/ delivery value for the customer?
Thanks and regards.
Sivarajesh

Credit set up is not active for the sales order type (OVAK) or the delivery type (OVAD).
the above two settings are credit checks at what level( example order level or delivery etc) you what to block the customer if the customer payer exceeds the credit limit.
Where as if the credit active field is active in VOV7 in corresponding item category, system update the respective document values in to credit management (FD32/33) in your example open order value.
Even though OVAK, OVAD settings are not done still system update the document values in to FD33 subject to credit active field is active in t code VOV7 .
Please check in your item category whether credit active field active.
thanks,
Srinu.

Rebate: Differ "Scale Base Value" between "Statistics" and "Billing Doc"

Dear SD Expert,
After I go with Transaction Code :"VOB3" (run report RV15B002), I found that "Scale Base Value" have different value between "Statistics" and "Billing Doc". And the correct value is "Billing Doc". However, the value which shows in my rebate condition now is "Statistic". Thus, my question is
How can I configure my rebate condition based on "Billing Doc" Value instead of "Statistic"? (I don't want to "Correct backlogs" anytime in changing scales based value.) Anyone please feel free in suggestion.
Thanks,
Prach

HI,
This may be useful to you.
http://help.sap.com/saphelp_47x200/helpdata/en/dd/5612d8545a11d1a7020000e829fd11/content.htm
Vrajesh

Open Billing Doc value table in Credit management

Similar Messages

Maybe you are looking for