CIN, TAX PROCEDURES PURPOSE

Helloooo SD Gurus,
Pl resolve my doubt regarding the exact difference between taxinj, taxinn procedures with live example.
tnx in advance.
yours
venkat g

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.

Similar Messages

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 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.

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.

CIN TAX PROCEDURE

Can u pls. help me to know TAXINN procedure and creating a new tax code??

Hello,
Basically CIN is divided in to two types:
1. TAXINJ - Is a Routine Based that is used in the condition types. it will work on the logic what ever is there in the Routine.
2. TAXINN: - Is a condition Record based. Means we have to create condition records for each and every condition type that you are going to use in the Pricing Procedure.
CIN:
IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings >
Maintain Excise Registrations
For the tax code can be create in FTXP
Regards
Rajesh Dalal

Purpose of CIN and procedure to map into SAP

Hai Gurus,
Can any one explain teh purpose of CIN and procedure to map to SAP
Thanks in Advance
sameer

CIN stands for Country India and represents the tx structure of India in SAP. Following are the settings to be maintained in the SAP
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
Reward points if it helps you.

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

Let me know recommended Tax Procedure for CIN

I heard from some of my friends Condition based Tax procedure is recommended by SAP (ie. TAXINN).
If the above statement is true, Can any help me to identify the SAP Note no. for this recommendation? Because i need to give the same to my client.
Thanks,
Venkat

Hi,
952289 - General Clarifications on TAXINN
950976 - Country Version India (CIN) Master note for MM FAQs
Go to following link
[https://websmp106.sap-ag.de/notes]
and enter Search Terms as "TAXINN" it will provide list of all the possible SAP Notes relevant to TAXINN

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 servers 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 XR1XR6 are maintained with a 100% rate.      A
(Output tax)     2
O1     A/R Sales Tax     Condition types XR1XR6 are maintained with a 100% rate.     A
(Output tax)     0
I0     A/P Tax Exempt     Condition types XP1IXP6I are maintained with a 100% rate.      V
(Input tax)     2
I1     A/P Sales Tax     Condition types XP1IXP6I are maintained with a 100% rate.     V
(Input tax)     0
U1     A/P Self Assessment Use Tax     Condition types XP1IXP6I are maintained with a 100% rate. Negative 100% is entered for condition types XP1UZP6U 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

Cin implementation procedure

Hi all,
I have to questions.
1. Can any one can help me how to configure the cin in SAP?.
2. what is the use of Validations and Substitutions in Sap. how we are going to use?

Forward me your email id, so that I can forward you CIN Configuration Document (with screenshots).
<b>Document is as under (without screenshots):</b>
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings >
Maintain Excise Registrations
Use
In this IMG activity, you maintain the data relating to your excise registrations.
Activities
Enter each of your excise registrations, specifying a four-character code for each
Excise Registration IDs
In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
Activities
For each excise registration in your business create a registration ID, and state:
     Which taxes the registration covers (additional excise duty, special excise duty, and cess)
Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
     The maximum number of items to be printed on each excise invoice
     Whether you are allowed partial CENVAT credits
Maintain Registration ID NUMBER, Excise code number, excise registration number
Excise Registration Number
A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
ECC Number
Specifies the organization's ECC number.
Excise Registration Number
A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division
Specifies the excise division in whose area the excise registration is located.
Excise Collectorate
The code of the excise collectorate in whose area the excise registration is located.
Indicator for confirming AED usage
Additional Excise duty Percentage. These are leviable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty.
Example
Additional Excise duty is leviable in case of textile products, tobacco and sugar.
Similarly for SED CESS
Number of Items in Excise Invoice
Shows the maximum number of line items that the authorities allow per excise invoice.
Dependencies
This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements.
This information is used to split the transfer postings' items into multiple subcontracting challans.
Excise register set description
Description of the excise registers set.
Partial CENVAT Credit
Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account.
Dependencies
When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
This information is also shown when you post the vendor's excise invoice.
Maintain Company Code Settings
Use
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings
It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
Indicator for providing debit account overwriting
Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
Automatic balance Indicator
Excise year start month
The calendar month marking the beginning of the excise year
Use
This start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
Excise invoice selection procedure
Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received.
Number of excise invoices to be selected
Indicates the number of excise invoices that needs to be selected in the excise invoice selection.
Days to be considered for excise invoice selection
Number of days from document date for excise invoice selection.
Example
If the value of this field is 20 and today is 28-03-97. The excise
invoice selection will show the related invoices only for the
period 08-03-97 to 28-03-97.
Document type for TDS FI posting
Financial accounting document type for TDS posting.
Document type for FI posting on Utilisation
Financial accounting document type for TDS posting.
Indicator for item level excise duty round off
This indicator is to be used for deciding whether Item level excise duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
Rounding off of Excise duty for outgoing excise invoice
You can round off the Excise amount to be paid during an outgoing Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
Immediate Credit on Capital Goods
Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts.
The rest is posted the CENVAT on hold account, for use in the following year.
CVD Clearing Account
Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
Exchange rate type
Key representing a type of exchange rate in the system.
Use
You enter the exchange rate type to store different exchange rates.
Example
You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
Exchange rate type to be used for Export excise duty converts
When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
Maintain Plant Settings
Use
In this IMG activity, you maintain excise information relating to your plants.
Plant Settings
In this activity, you maintain excise information relating to your plants.
Activities
For each plant:
     Specify whether it is a manufacturing site or a depot.
     Assign it an excise registration ID.
You can assign the same ID to more than one plant, if required.
Depot
Indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
Number of goods receipt per excise invoice.
Multiple GR for one excise invoice, Single credit
Multiple GR for one excise invoice, Multiple credit
Maintain Excise Groups
Use
In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
Excise Groups
In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
Recommendation
Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
If your company has only one set of excise registers, then you need to maintain only one excise group.
Activities
1. Create one excise group for each set of registers that you need to keep.
1.     Assign the excise groups to plants.
2.     Maintain whether this Excise group is for a depot or not.
3.     If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4.     If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
5.     During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
6.     If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7.     If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
8.     'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
9.      'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock .
10.      'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
11.      'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock.
Excise Group
Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration.
Dependencies
In define excise groups in Customizing.
Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to.
At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
Indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
GR Per Excise Invoice
Multiple GR for one excise invoice , Multiple credit
Multiple GR for one excise invoice , Single Credit
Create Excise Invoice Automatically
Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
The excise invoice is created in the background.
Dependencies
If you want to make use of this function, you must also define the default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
RG23D Sales Creation and posting option
RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step.
If this is not selected then you need to separately do RG23D selection followed by PGI and then RG23D verification and posting.
If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
Default excise qty in GR
If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
Folio number for depo
Posting
If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
Also we can set indicator for creation of part 1 for:
Blocked stock
Stock transport order
Consignment stock
Maintain Series Groups
Use
In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents.
Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
Activities
     Define excise series groups based on type of outgoing document
     Assign series group to excise registration ID
     If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
     If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.
Example
You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
No account postings for CENVAT in sales cycle
No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
IF the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT
Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
Maintain Excise Duty Indicators
Use
In this IMG activity, you maintain the excise duty indicators.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Select Tax Calculation Procedure
Use
In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
     If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
     If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
Maintain Excise Defaults
Use
In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
Activities
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
If you use formula-based excise determination, fill out all of the fields as follows:
     Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
     Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
     Specify the conditions in the sales order that are used for excise rates.
     Specify the countervailing duty condition type used for import purchase orders.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
Use
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features
The standard system comes with two tax calculation procedures. TAXINN is 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.
Activities
Customizing
Make the settings in Customizing for Logistics General, by choosing Taxes on Goods Movements  India  Basic Settings  Excise Duties Using Condition Technique and  Account Determination.
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data
Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities
When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1.     In the command field, enter FV11 and choose .
2.     Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3.     Select the combination of objects that you want to create the condition record for.
On the dialog box, Control Code means "chapter ID."
So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4.     Choose .
5.     Enter data as required.
In the Tax Code field, enter the dummy tax code that you have defined.
6.     Save the condition record.
Formula-Based Excise Determination
Use
When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
Prerequisites
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can access from the SAP Easy Access screen by choosing Indirect Taxes  Master Data  Excise Rate Maintenance.
You maintain the following types of data:
     Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone.
See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
     Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry.
For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
     Customer master data
Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
     Material master data
Each material is assigned a chapter ID.
     Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Activities
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1.     Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2.     Looks up the plant master data to see what status you have assigned the plant.
Similarly, your plant has status 2.
3.     The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indictor is for customer status 3 and plant status 2: It is 7.
4.     The system determines the chapter ID of the ball bearing for the plant.
Lets assume the chapter ID at plant for the ball bearings is 1000.01.
5.     Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under status 7.
Define Tax Code for Purchasing Documents
Use : In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
Only carry out this activity if you use condition-based excise determination.
Activities: Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
Assign Tax Code to Company Codes
Use
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
Classify Condition Types
Use
In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.
The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.
In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
     For taxes on purchases, use the condition types contained in the tax procedure.
     For taxes on sales, use the condition types contained in the pricing procedures.
Standard settings
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
Define G/L Accounts for Taxes
Use
In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements
You have set up G/L accounts for each of the processing keys listed below.
Activities
Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
     VS1 (basic excise duty)
     VS2 (additional excise duty)
     VS3 (special excise duty)
     VS5 (sales tax setoff)
     MWS (central sales tax)
     MW3 (local sales tax)
     ESA (service tax)
     ESE (service tax expense)
Specify Excise Accounts per Excise Transaction
Use
In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
If you use subtransaction types, enter the accounts for each subtransaction type as well.
Activities
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example
Excise TT     DC ind     Account name
GRPO     CR     CENVAT clearing account
GRPO     CR     RG 23 BED account
GRPO     DR     CENVAT on hld account
Specify G/L Accounts per Excise Transaction
Use
In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
     Excise group
     Company code
     Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
     Defined the G/L accounts
     Defined the excise groups
     Maintained the transaction accounts
Activities
For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
Note
You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
Config setting needed to be done in order to get the Excise Details Screen in Material Master.
Even though this functionality is available in enterprise version, a small config step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
1.     Go to IMG  Logistics General  Material Master  Configuring the Material master  Define Structure of Data Screen for each Screen Sequence.
2.     Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3.     Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is Foreign Trade: Import Data. Select the same and click on Subcreens in the left frame.
4.     Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view subscreen and ensure that the subscreen is blank.
5.     Now in the last sub screen i.e. no.6 you delete SAPLMGD1 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6.     Save the setting.
7.     Create a Material Master and check whether in Screen Foreign Trade Import, Excise related subscreen appears.
Regards,
Rajesh Banka
Reward points if helpful

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 Procedures and MM pricing procedures

Currently when creating a PO under the invoice tab you can input the Tax code and jurisdiction code.
The tax code I am using is set up for a Canadian Tax procedure (TAXCAJ).
The procedure is calling two tax condition types JC1E (GST) and JC1I (PST). They are both condition class D and they are the same accross other statistics but they differ in condition category. JC1E is condition category 1 and JC1I is condition category 2.
JCIE uses account determination VST while JC1I uses NVV. JC1E needs to be posted to a seperate account as it is partially recoverable.
The real underlying issue here is that tax condition type JC1I comes accross to teh MM condition tab under NAVS but JC1E does not. I need the value from JC1E to come over to the conditions tab as my PO print is driven by this.
Any ideas how to get tax condition type JC1E (or its value) over to the conditions tab. I can make JC1E come over with JC1I but i need JC1E seperate. If you need clarification or more information just let me know.

Hi,
NAVS condition collects the non-deductible portion of the Tax Code and hence only showing JC1I which is a non-deductible condition type. The logic behind this is non-deductible tax is part of cost, so for updating the stock account at the time of GR with base value + discounts and other pricing conditions + non-deductible tax, NAVS condition type is being used in PO pricing procedure. JC1E is a deductible type tax and as not being a part of cost it is not updated in NAVS and hence the stock account at the time of GR.
If you want all the tax amounts for PO printing purpose, use JEXS condition type and insert this at the last of the pricing procedure with statistical indicator. Modify your print program to print value against JEXS instead of NAVS.
regards,
mallik

Cin pricing procedures

what r the major differences between TAXINJ and TAXINN. which would be very useful in present scenario. and advisable,
will reward

Refer link below hope it helps
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.
TAXINN AND TAXINJ difference ? AND Which is better ?
TAXINJ & TAXINN are Tax Procedures in India. TAXINJ is old version & TAX INN is new version. Both has its own advantage & disadvantage.
Upto 4.6C & partially 4.7 version of SAP, TAXINJ was used. TAXINJ is formula based calculation, in which we maintain the tax rate in Tax Code itself. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST & permutation & combination of these, we require that many Tax Codes. For example:
Tax Code: A1
Taxes: 16% Excise Duty + 2% Education Cess + 12% VAT
Tax Code: A2
Taxes: 16% Excise Duty + 2% Education Cess + 8% VAT
Tax Code: A3
Taxes: 12% Excise Duty + 2% Education Cess + 12% VAT
Tax Code: A3
Taxes: 12% Excise Duty + 2% Education Cess + 8% VAT
From 4.7 version onwards of SAP, TAXINN is being recommended & used. TAXINN is more user friendly & condition record based. In TAXINN, Tax Codes are statistical & of not much relevance, but are required to be maintained in condition record for taxes condition type. This makes Tax Codes simpler. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST, we need not have the tax codes to that combination. For example:
Tax Code: A1
Can be used for any rate of excise duty, as tax code is only required to be maintained statistically in condition record.
Tax Code: A2
Can be used for any rate of VAT, as tax code is only required to be maintained statistically in condition record

What is tax procedure in india is only vat?

hi, good morning to everybody,
i am working on sap sd module , i have idea tax determination procedure but i don't have complete idea about tax procedure can anybody explain about tax procedure and what is relation between cin and tax proceudre...
pls help me out...
thanks,
hari shankar..

Hi,
Please refer to
SAP Note - 950977 Country Version India (CIN) Master note for SD FAQs or
SAP Note - 950976 Country Version India (CIN) Master note for MM FAQs
SAP Note - 532557 FAQ: Country Version India (CIN) General queries
Links below : http://help.sap.com/saphelp_47x200/helpdata/en/40/a23c39129ffe2ee10000000a114084/frameset.htm
Rgds.

Tax procedure Routine

HI Team.
Case 1: Tax amount calculation
Net Price(Basic Price) + Freight on tax or Packing on
Forwarding on Tax + Excise duty + Vat/CST = Total value
In this case Tax procedure Routine is 17.
Case 2: Tax amount Calculation
Net Price + Excise duty + Freight + Vat = Total value
In this case Tax Procedure Routine is 363.
MY Requirement is i want above 2 Requirements in PO Creation, Please tell Tax procedure Routine to match above cases.

Hi,
If you are working for CIN, then refer the doc: Tax Calculation on Freight - Different Scenarios
Regards,
AKPT

CIN, TAX PROCEDURES PURPOSE

Similar Messages

Maybe you are looking for