Change Due date of Retention Document

Hi,
I have posted one Retention document through MIRO & put some due date.
Now I want to change this Due date (Baseline payment date) in FB02, but in the line item I am not able to see that field.
It is showing in FBL1N, but as I click on change document, this field is hidden.
How can I change this due date field?
Regards,
Hitesh

Hi Hitesh,
Baseline item can be changed when document is not cleared. Please make sure that it has not restricted through line item change rules(OB32).
You can change the baseline date of the transaction manually by double-clicking the line item from FBL1N or FBL5N and then change using the change option, save, & refresh
Necessary settings has to be done in OB32.
Also check if the baseline date field is editable in your case.
SPRO > FA (new) > Document > rules for changing document.
BSEG-ZFBDT field for vendor or customer as required should be present.
I hope you find this information helpful.
Regards,
Jose

Similar Messages

  • Cannot change Due Date in marketing Documents

    Hello to all
    i have a problem with marketing documents. while they are open-printed, i cannot change the due date. it is grey and read only
    the payment terms has one installments and the localization is Cyprus
    in another installation with localization Italy i can  edit the due date
    do you have any idea about it?

    Hi,
    You may test this solution:
    To change the due date of an installment, perform the following:
    Open the relevant document and choose the Accounting tab.
    Click the orange link arrow in the Installments field.
    In the Installments window, in the Date column, change the required date and choose the OK button.
    To save the changes, in the sales or purchasing document, choose the Update button.  
    it quoted from sap note 1333212 - Changing the due date on installment modifications
    Regards,

  • [VF11] change due date when cancelling a document

    Hi everybody,
    I want to change due date (( FAEDT ) in FBL5N ) when cancelling invoices in VF11.
    I know that for that I need to change ZFBDT but I dont konw how .
    I need a user exit or a BTE or a Custo to make me change the due date.
    Thanks in Advance.

    Hi,
    As understand from your question, I think its better practice to change the baseline date either manually or automatically from some logic during the billing document creation.  This can be done through through the following userexit
    USEREXIT_FILL_VBRK_VBRP   or
    SDVFX004 or
    SDVFX008
    or
    As Mr.Lakshmiprasad explain in his message, make the default setting after concern with FI Consultant in OBB8.
    Regards
    Goutham

  • Approval for change Due date in AR invoice through Paymnet Term

    Hi all!
    I try to query for approval with AR invoice change Due date in AR invoice through Payment Term.
    SELECT Distinct 'True' FROM OCTG T0  INNER JOIN OINV T1 ON T0.GroupNum = T1.GroupNum
    WHERE dateadd(day, T0.[ExtraDays],T1.[TaxDate])<>   T1.[DocDueDate] and  T1.[CardCode] =$[$4.0.0] and T1.[Docnum]=$[T1.[Docnum]
    I think we can not combine 2 variable for this form (
    T1.[CardCode] =$[$4.0.0] and T1.[Docnum]=$[T1.Docnum]
    Could you help me!
    Thanks!

    Hi Tien again.......
    In order to prevent the misunderstanding again please ket me know
    whether I'm correct or not.
    You want such kund of approval where if in the base document Payment Terms Net30 is there
    and in the target document if its changed to Net 60 then it should ask the approval while adding.
    M I right?
    Regards,
    Rahul

  • Error while changing due date deadline

    Hi,
    I am trying to change due date deadline of an action. I am getting this error. Please see if you can help me on this?
    I don't think this error is from my code.
    <p>
    <b>Root Cause</b>
    The initial exception that caused the request to fail, was:
       com.sap.caf.eu.gp.base.exception.InvocationException: Impossible to define a start date.
        at com.sap.caf.eu.gp.model.pfw.util.Deadline.setStartDate(Deadline.java:209)
        at com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueItemsPersistence.retrieveDeadline(NotificationQueueItemsPersistence.java:912)
        at com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueItemsPersistence.retrieveNotification(NotificationQueueItemsPersistence.java:850)
        at com.sap.caf.eu.gp.model.pfw.notification.NotificationQueueItemsPersistence.retrieveNotifications(NotificationQueueItemsPersistence.java:1032)
        at com.sap.caf.eu.gp.model.pfw.notification.NotificationManager.retrieveNotifications(NotificationManager.java:563)
        ... 135 more
    <p><b>
    Detailed Error Information</b>
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session ApplicationSession(name=com.sap.caf.eu.gp.ui.rt.Runtime, id=qFEa9dPuRZ1jAYyFzhCxAAECkPW7TnlHbbTL4aP4cq5Q/pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.caf.eu.gp.folders.gp/com.sap.caf.eu.gp.roles.runtime/com.sap.caf.eu.gp.worksets.runtime/com.sap.caf.eu.gp.pages.procinstance2/sap.com/cafeugpuirt/Runtime/base/). The causing exception is nested. RID=1dda6030410b11dead950050568f296d
    <br>  at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:650)
    <br>  at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:225)
    <br> at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)
    <br>  at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
    <br>  at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
    <br>  at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
    <br>  at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
    <br> at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
      <br>at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
      <br>at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
      <br>at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.dispatch(ApplicationHandle.java:320)
      <br>at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
    <br> at com.sap.tc.webdynpro.portal.pb.impl.LocalApplicationProxy.sendDataAndProcessActionInternal(LocalApplicationProxy.java:1043)
      <br>at com.sap.tc.webdynpro.portal.pb.impl.LocalApplicationProxy.create(LocalApplicationProxy.java:259)
      <br>at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1563)
      <br>at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:390)
    <br> at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:628)
      <br>at com.sap.portal.pb.PageBuilder.wdDoApplicationStateChange(PageBuilder.java:330)
      <br>at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoApplicationStateChange(InternalPageBuilder.java:166)
      <br>at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doApplicationStateChange(DelegatingComponent.java:222)
    <br>  at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doApplicationStateChange(ClientComponent.java:633)
    <br> at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doApplicationStateChange(ClientApplication.java:693)
    <br> at com.sap.tc.webdynpro.clientserver.phases.ResumePhase.execute(ResumePhase.java:65)
    <br> at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:161)
    <br> at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:109)
    <br> at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:96)
    <br> at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:469)
      <br>at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
    <br> at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1431)
      <br>at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1251)
      <br>at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:158)
    <br> at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
    <br> at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
    <br> at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
      <br>at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
    <br> at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:81)
      <br>at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:507)
      <br>at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:527)
      <br>at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:458)
    <br> at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:249)
      <br>at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:699)
      <br>at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:231)
      <br>at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)
    <br> at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
      <br>at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
      <br>at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
    <br> at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
    <br> at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
    <br>  at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
    <br>  at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
    <br>  at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    <br>  at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
    <br> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    <br> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    <br>  at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
    <br> at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
    <br> at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
    <br> at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
    <br> at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
    <br> at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
      <br>at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
      <br>at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      <br>at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
    <br> at com.sap.engine.se
    Edited by: Pratik Khandelwal on May 15, 2009 7:01 AM
    Edited by: Pratik Khandelwal on May 15, 2009 7:02 AM

    Dear Prathik,
    Please share me how you have change deadline in runtime for notification.
    can u plss share the code and procedure it will be very thankful to u.
    Rajesh

  • Function module to calculate due date of FI document

    Hi All
    I need a function module to calculate the due date of FI document considering BSId Zterm ( Payment terms ) Document date , Basline date .
    Regards,
    chitra

    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_zbd2t         = gv_zbd2t
        e_zbd3t         = gv_zbd3t.
    faede-shkzg = 'H'.
      faede-koart = 'K'.
      faede-zfbdt = gv_zfbdt.
      faede-zbd1t = gv_zbd1t.
      faede-zbd2t = gv_zbd2t.
      faede-zbd3t = gv_zbd3t.
      faede-bldat = gv_bldat.
      call function 'DETERMINE_DUE_DATE'
        exporting
          i_faede = faede
        importing
          e_faede = faede.
    *    if sy-subrc eq 0.
      duedate = faede-netdt. <<<<<< ------

  • Print Layout Designer:Due date in Delivery document

    In print layout designer in 2005 version for Delivery document when they preview the document in document printing it compute an automatic due date but if the preview was done in the delivery document itself the due date is the same as posting date.
    And as to delivery document in SAP no due date will be computed because due date will be determine upon invoice. But upon checking on their database, the same layout/template was used in the preview of the document in the delivery itself and in the document printing. The due date used in the layout was delivery due date.
    They want to apply the scenario of having automatic computation of due date in Delivery document in the print layout designer in their 2007 version. All details created in the Print layout designer in 2005 version are defined already in their 2007 version but when the document was preview in document printing no computation of due date.
    Is the layout used in the preview of delivery document itself was different when i used the document printing and select the same document and preview it? Is it possible to compute the due date in delivery document?
    Can someone help me?

    Hi Paul,
    Yes, we already informed our customer that in delivery document no due date will be computed. But my question is it is possible that the print layout used in the preview of delivery document itself was different when the preview is done in the document printing window? To preview the document in document printing, select or highlight one transactions and click preview.
    When we check the customer database and preview the delivery document itself the due date is
    the same as posting date but when i preview the document in the document printing when you check the
    field due date it was not the same as posting date.
    We check the layout and the field is Database Delivery: Due date. The layout name was also the same when we preview
    the transactions in delivery document itself and in the document printing.
    Can someone tell me if the layout was different in the document printing window under Sales A/R module?
    Thanks,
    Janice

  • FI: Payment condition calculating 2 due-dates depending on document-date

    Hello community!
    I'm searching for a definiton of a FI-payment-condition which is calculating two different due-dates depending on document-date.
    E.g.:
    Invoices dated from 01.03.08 till 09.03.08 should be paid on 10.04.08.
    Invoices dated from 10.03.08 till 31.03.08 should be paid on 10.05.08.
    Or must this be realized by a FI-substitution???
    Thanks for an answer.
    Kind regards,
    Bernd

    Hello,
    You didnot mention if u need posting date as base or document date. However your scenario, below is
    the answer for your query is
    1. Create one customised payment term only eg. XXX
        for first scenario,
       Day limit is 9 ;
       under payment terms tab , fixed date 10, Addl month 1
       for second scenario
       in the same payment term XXX
       Day limit is 31,
       under payment terms tab , fixed date 10, addl month 2.
    Explanation.
      as day limit is 9, what ever the dates of transaction between 1-9 it picks first setting
    and after 9th until 31st it picks second setting.
    I hope this clarifies you.
    Thanks
    G.Bharathi

  • Due date as the document date in Payment run

    Hi,
    We would like to have the invoice due date as the document date for the payment document.
    To explain in detail; let us suppose I am executing a payment run today i.e. 19.02.2008 with the next payment date as 31.03.2008. The payment program picks the invoice due on 25.02.2008 as well. The bank statement shows the document date as 25.02.2008 (as they will make payment on that date)but the system posts the payment document with the posting date as the document date.
    Can smebody help me to have the net due date of the invoice as the document date in the payment document created by F110.
    Thanks & Regards,
    Raghava

    Hi Anand,
    In your case, the Payment document is also a clearing document since you are not carrying out the manual clearing.
    The only way which can satisfy your requirement is not to have any payment term assigned to your Vendor to whom you want to pay thru F110.
    This will make your invoice immediately due, so when you pay your Payment document/Clearing document has the same date.
    (There is no other way to make the due date as clearing date/payment doc date since we do not know when the clearing/payment would happen)
    Hope this resolves your query.
    Regards
    Bharat

  • Function Module/Document to change Reversal date for FI  document.

    Can anyone please provide me with the Function Module/Document to change Reversal date for FI  document.

    Hi Vikram,
    Normally, you post a reversing document in the same period you posted the original document.  The period of the original document must be open to post a reversing document. If the period is not open, you can overwrite the posting date field with a date in an open period, such as the current period.
    Regards,
    Manoj.

  • Change due date in receivables for credit check

    Hi Sappers!!
    Scenario: When SAP performs a credit check for a customer we need that pending receivables
    (open items) for this customer which have a concrete payment method, don't use due date
    for calculation, instead we want to use invoice date for carrying out the credit check
    calculation.
    Is that posible? Is there any user-exit where we can change this date to be used during
    credit check control for documents which fulfill this requirement?
    We don't want to change permanently the due date for this kind of documents, we only need to take another date into account when performing credit control.
    Thanks so much in advance & best regards

    Thanks so much for your quickly answer.
    Creating a new payment term is not a valid solution because, we don't want to change any date in the financial document. We just only need to use another data only for credit check. Here you have a concrete example:
    Invoice created with invoice date 01/12/2009
    Payment method confirming 90 days.
    Base line calculated: 01/03/2010
    If we create a new sales order, this open item will not be considered exceeded because due date is still in the future.
    We want to consider it as exceeded and the due date would be 01/12/2009 but only for credit check. This "new" due date must not be stored anywhere.
    Thanks so much once again & best regards

  • Changing due date in SP GL transaction

    Frnds
    I posted a down payment request with Due date, but i need to change that due date, actualli tried to do itin FBL1N, with the selection of Special GL transactiona and Noted items,
    i am able to pull the document, but when it chage it from display mode, Due date field is not being active.
    how cani change th due date?
    thanks

    Ravi
    in ob32
    Field Name is BSEG-ZFBDT - Baseline payment date
    Rule is valid for....
    Account type K- Vendor line items
    Transaction type --  it is blank
    company code--- it is blank
    Possibility of changing the field.
    Field can be changed ( it is ticked)
    Stipulation for changing
    Posting period not closed ( Not ticked)
    Line item not cleared ( It is ticked)
    Custome debit of vendor debit (not ticked)
    No invoice related credit memo ( it is ticked)
    No credi memo from down payment ( It is ticked)
    Above is the configuration.
    please have look at it and let me know the solution
    thanks

  • Any one knows how to change "TransptnPlanng date" in delivery document?

    Deal All,
    Could any one provide the BAPI/FM that can change "TransptnPlanng" date/time in inbound/outbound delivery documents?
    I need to update the dates only in ABAP program based on external information.
    I tried WS_DELIVERY_UPDATE with the following parameters setup:
    VBKOK_WA-VBELN_VL = target delivery number
    VBKOK_WA-TDDAT = "12/12/2009"
    VBKOK_WA-TDUHR = "12:12:12"
    (for the other fields in structure VBKOK_WA, I leave them blank)
    DELIVERY = target delivery number
    After run the FM in test mode, no error returns but no data updated in the delivery... (dates not change)
    Do I need to specify all the other fields for the delivery (like delivery date, line item details etc) even though I just want to update two fields in the header of the delivery?
    Thanks & Regards,
    Wenling

    BAPI_OUTB_DELIVERY_CHANGE works in this case (just to change the date)
    Need to put "X" on the date field on structure BAPIOBDLVHDRCTRLCHG and need to use table BAPIDLVDEADLN with correct date type to update.
    Thank you all for your replies.

  • Implications of Changing Posting date of parked document.

    Hi,
    I have changed the posting date, document date & translation date to current period
    of an already parked document in a closed period.
    (e.g) Document parked in month of 28.04.2009(closed period) & i have changed the dates to
           28.05.2009(current period)
    I need to know what are the implications of the changes in dates for (posting date, document date & translation date) induvidually for both the periods(closed & current).
    Thanks
    Kenn

    Hi,
    There is no implications of change the the posting date of parked document because parked documents are not affected in financial.When you post the doucment then it will affect in finance.so there is no problem. You can change the posting date or document date only in a Fiscal year.

  • How to change Due date in Cash flow (yet to post) lines in a contract.

    Hello All,
    I have a requirement where i want to change the due date of cash flow line items of a contract. I am able to do that in RECN transaction, by clicking on the date field and change the date. Here i am looking for a BAPI or function module using which i can update the date of cash flow items. Can anybody help me in doing this.
    Thanks,
    Bala.

    Hi Bala,
    we had a similar requirement during the initial implementation project.
    We have used BADI_RECD_CASHFLOW for this purpose. We have used both Methods - CHANGE_CASHFLOW_OBJ and CHANGE_CASHFLOW_PAY in such a way (for the last one):
      LOOP AT ct_pay ASSIGNING <ls_cashflow_pa>
                 WHERE ( cfstatus = 'P'              ) AND
                       ( origflowtype IS NOT INITIAL ) .
        IF <<condition>>.
          <ls_cashflow_pa>-dfaell = ....
        ENDIF.
      ENDLOOP.
    HTH,
    Siarhei

Maybe you are looking for