TAXINN ISsue

Hi Team,
I am working on TAXINN procedure on one project.
i have made a dummy tax code Z0 through FTXP . No tax rate is maintained in it.
I have to procure one material for which various taxes are applicable
Excise duty (16%) , Local Sales Tax (10%).
I have maintained the Tax conditions on plant/material/vendor level.
i have created a Purchase Order for the same.
i have added a freight condition (100) in PO , as we have to pay the freight to freight vendor.
no tax condition is maintained for freight vendor.
I have received the material in Stock
i have done the IV for MAterial supply.
when i am doing the IV for the freight condition (planned delivery cost), then also excise and local sales tax gets loaded on it.
means on simulation, systems shows
freight 100
excise 16
Local sales tax 11.6
actually only 100 has to come on simulation.
regards
Arunesh

Hi,
I am using one dummy tax code for which no value is maintained.
excise rate and other tax rate is maintained at material/plant/vendor level for this material.
i have done the MIRO of the material against dummy tax code. rsults for this is correct
now when i does the MIRo for freight condition for freight vendor, then also system is picking the tax value.
the tax rate calculation is happening on this condition also
I need help in it.
I ahve checked the pricing procedure also.
the freight is calculated only after tax calculation
Arunesh

Similar Messages

CIN TAXINN Issue

Hello Friends
i have some issues regarding TAXINN.
i have done the following config.
1. OBYZ
2. OBBG
3. OBCN
4. OB40
Create Tax Codes in FTXP and Maintain Tax Rates in FV11 for conditions.
I have following Questions.
1. Do we Need to Have Tax Jurisdcition for TAXINN at all i-e do we have to maintain anything in <OBCO> and <OBCN>? as i have read that in TAXINN al the codes created are summy only in FTXP?
2. my biggest concern is that if i dont give OBCO and OBCN settings, then i am not able to use those codes for Misc FI Invoices, i-e in FB60 and FB70.
Please advice first that my understanding is correct, second how we can use these codes in FB60 and FB70, as when i use them it gives me error saying tax code xy does not exist in TAXINN, which goes away by maing OBCO and OBCN settings, but i get another error then sying Tax code invalid for Tax Jurisdiction IN00? i am wondering if i need to have tax jurisdiction for TAXINN at all or not?
King

Hi,
The Tax Jurisdiction Code is not necessary for TAXINN as the tax percentages are same throughout India.
In OBCN, you define the account keys which are used to transmit the values of the transaction based on
the condition types that you have defined in tax calculation procedure TAXINN and posts in relevant GL account
through OB40 for the % you have given in FTXP, which is mandatory.
Regards,
Sadashivan

Issue Related to Price & Taxinn

Dear Gurus,
I have a scenario
There is a component that is purchase for Basic price of pattern = 19530   Rs (X)
For this there is also pattern value                                                  = 93        Rs (Y)
Total value                                                                                = 19623 Rs
On 19623 Edu Duty10% + 2% Ecs + 1% SHECs Should be calculated .But During VAT Calculation shod be calculated excluding 93 Rs (Y Shown above)
How can I map this in SAP Taxinn & Pricing Procedure.Please explain
Thanks in Advance

hi,
this is to inform you that,
you need to check the function module PRICING_COMPLETE
http://erpstudies.com/sap/61-sap-basic-tutorials/1162-sap-message-ve108-in-pricing-analysis-for-a-sales-document.html
check and come back
balajia

TAXINN SD issue

is Tax code necessary for excise determination in TAXINN in SD Scenario? While maintaining condition record ( JEXP) for Excise access sequence JEXC doesnu2019t has Tax Code field Whereas for Sale Tax determination ( JCST/JLST) access sequence JLST /CST which has Tax code field . (In TAXINN we create Dummy tax code (blank))
is it true whatever I have written ? If yes then what is use of tax code where it triggers in FI Posting? Why we use only for Sale Tax not for Excise duty?

hi Rajesh & sarvanad.
If u go to SAP Std condition type & access sequence provide for CIN in SD (TAXINN) While maintaining condition record ( JEXP) for Excise. Access sequence JEXC doesnu2019t has Tax Code field . do u think we should modify that create field for Tax code ..... Pl check in system & answer the question .......I hope u understand what i want to ask.

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

CIN: Alteration of base value for CST in TAXINN

Hi,
In our business process there is a requirement that CST should not be calculated only on Basic Price + Excise Duties (BEDEcessSEcess) rather base value for CST should be Basic Price + Excise Duties (BEDEcessSEcess) + 2 Additional Surcharges as mentioned below:
Basic Price     100.00
BED (10%)     10.00
Ecess (2%)     0.20
SEcess (1%) 0.10
Additional Surcharge1     4.00
Additional Surcharge2     6.00
Base for CST 120.30 (100100.20.14+6)
CST (2%)     2.41 (2% of 120.30)
Total Value     122.71
The tax procedure being used is TAXINN
Is there any standard routine or subtotal available so that by using this in PO Calculation Schema and TAXINN the base value of CST can be modified as desired?
Please provide some useful ideas.
Thanks in advance
Edited by: Sapdear on Aug 29, 2011 8:22 AM

Hi,
The additional surcharges are condition types in the calculation schema of PO whereas CST is being calculated in Tax Procedure TAXINN so how "From" and "To" functionality can work. The surcharges are getting calculated in PO Pricing and CST in tax procedure TAXINN (both at different places)
We want to use a tax code (BED10%Ecess2%SEcess1%+CST2%) to calculate Excise Duties and CST by additional surcharges taking into account.
Can any one provide some idea to resolve this issue?
Thanks in advance

Issue of Excise Duties in Foreign Currency in J1IIN

Dear All,
As one of my user has created Export Excise Invoice on 31st of May. Unfortunately Exchange Rate was not maintained by him for currency Euro in OB08 and While creating the Excise Invoice all the duties came in EURO but the document currency is INR. Please find below screen shot.
Now my query is, Is it possible to update/convert these Excise Duty Values in INR without cancelling this document. Because while creating ARE1 all the data are coming in EUR only.
Regards:
Abhishek

Hi,
    Could you please replicate the scenario in Dev / QAS and check whether the excise duties are calculated correctly in J1IIN when the the billing currency is EUR, and OB08 is correctly maintained.
    Repeat the same scenario without maintaining the currency conversion factor in OB08 and compare the excise invoices. Revert back with the results.
    I guess that the issue is not because OB08 was not maintained. Found a similar issue mentioned in the notes: 957377 - Excise base appears in foreign currency in J1IIN for TAXINN and 936007 - Excise base not converted to INR in J1IIN/J1II for exports You may check the notes if its applicable for your SAP release.
Regards,
AKPT

A.R.E ISSUE

DEAR ALL
Can any one explain or if some one has faced the same problem
1. Under Duty rates- In Ad Valorem tab: BED is not appearing
2. In ARE print output Under "Amount of rebate claim" tab : Material Number is appearing instead of amount of rebate to be claimed. Kindly also tell that while creating ARE we can take the print output once, can we take twice while posting?
Regards
SB

Hello Sandeep,
Regarding your first issue. Please check the following, If you are using tax proceedure TAXINN then check whether your export priciing procedure is classified for BED condition types under CIN customizing
Also please check BED condition type is classifed to JINFAC too.
If you are using TAXINJ procedure check whether you have maintained
BED percentage in J1ID.
Regarding your second issue, You have to sit with your apaber,s to find out the exact problem. This is nothing to do with cin cofiguration.
Regards
MBS

Tax Code in procedure TAXINN is invalid

Dear Sir,
Tax Code in procedure TAXINN is invalid
When from SD module our sales person is trying to release billing document to accounts through FV02 they are geting the above referred error message and the accounting document doesn't get generated and/or released.
They says that the error is in FI module but I am unable to resolve the issue.
Kindly guide
Thanks in anticipation and Regards
Chirag Shah

Hi,
in first Step check Condition record for your TAX code for the time period in which you want to use. Tcode FV11
Use proper Account key (OBCN)for the tax code in TAX procedure(OBQ3) TAXINN and use the appropiate Account which allows the tax code to be posted in GL using Account key(OB40).
Also check the nature of Condition Type(OBQ1) in Tax procedure.
Assign the Tax code to country also, follow the path .
SPROu2192logistics general u2192 tax on goods movementu2192 Indiau2192 Basic settingsu2192determination of excise dutyu2192condition based excise determinationu2192 Assign tax code to company code.
Regards
Arun

Tax condition types issue in sales order

Hi Friends,
I am bit lost with the following issue. I have searched sdn and other SAP forums for this. There were similar issues discussed but they didnu2019t solve my issue. There was exactly similar issue but it was unanswered. So I am posting the issue here to get some inputs.
This is the Indian tax scenario. I have configured pricing procedure where I have JVAT and JCST. If the company is selling to customer in the same state where company is located letu2019s say region 05 JCST 2% applicable. If the customer is outside region 05 then 5% JVAT should applicable.
=> In the pricing procedure it was like
150 0 JVAT
160 0 JCST
Both will be calculate on the gross value.
=> I have created two new tax classifications for customer master.
JCST   2   Tax liable outside region 05
JVAT 3    Tax liable inside region 05
So in the customer master I have both JCST and JVAT. I have created a customer with region 05 and in customer master under Billing document tab I have entries like below
Country    Name   Tax Category   Name   Tax classification Description
IN              India        JCST                IN: CST              2                  Tax liable outside region 05
IN              India        JVAT               IN: VAT              0                  Tax Exempt
=> I have created condition record for JCST with the following key combination
Country u2013 IN
Region of dlv. Plant u2013 05
Region u2013 05
TaxClass1-Cust. -- 2
TaxCl.Mat u2013 1
Amount u2013 2 percentage
Tax code u2013 A1 (TAXINN A1 2% Output tax)
=> With the above condition records maintained for JCST and maintaining tax classification as 2 for JCST and 0 for JVAT, I assume in Sales order SAP should calculate tax JCST 2 percentage. But in sales order SAP is not considering JCST and JVAT. For JVAT it makes sense as it does not have condition records. But I didnu2019t get the reason for not getting JCST. When I checked analysis and click on JCST condition type it says condition record is missing. Surprisingly when I click on the access details it shows u201CTaxClass1-Cust. as 0u201D it didnu2019t show as 2 as maintained in the customer master.
When I change the Tax classification for JVAT from 0 to 1 or from 0 to 3 in the customer master, in the analysis when I click on access details for JCST it shows tax classification maintained for JVAT that is as 1 or 3 so it seems SAP is not considering JCST in customer master at all. Why is that so?
The access (condition table) for JCST and JVAT are same.
Any inputs?

Hai SAP_2006,
We are also having similar requirement and inform the USER to maintain
In our customer master we gave like
Customer master:
Sales area data
Billing documents
JTX1     Tax Jurisdict.Code d     1     Full Tax 12.5%
JTX2     Tax Jurisdict.Code d     1     Full Tax 12.5%
JTX3     Tax Jurisdict.Code d     1     Full Tax 12.5%
JTX4     Tax Jurisdict.Code d     1     Full Tax 12.5%
To get LST we maintain
Country u2013 IN
Region of dlv. Plant u2013 05
Region u2013 05
TaxClass1-Cust. -- 1
TaxCl.Mat u2013 1
Amount u2013 12.5 percentage
Tax code u2013 A2 (TAXINN A1 12.5% Output tax)
To get CST
Country u2013 IN
Region of dlv. Plant u2013 05
Region u2013 06
TaxClass1-Cust. -- 1
TaxCl.Mat u2013 1
Amount u2013 12.5 percentage
Tax code u2013 A2 (TAXINN A2 12.5% Output tax)
In case if they want CST 2%, then user has to go
Sales order header Biiling
Alt tax Classification : Shouls change the Blank to 2 in the 1 box out of 4.
for that we maintained condition record as
Country u2013 IN
Region of dlv. Plant u2013 05
Region u2013 06
TaxClass1-Cust. -- 2
TaxCl.Mat u2013 1
Amount u2013 12.5 percentage
Tax code u2013 A3 (TAXINN A3 2% Output tax)
This doesn't require to change customer master regularly and default system finds LST or CST 12.5 unless they change to 2% system will not change automatic. So CST 2% Vs CSTfull tax risk is also avoided.
Regards,
Mani

Issue in Return sales, condition value calculation.

Hello All,
I am creating return sales order (order type-RE) with reference to a Billing document, and reducing the quantity while creating the sales order (Example: Ref billing quantity-60 and sales order quantity-30). Here even though the quantity is reduced to 30 PC the basic excise duty value shown in the sales order is same as in the reference billing document (with 60 PC quantity).
In pricing procedure for condition type (basic Excise duty) calculation type used is 355.
Kindly help me out to over come this issue.
Regards,
Manoj

Your post is not sufficient to understand your requirement. Let me know whether your client are into TAXINJ or TAXINN. Also as requested already, share your pricing procedure screen shot. Moreover, have you checked the Analysis screen from condition tab of that sale order ? If not, better check there which will give a clear picture. Finally, ensure that there is no manual condition type JMAN used in billing document in which case, as per routine 355, system will copy that value.
G. Lakshmipathi

Excise duty condition type and Purchase Order Print Issue

Dear Friends,
We have a issue related to Purchase order print out.
We are maintaining TAXINN.
We have implemented CIN and we are maintaining Excise Conditions i.e. Basic Excise in JMOP
In FV11 we are maintaining values for JMOP with plant and material Group combination.
In Purchase Order Tax calculation is happening correctly.
But issue is to find the value of taxes for Purchase Order Print.
We are using function module CALCULATE_TAX_FROM_NET_AMOUNT
and passing values of Company Code, Country, Currency, and Base amount to get the entries in condition types.
But we are not getting any entry even after passing the values.
How we can get these values in JMOP.
Regards
Kant

Why do you want to calculate the taxes during the PO Print when you are getting correct values in PO itself?
Modify your print program with pulling values directly from EKPO/ EKKO Tables and display it to Spool.
check with ur ABAP Person

Excise Indicator issue

Dear Gurus,
In our company we are following TAXINN and our Plant and regular Customers are applicable for Excise.
If Customer is Excise relevant, in J1ID, under 'Customer Excise Details' we assign 'Customer Excise Indicator' as '1' and if not relevant for Excise, we assign the indicator '3'. Same is the case for the Plant.
For regular Customer and regular Plant the combination under 'Excise Indicator for Plant and Customer' is 1 : 1 = 1.
For SEZ customers and regular Plant, the combination is 3 : 1 = 3 (combination is not relevant for Excise).
Now my issue is after maintaining like this and maintaining normal Excise condition record for BED as 8%, how to make the system take zero Excise duty for SEZ customer only?
Though Excise Indicator '3' is given, where are we saying to the system that if Excise Indicator is '3', then pick zero value for calculation purpose in Pricing Procedure of Sales Order?
What is the configuration I am missing? Help me with this, as it is an immediate issue for me.
Best regards and thanks in advance.

DearAA,
If I am not totally wrong, Customer Tax classification is for Sales Tax (which is maintained in CMR under Billing Tab in Sales Area Data screen) and nothing to do with Excise duties. I need to change the Excise duties differently for different customers of the same group, distribution channel and division.
Dear Prashanth,
I am not doing Exports or Deemed exports, ya, I realise I gave wrong information regarding SEZ. I meant to say that if the customer is like SEZ customer who is not liable for Excise duties, how to prevent the system from populating excise values in the pricing procedure. My customers are not SEZ customers, but regular Dealers, who have Excise exemption due to some special circumstances.
Any help plzzzz . . .

Excise Pricing procedure for Stock Transport Order in MM with TAXINN

I am an SD guy running STO from manufacturing plant to sales depot
AND not able to create JEX proforma excise invoice from NL
to TEST my configuration, I created excise invoice in J1IS with respect to goods issue from NL from UB means configuration is ok
BUT base amount in J1IS is coming as zero because of missing excise conditions in MM STO pricing procedure
CAN anybody give me a sample EXCISE pricing procedure for STO
AND do i need to create records for the condition types in FV11 OR MEK1 please clarify
I know that calculation type 362 attached to BASB in TAXINN has something to do with this
I am able to see chapter ID in J1IS
And the relation between condition types in TAXINN and excise pricing procedure for STO
And I am able to create excise invoice in J1IG with zero excise values
I also maintained pricing procedure determination for JEX in OVKK that is document pricing procedure N pricing procedure JINSTOCK
I think my explanation is sufficient enough
please give A sample of TAXINN

Hi Yoga,
Here u not need to do VL10b.just follow this steps and try.
In PO,Document type is UB and Item Category is U.
After creating PO,In MB!B with reference that PO number and using movt type 541
then u can see that stock in Transit.Now u do GR with respect to PO number.
Thanks & Regards
Suresh.
> Hello MM Gurus,
>
> I am doing Stock transport order between 2 plants
> under same company code.
> I have maintained all the required settings.Following
> is the process flow.
>
> 1.Creation of Purchase order with document type
> UB.(ME21N)
> 2.Creation of outbound delivery with respect to
> Purchase order.(VL10B)
> 3.Post Goods Issue from the supplying plant. (VL02N)
> 4.Creation of Excise Invoice in supplying plant.
> (J1IS)
> 5.Goods receipt at the receiving plant.(MIGO)
>
> While I am doing Goods receipt in the receiving
> plant, system is giving an error
> message "Maintain Vendor for the Excise Invoice" -
> Message no. 4F185.
> Why this message is coming and how to resolve this?
>
> Thanks & Regards
> Yoga

CIN configuration in TAXINJ and TAXINN !!

Friends !!
Please help in configuring TAXINJ and TAXINN for VAT, Higher Edn.cess.If possible send me screen shots for the same and how to maintain taxcodes.
Thanks.
Yours sincerely,
sreedhar

Dear sreedhar kodali,
CIN Means Country India Version
In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenarios. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself.
Some info on CIN Configuration (it may not appear as understandable below, but if you check on screen, it will be understood better)
Country Version India comes with four pricing procedures as follows:
- JINFAC (Sales from manufacturing plants)
- JINEXP (Export sales)
- JINDEP (Sales from depots)
- JINSTK (Stock transfers
CIN: IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings > Maintain Excise Registrations
In this IMG activity, you maintain the data relating to your excise registrations.
- Enter each of your excise registrations, specifying a four-character code for each Excise Registration Ids
In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
- For each excise registration in your business create a registration ID, and state:
- Which taxes the registration covers (additional excise duty, special excise duty, and cess) Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
- The maximum number of items to be printed on each excise invoice
- Whether you are allowed partial CENVAT credits
Maintain Registration ID NUMBER, Excise code number, excise registration number
ECC Number: Specifies the organization's ECC number.
Excise Registration Number: A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division: Specifies the excise division in whose area the excise registration is located.
Excise Collectorate: The code of the excise collectorate in whose area the excise registration is located.
Indicator for confirming, AED usage Additional Excise duty Percentage.
These are livable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty. Example - Additional Excise duty is livable in case of textile products, tobacco and sugar.
Similarly for SED CESS Number of Items in Excise Invoice Shows the maximum number of line items that the authorities allow per excise invoice.
Dependencies - This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements. This information is used to split the transfer postings' items into multiple subcontracting challans.
Excise register set description: Description of the excise registers set.
Partial CENVAT Credit: Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account
Dependencies - When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
This information is also shown when you post the vendor's excise invoice.
Maintain Company Code Settings.
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings.
It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
Indicator for providing debit account overwriting
Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
Automatic balance Indicator - Excise year start month. The calendar month marking the beginning of the excise year. This start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
Excise invoice selection procedure :Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received. Number of excise invoices to be selected Indicates the number of excise invoices that needs to be selected in the excise invoice selection.
Days to be considered for excise invoice selection Number of days from document date for excise invoice selection.
Example - If the value of this field is 20 and today is 28-03-97. The excise invoice selection will show the related invoices only for the period 08-03-97 to 28-03-97.
Document type for TDS FI posting: Financial accounting document type for TDS posting.
Document type for FI posting on Utilisation Financial accounting document type for TDS posting.
Indicator for item level excise duty round off - This indicator is to be used for deciding whether Item level excise
duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
Rounding off of Excise duty for outgoing excise invoice - You can round off the Excise amount to be paid during an outgoing
Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
Immediate Credit on Capital Goods - Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts. The rest is posted the CENVAT on hold account, for use in the following year.
CVD Clearing Account - Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
Exchange rate type - Key representing a type of exchange rate in the system.
- You enter the exchange rate type to store different exchange rates. Example - You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
Exchange rate type to be used for Export excise duty converts - When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
Maintain Plant Settings - In this IMG activity, you maintain excise information relating to your plants.
Plant Settings - In this activity, you maintain excise information relating to your plants.
For each plant:
- Specify whether it is a manufacturing site or a depot.
- Assign it an excise registration ID. - You can assign the same ID to more than one plant, if required.
Depot - Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
- Number of goods receipt per excise invoice.
- Multiple GR for one excise invoice, Single credit
- Multiple GR for one excise invoice, multiple credit
Maintain Excise Groups - In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
Excise Groups - In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
Recommendation - Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
If your company has only one set of excise registers, then you need to maintain only one excise group.
1. Create one excise group for each set of registers that you need to keep.
2. Assign the excise groups to plants.
3. Maintain whether this Excise group is for a depot or not.
If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'.   Alternatively if you want to availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock .
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock. Excise Group Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration. - In define excise groups in Customizing.
Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to. At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
- GR Per Excise Invoice
- Multiple GR for one excise invoice , Multiple credit
- Multiple GR for one excise invoice , Single Credit
Create Excise Invoice Automatically - Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
The excise invoice is created in the background. - If you want to make use of this function, you must also define the
default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
RG23D Sales Creation and posting option - RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step.   If this is not selected then you need to separately do RG23D selection
followed by PGI and then RG23D verification and posting. If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
Default excise qty in GR - If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
Folio number for depo Posting - If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
Also we can set indicator for creation of part 1 for:
- Blocked stock
- Stock transport order
- Consignment stock
Maintain Series Group - In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents. Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
- Define excise series groups based on type of outgoing document
- Assign series group to excise registration ID
- If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
- If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' Iindicator.   Example - You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
- No account postings for CENVAT in sales cycle
- No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
If the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT - Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
Maintain Excise Duty Indicators - In this IMG activity, you maintain the excise duty indicators.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty > Select Tax Calculation Procedure
In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
- If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
- If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
Maintain Excise Defaults - In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
If you use formula-based excise determination, fill out all of the fields as follows:
- Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
- Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
- Specify the conditions in the sales order that are used for excise rates.
- Specify the countervailing duty condition type used for import purchase orders.
See also : SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features : The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
Customizing : Make the settings in Customizing Basic -> India -> for Logistics General, by choosing Taxes on Goods Movements Account -> Excise Duties Using Condition Technique and -> Settings Determination.
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data - Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities - When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for.   On the dialog box, Control Code means "chapter ID." So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose .
5. Enter data as required. - In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination - When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data®access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.
You maintain the following types of data:
- Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone. See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
- Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry. For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
- Customer master data
Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
- Material master data
Each material is assigned a chapter ID.
- Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant. Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indicator is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Lets assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under
status 7.
Define Tax Code for Purchasing Documents - In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents. Only carry out this activity if you use condition-based excise
determination.
- Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
- Assign Tax Code to Company Codes
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
Classify Condition Types - In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method. The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a
purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here. In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
- For taxes on purchases, use the condition types contained in the tax procedure.
- For taxes on sales, use the condition types contained in the pricing procedures.
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
Define G/L Accounts for Taxes - In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements - You have set up G/L accounts for each of the processing keys listed below.
- Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
- VS1 (basic excise duty)
- VS2 (additional excise duty)
- VS3 (special excise duty)
- VS5 (sales tax setoff)
- MWS (central sales tax)
- MW3 (local sales tax)
- ESA (service tax)
- ESE (service tax expense)
Specify Excise Accounts per Excise Transaction - In this IMG activity, you specify which excise accounts (for excise
duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type. If you use sub transaction types, enter the accounts for each sub transaction type as well.
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly. The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example:
- Excise TT DC ind Account name
- GRPO CR CENVAT clearing account
- GRPO CR RG 23 BED account
- GRPO DR CENVAT on hld account
Specify G/L Accounts per Excise Transaction - In this IMG activity, you assign the excise and CENVAT accounts to G/L
accounts. When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
- Excise group
- Company code
- Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
- Defined the G/L accounts
- Defined the excise groups
- Maintained the transaction accounts
Activities - For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for all transactions.
Note : you need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty. Config setting needed to be done in order to get the Excise Details Screen in Material Master.
Even though this functionality is available in enterprise version, a small configuration step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
- Material Master à Logistics General
1. Go to IMG Define Structure of Data Screen for each Configuring the Material master Screen Sequence.
2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is Foreign Trade: Import Data. Select the same and click on Sub screens in the left frame.
4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view sub screen and ensure that the sub screen is blank.
5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6. Save the setting.
7. Create a Material Master and check whether in Screen Foreign Trade
Import, Excise related sub screen appears.
A small search on SDN SD forum will help you to answer your query.
I will suggest you to visit http://sap-img.com/sap-sd.htm. It will give you the overview of SAP SD module.
Moreover there is a separate section of FAQs with answers which will help you in great deal.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

TAXINN ISsue

Similar Messages

Maybe you are looking for