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

Similar Messages

  • How to set a condition type to inactive/statistical during sales order crea

    Hi
    There is a manual header condition (Z0L1) in one our pricing procedure which I want to set to inactive or make it statistical during sales order (doc type Z9) creation in some scenarios.
    How can I achieve?
    Can I use user exit USEREXIT_PRICING_CHECK (Program MV61AFZA) and what code should I write here. Any help would be highly appreciated
    Regards,
    Javed

    Thanks for your replies. Basically this condition type is a manual condition type which will be entered in sales order and then will be available in billing document. But when there is a return order created with reference to that billing document then I want that the manual condition is not deteremined in the return order.
    I tried by assigning a requirement to the condition type in pricing procedure but seems to be pricing requirement don't work for manual header conditions. Then I tried to assign a condition value formula and tried to set the value to zero in case of return orders but that also did not work.
    Then I also tried to apply the same logic in user exit USEREXIT_PRICING_CHECK  in the following programs
    LV69AFZZ
    MV61AFZA
    But still it did not work. Any help would be highly appreciated
    Regards
    Javed

  • Header condition type value not displayed in sales order output

    Hi gurus,
    I have observed a strange issue regarding a header condition in a sales order.
    we have a set up like following:
    1. If the Header condition XXXX is used in sales Order then this value should be printed on sales order output.
    2. If the Header condition mentioned in above point is not maintained in sales order it should print the total price of all line items.
    Though i have maintained the header condition value in Sales Order Header its not displayed in SO output.
    That is , I have a sales order and it has one HEADER condition type entered with 3500 USD.
    In fact this value is used for some business purpose and is being printed on the sales order output for a specific output type.
    But where as in a sales order this header condition value is not getting printed on the output though I am using same data as of the sales order which is having the header condition value printed on its output.
    According to business,we must have the header condition value printed on  sales Order output.
    Please suggest how to proceed.
    Thanks in advance.

    Not sure if you are using costom smartform to print invoice, if yes then ask developer to debug and find the root cause and fix it.
    You might need to give him condition when it shuld be printed and when not.
    You can take reference of another output type for which it is printing

  • Condition type in Billing not in Sales Order

    Dear Friends,
    I have the following scenario in our project. Please clarify.
    We have a condition type. That should be appeared only in Billing, it should not appear in Sales Order.
    Please answer ASAP.
    Regards,
    Rajesh L

    Hello,
    To fullfil you requirement go to V/08 select your pricing procedure and relevant condtion type.  Then select requirement column and assign the Routing 24 click save.
    regards
    rc gopi

  • Report of condition types per line item in sales order

    Hi all,
    Is there any report that can tell me all the price conditions that are allocated to a sales order line item? I am talking about the actual conditions relevant for a line item, not only conditions that have a condition record setup.
    So I would like to key in sales order number, the line item and get a report of all conditions that are allocated to that line item in the specific sales order.
    If there is no such standard report, does anyone know what tables to link?
    Thanks in advance,
    Lars

    Hi Lars,
    In my current customer they had the same requirement and after almost 1 month of analysis we decided to build a custom report to execute this.
    And as an enhancement we compare prices from the sales orders and the sap price records in order to check the differences.
    First we need to find all the open lines (status and reason for rejection (ABGRU)), than loop KONV and select the  KSCHL (condition types) you want, material text descriptions, etc.....of course a lot more in terms of coding.....;-)
    This was the form I used :
    FORM FIND_SO_PRICES.
      LOOP AT IT_ITEM_REPORT.
        REFRESH IT_PRICING.
        SELECT KSCHL KBETR WAERS KPEIN KMEIN KUMZA KUMNE
          INTO IT_PRICING
          FROM KONV
         WHERE KNUMV = IT_ITEM_REPORT-KNUMV
           AND KPOSN = IT_ITEM_REPORT-POSNR
           AND KINAK <> 'M'
           AND KINAK <> 'X'.
          APPEND IT_PRICING.
        ENDSELECT.
        READ TABLE IT_PRICING WITH KEY KSCHL = 'XXXX'. -> My price condition
        IF SY-SUBRC = 0.
          IT_ITEM_REPORT-ZSP1 = IT_PRICING-KBETR.
          MODIFY IT_ITEM_REPORT.
        ENDIF.
        READ TABLE IT_PRICING WITH KEY KSCHL = 'XXXX'. -> My discount condition
        IF SY-SUBRC = 0.
          IT_ITEM_REPORT-ZSD1 = IT_PRICING-KBETR / -10.
          MODIFY IT_ITEM_REPORT.
        ENDIF.
       IT_ITEM_REPORT-LIQ = IT_ITEM_REPORT-ZSP1 - ( IT_ITEM_REPORT-ZSP1 * (
                                              IT_ITEM_REPORT-ZSD1 / 100 ) ).
        MODIFY IT_ITEM_REPORT.
      ENDLOOP.
    ENDFORM.                    " FIND_SO_PRICES
    Please tell me if this helped you,
    Regards,
    Alcides Fialho

  • Enter condition type several times in a sales order

    Hello Gurus,
    I have a Pricing Procedures with net price minus some discounts and sales price. This is standard. One of the discount condition types you can enter manually in a sales order. Now my problem. This discount  condition type you can enter several times in a sales order. How I can solve this for one time enter.
    Regards
    Artur

    Yes, it is a standard behaviour only, you can only control with User exit only. Include MV45AFZZ , co ordinate with your ABAPer for the same.
    Regards,
    Ramesh

  • Condition type JEXP not picking in sales order

    hi
    i was working with all configuration of TAXINN
    i am facing with a problem
    when i am running mine sales order i am not able to see condition type JEXP(BED) , JEAP (AED)
    can i now where i am gng wrong
    whereas i can see all the other condition in sales order
    but when i enter it manually JEXP it is taking but in again in billing it is not showing
    can u plz help me
    Regards
    Vini

    Dear Vini,
    Please Check the configuration settings through IMG path
    SPRO>IMG>Logistics general-->Tax on Goods movements >India>Basic settings-->Determination of Excise Duty -->Maintain Excise defaults here you check JEXP condition type is maintaining for A/R BED or not if not maintain then try.
    Also check the condition record maintanance for the JEXP condition type through VK12 transaction.
    I hope this will help you,
    Regards,
    Murali.
    Edited by: Murali Mohan.Tallapaneni on Oct 1, 2008 6:51 AM

  • Rebate Condition Type cannot be reflected in sales order?

    Hi Guru:
    It seemed to be a issue? I set up the rebate agreement and ran the vbof successfully regarding this condition type rebate,and the retroactive billing also can view its rebate condition type as well as the accruals,and I believe the rebate settlement had been run too,credit memo to customer will be aslo routed to accounting side for sure,but I failed to see the rebate condition type and accrual value in the sales order based upon the retroactive all billings,please advise what I should do,thanks.

    Hi Klaas,
    If I remember well, in the standard price determination there is a conditional formula that only shows rebate conditions in the invoice, therefore you should not see rebate conditions in the sales order.
    That is standard functionality.
    For a Customer I took out the formula condition in the pricing so he could actually see the rebate condition in the sales order, the reason was to had access to this information before end of month invoicing. The problem is that in case of changes in rebate agreement or in case of retrospective agreements the rebate condition is only updated in the invoice, not in the sales order.
    Best Regards,
    Franck

  • Condition type value not update in sales order

    Hello Guru's
    As per the  sales order in VA01 the condition type value i.e surcharge value is not updating in sales order.
    But I have maintain the condition record(Surcharge)also and in Condition technique I have checked every thing is correct .
    please find below I have attached the Screen short .
    Please give me solution Asap.

    Hi Sukdev,
    Have you checked the respective pricing procedure for From and To reference step maintained against the condition type ZSUR?
    Regards,
    T.R.S.Praveen

  • Condition type is not reflecting in sales orders

    hi,
    i have created two condition type like jser (service tax) and other one is jste(service tax +cess) but in pricing procedure jfact  it is reflecting but while making contract order these two condition type is not accessing.
    please help in this connection.

    Hi,
    After Creating the CONDITION TYPES you need to assign the condition types in the PRICING PROCEDURE
    goto the
    SPRO->FINANCIALACCOUNTING>FINANCIAL ACCONTING& GLOBAL SETTINGS>TAX ON SALES /PURCHASE>BASIC SETTINGS--->CHECK CALCULATION PROCEDURE.
    Here select you procedure and assign the CONDITION TYPE
    regards,
    santosh

  • Use condition type 'RC00' to process return sales order

    first, I copy RC00 to RC10 and change its Calculat.type = B(Fixed amount).
    second, I place a sales order to deliver 10 PC(RC10 = 10 USD) to customer and bill 8PC(RC10 = 8 USD) to customer.
    third, I place a return sales order(only return 2 PC) reference to above billing but the RC10's amount is still 8 USD instead of 2 USD.
    I think this is relative to Cond.base value and Cond.control = F(Condition value fixed (billed)) and who can tell me how to realize my purpose?
    tks in advance.

    Hi
    Guess, If you do returns again for two more pieces, again it will determine the same value for RC10.
    Please look into  the areas of 'copy controls - price type' field and also the Calculation type (fixed amount) also.
    Thanks,
    Ravi

  • 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

  • Condion Type "VPRS" should not appear in Sales Order, Inquiry, Contract

    Hi Gurus,
    Normally when you create Sales Order/Inquiry/Contract,  in the Condition Tab VPRS Condition Type will appear and show the cost price of Materail from the Material Master.
    My Client requirement is, VPRS Condition type has to be calculated as "Statistical" Contion but IT SHOULD NOT APPEAR IN THE CONDITIONS TAB IN THE SALES ORDER/INQUIRY/CONTRACT.
    Thanks,
    Bala

    hello, friend.
    try sapnote 105621.  this is about restricting view of condition types (i.e. vprs) in sales orders by creating anauthorization object for cond types..
    i wish to discuss our experience with this, as we had the same business requirement.
    first, we simply deleted vprs from the PP.  this did not affect financial accounting, until the client decided to implement std cost estimates.  we had to bring back vprs.
    now, we did the sapnote, which required joint efforts among SD, ABAP and BASIS.  although we were able to restrict view of vprs in the cond tabs at itm level, this was still visible at header level.  also, a resourceful data encoder can always find ways to view the same in, for example, the document flow or materials movement data.
    however, try this and maybe you will get it right.
    regards.

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

Maybe you are looking for