Define tax procedure issue

Dear SAP Gurus.,
When we define tax procedure TAXINN in t.code OBQ3 three option is there ,manual, required, statistical these are three check box option is there, when i was tick the check box of statistical indicator after i was going to post a invoice document with tax code A0 in t,code F-22 but system has not accepted to post invoice document,the system showing error message like tax code A0 not defined in the procedure of country IN in procedure of TAXINN,but i have done configuration everything fine.but when i was untick the check box of statistical indicator then i was going to post a invoice document with tax code A0 in t.code f-22 the system accepted to post a invoice document with tax code A0. i have done this in development server, i am facing that same problem also in production server,so now my question is before going to touch with production server i need some clarification,why should tick check box of statistical indicator or why should not tick check box of statistical indicator in t,code OBQ3,if i will tick check box of statistical indicator in t.code OBQ3 what problem i need to face, if i will not tick check box of statistical indicator in t.code OBQ3 what problem i need to face, finally my question is it should be tick or it should not be tick in statistical indicator box in .code OBQ3.please any one help me because i am facing this problem in production server, so before going to touch with production server what i to do

when i was maintaining statistical indicator field in t.code OBQ3 whilst i was trying to post a invoice with tax code A0 in t.code F-22 The system has not accepted post a document,when i was not maintaining statistical indicator field in t.code OBQ3 the system has accepted to post a document with tax code A0.i have done this in development server, i am facing this problem also in production server ,so in production server there is also statistical indicator field are maintained , so before going to touch with in production server we should maintain or we should not maintain statistical indicator field in t.code OBQ3, my senior consultant asked me this questions what i tell him

Similar Messages

Tax procedure for VAT calculation on Base amount + WHT amount

Hi All,
Needed your inputs on definition of tax procedure, to calculate VAT tax where base amount + withholding tax amount are tax base components.
E.g. in AR line item:
     Revenue: 950 (FB70 ->Editing options: calculate taxes on net amount check box is enabled)
     WHT: 50 (5%) (Re-grossing method using)
     VAT: 70 (7%)
To achieve as above how to define tax procedure: current procedure definition as below.
StepCounter-Ctyp----Description-From--To
100--0---     -BASB--Base Amount
117--0---     -J1W1Output Tax----100
118--0MWS1-Subtotal--100----117
120--0---     -MWASOutput Tax------118
Please through some light on this.
Thanks in advance.
SK

Dear all,
Any comments please.
Highly appreciated calculating VAT tax on base amount and WHT (re-grossing up).
Thanks in advance.
SK

Mauritius Country Tax procedure

Hi Friends,
I need to assign tax calculation procedure for a new company code I have created. I want to know the tax calculation procdure for Mauritius Country.
Please help .
Thanks,
Hani

You need to define Tax Procedure based on the applicable rates in SPRO and then got ot Transaction Code -OBBG - Assign Country to calculation procedure
Regards
Jaydip

Tax Jurisdiction Code not defined for procedure TAXSE

Hello,
We are facing any issue with the error "Tax Jurisdiction Code not defined for procedure TAXSE"
We are in mid of production bill run and this is getting very critical. Any pointers would be highly appreciated.
The company code country is SE (Sweden)
We have 2 BPs with address in California, US.
The Billing is successful for both the BPs.
While invoicing, one BP is successful.
The other is going in error "Tax Jurisdiction Code not defined for procedure TAXSE".
Error Details
Jurisdiction code not defined for procedure TAXSE
Message no. FF748
Diagnosis
You have entered a jurisdiction code in a country whose calculation procedure
does not allow the entry of jurisdiction codes.
System Response
Procedure
Check and, if necessary, correct the entry.
Procedure for System Administration
If it is not an input error, check and possibly change the system
settings.
To do this, choose Maintain entries (F5).
Change your calculation procedure so that tax calculation is carried out
using the jurisdiction code.
The BP and the CA setup is exact for both the cases.
Thanks

Hi
Go to the following SPRO config-
SAP Customizing Implementation Guide-->Financial Accounting-->Contract Accounts Receivable and Payable--->Basic Functions--->Contract Accounts--->Field Modifications--->Configure Field Attributes per Activity
Select Change and double-click on field grouping Jurisdiction code.
You will get the following screen.
You have to tick the option Changes plannable and then you will be able to remove jurisdiction code from CAA2
Hope it helps..
Thanks,
Amlan

VAT/Excise calculation - map pricing & tax procedures

Dear,
Pls tell me how to map my blw senerio;
In pricing procedure, i have
A- Gross price
B- Handlying charges
C- Excise on A+B,
here i need to calculate my exise on A+B values and it flows (C) frm tax procedure (taxinn). until here i'm ok.
D - A BC
E - Insurance (defined in pricing proce) on D value,
here i'm unbale to map my price, since the sytem taking A+ B price only, its not taking my D values... I need to map pricing & tax procedures, since Gross price, Han. charges and insurance flows frm pricing proce and Excise frm tax procedure.
Anyone has right solution, pls guide me...

Hello sapjj
Here in your issue, u have to maintain a dummy condition type for excise calculation in your pricing procedure. The excise on A+B will be calculated in pricing procedure itself and not it flows from tax procedure.You have to make a condition type in pricing procedure and mark it as statistical in the procedure so that it doesn't get added to material value.
you are ok till gross price and handling charges, right?
Then you include your dummy condition type for excise amount calculation.Then in the next step calculate a subtotal without giving any condition type and maintaining 'S' in the subtotal field in the pricing procedure.
In the next step include the insurance condition type and calculate it on the subtotal.
This will help
Regards
Gregory Mathews

Questions about CIN tax procedure choice and pricing schemas

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

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

EFFECT OF TAX PROCEDURE

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

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

Non Dedutable tax code issue

Hi Gurus,
I have one issue, User Created PO with non dedutable tax code and Did GR and while doing IR
Invoice Account Details
Posting        Accounting        G/L Code             Act/ mat/Ven             Amount
1                   K                        220000               Vendor code               5050.02-
2                   S                        230000                GR/IR Clearing Acc     4449.39
3                   M                        110950               Material code               600.66
Issue is tax amount is 600.66, Why it is posting Accounting Key M as this is non dedutable tax code, so as per my understanding
System shoud post 600.66 to GR/IR clearing account, so why it is posting to M.
Please suggest where it is went wrong?
Anil

hi,
as in your case you are not availing the cenvat credit, instead you are loading the same on the inventory as you could not avail it.hence the system has loaded the cenvat credit on the material that why you are getting sepearte line item in the accounting doc.
in the tax procedure you would have assign NVV accounting key against the condition type. you define the details of NVV in OBCN trx where you would have mentioned as seperate line item(2) against the posting indicator. if you have maintained (3) against the posting indicator then it would distribute the expense /revenue item.i.e nothing but your GR/IR account
Regards,
velu

Relation between Tax procedure and Pricing procedure

Dear All,
I would like to get more clarity on Tax procedure, Pricing procedure.
a) Why do we have Tax procedure and assigned to Country?
b) If the tax procedure has been created and assigned to Country-IN (in FI module), then why do we need to create pricing procedure with same condition type for purchasing in MM module? We are even creating lot of pricing procedure for Sales in SD module.
Regards
Manivannan R

Hi
Tax
During SD document transactions, tax calculation procedure TAXUSX is only relevant to determine the tax liability accounts for output sales tax. Notice that in pricing procedure RVAXUS, the condition types XR1 - XR6 carry the tax rates and tax amounts - resulted from the external tax system calculation - which is posted to tax G/L accounts. However, the tax accounts are not specified in the pricing procedure but rather in the tax calculation procedure.
Tax codes are the link between pricing procedure and tax calculation procedure.
Pricing
The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
Which sub-totals appear during pricing
To what extent pricing can be processed manually
Which method the system uses to calculate percentage discounts and surcharges
Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
Example
Example of a Pricing Procedure
If a sales department processes sales orders for a variety of foreign customers, the department can group the customers by country or region. A pricing procedure can then be defined for each group of customers. Each procedure can include condition types that determine, for example, country-specific taxes. In sales order processing, you can specify pricing procedures for specific customers and for sales document types. The system automatically determines which procedure to use.
Pricing Procedures in the R/3 System
The standard system contains pre-defined pricing procedures, which contain frequently used condition types along with their corresponding access sequences. You can, of course, modify these procedures or create your own from scratch.
Creating and Maintaining Pricing Procedures
You create or maintain pricing procedures in Customizing for Sales. For more information on creating pricing procedures, see the online Implementation Guide for Sales and Distribution.
To reach the pricing procedure screen from SD Customizing:
1. Choose Basic Functions
2. ® Pricing ® Pricing control ® Define and assign pricing procedures.Select the transaction that you want to execute.

How to copy Value of fright from pricing procedure to the tax procedure

Dear All,
Please note, I have a condition type in Pricing procedure i.e. ZRCO-this is for fright which will be added by the user in the PO.
I want to copy the same value to ZRC1 which is a condition type in tax procedure.
Kindly advise, is there any way we can do this automaticaly. My requirement is to add the fright to the gross price while caluclating the VAT in tax procedure.
Rgds,
Raghavendra N N

Hi,
There is a Field for Manual entries in configutration for Conditions : Condition Types.
Manual Entries Indicator which controls the priority within a condition type between a condition entered manually and a condition automatically determined by the system.
Make the following entries according to your requirements:
_: No limitations
A: Freely definable
B: The automatic entry has priority. If a condition record exists, the condition cannot be entered manually.
C: The manual entry has priority. When you enter the condition manually, the system does not check whether a condition record exists.
D: Cannot be processed manually
Hope this will help.

CIN tax procedure TAXINN

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

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

Discount in Tax procedure

Hi,
    My Client want to make a PO with requirement is as follows
Basic Price -                                 100   (which will come in pricing procedure)
Basic Excise duty -                         10   (which will come in tax procedure)TAXINN
Ecess                                              2   (which will come in tax procedure)
Sub total                                       112
Discount                                          -5   (which will come in tax procedure)
Sub total                                       107
VAT                                                 4   (which will come in tax procedure)
AVAT                                               1   (which will come in tax procedure)
Final value                                      112
Now My question is how to Include condition type of discount in tax procedure. I mean what shall be condtion class, Calculation type, and condition category. As of now i have maintained in condition type in tax procedure in TAXINNcondition class as "Tax" Calculation Type "Percentage" and Condition Category as " tax". But what happening if i give discount as 5 % the so it should be subtracted from the sub total amount , which is showing in calculation but when i do GRN Discount amount is getting added to the inventory (rather it should have been deducted)
   How to solve this Discount issue , it should be subtracted in the inventory rather that adding to that

Hi there,
Check the account key for the discount condition type, and make it deductable in transaction OBCN.
I belive the discount condition type you have included in the TAXINN.
Note: But as far as my experience goes discount should be included in the pricing procedure, an ays it totally depends upon the client's request.
Regards
Sujoy

Error in Tax procedure TAXINJ

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

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

Tax Procedures and MM pricing procedures

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

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

Comparing the Tax procedures of Europe and Asia

Hi
There is a requirement for me to compare and produce an analysis report on the Tax procedures followed by Europe and Asian Countries.
As i have not worked much in this area,i have no clues as of where to start from. Out of my own study i have gathered the following info :-
a) A tax procedure would be defined for every country :- But here we have so many condition types ( more than 20 for each country) and moreover they differ from each other.
In the above case how should we begin the analysis. Should we have to compare condition type by condition type ?
If so then it would consume a lot of time. Please advise.
b) I feel that once this procedure is defined, almost three-fourths of the job is done.
The rest remains to assign a country and define the GL accounts for thr relevant ActKeys mentioned in the respective procedures.
But i wish to know the analysis part of the Tax procedure. Also how can i know that a particular country is following a specific Tax procedure. Is there any place where i can check this out ?
Thanks in advance

Hi llona,
we are having the same situation that our Company Code is having its offices in almost all the countries. So we have created Tax Codes with reporting countries in the same way you told that first character for type of tax and second character for reporting country. Deductible/non-deductible is maintained in the description itself. As per my knowledge it is the better way.
bye
Mallik

Define tax procedure issue

Similar Messages

Maybe you are looking for