0% found this document useful (0 votes)
70 views2 pages

Set Upfor India Localization

This document outlines 10 steps for setting up India localization in Oracle Applications. It details configuring item attributes, additional organization information like tax calendars and accounts, defining subinventory locations, suppliers for tax deduction at source, tax codes, tax categories, item category lists, additional supplier/customer information including tax deduction at source, bond registers, and excise configuration for trading organizations.

Uploaded by

harish1002
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
70 views2 pages

Set Upfor India Localization

This document outlines 10 steps for setting up India localization in Oracle Applications. It details configuring item attributes, additional organization information like tax calendars and accounts, defining subinventory locations, suppliers for tax deduction at source, tax codes, tax categories, item category lists, additional supplier/customer information including tax deduction at source, bond registers, and excise configuration for trading organizations.

Uploaded by

harish1002
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

STEPS FOR SETTING UP INDIA LOCALIZATION

1) Item Attribute: While defining the item, in the descriptive flexfield,


the following information is to be given.
Excise Flag:
Yes
MODVAT Flag:
Yes
Item Class:
(Any Value)
Trading Flag:
Yes
2) Additional Organization information: In the Additional
Organization information form, the relevant information for the
Inventory Organization has to be entered. First, the information is to
be defined and saved without specifying the location of the
organization. Then we specify the location of the organization and
the same information defaults there. Unless we define the additional
information for the location, the localization does not work. If we
want to allow the users to change tax amounts while recording
receipts, the 'Allow Tax Change on Receipt' has to be checked. If we
want to allow -ve balances in PLA, the -ve balance in PLA box is to
be checked. We have to define tax calendar. In a tax calendar, only
one year at a time can be active. So before opening the next year,
we have to be sure that all the entries for the earlier year have been
passed. The tax calendar is applicable for excise and sales tax. For
TDS, we define the year in Payables Module.
(Set
up\Others\TDS year info) The information regarding excise accounts
and invoice generation is to be given.
3) Subinventory Location: Each Inventory Organization has
subinventories. An inventory organization can have multiple
locations. The location for which additional organization information
is defined as per step 2 above needs to be attached to the
subinventory in the subinventory locations form. More than 1
subinventories can be attached to the same location. In the same
form, we have to specify whether the subinventory is a bonded
warehouse and a trading organization. For trading organizations,
register under rule RG 23 D is required to be maintained which
records quantitative and MODVAT details.
4) Supplier for TDS: We have to define the supplier for TDS. The
supplier has to be of the type TDS Authority. The TDS invoices will
be generated in the name of this supplier after it is attached to the
Tax Code.
5) Define Tax code: The tax codes for ED, Sales Tax, TDS, freight etc.
are to be defined in the Tax definition form. For TDS type of tax, the
supplier defined as TDS Authority is to be attached to the Tax Code.
The GL Account has to be specified for the Tax Code. For purchase
type of Tax Codes, this account is hit with the MODVAT/Set of
amounts. For sale type of Tax Codes, this account is hit with the tax

collected on sales. For TDS type of Tax Codes, this account appears
as the distribution for the invoices & credit memos generated. The
MODVAT/Set Of % for the tax is to be specified. If the % is not fixed,
the ad-hoc box is to be checked.
6) Define Tax Categories: The tax categories are to be defined in
this form. Optionally, the item class can also be specified. The
precedence of taxes to be charged is specified. The value 0
indicates basic. For ad-hoc type of tax, precedence is not to be
specified.
7) Define Item Categories lists: The items are to be attached to the
tax categories in the Item category List form. If for an item tax
category is not attached, the tax category attached to the item
class to which the item belongs will default for the item.
8) Additional Supplier/Customer Information: In this form, the
item category list is to be attached to the supplier/customer. In the
TDS details region, the TDS information is to be given. The TDS is
attached to the supplier at the header level(without specifying site).
All the other taxes can be attached at the site level.
9) Define Bond Register: In this form, we have to attach inventory
organization and the location to the order type or invoice type
alongwith the register type ie Domestic with excise, Trading
Domestic with excise etc. Only after this step the prescribed
registers under excise act will be maintained.
10) Excise for Trading Organizations: For trading organizations,
register under rule RG 23 D is required to be maintained. The tax
code for excise for trading organizations has to be ad-hoc. After
receipt of goods, the MODVAT credit is recorded in this register. For
sale of goods, after pick release, the matching of dispatches with
the receipts is required to be done in the Match Receipt Trading
form. The matching can be done either on FIFO basis or LIFO basis
or it can be done manually also. The excise paid on the receipts
matched is passed on to the customers after ship confirm.

You might also like