Field Control

Use

This function enables you to adapt the user interface to ensure that you record and process exactly the data that you need in SAP EHS Management. Field control enables you to control the behavior and appearance of the fields, buttons, and groups on the user interface at runtime if a data record fulfills certain conditions. For example, if you use SAP EHS Management to record work-related injuries and illnesses, you can adapt the user interface to make certain fields visible and mandatory for a specific region or country. This function helps organizations to fulfill data recording and regulatory compliance requirements.

Prerequisites

You are familiar with the structure of the business objects of SAP EHS Management that are modeled in the Business Object Processing Framework (BOPF). For more information about the business objects of SAP EHS Management, see Business Objects.

You have specified field control in Customizing for SAP EHS Management under Foundation for EHS Management  Settings for Business Objects  Specify Field Control.

Features

Field control provides the following features:

• Profiles

  Field control uses profiles to store the information about both the conditions that a data record must fulfill for field control to apply, and how the system then controls the user interface when field control applies.

  You can set up a profile to use the following conditions when determining if field control applies:

  • Node Attribute Value

    You can use profiles that are based on an entered value for a given field (node attribute). For example, when you have entered the value X for the Y field, the corresponding profile applies.

  • Authorization-Based Profile

    You can use profiles that adapt the user interface based on a user’s authorizations for the corresponding node level. This way, you can ensure that the system provides data access and the possibility to execute business logic only to authorized users.

  • Function Class

    You can use profiles that contain customer-specific logic implemented by classes. This allows you to specify more complicated logic for a field if basing the profile on a node attribute value is not sufficient.

  You can set up a profile to use the following property settings to control how the system applies field control:

  • Attribute

    You can specify fields to be enabled (visible), read-only, or mandatory.

  • Node

    You can specify whether instances of the node can be created, read, updated, or deleted.

  • Action

    You can specify the actions that a user can perform on the data of a corresponding node, for example, change the status, create subnodes, and so on.

  • Association

    You can specify other nodes that are associated with the node of your profile. This makes it possible to apply field control settings for a given profile to associated nodes. Such settings specify, for example, if a new data record of an associated node can be created.

• Merge Strategy

  When you have two or more profiles whose conditions all apply in parallel for a certain node, but which define contradicting property settings, you can specify a merge strategy. This strategy dictates priorities for contradicting property settings.

• Propagation

  You can apply node and association property settings dynamically to all subnodes (to the whole subtree). This saves configuration effort if you want to reuse settings in a field control profile.