Regarding condtion type in sales order

HI Gurus i have a requriement
i am giving a manual condition type eg frieght in sales order at header level, in the sales order there
are 8 items the amount i give on header comes to all the items, but i want that only in the header level only as i give it is a nominal amount eg Rs. 400 for the entire order, so it should come only one time in the sales order.
how to do that
Thanks in advance
Rajesh

As i said, there is no way that you can have a value only at the header level.........i have researched a lot about this..
and it is logically not correct as well........any charge should be attributed to an item since it has to be accountable. so system has to divide the values to the items.
As far as printing goes, you can make the frieght print at the totals level in your pricing procedure by making the 'Print' field as 'S' for your freight cond type. This way, it will appear at the bottom and not at the item level.

Similar Messages

  • How to delete header condtion line of sales order by BAPI

    Hi,
    I want to delete the condtion line of sales order header using BAPI "BAPI_SALESORDER_CHANGE",
    it is work well in item level condition type, but it is not work for header condition type. show error message "missing item number" since of pass item number "000000" for header condition line.
    Below is reference source code, thanks in advance.
    *& Report  ZTEST_BAPI_SO_DELETECONDLINE
    *& Sample program to call BAPI_SALESODRER_CHANGE to
    *& delete condition line of so line item
    REPORT  ZTEST_BAPI_SO_DELETECONDLINE.
    ***--- Structures for create BAPI
    DATA: SALESDOCUMENT LIKE BAPIVBELN-VBELN.
    DATA: ORDER_HEADER_INX LIKE BAPISDH1X,
          BEHAVE_WHEN_ERROR LIKE BAPIFLAG-BAPIFLAG,
          SIMULATION LIKE BAPIFLAG-BAPIFLAG.
    DATA: BEGIN OF ORDER_ITEM_IN OCCURS 2.
            INCLUDE STRUCTURE BAPISDITM.
    DATA: END OF ORDER_ITEM_IN.
    DATA: BEGIN OF ORDER_ITEM_INX OCCURS 2.
            INCLUDE STRUCTURE BAPISDITMX.
    DATA: END OF ORDER_ITEM_INX.
    DATA: BEGIN OF SCHEDULE_LINES OCCURS 2.
            INCLUDE STRUCTURE BAPISCHDL.
    DATA: END OF SCHEDULE_LINES.
    DATA: BEGIN OF SCHEDULE_LINESX OCCURS 2.
            INCLUDE STRUCTURE BAPISCHDLX.
    DATA: END OF SCHEDULE_LINESX.
    DATA: BEGIN OF ORDER_CFGS_REF OCCURS 2.
            INCLUDE STRUCTURE BAPICUCFG.
    DATA: END OF ORDER_CFGS_REF.
    DATA: BEGIN OF ORDER_CFGS_INST OCCURS 2.
            INCLUDE STRUCTURE BAPICUINS.
    DATA: END OF ORDER_CFGS_INST.
    DATA: BEGIN OF ORDER_CFGS_VALUE OCCURS 2.
            INCLUDE STRUCTURE BAPICUVAL.
    DATA: END OF ORDER_CFGS_VALUE.
    DATA: BEGIN OF CONDITIONS_IN OCCURS 2.
            INCLUDE STRUCTURE BAPICOND.
    DATA: END OF CONDITIONS_IN.
    DATA: BEGIN OF CONDITIONS_INX OCCURS 2.
            INCLUDE STRUCTURE BAPICONDX.
    DATA: END OF CONDITIONS_INX.
    DATA: BEGIN OF EXTENSIONIN OCCURS 2.
            INCLUDE STRUCTURE BAPIPAREX.
    DATA: END OF EXTENSIONIN.
    DATA: BEGIN OF RETURN OCCURS 2.
            INCLUDE STRUCTURE BAPIRET2.
    DATA: END OF RETURN.
    DATA: TMP_POSNR  LIKE VBAP-POSNR,
          L_KNUMV    LIKE VBAK-KNUMV,
          L_KSCHL    LIKE KONV-KSCHL,
          L_STUNR    LIKE KONV-STUNR,
          L_ZAEHK    LIKE KONV-ZAEHK.
    ***--- Selection
    PARAMETERS: P_VBELN LIKE VBAK-VBELN OBLIGATORY MEMORY ID AUN DEFAULT '7000510', "'0001007443', " SO
                P_POSNR LIKE VBAP-POSNR OBLIGATORY DEFAULT '000000' , " so item
                P_CONDN LIKE  KONV-KSCHL  DEFAULT 'ZOSP',    " condition type
                P_CONDI LIKE  KONV-ZAEHK  DEFAULT '01',      " Condition item number
                P_TEST  AS CHECKBOX DEFAULT 'X'.             " test mode
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
        EXPORTING
          INPUT         = P_VBELN
        IMPORTING
          OUTPUT        = P_VBELN.
      CLEAR: L_KNUMV.
      SELECT SINGLE KNUMV INTO L_KNUMV
      FROM VBAK
      WHERE VBELN  = P_VBELN.
      IF SY-SUBRC = 0.
        CLEAR: L_KSCHL,L_ZAEHK,L_STUNR.
        SELECT SINGLE KSCHL ZAEHK STUNR INTO (L_KSCHL, L_ZAEHK, L_STUNR)
        FROM KONV
        WHERE KNUMV = L_KNUMV
          AND KPOSN = P_POSNR
          AND ZAEHK = P_CONDI
          AND KSCHL = P_CONDN.
        IF SY-SUBRC <> 0.
          WRITE:/ 'Condition type or condition item is not exist.'.
          EXIT.
        ENDIF.
      ELSE.
        WRITE:/ 'Sales order number is not exist'.
        EXIT.
      ENDIF.
    IF L_ZAEHK IS INITIAL.
          WRITE:/ 'Condition type or condition item is not exist.'.
          EXIT.
    ENDIF.
    SALESDOCUMENT = P_VBELN.     " Sales order number
    ORDER_HEADER_INX-UPDATEFLAG = 'U'.   "U = change sales order
    ***Item Data
    ORDER_ITEM_IN-ITM_NUMBER = P_POSNR.
    APPEND ORDER_ITEM_IN.
    ORDER_ITEM_INX-UPDATEFLAG = 'U'.   "I = add, U= update, D=delete
    ORDER_ITEM_INX-ITM_NUMBER = P_POSNR.
    APPEND ORDER_ITEM_INX.
    ***--- Begin delete a condition line
    ***--- Make sure to use update flag 'D'. Here I = add, U= update, D=delete
    CLEAR: CONDITIONS_IN,CONDITIONS_INX.
    REFRESH: CONDITIONS_IN,CONDITIONS_INX.
    CONDITIONS_IN-ITM_NUMBER = P_POSNR.
    CONDITIONS_IN-COND_ST_NO = L_STUNR.
    CONDITIONS_IN-COND_COUNT = L_ZAEHK.
    CONDITIONS_IN-COND_TYPE  = L_KSCHL.
    APPEND CONDITIONS_IN.
    CONDITIONS_INX-UPDATEFLAG = 'D'.
    CONDITIONS_INX-ITM_NUMBER  = P_POSNR.
    CONDITIONS_INX-COND_ST_NO  = L_STUNR.
    CONDITIONS_INX-COND_COUNT  = L_ZAEHK.
    CONDITIONS_INX-COND_TYPE   = L_KSCHL.
    APPEND CONDITIONS_INX.
    ***--- End delete a condition line
    BEHAVE_WHEN_ERROR = 'P'.
    SIMULATION = P_TEST.   " Test mode or not
    "=== call BAPI
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
      EXPORTING
        SALESDOCUMENT               = SALESDOCUMENT
        ORDER_HEADER_INX            = ORDER_HEADER_INX
        LOGIC_SWITCH                = '    U'
      TABLES
        RETURN                      = RETURN
        ORDER_ITEM_IN               = ORDER_ITEM_IN
        ORDER_ITEM_INX              = ORDER_ITEM_INX
        CONDITIONS_IN               = CONDITIONS_IN
        CONDITIONS_INX              = CONDITIONS_INX .
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'Return code =', SY-SUBRC.
    SKIP 1.
    LOOP AT RETURN.
      WRITE: / RETURN-MESSAGE.
    ENDLOOP.
    Edited by: hank jiang on May 21, 2010 5:07 AM
    Edited by: hank jiang on May 21, 2010 5:25 AM
    Edited by: hank jiang on May 21, 2010 5:27 AM

    SALESDOCUMENT = P_VBELN.     "Sales order number
    ORDER_HEADER_INX-UPDATEFLAG = 'U'.   "U = change sales order
    ORDER_ITEM_IN-ITM_NUMBER = P_POSNR.
    APPEND ORDER_ITEM_IN.
    ORDER_ITEM_INX-UPDATEFLAG = 'U'.   "I = add, U= update, D=delete
    ORDER_ITEM_INX-ITM_NUMBER = P_POSNR.
    APPEND ORDER_ITEM_INX.
    "Begin delete a condition line
    "Make sure to use update flag 'D'. Here I = add, U= update, D=delete
    CLEAR: CONDITIONS_IN,CONDITIONS_INX.
    REFRESH: CONDITIONS_IN,CONDITIONS_INX.
    CONDITIONS_IN-ITM_NUMBER = P_POSNR.
    CONDITIONS_IN-COND_ST_NO = L_STUNR.
    CONDITIONS_IN-COND_COUNT = L_ZAEHK.
    CONDITIONS_IN-COND_TYPE  = L_KSCHL.
    APPEND CONDITIONS_IN.
    CONDITIONS_INX-UPDATEFLAG = 'D'.
    CONDITIONS_INX-ITM_NUMBER  = P_POSNR.
    CONDITIONS_INX-COND_ST_NO  = L_STUNR.
    CONDITIONS_INX-COND_COUNT  = L_ZAEHK.
    CONDITIONS_INX-COND_TYPE   = L_KSCHL.
    APPEND CONDITIONS_INX.
    "End delete a condition line
    BEHAVE_WHEN_ERROR = 'P'.
    SIMULATION = P_TEST.   " Test mode or not
    "=== call BAPI
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
      EXPORTING
        SALESDOCUMENT               = SALESDOCUMENT
        ORDER_HEADER_INX            = ORDER_HEADER_INX
        LOGIC_SWITCH                = '    U'
      TABLES
        RETURN                      = RETURN
        ORDER_ITEM_IN               = ORDER_ITEM_IN
        ORDER_ITEM_INX              = ORDER_ITEM_INX
        CONDITIONS_IN               = CONDITIONS_IN
        CONDITIONS_INX              = CONDITIONS_INX .
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'Return code =', SY-SUBRC.
    SKIP 1.
    LOOP AT RETURN.
      WRITE: / RETURN-MESSAGE.
    ENDLOOP.

  • 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

  • Purchase order type in sales order header

    Dear Friends,
    how can I make purchase order type in sales order header be default.
    With regards

    Hi Vamsi,
    if you want to enter a default value in the purchase order type field in sales order header, then do it by either of the ways
    1. by variant tcode SHD0
    2. by USEREXIT_MOVE_FIELD_TO_VBKD in program MV45AFZZ
    regards,
    Santosh

  • 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

  • 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

  • Add an output type in sales order header

    Hi Dear Experts,
    I try to find a way to add an output type in sales order header after the order was created.
    I also need the output to be sent immediately to the FAX.
    Do you know any BAPI or Function that can help me or have any idea how it can be done?
    Thanks and best regards,
    Sagit.

    Hi,
    You can use the FM ..RV_MESSAGE_UPDATE..
    Thanks
    Naren

  • Exchange Rate type in sales order

    Hi,
    can we see exchange rate type in sales order.
    regards
    sachin

    Dear sachin
    Yes in VA02, select Goto - Header - Sales.  Here at the bottom of screen, you will see a tab "Pricing and Statistics" under which, there is a field "Doc.currency".
    Thanks
    G. Lakshmipathi

  • Where we can see requirement type in sales order.

    Hi
    Where we can see requirement type in sales order ?
    Can we change the requirement type in sales order.
    Thanks,
    KP

    Hi
    1.You can see requirement type in sales order in the Procurement tab.
    2.Yes you can change the requirement type in sales order in the same field.
    Regards
    Vamsi

  • Default valuation type in sale order

    Hi,
    We have some materials which are split valuated. We need to have default valuation type which will appear in the sale order when we create sale order for that material.
    At present it looks that SAP does not have any provision to provide the valuation type defaults for sale order.
    Does anybody know if we can set up default valuation types for sale order and how to do this?
    Thank you for all your help.
    Thanks,
    -Shekhar

    Hi Shekhar
    Please check wheteher split valuation is applicable for FG
    Coz split valution is used in cases
    Split valuation is necessary if, for example:
      Stock from in-house production has a different valuation price than externally procured stock.
      Stock obtained from one manufacturer is valuated at a different price than stock obtained from another manufacturer.
      Different batch stocks of a material have different valuation prices.
    Check whether the Valuation Class ,Catogory is assigned to the Valuation area.
    Also Refer the Follwoing thread:
    Split valuation not possible for FG
    And the help Doc
    http://help.sap.com/printdocu/core/print46c/en/data/pdf/LOMDMM/LOMDMM.pdf
    regards
    Shailesh Meshram

  • What is the IDOC Basic Type for sales order creation

    Hi Experts,
    Can anyone tell me Idoc Basic type for sales order creation.
    Thanks
    Prashant

    Hi,
    The basic types for creating the order are:
    1.Orders01
    2.Orders02
    3.Orders03
    4.Orders04
    5.Orders05.
    The basic type for SIS order is:
    SISCSO01.
    Regards,
    Krishna.

  • 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

  • Default document currency as per document type for sales order

    Dear All,
    We are facing problem in Default document currency as per document type for sales order,
    Our requirement is not to give currency in customer master & set it as default document currency as per document type,
    for example: Document type 'OR' default currency 'INR',
                         Document type 'ZEU' default currency 'EUR',
                         Document type 'ZUS' default currency 'USD',
                         Document type 'ZNP' default currency 'NRP,'
                         Document type 'ZAF' default currency 'RAND,'
    Is it any how possible in standard setting ?,
    Regards,
    Sai

    Hi,
    The system proposes the sales document currency from the customer master record of the sold-to party. You can change the currency manually in the document or change in currency in customer master. If you change the currency, the system recalculates prices for the entire document.
    to determine different currrency in sales docuement you need to write an user exit and then overwrite the docuement currency copied from customer master. Try user exit 'USEREXIT_MOVE_FIELD_TO_VBAK' under include MV45AFZZ for this change.
    with regards
    vivek.

  • Requirement type in sales order

    hi sap gurus,
    i want to know how requirement type is configured and how it conmtroll the scenario in MAKE TO ORDER scenario. previously i have seen that with requirement type in sales order Procurement tab, system determine the planning statergy and it determine the special stock type of material, e.g. E for sales order stock and Q is for project stock. but i want to know whether this is correct or not and how this is happenning i.e. what is the configuration and assignment.
    please help at earliest.
    biplab rout

    Hi,
    Check this thread
    Re: Requirement type
    Re: requirement type and requirement class
    Thanks,
    Raja

  • 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

Maybe you are looking for

  • Profit Center missing in FAGLFLEXT and FAGLFLEXA

    Hi All, I am trying to download FAGLFLEXT data via SE16, and realized that the profit center is blank, although it appeared in the document display (FAGLB03). The same thing also happen to FAGLFLEXA. Is this a normal behavior or it is because of miss

  • GR Purchase Order has No Item

    What could be possible reason for the message "Purchase Order xxx has no item" Already Figured Closed PO (Delivery completed) Thanks in advance.

  • How to include validation attribute (xmlns:xsi) into the resulting XML ?

    Hi, I'm having a problem including the validation schema attribute (xmlns:xsi) into the resulting XML. For example, if I have the following schema: <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <xs:element nam

  • G Raid Setup

    Hello I just included a G Raid external drive to my edit system. I'll be using it for some of my long-term DV projects. When editing projects with media stored in the G Raid, should I set the system settings so that the render files go to the G Raid

  • Remove "Sales Office" from VA01 screen

    Hello All, We're using 4.6C and the initial VA01 screen consists of: Order Type Sales Organization Distribution Channel Division Sales Office Sales Group However, I'd like to remove Sales Office and Sales Group from the initial screen. Is there a way