Credit limit check and Payment terms

HI,
Is it possibile to enforce new credit limit check when the payment term is changed? Let's say that customer has "Immediate payment", and after few days wants to change payment term for "90 days payment term". In such case system should check new credit limit check on a sales order (va02). Could you tell me how to do that?
Best regards,
MK

Thanks, You were right. It runs well for the sales order with out delivery. After I create delivery in reference to this sales order and change payment terms in sales order there is no new credit control check.
Is there a possibility to run credit control check after a delivery is created?

Similar Messages

  • How to inactive "Credit Limit" field under "Payment Term" tab of BP Master

    Hi,
    Can anyone tell how to inactive "Credit Limit" field under "Payment Term" tab of BP Master Data in BP module?   I'd prefer to revise SAP SP (store procedure)...
    Thanks in advance

    Hi Michelle,
    You could use the sample codes available while installing the SDK setup.
    like in this path C:\Program Files\SAP\SAP Business One SDK\Samples\COM UI\VB.NET
    Add this code under SBO_Application_ItemEvent which will disable the field.
            If (pVal.FormType = 134 And pVal.EventType = SAPbouiCOM.BoEventTypes.et_FORM_LOAD And pVal.Before_Action = False) Then
                Dim oforms As SAPbouiCOM.Form
                Dim oitems As SAPbouiCOM.Item
                oforms = SBO_Application.Forms.GetFormByTypeAndCount(pVal.FormType, pVal.FormTypeCount)
                oitems = oforms.Items.Item("85")
                oitems.Enabled = False
            End If
    Note that the above is only a sample code and you have to track other events as well to disable this field like in add mode, browsing records
    If you need help with SDK, post it in SDK forum.
    Regards,
    Vijay kumar
    SAP Business One Forums Team

  • Customer credit limit check and error message in delivery

    Hi,
      I have a required to block the creation of delivery , if customer outstanding amount is there more than 150 days  after the payment due,  system should give the error message for this and should not allow to create the delivery  till that open item get cleared,  i try with OVA8   with risk category  002  and document type category  02 and 03  by selecting the oldest open item check box  setting reaction as D  status block Days oldestItem : 150  but with this system is still allowing to create the delivery,  how to blcok this  if i do any changes in the SO  then first time it set the static credit limit block  but once it is release with VKM3  then it is alllowing to create the delivery, so how to block the delivery creaton.
    Is there any user exit in delivery creation VL01N,  to check the cusromer open items and block.
    regards,
    zafar
    Edited by: zafar karnalkar on Sep 5, 2011 7:49 AM

    Hi
    To control the changes in the SO try to control a VOFM subroutine and set it the field 'No credit check' in OVA8. See the VOFM 002 (as a template) but you need the changes over the SO, and this you have in the 001. In delivery I don't know anything (for instance, see SAP Note 415716 - User exits in delivery processing). My idea is use the subroutine 001 to lock the SO, and with the field VGBEL and VGPOS in LIPS, search the status of credit for this SO when you create the delivery, and then, use the proposed userexits in the cited note.
    I hope this helps you
    Regards
    Eduardo

  • Does Simple Credit Limit Check Include Checking for Open Orders

    Hi all,
    I have this issue here where I have configured the system to use simple credit limit check with error message. I did not use the standard/common automatic credit limit check since user insist on a pop-up warning and that the order could not be saved. But, I realized that it does not take open orders into account too although I have set the risk categories. Is it true and what solution is there for this issue then.
    Thank you for all your help in inputs.
    Regards,
    Yvonne

    Hi,
    Please follow the below configuration settings for Simple credit check process.
    Simple credit check: In simple credit check the system compares the credit exposure with payers credit limit. The
    credit exposure results from the total of the net document value and the value of the open items.
    We can set the following system responses at when the credit limit has been reached.
    A u2013Warning message
    B u2013 Error message
    C u2013 Delivery block
    Specify in VOV8  Credit limit [C]
    Configuration settings:
    Sales documents types u2013 Credit limit check: Transaction code: OVAK
    Path:
     IMG
     Sales and Distribution
     Basic functions
     Credit management/Risk management
     Simple credit limit check
     Choose sales document type OR
     Specify value
    [ ] = No credit limit check
    [A] = Run simple credit limit check and warning message
    <b> = Run simple credit limit check and error message
    [C] = Run simple credit limit check and delivery block
     Save and Exit
    Define credit control area: Transaction code: OB45
    Credit control area is an organizational unit that specifies and checks the credit limit for customers. A credit control
    area can include one or more company codes. It means we can assign one credit control area to number of company
    codes.
    NOTE: Within credit control area the credit limit must be specified in the same currency.
    Path:
     IMG
     Enterprise structure
     Definition
     Financial accounting
     Define credit control area
     Go to new entries
    (OR)
     Choose existing credit control area
     Select it and click on copy icon
     Rename it and click on details icon
    Specify currency [INR]
    257
    Data for updating SD fields
    Update [000012]: Open order value on time axis, delivery and billing document value. This field value controls
    when the values are open sales orders, deliveries, billing documents are updated in LIS. We can specify the
    following update groups for updating credit related statistics.
     Update group 000012:
    Sales order: Increase open order value from delivery relevant schedule lines.
    Delivery: Reduces open order value from delivery relevant schedule lines.
    Increases open delivery value
    Billing document: Reduces the open delivery value, increases open billing document value.
    Financial accounting document: Reduces open billing document value
    Increases open items.
     Update group 000015:
    Delivery: Increases open delivery value.
    Increases open billing document value.
    Financial accounting document: Reduces open billing document value
    Increases open items.
     Update group 000018:
    Sales order: Increases open delivery value
    Billing document: Reduces open delivery value.
    Increases open billing document value.
    Financial accounting document: Reduces open billing document value.
    Increases open items.
    Fiscal year variant [K4]: It indicates specific fiscal year variant for particular credit control area. The fiscal year
    variant is essential when a credit control area covers multiple company codes whose fiscal years are different. Then
    the values of the open orders are updated by posting period.
    Specify risk category [001]: 001 = High risk
    002 = Medium risk
    003 = Low risk
    This risk category entered in the related control area of the customeru2019s credit master record, which is automatically
    created when a customer is created in a company code.
    The credit master record is automatically maintained when at least one of the below fields is maintained for the
    corresponding control area.
    (A) Risk category
    (B) Credit representative group
    (C) Credit limit
    Credit limit: The credit limit that we enter here in the specific credit control area of the customeru2019s credit master
    record. This is automatically created when a customer is created in a company code (in XD01).
    NOTE: This credit limit is not a total credit limit for the control area.
    Representative group [001]: Define credit representative group in IMG.
     All company codes: If we want to tell to the system that, this credit control area is permitted for
    postings in every company code we have defined.
     Save and Exit
    NOTE: After this create Risk categories and Credit representative groups and come back to this step and assign
    these values to our credit control area.
    Risk category and Representative group defined and maintained by FI/CO consultants in IMG.
    258
    Assign company code to credit control area: Transaction code: OB38
    Path:
     IMG
     Enterprise structure
     Assignment
     Financial accounting
     Assign company code to credit control area
     Choose our company code from position button
     Click on assign button on the application tool bar
     Select our credit control area from the list and assign it
     Save and Exit
     Go to FD32 and check whether system created customeru2019s credit master data automatically or not.
    System creates customers credit master data automatically when we (FI/CO) people) configure credit control area in
    IMG.
    So as to perform simple credit check we have to specify customer master payers limit in the credit control area, and
    create customer master in XD01 transaction code.
     Specify reconciliation account number (GL account number)
     Payment history record: Check payment history record control in payment transaction tab. It is the
    control parameter to update the payment details that are made by customers and system will show the
    payment details in the FD32.
     Specify the credit control area in credit control area field in billing document tab.
     Save and Exit
     Go to VA01 and raise the sales order
    Check the system responses in each and every level of sales document processing and check whether the system
    blocked the delivery document (due to the setting in VOV8 of OR in check credit limit field [C] = Blocked for
    delivery).
     To release the delivery go to VKM4 and release the delivery document.

  • Authorization for Credit, Commitment Limit and Payment Terms

    It's very required to have authorization for Credit Limit, Commitment Limit and Payment Terms change. Currently it's very hard to control limits as every user can change these values and omit approval procedure or authorization for Confirm Credit Line Deviation and Confirm Debt Line Deviation.

    Thanks, You were right. It runs well for the sales order with out delivery. After I create delivery in reference to this sales order and change payment terms in sales order there is no new credit control check.
    Is there a possibility to run credit control check after a delivery is created?

  • Sales Order Free item and Credit Limit Checking

    Hiii Guys,
    need your help,
    How to release Sales Order free item when credit limit exceeded ?
    Here some info :
    Customer : ABC
    Credit limit : 50,000.00
    Credit Exposure : 52,000.00
    Risk Category : 003 High Risk
    My user want to create sales order for free item for customer ABC, the customer abc credit limit already exceeded .and the item in sales order not contain any value, it should past the sales order creation. how to allow Free item past the credit limit checking ?

    To reslove this issue,
    I. you can create a new sales order type. for which you make the credit control de-active.
    2. If you can't create a new order type and this cotrol should happen at item category level.
    then try config at the IMG>Sales & Distribution>Basic function>creditmanagement>credit management/riskmanagement setting>Determine Active Receivables Per Item Category.
    Regards/Rakesh Jindal

  • Credit Limit Check - Exclude Specific Documents / Credits from Exposure

    Hi,
    I would like to know if it's possible to exclude specific document types (credits) from the credit exposure calculation used during credit limit checks.
    The ideia is to exclude "DG" credits in customer GL that are related to Trade Deal/Agreements to avoid over-exposure.
    Let me explain:
    Currently, our credit management is configured to "Static" + "Open Items" for all credit groups in the CCA. Therefore, SAP calculates the credit exposure as:
              CE = OPEN ORDERS (S066) + OPEN DELIVERIES (S067) + OPEN BILLING (S067) + OPEN ITEMS (BSID)
    Regarding "Open Items", I understand that SAP calculates the net value between all debits (receivables) and credits (returns, overpayments, etc...) already posted and not cleared in the Customer GL account. This rationale is correct since the credits are due to the customers and should be deducted from their exposure (i.e. "you may not pay them if you don't receive").
    However, in our case, we also pay trade deals contracts (i.e. trade incentives and trade marketing investments) directly to costumers and apart from sales orders or credit memos. The flow is the following: (1) contracts are managed on a satelite system and interfaced to SAP; (2) contracts are created in the costumer GL as a credit (doc. type "DG"); (3) credits are sent to accounts payable for payment via F110.
    Problem is that, contract credits volume is significant and are impacting customers credit exposure and limit check, resulting in greater exposure than allowed. That is, orders are being released while contract credits are open in the customer GL up to the max exposure, but when contracts are paid the exposure goes above the limit. For example:
    Day 1:
              Costumer Credit Limit: 100
              Sales Balance: 30
              Open Itens: 50 (receivables: 70 / contracts: -20)
              Credit Exposure: 80/100
    Day 2:
              Costumer Credit Limit: 100
              Sales Balance: 50
              Open Itens: 50 (receivables: 70 / contracts: -20)
              Credit Exposure: 100/100 (no additional orders are released)
    Day 3:
              Costumer Credit Limit: 100
              Sales Balance: 50
              Open Itens: 70 (receivables: 70 / contracts: 0 - contracts are paid on day 3)
              Credit Exposure: 120/100 (exposure is above customer limit since contracts that were being deducted were paid)
    Any ideas or thoughts? Is something wrong in the explanation above? Should contracts credits be treated through special GL?
    Many thanks!

    Hello Julie,
    the 2nd, System behavior (how do you interact the credit limit check (yes/no question) via DI?)
    Workaround:
    Before you issue the Document, you may do a manual check: BP balance againt Credit Limit, and make deceision.
    Regards
    János

  • Draft invoice and payment terms

    A customer has 30 day credit terms (for example), but when creating a DRAFT invoice the docuemnt date, posting date and due date defaults to todays date. 
    When converting the draft invoice to an INVOICE, the due date remains as today - not the payment terms of 30 days from posting date.
    How can the payment terms be activated to ensure correct aging of the invoice?
    2005A PL23

    The 'due date' appears as soon as the Customer is selected in Invoice not while saving as 'Draft'. The due date is based on the 'Payment Terms' set in the 'BP Master Data'.
    I request you to check if the 'Due Date' is set properly before saving the document as draft. It should be as per the payment Terms of the BP. If not check the Payment Terms of the BP.
    I have checked this feature with SAP B1 2005B PL: 38 and works properly.

  • Document cant be billed due to credit limit check

    Hi SAP gurus,
    I have a sales order i am going to do billing(order related) its showing error"document cant be billed due to credit limit check".
    I have checked in FD32 customer credit limit 200,000RM and  recievables140,991.4 and sales value 21,980.
    customer used only 81% of credit only.i have checked in open orders(9032.80), open deliveries and open billing doc.but customer can use still 28,086. But system not allowing to do billing for 950RM.
    Is there any other areas i need to check? Experts give me some inputs.
    Thanks and Regards,
    Nooka

    Hi
    KIndly check in the sales order  that you have maintain the  payment guarentee procedure  because of this the system is not allowing to do the invoicing
    PATH: VA02sales order no-Go toItembilling document---payment guarentee procedure
    so kindly check that and remove or assign the financial document to that for processing  the billing
    By doing above the issue will be resolved,kindly check and confirm.
    if you have any further clarifications let me know
    REgards
    Damu

  • Static Credit Limit Check for Sales Orders - Net Value vs Credit Value

    We are testing order credit check and we have run into a problem with the Static Credit Limit Check.  The Static Credit Limit Check is set to use both Order and Delivery Values.  SAP uses the values in S066 and S067 to determine what values it uses to check against the credit limit.  Standard SAP uses the confirmed quantity times the credit price to get the order values - this is the credit value. 
    So the problem is, once an order is released it is set up so it does not go back on credit hold, so anything which is not confirmed (but could be) it a potential credit value which is unaccounted for in the credit exposure and the customer can go over the credit limit.
    Additionally, we run AFS and have items which are rejected with a J0 rejection code (unconfirmed) which have the potential of being confirmed and shipped and we want to include these items in the value of the order which is being checked against the credit limit (along with the deliveries, invoices and receivables).
    Here is a quick example.
    Customer has a credit limit of $100 (no deliveries, invoices or receivables - to keep it simple)
    Order 1 is placed with a credit value of $50.00 but a potential value of $100 (the other half is J0) - this passes the credit check since $50.00 is less than the limit.
    Order 2 is placed for $50.00 and has a credit value of $50.  This also gets approved.
    At this point, the credit limit used is 100% (based on standard SAP)
    Then Order1 backorder is confirmed and the new credit value is now $100.  This order now puts the customer over their limit and if the order had been released would not go back on credit hold and therefore the customer is not over their credit limit by 50%.
    What I want is for Order1 to be credit checked for the $100 not the $50 so the exposure is correct.
    Does anyone have any suggestions as to how we could use the Net Value of the order to perform the static credit check?  And any thoughts on how to determine the correct credit exposure (open order value plus items which are J0, plus deliveries, plus invoices, plus receivables)?
    I am thinking about a Z table to track the adjusted values on the orders and then use one of the customer checks to do a static credit check with the adjusted value.  And for the exposure, use the adjusted value to recalculate the values in F.35 to show a more accurate view of the credit exposure.
    Does anyone have an easier way to do this?  Any advice is appreciated.
    Thanks,
    Suzanne

    Hi Suzzane,
    In the scenario that you have provided, in the first order items worth 50$ are rejected. Hence standard SAP will not take this into account as this item is rejected.Two solutions can be provided here:
    1) The line item can have a delivery block instead of  a reason for rejection.This way the 50$ will get accounted.However, if this is against customer norms as this will appear in the order acknowledgment, this cannot be used.
    2) User exit can be used where a credit check can be triggered once the document value changes, even though the document has a released status.
    Hope this helps.
    Thanks,
    Vinu

  • Credit limit check cause the item schedule line confirmed qty empty

    Hi,
    I have an SO that is under credit limit check, the problem is, after releasing it via VKM3, the confirmed qty at item schedule line is not taking the qty as of stock at the time. The SO qty is 100 Pcs, but there's still stock of 80 Pcs. I will then need to split the schedule line to 2 lines --> 1st line with order qty 80 Pcs, and 2nd line 20 Pcs. Then only the confirmed qty appear for the 80Pcs.
    For usual SO that is without credit checking, the confirmed qty will immediately shown as in 1 schedule line. Does anyone know why is this happening and can we amend this problem?
    Thanks.

    Hi
    If an order is subject to credit check once you save the order the confirmed quantities becomes 0 because if the settings done in t code OVB8 Number of the routine used for copying is set as 101and System FORM routine number is set as 1 (and this is the standard settings)
    This is kept like this in standard so that if a material stock is say 10 units and order from customer X has come for 10 units and that order is blocked on crediit limit so that when the next order from customer Y has come for another 5 units and this customer Y has a better credit limit and this order is not blocked on Credit limit check then she should not suffer for stocks
    A genuine customer should not be deprived of stocks
    For you between the order registered and released thro VKM3 another order has come from another customer for 20 units and hence the 100 units has become 80 now and balance 20 is confirmed for a future date thro forward scheduling
    In T code OVB8 you can do the customizations for this scenario according to the business requirement
    Regards
    Raja

  • Auto update of Valid to and Payment Terms field

    Hi,
    I have a scenario, where based on the Net value of the document, Valid To date of the Quotation and Payment Terms should auto populate.
    Ex: If Net value is above 5lks, then payment terms should be 100% with in 20 days from current day and valid to date is also 20 days from now. Like wise, if Net value is below 5lks, then payment terms and valid to date should be 10 days.
    Thanks for response in advance.
    Vam

    Hi,
    Please check if the following user exits help.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document" .
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    Regards,
    P Gomatheeswaran

  • Invoice and payment terms ...I don't understand . please suggest me

    I have given problem below. In FI, we normally configure in fbzp tocode...what is the outpur type here ? for the below which program I need to check ? Invoice and payment terms ...given
    Pls take a look at this invoice and let me know why it is changing the payment term.
    User has below problem :
    SAP FI Output type SAP19
    Payment Terms print "Payment Due Immediately" rather than actual terms.
    i.e. invoice 208615 - payment terms US02 - should print "Net 60" however prints "Payment Due Immediately".
    Is this hard coded and if so, can it be corrected and when?
    Please advise.
    Thanks,

    Using fb12, I am selecting customer invoice
    then in new popup I am giving  invoice number and fiscal year.  then it is giving message on status bar as 'customer invoice requested'.
    Then i am going to F.61 and executing by giving  in pop up -->correpspondence, company code, document number and  fiscal year.
    Then a spool is getting created and I am able to see the form output in /nsp01 where the error is occuring .
    Could you please suggest me hwo to find out the form name and driver program name.
    THANKS IN ADVANCE.
    Edited by: Sam  Kumar on Sep 3, 2008 7:30 PM

  • FSCM-CR - Credit limit checking

    Hi,
    When activating FSCM-CR, will the FI-AR credit limit checking be automatically inactive when posting open items (or creating sales orders in SD), or is it required to remove any costumizing settings in FI-AR in order to have only FSCM-CR triggering any verification events and messages?
    I am aware that in Business Partner master we need to set the Check Rule, but I would like to confirm if, apart from that, the transition of credit checking control among the modules is seamless.
    Thanks and regards,
    Gonçalo

    Please review within SPRO the FSCM Credit Checking configuration options.
    Define Checking Rules
    Define Blocking Reasons
    Define Field Groups for Parameters
    Define Info Categories
    Plus also look at Credit exposure update
    Define Liability Categories

  • Reason code and payment terms

    Hi Gurus,
    Is there any link between reason codes and payment terms ?
    When I am posting a document or creating any residual and assign a reason code, it automatically assign a payment term and which i am unable to change.
    any advice, suggestion would be appreciated.
    Thanks.

    Hi,
    There is no direct link between Reason Code and Payment terms.
    Reason code is the key actually specify the reason for payment difference it can be any reason like DISPUTE - TAX, DISPUTE - IN PRICE, DISPUTE EX - QTY and so on and those we can define.
    Where as Payment Term are used to define
    1. Base line date for due date calculation
    2. Cash discount periods
    3. Cash discount percentage rated
    And the Payment Term which is coming by default while posting the document is the same one which has been defined in your master data for that customer. So I would suggest you check the master for that customer and surely you will find the same payment term updated there as well.
    But it not means that you can not changed Payment term while creating or posting document, you change it and it will supersede you master data payment term.
    Hope this will answer your query.
    Regards,
    Abhinav Sharma

Maybe you are looking for