Kontakt

Ansicht
Dokumentation

RCSARCH2 - Report for archiving BOMs, deletion program

RCSARCH2 - Report for archiving BOMs, deletion program

BAL Application Log Documentation   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Title

BOM reorganisation deletion run

Purpose

This program enables you to delete the BOM data that you previously archived, from the database.

Features

The system imports all data records from the archive and checks the data record of each individual alternative BOM for how up-to-date and how complete it is:

  • If a data record from the database was changed, deleted or added after the archiving run, which has resulted in differences between the data in the database and data in the archive, then the system flags all data records of the corresponding alternative BOM as not for deletion.
  • The data records that have therefore only been archived because other data records are assigned to them, are flagged as not for deletion.
Therefore, a BOM header that is still valid and is archived, is flagged as not for deletion, because an item assigned to it is deleted.
  • The system checks whether other data records have dependencies. Therefore, for example, a STZU-record is only allowed to be deleted with the last alternative. To determine the dependencies, the system uses the implicit data model of the BOM organisation as the basis.

Consequently the system deletes all remaining archived data records as well as the data records the the dependent objects:

  • Long texts
  • Change documents
  • Classification data

Selection

You can specify that the deletion program is only started in the test run. In the test run, the checks for how complete and how up-to-date the archived data is, take place as in the normal run. However, no data records are deleted from the database.

Output

At the end of the deletion run, the system generates a spool list which produces a summary of the expired processes. The list is structured in two blocks:

  • Alternative BOMs not deleted due to an incorrect archive status (indicated by |@0W@)

  • deleted alternative BOMs (indicated by |@11@)

Both blocks are made up of a summary and a detailed list of database entries:

  • In the summary you can find the number of affected data records for each database table.
  • In the detail list the individual data records are displayed per alternative BOM.

If more references exist for a data record, the system does not physically delete the data record from the database, only the references.






PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3035 Date: 20240520 Time: 114036     sap01-206 ( 49 ms )