1. Product Definition
  2. Product Definition
  3. Maintaining multi-level authorization of a contract

1.15 Maintaining multi-level authorization of a contract

High value transactions requires multi-level of authorization. The levels of authorizations are defined in the Product Transaction Limits screen. You can use the Multi-level Authorization Detailed screen for authoring a contract n-1 times. However, final authorization can take place only in the contract screen.

When contract booked with huge amount, the contract must go for multi-level authorization. This can be done through three ways:
  1. Product level limit:

    Product limit can be further divided into 2 as follows:

    1. Transaction limit authorization:

      In this type, you have to maintain only transaction limit and level of authorization in the Product Transaction Limits Maintenance (OLDPLMNT) screen. When the transaction amount goes beyond the limit specified, then you have to authorize the transaction in Multilevel Authorization screen and final authorization can be done through the transaction screen.

    2. Role Based Authorization:

      In this type you have to specify the transaction limit along with role based authorization, such that authorization can be done by the users with the roles mapped, which was specified in Multilevel Authorization screen. This can be done in two ways with sequence and without sequence.

  2. User limit:

    User limit can be maintained in three different ways through the User Limits Maintenance (OLDUSRLM) screen , This does not move the transaction for multi authorization. The system throws an configurable error when the transaction amount goes beyond the input and authorization limit specified.

    1. User Limits:

      When user limits option is selected then you can maintain, the user level input and authorization limit which is applicable for all branches.

    2. Limits role:

      Limits role option is used to maintain branch specific user and authorization limit, specific role templates can be maintained through the Role Limit Maintenance (OLDRLLMT) screen.

    3. No limits:

      When no limits option is selected, then input and authorization limit is not used.

  3. Combination of product level limit and user level limit:

    This can be used only when the option cumulative and minimum authorization limit specified in the screen Product Transaction Limits Maintenance screen. This option helps to authorization the transaction when cumulatively. If minimum authorization limit in Product Transaction Limits Maintenance screen is greater than or equal to authorization limit specified at User Limits Maintenance screen.

    Note:

    The system throws the validation if the authorization limit is less than the minimum authorization limit specified.
    Using Product Transaction Limits Maintenance screen (OLDPLMNT) and Multilevel Authorization screen (OLDOVDEF), you can perform the following:
    • Transaction limits maintenance for validating transaction amount.
    • Defining authorization level hierarchy based on roles while authorizing a transaction.
This topic contains following sub-topics:

Parent topic: Product Definition