SAP CIN Configuration In Indian Taxing procedure

SAP CIN Configuration In Indian Taxing procedure, Excise Duty plays a vital role in
Manufacturing scenario s. Excise related configuration is known as CIN configuration.

CIN Configuration is a topic in itself. Some info on CIN Configuration (it may not appear
as understandable below, but if you check on screen, it will be understood better) Country
Version India comes with four pricing procedures as follows: - JINFAC (Sales from
Manufacturing plants) - JINEXP (Export sales) - JINDEP (Sales from depots) - JINSTK
(Stock transfers CIN: IMG > Logistics - General > Tax on Goods Movement > India >
Basic Settings > Maintain Excise Registrations In this IMG activity, you maintain the
data relating to your excise registrations. - Enter each of your excise registrations,
Specifying a four-character code for each Excise Registration Ids In this activity, you
Maintain excise registration IDs. You create one ID for each of your business's excise
Registrations. - For each excise registration in your business create a registration ID, and
state: - Which taxes the registration covers (additional excise duty, special excise duty,
and cess) Fields for any taxes that are not covered will be hidden in transactions
involving excise duty. - The maximum number of items to be printed on each excise
invoice - Whether you are allowed partial CENVAT credits Maintain Registration ID
NUMBER, Excise code number, excise registration number ECC Number: Specifies the
Organizations ECC number. Excise Registration Number: A number assigned to each
premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division: Specifies the excise division in whose area the excise registration is
located. Excise Collectorate: The code of the excise collectorate in whose area the excise
registration is located. Indicator for confirming, AED usage Additional Excise duty
Percentage. These are livable under the additional duties of excise act. These duties are in
addition to basic excise duty and special excise duty. Example - Additional Excise duty is
livable in case of textile products, tobacco and sugar. Similarly for SED CESS Number of
Items in Excise Invoice Shows the maximum number of line items that the authorities
allow per excise invoice. Dependencies - This information is used when you create an
excise invoice in Sales and Distribution (SD) for factory sales and for other movements.
This information is used to split the transfer postings' items into multiple subcontracting
challans. Excise register set description: Description of the excise registers set. Partial
CENVAT Credit: Indicates that the excise registration ID is allowed to credit only a
portion of its input excise duty to its CENVAT account Dependencies - When you post a
goods receipt, the system splits the input excise duty on the material into its deductible
and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT
account, and adds the nondeductible duty to the material value. This information is also
shown when you post the vendor's excise invoice. Maintain Company Code Settings. In
this IMG activity, you maintain the data relating to your company codes. Document Type
for CENVAT Postings. It controls, which document type the system uses when making
CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat
posting. Indicator for providing debit account overwriting Debit Account Overwrite
Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher
transaction. It provides the flexibility to the user to enter the debit account of his choice
depending on the nature of transaction. Automatic balance Indicator - Excise year start
month. The calendar month marking the beginning of the excise year. This start month
Represents the month for the start of the excise invoice number range. The month 04 is
entered here indicating April of the calendar year as the start month for excise invoices.
Any change by the Excise authorities regarding start month should be taken care of by an
entry in this field and initialization. Excise invoice selection procedure :Excise invoice
selection type. To indicate the method opted by the company for selecting the excise

invoice. It can be either earliest or latest invoices that were received. Number of excise
invoices to be selected Indicates the number of excise invoices that needs to be selected
in the excise invoice selection. Days to be considered for excise invoice selection
Number of days from document date for excise invoice selection. Example - If the value
of this field is 20 and today is 28-03-97. The excise invoice selection will show the
Related invoices only for the period 08-03-97 to 28-03-97. Document type for TDS FI
posting: Financial accounting document type for TDS posting. Document type for FI
posting on Utilisation Financial accounting document type for TDS posting. Indicator for
item level excise duty round off - This indicator is to be used for deciding whether Item
level excise duty amount rounding off is required during procurement cycle. If marked
'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase
order level. This will not round off the CENVAT credit to be taken. If the duty amount is
less than one rupee then no rounding is done Rounding off of Excise duty for outgoing
excise invoice - You can round off the Excise amount to be paid during an outgoing
Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for
each item where the amount is greater than 1 Rupee. Immediate Credit on Capital Goods
- Instructs the system, when you verify a goods receipt for capital goods, to immediately
post half of the input excise duty to the appropriate CENVAT accounts. The rest is posted
the CENVAT on hold account, for use in the following year. CVD Clearing Account Specifies which G/L account the system credits when you take a CENVAT credit on
countervailing duty in the Incoming Excise Invoices transaction. Exchange rate type Key representing a type of exchange rate in the system. - You enter the exchange rate
type to store different exchange rates. Example - You can use the exchange rate type to
define a buying rate, selling rate, or average rate for translating foreign currency amounts.
You can use the average rate for the currency translation, and the bank buying and selling
rates for valuation of foreign currency amounts. Exchange rate type to be used for Export
excise duty converts - When you are creating an Excise invoice for export sales then the
exchange rate for duty calculation will be picked up using this Exchange rate type.
Maintain Plant Settings - In this IMG activity, you maintain excise information relating to
your plants. Plant Settings - In this activity, you maintain excise information relating to
your plants. For each plant: - Specify whether it is a manufacturing site or a depot. Assign it an excise registration ID. - You can assign the same ID to more than one plant,
if required. Depot - Indicates that the plant in question is a depot. - Depots are required to
prepare register RG 23D, and follow different procedures for goods receipt and invoice
generation. - Number of goods receipt per excise invoice. - Multiple GR for one excise
invoice, Single credit - Multiple GR for one excise invoice, multiple credit Maintain
Excise Groups - In this IMG activity, you define your excise groups. For each excise
group, you can also control how various excise invoice transactions will work. Excise
Groups - In this activity, you define excise groups. An excise group allows you to
maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and
PLA serial numbers are created for an excise group. Recommendation - Under normal
Based Excise Determination and -> Formula-Based Excise Determination. IMG >
Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination
of Excise Duty > Condition-Based Excise Determination When you enter a purchasing
document, for example, a purchase order, the R/3 System automatically calculates the
applicable excise duties using the condition technique. Features : The standard system
comes with two tax calculation procedures. TAXINN is only supports condition-based
excise determination, whereas TAXINJ supports condition-based excise determination
and formula-based excise determination. Both tax procedures contain condition types that
cover all of the excise duties and sales taxes applicable. Since the exact rates of excise
duty can vary on a large number of factors, such as which vendor you purchase a material
from, or which chapter ID the vendor stocks the material under, you create condition
records for every sort of excise duty. When you come to enter a purchasing document,
the system applies the excise duty at the rates you have entered in the condition records.
Customizing : Make the settings in Customizing Basic -> India -> for Logistics

General, by choosing Taxes on Goods Movements Account -> Excise Duties Using
Condition Technique and -> Settings Determination. These activities include one

activity where you define a tax code for condition-based excise determination. Master
Data - Create condition records for all excise duties that apply, and enter the tax code for
condition-based excise determination in each. Day-to-Day Activities - When you enter a
purchase order or other purchasing document, enter the tax code for condition-based
excise determination in each line item. The system then calculates the excise duties using
the condition records you have created. When the ordered materials arrive, you post the
goods receipt and the excise invoice. The system posts the excise duty to the appropriate
accounts for deductible input taxes when you enter the excise invoice. Creating Condition
Records for Excise Duty 1. In the command field, enter FV11 and choose . 2. Enter the
condition type that you want to create a condition record for and choose . The Key
Combination dialog box appears. 3. Select the combination of objects that you want to
create the condition record for. On the dialog box, Control Code means "chapter ID." So,
for example, to create a condition record for a tax that applies to a combination of
country, plant, and chapter ID, select Country/Plant/Control Code. 4. Choose . 5. Enter
data as required. - In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record. Formula-Based Excise Determination - When you execute a
business transaction involving materials that are subject to excise duty, the system
automatically calculates the duty for you. In order for the system to be able to determine
which rate of excise duty to apply, you must have maintained all the data on the Excise
Rate Maintenance screen, which you can Master Dataaccess from the SAP Easy Access
screen by choosing Indirect Taxes Excise Rate Maintenance. You maintain the following
types of data: - Plant master data You assign each of your plants an excise duty indicator.
You can use the same indicator for all the plants with the same excise status from a legal
point of view, such as all those that are in an exempt zone. See also the information about
manufacturers that are only entitled to deduct a certain portion of the duty (see Partial
CENVAT Credit). - Vendor master data For each of your vendors with the same excise
status from a legal perspective, you define an excise duty indicator. You must also
specify the vendor type for example, whether the vendor is a manufacturer, a depot, or

a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale
industry. For each permutation of plant indicator and vendor indicator, you then create a
final excise duty indicator. - Customer master data Similarly, you assign the same excise
duty indicator to each of your customers that share the same legal excise status. Again,
for each permutation of plant indicator and customer indicator, you then create a final
excise duty indicator. - Material master data Each material is assigned a chapter ID. Excise tax rate For every chapter ID and final excise duty indicator, you maintain the rate
of excise duty. If your business only qualifies for partial CENVAT credit, you must
customize your system accordingly. Let us consider an example to illustrate how the
system determines which rate of excise duty to apply to a material. Assume you are
posting a sale of ball bearings to a customer. The system automatically determines the
rate of excise duty as follows: 1. Looks up the customer master data to see what status
you have assigned the customer. Let's assume you've assigned the customer status 3. 2.
Looks up the plant master data to see what status you have assigned the plant. Similarly,
your plant has status 2. 3. The system looks up the table under Excise Indicator for Plant
and Customer to see what the final excise duty indicator is for customer status 3 and plant
status 2: It is 7. 4. The system determines the chapter ID of the ball bearing for the plant.
Let s assume the chapter ID at plant for the ball bearings is 1000.01. 5. Finally, the

system looks up the table under Excise Tax Rate to see what rate of duty applies to
chapter ID 1000.01 under status 7. Define Tax Code for Purchasing Documents - In this
IMG activity, you define a tax code for the purposes of calculating excise duty when you
enter purchasing documents. Only carry out this activity if you use condition-based

excise determination. - Create a new tax code, and set the tax code type to V (input tax).
Do not make any other settings for it. - Assign Tax Code to Company Codes In this IMG
activity, assign the tax code for purchasing documents to the company codes where it will
be used. Only carry out this activity if you use condition-based excise determination.
Classify Condition Types - In this IMG activity, you specify which condition types you
use for which sort of tax. Note that this only applies to condition types that you use with
the new excise determination method. The system uses this information when you create
a document from another one. For example, when you enter an incoming excise invoice
from a purchase order, or when you create an outgoing excise invoice from a sales order,
the system determines the various excise duties in the excise invoice using the
information that you have entered here. In addition, when you create a purchasing
document, the system only uses the condition types that you enter here. - For taxes on
purchases, use the condition types contained in the tax procedure. - For taxes on sales,
use the condition types contained in the pricing procedures. The standard system comes
with sample settings for the tax calculation procedures and pricing procedures. Use these
settings as a basis for your own. IMG > Logistics - General > Tax On Goods Movement
> India > Account Determination Define G/L Accounts for Taxes - In this IMG activity,
you specify which G/L accounts you will use to record which taxes. Requirements - You
have set up G/L accounts for each of the processing keys listed below. - Assign an
account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are
used as clearing accounts during excise invoice verification. - VS1 (basic excise duty) VS2 (additional excise duty) - VS3 (special excise duty) - VS5 (sales tax setoff) - MWS
(central sales tax) - MW3 (local sales tax) - ESA (service tax) - ESE (service tax expense)
Specify Excise Accounts per Excise Transaction - In this IMG activity, you specify
which excise accounts (for excise duty and CENVAT) are to be posted to for the various
transaction types. Enter all the accounts that are affected by each transaction type. If you
use sub transaction types, enter the accounts for each sub transaction type as well.
Transaction type UTLZ is used for determining accounts only while posting excise JVs
and also if the payment of excise duty has to be done fortnightly. The fortnightly
CENVAT payment utility picks up the credit side accounts from the transaction types of
GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no
separate transaction type for fortnightly payment. Example: - Excise TT DC ind Account
name - GRPO CR CENVAT clearing account - GRPO CR RG 23 BED account - GRPO
DR CENVAT on hld account Specify G/L Accounts per Excise Transaction - In this IMG
activity, you assign the excise and CENVAT accounts to G/L accounts. When you come
to execute the various transactions, the system determines which G/L accounts to post to
by looking at the: - Excise group - Company code - Chart of accounts Furthermore, if you
want separate account determination settings within an excise group, you can also use sub
transaction types. Requirements You have already: - Defined the G/L accounts - Defined
the excise groups - Maintained the transaction accounts Activities - For each excise
group, assign the excise and CENVAT accounts to G/L accounts. For most businesses,
one set of accounts will suffice for all transactions. Note : you need not remit the
CENVAT to the excise department immediately, so maintain the credit account for
transaction type DLFC as an excise duty interim account. This will be set off when you
remit the duty. Config setting needed to be done in order to get the Excise Details Screen
in Material Master. Even though this functionality is available in enterprise version, a
small configuration step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration. - Material Master Logistics
General 1. Go to IMG Define Structure of Data Screen for each Configuring the Material
master Screen Sequence. 2. Select your screen sequence. Usually it would be 21. Select
the same and click on Data Screen in the left frame. 3. Once the data screens are
exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is F o reign Trade:

Import Data . Select the same and click on Sub screens in the left frame. 4. Go to the last

sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view sub
screen and ensure that the sub screen is blank. 5. Now in the last sub screen i.e. no.6 you
delete SAPLMGD1 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the

Screen no. 2205. 6. Save the setting. 7. Create a Material Master and check whether in
Screen Foreign Trade Import, Excise related sub screen appears.

Create characteristic"Re le as e _ PR_ p lant " in transaction code CT04.

Tab - Basic data - Data type - CHAR; Number of chars - 4
Tab - Values - Key in all the plants for which you are required to configure release proc. eg.
1000,2000,3000
Tab - Additional data - Table nameCEB A N and Field Name isW ERK S.
3) Purchaisng Group
Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
Tab - Basic data - Data Type - char, Number of chars eg. 3
Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as
required by Client.
Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
Step 2:
Define class in transaction code CL02
Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with
Classification>Edit classes
Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered
when all the conditions are met.
Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the
class name and select class type as 032 - RELEASE STRATEGY then click on symbolcr e ate to enter all the
details as mentioned below.
Tab - Basic data - Enter description as "PR_Release-Proc",
status- Released, Same classification - check the push button - Warning Message
Tab- CHAR Enter above created 3 characteristics
1.Release_PR_total_value
2.Release_PR_plant
3.Release_PR_PurchasingGroup
step3:
Menu path is
SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with
Classification>set up procedure with classification>
here define
1.Release Groups
Release group 01 is used for Purchase requisitions and 02 for Purchase orders.

Here assign class "PR_Release_proc" against release code "01"

check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be
released line item wise.
2.Release codes
Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs
through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
PRs are released by users in transaction code ME54N.
Eg
Type of user

- Level Release code

PR creator - clerk or Business user Approver - Supervisor
- R1
Approver - Project Lead
- R2
Approver - Asst. Manager
- R3
Approver - HOD/General Manager - R4
Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if
prior approvals till R3 are completed else not in ideal situation.
For detailed info please refer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
3. Release Indicator:
Release indicators show the release status of a Purchase Requisition.
For detailed info please refer SAP Help official site
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
4.Release Pre requisites:
These define the order in which individuals or departments release the PR in sequence.
3.Release strategies
Create a new release startegy eg ."A1" or "U1" , write its description PR release for value >1 lakh
Now select release codes according to the Chart of Authority set by your client.
Eg.
Release startegy " A1 - PR release for value >1 lakh"
R1 - Supervisor
R2- Project Lead
R3- Asst. Manager
R4- General Manager
Now click on" Release Prerequisites "push button and check all the boxes in ascending order.Save the
document
click on "Release statuses" push button, check release statuses then click on "Continue" push button.
In third push button you can maintain CLA SSI FI CA T I ON data or later you can directly maintain in
Transaction code CL20N for this strategy.
Classification data for example
1. Value - > 100000
2. Plant - 1000,2000,3000 etc
3. Purchasing groups - 101,102,103 etc
By clicking on "Release Simulation" push button you can check whether release is getting affected for
configured release codes or not.
In this way you can configure all the required Release startegies.
Workflow:
Here Maintain SAP user ids in the column "Agent ID" defined against Group/Rel code/Object type.PR after
approval will flow to the next user in the SAP inbox accessed through T code SBWP.
SAP User IDs or Agent IDs are tagged to respective Release Group and Release codes
Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen
at the time of check.Save the document and this can be released by respective users in TCode ME54N.
Tcode - ME54N - For Individual Release
Tcode - ME55 - For Collective Release
For detailed info please visit SAP HELP website
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm\\
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
List of most important notes in MM-PUR
MM-PUR
30316 Problems with fields that are not ready for input in purch.

MM-PUR-GF-ACC
496082 FAQ: Account assignment in purchasing
627072 ME21N: incorrect account assignment on cost center
551863 ME21N: Accnt assignment not derived for required entry field
MM-PUR-GF-ADR
498153 FAQ: Addresses in the purchasing
821981 Change in Vendor Address in PO updates Vendor Master address
422641 ME21N, ME22N:
MM-PUR-GF-ARC
456129 FAQ: Archiving in purchasing
401318 Archiving: Additional information
335800 SARA: Deletion indicator not set, but why?
MM-PUR-GF-REL
365604 FAQ: Release strategies in purchasing
493900 FAQ: Release Strategy
86900 Transport of Release strategies (OMGQ,OMGS)
MM-PUR-GF-ARL
499625 FAQ: Optical archiving in purchasing
732278 Display of Originals does not work for archived documents
There are many queries on Pricing Procedures in SD module
498153 FAQ: Addresses in the purchasing
821981 Change in Vendor Address in PO updates Vendor Master address
422641 ME21N, ME22N:
MM-PUR-GF-ARC
456129 FAQ: Archiving in purchasing
401318 Archiving: Additional information
335800 SARA: Deletion indicator not set, but why?
MM-PUR-GF-REL
365604 FAQ: Release strategies in purchasing
493900 FAQ: Release Strategy
86900 Transport of Release strategies (OMGQ,OMGS)
MM-PUR-GF-ARL
499625 FAQ: Optical archiving in purchasing
732278 Display of Originals does not work for archived documents
There are many queries on Pricing Procedures in SD module in the forum.
Pricing Procedure is indeed an heart of SD module, reason being if everything else is working fine, but price
is not being calculated correctly, the purpose of billing fails.
An Overview of Determination & Configuration of Pricing Procedure is as follows:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre
+ Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined
in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document
Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing
procedure is determined, Condition records are fetched. If appropriate condition records are found, the price
is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table.
Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG
-> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Table (select the required fields
combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access
sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows:
IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Access Sequence (Access sequence is

made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the
condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type.
Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG ->
Sales & Distribution -> Basic Function -> Pricing Control -> Condition Type. It is always recommended to
copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to
Condition type.
Step 4:

a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes
in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it
has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will
be done in spro as follows: IMG -> Sales and Distribution -> Basic Function -> Price Control -> Pricing
Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing
procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG -> Sales and
Distribution -> Basic Function -> Price Control -> Pricing Procedure --> Determine Pricing Procedure.
Step 5: Condition record: Condition record is a master data, which is required to be maintained by Core
team / person responsible from the client. During new implementation, the condition records can be
uploaded using tools like SCAT, LSMW, etc.
It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
How to Create SCAT program for any mass upload purpose?
SCAT is similar to LSMW/BDC to upload/updated data in SAP from legacy system.

The differences between SCAT and LSMW:LSMW and SCAT has different functionalities and different advantages, but common thing is
they are used for data upload.
SCAT is mainly used as a testing tool for follow-on transactions i.e. Purchase Requisition,
Purchase order, Goods Receipt etc.
Whereas LSMW is used for Master data (Materials, Customer, Vendor, BOM, Info record etc)
and some of the transactions data (Purchase order, purchase requisition)
There are many standard objects are available in LSMW so most of the consultants use LSMW,
but again depends on the requirement.
Writing a CAT script to create user:1 Recording a test case
1.1 To record a test case, call Transaction SCAT and enter test case Zuser_creat.
- Do not choose Enter.
- Choose Test Case ? Record Transaction. Enter Transaction SU01, and choose Record/Enter.
- The system runs Transaction SU01.
- Enter the user name TESTZ and choose Create.

- Enter the users title first name ZEBRA and the last name TEST.
- Select the Logon data tab, enter init as the initial password, and repeat the password, profile
select sap_all then choose Save.
- Go back a screen and in the dialog box displayed, select End recording.
- A message is displayed stating that the recording has ended.
- Enter the test case title User maintenance.
- In the field Component, enter BC-SEC-USR.
- Save the test case.
- In the field package class, enter $TMP.
- Choose Save to save the attributes.
- To save the test case functions, go back.
2 Entering parameters for a test case
2.1 To define parameters for a test case, call Transaction SCAT.
- Enter the test case name Zuser_creat.
- Select Functions and choose Change.
- Double-click on TCD.
- Then double-click on program SAPLSUU5 screen 0050. (first appearance of this program)
- The first screen of Transaction SU01 is displayed. (If you backed out, enter the procedure name
again and double-click on TCD.)
- Double-click on the user name field. In the field Param. name, enter an "&", and choose
Copy/Enter.
- Choose Next screen and double-click the last name. In the field Param. name, enter an "&" and
choose Copy/Enter.
- Go back until the Save folder appears, and choose Save.
3 Creating and using an external variant for the test case
3.1 To export the default parameters into a frontend file, in the test case, select Goto? Variants ?
Export Default.
Note: The default file name is <the name of your test case>.txt. Do not change the default
values.
3.2 Open the file, with excel and edit and add another couple of user, and save the text file
3.3 To execute the test case using the external variant from file, from the initial CATT screen,
enter the test case name and choose Execute.
In the field Variants, select External from file and choose Choose. Select the file created above,
and choose Open. Under Processing mode, select Errors, and choose Execute.
Entitled Allowed

For excise invoice you have to check table J_1iEXCHDR .you can link VBRK with this table like :
vbrk-vbeln = j_1iexchdr-rdoc.
Look in table j_1iexchdr for that particular billing document to see wheather excise invoice is created.

Excise Table Entry

1) While we do excise JV through J1IH does it make the part 2 entry in excise table ? If so than in which table?
2) In which table RG23A part1 &part 2 entries registered, while we do PGI & PGR for raw material?
3) In which table RG23C part1 &part 2 entries registered, while we do PGI & PGR for capital goods?
4) In which table RG1 entry registered, while we do PGI & PGR for finished goods?

5) In which table RG23D entry registered, while we do PGI & PGR from depot?
6) While we create return delivery and PGR for excisable material which register gets updated and how (while
excise JV has not done)? What is the setting behind it?I know that can be set in excise group but how it updates the
part1 entry is it hard coded??
The following are the tables
J_1IRG1 Excise RG1 details
J_1IRG23D RG23D register for the depot
J_1IRGSUM RG23 Summary of receipts and issues
J_1IPART1 Excise part I detials
J_1IPART2 Excise Part II details
J_1IEXCDEP Excise information of vendor at detail lev
J_1IEXCDTL Excise invoice line item details
Hi Verma, SAP CIN tables start with J_1I* . You can go to se11 or se16 and give J_1I* against field table name and
press F4. Then you will get all the CIN related tables. I am just giving some of the tables. J_1IADDEXC Additional
Excise rate table J_1IADDRES Excise Related Address Management J_1IADDRESS Excise Related Address
Management J_1IARE_ATTRB Excise Bonding: Attributes J_1IASSVAL Assessable value table for excise calculat
J_1IBILDET Billing Type Determination - India J_1IBOND Excise Bonding: Bonds/UT-/Running Bond mas
J_1IBOSDEFAULT Default Blling Type for Export J_1ICALOC Allocation of materials to assets J_1ICERTIF
TDS certificate information J_1ICHIDTX Text Table for Chapter ID J_1ICHPTER Chapter ID Master J_1ICOMP
Additional company data J_1ICONDTAX Tax Codes for Excise Duties Using Conditio J_1ICUS_BILL_TYP
Assign Customer Category to Bill Type J_1IDCLSDET Document class Determination - India J_1IEICOCU
Excise indicator determination for company J_1IEICOVE Excise indicator determination for company
J_1IEWTCALID Calendar for Payment Due date-EWT India J_1IEWTCALID_N Calendar for Payment Due dateEWT India: S J_1IEWTCHLN Table for Internal and external Challan no J_1IEWTDOCKEY Document Types for
Extended Withholding Ta J_1IEWTDTCHLN Document Type for Remittance Challan - Cla J_1IEWTDTPRV
Document Types for TDS Provisions -EWT In J_1IEWTDUEDATE Tax Due Dates J_1IEWTECESS Education
Cess Codes J_1IEWTHKONT Table for for TDS provisions Accounts / L J_1IEWTJV Document Types for Journal
Vouchers J_1IEWTNO No range for certificate Printing-EWT Indi J_1IEWTNUM INTERNAL NO RANGE FOR
CHALLANS- EWT INDIA J_1IEWTNUMGR Number Groups For Internal Challan Numbers
J_1IEWTNUMGR_1 Number Groups For Internal Challan Numbers J_1IEWTNUMGR_N Number Groups For
Internal Challan Numbers J_1IEWTPROV Table for TDS provisions J_1IEWTPROVISACC Maintain entries for
accts to be considere J_1IEWTSURC Surcharge Tax Codes J_1IEWT_CERT SAPscript Forms/section indicators
for E J_1IEWT_CERTIF Certificate Issued Details-EWT India J_1IEWT_CERTIF_N Certificate Issued DetailsEWT India:SECCO J_1IEWT_CERTNO Number Ranges for Withholding Tax Certific J_1IEWT_CERT_N
SAPscript Forms/section indicators for EWT J_1IEWT_COMP Surcharge Calculation Methods J_1IEWT_CUST
Customer certificates ,Challan customizin J_1IEWT_CUSTV View for Document type for Challan UpdateJ_1IEWT_ECESS1 Education Cess Rates J_1IEWT_ECFLAG Separate Tax code for Ecess J_1IEWT_HC Health
check for migration to EWT status. J_1IEWT_MAPEXM Assign Exemption Reasons to Withholding Ta
J_1IEWT_MAPEXMPT Table for Vendor type/exemption indicators J_1IEWT_MIGRATE Map Classic tax code
to EWT Tax type - Tax J_1IEWT_SURC Maintain Surcharge Calculation Methods J_1IEWT_SURC1 Surcharge
Rates J_1IEWT_VENTYP Assign Types of Company to Withholding Tax J_1IEXCACC Excise Account
Assignment table J_1IEXCDEF Tax default informations J_1IEXCDEFN Default Condition Types J_1IEXCDEP
Excise information of vendor at detail lev J_1IEXCDTL Excise invoice line item details J_1IEXCHDR Excise
invoice header detail J_1IEXCREF Delivery document to excise invoice refren J_1IEXCTAX Tax calc. - Excise
tax rates J_1IEXESTA Excise indicator determination for co / cu J_1IEXGRPS Excise Groups J_1IEXMPTCODE

VAT Exempted Tax code J_1IEXSRDET Excise / Series group determination J_1IEX_CUST_ACT Define
Processing Modes Per Transaction J_1IEX_CUST_FLDS J1IEX: Incoming Invoices field selections
J_1IEX_CUST_REF Define Reference Documents Per Transaction J_1IFRDTOT Transaction Table for Forms
Tracking-Non S J_1IFRDTPO tranasction Table for Forms Tracking for P J_1IFRDTSO Transaction table for
Forms Tracking for S J_1IFRMTYP Form Types J_1IGRXREF Goods Receipt to Excise Invoice Coss Refer
J_1IGRXSUB GR reference to subcontracting challans J_1IINDCUS Company Code Settings J_1IITMDTL Item
Details - for Capital goods and subco J_1IKONV Excise recalculated conditions J_1ILICDTL Excise Bonding:
License detail J_1ILICHDR Excise Bonding: License Header J_1ILICTYPE Excise Bonding: License type master
J_1IMATEXP Exceptional materials excise rates J_1IMESG Message Control J_1IMINBAL Minimum account
balances J_1IMOCOMP Company and Plant - Excise Additional Data J_1IMOCUST Customer Master Excise
Additional Data J_1IMOCUSTEWT Maintain PAN no for Customers -EWT India J_1IMODDET Modvat
Determination Table (Input Material J_1IMOVEND Vendor Master Excise Additional Data J_1IMOVENDEWT
Maintain PAN no for Certificates-EWT India J_1IMTCHID Combination of Material Number and Chapter
J_1IMVMT Movement types versus register relevance J_1IMVTGRP Movement type Group for Subcontrcting
J_1INEWJCODE VAT Transition Dummy Jurisdiction Code J_1INEXCGRP excise group for no range J_1IPART1
Excise part I detials J_1IPART2 Excise Part II details J_1IQEXCISE Quantity based AED, NCCD and SED
J_1IREGSET Excise Registrations J_1IREJMAS Rejection Codes J_1IRG1 Excise RG1 details J_1IRG1RNG
Group table for RG1 - Number Range Object J_1IRG23D RG23D register for the depot J_1IRGSUM RG23
Summary of receipts and issues J_1IRSNCODEM Exemption Reason Code; e-Filing India Loca J_1ISERVC
Service tax details J_1ISRGRPS Excise Document Series J_1ISSIRAT ssi concessional rates J_1ISTAPPL Tax
applicability J_1ISTATECD State Codes; e-Filing, Localization India J_1ISTATECDM State Code Mapping; eFiling India Locali J_1ISTATECDT State Code Texts; e-Filing India Localiza J_1ISTRATE Sales tax set off
percentages J_1ISUBATT Subcontracting Scenario Attributes J_1ISUBBYP Subcontracting Scrap/ Byproduct
J_1ISUBTYP Subtransaction type text J_1IT030K India Tax account determination ( T030K + J_1IT030K_V India
Tax Account Determination J_1IT059A Indicator to mention tax exemption J_1ITAXDEP Depreciation
computation as per Income Ta J_1ITAXIND Excise Tax Indicator J_1ITCJCMAP Tax code and Jurisdiction code
mapping J_1ITCJCUPDATE Updatation table for open documents J_1ITDS Classic TDS - reference table
J_1ITDSDUE TDS Payment due date customization J_1ITDSSEC TDS Sections J_1ITDSTXC TDS - Withholding
taxcode and section rel J_1ITRAN Transaction code J_1ITRNACC Transaction code vs accounts J_1IUTILIZE
Utilization Determination J_1IV2ARE_ATTRB Make Settings for ARE-1 Procedure J_1IVARE_ATTRB Make
Settings for ARE-3 Procedure J_1IVATDATE Maintain Valid from date of VAT legislatio J_1IVATDATE_V
Maintain Valid from date of VAT legislatio J_1IVATINVOICE Billing type determination for VAT J_1IVATREGIO
States Under VAT regime J_1IVCHID View of Chapter ID and text J_1IVEXGRP Help view for Excise groups
J_1IVEXGRPS Excise Group Maintenance J_1IVFRMTY Help view for Form type J_1IVFRTYP Maintenance
view for Form Types J_1IVREGID Help View for the register id J_1IVSRGRP Help view for serial group
J_1IVT001 Document types for TDS JV J_1IVTDSDU Payment due date in TDS J_1IVTRAN Help view for the
transaction type J_1IVTTXID Text maintenance J_1IVTTXOB Text object maintenance J_1IVTXNOR Excise tax
rates - normal J_1IVTXRAT Tax rate maintenance J_1IVTXSPL Excise tax rates J_1IV_INVC Help view for
Vendor Excise invoice J_1IWRKCUS Plant Settings J_1I_BCKEXCSUS Customizing table for background
capture o J_1I_CUST_CERT Data table for clearing doc on customer ta J_1I_EWT_RETURN Annual returns Documemnt View J_1I_INBDELV INBOUND DELIVERY DETAILS FROM sus J_1I_SECCODE Section Codes
for Extended Withholding Tax Hope this helps. Thanks, Viswanath

For PGR (Post goods Receipt) if you maintain the movement type 651 for RG1 Entry then it will update RG1. for
the returns.
According to standard process it should update RG23A or Rg1??
Please clear me. As u told we can configure any table to update through movement type 651.

If i am creating sales order excise duty is not calculating.there is message which is Im getting.No add. Vendor /
Customer data maint. for -Please maintain J_1IMOVEND.

Go to J1ID transaction and maintain the data for Vendor / Customer in the tab Vendor Excise Detail / Customer
Excise Detail.
In customer master and vendor master please check whether you have maintained the values in Excise tax
indicator.If the values are not maintained then the value will not flow.
In both Customer and Vendor master there is a Tab for CIN. If the tab is not appearing in your case go to transaction
OMT3E (Path :-IMG-->Logistic General-->Tax on Goods Movement--> India-->Master Data -->Assigne Users to
material Master Screen Sequence for Excise Duty)
There go to User Scren Reference and maintain your User ID in Name column and give * in SRef.User column -->
SAVE.
This will bring the CIN Tab in master data. Go there and maintain the CIN data. This will help you in processing the
Excise Transactions.
Go to J1ID, select "Customer Excise details" and execute. There check whether the customer code is maintained
there. If so, drag your mouse to right side and check "1" is maintained under the tab "Declared".
sapdocs.info/sap/sd-related.../excise-invoice-user-manual/
table for excise sap sd
http://sapdocs.info
http://www.scribd.com/doc/24369622/SAP-SD-Excise-Invoice-User-Manual-http-sapdocs-info