Kontakt

Ansicht
Dokumentation

OHIX_DP_VETO_CHECK - Overview

OHIX_DP_VETO_CHECK - Overview

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

If other applications still need the data in the HCM applications that is to be deleted, those applications can block data destruction. This is relevant in the following situations:

  • During the destruction of infotype and subtype data of Personnel Administration and of data on relationships for the person (infotype 1001) in personnel planning.
In an HCM system, you execute the data destruction runs with Archive Administration (SARA) to destroy the data saved in infotypes and subtypes using delete reports.
  • For deletion of personnel numbers
In an HCM system, you run the delete report Destruction of Personnel Numbers in Live Systems (RPUDELPP) to delete personnel numbers along with all the related data.

Problems can arise in both cases if other applications still need to access the data after data destruction has taken place. This can be relevant for the following scenarios:

  • The HCM data is not stored in the application. You access it with a BAPI call, RFC call, or using other local function calls.
  • Only references to the HCM data are stored in the application. You access the data with BAPI calls, RFC calls, or other local function calls.
  • The HCM data is stored in the application and synchronized with ALE.
  • The HCM data is stored in the application and synchronized with a custom function.

To enable other applications to block the destruction of data and personnel numbers, the applications can use function modules to run veto checks. The function modules are called during the data destruction run.

Depending on the scenario, the function modules contain the following information:

  • For data destruction
  • The type of data (infotype/subtype) to be destroyed

  • A list of personnel numbers and the date on which the data for each personnel number is to be destroyed

  • For deletion of personnel numbers
  • The personnel number to be deleted

Based on this information, the function modules can return information on personnel number level about whether the data in the applications is still required. The veto checkbox is selected on personnel number level

If the veto checkbox is selected, the system locks the destruction of infotype and subtype data as well as the deletion of personnel numbers.

To set up the blocking of data in your system, you have to perform the following activities:

  • Creating function modules
You create the function modules needed for the veto checks in the relevant software component of your application. The function modules have to be RFC-enable and are called when running the reports for deleting personnel numbers and for data destruction.
  • Function modules for veto checks when destroying infotype and subtype data

Use the function module Veto Destruction of Infotype and Subtype Data: Template (HRARCH_VETO_DATA_DEL_TEMPLATE) as a template and modify it according to your needs.
  • Function module for veto check when deleting personnel numbers

Use the function module Veto Deletion of Personnel Numbers: Template (HRARCH_VETO_PERNR_DEL_TEMPLATE) as a template and modify it according to your needs.
  • Function module for veto check when deleting relationships for the person

Use the function module Veto Deletion of Relationships for Person: Template (HRARCH_VETO_DATADEL_TEMPLATE) as a template and modify it according to your needs.

  • Make the necessary settings in Customizing
  • Register all applications that participate in the veto check and enter them in the relevant function modules.

  • Activate the applications for the veto check.






CL_GUI_FRONTEND_SERVICES - Frontend Services   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 5051 Date: 20240524 Time: 014417     sap01-206 ( 67 ms )