Modification in TAXINJ procedure

Dear all,
We are in the process of upgrading our SAP 4.7 to SAP 6.0 EHP7. In our existing SAP 4.7,we are using TAXINJ Tax procedure,
We have already upgraded our DEV server to SAP 6.0 EHP7, After upgrading to SAP 6.0 EHP7 in DEV server, we got issues in SD Module in Tax Calculations,
We want to continue with corrections in TAXINJ procedure in DEV server, then we will go ahead with the same in PRD server.
(removal of jurisdiction codes based tax calculations which was suggested by SAP)
Please advise a solution for the above issue.If anyone has worked on the similar upgrades what are the issues faced.
Best Regards,
LA

we got issues in SD Module in Tax Calculations
(removal of jurisdiction codes based tax calculations which was suggested by SAP)
With the above comments, it is highly impossible to propose a solution. It would be better if you can explain what exactly system was giving issue and what SAP has suggested. May be it would be helpful to all if you copy paste here SAP's comments.
G. Lakshmipathi

Similar Messages

TAXINJ Procedure (Conditon types need to be created)

Hi Experts,
Can anybody explain in detail about TAXINJ Tax procedure.
What are all the Condition types needs to be created to adopt in TAXINJ procedure for India.
So that I can enter Exicse duties ( Basic, Additional, education cess, higher education cess & VAT etc)
rgds
Swamy

Hi,
Please look in the TAXINJ procedure where you will fidn the condition types for your taxes.
Miantain the selected condition types in
Logistics - General>Tax on Goods Movements>India>Basic Settings>Determination of Excise Duty-->Maintain Excise Defaults.
Maintain the GL accounts in
Logistics - General>Tax on Goods Movements>India>Account Determination>Specify G/L Accounts per Excise Transaction
(most important transaction)
Create Tax Code in FTXP Tx and give the set off's.
Reward if useful.
Regards

TAXINN AND TAXINJ PROCEDURE

HI, CAN ANYBODY GIVE ME THE FULL TAXINN AND TAXINJ PROCEDURE WITH ALL TAXES COVERED.
REGARDS
SANDEEP.

hi kumar,
the TAXINN & TAXINJ are tax procedure you will not be able to find in the in sale & distribution follow the below menu path
spro>>finanical accounting>>finanical accountiing global setting>>tax on sale/purchase>>basic setting>>check calculation procedure
rewards if helpful
regards,
Arun prasad C R

CST & VAT configuration in TAXINJ Procedure

Dear Sir,
Could you please let us know , how can we configure the CST and VAT in TAXINJ procedure. i am really confused in tax code assignment in V11 and VK12.
Please give me step by step configuration of CST and VAT in TAXINJ procedure. i checked with SDN before posting and answers are good but i require more clarification to understand the issue.
Thanks
Shibu Chandran

i checked with SDN before posting
Very good
but i require more clarification to understand the issue.
Can you please let me know based on the inputs you took, upto what stage you tried and where you stuck ?? The simple logic is that system will calculate CST or LST based on the regions of delivery plant and ship to party.
G. Lakshmipathi

TAXINJ procedure

Hi,
We are using TAXINJ Procedure.
Maintained for Country India.
Tax codes also properly maintained.
Tax is properly getting calculated in PO and Invoice Receipt.
We are creating a Purchase report.
When we execute a Function module CALCULATE_TAX_ITEM
we get an error
"Tax code C0 country IN does not exist in procedure TAXINJ"
We get this error for all tax codes inspite of maintaining all the
tax settings properly.
Kindly guide me regarding this issue.
regards,
sathya

Hi,
We have maintained necessary settings relevant for tax codes.
Can u say in which settings we need to maintain it.
regards,
sathya

Difference between base type 362 & 363 in taxinj procedure

Currently, we are using base type 362 for base amount BASB in TAXINJ procedure, but in frieght condition type FRB1 tax is not properly getting calculated. If we change the base type to 363, then tax is getting calculated correctly. Can anyone suggest what will be the other impact if we change base type from 362 to 363 for base amount BASB in TAXINJ procedure.

Hi,
363 is used for all sales tax {VAT (Inv or set -off) & CST} and 362 is used for to pick base value to BASB condition type from MM pricing procedure.
Check frieght condition type FRB1 and the frieght value related not added to NET value in PO.
Regards,
Biju K

No TAXINN & TAXINJ procedures found in IDES

Dear Gurus ,
In my IDES , there is no TAXINN & TAXINJ procedure visible in the "change view procedure " Transaction
in Spro -> Financial Accounting ( new) -> Basic Settings -> Define Procedures
What should I do to incorporate these 2 procedures related to taxes in India ?
Will I need to maintain all these conditions manually which are normally seen
in other systems & create new procedure myself ? are there any more associations
to be made alongwith these procedures anywhere else also in spro ?
Please Guide. Thanks in Advance.

hi
IDES is for study purpose
so in IDES you wont find country india version
to get TAXINJ and TAXINN processes you need the country india version component to be installed on the system
catch a basis person for this
check Note 899086 - Guidelines to install CIN on a pre-customised client
regards
kunal

Isnull modification for store procedure

I am trying to add the following Isnull into the ATTACHED
Declare @ZZZZ char(4)
set @ZZZZ = 'ZZZZ'
INSERT INTO dbo.WORKING_IDCARDOUT
(REC_TYPE,
CARD_TYPE,
CARD_STOCK,
GRGR_ID,
GRGR_NAME,
MEMBER_ID,
MEMBER_NAME,
FILLER,
BSDL_TYPE,
PBP,
LETTER_TYPE,
KIT_TYPE)
select distinct
'01',
CARD_TYPE,
CARD_STOCK,
CGG.GRGR_ID,
LEFT(CGG.GRGR_NAME, 46),
MEMBER_ID,
MEMBER_NAME,
FILLER,
space(4),
----- This is the new logic for LETTER_TYPE checking with Common Table - 5/28/2013 -SP
CASE
WHEN @ZZZZ = (SELECT
ISNULL( (SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'INCLUDE_MEIA_REQ_TYPE'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE ),
ISNULL ((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'EXCLUDE_GROUP_ID'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = CGG.GRGR_ID),
ISNULL(( SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'INCLUDE_CSPI_MCTR_CTYP'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = CARD_TYPE ),
ISNULL(( SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'EXCLUDE_PDDS_MCTR_BCAT'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = CARD_TYPE ),(
ISNULL( (SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'INCLUDE_PDDS_MCTR_BCAT'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = BCAT )
----TO BE ADDED HERE
,'ZZZZ')))))
) THEN 'I' ELSE 'C' END as LETTER_TYPE_TMP,
----- This is the new logic for Mini-Kit checking with Common Table - 5/6/2013 -SP
(SELECT
ISNULL( (SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'INCLUDE_MEIA_REQ_TYPE'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE ),
ISNULL ((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'EXCLUDE_GROUP_ID'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = CGG.GRGR_ID),
ISNULL(( SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'INCLUDE_CSPI_MCTR_CTYP'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = CARD_TYPE ),(
ISNULL( (SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'INCLUDE_PDDS_MCTR_BCAT'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = BCAT )
----TO BE ADDED HERE
,'ZZZZ')))))
) as KIT_TYPE_TMP
from dbo.Extract_wt_311_PSI_IDC wrkt
INNER JOIN FacetsReport.dbo.CMC_GRGR_GROUP CGG
ON wrkt.GRGR_ID = CGG.GRGR_ID
sql statement .Please modify as appropriate.
ISNULL((SELECT
CHAR_CFLD3
FROMPHPExtracts.dbo.Extracts_Common_Table
WHEREEXTRACT_ID
=311
ANDDOMAIN_NAME
=
'EXCLUDE_PDDS_MCTR_BCAT'
AND Active
= 1
AND CHAR_CFLD1
= MEIA_REQ_TYPE
AND CHAR_CFLD2
= BCAT
),'ZZZZ')

Looking at that query, my first reaction is that there has to be a more effective, less complicated way of writing it. However, that would require more information about your underlying tables, and more specifics around the particular business problem
being solved. I would also venture a guess that you've inherited this monster from someone else that is long gone from your company. Instead, let's just assume "it is what it is" and just focus on the specific issue you're having.
You have multiple
ISNULL functions nested together with subqueries as the check_expressions. The chain involves starting up another ISNULL function as the replacement_value for the previous ISNULL function. Finally you end the chain with a value of 'ZZZZ'.
In the first ISNULL series, for column LETTER_TYPE_TMP, the value being checked against the ISNULL series result is 'ZZZZ'. A match with the 'ZZZZ' value means that none of the subqueries returned anything different than 'ZZZZ', so the result is 'I',
I'm guessing for "Insert". If anything is pulled up by the subqueries that doesn't match 'ZZZZ', then the result is 'C', I'm guessing for "Change".
The second ISNULL series, for column KIT_TYPE_TMP, is the exact same series, except it is not doing an evaluation against 'ZZZZ'. It is simply returning the result of the first subquery that is not NULL. However, if none of the subqueries return
a non-NULL value, then it ends with 'ZZZZ'.
Here are my SQL formatting recommendations:
Be consistent around the use of commas. All throughout the query, commas are placed at the end of an expression/field before starting the next expression/field. However, the final 'ZZZZ' result of each ISNULL series has the comma starting in
front of it, instead of being at the end of the subquery expression just before it. Not only does this confuse the readability, it also causes somone starting a new ISNULL tier to have to go to the previous ISNULL tier and remember to add a comma at
the end of it. If all the commas were at the end, you would just copy and paste another ISNULL tier, make the specific changes you need, and add another closing parenthesis to the ending 'ZZZZ' line of the ISNULL series.
Do not use tab characters. Not everyone has the same tab space settings on their editors. The code may look nice and formatted for you, but a big giant mess to the next developer who has different settings. Replace all the tab charcters
with spaces. Additionally, going forward in SQL Server Management Studio (SSMS), you can change your settings to always insert spaces whenever you press the tab key. Go to Tools >>> Options >>> Text Editor >>> All Languages
>>> Tabs >>> and select "Insert spaces".
Make sure everything is consistently lined up the same way. The way you choose to line up the code is subjective, but being consistent is not.
Use parameters consistently when they are in place to cut down on hard-coding. I'm not sure why the parameter @ZZZZ was defined only to use it once, and then ignore using it in favor of hard-coding 'ZZZZ' as the final replacement value of each ISNULL
series. If someone were to ever change the @ZZZZ parameter value, without making at least the first ISNULL series match the new value, then the LETTER_TYPE_TMP column would always return 'C' as the result.
Additionally, it appears that one of the ISNULL series tiers is missing from the KIT_TYPE_TMP field. I've added it in so the series matches between the LETTER_TYPE_TMP and KIT_TYPE_TMP fields. However, if it is truly intentional to be inconsistent,
then just remove the ISNULL tier that has this comment directly above it: "-- ***** THIS ISNULL TIER...", remembering to also remove it's closing parenthesis from the 'ZZZZ' line at the end of the ISNULL series.
Here is the final result with my recommendations and your new subquery incorporated.
DECLARE @ZZZZ CHAR(4)
SET @ZZZZ = 'ZZZZ'
INSERT INTO dbo.WORKING_IDCARDOUT (
REC_TYPE,
CARD_TYPE,
CARD_STOCK,
GRGR_ID,
GRGR_NAME,
MEMBER_ID,
MEMBER_NAME,
FILLER,
BSDL_TYPE,
PBP,
LETTER_TYPE,
KIT_TYPE
SELECT DISTINCT
'01',
CARD_TYPE,
CARD_STOCK,
CGG.GRGR_ID,
LEFT(CGG.GRGR_NAME, 46),
MEMBER_ID,
MEMBER_NAME,
FILLER,
SPACE(4),
----- This is the new logic for LETTER_TYPE checking with Common Table - 5/28/2013 -SP
CASE WHEN @ZZZZ = (SELECT ISNULL((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'INCLUDE_MEIA_REQ_TYPE'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE),
ISNULL((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'EXCLUDE_GROUP_ID'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = CGG.GRGR_ID),
ISNULL((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'INCLUDE_CSPI_MCTR_CTYP'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = CARD_TYPE),
ISNULL((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'EXCLUDE_PDDS_MCTR_BCAT'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = CARD_TYPE),
ISNULL((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'INCLUDE_PDDS_MCTR_BCAT'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = BCAT),
----TO BE ADDED HERE
ISNULL((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'EXCLUDE_PDDS_MCTR_BCAT'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = BCAT),
'ZZZZ'))))))
) THEN 'I' ELSE 'C' END as LETTER_TYPE_TMP,
----- This is the new logic for Mini-Kit checking with Common Table - 5/6/2013 -SP
(SELECT ISNULL((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'INCLUDE_MEIA_REQ_TYPE'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE),
ISNULL((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'EXCLUDE_GROUP_ID'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = CGG.GRGR_ID),
ISNULL((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'INCLUDE_CSPI_MCTR_CTYP'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = CARD_TYPE),
-- ***** THIS ISNULL TIER IN THE SERIES APPEARED TO BE MISSING. JUST REMOVE IF IT REALLY WAS INTENTIONAL TO NOT MATCH WTIH THE ISNULL SERIES OF THE LETTER_TYPE_TMP FIELD ABOVE *****
ISNULL((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'EXCLUDE_PDDS_MCTR_BCAT'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = CARD_TYPE),
ISNULL((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'INCLUDE_PDDS_MCTR_BCAT'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = CARD_TYPE),
----TO BE ADDED HERE
ISNULL((SELECT CHAR_CFLD3
FROM PHPExtracts.dbo.Extracts_Common_Table
WHERE EXTRACT_ID = 311
AND DOMAIN_NAME = 'EXCLUDE_PDDS_MCTR_BCAT'
AND Active = 1
AND CHAR_CFLD1 = MEIA_REQ_TYPE
AND CHAR_CFLD2 = BCAT),
'ZZZZ'))))))
) as KIT_TYPE_TMP
FROM dbo.Extract_wt_311_PSI_IDC wrkt
INNER JOIN FacetsReport.dbo.CMC_GRGR_GROUP CGG
ON wrkt.GRGR_ID = CGG.GRGR_ID

Migration of Tax calculation procedure---TAXINJ to TAXINN

Hi Gurus,
Currently we are doing technical upgrade from 4.7 to Ecc 6.0.
Considering benefits and advantages of TAXINN procedure,we want to migrate from TAXINJ to TAXINN so that it will also support CRM.
Kindly help me about the roadmap and guide for the migration.
Regards,
Krishna

Mr. Krishna,
changing from TAXINJ to TAXINN is not simple, as such SAP also has no guide for it.
We tried doing it in one of our upgrades from 4.6B to ECC 6.0 (for a Chemical MFG company in 2008) but SAP said they have no guide lines / notes available for this.
TAXINJ will also support CRM, and SAP will support TAXINJ procedure as long as the client is with the current SAP version.
This is what they told us. And it is logically correct, because when we change tax procedure, we should take care of 4 big things.
1. Open PO update after tax procedure change
2. Open SO update after tax procedure change
3. Change account determination
4. Create new condition records
And more over, we will have to create all access sequences againa and maintian the master data.
It is a risky item... although not impossible. As far as I know and I came to know from SAP, no client who has upgraded has migrated the tax procedure.
For more details contact SAP Helpdesk and put your query.
Thanks & regards
Hameed Parvez

TAXINJ COMPLTE PROCEDURE

HI, all
here i use TAXINJ procedure.
i have made the following settings, 1.J1ID -(maintain all details)
                                                  2. FTXP- (create tax code and maintain condition in that for ex. JMO1 - 16%).
                                                  3. i have maintain the data in( LOGISTIC GENERAL- tax on goods movement- india -basic settings - determintion of excise duty -maintain excise defults.
                                                4.other than that is there any setting for TAXINJ?

in further releases SAP will not release any
    new patches/additions in TAXINJ
I dont think so due to the fact that many clients who are in ECC6 are following TAXINJ. Also SAP recommends not to change over from TAXINJ to TAXINN unless the manufacturer is going in for a complete reimplementation.
user must manually select the correct tax code during PO creation
Not necessary. It can be automated if user maintains Info record in TAXINJ process. Also I dont find much difficulty in going for TAXINJ.
thanks
G. Lakshmipathi

TAXINJ to TAXINN in 4.7 SAP

My client is currently using taxinj ( ED inventorizing ) in 4.7 system. Now they want to have tax credits & going as excise registration. can this be achieved in TAXINJ only Or can we configure taxinn in 4.7 only ?
Please let me know how to proceed in htis scenario. also what are the pre-requisities for the same.

Hi,
In TAXINJ also you can fulfill the tax credit requirement.
Please follow the steps for TAXINJ (Formula Based Tax Calculation):
1-Master data maintainance:(Maintain Chapter Id for Material,material Assessable Value,cenvate,vendor excise,Excise indicator for Plant)
2- Excise Rates-Excise Tax Rate i.e Cess Rates ,Exceptional Material Excise Rate, Quantity based AED and SED
3-Access Sequence-
Menu Path: IMG->Financial Accounting-> Financial Accounting Global Setting->Tax on Sales / Purchases->Basic Setting ->Check Calculation Procedure->Access Sequences.
Standard Access Sequence for tax procedure is JTAX & MWST. So we can use these without any modification. But if there is any specific requirement from client we can create a new Access Sequence by copying and modifying the existing one to meet that requirement.
4-Condition Type-
Menu Path: IMG->Financial Accounting->Financial Accounting Global Setting->Tax on Sales / Purchases->Basic Setting -> Check Calculation Procedure-> Define Condition Types.
For formula based Tax Calculations the MM tax conditions are as follows:
MM Excise Conditions
MWVS-Input tax ,JMO1- IN: A/P BED deductib, JAO1- IN: A/P AED deductib,JSO1- IN: A/P SED deductib, JMO2- IN: A/P BED non dedu, JAO2- IN:A/P AED nondeduct ,JSO2- IN:A/P SED non deductible
LST/CST/VAT Conditions
JIP3- IN: A/P ST setoff, JIP1- IN: A/P CST, JIP2- IN: A/P LST
Service Tax Conditions
JSER- IN: Service tax, JSVD- IN: Service tax debit
5-Tax Procedure Setting
Menu Path: IMG->Financial Accounting-> Financial Accounting Global Setting->Tax on Sales / Purchases->Basic Setting ->Check Calculation Procedure-> Define Procedures.
Tax calculation procedures TAXINJ containing the necessary specifications with grouping of above mentioned tax condition types, for the purpose of calculation and posting of taxes on sales/purchases have already been defined in the standard SAP system for Country Version India. The latest changes of Educational CESS and VAT needs to be added to the TAXINJ procedure.
6-Account Key Setting
Menu Path: IMG->Financial Accounting-> Financial Accounting Global Setting->Tax on Sales / Purchases->Basic Setting -> Check Calculation Procedure-> Check and Change Setting for Tax Processing.
7-Account Key
Standard Acc.keys are:
ESA - Output acquisitn tax, ESE- Input acquisitn tax, JI1- India Basic Excise, JI2- India Addl Excise, JI3- India Special Excise ,NVV- Non-d.input tax dist, VS5- Input Tax PST Gross
8-Assignment of Tax Procedure to Country
Menu Path: IMG->Financial Accounting-> Financial Accounting Global Setting->Tax on Sales / Purchases->Basic Setting ->Check Calculation Procedure-> Assign Country to Calculation Procedure.
Country IN - Tax procedure TAXINJ
9-Define Tax Codes
10-Assignment of Tax Code to Company Codes
This will complete the settings for TAXINJ.
Hope this will solve your query.
Thanks & regards,
Bijay Pradhan

CHANGEOVER FROM TAXINJ TO TAXINN

HI all,
TAXINJ and TAXINN cannot co exist in the same system.
If you are talking about technical Upgrade, then I don't think this would be feasible since old Txn would have got posted with TAXINJ procedure with rates as defined in Tax codes and now after migration to TAXINN in same box, the system would pick value from Condition records.
Just check this basic point of feasibility before we go ahead and look for changes.
In SuX the change is for existing implementation, here at present they have R/3 4.7, and are now in the process of technical upgrade to ECC 6.00; TAXINN is required to be implemented in the upgraded version.
At present they are using around 129 pricing procedures, 25 sales org,220 tax codes in TAXINJ. Suzlon has 21 company codes, 219 plants and 1300 end users the whole nature of group activities results in use of all possible types of indirect taxes in India like VAT, CST, Excise, Service Tax etc...
i have tried to search on sap help, service market place and others but could not come across any document for the change over. However i will try again.
what are the things i need to take care before any implications busisneww point of view, what will be the status of open sales order and purchase orders, and splitting delivery docs. which are under process, what will be the cutoverstrategy.
WHAT WILL BE THE IMPACT AT DB LEVEL AND BUSINESSLEVEL.
RELEASE NOTES OR OSSNOTES, ANY DOCUMENT STEP BY STEP IS REQUIRED asap.
tahanks in advance.urgent
need ur help and guidance, thanks in advance.
sri_cnu

Hi Ravi
Thanx again. It was helpful. I really want to know the answers for these three questions.
1. Is it possible to migrate from TAXINJ to TAXINN during the middle of the year, or is there any restriction, that it has to be done only during the start of the fiscal year.
2. Is it possible to see the data, once we have migrated from TAXINJ to TAXINN (i.e. data in TAXINJ)
3. what are the difficulties that would be there while migrating from TAXINJ to TAXINN.
Please let me know
Regards
Rajaram

CHANGE OVER FROM TAXINJ TO TAXINN

HI ALL ,
TAXINJ and TAXINN cannot co exist in the same system.
If you are talking about technical Upgrade, then I don't think this would be feasible since old Txn would have got posted with TAXINJ procedure with rates as defined in Tax codes and now after migration to TAXINN in same box, the system would pick value from Condition records.
Just check this basic point of feasibility before we go ahead and look for changes.
In SuN the change is for existing implementation, here at present they have R/3 4.7, and are now in the process of technical upgrade to ECC 6.00; TAXINN is required to be implemented in the upgraded version.
At present they are using around 129 pricing procedures, 25 sales org,220 tax codes in TAXINJ. Suzlon has 21 company codes, 219 plants and 1300 end users the whole nature of group activities results in use of all possible types of indirect taxes in India like VAT, CST, Excise, Service Tax etc...
i have tried to search on sap help, service market place and others but could not come across any document for the change over. However i will try again.
what are the things i need to take care before any implications busisneww point of view, what will be the status of open sales order and purchase orders, and splitting delivery docs. which are under process, what will be the cutoverstrategy.
need ur help and guidance, thanks in advance.
We are migrating from 4.7 to ECC 6.00 ( technical upgrade only), at the same time we will shift from TAXINJ to TAXINN,please let us know the steps requred to do this activity.
RELEASE NOTES OR OSSNOTES, ANY DOCUMENT STEP BY STEP IS REQUIRED asap.
CHEERS
SRI_CNU

Hi
Vasu Sri,
I got this document from some body might help u a bit.
Condition-Based Excise Determination in MM (New)
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system can calculate excise duties
and sales tax in Materials Management (MM) using the standard condition technique.
SAP has enhanced the existing tax procedure, TAXINJ, so that it now supports formula-based
and condition-based excise determination. The R/3 System also comes with a new tax procedure,
TAXINN, which only handles condition-based excise determination.
Which Tax Procedure Must I Use?
Existing customers must continue to work using the same tax procedure.
If you switch to a new tax procedure, you cannot display any documents that you have already
posted using the old tax procedure.
If you have worked with formula-based excise determination in previous releases and wish to
continue, you do not have to do anything. However, if you wish to start using the
condition-based excise determination method, proceed as specified below.
We recommend that new customers use the condition-based excise determination and tax
procedure TAXINN.
<b>How Do the New Functions Work?</b>
First, customize the system in the activities listed below. Then, for each material, create one
condition record for each form of excise duty and sales tax that applies, and enter the tax code
for purchasing documents (see below) in every condition record.
When you come to create a purchase order, enter the tax code in each line item. The tax code
tells the system whether to look in the condition types for formula-based or condition-based
excise determination
To set up the new excise determination method, carry out the following activities:
IMG activity
What to do
Check Calculation Procedure
Existing customers: Adjust your tax procedure to
match the changes to TAXINJ. Steps 560-583 are new, as are 593-598.
New customers: Create a copy of TAXINN.
Select Tax Calculation Procedure
New customers only: Assign the copy of
TAXINN to India.
Maintain Excise Defaults
New customers only: Enter the condition type
that you use for countervailing duty.
Define Tax Code for Purchasing Documents
Define a tax code.
Assign Tax Code to Company Codes
Assign the tax code to the company codes that it
is relevant for.
Classify Condition Types
Specify which condition types you want to use
for condition-based excise determination.
Define Tax Accounts
Check which G/L accounts the various taxes will
be posted to. Define G/L accounts for the account keys used in the tax procedure
6 MM
Materialwirtschaft
16.1 Country Version India in Standard R/3 System
Verwendung
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), Country Version India is no longer
delivered as an add-on but as part of the standard R/3 System.
Integration of functions in the SAP Easy Access menu
The functions for withholding tax have been integrated into the SAP Easy Access menu, under
Accounting -> Financial Accounting -> Accounts Payable -> Withholding Tax ->
India and Accounting -> Financial Accounting -> Accounts Receivable -> Withholding
Tax -> India.
You can access all other functions using the area menu J1ILN, which you can call from the
SAP Easy Access screen using the transaction code J1ILN.
Country Version India Implementation Guide
The Country Version India Implementation Guide (IMG) has been integrated into the standard
Reference IMG (see Changes to Structures for Country Version India).
Release Notes
You can access release notes from previous add-on releases using the links below.
SAP Library Documentation
The SAP Library documentation for Country Version India is also delivered on the standard
SAP Library documentation CD (see below).
New and Changed Functions
For information about new and changed functions for Country Version India, see the other
release notes for this release.
Auswirkungen auf den Datenbestand
You do not need to change any data.
Auswirkungen auf das Customizing
IMG activity
What to do
Activate Country Version India for Specific Fiscal Years
Delete the entry ZIND and
create a new entry for IND.
Siehe auch
SAP Library -> Financials or Logistics -> Country Versions -> Asia-Pacific -> India.
Release Notes from Country Version India Add-On (FI)
Release Notes from Country Version India Add-On (SD)
SAP AG
1
SAP-System
Page 9
Release Notes from Country Version India Add-On (MM)
16.2 Condition-Based Tax Calculation (New)
Verwendung
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), a new method for calculating taxes
in Brazil is available, which makes use of the standard condition technique. Tax rates, tax laws,
and special indicators that influence whether tax line items are included in the nota fiscal are all
stored in the system as condition records. An additional tax calculation procedure, TAXBRC, is
delivered for this new method, in addition to the existing one for Brazil, TAXBRJ.
Auswirkungen auf den Datenbestand
You can continue to calculate taxes using the former method: when the system processes the tax
procedure assigned to the country (TAXBRJ), it calculates the taxes externally by calling
function module J_1BCALCULATE_TAXES. We do, however, recommend that you assign the
new procedure TAXBRC and use the condition-based tax calculation functions, as it enables you
to flexibly adapt the tax calculation logic to cover new legal requirements or special customer
needs.
You will need to migrate your existing tax rate table entries to condition records, which you
can do directly from the Tax Manager's Workplace described below. You can check all tables
and subsequently convert the entries, whereby the system generates condition records. After the
initial migration, each time you create or change a tax rate table entry, the system automatically
generates a condition record as needed.
Auswirkungen auf das Customizing
If you want to employ the new condition-based tax calculation, you need to activate it and
carry out all related Customizing activities, under Financial Accounting -> Financial
Accounting Global Settings -> Tax on Sales/Purchases -> Basic Settings -> Brazil
-> Condition-Based Tax Calculation, all of which are new:
o
Activate Condition-Based Tax Calculation
o
Map MM Tax Values to Nota Fiscal Fields
o
Map SD Tax Values to Nota Fiscal Fields
o
Map MM Tax Laws to Nota Fiscal Fields
o
Define Internal Codes for Tax Conditions
o
Assign Internal Codes for Tax Conditions to Condtion Types
o
Assign Tax Rate Tables to Condition Tables
In addition, you need to assign the new tax calculation procedure TAXBRC to the country in
Customizing, under Financial Accounting -> Financial Accounting Global Settings ->
Tax on Sales/Purchases -> Basic Settings -> Assign Country to Calculation Procedure.
A new Customizing tool called the Tax Manager's Workplace is available that enables you to
SAP AG
2
SAP-System
Page 10
make all tax-related settings for Brazil. You access it under the same path as above through
Tax on Sales/Purchases, then Calculation -> Settings for Tax Calculation in Brazil ->
Access Tax Manager's Workplace, or alternatively by entering transaction J1BTAX. You can
use the Tax Manager's Workplace regardless if you use condition-based tax calculation; it
simply brings all tax activities to a single transaction (only the Migration, Nota-Fiscal Mapping,
and Condition Mapping options under the Condition Setup pulldown menu are relevant only for
condition-based tax calculation).
16.3 Changes to Structures for Country Version India
Verwendung
As of SAP R/3 4.7, Country Version India is no longer delivered as an add-on, but forms part
of the standard system.
SAP has discontinued the Country Version India Implementation Guide (IMG) and has added its
activities have been added to the standard Reference IMG as follows:
Activities relating to withholding tax are now located in Customizing for Financial
Accounting (FI), under Financial Accounting Global Settings -> Withholding Tax.
Activities relating to excise duty and excise invoices are in Customizing for Logistics -
General, under Tax on Goods Movements -> India.
As far as the activities under Preparatory Activities are concerned, two of them (Activate
Country Version India for Accounting Interface and Activate Processes) are no longer
relevant and have been removed from the IMG entirely. The activity Execute Country
Installation Program is already included in the standard IMG under the name Localize Sample
Organizational Units. And the other two activities (Activate Country Version India for Specific
Fiscal Years and Activate Business Transaction Events) have been added to the standard IMG.
For information about other changes to the IMG relating to changes in the functions in Country
Version India, see the other release notes.
16.4 Release Notes from Country Version India Add-On (MM)
Verwendung
The Release Notes from Releases 3.0A and 4.0A of Country Version India for Materials
Managment (MM) are listed below. For more Release Notes, see the alias globalization in
SAPNet, and choose Media Center -> Country-Specific Documentation -> Country Version
India - Release Notes.
Release 3.0A
o
CENVAT Credit on Capital Goods After Budget 2000 (Changed)
o
Multiple Goods Receipts for Single Excise Invoices
SAP AG
3
SAP-System
Page 11
o
Enhancements to CVD Solution
o
Pricing Date Control in Excise
o
Order Price Unit in Excise
o
Alternate Assets MODVAT Capitalization
o
Enhancements for 57 F4
o
User Exits for Customer Validations
Release 4.0A
o
Procurement Transactions for Excise Invoices
o
New Transactions Based on User Roles for Incominng Excise Invoices
o
Capture Excise Invoices with Reference to Multiple POs for the Same Vendor
o
Capture Excise Invoice and Post CENVAT in a Single Step
o
Open Schedule Quantity Defaulted in Excise Capture for Scheduling Agreement
o
Accounting Document Simulation for CENVAT Postings
o
Rejection Codes for Excise Invoices
o
Single-Screen Transaction for All Excise-Related Entries
o
Stock Transfer Orders Through MM Route
o
Excise Invoices for Multiple Import Purchases
o
Customs Invoices Can Be Captured Using Logistics Invoice Verification and Conventional
Invoice Verification
o
Material Type at Line Item Level
o
Excise Invoice Capture Without PO
o
Excise Invoice Without PO - Capture and Post in a Single Step
o
Recalculation of Duty and Excise Defaults Restore Feature Available
o
Split of Nondeductible Taxes During Excise Invoice Capture
o
Error or Warning Messages Displayed at the Time of Saving
o
Reversal of Excise Duty
o
MIGO Solution Available as a Note 0408158 (Featuring All Functionalities as in MB01)
o
Excise Invoice Defaults in Excise Popup at Goods Receipt
o
Split Accounting Lines for CENVAT Posting
o
Authorization for Incoming Excise Invoices Extended
o
Authorization Available for Part I Entry at GR
o
Authorization Available for Register Update Transaction
o
User Exit Available for Incoming Excise Invoice Transaction for Defaulting Values
SAP AG
4
SAP-System
Page 12
o
User Exit Available for Incoming Excise Invoice Transaction Before Database Update
o
User Exit Available for Register Update for Validations on Fetched Records Based on
Selection Criteria
o
User Exit Available for Register Update of RGSUM Register
o
User Exit Available for Excise Invoice Create for Other Movements to Default the Excise
Details
o
Register Update Separately Handled for Receipts and Issues Based on Classification Code
o
Ship-From Vendor Can Be Defaulted and Captured in Incoming Excise Invoices for Other
Movements
o
Removal Time Can Be Captured in Excise Invoices for Other Movements
o
Field Selection of Incoming Excise Invoices
o
Transaction Code Customizing for Incoming Excise Invoices
o
Excise Group Setting for Part I Indicator for Blocked Stock, Stock Transfer Order, and
Consumption Stock
o
Multiple Goods Receipts and Multiple/Single Credit Settings Available at Excise Group
Level
o
Rejection Code Master Setting for Posting on Hold Is Available
o
Stock Transport Orders

Migrate from taxinj to taxinn what are the precautions to take, what will

CAN ANYONE HELP ME, FOR MY CLINENT THE REQUIREMENT IS TO CHANGE FROM EXISTING TAXINJ PROCEDURE TO TAXINN, THE ARE CHANGING FROM TAXINJ TO TAXINN ..BCAZ IN THE CURRENT TAXINJ PROCEDURE THEY ARE MAINTAINING 300 TAX CODES FOR 20 COMPANYCODES AND 190 PLANTS, 250 LOCATIONS. 1230 ENDUSERS.
SO THEY ARE COMING ACROSS DAY TO DAY PROBLEM.
BOFORE GOING TO MIGRATE FROM TAXINJ TO TAXINN WHAT ARE THE PRECAUTIONS AND IMPLICATIONS NEED TO BE TAKE INTO CONSIDERATIONS.
FROM BUSINESS POINT VIEW, WITHOUT DISTURBING MASTER DATA,
CAN ANYONE HELP URGENT.
THANKS IN ADVANCE
CHEERS
SRINIVAS.ANGAJALA

hi GK
When u delete the request in ODS or CUBE u want to delete the available data on those targets.
For deleting the datas in the targets u just right click on the ods or cube and give delete data so that if there is a data in the target it gets deleted. this is the main step u want to do when u reconstrcut the request and after doing this u can direclty schedule data to the target.
In targets after completing the data transfer process activate it to get that data in report also. dont forget to do this
In psa level there is no problem u can go and directly delete the request.
Assign points and gain some points in SDN
cheers
bye

Discount after tax in TAXINJ

Hai
My requirement is in TAXINJ procedure my client want discount to be reflected in PO like this.
Base value 1000
BED 14%         140
cess3%         4.2
Discount 2% -20 (this on base value but subtracted after tax)
subtotal   1124.20
Vat 4%          44.96 on subtotal
Total        1169.68
Discount has to be calculated after Tax I have assigned subtotal 6 for the discount condition type and AltCBV as 363 for vat condition type in TAXINJ procedure still I am not able to achieve the final value
Kindly advice how too proceed.
Regards
R.Senthil

Hi Experts,
I am also having same requirement. I have to apply any discount or freight after Tax calculations, means after VAT calculation.
Kindly keep me into loop.
Regards
Rohit
+91-9212510191

Modification in TAXINJ procedure

Similar Messages

Maybe you are looking for