Restrict Access to Specific SAP System

Sometimes, you might want to prevent users from accidentally running a script in production environment because you have fully tested this script. You can achieve this functionality centrally using Control Panel. Alternatively, you can use Dynamic Skip functionality in mapper to restrict an SAP system from being used.

To restrict an SAP system using Custom Dynamic Skip

  1. Open the Process file and clone a field to create a dummy field.
    How_to_restrict_process_file_1
  2. Rename the clone field and map the field to capture the SAP system ID.
    How_to_restrict_process_file_2

    The SAP system ID is used in Custom Dynamic Skip.

    How_to_restrict_process_file_3

  3. Enter the following code in Custom Field Skip Editor to prevent the SAP system ,CEP, from being used.

    If iValue = "CEP" then

    iReturnID = "E:00-999"

    iReturnMessage = "This process file is not yet released for CEP system."

    Return 4 'Stop current call

    else

    Return 1 'Allow user to continue

    end if

    When a user tries to run a Process file and logs on to CEP, the processing stops as shown in the following screenshot. Note that if the user logs on to any other system, the Process file runs normally.

    4-HT-Retrict-process-file-to-be-exe

To disable this check, go to the Mapper tab, and disable this field as shown in the following screenshot.

How_to_restrict_process_file_6

You can customize the SAP systems that you want to block, the return message ID, and the return message. We recommend that you use E: in Return Message; the return message will then be color coded in red in Excel.

Check Innowera cloud sample file <Cloud ID: 2294>  for example of this concept. Click here on how to use Innowera cloud sample file.