 |
The use of this option is to apply restrictions and privileges to specific users who deal with specific aspects of the financial system.
Users must be defined in {USERS-5}.
All users defined on menu option {USERS-5}, has a record in this option. User records cannot be created in the option but may be updated.
Furthermore multiple records cannot be defined for a user.
To restrict or grant privileges to a
specific user, the record of the user concerned must be retrieved by
executing the <ENTER QUERY> function, supply query data and then
execute the <EXECUTE QUERY> function. Apply the restriction
and/or privilege and execute the <COMMIT> function to save the
changes made.
On entering this option, the mode will automatically be <ENTER
QUERY>. By executing <EXECUTE QUERY> all records will be
retrieved.
| Field | Type & Length |
Description |
|---|---|---|
| User Type | A1 | Supply the user type. The valid values are (P)ersonnel, (S)tudent, (O)ther or (T)emp. |
| Number | N9 | Supply the number of the user as defined on menu option {USERS-5}. A <LIST> function containing user number and name is available on this field. On providing the user number, the name will default to the name field. |
| User Code | A8 | Supply user code as defined on menu option {USERS-5}. |
| A45 | Displays the user's name. | |
| Store | A2 | Supply the store code to which the user may have access. When a user is defined on menu option {USERS-5}, store code ZZ is automatically linked to the user. Store code ZZ grants the user access to ALL stores. This means that should the user have access to the store menu options, the user may access and process transactions for any of the stores defined. Care must be taken when granting access to store menu options. This restriction applies primarily to the users who have access to the Stores System, which is within the Procurement Management System. Where a store user's responsibility is restricted to a specific store, the user may be restricted to the specific store by linking the relevant store code. However, in the event where a store user's responsibility covers all stores, the user must be linked to store code ZZ. Thus, users can be restricted to a specific store or has access to all stores. A <LIST> function containing store code and name is available. Stores are defined on menu option {FPMM-22}. |
| Access Level in PRS | N1 | Supply the level of access to access salary related information of personnel on the Payroll System. These levels are 1 - Top management; 2 - Other salaried personnel; and 3 - Wages. This field must be null for users who are not authorised to access salary related information. |
| Override Insufficient Funds Rule | A1 | May this user override insufficient funds when such a condition exists? The valid values are (Y)es or (N)o. The completion of this field is dependent on rule BB, defined on menu option {FCSM-1b2}. If rule BB is set to (Y)es, all users in this option will be set to (Y)es and cannot be updated to (N)o. This implies that, as an institution, should any user encounter an insufficient funds situation, the user may override it to allow the transaction to be processed. If (N)o, all users on this option will be set to (N)o, but individual users who are granted privileges to override insufficient funds may be set to (Y)es in this option. This implies that, as an institution, the override of insufficient funds is not allowed except for those users who are authorised to. |
| Approval Privilege | A1 | Valid values are (Y)es or (N)o. The field is secondary to the Alpha Field value of the System Operational Definition Rule Code EA to ES. Only rule codes that are Electronic can be Approved. If Yes the user can approve transactions / documents depending on access and restrictions. Otherwise the user has no Electronic Approval Privileges. |
| Buyer Privilege | A1 | Valid values are (Y)es or (N)o. If Yes the user can maintain PM Buyer document fields depending on access and restrictions. |
| Validator Privilage | A1 | Select (Y)es or (N)o to allocate Validator status. The Validators will be selected when entering an iEnabler GRV. Restriction 'FPDG' is in effect for GRV status. |
| Default Validator | A30 | Select the Type of Validator from the List of Values.
|
| Acess to Bank Detail |
A1 |
If a SOD codes D1 to D6 - "Authorise Bank Details” is set
to (Y)es, bank details cannot be inserted or updated from biographical
screens for the related perosn type and must be maintained from the option “Maintain
Bank Details” . Each SOD relate to a specific subsystem. D1 - Alumni D2 - Debtors D3 - Creditors D4 - Other D5 - Personnel D6 - Student Banking details are maintained on the following menus. FARO-28 - AR Debtors FCTM-9 - All Person Types FACO-29 - Other defined in {GOPS-3} FCTM-10 - Person Type Other not defined in {GOPS-3} FPMM-6 - Creditors FPRI-14 - Personnel PBOP-13 - Personnel FSAO-16 - Student Debtors SREGB-17 - Student Debtors SALUM-15 - Alumni A user can either create / edit, authorisation or edit and authorise banking detail depending on the user privileges.
|
|
| Processing Rules |
|
|---|---|
| No special processing rules |
| Date | System Version | By Whom | Job | Description |
|---|---|---|---|---|
| 13-Apr-2015 | v03.0.0.1 | Charlene van der Schyff | t206469 | New Manual |
| 09-Sep-2016 | V04.0.0.0 | Marchand Hildebrand | t216486 | Add bank deatil authorisation |