Configures a password for the company that will be requested whenever an operator attempts access.

Prevents unauthorized access to this company (useful if you are maintaining a company and want to restrict other operators from capturing data).

This does not affect operators currently accessing the company.

The message you want to display to any unauthorized operator attempting to access the company.

An additional hyperlink is available (Resolve GeoLocation from address) to resolve addresses using the long or short name.

Indicate the company's physical address to which goods must be delivered (used by the Purchase Orders module).

An additional hyperlink is available (Resolve GeoLocation from address) to resolve addresses using the long or short name.

Indicate the company tax registration number. This can be printed on delivery notes, invoices, statements and purchase orders.

Indicate your company registration number. This can only be printed on delivery notes, invoices, statements, creditor's remittance advices and purchase order requisitions.

This is the warehouse displayed as the default at most Warehouse fields in the system.

Specifying a default warehouse is useful if you are only using one warehouse in the system and do not want to have to re-enter the code repeatedly. You can override the default warehouse at operator level.

Indicate the default currency in which you want to process transactions within the system. You cannot change this currency once you have added the company.

Enter the description for the Local currency code assigned to the company.

It also determines the relationship between the General Ledger and the sub-ledgers with regard to the posting of the sub-ledger transactions into the General Ledger.

Once defined, you should not change the number of accounting periods per year, or you may lose historical information (i.e. the history buckets for transactions written to the files in the sub modules are not moved, adjusted or corrected when you change the accounting periods per year).

4	Indicates that the General Ledger Period end function must run after every 3 months of trading activity and all sub-ledgers to have 12 months in the year. Sub ledger transactions Posted to GL period Months 1, 2, 3 Period 1 Months 4, 5, 6 Period 2 Months 7, 8, 9 Period 3 Months 10, 11, 12 Period 4
6	Indicates that the General Ledger Period end function must run after every 2 months of trading activity (i.e. 6 times per year) and all sub-ledgers to have 12 months in the year. Sub ledger transactions Posted to GL period Months 1, 2 Period 1 Months 3, 4 Period 2 Months 5, 6 Period 3 Months 7, 8 Period 4 Months 9, 10 Period 5 Months 11, 12 Period 6
12	Indicates that the General Ledger Period end function must run after every month of trading activity (i.e. 12 times per year) and all sub-ledgers to have 12 months in the year. When you set your accounting periods to 12, Auditor's journals are posted to Period 13 and all Year end (YE) journals are posted to Period 14.
13	Indicates that the General Ledger Period end function must run after every four weeks of trading activity and all sub-ledgers to have 13 periods in the year.

This account is used by the system to correct an out-of-balance situation in the General Ledger. It does so by posting an entry to this account to correct the imbalance. The value posted can then be journalized out to the correct ledger code manually.

The following programs add a GL Account called FORCED if it doesn't exist on the GenMaster file: Company Maintenance, Add Company Wizard and Companies - login window (when it first creates the 00 record on ADMCTL).

Indicates the description for your forced balance account.

This account is updated with the net income/loss for the year when you run the Year end function of the General Ledger. It is also used if you select to close out your expense and revenue accounts when you run the year end.

Indicates the description for your retained earnings account.

Although always stored in a CCYYMMDD format, this option enables you to define how you want dates to be displayed and requested within SYSPRO, at company level.

Note that dates in forms are determined by the Date format only (i.e.DDMMYY or YYMMDD). The short/long date format is not applied to any date fields in forms.

This overrides the date format settings made within the System Setup program.

Your selection here provides an alternative way of viewing and printing dates and does not affect the way in which dates are physically stored on file.

Select how you want the system to display the long version of the date for this company.

Select how you want the system to display the short version of the date for this company.

Select how you want the system to display dates on reports printed within this company.

The date entered here is used by the samples below to confirm that you have correctly configured your user-defined dates.

Displays how the setting for the Long date format will appear in the system.

Displays how the setting for the Short date format will appear in the system.

Displays how the setting for the Report date format format will appear in the system.

Enables you to set your nationality code at company level (i.e. overrides the setting made within the System Setup program, unless this conflicts with an existing tax option that has been defined).

This indicates the nationality of your company (e.g. USA - United States of America; GB - Great Britain; AUS - Australia; CAN - Canada; RSA - South Africa).

The nationality entered here affects the display of region-specific fields within the system (e.g. tax).

Select the preferred emailing method within SYSPRO.

	In a mapped-drive environment you will need to define the network permissions to invoke an executable program over the network.

Microsoft Outlook	Uses Microsoft Outlook as your preferred method of sending email within SYSPRO. You would typically select this option if you want to use simple MAPI mail. This option cannot be used if Microsoft Outlook 2010 is installed.
Outlook using Outlook email client	Uses Microsoft Outlook with Outlook's rich email client interface as your preferred method of sending Email within SYSPRO. The system attempts to locate the SYSPROEmailClient.exe file in your \Base folder. If the file exists, it is executed and the email parameters are passed to it in XML format. The SYSPROEmailClient.exe file is a standalone executable file which you can replace with your own custom UserEmailClient.exe file, if required. You would typically do this if you were using an email system that is not Outlook. Outlook's rich email client interface is only invoked if you have Microsoft Office Outlook 2003 (or later) installed on the client machine. If you have Microsoft Office 2003 you need to download Microsoft Office 2003 PIAs from the Microsoft website. This is not required if you have Microsoft Office 2007. Earlier versions of Outlook use the old-style email client interface. You can, at a later stage, revert to using simple MAPI mail by selecting the Microsoft Outlook option if required.
Macro using VBScript	Uses any COM-aware email subsystem (e.g. Groupwise or Lotus Notes) to send email in SYSPRO. This is achieved by selecting the Macro function to define VBScript macros for events (see Send Email). These events enable you to indicate which script to run when each of the following options are selected: Send Message - OnSendMessage Check Names - OnCheckNames To - OnToButton CC - OnCcButton Macro using VBScript is not supported for SRS document printing.

Indicates the default IP address of the specific SMTP server that SYSPRO will use to send messages.

Indicates the default email address of the sender of the message.

Enter the user name for the email account specified above.

Enter the password for the email account specified above.

Indicate the server port to be used.

You can enable job logging selectively by module and program using the Security Access function of the Operator Group Maintenance program.

Enabling this option may lead to excessive entries in the log from automated and semi-automated processes.

Disable this option if you don't want to create log entries for business objects invoked from e.net Solutions, Web-based applications, DFM and VBScripting (from forms, customized panes, etc).

If a regular SYSPRO program (e.g. Sales Order Entry) invokes a business object to perform a database update or query, then a job log entry is created as normal.

Job logging entries are not created when running SRS reports.

This applies to following journals:

You would typically use this option to indicate why some entries were included/excluded from a report, as well as if you print multiple copies of the same report with different report options.

SRS Reports will take longer to run when you select this option.

(See the Shared inventory considerations topic (Custom Forms Overview).

You won't be able to view any Inventory multimedia that is configured in the individual shared companies.

Note that this does not rename the multimedia files. It simply alters the %key value returned for Multimedia.

This applies when you use the %key variable in a multi-media object path. Depending on the %key, objects may not be accessible when this option is not enabled.

You can still change the number of decimals for individual tax codes which will override your selection here.

	Only SRS reports support the use of 5 decimal places. For all documents on which the tax rate is printed, the use of 5 decimal places is supported on Standard, Word and SRS documents.

These options enable you to share inventories across companies with different currencies and general ledgers across companies with differing accounting periods.

If both Inventory and General Ledger are shared, then the Inventory Interface setup in the Inventory 'holding' company is used to determine the General Ledger accounts to which transactions processed using the Inventory Movements program are posted.

If only Inventory is shared, then Inventory transactions update the files of the 'holding' company and the General Ledger side of the transactions are posted to that company's own General Ledger files.

It is not advisable to share Inventory files across companies that have different base currencies (generally accepted accounting practice assumes that the value of inventory is stated in the local currency of the company). However, if no transactions are processed across the companies' warehouses (e.g. you want to share Inventory for query purposes only) then this can be done without compromising the integrity of the General Ledger.

Refer to Shared files and tables for a list of files/tables which are shared.

Indicate the company that will be the holding company for all the general ledger master, history and detail transactions. This defaults to your current company, but can be changed.

You would typically use this facility if you want to produce consolidated financial reports for more than one company using the Financial Report Writer.

Although general ledger data for each company is stored in the same physical database, only the Financial Report Writer can access the data of other companies.

	If you have defined multiple data paths then ensure that the data paths defined for the sharing companies match those of the holding company. Ensure that the company control files are located in the same working directory for all companies sharing the general ledger database. You cannot share general ledger data between C-ISAM-based and SQL Server-based companies.

Indicate the company that will be the holding company for inventory data. This defaults to your current company, but can be changed.

You would typically use this facility if all companies sell the same inventory and you require a consolidated view of the stock holding of all companies.

If Bill of Materials is installed in the 'holding' company, then the sharing companies must have access to bill of material data. If Material Requirements Planning is installed, then the Requirements Calculation uses the inventory and bill of materials data from the Inventory 'holding' company, together with the sources of supply and demand from the company running the Requirements Calculation. Each company retains separate Purchase Order, Sales Order, MRP and Work in Progress data.

All numeric formatting is also applied to any numeric custom form fields added.

Indicate the type of decimal character you want to use for numeric fields that contains decimals (e.g. values, costs, prices, quantities, units of measure conversion factors, currency conversion factors, etc).

This character must be different from the 1000's separator character.

You can override this at operator level (Operator Maintenance).

In a client/server environment, the decimal character entered here must match the character defined in the Regional Settings on the client machine. Otherwise incorrect values could be saved for transaction entries processed in SYSPRO.

An error is displayed in programs that include an editable data grid in which there is at least one numeric column, when the decimal character in the Regional Settings on the client does not match the decimal character defined here.

Windows Regional Settings affect the formatting of numbers in SYSPRO graphs and currency values in SYSPRO Analytics.

In addition, variables have been added to the System Information section of all SRS reports to indicate the number of decimals to display (DecimalsToDisplay) and the decimal character to use (DecimalCharacter). This, in conjunction with the SeparatorToUse variable, can be used to format reports to meet your requirements.

If you define the decimal character as a comma (,) then entering a dot (.) is translated into a comma. This is to accommodate the use of numeric keypads which only have a dot (.) to indicate a decimal point. This also applies to the Regional Settings on the client machine.

This character must be different from the decimal character.

Reports changed to support extended field sizes remain visually unchanged unless the printed values exceed the available print space, in which case the report print line could change to print two lines instead of one.

You can override these settings at operator level.

If you enter zero in this field then decimals are removed from entry and display/print fields when values are used.

	The number of decimals to show in values defaults to 2 and all values are always held to 2 decimal places, regardless of any setting.

This does not affect free format stationery that assumes a minimum of two decimals for any price field, and three decimals for any Inventory unit cost field.

Reports changed to support extended field sizes remain visually unchanged unless the printed values exceed the available print space, in which case the report print line could change to print two lines instead of one.

This does not affect free format stationary, which assumes a minimum of two decimals for any price field and three decimals for any inventory unit cost field.

The option: Maximum decimals to show for price/cost (System-wide Personalization) controls the number of decimal zeroes displayed in price and cost list view columns.

This applies to the printing of all Work in Progress operation times (such as run time, teardown time, wait time, etc.) on reports. It defaults to four decimal places, but can be set anywhere from zero to six.

You would typically use multiple folders to store large files on a different physical drive or file system.

You would typically use this function if you have migrated your data to SQL Server, but are not yet in possession of a license number.

You should not process any transactions as they will be posted to the C-ISAM database and will no longer match the SQL Server data. It will require you to either remove the SQL Server database or remove the data in the tables and redo the migration to SQL.

A wizard guides you through this process (SQL Company Setup).

This must reflect the company name as specified on the registration form supplied with the software.

The year in which your Software License Agreement expires.

The month in which your license expires (if specified within the terms of your Software License Agreement). This applies to temporary licenses.

The registration number assigned to your company.

Imports the LICENSE.XML file into your system (see License Import Wizard).

You must run this function to access any e.net Business Object or Web-based Application and when using the Document Flow Manager.

	You must use the Companies - login window program if you want to import a 'DEMO FOR xxx' license and then deselect modules that are not licensed. This functionality is not available in the Company Maintenance program.

The number of users currently licensed to use the system as well as the number of licensed seats for:

You maintain these numbers using the System Setup program.

Espresso user licenses are allocated using the Espresso User Licenses program.

This pane displays the list of available modules, indicating the ones that are installed.

Your selections must match the list of modules indicated on your Software License Agreement.