Download FREE Presentations |
Users Interface and Users Management in ERP System
The internet user interface architecture is depicted in the following diagram:
The HTTP-server security mechanisms are used to offer secure access to the HTML-page that contains the Java applet. User Management: User management functionality is used to create user, provide user login and password and to give authorizations to the users. The users authorizations are dependent on their role in a company. To be able to work with ERP applications, users must have some sort of session authorization, database authorization, and library authorization. During installation of ERP, some default roles are automatically created. The default roles make sure that users can use the menu browser and its associated functions and commands. Users Type: There are various types of users for an ERP package which can be broadly classified as under:
Role dependent users authorization: From a user point of view, a role represents a function in an organization. In ERP, a role represents a set of authorizations for a function in a company (database). User authorizations that are defined per role instead of per user significantly reduce the redundant data. The authorizations for normal users are therefore defined in roles to which they can be linked. The role concept provides a user-friendly method to quickly add new users or to update user authorizations. Because an employee can have more than one function in a company, more than one role may be assigned to the user. A role can also contain more than one sub-role, which can also have sub-roles. All these roles and sub-roles form a role tree, which can be viewed with a role browser. The role browser shows the role tree in a graphical user interface. Role-dependent authorizations can be defined at the following component levels in an ERP system:
The non-role-dependent authorizations: In addition to these role-dependent authorizations, some additional authorizations can be specified that are not defined by the employees role, for example, the development parameters, device preferences, and so on. These non-role-dependent authorizations are defined in templates to reduce redundant data, which then can be linked to the user profile. These templates pertaining to non role dependent authorization can be divided into the following categories:
|