Preferences

SYSPRO Ribbon bar > Setup > Setup Options > Preferences

This enables you to monitor changes made to suppliers and currencies. You can view these changes in the Supplier Amendment Journal and Currency Amendment Journal programs.

This enables you to create and maintain a series of recurring entries that you want to post into Accounts Payable.

This enables you to enter notations against each distribution entry processed in the AP Invoice Posting program.

When you run the month end function of the AP Period End program, this accumulate all invoices, debit notes and credit notes for each supplier into a single invoice in the month that they are due.

Indicate whether you want to validate the supplier class defined against a supplier.

Indicate whether you want to validate the geographic area defined against a supplier.

This enables you to restrict the contra of credits and invoices belonging to the same branch when using the Contra invoice option of the AP Invoice Contra program. You typically select this if you have defined different General Ledger control accounts for your Accounts Payable branches.

This enables you to monitor changes made to customers and currencies. You can view these changes in the Customer Amendment Journal and Currency Amendment Journal programs.

This displays only customers linked to the AR branch associated with the operator when browsing on customers. The AR branch default is configured using the Operator Browse program.

If AR payments are linked to Cash Book, then the deposit slip posts these payments directly into Cash Book.

If integration is in detail or by bank, then payments for a single bank, currency, posting period and year are accumulated and printed on a single deposit slip.

If integration is by cash journal, then a new bank deposit slip is created for each cash journal generated. The journals are not purged if the deposit slip has not been printed.

This must be enabled to allow the processing of foreign currency transactions against customers.

This enables you to print an invoice for each posting made against a customer using the AR Post Permanent Entries program.

This forces the entry of a valid customer class when capturing details for your customers. Customer classes are captured using the Browse on Customer Classes program and assigned to customers using the Customers program.

This enables you to post to a different AR branch from the one defined against the invoice when processing payments and adjustments in the AR Payments and Adjustments program.

This prevents Point of Sale transactions from being posted by the AR Bank Deposit Slip program.

Select this if you require the tax value to be added to the merchandised value before calculating terms discount.

Select this if you require the freight value to be added to the merchandised value before calculating terms discount.

Select this if you require other charge values (e.g. miscellaneous charge lines) to be added to the merchandised value before calculating terms discount.

If you are using Trade Promotions and don't select this option, then the terms discount is calculated on the gross amount of the invoice. Off-invoice or line promotion values that appear as negative miscellaneous charges on the order are ignored.

Select this if you require terms discount to be calculated for credit and debit notes.

Enable this to calculate the taxable portion of settlement discount according to the tax code applied at line level for the invoice. Otherwise, the taxable portion is calculated using the single tax code assigned at the time of payment.

This generates a single discount note document per payment processed using the AR Payments and Adjustments program. A line is printed on the note document for the discount values for each individual invoice paid with the payment.

To avoid duplicate transactions being printed on the discount notes, ensure that the next discount credit note and debit note numbers have not previously been used. If you don't select this option, then one discount note is printed for each invoice paid.

Enable this to generate a collector list for a specific salesperson using the AR Collector Run Maintenance program and to capture payments collected for that salesperson.

Enable this to generate a collector list for a specific geographic area using the AR Collector Run Maintenance program and to capture payments collected for that area.

This generates documents for debt collection and recording outstanding invoice amounts collected from customers.

These documents are typically used when the salesperson must collect payment before being paid commission.

The AR Collector Run Maintenance program generates a collector list of invoices for which payment must be collected and to capture payments collected from customers against those invoices. The AR Payment Run program posts the payments received to the customers' accounts.

This indicates that authorization of the payment run is required before it is created.

This allocates post dated check amounts to specific invoices in the AR Post Dated Checks program.

This is enabled when the Collector required option is enabled (and cannot be disabled).

This lets you run the AR Post Dated Check Status program to maintain the status of post-dated checks as well as ensure that only cleared post-dated checks are posted during a payment run.

This enables you to link assets together as master and sub assets. You would typically use sub-assets for single assets which comprise components of significant value and which can be identified separately. Depreciation for the master and the sub-assets can be calculated at different rates.

This enables you to monitor changes made to asset information. You can view these changes using the Asset Amendment Journal program.

This deducts the residual book value from the cost of an asset before calculating the book value depreciation. Otherwise this is calculated on the cost of the asset, ignoring the residual value. Either way, the asset is depreciated only until the book value residual amount is reached. If you enable this option during the life of an asset, then depreciation is based on the difference between the asset's original cost and its residual value from this point onwards. Historical values are unchanged.

This deducts the residual tax value from the cost of the asset before calculating the tax value depreciation. Otherwise this is calculated on the tax cost of the asset. Either way, the asset is depreciated only until the tax residual amount is reached.

These options enable you to deduct the Residual value defined against an alternate valuation before calculating the depreciation value for that alternate valuation.

This creates entries for assets with no count differences when you confirm an asset count. Count differences occur when the asset quantity counted is not equal to the asset quantity saved in SYSPRO. These CNT type entries are displayed in the Asset Entries pane for the Book value of the Asset Query program and are useful for audit purposes (i.e. to prove that an asset was counted).

Select this to allow the processing of foreign currency transactions in Cash Book by maintaining foreign currency banks, or by entering foreign currency transactions against local currency banks. We recommend you run the Balance function of the Cash Book Period End program to ensure that the local value of the current balance is correctly calculated for foreign banks. This must be selected if AR is linked to the Cash Book and you want to process payments against foreign currency customers.

Select this to be able to create and maintain a series of entries that must be posted automatically into Cash Book on a given day of a particular month. De-selecting this option (after having created permanent entries) does not have any effect on the system. However, if you later decide to make use of the facility, then any currently valid entries are automatically posted when next the CB Permanent Entries Posting program is run.

Select this to be able to enter a notation against each GL distribution entry processed in the Cash Book Deposits and Withdrawals program. If Cash Book is linked to General Ledger in detail or summary, then the notation entered is passed through to the General Ledger system. The notation is printed on the Cash Book Journal, Cash Book Distribution Report and Cash Book Print reports.

This includes the current statement balance and current bank balance on the recap screen that is displayed when you exit the Cash Book Deposits and Withdrawals program. This option is enabled by default, so we recommend that you deselect this if you do not want operators to be able to view this information.

This enables you to monitor changes made to EFT Cash Book beneficiaries using the EFT Cash Book Beneficiaries program.

Select this to reverse provisional journals automatically at period and/or year end. Entries are made to the General Ledger journal and detail files in the next period. You typically process provisional journals for income accrued (but not yet received) or expenses incurred (but not yet paid) in a specific accounting period.

Select this to be able to produce a single tax report for sales transactions processed in the Accounts Receivable and Sales Order modules and for transactions posted in the Accounts Payable and Cash Book modules. It also enables you to enter a tax amount when processing transactions using the AP Invoice Posting, Cash Book Deposits and Withdrawals and CB Permanent Entries Posting programs (even if the Tax distribution method is set to Not required in Accounts Payable and Cash Book).

This enables you to restrict the viewing of account balances within the General Ledger Codes listview. It does not suppress the display of account balances in the GL Query or GL Structure Query programs.

This enables you to prevent unauthorized postings being made to individual ledger accounts.

This enables you to define different levels of integration for specific ledger account codes. This is particularly useful when the sub-ledger is linked to the General Ledger in detail, but for specific ledger accounts against which postings are made, you only want summary information passed through to the General Ledger, and vice versa.

This enable you to indicate the accounts types for which you may require account analysis. Disabling all the account types against this option does not switch off GL analysis; this will need to be done against each GL account code for which analysis has been enabled.

This enables you to monitor committed and uncommitted costs against the budgets for the ledger codes. It only applies to non-stocked items and services. For commitment accounting to function correctly, GL period end dates must be defined for the entire current year.

Select this to be warned when the value of a transaction causes the budget to be exceeded. An error is displayed (regardless of your selection here) when the operator is disallowed from any activity exceeding a commitment budget.

Indicate the text to use to describe the values of committed and uncommitted costs for unallocated transactions. These are transactions which cannot be allocated to a period because they don't have a due date, or the GL period end dates are not defined.

These options apply to the recording of uncommitted costs, arising from purchase order requisitions.

Select this to monitor uncommitted costs.

This validates requisitions against the ledger account's budget.

This retains transactions once an uncommitted value becomes committed, or a committed value becomes an actual cost. The completed transactions are retained for the current year and removed at year end.

This increases the budget for the first period of a new year by any outstanding uncommitted value from the previous year (e.g. unposted commitments from the previous year are added to the budget for the new year).

These options apply to the recording of committed costs, arising from purchase orders.

This indicates whether you want to monitor committed costs.

This validates this type of commitment against the ledger account's budget.

This retains transactions once a committed value becomes an actual value. The completed transactions are retained for the current year and removed at year end.

Select this if the budget for the first period of a new year should be increased by any outstanding committed value.

This requires the authorization of journals captured using the GL Journal Entry or GL Entries Import programs before they can be posted. This does not apply to sub-module journals (i.e. ledger journals created for sub module transactions) or journals automatically posted by the GL Period End program (e.g. the reversal of provisional journals or the setting of expense accounts to zero at year end).

This requires the authorization of journals created for sub module transactions before they can be posted. You will be unable to select the Post GL journal option for any sub-module within the integration options (i.e. you will be unable to use the full real time General Ledger facility, as all sub-module ledger journals will have to be authorized and manually posted to the General Ledger using the GL Journal Entry program).

This restricts operators to only be able to view their own journals within the GL Journal Entry and GL Journal Report programs. An operator activity enables you to restrict operators to only be able to print their own journals. However, if the operator activity to authorize GL Journals is allowed for an operator, then all journals can be viewed regardless of the setting here and the operator performing a period or year end can also view all unposted journals, regardless of the selection here.

This enables GL journal numbering by period - typically selected if you process more than 99999 journals in any single ledger year or need to comply with regulatory requirements. Otherwise, numbering is from 0 through to 99999, regardless of the ledger period. You can enable this option at any time, but we recommend only doing so immediately after a period or year end (the system will override your numbering to avoid duplication of journal numbers within a specific period).

If copying next years' budget to the current year and next years' budgets are not found, then the system sets the current years' budget to zero and you will have to enter budgets manually for the new year.

Select this if you require an additional budget period for the year end period.

Assign your own description for the first alternate budget.

Assign your own description for the second alternate budget.

Assign your own description for the third alternate budget.

Assign your own description for the fourth alternate budget.

Assign your own description for the fourth alternate budget.

Assign your own description for the sixth alternate budget.

Assign your own description for the seventh alternate budget.

Assign your own description for the eighth alternate budget.

This is the date that will be used as the default planned dispatch date when creating a dispatch note. It can be the Company date, the Sales order ship date or No default date.

This enables you to indicate whether you want to print dispatch notes or dispatch invoices on-line from within the Dispatch Note Review or Dispatch Note Maintenance programs respectively.

This enables you to reprint dispatch invoices on-line.

This enables you to monitor changes made to stock information. You can view these changes using the Inventory Amendment Journal program.

This is used when the number of decimals for a stock item differs from the number of decimals specified at the Quantity per field for the same item.

Round ups decimal places of .5 or larger, and rounds down decimal places of .4 or less.

This is appropriate only where the full 3 decimal places is not held against the stock item on the product master file. In this case, you are advised to select Round up as values less than 0.5 will be rounded down to zero.

Select this to reject imported job and purchase order receipts if they exceed the acceptable cost variance percentage defined. This check is performed at the time of actually processing the import and not at the time of validating the import file. When this option is not enabled, no check is performed.

This prevents the average cost of a stock item being recalculated when you post a negative receipt using the Inventory Movements, Purchase Order Receipts or Job Receipts programs. If you don't select this option, then the average cost for a stock item is recalculated only if the negative receipt does not cause the quantity on hand for the stock item to become negative. This option is only available if the Costing method is set to Average, or if Costing per warehouse is selected.

This maintains accurate warehouse costs for items received into stock by allowing you to specify a part of the transaction value comprising non-merchandise costs and to store these values in ledger accounts. You must select this if you intend using the full GIT transfers facility and you want to apply a cost multiplier for transfer-supplied items (as well as if you enabled the 'Include non-merchandise costs in last cost' option to include the cost multiplier value in the last cost of an item).

Select this to allow a batch serial number that exists against a stock code in one warehouse to be receipted against the same stock code in another warehouse. Otherwise, a batch serial can only exist in one warehouse and subsequent receipts against the serial number must occur in the warehouse in which it is stocked.

Select this if you do not require a List price code to be assigned to a stocked item. Note that if you are retaining a history of price changes then capturing a stock item without associating it to a price code will result in no price history being created for that item.

Select this to validate the product class assigned to a stock item. This option is ignored by the Sales Order Import and EDI Sales order lines programs as a valid product class must be defined against each line. Lines with invalid product classes are ignored by the export/import processes.

Select this to be able to backflush a bought out item and issue any attached materials and labor. This is typically an item that you purchase, but sometimes can be made-in so quickly that there is no need to set up a job. Alternatively, some companies initially purchase items but are responsible for warranty and service jobs on the item (e.g. appliances). These companies typically want to issue components and labor for the service without the overhead of maintaining a full manufacturing system.

If multiple bins is enabled, then this option enables you to include bin transfers when retaining transaction movements processed for a stock item. Otherwise, the bin transfer transaction can be printed on the Inventory Journal Report but no movement is created.

This enables the automatic creation of new bins when a non-existent bin is supplied against a transaction. If you are using fixed bins in the warehouse then this option doesn't apply - the bin must exist before you can process any transaction against it (including stock take capture/import). Bins are not automatically created when processing negative inventory transactions.

Select this to restrict access to the destination warehouse when performing a warehouse transfer out or a supply chain transfer. The system checks the warehouse security access settings and prevents the operator from processing supply chain transfers if that operator has been denied access to the destination warehouse. Similarly, the operator is prevented from processing a warehouse transfer out if access is denied to the destination warehouse.

Select this to include negative values arising from a negative on hand quantity in inventory valuations. This decreases the total value of stock.

This allows the transfer of a serial (currently selected for stock take) out of the stock take warehouse into another warehouse using the Bins, Lots & Serial Capture program.

This does not apply to serials created in the current stock take.

Select this to process all warehouses when running the Balance or Month end functions of the Inventory Period End program (i.e. you will not be able to select a specific warehouse to process). In order to finalize an Inventory month end and increment the current month number, all warehouses must be selected for processing.

Select this for the detection and subsequent reporting on variances during a stock take to be based on the percentage entered at the Maximum permitted field.

Select this for the detection and subsequent reporting on variances during a stock take to be based on the fixed quantity entered at the Maximum permitted field.

Indicate the cut-off percentage (or quantity) according to which variances detected during a stock take can be reported on using the Stock Take Variance report and queried using the Stock Take Query program. Variances are only calculated if this field is non-zero.

This defaults to browsing on multiple bins in bin number sequence.

This defaults to browsing on multiple bins according to the date on which items were received into the bin.

This allows you to add a stock code that already exists as a non-stocked item in the Quotations module. This applies to new stock codes added using the Stock Code Maintenance, Stock Code Copy and Quotation Stock Part Creation programs.

This displays the quantity available in each period, taking into account supply and demand.

This adds each period's regular ATP figure to the next period and displays a cumulative figure.

Select this to request the ledger code to be used as the distribution entry when processing inventory transactions.

This creates amendment journals for all changes processed against goods in transit. This information can be viewed using the GTR Detail Amendment Journals program.

This requests a ledger code when processing an inventory receipt transaction (i.e. this excludes purchase order receipts which are defined separately)

This requests a ledger code when processing an inventory adjustment transaction.

This requests a ledger code when processing an inventory issue transaction or an issue from stores requisitions.

This requests a ledger code when processing an inventory cost modification transaction.

This requests a ledger code when processing an inventory cost change transaction.

This requests a ledger code when processing an inventory physical transaction.

This requests a ledger code when processing an inventory stock transfer transaction.

This requests a ledger code when processing a purchase order receipt transaction.

This lets you change the default ledger code (typically an expense account) when processing the receipt of a non-stocked item.

This lets you change the default ledger code (typically the GRN suspense account) when processing the receipt of a stocked item or accepting an item from inspection into stock.

This lets you change the default ledger code when processing a non-merchandise receipt.

This lets you override the default WIP control account when processing a backflushing transaction.

Indicate the cut-off percentage for A and B items for classifying on the ABC Analysis, based on the annual usage value of items (i.e. the total cost of each item sold or issued over the past year). This defaults to 80.

Indicate the cut-off percentage for B and C items for classifying on the ABC Analysis, based on the annual usage value of items (i.e. the total cost of each item sold or issued over the past year). This defaults to 95.

This allows you to obtain the description of an in-transit item from the originating SCT - useful for customers who regularly change the description of items being transferred through the SCT process and need to see this description at all times. Any use of the stock description is obtained by tracing the appropriate information in the relevant sales order reprint file and using that description, if found. If the reprint has not been retained, then the inventory description is used.

This applies throughout SYSPRO where the lead time is applied to calculate the due date or receipt date of a transfer-supplied item (typically where the transportation of goods between warehouses is handled by a third party). Non-working days are not taken into account when applying the lead time (days) defined for transferring items between warehouses. Transfer-supplied indicates a stock item for a warehouse that is supplied by another warehouse, instead of a purchase order or job.

Select this to automatically deplete lots and/or serials when processing multiple issues for the same lot/serial. This option only applies to issues in Work in Progress and Inventory (cost buckets used in Sales Orders are always auto-depleted at the time the invoice or dispatch note is generated). This option is ignored when processing negative allocations in Work in Progress. A negative allocation mimics a receipt and therefore a new actual cost bucket is always created.

This allows you to view details of actual costs used in Inventory Movements and on lot or serial transactions. Otherwise the unit cost displayed is the warehouse cost based on the costing method applied to that warehouse. If the Lot traceable or Batch serial option is selected at the Actual costing field together with this option, then it applies to all modules and a movement record is output per actual cost bucket per lot/actual cost bucket per serial.

Select this to enable the equivalent option within the Balance function of the Inventory Period End program. If you select this option during the Balance function, the total value of the FIFO buckets and the total quantity is accumulated and used to calculate the new current cost of the item.

This option applies when the costing method of a warehouse is changed from FIFO to any other method. Select this to re-calculate the current warehouse cost for each item with a non-zero quantity on hand, based on the FIFO buckets. The value of each FIFO bucket is calculated and accumulated into a FIFO total value. This is then divided by the warehouse stock on hand to get the new current cost for the warehouse. If you do not select this option, then the current warehouse cost is not updated.

Indicate the default unit of measure applied when capturing stock items. The default unit of measure entered here is ignored when the units of measure are defined using the Maintain Global Defaults option in the Stock Code Maintenance program.

Enable this to always round quantities to the maximum number of decimals indicated against the stock code when converting between the different units of measure for the stock code.

Indicate the maximum number of decimals to round quantities when converting to different units of measure. This enables you to calculate quantities to a set number of decimals, even if it exceeds the maximum number of decimals against the stock code. This is only applied if you are not rounding to the number of decimals specified against the stock code. The entry against the stock code cannot exceed the entry here.

Select whether you want to print receipt documents in batch mode only or in batch mode and online.

Select whether you want to print issue documents in batch mode only or in batch mode and online.

Select whether you want to print transfers out documents in batch mode only or in batch mode and online.

Select whether you want to print purchase order receipt documents in batch mode only or in batch mode and online. If you are also using multiple bins, then you can only capture a single bin per receipt in the Purchase Order Receipts program.

Select whether you want to print inspection documents in batch mode only or in batch mode and online.

Select this to print inspection items online when receipting an item into stock.

Indicate the maximum number of decimals that must be printed when aligning your pre-printed stationery.

Select this to enable the Multiple Company Values option in the Inventory Query program, allowing you to view warehouse values and warehouse history for multiple companies. Your database format must be the same for all companies.

This lets you to indicate the companies for which you want to view warehouse values and warehouse history values in the Inventory Query program.

This displays prices and quantities when browsing on stock codes.

This limits the viewing of stock items to those warehouses which the operator is authorized to access. Against the operator, you must select the Filter reports and browses option for Warehouse in the Access pane and define a list of warehouses to which access is allowed/disallowed. This option applies only to the stock code browse, and is used to reduce the number of stock codes shown.

Indicate the default warehouse to display quantities when browsing on items.

This uses the warehouse defined against the operator.

This uses the default warehouse defined against the operator.

This uses the warehouse defined against the company.

This uses the warehouse defined at the Warehouse to use field against the stock item.

This uses the warehouse defined at the Distribution warehouse to use field against the item.

This allows you to deplete lots and bins automatically when processing a kit issue (stock is issued from the oldest, smallest lots and/or bins first).

This allows you to deplete lots and bins automatically in sales order entry, return merchandise, dispatch notes and back order releases (stock is issued from the oldest, smallest lots and/or bins first). This option takes precedence over the Request lots/bins/serials when reserving stock Sales Order Configuration option.

This depletes lots and bins automatically during Point of Sale entry. Stock is issued from the oldest, smallest lots and/or bins first.

This depletes the quantity (for which there is insufficient stock) from the default bin for items shipped in Sales Orders and kit issued in Work in Progress. You typically select this if you have enabled negative inventory and want to use automatic depletion to release or issue items (regardless of their stock level) for which you do not require a movement record through the system. The item cannot be serialized, traceable, or ECC-controlled.

Select this if you don't want to be prompted for the price of a component when adding a sales order for configuration. You are prompted to specify a price only if you are required to indicate a quantity.

Select this if you don't want to be prompted for the price of a component when adding a sales order for configuration, regardless of whether a price is held against the component. You are prompted to specify a price only if you are required to indicate a quantity.

Enable this to prevent stock items generated by the program from containing spaces in the stock code. This applies when generating a parent part using the Configurator Wizard program (e.g. when the parent code is generated by selection criteria).

This enables you to indicate which costs to use for bought out items at the time of creating a bill of material from within Product Configurator.

This uses the inventory cost for bought-out items when rolling up the single level costs towards the new parent created.

This uses the Bill of Material costs for bought-out items when rolling up the single level costs towards the new parent created.

Select this to be able to create a job and add a sales order line for a generated parent part which already exists as a stocked item. Selecting this option will only be effective if you are generating parent codes according to selection criteria. The generated parent must be a made-in stocked item and a bill of material for route 0 must be held on file for the existing parent.

Select this for the generated parent part in Sales Orders and Work In Progress to use the parent description entered within Product Configurator instead of the parent description from the inventory master file. If you enable the Update stock descriptions from inventory master file option then the descriptions entered are overwritten by the descriptions from the inventory master file.

Select this to prevent warehouse costs from being updated when configuring a product from within sales orders for an existing parent that does not have a bill of material and the quantity on hand is zero.

This lets you define conditions overriding when a stock code can be deleted.

This lets you delete a stock code that has been used in a product configuration (the Product Configurator module must be installed).

This lets you delete a stock code against which a customer/stock code cross reference exists (the Accounts Receivable module must be installed).

This lets you delete a stock code against which a supplier/stock code cross reference exists (the Accounts Payable module must be installed and the supplier/stock code interchange system must be enabled).

This lets you delete a stock code against which a valid drawing number exists (the Engineering Change Control module must be installed).

This lets you delete a stock code against which a bill of landed costs exists.

This lets you delete temporary stock codes that are associated with sales and/or purchase orders, providing that there are no quantities outstanding.

This lets you delete a stock code that is on hold.

This is the default algorithm to use when forecasting and defaults to 'Competition'. You can override this at stock code/revision/release/warehouse level.

Indicate the number of months (from 2 to 12) to include when calculating the mean. This defaults to 12. If the calendar is defined in weeks, the calculation still uses the number of months defined here to calculate the equivalent number of weeks. This parameter can be set as a default at company level and overridden for one or many stock code/revision/release/warehouse instances using the Forecast Calendars program.

Indicate the number of months (from 2 to 12) to include when calculating the median. This defaults to 12. If the calendar is defined in weeks, the calculation still uses the number of months defined here to calculate the equivalent number of weeks. This parameter can be set as a default at company level and overridden for one or many stock code/revision/release/warehouse instances using the Forecast Calendars program.

Indicate the number of months (from 2 to 6) to include when calculating the moving average. This defaults to 3. If the calendar is defined in weeks, the calculation still uses the number of months defined here to calculate the equivalent number of weeks. This parameter can be set as a default at company level and overridden for one or many stock code/revision/release/warehouse instances using the Forecast Calendars program.

This uses all the algorithms in turn within the look-back window to forecast what has already happened. It then compares the results of each algorithm with actual demand and uses the selected statistical formula to determine which algorithm performs best. Choosing different values for either of the two parameters can result in a different algorithm winning the competition.

This is the number of months into the past for which forecasts must be generated to compare algorithms. This defaults to 12.

This is the difference between the forecast and the actual sales for the period.

This is the average absolute deviation from the mean.

This is the sum of the squared forecast errors for each observation divided by the number of observations.

This is the average of the sum of all the absolute percentage errors.

This is the sum of the forecast errors divided by the mean absolute deviation.

Also known as double exponential smoothing, this algorithm calculates the forecast by adding a data component to a trend component. Each of these components has its own coefficient. Depending on the value of the coefficient, the algorithm will respond more slowly or more rapidly to trends. This algorithm does not detect seasonality.

This is the coefficient (between 0 and 1.0) used when calculating forecasts using this algorithm. This defaults to 0.7. The coefficient determines the weighting applied to the last two historic demands. The most recent demand is multiplied by the coefficient while the older one is multiplied by one minus the coefficient. This parameter can be set as a default at company level and overridden for one or more stock code/revision/release/warehouse instances using the Forecast Calendars program.

This is the coefficient used when calculating forecasts using this algorithm. This defaults to 0.6. You can override this at stock code/revision/release/warehouse level.

This calculates the forecast by weighting the contribution of the 6 periods immediately prior to the current one. Depending on the weighting values, the algorithm will respond more slowly or more rapidly to trends. This algorithm does not detect seasonality. The weightings for all periods added together must equal one. These parameters can be set as defaults at company level and overridden for one or many stock code/revision/release/warehouse instances using the Forecast Calendars program.

This is the weighting that should be applied to the two periods immediately prior to the period being forecast. This defaults to 0.5, meaning that these two periods contribute 50% to the calculation of the forecast.

This is the weighting that should be applied to the third and fourth periods prior to the period being forecast. This defaults to 0.3, meaning that these two periods contribute 30% to the calculation of the forecast.

This is the weighting that should be applied to the fifth and sixth periods prior to the period being forecast. This defaults to 0.2, meaning that these two periods contribute 20% to the calculation of the forecast.

This calculates the forecast by weighting the contribution of the 12 periods immediately prior to the current one. Depending on the weighting values, the algorithm will respond more slowly or more rapidly to trends. This algorithm does not detect seasonality. The weightings for all periods added together must equal one. These parameters can be set as defaults at company level and overridden for one or many stock code/revision/release/warehouse instances using the Forecast Calendars program.

This is the weighting that should be applied to the first three periods immediately prior to the period being forecast. This defaults to 0.45, meaning that these three periods contribute 45% to the calculation of the forecast.

This is the weighting that should be applied to the fourth, fifth and sixth periods prior to the period being forecast. This defaults to 0.25, meaning that these three periods contribute 25% to the calculation of the forecast.

This is the weighting that should be applied to the seventh, eighth and ninth periods prior to the period being forecast. This defaults to 0.2, meaning that these three periods contribute 20% to the calculation of the forecast.

This is the weighting that should be applied to the tenth, eleventh and twelfth periods prior to the period being forecast. This defaults to 0.1, meaning that these three periods contribute 10% to the calculation of the forecast.

The Holt-Winters algorithms are complex algorithms using three smoothing equations for level, trend and seasonality. The coefficients for these components of the forecast can be calculated by SYSPRO or set by the user. In the Holt-Winters Additive algorithm, the forecast is calculated by adding the three terms together. These parameters can be set as defaults at company level and overridden for one or many stock code/revision/release/warehouse instances using the Forecast Calendars; program.

This lets the system try to find the optimum coefficient values to use when forecasting, instead of the values at the coefficient fields below. Unless you have an advanced knowledge of how these algorithms work, we suggest that you let the system calculate the optimum values for the coefficients.

This is the level coefficient you want to apply when forecasting with this algorithm. This defaults to 0.

This is the seasonal coefficient you want to apply when forecasting with this algorithm.

This is the coefficient used when calculating forecasts using this algorithm. This defaults to 0.6. You can override this at stock code/revision/release/warehouse level.

The Holt-Winters algorithms use three smoothing equations for level, trend and seasonality. The coefficients for these components of the forecast can be calculated by SYSPRO or set by the user. In the Holt-Winters Multiplicative algorithm, the forecast is calculated by multiplying the three terms together. These parameters can be set as defaults at company level and overridden for one or many stock code/revision/release/warehouse instances using the Forecast Calendars program.

This lets the system try to find the optimum coefficient values to use when forecasting, instead of the values at the coefficient fields below. Unless you have an advanced knowledge of how these algorithms work, we suggest that you let the system calculate the optimum values for the coefficients.

This is the level coefficient you want to apply when forecasting with this algorithm. This defaults to 0.

This is the coefficient used when calculating forecasts using this algorithm. This defaults to 0.6. You can override this at stock code/revision/release/warehouse level.

This is the seasonal coefficient you want to apply when forecasting with this algorithm.

This is the number of months into the future for which you want to generate forecasts. This defaults to 12. The value chosen should be longer than the longest lead time for any stock code.

This is the default forecast calendar that must be used for forecasting. You can override this entry either singly or for multiple stock codes at stock code/revision/release/warehouse level using the Options Maintenance facility in the Inventory Forecasting and Inventory Optimization modules.

When adjusting for outliers, the demand history for any sales period for a given stock code/revision/release/warehouse that differs from the mean by more than the figure entered here will have an adjustment entry generated. This defaults to 3. Periods with zero demand are not adjusted. This parameter can only be set at company level.

Any stock code/revision/release/warehouse that (when tested for seasonality) has a seasonal profile correlation of less than the figure entered here will be deemed to be non-seasonal. This parameter can range from 0 to 1.0 (where 0 corresponds to no correlation and 1.0 to complete correlation) and defaults to 0.75. This parameter can only be set at company level.

This is the number of months of demand history that must be retained in the Inventory Optimization sales forecasting tables (a minimum of 36 months). 99 retains records indefinitely.

This automatically updates forecast history for sales and sales returns (for selected stock code/warehouse combinations) when next you run the Manual Forecasting, Batch Forecasting, Demand History Maintenance and Pareto Analysis programs. You should still run the IO Purge and Update program to update forecast history for all sales and sales returns. Otherwise the update to forecast history for sales and sales returns only takes place when you run the IO Purge and Update program.

This prompts you to aggregate sales history whenever you access the Families and Groupings program. You are prompted to perform the sales aggregation whenever you add to or delete an SKU, a consolidated warehouse item or a sub-collection in any collection, or when you maintain sales adjustments or adjust for outliers. Regardless of your selection here, the IO Purge and Update program performs the aggregation for you if an update is needed.

This generates journals for amendments made to Families and Groupings structures using the Families and Groupings program and enables you to monitor information that has changed for structures such as collection additions, changes and deletions and SKU (Stock Keeping Unit) additions and deletions. These changes affect the resultant forecast. You can list the journals using the IO Amendment Journal program.

This generates journals for amendments made to selection sets using the IO Selection Sets program. You can list the journals using the IO Selection Sets Amendment Journal program. This parameter can only be set at company level.

This generates journals for amendments made to policy settings using the Manual Forecasting, Batch Forecasting and Demand History Maintenance programs. You can list the journals using the IO Policy Amendment Journal program. This parameter can only be set at company level.

These options allow you to evaluate the effect of a stock policy. The model defaults to taking demand from the forecast. If there is no policy, then the suggested minimum is zero and the suggested maximum is the total demand for the period. These parameters can be set as defaults at company level and overridden for one or many stock code/revision/release/warehouse instances using the IO Stock Levels Modeling program.

Because the Optimization suite of modules uses a demand-driven approach, in most cases the inventory levels are determined by the forecasted demand.

This uses the forecast from the Requirements Calculation (stored in SYSPRO's Requirements Planning tables).

This uses the forecast created by the Inventory Forecasting or Inventory Families and Groupings modules. Last snapshot selects the last snapshot created for each stock code/revision/release/warehouse instance.

This applies the gross requirements rule defined against the stock item when calculating the demand for a stock code/warehouse. Sales order demand is used as the basis for the calculation to determine the minimum level required for each period. Otherwise, forecasts are always used as the demand.

This includes demand created by existing job allocations in calculating the model. This does not include demand from suggested jobs.

This calculates the maximum stock level using the batching rule. By default (with no policy in place) the model suggests a minimum of zero and a maximum equal to the total demand. If a policy is in place, the model calculates the minimum and maximum according to the policy. In either case, the calculation of the maximum will be modified by the effect of the batching rule.

This uses the total days in a period as part of the modeling calculation.

This uses only the working days in a period as part of the modeling calculation.

These parameters define the way in which the forecast accuracy program calculates the accuracy at each stock code/revision/release/warehouse instance and also at aggregated levels. They can be set as defaults at company level and overridden for one or many stock code/revision/release/warehouse instances using the IO Selection Sets program.

This compares the chosen forecast to the actual within the same period only. The forecast accuracy calculation only uses data pertaining to the period in question.

This compares the chosen forecast to the actual where both are calculated using a moving average. The forecast accuracy calculation uses data not only pertaining to the period in question but also to others near to it.

This indicates the forecast to use when comparing against sales for each period.

This uses the last forecast taken for the period.

This uses the last forecast for the period outside the lead time.

This uses the average of the most recent snapshots within the time window defined by the number of Snapshot months.

This uses the average of the most recent snapshots outside the lead time, within the time window defined by the number of Snapshot months.

This is the time window prior to the run date selected for the forecast accuracy review. If the calendar used is in weeks, then all the periods that fall within this time window are included. The time window can be anything from 1 to 12 months.

This is the time window for the periods used in the calculation of the moving average forecast in the forecast accuracy review. If the calendar used is in weeks, then all the periods that fall within this time window will be included. The time window can be anything from 1 to 12 months. This value is only used if the comparison type selected is Moving average.

This is the time window prior to the run date selected for the forecast accuracy review. If the calendar used is in weeks, then all the snapshots that fall within this time window are included. The time window can be anything from 1 to 6 months. This value is only used if the Forecast to use selected is either Average or Average outside lead.

Indicate the default pricing method to use during Purchase Order Entry. This can be based on the current inventory cost price (this defaults to a pricing method of Manual when capturing a stocked purchase order line if Activity Based Costing is required, or the order is for a foreign currency supplier, or FIFO or LIFO costing is implemented) the last price paid to the supplier, or the purchase price defined for the supplier.

This uses either the stocking or the alternate unit of measure as the order quantity.

Enable this option for completed orders to remain in a status of 4 until the number of days to retain completed purchase orders is exceeded. At that point the orders are purged (i.e. they are not moved to a status of 9).

You won't be able to maintain orders that were in a status 9 - Complete prior to switching on this option. Although you will be able to cancel a completed line, you won't be able to change a completed line.

This captures and prints alternate supplier prices on purchase order documents for local currency suppliers. It also enables the preference: Use alternate supplier price in the Purchase Order Format program and enables the Alternate supplier price field within the Browse on Supplier Stock Code Cross Ref program.

This retains purchase orders created without purchase order lines (typically to obtain the order number and later add the required lines). The header is created and retained in a status of 1 until the order is maintained. Otherwise purchase orders created without any detail lines are automatically cancelled when you exit the program. Adding a line and then cancelling it (even in the same run of the program) does not cancel the order. You have to manually cancel the order if it is not required.

This displays a warning when using the Receipt all function of the Purchase Order Receipts program if the acceptable cost variance percentage is exceeded. The warning is displayed for each line that exceeds the variance.

This sets a default shipping instructions message that you want to print on purchase orders.

This allows you to review demand for stock at the time of receipting an item into stock using the Purchase Order Inspection or Purchase Order Receipts programs. In the case of the Purchase Order Inspection program, this occurs when accepting an item into stock and, in the case of the Purchase Order Receipts program, when using the Receipting Quantity or Apportion Quantity functions.

This insert any additional purchase order text held against a stock item being purchased as comment lines. This only applies when creating a purchase order in the Purchase Order module (i.e. not when creating a purchase order via MRP).

This inserts as comment lines any dangerous goods text held against an item being purchased.

Enable this option for the status of an order that has been maintained but not printed to revert to 1 - Ready to print. This ignores the Reprint completed lines preference in the Purchase Order Format program and means you won't be able to reprint a purchase order with completed lines.

Don't enable this option if you want the order status to remain 4 - Printed after having been initially printed online. Any printing done during order maintenance is seen as a reprint and your selection at the Reprint completed lines option is taken into account.

This allow changes to the delivery address in the Purchase Order Header Information program, providing you have enabled the option: Restrict order to single warehouse and use for delivery address.

This enables you to modify the exchange rate at the time of capturing an order for a foreign currency supplier.

This allows you to add stocked and non-stocked items to blanket purchase orders using the Purchase Order Entry program (unless the BPO contract is fixed). If the item added is already part of the BPO contract, then the line details are pulled in from the contract and the relevant fields disabled (as these must match the contract). Otherwise only freight, miscellaneous and comment lines can be added and changed for any blanket purchase orders using the Purchase Order Entry program.

This forces the entry of a valid buyer when creating a purchase order, or requisition.

This validates the buyer at the time of creating a purchase order only if a buyer is actually entered.

This allows you to manually add normal purchase order line entries using only blanket purchase order programs if contracts are fixed, and standard purchase order programs for contracts that are not fixed.

This prevents the manual entry of normal purchase order lines (you will only be able to add entries using the blanket purchase order programs).

This permits the manual entry of normal purchase order lines using standard purchase order programs.

This applies to purchase orders created from sales orders.

This prevents adding a backorder line to an existing purchase order when the customer/customer purchase order numbers differ.

This allows the original customer and customer purchase order numbers on the p/o to be changed.

This allows a backorder line to be added to an existing p/o when the numbers differ.

This indicates how you want to confirm and notify the originator of a requisition when processing a partial purchase order receipt for the requisition.

This routes the requisition back to the originator only for the first receipt processed.

This notifies the originator each time a receipt is processed, regardless of whether it is acknowledged in the originator's Routed to view.

This routes the requisition back to the originator for the first receipt processed.

This updates the accumulated capex value with any changes made to a purchase order (including cancelled lines, which will reduce the accumulated capex value).

This doesn't update the accumulated capex value with any changes made to a purchase order.

This updates the accumulated capex value when purchase order lines are cancelled (i.e. the accumulated capex value is reduced).

This checks the maximum value that users can process and the maximum line value for which a requisition is automatically approved.

This checks the maximum value that users can process and the maximum requisition value for which a requisition is automatically approved. The total line values are summed up for each line on the requisition.

This performs the checks at the time of entry.

This performs the checks at the time of approval.

This enables you to process a shipment receipt for non-stocked lines on a purchase order. If a non-stocked line is encountered during consignment maintenance, then the system allows you to create a sundry consignment. The non-stocked code and quantity is retrieved automatically from details held against the non-stocked line. A Receive into stock option enables you to receipt the non-stocked line at the time of processing a shipment receipt.

This forces the operator to specify the exchange rate for a shipment at the time of adding the consignment advice. The entered exchange rate is applied to all purchase order lines with that currency which was added to the shipment for the current run of the program. If the exchange rate is not fixed on the purchase order, then the rate specified in the currencies table is used.

This uses the fixed exchange rate entered against the purchase order, regardless of whether you maintain individual or global exchange rates using the LCT Shipment Maintenance program. If you select this option together with the Auto prompt to establish exchange rate option, then the fixed rate against the purchase order is used regardless of whether the operator enters a rate when prompted.

This updates the due date for all order lines on all purchase orders for a shipment when you change the arrival date for an existing vessel.

Indicates how you want to process sales orders (i.e. set to complete, not complete or prompt operator) when using the Shipment Receipt program to receipt a shipment linked to a sales order (not a scheduled order) and the receipt quantity equals the back ordered quantity on the sales order.

Indicates how you want to process sales orders (i.e. set to complete, not complete, or prompt operator) when using the Shipment Receipt program to receipt a shipment linked to a sales order (not a scheduled order) and the receipt quantity is less than the back ordered quantity on the sales order.

Indicates how you want to process sales orders (i.e. increase the sales order to equal the receipt quantity, leave as is or prompt the operator) when using the Shipment Receipt program to receipt a shipment linked to a sales order (not a scheduled order) and the receipt quantity is more than the back ordered quantity on the sales order.

This enables you to reverse a receipt after the GRN has been matched. It does not, however, allow the reversal of a receipt for an item that is flagged as lot traceable or requiring inspection.

This indicates that freight charges for foreign suppliers must be entered in local currency by default when capturing purchase orders.

This indicates that freight charges for foreign suppliers must be entered in foreign currency by default when capturing purchase orders.

This indicates that miscellaneous charges for foreign suppliers must be entered in local currency by default when capturing purchase orders.

This indicates that miscellaneous charges for foreign suppliers must be entered in foreign currency by default when capturing purchase orders.

This includes freight and miscellaneous lines when exporting purchase orders in XML format (using either the Purchase Order Export program, or the Purchase Order Entry program). Previously exported freight or miscellaneous lines that are subsequently changed are not re-exported. However, freight and miscellaneous lines added to an order after it has been exported are included in the export.

This indicates the number of days before/after a purchase order's due date that it may still be supplied. 0 means no check is made for either early or late supply. Selecting the Receipt All option from the Purchase Order Receipts program, calculates the number of days between the receipt date and due date for each order line. If that number of days exceeds the number of days entered here, then those order lines are ignored.

This indicates the percentage according to which a purchase order receipt quantity can be more or less than the original purchase order quantity. This option comes into effect when either you attempt to receive into stock more than the original order quantity, or you attempt to specify that the order line is complete (i.e. an under supply has occurred). Only a warning message is displayed and the operator is not prevented from accepting the variance.

This is the percentage by which the expected costs and the actual AP invoice value can differ when apportioning the invoice value across cost elements.

This is the percentage by which the calculated landed cost and the current inventory cost of an item can differ when using the Calculate New Landed Cost program to update inventory costs.

This prints the document at the time of issuing the RMA (i.e. no values are printed). If you selected the cross-shipment option then you can also maintain and print the sales order.

This prints the RMA document only at the time of receipting the returned merchandise. You will be able to add/maintain jobs and credit notes as well as print the RMA document.

This prints the RMA document at the time of issuing and receipting the RMA (only applicable to printing RMA documents on-line).

This prompts you for the revision and release of ECC-controlled items at the time of issuing an RMA, or at the time of processing an RMA receipt. You are not prompted if you selected the Assume current rev/rel at time of adding order option at the Sales order creation setup option (Setup Options > Configuration > Manufacturing > Bill of Materials). The Rev/Rel function is, however, enabled, allowing you to change the revision/release.

This prompts you to save lines entered on a RMA in the RMA Issues and Receipts program. Otherwise the program saves lines automatically.

Indicate a default restocking percentage fee that you want to apply to returned merchandise for which the customer has requested a credit.

This prompts you to accept or change the restocking fee when you end an RMA (you are only prompted if the problem code on the RMA is blank, so don't enable the Problem code mandatory setup option (Setup Options > Configuration > Distribution > Return Merchandise Authorization).

This automatically applies the restocking fee when you end the RMA.

You can set RMA issues to default to a line type of Stocked or Non-stocked.

Indicate the default warehouse that must be used when receiving RMAs.

Indicate the default warehouse that must be used for repairing RMAs.

Indicate the default warehouse that must be used for restocking components.

This closes the RMA without taking any action.

This creates a credit note.

This creates a credit note for the returned item and a sales order for the new item shipped to the customer (not available for a cross-shipment).

This creates a non-stocked repair job and issues the returned material to the job.

This inspects merchandise received from a customer.

This lets you add notes to the RMA line when receiving returned merchandise from a customer.

Indicate the default invoice terms toimp040 use for a cross-shipment or exchange order.

Indicate the default non-stocked unit of measure to use.

Indicate the default non-stocked product class to use.

This inserts sales order additional text (defined against a stock item) automatically as comment lines when capturing orders. You assign this text to stock items using the Inventory Query program.

This inserts dangerous goods text (defined against a stock item) automatically as comment lines when capturing orders. You assign this text to stock items using the Inventory Query program. We recommend you select this option if you have enabled the Prompt for dangerous goods data sheets option. This will ensure that dangerous goods data sheets are always printed.

This displays a sales recap page (information about the invoices produced) once order processing is complete. An order recap is displayed regardless of whether an invoice sales recap is required.

Indicate whether costs associated with a stock item can be viewed within the Quick Sales Order Entry program accessed from the Sales Order Entry program or accessed from the main menu. This enables you to restrict the unauthorized viewing of costs and to prevent profit figures from being displayed in the quote totals. If you don't select this option, then you cannot specify a cost markup or profit margin percentage when processing Quick Quotes.

This enables the display of cost and profit information in the Sales Order Entry, Sales Order Query and Sales Invoice Query programs. This information is displayed for the entire order and for each line added using the Sales Order Entry program. You can prevent the unauthorized viewing of these costs and profits by defining the SO Show cost/profit operator activity field.

This lets you cancel order lines on a previously-invoiced order as well as status 2 orders without having to first mark them as complete. A status 2 order indicates a partially-delivered and invoiced shipment, with the remainder on back order. If you don't enable this option, then any previously-invoiced order (regardless of its status) cannot be cancelled, but has to be set to complete. Previously-invoiced order lines also cannot be cancelled. This applies to the Point of Sale Entry program.

This suppresses the warning message that is displayed when an invalid salesperson is held against the customer entered in the Sales Order Entry, Quick Sales Order Entry and Point of Sale Entry programs. A valid salesperson will still be required before you can add a line in Sales Order Entry; select and accept a stock code in Point of Sale Entry and convert a quote into an order in Quick Sales Order Entry.

Enable this to use the Ship to address against the header of an order still in progress, regardless of whether you change the ship address against the customer. Otherwise, the latest Ship to address against the customer is used for the order header when querying or printing an order that is still in progress. The Sales Order Query program always displays the current Ship to address in the Customer Information pane, while the order's Ship to address appears in the Order Header pane.

This clears the multiple ship address code when you manually change it on a form in the Sales Order Entry or SO Header Maintenance programs. The Ship address for the multiple ship address code is not reloaded after being manually changed.

This suppresses the warning message displayed in the Sales Order Entry program when saving a line for a stocked or non-stocked item that has a zero cost.

Indicate (at company level) which order type to use as the default when capturing orders. This field is accessed from the Invoice tab of the Order Header function. If a default order type has been assigned to the customer, then it overrides the default order type specified here.

This requires a valid entry to be made at the Order type field.

This indicates the default sequence in which you want to browse on sales orders. This can be by order, by customer, by customer purchase order or by alternate key (which you will have to specify).

This prevents operators from changing the AR branch and geographic area when processing orders (this does not, however, prevent operators from defining the default branch to use for orders).

This allows the change, but does not require the system to check that GL integration accounts are defined against the branch.

This allows the change but also requires the system to check that GL integration is defined for the branch.

This allows the Sales Order Entry program to change the order ship date when releasing an order from a status 2 (i.e. open back order). The order ship date will then be the release date entered at the start of order entry. This option does not apply to dispatch notes.

This forces operators to enter a reason code before they can successfully capture a credit note. Reason codes are maintained using the SO Reason Codes program. The reason code and description can be printed on your invoice and order acknowledgment documents.

Select this if you want the order date entered at the time of capturing a billing to become the invoice date for the invoice. Otherwise, the system date is used as the invoice date.

This uses the text entered at the Shipping instructions default message option as the default text for the Ship via field when capturing sales orders. The message can be printed on delivery notes and invoices.

This links your shipping messages to a two-character shipping instruction code. The message is displayed automatically when the code is entered at the Ship via field. If the code is not on file then you can enter a 28-character shipping message description.

This prompts you to enter serial numbers when processing order lines for serialized items. Otherwise you'll need to supply the serial numbers at the time of releasing the order for invoicing. If multiple bins is in use and the stock code is lot traceable, then you have to capture serial numbers regardless of your selection here. If the Request lots/bins/serials Reserving stock option is enabled, then you are only prompted for serials if multiple bins is not installed and the item is not traceable.

This enables you to change order quantities and ship quantities for optional component lines when capturing orders for a parent stock item.

This enables you to change the description of stocked items when capturing sales orders. Changes made apply only for the order being processed (i.e. the original inventory stock description held on file is unaffected). This does not apply to Quick Entry.

This indicates the default shipping message that is displayed at the Ship via field when capturing orders. The message entered here is only displayed if you selected Free form at the Shipping via usage option. This message can be overwritten when processing orders.

This doesn't apply to the Purchase Order Receipts, Job Receipts and Shipment Receipt programs (which use the Order linked to a receipt option).

This defaults to shipping the order quantity on the sales order.

This defaults to reserving the order quantity on the sales order.

This is used as the default code by the Sales Order Entry program when no commission code is defined for the stock code's price code.

This includes returnable items associated with a stocked item when processing a Supply Chain Transfer. When adding a line to a SCT (using either the Sales Order Entry or SO Supply Chain Transfer Creation programs, any attached service charge for a returnable item is added to the order.

This notifies you when a customer purchase order number is entered that has already been used for the same customer or company. The warning is displayed when capturing an order (at the time of adding the first line and when you end the order) and when maintaining an order.

This prevents an order from being captured if the customer purchase order number has already been used for the same customer or company.

This indicates how the Document Print program must treat the remaining order qty after you print an invoice for a partial shipment.

This sets the order status to complete (the order qty which could not be shipped is ignored).

This requires you to use the Order Maintenance function to move the qty from back order to ship manually.

This moves the backorder qty to shipped automatically (if there is enough stock on hand, or if you have allowed stock on hand to go negative).

This releases non-stocked items that are on back order automatically. The back order qty is moved to the Ship field without checking if there are any outstanding purchase orders, requisitions or jobs for the item.

This requires non-stocked items on back order to be released manually.

This releases non-stocked items on back order automatically, providing they are not attached to purchase orders, requisitions or jobs.

This notifies the operator when any out-of-stock items are ordered. If stock on hand is allowed to go negative, then the operator can ship the order quantity.

This ships the entire order quantity, regardless of stock availability when stock on hand is allowed to go negative. The operator is not notified. If stock on hand is not allowed to go negative, then the operator must indicate the quantity to be shipped and the quantity to be placed on back order.

This enables you to update the ship quantity of lines for orders that are in a status of 4 at the time of importing back order releases from an ASCII file. Back order releases are imported using the Import Back Order Releases program. In order to apply this option when importing back order releases, the entry at the Status field of the import file must be 8 and the entry at the Update ship quantity field must be Y.

This lets you indicate when the Insufficient Stock window must be displayed during sales order entry.

This displays it after the order qty is entered and you tab off the field.

This displays it as soon as the shortage qty is placed into backorder.

This enables the operator to manually select the option to display it.

This displays it according to the sales order preferences defined for the operator.

This lets you request the invoice date or number (provided automatic numbering is not defined) at the time of releasing a status 4 order or when a dispatch note is released for invoicing. Otherwise, the order number is automatically assigned as the invoice number for the first invoice produced for the order (if the Sales order moved to invoice option is enabled). For subsequent invoices, the next invoice number is assigned based on the invoice numbering method defined.

This notifies you when dangerous goods text is held against the stock item being processed for the customer during sales order entry. Upon saving the line, you are given the option to enter a standard comment or free format comment text. This allows you to notify customers of the delivery of dangerous goods items, where the data sheet for those items must accompany the goods, or to inform the customer of an updated specification or data sheet.

Indicates how often you want to notify a customer of dangerous goods text held against an item being ordered. 0 always notifies the customer of dangerous goods text (e.g. to inform customers at least every year about dangerous goods text, enter 365 here). When capturing an order, the program checks the date when last an invoice was raised for the customer/stock code combination, and notifies the operator of dangerous goods text only if the number of days entered here is exceeded.

This prevents an order from being released without authorization.

This prevents the release of an order for invoicing when the customer's credit terms and/or credit limit is exceeded. If the Apply check to current order only option is also enabled, then the order remains in its current status until the customer's outstanding balance is reduced or the credit limit increased to allow the order to be released for invoicing.

This ensures that a credit authority is requested when releasing orders that were placed in a status of suspense manually.

This applies customer credit limit checking when an invoice is about to be produced (i.e. orders in a status of 8) regardless of whether you selected No check at the Credit check for order to be released option. The check is based on the sum of the value of the invoice about to be produced; the customer's current balance; and the ship value of any orders for the customer which are in a status of ready to be invoiced. Negative orders (i.e. credit notes) are ignored from this credit check.

This ignores order lines that fail a customer credit limit check applied at the time the order is shipped (when selecting either the Apply release quantity or Release all lines functions of the Back Order Release program) and to place the order into a status of 2 (i.e. open backorder). Otherwise orders are placed into a status of suspense if any order lines fail the credit check applied at the time of shipping the order.

This resets a customer's credit status after using the Document Print program to process a credit note against an invoice.

Include orders in this status when the Order Purge program updates sales order prices where there have been changes to the price of a stocked item.

Include orders in this status when the Order Purge program updates sales order prices where there have been changes to the price of a stocked item.

Include orders in this status when the Order Purge program updates sales order prices where there have been changes to the price of a stocked item.

Include orders in this status when the Order Purge program updates sales order prices where there have been changes to the price of a stocked item.

Include orders in this status when the Order Purge program updates sales order prices where there have been changes to the price of a stocked item.

Include orders in this status when the Order Purge program updates sales order prices where there have been changes to the price of a stocked item.

Include orders in this status when the Order Purge program updates sales order prices where there have been changes to the price of a stocked item.

This enables you to apply an expired contract price (if it is the lowest price) to a contract customer during sales order entry. If the operator does not select to apply the expired contract price, then the program searches for the next lowest unexpired price as normal. This facility can be password-protected.

This uses the line ship date (instead of the document or order date) as the date for checking the contract prices of scheduled orders. For normal orders, the document date or order date is used to determine contract prices. Regardless of selection here, if you maintain an order line and change the ship date, the price is not automatically recalculated according to the contract dates.

This notifies you if there are no contracts on file for the current customer/stock code combination, whenever you attempt to retrieve contract prices (e.g. when entering an order or quotation).

This uses the stocking unit of measure as the default when entering orders for stocked lines.

This uses the alternate unit of measure as the default when entering orders for stocked lines.

This uses the other unit of measure as the default when entering orders for stocked lines.

This enables you to change the default unit of measure displayed at the Order quantity field when capturing an order.

This indicates that the relationship between the ordering and stocking units of measure is not absolute.

For example:

You sell fruit that you stock in kilograms but sell by the box. Theoretically, there should be 10 kilograms of fruit in a box. However, only at the time of actually selling (shipping) the fruit do you know exactly how many kilograms you have sold. An example of an absolute unit of measure is if you sell items by the dozen (i.e. there are always 12 items in a dozen).

This defines the quantity you want to use when calculating the total unit discount value for an order line.

This calculates the unit discount for an order line based on the quantity specified at the Order quantity field.

This calculates the unit discount for an order line based on the quantity specified at the Ship quantity field.

Indicate the default invoice format you want to use for counter sales invoices and point of sales documents. It overrides the default of 0 at the Format number field in the Sales Order Entry program.

Indicate the default format you want to use for counter sales deposits. You use the SO Document Formats program to define the fields you want to print on the deposit document.

Select this for the order quantity to default to 1 in sales order entry. You can override this quantity at the time of capturing the counter sale (or point of sale) during order entry.

This enables you to set the default payment code that you want to use when giving change. You can override this code during payment entry

This automatically selects and applies all qualifying tiered promotions for a sales order line. Otherwise, you will be prompted to manually select the qualifying promotions you want to apply from a list.

This automatically selects and applies all qualifying global promotions for a sales order line. Otherwise, you will be prompted to manually select the qualifying global promotions you want to apply from a list.

This enables the system to check if any trade promotions apply to existing sales orders that were created before the module was installed or activated (i.e. typically when you upgrade your system from a previous version of the software).

This enables you to apply global promotions from the menu of the Sales Order Entry program while adding or maintaining an order. It also enables you to apply/maintain line promotions against an entered order line (using your right mouse button) while adding or maintaining an order. If you don't enable this option and you don't apply global promotions to an order before ending the order, you won't be able to apply global promotions when maintaining the order.

This automatically reactivates an expired promotion when a sales order is cancelled, deleted or changed and the allocated amount falls below the budget amount. Otherwise the promotion will remain expired.

This applies the promotion to a sales order even if an order line exceeds the budget amount. The promotion is set to expired immediately after the sales order is added. Otherwise the promotion won't apply to the sales order that exceeds the budget amount. This option also applies when called from the Back Order Release program.

This enables you to change a miscellaneous line generated from an Off invoice or Free goods promotion. Only the Cost and the Tax values may be changed. If the cost is changed, then any subsequent recalculation of the promotion does not change the cost.

Enable this for the cost of a miscellaneous line generated from an Off invoice or Free goods promotion to default to zero. For example: When generating a promotion from a merchandise item that already carries a cost, you may want to process the promotion as a discount only, which does not carry a cost. This option enables you to generate such a promotion line with a zero cost. If you also select the Maintain miscellaneous line option, then the operator can change the cost from zero.

Indicate the default deduction code to use when adding accrual promotions using the Promotion Code program. Deduction codes are used in the processing of accrual promotion rebates and deductions.

Indicate the default resolution code to use when processing a normal approved deduction resolution using the Deduction Review program.

Indicate the default resolution code to use when writing off a deduction and when automatically writing off several deductions using the Deduction Review program.

Indicate the default resolution code to use when resolving deductions by offsetting them with accrued promotions using the Deduction Review program.

This enables you to assign dates to a structure indicating when the structure is active. Components that are Off (compared to the system date) are ignored from the Cost Implosion program which is designed to re-cost stock items from raw material level through to the finished part.

This enables you to monitor information that has changed for structures held on file. A journal is output whenever changes are made to structures within the Structures and Routings program. This information is listed using the Structure Amendment Journal program.

This enables you to enter text notes against a structure, allowing you to describe the link between a parent and its component parts. These narrations can be printed on a number of reports.

This enables you to assign coded text notes to a number of different operations. This text is linked to a narration code which is in turn assigned to your operations. If you do not select this option, then your text narrations must be unique for each operation.

This enables you to assign alternate routings for each set of operations for a parent part. The primary routing defaults to 0, while any selection in the ranges: 1-9; A-Z or a-z indicates an alternate routing.

This applies to jobs created through WIP and MRP. It allocates BOM components to jobs based on a range of job numbers. This is similar to the concept of structure on/off dates except that it is based on job numbers instead of date ranges. Note: You cannot run the Requirements Calculation program when you enable this option and your job numbering method is set to 'Manual'. If set to 'Scripted' then any suggested jobs will ignore any component inclusion/exclusion logic based on job numbering.

This records subcontract and material costs separately. Otherwise these costs are recorded as a single amount. Changing your selection will prompt you to run the Cost Implosion program to either split or merge the subcontract and material costs. If you don't run the program, BOM costs recorded against your stock items will be incorrect.

This enables you to take account of scrap at operation level (i.e. you capture scrap percentage and quantity against each operation configured within the Structures and Routings or WIP Add an Operation programs). When creating a job, the material allocations are inflated according to the scrap percentages and/or scrap quantities defined against the associated operations. The Requirements Calculation program caters for this at the time of calculating the demand of material allocations for jobs.

This uses the company calendar to calculate the start or job delivery date for operations. It only calculates operation movement time and does not calculate the actual elapsed time for operations. You typically select this if the work center against the current operation does not have the same working days as the next work center. Otherwise the work center calendar is used. If the work center calendar is not defined the system assumes that every day is a working day.

This displays a warning message in a number of programs if the Cost Implosion has not been run for all stock codes and warehouses. It indicates that the costs of the excluded items may not be up to date.

Indicate the maximum number of decimal places (up to 6) that you want to allow when making an entry at the structure's quantity per field.

Indicate the default time required for an operation to move between work centers. This is used only when a movement matrix for the work center is not defined.

Indicate a description of the time units applicable to your company. This description is displayed throughout the manufacturing modules whenever a field relates to a time unit.

This is the company default Work in Progress branch that will be used when capturing jobs, if you selected WIP branch level at the Apply integration level at setup option (Setup Options > General Ledger Integration > General Ledger Codes).

  • This default WIP branch is not used if you've configured a default against a bill of material routing or an operator.
  • The WIP Branch Update program lets you update existing, active jobs if no material or labor has been posted. The WIP control accounts are updated and saved against the jobs. If ledger accounts haven't been defined against a WIP branch, then the accounts defined at company level will be used by default.

This indicates the default code that will be used at company level, if one is not configured against one of the shift pattern levels.

This indicates the level at which you want to apply shift patterns. This can be assigned at Company, Site location, Work center, Production line, Warehouse or Machine level.

This assigns a sequence number to each structure added using the Structures and Routings program. It applies when you have multiple occurrences of the same parent/component combination and can also be used as a method of printing components in a sequence other than by stock code. If this option is enabled, then SYSPRO always assumes that there should be at least one milestone operation and that you would typically post labor to that operation.

Indicate whether you want to set the structure sequence key to be numeric or alphanumeric. Selecting numeric enables you to change the sequence of components assigned to the parent stock code.

Indicate the default sequence number (numeric or alphanumeric) that must be used when adding structures using the Structures and Routings program. If structure sequencing is not required, then the entry defined here is still assigned to each structure added, in case you enable this feature at a later stage.

An ECC bill of materials can only be selected for archiving when an engineering change order is moved to a status that accepts the changes made to the bill of material.

This let you archive BOM changes manually.

This archives a BOM automatically.

This prompts you to archive a BOM. If you don't archive the BOM when prompted, you can still archive it manually using the Structure and Routing Archive program.

This sets the revision/release for an ECC-controlled component to the current revision/release when using the Structure and Routing Archive program to archive bills of materials. When retrieving the archived BOM, the revision/release saved at the time of archiving is retained. If you don't enable this option, then when retrieving an archived BOM, the revision/release for the component is replaced by the revision/release which is current at the time of retrieval.

This indicates the first status in your workflow. All engineering change orders are assigned this status when they are created. You can prevent users from creating engineering change orders by denying them the authority to access the initial engineering change order status.

This indicates the engineering user to use when no responsible user has been assigned to an ECC-controlled stock item.

This enables you to make changes to the default non-stocked profit margin (or markup) when maintaining a quotation.

This enables you to make changes to the default labor margin (or markup) when maintaining an estimate.

This enables you to make changes to the default material margin (or markup) when maintaining an estimate.

These are the default descriptions you want to display for offers assigned to a quotation. You can change these descriptions at the time of maintaining a quotation.

This is the default description you want to display for offer 1 assigned to a quotation. You can change this description at the time of maintaining a quotation.

This is the default description you want to display for offer 2 assigned to a quotation. You can change this description at the time of maintaining a quotation.

This is the default description you want to display for offer 3 assigned to a quotation. You can change this description at the time of maintaining a quotation.

This is the default description you want to display for offer 4 assigned to a quotation. You can change this description at the time of maintaining a quotation.

This is the default description you want to display for offer 5 assigned to a quotation. You can change this description at the time of maintaining a quotation.

This is the default description for the default offer assigned to a quotation. You can change this description at the time of maintaining a quotation.

This uses route 0 in the Quotation Cost Implosion, Lead Time Calculation and Quotation Job Loading programs when no components and/or operations exist on the route you selected to process in these programs. Otherwise, no operations or components are included in the cost implosion or in the created job.

This allows changes to the default query date when maintaining a quotation.

This allows changes to the default quotation expiry date when maintaining a quotation and is enabled by default if you select the Force entry of expiry date option. You can't select this if the expiry date is based on the print date.

This makes the entry of an expiry date compulsory.

This calculates the expiry date from the query date.

This calculates the expiry date from the tender date.

This calculates the expiry date from the print date stored against the quote header (the print date is updated when you print or preview the quote).

This enables you to enter zeros (i.e. no expiry date) at the Expiry date field within the Quotations program.

Enter the number of days that must be added to the base date to determine the expiry date of the quotation.

This is the default period size applicable to reports and queries. You can override this in any program that requires a period to be entered. Options include: Single day, Multiple days, Weeks and Months.

This is the number of days that you want to be viewed as a period.

This is the first day of the week that will be used as the default for the period (0-Sunday, 1-Monday, 2-Tuesday, 3-Wednesday, 4-Thursday, 5-Friday, 6-Saturday).

This enables you to review jobs that have not yet been started within the Job Review program.

This displays the Stock Codes with Requirements listview when browsing on items in the Supply Chain Review, Job Review, Blanket Purchase Order Review, Purchase Order Review, and Requisition Review programs. Otherwise, the Browse on Stock Codes listview is displayed instead.

This is the number of days before stock can be used in the Requirements Calculation. This is added to the dock-to-stock days for each item and is used when calculating the delivery date of a job linked to a sales order, purchase order or supply chain transfer.

This is the maximum number of decimals (0 to 6) allowed to be held for the quantity per field in the resource structure file.

This is the default number of days in each time bucket for resource planning. The Resource Planning Query program allows you to override this time period at run time.

This creates a journal of all additions, deletions or changes made to forecasts.

This creates a journal of all additions, deletions, or changes made to build schedules.

This must be included if you are catering for expired lots (this decreases stock on hand). If sales orders are not included, then the available quantity is subtracted from safety stock to establish the demand quantity. If included together with sales orders, then the stock on hand is subtracted from safety stock to establish the demand quantity. If neither stock on hand nor sales orders are included, then safety stock is the demand quantity.

This creates demand in the prior period, which could result in the creation of a purchase order or a job (the demand created is reflected in the pegging file). Safety stock is included in the calculation used to establish any oversupply/shortage: (qty on hand + supply - demand - safety stock).

You can exclude/include purchase orders or purchase order lines from the MRP calculation when adding or maintaining purchase orders using the Purchase Order Entry program. Requisition lines can be excluded from the calculation using the Requisition Entry Maintenance program.

Select this to include confirmed jobs in the calculation of requirements.

Select this to include unconfirmed jobs in the calculation of requirements.

A job is placed on hold often because of a problem with the finished item, or the customer has canceled the order. So, you might want to exclude the job from the calculation to ensure that any materials attached are not incorrectly ordered. The Requirements Calculation, Forward Finite Scheduling and MRP Low Level Code Validation programs will check whether to exclude/include a job on hold. Sub jobs attached to a job on hold are also excluded, even if the sub jobs themselves are not on hold.

Forecasts are ignored if the Build schedule option is enabled.

Orders for MPS items are ignored if build schedules are included.

If orders are not included, then the available qty is subtracted from safety stock to establish the demand qty.

If orders are included (as well as stock on hand) then stock on hand is subtracted from safety stock to establish the demand qty. If neither is included, then safety stock is the demand qty.

If the Reduce quantity on hand by allocated option is enabled, then the on hand qty is reduced by the qty allocated to orders.

A default offer must be selected against the quotation for it to be included in MRP. Otherwise MRP does not generate demand for the items on the quotation.

This includes the build schedule in the calculation of requirements. This ignores forecasts and orders for MPS items as MPS only supports a single level of dependent demand (i.e. demand in the form of job allocations). The only demand seen for an MPS item is the build schedule.

This includes forward orders in the calculation of requirements. The Sales orders option must be enabled.

This includes orders in suspense in the calculation of requirements. The Sales orders option must be enabled.

This includes supply chain transfer orders in the calculation of requirements.

The Sales orders and Goods in transit options must be enabled and the Consolidate selected warehouses option must not be enabled.

The Inventory option: Full goods in transit transfers facility must be enabled (this creates suggested SCT's for items which are transfer-supplied).

This includes goods in transit records in the calculation of requirements. If including supply chain transfer orders, ensure that the Inventory option: Full goods in transit transfers facility is selected.

This applies forecasts only and sales orders only to determine the gross requirement of non-MPS items. If you only select this option then the gross requirement for all other non-MPS items is determined by applying rule A (sum of forecasts and sales orders). If you don't select this option then gross requirement rule A is applied to all non-MPS items assigned rule I and S.

This applies the highest of forecasts and sales orders and cumulative highest of forecasts and sales orders to determine the gross requirement of non-MPS items. If you only select this option, then the gross requirement for all other non-MPS items is determined by applying rule A (sum of forecasts and sales orders). If you don't select this option, then gross requirement rule A is applied to all non-MPS items assigned rule H and C.

This determines the period to which sales orders and forecasts are allotted if you selected to apply gross requirement rules H and C.

This uses only sales orders within the demand time fence, regardless of the gross requirement rule assigned to the item (i.e. forecasts within the demand time fence are excluded from the calculation of requirements).

When a quantity on hand for an item drops below its minimum level, MRP tries to replenish the order immediately, which may result in the unnecessary expediting of orders. This option enables you to indicate a time fence during which MRP will not raise demand for safety stock. MRP applies the rule you select and inserts safety stock demand at the calculation run date plus the time fence selected. Options include: None, Demand time fence, Manufacturing time fence and Planning time fence.

This overrides the buying rules held against each stock code when running the Requirements Calculation.

This uses the buying rule assigned to the stock item when running the Requirements Calculation.

This override only the buying rules held against MPS items when running the Requirements Calculation.

If you elected to schedule jobs and purchase orders according to demand, then this schedules a specific supply (existing or suggested job, sub job, purchase order or requisition) to the specific demand to which it is linked (e.g. supply for a job linked to a sales order will be scheduled according to the sales order). Otherwise the Requirements Calculation program links the supply of an item to the first demand for the item, according to the demand dates.

This includes all stock codes and warehouses in the requirements file, regardless of whether there is demand/supply. This enables you to produce reports listing all stock code/warehouse combinations that do not have demand or supply. Selecting this option may considerably increase the size of both the requirements file and the reports generated from this file.

This option cannot be deselected if you have enabled the Consolidate selected warehouses option.

If you are not including sales orders in the Requirements Calculation program, then this reduces the quantity on hand by the quantity allocated to sales orders in the warehouse file.

This decreases stock on hand for expired lots when generating material requirements in the Requirements Calculation program. You will also need to enable the Stock on hand option at the Include in requirements calculation field, because the suggestions made by the system vary depending on your selections. If this field is disabled, then stock on hand for expired lots is included as stock on hand in the Requirements Calculation program.

This indicates that additional requisition users can be included in the Requirements Calculation when calculating supply for requisitions according to requisition users. By default, only requisitions created by the requisition users QOT and MRP are recognized as supplies by the Requirements Calculation program.

This prevents the Requirements Calculation program from raising suggested supplies (i.e. jobs, requisitions or SCTs) for non-current revision/releases of ECC-controlled items. In addition, archived BOM structures are ignored when performing the low level calculation, except for Phantom parts (these are always included in the low level code calculation, even when archived).

This allows goods in transit to be re-scheduled if you are scheduling supply according to demand and there is existing goods in transit. Otherwise, existing goods in transit can be moved out to fill a future requirement and the demand created by this action can be filled either by suggesting a new supply chain transfer and/or moving existing supply chain transfers in.

This uses the date on which the MRP calculation is run (instead of the job start date) when checking structure off dates. If the suggested job start date is prior to the calculation date, then instead of checking that against the structure on/off dates, the calculation date is checked. This means that only structures that are current at the time of the calculation are used.

Select this to take account of quotes that are likely to become firm orders, by including them in the calculation of material requirements. In this way you could start purchasing raw materials with long lead times in anticipation of the order.

This assigns a higher priority to the start date of a job than the job priority held against the job, when using forward finite scheduling.

This assigns a higher priority to the job priority held against a job than the start date of a job, when using forward finite scheduling.

This assigns a higher priority to suggested jobs than quotations, when using forward finite scheduling.

This assigns a higher priority to quotations than suggested jobs, when using forward finite scheduling.

This indicates the maximum queue time allowed when calculating forward finite capacity, setting a limit on the insertion of operations into the capacity profile for each work center.

This indicates the warehouses you want to include in the Requirements Calculation. Options include All, Range, List and By warehouse. The By warehouse option includes warehouses according to the Include warehouse in requirements planning calculation option defined against the warehouse itself.

This consolidates the information of all the selected warehouses using warehouse --. You must specify a Component warehouse to use against each warehouse (for by the consolidation routine in the Requirements Calculation program). If left blank, then MRP cannot raise suggested supply. Don't select this if you want the Requirements Calculation program to include SCT orders and/or blanket purchase orders, or if you are using bought out details (e.g. supplier, lead time and dock to stock) at warehouse level.

If this option is enabled, then you won't be able to deselect the Include all stock codes in requirements option.

By default, only requisitions created by the requisition users QOT and MRP are recognized as supplies by the Requirements Calculation program.

This includes all requisition users in the MRP calculation.

This includes a range of requisition users in the MRP calculation.

This includes requisitions from requisition users only if the Include user in MRP calculation option is enabled against the user code.

Requisitions for requisition users QOT and MRP are also included/excluded according to the selection you make here.

This includes requisitions originated by the requisition user.

This includes requisitions currently held by the requisition user, regardless of the user who created the requisition. This includes requisitions created by the current holder and which have not yet been routed.

This depletes forecasts according to your selections.

This indicates the time frame into the future according to which you want to limit forecast depletion based on the ship date passed. Options include: Days, Demand time fence, Planning time fence, Planning horizon and Use forecast calendar.

This indicates the number of days to which you want to limit forecast depletion if you chose Days at the Forecast depletion period type option.

These options enable you to control forecast depletion into the past.

This depletes past due forecasts from the earliest active forecast with a quantity available.

This depletes past due forecasts from the ship date on the order.

This depletes past due forecasts up to a number of days prior to the ship date on the order. The depletion start date is moved back by the number of days specified.

If you chose Number of days prior to ship date at the Allow past due forecasts to be depleted option, then this is the number of days prior to the ship date used to calculate the depletion start date. The depletion start date for the forecast is calculated by subtracting the number of days defined here from the ship date on the order (e.g. if you enter 15, then depletion starts 15 days earlier than the ship date for a sale or credit note and any forecast located within 15 days is depleted).

This depletes forecasts relating to the customer against the sales order followed by forecasts where the customer is spaces. Forecasts with a different customer are excluded from depletion.

This only applies to stocked items. It works together with the Use forecast calendar choice against the Forecast depletion period type option and enables forecast depletion to take place beyond the current forecast calendar period end date. Otherwise depletion only takes place up to the end of the depletion date calculated (i.e. the current forecast calendar period end date is the end point of depletion).

This indicates the items for which you do not want to deplete forecasts. MPS items are always included in forecast depletion. You can only exclude MPS items by setting them to a gross requirements rule of A or I and then select to exclude them from depletion using the options below.

This excludes all MPS items with a gross requirements rule of A - Sum of forecasts & sales orders from forecast depletion. This only applies to stocked items. It does not apply to non-MPS items.

This excludes all MPS items with a gross requirements rule of I - Forecasts only from forecast depletion. This option only applies to stocked items. It does not apply to non-MPS items.

This excludes non-Master Production Schedule items from forecast depletion. This only applies to stocked items.

This excludes non-stocked items from forecast depletion. Depletion for non-stocked items only occurs when the item is invoiced, after the Deplete forecasts option is enabled and you are not excluding non-stocked items.

This enables you to change the setup time, startup time, startup quantity, unit run time, teardown time and wait time during maintenance of internal operations.

This allows an operation to end earlier than the prior one when calculating the start or delivery date of a job. Otherwise an operation's end date is never calculated as being before the completion date of a prior one. Also, when working backwards and negative move time is applied to an operation that causes it to start later than the next one, the system takes the current operation and works backwards until its start date is earlier than the next one's start date.

This is the warehouse that will be used for floor stock items (floor stock and bulk issue). Floor stock items don't require requisitions and are issued automatically to a job upon confirmation. They are included in the costing process and are allowed to go negative, regardless of your warehouse settings. Bulk issue items are issued automatically as material allocations to a job without affecting the on hand quantity of the item. The item is included as a component in the costing process.

This places a bin on hold that is affected by the receipt of a job into stock, preventing issues from the bin until the hold is released.

This lets the operator decide whether a bin affected by the receipt of a job into stock must be placed on hold.

This allows you to view the job number when maintaining an order linked to a job after the job is set to complete. Otherwise, the details of a receipted job set to complete are not displayed in the Sales Order Entry program and you will need to use the Sales Order Query program to view these details (by selecting the Show jobs that are complete or jobs linked to a completed detail line preference. This applies to jobs for stocked and non-stocked items set to complete after this option is enabled.

This allows you to review all demand for stock when receipting a job (e.g. reserve, allocate or issue quantities to jobs and orders as required).

This indicates that the maximum variance value that can be automatically cleared is a percentage of the total expected cost of the quantity to manufacture against the job.

This indicates that the maximum variance value that can be automatically cleared is the outstanding WIP value. This applies only if the Job Receipts program is used to process the receipt of a stocked item and the job is set to complete when the receipt is processed.

This is the maximum allowable variance value (up to 999999999999.99) that can automatically be cleared.

This is the maximum allowable variance percentage (up to 99.99) that can automatically be cleared.

This applies the automatically cleared variance rules regardless of the Inventory costing method selected. Otherwise the automatically cleared variance rules apply only to warehouses using standard costing.

This always charges for labor costs incurred when processing a part billing.

This lets the operator to decide whether to charge for labor costs incurred at the time of processing a part billing.

This is the default labor service charge code to use when processing a part billing and is used if a labor service charge code has not been defined against the work center.

This prints an on-line document for each kit issue processed for a job.

This enables you to perform kit issues, regardless of any shortages encountered (select this if you want to be able to substitute stock items when issuing kits in the Job Issues program. Otherwise, no kits are issued where shortages are encountered, forcing you to review material issues.

This enables you to substitute stock items when issuing kits in the Job Issues program. You must enable the Allow kits with shortages to be issued option.

For items where the manufacturing quantity basis is defined as pan size, this option rounds up to the pan size any materials issued as kits in the Job Issues program.

This ensures that the system prompts you for an operation number when you try to issue materials not defined as allocations for the job. If no operations exist for the job, then any issue of materials is added automatically as required for operation 1 (i.e. the start date of the job).

This enables the Sequence checking on operations required option by default when capturing job details.

This enables the Job confirmed option by default when capturing job details. You can override this in the RMA Issues and Receipts program.

This enables the Include overtime % in date calculation option by default when adding or maintaining jobs with a date calculation method of Finite scheduled delivery date.

This is the maximum queue time allowed when calculating the forward finite capacity. It sets a finite limit on the insertion of operations into the capacity profile for each work center.

This allows you to enter the quantity to manufacture against the notional part when creating a job. The quantities of the co-products to manufacture are then calculated according to the quantity entered for the notional part.

This allows you to enter the quantity to manufacture against each co-product attached to the notional part when creating a job for a notional part. The notional part's quantity to make is then calculated according to the quantities entered for each co-product.

This creates amendment journals when live jobs are created, confirmed, maintained, deleted, or placed on hold as well as when job labor and material allocations are added, changed or deleted. No amendment journals are created for MRP snapshot jobs. The journals can be viewed in the Browse on Job Amendment Journals program and listed on the WIP Job Amendment Journals Report.

This validates the machine code during processing in the Labor Posting program.

This validates the employee number during processing in the Labor Posting program.

This posts non-productive time against jobs when you select to update the job in the Labor Posting program. Otherwise only the productive time is updated against the job. If you don't update the job in the Labor Posting program, then posting is not made to a specific job. Only the BOM Work Center table is updated and the Labor journal is generated.

Indicate the last period end date for the Work in Progress labor analysis system. This field is updated when you run the Labor period end function of the WIP Period End program.

Indicate the last month end date for the Work in Progress labor analysis system. This field is updated when you run the Labor period end function of the WIP Period End program.

Indicate the last year end date for the Work in Progress labor analysis system. This field is updated when you run the Labor period end function of the WIP Period End program.

Choose whether you want to reserve lots for parent parts and co-products when confirming a job.

This captures lots only when the job is receipted into stock.

This loads the WIP Reserve Lots & Serials Maintenance program for each traceable parent part and co-product when the job is confirmed.

This prompts the operator once only to reserve lots for parent parts and co-products upon job confirmation.

This lets you choose whether you want to reserve serials for parent parts and co-products when confirming a job.

This captures serial numbers only when the job is receipted into stock.

This reserves serial numbers for serialized parent parts and co-products. The WIP Reserve Lots & Serials Maintenance program is loaded for each serialized parent part and co-product when the job is confirmed.

This prompts the operator once only to reserve serials for parent parts and co-products upon job confirmation.

Choose whether you want to reserve lots for material allocations when confirming a job.

This captures lots only when the materials are issued to the job.

This loads the WIP Reserve Lots & Serials Maintenance program for each lot traceable component when the job is confirmed.

This prompts the operator once only to reserve lots for material allocations upon job confirmation.

This lets you choose whether you want to reserve serials for material allocations when confirming a job.

This captures serial numbers only when the materials are issued to the job.

This loads the WIP Reserve Lots & Serials Maintenance program for each serialized component when the job is confirmed.

This prompts the operator once only to reserve serials for material allocations upon job confirmation.

This allows a job to be receipted into stock using different lots/serials to the ones that were reserved for the parent at the time the job was confirmed.

This allows components to be issued to a job using different lots/serials to the ones that were reserved for the material allocations at the time the job was confirmed.

This enables you to indicate which anticipated cost to use when calculating the threshold cost for a head/section. The posting threshold percentage and anticipated values are defined against each head/section using the P&C Maintenance of Job Hierarchies program. When adding or issuing allocations to a head/section, a warning is displayed if the threshold is exceeded.

This automatically expands the entire treeview of hierarchies before you can start posting or maintaining entries using a number of programs. Otherwise, the hierarchy maintenance and posting programs only display a single level of the treeview at a time (i.e. each level of the treeview is only loaded when you select the plus sign in the treeview). This means that large hierarchies are displayed more quickly.

This defaults to displaying hierarchies in a listview rather than a tree view in a number of programs.

This enables you to generate a delivery note online when using the Part Billings program to part-bill a non-stocked hierarchical job linked to an hierarchical sales order. The delivery note is created for the ship quantity when you release a quantity from back order in part billings (i.e. the current ship quantity on the sales order). This only applies to hierarchical sales orders linked to hierarchical jobs.

This is the number by which each operation must be incremented when adding operations in the Work in Progress module (this does not apply when adding operations in the Bill of Materials module). It determines the operation numbers assigned to operations.

This is the operation number you want to assign to the first operation added to a job.

This lets you define whether existing operations can be renumbered when the WIP Browse on Labor Allocations program is used to add operations to a job. You can prevent this if the operation has started, or a job has been added, confirmed or started. An operation is seen as started if the actual queue date or start date is set to non-zero. A job is seen as started if a value for materials exists or labor hours have been posted to the job. A job is added once created, regardless of whether it is confirmed.

Define your own descriptions for the selections of colors at the Follow up flag field of the Contact Activity Posting program (e.g. Red represents Urgent). The default selections are replaced by the selections you enter here.

This applies to activities against which attendees are defined. When you post an activity with attendees, the system automatically creates activities for the contacts listed as attendees. These activities include any attachments included by the originator of the activity. Any attendee who has security access to maintain activities can change the activity for all other attendees.

This limits the location defined against any activity to the locations currently defined in the drop down list of locations.

This limits the Regarding text defined against any activity to the list of regarding texts currently defined.

This limits the Result defined against any activity to the list of results currently defined.

This limits the 'User field 1' defined against an activity to the list of user defined texts defined for these fields.

This limits the User field 2 defined against an activity to the list of user defined texts defined for these fields.

This limits the User field 3 defined against an activity to the list of user defined texts defined for these fields.

This configures an alternate location for storing activity attachments from the SYSPRO Contact Management system. By default, activity attachments are stored in a sub folder of the SYSPRO Work folder.

This uses the standard folder as the location for attachments (\work\crm.?\activity\attach where ? refers to the company id).

This defines a specific folder as the location for attachments.

This is the folder you want to use for attachments. It can exist anywhere on your server, or on any drive that has been mapped to the server. The path always ends in slash and must not contain quotes.

This indicates the description for the three user defined fields for Activities.

They default to User field 1, User field 2 and User field 3, but can be changed here.

Optionally enter your own description for the Contact property field.

Optionally enter your own description for the Contact classification field.

Optionally enter your own description for the Contact type field.

Optionally enter your own description for the Contact category field.

This enables you to define your own descriptions for the selections of colors at the Contact property field that is used to classify a Contact (e.g. you could specify that Blue represents your employees). The default selections for the Contact property field in the Classification pane of the Contacts program are replaced by the selections you enter here.

This indicates the fields for which the Contact Copy Details to Multi Contacts program must be displayed whenever information against these fields is changed for a contact.

The entries made here are used as the defaults when you use the Contacts program to create a new contact.

This is the default multimedia object category in which you will save the image you want to display against each contact.

This is the default Internet website address you want to use for viewing weather information for your contacts. This defaults to http://www.weather.com, but can be changed.

This is the default Internet website address you want to use for viewing map information for your contacts. This defaults to http://maps.google.com/maps, but can be changed.

This includes the appointments and meetings added in the Contact Management System onto your SYSPRO calendar. You can indicate the types of meetings and appointments to include in your calendar which enables you to optimally configure the number of items displayed in your calendar.

These options enable you to indicate the criteria for purging contacts and activities when using the Contact Management Purge program. If you don't select to purge either contacts or activities or both, then you cannot access the Contact Management Purge program.

This deletes contacts when running a purge. Don't enable this if you want to retain contact details indefinitely.

This indicates the number of years for which you want to retain details of contacts against whom no activity was recorded. A contact is deleted when you purge contacts and no activities were recorded against the contact for the number of years specified here or the contact was added before the number of years specified here.

This deletes cleared activities and their associated attachments. Don't enable this if you want to retain details of Activities indefinitely.

This indicates the number of years for which you want to retain activities. An activity is deleted if it has been cleared (i.e. it is no longer active) and it is older than the number of years specified here.

This enables you to define the Delete contacts where no activity for and Delete activities older than options at the time of running the Contact Management Purge program.