Baseline date change OBB8- payment terms

Hi
Is it ok to change the baseline date in a payment term in OBB8 after posting several invoices? What consequesnces should this change have?
Thanks in advance
Aparna

This will effect for the all pending invocies. The effect could be change in the payment schedule for the vendors.

Similar Messages

  • 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 .....

    .

  • 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,

  • How to get default baseline date in a payment terms

    Hi,
    We have around 160 payment terms used in our system. We want to get the default baseline date for all these payment terms. Going to each individual payment terms and getting the default baseline date is a cumbersome job.
    Is there any easy way to get the default baseline date for each of the payment terms, like from any table or anything else. I have tried table T052. But it does not have default baseline date.
    Please help.
    Regards
    B.Mohanty

    Hello Bibhu,
    default baseline date is a customizing setting in paymentterms. That's the only way.
    I have no idea why TC lsmw is recommended, definetely the wrong way.
    Best regards
      Horst

  • Baseline date for Partial Payment in FB05

    When we created partial payment for SD invoice in FB05, the baseline date for line item is defaulted to today date. How to change this default date to original invoice date? Is there any OSS note that could do this? We are in version 4.7.

    Yes we are aware that baseline date determine in Payment Term setup OBB8.
    Our setup for Baseline date is Document date. We have invoice with document date e.g 01/01/2007. When we create partial payment using FB05, and do simulation. The baseline date change to new document date (e.g today date). We also aware that we can modify the baseline date directly in simulation. But we need to automate this, so we need to check if there is OSS notes that will default baseline date to original Document Date instead defaulted to new Document Date.

  • 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 Change

    Hi Experts,
    While doing MIRO, , the baseline date will be default as document date based on Payment Terms.
    But in my case, both invoice date and base line date is different. I assure that baseline date will set as default invoice date and it was changed while doing MIRO.
    But Client wants to confirm whether the entries (Baseline date) were changed or not.
    Any pointers to find the changes occured in the Baseline date.
    by
    Prabhu

    Dear,
    There is one more solution :
    Go to tcode MIR4..
    Enter the document and year.click on ENTER.
    Click on "GO TO" in Menu bar.....Click on Display change document.
    Here also you can get the changes which have occured in MIRO document.
    regards
    Utsav

  • Issuing a warning message while changing the payment terms in FB02

    Hi Gurus,
    The requirement is as follows:
    For a particular payment terms meant for customer only when we change the payment terms in FB02, the system should give an warning message.
    For example - A customer has the payment terms 0001in his master data and thus in the accoutning document as well after releasing billing to accounting. An user wants to change the payment terms to 0070 being in FB02. As and when he puts the payment terms 0070, the system should give an warning meesage saying 'bla bla bla ........' or the same message at the time of saving the document.
    How to make this possible. Please help.
    Rgds,
    BABA

    Mr. Tiwari,
    This is the standard feature of SAP!!!  You get below messages
    1)
    Net due date on 05.10.2007 is in the past
    Message no. F5149
    Effects on Customizing
    You can define when this system message is to be issued in accordance with your requirements.
    You do this in Customizing as follows: Cross-Application Components -> Bank Directory -> Change Message Control.
    The application area and message number can be taken from the technical documentation.
    2)
    Net due date on 05.10.2007 is in the past
    Message no. F5149
    Effects on Customizing
    You can define when this system message is to be issued in accordance with your requirements.
    You do this in Customizing as follows: Cross-Application Components -> Bank Directory -> Change Message Control.
    The application area and message number can be taken from the technical documentation.
    Terms of payment changed; Check
    Message no. F5231
    Effects on Customizing
    You can define when this system message is to be issued in accordance with your requirements.
    You do this in Customizing as follows: Cross-Application Components -> Bank Directory -> Change Message Control.
    The application area and message number can be taken from the technical documentation.
    Regards
    Santosh Hegde

  • Not allowing changes to payment terms after the AR document is released to accounting

    Hi,
    Anyone know the best way to not allow a user to change the payment terms after the AR document has been created in AR? This is affecting aging because users are changing the payment terms without permission. What is the best way to control that?
    Thank you.
    AK

    Hi A K
    Frequent change in payment terms is something business should introspect. Payment term is decided and agreed upon with customer/vendor during the initial stages.
    However from IT perspective, it can be controlled keeping some system controls.
    1. Limit the Customer master change transaction to very limited users or to a manager. There should be internal approvals by management for business to make a change. Bring this into force.
    2. Regularly run the customer master change reports and provide the trend to management to restrict or limit the changes.
    3. Use Change Message control for master data by providing necessary warnings or error messages when master data is changed.
    4. In  the sales order level, there is every possibility to change the payment term. Based on the user authorization get the payment term field greyed out and provide change access to accounting or to a specific user upon approvals. This is a bit complex process but I feel this brings up controls and stops the process from exploitation.
    5. Also activate 'Sensitive fields' KNB1-ZTERM for payment term field in customer master. This brings up another layer of confirmation of change by other users.
    6. Another back route, not recommended in all cases, is to subsititute the required payment term during accounting document posting.
    Hope it helps.
    Thanks,
    Sekhar

  • Different discount date from that of due date without using payment terms

    Hi,
    We would like have separate discount due date from due date without using payment terms for each invoice.
    We wants to modify ERDK-FAEDS but unable to find suitable event/exit for the same.
    So can anyone suggest any event where this can possibly be achived.
    Regards,
    Paresh

    Hi,
    We are using continuous days for working out due date from document date.
    But for discount due date business sought to provide only working days (say 7 days) from document date.
    So as to satisfy this requirement, I had adopted event R436 where system intially takes values provided but somehow it gets cleared in below lines. So I am unable to find a workaround to resolve this issue.
    PERFORM get_user_exit_function USING 'R436'.
      LOOP AT t_fbstab WHERE funcc <> 'ISU_SAMPLE_R436'.
        tmp_erdk = p_iiu-print_doc-erdk.
        tmp_erdz[] = p_iiu-print_doc-t_erdz[].
        CALL FUNCTION t_fbstab-funcc
          EXPORTING
            x_invoice_param    = p_param
            x_invoice_unit     = p_iiu
          TABLES
            xy_printdoc_lines  = tmp_erdz
            y_new_bill_lines   = tmp_new_bill_lines
          CHANGING
            xy_printdoc_header = tmp_erdk
          EXCEPTIONS
            error_message      = 1.
    Regards,
    Paresh

  • Change of Payment Term

    Hi All,
    1. I think we can change the payment term assigned to the vendor (in master data) while posting the invoice, please confirm if I am correct?
    2. Is it possible to change the payment term in the document before the payment either in case of manual or automated payment run (F110).
    Rg
    vk

    hi
    yes its possible to change payment terms in master data and in document before payment.
    You can restrict the payment terms changing by document change rule if you want.
    So if in your case document change rule has not restricted payment terms change it is possible to change it.
    Rewards points
    thanks
    s ap

  • How to make net due date dependent on Payment Terms in credit memo FB75

    Hi Experts,
    In our system currently when we create credit memo using tcode FB75 system makes the invoive due immediately.
    We wanted to make this net due date dependent on payment terms given by us. Please let me know how can I achieve this..
    Please let me know if there is any user exit there or the configration path to achieve this...
    Regards,
    Vidya

    Hi,
    "vbdkr-zterm. is nothing but Payment terms
    *   Fetching Payment term details
        SELECT SINGLE * FROM t052 INTO w_t052 WHERE zterm = vbdkr-zterm.
        IF sy-subrc = 0.
          CLEAR i_faede.
          MOVE-CORRESPONDING w_t052 TO i_faede.
          MOVE: w_t052-ztag1 TO i_faede-zbd1t,
          w_t052-ztag2 TO i_faede-zbd2t,
          w_t052-ztag3 TO i_faede-zbd3t.
          i_faede-bldat = BKPF-budat.                         "this is Importnat posting date
          i_faede-koart = 'D'.
    *     Fetching Due date using Function Module
          CALL FUNCTION 'DETERMINE_DUE_DATE'
            EXPORTING
              i_faede                    = i_faede
            IMPORTING
              e_faede                    = e_faede
            EXCEPTIONS
              account_type_not_supported = 1
              OTHERS                     = 2.
          IF sy-subrc <> 0.
          ENDIF.
          w_invdate = e_faede-netdt.              "this field contains Net due date...
        ENDIF.
    Prabhudas

  • Do not change the payment term created a Sales Order with reference

    Hi Gurus,
    Do not change the payment term created a Sales Order with reference to a contract where the payer of the change in Sales Order.

    Hello ,
    As per my understanding , you do not want the payment terms to be changed even if the payer partner function is changed ,
    as standard sap redetermines the payment terms with change in partner function, you may use the exit
    USEREXIT_MOVE_FIELD_TO_VBAK- header level
    USEREXIT_MOVE_FIELD_TO_VBAP- Item level
    in this you could write a small code which will not change the payment terms when payer is redetermined
    hope this helps
    Thanks
    akasha

  • Release retriggering while changing the payment terms

    Dear All,
    After releasing the purchase order if anybody Changes then payment terms in me22n, release should retrigger how to configure this process
    Regards,
    Vijaybhaskar

    Hi,
    You have two option to achieve this no.1 through user exit
    refer this link
    Release strategy for PO on Payment terms..
    No. 2 through version management
    refer this link
    Restricting Purchase order's payment terms change authorization

  • Change of Payment Terms: Vendor

    Hi All,
    Can somebody tell me how can we collectively change the payment terms in Vendor Master for a purchase organization.
    That is I dont want to change the Master Records individually...I want to change the records collectively....
    Please advice.....
    Helpful replies shall be rewarded accordingly.....
    Regards,
    Rounak

    Hi All,
    Thanks a ton.....
    It was helpful......
    Regards,
    Rounak

Maybe you are looking for

  • Possible bug in 3.1.1 with APP_ALIAS substitution string?

    Hello team, this morning we carried out the migration to 3.1.1 however i noticed that the only translated application i have doesn't correctly handle the APP_ALIAS substitution string any more. I had to manually replace all the occurrences of APP_ALI

  • Connecting my guitar to my IMAC?

    I'm trying to play my electric guitar through my IMAC. I have external speakers connected to my Headphones socket in the back of my MAC, how do i go about playing my guitar through those speakers? I have an adapter that will allow me to connect my gu

  • IM - IM52 Original assigned budget is automatically multiplied by 100

    When assigning the original budget to a Project (from a node) in the Investment Progam (transaction IM52), the amounts entered are automatically multiplied 100, but the available budget for the project is correct and the amount discounted in the Node

  • Using JProgress bar

    Dear all I am trying to you jprogress bar because on the program I am doing at the moment there are a lot of functions that take time to execute and so I thought that it would be good to use jprogress bar but I am not sure how to use it. I looked at

  • DBAdapter insert failing in Fusion Middleware SOA Suite 11g

    Hi, I am trying a simple example of inserting into database using DBAdapter. Here is the log message and am unable to figure out the problem it says log at DBAdapter logs can someone tell me where does DBAdapter logs exists. I tried the select and it