Manager Controls: Company Details Maintenance

Last Modified Date and Time

Company and System Settings. Last modified date and time. {MCDFILE.MCDMOD date datetime 8}

Print

To print a report of all company details. Right-click for report destination.

Revert to Saved

To edit the company details. No other users can be operating on the data file.

Save Changes

To edit the company details. No other users can be operating on the data file.

Sales Discount Descriptions 1 to 20

Company and System Settings. Discount class 1 to 20 description. {MCDFILE.MCDDIS1 char 15} to {MCDFILE.MCDDIS20 char 15}

Each Part is assigned a discount class of 0 to 20 (1 is default). Each customer is assigned discount rates for each class (other than 0 which is taken to be zero discount rate). When Sales orders are prepared the appropriate discount for the Part to that Customer is then applied by default, plus any quantity additional discount. The 20 non-zero discount classes can be assigned descriptive text as an ‘aide memoir’ during window entry. 15 characters are permitted for each descriptor.

User Defined Field Descriptions

Company and System Settings. User defined field descriptions row (columns Pa1 to Pa4 for ‘Pa’rts, ‘Cu’stomers, ‘Su’ppliers, ‘Jo’bs, ‘So’s, ‘Po’s, ‘Wo’s). {MCDFILE.MCDUSED row}

Parts, Customers, Suppliers, Jobs and Estimates, Sales orders and Quotations, Purchase Orders and RFQs, and Work Orders have 4 user defined fields. Field 1 is a single character, 2 is 4 characters, 3 is 18 characters and 4 is 30 characters. You can enter here a description for each of these fields and this description will be reproduced on windows that display the fields. These fields are provided typically for custom search and/or reporting requirements and are not otherwise processed by the system.

CUSTOM CAPABILITY: These descriptions can be used on any report, typically in square-bracket notation. They are held in a single row variable and can be expressed as:

[MCDFILE.MCDUSED.Pa1] for the parts 1 description
[MCDFILE.MCDUSED.Cu1] for the customers 1 description
[MCDFILE.MCDUSED.Su1] for the suppliers 1 description
[MCDFILE.MCDUSED.Jo1] for the jobs 1 description
[MCDFILE.MCDUSED.So1] for the sales orders 1 description
[MCDFILE.MCDUSED.Po1] for the purchase orders 1 description
[MCDFILE.MCDUSED.Wo1] for the work order 1 description

TIP: You can selectively get the system to inherit master record user defined field data onto documents. This is done by setting the following system options:

• optJobInheritsUserFields
• optPOInheritsUserFields
• optSOInheritsUserFields
• optWOInheritsUserFields

The option value is set to 1234, or any combination of those numbers. It will cause those Job, PO, SO or WO user defined fields to be inherited from the customer, supplier, customer or assembly part fields.

Purchase Order Receiving Quantity

Company and System Settings. Goods rec. qty. variance % limit. {MCDFILE.MCDRECP number 2dpShortnum}

During the goods receiving process, you may wish to have the option of completing a PO line item with a delivered quantity that is not exactly the ordered quantity. This can be useful to avoid leaving trivial quantities on back-order or, if the received quantity is in excess of that ordered, having to adjust the order prior to receiving it. To provide this feature, you can enter a variance limit in both quantity percent and value terms. For each PO line item the system will apply the lower of the two values and permit, after a warning, line item completion with that transaction. Purchase history and Inventory will reflect the actual receipt quantity.

Purchase Order Receiving Value

Company and System Settings. Goods rec. qty. variance value limit. {MCDFILE.MCDRECV number 2dpShortnum}

Work Order Kitting Quantity

Company and System Settings. WO kit variance % permissible without creating shortages. {MCDFILE.MCDWOKV number 2dpShortnum}

During the Work Order kitting process, you may wish to have the option of issuing a quantity that is greater or less than the BoM quantity. This can be useful where BoMs reflect average use of raw material. Works history and Inventory will reflect the actual kit quantity.

WARNING: If a kitting variance is permitted, care should be taken when returning a kit, as the system presumes the BoM kit quantity has been kitted.

Work Order Receiving Additional Quantity

Company and System Settings. WO receiving variance %. {MCDFILE.MCDWORV number 2dpShortnum}

During the WO assembly receiving process, you may wish to have the option of receiving a quantity that is greater than the ordered and kitted quantity. This can be useful where BoMs reflect average wastage of raw material. Works history and Inventory will reflect the actual receipt quantity.

Sales Dispatch Quantity

Company and System Settings. SO dispatch qty. variance % quantity limit. {MCDFILE.MCDSOVQ number 2dpShortnum}

During the dispatch process, you may wish to have the option of completing a SO line item with a dispatched quantity that is not exactly the ordered quantity. This can be useful to avoid leaving trivial quantities on back-order or, if the dispatched quantity is in excess of that ordered, having to adjust the order prior to receiving it. To provide this feature, you can enter a variance limit in both quantity percent and value terms. For each SO line item the system will apply the lower of the two values and permit, after a warning, line item completion with that transaction. Sales history and Inventory will reflect the actual dispatch quantity.

TIP: This feature is usually only useful where you are selling by length and billing by weight, for example. In other words is valid when the Sales Order quantity is only an estimate of the dispatch quantity.

Sales Dispatch Value

Company and System Settings. SO dispatch qty. variance % quantity limit. {MCDFILE.MCDSOVQ number 2dpShortnum}

Batch Additional on Dispatch

Company and System Settings. Batch variance % permissible on dispatch. {MCDFILE.MCDBATV number 2dpShortnum}

During the dispatch process, you may wish to have the option of completing a SO line item with a dispatched quantity that is not exactly the quantity available from a whole batch. This can be useful to avoid having to split batches on dispatch where trivial inaccuracies in quantity of a batch is the case.

TIP: This feature is usually only useful where you have complex sales UoM multipliers and where measuring accuracy of batch quantities is not as great as the resolutions of quantities in the system. For example, where you are mixing chemicals by weight but you are selling in quantities of volume.

System Currency Symbol

Company and System Settings. Standard currency symbol. {MCDFILE.MCDSTCU char 3}

Caliach Vision is a multi-currency system enabling you to create POs and SOs in any currency defined in Currencies. The symbol entered here is the local currency that you normally work in. The text is used in documents. Any Sales or Purchase record has the currency code (or symbol) written to it. Hence, if you change the standard currency symbol the system will warn you and, if confirmed, replace the old code on all records with the new one. This can take some considerable time if there are many history and/or ledger transaction records.

WARNING: If the updating process is running, you MUST NOT INTERRUPT the processing, however long it takes. If you do, the Datafile must be discarded and a backup used.

TIP: Alternatively, you can change your local currency to a new one. This special process does not just change the currency symbol but migrates all the appropriate values stored in the data to the new currency. For further details see the Local Currency Migration window.

System Currency Decimal Character

Company and System Settings. Monetary cent character (e.g. p). {MCDFILE.MCDCENT char 1}

TIP: If you use the # (hash or pound) character as your currency decimal character the cent portion of an amount printed in words on documents such as sales orders, invoices and cheques is suppressed. This feature is provided for large scale currencies such as Rupees and Yen.

System Currency Text

Company and System Settings. Standard currency text. {MCDFILE.MCDSTCT char 20}

Sales Tax Name

Company and System Settings. Sales Tax abbreviated name for Invoices. {MCDFILE.MCDVAT char 4}

Registration Number

Company and System Settings. Sales Tax (VAT) registration number. {MCDFILE.MCDTAXN char 30}

VAT (for European users) registration is a mandatory requirement on invoice documents. If nothing is entered here the VAT registration number line is not printed on invoices. The I.D is used to identify the type of tax on documents and windows.

Default sales non-part tax class

Company and System Settings. Default sales non-part tax class. {MCDFILE.MCDDTNS char 1} See the Tax Maintenance window for full details of the tax handling system.

Default purchase non-part tax class

Company and System Settings. Default purchase non-part tax class. {MCDFILE.MCDDTNP char 1}

Default sales part tax class

Company and System Settings. Default sales part tax class. {MCDFILE.MCDDTPS char 1}

Default purchase part tax class

Company and System Settings. Default purchase part tax class. {MCDFILE.MCDDTPP char 1}

Default customer regime

Company and System Settings. Default customer tax regime. {MCDFILE.MCDDTCR char 6} See the Tax Maintenance window for full details of the tax handling system.

Default supplier regime

Company and System Settings. Default supplier tax regime. {MCDFILE.MCDDTSR char 6}

Part Price Currency 1 to 5 Code

Company and System Settings. Part sales currency price 1 to 5 currency. {MCDFILE.MCDPC1 to 5 char 3}

5 currency parts pricing is possible in the parts master. Each part can be given a local sales price (in standard currency) and five prices in foreign currencies. You must enter here the currencies you want to apply to the 5 currency prices. They must be pre-defined as currencies in the appropriate “System Manager” section. When a SO is created in a foreign currency and that currency is one of these five and there is a non-zero price in the appropriate part currency price field, that price will be applied to the SO line item. Otherwise, the current currency exchange rate will be applied to the local price.

Currency Name

Currency Rates. Currency name. {CURFILE.CURNAME char 20}

Default non-part item sales commission class

Company and System Settings. Commission class default for non-part items (for choice of commission agent applicability on Job and SO non-part items). {MCDFILE.MCDNPCL char 1} See the Commissioned Sales Agents Maintenance window for full details of the commission handling system.

Tax Maintenance

Click to review or modify the tax structure and rates. It will open the Tax Maintenance window.

Currency Maintenance

Click to review or modify currencies. It will open the Currency Control window.

Commissioned Agents Maintenance

Click to review or modify commission classes and agents.. It will open the Commissioned Sales Agents Maintenance window.

Parent number Prefix in SO Configuration

Company and System Settings. Prefix characters for parent part number created in SO configuration. {MCDFILE.MCDCONL char 3}

When you use Sales Order Configuration to create a SO specific assembly from a set of options, the resultant assembly is given a part number constructed in the form XXX-123456-789. Where “XXX” is the prefix entered here, “123456” is the SO number and “789” is the line item of the order. The prefix can not contain a “WO” as this would cause a clash with work order operation outwork purchasing. If the prefix is left blank, SO Configuration will not be accessible to any user on the system. Sales Order Configuration is set up in the Sales Order Configuration Options window.

Parent number Prefix in Job Configuration

Company and System Settings. Prefix characters for parent part number created in Job configuration. {MCDFILE.MCDCONJ char 3} See above for more details.

Maximum BoM Structural Depth

Company and System Settings. Maximum BoM level number. {MCDFILE.MCDLLNO integer shortint}

Having very deep multi-level Bills of materials may be appropriate for your products or manufacturing process. However, the deeper the Bills the longer processing can take and the greater the number of transactions needed to create an end product from purchased components or raw materials. As a deterrent against excessive BoM depth the manager can set a limit to the depth at which Bills can be created. Components cannot be added to a Parent part if the Parent equals or exceeds the limit entered here. In any event the maximum is 99. It is suggested that this is initially set low until it is found to be inadequate. In this way the business can start with optimum performance. When, during BoM maintenance, the limit is encountered the System Manager may increase the Maximum BoM Level value.

Goods Receiving Overhead Rate

Company and System Settings. Goods receiving default overhead percent (can be overridden by PTMROVR) {MCDFILE.MCDPOOV number 2dpShortnum}

This is an overhead (burden) rate that is applied to all purchased parts during Cost Roll-Up or when their price is confirmed after a PO receipt. If the part has a non-zero individual rate (PTMROVR), then this will apply rather than this global rate. If PTMPOVR is negative, the overhead rate will be zero. The subsequent overhead amount is stored in the “Receiving overhead” field in the Parts Master record. The rate can be any range from 0.00 to 999.99% and applies to the prime (material) cost. This rate can be used to account for goods receiving costs such as inward freight, PO and stores administration, etc..

Work Order Receiving Overhead Rate

Company and System Settings. WO receiving default overhead percent (can be overridden by PTMROVR). {MCDFILE.MCDWOOV number 2dpShortnum}

This is an overhead (burden) rate that is applied in a similar manner to the Goods receiving overhead rate but in this case applies to assembly parts. It is only used during Cost Roll-Up. If the part has a non-zero individual rate (PTMROVR), then this will apply rather than this global rate. If PTMPOVR is negative, the overhead rate will be zero. The subsequent overhead amount is stored in the same “Receiving overhead” field in the Parts Master record. The rate can be any range from 0.00 to 999.99% and applies to the This-level material, labour and labour overhead cost. This rate can be used to account for WO handling and stores costs.

Mass Units Descriptor

Company and System Settings. Mass units for window/report display. {MCDFILE.MCDMASU char 4}

This is a window and report descriptor for the units of mass (weight) used throughout the system. Parts can be given a value for their mass and process route operations can be given a value of mass change. You should settle on a standard for your business, e.g. Kgs., Lbs. etc..

Batch Number Prefix Character

Company and System Settings. Batch number prefix character. {MCDFILE.MCDBATC char 1}

Batch numbers are seven characters long, created automatically by the system for inward part inventory transactions when the part is flagged as tracked. There are two batch numbering system options, controlled by a system preference, both generate a number up to 6 digits long. The prefix character is appended to the generated number. You can use this prefix to group batch numbers. You are restricted to numerals 0 through 9 and upper case letters A through Z only. In addition, you can not use any character that has already been used and is currently on file. See also System Preferences topic for control of the batch numbering system.

Purchase Part Performance Factors

Factors are used to load the four Purchase parts performance indicators to produce the overall performance of the supplier for a part. The factors are used on the purchase parts maintenance window and during the global changes function for calculating performance. The factors must add up to 100. If all four are given the value 25, then each indicator will be equally weighted. If one is given 100 and the others 0, the overall rating for the supplier will be solely based on that indicator.

Delivery Speed

Company and System Settings. Delivery speed performance factor (0-100). {MCDFILE.MCDPPDF integer shortint}

Delivery Reliability

Company and System Settings. Delivery reliability performance factor (0-100). {MCDFILE.MCDPPRF integer shortint}

Price

Company and System Settings. Price performance factor (0-100). {MCDFILE.MCDPPPF integer shortint}

Quality

Company and System Settings. Quality performance factor (0-100). {MCDFILE.MCDPPQF integer shortint}

Material Costing Method

When costs for parts are updated either in product costing roll-up or updating costs, the basis on which purchased parts and material current costs are updated is governed by your selection here. Last price paid simply takes the unit cost in the last purchase history record. First in First out (FIFO) takes account of the current inventory physical quantity and calculates the current costs based on the preceding history of purchases assuming that receipts into inventory are consumed in the order they are received. Last in First out (LIFO) uses purchase history in the same way as FIFO but assumes that newest receipts are consumed first. Average of history uses all purchase history records for the part and calculates a weighted average cost for the part. See the Product Costing window for more details.

Last price paid

Company and System Settings. Stock valuation method (0=Last,1=FIFO,2=LIFO,3=Average). {MCDFILE.MCDVALU integer shortint}

First In First Out

Company and System Settings. Stock valuation method (0=Last,1=FIFO,2=LIFO,3=Average). {MCDFILE.MCDVALU integer shortint}

Last In First Out

Company and System Settings. Stock valuation method (0=Last,1=FIFO,2=LIFO,3=Average). {MCDFILE.MCDVALU integer shortint}

Average of history

Company and System Settings. Stock valuation method (0=Last,1=FIFO,2=LIFO,3=Average). {MCDFILE.MCDVALU integer shortint}

ABC Class Value Breaks

The ABC codes for parts can be assigned automatically as part of MRP processing. The total value of the recommendations from the MRP plan (see MRP processing help) on a “This-level” basis is calculated. Then the parts accounting for the most ‘A value break’ value of the total are given ‘A’ class, those remaining that account for above ‘B value break’ value of the total are given ‘B’ class, those remaining that account for above ‘C value break’ value of the total are given ‘C’ class. Parts contributing less than ‘C value break’ or are not involved in the MRP results are cleared of any class. When editing ‘A’ must be greater than ‘B’ which must be greater than ‘C’.

A Class

Company and System Settings. ABC class A percent break. {MCDFILE.MCDABCA integer shortint}

B Class

Company and System Settings. ABC class B percent break. {MCDFILE.MCDABCB integer shortint}

C Class

Company and System Settings. ABC class percent break. {MCDFILE.MCDABCC integer shortint}

Stock Unit of Measure

Company and System Settings. Default stock unit of measure. {MCDFILE.MCDSTUM char 6}

This appears for new parts on the Parts master maintenance window and can be up to 6 characters in length.

Delivery Point Code

Company and System Settings. Default delivery point code. {MCDFILE.MCDPDPC char 2}

This is the code identifying the delivery data record that will be applied, by default, to all purchase orders when being created. The delivery details must be pre-defined.

Country Code

Company and System Settings. Default country code. {MCDFILE.MCDCOCD char 3}

This code must be pre-defined in the Country codes maintenance window and is, by default, applied to new customer and supplier entries.

Country Name

Country Definitions. Country title. {CONFILE.CONTITL char 30}

Quotation validity days

Company and System Settings. Default quotation validity days. {MCDFILE.MCDQVAD integer}

Payment Days

Company and System Settings. Default payment days for invoices. {MCDFILE.MCDTMDA number 0dpShortnum}

Days

Company and System Settings. Customer payment months rather than days. {MCDFILE.MCDCUSM boolean}

You can choose to either apply Customer payment Days or Months by selecting the appropriate radio button.

WARNING: The Days or Months option applies to specifically entered payment and quick-payment days for customers as well as the default. If you change, make sure the values are appropriate. The system will permit a payment period of 30 months! Use Global Changes.

Months

Company and System Settings. Customer payment months rather than days. {MCDFILE.MCDCUSM boolean}

Quick-payment days

Company and System Settings. SO or Job default quick-payment days (or months) for invoices (0 = same as payment days). {MCDFILE.MCDQPDA number 0dpShortnum}

Customer Pay Days From

Company and System Settings. Customer payment days from type (0=Today,1=Month-end,2=Period-end). {MCDFILE.MCDPAYT integer shortint}

You have the option of choosing the point from which the default payment date is calculated for Invoices. The default is to calculate the date from Today, i.e. the Invoice date. Otherwise you can have the date calculated as the payment days from the end of the current calendar month or the current sales ledger period-end. Period-end is the same as Month-end when you do not have the Ledgers license option.

Payment Terms

Company and System Settings. Default sales order payment terms. {MCDFILE.MCDTERM char 1000}

This is the default text (up to 1000 characters) that will be entered in each new Quotation or Sales Order if there is no specific Customer Payment Terms.

Part Index 1 Code

Company and System Settings. Default part index code 1. {MCDFILE.MCDDPX1 char 4}

These are the default index codes assigned to new Parts, Customers and Suppliers. These fields must be filled.

Part Index 2 Code

Company and System Settings. Default part index code 2. {MCDFILE.MCDDPX2 char 4}

Customer Index 1 Code

Company and System Settings. Default customer index code 1. {MCDFILE.MCDDCX1 char 4}

Customer Index 2 Code

Company and System Settings. Default customer index code 2. {MCDFILE.MCDDCX2 char 4}

Supplier Index 1 Code

Company and System Settings. Default supplier index code 1. {MCDFILE.MCDDSX1 char 4}

Supplier Index 2 Code

Company and System Settings. Default supplier index code 2. {MCDFILE.MCDDSX2 char 4}

Index Description

Index and Other Codes. Index code, scrap reason or QA test description (must have at least 1 character). {IDXFILE.IDXDESC char 255}

Countries

Click to review or modify the countries. It will open the Country Maintenance window.

Index Codes

Click to review or modify the index codes. It will open the Index and Other Code Maintenance window.

Date Format Style

Company and System Settings. Date presentation style of user. {MCDFILE.MCDATES char 8}

The system allows you to determine the format of dates on windows and reports. A code can be entered in this field to determine the date style. The code is made up of the following characters:

• Y = the year (93)
• y = the year with century (1993)
• C = the century part of the year (19)
• M = the month number (01)
• m = the three letter abbreviation of the month (JAN)
• n = the month in full text (January)
• D = the day number of the date (15)
• d = the day as text (15th)
• W = the day of the week (5)
• w = the day of the week (Friday)

Examples are as follows:

• m D,y displays JAN 15,1993
  D m y displays 15 JAN 1993
• M/D/Y displays 1/15/93
• YMD displays 930115
• D-m-19Y displays 15-JAN-1993

WARNING: All Caliach Vision date entry fields, list and report data are assumed to be no longer than 12 characters. You should therefore refrain from using the text style options that will inevitably cause some dates to exceed this limit.

TIP: There is also an option that can be used to extend time and datetime data to show Seconds and/or Centi-Seconds. optTimeShowSecs when set to 1 or 2 will show time and datetime data with seconds (1) and centiseconds (2) added. Warning: columns in lists and reports may overflow.

System Separators

Company and System Settings. System separator characters (5 characters: 1 = decimal point, 2 = thousands separator, 3 = function separator, 4 = import/export decimal point, 5 = import/export comma delimiter). {MCDFILE.MCDDPCR char 5}

You can change the usual . (full-stop, period mark) character as the decimal separator in numbers displayed and printed in the entire system. For some European countries a , (comma) character is used. (E.g. 10,50 for the more normal 10.50). There is a limited range of characters you can use. They are:

!”#$% ‘()*+,-.

Take great care with using these as they can cause a great deal of confusion. The use of the character you set here applies only to the use of a particular datafile and only within the system.

You can also change the usual , (comma) character as the thousands separator in long numbers displayed and printed in the system. For some European countries a . (full-stop, period mark) character is used. (E.g. 1.000.000,00 for the more normal 1,000,000.00).

Financial Year End

Company and System Settings. Financial year end (used in some date calculations). Actual year is unimportant. {MCDFILE.MCDDFYE date date1980}

Starting Day of the Week

Company and System Settings. First day of the week (used in date calculations) 1=Mon. {MCDFILE.MCDDWS integer shortint}

Base Language Code

Company and System Settings. Local base language: Use ISO 631-1 language code. e.g. en. {MCDFILE.MCDLANL char 2}

Base Language Name

Company and System Settings. Local base language name. e.g. English. {MCDFILE.MCDLANN char 100}

Language Swap Languages

Company and System Settings. Language Swap code,name; language pairs e.g. fr,French;th,Thai. {MCDFILE.MCDSWAP char 1000}

For details see Introduction to the Language Swap System.

Extreme character Unicode (hex)

Company and System Settings. Extreme Unicode character for searches in hex format up to 10FFFF. {MCDFILE.MCDXUNI char 6}

When searches are made and you enter a search range in a typical report selection window, if you don’t enter anything in the to range field the system will enter for you a single character that is presumed to be greater, in search terms, than the values in the data. To accommodate the universal character system of Unicode and when you use characters which are from high Unicode values, you may need to choose a higher value for this than our 221E default value. The maximum you can enter is 10FFFF and what you enter must be in hexadecimal format.

Dispatch Note

Manager Control Numbers. Last Dispatch Note number used. {MCNFILE.MCNDESP number 0dpShortnum}

Sales Invoice

Manager Control Numbers. Last Invoice number used. {MCNFILE.MCNINNO number 0dpShortnum}

Purchase Order

Manager Control Numbers. Last Purchase Order number used. {MCNFILE.MCNPONO number 0dpShortnum}

Sales Order

Manager Control Numbers. Last Sales Order number used. {MCNFILE.MCNSONO number 0dpShortnum}

Work Order

Manager Control Numbers. Last Work Order number used. {MCNFILE.MCNWONO number 0dpShortnum}

Job

Manager Control Numbers. Last Job number used. {MCNFILE.MCNJOBS number 0dpShortnum}

Batch

Manager Control Numbers. Last Batch number used. {MCNFILE.MCNBATC number 0dpShortnum}

Goods Received Note or GRN

Manager Control Numbers. Last PO Return Note Number used. {MCNFILE.MCNRENO number 0dpShortnum}

Return Note

Manager Control Numbers. Last PO Return Note Number used. {MCNFILE.MCNRENO number 0dpShortnum}

Non-Conformance Report or NCR

Manager Control Numbers. Last Non-Conformance Report number used. {MCNFILE.MCNNCR number 0dpShortnum}

Stock Transfer Document

Manager Control Numbers. Last Stock transfer number. {MCNFILE.MCNTRS number 0dpShortnum}

Marketing Business ID

Manager Control Numbers. Last Marketing Company created. {MCNFILE.MCNDEA number}

Marketing Contact ID

Manager Control Numbers. Last Marketing Contact created. {MCNFILE.MCNDEC number}

Additional Address

Manager Control Numbers. Last Additional Address serial number. {MCNFILE.MCNCAD number}

Quality Assurance Event

Manager Control Numbers. Last Quality Assurance event serial number. {MCNFILE.MCNQAH number}

Shipping Load

Manager Control Numbers. Last Shipping Load number. {MCNFILE.MCNLOAD number}

User Sequence 1 to 5

Manager Control Numbers. Last User 1 to 5 sequence number used. {MCNFILE.MCNUSE1 to 5 number}

Last Modified Date and Time

Manager Control Numbers. Last modified date and time. {MCNFILE.MCNMOD date datetime 8}

Revert to Latest Numbers

Re-reads the latest serial number data from the database and overwrites any changes to numbers you may have made and not saved.

Save Changes to Numbers

Saves any changes to document numbers you may have made. You must be the only users connected to the data file.

Period Dates

All three sets of period start dates are displayed on this window as they are part of the Company details file. However, they can not be changed. These dates are generated automatically when they are rolled-over during the period-end routine.

Stock Usage Period Start Dates

Company and System Settings. Part Usage period 1 to 3 start date. {MCDFILE.MCDP1DA date date1980} to {MCDFILE.MCDP3DA date date1980}

Within the Parts master file data is maintained on the consumption of parts from inventory (stock) for three periods of time: Period 1 is from its start date to today’s date; Period 2 is from its start date up to, but not including, Period 1’s start date; and Period 3 is from its start date up to, but not including, Period 2’s start date.

Customer Sales Period Start Dates

Company and System Settings. Customer period 1 to 3 start date. {MCDFILE.MCDCPD1 date date1980} to {MCDFILE.MCDCPD3 date date1980}

Supplier Receipts Period Start Dates

Company and System Settings. Supplier period 1 to 3 start date. {MCDFILE.MCDSPD1 date date1980} to {MCDFILE.MCDSPD3 date date1980}

Support Service

Company and System Settings. Support source identification (controls default update FTP site and fault email address). {MCDFILE.MCDSUPT integer longint}

NOTE: If there are language variants of the program, then you should set this to the language of your installation so that you receive updates in the appropriatly language.

Support Server Access User Name

Company and System Settings. CMS Internet upgrade ftp server access username. {MCDFILE.MCDCMSU char 64}

Convenience Functions

You can use this to copy or move certain directories of the Caliach Vision installation from their local installation location to the datafile directory, typically on a server. The contents of these directories will then be common to all users attached to the datafile. This can be useful to ensure backups are made regularly and it can be much more convenient for system management. However, using local directories will reduce network traffic. Moving a directory, rather than copying it will delete the local files. The process operates recursively on directories to any level.

Print License Order Form

To print a copy of the License Order form. Right-click to select report destination.