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

Similar Messages

User Exit in Credit Managment - Urgent

Dear All,
One of our customers want to use option of Oldest of open Items overdue in the Automatic credit check.
WIth the only difference that he does not want the field " Days oldestItem ( Table Name V_T691F / Field Name OITOL)" within IMG. He wants that field to be available in the customer master.
In order to achieve this we have thought of following solution --
1. Add new field in the customer master using screen exit in " General Data / Company Code" Tab for capturing " Days oldestItem ( Table Name V_T691F / Field Name OITOL)"
2. Use user exit LVKMPFZ1. Build following logic into the same.
Refer table for Open Line Item (Table BSID)
Due date = Document Date (Field BLDAT) + Days 1 (Field ZBD1T)
If, Due date + Field in Customer Master added through screen exit (in no. of days) < Today, Credit Check will be active & depending on the setting in Automatic Credit Check, we can get either warning message or error
Please check if above logic is OK. If you wish to suggest any changes, you are most welcome to do so. Points will be rewarded for any valuable suggestion. But please hurry up. Unfortunately we do not have much time.
Regards
Nikhil

Hi,
TRY THIS PROGRAM MAY BE HELP U,
REPORT z_find_userexit NO STANDARD PAGE HEADING.
*& Enter the transaction code that you want to search through in order
*& to find which Standard SAP User Exits exists.
*& Tables
TABLES : tstc,     "SAP Transaction Codes
         tadir,    "Directory of Repository Objects
         modsapt, "SAP Enhancements - Short Texts
         modact,   "Modifications
         trdir,    "System table TRDIR
         tfdir,    "Function Module
         enlfdir, "Additional Attributes for Function Modules
         tstct.    "Transaction Code Texts
*& Variables
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
*& Selection Screen Parameters
SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN END OF BLOCK a01.
*& Start of main program
START-OF-SELECTION.
Validate Transaction Code
SELECT SINGLE * FROM tstc
    WHERE tcode EQ p_tcode.
Find Repository Objects for transaction code
IF sy-subrc EQ 0.
    SELECT SINGLE * FROM tadir
       WHERE pgmid    = 'R3TR'
         AND object   = 'PROG'
         AND obj_name = tstc-pgmna.
    MOVE : tadir-devclass TO v_devclass.
    IF sy-subrc NE 0.
      SELECT SINGLE * FROM trdir
         WHERE name = tstc-pgmna.
      IF trdir-subc EQ 'F'.
        SELECT SINGLE * FROM tfdir
          WHERE pname = tstc-pgmna.
        SELECT SINGLE * FROM enlfdir
          WHERE funcname = tfdir-funcname.
        SELECT SINGLE * FROM tadir
          WHERE pgmid    = 'R3TR'
            AND object   = 'FUGR'
            AND obj_name = enlfdir-area.
        MOVE : tadir-devclass TO v_devclass.
      ENDIF.
    ENDIF.
Find SAP Modifactions
    SELECT * FROM tadir
      INTO TABLE jtab
      WHERE pgmid    = 'R3TR'
        AND object   = 'SMOD'
        AND devclass = v_devclass.
    SELECT SINGLE * FROM tstct
      WHERE sprsl EQ sy-langu
        AND tcode EQ p_tcode.
    FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
    WRITE:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    SKIP.
    IF NOT jtab[] IS INITIAL.
      WRITE:/(95) sy-uline.
      FORMAT COLOR COL_HEADING INTENSIFIED ON.
      WRITE:/1 sy-vline,
      2 'Exit Name',
      21 sy-vline ,
      22 'Description',
      95 sy-vline.
      WRITE:/(95) sy-uline.
      LOOP AT jtab.
        SELECT SINGLE * FROM modsapt
        WHERE sprsl = sy-langu AND
        name = jtab-obj_name.
        FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
        WRITE:/1 sy-vline,
        2 jtab-obj_name HOTSPOT ON,
        21 sy-vline ,
        22 modsapt-modtext,
        95 sy-vline.
      ENDLOOP.
      WRITE:/(95) sy-uline.
      DESCRIBE TABLE jtab.
      SKIP.
      FORMAT COLOR COL_TOTAL INTENSIFIED ON.
      WRITE:/ 'No of Exits:' , sy-tfill.
    ELSE.
      FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
      WRITE:/(95) 'No User Exit exists'.
    ENDIF.
ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'Transaction Code Does Not Exist'.
ENDIF.
Take the user to SMOD for the Exit that was selected.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ 'JTAB'.
SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
Thanksmate,
Reward if helpful,
Phani

Risk category field is missing in dso for 0fiar_o09 credit management.

Hi BI Experts,
I am using the standard extractor for the credit management dso 0fiar_o09. The field for risk category originates from our R3 system in table knkk-ctplc. It displays correctly in the psa. The transformation rsds 0fi_ar_9 maps it to 0risk_categ. It appears as an infoObject in the infoSource. The trcs transformation maps the rule also.
However, when I try to display the data in the dso, the risk category field does not display at all.
Please help with any possible suggestions to display the missing field.
Kind regards,
Cheryl Adamonis

I resolved this issue by removing the check in the 'attribute only' selection on the general tab of the infoObject.

Letter of Credit functionality and Credit Management

Hi,
we want to use Letter of Credit functionality for exports.
Currently, we have an ERP system that contains the sales data. In a separate system we have the credit management functionality (Financial Supply Chain Mgt - FSCM).
When order is created, the credit limit is checked in the FSCM system (via PI messages).
Now, we want to link some of the Sales orders with Letter of Credit. I believe, this is standard functionality in GTS.
So when Sales Order is created a LOC should be connected to this.
Can the GTS be connected also to FSCM credit management, so credit limit is not affected?
Example:
Sales Order value: 1 Mio USD
10% down-payment > this would be in the credit exposure visible (net exposure).
90 % covered through LOC > credit exposure should showing this, or it shows order value and in a negative figure this amount deducted so no effect on exposure.
Down-payment has no relation to LOC. When money is received for this the net exposure of the sales order is 0.
partial invoice: 0.4 Mio USD > it should be possible to link this invoice to the LOC. The posting FI document should have some LOC information, so when payment comes in the amount in LOC is reduced as well as in credit management this open.
Final invoice 0.5 USD: as above, all values go out from exposure if there are any.
A second case would be guarantees, where there is no reduction of values. This would stay same.
Anyone who can advise a solution here?
Thanks + Regards
Hein

Letter Of Credit can be used as a standard solution of SAP GTS with ERP solution. Yes you can connect both SAP & no SAP systems with GTS, but plugins, PI etc needs to be built in. But it would not be real time like RFC works. There are some standard available which needs to be hard coded to meet specific requirements.
Connecting LOC to Sales Order, invoice etc, is manual, based on business specific parameters and it comes standard with SAP GTS. Maintaining Values & Quantity of LOC based on actual LOC from bank is also possible. The depreciation of values & quantities is also standard with in LOC in GTS.
You can also setup various communication methods for LOC.
I think when Invoice is raised and payment is received the LOC should be closed in the system. There can also be other scenarios where in system determines LOC based on predefined logics for determination strategy put in to the GTS system.
Cheers,
Abir

Open Sales Order Values in Credit Managment

Hi,
1. I want to include the open sales orders that were created before implementing the functionality of Credit Managment. How to check the credit limits for that sales orders.
Fro Example. If i want do the credit checks for 1000 open sales orders.
2. How to reset the customer credit limit in FD32. I tried using the t.code f.28, but it will not be reset to zero(0).
Thank you,
Ravi

Hello Ravi,
You can try this: in table VBAK, you might have the date when this a particular order was created( ERDAT or sometihng like that..). You'll have to join table VBAK/VBAP/VBRK(billing table)/VBFA and the logic should be that the program should pick up all the orders created before 1 yr and should also check that the items are not rejected, and the delivery not yet created.
Check the following fields:
VBAK-ERDAT, VBAP-ERDAT, VBAP-ABGRU, VBAP-AEDAT.
Regards,
Raghu.

Open Delivery value update error in credit management

Hi
We have credit management active at delivery level. The value of open deliveries is not getting updated correctly for items with material substitution (material determination). For all other items, its getting updated correctly.
E.g Let say the credit limit set in FD32 is 10000 and the credit limit used % is 98 and the credit exposure value is 9800.
Now when I create an order with qty 10 for mat A, it creates a sub item B due to material determination and the value of the item is Rs.1200. In our system, the sub item with TAPS item category is relevant for pricing.
Then I create a delivery in VL01N and save it.
Now if i check in FD33, the credit limit used should be 101% and the credit exposure value should be 11000, but its not updating the open delivery value correctly. Its not considering the value of the new delivery.
However, If I add a normal item (TAN) in the same sales order and create a delivery for that item and save it, its updating the credit exposure based on the value of the normal item in the delivery correctly.
How to make the system update the open delivery values correctly by taking the items with material determination also into account.??
Please advise if any specific settings need to be done.
Regards
Madhu

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

Outbound IDOC for Credit Management

HI All,
We need to send the Credit management data from SAP to other system. For that we require Standard IDOC, could you please suggest the standard IDOC available for the same and how to configure it. Please let me know if we have any standard program which generates the IDOC for my requirement.
Regards,
Phanindra

Thanks for the Input, could you please let me know how we trigger this IDOC. Is it through configuration or any standard program which will generate idocs.

Customer complaint and credit management

Hi,
we have the following business case, credit management activated:
1. a customer has a complain about a delivery (e.g. poor quality/wrong material)
2. the corresponding invoice is shown as an open item in FBL5N
3. a credit note request is created for the sales order, but it can take weeks until it gets released. In the meantime the customer becomes overdue.
4. now the following happens: when the customer wants to place a new order he will be blocked by the credit management.
We first have to release him e.g. via VKM4. The same with deliveries.
Is there a possibility to mark the invoice in question as not relevant for the credit management?
My first idea was to change the credit note requests as relevant for the credit management (VOV8), but unfortunately those requests are not visible in FBL5N. Thus we would loose the overview of invoices in question.
Thanks for your answers...
Cheers,
Marc

hello, PP.
i don't have an answer yet. actually, i will add to your question.
a credit memo request is supposed to be not relevant for delivery. so why is this updating open delivery value? maybe it's SAP standard? maybe credit group 03 (delivery docs) was assigned to the credit memo request doc type? if so, why assign credit management to credit memo requests anyway?
regards.

Credit Management (Open Items and Oldest Open Items)

I have 2 questions.
1)What is the difference between Open Items check and Oldest open items
2) I want to activate a Credit management check which should work in way that the Order will be blocked on the basis of Payment term check
Let say if I am using the Payment terms 0001 i.e Payment immediately due net .now what I want is that if I post the first invoice system as configured will check only the Credit check againt the credit Limit but when i post the 2nd invoice on the same day and the first invoice is not cleared system should give a warning message for it .
Currenlty as i Configured it working but not for the same day option its give a warning on the 2nd day's invoice
SO Need the help of Experts.
Thanks in advance

Hi,
Open items check means it will consider all the open items when it is doing credit check. Here it adds all the open items amount and do the credit check..
Oldest open item means it will consider only the oldest open item and based on tht i will do credit check..Here i will check the oldest open item value and its date then do the credit check..
Coming to payment terms check, system is responding correctly.. because payment terms are immed due net. tht means still time is there in the same day. that is the reason it is not blocking the second document.
once move to 2nd day then it means first doc is not cleared tht is the reason it is blocking the 2 nd doc on 2nd doc..
Hope u have understand..
Regards
Sankar

Payment History In Credit management

Hi all,
How to activate the Payment History in Credit Management(FD32).
Regards
Talluri

Hi Talluri
If you want to activate payment history in FD32 then in XD02->Company code data tab->payment transactions tab check the box payment history and save it
Now when you do billing and forward it to FI for the blocked documents then the payment history will be updated
Regards
Srinath

Credit Management - Maximum time overdue limit for open item

Dear all,
I've this scenario to configure for automatic credit control. A customer is billed on Jan 22nd '10 and now the account receiveable shows an open item. This customer is allowed 52 calendar days to make payment for this invoice, hence no credit block yet. As such, the customer can still make orders.
In my existing configuration, I've already enable "static" credit check on "open orders" and "open deliveries". The static check is to check against the customer's credit limit.
So, if I were to add in the earlier mentioned overdue open items check, is it sufficient to just maintain the field "Days oldestItem" with "52" within the automatic credit control screen?
Thanks.
Steven

Hi
The sytstem will shows oldest open items depending on the payment terms from the invoice date.
Once it crosses the days of payment then it will show in oldest open items
if you want to extend some more days for that then you need to maintain the days in "Days oldestitem" the automatic credit control area
Prerequisites for credit management to work in Sales and Distribution:
1.Assign credit control area to company code
2.Maintain the credit limit in FD32 with details of risk category and the credit limit value
3.Do the settings in OVA8 -automatic credit control area with combination of Credit control area/Risk category /credit group.
4.Assign the credit groups to the sales and delivery document types.
5.Maintain the Subtotal 'A' in the pricing procedure against which value the sytem should check the credit limit.
If you have any further clarifications on above let me know
Regards
Damu

Credit management

We have open sale order for a customer after which the credit management was activated. In FD 32 the credit limit was set.
The risk category used is 006.
We have used static check. We have ticked on open orders and open items.
We want the system to prompt at the sale order level if we are trying to change the quantity.
After maintaining the master when we create order and if it exceeds the limit we are getting the error message that credit limit exceed by -
value.
For orders that are raised before fd32, we are not getting the error message.
Could anyone please guide

Hi Pooja
In OVA8 , for static check change the Reaction box to error and then check , but generally the open orders, open deliveries work for dynamic credit check and not for static credit check
Regards
Srinath

Credit Management requirement for cash business

Hi Gurus,
Actually my client business is a cash business, there is no credit concept for the customers.
My requirement is when i create a sales order, system should check the credit balance of the customer(Business receives the payment through cheque and entry is made in f.28 transaction) and should compare with the current document value and if it exceeds, then system should through the error.
And if any open sale orders exists for this customer, system should even consider those values while credit check is happening.
And the exceptions for this requirement is
1.Credit check option should be there only for specific case of customers i,e based on account group of customers.
2.There are very few customers(around 5) where they give credit.
Pls guide me, early resposes woould be highly appreaciable.
Thanks in advance
Regards
Mahendar.

hello, friend.
you can consider using the payment guarantee scenario in credit management. the customer advance payment could be treated sort of as a financial document or payment card.
as for the selective application of credit controls based on customer group, i believe you do this be configuring risk categories and assigning them to the appropriate credit account master data.
regards.
Edited by: jonathan y on Apr 24, 2009 12:57 PM

Credit Management: How to include back orders value in credit exposure?

Hello,
We have to have credit management implemented for some sales order types.
Credit exposure is working fine with normal sales orders.
But credit exposure is not taking into consideration the value of backorders which are present prior to credit management was implemented (with horizon period of 2 months).
Please let me know how we can include the value of back orders in credit exposure?
Thanks in advance for your answer.
Mallik

hi
goto OVAD
assign delivery type with dly credit group 02, GI credit group 03. s ave
goto OVAk
assing order type with check credit D credit group 01
goto OVA8 double click on relevant credit control
field Oldest open item select it, then Days oldest item assign value
regards
[email protected]

Credit management and credit exposure

Hi experts,
Pls anybody clarify my doubt in Credit management.
I activated the credit control areas update as 000015(Open delivery and billing document value).And activated dynamic credit management "Automatic credit control".Now i explain with some example how it working. Fixed credit limit for customer A Rs.30,000/-, Receivables amount 22,000/-. Now if create a sales order for value >8000 i m not getting the credit lock waring messages.
(I.e) i am creating one sales Order for value Rs.9,000/-.(So credit limit crossed and not getting error msg or waring messages)
After that creating another sales order for same customer i am getting Warning msg like"Credit limit crossed_____amount".
So finally, CCR Rs.30,000/, Recei Rs.22,000/- but i can able to make even Sales Order value for Rs One lakh. I want here to block sales order should not be create.
Thanks in advance.
SR

When a sales order is created , only the confirmed quantity is taken for pending sales value even if sale order qty is more
Check OVA8 setting , open deliveries and open orders should be selected
You can set reaction status as warning or error.
Pricing procedure - Subtotal should be A . This will update structure s066
The above condition will work only for order creation . For sales order ammendment you have do the same setting for credit group 02.
If Dynamic credit check works with credit Horizon date . It is better to have static credit check.
Check MC30 after creating sales order whether structure s066 updated for the order.
check and confirm
Senthils

Credit management urgent

Similar Messages

Maybe you are looking for