Goods movement quantity

can nyone plss tell me where will i find goods movement quantity n wat is the field name?

Hi,
You will find it in the Table MSEG
check and Take Menge or ERFMG field.
Regards,
Anji

Similar Messages

  • Hide the quantity field at goods movements in cofirmation.

    HI,
    My client is using CO11N for confirmation. and doing auto goods reciept and auto goods issue.
    Whn I am clicking on Goods movement in CO11N system is showing me which material is going in goods reciept and which is in Goods issue.
       Now my requirement is I want to hide the quantity field of the material in goods movement because some time user is changing the quantity of goods issue.
       Wat can I do for the same?
    Please sugest
    Thanks & Regards,
    Nilesh Ithape.

    Dear Nilesh,
    Try to achieve the same using the authorization control.
    You can take the help of the BASIS consultant and try to find the authorization object and the value
    which's allowing to change the quantity.
    Check whether this is the particular object C_AFKO_AWA is allowing the same(I'm not sure).
    After finding out the Authorization object remove the tick mark for the value which's for change or delete.
    You can find it using SU24 T code or using SUIM and other related T codes.
    If it cant be done even after authorization control ,revert back to the forum.
    Regards
    Mangalraj.S

  • Default quantity of confirmation(co11) should allowed in goods movements mb

    thank you for giving valuable reply.
    i have another question
    after confirming 10 pcs. partially of the order quantity say 50 pcs.(through co11)
    i have to cary out the goods movement mb31 (101) for 10 pcs.
    now, i put qtys. more than 10 pcs. & up to the 50 pcs the system will allowed
    for the goods movements.
    but i want restriction that the 10 pcs. confirmed qtys. only allowed for goods movement.
    please tell me the solution for the same.i have not defined auto G.R. in control key & in production scheduling profile.please give alternative for these.
    thanks
    regards
    mangesh

    Gowri,
    Code for your copy pasting in the source code of ZXMBCU02.
    Remember to activate the program. In SMOD enter the enhancement, press F8 and then click on activate button.
    *&  Include           ZXMBCU02
    data it_afvv like afvv occurs 0 with header line.
    tables: afvv, afko, afpo.
    data tot_gr like mseg-menge.
    If i_mseg-bwart = '101' and i_mseg-aufnr is not initial.
      select single * from afko where aufnr = i_mseg-aufnr.
      select * from afvv into table it_afvv where aufpl = afko-aufnr.
      sort it_afvv by aplzl descending.
      read table it_afvv index 1.
      select single lmnga from afvv into afvv-lmnga where aufpl = afko-aufnr
    and aplzl = it_afvv-aplzl.
      select single * from afpo where aufnr = i_mseg-aufnr.
      tot_gr = afpo-wemng + i_mseg-menge.
      if tot_gr > afvv-lmnga.
        MESSAGE 'GR qty greater than Confqty of the last opern' TYPE 'E'.
      Endif.
    endif.

  • Goods movement with serial numbers

    Hi,
    1. Is there any report or table where I can see goods movement of material with their serial numbers?
    2. Also in MMBE i can see 'On order stock'. I know this is PO open PO quantity.
    Now this open PO qty will not be there against any storage location. I got some stock on this status in some storage location.
    How I can move to 'unrestricted stock' status?
    Please advice.

    Hi
    Check these tables,
    SER00 General Header Table for Serial Number Management
    SER01 Document Header for Serial Numbers for Delivery
    SER02 Document Header for Serial Nos for Maint.Contract (SD Order)
    SER03 Document Header for Serial Numbers for Goods Movements
    SER04 Document Header for Serial Numbers for Inspection Lot
    SER05 Document Header for Serial Numbers for PP Order
    SER06 Document Header for Serial Numbers for Handling Unit-Content
    SER07 Document Header for Serial Numbers in Physical Inventory
    And in order to move On Order stock to Unrestricted you need to close those POs by doing GR.
    Hope it helps
    Rgds
    ramesh

  • Goods movements of material with serial numbers

    Hi,
    1. Is there any report or table where I can see goods movement of material with their serial numbers?
    2. Also in MMBE i can see 'On order stock'. I know this is PO open PO quantity.
    Now this open PO qty will not be there against any storage location. I got some stock on this status in some storage location.
    How I can move to 'unrestricted stock' status?
    Please advice.

    Hi,
    Is Serial number is the one obtained thro stadard batch management or is it a Zfield.
    On Order stock cannot be converted to unrestircted stock unless a GR is made.
    With regards,
    Jeeva

  • BAPI_GOODSMVT_CREATE: Transport Order Goods Movements

    Hi
    I have a transport order  (move material from plant A to plant B) and a outbound delivery already created on SAP.
    From xMII using FMu2019s o BAPIu2019s I need to update the picking and also confirm the outbound delivery in order to register the goods movement, the good movement that I need to create itu2019s 641 type.
    We are using quite well the BAPI_GOODSMVT_CREATE to move materials for Purchase Orders and Process Orders, but with movement type 641 I always get the following error message u201CGoods movement not possible with mvmt type 641u201D; so I began to search on the SAP SDN about this.
    Is there another BAPI for create a 641 movement?
    What are the BAPI or FM that I need to use?
    Any help?
    Best Regards and Thanks in advance

    Finally I've managed to create movement type 641...
    Let explain how:
    First its to update the outbound delivery using the BAPI_OUTB_DELIVERY_CHANGE where you can assign a storage location for a position, the delivered quantity, net weight, gross weigth, volume and also conversion factor between units of measure.
    The we need to do the picking and the post good issue (PGI) by WS_DELIVERY_UPDATE where you define the picking qty, date and time for the post good issue, etc. This is the one that creates a movement 641.
    Here you can see an example of the two BAPI/FM request that you need:
    <?xml version="1.0" encoding="UTF-8"?>
    <BAPI_OUTB_DELIVERY_CHANGE>
         <INPUT>
              <DELIVERY></DELIVERY>
              <HEADER_CONTROL>
                   <DELIV_NUMB></DELIV_NUMB>
                   <GROSS_WT_FLG/>
                   <NET_WT_FLG/>
                   <VOLUME_FLG/>
                   <DELIV_DATE_FLG/>
                   <DOCK_FLG/>
                   <DLV_DEL/>
                   <INCO1_FLG/>
                   <INCO2_FLG/>
                   <ROUTE_FLG/>
                   <SHIP_COND_FLG/>
                   <DLV_PRIO_FLG/>
                   <UNLOAD_PT_FLG/>
                   <PICK_DATE_FLG/>
                   <TRSP_DATE_FLG/>
                   <LOAD_DATE_FLG/>
                   <GDSI_DATE_FLG/>
                   <SIMULATE/>
                   <NO_LOCK/>
                   <SPLIT_DONE_FLG/>
                   <DLV_BLOCK_FLG/>
                   <DLV_CHANGE_OFF/>
              </HEADER_CONTROL>
              <HEADER_CONTROL_SPL>
                   <SENDER_METHOD/>
                   <DELIV_NUMB></DELIV_NUMB>
                   <GEOROUTE_FLG/>
                   <BOP_GUID/>
                   <INITIATOR_PROCESS/>
              </HEADER_CONTROL_SPL>
              <HEADER_DATA>
                   <DELIV_NUMB>2030000016</DELIV_NUMB>
                   <GROSS_WT/>
                   <NET_WEIGHT/>
                   <UNIT_OF_WT/>
                   <UNIT_OF_WT_ISO/>
                   <VOLUME/>
                   <VOLUMEUNIT/>
                   <VOLUMEUNIT_ISO/>
                   <DOOR/>
                   <INCOTERMS1/>
                   <INCOTERMS2/>
                   <ROUTE/>
                   <SHIP_COND/>
                   <DLV_PRIO/>
                   <UNLOAD_PT/>
                   <DLV_BLOCK/>
              </HEADER_DATA>
              <HEADER_DATA_SPL>
                   <DELIV_NUMB></DELIV_NUMB>
                   <GEOROUTE/>
              </HEADER_DATA_SPL>
              <SENDER_SYSTEM/>
              <TECHN_CONTROL>
                   <DEBUG_FLG/>
                   <UPD_IND/>
                   <RECV_WHS_NO/>
                   <RECV_SYS/>
                   <DLV_TYPE/>
              </TECHN_CONTROL>
         </INPUT>
         <TABLES>
              <COLLECTIVE_CHANGE_ITEMS>
                   <item>
                        <DELIV_NUMB></DELIV_NUMB>
                        <DELIV_ITEM/>
                        <DLV_QTY_FROM/>
                        <BASE_UOM/>
                        <BASE_UOM_ISO/>
                   </item>
              </COLLECTIVE_CHANGE_ITEMS>
              <EXTENSION1>
                   <item>
                        <FIELD1/>
                        <FIELD2/>
                        <FIELD3/>
                        <FIELD4/>
                   </item>
              </EXTENSION1>
              <EXTENSION2>
                   <item>
                        <PARAM/>
                        <ROW/>
                        <FIELD/>
                        <VALUE/>
                        <TYPE/>
                        <LENGTH/>
                   </item>
              </EXTENSION2>
              <HEADER_DEADLINES>
                   <item>
                        <DELIV_NUMB></DELIV_NUMB>
                        <TIMETYPE/>
                        <TIMESTAMP_UTC/>
                        <TIMEZONE/>
                   </item>
              </HEADER_DEADLINES>
              <HEADER_PARTNER>
                   <item>
                        <UPD_MODE_PARTN/>
                        <DELIV_NUMB></DELIV_NUMB>
                        <ITM_NUMBER/>
                        <PARTN_ROLE/>
                        <PARTNER_NO/>
                        <ADDRESS_NO/>
                        <DESC_PARTN/>
                        <MANUAL_ADDR/>
                        <SCA_CODE/>
                   </item>
              </HEADER_PARTNER>
              <HEADER_PARTNER_ADDR>
                   <item>
                        <UPD_MODE_ADR/>
                        <ADDR_NO/>
                        <FORMOFADDR/>
                        <NAME/>
                        <NAME_2/>
                        <NAME_3/>
                        <NAME_4/>
                        <C_O_NAME/>
                        <CITY/>
                        <DISTRICT/>
                        <CITY_NO/>
                        <POSTL_COD1/>
                        <POSTL_COD2/>
                        <POSTL_COD3/>
                        <PO_BOX/>
                        <PO_BOX_CIT/>
                        <DELIV_DIS/>
                        <STREET/>
                        <STREET_NO/>
                        <STR_ABBR/>
                        <HOUSE_NO/>
                        <STR_SUPPL1/>
                        <STR_SUPPL2/>
                        <LOCATION/>
                        <BUILDING/>
                        <FLOOR/>
                        <ROOM_NO/>
                        <COUNTRY/>
                        <LANGU/>
                        <REGION/>
                        <SORT1/>
                        <SORT2/>
                        <TIME_ZONE/>
                        <TAXJURCODE/>
                        <ADR_NOTES/>
                        <COMM_TYPE/>
                        <TEL1_NUMBR/>
                        <TEL1_EXT/>
                        <FAX_NUMBER/>
                        <FAX_EXTENS/>
                        <STREET_LNG/>
                        <DISTRCT_NO/>
                        <CHCKSTATUS/>
                        <PBOXCIT_NO/>
                        <TRANSPZONE/>
                        <HOUSE_NO2/>
                        <E_MAIL/>
                        <STR_SUPPL3/>
                        <TITLE/>
                        <COUNTRYISO/>
                        <LANGU_ISO/>
                        <BUILD_LONG/>
                        <REGIOGROUP/>
                        <HOME_CITY/>
                        <HOMECITYNO/>
                        <PCODE1_EXT/>
                        <PCODE2_EXT/>
                        <PCODE3_EXT/>
                        <PO_W_O_NO/>
                        <PO_BOX_REG/>
                        <POBOX_CTRY/>
                        <PO_CTRYISO/>
                        <HOMEPAGE/>
                        <DONT_USE_S/>
                        <DONT_USE_P/>
                   </item>
              </HEADER_PARTNER_ADDR>
              <ITEM_CONTROL>
                   <item>
                        <DELIV_NUMB>2030000016</DELIV_NUMB>
                        <DELIV_ITEM>0010</DELIV_ITEM>
                        <CHG_DELQTY>X</CHG_DELQTY>
                        <DEL_ITEM/>
                        <VOLUME_FLG>X</VOLUME_FLG>
                        <NET_WT_FLG>X</NET_WT_FLG>
                        <GROSS_WT_FLG>X</GROSS_WT_FLG>
                   </item>
              </ITEM_CONTROL>
              <ITEM_DATA>
                   <item>
                        <DELIV_NUMB>2030000016</DELIV_NUMB>
                        <DELIV_ITEM>0010</DELIV_ITEM>
                        <MATERIAL>000000000211000001</MATERIAL>
                        <BATCH/>
                        <HIERARITEM/>
                        <USEHIERITM/>
                        <DLV_QTY>2</DLV_QTY>
                        <DLV_QTY_IMUNIT>2</DLV_QTY_IMUNIT>
                        <FACT_UNIT_NOM>2</FACT_UNIT_NOM>
                        <FACT_UNIT_DENOM>2</FACT_UNIT_DENOM>
                        <CONV_FACT>1</CONV_FACT>
                        <GROSS_WT>2000</GROSS_WT>
                        <NET_WEIGHT>2000</NET_WEIGHT>
                        <UNIT_OF_WT>KG</UNIT_OF_WT>
                        <UNIT_OF_WT_ISO>KG</UNIT_OF_WT_ISO>
                        <VOLUMEUNIT>M3</VOLUMEUNIT>
                        <VOLUMEUNIT_ISO/>
                        <SALES_UNIT>TO</SALES_UNIT>
                        <SALES_UNIT_ISO>TO</SALES_UNIT_ISO>
                        <BASE_UOM>TO</BASE_UOM>
                        <BASE_UOM_ISO>TO</BASE_UOM_ISO>
                        <DEL_QTY_FLO></DEL_QTY_FLO>
                        <DLV_QTY_ST_FLO></DLV_QTY_ST_FLO>
                        <STOCK_TYPE/>
                        <VAL_TYPE/>
                        <MATERIAL_EXTERNAL></MATERIAL_EXTERNAL>
                        <MATERIAL_GUID></MATERIAL_GUID>
                        <MATERIAL_VERSION/>
                        <INSPLOT/>
                        <VOLUME>2000</VOLUME>
                   </item>
              </ITEM_DATA>
              <ITEM_DATA_SPL>
                   <item>
                        <DELIV_NUMB>2030000016</DELIV_NUMB>
                        <DELIV_ITEM>0010</DELIV_ITEM>
                        <STGE_LOC>CT2A</STGE_LOC>
                        <PICK_DENIAL/>
                   </item>
              </ITEM_DATA_SPL>
              <ITEM_SERIAL_NO>
                   <item>
                        <DELIV_NUMB></DELIV_NUMB>
                        <ITM_NUMBER/>
                        <SERIALNO/>
                   </item>
              </ITEM_SERIAL_NO>
              <RETURN>
                   <item>
                        <TYPE/>
                        <ID/>
                        <NUMBER/>
                        <MESSAGE/>
                        <LOG_NO/>
                        <LOG_MSG_NO/>
                        <MESSAGE_V1/>
                        <MESSAGE_V2/>
                        <MESSAGE_V3/>
                        <MESSAGE_V4/>
                        <PARAMETER/>
                        <ROW/>
                        <FIELD/>
                        <SYSTEM/>
                   </item>
              </RETURN>
              <SUPPLIER_CONS_DATA>
                   <item>
                        <DELIV_NUMB></DELIV_NUMB>
                        <ITM_NUMBER/>
                        <SPEC_STOCK/>
                        <SP_STCK_NO/>
                        <REF_QTY/>
                        <BASE_UOM/>
                        <BASE_UOM_ISO/>
                        <DLV_QTY/>
                        <SALES_UNIT/>
                        <SALES_UNIT_ISO/>
                   </item>
              </SUPPLIER_CONS_DATA>
              <TOKENREFERENCE>
                   <item>
                        <TR_EXT/>
                   </item>
              </TOKENREFERENCE>
         </TABLES>
    </BAPI_OUTB_DELIVERY_CHANGE>
    <?xml version="1.0" encoding="UTF-8"?>
    <WS_DELIVERY_UPDATE>
         <INPUT>
              <COMMIT>X</COMMIT>
              <DELIVERY>2030000016</DELIVERY>
              <IF_CONFIRM_CENTRAL> </IF_CONFIRM_CENTRAL>
              <IF_DATABASE_UPDATE>1</IF_DATABASE_UPDATE>
              <IF_ERROR_MESSAGES_SEND_0>X</IF_ERROR_MESSAGES_SEND_0>
              <IF_GET_DELIVERY_BUFFERED> </IF_GET_DELIVERY_BUFFERED>
              <IF_LATE_DELIVERY_UPD> </IF_LATE_DELIVERY_UPD>
              <IF_NO_BUFFER_REFRESH> </IF_NO_BUFFER_REFRESH>
              <IF_NO_GENERIC_SYSTEM_SERVICE> </IF_NO_GENERIC_SYSTEM_SERVICE>
              <IF_NO_INIT> </IF_NO_INIT>
              <IF_NO_MES_UPD_PACK> </IF_NO_MES_UPD_PACK>
              <IF_NO_READ> </IF_NO_READ>
              <IF_NO_REMOTE_CHG></IF_NO_REMOTE_CHG>
              <IF_WMPP> </IF_WMPP>
              <NICHT_SPERREN>X</NICHT_SPERREN>
              <NO_MESSAGES_UPDATE> </NO_MESSAGES_UPDATE>
              <SYNCHRON>X</SYNCHRON>
              <UPDATE_PICKING>X</UPDATE_PICKING>
              <VBKOK_WA>
                   <VBELN_VL>2030000016</VBELN_VL>
                   <VBTYP_VL/>
                   <VBELN/>
                   <LGNUM/>
                   <TANUM/>
                   <KODAT/>
                   <KOUHR/>
                   <BRGEW/>
                   <KZBRG></KZBRG>
                   <KZNTG></KZNTG>
                   <NTGEW></NTGEW>
                   <GEWEI/>
                   <VOLUM/>
                   <KZVOL></KZVOL>
                   <VOLEH/>
                   <KOMUE/>
                   <WABUC>X</WABUC>
                   <WADAT_IST/>
                   <KZWAD>X</KZWAD>
                   <WADAT>20080812</WADAT>
                   <WAUHR>115436</WAUHR>
                   <KZLFD></KZLFD>
                   <LFDAT></LFDAT>
                   <LFUHR></LFUHR>
                   <KZTOR></KZTOR>
                   <LGTOR/>
                   <KZLSP></KZLSP>
                   <LIFSK/>
                   <LIKP_DEL/>
                   <PACKING_REFRESH/>
                   <PACKING_FINAL/>
                   <PODAT/>
                   <POTIM/>
                   <KZPOD/>
                   <LIFEX/>
                   <BOLNR/>
                   <PRVBE/>
                   <XWMPP/>
                   <TRATY/>
                   <TRAID/>
                   <KZKODAT/>
                   <KZEBU/>
                   <INCO1/>
                   <INCO2/>
                   <ROUTE/>
                   <LPRIO/>
                   <VSBED/>
                   <LDDAT>20080812</LDDAT>
                   <LDUHR>115436</LDUHR>
                   <TDDAT/>
                   <TDUHR/>
                   <ABLAD/>
                   <KZINCO1/>
                   <KZINCO2/>
                   <KZROUTE/>
                   <KZLPRIO/>
                   <KZVSBED/>
                   <KZLDDAT>X</KZLDDAT>
                   <KZTDDAT/>
                   <KZABLAD/>
                   <KZLIFEX/>
                   <DECSPLI/>
                   <KZCHGOFF/>
                   <IMWRK/>
                   <KZREG/>
                   <KZLGBZO/>
                   <LGBZO/>
                   <SPE_ORIG_SYS/>
                   <SPE_CHNG_SYS/>
                   <SPE_TMPID/>
                   <SPE_LOEKZ/>
                   <SPE_NO_HU_CONS_CHECK/>
                   <SPE_LOGSYS/>
                   <SPE_RET_HU_UPDATE_REQUEST/>
                   <SPE_GEN_PROCESS/>
                   <SPE_WAUHR_IST/>
                   <SPE_WAZONE_IST/>
                   <SPE_LOC_SEQ/>
                   <SPE_ACC_APP_STS/>
                   <SPE_ACC_APP_STS_F/>
                   <SPE_SHP_INF_STS/>
                   <SPE_SHP_INF_STS_F/>
                   <SPE_RET_CANC/>
                   <SPE_RET_CANC_F/>
                   <SPE_QI_STATUS/>
                   <SPE_QI_STATUS_F/>
                   <SPE_GEOROUTE/>
                   <SPE_GEOROUTEIND/>
                   <SPE_CARRIER_IND/>
                   <SPE_GTS_REL/>
                   <SPE_GTS_RT_CDE/>
                   <GTS_CUSREF_NO/>
                   <BOP_GUID/>
                   <SPE_DIRECT_BILLING/>
                   <SPE_BILLING_WAIT/>
                   <SPE_PRINTER_PROF/>
                   <SPE_KZGEOROUTE/>
                   <SPE_KZGEOROUTEIND/>
                   <SPE_KZCARRIER_IND/>
                   <SPE_KZGTS_REL/>
                   <SPE_KZGTS_RT_CDE/>
                   <SPE_INITIATOR_PROCESS/>
                   <SPE_RESET_VLSTK/>
                   <SPE_KZTRAID/>
                   <SPE_KZTRATY/>
                   <SPE_INB_DLV/>
                   <SPE_DIST_PROC_CODE/>
                   <NO_TEXT_INIT/>
                   <NO_MESSAGE_INIT/>
                   <BLDAT/>
                   <KZBLD/>
                   <ANZPK/>
                   <KZAPK/>
                   <BORGR_KZWAD/>
                   <BORGR_KZABL/>
                   <MDIFF_BUCH/>
                   <MDIFF_STORNO/>
                   <KZTXT/>
                   <TXTOLD_DEL_ALL_LANG/>
                   <SPE_MDNUM_EWM/>
                   <SPE_OMDNUM_EWM/>
                   <SPE_CD_PLANT/>
                   <SPE_CD_PLANTF/>
                   <SPE_PRO_NUMBER/>
                   <SPE_KZ_PRO_NUMBER/>
                   <SPE_RED_IND/>
                   <SPE_AUTO_GR/>
                   <VORNU/>
                   <VORPA/>
                   <EXPVZ/>
              </VBKOK_WA>
         </INPUT>
         <TABLES>
              <ET_CREATED_HUS>
                   <item>
                        <MANDT/>
                        <VENUM/>
                        <EXIDV/>
                        <EXIDA/>
                        <VSTEL/>
                        <LSTEL/>
                        <BRGEW/>
                        <NTGEW/>
                        <MAGEW/>
                        <TARAG/>
                        <GEWEI/>
                        <BTVOL/>
                        <NTVOL/>
                        <MAVOL/>
                        <TAVOL/>
                        <VOLEH/>
                        <ANZGL/>
                        <ERNAM/>
                        <ERDAT/>
                        <ERUHR/>
                        <AENAM/>
                        <AEDAT/>
                        <AEZET/>
                        <SORTL/>
                        <VEGR1/>
                        <VEGR2/>
                        <VEGR3/>
                        <VEGR4/>
                        <VEGR5/>
                        <VHILM/>
                        <LAENG/>
                        <BREIT/>
                        <HOEHE/>
                        <MEABM/>
                        <ERLKZ/>
                        <GEWTO/>
                        <VOLTO/>
                        <MEINS/>
                        <VOLEH_MAX/>
                        <GEWEI_MAX/>
                        <VBELN_GEN/>
                        <POSNR_GEN/>
                        <INHALT/>
                        <VHART/>
                        <KAPPL/>
                        <KALSM/>
                        <KSCHL/>
                        <MAGRV/>
                        <WERKS/>
                        <PSTYV/>
                        <VKORG/>
                        <VTWEG/>
                        <LADLG/>
                        <LADEH/>
                        <FARZT/>
                        <FAREH/>
                        <ENTFE/>
                        <EHENT/>
                        <LGORT/>
                        <GEWFX/>
                        <VELTP/>
                        <EXIDV2/>
                        <LANDT/>
                        <LANDF/>
                        <NAMEF/>
                        <NAMBE/>
                        <VHILM_KU/>
                        <VPOBJ/>
                        <VPOBJKEY/>
                        <HANDLE/>
                        <WMSTA/>
                        <LGNUM/>
                        <SAPRL/>
                        <KZGVH/>
                        <ADGE_DG/>
                        <ADGE_DGPR/>
                        <UEVEL/>
                        <PACKVORSCHR/>
                        <PACKVORSCHR_ST/>
                        <LABELTYP/>
                        <ZUL_AUFL/>
                        <STATUS/>
                        <HU_LGORT/>
                        <HU_SYSTEM/>
                        <SPE_HDALL/>
                        <SPE_VLSTK/>
                        <SPE_DELDEC/>
                        <SPE_IDART_01/>
                        <SPE_IDENT_01/>
                        <SPE_IDART_02/>
                        <SPE_IDENT_02/>
                        <SPE_IDART_03/>
                        <SPE_IDENT_03/>
                        <SPE_IDART_04/>
                        <SPE_IDENT_04/>
                        <SPE_LOGPOS/>
                        <SPE_CHK_COUNTER/>
                        <EPC1/>
                        <EPC2/>
                        <PACKAGE_CAT/>
                        <TRANSP_INDEX/>
                        <CRIT_SAF_INDEX/>
                        <LYARD/>
                        <YLCCL/>
                        <YLOCT/>
                        <STATS/>
                        <PRRTY/>
                        <FWAGN/>
                        <SCACD/>
                        <OWNER/>
                        <TRNPD/>
                        <SEALN1/>
                        <SEALN2/>
                        <SEALN3/>
                        <SEALN4/>
                        <SEALN5/>
                        <BLIND/>
                        <RSNCD/>
                        <RFTYP/>
                        <REFER/>
                        <PTMST/>
                        <ATMST/>
                        <YDOOR/>
                        <YSTGA/>
                        <URGFL/>
                        <PRFLG/>
                        <SLFLG/>
                        <SIGNI/>
                        <LTEXT/>
                        <UPDKZ/>
                        <KZTRA/>
                        <VEBEZ/>
                        <SORTF/>
                        <AENDB/>
                        <AENDB_WV/>
                        <AENDB_QUAN/>
                        <AENDB_STATUS/>
                        <KZUNT/>
                        <KZOBE/>
                        <FRGEW/>
                        <GEWEI_FR/>
                        <FRVOL/>
                        <VOLEH_FR/>
                        <KZPGN/>
                        <WERFD/>
                        <SELKZ/>
                        <LE_LGPLA/>
                        <LE_LGTYP/>
                        <WM_VERW/>
                        <MTPOS/>
                        <DEST_LGNUM/>
                        <DEST_LGTYP/>
                        <DEST_LGPLA/>
                        <OBJNR/>
                        <KUNNR/>
                        <LIEFNR/>
                        <TARAVAR/>
                        <STSMA/>
                        <HISTU/>
                        <ACTIVITY/>
                        <OBJECT/>
                        <HU_STATUS_INIT/>
                        <LOGSYS/>
                        <HU_LOCKED/>
                        <LETYP_WM/>
                        <TOP_HU_DLVRY/>
                        <KZEBU/>
                        <VWPOS/>
                   </item>
              </ET_CREATED_HUS>
              <IT_BAPIADDR1>
                   <item>
                        <ADDR_NO/>
                        <FORMOFADDR/>
                        <NAME/>
                        <NAME_2/>
                        <NAME_3/>
                        <NAME_4/>
                        <C_O_NAME/>
                        <CITY/>
                        <DISTRICT/>
                        <CITY_NO/>
                        <POSTL_COD1/>
                        <POSTL_COD2/>
                        <POSTL_COD3/>
                        <PO_BOX/>
                        <PO_BOX_CIT/>
                        <DELIV_DIS/>
                        <STREET/>
                        <STREET_NO/>
                        <STR_ABBR/>
                        <HOUSE_NO/>
                        <STR_SUPPL1/>
                        <STR_SUPPL2/>
                        <LOCATION/>
                        <BUILDING/>
                        <FLOOR/>
                        <ROOM_NO/>
                        <COUNTRY/>
                        <LANGU/>
                        <REGION/>
                        <SORT1/>
                        <SORT2/>
                        <TIME_ZONE/>
                        <TAXJURCODE/>
                        <ADR_NOTES/>
                        <COMM_TYPE/>
                        <TEL1_NUMBR/>
                        <TEL1_EXT/>
                        <FAX_NUMBER/>
                        <FAX_EXTENS/>
                        <STREET_LNG/>
                        <DISTRCT_NO/>
                        <CHCKSTATUS/>
                        <PBOXCIT_NO/>
                        <TRANSPZONE/>
                        <HOUSE_NO2/>
                        <E_MAIL/>
    &nb

  • Goods Movement - BAPI_GOODSMVT_CREATE - input parameters

    Hi,
    I have to create a goods movement with movement type 343 and 344.
    While using the transaction MB1B (Tranfer Posting), I give the following parameters.
    Header
    1. Document Date              2. Posting Date
    Item
    1. Movement Type              2. Plant                  3. Storage Location
    4. Material                         5. Quantity
    But while using the BAPI for creating the goods movement, it creates material document. But I am neither able to view the document nor see any change in the good movement of the material. The quantity remains same in transaction MMBE.
    I feel that item details given as input to the BAPI needs changes. Can anyone suggest the fields to which each of the above item details needs to be given.
    Thanks.
    Regards,
    Senthil G.

    Hello Senthil,
    Check this sample code
    REPORT ZRICH_0001 .
    * Structures for BAPI
    DATA: GM_HEADER  TYPE BAPI2017_GM_HEAD_01.
    DATA: GM_CODE    TYPE BAPI2017_GM_CODE.
    DATA: GM_HEADRET TYPE BAPI2017_GM_HEAD_RET.
    DATA: GM_ITEM    TYPE TABLE OF
                     BAPI2017_GM_ITEM_CREATE WITH HEADER LINE.
    DATA: GM_RETURN  TYPE BAPIRET2 OCCURS 0 WITH HEADER LINE.
    DATA: GM_RETMTD  TYPE BAPI2017_GM_HEAD_RET-MAT_DOC.
    CLEAR: GM_RETURN, GM_RETMTD. REFRESH GM_RETURN.
    * Setup BAPI header data.
    GM_HEADER-PSTNG_DATE = SY-DATUM.
    GM_HEADER-DOC_DATE   = SY-DATUM.
    GM_CODE-GM_CODE      = '04'.                                " MB1A
    * Write 971 movement to table
    CLEAR GM_ITEM.
    MOVE '412'                 TO GM_ITEM-MOVE_TYPE     .
    MOVE 'Q'                 TO GM_ITEM-SPEC_STOCK.
    MOVE '3800533484'  TO GM_ITEM-MATERIAL.
    MOVE '1'     TO GM_ITEM-ENTRY_QNT.
    *MOVE 'PC'    TO GM_ITEM-ENTRY_UOM.
    MOVE '1060'  TO GM_ITEM-PLANT.
    MOVE '0007'  TO GM_ITEM-STGE_LOC.
    *MOVE '0901'   TO GM_ITEM-MOVE_REAS.
    MOVE 'P203601001' TO GM_ITEM-WBS_ELEM.
    MOVE 'P203601001' TO GM_ITEM-VAL_WBS_ELEM.
    APPEND GM_ITEM.
    * Call goods movement BAPI
    CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
         EXPORTING
              GOODSMVT_HEADER  = GM_HEADER
              GOODSMVT_CODE    = GM_CODE
         IMPORTING
              GOODSMVT_HEADRET = GM_HEADRET
              MATERIALDOCUMENT = GM_RETMTD
         TABLES
              GOODSMVT_ITEM    = GM_ITEM
              RETURN           = GM_RETURN.
    IF NOT GM_RETMTD IS INITIAL.
      COMMIT WORK AND WAIT.
      CALL FUNCTION 'DEQUEUE_ALL'.
    ELSE.
      COMMIT WORK AND WAIT.
      CALL FUNCTION 'DEQUEUE_ALL'.
    ENDIF.
    WRITE:/ GM_RETMTD.
    LOOP AT GM_RETURN.
      WRITE:/ GM_RETURN.
    ENDLOOP.
    " Also after iu call the BAPI use the FM BAPI_TRANSACTION_COMMIT
    If useful reward.
    Vasanth

  • Goods movement document based on stock determination

    All,
    I am trying to create goods movement document using BAPI_GOODSMVT_CREATE based on production order for movement type '261'. Before to that we have to use the function module BF_STOCK_DETERMINATION to pick the stock from appropriate storage location( for example: if order quantity is 3; then quantity 2 will be picked from
    Un-restricted stock and 1 qty will be picked from consignment stock). What happens is when it gets into MB_CREATE_GOODS_ISSUE_ITEM inside the BAPI, at the routine "MM07MMFF0_FUSSZEILE_WA_PRUEFEN" there is a routine called "FORM WERK_PRUEFEN(sapfm07m) when it gets into this routine the values in the internal table"T158"
    losses its visiblity. so i get an error "document type" missing, when the function module"FI_DOCUMENT_TYPE_CHECK"
    is called as part of the routine.
    But if i call the BAPI_GOODSMVT_CREATE without calling BF_STOCK_DETERMINATION material document is get created.
    If any one worked on this please help me i tried for more than week but i couldn't solve it. I really highly appreciate you help.
    With regards,
    Shiva.

    Called in two different program and it worked. In the first program i call "BF_STOCK_DETERMINATION" and export the values to memory and then i call the second porgram using "submit...and return"; import the values and called
    "BAPI_GOODSMVT_CREATE".  Material document is created.
    Regards,
    Shiva.

  • Field disable or non editable -- goods movements

    Hi team
    your assistace will be highly appreciated.
    I´m working with tx CO11N and after completion of  the requiere data we click on goods movements button and the next  screen  is : "Enter production order confirmation: goods movements" and this shows some fields and what I need is to disable some of them or make them non editable : quantity, storage location and movement type.
    Is it posible through Spro? if yes could you please tell the where.
    I don´t want to create a variant.
    thanks

    I guess Variant is the only option here, atleast thats what my PP consultant had done in my last project.
    There didnt seem to be any other alternative then.

  • Goods movement failures.

    Dear Freinds,
    All my movements are getting failed during the goods movement through CO11N transaction (movements w.r.t production order). These are appearing in transaction COGI. It is giving the error saying that "No stock posting possible for this material". But without any change ... I am able to save the movement. Error is giving the below detailed description
    *"No stock posting possible for this material
    Message no. M7097
    Diagnosis
    The material belongs to a material type whose stocks are not managed on a quantity basis.
    Procedure
    Enter a different material or terminate processing.
    If required, check the setting of the material type for the plant in the Customizing system of the material master data."*
    For your information, please note that we already maintained quantity updation check box in the material type configuration.
    Regards,
    Surya.

    Dear Friends,
    Thanks for your reply. Please note the below.
    1. I have maintained the material type settings initially itself.
    2. Today I observed that... this problem is coming only for the transaction CO11N. I am not getting this problem in CO15 transaction. But as per the clients requirement, I have to go for CO11N only.
    3. This is not the problem of batch management or batch management activation / stock availability...because without correcting any data... I am able to save the goods movement in COGI transaction.
    Regards,
    Surya.

  • Stock Transport Order u2013 Duplicate goods receipt quantity

    We implemented the scenario: the stock transport order process with SD. To post the goods issue , we have created a new goods movement  type (937) with reference to the movement type: 641, to differentiate these movements of other goods movements that are made in the company, because in this case, for issuing plant it is necessary to manually confirm these goods issues in WM (We need use storage bins in issuing plant). The outbound delivery, in issuing plant, is created through the transaction VL10B with reference to Stock transport Order, and goods issues is posted using transaction VL02N. In receiving plant, we use transaction MIGO to post goods receipt.
    Then, when we post the goods receipt for one replenishment delivery in Transaction MIGO, the system issues error message: M7022 telling us: u201Cthat the stock in transit has been exceeded by XXXu201D. The difference between the stock in transit and the Quantity in Unit of Entry is exactly equal to the quantity that was reported in the goods issue in Issuing Plant (outbound delivery). That is, Quantity in Unit of Entry is duplicated with respect to outbound delivery quantity. But if the goods receipt is posted with reference to the stock transport order, the Quantity in Unit of Entry is calculated correctly and corresponds with the quantity of outbound delivery of the issuing plant. This does not happen when using the standard goods movement type 641. As mentioned above, we have configured Warehouse Management for issuing plant.
    The only difference between the standard scenario and implemented one in the company is the goods movement type, which is a copy of movement type 641. So, my question is: Can not copy the goods Movement type 641 (Transfer to stock in transit)? Please, I appreciate your support to resolve this issues.
    Best regards,

    All goods movements are being posted in the same unit of measure (base unit of measure ), since the material has no alternative units of measure configured. And we think that has to do with the movement type, because when using the standard movement type (641), the whole process is flowing properly. However, when using the new movement type, the system behaves the way it was explained earlier.
    Through various tests, we identified that the quantity is duplicated  when the table T321 (Assignment MM Movement Type --> MM-WM Movement Type) and  the IMG view V_156S_WM (Reference Movement Types for Warehouse Management) are set, since it also was created a new movement type for WM. For this reason we think that the problem lies in the configuration of the new movement type.
    Anyway, thanks for your help.

  • Create a subsequent Goods Movement for a transfer posting

    Hi Team,
    I have a scenario where the users will create a Good Movement document for transfer posting. The Stock of Material "A" is transferred to stock of Material "B" using the movement types 561 etc. Now the quantity is reduced from unrestricted stock of "A" and posted to "Stock in Transfer/Transit" of "B". The requirement is to create another Goods Movement document immediately after the above transfer posting is completed and use movement type 101 to post the same quantity to unrestricted of "B".
    I tried searching for use exits and could not find a relevant one "After Save" for goods movement online transaction. I found the MB_GOODS_MOVEMENT_UPDATE Badi but don't know how to create another goods movement document while in the update task. I'm concerned that if I call a BAPI or BDC inside the update task, it might conflict with the current transaction (transfer posting). Looking for your guidance.

    Hi Deepali,
    You can use the userexit ' ZXMCBU02 '  to write your own code. This user exit gets triggered for almost all the goods movement transaction.
    There is also a very similar BADI which you can use which gets triggered for every goods movement transaction.
    I would like to know the BADI feel free to let me know. I think the above user exit should server your purpose.
    Hope this is useful for you.
    Cheers
    VJ

  • Problem with reverse goods movement

    Good Morning.
    I faced a problem with "schedule line" for an item in a sales order.
    I've an order quantity of about 14.000 pieces.
    I've created a partial outbound delivery for 8.000 pieces, but then for a problem, I made a "reverse goods movement" with VL09 for all 8000 pieces.
    When I came back into item's schedule line, I see in "Delivery quantity" column that is not considered the reverse goods momevent.
    I see that delivery quantity is still 8000.
    Can You give me some suggestion??
    Regards.

    There is no trasfer order in Sales Document Flow.
    Sales Order 10600587 / 10               12.12.07           14.000,000  NR      Completed          
    Delivery  8020600166 / 10                12.12.07           14.000,000  NR      Being rocessed    
    Picking request 20071212                   12.12.07           14.000,000  NR      Completed          
    GD goods issue:delvy 5500004772 / 1        12.12.07           14.000,000  NR      complete           
    RE goods deliv. rev. 5500004773 / 1        12.12.07           14.000,000  NR      complete           
    Delivery quantity is still 14000.

  • Enhancement in MIGO for Goods Movement

    Hi Gurus,
    I got a requirement to Create a 262 goods movement materials document with reference to a Sub-Contract GR for an account assigned Sub-Contract PO thru TCODE MIGO. The details are describe as follow:
    Once the 101/543 GR movement is carried out, a 262 movement type needs to be executed to reverse the consumption of the material against the service order and bring it back to the inventory (open stock). This movement needs to be triggered once MIGO ‘subcontractor goods receipt -101/543’ is committed (saved).
    When the 101/543 GR movement transaction MIGO is saved-
    1.     User exit needs to be invoked
    2.     Check if the GR is
    o     for an account assigned (EKPO- KNTTP Acct Assignment Cat =F) Sub-Contract PO (EKPO- PSTYP  Item Category L)
    o     AND the service order number (AUFNR) exists in ZXXXXXX (ZSUBCON_VALIDATION) table
    3.     Identify the line item material in the goods receipt document (First item /against movement type 101),
    4.     Identify the service order number (AUFNR) from ZSUBCON_VALIDATION table.
    5.     Call the goods issue (262) transaction via the BAPI using the material derived via step 3 and against the service order number derived via step 4. BAPI_GOODSMVT_CREATE  post goods movements

    Hi Matt,
    There are lots of Exits and BADI available in this transaction. See which suits you.
    Enhancement                                                                               
    MB_CF001                                Customer Function Exit in the Case of Updating a Mat. Doc.   
    MBCF0011                                Read from RESB and RKPF for print list in  MB26              
    MBCF0010                                Customer exit: Create reservation BAPI_RESERVATION_CREATE1   
    MBCF0009                                Filling the storage location field                           
    MBCF0007                                Customer function exit: Updating a reservation               
    MBCF0006                                Customer function for WBS element                            
    MBCF0005                                Material document item for goods receipt/issue slip          
    MBCF0002                                Customer function exit: Segment text in material doc. item                                                                               
    Business Add-in                                                                               
    MB_DOCUMENT_UPDATE                      BADI when updating material document: MSEG and MKPF          
    MB_DOC_BADI_INTERNAL                    BAdIs During Creation of a Material Document (SAP Internal)  
    MB_ME_CSGMT_BADI_SAP                    BAdI: Consignment Processing - Stock Transfer                
    MB_MIGO_BADI                            BAdI in MIGO for External Detail Subscreens                  
    MB_MIGO_ITEM_BADI                       BAdI in MIGO for Changing Item Data                          
    MB_PHYSINV_INTERNAL                     Connection: Core Inventory and Retail AddOn                  
    MB_QUAN_CHECK_BADI                      BAdI: Item Data at Time of Quantity Check                    
    MB_RESERVATION_BADI                     MB21/MB22: Check and Complete Dialog Data                    
    MB_RESERVATION_SCR                      Screen BAdI for Retrofit DFPS                                
    MB_RESERVATION_UPCHD                    BAdI for Creation and Changing of Manual Reservations        
    MB_RES_BAPI_CHANGE                      BAdI: Execution of Changes to Reservation Fields             
    MB_RES_BAPI_CREATE1                     BAdI: Adoption of Customer's Own Fields as Reserv. Fields    
    MB_RES_BAPI_DETAIL1                     BAdI: Display of Customer's Own Fields in Reservations       
    MB_STOR_LOC_BADI_GTS                    BADI to Check and Change Storage Location (GTS Fct. Only)    
    MB_DOCUMENT_BADI_SAP                    BADI for Creation and Changing of a Material Document        
    ARC_MM_EBAN_CHECK                       BAdI: Enhancement of Archivability Check (MM_EBAN)           
    ARC_MM_EBAN_PRECHECK                    BAdI: Enhancement of Archivability Check (MM_EBAN)           
    ARC_MM_EBAN_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EBAN)            
    ARC_MM_EINA_CHECK                       BAdI: Enhancement of Archivability Check (MM_EINA)           
    ARC_MM_EINA_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EINA)            
    ARC_MM_INVBEL_CHECK                     BAdI: Enhancement of Archivability Check (MM_INVBEL)         
    ARC_MM_INVBEL_WRITE                     BAdI: Enhancement of Scope of Archiving (MM_INVBEL)          
    ARC_MM_MATBEL_CHECK                     Prüfung ADD-ON-spezifischer Kriterien für MM_MATBEL          
    ARC_MM_MATBEL_WRITE                     Check Add-On-Specific Data for MM_MATBEL                     
    MB_CHECK_LINE_BADI                      BAdI: Check Line Before Copying to the Blocking Tables       
    MB_CIN_LMBMBU04                         posting of gr                                                
    MB_CIN_MM07MFB7                         BAdI for India Version exit in include MM07MFB7              
    MB_CIN_MM07MFB7_QTY                     Proposal of quantity from Excise invoice in GR               
    MB_DOCUMENT_BADI                        BAdIs During Creation of a Material Document                 
    Regards,
    Atish

  • Error message (M3024) during parallel goods movement

    For publication distribution, collected unreferenced deliveries and goods issues are done in SAP system for a customer group by a program which is triggered by a web service every day. Standart SAP functionalities are used in this program. At goods issue part of program, an error message is occuring "Valuation data for material &  is locked by the user &" with error code :M3024. The user who processes the program is locking himself. Also we have checked the other goods movement types in standart transactions (MB1B-MB11..)and same problem was occured. We have checked the notes that we applied before for to avoid material lock in paralel goods movement. There is nothing changed both in customizing and deveploment after upgrade. So we couldnt find the way to fix this problem. FIRST ANSWER FROM SAP***************************************** Can you kindly review the attached note 70865 with regards to this issue. WE APPLIED.-- We reviewed 70865 and this solution not applicable for our current system. According to note; We set material late lock exclusive time 15 seconds in OMJI. This solution solved material lock error at all plant level. After this solution, We get same batch error during goods movement(m3862), Then We applied note 157423, this note solved material batch lock error during goods movement, At last we have now m3024(Material valuation error lock) error during all goods movement. THEN********************************* As explained in the note 70865 , to ensure data integrity, it is necessary to block the material against updates by other users during good movements. This is achieved by blocking the material plant (lock object MARC) and the material valuation area (lock object MBEW) exclusively against othertransactions which update the material master. What you can do, as advised in the note, is to activate the late block via transaction OMJI. As a result of this change, several users will be able to carry out good movements to the same material and plant simultaneously. The problem is that you will experience a disadvantage of performance loss after this change. Please, notice that with this change in OMJI, several users will be ableto carry out GOODS MOVEMENTS to the same material and plant simultaneously. This change will not allow the simultaneous input of a goods movement and an invoice for the same material (in this case, the material will be locked as soon as the purchase order item is adopted in the invoice and the error message M3024 will occur). When the error message M3024 occurs, you could check with transaction SM12, there you could find some tables like MBEW are locked by user. The table is locked to prevent valuation, quantity etc. to be updated. System does not check if it is standard price or MAP, as soon as you work with one material it will be locked (its valuation data has to be locked, because otherwise there is no guarantee of the consistency of the stock values. Without this lock mechanism the possibility of serious data inconsistencies could arise). your customizing under: SPRO > IMG > Material Management > Set up Material block for goods movements Here you could choose setting 2(at positing) to have only a short locking period at posting. Please review information in attached notes. 521945 FAQ: Material block 322989 Late block: Number of blocking attempts AT LAST ** PROBLEM STILL GOING ON WHAT SHOULD WE DO TO SOLVE THIS ERROR.

    HI Fatih,
    Refer to SAP Note 1744780 - Error message M3024 during Invoice Verification process .
    In the standard system it is not possible the simultaneous entry of a GOODS MOVEMENTS and an INVOICE for the same material and the same plant.
    When you enter the invoice for the purchase order item, the valuation data for the material is updated, therefore this valuation data (table MBEW) needs to be blocked so that it is not changed at the same time by any other transaction (which might cause inconsistencies).
    Resolution
    This system behavior can not be avoided by any customizing setting or any user exit.
    This is correct system behavior to protect the other transactions update the material master.
    As advised in the note 70865 :
    It is possible to activate the late block via transaction OMJI. As a result of this change, several users will be able to carry out good movements to the same material and plant simultaneously, however there is a risk to cause the data inconsistency and performance problems.

Maybe you are looking for

  • Oracle map for Singapore

    Hi. Does anyone know how can i get the oracle map for Singapore? Thanks

  • Why won't my MacBook Pro go to sleep?

    Since my last software update my MacBook Pro will not go to sleep.  When I close the MacBook or if I initiate the sleep mode through the menu I just tries and then wakes back up.  If I clos the MacBook it just keep starting and stopping over and over

  • Improving VLC performance

    Hi! Im playing some mkv movie with vlc This movie is 24 Gb (1080p) and is being played through an integrated 512 Mb nVidia video card, connected via HDMI to a 32'' TV...... This did not happen before, and the memory does not seem to be the problem he

  • Interesting Support Respo

    Some of you may know that I am having a bit of an issue with getting my Micro to sync with Outlook 2003. It won't sync anything at all I started a CL-Technical Support Request in mid February and have had several rather unsatisfactory responses from

  • Total amount of memory?

    I know that the internal ram slot may be upgraded using a 1 gig stick, but i recently found the ram for the user slot, cannot remember the name of it, comes in 1 gig also. does that mean that i can use a total of 2 gigs?