Ansicht
Dokumentation
/FRE/DB_DIF_DELETE - DIF Occurrences Deletion
General Data in Customer Master General Data in Customer MasterThis documentation is copyright by SAP AG.
Purpose
This program is used to delete obsolete DIF data. DIF data (Occurrence, Assignment, Delta record) is obsolete if at least one of the following conditions is satisfied:
- The occurrence is not active.
- The validity period ends before the relevant past time horizon.
- The DIF definition no longer exists.
- The occurrence has no assignment.
- Delta records are obsolete.
- Assignment of a Metric DIF is obsolete.
You can delete DIF data that is not obsolete (as defined above) via a DIF user interface (for example, the DIF Workbench).
When a DIF Occurrence is deleted, all related objects (texts, assignments, memos) are also deleted.
Integration
Prerequisites
Features
Selection
- Select option for DIFs (optional)
- Select option for DIF Occurrences (optional)
- Only Inactive: If you set this indicator, the program will delete only inactive DIF Occurrences.
- Occurrences without DIF Definition: If you set this indicator, the program will delete all DIF Occurrences that refer to a nonexistent DIF definition (that is, the definition has been deleted in Customizing after the occurrence was created).
- Occurrences without Assignment: If you set this indicator, the program will delete all DIF Occurrences that do not have assignments.
- Delete Obsolete Delta Records: If you set this indicator, the program will delete all delta records that are no longer relevant for Delta Handling.
- Delete Metric Occurrences: If you set this indicator, the program will delete Metric DIF Occurrences that both:
- Match the other criteria
- For each location product, have another metric DIF Occurrence that starts before or within (<=) the past time horizon
- Delete Metric Occurrence Assignments: If you set this indicator, the program will delete assignments of Metric DIF Occurrences that are assigned other Metric DIF Occurrences starting before or within (<=) the past time Horizon.
- Number of weeks past due records must be kept in the database: The program will only delete obsolete DIF Occurrences older than the specified number of weeks.
- Past Time Horizon: If you set this indicator, the program checks against the relevant forecast horizon defined in location profiles of occurrence assignments before deleting data.
- Inactive without Time Restrictions: If you set this indicator, the program deletes all inactive occurrences matching the DIF and DIF Occurrence selection, regardless of the past time horizon restrictions.
- Simulation: If you set this indicator, the system produces only a simulated deletion. Records will not be deleted from the database. If you do not set the indicator, a warning message asks for confirmation before proceeding with the deletion. If the user responds Noto the confirmation prompt, the system runs a simulation. If the user responds Yes, the system proceeds with the deletion.
Standard Variants
Output
- A summary list of the deleted records:
- Number of DIF Occurrences that have been deleted
- Number of texts that have been deleted
- Number of assignment records that have been deleted
- Number of memos that have been deleted (maximum of 1 per DIF Occurrence)
- A detailed list of the deleted records (optional) with the following information for each DIF Occurrence:
- DIF Occurrence number
- DIF Occurrence text
- Valid-From date
- Valid-To date
- Number of texts deleted per DIF Occurrence
- Number of memos deleted per DIF Occurrence (maximum of 1)
- Number of assignment records deleted per DIF Occurrence
Activities
Selecting the Simulationflag simulates the deletion: the entire process is performed but nothing is actually deleted from the database.
The size of processing packages can be defined for performance optimization.
Example
PERFORM Short Reference Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 5778 Date: 20240423 Time: 081111 sap01-206 ( 70 ms )
