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

Similar Messages

  • Adding manual condition types to a service contract

    Hi,
    I need to add a manual condition type and price value at billplan line item level in a service contract. Could anyone please let me know any way of adding it after the service contract has already been created?

    Hi,
    You need to first create the Condition type which can take manual entries or the manual entries are prefered.
    Then add the Condition type to the pricing procedure being determined in service contract.
    Once done when you go to edit mode in conditions tab you shoudl be able to add the above condition types.
    Regards,
    Tanu

  • 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

  • How to change the manual condition type value in change sales order BAPI

    Hi All,
    My scenario here is, i want to either add/change the manual condition type value during change of SO.
    When i'm trying to pass the  order_conditions_in and  order_conditions_inx tables in  'BAPI_SALESORDER_CHANGE'.
    Condition type is coming at item level but the value is setting to zero. Pls. help if anyone has any idea how to handle this.

    Siva,
       I guess you posted in Wrong Thread. You need to post in WAS section.
       check for any BAPI's available in CRM.
    Nagesh Ganisetti.

  • 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.

  • Pricing - Manual Condition Type with value = 0

    Hi gurus,
    I need to insert a manual condition type with value = 0 into the billing data set.
    I realize that if its valiue is 0 it is not active.
    Anyone knows how to make it active despite its value = 0?
    Thank you.

    Dear Customer,
    if you have customized the condition as price then the condition will be inactive if the condition is set to zero.
    This is calling in:
    LV61AA55                                                                               
    inactivate prices with rate / condition value zero                   
          if xkomv-koaid eq 'B' and xkomv-kbetr eq 0 and komp-kposn ne 0 and 
             xkomv-kgrpe eq ' ' and xkomv-kinak ca ' Y' and xkomv-kwert eq 0 
             and xkomv-kntyp ne 'e' and komp-fareg na '45'.                  
            xkomv-kinak = 'X'.                                               
          endif.                                                             
    If you need an active condition with value zero, then the condition class should not be 'B' (price)
    I hope that the information are helpful.
    regards
    Claudia

  • Promlem in Manual Condition Type

    hi
    I am using Manual condition type for Price(in v/06 i maintained as 'Manula entry has priority' & in  V/08  activated manual check button)
    but in sales order after selecting manula condition & entering value if i press the enter button the values are dis-apperaing.
    if i enter 2nd or 3rd time system is takling the value?
    why not 1st time not accepting/
    Prasad

    Hi,
    The reason may be :
    you would have not maintained a condition type and its rate for it in tcode VK11.
    please do the same.
    also if you have done that , select the update icon on the right corner of the screen and select C option, copy manual pricing elements and redetermine the others.
    regards,
    Siddharth.

  • 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

  • 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

  • Condition type needed as both internal price and shown as cost in KE24

    Dear friend,
    I like to set up a condition type with attribute of internal price but like to it to be show as cost in profitability .
    Please see details.
    condition type needed as a internal price under condition part in SO line item , but will not be shown in customer invoice,
    At the same time, condition type needed to be shown in KE24 Please advise.
    Thanks,
    LG

    Hi
    You can transfer any kind of condition from SD to COPA although it will be an statistical condition (see for instance tcode KE4I).
    Talk with a CO consultant, because you will have to do a serie of steps.
    See these notes:
    Note 62536 - Info: Conditions in Profitability Analysis
    Note 74486 - INFO: Overview of consulting notes for CO-PA
    Regards
    Eduardo

  • 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

  • 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

  • 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

  • Manual condition types deleted on Quotation change

    Hi Friends
    This is an urgent issue.
    Please let me know the scenerios when can manual condition types get deleted when ever  call BAPI_CUSTOMER_QUOTATION_CHANGE
    Thanks in Advance
    Cheers
    LK

    Hi !!!!!!!!
    Can any one reply to this query

  • Is the Modavatable condition type of Import are loaded on material

    As I know there are seven taxes Basic Customs duty, CVD, Ecess on CVD, Shecess on Cvd, Custom Ecess, Custom Shecesss and Additional custom duty.
    Doubts-- Among these seven duties we get the setoff for for duties on  CVD. Ecess on CVD, Shecess on CVD and additional custom duty. Are this modavatabe duties are loaded on Inventory? If yes then how? if not loaded on material where is the setting for the condition type so that it should not be loaded on inventory.
    Please help me on this point. Hope i will get the solution .

    Hi Rajan,
    As per indian taxation system, you can take credit the duty paid to CVD, Ecess on CVD and SH Ecess and Add. Cutom Duty. Means these are not loaded to material but will get entry in to Cenvat Registers as credit and off-setting to Cenvat Clearing a/c.
    Basic Customs duty, Total Custom Ecess are not allowed to take credit so, they need to loaded on to material.
    To make the system understand this, we give default condition types in Custom defaults in IMG ( As sairam said in his reply). By this setting system decides which all the condition types are loaded / not loaded to material. But loading of CVD and other credit dutyies material does not sounds logical, so please check your scenorio
    Modvat Clearing account you will give it in Comapny code settings for excise.
    Thanks,
    Krishna Reddy

Maybe you are looking for