Problem about sales order stock stock transfer and batch determination

Hi, experts, I get a problem about sales order stock stock transfer and batch determination.The following is the current situation of my system:
  In OMCG I assigned search procedure ME0001 to both 311 and 311 E and ticked check batch. After that, I found  that if iI need to tranfer unrestricted-use material from storage location 1000 to 2000 with movement type 311, I just need to input * at the field batch, then the system will display all of the available batches. But for the transferring of sales order stock with movement type 311 E, after I input * at the batch field, no batch is displayed and there is also no message from the system.
  Can anybody help me? Is there anything else I need to do? Thanks very much.

I think my question is not clear, actually I tried 562 E , 411 E and 413 already. all the transaction looking for the sales order but unfortunatly the sales order is deleted  from SAP.

Similar Messages

  • Problem about Sales Order Position Status

    Hi everyone,
    I have defined a custom status profile with some custom status for my sales order positions.
    What I really need to know is how to check, from any user-exit while saving the sales order, If the status in my schema has been changed by the user, in order to execute some extra functionality.
    I would be very grateful if someone could tell me which structures should I analyze.
    Thanks in advance and best regards.
    Ben.

    If you set a breakpoint in sales order process, check the value of the following internal table
    (SAPLBSVA)jsto_buf[].
    Note:- This internal table will not get populated if user never navigates to the status screen.
    Another option is interrogating field RV45A-ASTTX. This field will store all the status that the order has.

  • Sale order wise stock and Issuance of external procurement material.

    Transaction : ME21N and MIGO                                           
    Dear SDNites,                                             
    When i make a account assigned PO(with ref to sale order), then material comes and goes directly for consumption.                              
    I want that when the material comes after 105 movt., it should go to un-restricted stock and i can see in mmbe(or any other transaction) how much qty. has come against 
    which sale order, so that i can issue material also sale order wise by movement 231                                                                  
    Pls. help as to how to go about it.                                    
    Rgds.,                                                    Parag                                                     09815999582.

    Hi,
    When you are trying to create PO with reference to SO what is the item category used in SO, Use item category as "TAB" then SO will generate a Purchase Requisition. Convert this Purchase requisition in to Purchase Order, account assignment will be copied as "E Individual Customer stock" Sales order and Cost element will populate from PR.
    When you post the GR for above PO, the stock is managed as Special Stock indicator "E" sales order stock, in MMBE also it displays as SO stock.At the time of GR value is booked to SO and stock will be shown in MMBE.
    This stock is reserve for particular SO against which you have procured, but you can transfer post the same from SO stock to your OWN stock
    Hope this clarifies,
    Thanks & Regards,
    Sridhar

  • STOCK TRANSPORT ORDER UNDER SALES ORDER SPECIAL STOCK

    Hello,
    we have a plant A that produce the same material for some clients and for another plant B (another company).
    Plant A works under sales order special stock. Plant A produce for sales order (other clients) and for cross-company purchase order (STO). The problem is that the STO create Planned orders under Unresticted stock, and sales order under sales order stock.
    It's pòssible that STO create special stock???? I think that plant A must produce always with the same system.
    Thanks

    Nobody know about that.???
    Please, it's a big problem for us.
    thanks for all

  • Sales order wise stock revaluation

    hi
    in case of make to stock material we run standard cost estimate every month and revaluate the stock. ck11n ck40n
    in case is of make to order stock, is valuated at sales order cost estimate. Please explain how this sales order wise stock will be revaluated.

    Hi Imdad
    First of all, why do you want to revaluate at all? When it is a sales order stock, it should be valuated at the sales order cost estimate and it is valuated as such.. Now why would you like to revaluate it?
    Anyways, if you want to do this, then MR21 is the only option... You must specify both Material/Sales order in MR21 in order to revaluate it
    But, I would ask you to re-think on why would you want to do this.. Moreover, revaluating stock every month is not a good accounting practice...I hope you have taken your auditors in confidence
    Regards
    Ajay M

  • Sales Order Valuated Stock Vs. Non Valuated Stock

    Hi Gurus,
    What is difference between Sales Order valuated stock and Non Valuated stock. What are the period end processes in each scenario?
    Please give me ur valuable inputs.
    Thanks in advance,
    Ganesh

    Hi
    The definitions are huge.  Sales order related costing and its components are quite complex and configuration involves defining parameters for Req Class, Req Types, also depends on whether sales order item has indv and collective requirements etc
    To answer your query In short it is as follows
    Valuated sales order stock -  this has both the situations of controlling of sales order with and without.  Which means u may or may not create a cost estimate for the sales order item
    In case of Non Valuated sales order stock - is always with controlling by sales order
    The usage of product cost by sales order depends on business situations and other criteria
    the main period end closing steps would be as follows
    Valuated sales order stocks has all the period end closing steps as u use in make to stock situation, whereas non valuated sales order stock does not support following period closing steps with the exception of RA which can be performed
    1)  No variances can be determined
    2)  Actual costs of production orders are settled to sales orde
    3)  No preliminary costing can be done on the production order
    4)  No details of costs can be posted to non valuated sales order.  Only one cost which is the total actual costs posted to sales order item. 
    5)  There are no planned costs for the sales order item and hence sale price is not determined based on expected standard costs etc. 
    6)  You cannot do profit planning here with changes to sales price based on actual costs of production order
    Please note
    Settlement receiver in non valuated sales order stocks is the sales item and the settlment type is FUL
    Recommendation
    SAP recommends to follow sales order controlling depending on the business scenarios becoz of above limitations of non valuated sales order stock
    Hope the above clarifies - Pls assign points as a way to say thanks

  • SCE for Sales order reserved Stock

    Hi Friends,
    During the SCE in CK40N, it is working fine for all materials except Sales order reserved stock. It is not updating the prices of Sales order stock prices in accounting view and not making valuation on the basis of new prices in MB52 stock report.
    Can you please provide me the solution so that we can get the valuation of Sales order reserved stock(MTO) updated by SCE run.
    Rgds, Krishan Raheja

    Dear Friends,
    Requested for your kind help on the matter.
    Rgds, Krishan Raheja

  • Problem with sales order and Service order

    Dear Guru's
    We have a real problem with sales orders and service orders and how we treat these. For a project that uses a WBS, it's not a problem to manipulate SAP to give us a list of shortages (orders with no or limited supply) for each order, but for some reason our after sales orders and our service orders do not work this way.
    Thanks and Regards,
    Deethya.

    CLOSED

  • I have a problem regarding sales order line item with confimed quanity

    Hi Experts,
    I have a problem regarding sales order line item with confimed quanity with '0'  with delivery block but confirming the sales order quantity once the order is released from credit check.
    The situation arises as per the below scenarios.
    Scenario - 1 -  When the sales order has two line item - one line item with confirmed qunaity in the schedule line and for the 2nd line item there is no available stock for the Material xxxxxx.
    Initially the sales order is created for the line item 2 with confirmed quantity = 0, and having the delivery block = 01 for the Material xxxxxx  and the order is set with credit check.  Once the order is relased from the credit check.  The quanity for the item 2 where the confirmed quantity will be = 0 ( Where it is not changing the confirmed quantity)
    Scenario -2-  Updating the order qunaity for the line item 2 as (9Pcs) it will goes to credit check and save the order.
    Maintain the stock for the line item 2 ( 5 Pcs).
    Once the order is released from the credit check.  Then  for the line item 2 the confirm quanity will be seting to 5 Pcs with Delivery blcok 01.
    This should not happen, When the credit check is released even though if it has stock based on the delivery blockl it should set the confirmed quanity to Zero.
    Can you please help me how to solve this issue.
    Looking forward for your reply.
    Thanks and Regards,

    Hi,
    I agree with your point.  In the sales order When the complete delivery check box is enabled where the confimed qty is set to zero, it is fine but when we save the orderr it goes to credit check.  Once we release the order using VKM3 where in the sales order the confimed quantity is setting to 5,  But it should set to Zero quantity.  Quatity should not be get confirmed it should be Zero Quantity. 
    Further in SPRO - customizing in the deliveries blocking reasons - It has a tick mark in the confirmation blcok.  But we dont want to remove the - Confirmation Block tick mark
    Please any one can help me if you have any solution to solve this problem.
    Thanks and Regards.

  • Problem in Sales order create using BAPI with reference to quotation

    Hi,
    I am creating a sales order from Quotation using BAPI /AFS/BAPI_SALESORD_CREATEFDATA.
    The Sale order is getting created and the document flow is updated. When i check the status of quotation it is "OPEN".
    Ideally when a sale order is created in VA01 with reference to a quotation and if all items are added in the order from quotation, then the status of the quotation must be "Complete".
    When i use the BAPI, the status of the quotation is sill "Open". Has anyone faced this issue?
    Even if anyone has faced this issue with BAPI_SALESORDER_CREATEFROMDAT2, please let me know...
    Regards

    Hi RV,
    I am using BAPI  to create order reference to contracts. I am facing same issue. Its not updating document flow (vbfa-plmin field). After creating orders I am forcing to update plmin field in vbfa. This worked fine. But now status in reference document not updating properly. I saw your thread. It looks like similar issue. I saw your comments "Customization was not maintained properly for the Order types ". Please can you explain little bit more about your solution. It will helps us lot.
    Thanks,
    srini

  • Condition Period Problem in Sales order -  Need help

    Hi Gurus
    I am testing Sales Order back dated
    Condition period Problem in Sales order
    example for you to understand
    Sales Order where PO date is 17.12.2007
    Del Date & Price date is 13.02.2008
    Then it is not calculating IN: A/R BED %IN A/R BED totalN A/R CESS [1621]
    But if i do it after 14 feb 2008 then it is calculating IN: A/R BED %IN A/R BED totalN A/R CESS [1621]
    When I do it with current date it is calculating IN: A/R BED %IN A/R BED totalN A/R CESS [1621] say date is 9-5-2008
    I am not able to trace out problem, kindly help me from where I do I check and why this is happening.
    Rajesh Chalke

    Hi,
    I am not sure if this solves your problem, but I am suspecting that this might be due to the 'valid on date' of the condition records created for the relevant duty condition types.
    Since it was a recent regulation and VK11 usually defaults current date as the valid date, that condition record may have been valid only from the recent date on which it was created.
    Check the date in VK12 (To find the exact selection parameters, check the pricing analysis in the sales order which will display the exact condition record which is being selected as of current date.) Check for the same parameters; change the date to relevant date in the past and recreate the sales order. Hopefully this should solve the issue.
    Cheers,
    KC

  • BAPI - Problem in Sales order creation

    Hi Friends,
    I have problem in Sales order creation using BAPI ,I am getting a messsage - Error in creating document ,I have sent the code along with this mail ,can you help it out.
    Code:
    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 OBLIGATORY.
    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.
    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'.
    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'.
    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'.
      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.
    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.
    Regards,
    Dinesh

    what messages u are gettting in RETURN ? Please check the RETURN tables data.
    [code]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.
    Regards
    Prabhu

  • Problem in Sales Order with specific condition type.

    Hello Experts,
    I'm facing a problem in sales order creation for a specific condition type.
    the actual scenario is as below,
    We have created a new condition type for special discount.This condtion type is applicable only for specific sales channels.Also the discount percentage has to fetched from a custom table.
    To achieve this I've written a user exit "RV64A999"
    In the FM, i've calculated the subtotal and fetched the discount percentage and calculated the discount amount. After implementing this, the SO were been created properly. for all the line items the discount amount was getting calculated properly.
    But then I added a condition at the top of code in exit that the calculation for the new condition type should happen only for selected sales channels.
    But after adding this condition in code, i'm facing problem. Now when I create/ change any SO, the discount amounts are getting calculated incorrectly. I'm getting discount amount even if the line item subtotal amount is zero (0).
    Any help or pointers reagrding this issue will be very helpful and highly appreciated.

    Hi ..
    Check your config. again or debug the routine code with your ABAPer and find the problem area.
    -Maharshi

  • Rounding off value problem in sales order

    Hi All,
    This is related to a rounding off value problem in sales order.
    The problem is described by an example which is as follows -
    Selling Price of Material A = Rs. 176.76
    Excise charged = Rs. 21.80
    Total Price = Rs.176.76 + Rs.21.80 = Rs. 198.56
    On this total Trade Discount (ZDTD) having access sequence,is calculated  at the rate of 4% = Rs. 7.94
    But the condition base value after the discount is showing Rs.198.60 instead of Rs.198.56
    I want the system to reflect the value as Rs.198.56 intact and it should not round up to the nearest value i.e. Rs. 198.60
    Why is this happening? Is it possible to reflect the exact value? If yes what is needed to be done?
    The commercial round off is activated for the DIFF Condition Type.
    Looking forward to some valuable suggestions.
    Thanks & Regards
    Priyanka Mitra

    Hi Ramesh,
    Thanks for your suggestion but the problem has been solved by me.
    Regards
    Priyanka Mitra

  • The problem for sales order ra settlement

    dear friends
    i encounter a problem in sales order settlement
    1 we use rev based result analyse ,and with profit realization
    2 when the so status is rel ,the valuation base is Q,when the status is TECO and finl ,the valuation base is J
    3 when we partially do the billing and run the ra settlement ,the poc = cumulate act rev/plan rev * actual cost in current period(i think this should be the cumulate actual cost ),and it lead to the error calcuation of the COGS,i do not know where the confirguation is error ,is in valuation base ?
    can you help me
    thank you

    dear friends
    i encounter a problem in sales order settlement
    1 we use rev based result analyse ,and with profit realization
    2 when the so status is rel ,the valuation base is Q,when the status is TECO and finl ,the valuation base is J
    3 when we partially do the billing and run the ra settlement ,the poc = cumulate act rev/plan rev * actual cost in current period(i think this should be the cumulate actual cost ),and it lead to the error calcuation of the COGS,i do not know where the confirguation is error ,is in valuation base ?
    can you help me
    thank you

Maybe you are looking for