AUTOMATION OF STO PROCESS. Stock Transport Process in SAP ERP System Basic Scenarios STO can be categorized into four types depending on different scenarios. Scenarios SD/LE MM Intra-company STO Delivery type: NL PO type: In two steps Delivery item category: NLN > UB Stock transport ord., with "U" item category Billing relevance: Not relevant > NB Standard PO, with "blank" item category Movement type: 641 Intra-company STO Delivery type: NL PO type: In two steps Delivery item category: NLN > UB Stock transport ord., with "U" item category Billing relevance: Not relevant > NB Standard PO, with "blank" item category Movement type: 647 Cross-company STO Delivery type: NLCC PO type: in one step > NB Standard PO, with "blank" item category Delivery item category: NLC Billing relevance: relevant to billing Movement type: 643 Cross-company STO Delivery type: NLCC in two steps Delivery item category: NLC PO type: > NB Standard PO, with "blank" item category Billing relevance: relevant to billing Movement type: 645 o o Shipping Data and Delivery Due Index To deliver STO, it's necessary to have shipping data (EKPV table entry) tab in the STO. If there is still open quantity to be delivered, "deliv. creation date" (EKPV-LEDAT) filled has value. When all the quantity has been delivered, the date will be cleared. o Shipping Data Determination Shipping data (table EKPV) in STO is determined depending on: 1. Incoterms: customer master data. Unloading Point: from Ship-to. otherwise customer master data (KNVV-VSBED)Delivery priority: material/customer/distribution chain (KNMT). Shipping Point: loading group/shipping condition/supplying plant (TVSTZ) 5. Route Schedule: with delivery scheduling (T161V) 8. 2. Precondition of VETVG: VETVG will be filled (STO is relevant to delivery) if: . please check whether the index are updated correctly. Loading Group and Transportation Group: material master data (MARA. 170082. 170075.o If STO is ready to be delivered. Delivery Type: Purchase order category/document type/supplying plant (T161V. 170029. Language of Material Description: customer master data (KNA1-SPRAS) (to read material master data from MAKT) 10. Index VETVG is needed for selection in VL10*/VL04. system will update delivery due index table VETVG. different delivery types) 7. 4. Ship-to (customer of the receiving plant) (IMG -> MM -> Purchasing -> Purchasing Order -Set up Stock Transfer Order -> Define Shipping Data for Plants) 3. Supplying Plant 2. 303957) Shipping Condition: default order type (‘DL’) for delivery type (TVLK-DAART). from purchase order 11. otherwise customer master data (KNVV-LPRIO) 3. Indicator for Order Combination: customer master data 12. otherwise customer master data (KNVV-KZTLF) Delivery Due Index VETVG Different from delivery due index of sales document. Shipping data determination: Sales Area: from supplying plant (T001W) (See SAP notes 169586. If a STO cannot be listed in VL10* / VL04. Route: usual criteria for route determination (TROLZ) 6. MARC) 9. o o o o Indicator for Partial Deliveries: material/customer/distribution chain (KNMT). VETVG is the delivery due index for stock transport orders and contains the POs that are due for delivery. Material Master Data Delivery Type (IMG -> MM -> Purchasing -> Purchasing Order -Set up Stock Transfer Order -> Assign Delivery Type and Checking Rule) o 1. if available 4. Report ZKORVETV of note 61148 can be used to reorganize the delivery due index VETVG. There is no dialog transaction to deliver STO. VL10F. 2.0000 o o Create Replenishment Delivery Replenishment delivery can only be created by collective transaction. 4. VL10* (VL10B. Tcodes: 1...) In user role. Characteristics of replenishment deliveries from STO (Note: 842829) . > delivery date in EKPV is not 00. "with purchase orders" indicator is flagged.> shipping data (EKPV) is filled. VL10D.00. VL04 (Out of date) 3. it will update PO history with delivery number. . called “stock-in-transit” in the receiving plant (MB5T) If replenishment delivery contains HU. the HU will have status "in transit". the material document will also be updated to PO history. Control of Replenishment Delivery o o o o Goods Movement Goods issue with 641 creates a special stock type. (Similar as normal purchasing order) How Replenishment Delivery Updates STO PO History (table EKBE) > When replenishment delivery is created. you can only sum up the stock transport orders that are open for goods receipt to determine what is “in transit” (stock type: “stock-in-transit-CC”) o o o Goods receipt (with 101) is done via MB0A/MIGO with respect to the replenishment delivery. You can also use inbound delivery to post goods receipt. Goods issue with 643 (cross-company) doesn’t create such a stock and contains only one line in the GI material document Goods issue with 643 (cross-company) is nearly the same as goods issue with 601 to an external customer. (VEKP-STATUS = 40). after goods issue with 641 movement. item number and delivery quantity. > When posting GI. the quantity will be cumulated to corresponding delivery schedule. o PO Delivery Schedule (table EKET) > When replenishment delivery is created. otherwise. short dump (message_type_x ME803) might occur. (EKETWAMNG). One-step Goods Issue . (EKET-GLMNG field). o Delivery schedule (EKET) must be consistent with PO history (EKBE). > When posting GI. the delivery quantity will be cumulated to corresponding delivery schedule. g. ‘F’ for purchase order) . e.o Set T161W-UML1S = ‘X’ for supplying and receiving plant (and purchasing document category. and Actual Costing. The inbound delivery is created using the output determination in the outbound delivery. Please read SAP note 965176 for more information. you can use condition type SPED (Stock Transfer Generates Inbound Delivery to specify that inbound deliveries with reference to an outbound delivery are automatically created for stock transfer processes with receiving valuated stock in transit. Stock in Transit. you can post the material from issuing valuated stock in transit to receiving valuated stock in transit in transaction VLPOD. If the quantity changes during the proof-of-delivery. After the goods issue has been posted successfully. Variance from Actual Delivered Quantity in Sales Unit). Note: . In transaction VLPOD (Proof of Delivery). or via the receiving stock in transit to the receiving plant (movement type 109).0 (SAP_APPL_605). the system displays the difference (POD Overview tab. The new transaction MB5SIT (Display Stock in Transit) allows you to o o Display receiving stock in transit for the intra-company and cross-company process. Short text LOG_MM_SIT: Inbound Delivery with Stock in Transit (New) Use As of SAP enhancement package 5 for SAP ERP 6.00. Business Function MM. by entering the inbound delivery number Display issuing valuated and receiving valuated stock in transit If you have created an inbound delivery using condition type SPED.Synchronize billing plans This documentation is copyright by SAP AG. the system updates the inbound delivery.o set TVEP-BWA1S = 645/647 for SD schedule type NC/NN that belongs to item category NLC/NLN in TVEPZ (tcode VOV6) Automatically Creation of Inbound Delivery during 2-step STO As of Release ECC 6. To post into the receiving plant. you can also use the automatic inbound delivery creation during two-step stock transfers. you must use movement type 109 in transaction VL32N or MIGO. the system uses a special function (output type SPED) to create the inbound delivery. The following functions are available for inbound deliveries with stock in transit: At goods receipt you can post an inbound delivery either in the standard way (movement type 101). LOG_MM_SIT: Inbound Delivery with Stock in Transit (New) ( RELNMM_605_LOGMMSIT_INB ) Fill RESBD Structure from EBP Component Structure ROGBILLS . . SPRO > MM > Purchasing > PO > Set up STO > Activate Automatic Delivery Creation and CRM Billing Make sure that you use the proper document type ("F"). Check that for confirmation category LA (Inbound Delivery). the new fieldDelivery Type Inbound Stock in Transit (SiT) contains a delivery type for the process with stock in transit (for example Inbound Delivery of Receiving Valuated Stock in Transit (ELST). check that movement type 109 or a movement type with posting string reference 109 is assigned to this item category. NLIR. supplying plant.merge external lists to one complete list with #if.. see the following release notes: o o Cross-Company-Code Stock Transfer and Customer Delivery (New) Intra-Company-Code Stock Transfer (New) Further Information SAP Library for SAP ERP on Help Portal under http://help. under Logistics Execution -> Shipping -> Deliveries ->Define Item Categories for Deliveries. In transaction VV22 (Change Output . post first into the valuated stock in transit of the receiving plant.com/erp -> SAP ERP Central Component -> SAP ERP Enhancement Packages -> ERP Central Component Enhancement Package 5 -> SAP ERP Central Component -> Logistics -> Materials Management (MM) -> Inventory Management (MM-IM) -> Managing Special Stocks (MM-IM) -> Stock Transfer Using a Stock Transport Order ->Processes with Valuated Stock in Transit Release note LOG_MM_SIT: Business Function MM. This delivery type must use an item category (for example ELST) that uses movement type 109 or another movement type with posting string reference 109. you need to make the following settings in Customizing: Check confirmation control key: In Customizing. Stock in Transit and Actual Costing SUBST_MERGE_LIST . choose Materials Management -> Purchasing -> Confirmations -> Set Up Confirmation Control For the confirmation control key 0004 (Inbound Delivery).If you have to enter a handling unit for the storage location in the receiving plant. NCC3. the following must be flagged under Confirmation Sequence: o o 1. Check that an entry exists with condition type SPED (Stock Transfer Generates Inbund Delivery) and Requirement 408 (Stock Transfer Attachment ID). Output type SPED with role WE (Goods Receiver). or NLI3) have been created for output type SPED for output determination.sap. check the item category that is assigned to this delivery type. From the valuated stock in transit of the receiving plant. and creation indicator ("Y" in /SPE/V_T161V-AUTO_DELV) Activate Automatic Delivery Creation and CRM Billing . ensure that the correct condition records for the outbound delivery type used (NCCR. Set up condition record You create inbound deliveries with this item category when processing output type SPED during the goods issue of an outbound delivery. Define delivery type In Customizing. o 1. medium 8 (Special Function) and time 4 (Send Immediately (When Saving Application). choose Logistics Execution -> Shipping -> Basic Shipping Functions -> Output Control -> Output Determination -> Maintain Output Determination for Outbound Deliveries -> Maintain Output Determination Procedure. you can then post the goods receipt with reference to the inbound delivery into the storage location with mandatory handling unit. Check the following: o In Customizing for Logistics Execution. In Customizing. 1. under Shipping -> Deliveries -> Define Item Category Determination in Deliveries. Confirmation is GR-Relevant checkbox GR with Reference to Confirmation checkbox Define condition type SPED: In Customizing. logic for R3up Addresses (Business Address Services) This documentation is copyright by SAP AG.Condition Records: Shipping). Select schema V10000 (Header Output) and choose Control Data. Effects Effects Effects Effects 1. 1. For more information. choose Materials Management -> Purchasing -> Confirmations -> Define Internal Confirmation Categories. on on on on Existing Data Data Transfer System Administration Customizing To set up inbound deliveries with stock in transit. ensures that the Confirmation Control field in the stock transport order is set to Inbound delivery ('0004'). you must define a new document type in Customizing for Materials Management. o When you create an inbound delivery from an outbound delivery in SPM. you can activate the automatic creation of replenishment deliveries and CRM Billing for stock transport orders. You may copy the document type Stock transport order ('UB'). This. set the Auto Delv. Activities If you want to create a replenishment delivery immediately after creation of the stock transport order. indicator. This does not apply for purchase orders that are not yet released and on . in turn. to ensure that the intra-company stock transport order copies the values from the vendor information record. by choosing Purchasing -> Purchase Order -> Define Document Type. Requirements o You must use SAP CRM to execute CRM Billing. but you must set the Vendor indicator.Use In this IMG activity. Further notes o If you use this function the system does not perform an availability (ATP) check when it creates the delivery. for cross-company and cross-border stock transfers). o The route is determined in Extended Warehouse Management (SAP EWM) only if the automatic creation of replenishment deliveries is active. It assumes that the availability has already been checked during stock transport order processing.hold. If billing is required in CRM Billing (for example. set the CRM Bill indicator. . . SPRO > MM > Purchasing > PO > Set up STO > Activate Automatic Delivery Creation for PO type and Shipping Point NOTE -There's one prerequisite: please check OSS note 1069448. 3.2. . choose the delivery creation profile 'STOA' and uncheck the indicator 'Georoute'. Go to the transaction VL10CUC. . . . . . . Auto picking 1) Shipping points(V_TVST) details screen enter the below details under "Print picking List" Output Type EK00 Message Language EN Number of Messages 1 Send Time 4 Transmission Medium 1 . . . LP01 Name LIST1S Suffix 1 EK00 Suffix 2 KOMMILISTE . Suffix 2 Shipping Point OutputDevice . Name. Suffix1. output device.2) via transaction VP01SHP under "shipping (special case)(V4) and picking list (EK00) enter your shipping point. so once the job exected it will pcik all the Deliveries which are pending for the PGI. 4. 7. Goto the Transaction code SM36 to create a job for the program SAPMSSY0 which is the program for the AUTO PGI create a variant for the Delivery document types and sales organisation combinatioans and add this variant to the bath job created in SM36. 5.RV_INVOICE_CREATE . 2. 8. 6.VF04 1. RM06BB30(ZME59N) SDV03V02(ZSTOV_V2) RVV50R10C(ZVL10B/ZVL10D) WS_MONITOR_OUTB_DEL_GDSI(ZVL23) SDBILLDL/ RV60SBAT(ZVF06)/ BAPI_BILLINGDOC_CREATEMULTIPLE(ZBAPI_BILLINGDOC_CREATEMULTIPL) J1I3/J_1I_BATCH_UTILIZATION_MODVAT(ZJ1I3)/ Z_J1I3.ZJ1I3 J1IP/J_1IPRNE(ZJ1IP) WS_MONITOR_INB_DEL_GDRC(VL06IG) 00 06 589 FM .The above setting should trigger automatic picking in DO Automatic PGI you can create the PGI Atomatically by BATCH JOB using the program nder the VL23 transaction code. 3. Set the time of the Job to run after every 5 minutes. Automatic Billing After the PGI done you can run SDBILLDL program to create the Billing for all the document which were cleared and due for Billing.