EDI invoice and posting date

Hello,
We are implementing EDI invoice using BAPI_INCOMINGINVOICE_SAVE and MRBP (background engine).
We would like the posting date be set at the date when the invoice is posted. At the present time the posting date is set at the date when the invoice document is created from the EDI file.
We tried substitution rules (OBBH) but the field posting date (BUDAT) is not available for substitution.
We also plan to run a daily job which change the posting date of the planned and erroneous document (RBSTAT = 1 or 3) to the current date. But we do not find any BAPI which do it properly. As a result we plan to change the posting date directly in RBKP. Do you think this operation is safe and will not generate inconsistencies?
Or do you have any idea to solve our problem?
Thanks
Pascal

the documentation clearly says it can chnage invoice which is 'onhold'.
FU BAPI_INCOMINGINVOICE_CHANGE
Short Text
Invoice Verification: Change Provisional Invoice
Functionality
You can use this method to change provisional invoice documents. Provisional invoice documents have the status:
'On hold' or
'On hold (from parking)' or
'Parked' or
'Parked as complete' or
'Parked and released'
With regard to the reference document categories to which an invoice can relate, this method offers the following functionalities:
If you do not make any changes to the items of an invoice document, the originally chosen reference to a document category is retained.
If a change is made to items of an invoice document (i.e. if you supply the method with information via the Itemdata table, the purchase order is used as reference document category

Similar Messages

  • MIR7 - Invoice and Posting date must be = PO Date

    Dear All,
    In MIR7 Invoice Date and Posting date is allowed prior to PO date.
    e.g.
    PO Date : 21.05.2010
    We can make MIR7 in back date i.e. 20.05.2010 or any back date.
    How to restrict this.
    We don't want to allow invoice date and Posting date < PO Date.
    Thanks and Regards,
    Nirav

    Please check this answered link:
    posting date
    Invoice posting not permissible after posting MIGO
    validation
    miro problem
    Edited by: Afshad Irani on May 23, 2010 10:39 AM

  • Posting of cancelled Invoice after posting date is over

    Hello Experts,
    I am stuck up with a situation and as such seek your help.
    A invoice was generated and the subsequent accounting document was also cleared. Now after the posting date was over, someone cancelled the invoice by T.code VF11 and as expected it didnt get posted .The document flow showing is as per below :
    Order - open
    Invoice - completed
    Accounting Document - Cleared
    Cancel Invoice - Open
    Now, the business and their audit policies do not allow the client to cancel the invoice in back date ( within the posting period).
    What are the options do we have to tackle the situation.
    Joy

    The issue has been temporarily addressed by changing the posting date.
    However, now the client wants us to make an ABAP development so that no user is able to cancel the invoice after posting date is over. Now for that I have the following issues. Can someone please help me out in this.
    The basic process details I am following is as per below:
    For Transaction Code VF11 (i.e for Cancellation of Invoice) , when the invoice number which is subject to cancellation is provided, the System should search in VBRK table for the following :-
    1)The System will at first search whether the entry exists or not. If the Entry is not valid then it should give an message u201C Document xxxxx does not Existu201D.This is in line to the existing practice.
    2) If the Document number is valid then it will go to the billing date field and  will fetch the value from the VBRK table . Then it will match  whether the value fetched (i.e. this Invoice date)  is in present posting period or not. The system can find the posting period from the table V_T001B.
    a.If  the  Invoice date lies in the present posting period then the system will allow the cancellation document to be saved. This is in line to the existing process.
    b.If the Invoice date lies beyond the present posting period then the system will not allow to save the cancellation of the Invoice with a pop up message of u201C The Document number subject to cancellation do not lie within the present posting periodu201D .
    Now We have looked both the tables, from VBRK we will get Doc# and Billing date(FKDAT) but when we select Posting Date from table T001B( Permitted Posting Periods) there is some issue.
    1.  What will be the condition for selecting records from T001B table.Since there is multiple key fields
        RRCTY (Record Type) ,
        BUKRS (Posting Period Variant) ,
        MKOAR (Account Type or Masking)
        BKONT (To Account). 
    So, to get unique record what will be the value of this key fields. Is there any relationship with VBRK table ? 
    2.  Which field I have to consider as Posting Date or Period. Because there are many fields related to Posting period.

  • MIRO(Invoice Verification) posting date is lesser than MIGO(Goods Receipt)

    MIRO(Invoice Verification) posting date is lesser than MIGO(Goods Receipt) posting date.
    Explanation:
    Miro sholud be posted after the GRN has posted. It means that the Posting date of Miro should be greater than or equal to the Posting date of Migo. But I am facing the issue that I can able to post the Miro before the Migo date..
    For example:  I have posted the Migo(Goods receipt) document with the posting date u2013 10.8.09 and at the same time I can also able to post the Miro(Invoice Verification) posting date as u2013 5.08.09. This is should not be allowed . Kindly give me the solution. Is there any options in SAP standards to restrict this type of Postings(without using user exit).
    regards
    Varadharaj

    Hi
    you  need to use BADi for this INVOICE_UPDATE
    you can give logic as whil;e MIRO system will compare posting date with MIGO doc , then create a Z error msg in se91 nad assign it in that badi
    take help of ABAPer, check following link
    [LINK |GR date lesser than the PO date, the system should show an error message.;

  • AP- Why exchange rate type between Post invoice and Post payment is differe

    AP- Why exchange rate type between Post invoice and Post payment is different ?
    Hello,
    I have question
    when post AP invoice , document type KR
    document date = 11.12.2009
    posting date = 31.12.2009
    entry date = 05.01.2010
    this document using exchange rate type B (standard translation at bank selling rate) on 31.12.2009 (use posting date )
    but when post payment for above document,document type ZP
    document date = 25.06.2010
    posting date = 25.06.2010
    entry date = 24.06.2010
    this document using exchange rate type M (standard translation at average rate) on 23.06.2010
    please answer
    why do post invoice and post payment use different exchange rate type?
    and why at payment donot use posting date for get exchange rate ?

    Nanas,
    Sorry if im not  being clear...
    My point is: the difference rates customization for payments is done at FBZP.
    At Paying Company Codes, you have 4 flags for exchange rates differentes.
    At Control Data look:
    *Do not Post any Exchange Rate Differences:
    If the indicator is not set, the difference between the exchange rate at the time of posting and the exchange rate at the time of payment is determined for items which are posted in foreign currency. The payment program uses the translation rate in the currency table in the system for this purpose.
    *No Exchange Rate Differences for Partial Payments:
    Has the effect that the payment program for partial payments (requests for payment using transaction F-59) does not post exchange rate differences.
    *Processing of Bill of Exchange Payments:
    *Separate Payment for each Payment Reference
    Regards
    Bruno

  • GR/IR from miro document and posting date.

    Hi experts,
    Is there any proper way to selecting data.
    My purpose is getting GR/IR on Miro Document and Posting date basis.
    THE CODE IS.
    TABLES : bkpf, rseg, bseg.
    DATA : BEGIN OF it_bkpf OCCURS 0.
            INCLUDE STRUCTURE bkpf.
    DATA : bbelnr TYPE bkpf-belnr,
          bgjahr TYPE bkpf-gjahr.
    DATA : END OF it_bkpf.
    *data : it_bkpf like bkpf OCCURS 0 WITH HEADER LINE.
    DATA : it_rseg LIKE rseg OCCURS 0 WITH HEADER LINE.
    DATA : it_bseg LIKE bseg OCCURS 0 WITH HEADER LINE.
    DATA : bbelnr TYPE bkpf-belnr.
    DATA : bgjahr TYPE bkpf-gjahr.
    DATA : bawkey TYPE bkpf-awkey.
    data : dmbtr1 type bseg-dmbtr.
    data : dmbtr2 type bseg-dmbtr.
    PARAMETERS : p_budat LIKE bkpf-budat.
    SELECT SINGLE * FROM bkpf
      WHERE budat = p_budat
      AND blart = 'RE'.
    WRITE :/ bkpf-awkey(10).
    WRITE :/20 'I/R'.
    WRITE :/20 sy-uline(30).
    SELECT * FROM bseg
      WHERE belnr = bkpf-belnr
        AND gjahr = bkpf-gjahr.
      IF bseg-shkzg ='H'.
        bseg-dmbtr = bseg-dmbtr * -1.
      ENDIF.
        dmbtr1 = dmbtr1 + bseg-dmbtr.
      WRITE :/20 bseg-belnr, bseg-dmbtr.
    ENDSELECT.
    bbelnr = bkpf-awkey(10).
    bgjahr = bkpf-awkey+10(4).
    SELECT SINGLE * FROM rseg
      WHERE belnr = bbelnr
      AND gjahr = bgjahr.
    SKIP 2.
    CONCATENATE rseg-lfbnr rseg-lfgja INTO bawkey.
    SELECT SINGLE * FROM bkpf
      WHERE awkey = bawkey.
    WRITE :/20 'G/R'.
    WRITE :/20 sy-uline(30).
    SELECT * FROM bseg
      WHERE belnr = bkpf-belnr
        AND gjahr = bkpf-gjahr.
      IF bseg-shkzg ='H'.
        bseg-dmbtr = bseg-dmbtr * -1.
      ENDIF.
        dmbtr2 = dmbtr2 + bseg-dmbtr.
      WRITE :/20 bseg-belnr, bseg-dmbtr.
    ENDSELECT.
    dmbtr1 = dmbtr1 - dmbtr2.
    skip 2.
    write :/ dmbtr1.

    self solved

  • Default key date, Document date and posting date needs to be changed automa

    Hi Experts,
    The user wants to create a variant for Foreign currency valuation, wherein the default key date, Doc date and Posting date needs to be changed every month automatically. Is it possible?
    Please let me know your thoughts.
    Warm regards,
    Murukan Arunachalam

    Hi
    Please follow this process.
    Only specify fields that should be changed
    Select these fields by entering an X in the checkboxes
    Enter a U in the UPDATEFLAG field
    Always specify key fields when changing the data, including in the checkboxes
    The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
    Maintain quantities and dates in the schedule line data.
    1. Minimum entry:
    You must enter the order number in the SALESDOCUMENT structure.
    You must always enter key fields for changes.
    You must always specify the update indicator in the ORDER_HEADER_INX.
    2. Commit control:
    The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.

  • Difference between Parked invoice and posted park invoice.

    Dear All,
    I am trying to create a new program to extract the invoices posted by MIRO and MIR7.  I have no problem to find invoices posted by MIRO in RBKP and RSEG.
    However, as currenty one user will use MIR7 to park invoices and another user will use MIRO to post the invoices, I don't know how to sparate the parked invoice and posted park invoice. C's I have found that the parked not posted invoice and posted park invoice were all displayed in RBKP with transaction code MIR7.
    Thank you very much
    Emma

    Hi,
    *Park*
    If the Invoice document is missing some information that is required for posting. In this case we will park the document. Here some preliminary checks will be performed.  Balance might not be zero.But in this case updates were performed.
    *Post*
    The invoice was posted online and verified as being correct(Balance must be Zero). Updates were made.
    Please use RBKP-RBSTAT field to find out the different type os status.
    I hope this helps.
    Regards
    Ravinagh Boni

  • FA-retirement-Asset value date and posting date are not in same fisc year

    Hello,
    I would like to post retirement in the new fiscal year but with asset value date in the previous year so that NBV is calculated correctly. It is not possible neither in ABAON nor in ABAVN with any transaction type.
    I always get message 'Asset value date and posting date are not in same fiscal year'.
    Is there any way how to handle this?
    Thank you,
    Jan

    Hi,
    I have tried this but the settings of our Depr keys works in the way. That if you use asset value date in the new month it will calculate depreciation for the whole month.
    This means if I retire with asset value date 31.12.2008 - NBV will be calculated as at 31.12.2008.
    If I retire with asset value date 1.1.2008 - NBV will be calculated as at 31.1.2009.
    Thank you anyway!

  • Asset value date and posting date are not in same fiscal year

    Hi,
    Our business user has created an asset under an incorrect asset class, which he is trying to transfer to a new asset whcih was created under correct asset class. However system is restricting user with the error message "Asset value date and posting date are not in same fiscal year". Can you please advise me how we can proceed further with this error.
    Regards,
    Asam.

    Hi,
    To transfer one asset to another asset within a company code can be done through ABUMN only.
    While doing this transfer you have enter the document date, posting date, and value date for the transaction, but all these dates should be in same fiscal year only.
    In your case you must have been entered the dates for asset value date and posting date , and these two dates are in diff financial years.
    Please make sure that both the dates are in same FY.
    Hope this will fix your issue.
    Thanks,
    Srinu

  • GR document and posting date issue for initial stock upload are overidden

    Hi all
    Loading initial stock into the system using standard idoc message type MBGMCR and basic type MBGMCR02.
    We are trying to post the intial stock upload with posting and document dates in past with this idoc. The Idoc is accepted with these dates but while posting the system is overiding these dates and posting the document with system date. Any clue as to what is happening?
    Regards,
    Amit

    Hi Jurgen
    I am aware about the posting being possible till the last period.
    But the system over-riding the posting and document dates in the IDoc even if I chose previos day's date in the current period. The dates in the IDoc are correct to be in the past. The IDoc is accepted by the system with the document and posting dates in the past.
    But dates in the document after posting are system dates. Very unsual. Please let me know the reasons.
    Thanks for the reply.
    Cheers,
    Amit

  • Changing document date and posting date by SE16N

    Hi All,
    an user has posted some customer documents (with tax codes) with wrong document date and posting date.
    I have to modify these data by se16n.
    In which tables I have to fill in?
    Thanks
    Gandalf

    Hi,
    It is not advisable to change the document date and posting date. Instead, try to reverse the document and post the correct one.
    Regards,
    Jigar

  • Vendor 800040 and posting data have different withholding tax types

    HI
    need some help..
    i ve created the lease in contract but unable to activate it... getting the following error
    Vendor 800040 and posting data have different withholding tax types...
    how to solve this issue,,

    Hi,
    could you please add the error message ID and error message number.
    Thank you.
    Regards, Franz

  • CIN - Excise Invoice - Cancel Reversed Invoice and Post New Invoice

    I need to Cancel the Excise Invoice posted for return delivery 122 document, and post a new one.
    The client says he has already cancelled the invoice, and posted another one.
    Now, same return delivery document has 2 Excise Invoices. But the one I am seeing in Excise Invoice tab of MIGO Display is the Excise Invoice with Reversed status.
    When I display the reversed invoice in J1IS - it says "Document is Reversed". Does that mean Cancelled?
    We need MIGO to show us the new Excise Invoice for this return docuemnt, not the reversed one. Kindly help.

    "Have you created Excise invoice for other movements (122) in J1IS and posted the same through J1IV."
    Yes. Invoice No. 2391 is created and posted for return delivery document 5000052046
    "What did you see in 122 Material document header in Excise tab Status after cancellation of Exicse invoice?"
    For 122, the first invoice # 2317 was never cancelled. It has reversed status. "Document is reversed" is showing in Invoice Display through J1IS. Also, in MIGO for return delivery document 5000052046 - STILL the reversed invoice # 2317 is mentioned. Although 2391 is the new invoice posted for the same return delivery document.
    "Have you tried creating J1IS again after canceling the Excise invoice? What systems says then"
    No invoice has been cancelled yet. I don't know how to cancel without cancelling the 122 Mvt material document.

  • MIGO -- document date and posting date

    Dear all,
    When i call Tcode MIGO then by default it is picking document date and posting date as 25.8.9
    I want document date as current date.....
    guide me

    Check your System date..
    also check  u have the option in the header - seting-default values in MIGO Trxn

Maybe you are looking for