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

Similar Messages

Stock transport order with movement type 643 - post to COPA

Hello SAP gurus,
We use movement type 643 to post good issues for stock transport order (intercompany process). The delivery type is NLCC. We recently implemented account-based COPA. At the time of post goods issue, cost of goods sold should be posted to COPA, but it didn't. Could someone help me figuring out how to push PGI to COPA for stock transport order? Thanks in advance.
Regards,
Cassandra Wong

The reason that PA segment is not populated in the good issue for STO is because the cost element of the COGS account was set to "01" instead of "12". I changed the cost element category and the PA segment is populated correctly.

COGI error in relevance in production order goods movement

Hello,
Yesterday I have a COGI error with regards in reservation. "RE Quantity moved exceeded by 7,912 LB: 1000710 0111 0001 201200". But today someone done something on the production order, and the error yesterday in COGI are fixed. Am confused what happen or what they did to fixed this since yesterday the error still there but now it is gone.
when checking the Documented Goods Movement for material 1000710 in the production order here the details,
Goods MVt   Mat. Doc Mvt type Batch      Qty   Reservation
1                       4908430     261     201199    6000 1112345
1                       4908426     261     201198   14000 1112345
1                       4908437     262     201200   14000 1112345
2                       4908430     261     201200   14000
This is what it shows? could some one explain me with this data what was the reseason yesterday i did not fixed the COGI error while now it was fixed? and why in RESERVATION 1112345 it only shows qty 6000 not 14000 for this order?
Hope for your kind and urgent reply to this issue
Thanks
JJ
Edited by: John Jay Palisoc on Jul 24, 2008 5:02 AM

Hi JJ,
well, as far as I can see, there is an unplanned 261 (without reservation no.). This one (doc. 4908430) has wihtdrawn additional 14000 for batch 201200. Therefore, the later 262 posting (doc. 4908437) with 14000 for that batch could be put into store without error.
That's all
Regarding the reservation: It shows qty 6000 because as first step 14000 were withdrawn, then additional 6000 and then 14000 were put back. So 6000 remain.
Regards, Andreas
Edited by: Andreas Seibel on Jul 24, 2008 3:37 PM
Edited by: Andreas Seibel on Jul 24, 2008 3:40 PM
Edited by: Andreas Seibel on Jul 24, 2008 3:45 PM

Process Order - Goods Movements

Hi All,
I am working with the process order (COR2/COR3). From the general data tab of the process order I am navigating to Documented Goods movements via the path Goto --> Lists --> Documented Goods movements.
I need to generate a report of these docs. I am just checking if there is any FM available for this. I did the search and could not find any. I am aware that these are available in the table MSEG which we can parse by the material no and the process order no. Is this the right way to get a list of these docs or do we have a better approach or any FM which I am missing.
Please drop in your inputs.
Thanks.

This info is available in the table AUFM - Goods movements for order .

Production order goods movement issue

Hi,
i am interested in issuing the materials to a production order at the creation stage.please specify any settings can be made for this. I want it to happen in specific plant only and not at global level.
please suggest
regards
madan

Hi,
Normally system will not Allow any Goods Movement when the Order has CRTD status (Creation stage).
However u can overcome this by doing allowed Goods MVt for status at CRTD at BS22.
It will afftect all the Plants & order types globally ,
As i know your requirement is not possible .
Pradeep

Restricting Process Order Goods Movements within order basic dates

Hi Experts,
How can we restrict the goods movements against a process order only within the basic start and basic finish dates of the order? We create one order per month, but users can post goods movements to the current order in the previous period (MIGO GI / GR), as movements in the prior period is allowed as well. Appreciate your inputs.
Regards,
Ravi

Hi,
Thanks. Yes, we do 'TECO' the past orders and we also have user status that prevents any goods movements on such 'TECO'ed orders. But, my question is how to prevent movements on Current Order, posted with date in previous period.
Thanks,
Ravi

Process order goods movement for process order

Hi PP gurus,
In my client's company in MIGO with movement type 261 user isuing material and then doing confirmation with COR6. In migo system should not allow less quantity than mentioned in BOM. Is there any standard setting for it.
Jayesh

With the help User Exit you can control the said requirement.
Best Regards,
Raghavendra K Nayak

Stock transport order /stock in transit

Hello
For a stock Transport order scenario { Recieving Plant , Delivering plant } , the documented procedure is:-
1) stock transport order>Goods issue by delivering plant--
>stock in transit(valuated) -- >Unrestricted/inquality/blocked/consumption
just sticking to the above method, how many Material documents & accounting documents would be generated ?
Thanks

Hi,
It depends on your setting, whether you go for 2-step Stock Transport or 1-step.
If It is 1-step then 1 material document and 1 accounting document.
This material document will be of movement type 647 and stock will not come in transit, stock will directly get moved from Supplying Plant to Receiving Plant.
And if it is 2-step then 2 material documents and 1 accounting document.
1 material document for GI from Supplying Plant to Stock in Transit (Movement Type - 641), and another from stock in transit to receiving plant (Movement Type - 101).
And it will update PO History in both the cases.
You can config. this in SPRO > MM > Purchasing > Purchase Order > Setup Stock Transport order > Assign Document Type, One-Step Procedure, Underdelivery Tolerance > here activate "One-step" indicator if you want 1-step otherwise keep blank for 2-step.

Goods movement (movement type 601), Assign GL account

When you craete an outbound delivery (picking, packing & goods issue), it creates an Financial document (the goods issue), the goods issue have a plant and sales office & profit centre. When the financial document is created, it post to a specific GL Account, I want to change the GL Account, but don't know which field (plant, sales office, profit centre) determines the GL account, and where this setting is made, so that I can change it.
The movement type that involve is 601. This means for every goods issue we generate, there is a accounting document, and this account document is posting to a GL account, and I want to change this specific GL account. It is not in VKOA, OKGB or GGB1.
Thank you for your assistance

601 is created for goods issues against sales order. Look up the material document in MIGO and look for the FI document entries taking place. Then go in OBYC, and look up those account keys and you will find the G/Ls assigned against those accounts keys.
Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.
Here movement 601 takes place. This movement is configured in MM.
When goods issues are posted for sales:-
Movement type used for posting u2013 601
Accounting entry posted:-
Cost of goods sold -
Debit
Inventory of Finished goods -
Credit
For cost of goods sold transaction key----
GBB
is updated with general modification key----
VAX
Edited by: Afshad Irani on Apr 29, 2010 5:09 PM

Goods movement document not updating

Hi Gurus,
I have created the order with component and external services did the goods issues and service acceptance but while checking in Menu bar of order>Extras>Document for order---->Goods movements no movement document is updared.Pls guide me why the movement document is not updating,I am sure about the goods issue and service acceptance because Actual cost is coming..
Thanks,
Kumar

Hi,
For better chances of response, better to post this in MM forum of R/3.
Thanks - Pawan

Function or BAPI for goods movements

Hi all,
Somebody know which function or bapi can i use to apply a movement 601 GD goods issue:delvy? Please.
Thanks in advance
regards.
MArisol

Hi,
the bapi to create good movement is BAPI_GOODSMVT_CREATE.
to cnacel goods movement
BAPI_GOODSMVT_CANCEL
to get details of goods movements
BAPI_GOODSMVT_GETDETAIL
to get items in goods movement
BAPI_GOODSMVT_GETITEMS
reward points if helpful.

Material determination during goods movement

Hi Guys,
I am using the BAPI 'BAPI_GOODSMVT_CREATE' to create goods movement. And I want to check the material availability and execute the material determination based on atp check results also. Does this BAPI implicitly handles material determination based on ATP? OR should I write the logic to the material determination explicitly before calling this BAPI?
Regards,
Rahul

As Jurgen has mentioned, material substitution is a part of SD and has to achieved prior to the goods movement BAPI.
Have a look at FMs for the material substitution logic:
RV_MAT_SUB_SAVE
RV_KONDITION_SICHERN
RV_KONDITION_SICHERN_V13A
is there any BAPI or Function Module for Materi... | SCN

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.

Automatic Post Goods Issue Of Stock Transport Order

Here is the scenario:
We are using stock transport order to logically move inventory from one company to another company inside the same physical location. The material# is the same but the plant# is different.
Process is as follows:
Associate enters the purchase order
If inventory exists - delivery is created automatically
The delivery is also auto picked
Currently, we have the inventory to PGI in a batch job several times a day.
However, the user would like to have the inventory - move as soon as the delivery is created.
Does anyone know of any technique - to post the inventory immediately.
I was thinking along the line of a workflow/create of an idoc (WHSCON) to faciliate this.
Kind Regards, Steve

You could simply scedule the batch job to PGI right after the delviery creation job runs (just delay it a few seconds after the longest period of time the delivery creation job runs).
So there would only be a very short delay, Looking at vl10g now to see is auto PGI is an option but I am thinking it is not
(I will update my post if I find it is)
Edit: It doesn't look like a standard option but I would imagine you could change a function code profile with custom user exit to trigger goods issue

Error in posting goods movement with production order

Hi all,
    I have a custom program that post goods movement using function 'Bapi_Goodsmvt_Create'.
The material passed into is a FERT material along with movement type 101, goods-movement code = 02', movement indicator = 'F'.    This function gives an error :
'E M7 022 Order quantity exceeded by 21.390 cse : item xxxxxx, plant xx prod order xxxxx'.
The material is a take weight material.   In production order, it came up to 910lb for total weight.
In goods receiving this material, i have changed the material from 910lb to 1016.950.
This is where the error came in. Note: 21.39 cases = 106.95 lb.
We had such take weight material worked before.
Can anyone pls suggestion what can be done about this ?
Thanks
Joyce

Hi Dario,
    Because the finised material is a take weight product, it should be ok unless there is a tolerance in the takeweight.   Also the production order is generated from 2 sales orders.
   To migo a production order, would it be A01 Goods Receipt and R08 for prod order ?
Thank you.
Joyce

BAPI_GOODSMVT_CREATE: Transport Order Goods Movements

Similar Messages

Maybe you are looking for