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

Similar Messages

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

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

Tax procedure taxinj

Hi Experts,
In FV11 right now we have only key combination " taxes using jurisdiction code" we are using procedure taxinj and access sequence taxj.
Now that key combination is only asking country/taxcode at header and tax jur in footer.
I want plant also to be included but the condition table 053 attached to the acc seq taxj is not allowing me to change.
Where and how I can do that or I have to change alltogether the acc seq kindly suggest/
Can I create a new condition table and attach to the same acc seq
Rgds

Hi
Actually the entry of the added line item at the time of MIRO is giving me the problem, because that regarding to a prticular GL is falling in blank BA.
That is why I thought if plant can be included then that entry will fall into the respective BA.
The cond type JIP5 is maintained throught FV11 with tax code R2 for 4% vat.
Same tax code is chosen at PO as well as MIRO but the line item created in MIRO due to vat reimbrs thru a GL is falling into blank BA
if anybody has any clue how to overcome this plz help
rgds

Tax procedure-taxinj-----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 Ravi Kumar,
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.
Since Version 4.7 this TAXINN came into picture and start using this.
And one of the important points is since 4.6 c CIN comes a separate package. But after introduction of 4.7 Version, CIN is coming the SAP Package itself and even in the Customer Master Record also we will find the CIN Icon.
Basically 4 types of Pricing Procedures are used in CIN and are as follows:
1.JDEPOT - Depot Sales
2.JEXPOR - Export Sales
3.JFACT - Factory Sales
4.JSTKTR - Stock Transfer
Hope this Clarifies your Doubts and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

SAP CIN-MM Customizing - Tax Procedure TAXINJ

dear all expert pls explain what are the customization requir for CIN customer. thanks in advance

[http://wiki.sdn.sap.com/wiki/display/ERPLO/CIN%2bConfiguration]Hi,
[http://help.sap.com/erp2005_ehp_03/helpdata/EN/72/1535396503116fe10000000a114084/frameset.htm ]
[http://help.sap.com/bp_bblibrary/600/BBlibrary_start.htm ]*
Edited by: Saminathan Gopalan on Jun 7, 2010 1:53 PM

How to copy tax procedure TAXINJ from Client 000 to Dev client in ECC 6.0

Hi,
We are facing a problem for TAXINJ and TAXINN procedure, which are not available in our development client, but available in client 000.
Please advice how to copy those procedures from client 000 to development client.
(In client 000, we can not create a trabnsport request).

Hello ravi,
first check whether there request being generated at the time og customization in the server where the standard procedures exist.
if yes,then you just need to change a little bit of description of these procedures and save system will ask for the development request or customization request.,you can then ask the basis guy to transport it.
remember it is only a work around solution.
nevertheless you can also create it manually
revert if helpful
Mohit Singh

CIN diff betwn TAXINJ & TAXINN - Config settings SD

Hi,
1. can somebody help me out in giving a clarity on what condition types are maintained in TAXINJ and in TAXINN, similarly in JFACT & JINFACT.
2. Do we have any sales tax component like LST or CST in Exports in case yes what are they.
Points shall be rewarded for valuable answer
Regards
Mahesh

Hi Mahesh,
Let me share my knowledge on this
CIN Means Country India Version
In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenarios. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself.
Some info on CIN Configuration (it may not appear as understandable below, but if you check on screen, it will be understood better)
Country Version India comes with four pricing procedures as follows:
- JINFAC (Sales from manufacturing plants)
- JINEXP (Export sales)
- JINDEP (Sales from depots)
- JINSTK (Stock transfers
CIN: IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings > Maintain Excise Registrations
In this IMG activity, you maintain the data relating to your excise registrations.
- 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.
- 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
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 livable 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 livable 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.
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. 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.
- 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 - 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.
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. - 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 - 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.
1. Create one excise group for each set of registers that you need to keep.
2. Assign the excise groups to plants.
3. Maintain whether this Excise group is for a depot or not.
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. - 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. - 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. - 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 Group - 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.
- 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' Iindicator. 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 - 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
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 - In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
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
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.
Customizing : Make the settings in Customizing Basic -> India -> for Logistics General, by choosing Taxes on Goods Movements Account -> Excise Duties Using Condition Technique and -> Settings 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 - When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
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 Master Data®access from the SAP Easy Access screen by choosing Indirect Taxes 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.
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 indicator 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 - 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.
- 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
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 - 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.
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 - 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.
- 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 - 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 sub transaction types, enter the accounts for each sub transaction type as well.
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 - 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 all transactions.
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 configuration step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
- Material Master à Logistics General
1. Go to IMG Define Structure of Data Screen for each Configuring the Material master 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 Sub screens 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 sub screen and ensure that the sub screen 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 sub screen appears.
A small search on SDN SD forum will help you to answer your query.
I will suggest you to visit http://sap-img.com/sap-sd.htm. It will give you the overview of SAP SD module.
Award points if it adds information.
Thanks
Mohan

Calculation procedure TAXINJ and tax key E1 not in table T007A

Hi guys,
While creatig a sales order I am getting the following error:
" Calculation procedure TAXINJ and tax key E1 not in table T007A"
Kindly suggest corrective measures.
Bst regards,
Ashok

Dear ashok
please check for the Tax code assignment which is determined in UTXJ condition.
for the sales order.
and check that tax code is defined as output TAX in FTXP.
for country IN and Tax procedure TAXINJ.
Thanks & regards

TAXINJ , TAXINN & Excise

Dear Experts,
   1) If my tax procedure is TAXINJ, How systems links CIN with TAXINJ ? How the calculation takes place ?
   2) If my tax procedure is TAXINN, How systems links CIN with TAXINN ? How the calculation takes place ?
   3) What is the link between configuration of excise and configuration tax ?
   Kindly clear my doubts please.
Regards,
Prasath

Hi Prasath,
The tax proce (Taxinn or INJ) picks based on blw criteria.
1- ur country assigned to tax proce (obbg).. say IN is assigned to ur proce Taxinn or Inj
2- when u ever u create taxcode (ftxp) it will ask for the country (IN)-- here u r tax code will get link
3- as well, when u create cond record , it will have combination of Tax code , mat/vendor/plant...
4- excise determination is based on the Ex transcion type (GRPO,CAPE,DLFC,OTHER) , here u will assign the gl nbrs against ur plant and ex grp..
hope this will help for ur understanding.. and ref the blw link for config.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/207dd2ad-bf92-2b10-a88b-e3a4a01ca7fc?overridelayout=true
http://www.scribd.com/doc/7216701/MMCIN-Customization-Document

How to decide between TAXINJ & TAXINN

Hello experts ,
Can anyone please tell me with respect to INDIAN MANUFACTURING CONCERN ,how can a consultant decide what tax procedure should be opted for the client ?
Also can anyone pls brief regarding the advantages & disadvantages of using the two procedures ?
Regards,
Anis

Taxinj: Is formula based excise determination, which leads to create tax code in FTXP and assignment of tax code to company code. And later on mantain the formulas for each tax calculations in the J1ID transaction.
In contrast
Taxinn: is the condition based excise determination, wherein you create tax code in FTXP assignment of tax code to company code and then crete the condition records for diffrent condition types in FV11 transaction using diffrent key combination.
The thing is every times the budgets changes you will have to change the formulas which is very time consuming and lots of efforts need to be made for the same. Where as in Taxinn you have to create a new tax code and new condition records no need ot change the old records.. They can be left as they are for reporting purpose.
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.
SAP 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.
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 trhe requirement for different Tax rate.

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

Switching from one tax procedure to another.

Hi,
If a client uses tax procedure TAXINJ for one or more year and later want to shift to TAXINN, what will be the issues?
thanks and regards

Hi
Issues will effect TAX Codes since TAXINN uses less tax codes & you need to make sure transaction keys, G/L accounts linked each other & TAXINN supports J tables.
Regards
Rang

Right now which tax procedure is suitable for indian implementations

hi,
sap gurus,
can any body suggest me exactly that right now which tax
procedure is suitable for indian implementation projects.
or
right now all companies are trying to implement which type of
tax procedures out of TAXINN AND TAXINJ.
plz suggest excatly
regards,
balaji.t

hi,
The main difference is, TAXINN is Condition Based Tax Procedure while TAXINJ is Formula based.
In Tax Procedure (TAXINJ) we have to maintain Tax Codes through FTXP while in case of TAXINN we just need to maintain the condition records.
TAXINN is being used more becuase this Procedure it is more flexible as you can change the condition record any time while in case of TAXINJ if want to make a change in tax then you will have to make the changes in FTXP that is master data.
regards
sadhu kishore

What is the difference between the TAXINJ &TAXINN why the client impTAXINJ

please give me the advise
regards
ram

Dear ramsuresh
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.
thanks
G. Lakshmipathi

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

Similar Messages

Maybe you are looking for