Baseline Date Issue

Dear Experts,
I am facing a peculiar problem. In the payment terms configuration i have mentioned Posting Date as the baseline date. The invoice is created in our company when the goods are dispatched. At this point only the invoice is made and accounting/release to accounting is not done. Later, when the Bill of Lading comes back to us the accounting document is created. Now the system is expected to take the later (accounting) date as the baseline date but it is taking the invoice creation date as the baseline date. Please suggest a solution.
Warm Regards,
Mukesh

In export sales, this situation would be there predominently, where the Billing Date and Bill of Lading date differs and client insists that actual sales should be considered only based on Bill of Lading Date.
Since you already set the Posting Block as per your original post, whenever user tries to release the billing document via VF02, you can populate two fields
Bill of Lading Number and
Bill of Lading Date
via Function Module EXIT_SAPLV60B_001 in include ZXVVFU01 and whatever date user is keying in, that should be your posting date.  This means, irrespective of your billing date, actual FI postings (sales) will happen only based on the date whatever user enters.   If need, you can also add couple of more fields depending upon clients' requirement.
G. Lakshmipathi

Similar Messages

  • Baseline Date issue via FB60

    Hi SAP experts,
    Can anybody help with the issue below:
    FB60 (vendor invoice) was entered.
    Invoice Date entered manually by accident with date 01/04/2020
    Baseline date is used automatically as Invoice Date 01/04/2020
    Date was corrected manually in tab Basic Data 01/04/2011
    The problem is:
    If you enter in the document (FB03) and go to additional details, the Baseline date still shows 01/04/2020
    How can this be solved so that the Baseline date in Additional Details view, shows the correct Baseline Date??
    Any help is most welcome
    Regards
    Roger

    Hi,
    Baseline date gets defaulted to the Document date in your case and this is controlled by Payment terms configured in OBB8.
    Baseline date can be configured as 1) Document date 2) Posting date 2) No Value (means you enter it at the time of entry) 4) Entry Date.
    Probably this is the reason that doc date gets defaulted n FB60.. you can go to FB02 in Change document  and make the baseline date correction.
    Regards,
    SAPFICO

  • Base Line date issue

    Hi Experts,
    I have an issue on base line date.
    We have uploaed Vendor Open item cutover data through LSMW in foreground mode.  After uploaed we found that the base line date 30.07.9999 is automatically picked wrongly in some of vendor open items.  Some of the vendor items with same payment term is picked baseline date correctly. I have corss checked in LSMW upload fields and upload excel file and also i have checked in LSMW constant values and any field mapping for baseline date but there is no such mapping and constant values in the LSMW.   If i make manual posting of the same vendors its fetching the correct base line date.
    now the issue is how to identify the cause, is it uploaed through lsmw or manual input because client is asking how it is picking defaul 9999 year. Is there any way to identify through FI Tables.
    Kindly suggest some solution.
    Thanks in Advance.
    regards,
    Surendra.

    Hello Surendra,
    The baseline date is controlled by your terms of payment and in
    customizing the transaction is OBB8. You have four choices ->
    No default - Indicator that no default value is required for the
                 baseline date for payment. You then have to enter the base
                 date manually during document entry.
    Posting date - Indicator that the posting date is to be proposed in the
                   base date field during document entry.
    Document date - Indicator that the document date is to be proposed in
                    the base date field during document entry.
    Entry date - Indicator that the entry date is to be proposed in the
                 field "Base date" during document entry.
    The system will not re-determine the baseline date if the posting
    date is changed. Similarly, if the invoice date is changed and the
    baseline date is based on the invoice date, it will also not be
    re-determined once enter is pressed.
    regads
    Ray

  • Debit memo(DR doc type) baseline date exceding the payment term days

    Hi All
    For debit memo I am facing a issue where my baseline date for a customer is showing more then the days specified in his(customer's) payment terms.
    sales document category is DR and order is created for some customer xyz and payment terms of that customer is showing 0% UP TO 15 DAYS. But when I check it in FBL5n the Net due dt for that order is showing 180 + 15 = 195days.
    What can be the reason, is it due to some enhancement or some routine or what , I am not able to figure out from where these days are coming for. I have checked MV45AFZZ , RV60AFZA and other exit s, I couldnt find any code which shows these added 180 days..
    Guide me in finding out the source ot this, <removed by moderator>.
    Thanks in Advance
    Regards
    Amit
    Edited by: Thomas Zloch on Sep 30, 2011 3:46 PM

    HI,
    You may need to check the copy control settings between the debit memo request and sales document in transaction code VTAA.
    Select the target document type and source document type, and click on the details (header level). Check the routine that is assigned for the field copying requirements for transfering business data.
    The routine assigned may be copying the base line date from the source document. You may need to assign other routine or you may need to develop your own routine to resolve your issue.
    Regards,

  • Baseline date in Accounting document changed after creation of Invoice List

    Hi all,
    1) User Requirement:-
    Creation of Invoice document(using VF01), Transfer u201CGoods Issue Dateu201D to FI accounting as a Baseline date instead of Invoice creation date.
    To meet the above requirement I did enhancement name: SDVFX008 user exit: EXIT_SAPLV60B_008.
    Its working fine and transfered goods issue date to Accounting(as baseline date) insted of  invoice date.
    2) Problem:-
    After Creation of Invoice List (VF21) system again overwriting baseline date iwith invoice list date.
    Does anyone know how to Stop overwriting baseline date in accounting while creation of invoice list.
    Thanks & Regards
    Sudheer

    Hi Valerie,
    do you recall the User Exit?
    Thanks

  • Problem with baseline date of Credit memo

    Hello all
    The issue is like this: if I am posting a credit memo using TCode- FV75 then then the baseline date is picked automatically as the document date but if I use TCode: FV70 then the baseline date is not picked.
    Can anyone please tell as what is causing this issue :
    Thanks in advance.
    Regards.

    Dear all,
    A credit Memo without an Invoice Reference is always due on the
    Baseline Date (the Exceptions to this are Credit Memos which have an
    explicitly-stated Value Date)" > this Logic was introduced starting
    from Release 3.1I.
    Summary:
    1. Credit Memo with Invoice Reference have the same Terms of Payment
       and Baseline Date as the Invoice.
    2. For the Credit Memo without Reference to an Invoice, there are 2
       methods available for choosing the due Date :
    a) The Due Date for Net Payment (RFPOS-FAEDT) is identical to the
       Baseline Date for Payment (BSEG-ZFBDT). The Period for Net Term or
       the Term of Payment is not taken into Account. This is the Default.
    b) Or the Credit Memo is due based on the Payment Terms. For this,
       you must enter the Indicator "V" in the Credit Memo Field BSEG-REBZG
       "Invoice Ref", in addition to the specified Payment Method.
       You can modify this Field for the Credit Memos already posted.
       => the above Details are documented in the Help F1 behind the
       "Invoice Ref" Field.
    Manual filling of the Field can take place during the Entry of the
    Credit Memo, or in a Document Change Transaction:
    Run transaction FB02 to call up the Credit Memos. Drill down
    to Customer Line Item. Here, you should be able to see the Field
    "Invoice ref.' (BSEG-REBZG). Place a 'V' in this Field. With this,
    the Credit Memo is due based on the Payment Terms.
    I hope this helps.
    Mauri

  • Payment term and Baseline date are not appear after residual clearing

    Hi Friends,
    We have an issue in Payment term. Recently small changes were made in OBA3.Here they enable the option of "Payment term from invoice". the function of this is to - copy  the payment term and baseline date form invoice to Partial item .Due to enable of this function after residual clearing the payment term and base line fields are get empty.
    Now user want to get these fields to be updated even not changes take place in OBA3.Can you please suggest me the way,  with out changes in OBA3 can we get payment term and baseline date field after residual clearing .Please suggest .
    Thank you
    Regards,
    Dharma

    Hi Julie,
    Thanks for your reply..
    Here the issue is, the user using Baseline date for two specific purpose.
    1.Due day calculation-auditing purpose
    2.Agning report
    For due day calculation they recently enable the option "payment term from invoice in -OBA3".Due to active the function,system copy the payment term and baseline date from invoice to residual item.it means the residual item having baseline data as invoice date not posting date.
    But for aging report purpose it has to be update posting date.
    now user want to meet these both requirement .How can it possible .Please suggest.
    Thank you
    Regards
    Dharma

  • Substitution - Baseline Date to be replaced by the Goods Receipt date

    Dear Forum,
    We have the payment terms defined in the system, with the baseline date corresponding to the 'Document Date' and the credit terms as 60 Days. The users now desire that the Baseline Date should instead correspond to the Goods Receipt Date. To enable this we need to define the substitution such as the Baseline Date at the time of Invoice Verification gets substituted by the Goods Receipt Date, if the GR Date is earlier than the IV date.
    Would appreciate help from the friends as to how to configure this and which feilds to be chosen and replaced.
    Thanks!
    Regards,

    Hi
    You can make the Baseline Date in Invoice (MIRO) with Goods Receipt Date using BADI.
    BADI -->MRM_PAYMENT_TERMS
    Tell your ABAP Guy to work on this BADI.
    In the BADI,  MRM_PAYMENT_TERMS Read the Value in WEBUD of Internal Table TI_DRSEG and Pass it into E_ZFBDT.
    Also if the Baseline Date is changed manually, then after posting you can see the Goods Receipt Date in Baseline Date.
    This resolves your issue.
    regards
    venkat

  • Billing document - Baseline date change status

    Hi folks,
    I have the following issue with the baseline date for the billing documents.
    Billing date proposed by the systems based on the goods issue is 30.01.2010 while the date of creation of document is 31.01.2010. In FB03 transaction baseline date status is showing as changed from 30.01.2010 to 31.01.2010. Following is the setting done: In OBB8 for the said payment terms the baseline date shown is the "posting date' and in VTFL item level copy control
    it is defined as "Data VBRK/VBRP         007  Inv.Split (Rec/Div)".
    Why is the baseline date getting changed by the way  User is entering the bill of lading in the outbound delivery >Header>Shipment (on 31.01.2010)..not sure if this is in any way contributing to the baseline date change...Appreciate your reply.
    cheers
    Joseph

    Baseline date is generally governed by config in OBB8 but we can influence it by writing code in USEREXIT_FILL_VBRK_VBRP. This will obviously affect baseline date in billing docs. The same should get copied into the accounting document. Now the catch is if the accounting document is changed (e.g. Payment terms) then system will populate baseline date as per the config.
    So may be you should check if there is anything in the userexit and whether accounting document was changed.

  • Baseline date

    Hello SAPians,
    There is an issue from user relating to Baseline date:is as follows
    User is trying to change the payment blocking in FBL1N, in doing so, the baseline date is being changed automatically.
    I checked the Payment terms for that vendor ,the baseline date is defined as Entry date.
    Please can you help me with this issue what need to be done.
    varanasi

    Hello Neal,
    I checked the document changes ,but I didn't find any change in the payment terms.And even I checked the Tran: OBBH but there is no Substitution for this.
    I am trying to debug the issue ,if i find anything interesting to share with you all then I will post it.
    Considering Atif & Ravi Post ,the change may be due to the user posting error.As it is a one time change I could not find it again when testing.
    Thanks for participating.
    Varanasi

  • Baseline date & Payment terms are not populating for Intercomany vendor

    Hi,
    When we post intercompany invoice & check the vendor line items in FBL1N,it is expected to have data payment terms & Baseline date from the posted Invoice.this is occuring fime with single company but this data is blank for Intercompany which is creating issues for further steps.
    Anybody has faced such issue? What may be the resolution?

    Hello,
    Why are you directly executing these programs?
    You will not expect these program to execute directly by going to SE38.
    I would have configured the relevant payment methods in the country with DME structure or classical RFFO* programs, which in turn pick up the inherent programs at the time of running F110.
    For example, if you need to generate BACS file for country GB, either you copy the GB_BACS to ZGB_BACS or use GB_BACS directly in FBZP settings.
    Make sure that you have maintained OBPM1 / OBPM2 / OBPM3 and OBPM4 settings properly.
    The system automatically gives the access to system RFFOAVIS_FPAYM. Prepare a variant against this program in F110. Relevant file gets generated to folder path mentioned in OBPM4 will get generated. The file get generated can be seen in AL11.
    Hope this is informative and solves your issue.
    Regards,
    Ravi

  • Baseline date in Debit note creation

    Hi,
    I am creating a debit note with reference to a invoice(open- 42345) for which the baseline date is 24.06.2010. For this debit note I am getting baselinbe date as 30.07.2010 (Today's date).
    Issue: I am trying create a debit note with reference to other invoice (open-42346) for which the base line date is 25.06.2010. for this debit note I am getting baseline date as 25.06.2010.
    Note:Payment terms & other details are same.
    Thank you.
    Regards,
    Pramod.

    Hello Pramod.;
    Please, have a look in flag activated (V_TVFK-XVALGS - Credit memo with value date) in T-code VOFA for your billing document. maybe this configuration can be influencing.
    Regards
    Ruy Castro

  • Date issue in processing billing documents that shipped in a prior period

    Date issue in processing billing documents that shipped in a prior period that is now closed:
    SAP values those deliveries with the current document date in A/R when it should be the original delivery date.  Baseline date needs to stay the delivery date, but is getting copied from the billing date in the new period.  A user exit exists (& needs to be applied) to manipulate the baseline date when the accounting document is being created.
    Any input is appreciated.

    Hi
    Try with Invoice Correction Request concept
    Sale document Type: RK
    Reference Document Type : Billing Number
    for Understanding the Invoice Correction request check below link
    [Creating Invoice Correction Requests|http://help.sap.com/saphelp_46c/helpdata/en/dd/55feeb545a11d1a7020000e829fd11/content.htm]
    Regards,
    Prasanna

  • Invoice: Baseline date on the payment terms.

    Dear Experts,
    I am having a problem where trying to change the term of payment of an invoice before a posting, the account doesnt set the baseline date correctly.
    This issue occurs for baseline date type 'Entry Date' .
    After whichever interaction in MIR4 , 'Enter' or 'Save', the baseline date will:
    1. set to the date as in the existing entry if there is no change .
    2. set to the system date if there is a change in the payment terms,
    where the '2nd' is not correct because the payment term changed stated that the baseline date should be 'Entry Date'.
    The above mentioned logic is inside the function module
    'FI_CHANGE_PAYMENT_CONDITIONS'
    Codes bellow shows the scenario mentioned in '1.' no changes
    Wenn keine Änderung, dann Export versorgen und Tschüss-----
    e_zterm = i_newzterm.
    zterm = i_newzterm.
    e_zfbdt = i_newzfbdt. <----
    set to the existing entry
    zfbdt = i_newzfbdt.
    e_sklin = i_newsklin.
    sklin = i_newsklin.
    check not status is initial.
    Codes bellow shows the scenario mentioned in '2.'terms change, and baseline date type 'C'
    T052 contains first entry for payment term key entered "P00K005354
    case t052-zdart. "P00K005354
    when 'C'. "P00K005354
    zfbdt = sy-datum. "P00K005354
    if i_cpudt is initial. "Note 199967
    zfbdt = sy-datum. "P00K005354 <------ set to current date
    else. "Note 199967
    zfbdt = i_cpudt. "Note 199967
    endif. "Note 199967
    Is this a program logic error or is it the way it should be ?
    Any one encounter the similar problem ? or should there be OSS notes to apply ?
    Thank you .....

    .

  • Baseline Date after a change in Terms

    Dear Experts,
    I am having a problem where trying to change the term of payment of an invoice before a posting, the account doesnt set the baseline date correctly.
    This issue occurs for baseline date type 'Entry Date' .
    After whichever interaction in MIR4 , 'Enter' or 'Save', the baseline date will:
    1. set to the date as in the existing entry if there is no change .
    2. set to the system date  if there is a change in the payment terms,
    where the '2nd' is not correct because the payment term changed stated that the baseline date should be 'Entry Date'.
    The above mentioned logic is inside the function module
    'FI_CHANGE_PAYMENT_CONDITIONS'
    Codes bellow  shows the scenario mentioned in '1.' no changes
    Wenn keine Änderung, dann Export versorgen und Tschüss-----
      e_zterm = i_newzterm.
      zterm = i_newzterm.
      e_zfbdt = i_newzfbdt.    <----
    set to the existing entry
      zfbdt = i_newzfbdt.
      e_sklin = i_newsklin.
      sklin = i_newsklin.
      check not status is initial.
    Codes bellow  shows the scenario mentioned in '2.'terms change, and baseline date type 'C'
    T052 contains first entry for payment term key entered    "P00K005354
          case t052-zdart.                                "P00K005354
        when 'C'.                                    "P00K005354
           zfbdt = sy-datum.                     "P00K005354
           if  i_cpudt is initial.                   "Note 199967
               zfbdt = sy-datum.                "P00K005354   <------ set to current date
           else.                                      "Note 199967
               zfbdt = i_cpudt.                   "Note 199967
           endif.                                     "Note 199967
       Is this a program logic error  or is it the way it should be ?
    Any one encounter the similar problem ? or should there be OSS notes to apply ?
    Thank you .....

    Hi,
    If i gave the query that i mentioned above post, in my sql statement, the dynamic action is working but not fetching the correct date for the selected priority..
    what is the answer that im getting is
    When i select priority as low means
    what is populating in my due date field is not the date im expecting........
    it is giving some thing in the due date field like the below i mentioned.......
    " ,,11/10/10 0&amp;#58;0&amp;#58;0,11/10/10 0&amp;#58;0&amp;#58;0,,,,,,,,,,11/24/10 0&amp;#58;0&amp;#58;0,11/24/10 0&amp;#58;0&amp;#58;0,,,,,,,,,,,11/04/10 0&amp;#58;0&amp;#58;0,,,,,,,11/24/10 0&amp;#58;0&amp;#58;0,,,,,,,,,,,,,,,,,,,11/18/10 0&amp;#58;0&amp;#58;0,,,,,,11/24/10 0&amp;#58;0&amp;#58;0,,,11/24/10 0&amp;#58;0&amp;#58;0,11/24/10 0&amp;#58;0&amp;#58;0,,,,11/27/10 0&amp;#58;0&amp;#58;0,11/26/10 0&amp;#58;0&amp;#58;0,,,,,,,11/05/10 0&amp;#58;0&amp;#58;0,,,,11/24/10 0&amp;#58;0&amp;#58;0,11/24/10 0&amp;#58;0&amp;#58;0,,,,,,,,,,,11/19/10 0&amp;#58;0&amp;#58;0,11/05/10 0&amp;#58;0&amp;#58;0,11/24/10 0&amp;#58;0&amp;#58;0"
    i dont know why it is returning like this......please help me........
    Regards,]
    Harry......

Maybe you are looking for

  • Email button error works but gives Error message "10"

    I have "attach to email" buttons on my forms. I leave the email address blank for the person to fill in themselves. It works fine but on one form (and one form only) when clicking on the button an error message window comes up - with exclamation mark

  • Can't find upgrade master dvd  for ERP 6.0 EHP4 !

    Where can I find the upgrade master dvd for upgrade to ERP 6.0 EHP4  (windows/oracle) ? Does anybody knows the right materialnumber? My collegues has copied the relevant dvds from sap upgrade dvd-package to disk and I don't find th "upgrade master dv

  • Can't launch Business rules from Smartview

    Hi, I am trying to lauch a business rules from smartview, but the "calculation option"/ "business rules" menu is unavailable in Excel. This business rules is available in the Web HBR launcher. How could I get access to business rules in Excel please

  • Stuck at automated Activity

    Hello, I'm new to NetWeaver BMP and in SAP in general. I've downloaded and installed the following Trial Version: [SAP NetWeaver Composition Environment 7.2 Trial Version|http://www.sdn.sap.com/irj/scn/downloads?rid=/library/uuid/a0a6bd7b-3dfc-2c10-e

  • How to convert olympus RAW (.orf) to work with CS5?

    Hi-- I've never worked with RAW before so I'm learning as I go-- & immediately hit head-on into this wall--can't even begin to work with it.  I tried downloading some conversion filters that sounded like they would work with converting this format, b