Archiving object WME_TU for archiving and deleting shipping and receiving activities for transportation units (TU activities).
Extended Warehouse Management (EWM) uses the archiving object WME_TU to archive data from the following tables:
Table |
Description |
Explanation |
/SCWM/TU_DLV |
Assignment of Deliveries and HUs to Transportation Units |
This database table shows the relationship between the TU activity and its contents (deliveries). |
/SCWM/TU_DOOR |
Assignment of Transportation Units to Doors |
This database table contains the relationships between TU activities and door activities. |
/SCWM/TU_IDENT |
Table with TU Identifications |
This database table contains identifiers. Each TU activity can be mapped externally by multiple identifiers. |
/SCWM/TUNIT |
Transportation Unit |
This database table contains the data for the transportation unit (TU) itself. |
/SCWM/TUNIT_SEAL |
Seal for Transportation Units |
This database table contains seal information for each TU activity. |
/SCWM/TU_SR_ACT |
S&R Activity of a Transportation Unit |
This database table contains start dates/times and end dates/times. Each TU activity is defined by its start date/time and end date/time. |
/SCWM/TU_STATUS |
Status of Transportation Unit Activities |
This database table contains statuses. The progress of each individual TU activity is described by various statuses. |
/SCWM/TU_VEH |
Assignment of Transportation Units to Vehicles |
This database table contains one or more vehicle activities with which a TU activity can be linked. |
Each TU is connected to the stock information via a virtual handling unit (HU). The system deletes this HU as soon as the TU has been deleted. The system does not archive the HU information.
The following programs are available for WME_TU:
Program |
Function |
WME_ARCH_TU_MARK |
Mark only (preprocessing program) |
WME_ARCH_TU_WRITE |
Write only |
WME_ARCH_TU_MARK_AND_WRITE |
Mark and write |
WME_ARCH_TU_DELETE |
Delete |
WME_ARCH_TU_READ |
Read and display |
Before the system writes TU activities to archive files, it changes the status from Archivable to Archived. You can no longer process archived TU activities. The system archives the following data for each TU activity:
● Relevant TU data
● All status entries
● All identifiers
● All seal information
● All assignments to door activities
● All assignments to vehicle activities
● All assignments to deliveries
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 Logistics Inventory Management Engine (LIME).
After writing the archive files, the system performs a test run where it reads the data in the archive files and compares it with the data in the database. If it does not find any differences, the system deletes the database data.
Although the system always archives TU master data (/SCWM/TUNIT), it only deletes it from the database if the following condition has been met:
■ No other TU activities still exist.
When the system deletes the TU itself, the relevant HU information is also deleted automatically.
The system uses the selection options to search for suitable activity data in the data sources. The following table shows the selection criteria available:
Text |
Table |
Field |
Internal TU Number |
/SCWM/TU_SR_ACT |
TU_NUM |
External TU Number |
/SCWM/TUNIT |
TU_NUM_EXT |
License Plate Number |
/SCWM/TU_SR_ACT |
LIC_PLATE |
Transportation Service Provider |
/SCWM/TU_SR_ACT |
TSP_CURR |
Actual Activity Start |
/SCWM/TU_SR_ACT |
START_ACTUAL |
Actual Activity End |
/SCWM/TU_SR_ACT |
END_ACTUAL |
You can choose the following data sources:
● Database
● Archive file chosen manually
● Archive Information System (AS)
If you choose all three data sources and the system has archived a TU activity multiple times without deleting it, the system searches through the data sources in the following order:
...
1. The system reads the TU activity from the database.
2. The system reads the TU activity from the archive file chosen manually, as appropriate, and overwrites the version found previously.
3. The system uses the AS to search for the TU activity in multiple archive files, reads it, and overwrites the version found previously.
The last source that is found determines which data is displayed (in particular for the TU master data).
A list of the TU activities found is displayed. The cursor position determines the current TU activity. You can use the Details pushbutton to display this current TU activity as a form.
Only fields for which you have defined values are displayed in this form. The system suppresses fields with initial field values.
You can display the following dependent data:
● Data record with general TU data (TU Master Data pushbutton)
● Table with the relevant status entries (Status pushbutton)
● Table with the external identifiers assigned to the TU activity (Identifiers pushbutton)
● Table with the seal information assigned to the TU activity (Seal pushbutton)
● Table with the door activities assigned to the TU activity (TU <-> Door pushbutton)
● Table with the deliveries assigned to the TU activity (TU <-> Delivery pushbutton)
● Assignments of the TU activity to one or more vehicle activities (TU <-> Vehicle pushbutton)
You can use the TU Activities pushbutton to return to the activity table.
If you double-click the individual pushbuttons, you can display all the data records read, irrespective of the current TU activity. You can use the Details pushbutton to display the data in the format of a form.
As the selection criterion, you can specify the number of days that must have passed since the TU activities were completed (default value: 60 days).
You can use the following field catalog and archive information structure to access archived TU activities using the Archive Information System:
● Field catalog SAP_WME_TU
● Archive information structure SAP_WME_TU