Skip to content

SYMENU System Manager Introduction 35

Menu Level Security Control

 

For User Name SUPERVISOR, all flags for menu items are set to Y.  At this point, SUPERVISOR is the only person that can add, change, or delete password information.

 

Users must have SYS rights before they can access any of the individual packages.  Select System Utilities.  At the Package Name prompt, press F7 and the following screen will appear:

 

 

 

 


Select a Processing Application

 

Select System Utilities

 

At the Process Name prompt, press F7 and the following screen will appear:

 


 

 

 


By selecting Accounting, the system will display the five accounting packages: General Ledger, Accounts Receivable, Accounts Payable, Payroll, and Bank Book.  At this time, the user has full rights to the Accounting (ACT) packages as shown on the next page.

 

 

 

 


Function Keys:

 

           F4                      Change Flags (1–5) to N

 

           F5                      Change Flags (1-5) to Y

 

           Return               Allows you to continue and change flags 1-5 individually.

 

 

If all rights to the accounting packages are intended, then further definition of access privileges by package is not necessary.

 

If further restrictions are needed, enter the package name.  For example, if you had entered AR for the Package Name prompt and pressed F7, the processes available will be displayed as shown below.

 

 

 


The rights for this User Name may now be tailored by Maintenance, Inquiry, Processing, Reports, and Utilities.  By selecting Maintenance, the following screen will appear:

 

 

Maintenance Application Names for A/R

 

You may press the F4 key to change all flags to No, press the F5 key to select all as Yes or press RETURN to individually select flag status.

 

Finally, at the User Name entry field you may press the F3 key to change the user password or press the F2 key to delete the User Name from the password system.

 

 

Password Setup Process

 

1.                   Add User

2.                   Select System Utilities

3.                   Select as Required

a.       Accounting

b.       Distribution

c.       Util-Setup                        .                    

4.                   Select Package as Required

5.                   Select Process as Required

a.       Maintenance

    Select Rights

b.       Inquiry

           Select Rights

c.       Inquiry

    Select Rights

d.       Processing

    Select Rights

e.       Reports

    Select Rights

f.         Util-Setup

    Select Rights

 

           

                       

                       

Salesman Security in 7.3

 

To enable Salesman Security in Elliott, you need to perform the following setup:

 

1.       Identify the user as a salesman in Password Setup for that user.  If you leave the Salesman No blank, then it implies this person is not subject to salesman security.  (For example, this maybe an accounting person who needs to access all salesman records).


 

2.       Determine whether there should be a house account that all Salesmen can access in Global Setup for eContact Manager.  A house account is usually a customer that doesn’t have a specific salesman and any salesman can go after the house account.  As of this writing (05/12/05), the house account logic only applies to eContact Manager, eContact Processor and Export Processor.  We plan to apply the House Account logic to A/R and COP as well.


 

3.       The following flag is for Global eContact Manager.  You need to determine if a particular salesman is subject to the Salesman Security in eContact manager.


 

4.       The following flag “Disable Salesman View Other’s Customer in A/R” is used for

  • A/R Customer File Maintenance
  • A/R Customer File Inquiry
  • A/R Account Inquiry
  • A/R Summary Account Inquiry
  • eContact Processor (AR Files & Ship to)
  • Export Processor (AR Files & Ship to)

You need to determine if a particular salesman is subject to the salesman security in the above areas.


 

5.       The following flag “Disable Salesman Inquiry For Other’s in COP” is used in

  • COP Order Inquiry
  • COP Invoice History Inquiry
  • COP Stock Status Inquiry
  • COP Recurring Order Inquiry
  • COP Freight Calculation Inquiry
  • eContact Processor
  • Export Processor (COP Files, except Ship-To). 

You need to determine whether the salesman is subject to salesman security in the above areas.


 

6.       You also want to limit the activities that a salesman can do in Elliott.  The following are areas in Elliott that salesman security is implemented:

            A/R Customer File Maintenance

            A/R Customer Inquiry

            A/R Customer Account Inquiry

            A/R Summary Account Inquiry

            COP Order Inquiry

            COP Invoice History Inquiry

            COP Recurring Order Inquiry

            COP Stock Status Inquiry

            COP Freight Calculation Inquiry

            COP Order Entry

            COP Sales Desk (Add Other’s Orders, No Control on Change Quote)

            COP Order Edit List (VA,46)

            COP Order Acknowledgement/Email (not Laser Form) (VA,46)

            COP Order Quote/Email (not Laser Form) (VA,46)

            COP Open Order by Salesman (VA,46)

            eContact Manager

            eContact Processor

            Export Processor

We suggest you restrict the Salesman beyond these menu items.  For example, if you wish to let Salesmen print reports for their own customers, you do not want to give them the “Order Status Reports” menu item since there is no salesman security in that area.  Instead, you might consider giving your salesmen access to “Export Processor” where salesman security is implemented.

 

The following flags determine whether the user can use eContact/Export Processor


 

There is a separate flag for “Disable Interaction w/ eContact & Export Proc” because you may want certain people to use the “eContact/Export Processor” in batch mode without allowing them to use the interaction mode, where they can access more information.

 

Before you decide a user’s security for eContact, customers and sales orders, you should consider the following factors:

  • Is this user a salesman?  Do you want to limit this user to access only those eContacts that he/she is a salesman?
  • Do you have a house account?  Do you allow house account information to be accessed by all salesmen if the previous answer is “yes.”
  • Will this user use Global eContact?  Global eContact is like a Rolodex where you can have a list of contacts with information for their phone number, email, fax number, etc.  Do you want this user to see all Contact information in Global eContact or would you like to limit the salesman to see only his/her contacts in Global eContact? 
  • Do you want to let this user view eContact information only without the ability to edit it?
  • Do you want to let this user add and edit credit cards or view the credit card number?  Typically, you may allow collecting of credit card information, but once the credit card is collected you do not want users to see the credit card number for security reasons.
  • Do you allow this user to access eContact/Export Processor?  eContact/Export Processor is like a report writer where the user can access a lot of information in the Elliott system.  You may consider giving the user access to pre-written reports without the ability to change it.  This lowers the security concern.  If you wish to implement this, then you will give users access to eContact/Export Processor, but disable the “Interaction” with eContact/Export Processor.
  • If you decide to give users the ability to Interact with eContact/Export Processor, you need to decide whether this user use and view other people’s templates or not.  If a user is allowed to Interact with eContact/Export processor, even though they may be prevented from using other’s templates, they can still create new templates or change their own template criteria.
  • Once you allow a user to “Interact” with eContact/Export Processor, you should consider the Elliott menu security.  For example, if you allow this user to access customer file maintenance, then they can access all information in the Customer Category. Another example is if you allow this user to access order entry, then this user will be able to access all information in the Order Category.  This may be subject to the Salesman Security, depending on how you set the following flags:
    • Disable Salesman from Viewing Other’s Customer in A/R
    • Disable Salesman from Inquiring Other’s in COP
  • If this user is a supervisor (IT) and develops a template (pre-written report) for other users, you need to give this user the ability to change the template for other users.
  • The following areas in Elliott are also related to Salesman Security.  It shows how the security is controlled:
    • A/R Customer File Maintenance
      • Elliott Menu Security
      • Global Security: “Disable Salesman from Viewing Other Customers in A/R”.
      • Global Security: “Disable Change Customer”
      • Global Security: “Disable Delete Customer”
      • Global Security: “Disable Print Customer List/Label”
    • A/R Customer Inquiry
      • Elliott Menu Security
      • Global Security “Disable Salesman from Viewing Other Customers in A/R”
    • A/R Customer Account Inquiry
      • Elliott Menu Security
      • Global Security: “Disable Salesman from Viewing Other Customers in A/R”.
    • A/R Summary Account Inquiry
      • Elliott Menu Security
      • Global Security: “Disable Salesman from Viewing Other Customers in A/R”.
    • COP Order Inquiry
      • Elliott Menu Security
      • Global Security: “Disable Salesman Inquiry for Other’s in COP”
    • COP Invoice History Inquiry
      • Elliott Menu Security
      • Global Security: “Disable Salesman Inquiry for Other’s in COP”
    • COP Recurring Order Inquiry
      • Elliott Menu Security
      • Global Security: “Disable Salesman Inquiry for Other’s in COP”
    • COP Stock Status Inquiry
      • Elliott Menu Security
      • Global Security: “Disable Salesman Inquiry for Other’s in COP”
    • COP Freight Calculation Inquiry
      • Elliott Menu Security
      • Global Security: “Disable Salesman Inquiry for Other’s in COP”
    • COP Order Entry
      • Elliott Menu Security
      • Global Security: “Disable User from Adding Orders in Order Entry”
      • Global Security: “Create Credit Memo in Order Entry”
      • Global Security: “Create COP Credit Memo from Invoice History”
      • Global Security: “Allow User Enter Negative Qty in Order Entry”
      • Global Security: “Change COP Orders After Pick Ticket Printed”
      • Global Security: “Allow to Delete COP Orders”
      • Global Security: “Allow to Override Terms in Order Entry”
      • Global Security: “Allow to Override Salesman in Order Entry”
      • Global Security: “Allow to Override Disc Pct in Order Entry”
      • Global Security: “Allow to Override Line Item Unit Cost”
      • Global Security: “Allow to Override Order Commission Field”
      • Global Security: “Change COP Pre-Paid Info”
      • Global Security: “Disable User from Printing Order Edit List”
      • Global Security: “Disable Salesman Add Other’s COP Orders”.
      • Global Security: “Disable Salesman Change Other’s COP Orders”.
      • Global Security: “Disable Salesman Printing Other’s COP Orders”.

 

Feedback and Knowledge Base