on 11-22-2011 8:38 AM
Hello,
We have activated BADI VATDATE_VALUES_46 to calculate tax reporting date, but it is not being called when using transaction VF11, so tax reporting date is not being correctly calculated in billing document cancellation.
How could we solve it?
Thanks and best regards
Hi
Check if Note 1567029 "Badi VATDATE_RULES: VF11 w/ new cancellation, FB08 w/ input" is relevant in your system.
Regards
Eduardo
PD: I forgot, see Note 1232484 - How to use the VAT due date, tax reporting date VATDATE.
Edited by: E_Hinojosa on Nov 22, 2011 11:42 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Check with an ABAPer your coding in your BADI or copy it and maybe I could help you. For instance, I am doing it with IF_EX_VATDATE_VALUES~VATDATE_DETERMINE (I am in a ECC 5.00) and I set for E_VATDATE values depending of type of document. So, the question is read the ABAP and understand how the algorithm is setting the value for E_VATDATE.
See SAP Note 400000 - FAQ: Transaction VF11: Cancellation of SD billing documents and SAP Note 1259505 - FAQ: New cancellation procedure in SD for understand how VF11 works. As note 400000 says, the transfer to accounting is with FM RV_ACCOUNTING_DOCUMENT_CREATE. In the other hand, check with your tax advisor if it's advisable to set a different date in VATDATE with VF11 (remember the impact in modelo 340 and so on).
I hope this helps you
Regards
Eduardo
Hello,
We have entered Z code in the BADI to determine the tax reporting date in base on a Z table.
It works correctly in document generation (FB01, VF01...) but it does not calculate the correct tax reporting date in document cancellation (FB08, VF11...)
Is it correct to enter Z code in this BADI?
Thanks a lot for your help
Hi
Yes, it's right if you write your own coding. See the article [Business Add-Ins|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f3202186-0601-0010-6591-b832b1a0d0de] by Aveek Ghose to understand these tools.
SAP in note 1232484 gives a coding, that you can change according your requirement. Of course, it's your coding and so, it's your responsability. If you create this objects in your range name (SAP Note 16466 - Customer name range for SAP objects) there aren't problems. Think that BADI, enhancement, BTE and other userexits (as VOFM subroutines) are developed to manage special customer situation and avoid modifications in standard (SAP Note 170183 - What to consider when applying modifications). But usually, if there are risks with an unaccurate use of these objects, SAP uses to warn to developers (for instance Note 1284654 - Caution with implementations of the BAdI: MB_DOCUMENT_BADI).
I hope this helps you
Regards
Eduardo
User | Count |
---|---|
103 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.