Capture the purchase price during sales order creation

Hi,
User wanted to capture the item purchase price when a sales order is raised.
Currently, the sales order capture the VPRS whcih is coming from the material valuation (MAP) price.
Is there a standard condition type that will captured the purchase price in the PIR record or the PP condition?
Thanks

Hi
As far as i know it is not possible to fetch the purchase price in sales order.
May be you can define an another condition type asa statistical and maintain the condition records for that. But it will be a tedious job for maintaining all the things.
regards
Prashanth

Similar Messages

  • How to export the material list during sales order creation

    Hello,
    In VA01 while creating Sales Order is there are an option to export a list of material numbers at one shot?
    I have about 400 materials to create in 1 sales order. It's time consuming to enter one by one manually.
    Please help. Will reward points.
    Pri

    Hi Pri,
    Go to VOV8 transaction check the document type PV -Itemproposal if not there then define the document type for Itemproposal.
    You copy the Standard OR type do these settings only
    Sales document type PV Item proposal
    SD document categ. D
    Screen sequence grp. MA
    Transaction group 5
    Doc. pric. procedure C
    Display Range UALL
    FCode for overv.scr.UER1
    Propose deliv.date give chek mark    
    Define the number range and assign number range.
    Noe you try
    I hope it will help you,
    Regards,
    Murali.

  • Dump during sales order creation for a config material (uding order BOM)

    Dear all,
    I am getting the following error during sales order creation for a configurable material
    When I click on 'Engineering' tab in the characteristics value assignment for the parent material i.e. sales order material I get dump with following message,
                                   'Field symbol has not yet been assigned'
    Thanks,
    Yogesh

    Yogesh,
    what was the problem ?
    Thanks,
    Pavan Verma
    Edited by: Pavan Verma on May 11, 2010 9:31 AM

  • 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

  • Update error in  RV_SALES_DOCUMENT_ADD during Sales order creation

    I get an Update/ ABAP runtime error during Sales order creation. The error occurs during processing of the update module -RV_SALES_DOCUMENT_ADD.
    This error does not occuring always, as I am sometimes able to create a Sales order without getting update error. I am getting the error of all types of Sales orders and even contracts.
    Am I missing any configuration parameters?
    Thanks,
    Chitra

    Yes , I can see the error in ST22.
    While exceuting VA01 (Oder type OR, Entering Sold-to-party, Purchase order NO, Material, Qty, Plant),
    - I get run-time error "Run-time error "GETWA_NOT_ASSIGNED" occurred".
        Analysis of error shows:
         Update terminated in "Update module: RV_SALES_DOCUMENT_ADD"
          Fails in the Read table in one of the form
            Termination occurred in the ABAP program "SAPLV45U" - in "VBAP_BEARBEITEN"
    The main program was "RSM13000 ". In the source code you have the termination point in
    line 147 (READ TABLE FYVBAP WITH KEY VBAP_KEY.)
    of the (Include) program "LV45UF0V".
    The ABAP's say the functional module is trying to do an 'UPDATE' instead of 'INSERT" in the internal table FYVBAP.
    Thanks,
    Csuman

  • 100% advance payment during sales order creation

    Dear Experts,
               One of our international client is having one requirement for collecting the 100% advance payment from customer during sales order creation itself. Our customer is in Germany.
    For high risk customers they want to collect the advance payment for 100%. And if this 100% advance payment was not paid by customer then, sales order should not be processed.
    And during regular sales invoice creation the same down payment also needs to be displayed in the invoice as advance payment.
    Is it possible to setup this process using milestone billing.?? .or some other process is available to setup this process.
    Thanks for your cooperation.
    Warm Regards,
    Velmurugan

    Hi
    Try with this with Credit management.Put High Risk with Error message.
    When ever you will Create Sales Order it will Block due to Credit Chech.For this scenario Enter the Parking  Vale at F-66.
    Then make a entry for Customer-CR to BANK-DR.
    This may solve ur requirement.
    Regards
    JS

  • How to Overrride ATP values during sales order creation

    Hi all,
    How i override ATP values during sales order creation.
    The scenario is that we need to migrate open orders from an existing legacy system to SAP.
    While migrating these orders, we need to make sure that dates on the schdule lines are same as they are in the old system. Hence we need to override ATP.
    Any suggestion welcome..
    Regards,

    Hi Kantur Shekar madhuri,
    Would you confirm the whether in your schedule line category is activated for "Product Allocation" or not.
    if not please activate and re run your scenario.
    Regards
    Arun

  • Capacity check during sale order creation

    hi,
      i have the following doubts,
    1. During sale order creation i need capacity availability check for that i make settings, its working good,if i put the order in the evening time but system take the start time as morning shift starting time.can any one guide me to take the time as the order creation time. and also help me how the system check the capacity.
    2. During sale order creation , if suppose capacity is loaded means it will show a pop up with the name capacities with overload,
      Here i need the clarification how the system calculate the requirements and requirements order, capacity load, from where the system get the information for these calculation.
    Muthamil

    Hello, you are working with a make to order scenario, that means that a planned / production order must be created to address specifically your customer requirement ??
    By standard SAP you can have a capacity availabily check once the production order is in the creation phase....but this should be too late for you.....

  • BADI triggered during sales order creation

    Hi,
    Can any one please let me know the BADI triggered during sales oredr creation and  sales order change.
    Thanks

    <b>BADI for VA01:</b>
    ALV_SWITCH_GRID_LIST     ALV: Customer Exit for Switch Grid to Li
    BADI_ISPS_GRANT     BADI for IS-PS Grant Management
    BADI_SD_DMC_ORDER     BADI for Dispute and Collection Manageme
    BADI_SD_DPBP     Extensions in SD for DP90 with Billing P
    BADI_SD_DSD_ORDER     BADI for Direct Store Delivery
    BADI_SD_MENUE_FM     Menu Enhancement for Fund Management (FM
    BADI_SD_MENUE_TPM     Menu Enhancement for TPM Retrofit
    BADI_SD_SALES     General Enhancements for Sales Order Pro
    BADI_SD_SALES_BASIC     Enhancements for Sales Order Processing
    BADI_SD_SALES_ITEM     Enhancements for Sales Order Processing
    BADI_SD_TAB_CUST_H     Tab Page for Own Details - Header Detail
    BADI_SD_TAB_CUST_I     Tab Page for Own Data - Item Detail Orde
    BADI_SD_TO_FM     Commitments Management in SD for Funds M
    EHS_DG_002     EHS: Template Material Processing - Inte
    EHS_PS_002     EHS: Call Report Information System from
    EHS_PS_002     EHS: Call Report Information System from
    EHS_PS_002     EHS: Call Report Information System from
    SD_COND_ACCESS_A     Access in Pricing (replacement)
    SD_KONV_SELECT     Addition to Data When Reading KONV
    SD_PRICING_COPY     Enhancement for Copying Document Conditi
    VBX_SO_SEL_CRITERIA     Batch Selection Criteria in Sales Order
    <b>BADi for VA02</b>
    ALV_SWITCH_GRID_LIST     ALV: Customer Exit for Switch Grid to Li
    BADI_ISPS_GRANT     BADI for IS-PS Grant Management
    BADI_SD_DMC_ORDER     BADI for Dispute and Collection Manageme
    BADI_SD_DPBP     Extensions in SD for DP90 with Billing P
    BADI_SD_DSD_ORDER     BADI for Direct Store Delivery
    BADI_SD_MENUE_FM     Menu Enhancement for Fund Management (FM
    BADI_SD_MENUE_TPM     Menu Enhancement for TPM Retrofit
    BADI_SD_SALES     General Enhancements for Sales Order Pro
    BADI_SD_SALES_BASIC     Enhancements for Sales Order Processing
    BADI_SD_SALES_ITEM     Enhancements for Sales Order Processing
    BADI_SD_TAB_CUST_H     Tab Page for Own Details - Header Detail
    BADI_SD_TAB_CUST_I     Tab Page for Own Data - Item Detail Orde
    BADI_SD_TO_FM     Commitments Management in SD for Funds M
    EHS_DG_002     EHS: Template Material Processing - Inte
    EHS_PS_002     EHS: Call Report Information System from
    EHS_PS_002     EHS: Call Report Information System from
    EHS_PS_002     EHS: Call Report Information System from
    SD_COND_ACCESS_A     Access in Pricing (replacement)
    SD_KONV_SELECT     Addition to Data When Reading KONV
    SD_PRICING_COPY     Enhancement for Copying Document Conditi
    VBX_SO_SEL_CRITERIA     Batch Selection Criteria in Sales Order
    Regards,
    Nilesh

  • Can u tell me any bapi to create the purchase req with sales order as refer

    can u tell me any bapi to create the purchase req with sales order as reference?

    Hi Mukesh,
    You can use 'BAPI_REQUISITION_CREATE' for the purchase requisition creation if through transaction, you use transaction ME51N for creating the purchase requisition.
    Cheers,
    Sujay

  • 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

  • User Exit during Sales Order Creation - New Line Item needed

    I have a situation during the process of sales order creation. If a Material in a line item has say 27 EA and the Base Unit is EA. But the Sales Unit is CSE. Then whenever the user enters 27 EA and presses enter he should get two line items.
    The first line item needs to convert to maximum number of CSE posible and the rest will be the second line item with the remaining EA. The order isn't important but that is what is needed. Question is how do I approach this problem and code my user exit accordingly and where do I code it.
    I was looking at SAPMV45A and saw the program MV45AIZZ which is meant as a user exit for any PAI event handling. If anybody has encountered this kind of requirement can you please share your view on this.
    I will definitely reward points for useful answers.
    Clark

    Hello Mahendra
    The requirement is as follows :
    PART 1:
    Sales Order Enter: 
    1.     When a line item is entered on a sales order (VA01 or VA02), at enter, check the sales unit of measure (VBAP-VRKME).
    •     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP.  TANN are free goods that should not be considered for consolidation.  TAPS & ZTAP are lower level materials as a result of product selection.  They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
    •     Do not check items where VRKME <> EA
    2.     If VRKME = EA, go to MARM for MATNR.
    3.     Go to record where alternate unit of measure (MEINH) = CSE, get the value from the numerator field (UMREZ).
    4.     Divide the order quantity (VBEP-WMENG) by UMREZ.
    5.     If the result is greater than 1.0, the customer has ordered more than one case and a new line item needs to be added to the sales order for the case quantity.
    6.     Add a new line to VBAP for the same material with the case quantity.  If not a whole value, the remainder of eaches (bottles) should update the qty on the first item on VBAP.
    •     Part 1 is relevant for order types ZCA, ZOR, ZSO, RE, ZSM
    PART 2:
    Batch Job to run prior to the Delivery Due List:
    1.     Read VBUK for Delivery Status (LFSTK) = A (delivery not processed).  Get all of the document numbers (VBELN).
    2.     Go to VBEP for those document numbers to get the goods issue date for the order.  There will be many records in VBEP for the same sales order.  Look at all orders with a goods issue date (WADAT) of next day.
    3.     Go to VBAK for those document numbers to see if there are multiple sales orders for the same Sold To party (KUNNR).
    4.     For customers who have more than one order in VBAK, search all line items (for all orders).  If there are no duplicate materials across sales orders, do nothing.
    •     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP.  TANN are free goods that should not be considered for consolidation.  TAPS & ZTAP are lower level materials as a result of product selection.  They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
    •     Do not check line items where reason for rejection (VBAP-ABGRU) is not blank
    5.     If there are duplicate materials, go through the same logic as in part 1.  If the quantity across the sales orders adds up to greater than one case, add the appropriate quantity to a new line item on the first sales order.   If there is a remainder qty, update the line item on the first sales order with this qty. In this case, the quantities on the second sales order needs to be closed out with a reason for rejection code of 50, ‘Line Item Consolidation’. If there is no remainder,  update the qty on this item directly.
    •     Part 2 is relevant for order types ZOR, ZCA, ZSM
    •     This batch job will have to be run manually for Day Pick orders.  The end of this program should automatically kick off the delivery due list for Day Pick orders, shipping condition 02.
    Business Justification:
    The business requires that like order line items be consolidated to one line item prior to the order going to the warehouse for picking.  This will aid in picking at the warehouse as well as result in the customer invoice not reflecting more than one line item for the same material.  In the case where the customer has truly ordered more than a case, i.e;, 1 case, 2 bottles, the documents in SAP will still reflect 2 lines.

  • Report purchase price from Sales order to delivery.

    Please, is there anyone knows a solution for a resumption of the purchase price was register in a libne of sales order when we created by the DI API corresponding delivery ?
    Edited by: Rui Pereira on Dec 23, 2008 3:08 PM

    Hi Jane,
    Thank for your answer.
    In my sales order, the purchase price is the field GrossBuyPr.
    But when I create a new delivery from this sales order the price is take from Item.
    I used DI_API, because in my sales order, delivery's quantity is an user field. I generates the delivery with an addon.
    Best regards.
    Patrick
    Edited by: Rui Pereira on Dec 23, 2008 2:58 PM

  • Withholding Tax Selection during Sales order creation

    Hi,
    Do we have an option to select or deselect Withholding Tax Codes at the time of Creating Sales order / Billing for the Customer?
    As, We get the popup during the time of invoice creation to the vendor.
    Your inputs are appreciated.
    Thanks & Best Regards
    Shashikanth.M

    Hi,
    Refer the below OSS note:-
    [https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=178824]
    Regards,
    Gaurav

  • One Time Customer Mandatory field during Sales Order Creation

    Hi
    My client has lots of one time customer and they need to capture the phone number  and name of the individual customer at the time of sales order creation using one time customer code.
    They want only "NAME & PHONE NO" as mandatory field so that the Person who creates a Salesorder should enter the NAME & PHONE NO" . Please let us know where the configuration for teh above is?
    We have tried in Account Group One time customer settings which is working at the time of creation of order and not at the time of creation of Sales Order, please help us on the above..
    Regards
    Anis

    Hi Anis,
    In the Account group , if you check the one-time customer then while creating the sales order itself it will appear to change the address for that customer.
    By the time you can enter your required fields.
    I think you mentioned as
    We have tried in Account Group One time customer settings which is working at the time of creation of order and not at the time of creation of Sales Order, please help us on the above..
    Order creation and creation of sales order are both same.
    May be you would have confused.
    regards,
    santosh

Maybe you are looking for