Sales Audit Database Administration Release User Guide

Transcription

1 Sales Audit Database Administration Release User Guide March 1, 2005

2 2005 NSB Group The contents of this manual and the software it describes are the property of NSB Group and are copyrighted. Any unauthorized reproduction in whole or in part is strictly prohibited. For additional copies of the manual, contact NSB Group. NSB Group 2800 Trans-Canada Highway Pointe-Claire, Quebec, Canada H9R 1B1 Tel.: (514) Fax: (514) Connected Retailer Sales Audit Database Administration User Guide Software Release: NSB No.: Printed in Canada

3 Contents Introducing Database Administration (DB Admin)... 1 Working With This Manual... 2 A few terms... 2 Prerequisites and related documentation... 2 The Basics... 3 Accessing DB Admin for SQL Server... 3 Accessing DB Admin for Oracle... 3 Changing the DB Admin server... 4 Entering information... 4 Help... 4 Exiting DB Admin Login Control... 5 Login Control window... 6 Users... 7 Creating a login ID... 7 Modifying a login ID... 8 Deleting a login ID... 9 Changing a password... 9 Database assignment Assigning databases for a login ID Removing access to a Sales Audit database from a login ID Security Overview of DB Admin Security Security Class Adding a new security class Removing a security class Assigning a user to a security class...15 Granting database access to a login ID Removing access to a database for a login ID Changing the access setup for a login ID System Processes Accessing the System Processes window Appendix A: Security Class Template Guidelines...21

4 ii Sales Audit Database Administration Security Class Template Glossary of Terms... 29

5 Preface Introducing Database Administration (DB Admin) Database Administration is a client/server module based on Windows, used to define and control user access to the Sales Audit databases and the application's modules. DB Admin is used to: grant access to new users maintain access for existing users create security classes assign users to security classes and audit groups

6 2 Sales Audit Database Administration Working With This Manual This manual explains how to use DB Admin to set up user access and control security for your Sales Audit application. It is addressed to system administrators and those with some computing background, so we assume knowledge of standard Windows tools, and familiarity with its basic concepts. We use the following formats and icons in this manual: This symbol or format Bold Indicates A mandatory field. A menu item, button, tab, field name or check box in your application interface. > and then click If you need information about Windows, we suggest you read a basic introduction. A few terms The following terms are used in this manual and may be unfamiliar: Mandatory (or Required), indicates that there must be information in a field. Either you enter it or the system provides it. Default, indicates information that appears automatically, without your having to enter it each time. Defaults can usually be overridden. Flag is an option or parameter that acts as a signal to the system. Select, when used with options, means to place a check mark in an option box to enable it. Clear, when used with options, means to remove a check mark from an option box to disable it. Prerequisites and related documentation You should be familiar with Sales Audit prior to using this manual. Documentation for the Sales Audit application consists of help files and the following manuals: Sales Audit User Guide describes how to use all the features of the Sales Audit application, including Guided Audit, Store Performance, Customer Liability, Store Operations Security and Reports. Sales Audit Table Maintenance Configuration Guide describes how to set up the tables in Sales Audit to support your day-to-day operations. The Security Configuration section of the Sales Audit Product Review Manual (PRM) describes security considerations.

7 The Basics 3 The Basics DB Admin can only be accessed with a User ID and password that have the required permissions. Generally, this user will be the system manager or the Sales Audit manager. Database Administration Accessing DB Admin for SQL Server 1. Click the DB Admin icon on your desktop or select the program from your Start menu. The login window appears. 2. Enter the following information: Field Name User ID Password Server Database DBMS 3. Click OK. Description sa sysadmin The name of the Sales Audit server you are connecting to. master Sybase SQL Server or Microsoft SQL Server Database Administration Accessing DB Admin for Oracle 1. Click the DB Admin icon on your desktop or select the program from your Start menu. The DB Admin Login window appears.

8 4 Sales Audit Database Administration 2. Enter the following information: Field Name Description User ID Password Server Database auditworks oracle The name of the Sales Audit server you are connecting to. Unused DBMS Oracle 7.3 or Oracle Click OK. Changing the DB Admin server You can change the server to which you are logged on without exiting DB Admin From the Edit menu, select Server Login. Enter the appropriate login information for the server you want to access and click OK. Entering information As you enter, retrieve and change information, remember that when a field is gray, it can't be edited. Gray areas usually indicate values that have been defined elsewhere or that are not applicable to your environment. Help Help provides you with: step-by-step instructions on how to accomplish tasks. field definitions and key terms. 1. To access help, select Help from the menu bar or press F1. Exiting DB Admin Click in the upper right corner of the DB Admin main window.

9 1 Login Control DB Admin offers multi-level security for applications and databases. You can control the users who log in to applications and define the databases they can access. You can also restrict access to the modules within applications and the degree to which users can modify the data to which they have access. All these features are accessed through the Login Control window.

10 6 Sales Audit Database Administration Login Control window The Login Control window gives you access to all the major functions of DB Admin including: creating, modifying and removing user login IDs granting and denying access to databases adding and removing databases adding and deleting security classes restricting access to security classes setting up security for individual users Field Name Full name Default database Currently logged in Last password changed Language Users Databases not in Databases in Description The name of the user. Will be the same as their login ID. The database the user will be accessing upon logging in to Sales Audit. A flag indicating whether the user is on the system. Information purposes only. The date the password for this user ID was last changed. The default language for this user ID. The list of users defined in the system. The databases to which the user ID has not been assigned. The databases to which the user ID has been assigned.

11 Users 7 Users All users of Sales Audit servers and databases must be defined in DB Admin and given access to the Sales Audit databases. The databases required for Sales Audit are: auditworks auditworks_work (the work tables used by the application; mandatory for all users) auditworks_test (testing database; optional) Note: If you use multiple Sales Audit companies, each with its own Sales Audit database, users must be given explicit access to those databases. Creating a login ID Modify Logins Launch DB Admin. Click Modify Logins. The Login Control window appears. Click Add Login. The Add New Login window appears. 4. Enter the following information: Field Name Login ID Full name Password Default database Description A unique identifier that must be entered when the user logs in to Sales Audit. The standard is the user's first name and the initial of his/her family name, for example, JOHNR. Used only for Oracle databases; the user's first and last names. The password that must be provided when a user logs in with this ID. Used only for SQL databases. The database to which the user will be connected by default. For Sales Audit, should be auditworks.

12 8 Sales Audit Database Administration 5. Click OK. 6. Double-click the database to which the user ID is to be assigned or highlight the database name and click Add Database. The Add User to Database window appears. 7. Select the database role: awbrowsers grants read-only access; awusers grants read and write access. Note: DB Fixed Roles are not used and should not be selected. 8. Click OK. Repeat steps 6-8 for each database the user ID is to be granted access to. Note: You can also add multiple databases in one step using SHIFT+CTRL. If you do so, the system will prompt you for the roles, one by one. Assignment occurs in order from the first selected database in the list to the last. You are not prompted with the name of the database for which you are assigning the role. 9. Modifying a login ID Once a login ID has been set up, you can modify its default database and the databases it can access. From the Login Control window, highlight the ID you want to modify. 10. If required, enter the new default database.

13 Users If required, change the databases the login ID can access. To Do this Add a database Highlight the database to add in the Databases not in column and click Add Database. Select the role for the database in the Add User to Database window. Remove a database 3. Click OK. Highlight the database to remove in the Databases in column and click Remove Database Deleting a login ID From the Login Control window, highlight the login ID you want to remove. In the Databases in column, select all databases to which the ID has access and click Remove Database. Click Remove Login and reply Yes in response to the prompt to confirm the removal. Changing a password The database administrator can change the password associated with a login ID. Password 1. From the Login Control window, click Password. The Password change for window opens Type the new password. Type it again to confirm, then click OK.

14 10 Sales Audit Database Administration Database assignment The database assignment of any login ID can be modified at any time; databases can be added or removed Assigning databases for a login ID From the Login Control window, highlight the login ID for which you want to assign databases. Highlight the database to add in the Databases not in column and click Add Database. Select the role for the database in the Add User to Database window. Click OK. Removing access to a Sales Audit database from a login ID From the Login Control window, highlight the login ID for which you want to remove database assignments. Highlight the database to remove in the Databases in column and click Remove Database.

15 2 Security Overview of DB Admin Security Although there are security features built in to Sales Audit, the Database Administration application enables you to assign additional levels of security on a user by user basis using security classes. Security classes enable you to restrict: access to modules access to tabs within modules access to Table Maintenance the ability to modify transactions within certain transaction categories access to certain menu options and command buttons the ability to accept and unaccept store/register/date records the ability to create and modify exception transaction criteria

16 12 Sales Audit Database Administration Security Class Every user of Sales Audit must be assigned to a security class. You define the classes and the restrictions that apply to each one. You can set up as many security classes as are necessary for your organization. You might set up the following classes, for example: Sales Audit Manager, whose members have access to all Sales Audit functionality Sales Audit department, whose members can access auditing functions and audit reports, but not Store Operation Security and Table Maintenance Management, whose users can retrieve reports, but can't modify data. Field Name Classes Modules Access Modify transaction category level access Description A list of the security classes in DB Admin. A list of the modules that apply to the security classes. Defines the access granted to members of the security class. Defines the level of access granted to the security class for the transaction category. Used for the Sales Audit, Customer Liability and Accounting modules. The value determines the degree of access users in the class have: the lower the value, the greater the restrictions. The values assigned to transaction categories come from the Transaction Header table of Table Maintenance in Sales Audit where transaction categories are defined.

17 Security Class 13 Field Name Retrieve transaction category descriptions from Description You highlight the highest value transaction category that users assigned to the security class should have modify access to. They will be denied modify access to transactions in categories with higher values. Values range from 0 to 255. Zero (0) denies modify access to all transactions. 255 grants access to all transactions. The database from whose tables descriptions and values for transaction categories are to be retrieved. Adding a new security class 1. Modify Logins Security Classes Launch DB Admin then click Modify Logins. 2. From the Login Control window, click Security Classes. The Sales Audit Security Classes window opens.

18 14 Sales Audit Database Administration 3. Click Add Class. The Class Name New window opens In the Class ID field, enter a unique numeric value between 1 and 999. The default is the next available value. In the Description field, enter an identifier for the class, then click OK. The Sales Audit Security Classes window lists the class you just created. In the Classes box of the Security Classes window, highlight the class you want to set up. The balance of the screen fills with the default access settings for the Startup Frame module Clear the features in the Access box to which the security class should be denied access. In the Module box, highlight Sales Audit, click OK to save the changes to Startup Frame access and then repeat step 7. In the Retrieve transaction category descriptions from box, select the database on which the transaction categories and their values are to be based. In the Modify transaction category level access box, highlight the highest value transaction category that users assigned to the security class should be able to modify.

19 Security Class Repeat the applicable steps for each module. When you have set up the class, click Save. Security Classes Removing a security class From the Login Control window, click Security Classes. The Sales Audit Security Classes window opens. Highlight the class you want to remove and click Delete Class. Click Yes to confirm the deletion. Assigning a user to a security class All login IDs in Sales Audit must be assigned to a security class and explicitly be given access to the databases to which they were assigned when the IDs were created. Security classes determine the degree of access login IDs have; security class for a login ID is assigned by database. Field Name Users User does not have access to User has access to User information User Id Class Id Description The login IDs that have been defined in the system. The databases the login ID has been assigned to, but not yet given access to. The databases the login ID has been assigned and given access to. The login ID for the user. Same as the value you selected from the Users list. Mandatory. The Class ID to which the login ID is assigned.

20 16 Sales Audit Database Administration Field Name First name Last name Department Phone Extension Exception Edit Access Audit Group Description Mandatory. The user's first name. Mandatory. The user's family name. Mandatory. The department in which the user works. The user's phone number. For Sales Audit. If selected, the user of the login ID can add and modify exceptions. Mandatory. The Audit Group in Sales Audit to which the login ID belongs. The default value is All Stores. Application Security Granting database access to a login ID In the Login Control window, highlight the login ID for which you want to set up database access. Click Application Security. The Sales Audit User Setup window opens. In the User does not have access to box, select the database the login ID should be granted access to. Enter all necessary information and click Save. Application Security Removing access to a database for a login ID In the Login Control window, highlight the login ID for which you want to remove database access. Click Application Security. The Sales Audit User Setup window opens. In the User has access to box, select the database for which you want to remove access and click Remove. Click Yes in response to the prompt to confirm the removal. Application Security Changing the access setup for a login ID In the Login Control window, highlight the login ID for which you want to change the access setup. Click Application Security. The Sales Audit User Setup window opens. Make the changes and click Save.

21 3 System Processes The System Processes window allows you to view the processes, along with their waittime, for all the users that are logged on. System Processes Note: Users that have access to Microsoft SQL Server generally view the same information that s contained in the System Processes window through specific SQL scripts.

22 18 Sales Audit Database Administration System Processes window System Processes window 1 of 3 System Processes window 2 of 3

23 System Processes window 19 System Processes window 3 of 3 Field Name Spid Loginame sid Status Kpid Blocked Waittime Lastwaittype Waitresource Dbid Uid Cpu Physical lo Memusage Description SQL Server process ID. The login name the user entered to launch the Sales Audit or DB Admin application. A globally unique identifier (GUID) for the user. Indicates the Process ID s status, such as running, sleeping or background. Microsoft Windows NT 4.0 thread ID. Process ID (spid) of a blocking process. Current wait time in milliseconds. Is 0 when the process is not waiting. A string indicating the name of the last or current wait type. Identifier of a lock resource. ID of the database currently being used by the process. ID of the user who executed the command. Cumulative CPU time for the process. The entry is updated for all processes, regardless of whether the SET STATISTICS TIME ON option is ON or OFF. Cumulative disk reads and writes for the process. Indicates the number of pages in the memory cache that are currently allocated to this process. A negative

24 20 Sales Audit Database Administration Field Name Login Time Last Batch Ecid Open Tran Hostname Program Name Hostprocess Cmd Nt Domain Nt Username Net Address Net Library Description number means that the process is freeing memory. Indicates the time at which a client process logged on to the server. For system processes, indicates the time when SQL Server startup occurred. Last time a client process executed a remote stored procedure call or an EXECUTE statement. For system processes, the time at which SQL Server startup occurred is stored. Execution context ID used to uniquely identify the subthreads operating on behalf of a single process. Number of open transactions for the process. Name of the workstation that launched the process. Name of the application program that started the process. The process ID number of the workstation that launched the process. Command currently being executed. Windows NT 4.0 domain for the client (if using Windows Authentication) or a trusted connection. Windows NT 4.0 user name for the process (if using Windows Authentication) or a trusted connection. Unique identifier assigned to the network interface card on each user's workstation. When the user logs in, this identifier is inserted in the net_address column. Column in which the client's network library is stored. Every client process comes in on a network connection. Network connections have a network library associated with them that allows them to make the connection. Accessing the System Processes window To view the system processes, do the following: System Processes 1. Click the icon. The System Processes window will open displaying all the system processes. 2. Click Refresh to view the most current information. Note: The Locks command button opens the Database Locks window which displays the database objects held locked from the System Processes window.

25 Appendix A: Security Class Template The Sales Audit Security Class Template is a simple tool to help you plan the settings of the security classes required for your organization. In the Security Class field of the template, enter both a security class code and a description that will be used to distinguish the class. The template lists all the Sales Audit modules, the tabs within each module, and functions within the Sales Audit module to which you may elect to restrict access. For the security class being created, in the Access? column, indicate whether or not the users assigned to the security class will have access to the module, tab, or function in question. Guidelines Numbered references are supplied in the template for clarification. These refer to the following guidelines: Allows access to the individual Sales Audit modules via the toolbar icons or the Modules menu item. This option allows a user to create or modify Guided Audit or module exceptions. This allows a user to verify a translate reject or a process error. Without this access, a user can still open up the Process Error Log and Unverified Translate Rejects windows. In this instance, it is necessary to indicate those transaction categories for which a user will be able to modify the transactions. The users belonging to the security class can have transaction modification privileges for all or none of the transaction categories, or for specific categories only. Allows the user to mass delete a complete store/register/date record. This feature supersedes the Count/Deposit Modification Method parameter set up in Sales Audit table maintenance. Even if the setting of this parameter allows for the modification of the count or deposit figures, a user belonging to a security class where this feature is not enabled would not be able to do so via the Media Reconciliation window. Once a store/register/date record has been audited and has a status of Verified, in preparation for the Day-end function, the user is allowed to change the status of the record to Accepted. Once a store/register/date record has a status of Accepted, its status can be changed back to Edited or Verified, thus allowing for further manipulation of the data.

26 22 Sales Audit Database Administration 9. Users with access to the Force-Accept feature can force a status of Accepted on a store/register/date record for which there is still an outstanding short/(over) concern or missing, exception, or duplicate transactions have not been verified. 10. Grants access to the various reports pertaining to each module Allows a user to set up or modify the tables or parameters required in the setup of that module. When a user has access to the Table Maintenance Module via the toolbar or the File menu, this allows access to the complete Company tab. If, however, a user does not have access to the Table Maintenance Module, then granting access to Company Table Maintenance will still enable the user to create new stores and registers from the Guided Audit window. Selecting this option gives a user access to the Security tab in Table Maintenance, provided that the users of this class already have access to the Table Maintenance Module via the toolbar or the File menu. This is necessary if you want the users belonging to this security class to have the ability to temporarily modify their audit group. Selecting this option gives a user the ability to unlock a process in Audit Status whose status has been In Progress for an inordinate length of time. Selecting this option gives a user the ability to modify archived transactions. Selecting this option allows a user to launch the FTP/UNC wizard for Express Add from outside the Express Add window. 17. Selecting this option allows a user to verify media reconciliation.

27 Appendix A: Security Class Template 23 Security Class Template Sales Audit Security Class Template #1 Security Class: Sales Audit Module Setting/Function Transaction Category Access? (Yes/No) Startup Frame (1) Sales Audit Accounting Store Operations Security Store Performance Customer Liability Batch Processes Reports Table Maintenance Archived Report Viewer Exceptions Setup (2) Sales Audit Translate and Process Error Verification (3) Transaction Modification (4) All Customer Cashier Stock Control Payroll Register Closeout Totals Training Mode None Transaction Move Mass Delete (5) Media Reconciliation Count Modification (6) Accept (7) Unaccept (8) Force-Accept (9) Sales Audit Reports (10) Module Table Maintenance (11) Unlock Status Record (14) Archived Transaction Modifications (15) Express Add FTP/UNC File Transfer (16) Media Reconciliation Verification (17) Accounting Store Balance tab Subledger tab Tax tab Accounting Reports (10) Module Table Maintenance (11) Store Performance Media Category tab Register Activity tab Store Performance tab Module Table Maintenance (11)

28 24 Sales Audit Database Administration Sales Audit Security Class Template #1 (cont d) Security Class: Sales Audit Module Setting/Function Transaction Category Access? (Yes/No) S.O.S. Cash Security Control Over/Short Trend tab Employee Purchases tab Credit Security Control Customer Liability Aging tab Activity tab Stocked Document Control tab Customer Liability Reports (10) Merchandise Status tab Module Table Maintenance (11) Aging tab (Legacy) Forms Control tab (Legacy) Promotions tab (Legacy) Layaways tab (Legacy) Batch Processes Day End Period End Batch Processes Reports (10) Table Maintenance Company Table Maintenance (12) (Set in Startup Frame) Security Table Maintenance (13) (Set in Startup Frame) General Table Maintenance (Set in Startup Frame) System Table Maintenance Table Maintenance Reports (10) Cash Management Module Table Maintenance Accept

29 Appendix A: Security Class Template 25 Sales Audit Security Class Template #2 (cont d) Security Class: Sales Audit Module Setting/Function Transaction Category Access? (Yes/No) Customer Liability Aging tab Promotions tab Layaways tab Customer liability Reports (10) Module Table Maintenance (11) Batch Processes Day End Period End Batch Processes Reports (10) Table Maintenance Company Table Maintenance (12) Security Table Maintenance (13) General Table Maintenance System Table Maintenance Table Maintenance Reports (10)

30 26 Sales Audit Database Administration Sales Audit Security Class Template #2 Security Class: Sales Audit Module Setting/Function Transaction Category Access? (Yes/No) Startup Frame (1) Sales Audit Accounting Store Operations Security Store Performance Customer Liability Batch Processes Reports Table Maintenance Archived Report Viewer Exceptions Setup (2) Sales Audit Translate and Process Error Verification (3) Transaction Modification (4) All Customer Cashier Stock Control Payroll Register Closeout Totals Training Mode None Transaction Move Mass Delete (5) Media Reconciliation Count Modification (6) Accept (7) Unaccept (8) Force-Accept (9) Sales Audit Reports (10) Module Table Maintenance (11) Unlock Status Record (14) Archived Transaction Modifications (15) Express Add FTP/UNC File Transfer (16) Media Reconciliation Verification (17) Accounting Store Balance tab Subledger tab Tax tab Accounting Reports (10) Module Table Maintenance (11) Store Performance Media Category tab Register Activity tab Store Performance tab Module Table Maintenance (11)

31 Appendix A: Security Class Template 27 Sales Audit Security Class Template #2 (cont d) Security Class: Sales Audit Module Setting/Function Transaction Category Access? (Yes/No) S.O.S. Cash Security Control Over/Short Trend tab Employee Purchases tab Credit Security Control Customer Liability Aging tab Activity tab Stocked Document Control tab Customer Liability Reports (10) Merchandise Status tab Module Table Maintenance (11) Aging tab (Legacy) Forms Control tab (Legacy) Promotions tab (Legacy) Layaways tab (Legacy) Batch Processes Day End Period End Batch Processes Reports (10) Table Maintenance Company Table Maintenance (12) (Set in Startup Frame) Security Table Maintenance (13) (Set in Startup Frame) General Table Maintenance (Set in Startup Frame) System Table Maintenance Table Maintenance Reports (10) Cash Management Module Table Maintenance Accept

32

33 Glossary of Terms Access Sales Audit Security Classes window. Defines the access granted to members of the security class. Audit Group Sales Audit User Setup window. Mandatory. The Audit Group in Sales Audit to which the login ID belongs. The default value is All Stores. Class Id Sales Audit User Setup window. Mandatory. The Class Id to which the login ID is assigned. Classes Sales Audit Security Classes window. A list of the security classes in DB Admin. Currently logged in Login Control window. A flag indicating whether the user is on the system. Information only. Database Login window. The database you want to connect to. Not applicable for an Oracle DBMS. Databases in Login Control window. The databases to which the user ID has been assigned. Databases not in Login Control window. The databases to which the user ID has not been assigned. DBMS Login window. The database management system you are using. Default database Add New Login window. Used only for SQL databases. The database to which the user will be connected by default. For Sales Audit, should be auditworks. Default database Login Control window. The database the user will be accessing upon logging in to Sales Audit. Department

34 30 Sales Audit Database Administration Sales Audit User Setup window. Mandatory. The department in which the user works. Exception Edit Access Sales Audit User Setup window. If selected, the user of the login ID can add and modify exceptions. First name Sales Audit User Setup window. Mandatory. The user's first name. Full name Add New Login window. Used only for Oracle databases; the user's first and last names. Full name Login Control window. The name of the user. Will be the same as their login ID. Language Login Control window. The language Sales Audit is launched in for this user ID. Last name Sales Audit User Setup window. Mandatory. The user's family name. Last password changed Login Control window. The date the password for this user ID was last changed. Login ID Add New Login window. A unique identifier that must be entered when the user logs in to Sales Audit. The standard is the user's first name and the initial of his/her family name, for example, JOHNR. Modify transaction category level access Sales Audit Security Classes window. Defines the level of access granted to the security class for the transaction category. Used for the Sales Audit, Customer Liability and Accounting modules. The value determines the degree of access users in the class have: the lower the value, the fewer the restrictions. The values assigned to transaction categories come from the Transaction Header table of Table Maintenance in Sales Audit where transaction categories are defined. You highlight the highest value transaction category that users assigned to the security class should have modify access to. They will be denied modify access to transactions in categories with higher values. Values range from 0 to 255. Zero (0) denies modify access to all transactions. 255 grants access to all transactions. Modules Sales Audit Security Classes window. A list of the modules that apply to the security classes.

35 Glossary of Terms 31 Password Add New Login window. The password that must be provided when a user logs in with this ID. Login window. The password the user must enter to access DB Admin. Phone Extension Sales Audit User Setup window. The user's phone number. Retrieve transaction category descriptions from Sales Audit Security Classes window. The database from whose tables descriptions and values for transaction categories are to be retrieved. Server Login window. The name of the server you want to connect to. User does not have access to Sales Audit User Setup window. The databases the login ID has been assigned to, but not yet given access to. User has access to Sales Audit User Setup window. The databases the login ID has been assigned and given access to. User ID Sales Audit User Setup window. The login ID for the user. Same as the value you selected from the Users list. Login window. The ID the user must enter to access DB Admin. Users Login Control window. The list of users defined in the system. Users Sales Audit User Setup window. The login IDs that have been defined in the system.

36 Index A M access DB Admin Oracle 3 access DB Admin SQL server 3 modify login ID 11 access setup, change for login ID 20 add security class 17 O add user role 9 assign login ID to security class 18 Oracle, login to DB Admin 3 C P change access setup for login ID 20 password, change 11 change password 11 change server 4 create login ID 9 create security class 17 remove login ID 11 remove security class 18 D required databases 9 role, add 9 database access 9 role, user 9 database assignment 13 database assignment, add for login ID 13 database assignment, remove 13 database, remove access to 20 delete login ID 11 security class, assign login ID 18 delete security class 18 security class, create 17 security class, remove 18 server, change 4 E SQL server, login to DB Admin 3 R S exit DB Admin 5 U H user ID, assign to security class 18 user ID, change access setup 20 Help 4 user ID, create 9 user ID, delete 11 user ID, modify 11 L user ID, remove 11 login 3 login ID, assign databases to 13 login ID, assign to security class 18 login ID, change access setup 20 login ID, create 9 login ID, delete 11 login ID, modify 11 login ID, remove 11 login ID, remove access to database 20 login ID, remove database assignment 13 user ID, remove access to database 20 user role 9 user role, add 9