Ansicht
Dokumentation

/SAPAPO/PDEM_DELETE - eSPP Capture Demand Data Deletion

/SAPAPO/PDEM_DELETE - eSPP Capture Demand Data Deletion

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You use this report to delete CPD relevant records from the demand history, raw demand and the staging tables for SD demand, STO demand and external demand.

The data is stored in, and thus deleted from the following database tables:

Radio Button Database table
Demand History /SAPAPO/DEMHIS
Demand Future BOD /SAPAPO/DEMBOD
Raw Demand /SAPAPO/RAWDEM
SD Demand /SAPAPO/SDDEM
STO Demand /SAPAPO/STODEM
External Demand /SAPAPO/EXTDEM

You can use this report for housekeeping, for example to delete data records that are older than a certain number of months and are no longer needed for eSPP-relevant calculations. Therefore, you could delete all demand data that is older than e.g. 4 years (48 months).

You can also use this report to delete single records, for example when an inconsistency has occurred.

External Demand

If you have accidently deleted data from the demand history and/or the Demand Future BOD, it is possible to recalculate and restore this data from the existing raw demand by the execution of the Demand Alignment Service for the specific product(s).

Data from the other tables cannot be restored!

Integration

Prerequisites

Features

This report provides a variety of different features.

Selection

There are several selection options available. Some of these selection options are only available for certain tables.

You can delete the following data records:

  • data records that are older than a certain number of months
  • data records that belong to a certain Product
  • data records that belong to a certain Order Number
  • data records that belong to a certain Item Number
  • data records that belong to a certain Schedule Line Number
  • data records that have a certain Shipping Date

These selection criteria can be combined in all possible ways.

For the selection parameter Del. older that Num. of Months which exists for the demand history and the Demand Future BOD the following logic applies:

Starting from the date of execution, the number of months is used to calculate a date in the past. The date in the past is converted into a Period depending on the actual Forecast Periodicity setup (Day/Month/Year). All demand history older than this period is removed from the database table(s).

The report also can be run in Test Mode(No Data Update) which can be used to check how many data records will be deleted. In test mode no changes will be made to the database.

It is highly recommended to execute the report in simulation mode first, before running it in execution mode.

Standard Variants

Output

When executing the report (in execution and/or simulation mode) the report will put out the total amount of deleted (or to be deleted) entries in the Logfiles.

If the Detailed Logging option is checked, the report will additionally provide a summary of how many entries were deleted for a certain product.

Additional Information

Moreover, in case you have set the demand history data storage as Virtual you will also have the option Delete all data to reset the demand history data completely.

This option is only available for the demand history and the Demand Future BOD.

The Delete all data option has to be handled with care.

In case you changed the demand history data storage from Persisted to Virtual (see Customizing in Transaction ‫/SAPAPO/PDEMCUST‬, Parameter DBDEMHIS = V) it is advisable to clear the demand history completely, as the data on the database is no longer up to date then. For further explanation regarding the virtual/persisted demand history see SAP Note 2912255 eSPP Capture and Manage Demand.

If the report deletes all raw demand entries of a certain product, the report will also delete all entries of the demand history and Demand Future BOD where this product is the original product.

In general, it is recommended to execute the alignment service for the specific product(s) after a raw demand deletion.

Activities

Example






RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 6238 Date: 20240426 Time: 232445     sap01-206 ( 74 ms )