Navigation:  Business Operations > System Configuration >

Configuration

Training Manuals Alphabetical Function List Back Print this Topic Previous topicOne level upNext topic
Show/Hide Hidden Text

On this tab the following fields can be viewed:

 

hmtoggle_plus1Additional Cost Percentage Default

This field keeps a default additional cost percentage. When a purchase order line is released via the released purchase order generation function, and the freight term specified on the purchase order line allows additional costs, this percentage will automatically be defaulted.

It can still be amended.

hmtoggle_plus1Allow Cheque Payments To Foreign Currency

This setting relates to the Creditors function.  This field allows for a Yes/No setting and governs whether creditors invoices rendered in a foreign currency can be settled by means of a cheque payment.

 

If set to "Yes", the settlement method on the creditors invoice line link will allow a selection of "Cheque".  The cheque will still be printed in the base currency and the decision is thus guided by whether a cheque in your base currency will be deemed as acceptable by suppliers in foreign countries.

 

If set to "No", cheque payments, as a settlement method, will be disallowed on creditors invoice line links and a settlement method of "Bank Transfer" will therefore need to be specified.

 

Functions referencing this setting include the following:

 

Settlement Method on Creditors

hmtoggle_plus1Allow Credits On Latest Invoices

This setting relates to the External Organisation function. It is a constraint that will

 

Disallow,
Allow and default no credits on latest invoices or
Allow and default credits on latest invoices.

 

This setting governs whether it will be allowed to add credits on the latest invoice rendered. If set to "Disallowed", no credits will be allowed to add to any invoices.

 

If set to "Allowed and default no Credits on latest Invoices", credits will be allowed but not to the latest Invoice rendered. If set to "Allowed and default Credits on latest Invoices", credits will be allowed to all invoices, including the latest Invoices.

 

Functions referencing this setting include the following:

 

Settlement Method on Debtors

External Organisation

hmtoggle_plus1Allow Debtor Links Witout Source

The setting governs whether Debtor Line Links will be allowed without a valid source. The source document can either be a valid invoice or a customer order. The setting on System Configuration only governs the 'Allow Links Without Source' setting on External Organisation while  the External Organisation Setting then again governs the Debtor Line Link creation.

 

The System Configuration setting has three options:

 

Disallow links without source, (The setting on External Organisation will not allow links without source)
Allow and default no links without source. (The setting on External Organisation will default not to allow links without source but will be open for change)
Allow and default links without source. . (The setting on External Organisation will default to allow links without source but will be open for change)

 

If set to "Allowed and default no links without Source", links will be allowed but only those with a Source. If set to "Allowed and default  links without a Source", links with or without Sources will be allowed.

 

Functions referencing this setting include the following:

 

Settlement Method on Debtors

External Organisation

hmtoggle_plus1Allow For Budgeting

hmtoggle_plus1Allow Multiple Divisions Per Document

This field allows for a Yes/No setting and governs whether more than one division can be linked to an invoice.

 

If set to "Yes", more than one Division may be linked to a document/invoice. If set to "No", only one Division can be linked to a document/invoice.

 

Functions referencing this setting include the following:

 

Debtors

External Organisation

hmtoggle_plus1Allow Multiple Orders Per Document

This setting relates to the External Organisation function.

 

It is a constraint that will:

 

Disallow,
Allow and default one order per invoice or
Allow and default multiple orders per invoice.

 

This setting governs whether it will be allowed more than one order per invoice. If set to "Disallow", no orders will be allowed.

 

If set to "Allowed and default one order per invoice", only one order per invoice will be allowed per invoice. If set to "Allowed and default multiple orders per invoice.

 

Functions referencing this setting include the following:

 

Settlement Method on Debtors

External Organisation

hmtoggle_plus1Allow Payment Goods Inspection

This option allows the creditors department to decide whether stock can be paid while still in Inspection.

 

When "Yes" is selected Invoices can be settled while stock is still in Inspection, but when "No" is selected, Invoices can only be settled when stock is moved to their destination Store.

hmtoggle_plus1Asset Depr Commit Status

This setting relates to the Asset depreciation Model function where the point of commitment can be set by either using the "Accepted" status or the "Requested" status.

 

This will bring about the point where the system will decide at what status the Asset must be when depreciation can be induced.

 

Functions referencing this setting include the following:

 

Asset Information
Asset Depreciation Model
hmtoggle_plus1Assets Integrated

This setting impacts the working of the Maintenance Requisition.

 

If set to Yes "1", maintenance requisitions can be linked to assets defined on the Asset Master.

 

If set to No "0", maintenance requisitions can be linked to assets defined on the Asset Master or a free format asset number can be entered.

hmtoggle_plus1Asset TOV Change Enforce Depreciation

hmtoggle_plus1Asset Status Change Enforce Depreciation

hmtoggle_plus1Authorisation Limits Inherited By Acting Employee

This setting impacts on the release of Requisitions.  The requisition release routine validates whether anyone in the approval history of the Requisition (including the person attempting the release) has adequate authorisation limits considering the Requisition,

required amount.

 

The Routine also determines whether anyone in the approval history of the Requisition (including the person attempting the release) approved the requisition in an "Acting for" capacity and whether the "Acting for" record granted inheritance of authorisation limits to the "Acting" employee.  This setting governs the extent of authorisation limits inherited when acting for an absent employee and provides the following options:

 

       "No authorisation limits inherited"
       "Personal authorisation limits of absent employee inherited"
       "Job assignment authorisation limits of absent employee inherited"
       "Both personal and job assignment limits of absent employee inherited"

 

Personal limits are specified on the "Employee Master" and is granted to an individual of their job assignment. Job assignment limits are specified for cost centres and divisions on the respective Cost Centre and Division functions and is granted to whoever holds the position as Cost Centre manager, Division manager or Division Accountant at the time.

 

If set to "No Authorisation Limits Inherited", the system will disallow you to grant inheritance of authorisation limits when creating an "Acting for" record.  Previously created records that granted such inheritance, will be overridden by such a System Configuration setting.

 

If set to any of the other three options, the "Acting" employee will inherit authorisation limits according to the setting, but only if the "Acting for" record granted inheritance of such limits to the "Acting" employee.

hmtoggle_plus1Auth Limit To Be Exceeded Before C.E.O. Informed

It is a value that, when exceeded when granting personal limits of authorisation to employees, will result in informative mail to the CEO.

 

Functions referencing this setting include the following:

 

Apply on Cost Centre

Apply on Division

Change on Employee Information

hmtoggle_plus1Bill Of Material Max Levels

It is the maximum number of levels allowed for a product structure.  Any product structure inquiry or navigation result or MRP run returning a greater number of levels, will assume the presence of a loop in the structure and will only

display up to the specified number of levels.

 

Change the value of this setting in the "Value" column.  The Bill of Material Max Levels can be between 2 and 35.

 

Functions referencing this setting include the following:

 

MRP

Cost Generation

Product Structure Navigation

hmtoggle_plus1Client Connections Max

It is the maximum number of simultaneous connections any one client will be allowed to the Server.

 

Change the value of this setting in the "Value" column.  The Client Connections Max can be between 2 and 10, with 3 being an ideal value.

hmtoggle_plus1Completion Date In Past For Customer Orders

hmtoggle_plus1Completion Date In Past Internal Orders

hmtoggle_plus1Completion Date In Past For Purchase Orders

hmtoggle_plus1Cost Centre Levels Max

It is the maximum number of levels allowed for a cost centre structure.  Any cost centre structure inquiry or navigation result returning a greater number of levels, will assume the presence of a loop in the structure and will only display up to the specified number of levels.

 

Change the value of this setting in the "Value" column.  The maximum cost centre levels must be between 2 and 35 days.  Functions referencing this setting include the following:

 

Structure Tree Detail on Division

Cost Centre

hmtoggle_plus1Crate Dimension Uom Default

This is a unit of measure default used to define the unit of measure in which the crate is measured.  When loading a crate from either the Crate or Store to Crating function, this default will be applied.

 

When you click on the corresponding "Value" column, you can select a dimension unit of measure from the dropdown combo displayed. Functions referencing this setting include the following:

 

Add on Store to Crating
Apply on Crating to Store
Dimension UOM Code on Crate
hmtoggle_plus1Crate Mass Uom Default

This is a unit of measure default used to define the unit of measure in which the crate is measured.  When loading a crate from either the Crate or Store to Crating function, this default will be applied.

 

When you click on the corresponding "Value" column, you can select a dimension unit of measure from the dropdown combo displayed. Functions referencing this setting include the following:

 

Add on Store to Crating
Apply on Crating to Store
Dimension UOM Code on Crate
hmtoggle_plus1Credit Department Overpay

It is a constraint on the amount with which Creditors can overpay on an invoice line compared to the purchasing value of such a line.

 

Make the necessary changes in the text box in the corresponding "Value" column.  The Creditor Department Overpay must be between 0 and 20 000 currency units.

 

This setting is referenced when adding a credit link on the Creditors function.

hmtoggle_plus1Credit Limit Max (Debtors)

It is a constraint on the credit limit that can be specified for any External Organisation your Company deals with.

 

Make the necessary changes in the text box in the "Value" column.  The credit limit max (debtors) must be between a minimum of 10 and a maximum of 1,500,000,000 currency units.

 

Functions referencing this setting include the following:

 

Credit Limit on External Organisation

hmtoggle_plus1Currency Base

It is the base currency of your country and it can only be entered if a record exists on the Currency table with a conversion of 1=1.

 

Make the necessary changes in the drop down combo displayed when clicking on the "Value" column.  Functions referencing this setting

include the following:

 

Cost Centre Timesheet Approval

Creditors

Creditors Credit Per Settlement

Currency Codes

Customer Orders

Debtors

Debtors Credit Per Settlement

Division

External Organisation Parts

Purchase Orders

Released Purchase Order Generation

Requisitions

Sales Order Wizard

Shipment Document

Stock Purchase Order Requisition

Stores to Customer

hmtoggle_plus1Currency Base Symbol

It is derived from the Currency table for the base currency. This base symbol will precede any monetary value displayed by the screens e.g. R10.

 

Make the necessary changes in the drop down combo displayed when clicking on the "Value" column (mandatory).  Functions referencing

this setting include the following:

 

Division

External Organisation Parts

Purchase Orders

Released Purchase Order Generation

hmtoggle_plus1Days Supply Max

It is a constraint on the "Number of Days Supply" specified for the replenishment of any part in your Company when applying the period covered interval replenishment technique.

 

This is validated on the Part Master table when "Days Supply" data is maintained. Make the necessary changes in the text box in the "Value" column.

 

The maximum days supply must be between 22 and 255 days.  Functions referencing this setting include the following:

 

Days Supply on Part Master

Fixed/Period Combination on Part Master

hmtoggle_plus1Default Country Code

This setting shows the default country code as defined on the Country function and defaulted to all addresses in the system (i.e. Billing address on External Organization).

hmtoggle_plus1Default Settlement Term

This setting shows the default settlement term as defined on the Settlement Term function and as is defaulted on the External Organisation function.

hmtoggle_plus1Decimal Movement Allowed

This setting relates to all the Movement functions. This setting governs the Movement Quantity of parts where;  No records exist on the Product Master table where Decimal Movements Allowed = 1 and No records exist on the3 Unit Of Measure table where Decimal Movements Allowed = 1

 

When checked, will allow stock to be moved in decimal units. Smaller or larger that a whole unit but less or larger that the following or previous unit.

 

When unchecked will only allow movements with quantities not containing decimal numbers.

 

Functions referencing this setting include the following:

 

Movements

Debtors

External Organisation

hmtoggle_plus1Debtor Credit Line Link Option

This setting relates to the External Organisation function. It is a constraint that will govern whether a credit line will be added, or added and linked to an Invoice (or Credit Note).

 

If set to "Add Credit Links to Credit Notes", a Credit Link can be added to an Invoice/ Credit Note.

 

If set to "Add a new Credit Line and Link to the same Created or Not Approved Invoice", a new line will be added to the Invoice/Credit Note with the status of "Created" or "Not Approved".

 

If set to "Add a new Credit Line Link to the same Created or Not Approved Invoice", a link can be added to a line on an Invoice/Credit Note.

 

If set to "Add a new Credit Line to the latest Created or Not Approved Invoice", a new credit line will be added to the latest Invoice/Credit Note.

 

Functions referencing this setting include the following:

 

Settlement Method on Debtors

External Organisation

hmtoggle_plus1Debtor Credit Note Option

This setting relates to the External Organisation function. It is a constraint that will govern whether a new Credit Note will be created, or only lines added or links added to lines on an Invoice (or Credit Note).

 

If set to "Create new Credit Note", no lines will be created. A whole new Credit Note will be created.

 

If set to "Add Credit Line Link to the latest Created or Not Approved Credit Note", a link will be added to a line on the latest and already existing Credit Note with the status of "Created" or "Not Approved".

 

If set to "Add Credit Line and Line Link to the latest "Created" or "Not Approved" Credit Note, a new line will be added to the latest and already existing Credit Note with the status of "Created" or "Not Approved".

 

Functions referencing this setting include the following:

 

Settlement Method on Debtors

External Organisation

hmtoggle_plus1Debtor Invoice Option

This setting relates to the External Organisation function.  It is a constraint that will:

 

Create a new invoice for each delivery note and use separate number sequences,
Create a new invoice for each delivery note and use same number sequences,
Add a delivery shipment line and line link to an existing "Created" or "Not Approved Invoice", or
Add a delivery shipment line link to an existing "Created" or "Not Approved" Invoice Line.

 

If set to "Create a new Invoice for each Delivery Note and use separate number sequences" a new invoice will be created and the number sequence in use will determine what the number of the invoice will be.

 

If set to "Add a delivery shipment line and line link to an existing Created or Not Approved Invoice", a delivery shipment line and a line link can be added to an existing invoice with the status of Created or Not Approved.

 

If set to "Add a delivery shipment line link to an existing Created or Not Approved Invoice Line", a delivery shipment line link can be added to an existing invoice with the status of Created or Not Approved.

 

Functions referencing this setting include the following:

 

Settlement Method on Debtors

External Organisation

hmtoggle_plus1Debtor Settlement Auto Apply

This setting governs whether settlement must be automatically applied for Debtors or not. This setting will default to a similar setting on the External Organisation function.

hmtoggle_plus1Default Exempt Tax Code

By setting this indicator to the appropriate code, the system will use the tax code as the Default Exempt Tax Code where the tax codes from the Tax Code table is an active tax code.

hmtoggle_plus1Document Structure Levels Max

hmtoggle_plus1Ecp Allow Non Mrp Config Items

This setting governs the population of the Configuration Item (CI) Number on the Change Proposal function.

 

If this setting is No, the Configuration Item (CI) Number field only populates with MRP planned, phantom parts from the Part Master table.

 

If this setting is Yes, the Configuration Item (CI) Number field populates with all parts from the Part Master table.

hmtoggle_plus1Ecp Control Part Operations

ECP control on the System Configuration level is used to control the level of control specified on products.

 

When loading a new product definition, and the level of control is changed, this default will be applied to ensure that either ECP control where key fields are predefined, or recorded later, are forced from the "Life Cycle" selected here.

 

Functions referencing this setting include the following:

 

Change Control Grid on the Product Master

Add, Change, and Delete on Part Operations

hmtoggle_plus1Ecp Control Part Revisions

ECP control on the System Configuration level is used to control the level of control specified on products.

 

When loading a new product definition, and the level of control is changed, this default will be applied to ensure that either ECP control where key fields are predefined, or recorded later, are forced from the "Life Cycle" selected here.

 

Functions referencing this setting include the following:

 

Change Control Grid on the Product Master

Add and Delete on the Part Master

hmtoggle_plus1Ecp Control Product Structure

ECP control on the System Configuration level is used to control the level of control specified on products.

 

When loading a new product definition, and the level of control is changed, this default will be applied to ensure that either ECP control where key fields are predefined, or recorded later, are forced from the "Life Cycle" selected here.

 

Functions referencing this setting include the following:

 

Linked Components,

Available Components,

Linked Parents ,

Dustbin,

Logical Delete Dustbin on Product Structure

Change Control Grid on the Product Master

hmtoggle_plus1Ecp Product Code Enforcement

This is a Yes/No setting that governs whether it is permitted to deviate from the product code of the selected CI (Configuration Item) on an ECP.

 

When "Yes", the product code on the configuration item selected, is enforced and cannot be changed.  If "No", the product code of the configuration item selected is not enforced and can be changed.

 

A number of new fields have been added on the Change Proposal function and include the CI Number and ECP Product Code.  Once the CI Number is selected, the product code as defined on its part master record, will be applied as the ECP Product Code.  This field provides the following 3 options to enforce the product code:

 

"No Deviation Allowed'
"Allow Deviation from CI Product Code"
"Allow Deviation from CI Product Code, but send mail to Product Manager".
hmtoggle_plus1Eis Saved Reports Option

This field is not yet functionally applied and the option you select will have no impact on saved EIS reports .  Advance notice will be given  when the field becomes functional, to enable you to set the field value according to the preference in your Organisation.

 

The setting, once functional, will govern whether EIS reports created by users, can be saved as either Private or Shared (public).  The current  options might be adjusted to better describe the control options.

hmtoggle_plus1Employee Id Length

This field governs the length of employee IDs that can be entered on the Employee Master.  The employee ID on the Employee Master table allows for up to 20 characters to be entered.

If you wish to allow users to create employee records where the ID is allowed to be any value between 1 and 20 characters, set the value in this field to 0.

 

EXAMPLE:

 

If you wish to enforce a specific length for the employee ID, enter the length to be enforced.

 

Specifying a length of 6 characters will force the users to enter an ID of exactly 6 characters on the Employee Information function.

hmtoggle_plus1Employees Maintained In System

A Yes/No setting used to specify whether employees are added and maintained via the system (Yes) or via another integrated personnel/human resources system (NO).

 

Only a setting of Yes will enable the Add button on the function Employee Information .  Changes will, however, be allowed irrespective of Yes/No setting.

 

Either select or deselect this setting by ticking or unticking the check box in the "Value" column.

hmtoggle_plus1Enforce Commodity Code Report Uom

This setting specify whether reporting for specific Commodity Codes will use the specified UOM or the alternate UOM used.

 

When select will force the UOM used in the Commodity Code function to create the report.

 

Functions referencing this setting include the following:

 

Reporting UOM on Commodity Codes.

hmtoggle_plus1Escalation Max %

It is a constraint on the escalation factor that can be entered on Purchase and Customer Orders.  It is entered as a Factor, for example, 0.15 being equal to the escalation of 15%.

 

Make the necessary changes in the text box in the "Value" column.  The escalation factor must be between 0 and 99 percent. Functions  referencing this setting include the following:

 

Escalation Factor on Customer Orders

Escalation Factor on Purchase Orders

hmtoggle_plus1Escape Sequence (Not Represented In Data)

It is a string of characters that will never be presented in data and is used for begin/end/escape commands so that the system does not confuse it with data.

 

Make the necessary changes in the text box in the "Value" column. The escape character sequence must be between 3 and 10 characters.

hmtoggle_plus1Exclude Debtor Statement Creation

With this setting on, no debtor statement detail will be written, this will result in no debtor statement available for users out of Qmuzik.

hmtoggle_plus1External Object Force Store Use

It is a Yes/No setting that will allow or disallow objects to be kept in a non store location.

 

Either select or deselect this setting by ticking or unticking the check box in the "Value" column.  Functions referencing this setting include the following:

 

Use Non-Store Location on External Object

hmtoggle_plus1External Object In One Location Only

It is a setting of Yes/No that will allow or disallow multiple locations to be specified for an External Object.

 

Either select or deselect this setting by ticking or unticking the check box in the "Value" column.  When ticked the external object can only  be specified in one location.  Functions referencing this setting include the following:

 

button on External Object

hmtoggle_plus1Force Debtor Invoice Option

This setting relates to the External Organisation function.  It is a constraint that will:

 

Enforce and disallow change
Enforce and allow change
Do not enforce and allow change

 

If set to "Enforce And Disallow Change" the setting on the External Organisation that determines the Debtor Invoice will be Enforce without any changes allowed.

 

If set "Enforce And Allow Change", the setting on the External Organisation that determines the Debtor Invoice will be Enforce, but will allow changes.

 

If set "Do Not Enforce And Allow Change", the setting on the External Organisation that determines the Debtor Invoice Option can be change at free will without any option that will be enforced.

 

Functions referencing this setting include the following:

 

Settlement Method on Debtors

External Organisation

hmtoggle_plus1Force Debtors Credit Line Option

This setting relates to the External Organisation function.  It is a constraint that will:

 

Enforce and disallow change
Enforce and allow change
Do not enforce and allow change

 

If set to "Enforce And Disallow Change" the setting on the External Organisation that determines the Debtor Credit Link Option will be Enforce without any changes allowed.

 

If set "Enforce And Allow Change", the setting on the External Organisation that determines the Debtor Credit Link Option will be Enforce, but will allow changes.

 

If set "Do Not Enforce And Allow Change", the setting on the External Organisation that determines the Debtor Credit Link Option can be change at free will without any option that will be enforced.

 

Functions referencing this setting include the following:

 

Settlement Method on Debtors

External Organisation

hmtoggle_plus1Force Debtors Credit Note Option

This setting relates to the External Organisation function.  It is a constraint that will:

 

Enforce and disallow change
Enforce and allow change
Do not enforce and allow change

 

If set to "Enforce And Disallow Change" the setting on the External Organisation that determines the Debtor Credit Note Option will be Enforce without any changes allowed.

 

If set to "Enforce And Allow Change", the setting on the External Organisation that determines the Debtor Credit Note Option will be Enforce, but will allow changes.

 

If set "Do Not Enforce And Allow Change", the setting on the External Organisation that determines the Debtor Credit Note Option can be change at free will without any option that will be enforced.

 

Functions referencing this setting include the following:

 

Settlement Method on Debtors

External Organisation

hmtoggle_plus1Front End Customisation Allowed

This option enables or disables the customisation of Front End captions in the System.

 

Related Topic: Customised function

 

To see the Customised Captions and use the function the setting must be checked.

hmtoggle_plus1Function And Screen Access Display Option

This "Function and Screen Access Display Option" provides the following four options:

 

"Show all functions as enabled"
"Show all but gray non-linked functions"
"Show all but gray and disable non-linked functions"
"Show linked only (gray non-linked on Business model)"

 

These options are NOT yet applied, but are bound to control the display of functions (screens) on the standard and book menus in accordance with the access to functions derived via the security profiles linked to a specific employee.

 

It will show all screens as "enabled", as currently done (option one) or gray, the screens that the user has no access to on the menu (option two).  The third option will gray and disable the selection of screens not linked to the user via a security profile while the fourth option will display linked functions only on the menus and gray the non-linked functions when the user views the Business model.

hmtoggle_plus1Hand Journals For Nodes Allowed

The Hand Journal function provides the ability to transfer amounts from a node to one or more other nodes, between a node and an account and between accounts by means of credit and debit journals.

 

This Yes/No setting on System Configuration governs whether the Hand Journal function will permit nodes of the Project Management System to be credited or debited by means of hand journals.

 

Should the option be set to "No", the columns "Node", "Resource" and "Material Budget Financial Period" will be hidden on the screen to make it non-accessible.

 

Functions referencing this setting include the following:

 

Hand Journal Function on Hand Journal

hmtoggle_plus1Homogeneous Lot Issuing To Orders

When checked, only stock belonging to the same lot number can be issued to specific order requirements.  When this setting is checked, material back flushing will not issue lot controlled stock.

 

When unchecked, stock of more than one lot can be issued for an orders requirements.

 

Functions referencing this setting include the following:

 

Lot Controlled on the Part Master

Order Requirements to Stores

Stores to Order Requirements

hmtoggle_plus1Invoice Period 1

It is a pre-defined period, for example, 30 (Period 1), 60 (Period 2), that will be used by summarised invoice age analysis and invoice printing to group the value of unsettled invoices into period sub totals for a given external organisation.

 

Make the necessary changes in the text box in the "Value" column.  Functions referencing this setting include the following:

 

Age Analysis Option on the External Organisation function

hmtoggle_plus1Invoice Period 2

Is a pre-defined period, for example, 30 (Period 1), 60 (Period 2), that will be used by summarised invoice age analysis and invoice printing to group the value of unsettled invoices into period sub totals for a given external organisation.

 

Make the necessary changes in the text box in the "Value" column.  Functions referencing this setting include the following:

 

Age Analysis Option on the External Organisation function

hmtoggle_plus1Invoice Period 3

Is a pre-defined period, for example, 30 (Period 1), 60 (Period 2), that will be used by summarised invoice age analysis and invoice printing to group the value of unsettled invoices into period sub totals for a given external organisation.

 

Make the necessary changes in the text box in the "Value" column.  Functions referencing this setting include the following:

 

Age Analysis Option on the External Organisation function.

hmtoggle_plus1Invoice Period 4

Is a pre-defined period, for example, 30 (Period 1), 60 (Period 2), that will be used by summarised invoice age analysis and invoice printing to group the value of unsettled invoices into period sub totals for a given external organisation.

 

Make the necessary changes in the text box in the "Value" column.  Functions referencing this setting include the following:

 

Age Analysis Option on the External Organisation function.

hmtoggle_plus1Invoice Period 5

Is a pre-defined period, for example, 30 (Period 1), 60 (Period 2), that will be used by summarised invoice age analysis and invoice printing to group the value of unsettled invoices into period sub totals for a given external organisation.

 

Make the necessary changes in the text box in the "Value" column.  Functions referencing this setting include the following:

 

Age Analysis Option on the External Organisation function.

hmtoggle_plus1Invoice Age Analysis Debtors Aging Method

AGING BY

This setting will be use as the default for Debtors Aging Method on External Organisation Invoice Analysis.

 

Capture Date

Should you regard all invoices received/issued within a month, to start aging on the capture date, select the option Capture Date.

 

Invoice Creation Date

Should you regard all invoices received/issued within a month, to start aging on the invoice creation date, select the option Invoice Creation Date.

 

However, for debtor invoices, it will assume the invoice date as being the date the invoice was created, by extracting the debtor invoice status history (on the Debtors function).

 

Line Creation Date

Should you regard all invoices received/issued within a month, to start aging on the date the invoice line was created, select the option Line Creation Date.

 

Print Approved Date

Should you regard all invoices received/issued within a month, to start aging on the date the invoice was printed approved, select the option Print Approved Date.

 

Print Date

Should you regard all invoices received/issued within a month, to start aging on the date the invoice was printed, select the option Print Date.

hmtoggle_plus1Invoice Age Analysis Debtors Date Method

The purpose of the age analysis option is to specify the method according to which the age of the invoice is determined, which will have an effect on the "age period" into which an invoice will be grouped.  This setting will be use as the default for Debtors/Creditors Date Method on External Organisation Invoice Analysis.

 

Calendar Month End Date

Should you regard all invoices received/issued within a month, to start aging on the last day of the month, select the option Calendar Month End Date.

 

All invoices, irrespective of the actual invoice date will therefore be assumed to have an invoice date equal to the last calendar day of the month during which it was invoiced.

 

Financial Month End Date

Should you regard all invoices received/issued within a month, to start aging on the last day of the month, select the option Financial Month End Date.

 

All invoices, irrespective of the actual invoice date will therefore be assumed to have an invoice date equal to the financial month end of the month in which it was invoiced.

 

Specific Day of Month

Should you regard all invoices received/issued within a month, to start aging on the last day of the month, select the option Specific Day of Month.

 

When this option is selected, the "Day of Month" spinner is enabled and defaults to the value specified in the setting Invoice Age Analysis Day of Month on System Configuration.  The spinner allows you to specify any value between 1 and 28.  All invoices, irrespective of the actual invoice date will therefore be assumed to have an invoice date equal to the specified day of the month.

 

Use Date As Is

Should you regard an invoice received/issued to start aging on the actual invoice date, select the option "Use Date As Is". The actual invoice date depends on the Aging by setting used.

 

All invoices will be individually aged according to their actual invoice date.

hmtoggle_plus1Invoice Age Analysis Debtors Day Of Month

This setting will be use as the default for Debtors/Creditors Day of Month on External Organisation Invoice Analysis.

 

This setting will only be used if the aging method, "Specific Day of Month" is selected.  It can have a minimum value of 1 and a maximum value of 28.

hmtoggle_plus1Invoice Age Analysis Creditors Aging Method

AGING BY

This setting will be use as the default for Creditors Aging Method on External Organisation Invoice Analysis.

 

Capture Date

Should you regard all invoices received/issued within a month, to start aging on the invoice capture date, select the option Capture Date.

 

Invoice Date

Should you regard all invoices received/issued within a month, to start aging on the date the invoice was printed, select the option Invoice Date.

 

For creditor invoices, it will assume the invoice date entered on the creditor invoice as the invoice date.

 

Line Creation Date

Should you regard all invoices received/issued within a month, to start aging on the date the invoice line was created, select the option Line  Creation Date.

hmtoggle_plus1Invoice Age Analysis Creditors Date Method

The purpose of the age analysis option is to specify the method according to which the age of the invoice is determined, which will have an effect on the "age period" into which an invoice will be grouped.  This setting will be use as the default for Debtors/Creditors Date Method on External Organisation Invoice Analysis.

 

Calendar Month End Date

 

Should you regard all invoices received/issued within a month, to start aging on the last day of the month, select the option Calendar Month End Date.

 

All invoices, irrespective of the actual invoice date will therefore be assumed to have an invoice date equal to the last calendar day of the month during which it was invoiced.

 

 

Financial Month End Date

 

Should you regard all invoices received/issued within a month, to start aging on the last day of the month, select the option Financial Month End Date.

 

All invoices, irrespective of the actual invoice date will therefore be assumed to have an invoice date equal to the financial month end of the month in which it was invoiced.

 

Specific Day of Month

 

Should you regard all invoices received/issued within a month, to start aging on the last day of the month, select the option Specific Day of Month.

 

When this option is selected, the "Day of Month" spinner is enabled and defaults to the value specified in the setting Invoice Age Analysis Day of Month on System Configuration.  The spinner allows you to specify any value between 1 and 28.  All invoices, irrespective of the actual invoice date will therefore be assumed to have an invoice date equal to the specified day of the month.

 

Use Date As Is

Should you regard an invoice received/issued to start aging on the actual invoice date, select the option "Use Date As Is".  The actual invoice date depends on the Aging by setting used.

 

All invoices will be individually aged according to their actual invoice date.

hmtoggle_plus1Invoice Age Analysis Creditors Day Of Month

This setting will be use as the default for Debtors/Creditors Day of Month on External Organisation Invoice Analysis.

 

This setting will only be used if the aging method, "Specific Day of Month" is selected.   It can have a minimum value of 1 and a maximum  value of 28.

hmtoggle_plus1Include Group Requisition In Budget Check

This setting governs whether a grouping requisition amount should be provided for in the node budget.

 

If the setting is true, the Grouping Requisition amount will be shown as a commitment on a node.   If false, the grouping requisition is not seen as part of the committed cost (if false, the system will not even create a budget record for the grouping requisition).

hmtoggle_plus1Labour Overspend Tolerance Max %

This is a constraint that can be placed on the labour over-spend tolerance (%)specified on nodes.

 

Make the necessary changes in the text box in the "Value" column.  The maximum labour overspend tolerance must be between 0 and 90 percent.

 

RELATED TOPIC: Add on Node

hmtoggle_plus1Labour Rate Max

This is a constraint that can be placed on the labour rate for cost centres, labour resources,  employees and project budgets.

 

Make the necessary changes in the text box in the "Value" column.  The maximum labour rate must be between 1 and 20 000 currency units.  This settings is used by:

 

Financial Costs List Box on Cost Centre

Labour Rate on Employee Information

Labour Rate on Labour Resource

Apply on Labour Budget

hmtoggle_plus1Language, Default

It is the language most commonly used in your Company.  It will only be used if a back end message cannot determine an employee's preferred language, which will result in a back end message given in the "Default Language".

 

When clicking on the "Value" column, a drop down combo is displayed allowing the user to select the language default from the list.

 

The default language may be either English "E", Italian "I", French "F", Spanish "S", or German "G".  Functions referencing this setting include the following:

 

Language Preference on Employee Information.

hmtoggle_plus1Lead Time Days (Manufacturing) Max

It is a constraint on the lead-time that can be specified for manufactured parts (sources being Manufactured, Interplant and Phantoms).  The constraint is applied when maintaining lead-time days on the Part Master table and when creating internal orders via the Order Master function.

 

Make the necessary changes in the text box in the "Value" column.  The maximum purchase lead time must be between 5 and 1000 days.  Functions referencing this setting include the following:

 

Lead Time Days on the Customer Orders function

Lead Time on the Order Master function

Lead Time on the Part Master function

hmtoggle_plus1Lead Time Days (Purchasing) Max

It is a constraint on the lead-time that can be specified for purchased parts (sources being Purchased, Sub-Contracted and Customer Furnished). The constraint is applied when maintaining lead time days on the Part Master table and when creating purchase orders.

 

Make the necessary changes in the text box in the "Value" column.  The maximum purchase lead time must be between 5 and 1000 days.  Functions referencing this setting include the following:

 

Lead Time on the Part Master.

hmtoggle_plus1Load Creditors Invoice On Hold

hmtoggle_plus1Log Po Line Changes

hmtoggle_plus1Material Overspend Tolerance Max %

This is a constraint that can be placed on the material over-spend tolerance (%)specified on nodes.

 

Make the necessary changes in the text box in the "Value" column.  This setting can have a value between 0 and 90%.

 

RELATED TOPIC: Add on Node

hmtoggle_plus1Maximum Combo Entries Displayed

By setting this amount the system will be able to display that amount of entries in ALL Combo boxes right through the system.

hmtoggle_plus1Maximum Listview Entries Displayed

By setting this amount the system will be able to display that amount of entries in ALL Listviews right through the system.

hmtoggle_plus1Movement History Archived After (Days)

This field has been created to provide the ability to archive the movement history after a number of days and delete it from the "Movements" table.

 

This field is NOT yet functional and the value specified for this field will currently have no impact on the period for which the movement history is retained.  Advance notice will be given when the field becomes functional to enable you to set the field value according to the preference in your Organisation.

 

This setting can have a value between 7 and 3660 days.

hmtoggle_plus1Mrp Run After (Time)

The times entered will place a constraint on MRP runs that are submitted during the day.  Only selective runs performed prior to the Run  Before and later than the Run After times will be executed online and real-time.

 

Make the necessary changes in the text box in the "Value" column.  Functions referencing this setting include the following:

 

MRP Function on MRP

Run button on MRP

hmtoggle_plus1Mrp Selective Run Message To System Log

It is a Yes/No setting that determines whether a Selective MRP Run will send messages to the System log to enable an exact trace of its status and activities.  A setting of Yes will result in a performance penalty.

 

Either select or deselect this setting, by ticking or unticking the check box in the "Value" column.  Functions referencing this setting include the following:

 

Run button on MRP

hmtoggle_plus1Mrp Message (Global Run) To System Log

It is a Yes/No setting that determines whether a Global MRP Run will send messages to the System log to enable an exact trace of its status

and activities.  A setting of Yes will result in a performance penalty.

 

Either select or deselect this setting, by ticking or unticking the check box in the "Value" column.

hmtoggle_plus1Mrp Run Before (Time)

The times entered will place a constraint on MRP runs that are submitted during the day.  Only selective runs performed prior to the Run Before and later than the Run After times will be executed online and real-time.

 

Make the necessary changes in the text box in the "Value" column.  The MRP "Do Not Run Before" time must be less than the MRP "Do Not Run After" time.

 

Functions referencing this setting include the following:

 

MRP Function on MRP

Run button on MRP

hmtoggle_plus1Mrp Simultaneous Runs (Max)

Defines the number of users who may simultaneously perform MRP runs on the system.  Some constraint is required to ensure that other  users do not pay too much of a performance penalty resulting from too many simultaneous MRP runs by their colleagues.

 

Make the necessary changes in the text box in the "Value" column.  The maximum simultaneous MRP runs must be between 1 and 25.  Functions referencing this setting include the following:

 

MRP Function on MRP

Run button on MRP

hmtoggle_plus1New Object Indicator

This indicator informs the user whether an object is new or existing.  Should any work have been done on a particular object, for example, function in a particular release/service pack, the status will be 'New'.   The aim is to easily identify new functionality within the system.

 

The setting on System Configuration must allow the client to decide whether to convert objects from 'New' to 'Existing' after a selected time period has passed since the object creation date, or to leave this status unchanged until the next service pack or release of software.  In the latter instance, the software house will be solely responsible for the update of the object status.

hmtoggle_plus1Node Budget Run After (Time)

The times entered will place a constraint on Node budget runs for a division that are submitted during the day.

 

Only runs performed prior to the Run Before and later than the Run After times will be executed.  This has no effect on runs performed for individual nodes/node structures.

 

Make the necessary changes in the text box in the "Value" column.  Functions referencing this setting include the following:

 

Node Budget Commitments and Actuals

hmtoggle_plus1Node Timesheets Allowed In Closed Periods

This field allows for a Yes/No setting and governs whether timesheets will be allowed to be entered in already closed financial periods.

 

If set to "Yes", timesheets will be allowed in closed periods.

 

If set to "No", timesheets will not be allowed in closed periods.

 

On the function Journal Source, the user can indicate for which financial period, which type of journals may run.  If, for any specific period, the timesheet journals (source = 'N') are not allowed, journals which must run when a timesheet is approved will run in the present financial period.  For some companies, this situation is not acceptable, since journals must run in the same period than the timesheet date itself.  To avoid this, this setting can be set to 'Off'.  This will prevent the timesheet being approved or unapproved, and therefor avoid any journals.  If the timesheet is legitimate and its journals must run in the closed period, the period must temporarily be opened.  If the timesheet is legitimate but its journals may not run in the closed period, this setting must temporarily be set to 'On' - the timesheet approval will be allowed and the journals will run in the current period.

 

New timesheets will always be disallowed for closed periods if this setting is set to 'Off'.  If a period is closed whilst there are existing timesheets in that period, mail will be sent to the user, indicating that there are timesheets which cannot be approved anymore, because they exist in a closed period and this setting is set to 'Off'.

 

Functions referencing this setting include the following:

 

Nodes and Timesheets.

hmtoggle_plus1Node Calculation View

hmtoggle_plus1Node Budget Adjustment Max Retrospective Months

MONTHS

This setting limits the number of months, into the past, that a Node manager can access unused budgets, and transfer these budgets to present or future budgets.

 

On the Node Budget Roll function, the Node Manager will not be able to select a source financial period that is prior to the value specified in this setting.

 

'This setting is aimed at assisting the division / company accountant or director, to protect the cash flow of the company and are especially useful for long running multi-year projects.  Cash flow planning for large projects is one of the many activities that must be considered when approving large projects.  After approving those projects, the budgets may change considerably, without the financial personnel necessarily being involved.  Project managers may, for example, use unused budgets of the previous financial year, and transfer it to the present financial period, adversely affecting cash flow, even though the whole projects has already been approved.  Similarly, budgets for next year may also be transferred into the current financial period, also affecting cash flow.  By setting these two settings, the extent to which budgets can be rolled around can be limited.  These settings are only interpreted when performing budget rolls.

hmtoggle_plus1Node Budget Adjustment Max Future Months

This setting limits the number of months, into the future, that a Node manager can access unused budgets, and transfer these budgets to other financial period budgets, for example, the Node manager can access budgets 7 months into the future and transfer them for use in 5 months.

 

On the Node Budget Roll function, the Node Manager will not be able to select a source financial period that is later than the value specified in this setting.

 

'This setting is aimed at assisting the division / company accountant or director, to protect the cash flow of the company and are especially useful for long running multi-year projects.  Cash flow planning for large projects is one of the many activities that must be considered when approving large projects.  After approving those projects, the budgets may change considerably, without the financial personnel necessarily being involved.  Project managers may, for example, use unused budgets of the previous financial year, and transfer it to the present financial period, adversely affecting cash flow, even though the whole projects has already been approved.  Similarly, budgets for next year may also be transferred into the current financial period, also affecting cash flow.  By setting these two settings, the extent to which budgets can be rolled around can be limited.  These settings are only interpreted when performing budget rolls.

hmtoggle_plus1Node Budget Run Before (Time)

The times entered will place a constraint on Node budget runs, for a Division, that are submitted during the day.

 

Only runs performed prior to the Run Before and later than the Run After times will be executed.  This has no effect on runs performed for individual nodes/node structures.

 

Make the necessary changes in the text box in the "Value" column.  The Divisional Node Budget "Do Not Run Before" time must be less than the Divisional Node Budget "Do Not Run After" time.

 

Functions referencing this setting include the following:

 

Node Budget Commitments and Actuals

hmtoggle_plus1Object Levels Max

Its the maximum number of levels allowed for objects in a structure.  Any inquiry or navigation result returning a greater number of levels,

will assume the presence of a loop in the structure and will only display up to the specified number of levels.

 

Make the necessary changes in the text box in the "Value" column.  The maximum object levels must be between 2 and 35.  Functions

referencing this setting include the following:

 

External Object

hmtoggle_plus1Off Site Area

Inactive at this stage. For future development.

hmtoggle_plus1Order Operations Planned Order

This option indicates the creating of Operations when planned orders are created through MRP with starting dates within the Order Operation Planned Order Horizon specified.

 

Functions referencing this setting include the following:

 

Purchase Orders And Order Operations

hmtoggle_plus1On Hold Line Links Enforce New Document
Enforce new document and disallow change.
Enforce new document and allow change.
Do not enforce new document and allow change.
Do not enforce new document and disallow change.
hmtoggle_plus1Order Operation Planned Order Horison

This option is used to set the horizon days for starting dates in which the MRP will create Order Operations for Planned Orders.

 

Functions referencing this setting include the following:

 

Purchase Orders And Order Operations.

hmtoggle_plus1Order Short Close Allowed

Order lines on internal orders (created via the Order Master screen) and customer order lines (created via the Customer Order screen) are automatically "Closed" (completed) as follows:

 

Internal Orders

When a Production to Store or Production to Scrap movement is performed via the Movements function and the sum of the quantity complete and the quantity scrapped becomes equal to the quantity ordered, the system automatically closes the order line, since the total expected quantity has been yielded.  Alternatively, the option exists to down adjust the order quantity to equal the sum of the quantity complete and quantity scrapped, which results in the automatic closure of the order line.

 

Customer Orders

When a shipping movement is performed via the Movements function and the quantity complete becomes equal to the quantity ordered, the system automatically closes the order line since the total quantity has been shipped.  Alternatively, the option exists to down adjust the order quantity to equal the quantity complete, which also results in the automatic closure of the order line.

 

Short Close

Clicking the "Closed" status and clicking the "Change" button can manually short close a partially completed order line.  This will result in the "Short close" of the order line but no adjustment of the quantity ordered or the required quantities of material/components required.  The requirements will also be regarded as closed and unissued quantities will no longer be regarded as open (outstanding) requirements.

hmtoggle_plus1Overhead (Variable) Rate Max

This is a constraint that can be placed on the variable overhead for cost centres, labour resources, employees and project budgets.

 

Make the necessary changes in the text box in the "Value" column.  The maximum overhead rate must be between 1 and 20 000 currency units.

 

This setting is used by:

 

Variable Overhead Rate on Employee Information

Labour Resource Rates on Labour Resource

Cost Centre Rates on Cost Centre

Apply on Labour Budget.

hmtoggle_plus1Overhead (Fixed) Rate Max

This is a constraint that can be placed on the fixed overhead rate for cost centres, labour resources, employees and project budgets.

 

Make the necessary changes in the text box in the "Value" column.  The maximum fixed overhead rate must be between 1 and 20 000

currency units.

 

This setting is used by:

 

Fixed Overhead Rate on Employee Information

Fixed Overhead Rate on Labour Resource

Financial Costs List Box on Cost Centre

Apply on Labour Budget

hmtoggle_plus1Password Force Change In Days

If internal security is used to run the system, all the users will be forced to change their passwords whenever the set number of days have expired since the previous password change.

 

Make the necessary changes in the text box in the "Value" column.  The password force change must be between 5 and 250 days.

 

Functions referencing this setting include the following:

 

Employee Information

hmtoggle_plus1Path, Company Reports (Unc Name)

It is the path/address on the network where the Company reports are located.

 

Make the necessary changes in the text box in the "Value" column. (mandatory).  On applying the changes the path is resolved and an error is generated when the path is not found.

 

Thus the \\Computer\Share must be accessible/available.  At some installations it may take a few seconds for the path \ filename to be resolved.

 

Functions referencing this setting include the following:

 

Credit Note

Purchase Orders

Stores to Customer

Print Documentation

Production to Customer

Stock Purchase Order Requisition

Inquiries and Normal Cheques tabs on Cheque Printing

hmtoggle_plus1Path, Image (Unc Name)

It is the path/address on the network where the images of parts and employees are located. Make the necessary changes in the text box in the "Value" column (mandatory).

 

On applying the changes the path is resolved and an error is generated when the path is not found.  Thus the \\Computer\Share must be accessible/available.  At some installations it may take a few seconds for the path\filename to be resolved.

 

Under this path, two folders, Parts and Personnel, contain all the part pictures and personnel pictures respectively.  These pictures are usually .JPG format, although other formats like .BMP is also supported.  The system will be able to associate the personnel picture to the correct person if the picture name corresponds to the Employee ID (i.e. John Black - 1751174 picture name is 1751174.JPG).

 

The system will be able to associate the part picture to the correct part if the picture name corresponds with the Part Number (i.e. Earth Pin - 660000055000 Picture Name is 660000055000.JPG)

 

The pictures can then be taken with a digital camera and copied and renamed in the correct folder.  Functions referencing this setting include the following:

 

Division Logo Filename on Division

Part Master

Employee Information

Picture

hmtoggle_plus1Path And Filename For Movement Picture

It is the path/address on the network where the graphical image of the Movements function is located.

 

Make the necessary changes in the text box in the "Value" column.  On applying the changes the path \ filename is resolved and an error is

generated when the path \ filename is not found.

 

Thus the \\Computer\Share must be accessible/available.  At some installations it may take a few seconds for the path \ filename to be  resolved.

 

The movement picture path must consist of at least 5 characters.

hmtoggle_plus1Path, Toolbar Settings (Unc Name)

It is the path to the customised employee toolbar and is used to store/save the, customised setting for the toolbar(s).

 

On applying the changes the path is resolved and an error is generated when the path is not found.

 

Thus the \\Computer\Share must be accessible/available. At some installations it may take a few seconds for the path \ filename to be resolved.

 

Functions referencing this setting include the following:

 

System Main Form

hmtoggle_plus1Purchase Decouple Time (Days) Max

It is a constraint on the Purchase Decouple Time (Days) as specified for purchased parts on the Part Master function.

 

Make the necessary changes in the text box in the "Value" column.  The purchase decouple time (days) max must be between 0 and 90 days.

hmtoggle_plus1Purchase Order Firming Allowed Without Mrp Order

This is a Yes/No setting.  If set to "Yes", this setting will allow the user to enter a Stock Purchase Requisition for a part, without the necessity for MRP to have suggested a planned purchase order from nett requirements or from a safety stock demand for which there is insufficient stock.  Firm orders created in this manner will be a valid Firm replenishment and serve to the Released Purchase Order Generation function as input to release a purchase order on a supplier.

 

When set to "No", the Stock Purchase Order Requisition function will require a planned purchase order suggested by MRP as input before a firm order can be created.

 

Functions referencing this setting include:

 

Stock Purchase Order Requisition

Released Purchase Order Generation

hmtoggle_plus1Purchase Order Manual Release (No Source Order)

This setting impacts on the Released Purchase Order Generation function which has a mode that can be applied to manually create released purchase order lines without a source order such as an MRP planned order or a firm order.

 

The setting on this field governs whether or not the Manual mode can be selected on the Released Purchase Order Generation function.

hmtoggle_plus1Purchase Order Release Back To Back With Sales Allowed

WITH SALES ALLOWED

This field is a bit field that can have a value of 0 for no (unchecked) or 1 for yes (checked).

 

This field governs whether the new mode "Back to Back With Sales Orders", on the Released Purchase Order Generation function is enabled or disabled.

 

When this field is checked and "Back to Back With Sales Orders" is enabled, the Released Purchase Order Generation function will allow the creation of new purchase order lines with a customer (sales) order requirement as the source of the purchase order.

 

In addition to adding the new purchase order lines, the function will automatically create order cross reference records.

hmtoggle_plus1Purchase Order Planned To Release Allowed

This Yes/No setting impacts on the Released Purchase Order Generation function.  This setting governs whether planned orders can be directly released or whether only the releasing of previously firmed orders will be permitted.

 

A setting of "Yes" will allow the release of a planned order but only for fixed account parts.  Planned orders for non-fixed account parts need to be firmed since a released stock purchase order requisition is mandatory for non-fixed account parts.

 

A setting of "Yes" will not prohibit the firming of planned orders and thus allows the release of both planned and firm orders.

 

A setting of "No" will disable the option Include Planned Orders on the function Released Purchase Order Generation and will only allow the release of previously firmed orders.

hmtoggle_plus1Purchase Order Receiving Days Early

This setting will determine the number of calendar days that will be added to the current date when defaulting the "Completion Dates Till ." on the "From Suppliers" movement functions, which will result in the display of available lines with completion dates equal to or less than the default date.

 

Make the necessary changes in the text box in the "Value" column.  Receiving days early must be between 0 and 120 days.  Functions referencing this setting include the following:

 

Completion Dates Till on Supplier to Inspection

Completion Dates Till on Supplier to Stores

hmtoggle_plus1Purchase Order Receiving Days Error

It is a Yes/No setting that will either allow or disallow the manual over ride of the "default date"  in Purchase Orders Receiving Days Early.

 

When the check box is ticked (Yes) it indicates that the manual over-ride of the default date in Purchase Orders Receiving Days Early is allowed.

 

Functions referencing this setting include the following:

 

Completion Dates Till on Supplier to Inspection

Completion Dates Till on Supplier to Stores

hmtoggle_plus1Purchase Order Release Option

This field provides control options that impact on the Released Purchase Order Generation function.  The options govern whether it is allowable to deviate from the quantity/date source order that is selected for release, irrespective of whether the source order is an MRP suggested order or a previously firmed order.

 

A setting of "Must Adhere to Source Order Date and Quantity" will totally disallow adjustments to the delivery date and/or quantity to be ordered.

 

A setting of "Allow Deviation from Source Order Date and Quantity" will allow for adjustments if the source order is for a fixed account part where the order is not linked to a Stocked PO Requisition.

 

A setting of "Allow Deviation from Source if Buyer is also Planner" will allow for adjustments, if the source order is for a fixed account part, where the order is not linked to a Stocked PO Requisition.  This is only the case if the part to be ordered has the same employee as its Buyer and Planner.

 

Deviation is never allowed where requisitions are involved, since budget checking, electronic budget moves and project end dates etc. comes into play and are validated when requisition changes are made relating to dates and values.

hmtoggle_plus1Purchase Order Release Price Default

This setting impacts on the Released Purchase Order Generation function and will apply the option chosen as a default on the PO Line Defaults tab for the Unit Price Default field.

 

This setting does not place a limitation on the Released Purchase Order Generation function and the user is still permitted to select another option on the Purchase Order Release function to be applied as the default.

 

The options are "No default", "Part Financial Year Data", "Last Purchase Price" and "Requisition Unit Price".

hmtoggle_plus1Ratio Checker Production Sensitivity %

Any percentage specified that is greater than zero, will result in a relaxation of the ratio checker (being the relation between the order line % complete versus the order line requirements % issued).

 

Over receipts (quantity complete greater than quantity ordered) are therefore possible on production orders within the constraints of this setting.

 

A setting of 10% will thus allow a yield of 10% more than the quantity ordered.  This relaxation of the ratio check is also applied on the following movements:

 

Store to Order Requirements

Order Requirements to Stores

Order Requirements to Scrap

Scrap to Order Requirements

Production to Stores

 

When this field is selected/clicked on, a text box is displayed below the grid allowing the user to enter the desired changes.

hmtoggle_plus1Requisition (Stocked Po) Inflate % Max

Is the maximum percentage with which a buyer may exceed the requisition value when placing the Purchase order.

 

This is merely to eliminate all the administration involved in adjusting the requisition amount up where relatively small variances are involved.  The system will allow the lesser of the Max Inflate %.

 

Make the necessary changes in the text box in the "Value" column.  The maximum requisition inflation percent must be between 0 and 80 percent.

hmtoggle_plus1Requisition (Stocked Po) Inflate Value Max

It is the maximum value with which a buyer may exceed the requisition value when placing the Purchase order.

 

This is merely to eliminate all the administration involved in adjusting the requisition amount up where relatively small variances are involved.  The system will allow the lesser of the Max Inflate Value.

 

Make the necessary changes in the text box in the "Value" column.  The maximum requisition inflation value must be between 0 and 10 currency units.

hmtoggle_plus1Requisition (Nstk) Max Date Offset

This field merely serves as a default when the system suggests a date when adding a new Non Stock Purchase Order Requisition .

 

The Requisition function will read the default value in this field and add it as a number of days to the current date, thus deriving the suggested maximum required date.  The user will however, still be able to over ride the suggested date on the Non Stock Purchase Order Requisition .

 

The value entered for this field will most likely represent an estimate of the administrative lead time to approve requisitions, as well as the time granted to your Company buyers to interpret the requisition request, obtain quotations, and release a non-stock purchase order requisition. It should also consider supplier lead times for general commodities.

 

It therefore also serves the purpose, of indicating that the suggested date is deemed reasonable in relation to the lead time required by the buyers under normal circumstances.  This field can have a maximum value of 1000 days.

 

Functions referencing this setting include:

 

Max Acceptable Delivery Date on the Non Stock Purchase Order Requisition

hmtoggle_plus1Requisition (Nstk) Pref Date Offset

This field merely serves as a default when the system suggests a date when adding a new Non Stock Purchase Order Requisition .

 

The Requisition function will read the default value in this field and add it as a number of days to the current date, thus deriving the suggested maximum required date.  The user will however, still be able to over ride the suggested date on the Non Stock Purchase Order Requisition .

 

The value entered for this field will most likely represent an estimate of the administrative lead time to approve requisitions, as well as the time granted to your Company buyers to interpret the requisition request, obtain quotations, and release a non-stock purchase order requisition. It should also consider supplier lead times for general commodities.

 

It therefore also serves the purpose, of indicating that the suggested date is deemed reasonable in relation to the lead time required by the buyers under normal circumstances.  This field can have a maximum value of 1000 days.

 

Functions referencing this setting include:

 

Max Acceptable Delivery Date on the Non Stock Purchase Order Requisition

hmtoggle_plus1Requisition (Order Issues) Auto Release If 0 Value

IF 0 VALUE

This setting governs whether the automatic releasing of order issue requisitions should apply to order issue requisitions with a zero value as well.

hmtoggle_plus1Requisition Request/Release Single Person Ceo Limit

This setting will allow the specification of an amount to act as a limit below which the CEO of the company will be allowed to be the Beneficiary and also release a requisition.

 

The beneficiary of a requisition can be either the Requestor, the Driver as specified on a transport requisition or the Beneficiary on a Cash Advance, Non Stock PO or Service requisition.

 

If a company does not want this setting to be applied, the amount can be set to zero.  This will force the release of a requisition by another person.

 

This setting is independent of the CEO's personal/job assignment limits as determined on his cost centre or employee record and all other rules for approval of requisitions still apply.                

This setting is referenced by the Requisitions function.

hmtoggle_plus1Requisition Request/Release Single Person Division Limit

LIMIT

This setting will allow the specification of an amount to act as a limit below which the Division Manager or Division Accountant will be allowed to be the Beneficiary and also release a requisition.

 

The Beneficiary of a requisition can be the Requestor, the Driver as specified on a transport requisition or the Beneficiary as specified on a Cash Advance, Non Stock PO or Service requisition.

 

If a company does not want this setting to be applied, the amount can be set to zero.  This will force the release of a requisition by another person.

 

This setting is independent of their personal or job assignment limits as determined on cost centre or employee records.  All other rules for approval of requisitions still apply.

 

This setting is referenced by the Requisitions function.

hmtoggle_plus1Requisition Request/Release Single Person Others Limit

OTHERS LIMIT

This setting will allow the specification of an amount to act as a limit below which the employees in the Organisation will be allowed to be the Beneficiary and also release a requisition.

 

The Beneficiary of a requisition can be the Requestor, the Driver as specified on a transport requisition or the Beneficiary on a Cash Advance, Non Stock PO or Service requisition.

 

If a company does not want this setting to be applied, the amount can be set to zero.  

 

This will force the release of a requisition by another person. This setting is independent of their personal or job assignment limits as determined on cost centre or employee records.  All other rules for approval of requisitions still apply.

 

This setting is referenced by the Requisitions function.

hmtoggle_plus1Reallocate Requisition To Other Account

This option is only applicable to Employee Expense requisitions. The available money can then be allocated to different accounts according to the selected setting.

 

When "ALLOW ACCOUNT DEVIATION WITHIN DIVISION/COST CENTRE" is selected only accounts from that specific Division or Cost Centre can be use to move the money between.

 

When "ALLOW WITHOUT RULES" is used, no rule will stop the money from being moved between any account in any Division or Cost Centre.

 

When "DISALLOW" is used, normal rules will block the user from moving money to any other account than the one selected on the Employee Expense Requisition.

 

Functions referencing this setting include the following:

 

Bank Transactions

hmtoggle_plus1Serial And Lot Tracking To End Item Level

When this setting is checked, and a part is changed to serialised or lot controlled on the Part Master function, a check is performed to determine if the next level parent(s) of the part are also serialised or lot controlled. This applies to MRP Planned and Non-Phantom parts.

 

If the part is changed to not serialised "No", or Lot Controlled is set to off (unchecked) on the Part Master function, a check is performed to determine whether the components of the part are serialised.  If they are serialised and this setting is checked, the change is not allowed.  This applies to MRP Planned and Non-Phantom parts.

 

If a phantom (source "N") part is linked in a product structure, the structure is exploded to determine if MRP Planned and Serialised or Lot Controlled parts exist (if this setting is checked).  If such a part(s) exist, a check is performed to see that the part(s) have serialised or lot controlled parents where the parts are MRP Planned.  If they are not serialised or lot controlled, the linking of the phantom part will not be allowed.

 

This setting is also used in conjunction with the field Equipment Base Option on the Product Master function, to govern the creation of an equipment base on the movement Production to Customer.

 

When this setting is checked, the movement on the Production to Customer, Production to Stores and Production to Crating functions will only be allowed if the parent serial/lot numbers were linked via the Serial Number Linking function to the serialised components.

 

The checks will also be applied on the movement "Production to Customer" where the field Equipment Base Option is checked on the Product Master function to determine whether serialised components issued to a customer special order should be used in the creation of the equipment base.

 

When this setting is not checked, the above checks will not be performed to ensure the serialised parent to component relationships.

 

Functions referencing this setting include the following:

 

Change on the Part Master

Equipment Base Option on Product Master

Serial Number Linking

Production to Crating

Production to Customer

Production to Stores

Product Structure

hmtoggle_plus1Settlement Days Min (Purchase Orders)

It is a constraint on the settlement days that can be specified on a customer order or on the external organisation record of a supplier.

 

Make the necessary changes in the text box in the "Value" column.  The minimum settlement days must be between 0 and 180 days.  Functions referencing this setting include the following:

 

Expected Settlement Days on Creditors

Settlement Days on External Organisation

Settlement Days on Released Purchase Order Generation

hmtoggle_plus1Settlement Days Max (Customer Orders)

It is a constraint on the settlement days that can be specified on a customer order or on the external organisation record of a supplier.

 

Make the necessary changes in the text box in the "Value" column.  The settlement days max (customer orders) can be between 7 and 180 days.  Functions referencing this setting include the following:

 

Settlement Days on External Organisation

Settlement Days on Sales Order Wizard

Settlement Days on Customer Orders

hmtoggle_plus1Settlement Days Default

It is the default for the settlement days that will be applied on specified on the External Organisation record.

 

Make the necessary changes in the text box in the "Value" column.  The default settlement days must be between 0 and 180 days.  Functions referencing this setting include the following:

 

Settlement Days on External Organisation

Settlement Days on External Organisation

Settlement Days on Customer Orders

Settlement Days on Released Purchase Order Generation

Expected Settlement Days on Creditors

hmtoggle_plus1Settlement Discount (Creditors) Automatically Applied

This is a Yes/No setting.  If set to "Yes", the function will automatically apply settlement discount to Receipt, Advance Payment and Additional Cost links.

 

Links to Purchase Orders will calculate the discount by applying the settlement discount percentage as specified on the purchase order line.  A credit link will be inserted with comments stating the application of a settlement discount.  This link will be inserted if the settlement days applied on the function are equal to or less than the settlement days specified on the purchase order line.

 

Links to Service Requisitions will apply the settlement discount percentage and settlement days as defined on the External Organisation record of the service provider.  The user can however, delete any suggested credit links for settlement discount before applying the Link.

 

If a requisition is involved for the financing of the transaction, the credit will be passed on to the Requisitions' actual amount.

 

If set to "No", any credits applied to the invoice amount must be manually entered by the

user via the "Credit Link" button.

 

The Invoice Line Links Grid on Creditors references this setting.

hmtoggle_plus1Settlement Discount Max % (Customer Orders)

It is a constraint on the settlement discount that can be specified on a customer order or on the external organisation record of a supplier.

 

Make the necessary changes in the text box in the "Value" column. The settlement discount max % can have a value between 0 and 99 percent.  Functions referencing this setting include the following:

 

Settlement Discount % on External Organisation

Settlement Discount % on Customer Orders

Settlement Discount % on Sales Order Wizard

hmtoggle_plus1Settlement Payment Control

This control sets the Creditors Payment option for the company where the policy stated that:

"PAY ON TIME PLUS SELECTIVE EARLY PAYMENTS", means that Creditors accounts Payable will be forced to settle all invoices due for payment up to the current date plus the option to selectively settle invoices only due for settlement at a future date.

 

"PAY ON TIME": means that Creditors Accounts Payable will be forced to settle all invoices due for payment up to the current date. The option to selectively settle invoices only due for settlement at a future date is not available for this mode.

 

"SELECTED PAYMENTS ONLY", means that Creditors Accounts Payable will not be forced to settle all invoices due for payment up to the current date, but will have the freedom of choice to sellect any invoices for payment irrespective of the expected settlement date.

hmtoggle_plus1Settlement Term Control

This setting governs whether the user may use a different settlement term compared to the Default Settlement Term.

hmtoggle_plus1Server Process Timeout (In Sec)

It is the number of seconds since the last call to the database server without receiving a response, after which the call will be abandoned and a resulting message will be given to such effect.

 

Make the necessary changes in the text box in the "Value" column.  This setting can have a value between 60 seconds and 3300 seconds.

 

An ideal value for this field would be around 300 seconds (5 minutes).

hmtoggle_plus1Shelf Life (Days) Max

Is a constraint on the shelf life days that can be specified for any product in your Company for the purpose of preventative maintenance, sell by or expire dates.

 

NOTE: This applies only to products where the shelf life is a real inherent feature.  A zero value in the field Shelf Life In Days on the Part Master screen implies an unlimited shelf life.

 

Make the necessary changes in the text box in the "Value" column.  The maximum shelf life in days must be between 2 and 3660 days.

hmtoggle_plus1Stock Valuation Method

This field allows for three valuation methods i.e. standard cost and average cost.

 

 

The Average Cost options apply the average cost of a stock record as defined in the Location table, when stock is issued.  Stock is valued at the total cost of the movement where the stock was sourced, i.e. if the stock was purchased the stock value will be the sum of the order cost including any additional costs incurred on the Purchase order.  The stock value will be captured on the location total as a unit price for the stock and will be averaged in accordance with the averaging rule of the inventory as expressed on the Store into which the stock is being received.

Any subsequent movements of the inventory will be performed on the average cost of the location.

Should stock be moved to other entities still in the balance sheet of the company,  and the new location like for instance a new store location is not unique, it will be averaged according to the new location's Store averaging rule. If stock is issued to a requirement against an Order, the stock will be averaged on the requirement it was issued to with other stock of the same part that might have been issued to the same requirement.

If stock is issued to an entity outside of Stock or WIP it will retain it's average cost an if it is returned at a stage the original cost at which it was issued will be retained.

 

 

The Standard Cost Option will use the Part Financial Year Cost of the Current Financial year for inventory and movement valuation. An update of the Part financial year data in the current Financial year will lead to a automatic revaluation of all the inventory in the Location Table, Work in Progress on the Requirements Table and any stock in IRI as per the Order line Table.

At the end of a Financial year or in the beginning of a new Financial year the Stock, Work in Progress and Stock in IRI must be revalued to reflect the values in the new Financial year. This revaluation has to be performed via the function Year End Part Revaluation. It is important to note that the front end function has to be used in this regard. The function can be used at any time after completion of the last movement in the old year and before the first movement is allowed in the new year.

The system will prevent the any movements in the old financial year after the job was performed and in the new financial year unstill the job has been performed.

 

To change the Cost option on System Configuration is a Company Decision which cannot be performed on the flight as all of the following needs to be in place and be compatible with the cost option chosen.

Settings on Stores regarding the averaging rule of locations. For Standard cost this rule should be set to Not Applicable while in Average Cost the rule can be varied between Average by Location, Average by Store, or Average by Division.

Settings on Part Master controls the Last Average Cost Calculation Method which should be set to Last Movement Unit Cost or Average of Locations in an Average Cost database or Not Applicable in a Standard Cost database.

Setting on Division allows the user to automatically update the Part Financial Year cost to reflect the Last Average Cost on Purchased or Subcontract parts in an Average Cost database. This will keep the Part Financial Year data current. It can be varied per Division.

Setting on Product Master for Landed Cost Preferences should be setup for Preference One, Two and Three. It can be varied between Part Financial Year date, Last Average Cost, Last Purchase Price and  Preferred Supplier List Price while in Standard Cost the preferences can only be Varied between Part Financial Year data, Last Average Cost and Preferred Supplier List Price.

When Changing the Cost Setting from Standard to Average Cost the current Part Financial Year data must be scripted from the Part Financial Year table  to the Average Cost column on the Location Table as well as the Requirements Table.

EXAMPLE:

 

The standard costing method will require predefined part fin year data records for the current year, prior to allowing the selection of the part on a specific function.  This rule will not apply if a different stock valuation method is selected.

 

Functions referencing this setting include the following:

 

Crating to Store

Material , Sub-Contract , and Transfer Cost on the

Part Master

Purchase Orders

Released Purchase Order Generation

Requirements

Sales Order Wizard

Stock Purchase Order Requisition

Stores to Crating

Store

 

If the Costing Method is changed from Standard to Average Costing, the current stock and stock Requirements on all orders needs to be valued at the present value as on the Part Financial Year Data table.

 

The Stock Value will be carried on the Location table, and will be averaged out according to the setting on the Store table for the Store into which the goods are being received. The settings will enable average stock by Location, or by Store, or by Division where the same Stock Account per Part applies.

hmtoggle_plus1Timeout Client Thread (Minutes)

It is the number of minutes, since the establishment of a thread via a database call, after which the thread will be deleted (timed out).

 

Make the necessary changes in the text box in the "Value" column.  The client thread timeout must be between 2 and 15 minutes.

hmtoggle_plus1Tax Policy

This setting specifies the method applied to calculate tax. The available options are:

 

1.  Calculate Tax via the application of Tax Codes with predefined Tax Percentages.

2.  Calculate Tax via the application of a Third Party interface such as Taxware or Vertex.

 

If your Tax is based on "Value Added Tax" (V.A.T.), always apply option 1(Tax Codes).

 

If your Tax is based on "General Sales Tax" (G.S.T.), and you do not interface with a Third Party Tax System, select option 1(Tax Codes).

 

If your Tax is based on "General Sales Tax" (G.S.T.), and you do interface with a Third Party Tax System such as Taxware or Vertex, select option 2(Tax Calculation via Third Party Interface).

hmtoggle_plus1Tax Percentage Maximum

It is the maximum tax rate applicable to your area/country.  This value will be applied to limit the tax percentage entered on Purchase Orders, Customer Orders, Bank Transactions, Creditors, Debtors and other screens applying a TAX percentage.

 

It is advised that you set the value to at least 0.1% higher than the default Tax percentage.  The reason being that calculated Tax amounts where a 3 decimal value is rounded to a 2 decimal value, will result in a slightly higher resulting percentage.

 

Make the necessary in the text box in the "Value" column. The maximum Tax percentage must be between 0 and 80 percent.  Functions referencing this setting include the following:

 

Tax Percentage on External Organisation

Differential Tax % on Commodity Codes

Total Tax Amount on Debtors

Tax % column in Grid on Released Purchase Order Generation

Tax % on Sales Order Wizard

Tax % on Customer Orders

Tax % on Purchase Orders

Tax % in Linked Lines grid on Stores to Customer

Base Additional Cost Tax % on External Organisation Parts .

hmtoggle_plus1Tax Percentage Default

It is the default TAX rate applicable to your area/country.  This rate will be defaulted to Purchase Orders, Customer Orders, Bank Transactions, Creditors, Debtors and other screens applying a TAX percentage.

 

The user may however, adjust the defaulted percentage if it is not deemed correct for the transaction being performed.  Make the necessary in the text box in the "Value" column.

 

The default Tax percentage must be between 0 and 40 percent. Functions referencing this setting include the following:

 

Tax % on External Organisation

Tax % on Bank Transaction

Tax % on Customer Orders

Tax % on Purchase Orders

Tax % in Linked Lines grid on Stores to Customer

Unit Price on Creditors

Tax % on Sales Order Wizard

Commodity Codes

hmtoggle_plus1Tax Integration System

This setting specifies with which Tax Software package does our company integrate.  Possible values are "T" for Taxware, "N" for None and "V" for Vertex.

hmtoggle_plus1Tax Differential

It is a Yes/No setting used to specify whether or not, differential TAX is applicable in your Company.

 

Select or deselect this setting by clicking on the check box in the "Value" column.  If ticked, differential Tax is applicable in your company else it is not.

 

Functions referencing this setting include the following:

 

Differential Tax % on Commodity Codes.

hmtoggle_plus1Tax Applicable

It is a Yes/No setting used to specify whether TAX is applicable in your Company.

 

Select or deselect this setting by clicking on the check box in the "Value" column.  If ticked, Tax is applicable else it is not applicable.

 

If Tax is not applicable, the Tax Percentage Max and Default Tax Percentage must be set to zero, with the Differential Tax being set to "No".

 

Functions referencing this setting include the following:

 

Tax % on External Organisation

Tax Number on External Organisation

Tax Number on Company Information

Tax Number on Division

Tax % in Linked Lines Grid on Stores to Customer

Tax % in Grid on Debtors

Tax % on Released Purchase Order Generation

hmtoggle_plus1Timesheet Cutoff Frequency

This option setting runs in conjunction with Timesheet Cutoff Days. It is divided into periods of days, weeks, months or quarterly as options for the Timesheets to be entered.

 

This represent the time resolution in which timesheet must be entered.  If the node manager forces the entry of the timesheet's Target Date and / or Hours Remaining, the system will check that the timesheet employee has entered a value for at least one of the timesheets in a  given Timesheet Cutoff Frequency.  For example, if the timesheet cutoff frequency is 'Weekly', then at least one of the timesheets in that week must have the Hours Remaining and / or Target Date (as per the node setting) entered.

hmtoggle_plus1Timesheet Cutoff Days

This option setting runs in conjunction with Timesheet Cutoff Frequency.  A number can be added indicating the amount of days allowed after the cutoff frequency period, for the timesheets to be entered.

 

This represents the number of days (either working or non-working, depending on interpretation) after the end of a timesheet cutoff  frequency, where the timesheet must be resolved.  For example, if the cutoff frequency is 'Weekly', and the cutoff days is 2, then all  timesheets must be resolved by Tuesday night the next week (since a timesheet week runs from Monday to Sunday).  All timesheets not  resolved will be deemed late by Wednesday morning.

 

This setting is not specifically implemented anywhere in Qmuzik, since it is largely dependant on the implementation-specific interpretation of what a 'late' timesheet constitutes.  It can either mean the timesheet is not node approved, or not captured, or not cost centre approved.  To implement this setting, a 'Timesheets Overdue' report must be written.

hmtoggle_plus1Transport Rate Min

It is a constraint on the transport rate per distance unit, for example, kilometers that can be specified for a vehicle type on the Vehicle table.

 

Make the necessary changes in the text box in the "Value" column.  Functions referencing this setting include the following:

 

Rate/Kilometer on Vehicle

Rate/Kilometer on Transport Requisition

hmtoggle_plus1Transport Rate Max

It is a constraint on the transport rate per distance unit, for example, kilometers that can be specified for a vehicle type on the Vehicle  table.

 

Make the necessary changes in the text box in the "Value" column.  Functions referencing this setting include the following:

 

Rate/Kilometer on Vehicle

Rate/Kilometer on Transport Requisition

hmtoggle_plus1Transport Distance Units (Single)

It is the measure used for transport distance in your country, for example, Kilometer, Mile etc.

 

Make the necessary changes in the text box in the "Value" column.  The transport distance units (single), may not be less than three characters. Functions referencing this setting include the following:

 

Transport Requisition on Requisitions

Estimated Kilometers Traveled on Transport Administration

hmtoggle_plus1Transport Distance Units (Multiple)

It is the measure used, for transport distance in your country, for example, Kilometers, Miles etc.

 

Make the necessary changes in the text box in the "Value" column. The transport distance units (multiple), may not be less than 3 characters. Functions referencing this setting include the following:

 

Transport Requisition on Requisitions

Actual Kilometers Traveled on Transport Administration

hmtoggle_plus1Trade Discount Max % (Customer Orders)

It is a constraint on the trade discount that can be specified on a customer order or on the external organisation record of a customer.

 

Make the necessary changes in the text box in the "Value" column.  The trade discount max % can have a value between 0 and 99 percent.

Functions referencing this setting include the following:

 

Trade Discount % on External Organisation

Trade Discount % on Customer Orders

Trade Discount % on Stores to Customer

Trade Discount % on Sales Order Wizard

Trade Discount Percentage on Product Master

hmtoggle_plus1Uom Over Receipt % Max

It is a constraint on the unit of measure over receipt % that can be specified for any unit of measure on the Unit of Measure function.

 

Make the necessary changes in the text box in the "Value" column.  The UOM Over Receipt % Max must be between 0 and 80%.

hmtoggle_plus1Uom Force Predefine Of Conversion

This is a Yes/No setting.  If set to "Yes", a unit of measure conversion must be predefined for a part on the Part Unit of Measure Conversion function before a unit of measure conversion can be applied on either Purchase Orders or Customer Orders for the Part.

 

If set to "No", both Purchase and Customer orders will allow the user to apply unit of measure conversions on Purchase and Customer orders, but the user will have to supply the conversion factors to the order in order to calculate the respective quantities.  For parts with predefined UOM conversions, users can also select undefined units of measure for the part in question on a "No" setting.

 

Functions referencing this setting include the following:

 

Ordered Unit of Measure on Purchase Orders

Ordered Unit of Measure on Customer Orders

Contract UOM in Grid on Released Purchase Order Generation

 

hmtoggle_plus1Number Control Independent Division

This field governs how number control per division can be set up. If it is on, only independent business entities can have seperate number control numbers. If the setting is off, all divisions can have independent number control ranges.

 

hmtoggle_plus1MTT Interface

“MTT Interface”(Data Type = Bit)

The default for the field “MTT Interface” will be 0(Unchecked).

This field is an indicator to the system that the MTT functionality is used for clocking on order operations.

When the user wants to delete an order operation and if this field is checked the system will perform and additional check to determine if any clocking’s exists in MTT for the order operation and if yes an error will be raised.