Condition Types and number of decimals

Hi friends,
How can I define condition types and condition taxes with more than two decimals, but the company code currency has two decimals?
Thanks in advance,
Gerardo

Dear Gerardo Castell,
If you change the company code currency it will effect all the currencies, if you want to change the decimals only for the respective condition records there is one possible way.
You multiple the  price amount with 1000 and give this resulted amount in condition records , apart from that change the unit of measures accordingly.
check and revert
Raghu.k

Similar Messages

  • Condition type and calculation schema

    Hi,
    I would need to set up a condition type and set this into a calculation schema.
    The condition type is a kind of tax. (It must be percentage.)
    The tax amount increases the cost, asset value or stock value so the NET amount must be summed up with this tax amount and posted in the GR.
    Please let me know how to set up this condition type and how to set up the calculation scheme so that NET amount and tax amount could be posted in the MIGO.
    When creating a PO line itme with w material I would like to be able to set the NET amount there.
    When lookint at the Condition tab of the line item in the po I would like to see the
    NET amount
    The tax percentage calculated
    The total of these.
    In the MIGO I need to post the total.
    Thanks in advance,
    Agnes

    Hi,
       The option is available with Transportation Management in standard using Multi-dimensional calculation type. As of my knowledge, the full functionality is not available without TM, as there is no option to assign the scale type in MM.
        If you want to map the same scenario in MM without TM, then you may go for development. You may create a new Z table and maintain the kilometers and rate per km for each vendor and ship to party (customer number for the receiving plant). Create custom routine to pull the price (distance * rate per km) from the z table and calculate the total price based on the calculation.
       If the kilometers / route is changeable for each PO, then you may add the distance field in PO.
    Regards,
    AKPT

  • Condition type and amount  in VI01 transaction

    Hi All,
    I want to update condition type and amount  in VI01 transaction.
    process : transaction VI01 --> enter shipment number -->enter
                  then double click on item inside that>it will open new screen for that item> here you can see CONDITION tab...i have to update condition type and amount over there.
    Please suggest me what i suppose to do..as i have tried all user exit but in vain...even badi also

    Hi,
    have u tried these user-exits
    Exit Name           Description
    V54B0001            Shipment costing: Configure pricing
    V54B0003            Shipment Costs Calculation: Determine Rate Type and Currency
    V54B0004            Shipment Cost Calculation: Determine Status
    V54C0001            Shipment costing: Description(s) shipement cost item(s)
    V54C0002            Shipment costing: Create shipment cost sub-items
    V54C0003            Shipment Costs Processing: Determine Invoicing Party
    V54C0004            Shipment Costs Processing: Determine Loc. for Tax Invoice
    V54D0001            Shipment Costing: Determining the Tax Countries
    V54KSFRC            Determining the factors for apportionment of shipment costs
    V54P0001            Extended Function Codes for Shipment Cost Information
    V54U0001            Shipment cost processing: Check whether changes made
    V54U0002            Check shipment costs for completion
    V54U0003            Specification of shipment cost number
    V54U0004            Formatting for update of new objects (shipment costs)
    V54U0005            Updating new objects in shipment cost processing
    V54U0006            Shipment Purchase Order - Header Data Supply
    V54U0007            Shipment Purchase Order - Item Data Supply
    Reward points if useful..
    Regards
    Nilesh

  • Standard Report with Condition Type and Condition Records

    Hello to all,
    Is there any standard report available in which Condition Type and Condition values are displayed in either column or row format? The selection criteria can be either Quotation, Contract, Sales Order, Delivery, Invoice or Billing. Thanks anyways...

    Hi Huzefa,
      Pls check the relevant table where the condition records are stored. then do a query with  that condition table and KONP. say for eg: condn type ZINV,ZMRP gets stored in condition table A821, then combine A821 and KONP, u can input condition type and get the values........................
    go to vk13, display and click on layout, u will able to see the condition table.
    Rgds,
    Anitha J

  • Requirement of creation of new condition types and Account keys tax codes

    Hi,
                   In what all possible scenarios will the requirement to create new Condition types and accont keys arise for the creation of new depreciation keys.
    Thanks
    Raja.
    Edited by: Raja Gopal 345 on Aug 29, 2010 1:06 PM

    Unless you use jurisdiction codes, and no external tax system, for
    example with tax procedure TAXUSJ, there is no validity dates for the
    condition records.  You can see this differnce by comparing the tables
    A003 without jurisdiction codes and A053 with jurisdiction codes.  A053
    contains the extra fields DATBI (key field) and DATAB.  This is the
    standard functionality.
    Please have a look at the following part of note 418582:
    " Changing past percentage rates has to be inhibited in order to avoid
    database inconsistencies. For this reason, the functions which allow you
    to transport time-dependent tax codes with percentage rates from the
    past are not supported."

  • Relationship between condition type and payment term

    Hi,
    I created a purchase order (only 1 item) with with payment term "Within 14 days 2 % cash discount" So a condition type SKTO auto added for the item with discount is 2%.
    can anybody show me the relationship between payment term with the condition type and the IMG T.code to make this relationship?
    Thanks
    Long

    If you go to IMG - MM- Purchasing - conditions- Define price determination process - Define Condition types
    For SKTO the condition category is E- Cash discount
    For this condition type which is defined in the calculation procedure , the system internally derives a percentage from the terms of payment and inserts it in the condition type with the category E

  • Could you check our source? (To determine the PR type and number range)

    Hello.
    We use SRM Server5.5 with Classic Scenario.
    We will use the BADI BBP_SC_TRANSFER_BE to determine the PR type and number range according to your recommend.
    We have two PR type in R/3.
    1) KGPR
    2) KTR1
    As you know that shopping cart has no type. So we add customer field to mapping to R/3 PR type and this field has two values.
    1)     PR01: mapping to KGPR
    2)     PR02: mapping to KTR1
    We will use the method GROUP_RQ to determine the PR type.
    If customer field is PR01, PR type is determined KGPR
    If customer field is PR002, PR type is determined KTR1.
    To determine the PR number range, we will use the method GET_NUMBER_OR_RANGE.
    If PR type is KGPR, Choose the No key 12
    If PR type is KTR1, Choose the No key 16.
    Configuration step:
    1.     Maintain the PR number range in SRM.
    No key: 12  (for KGPR) internal NR
    No range: 2520000000 – 2529000000
    No key: 16 (for KTR1) internal NR
    No range: 2560000000 – 2569000000
    2.     Maintain the PR number range in R/3
    No key: 12  (for KGPR) Ext NR
    No range: 2520000000 – 2529000000
    No key: 16 (for KTR1) Ext NR
    No range: 2560000000 – 2569000000
    3.     Assign the PR number range to PR type in R/3
    KGPR – 12 (EXT)
    KTR1 – 16 (EXT)
    4.     Maintain the attribute in SRM
    Document type in R/3
          Add KGPR and KTR1
    We developed this logic, but it’s not working.
    LOOP AT ct_proc_item INTO ls_proc_item “ Where is no date in ct_proc_item:
    We can not find out the reason.
    Could you check our source?
    METHOD if_ex_bbp_sc_transfer_be~group_rq.
      DATA:
           ls_proc_item           TYPE bbps_procurement,
           lv_number_int          TYPE bbp_item_no,
           ls_item                TYPE bbp_pds_transfer_item,
           lv_group_counter       TYPE numc5,
      CONSTANTS:
          lc_on(1)               VALUE 'X'.
      SORT ct_proc_item BY obj_to_gen.
      CLEAR: lv_group_counter.
    LOOP AT ct_proc_item INTO ls_proc_item  
    where obj_to_gen eq iv_object_to_generate.
    get item data which includes customer fields
        MOVE ls_proc_item-preq_item TO lv_number_int. " convert
        READ TABLE it_item INTO ls_item WITH KEY number_int = lv_number_int.
        IF sy-subrc = 0.
          IF ls_item-pr_type EQ 'PR01'.
            ls_proc_item-doc_type = 'KGRP'.
          ELSEIF ls_item-pr_type EQ 'PR02'.
            ls_proc_item-doc_type = 'KTR1'.
          ENDIF. " lv_cust_field
          lv_group_counter = lv_group_counter + 1.   " increase counter
          ls_proc_item-group_1 = lv_group_counter.
          MODIFY ct_proc_item FROM ls_proc_item
                 TRANSPORTING group_1.
        ENDIF.  " sy-subrc
      ENDLOOP.
      cv_method_active = lc_on.
    ENDMETHOD.
    method IF_EX_BBP_SC_TRANSFER_BE~GET_NUMBER_OR_RANGE.
      if is_item-pr_type = 'PR01'.
         CV_NUMBER_RANGE = '12'.
         CV_NUMBER = '2520000000'.
      elseif is_item-pr_type = 'PR02'.
         CV_NUMBER_RANGE = '16'.
         CV_NUMBER = '2560000000'.
      endif. " is_proc_item / is_item
    Thank you
    Best Regard
    SH

    Hi
    Please find some suitable sample code, which might help you out.
    method IF_EX_BBP_SC_TRANSFER_BE~GET_NUMBER_OR_RANGE .
    * IV_OBJECT_TO_GENERATE
    *   '1' Reservation
    *   '2' Purchase Requsition (BANF)
    *   '3' Purchase Order
    *   '4' Customer Object
    * 1. current item data are in structures
    *    - IS_ITEM shopping cart item data including Customer Fields
    *    - IS_PROC backend relevant item purchasing data
    * 2. accounting data in tables
    *    - IT_ACCOUNT all shopping cart account. data with Customer Fields
    *    - IT_PROC_ACCOUNT backend relevant accounting data for current item
    *  - key criteria between this tables are
    *    - it_proc_account-preq_item
    *                     -serial_no (numc 2)
    *    - guid from is_item
    *    - it_account-p_guid
    *                -accno(numc 4)
    * A) example to use current item data + item customer fields
    *  if is_proc_item-DOC_TYPE = 'ABCD' AND
    *     is_item-<field of CI_BBP_ITEM> = .
    * set own number range
    *  CV_NUMBER_RANGE = .
    ** set own number
    ** .. ==> if initial SAP Standard with no.range will be processed
    *  CV_NUMBER = .
    *  endif. " is_proc_item / is_item
    * B) example to use only proc_account no accounting customer fields
    *data:
    *     ls_proc_account   type bbp_bapipogna.
    *  loop at it_proc_account
    *            into ls_proc_account.
    *    if ls_proc_account-BUS_AREA = '9988'.
    ** set own number range
    *  CV_NUMBER_RANGE = .
    ** set own number
    ** .. ==> if initial SAP Standard with no.range will be processed
    *  CV_NUMBER = .
    *     endif. " ls_proc_account
    *  endloop.
    * C) example to use only accounting customer fields, no other accounting
    *data:
    *     ls_account        type bbp_pds_acc.
    *  loop at it_account
    *            into ls_account
    *            where p_guid = is_item-guid.
    *    if ls_account-<field of CI_BBP_ACC> = .
    ** set own number range
    *  CV_NUMBER_RANGE = .
    ** set own number
    ** .. ==> if initial SAP Standard with no.range will be processed
    *  CV_NUMBER = .
    *   endif. " ls_account
    *  endloop.
    * D) example to use proc_account + customer fields for accounting
    *data:
    *     lv_serial_no      type bbp_bapipogna-serial_no,  " sequence num 2
    *     lv_acc_no         type bbp_pds_acc-acc_no,       " sequence num 4
    *     ls_proc_account   type bbp_bapipogna,
    *     ls_account        type bbp_pds_acc.
    *  loop at it_proc_account
    *            into ls_proc_account.
    *    move ls_proc_account-serial_no to lv_acc_no.
    *    read table it_account
    *         into ls_account
    *         with key p_guid = is_item-guid
    *                  acc_no = lv_acc_no.
    *    if sy-subrc = 0.
    **     if ls_account-<field of CI_BBP_ACC> = .
    ** set own number range
    **  CV_NUMBER_RANGE = .
    ** set own number
    ** .. ==> if initial SAP Standard with no.range will be processed
    **  CV_NUMBER = .
    **      endif. " ls_account
    *    endif. " sy-subrc
    *  endloop.
    endmethod.
    method IF_EX_BBP_SC_TRANSFER_BE~GROUP_RQ .
    * 1. current item data are in structures
    *    - IT_ITEM all shopping cart item data including Customer Fields
    *    - IT_PROC_ITEM backend relevant item data of current log.system
    *    key criteria between this tables are:
    *    - IT_ITEM-NUMBER_INT (numc 10)
    *    - IT_PROC_ITEM       (numc  5)
    * 2. accounting data in tables
    *    - IT_ACCOUNT all shopping cart account. data incl. Customer Fields
    *    - IT_PROC_ACCOUNT backend relevant accounting data for current item
    *  - key criteria between this tables are
    *    - it_proc_account-preq_item (numc 5)
    *                     -serial_no (numc 2)
    *    - is_item-guid
    *             -number_int (numc 10)
    *    - it_account-p_guid
    *                -accno(numc 4)
    constants:
          lc_on(1)               VALUE 'X'.
    * A) example to use only proc_item with NO customer fields
    *         group requisitions by backend document type
    *data: lv_doc_type            TYPE esart,
    *      ls_proc_item           type BBPS_PROCUREMENT,
    *      lv_group_counter       type numc5.
    *    clear lv_group_counter.
    *    clear lv_doc_type.
    *    SORT ct_proc_item BY obj_to_gen doc_type.
    *    LOOP AT ct_proc_item
    *            into ls_proc_item
    *            WHERE obj_to_gen EQ iv_object_to_generate.
    ** new group criteria?
    *      if lv_doc_type ne ls_proc_item-doc_type.     " backend doc.type
    *        lv_group_counter = lv_group_counter + 1.   " increase counter
    *        lv_doc_type      = ls_proc_item-doc_type.       " save criteria
    *      endif.
    *      ls_proc_item-group_1 = lv_group_counter.
    *      modify ct_proc_item from ls_proc_item
    *             transporting group_1.
    *    ENDLOOP.
    * B) example to use item customer fields
    * data:
    *      ls_proc_item           type BBPS_PROCUREMENT,
    *      lv_cust_field          type <field of ci_bbp_item>.
    *      lv_number_int          type BBP_ITEM_NO,
    *      ls_item                type BBP_PDS_TRANSFER_ITEM.
    *    clear lv_group_counter.
    *    clear lv_cust_field .
    *    SORT ct_proc_item BY obj_to_gen.
    *    LOOP AT ct_proc_item
    *            into ls_proc_item
    *            WHERE obj_to_gen EQ iv_object_to_generate.
    ** get item data which includes customer fields
    *      move ls_proc_item-preq_item to lv_number_int. " convert
    *      read table it_item
    *           into ls_item
    *           with key number_int = lv_number_int.
    *      if sy-subrc = 0.
    **       new group criteria?
    *        if lv_cust_field ne 'XYZ'.
    *         lv_group_counter = lv_group_counter + 1.   " increase counter
    *         lv_cust_field = ls_item-<field of ci_bbp_item>."save criteria
    *        endif. " lv_cust_field
    *        ls_proc_item-group_1 = lv_group_counter.
    *        modify ct_proc_item from ls_proc_item
    *               transporting group_1.
    *      endif.  " sy-subrc
    *    ENDLOOP.
    * C) example to use accounting data with customer fields
    *            group requisitions by backend document type
    *data: lv_doc_type            TYPE esart,
    *      ls_proc_item           type BBPS_PROCUREMENT,
    *      lt_account             type BBPT_PD_ACC,
    *      ls_account             type bbp_pds_acc,
    *      ls_item                type BBP_PDS_TRANSFER_ITEM,
    *      lv_number_int          type BBP_ITEM_NO,
    *      lv_account_flag        type c,
    *      lv_group_counter       type numc5.
    *    clear lv_group_counter.
    *    clear lv_doc_type.
    *    SORT ct_proc_item BY obj_to_gen doc_type.
    *    lt_account[] = it_account[].
    *    SORT lt_account BY p_guid acc_no.
    *    LOOP AT ct_proc_item
    *            into ls_proc_item
    *            WHERE obj_to_gen EQ iv_object_to_generate.
    ** get accounting customer fields for this item
    *    clear lv_account_flag.
    ** ..first get item guid
    *    move ls_proc_item-preq_item to lv_number_int.
    *    read table it_item
    *         into ls_item
    *         with key number_int = lv_number_int.
    *    if sy-subrc = 0.
    *      loop at lt_account
    *           into ls_account
    *           where p_guid = ls_item-guid.
    *        if ls_account-<field of CI_BBP_ACC> = .
    *           lv_account_flag = lc_on.
    *        endif.
    *      endloop.
    *    endif. " sy-subrc it_item
    ** new group criteria?
    *      if lv_doc_type ne ls_proc_item-doc_type OR     " backend doc.type
    *         lv_account_flag = lc_on.                    " accounting
    *        lv_group_counter = lv_group_counter + 1.   " increase counter
    *        lv_doc_type      = ls_proc_item-doc_type.       " save criteria
    *      endif.
    *      ls_proc_item-group_1 = lv_group_counter.
    *      modify ct_proc_item from ls_proc_item
    *             transporting group_1.
    *    ENDLOOP.
    * !!!! set flag that BADI was processed
    * .. ==> no SAP Standard grouping will be processed
        cv_method_active = lc_on.
    endmethod.
    Hope this will help.
    Please reward suitable points, incase it suits your requirements.
    Regards
    - Atul

  • Related to condition types and access sequence

    Dear all,
           i want to know abt one scenario, m using a pricing procedure with my service PO: ZVSTOT, in this Procedure, 12 condition types are there, during searching i found tat 3- 4 condition are are using different different access sequence, so i want to know tat in what procedure, we do it, what is use of it.?
    plz reply me.

    Hi Nisha,
    Prcing procedure configured in your service PO PO: ZVSTOT, Based on this pricing procedure system adopted the condition type in PO.
    Please go through this below link to better understanding the MM-Pricing procedure
    http://it.toolbox.com/wiki/index.php/Pricing_Determination_Process_-_MM
    http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
    CONDITIONS OR PRICING PROCEDURE or PRICE DETERMINATION PROCESS
    We deal with the Pricing Procedure for vendors.
    PB00 Gross Price (info record, contract, scheduled Agreement)
    PBXX Gross Price (PO)
    FRA1 Freight
    RA00 Discount on net
    RA01 Discount on Gross
    ZA00 Surcharge on net
    SKT0 Surcharge / discount
    ZPB0 Rebates
    MWVS Input Tax
    MWAS Output Tax
    BASB Base Amount
    RM0000 Calculation Schema or Pricing Procedure
    (PB00 & PBXX)
    RM0002 Calculation Schema or Pricing Procedure
    (PB00)
    PB00 --> AB00
    Copy the Standard one and create new one (ours)
    RM0000 contains all the condition types
    Pricing Procedure (PP)
    We define the pricing procedure to define condition supplement for the material price. The condition supplement specifies the discount, surcharge, freight etc that we want a system every time to access material price condition records.
    The total value of the material is calculated or based on all addition and subtraction i.e. discounts, surcharge, tax freight etc
    Condition Table
    It is a table, which defines the structure of condition record key.
    Condition Record
    It is a data record used to store conditions or condition supplements, i.e. condition like, discount, freight, and surcharge, Tax etc.
    Condition Type
    It is used for different functions. In Pricing the condition types leads you to differentiate different types of discounts, in output determination, batch determination, difference between two output types, such as delivery note or order confirmation, between different strategy types
    Access Sequence
    It specifies the order in which system searches or access the condition records from condition table
    Difference between PB00 & PBXX
    1. Condition maintained in PB00 is time dependent whereas PBXX is time independent.
    2. Condition type PB00 u2013 used for IR, RFQ, Contract, Schedule Agreement
    Condition type PBXX u2013 used for PO.
    Calculation Schema
    The main function of calculation schema is to provide framework of steps for the price determination process to specify the discounts, surcharge, freight rebate etc.
    It also determines the sequence of conditions that are to be followed and in which sequence.
    Schema Group Vendor
    The main function of it is to identify or to pick the right process and conditions for a particular vendor.
    Schema Group Purchasing Organization
    Key that determines which calculation schema (pricing procedure) is to be used in purchasing documents assigned to the relevant purchasing organization.
    Schema Group
    It allows to group together the purchasing organizations, which uses the same calculation schema.
    Steps: -
    1. Create Access sequence
    2. Create condition types
    3. Create pricing procedure or calculation schema
    4. Link pricing procedure & access sequence to condition type
    5. Create schema group for vendor
    6. Create schema group for purchase organization
    7. Assign schema group vendor-to-vendor master record in purchasing data view
    8. Assign schema group purchase organization to our purchase organization
    9. In inforecord purchase organization data enter condition types and pricing or calculation procedure
    CUSTOMIZE SETTINGS: -
    SPRO > IMG>MM>PUR>Conditions -->Define price determination Process
    1. Define access sequence
    2. Define Condition type
    3. Define cal. Schema
    4. Define schema group
    o Schema group vendor
    o Schema group purchasing group
    5. Assignment of schema group to PUR org
    6. Define schema determination à determine cal schema for standard PO.
    With Thanks,
    Thiru

  • How to transfer SRM PO Condition Type and Custom fields to ECC?

    Hi All,
    I have a scenario to transfer SRM Line item condition types and few custom fields to ECC.
    I have found the following things but structure  'CI_EKPODB' does not exists in ECC.
    I am using 'SRM 5.00' and 'SAP ECC 6.0'.
    NOTE: I have to transfer condition records when PO is getting created / modified.
    1) Earlier I was planning to use BADI 'BBP_CREATE_BE_PO_NEW' in SRM and this will transfer the data to ECC in case of PO 
        Creation.
                   It contains the Condition fields to be passed to ECC.
    But i am unable to implement the same, whenever i create implementation when i click 'Activate' its getting activate then after few seconds its getting deactivate, i think this is because this BADI is not allowed for multiple use and SAP has already made one implementation on the same.
    2) I need to implement BADI 'BBP_ECS_PO_OUT_BADI' in SRM and 'BBP_PO_INBOUND_BADI' in ECC.
    SRM BADI will pass verified field details to ECC as a custom fields
           It does not contains the Condition fields to be passed to ECC, so i was planning to pass the same as custom field(s).
    ECC BADI 'BBP_PO_INBOUND_BADI'  will be used to map the fields to correct place and this should work.
    i need to modify the structures and pass all the custom fields (z-fields) - (CI_EKPODB but does not exists kindly suggest) as data.
    Other required details:
          Transfer of PO does not supported by SAP for service PO's, any suggestion on the same?
    Expecting quick reply from your end.
    Thanks in advance.
    Regards,
    Hemant

    Naresh,
    Thanks for quick response.
    My concern is this BADI 'BBP_CREATE_BE_PO_NEW' will trigger only in case of creation, not when PO is changes.
    I have to transfer condition types and custom fields to ECC in both the case (create / change)
    If i have to do this only in case of creation then i can pass Condition types / custom fields then i can use parameter 'CS_PO1_DOCUMENT' from method 'FILL_PO_INTERFACE1'.
    this parameter contains 'IT_POCOND', 'IT_POCONDX' and 'IT_EXTENSIONIN' as parameter  so my problem will be solved.
    But i dont think this will trigger in both the cases and 2nd thing i cann't implement the BADI since its not marked for multiple use so i am unable to implement the same.
    Kindly correct me if i am wrong.
    Once again thanks for your reply.
    Please suggest on the same.
    Regards,
    Hemant

  • Condition Type and Movement Type

    Dear all,
    Could anyone explain how the relationshipship between condition type and movement type are being maintain?
    Example : WE03 and Mvt 101,
                    WA03 and Mvt 201.
    Is there any table or tcodes  to view these relationship?
    Thank you.

    Hi
    Both are linked based on the Transaction event type.
    for GR movements the transaction even type is WE
    For GI Movements the transaction event ype is WA.
    Thanks & Regards
    Kishore

  • BBP_BS_GROUP_BE for new document type and number range

    Hi gurus,
    I am working on Classic scenario in SRM and currently have used the above BADI to use a different document type and number range when creating the PO in the backend system. It all works fine. The only thing is I noticed that the BE_DOC_TYPE field in the shopping cart is still reflected as 'EC' even though the PO created in ECC is for example EC1. My question: Is this standard SRM? If so, is it common to leave this field as it is or is it advisable for us to change the document type to EC1 as well? Also, is there any implication in standard SRM reporting and downstream processes that you are aware of?
    Appreciate any advice on the above.
    Cheers!
    Sf

    We have ended up having to populate the document type on a custom field or alternatively replace the existing one.

  • Condition types and scale basis

    Hi
    Can any one tell me for conditions types and scale basis for maintaining condition records
    thanx in adv

    dear
    Scales in nothing but a range of order quantity, according to the pricing element depending upon the range of quantity prices way be increased/decreased, higher discounts, low freight changes can be offered.
    Ex: when per one item is 100/- if customer placed the order for
    Range          price
    100/-
    95/-
    90/-
    Check --&#61527;&#61509;value:     
    We can specify the changing rule for scale rates as ascending or descending.
    Scale type:     
    This indicator controls the validity of the scale value or percentage from certain quantities or value up to certain quantity or value, alternatively it is possible to work with internal scales that must be stored in the condition type that is the scale type the interval scale can’t be change in the condition record due to technical reasons ex: condition type PR02 graduated scale.
    Scale formula:     
    We can specify the formula for determining the scale base value; we can provide formula’s that has not been provided in the standard system. Ex: condition type ‘KP003’ to support mixed pallet surcharges can be used
    Condition scales:     
    We can maintain scales for each and every condition type so that we can determine pricing condition value depending upon the range of order quantity.
    Ex: If we maintain condition record for PR00 for material one as a Rs.1000/- for one material then we can maintain scale for this material like below.
         Quantity          Price
    0-10     1000.00
    11-20     999.00
    21-30     998.00
    31-40     997.00
    Configuration settings:     
    Go to VK11; maintain condition record for PR00,
    Select line item and click on scale icon on the application tool bar &
    Maintain scale rates accordingly, save it & exit.
    Got to VA01 and raise scales order, validity periods to scale. Check the condition value
    rewards if it helps
    siva
    Message was edited by:
            siva narayana

  • Alternative condition type and base value

    hi
    gurus  i am very much confused with this
    alternative condition type and base value  plzz clear me  from this confusion
    give me with realtime example and  tel me in simple way
    they will fully rewarded. and also a gud help to me
    thanks
    srinivask.

    Hi
    hope it is Alternative Calculation Type and Alternative Condition Base value
    if so pls refer below
    <b>Alternative Calculation Type:</b>
    Normally if you want to calculate a value you have to use a calculation type for determination the value. This calculation type is either addition, subtraction or multiplication. Similarly SAP also has got a default calculation type in the control data of the condition type. There you have the options of either Qty based , Fixed Amount Based or Percentage based.  
    Here what happens is suppose if you define Your condition type that calculates the base price of a material on Qty based. Then the calculation will be done based on the quantity of the material. If the customer orders 10 Nos and you have maintained a unit price of 100 Rs for each material then the value determined is 1000 INR. Similarly if the discount condition type , you maintain the calculation type as %. This means if you maintain the value of 10  % in the condition record. Then this percentage is taken as the calculation type  and the condition value is determined.
    In some cases you have to forego the default calculation types and use the customer specific method for calculating a value. For ex if you are calculating the Freight charges for a Material . it depends on so many criteria like, the weight, volume  and also the minimum amount etc etc, in those cases, you forego the default value and then use the alternative calculation type in calculating the condition value against the particular condition.
    <b>
    Alternative Condition Base value</b> :
    If you have to calculate any value then you have to have a base value for it. For ex if you want to calculate the  discount of 10 % for a material then you have to have a base value on which this 10% is calculated. Normally you take the  condition value of the base price of the material to calculate the value.
    Now you don't want to take the base value and take other values as base value which are derived on some formulae. So you create a routine which will do the mathematical operations in the routine and derive you a value which is now used as the base value for calculating the condition value for a particular condition type

  • Condition types and value fields

    hi Gurus,
    Can anybody please explain me what is condidion type and value field and the purpose of these two in costing??
    Regards,
    S.Sumana

    Dear Sumana,
    Condition types and Value field conjuction is used in Profitability Analysis.
    Condition type is an element in pricing procedure. For e.g price of the product consist of several things like base price, discount, tax, etc. so each compenent is called condition type.
    Value fields are grouping of cost elements for e.g. you have created a cost element Sales revenue then all revenue cost elements which consist of revenue.
    Condtion type Base Price is revenue which is mapped to value field Sales revenue. So as soon as the billing document is created value field is updated.
    For more information on Profitability analysis please read the documentation provide in www.help.sap.com
    Regards,
    Chintan Joshi.

  • Internal order types and number ranges

    We have two SAP instances and want to load Internal order types and number ranges and Internal orders from 4.6 to 4.5 version.
    I need to determine if there is an overlap of number ranges for the internal order types used in 4.6 and 4.5
    Could you please help me how to approach? Manually verifying each range in both system is a tedious job and very confusing as the numbers are too big.

    Hi,
    I can suggest one thing which seems to be worth trying. Involve one technical guy in downloading the number ranges as well the orders of the numbers used from both the system and compare it. Then compile them and upload it again.
    Trust this helps much!
    Cheers!

Maybe you are looking for