Operator Maintenance
Exploring
This program lets you maintain the list of users who require access to SYSPRO and to define any restrictions applicable.
Things you can do in this program include:
- Add a new operator
- Maintain an existing operator
- Copy an existing operator
- Delete an existing operator
Starting
-
If you are using the Contact Management System and you delete an operator code, only the link to the contact in CMS is removed not the contact itself.
-
When you delete an operator code, the operator name is no longer displayed in any SYSPRO program where it was previously visible, regardless of whether transaction details were captured before the operator was deleted.
This is because programs reference the operator table to retrieve the operator name (i.e. the operator name is not saved against a transaction).
- You must assign a valid Job classification to the operator if your job numbering method is by job classification (Setup Options > Keys > Manufacturing) and you use the Requirements Calculation program.
Solving
Amendment journals are created automatically for changes to operator settings.
These journals can be viewed, printed and purged using the Operator Amendment Journal program.
When you delete an operator code, the operator name is no longer displayed in any SYSPRO program where it was previously visible, regardless of whether transaction details were captured before the operator was deleted. This is because programs reference the operator table to retrieve the operator name (i.e. the operator name is not saved against a transaction).
Instead of deleting the operator, you could enable the Operator locked out option (Operator Maintenance) to prevent the operator code from being used.
If you are using the Contact Management System and you delete an operator code, only the link to the contact in CMS is removed not the contact itself.
If the global role configuration option: All operators must be assigned to a role (Role Management) is enabled, then you won't be able to save details for an operator until the operator is assigned to a role.
This applies to any new operator added as well as any existing operator changed from the time this option is enabled. Changes made will only take effect once the operator logs back into SYSPRO.
Enter the Network user name in the Operator Details pane if you want the operating system to authenticate the operator.
If the global role configuration option: Access control always by role is enabled (Role Management) then no information is displayed in the Access list view if the operator belongs to a role.
Access control must be defined against the role.
If the global role configuration option: Activities and fields always by role is enabled (Role Management) then the Activities and Fields section of the Security pane is disabled and must be defined against the role.
Operator subgroups accommodate the need for certain operators to inherit the program access settings of a number of different groups, without you having to configure additional groups.
When establishing an operator's level of access to a program, the system allows access if any of the groups allow access to the program.
Access to a program is Denied only if all the groups to which the operator belongs deny access to that program.
You can assign the operator to up to 200 subgroups.
A group that has administrator rights cannot also be a subgroup.
If a list of subgroups is defined for an operator and the primary group is changed to be an administrator group, then that list of subgroups is removed from the operator.
To restrict operators from viewing contacts for an account you should use one or more of the CMS security settings (e.g. Contact property, classification, type, category or territory) to prevent access to the contact information.
This is achieved using the files indicated below (the English version of the files is shipped as standard):
-
An XML-based dictionary file (LANGUAGExx.XML where xx indicates the language code)
This file contains the translated captions and is stored below the root folder of the e.net web applications folder (i.e. \Main\Language). The stylesheet file is stored in the \Main\Transform folder.
-
An error message file that contains translated error messages.
Error messages are stored in four separate files:
- MSGCOMxx.IMP (common messages)
-
MSGFINxx.IMP (financial messages)
-
MSGDISxx.IMP (distribution messages)
-
MSGMANxx.IMP (manufacturing messages)
When an error occurs in a business object, the system automatically retrieves the language code for the operator and attempts to open the appropriate message file.
If the error message for a specific language code cannot be accessed, then the system defaults to a language code of 05 (i.e MSGCOM05.IMP, MSGFIN05.IMP, MSGDIS05.IMP and MSGMAN05.IMP).
Using
- Amendment journals are created automatically for any changes made to operator settings. These journals can be viewed, printed and purged using the Operator Amendment Journal program.
-
Because operators are available across all companies (while contacts are company-specific) operators are created as contacts in all companies.
- Whenever you add or change the default operator warehouse, you need to restart SYSPRO for your changes to take effect.
- If the Office Automation and Messaging module isn't installed, then you can only bulk email/fax statements using the Statement Print program and fax/email SRS reports.
- Setting the accounting date to the system date ensures that all clients connecting to the server use the same date and time (for those operators that have this option enabled).
- Setting a low tickover can compromise the performance of your system. Consider using SYSPRO's Print Preview facility to review the output from a report before actually printing the document.
- Operator role settings for display and entry forms take precedence over any operator, group or company setting.
-
Global role configuration:
-
If the Access control always by role option is enabled (Role Management) then no information is displayed in the Access list view if the operator belongs to a role. Access control must be defined against the role.
- If the Activities and fields always by role option is enabled (Role Management) then the Activities and Fields section of the Security pane is disabled and must be defined against the role.
-
If the All operators must be assigned to a role option is enabled (Role Management) then you won't be able to save details for an operator until the operator is assigned to a role.
This applies to any new operator added as well as any existing operator changed from the time this option is enabled.
-
-
If the Save docking layout when using roles operator activity is disabled, then changes to the personal view of an operator's role (e.g. pin and unpin panes and change splitter positions) are not saved when the operator exits the application.
Columns in a list view can be removed and repositioned when roles are in use. However, any changes made by the operator are not saved and the original list view layout for the current role is restored when next the application is launched.
-
Groups enable you to categorize operators, selectively indicating modules and programs they are allowed to access.
Groups are configured using the Operator Groups program.
-
A group that has administrator rights cannot also be a subgroup.
If a list of subgroups is defined for an operator and the primary group is changed to be an administrator group, then that list of subgroups is removed from the operator.
-
The job logging setting for a program accessed by an operator belonging to multiple groups is taken from the first group/program where access is permitted.
The primary group is processed first, followed by the subgroups, in alphabetical order.
-
If an operator is allowed access to a program within either a primary or subgroup, then the operator has access to that program.
In the following example, where an operator belongs to three groups, the operator's security level is equivalent to Allowed for the programs listed:
Program Primary Group Subgroup1 Subgroup2 Asset Group Maintenance
Denied
Browse only
Allowed
A/P Period end
Denied
Allowed
Denied
GIT Transactions
Browse only
Allowed
Browse only
Although denying an operator access to a CMS Account type prevents the operator from accessing that Account type, the security does not cascade down from Account security (i.e. the operator can still access contact information for an Account).
This is because a contact can be linked to multiple Accounts, Customers and Suppliers.
In this case, the access control for the organization is handled by Customer, Supplier and Account and the access control against a Contact is handled at the Contact level.
To restrict operators from viewing contacts for an Account you should use one or more of the Contact security settings (e.g. Contact property, classification, type, category or territory) to prevent access to the Contact information.
- You can allow an operator to create new reports (SYSPRO Reporting Services) and design new SRS document templates (SRS Document Print Setup) by enabling the Report designer option in the Options pane for the operator required.
- You cannot access this option if concurrent use of the operator code is enabled, as the license conditions for the SRS Report designer requires that only specific operators can use the designer.
-
The number of report designers and the number of designer seats is used to determine the number of users who may access the Report Designer function of SYSPRO Reporting Services concurrently.
For example: If you are licensed for two designer seats, then you can only select this option for two operators.
- If you enable this option, ensure that the Crystal Designer has been installed on the operator's client machine, otherwise the operator cannot design SRS reports.
-
Regardless of the number of report designers licensed, only one SRS document format can be modified at a time.
There is one XML document in \BASE\ReportingCustomized\DocumentControl\Documents.XML that contains all the meta data on SRS document formats.
XML does not support multiple edits to the same file. You can, however, maintain multiple SRS reports as each report has its own report control XML file.
Referencing
Field | Description | ||||||
---|---|---|---|---|---|---|---|
File |
|
||||||
Edit |
|
||||||
Contact |
These options are only applicable if the Contact Management System is installed. Operators are available across all companies, while contacts are company-specific. For this reason, operators are created as contacts in all companies. |
||||||
Contact Details |
This uses the Contacts program to maintain contact details for this operator in the Contact Management System .
If a link if one
does not exist, you will be prompted to create one.
|
||||||
Remove Contact Link |
Remove any link between the operator code and a CMS contact.
Only the link is
removed (i.e. you must use the Contacts program to delete contacts.
|
||||||
Password |
|
||||||
Set Password |
This lets you use the Admin Password System program to assign a login password to this operator code. This enables you to prevent unauthorized usage of this code. |
||||||
Set Alternate Password |
This lets you assign an alternate password for the operator. This is used exclusively for the Electronic Signatures system, where against the eSignature Global Configuration you indicate whether to use the operator's primary or alternate password to secure the respective transactions. |
||||||
New |
This creates a new operator code. |
||||||
Delete |
This deletes the current operator code. |
||||||
Copy |
This creates a new operator by copying the details from another operator code. You can view the last operator code copied during the current run of the program, once you copy at least one operator. |
||||||
Operator |
Indicate the operator code you want to maintain or add. |
||||||
Notepad |
This loads the Admin Notepad Editor (Rich Text) program to add notes against the operator code. |
||||||
Printers |
This loads the Printers per Operator program to allocate printer access for the operator. |
||||||
Contact... |
If the Contact Management System is installed, then this creates a new contact for the operator, or enables you to maintain existing contact details. |
Field | Description | ||||
---|---|---|---|---|---|
Personal |
|
||||
Operator |
This indicates the operator code entered. |
||||
Operator name |
This indicates the descriptive name assigned to the operator. |
||||
Network user name |
This indicates the name used by this operator to log in to the network. You typically enter a network user name if you want the operating system to authenticate the operator. If you enabled the Use network user name (System Setup ) option, SYSPRO assumes that the operator code is the same as the network user name and inserts the network user name automatically in this field when you save the operator settings. |
||||
Group |
This indicates the primary group to which this operator belongs.
This cannot be the same as a subgroup already
defined against the operator.
|
||||
Subgroup |
Assign the operator to up to 200 subgroups. This accommodates the need for certain operators to inherit the program access settings of a number of different groups, without you having to configure additional groups. |
||||
Location |
This indicates the physical location of the operator. |
||||
|
This indicates the e-mail address of the operator. This can be used by the Event Management program when you define an event type as email and select the Notify user option, or when you select the Requisition routed to another user event. |
||||
SQL Server authentication |
|
||||
SQL login |
Indicate the SQL Server authentication required for the operator:
|
||||
Login name |
This indicates the name used to validate the operator's access to SYSPRO, if you indicated that you require SQL Server authentication (System Setup ). If you indicated that you require NT authentication (System Setup) then the operator login and password required to access SYSPRO is the network login id that is authenticated by Windows NT. |
||||
Password |
This indicates the password assigned to the Login name. |
||||
Test SQL connection | This lets you confirm that you can connect to SQL based on your login information entered. |
Field | Description |
---|---|
General |
|
Company |
This indicates the default company that must be used for this operator. |
Requisition user |
This indicates the default requisition user that must be used for this operator within the following programs:
You can use the eSignature PO Requisition
change user (eSignature Setup
) or the operator activity PO Req
change user to enforce the use of the default requisition user defined
here.
|
Buyer |
Enter a default buyer. The buyer will be added to the following programs, unless a buyer has already been specified:
|
Counter sales |
|
Customer |
This indicates the default counter sales customer that must be used for this operator within the Sales Order Entry and Point of Sale Entry programs. If left blank, then the Counter sales Default customer is used (Setup Options > Configuration > Distribution > Sales Orders ). |
Cash drawer |
This indicates the default cash drawer that must be used for this operator. |
Payment code |
This indicates the default payment type that must be used for this operator. |
Access |
|
Bank |
This indicates the default bank that must be used for this operator. |
Customer branch |
This indicates the default AR branch that must be used for this operator. |
Supplier branch |
This indicates the default AP branch that must be used for this operator. |
Job classification |
This indicates the default job classification that must be used for this operator. You must assign a valid Job classification to the operator if your job numbering method is by job classification (Setup Options > Keys > Manufacturing) and you use the Requirements Calculation program.
|
Warehouse |
This indicates the default warehouse that must be used for this operator. When this is not defined, the Default warehouse defined against the Company is used (Company Maintenance). Whenever you add or change the default operator warehouse, you need to restart SYSPRO for your changes to take effect. |
Field | Description | ||||||
---|---|---|---|---|---|---|---|
Date options |
|
||||||
Set accounting date to system date |
This sets the accounting date and time to the operating system date when this operator accesses SYSPRO. Otherwise the SYSPRO company date is used. In a client/server environment, setting the accounting date to the system date ensures that all clients connecting to the server use the same date and time (for those operators that have this option enabled). |
||||||
Use client system date |
This bases the accounting date on the system date of the client workstation instead of the server. This is typically used if the geographic locations of the client and the server are in different time zones, which could affect dates. When this option is enabled, the client date is used for business objects invoked by VBScripts run from the client machine. This option applies only to the date and has no effect on the transaction time. All transactions are relative to the server time (i.e. all times on reports and transactions are always the server time). |
||||||
Allow to change temporary company date |
This lets operators use a specific default date for transactions which remains valid until they exit from SYSPRO, or select a different date. |
||||||
Allow to change company date |
This lets the operator change the company date in SYSPRO (if the operator is allowed to change the temporary company date). |
||||||
Login |
|
||||||
Allow concurrent use of this operator |
This lets more than one person use the same operator code at the same time (e.g. several administrators sharing an account, or several operators using an account as a guest).
|
||||||
Notify ADMIN inbox if duplicate login |
This lets you notify the administrator (via the Message Inbox facility) when the operator code is used more than once at the same time (if concurrent use of the operator code is disabled). |
||||||
Override when company logins prevented |
This allows an operator to log into a SYSPRO company despite logins being prevented for that company (Company Maintenance). This is useful for operators who don't have system administrator privileges, but require access to resolve a problem. For example: An automated task prevents operators from logging in until the task is complete, but the task fails and the operator needs to access the system. |
||||||
Company access |
This indicate whether the list of companies refers to those the operator is denied/allowed to access. |
||||||
Company list |
This indicate the SYSPRO companies to which the operator is allowed/denied access. |
||||||
General |
|
||||||
Fax/mail integration required |
This allows the operator to fax documents (e.g. purchase orders, sales order and statements) from within the system, as well as email any SYSPRO report from within the system. If this option isn't enabled, the email option on the SRS Document Print Preview window is disabled. If the Office Automation and Messaging module isn't installed, then you can only bulk email/fax statements using the Statement Print program and fax/email SRS reports. |
||||||
Tickover refreshes on reports/batches |
This indicates the rate at which the system must notify the operator of its progress when producing reports and running batch programs. You can set the tickover according to a record count (i.e. the number of rows processed) or a time period (i.e. the number of minutes or seconds that have elapsed).
|
||||||
Special language support |
This option is only applicable if you are using SYSPRO in Thai. It affects the display of text in the Admin Notepad Editor (Rich Text).
|
||||||
Access | |||||||
Espresso license type |
Indicate whether the operator is a:
|
||||||
Report designer |
This lets the operator create new reports using SYSPRO Reporting Services and to design new SRS document templates (SRS Document Print Setup ).
Because the license conditions for the SRS Report Designer requires that only specific operators can use the designer, you can't access this option if concurrent use of the operator code is enabled.
|
||||||
Analytics administrator |
This lets the operator access the SYSPRO Analytics Setup program as well as the Site Administration Menu within the SYSPRO Analytics Administration program. |
||||||
Analytics viewer |
This lets the operator access the Viewer Menu within the SYSPRO Analytics Administration program.
You cannot access this option if concurrent use
of the operator code is enabled.
|
||||||
Role layout design |
This lets the operator define the layout of docking panes or configure list views and data grids (see Customization Management ). In addition, this option determines whether SRS Menus, Templates and Forms can be defined, copied and saved by operator role. If this option is enabled for multiple users, only one operator at a time can access the Design UI Layouts function. Otherwise you will only be able to create and copy Organization Lists within the Contact Management System for your own operator code. |
||||||
Contact management user only |
This indicates that the operator is licensed to only use the Contact Management System features of the SYSPRO application suite. This option cannot be enabled for operators with Administrator rights. Only the licensed number of operators configured as CMS only operators can access SYSPRO concurrently. |
||||||
Point of sale user only |
This indicates that the operator is licensed to only use the Point of Sale module. This option cannot be enabled for operators with Administrator rights.
|
||||||
Numeric formatting | |||||||
Override company setting |
This uses the decimal symbol defined in the Decimal character field for numeric values defined against the operator, instead of at company level. |
||||||
Decimal character |
This indicates the decimal symbol you want to use for numeric values for this operator. This affects every numeric field that contains decimals (e.g. values, costs, prices, quantities, unit of measure conversion factors, currency conversion factors, etc.).
In a client/server environment, the character you
indicate here must be the same as the one defined in your Region and
Language settings, otherwise incorrect values may be saved when
processing transactions in SYSPRO.
|
||||||
Override company settings | This lets you define a delimiter for numeric values over 999.00 for this operator. | ||||||
Use 1000 separator |
This is the delimiter for numeric values over 999.00 for this operator (e.g. a value of 123456789.12 is displayed as 123,456,789.12). This affects every numeric field, including (but not limited to):
|
||||||
1000's separator character |
This is the character (symbol) that must be used as the 1000's separator for numeric values for this operator.
In a client/server environment, the character you
indicate here must be the same as the one defined in your Region and
Language settings, otherwise incorrect values may be saved when
processing transactions in SYSPRO.
This affects every numeric field, including (but not limited to):
|
||||||
Number of digits after decimal |
This indicates the number of decimals you want to use for numeric values for this operator. An entry of zero removes decimals from values in entry and display/print fields. Regardless of your setting here, values are always held to two decimal places. Free-format stationery assumes a minimum of two decimals for any Price field, and three decimals for any Inventory Unit cost field. The Maximum decimals to show for price/cost option (System-wide Personalization ) controls the number of decimal zeroes displayed in price and cost list view columns. |
Field | Description | ||||
---|---|---|---|---|---|
Settings |
|
||||
Timeout required in menu and queries |
This indicates whether a timeout facility is required for this operator against SYSPRO menus and Query programs. This can be used to prevent the unauthorized usage of an operator's code when, for example, the operator is away from the computer. |
||||
Timeout action |
|
||||
Timeout period |
Indicate a specific period of time (where no keyboard/mouse activity has been detected) after which the selection made at the Timeout action field is activated. If you are also using the KeepAlive timeout (minutes) option (System-wide Personalization) then you must set the timeout period here to be less than the KeepAlive timeout (minutes) value. The system relies on 'no events occurring' for the operator timeout to take effect, but the KeepAlive system works by sending an 'event' to the system which causes the operator timeout to refresh. |
Field | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Activities | |||||||||
Selection |
|
||||||||
Configure Activities | Select Edit to selectively configure the access level to activities for the operator. | ||||||||
Fields |
|
||||||||
Selection |
|
||||||||
Configure fields |
Select Edit to view a list of available fields and configure the access level for this operator. |
||||||||
Menus | |||||||||
Enable standard SYSPRO menus |
Indicate whether the operator is allowed to access the standard SYSPRO menus provided. |
||||||||
Password |
|
||||||||
Number of login attempts |
This is the number of times the operator can incorrectly enter the password before being locked out of the system. This defaults to unlimited, but can be between 1 and 9 failed login attempts. This does not apply to e.net Solutions. |
||||||||
Operator locked out |
Indicate whether a lock has been set against the operator (i.e. the operator will be unable to load SYSPRO). |
||||||||
Password never expires |
This indicates you do not want the password for this operator to ever expire, regardless of any other password settings. |
||||||||
Last login |
This indicates the date and time that the operator code was last used to load SYSPRO. |
||||||||
Salesperson access control |
The access level defined here also applies to customer and account information within the SYSPRO Contact Management System . |
||||||||
Assign salesperson to current operator |
This indicates that the operator is also a salesperson. |
||||||||
Salesperson |
This indicates the SYSPRO salesperson code of the operator. |
||||||||
Apply access control |
This limits the operator to only edit their own data. The operator can, however, still view the data for other salespersons. |
||||||||
Filter reports and browses |
This prevents the operator from viewing the data of other salespersons in browses or reports. |
||||||||
Tile KPI definition access control | These options control the level for which the the user can add, change and delete tile KPIs. | ||||||||
Default access control |
This is enabled by default, meaning all operators who have access to the tile Insight Tile KPI Definitionprogram can make any changes. When you disable theDefault access controloption, the Administrator option is enabled by default. |
||||||||
Administrator |
The tile KPI administrator has full control to add, change and delete tile KPIs for the system, all companies, roles and operators. When you disable the Administrator access control option, you can disable or enable one or more of the remaining three access control settings:
|
||||||||
Company supervisor |
When enabled, this allows the operators to maintain tile KPI definitions for all companies they have access to. |
||||||||
Role supervisor | When enabled, this allows the operators to maintain tile KPI definitions for roles to which they belong and tile KPI definitions for all operators who belong to those roles. | ||||||||
Operator self-service |
When enabled, this allows the operator to maintain their own personal tile KPI definition. The operator can only edit tile definitions for themselves. |
Configuration
The E.net tab lets you configure restrictions and preferences against an operator with regard to the customers they can access and is applied to business objects when sales orders are processed.
Settings
Field | Description |
---|---|
Functional role |
This indicates the role of the user who is linked to this operator code. It enables you to filter information returned by business objects according to the user's role. Available roles that can be assigned include:
|
Language |
This indicates the language in which you want to display the user interface for business objects loaded by this operator. You can choose a language from the dropdown menu, or select {custom} to enter a user-defined language code. The business object retrieves the operator's language code automatically and returns the value as an XML attribute in the root element of the returned document (e.g. a language code of 07 is displayed as: <InvQuery Language="07"...>) Translating the user interface of business objects is accomplished using two files:
|
Language code |
Enter a user-defined language code. Only entries in the range 30 to 99 are allowed. |
Date format |
This indicates the format in which you want the user interface to display dates within business objects loaded by this operator. The business object retrieves the operator's date format automatically, and returns the value as an XML attribute in the root element of the returned document (e.g. A date format of 05 is displayed as: <InvQuery DateFormat="05"Tgt;) Select 08 - {custom} to define exactly how dates must be transformed if the predefined settings are not suitable. This is achieved using an XSLT stylesheet format.xsl which is stored below the root folder of the e.net web applications folder (i.e. \Main\Transform). If you do not modify this stylesheet file then the format defaults to 01. |
Decimal format |
This indicates the format in which you want the user interface to display value, price and cost fields within business objects loaded by this operator. The business object retrieves the operator's decimal format automatically, and returns the value as an XML attribute in the root element of the returned document (e.g. a decimal format of 02 is displayed as: <InvQuery DecFormat="02"Tgt;). Select 03 - {custom} to define exactly how decimals must be transformed if the predefined settings are not suitable. This is achieved using an XSLT stylesheet format.xsl which is stored below the root folder of the e.net web applications folder (i.e. \Main\Transform). If you do not modify this stylesheet file then the format defaults to 01. |
Default supplier |
Indicates the primary supplier code that is associated with this operator profile. |
Login
Field | Description |
---|---|
Usage for e.net business objects |
This lets you indicate how you want to control operator access to functional areas of e.net Solutions (according to the terms of your software license agreement). These are apportioned using the e.net License Import Wizard program. |
No access |
The operator code cannot be used as a login for the business objects of e.net Solutions. |
Named user |
The operator code can be used as a single-user login to functional areas of e.net Solutions. If a second user accesses e.net Solutions using this operator login, then the first user is effectively logged out. This lets you monitor the activities processed by the user. Each named user effectively consumes one license, regardless of whether they are logged in.
This option is not recommended if you have a
large number of users, but only a few require access to the business objects
at any one time.
|
Guest/anonymous user |
The operator code can be used by a concurrent number of users as a login to functional areas of e.net Solutions. For example: If your license caters for 10 concurrent users, then although any user can login using this operator code, only 10 can be logged in within a 30 minute period). However, this method can consume more licenses than necessary (e.g. a user who logs off and then logs back in within 30 minutes will consume two licenses). This option is recommended if you have a large number of users, but only a few require access to the business objects at any one time. One benefit of this method is that you don't require a SYSPRO operator code for each person that needs the same access to the business objects of e.net Solutions. However, because the users of this operator login are anonymous, you won't be able to place restrictions on individual users (i.e. all users of this operator login will have the same defaults and restrictions) and you won't be able to use job logging and journals to establish which user performed a specific task. The Concurrent users field indicates the number of times that this operator code can be used as a login to the business objects of e.net Solutions within 30 minutes. |
Access control
Select the Edit option from the Access control section:
Field | Description | ||||||
---|---|---|---|---|---|---|---|
Customers |
|
Customer order options
Select the Edit option from the Customer orders options section:
Field | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Warehouse selection |
|
||||||||||
Warehouses |
This indicates a list of warehouses for which the customer associated with this operator profile can create orders. |
||||||||||
Access Control |
|
||||||||||
Product Classes by Customer |
This indicates the product classes for which the customer associated with this operator profile can create orders. You can select all product classes, or specify a list of up to 50 product classes. |
||||||||||
Order creation |
|
||||||||||
Type of order |
Indicate the type of order that must be created when the customer associated with this operator profile places an order.
|
||||||||||
Order status |
Indicate the specific status that you want to assign to the capture of scheduled orders by the customer associated with this operator profile.
|
||||||||||
Minimum number of days to ship |
This is the number of days it typically takes to package and prepare a shipment for the customer associated with this operator profile. The order ship date is calculated as today's date plus your entry made here. |
||||||||||
Allow non-stocked items |
This treats the entry of an invalid stock code as if it were a non-stocked item. |
||||||||||
Accept orders that fail credit check |
This places orders into suspense if the customer's credit limit/terms are exceeded. |
||||||||||
Message to send if credit check failed |
This is the message that must be sent if an order causes the credit limit/terms to be exceeded. |
||||||||||
Operator to inform about new orders placed |
This is the operator who must be notified of any new orders placed by the customer associated with this operator profile. A message file (ADMMSG.DAT) is created by the order entry application in SYSPRO's working directory. This message file will contain information about orders created over the web. You can view this file from the Sales Orders Created Externally program. |
||||||||||
User defined sales message |
This indicates user-defined text for this operator profile that will be displayed prominently within the sales order applet. |
Field | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Access control |
This column displays the key fields for which you can configure operator access:
|
||||||||||||||||||||||
Access type |
This indicates the level of access granted to the operator for the key field:
|
||||||||||||||||||||||
Filter reports and browses |
This prevents the operator from viewing the data for the key field in browses or reports.
|
Field | Description |
---|---|
Add Roles |
This loads the Role Management program to maintain role descriptors. |
Organogram |
This loads the Role Organogram Maintenance program to view and manipulate the hierarchy of roles (organogram) for your organization. |
Column 1 |
A tick in this column indicates the operator has been assigned to the role. If more than one role is enabled for an operator, then the operator can switch between these roles using the Switch Role option from the SYSPRO Desktop ( ). |
Role |
This indicates the role descriptor usually matching the job description or job function assigned to an operator. SYSPRO operators can be assigned up to five roles, enabling them to switch between assigned roles as required. |
Primary role |
A tick in this column indicates that this is the primary role for the operator (i.e. the default role used when the operator logs into SYSPRO). |