Default for baseline date  in Payment terms

Hi All,
Can anyone please explain me the options in OBB8 default for base line date 1. No Default 2. Posting Date 3. Document date 4. Entry Date while creating payment terms with examples.
It's very very very Urgent!!!!!!!!!!!!
Thanks in advance.
Boppana

Hi,
The following are the examples:
1. No default:  Self explanatory, hence system does not consider any default value to start for calculation of due date. The baseline date has to be entered manually at the time of Invoice creation.
2. Posting Date: The date of entry in the system 31-Jul-11 (after two days).
3. Document Date: The date on the physical Invoice which we key in at the time of Invoice entry. Say for example 25-Jul-11.
4. Entry Date: This is the system date i.e. todayu2019s date 29-Jul-11. This date is internal in the system and not controllable or editable.
To summarize, for 2, 3 & 4 the system defaults the baseline date (changeable) at the time of Invoice entry but, for 1 system does not default any baseline date.
Regards,
Kiron Kumar T.

Similar Messages

  • Baseline  date in payment terms

    Hi experts,
    There're 4 kinds of baseline dates in payment terms: no default, posting date, document date & entry date. I have gone through the relevant thread & tested in the system.
    However, I found no differences among them, i.e. no matter which baseline date is selected, billing date automatically captures actual delivery date from delivery when creating invoice.
    Why? Is there something wrong?
    Plz help. Many thanks.

    As I already mention, baseline date for payment is the date from which the terms of payment apply.
    So,
    - No default for the base date, this Indicates that no default value is required for the baseline date for payment. You then have to enter the base date manually during document entry.
    - Propose posting date, this Indicates that the posting date is to be proposed in the base date field during document entry.
    - Propose document date, this indicates that the document date is to be proposed in the base date field during document entry.
    - Propose entry date, this indicates that the entry date is to be proposed in the field Base date during document entry.
    Where,
    Base Date is the date to be entered in the header of a document.
    Posting Date is the date on which a business transaction is transferred into one or more accounting ledgers on document entry.
    Document Date is the date on which the original document (such as vendor invoice) was created.
    For understanding refer following links:
    [Terms of Payment|http://help.sap.com/saphelp_40b/helpdata/en/96/8b3fc643ce11d189ee0000e81ddfac/content.htm]
    [Baseline Date for Payment|http://help.sap.com/saphelp_46c/helpdata/ru/e5/0783804acd11d182b90000e829fbfe/content.htm]
    Hope this can assist you.
    Thanks & Regards
    JP

  • Day Limit, Fixed day/Additinal months & Baseline Date in Payment Terms-OBB8

    Hi Gurus,
    Please put some light on the following:-
    1. What is the relation between Day Limit & Baseline Date.
    2. What is the use or significance of Day Limit as far as Payment Term for Vendor/Customer is concerned?
    Thanks & regards,
    CS

    Hi,
    The day limit is used to process the document for due date determination based on the baseline date (document date, posting date etc. which is specified in payment term) of the documnt.
    For example, if you have defined first payment term P000 with the day limit as 15 and second P000 with day limit 31, then the documents having baseline date 15th or before will attract first payment term for due date calculation and documents with baseline date after 15 will attract second payment term for due date calculation.
    I hope the things are clear to you now.
    Regards,
    Gaurav

  • BaseLine date different from Terms Of Payment Date

    Hi,
    My client posted 3 documents dated 23.12.2009,17.12.2009,14.12.2009  respectively. The terms of payment has been set to accept document date as default for the baseline date. This means that the baseline dates for the  documents should be same as 23.12.2009,17.12.2009,14.12.2009  respectively. However, the system has set 31.12.2009 as baseline dates for all MIRO documents. I have already checked Terms Of Payment  ,Vendor Master and the posted documents.
    Can anyone please provide any clues to this problem?
    Thanks In Advance
    Regards,
    Payal Saxena

    Hi Payal
    Request you to check settings for PT in OBB8
    Also, refer to this thread - Baseline date in payment terms_reply the question for FI experts
    If the problem still persists, you will require a user exit.
    Rgds,
    Zub

  • Baseline date in payment terms_reply the question for FI experts

    Hy guys,
    my problem is this: in payment terms I should want that the baseline date is the date of good receipts instead of the date of invoice receipt and this thing should happen only for a particular society.
    In your opinion is it possible to make this ?
    I have already made the same question to the MM experts but it seems to be more a FI problem and so I also ask you if perhaps there is a user exit that permit to me to make this.
    Thanks in advance for kindness and effort,bye
    Maximilian

    Hello,
    Baseline date is the date from which SAP calculates the due date.
    You can configure the terms of payment in transaction code OBB8. Within terms of payment you are required to maintain baseline date.
    You can select either one of these:
    1) Posting Date: Posting Date of the invoice
    2) Document Date: Document date of the invoice
    3) Entry Date: Nothing but current date of the entry
    4) No Default: In the case of no. default, the system will not propose any base line date, however, the user is forced to enter the base line date.
    In case of 1, 2 and 3 the system proposes the baseline date, however, the user will have the privilege to change at the time of posting.
    You do not have any other options for baseline date, except the these four date options.
    Please let me know if you need further details.
    Thanks,
    Ravi

  • Calendar date & net due date (FI) PAYMENT TERMS - OBB8 Vendor Invoice

    I read many posts on SDN forum about the topic.
    Anyway, I didn't find a simple solution for that.
    My aim is is to calculate a net due date based on working days.
    So, If I've got a 30 days document days payment term  ("Deafult for baseline date" = Document date ; Additional Months = '2'), a Vendor Invoice (document date = 12.05.2011), by standard net due date will be 12.06.2011.
    FROM 12.05.2011 to 12.06.2011 =
    32 CALENDAR  DAYS         
    22 WORKDAYS (32 minus  10 holyday - 2 weekends)
    WORKDAYS PAYMENT TERMS  Within 30 workdays Due net
    Vendor Invoice  document date = 12.05.2011
    plus   30 workdays   =  DUE DATE  22.06.2011  (and not 12.06.2011)
    Can I obtain that with a standard functionality?
    Edited by: Roberto Buono on Jul 1, 2011 2:29 PM

    Hi,
    Sadly this is not available as standard.  As per your need the Net due date should be worked out by using a factory calendar; but what this does is it delinks the direct correlation between the number of days in the payment terms with the difference between the due date and baseline date.  I hope you are aware that Net Due date is not stored but is a variable calculated during run time in reports.
    There are four things you can try:
    1.  The simplest to do is: As the number of weekends are fixed; and if the intention is to give a 30 working day term, then add on the number of weekends and make the payment term effectively for say 40 days.  There will be marginal variations over what you want. Best part here is that config remains standard.
    2. All the receivable reports will use a function module (usually the same one) to calculate the net due date; enhance the FM and make it consider a factory calendar for calculating due date.
    3. Enhance the accounting interface, and in runtime; modify the days that are coming from the payment term; based on a factory calendar, and update the accounting document. This delinks the days mentioned in the payment term and the accounting document and may not be palatable.
    4. Enhance the accounting interface, and in runtime; calculate the due date and update the baseline date with it and make the payment term as "Immediate" yielding the desired due date. Not very elegant.  Alternatively add to the baseline date days equivalent to holidays and weekends and keep the days from payment terms constant and update the accounting document. Better...
    All four options have somes pros and cons.  I do not see any other means of acheiving what you want.  Maybe you could restrict users to a custom receivables/due date/ageing report which delivers what you want and lock the standard reports.
    Cheers..

  • Payment Terms for more than 3 payment terms in OBB8

    Hi Gurus,
    Please advise as to how to create for more than 3 instances, say 4 or 5.  Because standard SAP provides only for 3.  Let me brief you as below :
    -  I created the 5 payment Terms in OBB8. 5001 (clicking as instalment) ; 5002 for 5% - 30 days ; 5003 for 4% for 60 days ; 5004 for 3% for 90 days and 5005 for Net 180 days.
    -  I assigned these 5002 to 5005 to 5001 with say 25% instalment each in OBB9.
    -  Now I assigned this 5001 payment term in the Vendor Master.
    -  Posted new FB60 invoices with say 01st Oct 09 as Document Date with say Rs. 25000/-
    -  Now, I have to make the payment to the Vendor on say 15th November 2009.
    -  So ideally I am eligible for 4% discount on Rs. 25000/- since I am paying after 30 days and before 60 days.
    -  I am posting through F-53 with 15.11.2009 as the document data, and now the system is not calculating discount for the first instalment of 25% instalment and for the next 25% the discount is calculated @ 4% on 25% only.
    -  Now my requirement is to calculate 4% discount in Rs. 25000/-.
    Can any one suggest the required approach.
    Vikas

    Hi,
    Unfortunatelly payment terms in OBB8 is working as designed and the functionality cannot be enhanced. In the standard system you cannot add additional levels in the transaction OBB8.
    Instead you can check the option of using Terms of Payment for Installment Payments (transaction OBB9). Terms of payment for installment payments are made up of individual terms of payment. An individual payment term can be assigned to each installment. When you post an installment payment, the total amount is split up into individual items for each installment and each installment
    is calculated with the relevant payment term. For more information on maintaining terms of payment, refer to the Implementation Guide for Accounts Receivable and Accounts Payable.
    The terms of payment key can determine the following:
    -The valid cash discount rate for an individual payment with a maximum of 3 payment terms (first cash discount period, second cash discount period, and due date for net payment) and also a baseline date for the payment
    -The terms of payment for installment payments.
    You define the following for the terms of payment key for installment payments:
    - Sequential number of the installment
    - Percentage rate for the installment
    - New terms of payment key for the installment item
    The percentage rates you specify must total 100%.
    Example
    Suppose you can create payment term NT30 (30 days net), NT60 (60 days net), NT90 (90 days net).
    Installment terms of payment
    RT01   1   30%   NT30
    RT01   2   30%   NT60
    RT01   3   40%   NT90
    I hope this helps.
    Regards
    Ravinagh Boni

  • Due date and payment terms data

    Hi All,
    Goodday to you all!
    My client is posting one transfer posting.
    He is transferring the normal customer line items to special GL items through FB01.
    Giving the first lime item posting key as 09 and customer number and special gl indicator
    But after going inside only the Dueon field shows as mandatory and there is no field called Payment terms.
    This dueon field is for taking the baseline date for calculating the due date.
    The payment terms field is optional in both the field status (Posting key as well as GL account field status variant)
    But the payment terms field is not showing while entering the transfer document !
    Can anybody advise me on this /
    Thanks in advance
    Shankar

    Hi Shankar,
    > Goto Tcode OBC4
    > select your field status variant
    > DoubleClick on Field status groups
    > Goto General (with text, allocation) - G001 (incase of standard SAP)
    >Goto payment transactions
    > Click on Req Entry or opt. entry in front of payment terms.
    Payment terms will appear in FB01
    Regards
    Saurabh

  • FIX DATE in Payment terms

    HI All,
    we have a requirement where the due date should be a fix date, say 31st march 2007, irrespective of invoice date.
    Please let me know if this can be configured & how?

    Hi
    Sorry Suryu , But here we want specific date along with the month (15/10/2008) as a baseline date , We can obviously set specific day but month for due date depends upon posting date or document date
    For instance today is 11/09/2008 if I want my payment term baseline to be set at 15th of october 08 then I can make a fix day 15th and also additional month 1 so it will make baseline date 15/10/2008 for only those transaction which is been done on september, but again in october it will add another month so it will become 15/11/2008
    Please let me know if you have solution about this

  • Function Module to Calculate Due Date from Payment Terms?

    I'm writing an aged debtor report as the SAP standard one isn't quite right for our requirements.  Is there a function module that will calculate the payment due date if I give it the payment terms and the base line date?
    I did a search in SE37 but couldn't see one which fitted my requirements (I was searching on CALCDUEDATE and variantions of).
    Any suggestions welcome, thanks.
    Gill

    Hi,
    Use the FM FI_TERMS_OF_PAYMENT_PROPOSE for calculating the Payment due date
    call function 'FI_TERMS_OF_PAYMENT_PROPOSE'
      exporting
        i_bldat         = gv_bldat
        i_budat         = gv_budat
        i_cpudt         = sy-datum
        i_zfbdt         = gv_zfbdt
        i_zterm         = gv_terms_paym
        i_bukrs         = gv_comp_code
      importing
        e_zbd1t         = gv_zbd1t
        e_zbd1p         = gv_zbd1p
        e_zbd2t         = gv_zbd2t
        e_zbd3t         = gv_zbd3t.
    Regards,
    Dwaraka.S

  • Regarding MIRO baseline date in payment tab

    Hi All,
    T-code: MIRO
    Input invoice date: 'xxxxxxxxxx', posting date:  'xxxxxxxxxx', PO# 'xxxxxxxxxx' and then press ENTER
    After pressing ENTER, can you do some coding to the user exit or field exit whatever in order to populate the GR date (i.e.  'xxxxxxxxxx') in baseline date field but WITHOUT pressing the "Payment" tab?
    Here i am using 4.6c version...
    please help me...

    hi,
    check these xits.
    Transaction Code - MIRO                     Enter Invoice
    Enhancement/ Business Add-in            Description
    Enhancement
    LMR1M001                                User exits in Logistics Invoice Verification
    LMR1M002                                Account grouping for GR/IR account maintenance
    LMR1M004                                Logistics Invoice Verification: item text for follow-on docs
    LMR1M005                                Logistics Inv. Verification: Release Parked Doc. for Posting
    MRMN0001                                Message output and creation: Logistics Invoice Verification
      Business Add-in
    INVOICE_UPDATE                          Business Add-In: Logistics Invoice Verification

  • User exit for VD03 to handle Payment Term (KNVV-ZTERM)

    Hi,
    I need to block a couple of Payment terms in VD03 ( KNVV-ZTERM )
    For that i need to find an exit to handle data associated with KNVV.
    Are there any exits available?
    Regards,
    Remi

    Hi,
    Thank you for the response.
    I tried writting code in the exit :
    EXIT_SAPMF02D_001. (Customers: User Exit for Checks prior to Saving)
      DATA zterm TYPE dzterm.
      "-- Block Payment Terms in SO --
      SELECT SINGLE zterm
             FROM zblkso
             INTO zterm
             WHERE zterm = i_knvv-zterm.
      IF sy-subrc =  0.
        MESSAGE e013(zmsg) WITH i_knvv-zterm.
      ENDIF.
    Set a break point to check whether it goes to that point when i try saving.
    It does not even trigger.
    I needed a point for KNVV much similar to form exit :
    userexit_move_field_to_vbak.
    Regards,
    Remi

  • Bapi_acc_document post is not calculating baseline date based pymnt terms

    Hello friends,
    Im using bapi_acc_document_post to post db and cr note and i m passing payment terms in the input file but the bapi is not calculating baseline date .
    pleasee let me knw the solution.
    Regards,
    Sunny

    that's the disadvantage of bapis and direct input in opposite to BDC. So use "old" rfbibl00 with batch input!
    A.

  • Sales order blocked for credit with status "Payment Terms"

    Hi Experts,
    Sales order is blocked for credit, as when i refer the t.code vkm3 or vkm1, the status of blocking showing as "Payment Term". Geenrally the status of credit block would be 'Old item', Dynamic check', value etc.
    My question here is how the sales order is blocked with status "Payment Terms", and what is the role of payment terms in credit management.
    regards
    Vivek.

    Hi  Vivek,
    The Standard Cr. management  ( Automatic credit check) of SAP has Critical Fields Check - payment terms is one of them,
    If it is being changed in sales order (other than maintained in Customer master) the sales order will go for credit block
    Thanks
    Dilip S

  • IDOC for creation/change of payment terms

    Hi all,
    We have a requirement to send payment terms information to a non SAP system. I am trying to look for a standard IDOC that contains this information how it can be triggered from OBB8.
    If somebody has done it before, please advice. Thanks.
    Regards,
    Nene

    HI nene,
    I think there is no standard idoc to send this. You create an RFC and send to  non sap.
    Regards,
    Madhu.

Maybe you are looking for

  • Events on iCal not showing up on my iPhone 4

    I downloaded iCloud and synced my iPhone calendar with my calendars on my mac. Before I did not have mobile me, so they were two seperate calendars that I could sync and update when I synced my phone to my computer. Now that I've merged the two toget

  • Function modul CRM_MKTBP_MAINTAIN_OW input

    Hello, i need to use FM CRM_MKTBP_MAINTAIN_OW. what exactly is the PROFILE_TEMPLATE_ID which is required in the input structure of this FM? Which database-table field is this? Thank you Best regards Manfred

  • SBL-DAT-00222: An error has occurred creating business component 'Admin SEA

    Hello, I am also facing simillar issue. I am trying to create admin account through Siebel Data bean using Business object "Users" and business component "User"; It works from Web client. but fails from siebel databean program. Following is an error

  • Applescript runner authentication required

    Hi all, Since recently upgrading one of our network machines to 10.6.6, the user of said machine keeps being prompted to authenticate when the script attached to the /Volumes/ folder kicks in. This script is in place to check that any new mounted vol

  • Major brush lag, no realtime brushing with wacom intuos 5

    hi - most of the time the pen is lagging when i brush, i cannot work in realtime, and have to wait until drawing is finished (2-4sec), with a soft brush medium size (400px) in documents at 31inch wide at 300dpi, sometimes 8 bit, sometimes 16 bit. - a