Output Print for MIGO movement type-107.

Hi All kindly help me in resolving the following issues:-
There is the requirement of printing RF Label while saving the GR from PO in movement type-107.
Help me to configure the output type in this case.
How the data flows from MIGO transaction to the ABAP program and finally to the printer ?
How to link the output type to the transaction MIGO and so in movement type-107 ?

Hi,
go to spro-Materials Management-Inventory Management and Physical Inventory-General Settings.
in General Settings print version migo is 2 .execute after Maintain Print Indicator for Goods Receipt Documents check 107 mvt type.
refer the below link
Print material document (WE02) automatic when GR
Regards
Raj.

Similar Messages

  • BAPI for MIGO - Movement Type 122 - Return deliveries to vendor

    Hi,
    I've been reading about bapi's for migo and the most commom was: BAPI_GOODSMVT_CREATE
    But I want to do a Movement Type 122, and that is not supported by the BAPI.
    Any idea beside Batch Input ?

    Ildar,
    Try this:
    GOODSMVT_HEADER:
    PSTNG_DATE
    DOC_DATE
    REF_DOC_NO (mandatory)
    GOODSMVT_CODE = 01
    GOODSMVT_ITEM
    MATERIAL
    PLANT
    STGE_LOC
    MOVE_TYPE = 122
    ENTRY_QNT
    PO_NUMBER
    PO_ITEM
    MVT_IND = B (reference to the document that has the request )
                    MOVE_REAS (mandatory as well)
    Let me know if you need any further help.
    Francisco Coutinho,
    ToInovate

  • 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?

  • MIRO should not happen for Movement Type 107

    Dear All,
    We have a peculiar scenario/requirement fulfilled by business and we have done almost all but getting stuck in below area:
    We have developed a output type in order to automatically post Mat Doc with Movement Type 107 once the user reverses Material Document with Mvt Type 103, This as per a business requirement. That means when 104 will be done for a Mat Doc with Mvt Type 103, "PO History Tab" will display in following order:
    103 > 104 > 107
    After 107, user will reverse it with Mvt Type 108 and specific G/L accounts will be hit which will update the "PO History" as:
    103 > 104 > 107 > 108
    Now issue is we want MIRO to be possible for Mvt Type 108, not for Mvt Type 107 else it will create a vendor liability twice and business will end up paying amount to vendor twice.
    How can this be achieved?
    Your sound suggestions are most welcome.
    Regards
    Samier Danish

    No replies
    Regards
    Samier Danish

  • MIGO T code for 453 Movement type

    hi sap gurus,
    I am getting These error message when i am using MIGO T code for 453 Movement type
    Deficit of BA Ret.blocked prev. 104 EA : NTH-607-P5G 1034 3401 5786051

    This means your stock level in return blocked stock is not sufficientt to be able to carry out the goods movement. Check your stock level for your material in MARD-RETME (or in MB52).
    Mvt 453 means stock transfer from return blocked stock (that was sent back by customer) to your own stock. Return blocked stock is owned by the customer, through this goods movement you take over the ownership of the goods.
    Regards,
    Csaba

  • What is the need for movement type 107

    Hi Gurus,
    In ECC 6.0 i have seen that SAP has introduced 107 for GR Block stock (valuated). Can anyone tell me the business sense for doing so.
    What was the exact need for introducing 107
    Rgds
    Venkat

    Hi,
    GR Blocked valuatedstock menas , when you do the GR with movement type 107 it  will posted under Plant and the value of the goods will be considerd/increased for that Plant. But the stock will be under Blocked Stock..It will not be used all other purpose till you do the transfer psting from Blocked to unresticted.
    Thanks,
    Kumar Arcot

  • Customize delivery note during MIGO mov. type 541

    Hi, everyone.
    Pls. I need help because during MIGO mov. type 541, I need to print the delivery note just to accompany the materials.
    I can create/save the material doc. correctly, but when I save I have to customize the printout of delivery note.
    Thanks for tell me the step by step.
    Regards.

    Hi,
    Following are the general settings to take the printout of any materail document posted by MIGO:
    Go through these steps you can get the GRN Printout
    1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
    Enter the local printer where you want to print your Goods posting document
    2. Ensure that in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Item Print Indicator, 1 stands for Matl Doc print out
    3. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Print Version, maintain Print Version 2
    4. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Maintain Print Indicator for Goods Receipt/GI/Transfer Posting Documents
    Here for Particular mvt type 101,201,121,311,541 etcu2026 Maintain the Print item as 1--Material document printout
    5. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WE01, WE02 and WE03, ensure the following--
    Select the particular Output type then goto Details
    a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Transmission medium is 1
    b. Print Parameter is 7
    6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Printer Determination by Plant/Str Loc, Maintain the Output device for all your Plants
    7. Go to MN21, for Tr Type WE, Print Version 3, maintain Print Item as 1.
    Now the settings are ready for Printing Material doc
    8. While doing MIGO, ensure that in General Tab, you get "3 Collective Slip" beside the Print Indicator and you tick mark the field.
    9. Now depending on the setting in 5a, the Matl doc is printed. If it is 3, you have to print it using MB90. If it is 4, it is printed immediately.

  • GL posting during movement type 107 & 108

    Presently system is posting to inventory Gl Account for rejections ,returns and damages from customers during 107 and 108 movement type in MIGO
    we want system to post to different GL Account with respect to reason for movement only  during Movement type 107 and 108
    Edited by: Prabhudev on Nov 8, 2008 9:39 AM

    Hi
    These are the new movemnt types used for Goods receipt with ref. to Purchase order
    107 Mvt recives the Stock as GR Blocked Stock but with Value, An accounting document gets generated
    109 Mvt moves the material fro GR Blocked stocked to Unrestricted use stock , No accounting Documents are generated.
    108 & 110 are reversal movements ffor 107 & 109
    These movments are similar to that of 103 & 105. Which are used for 2 step GR w.r.t PO
    In 103  Stock type is GR Blocked stock with out value , no accounting document genareated
    105 Stockm is moved from GR blocked to Unrestricted use. accounting document is generated.
    hope this helps
    Edited by: Manohar Raju on Feb 26, 2008 10:53 AM

  • Output Determination for Material movement

    Hi All,
    I am configuring output Determination for Material movement.
    In my case, am doing the config when the movement type is 311, we want to generate IDoc.
    i have configured everything, output type,output Determination schema..
    When i am trying to maintain the condition record for the same through MN21,
    here i am facing one problem on Partner Function.
    Here what partner functuion i'll give.
    waiting for all valuable response.
    Regards
    Indrashish

    Hello Indrashish,
    Maintain that output type as partner independent.
    This will help.
    Regards
    Arif Mansuri

  • How to set receiving batch mandatory in MIGO-mov type 303

    Hi gurus,
    We want to set receiving batch mandatory in MIGO-mov type 303.
    We already made this field (UMCHA) as Required in OMJJ under Field selection-Enjoy and Field selection (from 201)/Batch search procedure, but when do transaction, the field still not even appear. Can you help to know how to do that?
    Many thanks in advance

    Hello HongNguyen ,
    Please try the following customzing path in your system if you haven't already:
    - Transaction SPRO
       - IMG
         - Materials Management
          -  Inventory Management and Physical Inventory
            - Settings for Enjoy Transactios
               - Settings for Goods Movements (MIGO)
                  -   Field Selection per Mvt Type
    Please check your settings for Movement Type 303 and see if they are set to "Mandatory".
    I hope this information has been helpful.
    Best Regards,
    Frank

  • Quality Inspection for a Movement Type 103 , change batch when doing QA11 .

    Hi all,
    I activated Quality Inspection for a Movement Type 103 .  When do MIGO(GR 103) reference to PO ( include material A, qty 100 PC), it will  create insp lot. Material  A  needs batch management.
    1st time use QA11 to post  50 PC  to stock, it will create a new batch( or you can select a exist batch ).
    2nd time use QA11 to post another 50 PC to stock, it will use the batch 1st time used, and you can't change this batch number .
    The question is : how to change  batch number at the 2nd time ?
    Thanks.

    Hi,
    Pls. check that how u have configured the new batch number in configuration for goods movement.

  • How to set error message for 541 Movement type

    Dear gurus,
                I want to know that is it possible to set error message through any configuration? My requirement is that when we create issue document using m.t 541 it will not allow me to process that document without releasing PO document.so for that i want to set error message.
    <removed by moderator>
    Message was edited by: Jürgen L

    Hi,
       The subcontracting goods issue can be done even without PO reference. If your organization is strictly following the goods issue against PO only and you want to restrict the goods issue if the PO is not released, then you may check the below option. Please note that the below option is available in standard only from EHP 4 or above.
    1. Refer the KBA: 1915825 - Transfer Posting reference to a Purchase Order in MIGO and activate the PO reference option in MIGO - Transfer posting.
    2. Restrict the use of 541 movement in MB1B - Go to OMJJ and enter movement type as 541. Now go to "allowed transactions" folder and remove MB1B. Now the user cant use 541 in MB1B.
    3. Maintain the field - Purchase order as mandatory field for the movement type 541 in OMJJ.
    4. Train the users to use MIGO - Transfer Posting - Purchase order option for goods issue with 541 movement.
    5. If the PO is not released, system wont allow to use the PO in MIGO - Transfer Postings.
    6. If the user is selecting Transfer Posting - Other, system wont check the PO and hence it will allow to post the goods issue even if PO is not released. You may take organizational measures to restrict the usage or you may check for authorization concept - Refer the note: 773003 - MIGO: No authorization object for action/reference document
       If you are below EHP 4, there is no standard functionality available for the requirement as of my knowledge. If so, you may go for development to restrict the same.
    Regards,
    AKPT

  • Sap notes for 103 movement type and 105 movement types in sap

    Hi all,
    Please let me know if there are any sap notes for 103 movement type and 105 movement type in sap as soon as possible
    points will be awarded.
    thanking u in advance,
    srinivas.

    There are many SAP notes related to these movement types e.g 514609,750836,
    533833, 808029, 317823,etc.
    You can search them at http://service.sap.com
    Regards,
    Amit

  • Report MB5B for selected movement types

    Dear All,
    When I am executing report for selected movement types , system givivng me message below " Movment type is reset"
    After continuing that Movement type field turns BLANK, and report is executed with considering all movement types.
    If there is a way for executing MB5B report for selected movement types, please suggest.
    Thanx..

    Hai,
    1.The MB5B report will show the stock on posting date with all movements like Goods recipt from Purchase, production order, stock transport order, & goods issue due to consumption posting, stock transfers & transfer posting.
    2. This is designed to see the Opening balane+Goods receipt - goods issue = closing balance.
    3.You can't take report only for particulat movement type.
    4.If u want to get the details as per the movement type, then use MB51 report.

  • PGI for STO movement type error Message no. L9005

    Hi Gurus,
    I have created an STO.Created delivery and confirmed TO.
    Now while doing PGI,single step only(647 movement type),
    system throws the following message,
    "" Error during search for WM movement type (641 1 L K  )
       Message no. L9005 "".
    As per my checking for both IM movement types 641 and 647, ' 641 ' has been assigned as
    Ref movement type and " 601"  has been assigned as WM movement type.
    601 is maintained in WM.Should I maintain 641 in WM?That case I have to change SAP std settings..
    If so pls provide me the details for 641 K.
    Kindly help.
    Best Regards

    Hi Kumar,
    Try the following:
    Maintain an entry for your warehouse with movement type 641 SpStIn and Movment Indicator l combination in transaction OMLR.
    And also ,
    Check in IMG Path - Enterprise Structure --> Assignment --> Logistis Execution --> Assign warehouse number to plant/storage location.
    Here check whether the warehouse number is assigned to your plant and storage location.
    Thanks!
    Preethi
    Edited by: preethi R on Dec 2, 2008 10:50 AM
    Edited by: preethi R on Dec 2, 2008 10:50 AM

Maybe you are looking for