Ansicht
Dokumentation

DC_DELETION_VETO_CHECK_SIM - Data Controller: Deletion Veto Check Simulation

DC_DELETION_VETO_CHECK_SIM - Data Controller: Deletion Veto Check Simulation

ROGBILLS - Synchronize billing plans   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

Using this program deletion veto checks of data controllers and/or assignments can be simulated. This program does not delete any configuration or other data but is just a simulation.

Integration

Prerequisites

Features

Selection

The program offers the following selections:

  • Call Control
    You can control which Business Add-In (BAdI) implementations of BAdI DC_DELETION_VETO_CHECK are called. By default all BAdI implementations are called. In case you want to simulate a deletion veto check considering only a specific BAdI implementation unselect option All BAdIs and specify a BAdI implementation. You might use the value help to select a certain BAdI implementation.
  • Further Selection Criteria
    By default all data controllers and assignments configured in view cluster DCVC_DC are considered for the deletion veto check simulation. In case you want to perform a deletion veto check simulation only for specific data controllers or assignments, you can use these selection criteria for filtering.

    In case simulation method Data Controller is selected you can filter by specific data controller names. In case simulation method Assignments is selected you can filter by entity types and IDs.

    Note that all filter criteria are combined with or-semantics.

Standard Variants

Output

Deletion veto check results are provided as log messages. The display allows to filter the results (navigation tree):

  • Called BAdI implementations
    Information on all BAdI implementations called during the deletion veto check simulation are listed under this node.
  • Results for each data controller
    For each data controller a node using the data controller name is listed in the navigation tree. This tree item contains all results for the respective data controller:
  • Aggregated result for the data controller telling whether it can be deleted.
  • A separate node for each entity type the data controller has an assignment for. Deletion veto check results for this entity type are grouped under this tree item. For each assignment (combination of entity type and ID) a respective result is listed in the log view.

The log view contains all deletion veto check results in form of messages. For each message the following, additional information is available:

  • Component ID
    The Application Component Hierarchy (ACH) component ID of the BAdI which raised a deletion veto. It has value Not applicable for non-vetos since these have been inferred by this simulation.
  • Log Exists
    An icon is display in case the respective BAdI implementation provides detail information on the deletion veto check. There is no icon in case no detail information is provided.
  • Object Type Name
    Class name of the deletion veto check BAdI implementation. For non-veto information text information is inferred is displayed since these deletion veto check results are inferred by this simulation program.

Activities

Example






ABAP Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4281 Date: 20240520 Time: 081645     sap01-206 ( 70 ms )