Invoice Date as default to calculate tax in MIRO

Hi,
I need to make Invoice date as default to calculate tax in MIRO.Can anybody suggest me User-Exit or BADI to do the same?
i need to calculate the tax according to Invoice date and not system date (posting date).

hi!
  You can set transaction variant for your requirement using T.code SHD0 and that too only if the requirement is needed for all LIV postings. In SHD0 you can enable the tick and set the field in display mode. If the requirement is not for all postings then you copy the MIRO trtansaction USING T.Code OMW9 and set the transaction variant for that new t.code. But if you want to create a new t.code its upto you to check all other requirements.
Reward if useful.
Yuvi.

Similar Messages

  • "Calculate tax" on MIRO/FB60 to be checked by default

    Hi,
    Can anyone tell me if it's possible through configuration to make the "Calculate tax" box on MIRO/FB60 checked by default and grayed out (user isn't allowed to uncheck it).
    Regards,
    Yathi P

    Hi ,
    the problem that you have stated can be resolved by creating a screen varient for the same , where in you can make the calculate tax as only output mode .
    for this execute the t code SHD0 , enter the T code and create a screen varient for the same .
    do revert back in case you have any queries in creating a screen varient .
    Cheers ,
    dewang

  • Could I Manually calculate tax in MIRO

    Dear
    1， We know that we can use auto-calculate tax function in Tcode MIRO.
    2， But there is a little difference of tax between actual invoice and auto-calculated by SAP.  Meanwhile the tax field is disable if we use auto-calculate tax function. So, we want to manually enter this tax instead of auto-calculated. and then add one adjustment item. this way is OK?
    Regards
    Henry

    While entering MIRO, please uncheck auto tax calculation check box, then system will allow you to put manually tax amount.
    Hope this helps.

  • Calculate tax in MIRO

    I want "Calculate tax" check box in miro to be ticked and in display mode.
    How to do it?

    hi!
      You can set transaction variant for your requirement using T.code SHD0 and that too only if the requirement is needed for all LIV postings. In SHD0 you can enable the tick and set the field in display mode. If the requirement is not for all postings then you copy the MIRO trtansaction USING T.Code OMW9 and set the transaction variant for that new t.code. But if you want to create a new t.code its upto you to check all other requirements.
    Reward if useful.
    Yuvi.

  • MIRO field INVOICE DATE must be blank in the initial MIRO

    Dear friends ,
    I'd like to know how to make the field INOVICE DATE  at tab Basic Data in MIRO transaction to come blank.
    The field is being populated with the current date.
    Does anyone knows if the field INVOICE DATE(document date) has some parameter or customizing to make it blank in MIRO ?
    best regards,
    Alessandro

    Hello,
    You may be able to do this with method HEADER_DEFAULT_SET of BADI MRM_HEADER_DEFAULT. You can also do this with transaction variant.
    Thanks,
    Venu

  • Tax code on the basis of Invoice Date in MIRO

    Hi Gurus!
    Tax rate change from 12.5% to 15 % is due on 1st October in NZ._________________
    Client requirement is that in MIRO transaction w.r.t. PO instead of the tax code being picked up from PO, the Tax code should be picked up depending upon the Invoice Date. _____________
    For Eg. Tax rate changes from 12.5% to 15% on 1/Oct/2010,
    Invoice Date = 20/Sep/2010, Posting Date = 20/Sep/2010, Tax Code = H1 (12.5%)
    Invoice Date = 20/Sep/2010, Posting Date = 01/Oct/2010, Tax Code = H1 (12.5%)
    Invoice Date = 01/Oct/2010, Posting Date = 01/Oct/2010, Tax Code = H3 (15%)
    Is there a way this can be achieved?
    Kind Regards,
    Mehul

    Hi Mehul,
    We just had such situation in Canada.
    It is recommended not to change the tax rate in the Tax code which is being used in open invoices because that could cause reporting and discount problems. And I am sure there will be open invoices with tax rates 12.5% come october 1. The solution is:
    Create a new Tax code in transaction code FTXP with rate 15%( effective date Oct 1 and set the same GL Tax account) everything as old tax code except for 15%  which will used for POs initiated from Oct1 onwards. For PO's prior to Oct 1. just use the same tax code with 12.5%.
    During MIRO the Tax code/rate  used in PO will be default,  you will have the option to go with old Tax code-12.5% or new tax code 15%.

  • The TermsDate of Invoice Headaer to defaulted to the invoice received Date

    The TermsDate of Invoice Header to defaulted to the invoice received Date. How can we acheive this. Please suggest
    current setup shows termsdate as sysdate

    I assume you are on R12. Pl follow the below steps.
    - Go to Payables system set up option in Payables responsibility.
    - Under Payment tab, change 'Term Date Basis' to 'Invoice Received'.
    Re-test the issue.
    Hope this helps.
    Tarun

  • The Invoice date should hold the GR date by default

    Hi SDners,
    I have a requirement.
    When the Billing is done in MIRO, the user wants the field  Invoice Date to be automatically populated with GR  Date.
    Guide me as to where i need to do the coding for the same.
    Should this be coded in the user exit?
    Regards,
    SuryaD.
    Edited by: SuryaD on Dec 16, 2009 8:53 PM

    Hi ,
    Obviously you have to use an user exit. Kindly search for the same on SCN.
    Regards
    Abhii

  • Calculate Tax using BAPI_SALESORDER_SIMULATE

    Hi All,
    I am doing a proof of concept to get some data from the third party tool and calculate tax using BAPI_SALESORDER_SIMULATE.
    I am gonna wrap this BAPI in a web service and pass the calculated tax amount back to the third party. I want to pass the default values for all the fields except for the credit card parameters.
    Can some one help me with the default values that I can pass to this BAPI to check how it works.
    Thanks,
    Guru.

    Hi Anurita,
    How did you solve this issue? Do you also have an example code?
    I am trying to enable auto vat calculation for vendor invoices.
    Many Thanks!
    Kenan

  • Reg. Tax calculate tick in MIRO

    Dear Experts
    During MIRO if I tick the Tax calculation tab tax is not calculated but tax is calculate if I put either VAT or Excise any one in PO,if I use both taxs the tax calculation tab is not working in MIRO,Pls help me and then in MIRO simulation entry the entries are like this
    1     K                    RAJA DESIGNERS / 641687 COIMBATORE          0.00      INR                                                   
    2     S     504007     GR/IR Clearing - Poly Bags          104.12      INR     4500052909     10
    G/L for vendor is not there,how to assign ?
    thanks in advance
    Rajakumar.K

    please check
    1.schema group of vendor in xk02
    2.in me11 maintain the correct tax code in purchasing data
    3.J1id table should be properly maintained ie material data and vendor data related to excise
    4.maintain condition record in FV11
    5.tax code can be maintained or changed in po  to. do that also
    6.during migo go for capture invoice only. check item level screen here correct material type and chapter id picks correct excise rates .
    7.post the excise invoice using j1iex after checking all entries
    8.in miro check the calculate tax box here the excise duty and tax rates will be calculated as per your settings
    even  after this you are getting the above problem please let me know

  • Calculate tax item field name in bapi .. bapi_acc_document_post

    Hello Friends,
    Im using Bapi>> Bapi_acc_document_post to post vendor and customer invoices, im not getting mapping field for the "calculate tax item(checkbox)" technical name is xmwst in any of the bapi strucuture.
    please tell me in which bapi structure we have to pass this field so that the tax amount should get calculated automatically.
    regards,
    Sunny

    You can try the Financial Posting Interface (FIPI).
    *=======================================================================
    CONSTANTS:
    *=======================================================================
                c_typehead  TYPE stype_pi VALUE 'K',
                c_typepos   TYPE stype_pi VALUE 'P',
                c_waers     TYPE waers    VALUE 'EUR',
                c_blart     TYPE blart    VALUE 'ZN',
                c_debit     TYPE bschl    VALUE  '40',
                c_credit    TYPE bschl    VALUE  '50',
                c_inddebit  TYPE shkzg    VALUE  'S',
                c_indcredit TYPE shkzg    VALUE  'H'.
    *===================================================================
    FORM append_ftpost
    *===================================================================
                      USING    p_stype   TYPE stype_pi
                               p_count   TYPE count_pi
                               p_fnam    TYPE bdc_fnam
                               p_fval    TYPE any
                      CHANGING pt_ftpost TYPE tt_ftpost.
      DATA: ls_ftpost LIKE LINE OF pt_ftpost.
      CLEAR ls_ftpost.
      ls_ftpost-stype = p_stype.
      ls_ftpost-count = p_count.
      ls_ftpost-fnam  = p_fnam.
      ls_ftpost-fval  = p_fval.
      APPEND ls_ftpost TO pt_ftpost.
    ENDFORM.                    "append_ftpost
    *===================================================================
    FORM post_document
    *===================================================================
                        USING    p_bukrs   TYPE bukrs
                                 p_gjahr   TYPE gjahr
                                 p_monat   TYPE monat
                                 p_tip     TYPE zga_nomtipcont
                                 p_saknr   TYPE saknr
                                 p_bktxt   TYPE bktxt
                                 pt_pos    TYPE tt_pos.
      DATA: lt_blntab TYPE tt_blntab,
            lt_ftpost TYPE tt_ftpost,
            lt_fttax  TYPE tt_fttax,
            ls_blntab LIKE LINE OF lt_blntab.
      REFRESH: lt_blntab,
               lt_ftpost,
               lt_fttax.
      CALL FUNCTION 'ENQUEUE_EZGA_NOMLOG'
        EXPORTING
          bukrs          = p_bukrs
          gjahr          = p_gjahr
          monat          = p_monat
          tipcont        = p_tip
          _wait          = 'X'
        EXCEPTIONS
          foreign_lock   = 1
          system_failure = 2
          OTHERS         = 3.
      IF sy-subrc IS NOT INITIAL.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
      PERFORM fill_bkpf USING    p_bukrs p_gjahr
                                 p_monat p_bktxt
                        CHANGING lt_ftpost.
      PERFORM fill_bseg USING    p_saknr p_bktxt
                        CHANGING pt_pos lt_ftpost.
      CALL FUNCTION 'POSTING_INTERFACE_START'
        EXPORTING
          i_function = 'C'
          i_mode     = 'N'
          i_update   = 'S'.
      CALL FUNCTION 'POSTING_INTERFACE_DOCUMENT'
        EXPORTING
          i_tcode  = 'FB01'
        IMPORTING
          e_msgid  = sy-msgid
          e_msgno  = sy-msgno
          e_msgty  = sy-msgty
          e_msgv1  = sy-msgv1
          e_msgv2  = sy-msgv2
          e_msgv3  = sy-msgv3
          e_msgv4  = sy-msgv4
          e_subrc  = sy-subrc
        TABLES
          t_blntab = lt_blntab
          t_ftpost = lt_ftpost
          t_fttax  = lt_fttax.
      IF sy-subrc IS NOT INITIAL.
        MESSAGE i021(zga_nom).
      ELSE.
    *  Grabación en tabla de log y mensaje
        READ TABLE lt_blntab INTO ls_blntab INDEX 1.
        IF sy-subrc        IS INITIAL AND
           ls_blntab-belnr IS NOT INITIAL.
          PERFORM insert_log USING p_bukrs
                                   p_gjahr
                                   p_monat
                                   p_tip
                                   ls_blntab-belnr.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                  WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ELSE.
          MESSAGE ID sy-msgid TYPE 'I' NUMBER sy-msgno
              WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
      ENDIF.
      CALL FUNCTION 'POSTING_INTERFACE_END'
        EXCEPTIONS
          session_not_processable = 1
          OTHERS                  = 2.
      CALL FUNCTION 'DEQUEUE_EZGA_NOMLOG'
        EXPORTING
          bukrs   = p_bukrs
          gjahr   = p_gjahr
          monat   = p_monat
          tipcont = p_tip.
    ENDFORM.                    " post_document
    *===================================================================
    FORM insert_log
    *===================================================================
                    USING p_bukrs TYPE bukrs
                          p_gjahr TYPE gjahr
                          p_monat TYPE monat
                          p_tip   TYPE zga_nomtipcont
                          p_belnr TYPE belnr_d.
      DATA: lv_belnr TYPE belnr_d,
            ls_log   TYPE zga_nomlog.
      CLEAR: lv_belnr, ls_log.
      ls_log-bukrs   = p_bukrs.
      ls_log-gjahr   = p_gjahr.
      ls_log-monat   = p_monat.
      ls_log-tipcont = p_tip.
      ls_log-belnr   = p_belnr.
      SELECT SINGLE belnr INTO lv_belnr
        FROM zga_nomlog
        WHERE bukrs   = p_bukrs AND
              gjahr   = p_gjahr AND
              monat   = p_monat AND
              tipcont = p_tip.
      IF sy-subrc IS INITIAL.
        UPDATE zga_nomlog FROM ls_log.
      ELSE.
        INSERT zga_nomlog FROM ls_log.
      ENDIF.
    ENDFORM.                    "insert_log
    *===================================================================
    FORM get_posting_date
    *===================================================================
                          USING    p_gjahr TYPE gjahr
                                   p_monat TYPE monat
                          CHANGING p_date  TYPE dats.
      DATA: lv_date TYPE dats,
            lv_month TYPE tfmatage.
      IF p_monat <= '12'.
        CONCATENATE p_gjahr p_monat '01' INTO lv_date.
        CALL FUNCTION 'FIMA_END_OF_PERIOD_DETERMINE'
          EXPORTING
            i_date               = lv_date
            i_months             = '1'
          IMPORTING
            e_date_end_of_period = p_date.
      ELSE.
        CONCATENATE p_gjahr '1231' INTO p_date.
      ENDIF.
    ENDFORM.                    "get_posting_date
    *======================================================================
    FORM fill_bkpf
    *======================================================================
                     USING    p_bukrs   TYPE bukrs
                              p_gjahr   TYPE gjahr
                              p_monat   TYPE monat
                              p_bktxt   TYPE bktxt
                     CHANGING pt_ftpost TYPE tt_ftpost.
      DATA: lv_posting_date TYPE dats,
            lv_dats TYPE char10.
      PERFORM get_posting_date USING    p_gjahr p_monat
                               CHANGING lv_posting_date.
      WRITE lv_posting_date TO lv_dats.
      PERFORM append_ftpost USING    c_typehead '1'
                                     'BKPF-BUKRS' p_bukrs
                            CHANGING pt_ftpost.
      PERFORM append_ftpost USING    c_typehead '1'
                                     'BKPF-MONAT' p_monat
                            CHANGING pt_ftpost.
      PERFORM append_ftpost USING    c_typehead '1'
                                     'BKPF-BLART' c_blart
                            CHANGING pt_ftpost.
      PERFORM append_ftpost USING    c_typehead '1'
                                     'BKPF-BUDAT' lv_dats
                            CHANGING pt_ftpost.
      PERFORM append_ftpost USING    c_typehead '1'
                                     'BKPF-BLDAT' lv_dats
                            CHANGING pt_ftpost.
      PERFORM append_ftpost USING    c_typehead '1'
                                     'BKPF-WAERS' c_waers
                            CHANGING pt_ftpost.
      *PERFORM append_ftpost USING    c_typehead '1'*
                                     *'BKPF-XMWST'  'X'*
                            *CHANGING pt_ftpost.*
      PERFORM append_ftpost USING    c_typehead '1'
                                     'BKPF-BKTXT' p_bktxt
                            CHANGING pt_ftpost.
      PERFORM append_ftpost USING    c_typehead '1'
                                     'BKPF-XBLNR' p_bktxt+0(16)
                            CHANGING pt_ftpost.
    ENDFORM.                    "fill_bkpf
    *===================================================================
    FORM fill_bseg
    *===================================================================
                          USING  p_saknr   TYPE saknr
                                 p_bktxt   TYPE bktxt
                        CHANGING pt_pos    TYPE tt_pos
                                 pt_ftpost TYPE tt_ftpost.
      DATA: ls_pos      LIKE LINE OF pt_pos,
            ls_ftpost   LIKE LINE OF pt_ftpost,
            lv_item     TYPE buzei,
            lv_wrbtr    TYPE wrbtr,
            lv_saknr    TYPE saknr,
            lv_bschl    TYPE bschl,
            lt_poscont  TYPE TABLE OF zga_nompospost,
            ls_poscont  LIKE LINE OF lt_poscont,
            ls_poscontaux LIKE LINE OF lt_poscont.
      CLEAR: ls_pos, ls_ftpost.
      REFRESH lt_poscont.
      LOOP AT pt_pos INTO ls_pos.
        MOVE-CORRESPONDING ls_pos TO ls_poscont.
        APPEND ls_poscont TO lt_poscont.
      ENDLOOP.
      SORT lt_poscont BY saknr.
      lv_item = '002'.
      LOOP AT lt_poscont INTO ls_poscontaux.
        ls_poscont = ls_poscontaux.
        AT NEW saknr.
          CLEAR: lv_wrbtr,
                 lv_saknr,
                 lv_bschl.
        ENDAT.
        CASE ls_poscont-shkzg.
          WHEN c_inddebit.
            lv_bschl = c_debit.
          WHEN c_indcredit.
            lv_bschl = c_credit.
        ENDCASE.
        IF ls_poscont-saknr IS INITIAL.
          lv_saknr = p_saknr.
        ELSE.
          lv_saknr = ls_poscont-saknr.
        ENDIF.
        IF ls_poscont-indhkont = abap_true.
          lv_wrbtr = lv_wrbtr + ls_poscont-wrbtr.
        ELSE.
          PERFORM fill_bsegpos USING   lv_bschl lv_saknr
                                       ls_poscont-wrbtr p_bktxt
                                       ls_poscont-kostl ls_poscont-prctr
                                       lv_item
                              CHANGING pt_ftpost.
          CLEAR: lv_wrbtr,
                 lv_saknr,
                 lv_bschl.
          lv_item = lv_item + 1.
        ENDIF.
        AT END OF saknr.
          IF ls_poscont-indhkont = abap_true.
            PERFORM fill_bsegpos USING   lv_bschl lv_saknr
                                         lv_wrbtr p_bktxt
                                         ls_poscont-kostl ls_poscont-prctr
                                         lv_item
                                CHANGING pt_ftpost.
            lv_item = lv_item + 1.
          ENDIF.
        ENDAT.
      ENDLOOP.
    ENDFORM.                    "fill_bseg
    *===================================================================
    FORM fill_bsegpos
    *===================================================================
                        USING    p_bschl   TYPE bschl
                                 p_saknr   TYPE saknr
                                 p_wrbtr   TYPE wrbtr
                                 p_bktxt   TYPE bktxt
                                 p_kostl   TYPE kostl
                                 p_prctr   TYPE prctr
                                 p_pos     TYPE buzei
                        CHANGING pt_ftpost TYPE tt_ftpost.
      DATA: lv_wrbtrstr TYPE char16.
      WRITE  p_wrbtr TO lv_wrbtrstr
                    CURRENCY c_waers NO-SIGN.
      PERFORM append_ftpost USING    c_typepos p_pos
                               'BSEG-BSCHL' p_bschl
                      CHANGING pt_ftpost.
      PERFORM append_ftpost USING    c_typepos p_pos
                                     'BSEG-HKONT' p_saknr
                            CHANGING pt_ftpost.
      PERFORM append_ftpost USING    c_typepos p_pos
                                     'BSEG-WRBTR' lv_wrbtrstr
                            CHANGING pt_ftpost.
      PERFORM append_ftpost USING    c_typepos p_pos
                                     'BSEG-SGTXT' p_bktxt
                            CHANGING pt_ftpost.
      IF p_kostl IS NOT INITIAL.
        PERFORM append_ftpost USING    c_typepos p_pos
                                      'COBL-KOSTL' p_kostl
                             CHANGING pt_ftpost.
      ENDIF.
      IF p_prctr IS NOT INITIAL.
        PERFORM append_ftpost USING    c_typepos p_pos
                                      'COBL-PRCTR' p_prctr
                             CHANGING pt_ftpost.
      ENDIF.
    ENDFORM.                    "fill_bsegpos
    Edited by: Javier Meavilla Olivas on Feb 25, 2010 1:25 PM

  • How could I change the Invoice date automatically in MIRO?

    Of course, I can change it manually. But the user want to calculate the due date in their own way---we have a special way to calculate the due date. So, I am looking for User-exit where I can write ABAP codes to recalculate the invoice date and cover the default invoice date, so the system can get the right due date by calculate the invoice date in the standard way.
    Did anyone have any experience in change the invoice date??Pls tell me. THKS!

    You can use the badi MRM_HEADER_DEFAULT.
    (See in transaction SE18)

  • MIRO Calculate Tax button should be automatically checked.

    Hi All,
    While doing MIRO (Invoice), calculate Tax checkbox needs to be automatically checked. Could any one let me know where to configure these settings so that "Calculate Tax" will be automatically checked. Is this setting will be on a User level ?
    Thanks
    Rajanikanth

    I don't think there is a customizing for this.  You have to do it for each user in the user profile.
    Ask your user to go to System -> User Profile -> Own Data from the menu on top (in any screen in SAP) or execute T-Code SU3. In the session that opens up (User Profile), go to Parameters tab and key in 'XTX' in Parameter ID and 'X' in Parameter value. Save the changes to User Profile. Restart MIRO.

  • Receivable Aging Report for India based on Invoice Date

    We have a reporting/legal need for our India location to report the aging of their receivables based on the invoice date of the documents rather than the net due date.  Is there an existing report available that already does this?
    Currently when you use FBL5N and related aging reports RFDOPO10 etc. it calculates the arrears from the net due date.  They need to calculate the arrears from the document date.

    The report S_ALR_87012168 still does not allow me to choose that I want to calculate the arrears from the document date rather than the net due date:
    I guess what they really need to know is how old the receivables are based on the date they were created.
    As in the example below, current aging reports use the Net Due to calculate a days in arrears of 6 days (based on current date of 2008/11/05).
    Ty Doc. Date  Pstng Date Bline Date Net due dt Arrea
    RV 2008.09.30 2008.09.30 2008.09.30 2008.10.30     6
    What they need is the number of days in arrears based on the document date (2008.09.30) which would increase the numer of days the receivable has been open to 36.

  • Invoice Date needs to be date when Customer receives goods

    Client when shipping by sea would like the Invoice Date to be the same day the customer received the goods, basically the Pick Up Date even though the delivery might have been 'shipped' from the jetty.
    How can this be done? Would the Invoice Date be the Pick Up date?
    Sanjib

    Hi,
    I guess you're asking about OM shipping and AR invoices. If you have invoicing at line level, as soon as you ship a line, OM insert a line into AR interface and this line is ready to be imported into AR. If you ship from USA to Europe by sea it will take about 10-15 days to goods be delivered. As invoice date is defined when you import it into AR, in order to achieve your requirement, you will not be able to import your invoice into AR and will not have info on Receivables. Or do you want to import your invoice into AR as soon as goods are shiped and change the invoice date when customer receives them?
    In the first option, you could do the following: define two AR batch sources: AIR and OTHER, for example. The first one will be used to sea shipping and the second one to ground or air shipping. In the first AR batch source, uncheck derive date. In OM, define two order types: OT_AIR and OT_OTHER, one to sea shipping and other one to ground/air shipping. In order type AIR, define AIR as batch source, and in OT_OTHER define OTHER as batch source.
    Normally import your transaction with batch source OTHER into AR. For the orders shipped by sea, you will have to import them one by one. As soon as you receive the customer acks, go to ar autoinvoice and import the order received by the customer and define as default transaction date the date informed by the customer.
    I know it is not a good solution, so I think you will need some custom to have it done.
    Hope it helps,
    Ketter Ohnes

Maybe you are looking for