Kit to Stock Management in EWM

 

Kit to Stock

Status: on-line

Shailesh Mishra

Business Process Senior Consultant at SAP America Inc.

6 artigos 

The kit-to-stock process is primarily used to create kits and then transfer them to stock. A kit is a list of products that are always delivered together. Kit-to-stock management provides with a simple, streamlined kit-creation process that is executed and documented in the warehouse. This can be either trigger kit creation manually in the SAP S/4 system based on a production order( Manufacturing order), or in the SAP EWM system directly, using a value-added service order (VAS order). This blogs is written to explain 'Kit to Stock' process from S/4 system via creation of Production Order with VAS.

Definition: A kit is a list of products that are always delivered together. Examples of kits include the following entities:

• Groups of materials used to repair a piece of machinery
• Groups of materials used for assembly tasks
• Add-on products for other products
• Displays or assortments of products to sell in a retail store

>To set up ''Kit to Stock'' management in system, SAP suggests to activate below BC sets.

• /SCWM/KTS_KTR is a hierarchical BC sets which needs activation of lower BC sets also. /SCWM/KTS, /SCWM/KTR and /SCWM/KTS_KTR_DLV.( Read SAP documentation for complete information related 'Kitting' BC sets.

Replication in system:

Creation of production order in S/4. The production scheduling profile in S/4 facilitate kit to stock management.

Once production is released, it creates 2 deliveries- Outbound for kit components and Inbound for Kit Header. Production order must have status as ''LFAN'' symbolizing creation of deliveries. Check LIPS table with Order number( AUFNR) or with VL06O/I transaction for deliveries.

Check EWM monitor for distributed Kitting deliveries. A VAS order is the connecting bridge between Inbound & Outbound delivery.

Conduct picking of kit components to a work center. The kits are routed to work centre via a pick HU.

Perform Kitting process via navigating to 'Kitting VAS Work Center''

Once Kit component is posted, consumption is triggered.

Now, post the Kit header production.

Post Kit header production via packing in HU

Goods receipt is updated in Inbound delivery and 101 is posted in S/4 Production order.

Later, Kit header can be putawayed to final Bin in warehouse. This completes the process.

Lesser Known Facts about Kit to Stock

• Overpicking of Kitting delivery:It is possible to carry out over picking in EWM if the 'Unlimited overdelivery allowed' indicator has been set for the ship-to of the KTS outbound delivery.

Co- Products in Production Order and many other restrictions:Below process will not trigger any kitting delivery from S/4, release rejection error gets prompted.

Kit to Stock with Sales Order Stock or Project Stock:Kit to stock is also supported with special stock like Sales order stock or Project stock.

Regeneration of Deleted Kitting Inbound delivery: There is no way to generate deleted or rejected inbound delivery from EWM. Kitting deliveries(Kit to Stock) are always created from production order. Kit to stock deliveries can also be never created from Manufacturing order confirmation or via MIGO. It is always recommended to switch off the ''Process Code'' for the required process code profile relevant to Kit to stock Inbound delivery.

Important functional modules:Below are important and critical function modules available for debugging Kit to stock process.

Most important are highlighted in yellow for Kit components and Kit headers.

All testing is performed in S/4 HANA 2020 Sandbox system

Source: https://www.linkedin.com/pulse/kit-stock-management-ewm-shailesh-mishra/

Transportation cross docking with SAP Extended warehouse management (EWM) with S/4HANA

 Cross – docking is very widely used in today’s supply chain. There are different variants of cross docking. Recently, I worked on a specific business requirement (on Title of ownership of goods while moving goods from one warehouse to another) for a customer. SAP Transportation cross docking(TCD) meets the requirement and my present blog is to explain the same highlighting its unique features.

That Customer has several plants producing several products and they have intermediate warehouses where the products are consolidated and then delivered to the customer as depicted in below image. One of the main requirements is that the title of ownership of the products will still be with the manufacturing plant 1010 while the products are physically at the intermediate warehouse D002 (linked with plant 2010). Standard SAP’s transportation cross docking (TCD) flow with EWM supports this requirement on title of ownership (as explained later in this blog).

A high-level process flow for TCD is depicted in below image.

and described as below.

1.      An outbound delivery is created in ERP (ECC or S/4HANA). This outbound delivery can be created from a Sales order (or Stock transfer order). Outbound delivery 80002978 created for customer / Ship to party (10100001) from plant 1010 with Storage location DAFS. 

2.   This ERP outbound delivery gets distributed to decentralized EWM and creates an Outbound delivery order with same number 80002978 for warehouse D001. Note that it has a route TCD_ROUTE1 with Ship to party BP2010 and final ship to party as 10100001 (i.e goods will first be moved to an intermediate warehouse with BP2010 and finally to customer 10100001.

Route TCD_ROUTE1 is a part of TCD route TCD_ROUTE which has 2 legs. First leg corresponds to the flow from plant 1010 (warehouse D001) to intermediate warehouse D002 and second leg corresponds to the flow from the intermediate or Cross docking warehouse D002 to the customer 10100001.

Outbound delivery order is picked and packed with a handling unit as in below image.

Normal EWM process is followed to trigger goods issue which creates EWM outbound delivery order updating the ERP outbound delivery with the handling unit number and posting goods issue.

3. Goods issue on the original ERP outbound delivery 80002978 triggers output CDOD which creates a delivery pair – Inbound 180001033 and outbound delivery 80002979 as shown in below image from the Transportation cross docking monitor. 

4. ERP Inbound delivery 180001033 is created for the  intermediate warehouse (D02) with plant 1010 and cross docking storage location (TCDO).   

As the plant in the inbound delivery is 1010 (i.e the manufacturing plant), the title of ownership of the goods lies with the manufacturing plant (This is one of the major requirements for the customer and one of the best features of TCD).

5. EWM inbound delivery 180001033  (as created from ERP inbound delivery) has the Owner as BP1010 is depicted in below image i.e the title of the goods will still belong to the manufacturing plant 1010 after goods receipt of the product in intermediate warehouse D002 (belonging to plant 2010).

Handling unit number is also transferred to this EWM inbound delivery from the original outbound delivery as shown in below image.

Goods receipt is carried out following the standard EWM process.

6. ERP outbound delivery 80002979 belongs to the warehouse D02 , but the title ownership of the goods is still with the manufacturing plant 1010 as shown in below image.

7. As expected the EWM outbound delivery order 80002979 also has the owner as BP1010 as shown in below image i.e title ownership of goods is still with the manufacturing plant though the goods are now in intermediate warehouse D002 (belonging to a different plant 2010).

Now goods issue is carried out on the EWM ODO as per the standard process and the title ownership is transferred to the customer 10100001 only after the goods are issued from the intermediate cross docking warehouse.

Now, like to highlight the salient features of this TCD flow

• This flow is possible only with decentralized EWM (i.e not with embedded EWM) as the routing with multiple legs (through EWM routing guide) is NOT supported in embedded EWM
• Title of ownership of goods belongs to the manufacturing (or original delivery) plant though the goods are physically present in intermediate cross docking warehouse (This is an unique feature with TCD)
• There can be multiple intermediate transporattion cross docking warehouses in the supply chain (considered only one intermediate warehouse in my blog for the sake of simplicity)

This prototype has been carried out with S/4HANA 2021 release (as ERP) with decentralized EWM on  S/4HANA 2021 release. There is no custom coding i.e it is a pure standard SAP flow. Will appreciate your feedback / comments.

Source: https://www.linkedin.com/pulse/transportation-cross-docking-sap-extended-warehouse-management-roy/