Kontakt

Ansicht
Dokumentation

EHENV_WF_WFS - Adapt Workflows for Environment Management

EHENV_WF_WFS - Adapt Workflows for Environment Management

rdisp/max_wprun_time - Maximum work process run time   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

In this activity, you can learn how to adapt the workflows of SAP Business Workflow to suit your customer-specific processes. The process foundation of the Environment, Health, and Safety component 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 checked the processes by implementing the Customizing activity List Configured Processes under Foundation for EHS.

The following workflow templates are delivered with the corresponding workflow adapter class and triggering event:

Workflow Template Class Name/Triggering Event
00800243 EHENV_MDINF CL_EHENV_USR_WF_ADAPTER/COLLECTION_INFO
00800245 EHENV_MDDUE CL_EHENV_USR_WF_ADAPTER/COLLECTION_OVERDUE
00800246 EHENV_MDESC CL_EHENV_USR_WF_ADAPTER/COLLECTION_ESCALATION
00800247 EHENV_SCEN CL_EHENV_SCEN_WF_ADAPTER/SCENARIO_DEACTIVATED
00800249 EHENV_RQNTF CL_EHENV_REQ_WF_ADAPTER/COMPLIANCE_REQ_NEW_VERSION

To setup notification workflows, use the class name/triggering events for each corresponding workflow, as specified in the table above.

00800249 EHENV_RQNTF

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.
  4. Activate the workflow template.
  • You can add logic that can be called from a workflow task (process step) by performing any of the following:
  • Create a new workflow adapter class that inherits a delivered class of the processes (CL_EHENV_USR_WF_ADAPTER, CL_EHENV_SCEN_WF_ADAPTER, or CL_EHENV_REQ_WF_ADAPTER). It is recommended to inherit the delivery classes and adapt them with further public methods. Then, include your business logic in the newly created method.

  • Enhance the existing, delivered by default, workflow adapter classes (CL_EHENV_USR_WF_ADAPTER, CL_EHENV_SCEN_WF_ADAPTER, or CL_EHENV_REQ_WF_ADAPTER). Add your public methods and business logic and thus enhance or override the default business logic.

  • Create a new workflow adapter class based on the foundation adapter class (CL_EHFND_WFF_BASE_ADAPTER) and add your custom business logic to it. You can use the new adapter class to override the usage of the entire workflow adapter classes that were delivered with the standard system.

00800249 EHENV_RQNTF




CPI1466 during Backup   General Material Data  
This documentation is copyright by SAP AG.

Length: 5478 Date: 20240523 Time: 181409     sap01-206 ( 60 ms )