Define Maintenance Authorization for a User

This document explains how you define the work order authority level for different users. This is done to limit user access to the work order system.

Use this instruction when you do not want all users to have full access to all maintenance data.

Note: When one user is added to the authority list, all other users must also be defined.

Outcome

The work request authority is defined for all users, which limits their ability to work with work requests.

The information is stored in the work order authorization (MPAUTW) file.

The settings are used by the system and restrict the work request authority per user.

Before you start

The user for whom authority will be defined must first be defined in 'User. Open' (MNS150).

Follow These Steps

  1. Start 'Work Order Authorization. Open' (MOS175/B).

  2. Select an sorting order.

  3. Select a user ID and an authorization level (if sorting order 2 is used), and select New to display the E panel.

  4. On the (MOS175/E) panel, specify an authorization level (when sorting order 1 is used), a signature and a maximum order amount (optional).

  5. Specify the restrictions, if any, per site, order type, facility, warehouse and service group. Also specify whether the selected objects are to be included in or excluded from the user's authority.

    If, for example, all fields are left blank and the flag is set to 2, the user will be fully authorized.

  6. Specify whether quick entry is allowed, whether work requests may be released without costing, and whether the user may release work requests.

  7. If the user should not be allowed to release work requests, set a highest work request status for the user. Press Enter to finish.

Parameters to Set

Program ID/Panel Field The field indicates …
(MOS175/B) Authorized …the name of the user to which give system access will be given.
(MOS175/E) Authorization level

…the user's authority level. The user can be defined with authority 1 to 9, where 1 is the highest authority.

Users with authority level 1 have full authority to make changes to other users' authority.

Users with authority level 2 to 9 are authorized to access and change the authority for users with the same or lower authority levels.

(MOS175/E) Signature …a pin code of four alphanumeric characters. The code is used in some programs, for examplesuch as (MOS170), as an override.
(MOS175/E) Max order amount

…the maximum level that the user may authorize in (MOS170).

Example: If the user is defined with an authority of EUR 100, the system will check that the estimated value of the work request in (MOS170) is less than EUR 100 (materials, labor, etc.). A user cannot release or edit a request that is over his or her budget.

(MOS175/E) Site …a site or a range of sites to which the user is authorized tohas authorization. If maximum authority should be given to the user, these fields should be left blank and the include/exclude flag should be set to '2'.
(MOS175/E) Order type …an order type or range of types to which the user has authorization. If maximum authority should be given to the user, these fields should be left blank and the include/exclude flag should be set to '2'.
(MOS175/E) Facility …a facility or range of facilities to which the user has authorization the user is authorized to. If maximum authority should be given to the user, these fields should be left blank and the include/exclude flag should be set to '2'.
(MOS175/E) Warehouse …a warehouse or range of warehouses to which the user has authorizationthe user is authorized to. If maximum authority should be given to the user, these fields should be left blank and the include/exclude flag should be set to '2'.
(MOS175/E) Service group …a service group or range of service groups to which the user has authorizationthe user is authorized to. If maximum authority should be given to the user, these fields should be left blank and the include/exclude flag should be set to '2'.
(MOS175/E) Quick entry allowed …whether the user is allowed to use the quick order entry function in (MOS070) or use the F14 (retro order function) in (MOS185).
(MOS175/E) Approved by

…the identity of a the user that needs to approve the requests entered by the current user. If this field is filled in, the 'Allow release' field must not be set to 1.

Work requests can be displayed per approver in 'Work Request. Open Toolbox' (MOS197).

(MOS175/E) Allow work order without product costing

…whether the user is allowed to release a work request without performing pre-costing.

The valid alternatives are:

0 = No

1 = Yes

(MOS175/E) Allow release …whether the user is allowed to release work requests to become work orders in (MOS170).
(MOS175/E) Status …the highest work request status for a user. This field should only be used when the user is not allowed to release work requests. The status entered in this field will be the highest status the user is allowed to set on a work request.
Related topics