Professional Documents
Culture Documents
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.
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
ECC Number
Specifies the organization's ECC number.
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.
This information is used to split the transfer postings' items into multiple subcontracting challans.
This information is also shown when you post the vendor's excise invoice.
The rest is posted the CENVAT on hold account, for use in the following year.
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.
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.
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
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.
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.
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)
Even though this functionality is available in enterprise version, a small config step has to be made
in Screen Sequences for Material Master.
? 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.
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.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
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.
For PR - both item by item and Header level release can be configured
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
Tab - Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency eg.
INR or USD"
Tab - Additional Data- Table Name "CEBAN" and Field Name "GSWRT"
2) Plant
Create characteristic "Release_PR_plant" in transaction code CT04.
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
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:
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.
status- Released, Same classification - check the push button - Warning Message
1.Release_PR_total_value
2.Release_PR_plant
3.Release_PR_PurchasingGroup
step3:
Menu path is
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.
Eg
Approver - Supervisor - R1
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.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
3. Release Indicator:
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
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.
R1 - Supervisor
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.
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.
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
MM-PUR
30316 Problems with fields that are not ready for input in purch.
MM-PUR-GF-ACC
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
MM-PUR-GF-REL
MM-PUR-GF-ARL
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.
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.
It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
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.
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.
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