Solution Manager Content for Inbound Process With Stock-Specific UoM

Transcription

1 Solution Manager Document version: Solution Manager Content for Inbound Process With Stock-Specific UoM Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. 1

2 Document History The following table provides an overview of the most important document changes. Version Date Description First version Changed storage location from 'ROD' to 'AFS' in test cases, step Preparation Step 1 (all variants) Copyright 2015 SAP SE or an SAP affiliate company. 2 All rights reserved.

3 Content Inbound Process With Stock-Specific UoM (Manual Goods Receipt) Inbound Process With Stock-Specific UoM (Manual Warehouse Task) Configuration of Inbound Process With Stock-Specific UoM Configuring Automatic Creation of Purchase Orders in SAP ERP Configuration of Expected Goods Receipt Creation Checking Document Types and Item Types Checking Determination of Document Types and Item Types Checking Determination of Date Types Scheduling Background Jobs for Creation of Expected Goods Receipts Configuration of Inbound Delivery Creation Checking Document Types and Item Types Checking Manual Creation of Inbound Deliveries Checking UoM Handling of Inbound Deliveries Checking Determination of Document Types and Item Types Checking Determination of Date Types Checking Determination of Warehouse Process Types Configuring Determination of Staging Areas and Goods Movement Bins Configuration of Warehouse Order Creation Configuring Automatic Creation of Warehouse Tasks Checking Warehouse Process Types Checking Activity Areas for Putaway Checking Determination of Destination Bins for Putaway Checking Warehouse Order Creation Rules Configuring Printing of Warehouse Orders Configuration of Stock-Specific Unit of Measure Configuring Unit of Measure Handling Checking Determination of Destination Bins for Putaway Creating Products Configuring Automatic Creation of Purchase Orders in SAP ERP Test Case for Inbound Process with StockSpecific UoM (Manual GR) Test Case for Inbound Process with StockSpecific UoM (Manual WT) Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. 3

4 1 Solution Manager Content for Inbound Process With Stock-Specific UoM Copyright 2015 SAP SE or an SAP affiliate company. 4 All rights reserved.

5 2 Inbound Process With Stock-Specific UoM (Manual Goods Receipt) You use this business process to receive goods on pallets from external vendors. Each pallet contains only a single product. The goods on the pallets have a unit of measure (UoM) that represents a smaller package size, for example, cartons containing six items. You are interested in this information because you will handle the product in your warehouse using this UoM. Some vendors send advanced shipping notifications (ASNs) to SAP ERP. You check the goods in the goods receipt area, and post the goods receipt (GR) in SAP Extended Warehouse Management (EWM). Upon GR posting, warehouse orders (WOs) are created. Depending on the product attributes, you move the goods to different areas in the warehouse using the information contained in the printed WOs. You move uncategorized products to a clarification zone before you put them away. Figure 1: Inbound Process With SUoM (Manual Goods Receipt) When a truck arrives, a checkpoint clerk directs the truck to a door. The truck driver brings the delivery note to the GR office. If the vendor has sent an ASN to SAP ERP, a GR office clerk finds the corresponding inbound delivery in EWM. If there is no inbound delivery in the system, the GR office clerk creates it in EWM. A warehouse worker unloads the truck. A warehouse clerk checks the goods against the delivery note, writes differences on the delivery note, and takes the revised delivery note to the GR office. If there are differences, the GR office clerk adapts the inbound delivery and changes the quantity or the UoM in the system. The GR office clerk posts the GR. Upon GR posting, the system automatically creates and prints WOs for the inbound delivery to move the goods into the warehouse. The truck leaves. The warehouse worker moves the goods from the GR area into the warehouse. The goods are then moved to the following storage types: A storage type for pallets A storage type for cartons A storage type for single parts In the storage types for cartons and single parts, the next empty storage bin is determined as the destination storage bin. Products that have no fixed bin assignment in the pallet storage are moved into a separate storage type for clarification. When the goods are in the destination storage bins, the warehouse clerk confirms the putaway WOs. This process does not use the following functions: Packing using handling units (HUs) Shipping and receiving using transportation units (TUs) Inbound Process With Stock-Specific UoM (Manual Goods Receipt) Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. 5

6 ... Quality inspection Storage control (multistep putaway) Radio frequency (RF) devices Prerequisites In the business process Inbound Process With SUoM (Manual Warehouse Task) [page 10], you can create warehouse tasks (WTs) manually, and the system posts the GR automatically. Either a purchasing document already exists in SAP ERP, or no purchasing document exists yet but you have set up automatic purchase order creation in SAP ERP. For more information about the configuration prerequisites, see Configuration of Inbound Process Without Packing Information [external document] and Configuration of Inbound Process With SUoM [page 14] Process The business process runs in EWM as follows: 1. A truck arrives at the checkpoint and drives to the door The truck drives to the door assigned by a checkpoint clerk. This step is not carried out in the system. 2. Check the delivery note and find or create an inbound delivery (EWM) The truck driver brings the delivery note to the GR office where a GR office clerk checks it against the system data. Variant A: The GR office clerk finds the inbound delivery by entering the ASN number in the system. In this case, the vendor has sent an ASN, the inbound delivery is created in SAP ERP, and it is automatically sent to EWM. The UoM of the ERP inbound delivery item is taken over into the EWM inbound delivery item as far as it is a stock-specific UoM (SUoM). Otherwise the quantity remains in base UoM or the preferred UoM is proposed if the quantity fits. Variant B: The GR office clerk finds an expected GR by entering the PO number in the system. In this case, he or she manually creates an inbound delivery based on the expected GR. The UoM of a purchase order item is taken over into the EGR document and from there into the EWM inbound delivery item as far as it is an SUoM. Otherwise the quantity remains in base UoM or the preferred UoM is proposed if the quantity fits. Variant C: The GR office clerk finds no inbound delivery and no expected GR in the system. In this case, he or she manually creates an inbound delivery by entering the data from the delivery note in the system. If the delivery note contains information about the UoM of the items, the GR office clerk creates the EWM inbound delivery items directly in this UoM. Instead of manually creating inbound deliveries in EWM, you can also create the deliveries in SAP ERP, or to switch to SAP ERP from the user interface in EWM to create them. If you choose an SUoM for the delivery item it is replicated to the EWM inbound delivery item. 3. Unload the truck and check the goods A warehouse worker unloads the truck. A warehouse clerk checks the package information against the delivery note and writes differences on the delivery note. As well as the quantity that was delivered, he also checks the UoM of the delivered product. The warehouse clerk takes the revised delivery note to the GR office. This step is not carried out in the system. 4. Post the goods receipt and create the putaway WOs (EWM) Before posting the GR, the GR office clerk can change the delivery data in the system (for example, quantities and UoMs) based on the revised delivery note. If there is no information about the UoM in which an item is delivered, or if the UoM actually delivered differs from the one in the system, the GR office clerk can adapt it. Copyright 2015 SAP SE or an SAP affiliate company. Inbound Process With Stock-Specific UoM (Manual Goods Receipt) 6 All rights reserved.

7 The GR transaction offers scanning capabilities to identify delivery items by product or GTIN (EAN/UPC). The GR office clerk posts the GR. The system sends the GR to SAP ERP. When the GR is posted, the system automatically creates warehouse tasks (WTs). Using the quantity classification of the SUoM handling, the system creates one WT for each physical unit of the product and sends it to a bin appropriate for the package size. The system then creates one WO for each WT. If the fixed bin or the destination storage type of a product is full, the system also determines a destination bin in the clarification zone. Upon creating the putaway WOs, the system automatically prints two copies of them in the GR office. One printout is attached to the goods; the other one is used for putaway execution and confirmation. 5. The truck leaves This step is not carried out in the system. 6. Put away the goods (EWM) The warehouse worker takes both printouts of the WOs from the GR office. He or she then goes to the GR area to identify the goods (using the product short description in the WO). He or she attaches one WO printout to the goods, and moves them to the destination bin. If the destination bin cannot be reached or if it is full, he or she takes the goods to the clarification zone. At the end of putaway execution, a warehouse clerk confirms the putaway WOs in the system. 7. Put away the goods from the clarification zone (EWM) This step is necessary only in exceptional cases. The warehouse clerk monitors the stock in the clarification zone. If stock exists there, he or she checks the reason why the stock was moved to the clarification zone. If the warehouse-specific master data is missing for the product, he or she creates it. If the packaging specification for the product is missing, he or she creates it together with the condition record. If the assigned fixed bin is full, he or she assigns a new suboptimal fixed bin to the product. Finally, he or she creates an ad hoc WO to put away the product. The system prints the ad hoc WO. After the warehouse worker has put the product away, the warehouse clerk confirms the WO in the system. Process Monitoring The monitoring functions are described in the configuration of the process Inbound Process Without Packing Information (Manual GR) [external document]. More Information For more information about how to run this business process in the system, see Test Case for Inbound Process With SUoM (Manual GR) [page 52]. For more information about the functions used in this business process, see SAP Library for SAP Extended Warehouse Management on SAP Help Portal at help.sap.com/ewm. Inbound Process With Stock-Specific UoM (Manual Goods Receipt) Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. 7

8 3 Inbound Process With Stock-Specific UoM (Manual Warehouse Task) You use this business process to receive goods on pallets from external vendors. Each pallet contains only a single product. The goods on the pallets have a unit of measure (UoM) that represents a smaller package size, for example, cartons containing six items. You are interested in this information because you will handle the product in your warehouse using this UoM. Some vendors send advanced shipping notifications (ASNs) to SAP ERP. You check the goods in the goods receipt area, and post the goods receipt (GR) in SAP Extended Warehouse Management (EWM). Upon GR posting, warehouse orders (WOs) are created. Depending on the product attributes, you move the goods to different areas in the warehouse using the information contained in the printed WOs. You move uncategorized products to a clarification zone before you put them away. Figure 2: Inbound Process With SUoM (Manual WT) When a truck arrives, a checkpoint clerk directs the truck to a door. The truck driver brings the delivery note to the GR office. If the vendor has sent an ASN to SAP ERP, a GR office clerk finds the corresponding inbound delivery in EWM. If there is no inbound delivery in the system, the GR office clerk creates it in EWM. A warehouse worker unloads the truck. A warehouse clerk checks the goods against the delivery note, writes differences on the delivery note, and takes the revised delivery note to the GR office. If there are differences, the GR office clerk adapts the inbound delivery and changes the quantity or the UoM in the system. The GR office clerk posts the GR. Upon GR posting, the system automatically creates and prints WOs for the inbound delivery to move the goods into the warehouse. The truck leaves. The warehouse worker moves the goods from the GR area into the warehouse. The goods are then moved to the following storage types: A storage type for pallets A storage type for cartons A storage type for single parts In the storage types for cartons and single parts, the next empty storage bin is determined as the destination storage bin. Products that have no fixed bin assignment are moved into a separate storage type for clarification. When the goods are in the destination storage bins, the warehouse clerk confirms the putaway WOs. This process does not use the following functions: Packing using handling units (HUs) Shipping and receiving using transportation units (TUs) Quality inspection Copyright 2015 SAP SE or an SAP affiliate company. Inbound Process With Stock-Specific UoM (Manual Warehouse Task) 8 All rights reserved.

9 Storage control (multistep putaway) Radio frequency (RF) devices Prerequisites In the business process Inbound Process With SUoM (Manual Goods Receipt) [page 6], the system creates WTs automatically, and you can post the GR manually. Either a purchasing document already exists in SAP ERP, or no purchasing document exists yet but you have set up automatic purchase order creation in SAP ERP. For more information about the configuration prerequisites, see Configuration of Inbound Process Without Packing Information [external document] and Configuration of Inbound Process With SUoM [page 14]. Process The business process runs in EWM as follows: 1. A truck arrives at the checkpoint and drives to the door The truck drives to the door assigned by a checkpoint clerk. This step is not carried out in the system. 2. Check the delivery note and find or create an inbound delivery (EWM) The truck driver brings the delivery note to the GR office where a GR office clerk checks it against the system data. Variant A: The GR office clerk finds the inbound delivery by entering the ASN number in the system. In this case, the vendor has sent an ASN, the inbound delivery is created in SAP ERP, and it is automatically sent to EWM. The UoM of the ERP inbound delivery item is taken over into the EWM inbound delivery item as far as it is a stock-specific UoM (SUoM). Otherwise the quantity remains in base UoM or the preferred UoM is proposed if the quantity fits. Variant B: The GR office clerk finds an expected GR by entering the PO number in the system. In this case, he or she manually creates an inbound delivery based on the expected GR. The UoM of a purchase order item is taken over into the EGR document and from there into the EWM inbound delivery item as far as it is an SUoM. Otherwise the quantity remains in base UoM or the preferred UoM is proposed if the quantity fits. Variant C: The GR office clerk finds no inbound delivery and no expected GR in the system. In this case, he or she manually creates an inbound delivery by entering the data from the delivery note in the system. If the delivery note contains information about the UoM of the items, the GR office clerk creates the EWM inbound delivery items directly in this UoM. Instead of manually creating inbound deliveries in EWM, you can also create the deliveries in SAP ERP, or to switch to SAP ERP from the user interface in EWM to create them. If you choose an SUoM for the delivery item it is replicated to the EWM inbound delivery item. 3. Unload the truck and check the goods A warehouse worker unloads the truck. A warehouse clerk checks the package information against the delivery note and writes differences on the delivery note. As well as the quantity that was delivered, he also checks the UoM of the delivered product. The warehouse clerk takes the revised delivery note to the GR office. This step is not carried out in the system. 4. Create the putaway WOs (EWM) Before creating the putaway WOs, the GR office clerk can change the delivery data in the system (for example, quantities and UoMs) based on the revised delivery note. If there is no information about the UoM in which an item is delivered, or if the UoM actually delivered differs from the one in the system, the GR office clerk can adapt it. The GR office clerk manually creates WTs in the system. He or she checks the packaging of the product and saves the WTs. Using the quantity classification of the SUoM handling, the system proposes to create one WT for each physical unit of the product and sends it to a bin appropriate for the package size. The system then creates one WO for each WT. Inbound Process With Stock-Specific UoM (Manual Warehouse Task) Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. 9

10 If the fixed bin or the destination storage type of a product is full, the system also determines a destination bin in the clarification zone. Upon creating the putaway WOs, the system automatically prints two copies of them in the GR office. One printout is attached to the goods; the other one is used for putaway execution and confirmation. 5. The truck leaves This step is not carried out in the system. 6. Put away the goods and post the GR (EWM) The warehouse worker takes both printouts of the WOs from the GR office. He or she then goes to the GR area to identify the goods (using the product short description in the WO). He or she attaches one WO printout to the goods, and moves them to the destination bin. If the destination bin cannot be reached or if it is full, he or she takes the goods to the clarification zone. At the end of putaway execution, a warehouse clerk confirms the putaway WOs in the system. Upon the confirmation of the putaway WOs, the system automatically posts the GR and sends it to SAP ERP. 7. Put away the goods from the clarification zone (EWM) This step is necessary only in exceptional cases. The warehouse clerk monitors the stock in the clarification zone. If stock exists there, he or she checks the reason why the stock was moved to the clarification zone. If the warehouse-specific master data is missing for the product, he or she creates it. If the packaging specification for the product is missing, he or she creates it together with the condition record. If the assigned fixed bin is full, he or she assigns a new suboptimal fixed bin to the product. Finally, he or she creates an ad hoc WO to put away the product. The system prints the ad hoc WO. After the warehouse worker has put the product away, the warehouse clerk confirms the WO in the system. Process Monitoring The monitoring functions are described in the configuration of the process Inbound Process Without Packing Information (Manual WT) [external document]. More Information For more information about how to run this business process in the system, see Test Case for Inbound Process With SUoM (Manual WT) [page 64]. For more information about the functions used in this business process, see SAP Library for SAP Extended Warehouse Management on SAP Help Portal at help.sap.com/ewm. Copyright 2015 SAP SE or an SAP affiliate company. Inbound Process With Stock-Specific UoM (Manual Warehouse Task) 10 All rights reserved.

11 4 Configuration of Inbound Process With Stock-Specific UoM You use this process to configure the following business processes: Inbound Process With SUoM (Manual Warehouse Task) [page 10] Inbound Process With SUoM (Manual Goods Receipt) [page 6] You can use this configuration process in the following warehouses in SAP Extended Warehouse Management (EWM): Standard warehouse W001 with preconfigured business processes This is the recommended way of getting started with EWM. For more information, see the business scenario Warehouse Management with Preconfigured Processes [external document]. Your own warehouse To set up the preconfigured business processes in standard warehouse W001, implement all configuration steps except the steps marked with Optional. These steps help you to understand the configuration of the processes but do not require a manual activity. To configure the processes in your own warehouse, implement all configuration steps. In the steps marked with Optional, check if you need to adapt the existing entries to your own warehouse and carry out changes as needed. All configuration steps require activities in EWM unless the documentation explicitly tells you to carry out an activity in SAP ERP. Prerequisites For more information, see Configuration of Warehouse Management with Preconfigured Processes [external document]. You have implemented the SAP Process 1. Configuring Automatic Creation of Purchase Orders in SAP ERP [page 17] 2. Configuration of Expected Goods Receipt Creation [page 18] 3. Configuration of Inbound Delivery Creation [external document] 4. Configuration of Warehouse Order Creation [page 34] 5. Configuring Printing of Warehouse Orders [page 45] Result You have configured the Inbound Process With SUoM (Manual Warehouse Task) and the Inbound Process With SUoM (Manual Goods Receipt). In warehouse W001 you can run the business processes as described in the following test cases: Test Case for Inbound Process With SUoM (Manual WT) [page 64] Test Case for Inbound Process With SUoM (Manual GR) [page 52] Example You configure these business processes in warehouse W001 using the following data (see Configuration of Warehouse Structure and Master Data for SAP EWM [external document]): Warehouse Structure The warehouse structure for the SUoM inbound process differs slightly from the inbound process of the preconfigured warehouse. Whole pallets are stored In storage type T050, cartons are stored in storage type T020, and single items are stored in storage type T051. Storage Type T020 Description Carton Storage Configuration of Inbound Process With Stock-Specific UoM Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. 11

12 T050 T051 T910 T970 Pallet Storage Single Part Storage Provide in Goods Receipt Clarification Zone Storage Type Storage Section Description T020 S001 Fast-Moving Items T020 S002 Slow-Moving Items T050 S001 Total Section T910 S001 Total Section T970 S001 Total Section Storage Bin Description T020* All Bins Starting with T020 T050* All Bins Starting with T050 T051* All Bins Starting with T051 GR-ZONE CL-ZONE Goods Receipt Zone Clarification Zone Activity Area T020 T050 A001 A002 T970 Description Act. Area for Storage Type T020 Act. Area for Storage Type T050 Act. Area for Small, Mid Parts in T051 Act. Area for Large Parts in T051 Act. Area for Storage Type T970 Staging Area Group Staging Area Description T910 S001 Staging area referring to the goods receipt zone Master Data Vendor VEND001 Description Vendor VEND001 Product Description Copyright 2015 SAP SE or an SAP affiliate company. Configuration of Inbound Process With Stock-Specific UoM 12 All rights reserved.

13 PROD-S01 Small part, fast-moving 01 PROD-S02 Small part, fast-moving 02 PROD-S03 Small part, fast-moving 03 PROD-S04 Small part, fast-moving 04 PROD-S05 Small part, slow-moving 05 PROD-S06 Small part, slow-moving 06 PROD-S07 Small part, fast-moving 07 PROD-L01 Large part 01 PROD-L02 Large part 02 PROD-L03 Large part 03 Printer PR05 PR06 Description Printer located in the goods receipt office Printer located in the clarification zone Other Master Data Supply Chain Unit PLPL01 SP0002 Description Supply chain unit for warehouse W001 Supply chain unit with role receiving office Process-Specific Settings Warehouse Process Type P110 P115 Description Putaway with Palletization Warehouse process type used to put away goods Putaway with Palletization from Cl. Zone Warehouse process type used to put away goods from clarification zone 4.1 Configuring Automatic Creation of Purchase Orders in SAP ERP You use this procedure to configure the automatic creation of purchase orders (POs) in SAP ERP. This is necessary if you want to allow inbound deliveries without a purchase order reference to be created in SAP Extended Warehouse Management (EWM). Prerequisites You have implemented SAP in ERP. Procedure 1. Enable automatic purchase order determination as follows: a. In Customizing for Logistics Execution, choose Extended Warehouse Management Integration Extended Inbound Delivery Processing Settings for Inbound Delivery Processing. Configuration of Inbound Process With Stock-Specific UoM Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. 13

14 b. Change the entry for document type EL as follows: Delivery Type Description Automatic PO Determination EL Inbound Delivery 1 (Automatic PO Determination: Yes) 2. Create info records for the automatic creation of purchase orders as follows: a. On the SAP Easy Access screen, choose Logistics Materials Management Purchasing Master Data Info Record Create. b. Create the following entries: Vendor Material VEND001 PROD- S01 Purchasing Organization Plant Variable Order Unit Planned Delivery Time / Days Standard Quantity / PAL Net Price / EUR Create Purchase Order for Delivery Without Reference 0001 PL X 0004 Confirmation Control Key VEND001 PROD- S02 VEND001 PROD- S03 VEND001 PROD- S04 VEND001 PROD- S05 VEND001 PROD- S06 VEND001 PROD- L01 VEND001 PROD- L02 VEND001 PROD- L PL X PL X PL X PL X PL X PL X PL X PL X Configuration of Expected Goods Receipt Creation You use this process to configure the creation of expected goods receipts. This is necessary if you want to create inbound deliveries based on expected goods receipts and also if you do not have an advanced shipping notification (ASN) from the vendor. The process includes the configuration of the following objects: Process Goods receipt notification: A document in the inbound delivery process that copies all relevant logistics data from the initiator of the inbound delivery process, such as data of a purchase order or a production order. An expected goods receipt is generated out of a notification of expected goods receipt. Expected goods receipt: Document that contains the expected goods receipt data. An expected goods receipt contains data of an open purchase order or a production order. It displays a copy template so that data from the production order or from the purchase order can be copied when manually creating a delivery. Copyright 2015 SAP SE or an SAP affiliate company. Configuration of Inbound Process With Stock-Specific UoM 14 All rights reserved.

15 1. Checking Document Types and Item Types [page 19] (Optional) 2. Checking Determination of Document Types and Item Types [page 20] (Optional) 3. Checking Determination of Date Types [page 22] (Optional) 4. Scheduling Background Jobs for Creation of Expected Goods Receipts [page 24] More Information For more information, see SAP Library for SAP Extended Warehouse Management on SAP Help Portal at help.sap.com/ewm under Delivery Processing Notification of Expected Goods Receipt Checking Document Types and Item Types You can use this procedure to check the configuration of the document types and item types for goods receipt notifications and expected goods receipts. Procedure 1. Check the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Expected Goods Receipt Manual Settings Define Document Types for Expected Goods Receipt: Document Type Document Category EGRE EGR Expected Goods Receipt EGRE GRN Expected Goods Receipt Notification Document Category Description Description Status Profile Expected Goods Receipt Expected Goods Receipt /SCDL/EGR /SCDL/GRN 2. Check the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Expected Goods Receipt Manual Settings Define Item Types for Expected Goods Receipt: Item Type Document Category Item Category Description EDLV EGR DLV Standard Item Expected Goods Receipt EDLV GRN DLV Standard Item Expected Goods Receipt ETXT EGR TXT Text Item Expected Goods Receipt ETXT GRN TXT Text Item Expected Goods Receipt 3. Check the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Expected Goods Receipt Define Allowed Item Types for Expected Goods Receipt: Document Type EGRE EGRE Item Type EDLV ETXT 4. Check the status profiles as follows: a. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery Processing Status Management Define Status Profiles. b. Select a status profile, for example /SCDL/EGR. c. In the dialog structure, choose Status Types. Configuration of Inbound Process With Stock-Specific UoM Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. 15

16 d. Check the following entries (for example, for status profile /SCDL/EGR): Status Type Short Text Inactive DBC Blocked (Inconsistency) - DBO Blocked (Overall Status) - Goods receipt notifications and expected goods receipts are deleted and not archived (see Scheduling Background Jobs for Creation of Expected Goods Receipts [page 24]). Therefore, completion status type DCO is not relevant as for other documents, such as inbound deliveries (see Checking Document Types and Item Types [page 25]) Checking Determination of Document Types and Item Types You can use this procedure to check how the system determines document types and item types for goods receipt notifications and expected goods receipts. Procedure 1. Check the following entry in Customizing for Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Map Document Types from ERP System to EWM: Document Type from ERP Code for Initiator of a Communication Chain EL GRN EGRE Mapping Delivery Type Document Type If you use a delivery type other than EL in the SAP ERP, create the entries for your SAP ERP delivery type accordingly. 2. Check the following entries in Customizing for Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Map Item Types from ERP System to EWM: Document Type from ERP Item Type from ERP Document Type EL ELN EGRE EDLV EL ELTX EGRE ETXT Mapping of ERP Item Type Result Copyright 2015 SAP SE or an SAP affiliate company. Configuration of Inbound Process With Stock-Specific UoM 16 All rights reserved. If you use an ERP document type other than EL or different item types, create the entries for your SAP ERP document type and item types accordingly. You create a purchase order in SAP ERP. The related goods receipt notification and expected goods receipt are created with document type EGRE and item type EDLV in SAP Extended Warehouse Management (EWM). More Information For more information, see the following: Customizing documentation for Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Map Document Types from ERP System to EWM Customizing documentation for Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Map Item Types from ERP System to EWM

17 Business Add-In (BAdI) for the determination of the document types and items type in Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Interfaces ERP Integration BAdI: ERP-EWM Integration for the Delivery If you want to define document types and item types that differ from those used for the goods receipt notification, see the following: Customizing documentation for Extended Warehouse Management under Goods Receipt Process Expected Goods Receipt Define Document Type Determination for Expected Goods Receipt Customizing documentation for Extended Warehouse Management under Goods Receipt Process Expected Goods Receipt Define Item Type Determination for Expected Goods Receipt Checking Determination of Date Types You can use this procedure to check the configuration of the relevant date types for goods receipt notifications and expected goods receipts and the configuration of delivery date mapping from SAP ERP to SAP Extended Warehouse Management (EWM). Procedure 1. Check the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Expected Goods Receipt Manual Settings Define Document Types for Expected Goods Receipt: Document Type Document Category Date Profile EGRE EGR /SCWM/EGR EGRE GRN /SCWM/GRN 2. Check the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Expected Goods Receipt Manual Settings Define Item Types for Expected Goods Receipt: Item Type Document Category Item Category Date Profile EDLV EGR DLV /SCWM/EGR_DLV EDLV GRN DLV /SCWM/GRN_DLV ETXT EGR TXT - ETXT GRN TXT - A date profile is not required for the ETXT (Text Inbound Delivery) item type since such items are not relevant for warehouse activities and are intended as information only. 3. Check the date profiles as follows: a. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery Processing Dates/Times Define Date Profiles. b. Select a date profile, for example, /SCWM/GRN. c. In the dialog structure, choose Date/Time Types. d. Check the following entry (for example, for profile /SCWM/GRN): Date/Time Type Inactive TDELIVERY - e. Repeat steps 2-4 for each date profile mentioned above. Configuration of Inbound Process With Stock-Specific UoM Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. 17

18 Since the date/time type TDELIVERY is active in profile /SCWM/GRN, the corresponding date and time can be set to the planned date from SAP ERP. Since the TDELIVERY date/time type is also active in profile /SCWM/EGR, the date and time can be completed in the expected goods receipt based on the data in the goods receipt notification. 4. Check the following entries in Customizing for Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Map Date Types from ERP System to EWM: The mapping below is defined to set the planned delivery date to the date of type TDELIVERY in the expected goods receipt. Document Type from ERP Document Type Item Type Start Date End Date WSHDRLFDAT EGRE - - TDELIVERY WSHDRWADAT EGRE EDLV SGOODSRECPT EGOODSRECPT WSHDRWADTI EGRE EDLV - EGOODSRECPT Result You have checked that the planned delivery date from SAP ERP is to be mapped to the planned delivery date in the goods receipt notification. More Information For more information, see the following Customizing documentation for Extended Warehouse Management: Goods Receipt Process Expected Goods Receipt Manual Settings Define Document Types for Expected Goods Receipt Goods Receipt Process Expected Goods Receipt Manual Settings Define Item Types for Expected Goods Receipt Scheduling Background Jobs for Creation of Expected Goods Receipts You use this procedure to schedule the creation of an expected goods receipts in SAP Extended Warehouse Management (EWM). The transaction is scheduled to run on a daily basis. Procedure 1. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery Expected Goods Receipt Generate or Delete Expected Goods Receipt. 2. Create a variant with the following data: ERP Warehouse Number: For example, W01. Business System: For example, ERX_001 In the Special Selection Parameters screen area, select Purchase Order/Deliv. Schedule. In the Program Mode screen area under Technical Settings, select Delete and Create. 3. Schedule this transaction with the variant as a background job that runs on a daily basis. 4.3 Configuration of Inbound Delivery Creation You use this process to configure how the system creates inbound deliveries. The process includes the configuration of the following objects: Inbound delivery notification: Copyright 2015 SAP SE or an SAP affiliate company. Configuration of Inbound Process With Stock-Specific UoM 18 All rights reserved.

19 ... Document in the inbound delivery process containing all relevant logistics data from the initiator of the inbound delivery process. The inbound delivery notification is used to create an inbound delivery. Inbound delivery: Document that contains all data necessary for triggering and monitoring the complete inbound delivery process. This process starts with the receipt of the goods in the yard and ends with the handing over of the goods for final putaway, production, or outbound delivery. Process 1. Checking Document Types and Item Types [page 25] (Optional) 2. Checking Manual Creation of Inbound Deliveries [page 26] (Optional) 3. Checking UoM Handing of Inbound Deliveries [page 28] (Optional) 4. Checking Determination of Document Types and Item Types [page 29] (Optional) 5. Checking Determination of Date Types [page 30] (Optional) 6. Checking Determination of Warehouse Process Types [page 32] (Optional) 7. Configuring Determination of Staging Areas and Goods Movement Bins [page 33] More Information For more information, see SAP Library for SAP Extended Warehouse Management on SAP Help Portal at help.sap.com/ewm under Delivery Processing Documents in Delivery Processing Checking Document Types and Item Types You can use this procedure to check the document types and item types for inbound delivery notifications and inbound deliveries. Procedure 1. Check the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Manual Settings Define Document Types for Inbound Delivery Process: Document Type Document Category INBS IDR Inbound Delivery Notification Document Category Description Description Status Profile Inb. Del. Not. Unpacked Products /SCDL/INB_REQ_STANDARD INBS PDI Inbound Delivery Inb. Del. Unpacked Prod. from Vendor /SCWM/INB_PRD_SIMPLE_UNPACKED 2. Check the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Manual Settings Define Item Types for Inbound Delivery Process: Item Type Document Category Item Category Description IDLS IDR DLV Inb. Del. Item GR from Vendor, Unpacked IDLS PDI DLV Inb. Del. Item GR from Vendor, Unpacked ITXT IDR TXT Text Inbound Delivery ITXT PDI TXT Text Inbound Delivery Configuration of Inbound Process With Stock-Specific UoM Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. 19

20 3. Check the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Define Allowed Item Types in Inbound Delivery Process: Document Type INBS INBS Item Type IDLS ITXT 4. Check the status profiles as follows: a. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery Processing Status Management Define Status Profiles. b. Select a status profile, for example, /SCWM/INB_PRD_SIMPLE_UNPACKED. c. In the dialog structure, choose Status Types. d. Check the following entries: Status Type Short Text Inactive DCO Completion - DEU Planning Putaway - DPT Putaway - For archiving purposes, the inbound delivery needs to have the status value Completion for the status type DCO. Status types DCO and DEU for the inbound deliveries are relevant for putaway planning and for creating putaway warehouse tasks in the Inbound Process Without Packing Information (Manual WT) and the Inbound Process Without Packing Information (Manual GR). 5. Check the following entry in Customizing for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Define Document Type Determination for Inbound Delivery Process: Document Category Document Type Document Category Document Type EGR EGRE PDI INBS If you want to enable an inbound delivery to be created on the basis of an expected goods receipt document, you need to set up the inbound delivery document type as the successor document type to that used for expected goods receipts Checking Manual Creation of Inbound Deliveries You can use this procedure to check the manual creation of inbound deliveries in SAP Extended Warehouse Management (EWM). Procedure 1. Check the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Manual Settings Define Document Types for Inbound Delivery Process: Document Type Document Category Document Category Description Description Create Manually Reference Document Category Profile Copyright 2015 SAP SE or an SAP affiliate company. Configuration of Inbound Process With Stock-Specific UoM 20 All rights reserved.

21 INBS PDI Inbound Delivery Inb. Del. Unpacked Prod. from Vendor Allowed /SCWM/INB_PRD_ASN_SIMPLE 2. Check the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Manual Settings Define Item Types for Inbound Delivery Process: Item Type Document Category Item Category Create Manually IDLS PDI DLV Allowed ITXT PDI TXT Allowed 3. Check reference document type profiles as follows: a. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery Processing Reference Documents Define Reference Document Type Profiles. b. Select the reference document category profile /SCWM/INB_PRD_ASN_SIMPLE. c. In the dialog structure, choose Reference Document Categories. d. Check the following entries: Document Category Inactive ERO - ERP - 4. Check the following entry in Customizing for Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Define Number Ranges for ERP Documents: Number Range Number From Number To Number External When inbound deliveries are created in EWM, the system allocates a number for the SAP ERP delivery that is to be created. This number is stored as a reference document with reference document category ERO in the inbound delivery header. The number is derived from an internal number range. This internal number range needs to be independent of the internal and external number ranges for inbound deliveries in SAP ERP. 5. Check the following entry in Customizing for Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Control Message Processing Dependent on Recipient: Document Type from ERP HU Parameter Internal Number Range Item Number Increment INBS Report HU Data Checking UoM Handling of Inbound Deliveries You can use this procedure to control how units of measure (UoMs) are handled in EWM. If an alternative UoM is available in the ERP inbound delivery item, this UoM is used for the inbound delivery item quantity, if the UoM is an allowed stock specific UoM (SUoM). If the ERP inbound delivery item is created with the base UoM and the preferred UoM in EWM is maintained, this preferred UoM will be used for the EWM inbound delivery item. Procedure 1. Check and, if necessary, create the following entries in Customizing for Extended Warehouse Management under Master Data Product Define Unit of Measurement Attributes: Configuration of Inbound Process With Stock-Specific UoM Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. 21

22 Warehouse Number Unit Stock-Specific UoM W001 EA W001 CAR X W001 PAL 2. Check and, if necessary, create the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Manual Settings Define Item Types for Inbound Delivery Process: Item Type Document Category Item Category IDLS IDR DLV X IDLS PDI DLV X Apply ERP AUoM as SUoM When creating an inbound delivery request from ERP, the system determines the alternative UoM. However, as the UoM can also be changed manually in the inbound delivery in EWM, you must also set the indicator for the document category PDI. More Information For more information, see the following: Customizing documentation for Extended Warehouse Management under Master Data Product Define Unit of Measurement Attributes Customizing documentation for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Manual Settings Define Item Types for Inbound Delivery Process Checking Determination of Document Types and Item Types You can use this procedure to check how the system determines document types and item types for inbound delivery notifications and inbound deliveries. Procedure 1. Check the following entry in Customizing for Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Map Document Types from ERP System to EWM: Document Type from ERP Code for Initiator of a Communication Chain EL - INBS Mapping Delivery Type Document Type If you use a document type other than EL in SAP ERP, create the entries for your SAP ERP document type accordingly. 2. Check the following entries in Customizing for Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Map Item Types from ERP System to EWM: Table 37 Document Type from ERP Item Type from ERP Document Type EL ELN INBS IDLS EL ELTX INBS ITXT Mapping of ERP Item Type Copyright 2015 SAP SE or an SAP affiliate company. Configuration of Inbound Process With Stock-Specific UoM 22 All rights reserved.

23 Result If you use a document type other than EL or different item types, create the entries for your SAP ERP document type and item types accordingly. You have checked how the system determines the document type and item types in EWM during inbound delivery creation either by activating an inbound delivery notification or by manually creating an inbound delivery in EWM. You create an inbound delivery with document type EL and item type ELN in SAP ERP. The inbound delivery is created with document type INBS and item type IDLS in EWM. If a delivery is created manually with the help of an expected goods receipt document with document type EGRE and item type EDLV, the inbound delivery is also created with document type INBS and item type IDLS. More Information For more information, see the following: Customizing documentation for Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Map Document Types from ERP System to EWM Customizing documentation for Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Map Item Types from ERP System to EWM Business Add-In (BAdI) for the determination of the document types and item types in Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Interfaces ERP Integration BAdI: ERP-EWM Integration for the Delivery If you want to define document types and item types that differ from those used for the inbound delivery notification, see the following: Customizing documentation for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Define Document Type Determination for Inbound Delivery Process Customizing documentation for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Define Item Type Determination for Inbound Delivery Process Checking Determination of Date Types You can use this procedure to check the relevant date types for inbound delivery notifications and inbound deliveries, and the configuration of the delivery date mapping from SAP ERP to SAP Extended Warehouse Management (EWM). Procedure 1. Check the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Manual Settings Define Document Types for Inbound Delivery Process: Document Type Document Category Date Profile INBS IDR - INBS PDI - Since a date profile is not assigned to the document type, the system uses the system date profile. 2. Check the Customizing of delivery processing as follows: a. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery Processing Check of Customizing for Delivery Processing. b. Select the Document Type radio button. c. Enter warehouse number W001. Configuration of Inbound Process With Stock-Specific UoM Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved. 23

24 d. Enter document type INBS. e. Choose Execute (F8). f. Check the following entries: Document Type Document Category Profile Type Profile System Profile INBS IDR DT No Customer Profile Assigned INBS PDI DT No Customer Profile Assigned /SCWM/INB_REQ /SCWM/INB_PRD 3. Check the following entries in Customizing for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Manual Settings Define Item Types for Inbound Delivery Process: Item Type Document Category Item Category Date Profile IDLS IDR DLV /SCWM/INB_REQ_DLV IDLS PDI DLV /SCWM/INB_PRD_DLV ITXT IDR TXT - ITXT PDI TXT - A date profile is not required for the ITXT (Text Inbound Delivery) item type since such items are not relevant for warehouse activities and are intended as information only. 4. Check the date profiles as follows: a. In Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery Processing Dates/Times Define Date Profiles. b. Select a date profile, for example, /SCWM/INB_REQ. c. In the dialog structure, choose Date/Time Types. d. Check the following entry: Date/Time Type Inactive TDELIVERY - e. Repeat steps 2-4 for each date profile mentioned above. Since date/time type TDELIVERY is active in profile /SCWM/INB_REQ, the corresponding date and time can be set to the planned delivery date from SAP ERP. Since date/time type TDELIVERY is also active in profile /SCWM/INB_PRD, the date and time can be completed in the inbound delivery based on the data in the inbound delivery notification. 5. Check the following entry in Customizing for Extended Warehouse Management under Interfaces ERP Integration Delivery Processing Map Date Types from ERP System to EWM: The mapping below is defined to set the planned delivery date to the date of type TDELIVERY in the inbound delivery notification. Document Type from ERP Document Type End Date WSHDRLFDAT INBS TDELIVERY Copyright 2015 SAP SE or an SAP affiliate company. Configuration of Inbound Process With Stock-Specific UoM 24 All rights reserved.