Kontakt

Ansicht
Dokumentation

EHHSS_INC_RDY_ACT - BAdI: Check Readiness for Action

EHHSS_INC_RDY_ACT - BAdI: Check Readiness for Action

RFUMSV00 - Advance Return for Tax on Sales/Purchases   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Environment, Health, and Safety component. You can use this BAdI to perform checks on the following actions:

  • Set status of a data record to Closed
  • Set status of a data record to Void
  • Set status of an incident investigation to Closed
  • Set status of an investigation step to Closed

For each action, a BAdI implementation is delivered that you can use to perform the corresponding check in the standard system. If necessary, you can also deactivate the standard implementations and implement customer-specific checks instead.

Caution

If you implement customer-specific checks, you must ensure that these are complete in terms of data consistency and legal requirements, for example, when generating legal reports based on the incident data.

The BAdI is active in the standard system.

  • BADI_RDY_FOR_ACT_INC_CLOSE
You use this BAdI implementation to perform the following checks before the status of an incident is set to Closed:
  • Check if the Restricted Accessattribute for the incident is set to Yesor No

  • Check if an incident group is assigned

  • Check if the Investigation Requiredattribute is set to Yesor No

  • If an investigation is required, check if the investigation is completed

  • If the incident is an occupational incident, check if at least one involved person has the Injured Personrole

  • If the incident is classified as Release, check if at least one release is assigned

  • Check if the Reporting Required attribute for a release is set to Yesor No

  • Check if risk matrix entries are complete and confirmed

  • If the incident is classified as a notice of violation, check if at least one notice of violation is assigned

  • If the incident has actions assigned, check if all actions that are not recurring are complete

  • Check if all inquiry processes are complete

  • For any injured person, check if the Required in Summary Reportattribute is set to Yesor No

  • For any release of incident, check if the Reporting Requiredattribute is set to Yesor No

  • BADI_RDY_FOR_ACT_NM_CLOSE
You use this BAdI implementation to perform the following checks before the status of a near miss is set to Closed:
  • If the near miss has actions assigned, check if all non-recurring actions are complete

  • Check if all inquiry processes are complete

  • BADI_RDY_FOR_ACT_SO_CLOSE
You use this BAdI implementation to perform the following checks before the status of a safety observation is set to Closed:
  • If the safety observation has actions assigned, check if all non-recurring actions are complete

  • Check if all inquiry processes are complete

  • BADI_RDY_FOR_ACT_INC_VOID / BADI_RDY_FOR_ACT_NM_VOID / BADI_RDY_FOR_ACT_SO_VOID,,
You use these BAdI implementations to implement customer-specific checks that you want to perform before an incident, near miss, or safety observation is set to Void. The implementations do notperform any checks in the standard system.
  • BADI_RDY_FOR_ACT_INV_CLOSE
You use this BAdI implementation to perform the following checks before the status of an investigation is set to Closed:
  • Check if the Investigation Requiredattribute is set to Yesor No

  • Check if an investigation lead is assigned

  • Check if a major root cause is selected

  • Check if all investigation steps are complete (status Closed, Void, or Completed)

  • BADI_RDY_FOR_ACT_STEP_CLOSE
You use this BAdI implementation to perform the following check before the status of an investigation step is set to Closed:
  • For investigation steps with the step category EHHSS_ST_CAT_ROOTCAUS, check if all assigned actions are complete (status Closed, Void, or Completed).

  • BADI_RDY_FOR_ACT_CHANGE_CAT

You use this BAdI implementation to perform the following checks before changing the category of an incident:

  • Check if incident status is set to Void or Closed

  • Check if incident investigation status is In Process or Reopened

  • Check if HR absence worklflow step is New or In Process

  • Check if incident inquiry status is New or In Process

  • Check if incident report status is New or In Process

  • Check if incident approval task is New or In Process

  • Check if a reopened incident worklflow instance is In Process, and the process status is not Initial

You can use the following filter values when defining customer-specific BAdI implementations:

  • INCIDENT_CATEGORY
  • 001 ,,Incident

  • 002,,Near Miss

  • 003,,Safety Observation

  • ACTION_NAME
  • SET_VOID_ROOT

  • SET_CLOSED_ROOT

  • INVESTIG_RESULT_SET_CLOSED

  • NODE_NAME
You can use all existing node names from business object EHHSS_INCIDENT. To display the nodes of this business object, use transaction /BOBF/CUST_UI or execute the search help EHFND_ELM_BO_NODE_NAME in transaction SE11 in test mode using BO_NAME = EHHSS_INCIDENT.

You want to define a check that is only executed if:

  • The incident is a Near Miss
  • The action that is performed to set the status to Closed
  • The BASIC_INFO_ALL node is processed.

To do this, set the following filter values:

  • INCIDENT_CATEGORY = 002 (Near Miss)
  • ACTION_NAME = SET_CLOSED_ROOT
  • NODE_NAME = BASIC_INFO_ALL





RFUMSV00 - Advance Return for Tax on Sales/Purchases   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 11313 Date: 20240523 Time: 182137     sap01-206 ( 86 ms )