Doubt in tax procedure in CIN
Hi,
we are using TAXINN Procedure in MM.
Do the tax conditions meant for SD like CST, VAT , etc are to be put in TAXIINN procedure for price determination in SD?
I am MM consultant, if I see the TAXINN procedure in SAP, it doesnot have any condition for SD.
please help.
regards
Hi dixit
For purchase tax/excise calculations are calc by using tax condition types(i.e, taxinn condtypes)
For sales tax/excise calc are calculated by using the pricing condition types.(JINFACT,JINSTO,JINDEPO)
regards
lakki
Similar Messages
-
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,
VenkatHi,
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 -
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 -
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 -
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
Gianpaolohi,
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 -
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,
DAVIDDifference 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. -
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 -
Helloooo SD Gurus,
Pl resolve my doubt regarding the exact difference between taxinj, taxinn procedures with live example.
tnx in advance.
yours
venkat gThe 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. -
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. -
Pricing procedure and CIN master
Hi MM Gurus,
I need one simple procedure for creating Pricing Procedure.........and ......creating Excise details and relating and can anybody show how the pricing procedure and excise (CIN) is related .
Regards,
Girish.C.MHi,
CIN Setting:
Check Calculation Procedure
In this activity, you can check and, if necessary, change existing procedures for tax calculation.
Standard settings
Calculation procedures containing the necessary specifications for the calculation and posting of taxes on sales/purchases have already been defined in the standard SAP system for certain countries. Every calculation procedure groups several tax types together into a condition type (for example, output tax or input tax) in the calculation procedure, and determines calculation rules for it.
The calculation procedure determines for which amount the individual condition types are to be calculated. This can be the base amount (total of the expense items and the revenue items) or a subtotal. The entry in column FrmLvl, determines for which amount tax is calculated.
Note
In this activity, the condition types for the check and the possible change provided in the standard system are also displayed. Here, for example, the condition calculation rule, or for which base amount the tax is calculated is determined (= condition type).
Recommendation
If possible, do not change the condition types and calculation procedures provided in the standard system. Only check the standard condition types and calculation procedures regarding whether you can use them for your requirements. If necessary, make changes.
Activities
If you cannot use the standard settings, change the condition types and calculation procedures delivered to meet your requirements.
Procedure (pricing, output control, acct. det., costing,...)
Specifies the conditions that are allowed for a document and defines the sequence in which they are used.
Example
Procedures are used, for example, in the following applications:
· Pricing in sales and distribution
· Applying overhead in Product Costing (costing sheets) and for CO internal orders
· Calculating accrued costs in Profitability Analysis
· Output control (printed confirmations, EDI messages, electronic mail)
· Account determination
· Calculating taxes on sales/purchases
· Calculating accruals in Cost Center Accounting
· Pricing for resource planning
Definition: condition type
Controlling (CO)
A distinction, in overhead calculation, is made between:
· Base condition types, which determine the object for which the overhead is to be calculated
· Overhead condition types, which define the percentage overhead to be applied
In resource planning, a condition type determines the types of resource prices that are stored in the SAP System. These can be absolute or percentage values, for example.
Real Estate Management (RE)
An exact definition of a condition that specifies the amount paid for a specific service.
Condition types include:
· Basic rent
· Advance payment for operating costs
· Pest control
Sales and Distribution (SD)
A characteristic of a condition.
For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
Treasury (TR)
A characteristic of a condition used to classify financial transactions.
Typical examples of condition types are interest, dividends, or full repayment upon maturity. The various parameters specified for the individual condition types determine how the flows are calculated in the cash flow.
Return ->
Definition: condition_type
Condition type
The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Access sequence
With the access sequence you define
· the condition tables used to access the condition records
· the sequence of the condition tables
· which field contents are the criteria for reading the tables
Assign Country to Calculation Procedure
In this activity, you enter the key for the calculation procedure which determines the conditions which are allowed per document and which defines the sequence of the conditions in the document for each country.
Requirements
Each calculation procedure which you enter must contain the necessary specifications for calculating and posting the taxes on sales/purchases. For more information on this, read the chapter "Create calculation procedure".
Activities
1. Assign a procedure for tax calculation to every country with which your company has business dealings.
2. Make sure that the corresponding data for calculating taxes is stored for each calculation procedure which you enter here.
Check and Change Settings for Tax Processing
In this activity you make the necessary specifications for posting taxes. In doing this you specify under a process key the following indicators:
· Tax type
Output tax, input tax, additional taxes, or "not tax-relevant" can be specified as the tax type.
· Nondeductibility of tax amounts
For this, tax amounts are marked as not deductible.
· Posting indicator
Here you specify whether the tax amount is posted separately or distributed to expense or revenue items.
· Tax not relevant to cash discount (Not discount relevant)
This indicator is set only for Canada. If you select it, the system does not take into account the corresponding tax amount when determining the tax base.
Standard settings
Process keys with the most important characteristics for tax amounts have already been set in the standard SAP system.
Recommendation
Do not change the standard settings. Check whether you can use these process keys for your company, making changes only if necessary.
Activities
If you cannot use the standard settings, use new process keys and enter them in your calculation procedure. Do not change the standard SAP process keys.
Note
You must make enhancements to the standard settings if you want to specify a new account key in the "Create calculation procedure" activity. You must create and maintain this key beforehand in the "Settings for tax processing" activity.
Internal processing key
The internal processing keys are used by the system to determine accounts or posting keys for line items which are created automatically.
The processing keys are defined in the system and cannot be changed by the user.
Definition: posting key
Financial Accounting (FI)
A two-digit numerical key that determines the way line items are posted.
This key determines several factors including the:
· Account type
· Type of posting (debit or credit)
· Layout of entry screens
Return ->
Definition: posting_key
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.
Definition: excise registration
Financial Accounting (FI)
An entity in India that is entitled by law to produce any goods liable to excise.
Each entity is assigned its own excise registration number.
Every factory that manufactures excisable goods is required to register separately, so that a business with seven factories requires seven registrations.
Return ->
Definition: excise registration
Maintain Company Code Settings
Use
In this IMG activity, you maintain the data relating to your company codes.
Maintain Plant Settings
Use
In this IMG activity, you maintain excise information relating to your plants.
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.
Definition: excise group
Financial Accounting (FI)
A unit within an excise registration, in India, which keeps its own set of excise records.
Whereas the excise registration reports to the excise authorities, the excise group is a purely internal organizational unit. Each excise group keeps records of all transactions that have to be reported to the excise authorities. When the time comes to present these records to the authorities, the excise registration compiles the information from all of its excise groups.
Return ->
Definition: excise group
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.
Maintain Excise Duty Indicators
Use
In this IMG activity, you maintain the excise duty indicators.
Maintain Postal Addresses
Use
In this IMG activity, you maintain the addresses of various customs and excise organizations that your company deals with.
You use these addresses in the ARE Documents functions. When you create an ARE-1 or ARE-3, you enter the address of the excise department and the customs department involved in the export process. The system then prints their names and addresses on the AREs.
You can then define a default local excise department for each excise group and a default customs department for each series group.
Definition: ARE-1 document
Logistics - General (LO)
A form, in India, that companies have to fill out when they remove excisable goods from their manufacturing plants for export.
The form exempts them from paying excise duty when they remove the goods from their premises.
Return ->
Definition: ARE-1 document
Definition: ARE-3 document
Logistics - General (LO)
A form, in India, that allows companies to sell otherwise excisable goods from their premises without paying basic excise duty. The buyer of the goods must be in possession of a deemed export license.
The ARE-3 states what goods are being removed and which deemed excise license covers it.
Return ->
Definition: ARE-3 document
Maintain Subtransaction Type with Text
Sub Transaction Type
Sub transaction type is used for multiple purposes
Subcontracting:
It determines the subcontracting attributes and determines the accounts for the posting while doing a sub contracting transaction.
Excise removals
Sub transaction type is also used for determining the accounts while doing excise removals.
With in CIN the account determination is based on the transaction type. So normally you can have a single set of accounts for Excise utilization. In case you need alternate account determination for handling various scenarios you can define sub transaction types. The sub transaction types and corresponding account assignments needs to be maintained in CIN customization
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.
Definition: condition-based excise determination
Logistics - General (LO
A method that the system uses of determining excise duty in India.
This method requires you to create condition records for each combination of vendor or customer and material (and possibly other conditions).
When you create a purchasing document, the system calls the tax procedure assigned to India. The tax procedure finds all of the condition records that you have created for that combination of vendor and material.
When you create a sales document, the excise duties and sales taxes are determined by the pricing procedure (not the tax procedure).
Return ->
Definition: condition-based excise determination
Definition: formula-based excise determination
Logistics - General (LO)
A method that the system uses of determining excise duty in India.
This method was used in the Country Version India Add-On and requires you to maintain additional data in the Excise Rate Maintenance transaction, J1ID.
When you create a purchasing document, the system calls the tax procedure assigned to India. Each of the excise duties in the tax procedure has its own condition types, and each condition type is assigned to a formula. This formula instructs the system to calculate the excise duty using the data that you have maintained in the Excise Rate Maintenance transaction.
When you create a sales document, the system determines the excise duties and sales taxes using the pricing procedure (not the tax procedure).
Return ->
Definition: formula-based excise determination
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.
Definition: basic excise duty
Financial Accounting (FI)
The main type of excise duty in India.
It is levied on a wide range of products, for example, foodstuffs, metals, jewellery, leather goods, and machinery.
Return ->
Definition: basic excise duty
Definition: additional excise duty
Financial Accounting (FI)
A form of excise duty, in India, levied on a select range of products, for the most part, textiles.
Return ->
Definition: additional excise duty
Definition: special excise duty
Financial Accounting (FI)
A form of excise duty in India on a limited number of goods, mostly luxury goods, including pan masala, sparkling waters, furs, and yachts.
Return ->
Definition: special excise duty
Definition: cess
Financial Accounting (FI)
In India, a tax on the manufacture of certain products, mostly foodstuffs.
Return ->
Definition: cess
Definition: countervailing duty
Financial Accounting (FI)
A form of excise duty imposed on imports that are subsidized by the country in which they were manufactured.
Countervailing duty (also known as CVD) is intended to make the imports more expensive, thereby redressing any competitive advantage they might have over goods produced locally.
Return ->
Definition: countervailing duty
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.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Deter
Sales Tax Code
The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.
Procedure
For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.
Note
You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
Definition: tax code
Financial Accounting (FI)
A two-digit code that represents the specifications used for calculating and displaying tax.
Examples of the specifications defined under the tax code are:
· Tax rate
· Type of tax (input tax or output tax)
· Calculation method (percentage included or percentage separate)
Return ->
Definition: tax_code
Definition: tax rate
Financial Accounting (FI)
The percentage rate used to calculate the tax amount.
Return ->
Definition: tax_rate
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.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> 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.
Maintain Chapter IDs
Use
In this IMG activity, you maintain the chapter IDs and the corresponding descriptions as per the schedules published by the Central Board of Excise and Customs.
Definition: chapter ID
Logistics - General (LO)
The number given to a material in the schedules of materials published by the government of India.
The schedule lists all materials involved in manufacturing, input materials and output materials alike. It shows how much excise duty is levied on each material.
Each material in the schedule is assigned its own identification code, called "chapter ID."
Example
The schedule contains an entry for ceramic roofing tiles, which are liable to basic excise duty at 16%. The chapter ID associated with these tiles is 6903.10.
Return ->
Definition: chapter ID
Assign Users to Material Master Screen Sequence for Excise D
Use
In this IMG activity, you customize the material master data so that it shows the information relating to excise duty.
Standard settings
Country Version India comes with a screen sequence (IN) that shows the excise duty fields. You have to assign it to each of your users.
Activities
1. Double-click User Screen Reference.
2. Assign all users who need to see the excise duty information to the screen reference IN.
Example
Name Screen Reference
MISHRA IN
Screen Sequence Number
Alphanumeric key identifying the screen sequence. The screen sequence defines the sequence of information units in the material master dialog. A screen sequence is made up of data screens. For information on the screen sequences defined in the standard R/3 system, see the IMG documentation Configuring the Material Master.
Note
When creating a screen sequence, use an alphanumeric key beginning with the letter Y or Z (customer name range). This key cannot subsequently be changed.
Dependencies
You can assign screen sequences to users in the IMG activity Assign Screen Sequences to Users/Material Types/Transactions/Industry Sectors.
Screen reference depending on the user
Grouping of users that determines what screens are displayed in accordance with the user master record when you maintain material master records. It also determines the order in which the screens appear.
Definition: user master record
User and Authorization Management (BC-SEC-USR)
Record that contains important master data for a user in the SAP System.
The user master record contains the assignment of one or more roles to the user. This is how a user menu and the corresponding authorizations for the activities contained in the user menu are assigned to the user. Only users who have a user master record can log on to the system.
Return ->
Definition: user_master_record
Define Form Types
Use
In this IMG activity, you define which form types you want to record in the system. You can only use form tracking for the form types that you enter here.
Example
· Form type: CT3
· Form description: Concessional tax form
· Status: Receive
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 hold 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.
Define Processing Modes Per Transaction
Use
In this IMG activity, you specify which processing modes the user can use in the various Incoming Excise Invoice transactions.
This way, you can tailor the transaction to what your users have to do.
Standard settings
The system comes with three standard transactions relating to the Incoming Excise Invoices function (those that are included in the role SAP_CIN). The processing modes available in these transactions are as follows:
· J1IEX_C
This transaction is for excise clerks: users of this transaction can only capture and display excise invoices.
· J1IEX_P
This transaction is for excise supervisors: they can change, display, cancel, and post excise invoices.
· J1IEX
In this transaction, users can capture and post excise invoices, as well as displaying, changing, and canceling them.
Activities
If the standard settings meet your requirements, do not do anything.
Otherwise, you can adjust the standard settings or you can create your own transactions. To do so:
1. In Maintain Transaction, create a new transaction by making a copy of one of the standard transactions. Give the new transaction a transaction code of your choice.
2. In this activity, enter data as follows:
o Tcode: The transaction code that you have just created.
o Proc. mode: Specify what the users of the transaction will do with the excise invoices.
o Active: Select this indicator to activate the setting.
Example
You might want to create a transaction that only allows users to display excise invoices.
Define Reference Documents Per Transaction
Use
In this IMG activity, you specify for each combination of transaction and processing mode which reference documents you want the users to be able to use.
Activities
If the standard settings meet your requirements, you do not have to do anything.
Otherwise, add the entries that you need to the table: For each transaction, make one entry per combination of processing mode and reference document. Activate each entry for it to work.
Definition: excise invoice reference document
Logistics - General (LO)
A document, in India, that you refer to when you enter an incoming excise invoice.
If you have already posted the goods receipt, you can use the goods receipt document as the reference document. Otherwise, you can use the purchase order (or another purchasing document, such as a be a contract or a scheduling agreement).
Example
In the SAP System, you create a purchase order for 100 bags of sand and send the order to your vendor. Two weeks later, the vendor delivers the sand, accompanied by an excise invoice.
When you enter the excise invoice in the system, you specify the number of the original purchase order: this is the reference document.
Return ->
Definition: excise invoice reference document
Maintain Rejection Codes
Use
In this IMG activity, you define the rejection codes that are used in the Incoming Excise Invoices transaction.
Activities
For each rejection code, enter a code and a description. You can also specify whether the excise duty in the invoice is to be posted to the CENVAT on hold account, instead of the CENVAT clearing account.
Specify Which Movement Types Involve Excise InvoicesUse
In this IMG activity, you specify which movement types relating to goods receipts involve excise invoices.
The system uses this information during the goods receipt procedure. When you post a goods receipt using one of the moevement types that you have specified here, the system prompts you to enter the excise invoice number.
Note
This option cannot be used for processing goods receipts without purchase orders.
Maintain Default Excise Groups and Series Groups
Use
In this IMG activity, you specify which excise group and series group you want to appear in these fields by default. You can make separate settings for different combinations of sales organization, distribution channel, division, and shipping point.
Activities
This activity is optional, unless you want the system to automatically create outgoing excise invoices when you create a customer invoice.
In this case, you must also make the appropriate setting in Customizing for Excise Duty, by choosing Basic Subcontracting Attributes
Use
The subcontracting attributes help determine conditions for a combination of an excise group, a transaction type, and a subtransaction type.
The conditions such as the number of excise items per subcontracting challan, if the nonexciseable materials have to be filtered or not when the subcontracting challan is created, the movement type groups for issues and receipts and the hierarchy of determining the excise base value are mentioned here.
Requirements
Before you continue with this activity, work through the following activities:
· Materials Management -> Inventory Management and Physical Inventory -> Goods Issue / Transfer Postings -> Define Screen Layout.
For the movement type 541, maintain the field Purchase Order as an optional entry or as a required entry.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Maintain OutputTypes.
Maintain the output type. On the Default Values tab, maintain the dispatch time and the transmission medium. Maintain the print parameter on the Print tab. This output type has to be maintained in this activity here.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Assign Forms andPrograms.
Maintain the Program, FORM routine, and the form for the output type.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Printer Determination -> Printer Determination by Plant / Storage Location.
Enter the output device that you use.
Settings -> Maintain Excise Groups, and selecting Create EI (Create Excise Invoice Automatically).
Maintain Movement Type Groups
Use
In this IMG activity, you group movement types together to form movement type groups.
Definition: movement type
Inventory Management (MM-IM)
A classification key indicating the type of material movement (for example, goods receipt, goods issue, physical stock transfer).
The movement type enables the system to find predefined posting rules determining how the accounts of the financial accounting system (stock and consumption accounts) are to be posted and how the stock fields in the material master record are to be updated.
Return ->
Definition: movement type
Utilization Determination
Use
In this IMG activity, you specify which CENVAT accounts are to be debited by the Fortnight Utilization of CENVAT report: When the report calculates how much excise duty you must remit, it automatically proposes which CENVAT accounts the duty should be debited to. Here, you specify those defaults.
You can either:
· Debit all the excise duty to one account
· Debit the excise duty to more than one account, in which case you specify which percentage is to be debited to each account
Example
If you want 50% of basic excise duty (BED) to be debited to the RG 23A account and the remaining 50% to the RG 23C account, you would make the following settings:
Acct name BED perc.
RG 23A BED account 50
RG 23C BED account 50
Alternatively, to debit all of the BED to the RG 23A account, and then RG 23C account, if there is not enough in the RG 23A account, you would make the following settings:
Acct name BED perc. +
RG 23A BED account X
RG 23C BED account X
When you come to run the report, the system takes the RG 23A account because it is the first one you have entered. If this account does not cover the BED, the system takes the RG 23C account instead.
Maintain Minimum Balances for Excise Accounts
Use
In this IMG activity, you can maintain minimum balances in your excise accounts. When the balance in these accounts during utilization falls below this level, the system automatically utilizes funds in the PLA account.
Activities
Maintain the minimum balance amount for the excise accounts. If you have more than one excise group, you can maintain different minimum balances.
Specify SAPscript Forms
Use
In this IMG activity, for each of your company codes, you specify which SAPscript forms the system prints the excise registers with.
Standard settings
Country Version India includes a number of sample SAPscript forms and printing programs, which you can use as follows:
Reg. name Lay. no. Form Tcode/Prog
RG 23A Part I 1 J_2IRG23A_PART1 J_2IRAP1
RG 23C Part I 1 J_2IRG23C_PART1 J_2IRCP1
RG 23A Part II 1 J_2IRG23A_PART2 J_2IRAP2
RG 23C Part II 1 J_2IRG23C_PART2 J_2IRCP2
PLA 1 J_2I_PLA J_2IPLA
RG 23 D 1 J_2I_RG23D J_2IRG23
RG 1 1 J_2I_RG1 J_2IRRG1
RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
RT 12 1 J_2I_RT12_3 J_2IRT12
The layout description can be left blank or an appropriate description maybe filled in. You may not change the register name. You can have your own layouts and maintain the name here. If the output device and number of copies are maintained it is automatically picked up for printing.
Number Ranges
You can maintain the number ranges for all CIN Number range objects using this transaction
Activities
Please maintain the number ranges for the folllowing objects The no nr has to be '01' for all
1. j_1iintnum
At an Excise group
1. j_1irg23a1
2. j_1irg23a2
3. j_1iRG1
4. j_1irg23c1
5. j_1irg23c2
6. j_1ipla2
7. j_1iintpr2
8. j_1irg23d
9. j_1irg1_t ( material level)
10. j_1iconpla ( if Consolidated PLA is used )
At Series group
1. j_1iexcloc
2. j_1iexcexp
3. j_1idepinv
4. j_1i57Fc ( 57F Challans )
Rewards if Helpful
regards
rb -
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 settingIndia 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. IMGSPRO Maintain Basic setting India tax on Goods Movements Logistics general Excise Groups
1.5 Maintain Series Groups
SAPSPRO 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 TextBasic setting
1.8 Determination of Excise Duty
tax Logistics general SAP Ref. IMG SPRO Select Tax Calculation Determination of Excise DutyIndia on Goods Movements Procedure
1.9 Maintain Excise Defaults
SAP Ref.SPRO Determination of ExciseIndia tax on Goods Movements Logistics general IMG Maintain Excise DefaultsDuty
1.10 Condition-Based Excise Determination
tax on Goods Logistics general SAP Ref. IMG SPRO Define Tax Code for Condition-Based Excise DeterminationIndia 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 DeterminationIndia Movements Company Codes
1.12 Classify Condition Types
SAPSPRO Condition-BasedIndia tax on Goods Movements Logistics general Ref. IMG Classify Condition TypesExcise Determination
1.13 Maintain Chapter IDs
tax on Goods Logistics general SAP Ref. IMG SPRO Maintain Chapter ids Master dataIndia Movements
1.14 Assign Users to Material Master Screen Sequence for Excise Duty
SPRO Master dataIndia 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 determinationIndia 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 determinationIndia Movements Transaction
1.17 Incoming Excise Invoices
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Incoming Excise InvoicesTransactions
1.18 Define Processing Modes Per Transaction
Logistics general SAP Ref. IMG SPRO Define Processing Modes Business TransactionsIndia 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 TransactionsIndia Movements Transaction
1.20 Maintain Rejection Codes
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Maintain Rejection CodesTransactions
1.21 Specify Which Movement Types Involve Excise Invoices
Logistics SAP Ref. IMG SPRO Specify Which Business TransactionsIndia tax on Goods Movementsgeneral Movement Types Involve Excise Invoices
1.22 Outgoing Excise Invoices
tax on Goods Logistics general SAP Ref. IMG SPRO Assign Outgoing Excise Invoices Business TransactionsIndia 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 TransactionsIndia 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 TransactionsIndia Goods Movementsting Attributes
1.25 Maintain Movement Type Groups
SPRO BusinessIndia tax on Goods Movements Logistics general SAP Ref. IMG Subcontracting SubcontractingTransactions Attributes
1.26 Utilization Determination
SAPSPRO BusinessIndia tax on Goods Movements Logistics general Ref. IMG Utilization Determination UtilizationTransactions
1.27 Specify SAPscript Forms
tax on Logistics general SAP Ref. IMG SPRO Specify Excise Registers Business TransactionsIndia Goods Movements SAPscript Forms
1.28 Number Ranges
SAP Ref. IMGSPRO Number ToolsIndia tax on Goods Movements Logistics general Ranges
1.29 Message Control
SAP Ref. IMG SPRO Message ToolsIndia tax on Goods MovementsLogistics general Control
Regards,
Rajesh Banka -
Query for MM Pricing Procedure & tax Procedure
Hello,
Can someone advice me on following.
I need one Condition in MM Pricing Procedure : Discount should be reduced after Calculation of Excise duty and Taxes on PO.
Discount should not be calculated for Excise Base amont & or Tax (CST /VAT) base amount.
Calculation
Basic : 100
Freight 20
Subtotal 120 (Excise Base)
Excise duty: 30
Subtotal: 150 ( Tax Base)
Tax @4% 6
Subtotal 156
Discount 10
Total Price 146
My Requirement is how to add Discount at the Place shown above.
Regards,
ManishDear Manish,
After subtotal 120 put in subtotal column 7 and after subtotal 156 put 1.
Truly, I was bit surprised to see your first post, now I got the reason what kept you held.
I tell you why this happens.
I believe you are using tax procedure TAXINN. The routine 362 (in tax procedure) has the program which fetches the data from your pricing procedure and on what amount the taxes have to calculated is the value passed into BASB condition type of tax procedure. One should always read the routine 362 in tax procedure with the help of ABAP consultant. This will give you clarity on the concept of calculation. the subtotal field i.e is KZWI plays important role in calculation.
Currently I do not have access to any test system. If you put the subtotal what I have mentioned the result will come.
Another layman tip I am giving you for tax procedure calculation. where ever you are calculating subtotal just give value from 1 to 7 in subtotal column with different combination one by one and see the results, you will have good idea how the system behaves. Say if you put subtotal as 1, the system response will be different from if you give subtotal 4.
Why this is important to understand is when in future if you are going to add any new condition type you will know how the system response is towards the tax calculation.
That is why I suggested you to read the routine 362.
Moreover, if I see your procedure, excise duty, CST and LST should not be calculated on freight charges. Legally this is not correct. Freight charges are in the preview of service tax. In many implementations I came across the similar scenario where the client insisted on the similar procedure. This all happens due to ignorance of client. We have shown the client the official documents as well we also arranged the official meetings with excise commissioners to clear there doubt.
This scenario is usually insisted in the case of freight billed what client says. this is not correct.
Regards
Rajesh -
Tax Procedure - Condition Base Value Inclusive Freight
Hi Experts,
I have created a routine and assigned it in Tax Procedure - BASB Condition Type.
In that routine i have written the coding like ZWRBTR = XKAWRT.
Here XKAWRT holds the value as Net Value + Freight Value.
Problem is while opening Purchase Order in Change Mode,
If i directly go to Taxes Tab the Base Amount of the BASB condition type is displaying as 0.
But the Material No and the item No are displayed correctly.
But if i go to the Conditions Tab then Taxes tab this value is getting updated.
My Doubts are
Do we need to assign the routine in Pricing Procedure also?
While opening in change mode the values are already saved in the database,
then why does the standard program is not picking the value to screen?
Am i need to write any logic in my routine to achieve the above?
Regards,
Ragunathan.RHi,
Its not helping to solve my requirement.
Can i get the links for assigning the routine in appropriave condition types in Purchase Order.
Regards,
Ragunathan.R -
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 -
Whta is the standard pricing procedure in CIN INDIA
i want to take a standard pricing procedure ,so what is the standard pricing procedure in CIN INDIA
i want to include the condition like
<b>base price
maximum retailing price
customer discount
material discount
excise duty
VAT
educational cess
additional cess duty</b>
i want to know what should be the customer pricing procedure
and document pricing procedurehi,
pl use TAXINN. Remaining as usual.
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.
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.
Regards,
Rajesh Banka
Reward points if helpful.
Rajesh Banka
Posts: 1,308
Questions: 7
Registered: 11/21/06
Forum points: 1,800
Re: Taxinn tax procedure settings in SD pricing
Posted: May 6, 2007 11:34 AM in response to: Sunil Kumar Garg Reply E-mail this post
Impact on Pricing Procedure & Condition Record:
Another Important difference between TAXINJ & TAXINN is that in TAXINJ along with formula in Tax Code, you also have to maintain condition record & there are 2 condition types for Basic Excise duty & similarly other excise duties. in one condition you maintain the actual excise duty % & in other you main as 100%, which will be a copy of actual excise duty. But in TAXINN, instead of 2, you require to maintain only one condition type for each excise dity like JEXP for Basic Excise duty & similarly for other excise duties. You require to design pricing procedure accordingly.
source forum thread :
<a href="https://forums.sdn.sap.com/click.jspa?searchID=2814520&messageID=3397693">source thread</a>
thanks.
Sadhu Kishore
Maybe you are looking for
-
Word file will not scroll to printer in classic
I'm using microsoft office 2001. When I want to print a word file (using classic envir.), it stops until printing is completed. (I have a Canon i550 ). When working off (OS 10.2.8) Appleworks, the file quickly scrolls to printer and I can go on to so
-
Transformation routine on 2 different targets fields
Hi gurus, I have been trying do some ABAP transformation routines, I did 1 and it was good works fine, then I tried to create another transformation routine on a different target field of the same DSO, and for some reason what I did on the global dec
-
I am running OSX 10.4.11 on my iMac; Firefox automatically updated to version 12, and now it will not run on my computer. Is there a way to deinstall the new version while keeping my saved bookmarks, etc? If not, how do I deinstall 12 and reinstall t
-
Archive and Install Time? Clarification?
I have several symptoms going on simultaneously that lead me to think that I need to try an Archive and Install. 1. Mail loses all settings and data on a daily basis. 2. Trying to install Quicken via CD that is known to be good gives bad disk error m
-
Plus de mails sur iPad depuis iOS6
Bonjour, Depuis la maj iOS6' impossible de recevoir mes mails bbox (compte imap) sur mon iPad. Je les reçois sans pb sur mon iPhone. J'ai essayé en supprimant puis en recréant le compte, en éteignant / rallumant l'iPad, mais rien n'y fait. Avez vous