Setup Options
SYSPRO's Setup Options program provides a central area from which implementers are able to quickly configure SYSPRO modules as well as make information easily available to support staff - significantly speeding up the process to resolve issues.
Things you can do in this program include:
- Configure setup options.
- Search for and maintain setup options across all modules.
- View and compare company options.
- Import and export configurations.
- Monitor changes to setup options.
Starting
- Ensure that the SYSPRO 8 e.net Communications Load Balancer service is installed and properly configured within the System Setup program.
- Because SYSPRO's setup options affect the way programs work and/or interact with other programs and data, these options should ideally be configured by the system administrator before operators start using the functionality.
You can prevent operators from seeing or accessing module setup options by configuring Setup Option activities within the Operator Maintenance program (Security > Activities > Configure activities > Edit).
For example:
Denying an operator access to the Accounts Payable module hides all form information relating to Accounts Payable (e.g. Configuration, Preferences, etc.). It also hides disallowed form options from being displayed in the search bar.
You can also prevent operators from accessing functions available from the toolbar by configuring Setup Option activities that restrict access to functions within the program (e.g. Compare, Import, Export, etc.). Functions to which an operator has been denied access are grayed out.
If you are using role-based security then you can prevent operator roles from seeing or accessing module setup options by configuring Setup Option activities within the Role Management program (SYSPRO Ribbon bar > Setup).
- For the role you want to secure, ensure that the Activities and fields role configuration option is set to Configured by role.
- Click on the Configure icon to load the Role Activities and Fields Maintenance program.
- Access the activities you want to secure (e.g. in this case, it would be the Module: Setup Options section).
You can also prevent roles from accessing functions available from the toolbar by configuring Setup Option activities that restrict access to functions within the program (e.g. Compare, Import, Export, etc.). Functions to which a role has been denied access are grayed out.
- By default, access to all the module setup options and functions is allowed.
- Although you can configure a Setup Option activity to control access to View Amendment Journals from within this program, this security does not extend to running the Setup Amendment Journal program when selected from the SYSPRO ribbon bar.
- You can't selectively restrict access to setup options that aren't grouped by module (e.g. Tax Options, Keys, Company Options). Denying or allowing access to them applies to all the forms and options in that group.
- Module activity restrictions that you configure will also apply when selecting to View All Options (i.e. you won't be able to view options to which you have been denied access) as well as the Help Caption text.
Referencing
Field | Description | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Company |
This defaults to the company you are currently logged into. Only the companies to which you have access are displayed here. You configure this using the Operator Maintenance program. |
||||||||||||||||||||||||||||
Functions |
|
||||||||||||||||||||||||||||
Define |
|
||||||||||||||||||||||||||||
Information |
This provides you with a quick glance of information relating to your financial modules across a specific company. Information includes:
The details displayed are for informational purposes only (i.e. you won't be able to make changes).
|
||||||||||||||||||||||||||||
Quick search |
This lets you search for specific setup options (useful if you don't know the form on which the option is located). The search dynamically matches entries as you type and when you click on an entry it navigates straight to the option on the relevant form. |
||||||||||||||||||||||||||||
Toggle caption help for the program. If switching on caption help for the first time, you will need to navigate to a new form before the help text is visible. |
This indicates your pre-printed stationery is a combined remittance and check.
This prints checks and remittances on separate stationery or printers (e.g. you can print your checks on pre-printed stationery and your remittances on pre-printed stationery or using MS Word or SRS printing).
This indicates that you only want to print remittances (e.g. you typically pay your suppliers electronically).
This indicates that you want to configure your check print requirements against the bank.
This indicates whether the difference between the supplier's invoice value and the total merchandise value of the GRN line(s) you selected to match is based on a percentage or a value.
This occurs during processing in the AP Invoice Posting program.
This is the maximum permitted GRN variance percentage or value.
Enter the cut-off % for variances arising when matching the value of supplier invoices to the value of selected GRN line(s).
If Inventory is integrated to GL and the difference is less than this % then the variance is posted to the GRN suspense account. Otherwise it is posted to the Purchase price variance account.
If Inventory is not integrated to GL and the difference is more than this % then the variance is posted to the Default merchandise account. Otherwise it must be allocated manually.
This applies the exchange rate against the invoice as the default rate when the invoice is released for payment, or when a check is voided, or when a manual check payment is made.
This applies the exchange rate from the Browse on Currencies table to the invoice as the default rate.
This revalues all invoices released for payment and generates a revaluation value for any exchange rate variance created.
This option is only enabled when you select Default to currency table rate.
The exchange variance is posted to the Realized variance account account defined in the AP Currency Variance GL Interface program. If not defined, then the variance is posted to the Exchange variance account defined against the bank.
This posts checks to the Cash Book module as withdrawal entries at the time of printing the Payment Cycle Maintenance report.
This accumulates all invoices, debit notes and credit notes of a specific age (based on the ageing method) into a single invoice for each balance forward customer when you run the Month end function of the AR Period End program.
Once consolidated, all original invoices and associated payments, adjustments, debit notes, credit notes, multimedia and invoice notes for the age are deleted.
You cannot select this option if your invoice ageing method is set to By invoice due date.
Reports that print detailed information on invoices and the transactions processed against them will only report on the consolidated invoices once the month end has been processed.
Invoices for foreign currency customers are not consolidated, because each invoice can have its own fixed exchange rate. Future invoices (i.e. ones that have an invoice date in the future) are not consolidated.
This indicates the default ageing method to use when producing AR statements.
This ages invoices according to the last seven period end dates. An invoice is defined as current if the invoice date is after the last period end date.
This ages invoices according to the last seven period end dates. An invoice is defined as current if the invoice date is after the second last period end date.
This ages invoices according to the difference between the invoice date and the system run date.
This ages invoices according to the due date of the invoice. This is calculated as the invoice date plus the days till due as defined within the AR Invoice Terms program. The invoice remains current for as long as the due date remains greater than the ageing date.
This indicates the terms code to use for finance charge invoices created by the AR Finance Charge Calculation program.
Although your entry here is not validated (i.e. the AR Invoice Terms program is not checked to ensure that the terms code entered here exists) if you want to compound finance charges then you need to enter a valid terms code here. You should also enter a valid terms code here for credit control purposes.
This indicates whether debit or credit notes must be generated when settlement discount is processed as part of a customer's payment.
Local tax regulations may require generating a credit note when settlement discount is processed against a customer payment and a debit note when a payment that includes settlement discount is reversed.
The As required option generates discount credit and debit notes if this is selected in the AR Payments and Adjustments program.
This option (together with the payment type defined against the deposit slip details) determines how AR payments are posted to Cash Book. The Bank deposit slip required option must be enabled to integrate AR payments to Cash Book.
This overrides the Cash Book integration level when capturing AR payments and is enabled if integration is set to Posted by cash journal.
Individual transactions are created for each payment with a type of Check.
A single transaction per journal is created for the total of all payments with a type of Cash.
A single transaction is created per journal for the total of all local currency payments with a type of Other and individual transactions are created for each foreign currency payment.
This consolidates the payment types (cash, check, other, post dated checks) into one amount before integrating to Cash Book.
This posts book value depreciation to GL according to the settings defined for asset integration.
This posts book value depreciation values to the GL code defined against each asset. You can only access this option after completing an Asset month end and before running the Asset Depreciation Calculation for the current month. This is to prevent you changing the integration method between routines.
This indicates whether you want the system to calculate (historical) book and tax depreciation when adding a new asset purchased before your current financial month and whether it must be added historically or in the current period.
The system will not calculate the (historical) book and tax depreciation automatically up to the end of the last financial month (i.e. no catch-up depreciation is calculated). You will need to enter the historical depreciation information for each prior period and year manually using the Asset Acquisition program
The system will not calculate the (historical) book and tax depreciation automatically up to the end of the last financial month. You will need to enter the historical depreciation information for the prior periods manually using the Asset Acquisition program.
The system calculates the (historical) book and tax depreciation automatically up to the end of the last financial month.
A brought forward balance is created, which could mean that historical reports may not balance to current year reports. This is typically only useful in take-on situations.
The system attempts to spread the book value depreciation across historical periods depending on the period end dates defined for the Assets Register module and the Start depreciation date defined against each asset.
When you add an asset into a prior year, Addition and Catch-up depreciation (accumulated) entries are created plus the current year entries.
Regardless of your selection here, tax (wear and tear) depreciation is always calculated automatically up to the end of the last financial month.
The system calculates the (historical) book and tax depreciation automatically up to the end of the last financial month and places the total value of the historical depreciation into the current period. No 'brought forward' balance is created.
Changing the basis for depreciation can result in loss of historical data and entries.
Indicate the basis of depreciation for the book value of your assets.
Indicate the basis of depreciation for the tax value of your assets.
This calculates the current period depreciation at period end.
This recalculates the full current year's depreciation at each period end.
This recalculates depreciation for the full life of the asset.
Indicate the basis for depreciation for each of the Alternate valuations of your assets.
This uses the date conventions defined here against the various asset valuations, for all assets in that asset valuation.
This uses the date conventions defined against each individual depreciation code.
Indicate the date convention you require for book value depreciation.
Indicate the date convention you require for tax value depreciation.
Indicate the basis for depreciation for each of the Alternate valuations of your assets.
This lets you indicate how you want to match deposit records which are imported using the Automatic Bank Reconciliation program to deposit transactions in the cash book transaction file.
This reconciles deposits automatically if the entry at the value field in the import file matches the entry in the transaction file.
This reconciles deposits automatically if the entries at the value, date and reference fields in the import file match the entries in the transaction file.
This reconciles deposits automatically if the entries at the value and date fields of the import file match the entries in the transaction file.
This defaults to viewing the ledger file in ledger code sequence.
This defaults to viewing the ledger file in ledger description sequence.
This lets you query General Ledger budget balances by section using the GL Structure Query program. You can only select this if you enabled the Section analysis required option.
This leaves budget information intact after running a year end.
This sets the current years' budgets to zero at year end (i.e. you will have to enter budgets manually for the new year).
This sets next years' budgets to become the budgets for the current year after running a year end. If the budget for the next year is not defined, then the current year budget remains intact.
This indicates the level at which you require variable budget amounts to be spread across each period of the year.
This applies the spread to all ledger codes in the company.
This applies the spread to ledger codes according to the groups to which they are assigned.
This extends the sales order credit checking routine to the dispatch notes system. It can be performed either at the time of creating the dispatch note or when the dispatch note is released for invoicing.
This indicates how you want to process freight lines (entered during sales order entry) on dispatch notes. You can include them on all dispatch notes, only on the first dispatch note, only on the last dispatch note, or you can exclude them from dispatch notes.
This indicates how you want to process comment lines (entered during sales order entry) on dispatch notes. You can include them on all dispatch notes, only on the first dispatch note, only on the last dispatch note, or you can exclude them from dispatch notes.
This indicates how you want to process miscellaneous lines (entered during sales order entry) on dispatch notes. You can include them on all dispatch notes, only on the first dispatch note, only on the last dispatch note, or you can exclude them from dispatch notes.
This indicates the basis according to which you want include sales order lines in the dispatch review. This can be based on lines having a quantity to ship, lines having a quantity on back order, or lines having an outstanding order quantity (i.e. either a quantity to ship or a quantity on backorder). The suggested dispatch quantity will be based on your selection here, subject to stock availability.
This uses the ledger account defined at the Non-stocked misc and freight field against the AR branch for non-stocked items, freight charges and miscellaneous charges dispatched using the Dispatch Note Review program. If Inventory is not installed, then this option applies only to freight charges and miscellaneous charges dispatched using the Dispatch Note Review program.
If you indicated that unit of measure conversion factors are theoretical then your entry here indicates the cut-off percentage at which the stocking quantity to dispatch is allowed to deviate from the calculated percentage before it is rejected.
This lets the dispatch of a quantity to exceed the order quantity on a sales order line. You won't be able to over-dispatch kit type items if the Retain original order quantity when over-dispatching option is also enabled.
This retains the original order quantity against the sales order when the corresponding dispatch note is over dispatched. You will be unable to over dispatch kit type items if this option is enabled.
This allows the dispatch of a quantity that is less than the order quantity on the sales order line. When using the Dispatch Note Review program, you can under-dispatch the order line and mark the line as complete if no further dispatching against the line is required.
This lets you change the status of a dispatch note to 3 (ready to print) when maintenance is performed on a dispatch note that has been previously printed (i.e. Status 5 - dispatch printed).
This prints dispatch note lines even if the quantity to dispatch is zero.
This lets the operator change the status of a dispatch note manually from 5 (dispatch printed) to 7 (ready to invoice) during dispatch maintenance. Otherwise the status of the dispatch note is set to 7 (ready to invoice) automatically once the dispatch note has been printed.
This retains custom form data captured against dispatch notes, for reprinting on dispatch invoices. If this option is enabled, then dispatch note custom forms are copied to the dispatch invoice reference, enabling you to reprint the forms. Dispatch invoice custom form data is created when a dispatch invoice is printed and can be viewed and maintained using the Sales Invoice Query program. Custom form data is not printed on consolidated dispatch invoices.
This uses the dispatch note number to confirm the next invoice/dispatch. Enabling this option sets the Use dispatch note to confirm delivery option to selected by default in the Contract Maintenance program. You should not select this option if you are confirming deliveries by invoice.
Select this to print a line on the dispatch note invoice for each dispatch line that was consolidated.
This option is only applied if the dispatched lines have the same:
- unit cost
- tax code
- line discounts
- unit of measure and conversion factors
- price and price unit of measure
- tariff codes (for EU companies)
If these fields are the same then the Dispatch Note Consolidation program consolidates the dispatch lines into one line for printing. The option then determines whether it should print the dispatches that make up that consolidated line as sub-lines on the invoice, or print all the dispatches as separate invoice lines.
If you don't select this option, then a line is printed for the total consolidation and a sub-line for each dispatch. You typically select this option to avoid rounding errors. Rounding errors may occur if you consolidate a number of different dispatches for a single sales order line and the sales order quantities are defined to 3 decimal places or the price is defined to 4 or 5 decimal places.
If you select this option, then ensure that you also enable the Individual dispatch lines on cons inv preference (SO Document Formats)
This automatically sets the dispatch note header to cancelled when all lines on the dispatch note are cancelled in the Dispatch Note Maintenance program. As soon as you cancel the last line, the dispatch note itself is set to cancelled. If this option is not enabled, then the dispatch note header remains in the status it was in when you loaded the Dispatch Note Maintenance program.
This values your inventory on a first-in-first-out basis. You won't be allowed to store inventory costs in a unit of measure other than stocked and stock on hand won't be allowed to go negative in any warehouse (except for floorstock items stocked in the floorstock warehouse). This option is automatically selected if Actual costing is enabled, or if Costing per warehouse is enabled and the costing method for any warehouse is set to FIFO.
This requires entry of bins upon the receipt, issue or transfer of items and when capturing stock take information. The Purge and Archive program runs to ensure the default bin is inserted into existing lot records and their associated transactions against your traceable or ECC-controlled items. Run the Balance function of the Order Purge and Inventory Period End programs to ensure there are no quantities in ship without bin allocations and to transfer any qty on hand to the default bin.
This is only available if multiple bins is enabled and the serial tracking system is required. You typically use this to track serialized items by bin location.
This requires a bin to exist in the newly-created InvMultBin table before you can transact against it. This feature is only available in a SQL environment and if the Multiple bins option is enabled.
Initially, all warehouses that use multiple bins will be flagged as fixed bin warehouses. Use the Show Warehouses function to switch off this facility selectively for individual warehouses.
This is the percentage by which the cost of an item received into stock (and a cost change to an item) is allowed to differ from the cost of the item on file. Although a warning is displayed if this percentage is exceeded, it only applies to cost changes made to individual items and it does not apply to receipts if your costing method is set to Standard costing (items are receipted at standard cost and, therefore, no variance occurs).
Select this to monitor inter-warehouse transfers generated from the Inventory Movements program, as well as supply chain transfers generated from the Sales Order Entry program. You must select this to perform requisition issues and/or transfers. Any stock transfers that are still in process should be completed before you enable/disable this feature. The Warehouse Exception program highlights unfinished transfers while the GIT Conversion Program program converts existing warehouse transfers to GIT transfers.
Also known as item or batch-specific costing, this applies to lot traceable and batch serialized items. It uses FIFO valuation to track and process costs and overrides any other costing method defined at company or warehouse level. Manual numbering must be set for traceable items and serialized items must be set for capture at the time of receipt and not during order entry. If you are currently using serials, then first run the Serial File Balance Report to ensure all batch serials balance.
This prints an Inventory Initial Aged Valuation report of stock quantities over the last five years. This is useful when you carry a limited stock of spare parts for component items that may have a long life and you need to provide for the depreciation of these items annually.
This stores the last cost entered for a receipt separately from the standard inventory cost. This only applies if the costing method is set to Standard, or if costing per warehouse is enabled.
Select this to add the calculated cost multiplier value to the receipt cost of an item when using the Inventory Movements program to process a receipt or a GIT transfer in. You must also select the Apply cost multiplier to process receipt option to include the cost multiplier in the last cost of the item. If not selected, then the cost multiplier defined against the item is ignored and its value is not reflected in the Last cost of the item.
This records serial number information when processing transactions for serialized stock items. Once selected, you can only deselect this option when no active orders exist for any serialized item and there is no allocated quantities of serialized items.
This allows the same serial numbers to be used for different stock codes when accepting items into stock. When receipting batch serialized items (and you have not enabled the Multiple batch serial receipts allowed option) the existing serial numbers must be stocked in the warehouse in which the receipt is being processed. This does not apply to manual serials. If this option is not selected, then you cannot receipt reserved serials into an alternate stock code from inspection.
This retains the history of header and transaction details for manual serial numbers against which a negative receipt has been processed (i.e. reversing a receipt processed against the wrong serial number). You won't be able to re-use the serial number for the same stock item. If this option is not enabled, serial history is removed if the only other transaction for the serial was a receipt (i.e. the system assumes you are reversing a receipt done against an incorrect serial number).
This enables you to alternate between entering a SYSPRO stock code or a supplier's catalogue number during Purchase Order Entry. You must enable this option before defining your supplier stock codes. If you enable this option and purchase a non-stocked item from a supplier, the system automatically creates an entry in the supplier/stock code interchange file.
This lets you hold inventory costs in a unit of measure other than the stocking unit of measure. You define the applicable cost unit of measure when adding stock items using the Stock Code Maintenance program. You cannot select this option if FIFO valuation is enabled, or if your costing method is set to FIFO or LIFO.
This depletes lots by the earliest date that a lot was received into stock. If a lot does not already exist then it retains the date of when the lot was receipted for that stock item. Upon transfer to a new warehouse, the receipt date from the original lot is used.
This depletes lots by the earliest lot expiry date. Upon transfer to a new warehouse, the receipt date is set to the transaction date. If a lot does not already exist then it is created with the transaction date.
This initially assigns each warehouse the chosen costing method. You can then change the method for specific warehouses (e.g. when high value, low usage items are stored in a separate warehouse and you require a different method of costing for accuracy. Alternatively, if you manufacture and distribute a product you may want to apply standard costing to your work in progress and average costing to your distribution warehouse). Otherwise the costing method selected is used for all warehouses.
This uses the BOM costs held against the warehouse for costing purposes for all stock items held in that warehouse. Otherwise the BOM costs held against each individual stock item are used for costing purposes and you won't be able to process the cost implosion by warehouse. You should use the Cost Implosion program to roll-up costs before selecting this option. You must select this option to be able to use the cost against an alternate route when you transfer BOM costs to Warehouse.
This determines how your inventory is valued.
This averages out the new cost and the existing cost of an item.
This lets you define a cost for each item that is only updated using the Cost Change function or Transfer BOM Costs to Warehouse Costs program.
This values your inventory according to the last cost entered when receipting the item.
This issues from the oldest bucket held on file.
This issues from the newest bucket held on file.
If you change to LIFO costing (company-wide or against a warehouse then we recommend you run the Balance function of the Inventory Period End program before you start posting transactions.
Indicate whether you want to allow stock on hand to go negative in warehouses for the selected company.
The Yes and Dependent on warehouse options do not activate negative stock for the warehouse; you must maintain details against the warehouse(s) for this option to take effect.
Indicate a specific list of warehouses in which stock is allowed (or not allowed) to go negative.
Indicate a range of warehouses in which stock is allowed (or not allowed) to go negative.
This lets you choose whether to allow or disallow negative stock for the selected warehouses.
If you don't select this option, then FIFO journals are still created, but they are not printed. It also does not prevent FIFO journals from being displayed in the Journal Entries listview of the Inventory Movements program.
This makes adjustments to lots from the most recent FIFO bucket when running the Balance function of the Inventory Period End program. This applies only when FIFO valuation is enabled.
This allows a zero cost transaction to be processed when returning stock to a LIFO bucket that has a zero unit cost. The returned quantity is added to the LIFO bucket, but the unit cost of the bucket remains unaffected. Otherwise a new LIFO bucket is created with the returned quantity at the current warehouse cost. The Stock Take Confirmation program updates LIFO buckets according to your selection here.
This uses the web-based Product Configurator instead of the Configurator Wizard wizard program.
Enter the path to the logon screen of the Product Configurator website.
This includes non-merchandise costs (entered in the Apportion Details function of the PO Receipts with Apportionment program) in the last cost of the item. It also includes the calculated cost multiplier value to the receipt cost of an item when using the Purchase Order Receipts program. When receipting into a standard costing warehouse, the standard cost of the item is used; non-merchandise costs are not included in the last cost.
This restricts each purchase order to a single warehouse (i.e. you cannot enter a warehouse per line). The warehouse address is used as the delivery address for the order and can only be changed if the Allow maintenance of delivery address option is enabled. You can define a default warehouse against operators who use the Purchase Order Entry program so that they don't have to manually enter the required warehouse when adding purchase orders.
This stores all purchase order receipts entered in a special suspense file for Accounts Payable invoice matching and checking.
This allows an operator to decide whether the supplier must be paid for inspection items that are scrapped.
Indicate the minimum capex requisition line value permitted before the program forces the requisition user to enter a valid capex number.
You typically enter a minimum value here to ensure that any requisition line with a greater value is seen by the requisition users listed at the Mandatory user codes checked in routing field, before being approved. This lets each requisition user (to whom the line is routed) view the line and add comments, if required.
This indicates the minimum value from which you can create an RFQ from a requisition.
Indicate the first user code to which you want to route a requisition line when the Minimum line value for checking routing amount is exceeded.
Indicate the second user code to which you want to route a requisition line when the Minimum line value for checking routing amount is exceeded.
Indicate the third user code to which you want to route a requisition line when the Minimum line value for checking routing amount is exceeded.
Indicate the fourth user code to which you want to route a requisition line when the Minimum line value for checking routing amount is exceeded.
This indicates you don't require the entry of routing narrative when saving a requisition, or when accessing additional information, or when routing the requisition to another user.
This automatically replaces whatever narration you entered in the Route note field with the routing comment: Automatically Approved or Requires Approval, depending on whether a requisition/requisition line is approved or fails approval.
This allows you to maintains budgets for groups of requisition users. Ensure that you have defined requisition groups and allocated all requisition users to a requisition group.
This defines requisition budgets at stock code level (you can enter a budget for a product class instead of stock code if you want to budget for non-stocked items at product class level).
This defines requisition budgets at product class level (you can also define a stock code within the product class).
This indicates the budget values are monetary amounts.
This indicates the budget values are quantities.
This means you don't want to use stores requisitions (i.e. requisitions can only be turned into purchase orders).
This creates requisitions on your warehouses to supply items.
This creates requisitions to transfer items from another warehouse.
This lets you to choose the type of requisition to create providing your requisition user authority level allows you access to the detailed information in the Requisition Entry Maintenance program.
This performs checks based on the maximum requisition values defined against the requisition user. Automatic approval can only be done at this level.
This performs checks based on the maximum approval value defined against the requisition user group. Automatic approval cannot be done at this level.
This performs checks based on product classes within user groups. Automatic approval cannot be done at this level.
This optionally includes fixed costs and minimum charges when calculating the new landed cost of an inventory item (calculated using the Calculate New Landed Cost program). You configure fixed costs/minimum charges against LCT elements which you attach to the various routes that you will use to ship items from the supplier to your warehouse.
This lets you add a purchase order line with a zero price to a shipment using the LCT Shipment Maintenance program.
This includes the calculated cost multiplier value with the receipt cost of an item when using the Shipment Receipt program. It also includes the additional costs calculated when using calculation codes to apportion additional costs incurred within a shipment. This only applies to foreign currency suppliers. You will also need to enable the Inventory option to apply a cost multiplier when processing receipts.
This uses an alternate unit of measure as the basis of any calculation or apportionment in Landed Cost Tracking. The quantity of a purchase order raised using an alternate unit of measure is converted to the stocking unit of measure on all lines of the shipment. This means that when calculation codes or apportionments are done, all the lines are based on the same unit of measure. Otherwise all calculations are always based on the quantity entered on the purchase order.
This creates an order when cross-shipping an item that has been returned by a customer for repairs or refurbishment. Cross-shipping is typically required when the customer is unable to return the defective item before receiving the replacement.
This creates a works order for the repair of merchandise that has been returned by a customer.
This only prints the RMA.
This forces the operator to enter a problem code at the time of issuing an RMA. Don't enable this if you want the system to prompt you for a restocking code 'At line level' as the prompt is only displayed if the problem code on the RMA is blank.
This automatically creates a sales order when issuing an RMA which requires a cross-shipment (i.e. a customer requires the replacement item before being able to return the defective item).
This prompts you to enter serial numbers when processing a cross-shipment. Otherwise you only need to supply the serial numbers at the time of invoicing (i.e. when the order goes to a status of 8). If multiple bins is installed in the warehouse, or the stock code is lot traceable or ECC-controlled, then you have to capture serial numbers regardless of your selection here.
This indicates the maximum number of days that merchandise returned for cross-shipments can be received before warning messages are displayed.
This indicates the default product class for restocking.
This indicates that restocking is required when the customer is credited for the return of defective items.
This indicates that restocking is required for the repair of items that are still under warranty.
This indicates that restocking is required for the repair of items that are no longer under warranty.
This indicates that restocking is required when the customer is unhappy with the product and requires a credit.
This indicates that restocking is required for a returned item that was incorrectly ordered by a customer.
This indicates that restocking is required for a returned item that was incorrectly shipped to a customer.
This indicates that restocking is required when the customer needs to be credited for the balance of a shipment that was short-supplied.
This indicates the default product class that will be used for non-stocked items when adding an RTS.
This generates AP credit invoices for a supplier for any freight and/or handling costs incurred on returned merchandise.
This is the account to which postings are made for RTS items accepted for a credit, or rejected and scrapped transactions.
This is the account to which variances (positive or negative) are posted when an RTS is accepted and the price differs from the original captured price.
This is the account to which the cost of rejected goods returned by a supplier needs to be expensed.
This is the account to which posting is made when an RTS item is accepted for credit or replacement. The entry creates an accrual in GRN Suspense against the anticipated credit note from the supplier.
This is the account to which posting is made to decrease the cost of goods sold and to move the value of non-stocked goods returned via RMA into the RTS control account.
The RTS Journal Report must be run to generate this journal entry.
This is the account credited by the freight charges for an RTS item that has been accepted by the supplier. The default AP control account is debited by this amount in anticipation of a supplier credit for freight charges.
This is the account credited by the handling charges for an RTS item that has been accepted by the supplier. The default AP control account is debited by this amount in anticipation of a supplier credit for handling charges.
This indicates whether you want to store month-to-date and year-to-date sales figures in the salesperson/product class file as quantities or values. Because Sales Analysis figures are held in a single set of buckets, if sales analysis history already exists and you change this option then historical information is not changed (i.e. a mix of quantities and values is displayed in the Sales Analysis Query).
Enable this to produce an analysis of all taxable/exempt sales made against each tax code for the period, month and year-to-date from the Sales Tax program. If this option is changed at a later date, then no details are printed on the report, regardless of whether data is held on file.
This updates your sales history files only at the time of running the Sales Analysis Update program.
This updates your sales history files real-time (i.e. the sales history files are updated after the completion of each AR invoice transaction, depending on your sales history selections). If you have existing sales orders, then you need to run the Sales Analysis Update program before changing this option, to ensure that all transactions are updated in the Sales Analysis files.
This retains a detailed history of sales transactions based on your selections at the Detailed key options section of the screen. The detailed history is sequenced according to these keys. If you select this option, then you must include at least one key option before you can exit the program.
This retains a summary history of sales transactions, sequenced according to the sales history key areas defined using the Maintain Summary function.
This retains a file of all the transactions from the Accounts Receivable sales transaction detail file that has been used to create history. This enables you to re-define your sales analysis key selections after implementation and rebuild your sales history detail and summary files automatically using the Recreate Sales History program.
This retains the summary zoom index (maintained in the Sales Analysis zoom index on the sales history summary file).
It is used by developers of 3rd party applications (e.g. ODBC-compliant programs such as Access or Excel) to drill down to the transactions making up a particular value.
You would therefore only select this option if you intended to write custom reports to drill down to transaction level. You must retain the archive sales history data if you want to retain the summary zoom index.
Miscellaneous charges (except ones processed against an underscore product class) are included in your summary, detail and archive history.
When adding miscellaneous lines in Sales Order Entry, ensure that you review the default product class (_OTH) assigned.
To update past history:
- Select the Recreate archive from transactions option in the Recreate Sales History program.
- Re-run the Recreate Sales History program and select the Recreate history detail/summary from archive option.
If retaining detailed sales history, this includes the salesperson as part of the key to your detailed sales history records.
If retaining detailed sales history, this includes the branch as part of the key to your detailed sales history records.
If retaining detailed sales history, this includes the order type as part of the key to your detailed sales history records.
If retaining detailed sales history, this includes the customer class as part of the key to your detailed sales history records.
If retaining detailed sales history, this includes the geographic area as part of the key to your detailed sales history records.
If retaining detailed sales history, this includes the customer as part of the key to your detailed sales history records.
If retaining detailed sales history, this includes the warehouse as part of the key to your detailed sales history records.
If retaining detailed sales history, this includes the department as part of the key to your detailed sales history records.
If retaining detailed sales history, this includes the product class as part of the key to your detailed sales history records.
If retaining detailed sales history, this includes the stock code as part of the key to your detailed sales history records.
This uses the branch as the default warehouse in Sales Order Entry, Point of Sale Entry and Product Configurator. Otherwise, the default warehouse defined at operator level is used. If this is not defined, then the default warehouse defined at company level is used.
This allows the entry of negative quantities for stocked and non-stocked lines when capturing orders.
This calculates the invoice discount after line discounts have been applied. Otherwise invoice and line discounts are applied to the total merchandise value of the order entered.
This updates the sales order customer delivery performance file/table with details of each stocked and non-stocked order line invoiced. If using single level bill of materials, then only details of the parent part of the kit is output to the performance file. Details are not output for IBT sales, credit/debit notes, any order line containing a negative line, and any order line for which the order quantity is zero.
This indicates how you want to be notified of stock shortages for billing-type orders.
This only notifies you if the back order decision is by operator (or by warehouse and stock is not allowed to go negative).
This only notifies you if stock is not allowed to go negative.
This only notifies you if stock is not allowed to go negative and also caters for entry of a manual invoice number for the first invoice produced, even if automatic invoice numbering is selected.
This is the number of days (up to 99999) within which stock for a line must be allocated for scheduled orders. Stock is allocated if the difference between the order date and the entered ship date is less than the number of days entered here. If equal to, or greater than the number of days entered here, then stock is not allocated. If you change this entry, then any quantities already allocated and ready to be shipped are reset and placed on back order.
An entry is required here if your Default Sales Order browse sequence preference is set as Alternate key. This can be the geographic area assigned to the customer, the warehouse assigned to the order, or the branch assigned to the order. Alternate keys enable you to browse on orders in a sequence other than order number, customer, or customer purchase order number.
This will force an entry at the Alternate key field when capturing sales orders or RMAs.
Enter your own wording for the Alternate key field. This description does not apply to the Point of Sale Entry program. To avoid confusion with standard SYSPRO field descriptions in forms and listviews, we don't recommend that you use the same description as a key field in SYSPRO (e.g. customer, supplier, stock code, etc.). You'll need to manually change the Alternate key caption (right-click the Alternate key field, select Field Properties and change the Caption field).
This lets you indicate the stock code cross references that must be used when adding stocked lines to an order using the Customer/Stock Code Interchange facility.
This uses only the stock code cross references defined against the sub-account.
This uses only the stock code cross references defined against the master account.
This uses the stock code cross references defined against the sub-account (if they exist) or the master account.
This displays a Packaging Details screen when you select it from the Dimensions function of the Sales Order Entry program.
This displays the Packaging Details screen when you save a stocked line with a non-zero ship quantity.
This displays the Packaging Details screen when you save a stocked line with a non-zero ship quantity, but prevents you from saving the line until these details are entered. The details are translated into comments that are attached to the order line.
This lets you assign your own wording for the Special instructions field. This field can be printed on delivery notes and invoices.
Assign your own wording for the Order type field. The field is used to classify sales orders according to the type of sale, as well as a selection criterion for the printing of Sales Order reports. It can also be used in the Sales Analysis module to provide a breakdown of the salesperson, product class and sales history reports.
This indicates you want to enter a stock item's price manually for each order line.
This establishes the price by combining the customer's Auto price code selection and whether the item's pricing method is coded or discounted.
This matches the stock item's Price category to a position in the customer's Price category/code table to establish the price of an item. The price code/discount code is retrieved depending on whether the item's pricing method is coded or discounted.
This option enables you to control the price update of a stocked line with quantity discounted pricing.
This recalculates the price on a sales order, regardless of whether changes have been made to the line (this caters for a situation where the quantity discounted price has changed).
This recalculates the price only when a change is made to the order quantity of the line.
This calculates line discounts by multiplying the price of an item by the quantity ordered and then applying the discount applicable.
This calculates line discounts by applying the discount to the unit price before multiplying this by the quantity ordered, letting you establish the net unit price of a line to which the quantity is then applied.
This uses the system/company date to determine the validity of the price (the date must be in the range of the valid sales order contract for the correct price to be used on a sales order). The ship date entered in the sales order header is ignored.
This uses the date entered in the Order date field to determine the validity of price contracts. The system date and the ship date entered in the sales order header are ignored.
This disables order maintenance functions if a delivery note has been produced for an order.
This disables order maintenance functions if a delivery note has been produced for an order but allows for the cancelling of an order line/order.
This enables the order maintenance functions if a delivery note has been produced for an order. This option is set at company level and therefore applies to all operators. However, you can prevent unauthorized access using operator activities.
This saves sales order custom form information against invoice reprint details and allows its retrieval at the time of reprinting the invoice. The information is deleted when you select the Purge invoice reprint file option in the Order Purge program. Custom form fields defined against the sales order (header) and individual order lines are saved for reprinting. Invoice custom form data is created when an order is printed and can be viewed and maintained by the Sales Invoice Query program.
This prints all orders lines on the initial invoice, including lines with a zero quantity to ship. Subsequent invoices will print only those lines where there are goods to ship.
This prints only lines with a non-zero ship quantity on the initial invoice. Regardless of your selection here, details for back-ordered lines are printed on the invoice if you enabled the Print all back-ordered lines option at the time of defining the invoice format.
This lets you enter an expiry date for manual serial numbers entered during sales order processing.
This lets you enter a scrap date for manual serial numbers entered during sales order processing.
This lets you indicate the level at which you want to set a minimum percentage by which the price must exceed the cost for stocked and non-stocked items. This does not apply to credit notes or inter-branch transfers.
For Stock code margin this is only used if you have assigned a minimum margin to the item.
Margin checking is only performed when the order line is entered and saved. It is based on the current cost (if your costing method is Standard or Average) and on Last cost (if your costing method is FIFO, LIFO or Last cost).
This bases the minimum margin check on the extended order line value, excluding any line discounts.
This bases the minimum margin check on the extended order line value, including line discounts.
For Kit type F items, the check is performed on the parent.
For Kit type K items, the check is performed on each individual component of the kit.
For Kit type S items, no check is performed.
This enables you to continue processing an order, regardless of whether the minimum price margin has been exceeded. Otherwise you will be unable to continue processing a sales order that has exceeded this minimum price percentage above cost margin.
This indicates the warehouse from which returnable items (e.g. crates, pallets, etc.) must be depleted. The warehouse entered here is ignored if you enable the Use associated merchandise warehouse option.
This uses the warehouse associated with the stock item as the warehouse from which the returnable item must be depleted. If this option is enabled, then the entry at the Warehouse field is ignored. When processing a supply chain transfer, only one source and one target warehouse can be specified. Therefore, a returnable item is always issued from, and receipted into, the source and target warehouses selected for the SCT.
This relates to the entry of customer purchase order numbers in the Sales Order Entry and Quick Sales Order Entry programs.
This indicates you do not require unique customer purchase order numbers.
This requires unique customer purchase order numbers for the customer.
This requires customer purchase order numbers to be unique for the company.
This generates order analysis files when you add order lines.
This generates order analysis files when you change order lines.
This generates order analysis files when you cancel orders and order lines. Ensure that you also enable the Output detail lines for cancelled order option. You must also select this option if you want to record lost sales when cancelling merchandise lines in programs such as Sales Order Entry or Point of Sale Entry.
This generates order analysis files for blanket sales orders. If you enable this option together with the Order lines added option, then when processing a release for a new sales order the sales order is included in the Order Intake Query. Similarly, if you enable this option together with the Order lines changed option, then any changes to a blanket sales order are included in the Order Intake Query.
This generates order analysis files when changes are made to order lines affecting the total value of discount applicable to the order.
This includes all the detail lines attached to an order in the order analysis files generated when you cancel an order.
This enables you to alternate between entering a SYSPRO stock code or the supplier's catalogue number when capturing sales orders.
This generates detail order lines for first level components automatically when capturing an order for a parent stock item. You must select this option to be able to process the return of kit items using the RMA Issues and Receipts program.
Define the wording you want to print/display for the packaging comment. Packaging details are printed as comment lines against sales order lines for stocked items. In addition, the wording you define here is displayed on the Packaging Details screen of the Sales Order Entry program.
Indicate the default wording that you want to display for the package type field. The default wording is 'packages', but this can be changed to the package type you typically use (e.g. cartons, boxes, rolls, pallets, containers, etc.).
This is the default wording you want to use for the package contents field. The default wording is 'containing', but can be changed.
This is the default wording you want to use for the unit of measure contained in the package. If blank, then the order unit of measure defined on the sales order line is used for the packaging comment.
This lets you reserve stock for a customer when processing sales orders for stocked and non-stocked items (i.e. it prevents the sale of that stock to another customer, which allows you to guarantee delivery prior to the actual shipping process). Reserved quantities are not used in Dispatch notes - if you want these order quantities to be considered for dispatch then any reserved quantity must be moved to backorder or ship.
This requires the entry of lot, bin and serial information when reserving stock (unless the Capture serial numbers for orders option is not selected; multiple bins is not in use; and the item is not traceable, in which case you are only prompted when the items are shipped). The Automatic deplete in Inventory preference option takes precedence over this option (i.e. lots are allocated automatically from the first lot that can fully satisfy the requirement).
This places the quantity in ship when processing a receipt linked to a sales order.
This places the quantity in reserve when processing a receipt linked to a sales order. Any lot and serial information entered against the receipt is automatically added to the order.
This reserves quantities only if the sales order is in a status 4 or status 8. Otherwise the quantity received is moved into ship.
This bases credit checking on whether the customer's balance and outstanding order value exceeds the credit limit. If a customer fails a credit check, then the entered order is placed into suspense until the appropriate credit authority is entered to release the order.
This bases credit checking on the customer's invoice terms and is performed automatically when processing orders during sales order entry. The calculation using the invoice terms code, the invoice ageing method and settings configured against the customer.
This uses the credit status of the customer when performing invoice terms credit checking. The number of days outstanding is calculated as: 30 times the credit status defined against the customer, less the number of days defined against that customer's invoice terms code. If the result is positive, then the terms are deemed to have been exceeded. Otherwise the terms credit check is based on the number of days that the oldest, non-credit transaction is outstanding against the customer.
This performs credit checking on current orders at the time an order is shipped and is based only on the customer's credit limit. This option only applies when the Apply check to current order only preference is enabled.
If checking the customer's credit limit, then this includes tax when calculating a customer's outstanding/released order value.
If the Apply check to current order only preference is enabled, then tax is included when the invoice is about to be produced.
If the Apply check when quantity moved to ship option is enabled, then tax is included when the order is shipped. It does not apply if USA tax is in use (USA tax is always exclusive, so the order value is always exclusive).
If checking the customer's credit limit, then this includes tax when calculating a customer's invoiced order value. It does not apply if USA tax is in use (USA tax is always exclusive, so the order value is always exclusive).
This indicates the number of decimals to use when calculating contract prices and net unit prices. The number of decimals normally applied to pricing calculations is three. This option enables you to round the calculated price to two, three, four, or five decimals. This option only affects contract prices that are calculated (i.e. mark-up list price, mark-up cost by a percentage, quantity discount breaks, list price less a percentage, list price less chain discount, coded less chain discount)
This includes order lines attached to contracts that are defined as a flat price, coded, list price less a percentage, or mark-up cost by a percentage in the order line discount calculation. Contract prices based on a discount (i.e. quantity discount breaks, list price less chain discount and coded less chain discount) are excluded from the order line discount calculation.
This bases commission on the sale of merchandise after discounts have been applied.
This bases commission on the profit gained from net merchandise sales.
This bases commission on the merchandise sale quantity multiplied by the list price of the item, regardless of the actual price entered against the order line.
This multiplies the commissionable amount by the commission percentage assigned to the salesperson.
This multiplies the commissionable amount by the percentage assigned to the commission code of the price code used in the order.
Select this to request the commission code whenever the commission is based on price.
This enables delivery notes to be printed online when processing sales orders
This enables invoices to be printed online when processing sales orders.
This allows invoice reprints to be printed online when processing orders.
This enables order acknowledgments to be printed online when processing sales orders.
This prints all order lines on delivery notes, regardless of whether there is any quantity to be shipped. This option relates only to merchandise lines on delivery notes (freight, miscellaneous and comment lines are printed if you have configured them against the document format). If you enabled the Print all back-ordered lines option when defining the delivery note format, then details for back-ordered lines are also printed on the delivery note.
This prints plus/less wording on delivery notes and invoices for any chained discount percentages entered against an order.
This indicates the default counter sales or point of sales customer you want to use when processing an order. This is used only if you have not defined a default Counter sales customer against the operator. You can also define customers as cash only customers by enabling the Counter sales only option in the Customers program. This prevents credit sale transactions from being processed for these customers.
This displays change due after printing a counter sales invoice or a point of sale document (either from a new order or as a result of maintaining an existing order). The change due from the last invoice is displayed when you return to either the Customer field or the Order number field.
This changes the order type of a normal order to be a counter sales type order when processing deposit transactions against the order.
If you select this option together with the Deposits only for back order quantities option, then the sales order must be in a status 4 or status 8 before you can process a payment or a deposit.
This option does not apply to the Point of Sale Entry system.
Select this if you only want to be able to process deposits for counter sales if the order has a quantity on backorder.
This enables you to close a counter sale without processing a payment, regardless of whether there is an undistributed amount.
This is useful, for example, where the merchandise line is on back order but the counter sale includes freight and/or miscellaneous charges which should only be invoiced when the merchandised line is shipped.
If you select this option, then the End Sales Order function is enabled on the counter sales screen.
This option does not apply to Point of Sale Entry.
This allows operators to change the default payment code defined against the Payment code for cash transaction option when processing transactions to pay cash out or take cash in. You can prevent operators from changing the payment code by restricting access to the Counter Sales payment code cash in/out operator security field.
This sets the default payment code to use when processing transactions where cash is paid out of the cash drawer, or taken into the cash drawer. If the Change payment code for cash transaction option is enabled, then the payment code can be changed at the time of paying cashing out or taking cash in.
This enables you to process a payment in a foreign currency for a local currency customer. This only applies to Normal payment types processed using the SO Counter Sales program.
This displays and prints counter sales payments as comment lines against the order/invoice. If you don't select this option, then details of counter sales payments can be printed on sales order documents as payment lines.
This displays and prints counter sales deposits as comments against the order/invoice. When more than one deposit is taken against a counter sale, an additional comment line indicates the current total deposit amount on the sales order. If you don't select this option, then counter sales deposits can be printed on sales order documents as deposit lines.
This allows you to enter a list of up to 10 invoice formats for which you want to print invoices on continuous stationery (with one header and one total section). If you leave this blank, then your invoices will print on standard invoice stationery with a header section on each page and both a header and total section on the last page.
This lets you restrict entry of the credit card number in the SO Counter Sales program and the display of the credit card number on the Counter Sales Report.
This lets you enter up to 18 digits.
This lets you enter up to four digits.
Once enabled, you must configure a route code against each customer (or warehouse, for an SCT order) to indicate the standard delivery method as well as a distance to indicate the order in which the load must be delivered. You associate a delivery frequency to each route as well as the number of deliveries that can be made on a single day. You associate an order to a route based on the customer and as each specific line is added to the order, the appropriate route detail (load) is calculated.
This lets you create delivery loads only on working days as defined in your company calendar.
This includes sales orders created through counter sales in Load Planning.
This calculates load capacity using the ship qty of each order line added to the load. A single order line can be part-shipped on different loads.
This calculates load capacity using the order qty of each order line added to the load. Each order line must be delivered in full on a single load.
This calculates load capacity using the dispatch qty of each dispatch note line added to the load. Each dispatch note must be delivered on a single load.
When you use the Browse on Delivery Routes or Delivery Loads programs to add loads to a route, you can let the system automatically create additional loads based on the information you entered for the first load.
This creates loads based on the number of loads specified at the Number of loads/days field.
This creates loads based on the number of days specified at the Number of loads/days field.
This is the default number of loads/number of days for which you want the system to automatically add loads when using the Browse on Delivery Routes program.
This allocates sales order lines to loads based on the required delivery date and the capacity of the load.
This allocates sales order lines to loads based on the date when stock is available for delivery and the capacity of the load.
This allows you to manually allocate sales order or dispatch note lines to loads when the lines are added/dispatched.
This allocates lines to loads automatically when the lines are added/dispatched.
This lets you only allocate sales order or dispatch note lines to loads using the Load Planning Delivery Load Maintenance program.
This checks that a delivery note or dispatch note was printed for each order line on a load before the load can be set to Confirmed.
This checks that an invoice was generated for each order line on a load before the load can be set to Confirmed.
This text is used to label deduction entries processed in the AR Payments and Adjustments program.
Enter text to prefix the stock description of free goods on a free goods promotion line. This defaults to Free: if left blank. However, promotions that allow the addition of extra stock items to an order often carry a price, so the prefix of Free is not always appropriate. {blank} uses the description of the free goods stock item without a prefix.
This assigns the current system date to the debit note generated when reinstating a deduction (using the Deduction Review program).
This assigns the original payment date to the debit note generated when reinstating a deduction.
This applies Trade Promotions credit checking after normal customer credit checking and is only relevant if Sales Order credit checking is enabled.
This includes kit components in the qualifying totals for the relevant global promotions.
This automatically ships free goods for a sales order line qualifying for a tiered free goods promotion, if the full quantity of the free good is available and the parent item is also shipped. Otherwise free goods line quantities are automatically placed on backorder for later release.
This automatically ships free goods for a sales order qualifying for a global free goods promotion, if the full quantity of the free good is available and the parent items are also shipped. Otherwise free goods global quantities are automatically placed in backorder for later release.
This applies order discounts in the Sales Order Entry and Point of Sale Entry programs to customers defined as Trade promotions customers (this does not apply to line discounts by product class). Order level discounts are not applied to customers defined with Trade promotions pricing.
This reduces rebate accruals when credit notes are created from invoices against which trade promotions accruals apply. When a credit note is built from an existing invoice, any accrual-type promotions applied on the invoice for the credited lines are recorded against the credit note. When the credit note is invoiced, the value of the accrual promotion for the original invoice is reduced based on the quantity credited, and a new transaction is created.
This controls the creation and updating of off-invoice promotions on a credit note.
This prevents order discounts from being applied to certain trade promotions lines.
Select this if you don't want to apply order discounts to free goods lines.
Indicate the default product class to use when adding off-invoice tiered promotions using the Promotion Code program.
Indicate the default product class to use when adding off-invoice global promotions using the Promotion Code program.
This uses the same product class code applied to the merchandise line for its promotional free goods item.
This uses the same product class code applied to the merchandise line for its promotional off-invoice value.
These options display the custom form fields defined against any inventory form. They provide additional qualifying criteria when adding promotions in Promotion Code.
Select the stock custom form to be included in a promotion.
Select a second stock custom form to be included in a promotion.
These options display the custom form fields defined against any customer form. They will be used as variable customer qualifications in Promotion Code.
Select the customized customer criteria to be included in a promotion.
Select a second customized customer criteria to be included in a promotion.
Indicate whether you want to apportion a product's elements of cost at the point of transition in the purchasing, manufacturing and sales cycle. If you choose not to update costs, then ABC fields are accumulated in parallel with conventional costs when the Cost Implosion program is run, but only the conventional costs are used in the accounting system
This lets you formalize changes to your bill of materials without needing to retain previous iterations of the bill.
This requires you to indicate the revision level when processing purchase orders, sales orders and jobs.
This requires you to indicate the revision and release level to use.
This lets you create more than one allocation against the same job at the time of issuing ECC material allocations to the job and depleting the oldest revision/release (only if the Deplete oldest rev/rel first (Component) option is enabled).
When this option is enabled, all ECC components against BOMs and jobs with an ECC consumption method of Use oldest are set to Use current (Structures and Routings). An allocation is created per revision/release, from the available quantity to issue of the rev/rel, for the quantity required for the job.
If not enabled, it prevents mixing different revisons/releases in one transaction when issuing ECC components to a job, or when backflushing using the Inventory Movements program if the Backflushing deplete oldest rev/rel option is enabled. In this case, the oldest rev/rel is not depleted when there is insufficient quantity to issue and the next single revision/release with sufficient quantity on hand is used instead.
Component reservation and depletion are mutually exclusive, so this option is not available when Reserve stock for confirmed jobs is enabled (Setup Options > Configuration > Manufacturing > Work in Progress).
This indicates that no changes are cosmetic (i.e. the revision/release is changed for each ECO change made).
This lets the system decide if changes are cosmetic or major.
This lets the operator decide if changes are cosmetic or major.
If you're applying BOM changes to an ECO and a component revision/release has changed, then this updates the component revision/release against BOMs of affected parent items in which the component exists. If the component revision/release is the same as the current revision/release of the component before it was updated, then the component revision/release against the BOM is updated automatically with the new revision/release of the component, regardless of this option.
Enable this option to prevent SYSPRO incrementing the release number of an item when only minor changes (which do not materially impact the composition or functionality of the part) are made to the BOM.
Indicate the revision/release to use (i.e. the consumption method) for jobs created from Bill of Materials.
Enable this to change BOM components with an ECC consumption method of Use current to a consumption method of Specific and to set the current revision and release against these allocations when creating a job.
This issues the oldest revision/release when issuing components to a job. You can also specify whether multiple revisions/releases of components can be issued to the job by setting the Allow issues from multiple rev/rels option. You cannot deselect this if an MRP snapshot exists and material allocations in the snapshot tables are set to Deplete oldest. The snapshot must be deleted first. You cannot select this if you are reserving stock for WIP allocations.
These options apply to the creation of purchase orders for ECC items. No default forces manual entry of a revision/release at the time of adding a purchase order.
These options apply to the creation of inventory movements for ECC items.
This enables you to issue the oldest revision/release when issuing components during backflushing and is only available when Deplete oldest rev/rel first (Component) is enabled.
These options apply to the creation of sales orders for ECC items. No default forces manual entry of a revision/release at the time of adding an sales order.
This prevents you from attaching a traceable component to a non-traceable parent item (ensuring that you can trace a component through all the levels as well as see where a lot has been used). You can still attach non-traceable components to a traceable parent part (e.g. you may not want to trace 'grease' as an item, but you still want to be able to use grease when making a traceable parent item). This option also affects the replacement of components.
This allows the same lot numbers to be used for different stock codes when adding new lot numbers in the Inventory, Purchase Orders and Work In Progress modules. Don't select this if you require lot numbers to be unique at company level. This option does not apply to adding lots if the Automatic lot numbering option is enabled as you won't be able to receipt in a specific lot. The option is ignored by the Job Receipts program if you enabled the Lot number to be equal to job number option.
The profit entered here is applied to non-stocked items on a quotation once any additional charges have been added.
This adds a default markup percentage to each non-stocked item on a quotation (this is added to the cost of the item).
This adds a default percentage margin to each non-stocked item on a quotation (this is added to the selling price of the item).
This determines how you want to calculate the costs and manufacturing lead times for made-in items when you use the Cost/Lead Time Rollup function.
This uses the current inventory cost of made-in items as the basis for the calculation.
This uses the last cost used for made-in items as the basis for the calculation.
This uses the current Bill of Materials material cost of made-in items as the basis for the calculation.
This calculates and applies sales order discount breaks to sales orders created from quotations using the Quotation Confirmation program. If you don't select this, then you won't be able to apply discounts according to discount breaks to a sales order created from a quotation.
This recalculates and applies discount breaks when confirming a quotation. Otherwise the incorrect discount may be applied to the order (e.g. if you have 2 quote lines for a product class - one below the minimum quantity and the other above, both lines are discounted because the system adds the total quantity for the product class to apply discount. If you confirm the quote, but only select the line that is below the minimum quantity, the discount is not recalculated).
This caters for a number of versions of a single quotation, instead of changing the quotation number each time you amend and save the quotation using the Quotations program.
If quotation version is enabled, then this prompts you to change the quotation version number when changing an existing quotation using the Quotations program. The prompt occurs once only on the first change of the quotation. Thereafter, it is only redisplayed after you save the quotation and version and later make another change. If not enabled, the quotation version number is automatically increased on a change.
Choose the default pricing method to use when reviewing suggested purchase orders within the Purchase Order Review program. This can be the Current inventory cost price, the Last price paid or the Purchase price.
This includes the final phase of the requirements planning calculation. If not selected, then the dynamic capacity profile is not built in the snapshot directory and load levelling is unavailable within Requirements Planning.
This is added to the longest cumulative manufacturing time to calculate the manufacturing time fence.
This indicates the number of days into the future that you want to look for forecasting purposes (i.e. the number of days from the planning time fence that general planning will take place). The visibility factor (in days) added to the planning time fence gives the planning horizon and any date thereafter is not normally subject to any build schedules. Note: The higher the Visibility factor, the longer the Requirements Calculation program will take to create the snapshot.
This schedules supply according to the earliest demand date found, even if the supply may have been linked to a demand in the future. Selecting this may lead to inappropriate assumptions as supply dates may be suggested to be altered to new dates which are impractical to implement. Not selecting this option may lead to serious over-ordering of supplies as an unsatisfied demand generates a suggested job or purchase order, despite the availability of supply the next day.
This leaves your live data files unlocked while snapshot files are created using the Requirements Calculation program. Regardless of your selection, you cannot run the Requirements Calculation program while any job maintenance program is being run by any operator; or when the SCT creation program is being run and you are including transfers or quotations; or when converting a customer, supplier or GL code through the respective conversion programs.
This enables you to load jobs onto the dynamic capacity profile so that you can identify and resolve capacity constraints that occur within the manufacturing time fence. You can determine the seriousness of work center overloads and identify the jobs contributing to the overload. You can then maintain these jobs and alter the quantity to be made, change the start/finish dates, or move operations within the job by manipulating the queue time, move time or the operation elapsed time.
This uses the manufacturing unit of measure held against components when adding them to a bill of material. This enables you to manufacture items in the unit of measure in which you make them instead of the stocking unit of measure. Note that transactions are always calculated in the stocking unit of measure. They are then converted to the manufacturing unit of measure for display and reporting purposes, allowing you to view and report on the unit of measure you entered to manufacture the item.
These options only apply if the relevant components of the Advanced Scheduling and Planning module are installed as part of your license agreement (i.e. Finite Capacity Scheduling, Factory Planning, Progress Tracking and Quality Monitoring).
This requires the advanced scheduling programs to be available for use within this company. The advanced scheduling programs are run from the Scheduling folder of the Factory Scheduling menu.
This updates the Advanced Planning and Scheduling system whenever a sales order is added, copied, changed or canceled. This option replaces the need to configure SYSPRO triggers to generate a link between the Sales Order module and the Advanced Planning & Scheduling system.
This updates the Advanced Planning and Scheduling system whenever a job is added, changed or canceled. This option replaces the need to configure SYSPRO triggers to generate a link between the Work in Progress module and the Advanced Planning & Scheduling system.
This enables you to receive jobs into inspection for stocked parent parts that have been defined as traceable, or that require inspection. You cannot deselect this option once WIP inspection references are in progress; you must complete all outstanding WIP inspection references. If a parent item is defined as traceable (but without inspection) then the item is not taken into inspection, regardless of your selection here.
This allows the capture of serial numbers for jobs requiring inspection only once the item is received into stock after the inspection phase. Otherwise you can capture serials at the time the item is received into inspection. You cannot deselect this option once WIP inspection references for serialized items are in progress (unless they are only for items that are serialized, but not traceable, and you are recording serial numbers during order entry). You can generate a report to identify the inspection references still be completed.
This allows the capture of lots numbers for jobs requiring inspection only once the item is received into stock after the inspection phase. Otherwise, you can capture lots at the time the item is received into inspection. You cannot deselect this option once WIP inspection references for traceable items are in progress. You can, however, generate a report to identify the inspection references that must still be completed.
This sets the Part Billings program to calculate the gross profit automatically when processing a completed job. The gross profit is the difference between the accumulated costs to date and the selling price of the job. You won't be able to part-bill the entire quantity using the Line details billing method if the job is set to complete (which is automatically done when the entire quantity is part-billed). In this case, you are forced to use the Selling price billing method.
This is the lowest percentage of gross profit that the system will accept if you require the Part Billings program to calculate the gross profit automatically. An entry of zero indicates that there is no low profit margin.
This is the highest percentage of gross profit that the system will accept if you require the Part Billings program to calculate the gross profit automatically. An entry of zero indicates that there is no high profit margin.
This is used to calculate the value of allocations required. The expected value of allocations is printed on the Job Status report to indicate any variance between the expected and actual issues.
This values material allocations to a job at the Bill of Materials cost.
This values material allocations to a job at the current inventory unit cost. Regardless of your selection here, the actual value of issues to the job is not affected.
This forces a valid entry at the Job classification field when adding jobs. You use this option (together with security access settings defined against your operators) to restrict the unauthorized processing of jobs and allocations (i.e. viewing, adding, changing, importing, canceling and posting).
This reserves stock for material allocations for confirmed jobs. Quantities are reserved at the time of confirming created jobs. The quantity reserved for allocations is taken into account in the various modules when calculating quantities available and quantities allocated.
This tracks lots from the components through to the parent part. This enables you to track which component lot numbers were used in the production of a particular parent lot (i.e. one-to-one tracking between component lots and parent item lots).
This tracks serials from the components through to the parent part. This enables you to track which component serial numbers were used in the production of a particular parent serial number. (i.e. one-to-one tracking between component serials and parent item serials).
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.
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 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 list view. 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. 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 Serial Entry for Receipts 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 an already existing stock code 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 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 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.
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
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).
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 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 any dangerous goods text held against a stock item being purchased as comment lines.
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 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.
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 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 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.
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
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.
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 pption 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 percentage or value that can automatically be cleared (99.99 if defined as a percentage and 999999999999.99 if defined as a value).
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 list view 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 (Post Activity). 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 the 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 indicates the description for the three user defined fields for Activities.
They default to
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.
This determines the tax applied to stocked order lines.
This uses the item's tax code.
This uses the tax code of the customer's area.
This uses the tax code of the customer's area (split into state, county and city rates - the total of which is used to calculate tax).
This uses the tax code against the postal/zip code (split into state, county and city - the total of which is used to calculate the sales tax).
This is the company's tax code file you intend using for the USA Tax by advanced geocodes or USA AVP sales tax system options.
This levies tax according to GST (federal level) and PST (provincial level). Most provinces charge PST besides GST, but some charge PST on GST. If you are also using Tax by geographic area, then a stock item with a blank tax code is interpreted as being exempt from tax and the tax code assigned to the geographic area when calculating tax for that item on an order is disregarded. Enabling this after defining your product classes requires you to create the _GST product class manually.
This levies tax on the supply of goods and services in Australia and on goods and services imported into Australia. It is essentially a value added tax (VAT) system where tax is paid at each step along the chain of transactions involving goods or services, until the end-user is reached. This is enabled when your nationality code is set to AUS.
This calculates tax using a third party system. Details captured are passed as XML to the query business object supplied by the designer of the third party tax system. This option only applies if you selected the USA tax by advanced geocodes or USA AVP sales tax system options.
Branch level integrates sales tax to General Ledger according to the branch code of the sale. The sales tax ledger account held against the AR branch is used for tax distribution. Tax code level integrates sales tax to General Ledger according to the ledger account held against each tax code. This does not apply to Canadian GST because GST is always integrated at branch level.
This calculates tax at the end of an invoice for each tax rate used in the invoice calculation. The taxable amount for each invoice line is accumulated and the tax is calculated for the total invoice amount to give the invoice level tax value.
This calculates tax for each line on an invoice before it is accumulated into a total invoice tax value. You must select this option if your nationality code is USA and you want sales order programs to calculate tax based on tax limits.
This calculates GST at the end of an invoice for each tax rate used in the invoice calculation.
This calculates GST for each line on an invoice before it is accumulated into a total invoice tax value.
This uses the period end dates defined for your General Ledger as the tax return periods for generating the Tax Return report (you will need to run the Tax Return Setup program). Otherwise you need to use the Tax Return Period Maintenance program to define the tax return period dates for the Tax Return report.
This enables you to define tax codes of up to 20 characters long to comply with legislation where tax codes longer than three characters are required. This option only applies when running SYSPRO in a SQL environment.
This allows you to reduce the taxable portion of lines by the settlement discount percentage for tax codes which are defined as inclusive (i.e. reduces the tax base by the terms discount prior to the tax being calculated). This option allows you to assume the discount is being taken prior to calculating tax. If any tax code is defined as inclusive, then you must select this option before you can reduce the taxable portion of merchandise, freight and miscellaneous charge lines.
This reduces the taxable portion of merchandise lines according to the settlement discount percentage, before tax is calculated.
This reduces the taxable portion of freight lines according to the settlement discount percentage, before tax is calculated.
This reduces the taxable portion of miscellaneous lines according to the settlement discount percentage, before tax is calculated.
This applies if you are using the Basic tax system or Tax by geographic area.
If using Tax by geographic area and a tax code exists for the geographic area, then that code is used (i.e. the codes defined here are only used if no corresponding tax code is held against the geographic area).
If you are using the USA tax by advanced geo codes or USA AVP sales tax system, then an entry in any of the Default sales tax code fields indicates that the default state of the corresponding line is taxable.
Assign a default tax code for miscellaneous charges or leave blank to default to non-taxable.
Assign a default tax code for freight charges or leave blank to default to non-taxable.
Assign a default tax code for non-stocked items or leave blank to default to non-taxable.
Assign a default tax code for credit notes or leave blank to default to non-taxable.
These options apply only to Sales (including Point of Sales) Quotations and Return Merchandise.
This rounds your tax and invoice values to the nearest monetary unit of your currency. Rounding occurs on the total tax amount and total invoice amount (i.e. values at line level are ignored).
The rounding values are output to _RND (for the document value) and _TAX (for the tax value).
This applies rounding to the total tax amount which is applied to the net invoice value. Tax rounding is typically only necessary if required by legislation in your country.
This applies rounding to the total invoice amount. You would typically use this if rounding is required because of the non-existence of small denomination coins (e.g. if the smallest denomination in your currency is 5, rather than 1 or 2). If you select to round both the tax value and the invoice value, then rounding is first applied to the tax value.
This applies tax and/or invoice rounding to invoices for foreign currency customers.
This rounds tax and/or invoice values up to your nearest currency unit (e.g. if rounding to the nearest 5 cents and the invoice value is 101.84, then the invoice value is rounded up to 101.85).
This rounds tax and/or invoice values down to your nearest currency unit (e.g. if rounding to the nearest 5 cents and the invoice value is 101.84, then the invoice value is rounded down to 101.80).
This rounds tax and/or invoice values to the nearest required value where 0-4 is down and 5-9 is up.
This applies tax rounding to all invoices produced from Sales Orders or Dispatch Notes.
This applies tax rounding only to invoices processed using the SO Counter Sales program.
This applies tax rounding only to invoices processed using the SO Counter Sales program, where the Payment type for AR is set to Cash for the Payment code used.
Enter the monetary or local unit of currency to which you want to round tax and invoice values.
For example:
If your smallest monetary unit of currency is 5 cents, then you would probably enter 5 in this field. If you are using the Point of Sale system, you may need to give change to customers. You can therefore not round invoices to a monetary unit that is less than the smallest coin available (e.g. you would not round to 1 or 2 cents if the smallest available coin is 5 cents).
This indicates that the purchaser is responsible for remitting the tax portion of the purchase to the tax office (i.e. the purchaser makes one payment to the supplier of the goods/services purchased and another payment to the tax office for the withholding tax portion of the transaction).
This calculates the value of withholding tax automatically at the time of making a payment in the Accounts Payable module (Taxable Amount * Withholding Tax Rate)/100). You should not select this option if you are disbursing tax over multiple general ledger tax accounts. For each invoice processed using the AP Invoice Posting program, the withholding tax system recognizes only the first tax code entered.
This calculates withholding tax when the actual invoice payment is made.
This calculates withholding tax when capturing the supplier invoice.
This applies withholding tax to foreign companies/suppliers only.
This applies withholding tax to local companies/suppliers only.
This applies withholding tax to an individual supplier. This can include contractors or consultants.
This bases the calculation on the fixed rate defined in the Withholding Tax Codes Maintenance program (currently only the Fixed rate is used, and is selected by default).
This is similar to tax brackets in which a different % is used depending on the amount (e.g. 0-1000 is 1%, 1001-9999 is 5%, etc.).
This is like a fixed rate, but if the amount is over a certain number (e.g. over 1 million) then an additional % tax is withheld."
This calculates withholding tax on the net invoice value (gross invoice value less tax and less QST if applicable) of the good or service.
This calculates withholding tax on the invoice amount less any trade discounts.
This is the type of transaction declared on the Supplementary Declaration (e.g. sales, acquisitions, goods sent for processing or free of charge goods). The Default nature of transaction codes options are disabled if you have not enabled the EC VAT system required setup option.
This is the default dispatch code (goods going to other EC Member States) for invoices.
This is the default dispatch code (goods going to other EC Member States) for credit notes.
This is the default code for arrivals (acquisitions).
This is the default three-character alphanumeric Incoterms code, denoting the terms of delivery. The Incoterms code indicates the portion of costs and risks agreed to by the parties in a contract of purchase or sale. For example, the Delivery term CIP (Carriage and Insurance Paid) indicates that the seller pays the cost of carriage and insurance necessary to bring the goods to a named destination (i.e. Shipping location).
This is the default Incoterms code for dispatches (goods going to other EC Member States) for invoices.
This is the default Incoterms code for dispatches (goods going to other EC Member States) for credit notes.
This is the default Incoterms code for arrivals (acquisitions).
This allows the entry of Delivery Terms and Shipping Locations into sales order/purchase order documents for customers/suppliers who are non-EC members. This option is not dependent on the EC VAT system required setting.
This uses a third party tax system for all calculations relating to order and line totals in Sales Order Entry and Point of Sale Entry. If the Business object is not found, then the SYSPRO tax calculation is used.
This is the name of the third party tax system.
This is the 6-character name of your query business object called to interface to the selected third party routine. This business object must take XML from SYSPRO, call the third party process and pass the results back to SYSPRO as XML. SORQT3.XML (located in the Base\Schemas folder) is provided as a sample XML instance to demonstrate the use of the Extended Tax Calculation Query Business Object provided. SORQT3OUT.XML is provided as a sample XML instance returned by the Extended Tax Calculation Query Business Object.
This is the 6-character name of the NetExpress program called to maintain information specific to the third party routine used. The program must reside in SYSPRO's Programs folder and is only used to define additional options (i.e. specific customer parameters required which do not form part of the core SYSPRO) which may be required by the third party tax system. These parameters are defined using the Third Party Setup function.
This is the default ship from fields required for non-stocked and miscellaneous lines.
This is the level of identification required by the tax process.
This determines whether this is a test company or a company that requires updates. If enabled, a flag is passed to the business object at the appropriate time to update the tax information in the third party system. Otherwise, the flag passed is always N.
This indicates how you want to distribute the taxable portion of a transaction processed in the AP Invoice Posting and AP Permanent Entries Posting programs.
This creates tax entries for each transaction processed, enabling you to print a detailed Tax Distribution Report.
This creates tax entries summarized for each journal, enabling you to generate a summary Tax Distribution Report.
This indicates you don't want to print a Tax Distribution Report.
This indicates that you want to use a two-tier tax system in conjunction with other tax systems available. It is applicable only to transactions posted within Accounts Payable against local suppliers and is calculated on the compounded amount (i.e. on the total amount after the initial tax, discounts, surcharges etc., have been calculated). This option is not available if you indicated that the Tax distribution method is not required.
This is the description that must be used as the default for all fields relating to second tier tax.
This calculates QST on the selling price inclusive of tax (i.e. selling price + tax). Otherwise, QST is calculated on the selling price only (i.e. selling price exclusive of tax). This option has no effect on the calculation of tax on settlement discount. QST on settlement discount is always calculated on tax, regardless of your selection at this option.
This calculates QST against foreign currency suppliers if you have enabled the Foreign currency suppliers tax entry option.
Multiple GL tax accounts distributes the total tax amount entered during AP Invoice Posting and AP Permanent Entries Posting to the AP tax ledger code defined against each of the tax codes that you intend using. You should not select this option if you selected to use the Withholding Tax system. Single GL tax account distributes the total tax amount entered to the Accounts Payable Input tax account.
This is the default tax code that must be used for tax distribution in the AP Invoice Posting and AP Permanent Entries Posting programs. If the EC VAT system is enabled and you select the Supplier default tax code required option, then the supplier's tax code is used instead of this default code.
This is the default tax code that must be used for second tier tax distribution in the AP Invoice Posting and AP Permanent Entries Posting programs.
This enables the Tax code and Tax amount fields when processing transactions for foreign currency suppliers in the AP Invoice Posting and AP Initial Invoice Capture programs.
This uses the tax code defined against the supplier when processing Accounts Payable invoices using the AP Invoice Posting and Browse on AP Permanent Entries programs. Otherwise the default code defined for invoice posting is used. The option is only available if the EC VAT system required option is enabled.
This requests the taxable portion of a non-zero discount amount when processing a payment using the AP Release Invoices to Pay by Review, AP Manual Check Entry, AP Void Checks or Payment Cycle Maintenance programs. The default value displayed in these programs is determined by the rate assigned to the entry made at the Default tax code field. In addition, you need to define the Settlement discount (tax) ledger code. You cannot select this option if the Withholding tax system is in use.
Current uses the current tax rate against the Default tax code or Default QST code to calculate the tax/QST on settlement discount.
Historical uses the invoice date of the transaction being paid to determine the tax rate to use for settlement discount.
This option only applies when the Request tax amount option is enabled.
This tax code is used to calculate the tax on settlement discount when processing a payment. The rate to use is determined by your selection at the Calculate tax using historical rates option. Historical uses the invoice date to ascertain the tax rate at that date. Current uses the current tax rate against the tax code. A valid default tax code must be entered if you want the value of tax on settlement discount to be printed on the Tax Return report.
This requests the second tier tax portion of a non-zero discount amount when processing a payment. The default tax value displayed in the payment programs is determined by the rate assigned to the entry made at the Default QST code field. In addition, you need to define the Settlement discount (QST) ledger code.
This is used to calculate the QST on settlement discount when processing a payment. The rate to use is determined by your selection at the Calculate tax using historical rates option. Historical uses the invoice date to ascertain the QST rate at that date. Current uses the current tax rate against the QST code.
This is the default tax code to which the tax amount must be posted in the AR Invoice Posting program when no tax integration is selected (i.e. when sales tax integration to General Ledger is not set to Branch level or Tax code level. If no tax code is entered, then tax code A is used, even if it has not been defined.
This is the default GST tax code to which the tax amount must be
posted in the AR Invoice Posting program when using the Basic tax
system. If left blank then the tax status of the transaction in
the AR Invoice Posting program is set to
This automatically calculates the taxable portion on adjustments and discount entries processed using the AR Payments and Adjustments program. You cannot select this option if the Withholding Tax system is enabled.
The tax rate assigned to this tax code is used to calculate the taxable portion of an adjustment or discount amount entered within the AR Payments and Adjustments program.
This disburses the taxable portion of an adjustment to the sales tax ledger code defined against the tax code during processing in the AR Payments and Adjustments program. If you don't select this option (or the sales tax ledger code assigned to the tax code is blank) then the taxable portion is disbursed to the Adjustment value (tax) GL control account. This option only applies if your sales tax integration to General Ledger is set to Tax code level.
This indicates how you want to distribute the taxable portion of a transaction processed in the Cash Book Deposits and Withdrawals and CB Permanent Entries Posting programs.
This creates entries for each transaction, enabling you to print a Tax Report for each transaction within a journal individually, as well as a breakdown at transaction level.
This creates entries for each journal, enabling you to print a Tax Report listing totals for each journal together with a breakdown at journal level.
This indicates the type of transactions (deposit, withdrawal or both) for which you want to distribute a taxable portion during processing in the Cash Book Deposits and Withdrawals and CB Permanent Entries Posting programs.
This either displays a warning or an error message when posting a Cash Book transaction exclusive of tax and there is a difference between the calculated tax and entered tax.
This is the default tax code for deposit transactions processed in the Cash Book Deposits and Withdrawals and CB Permanent Entries Posting programs.
This is the default tax code for withdrawal transactions processed in the Cash Book Deposits and Withdrawals and CB Permanent Entries Posting programs.
This sets the company's default tax status to taxable or non-taxable. If non-taxable, you will be unable to enter tax information for non-stocked lines in the Purchase Order Entry and Requisition Entry Maintenance programs.
This overrides the tax code assigned to stock items during processing in the Sales Order Entry program.
This uses the tax code held against an item when processing credit notes for stocked lines and the tax code held against the service charge when processing service charge lines (instead of the default tax code for credit notes). If no tax code is held against the stock item or the service charge, then the program defaults to using the default tax code for credit notes. Credit notes processed for non-stocked, miscellaneous and freight charge lines will use the default tax code for credit notes.
This reduces extended sales order line values by the tax amount, if the tax code is inclusive. You won't be able to access this option if the USA tax by advanced geocodes or the USA AVP sales tax system is enabled. The order values are reduced by the tax amount for the following reports: Dispatch Note Report, Order and Booking, Backlog by Stock code, Sales Order Backlog by Customer and Import Back Order Releases and the Order Intake Query query.
This indicates whether you want the system to perform checks on a customer's company tax registration number. Certain tax authorities require the customer's company tax registration number to be printed on an invoice. You can assign this number when setting up a customer or when maintaining the order header.
This requires the customer's company tax registration number to be captured before an invoice can be produced for the customer.
This requires the customer's company tax registration number to be captured before an order can be added using the Sales Order Entry program or before processing a point of sale entry using the Point of Sale Entry program.
This is the default tax code for taxable promotional transactions posted directly to a sales order as miscellaneous charge lines. The Descriptive tax code must be used if defined. If you are using tax by geographic area and against the area you select to use the tax code from the stock item, then the tax code entered here is used for trade promotions. If no tax code is defined here, then no tax is applied to trade promotions, regardless of the tax options defined against the geographic area.
This uses the same tax code applied to the merchandise line for its promotional miscellaneous charge line. This does not apply to a Global off invoice line. A Global off invoice line cannot be based on a merchandise line as it is derived from any number of merchandise lines that may have different stock codes. The system therefore uses the default tax/GST code. If blank, no tax is calculated.
This is the default GST tax code for taxable promotional transactions posted directly to a sales order as miscellaneous charge lines. The Descriptive tax code must be used, if defined. If you are using tax by geographic area and against the area you select to use the tax code from the stock item, then the tax code entered here is used for trade promotions. If no tax code is defined here, then no tax is applied to trade promotions, regardless of the tax options defined against the area.
This uses the same tax code applied to the merchandise line for its promotional miscellaneous charge line. This does not apply to a Global off-invoice line (which cannot be based on a merchandise line as it is derived from any number of merchandise lines that may have different stock codes). The system therefore uses the default tax/GST code. If blank, no tax is calculated.
This includes tax/GST in accrual promotions. You will need to enter a valid tax code and define the point at which accrual tax must be applied.
This is the default tax code for deductions and accrual promotions. The Descriptive tax code must be used, if defined. When processing an accrual promotion, the sales invoicing process calculates the tax portion of the transaction based on this code, and adds it to the promotion accrual amount. When you use the AR Payments and Adjustments program to process a deduction, the tax portion of the deduction is automatically calculated and posted according to the rate defined against this tax code.
This is the default GST tax code to use for deductions and accrual promotions. The Descriptive tax code must be used, if defined. When you process an accrual promotion, the sales invoicing process calculates the tax portion of the transaction based on the default GST tax code entered here and adds it to the promotion accrual amount. When you use the AR Payments and Adjustments program to process a deduction, the tax portion of the deduction is automatically calculated and posted according to the rate defined against this GST tax code.
This calculates tax against the promotion using the tax code defined against the promotion in Promotion Code. This option is enabled if you selected to add accrual tax at the time of review. It enables you to update existing promotion transactions and current promotion codes with the default deductions and accrual tax and GST codes.
This is the number of months for which you want to retain invoices with a zero balance. 99 retains this information indefinitely. Enter at least 3 if you are using multi-period accounting.
This is the number of months for which you want to retain expense journals. 99 retains this information indefinitely.
This is the number of months for which you want to retain details for payment cycles created using the Payment Cycle Maintenance program. The minimum retention period is six months. 99 retains this information indefinitely.
This is the number of months for which you want to retain tax distribution details for Accounts Payable transactions. This option is only displayed if you have enabled the EC VAT system (Setup Options). 99 retains this information indefinitely.
This is the number of months for which you want to retain expense distribution entries.
This is the number of General Ledger periods for which you want to keep your disbursement distribution entries created when you process payments for your suppliers (if Accounts Payable is integrated to General Ledger in summary or detail). 99 retains this information indefinitely. 0 (or if not integrated in summary or detail) deletes all disbursement distribution entries that have been printed when next you select to purge records.
This retains a detail record of each payment received from the customer. This information is stored for the number of months you are retaining payment history. These details can be printed on customer statements. You must select this option to be able to calculate the average number of days it takes a customer to pay invoices in full.
This determines the cut-off point for including paid invoices (i.e. zero balance invoices) in the average number of days to pay calculation. This is calculated for each customer as the total number of days taken to pay invoices divided by the total number of zero balance invoices. If you change this entry, then you must run the Balance function of the AR Period End program to recalculate the average number of days to pay against all customers.
If purging customer sales movements by date, then this refers to the maximum number of days that movement records will be retained. If purging by number, then this is the maximum number of movement records that will be retained. 99999 retains this information indefinitely. 0 removes all movement records for all customers at month end.
This is the number of months for which you want to retain zero balance invoices. The minimum is one month. This option does not apply to consolidated invoices. Zero balance consolidated invoices are deleted by the month end routine of the AR Period End program when their balance is zero for the current and previous two periods.
This is the number of months for which you want to retain cash journals. The minimum is one month. This determines the number of months for which you can reprint the AR Cash Journal and AR Payments Distribution reports.
This is the number of months for which you want to retain payment history. The minimum number is one month. Payment history is retained only if you are retaining payment details.
This is the number of months for which you want to retain sales transaction summary records. The minimum is one month. This determines the number of months for which you can reprint the AR Sales Distribution and AR Invoice Register reports.
This is the number of months for which you want to retain sales transaction detail records. The minimum is one month. This determines the number of months for which you can reprint theAR Sales Distribution and AR Invoice Register reports.
This is the number of months for which you want to retain discount credit note detail records. The minimum is one month.
This is the number of months for which you want to retain discount debit note detail records. The minimum is one month.
This is the number of months for which you want to retain details for the payment runs created using the AR Payment Run program. This includes cancelled and closed collector runs associated with the payment run.
This indicates the number of months for which you want to retain customer complaint history. The minimum is one month.
This is the number of periods for which you want to retain your Receivables sales distribution entries. When these records have been held on file longer than the number of periods specified here, they are deleted when you run the Purge function of the AR Period End program. The number of periods specified here also determines the number of periods for which you can reprint ledger distribution entries using the AR Sales Distribution program. 99 retains this information indefinitely.
This is the number of periods for which you want to retain your Receivables payments distribution entries. When these records have been held on file longer than the number of periods specified here, they are deleted when you run the Purge function of the AR Period End program. The number of periods specified here also determines the number of periods for which you can reprint ledger distribution entries using the AR Payments Distribution program. 99 retains this information indefinitely.
These options enable you define the number of periods for which you want to keep asset information. The minimum is 24 periods.
This is the number of periods for which you want to retain your Assets Register GL distribution entries. When these records have been held on file longer than the number of periods specified here, they are deleted when you run the Purge function of the Asset Period End program. The number of periods specified here also determines the number of periods for which you can reprint ledger distribution entries using the Asset Distribution program. 99 retains this information indefinitely.
This is the number of periods for which you want to retain entries for assets that have been disposed of using the 'Asset Disposal' program. When records have been held on file longer than the number of periods specified here, they are deleted when you run the Purge function of the Asset Period End program. It also determines the number of periods for which you can view asset information on disposed assets using the Asset Query and Asset List of Disposals programs. 99 retains this information indefinitely.
This is the number of periods for which you want to retain Assets Register transactions processed using the Asset Transactions program. When entry records have been held on file longer than the number of periods specified here, they are deleted when running the Purge function of the Asset Period End program. 99 retains this information indefinitely.
This is the number of periods for which you want to retain a record of capex items that are in a status of Closed. 99 retains this information indefinitely. Items are deleted when next you purge records using the Asset Period End program providing the current Assets period and all capex lines for the item are in a status of Closed.
This is the number of periods for which you want to retain a record of capex requisitions lines in a status of Closed. This cannot exceed the number of periods for which you want to retain capex items. 99 retains this information indefinitely. Lines are deleted when next you purge records using the Asset Period End program providing the capex line is not linked to a requisition, purchase order or job that has not yet been purged; and there is no asset in suspense for the capex line.
This is the number of periods for which you want to retain book value asset entries. The minimum is 24 periods.
This is the number of periods for which you want to retain taxation valuation asset entries. 00 indicates that no entries must be retained. If the Basis for depreciation for Tax value is set to Period or Year, then you must retain tax valuation entries for at least 24 periods.
This is the number of periods for which you want to retain alternate value asset register entries. 00 indicates that no entries must be retained. If the Basis for depreciation for an Alternate value is set to Period or Year, then you must retain tax valuation entries for at least 24 periods for that alternate valuation.
This is the number of years that you want to retain Assets history (i.e. the summary records of the transactions processed against your assets). Records are deleted by the Purge function of the Asset Period End program when the cut-off time is reached. The number of years specified here also determines the number of years for which you can view asset history using the Asset Query program. 99 retains this information indefinitely. 00 indicates that no history must be retained.
These fields enable you to define the length of time you want to retain Cash Book information. The minimum number of months you can retain this information is one month (i.e. you cannot delete any information until after at least one month end).
This is the number of months for which you want to retain your Cash Book journals. This determines the number of months for which you can reprint the Cash Book Journal and the Cash Book Distribution Report report. 99 retains this information indefinitely. These journals are deleted when next you use the Purge function of the Cash Book Period End program.
This is the number of months for which you want to retain reconciled transactions. 99 retains this information indefinitely. These transactions are deleted when next you run the Purge function of the Cash Book Period End program. You should retain reconciled transactions for a minimum of three months so that they can be unreconciled in Previous period 1 or 2, if required.
These options enable you to indicate the number of months for which you want to keep EFT data on file. 99 retains information forever (i.e. it is not deleted when the EFT Purge program is run).
This is the number of months for which you want to retain extracted EFT batches. These batches are created by the EFT Payments Extract program.
This is the number of months for which you want to retain audit of extracted EFT batches. These batches are created by the EFT Payments Extract program.
This is the number of months for which you want to retain audit of voided EFT entries records. These entries are created by the EFT Payments Extract and AP Void Checks programs.
This indicates the number of months for which you want to retain details of EFT beneficiaries. These beneficiaries are created by the EFT Cash Book Beneficiaries program.
This is the number of years for which you want to retain summary history of balances (a minimum of 1). This affects the number of prior years for which you can report on summary balances. Balance history and alternate currency history for the current company is deleted when next you run the Purge function of the GL Period End program.
This is the number of years for which you want to retain detail transaction history (a minimum of 1). This affects the number of prior years for which you can report on detail transactions. Detail transaction history and alternate currency detail for the current company is deleted when next you run the Purge function of the GL Period End program. Analysis entries associated with deleted transactions are also removed.
This is the number of periods for which you want to retain cancelled and posted journals (a minimum of 1). This affects the number of prior periods for which you can report on posted journals. Cancelled and posted journals that have been printed are deleted when next you run the Purge function of the GL Period End program. Any notes associated with the deleted journals are also removed.
This is the number of periods for which you want to retain expired recurring journals. Expired recurring journals are deleted when next you run the Purge function of the GL Period End program. Any notes associated with the deleted journals are also removed.
This is the number of periods for which you want to retain cancelled and posted group entries (a minimum of 1). These are deleted when next you run the Purge function of the GL Period End program. This affects the number of prior periods for which you can report on posted group entries (Group entries only apply to versions of SYSPRO prior to SYSPRO 6.1).
This includes the value of stock that has been sold in sales history quantities (but not the value of stock that has been issued).
This includes the value of stock that has been issued in sales history quantities (but not the value of stock that has been sold).
This includes both.
This is the number of months for which you want to retain your Inventory journals (a minimum of 1). This affects the number of months for which you can reprint the Inventory Journal and Inventory Distribution reports. 99 retains journals indefinitely. These journals are deleted when next you run the Purge function of the Inventory Period End program, if they meet all the criteria for deletion.
This is the number of months for which you want to retain inventory documents (i.e. inventory receipts, issues, transfers out and purchase order receipts). 99 retains these documents indefinitely. Printed inventory documents are deleted when next you run the Purge function of the Inventory Period End program, if they meet all the criteria for deletion.
This is the number of days for which you want to retain cycle counts.
This is the number of ledger periods for which you want to retain completed goods in transit detail lines (a minimum of 3 months). This is only enabled if you are using the full goods in transit transfers facility. 99 retains these entries indefinitely. Completed goods in transit detail lines are deleted when next you run the Purge function of the Inventory Period End program if they meet all the criteria for deletion.
This is the cut-off number of records/days for which you want to retain each stock code/warehouse combination. 99999 retains records indefinitely. 0 deletes all movement records when next you run the Purge function of the Inventory Period End program.
This enables you to print a Kardex Report; print an Inventory Valuation report for previous month 1 and 2; and post adjustments, bin transfers and expense issues to a previous posting month.
This retains a history of all changes made to the price or the price basis of an item. This information can be printed using the Inventory Price History program. If you are allowing blank price list codes then capturing a stock item without associating it to a price code will result in no price history being created for that item.
This is the number of days/months for which you want to retain a history of changes made to the selling price or the price basis of an item. 999 retains this information indefinitely. 0 deletes all price history records dated prior to when you ran the Purge function of the Inventory Period End program. Price history data is deleted by the Purge function of the Inventory Period End program when the number of days or months for which you are retaining this information is exceeded.
This takes the values entered at the Number of days to retain price history and the Days to retain zero quantity buckets to represent months instead of days.
This is the number of days/months for which you want to retain FIFO buckets with a zero quantity. 9999 retains this information indefinitely. FIFO buckets are deleted when next you run the Balance function of the Inventory Period End program if they have a zero qty on hand and the number of days/months between the current company date and the bucket's last issue date is greater than the days/months specified here.
This indicates the last five year end dates for the Inventory module.
This records each purchase order receipt in a special receipts file, enabling you to produce a supplier performance report.
This enables you to designate as ready for archiving, shipments that include items in inspection, items not yet received into stock and items with no invoice number. These selections are made at the Incomplete Shipment Options function within the Shipment Archiving program which is displayed only if you are allowing incomplete shipment lines to be designated as ready for archiving.
This enables you to remove completed purchase order lines when you run the Purchase Order Purge program. Regardless of the number of days you are retaining completed purchase orders, completed order lines are deleted if you select the Remove completed lines option within the Purchase Order Purge program.
This is the maximum number of days for which records must be retained, or the maximum number of records that must be retained before the history of receipts file is purged.
This is the number of months for which you want to retain matched GRNs before the GRN Purge program deletes them. This option is only available if you have enabled the GRN suspense system.
This is the number of days/months after a shipment has been received into stock, that it can be archived. To reduce the size of live Landed Cost Tracking shipment tracking files, the Shipment Archiving program removes any completed shipments in the Landed Cost Tracking system and archives them for later retrieval and reporting.
This is the number of days/months for which you want to retain GRN price variances. 999 retains GRN price variances indefinitely.
This is the number of days/months after a shipment has been archived, that it can be deleted. 999 retains archived shipments indefinitely.
This is the number of days/months for which you want to retain GRN journals. This determines the number of months for which you can reprint the GRN Journal Report ad the GRN Distribution reports. 999 retains GRN journals indefinitely. GRN journals are purged only if they have been printed.
This represents the values entered for the Retention periods fields in months instead of days.
This is the number of days for which you want to retain completed purchase orders before they are deleted by the Purchase Order Purge program. 0 deletes purchase orders when they are complete. 99999 retains purchase orders indefinitely. Completed order lines are deleted only if you enable the Remove completed lines option within the Purchase Order Purge program.
This is the number of days for which you want to retain requisition lines. 9999 retains requisition lines indefinitely. The Requisition Purge program automatically removes cancelled requisitions, as well as any confirmed requisition lines that have exceeded the number of days specified here, based on your selections in the Requisition Purge program.
This is the number of days for which you want to retain completed Blanket Purchase Order contracts. 99999 retains BPO contracts indefinitely. The Blanket Purchase Order Purge program uses the number of days entered here to determine whether completed and expired BPO contracts can be purged. This does not apply to cancelled BPO contracts, as these are purged whenever you run the Blanket Purchase Order Purge program.
This is the number of days for which you want to retain requests for quotes. 99999 retains requests for quotes indefinitely.
This is the number of days for which you want to retain completed returns to supplier. 99999 retains completed returns to suppliers indefinitely.
This is the number of days for which you want to retain completed RMAs. '9999' retains records indefinitely. The RMA Purge program automatically removes completed RMAs that exceed the number of days specified here, based on your selections in the RMA Purge program.
This is the number of years for which you want to retain detailed sales history. The Sales Analysis Update program uses this information to determine the cut-off date according to which information is deleted. 99 retains your Detailed sales history indefinitely (i.e. these records are ignored by the Purge function of the Sales Analysis Update program).
This is the number of years for which you want to retain summary sales history. The Sales Analysis Update program uses this information to determine the cut-off date according to which information is deleted. 99 retains your Summary sales history indefinitely (i.e. these records are ignored by the Purge function of the Sales Analysis Update program).
This is the number of years for which you want to keep Archived sales history data. The Sales Analysis Update program uses this information to determine the cut-off date according to which information is deleted. 99 retains your Archive sales history indefinitely (i.e. these records are ignored by the Purge function of the Sales Analysis Update program).
This is the number of months for which you want to retain sales commission data on file (a minimum of one month). 99 retains records indefinitely (i.e. these records are ignored by the Purge function of the Sales Analysis Update program).
This is the number of months for which you want to retain sales tax details on file (a minimum of 1). 99 retains records indefinitely (i.e. these records are ignored by the Purge function of the Sales Analysis Update program).
This is the number of months for which you want to keep GST tax details on file (a minimum of 1). 99 retains records indefinitely (i.e. these records are ignored by the Purge function of the Sales Analysis Update program). GST records can only be purged by the Sales Analysis Update program if they have been printed using the GST Report by Entry or GST Report by Area programs.
This is the number of months for which you want to keep EC tax details on file. The GL Global Tax Report uses this to delete tax distribution details where the current ledger period and year exceeds the year and month of submission against the tax distribution record by more than the number of months specified here. It is also used by the Purge function of the Sales Analysis Update program to delete records from the Sales Analysis EC VAT Sales table/file.
This is the number of days/months for which you want to retain the invoice, dispatch invoice and consolidated dispatch invoice reprint files. These records are deleted when you run the Order Purge program and the number of days/moths specified here is exceeded. 999 retains records indefinitely. 0 deletes all records when next you run the Order Purge program.
This is the number of days/months for which you want to retain delivery performance records, which are created if the Generate customer delivery performance file Sales Order configuration option is selected. These records are deleted when you run the Order Purge program and the number of days/months specified here is exceeded. 999 retains records indefinitely. 0 deletes all records when next you run the Order Purge program.
This is the number of days/months for which you want to retain order analysis records. These records are deleted when you run the Order Purge program and the number of days/months specified here is exceeded. 999 retains records indefinitely. 0 deletes all records when next you run the Order Purge program.
This is the number of days/months for which you want to retain sales orders that are complete (i.e. orders in a status of 9). These records are deleted when you run the Order Purge program and the number of days/months specified here is exceeded. 999 retains records indefinitely. 0 deletes all completed sales orders that are dated prior to the date on which the Order Purge program is run.
This is the number of days/months for which you want to retain completed dispatch notes. These records are deleted when you run the Order Purge program and the number of days/months specified here is exceeded. 999 indicates that you want to retain records indefinitely. 0 deletes all completed dispatch notes dated prior to the date on which the Order Purge program is run.
This represents values entered for the Number of days to retain options in months instead of days.
This removes completed stocked, non-stocked, freight and miscellaneous order lines from file when next the Order Purge program is run. This option relates only to incomplete orders (i.e. orders not in a status of 9). When an order is complete, its detail lines are purged at the same time the order is deleted (i.e. when the number of days/months to retain completed orders is exceeded).
This archives completed sales orders when next the Order Purge program is run. Orders are selected for archiving only when they exceed the number of days/months for which you are retaining completed sales orders.
This is the maximum number of sales orders that must be saved in a single archive file. 9999 indicates an unlimited number of sales orders can be archived into a single file. When sales orders are archived using the Order Purge program and the number of sales orders to archive exceeds the number specified here, then more than one archive file is created. If you process a large number of sales orders, then you can define a value in this field to keep your archive files to a manageable size.
This is the number of days for which you want to retain details of promotions that have expired. The validity dates for a promotion are defined against its promotion code.
This retains scrap analysis records indefinitely. Otherwise these records are deleted according to the cut-off date entered when running any WIP Period End program function that includes a purge option.
This retains non-productive analysis records indefinitely. Otherwise these records are deleted according to the cut-off date entered when running any WIP Period End program function that includes a purge option.
This is the number of months for which you want to retain your labor journals (a minimum of one month). It determines the cut-off date according to which labor posting journals are deleted when running any WIP Period End program function which includes a purge option and also the number of months for which you can reprint the WIP Labor Journal and WIP Labor Distribution.
This is the number of months for which you want to retain your part billing journals (a minimum of one month). It determines the cut-off date according to which part billing journals are deleted when running any WIP Period End program function that includes a purge option and the number of months for which you can reprint the WIP Part Billings Journal and WIP Part Billings Distribution.
This is the number of months for which you want to retain your job amendment journals after a job is completed (a minimum of one month). It determines the cut-off date according to which job amendment journals are deleted when running any WIP Period End program function which includes a purge option. 99 retains the journals indefinitely.
This is the number of periods for which you want to retain your labor distribution entries. When these records have been held on file longer than the number of periods specified here, they are deleted when you run the Purge function of the WIP Period End program. The number of periods specified here also determines the number of periods for which you can reprint ledger distribution entries using the WIP Labor Distribution program. 99 retains this information indefinitely.
This is the number of periods for which you want to retain your part billing distribution entries. When these records have been held on file longer than the number of periods specified here, they are deleted when you run the Purge function of the WIP Period End program. The number of periods specified here also determines the number of periods for which you can reprint ledger distribution entries using the WIP Part Billings Distribution program. 99 retains this information indefinitely.
This allows the system to determine the cut-off date according to which completed jobs must be purged from the system. It prevents operators from specifying a cut-off date in the WIP Period End program. The cut-off date is calculated as the system date aged by the number of days specified at the Number of days field. Completed jobs are deleted only if the value of the job is zero for the current and previous two months.
This is the number of days to use to calculate the cut-off date for completed jobs.
This enables you to archive completed jobs during the purge routine of the WIP Period End program. For all completed jobs that qualify for purging from the system, header details are copied to a work in progress archive file. Archived jobs can be viewed in the WIP Query program.
This additionally archives all the transactions that were posted against a job.
Wording you assign to these fields is displayed in entry/display forms in the Suppliers program.
Specify your own wording for this supplier field. This field allows you to store any extra information you require for the supplier (e.g. this field could hold the full description of the Supplier Class code).
Specify your own wording for this supplier field (e.g. this field could store a value to use in calculations performed in the Report Writer module.
Wording you assign to these fields is displayed in entry/display forms. User-defined fields are defined against each customer. These captions are also used in Contact Management.
Assign your own wording to this customer field. This is a text field held against the customer that can contain any information you require. The wording defined here is also used in the Contact Management System.
Assign your own wording to this customer field. This is a numeric field held against the customer that can contain any information you require. The wording defined here is also used in the Contact Management System.
These selections are specifically for use with the Number of days fixed invoice terms option which enables you to define your own ageing buckets. When customer accounts are configured to use user-defined ageing buckets, you can add up to two custom form fields against these customers, enabling you to filter reports based on the ageing buckets defined.
Use this to filter customers for inclusion in Accounts Receivable reports. The values displayed in the drop down are the caption names of the custom form fields you added to your customers.
Use this to filter customers for inclusion in Accounts Receivable reports. The values displayed in the drop down are the caption names of the custom form fields you added to your customers.
Wording you assign to these fields is displayed in entry/display forms.
Assign your own wording for these alternate valuation fields. The wording you enter is used instead of the default Alternate Valuation wording in the Assets programs.
This indicates the default wording that you want to display for the first EFT user-defined field in the Accounts Payable module. If you leave this field blank, then the default wording EFT User 1 is used.
This indicates the default wording that you want to display for the second EFT user-defined field in the Accounts Payable module. If you leave this field blank, then the default wording EFT User 2 is used.
This indicates the default wording that you want to display for the first EFT user-defined field in the Cash Book module. If you leave this field blank, then the default wording EFT User 1 is used.
This indicates the default wording that you want to display for the second EFT user-defined field in the Cash Book module. If you leave this field blank, then the default wording EFT User 2 is used.
The caption for this field is defined using the Accounts Receivable User-defined Fields form and is displayed here for information purposes only. Its usage is the same as that applied to customers.
The caption for this field is defined using the Accounts Receivable User-defined Fields form and is displayed here for information purposes only. Its usage is the same as that applied to customers
Assign your own wording for this user-defined Account field. You enter the required information for this field using the Accounts program.
Assign your own wording for this user-defined Account field. You enter the required information for this field using the Accounts program.
Assign your own wording for this user-defined Account field. You enter the required information for this field using the Accounts program.
Assign a description to the first user-defined field that can be accessed at the time of creating a dispatch note. The wording assigned to the field is displayed within a number of Dispatch Note programs.
Assign a description to the second user-defined field that can be accessed at the time of creating a dispatch note. The wording assigned to the field is displayed within a number of Dispatch Note programs.
Assign your own descriptions for these additional stock code fields that can be configured within the Browse on Stock Codes program. The fields can be used to store any extra information you require for the stock item.
Assign your own description for these additional warehouse fields that can be configured when using the Inventory Warehouses for Stock Codes program to maintain warehouse details for stock items. The fields can be used to store any extra warehouse information you require for the stock item.
Assign your own description for alternate keys. The fields can be used to change the sequence in which you want to browse on stock codes.
Assign the prompt wording that must be displayed for the user-defined field that appears on the RMA header.
This indicates that an entry must be made at this field when issuing an RMA.
Assign the wording that must be displayed for the first user-defined field that appears on the RMA detail line.
This indicates that an entry must be made at this field when issuing an RMA.
Assign the wording that must be displayed for the second user-defined field that appears on the RMA detail line.
This indicates that an entry must be made at this field when issuing an RMA.
Assign your own wording to a user defined field that can be accessed for each order line entered. This field is accessed within the Extra function of the Sales Order Entry program.
Assign your own wording for these user-defined fields displayed in the Browse on Element Descriptors program. Element descriptors are assigned to stock items to establish their recovery costs at points of transition in the purchase, manufacturing and sales cycle.
Assign the wording you want to display for the Revision, Release, Rev and Rel fields throughout the system. Leave blank to default to the original wording displayed for the fields.
This uses as the invoice number either the next available auto voucher number, or the supplier's delivery note number, or the Goods received note number, or the purchase order number. If the delivery note, GRN or purchase order is defined with a presentation length that is more than 15 characters, then that numbering method is disabled.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
If you have selected a key type that can be prefixed, then this indicates the length of the prefix required. If the prefix is zero, then the prefix length is dynamic and is determined by the number of characters you define in the prefix.
This generates invoice, credit and debit note numbers at company level and the branch associated with the transaction has no bearing on the document number.
This generates invoice, credit and debit note numbers from the AR branch associated with the transaction. If the AR Invoice number key type is set to alphanumeric, then you can assign a single character as a prefix to the document numbers generated by each branch. This enables you to identify the branch that generated the document.
This is the next invoice number that will be used if automatic numbering is defined. Numbers are allocated up front and incremented during processing. Note: Cancelling or rolling back a transaction does not de-allocate this number and will result in gaps in the numbering sequence as the allocated number is not re-used.
This is the next credit note number that will be used if automatic numbering is defined. Numbers are allocated up front and incremented during processing. Note: Cancelling or rolling back a transaction does not de-allocate this number and will result in gaps in the numbering sequence as the allocated number is not re-used.
This is the next debit note number that will be used if automatic numbering is defined. Numbers are allocated up front and incremented during processing.
Cancelling or rolling back a transaction does not de-allocate this number and will result in gaps in the numbering sequence as the allocated number is not re-used.
This allocates the order number as the invoice number for the first invoice generated for the order. Subsequent invoices for the order assigns the next invoice number based on the invoice numbering method defined. You can't select this if the Auto invoice numbering - order release option is set to Use delivery note. Don't select this if you intend to part-ship goods (where more than one invoice will be produced for one sales order) as this may result in missing invoice numbers.
This lets you use the same invoice number for different customers within a SYSPRO company when processing invoices, regardless of your order or invoice numbering methods.
If you chose the Same invoice for different customers option, then this lets you delete the invoice cross reference table and rebuild it.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This allocates the next customer code automatically when you add a new customer.
This lets you assign a unique code to identify a new customer added.
This assigns the next code automatically when you add a new customer, based on a user-defined script (i.e. you can use the VBScript Editor to build a unique code for each new customer added).
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This allocates the next supplier code automatically when you add a new supplier.
This lets you assign a unique code to identify a new supplier added.
This assigns the next code automatically when you add a new supplier, based on a user-defined script (i.e. you can use the VBScript Editor to build a unique code for each new supplier added).
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This generates delivery note numbers using the entry made at the Next delivery note field.
This generates delivery note numbers based on the numbering defined for the branch associated with the sale.
This generates delivery note numbers based on the numbering defined for the branch, together with a prefix that can assist in identifying the branch that generated the document.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This is a 15-digit number incremented with each new pick.
This is a 5-digit number incremented with each new pick and prefixed by the original sales order from which it originated.
This is a 5-digit number incremented with each new pick and prefixed by the date (in CCYYMMDD format) the pick was created.
This is a 5-digit number incremented with each new pick and prefixed by the warehouse of the first picking line and the date (in YYMMDD format) when the pick was created.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
If you have selected a key type that can be prefixed, then this indicates the length of the prefix required. If the prefix is zero, then the prefix length is dynamic and is determined by the number of characters you define in the prefix.
This lets you assign an RMA number whenever merchandise is returned from a customer.
This allocates the next RMA number automatically according to your entry at the Next RMA number field when merchandise is returned from a customer.
This allocates the next RMA number held against the branch when merchandise is returned from a customer.
This allocates the next RMA number and prefix from the branch when merchandise is returned from a customer.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
If you have selected a key type that can be prefixed, then this indicates the length of the prefix required. If the prefix is zero, then the prefix length is dynamic and is determined by the number of characters you define in the prefix.
This lets you assign a unique number when you add an order.
This allocates the next number automatically when you add an order.
This allocates the next order number automatically using the numbering against the branch linked to the sale. If your order key type is alphanumeric, then you can assign a single character as a prefix to the document numbers generated by each branch. This helps you identify the branch that generated the document.
This is the next sales order number that the system will use if order numbers are being generated at company level.
This is the next credit note number that the system will use if order numbers are generated at company level. The number must be in the range 800000 to 899999. The number of characters will depend on the presentation length selected.
This is the next debit note number that the system will use if order numbers are generated at company level. The number must be in the range 900000 to 999999. The number of characters will depend on the presentation length selected.
This assigns the next order number to a supply chain transfer order according to the numbering method of the branch assigned to the source warehouse. Otherwise the numbering method of the branch assigned to the target warehouse determines the next order number assigned to a supply chain transfer order.
This assigns an invoice number automatically when you release an order. The number allocated to the first invoice generated for the order is the order number providing you enabled the Sales order moved to invoice setup option. Otherwise it is the next invoice number by branch or by company based on the AR invoice numbering method defined.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
If you have selected a key type that can be prefixed, then this indicates the length of the prefix required. If the prefix is zero, then the prefix length is dynamic and is determined by the number of characters you define in the prefix.
This indicates how you want to allocate GRN numbers for purchase order receipts (i.e. automatic, manual, by warehouse, by warehouse with prefix, by branch and by branch with prefix).
This generates a new GRN number for each stock item receipted using the Purchase Order Receipts program. If any item on the purchase order requires inspection or is traceable, then a new GRN number is assigned to each line, regardless of whether this option has been enabled.
This produces a GRN number per line when using the Receipt All function in the Purchase Order Receipts program. Otherwise the Receipt All function generates a single GRN number for all lines. If any item on the purchase order requires inspection or is traceable, then a new GRN number is assigned to each line, regardless of whether this option has been enabled.
Select this to assign a GRN number to each new shipment received into stock using the Landed Cost Tracking system.
This forces GRN numbers to be unique, regardless of the supplier. You will need to create a GRN master file using the Reindex Files program to ensure that duplicate GRN numbers are not created.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
If you have selected a key type that can be prefixed, then this indicates the length of the prefix required. If the prefix is zero, then the prefix length is dynamic and is determined by the number of characters you define in the prefix.
This indicates how you want to allocate numbers when capturing purchase orders (i.e. automatic, manual, by warehouse, by warehouse with prefix, by branch and by branch with prefix).
If by Warehouse or Branch ensure that you assign a unique range of numbers for each warehouse (or branch) to avoid duplicating purchase order numbers.
If by Prefixed warehouse or Prefixed branch ensure that the prefix is unique in order to avoid duplicate keys, which would prevent SYSPRO from allocating the next number.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
Manual lets you assign a unique number for each RFQ. Automatic allocates the next RFQ number automatically.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
If you have selected a key type that can be prefixed, then this indicates the length of the prefix required. If the prefix is zero, then the prefix length is dynamic and is determined by the number of characters you define in the prefix.
This lets you assign a unique GIT Reference number whenever you process an inter-warehouse or supply chain transfer of goods.
This allocates the next GIT Reference number automatically.
This allocates the next GIT Reference number according to the numbering method defined against the source warehouse.
This allocates the next GIT Reference according to the numbering method defined against the source warehouse, together with a two character prefix.
This is the number that will be assigned to the next document printed to record the receipt into stock of an item using the Inventory Movements program. This number is assigned only if the option to generate the next document number is enabled for your Stock receipts document format.
This is the number that will be assigned to the next document printed to record the issue of items for miscellaneous purposes using the Inventory Movements program. This number is assigned only if the option to generate the next document number is enabled for your Issue document format.
This is the number that will be used for the next inspection document to be printed. This number is automatically updated by the system each time you print a new inspection document using the Purchase Order Inspection program.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This sets the lot number to be the same as the job number when processing transactions in the Job Receipts program. Both your lot and job number key types must be the same (i.e. either both must be numeric, or both must be alphanumeric). This option is only applied to co-products if the Use same lot on multiple stock codes option is enabled.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This lets you create ranges of manual serial numbers that are sequential within the company - created according to the prefix and suffix defined against the company (the combined prefix and suffix cannot exceed 20 characters).
This lets you track the last serial number range created for a specific stock code (you define the prefix and next suffix against each individual stock item).
This is the character(s) that must form the start of the serial number when you add a range of manual serial numbers within this company.
This number is appended to the prefix and together they form the serial number. The system automatically increments the next suffix for each new serial number created in the range, providing the number was created using the prefix. The number of numeric characters entered for the suffix must cater for the total quantity of serial numbers you want to add using the defined prefix.
For example:
A suffix of 1 character will allow 9 serials to be added for the prefix you defined.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
This lets you assign a unique code to identify a new stock item added.
This allocates the next code automatically when you add a new stock code (for numeric key types only).
This assigns the next code automatically when you add a new stock item, based on a user-defined script (i.e. you can use the VBScript Editor to build a unique code for each new stock item added).
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This lets you automatically increment the last release of an item when you go back a revision when updating the revision/release of an item.
Your selection here is ignored when stock control is not at release level and release numbering is not automatic. This is also dependent on the option Allow non-sequential entries.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This lets you apply a revision/release that is smaller than the one when you apply a new revision/release through an ECO. This option only applies to the revision and not the tracked release when the Track release option is enabled. Typically, you would set up the revision to refer to a specific location or status and the release to be incremental. It would then be necessary in each design change for an ECC-controlled item to enter a revision that does not occur after the previous revision.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
If you have selected a key type that can be prefixed, then this indicates the length of the prefix required. If the prefix is zero, then the prefix length is dynamic and is determined by the number of characters you define in the prefix.
This lets you assign a unique code to identify a new job added.
This allocates the next job number automatically when you add a job.
This numbers your jobs automatically according to the classification assigned at the time of capturing the job.
This assigns the next job number automatically when you add a new job (Job Entry program only) based on a user-defined script (i.e. you can use the VBScript Editor to build a unique code for each new job number added).
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This automatically converts alphabetic characters in the key to uppercase.
This automatically converts any alphabetic characters in the key to lowercase.
This caters for both upper and lowercase characters (i.e. no conversion is performed). This conversion capability is supported in all forms, toolbars and data grids and applies to alphanumeric key types.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
If you have selected a key type that can be prefixed, then this indicates the length of the prefix required. If the prefix is zero, then the prefix length is dynamic and is determined by the number of characters you define in the prefix.
This allows for both alphabetic and numeric characters. Data is left-aligned with trailing blanks.
This only allows the entry of numeric characters (i.e. 0-9). Data is right-aligned with preceding zeros.
This suppresses the display of zeros that appear before the numeric key.
This restricts the number of characters that can be entered or displayed in a key field.
If you have selected a key type that can be prefixed, then this indicates the length of the prefix required. If the prefix is zero, then the prefix length is dynamic and is determined by the number of characters you define in the prefix.
This lets you assign a unique WIP inspection number at the time of receiving items into inspection.
This allocates the next available WIP inspection number automatically.
This numbers WIP inspections by job class.
This can be used to describe the company, although it is not used by the system or printed.
These address details can be printed on any free-format stationery.
These address details indicate the company's physical address to which goods must be delivered (used by the Purchase Orders module).
This indicates the geographic location of the address in terms of longitude and latitude. It includes a hyperlink to the map directions. An additional hyperlink is available (Resolve GeoLocation from address) to resolve addresses using the long or short name.
This indicates the code page of the company's data and is applicable when using the BULK INSERT function and special characters exist that SQL Server needs to recognize.
This is the company's tax registration number that can be printed on delivery notes, invoices, statements and purchase orders.
This company registration number can only be printed on delivery notes, invoices, statements, creditor's remittance advices and purchase order requisitions.
This is the warehouse displayed as the default at most warehouse fields in the system. Specifying a default warehouse is useful if you are only using one warehouse in the system and do not want to have to re-enter the code repeatedly. You can override the default warehouse at operator level. Whenever you add or change the default company warehouse, you need to restart SYSPRO for your changes to become effective.
This is the default currency in which you want to process transactions within the system. You cannot change this currency once you have added the company.
This is the description for the Local currency code assigned to the company.
This is typically determined by the frequency of a company's financial and management reporting cycles. It also affects the relationship between GL and the sub-ledgers with regard to the posting of the sub-ledger transactions into General Ledger. Once defined, this should not be changed as you may lose historical information (i.e. history buckets for transactions written to the files in the sub modules are not moved, adjusted or corrected when you change the accounting periods per year).
This levies tax according to GST (federal level) and PST (provincial level). Most provinces charge PST besides GST, but some charge PST on GST. If you are also using Tax by geographic area, then a stock item with a blank tax code is interpreted as being exempt from tax and the tax code assigned to the geographic area when calculating tax for that item on an order is disregarded. Enabling this after defining your product classes requires you to create the _GST product class manually.
This determines the tax applied to stocked order lines.
This uses the item's tax code.
This uses the tax code of the customer's area.
This uses the tax code of the customer's area (split into state, county and city rates - the total of which is used to calculate tax).
This uses the tax code against the postal/zip code (split into state, county and city - the total of which is used to calculate the sales tax).
Although always stored in a CCYYMMDD format, this option enables you to define how you want dates to be displayed and requested within SYSPRO, at company level. Dates in forms are determined by the Date format only (i.e. DDMMYY or YYMMDD). The short/long date format is not applied to any date fields in forms.
This overrides the date format settings made within the System Setup program.
This is the format in which you want all system dates to be displayed and requested within SYSPRO for this company.
This indicates how you want the system to display the long version of the date for this company.
This indicates how you want the system to display the short version of the date for this company.
This indicates how you want the system to display dates on reports printed within this company.
This displays how the setting for the Long date format will appear in the system.
This displays how the setting for the Short date format will appear in the system.
This displays how the setting for the Report date format format will appear in the system.
This lets you set your nationality code at company level. It overrides the setting made within the System Setup program, unless this conflicts with an existing tax option that has been defined.
This indicates the nationality of your company (e.g. USA - United States of America; GB - Great Britain; AUS - Australia; CAN - Canada; RSA - South Africa). The list of SYSPRO nationality codes is defined in the IMPNAT.IMP file located in the SYSPRO Programs folder. The nationality entered here affects the display of region-specific fields within the system (e.g. tax).
The Email/SMTP settings of the System Setup program are required for the following facilities:
- Forgot Password
- Multi-Factor Authentication
- Single Sign-on
- SYSPRO Supply Chain Portal
In a mapped-drive environment you will need to define the network permissions to invoke an executable program over the network. Microsoft Outlook is typically selected if you want to use simple MAPI mail.
This uses Microsoft Outlook (with its rich email client interface) as your preferred method of emailing within SYSPRO.
This uses any COM-aware email subsystem to email in SYSPRO
This uses the system-wide SMTP options configured within the System Setup program, instead of the options configured here.
If you enable this option, the Email/SMTP details configured here are disabled, but stored in the company record.
The following facilities rely on the Email/SMTP settings configured in the System Setup program to work:
- Forgot Password
- Multi-Factor Authentication
- Single Sign-on
- SYSPRO Supply Chain Portal
This is the default IP address of the specific SMTP server that SYSPRO will use to send messages.
This is the default email address of the sender of the message.
This entry must contain a valid email structure, such as auto.generated.mail@company.com.
This the email account's user name.
This is the email account's password.
This is the server port to be used.
This specifies that communication with the SMTP server requires SSL encryption (i.e. send email via an SSL connection).
This creates a log file detailing each program that is accessed by each operator. You can enable job logging selectively by module and program using the Operator Groups program.
This includes job logging entries for business objects invoked from e.net Solutions, Web-based applications, DFM and VBScripting. This may result in excessive log entries from automated and semi-automated processes. If you disable this option, then log entries are still created for business objects invoked from a regular SYSPRO program database updates or queries.
Includes job logging entries for running SRS reports. The log file lets you see the date, time and name of the operator who ran the SRS report.
Prints the name of the operator who made any postings to the journal file, on the report. This applies to the following journals: Receivables, Payables, Cash Book, Ledger, Inventory, Supplier amendment, Customer amendment, Inventory amendment and Structure amendment.
Prints the report options you selected for a report on the first page of any system report. You typically use this to indicate why entries are included/excluded from a report or if you print multiple copies of the same report with different report options. This will affect the time take to print SRS reports.
Prints and displays postal codes as a 5-4 field.
Closes a sub-ledger month automatically when you complete a month end within the relevant module. You typically use this if you generally only post to the current month. If you need to post transactions to a prior month then you will have to reopen the month manually.
If using shared inventory this indicates that custom forms configured for the shared company must be used for each of the companies sharing the same inventory files.
If using shared inventory this indicates that multimedia objects configured for the shared company must be used for all the companies sharing the same inventory files. You won't be able to view any Inventory multimedia configured in the individual shared companies.
This option lets the Multimedia program access objects using the presentation key length in the file path when you're using the %key variable in the multimedia object path.
It doesn't rename the multimedia files, it just alters the %key value returned for multimedia.
The key length of the Customer field is 15 characters. If you set the presentation length to 7 characters then the system looks for:
- 0000040.bmp if you have enabled the Presentation length for multimedia %key option option
- 000000000000040.bmp if you have not enabled the Presentation length for multimedia %key option
The key length of the Customer field is 15 characters. The key length of the Invoice field is 15 characters. If you set the presentation length of the Invoice field to 6 characters and the Customer field to 7 characters, then the system looks for:
- 000000000000040000000000000001.bmp regardless of whether the Presentation length for multimedia %key option is enabled.
This is the default number of decimals to use for all tax rates. This is applied to the Tax rate decimals field in the Browse on Tax Codes program. You can still change the number of decimals for individual tax codes, which will override your selection here. Only SRS reports support the use of 5 decimal places. For all documents on which the tax rate is printed, the use of 5 decimal places is supported on Standard, Word and SRS documents.
These options enable you to share inventories and general ledgers across companies.
If both Inventory and General Ledger are shared, then the Inventory Interface setup in the Inventory holding company is used to determine the ledger accounts to which transactions processed in the Inventory Movements program are posted.
If only Inventory is shared, then Inventory transactions update the files of the holding company and the General Ledger side of the transactions are posted to that company's own General Ledger files.
It isn't advisable to share Inventory files across companies that have different base currencies (GAAP assumes that the value of inventory is stated in the local currency of the company).
The value of any purchase or cost of sale costs is processed in the currency of the host company (i.e. transactions in the sharing companies aren't translated into the currency of any shared company).
A mixture of currencies results in inaccurate costs in both the host and sharing companies. However, if no transactions are processed across the companies' warehouses (e.g. you want to share Inventory for query purposes only) then this can be done without compromising the integrity of the General Ledger.
This is the holding company for all the GL master, history and detail transactions. It lets you produce consolidated financial reports for more than one company using the Financial Report Writer (only the Financial Report Writer can access the data of other companies). Ensure that the data paths defined for the sharing companies match those of the holding company and that the company control files are located in the same working folder for all companies sharing the GL database.
This is the holding company for inventory data. It provides you with a consolidated view of the stock holding of all companies if they all sell the same inventory. If MRP is installed, then the Requirements Calculation uses the inventory and bill of materials data from the Inventory 'holding' company, together with the sources of supply and demand from the company running the Requirements Calculation. Each company retains separate Order, MRP and WIP data.
All numeric formatting is also applied to any numeric custom form fields added.
This is the character to use for numeric fields containing decimals and must be different from the 1000's separator character. In a client/server environment, it must match the character defined in the Regional Settings of the client machine. Otherwise incorrect values could be saved for transaction entries processed in SYSPRO. Dots are translated to commas if the decimal character is defined as a comma (to accommodate numeric keypads that only have a dot to indicate a decimal point).
This defines a delimiter for numeric values over 999.00 (e.g. a value of 123456789.12 can be displayed as 123,456,789.12.)
This is the character (symbol) to use as the 1000's separator. It can be a space (e.g. if you want to have 1 000.00) and must be different from the decimal character. In a client/server environment, this character must match the character defined in the Regional Settings on the client machine. Otherwise incorrect values could be saved for transaction entries processed in SYSPRO.
These options enable you to indicate how transaction values must be printed/displayed in SYSPRO. Reports changed to support extended field sizes remain visually unchanged unless the printed values exceed the available print space (in which case the report print line could change to print two lines instead of one). You can override these settings at operator level.
This is the number of decimals you want to use for numeric values. If you enter zero here, then decimals are removed from entry and display/print fields when values are used. The number of decimals to show in values defaults to 2. All values are always held to 2 decimal places, regardless of any setting. This does not affect free-format stationery which assumes a minimum of 2 decimals for any price field and 3 decimals for any Inventory unit cost field.
You can override these settings at operator level using the Numeric formatting options.
This indicates how you want to print costs/prices on reports. Reports changed to support extended field sizes remain visually unchanged unless the printed values exceed the available print space (in which case the report print line could change to print two lines instead of one).
This is the character (symbol) to use as the 1000's separator (e.g. a value of 123456789.12 can be printed as 123,456,789.12).
This is the minimum number of decimals that must be printed for a cost/price field (e.g. a price of 123456789.12000 may be printed as 123,456,789.120 if the decimal option is set to 3). It does not affect free-format stationary (which assumes a minimum of 2 decimals for any price field and 3 decimals for any inventory unit cost field). The system-wide personalization option: Maximum decimals to show for price/cost controls the number of decimal zeros displayed in price and cost listviews.
This displays stock code-related quantities in listviews according to the Maximum number of decimals defined against the stock item.
This indicates how many decimal places to print for all labor times in reports. It applies to the printing of all Work in Progress operation times (such as run time, teardown time, wait time, etc.) on reports. It defaults to four decimal places, but can be set anywhere from zero to six.
This lets you convert from one currency to another using an intermediate currency (to conform with European Monetary Union regulations).
This prints a currency exchange audit line for each foreign currency transaction using triangulation.
This generates a distribution report from which manual postings to GL can be made. Accounts aren't validated and account descriptions aren't printed.
This prints detail entries on the Expense and Disbursement distribution reports to be summarized by ledger code before being posted to GL.
This prints each detail entry on the Expense and Disbursement distribution reports to be posted to GL. It also enables the zoom facility within the GL Query.
This prints detail lines for control accounts on distribution reports which can be viewed using the GL Query program and from within the relevant journals maintenance program.
If Accounts Payable is linked to General Ledger, then this creates the journal for GL from the AP transaction journal automatically whenever you successfully post a transaction in the Accounts Payable module. If you don't select this option, then you'll need to use the AP Invoice GL Integration and AP Payments GL Integration programs to manually create the journals for GL.
This posts journals (output by the AP Invoice GL Integration program) to GL automatically. Otherwise you'll need to use the GL Journal Entry program to post the journals manually after they're created. You can't select this if you've enabled the GL preference (and vice versa). Sub module journals are created, but placed on hold if a GL account used in the journal is on hold. You'll need to correct the error and post the journals manually.
This ensures that journals from the AP Payment Cycle are created with check numbers, where applicable. Otherwise journals are created using only the Execute AP Payment Run program without check numbers. Only when you print the checks and run the AP Payment Register program are the check numbers allocated to journals not yet posted. You can only select this if you have enabled both the Create GL journal and Post GL journal options.
This forces you to enter GL analysis information at the time the transaction is processed in the sub-module.
This lets you enter GL analysis information when the ledger journal for the transaction is posted (you can select an Ask Me Later option in the Capture GL Analysis Entries program) and the GL analysis information must then be entered using the GL Journal Entry program before the ledger journal for the transaction can be posted.
This generates a distribution report from which manual postings to GL can be made. Accounts aren't validated and account descriptions aren't printed.
This prints detail entries on the Payments and Sales distribution reports to be summarized by ledger code before being posted to GL.
This prints each detail entry on the Payments and Sales distribution reports to be posted to GL. It also enables the zoom facility within the GL Query.
This prints detail lines for control accounts on distribution reports which can be viewed using the GL Query program and from within the relevant journals maintenance program.
If Accounts Receivable is linked to General Ledger, then this creates the journal for GL from the AR transaction journal automatically whenever you successfully post a transaction in the Accounts Receivable module. If you don't select this option, then you'll need to use the AR Invoice GL Integration and AR Payments GL Integration programs to manually create the journals for GL.
This posts journals (output by the AR Invoice GL Integration program) to GL automatically. Otherwise you'll need to use the GL Journal Entry program to post the journals manually after they're created. You can't select this if you've enabled the GL preference (and vice versa). Sub module journals are created, but placed on hold if a GL account used in the journal is on hold. You'll need to correct the error and post the journals manually.
This forces you to enter GL analysis information at the time the transaction is processed in the sub-module.
This lets you enter GL analysis information when the ledger journal for the transaction is posted (you can select an Ask Me Later option in the Capture GL Analysis Entries program) and the GL analysis information must then be entered using the GL Journal Entry program before the ledger journal for the transaction can be posted.
If you intend processing inter-company Cash Book transactions, then we strongly recommend that you define the same General Ledger integration options in both SYSPRO companies
This generates a distribution report from which manual postings to GL can be made. Accounts aren't validated and account descriptions aren't printed.
This prints detail entries on the Cash Book distribution report to be summarized by ledger code before being posted to GL.
This prints each detail entry on the Cash Book distribution report to be posted to GL. It also enables the zoom facility within the GL Query.
This prints detail lines for control accounts on distribution reports which can be viewed using the GL Query program and from within the relevant journals maintenance program.
If Cash Book is linked to General Ledger, then this creates the journal for GL from the CB transaction journal automatically whenever you successfully post a transaction in the Cash Book module. If you don't select this option, then you'll need to use the Cash Book GL Integration program to manually create the journals for GL.
This posts journals created from the Cash Book module to GL automatically. Otherwise you'll need to use the GL Journal Entry program to post the journals manually after they're created. You can't select this if you've enabled the GL preference (and vice versa). Sub module journals are created, but placed on hold if a GL account used in the journal is on hold. You'll need to correct the error and post the journals manually.
This forces you to enter GL analysis information at the time the transaction is processed in the sub-module.
This lets you enter GL analysis information when the ledger journal for the transaction is posted (you can select an Ask Me Later option in the Capture GL Analysis Entries program) and the GL analysis information must then be entered using the GL Journal Entry program before the ledger journal for the transaction can be posted.
This generates a distribution report from which manual postings to GL can be made. Accounts aren't validated and account descriptions aren't printed.
This prints detail entries on the Inventory distribution report to be summarized by ledger code before being posted to GL.
This prints each detail entry on the Inventory distribution report to be posted to GL. It also enables the zoom facility within the GL Query.
This prints detail lines for control accounts on distribution reports which can be viewed using the GL Query program and from within the relevant journals maintenance program.
If Inventory is linked to General Ledger, then this creates the journal for GL from the Inventory or GRN transaction journals automatically whenever you successfully post a transaction in the Inventory module. If you don't select this option, then you'll need to use the Inventory GL Integration and GRN GL Integration programs to manually create the journals for GL.
This posts journals (output by the Inventory GL Integration and GRN GL Integration programs) to GL automatically. Otherwise you'll need to use the GL Journal Entry program to post the journals manually after they're created. You can't select this if you've enabled the GL preference (and vice versa). Sub module journals are created, but placed on hold if a GL account used in the journal is on hold. You'll need to correct the error and post the journals manually.
This forces you to enter GL analysis information at the time the transaction is processed in the sub-module.
This lets you enter GL analysis information when the ledger journal for the transaction is posted (you can select an Ask Me Later option in the Capture GL Analysis Entries program) and the GL analysis information must then be entered using the GL Journal Entry program before the ledger journal for the transaction can be posted.
This generates a distribution report from which manual postings to GL can be made. Accounts aren't validated and account descriptions aren't printed.
This prints detail entries on the Assets distribution report to be summarized by ledger code before being posted to GL.
This prints each detail entry on the Assets distribution report to be posted to GL. It also enables the zoom facility within the GL Query.
There is no Control account in detail option for assets because posting to asset control accounts have always been in detail.
If Assets is linked to General Ledger, then this creates the journal for GL from the Assets transaction journal automatically whenever you successfully post a transaction in the Assets Register module. If you don't select this option, then you'll need to use the Asset GL Integration program to manually create the journals for GL.
This posts journals (output by the Asset GL Integration program) to GL automatically. Otherwise you'll need to use the GL Journal Entry program to post the journals manually after they're created. You can't select this if you've enabled the GL preference (and vice versa). Sub module journals are created, but placed on hold if a GL account used in the journal is on hold. You'll need to correct the error and post the journals manually.
This forces you to enter GL analysis information at the time the transaction is processed in the sub-module.
This lets you enter GL analysis information when the ledger journal for the transaction is posted (you can select an Ask Me Later option in the Capture GL Analysis Entries program) and the GL analysis information must then be entered using the GL Journal Entry program before the ledger journal for the transaction can be posted.
This generates a distribution report from which manual postings to GL can be made. Accounts aren't validated and account descriptions aren't printed.
This prints detail entries on the WIP Part Billings Distribution and WIP Labor Distribution reports to be summarized by ledger code before being posted to GL.
This prints each detail entry on the WIP Part Billings Distribution and WIP Labor Distribution reports to be posted to GL. It also enables the zoom facility within the GL Query.
This prints detail lines for control accounts on distribution reports which can be viewed using the GL Query program and from within the relevant journals maintenance program.
If Work in Progress is linked to General Ledger, then this creates the journal for GL from the Work in Progress transaction journal automatically whenever you successfully post a transaction in the Work in Progress module. If you don't select this option, then you'll need to use the WIP Part Billings GL Integration program to manually create the journals for GL.
This posts journals (output by the Inventory GL Integration and GRN GL Integration programs) to GL automatically. Otherwise you'll need to use the GL Journal Entry program to post the journals manually after they're created. You can't select this if you've enabled the GL preference (and vice versa). Sub module journals are created, but placed on hold if a GL account used in the journal is on hold. You'll need to correct the error and post the journals manually.
This forces you to enter GL analysis information at the time the transaction is processed in the sub-module.
This lets you enter GL analysis information when the ledger journal for the transaction is posted (you can select an Ask Me Later option in the Capture GL Analysis Entries program) and the GL analysis information must then be entered using the GL Journal Entry program before the ledger journal for the transaction can be posted.
Entries are posted to this capital-type account to correct an out-of-balance situation in the General Ledger. The posted value can then be journalized out to the correct ledger code manually.
Entries are posted to this account when you run a GL Year End and choose to set expense and revenue accounts to zero, resulting in a net income/loss. This applies to ledger accounts against which a retained earnings account has not been defined. You can define multiple retained earnings accounts by defining them against your expense and revenue type ledger codes. The retained earnings account defined against a ledger code takes precedence over the account defined here.
This is the account to which the merchandise value of a supplier invoice is posted during processing in the AP Invoice Posting program if the account is not defined against the supplier. You should only enter a default account here if you charge all inventory purchases to one account and a very large portion of the invoices posted are inventory-related. This account is not applicable if the GRN system is in use.
This is the account to which the freight value of a supplier invoice is posted during processing in the AP Invoice Posting program, if the account is not defined against the supplier.
This is the account to which tax entries are posted during processing in the AP Invoice Posting and AP Permanent Entries Posting programs, if you selected to disburse tax over a single GL tax account; your tax AP tax distribution is set to detail or summary; and you require a global tax file.
If using the EC VAT system, then this is the account to which 'self-charged' VAT is posted when you purchase goods from a supplier within an EC Member State (excluding local purchases) and you supplied the supplier with your VAT details (i.e. the supplier does not include VAT on the invoice to you).
This is the account to which withholding tax entries are posted when processing supplier payments using the Payment Cycle Maintenance program and you selected Single GL tax account at the Disburse tax amount over setup option. This field is only displayed if the Withholding tax required setup option is enabled.
This is the account to which second tier tax entries are posted during processing using the AP Invoice Posting and AP Permanent Entries Posting programs. This field is only displayed if the Second tier tax required setup option is enabled.
If the Request QST amount setup option is enabled then this is the account to which the 2nd tier tax portion of settlement discount must be disbursed. Since tax is based on the gross amount before settlement discount is calculated when posting an AP invoice, when you take advantage of terms discount the amount of 2nd tier tax refundable to you must be reduced. The system passes a credit through this link to the tax recoverable account in GL.
This is the account to which the value of supplier invoices offset against customer invoices is posted when using the Customer-Supplier Contra program (typically a credit). This could be the same code you enter at the Contra suspense field on the Receivables form. The credit posted from offsetting the supplier invoices and the debit posted from offsetting the customer invoices are then posted to the same account, resulting in a zero balance in this account.
This is the account to which tax accrual entries are posted for suppliers whose tax assessment is defined as Self (USA tax only).
This is the account to which previously-claimed input tax (not yet paid to a supplier) must be repaid to the tax authority. The account is credited by the AP Tax relief program and debited by the Execute AP Payment Run program when paying invoices against which tax relief was previously processed. The account must be manually adjusted when using the AP Invoice Posting program to post adjustments, debit notes and credit notes against invoices for which tax relief was previously processed.
This is the ledger account description for merchandise printed on the Accounts Payable distribution report if Accounts Payable integration to General Ledger is set to Not linked to GL distribution report.
This is the ledger account description for freight printed on the Accounts Payable distribution report if Accounts Payable integration to General Ledger is set to Not linked to GL distribution report.
This is the ledger account description for input tax printed on the Accounts Payable distribution report if Accounts Payable integration to General Ledger is set to Not linked to GL distribution report.
This is the account to which exchange rate gains or losses are posted when using the AR Payments and Adjustments program. You can override this account at the time of entering a payment against a foreign customer. Also, if you did not use the AR Currency Variance GL Interface program to define interface ledger accounts by branch/currency, then the AR Exchange Rate Revaluation program also uses this account to post exchange rate variances.
This is the account to which withholding tax entries are posted when processing customers' payments using the AR Payments and Adjustments program. You can only access this field if the Withholding tax required option is enabled against the Setup Options > Tax > Company Tax Options form.
If you enabled the option to request the tax portion for an invoice, then the tax portion of an adjustment or discount amount is posted to this account from the AR Payments and Adjustments program.
This is the account to which the value of customer invoices offset against supplier invoices is posted when using the Customer-Supplier Contra program (typically a debit). This could be the same code you enter at the Contra suspense field on the Payables form. The credit posted from offsetting the supplier invoices and the debit posted from offsetting the customer invoices are then posted to the same account, resulting in a zero balance in this account.
This account is used for tax relief and recovery in Accounts Receivable (reserved for future use).
This is the account to which the expense/revenue side of a Balance rounding correction is posted by the AR Period End program. This is an expense/revenue type account.
This is the account to which the balance sheet side of a Balance rounding correction is posted by the AR Period End program. This is an asset type account.
This is the account to which inter-company distribution amounts are posted. It serves as the link for inter-company transactions entered in the Cash Book Deposits and Withdrawals program. This account is only used if Cash Book is linked to General Ledger and you intend entering distribution codes for companies other than the one in which you are working.
This is the default account to which the tax portion of any deposit (or adjustment to a deposit) is posted during processing in the Cash Book Deposits and Withdrawals program. All Tax only transactions for deposits processed in the Cash Book Deposits and Withdrawals program are posted to this account.
This is the default account to which the tax portion of any withdrawal (or adjustment to a withdrawal) is posted during processing in the Cash Book Deposits and Withdrawals program. All Tax only transactions for withdrawals processed in the Cash Book Deposits and Withdrawals program are posted to this account.
This is the clearing account used when processing inter-bank transfers using the Cash Book Deposits and Withdrawals program. This should be an asset-type account. If Cash Book is linked to General Ledger, then this must be a valid SYSPRO ledger account. In addition, you can only select the Interbank Transfers option from the Cash Book Deposits and Withdrawals program if this account is specified.
This is the ledger account description for deposits printed on the Cash Book distribution report if Cash Book integration to General Ledger is set to Not linked to GL distribution report.
This is the ledger account description for withdrawals printed on the Cash Book distribution report if Cash Book integration to General Ledger is set to Not linked to GL distribution report.
This account links the Inventory Control module to the non-stocked control accounts in the General Ledger. The debit side of a non-stocked inventory receipt is passed through this link. Non-stocked items must be received against a purchase order. You cannot run the Inventory Movements program if you don't enter a ledger code here.
This is the account to which cost of sales adjustments are posted, arising when the inventory balance on hand goes negative. This only applies if you are using average costing and you have allowed the warehouse to go negative. The adjustment value is calculated as the new cost less the old cost multiplied by the quantity received. This account is used when a receipt is entered where the current quantity on hand is negative and the costing method is based on average costing.
This is the account to which postings are made when the receipt of a subcontract purchase order line is made directly to a job, and the GRN suspense system is not required.
This is the account to which distribution entries are posted during processing within the AP Invoice Posting program, where GRN matching is selected.
This is the account to which distribution entries are posted during processing in the AP Invoice Posting program, where GRN matching is selected and there is a variance between the actual receipt value and the invoice value. Purchase price variances that are below a pre-defined percentage that you set to ignore are posted to the GRN suspense account.
This is the account to which rounding errors are posted during the processing of a receipt into stock of an item that requires Activity Based Costing. Postings are only made to the ABC costing variance account if the value of the total cost of the receipt differs from the value of the new unit cost multiplied by the receipt quantity.
This is the account to which postings are made for goods in transit transactions processed against a warehouse which has not been assigned a Goods in transit control account. This account (usually defined as an asset) is debited when processing a non-immediate transfer out, and credited when processing a transfer in.
This account (usually defined as an asset) is debited at the time of creating a dispatch note, and credited once the dispatch note is invoiced. If this account is defined against the warehouse from which the items are being dispatched, then the Dispatched but not invoiced account held against the warehouse takes precedence. Dispatches involving non-stocked items will always use the account defined here.
This is the account to which the cost/value amounts are posted for asset additions, asset disposals and changes to asset cost/value amounts.
This is the account to which postings are made for the gain/loss you incur when you dispose of an asset using the Asset Disposal program.
This is the account that is
This is the account to which postings are made when an asset is revalued using the Asset Revaluation program.
This is the account to which postings are made for asset additions,
asset disposals and changes to asset cost/value amounts. The cost/cash price
of asset additions is
This is the expense account to which book value depreciation amounts are posted. If you are depreciating assets at individual asset level then the account entered here is ignored for book value depreciation, regardless of whether a ledger code is defined against the asset. If no ledger code for book value depreciation is defined against the asset, then the transaction journal is created with a blank ledger code (i.e. it does not default to the depreciation ledger code defined here).
This is the balance sheet account to which book value depreciation amounts are posted.
This is the clearing account used when transferring assets between SYSPRO companies.
This is the account to which the difference between the book value in the current company and the transfer book value to the new company is posted.
This is the default account to which the value of work in progress is posted when a job is created, if a work in progress account has not been assigned to the stock item for which the job is being created. The ledger code defined in the Capex in Progress field is used for all jobs created for and linked to a capex requisition line.
This is the account to which postings are made during the Backflushing function of the Inventory Movements program if there is a variance between the entered cost of the manufactured item and the cost of the item's material and labor allocations calculated by the system.
If you're using standard costing, then this is the default account to which WIP variances (falling below your specified value) are posted automatically when receiving a finished part into stock from a completed job. The account is only used if the Automatically cleared variance account is not defined against the warehouse.
If WIP inspection is required, then this is the default account to which the WIP value of goods received into inspection is posted. The account is used if a WIP inspection account is not held against the warehouse into which the goods are being received. You can't receive items from inspection into stock using the WIP Inspection Maintenance program if you haven't defined a WIP inspection account here or against the warehouse and you didn't enable the Request ledger code at transactions option.
This is the default account to which the value of accrual promotions must be credited when processing a sales order. The GL promotion accrual account defined against the promotion code is used if it differs from the code entered here.
This is the default account to which the value of the accrual promotion must be debited when processing a sales order. The GL promotion expense account defined against the promotion code is used if it differs from the code entered here.
This is the default account to which deduction amounts are accumulated in the General Ledger (typically the AR Deduction Control Account). This can be changed for individual deduction codes. The GL deduction receivable account defined against the deduction code is used if it differs from the code entered here.
This is the default account to charge when a deduction is resolved for a reason other than a match to a corresponding accrual promotion account. This can be changed for individual deduction codes. The GL deduction resolution account defined against the deduction code is used if it differs from the code entered here.
This is the expense account charged when a deduction is written off and can be changed for individual deduction codes. The GL deduction writeoff account defined against the deduction code is used if it differs from the code entered here.
This is the account to which postings are made for RTS items accepted for a credit, or rejected and scrapped transactions.
This is the account to which variances (positive or negative) are posted when an RTS is accepted and the price differs from the original captured price.
This is the account to which the cost of rejected goods returned by a supplier needs to be expensed.
This is the account to which posting is made when an RTS item is accepted for credit or replacement.
The entry creates an accrual in GRN Suspense against the anticipated credit note from the supplier.
This is the account to which posting is made to decrease the cost of goods sold and to move the value of non-stocked goods returned via RMA into the RTS control account.
The RTS Journal Report must be run to generate this journal entry.
This is the account credited by the freight charges for an RTS item that has been accepted by the supplier.
The default AP control account is debited by this amount in anticipation of a supplier credit for freight charges.
This is the account credited by the handling charges for an RTS item that has been accepted by the supplier.
The default AP control account is debited by this amount in anticipation of a supplier credit for handling charges.