CIN Customization Documentation: Caution: Do Not Run The Country Version Installation Program in A Live System

http://thefico.weebly.
com/
CIN Customization Documentation
India Localization Menu

Preparatory Activities
Execute Country Installation Program
Change Country-Specific Settings

You use the Country version function to activate the standard country versions delivered by SAP. For detailed
information see the report documentation Country Version Installation Program RSCICO02.
Install the country version in a copy of client 000 in your test system; then test your Customizing settings; finally
transport these settings to your live system. To do this, you must set up the client in which you are installing the
version in such a way that Customizing changes are recorded automatically.
Caution:
Do not run the country version installation program in a live system.
Prerequisites
Organizational units must be available in the SAP standard system. You cannot make changes to the standard
system. Note that only organizational units from the standard system can be converted when you install the country
version, not organizational units that you have created yourself.
Activities
For more information on standard settings and activities, see the report documentation on the Country Version
Installation Program (RSCICO02).
Additional Notes
To execute the program, you must have authorization for authorization object S_TABU_CLI . You can run this
program in any client that is a copy of client 000.
Return ->
Change Country-Specific Settings
Customizing: Country Version

Description
You use this program to activate the country versions supplied with the standard R/3 System.
The standard Customizing settings required for the country versions are supplied in client 000.
Note
Ensure that company code 0001 contains all of the standard Customizing settings according to the chart of accounts
INT. The Customizing settings for the various standard countries (which cover legal and business requirements) are
contained in the company code templates XX01 (where XX is the country key). However, these templates only
contain some of the standard Customizing settings for company code 0001, which means that you cannot use them
as your production company code. You must only use them in conjunction with this program.
When you execute the program, the R/3 System makes the standard Customizing settings for the country in question
in company code 0001, for example:
the chart of accounts
account determination
tax calculation schemata
financial statements
payment methods
charts of depreciation
cost elements.
The program integrates the legal and business requirements contained in the templates by overwriting the countryspecific parameters in company code 0001, combining the company code with the appropriate controlling area.
For standard countries that use chart of accounts INT, that means a combination of the company code 0001 and
controlling area 0001. For countries with their own chart of accounts, the result is a combination of company code
0001 and controlling area XX01 (again, where XX is the country key).
Page 1 of 64
http://thefico.weebly.com/
You execute this program in your test system, in a copy of client 000. You then test the Customizing settings and
transport them to your production system.
Caution
You must not execute the program in your production system, because it will change the current Customizing settings
to those of the country in question. The program changes the settings of company code 0001 exclusively.
Requirement
In order to execute the program, you will need authorization for the authorization object S_TABU_CLI.
Procedure
1. Make sure that company code 0001 in the test client still contains the standard Customizing settings (delivered
in client 000).
You must not have changed any settings. If you need to restore the original standard Customizing settings, you
can transport them from client 000.
2. In company code 0001 of your test client, start the country installation program and install the standard country
version that you want.
3. Choose Change country-specific settings in Enterprise structure customizing.
4. Choose Country version.
5. Enter the country that you want to install and start the program.
If the system prompts you to enter the chart of accounts, do so.
Note
If you execute the program in test mode, the R/3 System does not make any changes to the database, but
issues a log of all the changes that the System would normally have made. It does not make any changes unless
you execute it in update mode.
6. Using the entity copier, copy the new Customizing settings into a new company code of your choice.
Caution
Do not use company code 0001 for production operation.
7. Check that the copied organizational units and their dependent objects are complete.
Make any manual adjustments required.
Copying the organizational units into a different company code means that company code 0001 remains
available for other country installations.
Creating Multiple Country-Specific Company Codes

Repeat the above procedure for every other country. You do not need to restore the settings in company code 0001
unless you have made any changes to the standard Customizing settings (other than installing the country versions).
Return ->
Customizing: Country Version
Activate Country Version India for Accounting Interface
Activate Country Version India for Accounting Interface

In this activity, you activate Country Version India (CIN) for the accounting interface.
Activities
In the table, enter component ZIND.
Return ->
Application
Activate Country Version India for Specific Fiscal Years

In this activity, you specify for which fiscal years you want to activate Country Version India (CIN) for the accounting
interface.
Activities
In the table, maintain data as follows:
Comp. (Component): ZIND
To year: 2999
Active: X
Return ->
Application
Page 2 of 64
Activate Processes
In this activity, you maintain the different transactions and assign them to different function modules.
Activities
In the table, make the following settings:
Transaction
Time
No. Comp.
Function module
DOCUMENT
CLOSE
910 ZIND
J_1I6_COPY_TO_LOCAL
DOCUMENT
POST
910 ZIND
J_1I6_CHECK_GR_AGAINST_EXC_INV
BELEG
CLOSE
920 ZIND
J_1I2_COPY_TO_LOCAL
BELEG
POST
920 ZIND
J_1ITDS_TABLE_UPDATE
DOCUMENT
CLOSE
*
ZIND
J_1I6_UPDATE_BA
BELEG
CLOSE
921 ZIND
J_1IEWT_COPY_TO_LOCAL
BELEG
POST
911 ZIND
J_1IEWT_UPDATE_PROVISION
DOCUMENT
POST
911 ZIND
J_1IEWT_UPDATE_PROVISION
DOCUMENT
CLOSE
921 ZIND
J_1IEWT_COPY_TO_LOCAL
DOCUMENT
CLOSE
920 ZIND
J_1I2_COPY_TO_LOCAL
DOCUMENT
POST
922 ZIND
J_1ITDS_TABLE_UPDATE
RABELEG
ERGAENZE910
ZIND
J_1IEWT_COPY_BUPLA_FBZ
*This sequence number must be lower than the sequence number used for function module
FI_DOCUMENT_CLOSE.
Leave the Doc (Function component operates in document) column blank.
Return ->
Application
Activate Business Transaction Events

In this activity, you activate the function modules from the Country Version India (CIN) solution. Follow the instructions
listed below, but if you need more information about what this function does, see the standard documentation.
Activities
1. Choose Settings -> Identification -> Partners.
2. Make sure that there is an entry for partner INDIA and that it is active.
3. Go back to the SAP Business Framework: Business Transaction Events screen.
4. Choose Settings -> Products -> ... of a partner -> Edit.
5. Make sure that there is an entry for product TS in conjunction with partner INDIA.
6. Make sure that there is an entry for product EWT in conjunction with partner INDIA
7. Choose Settings -> Products -> ... of a partner -> Activate.
8. Make sure that there is are entries for products TS & EWT with partner INDIA
9. Go back to the SAP Business Framework: Business Transaction Events screen.
10. Choose Settings -> P/S function modules -> ... of a partner.
11. Make sure that there are entries for the following:
Event 00001110, which must be assigned to function module J_1ITDS_SAVE_CHANGES with

product TS .
Event 00001030, which must be assigned to function module J_1IEWT_CHALLAN_UPDATE with

product EWT .
Event 00001050, which must be assigned to function module J_1ITDS_TABLE_UPDATE_LIV with

product TS .
12. Choose Settings -> Process function modules -> ... of a partner.
13. Make sure that there is an entry for event 00001120, function module J_1IEWT_DUEDATE with partner
INDIA and product EWT .
Return ->
Application
Global Settings
In the following activities, you make the global settings for working with Country Version India.
Page 3 of 64
Return ->
Application
Company Settings
Maintain company-specific default values for processing excise documents. Default excise invoice selection
parameters, excise duty percentage for subcontract operations can be maintained here.
Example
Subcontract Period - 60 Days.
Excise Duty for Subcontract Operations - 10 %.
CENVAT Document Type - SA.
Recommendation
Maintain the values here and avoid filling the selection parameters repeatedly during document creation.
You maintain all customization for Financial postings at this level.
You can maintain the document types which has to be ued for creating FI documents for
1. CENVAT credit
2. CENVAT debit or utilization
3. TDS postings
You can maintain separate rounding indicator for

1. Procurement
2. Sales
This decides whether the excise duty in the incoming and outgoing excise invoice has to be rounded to the nearest
rupee at item level.
You can maintain separate Exchange rate types for

1. CVD invoices incoming
2. Export invoice outoging
Further Notes
CENVAT document type indicates the posted FI document types.
Excise Registration IDs

Return ->
Application
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

Return ->
Application
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.
Return ->
Application
Page 4 of 64
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.
2. Assign the excise groups to plants.
3. Maintain whether this Excise group is for a depot or not
4. 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'.
5. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator
'Create EI'
6. 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.
7. 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.
8. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of
excise invoice into depot.
9. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation
in single step.
10. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked
stock.
11. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant
transfers.
12. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into
consumption stock.
Return ->
Application
Maintain Series Groups

In this 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.
Example
You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
Recommendation
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 series 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.
Return ->
Application
Excise Defaults
In this activity, you define which tax procedure and pricing condition types are used in calculating excise taxes.
Page 5 of 64
Activities
1. Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
2. Specify the purchasing and sales conditions types used for basic excise duty (BED), additional excise duty
(AED), special excise duty (SED), and cess.
3. Specify the conditions in the sales order that are used for excise rates.
4. Specify the countervailing duty (CVD) condition type used for import purchase orders.
Return ->
Application
Tax indicator maintenance
No Document
Accounting
In the following activities, you set up the G/L accounts that are to be used for excise duty.
Return ->
Application
Make Sure That Processing Keys Are Deductible

In this activity, you check a number of processing keys to make sure that the taxes are deductible.
Activities
For each of the following keys, deselect Not deductible, if necessary:
VS1 (basic excise duty)
VS2 (additional excise duty)
VS3 (special excise duty)
VS5 (sales tax setoff)

Return ->
Application
Define G/L Accounts for Taxes

In this 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)

Return ->
Application
Maintain Transaction Accounts

In this activity, you specify which G/L 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, define the credit and debit acounts for each subtransaction type as well.
Page 6 of 64
Example
Excise TT
DC ind
Account name
GRPO
CR
CENVAT clearing account
GRPO
CR
RG 23 BED account
GRPO
DR
CENVAT on hold account
Recommendation
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 fort nightly.
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.
Return ->
Application
Maintain Transaction Accounts

In this activity, you specify which G/L 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, define the credit and debit acounts for each subtransaction type as well.
Example
Excise TT
DC ind
Account name
GRPO
CR
CENVAT clearing account
GRPO
CR
RG 23 BED account
GRPO
DR
CENVAT on hold account
Recommendation
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 fort nightly.
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.
Return ->
Application
Maintain Minimum Balances for Excise Accounts

In this activity, you can maintain minimum balances in your excise accounts. When the balance in these accounts
during utilization falls below this level, the system automatically utilizes funds in the PLA account.
Activities
Maintain the minimum balance amount for the excise accounts. If you have more than one excise group, you can
maintain different minimum balances.
Return ->
Application
Logistics
In the following activities, you make the logistics settings for use in Country Version India.
Return ->
Application
Incoming Excise Invoices
No Document
Enjoy Version Settings
No Document
Page 7 of 64
Select Fields
In this IMG activity, you specify which fields you want in the Incoming Excise Invoices transaction.
The settings that you make here apply for all versions of the transaction that you might create.
Activities
For each field, specify whether you want it to be an input field, a display field, and so on. You can also highlight fields
of particular importance.
Only the main table is of interest. You do not need to use the other functions, such as Influencing or Screen Groups.
Return ->
Application
Define Processing Modes Per Transaction

In this IMG activity, you specify which processing modes the user can use in the various Incoming Excise Invoice
transactions.
This way, you can tailor the transaction to what your users have to do.
Example
You might want to create a transaction that only allows users to display excise invoices.
Standard Settings
The system comes with three standard transactions relating to the Incoming Excise Invoices function (those that are
included in the role SAP_CIN). The processing modes available in these transactions are as follows:
J1IEX_C
This transaction is for excise clerks: users of this transaction can only capture and display excise invoices.
J1IEX_P
This transaction is for excise supervisors: they can change, display, cancel, and post excise invoices.
J1IEX
In this transaction, users can capture and post excise invoices, as well as displaying, changing, and canceling
them.
Activities
If the standard settings meet your requirements, do not do anything.
Otherwise, you can adjust the standard settings or you can create your own transactions.
To do so:
1. In Maintain Transaction, create a new transaction by making a copy of one of the standard transactions. Give
the new transaction a transaction code of your choice.
2. In this activity, enter data as follows:
Tcode: The transaction code that you have just created.
Proc. mode: Specify what the users of the transaction will do with the excise invoices.
Active: Select this indicator to activate the setting.

Return ->
Application
Define Reference Documents Per Transaction

In this IMG activity, you specify for each combination of transaction and processing mode which reference documents
you want the users to be able to use.
Activities
If the standard settings meet your requirements, you do not have to do anything.
Otherwise, add the entries that you need to the table: For each transaction, make one entry per combination of
processing mode and reference document. Activate each entry for it to work.
Return ->
Application
Define Rejection Codes

In this IMG activity, you define the rejection codes that are used in the Incoming Excise Invoices transaction.
Page 8 of 64
Activities
For each rejection code, enter a code and a description. You can also specify whether the excise duty in the invoice is
to be posted to the CENVAT on hold account, instead of the CENVAT clearing account.
Return ->
Application
Specify Which Movement Types Involve Excise Invoices

In this activity, you specify which movement types relating to goods receipts involve excise invoices.
The system uses this information during the goods receipt procedure. When you post a goods receipt using one of
the movement types that you have specified here, the system prompts you to enter the excise invoice number.
Note
This option cannot be used for processing goods receipts without purchase orders.
Return ->
Application
Subcontracting
The IMG settings that mandatory have to be set for subcontracting are:
(1)
Materials Management -> Inventory Management and Physical Inventory -> Goods Issue /
Transfer Postings -> Define Screen Layout.
For the movement type 541, maintain the field Purchase Order as an optional entry or as a required
entry.
(2)
Materials Management -> Inventory Management and Physical Inventory -> Output
Determination -> Maintain Output Types.
Maintain the Output Type. In the Default Values tabstrip maintain the Dispatch Time and the
Transmission Medium. Maintain the Print Parameter in the Print tabstrip.
(This Output Type has to be maintained in the Subcontracting Attributes in CIN IMG.)
Determination -> Assign Forms and Programs.
Maintain the Program, FORM Routine and the Form for the Output Type.
Determination -> Printer Determination -> Printer Determination by Plant / Storage Location
Output device can be maintained here.
The Print Immediately option can also be maintained here.
Return ->
Application
Subcontracting Attributes
The subcontracting attributes help determine conditions for a combination of an excise group, a transaction type and
a subtransaction type.
The conditions such as the number of excise items per subcontracting challan, if the non excisable materials have to
be filtered or not when the subcontracting challan is created, the movement type groups for Issues and Receipts and
the hierarchy of determining the excise base value are mentioned here.
Return ->
Application
Movement type Groups for Subcontracting
No Document
Page 9 of 64
Sales and Distribution

In the following activities, you make the Sales and Distribution (SD) settings for use in Country Version India.
Return ->
Application
Sales and Distribution Customization

Standard Settings
Pricing
Factory Sales Pricing Procedure - JFACT
This is a template of pricing procedure for Sales from Factory. JMAN is a manual condition for Excise. When manual
override is required for the calculated excise value it could be given for the condition JMAN. The condition value
formula 355 checks and copies this on to the Basic Excise duty value. UTXJ is the condition in JFACT, which triggers
the calculated call of tax procedure TAXINJ. Condition records need to be maintained for UTXJ with the appropriate
tax code. Access sequence JIND has been assigned to the condition UTXJ. Base value for calculation of excise
derived from the condition base value formula 351. This ensures that if an assessable value is maintained for the
material through Excise rate maintenance (J1ID) then that will be used as basis for excise calculation. In the absence
of an assessable value the selling price will be used for excise calculation.
JMOD is a FI Tax condition which gets the Basic Excise duty from calculation formula 352. JEX2 is a copy of JMOD
and is a Sales pricing condition. The value of JEX2 gets posted for Excise account key. This ensures that the cost
accounting of excise value paid is done correctly. In cases where commercial invoice is created after utilization the
condition value formula 353 ensures that the actual MODVAT utilized is accounted as excise. Similarly JAED is a FI
Tax condition which gets the Additional Excise duty from calculation formula 352. JEXA is a copy of JAED and is a
Sales pricing condition. The accounting is done for the value of JEXA. JSED is a FI Tax condition which gets the
Special Excise duty from calculation formula 352. JEXS is a copy of JSED and is a Sales pricing condition. The
accounting is done for the value of JEXS. JCES is a FI Tax condition which gets the CESS from calculation formula
352. JCED is a copy of JCES and is a Sales pricing condition. The accounting is done for the value of JCED.
Sales Tax - Identification of Central or Local Sales tax.
Both CST and LST rates are maintained in one tax code in the same jurisdiction. (Refer Tax code V8 ). The rates are
maintained at the tax code level. But then requirement formulae are attached to the LST and CST tax conditions in
the tax procedure. The requirement formula 351 decides whether CST is applicable based on the Region of the shipto party and the region of the delivering plant being different. The requirement formula 352 decides whether LST is
applicable based on Region of the ship-to party and the region of the delivering plant being same.
You can enhance the requirement formula to add your own logic for deciding whether the tax applicable is CST or
LST. All the fields specified in the pricing field catalog are available in the formula.
Important: If you are not using requirement formula to decide on the sales tax remove it from the Tax procedure as
well as pricing procedure. Sales tax rates needs to be maintained separately for each jurisdiction
Important: Manual override of applicability of LST or CST is not possible if elimination is done using requirement
formulae.
LST and CST rates are maintained in different tax codes at different jurisdiction. ( Refer tax code V5 and V6 ) Default
Export Sales Pricing Procedure - JEXPOR
There is no Excise condition in the Exports pricing. But excise can be calculated at MODVAT utilization.
Stock Transfer Pricing Procedure - JSTKTR
Stock transfer pricing has only excise conditions as it is used only for the calculation of excise value.
Depot Pricing Procedure - JDEPOT
Depot pricing procedure is exactly similar to the Factory pricing procedure with the exception that the condition value
formula attached to the excise condition is 356. This ensures that the excise value from the referred excise invoices
for the delivery is picked up and used by the commercial invoice.
Output Determination:
In Standard Customizing for output determination following settings have to be maintained.
Output determination procedure has to be maintained against the Billing type
Create an output type and maintain the Driver program, Form routine and the layout.
Driver program is the name of the program that the system calls up to process the output
Form routine is the name of routine to be called up in the processing program
Layout is the name of a Sapscript layout set that can be designed as per user requirement
To enable printing of particular document for partner function, maintain the desired partner function against the output
type.
Printer communication details can be maintained by creating condition records where partner functions can be
assigned to output types
Copy Control from delivery to Billing
Page 10 of 64
(i) When excise and commercial invoice are the same

The copy control path is OR --> LF --> F2
When excise and commercial invoice are different, i.e. Multiple excise invoices for a single commercial invoice
The copy control path is OR JF JEX F2
To Maintain copy control for billing documents
Path: IMG Sales and Distribution Billing Billing documents Maintain copying control for billing documents
Maintain the following entries for Billing type F2 and Delivery type JF at item level
Item Category TAN
Copying requirements 310
Data VBRK/VBRP 351
Maintain the following entries for Billing type JEX and delivery type JF at item level
Item Category TAN
Copying requirements 311
Data VBRK/VBRP 351
To check the formula and change source if required
To check / change formula 310 & 311
VOFM --> Copying requirements --> Billing document --> Choose Formula (Source Text)
To check / change formula 351
VOFM --> Data transfer --> Billing document --> Choose Formula (Source Text)
Formula 310:
The routine is to be attached to the copying requirement in LF to F2 copy control for TAN item category. This is to be
used when the proforma invoice is used as reference for the excise invoice. ie. the procedure in sales is
SO -> LF -> JEX -> excise posting by J1II -> F2
The added functionality of this routine ensures that the excise posting takes place before the billing document is
created. In case of depot sale it ensures that the excise invoice selection has taken place before the billing document
is created.
Formula 311:
The additional check done in this routine is that post goods issue is done for the delivery document and it also
prevents multiple creation of the billing/pro forma document to which this formula is attached multiple times for the
same delivery item.
Data transfer - Billing documents:
This routine splits the items of a delivery into multiple billing/ proforma documents. The split is based on the following
fields : Distribution channel, division, delivery, chapter id and also the maximum number of items in a document is
picked up from the customization and imposed on the document being created
Return ->
Application
Assign excise invoice billing type to delivery type

The excise invoice can be created in combination with the customer invoice or separately (using a Proforma-type
invoice). These options are represented in the system by different document types and document flows. You need to
identify the billing document types that will be used as reference for Modvat utilization and assign them to the
respective delivery document types. Based on the assignment the system will also carry out consistency checks and
validations.
Requirements
The delivery types and copy control need to be maintained.
Create separate delivery types using IMG -> Sales and Distribution -> Shipping -> Deliveries - > Define
Delivery types
Setup copy control for the delivery types using IMG ->Sales and Distribution -> Shipping -> Deliveries - >
Specify copy control for Deliveries
Create Billing types using IMG -> Sales And Distribution -> Billing-> Billing Documents -> Define Billing
Types
Setup copy control for the billing types using IMG -> Sales And Distribution -> Billing -> Billing Documents ->
Maintain copy control for Billing types
Standard Settings
Setup has the delivery types LF anf JF defined for standard order OR. Billing type JEX has been defined for Proforma
excise document. Copy control is set as OR -> LF -> JEX -> F2 and OR -> JF -> F2
Recommendation
It is recommended that you use the standard setup in the delivered system. But if you so wish you can have your own
document types but you need to ensure that all the steps in the preconditions have been carried out.
Page 11 of 64
Activities
Assign a Modvat reference billing type to each delivery type.

Return ->
Application
Utilization Determination
In this activity, you specify which CENVAT accounts are to be debited by the Fortnight Utilization of CENVAT report:
When the report calculates how much excise duty you must remit, it automatically proposes which CENVAT accounts
the duty should be debited to. Here, you specify those defaults.
You can either:
Debit all the excise duty to one account
Debit the excise duty to more than one account, in which case you specify which percentage is to be debited
to each account
Example
If you want 50% of basic excise duty (BED) to be debited to the RG 23A account and the remaining 50% to the RG
23C account, you would make the following settings:
Acct name
BED perc.
RG 23A BED account
50
RG 23C BED account
50
Alternatively, to debit all of the BED to the RG 23A account, and then RG 23C account, if there is not enough in the
RG 23A account, you would make the following settings:
Acct name
BED perc.
+
RG 23A BED account
X
RG 23C BED account
X
When you come to run the report, the system takes the RG 23A account because it is the first one you have entered.
If this account does not cover the BED, the system takes the RG 23C account instead.
Return ->
Application
Excise group - Series Group Determination

In this activity, you can specify which excise group and series group you want to appear in these fields by default. You
can make separate settings for different combinations of sales organization, distribution channel, division, and
shipping point.
Activities
This activity is optional, unless you want the system to automatically create outgoing excise invoices when you create
a customer invoice.
In this case, you must also make the appropriate setting in Customizing for Global Settings, by choosing Excise
Groups and selecting E (Create Excise Invoice Automatically).
Return ->
Application
Forms
In the following activities, you make the settings for using forms in Country Version India.
Return ->
Application
Define form types

In this activity, you define which form types you want to record in the system. You can only use form tracking for the
form types that you enter here.
Example
Form type: CT3
Form description: Concessional tax form
Page 12 of 64
Status: Receive
Recommendation
Maintain the concessional form types here.
Return ->
Application
Tax Deducted at Source

In the following activities, you make the settings for tax deducted at source in Country Version India.
The SAP System offers two solutions for tax deducted at source:
Extended Withholding Tax

This is the generic withholding tax solution, used by many other countries other than India; we recommend that
users installing the SAP System for the first time use this solution.
Classic Tax Deducted at Source

This is solution developed specially for India and used in previous releases of Country Version India. This may
be discontinued in the future.
You only have to make the Customizing settings for the solution that you want to use, either Extended Withholding
Tax or Classic Tax Deducted at Source.
Return ->
Application

This solution supports company codes for which you have activated the extended withholding tax option. To use this
solution, you have to work through:
The standard Implementation Guide for Extended Withholding Tax
The activities in the CIN IMG for Extended Withholding Tax

As you make the Customizing settings, note the following:
In the standard IMG, ignore the activities for certificate printing, since this feature is covered by other
activities in the CIN IMG. However, for the certificate printing programs to work, you must select No
certificate numbering in the tax types.
The various sections of the Income Tax Act are mapped to official withholding tax keys field of the tax code.
We therefore recommend that you assign official keys to all tax codes.
Receipient types are used extensively in programs, so we recommend that you assign receipient types to
tax types and then attach these to the appropriate vendor master records.
The tax types used for one-time vendors must not be enabled for accumulation.
Return ->
Application
Define Business Place

In this activity, you maintain the information about the local tax offices that you have dealings with.
The use of business places is mandatory.
Activities
Create a business place for each tax office that you are registered with and, in the address data (which is printed on
the vendor withholding tax certificates) maintain the data as follows:
Name (lines 1 and 2)

Enter the name of the tax office.
Name (lines 3 and 4)

In these fields, enter the TDS range and circle respectively for annual returns.
Search term 1
Enter your tax deduction account number (TAN) at this office.
Street 2, Street 3, and Street/House number

Enter the business place's postal address.
District
Postal code/City
Enter your PIN code and city.
Page 13 of 64
Return ->
Application
Withholding Tax on Clearing Accounts and Adjustment of Tax I

In the following activities, you make the settings required by the Calculation of Withholding Tax on Clearing
Accounts report and for when you adjust withholding tax items.
Return ->
Application
Assign Document Types

In this activity, you specify which document types you want to use for adjustments to withholding tax items and
withholding tax on clearing accounts.
Requirements
You must have created the document type already.
Recommendation
Whether you use separate document types for the transactions will vary on your own particular requirements.
Return ->
Application
Specify Which Clearing Accounts Are Liable to Withholding Tax

In this activity, you define which G/L accounts need to be adjusted by the Calculation of Withholding Tax on
Clearing Accounts report.
Activities
Enter each G/L account that you want the report to cover, specifying the company code.
Return ->
Application
Specify Which G/L Accounts to Post Withholding Tax and Losse

In this activity, you specify to which G/L accounts the system must post:
Withholding tax calculated by the Calculation of Withholding Tax on Clearing Accounts report
Any losses incurred when you adjust withholding tax items

Recommendation
In the case of the withholding tax on clearing accounts, we recommend that you maintain separate G/L accounts for
each tax type.
For most businesses, a single account will suffice for all losses incurred by adjustments to withholding tax items.
Return ->
Application
Calculation of Surcharges
In the following activities, you make the settings required in order for the system to be able to calculate surcharges
when you post a vendor invoice.
Return ->
Application
Maintain Surcharge Calculation Methods

In this activity, you specify which method you want to use to handle surcharge taxes, according to whether you wish
your business to show basic withholding tax and surcharges separately, or whether they can be combined. The SAP
System offers you two choices:
You can define tax codes that contain both the basic tax and the surcharge tax.
Page 14 of 64
You can define separate tax codes for basic tax and surcharge tax respectively.
Example
The rate of your base tax of income tax is 2%, and the surcharge tax is 10% of that, giving an overall tax rate of 2.2%.
Depending on which method you select in this activity, you would therefore define:
Two separate tax codes, one at 2% and one at 10%
One tax code at 2.2%

Recommendation
Some tax offices prefer you to show surcharges separately from basic withholding tax; others prefer the two to be
rolled into one. You cannot customize this information at business place (tax office) level, so we recommend that you
use the method that is preferred by the majority of your tax offices.
Activities
For each company code, specify which method you want.
After you have done that, carry out either of the two following activities, depending on what method you have
selected.
Return ->
Application
Maintain Surcharge Tax Codes (Separate Tax Codes)

In this activity, you maintain the tax codes that you want to use for surcharges. During challan update, the surcharge
tax codes are referred to and appropriately displayed. At the time of Annual returns also, the surcharge tax codes
would be referred.
Example
In case of Section 194(C), the surcharge rates are 15% for individuals with estimated annual income over Rs150000
and for all other categories it is 10%,. When documents are posted, the surcharges are deducted using appropriate
tax codes in addition to basic tax rates. These surcharge tax codes are entered here for use during challan update
and annual returns.
Requirements
You must only perform this activity if you have specified that you want to use a separate tax code for surcharges in
the previous activity ( Maintain Surcharge Maintenance Methods). Otherwise, use the next activity ( Maintain
Surcharge Rates).
Return ->
Application
Maintain Surcharge Rates (Surcharges Combined with Basic WH

In this activity, you maintain the surcharge rates for various permutations of tax codes and recipient types.
Recommendation
the first activity in this section ( Maintain Surcharge Maintenance Methods). Otherwise, use activity Maintain
Surcharge Tax Codes.
Activities
For each combination of tax code and recipient type, enter the surcharge rate that is to be applied over and above the
basic withholding tax.
Return ->
Application
Calculation of Surcharges
In the following activities, you make the settings required in order for the system to be able to calculate surcharges
when you post a vendor invoice.
Return ->
Application
Maintain Surcharge Calculation Methods

In this activity, you specify which method you want to use to handle surcharge taxes, according to whether you wish
your business to show basic withholding tax and surcharges separately, or whether they can be combined. The SAP
System offers you two choices:
Page 15 of 64
You can define tax codes that contain both the basic tax and the surcharge tax.
You can define separate tax codes for basic tax and surcharge tax respectively.
Example
The rate of your base tax of income tax is 2%, and the surcharge tax is 10% of that, giving an overall tax rate of 2.2%.
Depending on which method you select in this activity, you would therefore define:
Two separate tax codes, one at 2% and one at 10%
One tax code at 2.2%

Recommendation
Some tax offices prefer you to show surcharges separately from basic withholding tax; others prefer the two to be
rolled into one. You cannot customize this information at business place (tax office) level, so we recommend that you
use the method that is preferred by the majority of your tax offices.
Activities
For each company code, specify which method you want.
After you have done that, carry out either of the two following activities, depending on what method you have
selected.
Return ->
Application
Maintain Surcharge Tax Codes (Separate Tax Codes)

In this activity, you maintain the tax codes that you want to use for surcharges. During challan update, the surcharge
tax codes are referred to and appropriately displayed. At the time of Annual returns also, the surcharge tax codes
would be referred.
Example
In case of Section 194(C), the surcharge rates are 15% for individuals with estimated annual income over Rs150000
and for all other categories it is 10%,. When documents are posted, the surcharges are deducted using appropriate
tax codes in addition to basic tax rates. These surcharge tax codes are entered here for use during challan update
and annual returns.
Requirements
the previous activity ( Maintain Surcharge Maintenance Methods). Otherwise, use the next activity ( Maintain
Surcharge Rates).
Return ->
Application
Maintain Surcharge Rates (Surcharges Combined with Basic WH

In this activity, you maintain the surcharge rates for various permutations of tax codes and recipient types.
Recommendation
the first activity in this section ( Maintain Surcharge Maintenance Methods). Otherwise, use activity Maintain
Surcharge Tax Codes.
Activities
For each combination of tax code and recipient type, enter the surcharge rate that is to be applied over and above the
basic withholding tax.
Return ->
Application
Determination of Tax Due Dates

In the following activities, you make the settings that allow the system to calculate the tax due date (that is, the date
on which the withholding tax must be remitted by) when you post an invoice.
Return ->
Application
Page 16 of 64
Assign Factory Calendars to Business Places

In this activity, you effectively specify which days the tax offices that you work with are open. The system uses this
information when you post a vendor invoice, so that it can allow for public holidays when it determines the tax due
date.
Note
This activity is optional. If you do not make any entries, the system still determines the tax due date, but without
reference to any factory calendar.
Requirements
You have maintained factory calenders for each of the calendars followed by the tax offices.
Activities
For each business place (tax office):
Assign a factory calendar
Specify whether, in the event of a tax due date falling on a holiday, the office requires you to remit the tax on
the day before the holiday, or on the day after.
Return ->
Application
Maintain Tax Due Dates for Tax Types

In this activity, you maintain the various tax due dates. Because due dates can differ, depending on the withholding
tax type and recipient type, you can maintain the dates at this level.
Note
Make sure that you maintain entries for all the recipient types that you use.
Activities
For each permutation of official withholding tax key and recipient type, specify when the tax has to be remitted:
Where tax is due on the seventh day of each month, enter 777 in the tax due date field.
Where tax is due in a specific number of days' time after being posted, enter this number in the field. For
example, if the tax has to be remitted within three days, enter 3.
Return ->
Application
Creation of Remittance Challans

In the following activities, you make the settings that enable the system to create the system documents when you
remit withholding tax to the tax office using withholding tax remittance report.
Document Type
In the first activity, you specify which document type you want the system to make the postings with.
Numbering
In the following activities, you set up the numbering for the challans.
Since you must create one challan for the taxes in each section of the Income Tax Law (official withholding tax keys),
and for separate tax offices (business place), you must create different number range objects for each permutation of
official withholding tax key and business place.
The procedure is as follows:
1. For each permutation of tax key and business place, create a number group.
2. For each number group, create a number range.
3. Assign each number group to a number range.
You have to follow this procedure for technical reasons.
Return ->
Application
Page 17 of 64
Maintain Document Type

In this activity, you specify which document type the withholding tax remittance report is to use to post clearing
documents.
Return ->
Application
Maintain Number Groups

In this activity, you group together the permutations of company code, business place, and official withholding tax key
that you want to remit withholding tax for. You can assign the same group number to more than one permutation, if
you need to.
Return ->
Application
Assign Number Ranges to Number Groups

The Number Group maintained in the step ' Maintain Number Groups' is attached to a Number Key here. This
number key is referred to in the number range maintenance. This two step maintenance facilitates maintenance of
number ranges for 3 entities - company code, Business Place and section.
Return ->
Application
Maintain Number Ranges

In this activity, you maintain the number ranges that the system is to use to number the challans.
Activities
Define a number range for each number group that you have defined in the previous activity.
Return ->
Application
Posting of Withholding Tax Certificates from Customers
In this activity, you make the settings required for when you:
Post a withholding tax certificate sent to you by a customer
Create a remittance challan

Activities
Specify:
The G/L account number of the customer tax creditable account, to which the system is to clear the
withholding tax when you post a customer withholding tax certificate
We recommend that you define a separate customer tax creditable account for each section of the Income Tax
Law (that is, for each official withholding tax key). Then, when you come to post tax withholdings made by your
customers, the tax is posted to different accounts, depending on the section. This procedure makes it easier for
you when you come to choose which tax items you want to clear.
Return ->
Application
Withholding Tax Certificates

In the following activities, you make the settings that the system uses when Printing withholding tax certificates
Vendors: or Printing withholding tax certificates Customers:
Which SAPscript forms you want to print the certificates with
How you want the certificates to be numbered

You will probably have to use separate certifcates for each type of withholding tax (each official withholding tax key),
and you may have to use different forms for different tax offices (business places).
Page 18 of 64
The procedure is as follows:

1. For each official withholding tax key, create a number group and assign it a SAPscript form.
2. For each number group, create a number range.
3. Assign each number group to a number range.
You have to follow this procedure for technical reasons.
Return ->
Application
Maintain Number Groups and SAPscript Forms

In this activity, you specify which SAPscript forms you want to use to print the withholding tax certificates.
Requirements
You must have created the SAPscript forms already. A form is supplied with the standard system, J_1IEWTCERT,
which you can use as the basis for creating your own forms for vendors as well as customers
Activities
For each section of the Income Tax Law (official withholding tax key):
Specify which SAPscript form you want to use

If different tax offices require different forms, you can enter different forms for different offices.
Specify what number group you want for each certificate.

This information determines which number range the system uses to number the certificates. You assign the
number range to the number group in the next two activities.
Return ->
Application

In this activity, you assign the number groups to number ranges, both of which you defined in the previous two
activities. For Classic TDS certificate Printing, the Number groups are assigned to sections . For Eextended
withholding tax Certificate Printing, the number groups are assigned to a combination of Business Place and Section .
Return ->
Application
Maintain Number Ranges for Certificates

In this activity, you maintain the number ranges that the system is to use to number the vendor withholding tax
certificates.
Activities
Return ->
Application
Maintain Vendor's PAN for Certificates

In this activity, you maintain your vendors' permanent account numbers (PANs). This information is then printed on
their withholding tax certificates.
Activities
Carry out this activity for all of the vendors that you withhold tax from.
Return ->
Application
Maintain Customer's PAN for Certificates

In this activity you maintain the Permanent account number (PAN) for the Customer accounts to be printed in the
Withholding tax certificate certificates.
Page 19 of 64
Return ->
Application
Migration from Classic TDS to Extended Withholding Tax

Presently you are using Classic withholding tax solution and you would like to move to extended withholidng tax
solution . You would need to run a migration program to convert classic withholding tax data to be compatible with
extended withholding tax . This node is relevant for those who are using the Add-on, Country Version India ( CIN )
only. For customers who have not used CIN, pls refer to the standard migration program and documentation .
This is only relavant for those upgrading from CIN versions 2.0C, 2.1B, 2.2B & 30A Classic and then to Extended
withholding tax solution.
Consider the following before choosing to switch to EWT.
1. The customizing required for EWT could be done in three parts.
Country level customizing
Company code customizing in R/3
Indian Localization customizing.

Smooth transition is dependent on proper customizing since once EWT is switched on, it cannot be switched off
without inconsistencies.
Carry out country level customizing and run the health check program j_1iewt_health_check to list out probable errors
in customizing and correct the errors reported. Run the health check program to obtain a list of the following
Invoice with payment tax codes are not migrated. So these invoices would need to be either
processed prior to stwitch or reversed and recreated after the swtich.
Recurring documents, parked documents and DP requests not yet paid are not migrated. These
would also need to be evaluated before the switch.
2. Switch the company code to EWT mode. At this stage, the following would need to be done. Company specific
customizing in R/3 Master data creation for business partners.
Company specific customizing in R/3
Master data creation for business partners.
Localization customizing.
Run the health check program again, with company code so that the possible inconsistencies are corrected prior to
posting documents in EWT mode.
3. Run the migration program. Invoices, Clearings, Credit memos and TDS documents on the above are required to
be migrated only if they are unpaid or if the payment reversal will be made after switching to EWT. So restrict the
selection to these documents
In respect of Down payments, only the uncleared portion of the downpayment is migrated. Choose the correct
business place for the downpayment .
4. Continue TDS processing depending on at what point of time the documents were created.
For example if an invoice is created in classic mode and TDS posted is on it using periodic TDS posting program,
carry out challan update, tax certificate printing etc, for this document using classic TDS programs only, though EWT
is active for the company code at the time of running these programs. TDS processing programs in EWT such as
Challan update, cert printing, JV program will work only for those documents that are created in EWT mode.
Till the classic documents are fully processed, the classic TDS programs should be run for those documents. So for
some time period, programs such as challan update and certificate print programs would be running in both the
modes, though only EWT is active.
5. As soon as the status of a migrated document changes, like for example invoice is migrated but after migration,
TDS is posted on it. Again the migration program is required to be run to migrate the TDS document.
6. In respect of down payments, once migrated, the tax adjustment on clearing against an EWT invoice, would
happen along with the posting of a clearing document. The further processing of this tax adjustment would happen in
EWT mode.
If after migration, the down payment is cleared against a classic invoice the tax adjustment would happen only on
running the periodic tax adjustment program. In this event the further processing would happen with classic programs
After changeover to extended withholding tax, if you face any errors in challan updation or certificate printing or in
vendor payment , check for migrated data and if required run the data migration program again to take care of the
delta migration .
Return ->
Application
Page 20 of 64
Health Check
Example
This program scans through the customising done for extended withholding tax and also checks the documents
posted in classic withholding tax. Inconsistencies are output as a list for the user to rectify before the migration
programs is run.
Requirements
The helath check program needs to be run prior to migration . Refer program documentation for running the program.
Standard Settings
This documentation is applicable for those who are using the Add-on, Country Version India ( CIN ) only. For
customers who do not use CIN, pls refer to the standard migration program and documentation .
Recommendation
Refer to the program documentation for details. Also refer the manual for the migration program.
Activities
Complete the Eextedded withholding tax customisng before running this program.
Return ->
Application
Migration Program
Example
Presently you are using Classic withholding tax solution and you would like to move to extended withholidng tax
solution . You would need to run this program to convert classic withholding tax data to be compatible with extended
withholding tax .
Requirements
This note is relevant for those who are using the Add-on, Country Version India ( CIN ) only. For customers who do
not use CIN, pls refer to the standard migration program and documentation .
Standard Settings
Extended withholding is to be made active for the company code.
Recommendation
This is not required for fresh CIN 40A installations where extended withholding tax is made active on going live .
Ensure that no Finacial accounting documents are being posted while running this program .
Further Notes
Run the health check program before executing the migration program.
Return ->
Application
Classic Tax Deducted at Source

This solution supports company codes for which you have not activated the extended withholding tax solution.
In order to use this solution, work through
The standard Implementation Guide for Withholding Tax
The activities here under Classic Tax Deducted at Source.

Return ->
Application
Section Maintenance
Maintain section type and description for all TDS sections here.
We can link tax codes to TDS sections only for the TDS sections defined here.
Maintain Surcharge applicablility and also the number groups for certificate printing.
The number groups are assigned to number keys in the node for certificate printing.
Example
TDS Section Section type Description
194J J Professional fees
Recommendation
Page 21 of 64
Maintain this for all the TDS sections.

Return ->
Application
TDS Section - Tax Code Relationship

Assign TDS sections to Tax Codes here.
Example
o Tax Code - W1.
o TDS Section - 194C.
Activities
Helps to build section -> tax code -> G/L Account link.
Further Notes
TDS Section wise balances can be computed.
Return ->
Application
Payment Due Date Maintenance

The number of days after which the payment is due has to maintained for each section and for each type of recipient
When TDS posting is done the payment due date is calculated and this is used by challan to distinguish the
payments which are due on that date.
Recommendation
Make sure that you maintain entries for all the recipient types that you use.
Activities
For each permutation of official withholding tax key and recipient type, specify when the tax has to be remitted:
Where tax is due on the seventh day of each month, enter 777 in the tax due date field.
Where tax is due in specific number of days ' time after being posted , enter this number in the field. For
example if the tax is to be remitted within 3 days , enter 3 .
Return ->
Application
Vendor Certificate Printing
No Document

In this activity, you assign the number groups to number ranges, both of which you defined in the previous two
activities. For Classic TDS certificate Printing, the Number groups are assigned to sections . For Eextended
withholding tax Certificate Printing, the number groups are assigned to a combination of Business Place and Section .
Return ->
Application
Maintain Number Ranges for Certificates

In this activity, you maintain the number ranges that the system is to use to number the vendor withholding tax
certificates.
Activities
Return ->
Application
Text Determination
No Document
Page 22 of 64
Long Texts
In this IMG activity, you define the different types of long texts that you want to be able to maintain in the various
excise transactions.
There is no limit to the number of types of long texts you can define.
Activities
For each long text, you have to specify which transactions the long texts are for, so fill out the Object field
accordingly:
Transactions involving
Code
Excise invoices
J1IA
Excise JVs
J1IH
Subcontracting 57F4
J1IF
Factory sales
J1II
Fortnightly payment
J1IU
For example, if you want to create a long text for the Incoming Excise Invoices transaction, enter J1IA.
Then give the long text an ID and description of your choice.
Return ->
Application
Number Ranges
No Docment
Number Ranges
You can maintain the number ranges for all CIN Number range objects using this transaction
Activities
Please maintain the number ranges for the folllowing objects The no nr has to be '01' for all
1. j_1iintnum
At an Excise group
1. j_1irg23a1
2. j_1irg23a2
3. j_1iRG1
4. j_1irg23c1
5. j_1irg23c2
6. j_1ipla2
7. j_1iintpr2
8. j_1irg23d
9. j_1irg1_t ( material level)
10. j_1iconpla ( if Consolidated PLA is used )
At Series group
1. j_1iexcloc
2. j_1iexcexp
3. j_1idepinv
4. j_1i57Fc ( 57F Challans )
Return ->
Application
Reports
No Document
Maintain SAP Script Layouts

For each of your company codes maintain the SAP script layouts for the
registers as follows
Register Name
Layout no
Layout set
RG23A1
1
J_2IRG23A_PART1
RG23C1
1
J_2IRG23C_PART1
RG23A2
1
J_2IRG23A_PART2
Layout program
J_2IRAP1
J_2IRCP1
J_2IRAP2
Page 23 of 64
RG23C2
1
J_2IRG23C_PART2
PLA
1
J_2I_PLA
RG23D
1
J_2I_RG23D
RG1
1
J_2I_RG1
RT12 1 J_2I_RT12_ABSTRA J_2IRT12
RT12 1 J_2I_RT12_ABSTRA J_2IRT12
RT12 1 J_2I_RT12_3 J_2IRT12
The layout description can be left blank or an appropriate description
maybe filled in. You may not change the register name. You can have
your own layouts and maintain the name here. If the output device and
number of copies are maintained it is automatically picked up for
printing
Return ->
Application
J_2IRCP2
J_2IPLA
J_2IRG23
J_2IRRG1
Message Configuration
No Document
Message type configuration
No Document
CIN 2.0B Release Notes
Release notes- Materials Management
Short text
MODVAT credit on the countervailing duty paid for imports.
Description
On imports customs duty is paid and MODVAT credit can be availed on the countervailing duty portion of the customs
duty. This CVD component may or may not be available in the PO. In case it is not available on the PO the same can
be captured in the excise invoice. Based on the excise invoice MODVAT credit can be availed.
Return ->
Application
Short text
Excise invoice can be created with out referencing a PO or a GR
Description
Modvat credit can be availed by a company if the consignee (ship to ) is the company. The purchase order for the
goods which are mentioned inthe excise invoice need not be raised by the company. In such cases PO need not
exist. Excise invoice can be captured giving the actual excise paid details of the vendor and MODVAT can be availed.
In these cases even goods receipt is not mandatory. Excise Part1 and Part2 registers are created based on the
excise invoice itself.
Return ->
Application
Page 24 of 64
Short text
MODVAT credit can be availed on inter-plant transfers based on stock
transport order.
Description
When goods are transferred from one plant to another for processing excise is paid by the sender on which MODVAT
credit can be availed by receiving plant. This is possible by capturing the excise invoice with reference to the stock
transport order.
Return ->
Application
Short text
Availment of partial MODVAT credit.
Description
Based on the nature of the industry and other stipulations, only a specific percentage of the excise duty that has been
paid can be availed as MODVAT credit. The balance of the excise duty has to be passed on to the material value.
Effects on Customizing
Partial credit allowed has to marked as required in the Excise registration settings of IMG. Excise registration
The tax code used for the purchase order should reflect the extent of MODVAT that can be taken and the extent to be
loaded on to inventory.
Return ->
Application
Release notes - Sales and Distribution
Short text
Excise invoice based on a material issue, Vendors excise invoice or
Plant excise invoice or with a general reference.
Description
Excise invoice can be created for any outgoing material based on
1. Material issue document
2. Vendors excise invoice (Vendor returns)
3. Excise invoice at factory sales - (A-certificates - Sales returns)
4. Any other document
In case the reference document has excise details the same gets copied. MODVAT utilization can be done if excise
duty has been paid and the excise invoice gets generated. The excise invoice can be printed after posting.
Return ->
Application
Page 25 of 64
Short text
Excise based on pricing reference material/
Description
If a pricing reference material is maintained in the sales view of the material master , the same can be used as
reference for excise. Excise tariff needs to be maintained only for the reference material and this gets copied to the
Sales order just like any other pricing condition.
Return ->
Application
Short text
User-exits in transactions J1II J1IG and J1IJ
Description
User-exits have been provided before save in
1. MODVAT utilization J1II
2. Depot receipts J1IG
3. Depot sales J1IJ
Return ->
Application
CIN 2.0C & CIN 2.1B Release Notes
Release notes - Materials Managements
Short text
Multiple GR for single Excise Invoice
Description New customizing option provided at the plant level to identify whether multiple GR's are allowed for an
excise invoice. Also customer can set whether multiple credit is allowed for a single excise invoice. At the time of
creation of GR system will allow multiple GR's. Then while availing credit there can be an override set at material
level for multiple credit. Based on this system will allow multiple credit can be taken
Return ->
Application
Short text
Enhancements to CVD solution
Description
For import purchases the customs duty can be configured as delivery charges on the purchase order. The CVD
condition type has to be defined in J1IT. The customs duty payment can be made by processing the delivery charges
for the invoice. Later excise invoice can be created for this PO with reference to the delivery charges invoice. The
actual CVD paid in local currency can be picked up and shown for capture. The GR when made with reference to the
excise invoice will not consider this particular delivery cost for valuation. The excise invoice can be posted
subsequently and credit taken to RG23.
Page 26 of 64
Return ->
Application
Enhancement to Partial Modvat Credit solution
No Document
Short text
Pricing date control in excise
Description
Even when the purchase order is set to have pricing date control at GR, excise value captured will be used to
calculate the non-deductible tax.
Return ->
Application
Short text
Order price unit in excise
Description
When the order price unit is different from the ordering unit, excise invoice capture is possible with order price unit.
Also if the quantity in order price unit is changed in GR the subsequent adjustment of MODVAT and valuation is taken
care of.
Return ->
Application
Immediate credit on consumables
No Document
Excise invoice without PO for capital goods
No Document
Display of capital goods document
No Document
Short text
Alternate assets MODVAT capitalization
Description
An account assigned PO can be used for the procurement of assets. There is no need to take the asset into stock.
The GR can be made directly to an internal order, WBS, network or cost center. The excise invoice verification puts
modvat to on-hold.
It is possible to allocate the excise invoices directly to the asset. This asset can optionally be validated with fixed
assets. Selection possible on wide range of parameters for the excise invoices to be picked up. Allocation of excise
invoices ( Inclusion/exclusion of excise invoices for an asset ) possible until the asset is installed. Nosplitting of excise
invoices across assets. Partial capitalization of one excise invoice not possible Allocate excise invoice to an asset as
declared to excise.
Installation certificate for an asset can be entered. Accumulated modvat credit for the asset can be displayed and it is
possible to go to details display of all excise invoices. This takes the modvat credit on to RG23C Part2.
Page 27 of 64
Return ->
Application
57F4 Utilization from RG23AED and SED
No Document
57F4 completion list
Short text
Excise invoice posting could be put on hold by marking a rejection
indicator and keeping it as status 'P'.
Description
Excise invoice can be set to hold by putting a rejection indicator. This will help to mark the status as 'P' and hence
system will consider this amount while proposing vendor payment. But still the system will not take this amount into
CENVAT credit. A report is available which will list all the excise invoices where rejection indicator is set and this can
transfer the credit to CENVAT.
Return ->
Application
Short text
Various enhancements have been made to 57F4
Description
57F4 for stock transfers and vendor returns
Cancellation of 57F4 after posting
Facility for entry of pre-printed number during printing
Time of removal in 57F4
Rounding off of duty in 57F4
Enhancements to pending 57F4 list
Return ->
Application
Excise invoice for vendor returns
No Document
Display of RG23 Part1 and Part2 entries
No Document
User-exits have been added for customer validations

Description
User exit in Excise invoice capture to decide the MODVAT Credit
User exit in verify-post for rounding MODVAT credit
User exit in Excise invoice without PO for validation of material docu
Return ->
Application
Page 28 of 64
Release notes - Sales and distribution

No Document
RG23D receipts for sales returns
Short text
Printing of excise invoice for other movements
Description
Allows to print according to layout set maintained by customers
Allows capture of pre-printed excise invoice number during printing
Return ->
Application
RG23D serial number generation
No Document
Enhancements to depot receipts
Enhancements to depot sales
Cancellation of excise invoice for other movements
Inter company utilization
Sub transaction type for alternate account
Excise invoice selection in Excise other movements
Sales tax register - location wise
Minimum balance check across GL accounts
No Document
Release notes - Financial Accounting
Short text
Business Area wise Posting
Description
Now it is possible to Post TDS documents Per business Area or a range
of business Areas Provided the original document is posted with Business Area. The TDS line item is also posted with
business
Area as inherited from parent document
Software/Hardware Requirements
None
Installation Information
None
Page 29 of 64
Effects on System Administration

None
None
Changes in Procedure
None
Dependent Functions
None
Planning
None
Further Notes
None
Return ->
Application
Short text
Posting to Special periods:
Description
Now posting to special Periods is possible, provided normal posting
periods are closed. The special posting period is chosen from
selection screen
Dependent Functions
none
Return ->
Application
Short text
Copy Invoice Reference:
Description
If the invoice is filled with a reference document number or any text,
the same is copied onto the TDS document also.
Return ->
Application
Page 30 of 64
Short text
Profit center Posting:
Description
If the reference invoice holds profit center, the TDS document is also p
is also posted with that Profit center.
Return ->
Application
Short text
One time vendors:
Now one time vendor certificates can be separately printed
under program J_1ITDS6.
The main certificate printing program will not print certificate for one
time vendors.
Bank Key:Now bank key is added to selection screen so that the bank
details are picked from the key and certificates are printed using thi
this key.
Place of Printing:
Place of printing is added to selection screen.
Vendor wise Printing:
It is possible to print vendor wise certificates selectively.
User Exits:
New user exits have been provided to get TAN/PAN numbers for
Vendors
and for one time vendors.
Return ->
Application
Page 31 of 64
Short text
Annual Return Programs
Description
New Annual return programs are provided to print returns
under Sections 194C,D,I,J
Return ->
Application
Surcharge on TDS
No Document
Short text
Copy House Bank to TDS documents
Description
A new program J_1IHBKD (Transaction J1IHBK) has been provided to copy House Bank
as in Vendor Invoices into Vendor line created during
TDS posting.
Return ->
Application
Short text
Challan Update:
Description
Challan Update Program uses Open item clearing funtions
of R/3 to clear the Tax lines and generate Internal challan
numbers. The Challan numbers received from Bank can then
be updated separately.
It is possible to reverse the tax payment document and
repost.
Return ->
Application
Short text
Certificate Printing.
Description
Following new features have been provided.
1. Customizable layout sets have been provided per section and
business place.
2. Both one time vendors and normal vendor certificates can
be printed by the same program.
3. Number range objects can be maintained per business place
Page 32 of 64
and section
Return ->
Application
Short text
Tax Adjustment
Description
When Tax Lines need to be corrected after challans have been
paid or certificates issued, this functionality can be used.
It provides for amount correction as well as Tax code
correction.
Return ->
Application
Short text
Tax on Services
Description
It is possible to post tax on services which were
booked earlier for which no invoices have been received.
The posting happens to Tax Provisions account. The provisions
are reversed at the time of Invoice verification
Return ->
Application
Short text
Tax Adjustment on DP Clearing
Description
At the time of clearing of a down payment against an Invoice, the proprotional tax
deducted on the invoice is refunded to vendor provided the sections on tax deducted during Down payment and
Invoice are the same and the business place on both documents are the same.
Return ->
Application
Short text
Payment Due Dates
Description
Payment Due Dates are determined at the time of posting
FI documents with withholding tax lines. The due dates
can be customized for Recipient type and section.
In addition, Calender IDs can be attached to
Page 33 of 64
Business Place to pick the next or previous day in case

the due date happens to be a holiday.
Return ->
Application
Release notes Others
Data extraction and printing for excise registers
Customizing Wizard for Health Check
Configurable messages
New authorization checks
CIN 30A Release notes

Release notes Procurement
Short text
CENVAT credit on capital goods after budget 2000
Description
For capital goods 50% of the CENVAT credit can be taken immediately on goods receipt. This is done when you
Verify the vendor excise invoice. For the balance credit which is available it is possible to take it into CENVAT using
this functionality. It is also possible to transfer only a portion of the balance credit into CENVAT.
In case you have already taken the credit on capital purchases into Onhold before April 2000 then using the above
facility you can transfer it into CENVAT.
The immediate credit on consumables at the company code level has to be marked on always.
The treatment is same irrespective of whether you keep the material type indicator as 'A' - Assets , 'C" - Consumables
or 'T' - Tools. There is no differential treatment for these as there in legal requirement.
Return ->
Application
Short text
Monthly CENVAT register as per the format given by Excise under rule
57AE
Description
Monthly CENVAT register is required to be submitted to the authorities showing the CENVAT credit availed on inputs
and capital goods separately. The report gives the CENVAT opening balance of the various duty components, credits
and debits for the period and the closing balance. This also gives an annexure as per the format prescribed by the
rule detaling all the excise invoices.
Return ->
Application
Page 34 of 64
Short text
Excise on SSI vendors
Description
The vendor can be classified as Small Scale Vendor. Even with in SSI the vendor could be using the CENVAT
scheme or not. The status of this can be captured. The excise rate if the vendor does not take credit will be a flat
percentage which you maintain in the system. In case he takes CENVAT credit then he has to be applied a portion of
the normal excise rate based on the slab in which he falls.
The flat rates and the proportion for normal excise has to be maintained for different SSI slabs.
Return ->
Application
Short text
Quantity based AED and SED
Description
Additional excise duty AED and Special excise duty can be given as quantity based also in addition to being
advalorem. It is possible to capture this quantity based AED and SED rates and use it for Excise calculation
Dependent Functions
The master data for the quantity based rates has to be maintained for AED and SED for the materials which attract
this duty.
Further Notes
The quantity based duty is over and above the Normal CENVAT duty
Return ->
Application
Short text
Excise invoice number can be captured in the new Enjoy Goods
receipt transaction
Description
When Goods receipt is done using the new Enjoy Goods receipt a new tab will come up for Excise invoice details.
You can enter the excise invoice number , year and the excise group in which it should go. Also If the Goods receipt
is done prioi to Excise invoice capture then you can enter the excise group and the register type and system will
create Part1 entries in the respective register. If no Part1 entry is required for a GR then you need to mark the
register column as 'NOREG'
Return ->
Application
Page 35 of 64
Short text
Excise calculation in new Enjoy Invoice verification
Description
Excise value proposal possible for new Enjoy invoice verification
Return ->
Application
Short text
Proposal of CVD during Delivery cost invoice verification
Description
For import purchase order if the customer is following a process of GR based IV and he is booking the customs
charges as a delivery charge invoice after Goods receipt and excise invoice then the amount captured will be
defaulted on to the invoice proposal
Return ->
Application
Short text
Excise value is considered during ERS
Description
Excise value calculation is possible during ERS payments to vendors.
The limitation to this process is that it works well when there are single items per goods receipt as ERS applies the
taxes at the header level and not at item level
Return ->
Application
Short text
Excise invoice can be booked for a vendor with preliminary parking
and later posting of the vendor invoice
Description
Excise invoice calculation is possible even with preliminary posting of the vendor invoice.
Return ->
Application
Page 36 of 64
Short text
Excise invoice posting could be put on hold by marking a rejection
indicator and keeping it as status 'P'.
Description
Excise invoice can be set to hold by putting a rejection indicator. This will help to mark the status as 'P' and hence
system will consider this amount while proposing vendor payment. But still the system will not take this amount into
CENVAT credit. A report is available which will list all the excise invoices where rejection indicator is set and this can
transfer the credit to CENVAT.
Return ->
Application
Short text
Separate tax bases possible for excise and sales tax during tax
calculation in purchase order
Description
Separate tax bases possible for excise and sales tax. Excise can have a base of assessable value but the sales tax
can be the net price on the Purchase order
Return ->
Application
Short text
Quantity based Excise rates possible for AED and SED
Description
It is possible to maintain the rates of AED and SED based on the quantity.
Return ->
Application
Short text
Logistics invoice verification with multiple allocation possible
Description
Logistics invoice verification with all possible options is supported along with excise calculation
Return ->
Application
Page 37 of 64
Short text
Sub transaction type can be entered during excise invoice verification
to allow alternate account determination.
Description
Sub transaction type can be entered in the excise invoice verification and this allows to have alternate account
determination.
Return ->
Application
Short text
Profit center documents are created during postings of excise
Description
Profit center document creation during excise invoice
Return ->
Application
Short text
Sub transaction type possible in Excise invoice without PO to allow
alternate account determination
Description
Sub transaction type can be entered during Excise invoice without PO and this will allow alternate account
determination
Return ->
Application
Short text
Rounding at item level can be set separately for Procurement and
Sales
Description
Rounding indicator for round off of duty at item level cna be set separately for Procurement and Sales transactions in
CIN
Return ->
Application
Page 38 of 64
Short text
RBI exchange rate for CVD excise invoices
Description
For taking credit on the CVD component of import purchases we need to know the RBI exchange rate during the time
of CVD payment. You can define a separate exchage rate type and maintain the RBI exchange rate for import
purchases. This has to be maintained in CIN IMG and will be picked up during Excise invoice creation for foreign
POs.
Return ->
Application
Short text
Excise invoice calculation during subsequent credits to vendor
Description
Subsequent credit cane be booked to vendor through invoice verification and Excise value will be calculated
proportionately
Return ->
Application
Short text
Depot or factory identification at the excise group level
Description
You can have a single plant and with in that multiple excise groups. Each group could point to a factory or depot. You
can leave the setting at the plant blank and then do at the excise group level
Return ->
Application
Short text
Multiple excise registration possible for a plant
Description
A plant in SAP can have multiple excise registrations. This is achieved by shifting the excise registration to excise
group level and making it possible to have multiple excise groups attached to one plant
Return ->
Application
Page 39 of 64
Short text
Excise invoice quantity can be defaulted in GR
Description
If user wants so he can set the customization option at excise group level to default excise invoice quantity during
Goods receipt
Return ->
Application
Flagging mis-match between excise invoice and Goods receipt

quantity
Description
When there is difference between excise invoice quantity and Goods receipt quantity system can flag a message that
mis-match exists
Return ->
Application
Automatic Excise invoice pickup during GR cancellation using

'Cancel Goods receipt'
Description
User need not enter the excise invoice during the pop-up while cancelling GR using 'MST - Cancel Goods receipt'.
System will automatically pickup the excise invoice information from the original GR and use it for cancellation of
Part1.
Return ->
Application
Excise invoice query in customizable list format

Description
Excise invoice query has been enhanced to provide a customizable format and selection options have been
enhanced
Return ->
Application
List of Goods receipt with out excise invoice

Description
For a given list of material documents or with open selection it is possible to list all the goods receipt where there has
been no excise invoice
Return ->
Application
Page 40 of 64
Excise invoice on MRP pricing

Description
Excise invoice can be created for purchase order with MRP price. the purchase order will just have a single MRP
price and a zero tax code attached to it. Creation of excise invoice mark the 'MRP indicator'. GR will reduce the
excise value from the stock value. during invoice verification adjust the material price to less of excise duty and post
the vendor invoice with calculate tax on.
Return ->
Application
Creation of Part1 during inter plant receipts and receipt into blocked
stock
Description
Part1 gets created during inter plant sock transfer receipts and also during receipts into blocked stock. This is
achieved by a customization setting at the excise group level
Return ->
Application
Release notes - Sub-contracting
Changes to Subcontracting Transaction

The earlier subcontracting challan transaction(J1IF) has been replaced by the following:
Subcontracting Challans are created using: Create - J1IF01
Subcontracting Challans can be changed and if required deleted using: Change & Delete - J1IF11
Subcontracting Challans are displayed using: Display - J1IF12
Quantity Reconciliation transaction to reconcile the quantities of input materials consumed against those issued
through the challans, when the processed materials are received from the subcontractor, is run using the transaction:
J1IFQ
In the Complete transaction, new functionality to reverse and avail recredit has been introduced. The non-receipt
transaction existing earlier (57NR) has been replaced by the reversal functionality. Subcontracting Challans can be
completed or reversed or recredited using: Complete/ Reversal / Recredit - J1IF13
A listing program that allows users to determine the challans for the selection options he chooses is provided using:
Challan Listing - J1IFR
Return ->
Application
Create, Change & Display and Complete transactions have more fields and a new screen for text objects.
The usagability of the screens have been enhanced and thus have been given a relook.
Return ->
Application
Print Immediately option at the time of creation of the Challan

Subcontracting Challans can be printed immediately during creation. An indicator to print the challan (Print
Immediately) when it is created has been provided. Thus there is no separate transaction for printing.
Return ->
Application
Page 41 of 64
A single transfer posting can be split into Multiple Challans

More than one challan can be created from a single transfer posting. This means there is no restriction on the number
of items a transfer posting document can have. Earlier there was a restriction on the number of line items a challan
could have and this restriction translated itself directly to the transfer posting document as only one challan could be
created with reference to a transfer posting document.
Return ->
Application
Complete transaction to have additional functionality for Reversal and

Recredit.
For the Input materials / Capital goods lying with the subcontractor for more than 180 days, duty credited has to be
reversed. This reversal is posted in the completion transaction. Further receipt after reversal, allows the duty reversed
to be recredited. This recredit is posted in this transaction itself. The recredit is to the extent of goods (input
materials / capital goods) that have been returned by the subcontractor.
Return ->
Application
Quantity Reconciliation for Subcontracting Challans
When the processed materials are received from the subcontractor, the receipt of the processed materials and hence
the consumption of input materials have to be reconciled against the dispatches of the input materials ( which are
through the Challans). These assignments of the goods receipt document and other receipt documents to the
Challans is done using the new transaction J1IFQ
Return ->
Application
Multiple Challans captured against a single Goods Receipt document

More than one challan can be captured for a goods receipt document in a new dialog screen. These challans will
have to be allocated in the new transaction J1IFQ.
Return ->
Application
A new Challan listing program with many features

Along with the Annexure IV option this new challan listing program has many selection options such as
the challans due for Reversal for a given period or on a given day
the challans that are due for Recredit
the challans whose reference material documents have been cancelled or deleted
a list of challans with a given status or for a list of statuses

and many other features.
Return ->
Application
Components can be sent to the subcontractor under full duty

payment
The 57F2/F3 process wherein the components are sent out to the subcontractor on full duty payment is supported.
The components are issued to the subcontractor and duty is paid. The processed goods are returned and the goods
receipt document is created. To this goods receipt document the excise invoice that accompanies the processed
goods is referenced by capturing the excise invoice number in the pop-up. Credit can be availed for the excise duty of
the processed goods.
Page 42 of 64
Return ->
Application
CIN customizing for the subcontracting procedure

The customizing for the subcontracting procedure has been changed. Subcontracting Attributes and Movement Type
Groups for Subcontracting have been created.
Some of the standard customizations required have been mentioned in the Subcontracting Node.
Return ->
Application
Printing of excise invoice for other movements

Description
Allows users to print excise invoice for other movements using their own layout set by specifying an output type
during the time of printing
Std. SD Customizing Settings:
SD --> Basic functions --> Output --> Output determination -->
Output proposal using the condition technique -->
Maintain output determination for billing documents -->
Maintain Output Types
SD --> Basic functions --> Output --> Output determination -->
Process output and forms --> Assign forms and programs --> Allocate to
billing documents
Return ->
Application
Pre-printed number during printing of excise invoice for other

movements
Description
During printing of excise invoice for other movements, a popup is provided to capture the pre-printed excise invoice
number
Return ->
Application
Enhancements to excise invoice for other movements

Description
An additional field to capture unit assessable value which will be used to compute the base value.
Default of the excise invoice amount in J1IV utilization screen.
Cancellation of nil duty excise invoice created through J1IS.
Checks if any other excise document against a material document is created before creation of excise invoice
through transaction J1IS.
Defaulting of master data in the details screen.
Automatic adjustment of duty amounts based on changes in quantity
Page 43 of 64
Number range warning depending on the warning percentage maintained in customizating specifications for a
number range object.
Automatic Creation of excise invoice and Posting after creation of the internal document based on customizing.
SOFT/HARD_REQUIREMENTS&
CIN IMG --> Global settings --> Excise group.
Maintain 'X' in the field 'Automatic posting fir J1IS'
Return ->
Application
Excise invoice split for other movements

Description
Allows excise invoices to be split based on the number of items maintained in customizing thus ensuring number of
items printed in an excise invoice does not exceed the permissable limit.
CIN IMG --> Global settings --> Excise Registration IDs.
Maintain number of items in excise invoice
Return ->
Application
Document flow for an outgoing excise invoice

Description
Displays all the preceding documents of an outgoing excise invoice. Also displays cancelled invoices, if any.
Return ->
Application
Utilization due list

Description
List displaying all billing documents due for utilization. Also shows account balances, total duty amount needed to
utilize the displayed billing documents and deficit, if any.
Return ->
Application
Batch utilization
Description
Allows utilization of billing documents in batches.
Additional fields in selection screen like billing date, SD document category, Billing document category to impove
performance.
Return ->
Application
Page 44 of 64
Cancellation of outgoing excise invoice

Description
Allows reversal of excise invoice without the need to mark the excise invoice for cancellation
Return ->
Application
Enhancements to Register update for RG23 and RG1

Description
Validations to avoid downloading non-modvatable items.
Control built to ensure that only corresponding items are downloaded for respective registers.
Option to download RG1 entries either for posting or document entry dates.
Option to extract RG23 and RG1 register using document header details.
Return ->
Application
Fortnightly payment of duty

Description
This functionality can be used to calculate duty accumulated for each fortnight and is used to subsequently make the
payments. Based on the criteria entered, a screen is displayed showing the Balances available, Duty payable
amounts and the utlization screen.
Option is also available to do utilization based on an excise invoice or a range of excise invoices
CIN IMG --> Sales and Distribution --> Utilization determination
Maintain Percentage rates for excise group and excise components
Return ->
Application
Automatic determination of excise and series group

Description
During creation of outgoing excise invoice, excise and series group can be automatically determined by maintaining
appropriate customization
CIN IMG --> Sales and Distribution --> Excise / Series group determination
Return ->
Application
Page 45 of 64
Excise invoice creation in background

Description
This functionality facilitates the creation of the outgoing excise
invoice in background at the time of creation of billing document.
After the creation of excise invoice system prompts for printing .
Mark 'X' in the field for 'Create excise invoice in background'.
CIN IMG --> Sales and Distribution --> Excise group - Series group determination
For export sales, maintain whether under bond, no bond, deemed exports
Optionally, Maintain sub-transaction type
Return ->
Application
Excise invoice creation in background

Description
This functionality facilitates the creation of the outgoing excise
invoice in background at the time of creation of billing document.
After the creation of excise invoice system prompts for printing .
Mark 'X' in the field for 'Create excise invoice in background'.
CIN IMG --> Sales and Distribution --> Excise group - Series group determination
For export sales, maintain whether under bond, no bond, deemed exports
Optionally, Maintain sub-transaction type
Return ->
Application
Enhancements to Register Printing

Description
Prints the consolidated debit entry generated during fortnightly payment for the RG23A Part2, RG23C Part2 and PLA
registers.
Goods receipt and vendor details are printed for items without material numbers i.e. non-coded items.
Return ->
Application
Automatic folio generation at depot
Separate exchange rate for Export invoices
Excise concession forms based on customer and material tax classification
Sales tax concessions based on customer and material tax classification
Page 46 of 64
Excise invoice selection based on GR date in the depot

Classic TDS
Business Area wise Posting

Description
Now it is possible to Post TDS documents Per business Area or a range
of business Areas Provided the original document is posted with Business Area. The TDS line item is also posted with
business
Area as inherited from parent document
None
Installation Information
None
Effects on System Administration

None
None
None
Dependent Functions
None
Planning
None
Further Notes
None
Return ->
Application
Logistics Invoice Verification is Supported

Description
Classical TDS programs now support Logistics Invoice Verification also. The invoices which are posted through LIV
are considered by TDS post program for deduction of tax .
Extended Witholding tax functionality should not be active for the company code for which this is required
Return ->
Application
Page 47 of 64
Posting to Special periods:

Description
Now posting to special Periods is possible, provided normal posting
periods are closed. The special posting period is chosen from
selection screen
Dependent Functions
none
Return ->
Application
Copy Invoice Reference:

Description
If the invoice is filled with a reference document number or any text,
the same is copied onto the TDS document also.
Return ->
Application
Profit center Posting:

Description
If the reference invoice holds profit center, the TDS document is also p
is also posted with that Profit center.
Return ->
Application
Page 48 of 64
One time vendors:

Now one time vendor certificates can be separately printed
under program J_1ITDS6.
The main certificate printing program will not print certificate for one
time vendors.
Bank Key:Now bank key is added to selection screen so that the bank
details are picked from the key and certificates are printed using thi
this key.
Place of Printing:
Place of printing is added to selection screen.
Vendor wise Printing:
It is possible to print vendor wise certificates selectively.
User Exits:
New user exits have been provided to get TAN/PAN numbers for
Vendors
and for one time vendors.
Return ->
Application
Annual Return Programs

Description
New Annual return programs are provided to print returns
under Sections 194C,D,I,J
Return ->
Application
Copy House Bank to TDS documents

Description
A new program J_1IHBKD (Transaction J1IHBK) has been provided to copy House Bank
as in Vendor Invoices into Vendor line created during
TDS posting.
Return ->
Application
Page 49 of 64
Tax Adjustment
Description
When Tax Lines need to be corrected after challans have been
paid or certificates issued, this functionality can be used.
It provides for amount correction as well as Tax code
correction.
Return ->
Application
Tax Adjustment on DP Clearing

Description
At the time of clearing of a down payment against an Invoice, the proprotional tax
deducted on the invoice is refunded to vendor provided the sections on tax deducted during Down payment and
Invoice are the same and the business place on both documents are the same.
Return ->
Application
Payment Due Dates

Description
Payment Due Dates are determined at the time of posting
FI documents with withholding tax lines. The due dates
can be customized for Recipient type and section.
In addition, Calender IDs can be attached to
Business Place to pick the next or previous day in case
the due date happens to be a holiday.
Return ->
Application
Challan Update:
Description
Challan Update Program uses Open item clearing funtions
of R/3 to clear the Tax lines and generate Internal challan
numbers. The Challan numbers received from Bank can then
be updated separately.
It is possible to reverse the tax payment document and
repost.
Return ->
Application
Tax on Services
Description
It is possible to post tax on services which were
booked earlier for which no invoices have been received.
Page 50 of 64
The posting happens to Tax Provisions account. The provisions

are reversed at the time of Invoice verification
Return ->
Application
Customer Tax Clearing.

Description
When certificates are received from Customers, The open tax lines being withholding tax deducted by customers, can
be cleared to an account called "Customer Certificate Received Account' .The balance in this account can be used to
adjust advance tax liability of the company .
Return ->
Application
Certificate Printing.
Description
Following new features have been provided.
1. Customizable layout sets have been provided per section and
business place.
2. Both one time vendors and normal vendor certificates can
be printed by the same program.
3. Number range objects can be maintained per business place
and section
Return ->
Application
Release notes Others
Business addins in CIN

Description
All changes required for CIN in R3 functionality have been achieved through business addins which get activated only
if the country is 'IN'
Return ->
Application
CIN 40A Release notes
Release notes Procurement
Procurement Transaction to Capture and Post Incoming Excise Invoice has been replaced.
Description
The earlier transactions (J1IA, J1IB, J1IW, J1IX, J1IREJECTION) have been replaced by a single enjoy transaction
(J1IEX).
Return ->
Application
New Transactions based on User roles for incoming excise invoice.
Page 51 of 64
Description
Two transactions J1IEX_C and J1IEX_P have been created to suit business process workflow for customers.
Transaction J1IEX_C, would enable a specific set of users to capture and display the excise invoice J1IEX_P allow
posting, change, cancel and display of the excise invoice.
Return ->
Application
Capture an Excise Invoice with reference to Multiple POs for the same Vendor
Description
A single Excise Invoice can now be captured, in case of a delivery for multiple Purchase Orders for the same Vendor.
Return ->
Application
Excise invoice capture and post CENVAT in a single step
Description
If the customers desire to avail the credit of excise duty at the time they captures the vendor excise invoice in their
system, they time they captures the vendor excise invoice in their system, they should process Goods receipt first
and then capture and post excise invoice.
Return ->
Application
Open Schedule Quantity is defaulted in Excise Capture for Scheduling Agreement
Return ->
Application
Accounting Document simulation for CENVAT posting
Description
An option to simulate the CENVAT postings to view the accounting entries is a feature provided when the credit is
available for posting to Part II.
Return ->
Application
Rejection codes for Excise Invoices
Description
A rejection code can prevent the posting of CENVAT if the necessary customization for the rejection code has been
maintained. The postings in this case are to ONHOLD Accounts. This rejection code could be deleted from the excise
invoice and then posting can be made into the RG23 registers. The rejection codes could be defined for mutilated
excise invoices for example.
Return ->
Application
A single screen transaction for all the excise related entries
Description
View the entries into the Part I register, Part II register and the accounting documents (CENVAT postings, ONHOLD
postings), in this single transaction.
Return ->
Application
Page 52 of 64
Stock Transfer Order functionality through MM route addressed
Description
For Stock transport orders where the materials are moved from one plant to another through the MM route (transfer
posting to stock in transit), the excise invoice can be captured at the receiving plant, for the quantities of stock in
transit, by referring to the excise invoice invoice created at the supplying/issuing plant.
Return ->
Application
Excise Invoice for Multiple Import Purchase Orders can be captured with reference to a single Customs Invoice (Bill
of Entry).
Description
The Quanity and CVD amount as captured in Customs Invoice is defaulted when the Excise Invoice is captured.
Return ->
Application
Customs Invoice for the Imports PO can be captured using Logistics Invoice Verification and Conventional Invoice
Verification
Return ->
Application
Material Type is at the line item level
Description
The Material type for the excise invoice is at the line item level and can be changed for each item. Combination of
Raw Material/Capital goods and non-Cenvatable is allowed for a single Excise Invoice.
Return ->
Application
Excise Invoice capture without PO
Description
Excise Invoice can be captured without a reference to a PO in the new incoming excise invoice transaction (J1IEX)
Return ->
Application
Excise Invoice without PO - Capture and Post in a single step
Description
The excise invoice captured without a PO's reference can be posted while capturing
Return ->
Application
Recalculation of Duty and Excise defaults restore feature available
Description
Excise duty can be recalculated at the time of capture based on the data, Excise base and Rates. And if duty values
are incorrect, they can be restored to whatever values defaulted initially.
Return ->
Application
Page 53 of 64
Split of Non-deductible Taxes available during excise invoice capture
Description
Excise invoice BED, AED and SED inventory components and Sales Tax is available and changes to Excise base or
credit available is also reflected onto non-deductible Taxes.
Return ->
Application
To ease user entry, Error or Warning Messages are displayed at the time of saving.
Description
Both warning and error messages are issued when Check button is pressed but only error messages are issued if the
document is saved.
Return ->
Application
Reversal of excise duty
Description
Reversal of excise duty allowed only for Material Document Cancellation and not for vendor returns
Return ->
Application
MIGO solution available as a note 0408158 (featuring all functionalities as in MB01)
Description
All the correction to MIGO will be delivered through a note, which needs to be applied after every Support Package
application.
Return ->
Application
New Popup for referencing Excise Invoice and Subcontracting challans at GR(MIGO & MB01)
Description
The pop-up consists of two tab strips- one for Incoming Excise Invoice and the other for Subcontracting Challans. If
the Purchase Order has item Category 'L', both the tab-strip wil be displayed. Only valid Excise Invoice or
Subcontracting Challans can be entered before posting GR.
Return ->
Application
Excise Invoice Defaults in Excise Pop-up at GR
Description
The pop-up will default: the register relevant to the material and also the excise group based on the plant.
Return ->
Application
Split Accounting Lines for CENVAT Posting
Description
Postings of accounting entries is now for every line item of the excise invoice. The Posting has been moved from the
header level to the line item level. Each line item of the posting is attached to a profit center
Page 54 of 64
Return ->
Application
Authorization for Incoming Excise Invoice has been extended
Description
Authorization fields for Excise Invoice are Actvity, Company Code, Plant, Excise Group, Transaction Type, Sub
Transaction Type
Return ->
Application
Authorization available for Part1 Entry at GR
Description
Authorization fields for Excise Invoice are Actvity, Company Code, Plant and Excise Group
Return ->
Application
Authorization available for Register Update Transaction
Description
Authorization fields for Excise Invoice are Actvity, Company Code, Plant and Excise Group
Return ->
Application
User Exit available for Incoming Excise Invoice Transaction for Defaulting values
Return ->
Application
User Exit available for Incoming Excise Invoice Transaction before database updation
Return ->
Application
User Exit available for Register Update for validations on fetched records based on selection criteria
Description
The customer can use this user exit for carry out further validations on the fetched records based on the inputs on the
selection screen. For eg. the user can screen records if they are not of a particular movement type. Only the records
that are passed by the user exit back to the program will be displayed on the output list.
Return ->
Application
User Exit available for Register Update for updation of RGSUM register.
Description
This user exit can be used for eg. if the user needs to change and update the material form of the line item being
updated.
Return ->
Application
User exit available for Excise Invoice Create for Other Movements to default the excise details
Return ->
Application
Page 55 of 64
Register Update separately handled for receipts and issues based on classification code
Description
Based on the selected Register type and the type of material document the receipts and issues are handled for the
following classification codes:
Register : RG23A PARTI and RG23C PARTI
Classification codes for Issues: IIM, IPD, IWD.
Classification codes for Receipts : ROP.
Register : RG1
Classification codes for Issues : IDH, IDE, IWE, IWT, IWO.
Classification codes for Receipts : ROP, RMA
Return ->
Application
Ship-from Vendor can be defaulted and captured in Excise Invoice Create for Other Movements
Description
The default Ship-from will be from the selected excise invoice
Return ->
Application
Removal Time can be captured Excise Invoice for Other Movements
Return ->
Application
Field selection of Incoming Excise Invoice
Description
Customers can decide the screen attributes of the fields in this setting
Return ->
Application
Transaction code customizing for Incoming Excise Invoices
Description
Customers can define their own transaction codes. For each transaction code the processing mode and the reference
document as required can be linked.
Return ->
Application
Excise Group setting for Part I indicator for Blocked Stock, Stock transfer order and Consumption stock
Description
This indicator would assist in creating an entry in the Part I register for the stock types mentioned.
Return ->
Application
Multiple Goods Receipts and Multiple / Single credit setting is available at the excise group level.
Return ->
Application
Rejection Code Master setting for Posting on hold is available
Return ->
Application
Page 56 of 64
For Stock Transport Orders, the plant has to be maintained as a Vendor as well as a Customer for Excise Invoice
Capture via GRPO route
Return ->
Application
CENVAT payment can be done immediately at the time of removal

optionally.
Description
It is now possible to pay the CENVAT immediately outof CNVAT credit or PLA based on customization.
The decision of whether the payment is to be made Fort nightly or immediately is made based on the series group.
If the payment is Fort nightly then the accounts are picked from the Account assignment for ' Outgoing Excise
invoices transaction' and the entries are created in the Despatch register. The Fort nightly payment program can be
used to pay the CENVAT amount. Simultaneously you can have another Series group which needs Immediate
payment and in this case the accounts are picked up from the 'Incoimg credit' and PLA accounts.
You need to mark the Immediate credit indicator in Series Group details
Return ->
Application
Item level accounting postings for Excise invoice

Description
The excise invoice accounting postings are done at line item level. This enables the expense lines to be posted with
complete details of the line items. This allows the excise paid open items to be cleared automatically.
Return ->
Application
Performance improvements has been brought into Excise invoice

creation with improved processing.
Return ->
Application
Autorization for Excise invoice creation can be controlled at an Excise

group as well as Series group level.
Return ->
Application
Excise invoices can be created based on Intercompany billing

documents
Description
When there are exceptional scenarios where the Sales order is raised by one company and the despatch happens
from a plant which is attached to another company then you need to use this functionality. In this case there will be a
Inter company billing document across the two companies. This billing document is the basis for creation of Excise
invoices.
Page 57 of 64
Return ->
Application
Posting of CENVAT to profitability segments

Description
In case CO-PA is active in your system; during posting of Excise invoice utilization the Profitability segments are
picked up from the Billing document and the accounting document creates a CO-PA document in the back ground.
Return ->
Application
Business area wise posting of Fort nightly payment

Description
It is possible to specify a Business area while posting of Fort nightly CENVAT credit
Return ->
Application
Text entry during Fort nightly payment

Description
You can enter some free form text while doing Fort nightly payment using defined Text Id's. For maintaining the
different text'x please use the object J1IU.
Return ->
Application
Printing of pending invoices during Fort nightly payment

Description
You can print a list of all Excise invoices which are pending for Fort nightly payment until todays date or in a given
period.
Return -> Application
Printing of Annexure of excise invoices for Fort nightly payment

Description
You can display and print all the Excise invoices that are included for the Fort nightly payment
Enhancements to Automatic creation of Excise invoice

Description
Automatic creation of Excise invoice during Billing has been enhanced
Page 58 of 64
Depot receipts for Returnable packaging

Description
It is possible to create a delivery document with returnable packaging and ignore the selection of RG23D for these
materials. since the packing is going to come back there is no RG23D entry for the same.
Default of Purchase order details on to depot receipts

Description
While doing receipts in depot from third party purchase orders you will be having a direct PO on the supplier and the
excise invoice will not exist in the system. The invoice details will be manually entered. Now the chapter-id, Excise
base and the duty amounts willbe defaulted onto the Excise capture details screen.
Return ->
Application
Entry of Cess during capture of Excise invoice in depot

Description
While doing Excise invoice capture at depot you can enter the Cess amount paid by the supplier or sending plant.
CVD indicator can be maintained for Depot receipt

Description
If the receipt into the Depot is through imports then CVD indicator can be maintained against the Depot receipt entry
so that future tracking is easier.
Suppplementary Excise invoice at depot

Description
Some times after transferring the goods to depot, price escalation can happen with retrospective effect. In these
scenarios it is possible that you need to pay the differential excise amount at the factory using A-certificate. Once it is
paid the additinal entry details needs to be reflected on to the RG23D register. A new entry with the same folio
number but a new serial number will be generated. The additinal entries can be displayed or changed until the
additional amount is picked up for payment during removal. you can have any number of additional certificate entries
for a given RG23D folio. Once the full quantity with in the folio is used up then you cannot enter any further additional
certificate entries.
Folio number generation should be active for the excise group.
Supplementary excise invoice selection during depot selection

Description
If additional duty has been paid at the factory using A-certifcates then they need to be charged back to the customer
during sales. For this while doing excise invoice selection for removals , system displays all A-certificate entries which
Page 59 of 64
have been generated for the folio. User can pick up one or more additional entries and post. the additional duty of the
A-certificate will get added to the excise charged from the customer when the Billing document is prepared.
You can only select one more Additional entries completely. Partial selection from an A-certificate is not allowed. The
a-certificate entries chosen will come as additional lines in RG23D
Foliow number generation should be active
Depot stock display

Description
You can display the stock in RG23D register using this functionality. The stock can be displayed for a plant, material
or excise group
Asset Accounting - Recommended Customization settings for Income

Tax Depreciation in India
Description
In India, depreciation on assets for the purpose of computation of net income as per the Income Tax (IT) Act 1961 is
calculated over a block of assets instead of individual assets as allowed under the Companies Act 1956. Asset
acquisitions and retirements are managed over the block level. The IT Act prescribes certain rates of depreciation to
be used under the Written Down Value (WDV) method over these asset blocks to compute depreciation.
The following are the customization settings that may be followed in the R/3 system in order to manage your assets in
the income tax depreciation area.
Customization Settings relevant to Income Tax Act

Description
In India, depreciation on assets for the purpose of computation of net income as per the Income Tax (IT) Act 1961 is
calculated over a block of assets instead of individual assets as allowed under the Companies Act 1956. Asset
acquisitions and retirements are managed over the block level. The IT Act prescribes certain rates of depreciation to
be used under the Written Down Value (WDV) method over these asset blocks to compute depreciation.
The following are the customization settings that may be followed in the R/3 system in order to manage your assets in
the income tax depreciation area.
Customization settings
1. Copy the standard chart of depreciation 0IN as provided by SAP and create your own chart of depreciation.
2. Use the depreciation area 15 for the purpose of management of assets under the IT Act. Make it statistical in
nature. (Reference Transaction Code: OADB). Do not check the box negative net book value.
3. Specify that the Income Tax depreciation area takes over the APC from the book but not make it identical
(Reference Transaction Code: OABC).
4. Create an asset class for the purpose of income tax blocks. This asset class will be used to create only group
assets. (Reference Transaction Code: OAOA)
5. Specify that the depreciation area for income tax can be managed only for group assets. (Reference Transaction
Code:
OAYM). This would mean that depreciation for this depreciation area would be computed only at group asset level.
6. Specify that the asset class defined in (b) above will be used for creating group assets only. (Reference
Transaction Code: OAAX)
7. Two period control methods (IT and NL) have been defined in the system for determination of start or the end of
depreciation calculation at the time of a fixed asset acquisition or retirement. You may use these period control
methods while creating the depreciation keys for the purpose of IT depreciation.
Page 60 of 64
Calender assignments have been made for the above mentioned period control methods in order to reflect valuation
requirements as per the Income Tax Act (Transaction Code: OAVH). You may create your own period control methods
depending on the fiscal year variant you use. The period control methods supplied are based on the fiscal year
variant V3.
8. Depreciation Keys:
The following depreciation keys have been created in the system. They correspond to the income tax block that are
prescribed under Indian tax laws. They are as below:
Depreciation Keys :
1. IN1 - Tax Depreciation - 5% - India
The features of the keys supplied are as below:
Depreciation type: ordinary depreciation
Class: declining balance depreciation
Depreciation method: stated percentage
Base value: remaining book value with proportional value adjustments
Percentage rate: will correspond to the depreciation rate of an IT block
Period controls:
Acquisition: IT
Acquisition in following year: IT
Retirement: NL
Transfer: NL
9. For the asset classes corresponding to the IT blocks, default the corresponding depreciation key for the
depreciation area created for income tax. (Reference Transaction Code: OAYZ). Use an infinite useful life e.g. 999.
10. Create a screen layout rule for depreciation areas (Reference Transaction Code : AO21) in which the field group
asset is mandatory.
11. While maintaining the other asset classes for the income tax depreciation area, use the screen layout rule as in
(j). (Reference Transaction Code: OAYZ).
12. Create group assets using the asset class defined in (b), where each group asset master record corresponds to
an IT block. You will be able to view only the income tax depreciation area for the group assets.
13. Maintain the following posting variants for the transaction types normally used for asset retirements: 200, 210,
250, 260 (Reference Transaction Code: OAYS) in the income tax depreciation area:
Treatment of retirement: balance revenue
14. Create individual asset master records, where for the income tax depreciation area, you have to enter a group
asset. Choose the group asset depending to which IT block your asset belongs.
Note :
1. For individual assets, the system will not show any depreciation in the income tax depreciation area.
2. For the group assets, the system will not display the book depreciation area.
3. At the time of takeover of old asset data, create the group assets first and specify the opening gross value and
accumulated depreciation for the income tax depreciation area. Then while creating the individual assets, you have to
specify the opening gross value and accumulated depreciation for the book depreciation area only.
Classic TDS
Change in Challan Update (J_1ICHLN) program

Description
Challan Update program ( Tcode J1I8) lists the original (invoice or downpayment document references) only. It does
not list the document numbers of the TDS documents created through the TDS Posting program (J_1ITDS2).
With the changes, the TDS document for the original document also gets listed on the Challan list, in order to make it
possible for the user to select, for payment, documents for which he has carried out a Challan Update.
Page 61 of 64
Reversal of TDS: Change in accounting postings

Description
TDS is posted on invoices using the program J_1ITDS2 which generates a secondary tax document that debits the
vendor account. When the invoice is reversed (using transaction FB08/MR08), the withholding tax is reversed in a
subsequent run of the TDs program. The reversal document was created as a new document without any link to the
original document and as a result manual clearing of the Tax account had to be done.
With the changes, the reversal document is created using the standard reversal transaction (FB08) and this
document clears the tax account also .
User Exits in the certificate printing program

Description
One user exit has been provided to use a layout other than the standard layout delivered along with CIN for TDS
certificate printing.
The second user exit has been provided to determine the certificate number if you have organised your TAN numbers
differently from the suggested configuration and would like to have discrete numbers within the number range object
for the TAN offices
Further Notes
See OSS Note 382113
User Exit for One time Vendor's PAN in Certificates

Description
PAN number of One time vendors is not maintained in master records. It is to be stored in the accounting document.
An user exit is provided in certificate print program which can return PAN number from accounting document for the
one time vendor.
Further Notes
See OSS Note 335911
Business area posting for TDS provisions

Description
Business area posting during TDS Provisions Posting for India - EWT. The program for TDS provisions posting did
not allow postings to be madefor business area. The same program has been enhanced to post the Business area as
per the user input.
Further Notes
The following should be ensured while posting provisions: If the purchase order has items corresponding to more
than one business area, the user has to post to these separately while posting provisions, as a single purchase order
can be posted to only once during the provisions posting run.
Migration from Classic to Extended withholding tax
Page 62 of 64
Health check for migration to Extended Withholding Tax from Classic

Description
The health check program should be executed before migration of data to Extended Withholding Tax , it check
whether the relevent customizing are complete.
Relevent Extended Withholding Tax customizing should be completed.
Annual returns for Extended Withholding Tax

Description
Annual returns for section 194C , 194D, 194I, 194J under sec 206 of Income Tax Act 1961 can be obtained from
program J_1IEWT_ANN_RET with transaction code J1INAR.
Cash Journal postings supported
Description
CIN 40A functionality supports Cash journal postings made using the standard functionality. Business Place inforation
can be captured as per user input
Withholding tax on Interest payments to Customers

Description
If the interest is to be paid to the customer, withholding tax under section 195 A of Indian Income Tax Act 1961 needs
to deducted at time of making the interest payment. There is a standard program to post interest on customer
balances. Business place if captured in this document is transferred to the withholding tax lines .
Dependent Functions
Interest calculation program for customers (RFDIZ00) is used to post interest on customer account balances.
Further Notes
In the master record of the customer, the withholding tax information needs to be maintained. You would need to
maintain the first two characters of the W/Tax Number field as the 'Recipient Type' information for the customer.
Ensure that the first 2 characters of the field W/Tax Number in the customer master is the same as the Recipient type
maintained in the customizing settings
Financial Accounting -> Financial Accounting Global Settings -> Withholding Tax -> Extended Withholding Tax ->
Basic Settings -> Check Recipient Types.
Challan update for withholding tax deducted on interest payments to

customers
Description
to deducted at time of making the interest payment. If the tax is deducted, it needs to be remitted with the
government.
Page 63 of 64
There is a program that does the GL account clearing for the withholding tax accounts so that payment can be made.
This program does the GL account clearing for all withholding tax deductions from payments made to customer
accounts. The functionality is similar to the GL account clearing program for vendor accounts .
Dependent Functions
Certificate Printing for Withholding tax on Customers

Description
to deducted at time of making the interest payment.
There is a separate program to print the certificate to be issued to theCustomers for such tax deducted and remitted
to the govenrment .
Dependent Functions
Challan update for withholding tax deducted on customers is to be done through the program
'J_1I_CHALLAN_UPDATE_CUST' .
Bank challan update is to be carried for the same using the program 'J_1IEWT_BANK_UPDATE' .
MIS Report for Withholding Tax - India.

Description
The purpose of this report is to:
1. Provide the user with information relating to the transactions carried out with respect to Withholding Tax (TDS).
2. Display the details of the transactions carried out and the ones that are pending.
3. Select the pending transactions and run them based on the selection.
This report can be run only if the extended withholding tax functionality is active for the company code.
No customizing changes are required to run this transaction.
Further Notes
The user may decide to run the relevant withholding tax transactions based on this report. He can select the
documents for which the transactions need to be carried out, and run them from this report. The transactions once
carried out, its relevant details are updated. For further information relating to running the report and all its features,
the application documentation may be referred to.
Page 64 of 64

CIN Customization Documentation: Caution: Do Not Run The Country Version Installation Program in A Live System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CIN Customization Documentation: Caution: Do Not Run The Country Version Installation Program in A Live System

Uploaded by

Copyright:

Available Formats

http://thefico.weebly.

CIN Customization Documentation

India Localization Menu

Change Country-Specific Settings

Customizing: Country Version

the chart of accounts

tax calculation schemata

CIN Customization Documentation

Creating Multiple Country-Specific Company Codes

Activate Country Version India for Accounting Interface

Activate Country Version India for Specific Fiscal Years

Comp. (Component): ZIND

CIN Customization Documentation

Activate Business Transaction Events

Event 00001110, which must be assigned to function module J_1ITDS_SAVE_CHANGES with

Event 00001030, which must be assigned to function module J_1IEWT_CHALLAN_UPDATE with

Event 00001050, which must be assigned to function module J_1ITDS_TABLE_UPDATE_LIV with

CIN Customization Documentation

You maintain all customization for Financial postings at this level.

You can maintain separate rounding indicator for

You can maintain separate Exchange rate types for

Excise Registration IDs

The maximum number of items to be printed on each excise invoice

Whether you are allowed partial CENVAT credits

Specify whether it is a manufacturing site or a depot.

Assign it an excise registration ID.

CIN Customization Documentation

Maintain Series Groups

Define excise series groups based on type of outgoing document

Assign series group to excise registration ID

CIN Customization Documentation

Make Sure That Processing Keys Are Deductible

VS1 (basic excise duty)

VS2 (additional excise duty)

VS3 (special excise duty)

VS5 (sales tax setoff)

Define G/L Accounts for Taxes

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)

Maintain Transaction Accounts

CIN Customization Documentation

Maintain Transaction Accounts

Maintain Minimum Balances for Excise Accounts

CIN Customization Documentation

Define Processing Modes Per Transaction

Tcode: The transaction code that you have just created.

Active: Select this indicator to activate the setting.

Define Reference Documents Per Transaction

Define Rejection Codes

CIN Customization Documentation

Specify Which Movement Types Involve Excise Invoices

CIN Customization Documentation

Sales and Distribution

Sales and Distribution Customization

CIN Customization Documentation

(i) When excise and commercial invoice are the same

Assign excise invoice billing type to delivery type