Ansicht
Dokumentation

EHHSS_RAS_WF_WFS - Adapt Workflows for Health and Safety Management

BAL_S_LOG - Application Log: Log header data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

In this activity, you can learn about the organizational activities for adapting the workflows of SAP Business Workflow to suit your customer-specific processes. The process foundation of the Environment, Health, and Safetycomponent makes integration with workflows possible. You can adapt workflows to your processes in the following ways:

• Change the workflow template

• Add steps within a process

• Call further logic from a workflow task (process step)

• You have specified processes for the health and safety (HSS) component in the Customizing activity Specify Process Definitions under Foundation for EHS.

• You have checked the processes by implementing the Customizing activity List Configured Processes under Foundation for EHS.

The following workflow templates are delivered with the corresponding PCO class/triggering event:

Workflow Template	Class Name/Triggering Event
00600060 - EHHSS_RRQ	CL_EHHSS_PCO_RAS_REQUEST
00600072 - EHHSS_RAS_RP	CL_EHHSS_PCO_RAS_CONTROL_RPL
00800016 - EHHSS_RA_FTC	CL_EHHSS_PCO_RA_FTC_NOTIFIC
00800018 - EHHSS_RAS_AC	CL_EHHSS_PCO_RAS_ACTION_STD
00800019 - EHHSS_RAS_PM	CL_EHHSS_PCO_RAS_ACTION_PM
00800028 - EHHSS_RAS_AP	CL_EHHSS_PCO_RAS_APPROVAL
00800029 - EHHSS_RAS	CL_EHHSS_PCO_RAS_LIFECYCLE
00800031 - EHHSS_RAS_SI	CL_EHHSS_PCO_RAS_SIGNATURE
00800032 - EHHSS_RAS_EV	CL_EHHSS_PCO_RAS_EVL_INQUIRY
00800033 - EHHSS_RSKREL	CL_EHHSS_PCO_RAS_RSK_REL
00800040 - EHHSS_RA_IMP	CL_EHHSS_PCO_RAS_IMP_NOTIFIC
00800041 - EHHSS_RA_HAZ	CL_EHHSS_PCO_RAS_HAZ_NOTIFIC
00800042 - EHHSS_RA_AGT	CL_EHHSS_PCO_RAS_AGT_NOTIFIC
00800049 - EHHSS_RAS_CF	CL_EHHSS_PCO_RAS_EVL_INC_CFA
00800050 - EHHSS_RA_CTR	CL_EHHSS_PCO_RAS_CTRL_NOTIFIC

00800050 - EHHSS_RA_CTR

To adapt workflows, you can perform the following activities:

• You can change the process flow directly in the workflow template (in the Workflow Builder), or copy the delivered template to the customer-specific namespace.

• You can add additional steps within a process by performing the following steps:

1. Change the workflow template (or copy the delivery to the customer-specific namespace)
2. Create further steps and (if necessary) workflow tasks in the customer-specific namespace in the Customizing activity Define Tasks and Actions for Cross-Application Components.
3. Add the new tasks to the workflow inbox configuration in the Customizing activity Assign Task IDs to POWL Types for Cross-Application Components. Enter the application ID EHHSS_INBOX and the POWL type EHHSS_INBOX_TYPE for your task.
4. Activate the workflow template.

• You can add logic that can be called from a workflow task (process step) by performing the following steps:

1. Create a PCO class that inherits from the delivered class of the process that is specified in the Customizing activity Configure Process Definitions. It is recommended to inherit from the delivery class and adapt it with further public methods. To include your business logic, use one of the following two options:

• Implement the logic directly in the PCO method.

• Implement the logic in a BOPF action of the corresponding process control business object (PCBO). Note: this is the architecture that Environment, Health, and Safety follows.

1. Use the standard event (WORKITEM_COMPLETED) if you open a dialog and the workflow has to wait for an event. If you want to use a more specific event, you must define the new event on the PCO class. For the dialog to raise the new event to continue the workflow, you can use the static method RAISE_WF_EVENT of the root PCO CL_EHFND_WFF_ROOT_PCO.
2. After you have finished implementing and adapting the workflow template, configure the new PCO class in the process definition in the Customizing activity Configure Process Definitions under Health and Safety Management.

rdisp/max_wprun_time - Maximum work process run time   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 6260 Date: 20240523 Time: 173822     sap01-206 ( 67 ms )