Flowing of the Condition  type from Sales Order to invoice

Dear All,
I'm facing a problme in the copying the condition types from Sales order to Invoice.
The details are as mentioed below:
I have a Condition type CONC and made the Copy of the Condition typs as ZDIS.So that CONC's value will be debited and ZDIS' value will be credited in the FI..
But ALL the condition types which i have mentioed including tax and discounts condition types are copying from Sales order to invoice.Except CONC.
I have checked all the copy controls,i'm sure those are OK.Bcoz other condition types are working perfectly fine.
What could be the reason for this???
Will be any setting for on condition type level for copy controls???
Please Guide me its URGENT.
Thanks
Vinay

hi
from which condition type u have copied this CONC , can u pl elaborate more on this.
and just write what is exact scenario and whats going wrong?
in copy controls check for pricing source and pricing type.
regards
mandar

Similar Messages

  • Forgot to put ZPNT (Penalty condition type) in sales order

    Dear Expert,
    We have created sales order and billing document has been sent to customer,after that we came to know tht we forgot to put ZPNT Condition type in sales order. Now i want to create another sales document with reference to billing document, in which only ZPNT Condition type will be appear (not other condition) and thn will create billing document with reference to new sales order so that ZPNT amount goes to the right ledger A/C......Is it the right process to solve this problem if yes thn please advise me how to fonfigure the system.
    Regards
    Parul Deshwal

    hi Parul,
    rather than doing this which is quite complecated process
    saying complecated because, when u do Copy from billing to sales document all condition will appear and might be there r some mandatory conditions in pricing procedure which you can not remove.
    Above all, IF your condition ZPNT value is based on some other conditions then also it will not be possible for you to calculate it correctly.
    there is one more possible way by creating DEBIT NOTE with reference to sales order but again you might have to face above mentioned problems
    So better you follow standard and easy method
    1. Reverse the billing document if PAYMENT is not posted
    2. Reverse the Delivery (if any)
    3. add your condition type to sales order for line item and create it
    Regards

  • Condition update error  :There is no condition update from sales orders.

    I am testing the condition update by condition type K005 , which have been set the condition update indicator ,and I have also set the Max.number.of.orders  to 1 , but after I created the first sales order ,the condition record still make effect in the second  and third sales order ,which was created without referece to the first one .
    And  when I  look at the cumulative value in the condition record ,it says "There is no condition update from sales orders."
    Anyone can give me some light ?
    BTW , the sales order type is ZOR ,which I copy from the standard order type .And the item category is ZTAN , copy from  standard IC TAN .
    thanks for your help in advance .

    hello, friend.
    there are at least 3 things that you will have to check, since records for condition type K005 is created for a specific combination:
    1.  check if the item category with condition update was the one determined in the order
    2.  check if the customer has a valid K005 record
    3.. check if the material has a valid K005 record
    also, since you specified "1" as maximum number of orders, this could have prevented any updates.
    regards.
    Edited by: jonathan y on Sep 17, 2009 2:59 PM

  • How to Avoid Duplicate Pricing Condition Types In  Sales Order and Billing

    Hi SAP Gurus
    I have a requirement in Pricing (Sales and Distribution). We have  issue duplicated condition types in Sales order and it causes wrong posting in to accounts.
    I want make them inactive duplicated Condition type in Sales order and Billing Documents.
    Please advice me how to make inactive status to duplicated Condition types
    Thanks  in Advance.
    Ravikanth

    Hi
    You can use Exclusion Group
    You can define 2 Groups and include 1 condition type in each
    and define exlusion procedure
    A   Best condition between condition types                
    B   Best condition within the condition type              
    C   Best condition between the two exclusion groups       
    D   Exclusive                                             
    E   Least favorable within the condition type             
    F   Least favorable betweent the two exclusion groups     
    you can use Exclusive to set your condition type or as per your requirement
    Regards
    Jitesh

  • About hide special condition type in sales order condition screen

    Hi all,
        I have such requirement:
        Customer want to hide some condition type in sales order condition screen.
        I have tried the authrization object :V_KOND_VEA  but it only controll the master data level
        and the special still show on the condition table.
        I have also find any user exit in SD module:
        USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA)
        But it looks like a system modification, and need the modification key.
        So, is there any solution such as enhancement or configuration to meet this requirement?
    Many , thanks.

    Check this thread where similar requirement was discussed
    [Condition Type |Condition Type]
    thanks
    G. Lakshmipathi

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

  • User Exit for eliminating double condition type in sales order

    Sir,
    In SE38,  Program SAPMV45A,  I am using user exit ( Userexit_pricing_prepare_tKomp )  to avoid double entry
    of condition type like PR00 in sales order . But i am not getting how to write code.
    Please, help me how to write code in user exit.
    thanks,
    Manoj.

    Thanks for replay.
    Sir, I want to impliment it in sales order (VA01 OR VA02 )
    for pricing  . Here I want to avoide double  condition types like PR00, packing forwarding, frieght ....etc
    in  sales order pricing.
    Here i want to give logic that codition type is already exit and you canot enter same condition type
    again. means if condition type is already exit then system should not allowed to enter again the same condition type
    in sales order pricing.
    Thanks
    Manoj.

  • How to update the condition price in sales order while creating the invoice

    Hi,
    How to update the condition price in the sales order to carry out the new price while creating the invoice?
    While creating the invoice it should update the condition price in sales order.
    Thanks,
    Balaram

    No, pricing is not there in delivery.
    I found an exit for VF01transaction where we can update the price in order.
    Can you please tell me how to update the price if I have the order, material numbers and conditions number?
    Thanks,
    Balaram

  • How can prevent duplication of condition types in sales order??

    How can prevent duplication of condition types in sales order.
    While we want Amount field Changeable by user.
    Please give me solution.

    Dear Rohit,
    Can you explain your scenario in detail with an example or any screen shot so that we will help you in easy way ...
    Regards,
    C.B Reddy

  • Budget control in project WBS'e  while creating the auto PR from Sale order

    Hi experts,
    we are creating the auto pr from sales order for trading process with budget wbs element. but commitment is not posted in project wbs were as pr is created through sale order
    pls suggest if any additional setting is required  to post commitment while creating auto pr from sale order.
    rgds
    rajesh

    Check account assignement categories in SD for PR creation and See if you can make PR to be created with WBS as account assignement like we do in OPTT.

  • Sales Office copying from Sales order to Invoice ( order related billing)

    Hi
    In sales invoice (vf01) is there any field for Sales Office.
    In order related billing . how we can copy sales office from sales order to Invoice.
    Regards\Adnan

    Hi Adnan,
    In Invoice you can find Salees office filed In the Item data >in the Item Detail tab>under Sales Order Data here you can get the sales office which you enter in the sales order.
    I hope it will help you,
    Regards,
    Murali.

  • Condition type in sales order - enhance extractor

    Can anyone help me in enhancing field condition type for sale flow. I need to filter sales orders with condition type 'minimum order surcharge' in BI.
    There is KONP table having condition type field.
    Do I need to enhance VAHDR or VAITM. Please help.
    Thanks

    If orders are to be filtered then both Order Header (VAHDR) and Order Item (VAITM) should be enhanced.
    But I'd strongly recommend not to filter out the orders at the time of extraction/loading (in info-pkg).
    It is better to do the filtering in the report itself.
    Hope this helps.

  • Copy condition from sales order to invoice ?

    Sorry for this very general question, but i need a starting point for my development. It is partly functional and partly technical. Data transfer or copy requirements are probably needed.
    The situation is :
    Sales order with a condition type and value (manual entry)
    -->
    Delivery without that condition type
    -->
    Invoice (Intercompany) should get the condition type (with same value) from the related sales order
    I think that the condition type also should be added to the pricing procedure of the invoice ?
    How can i arrange that if the condition type exists on sales order is copied to the invoice at creation ?
    regards,
    Hans

    Hello saurabh,
    thanks for your reply, as you said, I can create the same PP in SD and determine in IV, but the issue which I am facing is I am capturing mkt mvg price from material master in my PO.  Once the PO is raised, IV can be done after some time, whereing there is a huge chance, that mvg avg price from MM can be changed.  Now if I determine a PP in billing, the price in billing doc and PO will be different.
    So, I have to have capture the value from PO to billing.....
    Any help is much appreciated.
    Thanks in advance
    AKASH

  • Need to find where to retrieve conditon types from sales orders

    Sorry if this should be under data dictionary.
    I am trying to find out how to retrieve the pricing elements from the sales order/invoice. The ultimate goal is to create a list of all customer/materials that were purchased with a certain condition type.  From the condition tab of the sales order, the technical information shows the sturcture KOMV and field name KSCHL for the condition type column.
    Thanks for any help!
    Rick

    Halo Richard,
    The table name is KONV .
    If you are looking out for relating Purchasing side with KONV table , then  EKKO/EKPO tables have KNUMV which has corresponding foreign key entries in KONV table also
    If you are looking out for relating Sales side with KONV table , then  VBAK/VBRK  tables have KNUMV which has corresponding foreign key entries in KONV table also
    Regards
    Arshad

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

Maybe you are looking for