Archiving in Extended Warehouse Management (SCM-

EWM):
You can archive the following data in Extended Warehouse Management (EWM):

EWM Areas Document Category Archiving Object

Archiving in Delivery Processing Internal Warehouse Requests (Inbound Delivery) DLV_INB
Internal Warehouse Requests DLV_OUT
Warehouse Requests from External Systems DLV_REQ
Production Material Requests DLV_PROD
Archiving in Quality Management QIE Inspection Documents QIE_INSP
Archiving in Shipping and Receiving Door Activities WME_DOOR
Vehicle Activities WME_VEH
TU Activities WME_TU
ESI Manifests EWM_ESI_MF
ESI Parcels EWM_ESI_PA
Archiving for Value-Added Services Value-Added Service Orders (VAS Orders) WME_VAS
Archiving in Wave Management Waves WME_WAVE
Archiving in Warehouse Order Processing Telegram Flows WME_MFS
Relevant Resource Data WME_RSRC
Warehouse Tasks WME_TO
Warehouse Orders WME_WO
Handling Units WME_HU
Archiving of Warehouse Billing Warehouse Billing Measurements EWM_WBM
Measurements

Business Partner End of Purpose (EoP) Check in SAP

EWM:
SAP Extended Warehouse Management (SAP EWM) provides an end of purpose (EoP) check to determine whether business partner data is still relevant for
business activities in the application or can be blocked.
 Prerequisites

You have activated the business function ILM-Based Deletion of Business Partner Data (BUPA_ILM_BF) for required ILM Objects.

EoP Check Implementation

SAP EWM provides the following functionality for the EoP check of the business partner:

• The application searches for any dependent data for the business partner in relevant SAP EWM tables.

If dependent data exists and the data is still required for business activities (that is, EoP has not been reached and the retention time for the document referring to the
business partner is not over), the system does not block the business partner.

• The end of business is reached when the retention time of all documents referring to the business partner has been reached.

Typically, SAP EWM stores data in table BUTSORT for each document that is closed. This data contains the start of retention time for the corresponding business
partner in the assigned application rule variant. Depending on the retention times of the ILM policies that are maintained for the referring documents, SAP EWM
determines for each type of document if data for the concerned business partner exists and whether the retention time has already passed. If the EoP check finds
open documents referring to the business partner, the EoP has not been reached.

• The application returns the following time reference that represents the end of business date to the EoP check as Start of Retention Time (SoRT). This means that
the following applies:

o SAP EWM determines the next check date, which is the earliest date that the system needs to check whether the business partner is still in use.

For example, if there is a warehouse order for the business partner with completion date 2017.10.27 and the retention time is 1 year, the next check date is
2018.10.27.

o SAP EWM determines the completion time stamp as the start of retention time, for example, the CONFIRMED_AT time stamp from table /SCWM/ORDIM_C or
/SCWM/WHO.

• The EoP check for SAP EWM supports the use of application rule variants based on ILM rule groups: If you want to define differing residence and retention periods
for business partner data depending on application-specific condition fields, you can define application rule variants in Customizing for Cross-Application
Components under Data Protection Blocking and Unblocking of Data Business Partner Define and Store Application Rule Variants for EoP Check.
 In this Customizing activity, you assign the application rule variants to ILM rule groups that you have created in transaction IRM_CUST_CSS (Information
Retention Manager - Calling Customer-Specific Settings). To determine the retention rules, the ILM rule groups must also be entered in the corresponding
retention rules for the ILM objects of SAP EWM in transaction IRMPOL (ILM Policies).

• The EoP check for SAP EWM calculates the end of residence time (representing the EoP) based on residence periods maintained for ILM object CA_BUPA that is
active for audit area BUPA_DP for application EWM and the existing rule variants.

• SAP EWM uses transparent table BUTSORT to collect SoRT information upfront.

Initial Load Reports

The EoP check for SAP EWM offers the following initial load report:

Report Name Use To Be Used When Affected Data

/SCWM/DPP_CREATE_SORT_EWM Use this report to initially fill tableThis report can be used more than
This report reads data from the
(SoRT Data Creation for Existing EWM BUTSORT with SoRT information
once. archive and the database and
Documents) for all available documents and writes the latest start of retention
business partners in SAP EWM date to table BUTSORT for every
documents. You also use this business partner and application
report after retention periods are rule variant.
changed.

The EoP check for SAP Dock Appointment Scheduling offers the following initial load report:

Report Name Use To Be Used When Affected Data

/SCWM/RDPP_CREATE_SORT_DAS Use this report to initially fill or This report can be used more than
This report reads data from the
(Create Start of Retention Time for create SoRT information for table
once. database and writes the start of
Existing Appointment Documents) BUTSORT for existing dock retention time to table
appointment documents that refer BUTSORT.
to business partners (carriers).
Report Name Use To Be Used When Affected Data

You also use this report to fill

table BUTSORT if you change
the retention period by changing
the rule group or application rule
variant.

Archiving in Delivery Processing (SCM-ECT-DLP):

You can use archiving to remove data records for warehouse requests that are no longer required in the system from the database.

Delivery Processing uses the SAP NetWeaver data archiving.

Prerequisites

The documents to be archived must have the status Completed and the retention period of the documents must have expired.

The archiving objects provide a series of actions that you can use in the archive administration (transaction SARA) for the data records in Delivery Processing.

Report /SCDL/BO_ARCHIVE

You use this report for all documents whose expiry date has been reached to change their status from Completed to To Be Archived. You define the retention
period of the documents via the document type. In the selection screen of the report, you can select the documents to be archived via the selection criteria document
type and document identification. You can also define whether the detailed log is to be displayed on the user interface after running the report or whether it is to be
saved. You can also simulate a program run. You can schedule this report to run in the background or you can start it manually.
 Activities

Preparing Documents for Archiving

Before archiving, you have to change the status of all the documents to be archived whose expiry date has been exceeded from Completed to To Be Archived.

1. Choose transaction /SCDL/BO_ARCHIVE.

2. In the selection screen, enter the document type and the document identification of the documents that you want to archive.

3. Choose Execute.

Note
You can also schedule this report to run in the background.