Missing data: Profitability segment no. in Sale order creation

Hi Gurus,
while creating a Sales order, I am getting the Below Error;
"Error while the Operating Concern being determined"
Massage no: KE/AD817
Error: Missing data: Profitability segment no.
Its Urgent..
Can anybody suggest....
Thanks
BKT

Hi Bani,
Please check if note 380102 helps in this case. From the long text of the error message you can find out which charachteristic is responsible for the error message.
Regards,
Abhisek

Similar Messages

  • Profitability segment No in Sales Order

    Hi All,
    While I am creating Sales order the following incomplete data error occurs;
    Missing data:Profitability segment No
    Message No:VU019
    Diagnosis
    The system checked the document for completion and found some missing data.
    You cannot continous the process,
    Pls anyone aware of this issue.
    Likely the setting will  be missing  in CO-PA area configuration.
    Thanks,
    Thiru

    HI,
    Case 1: if you do not have the profitability segment in the incompletion procedure of the item category (transaction OVA2), it will be checked nevertheless if the profitability segment is required from a business point of view (for example, if the account-based profitability analysis is active in transaction KEKE, the incoming sales orders for the controlling area is active in transaction KEKF, etc...). When the profitability segment is required from a business point of view, it is checked in a "hard-coded" incompletion procedure and that´s why the order may be incomplete even if the profitability segment is not maintained in the incompletion procedure. If it is not required from a business point of view, this "hard-coded" incompletion procedure will be set as complete.
    Case 2: if you explicitly have the profitability segment in the incompletion procedure of the item category (OVA2), the profitability
    segment will be checked no matter if it is required from a business point of view or not.
    Please read note 114520 which describes this standard behaviour. This note also describes the system behaviour if the profitability segment has been included explicitly in the incompletion procedure (our case 2) in point 2. In this case, the solution would be to remove the field VBAP-PAOBJNR from the incompletion procedure (providing that the profitability segment is not required from a business point of view).
    regards
    Waman

  • Why we should assign Profitability Segment Number in sales Order

    Dear Gurus,
    Can any one tell me why we should assign profitability Segment Number in Sales Order?
    While i am createing the sales order system is asking to assign profitability Segment Number and WBS Element. Even though there is no specific assignment of these fields for incompletion log.
    Can anyone tell me what exactly is the functionality behind this Profitability Segment number?
    Good answers are rewarded with points
    Thanks and Regards
    SAP SD
    Yoganand

    Hi,
    If CO-PA is active settlement transfer the costs and revenue of the sales order item to profitability segment in CO-PA, if not active it gets transferred to G/L account in FI.
    Regarding functionality of Profitability segment - Need to specify Characteristics in CO-PA for profitability segments and these characteristics are used for Information system and planning. Charcteristics which are not involved in profitablity segment remains in the line item of CO-PA. In essence charcteristics decides on profitablity segments.
    Regarding removal of Profitablity segment no in Sales order .Kindly refer back to the earlier threads.
    Thanks & Regards
    Madhu

  • Missing data: G/L Account----Create Sales Order

    Hi all,
    I am testing scenario for individual purchase order in sales. That is material type:HAWA Item category:TAB Schedule Line:CB.
    The test is OK.
    But when I create sales order for it ,  it pops up
    Missing data: G/L Account
    Message no. VU019
    Diagnosis
    The system checked the document for completion and found some missing data.
    System Response
    You cannot continue processing.
    Procedure
    Enter the missing data.
    I have checked the log of incomplete items, no item for GL Account.
    Could anyone please kindly give some suggestions?
    Regards

    Hi
    check the below SDN links
    [Re: Missing data: G/L Account :.Message no. VU019|Missing data: G/L Account :.Message no. VU019;
    [Re: G/L Account missing|G/L Account missing after Upgradtion to ECC6.;
    [Re: Error in Sales Order savings Missing data: G/L Account Message no. VU019   |Error in Sales Order savings Missing data: G/L Account Message no. VU019;
    Regards,
    Prasanna

  • How the availiblity check is carried out during the sales order creation

    Hi All,
    I have maintained planned delivery time, GRProcesing time and replenishment lead time in days in material master. I am not understand ing how the system is calculating the availability date of the material during sales order creation.
    Please do needful regarding this.
    Regards
    Phani

    Hi,
    Using the Scheduling data from Delivery & Transportation Scheduling, the system does the backward calculation from the Requested Delivery Date. This is used to arrive at Material Availability Date.
    On the Material Availability Date, system checks the Available Qty, as seen in CO09 in column ***. ATP Qty. If the Available Qty is > than Required Qty, Requested Delivery Date is confirmed. Otherwise,
    System moves into the future till it finds the required Available Qty. The new date is then the new Material Availability Date.
    On getting the confirmed Material Availability Date, system does the Forward Scheduling to arrive at a Confirmed Delivery date.
    Regards

  • How to fetch post goods issue date and sales order creation date

    Hi All,
    How to find out the difference between SD Sales Order Item Creation Date and final Post goods issue Date. I would like to know how to fetch those dates and what is the relationship between the tables from which i will get the dates.
    Please let me know the solution .
    Thanks in advance.

    Hi,
    Sales order creation date is when u raise a sales order in favor of the customer using VA01.......using ATP logic system purposes the material availability date....
    after saving ur sales order...when u raise the Delivery using VL01n  w.r.t to OR...than u have to perform picking ....In the picking Tab...specify the amount to be picked than press Post Good Issue....means the goods left the company premises ..
    You can the fetch the values using tables-  Use T code   SE12  or SE16
    Vbak-----order header
    Vbap-----order item
    Vbek-----order schedule line
    Likp-----Delivery header
    Lips----Delivery item

  • Sales Order creation/ change date for the items

    I have a unique scenario and i need to get a Report for this
    A sales order is created for 4 line items.
    Out of these , for 2 line items a delivery is created. I need the sales order creation date and time  for these 2 items in a custom report
    Now the other 2 items go in to some kind of block- Now these are released by going in the sales order VA02 and after releasing the delivery is created. Again for these two items , i need the sales order change date as after a user goes and changes the sales order to remove the block only then delivery is created for these two items
    Also another scenario is the 2 line items go for back order and when we get stock  at tht time system confirms the stock and then the delivery is created for these. So also for this when this change occured i need to get the date for these 2 line items
    Can any one please suggest how to get this data  from the scenarios?
    I dont want to get the date when the delivery is created as i can get tht from the LIKP table. I need the sales order create and change dates for these.

    You may be aware, any changes to a document will be recorded in CDHDR (for header changes) and CDPOS (for item changes).  You can explore these two tables.
    thanks
    G. Lakshmipathi

  • Regarding the date of last change in sales order...

    Hi,
    Can anyone help me in the scenario...
    I have to pick the date of last change in sales order...whether it is done on Configuration items ,additional data B or on the ordered quantity...
    the problem is that it has some customized fields that are included in VBAK....
    So i need help regarding this...shud i have to writ a user exit for this....or i hv to do a change in USEREXIT_SAVE_DOCUMENT .
    Plz help me..
    Edited by: Amit Gupta on May 1, 2008 3:02 PM

    VBAK-AEDAT will be updated, evenIf you have your custom fields in Sales Order.
    Regards,
    Naimesh Patel

  • Sales order creation - data stored in which tables for customer

    Hi experts,
    During sales order creation, data entered during sales process is stored in various related tables. Can anyone list the tables where data is stored for customers?
    Thank you

    Dear Manisha
    Once you saved the sale order,
    - all header datas are stored in VBAK
    - all item level datas are stored in VBAP
    - schedule line confirmation in VBEP
    - all condition types and values are stored in KONV / KONP
    - Partner functions in VBPA
    - Delivery related fields like Shipping Point, Delivery Date, Goods Issue etc., are all in VEPVG
    thanks
    G. Lakshmipathi

  • Closing / Cancell Date of Row Item in Sales Order

    Dear All
    We have to generate one report for one of our customer, which requires to know the 'Cancell / Closing Date' at row level of Sales Order. We could not found it in 'RDR1' table. 'Cancell / Closing Date' only available in header table i.e. in ORDR table. But if any row is closed or cancelled then that is not reflected in header table. So please let us know how to know the 'Cancell / Close Date' in row level in SO.
    Thanks & with regards
    Aloke Bandyopadhyay

    Dear Aloke,
    You may check ADO1 table for historical record to find it.
    Something like:
    SELECT T1.DocNum, T1.DocDate, T0.Linenum+1 'Line#', T0.Itemcode, T0.LineStatus, T0.DocDate 'Line Close Date'
    FROM ADO1 T0
    INNER JOIN ADOC T1 ON T1.DocEntry=T0.DocEntry AND T1.ObjType='17'
    WHERE T1.DocNum LIKE '[%0\]%' AND T0.LineStatus = 'C'
    Thanks,
    Gordon

  • Sales order Creation date

    Hi All,
    I see that the sales order creation date in VBAK is suppose 2009.06.16 and in VA03 if i see th document flow the date is 2009.06.15. and quatation date is also 2009.06.15.
    Which date is the correct Sales order date.If va03 one is correct what is the source table of this date?
    PLease commnet .
    Thanks in advance,
    Swati

    Hi ,
    Let me know in which field you are looking into in VBAK table
    Please let me know if you still need any help.
    Thanks and regards,
    Rajeshwar.

  • 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

  • Spliting up the G/L account in time of Sales Order creation .

    Hi,
    I am an ABAPer. Please let me know using ABAP code how to split the G/L account in time of Sales Order creation for a Payment Card.
    Shyamal.

    Hiya,
    Don't have the system before me, but I think the approx path is:
    IMG --> Controlling --> Profitability Analysis --> Master Data --> Valuation --> Define and Assign Val Strategies (I think it is KE4U).
    Look up the Val Strategy assignments and look for anything with Record Type "A".
    Secondly, look for:
    IMG --> controlling --> Profitability Analysis --> Actual Postings --> Active transfer of Sales Order Data
    Under here, look for any assignments of Condition Types to Value Fields and Quantity Fields to COPA Value Fields (Qty.)
    If these are present, they must have been put there on purpose. You should NOT JUST GO AHEAD AND DELETE them. Check why these are there and then check why these are flowing into your COPA report.
    Normally COPA reports are defined by Record Type. If you used Record Type "F" in your reports, you should always get the proper PL report. However, if you assigned a combination of "F" and "A", you will find that your Order data is flowing into COPA along with the Billing data. So the third check point should be your report definition. Call up the form for the report you are running using transaction KE35 (Change Mode). Check the definition of the Sales quantity, etc. and look for any flows with Record Type "A". Since the form may be used by others, it is not a good idea to delete a form as it is. Copy the form into another and change the new one. Delete the "A" assignments and see if you get the correct result.
    Broadly these are the areas you need to check. But COPA is vast and there could be other areas as well (e.g., KEDR Derivations, or some custom programs (SMOD)) which can trigger flows to COPA Value Fields.
    Cheers.

  • Mass sales order creation using BAPI

    Dear All,
    Can anyone help in  mass sales order creation using Bapi BAPI_SALESORDER_CREATEFROMDAT2.
    For example if i want to create 3 sales order with three item per order . i am populating
    HEADER = 3 Records
    Item   = 9 records
    schedule = 9 records
    partner  = 1 record.
    Then after populating the records I am calling Bapi BAPI_SALESORDER_CREATEFROMDAT2
    to create order. It should have created three order but unfortunately it creates
    only one sales order. I debugged and found that records are correct both in header,
    item, scheudle and partners.
    Could you please guide me what I am missing for creation of mass orders.
    I appreciate your time and many thanks in advance.
    cheers
    chandra

    Hi Chandra,
    Do like this.
    Loop at Header table into wa_header.
    *-- Move BAPI Header data
    Loop at item table into wa_item where condition.
    *--  in this move all Item and Schedule line item  to the BAPI.
      At end of item .
    Use the below function modules.
    BAPI_SALESORDER_CREATEFROMDAT2
    BAPI_TRANSACTION_COMMIT.
    Endloop.
    Endloop.
    Regards,
    Balavardhan.K

  • Change Transportation Zone in Sales Order creation

    Hi Gurus,
    I am looking for an user-exit to overwrite the transportation zone for the ship-to party while creating the Sales order.
    Actually the order is getting created thru IDOC. The segment E1EDKA1 with PARVW 'WE' contains all the data including name, street, city, phone etc. But there is no option(field) to send this transporation zone (LZONE). In the sale order creation program, it is automatically picking it up from VBPA for the customer. I need to overwrite this one with a different value. Is there any User-exit available to accomplish?
    For your information its PO-SO process. A KBZI order will be created. Using the PR generated from this order, we need to create the PO that in turns automatically creating an Intercompany Sales Order ( thru IDoc). In this second Sales Order, I need to overwrite the transportation zone based on the initial order.
    Thanks in advance,
    Vijay.

    >
    Murphy wrote:
    > I modified the value at runtime KUVEW-LZONE. But this values is keep on getting modified by XVBPA-LZONE for the customers...
    How about if we modifiy the value of XVBPA-LZONE itself at runtime in Routine either USEREXIT_SAVE_DOCUMENT or USEREXIT_SAVE_DOCUMENT_PREPARE?
    See if the values of KUVEW-LZONE or XVBPA-LZONE in our hand in above exit?

Maybe you are looking for