Cin implementation procedure

Hi all,
I have to questions.
1. Can any one can help me how to configure the cin in SAP?.
2. what is the use of Validations and Substitutions in Sap. how we are going to use?

Forward me your email id, so that I can forward you CIN Configuration Document (with screenshots).
<b>Document is as under (without screenshots):</b>
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings >
Maintain Excise Registrations
Use
In this IMG activity, you maintain the data relating to your excise registrations.
Activities
Enter each of your excise registrations, specifying a four-character code for each
Excise Registration IDs
In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
Activities
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
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.
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 leviable 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 leviable 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
Use
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
Use
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.
Use
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
Use
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.
Activities
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.
Dependencies
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
Use
In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
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.
Activities
1. Create one excise group for each set of registers that you need to keep.
1.     Assign the excise groups to plants.
2.     Maintain whether this Excise group is for a depot or not.
3.     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.
Dependencies
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.
Dependencies
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.
Dependencies
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 Groups
Use
In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents.
Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
Activities
•     Define excise series groups based on type of outgoing document
•     Assign series group to excise registration ID
•     If  no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
•     If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.
Example
You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
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
Use
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
Use
In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
•     If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
•     If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
Maintain Excise Defaults
Use
In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
Activities
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
If you use formula-based excise determination, fill out all of the fields as follows:
•     Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
•     Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
•     Specify the conditions in the sales order that are used for excise rates.
•     Specify the countervailing duty condition type used for import purchase orders.
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
Use
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.
Activities
Customizing
Make the settings in Customizing for Logistics – General, by choosing Taxes on Goods Movements &#61614; India &#61614; Basic Settings &#61614; Excise Duties Using Condition Technique and … &#61614; Account 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
Use
When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
Prerequisites
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 access from the SAP Easy Access screen by choosing Indirect Taxes &#61614; Master Data &#61614; 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.
Activities
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 indictor 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.
Let’s 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
Use : In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
Only carry out this activity if you use condition-based excise determination.
Activities: Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
Assign Tax Code to Company Codes
Use
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
Classify Condition Types
Use
In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.
The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.
In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
•     For taxes on purchases, use the condition types contained in the tax procedure.
•     For taxes on sales, use the condition types contained in the pricing procedures.
Standard settings
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
Define G/L Accounts for Taxes
Use
In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements
You have set up G/L accounts for each of the processing keys listed below.
Activities
Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
•     VS1 (basic excise duty)
•     VS2 (additional excise duty)
•     VS3 (special excise duty)
•     VS5 (sales tax setoff)
•     MWS (central sales tax)
•     MW3 (local sales tax)
•     ESA (service tax)
•     ESE (service tax expense)
Specify Excise Accounts per Excise Transaction
Use
In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
If you use subtransaction types, enter the accounts for each subtransaction type as well.
Activities
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example
Excise TT     DC ind     Account name
GRPO     CR     CENVAT clearing account
GRPO     CR     RG 23 BED account
GRPO     DR     CENVAT on hld account
Specify G/L Accounts per Excise Transaction
Use
In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
•     Excise group
•     Company code
•     Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
•     Defined the G/L accounts
•     Defined the excise groups
•     Maintained the transaction accounts
Activities
For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
Note
You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
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 config step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
1.     Go to IMG &#61664; Logistics General &#61664; Material Master &#61664; Configuring the Material master &#61664; Define Structure of Data Screen for each  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 Subcreens 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 subscreen and ensure that the subscreen 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 subscreen appears.
Regards,
Rajesh Banka
Reward points if helpful

Similar Messages

  • Questions about CIN tax procedure choice and pricing schemas

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

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

  • CIN Implementation

    Hello folks
    Am going to my first CIN Implementation.
    I would be greatful if you people can tell me what all details i have to collect from the client from MM point of view and the sequence in which the configurations to be done.
    Also please help me with the tips and points to be remembered at the time of implementation.
    Any helpful inputs are appreciated.
    regards to all
    Sindhya

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

  • CIN pricing procedure and normal procedure linkup

    Hi gurus
    How do we link cin pricing procedure taxinn and normal pricing procedure rvaa01(for example)
    what are the confi settings....like we maintain jexp,jeap etc, in taxinn and pr00,k004,k005 in rvaa01, ver do we linkup these two pricing procedure to reflect in sales order item conditions screen....i feel this will be of gr8 help to so many SDCs.
    Good points if helpful...
    thanks in advance
    krishnamohan

    Hi gurus
    How do we link cin pricing procedure taxinn and normal pricing procedure rvaa01(for example)
    what are the confi settings....like we maintain jexp,jeap etc, in taxinn and pr00,k004,k005 in rvaa01, ver do we linkup these two pricing procedure to reflect in sales order item conditions screen....i feel this will be of gr8 help to so many SDCs.
    Good points if helpful...
    thanks in advance
    krishnamohan

  • CIN pricing procedure steps

    Dear SAP's
      Can any one send me the screen shots for Cin pricing procedure configuration on domestic sales, deemed export sales and export sales.
    my mail id is [email protected]
    thanks and points will be rewards if useful
    regards,
    Reshmi

    Hi reshmi,
    please do send me the CIN install steps and study material to   [email protected] ,it ll be grt helpful to me thanks in advance
    Regards
    Balaji

  • CIN implementation in SAP 4.6c

    Hi All
    We plan to roll-out SAP 4.6c for a customer's plant in India. CIN is also required to be implemented. Does any one know whether SAP support CIN in 4.6c version?. If so, what version is used and whether any patches need to be applied? Also can anyone give a rough estimate of how many resources in each module required for a standard CIN implementation for one plant.
    Thanks & Regards
    S Jayaram

    You can't delete all clients in one go... you need to logon into each and schedule the deletion via SCC5.
    A reorg of this scale will be very time consuming.. I think it will be much quicker to do a Homogeneous system copy via Export/Import.
    Also, if this is your development system make sure you check the client independent requests that might have been release from those clients and also the version management of developments.
    Thats my 2cents.
    Regards
    Juan

  • What is ALV grid and describe its implementation procedure

    Hi all,
               Can you tell me the step by step implementation procedure of ALV grid

    hi..
    Steps To Use ALV Grid in a Program
    1. Declare reference variables for,
           Container (class CL_GUI_CUSTOM_CONTAINER) and
           Grid (class CL_GUI_ALV_GRID)
    Example
    DATA: grid  TYPE REF TO cl_gui_alv_grid,
                custom_container  TYPE REF TO cl_gui_custom_container
    2. Create Standard Screen and a container on that screen  and give a name to that container ( Use custom control button from tool bar) . This name will be used to link the container we have created on the screen with the object reference of class CL_GUI_CUSTOM_CONTAINER, which we have declared in the first step
    3. Call the screen which has been created
    4. Instantiate the container control and the ALV Grid Control in PBO of the screen.
    Example
    IF custom_container IS INITIAL.
      CREATE OBJECT custom_container
             EXPORTING
            CONTAINER_NAME = u2018MY_CONTAINER'.
    CREATE OBJECT grid
           EXPORTING
           I_PARENT = custom_container.
    ENDIF
    5. For displaying the data, call the method set_table_for_first_display of object reference of CL_GUI_ALV_GRID.
    Example
    CALL METHOD grid->set_table_for_first_display
    EXPORTING
    I_BUFFER_ACTIVE               =
    I_BYPASSING_BUFFER            =
    I_CONSISTENCY_CHECK           =
    I_STRUCTURE_NAME              =
    IS_VARIANT                    =
    I_SAVE                        =
    I_DEFAULT                     =
    IS_LAYOUT                     =
    IS_PRINT                      =
    IT_SPECIAL_GROUPS             =
    IT_TOOLBAR_EXCLUDING          =
    IT_HYPERLINK                  =
    IT_ALV_GRAPHICS               =
    IT_EXCEPT_QINFO               =
    CHANGING
    IT_OUTTAB                     =
    IT_FIELDCATALOG               =
    IT_SORT                       =
    IT_FILTER                     =
    EXCEPTION
    INVALID_PARAMETER_COMBINATION =
    PROGRAM_ERROR                 =
    TOO_MANY_LINES                =
    others                        =
    EXPLANATION OF SOME IMPORTANT PARAMETERS.
    I_BYPASSING_BUFFER & I_BUFFER_ACTIVE :
    When the program is run for the first time, the fields present in the output table and their positions are stored in a buffer.  So the buffer is taken as reference for the successive executions.  In order to bypass this buffer the above parameter values should be u2018Xu2019 and  u2018 u2018(space)  respectively. If these values are not passed  to the function module, the changes made in the structure of the internal table will not be reflected in the output.
    I_STRUCTURE_NAME:
    If the structure of your output table corresponds to a structure stored in the Data Dictionary (DDIC), the ALV Grid Control can use this information to generate the field catalog automatically. Pass the table structure as parameter. In this case, all fields of this DDIC structure are displayed in the list.
    IS_VARIANT :
    It allows the user to save and reuse the layout. It is a structure of type DISVARIANT and contain the display variant name. It  facilitates pre-assignment for a layout, rather than displaying report and then choosing displaying variant.
    I_SAVE:
    This single character variable specifies whether the user specific display variants can be saved or not.
    The I_SAVE "Options for saving layouts" parameter can have the following values:
    U Only user specific layouts can be saved
    X Only global layouts can be saved
    A Both user specific and global layouts can be saved
    Space Layouts can not be saved
    IS_LAYOUT:
    This structure of type LVC_S_LAYO
    is used to control the layout of the ALV.  Two important fields are:
    GRID TITLE. : Title of grid
    ZEBRA : Alternate lines in list are displayed in different colors.
    IT_FIELDCATALOG:
    This internal table of type LVC_T_FCAT
    is used to specify the position of various fields in the report itab.
    There are three ways we can fill the field catalog table
    1. Automatically through data dictionary structure (DDIC). In this case we pass the table structure to I_STRUCTURE_NAME.
    2. Manually in ABAP program. Filling the internal table of type LVC_T_FCAT
    1.                  . With each row corresponding to each column of output table. Each row of this table will hold value like
    i). TABNAME & FIELDNAME specifies the reference fields for F1 help
    ii). CTABNAME & CFIELDNAME specifies the reference fields for currency formatting
    iii). QTABNAME & QFIELDNAME specifies the reference fields for quantity formatting
    iv). SELTEXT_L holds the long description of the field
    v).  SELTEXT_M holds the medium description of the field
    vi). SELTEXT_S holds the small description of the field
    vii). KEY specifies the Key field ( cannot be hidden )
    viii). OUTPUTLEN species the output length of the field
    ix). DO_SUM specifies that subtotal is required on this field
    x). NO_OUT specifies a hidden field
    3.  Semi-Automatically by combining the above 2 procedures.
    Call function Module REUSE_ALV_FIELDCATALOG_MERGE and pass DDIC
    structure or the output table to generate the field catalog.
    Add additional Rows or modify existing properties of the fields to be displayed.
    hope this will help you.
    regards
    lokesh

  • Purpose of CIN and procedure to map into SAP

    Hai Gurus,
                  Can any one explain teh purpose of CIN and procedure to map to SAP
    Thanks in Advance
    sameer

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

  • CIN Tax Procedures

    HI CIN GURU'S,
    Can anyone please explain me why different tax procedures are used,
    These below procedures are used for factory sales...
    J1INFAC (condition-based excise determination) and JFACT (formula-based excise determination).
    Then why TAXINN & TAXINJ....
    getting confused, please help ASAP.
    Please explain me how, where, why these procedures to be used and how does it would impact !!!
    Thank you,
    DAVID

    Difference between TAXINJ and TAXINN
    TAXINJ:
    1. It is Formula Based Tax procedure.
    2. It was most commonly used upto intial phase of R/3 4.7, but the latter implementations were with TAXINN.
    3. Tax Code plays a vital role, as the Tax Rate are maintained in Tax Code.
    4. It is complex compared to TAXINN
    TAXINN:
    1. It is Condition Based Tax procedure.
    2. Tax Code is required to be maintained in Condition Record, & if Tax Code is not found in Condition Record, Sales Cycle will go upto billing, but not release to accounting. Hence even a single Tax code may suffice the requirement for different Tax rate.
    Regards,
    Rajesh Banka
    Reward points if helpful.

  • CIN tax procedure TAXINN

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

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

  • SAP MM CIN Pricing procedure

    Hi,
    I am a SAP MM learner.
    I have done the pricing procedure for CIN (ZAXINN) in IMG - FI part.  I have assigned the calculation procedure to the country IN also. 
    But while creating the PO, the calculation procedure taken is RM00001 from MM.  Because of this i am not able to complete the cycle.  Pls help me to make the proper setting to get the ZAXINN procedure.
    Thanks,
    N Murali

    Hi
    1.  I have created a pricing procedure ZAXINN in FI Module for CIN (capturing Cenvat amounts like BED, AED, SED, E Cess, etc).
    2.  I have checked the assignment of the pricing procedure in the below mentioned 4 headings and found to be correct.
    -a. IMG > FI > FI GLOBAL SETTINGS > TAX ON SALES / PURCHASE > BASIC SETTING > ASSIGN COUNTRY TO CALCULATION PROCEDURE
    b. IMG > LOGISTICS GENERAL > TAX ON GOODS MOVEMENT > INDIA > BASIC SETTING > DETERMINATION OF EXCISE DUTY > SELECT TAX CALCULATION PROCEDURE
    c. T Code - OBBG
    d. T Code - OY01
    3.  I have completed all the IMG settings for the CIN.
    4.  But while creating the PO, system automatically picks the pricing procedure of RM0000 from MM Part.
    5.  I tried doing the MIGO and found all the Excise amounts are getting captured properly and getting posted to the necessary GL accounts.
    6.  But I am not able to do the MIRO because the condition type is not picked up during the purchase order creation.  I need a help to find out what setting to be done in SAP to pick up the pricing procedure while creating PO which is assigned to the country IN for completing my project.
    Thanks,
    N Murali

  • CIN Pricing Procedure

    Hi
    Iam new to cin kindly explain me what are the condition types used for JINFAC,JINSTO and JINDEPO AND In which manner(order)kindly send any screen shots regarding those pricing procedures,that will be great help for me. and My mail id is [email protected] or [email protected]
    Thanks and Regards
    Ashwath Reddy

    hi,
    pl check this
    [cin|http://www.sap-img.com/sap-sd/sap-sd-cin-configuration.htm]
    regards
    sadhu kishore

  • CIN Pricing Procedure for Intercompany Billing Process

    Hello All,
    Please suggest me what Pricing procedure I can use for Intercompany Billing for CIN.
    I have created a ZPricing Procedure coping the JINFAC but its for normal sales what CIN configuration I have to do for Intercompany billing.
    Please suggest..
    Regards
    Venkat

    Not Answered

  • Cin pricing procedures

    what r the major differences between TAXINJ and TAXINN. which would be very useful in present scenario. and advisable,
    will reward

    Refer link below hope it helps
    TAXINJ/TAXINN are the two different pricing procedure used in CIN.
    TAXINN only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination.
    Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
    Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
    When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
    TAXINN AND TAXINJ difference ? AND Which is better ?
    TAXINJ & TAXINN are Tax Procedures in India. TAXINJ is old version & TAX INN is new version. Both has its own advantage & disadvantage.
    Upto 4.6C & partially 4.7 version of SAP, TAXINJ was used. TAXINJ is formula based calculation, in which we maintain the tax rate in Tax Code itself. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST & permutation & combination of these, we require that many Tax Codes. For example:
    Tax Code: A1
    Taxes: 16% Excise Duty + 2% Education Cess + 12% VAT
    Tax Code: A2
    Taxes: 16% Excise Duty + 2% Education Cess + 8% VAT
    Tax Code: A3
    Taxes: 12% Excise Duty + 2% Education Cess + 12% VAT
    Tax Code: A3
    Taxes: 12% Excise Duty + 2% Education Cess + 8% VAT
    From 4.7 version onwards of SAP, TAXINN is being recommended & used. TAXINN is more user friendly & condition record based. In TAXINN, Tax Codes are statistical & of not much relevance, but are required to be maintained in condition record for taxes condition type. This makes Tax Codes simpler. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST, we need not have the tax codes to that combination. For example:
    Tax Code: A1
    Can be used for any rate of excise duty, as tax code is only required to be maintained statistically in condition record.
    Tax Code: A2
    Can be used for any rate of VAT, as tax code is only required to be maintained statistically in condition record

  • SNOTE Implementation Procedure

    Hi,
    Can anybody please give me the Step By Step procedure of implementing SNOTE.
    Points will be rewarded definitely for all the contributors.
    My mail id is <b>[email protected]</b>
    Thanks

    Notes are nothing but Corrections / Changes happend in Standard SAP .
    check tcode : SNOTE
    SNOTE is the transaction that implements SAP recommended OSS Note in your system for you. In other words if you want to implement a OSS you have to get access key to change the SAP Standard program and then implement the code corrections manually at the appropriate place. SNOTE wipes out the process for you and implements the note directly and changes all the objects that are affected. It even asks for a Transport number and all you have to do to implement the note is to move the transport.
    Check these links. It gives details about OSS Implementation using SNOTE transaction.
    http://help.sap.com/saphelp_nw70/helpdata/en/b8/3cf839fd35384de10000000a11402f/frameset.htm
    http://www.sapdevelopment.co.uk/tips/tips_snote.htm

Maybe you are looking for