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.

Similar Messages

BAPI_GOODSMVT_CREATE is not working for movement type 701 in MIGO

Hi gurus
Can anybody help to track that bapi: BAPI_GOODSMVT_CREATE is not working for movement type 701 for MIGO Transaction.

call this standard BAPI, AND EXECUTE IN SE37
""Local Interface:
*" IMPORTING
*"     VALUE(GOODSMVT_HEADER) LIKE BAPI2017_GM_HEAD_01 STRUCTURE
*"        BAPI2017_GM_HEAD_01
*"     VALUE(GOODSMVT_CODE) LIKE BAPI2017_GM_CODE STRUCTURE
*"        BAPI2017_GM_CODE
*"     VALUE(TESTRUN) LIKE BAPI2017_GM_GEN-TESTRUN DEFAULT SPACE
*"     VALUE(GOODSMVT_REF_EWM) LIKE /SPE/BAPI2017_GM_REF_EWM STRUCTURE
*"        /SPE/BAPI2017_GM_REF_EWM OPTIONAL
*" EXPORTING
*"     VALUE(GOODSMVT_HEADRET) LIKE BAPI2017_GM_HEAD_RET STRUCTURE
*"        BAPI2017_GM_HEAD_RET
*"     VALUE(MATERIALDOCUMENT) TYPE BAPI2017_GM_HEAD_RET-MAT_DOC
*"     VALUE(MATDOCUMENTYEAR) TYPE BAPI2017_GM_HEAD_RET-DOC_YEAR
*" TABLES
*"      GOODSMVT_ITEM STRUCTURE BAPI2017_GM_ITEM_CREATE
*"      GOODSMVT_SERIALNUMBER STRUCTURE BAPI2017_GM_SERIALNUMBER
*"       OPTIONAL
*"      RETURN STRUCTURE BAPIRET2
*"      GOODSMVT_SERV_PART_DATA STRUCTURE
*"        /SPE/BAPI2017_SERVICEPART_DATA OPTIONAL
*"      EXTENSIONIN STRUCTURE BAPIPAREX OPTIONAL
*"      GOODSMVT_ITEM_CWM STRUCTURE /CWM/BAPI2017_GM_ITEM_CREATE
*"       OPTIONAL
call function 'BAPI_GOODSMVT_CREATE'
    exporting
      goodsmvt_header         = goodsmvt_header
      goodsmvt_code           = goodsmvt_code
      testrun                 = testrun
      goodsmvt_ref_ewm        = goodsmvt_ref_ewm
    importing
      goodsmvt_headret        = goodsmvt_headret
      materialdocument        = materialdocument
      matdocumentyear         = matdocumentyear
    tables
      goodsmvt_item           = goodsmvt_item
      goodsmvt_serialnumber   = goodsmvt_serialnumber
      return                  = return
      goodsmvt_serv_part_data = goodsmvt_serv_part_data
      extensionin             = extensionin.
commit work.
hi, rewards point, if this is useful,
regrds
karthikeyan

Movement Type 541

Hi All,
I am using the movement type 541 for GI .I have attached a ZFORM OF WESCHEINVERS3.I have Two line items for a material document number.For line item 10 i have posted the document and not for line item 2.But in the print preview its giving me both.I need only those line items which are posted.
Please help me
Regards
Lalit

Mathur:
From the link:
http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/mb04-subsequent-adjustment-1108606
We create a subcontracting purchase order. We add components to the PO. We then create a delivery using transaction ME20. Once the delivery is
posted the material shows at the vendor being transferred with movement
type 541. When the vendor ships in the material we perform a GR which receives the
assembly and removes the material at vendor with a movement type 543.
I believe your offsetting entry would be 543, 542 is used for reversal
For more info:
http://www.sap-basis-abap.com/sapmo006.htm
Assign points if info helps
Vj
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left.

Error in Goods issue with movement type 541

Dear Users,
I have created a Sub contracting PO. After that when i m issuing the goods to vendor with movement type 541, its giving the following error: Movement type 541 is not planned for this operation.
Please help me out

You can provide material to vendor either using Transaction codes :
1. MIGO - Transfer Posting - Other - Movement type 541
2. MB1B - Movement type 541 or
3. ME2O - Mention the vendor & execute
S. Kumar

No budget check during MB1A mov type 201

Dear All
How to exclude MB1A by using mov type 201 from budget check. I actually want to issue goods to cost center and don't want budget consumption in cost center where goods and issue and on the same time sending plants budget should also not be reduced
Thanks in advance

Dear Eli,
Thanks for your instant reply. I want to issue the goods to cost center by using Mov type 201at this time my consumption gl and inventory gl will be used and same is the commitment item. Now inventory gl cannot be made as dummy commitment item as during migo it will not consume budget (if wrong please correct me) and also consumption gl/commitment item i want it to be excluded only in case of 201 not in other mov type.
As per your second option could you please elaborate as i couldnt get that.
Regards,

MIGO, movement type 412 E

Hi,
I am attempting to create a reservation against a sales order using transaction MIGO, movement type 412 E. I have entered the sales order number and I am getting the message Document 257 does not contain any selectable items.
I have also created a new item category code and updated it with the special stock indicator 'E'.
Is there anything else that I need to do?
Regards,

HI
check this links
MIGO(SA)does not contain any selectable items
Reservation against the sales order
Regards,
Krishna.
Edited by: kris_hna on Sep 6, 2011 10:58 AM
Edited by: kris_hna on Sep 6, 2011 11:41 AM

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

Table MSEG with movement type 541

Dear All,
In order to display the PO number, we maintain the customizing for
movement type 541 in Transaction Code OMBW. Here we change the indicator
From 'Suppress' inot 'Opt. entry', then the created material document
will display the PO number in Table MSEG.
Similarly if we want to display PO line item number,in which part we should do the Opt. entry????
regards,
indranil

As of my knowledge, It is not Possible.
Any way in the same trxn code OMBW Check the commitment Item Once for 541 Mov type.
Regards,
Ashok
Edited by: Ashok Kumar Telikula on Aug 29, 2008 2:50 PM

MRN2- Impact if we add movement types 541 and 542

Hi ,
Hungary country is using MRN2 Tcode with Selecting data base update option.This tcode will call for movement types tcode OMWV(Table TNIW4). Presently we have movement types 101, 102,103,104,105,106,201,202,,221,222,261,262,501,502 in the tcode OMWV.This is at client level.
              Now Romania country wants to add movement types 541 and 542 . So if we add these movement types then what is the impact for the Hungary country as it is at client level .????????
As Hungary countryusing data base update option, in the material master under accounting 2 tab tax price 1 and devaluation indicator fields are updating..
Thanks & regds
ramachandra

Hi,
    A) As long as Hungary does not use these there is no effect.
   B) If HU does use these then in general you movement rates will be higher, resulting in less devaluation (hence a higher stock value). Since these are transfer postings (and not consumption or receipt) i do not think that they should be included.
   If RO insist, the best solution is to make copies of 541/542 which RO will then have to use and can be added for MRN2 without influencing HU.
Kind regards

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

MM Issue Movement type 541

Hi All,
I have generated a sap-script form for Goods Issue Slip.I went to mb1b Transaction and posted one line item .But in the form its showing both line items ,I want only those line items which are posted.Please help me on the same .
Regards
Lalit

hi lalit,
SAP system allows user to issue material to the vender through 541 movement type (transfer posting -MB1B) without refering to any purchasing document.
It's a standard SAP functionality which you can control in two ways:
1. Field settings : Change fields settings for 541 to include Purchase Order number field as mandatory in the screen. But, this is a weak control as you can enter a Purchase Order and send any material to vendor.
OMBW - double click 541 -> double click Material Management
2. Change the IMG settings for movement type 541 and remove the transaction code MB1B as allowed transaction code. Use ME2O only. If you want to issue excess material to vendor, you will have to change the Purchase Order components.
OMJJ - click the Select all button
              Type 541 for the Movement Type
              Click the Back button
              Click Allowed Transactions
              Delete transaction code for MB1B
reward me points if helpfull
karthikeya

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?

Error in MIGO Movement type 101 E is not planned.(Entry is not copied over)

Hie Experts,
I had created a process order for XYZ material. Now i want to assign this goods receipt to sales order. For this i am trying to go MIGO with mvt type 101 & special stock indicator as 'E'(order stock). I am facing the error as "Movement type 101 E is not planned. (Entry is not copied over)".
Can anyone help to solve this error.
Regards,
Piyush

Hie,
Thanks for your valuable response. But, my scenario is like this. I am doing goods receipts against PRODUCTION Order.
I want to take this stock as Sales order stock(Special Stock).
Can u pl help me for this scenario.
Regards,
Piyush

MIGO - GR - Others -- Serial Number Not saved for Movement Type : 561

Hello,
I am trying to post good receipt-other ( for movement type 561) using MIGO transaction. I have specified all required data.
Also depending on the item qty., I entered serial number in serial number tab.
Its creating document successfully. However if I try to display same document using MIGO, serial number is missing.
I tried to debug the code and I realized its not saving serial number itself.
For other movement type its creating document with correct serial number.
If I repeat same process using same data using transaction MB11 its posting successfully and I can see serial number using MIGO transaction as well.
One more thing which I've noticed is when I post document using MIGO, Account assignment details are missing. However with MB11 I can see account assignment data too.
Would be really appreciated if someone can help me on this. I dont know If I'm missing any configuration part here.
Thanks & Rgds,
Nilesh

Any help Experts?
Nilesh

Migo (Movement type 101) does not update quntity in the report.

Dear experts,
I have a custome report for goods receipt (ABAP Query).
In this report, quntity (unrestricted stock) is not updated when I do MIGO (mType 101). The quntity however, is updated in MMBE unrestricted stock columm after MIGO.
Could you please help me how to make quntity updated in the report when I do MIGO with movement type 101?
I thank in advance for all replies.
Jaan
Edited by: Bhajan Singh on Feb 9, 2010 10:19 AM

Thanks R.S. Nambi for your rpely.
The question is solved.
I went to query, then Additional fields and picked movement tyep-quntity field, went to Local fields and added complex calculation for mtype 101.
I am going to close this thread.

Customize delivery note during MIGO mov. type 541

Similar Messages

Maybe you are looking for