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

Similar Messages

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.

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

Cash Discount after Tax & VAT

Hi , Friends,
My client has a scenario where in some purchase orders , he receives the discount after tax.
when I add the discount (absolute) after tax in the m/08 , the net price changes and the tax is calculated on this new net price which is wrong & not required .
Friends tell me what chnages I need to do so that discount is calculated after Tax & VAt and the ideally what should be the accounting entries in MIGO and MIRO.
if the gross price is Rs 100
tax is Rs 10
and discount is Rs 5.
Thanks in advance

Hi Dgn,
What type of industry sector your client belongs to. But as a standard practise, cash discounts are captured before adopting the Tax or VAT through Invoice.
We will calculate the accounts payable:
Usually below is the scenario for taking the discounts from the vendor in the process of purchaing:
will take your given figures/values:
Eg. (1)
                           Total gross price:      100.00 INR            (as per your client)
                           Discount:                       5.00 INR          (-ve)
                                                                                95.00 INR
then adopt, Tax (10%):                             9.50 INR      (10% on gross ( = 9.50 INR) :   goes to govt. for tax depart.
that means, the total amount:                   85.50 INR      payable to the vendor (A/P)
But, where as in your case /as per client,
(2)
Taking your eg. Total gross price:      100.00 INR            (as per your client)
                           Tax amount: (10%)     10.00 INR            (10% on gross = 10 INR)    : goes to govt. for tax depart.
                                                                                110.00 INR
then taking,       Discount:                         5.00 INR      (-ve)
that means, the total amount:                105.00 INR      payable to the vendor (A/P)
(1): 85.5 INR   < (2) : 105.00 INR
So, in 2nd scenario, your client has to pay more to their vendors & also more tax in the process of purchasing compare to the usually procedure (1). Other wise your client has to pay extra 20.00 INR. Hence option 1 is the rightone.
Pls check with your client again and suggest them further.
Hope you understood.
Regards,
Sapsrin.

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

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,
Manish

Dear 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

MM pricing Tax procedure

Dear All,
There is no tax on purchase. Whatever tax mentioned in the invoice are capitalized/booked under expenses. Should i use FI Tax procedure for it. The illustrative pricing is as follows:
Please suggest an approach for it
Price of item          1000
Sub Total          1000
P & F @2 %          20
Sub Total          1020
Excise Duty @8%          81.6
E Cess@2%          1.63
HE Cess @1%          0.82
Sub Total          1104.05
VAT/Sales Tax /CST as applicable (Say 12.50%)          138.01
Surcharge on VAT @5%          6.90
Sub-Total          1248.95
Freight          Nil
Octroi          Nil
Insurance          Nil
Sub-Total          1248.95
Discount if any          Nil
Total          1248.95

Hi,
MM Pricing Procedure and Tax Procedure are entirely different concepts. In your example you have mentioned about excise duty, education cess and higher education cess, VAT etc. is nothing but tax. Material price, packaging and forwarding charges and discount are nothing but pricing conditions.
MM Pricing Procedure
The Basic thing is Condition Technique. In which there are
1. Access Sequence (M/07) 2. Condition Record (MEK1) 3. Condition Type (M/06) 4. Condition Table.
Tax Procedure
1. Access Sequence (OBQ2) 2. Condition Types (OBQ1) 3. Procedure (OBQ3) 4. Condition Records (FV11)
- Saleel

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

BASB CONDITION IN TAX PROCEDURE.

Hi Guru's
Pb00--100      (Gross Value )
ra01--2           (Discount )
Net value--98
My question is while creating Purchase Order if i give Gross value as 100 as above
and if we add tax code what will the amount transfer to BASB in tax procedure , will it be
net value98 or the gross value100.
Rgds
Kamat.

Hello,
Tax is always based on net payable amount to the Vendor.
Thanks,
Venu

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

Tax procedure-taxinj-----cin

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

Hi Ravi Kumar,
1. TAXINJ - Is a Routine Based that is used in the condition types. it will work on the logic what ever is there in the Routine.
2. TAXINN: - Is a condition Record based. Means we have to create condition records for each and every condition type that you are going to use in the Pricing Procedure.
Since Version 4.7 this TAXINN came into picture and start using this.
And one of the important points is since 4.6 c CIN comes a separate package. But after introduction of 4.7 Version, CIN is coming the SAP Package itself and even in the Customer Master Record also we will find the CIN Icon.
Basically 4 types of Pricing Procedures are used in CIN and are as follows:
1.JDEPOT - Depot Sales
2.JEXPOR - Export Sales
3.JFACT - Factory Sales
4.JSTKTR - Stock Transfer
Hope this Clarifies your Doubts and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

What is difference between tax procedure and pricing procedure?

Dear Gurus,
Would you please let me know the difference between tax procedure and pricing procedure?
Why it is necessary to maintain them separately?
Thanks in advance,
Ranjan

Hi
Tax procedure settings
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.
In MM module, pricing procedure is used during RFQ and PO creation. Total value of material based on all addition and subtraction like discount, surcharge, tax, freight, etc. In this we are defining pricing procedure and linking to vendor and purchase department through the virtual schemas.
Following steps for pricing procedure as,
1. Define conditions.
2. Define pricing procedure.
3. Define virtual purchase organization and vendor.
4. Info Record.
Regards,
Raman

Tax procedure mm

could someone please provide me steps for tax procedures in MM

What 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.
There is two type of pricing procedures,one is our pure MM pricing procedure to calculate Basic price,Discount,freight etc
Second one is taxprocedure this is FI Persons they will configure taxprocedure.In Indian scenarios there is TAX INN and TAXINJ.In defination itself its saying TAXINN is for Condition based tax procedure and TAXINJ is for Formula based tax procedure.
Basically there are two types of taxes that is Excise and sales tax.
In Excise there are Basic excise duty,E cess on Basis Excise duty and finally Secondary and highere education cess on Excise duty.apart from Additional excise duty and Special excise duty its depending upon Material.
In sales tax also VAT,CST are there.
For Calculating these taxes first you have to 1)create atxprocedure in Financial accounting-Financial accounting global settings-Basic settings----.
2)Assign taxprocedures to the country.
3)create Taxcode.
4)Specify Nondeductable taxes to the country.
5)assign G/L accounts for the account key.
Tha above said one is BAsic settings(essential part)
Major part is CIN settings.
1)Excise settings.
2)Company code setting
3)Excise group
4)Plant setting
5)Series group
6)Excise transactions setting
7)Account determanation
8)Master data.
Create Material Master and Vendor master.maintain master data for this in J1ID(Chapter ID,Chapter iD and Material Combination,Cenvat determination and Vendor Excise details.)
Maintain Condition records in FV11 through different Condition types.
Now u can create Purchase order and in Invoice tab and taxes we can see the tax details.
Whatever i explained above its for TAXINN>

Pricing procedure and Tax Procedure.

Hi,
Can any body suggest, how to bring tax values in Condition, in Pricing procedure of MM. Now as per my settings Tax is coming under tax head and MM pricing prodcedure is coming separately, I need ,
Thanks & Regards
Sudhansu

Hi,
Did all you taxes in tax procedure in %!
No access sequence required for your requirement. Create a condition type as ZTFT & maintain
Cond. Class: D
Calculat.type: B
Cond.category: N
Keep BLANK access sequence filed & make it as item condition and then add this condition type in pricing procedure with logic just before calculation of TOTAL price.
Now do create PO with all taxes and now you can see all tax amounts in condition type ZTFT in PO Condition TAB( which flow from tax procedure to MM pricing procedure with a condition type ZTFT)
Regards,
Biju K

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

Discount in Tax procedure

Similar Messages

Maybe you are looking for