Show TOC

 XStep: Input Validations in Input Fields Locate this document in the navigation structure

Use

To restrict the value range for a specific input value, you define an input validation for it in the XStep process instruction. In the input validation, you determine:

  • The validation rule that is used to check the input value in the PI sheet

  • Whether invalid values in the PI sheet are accepted and how this is done

If the process operator has entered an invalid value in the PI sheet the system issues a warning message, informing the process operator that the value entered does not correspond to the validation rule. The process operator can reject or accept the value. If the process operator accepts a value that does not correspond to the validation rule he or she may be requested to sign.

Example Example

This graphic is explained in the accompanying text.

End of the example.

Prerequisites

  • Check function

    If you want to use a check function to check the input value, a suitable function module must have been created in the system.

    To create or display function modules, go to Customizing for Process Management and choose   Process Instructions   Define PI Categories for PI Sheet Using Characteristic Overview.   Assign Characteristics to Dynamic Function Calls   Create Function Modules for Dynamic Function Calls.  

  • Error Handling

    If a signature is required when invalid input values are accepted in the PI sheet, you must specify which type of signature you want to use in Customizing for Control Recipe Destinations . You have the following options:

    • Signature without a password check

    • Digital signatures

      If several individual signatures are to be executed, you also specify the signature strategy in the control recipe destination.

      For more information about digital signatures and the required settings, see Approval Using Digital Signatures .

Features

In the XStep process instruction, you can define the validation rule for the input validation as follows:

  • As a check formula for numerical values

    You write the check formula in the Editor. When doing so, refer to Check Formula Syntax for Input Validations .

  • As a check function for all values

    You specify a function module and assign the obligatory parameters of the function module with values.

    Error Handling

In addition to the validation rule, you can also enter the following information in the XStep process instruction to control how invalid input values are processed:

  • Invalid values are accepted

    You can choose from the following options:

    • Always Accept

      All invalid values are accepted by the system.

    • Never Accept

      Invalid values are never accepted by the system. In this case, you must discard the invalid value.

    • Only with Signature

      Depending on the settings made in the control recipe destination, the PI sheet requests a signature without a password, one digital signature, or several individual signatures defined in a signature strategy. You must also enter a comment for digital signatures.

      The input value is not automatically confirmed when the signature is entered. Once you have entered a correct value again, the system automatically accepts this value, which means you do not need to enter another signature.

      All deviating input values are documented in a deviation history . For more information, see Recording Actual Data in Browser-Based PI Sheets .

  • Signature strategy for digital signatures

    For digital signaturesin PI sheets you can define a signature strategy. This ensures that invalid values must be signed by several people. In the signature strategy, you specify which individual signatures are required.

    You can assign a signature strategy in the control recipe destination. This strategy is then used for all input validations. If you want to use a different strategy for a particular process instruction, you assign the strategy to this process instruction.

    The signature strategy must be carried out synchronously in the PI sheet. This means that the individual signatures must be executed immediately after one another (see Signature mode).

  • Authorization to execute a signature

    For signatures without a password check and for digital signatures, you can specify that a user requires a special maintenance authorization for the PI sheet to execute the signature.

    The system then checks if the activity specified in the process instruction has been included in authorization object C_CRPI_BER in the user master record.

    Irrespective of the settings you make here, the system checks the following authorizations for digital signatures:

    • Activity 73 ( Archive ) in authorization object C_CRPI_BER (PI sheet)

    • For individual signatures in a signature strategy, the authorization group for the individual signature in authorization object C_SIGN_BGR (authorization groups for digital signatures)

  • Signature mode

    If invalid values are accepted, signatures can only be entered synchronously ( synchronous signature process).

    See also: Definition of Signatures in PI Sheets

  • Warning

    If you have accepted an invalid value in the PI sheet anyway the system issues a standard message to this effect. Instead of this standard message you can also save your own message text.

Activities

Input Field with Check Function and Error Handling

  1. You create an XStep process instruction of type Input -> Character String.

    See also: XStep: Inputs

  2. You enter the name of the function module in the process instruction on the Input Validation tab page.

  3. You assign values to the parameters of the function module.

    See also: XStep Function Module Parameters

  4. On the Error Handling tab page, you define whether invalid values are accepted in the PI sheet and if so, how.

  5. If invalid values can only be accepted with a signature, you can also specify a signature strategy and an authorization.

  6. If applicable, you create your own warning message.