5.8.1 /SCWM/DOOR_SRACT, /SCWM/TDOOR: Door Activities within SAP EWM
A door is a location in the warehouse where the goods arrive at or leave the warehouse. The door is an organizational unit that you assign to the warehouse number.
5.8.1.1 Avoidance Cannot be used 5.8.1.2 Summarization Cannot be used 5.8.1.3 Deletion Cannot be used 5.8.1.4 Archiving
The relevant archiving object for door activities is WME_DOOR. As prerequisites for archiving, please consider the following:
· Door activity must be completed. · Residence time must be reached.
· All the assigned transportation unit activities for the door activity must be archived and deleted from the database before the door activity is archived.
Caution: Since the write program cannot restrict the number of processed records, we advise caution when scheduling the pre-processing report. Avoid creating an "overload" or "too long runtime" situation by dividing pre-processing into manageable chunks. Schedule the write program after the pre-processing run and before the next pre-processing run.
See SAP Notes:
· 1669731 (SCMEWM 510 – 712): Archiving in S&R
· 1814941 (SCMEWM 510 – 900): WME_DOOR deletion report does not delete all entries
5.8.2 /SCWM/TU_SR_ACT, /SCWM/TU_STATUS: Transportation Units Within SAP EWM A transportation unit is the smallest loadable unit of a vehicle that is used to transport goods. The transportation unit (TU) can be a fixed part of the vehicle. You map transportation units as handling units (HUs) and assign packaging materials to them. By linking these packaging materials to means of transport, you define construction rules for your vehicles. In this way you define, for example, how many transportation units a vehicle is supposed to have and the order in which they are to be arranged.
5.8.2.1 Avoidance Cannot be used
5.8.2.2 Summarization Cannot be used
Cannot be used
5.8.2.4 Archiving
You can use archiving to remove data records for shipping and receiving activities from the database that are no longer required in the system. Use the archiving object WME_TU for archiving and deleting shipping and receiving activities for transportation units (TU activities). Each TU is connected to the stock information via a virtual handling unit. The system deletes this HU as soon as the TU has been deleted. The system does not archive the HU information.
TU activities must have the status Archivable in order for the system to be able to archive them. The system flags a TU activity with the status Archivable if the following conditions have been met:
· The activity end was at least 60 days ago (fixed value).
· No stock is still assigned to the TU activity in the Logistics Inventory Management Engine (LIME). See SAP Note:
· 1570600 (SCMEWM 510 – 701): There is no BAdI for archiving object WME_TU
5.8.3 /SCWM/WHO: Warehouse Order Processing Within SAP EWM
Extended Warehouse Management (SAP EWM) offers flexible, automated support for processing various goods movements and for managing stocks in your warehouse complex. The system supports scheduled and efficient processing of all logistics processes within your warehouse.
A warehouse order is a document that represents an executable work package that a warehouse employee should perform at a specific time. The warehouse order consists of warehouse tasks or physical inventory items. 5.8.3.1 Avoidance Cannot be used 5.8.3.2 Summarization Cannot be used 5.8.3.3 Deletion Cannot be used 5.8.3.4 Archiving
Warehouse orders saved in SAP EWM a certain number of days ago (residence time) can be archived. Warehouse orders can be archived simultaneously for multiple warehouse numbers by archiving object WME_WO. To determine whether a warehouse order can be archived, analyze table /SCWM/WHO. Please note the following prerequisites for archiving:
· The related warehouse tasks must have been archived with WME_TO. · The defined residence time must have been reached.
· The warehouse order must have the status Canceled or Confirmed. See SAP Note:
5.8.4 /SCWM/WAVEITM, /SCWM/WAVEHDR: Wave Management within SAP EWM
A wave is a grouping of warehouse request items that is used to control warehouse activities, for example, picking or posting changes.
These groupings are then processed together in subsequent processes, for example, the transfer of all warehouse request items assigned to a wave at a certain point in time to warehouse task creation. The warehouse tasks created are then forwarded to warehouse order creation.
Extended Warehouse Management can combine warehouse request items and split items into waves on the basis of criteria such as activity area, route, or product.
Waves can be created automatically or manually with the use of existing wave templates.
5.8.4.1 Avoidance Cannot be used 5.8.4.2 Summarization Cannot be used 5.8.4.3 Deletion Cannot be used 5.8.4.4 Archiving
Archiving object WME_WAVE is used to archive and delete waves. A wave entry can be archived if it has the relevant status and has exceeded the residence time. The default value is 200 days. To determine the status of the wave entry, evaluate header table SCWM/WAVEHDR and field STATUS. Please consider the following prerequisites for archiving:
· The status of the wave header must be Released, Released with Defects, or Transferred to Subsystem.
· Read from table /SCWM/WAVEHDR and field STATUS (values R, E, or C).
· Residence time reached: Read from table /SCWM/WAVEHDR and field RELEASED_AT. See SAP Notes:
· 1517747 (SCMEWM 510 – 701): Entries are not deleted from /SCWM/WAVEITM after
· 1586212 (SCMEWM 510 – 701): No archiving BAdI for WME_WAVE, WME_TO and WME_WO · 1699322 (SCMEWM 510 – 712): Wrong archive statistics and log information for WME_WAVE