Condition types in Sales order creation process

Hi Friends...
While creating the sales order with BAPI,
What is the condition type i have to pass for pricing procedure...
There many condition types for my pricing procedure, which one o have to select...
Some of them are mannual, and other reuired, which one I have to pass?
I want the information related to this condition types.., as here no SD consultant availble for me.
Sales order creation, Line item error
Thanks,
Naveen.I

Hi Friends...
   Please let me know is it mandatory to give condtion type while creating the sales order...?
I am using BAPI_SALESORDER_CREATEFROMDAT2  to create my sales order...
http://www.sap-img.com/abap/bapi-salesorder-createfromdat2.htm
Thanks,
Naveen.I

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

  • What are the User Exits for Sales Order creation process?

    Hi,
    what are the User Exits for Sales Order creation process? how can I find them?
    thanks in advance,
    will reward,
    Mindaugas

    Please check this info:
    User Exits In Sales Document Processing
    This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
    Involved program components
    System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
    MV45ATZZ
    For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
    User exits in the program MV45AFZZ
    The user exits which you can use for modifications in sales document processing are listed below.
    USEREXIT_DELETE_DOCUMENT
    This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
    For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
    The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
    USEREXIT_FIELD_MODIFICATION
    This user exit can be used to modify the attributes of the screen fields.
    To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
    The usage of the field groups (modification group 1-4) is as follows:
    Modification group 1: Automatic modification with transaction MFAW
    Modification group 2: It contains 'LOO' for step loop fields
    Modification group 3: For modifications which depend on check tables or on other fixed information
    Modification group 4: is not used
    The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
    This FORM routine is called up by the module FELDAUSWAHL.
    See the Screen Painter manual for further information on structuring the interface.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBAP
    Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBEP
    Use this user exit to assign values to new fields at the level of the sales document schedule lines.
    The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    USEREXIT_PRICING_PREPARE_TKOMK
    Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
    USEREXIT_PRICING_PREPARE_TKOMP
    Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
    USEREXIT_READ_DOCUMENT
    You use this user exit if further additional tables are to be read when importing TA01 or TA02.
    The user exit is called up at the end of the FORM routine BELEG_LESEN.
    USEREXIT_SAVE_DOCUMENT
    Use this user exit to fill user-specific statistics update tables.
    The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
    Note
    If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    User exits in the program MV45AFZA
    USEREXIT_MOVE_FIELD_TO_KOMKD
    Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMPD
    Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMKG
    Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_MOVE_FIELD_TO_KOMPG
    Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_REFRESH_DOCUMENT
    With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
    For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
    The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
    The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
    User-Exits in program MV45AFZB
    USEREXIT_CHECK_XVBAP_FOR_DELET
    In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
    USEREXIT_CHECK_XVBEP_FOR_DELET
    In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
    USEREXIT_CHECK_VBAK
    This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
    USEREXIT_CHECK_VBAP
    This user exit can be used to carry out additional checks (e.g. for completion) at item level.
    USEREXIT_CHECK_VBKD
    The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
    USEREXIT_CHECK_VBEP
    This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
    USEREXIT_CHECK_VBSN
    You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
    USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
    USEREXIT_FILL_VBAP_FROM_HVBAP
    You can use this user exit to fill additional fields in the sub-item with data from the main item.
    USEREXIT_MOVE_FIELD_TO_TVCOM_H
    You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    USEREXIT_MOVE_FIELD_TO_TVCOM_I
    You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    User-Exits for product allocation:
    The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
    USEREXIT_MOVE_FIELD_TO_COBL
    Option to include new fields in structure COBL.
    USEREXIT_COBL_RECEIVE_VBAK
    Option to assign values from the document header to the new fields.
    USEREXIT_COBL_RECEIVE_VBAP
    Option to supply values from the item to the new fields.
    USEREXIT_COBL_SEND_ITEM
    A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
    USEREXIT_COBL_SEND_HEADER
    A changed field can be copied from the structure to the header (see source text MV45AFZB)
    USEREXIT_SOURCE_DETERMINATION
    You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
    USEREXIT_MOVE_FIELD_TO_ME_REQ
    With this user exit you can include additional fields for the following fields:
    EBAN (purchase requisition)
    EBKN (purchase requisition-account assignment)
    USEREXIT_GET_FIELD_FROM_SDCOM
    Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
    USEREXIT_MOVE_WORKAREA_TO_SDWA
    You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
    User-Exits for first data transfer:
    The following user exits can only be used for the first data transfer.
    Note
    Only use the user exits if the names/fields do NOT have the same name.
    USEREXIT_MOVE_FIELD_TO_VBAKKOM
    Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
    USEREXIT_MOVE_FIELD_TO_VBAPKOM
    Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
    USEREXIT_MOVE_FIELD_TO_VBEPKOM
    Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
    USEREXIT_MOVE_FIELD_TO_VBSN
    You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
    USEREXIT_MOVE_FIELD_TO_KOMKH
    You can use this user exit to include new fields for batch determination (document header).
    USEREXIT_MOVE_FIELD_TO_KOMPH
    You can use this user exit to include new fields for batch determination (document item).
    USEREXIT_CUST_MATERIAL_READ
    You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
    USEREXIT_NEW_PRICING_VBAP
    Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
    USEREXIT_NEW_PRICING_VBKD
    Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
    User-Exits in Program MV45AFZD
    USEREXIT_CONFIG_DATE_EXPLOSION
    The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
    User exits in the program FV45EFZ1
    USEREXIT_CHANGE_SALES_ORDER
    In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
    If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
    User-Exits in Program RV45PFZA
    USEREXIT_SET_STATUS_VBUK
    In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
    The following workareas are available for this user exit:
    VBUK (header status)
    FXVBUP (item status)
    FXVBUV (Incompletion)
    USEREXIT_SET_STATUS_VBUP
    In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
    The following workareas are available for this user exit:
    FXVBAP (Item data)
    FXVBAPF (Dynamic part of order item flow)
    FXVBUV (Incompletion)
    USEREXIT_STATUS_VBUK_INVOICE
    You can use this user exit to influence billing status at header level.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    User Exits in Program MV45AFZ4
    USEREXIT_MOVE_FIELD_TO_KOMK
    You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
    USEREXIT_MOVE_FIELD_TO_KOMP
    You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
    User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
    EXIT_SAPFV45P_001
    You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
    Regards
    Eswar

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

  • 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

  • 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

  • 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

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

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

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

  • Get condition prices before sales order creation

    Hi Experts,
    I have a non-SAP system which needs price information from SAP.
    As we know, in SAP after Sales order creation, the prices can be found in item condition tabs. All condition records and prices can be found.
    Now, before the non-SAP system sends data to SAP for sales order creation, non-SAP needs the condition record and prices same as after sales order creation.
    seems i have to write code in SAP for the logic of price determination. i assume that will be a big work.
    so i'm supposing whether we can get the condition from the bapi for sales order creation. i can mask testrun = 'X', then get the conditions. but i tried creating sales order in code and found the condition - ORDER_CONDITIONS_IN is not populated.
    anyone got a idea to solve this?
    Thanks a lot.
    Legend Lee.

    Hi,
    If you run the BAPI under the same conditions but without the text flag checked do you get anything returned? Are there any messages in the RETURN table?
    There are a number of OSS notes on this BAPI e.g. 93091 if you search on service.sap.com. The answer may lie in the pricing configuration; that the BAPI is not designed to work how you want it to work or a parameter has not been specified correctly.  You could look at FM SD_SALESDOCUMENT_CREATE and try and use that however it is not released. Unfortunately I canu2019t give you a definitive answer or solution.
    Regards, David

  • Replacing Profit Center value while sales order creation process - VA01

    Hi,
    Profit Center replacement   in Tcode VA01 and VA02
    I want to replace the profit center value (COBL- PRCTR) in Account assignment TAB in sales order creation time VA01 and VA02 by using custom logic (Line item Material Group and Sales District VBKD-BZIRK).
    Can anyone tell me what exit or BADI I can use for this ( I tried some of them and not working properly).
    1.     In Exit I need to have the value of Sales District VBKD-BZIRK and Line item u2013 Material Value  - These 2 field values I need in the exit.
    Thanks in advance.
    Rajesh.

    What do you mean this is not correct user exit. That is an include and there are user exits within that include.
    Have you tried save document prepare?  If yes, what have you done?
    Don't just blindly say 'that is not correct' or don't expect someone code for you. You better try in different way and learn how to do it. I just got it worked in my system just in 5 minutes in debug.
    You are not going to change COBL-PRCTR but you should change XVBAP-PRCTR.
    put a break point in userexit_save_document_prepare in include MV45AFZZ
    Loop through XVBAP and change PRCTR as per your logic.... This changed PRCTR carried till end (billing document/accounting document). I can see the profit center document with changed profit center.
    Good luck... if that solves. Mark this thread appropriately.
    Most importantly, you better close your previous threads if they are answered. if you solved by yourself post the solution so that others can benefit from that. 
    @moderator, please check this guy posts
    Edited by: Sampath Kumar on Apr 28, 2011 1:16 PM

  • Sales Order Creation Process.....!!

    All,
    I have been trying to call "BAPI_BUSPROCESSND_CREATEMULTI" remotely (from .Net environment with SAP .Net Connector ). I understand this is the FM, which is being called from most of other important FM, like BAPI_ACTIVITYCRM_CREATEMULTI or from Sale Order creation BAPI.
    Anyway the issue I am facing is that, I have to call "BAPI_BUSPROCESSND_PROCSETTINGS" before calling "BAPI_BUSPROCESSND_CREATEMULTI" to persist the data in Data base tables (even if I am using Transaction Commit).
    While calling these FMs remotely, if I call "BAPI_BUSPROCESSND_PROCSETTINGS" and then "BAPI_BUSPROCESSND_CREATEMULTI", it does not work. But If make a wrapper BAPI in CRM with call to "BAPI_BUSPROCESSND_PROCSETTINGS" and then to "BAPI_BUSPROCESSND_CREATEMULTI" within the same LUW, it works.
    Now my problem is that I want to use Std BAPIs only (like "BAPI_BUSPROCESSND_CREATEMULTI") and don't want to use any wrapper BAPI..
    Anybody could guide me how to surmount the issue I am facing..?Also if somebody knows what this "BAPI_BUSPROCESSND_PROCSETTINGS" is suppose to do?
    Thanking all in advance....

    I had faced the similar issue while calling the RFC's exists remotely.
    I was calling couple of BAPI's in the same session and failing to commit the work in the same LUW.
    I have resolved it by calling BAPI_TRANSACTION_COMMIT sequentially in the same LUW.Try to do this.
    Do you mention the 'DESTINATION' parameter to the BAPI's ?
    And using wrapper RFC's is also recommended.
    Thanks,
    Thirumala.

Maybe you are looking for