Controls the automatic authorisation of invoices. If the system key does not exist or is set to YES, then authorisation of invoices is attempted when exiting in the invoice entry program (as per manual authorisation). Other values are:

NO = follow authorisation procedure but do not change the invoice status.
ASK = follow authorisation procedure and ask the user if they require the status to be amended.
AUTO = automatically authorises all invoices and can thus be used in an EDI environment.

Type YES if the invoice is to be automatically authorised. Type ASK if you wish the user to be prompted to authorise the invoice. Type NO if the invoice is to be manually authorised.

Automatically post purchase orders? This system key determines whether individual invoices can be posted automatically to Accounts Payable after they have been authorised. If invoices are not batched, that is POBATCH is set to NO, this system key should be set to YES if purchase invoices can be posted automatically once they have been authorised.

Type NO if purchase invoices are to be posted manually.

Is a batch system used for Purchase Order Processing?

Type YES if purchase invoices are to be entered in batches.

Type NO if purchase invoices are to be entered individually.

The batch number is generated automatically by either the system key PLLASTINV or the system key PLLASTINVA if this key has been set up and is valid.

Check values against the budget totals. If project DA0246-Budget Control on Requisitions is licensed then:

Type PREVENT to display a warning if the budget is exceeded. Authorisation can ONLY go ahead if the is user is also a GL budget authoriser in User Activity maintenance.

Type WARN to display a warning if the budget is exceeded. If project DA1316-Graphical MPS is also licensed and POUSERBUDG=YES then the budget check flag in user activity maintenance will come into effect.

Leave blank if no check to be performed.

Which budgets are checked in Requisitions? This system key is used by project DA1314-Project Budget Checking In Requisitions.

GL - Only check General Ledger (NLBUDCODE) budgets.
PROJ - Only check Project Ledger (PRBUDCODE) budgets.
BOTH - Check the Project Ledger budget for the given project, if it is not in the budget check the General Ledger budget for the mapped General Ledger code

Which budgetary values are to be used? This system key is used by DA1314-Project Budget Checking In Requisitions.

BLANK - The budget for the whole financial year is checked.
CUM - The cumulative budget up to the period of the proposed commitment is checked.

Purchase order buyer authorisation mode.

NO - No buyer authorisation required.

AUTO - Automatically assign buyer codes to purchase orders wherever possible. The buyer code is assigned from the stock records for the detail lines. If the stock items vary and several buyer codes are available, the buyer code is left blank. A valid code will have to be entered manually.

YES - Buyer codes must be assigned manually. The system checks that the buyer code has been entered and that the order value has not exceeded the buyer's limit.

Note that the value you enter in this key is ignored if system key POBUYIDOFF is set to NO.

Switch off the functionality that defaults the Buyer ID to the current user when a purchase order is raised?

NO - the Buyer code is to default to the current user when a purchase order is raised.
YES - the Buyer code is to be obtained from system key POBUYAUTH.

Should the price list be checked?

NO - any discount for supplier will be applied to all products.

YES - discount will be applied to only the product(s) on the supplier's price list.

Determines how changes to the required date on a purchase order header affects the required date on the order detail line.

NO - any change to the required date on the order header does not affect the order lines.
GLOBAL - changes to the required date on the order header are applied to all detail lines. The user is prompted to confirm the changes.
MATCH - changes to the required date on the order header are applied to any detail line where the order line req'd date matches the original required date. The user is prompted to confirm the changes. For example: the required date on the header is 01/07/10. Order line 1 req'd date = 01/07/10. Order line 2 req'd date = 08/07/10. The order header required date is changed to 05/07/10. Therefore, the Order line 1 req'd date is now 05/07/10. Order line 2 req'd date is still 08/07/10.

This system key is used to determine whether or not VAT can be clawed back.

Type YES if you want to be able to claw back any VAT from discount taken.

Type NO if the VAT clawback facility is not required for your system.

Automatically clear the free of charge ('FOC') text from the Discount field on a Purchase Order detail line when a non-zero List price is entered?

Type YES to automatically clear the FOC indicator from the Discount field on a Purchase Order detail line when a non-zero list price is entered for the product or service.

Type NO to prevent the FOC indicator from being automatically removed from the Discount field on a Purchase Order detail line when a non-zero List price is entered for a product or service.

Update commitment actuals when raising an invoice?

Type YES to update commitments with actuals (A type) when invoices are raised. This system key only applies if your system is also set up to use Commitment Accounting (DA0269). This system key is not applicable if your system is set up to use Project Accounting (PR_INSTAL=YES).

Type NO if commitments are only to be updated with actuals when the invoice is posted.

Reopen commitment? This system key only applies if your system is set up to use Commitment Accounting (DA0269) and Reserves and Commitment Extensions (DA0585), and if you are not using Project Accounting (PR_INSTAL=NO).

Type YES to reopen a previously fulfilled commitment when a credit note is applied to it.

Type NO to prevent a previously fulfilled commitment from being reopened when a credit note is applied to it.

Note this system key does not apply when processing invoices for orders from consolidated requisitions (project DA0682-Consolidated Requisitions is licensed).

When are commitments posted from? This system key defines at which stage in the requisition cycle the commitment to raising an order is made. Once the commitment has been made, the details are posted to the General Ledger.

Blank = No commitments posted.
FINAL = After final authorisation.
NLCODE = After budget authorisation.
PORDER = At Purchase Order creation.

Type NLCODE if the posting is to be made when the General Ledger code is first entered. If, subsequently, the requisition is amended, a reverse posting is made to remove the commitment.

When completing a purchase order line at the invoicing stage, is the completed date of the line to be set to the invoice date or the system date?

Type INVOICE if the completed date of a Purchase Order line is to be set to the invoice date.

Type SYSTEM if the completed date of a Purchase Order line is to be set to the date the invoice is posted, i.e. the system date.

When completing a purchase order line at the receipt stage, is the completed date of the line to be set to the receipt date or the system date?

Type RECEIPT if the completed date of a Purchase Order line is to be set to the receipt date.

Type SYSTEM if the completed date of a Purchase Order line is to be set to the date the receipt is entered, i.e. the system date.

Should PO receipts check for suspended contracts?

Type YES - the PO goods receipts will not be accepted.

Type WARN - you will be told that the contract has been suspended but will be able to accept delivery.

Type NO - no warning will be given and the receipt will be accepted as normal.

Type of cost used in order entry. The system will search the Supplier Information table or the Price List table, depending on the POPRICING system key setting, and use that cost first. If the price has not been set up, the system will check this system key to determine which cost on the Stock table is to be used. If the Supplier Information table or the Price List table are not being used to cost the stock, enter one of the following values: STANDARD = cost of the stock to be based on the fixed unit cost;
LAST = cost to be based on the last, that is current, cost;
EXPECTED = cost to be based on the price you expect to pay for your purchases.

If the EXPECTED cost is to be used and this has been set to 0 on the Stock table, the value will be determined by the setting of the STCOSTTYPE system key.

Use number of decimal places from currency record?

Type YES if the cost fields in the Purchase Order modules are to be displayed using the number of decimal places for the currency being used by the supplier. For example, if the base currency is Lire and the supplier is using French Francs, then the costs will be displayed with 2 decimal places.

Otherwise, type NO, the value recorded in the system key STVALDEC will be used.

Use the current currency rate. Not the rate when ordered.

Type YES if you wish to use the currency rate at the time that the stock is received.

Type NO if you wish to use the original currency rate when the stock was ordered.

Which analysis code is the department code (1,2,3)? This system key defines which transaction code field you want to use for recording the department code in purchase order entry. This facility is used in Purchase Order Requisitions, if installed, but is optional in Purchase Order Processing. The forms may then be amended so that the appropriate transaction code field is displayed as the `Department code' field.

Type 1 if you want to use the value entered in the `Transaction code 1' field as the department code.
Type 2 if you want to use the value entered in the `Transaction code 2' field as the department code.
Type 3 if you want to use the value entered in the `Transaction code 3' field as the department code.

Note that the department codes are set up as narrative codes in the General Configuration tables. See the Narrative Types help page for further information.

Type YES to use the default Expense and Revenue codes on detail lines when a Project code has not been entered on the sales order header.

Type NO to have no default Expense and Revenue codes on detail lines when a Project code has not been entered on the purchase order header.

This system key is only used if your system is set up to use Project Support for Sales and Purchase Order Processing (DA1197).

This system key is used with purchase invoices.

Type YES to allow deletion of individual invoices that have been authorised. Note that this is only possible for users that are allowed to authorise invoices.

Type NO to prevent authorised invoices from being deleted.

The database name storing the Purchase Order Processing (PO) data (the database name must end with an exclamation mark ('!')). If you are using the standard, or current database to store your Purchase Order Processing data you can leave this key blank. If Purchase Order Processing data is stored on a different database you must specify where the data is stored, for example, if the Purchase Order Processing data is stored on database syscomp1 set this key to syscomp1!.

Can Goods Received be greater than Goods Ordered?

Type YES if received quantities can exceed ordered quantities.

Type NO if received quantities must always be equal to or less than ordered quantities.

Generate unique headers in consolidate orders?

NO - the batch number will be used as the requisition number on the consolidated purchase orders (BATCHXXXXX).

YES - the consolidation process will attempt to provide Unique requisition numbers on purchase orders by adding a running count (BXXXX9999), XXXX is batch number, 9999 is running count.

The price list used in GRN margin calculations.

Enter the price list which will be used in margin calculations when producing PO receipts.

Enter a price list number if you want the suspended receipts to use the price per unit for a given stock item, from a supplier price list which is defined by the price list code in this system key.

Leave the key blank if you want the suspended receipt to use the price per unit from the stock item.

Print page headings on each page of a Goods Received Note (GRN)? Type YES to print the GRN headings at the top of each page of a multiple-page GRN.

Type NO if you only require the GRN headings to be printed at the top of the first page of a multiple-page GRN (the default).

This system key is used by the option Receipts. See also system key POPRINTGRN.

Force a page throw at the end of a Goods Received Note (GRN)?

Type YES to force a new page at the end of a GRN.

Type NO if you do not require a page break at the end of a GRN print (the default).

This system key is used by the option Receipts. See also system key POPRINTGRN.

Which costs are to be used when calculating the landed or add-on costs? The setting of this system key defines which costs are to be used when calculating the landed or add-on costs, i.e. standard, current, expected.

Type STANDARD if FIFO batches are to be created with stock costed at standard cost.

Type CURRENT if FIFO batches are created with stock costed at current cost. The cost can be amended with the actual cost when the receipt is entered.

Type EXPECTED if the costs from the purchase order line for the stock item are to be used.

Type ACTUAL if FIFO batches are to be created with stock costed at standard cost. The current costs will be updated from the purchase order line expected cost.

Type ZERO if the value defined in the POCOSTTYPE system key is to be used.

Are gross based transactions in use?

Type YES to include Unrecoverable VAT with the Requisition value.

Type NO for Requisition values to exclude Unrecoverable VAT.

Allow entry of analysis codes in Purchase Order Processing invoices?

Type YES to allow entry of analysis codes in Purchase Order Processing invoices, regardlesss of setting of system key PLABCANAL. Note that analysis codes can only be selected via Browse and validated if PLABCANAL is YES.

Type NO if analysis codes cannot be entered in Purchase Order Processing invoices.

Controls when Purchase Invoices are to be removed from the live data tables.

Type A if Purchase Invoices are to be archived when the option Remove Completed Orders is run.

Type P if Purchase Invoices are to be removed when the Purchase Order Processing Period End is run – note that if set to P the options Period End and Remove Completed Orders are not available if project DA0199-Vendor Analysis is licensed.

If this system key is blank the default value is A if system key POARCHIVE is set to YES and project DA0199-Vendor Analysis is licensed or system key PR_INSTAL is set to YES, otherwise the default value is P.

Retain detail lines for posted invoices ?

Type YES if purchases order invoice detail lines for posted invoices, are not to be removed during Purchase Order Processing Period End.

Type NO if all detail lines for posted invoices are to be removed during Purchase Order Processing Period End.

Is GRN required before an order line can be invoiced?

NONE (or blank) - with the GRN required? checkbox ticked, it is possible to invoice an order line before it has been received. A warning message indicating that you are trying to invoice more than has been received is displayed.

ANY - with the GRN required? checkbox ticked, it is possible to invoice an order line which has been partly received. The system prevents invoicing of an order line which has no receipt. It is possible to invoice more than received once something has been received.

PART - With the GRN required? checkbox ticked, it is not possible to invoice an order line for more than has been received.

FULL - With the GRN required? checkbox ticked, it is not possible to invoice an order which has not been fully received and it is not possible to invoice more than received.

Validation level for invoicing with tolerances. When purchase order processing with tolerances, this system key controls the behaviour of invoice entry when it encounters values that are outside of the relevant tolerance allowed. Valid values are NONE, WARN and FORBID.

Type FORBID = the system will prevent invalid values.

Type WARN = the system will accept the value but only after a warning.

Skip buyer activity/posting code/budget authorisation.

0 = full authorisation process, i.e. to use separate buyers and General Ledger activities;
3 = skip buyer activity;.
4 = skip buyer activity/posting code, i.e. if you do not wish to have either a separate buyer or a General Ledger activity;
5 = no separate buyer, General Ledger code or final authorisation activities.

This system key defines the method of requisitioning that is to be used, and is used to validate the status at which requisitions are to be raised when actioning MRP recommendations.

Controls added functionality within landed costs.

Type ACTUAL if you wish to use the actual landed costs entered via the Purchase Orders Receipts program.

Type ESTIMATED if the landed costs are to be taken from the Supplier Category/Product Category matrix. If no record exists, the costs will be assumed to be zero and no record will be written to the Landed Costs Log table.

This system key is used when obtaining the next requisition or schedule number. It defines the action to be taken when the POLASTREQ or POLASTSCH system key is locked. Type YES, NO or a number. When an attempt is made to obtain the next requisition or schedule number a message is displayed informing the user that the POLASTREQ or POLASTSCH system key, as required, is locked. When YES, the return key must be repeatedly selected until the POLASTREQ/POLASTSCH system key is free and the next number can be obtained. When NO, selecting the return key to confirm the message returns the user to the program. Multiple attempts can be made to obtain the next requisition or schedule number with the user being returned to the program each time the message is confirmed until the POLASTREQ/POLASTSCH system key is free and the next number can be obtained. When a number, the return key can be repeatedly selected up to the number of times defined until the POLASTREQ/POLASTSCH system key is free and the next number can be obtained, otherwise the user is returned to the program when they can retry. Note that the options Buyer Activity (POLASTREQ is required when splitting a requisition) and Automatic Requisitions always behave as if POLASTLOCK is YES. The options Requisition Entry, Call off/Blanket Requisitions and Action Call off/Blanket allow any of the settings to be used.

Last Purchase Order receipt number used. Enter the last goods receipt note number used. This can be any valid 5 digit number, e.g. 00036 or the value 'STOCK', in which case the value of system key STLASTGRN is used. The first digit is alphanumeric, i.e. 0-Z. The program automatically adds the transaction prefix Q. If you type STOCK, the program uses the automatic numbering sequence defined in system key STLASTGRN and adds the prefix G. If receipt notes are to be numbered automatically, set this key to a number, one less than the first number required. Thereafter, the value in the key will be updated by the appropriate program whenever a new receipt is entered.

Last Purchase Order receipt number used (alphanumeric).

Use this system key instead of POLASTREC if you want to generate alphanumeric receipt numbers, resulting in a larger number of recept numbers being available.

This system key holds the last generated alphanumeric receipt number.

Leave this system key to use POLASTREC instead.

If receipts are to be generated automaticallyset this system key to a five character string one less than the first receipt number required, for example 00000 to start numbering batches from 00001. Thereafter the value of the system key will be updated by the appropriate program whenever a new receipt is created.

The format for the batch number is XNXXX where X is an uppercase alphanumeric character (A-Z, 0-9) and N is a number (0-9).

Examples:
Value 00001, next value is 00002
Value 00009, next value is 0000A

Which purchasing lead time is used by MRP. When calculating recommendations in MRP, which lead time is used?

STOCK - The lead time defined on the stock record.
SUPPLIER - The lead time defined on the Supplier Information record.

The following values are acceptable as pre-defined apportionment methods:

w = allows apportionment of a header element cost to each receipt detail line by its given weight, in relation to the total weight for the given receipt.

q = allows apportionment of a header element cost to each detail line by its receipt quantity , in relation to the total quantity for the given receipt.

v = allows apportionment of each detail line by its given value, in relation to the total value for the given receipt.

d = allows apportionment of each detail line by its given dimension, (where dimension is either height, length, or width, as defined by POLANDDIM) in relation to the total dimension value.

Add PO Location records during PO receipts? Where purchase order records were created with Location Codes (project DA0361) switched off, and receipts are required for the orders.

Type YES to indicate that PO Location records are to be created. If this is not done, GRN's cannot be printed for the receipts. The default value is NO.

Controls how purchase orders are removed from your system when deleted.

Type YES if purchase orders deleted using the Purchase Orders option are only to be marked as deleted. They must be removed from your system via the option Remove Completed Orders.

Type NO if purchase orders deleted using the Purchase Orders option are to be removed immediately.

Match more than invoice/credit quantity?

WARN - When matching more than the invoice/credit quantity, on leaving the matching form a warning will be displayed.

FORBID - Matching more than the invoice/credit quantit\y will be forbidden; you are forced to stay in the matching form until the matched quantity is not more than the invoice/credit quantity.

blank - No warning when matching when matching more than the invoice/credit quantity.

This system key is used by Purchase Invoice Matching to Goods Receipts (project DA0533).

Are alternate purchase units allowed? This system key governs whether products can be stocked in one unit and purchased in one or more other units.

Type MULTIPLE if you want the stock units to convert from buying units to stock units automatically and the conversions are to be taken from the Inventory Control Unit table. This allows multiple conversions for a single stock item. For example, an item may be stored individually, but it could be purchased in cases, boxes or individually.

Type BUY if you want the stock units to convert from purchase units to stock units automatically and conversions are to be taken from the Inventory Control Stock table. This allows a single conversion from the purchase unit defined on the Stock record for a particular item to the stock unit defined on the Stock record. For example, an item may be purchased in boxes of six, but stocked individually.

Type NO if you do not want stock units to convert from purchase units to stock units automatically. This means that all stock items are stored and purchased in the same unit.

Note: The BUY setting is for users upgrading from previous releases. Check with your Dealer for which settings apply to your system. The BUY function is not valid for use with Requisitions. It will have the same affect as setting this key to NO.

Allow zero and negative requisition lines?

Type NO to disallow zero and negative requisition lines.

Type YES to allow zero and negative requisition lines.

Use matrix % to calculate actual landed cost.

Type YES if, where the landed cost matrix entry is a percentage type, you wish the landed costs on each purchase order receipt line to be calculated by applying this percentage to the line values. The header landed cost values are just for memo purposes in this case.

Type NO if, where the landed cost matrix entry is a percentage type, you wish the landed costs on each purchase order receipt line to be calculated by apportioning the values entered on the receipt header.

Type in a valid currency type which will be used for the planned exchange rates. Purchase order entry will record the relevant exchange rate details on the Variance History table. If running Purchase Order Processing variance analysis, this will be used in the calculations of the purchase order variances.

The currency type must be a valid currency type which is defined in General Configuraton tables.

Validation level for Price List Entry. This system key governs the level to which suppliers, items or currencies are to be validated when they are entered on price lists.

Type NONE if suppliers which do not exist on the Supplier table or products which do not exist on the Stock table can be entered on a price list. These actions can be taken and no warnings are given. This option allows price lists to be set up before the Supplier table and Stock table are completely correct. It is assumed that the price lists will be checked carefully after entry and that these errors will be resolved before the Purchase Order Processing module is used.

Type WARNING if you want to display a warning when an invalid supplier or item is entered on a price list. The invalid entry can still be made.

Type FORBIDDEN if you do not want to allow invalid entries of suppliers or items. The invalid entry must be removed or changed to a valid entry.

Use multiple Accounts Payable accounts?

Type YES if the Accounts Payable module uses several separate data directories for service items.

Type NO if there is only one Accounts Payable data directory.

Use POPERIOD to validate the effective date?

Type YES if the effective date is to be validated against the POPERIOD system key during Purchase Invoice Entry and against PLPERIOD system key during Purchase Invoice Posting.

Type NO if the PLPERIOD system key is to be used to validate the effective date during both Purchase Invoice Entry and Purchase Invoice Posting.

Is Purchase Order Processing posting direct to Accounts Payable and the General ledger? This system key controls whether the purchase orders are posted to the Accounts Payable module and/or the General Ledger.

Type NO if purchase invoices are to be posted to Accounts Payable as unposted batches. These batches will then have to be posted from within Accounts Payable via the options Invoices entry/posting or Batches.

Type DIRECT if the purchase invoices are to be posted directly to Accounts Payable and General Ledger respectively. This can only occur if system key PLNLPOST is set to YES.

Please note that if PLNLPOST is set to NO, you will not be able to run the Invoices option within Purchase Order Processing. This key must be set to NO if system key POREGINV is set to YES.

This key determines whether or not unauthorised purchase invoices may be posted.

Type YES if unauthorised invoices can be posted.

Type NO if unauthorised invoices cannot be posted (the default). A message will be displayed if a batch contains any unauthorised invoices.

If this system key is missing or blank, all invoices must be authorised.

Pricing Method used in Purchase Order Processing. This system key governs the prices used during the Purchase Orders entry program.

Type P if you want to use prices from the Price List table or, if these do not exist, the prices on the Stock and Service tables.

Type S if you do want to use prices from the Supplier Information table or, if these do not exist, the prices on the Stock and Service tables.

Type ALWAYS if Goods Received Notes are always printed after receipts have been entered in the Receipts program.

Type OPTIONAL if operators are to be given the option to print Goods Received Notes after entering receipts. This option is provided by the F10 function key.

Type NEVER if Goods Received Notes are not to be printed.

Do you wish to print Purchase Orders?

Type YES if purchase orders are to be produced for distribution to suppliers. Receipts cannot be entered for a purchase order until the order has been printed.

Type NO if printed purchase orders are never issued to suppliers. The order status will be set automatically to order printed when entry is complete and receipts can be entered against this order immediately. Purchase orders raised from MRP and Purchase Order Requisitions will automatically be raised as status printed .

Print company name and address on Purchase order?

Type YES if the Purchase Order Print program is to print the company details defined in system keys COMPADDR1 to COMPADDR6 at the top of each purchase order.

Type NO if this information is already preprinted on the purchase order forms.

Should the reserve accrual include project details?

Type YES if the reserve accrual should include the project and /expense lines for the detail and journal.

Print pricing information on Purchase Order?

Type YES if the purchase orders are to show quantity, discount percentage, price and net value figures for individual items, and the total order value.

Type NO if stock/service codes, descriptions and quantities only are to be printed.

Type of exception trapping for suspended receipts. Exceptions on suspended receipts can be trapped when they are posted. When posting suspended receipts, the over and under receipts will be recognised, and the user prompted to enter reasons for the over and under receipts. This system key is used in conjunction with POGDSREC. The following values can be entered:

OVER = the received quantity is more than the quantity outstanding;
UNDER - the received quantity is less than the quantity outstanding;
BOTH = the received quantity is either more or less than the quantity outstanding.

Type YES if you wish to input the expiry date and bin-number for detail lines on the suspended receipt.

Type NO if you do not wish to be prompted to enter this information.

Type YES to duplicate suspended receipt lines. All details for the selected line will be copied to the following line and a new line number will be assigned.

Type NO if you do not wish to duplicate the detail lines.

Type YES if you wish to duplicate detail lines on a suspended receipt. All details for the selected line will be copied to the following line and a new line number will be assigned.

Type NO if you do not wish to duplicate the detail lines.

Type YES if both standard and registered invoice posting is required, otherwise type NO. This system key only applies if POBATCH is YES and POPLPOST is NO.

If this system key applies, also note system key PLREGFORCE, which if set to YES, forces Registered Invoices posting by user in Purchase Order Processing.

Enter the requisition number template to be used of up to 10 characters. All requisition numbers will be checked for consistency with the template, e.g. if PQFMTCHAR is set to @#, this key was set to @@###, the requisition number will generate AA0001, etc.

Type YES if the Requisitions module is installed and available for use by other modules.

Type NO if the Requisitions module is not installed or requisitions may not be accessed by other modules.

Type YES if you wish to force the use of automatic numbering of purchase order requisitions. You will need to set up the number using the system key POLASTREQ.

Otherwise, type NO, automatic numbering will be optional.

This system key applies to Purchase Order Processing receipts and suspended receipts when returning stock via a negative receipt.

Type ORDER if the cost on the receipts audit trails is to remain as entered/displayed in Purchase Order Processing Receipts.

Type STOCK if the cost on the receipts audit trail is to be set to the stock history cost of the returned stock.

This system key has no affect if projects DA0361-Locations Codes and DA0370-European Tax are licensed, or if DA0940 is licensed, in which case the behaviour is automatically ORDER.

The sales margin is calculated as the difference between unit price and the current cost, and then expressed as a percentage of either the unit price or the current cost.

Type YES if you wish to express the sales margin as a percentage of the unit price.

Type NO if you wish to express the sales margin as a percentage of the current cost.

This system key is only used when project DA1197-Project support for Sales and Purchase Order Processing is licensed and system key PR_INSTAL is set to YES.

It defines the type of validation for browse, and selection of, Project Accounting expense and revenue codes for Purchase Order Processing Services. Type one of the following values to define which records are presented when browsing for an expense/revenue code via the Purchase Order Processing option Services:

IGNORE - to allow both expense and revenue codes to be shown.
WARN - to show both expense and revenue codes but to warn if the code selected is of the wrong type for the ledger.
PREVENT - to allow only expense codes to be added to Purchase Order Services, preventing the entry of revenue codes.

Calculate settlement discount on the gross or nett values of an order or invoice?

Type GROSS to calculate settlement discount on the gross value of an order or invoice, i.e. goods and VAT – note that POSETTCALC must be set to GROSS if system key CESETTDISC is set to YES.

Type NETT to calculate settlement discount on the nett value of an order or invoice – note that POSETTCALC must be set to NETT if system key CESETTDISC is set to NO.

Is the scheduled shipment date to be used?

Type YES if the schedule shipment date (SSD) is to be used rather than the required date.

Type NO if the required date entered on the purchase order is to be used as the date by which the order is required.

This system key is used in Purchase Order Processing, Invoice Entry.

Type YES to display fully completed pages when entering invoice details against a purchase order.

Type NO if fully completed pages are to be skipped.

Type YES if you wish the initial detail line form to display the description field. If requested, the stock details can then be entered on a subsequent form. A key press will allow you to toggle between the two.

Alternatively, type NO to initially display the product code and the General Ledger codes.

Type YES if a single Purchase Order Company is being used with multiple Requisition and Purchase Ledger Companies, and it is required to select only those Purchase Orders whose phpl_company company field matches the "Accounts Payable Company" field, in the Requisitions linked enquiry option.
POPLMULTI must be set to YES, PLMULTCOMP must be set to NO and the POFILESDD keys will need to be set to the single Purchase Order Company in each of the other companies.

Otherwise type NO.

This system key is used to allow some steps of the validation process to be skipped when generating requisitions from Schedules. Requisitions raised when this key is set to YES will be raised either at With Requestor, Authorised or Complete status. The general action of this key is to skip the Value Authorisation stage. Requisitions are only set to With Requestor if Budget Validation fails and the status of the requisition goes beyond the point where Commitments are written.

If you want to use normal validation steps as would be followed when raising the requisition manually type NO.

Allow reuse of Serial Numbers for Supplier Returns. This system key is used by Purchase Order Receipts to allow for the reuse of serial numbers. The serial number assigned to a returned item may be reassigned to a new receipt.

Type YES if serial numbers may be reused. Batch traceability will be maintained.

Otherwise, type NO if serial numbers are not to be reused.

This system key controls whether the supplier is to be validated against the three supplier codes defined on the Service record. This facility allows an operator to ensure that only recommended suppliers are used for each service.

Type YES if you wish the supplier codes entered on the Service record to be validated against the Supplier table.

Type NO if there is to be no validation of suppliers and services.

Type YES if the value fields in the Purchase Order modules are to be displayed using the number of decimal places from the system key STVALDEC.

Otherwise, type NO, the value fields will be displayed to the number of decimal places for the currency being used by the supplier.

This only applies to suppliers using foreign currency.

This system key is only used when project DA0650 is licensed.

Type REQUIRED if you require supersessions for an ordered product to be selected according to the order required date.

Type SYSTEM if you wish to retain the existing behaviour where supersessions are selected according to the system date.

This system key is only used when DA0650 is licensed.

Type AUTO if you require supersessions for an ordered product to be selected automatically if valid.

Type MANUAL if you wish to retain the existing behaviour where supersessions are proposed by the system and accepted by the user.

If the key is set to AUTO the system will allow ten levels of supersessions before switching into manual mode. This is to prevent the system looping if recursive supersessions have been entered.

This system key is used when browsing supplier information for a specific supplier. The standard browse displays the supplier code in the first column followed by the combined warehouse and product code in the second column. An alternative browse can be used which excludes the supplier code from the browse so that the combined warehouse and product code for the supplier is displayed in the first column.

Leave this system key blank to use the standard browse, i.e. the supplier code, followed by the warehouse and product code. Additional searches within the Browse form are not available.

Type 2 to use the alternative browse, i.e. so the combined warehouse and product code for the supplier is displayed in the first column. Additional searches within the Browse form can be performed upon the warehouse and product code. Please note that this method of browsing may be slow if the data tables are very large.

The values O, P and/or L may be entered in any order. Supplier information lookup will be attempted using each one in turn.

The preferred and last supplier will be taken from the stock record for stock items.

For services, the preferred supplier will be taken from 'Supplier 1' and the last supplier from the 'Supplier Code' on the Purchase Order Processing Service record.

This system key controls the way that the details defined in the supplier Analysis Code A, B or C field are to be copied to purchase orders. If this system key is missing or the project is not licensed, it will behave as if it was set to S.

Type S if the supplier analysis code is to be copied to the order header analysis code. The code on the header will then be copied to the order detail.

Type H if the supplier analysis code is only to be copied to the order header. It will not be copied to the order detail.

Type D if the supplier analysis code is to be copied straight to the order detail and not copied to the order header.

Type N if the supplier analysis code is not to be copied to the order header or detail, or from the header to detail.

Type L if the supplier analysis code is not to be copied to the order header or detail, but allow the order header analysis code to be the order detail.

Type B if the supplier analysis code is to be copied straight to the order header and order detail, however the order header analysis code is not to be copied to the order detail.

Allow unmatched service lines on the invoice? This system key determines whether purchase invoices can be posted when they contain detail lines for services which have not been matched to purchase order lines. A purchase invoice cannot be authorised if it contains unmatched product detail lines.

Type YES if purchase invoices can be posted automatically when they contain service lines which are unmatched with purchase order lines.

Type WARN if a warning is to be displayed and the operator is to be given the option of whether to post a purchase invoice with unmatched service lines.

Type NO if purchase invoices are not to be posted until all detail lines have been matched to purchase order lines.

Update stock current costs from Invoice Posting?

Type YES if you wish to update the current material costs on the Stock table when an invoice is posted.

Type NO if you do not wish to update the material costs on the Stock table when an invoice is posted.

Update the Supplier Information table with the received value?

Type YES if you want to use the calculated cost of each order line to update the price stored on the Supplier Information table record.

Type NO if you do not want the supplier information to be updated.

Type YES if you want to force the use of F6 Next Number function key in Orders/Receipts/Invoices.

Otherwise, type NO.

Use Budget Check flag in requisition authorisation? Used by project DA0361-Location Codes.

Type YES if the Budget Checking flag for a user, set in User Activity, is to be used in the budget authorisation of requisitions.

Type NO if the Budget Checking flag for a user, set in User Activity, is NOT to be used in the budget authorisation of requisitions.

NOTE: Project DA0361 is required to set the flag in the Purchase Order Processing User Activity program. If POBUDGEXCD is set to PREVENT it overrides this system key. Project DA0246-Budget Control on Requisitions is required to perform Budget Authorisation.

Purchase variance calculation method. This system key controls how the Purchase Order Processing variances will be calculated when entering a Purchase Invoice if the functionality is licensed. Valid values are A or B.

Method A = Purchase Price Variance, PPV = Receipt Quantity * (Invoice Price - Standard Cost) / Order Exchange Rate. Purchase Exchange Variance, PEV = Receipt Quantity * (Order Price / Order Exchange Rate - Order Price / Invoice Exchange Rate). Purchase Quantity Variance, PQV = (Invoice Quantity - Receipt Quantity) * (Invoice Price / Invoice Rate).

Method B = No variances are calculated. The system keys PONLPPV , PONLPEV and PONLPQV define the General ledger posting codes used for each value calculated. Variance analysis functionality is only supported when running a standard cost system.

Check VAT values? This system key determines whether or not the VAT values are checked at the end of entering an invoice.

Type YES if VAT is to be recalculated and checked against the original order amount at the end of invoice entry. The VAT amount is checked for every VAT code and if a difference is found, the VAT codes and values together with a warning message are displayed. The original value can be accepted or the VAT can be recalculated.

Type NO if VAT is not to be checked after an invoice entry.