Configuration of ZCST & ZVAT For ne pricing procedure

Hi All
I searched the Forum but didnt get the solution so writing to you all , i have created Zpricing procedure now am stuck up how to create or calculate the Taxes in Newly Pricing Procedure , everything working fine i.e basic price discount but taxes is not coming i have created ZCST And ZVAT condtion type too kindly suggest the config .
Thanx

Dear,
Kindly check following setting is there or not,
Configuration Path:
IMG --> SD --> BF --> Taxes
a. Define Tax determination rules
you will have to maintain ZCST and ZVAT against the Country
b. Define regional Codes. Create City code within India - IN
c. Assign Delivering plants for tax determination. Click details button of your plant and mainatain country and city for your plant
d. Define Tax Relevancy of master records For Customer Taxes and Material Taxes
Click on customer Taxes
Maintain Tax category as ZCST and tax class 0,1,2 (Depending on your requirement)
Similarly mainatin it for ZVAT (0,1)
Maintain same classification for Material taxes.
e. Maintain these values in Customer master record and Material master records appropriately.
Now create condition types ZVAT and ZCST, maintain condition records through VK11
Pricing procedure
FROM TO
10 PR00 Price
20 ZCST CST 10
30 ZVAT VAT 10
35 Netprice 10 30
Mainatain Account ting keys accordingly for all the condition types excpt "Netprice" and assign it to concern G/L Account.
Regards
AJIT K SINGH
HAPPY TO HELP U

Similar Messages

What is the procedure for Return Pricing Procedure

Dear Experts,
   Pricing Routine for Return Pricing Procedure To create Return sales order w.r.t billing document without copying the Pricing Procedure. To capture the net price from the Billing document to the Return Sales order .To change the net price to 0.01 based on the scrap item category RSCR in return sales order. please help me out from this issue .Thanks in advance.I'll give you full points.

Dear Experts,
   Dear Experts,
I've been working in an implementation project..I never worked on pricing routines...so please give me any inputs which can help full for me...
To create Return sales order w.r.t billing document without copying the Pricing Procedure.
To capture the net price from the Billing document to the Return Sales order
To change the net price to 0.01 based on the scrap item category RSCR in return sales
     order.
please help me out from this issue
Thanks in advance..
I'll give you full points..

Account document not created Message no. VF062 for the pricing procedure

When I tried to create an invoice I came across this problem of Account document not created Message no. VF062.
I created a pricing procedure with base price,BED,EDU CESS,HIGH EDU CESS ,VAT,CST.
Condtion record was set for each pricing condtion type.
Sale order>delivery->invoice
When invoice was stored i get the message accounting document not created.
After that i changed the condtion class of (BED,EDU CESS,HIGH EDU CESS ,VAT,CST.) from D-tax to B-price.Now the invoice is stored without the messag(accounting document not created).What will be the problem associated with this

i changed the condtion class of (BED,EDU CESS,HIGH
EDU CESS ,VAT,CST.) from D-tax to B-price
Whaterver condition types you have with condition class as D, I am sure, you should have assigned some Account Keys in your Pricing Procedure. Ensure that those Account Keys are appearing in OB40 as otherwise, you will face this issue.
G. Lakshmipathi

Using Field determined in a Condition in another Condition for a pricing procedure

Hi Gurus,
I have a scenario in a pricing procedure as follows:
Cond type ZABC : Determines field HIENR because of the Processing type marked as B for determination based on a field KUNNR ..
I want to use the HIENR determined in the previous access in a subsequent condition type for processing. I want to know if there is any way to do this without coding.
Cond type ZPQR: HIENR is passed as a mandatory field for processing access.

Hello Santosh,
These are two different condition types with two different access sequences. In the pricing procedure, ZPQR follows ZABC, now, i want to use the HIENR determined in access for ZABC as a variable in access for ZPQR .
HIENR >> determined from Access ZABC >> Conditon type ZABC
HIENR should be populated into table ABC table for ZABC access sequence.
HIENR passed as a variable to Access ZPQR >> Condition type ZPQR.
Is there a way to do this without addind code??

Query for MM Pricing Procedure & tax Procedure

Hello,
Can someone advice me on following.
I need one Condition in MM Pricing Procedure : Discount should be reduced after Calculation of Excise duty and Taxes on PO.
Discount should not be calculated for Excise Base amont & or Tax (CST /VAT) base amount.
Calculation
Basic :          100
Freight            20
Subtotal        120 (Excise Base)
Excise duty:   30
Subtotal:       150 ( Tax Base)
Tax   @4%       6
Subtotal        156
Discount         10
Total Price     146
My Requirement is how to add Discount at the Place shown above.
Regards,
Manish

Dear Manish,
                    After subtotal 120 put in subtotal column 7 and after subtotal 156 put 1.
Truly, I was bit surprised to see your first post, now I got the reason what kept you held.
I tell you why this happens.
I believe you are using tax procedure TAXINN. The routine 362 (in tax procedure) has the program which fetches the data from your pricing procedure and on what amount the taxes have to calculated is the value passed into BASB condition type of tax procedure. One should always read the routine 362 in tax procedure with the help of ABAP consultant. This will give you clarity on the concept of calculation. the subtotal field i.e is KZWI plays important role in calculation.
Currently I do not have access to any test system. If you put the subtotal what I have mentioned the result will come.
Another layman tip I am giving you for tax procedure calculation. where ever you are calculating subtotal just give value from 1 to 7 in subtotal column with different combination one by one and see the results, you will have good idea how the system behaves. Say if you put subtotal as 1, the system response will be different from if you give subtotal 4.
Why this is important to understand is when in future if you are going to add any new condition type you will know how the system response is towards the tax calculation.
That is why I suggested you to read the routine 362.
Moreover, if I see your procedure, excise duty, CST and LST should not be calculated on freight charges. Legally this is not correct. Freight charges are in the preview of service tax. In many implementations I came across the similar scenario where the client insisted on the similar procedure. This all happens due to ignorance of client. We have shown the client the official documents as well we also arranged the official meetings with excise commissioners to clear there doubt.
This scenario is usually insisted in the case of freight billed what client says. this is not correct.
Regards
Rajesh

Code for SD pricing procedure for Australia

Dear All,
Can anybody tell what is the standard code for SD Prcing Procedure for australia.

Hi,
Check in V/08, there is not any Standard Pricing Procedure for Australia provided by SAP.
In this case, refer Pricing Procedure 'RVAA01" (Standard)

Pricing Procedure for India

Hi SD Gurus,
I am in US working for MNC having offices in India and other countries. I have to create a pricing procedure for India.
My company does have CIN ( country India) as Add-on to our SAP 4.6C but I donu2019t see any standard pricing procedure for India in there.
Now how to create pricing procedure for India ?
And which latest Service pack SAP 4.6C should be on for Indian Pricing procedure to work properly ? Currently we are on SP # 41.
Thanks,

Dear Manish
Copy the Std procedures mentioned above,rename it & then map/modify it to fit your requirement.
Also, the relevant CIN Configuration & customization settings are to be done for the company code.
Rgds
Sumanth.Gururaj

Pricing procedure determination for complaint document with reference to billing

Hello Guys,
I am configuring complaint process for project purpose and I got stuck. I need to change the pricing procedure which is determined for complaint
document . Right now the pricing procedure is copied from Billing Document for which complaint refers to.
I am searching a place in configuration where I could change the pricing procedure determination for complaint document with reference to billing doc.
Could you please advise where I can find it ?
Thank you in advance!
Br,
Frederic

Hello Frederic,
I would check the following in SPRO:
- CRM
- Basic Functions
- Pricing
- Pricing in the Business Transaction
- Determine Pricing Procedures
Here the pricing procedure depends on sales organization, division, distribution channel, document pricing procedure and and customer pricing procdure.
Best regards,
Thomas Wagner

New pricing procedure for invoice correction

Hi ALL,
We want a new pricing procedure during invoice correction request.
Scenario:When we execute a sales order ,create a delivery & create a billing docuemnt with z@1111 a pricicng procedure.
Now we want to create an invoice coreection with different pricicng procedure Z@0002.
can any one help!!!
Regards,Rajneesh

Maintain a new Document Pricing Procedure in Invoice correction request. This will help in determining new pricing procedure based on assignment in T.Code: OVKK.
Pricing Procedure:
Determination of Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure through T.Code: OVKK. 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.
Configuration of Pricing Procedure:
Step 1:
Condition table (T.Code: V/04): 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 (T.Code: V/07): 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 (T.Code: V/06): 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 (T.Code: V/08): 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 & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): 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 & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): 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. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka
Reward suitable points.

Pricing Procedure Configuration steps with screenshots

Hi,
Can anybody send screenshots as per above said subject.
The main reasion now I am working in implementation project.
If you are able to give your contact no,I will be greatfull to you.
Regards
ramakrishna
9618087321

You can confi. new Pricing procedure and can go for pricing manually or automatic. If you need pricing automatic you have to go for use of Access Sequences and Schema Group of Vendor. You can customize your pricing procedure according to your requirement such as like Domestic, Import and Stock transport.
For the above individually you have to configure Pricing Procedure and the following steps are:
SPRO->MM->Purchasing->Conditions->Define Price determination process
1. Define Condition Table:
2.Define Access Sequence,
3.Define Condition Type,
4.Define Calculating Schema,
5.Assign Calculation Schema, Access Sequence and Condition Type,
6.Define Schema Group Of Vendor,
7. Define Schema Group Of Purchasing Organization,
8.Assign Schema Group Of Vendor to Purchasing Organization,
9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organization and Calculation Schema.
10.Assign Vendor to Schema Group Of Vendor (XK02)
11.Maintain Condition record(MEK1)
After above steps , you can go for create PO in ME21N.
In the case of Import PO, you have to activate Import PO.
SPRO->Materials Management -> Purchasing -> Foreign Trade/Customs ->Control Foreign Trade Data in MM and SD Documents ->Incompleteness Schemas for Foreign Trade Data .
For more check the links:
http://**********************/2008/09/price-determination-process-or-pricing.html
http://www.scribd.com/doc/7149675/Steps-for-MM-Pricing-Procedures
http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
Please refer the following threads
Pricing Procedure for PO
pricing procedure steps reg.,

Pricing Procedure for Indian Customer

Hi Friends,
What will be the structure for indian Pricing Procedure.
What are all the condition types used for indian customers.
And
Condition Types used for Tax for Indian client
Regards,
Kannan M

Dear Kannan,
I will suggest you to visit http://sap-img.com/sap-sd.htm.
There is a separate section on CIN in the link I have given you. Trust me if you go through all the links you will have a fairly good idea of the CIN.
Do let me know in case of any queries.
Hope this helps you.
Regards,
Rakesh

Explain the Pricing Procedure

Hi Friends
Explain how the pricing is determined for an item, starting from the sales order
Discuss the full cycle also make a mention on the Condition type controls, and Maintain pricing procedure controls.
Kindly explain it with an example.
Thanks

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 & Distribution -> Basic Function -> Pricing 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 & Distribution -> Basic Function -> Pricing 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.

Pricing procedure execution...

Hi Folks,
How SAP reads the pricing procedure..
Example
Con.Type      Requirement        Routine
ZSAA            601                     901
ZSAB            602                     902
Doubt 1: -Is system reads this pricing procedure line by line or coulmn by column?, In the debug we noticed it goes column by colmun? why?
Doubt 2: - I want to know the value found for ZSAA during the execution of 602 requirement. Example scenario is if ZSAA is more than 100$ don't execute ZSAB.

Pricing Procedure:
Determination of Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure through T.Code: OVKK. 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.
Configuration of Pricing Procedure:
Step 1:
Condition table (T.Code: V/04): 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 (T.Code: V/07): 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 (T.Code: V/06): 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 (T.Code: V/08): 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 & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): 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 & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): 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. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka
Reward suitable points.

How to design a Pricing Procedure with both MWST and MWSI in it ?

Hi there.
My business requirement dictates that I can have both Tax inclusive(PR01/MWSI) and Tax Exclusive(PR00/MWST) items within a Single Sales Order.
I know that One pricing procedure can only be assigned to 1 Document Type. So,
Has anyone successfully created a Pricing Procedure that incorporates both the MWST and MWSI tax components ? If so, could you post a sample of the pricing procedure in order for me to understand how I should group the discounts/surcharges and reflect the Subtotals, as well as incorporate the MWST and MWSI all within a single Pricing Procedure ? I will also need to include the PR01 and PR00 conditions into the procedure too, right ?
Really really hope someone with the experience, can aid me on this. I cannot find any relevant materials on this matter, both in OSS Sapnotes and within this forum.
regards
Poo

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 & Distribution --> Basic Function --> Pricing 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 & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
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.
Similarly in MM Module we have Pricing Schema.
Regards,
Rajesh Banka
Reward points if helpful.

Pricing procedure and CIN master

Hi MM Gurus,
I need one simple procedure for creating Pricing Procedure.........and ......creating Excise details and relating and can anybody show how the pricing procedure and excise (CIN) is related .
Regards,
Girish.C.M

Hi,
CIN Setting:
Check Calculation Procedure
In this activity, you can check and, if necessary, change existing procedures for tax calculation.
Standard settings
Calculation procedures containing the necessary specifications for the calculation and posting of taxes on sales/purchases have already been defined in the standard SAP system for certain countries. Every calculation procedure groups several tax types together into a condition type (for example, output tax or input tax) in the calculation procedure, and determines calculation rules for it.
The calculation procedure determines for which amount the individual condition types are to be calculated. This can be the base amount (total of the expense items and the revenue items) or a subtotal. The entry in column FrmLvl, determines for which amount tax is calculated.
Note
In this activity, the condition types for the check and the possible change provided in the standard system are also displayed. Here, for example, the condition calculation rule, or for which base amount the tax is calculated is determined (= condition type).
Recommendation
If possible, do not change the condition types and calculation procedures provided in the standard system. Only check the standard condition types and calculation procedures regarding whether you can use them for your requirements. If necessary, make changes.
Activities
If you cannot use the standard settings, change the condition types and calculation procedures delivered to meet your requirements.
Procedure (pricing, output control, acct. det., costing,...)
Specifies the conditions that are allowed for a document and defines the sequence in which they are used.
Example
Procedures are used, for example, in the following applications:
· Pricing in sales and distribution
· Applying overhead in Product Costing (costing sheets) and for CO internal orders
· Calculating accrued costs in Profitability Analysis
· Output control (printed confirmations, EDI messages, electronic mail)
· Account determination
· Calculating taxes on sales/purchases
· Calculating accruals in Cost Center Accounting
· Pricing for resource planning
Definition: condition type
Controlling (CO)
A distinction, in overhead calculation, is made between:
· Base condition types, which determine the object for which the overhead is to be calculated
· Overhead condition types, which define the percentage overhead to be applied
In resource planning, a condition type determines the types of resource prices that are stored in the SAP System. These can be absolute or percentage values, for example.
Real Estate Management (RE)
An exact definition of a condition that specifies the amount paid for a specific service.
Condition types include:
· Basic rent
· Advance payment for operating costs
· Pest control
Sales and Distribution (SD)
A characteristic of a condition.
For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
Treasury (TR)
A characteristic of a condition used to classify financial transactions.
Typical examples of condition types are interest, dividends, or full repayment upon maturity. The various parameters specified for the individual condition types determine how the flows are calculated in the cash flow.
Return ->
Definition: condition_type
Condition type
The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Access sequence
With the access sequence you define
· the condition tables used to access the condition records
· the sequence of the condition tables
· which field contents are the criteria for reading the tables
Assign Country to Calculation Procedure
In this activity, you enter the key for the calculation procedure which determines the conditions which are allowed per document and which defines the sequence of the conditions in the document for each country.
Requirements
Each calculation procedure which you enter must contain the necessary specifications for calculating and posting the taxes on sales/purchases. For more information on this, read the chapter "Create calculation procedure".
Activities
1. Assign a procedure for tax calculation to every country with which your company has business dealings.
2. Make sure that the corresponding data for calculating taxes is stored for each calculation procedure which you enter here.
Check and Change Settings for Tax Processing
In this activity you make the necessary specifications for posting taxes. In doing this you specify under a process key the following indicators:
· Tax type
Output tax, input tax, additional taxes, or "not tax-relevant" can be specified as the tax type.
· Nondeductibility of tax amounts
For this, tax amounts are marked as not deductible.
· Posting indicator
Here you specify whether the tax amount is posted separately or distributed to expense or revenue items.
· Tax not relevant to cash discount (Not discount relevant)
This indicator is set only for Canada. If you select it, the system does not take into account the corresponding tax amount when determining the tax base.
Standard settings
Process keys with the most important characteristics for tax amounts have already been set in the standard SAP system.
Recommendation
Do not change the standard settings. Check whether you can use these process keys for your company, making changes only if necessary.
Activities
If you cannot use the standard settings, use new process keys and enter them in your calculation procedure. Do not change the standard SAP process keys.
Note
You must make enhancements to the standard settings if you want to specify a new account key in the "Create calculation procedure" activity. You must create and maintain this key beforehand in the "Settings for tax processing" activity.
Internal processing key
The internal processing keys are used by the system to determine accounts or posting keys for line items which are created automatically.
The processing keys are defined in the system and cannot be changed by the user.
Definition: posting key
Financial Accounting (FI)
A two-digit numerical key that determines the way line items are posted.
This key determines several factors including the:
· Account type
· Type of posting (debit or credit)
· Layout of entry screens
Return ->
Definition: posting_key
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.
Definition: excise registration
Financial Accounting (FI)
An entity in India that is entitled by law to produce any goods liable to excise.
Each entity is assigned its own excise registration number.
Every factory that manufactures excisable goods is required to register separately, so that a business with seven factories requires seven registrations.
Return ->
Definition: excise registration
Maintain Company Code Settings
Use
In this IMG activity, you maintain the data relating to your company codes.
Maintain Plant Settings
Use
In this IMG activity, you maintain excise information relating to your plants.
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.
Definition: excise group
Financial Accounting (FI)
A unit within an excise registration, in India, which keeps its own set of excise records.
Whereas the excise registration reports to the excise authorities, the excise group is a purely internal organizational unit. Each excise group keeps records of all transactions that have to be reported to the excise authorities. When the time comes to present these records to the authorities, the excise registration compiles the information from all of its excise groups.
Return ->
Definition: excise group
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.
Maintain Excise Duty Indicators
Use
In this IMG activity, you maintain the excise duty indicators.
Maintain Postal Addresses
Use
In this IMG activity, you maintain the addresses of various customs and excise organizations that your company deals with.
You use these addresses in the ARE Documents functions. When you create an ARE-1 or ARE-3, you enter the address of the excise department and the customs department involved in the export process. The system then prints their names and addresses on the AREs.
You can then define a default local excise department for each excise group and a default customs department for each series group.
Definition: ARE-1 document
Logistics - General (LO)
A form, in India, that companies have to fill out when they remove excisable goods from their manufacturing plants for export.
The form exempts them from paying excise duty when they remove the goods from their premises.
Return ->
Definition: ARE-1 document
Definition: ARE-3 document
Logistics - General (LO)
A form, in India, that allows companies to sell otherwise excisable goods from their premises without paying basic excise duty. The buyer of the goods must be in possession of a deemed export license.
The ARE-3 states what goods are being removed and which deemed excise license covers it.
Return ->
Definition: ARE-3 document
Maintain Subtransaction Type with Text
Sub Transaction Type
Sub transaction type is used for multiple purposes
Subcontracting:
It determines the subcontracting attributes and determines the accounts for the posting while doing a sub contracting transaction.
Excise removals
Sub transaction type is also used for determining the accounts while doing excise removals.
With in CIN the account determination is based on the transaction type. So normally you can have a single set of accounts for Excise utilization. In case you need alternate account determination for handling various scenarios you can define sub transaction types. The sub transaction types and corresponding account assignments needs to be maintained in CIN customization
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.
Definition: condition-based excise determination
Logistics - General (LO
A method that the system uses of determining excise duty in India.
This method requires you to create condition records for each combination of vendor or customer and material (and possibly other conditions).
When you create a purchasing document, the system calls the tax procedure assigned to India. The tax procedure finds all of the condition records that you have created for that combination of vendor and material.
When you create a sales document, the excise duties and sales taxes are determined by the pricing procedure (not the tax procedure).
Return ->
Definition: condition-based excise determination
Definition: formula-based excise determination
Logistics - General (LO)
A method that the system uses of determining excise duty in India.
This method was used in the Country Version India Add-On and requires you to maintain additional data in the Excise Rate Maintenance transaction, J1ID.
When you create a purchasing document, the system calls the tax procedure assigned to India. Each of the excise duties in the tax procedure has its own condition types, and each condition type is assigned to a formula. This formula instructs the system to calculate the excise duty using the data that you have maintained in the Excise Rate Maintenance transaction.
When you create a sales document, the system determines the excise duties and sales taxes using the pricing procedure (not the tax procedure).
Return ->
Definition: formula-based excise determination
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.
Definition: basic excise duty
Financial Accounting (FI)
The main type of excise duty in India.
It is levied on a wide range of products, for example, foodstuffs, metals, jewellery, leather goods, and machinery.
Return ->
Definition: basic excise duty
Definition: additional excise duty
Financial Accounting (FI)
A form of excise duty, in India, levied on a select range of products, for the most part, textiles.
Return ->
Definition: additional excise duty
Definition: special excise duty
Financial Accounting (FI)
A form of excise duty in India on a limited number of goods, mostly luxury goods, including pan masala, sparkling waters, furs, and yachts.
Return ->
Definition: special excise duty
Definition: cess
Financial Accounting (FI)
In India, a tax on the manufacture of certain products, mostly foodstuffs.
Return ->
Definition: cess
Definition: countervailing duty
Financial Accounting (FI)
A form of excise duty imposed on imports that are subsidized by the country in which they were manufactured.
Countervailing duty (also known as CVD) is intended to make the imports more expensive, thereby redressing any competitive advantage they might have over goods produced locally.
Return ->
Definition: countervailing duty
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.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Deter
Sales Tax Code
The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.
Procedure
For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.
Note
You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
Definition: tax code
Financial Accounting (FI)
A two-digit code that represents the specifications used for calculating and displaying tax.
Examples of the specifications defined under the tax code are:
· Tax rate
· Type of tax (input tax or output tax)
· Calculation method (percentage included or percentage separate)
Return ->
Definition: tax_code
Definition: tax rate
Financial Accounting (FI)
The percentage rate used to calculate the tax amount.
Return ->
Definition: tax_rate
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.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> 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.
Maintain Chapter IDs
Use
In this IMG activity, you maintain the chapter IDs and the corresponding descriptions as per the schedules published by the Central Board of Excise and Customs.
Definition: chapter ID
Logistics - General (LO)
The number given to a material in the schedules of materials published by the government of India.
The schedule lists all materials involved in manufacturing, input materials and output materials alike. It shows how much excise duty is levied on each material.
Each material in the schedule is assigned its own identification code, called "chapter ID."
Example
The schedule contains an entry for ceramic roofing tiles, which are liable to basic excise duty at 16%. The chapter ID associated with these tiles is 6903.10.
Return ->
Definition: chapter ID
Assign Users to Material Master Screen Sequence for Excise D
Use
In this IMG activity, you customize the material master data so that it shows the information relating to excise duty.
Standard settings
Country Version India comes with a screen sequence (IN) that shows the excise duty fields. You have to assign it to each of your users.
Activities
1. Double-click User Screen Reference.
2. Assign all users who need to see the excise duty information to the screen reference IN.
Example
Name Screen Reference
MISHRA IN
Screen Sequence Number
Alphanumeric key identifying the screen sequence. The screen sequence defines the sequence of information units in the material master dialog. A screen sequence is made up of data screens. For information on the screen sequences defined in the standard R/3 system, see the IMG documentation Configuring the Material Master.
Note
When creating a screen sequence, use an alphanumeric key beginning with the letter Y or Z (customer name range). This key cannot subsequently be changed.
Dependencies
You can assign screen sequences to users in the IMG activity Assign Screen Sequences to Users/Material Types/Transactions/Industry Sectors.
Screen reference depending on the user
Grouping of users that determines what screens are displayed in accordance with the user master record when you maintain material master records. It also determines the order in which the screens appear.
Definition: user master record
User and Authorization Management (BC-SEC-USR)
Record that contains important master data for a user in the SAP System.
The user master record contains the assignment of one or more roles to the user. This is how a user menu and the corresponding authorizations for the activities contained in the user menu are assigned to the user. Only users who have a user master record can log on to the system.
Return ->
Definition: user_master_record
Define Form Types
Use
In this IMG activity, you define which form types you want to record in the system. You can only use form tracking for the form types that you enter here.
Example
· Form type: CT3
· Form description: Concessional tax form
· Status: Receive
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 hold 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.
Define Processing Modes Per Transaction
Use
In this IMG activity, you specify which processing modes the user can use in the various Incoming Excise Invoice transactions.
This way, you can tailor the transaction to what your users have to do.
Standard settings
The system comes with three standard transactions relating to the Incoming Excise Invoices function (those that are included in the role SAP_CIN). The processing modes available in these transactions are as follows:
· J1IEX_C
This transaction is for excise clerks: users of this transaction can only capture and display excise invoices.
· J1IEX_P
This transaction is for excise supervisors: they can change, display, cancel, and post excise invoices.
· J1IEX
In this transaction, users can capture and post excise invoices, as well as displaying, changing, and canceling them.
Activities
If the standard settings meet your requirements, do not do anything.
Otherwise, you can adjust the standard settings or you can create your own transactions. To do so:
1. In Maintain Transaction, create a new transaction by making a copy of one of the standard transactions. Give the new transaction a transaction code of your choice.
2. In this activity, enter data as follows:
o Tcode: The transaction code that you have just created.
o Proc. mode: Specify what the users of the transaction will do with the excise invoices.
o Active: Select this indicator to activate the setting.
Example
You might want to create a transaction that only allows users to display excise invoices.
Define Reference Documents Per Transaction
Use
In this IMG activity, you specify for each combination of transaction and processing mode which reference documents you want the users to be able to use.
Activities
If the standard settings meet your requirements, you do not have to do anything.
Otherwise, add the entries that you need to the table: For each transaction, make one entry per combination of processing mode and reference document. Activate each entry for it to work.
Definition: excise invoice reference document
Logistics - General (LO)
A document, in India, that you refer to when you enter an incoming excise invoice.
If you have already posted the goods receipt, you can use the goods receipt document as the reference document. Otherwise, you can use the purchase order (or another purchasing document, such as a be a contract or a scheduling agreement).
Example
In the SAP System, you create a purchase order for 100 bags of sand and send the order to your vendor. Two weeks later, the vendor delivers the sand, accompanied by an excise invoice.
When you enter the excise invoice in the system, you specify the number of the original purchase order: this is the reference document.
Return ->
Definition: excise invoice reference document
Maintain Rejection Codes
Use
In this IMG activity, you define the rejection codes that are used in the Incoming Excise Invoices transaction.
Activities
For each rejection code, enter a code and a description. You can also specify whether the excise duty in the invoice is to be posted to the CENVAT on hold account, instead of the CENVAT clearing account.
Specify Which Movement Types Involve Excise InvoicesUse
In this IMG activity, you specify which movement types relating to goods receipts involve excise invoices.
The system uses this information during the goods receipt procedure. When you post a goods receipt using one of the moevement types that you have specified here, the system prompts you to enter the excise invoice number.
Note
This option cannot be used for processing goods receipts without purchase orders.
Maintain Default Excise Groups and Series Groups
Use
In this IMG activity, you specify which excise group and series group you want to appear in these fields by default. You can make separate settings for different combinations of sales organization, distribution channel, division, and shipping point.
Activities
This activity is optional, unless you want the system to automatically create outgoing excise invoices when you create a customer invoice.
In this case, you must also make the appropriate setting in Customizing for Excise Duty, by choosing Basic Subcontracting Attributes
Use
The subcontracting attributes help determine conditions for a combination of an excise group, a transaction type, and a subtransaction type.
The conditions such as the number of excise items per subcontracting challan, if the nonexciseable materials have to be filtered or not when the subcontracting challan is created, the movement type groups for issues and receipts and the hierarchy of determining the excise base value are mentioned here.
Requirements
Before you continue with this activity, work through the following activities:
· Materials Management -> Inventory Management and Physical Inventory -> Goods Issue / Transfer Postings -> Define Screen Layout.
For the movement type 541, maintain the field Purchase Order as an optional entry or as a required entry.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Maintain OutputTypes.
Maintain the output type. On the Default Values tab, maintain the dispatch time and the transmission medium. Maintain the print parameter on the Print tab. This output type has to be maintained in this activity here.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Assign Forms andPrograms.
Maintain the Program, FORM routine, and the form for the output type.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Printer Determination -> Printer Determination by Plant / Storage Location.
Enter the output device that you use.
Settings -> Maintain Excise Groups, and selecting Create EI (Create Excise Invoice Automatically).
Maintain Movement Type Groups
Use
In this IMG activity, you group movement types together to form movement type groups.
Definition: movement type
Inventory Management (MM-IM)
A classification key indicating the type of material movement (for example, goods receipt, goods issue, physical stock transfer).
The movement type enables the system to find predefined posting rules determining how the accounts of the financial accounting system (stock and consumption accounts) are to be posted and how the stock fields in the material master record are to be updated.
Return ->
Definition: movement type
Utilization Determination
Use
In this IMG activity, you specify which CENVAT accounts are to be debited by the Fortnight Utilization of CENVAT report: When the report calculates how much excise duty you must remit, it automatically proposes which CENVAT accounts the duty should be debited to. Here, you specify those defaults.
You can either:
· Debit all the excise duty to one account
· Debit the excise duty to more than one account, in which case you specify which percentage is to be debited to each account
Example
If you want 50% of basic excise duty (BED) to be debited to the RG 23A account and the remaining 50% to the RG 23C account, you would make the following settings:
Acct name BED perc.
RG 23A BED account 50
RG 23C BED account 50
Alternatively, to debit all of the BED to the RG 23A account, and then RG 23C account, if there is not enough in the RG 23A account, you would make the following settings:
Acct name BED perc. +
RG 23A BED account X
RG 23C BED account X
When you come to run the report, the system takes the RG 23A account because it is the first one you have entered. If this account does not cover the BED, the system takes the RG 23C account instead.
Maintain Minimum Balances for Excise Accounts
Use
In this IMG activity, you can maintain minimum balances in your excise accounts. When the balance in these accounts during utilization falls below this level, the system automatically utilizes funds in the PLA account.
Activities
Maintain the minimum balance amount for the excise accounts. If you have more than one excise group, you can maintain different minimum balances.
Specify SAPscript Forms
Use
In this IMG activity, for each of your company codes, you specify which SAPscript forms the system prints the excise registers with.
Standard settings
Country Version India includes a number of sample SAPscript forms and printing programs, which you can use as follows:
Reg. name Lay. no. Form Tcode/Prog
RG 23A Part I 1 J_2IRG23A_PART1 J_2IRAP1
RG 23C Part I 1 J_2IRG23C_PART1 J_2IRCP1
RG 23A Part II 1 J_2IRG23A_PART2 J_2IRAP2
RG 23C Part II 1 J_2IRG23C_PART2 J_2IRCP2
PLA 1 J_2I_PLA J_2IPLA
RG 23 D 1 J_2I_RG23D J_2IRG23
RG 1 1 J_2I_RG1 J_2IRRG1
RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
RT 12 1 J_2I_RT12_3 J_2IRT12
The layout description can be left blank or an appropriate description maybe filled in. You may not change the register name. You can have your own layouts and maintain the name here. If the output device and number of copies are maintained it is automatically picked up for printing.
Number Ranges
You can maintain the number ranges for all CIN Number range objects using this transaction
Activities
Please maintain the number ranges for the folllowing objects The no nr has to be '01' for all
1. j_1iintnum
At an Excise group
1. j_1irg23a1
2. j_1irg23a2
3. j_1iRG1
4. j_1irg23c1
5. j_1irg23c2
6. j_1ipla2
7. j_1iintpr2
8. j_1irg23d
9. j_1irg1_t ( material level)
10. j_1iconpla ( if Consolidated PLA is used )
At Series group
1. j_1iexcloc
2. j_1iexcexp
3. j_1idepinv
4. j_1i57Fc ( 57F Challans )
Rewards if Helpful
regards
rb

Configuration of ZCST & ZVAT For ne pricing procedure

Similar Messages

Maybe you are looking for