Can we attach requirement for manual condition type

Hi,
Pricing question....
ZOTH is the manual condition type
(The condition type configuration: - Manually editable, no access sequence attached )
(Pricing procedure : - No alternative calculation type attached)
Can I attach a requirement to ZOTH in the pricing procedure?
Laxman

hi,
we can very well have requirements for manual conditions also. Like we have standard requirement "2" Item with pricing and this is assigned to PN00 ( Net price ) condition which is a manual condition.
you can check in RVAA01 pricing proc. also
regards
sadhu kishore

Similar Messages

  • How can we create new pricing requirement for a condition type

    Hi All,
    I am in urgent need of creating new pricing requirements for a condition type.
    Or if there is already a conditin type existing and we want to make changes in the pricing requirements of that condition type, How can we do so ?
    In short if you can let me know how does pricing get impacted by the condition types.
    Thanks
    Mark

    Hi!
    The common transactions for condition mantaining are VK11, VK12, VK13.
    In SPRO - Sales and distributoin - Basic function - Pricing - Pricing control - *.
    Is this what you want?
    Regards
    Tamá

  • Authorization object for manual condition type in sale order

    Hi experts
    I want ask them, If exist an authorization object for manual Condition type (KOMV-KSCHL) in the sales order (VA01/VA02), that the user don' t can create neither modify the sale orden with a specific manual condition type (payment term) by stardard way.
    Best regards
    John Angulo

    HI John,
    I would be surprised to know that someone uses the Payment terms as a condition in the Pricing procedure for sales orders. The payment terms define when the customer agrees to pay, (15, 20, 45 ,....days or 5 years or 10 years....whatever it be)
    this detail for what i know is in the sales order header,and ideally has nothing to do with the Item level material price conditions.
    its ok, If you mean something else by payment terms.....in principle you can have a conditon type restrcited such that manual entries on the condition are not possible. this cane be done in SPRO customizing, i am sure your functional consultants would know what to do (SPRO->Sales and Distribution->Basic Function->Condition Types), in the tab "Changes that can be made" have a value that says manual Processing is not allwowed
    The ABAP route mentioned above is for a different scenarion and i dont think it is necessary for your requirement

  • Config required for EK02 condition type in Sales Pricing procedure

    Dear friends,
    I am trying to derive a costing run for sales order. I would like to know what are the config steps required to arrive a percentage factor for GP.
    Kindly guide me in this regard,
    Thanks in advance,
    Vinayak

    Hi,
    If you are doing sales order costing then you will have to define the condition type EK02. Go to V/08. Select the Procedure used in SD. Click on Control. Enter the condition EK02 - Calculated Cost and mark it as statistics.
    You sales order cost will be stored in such condition type.
    Regards,
    Jigar

  • To Restrict Duplicate & Without Value Manual Condition Type in ME21N

    Hi Friends,
    While making a stock transfer (purchase order) by ME21N from supplying plant (Factory) to other plant (depot), if user make mistake & donu2019t put value for Manual condition type ZMRP, system accept & save the order.
    Afterwards when he realizes the same or immediately come to know about not putting value & put again, system take that second line entry also & create double entry.
    When invoice come then it pick the value from first line & show in negative.
    How it is possible to restrict it at order level only to not to allow 0 value & repeat entry for the same condition type?
    I have triedu2026.
    1. At pricing procedure, there ZMRP is required entry.
    2. Condition Type - ZMRP, there is _ No Limitations
        We can not put D Not possible to process manually or fix this condition type as then we have to maintain condition record & prices are varies depot to depot & day       by day.
    3. Since this is a Header Condition, so canu2019t restrict at Access Sequence level.
    This is only has to put manually by user according to the instruction of sales department. 
    Got Suggestion to change at user exit level to put check at delivery to not to allow printing or invoicing by putting 0 value/without any value.
    Please suggest at configuration level only as itu2019s difficult to create User Exit for all requirement.
    Srivastav
    +91-9694096833

    Hi,
    You must update the forum how did you solved the issue as it will help others also in future.
    This is good practice.
    Regards
    Sanjay

  • Manual Condition Type should be visible in Sales order by default

    Hi
    How to maintain manual condition types in Sales orders by default. They will be maintaining the value based on the discussion they had with the customer(Negotiated price). The condition type should be visible in the procedure and they will only enter the value.(The method of keying condition type manually is not accepted by the client).
    Thanks in advance.
    Regards
    Vamsi Javaji.

    Hi,
    In the PRICING PROCEDURE V/08 maintain the CONDITION TYPE as Mandatory
    In the CONDITION TYPE V/06 maintain the field  MANUAL ENTRIES  as C which is Manual entry has a priority.
    And check the box VALUE
    Now maintain the condition records for the condition type in VK11 with 0 value
    Now while processing the sales order the CONDITION TYPE will trigger from the CONDITION RECORDS with 0 value and this can be in EDITABLE mode ( and maintain the value)because of the check box VALUE you flagged in V/06.
    Please try this and revert back if you need further details
    thanks,
    santosh

  • Manual condition types need to be reapplied after material change

    HI Team,
    For some of order items user enters manually condition type through VA02 for availing discount for the order item,
    I am having a custom program for updation of sales orders, Through which we can change the order materials.
    Order 123 having item material ABC. For which he entered manual condition type ZXYX.
    now using custome program he wants to change the mateial ABC  to XYZ. Thorugh custom progam material is updated. Price has been recalculted.
    But customer wants condition type ZXYX also need to apply for the XYZ material.
    Please guide me how to proced.
    Regards.

    Hi,
    Ask your ABAP consultant to check program MV45AFZZ.
    Here in item pricing update i.e
          FORM USEREXIT_PRICING_PREPARE_TKOMP   *
    write   PERFORM preisfindung_gesamt(sapmv45a) USING charc.
    where charc is  'C' (copy manual pricing elements & redetermine others) or you may also use 'G'(Copy pricing elements unchanged and redetermine taxes.)
    This surely works.
    Regards,
    Amit

  • Tax value is not picked up correctly for the condition type in SO creation

    Hi All,
    I have a issue in Picking up Tax value correctly for the condition type in SO Creation.
    Actual Issue:
    When creating the sales order manually,
    tax value is picked up correctly for one condition type: ISS3.
    When the Sales Order is created via Idoc using the function module 'idoc_input_orders', tax value is not picked for same condition type: ISS3.
    We need to find out why the value for the condition type 'ISS3' is not picked in this way!
    Can anybody solve this issue!
    What can be the reason which is stopping picking up tax value for condition type: ISS3 when Sales Order is created via F.M 'IDOC_INPUT_ORDERS'! While it picked up the same while creating Sales Order manuallly.
    Thanks in advance.
    Thanks,
    Deep.

    Hi All,
    Can anybody give the solution for above posted issue!
    Working:
    When creating the sales order manually,
    tax value is picked up correctly for the condition type ISS3.
    Actual Issue:
    When the Order is created via Idoc using the function module 'idoc_input_orders',
    tax value is not picked .
    I need to find out why the value for the condition type 'ISS3' is not picked.
    I have debugged the issue from WE19 but upto Conditions tab it is picking up tax value but then it is becoming zero again it remains zero after saving SO.
    But Manually tax value is picked up for condition type ISS3 and remains same after saving order.
    I have debugged it several times fro WE19 but not able to find route cause for the issue.
    What can be the issue over here!
    Can anybody give me solution for the same!
    Thanks in advance.
    Thanks,
    Deep.

  • Manual Condition type in Sales Order

    Hi,
    i need to enter a manual condition type in sales order which should come in % and the value should not come or it should come as zero, Is there any way to make that manual condition value as Zero in sales order.
    Ragu

    Raghu,
    Pls check the OSS notes 392668, that will solve your problem.
    The same pasted here for your reference. However, I advise you to download it and then read due to inconsistent formatting here.
    Reward if this helps.
    When you create documents in which the standard pricing is used to determine condition records as well as to calculate a pricing result, the display and entry of manual entries is not clear in the relevant condition screen (screen 6201 in the SAPLV69A or SAPMV61A programs for releases prior to 4.6A).
    This note explains the interaction of manual entries with the attributes maintained in the pricing procedure and in Customizing of the condition type.
    Other terms
    KAUTO, V/06, V/08, KAEND fields, KOZGF, PRICING_CHECK, LV61AU08, XKOMV_ERGAENZEN_MANUELLE, LV61AA53, manual entries, MANU
    Reason and Prerequisites
    In the pricing Customizing, the following fields affect the manual entry of complete condition lines or individual condition rates:
      Description        Technical name              Maintenance transaction in SD
      Access sequence    KOZGF                  V/06 and V/07
      'Manu'            KAUTO                  V/08
    Depending on the characteristic of the mentioned fields, the pricing condition screen appears as follows:
      KAUTO   | KOZGF    | Condition record existing on DB? | Result
      Initial | Initial   | -                                | (1)
      Initial | Existing  | No                              | (2)
      Initial | Existing  | Yes                              | (3)
      Set     | Initial   | -                                | (2)
      Set     | Existing  | No                              | (2)
      Set     | Existing  | Yes                              | (4)
    Result (1)
    A condition line is set for the relevant condition type [KSCHL]. The 'Condition rate' field [KBETR] does not contain a value, but is ready for input. The displayed line serves as an input help or a template for the manual entry.
    Result (2)
    No relevant condition line is set on the pricing condition screen, in other words, the condition type is missing.
    If you enter the condition type manually without entering a condition rate in the same processing step, you get a 'template line' as described in (1).
    Result (3)
    A suitable condition record that exists on the database is set with amount (= normal, automatic determination).
    Both the 'Condition origin' indicator [KHERK] and the 'Condition control' indicator [KSTEU] are set to 'A'.
    If you create another line with this condition type and enter a condition rate not equal to zero, a line is set with this condition rate.
    The 'Condition origin' indicator [KHERK] as well as the 'Condition control' indicator [KSTEU] has characteristic 'C'.
    If, on the other hand, you create another line and enter a condition rate of zero (or do not enter any condition rate) and the condition record that exists on the database has a scale, the system sets the condition rate according to the achieved scale level. If zero is to be set as the condition rate even if scales exist, then use modification Note 179354. If no scale is maintained, then the system always sets zero as the condition rate.
    In these cases, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] characteristic 'A'.
    Result (4)
    No relevant condition line is set on the condition screen, even though a condition record suitable for the access sequence exists on the database. The pricing analysis displays the message "Manual condition (Condition record exists)". If you enter the condition type manually without entering a condition rate in the same processing step, the record that exists on the database is set. If a condition record has a scale, the system sets the condition rate of the first scale level independently of the achieved scale level.
    In this case, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] has characteristic 'A'.
    Thus, the setting variant leading to result (4) serves to suppress the setting of automatically found condition records into a pricing result. However, you can add the maintained record to the already determined pricing result by entering the relevant condition key.

  • Manual conditions type - Net value effect

    Hello,
    For some materials when I enter the manual condition type the system updates the net value immediately (without me clicking on the "update" button).
    For some other materials when I enter the same manual condition type (in the same order type), I have to click on the "update" button for the net value to get affected.
    Can anybody say where is the settings to control this?
    Thanks,
    Shankar

    Hello,
    Check the userexit: USEREXIT_NEW_PRICING_VBKD
    in the include MV45AFZB.
    May be some code has been written, if you change price for specific Material Type then it should do 'B'   = Carry out new pricing.
    I hope this helps you..
    Regards,
    Murali

  • New Requirement for my Output type?

    Hi.
    I want to create a new requirement for my output type.
    Please guide me how shall I do it?
    thanks

    You can trigger the output type by creating a condition record.
    Go to transaction VV21, enter the output type, click on Key combination, if ther's a radiobutto for shipping point only, select it and create a condition.
    If ther's no radio button for shipping point, add table 024 to the access sequence assigned to the output type in NACE.
    After modifying the access seq. go back to VV21 and create a condition.
    You can create condition records in NACE also.
    Regards
    Sridhar

  • Authorization for discount condition type

    Hi Experts
    1)when create a sales order client want flexibility for discount condition type
    like 10% ,15% , 20% it should not be manual and end user can choose from drop down and
    2) If they want to give excess discount there should be authorization any supervisor can give  excess discount 
    how to map this authorization to condition type
    Regards

    hello again, friend.
    go to IMG > SD > Basic Functions > Pricing > Pricing Control > Define Cond Types... here you will find the settings for the upper and lower limits.  please note that the larger discount rates would be represented by the lower limit.  for surcharges, the lower rate is the lower limit.
    scales in pricing allows you to set different discount/surcharge rates or fixed amounts depending on either value, quantity, weight, etc.  in the same pricing condition record (using VK11 or VK31).  if you look inside your condition type using V/06, you will see under sub-tab Scales if this has been set.
    example:  condition type Z007, with Scale 'Quantity'
    you can set a discount of 2% if item quantity is from 0 to 100 pieces
    you can set a discount of 3% if item quantity is from 101 to 200 pieces, and so forth...
    regards and thanks.

  • Default Currency for freight condition type in sales order

    Hi Gurus,
    I have  Freight condition type, maintained condition record with combination of Customer, Incoterms & Material Group.
    In Customer Master Currency is USD or EURO.
    When we create Export sales order, so by default currency should come INR, not USD or EURO for Freight condition type from Customer master.
    How to get this requirement.
    Regards,
    Rakesh

    Hi Rakesh,
    I think you need a revision on condition table and access sequence for frieght condition records from SD >> basic functions >> pricing >> pricing control >> follow standard pricing configs. Actually, you need to add country ( ALAND ) and  destination country ( LLAND ) fields to your table and access sequence for export sales.
    After those configs,  you can create records in USD or EURO for domestic sales and create records INR currency for export processes.
    I hope you can neet your requirement by using this way.
    Regards,

  • Issue regarding condition pricing date as system date for some condition types in sales order

    Hi
    I have already created a sales order on 30.04.2014. Today I am adding new line item to sales order in VA02 transaction. in this order new line items condition pricing date for conditions JEX2,JECX should show as 12.06.2014. But currently it is showing as 30.04.2014. I need condition pricing date as system date for above conditions.
    Regards
    prashant

    Hi
    When I am changing pricing date VBKD-PRSDT in sales order header . It is changing the condition pricing date for all. Sales order is created on 04.06.2014. I have added line item 150 on 14.06.2014.
    After adding line item 150 , there I have changed the pricing date as 14.06.2014. in sales A tab of item 150. But still it is taking from Sales order header date as 04.06.2014 for all conditions. But my requirement is for line item it should take as system date for some conditions like JEX2,JECX& JA1Y but for other conditions it will take as Order creation date. Please suggest. I have also attached screen shot below. please go through it.
    Regards
    PK
    Sales order header change mode VA02
    Here pricing date VBKD-PRSDT = 04.06.2016
    Item change mode
    I have added new line item 150 on 14.06.2014
    Changed the condition pricing date to 14.06.2014 & saved
    After saving I have gone to Va02 screen of line item 150
    & there I have gone to condition pricing date field from item condition tab
    for JEX2 condition type but still here condition pricing date is showing as
    04.06.2014 as below.
    Condition pricing date
    My requirement is like this
    For some particular conditions like JEX2  condition pricing date will take as system
    date instead sales order creation date when I will add a new item 150 on
    14.06.2014.but for other conditions it will show as order creation date for the
    same line item 150 .

  • Tracking manual condition types in billing document

    Hi,
    I need to track changes in manual condition types in billing docs over a period of time. These changes are not maintained at Change doc tables (CDHDR,CDPOS).
    Please suggest whether there is any other way to solve this issue.
    Thanks.

    Hi,
    Check with KONV table
    Enter the Condition record number in field KNUMV of table KONV (This you can get from VBRK table for the Billing Document), and check with the field KMPRS in KONV.
    Reward point if it helps !!!!!
    Harsh

Maybe you are looking for