Transport Order Error

Hi experts,
I am trying to transport a TO containing a Datasource for the BW.
After the transport process, i am getting this error message in the TO log.
Only tables and views are permitted for extraction Message no. RJ044
I found just this link, but it doesen't really helped me.
Extract Structure not Being transported with custom Datasource
Can any one knows what is the cause of this problem?
Many thanks.
Regards.
Amine

Hi Amine,
Make sure your data source is active in Source system. IF not activate the data source in source system(if it is active also activate once again). Replicate the data source in BI system.
Now re-import the transport, it shold get successful.
Regards,
Venkatesh

Similar Messages

Error occuring while creating a Delivery for Stock transport order

Hi,
I am getting error while creating the delivery for thr stock transport order.The error message is given below.
                                                                                Error Log for coll. run 0001248218
4       6000038321 000010 Only 0 ST of material F784100 available
     4       6000038321 000010 An item with no delivery quantity is not permitted. Item will be deleted.
     4       6000038321 000020 Only 0 ST of material F784100 available
     4       6000038321 000020 An item with no delivery quantity is not permitted. Item will be deleted.
     4       6000038321 000030 Only 0 ST of material F784100 available
     4       6000038321 000030 An item with no delivery quantity is not permitted. Item will be deleted.
The stocks are present in the plant.
Can anyone help me to solve this issue?
Thanks
Srinivasan

Hi,
Check in
SPRO--IMG-MM-IM and PI---stock determinationassign stock determination in applications---Inventory management
Check for 641 or 647,there is a SD rule assigned.
Regards,
Deepak.

Commitment Item error in Stock transport order

Hi all
I have a stock transport order (STO) for a material non valuated in both sending and receiving plants.
While creation , there is an error with respect to completion of an "committment item" *.
If I input the committment item in STO create transaction in R3 , the STO is saved (permitting blank account assignment for the STO item as intended) and there is no further issue till post goods issue in sending plant or GR in receiving plant.
The problem is however that this STO is triggered from APO and transferred via CIF to R3 while there is no chance to input the commitment item. This results into a CIF error with the STO not created in both R3 and APO.
Is there a way I could bypass this "committment stuff" in this situation?
Thanks in advance
Anton
*The exact error message is as follows;
" No commitment item entered in item 00001 plant < >
Message no. FI311
Diagnosis
The posted document contains at least one company code in which Funds Management, Cash Budget Management, or Project Cash Management is active. Therefore you must enter a commitment item in all involved company codes.
Procedure
Enter a commitment item.
If you cannot enter a commitment item, check with your system administrator that your account assignment derivation is adjusted so that the system can automatically derive a commitment item from another account assignment, or from the G/L or cost element. "

Hi,
Did you try using derivation rule using FMDERIVE in case funds management is active.
Please also refer to the link below which guides on the item category to be assigned in Commitment item.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/f0/ca5716260211d28a430000e829fbbd/frameset.htm
Regards
K.R

Error when releasing a transportation order

Good morning.
I am trying to release a transportation order that contains a nonstandard table which has been added two fields, and the corresponding data elements and dominions of the new fields.
When releasing the order, dumps an error and cancels the export.
The status of the order now is "Initiated liberation".
The error code is:
"Error SQL 932 when accesing SPROXDAT: ORA-00932: inconsistent datatypes: expected %s got." And makes reference to data elements, but i think they are OK.
Please, ¿someone can help me?
Thanks a lot.
Regards.

well the problem is very likeley that the table has enhancement options which allow only character and NUMC append fields.
you most probably violated those preferences.

Error in stock transport order

Hi Sap Fans
i have created a stock transport oder from plant to depot for that first i have created a stock transport order in me21n and later i have done outbound delivery in vl10b and after i have done replenishment delivery in vl02n and after that i am doing billing in vf01 at that time i am getting the following log please help me how to solve the issue
error log 0080000011   000000 customer 0000002010: exception 7 in function module view _kuag2
please help me to complete the billing
thanks in advance
Srinivas

Hi Murali
at the time of doing migo am getting the following error
Goods receipt not possible for delivery 80000012: error code 4
Message no. M7865
Diagnosis
The goods receipt for the delivery cannot be posted.
The error according to the error code:
1. The delivery does not exist.
2. The delivery type is unknown.
3. The delivery is not goods issue posted.
4. There are no delivery items.
5. The receiving plant could not be determined.
6. The delivery items have already been goods receipt posted or contain zero quantities.
7. Goods receipt(effect)movement type to goods issue movement type could not be determined.
8. It is not currently possible to block the delivery.
Procedure
Error code 1      : Check your entry.
Error code 2,3,4,6: Check the delivery and its document flow.
Error code 5      : The delivery must be related to a purchase order or
                    the customer must be a retail business.
Error code 7      : Check the settins for your movement types.
please let me know how to solve this issue
Thanks n regards
srinivas

Optimizer run error - COM error 2 1 when deleting transportation orders

Hi Experts,
Optimizer run job (program /SAPAPO/RMSNPOPT) gets failed with following error: -
COM error 2 1 when deleting transportation orders
Can anybody let us know why this error occurs and how to resolve it. Thanks a lot.
Regards,
Chandan

Hi Chandan,
Could you check SAP note 1232670 whether applicable
for you
Regards
R. Senthil Mareeswaran.

Error in creating delivery document from stock transport order

hi sd gurus plz help i m nt able to create delivery in vl10b from stock transport order me21n after giving shipping point and po number also. can u help me out and can u tell me how to maintain copy control from stock tarnsport to delivery docu.

Hi Debesh,
The settings for Delivery type for STO is maintained using the following path:
Materials Management>Purchasing>Purchase Order>Set up Stock Transport Order>Assign Delivery Type and Checking Rule . Here you assign the Delivery type to Stock Transport order (with reference of Suplying Plant)
For creation of STO for delivery creation use T-code- VL04. Enter the Relevant Shipping Point and the Delivery Creation Date. Also tick mark the option Purchase order. If you already have a Purchase order enter the no.
System will show the details of the STO here by using the Main Menu > Delivery> Create Deliveries you can create the Delivery against the STO. Then by using the VL02n option you can do the Picking / PGI for the Delivery.
Hope the above helps you.
REWARD if it helps you!!
Regards,
Ajinkya

Problem in creation of STO(stock transport order)

hi all SAP gurus,
i am facing the problem in creation of stock transport order with ME21N code. i m getting the error msg of "Not possible to determine shipping data for material in STO "
i have checked the stock transport order setup in customization. but not getting the clear idea to come out from this problem.
if anybody have the idea of " how to do the customization of stock transport order setup, pls. let me explain.
thnx in advance.
rgrds,
rajesh

Hi Rajesh,
when ur creating STO with UB doc type, then you have to maintain material in both the plants.
Regarding the error which is comming for you, you have to check the settings at
SPRO- IMG- MM-Purchasing-Set up stock transport order- Assign delivery type & Checking rule
here for document type UB and your supplying plant-XXXX select nothing for Dlv type(delivery type) and chr - 01 and after this save.
After this you create STO as you are doing and see what the system is prompting.
For any further clarification let me know.
Regards,
NJ

Inter - Company Stock Transport Order Issue

MM SAP Gurus,
When I try working on "inter company stock transport order between two company codes."
I found the errors while creating PO(using document type UB)
ie.
*1st Error -Material 1 not maintained in Plant 2.
2nd Error - Customer 1 does not exist (please check entry in plant 1)
3rd Error - Not possible to determine shipping data for material1)*
i couldnt find out the error................................
Here is the configuration done by me......
Company codes:c1,c2
Plant for c1:p1
Plant for c2:p2
I m going to create and transfer stock from p2 to p1.
Here i m using stock transport order with billing(SD)
Purchase org for c1:porg1
Vendor for c1,porg1:v1
I assigned plant p2 in additional purchase data of vendor v1.
Sales area for c2:sorg2,ds2,d2
Customer for sales area(sorg1,ds1,d1):cust1
Now i go to mm->purchasing->purchase order->setup for stock transport order
> for receiving plant p1 i assign cust1,sales area(sorg1,ds1,d1)
> delivery type for supplying plant:NLCC
>checking rule RP.
i assigned doc.type UB into receiving plant p1 and supplying plant p2.
Then, in ME21N used doc type UB, these r the errors::::::::::::::::::::::::::::::
*1st Error -Material 1 not maintained in Plant 2.
2nd Error - Customer 1 does not exist (please check entry in plant 1)
3rd Error - Not possible to determine shipping data for material1)*
I already maintained all this.
The doc type NB also I tried ,,,,,,,but same errors r being shown.
Also where to create the inter company a/cs for billing?
Please check the attached file for the error and let me know.
Thanks & Regards
Keerthi ...

Business partner
● Vendor master u2013 supplying plant
Create the vendor for the purchasing organization of the receiving plant.
Assign the vendor to the supplying plant in the vendor master record.
From the menu, choose Logistics ® Materials Management ® Purchasing ® Master Data ® Vendor ® Purchasing ® Change (Current). Go to the Purchasing View and choose Extras ® Additional Purchasing Data.
● Customer master u2013 receiving plant
Create a customer master record for the receiving plant. From this, both the address and the data that is relevant for shipping point determination, such as transportation zone and shipping condition are taken.
From the menu, choose Logistics ® Sales and Distribution ® Master Data ® Business Partner ® Customer ® Create.
The above is from help.SAP:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/4d/2b90dc43ad11d189410000e829fbbd/frameset.htm
Plz check this link for tht information.
So, basing on this: I have customer 1 and vendor 1 for CC1......
--> Customer 1 is assigned to the receiving plant with sales area1 in setup STO configuration.
--> Vendor 1 is assigned to the supplying plant in the vendor master.
--> My question for u is:
1) In ME21N, in the vendor field u assign the vendor from CC1 or CC2 (Because it says the vendor - external supplier if u read in F1 in tht vendor filed)
Company code , Purc Org, plant all this will be from CC1 in ME21N, right?????????
Material exists in both the plants P1 and P2.......right?????
2) How to configure the inter - company accounts for the billing in sd for this STO scenario.???
Please clarify these things.....
You will be appreciated and rewarded too.
Thanks
Keerthi

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

Delivery costs in stock transport order

Dear SAP experts,
We want to add certain delivery cost in the stock transport order.
We create a new pricing schema with 3 delivery cost conditions "Z" conditions. The new pricing schema is assigned to the stock transport order doc type.
In transaction code me27, when the try tp enter the delivery cost conditions by clicking on the conditions icon, system given an error message saying that "Function not possible for this item". Message No. 06096.
Pricing is as follows -
STKP - Stock transfer price
Z001    10% on STKP
Z002     2% on STKP
Z003     1% on STKP
Kindly help.
Thanks & Regards,

Hi,
Check the following things
1. Make sure manual entry is allowed for Delivery Costs Condition
2. Make sure PO is not yet processed or no subsequent documents exists for the PO so that you can manually edit the PO using ME22N.
Thanks & Regards,

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.

Overdelivery in intra-company stock transport order

Hello,
I have the following scenario - I have two plants, 1000 and 2000, both under the same company code.
I transfer 450KG of material 123456 from plant 1000 using STO with SD (mvt. type 641), material is packed in HUs. In the receiving plant, the HUs are being place on a weight to check their actual weight. It;s possible for the actual weight be greater than the GI weight of 450KG (for example, due to weight scale accuracy issues) . When doing GR, I need to be able to receive quantity greater than the GI quantity. That is not allowed in stock transport order (per note 212387). For the same scenario with intercompany STO (GI mvt type 643) I'm able to post GR quantity which is greater than GI qty.
Any suggestion on how to solve this? Can I create a customer order type that is both intra-company and allows for overdelivery?
Thanks,
Yossi

a overdelivery does not make any sense in stock transfers, you would solve the problem of the stock accuracy in the receiving plant, but at the same time you create another problem with a negative stock in transit, that never gets cleared.
a STO having stock left in transit is never considered as closed. even intercompany stock transfers are not considered as closed, even you can receive more than issued.
Latest when archiving purchasing documents then you will see all your error in the process design, because only closed business cases can be archived.
in stock transfer business you always have to care about both sides, you cannot just care about the receiving plant and ignore the problems of the sending plant.

Intra Company Stock Transport Order

Hi,
This is a scenario of Intra Company Stock Transfer (using Stock Transport Order with document type UB) from one manufacturing plant to another manufacturing plant within the same company code.
I have created STO, prepared Outbound Delivery with T-Code VL10B and did PGI. Billing was done with T-code VF01 and Outbound Excise Invoice was created with T-Code J1IIN
While doing Goods Receipt in the Receiving plant with the T-code MIGO, when I referred the outbound excise invoice that was created in the previous step with the T-code J1IIN (put Excise Invoice No. and Date), I got the following error message "Excise invoice doesn't exist in the supplying plant" and not any Excise Value is flowing from the Excise Invoice in the screen of MIGO.
The CIN configuration and master data in J1ID seems to be ok.
Please provide the expert opinions to overcome the issue.
Thanks in advance
Rajesh Praveen

I did Goods Receipt with reference to Outbound Delivery in the Receiving Plant without referring any Excise Invoice Number (as our system has been designed now like this). I updated part RG23A part 1 using the material document number (generated as a result of Goods Receipt) in J1I5.
Now I am trying to post RG23A part 2 in J1IEX with reference to the material document number (generated as a result of Goods Receipt) and putting the Excise Number created in J1IIN earlier. The system is picking BED, ECS and SECess values but the value of Base Value is not being picked up as a result of which I am not able to post the Excise Invoice.
Please provide some idea to resolve this
Thanks in advance

Automatic delivery for stock transport order

Hi,
with ECC6 you have the possiblity to automatically create the delivery out of the stock transport order (STO) using the following customizing steps in SPRO:
Materials Management ->Purchasing->Purchase Order->Set up Stock Transport Order->Activate Automatic Delivery Creation and CRM Billing
Materials Management ->Purchasing->Purchase Order->Set up Stock Transport Order->Activate Automatic Delivery Creation for PO Type and Shipping Point
We want to use a batch job that runs ME59N to autmatically convert the purchase requisitions to STO and deliveries. While testing we found out that ME59N gives a warning when the availability check in the STO is running in case there is not enough stock. But you still can create STO and delivery.
In case you only create a STO and put it in VL10B to create the delivery it will only create delivery items with the quantities that are available in warehouse. So no stock means no delivery at that time.
Is it also possible using ME59N to
a) not create STO and delivery in case there is no stock
b) only create STO and no delivery in case there is no stock
Cheers
mickey

Hi,
Setting to error message not possible as this would cause all STOs not be convertered where no stock is available. But we need this functionality only for one specific process.
Omit faulty items we also tested and did not provide the result we need. It is related to faulty purchase requisition items.
Cheers
Mickey

Transport Order Error

Similar Messages

Maybe you are looking for