Import new sales order line in existing sales order

Hi All,
I want to import new sales order line in existing sales order using these open Interface tables or APIs.
I did some test but the import request always give me the error message:
You are trying to insert an existing order or update an order that does not exist. Please enter a correct operation code.
Help..
BR,
Edited by: user7993358 on 2011/5/26 下午 8:48

Hi,
The script available in Oracle Note 746796.1 may be of help with your troubleshooting.
Cheers,
Arun

Similar Messages

  • How to add new price break lines to existing PO quotations?

    Hi,
    I am using a custom interface (to insert quotations data into PO headers/lines interface tables) and PO documents open interface to create PO Quotations in Oracle.
    I need to modify this interface to:
    1. Update existing price break lines for a quotation line.
    2. Add new price break lines to existing quotation line(which may/may not have exsiting price break lines).
    Please let me know:
    1. What modifications need to be done to the existing code.
    2. What values needs to be passed to the action columns in PO_HEADERS_INTERFACE and PO_LINES_INTERFACE for above scenarios?
    Any ideas/help will be appreciated.
    Thanks
    Imran

    Hi Imran,
    I have done a similar exercise for BPA price breakup.. Let me know if you need that as reference. I can share that :).. Please provide your personal mail id..
    Regards,
    S.P DASH

  • Unable to copy line item from Sales Order [ZPLV] to new Sales Order [ZPCV]

    I have here a requirement to create a new Sales Order[ZPCV] with reference to the previously created SO[ZPLV].
    I looked in transaction code VTAA, and the configuration for the aboves condition is:
    target sales doc type - ZCPV   from sales doc type - ZPLV
    dataT: 302, 907 and 001 respectively
    copying requirement: 001
    copy item number is checked
    complete reference is checked
    is there something wrong with the configuration?
    please advice!
    thanks,

    Hi
    For those line items you can assign a REASON FOR REJECTION. Automatically the status of those line items will be closed.
    Thanks,
    Ravi
    PS : sorry....please ignore my post.
    Edited by: sankar ravi on May 20, 2008 3:45 PM

  • Can anyone tell me how to insert the new sales order lines using API.

    Hi,
    I am trying to Insert new sales order lines using oe_order_pub.Process_Order API, but i am unable to insert.
    Help me on this.
    Thanks in Adavance
    Shravan Kumar.

    Hi,
    Have you checked this link?
    http://download-west.oracle.com/docs/cd/B25516_08/current/acrobat/115omapi.zip
    it has extensive information on OM APIs
    Regards
    Prashant Pathak

  • After creating new sales order through BAPI, it is not showing in VA03

    Hi Experts
    I am developing one program to create sales order using FM BAPI_SALESORDER_CREATEFROMDAT2. In output screen it is showing that the new sales order number created with new sales order number. But whenever I want to display the newly created sales order via VA03 it shows an error message SD document 10007547 is not in the database or has been archived but in program output it shows that 10007547 is created. This is in DEV server. Document numbers are generated by the system sequencially, but it is not reflected in database.
    I am also attaching my code below.
    REPORT  z_bapi_salesorder.
    DATA : gt_header LIKE bapisdhd1,
           gt_item TYPE TABLE OF bapisditm,
           gt_itemx TYPE TABLE OF bapisditmx,
           gt_partner TYPE TABLE OF bapiparnr,
           gt_return TYPE TABLE OF bapiret2.
    DATA : gs_item LIKE LINE OF gt_item,
           gs_itemx LIKE LINE OF gt_itemx,
           gs_partner LIKE LINE OF gt_partner,
           gs_return LIKE LINE OF gt_return.
    DATA : v_vbeln TYPE vbeln_va.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(30) ord_type FOR FIELD p_auart.
    PARAMETERS : p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN SKIP 1.
    SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    PARAMETERS       : p_vkorg TYPE vkorg OBLIGATORY,
                       p_vtweg TYPE vtweg OBLIGATORY,
                       p_spart TYPE vbak-spart OBLIGATORY,
                       p_sold TYPE kunnr OBLIGATORY,
                       p_ship TYPE kunnr OBLIGATORY,
                       p_matnr TYPE matnr OBLIGATORY,
                       p_menge TYPE kwmeng OBLIGATORY,
                       p_plant TYPE werks_d OBLIGATORY.
    SELECTION-SCREEN : END OF BLOCK b1.
    INITIALIZATION.
      ord_type = 'Order Type'.
    START-OF-SELECTION.
    *Header information data.
      gt_header-doc_type = p_auart.
      gt_header-sales_org = p_vkorg.
      gt_header-distr_chan = p_vtweg.
      gt_header-division = p_spart.
    *Partner information data.
      gs_partner-partn_role = 'AG'.
      gs_partner-partn_numb = p_sold.
      APPEND gs_partner TO gt_partner.
      CLEAR gs_partner.
      gs_partner-partn_role = 'WE'.
      gs_partner-partn_numb = p_ship.
      APPEND gs_partner TO gt_partner.
      CLEAR gs_partner.
    *Item data
      gs_item-itm_number = '000010'.
      gs_itemx-itm_number = 'X'.
      gs_item-material = p_matnr.
      gs_itemx-material = 'X'.
      gs_item-plant = p_plant.
      gs_itemx-plant = 'X'.
      gs_item-target_qty = p_menge.
      gs_itemx-target_qty = 0.
      APPEND gs_item TO gt_item.
      APPEND gs_itemx TO gt_itemx.
      CLEAR : gs_item, gs_itemx.
      CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
        EXPORTING
      SALESDOCUMENTIN               =
          order_header_in               = gt_header
      ORDER_HEADER_INX              =
      SENDER                        =
      BINARY_RELATIONSHIPTYPE       =
      INT_NUMBER_ASSIGNMENT         =
      BEHAVE_WHEN_ERROR             =
      LOGIC_SWITCH                  =
      TESTRUN                       =
      CONVERT                       = ' '
       IMPORTING
         salesdocument                = v_vbeln
        TABLES
         return                       = gt_return
         order_items_in               = gt_item
         order_items_inx              = gt_itemx
         order_partners               = gt_partner
      ORDER_SCHEDULES_IN            =
      ORDER_SCHEDULES_INX           =
      ORDER_CONDITIONS_IN           =
      ORDER_CONDITIONS_INX          =
      ORDER_CFGS_REF                =
      ORDER_CFGS_INST               =
      ORDER_CFGS_PART_OF            =
      ORDER_CFGS_VALUE              =
      ORDER_CFGS_BLOB               =
      ORDER_CFGS_VK                 =
      ORDER_CFGS_REFINST            =
      ORDER_CCARD                   =
      ORDER_TEXT                    =
      ORDER_KEYS                    =
      EXTENSIONIN                   =
      PARTNERADDRESSES              =
      IF v_vbeln <> space.
        COMMIT WORK.
        WRITE :/ 'Document', v_vbeln ,'created'.
        CLEAR : v_vbeln, gt_header.
        REFRESH : gt_partner, gt_item, gt_itemx.
      ELSE.
        WRITE :/ 'Error in creating document'.
      ENDIF.
    Please give the possible solutions for this. What is reason for that update termination.

    CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
        EXPORTING
          ORDER_HEADER_IN           = ORDER_HEADER_IN
      WITHOUT_COMMIT            = ' '
      CONVERT_PARVW_AUART       = ' '
       IMPORTING
         SALESDOCUMENT             = SALESDOCUMENT
      SOLD_TO_PARTY             =
      SHIP_TO_PARTY             =
      BILLING_PARTY             =
         RETURN                    = RETURN
        TABLES
          ORDER_ITEMS_IN            = ORDER_ITEMS_IN
          ORDER_PARTNERS            = ORDER_PARTNERS
      ORDER_ITEMS_OUT           =
      ORDER_CFGS_REF            =
      ORDER_CFGS_INST           =
      ORDER_CFGS_PART_OF        =
      ORDER_CFGS_VALUE          =
      ORDER_CCARD               =
      ORDER_CFGS_BLOB           =
         ORDER_SCHEDULE_EX         = ORDER_SCHEDULE_EX
    use bapi_transaction_commit.
    Regards,
    Venkat

  • Creation of new Sales order

    Hi,
           While creating a new Sales Order(tcode VA01) depending on the material, Item category will be generated and depending on the Item category purchase requisition screen(ME51n) will be automatically opened and PR will be created.
    Now to automate this process, BAPI_SALESORDER_CREATEFROMDAT1 will be called to create the sales order. But the requirement is that we need to pass Requisitioner and Vendor to the BAPI for creation of PR.
    But in this BAPI there is no option/field to pass Requisitioner and Vendor. So is there any other BAPI/Function Module where a new Sales order is created and also we can pass Requisitioner and Vendor required for creation of new PR.

    REPORT  ZSALESORDER.
    Parameters
    Sales document type
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
    PARAMETERS: p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Sales organization
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
    PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Distribution channel
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
    PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Division.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
    PARAMETERS: p_spart TYPE spart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Sold-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
    PARAMETERS: p_sold  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Ship-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
    PARAMETERS: p_ship  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Material
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
    PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Quantity.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
    PARAMETERS: p_menge TYPE kwmeng  OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Plant
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
    PARAMETERS: p_plant TYPE werks_d .
    SELECTION-SCREEN END OF LINE.
    Complete Deliver
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
    PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
    SELECTION-SCREEN END OF LINE.
    Data declarations.
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead1.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapisditem  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                             WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                             WITH HEADER LINE.
    DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                             WITH HEADER LINE.
    Initialization.
    INITIALIZATION.
    v_text   = 'Order type'.
    v_text1  = 'Sales Org'.
    v_text2  = 'Distribution channel'.
    v_text3  = 'Division'.
    v_text4  = 'Sold-to'.
    v_text5  = 'Ship-to'.
    v_text6  = 'Material'.
    v_text7  = 'Quantity'.
    v_text9  = 'Plant'.
    v_text10 = 'Complete delivery'.
    Start-of-selection.
    START-OF-SELECTION.
    Header data
    Sales document type
      header-doc_type = p_auart.
      headerx-doc_type = 'X'.
    Sales organization
      header-sales_org = p_vkorg.
      headerx-sales_org = 'X'.
    Distribution channel
      header-distr_chan  = p_vtweg.
      headerx-distr_chan = 'X'.
    Division
      header-division = p_spart.
      headerx-division = 'X'.
      headerx-updateflag = 'I'.
    *Complete delivery
        header-COMPL_DLV = p_autlf.
        header-COMPL_DLV = 'X'.
    Partner data
    Sold to
      partner-partn_role = 'AG'.
      partner-partn_numb = p_sold.
      APPEND partner.
    Ship to
      partner-partn_role = 'WE'.
      partner-partn_numb = p_ship.
      APPEND partner.
    ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000010'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
    item category
      itemx-ITEM_CATEG = 'X'.
      APPEND item.
      APPEND itemx.
      ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000020'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
      APPEND item.
      APPEND itemx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000010'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000010'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000020'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000020'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
    Call the BAPI to create the sales order.
      CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
           EXPORTING
                sales_header_in     = header
                sales_header_inx    = headerx
           IMPORTING
                salesdocument_ex    = v_vbeln
           TABLES
                return              = return
                sales_items_in      = item
                sales_items_inx     = itemx
                sales_schedules_in  = lt_schedules_in
                sales_schedules_inx = lt_schedules_inx
                sales_partners      = partner.
    Check the return table.
      LOOP AT return WHERE type = 'E' OR type = 'A'.
        EXIT.
      ENDLOOP.
      IF sy-subrc = 0.
        WRITE: / 'Error in creating document'.
      ELSE.
    Commit the work.
        COMMIT WORK AND WAIT.
        WRITE: / 'Document ', v_vbeln, ' created'.
      ENDIF.

  • Can we create new sales order for RMA?

    Hi
    We have processed one sales order eg.ABC in INR instead of USD and we have closed it. Later we found that the order entry was wrong (that is the currency was wrongly entered in INR instead of USD) and created a new sales order eg. XYZ for RMA of that material and entered the sales order number ABC and invoice number as reference under returns tab. Now if I go to take the receipt of the new sales order created for RMA that for XYZ , I was not able to see that order number XYZ from the list of values in Receiving Transactions under Customer tab.
    Can anyone please give me an idea on how to open an closed order and to cancel the existing order so that i can take back the material in the same closed order i.e, ABC after reopening it and cancel the new sales order i.e, XYZ created for RMA.
    Thanks in advance
    Prem.

    You have mentioned that the sales order is closed. Does it mean that the lines are interfaced to AR ? Is the invoice generated? Is the shipment done?

  • How to create a new sales order to internal requisition?

    Hi, All
    Need help!!!
    How to create a new sales order to internal requisition?
    The internal requisition has generated order sales but this has already been canceled, so I need to create a new sales order to the same internal requisition.
    How to release the internal requisition to re-create new sales order and after import in OM?
    please help me
    Thanks and regards
    Manuel,

    You cannot.
    Once a ISO is generated for an IR, the transferred_to_oe flag is set on that req.
    If the ISO was canceled, you should cancel the IR and create a new one.
    Hope this helps,
    Sandeep Gandhi

  • IMG Settings for creating a new sales order type

    Hello All,
    I seek you valuable inputs on the steps to follow in IMG(SPRO) setting to create a new sales order type in the system.
    I want to create a new sales order type for which i have done the following setting in IMG,
    1) Sales and Distribution->Sales->Sales Document Header->Define sales document type.
    2)  Sales and Distribution->Sales->sales Document Header->Assign Sales Area To Sales Document Types.
    3) Sales and Distribution->Sales->Sales Document Item->Define Items Categories
    4) Sales and Distribution->Sales->Sales Document Item->Assign Item categories
    5) Sales and Distribution->SalesàSchedule Lines->Assign Schedule lines Categories.
    Also created a new number range for the same.
    After this when i am trying to create a sales order with VA01 i get an error "Enter a Sales Area".
    what am i missing ?Please suggest.
    Thanks in advance,
    Swati

    Hello,
    In the Initial screen of VA01 you have to enter the sale area which is nothing but the combination of
    Sales organization
    Distribtion channgel
    Division
    And in the transaction code  OVAZ you should assign the sales document type for this sales area .
    Please revert if you need any frther clarification
    regards,
    santosh

  • How to avoid duplicated customer ref. no when create new sales order?

    Hi,
    In my company, we need input customer ref. no when create a new sales order, but I found there was no any validation to avoid input a existed number.
    Can somebody show me how to add some check function on this filed?
    thanks.

    Hi,
    This can be handled in standard system.
    Go to Administration> System Initialization> Document Settings>Per Document (Tab)> Select Sales Order-->Tick Block release (When duplicated  customer reference no. occurs).
    Thanks,
    Joseph

  • Safety Stock Not Being Released To Cover New Sales Orders Or Forecast

    Hi,
    Does anyone know of a way to get safety stock at the lower levels of the BOM to get released for upper level sales order or forecast demand without having to adjust the effectively out to a future date?
    Example:
    A = Finish goods item with two weeks lead time
    B= component of A and it has two weeks lead time
    C= component of B and has 10 weeks lead time.
    Have safety stock hard coded with an effective date of today for 100,000 units.
    I have 100,000 in inventory and I have planned orders to cover all my demands and future safety stock requirements for the next ten weeks.
    I receive a new sales order for 50,000 units with a customer request date five weeks out.
    I am getting ATP dates to assign to the new sales order 14 weeks out versus allowing me to use 50,000 units from the safety stock to schedule in week five?
    Even If I schedule the sales order for five weeks, because I have gone down two levels to confirm that I have safety stock, and It could be used, planned orders would not get generated at the next two levels, because the demand date on the safety stock is earlier than the demand date for the new order?
    Is there any resolution that anyone has found that addresses this issue?
    We have set a demand priority rule on the ASCP plan options tab to "Sales Order Priority" where we have set criteria for number one to "Sales Orders & MDS Entries Priority" and number two to "Schedule Date".
    We have found that adjusting the supply and demand dates out to cover the full 14 week period does reduce the safety stock at the lower levels, but it also creates additional starts and inventory to be put into the line, which makes this approach not feasible.
    Does anyone have any solutions to this problem? We do not build safety stock for the sake of building safety stock. We want it to be used for any sales order or forecast demand that comes within the planning horizon.
    Appreciate any inputs.
    Regards,
    Dave

    Hi Dave,
    Try this note suggestion, possibly help you in resolving your issue.
    How to Avoid Getting Safety Stock Replenishment Too Early in an ASCP Plan [ID 301629.1]
    In order to line up the safety stock supply with the changes in safety stock, a combination of the profiles must be used:
    MSC: Use FIFO Pegging as yes
    and the plan option
    Peg Supplies by Demand Priority is checked.
    The profile MSC: Use FIFO Pegging as yes will perform the following:
    For all demands and supplies, it proceeds item by item and
    pegs supplies to demands on a daily basis. Daily supplies
    and demands are not sorted. When supplies or demands
    on a given date are used up, it picks from supplies or
    demands on the next date. The unpegged supplies are
    pegged to excess.
    The peg supplies by demand priority combined with the profile above will prevent the system to plan ahead for safety stock.
    Also no safety stock smoothing is setup.
    To implement the solution, please execute the following steps:
    1. Please set the profile:
    MSC: Use FIFO Pegging as yes and
    2. Under the plan settings in the main tab the set the following options:
    Enable Pegging ON
    Peg Supplies by Demand Priority ON
    Warm Regards
    Sivaraman.G

  • Creating new sales-order item with text using BAPI_SALESORDER_CHANGE

    Hi all.
    I want to create new sales-order item in an existing sales-order by using BAPI_SALESORDER_CHANGE. This works fine.
    I also want to enter item-texts for the new item in the same call, but this doesn't work.
    When I call the BAPI I do not assign an item-number for the new item, thus I have no item-number to assign to ITM_NUMBER in table ORDER_TEXT.  IF ITM_NUMBER is empty, it's treated as a header text....
    Any clues?
    Regards
    /Elisabet

    increment the last itemnumber and pass it to that.
    if they are following a sequence 10,20,30.
    find the next sequence and send it to the ITEMNUMBER field.
    or else you add the text after the Function call.

  • Best Way to Import Open Sales Orders

    Dear Experts,
    Which is the best possible way to export and import open sales orders from one DB to an another both being (SAP B1 2007)
    Regards,
    Aditya

    Hi,
    The only othe way to acheive this would be with SDK really. I've heard of people doing things like this in the past where the volume of data was so much that it was worthwhile to write some code, but to be honest if you're relatively proficient in DTW then you can have done the job by the time you've conned a programmer into writing it for you!
    Good luck!
    Julian

  • Sales order cancelled and new sales order with added components

    Hi all,
    There is a MTO scenario.Lets say a product X was to be made .Now when the production was complete,the sales order got cancelled and a new sales order was generated for same product with 2 new components to be added,lets say A and B.
    So now i have to use the finished good x and new components A and B for the new sales order.How will the costing of new product be done and how do i maintain the BOM?

    Dear,
    You have to create the new material code for your new product as it is having two new components. For that new product say Y you need to add the X, A and B.
    As you have already manufactured the X so system will not create any procurement proposal for it and you can consume the X while manufacturing the Y and it cost also get capture to the Y. This is standard Practice.
    Hope clear to you.
    Regards,
    R.Brahmankar

  • How to transfer cost from old sales order (cancelled) to new sales order

    Hi Gurus
    I want to know, how to move cost from one sales order to another sales order.
    SD created sales order before 1 month and there was production order behind this. Production was completed and all the cost was moved to sales order and also SD has raised invoice on customer. This transaction was completed.
    The above order was rejected by customer due to some changes in the order. SD raised another sales order and production order was created to to additional work. Production transfered above stock (produce before on old production order) to new production order.
    My problem is stock is now transfered to new production order but cost is still sitting on old sales order. How do I transfer cost from old sales order to new sales order. SD cancelled old invoice and raised new one with full value (old + new work) on new sales order. Now cost is on old sales order and revenue is on new sales order.
    Please help.
    Thanks

    Hi
    I have reverse the sales order settlement, PP order settlement to sales order and I have also done KB11N for transfering the cost to the new production order.
    The only problem is I was unable to transfer labour hour confirmation as cost element used for this are not for transfering cost. If I will reverse the confirmation in PP order system will reverse material movement also which I don't want any more. Can you please tell me how to I reverse the Labour hours with out affecting goods movement?
    Many thanks

Maybe you are looking for