Pricing Procedure Technique

Hello Forum Contributor,
Can i have both tax included and tax excluded in the same pricing procedure at sales order?
Please find my scenario as below:
Selling Price          - $12 ($7 + $5) (Card Value Loaded + Cost Price)
Card Value Loaded  - $ 7 (no tax)
Cost Price          - $ 5 (7% tax included into amount)
Service Charges      - $ 5 (7% tax to be calculated from amount)
Commission          - $ 5 (7% tax to be calculated from amount)
How can i set in the system so that it will only take tax from $5 out of the $12 in Selling price? Since Card Value Loaded is not taxable but Cost price is taxable?
Please advise. Thanks.

Dear Lee,
When you maintain your Tax condition type, under Scales - mention B (Value scale) in Scale Basis.
Then while maintianing your condition, enter scales. where you do the setting so that system would calculate Tax only on amount above 7 $.
Hope this helps...
Reward if useful...
Thanks,
Jignesh Mehta
Mumbai
+91 98700 10230

Similar Messages

  • Pricing procedure(Condition technique)

    Hi All
    Can someone provide me all the configuration steps in pricing procedure in MM...

    Select the pricing procedure which is the standard and copy it and create our own pricing procedure.
    Highlight it and double click the Control icon in the LHS screen.
    We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.
    The detail description of each column is given below.
    Step:
    Number that determines the sequence of the conditions with in a procedure.
    It indicates the position of the condition type in pricing procedure.
    Ex.: 10, 15 etc.
    Counter:
    System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
    Access number of the conditions with in a step in the pricing procedure.
    During automatic pricing, the system takes into account the sequence specified by the counter.
    Condition Type:
    It represents pricing element in pricing procedure as a base price, discount, freight and tax.
    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.
    Ex.: PR00 - Price
    K004 - Material Discount
    K005 - Customer/Material Discount
    K007 - Customer Discount.
    Description:
    System copies description of condition type from its description (V/06).
    From and To:
    1.From: This can be used as a base to the condition type for calculating further value.
    1.{+}From and To: + The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
    Manual:
    This indicator specifies whether the specific condition type can be determined manually during sales order processing.
    If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
    For Base Price and Taxes, the entry should be automatic.
    For Discounts and Freights, The entry should be manual.
    If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
    If we un-check the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
    Mandatory:
    This indicator specifies that particular condition type is mandatory in the pricing procedure.
    If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
    If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
    Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
    If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
    Statistical:
    This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
    It is used only for information purposes only.
    This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
    This is commonly used for condition types
    SKTO - Cash Discount
    VPRS - Cost (Moving average price/Standard Price).
    Print:
    The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
    Subtotal:
    The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
    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.
    Requirement:
    It is a routine that is written by an ABAP consultant according to the business requirement.
    By defining Requirement in condition technique we can restrict the access of condition type.
    To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
    For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
    This Requirement will ensure that these condition types will appear only during the billing document processing.
    If new Requirements are to be defined we follow the procedure given below.
    Go to T.Code: VOFM. - Maintain Requirements & Formulas
    Click on the "Requirements" in the top menu and then click on "pricing".
    We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
    And we assign the application type like V - Sales/Distribution etc.
    AltCty - Condition formula for alternative calculation type:
    It is again a Routine that is written by ABAP Consultant.
    It is an alternative formula for the condition type that can be used instead of standard formulas.
    For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
    Ex.: 950 0 Profit Margin 11.
    So we assign 11 - Profit Margin.
    If new routines are to be defined we follow the procedure given below.
    Go to T.Code: VOFM. - Maintain Requirements & Formulas
    Click on the "Formulas" and then on the "Condition Values".
    We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
    And we assign the application type.
    AltCBV - Alternative formula for condition base value:
    Formula for determining the condition basis as an alternative to the standard.
    It is again a Routine that is written by ABAP Consultant.
    It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
    Ex.: Freight - KF00.
    Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
    In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
    During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
    Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
    AcyKy - Account Key/ Accrls - Accruals:
    The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
    In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
    ERB Rebate sales deduct.
    ERF Freight revenue
    ERL Revenue
    ERS Sales deductions
    ERU Rebate accruals
    For Ex.,
    For all Price condition types like PR00 etc. we assign ERL - Revenue.
    For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
    For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
    For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
    This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
    This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
    or
    Hi,
    Pricing Procedure in MM
    The steps are:
    SPRO->MM->Purchasing->Conditions->Define Price dertermination process
    1. Define Condition Table:
    2.Define Acces Sequence,
    3.Define Condition Type,
    4.Define Claculatin Schema,
    5.Assign Calulation Schema,Acces Sequence and Condition Type,
    6.Define Schema Group Of Vendor,
    7. Define Schema Group Of Purchasing Organisation,
    8.Assign Schema Group Of Vendor to Purchasing Organisation,
    9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organisation and Calculation Schema.
    10.Assign Vendor to Schema Group Of Vendor (XK02)
    11.Maintain Condition record(MEK1)
    Edited by: MANI ROOPA SD/MM on Apr 17, 2008 8:44 AM

  • Grouping Condition technique in Pricing Procedure

    Hi Guys:
    In PO :            Vendor :  V1       Central Purchasing oranization: C1
    Material             Qty        Plant
    M1                    5000       P1
    M1                    5000       P2
    we have requirement , there ia central purchasing org . which buys material M1 from vendor V1 for two different plants.
    You get a discount from the vendor ( Scaling ) on the Total Quantity (M1) from V1.
    what are the config settings i need to maintain in pricing procedure so that , when creating the PO , it takes combined quantities of M1 into consideration and pull the respective price from Condition record?
    Thanks
    Sweth

    Hi sai
    When you try to put your own  condition types in pricing procedure in cond type  feild by pressing F4 all the available condition types wont get displayed, (by default it gives the no. of hits as 500), so the solution is remove the number of hits and then you can see the all the condition types ( your own created ones also ).
    If useful reward points
    Regards
    Srinath

  • About the pricing procedure of purchasing order

    Hello friends,
    can anyone tell me about the pricing procedure,conditions & texation of Purchase order?
    and hoew to maintain all those term in Customisation?

    The Basic thing is Condition Technique. In which there are 
    1. Access Sequence 2. Condition Record 3. Condition Type 4. Condition Table. 
    A Access Sequence access a Condition Record of a Condition Type in a Condition Table is a  Condition Technique.This is a simple logic 
    Here the Condition Type is very important like PB00, PBXX,RA01 etc. 
    In the background every Condition Type has its own defition means the purpose of the Condition Type  like, is it for Pricing or Percentage, Quntity base, Accrual Feilds etc is to be defined to work this functions.  Normally we use the existing ones without any risk. But some cases, we have to Create a New Condition Types as per the organisation requirement. 
    The Pricing Schema is useful to minimise condition types while mention prices for Vendor on the basis of Pricing Schema which we defined according to organisation requirement. 
    The Pricing Schema means the calculations procedure of Condition Type. 
    Ex.  RA01 - Discoount % is caclulated on PB00 - Gross Price  means 
    RA01 is based on PB00  like that we have to define in the Pricing Schema 
    which makes easy to use in real time. 
    Here PB00 has the Access Sequence - 0002. 
    But RA01 does not have the Access Sequence.Why because it is a dependent on PB00. But both are Condition Types. 
    In the system, by default some standard  Scheme will be there at Vendor Schema Group in the Vendor Master Screen means the standard one is assigned which is very lengthy which may fullfil our requirement. But some cases which may not fullfil our requirement, in such we have to define. 
    For the configuration, I may not able to explain properly through here but will give some idea. 
    Configuration: SPRO - IMG - Material Management - Purchasing - Conditions - Define Price Deternmination Process:
    1. Define Access Sequence 
    2. Define Condition Type 
    3. Defince Calculation Schema:- Here you have to define the Schema - Define Schema group 
    1. Define Schema Group vendor 
    2. Define Pricing Schema group 
    3.  Schema group for Purchase Organisation 
    4. Assign Schema group to Purchase Organisation - Define Schema determination 
    1.define calculation schema for Standard purchase organisation 
    After completion of the Schema Group, we have to assign it to Vendors. 
    Then whenever we use any transaction with this Vendor, the concerned  Schema will work as configured by us. 
    The Pricing in MM is vast because each Condition have its own importance and each Access Sequence have its own importance. So you need not bother about this. First you learn how to define the Calculation Schema through the above.

  • Meaning of coloums in MM Pricing Procedure

    Will you please explain me the meaning and use of foloowing in MM Pricing Procedure
    Statistic, Subtotal, Requirement, Base Type
    Please explian me in detail if possible . I have searched for similar threads earlier but the explanation is 1 line only
    Pls anyone can tell me the exact meaning of subtotals dropdown options ( Just for Example 3,9 ,5 not all)
    Pls anyone can tell me the exact meaning of requrements  dropdown options
    Thanks

    Dear,
    Please find below:
    Statistical:
    This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
    It is used only for information purposes only.
    This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
    This is commonly used for condition types
         SKTO - Cash Discount
         VPRS - Cost (Moving average price/Standard Price).
    Subtotal:
    The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
    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.
    Requirement:
    It is a routine that is written by an ABAP consultant according to the business requirement.
    By defining Requirement in condition technique we can restrict the access of condition type.
    To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
    For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
    This Requirement will ensure that these condition types will appear only during the billing document processing.
    If new Requirements are to be defined we follow the procedure given below.
    Go to T.Code: VOFM. - Maintain Requirements & Formulas
    Click on the "Requirements" in the top menu and then click on "pricing".
    We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests. And we assign the application type like V - Sales/Distribution etc.
    Regards,
    Syed Hussain.

  • Pricing Procedure to be configured for calculating excise

    Hello ,
    I have new pricing procedure to be configured for calculating excise on base value , the procedure is as under
    Base Price                              -
                       X  Amount
    Surface transport                    -
                   Y  Amount.
    Crush Charges                        -
                  Z  Amount.
    Base for Excise Duty               -
                 X + Y + Z
    Excise Duty 10 % on base value i.e X+Y +Z
    Education cess 2%
    Secess              1%
    Net Inclusive of Excise Amount.
    Clean Energy Charges  -
      A
    Freight Charges            -
       B
    Other charges               -
      C
    Net Total          -    ( Net charges inclusive of Excise Duty + A + B + C )
    CST                 2% 0n Net total.
    I need to configure the above pricing procedure with Taxcode with Excise and CST .Request for valuable suggestions.
    Thanks
    Guru.

    Hi,
    To configure pricing procedure we need to following Condition Technique
    1. Create condition table -v/03
    2. Access Sequence - v/07
    3. Condtion Type v/06
    4. Pricing procedurev/08 -
    5. Determination of pricing procedure. ovkk
    Now to create your new pricing procdure you need to create first conditon type to enter in pricing procedure
    You can create new pricing procedure by copying existing one RVAA01 is the pricing procedure given by SAP & then do changes according to your requirement.
    Step - enter no
    counter-
    Condition Type
    FROM & TO - here put counter no to do calculations as per your requirement
    to Make conditon manual /required/staticatl - click as per u r requirement
    Print conditons
    set other fields as per your requirement.
    Hope this will help you.
    You can also search threads for the same also for more infomation.
    Thanks
    Trupti

  • Pricing Procedures MM

    Hi all,
    I have problem identifying the link between the schema group and the pricing procedure. Where is that in SPRO?
    And also, which transaction do i use to maintain the condition records?
    How do i know if the pricing procedure is for PO or for info record? or rather can i actually configure a pricing procedure for info record?
    thanks

    Pricing Procedure :
    In MM module, pricing procedure is used during RFQ and PO creation. Total value of material based on all addition and subtraction like discount, surcharge, tax, freight, etc. In this we are defining pricing procedure and linking to vendor and purchase department through the virtual schemas.
    Following steps for pricing procedure as,
    1. Define conditions.
    2. Define pricing procedure.
    3. Define virtual purchase organization and vendor.
    4. Info Record.
    Customization for Pricing Procedure :
    1. Definition of Conditions :
    /NMEK0-condition type…condition types- definition (define for basic price, net price, discount, surcharge, tax etc.)
    2. Defining pricing procedure :
    /NMEK0- calculation schema-calculation schemas—New entries (Define procedure and put the conditions like formula so that final price will be net price / total value as per company requirement)
    3. Linking pricing procedure to independent condition types.
    /NMEK0-condition type…condition types- definition for position for defined conditions (Enter the defined pricing procedure in the each independent conditions “Pricing Procedure” box)
    4. Defining Schema group for Vendor :
    /NMEK0- calculation schema-schema groups—vendor—New Entries.
    5. Defining Schema group for Purchase Organization--- New entries.
    /NMEK0- calculation schema- schema groups---- purchasing organization--- new entries.
    6. Linking Virtual Purchase Organization to actual Purchase Organization.
    /NMEK0- calculation schema- schema groups----- Assign P.Org. (in actual P.Org, enter virtual P.Org)
    7. Linking Pricing procedure to virtual P.Org and virtual vendor :
    /NMEK0- calculation schema- Determine Schema--- -Standard --- New entries (Enter virtual schema and P.Org. along with pricing procedure)
    8. Linking virtual vendor to actual vendor-- /NXK02 then enter schema group vendor in Purchasing Data )
    9. Info Records (/NME11)---- click on “Purch. Org. data1” and enter condition types and pricing procedure
    What are the steps in pricing determination in MM. Condition, Access sequence and schema:-
    In the SAP MM Pricing is more important. Just yesterday I have completed the Pricing as I am doing the SAPMM now. I can give some light on this Topic, not 100%. After 2 days definitely some more I can share.
    The Basic thing is Condition Technique. In which there are
    1. Access Sequence 2. Condition Record 3. Condition Type 4. Condition Table.
    A Access Sequence access a Condition Record of a Condition Type in a Condition Table is a Condition Technique.This is a simple logic
    Here the Condition Type is very important like PB00, PBXX,RA01 etc.
    In the background every Condition Type has its own defition means the purpose of the Condition Type like, is it for Pricing or Percentage, Quntity base, Accrual Feilds etc is to be defined to work this functions.
    Normally we use the existing ones without any risk. But some cases, we have to Create a New Condition Types as per the organisation requirement.
    The Pricing Schema is useful to minimise condition types while mention prices for Vendor on the basis of Pricing Schema which we defined according to organisation requirement.
    The Pricing Schema means the calculations procedure of Condition Type.
    Ex. RA01 - Discoount % is caclulated on PB00 - Gross Price means
    RA01 is based on PB00 like that we have to define in the Pricing Schema
    which makes easy to use in realtime.
    Here PB00 has the Access Sequence - 0002.
    But RA01 does not have the Access Sequence.Why because it is a dependent on PB00. But both are Condition Types.
    In the system, by default some standard Scheme will be there at Vendor Schema Group in the Vendor Master Screen means the standard one is assigned which is very lengthy which may fullfil our requirement. But some cases which may not fullfil our requirement, in such we have to define.
    For the configuration, I may not able to explain properly through here but will give some Idea.
    Configuration: SPRO-IMG-Material Management- Purchasing- Conditions-Define Price Deternmination Process
    1. Define Access Sequence
    2. Define Condition Type
    3. Defince Calculation Schema:- Here you have to define the Schema
    Define Schema group
    1. Define Schema Group vendor
    2. Define Pricing Schema group
    3. Schema group for Purchase Organisation
    4. Assign Schema group to Purchase Organisation
    Define Schema determination
    1.define calculation schema for Standard purchase organisation
    After completion of the Schema Group, we have to assign it to Vendors.
    Then whenever we use any transaction with this Vendor, the concerned Schema will work as configured by us.
    I think this will help you. Actually the Pricing is a vast. Becuase each Condition have its own importance and each Access Sequence have its own importance. So you need not bother about this. First you learn how to define the Calculation Schema through the above.
    Here we can create many Calculation Schemas which can assign one schema to Local vendors
    another schema to out side vendor one more schema to foreign vendors like that we can classify.
    hope this will clear ur doubt.Definitely it will help you something.
    Reward the points

  • Pricing Procedure in Delivery Document- SD

    Hi Friends
    Its Ravi again. In general pricing procedure. RVAA01 the conditions and assignment i know. But in delivery document ( VL01N) How we are getting ZLF001 pricing procedure which has 3 header conditions HB00, HD00 and....... This pricing we can veiw in VL01N screen analysis area.
    So My dought is how this pricing procedure is triggered in delivery document. Where we can do changes. Please tell me in details.
    Reagrds,
    Ravi Chandra.

    Hi Ravi,
    SPRO -> Logistics Execution -> Shipping -> Basic Shipping Functions -> Pricing.
    Like the sales order pricing the same condition technique is used.
    Regards
    Nadarajah Pratheb

  • Pricing Procedure IN STO PO

    Hi,
      Please tell the Procedure to create the Pricing Procedure for the STO Purchase Order. I want to Maintain a Pricing Procedure in STO similar to the standard PO.
    Regards,
    Kapil.

    The Basic thing is Condition Technique. In which there are
    1. Access Sequence 2. Condition Record 3. Condition Type 4. Condition Table.
    A Access Sequence access a Condition Record of a Condition Type in a Condition Table is a Condition Technique.This is a simple logic
    Here the Condition Type is very important like PB00, PBXX,RA01 etc.
    In the background every Condition Type has its own defition means the purpose of the Condition Type like, is it for Pricing or Percentage, Quntity base, Accrual Feilds etc is to be defined to work this functions. Normally we use the existing ones without any risk. But some cases, we have to Create a New Condition Types as per the organisation requirement.
    The Pricing Schema is useful to minimise condition types while mention prices for Vendor on the basis of Pricing Schema which we defined according to organisation requirement.
    The Pricing Schema means the calculations procedure of Condition Type.
    Ex. RA01 - Discoount % is caclulated on PB00 - Gross Price means RA01 is based on PB00 like that we have to define in the Pricing Schema which makes easy to use in real time. Here PB00 has the Access Sequence - 0002. But RA01 does not have the Access Sequence.Why because it is a dependent on PB00. But both are Condition Types.
    In the system, by default some standard Scheme will be there at Vendor Schema Group in the Vendor Master Screen means the standard one is assigned which is very lengthy which may fullfil our requirement. But some cases which may not fullfil our requirement, in such we have to define.
    For the configuration, I may not able to explain properly through here but will give some idea.
    Configuration: SPRO - IMG - Material Management - Purchasing - Conditions - Define Price
    Deternmination Process:
    1. Define Access Sequence
    2. Define Condition Type
    3. Defince Calculation Schema:- Here you have to define the Schema
    - Define Schema group
    1. Define Schema Group vendor
    2. Define Pricing Schema group
    3. Schema group for Purchase Organisation
    4. Assign Schema group to Purchase Organisation - Define Schema determination
    Here assign UB with the STO pricing procedure (RM2000 is the standard one)
    After completion of the Schema Group, we have to assign it to Vendors. Then whenever we use any transaction with this Vendor, the concerned Schema will work as configured by us.
    The Pricing in MM is vast because each Condition have its own importance and each Access Sequence have its own importance. So you need not bother about this. First you learn how to define the Calculation Schema through the above.
    Regards,
    Indranil

  • Requirement in pricing procedure

    whta is the use requirement in pricing procedure?  gurus please explain me briefly?

    Hi Durga,
    Requirement:
    • It is a routine that is written by an ABAP consultant according to the business requirement.
    • By defining Requirement in condition technique we can restrict the access of condition type.
    • To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
    • For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
    • This Requirement will ensure that these condition types will appear only during the billing document processing.
    • If new Requirements are to be defined we follow the procedure given below.
    o Go to T.Code: VOFM. - Maintain Requirements & Formulas
    o Click on the "Requirements" in the top menu and then click on "pricing".
    o We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
    o And we assign the application type like V - Sales/Distribution etc.
    Hope this info has been useful.
    Rgds,
    Aram K.

  • Condition type field when Define Pricing Procedure Determination

    Hello Gurus,
        there is a condition type field when Define Pricing Procedure Determination. what does it mean ?
    Many thanks,
    Frank Zhang

    Here is are the details of various fields while configuring pricing procedure.
    A. STEP
    This indicates the number of step-in the procedure.
    B. COUNTER
    This is used to show a second ministep
    C. CONDITION TYPE
    This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.
    D. DESCRIPTION
    This forms the description of the condition type.
    E. FROM
    This is used to define the progression of the calculation and range of subtotals
    F. TO
    This is used to define the progression of the calculation and range of subtotals
    G. MANUAL
    This function enables to allow the condition type to be entered manually also apart from automatic pickup.
    H. MANDATORY
    This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.
    I. STATISTICS
    This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price
    J. PRINT
    The activation of this function will enable the printing of the values and conditions to the document.
    K. SUBTOTAL
    A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also
    L. REQUIRMENT KEY
    This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.
    M. ALTERNATE CALCULATION TYPE
    This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.
    N. ALTERNATE CONDITION BASE VALUE.
    The 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.
    O. ACCOUNTS KEY
    The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.
    PR00- ERL
    K007/KA00- ERS.
    KF00- ERFu2026u2026u2026u2026.& so On.
    P. ACCRUAL KEY.
    The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.
    Kalpesh

  • Requirment---In Pricing Procedure

    Hi,
    Please explain what is meant by Requirement in Pricing Procedure.
    Explain specifically about 6 and 17 requirement(Cond.exclusion <>'X' and Cash disc.in purch. respectively)
    Will reward.
    Regards

    Requirement:
    It is a routine that is written by an ABAP consultant according to the business requirement.
    By defining Requirement in condition technique we can restrict the access of condition type.
    To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
    For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
    This Requirement will ensure that these condition types will appear only during the billing document processing.
    If new Requirements are to be defined we follow the procedure given below.
    Go to T.Code: VOFM. - Maintain Requirements & Formulas
    Click on the "Requirements" in the top menu and then click on "pricing".
    We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
    And we assign the application type like V - Sales/Distribution etc.

  • Standard Pricing Procedure Control Options

    Hi,
    Need to know the use of columns in control tab of the pricing procedure like: counter,  From & To with an example.
    Say i have 10 - 100 steps ....
    In the 50th step i have From as 10 and To as 40......what will happen for the 50 th step condition value....Also, in the 50 th step you have condition type and condition records are maintained.......
    Regards

    Hi,
    Hope the below reply helps you.
    Step:
    Number that determines the sequence of the conditions with in a procedure.
    It indicates the position of the condition type in pricing procedure.
    Ex.: 10, 15 etc.
    Counter:
    System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
    Access number of the conditions with in a step in the pricing procedure.
    During automatic pricing, the system takes into account the sequence specified by the counter.
    Condition Type:
    It represents pricing element in pricing procedure as a base price, discount, freight and tax.
    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.
    Ex.: PR00 - Price
    K004 - Material Discount
    K005 - Customer/Material Discount
    K007 - Customer Discount.
    Description:
    System copies description of condition type from its description (V/06).
    From and To:
        1. From: This can be used as a base to the condition type for calculating further value.
        2. From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
    Manual:
    This indicator specifies whether the specific condition type can be determined manually during sales order processing.
    If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
    For Base Price and Taxes, the entry should be automatic.
    For Discounts and Freights, The entry should be manual.
    If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
    If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
    Mandatory:
    This indicator specifies that particular condition type is mandatory in the pricing procedure.
    If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
    If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
    Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
    If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
    Statistical:
    This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
    It is used only for information purposes only.
    This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
    This is commonly used for condition types
    SKTO - Cash Discount
    VPRS - Cost (Moving average price/Standard Price).
    Print:
    The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
    Subtotal:
    The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
    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.
    Requirement:
    It is a routine that is written by an ABAP consultant according to the business requirement.
    By defining Requirement in condition technique we can restrict the access of condition type.
    To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
    For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
    This Requirement will ensure that these condition types will appear only during the billing document processing.
    If new Requirements are to be defined we follow the procedure given below.
    Go to T.Code: VOFM. - Maintain Requirements & Formulas
    Click on the "Requirements" in the top menu and then click on "pricing".
    We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
    And we assign the application type like V - Sales/Distribution etc.
    AltCty - Condition formula for alternative calculation type:
    It is again a Routine that is written by ABAP Consultant.
    It is an alternative formula for the condition type that can be used instead of standard formulas.
    For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
    Ex.: 950 0 Profit Margin 11.
    So we assign 11 - Profit Margin.
    If new routines are to be defined we follow the procedure given below.
    Go to T.Code: VOFM. - Maintain Requirements & Formulas
    Click on the "Formulas" and then on the "Condition Values".
    We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
    And we assign the application type.
    AltCBV - Alternative formula for condition base value:
    Formula for determining the condition basis as an alternative to the standard.
    It is again a Routine that is written by ABAP Consultant.
    It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
    Ex.: Freight - KF00.
    Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
    In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
    During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
    Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
    AcyKy - Account Key/ Accrls - Accruals:
    The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
    In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
    ERB Rebate sales deduct.
    ERF Freight revenue
    ERL Revenue
    ERS Sales deductions
    ERU Rebate accruals
    For Ex.,
    For all Price condition types like PR00 etc. we assign ERL - Revenue.
    For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
    For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
    For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
    This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
    This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.

  • Columns in Pricing Procedure

    Hi..
    What is the meaning of this column in the pricing procedure?
    Regds
    Shriniwas

    hi
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erplo/16FieldsDescriptioninPricing+Procedure&
    16 columns - Define Pricing Procedure
    •     Select the pricing procedure which is the standard and copy it and create our own pricing procedure.
    •     Highlight it and double click the Control icon in the LHS screen.
    •     We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.
    •     The detail description of each column is given below.
    <b>Step</b>:
    •     Number that determines the sequence of theconditionswithin a procedure.
    •     It indicates the position of the condition type in pricing procedure.
    •     Ex.: 10, 15 etc.
    <b>Counter</b>:
    •     System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
    •     Access number of the conditionswithin a step in the pricing procedure.
    •     During automatic pricing, the system takes into account the sequence specified by the counter.
    <b>Condition Type</b>:
    •     It represents pricing element in pricing procedure as a base price, discount, freight and tax.
    •     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.
    •     Ex.: PR00 - Price
    K004 - Material Discount
    K005 - Customer/Material Discount
    K007 - Customer Discount.
    <b>Description</b>:
    •     System copies description of condition type from its description (V/06).
    <b>From and To</b>:
    1.     From:This can be used as a base to the condition type for calculating further value.
    1.     {}From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
    <b>Manual</b>:
    •     This indicator specifies whether the specific condition type can be determined manually during sales order processing.
    •     If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
    •     For Base Price and Taxes, the entry should be automatic.
    •     For Discounts and Freights, The entry should be manual.
    •     If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
    •     If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
    <b>Mandatory</b>:
    •     This indicator specifies that particular condition type is mandatory in the pricing procedure.
    •     If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
    •     If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
    •     Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
    •     If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
    <b>Statistical</b>:
    •     This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
    •     It is used only for information purposes only.
    •     This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
    •     This is commonly used for condition types
    o     SKTO - Cash Discount
    o     VPRS - Cost (Moving average price/Standard Price).
    <b>Print</b>:
    •     The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
    <b>Subtotal</b>:
    •     The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
    •     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.
    <b>Requirement</b>:
    •     It is a routine that is written by an ABAP consultant according to the business requirement.
    •     By defining Requirement in condition technique we can restrict the access of condition type.
    •     To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
    •     For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
    •     This Requirement will ensure that these condition types will appear only during the billing document processing.
    •     If new Requirements are to be defined we follow the procedure given below.
    o     Go to T.Code: VOFM. - Maintain Requirements & Formulas
    o     Click on the "Requirements" in the top menu and then click on "pricing".
    o     We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
    o     And we assign the application type like V - Sales/Distribution etc.
    <b>AltCty - Condition formula for alternative calculation type</b>:
    •     It is again a Routine that is written by ABAP Consultant.
    •     It is an alternative formula for the condition type that can be used instead of standard formulas.
    •     For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
    •     Ex.: 950 0 Profit Margin 11.
    •     So we assign 11 - Profit Margin.
    •     If new routines are to be defined we follow the procedure given below.
    o     Go to T.Code: VOFM. - Maintain Requirements & Formulas
    o     Click on the "Formulas" and then on the "Condition Values".
    o     We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
    o     And we assign the application type.
    AltCBV - Alternative formula for condition base value:
    •     Formula for determining the condition basis as an alternative to the standard.
    •     It is again a Routine that is written by ABAP Consultant.
    •     It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
    •     Ex.: Freight - KF00.
    •     Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
    •     In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
    •     During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
    •     Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
    <b>AcyKy - Account Key/ Accrls - Accruals</b>:
    •     The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
    •     In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
    o     ERB Rebate sales deduct.
    o     ERF Freight revenue
    o     ERL Revenue
    o     ERS Sales deductions
    o     ERU Rebate accruals
    •     For Ex.,
    o     For all Price condition types like PR00 etc. we assign ERL - Revenue.
    o     For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
    o     For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
    o     For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
    •     This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
    •     This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
    Reward if USeful
    Thanx & Regards
    Naren..

  • Pricing procedure+TAXINN

    Pl. give me configuration documents on Pricing +TAXINN procedure.
    E mail [email protected]
    Thanks
    Vaibhav

    In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenario's. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself.
    Some info on CIN Configuration (it may not appear as understandable below, but if you check on screen, it will be understood better):
    Country Version India comes with four pricing procedures as follows:
    1. JINFAC (Sales from manufacturing plants)
    2. JINEXP (Export sales)
    3. JINDEP (Sales from depots)
    4. JINSTK (Stock transfers
    CIN:
    IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings >
    Maintain Excise Registrations
    Use
    In this IMG activity, you maintain the data relating to your excise registrations.
    Enter each of your excise registrations, specifying a four-character code for each Excise Registration IDs
    In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
    Activities
    For each excise registration in your business create a registration ID, and state:
    1. Which taxes the registration covers (additional excise duty, special excise duty, and cess)Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
    2. The maximum number of items to be printed on each excise invoice
    3. Whether you are allowed partial CENVAT credits
    Maintain Registration ID NUMBER, Excise code number, excise registration number
    Excise Registration Number
    A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
    Every entity with an excise registration number is required to keep its own excise books.
    ECC Number
    Specifies the organization's ECC number.
    Excise Registration Number
    A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
    Every entity with an excise registration number is required to keep its own excise books.
    Excise range: Specifies the excise range in whose area the excise registration is located.
    Excise Division
    Specifies the excise division in whose area the excise registration is located.
    Excise Collectorate
    The code of the excise collectorate in whose area the excise registration is located.
    Indicator for confirming AED usage
    Additional Excise duty Percentage. These are leviable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty.
    Example
    Additional Excise duty is leviable in case of textile products, tobacco and sugar.
    Similarly for SED CESS
    Number of Items in Excise Invoice
    Shows the maximum number of line items that the authorities allow per excise invoice.
    This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements.
    This information is used to split the transfer postings' items into multiple subcontracting challans.
    Excise register set description
    Description of the excise registers set.
    Partial CENVAT Credit
    Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account.
    Dependencies
    When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
    This information is also shown when you post the vendor's excise invoice.
    Maintain Company Code Settings
    Use
    In this IMG activity, you maintain the data relating to your company codes.
    Document Type for CENVAT Postings
    It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
    Indicator for providing debit account overwriting
    Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
    Automatic balance Indicator
    Excise year start month
    The calendar month marking the beginning of the excise year
    Use
    This start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
    Excise invoice selection procedure
    Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received.
    Number of excise invoices to be selected
    Indicates the number of excise invoices that needs to be selected in the excise invoice selection.
    Days to be considered for excise invoice selection
    Number of days from document date for excise invoice selection.
    Example
    If the value of this field is 20 and today is 28-03-97. The excise
    invoice selection will show the related invoices only for the
    period 08-03-97 to 28-03-97.
    Document type for TDS FI posting
    Financial accounting document type for TDS posting.
    Document type for FI posting on Utilisation
    Financial accounting document type for TDS posting.
    Indicator for item level excise duty round off
    This indicator is to be used for deciding whether Item level excise duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
    Rounding off of Excise duty for outgoing excise invoice
    You can round off the Excise amount to be paid during an outgoing Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
    Immediate Credit on Capital Goods
    Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts.
    The rest is posted the CENVAT on hold account, for use in the following year.
    CVD Clearing Account
    Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
    Exchange rate type
    Key representing a type of exchange rate in the system.
    Use
    You enter the exchange rate type to store different exchange rates.
    Example
    You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
    Exchange rate type to be used for Export excise duty converts
    When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
    Maintain Plant Settings
    Use
    In this IMG activity, you maintain excise information relating to your plants.
    Plant Settings
    In this activity, you maintain excise information relating to your plants.
    Activities
    For each plant:
    1. Specify whether it is a manufacturing site or a depot.
    2. Assign it an excise registration ID.
    You can assign the same ID to more than one plant, if required.
    Depot
    Indicates that the plant in question is a depot.
    Dependencies
    Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
    Number of goods receipt per excise invoice.
    Multiple GR for one excise invoice, Single credit
    Multiple GR for one excise invoice, Multiple credit
    Maintain Excise Groups
    Use
    In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
    Excise Groups
    In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
    Recommendation
    Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
    If your company has only one set of excise registers, then you need to maintain only one excise group.
    Activities
    1. Create one excise group for each set of registers that you need to keep.
    1. Assign the excise groups to plants.
    2. Maintain whether this Excise group is for a depot or not.
    3. If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
    4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
    5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
    6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
    7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
    8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
    9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock .
    10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
    11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock.
    • Excise Group
    Governs which set of excise registers a business transaction will be included in.
    Following is the relation between excise group, plant and registration.
    Dependencies
    In define excise groups in Customizing.
    Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to.
    At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
    Indicates that the plant in question is a depot.
    Dependencies
    Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
    GR Per Excise Invoice
    Multiple GR for one excise invoice , Multiple credit
    Multiple GR for one excise invoice , Single Credit
    Create Excise Invoice Automatically
    Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
    The excise invoice is created in the background.
    If you want to make use of this function, you must also define the default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
    RG23D Sales Creation and posting option
    RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step.
    If this is not selected then you need to separately do RG23D selection followed by PGI and then RG23D verification and posting.
    If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
    Default excise qty in GR
    If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
    Folio number for depo
    Posting
    If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
    Also we can set indicator for creation of part 1 for:
    Blocked stock
    Stock transport order
    Consignment stock
    Maintain Series Groups
    Use
    In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents.
    Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
    Activities
    1. Define excise series groups based on type of outgoing document
    2. Assign series group to excise registration ID
    3. If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
    4. If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.
    Example
    You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
    No account postings for CENVAT in sales cycle
    No utilization Flag
    If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
    IF the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
    Immediate Utilization of CENVAT
    Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
    If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
    Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
    Maintain Excise Duty Indicators
    Use
    In this IMG activity, you maintain the excise duty indicators.
    IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
    Select Tax Calculation Procedure
    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.
    1. If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
    2. If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
    This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
    We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
    Maintain Excise Defaults
    Use
    In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
    Activities
    If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
    If you use formula-based excise determination, fill out all of the fields as follows:
    1. Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
    2. Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
    3. Specify the conditions in the sales order that are used for excise rates.
    4. Specify the countervailing duty condition type used for import purchase orders.
    See also
    SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
    IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
    Condition-Based Excise Determination
    Use
    When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
    Features
    The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
    Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
    When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
    Activities
    Customizing
    Make the settings in Customizing Basic? India?for Logistics - General, by choosing Taxes on Goods Movements Account? Excise Duties Using Condition Technique and ...?Settings Determination.
    These activities include one activity where you define a tax code for condition-based excise determination.
    Master Data
    Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
    Day-to-Day Activities
    When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
    When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
    Creating Condition Records for Excise Duty
    1. In the command field, enter FV11 and choose .
    2. Enter the condition type that you want to create a condition record for and choose .
    The Key Combination dialog box appears.
    3. Select the combination of objects that you want to create the condition record for.
    On the dialog box, Control Code means "chapter ID."
    So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
    4. Choose .
    5. Enter data as required.
    In the Tax Code field, enter the dummy tax code that you have defined.
    6. Save the condition record.
    Formula-Based Excise Determination
    Use
    When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
    Prerequisites
    In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data?access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.?
    You maintain the following types of data:
    1. Plant master data
    You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone.
    See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
    2. Vendor master data
    For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type - for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry.
    For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
    3. Customer master data
    Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
    Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
    4. Material master data
    Each material is assigned a chapter ID.
    5. Excise tax rate
    For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
    If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
    Activities
    Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
    1. Looks up the customer master data to see what status you have assigned the customer.
    Let's assume you've assigned the customer status 3.
    2. Looks up the plant master data to see what status you have assigned the plant.
    Similarly, your plant has status 2.
    3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indictor is for customer status 3 and plant status 2: It is 7.
    4. The system determines the chapter ID of the ball bearing for the plant.
    Let's assume the chapter ID at plant for the ball bearings is 1000.01.
    5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under status 7.
    Define Tax Code for Purchasing Documents
    In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
    Only carry out this activity if you use condition-based excise determination.
    Activities: Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
    Assign Tax Code to Company Codes
    Use
    In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
    Only carry out this activity if you use condition-based excise determination.
    Classify Condition Types
    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.
    1. For taxes on purchases, use the condition types contained in the tax procedure.
    2. For taxes on sales, use the condition types contained in the pricing procedures.
    Standard settings
    The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
    Use these settings as a basis for your own.
    IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
    Define G/L Accounts for Taxes
    In this IMG activity, you specify which G/L accounts you will use to record which taxes. You have set up G/L accounts for each of the processing keys listed below.
    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.
    1. VS1 (basic excise duty)
    2. VS2 (additional excise duty)
    3. VS3 (special excise duty)
    4. VS5 (sales tax setoff)
    5. MWS (central sales tax)
    6. MW3 (local sales tax)
    7. ESA (service tax)
    8. ESE (service tax expense)
    Specify Excise Accounts per Excise Transaction
    In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
    If you use subtransaction types, enter the accounts for each subtransaction type as well.
    Activities
    Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
    The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
    Example
    Excise TT DC ind Account name
    GRPO CR CENVAT clearing account
    GRPO CR RG 23 BED account
    GRPO DR CENVAT on hld account
    Specify G/L Accounts per Excise Transaction
    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:
    1. Excise group
    2. Company code
    3. 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:
    1. Defined the G/L accounts
    2. Defined the excise groups
    3. Maintained the transaction accounts
    Activities
    For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
    Note
    You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
    Config setting needed to be done in order to get the Excise Details Screen in Material Master.
    Even though this functionality is available in enterprise version, a small config step has to be made in Screen Sequences for Material Master.
    Following document helps you to do this configuration.
    ? Material Master ? Logistics General ?1. Go to IMG Define Structure of Data Screen for each?Configuring the Material master Screen Sequence.
    2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
    3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is "Foreign Trade: Import Data". Select the same and click on Subscreens in the left frame.
    4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view subscreen and ensure that the subscreen is blank.
    5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 - 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
    6. Save the setting.
    7. Create a Material Master and check whether in Screen Foreign Trade - Import, Excise related subscreen appears.
    Reward points if helpful,
    Rewards,
    Archit

Maybe you are looking for

  • How to force password policy requirements on password resets for user accounts reset by the Administrator?

    OS: Windows Server 2008 R2 Enterprise Domain Level: 2008 Forest Level: 2000 We have Domain Administrators in our domain that reset passwords for user accounts, and the passwords the Administrators set them to are not being enforced follow our default

  • Substitution Variable in Security Filter

    Hi, my filter looks like below. Write : @idesc("Accounts"),Oct,"07 10 + 2",@idesc("SiteName") here 07 10 + 2 is the version name which am using. the same version is used in so many security filters. i want to replace this by the substitution variable

  • CD Printing using HP Essential

    I have HP Photosmart D5360, I'm using it for CD printing for years. My OS is Windows 7 64-bit. I downloaded HP Photosmart Essential 3.5, added photos in Library and when I went on Create there is only one option Photo Book. There isn't an option Crea

  • Handling events in a while loop

    In a while loop, I need to stop the loop after a change of state from false to true or true to false or I can do this by detecting a certain string from the serial port. Seems like I should be able to do this simply by using a counter which is edge t

  • Overriding Spark DataGrid item renderer's prepare method - renderer's child is initially null

    I am currently using the 4.12.0 SDK.  I have a Spark DataGrid setup that makes use of an externally-defined itemRenderer: <s:DataGrid id="dgEquipment"             width="100%" height="100%"             doubleClickEnabled="true"             creationCo