You use this program to view and maintain the configuration options for your SYSPRO system. The information entered here updates your IMPACT.INI file, which contains a list of settings used by SYSPRO. Any settings that you change will take effect only when next you load SYSPRO.
Field | Description |
---|---|
Configure e.net License | Select this to load the Configure e.net License wizard program to import and apportion your e.net licenses. |
Edit Client Configuration | Select this to edit the IMPACT.INI file on the client workstation (e.g. to specify the standard client directory, the custom client directory and the client id code). This function is not enabled in a mapped-drive environment. |
Field | Description |
---|---|
Options | |
Language |
This indicates the language code applicable to your system. |
Multi-language for document printing | This enables you to save and print descriptions and notes against key fields in SYSPRO for up to 80 languages. |
Available languages | Select the Configure List hyperlink to select up to 80 language codes you want to use within the system. |
Nationality | This indicates the nationality of your
site. Entering one of the reserved nationality codes (i.e. CAN, USA, AUS, RSA, UK) affects the display of certain fields (e.g. tax-related) within the system. You can override the nationality setting at company level (Company Maintenance). |
Use double byte character set (DBCS) | (Chinese-based system only). This facility ensures that
the correct SQL statements are issued when combining data
access from multiple tables with mixed collations. For example: one database is in English and the other is in Chinese, but both share the General Ledger tables (which are in Chinese). A text file (_SYSPRO_Collation.txt) resides in the \Base\Settings folder that contains details of all the database collations in SYSPRO (i.e. SYSPROAdmin.db). If the file is does not exist, SYSPRO regenerates it when next you log in. |
Site |
This is used by support personnel to identify your site. |
Diagnostics |
This is used to output a script or text file in the \Base\Settings folder to monitor and debug problems in e.net or SQL environments (see Diagnostic Codes). The option is enabled as soon as the setting is saved. |
Diagnostic note | This indicates a description for the diagnostic code selected. |
License usage options | These options enable you to monitor SYSPRO and CMS only license usage to more accurately predict when you are about to run out of licenses. |
Log when approach user limit | Enable this to log a record when the number of SYSPRO licenses used reaches the value set in the Log within x users of maximum field. |
Log within x users of maximum | Indicate the point at which you want to record a log
entry for SYSPRO license limits. For example: If you currently have a 50-user SYSPRO license and you enter 5 in this field, then an audit log entry is created when the 45th operator logs in. The log entry created is: Login attempted - license limit approached (System Audit log). |
Log when approach CMS user limit | Enable this to log a record when the number of CMS only users reaches the value set in the Log within x CMS users of maximum field. |
Log within x CMS users of maximum | Indicate the point at which you want to record a log
entry for CMS only user license
limits. For example: If you currently have a 10 CMS only user license and you enter 3 in this field, then an audit log entry is created when the 7th CMS only user operator logs in. The log entry created is: Login attempted - CMS license limit approached (System Audit log). |
Edit license information | Select this to configure system-wide license parameters. Changes are validated as part of the registration mechanism and will require you to update the license registration details for each company. |
Number of licensed users | This defines the maximum number of users allowed to run the system concurrently. |
Number of CMS only users | This indicates the number of CMS only users allowed to run the system concurrently. |
Number of SYSPRO POS users | This indicates the number of Point of Sale users allowed to run the system concurrently. |
Number of ODBC seats |
(C-ISAM) This defines the maximum number of users that may access the Universal Data Dictionary concurrently via ODBC. You won't be allowed to make any changes to the dictionary. |
Number of U/SQL Manager seats | (C-ISAM) This defines the maximum number of users that
may be running the U/SQL Manager concurrently. An entry other than zero indicates that you intend modifying the Universal Data Dictionary (UDD) using the U/SQL Manager software. |
Number of Dialog System seats | This indicates the number of Dialog System seats you have purchased (if you purchased the Micro Focus Dialog System) which allows you to customize screens using the Screen Customization Kit. |
Number of CALs | This indicates the number of Client Access Licenses (i.e. SQL Server seats) as defined by Microsoft that matches your license information. |
Number of Analytics Viewer seats |
This indicates the maximum number of users who may access the SYSPRO Analytics Viewer concurrently. |
Number of Report Designer seats |
This indicates the maximum number of users who can concurrently be defined as report designers and may therefore design reports using the SYSPRO Reporting Services program. |
Number of Licensed Companies (0=default) | This indicates the maximum number of companies that can be used concurrently on a site. |
Number of Espresso seats | This indicates the number of Espresso seats that you
are licensed to use. Espresso user licenses are allocated using the Espresso User Licenses program. |
Field | Description |
---|---|
User name options | |
User name represents | Indicate whether your entry at the User name login prompt refers to the operator code or whether the system must use the network user name to establish the operator code. |
User name default | Indicate the default entry you want to use at the User name field of the Login window. |
User name prompt | Indicate whether access to the User name field is allowed. |
User name history | Indicate whether you want the system to remember the
last 20 successful user names entered. These are stored in the Base\Settings folder on the server in the [UserName] section of the Login_Dialog_xxxx.TXT file (where xxxx is the network user name). |
Company options | |
Company default | Indicate the default entry you want to use at the Company field of the Login window. |
Company prompt | Indicate whether access to the Company field is allowed. |
Company history | Indicate whether you want the system to remember the
last 20 successful companies entered. These are stored in the Base\Settings folder on the server in the [Company] section of the Login_Dialog_xxxx.TXT file (where xxxx is the network user name). |
Field | Description | ||||||
---|---|---|---|---|---|---|---|
Database access | |||||||
System-wide configuration |
|
||||||
Database connection | |||||||
Authentication |
|
||||||
Connection method | Indicate whether you want to connect to the database using a direct SQL Server connection or using the ODBC Data Source Name. | ||||||
SQL Server name | This indicates the SQL Server name that will be used. This is typically the name of the computer on which SQL is running. | ||||||
Connection string | |||||||
ODBC Data source name | This indicates the name of the ODBC data source that will be used to connect to SQL Server when you load the system. | ||||||
System-wide database information | |||||||
Database | This indicates the database of SYSPRO's configuration tables. | ||||||
Table | This indicates the table within the configuration database that is used by the system to cross-reference each company to its relevant database. | ||||||
SQL Server system admin information | |||||||
Login | This indicates the administrator login with the authority to perform advanced SQL functions. This must be an account login that is a member of the sysadmin fixed server role. | ||||||
Password | This indicates the password assigned to the administrator login. | ||||||
Bulk insert code page | This indicates the CODEPAGE required when the BULK INSERT function is used if special characters exist that SQL Server needs to recognize. | ||||||
Bulk insert temp folder | This indicates the temporary folder for storing intermediate bulk copy format files (*.bcp). In a 3-tier environment, ensure that the temporary folder is available to both SQL server and the application tier. Typically, use a UNC address. |
Field | Description | ||||
---|---|---|---|---|---|
System date format | |||||
Edit system date format |
Select this to change the format in which you want all system dates to be displayed and printed within SYSPRO. You can override this date format at company level. Although your selection here does not affect the way in which dates are stored in the system (i.e. this is always in a CCYYMMDD format) there are instances where SYSPRO overrides your preferred date display format and shows dates in a CCYYMMDD format. This typically occurs in list views where the date column can be used for sorting purposes. |
||||
Presentation format | Indicate your preferred date display format. | ||||
User defined date formats |
|
||||
Long date format | This indicates how the system will display the long version of the date. It does not affect the way dates are physically stored on file, it merely provides an alternative way of viewing and printing them. You can override this date format at company level. | ||||
Short date format |
This indicates how the system will display the short version of the date. It does not affect the way dates are physically stored on file, it merely provides an alternative way of viewing and printing them. You can override this at company level. |
||||
Report date format | This indicates how dates will be represented on reports. It does not affect the way dates are physically stored on file, it merely provides an alternative way of viewing and printing them. You can override this at company level. | ||||
Test date |
The date entered here is used to display the samples in the date fields below. |
||||
Long date sample |
This indicates a sample of how the Long date format will appear in the system. |
||||
Short date sample |
This indicates a sample of how the Short date format will appear in the system. |
||||
Report date sample |
This indicates a sample of how the Report date format will appear in the system. |
You can tailor your date format using separators (e.g. / , -) as well as additional text within single quotation marks (e.g. 'Today is my birthday' dddd dd MM).
Field | Description | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Date key |
|
||||||||||||||||||||||||||
Time key |
|
Field | Description |
---|---|
Server-side folders | |
Programs folder |
This indicates the location of your IMPACT programs. |
Screens folder |
This indicates the location of your standard screensets. |
Temporary folder |
This indicates the folder that is used for creating temporary files typically used for sorting. |
Multimedia folder |
This indicates the default folder in which you should store all your multimedia files. If undefined, this defaults your working directory. Although this field is disabled on the client, you can use the Edit Client Configuration function to define the path on the client. |
APS data folder |
This indicates the folder in which the Requirements Planning module stores the files used by the Advanced Planning and Scheduling system (if installed). |
Custom server-side folders | |
Custom program folder |
This indicates the location of your customized programs. |
Custom screens folder |
This indicates the location of your customized screensets. |
Data server-side folders | |
Data folder 1 |
This indicates the 1st folder in which you want to store data files for your companies. |
Data folder 2 |
This indicates the 2nd folder in which you want to store data files for your companies. |
Data folder 3 |
This indicates the 3rd folder in which you want to store data files for your companies. |
Data folder 4 |
This indicates the 4th folder in which you want to store data files for your companies. |
Data folder 5 |
This indicates the 5th folder in which you want to store data files for your companies. |
Data folder 6 |
This indicates the 6th folder in which you want to store data files for your companies. |
Data folder 7 |
This indicates the 7th folder in which you want to store data files for your companies. |
Data folder 8 |
This indicates the 8th folder in which you want to store data files for your companies. |
Data folder 9 |
This indicates the 9th folder in which you want to store data files for your companies. |
Snapshot directory (for MRP) | This indicates the location of your Requirements
Planning snapshot files. These files are created when you take a new snapshot from within the Requirements Calculation program (if Requirements Planning is installed). |
Field | Description | ||||||
---|---|---|---|---|---|---|---|
Reporting | |||||||
Reporting configuration |
|
||||||
Database connection | |||||||
SQL Server name | Specify the name of the SQL Server hosting the database. | ||||||
Connection string | If you make use of a connection string, indicate the connection string here. | ||||||
Database authentication | |||||||
Reporting authentication |
|
||||||
Login | Specify the SQL authentication login here. | ||||||
Password | Specify the SQL authentication password here. | ||||||
Test SQL connection | Select this to ensure you can connect to SQL. | ||||||
Server-side configuration | See also Implementation. | ||||||
Reporting service | Define the reporting service address and port (for example, localhost:1979) | ||||||
Test service connectivity | Select this to ensure you can connect to the service. | ||||||
Scheduler authentication | Enter the scheduler authentication user name and password. These are the Windows Task Scheduler permissions that allow the operator to create and maintain schedules on the server. | ||||||
Document Printing |
These options are only available if you have enabled the Server-side reporting using SQL option and are only available for server-side printing. |
||||||
Automatically purge queue | Enable this option for the automatic purging of the document print queue. | ||||||
Days to keep queue item |
Enter the number of days for an item to remain in the queue before being automatically purged.
|
Field | Description |
---|---|
Notification address | Indicate the address of the Espresso Server (e.g. http://localhost/SYSPROEspresso). This will be used to push notifications to a user's devices. |
Exercise caution when changing any of your system options as the changes may adversely affect the running of your SYSPRO system. All changes to this program are logged to the Setup Amendment Journals program.
After making any changes on the Reporting tab, you need to restart the SRS Host services to apply your changes. The settings are only read once when the SRS Host services are started and remain in force until the services are restarted.
In an ISAM environment, the number of licensed companies is limited to 36 (i.e. a single character id in the range A-Z and 0-9).
In a SQL environment the number of licensed companies can be a combination of any 4 characters in the range A-Z and 0-9.
Application Help Panes provide step-by-step instructions for various functions within the program, including a brief overview of what the program does, what setup options are required and how to personalize the program. The intention is that the pane provides information that is uncluttered and easy to navigate.
You can embed an Application Help Pane:
in the main SYSPRO menu
in any program with panes, if not using roles
when adding a role layout in Design Mode.
Inserting Application Help
You would typically follow this procedure to display help for the current program in a customized pane that can be pinned to the program window.
Information includes step-by-step instructions for the various functions available within the program, including a brief overview of what the program does, what setup options are required and how to personalize the program.
Open the program for which you want to insert application help into a customized pane.
This functionality is only available for a program that has panes.
Right-click any form field.
You can also click the triangle menu icon that appears in the title area of a pane.
Select Insert Application Help from the context-sensitive menu.
The application help appears in a pane within your program. You can reposition the pane using the docking stickers or pin it to the program window.
Removing the Application Help pane
If you no longer want to display application help in a pane for your current program, you can simply remove it.
Select the Close icon in the right-hand corner of the application help pane.
Confirm that you want to delete the pane.