In Pricing Procedure to Calulate Taxes on subtotal = price+ Freight+   ---

Hello Champions,
I have an issue, while applying taxes on custom Pricing Procedure,   The Scenario is to apply TAX on a sub total, It contains costFreightMiscellaneous expenses + --- XXXX etc,. ,  I have to collect 10% on the subtotal amount. Is there anyway in SAP to find 10% Tax on subtotal amount.will anyone guide me?.  If it needs user exit will you guide me the procedure.  It will be of great help.
  Full points for the solution.

Hi PV
You can go for Alt calc type ,there we can write, the requirement what we need and that has to be put in the subtotal table
Reward if useful
Regards
Srianth

Similar Messages

  • How to copy Value of fright from pricing procedure to the tax procedure

    Dear All,
    Please note, I have a condition type in Pricing procedure i.e. ZRCO-this is for fright which will be added by the user in the PO.
    I want to copy the same value to  ZRC1 which is a condition type in tax procedure.
    Kindly advise, is there any way we can do this automaticaly. My requirement is to add the fright to the gross price while caluclating the VAT in tax procedure.
    Rgds,
    Raghavendra N N

    Hi,
    There is a Field for Manual entries in configutration for Conditions : Condition Types.
    Manual Entries Indicator which controls the priority within a condition type between a condition entered manually and a condition automatically determined by the system.
    Make the following entries according to your requirements:
    _: No limitations
    A: Freely definable
    B: The automatic entry has priority. If a condition record exists, the condition cannot be entered manually.
    C: The manual entry has priority. When you enter the condition manually, the system does not check whether a condition record exists.
    D: Cannot be processed manually
    Hope this will help.

  • In Pricing Procedure PO is created the lowest  price has to  be picked

    Hi All,
    In Pricing procedure there is price for material in outline agreement, inforecod and material specific price, my client want when a PO is created the the lowest  price has to  be picked.
    Kindly let me know the process for the issue hope to hera back from you all u2026..
    Thanks&Regards,
    Chand

    Hi Pherasath,
    I know price will be picked from inforecord but my clients want price which is the lowest one from outline agreement, material specific price, and inforecord.
    for example the material price is in out line agreement-15, inforecord price 16, and material spefic price-13,
    whaen we create a PO price should be the lowest price i.e 13 this my requirment...
    hope you understand........
    hope to hear back from you all
    Thanks&Regards,
    Chand

  • How to make priceing procedure in outgoing tax

    hi
    Please explian step by step how to make the pricein procedure in outgoing tax

    Welcome to the forum.  Before posting any question, you should search the forum to find out whether it has already been answered.  Also please try to post your query with some clarity.
    thanks
    G. Lakshmipathi

  • Tax Problem in pricing procedure

    Hi,
    I define the pricing procedure to sell material.
    In the pricing procedure:
    1- First I define sales price
    2- Discount (condition subtotal = A)
    3- and Output Tax / subtotal (condition subtotal = 2)
    but when create sales order, system only calculate the sales price, and it did not calculate discount and Tax in the net value.
    I want to know that Is it some configuration remained that I forgot?
    Thanks.

    Hi Lida,
    There is nothing wrong with your procedure, nor with your calculation. It's just that on the basis of Price, discounts and rebates you calculate Net Price and on the basis of Net Price and Tax you calculate Total Price.
    For Ex :
         ZPR0     Price- Test     1,500.00      INR     1     EA     1,500.00
         Gross Value     1,500.00      INR     1     EA     1,500.00
    ZTK3     Promo Discount % 3-T     3.000-     %                    45.00-
         Discount Amount     45.00-     INR     1     EA     45.00-
         Rebate Basis     1,455.00      INR     1     EA     1,455.00
         Net Value for Item     1,455.00      INR     1     EA     1,455.00
         Net Value 2     1,455.00      INR     1     EA     1,455.00
         Net Value 3     1,455.00      INR     1     EA     1,455.00
    ZZWR     Down Pay./Settlement     0.00      INR                    0.00
    ZTST     Output Tax-Test     2.000      %                    29.10
         Total     1,484.10      INR     1     EA     1,484.10
    SKTO     Cash Discount     0.000      %                    0.00
    VPRS     Internal price     980.00      INR     1     KG     980.00
         Profit Margin     475.00      INR     1     EA     475.00
    Rgds
    Ravi

  • MM Pricing procedure VS Tax procedure

    Hi Gurus,
    I have checked many  thread here , but still can not find the answer.
    Tax calculation procedure basically calculate the tax amount based on condition recaord maintained
    (dor tis corresponding Condition type).
    But we also can maintain Condition record for the condition type NAVS  (pricing procedure) that bring tax amout into the pricing procedure of PO).
    My question is why do we have to maintain Tax procedure as well as pricing procedure (regarding tax of course ).
    Cheers Guys
    Julien

    HI
    Basically why we have taxing procedure is that its always country specific that means it can be any vendor selling any material but he has to follow some government regualations whcih is what will be given in the taxing procedure that sholuld be the same for all customers it will be different if the customer is foreign.
    the pricing procedure is where we carry out pricing that is customer specific here we can have different prices for different customers depending on what he buys and ETC.
    hope this clarifies .
    Regards
    Vignesh

  • Pricing Procedure vs Tax Procedure

    Dear all,
    The scenario is as follows
    My company purchase material from a trading company which imports the materials from other countries.
    In PO we have maintained import pricing procedure so that we can take the duties paid by trading company during import.
    We pay duties to the trading company.
    Taxes are also involved in this.
    I have created a pricing procedure for this seperate where there is a line with 'condition value' = total of
    [ Net price of materialCustoms dutyCVD+ECS on CVD + SEC ECS on CVD + AED]
    Now we all know tax should be calculated on this total amount.
    In normal case the Net price will come as the base price for tax calculation  which is here wrong.
    I want this total amount to be the base amount for tax calculation in tax procedure.
    What i need to assign in the pricing procedure against this 'total' so that  it is taken as base amount for tax calculation
    How to do this?
    sapmmlearner

    Hello,
    As per your said scenario:
    My company purchase material from a trading company which imports the materials from other countries.
    In PO we have maintained import pricing procedure so that we can take the duties paid by trading company during import.
    We pay duties to the trading company.
    Taxes are also involved in this.
    I have created a pricing procedure for this seperate where there is a line with 'condition value' = total of
    Net price of materialCustoms dutyCVD+ECS on CVD + SEC ECS on CVD + AED
    Now we all know tax should be calculated on this total amount.
    In normal case the Net price will come as the base price for tax calculation which is here wrong.
    I want this total amount to be the base amount for tax calculation in tax procedure.
    What i need to assign in the pricing procedure against this 'total' so that it is taken as base amount for tax calculation
    My question is if your company and your vendor /supplier (Is a trading company from where you are procuring the materials) are geographically located at the same place (such is within country in same place or within country at different places, etc)
    means, then you should not worry about the Import duty. Because for you, when you procure the goods it should be treated as Inland/Domestic procurement  (by the by your vendor, who is trading company procures materials from Abroad, that is his risk or his duty to pay the Customs duty or Importation clearing charges, etc since he is procuring from outside the country through Import procurement process, so don't worry for that).
    Hence when you order the material through standard PO to your vendor (that is trading company), then Logically it must be Domestic pricing procedure (there is no involvement of import duties, importation, etc), that means system will pickup the Pricing procedure - Domestic - which consists of Gross price, and all other suitable pricing elements which are in currently used in your company (for the vendor) and part from the tax condition elements such as Basic excise duty (BED), SED, AED, Cess, etc... these are not part of the Pricing proceudre, but relevent to the Tax procedure. So which can be arranged in a sequential order for the Tax procedure - TAXINN - which is currently in use from any industry - for calculating the tax amount for the item that you procure from the supplier or vendor. And thats how you (your company) will pay the Duty or tax amount agains the goods that are procured from external source.
    Please note:  the tax caluclation is always based on the Base amount, not on anything else, that is based on the total ordered amount through the PO. And the tax amount is always interm calculated by adopting the suitable tax code in the PO (in item details), provided you have to maintain all these tax condition elements in a Condition records through FV11 t.code. then once the tax code (i.e., Input tax - which is tax on purchases) is adopted for the PO, system will pick all the valid condition records and sum the total tax amount in the PO.
    Maintainaing of condition records is required, because the tax procedure which is a Condition based tax calculation procedure. hence you have to maintian the condition records as you said. Then it will calculate correctly.
    Hope it clarifies,
    Regards,
    Sapsrin

  • How is pricing procedure in MM linked with tax procedure ?

    how do we link a pricing procedure with a tax procedure for a particular vendor material combination?
    eg RM0000 is applied to standard order which contains condition type eg gross price PBXX and tax procedure applicable is Taxinn which contains condition type BASB ...now how is BASB value determined for further tax calculations???

    Hi,
    Whlie createing the tax condition in M/06 you have to check the Condition category It should be D and then the link is mentioning the 352 as calculation type against BASB condition type in tax procedure.
    Warm regards,

  • Pricing procedure for tax

    hi all, i need some help.
    in PO, i used my customized pricing procedure which is ZRBAPO.
    the pricing procedure contain standard price , discount , and freight
    ex :
    price (PBXX) = 100 USD
    disc (ZDIC)   = 10 USD
    freight (ZFRI)  = 20 USD
    total = 110 USD
    standard system use 110 as base amount for tax (tax proc TAXID cond type BASB), but i only want determined base amount only from basic price and discount, which is the value is 90 USD not 110 USD.
    how we achieve that req?
    what's the relationship between pric proc ZRBAPO and TAXID?
    Thanks
    Best Regard,
    Hendry

    Hi Hendry,
    In your customized Pricing procedure ZRBAPO, I suppose the tax condtion type used is "NAVS", pl check what is the "From reference step" that you have defined, it might be the step agaist the Total value of 110 USD,
    Now you make a change in the pricing procedure, make a sub total after price and discount and use that step to calculate the tax condition, this should resolve your issue.
    Regards
    Merwyn

  • Tax calculation in Pricing Procedure

    Hi Guys,
    I have a pricing procedure setup to be modified for calculation of surcharge. The current pricing procedure calculates surcharge based on total price. Needs to change it to calculate on Unit price.How to achieve this?
    Current Setup
    Price    Unit Price      Qty.    Net Price
    PR00       655.55          5       3277.75
    ZSUR = 3277.75*12/100 = 393.33
    Required setup
    Price    Unit Price  Qty.    Net Price
    PR00       655.55          5       3275
    ZSUR = 655*12/100 = 78.666 = 78.67
    Then this should be multiplied with the qty. 78.67*5 = 393.35
    How to achieve this.
    Thanks

    I solved this same issue by doing the following.
    When determining ZSUR, create a Condition formula for alternative calculation type in VOFM.
    calculate the 12% off of the PR00 each price and round this result to 2 decimals. In your example you would get .12 * 655.55 = 78.666 commercial rounded to 78.67, then multiply this rounded result with qty to get your extended amount 78.67 * 5 = 393.35 and put the result in XKWERT for ZSUR.
    With this type of calcualtion you will always get consistant pricing regardless of qty. When you are finished with your formula assign it within config of the pricing procedure on your ZSUR
    line. Hope this helps.
    When calculating .12 * 655.55 , create a working data field and do a 'like' to netpr in your formula:
    eg DATA: ZZEA LIKE KOMP-NETPR. ( netpr is curr dec 2)
    when calculating zzea = .12 * 655.55 since the field is defined as 2 decimal, commercial rounding will be the default calculation(round up if >= .005, down if < .005). So in your example 78.666 = 78.67
    Code looks like(had to deal with floating decimals):
    DATA: ZZEA LIKE KOMP-NETPR.
    ZZEA = KOMP-NETPR * XKOMV-KBETR / 100000.
    XKWERT = ZZEA * KOMP-MGAME / 1000.

  • Subtotal in mm pricing procedure

    Hi All,
    Which sub-total type is used from the pricing procedure to calculate the moving average price of the material?
    Can this value be different from the value that is used for invoice verification?
    I mean, letsay we have an article whose gross price is 10 (PB00)
    Freight is 1 (FRA1)
    Other discounts from the vendor -1 (ZDIS)
    So, is it possible that i say that for my landed cost (moving average price) calculation
    only PB00 + FRA1 sub total is used..
    but for my invoice verification and vendor payable,
    PB00 + FRA1 - ZDIS sub total is used??
    Thanks in advance!
    Regards,
    Waheed

    Hi Jack,
    Thanks for the response.
    I am not sure if I understood your answer to this.
    Are you saying that the sub-total type 5, 6 and 7 are used as the sub-totals relevant for MAP price?
    Regards,
    Waheed

  • Pricing procedure  change the condition value

    Hi,
    My pricing procedure determines the Tax in %basis.Now i have a rewuirement wherein i should be able to enter the amount in AMOUNT COLOUMN in condition tab. This value should be the condition Value for the condition type.
    Now my pricing procedure doesnt allow me to make any changes and the condition type is greyed out. how can i calulate the tax in amount instead of % and be able to enter the value manually?
    Thanks,
    Challa

    Hi Challa,
    Price can be maintained either on percentage basis or on amount basis.
    So you have to make changes in condition type to convert it from percentage to amount.
    Go to IMG u2013 sales and distribution u2013 master data u2013 basic function u2013 pricing u2013 pricing control u2013 define condition type.
    Select maintain condition type from the options.
    Now select your condition type and click on detail.
    Change the calculation type from A (percentage) to B (Fixed amount) and save it.
    Now go to VK11 and maintain the new condition record for that condition type.
    Now create the sales order and go to condition tab and check out the pricing it will be amount.
    Please do this method if you find any difficulty then tell us.
    Regards
    Raj.

  • 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

  • Butter stuff on Pricing Procedure Understanding

    Hi Gurus
    Please help me on Pricing Procedure Understating , Detail functionality of fileds , like   From , To, SubTo, Reqt, Altcty etc.
    Regards\Adnan

    Hello Adnan,
    Pricing –
         Menu path – IMG – sales & distribution – basic functions – pricing – pricing control – define & assign pricing procedures – maintain pricing procedures (V/08).
         A pricing procedure consists of a list of condition types in a defined order, such as price, less discount, plus tax. Some controls exist in the pricing procedure. For example you can specify that a condition type is mandatory; it must have an entry defined either automatically or entered manually.
         The pricing procedure is also used in account determination. This determines the general ledge (GL) accounts to which the prices, discounts and taxes must be posted. The condition types in the pricing procedure are linked to an account key. This key in turn is linked to the GL Accounts. This shows the integration between the pricing in the invoice and the financial accounting module.
         It is suggested to use to the SAP standard pricing procedure RVAA01 to copy and make necessary changes according to the requirement while configuring a pricing procedure. The following is the control data of the pricing procedure in detail –
    1.     Step – this indicates the number of steps in the procedure. The first condition type should be step 10; the second condition type should be step 20 and so on. It is possible to number the steps in the intervals of 1, but it is not suggestible as it may cause inconvenience when changing the procedure in future.
    2.     Condition counter – this is used to show a second mini-step within an actual step. For example, you may have assigned all you freight surcharges to step 100. However there may be three condition types, each representing a different freight surcharge. Thus you can assign a freight condition type to step 100, counter 1; another to step 100, counter 2; another to step 100, counter 3 and so on.
    3.     Condition type – this is the backbone of the pricing procedure. The condition type is the link from the access sequence all the way to the actual condition record. When you enter a condition type, the description field is automatically filled in with the description from the condition type.
         Note: A description without a condition type can be entered for sub-total or total or net price in between the condition types in the control data.
    4.     From & To columns – these are used in two circumstances –
    a)     To define the range for a sub-total – for example, if you want to add up all the condition types from step 10 to step 50; you would enter 10 and 50 in the From and To columns respectively.
    b)     To define the basis for a calculation – for example, if a discount is defined as a percentage, you need to indicate which step must be used as the basis for the calculation. If the calculation must be performed from step 100, you would enter 100 in the From field.
    5.     Conditions determined manually – indicates if the condition type it is assigned to is allowed to be processed automatically or only manually. Conditions, that are given this indicator in the pricing procedure, are only included in determination (price determination, output determination, and batch determination) either if they are entered manually, for example, on the condition overview screen in Pricing or if they are transferred from an external process, such as costing.
    6.     (Note: when assigning the pricing procedure to the sales documents, a condition type is also assigned to it; reason being that the condition type assigned to the sales document here is displayed in the sales document item level which can be manually changed - provided it is indicated while configuring the control data  - conditions determined manually). This feature is more often used in case of costing and output determination.
    7.     Condition is Mandatory – the mandatory column identifies those condition types that are mandatory in the pricing procedure. Mandatory condition types are the sales price or the cost price. If the mandatory condition is missing in the pricing procedure, the system has an error in pricing and the respective sales order cannot be processed.
    8.     Condition is used for statistics - This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value). This can be used to represent the cost price of the material sold.
    9.     Print – determines which descriptions and associated values assigned to a step are printed on a document, such as order confirmation.
    10.     Condition Subtotal - Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored. If the same fields are used to store different condition amounts, the system totals the individual amounts. These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order. These subtotals are used in other areas of the system such as in logistics information system. It is recommended that you assign the subtotal field 4 to the total value in the pricing procedure for Freight.
    11.     Requirement – this column is used to assign a requirement to the condition type. This requirement can then be used to exclude the system from accessing the condition type and trying to determine a value. This can be used to specify that the condition type, a discount, should only be accessed if the customer has a low risk credit group.
    12.     Alternative calculation type - specifies that the system is to use the formula represented in this column as an alternative in finding the value of the condition type, rather than by using the standard condition technique. This can be used to calculate complex tax scenarios. This field is used in obtaining values such as “Net Price”, ‘Profit Margin’ – where there wouldn’t be any access sequence to get the required value. Instead the system calculates net value using the existing amounts and the alternative calculation types. (formula: profit margin = net value – cost price)
    13.     Alternative condition base value – is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value. For example, one can specify a formula that uses a subtotal, such as 4, from the subtotal field; modify it slightly, such as dividing it by 2, and then using the resultant value as a base value for the condition type.
    14.     Account key - Key that identifies different types of G/L accounts. The account key enables the system to post amounts to certain types of revenue account. For example, the system can post freight charges (generated by the freight pricing condition) to the relevant freight revenue account.
    15.     Account key – accruals/provisions - Key which identifies various types of G/L accounts for accruals or provisions. With the aid of the account key, the system can post amounts to certain types of accruals accounts. For example, rebate accruals which are calculated from pricing conditions can be posted to the corresponding account for rebate accruals.
    REWARD POINTS IF HELPFUL
    Regards
    Sai

  • How to update the z-condition type in pricing procedure in a quote

    Hi Gurus,
    I need your help to solve my issue.
    I have created a RFC which will trigger any time there is a CRM Quote/ CRM Order create or change occurs. IN response of the RFC i will get the rate and rate type for the line items .
    When the service  returns with rate value the SAP system will insert this value by inserting z-condition type  in to the pricing structure. The normal pricing function module will then carry the process forward.
    Todo this ,Can i code the RFC call in Order_save badi ,but where can i get the pricing sturcure  data to update the returned rate values in the pricing.
    and also one more thing ,In ecc  I am using the CUCB_GET_CONFIGURATION to get product configurations. for the same which FM can i use in CRM.
    Please reply me ASAP.

    hei,
    you can use field KOMP-KZWI1 - KZWI6 to store your condition type. then it can be used for analysis in SIS.
    if you want to put more than one condition type to field KOMP-KZWI1, go to V/08 (pricing Procedure), put "1" in condition subtotal.
    Best Regard,
    Hendry

Maybe you are looking for