Country Version India
A Country Version is designed specifically to cater the business operations of that country over and above the generic SAP system functionalities. It comprises of functionalities degined for the laws and business practices pertaining to the country.
Most of the country-specific functions for India relate to Financials and Logistics.
The main areas are as follows:
- Excise duty and the central value-added tax system (CENVAT)
- Withholding tax (also known as tax deducted at source)
- Sales tax
- Maintenance and printing of statutory excise registers
CIN determines taxes based on the chapter-id of the material. There are 2 levels for rate determination. First the system will check if there is an exceptional rate available. If this is available then that rate is picked up. This rate could be for a material or material and customer combination. If there are no exceptions then the system looks for chapter-id of that material. The customer will have an excise tax status, which along with the plant status will give a final excise status. Based on the excise status and the chapter-id the rates are maintained.
You can change the excise rates with any given validity period. After making the changes you will have to update the sales orders if the new tax rates have to be considered for future deliveries.
You can maintain exceptional rates for either incoming or outgoing based on the volume of exceptions data.
Along with exceptional rate maintenance you can maintain the chapter-id, which should be used for the outgoing transactions. This chapter-id will be used only for copying on to the document and will not be used for rate determination.
You can maintain multiple excise indicators and based on that you can have additional rates.
While picking up the rate for a given transaction system will check for that validity period where the valid from is the maximum but with in the pricing date and based on that pick up the rate applicable.
CIN uses R3 condition technique for pricing along with the pricing formulae. Details are available in the CIN knowledge bank. Template pricing procedures are provided for various sales scenarios.
The number of tax codes will directly depend on how you want to account the sales tax. You can have CST and LST being determined by the same tax code if both can be accrued into the same account. Instead if you need separate account determination then you need separate tax codes. Also based on the tax concessions available you need to decide the various tax rates, which need to be mapped.
CIN comes with default customization to open up the tax classification fields. The procedure is as follows. You need to define as many condition types as the number of tax classification fields. The following procedure could be used
SPRO – Sales and distribution -Basic functions-Taxes – Tax determination rules For Country ‘IN’ make entries as follows (This is precustomized in client 000)
– Seq 1 – UTXJ
– Seq 2 – JTX1
– Seq 3 – JTX2
– Seq 4 – JTX3
In SPRO – Sales and Distribution – Basic functions – Taxes
Determine tax relevancy of master records
This is explained in SAP note 335577. Having opened up the new tax classification fields you might have to do the following
- Customer taxes maintain the possible values for JTX3 . Each unique value should denote one concession rate. For eg 1 – normal excise duty
- Maintain the JTX3 value against the form code in J1IT -Define Form types
- Maintain the customer tax classification in customer master if the customer has got excise exemption
- Maintain the excise indicator in J1ID for the customer and form code and this indicator gives the final indicator
- Forms database is used for determination of whether the form has arrived or not at the time of billing.
- The tax classification value gets defaulted from the customer master in the sales order. This can be changed in the header billing data if required
SPRO – Sales and distribution -Basic functions-Taxes – Tax determination rules For Country ‘IN’ make entries as follows (This is precustomized in client 000 )
– Seq 1 – UTXJ
– Seq 2 – JTX1
– Seq 3 – JTX2
– Seq 4 – JTX3
Taxes – Determine tax relevancy of master records – Customer taxes maintain the possible values for JTX1 and JTX2. Each unique value should denote one concession rate. For eg 1 – 4% . Multiple forms could correspond to a single rate. JTX1 could be used for CST and JTX2 for LST. (UTXJ could be freely used by the customers as earlier )
Maintain the tax classification in customer master as well as material master ( Sales org data 2)
Build access sequences based on these new fields to point to the correct sales tax code You might have to have a new access based on region of delivering plant and region of ship to party
SAP can handle normal VAT regulations. CIN will take a review of the VAT rule when it is implemented in India and suggest the best business process to comply with the same.
This is happening because the Excise conditions for sales are statistical in the tax procedure for India. So while creating a new tax code you need to open the tax procedure remove the statistical flag, maintain 100% for all excise conditions. After saving the tax code you need to make the conditions statistical once again.
This is happening because one or more lines in the tax procedure has a condition with a value but is not marked statistical. You need to check whether the conditions JMOD, JAED, JSED and JCES are marked statistical in the tax procedure. You cannot rectify the documents, which are in error. The correction takes into effect only the future orders.
This is happening because the tax base for some tax condition is falling less than the tax base amount. R3 does not allow the tax base to fall below the tax amount. You need to check which condition is giving the problem and based on that you can verify the tax procedure from-to settings.
If the same chapter-id is applicable for the material in all the plants then you need not maintain the chapter-ids for all the plants. You can leave the plant blank.
Check whether you have maintained the opening balance for the item in the corresponding register (Table J_2IACCBAL for register account balances). Next check whether you have maintained the sapscript forms which are used for printing the registers in the CIN configuration. Finally check whether the extraction has been done for the period.
This is because you have not maintained the condition record for output determination. You need to maintain the condition record for output determination at the sold to party level. Also for the documents created already you can go into Billing header – output and manually enter the output type j1io and save. Later the excise invoices can be printed.
This is happening because you are trying to create an issue entry and the stock in the register is not enough to do the issue. So you need to first update RG1 with the receipts and then go into the issues.
You can re-extract the data if you have added more transaction data for the given period.
To prevent data inconsistency in the third party application CIN does not allow you to re download the register data once it has already been downloaded.
You need to classify the RG1 entries as to whether they are receipts from manufacture or other receipts, clearances of various types so that they can be reported under the various headings as required by the Excise commissionerate.
You need load them manually at the initial data upload.
CIN calculates the opening balance for reporting purposes based on the transaction s extracted in any period.
You must not pick up the opening and closing balances that are calculated by reporting because they might get changed if someone does are extracting. So they need to be recomputed dynamically. They are not stored.
Duty can be rounded off in CIN only at the item level. Due to technical reasons duty round off is not provided at the header level.
System picks up the exchange rate which is maintained in the CIN configuration data for the company code.
With fortnightly utilization you do not create an entry in the CENVAT or PLA registers. Instead CIN keeps a separate Despatch register and generates continuous serial numbers in this register that can be used for future reconciliation.
At the time of excise invoice creation the debit is being made into an Excise payable account. So you need not have balances in the CENVAT account. You need to have enough money at the time of fortnightly utilization or you should have made a debit through TR6 into PLA.
You can list all the billing documents for which excise invoice is not created. You can get a list of all excise invoices for which billing document has been cancelled., You can also have a report of all cancelled excise invoice for which the billing document is still open.
Excise due list gives you all billing documents for which there is no excise invoice.
Number range skipping happens for excise invoice. What could be the reason?
CIN number ranges are defined as not buffered. You need to check if this has been changed. If skipping happens never reset the number range.. you must report the problem to SAP support immediately so that they can help you resolve this.
While creating the excise invoice, at the time of saving system tries to lock the GL account that is getting updated with the new balances. S probably someone else could be changing the GL account data at that point of time. This is a very short phenomena and is meant to keep the data consistency.
You need to check the customization settings for LIFOor FIFO and the invoices of which period you have set. Also you need to check the excise group, which is being used. System will show you only those excise invoices, which belong to the same excise group, plant, storage location and batch.
A- certificates come when the goods are removed after paying a provisional duty. When the final price is decided at the time of the order you need to pay the balance of the duty. There is no facility at the moment to calculate the differential duty. You have to make the payment manually using J1IS at the factory. Once this is done you can go back to the depot and capture this extra payment into your RG23D. This is recorded as a new serial no within the original folio so that the RG23D register value tally. At the time of selection of excise invoice for sale you have the option to pick up the a-certificates for the excise invoice and then the additional duty gets added into the invoice amount. Also this is reflected in the RG23D register.
No you need an A certificate if you have to get an additional duty in RG23D invoice. Alternative is to write customer specific routines which are not supported by CIN.
If there are returns to depot, that can be captured as any other receipt. You can enter the material document no of the return receipt and the data gets copid and you can copy into RG23D.
There are no D3 procedures at the moment which is mandated by the excise department. Legally you can take credit for all the receipts and then pay the duty when it goes out after repair or to another customer. You can Excise invoice without PO route to take the credit.
This does not happen anymore. There was a need felt that we should check the balance s even though we can pay the duty 15 days hence.
You need to check the object type for the object id J1IN. this can be done by checking the data of the view J_1IVTTXOB. The editor mode has to be set as ‘Application text with SAVE key ‘.
You can use the CIN IMG text maintenance option and add more ids with descriptors. For excise invoice creation the object is J1II. For depot receipts the object is J1IG and for depot sales it is J1IJ.
Excise invoice does not allow entry of business area. The business area in the billing document is automatically taken for the excise invoice.
Excise invoice picks up the profit center from the billing document if it is available there. If it is not available there then it looks at the plant specific material master data and picks up if available.
Tax jurisdiction codes are one method by which you can maintain tax rates with out having multitude of tax codes. You can maintain the LST effectively with one tax code and multiple jurisdiction.
You have to use tax jurisdiction code with the standard CIN. If you do not want to make use of that for rate determination you should at least have one jurisdiction at the federal level.
The system will first check in the Form type maintenance whether the form is marked as required. This means that the form has to come by the time billing happens. Once you receive the form you need to enter it into the forms data base (J1IU) for the delivery document number. If the form receipt is not maintained then the billing will do a repricing and charge full tax for the particular excise duty.
There is no transaction type for determining the accounts of the fortnightly utilization. The credit account of the transaction type ‘DLFC ‘ is used as the debit account here. For the credit side we pick the debit accounts from the GRPO, EWPO and TR6C transactions. So it is mandatory that whether you use EWPO or not you should have maintained the account determination for all transaction tyes for a given excise group
Transaction type UTLZ is used for determining the accounts when a JV is posted with an option of fortnightly payment.
Transaction types are used internally by CIN for various purposes. So you cannot define your WN transaction types. Alternate account assignments can be done using sub transaction types.
Initially when you upload the balance in RG1 you need to mention the material form. Later the system assumes the same for for the same material code. If you need to dynamically change this then you can make use of the user-exit. A material can be marked either as packed or loose but not both.
Batch utilization is just an interface that helps you to complete the utilization of a set of documents in one step. This simply triggers individual utilization as a BDC so that the user interaction can be minimized.