Cutting checks against invoices with a later date

A question/issue from a customer.
They post AP invoices with future dates. Problem is, SAP would not allow them to cut a check for invoices that were posted at a later date than the check posting date.  Any idea how to get around this?
thanks
Simon

Ok thanks I guess the answer is that they can't do that it.
Not sure I agree with your statement though. If you incur a charge for using software maintenance contract for 2009, then that should hit P&L in 2009. if they book that in 2008, they will have double charges from 08 and 09.
Anyway, I dont mean to start a discussion on this. Thanks for the response. you have answered my question.

Similar Messages

  • My iphone has synced with a later date than photos taken and now cant get resent photos back?

    my iphone has synced with a later date than photos taken and now cant get photos recently taken same with messages :-(

    iDevices do not sync with a date... they sync with the computer.
    If the user has restored the device using an older backup, simply restore it with a more current backup.

  • Check double invoice with GL account and Reference field

    Dear SAP GURU's,
    I am very new to SDN. I have one query.
    I know we have the option of control double invoice against Vendor/Customer by using reference field. But here my client is asking that control has to be from GL account and reference field, becoz some times he will receive the shipping bills 3 or 4 times agianst one billing document ( i am booking Transporter Vendor invoice by using FB60) with same bill number but expense GL's will be different most of the times. Some times knowingly or unknowingly same GL Expenditure account will be repeated with the same shipping bill number. This was happend most of the times.
    So can i know how can i get the GL account and Reference field checking and error message for the same.
    Thanks & Regards,
    Shobha.

    Dear Shobha,
    I feel that having a check on GL is not a good idea.  If your client insists you can go for an exit or BTE. 
    We used BTE to have the same functionality of Logistics for FI documents also in our office.
    Duplicate Invoice check process documentation is given below for your ready reference --
    with Regards
    Check Flag for Double Invoices or Credit Memos
    Indicator which means that incoming invoices and credit memos are checked for double entries at the time of entry.
    Use
    Checking Logistics documents
    Firstly, the system checks whether the invoice documents have already been entered in the Logistics invoice verification; the system checks invoices that are incorrect, or invoices that were entered for invoice verification in the background.
    Checking FI documents
    The system then checks whether there are FI or Accounting documents that were created with the original invoice verification or the Logistics verification, and where the relevant criteria are the same.
    Checking Logistics documents
    In checking for duplicate invoices, the system compares the following characteristics by default:
    Vendor
    Currency
    Company code
    Gross amount of the invoice
    Reference document number
    Invoice document date
    If all of these characteristics are the same, the system issues a message that you can customize.
    When you enter credit memos or subsequent adjustments, the system does not check for duplicate invoices.
    Exception: Country-specific solution for Argentina, where invoices and credit memos are checked for duplicate documents.
    No message is issued if you enter a document that has previously been reversed.
    Dependencies
    The system only checks for duplicate invoices in Materials Management if you enter the reference document number upon entering the invoice.
    In Customizing for the Logistics invoice verification, you can specify that the following characteristics should not be checked:
    Reference document number
    Invoice document date
    Company code
    This means that you can increase the likelihood that the system will find a duplicate invoice, because you can reduce the number of characteristics checked.
    Example
    The following document has already been entered and posted:
    Reference document number: 333
    Invoice date: 04/28/00
    Gross invoice amount: 100.00
    Currency: EUR
    Vendor: Spencer
    Company code: Munich
    You have made the following settings in Customizing:
    The field "Reference document number" and "Company code" are deselected, which means that these characteristics will not be checked.
    Now you enter the following document:
    Reference document number: 334
    Invoice date: 04/28/00
    Gross invoice amount: 100.00
    Currency: EUR
    Vendor: Spencer
    Company code: Berlin
    Result
    Because you entered a reference document when you entered the invoice, the system checks for duplicate invoices.
    The reference document number and the company code are different from the invoice entered earlier, but these characteristics are not checked due to the settings you have made in Customizing.
    All other characteristics are the same. As a result, the system issues a message that a duplicate entry has been made.
    If the "Reference document number" had been selected in Customizing, the system would have checked the document and discovered that it was different from the invoice entered earlier, so it would not have issued a message.
    Checking FI documents
    Depending on the entry in the field "Reference", one of the following checks is carried out:
    1. If a reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has been posted where all the following attributes agree:
    Company code
    Vendor
    Currency
    Document date
    Reference number
    2. If no reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has been posted where all the following attributes agree:
    Company code
    Vendor
    Currency
    Document date
    Amount in document currency

  • Problem creating A/R Invoice with Withholding tax data via DI-Server

    Hi!
    Using the following SOAP Request to the DI-Server, I wanted to create an A/R Invoice having a withholding tax data but it always respond with an error saying
    Total taxable amount of all rows exceeds the base amount  [INV5.TaxbleAmnt][line: 1]
    SOAP Request:
    <?xml version="1.0" encoding="UTF-16"?>
    <env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
      <env:Header>
        <SessionID>203A3C01-7808-4638-8322-2307DF3C0F8F</SessionID>
      </env:Header>
      <env:Body>
        <dis:Add xmlns:dis="http://www.sap.com/SBO/DIS">
          <Service>InvoicesService</Service>
          <Document>
            <DocType>dDocument_Items</DocType>
            <HandWritten>tNO</HandWritten>
            <DocDate>2010-02-08</DocDate>
            <DocDueDate>2010-02-08</DocDueDate>
            <TaxDate>2010-02-08</TaxDate>
            <VatDate>2010-02-08</VatDate>
            <CardCode>NPI</CardCode>
            <Comments>test di-server soap message 1</Comments>
            <DocumentLines>
              <DocumentLine>
                <ItemCode>TRC</ItemCode>
                <Quantity>1</Quantity>
                <Price>1000</Price>
                <TaxCode>OVAT</TaxCode>
                <VatGroup>OVAT</VatGroup>
                <TaxLiable>tYES</TaxLiable>
                <WTLiable>tYES</WTLiable>
              </DocumentLine>
            </DocumentLines>
            <WithholdingTaxDataCollection>
              <WithholdingTaxData>
                <WTCode>C140</WTCode>
                <TaxableAmount>1000</TaxableAmount>
                <WTAmount>100</WTAmount>
              </WithholdingTaxData>
            </WithholdingTaxDataCollection>
          </Document>
        </dis:Add>
      </env:Body>
    </env:Envelope>
    OVAT rate above is 10%.
    The withholding tax code C140 is setup as
    rate=10,
    Category=Payment,
    Base Type=Net,
    % Base Amount = 100,
    Rounding Type = Commercial Values.
    We are using the New Zealand/Australia localization in SAP B1 2007A PL49.
    The above code can be successful only if I set the <WithholdingTaxDataCollection> node to:
            <WithholdingTaxDataCollection>
              <WithholdingTaxData>
                <WTCode>C140</WTCode>
                <TaxableAmount>0</TaxableAmount>
                <WTAmount>100</WTAmount>
              </WithholdingTaxData>
            </WithholdingTaxDataCollection>
    setting TaxableAmount equal to 0 which is not desired.
    Can anyone extend me some help, please?
    Thanks.

    Albert,
    Did you try adding this via the DI API and not the DI Server?  Do you get the same error?  Please see this SAP Note ...
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=0001303019
    Eddy

  • Sales return against invoices with batches.

    01.11.2010
    Hi friends,
    We are using BOM for materials. During delivery batches are determined and in the invoice i have the main material with zero quantity and zero value,  followed by the lines with the batches determined and the components.
    In case of returns i want to copy each of the batch line followed by the corresponding BOM quantity.  For eg. if the delivery quantity was 50 and 3 batches were determined of 10,15,25 then in the sales return i want the line with the batch quantity 10 and the components, followed by the batch line with quantity 15 with their components and finally the quantity 25 followed by the components for 25 nos. How can this be achieved.   Please suggest.
    Regards,
    Uday

    Hi
    You have to create your own data transfer routine for this. This routine is to be used in the copy control from invoice to order.
    Regards,
    Torben

  • Invoice posted in later date

    Dear all,
    All Invoices raised on 10.10.09(Saturday) get posted in 12.10.09(Monday),What may be reason for it ?
    How to solve the problem in future ?
    Edited by: Jeyakanthan A on Oct 12, 2009 10:29 AM

    Jeyakanthan A wrote:Hi Jeyakanthan,
    >
    > All Invoices raised on 10.10.09(Saturday) get posted in 12.10.09(Monday),
    Is it happened only for 10.10.09 (Saturday)? Or is it happening for all Billing documents created on Saturdays & Sundays?
    Please check that in the system to isolate the issue.
    If same is happening for all Billing documents created on Saturdays & Sundays, then it has to be with the Calendar settings.
    Go to below IMG Path:
    SAP NetWeaver -> General Settings -> -> Maintain Calendar
    Check SAP help documentations available there in the node,  if your not familiar with Calendar settings.
    It has very good information
    Best regards,
    Anupa

  • ATP check against delivery with multiple plants

    Hi all,
    we have R/3 4.6c and APO 3.1 systems, this topic is related to ATP functionlity.
    Our Existing ATP Practice in R/3:
    1.sales are delivered via several Distribution Centers  (DC).
    2.The right DC is determined by a delivering plant which chosen during the order creation.
    3.In case of ATP no planned receipts are taken into  account.
    4.When a product is not available at the determined DC it has to be checked manually if in any other DC is stock available which can deliver the customer in stead of the original DC.
    5.If so the customer order (single order or scheduling agreement) has to be changed manually and the delivery can be created for the new chosen DC.
    6.ATP is done during a delivery run, which happens 2 to 3 times a day.
    7.Deliveries are only created for those orders where free stock is available.
    Expectations from APO GATP:
    At this point of time gATP should check in case of non available stock, is there an alternative DC available?
    Is there enough stock available in the alternative DC to create the delivery?
    Are all parameters available to be able to deliver this customer from the alternative DC?
    In case everything is ok the order should be changed (delivering plant) and the delivery for the alternative DC needs to be created.
    To avoid confusion order management people of the alternative DC have to be informed about that change.
    It is grateful if any one look into this and suggest the solution in gATP?
    And for better solution one can expect maximum reward points
    Thanks in advance
    -RK

    Hi Ramkrishna,
    As hemant rightly said we can do this with the help of RATP. But I think it will not take CTP scenario for planed orders as RATP is not compatible with CTP.
    Rules can be set in rule maintainence. And as I understand u need only location substitution. Do remember to set rule type as "chain"
    And if product is not available at alternate DC and if u want to start production (by triggering PPDS) then u can set this instructions in location determination activity.
    Also now if u want the alternate DC to deliver the product then check the "create subitem" mark in check instructions. This will create subitem in sales order and will show delivery plant as the DC where product is available
    hope this helps!

  • Error: A previous document of this type has been created with later date

    hi
    when i am adding invoice with a particular date.
    and if i am adding  another invoice for same customer with date previous to the first one i am getting this error
    pls tell the error were i have made and how to slove the error

    Om,
    Pleae check the following ...
    Marketing document with earlier posting date not added
    Symptom
    Error message: 'A previous document of this type has been created with a later date.' and the document is not added.
    Other terms
    AR, AP, invoice, credit memo, reserve invoice, wizard, document, generation, past, previous, posting date, settings, initialisation, SAP Business One
    Reason and Prerequisites
    Business requirement that marketing documents with an earlier date than the current system date are entered.
    Solution
    Under Administration -> System Initialisation -> Document Settings -> Tab 'General' is a tickbox 'Block Documents with Earlier Date'.
    If this box is ticked, the error message 'A previous document of this type has been created with a later date.' is received and the document cannot be added. This affects the following documents:
    AR and AP Invoice
    AR and AP Credit Memo
    AR and AP Reserve Invoice
    If the box is unticked, the system displays the message: 'A previous document of this type has been created with a later date. CONTINUE or CANCEL.' If 'Continue' is chosen, the document can be added.
    This setting will also affect documents to be processed by the 'Automatic Summary Wizard'.
    HTH,
    Eddy

  • MM-Check Double Invoice functionality for Vendor Invoices

    Dear All,
    How Check Double Invoice functionality for Vendor Invoices can be implemented in SAP?
    We have implemented Check double invoice with the standara sttings for it however if i give my referenece text differently it will aloow me to post double invoices and against vendor open items are shown for payment?
    Is there any other efficient way to do it?
    Thanks and Regards
    Shrinivas

    dear SAPian friend,
    go through the below link and you will find the solution with the screenshots.
    http://sapfunctional.com/MM/Duplicate/Invoices.htm
    U can also do the setting using the SPRO t-code:-
    path is
    >>SPRO
    >>SAP Reference IMG
    >>Materials Management
    >>Logistics Invoice Verification
    >>Incoming Invoice
    >>Set check for duplicate invoices

  • Automaically load data in payment against invoices in payable

    Dear Experts
    My scenario is following
    Suppose I have two
    hundred invoices then I have to issue 200 checks against these invoices, Its means that
    I have to put manual entry two hundred times for two hundred checks issues, I like to avoid to put two hundred time manualy in payments
    and want to upload data automatically for two hundred checks in payments form against two hundred invoices.
    Is there any API or open API?
    Thanks

    Hi Sharma,
    suppose I have 100 invoices, they had same same supplier type with same pay order with invoice number 1..100 in
    order but supplier names are different , and want to issue 100 check for each invoice, I want to issue checks
    of the same bank and branch, so I want to upload these data of 100 invoices automaticaly in payment form, Just
    need to know any oracle built in procedure,concurrent program or api etc, If this can not help then
    I like to writhe procedure to insert data into payments form, but I need to know the correct tables to insert payments
    base on these invoices.
    I shall be very thankful of your kind help.
    once again I want to clear my logic, I want to avoid manualy entry for 100 invoices, and these invoices are with same
    pattern supplier type and are in order.
    Thanks

  • Tcode FV60 with ECC 6.02 does not check duplicate invoices

    Hi,
    We use FV60 top enter all invoices.  We have config (under MM) for duplicate invoice check against company code and "ref field" only.  When we enter an invoice with the same ref field value, it gives error message as expected.  However, when we change the date, the error message is gone and we are allowed to create the invoice and post the invoice.  This is not desireable and behaves very differently than tcode MIRO. 
    Is there any solution to have tcode FV60 perform the same checks, look to the same config for duplicate invoices in SPRO as MIRO and not allow for invoice creation if the "ref field" is identical?

    Hi all,
    Any solution on this..  Even we have the same kind of issue in our organization.  I am also trying various ways.  Plz help me if anyone has found the solution for this.  If I get something, i will update.
    Regards

  • PO/ S.Location and GR msg check box in 'delivery/invoice' tab of header dat

    Hi all,
    Under which case the below 2 fields are required to b filled while creating a PO apart from making them mandatory fieds in document type settings.
    1. GR msg check box in 'delivery/invoice' tab of header data
    2. Storage Location data in item details
    in me59n, system unable process p.req to PO becoz it is mandatory to fill these two fields.

    Hi,
    1. GR message check box issues message to the buyer after every the goods receipt against the PO.
    Message type has to be configured for this functionality.
    2. If you are managing stock of material at storage location level , then you will need to maintain this at PO item level.
    Regards,
    Maheshwari

  • R11.0.3: An Invoice with future dated apyment data flow

    제품 : FIN_AP
    작성날짜 : 2003-11-18
    R11.0.3: An Invoice with future dated apyment data flow
    ===============================================
    PURPOSE
    Future Dated Payment Term을 사용하는 Invoice의 Data Flow에 대해 살펴보도록 한다.
    Explanation
    accounting rule = accrual
    .allowed future dated payment
    1. Create a standard invoice (invoice amount: 2100, item amount: 2100, payment term : future dated payment)
    And transfer it to GL.
    * ap_invoice_distributions_all
    accounting_date = 2003-11-11
    accrual_posted_flag = Y
    posted_flag = Y
    * ap_trial_balance
    accounting_date = 2003-11-11
    distribution_amount = 2100
    * 해당 data gl_interface table로 넘어감.
    2. Posting these transferred journals in gl module
    * 해당 data가 gl_interface table에서 삭제 된 후
    * gl_je_lines
    accounted_dr = 2100 charge
    accounted_cr = 2100 liability
    3. Create a payment against this invoice with mature date = 12-nov-2003 and then transfer it to gl
    * ap_invoice_payments_all
    accounting_date = 2003-11-11
    accrual_posted_flag = 'N'
    posted_flag = 'N'
    future_pay_posted_flag = 'Y'
    * ap_payment_distributions_all
    line_type_lookup_code = 'CASH'
    * ap_trial_balance
    accounting_date = 2003-11-11
    payment_amount = 2100
    * ap_checks_all
    status_lookup_code = 'NEGOTIABLE'
    4. Posting these payment journals in gl module
    * 해당 data가 gl_interface table에서 삭제 된 후
    * gl_je_lines
    accounted__cr : 2100 future pay
    accounted_dr : 2100 liability
    5. Clear this payment and then transfer to gl
    Future dated payment 이고 Cash Management 를 사용하면 Cash Management 에서
    Bank Reconcilation을 해주시면 됩니다.
    Cash Management 를 사용하지 않으실 때는
    "automatic clearing for future dated payment" 를 수행하여서 clear 를 해주어야 합니다.
    이번 test case에서는 cash managemnt를 사용하지 않고 automatic clearing for
    future dated payment 를 수행하여 clear 해주었습니다.
    * ap_checks_all
    status_lookup_code = 'CLEARED BUT UNACCOUNTED'
    Cash Management를 사용하지 않기 때문에 status가 위와 같이 나타납니다.
    Cash Management를 사용하면 option에 따라 status가 cleared나 reconciled로 변경 됩니다.
    6. Transfer these cleared payment to gl and posting in gl
    * 이 때에는 ap_trial_balance table에는 아무런 영향도 주지 않습니다.
    * ap_invoice_payments_all
    accrual_posted_flag = 'Y'
    posted_flag = 'Y'
    * gl_je_lines
    accounted_dr= 2100 future pay
    accounted_cr = 2100 cash
    Example
    Reference Documents
    N/A

    Rohini,
      Thanks for your answer; I was out for few days and hence the delay.
      What I am looking for is the complete usage model of the following ODS.
    1> 0BBP_SC     we have figured it out
    2> 0BBP_SCA    we have figured it out
    3> 0BBP_DOC    we have figured it out
    4> 0bbp_inv    we need help
         Looks like this can be populated from R3 using the following
    Data Source    Info Source                    ODS Object
    2LIS_02_ITM    2LIS_02_ITM                 0BBP_INV
    2LIS_02_HDR    2LIS_02_HDR                0BBP_INV
    5> 0BBP_DS     we need help
    6> 0bbp_po     we need help
        The same combination is also used to populate the 0BBP_PO as well. We suspect that 0BBP_DS will then be populated from both 0BBP_INV and 0BBP_PO. At least that what we though after activating the BC and reading the sap help on BC for SRM.
      We are doing a proof of concept and want to know all the ODS with data. We want to build an end to end (Shopping cart, approval, Doc flow, PO data with value, Invoice data with Value) and struggling to understand the model surrounding this three ODS ( 0bbp_inv, 0bbp_ds, 0bbp_po). Any help in this area will be appreciated.
    Thanks
    Arun

  • Double Invoice Check - Against the Delivery Note/ Bill #

    Dear All,
    I have a requirement here, Bit different from the Regular Double Invoice Check,
    I will receive the Material A, 10 different times, will do the GR 10 times & enter the Bill # & Challan # during GR. While posting the Invoice i want the system to check against which Bill # i am posting the invoice. Say during GR my Bill #s were 1 to 10. I receive the Invoice from my Vendor from 1 to 5 today, so i posted the invoice. After few days He will send a duplicate Invoice with Bill # as 5, & he will inform me that he lost original Invoice so he is sending the duplicate. As i have'nt posted Bill # 6 to 10, system will accept the Bill 5 also again. How can i avoid these things ?
    regds,
    CB

    Hi,
    Already I am maintaining these Bill # & Delivery Challan # during GR. My issue is during Invoice i want a check. In Invoice we have a reference field at header, If i am posting a single GR as a single invoice thats OK. But if I am posting more than 1 GR in single Invoice, where can i maintain the Bill # ? Any solutions pls ?
    regds,
    CB

  • Document Type with a later posting date

    Hi,
    We are on SAP B1 2005 PL50.
    We occasionally get the message " There is a document of this type with a later posting date" while posting AP invoices. It happens to some AP invoices only because other invoices get added even though the document is posted with a prior posting date then what is in existence
    Please advice, what could be causing this.
    Thanks
    Asif

    Hi Mohamed,
    If there is a document existing in the database with a posting date later       
    than the current one, this system message will pop up.                                                                               
    This system message works based on the following setting:                                                                               
    Under Administration -> System Initialisation -> Document Settings ->         
    Tab 'General' is a tickbox 'Block Documents with Earlier Date'.                                                                               
    If this box is ticked, the error message 'There is a document of this         
    type  with a later posting date.' is received and the document                
    cannot be added. This affects the following documents:                                                                               
    - AR and AP Invoice                                                           
    - AR and AP Credit Memo                                                       
    - AR and AP Reserve Invoice                                                                               
    If the box is unticked, the system displays the message: 'There is a          
    document of this type with a later posting date. CONTINUE or                  
    CANCEL.' If 'Continue' is chosen, the document can be added.
    It is not possible to turn this off message.       
    Hope it helps.                                  
    Jesper

Maybe you are looking for