Tuesday, September 6, 2016

SAP EWM Questions
Q. What are the Organizational elements of SAP EWM?
Ans> 1. Warehouse number - four character cod that represents single warehouse. 2. Storage type - represents individual physical area e.g. high rack, bulk storage, fixed bin etc 3. Storage section - it is subdivision of Storage sections 4. Storage bin 5. Activity Area - Logical grouping of Storage bin
Q. What are the inbound processes that are handled in SAP EWM?
Ans> Transportation Unit Processing, Goods receipt management, inbound quality management and internal routing.
Q. What are the storage and operations processes in SAP EWM?
Ans> Physical Inventory, Replenishment and Rearrangement and Kit-to-stock management
Q. What are the outbound processes in SAP EWM?
Ans> Outbound planning, Picking optimization, packing, staging and load management.
Q. What is Resource and labor management?
Ans> Resource management is the integration of: Warehouse resources, people and material handling equipment such that proper resources are assigned to the warehouse task.
Following are the advantages of Resource management: Planning of labor time, visualization of warehouse activities, comparison of performance of warehouse employees.
Q. What is Cross docking?
Ans> Cross docking is the process of transfer of goods directly from goods receipt to goods issue without storing them. It can be Planned (Transportation cross docking) and unplanned.
Q. What is Yard Management?
Ans> Yard management is the process of monitoring and managing Transportation units (TU). This includes the TUs
Q. What is the document flow between ERP and EWM
Ans> Purchase order created in ECC >> Inbound Delivery doc is created in ECC >> Inbound Delivery notification is replicated automatically in EWM >> Inbound delivery document is created in EWM
Q. How is ECC and EWM integrated in outbound delivery process?
Ans> Sales order created in ECC>> Outbound delivery doc created in ECC >> Outbound delivery request created in EWM>> Outbound delivery order created in EWM >> Outbound delivery doc created in EWM
Q. What is Warehouse request document?
Ans> Warehouse request document is the basis on which the warehouse activities can be carried out. Following are the warehouse documents in each process: 1. Picking (goods issue) - Outbound delivery request document is warehouse request document. 2. Putaway (goods receipt) - inbound delivery document is warehouse request document 3. Posting changes - Posting change document is the warehouse document
Q. What is document flow in EWM?
Ans> Warehouse request document > Determine warehouse process type (determines direction whether Putaway or Picking) > Create Warehouse Task for process > Assignment of warehouse task to Warehouse orders
Q. What is Warehouse task? Give example of warehouse task in each of the business process.
Ans> Warehouse task is the set of activities that are needed to be executed to complete a warehouse process. Warehouse task depends upon the warehouse process type. It can be created manually or automatically depending upon customization. Warehouse task can be created with or without reference to warehouse request document e.g. internal goods movement. Following are the warehouse task in each of the business process:
- Putaway task moves the product from source location to destination putaway bin. - Picking Task directs the removal of a product for source to destination location - Posting change task used to reassign the quantity of a product to different plant and stock type. - internal goods movement task to move product from bin-to-bin - Goods receipt posting task represents posting of GRN in ECC - Goods issue posting task represents posting of Goods issue in ECC
Q. What are the different types of Warehouse task?
Ans> There are two types of warehouse taks:
1. Product warehouse task - contains the information required to execute the physical transfer of products into the warehouse, out of warehouse or withing warehouse, from one storage bin to another.
2. Handling unit warehouse task - contains the information for goods movement of a product in a handling unit from source location to destination location.
Q. How is Warehouse number determined in EWM and ECC
Ans> 1. One the basis of the Plant and Storage location Warehouse number (intermediate warehouse) is determined in ECC
2. Intermediate warehouse in ECC is mapped to Warehouse number in EWM (This mapping is stored in customizing of interface settings in ERP)
Distribution model is created in ECC and EWM such that delivery data is transferred to and from EWM.
Q. What are the steps of ECC and EWM integration?
Ans> following are the steps of integration of SAP EWM and ECC
1. Assign Warehouse number to Plant - Storage location number in ECC
2. Enable EWM process for intermediate warehouse in ECC
3. Generate Distribution model in ECC
4. Assign Warehouse number to warehouse number of Decentralize system in ECC
5. Setup of confirmation control key in ECC
Following settings are needed to be maintained in EWM System
1. Business system integration
2. Map ERP Business system and warehouse to EWM warehouse
Q. How to setup Delivery document integration?
Ans> Process of delivery document integration is as follows
1. Delivery document is created in ERP.
2. Warehouse request is created in EWM
3. Delivery split may also take place in ECC
4. Execute delivery as per the split of delivery
Following mapping should be configured:
1. Mapping of ERP document type to EWM document type
2. Mapping of ERP Item category to EWM Item type mapping
Q. What is the document structure in EWM?
Ans> A document in EWM consist of Header and Item details.
Document Header - Document header is a combination of Document type and Document category codes. EWM document type classifies a document represents Primary business process and Document category code represents various documents within a business process.
Document Item Details - Item details consists of Item categories and Item types. Delivery item type classify the items for a document type for a business process.
Q. What is Post Processing Framework (PPF)?
Ans> PPF is a component that links the subsequent Action profile to document type.