Tick on statistical tab ( MM pricing procedure )

Dear experts,
   Please explain me what is the significance of ticking the statistical tab in MM pricing procedure.
Regards,
Abhijeet

hi
Statistical:
u2022     This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
u2022     It is used only for information purposes only.
u2022     This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
u2022     This is commonly used for condition types
o     SKTO - Cash Discount
o     VPRS - Cost (Moving average price/Standard Price).
http://www.scribd.com/doc/6998819/16-Fields-Description-in-Pricing-Procedure
regards
kunal

Similar Messages

  • The use of Cond type tab in Pricing procedure determination

    Hi Guys,
    In T-code:OVKK we  are doing the pricing procedure determination. But ther is one tab called as :CType(Cond Type) there in that screen after our pricing procedure. Could you please some one tell me what is the use of this cond type and where it's reflecting in SAP.
    Regards,
    Kumar

    Hi,
    It is very useful to avoid Data entry work Pricing Conditiontype for example: PR00.
    Ex:  When your creating Sales order by using Item proposal there may be 100 item
    if you maintain this in OVKK you no need enter the price for each item when ever your process sales order just creat condition record by using VK11 and condition type PR00.
    Proposed condition type for fast entry
    The condition type that the system automatically proposes in the double-line entry screen during sales order processing.
    ProcedureEnter a condition type. If you leave the field blank, the system displays the active price condition during sales order processing.
    ExceptionIf you change a condition manually, this will be displayed in the double-line entry screen.
    Regards,
    MH
    Edited by: Mohammad Minahazoddin on Nov 22, 2010 9:54 AM

  • Statistical conditions in Pricing procedure

    Hi Gurus
    Kindly clarify the doubts
    1. In the sales order header, i want to show the net value along with the tax amount. Not separately.
    2. In priicing procedure, Can the Statistical value be posted to the GL accounts if we assing account keys for the statistical conditions.
    Regards
    Stephd

    Hi,
    1. In the sales order header, i want to show the net value along with the tax amount. Not separately.
    Ans: Let us say, in your pricing procedure, you have Step 10 as Base Price and Step 20 as Tax.
    Now Create Step 30 as subtotal from step 10 to 20 and assign 4 in Calculation Type column. This will give you sub\m of Net value+Tax. I have tried it and it works.
    2. In priicing procedure, Can the Statistical value be posted to the GL accounts if we assing account keys for the statistical conditions.
    Ans: For a condition type that is marked statistical you cannot post to G/L. However, if it is very much necessary as per the business requirement, then in T.Code V/06 for that particular condition type mark the Accruals Check box and assign an account key and do the account determination. This will make the value flow into accounts.
    But then again, my question is, if you want to make a condition type flow into accounts, why do you want to make it statistical? Is it for Royalty config.?
    Check the above solutions and revert in-case you need further assistance.
    Regards,
    Rohan Gudavalli.
    Edited by: Rohan Gudavalli on Oct 21, 2011 11:25 AM

  • Statistical condition in Pricing Procedure

    Hello
    Can you let me know about statistical condition GRWR?
    Whats the use of this condition ?
    Regards

    Hi,
    you need the GRWR to determine the statistical value for the Intrastat.
    Usually you maintain the value with 100% of the net price.
    regards, Paul.

  • Copy Control Different Pricing Procedure same condition statistic

    Hi Guys,
    I have the following issue perhaps someone outhere can support me.
    I have customized a copy control from Sales Order to another Sales Order(Credit Memo). For both sales orders I customized an own pricing procedure determination. For sales order A pricing procedure A is found, for sales order B pricing procedure B is found. That is working fine. Now my problem. The values of my conditions must be copied 1:1 from Sales order A to Sales Order B. In Pricing Procedure B is the same condition as in pricing procedure A only with the difference that this condition is customized in pricing Procedure B as STATISTIC, in pricing procdure A as non STATISTIC
    I tried different settings for pricing type in copy control (VTAA)
    C     Copy manual pricing elements and redetermine the others
    Result: My condition gets determined again but the problem is that now the condition has a negative value.
    G     Copy pricing elements unchanged and redetermine taxes
    Result: Condition is copied 1:1 but also the NON STATISTIC sign is copied from Sales Order A
    I want to copy the value of one conditon from Sales Order A to Sales Order B, but it should be (as customized in pricing procedure B) set in Sales Order B as STATISTIC.
    Thanks for your help,
    Matthias

    Hi,
    I found the solution myself. If you have anytime same problem go to V/08 and tick TSPP for your second pricing procedure.
    Regards,
    Matthias

  • Pricing procedure in billing type

    How can I change pricing procedure in billing type

    Hi,
      Go to Tcode ovkk Transaction code and enter your sales area details(for which sales area you had created this pricing procedure) and customer pricing procedure(you can assign this in by using T.code XD02 sales area data sales tab and pricing procedure) and dcocument pricing procedure,which u had assigned in ur billing doc type(check by using T.code VOFA and go to ur billing type and check in views of account assignment and pricing -
    pricing)

  • How to Change Contract pricing Procedure

    Is there a way after the contract has been created to change the pricing procedure it uses. I know you can do this in the sales order.
    Will reward any help.
    Thanks,
    Richard

    Hi
    Pricing procedure is determined from the customer master(customer pricing group in the sales area tab) + document pricing procedure in the order type + sales area
    So if you want to change the contract pricing procedure, change the document pricing procedure in the contract type you are using.
    And make sure there is a combination maintained for the new document pricing procedure in IMG to determine the pricing procedure in the contract.
    Regards
    Sreekar M

  • Statistical Condition not appearing in Rebate Specific Pricing procedure

    Hi,
    We had recently implemented Rebate Billing in SAP and for the credit notes I had created a new pricing procedure and marked it as 'Special PP' for rebate at Pricing procedure level.
    I am calculating Discount and providing Tax in Rebate Credit Memo.
    My India Tax JIVC and JIVP are based on some statistical conditions ZATS and ZSEB, although I am getting the Tax Condition in the document but for the statistical condition, it says "Condition record exists, but has not been set".
    Kindly suggest what is that I am missing.
    Regards,
    Naveen

    Pls check the validity of your condition type as per the pricing date of the conditon type. The condition record should be valid on the pricing date of the c.type.
    This should solve your problem.
    Reward if this helps.

  • Pricing Procedure is missing in processed CRM-ISA order on Tab "Prices"

    Dear all,
    after creating successfully an order in CRM, it is distributed to R/3 where it gets processed without problems. When I get the order back in CRM the field "Pricing Proc." is empty on Tab "Prices".
    Does anyone have an idea, where to search for the reason ? We are using CRM Internet Sales 3.1.
    Thanks in advance.
    Best regards
    Mirko

    Hi Mirko,
    Check the sales area on the sales organization tab of the replicated order in CRM. Is the sales area is the same that you have assigned to the catalog variant? If both are different then the sales area determination is again taking place on R/3 and in CRM there may not be a pricing procedure assigned for the new sales area.
    If both the sales areas are same then it may be bug in the service pack.
    Regards,
    Paul Kondaveeti

  • Pricing procedure error in Sales Order

    Hi,
    I have made all necessary SD config. setting for pricing procedure creation and determination in Sales orders. But while creating a sales order I am getting an error as "No pricing procedure could be determined as entries are missing in TAble 683v. but I can see the relevant entry in this table. How this error can be rectified. i am unable to procees for sales order creation.

    Hi,
    Check in sales document type - VOV8 Which document price procedure you maintained under transaction flow tab
    Check in customer master which customer master pricing procedure maintained in sales area data >> sales tab >> pricing/statistic.
    Then in pricing procedure determination OVKK maintain
    Sales orgz + Dchl + Div + Document price procedure + Customer price procedure = PRICED PROCEDURE
    Kapil

  • Step number in the pricing procedure

    Hi experts,
    Pls advise the reasons. How to solve them without changing the step number?
    Q1: As long as HM00 is the first step number in the pricing procedure, the value of HM00 cannot be distributed among items.
    Example:
    Pricing procedure:
    step no.         conditon type
    10                      HM00 (statistical)
    30                      NETW (ERL)
    Sales order (HM00 = $100):
    item 1     NETW = 0
    item 2     NETW = $100
    Q2: When putting a conditon type between PR00 & subtotal in the pricing procedure, such as VPRS, the value of subtotal cannot be the same as PR00.
    Example of sales order:
    PR00 (unit price) = $19.95 per 10kg
    VPRS (internal price) = $10 per 1kg
    subtotal = $2 per 1kg
    Request: PR00 = subtotal = $19.95 per 10kg

    hello, cathy.
    i do not have access to my references now, but please allow me to advance a general concept.
    in SAP standard, HM00 is a group condition, and fixed value.  the distribution of this value is controlled by certain logic.  as in other header condition types, distribution of this amount can be based on either the value or quantity contribution of the different sales order items. 
    what serves as the basis for distribution of HM00, i do not recall but i will get back to you on this... or perhaps another consultant can give it sooner.
    as to your second issue, i will try to understand your situation better.  but generally VPRS is statitical and not meant to come between PR00 and the sub-total.  VPRS has a different logic compared to the other condition types, and is intended to return a statistical presentation of profit margin in the condition tabs.  if fact, in pricing procedure RVAA01 you will notice that VPRS is grouped with the other statistical condition types just before the profit margin.
    regards.

  • Pricing Procedure- Handling of VAT

    Hello All
    Need help for designing IMPORT pricing procedure for a specific case (Thailand).
    Our client applies VAT - 7% on total value of the Import PO i.e. at the end.
    Their Pricing Structure is like:
    1 Basic Price
    2 Freight
    3 Insurance
    4 Custom Duty
    5 Surcharge
    6 Excise
    7 Internal Duty
    Net value = (1234567)
    and then
    8 VAT on this Net Value.i.e 7% of (1234567).
    They are paying this 7% directly to government and not to the Foregin Supplier.
    Now this VAT amount is deductable as they are having a VAT return report submitted to the government each month.
    i don't know how to handle this case..so request you all if anybody have idea please help me.
    It is vey urgent...
    Regards
    Yogesh

    Hi Yogesh,
    In our case the requirement is simple.We have defined a tax procedure for african country which only has input and out put conditions on the base amount.
    In PO, we have several conditions (header) for additional costs like freight,demurage,port charges etc and which we have defined as fright conditions.
    The accrual indicator has been ticked and so is the Vendor GR checkbox.
    The reason is that while GR, ALL THESE CONDITIONS WILL BE LOADED ON MATERIAL SO TO HAVE a LANDED COST.
    Now,the requirement in this country is that whatever they receive vide PO incurrs certain % of VAT on basic price of an item + all the additional costs(freight,demurage,port charges).
    As per the tax procedure, it calculates VAT on the BASE amount which does not consider the net price in PO.It considers gross price entered against the material.
    This is the problem.
    If I remove the accrual tick in PO pricing procedure for all the conditions for freight,port charges etc, then those conditions will get added on the basic cost of the material and thus the net price will change accordingly.VAT can then be calculated on this.
    But the problem in this is that the FREIGHT tab at the time of GR does not appear  which does not allow me to consider all these costs at the time of GR.
    I hope you understand our requirement clearly now.
    There is some additional requirement but that can be thought of later.The requirement is that the VAT will differ in % depending on the material in a PO.It means a PO can have items with different VAT %
    Thanks in advance.I hope someone must have tried out this earlier.
    Thanks in advance.
    Regards,
    manOO

  • 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

  • Tax Procedures and MM pricing procedures

    Currently when creating a PO under the invoice tab you can input the Tax code and jurisdiction code.
    The tax code I am using is set up for a Canadian Tax procedure (TAXCAJ).
    The procedure is calling two tax condition types JC1E (GST) and JC1I (PST). They are both condition class D and they are the same accross other statistics but they differ in condition category. JC1E is condition category 1 and JC1I is condition category 2.
    JCIE uses account determination VST while JC1I uses NVV. JC1E needs to be posted to a seperate account as it is partially recoverable.
    The real underlying issue here is that tax condition type JC1I comes accross to teh MM condition tab under NAVS but JC1E does not. I need the value from JC1E to come over to the conditions tab as my PO print is driven by this.
    Any ideas how to get tax condition type JC1E (or its value) over to the conditions tab. I can make JC1E come over with JC1I but i need JC1E seperate. If you need clarification or more information just let me know.

    Hi,
    NAVS condition collects the non-deductible portion of the Tax Code and hence only showing JC1I which is a non-deductible condition type.  The logic behind this is non-deductible tax is part of cost, so for updating the stock account at the time of GR with base value + discounts and other pricing conditions + non-deductible tax, NAVS condition type is being used in PO pricing procedure.  JC1E is a deductible type tax and as not being a part of cost it is not updated in NAVS and hence the stock account at the time of GR.
    If you want all the tax amounts for PO printing purpose, use JEXS condition type and insert this at the last of the pricing procedure with statistical indicator.  Modify your print program to print value against JEXS instead of NAVS.
    regards,
    mallik

  • Import Pricing Procedure-Assesable Value

    Dear All,
    we already having import pricing procedure, now we are adding the assesable value condition in the pricing procedure JASS is the condition which added. All customs duty is calculated properly but at the end we have the conditon of actual price which is basic price + taxes which is not coming properly. after adding the assesable value the actual price is copying the value of assesable value. actual price is statistical and in sub total column 'S - Copy values to KOMP-EFFWR (effective value)' is there. what is the reason it is not calculating the acutal price correctly?
    Thanks in advance
    Ramakant

    hi
    check following
    in ur pricing u have to create following
    JCDB IN: Basic Custom Duty
    JCV1 IN : CVD
    JECV IN : Ed Cess on CVD
    J1CV IN : H&SECess on CVD
    JEDB IN : Ed Cess on BCD
    JSDB IN : H&SECess on BCD
    JADC Additional Duty of Custom
    JCV1, JECV, J1CV and JADC will go to Excise MODVAT Accounts and JCDB, JEDB and JSDB will get loaded on inventory.
    In M/06, for all above conditions, keep following controls;
    Cond. class A (Discount or surcharge) Plus/minus A (Positive)
    Calculat.type A (Percentage)
    Cond.category B (Delivery costs)
    Activate "Currency Conversion" and "Accrual"
    Now for setoff
    maintain the following conditions in excise default settings.
    JCV1, JECV, JADC
    path: spro>logistic general >tax on goods movements>India >basic settings>determination of excise duty >maintain excise defaults >
    along with ur tax procedure maintain these conditions in the specified fields
    JCV1 in CVD condition field.
    JECV in ECS condition field.
    JADC in ACD condition field.
    in case of SECess on CVD, no need to maintain.
    it is hardcode in the standard
    Vendor in GR 2 (Entry always possible)
    Import scenario
    1.Create material master of import goods.
    2. Create vendor master record of import vendor and Customs clearing vendor.
    3. Maintain CIN settings.
    4. Maintain J1id.
    5. Maintain Pricing procedure SAP standard JIMPOR.., maintain required conditions..JCDB, JCV1...
    6.Assign the schema to respective import vendor in purchasing view of VMR.
    7. Create import PO, check in conditions of JCDB, JCV1 the customs clearing vendor(Indian vendor) and percentage is assigned. This can be done by In condition tab select condtion then click on display, then enter.
    Save the PO.
    8. MIRO --Capture Bill Of Entry.(Commercial Invoice No.,).Customs clearing first .Here CVD will b converted to BED.
    9. Capture Excises invoice--D.
    10.MIGO.
    12.Post Excise Invoice.
    13.MIRO...Payment to vendor(import vendor)

Maybe you are looking for