Refurbishment initial movement type

Hi,
Please clarify which movement type needs to use for moving material from productional shop floor to repairable storage location for refurbishment , and is it possible to maintain any reference document for that initial process like as reservation hard copy.
Regards
Senthil

Hi ,
I am appreciating ur answer , but What you have answered is not for my question and Hopefully U know the purpose of Refurbishement process.
My requirement I want to move material which is failed from equipment and obviously not maintained in any stores .
Ok .. I want to move material from shop floor to storage location which is failed from equipment .
Thanx
Sendil

Similar Messages

Movement types for material movements in refurbishment process

Hi,
I require some clarification about the movement types to be used when posting material movements in the standard refurbishment process.
I am mentioning the standard refurbishment process below. Please correct me if I am wrong or if I missed anything.
1) Dismantle a defective spare part from the machine.
2) Take this defective spare to a storage location for unserviceable stock. (Materials movement-post GR)
3) Withdraw a new or repaired spare for the above material. (Materials movement-post GI)
4) Install the the above new or repaired spare to the machine.
5) Repair the defective spare.
Now I am confused and what I require to know is that for steps 2 and 3 what transaction to use for goods movement and what standard movement types are recommended for this GR and GI?
Thanks and regards,
Abhijit Dutta

Abhijit Dutta
The standard Refurbishment process does not involve the initial move into the warehouse/stock. That is part of the standard maintenance processes.
The Refurbishment takes defective item from the warehouse (goods issue), repairs them, and returns the, back to stock (goods receipt). Usually these items are valuated stock.
[SAP Help|http://help.sap.com/erp2005_ehp_04/helpdata/EN/5b/ae3bf14b8611d182ba0000e829fbfe/frameset.htm]
PeteA

Initial Stock Upload T code MB1C and Movement Type 561through LSMW - Error

Hi,
Trying to Upload the Initial Stock, Transaction Code MB1C and Movement Type 561 through LSMW.
While recording the fileds, system giving a message of Code Block.
Please let us know about Code Block while uploading the Initial Stock.
Thanks
Siddu.

Check this thread
[Re: Coding Block in LSMW recording via MB1C|Coding Block in LSMW recording via MB1C;
thanks
G. Lakshmipathi

MB11/MB1C/MB1B post GL entry for tax for movement type 561 initial stock

Hi,
We want to bring in stock into new system using movement type 561. The usual account posting is:
Debit stock
Credit account in OBYC GBB
How can I add additional tax posting in the transaction? For e.g.
Debit stock
Debit input tax
Credit account in OBYC GBB
I tried to open up the Tax Code in the movement type field status but it doesn't show up in any of MB11/MB1C/MB1B.
Any customized BAdI/user-exit for this?
Any suggestions?
Thanks in advance for help!

hi,
you cant update the tax account directly using the 561 mov type.
please find below the link for more clarifications regarding the tax accounts.
http://forums.sdn.sap.com/thread.jspa?threadID=2126200
Regards,
velu

Accounting Document for New Movement Type

Good day!
Here's the scenario: I have created a new movement type in SPRO. I just copied from the existing movement type closely related to what I wanted to create. I executed the transaction in MB1C and it went well and generated a Material Document number. When I viewed the Material Document number in MB03, it has no Accounting Document number. Is there any config that i missed? How can I relate this transaction to accounting?
Thank you for your assistance.

hi
first check which movement type u have copied .
now check is ur material is valuated for the plant
now in OMJJ go to ur movemnttype and in update control u should have value and quantity update entry
also check if u have used the po as free or if it is initial entry then check ur material master price
hope it hellp
regards
kunal

Error while using BAPI_GOODSMVT_CREATE wiht movement type 311.

Hi All experts,
i am geting error msg, while using BAPI_GOODSMVT_CREATE wiht movement type 311.
the error msg is " For reservation 0000443815 0000, no movements can be posted".
Here is my code.
IF I_ZMM_S_MBIB_LOT[] IS NOT INITIAL.
*moving posting date and document date to header
    GOODSMVT_HEADER-PSTNG_DATE = ZMM_S_MBIB_311-BUDAT.
    GOODSMVT_HEADER-DOC_DATE   = ZMM_S_MBIB_311-BUDAT.
    LOOP AT I_ZMM_S_MBIB_LOT WHERE MENGE NE '0'.
      IF I_ZMM_S_MBIB_LOT-IND = 'X'.
*moving material and plant ,stge_loc,qty and movement type to header
        GOODSMVT_ITEM-MATERIAL       = I_ZMM_S_MBIB_LOT-MATNR.
        GOODSMVT_ITEM-PLANT          = I_ZMM_S_MBIB_LOT-WERKS.
        GOODSMVT_ITEM-BATCH          = I_ZMM_S_MBIB_LOT-CHARG.
        GOODSMVT_ITEM-STGE_LOC       = I_ZMM_S_MBIB_LOT-SLGORT.
        GOODSMVT_ITEM-MOVE_TYPE      = '311'.
        GOODSMVT_ITEM-ENTRY_QNT      = I_ZMM_S_MBIB_LOT-MENGE.
        GOODSMVT_ITEM-ENTRY_UOM      = I_ZMM_S_MBIB_LOT-MEINS.
        GOODSMVT_ITEM-MOVE_MAT       = I_ZMM_S_MBIB_LOT-MATNR.
        GOODSMVT_ITEM-MOVE_PLANT     = I_ZMM_S_MBIB_LOT-RWERKS.
        GOODSMVT_ITEM-MOVE_BATCH     = I_ZMM_S_MBIB_LOT-UMCHA.
        GOODSMVT_ITEM-MOVE_STLOC     = I_ZMM_S_MBIB_LOT-UMLGO.
        GOODSMVT_ITEM-RESERV_NO      = I_ZMM_S_MBIB_LOT-RSNUM.
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
        EXPORTING
          GOODSMVT_HEADER               = GOODSMVT_HEADER
          GOODSMVT_CODE                 = '04'
      TESTRUN                       = ' '
      GOODSMVT_REF_EWM              =
        IMPORTING
      GOODSMVT_HEADRET              =
          MATERIALDOCUMENT              = MATERIALDOCUMENT
          MATDOCUMENTYEAR               = MATDOCUMENTYEAR
        TABLES
          GOODSMVT_ITEM                 = GOODSMVT_ITEM
      GOODSMVT_SERIALNUMBER         =
          RETURN                        = RETURN.
      GOODSMVT_SERV_PART_DATA       =
      EXTENSIONIN                   =
    ELSE.
Moderator message: duplicate post locked.
Edited by: Thomas Zloch on Feb 23, 2011 11:46 AM

Hi Sachin,
Pass the Item Number of Reservation to GOODSMVT_ITEM-RES_ITEM .
Regards
DKS

Creation of TO with 101 Movement type

Hi
My requirement is:
To create a Transfer Order(TO) with Movement Type 101 and when TO is created, checkbox "Immediate TO" should get ticked.
For TO creation I am using : L_TO_CREATE_MULTIPLE
But Checkbox "Immediate TO" does not gets checked for the PO.
Please suggest how to proceed.
Many thanks in advance.

Hi Andrei
Thanks for your reply. What you have mentioned above is correct.
Immed. TO(Checkbox under WM tab in Material Document)
Automatic TO Creation Immediately After TR Generation
Indicator determining that automatic transfer order generation is active.
Automatic transfer order generation can be initiated both during the creation of the IM document as well as during material staging for production orders (PP interface).
After the IM document has been created, a transfer order for a transfer requirement or for a posting change notice is created, provided the following requirements are met:
Automatic transfer order generation is active (depending upon the movement type for all items of the IM document for which a transfer requirement or a posting change notice is to be created.
Within the entire document, the postings are executed in one warehouse number only.
If the current document is to created for each function module, for example, from the usage decision of QM, the automatic transfer order generation function must not be switched off. This can be the case if on the basis of the constellation in the inspection lot automatic TO generation is not appropriate (see also the documentation on the interface WM <-> QM).
My requirement is not to use Customization i.e. I donot want to check 'Automatic TO' in customization.
Instead I am using FM: L_TO_CREATE_MULTIPLE in a program for TO creation.
And when TO is created with Movement type '101' from the program, it should also check the checkbox 'Immed. TO'
Just wanted to confirm if this is possible.
Thanks & Regards,
Shashank

Dump while doing goods issue against order with movement type 261

Hi Team,
We are integrating Asset management process along with the goods issue against the order which is created with a business partner for movement type 261.
when we try to complete the process the system gives us a dump as described below.
please look through the dump and advice for the same.
Short text
    The current application triggered a termination with a short dump.
What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
Error analysis
    Short text of error message:
    System error in the FI/CO interface
    Long text of error message:
     Diagnosis
         Updating of the FI/CO interface was called with object type "MKPF"
         yet the checks were run for object type "AMBU".
     System Response
         Checking and updating must be for the same object type.
     Procedure
         It has to do with a system error from the calling applications.
    Technical information about the message:
    Message class....... "RW"
    Number.............. 103
    Variable 1.......... "MKPF"
    Variable 2.......... "AMBU"
   Variable 3.......... " "
   Variable 4.......... " "
rigger Location of Runtime Error
   Program                                 SAPLMBWL
   Include                                 LMBWLU21
   Row                                     62
   Module type                             (FUNCTION)
   Module Name                             MB_POST_GOODS_MOVEMENT
46    IF xmkpf-xabln IS INITIAL.                               "note 434093
47        CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
48    ENDIF.                                                   "note 434093
49
50 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
51
52 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
53    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
54         EXCEPTIONS
55           error_message = 4.
56 * As soon as we have started to put things into UPDATE TASK, we must
57 * ensure that errors definitely terminate the transaction.
58 * MESSAGE A is not sufficient because it can be catched from
59 * external callers which COMMIT WORK afterwards, resulting in
60 * incomplete updates. Read note 385830 for the full story.
61    IF NOT sy-subrc IS INITIAL.
>>>       MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
63                  sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
64 *     MESSAGE A263.
65    ENDIF.
66 * Optische Archivierung
67 * Spaete Erfassung mit Barcode
68 * Redesign of barcode handling -> note 780365
69   PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
70                                          xmkpf-mjahr
71                                          barcode.
72
73   MOVE-CORRESPONDING xmkpf TO emkpf.
74   CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
75     EXCEPTIONS
76       error_message = 4.
77    MOVE-CORRESPONDING xmkpf TO emkpf.
ource Code Extract
ine SourceCde
32 *    BKPF as well. There is no other way to forward XBLNR to FI as not
33 *    every document is posted by MB_CREATE -> a new function module in
34 *    MBWL for transferring the information, called by FI, meant to load
35 *    the complete function group for all MBxx postings when this isn't
36 *    required (Performance). Would be the better way to transport the
37 *    information after switching off MBxx in later release.
38 *    corresponding IMPORT ... FROM MEMORY ... can be found in
39 *    AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
40      l_mem_id = 'MKPF-XBLNR'.                                   " 641365
41      EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
42    ELSE.                                                        "1245374
43      l_mem_id = 'MKPF-XBLNR'.                                   "1245374
44      FREE MEMORY ID l_mem_id.                                   "1245374
45    ENDIF.

Couple of notes are mentioned (385830, 780365 etc) and check whether these notes are applied. If so, check with the ABAPer and go through the source code corrections explained in the respective notes.
You may also go through the following notes
1) Note 386656 - FBV4: RW103 'System error in the FI/CO interface'
2) Note 388316 - RW103 "System error in the FI/CO interface"
3) Note 543463 - Inconsistent Posting in budgetary ledger and/or RW102/RW103
thanks
G. Lakshmipathi

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 when posting an goods issue of movement type 501: order not contain

I tried to post an goods issue of movment type 501 to a stock transport order. But I get the error as below.
Document 4500000130 does not contain any selectable items
Message no. M7 064
Diagnosis
The document or item entered cannot be adopted.
Possible reasons for this are:
The document items have already been processed
(Suggest zero lines indicator set?).
the document items have been deleted or are blocked.
the document items have been created for a different plant.
(for reservations only) movements are not yet allowed for the reservation items.
(for reservations only) the document items are retrograde components of the order. These are posted using the order confirmations.
The document is an R/2 document.
Procedure
Make sure your entries are correct.
If the system has already processed the total quantity, you can set the Suggest zero lines indicator. The system will suggest the quantity zero for the items that have already been processed.
If you have entered a particular item, cancel the item. If you do not enter an item, the system searches all of the open items in the document.
If the document is a purchase order, production order or a reservation, you can enter search criteria in the dialog box.
You access the dialog box by choosing the menu option Enter with reference on the initial screen.
If the document is an R/2 document, you have to cancel it manually by entering the reversal movement type.
How can I proceed to post?
Thanks,
Eda

Hi
Go to T.code MB1A, enter the required movement type, Plant and storage location and then click,
The push button of Reservation on the tool bar for refereing the reservation or
The push button of order on the tool bar for refereing the Production order.
Cheers
Kris

Amount not turning up for material movement type : 601 from 2lis_03_bf

Hi all,
i have loaded the inventory cube from 2lis_03_bx the quantity is turning up for movement type 601 but the amount is not getting reflected it is always blank.
   If   ( SOURCE_FIELDS-BWVORG EQ '000'         "Other Issues
   OR    SOURCE_FIELDS-BWVORG EQ '101'        "Returns / Vendor
   OR   SOURCE_FIELDS-BWVORG EQ '104'         "Material Transfer
   OR SOURCE_FIELDS-BWVORG EQ '105'          "Stock Adjustment InvD
   OR   SOURCE_FIELDS-BWVORG EQ '106'         "Stock Ajdustment Other
   OR SOURCE_FIELDS-BWVORG EQ '110' )
   "Issues from stock transfer
   AND SOURCE_FIELDS-BWAPPLNM EQ 'MM'
only movements which are relevant for stock control
   AND SOURCE_FIELDS-BWBREL EQ '1'
   AND SOURCE_FIELDS-BWGEO <> 0
SEE OSS NOTE 630254
   AND ( SOURCE_FIELDS-BSTTYP IS INITIAL OR
               ( SOURCE_FIELDS-BSTTYP CA 'EQ' AND
                  SOURCE_FIELDS-KZBWS CA 'AM' ) ).
*IF THE RETURNCODE IS NOTE EQUAL ZERO, THE RESULT WILL NOT BE UPDATED
     RESULT = SOURCE_FIELDS-BWGEO.
and i can see for other movement type like 641 the amount is turning up.
Can anyone advise me on this
thanks

does the material movement type : 601 will be updated from this data source : 2lis_03_bx nor it is from 2lis_03_um??
Can anyone advise me on this!!
thanks

Transaction Key for Movement Type 561

Hello,
For movement type 561, I know one of the Transaction Key is BSX. I would like to ask what is the other Transaction Key as I would like to set the GL Account Determination. Thanks.
Thanks.

Hi
Transaction keys required for 561 movemnt type are
BSX - For the inventory posting
GBB - BSA - For initial entry of stock balances
For performing the 561 movment G/L account needs to be assigned to both these transaction keys.
Thanks & Regards
Kishore

The movement type 261 is greyed out in MIGO

HI Experts,
We have a scenario where we want to use the copy of movement type 261 to post goods issue against a process order. In MIGO even if I change it in the initial screen and execute, system takes only 261. System is not allowing to change it in the tab "Where". The field for mvt type in this tab is greyed out.
But we have created a movement type to post the goods receipt which is copy of 101. This is working fine. System takes this movement type when we enter it in the initial screen and copies to the tab where.
How to solve this issue?
Request your expert advice.
Regards
Prathib

Hi Ajit,
Thanks for the reply. Here the issue is we wanted to use the customized movement type only for a particular type of order. For all the other order we should use 261 only.
I dont think this can be done through standard SAP. Is there any user exit or BADI for the same?
Please let me know.
Thanks & Regards
Prathib

Material Movement Types in Inventory

Hi All,
I am a BI person and have extremly limitted knowledge in the area of MM. I am working on an inventory valuation project and I need some larification on movement types. I have receipts, issues and adjustments. I have the following questions.
1. On receipts I have both GR (101) and GR reversal for PO (102) is there. SUppose 101 is 10 and 102 is 2, my receipts result is 8. Am I correct? There are many different sets of receipts and reversals exist in my installation.
2. The same is true in the case os issues. GI for cost center (201) and RE for cost centers (202). Total issue here is the difference between 201 and 202. Is this assumption correct?
3. In the case of adjustments, is it adjustments to receipts and issues. In otherwords certain adjustments will increase receipts and certain will decrease issues.eg 701 GR physcial inventory -warehouse and 702 GI physical inventory warehouse. 701 quantity need to be added with receipts and 702 quantity to be added with issues. Is this assumption correct?
4. When initializing stocks (Opening balance) everything is like stock in hand. Can I treat them as GR into inventory?
5. What is valuated and Non-valuated stocks?
understanding these will help me matching ECC and BI reports.
Thanks,
Alex.

Hi Alex,
As per my knowledge
1. GR(102) is reversal to GR(101) i.e. how much u receive in 101 that all is to reverse via 102. .i.e. if GR is of 10 Qty then by 102 whole qty will be reversed.
Change Oty is done only with 122 - return to the vender.
2. But in case of Issue it is not true as above mentioned. if u have to change Qty while giving back with 202.
3. Yes, while Initial stock, it is GR, MB1C or MIGO with 561. maintain the price in MR21.
4. Valuated Stock is used in material Requirement planning but other is not.
Regards,
Pardeep Malik

GOODS RETURN MOVEMENT TYPE 202

DEAR GURUS
USER HAVE ISSUED MATERIAL QTY 1    MVT 201,
NEXT TIME SAME MTRIAL ISSUED QTY 1   MVT 261
BUT SAME MATERIAL HAS BEEN RETURNED QTY 3    MVT 202.
HOW IS IT POSIBLE WHERE CAN I CHECK THIS
REGARDS

Hello ,
Mvt type 202 is technically the movement type for reversal of 201 mvt type ( issue to cost center ).
This mvt type is picked up automatically in case of cancellation of 201 mat docs .
But when manually a posting is done using this movement type , this is deemed as good as initial stock entry .
Same will be the case when u post a 262 mvt type directly .
It is highly recommended to be extremely disciplined in directly posting such document . The system will never check it if it is a cancellation .
Also in case issued are to be reversed , always cancel the 201 document .
Hope this clarifies .
Regards
Anis

Refurbishment initial movement type

Similar Messages

Maybe you are looking for