Pricing condition record Scales for width

Hi,
Wanted your expertise, as we are trying to implement scale for a pricing condition as below. Please advise which scale type to be used I think we should use D as interval graduated scale, but my query is my width value stored in material master and once order read it should pick the price as per interval . Need to know when i select type D it should not do graduation in same sales order for other lines. I mean if order has two line item with same material and third line with different material. system should calculate first line price 0.09 and second line should also pick price 0.09 as width is within 0 to 1
third material should price 0.13
please advise how this is posible because i think gradutaion type adds previous line record value, which we don't want.
Mat 1 - 0.7 in
Ma t2 - 0.9 in
Mat 3 - 2.5 in
0.000 - 1.000 in 0.090
1.010 - 2.000 in 0.110
2.010 - 3.000 in 0.130
3.010 - 4.000 in 0.140
4.010 - 5.000 in 0.150
5.010 - 6.000 in 0.160
6.010 in 0.200
thanks
Niki

My order has quantity 1 and sales unit of measure is PAC and material base unit of measure is FT. As if now maintained condition record scale in FT for the width.
in additional data of material we have unit convertion as below
1     FT     Foot     <=>     1     FT     Foot                                                                                1.722     1.566     LB     1.000     FT
1,566     LB     pound, US     <=>     1,000     FT     Foot                                                                                0.000          0.639     FT
3,600     PC     Piece     <=>     54,600     FT     Foot                                                                                0.000          15.167     FT
100     PAC     Pack     <=>     54,600     FT     Foot                                                                                0.000          546.000     FT
                               <=>                FT     Foot                                                                                0.000                   
thanks

Similar Messages

  • Pricing condition record, calculation type F volume, scale basis E net weig

    HI SAP Gurus,
    I have a question on pricing condition records.
    I have a requirement that needs to populate discount based on total net weight on the PO.  For example, if total net weight is greater than 1000 LB, it should give 10 cents discount per GAL.  The base UOM of the material is EA, GAL is an alternative UOM and Order Pricing Unit.  I can make the pricing condition works if the discount is per LB.  However, it doesn't work for discount given per GAL.  The calculation type is F volume and sacle basis is E net weight.  Pls advise what I need to do to make it work.  Thank you so much!

    closed

  • Coprying rule-Pricing Condition records

    Hi,
    When copying the condition records, it gave the message "*Copying is incomplete because no rules have been defined."Can anybody pls. guide as to how to define copying rule for pricing condition.
    Regards

    Prerequisites for Copying
    The following general prerequisites apply to copying condition records:
    If the condition tables differ between the source and target condition records, then:
    Only one field may differ between the two condition tables
    The condition tables must contain the same number of fields
    If the condition types differ between the source and target condition records, then each condition type must have the same calculation rule, scale type, condition class, and plus/minus indicator.
    Copying Rules
    Copying rules determine which condition types and condition tables you can use for copying between source and target condition records. The rules are defined in Customizing for Sales and must meet the prerequisites listed above. The standard R/3 System contains standard copying rules. If required, your system administrator can modify the standard copying rules or add new ones to meet your requirements. During processing, you can select from alternative copying rules, depending on what you are trying to copy.
    Examples of Different Copying Scenarios
    The following three scenarios describe how you can copy condition records.
    Scenario 1: Same condition types/same condition tables
    You offer a special discount to a particular price group (a group of customers defined in the customer master record). You want to make this discount available to other price groups by copying pricing details from the existing record. In this type of copying, the condition types (K020) and the condition tables (table 20) are identical for both source and target condition records. The only thing that varies in this case is the value of one of the key fields (the Price group field).
    Scenario 2: Same condition types/different condition tables
    The access sequences for a particular condition type can be defined in Customizing for Sales so that it accesses more than one condition table. This means condition records with the same condition type can have different keys. You can also copy condition records where the condition type is the same but the condition tables are different. Say you offer a material-specific discount to a particular price group (condition type K032, condition table 32). You can copy this material discount and create a new condition record for a specific customer (condition type K032, condition table 5).
    Scenario 3: Different condition types/different condition tables
    You can also copy condition records even when both condition types and condition tables are different. Say you offer a special discount to a particular price group (condition type K020, condition table 20) as you did in the first scenario. Here, however, you want to copy this condition record not to another price group but to a new customer-specific discount (condition type K007, condition table 7). In this case, both condition types and condition tables are different.
    Copying Process
    You can call up the copy function from the Edit menu in any of the following condition record screens:
    Creating
    Creating with reference
    Changing
    Overview
    There are several typical scenarios for using the copying function. You may want to copy an existing condition record into a number of new condition records. In this case, you use the change condition record function. Alternatively, you may want to create a new condition record and copy it to other records all in one step. In this case, you use the create condition record function. In both cases, you can change the copied data before you save the new condition records.
    Note:
    If the existing rules not suited to ur requirment , u have to contact Abapers to write the routines for ur requirement.
    Hope it is useful
    REWARD POINTS IF USEFUL...

  • How to Maintain the Pricing Condition Records in CRM

    Hi
    I am new to the CRM
    How to maintain the pricing condition records in crm for the particular condition type?
    as we do in SD(VK11)
    Thanks

    Hi Binu,
    First of all, you could maintain pricing conditions in the following places:
    1. In General Condition Maintenance (GCM)
    2. At the product maintenance level
    3. At the 'Price agreement' tab of Contracts
    4. As manual conditions during order processing at item level
    Now, if you want to maintain conditions using GCM, you first have to maintain a condition maintenance group in the customizing where in you can assign condition table and condition type for different counter values. I am assuming that you have done this activity successfully.
    When you run the transaction '/SAPCND/GCM', for application 'CRM', your condition maintenance group name and context 'GCM', you will be initially taken to a screen where in you'll have an item area which would be blank and then condition fields would be displayed in a tree on the left.
    Here, select the field 'Condition type' and click on icon 'Select records'. You would get a dialog prompting you to enter condition type. Here you can specifiy the condition type for which you want to maintain/view condition records.
    If no condition records are available, item area would be left blank. Here, you can choose a condition type using the standard F4 help. Depending on condition types that are assigned to condition maintenance group, different condition types would be displayed in the F4-help using which you can maintain condition records.
    Hope this helps.
    Regards,
    Pavithra
    **PS: Please reward points if this helps.

  • Pricing condition record

    Hi All,
    There is a problem with the invoice condition records.In our case invoices are actually created via Idocs.
    Usually the condition record type is sent in the Idoc and the corresponding condn. type comes in the invoice.But in one case,the Idocs do not have a particular condition record type present in the data segment ,yet the invoice when created has the condition type in it.
    Does any one have  a idea if the condition type gets picked from any master table or is there any other way it  appears in the invoice.
    As far as the program that creates the Idocs,It picks the condition records from a Z table and fills in the Idocs.
    Thanks for your help!
    Regards,
    Gowthami SK

    Hi Sam,
    the preceding document is the sales order.
    the scenario is like the sales order gets created through Idocs (msg type:VLCCPO),the pricing condition record is filled in the Idoc ( KSCHL) and it appears in the invoice.
    But in a particular case,there is no condition type in the Idoc  ,yet the condition type appears in the invoice.
    Is it possible that any standard pricing condition has been defined???
    Regards,
    Gowthami SK.

  • Changing currency in the Pricing Condition Records after saving

    Hello,
    I would like to know whether there is any way we can change the currency in VK12 in the pricing conditions records created via VK11. Please let me know.
    For example, for PR00 condition type, I am maintaining condition records in VK11. I enter an amount and currency as USD and I save it. Now, in VK12, I would like to change the currency to EUR. Is this possible? Please share your ideas.
    Regards,
    Venkata Phani Prasad K

    Closing this thread.

  • Duplicate pricing condition records in Billing

    Helllo evry one,
    I have an issue with an Invoice document, Where the pricing  condition records is appearing twice both at the item level and header level. 
    It is appearing as
    Condition Type     Condition base value        Condition value      
    ZABC                               20.00                                       200.00
    ZABC                                20.00                                      200.00
    Any clue at what level is might happen and how can we avoid such issues
    Regards,
    Ganesh
    Edited by: Tcode on Dec 15, 2009 5:56 PM

    Hi,
    Check  Whether the CONDITION TYPE is a HEADER CONDITION
    Goto V/06 and check the HEADER DISCOUNT filed is activate for the condition type, if yes then it will copy to Item also.
    Please check and revert back.
    regards,
    santosh

  • Deletion of bulk pricing condition records

    Hello thr,
    I have thousands of pricing condition records to be deleted. I use condition type ZP01 in VK12 and select the key combination customer/material and then enter the details and then mark the condition record for deletion. To delete the next condition record, I need to go back and do the entire process again. Could someone please let me know if there is a txn that can help me do this in one step.
    Thanks very much for your help.

    Hi Swetha,
    If you want to delete all conditions for ZP01 condition type, you need to create a LSMW batch input from LSMW t-code. you can check and try followings:
    [https://wiki.sdn.sap.com/wiki/display/ABAP/LSMW%20steps%20-Batch%20Input%20Recording]
    [http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc]
    You should go to in LSMW t-code, a recording should be created for one record from VK12 t-code and it can be run for all records like same from SM35 t-code.
    Please follow the links above for VK12 condition deletion.
    I hope these will meet your requirement fully.
    Regards,

  • P.O Pricing Condition Record

    Hi
    Which Tcode to maintain the Purchase order condition record (Specifically for the Tax Condition).
    Rgds
    RG.

    Hi
    You can use MN04 to maintain the Pricing condition.
    You must define in SPRO the necessary Pricing condition (Tax condition) ,  Access  Sequence, add it to Pricing schema  and to appropriate pricing procedure.  Maintian the condition record.  Also look into t-code NACE that will give you the all the condition records on all application aras.
    Hope this helps,
    Thx
    MJ

  • Pricing condition records maintanence

    Hello All,
    We have a requirement to store the pricing condition records in 3 decimal places say 1.733 instead of 1.73 that way standard SAP is doing.
    Do we have any solution for this? Can we maintain the pricing condition records in 3 decimal places?
    Any suggestions would be appreciated ?
    Thanks,
    Vinay

    chk the following thread:
    https://forums.sdn.sap.com/click.jspa?searchID=5045505&messageID=3878405
    Regards
    AK

  • Pricing condition record text maintenance in multiple language

    Hi friends,
    While maintaining condition record by VK31 transaction, there are options for multiple language selection. but after saving it appears only in English. Please let me know whether we can maintain text in multiple languages for a pricing condition record?
    Regards
    Manish
    9741178072

    HI Manish,
    You need to maintain the translations for the condition types in SPRO.
    The path is SPRO - Sales and Distribution - Basic Functions - Pricing - Pricing condition types - Maintain Condition types.
    Then selecting the particular condition type GOTO- Translations, you need to maintain the translation in the particular language as desired.
    Thanks
    Ani

  • Archive pricing condition record

    Hello everybody,
    I want to ask about how to archive MM pricing condition record?
    I tried with SARA, archive object CND_RECORD or program /SAPCND/CND_RECORD_WRITE but it doesnt work.
    Kindly advise,
    Thanks,
    HN

    Hello Jurgen,
    We're about to archive tens of millions of SD_COND entries - mainly to reduce the number of change records we have in table CDHDR, of type COND_A (COND_A is the change document object for SD Pricing conditions and we have over 100 million of them! And is now causing a few performance issues).
    Understandably this is going to take a long time to process so I was intrigued to read your post that no conditions should be maintained whilst the archiving programs run...
    I've tried searching OSS but haven't been able to locate any information about this.
    Could it be that you were referring to the old archive programs and not the newer ones such as those described in:
    Note 838768 - New archiving programs for condition records
    Any help you could offer would be much appreciated!

  • Bulk Pricing condition record upload

    can any body help out for , Is there any transaction code  for uploading the pricing condition record in BUlk.
    Ex: 1000 condition records upload for condition type PR00..
    Ragards

    Dear Ramesh,
                           This you can do by creating an LSMW,one of the mass upload tool.
    Regards,
    AKD
    Edited by: Ashish Dikshit on Sep 19, 2009 9:31 AM

  • Extracting the pricing condition records

    Hi,
    I would like to extract the pricing condition records of a particular sales organization. I need to upload these records to another system.
    Any guidelines?
    Thanks a million.

    Hi,
    For Sales dacuments pricing conditions you can use :
    RV_PRICE_PRINT_HEAD  --Header pricing conditions
    RV_PRICE_PRINT_ITEM  -- Item level.
    Lanka
    Message was edited by: Lanka Murthy

  • Pricing Condition Records initial upload - COND_A

    Hi,
    I have configured outbound COND_A pricing condition Idocs for Change documents. Whenever the pricing condition is changed IDoc will be generated.
    Now my requirement is how can I do the initial upload of existing Pricing Condition records to legacy system? I mean how can I generate Outbound IDocs for existing pricing condition records to do initial upload.
    Thanks in advance for your help.
    Rgds,
    AK

    HI,
    way1:
    if you are using Sretail (ARTMAS) then you can use BD10 tcode with the flag "send all data".
    In that case the COND_A for every ARTMAS is send.
    way2:
    1. if you want to send a all condition, then go to MEK3 choose your conditiont ype and push "condition Info".
    2. Make your selection and go ahead with F8
    3. Push "Send condition"

Maybe you are looking for

  • Problem with socket responses with flex

    Hi, I am using the code below to connect to an IMAP server. When I telnet to the server and use the commands that I am sending in the code, the rsponses are correct. However, when I run the code below, I only obtain the ready and logged in responses

  • Not possible to change purchase order

    hi all, i have problem in SRM , system does not allow me to change po , and the po is with the approver. the following error message comes up 'change mode possible only after selection of valid work item' , i am not able to find the error message fro

  • I can't log in to my itunes account, and it does not give me any errors.

    I can't log in to my itunes account.  When I try, the login screen disappears for a moment.  It then pops up requesting I log in.  It does not include any error messages.

  • Reg: Generation of Training Proposals from PD

    Dear All, I am new to the PD module of SAP HCM. I need to know how can we generate training proposals from Career Planning and succession planning and also if there is some point in the PE module where we can specify the qualification attained once a

  • SW update problem n97mini

     i have a N97mini,  when i try do update my software through the SW update app on the phone, it detects there is new updates for the firmware, however when it finishes downloading and trying to install it will end up " not compatible with device, ple