Movement type from QM to Unrestricted

Hi ALL,
How to move the material from QM to Unrestricted...I am aware of 321 mvt type..
Please suggest me diffferent mvt type..
Thanks,
Regards,
Ameya k.

Hello Ameya,
The only one mvt type 321 is used to move material from QI to UR - Unrestricted. This can be done through MB1B transaction code (if QM module is not active) or using QA11 (usage Decision) as explained by Srinivas.
If you have any other business scenario, please let us know so we can address accordingly.
Regards
Arif Mansuri

Similar Messages

  • Movement   types  from  sd  point of view

    does somebody have a list of movement  types   and   some  document   explaining  what  movement types  are  meant for   what?  from  sd  point of  view
    thank
    s.r.c
    [email protected]

    Movement types
    Any movement of stock in SAP has a movement type , u can see the movement types in  T:code: OMJJ
    As such a movement type is not directly related to any order type. But the combination of
    order type + item category group ==> item category
    now
    item category + MRP type ( from mat master) --- > Schedule line category.
    The movement type is linked with schedule line category. As a thumb rule all Movement types from 601 to 699 belong purely to SD.
    If u want to c the movement type related to that particular order go with the following path.
    Hit the icon 'schedule line for the item' , in the following screen hit 'procurement push button' there u will find the movement type.
    For each material movement, the system uses the movement type to determine the rules for updating the stock quantities and the stock values in the relevant G/L accounts.
    http://help.sap.com/saphelp_40b/helpdata/ru/fc/6cec6eb435d1118b3f0060b03ca329/content.htm
    601 Goods issue for delivery (Shipping)
    In Shipping, this movement type is created automatically with the Goods issue for delivery function.
    The quantity is taken from unrestricted-use stock.
    Possible special stock indicators:
    E, K, Q
    603 Goods issue for stock transport order (Shipping) with additional
    item
    If you issue goods for a stock transport order in Shipping using movement type 641, you can use this movement type to assign an extra item to the order.
    The ordered material is transferred to the stock in transit of the receiving plant. The material for the additional item is transferred from unrestricted-use stock in the issuing plant to stock in transfer in the receiving plant.
    You can also use this movement type without referencing a purchase order.
    Possible special stock indicators:
    None
    See also: 303, 641
    605 Goods receipt for a stock transport order (Shipping) with
    additional item
    You can use this movement type to transfer into unrestricted-use stock the material you posted into stock in transfer in the receiving plant using movement type 603. You post the goods movement with reference to the purchase order (if available) or the delivery.
    Possible special stock indicators:
    None
    See also: 305 and 641
    621 Transfer posting unrestricted-use - returnable packaging (Shipping)
    The quantity is transferred from unrestricted-use stock to the returnable packaging stock at customer.
    Possible special stock indicators:
    none
    623 Goods issue from returnable packaging stock at customer (Shipping)
    This quantity is withdrawn from unrestricted-use returnable packaging stock at the customer.
    Possible special stock indicators:
    V
    631 Transfer posting unrestricted use - customer consignment stock (Shipping)
    The quantity is transferred from unrestricted-use stock to consignment stock at customer.
    Possible special stock indicators:
    E, Q
    633 Goods issue from customer consignment (Shipping)
    The quantity is withdrawn from unrestricted-use consignment stock at the customer.
    Possible special stock indicators:
    W
    641 Goods issue for a stock transport order (Shipping)
    The quantity is transferred using a delivery in Shipping from unrestricted-use stock of the issuing plant to stock in transit of the receiving plant.
    The goods receipt for the stock transport order takes place using movement type 101 and can, if required, refer to the purchase order or to the delivery. If a purchase order item is flagged as a returns item in the stock transport order, you can post the goods receipt of the returns in the issuing plant with movment type 671.
    Possible special stock indicators:
    E, Q
    For the special stock indicators E and Q and for purchase orders assigned to an account, you must ensure that the quantity is not posted to the stock in transit of the receiving plant.
    See also: 351, 643, 671
    643 Goods issue for a cross-company stock transport order (Shipping)
    It is used only for cross-company stock transport orders with SD billing and invoice. The quantity is withdrawn from the unrestricted-use stock of the issuing plant. No stock in transit is created here. In the second step, the goods receipt must be entered in the receiving plant. If a purchase order item is flagged as a returns item in the stock transport order, you can post the goods receipt of the returns in the issuing plant with movment type 673.
    Possible special stock indicators:
    E
    See also: 351, 641, 673
    645 Goods issue for a cross-company
    stock transport order in one step (Shipping)
    Unlike movement type 643 when a goods issue is posted using movement type 645, a goods receipt line is generated automatically 101). If a purchase order item is flagged as a returns item in the stock transport order, you can post the goods receipt of the returns in the issuing plant with movment type 675.
    Possible special stock indicators:
    E
    See also: 675
    647 Goods issue for a stock transport order in one step
    (Shipping)
    Unlike movement type 641 when a goods issue is posted using movement type 647, a goods receipt line (movement type 101) is generated automatically in the receiving plant. If a purchase order item is flagged as a returns item in the stock transport order, you can post the goods receipt of the returns in the issuing plant with movement type 677.
    Possible special stock indicators:
    E, Q
    See also: 677
    651 Returns from customer (Shipping)
    Using movement type 651, you post returns from a customer with a return delivery in Shipping to blocked stock returns.
    Possible special stock indicators:
    None
    See also: 451, 453, 653
    653 Returns from customer (Shipping) to unrestricted-use stock
    With this movement type you post returns from the customer with returns delivery via Shipping directly to the valuated stock.
    Possible special stock indicators:
    E
    See also: 451, 453, 651
    655 Returns from customer (Shipping) to stock in quality inspection
    With this movement type you post returns from the customer with returns delivery via Shipping directly to the valuated stock.
    Possible special stock indicators:
    E
    See also: 451, 453, 651
    657 Returns from customer (Shipping) to blocked stock
    With this movement type you post returns from the customer with returns delivery via Shipping directly to the valuated stock.
    Possible special stock indicators:
    E
    See also: 451, 453, 651
    661 Returns to vendor via Shipping
    As with movement type 502, a return delivery to the vendor is entered without reference to the purchase order, but the goods issue is posted via a delivery in Shipping.
    Possible special stock indicators:
    E
    671 Returns for stock transport order via Shipping
    If a purchase order item is marked as a returns item in a stock transport order using movement type 641 when a goods receipt for a stock transport order ( 101) is posted, the return is posted to stock in transit using movement type 161. When the return arrives, the issuing plant posts the goods receipt for the return using movement type 671. Movement type 671 (like movement types 352 and 642) reduces the receiving plant's stock in transit and increases the issuing plant's unrestricted-use stock.
    Possible special stock indicators:
    E, Q
    673 Returns for cross-company stock transport order
    (Shipping)
    673.
    Possible special stock indicators:
    675 Returns for cross-company stock transport order
    (Shipping) in one step
    677 Returns for stock transport order in one step (Shipping)

  • How to post reason code/movement type from MM to FI document?

    Have had a request from our Finance guy here that when a movement is posted in MM (eg a scrapping), the reason code and movement type are to go onto the FI document when the movement is posted to the GL accounts. These values are to be viewed from FBL3N.
    He thinks it might need to be done with substitutions but I have had no experience in this area and he has no idea how to go about it. I have extended the COBL structure using OKX3 which has put the field into BSEG but have no idea how to go about doing the substitution or which exit to use. Inaddition in SAP standard, MSEG passes the movememnt type tyo COBL field BWART but then this seems to get voided.
    Can anyone help me?
    Regards
    Larissa Maryniuk

    Hi Larissa,
    Please go through with this below link. You can easily understand about Substitutions.
    http://techbays.files.wordpress.com/2008/08/sap-tip-how-to-use-substitutions-lakshman-tandra1.pdf
    Best Regards,
    Mohan.

  • Movement type from restricted to block

    Dear ALL,
    I have a scenario of Deadline Monitoring, in which one the material date get expired it went to restricted stock and from there directly to block stock..So which movement type should i used for such scenario.We used presently QA05 T-Code.
    Regards,
    Asif

    Hi Asif,
    I assume that you have decided to go with the Z program suggested earlier.
    Now You just want to make sure that records passed using this program are of QA07.
    If TCODE2_MKPF is not available in MSEG, then i would go with reference to MKPF table.
    First of all i shall get the list of restricted batches from MCHB (Or May be MCH1),
    Then Pass Material, Plant, Batch and Movement type as 341 to MSEG,
    And then i would pass outcome of this to table MKPF and check field TCODE2.
    Dont forget that I am currently not able to check in my system whether system puts QA07 in TCODE2 field of MKPF at the time of 341 mvt (When it is restricted). Please confirm before proceeding.
    moreover, i did not get about the effect your team is concerned about.
    It will be good if you execute by yourself, means check these tables with right sequence and at the end you will be able to judge whether this logic gives you correct list of batches needs to be transferred to blocked.
    Amol.

  • Movement type '344' blocked to unrestricted - reversal error.

    Hi,
    I am trying to post movement type '344' blocked to unrestriced reversal in IM. I am using WM for this storage location. while posting the '344' i am getting an error 'Data for creating a delivery is incomplete (vendor)'. Will appreciate any help to resolve this.
    thanks.

    Hi,
    I am trying to post movement type '344' blocked to unrestriced reversal in IM. I am using WM for this storage location. while posting the '344' i am getting an error 'Data for creating a delivery is incomplete (vendor)'. Will appreciate any help to resolve this.
    thanks.

  • Trace the reference Standard movement type from customized movement type

    Hi,
    In my system there are few customized movement type.
    Can I know which Standard movement type was used as reference to create the customized movement type.

    try table t156 table .. put your mvt type and see the BUSTR field for the reference mvt

  • Create custom movement type from 101 with only qunatity update

    Dear Experts ,
    I need to  create a movement type behaving just like 101 but should have no accounting entries generated .
    Is it possible . Can i customise the account grouping to meet the above requirements ?
    Regards
    Anis

    HI,
    You can try movement type 511(free of charge). but Price control in material master should be MAP.
    Regards,
    Pardeep Malik

  • Movement type from unrestricted to reserved

    Hi Friends,
    Is there a T-code for stock transferring from unrestricted to reserved?
    Here is the scenario, we have 100 pieces of material ABC under unrestricted , we'd like to reserve 50 pieces for a particular customer who will place the order two months later.
    Thanks for your help
    Linda

    it is not possible to create a reservation in MB21 transaction for movement 601.
    So you need  to find a workaround to "reserve" the material.
    one idea could be to create the sales order in advance with a certain delivery data (e.g. Dec.31) and use and change this one when the real order comes in.
    Another option could be to change the status to blocked, or move the stock into an extra storage bin.
    any workaround has follow on actions, as you would need to transfer the status again to unrestrcted if you want make use of this material.
    In any case, such reservations may lead to dead-stock if the expected sales order does not arrive.

  • Movement type from unrestricted use to particular storage location

    Hi ,
    I have situation wherein the stock was goods receipted with referendce to  a PO into unrestricted stock (without mentioning storage location).
    I now want to transfer this stock to a particular storage location.
    Please let me know how to do this,
    Regards,
    Vinayak

    Hi,
    How can you receive a material without mentioning the storage location in MIGO (101), it is not possible as per standard system.
    Please check the PO, It must be created with account assignment that means it was consumed at the time of GR, that is the reason you do not need to enter storage location at MIGO
    So if you need that material in storage location cancel that GR, change that PO receive again in desired Store

  • Movement Type from Customer owned Stock back to Plant Stock

    Hi Guru's,
    Is there a Mov. Type that allows you to transfer from Customer owned Stock back to Plant Stock, without creating any FI Documents? Please help thanks in advance Carlo

    What is customer owned stock?
    from my point of view it is any stock that you and others sold to this customer. not in your system at all.
    If you want to get it back to your promises, then you have to create a customer return.
    The customer return goes into return stock, this does not create any financial postings.
    But if you transfer the retun stock into own stock, then you create an accounting doc with value (quantity * price / price unit)
    You cannot create stock for a valuated material without any financial document

  • Movement type 671 (copy) to blocked stock instead of unrestricted use

    Hello,
    I want to post the stock from a return delivery (created with reference to return line of a stock transport order) to blocked stock instead of unrestricted use stock.
    Standard SAP uses delivery item category NLRN (Return StockTransItm) and movement type 671 (TR to stock in transit).
    I want to do the same thing that movement type 671 does but post the GR to blocked stock.
    Any ideas,
    Best regards,
    Dominik

    Dear ,
    Normally the process for intercompany 'return' stock transfer is as               
    follows:                                                                               
    1) Create an intercompany stock transfer order with flag 'Return'                 
       (transaction ME21) or an item with the return flag (field RETPO)                                                                               
    2) Create a delivery with VL10B (or VL04)                                         
    Cross-company, delivery type NCR, item category NCRN                              
    Intra company, delivery type  NLR, item category NLRN                                                                               
    The delivery type will be assigned via Customizing IMG -> Materials               
    Management -> Purchasing -> Purchase Order -> Returns Order -> Store              
    Return                                                                               
    3) Create with the transaction MIGO a goods receipt from the receiving               
       plant (the plant that created the NB purchase order for return -                  
       therfore the quantity is negative) with movement type 101                         
       (this step is only necessary with the two-step procedure).                        
       The goods receipt will NOT be created with reference to the delivery,             
       that means, that the returns delivery will not be updated. In                     
       the system posts a goods issue with reference to the                              
       returns purchase order that is the system converts                                
       the movement type due to the returns indicator.                                   
       Cross company   161                                                               
       Intra company   161                                                               
       If the one-step procedure is used, step 3 needs not to be performed,              
       automatically posts the negative goods receipt when performing step 4             
       The quantity is then transferred to the transit stock.                                                                               
    4) Posting of goods issue via the delivery; Button 'Goods issue' -      
       starting with 4.6 the button is changed to 'Goods receipt'.                                                                               
    In background a goods receipt is performed                                                                               
    Cross company                                                        
       Two step procedure 673                                               
       One step procedure 675 (step 3 with mov.type 161 is automatically    
       posted)                                                                               
    Intracompany                                                         
       Two step procedure 671                                               
       One step procedure 677 (step 3 with mov.type 161 is automatically    
       automatically posted)                                                                               
    5) Create a credit for it                                                  
    6) and check this credit.                                                                               
    In the standard it is not foreseen that the returns of cross-company       
    stock transport orders arrive a blocked returns stock. As you found,       
    in Note 430074, the relevant movement types for this process are 671,673   
    675 and 677. As indicated in the documentation you have, these movement    
    types transfer returns into unrestricted-use stock. Therefore, if you      
    wish to place these particular returns in blocked stock, you will need     
    to perform another movement from unrestricted-use stock once the return    
    has been received as such.                                                                               
    I am sorry I can not provide a more satisfactory solution.

  • BDC for MIGO for GR OutBound Delivery( A01 & R05 ) from Movement Type 107 to 109

    Hi,
    I am stuck with a very typical situation need all your expertise and advices for a solution.
    We are basically trying to create change the movement type from 107 to 109 through MIGO.
    I have made a BDC recording for MIGO ( because we would like to track each delivery specifically under shipment , I know that there is a BAPI which is there to do this but it works fine if we do the shipment with Purchase Order as input which dont want in that manner )
    Process:
    1. Creating Production Order
    2. Creating Purchase Order
    3. Creating STO
    4. Deliveries
    5. PGI for Deliveries
    6. Shipment for group of outbound Deliveries
    I have created a z program where i am passing shipment number in the selection screen.
    Then it would take all the deliveries for that shipment and pass each delivery to MIGO and process it and change the status from 107 to 109.
    Interesting part here is, the code works absolutely perfect only from my ID. But when I test from other ID it is not executing, so to check where is the problem I have added mess_tab to the CALL TRANSACTION to capture what message is been populated for my ID comparing with others
    Message Captured on Others ID's:
    MSGID: 00
    MSGNR: 344
    MSGV1: SAPLMIGO
    MSGV2: 1300
    Message Captured on MY ID:
    MSGID: MIGO
    MSGNR: 012
    MSGV1: 5000005802
    MSGV2: (empty)
    This is the problem this program is executing only on MY ID, rest all ID's it is not processing.
    We have cross verified with security and basis regarding any authorization issues but nothing came up.
    Please help me what could be the issue ( WHY it is processing successfully for my and WHY NOT for other ID's)
    Below is the main code :
    CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'                     " Converting Date format to DD/MM/YYYY
         EXPORTING
           DATE_INTERNAL            = sy-datum
         IMPORTING
           DATE_EXTERNAL            = lv_date_external
         EXCEPTIONS
           DATE_INTERNAL_IS_INVALID = 1
           OTHERS                   = 2.
           IF SY-SUBRC <> 0.                                     "#EC NEEDED
    * Implement suitable error handling here
           ENDIF.
    *   Validating input shipment number with database table VTTP
           SELECT VTTP~TKNUM
                  VTTP~TPNUM
                  VTTP~VBELN
             FROM VTTP INNER JOIN VTTK
             ON VTTP~TKNUM = VTTK~TKNUM
             INTO TABLE IT_VTTP
             WHERE VTTK~TKNUM = P_TKNUM
               AND VTTK~STDIS = 'X'.
           IF sy-subrc = 0.
    *   Validating all deliveries having same Delivery type or not
             SELECT * FROM likp INTO TABLE it_likp FOR ALL ENTRIES IN it_vttp WHERE vbeln = it_vttp-vbeln
                                                                                AND vbtyp = 'J'.
             IF sy-subrc = 0.
               CLEAR lv_lines.
               LOOP AT it_likp INTO wa_likp.
                 REFRESH:it_vbfa,BDCDATA.
    *   Validating if Delivery Type = 109 (GR already done), or Delivery Type = 107 (must process for GR )
                 SELECT * FROM vbfa INTO TABLE it_vbfa WHERE vbelv = wa_likp-vbeln
    *                                                AND vbtyp_v = 'J'
                                                         AND bwart = '109'.
                 IF sy-subrc = 0.
                   lv_flag1 = 'X'.
                 ELSE.
                   SELECT * FROM vbfa INTO TABLE it_vbfa WHERE vbelv = wa_likp-vbeln
    *                                                  AND vbtyp_v = 'J'
                                                           AND bwart = '107'.
                   IF sy-subrc NE 0.
                     MESSAGE 'No Deliveries with Movement Type "107" ' TYPE 'I'.
                   ELSE.
                     lv_flag2 = 'X'.
                     lv_lines = lv_lines + 1.
    **  BDC for MIGO
                     perform bdc_dynpro      using 'SAPLMIGO' '0001'.
                     perform bdc_field       using 'BDC_OKCODE'
                                                   '=OK_GO'.
                     perform bdc_field       using 'GODYNPRO-ACTION'
                                                   'A01'.
                     perform bdc_field       using 'GODYNPRO-REFDOC'
                                                   'R05'.
                     perform bdc_field       using 'GODEFAULT_TV-BWART'
                                                   '109'.
                     perform bdc_field       using 'BDC_CURSOR'
                                                   'GODYNPRO-OUTBOUND_DELIVERY'.
                     perform bdc_field       using 'GODYNPRO-OUTBOUND_DELIVERY'
                                                   wa_likp-vbeln. "'80019574'.
                     perform bdc_field       using 'GOHEAD-BLDAT'
                                                   lv_date_external. "'04/29/2015'.
                     perform bdc_field       using 'GOHEAD-BUDAT'
                                                   lv_date_external. "'04/29/2015'.
                     perform bdc_field       using 'GOHEAD-WEVER'
                                                   '1'.
                     perform bdc_dynpro      using 'SAPLMIGO' '0001'.
                     perform bdc_field       using 'BDC_OKCODE'
                                                   '=OK_POST1'.
                     perform bdc_field       using 'GODEFAULT_TV-BWART'
                                                   '109'.
                     perform bdc_field       using 'GOHEAD-BLDAT'
                                                   lv_date_external. "'04/29/2015'.
                     perform bdc_field       using 'GOHEAD-LFSNR'
                                                   wa_likp-vbeln. "'0080019574'.
                     perform bdc_field       using 'GOHEAD-BUDAT'
                                                   lv_date_external. "'04/29/2015'.
                     perform bdc_field       using 'GOHEAD-WEVER'
                                                   '1'.
                     perform bdc_field       using 'GODYNPRO-DETAIL_ZEILE'
                                                   '   1'.
                     perform bdc_field       using 'GOITEM-ERFME'
                                                   'EA'.
                     perform bdc_field       using 'GOITEM-ERFMG'
                                                   '1'.
                     perform bdc_field       using 'GOITEM-LSMNG'
                                                   '1'.
                     perform bdc_field       using 'GOITEM-LSMEH'
                                                   'EA'.
                     perform bdc_field       using 'GOITEM-MIGO_ELIKZ'
                                                   '1'.
                     perform bdc_field       using 'GOITEM-BWART'
                                                   '109'.
                     perform bdc_field       using 'GOITEM-LGOBE'
                                                   'RX Cross-docking'.
                     perform bdc_field       using 'BDC_CURSOR'
                                                   'GODYNPRO-DETAIL_TAKE'.
                     perform bdc_field       using 'GODYNPRO-DETAIL_TAKE'
                                                   'X'.
                     PERFORM bdc_dynpro      USING 'SAPLMIGO' '1300'.
                     PERFORM bdc_field       USING 'BDC_CURSOR'
                                                   'G_TIP_DONT_SHOW_AGAIN'.
                     PERFORM bdc_field       USING 'BDC_OKCODE'
                                                   '=OK_TIP_GO'.
                     PERFORM bdc_field       USING 'G_TIP_DONT_SHOW_AGAIN'
                                                   'X'.
    *& Avoid unncessary screens to populate while processing background.
                     LV_OPTIONS-DISMODE = 'N'.
                     LV_OPTIONS-UPDMODE = 'S'.
                     LV_OPTIONS-NOBINPT = 'X'.
                     CALL TRANSACTION 'MIGO' USING BDCDATA  OPTIONS FROM LV_OPTIONS MESSAGES INTO IT_MESSTAB1 .
                     WAIT UP TO 1 SECONDS.
                     DELETE IT_MESSTAB1 WHERE MSGTYP NE 'E'.
                     IF IT_MESSTAB1[] IS NOT INITIAL.
                       APPEND LINES OF IT_MESSTAB1 TO IT_MESSTAB.
                     ENDIF.
                   ENDIF.
                 ENDIF.
               ENDLOOP.
             ENDIF.
           ELSE.
             MESSAGE 'Shipment Number does not exists Or not Planned' TYPE 'E'.
           ENDIF.
         ELSE.
           MESSAGE 'Please insert Shipment Number' TYPE 'E'.
         ENDIF.
         IF lv_flag1 = 'X' AND lv_flag2 = 'X'.
           MESSAGE 'This shipment is processed with an inconsistent goods receipt' TYPE 'I'.
         ELSEIF lv_flag1 = 'X'.
           MESSAGE 'Shipment already been processed for these deliveries' TYPE 'I'.
         ELSEIF lv_flag2 = 'X'.
           lv_lines1 = lv_lines.
           CONDENSE lv_lines1 NO-GAPS .
           CONCATENATE lv_lines1 'Goods Receipt are posted for the shipment '
                  INTO lv_message SEPARATED BY space.
           MESSAGE  lv_message TYPE 'I'.
         ENDIF.
    * Display Messages from Message TAB.
         DELETE ADJACENT DUPLICATES FROM IT_MESSTAB.
         DATA:lv_msg TYPE string.
         LOOP AT IT_MESSTAB INTO WA_MESSTAB.
           CALL FUNCTION 'FORMAT_MESSAGE'
             EXPORTING
               ID        = WA_MESSTAB-MSGID
               NO        = WA_MESSTAB-MSGNR
               V1        = WA_MESSTAB-MSGV1
               V2        = WA_MESSTAB-MSGV2
               V3        = WA_MESSTAB-MSGV3
               V4        = WA_MESSTAB-MSGV4
             IMPORTING
               MSG       = lv_msg
             EXCEPTIONS
               NOT_FOUND = 1
               OTHERS    = 2.
           IF sy-subrc <> 0.
    * Implement suitable error handling here
           ENDIF.
           WRITE:/ lv_msg.
         ENDLOOP.
    *        Start new screen                                              *
       FORM BDC_DYNPRO USING PROGRAM DYNPRO.                 "#EC PF_NO_TYPE
         CLEAR BDCDATA.
         BDCDATA-PROGRAM  = PROGRAM.
         BDCDATA-DYNPRO   = DYNPRO.
         BDCDATA-DYNBEGIN = 'X'.
         APPEND BDCDATA.
       ENDFORM.
    *        Insert field                                                  *
       FORM BDC_FIELD USING FNAM FVAL.                       "#EC PF_NO_TYPE
         CLEAR BDCDATA.
         BDCDATA-FNAM = FNAM.
         BDCDATA-FVAL = FVAL.
         APPEND BDCDATA.
       ENDFORM.
    Thanks,
    Srini

    Hi Rob,
    Thanks for quick reply.
    I have checked the NOTE : 304122
    But there in the NOTE it says ( " BAPI, BAPI_GOODSMVT_CANCEL, BAPI_GOODSMVT_CREATE, CNTL_ERROR" )
    These BAPI's work perfectly for (purchase order as input type), but here out type is ( A01 & R05 ) we are giving DELIVERY NUMBER as input to MIGO.
    So for this scenario we cannot use those BAPI's mentioned in the NOTE.
    Also as stated earlier in the message interesting part is
    "The code works absolutely perfect only from my ID. But when I test from other ID it is not executing. Code is working exactly as expected ONLY to my ID. When i try to execute the same code from another's ID it is not working"
    So what do you think might be the issue?

  • Material movement from Quality to Unrestricted

    Dear All
       My problem is that i have given UD for a particular batch and posted the stock from quality inspection to unrestricted use.
    But when i see in the stock overview the quantity still lies in Quality i.e in MMBE
    But when i see in QA33 the stock is available in Unrestricted.
    Kindly give me a solution
    Regards
    Surender

    Dear,
    Use movement 321 to move material from QI to unrestricted and movement 343 from blocked to unrestricted.
    Regards,
    R.Brahmankar

  • Returns to unrestricted movement type

    Hi Folks,
    What is the movement type for returns to unrestricted stock.
    Thanks in advance.

    use movement type 453 through MB1B t-code
    regards,
    ramky

  • How to block movement type 261 and 262 from several storage locations

    Dear Expert,
    Can we block the  261 and 262 movement type from several storage locations? These storage locations are not affected by the MRP run, where for the materials that have been moved to these storage locations their existance are not count. These storage locations could not be used for confirmation production order, therefore i want to block  261 and 262 movement type from these storage locations.
    Thanks
    Pauline

    Dear Pauline,
    if my understanding is correct abt ur query,
    1) you want in confirmation screen, Consumption should happen only from one storage location
    2) Rest all storage locations should not be allowed
    3) Maintain Storage location in BOM component view, in mass you can maintain in CEWB
    4) Now GO with SHD0, Make storage location field as Out put only, for CO11N Transaction
    Plz refer this link for SHD0 Demo
    [https://www.sdn.sap.com/irj/scn/wiki?path=/display/snippets/transactionVariant-AStepbyStepGuidefor+Creation]
    Regards
    Madhu Kumar

Maybe you are looking for