You can delete obsolete planned shipping handling units (PSHUs) by using the transaction Delete Planned Shipping Handling Units
.
Recommendation
We recommend that you delete obsolete PSHUs regularly.
Note
Using the transaction Delete Planned Shipping Handling Units
, you can only delete a PSHU if all its related outbound delivery order items fulfill the selection criteria. If you want to delete a PSHU that contains delivery items not fulfilling your selection criteria, you have to use the transaction Cartonization Planning for Outbound Delivery Orders
or Cartonization Planning for Waves
in execution mode Deletion of PSHUs
. These transactions also offer further criteria to select PSHUs for deletion. For more information, see Cartonization Planning for Outbound Delivery Orders or Cartonization Planning for Waves.
Note
You can also delete PSHUs before wave creation with the report /SCWM/R_WAVE_PLAN_BACKGROUND
. To do so, select the Delete Planned Shipping HUs
checkbox in the report.
In transaction Delete Planned Shipping Handling Units
, you can select PSHUs for deletion by the following criteria:
Organizational Data
You have to select the warehouse number in which you want to delete PSHUs.
Selection of Planned Shipping Handling Units
You have to select PSHUs with or without related outbound delivery orders.
With Outbound Delivery Orders
You can select PSHUs by the status of their related outbound delivery orders. You can use one of the following options:
Goods Issue Status
You can select PSHUs by specifying the minimum number of days since goods issue posting for their related outbound delivery order items. The default number of days since goods issue posting is 30.
Goods Issue Status
You can select PSHUs by specifying the date range of goods issue posting for their related outbound delivery order items.
Archiving Status
You can select PSHUs whose related outbound delivery orders have been already marked for archiving.
Without Outbound Delivery Orders
You can select PSHUs whose related outbound delivery orders have already been deleted.
You can make the following technical settings:
Package Size for Processing
To avoid errors due to maximum runtime and also memory or lock overflows, the system can process data in packages. You can define the package size by defining the maximum number of the highest-level PSHUs in a package. The default package size is 5000.
The system processes each package independently. If the processing of one package stops due to an error, this does not stop the execution of the transaction as the system can process the remaining packages.
Simulation
If you execute the transaction in simulation mode, the system selects PSHUs without actually deleting them and displays the result in the application log.
The system stores the results of the execution in the application log, which contains information about the selected PSHUs as well as about their related outbound delivery orders if any.
To delete obsolete PSHUs, on the SAP Easy Access
screen, choose or schedule the report /SCWM/R_CAP_DELETE
.
Recommendation
To check your selection of PSHUs, we recommend that you first run the report in simulation mode.
You use cartonization planning in your outbound process. You post goods issue for all items of an outbound delivery order on the same day or latest one day later. Once you have posted the goods issue, you do not need the PSHUs any longer. However, for monitoring reasons you want to keep them for two weeks. After two weeks you want to delete them so that the database for the PSHUs does not contain obsolete entries. To delete the obsolete PSHUs regularly, you schedule the report /SCWM/R_CAP_DELETE
as a background job. In the report, you enter the warehouse number and the following selection criteria:
You select With Outbound Delivery Orders
.
You select Goods Issue Status
and enter 14 as the minimum number of days since goods issue posting.
Since you expect a large amount of PSHUs to be deleted, you use the standard package size.