TAXINJ Tax Procedure in Ecc6.0 EHP2

Hi All,
We have ECC 6.0 EHP2 version. Can we use taxinj tax procedure, if yes, what are the limitations we have or what might be the problems we face ?
Regds,
CB

in further releases SAP will not release any
    new patches/additions in TAXINJ
I dont think so due to the fact that many clients who are in ECC6 are following TAXINJ.  Also SAP recommends not to change over from TAXINJ to TAXINN unless the manufacturer is going in for a complete reimplementation. 
user must manually select the correct tax code during PO creation
Not necessary.  It can be automated if user maintains Info record in TAXINJ process.  Also I dont find much difficulty in going for TAXINJ. 
thanks
G. Lakshmipathi

Similar Messages

  • Impact of tax procedure

    Dear All,
    In the Indian context TAXINJ and TAXINN tax proceudres are used.
    Now suppose a customer has activated TAXINJ tax procedure. After some years the customer wants to change the tax procedure to TAXINN. [Vice-versa also]
    I would like to know the impact of change in the tax procedure.
    Can anybody help me?
    Thanks in advance.
    Piyush Ranpura

    In one of my earlier projects, we had referred the same with SAP who had indicated that it is NOT recommended to change in the middle unless you go for complete reimplementation.
    Still if you want to hear any opinion, I would request you to refer to SAP so that they will direct as to what should be done.
    thanks
    G. Lakshmipathi

  • Error in Tax procedure TAXINJ

    Dear Friends,
    During creating of tax procedure TAXINJ i am getting error in condition types. The error is Condition type JM01(IN: A/P BED deductib) not defined, please tell me where can i create these condition types i.e. JM01, JA01, JS01 etc...
    If possible please tell me step by step and navigation to create tax procedure taxinj.
    And tell me what is the difference between TAXINJ and TAXIIN
    Advanced thanks
    ES.

    CIN Configuration
    1.1 Maintain Excise Registration
     Logistics general  SAP Ref. IMG SPRO  Maintain Excise Basic setting India tax on Goods Movements Registrations
    1.2 Maintain Company Code Settings
    SPRO   Basic settingIndia  tax on Goods Movements Logistics general SAP Ref. IMG   Maintain Company Code Settings
    1.3 Maintain Plant Settings
    tax on Goods Logistics general  SAP Ref. IMG SPRO   Maintain Plant Basic setting India Movements Settings
    1.4 Maintain Excise Groups
    SAP Ref. IMGSPRO   Maintain Basic setting India  tax on Goods Movements Logistics general  Excise Groups
    1.5 Maintain Series Groups
    SAPSPRO   Basic setting India  tax on Goods Movements Logistics general Ref. IMG  Maintain Series Groups
    1.6 Maintain Excise Duty Indicators
    tax on Goods Logistics general  SAP Ref. IMG SPRO   Maintain Excise Duty Basic setting India Movements Indicators
    1.7 Maintain Subtransaction Type with Text
    India  tax on Goods Movements Logistics general  SAP Ref. IMG SPRO   Maintain Subtransaction Type with TextBasic setting
    1.8 Determination of Excise Duty
    tax Logistics general  SAP Ref. IMG SPRO   Select Tax Calculation Determination of Excise DutyIndia on Goods Movements Procedure
    1.9 Maintain Excise Defaults
    SAP Ref.SPRO   Determination of ExciseIndia  tax on Goods Movements Logistics general IMG   Maintain Excise DefaultsDuty
    1.10 Condition-Based Excise Determination
    tax on Goods Logistics general  SAP Ref. IMG SPRO   Define Tax Code for Condition-Based Excise DeterminationIndia Movements Purchasing Documents
    1.11 Condition-Based Excise Determination
    tax on Goods Logistics general  SAP Ref. IMG SPRO   Assign Tax Code to Condition-Based Excise DeterminationIndia Movements Company Codes
    1.12 Classify Condition Types
    SAPSPRO   Condition-BasedIndia  tax on Goods Movements Logistics general Ref. IMG   Classify Condition TypesExcise Determination
    1.13 Maintain Chapter IDs
    tax on Goods Logistics general  SAP Ref. IMG SPRO   Maintain Chapter ids Master dataIndia Movements
    1.14 Assign Users to Material Master Screen Sequence for Excise Duty
    SPRO   Master dataIndia  tax on Goods Movements Logistics general SAP Ref. IMG  Assign Users to Material Master Screen Sequence for Excise Duty
    1.15 Specify Excise Accounts per Excise Transaction
    tax on Goods Logistics general  SAP Ref. IMG SPRO   Specify Excise Accounts per Excise Account determinationIndia Movements Transaction
    1.16 Specify G/L Accounts per Excise Transaction
    tax on Goods Logistics general  SAP Ref. IMG SPRO   Specify G/L Accounts per Excise Account determinationIndia Movements Transaction
    1.17 Incoming Excise Invoices
    SAPSPRO   BusinessIndia  tax on Goods Movements Logistics general Ref. IMG   Incoming Excise InvoicesTransactions
    1.18 Define Processing Modes Per Transaction
     Logistics general  SAP Ref. IMG SPRO   Define Processing Modes Business TransactionsIndia tax on Goods Movements Per Transaction
    1.19 Define Reference Documents Per Transaction
    tax on Goods Logistics general  SAP Ref. IMG SPRO   Define Reference Documents Per Business TransactionsIndia Movements Transaction
    1.20 Maintain Rejection Codes
    SAPSPRO   BusinessIndia  tax on Goods Movements Logistics general Ref. IMG   Maintain Rejection CodesTransactions
    1.21 Specify Which Movement Types Involve Excise Invoices
    Logistics SAP Ref. IMG SPRO   Specify Which Business TransactionsIndia  tax on Goods Movementsgeneral  Movement Types Involve Excise Invoices
    1.22 Outgoing Excise Invoices
    tax on Goods Logistics general  SAP Ref. IMG SPRO  Assign Outgoing Excise Invoices  Business TransactionsIndia Movements Billing Types to Delivery Types
    1.23 Maintain Default Excise Groups and Series Groups
     Logistics general  SAP Ref. IMG SPRO   Outgoing Excise Invoices  Business TransactionsIndia tax on Goods Movements Maintain Default Excise Groups and Series Groups
    1.24 Subcontracting Attributes
    tax on Logistics general  SAP Ref. IMG SPRO   Subcontrac Subcontracting Business TransactionsIndia Goods Movementsting Attributes
    1.25 Maintain Movement Type Groups
    SPRO   BusinessIndia  tax on Goods Movements Logistics general SAP Ref. IMG   Subcontracting SubcontractingTransactions Attributes
    1.26 Utilization Determination
    SAPSPRO   BusinessIndia  tax on Goods Movements Logistics general Ref. IMG   Utilization Determination UtilizationTransactions
    1.27 Specify SAPscript Forms
    tax on Logistics general  SAP Ref. IMG SPRO   Specify Excise Registers Business TransactionsIndia Goods Movements SAPscript Forms
    1.28 Number Ranges
    SAP Ref. IMGSPRO   Number ToolsIndia  tax on Goods Movements Logistics general  Ranges
    1.29 Message Control
     SAP Ref. IMG SPRO   Message ToolsIndia  tax on Goods MovementsLogistics general  Control
    Regards,
    Rajesh Banka

  • Tax  Procedure-TAXINJ/TAXINN-----cin

    Hi Gurus,
    We have a stanrdard pricing procedure like RVAA01 and inthis procedure we maintain all conditions like pricing, discount, frieght, tax..etc., but my doubt is why we need tax pricing procedure specially...like TAXINJ, TAXVAT, TAXINN..?
    And in TAXINJ we maintain condition BASB instead of PR00....what is the difference of these condition??
    Please help me..
    Rewards will be given...

    Hi,
    TAXINJ/TAXINN are the two different pricing procedure used in CIN.
    TAXINN only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination.
    Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
    Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
    When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
    Hope i have answered your query.
    Thanking You
    Regards
    Manjunath

  • Non deductable BED ( to be inventorized) tax procedure TAXINJ

    Hi,
    We are using Tax Procedure TAXINJ
    We have created tax code AA and used JMO2(BED Non Deductable) this is to be inventerized since we r not getting CENVAT credit for the same. *In PO the tax amount is not displaying in Taxes tab.*
    where as if i change the tax code to P5(JMO1 BED set off) it is displaying correctly.
    that means "J1ID"(Excise Master data) is maintained.
    Please help to solve this problem. Its really urgent.

    Get in to the Taxation procedure OBQ3 check whether NVV transaction key has been assigned against the condition JM02
    Check that J1iD is properly Maintained , Check that the condition record has been maintained for the JM02 ,
    check ur tax code is proerly defined as Input type
    It will work fine if u have maintained all
    Regards
    R.Rajaram

  • Questions about CIN tax procedure choice and pricing schemas

    Hi all,
    I have to implement SAP on a Indian company and I'm verifying all particularity about this country (in particular tax procedures and the great number of differents tax conditions used).
    I have two questions about tax procedures and pricing schemas. Every feedback about thse points will be appreciated.
    a) To choose tax procedure TAXINN or TAXINJ which are the elements that I have to consider?
         I have read lot of documentation about CIN implementation and Iu2019m oriented to choose TAXINN schema, but If possible I  would  to understand better which are on behalf of one choice or another.
    b) To define pricing schemas for India, after check with local users and using examples of documents (in particular tax invoice) actually produced, I have understood that taxes have to be applied on amount defined starting from price list, minus discounts recognized to customer plus surcharges eventually to bill (packing, transport,  etc.).
    Itu2019s correct for any type of taxes that tax amount is calculated on u201Cnet valueu201D defined at item level or there are exceptions to this rule?
    Thanks in advance
    Gianpaolo

    hi,
    this is to inform you that,
    a) About point 1 I know the difference between the 2 tax procedures (conditions or formulas). I also have read in others post in the FORUM that TAXINN is preferable. So I would to understand which are the advantages to choose instead TAXINJ. There are particular reasons or it'a only an alternative customizing setting?
    a.a. for give for posting the link : plese give me the advantages of TAXINJ and TAXINN
    CIN - TAXINN and TAXINJ
    b) About point 2, to define which value has to be used as base amount to calculate taxes isn't a choice, but is defined depending by fiscal requirement of the country, in this case India fiscal requirement. I know that, as Lakshmipathi
    write as answer on my question, exception could be, but it was important for me to understand if I have understood correctly the sequence of the pricing condition in the schema in "normal" situation.
    b.b. you can create your own pricing procedure for this and go ahead.
    hope this clears your issue.
    balajia

  • CIN tax procedure TAXINN

    hi all,
    in
    Logistics - General - Tax on Goods Movements - India - Basic Settings - Determination of Excise Duty - Select Tax Calculation Procedure
    if i choose to have tax procedure TAXINN,
    in
    Logistics - General - Tax on Goods Movements - India - Basic Settings - Determination of Excise Duty - Maintain Excise Defaults
    i can only define 1 condition type under CVD cond. field..
    what if i have a few several more condition type to be defined?
    because in J1IEX, the Total BED value is taken from the condition type defined in CVD cond. field.
    how is it possible for me to add in a few more condition type into CVD cond. field?
    i have tried adding the other condition types under field like A/P BED Cond. and A/P SED Cond. but the value was not being captured in J1IEX.
    anyone can advice?
    thanks.

    Hi all,
    my scenario is i need to have the following condition type(customized) to be populated in the excise invoice.
    Z001 - Z004 are the customized condition type for their respective tax.
    CVD - Z001
    Edu CESS - Z002
    Higher Edu Cess - Z003
    S.A.D  - Z004
    IN
    Tax on Goods Movements - India - Basic Settings - Determination of Excise Duty - Maintain Excise Defaults
    since i am using TAXINN, i have managed to tagged Z001 to CVD cond field and the value was able to come out in J1IEX correclty.
    what about Z002 to Z004? do i need to switch to TAXINJ so i can populate them into A/P BED cond, A/P SED Cond, A/P AED Cond? what are the alternatives for TAXINN?
    i read somewhere that for india implementation, it's best to use TAXINN, as TAXINJ will be obsolete soon. - correct me if i am wrong.
    I will need to populate all the values above to in J1IEX so that in my RG23D form can capture and display the value from Z001 to Z004.
    thank you.

  • ECC6 EHP2 (ABAP+Java)  system copy using file system copy

    Hello Experts,
    I have a question around system copy method for a dual stack ECC6 EHP2 system.
    We are planning to take full file system backup of this entire ECC6 EHP2 dual stack system and throw it on a completely new hardware with new host name but same SID.  We are also planning to do a host renaming in instance profiles and re-building the control files in target system after we finish the file system restore.
    Is this method supported in SAP ? Or we strictly have to use  SAPinst to do export and import method.  In any case our source and target platform is not going to chance as per our scenario.
    Any suggestions will be greatly appreciated.
    Thanks,
    Harshal

    > Thanks for the quick response. Is their any document that says it is not supported ?  Because of no proper document that says no to do it, client want's to try it out.
    For the ABAP part this is certainly feasible.
    The Java part has not only issues with the secure store but also with SID and hostname. The old values are stored in many places in the database and in, depending on the applications installed, many .properties files in the filesystem. So it would be not enough to somehow regenerate the secure store but also change hostname and SID in different places that are not really all documented.
    What you are basically looking for is
    Note 757692 - Changing the hostname for J2EE Engine 6.40/7.0 installation
    with the significant sentence
    This note should be applied only when the hostname of a machine
    where the j2ee engine was already installed has changed.
    It does not replace the SAP official system copy procedure and
    MUST NOT be used for copying of an instance to another host and/or with different SID.
    Markus

  • Client from 800 to 000 client to activate the TAX Procedures..

    Hi Guru's,
    In my practice server i am not able to get the tax procedures TAXINN and TAXINJ for this i went to institute they said that copying from 000 client to 800 client..then we can get in 800 client also.. but here is the problem how to do it..
    Please friends if any one know's please reply me...
    Thanks & Regards
    Sunil gupta.

    Hi Sunil,
    Please go through the link given below.
    SAP Library - BC ? Client Copy and Transport (BC-CTS-CCO)
    Hope this will help you.
    Regards
    Eugene

  • Tax Procedure in India

    Hi All,
    There is a requirement  to changes in taxes for Indian states  Kerala & Gujarat.  Post India Budget 2008-2009, the state governments have proposed a few changes to the taxes . There has been a requirement from the State Governments of Kerala and Gujarat, for imposing Social Security Cess  on VAT( kerala)  & Additional tax( Gujarat) on Base amount  applicable from 1st April 2008 and . The details of the same are as below:
    As per clause 6 the Kerala Finance Bill, 2008, a Social Security Cess has been imposed on
    at the rate of 1% on VAT Payable.
    In the State of Gujarat,  Here are the changes as per the Bill. As per the Bill the total tax including additional tax, in case of goods attracting 4% will be 4% VAT + 1% Additional Tax and therefore total tax will be 5%. In case of goods attracting 12.5% the rate would be 12.5% VAT + 2.5% Additional Tax and therefore total tax would be 15%.
    To meet this requirement at FI side following is been carried out:
    1.     Two new conditions will be added to the Tax procedure( TAXINJ):
    a.     ZSSC u2013 Itu2019s a new condition proposed for Kerala tax changes which represents the Social Security Cess calculating on VAT in Kerala. This will be applied on VAT (JIP5). This new condition needs be added in the Pricing procedure from PUR.
         This ZSSC tax condition which will be created in FI will post to G/L account -1337027.
    b.     ZADT u2013 Its new condition proposed for Gujarat Additional tax. This will be applied on the value on which VAT (JIP5) is calculated. This new condition needs be added in the Pricing procedure from PUR.
         This ZADT tax condition which will be created in FI will post to G/L account -1337032.
      3.   Tax codes needs to be created for respective states. Respective changes needs to be done in pricing procedure by PUR.
    My question is what need to be done at Purchasing level for Input tax. All I understand is we need to do  the testing once tax code is changed.  There is no Change at Pricing Procedure level at Purchasing. Please advice what all should be covered in testing ? Do I need to cover all purchasing documents and PO processes like consignment, Subcontracting, Contract,SA etc,
    Thanks.
    Shalini

    Hi,
    If u modified  the TAXINJ procedure as per the requirement means .
    on which amount VAT @ kerala state needs to be calculated?
    on which amount VAT @ Gujarat state needs to be calculated?
    this is importent from TAXINJ procedure point of view.
    Secondly ,
    In TAXINJ Tax code is important u should have diff tax code (u allready have it)
    Testing point of view:
    U should run a domestic procurement cycle and check the account enties at the time of MIGO & MIRO (important).
    I think this would be enough.
    regards,
    SNB

  • EFFECT OF TAX PROCEDURE

    HI
    First we configured CIN settings (TAXINN procedure) in our 650 client (DEV clinet) later we changed to TAXINJ in DEV itself and again we changed to TAXINN only. Now the tax codes are not working while doing the MM transaction is coming stating that Tax code is not assigned to TAXINN procedure. Now i want to know is there any effect by chaning the tax procedure like this manner will effect the tax codes or not? Please help me in solving this issue.

    hi sravani,
    the following are the SAP Tax Procedures to configure
    OBBG - Assign Country to calculation procedure.
    OBCO - Specify structure for Tax Jurisdiction code. For country like U.S.A.
    LG -> character length of first level of hierarchy within your tax jurisdiction code structure.
    LG -> Second level of hierarchy as above.
    LG -> Third level of hierarchy as above.
    LG -> Fourth level of hierarchy as above.
    TX -> Tick if you want the system to determine taxes on a line by line basis instead of determining them on a cumulative basis
               per tax jurisdiction code.
    OBCP - Define Tax Jurisdiction code
    Dil -> Tick if you do not want tax amounts included in the based amount used for calculating cash discounts.
    Txl -> Tick if you want the cash discount amount deducted from the base amount that is used to calculate taxes.
    FTXP - Define Taxes on Sales/Purchases Code.
    OBCL - Allow Tax codes for non-taxable transactions.
         External Tax Determination U.S.
    SAP AG
    Neurottstr. 16
    69190 Walldorf
    Germany     Configuration Guide
    Copyright
    © Copyright 2006 SAP AG. All rights reserved.
    No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
    Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
    Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
    IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.
    Oracle is a registered trademark of Oracle Corporation.
    UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
    Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
    HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
    Java is a registered trademark of Sun Microsystems, Inc.
    JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
    MaxDB is a trademark of MySQL AB, Sweden.
    SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
    These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
    Icons
    Icon     Meaning
         Caution
         Example
         Note
         Recommendation
         Syntax
    Typographic Conventions
    Type Style     Description
    Example text     Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.
    Cross-references to other documentation.
    Example text     Emphasized words or phrases in body text, titles of graphics and tables.
    EXAMPLE TEXT     Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
    Example text     Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
    EXAMPLE TEXT     Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.
    Example text     Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
         Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
    External Tax Determination
    1.1     Prerequisites
    Before using this configuration guide, you need to install the following building blocks in the order shown:
    Building Block     Description
    B32     Best Practices R/3 Installation
    V32     Best Practices Technical Objects (Manual DDIC, Tables, User Exit, Routine) + Install Transport
    J02     Organizational Structures
    V03     Financial Accounting
    V08     Basic Controlling
    V05     Delta Materials Management
    J04     Sales and Distribution
    V04     Delta Sales and Distribution
    1.2     Configuration
    1.2.1     Defining Physical Destination
    Use
    This activity defines an RFC destination.
    Procedure
    1.     Run the following activity:
    SAP R/3 Menu     Logistics  Central Functions   Supply Chain Planning Interface  Core Interface Advanced Planner  Settings   RFC Destination for Application
    Transaction Code     SM59
    2.     On the Display and Maintain RFC destinations screen, click TCP/IP connections.
    3.     Choose the Create button.
    4.     In the RFC Destination screen, enter the following:
    RFC destination     VERTEX_MAXTAX
    Connection type     T
    Description 1     Connection to Vertex
    5.     On the Technical settings tab, enter the following:
    Gateway host     Vertex server’s name
    Gateway service     Your gateway service for Vertex server
    6.     Choose the Save button.
    1.2.2     Define Logical System
    Use
    This activity defines the logical destination for external tax determination.
    Procedure
    1.     Start the following activity:
    IMG Menu     Financial Accounting (New)   Financial Accounting Global Settings  Tax on Sales/Purchases  Basic Settings  External Tax Calculation  Define Logical Destination
    Transaction Code     SPRO
    2.     Enter the following values:
    N     Ex     Event for ext. taxation proc.     Function Module     RFC Destination
    1     V     JUR     RFC_DETERMINE_JURISDICTION     VERTEX_MAXTAX
    2     V     TAX     RFC_CALCULATE_TAXES1     VERTEX_MAXTAX
    3     V     UPD     RFC_CALCULATE_TAXES1     VERTEX_MAXTAX
    3.     Choose Save.
    1.2.3     Maintain Pricing Procedures
    Use
    This activity maintains pricing procedures.
    Procedure
    1.     Start the following activity:
    IMG Menu     Sales and Distribution  Basic Functions  Pricing  Pricing Control  Define and Assign Pricing Procedures
    Transaction Code     SPRO
    2.     Enter the following values:
    Table VV_T683_VA
    N     Cl     U     App     Proc     LA     Destination     TSPP     PrTy
    1     030     A     V     ZVAXUD     EN     BU SMB with ext. Jurisd.NEW          
    2     030     A     V     ZCAX01     EN     Intercompany Billing US Ext.     X     
    3     030     A     V     ZDPJXD     EN     myPCC US DownPaym/Tax per doc.          
    4     030     A     V     ZSER02     EN     Service BP Exp Settlement Ext.          
    5     030     A     V     ZSPUS1     EN     SP:Resource Related Bill Ext.          
    6     030     A     V     ZSPUS2     EN     SP: Res Rel Bill Down Pay Ext.          
    7     030     A     V     ZSPUS3     EN     SP: Res Rel Bill CrossComp Ext          
    8     030     A     V     ZU0030     EN     Credit memo (US) Ext.          
    3.     Choose Save.
    1.2.4     Define Pricing Procedure Determination
    Use
    This activity defines pricing procedures.
    Procedure
    1.     Start the following activity:
    IMG Menu     Sales and Distribution  Basic Functions  Pricing  Pricing Control  Define and Assign Pricing Procedures
    Transaction Code     OVKK
    2.     Enter the following values:
    Table V_T683V
    N     SOrg     DChl     Dv     DoPr     Cupp     PriPr     CTyp
    1     BP01     01     01     A     1     ZVAXUD     PR00
    2     BP01     02     01     A     1     ZVAXUD     PR00
    3     BP01     01     01     I     1     ZCAX01     
    4     BP01     01     01     V     1     ZSPUS1     RB00
    5     BP01     01     01     W     1     ZSER02     
    6     BP01     01     01     W     2     ZSER02     
    7     BP01     01     01     Z     1     ZU0030     
    8     BP01     02     01     Z     1     ZU0030     
    9     BP01     03     01     I     1     ZCAX01     
    10     BP01     03     01     I     1     ZCAX01     
    3.     Choose Save.
    1.2.5     Activate External Tax Interface
    Use
    This activity activates external tax interface.
    Procedure
    1.     Start the following activity:
    IMG Menu     Financial Accounting (New)  Financial Accounting Basic Settings (New)  Tax on Sales/Purchases  Basic Settings  External Tax Calculation  Activate External Tax Calculation
    Transaction Code     SPRO
    2.     Enter the following values:
    Table V_TXD_E
    N     Reference     Ex     version of the tax interface     TC     RFC Destination
    1     TAXUSX     V     TAXDOC00          VERTEX_MAXTAX
    3.     Choose Save.
    1.2.6     Assign Country to Tax Calculation Procedure
    Use
    This activity assigns a country to tax calculation procedure.
    Procedure
    1.     Start the following activity:
    IMG Menu     Financial Accounting (New)  Financial Accounting Basic Settings (New)  Tax on Sales/Purchases  Basic Settings   Assign Country to  Calculation Procedure
    Transaction Code     SPRO
    2.     Enter the following values:
    Table V_005_E
    N     Cty     Proc     Name
    1     US     TAXUSX     
    4.     Choose Save.
    1.2.7     Allocate Company Code to Non-Taxable Transactions
    Use
    This activity allocates company code to non-taxable transactions.
    Procedure
    1.     Start the following activity:
    IMG Menu     Financial Accounting (New)   Asset Accounting  Asset Accounting(Lean Implementation)  Organizational Structures  Assign Input Tax Indicator for Non-Taxable Acquisitions
    Transaction Code     OBCL
    2.     Enter the following values:
    Table V_001_J
    N     CoCd     Company Name     City     Input tax code     Output tax code     Jurisdict. code
    1     BP01     SAP Best Practices     Palo Alto     I0     O0     XX00000000
    3.     Choose Save.
    1.2.8     Create Number Range for External Tax Document
    Use
    This activity creates a number range for the external tax document.
    Procedure
    1.     Start the following activity:
    IMG Menu     Financial Accounting (New)  Financial Accounting Basic Settings (New)  Tax on Sales/Purchases  Basic Settings  External Tax Calculation  Define Number Ranges for External Tax Returns
    Transaction Code     OBETX
    2.     Enter the following values:
    Table NRIV
    N     Object Name     Subobject value     Number range number     To year     From number     To number     Curr. Number     External
    1     ETXDC_NR          01     0000     000000000001     999999999999          
    3.     Choose Save.
    1.2.9     Activate External Updating
    Use
    This activity activates external updating.
    Procedure
    1.     Start the following activity:
    IMG Menu     Financial Accounting (New)  Financial Accounting Basic Settings (New)  Tax on Sales/Purchases  Basic Settings  External Tax Calculation  Activate External Updating
    Transaction Code     SPRO
    2.     Enter the following values:
    Table V_TRWCA
    N     Comp     To year     Activ
    1     EXTX     2999     X
    3.     Choose Save.
    1.2.10     Creating Tax Codes for External Tax Calculation
    Use
    This activity creates tax codes for external tax calculation.
    Procedure
    1.     Start the following activity:
    Transaction Code     FTXP
    2.     The following five tax codes were created for the tax procedure TAXUSX and country US.
    Tax Code     Description     Condition types      Tax Type     Relevant to Tax     Tax  Category
    O0     A/R Sales Tax Exempt     Condition types XR1–XR6 are maintained with a 100% rate.      A
    (Output tax)     2     
    O1     A/R Sales Tax     Condition types XR1–XR6 are maintained with a 100% rate.     A
    (Output tax)     0     
    I0     A/P Tax Exempt     Condition types XP1I–XP6I are maintained with a 100% rate.      V
    (Input tax)     2     
    I1     A/P Sales Tax     Condition types XP1I–XP6I are maintained with a 100% rate.     V
    (Input tax)     0     
    U1     A/P Self Assessment Use Tax     Condition types XP1I–XP6I are maintained with a 100% rate. Negative 100% is entered for condition types XP1U–ZP6U to force the credit entry to the tax liability accounts.     V
    (Input tax)     0     1 (Consumer Use Tax)
    The values in the Relevant to Tax column can be interpreted as follows:
    •     Setting the Relevant to tax indicator to 2 will bypass the call to the external tax system, which saves processing time. If handling exemptions within Vertex or Taxware, then this indicator must be set to 0 or space, because the call must be made to Vertex or Taxware to access their exemption handling.
    •     Leaving the Relevant to tax indicator blank means that the tax code is relevant to tax and a call will be made to Vertex or Taxware to decide the tax rate.
    You can verify the settings using transaction FTXP.
    1.2.11     Change Jurisdiction Codes for SAP Best Practices Cost Centers
    This activity removes the standard jurisdiction codes from cost centers in order for Vertex to determine a valid jurisdiction code. The jurisdiction code found by Vertex is based on our default Palo Alto address.
    If you want to create different addresses for each cost center, choose Accounting  Controlling  Cost Centers  Master Data  Cost Center  Individual or Collective Processing.
    1.2.12     Change Jurisdiction Codes for SAP Best Practices Company Code and Plants
    This activity goes through the organizational elements of the SAP Best Practices — company code BP01 and plants BP01 and BP02 — and remove the standard-delivered jurisdiction code from the related addresses in order for Vertex to determine a valid jurisdiction code. The jurisdiction code found by Vertex is based on our default Palo Alto address.
    If you want to create a different address for each of the organizational elements, use transaction OBY6 to change the company code address, and transaction OX10 to change the plant addresses.
    dont forget to reward me points if it helps you
    regards
    karthik

  • Tax procedure

    Dear all,
                   What exactly the difference between Taxinj (condition based and formula based tax procedure), Taxinn (conditionbased taxprocedure)?I want to know the advantages & disadvantages of both.
    Thanks.
    Regards,
    Aditya.

    Taxinj :
    1. This we call as formulae pricing procedure.
    2. condition record is calculated based on the tax code.
    Taxinn:
    1. This we call as condition based pricing procedure.
    2. The condition record is determined based on the tax code as well as condition record.
    Mainly if we have big project it is not sufficient to get the condition record for tax conditions  through tax code, so it is necessary to maintain the condition record.
    Ex: Tax code is a two letter alpha numeric naming convention we use. ex if it country  USA , U1 - - - -  U9 .or ua  - - - uz.
    If we want to maintain more then this it is very difficult , so this is an disadvantage for the formulae pricing procedure.
    Thanks
    Gopalkrishna

  • Tax procedures

    Hi,
    What is the difference between TAXINN and TAXINJ and which procedure we use? there are lot of procedures...
    Thanks,
    Gani..

    The only difference between TAXINJ & TAXINN is that TAXINJ is formula
    based tax procedure which is dependant to a large extent on routines
    to calculate taxes at each level.
    TAXINN on the other hand is condition based tax procedure which is very
    similar to the standard pricing procedure & is not dependant on routines
    and other programs to fetch taxes. It is simply dependant on condition
    records maintained for each of the tax conditions.
    Prior to R/3 Enterprise we had only formula-based and from R/3 Enterpri
    version you will have the option of Formula-based or Condition-based.
    If you select TAXINN, it will support only condition- based excise
    determination. And if select TAXINJ, you will have the option of Formula
    -based and Condition-based (in SD not MM).
    If you have future plans for extending your organisation to our new
    dimension product such as CRM....then using TAXINJ would mean that the
    formulas would need to be copied/rewritten to the CRM IPC. Where as you
    would not be required to do that in TAXINN....
    So if you do not have any plans for extending SAP solutions in your
    organisation then you can use TAXINJ, else it is recommended that you
    use TAXINN only.

  • CIN Tax Procedures

    HI CIN GURU'S,
    Can anyone please explain me why different tax procedures are used,
    These below procedures are used for factory sales...
    J1INFAC (condition-based excise determination) and JFACT (formula-based excise determination).
    Then why TAXINN & TAXINJ....
    getting confused, please help ASAP.
    Please explain me how, where, why these procedures to be used and how does it would impact !!!
    Thank you,
    DAVID

    Difference between TAXINJ and TAXINN
    TAXINJ:
    1. It is Formula Based Tax procedure.
    2. It was most commonly used upto intial phase of R/3 4.7, but the latter implementations were with TAXINN.
    3. Tax Code plays a vital role, as the Tax Rate are maintained in Tax Code.
    4. It is complex compared to TAXINN
    TAXINN:
    1. It is Condition Based Tax procedure.
    2. Tax Code is required to be maintained in Condition Record, & if Tax Code is not found in Condition Record, Sales Cycle will go upto billing, but not release to accounting. Hence even a single Tax code may suffice the requirement for different Tax rate.
    Regards,
    Rajesh Banka
    Reward points if helpful.

  • Tax Posting without maintaining Tax Procedure

    Hi Gurus -
    Currently we get invoice information from thrid party software to post into SAP through interface. The Tax Code and Tax Amount are passed to SAP as a line item and the Taxes are already calculated in the thrird party and we only need to post that tax amount with Tax Code in SAP. Could anyone explain me what are the different config settings need to be done to accomodate this? I don't want SAP to calculate the Tax because the invoice file that comes from thrid party software already brings in the calculated Tax values.
    Pls suggest how to handle this in SAP.
    Thanks
    Jay

    Hi,
    Even though you do not want the system to calculate the taxes, still, if you want the tax codes to be appearing in the transaction, you have to customize / use the standard tax procedure that is provided.
    Now once you have assigned the tax procedure to the country, you can create the tax codes and at the time of creation of the tax codes make sure that all the tax codes have only the descriptions, but the rates to be maintained as 0. this will ensure that SAP does not calculate tax again.
    So for example if you have two different tax combinations like:
    ED + 4% VAT
    ED + 12.5% VAT,
    you can create them as two tax codes say, V1 and V2, but inside both these tax codes, the % has to be maintained as 0.
    The above example is on the assumption that you will be using TAXINJ as the tax procedure.
    If you are using TAXINN, then the condition types are to be maintained with 0%.
    Again assuming that you are implementing in India. The same logic can also be applied for other countries.
    Regards
    Venkatesh

Maybe you are looking for