End Of Purpose (EoP) Checks for Business Partners used in Incident Management
Use
Incident management provides an end of purpose (EoP) check to determine whether business partner data is still relevant for business activities in the application or can be blocked.
Prerequisites
You have activated the business function ILM-Based Deletion of Business Partner Data (BUPA_ILM_BF).
Technical Details
ILM Objects
-
EHHSS_INC (Incidents)
EoP Checks
|
Application Name |
End of Purpose Check |
Further Information |
|---|---|---|
|
EHS_INC |
EHHSS_INC_EOP_CHECK_BP |
The check determines whether the business partner is used in incidents:
|
Data Used for EoP Checks
Incident management provides the following functionality for the EoP check of the business partner:
The EoP check EHHSS_INC_EOP_CHECK_BP searches for and determines the following data with relation to business partners, employees, or applicants that can be referred in the incidents as follows:
-
Persons or parties involved in incidents (for example, witness).
-
Injured persons in incidents.
-
First physician in incidents.
-
Further treatment provider in incidents.
-
Hospital information (only reference to business partner possible) in incidents.
-
Investigation lead and investigation step executer as part of the incident investigation process.
-
Persons responsible, implementers, and approvers of incident related tasks (actions).
End of Business Conditions
The end of business is reached when the incidents have the status Closed or Void.
For incidents that are in status other than Closed or Void, the end of business has not been reached yet.
Start of Retention Time
The application returns the latest date of status change (Closed or Void) of the incident as time reference that represents the end of business date to the EoP check as Start of Retention Time (SoRT).
Rule Variants for EoP Checks
The EoP check for incident management supports the use of application rule variants based on ILM rule groups: If you want to define differing residence and retention periods for business partner data depending on application-specific condition fields, you can define application rule variants in Customizing for .
In this Customizing activity, you assign the application rule variants to ILM rule groups that you have previously created in transaction IRM_CUST_CSS (Information Retention Manager - Calling Customer-Specific Settings). To determine the retention rules, the ILM rule groups must also be entered in the corresponding retention rules for the ILM objects of incident management in transaction IRMPOL (ILM Policies).
The EoP check for incident management calculates the end of residence time (representing the EoP) based on the residence periods maintained for ILM object CA_BUPA that is active for audit area BUPA_DP for the application name EHS_INC (EHS Incident Management Business Partners) and the existing rule variants.
Handling of Archived Data
-
The application collects SoRT information with relation to business partners during the archiving runs of the following archiving object:
-
EHHSS_INC (Incidents)
For archivable incidents, relevant SoRT data is collected and stored for business partners in incidents. The latest change date of the incident status (Closed or Void) is stored as start of retention date.
-
See Also
For more information, see-
For more information about data protection in component extension for SAP EHS Management, see http://help.sap.com/EHS-comp. Open the Security Guide and go to Data Protection.
-
For more information about data protection in SAP ERP, see http://help.sap.com/ERP. Select your release and open the SAP Library documentation. Go to .
-
For more information about SAP Information Lifecycle Management, see http://help.sap.com/ERP. Select your release and open the SAP Library documentation. Go to .
-
For more information, about Customizing settings, see the Customizing for Data Protection under Cross-Application Components.

