You are on page 1of 24

Country Version India

A Country Version is designed specifically to cater the business operations of that Links
country over and above the generic SAP system functionalities. It comprises of
Operations Home
functionalities degined for the laws and business practices pertaining to the country.
ERP SD
Most of the country-specific functions for India relate to Financials and Logistics. ERP MM
The main areas are as follows: ERP PP
ERP QM
• Excise duty and the central value-added tax system (CENVAT)
ERP WM
• Withholding tax (also known as tax deducted at source)
ERP TM
• Sales tax
• Maintenance and printing of statutory excise registers Forums
ERP General Forum
The official help documentation for Country Version India is here.
ERP-MM Forum
ERP-SD Forum
ERP-PP Forum
ERP-MM Forum

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.

Here is some information on CIN Configuration. While it may not appear understandable as given below, it
will be understood better when you check on screen.

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

Use
In this IMG activity, you maintain the data relating to your excise registrations.
Activities
Enter each of your excise registrations, specifying a four-character code for each
Excise Registration IDs
In this activity, you maintain excise registration IDs. You create one ID for each of your business's
excise registrations.

Activities
For each excise registration in your business create a registration ID and state:
• Which taxes the registration covers (additional excise duty, special excise duty, and cess)Fields for
any taxes that are not covered will be hidden in transactions involving excise duty.
• The maximum number of items to be printed on each excise invoice
• Whether you are allowed partial CENVAT credits

Maintain Registration ID NUMBER, Excise code number, excise registration number

Excise Registration Number


A number assigned to each premises or location that has registered as a manufacturer with the
excise authorities.
Every entity with an excise registration number is required to keep its own excise books.

ECC Number
Specifies the organization's ECC number.

Excise Registration Number


A number assigned to each premises or location that has registered as a manufacturer with the
excise authorities.
Every entity with an excise registration number is required to keep its own excise books.

Excise range: Specifies the excise range in whose area the excise registration is located.

Excise Division
Specifies the excise division in whose area the excise registration is located.

Excise Collectorate
The code of the excise collectorate in whose area the excise registration is located.

Indicator for confirming AED usage


Additional Excise Duty Percentage. These are leviable under the additional duties of excise act.
These duties are in addition to basic excise duty and special excise duty.
Example
Additional Excise duty is leviable in case of textile products, tobacco and sugar.

Similarly for SED CESS

Number of Items in Excise Invoice


Shows the maximum number of line items that the authorities allow per excise invoice.
Dependencies
This information is used when you create an excise invoice in Sales and Distribution (SD) for factory
sales and for other movements.

This information is used to split the transfer postings' items into multiple subcontracting challans.

Excise register set description


Description of the excise registers set.

Partial CENVAT Credit


Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to
its CENVAT account.
Dependencies
When you post a goods receipt, the system splits the input excise duty on the material into its
deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT
account, and adds the nondeductible duty to the material value.

This information is also shown when you post the vendor's excise invoice.

Maintain Company Code Settings


Use
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings
It controls, which document type the system uses when making CENVAT postings in Financial
Accounting (FI). Here ED is document type for cenvat posting.

Indicator for providing debit account overwriting


Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise
journal voucher transaction. It provides the flexibility to the user to enter the debit account of his
choice depending on the nature of transaction.

Automatic balance Indicator

Excise year start month


The calendar month marking the beginning of the excise year
Use
This start month represents the month for the start of the excise invoice number range. The month
04 is entered here indicating April of the calendar year as the start month for excise invoices. Any
change by the Excise authorities regarding start month should be taken care of by an entry in this
field and initialization.

Excise invoice selection procedure


Excise invoice selection type. To indicate the method opted by the company for selecting the excise
invoice. It can be either earliest or latest invoices that were received.

Number of excise invoices to be selected


Indicates the number of excise invoices that needs to be selected in the excise invoice selection.

Days to be considered for excise invoice selection


Number of days from document date for excise invoice selection.
Example
If the value of this field is 20 and today is 28-03-97. The excise
invoice selection will show the related invoices only for the
period 08-03-97 to 28-03-97.

Document type for TDS FI posting


Financial accounting document type for TDS posting.

Document type for FI posting on Utilisation


Financial accounting document type for TDS posting.

Indicator for item level excise duty round off


This indicator is to be used for deciding whether Item level excise duty amount rounding off is
required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to
the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken.
If the duty amount is less than one rupee then no rounding is done

Rounding off of Excise duty for outgoing excise invoice


You can round off the Excise amount to be paid during an outgoing Excise invoice by marking this
indicator as 'X'. The rounding is done at the item level for each item where the amount is greater
than 1 Rupee.

Immediate Credit on Capital Goods


Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of
the input excise duty to the appropriate CENVAT accounts.

The rest is posted the CENVAT on hold account, for use in the following year.

CVD Clearing Account


Specifies which G/L account the system credits when you take a CENVAT credit on countervailing
duty in the Incoming Excise Invoices transaction.

Exchange rate type


Key representing a type of exchange rate in the system.
Use
You enter the exchange rate type to store different exchange rates.
Example
You can use the exchange rate type to define a buying rate, selling rate, or average rate for
translating foreign currency amounts. You can use the average rate for the currency translation, and
the bank buying and selling rates for valuation of foreign currency amounts.

Exchange rate type to be used for Export excise duty converts


When you are creating an Excise invoice for export sales then the exchange rate for duty calculation
will be picked up using this Exchange rate type.

Maintain Plant Settings


Use
In this IMG activity, you maintain excise information relating to your plants.
Plant Settings
In this activity, you maintain excise information relating to your plants.
Activities
For each plant:
? Specify whether it is a manufacturing site or a depot.
? Assign it an excise registration ID.
You can assign the same ID to more than one plant, if required.

Depot
Indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt
and invoice generation.
Number of goods receipt per excise invoice.

Multiple GR for one excise invoice, Single credit


Multiple GR for one excise invoice, Multiple credit

Maintain Excise Groups


Use
In this IMG activity, you define your excise groups. For each excise group, you can also control how
various excise invoice transactions will work.
Excise Groups
In this activity, you define excise groups. An excise group allows you to maintain a separate set of
excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for
an excise group.

Recommendation
Under normal circumstances, excise authorities require every business to maintain only one set of
excise registers and one set of accounts. But through exemption from the authorities, multiple books
can be maintained.

If your company has only one set of excise registers, then you need to maintain only one excise
group.

Activities
1. Create one excise group for each set of registers that you need to keep.
1. Assign the excise groups to plants.
2. Maintain whether this Excise group is for a depot or not.
3. If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank.
If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark
the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to
availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one
excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick
the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately and would
like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the
selected records into RG23D automatically. You cannot cancel the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the
Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during
receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along
with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into
Blocked stock .
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through
inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of
material into consumption stock.
Excise Group
Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration.

Dependencies
In define excise groups in Customizing.
Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice,
you specify which excise group you are using. This information tells the system which G/L accounts
to post the excise to.
At the end of the period, when you come to prepare your excise registers, you create different sets
for each excise group.

Indicates that the plant in question is a depot.


Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt
and invoice generation.

GR Per Excise Invoice

Multiple GR for one excise invoice , Multiple credit


Multiple GR for one excise invoice , Single Credit

Create Excise Invoice Automatically


Instructs the system to automatically create a Sales and Distribution (SD) excise invoice
immediately you create a commercial invoice or a pro forma invoice.
The excise invoice is created in the background.
Dependencies
If you want to make use of this function, you must also define the default plant, excise group, and
series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series
Group Determination.

RG23D Sales Creation and posting option


RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of
excise invoices in single step.
If this is not selected then you need to separately do RG23D selection followed by PGI and then
RG23D verification and posting.
If you need automatic posting of RG23D selection then the Post Goods Issue should have been
completed before running RG23D selection.

Default excise qty in GR


If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise
invoice quantity on to the Goods receipt document.

Folio number for depo

Posting
If this indicator is marked then while creating Excise invoice for other movements system
automatically does the Verify and Post. You need not separately Post the excise invoice
Also we can set indicator for creation of part 1 for:

Blocked stock
Stock transport order
Consignment stock

Maintain Series Groups


Use
In this IMG activity, you define the different excise series groups within your company. Series groups
allow you to maintain multiple number ranges for the outgoing excise documents.
Based on excise regulations and exemptions from the authorities you can maintain multiple number
series for outgoing documents. But each of these series has to be declared to the excise authorities.
Activities
? Define excise series groups based on type of outgoing document
? Assign series group to excise registration ID
? If no financial postings are required for an Excise invoice in this seris group then you tick the 'No
utilization' indicator.
? If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then
mark the 'Immediate Utilization' indicator.
Example
You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4
documents.

No account postings for CENVAT in sales cycle


No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just generate an
excise invoice then you need to mark this indicator.
IF the flag is checked then system will create an Excise invoice in the given Series group but there
will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT
Specifies that when you create an excise invoice, the system immediately pays the amount from
CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the account
determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being done for
fortnightly utilization program.

Maintain Excise Duty Indicators


Use
In this IMG activity, you maintain the excise duty indicators.

IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of
Excise Duty >
Select Tax Calculation Procedure
Use
In this IMG activity, you specify which tax procedure you want to use for determining excise duties
and sales taxes on input materials in India.
? If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
? If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with
both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that
once you have started using a tax procedure, you cannot switch to another one, otherwise you will
not be able to display old documents.

Maintain Excise Defaults


Use
In this IMG activity, you define which tax procedure and pricing condition types are used in
calculating excise taxes using formula-based excise determination.
Activities
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others
blank.
If you use formula-based excise determination, fill out all of the fields as follows:
? Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
? Specify the purchasing and sales conditions types used for basic excise duty, additional excise
duty, special excise duty, and cess.
? Specify the conditions in the sales order that are used for excise rates.
? Specify the countervailing duty condition type used for import purchase orders.
See also

SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM)
-> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of
Excise Duty >
Condition-Based Excise Determination
Use
When you enter a purchasing document, for example, a purchase order, the R/3 System
automatically calculates the applicable excise duties using the condition technique.
Features
The standard system comes with two tax calculation procedures. TAXINN is only supports condition-
based excise determination, whereas TAXINJ supports condition-based excise determination and
formula-based excise determination. Both tax procedures contain condition types that cover all of
the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor
you purchase a material from, or which chapter ID the vendor stocks the material under, you create
condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates
you have entered in the condition records.
Activities
Customizing
Make the settings in Customizing 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


Use
When you execute a business transaction involving materials that are subject to excise duty, the
system automatically calculates the duty for you.
Prerequisites
In order for the system to be able to determine which rate of excise duty to apply, you must have
maintained all the data on the Excise Rate Maintenance screen, which you can Master Data?access
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.
Activities
Let us consider an example to illustrate how the system determines which rate of excise duty to
apply to a material. Assume you are posting a sale of ball bearings to a customer. The system
automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant.
Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final
excise duty indictor is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Let's assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to
chapter ID 1000.01 under status 7.
Define Tax Code for Purchasing Documents
Use : In this IMG activity, you define a tax code for the purposes of calculating excise duty when you
enter purchasing documents.
Only carry out this activity if you use condition-based excise determination.
Activities: Create a new tax code, and set the tax code type to V (input tax). Do not make any other
settings for it.

Assign Tax Code to Company Codes


Use
In this IMG activity, assign the tax code for purchasing documents to the company codes where it
will be used.
Only carry out this activity if you use condition-based excise determination.

Classify Condition Types


Use
In this IMG activity, you specify which condition types you use for which sort of tax. Note that this
only applies to condition types that you use with the new excise determination method.
The system uses this information when you create a document from another one. For example,
when you enter an incoming excise invoice from a purchase order, or when you create an outgoing
excise invoice from a sales order, the system determines the various excise duties in the excise
invoice using the information that you have entered here.
In addition, when you create a purchasing document, the system only uses the condition types that
you enter here.
? For taxes on purchases, use the condition types contained in the tax procedure.
? For taxes on sales, use the condition types contained in the pricing procedures.
Standard settings
The standard system comes with sample settings for the tax calculation procedures and pricing
procedures.
Use these settings as a basis for your own.

IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
Define G/L Accounts for Taxes
Use
In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements
You have set up G/L accounts for each of the processing keys listed below.
Activities
Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are
used as clearing accounts during excise invoice verification.
? VS1 (basic excise duty)
? VS2 (additional excise duty)
? VS3 (special excise duty)
? VS5 (sales tax setoff)
? MWS (central sales tax)
? MW3 (local sales tax)
? ESA (service tax)
? ESE (service tax expense)

Specify Excise Accounts per Excise Transaction


Use
In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be
posted to for the various transaction types. Enter all the accounts that are affected by each
transaction type.
If you use subtransaction types, enter the accounts for each subtransaction type as well.
Activities
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the
payment of excise duty has to be done fortnightly.
The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types
of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate
transaction type for fortnightly payment.
Example
Excise TT DC ind Account name
GRPO CR CENVAT clearing account
GRPO CR RG 23 BED account
GRPO DR CENVAT on hld account

Specify G/L Accounts per Excise Transaction


Use
In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
When you come to execute the various transactions, the system determines which G/L accounts to
post to by looking at the:
? Excise group
? Company code
? Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can
also use sub transaction types.
Requirements
You have already:
? Defined the G/L accounts
? Defined the excise groups
? Maintained the transaction accounts
Activities
For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most
businesses, one set of accounts will suffice for alltransactions.
Note
You need not remit the CENVAT to the excise department immediately, so maintain the credit
account for transaction type DLFC as an excise duty interim account. This will be set off when you
remit the duty.
Config setting needed to be done in order to get the Excise Details Screen in Material Master.

Even though this functionality is available in enterprise version, a small config step has to be made
in Screen Sequences for Material Master.

Following document helps you to do this configuration.

? 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
"Foreign Trade: Import Data". Select the same and click on Subscreens in the left frame.
4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view
subscreen and ensure that the subscreen is blank.
5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 - 0001 and instead add
SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6. Save the setting.
7. Create a Material Master and check whether in Screen Foreign Trade - Import, Excise related
subscreen appears.

Back to ERP Operation Home.

Transaction Codes for India


Transaction
Action

J1I2
Prepare a sales tax register

J1I3
Create outgoing excise invoices in batches

J1I5
Update the RG 1 and Part I registers

J1IEX
Incoming Excise Invoices (central transaction)

J1IEX_C
Capture an incoming excise invoice (excise clerk)

J1IEX_P
Post an incoming excise invoice (excise supervisor)

J1IF01
Create a subcontracting challan

J1IF11
Change a subcontracting challan

J1IF12
Display a subcontracting challan

J1IF13
Complete, reverse, or recredit a subcontracting challan

J1IFQ
Reconcile quantities for subcontracting challans

J1IFR
List subcontracting challans

J1IH
Make a CENVAT adjustment posting

J1IIN
Create an outgoing excise invoice

J1IJ
Assign excise invoices to a delivery for sales from depots

J1INJV
Adjust withholding tax Item

J1INREP
Reprint a withholding tax certificate for a vendor

J1IQ
Year-End Income Tax Depreciation Report

J1IR
Download register data

J1IS
Process an excise invoice (outgoing) for other movements

J1IU
Process exemption forms

J1IW
Verify and post an incoming excise invoice

J1IX
Create an incoming excise invoice (without reference to purchase order)

J2I8
Transfer excise duty to CENVAT account
J2IU
Remit excise duty fortnightly

J2I9
Monthly CENVAT return

J1IG
Excise invoice entry at depot

J1IGA
Create additional excise entry at depot

J2I5
Extract data for excise registers

J2I6
Print excise registers

CIN Configuration
1.1 Maintain Excise Registration
à Logistics general à SAP Ref. IMG àSPRO Maintain Exciseà Basic setting àIndia àtax on Goods Movements
Registrations

1.2 Maintain Company Code Settings


àSPRO Basic settingàIndia à tax on Goods Movementsà Logistics general àSAP Ref. IMG Maintain Company
Code Settingsà

1.3 Maintain Plant Settings


tax on Goodsà Logistics general à SAP Ref. IMG àSPRO Maintain Plantà Basic setting àIndia àMovements
Settings

1.4 Maintain Excise Groups


SAP Ref. IMGàSPRO Maintainà Basic setting àIndia à tax on Goods Movementsà Logistics general à Excise
Groups

1.5 Maintain Series Groups


SAPàSPRO à Basic setting àIndia à tax on Goods Movementsà Logistics general àRef. IMG Maintain Series
Groups

1.6 Maintain Excise Duty Indicators


tax on Goodsà Logistics general à SAP Ref. IMG àSPRO Maintain Excise Dutyà Basic setting àIndia
àMovements Indicators

1.7 Maintain Subtransaction Type with Text


àIndia à tax on Goods Movementsà Logistics general à SAP Ref. IMG àSPRO Maintain Subtransaction Type
with TextàBasic setting

1.8 Determination of Excise Duty


taxà Logistics general à SAP Ref. IMG àSPRO Select Tax Calculationà Determination of Excise DutyàIndia
àon Goods Movements Procedure

1.9 Maintain Excise Defaults


SAP Ref.àSPRO Determination of ExciseàIndia à tax on Goods Movementsà Logistics general àIMG
Maintain Excise DefaultsàDuty
1.10 Condition-Based Excise Determination
tax on Goodsà Logistics general à SAP Ref. IMG àSPRO Define Tax Code forà Condition-Based Excise
DeterminationàIndia àMovements Purchasing Documents

1.11 Condition-Based Excise Determination


tax on Goodsà Logistics general à SAP Ref. IMG àSPRO Assign Tax Code toà Condition-Based Excise
DeterminationàIndia àMovements Company Codes

1.12 Classify Condition Types


SAPàSPRO Condition-BasedàIndia à tax on Goods Movementsà Logistics general àRef. IMG Classify
Condition TypesàExcise Determination

1.13 Maintain Chapter IDs


tax on Goodsà Logistics general à SAP Ref. IMG àSPRO Maintain Chapter idsà Master dataàIndia
àMovements

1.14 Assign Users to Material Master Screen Sequence for Excise Duty

àSPRO à Master dataàIndia à tax on Goods Movementsà Logistics general àSAP Ref. IMG Assign Users to
Material Master Screen Sequence for Excise Duty

1.15 Specify Excise Accounts per Excise Transaction


tax on Goodsà Logistics general à SAP Ref. IMG àSPRO Specify Excise Accounts per Exciseà Account
determinationàIndia àMovements Transaction

1.16 Specify G/L Accounts per Excise Transaction


tax on Goodsà Logistics general à SAP Ref. IMG àSPRO Specify G/L Accounts per Exciseà Account
determinationàIndia àMovements Transaction

1.17 Incoming Excise Invoices


SAPàSPRO BusinessàIndia à tax on Goods Movementsà Logistics general àRef. IMG Incoming Excise
InvoicesàTransactions

1.18 Define Processing Modes Per Transaction


à Logistics general à SAP Ref. IMG àSPRO Define Processing Modesà Business TransactionsàIndia àtax on
Goods Movements Per Transaction

1.19 Define Reference Documents Per Transaction


tax on Goodsà Logistics general à SAP Ref. IMG àSPRO Define Reference Documents Perà Business
TransactionsàIndia àMovements Transaction

1.20 Maintain Rejection Codes


SAPàSPRO BusinessàIndia à tax on Goods Movementsà Logistics general àRef. IMG Maintain Rejection
CodesàTransactions

1.21 Specify Which Movement Types Involve Excise Invoices


Logisticsà SAP Ref. IMG àSPRO Specify Whichà Business TransactionsàIndia à tax on Goods
Movementsàgeneral Movement Types Involve Excise Invoices

1.22 Outgoing Excise Invoices


tax on Goodsà Logistics general à SAP Ref. IMG àSPRO Assignà Outgoing Excise Invoices à Business
TransactionsàIndia àMovements Billing Types to Delivery Types
1.23 Maintain Default Excise Groups and Series Groups
à Logistics general à SAP Ref. IMG àSPRO à Outgoing Excise Invoices à Business TransactionsàIndia àtax on
Goods Movements Maintain Default Excise Groups and Series Groups

1.24 Subcontracting Attributes


tax onà Logistics general à SAP Ref. IMG àSPRO Subcontracà Subcontractingà Business TransactionsàIndia
àGoods Movementsting Attributes

1.25 Maintain Movement Type Groups


àSPRO BusinessàIndia à tax on Goods Movementsà Logistics general àSAP Ref. IMG Subcontractingà
SubcontractingàTransactions Attributes

1.26 Utilization Determination


SAPàSPRO BusinessàIndia à tax on Goods Movementsà Logistics general àRef. IMG Utilization
Determinationà UtilizationàTransactions

1.27 Specify SAPscript Forms


tax onà Logistics general à SAP Ref. IMG àSPRO Specifyà Excise Registersà Business TransactionsàIndia
àGoods Movements SAPscript Forms

1.28 Number Ranges


SAP Ref. IMGàSPRO Numberà ToolsàIndia à tax on Goods Movementsà Logistics general à Ranges

1.29 Message Control


à SAP Ref. IMG àSPRO Messageà ToolsàIndia à tax on Goods MovementsàLogistics general Control

Vendor Master Tables

Vendor Master (General Section) LFA1

Vendor Master (Company Code) LFB1

Vendor master (VAT registration numbers general LFAS


section)

Vendor master (dunning data) LFB5

Vendor Master (Bank Details) LFBK

Vendor master record (withholding tax types) X LFBW

Vendor master record purchasing organization data LFM1

Vendor Master Record: Purchasing Data LFM2

Vendor Subrange WYT1

Vendor Sub Range Description WYT1T

Partner Functions WYT3

Customer Master Tables


General Data in Customer Master KNA1

Customer Master (Company Code) KNB1

Assign customer credit card VCKUN

Customer Master Contact Partner MASSKNVK

Customer master record sales request form MASSKNVD

Customer Master Sales Data KNVV

Customer Master Partner Functions KNVP

Customer Master Licenses KNVL

Customer Master Tax Indicator KNVI

Customer Master Unloading Points KNVA

Customer master credit management: Control area KNKK


data

Customer master credit management: Central data KNKA

Customer Master: Legal Control Sanctioned Party List KNEX

Customer Master (Bank Details) KNBK

Customer master (dunning data) KNB5

Customer master (VAT registration numbers general KNAS


section)

Material Master Tables

General Material Data MARA

Material Descriptions MAKT

Plant Data for Material MARC

Material Valuation MBEW

Storage Location Data for Material MARD

Units of Measure for Material MARM

Sales Data for Material MVKE

Forecast Parameters MPOP

Planning Data MPGD_MASS

Tax Classification for Material MLAN


Material Data for Each Warehouse Number MLGN

Material Data for Each Storage Type MLGT

SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for
excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15
release levels required for a client according to his Business needs then in this case initial 7 codes are
customised and remaining 8 release codes are configured in the system.

Release procedure is of two types

• Release Procedure without classification

This procedure is applicable only for Purchase Requisitions.

Here PR is released Item by Item only.

• Release Procedure with classification

This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract and scheduling


agreements.

Item by Item and Header level releases can be configured

For PR - both item by item and Header level release can be configured

For external purchasing documents - Release is possible only at Header level.

Step 1:

Create Characteristics

In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For
example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and
Purchasing group

1) Total value of PR more than Rs 50,000

create characteristic as "Release_PR_total_value" in transaction code CT04.

Tab - Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency eg.
INR or USD"

Tab -values key in > 50000 INR

Tab - Additional Data- Table Name "CEBAN" and Field Name "GSWRT"

Tab - Restrictions - class type - 032 - Release strategy

2) Plant
Create characteristic "Release_PR_plant" 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 name CEBAN and Field Name is WERKS.

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 symbol create 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 CLASSIFICATION data or later you can directly mainatain 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 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 user’s 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