Specify Internal Ledger Authority Combinations

Explanation

This activity is used to specify authority combinations for an authority class. The combination blocks or permits users who belong to the authority class to view information on certain code strings in the various query windows and reports in IFS/Internal Ledger, as well as in reports created in IFS/Report Generator.

Prerequisites

Before authority combinations can be specified, the following must have been completed:

• At least one internal ledger must have been created.
• Your user should be connected an internal ledger.
• At least one authority class should be entered for your company in IFS/Internal ledger.

System Effects

As a result of this activity, a user belonging to an authority class is either allowed or not allowed to to view information on specific code strings in the internal ledger.

Window

IL Authority Combinations

Related Window Descriptions

IL Authority Combinations

Procedure

To create an authority combination:

1. Open the IL Authority Combinations window.
2. Create a new record and enter a new authority combination. It is useful to start by allowing all code parts for use by the authority class; do this by marking all the code parts with a percent sign(%). On the next line you can then indicate the code parts which are not allowed, i.e., those to which authority is not given. It is possible for a combination of code parts to be both allowed and not allowed. In such cases, the combination that is not allowed always takes precedence.

When defining combinations the code parts can be marked in four different ways:

• Enter a value for the code part. This indicates that, if you are specifying combinations which are allowed, users who belong to this authority class can query the code part if it contains this value. If you are specifying combinations which are not allowed, users in this authority class cannot query the code part if it contains this value.
• Enter a space. This indicates that if you are specifying combinations which are allowed, users in this authority class can still query even if no value is specified on the code part. If you are specifying combinations which are not allowed, if the code part is left blank, users will be able to query only the code parts which have values specified and not the code parts which have no value specified.
• Enter a percent (%) sign. This indicates that, if you are specifying combinations which are allowed, users in this authority class can query on this code part regardless of its value. If you are specifying combinations which are not allowed, users in this authority class cannot query on the code part at all. You can also enter a value, such as 3%, in the Account field. This indicates that all accounts beginning with 3 are either allowed or not allowed, depending on how combinations are defined.
• Enter an underscore ( _ ). This indicates that, if you are specifying combinations which are allowed, users in this authority class can query on this code part regardless of the value in this position. If you are specifying combinations which are not allowed, users in this authority class cannot query on a code part if it contains a value in this position. For example, if you are specifying that code B_3_ is not allowed, users in this authority class cannot query on code part B, if the code part is 3 characters long and has 3 in the second position.