Extra element types

Prior to Extra Elements being inserted into an existing screen, they must first be defined. This step can be performed with assistance from the plugin provider, based on a web service’s required parameters. This configuration step is typically performed by a technical team in accordance with the plug-in developer’s requirements.

This ensures the functional team can use the Extra Element Type in the correct way.

Transaction code /TCTM/EWM_CUST - TCT is provided for this purpose. See customising node for EWM under Mobile Data Entry > TCT Mobility > Maintain TCT Mobility Basic Customizing.

The examples below would differ based on the available plugins:

Defining an extra element type for screen usage

This node allows customisation of additional functionality where available. Element type and description are defined at this level, with additional configuration held at the subsequent lower-level nodes.

Available Parameters

Available parameters are defined per element. The relevant plugin/web service provider should be contacted to understand the available parameters and values needed.

Defining the possible parameters for an extra element

Allowed Value Types

Each Extra Element parameter must also be configured with the permitted types of field maintenance. This ensures that functional consultants abide by the rules of usage for a service.

Defining the technical type for each parameter

Relevant Authorisations

Additional screen elements can be assigned SAP authorisations, applying any necessary restrictions during execution.

Defining the authorisation requirement for interacting with an extra element

The relevant authorisations and the application of restrictions ultimately depends on the back-end processing logic built in SAP.

Last updated

Was this helpful?